PCM version tracking (and their differences)

[chun]

My MY25 came in September 2024 with a not mentioned version: 4338.

The most notable difference for me after the update to 4360 is, that there is no way to restart the PCM anymore. With 4338 I could still do the two finger engineer mode reset thing.

I will add it as an intermediary version.

Tehnically there is also a 39xx and a 40xx version between 3885 and 4338, but I haven't seen them installed to anyone, just in PIWIS.

Sponsored

 

[Flying ace]

You are doing god's work

 

[Shug]

3885 is only for customers who complain about connectivity or rebooting PCM. I have a feeling you suddenly have connectivity issues. You should call OPC tomorrow.

Thanks Jasper,

My Taycan is in for a 12V battery software recall next week, so have complained about the poor connectivity with Octopus and asked for the PCM to be updated, will report back on how well the request went down.

 

[vhardono]

Thanks Jasper,

My Taycan is in for a 12V battery software recall next week, so have complained about the poor connectivity with Octopus and asked for the PCM to be updated, will report back on how well the request went down.

would you be able to share the labour cost if you manage to get it updated? thanks!

 

[chun]

would you be able to share the labour cost if you manage to get it updated? thanks!

It’s covered by warranty / porsche approved.

Otherwise, the update itself takes 25min; so realistically if you don’t have warranty / cpo and need to pay, it’s 50% of whatever their hourly rate is

 

[tonykara]

3885 is only for customers who complain about connectivity or rebooting PCM. I have a feeling you suddenly have connectivity issues. You should call OPC tomorrow.

I like this thread. Why are they opposed to pushing over the air (OTA) updates globally to fix things? What sections of the system are even capable of OTA, and what sections can only be performed by the dealership (or other capable entity)?
My ''22 had 3882, but it was doing so much stupid crap and I caught all of it on video, the dealership updated me to 3885 (after previously telling me 3882 was the latest. I wonder how it could have ever shipped with 3882 consider how flawed it was. Now I've got the map routing doing REALLY DUMB things. I'll probably go search for that topic here.

 

[GreenHornet]

It will be interesting to see if the rumored J1.1 PCM update to fix the navigation issues will homologate the 3xxx and 4xxx branches to one. Highly doubt it but one could always hope.

Keep up the good work @chun

 

[WalterM]

I will add it as an intermediary version.

Tehnically there is also a 39xx and a 40xx version between 3885 and 4338, but I haven't seen them installed to anyone, just in PIWIS.

My appointment with the dealership was cancelled: "Porsche is still working on a solution". Maybe somwhere in April.
In the meantime feel free to use Apple Maps which links now to your car and battery level."
... worked OK for one week.

 

[Gkwan]

Thanks for the job @chun !
In case it helps, I complained before buying my used MY20 Turbo (no Android Auto), they delivered me a 3885, and I haven't had a single problem since ~2 months (haven't used much the internal GPS though, mainly Maps)

 

[Murph7355]

I like this thread. Why are they opposed to pushing over the air (OTA) updates globally to fix things? What sections of the system are even capable of OTA, and what sections can only be performed by the dealership (or other capable entity)?
My ''22 had 3882, but it was doing so much stupid crap and I caught all of it on video, the dealership updated me to 3885 (after previously telling me 3882 was the latest. I wonder how it could have ever shipped with 3882 consider how flawed it was. Now I've got the map routing doing REALLY DUMB things. I'll probably go search for that topic here.

I'm guessing they don't want to do further updates for similar reasons to CT14's experience.

Spend a chunk of time updating the s/w, only to brick the h/w. Then they have that to replace too.

3885 does not splve the navy rebooting issue. Categorically.

From day 1 they've been on the back foot with the s/w side of the car and are seemingly no closer to getting a grip of it. Really poor for such an expensive product.

 

[Shug]

would you be able to share the labour cost if you manage to get it updated? thanks!

Car came back this afternoon for the recall at Porsche and despite emailing and also telephoning the workshop manager to advise there was poor connectivity with Octopus, the car has come back with no visible changes to the any of the software components or version numbers

 

[alex_bell]

Hardware is one thing but you have to keep in mind that J1.2 has a bunch of different controllers and things in it that don't even exist on J1.1.
There might be some surprises. The upgrade for J1.2 lists a lot of different control modules that have to be updated (integration step) to go up in software version safely, but many of those updates don't exist for the J1.1 or the module doesn't exist.

So I would not take it for granted that the J1.2 version just works as-is on a J1.1.
I'm sure the PCM will boot but there could be issues with functionality.

99% its not a case

PCM runs its own software, totally separated from other control units. So as long as package IDs remain the same(which I think it is) - you'll be fine

What I think is that you possibly can even upgrade(retrofit) PCM from newer version(newer HW) and it should run just well

I'm not sure if upgrading j1 units to j1.2 SW worth, because I suspect laggy j1 units will become even more laggy with 4xxx software revision. Same as when you install new IOS version to older phone - it just gets a bit slower

If anybody wants to sponsor this, I could try to find headunit with newer HV revision and install it to my j1 car

 

[prj]

99% its not a case

PCM runs its own software, totally separated from other control units. So as long as package IDs remain the same(which I think it is) - you'll be fine

Completely disagree, there is something called an "integration step".
The upgrade TSB's make multiple requirements towards having the same "integration step".

This is because the flexray/can matrix can change depending on the integration step, and for everything to work correctly all the controllers have to be on the same integration step.

If anything changes in the fibex version the controllers can't "talk" anymore, that includes the PCM. It can miss data from other controllers and input/output it in the wrong format.
Whether that is the case or not I don't know, but saying it's completely separate is not right.

Also, there are no significant hardware differences until MY26. Everything older than that essentially boils down to the same part. This is also why the replacements on MY20-24 with the MY25 style controller had zero effect on the crashing. It's a software problem.

 

[ct14garage]

This is because the flexray/can matrix can change depending on the integration step, and for everything to work correctly all the controllers have to be on the same integration step.

It works just fine, granted some data in certain apps and places doesn't display and shows ?? / ?? Instead but this is obvious since 9J1.1 doesn't even have those functions

the only problem is that the already high stakes of bricking just about double with this update

normal update of 9j1.1 pcm about 3/10 brick at most.... upgrading to 399X (which is the gateway to 43XX) bricks about 2/3 of the units consistently

 

[prj]

It works just fine, granted some data in certain apps and places doesn't display and shows ?? / ?? Instead but this is obvious since 9J1.1 doesn't even have those functions

Yeah, it doesn't show because the can/flexray matrix is wrong, and the software is wrong.

Sponsored