Issues with BaseCamp 4.1.0

Former Member
Former Member
There are some serious device connection issues with BaseCamp 4.1.0. That is why we pulled it from the auto-update servers. You can still download it from http://www8.garmin.com/support/download_details.jsp?id=4435 if you want to.

We are working on fixing the most pressing issues. They will be addressed in BaseCamp 4.1.1.

I'll outline the 2 most common issues and how to work around them in case you already installed 4.1.0:

1. You have a device connected and start BaseCamp, or you have BaseCamp running and connect a device -> BaseCamp stops responding.
Fix: This is most likely caused by a gpi file on your GPS. Look for 006D135900.gpi in the .System or POI folder. Rename the file to something else (006D135900.bak for example). Restart BaseCamp.

2. BaseCamp 4.1 does not recognize your Nuvi, but earlier versions of BaseCamp did.
Fix: Switching the device to Mass Storage mode might fix this. Disconnect the device. Turn it on. Go to the Odometer screen (View Map, tap speed). Press your finger on the odometer for around 10 seconds. A debug screen should appear. Go to MTP settings. Select Mass Storage mode. Connect the device to BaseCamp.

I apologize for all the trouble. This is something we should have caught before releasing, but it slipped through somehow.
  • Hi,
    I updated BaseCamp from 4.0.5 to 4.1.0.
    BaseCamp 4.1.0 does not recognize my nuvi 3590LMT as GPS device.
    4.1.0 recognize simply as a Memory Card.
    Map and Data in my nuvi 3590 are not displayed.
    OS of my PC is Windows 8 Pro x64.

    I switched 3590LMT to Mass Storage mode and started BaseCamp 4.1.0.
    BaseCamp started to recognize nuvi, but 3590 stopped and fell in shutdown.
    I tried same operation for BaseCamp 4.0.5, behavior of 3590 is same as 4.1.0.
    I think that Mass Storage mode is not compatible with BaseCamp.



    Did you read the FIRST POST in this thread?
  • Former Member
    0 Former Member
    You're confused. It's obvious to a blind baboon that there is no problem between Mapsource and any Garmin map set because a comprehensive test looking for a few post codes proved it worked perfectly. The people you see complaining of Mapsource crashes with 2013.3 in other forums you frequent or when you use Google are obviously similarly deluded; [waves hand in front of your face] everything is fine, this is not the problem you are looking for. If anything is making Mapsource crash it's one of these newer GPS units even if you don't own such a device.


    With all due respect KWELLER I think that it is you that is possibly confused. There have been countless posts regarding MapSource crashing when certain locations are clicked upon. That it isn't for you is maybe a reflection that you are lucky not to have clicked on these specific locations. However, for the many that have suffered from these crashes this is a BIG problem because it creates a loss of confidence in the product. Imagine for a moment yourself spending quite some time on creating and modifying a route to suit you and/or your groups needs only to click on one final point and whoosh, crash and start over again. Are you suggesting that the many that have reported this problem are all delusional? And let me make one point clear - we are talking about MS crashing during the route planning stage NOT when a GPS is connected to the computer. Whilst of course you are allowed to express an opinion I would suggest you temper your enthusiasm to make bland personal statements when you simply do not know what you are talking about.
    Getting used to Basecamp is simply not an option for many at this time for several reasons. Not only is the application in much need of refinement, and gawd, we're on version 4.1 now and still it's full of bugs/things that don't work e.g. the 'Find' function that has been accepted by Garmin (search for relevant posts if you think this is yet another delusion) along with more motorcycle related issues. You obviously don't ride a motorcycle or plan routes for one and if you do kindly post how you manage to place a via point on a junction so that it won't be announced/flagged filling up the navi screen with useless clutter. The work round for those bold enough to TRY to get used to Basecamp is to create their desired route(s) in the former, export as a gpx and then import into MapSource for a recalc. What a load of faffing around and in my view simply brought about by Garmin releasing a product that was nowhere near ready for primetime release and most probably brought about by market pressures as a result of losing sales to other gadgets where navigation is possible.

    Edit: oh by the way, could you kindly state the source of these comprehensive tests that have been conducted along with the test results. If done by yourself of course I feel sure that you will provide we Baboons with some test data. I feel pretty confident in stating that I doubt we'll see anything along these lines posted by you.

    Edit 2: I'm even more confused now. Having gone back a page I've now come across this from you. Which statement is true as they are conflicting?

    I have no confusion. The 2013.3 maps for both EU and NA can cause Mapsource to crash; it is nothing to do with any GPS hardware and everything to do with the latest release of the maps. In identical circumstances the 2013.2 and earlier maps do not cause the crash, 2013.3 does.


    Do you really think I'd be struggling with Basecamp in its current form if I could get Mapsource to work reliably with the latest maps?

    Kevin
  • Former Member
    0 Former Member
    With all due respect KWELLER I think that it is you that is possibly confused. <snip>


    You don't do irony do you...

    Try reading the thread.

    Oh, and we definitely don't do motorcycling but we've spent countless hours using Photoshop to create all the photos on www.thewellers.net; we're quite expert now...
  • Former Member
    0 Former Member
    Try reading the thread.


    I have. Are the quotes I attributed to you correct or not. They are conflicting are they not?
  • Former Member
    0 Former Member
    Another Issue to Report to Developers.
    When Maps are on GPS ONLY Adress Search does Not work.
    If Maps are on Computer Adress Search works Satifactory.
  • Former Member
    0 Former Member
    Guys, tempers seem to flare a little bit here.

    Please try to stay respectful and constructive or I will be tempted to use my mod powers.

    Regarding the actual topic at hand: I have heard about issues with 2013.3 and MapSource, but there isn't much I can do because MapSource is discontinued. You can still use MapSource as long as you like, but we will not offer any support. BaseCamp is the recommended software to use. Please let us know how you are struggling with BaseCamp and what we can do to help you.

    GRAYBIRD0, I am sorry to hear using the device in Mass Storage mode is not working for you. I am afraid you have a different issue then which is not one of the two that I described in the thread you referenced. Mass Storage mode certainly is compatible with BaseCamp. This almost sounds like a device issue to me. Did you try to contact Product Support?
  • Former Member
    0 Former Member
    Hi,
    I'm having the same 'crash' issue since Basecamp 4.1.0 installed. Sussamb, you posted a link to 4.0.5 for Windows. I tried mooching around for the Mac version but no luck. Do you (or anyone else) have a link I could use?

    Thanks
  • Former Member
    0 Former Member
    Hi,
    I'm having the same 'crash' issue since Basecamp 4.1.0 installed. Sussamb, you posted a link to 4.0.5 for Windows. I tried mooching around for the Mac version but no luck. Do you (or anyone else) have a link I could use?

    Thanks


    Have you tried to check for 006D135900.gpi on your device and deleted/renamed that file?
  • Former Member
    0 Former Member
    Hi Falagar,
    I searched for any '.GPI' files. There are none. I have a 1450LMT by the way. Can I help any other way?

    Thanks
  • Former Member
    0 Former Member
    Hi Falagar,
    I searched for any '.GPI' files. There are none. I have a 1450LMT by the way. Can I help any other way?

    Thanks



    Never mind. I used Apple's time machine and plucked a copy of the .app file from early January from the backup, restored using that file. Everything is fine now

    Thanks again,
    Jim