DCS or PS2, PS3 issues

I would tether the DCS Remote to the TIU with a phone handset cord to ensure your problems are not with the transmitters in the TIU or Remote. If everything works well while tethered, you may need to re-seat the transmitter in the Remote or TIU.

This situation sounds just like a REV. G TIU on my bench that is labeled "BAD". This TIU did many of the same things that you are describing above. If you can get your hands on a known good loaner TIU or just buy a new unit outright, I bet you'll solve your problems.

Yet another revision G TIU that is in my parts bin will only add PS3 engines on the FIXED 2 port but operate them on any of the 4 outputs (once added). However, PS2 engines will add and operate flawlessly all day on any of the 4 output ports. This particular TIU is listed as "degraded".

I have found that TIU's previous to the revision L do not work as well with newer PS3 engines especially when loading and saving sound files.

I was going to buy a new TIU eventually, but hopefully after a new rev came out with the issues of the shorting TVS's resolved and PLEASE an external antennae connection.

 It's been almost 8 years since the rev L came out.  New rev to correct and enhance operation in development??

Anyone proficient at delicate soldering want to put an antennae jack on a new rev L?

Gray Lackey

try loading one engine on the track at a time. No other engines passenger cars, lighted caboose,Nothing that is powered. Its best with just a 3 foot section of track not hooked to anything,  just TIU and transformer.  Hopefully this will get you going. 

Per Clem K's suggestion I put in a programming track (on fixed 2). 

My 44 tonner with PS3 that wouldn't respond to anything previously was deleted and re-added and woks fine again (WHEW).  I can't get any PS2 engines to program though.  The C&O E8 I finally got to previously add was deleted (ala the 44 tonner previous) but won't re program.  Out of 5 or 6 tries the system locked up while "LOOKING FOR ENGINE" and  had to be hard reset by removing a battery, one time I got "ENGINE ERROR".  I tried a PS2 Army genset and it kept giving me "ENGINE IN REMOTE" even though it is not.

Per H1000 I did all this with the remote tethered to rule out communication issues.  Also per H1000 I think I must label this TIU DEGRADED.

Looking for the latest rev with the new TVSS's.  I have a lot of ballast work and other stuff to do.  Hopefully I won't go mad with my H TIU.  I guess I can continue to use it to test new track with the PS2 engine that's in it and the PS3 engines that will add.

On your test track make sure both outside rails are wired together. you need good ground.  Happy to hear one engine started.

Clem

When you get an engine to work, try running a signal strength test to see what you get. Always make sure that any TMCC/Legacy engines are off the track.

From some of the posts, I get the feeling that there's several things going on. It's hard to guess at just what's happening by the posts. I would always suggest being more methodical, if possible writing the exact steps down and each and every result as well.

 I would also suggest checking the most basic stuff, like correctly having the correct polarity, red posts to the center rails, make sure the TIU is address #1, make sure the remote only has #1 TIU in it, etc.

 I wouldn't label the TIU bad unless you have poor signal all the time and narrow it to the TIU. Did you check signal on the test track?

It can be anything else like track connections, and other equipment causing signal loss. Where's the TIU connected to the TMCC stuff in the chain? (or vice versa)

It sounds like you know more of what's happening than you explain in your posts?

I think you should fully troubleshoot the TIU in a lab situation to eliminate all of the elements of the layout as possible cause for your problems. I'd remove the TIU from the layout and set it up on a test bench with a short test track. Test each channel individually while powering the TIU with the AUX power port.  Make sure that you can add and fully control all functions of both a PS2 and then a PS3 engine on each channel.

The above procedure is how I was able to determine that one of my older spare REV. G TIUs was degraded. It would work well with PS2 engines on all channels but I was only able to add and control PS3 engines on FIXED 2. Even after the PS3 was added on the good FIXED 2 channel, I was not able to find (read) or control it on any of the other three TIU channels.

I also used Mark DiVecchio's @SanDiegoMark RTC train control (website) program to force commands to the outputs of the degraded TIU. This program was very interesting as would allow me to do things the DCS remote won't. For example issuing commands to and engine address even though no engine has been identified at that address. My degraded TIU was able to issue commands and the PS3 engine would follow them, however the acknowledgement from the PS3 was never received. One thing I remember is that I could turn the bell on but it would not turn off again when I issued that command.

Mark's software does require additional hardware to allow your PC to interact with the TIU so be aware that more is needed than just his program to use it with your TIU.