All command not working correctly

Have you tried this with the TIU and remote tethered?

When the ALL command does not work, turn the remote off and on. If I move an engine from ACTIVE to INACTIVE, or INACTIVE to ACTIVE, the ALL command stops working until I turn the remote off and then on.     

Yes we tried tethered and it still would not work.  I finally gave up and used another handheld and that one works properly.  In the course of testing and rebuilding the CSX MU I found another issue. With the MU (lead engine forward trailing engine rear forward, the MU would go correctly with the MU selected. With the "ALL: command, the MU went correctly for the initial direction.  When direction was depressed the MU engines went in different directions.  This only occured with the "ALL" engines selected. If the MU was selected the MU engines were back in sync.  Note that in Relase 4.01 the MU operated normally.

If you have multiple remotes with the same engine mix loaded, why not do a reset of that remote, then backup the other remote and load it into the problem remote?

John, I may try to do a handheld "read"  for that loop and see if it picks up the engines and then rebuild the MU's for that loop on that handheld or just move the handheld to the loop that only has one Proto 2 engine (SMR loop with ERR and Proto2).  I would not need to utilize the "ALL" command.  In hindsite the 4.3 MU issue is the source of my issues with the 2nd loop when I had the MU with both engines going against themselves and effectively stopped and the GG1 ran into the tail of that train. That started a more than 10 hour mess over 3 days where I tried to get my 2nd loop back up and running.  Also this MU had been created under 4.01.  My earlier MU's all start up forward because the issue with MU's had been an issue under 3.X and it was fixed under 4.01.  My other MUs all work with 4.3 because they all all engaged as forward for both lead and trailing engines.