Skip to main content

I have the premium app on 2 iPads and 1 iPhone. After a long stretch of trouble-free operation, about half of my PS2 and PS3 locos are on the dead track. Engines that were running fine 10 minutes  ago quit right in the middle of what would have been a normal run and refuse to be resurrected from "inactive" to "active".  But there is no set pattern: (2) PS2 GP38s in a consist are running and one engine suddenly goes "inactive" right in the middle of a run. The other is fine.

To add insult to injury, I occasionally get "no WIU found" even though it was working 2 minutes ago. Start-stop-start-stop. I think I have reset everything you can reset. I deleted the app and re-loaded that. Everything is a mess!

The only thing I did recently was add my new iPhone 14Pro, which seems to have been a mistake. I have since deleted it from that one phone. Would that make everything go berserk???

Thoughts anyone?

Original Post

Replies sorted oldest to newest

I had the exact situation last week regarding engines all of a sudden dropping like flies, going inactive, inability to resurrect, with some still working and no set pattern.  The only difference, I do not have a WIU/wireless device.  My situation was the same as you with just the TIU and remote.

I could not re-activate by selecting engines and the remote started displaying all sorts of error message such as out of range, not on track along with other strange error messages…all out of the blue, just went nuts after a long trouble free stretch of working just fine.  No set pattern either...a couple of PS2 and PS3 engines continued to work just fine during all the chaos.

Here's what I ended up doing to get back to normal:

  1. Disconnected all wiring from the TIU channels.
  2. Removed *all* the engines from *all* tracks.
  3. Factory reset the remote.
  4. Factory reset each engine via a Z-4000 connected to a conventional loop.
  5. Connected an isolated test track to one channel on the TIU and added each engine back to the system while having the remote tethered to the TIU.
  6. Then added one loop back to the TIU and tested each engine on that loop.
  7. Then added the next loop to the another channel and continued to test the newly added engines.
  8. Reconnected the rest of the loops to TIU channels and tested multiple engines on multiple loops/channels.

Seems to be all glued back together for now. Have no idea why DCS lost its marbles as I have not made any changes to wiring, track, engines, etc. for ages and everything is back to normal...crossing fingers.

Hi again, and thanks to all. Especially kj356 for sending the link to prior discussions. I had searched "MTH woes" and a couple other "MTH...." subjects before I wrote my post, but turned up nothing. I was trying to avoid re-inventing the flat tire...LOL.

I only have one WIU. It has always worked flawlessly. After reading for a bit, I'd agree it's an Apple problem, unless I missed someone complaining about Android apps. Trying to get ready for some winter here tonight, so I may not pick this back up for day or so. I had one engine the app still saw but it was acting up so I did a factory reset. Now it's "gone" again. Sigh!

I also noticed when fiddling with one of my not-so-happy iPads that it was already in airplane mode. All the MTH engines and my 3 week old Atlas are getting kicked off the rails until I get this fixed. Lionels will have to do for now...LOL

Best regards, and stay warm!

Add Reply

Post
The DCS Forum is sponsored by
×
×
×
×
Link copied to your clipboard.
×
×