CANBUS Bridge - A device used to determine the source of message IDs

Ideas and discussion of what to do with the CAN Bus ( i.e. XMDirect, iPod, Carputer, etc... )
Post Reply
User avatar
BiggRanger
How the heck did I end up here?
Posts: 7
Joined: 2020 Feb 03 10:45
Contact:

CANBUS Bridge - A device used to determine the source of message IDs

Post by BiggRanger »

Looking at a bunch of messages on the CANBUS is interesting, but in order to aid in deciphering what the message content is it helps to know what device it broadcasting what message ID.

I created a project I call the CANBUS Bridge using an Arduino Uno, and 2 CANBUS boards. This device gets placed between a module and the rest of the vehicle bus, and it logs the message IDs coming into each CAN board and rebroadcasts them to the other CAN board. Granted this is messy since you need access to the device and have to cut the CAN wires in order to insert this device into it, but sometimes sacrifices need to be made.

My sacrifice - a 2008 Durango: dashboard removed, all interior wiring accessible, almost everything still works and it still drives!
1230191158e.jpg
I've posted the project on my GitHub at: https://github.com/BiggRanger/CANBUS-Bridge
The important information is in the PDF (how to build and use it), and the Arduino source is there too.
Like my last project the CAN library needs to be modified to support the 83.333Kbps speed of the CAN-IHS in older Chrysler vehicles (notes are in the source code).
CanBusBridge.jpg
Now for the interesting stuff from the CAN Interior:
Device - Message IDs
Cluster = 0x013, 0x014, 0x02E, 0x0D0, 0x11D, 0x150, 0x159, 0x1C8, 0x210, 0x340, 0x35E, 0x3A0, 0x414
SKREEM = 0x012, 0x1B6, 0x1E0, 0x1E2, 0x1F6, 0x3EC, 0x400
TIPM = 0x000, 0x402 (these are known, there are more below)
Window Module Driver = 0x0BA, 0x408
Window Module Passenger = 0x1B8, 0x40A
HVAC = 0x3EC, 0x411
Radio = 0x0F0, 0x18C, 0x190, 0x326, 0x3A5, 0x3AE, 0x3D0, 0x416
Airbag = 0x008, 0x41C
ECM via TIPM = 0x01B

These are the rest of the message IDs I have not documented the source for, they come from the TIPM but originate either from the TIPM, or some other device on the CAN-C network (since the TIPM acts as a CAN gateway).

CAN-IHS messages from the TIPM and CAN-C network:
0x002, 0x003, 0x006, 0x010, 0x011, 0x015 (maybe from ECU), 0x02C, 0x110, 0x18E, 0x19F, 0x1A5, 0x1A7, 0x1AD, 0x1AE, 0x1AF, 0x1B0, 0x1B2, 0x1B5, 0x1C0, 0x1D0, 0x1D2, 0x265, 0x370, 0x3F8

Notes about the project:
1) The supported CAN speeds are 80, 83.333, 125, 500Kbps.
2) Only standard CAN messages are supported, not extended messages.
Last edited by BiggRanger on 2020 Feb 12 21:51, edited 4 times in total.

uski
How the heck did I end up here?
Posts: 2
Joined: 2020 Feb 08 03:01

Re: CANBUS Bridge - Used to determine the source of message IDs

Post by uski »

That's very cool !
Do not hesitate to publicly document your findings, I just got started in this domain and for some reason it seems people jealously keep the CAN IDs and other info to themselves. I have no idea why. I will also publish all I find !

User avatar
BiggRanger
How the heck did I end up here?
Posts: 7
Joined: 2020 Feb 03 10:45
Contact:

Re: CANBUS Bridge - Used to determine the source of message IDs

Post by BiggRanger »

I'll be putting all my findings here:
https://github.com/BiggRanger/CANBUS-Ve ... ngineering
My work has slowed down a lot since everything is covered in snow right now, but as soon as it warms up again I'll be back at it.

Post Reply