[ErickF]

The VIN range is WVGFMPE24MP000559 to WVGUNPE27MP066592. All 2021 ID.4s are included. I'll explain... this is based on VW's 2021 VIN Decoder Card available through erWin.


W - Country of Origin: Germany
VG - Manufacturer: VW Europe SUV / MPV
F through U - Series: (such as First Edition, Pro, Pro S, etc)
M/N - Engine: (M = RWD, N = AWD)
P - Restraint: Side & Side Curtain Airbags
E2 - Model: ID4. SUV
4-7 - Check #
M - Model Year: 2021
P - Assembly Plant: Mosel (Zwickau-Mosel)
000559 to 066592 - Production Sequence (resets for each model, each year)

You'll notice the VIN range shows the following values unchanged:
W - Country of Origin: Germany
VG - Manufacturer: VW Europe SUV / MPV
P - Restraint: Side & Side Curtain Airbags
E2 - Model: ID4. SUV
M - Model Year: 2021
P - Assembly Plant: Mosel (Zwickau-Mosel)

Only the following vary:
F through U - Series: (such as First Edition, Pro, Pro S, etc)
M/N - Engine: (M = RWD, N = AWD)
4-7 - Check # (this is just a checksum so they know a VIN hasn't been tampered with)
000559 to 066592 - Production Sequence (resets for each model, each year)

So, the recall will apply to all 2021 ID.4 built in Emden, regardless of trim level or drivetrain configuration, as long as the production sequence number is between 559 and 66592. (I'd wager that's all of the 2021 production, btw!) Of those 60k, the 20k that came to US are the ones that are affected by this US recall; the 40k sold in other markets will have to be handled in those markets... this is only a US recall that we're discussing.

Presumably the 2022 cars have updated firmware in port before delivery and so are not affected.

2021 First Editions are WVGD* which would precede the range of VIN's.

 

[Aspen318]

The failure incidence on the BMW motorcycle model I referenced was much lower. My only point is it would seem companies let their legal and finance arms make the decisions on “Do Not Drive” and I’m not sure they factor the customers interest in the equation.

 

[d287]

2021 First Editions are WVGD* which would precede the range of VIN's.

Interesting… never found a good list of those fourth position trim level codes for the ID.4.

 

[Neil]

2021 First Editions are WVGD* which would precede the range of VIN's.

Incorrect - recheck your VIN. . The 4th character ("D" for FE) isn't relevant. It's the last 6 digits, the "Production Sequence", that applies to the recall coverage. This recall includes 100% of ID4s sold into the USA market, and produced in the range of 000559 to 066592.

 

[ErickF]

I wonder if these modules were manufactured specifically for the US market (or the firmware coded specifically for the US).

Per the range of VIN's, First Edition models are excluded. We sometimes consider First Editions as "German versions" or "Frankensteined" from available parts at time of manufacture.

 

[ErickF]

This recall includes 100% of ID4s sold into the USA market

It doesn't. The email sent from VW specifically states "certain 2021 model year Volkswagen ID.4 vehicles." The NHTSA Safety Recall Report also eludes to this.

If First Editions were included, the range would open with WVGD.

 

[Neil]

It doesn't. The email sent from VW specifically states "certain 2021 model year Volkswagen ID.4 vehicles." The NHTSA Safety Recall Report also eludes to this.

If First Editions were included, the range would open with WVGD.

OK, you can let me know later when you discover otherwise.

 

[Nai3t]

The Tesla caused pile up in San Francisco was the result of similar behavior

BIG difference between a car losing population and coasting to a stop vs. a car autonomously changing lanes and mashing on the brakes. Not that I'd want to be driving either car – but I assume in the Tesla case the driver at least had the opportunity to take over?

 

[rhhousehold]

 

[wetlands1443]

BIG difference between a car losing population and coasting to a stop vs. a car autonomously changing lanes and mashing on the brakes. Not that I'd want to be driving either car – but I assume in the Tesla case the driver at least had the opportunity to take over?

