BMW Nav5 will not connect to Mapsource

Status
Not open for further replies.
Left it connected for several hours, won't connect to the dealers Mac or PC either.

I'm aware, when it comes to USB cables/devices that if you have any USB 1 devices connected then the computer won't see a USB 2 device, or will keep 'ejecting' it!!

The advantage of buying BMW with two year guarantee ... unit being replace :thumby:

:beerjug:

Sure I read somewhere that it's a 3 year warranty on Nav V, or is it just the USA?
 
The Nav V is a 3.0 usb device so ideally uses a 10 wire usb lead. A 2.0 usb cable has only 4 wires so will be hit & miss at times if used.

They use a different cable from the older Garmins and the latest 300 series. The clue though is in the "U" part of USB it stands for universal. I have downloaded routes to hundreds of Nav V using generic USB cables, I have done the same to large number of 300 series devices and countless 660s and older units . Sometimes device will not connect but I have never solved this by using a Garmin branded one. In each case the problem has only been solved by returning the unit to Garmin. Thankfully this is a rare occurrence. No doubt using a faulty lead would cause problems but as long as the lead is fully functioning my experience is it makes absolutely no difference what brand of lead you use

John

And this still leaves the question why these expensive units are so slow both in connection and calculating routes.
 
It's the connectors that are universal not the lead. If you don't use a 3.0 lead you won't get the advantage of a faster 3.0 device when using it with a computer.

You mentioned slow in connection, not Garmins fault as they supply the required cable with the device from new.

Calculating routes is not related to USB data speeds
 
It's the connectors that are universal not the lead. If you don't use a 3.0 lead you won't get the advantage of a faster 3.0 device when using it with a computer.

You mentioned slow in connection, not Garmins fault as they supply the required cable with the device from new.

Calculating routes is not related to USB data speeds

As I pointed out the connectors are different, you can't use the USB 2 lead as supplied with other Garmins. If you read what I have written on this subject you will see that my experience (lots of it) is that there is absolutely no difference when using a Garmin supplied lead compared to a generic one. I have tried Nav Vs using the owner's Garmin lead, it works exactly the same as my own non Garmin lead. The Nav V is slow to connect to a computer whatever lead is used, if that is not Garmin's fault then maybe you can explain where the fault lies. Why given the supposed advantages of a 3.0 lead do these devices take longer to be recognised than a 660 connected via USB 2?

I am fully aware that route calculation speeds have nothing to do with the USB connection. The question is why should this "top of the range" device take so much longer than say a 390? On many occasions I have downloaded a route to a Nav V, turned it back on and said yes to the message saying that a new route has been found. I then download the same route to a 390, turn that back on and say yes to the same message. What happens is the 390 finishes the job before the Nav V despite that device have several minutes head start.



John
 
... unit being replace :thumby:

:beerjug:

that-s-all-folks.jpg


Thread closed.

Original question long since forgotten (self-answered within a day) and Micky is being mended.
 
Status
Not open for further replies.


Back
Top Bottom