Thread: CAN reliability
View Single Post
  #18   Spotlight this post!  
Unread 15-07-2010, 15:56
Radical Pi Radical Pi is offline
Putting the Jumper in the Bumper
AKA: Ian Thompson
FRC #0639 (Code Red Robotics)
Team Role: Programmer
 
Join Date: Jan 2010
Rookie Year: 2010
Location: New York
Posts: 655
Radical Pi has a spectacular aura aboutRadical Pi has a spectacular aura aboutRadical Pi has a spectacular aura about
Re: CAN reliability

Is the problem following the Jag or the ID (as in try switching it so the code sends the rear commands to the front motors)

Are you sending trusted SET messages every 100 ms? If a jag doesn't receive one every 100ms it will disable itself

Quote:
Originally Posted by kamocat View Post
In addition to this information, I have an explicit question:
What is a Token message? I noticed that the token messages (which seem to be the output set, enable, and disable for each mode) require two empty bytes at the beginning of each message. I can't find anything like this in Luminary Micro's CAN Specification. Is this where the "trusted mode" comes in? Does the FRC_BlackJagPlugin put some secret number in these two bytes, which the jaguars must have if they are to accept the message?
Read EricVanWyk's message above your's. I just asked the same thing (It's referred to as trusted mode in the C++ code).
__________________

"To have no errors would be life without meaning. No strugle, no joy"
"A network is only as strong as it's weakest linksys"
Reply With Quote