Porsche 718 Forum banner
1,941 - 1,960 of 1,970 Posts
Thanks @Ken G. I want to emphasize how much the efforts put out to supply this guide are appreciated. The usefulness of the guide is reinforced every time I drive my 2016 X3 (and when I drive my Boxster). There is just not anything even close in the BMW world to the guide and the very little that does exist is just too old and incomplete to make me feel safe coding some things that are important. Sincere thanks to you and everybody else that contributed to it!!
 
Discussion starter · #1,942 ·
Thanks @Ken G. I want to emphasize how much the efforts put out to supply this guide are appreciated. The usefulness of the guide is reinforced every time I drive my 2016 X3 (and when I drive my Boxster). There is just not anything even close in the BMW world to the guide and the very little that does exist is just too old and incomplete to make me feel safe coding some things that are important. Sincere thanks to you and everybody else that contributed to it!!
I agree. @Ken G has taken what I started 3 years ago with about a dozen 'tweaks' into a very comprehensive guide of coding options for these cars. An invaluable tool. Kudos!
 
Thank you for that. Unlike the other one (the one labeled 3) which is grouped by the various 718 modules, the one labeled 2 is completely made up by me. Any thoughts/ideas/comments to the various categories that I made up?
100% version 2,
my eyes immediately noticed the category separation and is very readable 👌
 
  • Like
Reactions: RobertM
The various items in the current version of the guide are arbitrarily listed and do not have any order. For the next version, I would like to group the items but can't decide on the best way to group them. I don't think there is any perfect way to group them because regardless of the manner they are grouped, I always think that an item could fit into multiple groups. Attached are two options. I would appreciate everyone's thoughts on which method you prefer and any comments to the manner in which they are grouped.
I vote #2.
 
Thanks @Ken G. I want to emphasize how much the efforts put out to supply this guide are appreciated. The usefulness of the guide is reinforced every time I drive my 2016 X3 (and when I drive my Boxster). There is just not anything even close in the BMW world to the guide and the very little that does exist is just too old and incomplete to make me feel safe coding some things that are important. Sincere thanks to you and everybody else that contributed to it!!
Little OT: For BMW I use BimmerCode, with it you can code many things on BMW and Mini. It works just with a good Bluetooth OBDII trasmitter.
It's very good and simple.
 
I am still working on the update to the coding guide. However, I did make sure that I could generate a pdf with working links so I thought I would post the original guide with working links. I hope to finish up the next version in the next couple weeks.
Working on my 2023 Cayman S. Have X431 Pro. When I get to the coding page it asks for 4-digit code. Is there a PDF or spread sheet that shows the coding numbers to input? Oil gauge check to 4 segments. Turn signals to blink 5 times when changing lanes to start with.
 
I finally had a chance to play around with the coding functions on my new Launch X431. I bought the CRP919E version which is really nice. I did get a chance to use it a week ago on my friend’s Ford F150 to scan for his CEL code. Seemed easy enough to use.

Today it was the 718’s turn. Using this guide I successfully changed the one-touch function on the turn indicator to blink five times instead of three. I also lowered the speed that activates the rear spoiler. And finally, I reduced the Sound Symposer volume to zero.

I probably wasted 20 minutes though because I didn’t have the fuse installed. 🤦🏼‍♂️ Once I installed that I was able to detect the Sound Symposer but I still had some troubles. The first three tries the Launch wouldn’t accept the code. I decided to restart the car and tried one more time and it accepted it.

Still want to spend more time with it so I feel more comfortable coding. I did see an option for backing up the code. Just so I’m clear, I should do this before making changes in case I mess something up?
What is the coding for turn signals and spoiler? My X431 asks for 4-digit code. Help
 
Working on my 2023 Cayman S. Have X431 Pro. When I get to the coding page it asks for 4-digit code. Is there a PDF or spread sheet that shows the coding numbers to input? Oil gauge check to 4 segments. Turn signals to blink 5 times when changing lanes to start with.
When I bought mine a couple years ago, there was a piece of paper included in the package, that had an activation PIN.
 
