AIM data via CAN-bus (to dashes, dataloggers)
Order [CAN_Dash] with AIM-AIM option:
35 bytes (0..34) are sent in 5 CAN-frames, CAN-ID 0x6F0..0x6F4, see
Some notable channels (See 1.2.38 on GenBoard/UnderDevelopment/FirmwareChanges )
- channels OILPRESSURE (9), OILTEMP (13), FUELTEMP (109), FUELPRESSURE (21), ERRORS (125)
- predefined calibrations and channel inputs for AIM pressure and temperature channels
- ERRORS (highbyte) has function activation states: ALS, Launch, Shiftcut, n2o, Traction Control, Injector stage 2, Idle, Ego
- ERRORS (lowbyte) has error states: o2 not ready, trigger error state, config slot active, baro problem, engine knocking, warning light state
It is practical to send data in this format to configurable dataloggers, instruments, dash.
- For example ERRORS high-byte bit6 is Launch activation
Message format (see AIM pdf for more info) (note: units might need review, especially temperature)
- CAN ID, Byte, (Bits), Gain/unit, Data type
- 6F0, 0, (0:16), 1, RPM
- 6F0, 2, (0:16), 1, WHEELSPEED
- 6F0, 4, (0:16), 1, OILPRESSURE
- 6F0, 6, (0:16), 1, OILTEMP
- 6F1, 0, (0:16), 1, WATERTEMP
- 6F1, 2, (0:16), 1, FUELPRESSURE
- 6F1, 4, (0:16), 1, BATTERYVOLTAGE
- 6F1, 6, (0:16), 1, THROTTLEANGLE
- 6F2, 0, (0:16), 1, MANIFOLDPRESS
- 6F2, 2, (0:16), 1, AIRCHARGETEMP
- 6F2, 4, (0:16), 1, EXHAUSTTEMP
- 6F2, 6, (0:16), 1, LAMBDASENSOR
- 6F3, 0, (0:16), 1, FUELTEMP
- 6F3, 2, (0:16), 1, GEAR
- 6F3, 4, (0:16), 1, ERRORS
- 6F3, 6, (0:16), 1, constant 0 ?
- 6F4, 0, (0:16), 1, 0xFB, 0xFA
- 6F4, 2, (0:8), 1, checksum
Note : VEMS also supports AIM via serial, via 1st or 2nd RS232 port; it has similar datarate as via CAN, and practical to broadcast to an arbitrary number of receivers, see:
- BroadcastDatastreamAim
- BroadcastDatastreamAimSecondSerial
- See AimCanBusSniffing especially if sniffing, (or possibly broken receiver that does NOT acknowledge messages)