Skip to main content

OBD support for 2026+ Subaru Solterra

I have a 2026 Solterra and the ODB dongle OBDLink CX. Get error “Error while handling ODB data commands” “We could not find SoC in the car data response” The car configuration loads and the connection to the dongle is successful, it just will not connect to the car.

What type of vehicle connection is this?
Status: Completed75 comments

Log in to comment and vote

Comments75

  • Samuel_ABRP

    Team•

    May 17

    Pinned

    We have now a working SoC reading via OBD, which is the most important value anyways. Calibration also works via SoC (without voltage + current / power). However power is even more accurate, so if anyone can find the proper values via the custom OBD editor, let me know and we’ll add it.

    • Kanchana Marasinghe

      •

      May 18

      This is what I found for voltage and current:

      https://abrp.featurebase.app/p/odb-support-for-2026-subaru-solterra/comment/69bcc89f5f0e284fdbce3258

      Copying the text from that comment:

      For the voltage and current I'm not sure if ABRP in its current way can handle it. The correct PID is 22F49A however it's a multi frame response split across 2 frames. All the data is there but ABRP cannot parse and split the data correctly.

      So voltage and current are in the same response. Because they're not single frame results for voltage and current individually, it can't be used to derive power. I'm fairly sure at this point ABRP needs an update to handle this.

      • Samuel_ABRP

        Team•

        May 18

        ABRP supports multi frame messages. Just try it in the custom OBD pid editor, and you’ll see if it works. If the response looks weird feel free to reach out to me at samuel@iternio.com and we can sort it out somehow.

        • Kanchana Marasinghe

          •

          May 19

          Nice, that's good to hear. I'm not 100% sure but I tried with the PID 2249A and got this:

          HVAC off: 0090:62F49A0E00671:C00008CCCCCCCC

          HVAC on: 0090:62F49A0E00671:C00018cccccccc

          For voltage I tried the formula

          ((C*256)+D)*0.015725 and it seemed like it returned an ok value (415v). I haven't had much getting a reasonable value for the current though.

          • Kanchana Marasinghe

            •

            May 19

            I thought maybe current was F*0.1 and it seems alright when at a stop but the numbers don't make a lot of sense when accelerating hard or under regen. I'm confident it's 9A that is the right PID but I'm not sure how to pull the current from it correctly. The voltage seems alright but I'm not 100% certain.

            • Samuel_ABRP

              Team•

              May 20

              You can check current and voltage at a charger and compare the values to what you see on the charger display. Please only send us values, that you have confirmed to be correct. You can open a new issue for that, we will not watch completed issues anymore.

  • Dominick Feragola

    •

    May 5

    Pinned

    This issue seems to be a recurring problem. Please come up with a solution. I'm hopeful that is Solterra EV owners will have a functional Trip planner with abrp. Thanks

    Here is some information that might help.

    2026 Solterra Advanced OBD2 Settings (for SOC) []

    • OBD Protocol: 7

    • Keep Alive Command: 3E00

    • Initialization Command: ATSP7, ATSH18DA5AF1, ATCRA18DAF15A, ATCAF1, ATE0, ATH0, ATL0, ATST64

    • Data Fetch Command (PID): 22F45B

    • Equation: (A/2.55-5)/0.9 (Results in a 0–100% range) [1]

    • Katya S.

      Team•

      May 8

      This may be helpful. But we would need to be able to confirm correct data is being read in collaboration with users.

      • Dan Leavitt

        •

        May 13

        Explain what we can do to help. Is there a way to get detailed diagnostic info from the connection sequence for you?

    • Samuel_ABRP

      Team•

      May 13

      Hey,

      I’m currently adding the new pid commands for the 2026 models. We got this from another user:

      (A*100/255 * 1.125) - 2.8

      It roughly is a diff of 3 percentage points to your calculation. Not sure which one to pick now. Any hints on that?

      • Deric Anthony

        •

        May 16

        The one you are using has consistently been within 1% of the vehicle displayed value for me.

        • Samuel_ABRP

          Team•

          May 17

          Thanks for feedback

  • Nick Leber

    •

    Jan 14

    Can we please get some traction on this ticket thanks

  • Luciano Martinez Stefanini

    •

    Jan 15

    Exactly the same problem. It looks like the connection profile for the Subaru Solterra 2026 and Toyota Bz 2026 was changed in 2026

  • Patrick Gelvin

    •

    Jan 5

    I have also experienced this issue for my 26 solterra (vgate icar pro obd reader, version 6.1.9 (3648) of the iOS app), I hope it can get resolved soon.

  • Armen

    •

    Jan 5

    Same here with my 2026 BZ, think the coding, PID or whatever it is that’s talks to the OBD to the car is different than previous years.

    • Nick Leber

      •

      Jan 7

      yes I can get the SoC and other telemetry via the ODBLink app, so its def accessible with the correct code.

  • F.A. Peeters

    •

    Jan 17

    Same issue here with my Toyota bZ4X 2026+. Can connect via OBDLink app and read data, but adding through ABRP shows “We could not find SoC in the car data response”. Using a OBDLink CX with latest december firmware. ABRP version 6.1.9 (3648) on iOS 26.2.

  • Mahde - ABRP changed status to Awaiting Clarification
    Team•

    Dec 22, 2025

    Hello @Nick Leber,

    This is more likely a bug that we need to report. But first, I need to know:

    • Where does this happen (iOS, Android Auto, CarPlay etc.)

    • ABRP version number (you can find this by entering settings in ABRP and scrolling to the bottom)

    • User

      •

      Jan 4

      Can we get this moved out of awaiting confirmation?

  • User

    •

    Feb 1

    What clarification do you need @Mahde ?

  • Mahde - ABRP

    Team•

    Feb 2

    Hello @Nick Leber,

    Have you tried to use the custom OBD pid editor to change the commands? If there are any working OBD pid command available on the internet, please try to use them and if it works for you afterwards.