This is the console-out from NetBeans containing our entire boot-up process with our CANTimeoutException. We were able to flash our Jaguars with the latest firmware using the 2CAN web interface, which makes us think that the CAN network is correctly set up. After the code deployment is complete, the 2CAN is flashing green fast, which indicates that the cRIO is communicating with the 2CAN. You can see from the console-out, the 2CAN plugin is loading properly. If we remove the 2CAN from the Ethernet network, we get an UncleanStatusException.
Our question is: what else can we do to troubleshoot the CANTimeoutException?
Are you using the latest plugin and latest 2CAN firmware from the CTRE web site? Are you certain you are addressing the Jaguars with the correct device numbers?
hi, I’m one of the mentors for this team. First, thanks for the response. I’m fairly confident that we are using the most up to date plugin for the cRio, and we are using firmware version 2.0 for the 2CAN. I’ll get back with you on the exact version of the plugin on the cRio.
As for the node id’s, yes. I’m fairly confident that we are addressing the correct node id on the CAN network. We recently used the 2CAN’s web interface to flash all of our Jaguars, and in doing this, we confirmed the node id of the Jaguar on our bus. We have removed all but two Jaguars from the CAN network and can confirm we see both of these node ids on the network through the 2CAN web interface.
We ran the exact same code again, this time switching out our Version 2.0 2CAN with a Version 1.6 Firmware 2CAN. There were no other changes to wiring, code, network configuration, etc. We only changed the 2CAN Firmware. Whereas with Firmware 2.0, we had CANTimeoutExceptions, there were no such exceptions with Firmware 1.6. Our cRIO version is 25 and all Jaguars are updated to version 2.1.