Our three remotes will not see and add new engines. The Wi-Fi system works fine will add new engines with no problem. The remotes will run engines that are loaded in the remotes. I reset one remote, that didn't help. Reloaded V5.0 and that didn't help The remotes will read the TIU's Any suggestions?
Replies sorted oldest to newest
When trying to add an engine, be sure that only that engine is on a powered track, and be sure that tracks has a good signal. You don't, I assume, already have 99 engines in the remote. AFter resetting the one remote, did you then re-add all the engines, or simply clone it?
Weird! As RJR mentioned a programming track with a good signal (or equivalent) is a must.... We're running version 5 with 4 tiu in super with no adding problems... Do you think the problem might be Wi-Fi software related?
As you know engine IDs stick with the engine if that's any clue?? The engine must have the same ID in all remotes.
After resetting the one remote it would not find a engine in add mth engine. All the current engine info is backed up in the mth dcs program and I did not try to download it to the remote. I tried to find two different engines on isolated tracks that have great signal with no luck. I disabled the WiFi system and that did not make a difference. These remotes have been getting weird over the past several months... Batteries are good they run the engines in the memory OK but the WiFi system is much better in response.
The biggest difference between accessing engines via the DCS App vs. the DCS Remote is that when using the remote you go though the transceiver boards in the TIU and the remote. These can become loose.
I'd suggest connecting the remote to the TIU's Remote Input port with a 4-conductor (curly) telephone handset cable.
 | This and a whole lot more is all in “The DCS Companion 3rd Edition!" This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at MTH's web store! |
If all the remotes are getting weird, then it is probably not the remotes. Check the layout ground wires. Are all TIU black outputs connected together? They must be. Only on Rev G were they internally connected.
After resetting, are you saying that remote wouldn't find any engine to add?
For what it's worth.. we know a engine already added to the remote will usually respond to commands even if the track signal is low..... 2 s 3s 4s. Adding engines requires a much higher dcs signal.... 7 and up.
You may want to double check the dcs signal.
As Barry suggested tether the tiu & remote... Don't be surprized if you get a message TIU error after tethering.... just cycle tiu & remote power .
Access to this requires an OGR Forum Supporting Membership
