MotorBug

I just bought a 30 last Friday, updated from 2.4 that was on it in the box to 2.7 and used it for the first time yesterday. It worked great, no sticky and good accuracy. I hate to fix it if it ain't broke but the description of 2.71 beta sounds interesting. Is it possible to revert to 2.7 if 2.71 screws things up?

Something is strange here. My eTrex 30 is plugged in right now and I don't see an 'All Data' folder. Neither do I see one in Basecamp when the program is open nor in the PC basecamp file structure when I open that. EDIT: Okay, reloaded basecamp and under devices it shows the eTrex and 'All Files.' That shows the caches and tracks. But I still don't see a way to process/play with the track. EDIT2: Okay, I'm seeing properties now. Whew! That is well hidden. I still prefer MapSoure's way of doing this. One right click and you are there.

See it, correct it, save points. Correct as in join two segments if the GPS shuts off as my 60CSx often does.

Can you tell me how to process a track log in Basecamp? I just don't see how to do that. A friend who is much better at this stuff still uses MapSource with a work around. I haven't tried this yet with my 30: A couple work arounds I use once I mount the 62s as a drive: * Start up Basecamp and let it download the info off the 62s. I then export a GPX or GDB file of the 62s "All Data". That than can be used in Mapsource or in ExpertGPS. The tracks included. or * Go to the GPX directory on the 62s and just open the GPX files directly in Mapsource. I then save the data off locally. Been doing that anyway for years as I use the GPS tracks as a sort of diary of my wanderings. The only thing I seem to loose with this is the data from the heart rate monitor. I don't use that all that often, so not a big miss. I don't get why Garmin is disconnected on Basecamp versus Mapsource functionality. Stupid.

Ah, just now see that this info was previously posted but I will leave it as it is all in one place. --------------------- 2.71 beta released for the eTrex 20/30 http://is.gd/tZjW1Q Change History Changes made from version 2.70 to 2.71: Improved GPS response at low speeds Improved elevation data stored in track logs (etrex 30) Fixed issue with distance to destination data field Fixed occasional overlapping of data fields in the elevation application Problems with this beta software may be reported to etrexBeta@garmin.com Changes made from version 2.60 to 2.61: Improved GPS response at low speeds Maybe this time they got it right. I'm going to wait since I have only used my 30 once with 2.70. Please advise any results with 2.71 beta.

Cached in the hills today under heavy tree cover and my new (2nd) 30 worked perfectly! It did not exhibit any 'sticky' issue and it seemed quite accurate when run side-by-side with my trusty 60CSx. Even had the opportunity to try out the Chirp function. After I came home I re-discovered that it will not upload to MapSource, so updated Basecamp from beta and quickly came to the same conclusion as several months ago that it is a POS. Sorry to be crude, and I'm very willing to hear differently, but that it is. MapSource might not look pretty, but it works. Not so Basecamp. The 30 has not reported any disk errors as did the 1st one I had last December. Many of my geocaching friends have the 62S and they all struggled with sticky and lock-up issues. One thing they found is that when loading a firmware update, delete all gpx files and restart before doing the update. Then restart again before adding back your gpx files. I did that and so far all is good with the 30. It might ever work if you are already on 2.7 on your 30. I'm assuming that you can reload the firmware but I haven't tried that.

Bought my second 30 today. Returned the first in December after it exhibited all the problems everyone has reported PLUS nearly every time I plugged it into my computer it showed 'disk' errors and would not start until I fixed them. I am hopeful that this one is okay. If it sticks, back it goes, life is too short and Garmin support, once excellent, has gone to hell. Thankfully REI has a no questions asked return policy. Anytime. They sell on-line too. If you are the least bit concerned that you may get a lemon, buy there. (Full disclosure: I have no connection with REI other than years of satisfied buying.) Hope to take this to the hills and woods on Sunday. I'll report back how it goes.

Hey Garmin, if you actually read this I'll make you a deal. You fix the sticky issues, I'll buy a second one within 72 hours if you or a lackey of yours replies with details about the fix to this thread. It all starts with one.. . PS I returned the first one cause of the sticky and other problems.

Does it work okay downloading from GSAK not running a macro?

Since you purchased from REI, just return it there for a 100%, no questions asked refund with a smile!

Looks to me like it is an issue. I can see it's uses for some, but at least for me I would rather not see it up top, 5 or 50. I guess I understand why the maps are changed but I would rather pay more and have something useful. I haven't experimented that much, but if routing is seriously degraded then that is a very bad thing. This may not be the place to ask, but the option to reorder or hide sections on the right side of "Your Profile" so I can see the useful stuff first would be good.

