开云体育

Background: We have a large O Scale club using NCE for our DCC. We have several people now who use their phone or tablet to run trains using the JMRI WiThrottle feature. Some use the Apple WiThrottle

Just to be clear. If you have NCE Power Pro system, and want to program Tsunami or any other decoder with CV numbers above 255 (Except ESU Loksound) you will need do one of the following: 1. Switch

Tim, I see two addresses being operated there, 837 and 2203, were those both being operated by Engine Driver? At the end of the log, the last operation request for each locomotive was properly

Ooops. Your question made me realize that I was having this conversation after apparently being misled by someone (maybe the engineers) into believing this is a problem. It appears now that I am

You will need to be more specific. What error are you getting? Paul

That is a difference in interpretation of the XPressNet protocol, and has been a long standing issue when mixing hardware from Lenz and Roco. We have always used the Lenz interpretation of the

Paul as requested. Tim XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 70 and direction Forward In 128 speed step mode. XPressNet Tunnel Reply: EF C3 45 04

Trying out this nightly build version, I get a problem opening my panel. I'm using the Z21 for loco control and point control, plus MERG Cbus to control more points. Using the production version,

What you do internal to your node is separate from the protocol on the line. For example, you could keep the current status in memory, then compare it when something new is written over the line. That

Regarding car locations, I use Excel (older version, 2000) to import the car roster export. Before pre-building any trains for an Ops Session, I do this (Export) then create a spreadsheet with two

Ok, so the question we need to answer with that problem is where are we loosing the connection. It could be between the PC and the Z21, but it could also be between the PC and Engine Driver. One thing

Phil Is this the build report that works, or the one that fails? Dan

Sudden memory: Go to Preferences->Defaults and check that NCE is selected for everything, rather than Internal. -- Dave in Australia

Norman, Instead of sending the file to the printer, try the "Microsoft XPS Document Writer" and send the output to me to review. You might have a printer that doesn't quite work right with JMRI. Dan

The "nce.NceConnectionStatus INFO - NCE EPROM revision = 7.3.0" in the log below indicates your drivers, jumpers, baud rate and JMRI settings are correct and that JMRI can communicate with your NCE

Geoff CMRI communication is well defined in this document: https://www.nmra.org/sites/default/files/standards/sandrp/Other_Specifications/lcs-9.10.1_cmrinet_v1.1.pdf There are four special characters

Due to a firmware problem, the NCE Power Pro is incapable of correctly programming CVs>256 in Program Track mode (a CV<256 will be reprogrammed instead of the correct one). However you can program

Update, tried WiThrottle (Android), starts loco going, but loses it, no control at all. Tim

OK thanks Paul. Throttle works, as I would expect it too. I am unable to test any programming as I don't use the Z21 for that purpose. Now onto the next but minor problem. I have done a workaround,

First apologies for my tirade about the new version. I could have been more tactful. As for 4.7.6, after about a day of testing and tries, I have given up on it, and gone back to 4.6.0, and all is