开云体育

Mark, The difference with RailCom is that it *is* part of the NMRA specifications, not proprietary, and it may be supported by any manufacturer. As far as I know TCS and MRC (NEXXT) are the only US

I'll try a strategy of changing the staging cassettes to a spur pool. I think it will be an extra burden on the yardmaster, but we'll see. -- Ken NYNH&H, Old Colony Division, Cape Cod Branch

_Or_ if you have: - a LocoNet system, and - Digitrax "Transponding" equipment, and - a mobile decoder that supports Digitrax "Transponding", and - the decoder has its "Transponding" feature enabled,

Heath, As others have indicated, the LokProgrammer is faster because it only works with ESU decoders. Kinda like that question you asked about function labels and BLI. Single manufacturer means

Tony Head Only. This means that only the head of the train can be detected. You must specify a train length and all your blocks must have their lengths specified. It works best if you use speed

Crew: Not reading the entire thread... If sound loading or modification is a needed function the the Lok programmer is a must and independent of your DCC system... Gotca is that Lok software is

Heath, I've been very happy with my TCS LT-50 using RailCom and LCC to interface with it. I can read LokSound decoders in under 5 minutes that way. -Ken Cameron, Member JMRI Dev

Guys, I have also used a SPROG 3 for many years - never let me down. Gerry -- This email has been checked for viruses by Avast antivirus software. www.avast.com

As others have said, the ESU Programmer uses a proprietary closed method to communicate. The fastest route for decoders that support RailCom (includes ESU) via JMRI is a Command Station which

Hi Thank you so much for your help with this. It is very much appreciated. I have just uploaded the latest exhib1.xml file to the same location. Most issues are now solved but there are still a few

But, how often do you need to read all cvs anyway?? I typically do it ONCE per decoder, so the wait isn’t that onerous - even with a Ras Pi. Phil G

Considering those issues, JMRI Warrants don't use train length but does provide for 'Automatic Speed Profiling'. Essentially calculating the time a train should take to traverse a block. If you used

All, I've used a SPROG 3 for several years now as my programming track interface to DecoderPro. Has been very reliable. Regards

Either name will work. I use the user name. Dave Sand

Mast name is system name or user name?

Thank You all for the very informative answers. -- Heath @ Human[c]ity http://www.humancity.org ( http://www.humancity.org/ ) http://www.riversidetransfer.nyc ( http://www.riversidetransfer.nyc/

DEAR STEVE Can you fill me in on the apparently new features in automation - using train length instead of having your last car and if needed your middle car with resistive wheels and using a ghost

The information is in the JMRI Javadoc. For signal masts, it is at https://www.jmri.org/JavaDoc/doc/undefined/jmri/SignalMast.html Here is a Jython fragment. The "if" statement checks to see if the

See JMRI's SignalMastFollower.py script. It uses: self.outSignal.setAspect(self.inSignal.getAspect()) This is what that script needs to do to make one signal mast reflect another signal mast's

Heath, Not a command station, but my PR4 will reliably read all the CV's on a LokSound in about 20-25 minutes. That's not as fast as the LokProgrammer, because as Ross pointed out, the LokProgrammer