Hi, guys,

Even on its brightest setting, my Columbus screen is rather dim, such that I can use it on its daytime setting even in the dead of night.

I would guess that it's been like this for about a few days, but can think of nothing that may have triggered it. I did upgrade to V9 maps at the weekend (I'm on 4024 firmware) but I THINK this dimness problem pre-dates that.

All of its functions work fine and its brightness is not connected to the instruments rheostat.

Any ideas?

Edited 22 October, 201213 yr by Ned Brickley

Go back to a known rev of firmware that was ok and see if that fixes it.

this is what I found today looking for something else: http://www.my-gti.com/3097

Yeah, that's interesting; thanks. I'm not sure it's the answer, though, as I updated the firmware about 2 months ago; everything was fine until very recently. I guess I can live with it...

Josi's answer in the linked thread is probably correct (he know's a thing or two...)

In fact this is not a firmware problem, a dim screen is caused by a incorrect LED screen coding in the RNS-510. It can be permanently fixed only with specialized software.

I wonder if it has anything to do with going from 2xxx firmware straight to 4xxxx and missing out the 3xxx that is allegedly needed to create the three partitions (I know it's not as two people I know have done it).

Just a thought...

I'm just thinking off the top of my head here: wasn't one of the more recent firmware updates (maybe 308x and 4020) coming with a promise of automatic illumination control? So I'm just wondering if the seeming dimness is just a new value setting. Have you tried gaming the display to increase or decrease the brightness (at night, perhaps try shining a torch at the light sensor and see if the display brightens). It sounds like you think the display is at the same brightness value in daylight or night-time, but it might just be compensating to the ambient light to display a similar brightness at all times.

We don't get much in the way of sunny days in Ireland at this time of year, but you could try shining a torch on the sensor during daylight and see what happens as well. I must admit, I've thought the display was a bit dim of late as well, but at the same time I've always been able to see the display clearly in whatever light. That's the only thing that's making me think one of the firmware updates might just have changed the "optimum" brightness level.

Of course, I could just be talking a load of rubbish!

Of course, I could just be talking a load of rubbish!

I don't think you are talking rubbish! It's certainly a possibility.

For those that don't know, the light sensor is in the top right hand corder (to the right of the eject button) and is a small circle in the front plate of the Columbus. I don't know when this hardware feature was introduced on the Columbus though - my 2010 LED version does have it.

Initially it confused me as the screen dims as it gets darker! But then logic took over and it made perfect sense. Whilst driving in the dark, you want the screen to be dimmer so as not to dazzle...

The 3xxx firmware didn't have 'automatic illumination control' enabled, but 4020 certainly did.

Very interesting ideas, Declan and Karl - I'll check this out ASAP as I didn't know about the automatic illumination. Thanks.

Only started happening on.my 2008 hardware when I upgraded from 381x to 402x, so it looks like there's a pattern here.

Only started happening on.my 2008 hardware when I upgraded from 381x to 402x, so it looks like there's a pattern here.

If you've gone from 381x to 4020 then that discounts my 'skipping 3xxx' theory.

My 402x firmware has enabled dimming on my 3T0...A hardware. It was not available prior to 4xxx firmware.

Wonder if there is any connection to the CAN Gateway installed as I have one of the later ones?

Bingo, boys! It was the automatic illumination, proved by the medium of a bright torch. You learn something every day. Cheers.