Mkin

Car was in service today. They ordered new door locking switch between the seats and new trunk light/flashlight. Trailer hitch is now coded correctly and tail lights are now coded on with DRL. Before the service I figured out that locking problems were user errors by a pensioner getting used to dsg, stop-start and kessy. Let's hope that all window and locking problems are sorted out with new lock switch and some user guidance. Allthough there MAY have been something in the dashboard driverside fusebox. When technician was checking the trunk light power supply, he had noticed some bad contact and did something. He had said, that the fusebox has been opened when they installed the trailer hitch in the service. He had said that CH/LH lights can't be coded to foglights from xenon. Is this true or didn't they just have instructions or bother to find them for original tester? This works on pre-FL Yeti : Change Coming/Leaving Home To Fogs:Cent Elect - 09 Coding - 07 Long Coding Helper - Byte 17 Bit 3 = Coming / Leaving Home with fog lights Is FL different that this doesn't work? Next time when I see the car I will take autoscan to see that everything is ok and maybe try to code the lights if possible.

Maybe this is getting a little bit offtopic, but the car is going to service next tuesday. Car has failed to lock the doors couple of times now. Door locking switch between front seats opens and closes the windows also and feels like it tangles up a little bit sometimes. Dad tested it few times and once windows came down with only a short press of the lock open button. Lets hope that there are some new fault codes and they can sort it out. If the switch or it's controller is faulty somehow it would explain why the doors won't lock and the windows come down sometimes. MAYBE it could somehow cause the automatic door locking ticks going back on by themselves in the MFD settings. I won't see the car before it goes to service. I asked them to check the trailer hitch coding and code the tail lights on with DRL. Also if they could code CH/LH lights to work with foglamps not bixenon while they are at it. Guy at the desk told me that no one has asked that before and they will see if that can be done... The car has to get sorted out before I try to do any coding. I truly hope that the car comes in shape fast and there are no new surprises in the near future. I got dad back from a Japanese car and there are already little problems after few weeks in a new car... The flashlight that you can take with you from the trunk doesn't work either, they will take a look at it too.

So that is all and is giving the fault code? Great! But it figures that they didn't do even the trailer hitch installation right before they handed the car over... Trailer hitch isn't from the factory, they installed it in Finland. I guess then the false coding isn't to blame for those few faults that have occurred. Once dad couldn't lock the doors. Not with kessy door handle or remote control. After he drove the car locks worked again. Today morning he had sat into the car and the windows opened by themselves... And the automatic door locking ticks from the MFD Settings came back on themselves. I took them off when dad got the car, and today dad told me that the car is locking the doors while driving again... Strange. Here is the first and second scan in the same file. I deleted codes in between. Log-VZG-206-TMBLA75LXH6046711-750km-466mi.txt

It should be just above...

Here is the last scan I took. Log-VZG-206-TMBLA75LXH6046711-759km-466mi.txt

I checked the car today with VCDS. It had this fault code about wrong coding, so I didn't do any tests or changes. I think we will have to check it at service, before I try to do anything. Car had changed automatic door locking settings back on (ticks on mfd) by itself and drove it's windows down once when sitting into the car. So maybe this wrong coding from service could do this...

I agree. Thanks for the information. Since Yeti can't be coded like the newer MQB platform cars, it is in the end easier to install this kind of module. Atleast if you have somekind of DIY skills. You can use s/s whenever you want by just pushing the button not having to code it back and forth many times.( For possible service/warranty issues or MOT) I found discussion here about more or less DIY versions of the module. There are 3 versions found at least in pages 1,6 and 7. It is my dad's car that I'm looking these options for and the decision is his what to do. If he wants to get the memory module I think I will buy reasonably priced ready one and install it for him.

