开云体育

Am 20.09.2019 um 01:35 schrieb conrad: Conrad, I have only made small changes in example.vsd. The reason for this was an issue on Github, created by a VSD user, see

Thomas, I have done the tests you recommended. On the programming track, ID reads 1477, CV19 reads 0, CV29 reads 34 Read Basic Sheet shows: Long (two byte) address Active Address = 1477 Primary

Marc Easydcc will not let you put "66" in the number AND in the Advance consist. He is using a Lenz LE 103 - they do not like 128 peed steps - they are better with 28 or even 14. Now, WiFi to JMRI to

Thanks for the responses, Dave and Dave! I'm tied up for the weekend, but will try your suggestions Monday. -- Jeff

Thanks Dave. I will check when I get home. I forgot to mention all other turnouts work correctly. It is just the new ones added that do not.

Does anyone use Jython scripts with the JythonAutomation and JythonSiglet classes? I am looking for sample scripts used with those classes as documented for automation (kind of) in

Just found the updated VSD example file on github (3 days old). All four locos run (3 diesel, 1 steam).? all sounds ?same? as previous release.? diesels good, steam not so good (choppy chuff

I found a different way to view the signal system mast appearance files that will properly view the files and display all of the information even though the files don't "correctly" reference the JMRI

Jeff, Since you are using Windows, a JMRI upgrade may leave some old stuff behind depending on how old the previous version was. I always do a clean install. This involves using the Control Panel to

Jeff, Do you still get the same errors if you aren't trying the loopback mode but just have it: 1) Unplugged from the Power Pro end. or 2) Plugged into the Power Pro. Unlikely.

I’m not sure if it was the same set of errors but yes, I got several errors about three times before I saved the last one. I did upgrade Java yesterday, too. Could that be related? -- Jeff Sent:

Jeff, It looks more like a transient error in the JMRI or the Pure Java Comm library we use. Or possibly a poor contact between pins 2 & 3. Is it reproducible every time you start JMRI? Dave in

Mike wrote: "From what I can see in the reference below, and the links on its page, I believe that semaphores are not covered in any of the existing tables; that they are set up only for lights. Am I

Klaus, "I did a test on my layout today. HALF_SPEED works, but there is one thing to keep in mind. If the assigned function key is pressed while driving, the loco decoder changes its status

From what I can see in the reference below, and the links on its page, I believe that semaphores are not covered in any of the existing tables; that they are set up only for lights. Am I correct?

Jacques, Per the DCS240 manual section 5.1, changing OpSw 36 (or 37, 39, or 40) _requires_ interaction with the command station's front-panel switches. JMRI cannot do anything via a LocoNet message to

Hal, Ok - with a better understanding of what you are trying to do, here's a better answer. Assuming that you are working with a pre-defined JMRI "signal system", simply look at the JMRI web site page

I did a test on my layout today. HALF_SPEED works, but there is one thing to keep in mind. If the assigned function key is pressed while driving, the loco decoder changes its status immediately. VSD,

Thanks, Everyone! Here’s where I am: I am careful to plug the USB end of the adapter into the same USB port on my computer. All Default radio buttons are set to “NCE” Upgraded to 4.17.4. No

Thanks both Good to see that the problem is being progressed, and that I can continue testing using internal turnouts. I will monitor 7431 to see the progress. Bill