langers2k

All driving modes will need a colour selected. As mention before, all 16 "Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil" channels need a none zero value. One driving mode can be customised and will use the colour selected in 'manual'. This is done by setting the "Ambiente_Fahrprofil_Individual" channel to that driving mode. In my example, it's set to 7 so "individual" can have the colour changed. This customised colour was the feature I had issue with until the CAN-gateway firmware was updated... If you end up with a disco mode (colour changed twice a second) on the headunit, set "Ambiente_Fahrprofil_Individual" to an unused profile like 6 or 9. You'll loose the ability to set it via manual mode I'm afraid though 😞

I think you've misunderstood what those channels are and what they are doing...? There are 16 channels, called Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_0 to 15. These are the different profiles, each number matches to a specific profile and has no relation to the ordering or availability on the headunit. 0 is always doors open 1 is always comfort 2 is always normal 3 is always sport 4 is always off-road 5 is always eco 6 is always race (cupra thing?) 7 is always individual 8+ I'm not sure about The value of each adaption channel specifies the colour it should use. This is taken from the RGB colour list so the colour shown will depend on how those channels are configured. For my car when I made those notes: 1 is white 2 is orange 3 is red etc etc This will match the ordering of the colour wheel shown in your headunit in 'manual' colour select mode. I think all 16 channels need to be none zero which is why I set all unused profiles to 1.

Yes it's possible. That entirely depends on where you find a steering wheel from... You will need a 3rd party adaptor to make it work properly. Not to my knowledge.

My 2018 car came with ambient lighting and this CAN gateway: Address 19: CAN Gateway (J533) Labels:| 3Q0-907-530-V1.clb Part No SW: 3Q0 907 530 L HW: 3Q0 907 530 C Component: GW MQB High 436 4326 It didn't have the 'automatic' mode for colours to start with. Looking at my notes, I flipped byte 11, bit 7 in the CAN gateway. I then changed these adaption channels in the BCM: channel IDE09731-ENG154513-Int. light: 2nd generation-Ambiente_Farbwahl_FPA_waehlbare_Kopplung adapted from not active to active channel IDE09731-ENG154514-Int. light: 2nd generation-Ambiente_Farbwahl_FPA_waehlbare_Kopplung_Status_hmi_default adapted from active to coupled channel IDE09731-ENG154511-Int. light: 2nd generation-Ambiente_Fahrprofil_Individual adapted from 0 to 7 channel ENG153712-ENG154602-Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_0 adapted from 0 to 1 (doors open) channel ENG153712-ENG154603-Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_1 adapted from 0 to 8 (comfort) channel ENG153712-ENG154610-Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_2 adapted from 0 to 2 (normal) channel ENG153712-ENG154611-Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_3 adapted from 0 to 3 (sport) channel ENG153712-ENG154612-Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_4 adapted from 0 to 1 channel ENG153712-ENG154613-Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_5 adapted from 0 to 9 (eco) channel ENG153712-ENG154614-Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_6 adapted from 0 to 1 channel ENG153712-ENG154615-Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_7 adapted from 0 to 1 (individual) channel ENG153712-ENG154616-Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_8 adapted from 0 to 1 channel ENG153712-ENG154617-Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_9 adapted from 0 to 1 channel ENG153712-ENG154604-Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_10 adapted from 0 to 1 channel ENG153712-ENG154605-Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_11 adapted from 0 to 1 channel ENG153712-ENG154606-Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_12 adapted from 0 to 1 channel ENG153712-ENG154607-Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_13 adapted from 0 to 1 channel ENG153712-ENG154608-Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_14 adapted from 0 to 1 channel ENG153712-ENG154609-Ambientelicht Zuordnung der Farbe zum Fahrprofil-Fahrprofil_15 adapted from 0 to 1 ` There are 15 profiles as that includes all the possible profiles from other cars as well, for example offroad, race and snow etc... At this point, the ambient lighting, dashboard and headunit colours would change when I changed drive mode. The only issue was individual mode would cause a disco effect and constantly change between two colours. To fix this, I had to flash the CAN gateway firmware (and parameterise it). After the update it became: Address 19: CAN Gateway (J533) Labels:| 3Q0-907-530-V1.clb Part No SW: 3Q0 907 530 Q HW: 3Q0 907 530 C Component: GW MQB High 436 4344 Once this was complete, all modes including individual work as expected For reference, my BCM is: Address 09: Cent. Elect. (J519) Labels:. 5Q0-937-08X-V2.clb Part No SW: 5Q0 937 084 CQ HW: 5Q0 937 084 CG Component: BCM MQBAB H H36 0253

On my MY18 Octavia, I had to upgrade the CAN gateway firmware to get ambient colours from driving modes working correctly... Iirc, it needed 4344 or higher which translates as a Q rev.

Honestly, hard to tell as it's a very subjective thing... I'd probably say it's a little softer and harder than before but I don't think there is much in it, especially as I'd typically be in normal previously so I don't have a decent baseline. I've tried a few settings today and settled about half way between normal and sport. I was hoping for more granularity rather than being able to set it softer or harder so I'm happy at that

