Skip to main content

OBD support for Peugeot Ion / Mitsubishi i-miev / Citroën C-Zero

🚧 THIS IS A TICKET MIGRATED FROM UPVOTY. The original ticket and comments will be available for a limited time over at:
https://abrp.upvoty.com/b/obd-requests/peugeot-ion-mitsubishi-i-miev-citroen-c-zero/
———————————————————————————
CAN data details here :
https://myimiev.com/forum/viewtopic.php?t=763
Or
https://prius-touring-club.com/forum/threads/c0-ion-exploitation-can-bus.3830/

Thank you !

What type of vehicle connection is this?
Status: Awaiting Clarification3 comments

Log in to comment and vote

Comments3

  • Katya S.

    Team•

    Jan 27, 2025

    Pinned

    Hi,

    We need the OBD PID commands and how to interpret the returned data. Since this is not easily available for most vehicles there is not possibility for us to provide a time estimate.

    You can check our telemetry API for relevant properties:
    documenter.getpostman.com/view/7396339/SWTK5a8w

    Also, you can check our (partially outdated) OBD repository to see what other cars report:
    https://www.github.com/iternio/ev-obd-pids

    If you find that an existing vehicle profile reads data correctly, please let us know, but please DO NOT keep using the incorrect vehicle model with live data.

  • Jan Alexander

    •

    Oct 16

    I did some work to push this forward. What I’ve found out is that there is a set of well-known and documented PIDs that are being sent by on-board devices and you just have to listen to using the OBD adapter. This is for example how “canIon” is gathering its data. AFAIK, passively listening to messages is not supported by ABRP, correct?

    However, there are other PIDs that you can actively query to get a similar set of data. These are not documented as well as the other PIDs, but there is at least some basic data available like SoC. SoH and HVDC battery voltage.

    I’ve tried to verify these using the PID testing tool in ABRP (on iOS). Init commands seem to be correct, I’m even seeing the correct response data in the “raw OBD response” and can decode it manually. However, ABRP is not decoding them and just saying “got response: null”, without any further error details.

    Example: PID 2101 returns several messages

    762 10 2E 61 01 9E A0 01 7D
    762 21 08 01 7C 00 0C 81 51
    762 22 04 4E 14 01 5D 01 5C
    …

    SoC is at data item 0, formula is A / 2 - 5, therefore 0×9E / 2 - 5 = 74 (% SoC), which matches the displayed bars in the car and what other apps like “car scanner” are reading.

    Any idea why ABRP is not reading the value? Any place where I can look to gather more error details?

  • ABRP User #2700903

    •

    May 20

    •

    Merged request

    •

    1 vote

    Peugeot iOn / Mitsubishi i-MiEV / Citroën C-Zero — Direct OBD Bluetooth Live Data support (iOS)

    Hi ABRP team,

    I am trying to connect my Peugeot iOn to ABRP for live battery data on iOS using a Vgate iCar Pro 2S (Bluetooth LE) dongle.

    I have two specific issues:

    1. OBD option not selectable: In the ABRP iOS app under Live Data settings, the direct Bluetooth OBD option is greyed out / not available for the Peugeot iOn vehicle profile.

    2. Enode flow is blocked: When using the Enode integration path, the process asks for a 4-digit "Personal PIN" from the myPeugeot app — which this vehicle/account does not provide, making the cloud connection impossible.

    My request:

    • Please add or enable direct Bluetooth OBD support for the Peugeot iOn / Mitsubishi i-MiEV / Citroën C-Zero platform on iOS.

    • These three cars share the same platform and OBD protocol, so a fix would benefit all three models.

    • The Vgate iCar Pro 2S is confirmed working and broadcasting correctly — the limitation appears to be on the ABRP app side.

    Thank you for considering this!

    Andreas Lindenberg