开云体育

Thanks Pete, This will save me lots of complexity and time. I hadn't thought about limiting the E and L shipments at staging. Good tip. I'm really liking schedules the more I get them deployed. I'll

Pawel, Use the LocoNet Monitor and turn on timestamps to measure the delay or absence of delay. I would consider it a fault if Dispatcher was somehow bypassing the delay. But a trace with those

Hey Charlie, Q1)? This is accurate, and I have never found the need to filter other than through the schedule.? If you prevent E and L from leaving staging, you need not exclude those from any spur

Obviously I'm new to these Groups too :)? The reply above was to Nags :)

I'm sure it's a very good suggestion, unfortunately I'm new to the JMRI and I don't understand much of what you wrote... :(

Thanks a lot for the suggestion of putting the delay in the connection settings - it worked great for routes: I removed the additional delay in the route configuration and routes work well now using

Does anyone know to get the throttle function buttons and add to their functionality, in jython? I can get all the buttons of all opened windows, but adding the .actionPerformed listener to them

Just putting it out there, how about LogixNG with Execute Delayed to throw the subsequent turnouts. This would run shortly after the first turnout changes, and progressively for each turnout. -- H.O.

I would agree with Steve and others, odds of the decoders being bad are extremely low. Having been around DCC for 25 years I've never seen or heard of a case where a decoder was truly failed by faulty

When I do a decoder index rebuild, I see the following in the console 19:34:22,124 ri.jmrit.decoderdefn.DecoderIndexFile INFO? - update decoder index [AWT-EventQueue-0] Warning:

David /KarenWoomer writes in part: " Then it goes on the rails, and operates just fine with the new programming.? But THE NEXT DAY, when I try to run the loco, it will not move.? Often, the lights

I have checked speed steps on all the non-working decoders, they are all set t0 28/128. My JMRI version is 5.4+R9005ecb4ac.

Over time I have accumulated a lot of spurs with “accept only” load restrictions. All spurs on the layout have schedules for receiving and shipping car/load combos. The long list of accepted

There is a connection specific delay you can add, but that would be for all turnout commands. It's worth a try, it is an additional configuration value in the connection. There may be other ways

Dispatcher simply sends the turnout commands, it is up to the turnout handler for a given interface? to know how to pace them. For example? digitrax configurations have a setting Turnout Command

I use three Modellbau Union new turnout decoders on my layout. Each controls eight turnouts (Kato Unitrack, with no feedback). They work great when turnouts are changed individually, but when more are

Ian, I think you need to prove the USB device from the DCS52. One usual method is to: 1. Open a command window on the Linux system 2. Go to the devices directory, "cd /dev" will get you

Are you referring to different versions of JMRI?? I am still trying to learn JMRI and not too familiar with the different releases.? If I decide to install an older version, how do ili get rid of

I have a switching layout, and rarely consist.? But I have checked CV19 on all these decoders, it has consistently remained at 0 and was not changed.? Decoders have all been reset multiple times

I have selected DCS52 USB Interface Serial Port:- ttyACM0 - this is the only choice I am offered Command Station Type - DCS52 (Zephyr Express) ________________________________ Sent: 30 November 2024