Support for 5F MIB2 Columbus & Amundsen on MY16 Octavia III

[andyvee]

Hi guys

Not sure if you are aware, but there are reports of menus disappearing from 5F on MIB2 units on the O3 after enabling some additional menu items. I haven't experienced it myself yet, but there are a couple of reports on Briskoda

http://www.briskoda.net/forums/topic/374919-my16-mib2-coding/

http://www.briskoda.net/forums/topic/369927-vcds-cant-enable-driver-alert-system/

 

[SBC Auto]

I have had this problem and along with others and have sent this to RossTech support but as yet no response. There are other issues but I will concentrate on one of the missing menus as I am certain this one was there prior to coding and demonstrates the problem

A controller map of 5f prior to any coding on that controller shows both
(166)-Car_Function_Adaptations_Gen2-menu_display_car_mirror
(168)-Car_Function_Adaptations_Gen2-menu_display_car_mirror_over_threshold_high
As "not activated". Even though at the time the menu was present and functioning in infotainment.

Coding was done in 5f to enable
1. Traffic sign recognition
2. Automatic daylight saving time
Saved and soft reset of the controller

After this the menu for "mirrors" had gone from infotainment.

One person has had success changing the above adaptions back to "activated" and recovered the menus however I did not

When I tried to place the above adaptions to "Activated" it said the coding had been accepted, the log shows the coding as accepted but the adaption stays as "not activated" and menu stays missing

As has been said in another forum, either VCDS 15.7.1 cannot correctly read the adaptions in the MY16 MIB2 units or the Columbus unit is storing its coding for the menus somewhere other than 5f.

 

[Dana]

Andyvee thanks for the link!

We are aware of this concern and received 2 emails that I'm aware of to date, including the one from from SBC Auto. Andy Smith's Mk7 has MIB-I installed but we believe MIB-II will be available in our market pretty soon ... which will allow us to look into this.

 

[SBC Auto]

Andyvee thanks for the link!

We are aware of this concern and received 2 emails that I'm aware of to date, including the one from from SBC Auto. Andy Smith's Mk7 has MIB-I installed but we believe MIB-II will be available in our market pretty soon ... which will allow us to look into this.

Thanks for acknowledging the problem Dana, it is the not hearing anything that was becoming an issue.

As far as I am aware MIB2 should have arrived Stateside with VW at the same time as it arrived this side of the Atlantic. VW cars delivered after June/July should be fitted with MIB2 units (same as here) and I did see a VW with Carplay in the States myself last month which I assume was MIB2.

Hope you can understand that the nature of this problem means that I have lost a little faith in VCDS and I'm sure I am not alone. Whatever we can do to help solve this I am sure we can collectively supply more information if needed.

 

[Eric]

Does this happen only on Skodas as far as you know?

 

[SBC Auto]

Does this happen only on Skodas as far as you know?

That I don't know for sure, It is finding someone with a new, high-spec VW that has coded 5f that knows their system well enough to realise other things in their system are now missing. Maybe that is just more likely with a Skoda! More will come it is just a matter of time as more of these cars get about and people know them better

Unfortunately I am not going to find many volunteers with a new VW to let me code their car knowing it may make permanent unwanted changes on their £2000 discover pro

The Discover Pro has the same menu functions as the Columbus as far as I can see so I cannot see it being any different from that or in fact any "(Gen2) Radio-High" unit.

The way you can find out if the cars you can get to are having the problem is to get an adaption map on 5f and compare it to what has been activated on the car from the factory. This SHOULD not cause any issue to the car in question

As said above, on mine on an initial adaption map of 5f prior to any coding (others found this to)

(166)-Car_Function_Adaptations_Gen2-menu_display_car_mirror
(168)-Car_Function_Adaptations_Gen2-menu_display_car_mirror_over_threshold_high

Were both showing as "not activated" although the menu function on the unit was certainly there and working with the three items in the menu

Synchronous adjustment
Lower while reversing
Fold in when parked

If the adaption map does not reflect the car as it is specc'd from the factory then it seems to be susceptible to this problem. It is as if VCDS is not reading the adaptions correctly and then saving those mis-readings to the map when any other changes are made.

