The simple node ident info gets garbled. Bunch of substrings appear twice.
A bunch of ArrayIndexOutOfBounds exceptions are logged to stderr from JMRI
When trying to go to the CDI load, the load fails after the first datagram with a permanent error on the far side.
The same setup works perfectly fine if the JMRI hub is not within the same process:
1) Start JMRI with a CAn simulator
2) start OpenLCB Hub
3) start another JMRI with Gridconnect CAN via network to localhost:12021
4) open the network tree/CDI tool in the second JMRI
5) start the external node process connecting to the first JMRI.
balazsracz
commented
7 years ago
Steps to repro:
1) start JMRI with a CAN simulator connection 2) OpenLCB->Start Hub 3) Open the network tree window. Observe only the JMRI node showing up there. 4) connect an external node (example: https://github.com/bakerstu/openmrn/tree/master/applications/io_board/targets/linux.x86 ) to localhost:12021
A couple of strange things happen:
The same setup works perfectly fine if the JMRI hub is not within the same process: 1) Start JMRI with a CAn simulator 2) start OpenLCB Hub 3) start another JMRI with Gridconnect CAN via network to localhost:12021 4) open the network tree/CDI tool in the second JMRI 5) start the external node process connecting to the first JMRI.