Might be worth taking a snapshot of the Long coding settings in VCDS if you have it. Would save any of us having to go through the trial and error method as it appears to be different to the older maxi dot displays.

Martin

Hi ,

I have a factory fitted Columbus to my new Octavia (new shape 59 plate).

I am tempted to upgrade, do I stand a good chance of success ? (I don't have the blue tooth option so that shouldn't be a problem).

Can't get into the setup menu to check existing firmware/hardware, guess it needs enabling via VAG-COM first..

Yes.

Well done it, couldn't bear to watch so went away until it finished, still **** myself twice over.

All seems to be okay including the MFSW.

One small issue I can't load NAV destination from SD card, the option is greyed out. Reads MP3 okay though..

Once an SD card is insterted with the VCard (in the correct folder) it should become an active button...

Have you stopped sweating yet?

Have a read of this thread:

Destination Entry From Memory Card

Yep all sorted now thanks... happy days:thumbup:

magic62 - would you be so kind as to give us a quick summary in english of what's happening on the german rns510 forum with the gateway errors and the guy replacing his hard disk?

I could, but dont want to translate the entire forum . Could you link the posts to the items you want to know more about?

@Brimma

The RNS has three different skins, one of them is called premium. Thats the skin I use.

And I must like christmas a lot (no facelift here).

Am i missing something here??

I have tried on numerous occasions to change the skin and they all stay exactly the same (yes i am rebooting the unit after changing)

I currently have it set on premium and it looks no different to sportsline or highline :confused:

Not particularly fussed just thought that you could only change it to match the car (i.e VW Premium/Seat Sportsline/Skoda Highline)

Carl:thumbup:

Hi Carl, I can choose one of the three skins. (RNS510 christmastree here ). Even in the roomster I can now access the RNS (with VCDS 908).

Had the highline first, didnt like the grey too much and tried the sportsline which is too red after that went for the premium skin and this is the skin I like most.

Just had to recode and restart, after that the skin changed.

It wont work on the Columbus though.

It wont work on the Columbus though.

Ahh thats probably why as mine is a Columbus (has it written above the CD Slot) which is prob why i won't change

Cheers Magic:thumbup:

Carl:thumbup:

Yes the skins thing is a VW peculiarity depending on the model.

Oh well, Bit the bullet and tried the upgrade and it worked. The only downside is now the audio and nav options have disappeared off the maxi dot. I take it this would be because the unit is now advertising itself as a 1TO rather than a 1ZO. Anyone near Slough with VCDS that could do me the honours with a re-code?

Did you change over the filenames?

Oh well, Bit the bullet and tried the upgrade and it worked. The only downside is now the audio and nav options have disappeared off the maxi dot. I take it this would be because the unit is now advertising itself as a 1TO rather than a 1ZO. Anyone near Slough with VCDS that could do me the honours with a re-code?

Before you did the flash, you should have swapped the PQTABLE and SKTABLE around and you will not get this problem. The issue is that the SKTABLE is not compatible with the maxidot, but the PQTABLE file is.

quote from my-gti website

Note! Skoda owners (thanks to Ted)

Extract files PQTABLE and SKTABLE from image (use magiciso or ultraiso). Files can be found from path: \VUCI\B101\RNSMIDEC\PROG

Switch the filenames by just renaming SKTABLE to PQTABLE and vice versa

Overwrite the renamed files back to image and save the image. Burn this image to DVD or CD.

Load or reload the Firmware to your RNS-510 using the steps below.

Voilá… buttons are back!

Hmm i dont think the SKTABLE.FLI file is the problem If they have disappeared off maxidot altogether. :rubchin:

I originally didn't modify the files and the Audio & Nav Option stayed on it was just once you selected one of them you couldn't get out of it by pressing the button at the end of the stalk you had to turn the unit off then back on again. I've not heard of them disappearing altogether.

Try rebooting the Maxidot by holding <> & i and see if they reappear. If not i think it's a coding issue rather than a Firmware FLI file issue. But there is no harm in trying.

Carl:thumbup:

Err update on this. Just took a drive down to the cashpoint and ran up nav for a laugh. About 5 seconds after I drove off, the compass appeared in the maxi dot, and the Audio and Nav options appeared and are working fine. The nav screen now shows turn directions and everything. It also doesn't lock the maxi dot. What a bonus.

