开云体育

Over the past few months, quite often, but not every time, I load JMRI, it gives me the PanelPro main menu. I select the panel file I want to load. The panels load.Logix presets any Turnout Logic I have, the commands are sent to the command station and you hear the turnouts switching, then everything stops. I load 2 Py scripts Set all unkown sensors to inactive and set all unknown Turnouts to closed. The sensors on JMRI turn to grey, the Turnouts do not set on the display or operate on the layout.I cannot operate any of the turnouts by clicking on them and the display doesn't change either. I can change them using the DCC master key pad and this is shown in the Loconet monitor. I am also unable to program any locos with error message?306 - timeout talking to command station.? being displayed and when I move locos using the hand throttle, the sensors do not go active.on the panel.

Cures tried and failed
Closing JMRI and restarting.
Turning off Command stations then turning on again.

Cure tried and succeeded
Turning off everything, then rebooting PC and turning on command stations

NOTES ON ERROR
It doesn't happen every time.
It happened before 4.17.8 was released so it isn't something that was introduced there.
I need to start the connection Monitors before loading any panels, then save the logs.

QUESTION
Is it possible to start the monitors automatically when selecting the profile, and if so how?

NOTICED WITH BOTH JMRI 4.16 and 4.17.8
PC running Windows 10

DCC HARDWARE
Digitrax DCS 52 Zephyr Express as a master for Accessories (JMRI Prefix L2) DCC Concepts AD8fx accessory decoders for turnouts
Digitrax DCS 50 Zephyr as a master for sensors and loco programming (JMRI?Prefix L) Digitrax BDL168 and DigiKeijs DR4088LN-CS sensors
Gaugemaster (MRC) Prodigy 2 for loco control (JMRI?Prefix M)

I am not 100% convinced that the problem is JMRI, but might be something that I've done wrong.

Chris,

Do you happen to be interfacing the JMRI computer to the DCS52 via the DCS52 integrated USB interface?

I ask, because several DCS240 users, including myself, have experienced some instability of the DCS240 USB interface. When issues occur, the symptom is often that the USB interface is "locked up", and the obvious workaround is to quit the program, disconnect the DCS240-to-DCS52 USB cable, power-down and power-back-up the DCS240, re-connect the USB cable, then re-start the computer program.

An alternate workaround is to connect the DCS240 to the computer using a separate interface device (PR3/PR4/LocoBuffer/LocoBuffer-USB/etc.). This solution has worked well for me.

Regards,
Billybob

Hi Billybob. Yes I am using the integral USB port on the DCS52, but I when I get this problem, it also affects the DCS 50 which is connected to USB via a PR4, I will reconnect the DCS 52 via loconet and the Pr4 and see what happens, but I am busy over the next day or 2. And yes, your symptoms describe the fault I am having. I wonder if the one locking up affects the others bearing in mind that one of them isn't Digitrax equipment but is linked via the Loconet pin 1.

A couple things to check.

1) On _both_ connection definitions, check the flow control configuration (under advanced settings) If it’s “no flow control” try hardware flow control

2) Try setting them both to “turnout command handling” as “spread”.



3) If that’s still not working, but only after selecting “Spread” and it not fixing it, try setting “Both”

4) And only if that’s not it, try selecting “Spread” again and setting flow control to “None”

Save and restart each time, of course.

Bob

On Dec 20, 2019, at 1:50 PM, SwissChris <chris@...> wrote:

Over the past few months, quite often, but not every time, I load JMRI, it gives me the PanelPro main menu. I select the panel file I want to load. The panels load.Logix presets any Turnout Logic I have, the commands are sent to the command station and you hear the turnouts switching, then everything stops. I load 2 Py scripts Set all unkown sensors to inactive and set all unknown Turnouts to closed. The sensors on JMRI turn to grey, the Turnouts do not set on the display or operate on the layout.I cannot operate any of the turnouts by clicking on them and the display doesn't change either. I can change them using the DCC master key pad and this is shown in the Loconet monitor. I am also unable to program any locos with error message 306 - timeout talking to command station. being displayed and when I move locos using the hand throttle, the sensors do not go active.on the panel.

Cures tried and failed
Closing JMRI and restarting.
Turning off Command stations then turning on again.

Cure tried and succeeded
Turning off everything, then rebooting PC and turning on command stations

NOTES ON ERROR
It doesn't happen every time.
It happened before 4.17.8 was released so it isn't something that was introduced there.
I need to start the connection Monitors before loading any panels, then save the logs.

QUESTION
Is it possible to start the monitors automatically when selecting the profile, and if so how?

NOTICED WITH BOTH JMRI 4.16 and 4.17.8
PC running Windows 10

DCC HARDWARE
Digitrax DCS 52 Zephyr Express as a master for Accessories (JMRI Prefix L2) DCC Concepts AD8fx accessory decoders for turnouts
Digitrax DCS 50 Zephyr as a master for sensors and loco programming (JMRI Prefix L) Digitrax BDL168 and DigiKeijs DR4088LN-CS sensors
Gaugemaster (MRC) Prodigy 2 for loco control (JMRI Prefix M)

I am not 100% convinced that the problem is JMRI, but might be something that I've done wrong.

--
Bob Jacobsen
rgj1927@...