Charged up at EA - had to tow Kona

[echeck]

Well, my car is ready to be picked up. Want to know what they did??

**drumroll**

NOTHING.

They literally did nothing. They had it for 27 days, drove it for 65 miles, and are now giving it back to me three days before the 30 day mark so as to avoid my Lemon Law claim.

I can’t believe this crap. So not only did they not resolve my issue, but they are giving the car back to me after admitting there is an issue and intentionally not doing anything about it so as to avoid the golden 30 day Lemon Law rule.

 

[doggyworld]

WTF? How did they even fix it then?

 

[echeck]

WTF? How did they even fix it then?

Great question.

They didn’t. They just released the car to avoid the 30 days. Because if they had it for 30 days Hyundai would have had to buy back my Kona.

I spoke to a lemon law attorney in my state a couple of hours ago. He said I don’t really have a choice but to pick up the car, and then to hope the error happens again. Said I (or even he) could argue that the issue isn’t actually resolved, but Hyundai could easily claim they just weren’t able to replicate it and that according to the information they have the issue has been resolved.

So I’ll be picking the Kona up today and doing everything in my power to brick it again.

 

[Tomek]

You shouldn't write it at all, because if they accidentally read it ... ;-)

 

[echeck]

You shouldn't write it at all, because if they accidentally read it ... ;-)

I’m not worried about that, because I’ve already told the Hyundai rep everything I’ve said here. She knows my goal is now to reproduce the error.

 

[KiwiME]

According to unreliable sources on the local FB group about 10 Konas have exhibited this error here so-far out of approx 800 on the road in NZ. One is getting a new battery, no word on the outcome of the others. It does seem that the BMS checking functions have a hair trigger and I have to wonder if a relatively-new update awaiting me "00D118 BMS improved monitoring logic" has anything to do with this.

 

[mannimagus]

According to unreliable sources on the local FB group about 10 Konas have exhibited this error here so-far out of approx 800 on the road in NZ.

India numbers are nearing 80 odd bricked Konas out of around 500 sold. The government bought a bunch of Konas a year ago and no idea how many of those are affected.

 

[ColoradoKonaEV]

Another update:

Still don’t have the Kona back. The technician said he’s had three others before with the same issue. Said with the others he cleared the codes, test drove it, all seemed fine, and released the car back to the owners.

Two of them came back within three weeks with the same issue.

And now Hyundai doesn’t want them to release it back to me. The Hyundai engineers said they want the local guys to drive it until the error comes back, and then capture additional info.

It’s nine days in and I have no idea when I’m going to get the car back.

So I have a rental. It’s one of those old fashioned cars that use fossil fuels to move. Really weird. And really loud.

This just happened to me too. 2021 Kona Ultimate, just 164 miles on it. I was going on a longer trip and charged it to 100% with level 2 charger at home. In the morning it refused to move so I had to take my 2004 XC 90 instead. It was a good reminder why I love this Volvo so much

Can these codes be cleared with OBDII scanner to get the car moving?

 

[electriceddy]

This just happened to me too. 2021 Kona Ultimate, just 164 miles on it. I was going on a longer trip and charged it to 100% with level 2 charger at home. In the morning it refused to move so I had to take my 2004 XC 90 instead. It was a good reminder why I love this Volvo so much

Can these codes be cleared with OBDII scanner to get the car moving?


View attachment 12762 View attachment 12762

Try disconnecting the negative terminal of the 12V battery (using the 10mm socket wrench) for a few minutes, reconnect and see if that clears it up. If it does you are good to go - software hiccup

 

[ColoradoKonaEV]

Try disconnecting the negative terminal of the 12V battery (using the 10mm socket wrench) for a few minutes, reconnect and see if that clears it up. If it does you are good to go - software hiccup

I tried this without success. When it happened 2 days ago, I disconnected it for just few minutes and re-connected it. Today I left it disconnected for 20 minutes. In both cases this did not fix the issue. I will have it towed to the dealership on Monday.

 

[ericy]

I tried this without success. When it happened 2 days ago, I disconnected it for just few minutes and re-connected it. Today I left it disconnected for 20 minutes. In both cases this did not fix the issue. I will have it towed to the dealership on Monday.

If you have SoulEVSpy, run a scan to find the voltages of the individual battery cells.

 

[ColoradoKonaEV]

If you have SoulEVSpy, run a scan to find the voltages of the individual battery cells.

Will do if I find the dongle.

In the meantime I connected an older OBD2 scanner AutoLink AL619. It found a permanent code P0C17 Drive motor 'A' position sensor not learned. I think while I was reading the "Stored Codes" and the "Pending Codes" (which there were none) the error light on the dashboard went away. It found only one permanent code I mentioned above. I tried to erase it and was not able to - it is still there. The car is drivable however.

I wonder if I should still take the car to the dealership. If it drives I am not sure they will do anything.

 

[electriceddy]

Will do if I find the dongle.

In the meantime I connected an older OBD2 scanner AutoLink AL619. It found a permanent code P0C17 Drive motor 'A' position sensor not learned. I think while I was reading the "Stored Codes" and the "Pending Codes" (which there were none) the error light on the dashboard went away. It found only one permanent code I mentioned above. I tried to erase it and was not able to - it is still there. The car is drivable however.

I wonder if I should still take the car to the dealership. If it drives I am not sure they will do anything.

I would take it in and advise them exactly what originally occurred and any steps you might have taken to resolve it. It sounds like the original error may have cleared when hooking up the incompatible scanner.
More info on that very same code here:
https://www.insideevsforum.com/community/index.php?threads/p0c17-position-resolver.6926/
Curious what make/model of EVSE are you using at home when charged to 100%, is this the first time charging on that unit to that level?

 

[ColoradoKonaEV]

...
Curious what make/model of EVSE are you using at home when charged to 100%, is this the first time charging on that unit to that level?

The EVSE is ChargePoint Home: https://www.amazon.com/gp/product/B07WXZDHGV

I have it since October 2019 and had no issues at all charging my old 2019 Kona Ultimate to 100% until they restricted it to 80% at some point this year.
Hyundai is buying back the 2019 Kona and I decided to replace it with 2021 Kona Ultimate. I charged the 2021 Kona from 70% to 100% once and then on the second time from 90% to 100% it showed the error.

 

[hobbit]

That P0C17 resolver code is always present, depending on what kind of scantool you have,
and is unrelated to the battery woes.

_H*

 

[ColoradoKonaEV]

Today I surrendered my 2019 Kona Ultimate. The whole process was fast and painless. The guy took pictures and inspected the car, I signed some forms and got the check.

While I was at the dealership I scheduled a service appointment for the "Check electric vehicle systems" problem for the 2021 Kona. They said they needed to keep the car for couple of days. I asked for a loaner car and was told they could not provide one because they already had too many cars in service for which they provided loaner cars?! This does not seem right to me. I could not find anything on the dealership's site or Hyundai USA.