2026 Subaru Uncharted Sport
Hello, I saw a post about setting up OBD BLE support for the 2026 Subaru Solterra but not one about the Subaru Uncharted so here’s a request.
I added my Uncharted, Sport trim, to the app and then changed the vehicle to Solterra so I could connect to my OBDLink CX dongle. From there, I have been experimenting with the Solterra equations and tweaking them to try and match what I see in my car and the logs from my dongle.
This is what I’ve got working on the OBD PID editor in the app, referencing the telemetry API.
OBD Protocol: 7
Keep alive command: (blank)
Initialization commands: same 13 as Solterra
Data fetching commands: 22F45B, 22F40D, 22F4A6, 22F49A, 22F446, 22F465
Telemetry keys:
current - command 22F49A, equation: (SIGNED(E)*256+F)/10
verified against a DC fast charger and comparing what I see in the PID editor against logs from my dongle generated under similar driving conditions.
ext_temp - command: 22F446, equation: A-40
This is accurate when the car is in ready mode/driving but drops to -40 when power is off because the bit changes to 00.
is_parked - command: 22F465, equation: B==0 (boolean)
I’m least confident of this one, but it also seems the least important - the bit is 02 when the car is in drive or reverse, and 00 when parked or in neutral
odometer - command: 22F4A6, equation: INT32(A:B:C:D)/10
soc - command 22F45B, equation: 0.4333*A-3.9131
I know there is a different equation out there for the Solterra, and this is a work in progress but it’s consistently within 1% of what shows on my dashboard.
speed - command 22F40D, equation: A
voltage - command: 22F49A, equation: INT16(C:D)/64
Unfortunately I can’t figure out is_charging or is_dcfc. I’m learning about this as I go from other posts so please let me know if something here doesn’t make sense or if you have other feedback. Thank you!
- What type of vehicle connection is this?
Log in to comment and vote
Comments24
ABRP User #2829409
Jul 9
Alright, I ran into the same problem as Theron. My line was really good through about 39%. Below that it started to fall off more quickly. It made me thing that things weren’t linear in the lower numbers. However, I charged with a level 1 charger overnight and got up to about 24% and ran the numbers, and it was even further below Theron’s chart. He had mentioned things getting way off after he charged, and I see that too. One positive is that it seemed we both had the same slope, but the Y-intercept was quite different. This makes me think that either the 22F45B or A aren’t actually just strictly the SoC, or the dash SoC display factors in other things instead of pure percent left. Here are the numbers I got, but I’m not sure that we’re on the right path for helping the ABRP guys to get OBD2 integration up and running.
80%: 182
80%: 181 (the dash is rounded to whole number, it makes sense that multiple raw numbers equal a percent, since 80% could mean anything between 79.5-80.4%)
79%: 180
75%: 172
74%: 169
73%: 164
70%: 155
69%: 153
69%: 150
59%: 129
54%: 119
52%: 111
45%: 96
44%: 92
41%: 86
39%: 80
29%: 61 (the slow started to curve downward here)
24%: 53
17%: 39
10%: 27
8%: 25
7%: 22 (I then charged overnight)
24%: 70
23%: 68
22%: 62
21%: 58
I’ve attached my graph (with comments) along with Theron’s numbers. The fit line is still there, but I’m not sure I trust it anymore. I’d love to hear anyone else’s thoughts that might have more experience with this.
Theron Schultz
Jun 23
I guess I was too naive about the soc equation. I thought I had it all figured out but there must be more to it in the car’s CPU because the dash % is more variable than I thought. The same result (A9, or 169) from the OBD command has shown as 72, 70, and 68 on my dashboard at different times.
So instead of consistently within -1% to +1% the equation I have is more like -3% to +3%.
Theron Schultz
Jul 4
You are correct, the formula in my post worked only until I re-charged and since then it is wrong.
I have been logging the last 10 days using the test PIDs button and comparing the dash % to the value returned for A. Of course, it keeps moving around like I mentioned in my last comment. I’m not sure if it has to do with warmer weather, or the car adjusting depending on where (or how) I drive, or something else.
Based on you getting 74% from my equation and 77% from the Solterra one, it seems like your value for A must be 180. My car has shown 75% on the dash both times I happened to log that value. Like I said in my last comment, there appears to be a lot of variance in what the dash shows. The most annoying case for me is my car showing 70% at A = 164 and another time at A = 172.
I was hoping it would be straightforward to figure this out, but unfortunately that is proving not to be the case. Probably the Solterra equation is as good as anything else.
ABRP User #2829409
Jul 5
One new option that just opened up is that the Car Scanner app was updated and offers ABRP integration now. If you have a dongle, you can use that with the generic OBD profile for the Uncharted and skip using the Solterra. One downside is that the SoC measure seems to be the raw number and not what’s displayed on the dash and is 7-10% below it, and you can’t save in the custom PID without the standard dongle connection. I got around this by switching to a Solterra, entering and saving the PID, then switching back to the Uncharted. This might be helpful so that ABRP uses the weight, wind resistance, etc. qualities of our smaller vehicle instead of the Solterra. I’ve also found the formula you have for Speed to be a bit off. For my vehicle, using
0.9445*A-0.4 was a bit more accurate. I have a GT though, so this might be the one number where the larger wheels make a difference between it and the Premium/Sport. It’s tough to test this though as Speed isn’t listed in Live Data and has to be measured using Test PID while you’re driving.
ABRP User #2829409
Jul 4
When I tried your SoC formula at 80%, I got 74%. The default Solterra one was 77%.