Porsche 718 Forum banner

718 Coding with X431

1 reading
311K views 2K replies 147 participants last post by  ReidMcT  
#1 · (Edited)
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.
 
#2 ·
I guess one can get into the weeds with this thing if they're not fully read in on it, but I will be following along. There are some items you have already addressed that I would also like to do as well. Did you purchase it from Amazon? Looks like they're price reduced right now.
 
#7 ·
Yup, you do need to proceed with care, and only make one change at a time. And take good notes. I've already caused one head-scratcher - I'm not sure where or how I disabled the front side marker function. They no longer come on as position lights, but they still blink with signals or hazards. I'd didn't make good note of what I did as I didn't notice when that behavior changed. I'll need to spend a little more time tracking it down.

I bought the X431 because I wanted a solution that supported both my Porsche and my Audi. The Launch products do that, and no extra charge for more than one car make.

Yes, from Amazon. It was $900 less a $50 'coupon' = $850. Not cheap, but it has already made several things about the car better (IMO), and definitely saved me $230 or so on the console switch memory module.
 
#3 · (Edited)
I was documenting my coding changes in my own log (My 2018 Cayman Mod Log), but figure this would be a better place to consolidate all coding changes…

All my coding mods/changes will be listed here:

Using my Launch X431 PRO 3S+ V2.0

1. Activated 4-point LED ON while headlights ON (normally 4-point LED turn off when headlight turns on).

Coding:
Rear-End Electronics: Codiertabelle: Exterior Lighting: Exterios Lights, DD as a marker light = YES

Rear End Electronics: Exterior Lights Parameters: Dimming value for DD lights as marker light = 100


This in essence makes the 4-point daylight driving light a marker light when headlights are on. It retains the daylight driving function when headlights are off.

Image


2. Activated window open/close with comfort function


CODING:
Front End Electronics: Coding: Coding_0: Coding-Comfort functions-Window Comfort Opening = YES

Front End Electronics: Coding: Coding_0: Coding-Comfort functions-Window Comfort Closing = YES



3. Changed turn signal "One-Touch flashing Cycle" from 3 to 5

CODING:
Front End Electronics: Coding: Coding_0: Exterior Lights Parameters-One touch flashing cycles = {whatever number of flashing cycles you prefer}


4. Activated Wiper Tear Drop function.
This function activates an additional pass of the wiper a few seconds after washer is activated and normal wiper mode is finished.

CODING:
Front End Electronics: WWS Coding: WWS Coding-Teardrop function active = YES

5. Enabled illumination on RPM gauge and Speedometer with headlights off (Another member in MacanForum and I did a lot of research to figure this one out, and you can even find threads here in the 718forum making reference to our discovery in the Macan Forum). You can turn on only the central RPM dial or both speedometer and RPM gauges.

CODING:
Instrument Cluster: Dimming-general configuration: Configuration-all dials white = YES

Instrument Cluster: Dimming-general configuration: Configuration-central dial white = YES


6. Emergency Brake Display (EBD) Activation: This code enables emergency brake display, when braking hard (which is a modifiable acceleration parameter), your brake lights will flash to catch attention of drivers behind you…. In the video I show this feature in my Macan…



CODING:
Rear-End Electronics: Coding Value (or Codiertabelle): Exterior Lighting: Exterior Lights, emergency brake display function available = YES

Rear-End Electronics: EBD Parameter: Speed brake light flashing On = 3 {whatever speed you want emergency brake to start activating, default is 70km/h, but I set it up at any speed above 3 km/h… once car reaches 3 km/h, if I brake hard, it will activate}

Rear-End Electronics: EBD Parameter: Decceleration brake light flashing On = 0.45 {whatever deceleration value you choose… through experimentation, I found that setting this value to 0.45g is appropriate}

Reae-End Electronics: EBD Parameter: Decceleration brake light flashing Off = 0.35 {whatever deceleration value you choose… through experimentation, I found that setting this value to 0.35g is appropriate}

Rear-End Electronics: EBD Parameter: Brake light flashing run-on time = 1 {this is the amount of flashing time… through experimentation found that 1 second is enough, otherwise you could stop at a light and the lights could still be flashing (while you are stopped)}


Other parameters within EBD parameters can change the rate of flashing. I left those unchanged, as I found the original setting to be OK.

7. Changing Sound Symposer (Soundaktor) sound loudness: This will change the loudness (volume) of the soundaktor, which is a device that produce artificial engine sound to ”enhance“ engine sound in the cabin.

CODING:
Sound Symposer: Loudness_actuator_for_structure_borne_sound = 0 {you can set this to any value between 0 to 100%. Original setting is 100%. I set this value to 0%, as the reality is that the engine sounds much better without artificial enhancement}
 