I've also got the Climatronic display as well.

I'm driving a VRS LE, so I haven't got MFSW (yet, but I live in hope), so I didn't change the filenames over.

The only thing which doesn't work is I don't get the bluetooth phone options on the Columbus (dial menus etc). I get them on the maxi dot, but the auto scroll down the contacts list doesn't work on this version by holding the button on the stalk (never has) and that's a pain.

I take it this is still something for coding. BTW has anyone got BT audio running on an OEM BT Kit?

Once I've got this going, I'll look at getting the mic re-wired and see if I can get the full voice control running. Happy days (I hope)

Martin

I take it this is still something for coding. BTW has anyone got BT audio running on an OEM BT Kit?

Once I've got this going, I'll look at getting the mic re-wired and see if I can get the full voice control running. Happy days (I hope)

Martin

Connected my BT mic to Columbus yesterday, all works fine, voice control is brill.

I re-routed the mic cable to the rear of HU as there is loads of spare cable. Get 4 repair wires (part no. 000 979 009) as posted by Stu, cut the mic cable then solder on the repair wires.Stick them in the HU job done.

One code change on VCDS is needed, Controller 37 long coding Byte 7 needs to be unchecked to enable voice control

See info at http://www.my-gti.com/1234/volkswagen-rns-510-microphone-connection-for-voice-control

Edited 9 October, 200916 yr by sibart
Forgot coding info

Connected my BT mic to Columbus yesterday, all works fine, voice control is brill.

I re-routed the mic cable to the rear of HU as there is loads of spare cable. Get 4 repair wires (part no. 000 979 009) as posted by Stu, cut the mic cable then solder on the repair wires.Stick them in the HU job done.

One code change on VCDS is needed, Controller 37 long coding Byte 7 needs to be unchecked to enable voice control

See info at Volkswagen RNS 510 Microphone Connection for voice control | my-gti.com

Thanks Silbart, just need to find some kindly soul with VCDS around here, who could help. I will supply the beer vouchers.

Martin

Connected my BT mic to Columbus yesterday, all works fine, voice control is brill.

I re-routed the mic cable to the rear of HU as there is loads of spare cable. Get 4 repair wires (part no. 000 979 009) as posted by Stu, cut the mic cable then solder on the repair wires.Stick them in the HU job done.

One code change on VCDS is needed, Controller 37 long coding Byte 7 needs to be unchecked to enable voice control

See info at Volkswagen RNS 510 Microphone Connection for voice control | my-gti.com

Bloody hell your still alive :eek: :P

Not seen you on here for ages. You got those cams in yet

Carl:thumbup:

Bloody hell your still alive :eek: :P

Not seen you on here for ages. You got those cams in yet

Carl:thumbup:

Still alive and kicking Carl..Been rather busy house renovating and being away with work.

Waiting for the sale of my old house to release funds for the cams and LSD.

Hope your saving for the K04 mate

Still alive and kicking Carl..Been rather busy house renovating and being away with work.

Waiting for the sale of my old house to release funds for the cams and LSD.

Hope your saving for the K04 mate

Different Plans now mate.

I'm Stage 2+ now so happy with that for the moment.

But when the next plan comes to fruition you will like it

Anyway stop dragging this thread Off Topic :P

Carl:thumbup:

Tried to update the firmware on a Columbus unit, and it recognised the CD but failed to update as it said the clamp needed to be removed or set to hour mode

Any ideas?

Also for the RNS 510's there is mention of a hidden menu, is there the same on a Columbus for the Skoda Superb?

Hi erniem

You must do the update with the key out of the ignition !

Yes the Columbus in the Skoda Superb has a hidden menu that needs to be turned on using vag-com

I tried to update the firmware on a Columbus unit in a Skoda superb and it recognised the CD as an update, but says I need to remove the clamp or set it to hour mode to update the firmware

Any ideas?

Clamp state error - VWnavi.com

The firmware upgrade will only work if the key is not in the ignition

I'm picking up a brand new car next week and I'm wondering if I get the new firmware in the Columbus. Should I complain if it's a older firmware then 2660......?

When is the official relase date for the new firmware. :confused:

I updated and lost the function of the stalk.

What do I need to change on the image other than the table files then it will allow me to update again.

Do I just need to +1 to the end of the image file name for it to recognise it as an update like on maps?

Thanks

Ste