Hi,
 
2 questions for all you VCDS experts out there.
 
I plugged my new MY16 Octavia VRS  into VCDS for the first time and started to try coding some of the possible adaptations.
 
the first 3 worked (changing the throttle mode to audi, showing blower speed on auto and switching off the sound generator) and I was able to follow the instructions fairly easily, however when I started to try and code other functions I was getting errors.
 
On trying to change the voltage for the Start/Stop system i followed the instructions:

 

 

 

Go to Module 19 (Can Gateway)
· Adaption
· Go to Kanaal: Start_stop_voltage_limit
· change to 12.1V ( standaard is 7.6V)

 

however when i came to apply the new voltage i get an error message saying the value is out of range.

 

I also had this on the first stage of enabling Traffic sign recognition.

 

 

The next issue is when it comes to enabling the intelligent light assist.  I followed the instructions provided by Andyvee and there was a slight descriptive difference in channels, however the coding was accepted.  When i came to activate light assist however (by pushing the stalk forward) I received a maxidot error "light assist error".  Is this because I was stationary?  I have now reverted all changes for the light assist to standard

 

EDIT:  I forgot to sya I'm using version 15.7.4. should I try again with one fo the newer betas?

 

EDIT 2:

 

I've just found this from Andyvee:

• The latest beta of VCDS has a tick box for a soft controller reset when changing adaptation channels - this is a feature I asked Ross Tech to add for a reason, it is needed on MQB platform cars, so use it!

Just to confirm, should I be ticking the box at the same time as changing the channel?

Edited 21 May, 201610 yr by octaviaconvert

Light assist should work the moment the lights are turned on, irrespective of whether you are moving or not.

 

What was the difference in the channels? 

 

When was the car built? if after July 15 then the Beta may help 

Thanks,

 

the car was built on the 6th May, so I'll download the latest beta and try again.  I've been resetting the coding as Ive going along.  Next time I try it I'll try and do screen grabs as I go just in case of any issues. As for the out of range errors, I found by doing soft resets and coming out of controllers before goign back fixed that issue