Hi all

 

I wonder if anyone can tell me what might have caused this problem yesterday. I made a shortish trip, the car functioned as normal but the Columbus unit was stuck - showing Radio 2 and the current program (Ken Bruce, thanks for asking) and DAB station info as normal - but no sound, none of the buttons was working so I couldn't change channel, or change to media/nav/setup etc. The steering wheel buttons for controlling the Columbus didn't work either. Everything else seemed fine, my phone seemed to be connected OK as usual via bluetooth...mind you I didn't make or receive a call.

 

The temperature was -2 at the time, on my return trip it was a heady +1 and everything was back to normal. However I'm sure the cold can't explain this! Anyone else experienced such a thing?

 

It's a 2014 L&K 170, love the car and this is the first and only problem I have had (except for intermittent odd noises that seem to be caused by the fan). Not too worried as it seems fine again now but in case something is wrong I'd like to get it fixed under warranty.

 

Thanks in advance 

 

 

sounds like its locked up, my Amundsen did something similar a month ago whilst in deepest Brittany couldn't set it up to get home directions etc   -  solved by removing the main radio fuse in the engine compartment fuse box (id it from the manual) for a minute, reinstalled it and no further probs!

I guess it's the IT solution - switch it off and on again, will bear in mind the fuse option!

I agree: The Columbus units do seem to lock up very very occasionally. If it's rare AND can be cured by switching off the ignition for a couple minutes and then rebooting, probably just one of those things. But potentially more of a real problem if it starts to happen repeatedly.

I guess beneath its disguise it's a computer and we all know they're liable to crash or lock up. I'll be monitoring it and if it becomes a frequent thing I'll take it to the dealer for a checkup.

 

Thanks for the advice :-)

I guess it's the IT solution - switch it off and on again, will bear in mind the fuse option!

We used to call it Power Cycling

I don't think just switching off is enough to reboot - the unit will still be live to maintain the services within, maybe removing the key for a couple of mins would work, my pref would be to remove the fuse completely for a min and then replace, cuts the supply completely, a true reboot!

I may have had it happen once with TIBETs I and II but it's occurred at least 3 times with TIBET III in 14k miles. 

 

Normally, pull over and switch off the engine and it all returns to normal. One time I couldn't pull over, it actually sorted itself out eventually.

 

I put it down to being a computer....

My Columbus has done this a couple of times. Turning off the engine didn't fix it so took out the fuse, waited 60 secs for the electronics to discharge & put the fuse back in again. Normal service resumed!

I have had similar issues with our Amundsen+. When I mentioned this to the dealer at a service 2 weeks ago they checked and found there was a software update available for it which they have applied.

 

Early days for sure, but no further issues as yet.

 

May be worth checking if there is a Columbus update available?