开云体育

Hello everyone,

I upgraded my DR5000 to YD7001 the other day and for the most part it went well and I'm up and running. I had a couple of niggles i.e. Dodgy USB cable, and I had to re-jig the S88 settings to get it to see the YD6016ES-GND for my toggle switches.

Prior to the upgrade, I used a Digitrax wired throttle (DT-602) and a LNWI unit with TCS UWT-100.

Since the upgrade (I removed the LNWI unit as it should now be obsolete) I'm using a combination of my wired throttle (DT602) and TCS UWT-100 via WiThrottle service from the YD7001.? My issue is that when I take up the TCS throttle and control a loco that was previously controlled by the DT602, the status of that session is not updated on the Loconet throttle, but it does update the other way around i.e. on the TCS when I use the DT602.?

Any ideas or thoughts on how I can workaround this? I realize that prior to the upgrade, I was effectively using 2 Loconet throttles (1 x wired, and 1 x LNWI), but I'm a little surprised that the session can update only 1 way.

Thanks.

On Sat, Mar 16, 2024 at 04:59 AM, Rafferman wrote:

My issue is that when I take up the TCS throttle and control a loco that was previously controlled by the DT602, the status of that session is not updated on the Loconet throttle, but it does update the other way around i.e. on the TCS when I use the DT602.?

Hi,

Can you describe a bit more elaborate what updates what and what does not ?

Now I conclude that the DT602 is not updated while operating the TCS ???

Greets,

Karst

Yes, the dt602 does not update the TCS throttle, but it works the way around.?

Hmm... an even more confusing statement ;)? ( since it's exactly the opposite of what I concluded )

Please try to elaborate what you are doing on either Throttle an what is/is not updated from which one.

?

Greets,

Karst

?

Sorry Karst, my mistake and you're assumption was correct.

?While operating the TCS, the DT602 does not update. It's not a massive problem, but if I pick up the TCS handset after previously using the DT602 (and it's still left plugged in), the DT602 seems to "refresh" and then sends it's update over to the TCS. This can result in the loco stopping or a function turning off or on depending on how the DT602 was left.

Hope that makes sense.

Thanks.

On Mon, Mar 18, 2024 at 08:21 AM, Rafferman wrote:

?While operating the TCS, the DT602 does not update. It's not a massive problem, but if I pick up the TCS handset after previously using the DT602 (and it's still left plugged in), the DT602 seems to "refresh" and then sends it's update over to the TCS. This can result in the loco stopping or a function turning off or on depending on how the DT602 was left.

Aha...

1. While operating the TCS, the DT602 does not update:?
   That's weird. When both have the same Loco selected, they should be syncronous.
2. ?but if I pick up the TCS handset after previously using the DT602 (and it's still left plugged in), the DT602 seems to "refresh" and then sends it's update over to the TCS.?
   That is very probably because the DT602 did not release the Loco. The TCS then effectively "steals" the loco. Which means the DT602 does what a LocoNet throttle has yo do: It sends it's last state every 30 seconds or so... :(
   
   

So please try again, but the releasing the Loco on the DT602 before picking it up with the TCS

Case 1. I will check ;)?

Greets,

Karst