Cars Forum

Send me your OBD scan logs and I'll take a look at why it's not finding any parameters: https://sidecar.clutch.engineering/help ... -scan-logs

One thing to check quickly too: does the scanner pick up your VIN in the Settings > Your scanners page?

@jeff just emailed the ODB logs and will be getting out again in a hour and will check if it picks up the VIN

Looks like the VIN being returned from the car is "NE3EV- BMS", which will require you set up a fallback vehicle in the Sidecar UI to pull the IONIQ 5 parameters. Had you already set up a fallback vehicle though?

@jeff did the fall back and its not showing a error anymore but still no data coming thru the app. Happy to troubleshoot any ideas you have.

Ah bummer. Can you send me your OBD logs and I'll try to see where it's getting hung up: https://sidecar.clutch.engineering/help ... -scan-logs

@jeff just emailed them over

One thing I'm noticing with your scanner so far is that it's not responding to the ATCRA7EC command, which is a pretty standard OBD command introduced in v1.4b models of the ELM327 chip. This matches up with the reported ELM327 version of your scanner, which is only v1.3a. The v1.4 chips notably introduced support for extended addressing mode for CAN protocols, which might be why your scanner is having a hard time chatting with your car.

The scanner model you're using should arrive at my house tomorrow, so I'll be able to test the hardware out, but in the meantime I'm suspecting the most likely next step here is that you might want to consider getting a scanner running a more modern chipset. https://sidecar.clutch.engineering/scanning/ has the scanners I've tested with Sidecar so far.

Going to keep digging into your logs.

Another thing I'm noticing is that your car is responding with different supported ECUs across different scanning sessions. This is sometimes due to the state of the car when your scanner connects. A test we can try:

1. Make sure your car engine is on, then plug in your scanner and connect to it with Sidecar.
2. Run the following commands in a new Terminal session:

0100

This will either return a packet starging with 7EE or 7EC. 7EC is the one that reports that it supports more parameters.

After running the above, then run the following to see if we can talk to your ECUs:

ATSH7E4
0131

This should return a valid "distance since DTCs cleared" response. If not, start a new terminal session and try the more general version of this:

ATSH7DF
0131

This essentially asks any OBD-II-capable ECU in your car to respond. We'll be able to use the responses to see which ECUs are talking to us.

I downloaded the app and have been testing it. I see the amount of charge left as well as tire pressure and other parameters. When I use CarPlay and use the app, all I see is just raw data. I can see the trip on the map but I dont see any data being overlayed. Am I doing it wrong?