PCM version tracking (and their differences)

[alex_bell]

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.

Yes, i expressed myself wrong. What I meant is that if some data is missing on flexray/can, it simply will not be displayed on PCM screen, maybe some ?? or ** symbols will appear in place of missing data

but absence of data has no impact on overall car performance, just a cosmetical effect

Sponsored

 

[ct14garage]

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

That is one way to put it, another is, it doesn't work because the modules that provide that data aren't even there to begin with

everything else that needs to work, does work though (I am talking features that were already present in 9j1.1)

 

[prj]

Yes, i expressed myself wrong. What I meant is that if some data is missing on flexray/can, it simply will not be displayed on PCM screen, maybe some ?? or ** symbols will appear in place of missing data

but absence of data has no impact on overall car performance, just a cosmetical effect

It's not always just data missing and depends on implementation. Saying it's completely separate is incorrect when the factory requires an integration step upgrade for the software version.

There are quite a few fibex and can changes between J1.1 and J1.2. Remember, the PCM is also responsible for controlling various parts of the car by sending requests to various controllers.
However, as early MY25 cars got delivered with the MY24 PCM version and then upgraded the differences can't be overly dramatic. MY26 is probably worse.

As for what works and does not work, it's not possible to know without testing all the functions. E.g. the combox got updated on MY26 and the hardware is a completely different part with references to upgraded compute, so at least the MY26 software is probably a no-go.

As for how much stuff breaks on a J1.1 when using MY25 software, I don't know, but e.g. battery management/profiles are different and few other things. Obviously data will be missing too. Then is the question of what Porsche Connect will do and so on.

I think Porsche most likely will void your PCM warranty if you try to do this and they collect a VAL.

 

[alex_bell]

It's not always just data missing and depends on implementation. Saying it's completely separate is incorrect when the factory requires an integration step upgrade for the software version.

There are quite a few fibex and can changes between J1.1 and J1.2. Remember, the PCM is also responsible for controlling various parts of the car by sending requests to various controllers.
However, as early MY25 cars got delivered with the MY24 PCM version and then upgraded the differences can't be overly dramatic. MY26 is probably worse.

As for what works and does not work, it's not possible to know without testing all the functions. E.g. the combox got updated on MY26 and the hardware is a completely different part with references to upgraded compute, so at least the MY26 software is probably a no-go.

As for how much stuff breaks on a J1.1 when using MY25 software, I don't know, but e.g. battery management/profiles are different and few other things. Obviously data will be missing too.

Sure, everything can be possible, but from my experience(writing code for other mutlimedia manufacturer) - changes within same model line usually minor and can be even backward compatible

The easiest way to test it - to buy headunit from j1.2 and see whats not working

 

[prj]

Sure, everything can be possible, but from my experience(writing code for other mutlimedia manufacturer) - changes within same model line usually minor and can be even backward compatible

The easiest way to test it - to buy headunit from j1.2 and see whats not working

It's not really the same model line, it's a model line upgrade.
Audi/VAG has a history of completely changing the HU on facelift on various variants.

E.g. 3G+ to MIB2 on Audi A6 C7 and so on.
On Taycan they spent the whole budget on the performance/battery upgrades so the infotainment was mostly left as-is, but it's certainly not a rule for VAG.

 

[BrumPorsche]

I have a MY25 with 4360 and Hardware H9J035070CE. I have no app store but desperately want it for the web browser.
Is there a way to get a 4360 WITH app store??

 

[chun]

I have added PCM Hardware version details to the first post.

PCM hardware version:

• For j1.1 Q4 2019-Q3 2024 latest part number and what it replaces:
  
  
• for j1.2 Q4 2024 doesn't seem to have app store, only Video app.
  
  
• for j1.2 Q1 2025 - Q3 2025 seems to have app store with youtube, etc.
  
  
• for j1.2 Q4 2025 - 2026+
  
  

They don't seem to be installing the latest parts in j1.1 Q4 2019-Q3 2024, even if they have to do PCM hardware replacements. Services/Dealerships don't decide what part goes in.

