The NCE Cab bus is monitored by setting DIP Switch 4 on before power up. The output isn't terribly informative as it consists mainly of cab pings from the command station, LCD display quadrant updates and the occasional key press. I just tried with JMRI V4.13.5 and it's been spewing out data like "80 81 82 95 96 AA" for many minutes now with no signs of a crash.
The NCE Control bus (a low current version of the DCC track bus - the booster input signal) or even jumpers to the track via pins 2 & 3 of the small 4-way Jack is monitored by setting DIP Switch 4 off before power up. You can then use the radio buttons to change the display format between decoded user-friendly output (Verbose) to various hex formats of the actual DCC packets. You need to use the "Show xx" radio buttons to show various packet types otherwise display will be blank. The "+ on" checkbox suppresses repeated packets, replacing them with "+" symbols. The "Info" button interrupts normal communication to ask the analyser for a comfort command help screen (JMRI is using those commands when you click on radio buttons).
Your BSOD has to be a USB-Serial cable/driver issue. What brand are you using?
Make sure you try JMRI 4.13.5 - just in case... I avoid V4.12 as it has many issues.
--
Dave in Australia
toggle quoted message
Show quoted text
On 27 Nov 2018, at 8:55 AM, James Muthig <jmuthig3@...> wrote:
Hi Dave and Jim A., thank you for your replies. I am using JMRI version 4.12. I'm not using any app to capture data, just using the NCE Packet Analyser's serial monitor in JMRI to view the output of the CabBus. After 10 or so seconds the blue screen of death.... I've never tried to monitor to the control bus. Any advice for doing this?
