Empty "Receive From Device"

New Mountain Lion Mac and fresh install of BaseCamp. Now BaseCamp does not read anything from the Nuvi 1490. Lots of waypoints and track logs. But nothing from BaseCamp.

Created a waypoint/favorite and uploaded it. Then was successful at downloading the same no matter it was just one of many on the GPS, it was the only thing that downloaded.

Drove 800 miles with the GPS and now even that one waypoint won't download.

So what is messed up, the GPS or the installation of BaseCamp 3.3.2?
  • I am running Mountain Lion and BC 4.0.1 with a Nuvi 1490 and not having a problem. My guess is your problem is the GPS. Have your tried resetting the GPS?
  • BaseCamp 3.3.2 downloads to/from my GPS on my other Macs. Why should I reset the GPS?
  • Installed 4.0.1.0, same result.

    Connected my 765T, same result.

    No data received from GPS but I can send waypoints and routes to. Read them back, but only them, and only briefly before they disappear from BaseCamp but are on GPS.

    MacPro currently running Lion and latest BC from App Store reads both GPSs just fine.

    Map Updaters have no problem with either GPS on any machine other than the updaters don't seem willing to erase the old maps. "You have only 70MB available for map storage" is typical until I manually remove the previous 1.5GB map file.
  • Bump.

    MacOS 10.8.4, BC 4.1.2, Nuvi 1490 and 765, same problem. Works with my 64-bit MacPro, but not my ~2010 MacBook Pro 15".

    Garmin Express works.

    Created a new user account and the same behavior was observed. After a "receive from device" there is nothing in the "recently read from ..." subfolder. But sometimes I can create waypoints or a route and drag it to the device and successfully install. Just can't ever read those back.

    How might I nuke BaseCamp and all preferences so as to start again? This machine used to work with BC before a clean disk re-install.
  • Please check the console and see if there is an issue with the transfer that is not making it to the UI. If you run "console" and then filter for BaseCamp it might say there was an issue.
  • Please check the console and see if there is an issue with the transfer that is not making it to the UI. If you run "console" and then filter for BaseCamp it might say there was an issue.


    Console says nothing about BaseCamp. This is what I got from time my 765 was connected and recognized, Garmin Express updating Jill's voice (thats not right, updated her a couple of days ago), launch of BootCamp and attempt to read waypoints, track logs and routes from 765:

    6/24/13 7:20:51.000 PM kernel[0]: USBMSC Identifier (non-unique): 0000de8bbfd0 0x91e 0x2366 0x509
    6/24/13 7:20:53.741 PM fseventsd[46]: check_vol_last_mod_time:XXX failed to get mount time (25; &mount_time == 0x109631518)
    6/24/13 7:20:53.741 PM fseventsd[46]: log dir: /Volumes/GARMIN/.fseventsd getting new uuid: EFF63CE8-3987-4968-B255-D0A2A0B2842F
    6/24/13 7:20:55.425 PM Garmin Express[4730]: An instance 0x10222b8b0 of class GarminDevice was deallocated while key value observers were still registered with it. Observation info was leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:
    <NSKeyValueObservationInfo 0x100628770> (
    <NSKeyValueObservance 0x100262a70: Observer: 0x10025dbc0, Key path: isAttached, Options: <New: NO, Old: NO, Prior: NO> Context: 0x0, Property: 0x10025dc30>
    )
    6/24/13 7:22:36.731 PM WindowServer[3433]: Received display connect changed for display 0x4272dc0
    6/24/13 7:22:36.770 PM WindowServer[3433]: Received display connect changed for display 0x3f003d
    6/24/13 7:22:36.771 PM WindowServer[3433]: Received display connect changed for display 0x3f003e
    6/24/13 7:22:36.773 PM WindowServer[3433]: CGXMuxAcknowledge: Posting glitchless acknowledge
    6/24/13 7:22:36.790 PM WindowServer[3433]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x04272dc0 device: 0x10034fb90 isBackBuffered: 1 numComp: 3 numDisp: 3
    6/24/13 7:22:36.849 PM WindowServer[3433]: Received display connect changed for display 0x4272dc0
    6/24/13 7:24:04.578 PM lsboxd[3813]: @AE relay 4755524c:4755524c
  • 6/24/13 7:20:55.425 PM Garmin Express[4730]: An instance 0x10222b8b0 of class GarminDevice was deallocated while key value observers were still registered with it. Observation info was leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:
    <NSKeyValueObservationInfo 0x100628770> (
    <NSKeyValueObservance 0x100262a70: Observer: 0x10025dbc0, Key path: isAttached, Options: <New: NO, Old: NO, Prior: NO> Context: 0x0, Property: 0x10025dc30>
    )


    Hmmm. Try quitting Garmin Express, then restarting BaseCamp and then the transfer. I've never seen any issue with that, but it's worth a try.
  • Hmmm. Try quitting Garmin Express, then restarting BaseCamp and then the transfer. I've never seen any issue with that, but it's worth a try.


    No change. No "leaking" message in Console.app but also no data from my 765.

    I deleted BaseCamp.app from Applications and used 'find ~/Library -name "*[Gg]armin*"' then manually deleted everything I found that wasn't a Safari cache or Garmin Express backup. Reinstalled 4.1.2. No change.

    The filesystem mounts just fine. Garmin Express works as expected. Previously Nuvi Lifetime Updates worked just fine. This problem with BaseCamp started a year or so ago with a clean install of MacOS X 10.8 on a machine BaseCamp previously performed as expected. Nothing was migrated, everything was installed new.
  • At this point, I'd suggest contacting customer support (http://www.garmin.com/support/). Seems this issue will require a more hands-on approach than I can provide.
  • New theory: Is anyone else running case sensitive filesystems? In other words my operating system (and BaseCamp) is installed on a "Mac OS Extended (Case-sensitive, Journaled)" filesystem.

    Last night I connected a USB drive, erased it with a "Mac OS Extended (Journaled)" filesystem. Fresh 10.8.4 from Apple. New user account on the case insensitive drive. AppStore insisted BaseCamp on my original drive qualified as "Installed" so I ran the old one with new OS on fresh disk. Everything worked!

    Brought the 765 to work to another Mac with case sensitive FS and it doesn't work. I thought it did when I started this thread. Whatever, it doesn't now.

    Is BaseCamp properly communicating with GPS for anyone using a case sensitive filesystem?