CAN Documentation Specification
Ross Cooney <[email protected]>
| Newsgroups | gmane.comp.hardware.bus.can |
|---|---|
| Message-ID | <CAJntQsye7SqQO1vOMsEXHB8=37R-gvGA8gLfdOttXv1MbPnjUg@mail.gmail.com> |
Hi List, I work for Smith Electric Vehicles and I am new to this list. Smith Electric Vehicles deal with a number of suppliers and internal development teams to design the components used in our vehicles. These components use various technologies to communicate with each other, the most prevalent of which is a CAN. Whilst documenting and tracking issues across these suppliers, we found that there was often confusion and miscommunication surrounding the documentation of the use of CAN. Every supplier had a different documentation format for describing the data structures and locations of the variables, and this began to make interoperability between various systems a more difficult task than it needed to be. We decided to design our own CAN documentation specification. We have uploaded this to our team blog and are interested in your comments. This is here: http://blog.sevtelem.com/2012/11/can-doc-spec/ Thanks, -- Ross Cooney -- Archives and useful links: http://groups.yahoo.com/group/CANbus Subscribe and unsubscribe at www.vector.com/canlist/ Report any problems to <[email protected]>