I have been given a Navman f20 and when I turn it on it says "Unable to detect internal memory, return to dealer".
Is there a fix to this that anyone knows about?
Can it be resoftwared for example?
Any help needed
Turned mine on today after 6 months of trouble free use, had the same message ending in contact Navman Tech Support.
I've sent an e-mail and awaiting reply, when I get it i'll let you know!!
Download the service pac from the Navman site, this will re load the operating system. I had this error when my update was broken by the the PC re booting
I also get the error message "UNable to detect internal memory"
I've tried up loading the service pack but I get the error message "unable to connect to NAVMAN etc etc........" Yet the NAVMAN says its connected to the USB port etc. and is switched on.
Hi all,
I now have the answer from Navman.
This is a fault with the internal memory chip failing. It can not be fixed and requires the unit to be sent to Navman and the chip replaced.
Return your GPS to the place of purchase and they will complete the return for you if you've had it less than a year. You will need a repair ref number from Navman before sending it back.
I guess this would cost you if the items out of waranty.
navman F20 = rubish if after 6-9 months memory fails!!! bad
Just a quick add - if navman the company has had a few of these models sent back - i suspect they bought a bad batch of memory chips. Why do companies not post somewhere that it is a known fault and all models with serial number XXYYZZ are faulty they will replace them and aid a good company reputation?
Intresting I had exactly the same error. I traced mine back to overheating. Everytime I leave it in the glove box on a hot day it refuses to boot up. If I position it over the air conditioning for a minute or so it switches on! Give it a try, it might get you out of a spot....
Download the service pac from the Navman site, this will re load the operating system. I had this error when my update was broken by the the PC re booting
This problem can also be caused by some kind of procedure mistake with doing the service pack upgrade. It happenned to me some time ago.
I did the service pack upgrade again, followed the instructions to the letter and all was sorted.
If I remember correctly this can also happen if the desktop software finds an older version of the service pack on the unit when it tries to connect to it.
Right mine started to do this at about 15 months old, it had not been used for a few months.
So took it apart, to find the microcard inside as I assumed it may be the problem.
My first thought was why is it moving about so "moved" it about a bit and switched unit on, straight away it worked again, so assume that vibration could cause the card to disconnect, in my case to cure this I dripped some candle wax onto the chip and main pcb, still working at moment. Bluetack or similar could also work.