Skip to main content

OBD values for 2024 KGM TORRES EVX incorrect

Hello ABRP Team,

I would like to request an engineering review of the telemetry and vehicle model profile for the KGM Torres EVX 2024.


Current ABRP version: 7.0.5 (5819)

After extensive real-world testing with an OBDLink CX adapter and comparing live data against the vehicle dashboard and Car Scanner, it appears that the current Torres EVX profile may need serious refinement.

Main findings:

  1. SOC is accurate and matches the vehicle.

  2. SOH is incorrect in ABRP (around 53%) while Car Scanner reports around 92%.

  3. Battery current and power scaling appear inconsistent.

  4. Outside temperature requires offset correction.

  5. Battery temperature PID mapping may need validation.

Because these values directly affect route planning, usable battery estimates, charging predictions, and confidence in ABRP, I kindly request a technical review of:

  • Telemetry PID mappings

  • Scaling formulas

  • Battery model parameters

  • Official Torres EVX OBD profile update

I would be happy to help with testing and feedback if required.

Thank you very much.

Where does this happen?
ABRP version number (found at bottom of settings menu)
Status: In Progress14 comments

Log in to comment and vote

Comments14

  • Samuel_ABRP

    Team•

    Jul 15

    Pinned

    Hey, everyone, sorry for the broken SoC. Reverted the SoC calculation back to the original equation. It should be live in a few minutes.

  • sinan oguc

    •

    Apr 30

    Hello ABRP Team,

    Thank you for your response.

    After testing with the ABRP OBD PID editor on a KGM / SsangYong Torres EVX 2024 (OBDLink CX, Android), I can confirm that most core signals are now working correctly after manual calibration.

    Here is a structured summary:

    ---

    ✅ Working / Verified Signals

    - SoC (22F403 → A) → stable and accurate

    - Voltage (22F417 → INT16(A:B)*0.1) → correct

    - Current → consistent

    - Power (voltage * current / 1000) → now correct

    - Battery temperature → stable

    ---

    🔧 Improvements Made

    - Corrected scaling factors (especially SoH and voltage-related values)

    - Fixed byte parsing issues (INT16 vs single byte)

    - Removed incorrect formulas causing unrealistic values

    - Verified that running “Test PIDs” improves live data responsiveness

    ---

    ⚠️ Remaining Issues

    1. External Temperature (ext_temp)

    - Appears sometimes in live data

    - But does NOT show consistently in PID test

    - Tried multiple OBD commands → no stable result

    👉 Likely ECU-specific or requires different initialization/header

    ---

    2. Data Refresh Delay

    - Without “Test PIDs” → live data is delayed

    - After test → data updates immediately

    👉 Suggests initialization / polling sequence issue

    ---

    3. Power Fluctuation at Low Speed

    - Rapid fluctuations in traffic

    - Verified this is likely real behavior (low current resolution), not PID issue

    ---

    4. SoH Calibration

    - Required scaling correction

    - Now aligns with BMS (~91–92%)

    ---

    📌 Additional Observation

    Telemetry stability improves significantly when:

    - Android battery optimization is disabled

    - Bluetooth load is minimal

    ---

    💡 Suggestion

    To improve reliability:

    - Keep working signals (SoC, voltage, current, power, battery temp)

    - Disable/remove unstable ones, especially:

    - External temperature

    - Any PID not consistent in test mode

    ---

    I’m happy to continue testing and help refine the PID profile further.

    Best regards,

    Sinan

  • sinan oguc

    •

    Apr 29

    •

    Merged request

    •

    1 vote

    KGM TORRES EVX 2024

    Hello ABRP Support,

    I am using a KGM Torres EVX 2024 with OBDLink. The OBD connection works, but several telemetry values appear to be incorrect, which may be affecting ABRP range calculations and battery estimates.

    The most important issue is SOH:

    • ABRP shows SOH around 53%

    • Car Scanner shows SOH around 92%

    The vehicle is healthy, so the ABRP value is clearly wrong. I believe ABRP may be reading the wrong PID or using an incorrect formula for SOH.

    Please note:

    • SOC is correct and matches Car Scanner exactly.

    • So the main problem is not SOC, but SOH and possibly some other battery values.

    Could you please confirm the correct OBD commands and formulas for KGM Torres EVX 2024?

    Main problematic values:

    1. SOH
      ABRP: 53%
      Car Scanner: 92%
      This is the most critical issue because it affects usable battery capacity and route planning.

    2. Battery temperature
      Current tested PID: 22F417
      Need confirmation of correct PID/formula.

    3. Outside temperature
      Current tested PID: 22F413
      Sometimes offset compared to vehicle display. Need confirmation.

    4. Battery current
      Current tested PID: 22F402
      Need confirmation of correct scaling and sign.

    5. Battery power
      Currently calculated manually using voltage × current.
      Is there an official PID for battery power?

    6. Battery voltage
      Current tested PID: 22F190
      Need confirmation if this is the correct HV battery voltage PID.

    Vehicle details:

    • Model: KGM Torres EVX 2024

    • Region: Turkey

    • OBD adapter: OBDLink CX

    If you have an official or verified OBD profile for Torres EVX, I would be happy to test it.

    Thank you very much for your support.

  • sinan oguc

    •

    Apr 29

    •

    Merged request

    •

    1 vote

    TORRES EVX 2024 OBD

    Hello ABRP Support Team,

    I am using ABRP on Android with my vehicle KGM Torres EVX 2025 and an OBDLink CX adapter.

    The OBD adapter and vehicle are working correctly:

    • Car Scanner app reads live data without any issues (SoC, battery power, current, etc.)

    • OBDLink CX firmware is up to date

    • Bluetooth and permissions are correctly configured

    However, ABRP does not receive any live OBD data:

    • ABRP connects to the OBDLink CX

    • Live data (SoC, power, consumption) remains empty

    • Vehicle profile selected: Torres EVX 2025

    Based on testing, it seems that ABRP does not yet support the required CAN/PID mapping for the Torres EVX, even though the vehicle profile exists for planning.

    I am happy to help by:

    • Providing Car Scanner OBD logs

    • Sharing PID information

    • Testing beta versions if needed

    Please let me know what data you need to enable OBD live data support for the Torres EVX.

    Thank you for your great work.

    Best regards, [Your Name]

    • sinan oguc

      •

      Apr 29

      •

      Merged request

      •

      1 vote

      Can not connect the KGM Torres EVX to ABRP via OBD

      Hello ABRP Support,

      I am using a KGM Torres EVX 2024 with Android and OBD adapters.

      I tested with:

      OBDLink CX

      Vgate iCar Pro 2S

      ABRP can detect the BLE adapter successfully and starts OBD connection.

      Status shown in app:

      Vehicle configuration loading: OK

      BLE connection established: OK

      Vehicle connection status: Failed

      However, ABRP is still able to read some battery values such as:

      Battery voltage: around 406.7 V

      Current: around -23.7 A

      So the adapter works and some CAN data is available, but the vehicle connection does not complete.

      Could you please check KGM Torres EVX 2024 support / OBD profile / PID mapping?

      I would be happy to help test if needed.

      Thank you.

      • Linda ABRP

        Team•

        Apr 17

        Hi

        Please look at this video to see how to change in the Pid editor.

  • Bo (ABRP)

    Team•

    Apr 29

    Thanks for the detailed report! Our OBD PIDs usually come from open sources so there may be issues with them. Would you be able to help us out using the ABRP OBD PID editor? If you cannot find a setting which works, we can at least remove those properties so they don’t ruin the planning.

    • sinan oguc

      •

      Apr 29

      Hello ABRP Team,

      Thank you for looking into the OBD support for the SsangYong / KGM Torres EVX (also sold under KG Mobility branding). I spent time testing and validating the current telemetry profile using an OBDLink CX adapter and your OBD PID Editor. I’d like to share complete findings so the profile can be improved for all Torres EVX users.

      Vehicle / Hardware Used

      - Vehicle: SsangYong Torres EVX / KG Mobility Torres EVX

      - Adapter: OBDLink CX (BLE)

      - Android device

      - ABRP Live Data + OBD PID Editor

      Main Issue

      The default Torres EVX profile connects and reads data, but some telemetry values are incorrect or misleading. This affects route planning quality.

      What Was Working

      The connection process works with OBDLink CX.

      Custom PID test mode was successful.

      The following values appear valid:

      Confirmed Good Values

      - SOC = 85%

      - Voltage ≈ 405V

      - Current ≈ 89.5A

      - Power ≈ 36.3 kW

      (calculated from voltage * current / 1000)

      These values were internally consistent.

      Main Incorrect Value: SOH

      Existing Default Formula

      Telemetry key: "soh"

      PID:

      "22F413"

      Formula currently used:

      "A*0.5"

      Result

      Returned value was around:

      "50.46%"

      and later ~53%

      This is clearly unrealistic for the tested vehicle.

      Cross-check with Other App

      Car Scanner reports battery SOH around:

      "92%"

      Tested Alternatives

      1. "INT16(A:B)*0.1"

      - Failed / no value returned

      2. "A*0.912"

      - Returned ~52.9%

      3. "A*1.55"

      - Returned:

      "89.9%"

      This is much closer to Car Scanner’s ~92%.

      Recommendation

      Please replace current SOH formula:

      From:

      "A*0.5"

      To:

      "A*1.55"

      (Or fine tune if you have internal validation data.)

      This alone would dramatically improve planning accuracy.

      ---

      Possible Fine Calibration

      If desired:

      - "A*1.58" ≈ 91.6

      - "A*1.59" ≈ 92.2

      But "A*1.55" is already usable and realistic.

      ---

      External Temperature Issue

      Telemetry key:

      "ext_temp"

      Current result:

      "65°C"

      This was incorrect during normal ambient conditions.

      This value appears invalid, mapped incorrectly, or using the wrong scaling / wrong PID.

      Recommendation

      Until corrected:

      - remove "ext_temp" from the profile

      or

      - disable it from route calculations

      because false temperature may negatively affect consumption modeling.

      ---

      Battery Temperature

      Telemetry key:

      "batt_temp"

      Returned:

      "15°C"

      This may be plausible depending on environment, but should be validated.

      ---

      Current / Power Sign Convention

      Current was positive during driving/load and power calculation matched positive propulsion demand.

      No obvious issue here.

      ---

      Summary of Recommended Fixes

      Update Torres EVX profile:

      Keep

      - SOC

      - Voltage

      - Current

      - Power

      Fix

      SOH:

      PID "22F413"

      Use:

      "A*1.55"

      Remove / Recheck

      - ext_temp (currently returning 65°C incorrect)

      Validate

      - batt_temp

      ---

      Why This Matters

      Many Torres EVX owners rely on ABRP for trip planning. Incorrect SOH especially can significantly distort:

      - battery degradation estimation

      - usable capacity

      - charging strategy

      - arrival SOC predictions

      - route confidence

      Fixing these values would likely solve issues for many current and future Torres EVX users.

      ---

      Final Note

      I’d be happy to test updated profiles if needed.

      Thank you for supporting this vehicle platform.

  • Samuel_ABRP

    Team•

    Jul 2

    Hey, I just pushed the updates from this threads discussion. Should be live in about an hour. Let me know if that improves the situation for you.

    • ABRP User #3289

      •

      Jul 7

      That’s the time I lost my correct communication between abrp and OBDlink cx. Please turn it back again!!!