We need the OBD PID commands and how to interpret the returned data. Since this is not easily available for most vehicles there is not possibility for us to provide a time estimate.
If you find that an existing vehicle profile reads data correctly, please let us know, but please DO NOT keep using the incorrect vehicle model with live data.
Katya S.
Team•
Apr 21
Could be that the PIDs we use for an already supported vehicle model could work. Here’s what you can do once you have access to the vehicle and a dongle;
Select the actual model of your car, save it
In vehicle settings, change the model of the saved vehicle to one that you suspect has compatible OBD commands (just any model will not work, it needs to be compatible)
Link the vehicle via OBD (details here; OBD Connection )
Select the correct vehicle model again
After verifying that the data is read correctly (or even partially correctly) notify us that the OBD commands for vehicle model X also works for vehicle model Y.
User
•
Apr 21
Thank you so much for the detailed reply. I will give this a go and let you know if its successful.
Samuel_ABRP
Team•
Oct 16
Should work now. Please try it.
ABRP User #2438832
•
Aug 9
Hi Katya / ABRP team,
the requested Kia PV5 OBD PIDs and interpretation are now available and have been tested successfully on the vehicle with a Vgate iCar Pro Mini BLE 4.0 and ABRP on iOS.
Working live dashboard/display SoC:
Protocol: ISO 15765-4 CAN (11 bit), OBD protocol 6
Request header: 7E4
BMS response address: 7EC
Initialization commands:
ATE0
ATH1
ATSP6
ATS0
ATM0
ATAT1
ATSH7E4
Data commands:
2201019
2201057
Telemetry:
key: soc
command: 2201057
equation: AF/2
type: Number
range: 0–100
This produced a parsed SoC of 74%, exactly matching the vehicle display, and ABRP showed the vehicle as connected with 74% live SoC.
2201019 is used as a warm-up request because the first BMS request after initialization can return CAN ERROR; the following SoC request succeeds. The final 7/9 digits are ELM expected-response-count modifiers used for reliable multi-frame retrieval with this adapter.
Additional values identified from the successful 220101 response:
current: ((Signed(K)*256)+L)/10 A
voltage: ((M<<8)+N)/10 V
power: (((Signed(K)*256)+L)*((M<<8)+N))/100000 kW
batt_temp: Signed(O) °C
soc_bms: E/2 %
The complete technical report and tested user setup are in the merged submission:
Could you please review this new technical data and update the “Awaiting Clarification” status? I can provide logs, screenshots and perform further tests if needed.
Log in to comment and vote
Comments5
Apr 21
PinnedHi,
We need the OBD PID commands and how to interpret the returned data. Since this is not easily available for most vehicles there is not possibility for us to provide a time estimate.
You can check our telemetry API for relevant properties:
documenter.getpostman.com/view/7396339/SWTK5a8w
Also, you can check our (partially outdated) OBD repository to see what other cars report:
https://www.github.com/iternio/ev-obd-pids
If you find that an existing vehicle profile reads data correctly, please let us know, but please DO NOT keep using the incorrect vehicle model with live data.
Katya S.
Apr 21
Could be that the PIDs we use for an already supported vehicle model could work. Here’s what you can do once you have access to the vehicle and a dongle;
Select the actual model of your car, save it
In vehicle settings, change the model of the saved vehicle to one that you suspect has compatible OBD commands (just any model will not work, it needs to be compatible)
Link the vehicle via OBD (details here; OBD Connection )
Select the correct vehicle model again
After verifying that the data is read correctly (or even partially correctly) notify us that the OBD commands for vehicle model X also works for vehicle model Y.
User
Apr 21
Thank you so much for the detailed reply. I will give this a go and let you know if its successful.
Samuel_ABRP
Oct 16
Should work now. Please try it.
ABRP User #2438832
Aug 9
Hi Katya / ABRP team,
the requested Kia PV5 OBD PIDs and interpretation are now available and have been tested successfully on the vehicle with a Vgate iCar Pro Mini BLE 4.0 and ABRP on iOS.
Working live dashboard/display SoC:
Protocol: ISO 15765-4 CAN (11 bit), OBD protocol 6
Request header: 7E4
BMS response address: 7EC
Initialization commands:
ATE0
ATH1
ATSP6
ATS0
ATM0
ATAT1
ATSH7E4
Data commands:
2201019
2201057
Telemetry:
key: soc
command: 2201057
equation: AF/2
type: Number
range: 0–100
This produced a parsed SoC of 74%, exactly matching the vehicle display, and ABRP showed the vehicle as connected with 74% live SoC.
2201019 is used as a warm-up request because the first BMS request after initialization can return CAN ERROR; the following SoC request succeeds. The final 7/9 digits are ELM expected-response-count modifiers used for reliable multi-frame retrieval with this adapter.
Additional values identified from the successful 220101 response:
current: ((Signed(K)*256)+L)/10 A
voltage: ((M<<8)+N)/10 V
power: (((Signed(K)*256)+L)*((M<<8)+N))/100000 kW
batt_temp: Signed(O) °C
soc_bms: E/2 %
The complete technical report and tested user setup are in the merged submission:
https://abrp.featurebase.app/de/p/kia-pv5-official-obd-ble-support-working-live-soc-pid
Could you please review this new technical data and update the “Awaiting Clarification” status? I can provide logs, screenshots and perform further tests if needed.