开云体育

One user (!) reported success using the boards with JMRI. But that was a long time ago, and the details are fuzzy. Perhaps he’s still here and can comment? If you’ve got the boards, it might be

Steve, I will have to let other CATS and JMRI experts take on the question of using the SE8c in "fourth aspect is flashing red" mode instead of "fourth aspect is dark" mode. I have almost no

Steve, Be aware that some LocoNet-connected devices get their Switch commands from the DCC track signal even if they have Loconet connected. This can cause difficulty if you go the "Bushby bit" route.

Billybob, Thank you for your response. Here are the answers to your questions: 1. I'm running JMRI 4.6 (Production version). I've not yet updated to 4.8. 2. I'm currently using the DCS210 command

Thanks Dick, Tried again and it let me in but did warn me that it was new programme, less than a week old. Thanks for the assurance John

John, This happens at every new release. Some 'Antivirus' software simply checks to see if other people have already downloaded the program before. If it is something new then it blocks it. Obviously

Hi, I attempted to update my 4.6 version of DecoderPro for Windows to the current production version of 4.8. However, on clicking on download to update my 4.6 version I was blocked with a message that

Yes. the 2 Radio buttons for the programmer were set to internal. It confused me. It saw my command station fine. Thanks!! Jay

Ah, the sweet taste of success.=I moved the jmri.conf file to my directory "C:\Users\ModelTrainNut\JMRI" and added JUST ?default_options="-J-Djogamp.gluegen.UseTempJarCache=false".=And

Klaus, That is now working for me. I got it into the jmri.conf but for my Eclipse sessions, I found I had to add it as a 'VM Options' in the configuration for my run/debug configurations. However, I

Bruce: One question, if I may. Have you tested JMRI with jmri.conf line default_options="-J-Djogamp.gluegen.UseTempJarCache=false" too? This bypasses the jogamp_exe_tst* process, which I think causes

Hi, I have been running JMRI 4.6 with my CMRI system for some time without issue. I'm using a USB - Serial converter with a Windows 7 machine. I recently tried updating to one of the 4.7 test releases

As Bob said, it sounds like you have selected Simulator as the connection type. Most Simulator connections deliberately return a value of 123 for every CV read, as a result the DCC address will show

Bob, Loaded v4.9.1 this morning on two machines - my train room desk top (Win10, 1.3gh, 4gb ram) programmed and read a bunch of locos with the Sprog 3 - no problems. The second machine - Acer laptop

Any program running on a PC can be slowed down by memory constraints, too much activity, or disk space issues. Also, connections to other devices can make it seem extremely slow. I would advise to not

Steve, Which version of JMRI are you running? What command station model are you using? Are you using "flashing" aspects on SE8c signals? LocoNet can become VERY busy when flashing aspects are used,

The production version was frozen for testing, so some updates didn’t make it into JMRI 4.8. They’re in the JMRI 4.9.1 release that came out shortly after. Re-installing those decoder files should

Open Preferences, select “Defaults”, and check that your hardware connection has been selected for the programmer (and in most cases, everything else too). It sounds like you’ve got the

Any frog power connection only involves 3 wires. The 3 connections usually come free with your switch motor. Andy Reichert Sent from my cost effective $15 keyboard.

This new release seems to have populated every field with 132 in the programming screen. I opened up an existing engine when this happened. The DCC Address was messed up too. Jay