[Radical Pi]

Some sort of flow limiter on the error messages that can be thrown out by WPILib would be nice. We run with a CAN bus (serial), so this is especially visible for us. There are 2 cases where I've specifically noted the problem.
1) Camera hasn't booted yet. We always wait for the camrea images to start updating on the dashboard before running the robot because the jags intermittently disconnect until the camrea is ready. According to the console there are a ton of E_CONNREFUSED errors being thrown that seem to delay the robot code enough to cause the jags to miss heartbeats and also cause serious control lag.
2) Disconnect enough jags. Basically the same symptoms as the one above. If enough jags lose power (intentionally or unintentionally) the errors thrown to the console from the attempted messages cause the same thing as above.

Also a small CAN library bug: Ever since updating to v87 (or whichever fixed the ID reset) the fwversion shown on the console when the CANJaguar class is initialized is always 0