langers2k

Have you got the adaption map to go with that?

Go to address 19, OBDeleven should be able to confirm the hardware/software versions

I thought DCC was a SWaP/FeC thing in the can gateway. Do you have any errors shown by VCDS? Which gateway have you got? Maybe it's too old to properly support the MIB2.5...?

That nozzle looks like the one fitted to the camera rather than the rear wiper

Pretty sure I also used ODIS-E too

I think it's similar to the MK2? If so, the cover will flip up and you can move the entire nozzle slightly, for more fine tuning, you can use a pin or similar to move the metal jets in the plastic housing.

Calibration is easy enough with ODIS but I don't think it's possible with VCDS. At least I couldn't do it Few pictures from when I calibrated mine:

Yup, for bog standard ACC it's all done by the radar unit. If you want some of the more advanced features like traffic jam assist/follow-to-stop, then you'll need both the radar and a highline camera capable of lane assist etc. Be warned, some radar units will only support front assist (emergency braking) and not ACC. Retrofitting ACC is not cheap, you're going to need a suitable radar unit, replacement stalks, possibly wiring and then you need to deal with component protection, any applicable FeC/SWaP codes and other coding...

ACC doesn't use the camera... It uses the radar behind the front grill.

If I were you, I'd take the cluster off and fully dry it out. Then check the lamp for any cracks/damage and inspect the seal. Assuming it's all fine, refit the cluster but make sure the wiring sits inside the car body and isn't preventing the seal from making a good connection with the car body.

Erm, not sure if you can do it via the Columbus. I'm sure there is a map delete CD somewhere for the Columbus. Otherwise, if you have some older maps you could try installing them. I haven't got a Columbus to play with anymore so it's hard to give more concise instructions I'm afraid.

The pre-fl lights are the wrong shape for a FL bumper... You either need to swap everything or customise the bumper so it'll fit your lights.

The part number you want is on the face of the mirror motor. You can see if in yellow here:

I doubt you'll get any warning lights from unplugging the bt module 👍

Unplug the BT module. It's probably under one of the front seats...

From the user manual: Yup, 57 is one above 56. Example autoscan with a Columbus (37 and 56) and TV tuner (57) installed: https://forums.ross-tech.com/index.php?threads/12823/

EQ settings tend to be a very personal thing, move the bars and see what sounds best to you

You know you have it as you can watch TV It's a separate device, I think it lives behind one of the boot panels. It should also show up as a module during a diagnostic scan, address 57 if I remember correctly.

Given your posts so far, I'd suggest you just grab a genuine card, they aren't expensive. Changing the CID is easy if you have the right knowledge, tools and SD. At least when I last did it, you needed: - a basic knowledge of linux and it's command line - a laptop with a 'real' SD card reader (not internal or external USB) it should show as /dev/mmcblkX (not /dev/sdX) - a suitable Samsung SD card (I believe they fixed the 'bug' that allowed CID changes in late 2017...) I believe you can also do it via an Android app called "SD Insight" but I've never used it and will only support certain phones. Couple of links that might help: - Thread with some suggested CID's for a MIB1 headunit: https://cartechnology.co.uk/showthread.php?tid=33768 - Youtube video of someone changing the CID: https://www.youtube.com/watch?v=tbWXsSaAb2M Good luck.

Yup, should be fine using VCDS, certainly worked on 20.4.2.0 when I updated my headunit. Quick google...

Please read my previous replies! The only difference between a 'genuine' and 'non-genuine' SD card is the CID. - If you have a SD card that allows you to change the CID, then do that - If not, buy a genuine card with the correct CID

The software version error can be cleared using VCDS or OBDeleven... No need for ODIS 👍

You're having issues trying to get navigation working on a retrofitted Amundsen. The way this works on a stock system is the headunit checks the SD card CID is valid. The CID is basically like a serial number that's programmed into the SD card which is designed to be one time programmable and unchangeable. This means you have three choices to get nav working (as far as I'm aware), you can either: - use a genuine Skoda/VW SD card - use a non-genuine Skoda/VW card with the CID changed to match a genuine card (only works on very specific SD cards!) - hack the headunit to accept all SD card CID's I believe you're trying to use a non Skoda/VW SD card? This won't work unless you either change the CID or hack the headunit... The second question is how did you get component protection removed? If a dealer did it, there is a good chance navigation won't work as a dealer can only activate features listed against your VIN which won't include navigation. Obviously if this is a hacked headunit then this shouldn't be an issue.

I don't think the VC software supports needle sweep. At least based on a few threads over on the VCDS forums where people have asked, sorry...

The two links are for the MK2. However, the two methods mentioned, (changing card CID or hacked firmware) are both valid for the MK3. How did you have component protection and the features enabled on your Amundsen? If it was a dealer, you might find satnav won't work as your cars VIN doesn't have entitlement for satnav... Can you confirm if you're using a genuine Skoda/VW SD card?