RNS 510/Columbus Map Scale On Startup

**Guest001** · 05-08-2013, 07:02 PM

Originally Posted by lunchboxGTI

My first RNS was v5 maps and 39xx and never changed scale. It had a issue with the 26 pin plug so Was returned. my next unit was v5 4120 and it changes scale all the time from 200m to 5km I then got v6 maps and still the same. It has to be a firmware thing. My scale never goes down always up from what I left it at. I have noticed it only changes when it's been a while. If the unit goes through its start up it will change.

Try the reset then

**kamold** · 05-08-2013, 07:28 PM

Mine has always stuck to the previous setting as far as I can remember, through every possible firmware version 2760->5238...

I find the autozoom to be a bit too far out generally (eg jumping to 1km scale when on a 60km/h arterial road), so prefer to control the scale myself. I'll have to look into the adaptation channels tomorrow and see if there is anything that might look remotely like it would control this behaviour...

**gjws** · 16-08-2013, 11:45 PM

Hi all,

Firstly to all the people that have sent me PM's over the last few months, sorry! I've been working OS and not paying attention to the forums as the GTI was 15000kms away

Anyway, the reason for my post is I'm having the same zoom problem and it's really starting to bug me. I rarely use the navigation function as to be honest I think it's crap, my iPhone and google maps puts it to shame. But I often use it when I want to see if I can duck around red lights or a traffic holdup, it's great to see where the roads around you lead.

When I do this I'm typically looking for a street quickly, and it's terribly frustrating when it pops up zoomed out to 75km! I've tried the reset with no joy, and I'm running the latest maps and firmware having upgraded a few days ago when I got home.

Has anyone had any joy finding a fix as yet, nothing in the VAG that looks promising?

**BottomScratcher** · 17-08-2013, 06:47 AM

Originally Posted by gjws

Has anyone had any joy finding a fix as yet, nothing in the VAG that looks promising?

Not that I'm aware of.

Mine only started doing it after a FW upgrade to 4120, but as can be seen from the posts on this thread the fact the satnav suddenly changed behaviour in conjunction with FW upgrade doesn't prove conclusively that the change in behaviour is due to the FW upgrade. That said I'm not a great believer in pure coincidence, but there's nothing that sees me able to say with any certainty that the FW upgrade is the cause of scale changing as a couple of people are running the same FW and map version as I am without scale changes on start up. Something to do with that combination of FW/maps in relation to the head unit model it's applied to perhaps? In the words of Qausimodo, just a hunch.

EDIT: Meant to say in the last couple of posts that I've tried soft resets as suggested, but they didn't resolve the issue.

**kamold** · 17-08-2013, 07:48 AM

I promised I'd check through the adaptation channels for anything related to this....will do so later today and report back.

**greg32** · 17-08-2013, 08:47 AM

I haven't had this problem. Try turning off auto zoom and setting a good size image with the map settings. This should be able to be done on the normal controls without vcds.

**BottomScratcher** · 17-08-2013, 09:06 AM

Originally Posted by greg32

I haven't had this problem. Try turning off auto zoom and setting a good size image with the map settings. This should be able to be done on the normal controls without vcds.

I never have Autozoom on, so I don't think it's related to that feature. Whether set by the screen, or by the knob the scale changes upwards at the next start.

**thezoneR32** · 17-08-2013, 12:28 PM

+ one for this annoying glitch and its def since FW upgrade to 4120. Mine is an older c vers so I dont have the abilty to turn the dial and and change zoom it has to be done manually on the touch screen and its freakin annoying!

**kamold** · 17-08-2013, 01:07 PM

Ok, just went through the adaptation channels, coding and all setup/test mode options, there doesn't appear to be anything that would control this.

Anyone want to be a guinea pig and try an upgrade to 5238 to see if it corrects it? I am on 5238 now but I have not ever seen these reported symptoms on any level of firmware from 26xx to 5238, with everything in between on my unit....

**BottomScratcher** · 17-08-2013, 01:28 PM

Originally Posted by kamold

Ok, just went through the adaptation channels, coding and all setup/test mode options, there doesn't appear to be anything that would control this.

Anyone want to be a guinea pig and try an upgrade to 5238 to see if it corrects it? I am on 5238 now but I have not ever seen these reported symptoms on any level of firmware from 26xx to 5238, with everything in between on my unit....

G'day. I was thinking of this, but didn't want to pester you again so soon after you last helped me out. I'm game. And thanks for the offer.