#8 · (Edited)
5. Enabled illumination on RPM gauge and Speedometer with headlights off (Another member in MacanForum and I did a lot of research to figure this one out, and you can even find threads here in the 718forum making reference to our discovery in the Macan Forum). You can turn on only the central RPM dial or both speedometer and RPM gauges.

CODING:
Instrument Cluster: Dimming-general configuration: Configuration-all dials white = YES

Instrument Cluster: Dimming-general configuration: Configuration-central dial white = YES
The quoted change works well, but doesn't illuminate the gauge needles, just the backlit numbers and such. An alternative is to enable what is sometimes called "Scandinavian DRLS" which basically adds all the exterior position lights when the ignition is on—front parking lights, side markers, tail and license lights. It also lights up the gauges, including the needles. So this is a more complete way to light the gauges if you are OK with having the tail lights and such lit all the time.

Front-End Electronics > Coding value--Exterior lighting--Exterior lights, DD lights with marker light = Yes
 
#4 ·
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.

And the coding function appears to be fairly complete and robust. Here's the list of what I've done so far:
  • A-S/S button saves last state
  • Gauge backlighting always on*
  • Disabled seatbelt warnings
  • Remapped coolant temp gauge accuracy
  • Comfort blinkers to 4
  • Windows up/down with key fob
  • Change side markers to indicators only**
  • Activated teardrop wiper (not tested yet, don't want to spray all over the car).
  • Change/disable the auto-headlight washing after 10 washer uses
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 spoiler deploy speed
  • Change Auto headlight sensitivity
  • Change side markers to indicators only*
*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.

**Note - I thought I'd failed on this one, but it appears to have working now, the front corner lights are now ONLY indicators, they do not illuminate with the parking or main lights. Not 100% sure what change that I made did that, so I hope I continue to like it that way as I didn't make notes of any of the settings that didn't seem to work...

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
  • Don't unlock all doors when opening trunk/rear lid via fob or proximity sensors
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.
I wasn’t able to disable auto start/stop with Launch…. I can deactivate in Gateway, but the two codes in Instrument Cluster are not taking. Wonder if you could do with yours. I think PIWIS may be required for this one.

BTW… congrats on your X431 purchase. This is a good investment, and one that every Porsche owner should consider, not only to modify coding, but it is a magnificent diagnostic tool.

Before I took delivery of my car, I took my X431 to the dealer and assessed the health of the car, checked rev limiter, battery health, etc…
 
#6 · (Edited)
I wasn’t able to disable auto start/stop with Launch…. I can deactivate in Gateway, but the two codes in Instrument Cluster are not taking. Wonder if you could do with yours. I think PIWIS may be required for this one.
I didn't disable A-S/S, I just changed the config so that the car remembers the state of the A-S/S button on start up. So I have A-S/S turned off now, and the car starts up with it already off. I don't have to remember to hit the button every time I get in the car. The setting apparently only remembers the A-S/S and PASM button states. PSE, PSM, etc. are not remembered.

Remember Auto Stop/Start (ASS):
AIR CONDITIONING> Coding value--Default Driving State Coding Value = Last Mode
{Default: Eco ON}
AIR CONDITIONING> Coding value--Default Driving State Coding Value Last Mode = Yes
{Default: No}

Image

Image
 
#9 ·
Disable seatbelt warnings. No seatbelt chimes on startup, and no lights in the gauge.

Instrument Cluster > Coding Value Driver Seatbelt Warning = No
Instrument Cluster > Coding Value PassengerSeatbelt Warning = No
Instrument Cluster > Coding Value USA Seatbelt Warning = No
Instrument Cluster > Coding Value Acoustic Seatbelt Warning (not USA, not Canada) = No
 
#14 · (Edited)
Coolant Temperature Characteristic Curve
I have modified the coolant temperature characteristic curve in my Macan a few months back maybe a year ago), and just did it in my Cayman as well. It is interesting how Porsche is modifying the actual values you see, probably to decrease variability in the display and avoid having unnecessary calls from customers that don’t know what’s going on. But I have to think that for a 718 or 911, having modified display temp values is completely unnecessary. I wasn’t surprised to see this in my Macan, fine, I just modified it.

The location for the characteristic curve values is here…

Instrument Cluster: Coolant temperature characteristic curve

You will see all real and displayed values (8 for each). See table below (in C):

Image


I plotted this table, shown below, so that you can see the behavior.
Image

If you follow the green line (displayed values in cluster), there is a long period of time where you will see a constant temperature, when in reality the temperature is higher. Then, once out of that range, it will shoot up really quick to catch up with real temperature value (blue line)… that may not give much response time if your car is overheating. That orange zone is what you would need to pay attention to.

This curve was designed for the temperature to remain steady during normal operation mode, but it will in fact introduce hysteresis in the values you are seeing.

Displaying actual temperature values makes common sense.

