Torgrim,
On 26 Dec 2019, at 9:31 AM, Torgrim Gjelsvik via Groups.Io <torgrimg@...> wrote:
I don't know the interfaces her, between JMRI, SPROG driver and SPROG hardware.
But I guess the SPROG driver is a generic ftdi driver,
That depends on your SPROG and Operating System types. Some use FTDI, my SPROG IIv3 reports as a generic modem-class device and in the case of macOS at least, uses inbuilt Apple drivers. But your problem isn't in that area.
and what I see in the SPROG console is what JMRI sends to the USB port.
I'd also be looking at the JMRI system console for any error messages.
I pulled out the scope and probed the DCC signal - the hardware keeps the frequency going in both cases.
The messages sent from JMRI are inserted into the idle stream.
In the erroneous state, the only thing that is sent is the signal decoder packets when I change a signal mast.
When pushing a turnout, *nothing* comes in the SPROG console, meaning JMRI sends nothing?
Even if the turnout changes on screen.
It sounds like JMRI thinks the SPROG is not in command station mode, or some other issue like inconsistent states.
There are some different code paths for Signal commands sent to SPROG versus Turnout Commands sent to SPROG.
In the functioning state, JMRI keeps continuously sending "decoder idle packets", (FF 00 FF), mixed with signal and turnout packets.
That's correct.
Check the JMRI system console for any error messages.
Dave in Australia
