CANJaguar errors on driver station after deploying code

[Tyler Scheuble]

Have you checked to make sure that you can see that CANJaguar using the roboRIO webdashboard?

I am having problems finding out where to get that. Does this screenshot make sense for you?
http://puu.sh/eEcav/f85f6c8588.png

[Joe Ross]

If the jaguars were properly connected, they would show up under CAN, like attached.

[RufflesRidge]

Originally Posted by Tyler Scheuble

I am having problems finding out where to get that. Does this screenshot make sense for you?
http://puu.sh/eEcav/f85f6c8588.png

It does and it indicates that your roboRIO sees no devices on the CAN bus (or you took it shortly after boot-up and you need to refresh the page).

Check your CAN wiring (I would try taking the Jags out of the chain and wiring from roboRIO to PCM if used) to PDP and see if you can get at least one device to show up, then start adding Jags to see where the cabling issue is.

[Tyler Scheuble]

Ok we are in the process of rewiring the jags now. Thank you!

[Tyler Scheuble]

We have tested, found and then replaced a wire that was stopping CAN as a whole, and now we are able to connect to the PCM and PDP, but the jags are still not being recognized. Here is a screenshot of our CAN connections:
http://puu.sh/eEuXx/a318618a2d.png
We aren't sure if this is a firmware problem but we installed the version from the update suite. The version number is 2.1.0f3.

[blueForest]

my team is also experiencing this issue but for us it has been appearing at seemingly random times, and then the issue disappears.
Currently the we have two versions of the code, on works one throws CANMessageNotFound

However i cannot figure out what the difference is that is causing the error, as they should both be doing effectively the same thing

Anyway, our code is at https://github.com/cougarTech2228/Dr...team2228/robot
(the working code that is, the error inducing version is in the master branch)
(warning the code may have changed since this post)