Errors in reading Oregon 550 files in Basecame.

Former Member
Former Member
I load my tracks & waypoints from Basecamp 3.0.6 to my Oregon 550, it doesn’t appear to matter whether I load it to the unit or to the micro SD card (the results are the same). I unplug the 550 from the USB cable, boot the 550 and edit the tracks (i.e. show on map, change track colors, send to archive, etc.) and then I re-plug the 550 to the USB cable. Basecamp reads the files in the 550 and then an error window pops up and says that it has had a communication error in reading the files. The error message lists the exact same tracks I edited in the 550 a few minutes before. Consequently, these edited tracks do not show up in the read files in the left library pane; only the tracks that I did not edit show up in the library. It appears to me that there are two possible reasons for this error. Either the Oregon 550 is incorrectly coding the edit change so that Basecamp can read them or Basecamp is not set up to read these files after the Oregon 550 has changed the files.
Has anyone else experienced this problem or is there a known fix for this problem?
I am running Windows 7 64 bit, Asus Crosshair 4 motherboard , 8 gigs of Corsair Dominator ram and an AMD Phantom 2 3.4 MHz 4 core CPU.
  • Former Member
    0 Former Member
    Yet another solution to the track color problem.

    I recently read the last reply on track color problems with the 62s named "Track color problem with the GPSmap 62s" by [email][email protected][/email]. I went to the site GPS-utility and it appears they want $60 to register. Again I will add that we should not have to be going through this. Please Garmin, get it together and fix this problem once and for all.
  • Former Member
    0 Former Member
    Garmin 550 team says they will fix track color error problems.

    In the last couple of weeks, I have been in contact with the Garmin 550 software team and they assure me that fixing the issues discussed in this post is on their list and it will be fixed. No definite date was given, but I am confident they are working to solve this problem. They seem to be very committed to their work and they are eager to correct problems with our Garmin products.