Everything is in the logs I sent to Andy but what cannot be logged is the change and loss in the infotainment menus. I can send in "after" screenshots if it helps and probably get "before" from someone else

To be clear it is making other unwanted changes, this is just the one I am very clear on.

 

[Eric]

Thanks. We should have a 2016 Passat to scan soon and that should help us decide if we want this car in a more "permanent" fashion. This is not going to be something I can fix sitting in the dealer's lot, and nobody has volunteered to send us their broken MIB2 yet

 

[DV52]

As said above, on mine on an initial adaption map of 5f prior to any coding (others found this to)

(166)-Car_Function_Adaptations_Gen2-menu_display_car_mirror
(168)-Car_Function_Adaptations_Gen2-menu_display_car_mirror_over_threshold_high
.

SBC Auto: not sure if it helps, but HERE is a database of admaps from a number of J794 units.
As you can see, the settings for the two adaptation channels that you mention above are "activated" (look at ID #477 and 479).

Don

 

[SBC Auto]

SBC Auto: not sure if it helps, but HERE is a database of admaps from a number of J794 units.
As you can see, the settings for the two adaptation channels that you mention above are "activated" (look at ID #477 and 479).

Don

This may be starting to get to the cause of the problem If these maps came of MY2015/ MY2015.5 as I suspect

Line 477 and 479 that you point to are showing as what I assume is MIB1 adaptions
(166)-Vehicle menu operation-menu_display_car_mirror
(168)-Vehicle menu operation-menu_display_car_mirror_over_threshold_high

It ALSO shows
(166)-Car_Function_Adaptations_Gen2-menu_display_car_mirror
(168)-Car_Function_Adaptations_Gen2-menu_display_car_mirror_over_threshold_high
Lines 687 and 689 further down

I don't know if all the above adaptions come from the same car but My car ONLY shows the "Gen2" adaptions/Function List

My car has
(27)-Car_Function_List_BAP_Gen2-mirror_0x0E
Which I cannot find in the adaption maps you linked to - only
(27)-Vehicle function list BAP-mirror_0x0E

ALL the function list BAP / car function Adaptions are "Gen 2" there are non of the old ones in there VCDS will not change some of the the "Gen2" adaptions

The problem is with MIB2 (Gen2) cars that are at most a month or 2 old

 

[DV52]

This may be starting to get to the cause of the problem If these maps came of MY2015/ MY2015.5 as I suspect

Line 477 and 479 that you point to are showing as what I assume is MIB1 adaptions
(166)-Vehicle menu operation-menu_display_car_mirror
(168)-Vehicle menu operation-menu_display_car_mirror_over_threshold_high

It ALSO shows
(166)-Car_Function_Adaptations_Gen2-menu_display_car_mirror
(168)-Car_Function_Adaptations_Gen2-menu_display_car_mirror_over_threshold_high
Lines 687 and 689 further down

I don't know if all the above adaptions come from the same car but My car ONLY shows the "Gen2" adaptions/Function List

My car has
(27)-Car_Function_List_BAP_Gen2-mirror_0x0E
Which I cannot find in the adaption maps you linked to - only
(27)-Vehicle function list BAP-mirror_0x0E

ALL the function list BAP / car function Adaptions are "Gen 2" there are non of the old ones in there VCDS will not change some of the the "Gen2" adaptions

The problem is with MIB2 (Gen2) cars that are at most a month or 2 old

SBC Auto:

HERE you go - an admap from a MIBII unit showing (27)-Car_Function_List_BAP_Gen2-mirror_0x0E. The admap is from one of our "true-blue" Aussie - German made vehicles - a MY16 110TSI Highline mk7 Golf. Hmm... I can't remember when I got his admap, but I would have thought that it was longer than a couple of months ago - I could be wrong!!
Don

PS: I believe that the admap was taken from a "virgin" control module - that had had no changes made to its settings
This notwithstanding, the 2 x adaptation channels that you mentioned in your previous post
(166)-Car_Function_Adaptations_Gen2-menu_display_car_mirror
(168)-Car_Function_Adaptations_Gen2-menu_display_car_mirror_over_threshold_high
have the setting not activated . I don't know why - perhaps the good folk at RT can explain?

 

[SBC Auto]

SBC Auto:

HERE you go - an admap from a MIBII unit showing (27)-Car_Function_List_BAP_Gen2-mirror_0x0E. The admap is from one of our "true-blue" Aussie - German made vehicles - a MY16 110TSI Highline mk7 Golf. Hmm... I can't remember when I got his admap, but I would have thought that it was longer than a couple of months ago - I could be wrong!!
Don

PS: I believe that the admap was taken from a "virgin" control module - that had had no changes made to its settings
This notwithstanding, the 2 x adaptation channels that you mentioned in your previous post
(166)-Car_Function_Adaptations_Gen2-menu_display_car_mirror
(168)-Car_Function_Adaptations_Gen2-menu_display_car_mirror_over_threshold_high
have the setting not activated . I don't know why - perhaps the good folk at RT can explain?

Yes this is exactly the problem. It would be helpful to know if he had the "Mirrors" menu to start with in the discover/pro, and if it is still there if any coding was done on 5f. It does at least show the VW does some of the same things as the Skoda

Those mirror channels are not being read correctly, any 5f coding and the car will then reflect those settings. i.e the menus become 'not activated' and will disappear. I was then unable to code them back manually. Although VCDS says coding accepted the adaption will not change

 

[DV52]

Yes this is exactly the problem. It would be helpful to know if he had the "Mirrors" menu to start with in the discover/pro, and if it is still there if any coding was done on 5f. It does at least show the VW does some of the same things as the Skoda

Those mirror channels are not being read correctly, any 5f coding and the car will then reflect those settings. i.e the menus become 'not activated' and will disappear. I was then unable to code them back manually. Although VCDS says coding accepted the adaption will not change

SBC Auto: Gee you sure do ask the big questions- LOL! The answer is I don't know what mirror set-up was on the screen when new, but here is the pertinent information about the mirror set-up on the car:


Address 42: Door Elect, Driver (J386) Labels: 5QX-959-X93-42.clb
Part No SW: 5Q0 959 593 E HW: 5Q0 959 593 B
Component: TSG FS 020 0041
Serial number: 190515BEJ01869
Coding: 003A13208001048000001000
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_DCUDriveSideEWMAXKLO 006003
ROD: EV_DCUDriveSideEWMAXCONT_AU37.rod
VCID: 438E883CCA647F2608-8016

Subsystem 1 - Part No SW: 5Q0 959 812 HW: 5Q0 959 812
Component: FOND_FHSG_DRV 005 0005
Serial number: 00000000000006280499
Coding: 0D0000

Address 52: Door Elect, Pass. (J387) Labels: 5QX-959-X92-52.clb
Part No SW: 5Q0 959 592 E HW: 5Q0 959 592 B
Component: TSG BFS 020 0041
Serial number: 130515BED10417
Coding: 003A11208E01048000801000
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_DCUPasseSideEWMAXKLO 006003
ROD: EV_DCUPasseSideEWMAXCONT_AU37.rod
VCID: 42808D38D57E762E03-8016

Subsystem 1 - Part No SW: 5Q0 959 811 HW: 5Q0 959 811
Component: FOND_FHSG_PSG 005 0005
Serial number: 00000000000006330032
Coding: 150000

The specific information about the mirrors is in Byte 4 as can be seen from the pictures below which come from my car. But my car has the same Hex value for Byte 4 as the Gen2 model.
Cheers
Don

 

[SBC Auto]

DV52 : Many thanks for all the help it has been useful if only to prove it affects VWs as well, but I have to admit I am still in the dark about what is causing this problem and as I don't know the inner workings of VCDS I think we are all going to be stabbing in the dark. The only people that will have the answers are Ross Tech.

I think that it is safe to say that until this is fixed coding anything on 5f on a car which has MIB2 (Gen2) will result in problems and is best avoided. There are over half a dozen menus that go including those that control the ESC so not insignificant.

Once VCDS can accurately read and code 5f on these machines then we can begin to try to unpick the un-requested and un-logged changes it made. This will take a lot of time as the adaption map taken at the start is no help as it is not accurate and could be the cause of the problem.

The only other way of correcting the problem has been a main dealer factory reload which will obviously not be covered by any warranty and is likely not be the cheap or easy option.

It is a case of waiting until VCDS is working or people going cap-in-hand to the dealers

 

[garyp]

Are there any updates on this yet?

Cheers

 

[Uwe]

Nope, no updates to this yet. We still don't have access to a car with any kind of MIB2. Moreover, it appears the MIB2s we'll be getting in NAR will be rather different than the ones in these Skodas.

Look, I hate to sound unsympathetic, but these systems are only found in MY 2016 cars and you guys are all using VCDS version 15.x... I'll only hang my head in shame if this is still an issue when we have a version 16 Release.

-Uwe-

 

[Andy]

FYI, per VWoA the 8-inch MIB-II is only found in the e-Golf in SEL Premium trim:

https://media.vw.com/release/1038/

e-Golfs are only sold in some states, and Pennsylvania is not one of them:

http://www.vw.com/models/e-golf/

Sorry, the e-Golf will be available only at participating dealers in California, Conneticut, Maine, Maryland, Massachussetts, New Jersey, New York, Oregon, Rhode Island, Vermont, and Washington, DC.

Coincidentally, mostly the same states shown here:

https://en.wikipedia.org/wiki/Concealed_carry_in_the_United_States#May-Issue

The following are "may-issue" states by law: California, Connecticut, Delaware, Hawaii, Maryland, Massachusetts, New Jersey, New York, and Rhode Island.

 

[Uwe]

So is there an e-Golf available at a dealer less than 100 miles from us? I.e. in New Jersey? And would any of us actually be willing to say baahhh long enough to go to NJ to get it?

-Uwe-

 

[andyvee]

Can we offer any asistance? A team viewer session or similar on to a laptop hooked up to a MY16 car with a MIB2 in it?

Appreciate there is a time difference etc. but if there is any way we can help

 

[Sebastian]

Is this really MIB2 related or is it the specific vendor the unit comes from? If so, what part numbers and hardware/software are affected? Is it all MIB variants or just the High? What about Entry and Standard? Has this been tested/confirmed with Audi units in the A6/A7 MY 2016 as well? I would assume those are out in the US and possibly easier to come by...

 

[Andy]

So here are some of the ones that customers have reported as having this problem:

Address 5F: Information Electr. (J794)       Labels: None
   Part No SW: 3V0 035 043 A    HW: 3V0 035 043 
   Component: MU-H-N-EU     H42 0318  
   Serial number: A436F0F7506097
   Coding: 03840101000000001111000200000A002F0000E4012001009E
   Shop #: WSC 33361 790 00076
   ASAM Dataset: EV_MUHig4CGen2HBAS 001001
   ROD: EV_MUHig4CGen2HBAS_SK37.rod
   VCID: 2959AFB9484D68762A-807C

Address 5F: Information Electr. (J794)       Labels: None
   Part No SW: 3G0 035 044 B    HW: 3G0 035 044 
   Component: MU-H-TN-EU    H42 0317  
   Serial number: A597H0F7553675
   Coding: 02840101FF00000051110001000808101F0106E4012000009F
   Shop #: WSC 05311 115 00094
   ASAM Dataset: EV_MUHig4CGen2HBAS 001001
   ROD: EV_MUHig4CGen2HBAS_VW48.rod
   VCID: 1C37866D171F8DDEA1-8048

Address 5F: Information Electr. (J794)       Labels: None
Part No SW: 3V0 035 020 A    HW: 3V0 035 020 
Component: MU-H-ND-EU    H42 0318  
Serial number: A435F0F7508164
Coding: 03730201FF00000011111201008800002F0000D601208100FE
Shop #: WSC 73430 790 00063
ASAM Dataset: EV_MUHig4CGen2HBAS 001001
ROD: EV_MUHig4CGen2HBAS_SK37.rod
VCID: 2447D64B2FF0F31E19-8070