CAN Bus Integration: Difference between revisions
No edit summary |
|||
| Line 10: | Line 10: | ||
==Controlling a CAN enabled Device== | ==Controlling a CAN enabled Device== | ||
AIM Mychron 3 Dash | |||
The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Example of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below: | |||
Packet 401h: RPM, Speed, Gear blink control, Gear | |||
TODO | |||
Packet 402h: Temperature/Pressure fields (bottom left of display) | |||
TODO | |||
Packet 404h: Control for fields displayed on bottom left of display | |||
TODO | |||
Packet 405h: Shift LEDs, Alarm LEDs | |||
TODO | |||
Packet 406h: RPM range for the digital RPM readout | |||
TODO | |||
Packet 408h: Timing | |||
TODO | |||
Revision as of 21:43, 8 January 2015
Introduction
Researching CAN Bus protocol
Reverse Engineering
Reading a CAN message
Mapping to a Virtual Channel
Controlling a CAN enabled Device
AIM Mychron 3 Dash
The following information is a sum up of reverse engineering findings documented here: [1]. Example of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below:
Packet 401h: RPM, Speed, Gear blink control, Gear
TODO
Packet 402h: Temperature/Pressure fields (bottom left of display)
TODO
Packet 404h: Control for fields displayed on bottom left of display
TODO
Packet 405h: Shift LEDs, Alarm LEDs
TODO
Packet 406h: RPM range for the digital RPM readout
TODO
Packet 408h: Timing
TODO
