Originally Posted by GGG:
Mark, The test at the friends is where I would go. No blink on the TIU is an issue.
You can try a factory reset on TIU and a reload of TIU software and see if it runs on FIX 1 after the load.
I think the TIU has issue with the higher voltage, more then the engine. MTH uses a Z-4000 and would have run it in command mode at 18-20V.
So if it runs fine at your friends house, the TIU is having issues with higher voltage, and the probably is causing issues with the PS-3 and some how corrupting the data signal that goes to the Boiler board driving your motor. G
I am suspicious the TIU is the problem also. Actually, I have had intermittent trouble with it almost since I got it in March 2014. I thought the problems were with me, since I was new to Command control afather 45 years in HO, N and O. I have other topics on the Forum on TIU. It finally completly failed at 11 months. After 2 months at MTH, I got it back, and all was fine until I got the PS3 J in mid May, and just got it back last week. Now it may be the TIU is the problem. I pushed the budget to buy the J. My other DCS engines I bought used, one is a 2007, and the other is a 1997 upgraded to PS2. I just took a "voluntary" early "retirement", so if the TIU needs repaired, I will have to run the J with the Z750 controller for the foreseeable future.
Sorry to whine, I try to stay positive, but my total experience with DCS has been a disappointmeant at best. I really, really like the sound on DCS engines, but the hassles I have had have made me really question the expense. More times than I can think, I pulled the MTH engine off the track, put a postwar engine on the track, and ran without the sound. It was more satisfying... This is just getting too expensive.