I shouldn't have brought up the example because they are different, the tesla is hitting the breaks, where I assume the ID.4 would just coast, but at least the driver would have a chance to respond. I know my vehicle isn't impacted, but it just makes me regret giving VW any money at this point. Hopefully this is the start of them taking their vehicle seriously and things get better from here.

 

[Nai3t]

It’s near the end of the NHTSA document - only 32 issues with pulse inverter. (That’s the thing that causes the “stall”) I believe 3 of them are on this board.

Can you screenshot it? I don't see it in either document. This to me like most of is not all of the '21s.

 

[rhhousehold]

Found it. In OBDeleven it is the drive motor, module 51. Its called MEB.inv4.0 internally and the software version matches (6044)

So people can check this themselves with OBDeleven or carscanner

The reason I ask is because just a month ago I took mine in to dealer for the same issue — sudden loss of power and coast to stop on busy freeway.

Dealer opened case with VWOA technical support and they said to replace the A19 inverter. Seems like a shot in the dark to me. They would have known at the time that this SW issue was the culprit? And didn’t want to do nothing so replaced a part?

 

[JimmyVW]

@Nai3t they know of 32 cases where it happend uptil now. But how much that number is downplayed or dealers never escalated the customer complaints…

 

[JimmyVW]

The reason I ask is because just a month ago I took mine in to dealer for the same issue — sudden loss of power and coast to stop on busy freeway.

Dealer opened case with VWOA technical support and they said to replace the A19 inverter. Seems like a shot in the dark to me. They would have known at the time that this SW issue was the culprit? And didn’t want to do nothing so replaced a part?

The fix for this issue is in EU software upgrade 2.4 (released july 2022) and the document has clearly stated the issue is known since jan 22. So yeah they knew that the fix would be to upgrade or replace that module in your specific case

 

[d287]

Can you screenshot it? I don't see it in either document. This to me like most of is not all of the '21s.

View attachment 21226

Just go the bottom of that document… they disclose the number of reported issues.

 

[d287]

Also, since they talk about reports from Europe, I suspect the 32 occurrences are out of the full 60k production run, not just the 20k imported to the USA.

 

[Nai3t]

Also, since they talk about reports from Europe, I suspect the 32 occurrences are out of the full 60k production run, not just the 20k imported to the USA.

Ok, then this is where you're losing me... you're taking about 32 instances, but up above you were talking about # of affected vehicles – I assume you're referring to vehicles affected by the recall?

Only 32 of the 20,000+ vehicles affected have the potential stalling issue

 

[Nai3t]

The fix for this issue is in EU software upgrade 2.4 (released july 2022) and the document has clearly stated the issue is known since jan 22. So yeah they knew that the fix would be to upgrade or replace that module in your specific case

So again, if that's the case, why would they suspend an active software update campaign that was addressing this issue? Not adding up.

 

[ErickF]

I think the 32 (and 384) figure can be inferred from this section. The definition of "Fault entries" is somewhat of a mystery to the average Joe. Does it mean a code that is thrown or the number of times the issue has been documented?

Prior statements in the chronology seem to infer number of occurrences in the field:

 

[Nai3t]

I think the 32 (and 384) figure can be inferred from this section. The definition of "Fault entries" is somewhat of a mystery to the average Joe. Does it mean a code that is thrown or the number of times the issue has been documented?

View attachment 21228

Prior statements in the chronology seem to infer number of occurrences in the field:
View attachment 21229

Ah! Got it, thanks.

So of some sampling of actual ID.4s whose owners either reported a related-sounding problem, or whose data was pulled during a service visit and then later culled, looking for a specific fault, these are the numbers they flagged. In other words, a fault that looks like it might have been caused by this recall condition.

Without the missing sample size or collection methods information, this doesn't tell us much of anything... other than that the condition exists in some non-insignificant number.

I'd like to think our connected cars can report this sort of data real time or at least on demand, once they know what fault they're looking for.

I'm not worried, but I am disappointed.