2015 chrysler 200

2015 chrysler 200 CANbus ID’s

Steering wheel buttons

Left button

Right button

Down button

Up button

Ok button

Behind steering wheel up left side

Behind steering wheel down left side

Behind steering wheel center button left side

Behind steering wheel up right side && volume up

Behind steering wheel down right side && volume down

Behind steering wheel center button right side



Vin number

190# [5]






Nice work!

By the way, are these codes the same as for the 2014 Charger (from your earlier post)?
I have not tried yet to find the codes on my 2015 RAM.

It would be nice to know if Chrysler FCA is using the same codes in all their vehicles…

these are CAN IHS
I manged to setup a bench test and have got a lot of info from just an instrument cluster and shifter from a 2015 charger.
If you look inside my code you will see some”steering wheel buttons” from a 2016 challenger

I just ordered a carloop + photon to probe my 2018 Ram 2500 CAN bus. I’m hoping to control it over MQTT from home home automation system when it’s parked in the driveway. I always forget to lock my doors and having it auto lock at whatever trigger I need (night time, idle time, etc) is the next improvement in my overall security system.

I’ll keep reading posts here. Hopefully I can glean all the little bits together to learn how to properly sniff the CAN bus and transmit the codes back to the truck. I’ll report back if the codes are similar for my 2500.

Carloop has been the best tool I’ve found. It can do what the $3k plus big boy toys can do. Not affiliated with them in any way just a huge fan of the product! All though a sponsorship would be nice :blush::raised_hands:t4:

I take it that I can’t get to the CAN-IHS bus via the OBDII connector? Seems like I need a can-hitch with a splice/y-cable to the internal radio/info CAN bus. Oh well. I needed a new OBDII reader since some s***head jacked it from my truck when I forgot to lock it overnight.

On my charger and maybe your ram the canIHS is on the obdii port, it’s pins 3&11 125k
The reason the carloop isn’t going work on it cause it’s wires for pins 6&14 500k
You can technically solder a canhitch to those pins, on the carloop they are not used and use a few jumper wires to attach it to the photon/electron.
I havnt tried it but that was my initial thought on trying to get “dual canbus” working.
I’ve been side tracked lately and have been doing a lot of ECU hacking and man the carloop is capable!!
On GM and Chrysler.

Thanks for that. I just ran across some data for RAM trucks and CAN bus codes. Last page is the one.

That’s a good find right there. Has a bunch of info.

I was slightly surprised to find that. However it makes sense as those 3/4, 1 ton trucks are often heavily modified after the factory to make construction trucks, EMS vehicles, etc. Making this data semi public helps those 3rd party “upfitter” companies out.

@dubb45 & @hartmms,

Good finds for discovering all that. It is going to be useful when I get around to working on my 2015 RAM 1500.
I found the same type of information easily for my previous F250 diesel exactly because of the upfitter market.
However, before getting to the RAM, I need to finish CarloopRetro to do K-Line (instead of CANbus) for a 2004 Impreza.

Important Note: The Photon is not able to do “dual CANbus”. If I remember, the STM processor pins for the other CAN interfaces were used for some other purpose. However, the Electron should be capable of “dual CANbus” in theory since another CAN interface is available on the C4 & C5 pins. I am not aware of anyone actually using the C4/C5 CAN interface, so someone needs to confirm that it does work.

Another way to go about it is with a Photon & Carloop on the OBD2 port and another Photon & CanHitch on the CAN-IHS bus. You would not need a second Carloop to do this.

I know “anything is possible” but was any thought given to a hardware mux on the carloop that would allow a photon to switch between the different CANbus signal pins on different OBDII pins? If so, I’m curious what the tradeoffs were to not enable it.

BTW - I’m not complaining. I got my carloop coming Saturday and am excited to test it out.


You suggestion of a mux could be done, but there are a lot of trade-offs. I do not work for Carloop, so the actual rationale may be a bit different than my thoughts.

To start, here in North America, the only legally required CANbus is the one that Carloop interfaces with. To implement only that bus means a simple device that is easy to build, small enough to fit in the package it does, and would meet the majority of use cases.

To add a second CANbus for the Photon, it means adding a mux, an additional CAN transceiver and all the circuitry to support that. That could likely double the physical size of the Carloop and it would no longer fit directly on the OBD2 port. That would also make it a lot more expensive. Then, there is the question of how many vehicle models have a second CANbus on that port; it would not be that many. For some models of cars, it would then be necessary to be able to disable the second CANbus at high impedance since the pins are used for other purposes that are not compatible, making things further complicated.

Once that hardware layer is in place, you could still only communicate with single CANbus at a time. That means that you have to miss out completely on what is happening on the CANbus that you are not connected to at that time. That might be seen as a big limitation.

Here is what is usually, but not always, available on the OBD2 port at this Wikipedia page:

As you can see, it gets hard to do a design that covers all the possibilities. You quickly getting into customizing things for a particular vehicle.

My opinion is that Carloop did a very good job of providing the right functionality for an almost-consumer level product.

Don’t forget that the design is completely open-source, so it is possible to customize both the hardware and firmware to fit your particular use case.