Well that was all surprisingly easy... Flashed the DCC module: Uploaded the Passat dataset (closest in size, weight and wheelbase to the Octavia): I already had my CAN gateway dataset from when I updated the firmware to support automatic colours per driving mode. Tweaked it as per the drive2 instructions I posted previously along with MQB-FPA. Uploaded the dataset: Cleared all the error codes, rebooted the headunit and was greeted by this: VCDS confirmed via measuring blocks the active DCC profile changed from 1 to 15 with the slider and that eco/comfort/normal/sport had sensible values. Took it for a 2 minute drive and everything feels to be working normally, happy days! Massive thank you to @ApertureS for the dataset

FL_5Q0907376C__0130.odx looks like an ODIS flash file. FL_5Q0907376C__0130.xml is basically identical, a name field changed from Henno to Stephan Pölzl. leon_dcc_5q0907376b.xml is slightly odd, it's not a ODIS XML dataset file, it might be some VCP thing as it appears to contain a number of different datasets... The missing part is still a publicly available C rev dataset, the B rev won't work

The firmware is likely generic, it's the dataset that's the harder part to find. Thanks though! I'll compare it to the thing I have...

Genuine ODIS with an online connection can pull appropriate datasets but afaik, it can only typically get datasets for modules originally installed for a VIN. Once updated, it'll no longer be a valid config and it'll refuse to provide a dataset. I've seen mention of the ZDC but I've never seem a copy online, they also tend to be encrypted to avoid cloned/pirated VCP interfaces so even if I did find it, I probably can't convert it for use with ODIS. Saying that, I literally just found what appears to be an ODIS XML on a random site: https://bbs.vwodis.com/forum.php?mod=viewthread&tid=31 Annoyingly, it is behind a paywall... I think 19000 'credits' are 190 CNY or ~£24 or 40 AUD although I'm not sure what payment methods they accept. Feels slightly dodgy but I might try and buy it later. As for the update file, that's available via one of the normal sources for this kinda stuff: https://mibsolution.one/#/1/9/Datasets/MQB/14 I haven't tested or verified it's legit. From what I can see, VAG never released this update

Alas the only part he shared was a gateway dataset. I assume he tweaked it in a similar way to this Russian chap: https://www.drive2.ru/l/604209952961078465/ I found what appears to be a C rev flash file but I've never found a dataset to go with it. I don't use VCP so I can't just grab their version 😞 I was hoping there might be an ODIS xml dataset floating round by now given it seems to be becoming a more well understood/popular tweak.

Might be worth messing this person: https://www.golfmk7.com/forums/index.php?threads/dcc-retrofit.378431/page-13#post-7863727 Seems they are collecting a few datasets at the moment, hopefully they'll put them all online soon. If you come across a C rev Arteon or B rev Octavia dataset it would great if you can post them here

Different part numbers as they are different parts Taking a look at the hatch/estate in the latest brochure, the angle the boot lid intersects looks very different and would explain the need for alternative parts.

A very quick google later for MIB pinout... FBAS 1 IN+ and the IN- are the reversing camera input. The other pins are pretty self-explanatory on the image below. I have no idea if you can connect both headhunts at the same time, I expect you may get some strange behaviour as both will be sending CAN-bus messages and may cause conflicts 😕

More likely to be the seat controller then needs updating... There is a tpi, it's the third one in my post here:

The official source is Erwin: https://erwin.skoda-auto.cz The headunit uses CAN-bus for the power on/off messages so there is no longer a switched ignition feed. Googling for a mib2 quadlock pin out will give you the basics like power, ground, CAN high and CAN low pins.

2049697/6 is about the GPS antenna but I imagine similar damage could occur to a dab connector.

There is a tpi regarding loose/damaged fakra connectors. The fix being to bend the outer metal connectors slightly to make a better connection 🤔

It'll very much depends on what cars and the generation of immobiliser. You might want to give some example of the year and models you're interested in 👍

Ease of manufacturing Rather than making 8 different hardware of each combination: - no assists - high beam assist (HBA) only - lane assist (LA) only - traffic sign recognition (TSR) only - HBA and LA - HBA and TSR - LA and TSR - HBA, LA and TSR They can fit one of the following 3 and turn the different options on or off depending on the car spec via software. - no front camera - 'lowline' camera capable of HBA only - 'highline' camera capable of HBA, LA and TSR The vRS got LA as standard so gets the 'highline' camera which means it's relatively easy to enable the other two features. Things are changing to make it harder. For example somewhere around 2019/20 the 'highline' camera was updated so it's no longer trivial to enable TSR. It now requires an appropriate licence/FeC/SWaP code which Skoda/VAG don't sell separately. New cars have SFD (Vehicle Diagnostic Protection) so you need a code from VAG to unlock a module before it'll accept any changes...

Given the part number starts 3V0, they are probably specific to the MK3 Superb...

Can you take a picture? Both the center console and boot ones work in my car and I'm not aware of any blanks... Might just need a new fuse at a guess.

Looks like the modules are still in the same place so it's plausible: https://www.ebay.co.uk/itm/115390854396 Part number has changed and now seems to be 8U0 941 329. Given you have extra lights fitted, I'd also be checking the wiring to the headlight to make sure it's not been messed with or damaged...

At a guess, 7L6 941 329 B but please check before ordering anything... You can see it on the underside of this headlight: https://www.ebay.co.uk/itm/234628708777

Corrosion on connectors for the module under the headlight due to water ingress would be my guess 😞 If you're lucky, you can clean it up and possibly replace the module.