I have two remotes now and I want to clone all the engines from my original remote to the other. My original remote works great running trains. It has no trouble finding the TIU when wireless. If I hook up a tether to try and run anything or to upload any engine data, it can't find the TIU. The new remote can communicate both wireless and tethered. I also purchased a back-up TIU and the same thing happens with the new TIU. I looked in the 4-pin socket of the remote in trouble to see if anything was shorted but found nothing shorted. Any suggestions?
Replies sorted oldest to newest
Do you have the same version of DCS on both TIUs and both remotes? Has one of the TIUs been assigned a different address (it should if both will be turned on at the same time).
Sorry for the delay. Yes, both remotes are on 4.10 and going to TIU #1. The remote with the problem will work fine in the wireless state but will not work with a tether. The other remote will work wireless and tethered (same cord used). Can the RJ-11 jack on the remote be replaced or is it part of the circuit board? Is there something internal that could be causing the loss of signal?
I have two remotes now and I want to clone all the engines from my original remote to the other. My original remote works great running trains. It has no trouble finding the TIU when wireless. If I hook up a tether to try and run anything or to upload any engine data, it can't find the TIU. The new remote can communicate both wireless and tethered. I also purchased a back-up TIU and the same thing happens with the new TIU. I looked in the 4-pin socket of the remote in trouble to see if anything was shorted but found nothing shorted. Any suggestions?
Did you assign the back up TIU another number first?
The remotes can only have one TIU number 1 is my understanding.
When the remote is tethered to a TIU, it will communicate even if there are a host of TIU #1 boxes around. The tether restricts the communication to ONLY that TIU/Remote combo. Also, the TIU that has the remote tethered to it will not be affected by any other remote trying to address TIU #1.
Lima, my experience is that I could detect no difference when all my 4 remotes had the same ID.
Are you sure the cable is good? Does it work tethered to a different TIU? Does another remote work tethered to that or another TIU? Have you tried resetting the remote?
When the remote is tethered to a TIU, it will communicate even if there are a host of TIU #1 boxes around. The tether restricts the communication to ONLY that TIU/Remote combo. Also, the TIU that has the remote tethered to it will not be affected by any other remote trying to address TIU #1.
Understand that, still have not got an answer to did he give the new TIU a higher number because I'm expecting more issues
Don't have a remote handy, doesn't the remote just have the stiff wires to contact the phone jack conductors upon insertion? Think you can just look in the open socket and see if all 4 are still parallel to each other.
Yep, it's exactly like the jack on a telephone handset, that's the cable that you use. It must have all four wires, some handset cables only have two.
GRJ, I read his posts as saying that the cable works with one remote. It almost has to be something in the socket. I think Lima is right about the stiff whiskers.