Seems like this is a newly common problem, but I cannot figure out what I'm doing. Help is appreciated!
It is, and I'm afraid it's possibly a hardware problem.
COM3 port is confirmed at 9600 baud in device manager (Windows 10). Confirmed same settings in DecoderPro Preferences.?
The baud rate settings in Device Manager are irrelevant. They are overridden by JMRI.
What matters is that the JMRI baud rate and the NCE USB Jumper settings match.
Service Mode Programmer NCE Is Online. Operations Mode Programmer NCE Is Online.?
That indicates you've got matching baud rates and JMRI has been able to talk to the NCE USB.
Every time I try to communicate with PowerCab from computer/JMRI via the identify function,? I time out and nothing occurs.? It also says "Unknown Programming Mode" at the top of the screen.?
See below. I'll explain the log.
2020-02-06 23:13:29,893 util.Log4JUtil? ? ? ? ? ? ? ? ? ? ? ? INFO? - * JMRI log ** [main]
2020-02-06 23:13:29,901 util.Log4JUtil? ? ? ? ? ? ? ? ? ? ? ? INFO? - This log is appended to file: C:\Users\tyler\JMRI\log\messages.log [main]
2020-02-06 23:13:29,901 util.Log4JUtil? ? ? ? ? ? ? ? ? ? ? ? INFO? - This log is stored in file: C:\Users\tyler\JMRI\log\session.log [main]
2020-02-06 23:13:29,905 apps.AppsBase? ? ? ? ? ? ? ? ? ? ? ? ?INFO? - DecoderPro version 4.18+R37ad3d0 starts under Java 1.8.0_241 on Windows 10 x86 v10.0 at Thu Feb 06 23:13:29 CST 2020 [main]
2020-02-06 23:13:30,041 gui3.Apps3? ? ? ? ? ? ? ? ? ? ? ? ? ? INFO? - Starting with profile My_JMRI_Railroad.3e2624fc [main]
2020-02-06 23:13:30,164 node.NodeIdentity? ? ? ? ? ? ? ? ? ? ?INFO? - Using 97c2d6e1-b0b9-4e73-bad0-4c798080bcc3 as the JMRI storage identity for profile id 3e2624fc [AWT-EventQueue-0]
2020-02-06 23:13:30,257 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "NCE" [main]
2020-02-06 23:13:30,530 usbdriver.UsbDriverAdapter? ? ? ? ? ? INFO? - NCE USB COM3? port opened at 9600 baud [main]
2020-02-06 23:13:30,639 nce.NceConnectionStatus? ? ? ? ? ? ? ?INFO? - NCE EPROM revision = 7.3.0 [AWT-EventQueue-0]
This tells us that JMRI has been able to communicate with the NCE USB and it has reported that it is a V7 and all jumpers are off.
These are correct settings. Do not change them under any circumstances. If you do, you will just make troubleshooting extremely difficult.
2020-02-06 23:15:03,285 nce.NceMessage? ? ? ? ? ? ? ? ? ? ? ? ERROR - attempt to send unsupported binary command KILL_MAIN_CMD to NCE USB [AWT-EventQueue-0]
2020-02-06 23:15:04,765 nce.NceMessage? ? ? ? ? ? ? ? ? ? ? ? ERROR - attempt to send unsupported binary command KILL_MAIN_CMD to NCE USB [AWT-EventQueue-0]
You seem to have tried the Power button. The Power Cab does not support that command so JMRI has blocked it.
2020-02-06 23:15:21,693 jmrix.AbstractMRTrafficController? ? ?WARN? - Timeout on reply to message: A9 00 1D consecutive timeouts = 0 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2020-02-06 23:15:23,951 jmrix.AbstractMRTrafficController? ? ?WARN? - timeout flushes receive buffer: 30 [nce.NceTrafficController Receive thread]
JMRI has now told the NCE USB to pass a "Read CV 29 in Direct Mode" on to the Power Cab and the NCE USB has reported back that the communication with the Power Cab failed.
The communication takes place on wires 3 & 4 of the Cab Bus cable. So check your connectors sockets and cables, try the NCE USB in the other available socket (rear or front right. If you have any spare cables, try swapping out cables.
Let us know what you find.
Dave in Australia
