Try wiring fixed output 2 to the isolated track, then try again.
I do apologize. I overlooked that. When you did the conventional (1W5B) reset, did you have all DCS signal off the track and get 2 toots when you were done?
If you have this problem with 2 TIUs. I don't think you have a hardware issue. I have some ideas based upon recent efforts to add 3 locos to a wifi app, but want to hold off suggesting this procedure.
New thought. You said two remote/TIU pairs. If the content of both remotes is not identical regarding locos and their IDs, you'll have a problem. I suggest pick the remote whose keys best reflect your wishes for layout, and back it up to your PC, using Loader 5.0. Then reset the other remote, which will clean out the data
Place one of the recalcitrant locos on an unpowered track. Using the reset empty remote, try a read. If no locos come up, try add engine. If either gives you an engine, edit the engine address to some ID number you've never used. Post results and we'll go on from there.
You said engine runs in conventional. If you cut power to the track, do sounds continue for more than 5 seconds or so? If not, bad supercap or battery, so engine can't hold an ID.
Dave Zucal posted:Try wiring fixed output 2 to the isolated track, then try again.
Tried FIXED 2 with no luck. 
Is it possible you may have the red & black wires crossed at the track? Not likely if the engine remains dark and silent but apparently with proto-3 it doesn't matter. However it does matter with proto-2 (red to center rail)
We know the read finds the tiu... so the remote and tiu are communicating.
You really can't check out the dcs signal if you can't add an engine.... I'm guessing this may be something simple we've overlooked.
Since you reset both TIU, Both tiu would be TIU #1. hopefully you only have 1 tiu powered up Not both while testing .
Menu/system/ dcs set up/ AON ... turns the dcs signal on to all channels. Never hurts to re do.
Gregg,
Only if he did a Factory Reset.
Greetings All,
After exhausting every possible fix I could think of, as well as the ones suggested by my fellow forum members, I believe the problem to be resolved. 
I Re-Loaded the DCS 5.00 software into both of the TIU's and Remotes and I was able to enter both the Genset AND the F40PH. 
WOO HOO!! 
Again, I would like to thank everyone who took the time to respond to my call for help. 
And a BIG thanks to Barry Broskowitz for taking time to expeditiously answer my emails. As it has been said many times before, this is a great forum with many like minded folks that are willing to help when called on to do so! Problem Solved!! 
Chief Bob (Retired) 
Great news Pufferbelly. Pat yourself on the back. That was something I would have never considered. When you said you had already upgraded to 5 in both TIUs, one would assume the upgrades completed correctly. I think from now on I'll run the upgrade process twice to play it safe.
Dave,
I think from now on I'll run the upgrade process twice to play it safe.
That's not necessarily a good idea. The odds of the second attempt being corrupt are the same as those of the first attempt. 
It is necessary, after upgrade is complete, to check remote & TIU to assure that the upgrade was successful. Sometimes when doing a remote upgrade, the process prematurely ends. Those of us who have done many upgrades at York have encountered this.
So we best make sure we see the window pop up that says "upgrade is complete" to be sure it's 100% loaded.
Best way is: Turn on remote. Current version on remote will appear on the screen. With TIU powered up, on remote, go to System/TIU setup/TIU version. Current version on TIU should appear on the screen.
- Both Remote/TIU pairs (Rev. L and Rev. G) were successfully upgraded to 5.0 and continued to function as expected until today.
- All functions of my "Test Engine" (MTH Premier Genset) functioned as expected using the Rev. L TIU and Remote that was upgraded last year.
Hey guys,
I have two loops on TIU AND REMOTE upgrade 6.1 . Both on z1000 bricks . 20 MTH engines scattered on the two loops.
Purchased a new Premier F7 proto3 . I couldn't get it to add on the fixed one which was powered up with fixed 2. Always had good luck adding engines this way amazingly.
The problem ended up ocurring when I shut down fixed 2 and used fixed 1 on a single 30 inch track. No problem with the F7 being added but I had to reenter all the other engines back to the active list when I put everything back to the two loops DCS . All were proto3 except one proto2 diesel.
BIG surprise...... one GP30 Premier proto 3 from a lash up gets a "no engine on track " . It was listed in the inactive list with the other Gp30, but when i tried to move it back to the active list , it disappeared. It just sits on the track with no indication of any function.
I did move it to a separate single track with a Z1000 and a Z controller. It had full functions even smoke .
I did the horn and 5 bells reset and got the 2 horn reset signal. I did this about a half dozen times with good success.
Moved the engine back on the two loop layout and fired everything up. I couldn't find an issue with some of the engines on the active list that I tried to operate. ......."No engine on track " for the GP30 though.
I kept trying the DCS reset and recover methods that have been on the forum so many times .........The GP 30 just sets there dark and lifeless. I've repeated the whole conventional and command methods with the same previous results hoping for a miracle. 😩
Help , my brain hurts 🤕
