Thread: Com wire
View Single Post
  #26   Spotlight this post!  
Unread 15-01-2016, 11:22
s1900ahon s1900ahon is offline
Registered User
AKA: Scott McMahon
FRC #2468 (Appreciate)
Team Role: Mentor
 
Join Date: May 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 155
s1900ahon has a brilliant futures1900ahon has a brilliant futures1900ahon has a brilliant futures1900ahon has a brilliant futures1900ahon has a brilliant futures1900ahon has a brilliant futures1900ahon has a brilliant futures1900ahon has a brilliant futures1900ahon has a brilliant futures1900ahon has a brilliant futures1900ahon has a brilliant future
Re: Com wire

Quote:
Originally Posted by timytamy View Post
Do you have a source for this? Particarly one that delves into more of the specifics of the FRC CAN protocol?
You mean other than my faint memories?

You can get all of the published documentation, including the protocol documentation:
1. Goto http://www.ti.com/tool/rdk-bdc24-cd, click the 'Get Software' red button, fill out the export regulatory stuff, and download the last distribution.
2. In the Folder, you should find Software > StellarisWare > docs > SW-RDK-BDC24-UG-xxxx.pdf (where xxxx was the last release #).

Section 4.1 contains the partitioning of the 29-bit MessageID. Note that since the most-significant bits of the message contain Device Type and Manufacturer, CTRE can, and probably has, defined their own API. The APIs in that document were for Jaguar.