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.
If you are coding your PCM or Headunit, the screen might go dark on your PCM. I have seen this on Stock and AIO PCM, every time that you code the PCM. It will go in Production Mode (dark screen). You need to deactivate Production Mode from the Maintenance and Repairs tab below. Select Produktionmodus deaktivieren then click on Next twice and Start the job by clicking F8.Start. At the end click on Next to return to the main menu. You will also see a Service Mode message on top of the screen. This will disappear once you disconnect your VCI connector. If you have a Carlinkit or Ottobox module for Wireless Android Auto or CarPlay, I would highly recommend that you disconnect it before coding your PCM.
If you are coding your PCM or Headunit, the screen might go dark on your PCM. I have seen this on Stock and AIO PCM, every time that you code the PCM. It will go in Production Mode (dark screen). You need to deactivate Production Mode from the Maintenance and Repairs tab below. Select Produktionmodus deaktivieren then click on Next twice and Start the job by clicking F8.Start. At the end click on Next to return to the main menu. You will also see a Service Mode message on top of the screen. This will disappear once you disconnect your VCI connector. If you have a Carlinkit or Ottobox module for Wireless Android Auto or CarPlay, I would highly recommend that you disconnect it before coding your PCM.
^^^ Yup, this happened to me after I fixed my automatic time issue (my PCM had the incorrect coding for automatic time synchronization with GPS causing my car to display DST all the time). Thankfully @718socal knew about the issue and de-activated production mode bringing my PCM back to life!
^^^ Yup, this happened to me after I fixed my automatic time issue (my PCM had the incorrect coding for automatic time synchronization with GPS causing my car to display DST all the time). Thankfully @718socal knew about the issue and de-activated production mode bringing my PCM back to life!
Yeah this happened to me too before I installed AIO. It took me two days to figure it out. No PCM screen for two days
What do you know. The speed calibration is different between US and Canadian cars. I checked two Canadian cars and they have the same as yours. Then I checked mine and a GT4 and they show 100%. That is the best way to avoid a ticket in Canada
To be clear, the first picture I posted was from simulation mode (not my actual car). I connected to PIWIS and discovered my actual settings are also 100, 100, 100.
To be clear, the first picture I posted was from simulation mode (not my actual car). I connected to PIWIS and discovered my actual settings are also 100, 100, 100.
settings from my '22 Boxster GTS 4.0
Very strange. The 2 simulation data that I had were from Canadian Spyders. Now we need to confirm on the US Spyder.
If you are coding your PCM or Headunit, the screen might go dark on your PCM. I have seen this on Stock and AIO PCM, every time that you code the PCM. It will go in Production Mode (dark screen). You need to deactivate Production Mode from the Maintenance and Repairs tab below. Select Produktionmodus deaktivieren then click on Next twice and Start the job by clicking F8.Start. At the end click on Next to return to the main menu. You will also see a Service Mode message on top of the screen. This will disappear once you disconnect your VCI connector. If you have a Carlinkit or Ottobox module for Wireless Android Auto or CarPlay, I would highly recommend that you disconnect it before coding your PCM.
I’ll piggy back to this as it happens to me too each time I code the PCM, and if I auto code all modules, then my rear camera also goes out (each time), I suspect cause the camera needs the PCM communication to fully code but by then the PCM is out. What I end up having to do is get PCM out of production mode and then go back and recode the rear camera. I freaked out the first time this happened. Luckily @rnlst_log came and rescued me. Lol.
I’ll piggy back to this as it happens to me too each time I code the PCM, and if I auto code all modules, then my rear camera also goes out (each time), I suspect cause the camera needs the PCM communication to fully code but by then the PCM is out. What I end up having to do is get PCM out of production mode and then go back and recode the rear camera. I freaked out the first time this happened. Luckily @rnlst_log came and rescued me. Lol.
I’ll piggy back to this as it happens to me too each time I code the PCM, and if I auto code all modules, then my rear camera also goes out (each time), I suspect cause the camera needs the PCM communication to fully code but by then the PCM is out. What I end up having to do is get PCM out of production mode and then go back and recode the rear camera. I freaked out the first time this happened. Luckily @rnlst_log came and rescued me. Lol.
Happened to me as well. Ended up bringing it up when it was at the dealer to fit a piece of brake duct-work the factory miss-shipped. Took them a couple hours, but they figured it out and recoded everything. Now I knw how to avoid that.
Happened to me as well. Ended up bringing it up when it was at the dealer to fit a piece of brake duct-work the factory miss-shipped. Took them a couple hours, but they figured it out and recoded everything. Now I knw how to avoid that.
Hahaha. I can't believe that this is not documented by Porsche.
There are other features you can enable in the cluster. That does not mean they would work. Additionall coding is necessary. For *** offf, you can just code the BKE to remember the last mode
03-12-2023, 07:32 PM
