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.
Just wanted to share in case anyone was interested in the comfort keyfob opening and closing of windows/sunroof.
I was able to successfully code this in my 9Y0 2019 Cayenne Turbo today with my Launch X431.
I followed post #390 in the 992 coding thread from rnlst_log. For the X431, it was: Rear end electronics Search for coding items: "comfort" Coding value-Comfort_operation : Active/Open (write code) Coding value-Comfort_operation_radio_remote_control: Active/Open (write code) Memory settings for vehicle-Comfort Opening Window (whatever windows you want: ie: driver side, frt. pass. side): Active/Open (write code) Memory settings for vehicle-Comfort Opening Rear Window (whatever windows you want: ie: driver side, frt. pass. side): Active/Open (write code) Memory settings for vehicle-Panoramic roof comfort opening: Open/Active (write code)
Then go to your PCM, Settings, Locking, Comfort Opening and you can select Windows, Windows and Sunroof, Sunroof By default, your sunroof will "tilt" when open but you can go back and code it to "slide" open if you wish. I opted for tilt as didn't want anything to drop into the car aka leaves, bird droppings while open.
Now, click unlock and holding it will open what you have selected and then clicking and holding lock on keyfob will close!
Oh, yes. I fully understand the instructions. No clarification needed. My only question pertaining to NAR (US) vehicles is if it would be more advantageous to leave AV2 alone, select 8G4 and choose B35 instead of B02. Then revert everything except 8G4. There are 3 versions of the 8G4 dataset on the 9YA. edit: SEE LIST BELOW.One is RdW. One is China region. The third is Canada (NAR). No specific dataset released for US which is why we are flashing in the RdW dataset but the Canadian might be closer to the requirements for this region so Im curious what your opinion might be. Canada and the USA both share the same 8G1 dataset for deactivated Matrix Headlamps. (SES_0A5_7103_9Y0_0364_02PO53600032_MXBPAHS) (MY17-23)
When Coding a E-hybrid model with PIWIS, can you just plug the charger into the car (220v 50amp)? Or do you still need to put a 90+amp trickle charger on it?
You will probably see few folks reminding you that Porsche technical doc states that 90A+ is needed.
But from my experience specifically on 2019 E-hybrid when creating full VAL etc, my external "homemade" 80A charger doesn't actually add any amps and the HV battery does all the work charging the 12V battery.
Some modules might not like being coded when EV is charging is connected and for safety I would charge the car ahead of coding. In reality the 10kWh+ will give you few hours of charging 12V battery, even at therotical 90A (which is not really the case).
Last edited by fifthBro; Oct 25, 2024 at 02:58 PM.
Has anyone enabled high beam (8G1) assist on their 9YA Cayenne with headlights (8JT) PDLS LED main headlights. I tried to autocode with 8G1 but ZFAS failed coding and I believe maybe it needs matrix led headlights. I was curious to see if anyone has had luck manually coding it perhaps? Thank you
Is there a way to code the 9y0 my2023 cayenne to be able to close the tailgate using the remote? I see kufatec sells a module to do so but was wondering if I can just code it myself since I have piwis software?
buongiorno a tutti. Vorrei codificare la funzione PSE su una Cayenne ibrida del 2019. Ho visto alcuni DIY dove si modifica la funzione 0P8 o 0P9 e la 2HB e si codificano automaticamente i moduli DME, KOMBI e MIB. Essendo su codifica BMW da diversi anni (almeno 15), la procedura sopra descritta non mi crea personalmente alcun problema... (è la stessa procedura su BMW per codifica esperta). Premesso che circa un anno fa avevo provato a codificare automaticamente le SPEED LIMIT INFO sulla mia Cayenne senza successo (codificate ZFAS, GATEWAY, KOMBI, MIB) purtroppo la macchina ha perso accidentalmente tutti i parametri dei fari Matrix LED e quelli della telecamera ZFAS per cui ho dovuto pagare una cifra per la riconnessione... circa i vostri 700$ :testa di cazzo:Considerando che molti di voi sono esperti, chiedo se è possibile attivare il PSE non in codifica automatica. Mi spiego meglio.... Vorrei codificare manualmente (engineering mode) il PSE tramite un'attività di confronto fisico dei trace file, che in questo caso i file in questione sono quelli di DME, KOMBI e MIB. Basterebbe effettuare un backup dei tre trace file prima della codifica del PSE ed effettuare un ulteriore backup dopo aver codificato il PSE. Come faccio regolarmente su BMW, una volta ottenuti i trace file vado a confrontarli con software come winmerge per estrapolare le differenze tra i due file, prima e dopo la codifica. In questo modo, una volta raccolti gli elementi da modificare, si può tranquillamente provare una codifica manuale (engineering mode) sui tre moduli. Considerando che, dato quanto già successo a me, mi è costato un bel po' di soldi, vorrei evitare se possibile la codifica automatica. Magari qualcuno che ha eseguito la codifica del PSE ha già i file prima e dopo la codifica, sarebbe di grande aiuto se potesse condividerli. La procedura di confronto descritta sopra può aiutare per diverse codifiche, ho utilizzato questa tecnica diverse volte su BMW con grande soddisfazione. Ogni aiuto è molto apprezzato.
Sorry for my bad English.
Grazie
buongiorno a tutti. Vorrei codificare la funzione PSE su una Cayenne ibrida del 2019. Ho visto alcuni DIY dove si modifica la funzione 0P8 o 0P9 e la 2HB e si codificano automaticamente i moduli DME, KOMBI e MIB. Essendo su codifica BMW da diversi anni (almeno 15), la procedura sopra descritta non mi crea personalmente alcun problema... (è la stessa procedura su BMW per codifica esperta). Premesso che circa un anno fa avevo provato a codificare automaticamente le SPEED LIMIT INFO sulla mia Cayenne senza successo (codificate ZFAS, GATEWAY, KOMBI, MIB) purtroppo la macchina ha perso accidentalmente tutti i parametri dei fari Matrix LED e quelli della telecamera ZFAS per cui ho dovuto pagare una cifra per la riconnessione... circa i vostri 700$ :testa di cazzo:Considerando che molti di voi sono esperti, chiedo se è possibile attivare il PSE non in codifica automatica. Mi spiego meglio.... Vorrei codificare manualmente (engineering mode) il PSE tramite un'attività di confronto fisico dei trace file, che in questo caso i file in questione sono quelli di DME, KOMBI e MIB. Basterebbe effettuare un backup dei tre trace file prima della codifica del PSE ed effettuare un ulteriore backup dopo aver codificato il PSE. Come faccio regolarmente su BMW, una volta ottenuti i trace file vado a confrontarli con software come winmerge per estrapolare le differenze tra i due file, prima e dopo la codifica. In questo modo, una volta raccolti gli elementi da modificare, si può tranquillamente provare una codifica manuale (engineering mode) sui tre moduli. Considerando che, dato quanto già successo a me, mi è costato un bel po' di soldi, vorrei evitare se possibile la codifica automatica. Magari qualcuno che ha eseguito la codifica del PSE ha già i file prima e dopo la codifica, sarebbe di grande aiuto se potesse condividerli. La procedura di confronto descritta sopra può aiutare per diverse codifiche, ho utilizzato questa tecnica diverse volte su BMW con grande soddisfazione. Ogni aiuto è molto apprezzato.
Sorry for my bad English.
Grazie
Translated your post using Google translate:
Italian - Detected
English
good morning everyone. I would like to code the PSE function on a 2019 Cayenne hybrid. I have seen some DIY where the 0P8 or 0P9 function and the 2HB are modified and the DME, KOMBI and MIB modules are automatically coded. Having been on BMW coding for several years (at least 15), the procedure described above does not create any problems for me personally... (it is the same procedure on BMW for expert coding). First of all, about a year ago I tried to automatically code the SPEED LIMIT INFO on my Cayenne without success (coded ZFAS, GATEWAY, KOMBI, MIB) unfortunately the car accidentally lost all the parameters of the Matrix LED headlights and those of the ZFAS camera for which I had to pay a fee for the reconnection... about your $700 :********: Considering that many of you are experts, I ask if it is possible to activate the PSE not in automatic coding. Let me explain better.... I would like to manually encode (engineering mode) the PSE through a physical comparison activity of the trace files, which in this case the files in question are those of DME, KOMBI and MIB. It would be enough to make a backup of the three trace files before encoding the PSE and make a further backup after encoding the PSE. As I regularly do on BMW, once I have obtained the trace files I go to compare them with software like winmerge to extrapolate the differences between the two files, before and after encoding. In this way, once I have collected the elements to be modified, you can safely try a manual encoding (engineering mode) on the three modules. Considering that, given what already happened to me, it cost me a lot of money, I would like to avoid automatic encoding if possible. Maybe someone who has performed the encoding of the PSE already has the files before and after encoding, it would be of great help if they could share them. The comparison procedure described above can help for different encodings, I have used this technique several times on BMW with great satisfaction. Any help is greatly appreciated.
Sorry for my bad English.
Thank you
The coding values applied through autocoding are stored in ZDC directory of PIWIS. The problem is that xml format is different to the one VAL uses and even comparing two sets with diff tools is quite painful as timestamps and other small differences emerge.
Perhaps someone smarter could write and simple python parser that takes two VAL xml files (before and after autocoding) and then module by module compares the "Control unit, coding" values. As an extra it could also then cross check these with the values that are written by autocoding in ZDC directory and then spit it out as summary of differences in a human readable format.
The coding values applied through autocoding are stored in ZDC directory of PIWIS. The problem is that xml format is different to the one VAL uses and even comparing two sets with diff tools is quite painful as timestamps and other small differences emerge.
Perhaps someone smarter could write and simple python parser that takes two VAL xml files (before and after autocoding) and then module by module compares the "Control unit, coding" values. As an extra it could also then cross check these with the values that are written by autocoding in ZDC directory and then spit it out as summary of differences in a human readable format.
thank you for answer.
actually comparing two trace files in xml format is not such a problem. It is a procedure that I have already used to retrofit the 18-way seats on my Cayenne. At the moment I do not have the notebook with PIWIS 3 at hand so I cannot publish the procedure to use.
Basically, it involves saving two trace files in the Engineering mode (coding without MCR rules), one before and one after the automatic coding. Once the coding values have been read in the Engineering mode of any control unit (example: MIB2, DME ACC ... and so on) via the PIWIS 3 menu with the key (F10 = Logs) the trace files are saved in xml format, furthermore, always via PWIS 3 there is the possibility of saving them also in PDF format.
The ones needed for the comparison are the XML format files.... no VAL is needed..
As soon as I have the chance I will post a sort of DIY for this comparison with the hope that it will be helpful to this forum.
The coding values applied through autocoding are stored in ZDC directory of PIWIS. The problem is that xml format is different to the one VAL uses and even comparing two sets with diff tools is quite painful as timestamps and other small differences emerge.
Perhaps someone smarter could write and simple python parser that takes two VAL xml files (before and after autocoding) and then module by module compares the "Control unit, coding" values. As an extra it could also then cross check these with the values that are written by autocoding in ZDC directory and then spit it out as summary of differences in a human readable format.
This Builder Is Turning Heads With Its Slantnose 911 Creation
Slideshow: A small Polish tuner has reimagined the Porsche 911 Slantnose for the modern era, blending 1980s nostalgia with widebody tuning culture and serious performance upgrades.
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.