JMRI

Request for help. 

We are having a problem with the JMRI throttle not controlling any DCC engine. Our DCC system is an EasyDCC from CVP and is working fine with no problem. JMRI appears to run fine on the computer. JMRI will turn the track power on and off and with the command monitor window open we see commands being sent, so we know the serial cable is connected. But the JMRI throttle we can't control an engine, throttle or function,even though we can see commands being sent in the command monitor. 

 Can anyone shed light on the situation?

jrbernier's picture

WiThrottle

  Is this the imbedded throttle in Decoder Pro, or are you starting the WiThrottle Server amd running from an app like Engine Driver on a cell phone?

Jim

Modeling The Milwaukee Road in SW Wisconsin

Either but focused on the embedded throttle.

We discovered the problem with a WiThrottle but the embedded throttle also did not work. We focused on the embedded throttle to remove the wireless variable. We still can't get the embedded throttle to work. 

pierre52's picture

One possible option

Hi

If you have a look at your Preferences  (edit menu) and check

"Connections"

     "System Connection"

and make sure that you have the right connection (sorry but don't know what your PC to Loconet interface is)

I had the same problem and had forgotten that I had set the connection to "Loconet Simulator"  rather than "Loconet Locobuffer USB".  I use RR Cirkits Loco Buffer.

 

 

 

Peter 

The Redwood Sub

jrbernier's picture

JMRI Yahoo User Group?

  It sounds like you have covered the connection bases as you can power on/off track power.  

Jim

Modeling The Milwaukee Road in SW Wisconsin

geoffb's picture

Similar Symptoms

Hi,

I had a similar situation with similar symptoms when there was a major Decoder mismatch between what the JMRI cab was setup for and the actual decoder in the loco. I had 2 instances: 1. A completely different decoder and decoder manufacturer selected. and 2. I had a 24 step decoder not a 128 step decoder.

Make sure the entire configuration is correct.

"Hope this helps. Have fun!  smiley
Best regards,
Geoff Bunza

Problem solved

thanks all for your help. 

It turned out that the serial port on the cvp easy DCC system was disabled.  I don't understand why this allowed us to turn the track power on and off from the jmri program, but it would not allow us to control trains via jmri. Once the port was enabled everything was good to go. 

Art

According to CVP, EasdyDCC

According to the CVP RS-232 protocol manual, EasdyDCC doesn't actually disable the port, but just ignores commands that are Q-D-S type. I'm not explaining what those commands are, but suffice to say that the power commands are NOT in any of those types.....

Therefore, the power commands will always be responded to.

 


>> Posts index


Journals/Blogs

Recent Blog posts: