Good news!
I reset the zephyr, nope.
I changed to have the script try to aquire address 4.? Still errored, so, it¡¯s not the loco.
On a chance, I changed the setThrottle second parameter to False.
It worked!? The script acquired the address and the loco took off.? Yeah.
I think that second parameter is false, for two digit address, and true for four digit address.
Now, I¡¯m running.
I¡¯ll start another thread with my next problem, since it¡¯s not about the throttle, anymore.
On Friday, November 15, 2019, billybob experimenter <
jawhugrps@...> wrote:
Kirk,
"Slot 6" might be assigned to loco address 6.? Or loco address 0.? Or loco address 3. or loco addres 2154, or any other loco address between 0 and something over 9900 (but not quite to 9999, with Digitrax systems).? "Slot 6" is NOT NECESSARILY associated with "DCC address 6".? In fact, it typically will not be.
Exact slot assignments depends entirely upon the sequence in which locos are acquired and dispatched/dropped, and the way that various throttles attempt to re-acquire locos when they become powered-up and/or attached to a live LocoNet.
It is generally only possible to know what address is associated with "Slot 6" when some LocoNet agent "queries" the command station for "slot 6" information.? JMRI can perform that function, as part of the LocoNet "Slot Monitor".? See .?
To interpret that tool's results when you use the tool, you need to reference the "slot number" that you see in LocoNet Monitor in the left-most "Slot" column of the tool's table - in your case, look for the row for "Slot" number 6.? Then look at that row's "Address" column to determine the address assigned to the slot.? Once you know that address, try to dial that address on a live throttle.? You will likely get the "Steal" message (or some LED color indication on those throttles which cannot display alphanumeric information).
In the image at the top of the above-referenced web page, slot 6 just so happens to be assigned to address 6.? (This is not typically what users see, unless they just happen to acquire locos of particular numbers in a particular order from a command station with a particularly-clean slot table.)?
This assignment of address 6 to slot 6 just happens to be coincidental, and this coincidence is likely because the JMRI developer who created the image did not use much imagination (or realism!) when "acquiring" locomotives before creating the image...? Perhaps that image needs to be updated to show a more-typical situation where random addresses were acquired, rather than sequential addresses.
Regards,
Billybob
