Fiat 500 Forum banner

500e CAN bus decoding

21009 Views 44 Replies 17 Participants Last post by  Yayitazale
Hey people,

I've been poking around the 500e CAN bus in my spare time, trying to decipher messages for custom behavior, data collection (like performance and battery health over time), and remote control. I believe I've identified 30+ messages, but want to confirm before sharing widely and going further down this rabbit hole. Any chance someone is willing to collect and share a minute or two of logs? You can PM me with an attachment if you aren't comfortable sharing publicly. Here is what would be helpful:

No adapter:
  • Connect the logger directly to the ODB-II port (I believe this is CAN-C?)
  • 500k speed
  • Make sure car is "ready"
  • Take note of any metrics you have access to: % charge and GOM from cluster. Pack voltage, Soc, SoH-R, SoH-C, ODO, 12v from AlfaOBD or Multiecuscan would be extra helpful.
Yellow adapter (requires a physical Alfa/Fiat yellow adapter or direct wire like it does):
  • Connect the logger to OBD-II through a yellow adapter (I think this is CAN-B?)
  • 50k speed
  • Make sure car is "ready"
  • Perform some actions inside the cabin (change gear, turn climate on/off, turn various lights on/off, press SWC buttons, open doors)
  • Write down which actions you did
Any format is fine. Here is a snippet (of pressing vol- on steering wheel) if you need an example of what I am looking for:
Code:
Timestamp;Type;ID;Data
24034253896;1;6284000;0000000000000000
24034253896;1;6284000;4000000000000000
24034253897;1;6284000;0000000000000000
Thanks for any help/consideration. Also, if you've already done some of this work I'd be happy to help or compare notes. I'd love to get this all documented for tinkerers, apps, and integrations.
See less See more
  • Like
Reactions: 1
1 - 1 of 45 Posts
Hey people,

I've been poking around the 500e CAN bus in my spare time, trying to decipher messages for custom behavior, data collection (like performance and battery health over time), and remote control. I believe I've identified 30+ messages, but want to confirm before sharing widely and going further down this rabbit hole. Any chance someone is willing to collect and share a minute or two of logs? You can PM me with an attachment if you aren't comfortable sharing publicly. Here is what would be helpful:

No adapter:
  • Connect the logger directly to the ODB-II port (I believe this is CAN-C?)
  • 500k speed
  • Make sure car is "ready"
  • Take note of any metrics you have access to: % charge and GOM from cluster. Pack voltage, Soc, SoH-R, SoH-C, ODO, 12v from AlfaOBD or Multiecuscan would be extra helpful.
Yellow adapter (requires a physical Alfa/Fiat yellow adapter or direct wire like it does):
  • Connect the logger to OBD-II through a yellow adapter (I think this is CAN-B?)
  • 50k speed
  • Make sure car is "ready"
  • Perform some actions inside the cabin (change gear, turn climate on/off, turn various lights on/off, press SWC buttons, open doors)
  • Write down which actions you did
Any format is fine. Here is a snippet (of pressing vol- on steering wheel) if you need an example of what I am looking for:
Code:
Timestamp;Type;ID;Data
24034253896;1;6284000;0000000000000000
24034253896;1;6284000;4000000000000000
24034253897;1;6284000;0000000000000000
Thanks for any help/consideration. Also, if you've already done some of this work I'd be happy to help or compare notes. I'd love to get this all documented for tinkerers, apps, and integrations.
Which OBD do you recommend for a 2017 500e?
1 - 1 of 45 Posts
Top