开云体育

using jmri 5.10 i open panel pro which ,on startup, opens system console, loconet monitor, slot monitor , 4 speedoipmeters,clock,dispatcher, then opens default throttles-10 throttles, 8 set with

Hi Tony, I wrote these notes back when I first needed to do a trace You'll need to change it to jmri.jmrit.dispatcher Debugging Log ------------- Command steps can be output, viewed and copied in

You are asking for my jmri trace log What is that and where do i find it I am familiar only with jmri system console and loconet monitor Tony

I've since had a perusal of the dispatcher java code but couldn't see the same processing. I believe Warrants take a somewhat different approach to running an autotrain. A Warrant script defines the

Put up a copy of your JMRI trace log. There should be references to throttle and speed changes. e.g. this post has an extract of a log and you can see it has speed, throttle and signal interaction

? Dear Steve or anyone else who can help You said “ in the selection box at the bottom, enter jmri.jmrit.dispatcher Select TRACE from the level selector, Click Set new logging level. View

Neil, Read this: https://hostlersinn.blogspot.com/2024/09/loksound-equipped-engine-refuses-to.html There's a list of things to check at the beginning of the post. [email protected]> wrote: --

The fact that this is affecting 2 locomotives indicates that the problem is not anything to do with the decoders in the locomotives, so as Nigel mentioned above, I don't recommend resetting the

Before you even try to go round "resetting" or "replacing every setting", start to analyse why they don't move. Likely reasons are that their is a "consist" involved - either set in the command

I returned to my layout after a lengthy vacation and attempted to Start running a pair of locomotives that I had successfully speed managed to speed match, and found that neither loco would move. The

Nimble, One thing I should have asked was which configuration did you have the Light-It using? My memory seems to say that using it via the signal aspect method is the more reliable way to use it.

Thanks Dave I like your suggestion about using font = background. I've now moved to a 3 state approach where I use unknown as the 'hidden' state. Inactive means available and active is 'in progress.

/g/NCE-DCC -- Peter Ulvestad Linux Mint 22.1, JMRI 5.11.5, Java 21.0.6 JMRI Users Group Moderator ( /g/jmriusers ) JMRI Developers Group Moderator (

Say Ken, I'm not sure what you mean by 'NCE list'? Regards, Nimble

Hi Ken, Thanks for taking the time to reply to my JMRI user group request.? What you say appears to be the case: for when a train moves from one sensor [track block] to the next, often several

The JMRI power button does not know if the track power is on or off. It’s does communicate through the command station to control the power state and receive a confirmation. The actual power on /

Jerry no not on Git or anywhere currently public. If you want to try the current version, I could mail it. It really needs some tidying, and more documentation so people can edit it to suit their

i may very well be. Like i said im not sure whats going on or how exactly how to do this

Are you confusing track power on with starting the WiThrottle server? That’s under Actions. Mick ______________________________________ Mick Moignard mick@... p:+44 7774 652504 The

I can confirm the strange behavior of the MXULF. The first time a CV is read, the previously read value is displayed. Only when a CV is read twice is the correct value displayed. I know that it worked