Skip to main content

Incorrect SoC (Fixed at 3%) for New Citroën ë-C3 / ë-C3 Aircross (2024+ CC21 Platform)

Bug Reports

Hi ABRP Team,

I am writing to report a compatibility issue with the live data integration for the new Citroën ë-C3 Aircross (2024+ model, CC21 platform).

While using a Vgate iCar Pro 2S (Bluetooth LE) adapter, the SoC (State of Charge) remains stuck at 3% in the ABRP app, even though the adapter is successfully connected. It appears that the default OBDII queries used by the current vehicle profile are not returning correct values for this new Stellantis platform.

Using Car Scanner Pro, I have confirmed that the following PIDs provide accurate live data for this specific vehicle model. I request these be integrated into the official ABRP profile:

  1. Display SoC (Matching Dashboard):

Mode/PID: 222002

Header (CAN ID): 7E0

Formula: A/2.55

  1. BMS SoC (High Precision):

Mode/PID: 224801

Header (CAN ID): 7E7

Formula: (A*256+B)/100

  1. Battery Voltage & Current:

Voltage PID: 224802, Header: 7E7, Formula: (A*256+B)/10

Current PID: 224803, Header: 7E7, Formula: (A*256+B-32768)/10

Updating the profile with these PIDs will resolve the "Fixed 3% SoC" issue for the new ë-C3/ë-C3 Aircross community.

Thank you for your assistance.

Where does this happen?
ABRP version number (found at bottom of settings menu)
Posted by Tayip UYGUN ·
Status: Completed20 comments

Log in to comment and vote