To display actual values in the instrument cluster, copy the respective X value into the Y value.

I recommend you write down all values first (so that you can have them as backup), then change all Y values.

I also changed the bargraph range to display the full temperature range starting at 36C… default is 60C.

Code:
Instrument cluster: Bargraph settings: Bargraph settings-coolant temperature bargraph start = 36 {default = 60}
 
#100 ·
I'm very interested in the ability to code the water temp gauge to read in an accurate number

I've searched high and low for something like this. It's so infuriating to see the temp gauge read perfectly till it levels out and then it acts like it's exactly the same temp from then on.
Any way to do this in degrees F instead of C? Also, is the unit to do the coding really $1000+? That seems....extreme.
 
#17 ·
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.

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.
Is this the Launch model that you bought?
$719 seems like a really good price.
thanks
 
#22 ·
Do either of you see any difference between these two Launch units?

Unit 1

Unit 2
Both units are OK. There are many versions of X431 out there and it can be confusing, but they are all running the same software. So you won’t go wrong with any of the units….

In addition to the two Porsches (Macan and 718 Cayman) I also have a BMW X2 and a Volvo XC90… I have used the X431 extensively on all my cars. Excellent tool to diagnose issues and also had replaced all brakes in all my cars, except the Cayman. Very useful tool.

This is the one I have….
LAUNCH X431 PRO3S+ Full Bi-Directional Car Diagnostic Scanner,ECU Coding,Key IMMO,AutoAuth,OEM All System & 31+ Service Automotive Scan Tool for All Cars[Upgrade Version] https://a.co/d/aTUaAJ4
 
#26 · (Edited)
No, you need PIWIS for that, or alternatively, look at this thread….


A lot of people turning on navigation with this DIY hack. I already had NAV, but didn’t have CarPlay. Using this, I activated CarPlay the same day I took delivery of the car….

I also have PIWIS 2. In my Macan, I had to use PIWIS for more complex service, adaptation or activation of features. For example, I replaced my BiXenon headlights with LED headlights and I had to use PIWIS to perform adaptation of headlight modules as well as headlight commissioning. Can’t do that with Launch. Also, modifying height of air suspension only in PIWIS…

Although Launch X431 is very good, it can’t do everything.
 
#29 ·
There care a few things above I would love to have. A major example is having the A/C system always restart exactly where it was set when the car was shutdown. Other nice to have functions are the washer teardrop feature, 5 turn signal flashes as three is never enough if start turn signals a few seconds before changing lanes, and opening either the front or rear trunk does not unlock the car. However, collectively I do feel good spending circa $800 plus the time, especially, needed to invent what to do, then probably never use the thing again. I have not used them but there are some BMW associated businesses, for a reasonable albeit expensive fee, will send a preprogrammed laptop to make the coding changes (and then the laptop must be returned). I would take advantage of something like that for my Boxster as it gets very old having to dick with the A/C controls every time I get into the car.
 
#31 ·
Our BGTS includes the memory package and was able to save my preferred A/C settings using the Key button. If your 718 has the memory package, it should save your A/C parameters.
 
#33 ·
I do have the memory package but it only saves the specific settings in effect at the time the settings are saved. It does not cause the system to retain the settings when the car was last shut down. In my experience, the probability is ultra high the desired setting will be the same settings last used so just about every time I start the car I have to fiddle with it (temperature setpoint, recirc, and seat ventilation). It is not much to do as it is all button pushes but it would be nice if it just simply returned to what I last used as our BMW X3 does. Interestingly, it does retain these settings for a few minutes but filling the tank is long enough for it to reset to the memorized settings.
 
#40 ·
Seatbelt warnings. I never drive without belting up, and do not need my car to chime and display warnings if I start it to back it out of the garage to wash it (for example). So those chimes and lights and warnings just annoy me.

There are either 1 or 4 params to change, depending on preferences.

Instrument Cluster > Coding value--Coding byte 2--Driver seatbelt warning = 0
{Default: 1}
Instrument Cluster > Coding value--Coding byte 2--Passenger seatbelt warning = 0
{Default: 1}
Instrument Cluster > Coding value--Coding byte 2--USA seatbelt warning = 0
{Default: 1}
Instrument Cluster > Coding value--Coding byte 2--Acoustic belt warning (Not USA, not Canada) = 0
{Default: 1}


Do only the 4th one (Acoustic) to simply kill the chimes without affecting the lights and MFI warnings. Do all 4 to completely disable the belt warnings.
Image

Image

Image

Image
 
#43 · (Edited)
Found another of my hoped for items. By default, opening either deck or trunk via fob or proximity sensors unlocks the doors as well. To me, that's silly. Say I'm at cars & coffee, and need something from the trunk. I open the trunk, grab the camera or whatever, and close the trunk. But now the doors are unlocked, so I have remember to lock the car again before I leave. Neither my Audi or Golf are/were this way. I can open the hatch on the Audi while locked, and none of the doors unlock. Close the hatch, the car chirps and is locked. Much more logical to me. The change here addresses this.

