Hyundai Kona powertrain components (PCAN)

[Pelland]

Hi Projectgus,

I have had good luck getting diagnostics using an OBDLink LX dongle and this Android app

I got the bluetooth module to try the android app. I must confess I wasn't expecting much as I paid more for shipping than the module.

I have been looking at ScanDoc for a while, but wanted to wait until I at least had something running before parting with lots of money.
On line demo here https://scandoc.online/last/0/32/2/72/3/0

I looked at the OBDLink LX dongle you linked to and it's relatively pricey, compared with the one I have, but less than ScanDoc. However since ScanDoc looks to match the Hyundai software I've decided to buy that. Fingers crossed it's as good as it says.

I think you're right about only UDS. I've run a set of UDS scans from Savvycan and it's found a whole list of addresses that respond.
I'll put them up on github once I've done some more work on confirming which module matches which ID.

Now for some pictures for those interested.

a new look "Battery Kona"

No HV connections yet, don't want to let the magic smoke out too soon.

A most surprising result from first power up.

I was quite surprised by how much came straight up.
Running my scan tools didn't show very much and I wondered why I wasn't getting anything from the BMS or motor.

I had started by putting in one fuse at a time while checking the current draw. When I got to the IG3 fuses that's when everything came to life, with a load warning buzzer.
Then I realized I populated all the main fuses but hadn't got to the fuses in the PCB block.
Added them and current draw increase but still nothing. While looking for an easy place to T into the P-CAN bus I discovered that it doesn't go directly between the main and front loom. It goes right around the car via the floor loom.
After all the rabbit hole mentioned previously I'm now getting lots of good data.

[projectgus]

Great stuff, Pelland! I'm really impressed you got the vehicle to come up in that state.

I have been looking at ScanDoc for a while, but wanted to wait until I at least had something running before parting with lots of money.
On line demo here https://scandoc.online/last/0/32/2/72/3/0

Oh wow, this looks incredibly useful! I had seen one of the more expensive scantools (Autel IIRC) had integrated some Hyundai GDS functions, but ScanDoc looks about 20% the price! I'm very interested to hear how this goes. Being able to run the "actuator tests" and "utility" operations (and maybe CAN log them, haha!) would be amazingly useful. I note the IGPM has an actuator test for "Ignition 3 relay", which might help solve the mystery of when the "EPCU Wakeup" signal changes...

I think you're right about only UDS. I've run a set of UDS scans from Savvycan and it's found a whole list of addresses that respond.
I'll put them up on github once I've done some more work on confirming which module matches which ID.

I had started a partial list of these myself, but I hadn't published it anywhere. I've just put it up on my Kona DBC repo here in case it's of use: https://github.com/projectgus/kona-ev-d ... nostics.md

Some of these may be wrong, for example I've written down UDS IDs for both water pumps at some point but I'm actually not sure the water pumps have UDS functions... Corrections/updates/rewrites welcome.

[uhi22]

I can confirm the both EPCU identifier pairs, the Ioniq uses the same. One for the inverter part and one for the VCU part.
https://github.com/uhi22/Ioniq28Investi ... munication

[Pelland]

Hi ProjectGus,
I found your UDS list when I went to download the latest version of your DBCs, Great resource thanks.

I'll rescan the waterpumps directly an see if they respond

I've been playing with the Airbag module as I'd like to work out what's needed to clear the crash symbol on the dash. I might want to use the dash in my conversion, once I work out what that is.

I have found that the Airbag module talks mainly on C-CAN with a single once per second message on P-CAN, That one is already in the DBC.
a UDS scan only gets responses from P-CAN (Two addresses), nothing from C-CAN. Odd since it's C-CAN is where the main message activity is.

Send 0x7D2 response 0x7DA. Send 0x7F1 response 0x7F9.
Notes and logs on Github https://github.com/Pelland-Coupe/EV_Hac ... g%20Module

Looks like I have 12 DTCs but they don't match the GSW DTM list. More work to be done if my scan tool arrives.

[Pelland]

I've written down UDS IDs for both water pumps at some point but I'm actually not sure the water pumps have UDS functions

I've just run a UDS scan on the BMS EWP and yes it does respond - send 0x715 reply 0x71D. Nothing in the generic range seems to be supported but could support some vendor specific. Logs here https://github.com/Pelland-Coupe/EV_Hac ... s/UDS-scan

[projectgus]

Thanks for sharing those logs, I'll add the UDS IDs to the table.

I've been playing with the Airbag module as I'd like to work out what's needed to clear the crash symbol on the dash. I might want to use the dash in my conversion, once I work out what that is.

FWIW if an airbag has deployed then you probably won't be able to clear the "crashed" signal via diagnostics. Manufacturers typically require the Airbag ECU to be replaced after deployment.

You could probably spoof the messages though, and figure out which bit to clear in the message so the warning goes away. The airbag also sends a PWM "crashed" signal to the BMS on a dedicated wire (Fakon has an implementation of this).

[uhi22]

Found a video which explains the PCAN messages to and from the VESS (virtual engine sound system).


And the related GitHub, also containing some connector pinouts
https://github.com/ereuter/vess

[Pelland]

My ScanDoc module has arrived and a quick test seems to show it's as good as the online demo.
No problems listing DTCs from BMS & VCU. Open/close contactors, read VIN etc.

FWIW if an airbag has deployed then you probably won't be able to clear the "crashed" signal via diagnostics.

Yes I was aware of that, I was looking to see what I needed to spoof to clear the dash. I have seen a couple of places advertising to re-write Airbag modules to clear the issue. Probably accessing the firmware directly is my guess.

What I thought was a "Crash" indication on the dash is actual indicating that the forward collision detection isn't working. Hardly surprising since none of it is plugged in. Funny what you can find if you RTFM.

Anyway if anyone has any specific diagnostic tests they would like a CAN log please let me know.

[Pelland]

I've captured some logs for running ScanDoc diagnostics against MCU, VCULDC, and IGPM for anyone interested.
https://github.com/Pelland-Coupe/EV_Hac ... us/ScanDoc

I'm very please with the ScanDoc tool so far.