Joined
Last Online
Recent Posts
posted in General Discussion read more

I'd like to start off saying that I don't actually own a CANBus Triple (I actually use my own device), but there aren't really any good, active CANBus forums, so I'm hoping this is an OK place to post this...

Anyway, I'm looking for more info on modern GMLAN vehicles (2010+).

I've done quite a bit of work on my own, but maybe others that have some knowledge that I don't would be willing to share?

Here's a dump of my notes file for my 2011 Camaro, these are all arbIDs from the 29bit CANBus ID on the low speed single wire connection.
0x106 - dash indicators?, 5 bytes:
(bits are left to right)
byte3:
bit0 -
bit1 -
bit2 - left turn indicator, only with bit4 set? seems flaky
bit3 -
bit4 -
bit5 -
bit6 -
bit7 -

byte1:
bit0 - ?
bit1 - headlight dash indicator
bit2 - highbeam dash indicator
bit3 - ?
bit4 - tigger auto headlight on message
bit5 - tigger auto headlight off message
bit6 - fog light dash indicator
bit7 - ?

0x120 - Steering column status?, 8 bytes, byte4+byte5 steering angle
0x121 - Key status, 1 byte (0x00 key off, 0x01 key acc, 0x02 key run)
0x165 - Engine status?, 8 bytes, byte2+byte3 RPM, byte4 oil pressure?, byte5 throttle position
0x170 - Engine status2?, 8 bytes, byte6 oil temp?, byte7 coolant temp
0x200 - Blinkers?, 5 bytes, needs more testing
0x20A - interior lock/lock button status?, 4 bytes, byte1 lock button stat (0x00 unlocked pressed, 0x01 locked pressed)
0x220 - Steering wheel buttons, 1 byte, (vol up = 0x01, vol down = 0x02, up = 0x03, down = 0x04, src= 0x05, pick up = 0x06, hang up = 0x07)
0x325 - windows, 2 bytes, byte0 driver, byte1 passanger, seems to be something with window positioning
0x360 - Odo related?, 5 bytes, overrides odo display on cluster (0x00 0x2c 0x04 0xb8 0x00, with odo at 28008 miles, maybe is coded in kms?)
0x392 - Seat warmer button status, 1 byte, byte0 (0x01 = driver, 0x08 = passanger, 0x09 = both?)
0x40A - fan/climate, 2 bytes, byte1 fan speed (0x00 to 0xE0), doesn't respond to message injection, status only?

OnStar module generated messages (running on bench, format unknown):
Module ID: 0x097
0x102A8097 (0x154) - 00 00 00 20 40 40
0x102AA097 (0x155) - 40 00 00 00 80 00 00 00
0x102AC097 (0x156) - 00 00 1D F4 00 E0 86 A0
0x106E0097 (0x370) - 0E 00
0x10704097 (0x382) - 04 01 00 00
0x10AC0097 (0x560) - 00 00 11 02
0x10ACA097 (0x565) - 00 00 5B 97 98