On 4/21/2025 4:35 PM, thomasmclae via groups.io wrote:
And since you are already in a Digitraxx profile, open the slot monitor to see which slots have which addresses set, and clear out any leftovers.
But DO NOT think "clearing the slots" will solve the problem!!!!
"Clearing the slots" is something that affects the command station, But it almost _never_ does anything to address the problem: the throttle can still attempt to "control" the slot!
The problem is in the throttle! In general, there is _no reliable way_ to tell a LocoNet throttle "not to use" a given slot. (Exception: some newer LocoNet throttles running with newer command stations in certain modes can be "forced" to stop using a slot.)
As I have said previously, the _best way_ to stop using a throttle that is running a loco on a LocoNet-based command station includes these following operations, in sequence:
- "Release" the loco(s) from the throttle.
- Disconnect it from LocoNet (if possible!).
- Turn the throttle "off" (if possible!).
- Remove the batteries and any other source of power (if possible!).
(And, other systems have similar "problems" when multiple throttles "cause problems". Exactly what the problems are, and what the "solutions" are, vary by the type of system. While I am familiar with a couple of non-Digitrax systems, I am NOT a good source for pretty much any system other than Digitrax...)