Which may indicate that there is some hardware discrepancy between BF and DD/DE parts - there for sure is a difference in how they handle the LED lighting inside the car - color wheel vs no color wheel.
More likely that it is a simple difference of what software they come preinstalled with - as both DD and DE come with 4360 installed; while BF comes with 3882 - and porsche wants to keep all j1.1 on 388X software version.

 

[BrumPorsche]

I have a CE unit MY25. So no AppStore. Never ever?

 

[chun]

I have a CE unit MY25. So no AppStore. Never ever?

I think CE is somewhere between BF and DD - and came with 3995 or 4002 preinstalled - later updated to 4360.

I would only speculate on what porsche chooses to do with software in the future, but seeing how things are right now, yes, probably stuck with what you have.

You're not missing that much. Spotify, youtube, browser and maybe 1 single game - all android apps - emulated or virtualized, i assume. Not the end of the world - of course, market dependent.

Performance wise, having driven both 4360 with app store and without, they seem to be just as fast. 4578 is definitely more responsive in the maps though, but beside that, also not that different.

 

[prj]

There are multiple part numbers for "CE":
9J1 035 070 CE
9J1 035 084 CE
9J1 035 086 CE
9J1 035 089 CE
9J1 035 092 CE
9J1 035 136 CE
9J1 035 878 CE
9J1 035 140 CE
9J1 035 877 CE
9J1 035 840 CE
The "CE" suffix controllers are -06.2024 in partslink.
So that's very early MY25.

01.07.2024>> - 24.11.2024 is suffix "DD"
25.11.2024>> - 15.05.2025 is suffix "DE"

And then there is a suffix "C" with a completely different part number that is 16.06.2025>> or MY26.

For J1.1 there is BF suffix.

The only current suffixes are BF, CE, DD, DE, C.
What the hardware number is inside - who knows, because that are just order numbers in the Porsche EPC.

 

[BrumPorsche]

I have a MY25 4S CT
H9J1035070CE
4360
w/passenger screen

Actually, I think there's no hardware changes inside the MY25 units. It's just software. There must be a god damn way to get the app center!!! I am so pissed! YouTube ist kinda ok (web emulated) but ScreenHitsTV is such a BS mess!!!

Could I flash my PCM with the app center version of 4360 with PIWIS?

 

[Shug]

There are multiple part numbers for "CE":
9J1 035 070 CE
9J1 035 084 CE
9J1 035 086 CE
9J1 035 089 CE
9J1 035 092 CE
9J1 035 136 CE
9J1 035 878 CE
9J1 035 140 CE
9J1 035 877 CE
9J1 035 840 CE
The "CE" suffix controllers are -06.2024 in partslink.
So that's very early MY25.

01.07.2024>> - 24.11.2024 is suffix "DD"
25.11.2024>> - 15.05.2025 is suffix "DE"

And then there is a suffix "C" with a completely different part number that is 16.06.2025>> or MY26.

For J1.1 there is BF suffix.

The only current suffixes are BF, CE, DD, DE, C.
What the hardware number is inside - who knows, because that are just order numbers in the Porsche EPC.

My Nov 2020 controller is 9J1 035 070T

 

[prj]

My Nov 2020 controller is 9J1 035 070T

There's a ton of older codes, but only 4 current ones.

 

[chun]

The only current suffixes are BF, CE, DD, DE, C.

I don't think they make CE and DD anymore.

Looked through the ordering menu with the service guy, only BF, DE and C were listed.

The version shown in the software is technically more accurate, as it reflects Porsche's internal tracking, which seems to be by batch/quarter.

I asked what the difference between these hardware's are, and the answer was: no idea .
My own asumption, the difference is what software they come preinstalled with (3882, 4360 and 4578)

Replacing the PCM seems to be a quick job, took less than 2h for my car. Put it in privacy mode, take out old part, put in new part, pair it to VIN with PIWIS. Done, no extra coding.
They do have to gather logs/diagnostic before ordering the part.

 

[Papi95]

Sponsored