|
Re: -44087 and other CAN errors
You can't really remove it... It's an exception in the underlying program (FRC_NetworkCommunications.out). If the connection is not made, then the program times out and it returns an error state. It behaves a lot like UDP in that it ignores packets that didn't go through, difference being of course that it recognizes if a packet was lost. For example, if I try to drive my robot and all my Jaguar's aren't connected, it will stutter. But when I tell the Jaguars to stop, they will stop even though they are receiving errors from the CAN Bus. I'm not too familiar with the CAN Bus so a lot of what I could be saying is wrong.
I would make sure that your Jaguars are plugged in and if they're not, at least make sure they aren't instantiated in your code. I'm not sure how LabVIEW works so I don't know if it's that simple... I come from C/C++ and Java.
Also, I would look at either using PWM for your Jags (ones that don't use any CAN features that the Jaguar offers) or getting a Cross the Road Electronics 2CAN from somewhere. That gives you a ton more bandwidth but they don't sell them anymore unfortunately.
Alex Brinister
|