2010 Octavia scout 2.0 Tdi (BMM Eng code) 
Hi guys, 

 

 I’ve had a disaster... using my snap on Ethos Edge diagnostic machine on very latest software I’ve killed part of my rear side lights.

 While under the Central Electronics section I performed parking light activation tests numbered 1too 9

“parking lamp activation 1”

“parking lamp activation 2” etc etc etc and since doing this the rear lower side lights don’t work and also only driver side reverse light works, it’s NOT the bulbs as I’ve tested them and it DOESNT show as bulb failure on the dash... I can’t find how to change them back to full rear side lights. Below is a photo of how they are now. Does anyone no what I need to do?? My diagnostic machine as brilliant (but obviously not as good as VAG) and I even managed to activate my front fog lights as cornering lights months ago. I can even code keys using my machine. 
 I had an idea... I copied the settings from a vehicle on the yard another Octavia 2 scout 2013 And the same thing has happened to that. It will let me input codes for adaption channels but I don’t no what code or channel to input to sort this problem. Any help or advice is greatly greatly appreciated. 
thanks guys. And yes I’m going to stop messing around with things I’m not sure of. 

Edited 22 November, 20196 yr by Mick562008
Added photo

Think I may of somehow changed country settings... anybody no how to change it back?? I can input long code in the central electronics but not sure what the code for over here would be (UK)  

There aren't any county settings in the BCM (Body Control Module) which is responsible for controlling the lighting. The only thing I can think of is that either byte 18 in the BCM coding has been messed with or the underlying lighting configuration in the BCM EEPROM has been changed.

 

I can't image why your diagnostic tool would possibly do either during an output test 😕

 

I would try:

- disconnecting the car battery to see if a hard reset helps

- contacting the diagnostic manufacturer to ask what's happening

 

Other than that, you could use VCP or ODIS-e to check the lighting configuration hasn't been messed with.

1 hour ago, langers2k said:

There aren't any county settings in the BCM (Body Control Module) which is responsible for controlling the lighting. The only thing I can think of is that either byte 18 in the BCM coding has been messed with or the underlying lighting configuration in the BCM EEPROM has been changed.

 

I can't image why your diagnostic tool would possibly do either during an output test 😕

 

I would try:

- disconnecting the car battery to see if a hard reset helps

- contacting the diagnostic manufacturer to ask what's happening

 

Other than that, you could use VCP or ODIS-e to check the lighting configuration hasn't been messed with.

Of course, why didn’t I think of a hard reset 🤯🤯

 I’ve been too busy looking for a problem that might not even be there. I will disconnect the battery and then join both cables together to totaly get rid of any ridiculous power so hopefully get rid of any “memory” 

 Thank you langers2k 

I will post the results as soon as I’ve done it. 

Ok so I did the hard re set but no joy... wondering if it’s a setting I changed as I’ve noticed when I open the boot with engine NOT on and only sidelights on as soon as boot opens the rest go off as soon as I close it they come back on, got a video here 

 

That's starting to feel more like a byte 18 issue.

 

I'd be tempted to find a VCP/ODIS user to extract and check the lighting config for you. Looking on the owners list, @James@Pentagon_Seat is your closest but hasn't been online for 18 months.

 

There are a few others on a VCP facebook group map: https://www.google.com/maps/d/embed?mid=1rhkQHDzey_CbYZlosrKDKBQUbFY

On 22/11/2019 at 20:29, langers2k said:

There aren't any county settings in the BCM (Body Control Module) which is responsible for controlling the lighting. The only thing I can think of is that either byte 18 in the BCM coding has been messed with or the underlying lighting configuration in the BCM EEPROM has been changed.

 

I can't image why your diagnostic tool would possibly do either during an output test 😕

 

I would try:

- disconnecting the car battery to see if a hard reset helps

- contacting the diagnostic manufacturer to ask what's happening

 

Other than that, you could use VCP or ODIS-e to check the lighting configuration hasn't been messed with.

Just noticed... mine says byte 80 ??