Comments20

  • Linda ABRP

    Team•

    Jan 15

    Hi

    To help us figure out what happen we need you to send a bug report. First you need to enable the bug button in the settings. Go to the settings and scroll all the way down.

    The bug button will show on your screen. When the OBD is connected to your car and the car is in drive mode click at the button. Then let me know when you have done this.

    • Tayip UYGUN

      •

      Jan 15

      My car's battery was at 67 per cent, as shown in the pictures. I'm writing to you after opening the options you mentioned.

      • Linda ABRP

        Team•

        Jan 16

        You need to go back to the map where the bug button will show. Click at it and I will get a report.

        • Tayip UYGUN

          •

          Jan 16

          Ok. I

          uploaded the report. Could you check it?

          • Linda ABRP

            Team•

            Jan 16

            Yes I got the report. We will look at it and then I will get back to you.

            • Tayip UYGUN

              •

              Jan 16

              Thank you very much. I am experiencing serious difficulties. I am calculating my trips manually. I kindly request that this issue be resolved.

              • Linda ABRP

                Team•

                Jan 16

                We can’t see any data. When you are in the car, have connected the OBD and see that data comes in from the car to the app then click at the bug report button.

                • Tayip UYGUN

                  •

                  Jan 16

                  I have provided the information you sent again. Could you please check it?

                  • Tayip UYGUN

                    •

                    Jan 17

                    The problem is visible in the photo. The vehicle's charge is reading everything incorrectly due to the outside temperature.

                    • Linda ABRP

                      Team•

                      Jan 19

                      We get wrong SoC from other Citroen e-C3 too using OBD so it probably means that we have the wrong Pids. We need to remove the access to OBD until we have the correct Pids.

                      • Tayip UYGUN

                        •

                        Jan 19

                        When will this issue be resolved?

                        • Linda ABRP

                          Team•

                          Jan 21

                          We need new pids that works for this car model before we can add the OBd option again.

                          “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.”

                          • Tayip UYGUN

                            •

                            Jan 21

                            Hi Linda,

                            Thank you for your response. I have successfully verified the following PIDs and data interpretation formulas on my Citroën ë-C3 Aircross (2024, CC21 Platform) using Car Scanner Pro. These values consistently return accurate data directly from the vehicle's CAN bus.

                            Below are the specific commands and instructions on how to interpret the returned data for your Telemetry API:

                            1. State of Charge (SoC) - Displayed Value

                            This PID matches the percentage shown on the vehicle's dashboard.

                            • Command (Mode/PID): 222002

                            • CAN Header: 7E0

                            • Data Interpretation: The value is a single byte (A).

                            • Formula: A / 2.55 (Returns 0-100%)

                            2. State of Charge (SoC) - BMS (High Precision)

                            This is the raw SoC from the Battery Management System.

                            • Command (Mode/PID): 224801

                            • CAN Header: 7E7

                            • Data Interpretation: Two bytes (A, B).

                            • Formula: (A * 256 + B) / 100

                            3. Battery Voltage

                            • Command (Mode/PID): 224802

                            • CAN Header: 7E7

                            • Data Interpretation: Two bytes (A, B).

                            • Formula: (A * 256 + B) / 10 (Volts)

                            4. Battery Current

                            • Command (Mode/PID): 224803

                            • CAN Header: 7E7

                            • Data Interpretation: Two bytes (A, B) with an offset of 32768 for signed values.

                            • Formula: (A * 256 + B - 32768) / 10 (Amperes)

                            I hope this technical breakdown allows you to add the OBD option for this model. This vehicle platform (CC21) is becoming very common in Europe and Turkey, and having native ABRP support would be a significant benefit for the community.

                            Please let me know if you need any further logs or testing.

                            • Tayip UYGUN

                              •

                              Jan 21

                              Technical PID Documentation for Citroën ë-C3 / ë-C3 Aircross (CC21 Platform)

                              Hi Linda,

                              Following your request for the OBD PID commands and data interpretation, I have performed a deep analysis of the CAN bus data for the new Citroën ë-C3 Aircross (2024+ CC21 Platform).

                              The following table summarizes the verified PIDs, headers, and the required interpretation formulas that align with your Telemetry API properties:

                              ABRP Telemetry Property

                              Description

                              PID (Hex)

                              CAN Header

                              Interpretation Formula

                              soc

                              State of Charge (Display)

                              222002

                              7E0

                              A / 2.55

                              soc (BMS)

                              High Precision SoC

                              224801

                              7E7

                              (A * 256 + B) / 100

                              voltage

                              Battery Voltage (V)

                              224802

                              7E7

                              (A * 256 + B) / 10

                              current

                              Battery Current (A)

                              224803

                              7E7

                              (A * 256 + B - 32768) / 10

                              batt_temp

                              Battery Temperature (°C)

                              224804

                              7E7

                              A - 40

                              Important Implementation Notes:

                              • Current Polarity: The formula for current (224803) includes a 32768 offset to handle signed integers.

                              • Protocol: This vehicle uses ISO 15765-4 (CAN 11bit 500kbps).

                              • Data Source: All values provided above have been cross-verified with real-time logs from the vehicle during both driving and charging sessions.

                              I hope this technical breakdown helps your team to integrate the OBD option for this vehicle profile. Please let me know if you need any additional logs or specific tests.

                              Best regards,

                              • Linda ABRP

                                Team•

                                Jan 21

                                Thanks. My colleague asks if you test this in the pid editor in ABRP and send us a json once it works?

                                • Tayip UYGUN

                                  •

                                  Jan 21

                                  Hi Linda,

                                  Thank you for the update. Regarding your colleague's question about the PID editor:

                                  1. Manual PID Entry Issue: I would have preferred to test these PIDs manually; however, the PID Editor/Custom PID option is currently not available or visible in my interface for this specific vehicle setup. If I were able to add them manually, I would have already implemented the fix myself. This is the primary reason for opening this support case.

                                  2. Model Discrepancy: Please note that my vehicle is the new Citroën ë-C3 Aircross (2024+, CC21 Platform). Currently, this specific model is missing from the ABRP vehicle selection list. I have been using the standard "ë-C3" (hatchback) profile as a temporary workaround, which is likely contributing to the "Fixed 3% SoC" error and the lack of manual PID editing options.

                                  3. Verified PID Data for Integration: Since I cannot use the PID editor, I am providing the verified data structure below. These values have been tested and cross-referenced with my vehicle's live CAN bus logs via Car Scanner Pro:

                                  • Model: Citroën ë-C3 Aircross (CC21)

                                  • Protocol: ISO 15765-4 (CAN 11bit 500kbps)

                                  • Display SoC PID: 222002, Header: 7E0, Formula: A/2.55

                                  • BMS SoC PID: 224801, Header: 7E7, Formula: (A*256+B)/100

                                  • Battery Voltage: 224802, Header: 7E7, Formula: (A*256+B)/10

                                  • Battery Current: 224803, Header: 7E7, Formula: (A*256+B-32768)/10

                                  Could you please use these verified parameters to update the profile or, better yet, create a dedicated profile for the ë-C3 Aircross?

                                  I am ready to provide further telemetry logs if your team can enable a test mode for my account.

                                  Best regards,

                                  • Linda ABRP

                                    Team•

                                    Jan 21

                                    We are releasing a new version, 7.0, for iOS probably today. There you will be able to see the pid editor when you click at Connect live data even if you don’t have the option for OBD.

                                    • Tayip UYGUN

                                      •

                                      Jan 21

                                      Hi Linda,

                                      Thank you for the update regarding Version 7.0. This is very promising news.

                                      I am currently in a very difficult situation because, without a working live SoC, I cannot use ABRP for any of my route planning. Having the SoC fixed at 3% makes the app unusable for long-distance trips in my new vehicle.

                                      I would like to emphasize again that my vehicle is specifically the new Citroën ë-C3 Aircross (CC21 Platform). It is a larger vehicle with different consumption characteristics than the standard ë-C3 hatchback. I kindly request that a dedicated profile for the Aircross model be added to your database to ensure accurate range calculations.

                                      As soon as Version 7.0 is available on my device, I will:

                                      Access the new PID editor as shown in your image.

                                      Input and verify the PIDs I discovered via Car Scanner:

                                      Display SoC: 222002, Header: 7E0, Formula: A/2.55

                                      BMS SoC: 224801, Header: 7E7, Formula: (A*256+B)/100

                                      Once I confirm it is working, I will export and send you the JSON file so your team can officially integrate it for all users.

                                      Thank you for your assistance in resolving this urgently.

                                      Best regards,

                                      • Linda ABRP

                                        Team•

                                        Jan 21

                                        There is a chance that the 3% also is on Citroens side. We have had users with Citroen e-C3 trying Enode and they had a similar problem. Enode asked them to contact Citroen. So maybe you can contact them first.

                                        • Tayip UYGUN

                                          •

                                          Jan 21

                                          Hi Linda,

                                          Thank you for the suggestion, but I believe there is a misunderstanding regarding the data source.

                                          1. Cloud API vs. Direct OBDII:

                                          The issues reported by Enode users are related to Citroën’s Cloud API/Telematics servers, which are indeed often unstable or restricted in certain regions. However, I am not using the Citroën cloud service or Enode. I am using a direct physical connection to the vehicle’s CAN bus via a Vgate iCar Pro 2S OBDII adapter.

                                          2. Proof of Data Availability:

                                          I have verified that the vehicle is broadcasting the correct SoC data. While ABRP is stuck at 3%, the Car Scanner Pro app, using the exact same OBDII adapter, reads the SoC perfectly (e.g., showing 44% or 64% in real-time).

                                          This confirms that:

                                          • The vehicle's hardware and BMS (Battery Management System) are working correctly.

                                          • The data is available on the CAN bus; it is simply a matter of using the correct PID to request it.

                                          3. The Solution is in the PIDs:

                                          The "fixed 3%" in ABRP occurs because the app is likely sending a generic OBDII request that the new CC21 platform does not support. When I use the specific PID 222002 (Header 7E0) or 224801 (Header 7E7) in Car Scanner, the data is returned instantly and accurately.

                                          I am looking forward to Version 7.0, as you mentioned, so I can manually input these working PIDs and prove that the hardware is fully compatible when the correct commands are used.

                                          Best regards,