langers2k

The radio has a long coding and some adaption channels. Ideally you need to copy the long coding and all adaption channels from the old radio to the new. This is pretty easy with VCDS assuming you have an autoscan and adpmap. However, I've never used OBDeleven so I can't add any specific steps I'm afraid

TSR works perfectly with my Amundsen (MIB2.5) Well, aside from it thinking some stretches of dual carriageway are 60 rather than 70...

If it's the same unit, copy the entire coding...

You can potentially have the same issues with any incorrectly coded unit... Maybe check your OBDeleven history for previous scans..?

I've been tempted but I'll give it six months from release to iron out teething issues 👍

It's the current driving mode. Cogs mean individual

You should have a few adaption channels like this: [19 - CAN-Gateway] [Adaptation - 10] Battery adaptation - Size (this may be something like IDE03256-MAS04490 Battery adaptation - Size) Select the battery Ah rating from the drop-down menu followed by [Do It!] and confirm [Yes] Battery adaptation - Manufacturer (this may be something like IDE03256-MAS03159 Battery adaptation - Manufacturer) Select the battery manufacturer from the drop-down menu followed by [Do It!] and confirm [Yes] Battery adaptation - Serial number (this may be something like IDE03256-IDE00010 Battery adaptation - Serial number) Type the serial number code from the replacement battery followed by [Do It!] and confirm [Yes] The Ah should be set correctly. The manufacturer and serial number don't matter too much, as long as the serial is different to the previous battery For example, mine are currently: IDE03256-MAS06105-Battery adaptation-Rated battery capacity,69 Ah IDE03256-MAS06106-Battery adaptation-Battery technology,EFB IDE03256-MAS06107-Battery adaptation-Battery manufacturer,JCB IDE03256-MAS06108-Battery adaptation-Battery Serial Number,1111111111 You can either set them manually if the tool allows, or try and use the guided function with made up data (apart from Ah!)...

After a quick google: 1) U110100 seems to be component protection active 2) B201200 seems to be implausible dataset 3) B201A00 seems to be SVM update 4) U111100 seems to be missing message 1) is probably due to it being hacked 2) needs ODIS or VCP to upload the correct dataset 3) can be cleared get generating a XOR'ed code 4) is likely coding related I'd suggest you contact the person you bought it from for support. Without the original coding and adaptions, it's hard to suggest an corrective action

Never come across a UK socket version. EU version seems to be available as a kit, part number: 000 063 826

If you're replacing like for like, you don't need a unlocked/hacked unit. Have a dealer remove component protection, re-enable the SWaP/FeC codes and revert to factory coding/adaptions. If you do want a hacked unit, you should copy the coding and adaptions from your old unit

At a guess, check "Road sign detection fusion mode" in A5 is set to "Road sign fusion"... Otherwise, you'll need to find out how to add an autoscan and adaption maps from OBDeleven

The manufacturer and codes aren't that important. It's just so the battery management system knows it's a new battery... As long as the capacity is right, it should be fine. Assuming the old battery and new are similar, just add one to the serial number

Sounds like someone has mess the lock up previously. It should work regardless of the car battery. I think there was another thread recently where they were able to connect the jump leads to the starter power feed and ground which allowed them to unlock it.

Bi-xenon were never an option on a pre-FL or FL MK2 Octavia. So it seems unlikely

Yeah, just bad spacing on the part. 1Z2941015B looks to be a RHD xenon based on this: https://www.ebay.co.uk/itm/363097468110

Yup, the remote fob can be done with VCDS. It's just the remote unlock/locking for the doors. No code is needed as it'll learn the new fobs when you press the buttons on them I remember now, if you have some light config issues, let me know and we can sort something out to fix them.

Yup, pretty sure that's a highline and it'll be pin compatible. Your only issue will be the lighting configuration. Typically, there isn't a correct byte 18 value for the Octavia (which is why it's 00) so you'd ideally need VCP or ODIS to copy/configure the lighting configuration directly in the EEPROM. After fitting, it'll still need coding and remote fobs matching but that's about it

If you're sure that the WD is correct, try it and see what happens It shouldn't damage anything if it's all just CAN-bus.

There are multiple separate CAN-buses in your car. When adding a module, it needs to be on the correct CAN-bus. The OBD port is the diagnostic CAN-bus so it cannot be used for the radio.

Pretty sure they all get removed in the same fashion, namely four removal keys around the edge as per this guide:

They are on the Skoda website.... As mentioned by 100andthirty go to: http://updateportal.skoda-auto.com/en-GB Enter your VIN Scroll down the webpage Download the UK logos Unzip them onto an SD card (not the maps card!) Scroll down further Under Steps it has a section for Import of radio station logos Insert supported medium (SD, USB.) into the slot of your infotainment system. Press "Radio" > "Settings" > "Station logos" and select requested station. If the station already has the logo assigned, you have to remove it. Select the medium with logo images and select desired logo. Repeat also for other stations. Now you can remove the medium from the slot. No idea, the MIB3 systems seem to be confusing everyone when it comes to updates. It might take a while until Skoda/VAG actually decide how it should be done... Sorry

If your car is 13 years old, the projector reflectors are probably shot. Check the condition of the reflectors and lens, replace as necessary Please don't use drop in xenon conversions, they are not road legal in the UK and cause glare to other drivers. They should also fail the MOT.

If I remember correctly: - the cap on the top squeezes off, might need a light pry with a screwdriver - the purple locking bar will slide in one direction - you can then use terminal removers to push the terminal through Example with the top removed and a Purple locking bar, I think it's in the locked position, should slight right(??) to unlock: Pictures from https://www.mk5golfgti.co.uk/forum/index.php?topic=90500.60 You can see the barbs on the terminals below, this is what the terminal removal tool needs to depress: Hope that helps

If I recall, you drive a 2018 Superb? The cost between a car scanner pro, OBDeleven and even VCDS is very little in comparison the the cars value... Obviously it's your choice, but personally, I'd want to reduce the risk of messing the car up by at least using an interface with known tweaks and guaranteed support from it's developer. As mentioned above, what are you wanting to achieve?

You need to find which channels are fog lights. Take a look through all the channels for something with functions "Nebellicht links" and "Nebellicht rechts" and change those If you're able to get a full list of adaption channels and settings out of obdeleven, I can take a look.