Does anyone actually have this working with DCC++???? The reason I ask is that I've run into a most unusual problem trying out ROC Rail......I've posted this to the ROC Rail forum, but no responses yet..... Motor Driver Issues I have a completely functional DCC++ system using basic, standard parts that works normally when connected to JMRI, connected using USB. BUT, when I connect to ROCRail, and attempt to power on the system, ONLY 1 of the LEDs on the MD board illuminates. Again, with JMRI, all 4 LEDs illuminate, showing that the DCC signal is being generated. Obviously, the DCC++ system is operational when using JMRI, but NOT when using ROCRail....... Absolutely nothing is different between switch between systems, and obviously I am actually selecting the DCC++ system, as it responds to the power on/off commands, but with these strange results....... I don't understand how issuing the <1> command internally to the DCC++ system can cause these results. HELP!!!! I'm completely stumped at this point.
Somebody should have an idea about what could possibly cause this......it's like there's a command being issued that's causing DCC++ to not function.
I don't know ROCRail at all, and I can't think of any commands that could be sent to the BS that would cause only one LED to light, so all I can suggest is that maybe the baud rate is wrong on ROCRail, and the Basestation is being over loaded with gibberish? Jim
Not likely, simply because it does respond correctly to the <1> or <0> commands to turn track power on and off, just that the DCC signal apparently isn't being generated correctly. The RocRail server program reports that it doesn't like something in the initialization sequence, but there's no clue what that is. As far as I know, except for initialization of the USB interface, nothing should be sent to the DCC++ system.
