Hi all,

I've had some really strange behaviors that I'd like to have your advice on. It's s bit of a read because I'm not good at cars and it's hard to filter what is relevant. It's a Superb, 3.6l, 4x4 from 2011.  First some history:

 

1. Three years ago, the trunk(!) started opening at engine start. It even opened by itself. Neighbour got in contact and told me I have had a car burglary. Turns out trunk had popped open and since I wasn't using the car for a couple of days, it was sitting open for a weekend. Had it in for repairs. Turns out rain water had leaked in through driver door window, corroding wiring in door. Replacement was around 1300 Euro.

Painful to say the least, but at least things were back to normal.

 

2. Last year, my Columbus RNS541 display just died. Unfortunately battery died at the same time. I changed the AGM battery. I did no "battery parameterization" as I had no clue that you needed to do it. Things seemed to work fine, except the Columbus wanted a security code. As the display was dead, I couldn't really fix it  Putting in a new Columbus was priced to 1500 Euro. Yeah, NO NO NO. I'm not paying that sum for ancient technology, I thought.

 

3. Summer -22. Did some research on retrofit Android units. Bought one that after a long email conversation where they guaranteed it would work in my particular variant. Yeah, NO. I have the amplifier under the seat, and I did the battery trick. But only the left side speakers started working. Even worse if I changed position in the driver seat the sound quality changed. Additionally, the seller tried to screw me and had sent an old model that didn't match the given specs.

Alright I turned it and got a refund, but I DID NOT put in the old Columbus unit.

I drove around without headunit for half a year. Idea was to get another Android unit, but life got in the way.

 

4. Noticed that the driver side capacitative handle intermittently did not work.

 

5. Winter -22. One of the first cold days. (-10). Drove to work without issues. 

When going home:

+ Cluster did not light up. Totally dead.

+ Engine didn't start

+ Lights inside car work.

+ Windows work and other electronics seemv to work.

Disconnected battery.

+ Cluster starts up with lots of errors

+ Engine starts

- ESP error, Adaptive lightning, Driver assist button error. On way home; key not found, steering column lock: workshop!

- IGN off, IGN on did not work, battery disconnect, IGN on works.

- Did E2E wheel turn and errors go away (specifically esp, adaptive, driver assist). Key not found did not reoccur. Steering column lock did not reoccur. Could drive 8-9km w/o issues.

- IGN off. iGN on does not work. Battery disconnect. IGN on work.

 

6. I've done some obd logs, but either they're empty (except for issues due to missing HU) or really full of errors everywhere (after disconnect).

 

I've ordered a odbeleven and hope to be able to take reasonable logs next week.

 

Anyone have any ideas? Is it possible that it comes from missing headunit? Is it due to broken IGN button? (Apparently common failure) but would the cluster be dead then?

Is it a continuation error from the KESSY problem?

 

If anyone knows an Android unit that works with external amplifier (in a good way), i can spend money on that. It just feels strange that the HU would cause this. Can immobilizer+KESSY make cluster dead? Or is this a temperature + bad contact error? Where would this then be located?

 

 

Ok sorry, for long post. I've read a bunch of stuff but i just have to face up to the fact that i don't have enough knowledge.

 

 

I can't spend money on a new car right now, and i really don't want to either. I like my superb.  I can replace the HU myself if I just need to have the name of a unit that works with external amplifier.

I looked at YouTube videos for changing the IGN button/s.c lock but both seem complicated, but that's a limited cost. If it's the wiring I've understood it can be massively expensive.

 

Cheers!

 

I think if you ignored the request for a code and just waited for a couple of minutes the Columbus unit would have, and still would burst into life, to my knowledge all the VAG head units are paired to the vehicles they were fitted to at the factory but wont work without a code (and probably some VAG programming) on another vehicle.

 

I know this through being impatient, looking through all the handbooks etc left by the previous owners, trying every different number written within only to find that the thing left to its own devices would have worked out that it was the original radio and started working.

Let me know model number and SW version of your KESSY module (address 05) - there were some issues that were solved by SW upgrade. I originally had 5K0 959 434 A with SW 0802 and had similar issues. I have solved them by upgrading SW to 0902 which caused model number to be changed to 5K0 959 434 B.

On 08/01/2023 at 20:29, pab567 said:

Let me know model number and SW version of your KESSY module (address 05) - there were some issues that were solved by SW upgrade. I originally had 5K0 959 434 A with SW 0802 and had similar issues. I have solved them by upgrading SW to 0902 which caused model number to be changed to 5K0 959 434 B.

Hi,

Thanks for taking the time to read and answer. I had to wait for the new OBDII device. 

Battery had almost drained again the fault log is not useful, but I managed to get the version of the KESSY.

 System description: VWKESSYPQ35GP
    Software number: 5K0959434A
    Software version: 0802
    Hardware number: 5K0959434A
    Hardware version: 085
    Serial number: 0140690923
    ODX name: EV_KESSY_PQ35GP
    ODX version: A01018
    Long coding: 030C0C

 

Seems it matches with your description.

On 08/01/2023 at 20:17, J.R. said:

I think if you ignored the request for a code and just waited for a couple of minutes the Columbus unit would have, and still would burst into life, to my knowledge all the VAG head units are paired to the vehicles they were fitted to at the factory but wont work without a code (and probably some VAG programming) on another vehicle.

 

 

Hi, thanks for the tip, but I failed to include the information that I drove around with PIN screen on the Columbus for around a month, as the display was not responding. 

There was no change, before or after battery change.

Start by sorting out the battery. Low or dead battery in these cars plays hell with the control modules. Assuming the battery you fitted is not damaged, charge it fully with a suitable battery charger and carry out the adaptation process.

 

When this is done we can start figuring what might actually be broken.

5 minutes ago, chimaera said:

Start by sorting out the battery. Low or dead battery in these cars plays hell with the control modules. 

 

Of course.  It's a new battery, so I think it's okay. The workshop I decided (in the end) to not continue with discharged the battery as an additional "service". Jump started the car and got it home and this weekend I intended to to charge it. 

 

It may have been a new battery but will no longer be giving of its best after being discharged beyond the point where it would start the vehicle, I suggest you have it checked on an electronic load tester which should give an idea of its remaining CCA capacity.

 

My "new" battery ended up testing like a 5 year old one after leaving the sidelights on inadvertently, it has not further deteriorated. If, no that should be when I get electronic problems the battery will be the first suspect.

Edited 14 January, 20233 yr by J.R.

@Grain get someone with Vag Can Pro or ODIS and upgrade your KESSY. If you don't find anyone locally make it with SKODA dealer. I bet all your issues will be solved (assuming Clumbus unit is 100% electrically OK).