Question is:

If VCDS is unable to handle the coding from MIB2 units ( writing all the zeroes in my case), is it able to read them correctly??

Cause if I understand VCDS right... The first autoscan saves your Long codings for all the ECU's, so in case you make a mistake, you can just program it back to standard with those codings.

This is what I tried to do, and according to the autoscan, they were coded like before, but no changes were made and my menu's were still gone.

The changes that we made (well at least I) were not in coding, but in adaptation channels, so you theory is not really correct in this case.

As I said, I'm no expert, but for me it looks like the adaptation channels are a visual (and explained with labels) representation of the coding or not?

As I said, I'm no expert, but for me it looks like the adaptation channels are a visual (and explained with labels) representation of the coding or not?

That is pretty much spot on - a 'section' of adaptation channels are in effect a hex string coded to a memory address. These need a 'map' to be interpreted as the text values we see in VCDS.

Thx for explanaiton will keep this in mind...

Is it fixed on new release 15.7.2 ?

Who knows - I can't find a changelog for 15.7.2

 

BUT, Dana indicated that they would look at the fix after Thanksgiving, so yesterday basically. I would be surprised that it was modified, tested and released in a day

 

I think we are more likely to see a 16.x beta .........

Looks like some progress has been made over on Ross tech forum

 

:clap:

That is sounding promising (what are performance gauges?!)

Still a bit confusing about how to diagnose and "fix" a car after it has list menus though. @Andyvee are you back up in Scotland again soon?

Still a bit confusing about how to diagnose and "fix" a car after it has list menus though. @Andyvee are you back up in Scotland again soon?

Easy: get similarly equipped car (ideally would be identical, but this could be a long shot ) and do ad. channel map ob both cars and then compare each line. Of course you have to use a big grain of salt (due to equppment differences).

 

Performance Monitor:

Easy: get similarly equipped car (ideally would be identical, but this could be a long shot ) and do ad. channel map ob both cars and then compare each line. Of course you have to use a big grain of salt (due to equppment differences).

Performance Monitor:

Don't think they will work on an octavia then.

That is sounding promising (what are performance gauges?!)

Still a bit confusing about how to diagnose and "fix" a car after it has list menus though. @Andyvee are you back up in Scotland again soon?

Friday 11th but just for the day .....

Sent from my HTC One_M8 using Tapatalk

Well I can confirm that with the 15.7.3 Beta I have been able to get most of the things lost back (everything I have tried) Mirrors, Green menu, consumers, still a couple of outstanding things (same as mtl has) still to do but at least there is a bit of hope we have the tool to do the job when we work out in full what was lost and how to put it back. Good effort by all involved 

 

Next to find out how to get the Performance Gauges working on a MiB2 Columbus   

Edited 5 December, 201510 yr by flybynite

Well I can confirm that with the 15.7.3 Beta I have been able to get most of the things lost back (everything I have tried) Mirrors, Green menu, consumers, still a couple of outstanding things (same as mtl has) still to do but at least there is a bit of hope we have the tool to do the job when we work out in full what was lost and how to put it back. Good effort by all involved [emoji106]

Next to find out how to get the Performance Gauges working on a MiB2 Columbus

Any chance of a guide on what you reenabled (and how?)

http://forums.ross-tech.com/showthread.php?4343-Support-for-5F-MIB2-Columbus-amp-Amundsen-on-MY16-Octavia-III&p=45734&viewfull=1#post45734

Any chance of a guide on what you reenabled (and how?)

 

Unless you are in a real hurry I would wait for 15.7.3 final to come out as the more I look at it things it may still not be 100% on the Beta. Either this release still does not read the map correctly or the early version did more damage than I thought.

Unless you are in a real hurry I would wait for 15.7.3 final to come out as the more I look at it things it may still not be 100% on the Beta. Either this release still does not read the map correctly or the early version did more damage than I thought.

Thanks, yeah plenty of time to make sure the changes are made right this time! Not going to be the first one to test it for sure.

(Thanks for those who are though!)

