Chrysler CAN-C Listings

[nemiro]

I have previously worked quite a bit on a project to decode a lot of IDs on a Chrysler CAN-B bus, to interface RER and RHR radios into cars without a CAN Bus. That was successful, so time to kick it up a notch!

About to perform an engine swap on a Chrysler Crossfire. Crossfire uses exclusively a CAN-C bus at 500kbps. As it uses a lot of the same modules as 2005+ Chryslers, I have a hunch that a lot of what it speaks is standard for 300, Charger, Challenger, and others.

At CANHack, we seem to focus on the CAN-B bus a lot, as this deals with the things we humans interface with (infotainment, windows, lights, etc). How about the engine control side of things, all of which resides on CAN-C? I have begun data captures, and I also have a hunch that a lot of that is industry standardized, as your typical OBDII reader will easily pick up the data off that bus for data streaming and diagnostics. I am looking to marry modules in from another vehicle, and also work with RealDash for an aftermarket type instrument cluster.

Surely someone here has some of the CAN-C bus decoded already? I will gladly post up what I have, as I get it. Anyone else willing to share?

[CIRC1977]

The crossfire is a totally different animal compared to the lx platforms. A lot of can c messages are industry standard when it comes to obd2 information but other stuff is proprietary . Crossfire is all Mercedes and I think uses can c for module to module communication but uses sci single wire to most modules for scan tool communication.

[nemiro]

I completely understand what you are saying. However, much of the basic architecture, and even the modules, such as the TCM and shifter module, carried into the LX cars. I have purchased a few LX platform modules, and they are being shipped, now. I will be comparing them to the Crossfire's (and even swapping some into that car) for testing.

[nemiro]

Adding these for reference. One is the full, open CAN-C (and only) bus in a 2004 Chrysler crossfire. All of the traffic. The others are captures on the bench of an EGS52 from a Crossfire, and and EGS53 TCM from a 2007 Dodge Charger 5.7L. I have captures of the EGS53 "talking" to an HP Tuners MPVI2, as well, but unsure that I will post that.

[BiggRanger]

I've been working out the CAN-C stuff from Chrysler vehicles and posting the data here:
https://github.com/BiggRanger/CANBUS-Ve ... ngineering
My work involves the following vehicles:
2006 Jeep Grand Cherokee
2008 Dodge Durango
2010 Jeep Wrangler

[nemiro]

Nice! Thank you! I will post up more as I learn them. I have other threads here with quite a bit of CAN-B info from my previous projects, but CAN-C is a different animal.

[nemiro]

Hmmm, your file, CAN-C JK WK DN.ods, doesn't seem to be there. Can you take a look?

[BiggRanger]

Sorry, and thanks for the heads up! I can't believe I did that...
It's there now. If you discover anything or have anything cool to add, let me know and I'll update my docs.

[nemiro]

Awesome, thanks! And, I will do!

[nemiro]

Did some work this evening with the Chrysler Crossfire instrument cluster. I used a 2004 MY unit. It uses the same connectors as 2005+, but appears to be pinned out differently. Unsure if the messages are any different between model years. Anyway, the cluster outputs two IDs: 0x0408, and 0x0410. On the bench, 0x0410 stays mostly static with indicators of ignition switch status. I'll document those later. For now, ID 0x0408 is more interesting. I have much more to do, but as of now, here's what I do know:

Fuel level, D0 (Byte 1). It moves between $00 for empty, $39 for full tank. $FF for open circuit. Low fuel lamp lights up at $0A.

D1 (Byte 2), it is a status register:
Bit
0
1
2
3
4
5
6
7 Left door ajar


D3 (4th byte), Dash Illumination level, ranging from $12 for the lowest setting to $64 for the highest.


I'll add more as I figure out what does what. Triggering the discrete wires seem to only turn indicator lamps on and off, without any effect on CAN messages.

[super-ss]

Great job.

Did you use an ihs can or C-lan?

[nemiro]

This is CAN-C, not the IHS/CAN-B bus. I have many of the CAN-B messages listed in other threads. I'll add more to the listings for CAN-C, soon.