Ok, have taken teh plunge and ordered a second hand Columbus unit for my Octavia arriving in a few weeks time, so I know that it will pop straight in and thats a straight forward job for me, plus the new facia for it, but it will obviously need coding for the display in the maxidot to work.

So what is the procedure in VCDS please?

A local member on here has offered to do the coding, but if anyone has a step by step guide for it that would be good.

Many thanks in advance

James

You just basically have to go into the navigation section (iirc) and just tick a few boxes to say that it has navigation. Once you have ticked this, it will show on the maxidot.....

Basically just scroll through all the bytes until you see a navigation check box. You may need to enable BAP also.

I did this yesterday.

>Click select control module

>Enter 19-CAN-BUS and click on installations, then tick 37-Navigation.

>Enter 37-Navigation and go into the long coding helper to set it up for the car, self explanatory apart from display type, I chose the bottom one from the list of 3, I think it was 'Highline'. Ensure 'Use BAP' is ticked.

>Disconnect VCDS

Turn off ignition, reset the columbus (not sure if this is necessary, but it was on mine) '<''>' + 'eject', then viola.

Edited 8 June, 201214 yr by phsroberts

I did this yesterday.

>Click select control module

>Enter 19-CAN-BUS and click on installations, then tick 37-Navigation.

>Enter 37-Navigation and go into the long coding helper to set it up for the car, self explanatory apart from display type, I chose the bottom one from the list of 3, I think it was 'Highline'. Ensure 'Use BAP' is ticked.

>Disconnect VCDS

Turn off ignition, reset the columbus (not sure if this is necessary, but it was on mine) '<''>' + 'eject', then viola.

Yep, thats it! been over a year since i did mine! I didn't have to reset my Columbus though.

Perfect thanks chaps, exactly what I needed!

Just got to wait for the Columbus and teh car to turn up now!

Getting excited now as it was built this week I believe so am hoping for a July 1st pick up!

Hi All, I was helping NinjaVRS code his Columbus to his PreFL VRS using my VCDS today, after spending ages looking for the BAP setting, its at the bottom of the Long Coding screen so you ovelook it a bit but it now displays on his Maxidot.

 

But once you set th eMaxidot to Navigation or Radio you cant get it back to MFD by pressing the wiper stalk t all. You have to switch the radio off then it goes back to MFD.

 

Can anyone help fix this? My Nexus lets me change between the displays so I assume the Columbus should?

In a pre FL you shouldn't use the BAP setting as it is a different (DDP) communication protocol.  I suspect this is the cause of the issue - it should still show in maxidot as long as it is ticked in the gateway.

In a pre FL you shouldn't use the BAP setting as it is a different (DDP) communication protocol.  I suspect this is the cause of the issue - it should still show in maxidot as long as it is ticked in the gateway.

AdamAl, we have switched BAP off! :-(

Can't figure it out. I tried the display type from standard to highline to see if it made any difference but nope.

 

But once you set th eMaxidot to Navigation or Radio you cant get it back to MFD by pressing the wiper stalk t all. You have to switch the radio off then it goes back to MFD.

 

Can anyone help fix this? My Nexus lets me change between the displays so I assume the Columbus should?

 

Thats a firmware issue in the columbus, I would suggest upgrading it to a later version or find one which has had the PQ and SK tables switched over which fixes the fault.

Hadn't realised you had switched it off sorry.

 

Had forgotten about the firmware issue, there is actually a firmware update which addresses this without having to completely reinstall the firmware.  See: the fixes section towards the bottom of http://www.my-gti.com/3374/volkswagen-rns-510-firmware-upgrade-and-information (under  Skoda Columbus (RNS 510) Fix).

I had that same problem. Installed the fix and voila! Works perfectly now.

 

I have since upgraded to 5270 firmware and re-applied the fix (think I found one for 5xxx firmware somewhere).

 

Phil