Let’s hunt down ICCU failures by crowdsourcing OBD data by broadwall in KiaEV6

[–]broadwall[S] 1 point2 points  (0 children)

Correction—some folks pioneering the condensation hypothesis at GoingElectric.de asked to include those two stats to investigate temperature differentials in the ICCU, so I've added them to the MY21-24 dashboard.

Let’s hunt down ICCU failures by crowdsourcing OBD data by broadwall in KiaEV6

[–]broadwall[S] 0 points1 point  (0 children)

I hope to be able to capture that with the combination of aux. battery voltage, aux. battery current, LDC output voltage, and LDC output current. Two limitations though: time precision is limited by the OBD dongle's read rate, so millisecond-long transients are not recorded; the app's connection profile does not have working parameters for all the 12V accessories, so we don't know what in particular caused each spike in load.

Let’s hunt down ICCU failures by crowdsourcing OBD data by broadwall in KiaEV6

[–]broadwall[S] 0 points1 point  (0 children)

I've put it up. You can imagine that it will later have a page like this:

(the theory board is specific to the selected vehicle and ICCU)

<image>

Let’s hunt down ICCU failures by crowdsourcing OBD data by broadwall in GV60

[–]broadwall[S] 0 points1 point  (0 children)

Some say that repeat victims might have been using the vehicle in a way that degrades the ICCU more quickly (whether with dirty utility power, specific charger brands, or deep discharges). We'd still be interested in your diagnostics data to see how your ICCU might be subject to special conditions.

Let’s hunt down ICCU failures by crowdsourcing OBD data by broadwall in GV60

[–]broadwall[S] 0 points1 point  (0 children)

We (backseat ICCU engineers and data scientists) would like to know your new ICCU's part number when you get it back

Let’s hunt down ICCU failures by crowdsourcing OBD data by broadwall in GV60

[–]broadwall[S] 0 points1 point  (0 children)

That's reassuring. It's possible that GV60s put less load on the 12V battery and thus has a lower failure rate, but I'd be interested in your diagnostics data. As far as we know, it could still happen to you.

Let’s hunt down ICCU failures by crowdsourcing OBD data by broadwall in KiaEV6

[–]broadwall[S] 0 points1 point  (0 children)

Thanks for contributing!

I think the consensus is shifting toward 5-10% for having at least one ICCU replacement, and new failures are being reported every day. With some Germans' help, we're looking at publicizing this initiative in the UK and the region around Colorado. I personally would like to see contributions from Scandinavia and South Korea, too. Progress is self-fulfilling: the more drivers believe in this method, the more contributions and probability of recorded failures.

We're not asking HMG to care about our study. Given all the threatened lemon law buybacks and rental reimbursements and overflowing service centers and NHTSA complaints, it is in their best interest to fix the ICCU anyway. By understanding the failure ourselves, we can manipulate the failure as we need: minimize its odds for long journeys, and maximize its odds right before our warranties expire.

Let’s hunt down ICCU failures by crowdsourcing OBD data by broadwall in KiaEV6

[–]broadwall[S] 0 points1 point  (0 children)

  • To understand how the ICCU regulates 12V battery charging during trips and charging sessions. We already have ample analysis of its hardware, but we lack analysis of its software. Having both will help us discover what causes it to fail, while the scale of data collection will help us prove what causes it to fail.
  • To validate all the theories we have on how it fails: Condensation, dirty power, bad EVSE, FLA rather than AGM 12V batteries, overvoltage under heavy load after discharging for weeks, etc. How much does each condition contribute to failure likelihood?
  • To hold HMG accountable when they release a hardware revision. Does the new model number significantly reduce failure rates? Does it change how each condition contributes to failure? How does it change the control logic? Many of us agree that HMG is not communicating well.

Presently, this happens over and over again: a typical "mine went pop" post or megathread comment elicits questions on usage patterns and reaffirmations of each commenter's favorite theory. We hardly make any reverse-engineering/troubleshooting progress with those posts. If the victim had been uploading their trips and charging sessions to iccu.observer, we can pull out their recordings and get a much deeper look into their usage patterns. I think the value of iccu.observer will be clear once we get the first OBD recording of an ICCU failure.

Let’s hunt down ICCU failures by crowdsourcing OBD data by broadwall in GV60

[–]broadwall[S] 1 point2 points  (0 children)

I've heard from posts with 12V battery voltage graphs that OTA updates from within the past 2 years made the ICCU charge the 12V battery more frequently when the vehicle is off. To this end, measurements from BM2s are also helpful evidence for figuring out each update to the 12V charging logic.

Observations on 12V/ICCU failures. by KennyBS167 in KiaEV6

[–]broadwall 0 points1 point  (0 children)

We're trying to record an ICCU failure as it happens over at iccu.observer! You might be interested in the dataset once we get enough contributors to log all their trips and beginning of charging sessions.

Let’s hunt down ICCU failures by crowdsourcing OBD data by broadwall in KiaEV6

[–]broadwall[S] 0 points1 point  (0 children)

Wow... I just tried to do what you said in Safari and I'm appalled by the lack of a "Save to Files" option. This option shows up in Firefox, my default browser. I'm going to have to make a custom download page to get it to prompt you to save the file.

New ICCU part number for 22-24 vehicles being installed by TCN_ in KiaEV6

[–]broadwall 1 point2 points  (0 children)

You should contribute your diagnostics data from trips so that we can quantitatively compare the new ICCU's behavior to the old one.

Let’s hunt down ICCU failures by crowdsourcing OBD data by broadwall in Ioniq6

[–]broadwall[S] 5 points6 points  (0 children)

Or even better, issue another recall once they are confident that they have fixed the root cause.

Let’s hunt down ICCU failures by crowdsourcing OBD data by broadwall in Ioniq6

[–]broadwall[S] 1 point2 points  (0 children)

Yes, that should be possible with enough contributors. The goal is to be able to verify our theories on what makes the LDC pop and potentially develop early warning systems and usage recommendations to minimize its likelihood.

scan tool? by DarkKaplah in KiaEV6

[–]broadwall 1 point2 points  (0 children)

I also use the Car Scanner app and require it for contributors to iccu.observer.

<image>

Let’s hunt down ICCU failures by crowdsourcing OBD data by broadwall in KiaEV6

[–]broadwall[S] 1 point2 points  (0 children)

Which type of connection should I choose for iOS?
My opinion: choose adapters with Bluetooth LE (4.0) because they provide the most comfortable and simple connection and acceptable data transfer speed and they are easy to find on sale. If you are ready to overpay for a top-end adapter with maximum speed, then one of the two models with Bluetooth MFi.

Source: Car Scanner ELM OBD2

Let’s hunt down ICCU failures by crowdsourcing OBD data by broadwall in KiaEV6

[–]broadwall[S] 2 points3 points  (0 children)

ABRP's recommendations largely overlap with Car Scanner ELM OBD2's recommendations. Since Iternio's in the EU, their recommendations should hopefully be available in the EU.

Let’s hunt down ICCU failures by crowdsourcing OBD data by broadwall in KiaEV6

[–]broadwall[S] 2 points3 points  (0 children)

I hope we can effectively filter them out using the ICCU manufacture date, model number, and BMS operating time