Discussion starter · #1,952 ·
When I bought mine a couple years ago, there was a piece of paper included in the package, that had an activation PIN.
Oh. I got mine 3½ years ago, don't recall anything like that either. But that might be @550fiatphil's issue.
 
Passenger seat exit / entry comfort can be turned on and adjusted for height and sliding rear. The current trick is the passenger seat won’t move unless passenger door and drivers door is opened.
Where is the setting for passenger seat comfort entry/exit? That will be a very cool setting
 
Where is the setting for passenger seat comfort entry/exit? That will be a very cool setting
There is the same code in the Passenger Seat Memory module as is in the Driver Seat Memory module: Comfort Entry/Exit adjustment travel- E/A adjustment travel in seat fore/aft movement. However, this code does nothing because I don't think our cars have comfort entry for the passenger seat.
 
Ken - As I had arranged it before and sent to you it is more convenient to have it by module, things that fit into multiple modules can be listed as such. But when coding someone’s car it is much more beneficial to have it by module as it saves a ton of time switching in and out of modules depending on what they want done. I saved the version I had previously sent to you and find it more expedient. Just my 2 cents worth.
 
Ken - As I had arranged it before and sent to you it is more convenient to have it by module, things that fit into multiple modules can be listed as such. But when coding someone’s car it is much more beneficial to have it by module as it saves a ton of time switching in and out of modules depending on what they want done. I saved the version I had previously sent to you and find it more expedient. Just my 2 cents worth.
I never really liked the idea of grouping items by module since many of the items require coding multiple modules. That is why I asked for input on the forum and the input I received was a preference to group items by function. If others agree with Croc 2.0, please speak up.
 
I received my new Launch X-431 Pro v.4 yesterday, and have spent a fair amount of time with it and the Cayman today.

I'm pretty pleased with the X-431 so far. Works great as a code reader (it knows I had pulled the fuse from the sound generator), and should do all the maintenance resets and other normal DIY stuff easily.

Link to @Ken G's Coding Guide - Latest Version of X431 Ken G and Croc 2.0 Coding Guide | Porsche 718 Forum

And the coding function appears to be fairly complete and robust. Here's the (updated) list of what I've done so far:
I've failed (so far) on a couple things, which means I either haven't found the true spot to change, or haven't found some other required spot (some changes need to be made in multiple locations).
  • Change Auto headlight sensitivity
  • Enable spoiler indicator light
*Have done this 2 ways, one with the white gauge face hack (that doesn't illuminate the needles), and one by adding the tail and parking lights to the DRLs, which illuminates the gauges and needles.

Still to come:
  • Enable NAV display in MFI (need LVDS cable)
Other things I'm thinking of that I'm not yet sure if they can be done:
  • Auto parking brake engage
  • Re-map tail light function to EU/RoW config
  • Enable PDK Coasting mode while A-S/S is off
Something I noticed to research further - There are some spoiler params that appear to indicate possible visual spoiler notification, either in MFI or console button light. First attempt did nothing, but I'm going to give that some more research later.

Anyway, so far, so good. Even if I don't get any of the other stuff to work, what I've done so far is great.
Does anybody know how to
  • Enable NAV display in MFI using x431
 
Does anybody know how to
  • Enable NAV display in MFI using x431
The two codes are

Instrument Cluster: Board computer menu configuration – Board computer menu configuration byte 0- Navi Map = 1 {Default: 0}

Instrument Cluster: Board computer menu configuration – Board computer menu configuration byte 0- LVDS = 1 {Default: 0}

However, in order to get full functionality, you must add an LVDS cable to your car. Many non-nav 2017 and 2018 718s do not have the video-in port on the cluster so you can’t physically add an LVDS cable. According to a Rennlist post, without the LVDS cable, turn-by-turn navigation will still work: PIWIS 3 Coding RePIWIS 3 Coding Retrofit and Feature Request - Page 57 - Rennlist - Porsche Discussion Forums. See this post for instructions on adding an LVDS cable to your car: OEM Navigation Retrofit DIY - Rennlist - Porsche Discussion Forums
 
1,941 - 1,960 of 1,970 Posts