Bitwise and Logical operators needed for ODB2 PIDs (2026 e-TNGA/e-SGP)
The ODB2 PID editor equations in ABRP cannot properly interpret the available data for current from the 2026 e-TNGA/e-SGP EVs Such as the Toyota bZ/Subaru Solterra, Toyota C-HR/Subaru Uncharted and Toyota bZ Woodland/Subaru Trailseeker.
This is because the data is in signed integer format and interpreting this correctly requires bitwise and logical operators - ABRP appears to be handling everything as a signed integer. Trying to come up with work arounds results in ridiculous outputs during regen breaking of over 2.5MW
it also should be noted that the power number doesn’t update promptly with the PIDs inputted.
here are the PIDs i have for the 2026 Trailseeker I own
SOC comes from 22F45B equation ((A - 20) * 100) / 220 [errors on side of over-estimating across most of the range. data appears non-linear]
Current and Voltage both from from 22F49A - it is a multi-frame response that can be quite large
Voltage: (C * 256 + D) / 64
Current [requires operators ABRP doesn't support]: ((E * 256 + F) - (E & 128 ? 65536 : 0)) / 10
Power, Virtual PID: ( Current * Voltage ) / 1000
- Where does this happen?
- ABRP version number (found at bottom of settings menu)
Log in to comment and vote
Comments3
Jul 1
PinnedHello @Derek Meek,
Does it mean that you found the issue at hand by the comment about signed(E)?
Derek Meek
Jul 4
yeah, i just had a hard time finding the docs. I’ve got it working you can see my comments here and
https://abrp.featurebase.app/p/odb-support-for-2026-subaru-solterra
here
https://abrp.featurebase.app/p/subaru-trailseeker
I’m still trying to hunt down more of the PIDs for Gen2 e-SGP/e-TNGA
Derek Meek
Jul 1
NEVERMIND! you support signed(E) and i just couldn’t find it in the docs forever.