Jump to content

TAZ427

+Premium Members
  • Posts

    69
  • Joined

  • Last visited

Everything posted by TAZ427

  1. Sent my info to Laval K-9: Nov 11, 2023 Name received from Laval K-9: Nov 26, 2023 Sent my gift: Dec 13, 2023 My gift arrived at destination: Dec 19, 2023 I received a gift: Dec 15, 2023
  2. Sent my info to Laval K-9: Nov 11, 2023 Name received from Laval K-9: Nov 26, 2023 Sent my gift: Dec 13, 2023 My gift arrived at destination: I received a gift: Dec 15, 2023
  3. MAIL SENT: 09/20/2023 NAME RECEIVED BY ME: 10/04/2023 MISSION SENT BY ME: 10/23/2023 OUTGOING MISSION ARRIVED AT DESTINATION:10/28/2023 INCOMING MISSION RECEIVED BY ME: 10/12/2023
  4. Sent my info to Laval K-9: Nov 11, 2023 Name received from Laval K-9: Sent my gift: My gift arrived at destination: I received a gift:
  5. MAIL SENT: 09/20/2023 NAME RECEIVED BY ME: 10/04/2023 MISSION SENT BY ME: OUTGOING MISSION ARRIVED AT DESTINATION: INCOMING MISSION RECEIVED BY ME:
  6. MAIL SENT: 09/20/2023 NAME RECEIVED BY ME: MISSION SENT BY ME: OUTGOING MISSION ARRIVED AT DESTINATION: INCOMING MISSION RECEIVED BY ME:
  7. Sent my info to Laval K-9: March 8, 2023 Name received from Laval K-9: March 9, 2023 Sent my gift: March: March 16, 2023 My gift arrived at destination: March 20, 2023 I received a gift: March 20, 2023 From FlagLady - Thanks for the Coins and Candy
  8. Sent my info to Laval K-9: March 8, 2023 Name received from Laval K-9: Sent my gift: My gift arrived at destination: I received a gift:
  9. Joyeux Noel Everyone! Sent my info to Laval K-9: 11/17/22 Name received from Laval K-9: 11/26/22 Sent my gift: 12/07/22 My gift arrived at destination: I received a gift: 12/05/22
  10. Joyeux Noel Everyone! Sent my info to Laval K-9: 11/17/22 Name received from Laval K-9: 11/26/22 Sent my gift: 12/07/22 My gift arrived at destination: I received a gift: 12/05/22
  11. EMAIL SENT: 09/14/2022 NAME RECEIVED BY ME: 09/25/2022 MISSION SENT BY ME: 10/17/2022 OUTGOING MISSION ARRIVED AT DESTINATION: INCOMING MISSION RECEIVED BY ME: 10/14/2022
  12. EMAIL SENT: 09/14/2022 NAME RECEIVED BY ME: 09/25/2022 MISSION SENT BY ME: Preparing OUTGOING MISSION ARRIVED AT DESTINATION: INCOMING MISSION RECEIVED BY ME:
  13. EMAIL SENT: 09/14/2022 NAME RECEIVED BY ME: MISSION SENT BY ME: OUTGOING MISSION ARRIVED AT DESTINATION: INCOMING MISSION RECEIVED BY ME:
  14. Update: 12/15/21 Sent my info to Laval K-9: 11/24/21Name received from Laval K-9: 11/27/21Sent my gift: 12/10/21My gift arrived at destination: 12/15/21 (per tracking notification.)I received a gift:
  15. Sent my info to Laval K-9: 11/24/21Name received from Laval K-9: 11/27/21Sent my gift: 12/10/21My gift arrived at destination: 12/15/21I received a gift:
  16. EMAIL SENT: September 15, 2021 NAME RECEIVED BY ME: September 26, 2021 MISSION SENT BY ME: October 9, 2021 OUTGOING MISSION ARRIVED AT DESTINATION: October 26, 2021 INCOMING MISSION RECEIVED BY ME: October 6, 2021
  17. I'm in! Sent my info to Laval K-9: Feb 26thName received from Laval K-9: March 6thSent my gift: March 10thMy gift arrived at destination:I received a gift: March 11th Updated: Shipped out gift!
  18. I'm in this year! Sent my info to Laval K-9: 11/14/2020Name received from Laval K-9: 11/28/2020Sent my gift: 12/09/2020My gift arrived at destination:I received a gift: 12/07/2020 Info Updated 12/09/2020
  19. Yes you can. You can select/deselect the gpx files you want to be active/inactive on the device via the filter screen. That's probably one of the nicest new features I've seen to date. I end up using c:geo and have the specific caches in separate lists to do this, it would be nice to have on the GPSr.
  20. Yes. Previously, if a LIVE GC upload was made, any GPX/GGZ data already on your device was completely removed from the SQL database, leaving you only the information brought by the LIVE GC upload for the geocaches in that upload. If the LIVE GC data was 'removed' from the Oregon 7xx via the Geocaching Options on the device, existing GPX/GGZ data was not restored, leaving you with no information for those geocaches. Firmware 2.70 now simply recognizes when you already have GPX/GGZ information on your device for geocaches in the LIVE GC upload and does not change anything for those caches. Of course, this means you can not get any updated or newer information for these, so they still have not implemented the best solution, but it is an improvement. I was really hoping they would either do as before, and overwrite the SQL database with the newer information UNTIL you remove the LIVE data, and then restore the GPX/GGZ data already on the device, OR simply show both the LIVE GC geocache data AND the device GPX/GGZ geocache data simultaneously, like they used to show both GC.com and Opencaching.com data simultaneously. IE, you might have two listing for the same cache, one is from the device GPX/GGZ data, the other is from the LIVE GC upload. Simply adding a special symbol or note to the listing would help the user differentiate between the LIVE GC and GPX/GGZ entries. GARMIN, are you listening? I'd like it to update to the latest online information, just so long as it uses my account and corrected coordinates. If it doesn't use this, then I don't want it overwriting my GPX/GGZ unless I explicitly tell it to.
  21. It is documented here 8^) This is pretty much my point. It's known well enough to be documented on wiki's but it's not in official Garmin documentation such as their User Manual http://static.garmincdn.com/pumac/Oregon_6xx_OM_EN.pdf I ended up learning more about my device from the garminoregon6xx.wikispaces.com than I did from Garmin (i.e. manual and their webpages.) I don't know when that page came about, but I didn't find it until sometime after Geowoodstock 2013 at which point I had it a couple weeks before going to Geowoodstock 2013 and then got to spend a lot of time getting very familiar with it's capabilities as we had a long roadtrip from Houston, TX to Lakeland, FL Overall I still love my Oregon 600, but there's just those couple of things that I need to complain about on occasion. My pet peeve was probably more about the fact that Garmin didn't document that you need to calibrate it every time and also implied that it was calibrated from the factory and would auto-calibrate over time in their manual which either it did a crap job of it or didn't do it at all. I won't give Garmin any credit for a community driven wiki page that has it documented well.
  22. I suspect the material and charge level inside each battery affects the compass reading to some small degree, and the calibration is to offset that value. Each time the batteries are removed, the GPSr must assume the newly installed batteries are not the same batteries removed, and re-calibrate to the 'new' batteries. While there is some small amount of truth to this, it's should be minimal, hence the some small degree. It appears to reset to the factory calibration, which is awful (at least on mine and every person that I know IRL that ones one.) I even tried it with their 'Battery Pack' that I borrowed for a test and still had the same experience. The manual actually states that it was calibrated at the factory, and uses automatic calibrating by default. And it says nothing about needing to re-calibrate after replacing the batteries or that it goes back to factory calibration settings (which appears to be the case, and which are complete crap.) I've never seen it auto calibrate - I've used it for couple long days of caching with frustration the compass being bad and it never got better when I first bought it. It wasn't until I did some looking online and found others that had discovered you need to recalibrate it after changing the batteries did I figure this out. I'd even accept it to a degree if Garmin would have put it in their documentation something like "For best performance, you should re-calibrate the compass after swapping out batteries"
  23. My 650 froze so often I returned it to Garmin after 11 months. Many people said theirs was fine. Garmin replaced it with a brand new one - which did exactly the same thing. Sometimes I would be removing batteries and putting them back in 3 times an hour. (I'm fairly sure it's power related as when the batteries discharge somewhat it actually gets more stable) I get that occasionally on my 600. There is no rhyme or reason to it. Sometimes I can go all day with no issues, other times I need to pull the batteries several times an outing. (For the record, my GPSMAP 62s also did this, so I think it's a common element in some of the firmwares). My caching buddy uses "find next closest" quite a bit, and you have to wait a bit before actually pressing it. I think the device takes a bit to mark the cache as being found. We both use GGZ files when we load our devices with GSAK. Never pulled the batter for the lockup. I simply hold the power button until it powers down and then power it back up. I prefer not to pull the battery as that means I need to recalibrate the compass. Which is another pet-peeve of mine. Why does the compass calibration go out when you pull the battery. I'd think they'd keep the info in long term data storage, but it doesn't appear that way as my compass is never happy after pulling the batteries. One recommendation is to user key (button below the power key) quick push to toggle the screen. It makes life a lot easier if you're hiking and you toggle the screen off as it also stops the touch screen actions (i.e. you're not in some remote menu or didn't accidentally change all your filter settings from it bouncing around.) After you use it a couple times this way, it becomes second nature to hit the button when you grab it to look at at and when you put it away. Everything else stays active with the screen is off, and the on is near instantaneous so it's a great feature.
  24. Last month the garmin let me down - I'd loaded caches from gsak as usual, tested they were all there, set it to the first one. I arrived and did the first cache, hit "Find next closest" (extremely useful feature) and... Nothing. It had lost every other cache. So I switched to the phone and C:Geo. I had to miss the next two caches as I climbed the hill far enough to get a signal, and c:geo took about 20 minutes of weak signal to load the 20 other caches I wanted to do, but it did so and I was able to rescue most of the day. I mention this because it was the first time I used C:Geo for an extended time and it wasn't as good for me - in fact I ended up copying the coords of each cache onto the garmin and setting them as a waypoint for navigating. The "Going backwards" issue is my assumption of why C:Geo would freeze. The screen would stop responding and eventually Android would give its "No longer responding, Wait/Close" warning and I had to bail out. I then learned that if I didn't go from cache to cache each time, instead navigating back from each cache once done to the first menu page, the crashes stopped. So I'm assuming, rightly or wrongly, that it's not freeing memory when used in the way I was doing so. (The phone is a Moto-G4, 2gb ram and plenty of onboard memory, everything else runs well) I don't want to be negative about c:geo because it's the best I've tried and it's truly awesome that it's free and not crippled with adverts. It's just... I don't find the interface as intuitive as Garmin (personal choice) although every feature I want is there, somewhere... It is difficult to be fair and impartial because each of us forms a strong routine for doing this stuff; we have a personal set of tools, systems and methods and there is probably a default negative position when we have to change from that routine. Much as I like tinkering with software and maps, I'd rather things worked perfectly and as I want them when I'm out and caching, allowing me to focus more on my surroundings than on the technology. My perfect system probably will never exist unless I write it, and its user base will be exactly 1 if I do. I had pretty much the same question. And with the exception of maybe opening a list w/ > 30K geocaches in it. I've seldom seen it crash in the past 5yrs or so (not sense the first few months or so after the group of Android developers took it over from Caramichael or whatever the original creators name was back in 2011 - and then the few issues do to API changes from Groundspeak which were quickly patched.) That said, i've got the same caches stored on my phone as my GPSr. I tend to sync them together w/ GSAK every couple weeks or so and keep all caches w/i about 65mi fresh. The one advantage that c:geo has is definitely being able to update caches as occasionally when looking you want to pull old logs, pictures, and sometimes even the refresh you'll find out that the cache was removed and archived the day before I have had the Oregon do the freeze when trying to get Hints, Logs, and other Details. And also had it select the same cache that I'm at when hitting find next cache (got to let it sit for several seconds after marking cache as found to avoid this.) Like was mentioned everyone has there own routines. I prefer my Oregon 600 while walking a trail to grab caches and c:geo when Navigating to a cache by car. And I'll more often then not pull out my phone if I want extra details about a cache, or if I want a quick Sat elite view. As far as accuracy. I can't say I see much difference between my Galaxy S5 vs my Oregon 600. And I'd say my S5 was better than my Oregon 450 was (no GLONASS on the 450)
×
×
  • Create New...