I've decided to return my eTrex 30 to REI. Some of the major issues even after reading the manual, applying the update to 2.5 and making appropriate adjustments: 1. Compass and maps continue to lock up under tree cover. Even in the wide open to some degree. 2. Driving about 80 miles with no more that +/- 200 feet elevation reports 4142 ascent and 3865 decent. This regularly happens. 3.It has caused GSAK to crash. 4. Plugging it in to the USB cable results in GPS disk errors about 1/3 of the time. This must be corrected before the computer will see the 30. The USB cable is fine, its a Garmin one that works on every other USB device I have. A friend got one at the same store a couple of days before I got mine. While that 30 has exhibited some map and compass lockup, the firmware update to 2.4 made it less of an issue. It has not exhibited the other problems. Makes me think I got a lemon. Whatever, I am returning it tomorrow. I don't trust it and most of the time have to refer to my 60CSx to make the find. Edit to correct firmware verion update.

I used my 30 for another hike yesterday under heavy and tall redwood tree cover. Often I could not see the bright blue sky of a spectacular winter day in northern CA. After installing firmware 2.5 it seemed to be more accurate and did not freeze up as it did in the first hike with 2.4; however, often there was a 2-3 second delay as the compass adjusted. I know the release notes said nothing about correcting this for 2.5 but I'm not complaining. I don't think it is a 'full' solution but the problem got less severe for me. I was running the 30 along side my 60CSx. On some caches the 30 was more accurate, others the 60 was. Once near the cache site both settled down close enough to make the find. Two friends have recently purchased the 30. One has City Navigator on it and it works well-- got a demo yesterday. I was concerned with the smaller screen size that it might be an issue using it in the car but I did so yesterday and thought it was fine. The other friend had an awful time with freeze up on the first cache, then it mostly went away. Go figure.

Thanks, that was useful. I'm still not seeing any track related name in Basecamp. Does that have to be imported separately? The more I try to do stuff in BaseCamp the more disappointing it becomes. What were they thinking? /rant. I'll try BaseCamp a bit more but it is not encouraging. I was able to drag the 30's track log and geocaches .gpx to MapSource when it is in USB mode so that is a work around to some degree. One weird thing is when I move caches to MapSource the name field changes from the name to the gc number. I use names, not numbers so that is a PITA. The name is now in the comment section but the info that was there is lost. Since this is the first time I have bought a Garmin shortly after release, about how long does it take Garmin to fix the obviously broken stuff? I remember caching buddies with the 62s complain a lot when it first came out but now it seems to be better. I'm willing to wait weeks but not months. I haven't registered it and REI has a great return policy.

I've had my 30 for a few days now and yesterday was on a hike in dense redwood tree cover. The problems recounted above all were present for me. Usually I am not an early adopter on new Garmin stuff and this unit is a bit unnerving for its awful reception and freezing compass. I'll have to go on faith that it will get sorted out. I have some questions that hopefully someone here can answer. For background, I've been using a 60CSx with extensive MapSource transfers. I also have a Nuvi 500 that has the geocaching function but it is convoluted to use and not good trying to pin point something small like a geocache. 1. The eTrek 30 can receive waypoints from MapSource, but not send them to it. When I try to do that I get the message that there are no waypoints on the 30. Can this be fixed with a setting? 2. Because of the above, I tried BaseCamp which is certainly different. Sorting waypoints is cumbersome-- the nice tabs in MapSource are gone. I don't see a count of waypoints like is at the top in MapSource. But my main complaint is that when I create a new BaseCamp map after hiking the caches found still show up as unfound and I can't find a way to see the track log. So the questions: Can found caches be shown in BaseCamp? How to I see the tracks? And can the huge icons be made smaller? I would stick with MapSource if I can get the 30 to send waypoints to it. 3. Has anyone developed custom waypoints for the 30 like are available for the 60 series? Thanks for any info. Tom

Not in gc, but you could do it in GSAK. For example, I found a whole series in a western state that were listed by the CO as 5/5. I changed and locked them all at 2/2 which still might be generous. Then I posted the stats on my gc profile page from the GSAK macro FindStatGen3.gsk and hid the gc generated statistics. Of course you could go the other way and increase the D/T as there are a few that are legitimately underrated. But I have only reduced ratings. One can of worms is enough. GSAK also nicely handles some of the data points fizzymagic mentioned.

