开云体育

Hello all. I am relatively new to JMRI. I have used it to program locomotive decoders and am now looking to install and program signals at a quad interlocking. Hardware: Digitrax DB150 command

I would have to look at the protocol to see if that is right, but the way it actually is interpreted is “RailCom tags A and B are in positions X and X+1 of ZRD6AA’s tag array”. The hardware

He said he designs and manufactures for MRC Corp. that’s what he has told me and I have a bad mrc sound decoder and it looks just like them. But I didn’t compare components but same blob on the

Steve, Agreed that there are other options (I did say "such as") but my reply is targeted at NCE users and in that case the Power Cab hardware can also be used in slave mode as a throttle with the

pcgumshoe, The NCE Power Cab doesn't have the CVs>256 issue, so is your ideal workaround for programming these decoders in Program Track mode. NCE command stations always report success for any CV

Looked at the Raspberry pi JMRI with that script of mine trying to get that script to run.? Got a system error saying it didnt like line 23 of InitLayout.py.? Reads "minPPwindow() By the way, I do

The Digitrax PR4 also works well with these (and most/all other) decoders and is a more economical alternative. Steve "Breezlys"

Rich, To do the "reset" I've always unplugged *everything* that could supply power to the PR4: The USB cable, the external power, and the LocoNet if it's supplying railsync. I also had a chance to

61 and 62, he had me try both number in CV 57 and CV 58.

Thanks Dave for that explanation. I placed my loco on my portable programming track that has an NCE USB connection and a PowerCab.? I was able to program the function correctly, so I thought, I

Jim, ManufacturerID is MRC. (Model Rectifier Corporation) Since you get multiple matches for version 0 it indicates that either: - there is no MRC decoder with a VersionID of 0. - there are multiple

Values of 253 for CV57 and 254 for CV58 appear to be default values from Soundtraxx. What did "Tech" say they should be? -- Peter Ulvestad JMRI Users Group Moderator - http://www.jmri.org (

pcgumshoe, The problem is caused by a Power Pro firmware issue that affects program track operations with both JMRI and the NCE throttle. If you, by any means, attempt to write a value to any CV>256

My problem just got bigger. I put a new Soundtraxx Econami Steam xxxPNEM sound decoder in one of my locos. DecoderPro didn't find the brand or model in CV 8 and 7. It reported both contained zeros.

Bob, Found the source of my problem.? I had changed scripts to match what I was using in my Raspberry JMRI Pi.? I normally used "InitLayout.py" by Bill Dickerson's Cascade Western railroad.? This

JMRI versions are the CURRENT version and 4.17 test versions were tried.

I'm using windows 10, Decoder pro works fine with NCE and LOCONet via PR3.? I can control locomotives, program them and do just about everything. My problem is these new 21PNEM decoders, I've tried

Bob, Took out the two scripts that clear turnouts and clears unknown sensors.? Did that on the Raspberry Pi.? All that did was leave all signals red. Trying to find my loconet checker.? It's a

I looked at my NCE program and it said manufacturer 143 and decoder version 0 I don’t know if this makes a difference either.?

Are you running any scripts at startup? It sounds like something it deliberately going through and setting those signals. Now we just have to figure out what. Two strong candidates are a script