开云体育

After reviewing the JMRI code, this makes sense to me. Each different mechanism for "resetting slots" has different effects on JMRI and the command station. - JMRI's Slot Monitor "Clear all Non-InUse

Dave – yes, the errors are the same if the adapter is plugged into the serial port on the command station as when it’s not (but still plugged into the USB port on the computer), which are both the

Dave -- I removed all the JMRI files and folders but the JMRI folders in the Users folder, rebooted the computer, reinstalled JMRI v.4.17.4, rebooted again, and still got the same thing. -- Jeff

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

Correction I use classes jmri.jmrit.automat.Siglet jmri.jmrit.automat.AbstractAutomaton -- Petr ?ídlo Czech Republic https://sites.google.com/site/sidloweb/

?SD Czechoslovakia signal definition is OK too https://www.jmri.org/xml/signals/CSD-1962-zakladni/appearance-entry.xml -- Petr ?ídlo Czech Republic https://sites.google.com/site/sidloweb/

I am working on a project how to adapt the JMRI Entry-Exit tool to an Extry-Exit interlocking system used by the Czechoslovak State Railways. Most work is done in Jython. The project is not ready yet.

Steve, I can’t help with decoder specific issues but I also run macOS, although Mojave not High Sierra. From the Apple menu, select System Preferences >> Security & Privacy, General tab. Unlock if

Hi Steve, I honestly don't know whether this is the cause of the more recent JMRI not working for you, but you missed something in the release notes. The ones after 4.12 contain this little nugget:

I am new to this group and have joined because I am stumped trying to install a newer version of DecoderPro. I have been a model railroader for almost 60 years but fairly new to DCC about 4 years with

Jacques wrote: "Before last week we were using a DCS 200 and we always clear the slots with JMRI alone no interaction with the command station. It should be the same with the DCS 240 because the

All, There are _several different_ methods available to clear LocoNet "slots". Some are JMRI specific. Some are defined in command station documentation. Some are provided by other software packages.

Before last week we were using a DCS 200 and we always clear the slots with JMRI alone no interaction with the command station. It should be the same with the DCS 240 because the option is present in

I just had a look at the definitions shipped and the docs for updating them. This is beyond my skill with XML to mess around with. I don't suppose that a tool exists to simplify this process a bit?

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

I now have a printout of the JMRI to EasyDCC commands for two locos. One with a year old basic NCE decoder using long address 349 works. One with a Lenz LE103 using long address 1477 does not. I will

Unfortunately, my earlier upload had the wrong checksum in the LocoNet message. It seems that I was not careful enough. A [corrected

Paul, Each movement of a car (spot) or (pull) takes one "move". If you want to allow both cars to be replaced with others, that will require 4 moves. Pulling one car and spotting another takes 2

I can confirm that this JMRI web site issue is resolved as of very late US Eastern Standard time Friday nite. Regards, Billybob

Marc, Are you using Slot Monitor's "clear all slots" pushbutton, or are you modifying command station OpSw36 in your test? I ask because the Slot Monitor "clear all slots" pushbutton _does not_ fiddle