开云体育

Yes, known issue. I believe it is being addressed. - Nigel

Hi, Just upgraded JMRI to 4.5.4 with my old xp computer with a USB Sprog, never had a problem until now, I only use DecoderPro on this machine but since the upgrade I cannot use the built in

Dale, That's a different situation than using the JMRIClient with the SimpleServer. In the JMRIClient/SimpleServer case, only one computer is actually connected to the layout and that connection is

I just loaded latest version on to my MAC. No other version was installed. I have the latest version of JAVA installed. Nothing loads. Any suggestions?

Hi Mike, Is your issue cars on interchange tracks that don't belong there, or cars on interchange tracks that don't move? More below. ---In jmriusers@..., <mcerpsligo@...> wrote

Sadly doing this is not easy. Each item needs to rotate 180 degrees. Then you need to translate every x and y top to bottom and left to right. I recall doing this sort of thing once but that was many

Thank you all for your information and suggestions. I worked with the system today and just used the NCE D405SR as the roster listed decoder and ignored the sound decoder completely. I found that the

Hi Iain As long as you have your layout in a layout editor panel you just need to add the signals to anchor points and auto-discover the logic. As long as there is a path between signals on the

I periodically run 2 layout attached computers with the exact same PanelPro panels and logic simultaneously without seeing any problems. I have the same Layout Editor panel open on both and can

So the layout owner has decided to move the main JMRI display screen to the opposite side of the room. This means that the layout editor panel is now upside down and back to front (ie: 180

Robin, I confirmed what you see on macOS as well and created Issue #2058 https://github.com/JMRI/JMRI/issues/2058 for it on GitHub. Will look into it and hope we can fix this soon. Egbert

/On 10/9/2016 10:50 AM, nsseeker@... [jmriusers] wrote:// / It's definitely not a Phoenix as the decoder would be close to the same size as the engine, from that era (grin). -- Jon

David, There were many early decoders that either had CVs 7 & 8 as "writeable" or had the values inverted thus trying to ID the with DecoderPro is unreliable. I don't believe a "DA120" specific

Your "fudge" is as good a method as any. You could add comments in the free-text field to remind you (and others) of the fudge. An alternative fudge is to use the generic "NMRA" decoder type. If you

I am trying to program an old decoder on DecoderPro V4.4. I have an Atlas N scale GP40-2 with a "DA120" decoder. This was pre-installed WAAAAYYY back in 1997 or so. DecoderPro doesn't have it

Ken, jmriusers@...> wrote: In the case of my friend's layout, it is becsuse the signals are being run by CATS not JMRI directly. At the time we put this together, JMRI did not have the

Unfortunately the Phoenix line is 'minimal' DCC. They understand taking a long or short address and a few adjustments so you can make it match your throttle speed. So while running it can follow the

Using your info as well as Jay's, I managed to find a string of accessory addresses not used ( or not a multiple of 256) on my layout and everything now works fine. Plus I have an added toggle switch

Steve, The Phoenix line of decoders is primarily targeted at the large scale locos. We use a lot of them in RC G gauge and riding scale locos. They use a dedicated USB connection for configuring

I have a friend with three TT's on his layout, or should I say a friend with three highly modified Lazy-Susans on his layout, manually operated of course. John