开云体育

Mike, Various things don't add up here. We need to get to the bottom of this one. 1) We need you to go to the Help->Locations menu item, click in the folders display area, Select All (ctrl-A), Copy

Thanks Marc, I thought it was something unique to NCE. Nick "I'm not a failure. I started at the bottom and I found it easily attainable. Life is too short to set unattainable goals" - Nick Kulp

It's implied from the locobuffer that you're using a digitrax command station. If thats wrong, or things are more complicated, please list that info, and the version of JMRI you're using. The easiest

Changing names, sometimes requires saving and restarting so everything picks up the name change. Many things get the change notice and work right away, but some, view like the name gets passed down a

Marc, I’d expected the same – up and running in a few minutes. Several hours later I’ve experienced ‘no joy:’ Ross Sent: Thursday, August 1, 2019 5:21 PM To: [email protected] Subject: Re:

Frank, Never attempt to guess the model of a modern ESU decoder. You must always use New Loco->Read Type from Decoder. This will uniquely identify any current ESU decoder. Never with an ESU decoder.

Marc, Thank you for checking. This may verify that we are not getting communication between the LocoBuffer and computer. I will re-check all of the cables. I can also run a ‘known-good’ jumper

I installed the drivers from the RR-CirKits web site. Dick Bronson confirmed they were correct from the data in the port properties. Ross Sent: Thursday, August 1, 2019 4:53 PM To: [email protected]

Does?multi decoder control allow you to program multiple decoder locos?? If so how do I use it? Thanks. Jim K

GitHub issue #7272 created.

Nigel, Thank you for the input. The COM ports seem to be correctly established, 1 for each LocoBuffer. This was verified on Device Manager both before and after re-installing the drivers. Dick Bronson

Marc, Thank you for the hint. I will check next time I’m at the club. Doesn’t explain why it works when the USB cable is unplugged from 1 computer and plugged into the other. Ross Sent: Thursday,

Phil, I have created a simple test case which replicates your issue. I have a pretty good idea of what is happening but I don’t have a solution yet. In the meantime, create a GitHub issue. Dave Sand

Typo – S/B 4.15.9 Sent: Thursday, August 1, 2019 4:31 PM To: [email protected] Subject: Re: [jmriusers] Help getting JMRI working on a new WIN10 computer Is that JMRI version 4.17.9 a typo ?

I'm assuming that you know to look at the Device Manager on the computer for the LocoBuffer connecting, and establishing a COM port ? If that's not appearing to work, then.... Are the ports on the

Marc, All 8 boxes are blank. Ross Sent: Thursday, August 1, 2019 4:29 PM To: [email protected] Subject: Re: [jmriusers] Help getting JMRI working on a new WIN10 computer

Phil, Now that I understand that you were using one of the panel editors, what you describe seems to make sense, but only almost. Certainly it is common for the panel editors to each make any name

You also need to do Read Type from Decoder, as new Loks from atlas, scale trains, etc are Loksound V5 decoders, not Selects. Add in Old V4.0 and Essential Sound Units, all of which are different, and

I've hit a road block establishing communication between JMRI and a Digitrax DCS100 using a LocoBuffer-USB interface. This is a new installation in a computer replacing a recently failed unit. After

There is a new board called a "decoder buddy" from NixTrains. Almost straight drop in for OEM QSI boards. Gives you a 21 pin motherboard to install any 21-pin decoder (I prefer Loksound) Thomas