As I mentioned in a previous post, we will not be addressing caches that have had "alternative" logging practices exercised on them. Missed that I guess. Seems to me that the non-counting for statistics could be date specific for these types of caches. But I'll just delete my find since I am more interested in correct mileage than numbers.

GC6D43, What in the World Cache? is still messing up stats. Any plans to fix?

By the Lake, GCC3A5 needs to be moved back to terra firma. I found it at N 37° 13.243 W 122° 03.220 GCC716, Urban Assault #4 looks like it is messing up results for most easterly. And GCE042, Tunnel, while active, is unrealistically out in the Pacific. Appears to have been placed before the generally accepted rule of keeping a puzzle cache within a few miles was invoked.

Favorites are fine and all, but I really can't see using them much nor assigning favorites to the 800 plus available to me. But I can understand, sort of. Numbers hound that I am-- almost-- I ain't that particular. A smiley is a smiley. And yes, I do appreciate the quality hides. What I would like to see, or rather NOT see, is the box that appears every time I log a cache that tells me, rather breathlessly, that I only have "x" finds to go until I get another vote. That is really unnecessary and already annoying. While I am at it, please move this favorites thing to the bottom of the right hand column. The useful stuff should be at the top. Thankfully the type of GPS is moved way down. I really did know since I look at it daily. One last observation.... beta maps don't work for me. No matter what I do they only show Seattle with no options. I will take that as I should do a road trip! Nice update!

An early cache was moved way out in the Pacific Ocean to save the waypoint. This was years ago before all the tools and statistics were available. It is GCA8BE - Emerald Oasis. Actual coords when I found it were: N 37° 42.629 W 121° 52.446 The current location removes the true most westerly cache for all finders. It should be moved back to the mainland or locked out of statistics. Thanks.

Several years ago in a moment of stupidity, I logged GC55A5, Änglamarken, a mis-identified traditional that was an armchair virtual. Now it shows up as my furthest cache as well as most northerly. I would guess this is the case for many a geocacher. I'm very willing to delete my log on this one but it seems the correct action would be to change the category to a virtual and exclude it from the statistics. Please advise if this is a possibility. Thanks.

Works exactly as advertised! I had use a rather clunky method before. This is certainly better. Thanks!

Interesting thread. Certainly gc has changed over the years, not all for the better. I don't have all that many caches still active anymore, part of the reason is some were lame, some were difficult for me to maintain, and some just didn't hold my interest or that of cachers based on logs, so when they needed maintenance they were picked up and archived. A few caches were stolen as were all but one of the travel bugs and geocoins I have put out. Maybe 30 or so, don't really keep track. This has gotten progressively worse over the years. All of that has probably influenced how I handle TFTC and 'Sent from my mobile device' logs. When I get a TFTC only log, I look at how the person logs other caches and what kind of logs I typically get on that cache. If TFTC is his/her MO and fairly new, I email and explain that a longer log, good or bad, would be more appreciated by me and every cache owner I know. I get everything from being ignored to I'm an a**hole. Fine, just give me a log so I know you were really there. When ignored I've even sent a second request for a changed log. I give them a week or so and then delete the log if no response. If I get a changed log, log stands. If it is a random TFTC only and the finder says more in other logs, okay, I get the message, he/she didn't like my cache. No problem, I do that myself. Log stands. 'Sent from my mobile device' (only) used to always get an email worded however I felt might get a positive response-- educating new cachers being the most common. But that is far to common so now I just delete the log and let them figure it out. Most don't even relog or ask why I deleted the log. It might sound like I delete a lot of logs, but actually most situations get worked out. As a cache owner I read every log. I would like something that gives me a reasonable feeling that the finder actually found the cache and signed the log. I generally spot check logs during maintenance or if a real question comes up. If you hit 5 countries & 16 states in one day and include a really nice log on one of mine, your log is probably toast. If I can help a new cacher get going on better logs, everyone wins. I often go back over old cache logs I made years ago and they provide some good memories. If people are logging only TFTC or 'Sent from my mobile device' I suspect they will regret that down the road if they stay with gc. I like the post suggesting "TFTC- placeholder" if in fact that what it turns out to be. Great idea, especially in a FTF hunt. I rarely log immediately from my phone, but will use that when I get a FTF. It's nice to let everyone know that FTF is gone.

Along with moving 20292: Personal Notes for Cache Listings to the bottom of the page, or better yet with an option to turn it off, please return "adding coordinates" to a log back to the top of the log. The bottom is very inconvenient place. Located there it will only add to more people putting corrected coords "in" the log rather than "adding" to the log.