I've connected successfully with my Veepeak OBDCheck BLE 4.0 scanner, but I had to override the detected VIN to get the app to connect. When the app attempts to communicate it panics the dash cluster and everything resets. I don't imagine it's going to hurt the car, but I'm going to hold off driving around with it connected for now. I've used the scanner without issue on ABRP previously so I know it's functional.
Looks like the diagnostic mode might be the culprit of the weird dash cluster behavior. I've removed the diagnostic mode request as it seems like the EV9's responding fine without it. Please refresh your parameters (https://sidecar.clutch.engineering/help ... parameters), verify you're on SHA: f991ec0, then try scanning again.
Yeah that seems to have resolved the cluster reset. I took a trip to the store and back without any issues. The BAT_SOC id is pulling the current state of charge, but EV9_HVBAT_SOC seems invalid. A bunch of the standard status values also load up. I didn't screengrab them all because they seemed generic.
Sending an updated scanner dump.
Attachments
photo_2024-10-18_18-05-26.jpg (79.21 KiB) Viewed 808 times
photo_2024-10-18_18-04-45.jpg (38.75 KiB) Viewed 808 times
According to Car Scanner's profiles, IONIQ 5/6, EV6/9, Niro EV, Kona EV, GV60/70/80 should all use a similar command set. They have a unified connection profile. I'll check it out later today.
Most of them looked good, with only a couple notes.
Odometer doesn't seem to be looking in the correct place because it's returning 0.
It looks like there are multiple options for SOC and they don't always agree. The dash cluster was showing the car at 80%.
I was parked in the garage so I didn't get to test whether vehicle speed returned the correct value.
I also grabbed a dump from Car Scanner, which may help in pointing out other useful data points to look for. It doesn't appear to have any sensitive information in it, but I'll send it via email just in case.
Screenshot
Screenshot
Screenshot
photo_2024-10-20_11-27-41.jpg (88.07 KiB) Viewed 764 times
photo_2024-10-20_11-27-37.jpg (90.16 KiB) Viewed 764 times
photo_2024-10-20_11-27-34.jpg (60.29 KiB) Viewed 764 times
photo_2024-10-20_11-27-30.jpg (26.72 KiB) Viewed 764 times
photo_2024-10-20_11-27-26.jpg (90 KiB) Viewed 764 times
photo_2024-10-20_11-27-04.jpg (26.55 KiB) Viewed 764 times
If you can do another run with Sidecar connected to your EV9 and export the logs that will help identify the remaining steps we need to take to get the EV9 fully onboarded.
For the Odometer I made an update to the parameters last week so hopefully we can see some improvements in this next test run.
@kanithus btw the last OBD export I received from you was October 18 5 hours before I made the updates to the parameter set, so I don't have a database of logs using what is now SHA: acae5ca.
@kanithus I think the last thing to see if we can try to tune is the SOC parameters; it's fairly common for cars to have multiple but I want to make sure that the ones we've documented are in fact correlated with real data, so if you can periodically check on the parameters and square them up with your dash, we can hopefully get a good sense of which parameters are closer to the dash value. Mind that off-by-one values are not uncommon because of differences in rounding.