Volkswagen ID Forum banner

Service Action 97FY is kaput!

17484 Views 170 Replies 52 Participants Last post by  nan7
Image from FB group:

Font Parallel Paper Document Paper product
See less See more
  • Wow
  • Angry
  • Like
Reactions: 5
1 - 3 of 171 Posts
An optimistic guess - They needed a sample update from a few ID.4s for each possible configuration, and they received enough samples to go re-work the update process for a broad release. That combined with a rumored US based update server.

Or I'm in denial that they could go 90% of the way there and give up...
  • Like
Reactions: 5
I think there is a lot of truth to this.
I hope your right
If we play the numbers game, what was it something like 100k 37k ID.4s that need a dealership visit? (FE, 2021s, a few 2022)
Some random website says there's 637 VW dealerships.
And the updates take "1 day". That's 157 58 cars per dealership, so 58 days to perfectly update them all.

Less optimistically, assume half of the dealerships have space/equipment/techs to perform updates, and the average update duration becomes 2 days per car. That's 2 years 4 months of updates...

So my guess - the update needs to take less "tech time" for them to proceed. Swap the 12v in the bay in 15 mins, put the VIN into a website, pick a USB out of 20 variants, and plug it into the car in the parking lot for 12 hours, customer picks it up the next day if the screen shows green.

At least that's how I'd do it, but the software I roll out doesn't touch hardware or need people to deploy it lol
  • Like
Reactions: 4
Can't be done.

As per Chris of Batterylife regarding 2.4 - the mandatory step on the way to 3.0 in Europe - the update has several parts, which need to be installed one by one, verifying every step and should something go wrong, the whole process needs to be re-started. So a tech needs to baby-sit the whole update. And there is a non-zero risk of bricking a module when doing the update.
Why not? I'm referencing what could be, not what's currently done. No reason you can't install an update in chunks, retry when necessary, and report faults back to the mothership & techs for manual diagnosis. Unless someone needs to pull out a wrench and flash a module on the bench, I can't see a good reason they can't make this process more stable. However, plenty of reasons an org wouldn't - missing competencies, poor or inconsistent decisions, risk vs reward, time and/or money budget, etc. I find this problem fascinating hence my speculation.

Everything else is baseless speculation and hand-wringing.

I spent decades developing large, complex software systems. My guess is that their upgrade process is not idiot-proof [...]
Speculation can be fun if it's not wrapped up in feelings or pushing opinion as fact!

I'm approaching a decade in large software systems, definitely agree with you that the process is likely not stable enough. If you have N 'modules' that each have M variants you're looking at exponential configurations. A great number of those can likely be grouped into one flow, and I'd bet big that VW knows exactly which modules are in every car. However, understanding what/why each module variant can fail is a different beast. Even in the edge case configurations that fail, I don't see why the updater script can't phone home and have someone outside the dealership deal with the hard problems remotely. I hear stories about service techs calling vw tech support, who say "idk try again". Where are the engineers pouring over data?
See less See more
  • Like
Reactions: 3
1 - 3 of 171 Posts