Since the v89 update for the Jaguars I noticed that on NetConsole all of the jags get a comms error on init and fwversion is always 0. BDC-Comm shows the correct version numbers. Operationally they are perfectly fine as far as I can tell, but I noticed on the inspection checklist posted in General that we will be required to prove firmware version, and in the (hopefully unlikely) event that we can’t plug the bus into our laptop and have to show it through the cRIO I don’t want to have to figure out this problem.