Help with updated App - Engines not responding

Go to: More.../Advanced Features/System Settings/TIU Settings and verify that your TIU is found.

Yeah it shows up as TIU 1 - 2FCE.  The app also transitions from having the message "no TIU found" to it being removed after refreshing it.  I'm just at a loss at to what could be the issue.

Refresh the app and then refresh the engine list by pulling down on the Engine Roster Screen.

Have tried that many times still does not find them.  With the engines immediately powering up into idle/neutral, does that indicate that there is an issue with no signal making it to the track?

With the engines immediately powering up into idle/neutral, does that indicate that there is an issue with no signal making it to the track?

Yes, that's correct, assuming that they show up in the Inactive Engine List. Have you verified that the app has the DCS signal turned on for all TIU channels?

• More.../Advanced Features/System Settings/TIU Settings
• Select a TIU
• Ensure that the DCS signal is turned on for all channels.

Yes turned on for all channels.  TIU firmware confirmed at 6.10.  WIU at 1.1.  Is there any chance the engines are stuck with an address from when I used them last, so that the updated app and TIU/WIU firmware would render them "stuck" in this state?  The App sees the TIU, I have full functionality in the App over the TIU, the WIU is connected to home network same as smart device.  Using fixed 1 input and output.  USB connected from WIU to TIU.  

Also, no engines on inactive list.  Cannot add MTH engine either.

It sounds as if the problem is either in the TIU, or the wiring, since the engines aren't being seen by the app and aren't getting a watchdog signal.

First, use the app to turn the TIU's DCS signal off and then back on for each channel. See if things improve.

Second, reset the TIU. This will only lose Custom Sounds and Record/Playback sessions. See if things improve.

Third, connect the TIU to a short test track, using each channel in turn, to see if you can access the engines. If you cannot, the problem is the TIU or the WIU, more likely the TIU..

Last, if you have a remote, you can tether it to the TIU and attempt to access the engines in that fashion. If you cannot, the problem is more than likely the TIU.

Tried all the above with no effect.  Reset the TIU, reloaded 6.10 with no issues.  Reloaded 1.1 into the WIU with no issues.   If it’s the TIU it shows up on the consumer loader 5.0 with no issue and responds to the App.  Disappointing if it is the TIU as it’s only 2 years old and has not been used much.   

Opened the TIU and fuses look good, no obvious damage.  Hate to go buy another when it’s not for certain where the problem lies.  Is there a way to isolate the problem to a faulty TIU or WIU?

Seems odd they apparently function normally individually yet the signal does not seem to be making it to/from the tracks.  

Really appreciate the help, any last thoughts or recommendations? About to throw the towel in.

Barry--

Ok, have one more piece of info.  I hooked up the Remote Commander that came with the set (start-up 2-8-0 PRR set) and when I applied power, it sat there as it should, yet, when I use the remote and press SU/SD, nothing happens.  When I went back to the WIU/TIU setup, it started moving down the track with no sounds/lights.  I removed power, then added it, and it went back to the standard startup into idle/neutral, and not discover-able to the app.  Does this point to an issue likely with the two engines?  Do the engines need to be reset potentially and if so, is this possible either through the app or the remote commander?  

Appreciate any insight with this new info.  Thanks!

The Remote Commander will not operate any engines that were previously loaded into the DCS Remote, as yours were, unless the engines are Factory Reset first.

If your engines are newer PS3 engines, you may be able to reset them from the Remote Commander by pressing SND, DIR, -

It seems like the issue is with the TIU. Have you tried using all four TIU channel, while also providing power to the TIU for itself via either Fixed #1 Input or the Aux. Power port.

Have you disconnected the layout and tried the TIU powered thru fixed #1 directly to a short piece of track?

What size layout? any plan of it available to see? how is it wired? what type of track? type connections?

what are you using for power? wire?

Do you have the loops broken in at least one spot? are they wire in blocks?

What else is on the tracks and/or drawing power?

There are many variables that can be causing the signal to suffer.

Barry's book is a great place to start.

Originally just a small oval about 60”x36”.

All of the testing I’ve been doing is on just a short piece of track after I encountered the initial problem.

 Powering with a Z-500, TIU REV L, WIU, and the latest app. Trying to simply run just one PS3 Railking 2-8-0 or PS3 Railking 4-6-0.  

Worked last year no problem, though I did have issues with the 2-8-0 not responding to the DCS Commander it came with and a friend needed to restore factory default, it wouldn’t respond.

With everything updated and the new app, I am now encountering this issue.  So with the DCS Remote Commander and the lock-on powered by the Z-500, engines will sit idle as they should apparently receiving watchdog signal, but do not respond to the DCS Remote Commander, I was just using this as a test, I used the app and WIU last time I was set up.  But with power through fixed 1 (tried all channels, switching polarity, cycling DCS Signal on/off in app as Barry suggested) I still get an immediate power up to neutral with sounds and lights.

For those more experienced, is there a possibility of the engines having an address issue?

or, is it possible there is something wrong with the TIU eventhough it appears to respond and update correctly etc?

My best guess is the TIU's signal generators are gone, possibly due to a bad component that all 4 channels share.

Thanks for the input and assistance troubleshooting.  A new TIU solved the problem, so lesson learned is that a TIU can apparently function 100% normally yet have an issue with its DCS signaling or generators.