Jump to content

Can't import caches into Garmin Oregon 450


Recommended Posts

I am wondering if anyone has had a similar problem and if they know of a solution. I have a PC and recently I can't get caches to import to my Garmin Oregon 450. It was working fine before. The computer recognizes it as being plugged in but Geocaching.com isn't finding the device. Any suggestions?

Link to comment

I am wondering if anyone has had a similar problem and if they know of a solution. I have a PC and recently I can't get caches to import to my Garmin Oregon 450. It was working fine before. The computer recognizes it as being plugged in but Geocaching.com isn't finding the device. Any suggestions?

Browser settings may change after an update. Are you trying to use “Send To” from a Windows PC and Internet Explorer only? It may work from Firefox. I use that in a cache emergency :anicute: to “Send To” my GPSr. Otherwise, Pocket Queries are ideal, or at least loading a “GPX File” manually. The “Send To” button copies the GPX file automatically, but you have more control over the process by doing the exact same thing manually. And that doesn't break as often. :anibad:

 

In case you want to try copying files yourself, the folder to place GPX files on the Oregon is [OR Drive]:/GARMIN/GPX

Edited by kunarion
Link to comment

Oh, thanks! I had been using Chrome, and I switched to Safari first to try it because I already had it downloaded (was going to try Firefox after that). Safari did the trick. It made me download some software (Chrome had also asked me to download this software but it still didn't work when I did that). SO happy the GPS wasn't broken. Thanks again.

Link to comment

The Garmin Communicator plugin is built on an old platform that Chrome is no longer supporting. Other browsers still support it, but might disable these plugins by default.

 

Regardless, adding caches one at a time using the "Send to GPS" is at best burdensome and at most irresponsible. That's because your Oregon can only read a maximum number of .gpx files, and the way you go about it, you load 1 file per cache. Meanwhile, with pocket queries, you can load up to 1000 cache listings at a time per file and have all of the caches in an area with you when you go out, which means choosing your caches while you're out instead of choosing them before you leave.

Link to comment

Oh, thanks! I had been using Chrome, and I switched to Safari first to try it because I already had it downloaded (was going to try Firefox after that). Safari did the trick. It made me download some software (Chrome had also asked me to download this software but it still didn't work when I did that). SO happy the GPS wasn't broken. Thanks again.

You're welcome! :P

Link to comment

I didn't know that. Why is it "irresponsible"--could it harm your GPS? It does sound like the best way to do things.

 

 

The Garmin Communicator plugin is built on an old platform that Chrome is no longer supporting. Other browsers still support it, but might disable these plugins by default.

 

Regardless, adding caches one at a time using the "Send to GPS" is at best burdensome and at most irresponsible. That's because your Oregon can only read a maximum number of .gpx files, and the way you go about it, you load 1 file per cache. Meanwhile, with pocket queries, you can load up to 1000 cache listings at a time per file and have all of the caches in an area with you when you go out, which means choosing your caches while you're out instead of choosing them before you leave.

Link to comment

What he is trying to say is that your Garmin can only hold so many GPX files but GPX files can hold multiple caches. Your device can only hold 200 GPX files but can hold 5,000 caches. So it is much better to use PQs or other methods to load multiple caches in one gpx file. Doing it the way you do can quickly fill up the device and after 200 it will not read any more caches you added. While one gpx with 5000 caches all will be read.

Link to comment

I think the specs were changed to 2000 gpx files, but that includes all of your routes, tracks, and waypoints, which are stored separately from geocaches.

 

The reason I say "irresponsible" is that by using the "send to GPS" button, you never have to open your GPS in a file window and look at what you have stored on there. Your found caches get hidden from searches on the device, but the .gpx file still takes up space in the memory. I learned this the hard way back when the file limit was 200 .gpx files, and caches I had loaded for an area didn't show up when I got to the trailhead. I immediately started setting up pocket queries that evening and haven't looked back since. Here are some reasons why pocket queries are superior to loading using the "Send to GPS" feature:

 

1. 5000 cache listings loaded in as few as 5 files.

2. Keep your cache listings up to date with the latest logs by running the PQ weekly.

3. Clean found listings off your GPS by selecting "I have not found" as part of your PQ.

4. Keep disabled listings off your GPS by selecting "are enabled" ensuring that you don't go after a cache that isn't there at the time.

5. Never miss a cache. You'll always have caches loaded for the area you are heading.

 

Yes, it seems like overkill to keep thousands of caches on hand, but it means you can make a find on a whim and you're not limited to the few you've added one at a time.

 

That's not to say that the "Send to GPS" function isn't useless. But I use it sparingly, mostly when I've run my PQ recently and then a new cache is posted that I want to run out for the FTF.

Edited by mineral2
Link to comment

I know this is a separate thread but I haven't actually done a pocket query yet... going off to search for instructions.

 

Thanks, all, for your help and information.

 

I think the specs were changed to 2000 gpx files, but that includes all of your routes, tracks, and waypoints, which are stored separately from geocaches.

 

The reason I say "irresponsible" is that by using the "send to GPS" button, you never have to open your GPS in a file window and look at what you have stored on there. Your found caches get hidden from searches on the device, but the .gpx file still takes up space in the memory. I learned this the hard way back when the file limit was 200 .gpx files, and caches I had loaded for an area didn't show up when I got to the trailhead. I immediately started setting up pocket queries that evening and haven't looked back since. Here are some reasons why pocket queries are superior to loading using the "Send to GPS" feature:

 

1. 5000 cache listings loaded in as few as 5 files.

2. Keep your cache listings up to date with the latest logs by running the PQ weekly.

3. Clean found listings off your GPS by selecting "I have not found" as part of your PQ.

4. Keep disabled listings off your GPS by selecting "are enabled" ensuring that you don't go after a cache that isn't there at the time.

5. Never miss a cache. You'll always have caches loaded for the area you are heading.

 

Yes, it seems like overkill to keep thousands of caches on hand, but it means you can make a find on a whim and you're not limited to the few you've added one at a time.

 

That's not to say that the "Send to GPS" function isn't useless. But I use it sparingly, mostly when I've run my PQ recently and then a new cache is posted that I want to run out for the FTF.

Link to comment

I haven't actually done a pocket query yet... going off to search for instructions.

Pocket Queries are easy, once you get the hang of them. I often have a PQ set to run on a Saturday, and load the files (usually two files, caches and parking coords) that morning. It's for a 12-mile radius from home (a list of almost 1000 caches here), and I can head in any direction I wish, and find caches. If I'm visiting friends somewhere else, I run a similar PQ for that town, too. Sooo much better than loading one at a time. :anicute:

Link to comment

I think the specs were changed to 2000 gpx files, but that includes all of your routes, tracks, and waypoints, which are stored separately from geocaches.

Apparently

 

https://support.garmin.com/support/searchSupport/case.faces?caseId=%7B0b02f820-03db-11e0-e050-000000000000%7D

Oregon 450(t) or 550(t)

 

2,000 GPX files

2,000 waypoints

5,000 geocaches

200 routes, 250 points per route

200 saved tracks

2,000 archive tracks*

10,000 points per track

100 custom map tiles

250 BirdsEye Imagery files

Mapping segments vary by model:

Oregon 450, 550: approximately 4,000

Oregon 450t, 550t: approximately 3,500 (due to internal mapping)

*Archive tracks do not count against GPX file limit; 1 archive track per gpx file.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...