Skip to main content

OBD Connection Issues and PID Support for Opel Frontera Electric (2026)

Bug Reports

Opel Frontera Electric (54kWh Long Range, 2026) using a Vgate iCar Pro 2S dongle.

I followed your suggestion and tested several Stellantis profiles (including the Peugeot e-3008, Astra Electric, and Jeep Avenger). Unfortunately, I am consistently encountering the following issues:

Initialization Errors: Even when the dongle is correctly paired, I receive an "Error writing init commands" and a message stating "could not get commands for type init from [object Object] opel:frontera:25:54".

Connection Stability: While the device works perfectly with Car Scanner Pro, ABRP often reports "not connected to any BLE device" or fails the data handshake during the PID test.

Data Parsing: On the few occasions a connection was partially established with other profiles, the SoC (State of Charge) data was either missing or completely incorrect.

As a Premium user, I really want to get this working. Could you please check if the PID set for the new Stellantis Smart Car Platform (used in the Frontera and new e-C3) can be implemented? If you need specific logs or if I can assist by running a specific debug mode to capture the PIDs you need, please let me know.

I look forward to your help in making the Frontera Electric fully compatible.

Best regards,

Where does this happen?
ABRP version number (found at bottom of settings menu)
Posted by ABRP User #2685130 ·
Status: Awaiting Clarification7 comments

Log in to comment and vote

