开云体育

Gilles, Lokprogrammer is its own stand alone programming device and requires the LokProgrammer software to function. It is not capable of interfacing to Decoder Pro. Lots of proprietary dragons

I agree with Don. Although I have figured out the secret by experimentation, the terminology used to delete, save, hide, etc panels is very confusing....especially to someone new to JRMI panels.

Don, When you close a panel with the “Delete” option, the panel will be skipped when you save the panel xml file. If you “Hide” it, it will be included if you save the panel xml file. It

Hello I would like to use decoderPro with the "lokprogrammer" interface of ESU. Is it possible ? I only see "USU ECOS" in the list ... thank you for your reply Gilles

*Merry Christmas?* *everyone..!!*

Andrew, The track colors are actually layout block colors. Their use as track colors was recently replaced by “rail" color which is set by Options >> Track Options >> Set Track Drawing

Cliff Many thanks for the support. All working as required Merry Christmas ? Peter

Hello dev team! i have recently discovered the amazing link between transits and logixs. Being able to set a sensor from a transit action to trigger a logix has fixed up a few bugs for me and added

Hey guys, After reading the suggestions and playing around for a bit with different situations, a very simple yet effective solution came to me. at the specific location, a signal is showing green

Thanks Dan and Paul, I found what I was looking for. Jacques

Tom, Since we just released the 4.14 version, you should try with it. There has been a fair bit of work on that system connection, plus work to prevent the Default = Internal issue. -Ken Cameron,

Ken, Thanks. I had an idea that that was the problem. However, nothing is selectable as Internal under Defaults. Everything defaults to XpressNet (except Service Programmer and Ops Mode Programmer,

Roger, I've been zoomed to 400% to see the 10x10 grid and element placements clearly for part placement. Moving sections has been at about 200%. To me, that's zoomed in, but may be what you mean? At

Jacques, I did not see the answer in Dan's link.? On the "Trains" page, go to "Tools" then select the "Build Report Options" then click the "Text Editor to Preview Build Reports". That will cause the

Tom, Your log shows you opening the serial port ok, but then it doesn't like what is happening with setting up the controls. Please check Edit->Preferences->Defaults, they should not be selecting

See my other post just now about the "FF FF FF FF 0 0 20 0” part of that pattern. It’s normal to see it over and over. Most of the time, JMRI asks the C/MRI node for it’s input status

This is what I’m seeing after rebuild roster. Thanks Russ Austin

This is what I’m seeing after rebuild Russ Austin

Aha! Thanks, I misunderstood. Yes, those have to be right. Perhaps there’s a clue here: That reply pattern is interesting, because the FF FF FF FF part isn’t something that a C/MRI input card

You can find it here: http://jmri.sourceforge.net/help/en/package/jmri/jmrit/operations/Operations.shtml#Trains Dan