Marc,
On 17 Dec 2019, at 3:27 PM, forfoum@... wrote:
Dave,
Does this not mean the driver is ok and loaded : Last 5 lines of his log
458429 jmrix.AbstractMRTrafficController WARN - timeout flushes receive buffer: [Receive]
458440 nce.NceConnectionStatus INFO - NCE EPROM revision = 7.3.0 [AWT-EventQueue-0]
Good spotting. I probably didn't scroll to the end of the log after seeing so many timeouts.
However, the fact that it took so long to reasons is concerning. It should have responded immediately.
Possible causes:
- Driver issues.
- He's using JMRI V3.4, which was using the old RXTX libraries rather than PureJavaComm.
- Bad 12V Power connection between the NCE USB and the Power Cab Panel (via Cab Bus wires 2 & 5). The 12V is needed for the microprocessor, which responds to the AA commands. (The opto-isolated USB part is powered by 5V from the computer and is obviously talking to some extent.)
675301 jmrix.AbstractMRTrafficController WARN - Timeout on reply to message: A1 00 08 consecutive timeouts = 0 [Transmit]
677374 jmrix.AbstractMRTrafficController WARN - timeout flushes receive buffer: 30 [Receive]
712425 jmrit.AbstractIdentify WARN - Stopping due to error: Timeout talking to command station (306) [AWT-EventQueue-0]
Things have gone bad when attempting to read CV8. Possible causes:
- Dodgy 12 Power connection (as above).
- Bad data connection between the NCE USB and the Power Cab (via Cab Bus wires 3 & 4).
- Other more obscure issues that have various troubleshooting paths (one of which is observing the two LEDs on the NCE USB and reporting exactly what happens when - normal operation is both flickering briefly as data is sent/received. Some more details in my previous email.
Dave in Australia
