¿ªÔÆÌåÓý

Locked Re: Possible roster problem #zimo


 

Bob,

Thank you for the very helpful?information that the JMRI throttle message code doesn't know or care what decoder type is out there.

I thought the EasyDCC Command Station just added those JMRI throttle messages as packets to its queue. But, if what you wrote is true, then the Command Station must convert speed commands into the right packets for the various decoder speed step settings, such as 14 or 28, or 128, and format them for long or short addresses.

Bob Jacobsen: "The code in JMRI that creates the Throttle messages to the EasyDCC command station knows _nothing_ of the decoder type. No matter what decoder type is out there, in JMRI¡¯s roster or not, JMRI will send the same message to the command station given the same address and same speed/function/whatever content.

The problem is somewhere in the EasyDCC command station, EasyDCC throttles, and/or decoders themselves."

And then: "The ones where it seem to work and then stop or are changed are almost certainly due to another throttle sending conflicting commands. Physically disconnect _all_ the EasyDCC throttles, remove the batteries from any that have them, reset (power off/on) the command station, and see if that class of problems remains."

I do understand that, and said so in different wording. I found it most significant simply because it was the first time I'd been able to make any JMRI throttle cause any action by an LE103 decoder.

I do think a packet sniffer is the next step. I need to compare packets to the LE103 decoders from EasyDCC throttles and JMRI throttles. Any differences in packets from my EasyDCC in response to JMRI messages would contain the problem. Once I know what's wrong, I should be able to zero in on the cause and fix. Yet, if packet formatting for both is done by my EasyDCC Command Station, it seems odd those from its throttles get formatted properly, and those from JMRI don't.

I do hope to get this to work. I want to keep my plug in EasyDCC throttles for most walkaround control of the trains. I don't want to replace the Command Station, walkaround throttles, and layout wiring to keep that function, simply to add guest train control via smart phones and JMRI. I'd probably give up JMRI train control first, using it only to replace hardware panels for route control and signalling.

Don Weigt.
Connecticut


Join [email protected] to automatically receive all group messages.