When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
992.2s will be more difficult to code because they all now have Vehicle Diagnostic Protection, which is a byproduct of new EU Cybersecurity regulations (also the reason the 718 Boxster and ICE Macan are no longer available). Even resetting the service history (eg after an oil change) is 'locked'. Like all things surely ppl will 'figure it out', but seems like it will take some time.
Originally Posted by siberian
Just a thought but were those items available on the 2019 991.2 meaning if not the cluster may not be able to display them?
siberian
Originally Posted by rnlst_log
Cluster may need to be firmware updated/upgraded to accommodate the function.
I managed to solve it.
The error i posted - "F-TAB coding rules evaluation" is related to PIWIS not being able to find coding rules file for instrument cluster which has been updated by the dealer to the newer firmware version (0237). The older PIWIS does not have coding rules for instrument cluster with such new firmware version (0237).
It's probably because the dealer used newer PIWIS software than i have used, while performing some sort of firmware upgrade/service campaign on the instrument cluster ECU . Therefore the instrument cluster had higher firmware version than the older PIWIS is capable of supporting.
I've updated the PIWIS to newer 24' release and i was able to successfully code instrument cluster and all other units without encountering any kind of issue
PS. Did anyone attempt to change the region? I was able to code Traffic Sign recognition.. i can see options in the PCM but it seems to be off. I found out it's region locked and it's off in certain countries, including mine. Can region be changed using maintenance of vehicle data? (F7) Will it impact vehicle language in the cluster/pcm?
Could you please share how you did it if you can. Using piwis? It's kinda hard to believe or maybe you got some newer MY that allows for these changes to be persistant.
I even asked the guys on russian piwis telegram channel, but also no working solution ))
All the options commonly mentioned here (DME codes editing or even gateway (stop prohibition)) are resulting in car restoring codes back to default on the next start. At least in my MY20. I tried doing that using Launch X431 and PIWIS 3.
with the launch x431 many of the code values I want to change fail to write(2022 turbo s), for instance there a 3 coding values in the DME code for *** but only one will allow a change. does piwis have the same limitations?
I managed to solve it.
The error i posted - "F-TAB coding rules evaluation" is related to PIWIS not being able to find coding rules file for instrument cluster which has been updated by the dealer to the newer firmware version (0237). The older PIWIS does not have coding rules for instrument cluster with such new firmware version (0237).
It's probably because the dealer used newer PIWIS software than i have used, while performing some sort of firmware upgrade/service campaign on the instrument cluster ECU . Therefore the instrument cluster had higher firmware version than the older PIWIS is capable of supporting.
I've updated the PIWIS to newer 24' release and i was able to successfully code instrument cluster and all other units without encountering any kind of issue
PS. Did anyone attempt to change the region? I was able to code Traffic Sign recognition.. i can see options in the PCM but it seems to be off. I found out it's region locked and it's off in certain countries, including mine. Can region be changed using maintenance of vehicle data? (F7) Will it impact vehicle language in the cluster/pcm?
What version did you upgrade to?
Changing region is tricky as there are dependencies in myriads of modules but you can start in VoF and see which ones from there could be affected. You'll need to AutoCode those changed modules and they might revert some changes you've made.
I managed to solve it.
The error i posted - "F-TAB coding rules evaluation" is related to PIWIS not being able to find coding rules file for instrument cluster which has been updated by the dealer to the newer firmware version (0237). The older PIWIS does not have coding rules for instrument cluster with such new firmware version (0237).
It's probably because the dealer used newer PIWIS software than i have used, while performing some sort of firmware upgrade/service campaign on the instrument cluster ECU . Therefore the instrument cluster had higher firmware version than the older PIWIS is capable of supporting.
I've updated the PIWIS to newer 24' release and i was able to successfully code instrument cluster and all other units without encountering any kind of issue
PS. Did anyone attempt to change the region? I was able to code Traffic Sign recognition.. i can see options in the PCM but it seems to be off. I found out it's region locked and it's off in certain countries, including mine. Can region be changed using maintenance of vehicle data? (F7) Will it impact vehicle language in the cluster/pcm?
I attempted to do this on my 982 and failed. Only 982 outside the US had the TSR option. It could different on 992 since the NAV Map could be TSR enabled. TSR is region based. There are a few settings to enable like Hybrid mode and the front camera. There is no documentation for Porsche so I researched the Audi and VW forums. Good luck
Changing region is tricky as there are dependencies in myriads of modules but you can start in VoF and see which ones from there could be affected. You'll need to AutoCode those changed modules and they might revert some changes you've made.
Keep us posted
siberian
I upgraded to 42.400 from 41.5, 42.4 is 2024 release, i think 04/2024. 41.5 is 2022 release.
Yes i'm aware of reverting changes & autocoding. I read many technical bulletins of Porsche and it seems that standard procedure on all kinds of retrofits is to modify vehicle order and then autocode ALL modules. Some people tend to code few modules only, no idea why. I guess it's for safety reasons.
Originally Posted by 718socal
I attempted to do this on my 982 and failed. Only 982 outside the US had the TSR option. It could different on 992 since the NAV Map could be TSR enabled. TSR is region based. There are a few settings to enable like Hybrid mode and the front camera. There is no documentation for Porsche so I researched the Audi and VW forums. Good luck
Thanks for letting us know. Perhaps it will save some time.
PS. I recommend everyone to get a proper power supply or use hybrid car charger that can act as power supply (such as victron chargers). Most of the typical car chargers are not acting as power supplies and lack current. Power draw for 992 with ignition on and lights on is easily 25-30A+ with no ongoing coding. Porsche alone recommends 90A power supply.
For what it’s worth, I did change the Speedo needle to red and removed the boost gauge from the far right display where I couldn’t see it. Also recalibrated the Speedo to read real speed but didn’t bother with coolant temp. Made the sports response button 30 sec. Looks like boost gauge can be extended beyond 1.6 bar and g-meter beyond 1g and 1.2g for modified cars. Got *** to stay off in normal drive mode for a few drive cycles via AC code but it reengaged again after playing around with the AC. on the PCM. I think it may be possible to keep it off as long as you keep AC on, which I do all year round.
I upgraded to 42.400 from 41.5, 42.4 is 2024 release, i think 04/2024. 41.5 is 2022 release.
Yes i'm aware of reverting changes & autocoding. I read many technical bulletins of Porsche and it seems that standard procedure on all kinds of retrofits is to modify vehicle order and then autocode ALL modules. Some people tend to code few modules only, no idea why. I guess it's for safety reasons.
Thanks for letting us know. Perhaps it will save some time.
PS. I recommend everyone to get a proper power supply or use hybrid car charger that can act as power supply (such as VICTRON IP22 REV2 15-30A). Most of the car chargers are not acting as power supplies and lack current. Power draw for 992 with ignition on and lights on is easily 25-30A+ with no ongoing coding.
Yes someone from Germany drove to another country (I think it was Poland) the TSR would stop working. So it is definitely region based and dependent on the NAV Map.
with the launch x431 many of the code values I want to change fail to write(2022 turbo s), for instance there a 3 coding values in the DME code for *** but only one will allow a change. does piwis have the same limitations?
I also got launch. I spend really long time reseraching how to disable *** in my 2019 992 MY 2020 using PIWIS or Launch. I believe it's not possible to disable *** via simple manual coding. I heard rumours that it can be done with porsche network access and newest PIWIS 4+, but it's only a rumour.
All the changes you make in PIWIS related to start stop will get overwriten on next start, such as stop prohibition etc. This *** functionality is deeply embedded into car system and spread across many modules.
The only working solution is using some sort of tuning dongle (M-Enginnering can do it), i suspect that these dongles are detecting car start and just applying these changes on every boot, instead of making them persistant (it's not possible). I know it's also possible by modifying DME firmware to achieve persistance, but that's something nobody want to do as it's too invasive. The guy who recently was in this thread and manage to disable ***, said it's done by firmware modification & flashing DME
I think the reason *** is so difficult to override is that the VDub consortium (et al) got seriously burned on their mileage claims and emissions. They're really publishing numbers based on *** being a "major" player on the mileage front. So while there are safeguards in place to disable it (battery level, outside temps etc.) they want to make it real hard (meaning not a simple Kombi code change) to disable it resulting in folks claiming their mpgs are no where near those advertised.
Just a thought which of course doesn't solve the issue.
Has anyone looked at the 2024 992 Turbo? I believe that's the only year for 992 Turbo when *** was not enabled after each restart. What has changed or was it removed?
I can confirm that changing region in vehicle order from Poland to Germany still did not enable traffic sign detection. I just tried it today. So it seems it's GPS location based like someone suggested above.
Just got my new PIWIS running version 42.400.037, on my 2023 911-T. First job is to program out the electric spoiler lift.
When following the PDF (992 Aerokit official PDF, ENU 13/21) When programming my software does not seem to follow what the instructions show. At 4.3.1 I do not have a "maintenance of vehicle data" function, so I cannot proceed. Does anyone have access to newer instructions? Or am I doing something else incorrectly? Thanks, Kevin
Just got my new PIWIS running version 42.400.037, on my 2023 911-T. First job is to program out the electric spoiler lift.
When following the PDF (992 Aerokit official PDF, ENU 13/21) When programming my software does not seem to follow what the instructions show. At 4.3.1 I do not have a "maintenance of vehicle data" function, so I cannot proceed. Does anyone have access to newer instructions? Or am I doing something else incorrectly? Thanks, Kevin
Do you have it in E mode? That option will only appear in Engineering mode, as Normal (V) mode will only show the option to change data through PIWIS-Online, which is what we can't do. Check under Tools in your main screen, there should be an option to change between modes (E or V). Once in E mode, go back to Additional Menu (F7 I believe) and you should see the Maintenance of Vehicle Data available.
Thanks, I was not in E mode. I changed that and was able to drill down and change to the wing value but when I try write it, I get an error code: this vehicle data could not be created. 29000: negative control unit response: security access denied (7F2E33). I am going to reinstall another image per Mars and try again. Cheers, Kevin
Porsche 911 GT3 Artisan Edition Pays Homage to Japanese Culture
Slideshow: Porsche has created a Japan-only 911 GT3 Artisan Edition that blends track-ready hardware with design cues inspired by traditional Japanese craftsmanship.
Porsche Reveals Coupe Variant of the Electric Cayenne With a Fresh Look
Slideshow: Porsche's latest electric Cayenne Coupe blends dramatic styling with supercar acceleration, turning the brand's midsize SUV into a 1,139-horsepower flagship.
