开云体育

Marc, CV1 and CV 66 are both short addresses. With that configuration, the only way to make the loco move is to send short address 66 speed packets. Having a non-zero CV19 overrides anything in CVs 1,

This is thought to be an unwanted side-effect of migrating the JMRI site to https: https://github.com/JMRI/website/issues/329 Bob -- Bob Jacobsen rgj1927@...

Conrad, I think that the loco decoder and VSD are in sync when the HALF_SPEED key is switched and the loco is not running. Prerequisite: the basic acceleration and deceleration times of the loco

Lately there is a strange message in the *Apperance table* for example https://www.jmri.org/xml/signals/AAR-1946/appearance-SL-3-high.xml *Error: This appearance does not appear in the aspect table.

PS: also a huge acceleration momentum value combined with a lack of patience can make it seem like a loco does nothing. Yes, the words 'clutching' and 'straws' may well spring to mind.

Hi Don, Have you checked the values of the speed table and of Vstart, Vmid and Vmax? If those were inadvertently all zero... Not likely, I'll readily admit, but as you're running out of likely things

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