lee737

I'd love a Smart-GPSr - imagine a dedicated GPSr, waterproof/shockproof, with WiFi and satellite comms - would be cool to be able to live update like an iphone when in remote areas, I wouldn't like the network costs though.....

My son and I are about to release our first bugs - just a tag attached to a 20c piece minted in the birth years of him and his brother. Shouldn't be *too* attracted to thieves (sorry - <cough> - collectors).....

As a land manager, you have the right to dictate some rules for caches on your land - like if CO absent for x time, doesn't sort out maintenance issues in x time, the cache will be removed.

If the CO is absentee, the archived cache should be removed by any responsible cacher. You are going to get a whole bunch of differing opinions.... I personally would do as you suggest (especially if there were innocent trackables trapped), after trying to lever the cache out/rock up. or - what colleda said above.....

I would say it depends on what you are doing with the string, and if you need a low/high visibility cord or not....

We need a baiting program - send out some photos of bugs that are definitely not in circulation, then instantly delete the profiles of anybody who logs a find on them.....

We picked up a travel bug in Australia on the weekend, that is on its way from Norway to New Zealand, luck has it that we are about to travel to NZ in Dec, the owner is happy for us to mind the bug until then, then it will accomplish its goal.....

I would definitely vote for this motion.....

Doubling up containers works well - mainly for larger containers of course.... I've seen ammo tins where a similar sized plastic container inside holds the log/swag, always dry..... We have New Zealand made 'Sistema' containers here that I believe are similar to Lock n Lock, and are very waterproof....

I made some changes, and the same problem has recurred today. This time, I loaded a single GPX file (exported from GSAK) onto the SD card, holds about 2500 caches approx - the same ones as before, but before, they were in straight PQ GPX files. Was going OK today, apart from a map-freeze (yes, another bug!), then the dreaded seize up on trying to search for a WP in WP manager. Not as bad, was able to turn the unit off with the power button this time. Removing the SD card solves the problem, but leaves the unit sans-caches, re-inserting the SD card reproduces the problem exactly. I assume it is the caches, but could be the SD card also?

Having to pull the batteries to reset just rubs in the salt.... Should never be needed in any well engineered electronic. There is no reason that these units should be less reliable than my iPhone, given how many fewer tasks they have to do, and the cost of the unit.

Based on leads in this thread, I just installed GSAK, added my PQs, then exported a GPX file for the Garmin. Turned unit on, tried to navigate to a cache, locked up on first one! I had to remove batteries to get it going, but it hasn't skipped a beat since then, and I haven't been able to reproduce the crash, maybe it needed the power cycle to refresh.... Can this be done on the Oregon without removing the batteries? - because that is a real nuisance.....

Mine crashes occasionally - but twice now in what I'd call a critical way - ie, the problem was not solved by a reboot. Most times I take it out, and it will run for several hours, it will be fine, then when you least expect it.... boom.

The first time it happened, I loaded fresh PQ files, this time, I haven't added new ones yet, just deleted the old. I'll put the new PQs on the SD card now, so next time it happens , I'll try your suggestion and see what happens. To be honest - I love this unit when it is working, but it crashes too often to be taken seriously as a potential piece of safety-critical equipment, I won't get rid of my Gecko yet....

Congratulations.... we just got our 'ton' a couple of weeks ago, we bought a geo-achievement patch for my son, he is now eyeing off the 250 patch.... good times.....

I've noted several 'types' of crash with this unit - normally seems fairly random, resolved with a power cycle, very irritating nonetheless..... In the past month or so though - twice, a reproducible crash has occurred - without warning, trying to search for a waypoint crashes the unit. The first time it occurred I would enter the search letter, say 'W', hit the tick, then the unit would be locked, with a screen corruption looking pattern overlying the normal display. Then yesterday, the same thing happened, when I was searching for a waypoint, hit the S key to start searching, and that locked the unit, literally, the S button enlarged like you had just typed it and that was it, was totally unresponsive. These last problems were different to the normal crashes - the power button was unresponsive, so it took a battery removal to get the unit functioning, but then the problem would recur, in exactly the same way. Now the solution - deleting the pocket query files worked to restore the unit to normal function, albeit without any caches..... Last time this happened, I just transferred new PQ files in, and all was OK, until yesterday.... I've googled this a lot, and can't find any solutions, has anyone had this and found a better solution? I'm worried this will occur in a remote area when I need the GPS to navigate, and don't have a laptop to get it working. Suffice to say, this could be the last Garmin we buy...... cheers Lee

I routinely see logs entered with the date found 'Tomorrow' - we have some fast cachers here....

I disagree with this - I would log a DNF +/- a NM (depending on the situation) ... if the CO fixes it, great, if not, it should be archived.

I don't agree with propping up caches (old or new) that aren't being cared for, apart from emergency type stuff - draining out water, perhaps an emergency log, but these should then be accompanied by a NM log so the problem can be fixed. Adding a new cache for any reason apart from being asked to by the CO is a mortal sin.

Small gear carabiners, safety whistles, LED torch keyrings.....

I hope I don't get considered a spammer!

We have heaps of this sort of cache around here - the cache is there, but wet/mouldy/full of ants etc..... I would log a NA given the previous 3-4 NM logs have been ignored... The CO seems too busy finding caches to maintain this one.

The Garmin Monterra runs Android, has wi-fi but I'm not sure about a data sim. I use my iPhone in conjunction with my Garmin Oregon for the reason you mention above.

Exactly. Anyone can encrypt something with AES and a decent password, even the NSA would struggle (we assume!)......

When you seriously can't find a cache after a good look, when most of the previous logs say "Easy find!", "Quick park and grab!"..... then the day after your DNF, the "Obvious spot! TFTC" logs start again..... embarrassing....even worse when it is a large cache.