Front end electronics > Coding value--General--General:Central locking opens with lid/rear lid unlocking = No
{Default: Yes}

Image
 
#44 ·
I've been researching the x431 and the Autel models. Do either of you see appreciable differences between them. I also went to the Launch web site and do not see the models offered on Amazon on their site. Thought this is odd. Are these models offered on Amazon ( also the models you both seems to be utilizing) - are they some kind of knock-off or Chinese imitation? Here's the Launch web site.
 
#45 · (Edited)
Mine looks exactly that the X431-Torquelll, assuming this is the US market label for the same machine I have. The label on the back has the Launch logo and all copyright information... but it is made in China...

Actually, Launch headquarters and R&D centers are in Hong Kong, which is now part of China. So, technically, whether you buy it from US dealer or directly from a dealer in China, you will get a China made product.

There are a number of reference websites, assuming dealers: (1) www.x431.com ; (2) www.x431tool.com ; (3) www.launchtechusa.com etc... And I believe this is the corporate website: en.cnlaunch.com

I think you'll be perfectly safe buying the ones from Amazon at a very good price. You'll have access to the main X431 website for latest updates (for 2 years). And you still get the same tool that will allow you to make modifications and diagnose your car.

I don't have experience with Autel, so I can't say.
 
#48 · (Edited)
More on on the lighting changes. The white-gauge-face hack to turn on the gauge backlighting at all times is well documented, and only has a single drawback—the gauge needles don't light up unless the lights are actually on.

The other main way to light the gauges does light the needles as well. That is done by adding the "marker lights" to the DRL settings. The "marker lights" are the tail lights, license lights, front side markers (in the US and Canada) and the gauges. By default (at least on my 2018 CB), the front parking lights are NOT activated by this change. (I did see a separate option to turn these on with DRLs.) But the gauges (incl. needles) do come on with the key, in any light. The drawback to this one is that while some people can tolerate running the tail lights at all times, having the front side markers always lit bothers them. To address that, read on into the next paragraph.

System Selection > Front-end Electronics > Coding value--Exterior lighting--Exterior lights, DD lights with marker light = Yes
{Default: No}


Don't like the side marker lights? Everywhere other than North America the front "marker" lights are used only for side indicators. So turning off the side marker function is simple. But do note, this cryptically named setting defeats all side marker (position) light functions. They only flash with blinkers or hazards if you do this.

System Selection > Front-end Electronics > Coding value--Exterior lighting--Exterior lighting: direction indicator at side direction indicator output = No
{Default for North America: Yes}
 
#53 ·
I just received my x431. I have to say this is a nice piece of kit. Really well packaged and nothing about it seems flimsy or cheap. I like how the bluetooth OBD connector stores in the unit too. It also came with the TPMS scanner/reader. Hopefully it performs as well as it looks. This is what's in the box.

Image


Image


Image
 
#54 ·
I've found, changed and tested the spoiler deploy speed. It's one of the parameters that is not fully translated from German.

System Selection > Rear-end Electronics > Spoiler parameter--GeschwSchwEinf 1 = your target speed in kph
{Default: 125}


The default of 125 kph is 78 mph, and with the normal speedo error of reading about 2 mph fast, it seems to deploy at 80 mph indicated. You can go higher or lower here, depending on your need. I dropped mine to 105 kph (65 mph) because I seem to frequently drive in windy conditions where the spoiler helps even at lower speeds.

Image
 
#1,040 ·
I have been testing different settings in this specific GeschwSchwEinf1 parameter (which I set to 55 km/h) without changing the GeschwSchwAusf1 parameter (set to 125km/h), but the spoiler always deploy at same speed (about 78mph).

Hence, the GeschwSchwAusf parameter seems to me is the spoiler deployment speed, while the GeschwSchEinf1 parameter seems to be the retraction speed. There are two reasons why I say this: (1) I can’t set the “Einf1” speed higher than the “Ausf1” speed. It errors out in code writing. That means that “Ausf1“ speed always need to be higher than “Einf1” speed, and (2) when I look at these parameters in PIWIS simulation mode, the ”Ausf1” parameter is set at 120 km/h, while the “Einf1” parameter is set at 80 km/h (See screenshot below).

This is an indication that the deployment speed is set at the “Ausf1” parameter while retraction is set at “Einf1” parameter.

WIth that in mind, then I set the deployment speed at 95 km/h (~60mph) and the retraction speed at 55 km/h (~35mph). I’m testing this tomorrow.

Any strong opinions on this logic? Maybe this is already solved in further posts below the one I’m replying to, but after reading some of them, it seems confusing.

Image