Edited 6 December, 201510 yr by Iamholam

Unless you are in a real hurry I would wait for 15.7.3 final to come out as the more I look at it things it may still not be 100% on the Beta. Either this release still does not read the map correctly or the early version did more damage than I thought.

Feed your findings back to RT

Not going to be the first one to test it for sure.

 

Yea, best that we all wait, maybe Santa will generous this and year and get us the solution.

 

Sorry, but I had to...

Edited 6 December, 201510 yr by mtl

What version of VCDS is causing this problems?

I have 15.7.0 and I hope not to have problems of missing menus or other things less visible...

Do you know what versions are concerned or is something strange between all the VCDS and the new MIB2 ?

 

Thanks and hope for the best!

You need 15.7.3 beta.

Sent from my HTC One_M8 using Tapatalk

With 17.5.0 I've got not problems. i have made adaptation by adaptation, note many at once. Always checked few times my choice and keep attention at the confirmations.

 

I can't understand how VCDS can change something by his own wish... If so, maybe it changed something in ECU too...

Ross Tech can't reproduce? Maybe there were some operation errors, done by users?!

 

I am afraid not to have any surprise so after reading those experiences. And now, I am in stand-by... 

What cable do you have - micro CAN or HEX-CAN?

The issue is a buffer overflow on hex-can cables.

Do not under any circumstances use a hex-can on MIB2 units unless you are running 15.7.3 beta.

Sent from my HTC One_M8 using Tapatalk

I do not know exactly, but I think it is HEX-CAN USB. No problem until now, but I just tried the following adaptions:

 

Lap Timer - not worked

Tear Drop wipe front windscreen - not worked

DRL off when Handbrake is engaged - Ok

Delay for trunk lock when unlocked from hey - Ok

SOC in dashboard showing ---% - tried to make it show a value by introducing battery type, manufacturer, serial no... - but still not showing a percentage value

Needles staging - Ok

 

Is it possible that anything else can be affected, like ECU, or other modules?

 

PS: never try soft-reset from VCDS, and even I did not reset nothing from Bolero MIB2.

Well I think I am getting somewhere, I have been able to get back most of what I see as missing with the really helpful postings of maps so far on the VCDS forum.

 

Mirrors and wipers menu using

(166)-Car_Function_Adaptations_Gen2-menu_display_car_mirror

(168)-Car_Function_Adaptations_Gen2-menu_display_car_mirror_over_threshold_high

(27)-Car_Function_List_BAP_Gen2-mirror_0x0E

 

Convenience Consumers menu using

(181)-Car_Function_Adaptations_Gen2-menu_display_BCmE 

(183)-Car_Function_Adaptations_Gen2-menu_display_BCmE_over_threshold_high

(67)-Car_Function_List_BAP_Gen2-BCmE_0x23

 

DriveGreen menu with

(186)-Car_Function_Adaptations_Gen2-menu_display_user_eco_rating

(188)-Car_Function_Adaptations_Gen2-menu_display_user_eco_rating_over_threshold_high

 

ESC system menu with

(191)-Car_Function_Adaptations_Gen2-menu_display_Brake_Function

(193)-Car_Function_Adaptations_Gen2-menu_display_Brake_Function_over_threshold_high

(73)-Car_Function_List_BAP_Gen2-Brake_0x26

 

Proactive occupant protection (Precrash) with

(141)-Car_Function_Adaptations_Gen2-menu_display_reversible_belt_pre_load

(143)-Car_Function_Adaptations_Gen2-menu_display_reversible_belt_pre_load_over_threshold_high

(73)-Car_Function_List_BAP_Gen2-Brake_0x26

 

(I am not sure how common this last one is as it was an option I specc'd which I am glad to have back)

 

As an aside, tried to stop the xenons comming on as CH/LH lights, it took the adaptions, all with a soft reset but does not seem to have had any effect. Anyone done this successfully on a MY16?

I've answered in the other thread about the CH/LH - pull an adaptation map from 09 and post up the full relevant channels