Comments7

  • Mahde - ABRP

    Team•

    Jul 10

    Hello @User,

    OBD support has been added for this vehicle (2025+ model) now. Please check that it works as it should and let us know of any issues you find.

    • ABRP User #2685130

      •

      Jul 10

      Hello, it's working fine, but the battery percentage isn't showing correctly. I'm talking about the 54kW long-range model.

      typecode: opel:frontera:25:54
      pids:
      {"data_commands":{"command":["ATSH6B4","ATFCSH6B4","ATFCSD300000","ATFCSM1","ATCRA694","22D408","22D510","22D511"]},"init_commands":{"command":["ATD","ATE0","ATH1","ATAT1","ATL0","ATS0","ATSP6"]},"obd_protocol":"6","keep_alive":{"command":"ATSH6B4"},"soc":{"command":"22D408","equation":"((A*256)+B)/10","type":"Number","minValue":0,"maxValue":100},"voltage":{"command":"22D510","equation":"((A*256)+B)/10","type":"Number","minValue":200,"maxValue":450},"isVerified":true,"current":{"command":"22D511","equation":"((A*256)+B)/10-62","type":"Number","minValue":-300,"maxValue":300}}

      To: premium@abetterrouteplanner.com
      App version: 7.1.3
      Build number: 5920
      Platform: ios
      User ID: 2685130

  • Bo (ABRP)

    Team•

    May 13

    Thanks for the detailed reports! Since you have been able to find a profile which partially works, I would recommend that you try the ABRP PID editor and play with the equations for parsing yourself. Perhaps you can find some inspiration from other vehicles from the data available at https://github.com/iternio/ev-obd-pids

    • ABRP User #2685130

      •

      May 13

      Hi Bo,

      Following up on the Opel Frontera Electric OBD support request.

      I did the work you suggested and was able to reverse-engineer the SoC formula myself by analyzing Car Scanner Pro logs. Here is what I found:

      Vehicle platform confirmation: Car Scanner Pro v2.1.15 groups the following three vehicles under a SINGLE shared OBD profile: "Citroen e-C3 CC21 (2024-) / Fiat Grande Panda EV (2025-) / Opel Frontera EV (2024-)"

      This is official confirmation that all three Stellantis Smart Car Platform / e-CMP vehicles share an IDENTICAL OBD command set. If ABRP already supports any of these three, the Frontera will work with the same PIDs.

      Connection parameters (verified working):

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

      • TX Header: 6B4

      • RX Filter: 694 (VCU) / 682 (BMS)

      • Flow control: ATFCSH 6B4, ATFCSD 300000, ATFCSM 1

      • Tester present: 22 D4 0A → response 62 D40A xx xx (12V battery voltage)

      SoC formula (verified against displayed dashboard value):

      When the dashboard showed 64% SoC, I captured the following values:

      PID 22 D5 A4 (BMS, header 6A2 / rx 682): Raw value: 0x2940 = 10560 Formula: value * 100 / 16384 Result: 64.45% ✓ matches dashboard

      PID 22 D5 23 (BMS, same header): Raw value: 0x2B30 = 11056 (Real/BMS SoC) Formula: value * 100 / 16384 Result: 67.48% (approx. 3% higher than displayed — typical Real vs. Displayed SoC offset)

      Other PIDs captured (multi-frame ISO-TP responses, headers 6A2/682 BMS and 6B4/694 VCU):

      • D510 (VCU): HV pack voltage, raw 0x0D81 = 3457 → /10 = 345.7V

      • D511 (VCU): HV pack current, raw 0x043E → likely signed, needs verification

      • D423 (VCU): Odometer, raw 0x0004A0 = 1184 km ✓ matches dashboard

      • D40A (VCU): 12V auxiliary battery, raw 0x0D81 → /100 = 14.85V ✓

      • D4CB–D4D2 (VCU): Individual cell temperatures, all approximately 0x41 (~65°C raw, needs offset)

      • D562/D563/D564 (BMS): Cell voltages ~0x0C13 (3091 → /1000 = 3.09V per cell)

      I have full Car Scanner logs with all PID command/response pairs (both BMS and VCU ECUs), captured across multiple sessions including charging and driving states. I can share them privately if useful.

      Given this evidence, I would like to ask:

      1. Can ABRP now add live OBD support for the Frontera Electric using these confirmed PIDs and formulas?

      2. Alternatively, can you share the Jeep Avenger OBD profile JSON privately, since the Avenger is also on the same e-CMP platform? I tested the Avenger profile on the Frontera and connection initialized successfully, but SoC reading was scaled incorrectly (~4% when actual was 41%). With minor scaling adjustments it would likely work.

      As a Premium subscriber I would appreciate either an internal fix using the data I have provided, or access to the existing Avenger profile so I can adapt it via the in-app PID editor.

      Thank you for your time.

      b64u-RnJvbnRlcmFfRVZfdjIuanNvbg.json

      3.6 KB• Text

      Best regards, Yasin

  • ABRP User #2685130

    •

    May 13

    I ran a PID test and attached a screenshot of the results.

  • ABRP User #2685130

    •

    May 9

    Following up on my Frontera Electric profile request: I tested the Jeep Avenger Longitude FWD 16" profile with my dongle and got a partial success. The OBD test results:

    • Init commands: ✅ SUCCESS

    • Data fetch commands: ✅ SUCCESS

    • Live data flowing

    However, SoC parsing is incorrect. ABRP reads ~4% when actual SoC is ~41% (10× difference, suggesting a scaling factor mismatch in the SoC PID formula). I have NOT used this for route planning since you advised against it.

    This is strong evidence that:

    1. PIDs are protocol-compatible between Avenger and Frontera

    2. Only the parsing/scaling formulas need adjustment

    3. The platform sharing argument is correct

    I am happy to test additional profile updates with controlled SoC readings (logged via Car Scanner Pro for ground truth). Please let me know what data would be most useful for calibrating the Frontera profile.

  • ABRP User #2685130

    •

    May 9

    Following up on my previous request to add the Opel Frontera Electric to ABRP. As requested, I’ve gathered evidence that the OBD PIDs are already documented and working correctly.

    Vehicle: Opel Frontera Electric, 54 kWh Long Range, 2026 model (Stellantis Smart Car Platform / e-CMP)

    Dongle: Vgate iCar Pro 2S

    Protocol: ISO 15765-4 CAN (11 bit ID, 500 kbaud)

    App: Car Scanner Pro (Frontera vehicle profile added December 2025)

    Live data log (CSV):

    https://drive.google.com/file/d/1woTpNWvO9wVA4NYy4z8ubcuNsOLG5Lcb/view?usp=drivesdk

    The Car Scanner Pro Frontera profile reads all critical EV parameters correctly. Key values from the log (parked, ignition on):

    • [BMS] Traction battery SoC: 41.1 %

    • [VCU] HV Battery SoC: 41.296 % (high-precision alternative)

    • [BMS] Traction battery voltage: 339.5 V

    • [VCU] Traction battery current: 0.25 A

    • [BMS] Traction battery Average Temperature: 19 °C (plus 16 individual cell temperature sensors)

    • [BMS] Traction battery Total Energy Capacity: 53,792 Wh (matches 54 kWh nominal spec)

    • [BMS] Traction battery Actual Energy: 21,792 Wh (consistent with reported SoC: 21,792 / 53,792 = 40.5 %)

    • [BMS] Odometer: 1,184 km

    • [VCU] On-board charger output power: 0 W (AC charging tracking available)

    • [VCU] Max HV Battery discharge power for 30 sec: 230 kW

    • [VCU] HV Battery generated power limit for 30 sec: 113.6 kW

    ECU prefixes [BMS] and [VCU] in the log indicate which ECU each PID is queried from, simplifying profile construction.

    Additional resources:

    • The Frontera community on frontera-forum.de (thread #181) has independently verified these readings on multiple Vgate dongles.

    • Car Scanner Pro’s developer (OBDDeveloper / OvZ) holds the full PID definitions and may be willing to share them with your team.

    • The Stellantis Smart Car Platform / e-CMP is shared with Citroën e-C3, Fiat Grande Panda, and Jeep Avenger — the Avenger PIDs already in your iternio/ev-obd-pids repository likely overlap significantly.

    I am happy to record additional logs (driving, DC fast charging, AC charging) if helpful. As a Premium subscriber, I would greatly appreciate a vehicle profile being added.

    Please let me know if the Drive link is accessible — it is set to “Anyone with the link can view.” If you prefer the file as an attachment, I can resend it that way.

    Best regards