odd satnav problems

Sign in to follow this  
Followers 0

6 posts in this topic

hi all

i have a 2009 elegance and the satnav died on me, dealer and skoda paid for repairing the system (new motherboard).

on completion all seemed well til the other day when using the satnav, the white matrix between the dials has no nav option anymore?

i suspect i may need either a newer can gateway or some coding.

any help appreciated.

info from satnav

3t0035680b

hw version H70

sw version 4120

map version 7920

thanks

roj

Share this post


Link to post
Share on other sites

Did you press and hold the button on the end of the wiper stalk when the sat nav was operating as that will make the maxidot go back to MFD screen.

Ian

Share this post


Link to post
Share on other sites

Columbus issues in 3yr+ old cars seem to be popping up frequentky at the mo. Mine died the other week, kept trying to re-boot itself, see other threads on columbus for more info, I was lucky as skoda and lease firm paid the bill between them so i got a fresh unit. Had to haggle with dealer for latest firmware and maps though, even though it was costing £2000 + vat they wanted another £175 for v7 but after a heated exchange they gave in and loaded the latest disc they had, v7 so i,m happy.

Interstingly though, I lost maxi dot nav and radio functions initially, however after restarting the car next morning, all menus were back, think it just needed to sleep for a while. I think if the car is off for 2 hours or more, the computers re-boot and recognise each other again, someone else suggested disconnect the battery may also work as both systems need to re-boot simultaneous to recognise each other

Share this post


Link to post
Share on other sites

Sorry for jumping in rojtatton but i have the very same thing , i have never had Radio or Nav in the maxidot display with mine .i have only had the car since September so i am unsure if it has ever been changed .

countryboy i dont have a button at the of my wiper stalk , should i ?

My car is a 2009 Elegance

Share this post


Link to post
Share on other sites

It'll be a coding issue, the Superb 2 uses BAP protocol to the cluster and this has to be enabled in the Columbus using VCDS or the dealer diagnostic tool.

The same thing may also happen if the firmware is upgraded with the wrong disc (one that's had the PQ and SK tables swapped) rather than a standard unmodified one.

Share this post


Link to post
Share on other sites

Thanks mannyo :)

Would running a standard Firmware sort this or does it need to be coded via VCDS ?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.