开云体育

Further to Mick's point number 4: " If you get a 302 programmer busy error that won't go away (the DCS240 programmer is prone to crashing), just power off the DCS240, wait 15 seconds and power on

While the NMRA standards define the bit mappings of CVs 21 & 22, various manufacturers have modified and extended these, so you need to rely on the Consist pane for each roster entry. The overall

Hi All, Just need a reminder for CV setting for intermediate units within a consist. I know I have it somewhere, just can't find it! Many thanks, Mike.

Having had a lot of trouble myself with a DCS240, and long chains of discussions here and with Digitrax, I'd suggest to you from bitter experience: 1. Ensure that the DCS240 is at the latest firmware

Hi Bob Some more info about what I've done using current 4.9.2: After removing the previous decoderindex.xml from my user's folder (created with 4.9.1 when I updated the Zimo V36 Plus profile), and

Bob: I don't see where I have made any script references to jmridefaults.py, but renaming jmri_bindings.py to that name resolved my issue. Thank you (again). I had to change some script references to

You need to go to Preferences->Connections and select a valid serial port from those available. The valid name for a SPROG connection will be something like cu.usbmodemxxxx (not the tty.usbmodemxxxx).

Bob, I installed 4.9.2 again. Then I checked for the decoderindex.xml file and I did have that file under My_JMRI_Railroad. I moved it out of there then launched DecoderPro. I put it through lots of

Might be more than one problem. Could you try the #1765 (or later) installer from http://jmri.tagadab.com/jenkins/job/Development/job/Packages/ please? It’s building now, should be done in about 20

Will look tomorrow when I get to club Sent from Yahoo Mail on Android

User with problems with a DCS240 and a locobuffer. I would like to know what the version number of the loco buffer is.. Its the first number when you select Loconet>LoconetStats. Walt

If you have scripts referring to “jmridefaults.py”, please replace that with a reference to “jmri_bindings.py”. Or you could copy the “jmri_bindings.py” file to be named

My programing track is less than 3ft away. We upgrade from a dcs 200. But we also have 5 sections each control 30 ft at max. My DCS240 is the main and controls antennas, programing track, and a 2

I would like to add some interesting observations here, I also hooked up a new dcs240 from a dcs 100. Initially I had a 30 ft run from the command station on 12 gauge running to a dcc specialties

I'm running 4.8..,

I get that error when the PR3 is in the wrong mode on my home set up with a DCS200. Our club uses the 240 just for running the layout so we haven't run in to this with it. So not sure how to change

Did you do the update v.3 on the DCs240? [Non-text portions of this message have been removed]

Will need to get back with you, but I installed newest version that was not a test version, I think 4.8 production release Sent from Yahoo Mail on Android On Mon, Aug 14, 2017 at 9:28 PM, DAVID KLEMM

Upgraded from 4.9.1 to 4.9.2 and now it does not like this line from jmridefaults.py and stops dead before showing any of my Layout Editor Panels. Any thoughts? 2017-08-14 21:18:35,692

What version of JMRI are you running? The 240 was addressed around 4.7.2. David Klemm Sent from my iPhone 7 Plus ________________________________ Sent: Monday, August 14, 2017 7:12:32 PM To: