Related

Basecamp 4.4.6 not working with Nuvi 65

Former Member
Former Member
After updating Basecamp 4.3.5 to ver 4.4.6 basecamp and my Nuvi 65 are no longer on speaking terms.

When conntcting a cold Nuvi, it is recognised by windows and appears in the device manager ok.

Basecamp starts ok without the Nuvi connected. When the Nuvi is connected to any USB port, Basecamp goes unresponsive and hangs for as long my patiente have lasted so far.
If Nuvi is connected first, Basecamp usually does not start but hangs unresponsive as soon as the program window opens.
When either of this has happened, the Nuvi program has likely crashed, the PC doesnt recognise it any longer and it disappears in the device manager.

If by a small miracle Nuvi remains recognised when Basecamp starts (happens sometimes, but seldom) I can receive data from the Nuvi ok. But if I try to send anything to the Nuvi, Basecamp and Nuvi hangs everytime.

When the Nuvi has hanged it displays the dim garmin splash screen indicating a connection. But is it dead. Disconnecting the USB cable changes nothing. it can stand for hours. Then I need to press the on-off button for a long time, the screen goes black. Then it restarts automatically to normal function without any on-off press. After that it can be swithed off normally, and will be recognised by the PC next time it is connected to an USB-port.

Using Garmin Express works OK as before, always recognised and can update or reinstall maps and software OK.

Trying Basecamp 4.4.6 on my sons Nuvi 52 works OK !!!

This is the same on all my three computers, Toshiba Satellite 750 win 7, Acer Aspire E1-572 win 8.1 and Acar Aspire one netbook with win 7 starter. All service packs installed as available.
Unfortunatly I updated all my computers before I recognised this problem. Uninstalling 4.4.6 and reinstalling 4.3.5 doesn't work either, as a reinstalled 4.3.5 will not start but instead gives an error and rudly tells me to update to 4.4.6 with out any choice.

Bo
  • 0
    No it's not so if that what he intends the nuvi 50 won't be able to do it. Should work with his other 2 GPS though.
  • Former Member
    0 Former Member
    I understand some of the limitations of the Nuvi 65. As last year, the trip is broken down by state, and further by multiple route segments within the state. I have also minimized shaping points. Usually, I can get 2 states worth of files loaded and functioning into trip planner on the Nuvi 65. The .gpx files are .75M - 1.2M.

    I have been able to load .gpx files directly into the Nuvi 65 from my computer using windoz Explorer. This seems to work.
  • Former Member
    0 Former Member
    Further update on loading .gpx files directly to Nuvi 65 from computer. I have successfully loaded complete 6000 mile route for RT66 trip to Nuvi. All route segments have been correctly extracted from the gpx files, including 187 custom way points. Trip is back on!

    Also confirmed that I can transfer the routes to the older 2555LMT through Base Camp with no issues.
  • Former Member
    0 Former Member
    Basecamp 4.4.7 is out. Unfortunatly it doesn't rectify this problem. It is obvious that the Basecamp 4.4.6 and 4.4.7 handling of the MTP-protocol on the nuvi 65 (and other models) leaves a lot to be desired.
    Setting the Nuvi to mass storage mode (as outlined in another post) solves the problem. I have read somewhere that it can be dangerous to do so, as a mistake in handling the (system-?) files in the unit may brick it. Even with the outmost care, I wonder if it would be susceptible to hacking while connected to the PC if one have a sloppy secutity on the PC.
    I always keep a clean PC so I am not overly worried, but the risk may have to be considered.
  • 0
    Unlikely to cause any issues, I always run my devices in mass storage mode. You're also unlikely to cause any real problem as the important .system folder would still be hidden if Windows is using its default settings.

    Only real risk is formatting your nuvi.

    Incidentally this may not be a BC issue as it only seems to be the 2 digit nuvis affected.
  • Former Member
    0 Former Member
    I agree.
    But I always run the file manager in show "hidden and system files# mode, so they are not hidden, on the other hand I am extremely careful. But windows nag if one is about to do something stupid.

    The Nuvi 65 worked fine with Basecamp 4.3.5. But it may be that the Basecamp 4.3.5 handling of the MTP-protocol was a little sloppy so, the Nuvi 65 got away with it even if there is a bug in the firmware 4.30. If BC 4.4.6 tightened up the protocol, a bug in the firmware may be the culprit. No-one really can know unless the programmers sort it out.
    So mass storage mode it is, until the MTP problem is solved, whether it is the Basecamp or the Nuvi firmware.
  • Former Member
    0 Former Member
    If you want to be safe, set the MTP back to the MTP Auto Detect after transferring data to the nuvi device. Only takes a few seconds. Hey at least we got a work around...I'm happy. FT :o
  • Former Member
    0 Former Member
    I had the opportunity to examine my son's Nuvi 52 one more time. Refer to my first post. The reason the Nuvi 52 worked with Basecamp 4.4.6 is obviously that it was by default set up as mass memory. So it should be OK to run the Nuvi 65 in the same mode.
  • Former Member
    0 Former Member
    Same problem here with the Nuvi 67.
    :(
  • 0
    Do you have the 65 set for Mass Storage mode, or are you using it in it's default MTP mode? I read on another thread on here complaining about "2 digit Nuvi's" and this issue. Setting the device for Mass Storage mode cured the problem. I have the 65 myself, but switched it to Mass Storage mode on day one when I had difficulty using POILoader.

    Touch Volume
    Touch and hold the upper right corner of the screen
    Touch MTP Settings (you may need to scroll down)
    Touch Configuration and Settings on some devices before getting the option for MTP Settings
    Touch Mass Storage
    Touch Save
    The device will now go into mass storage mode when connected.