Hi. Did you do that module yourself or where did you buy it from? I have been searching for information how to code the memory to stop/start function. Memory can't be coded in the Yeti. Possibly the whole system can be disabled permanently by coding. So I have been looking in to these memory modules also, because it would seem much more practical to push the stop/start back on when wanted. Like going to service or MOT test. I have found these so far: https://www.active-sound.eu/en/start-stop-automatic-ssa/start-stop-automatic-memory-modul-ssam-modul https://m.ebay.com/itm/Start-Stop-Memory-module-for-cars-SSA-state-memory-or-killer-/322352078637 https://www.amazon.co.uk/Start-Stop-Automatic-Memory-Module-SSAM/dp/B013ER5VKO https://www.carelectronic-webshop.de/en/car-memory-modules/deactivation-engine-stop-start-system/volkswagen-vw-engine-stop-start-system-deactivation-memory-module/a-26/ https://www.kfzteile-mayer.de/Start-Stopp-Automatik-Memory-Modul Yeti should have the + version of the module. I would like to hear experiences about these modules. How well do they work in the long run, problems installing them etc.?

I came across this topic about Audi Q3. Another coding that has worked for some PQ35 platform cars. http://www.q3ownersclub.co.uk/forum/tdi-start-stop-deactivation-mod_topic3033.html

Thanks. I'm not sure when I will be in the same place with the Yeti and my VCDS and have enough time to fiddle with it. But if my dad wants to get rid of the whole system I will try it sometime. Maybe I should try to find again the voltage and temperature coding instructions, if that doesn't work and try them also. If anyone has done this or has a chance to test it, I would also like to what happened. I don't want to mess anything up from a brand new car.

I have been searching forums and it seems that these PQ35 based light controllers can't be coded with VCDS. So dad has to ask the tail lights with DRL coding at the first car service. But how about the stop start coding? Has anyone coded the memory or disabled the stop start function? It is really irritating in my dad's driving conditions. Maybe I will have to look into those memory modules, if they are easy enough to install and work reliably without problems. It would be the best solution to have working stop start when wanted, but not having to push the button after every start. If it could be coded like in some other platforms, the best thing would be the reversed button light. It would light up only when stop start system is in use...

Thanks. After the Felicia I bought -00 Seat Ibiza TDI. That was a rocketship after the 64bhp traditional diesel. Then came -03 GTI Golf. I drove it for 2 years and sold it. I needed more space and bought -01 Passat variant 1.9 TDI 4motion. I've driven it now over 12 years. We have -06 Passat variant 2.0 FSI 4motion also. Next time when I'm buying a daily driver for my family we'll see if I'm getting back to Skoda myself. 4x4 Superb combi would do nicely.

Second generation Skodist here getting acquainted to your forum. My path with Skoda started back in -94 when my dad bought a brand new Forman 1.3 GLXi plus. It was a serious upgrade from our -91 Lada 1500 S, wich turned more to the left than right. (Not kidding!) Dad drove it for 11 years and then gave it to me for a toolbox for work. That was seriously my best car so far. Had it for free, drove it 8 years and sold it to my friend for 300€. Did only few minor repairs over the years. My first own Skoda was Felicia combi 1.9d LX -97, wich I bought in -99. It was registered as a van and had thin padded plywood backseat.(small diesel-tax) It was a good solid car and I drove it for two years. Nowadays I have been driving 3bg and 3c Passats for years. My dad drove a Subaru Forester -05 for 12 years and now traded it for brand new 1.4 TSI 4x4 DSG Outdoor Yeti. This car is the first really modern VAG in my family and I'm trying to help my dad figure out this mobilized computer of a car... Forester had automatic air conditioning, electric windows and a seven segment clock on the dash. So now everything is quite new for 70 years old pensioner. Hoping to find more information about FL Yetis and especially from VCDS codings, than what I found in finnish sites. Cheers

Hello. I found this old topic when I was searching coding instructions for -17 FL Yeti. My father bought new 1.4 TSI DSG 4x4 Outdoor Yeti and asked me if I can code rear lights on with DRLs. In some other topic someone said that in FL Yeti this can't be done with VCDS. But it can be done with the original maintenance tool. So this coding below does not work with my fathers car? Rear Tail Lights on with DRLs[09 – Cent. Elect.] [Coding - 07] -> Long Coding Helper -> Byte 2 Bit 7 - DRL's via Tail Lets Active (1 = Active) My father lives elsewhere and I haven't connected VCDS to the car yet. I'm trying to search information and good instructions before I try coding the car. Also he would like to have the stop start-button memory. But if I'm not wrong, that can't be done on Yeti either without the memory module between the button wiring? Only thing can be done is to disable stop start by coding some voltage or temperarure limits? It would be great if someone could confirm or/and help with these codings.