TeamCNJC
-
Posts
208 -
Joined
-
Last visited
Posts posted by TeamCNJC
-
-
The cache information exists in the GPX file. If you delete the GPX file, or re-upload the GPX file without the found cache (i.e., next week's PQ), it won't be there anymore.
-
The last time this happened, the backlog of queued mail just bogged down everything. I switched my PQ delivery to gmail last night. My Friday PQs, which normally arrive at 4am, weren't generated until 6am-ish, and took 25-35 minutes to arrive in my gmail box. I have yet to receive any notifications from yesterday in my Comcast box.
-
I'm guessing that you have Comcast as an ISP. Looks like they're throttling again. Good luck getting through to complain - I was on hold for an hour yesterday. I haven't received a geocaching.com email since 1pm yesterday. Back to gmail for me!
-
I know it's bad form to reply to yourself, but looking back at the change list:
19. Add A905/D900 unlock code communication protocolThis is probably the 2008NT/60CSx fix that some have been waiting for.
-
I read that thread on NT2008 and the 60CSx - I'm not sure what the cause of the original problem is. I don't have NT2008, so I can't check...
Anyone know what "MPC" maps are?
-
On the Garmin web site. Find it here. Number 21 is interesting - what makes the 76x different than the other models?
Change History
Version 3.30 to 3.50:
1. Change number of lines of text in the address field on map feature review page from 4 to 6.
2. Improve robustness when recovering from a partial map load.
3. Limit number of custom POI bitmaps to 64 to ensure enough memory resources. Bitmaps beyond 64 will show the default custom POI symbol.
4. Added better compatibility with Mac computers in USB mass storage mode.
5. Improved pedestrian route calculation for shortest distance method.
6. Added ability to recalculate a direct goto route.
7. Fix issue where MPC maps would use excess file handles and potentially cause a shutdown.
8. Address issue where nearest points search would skip some points.
9. Changed datum used in the the SWEREF 99TM grid to GRS80.
10. Changed datum used in the the Estonian grid to GRS80.
11. Fix potential shutdown when using TOPO West 1999.
12. Fix potential shutdown on track setup for data card when track log files have long file names.
13. Corrected French translation for "Log track points".
14. Improved promptness of the turn review popup.
15. Improve track log recording for sensor products to continue recording sensor data even when GPS doesn’t have a fix.
16. Fix potential shutdown when propagating in a cul-de-sac across a map boundary.
17. Added more time zones.
18. Fix potential shutdown when clearing recent find list when custom POI with custom bitmaps are in the list.
19. Add A905/D900 unlock code communication protocol.
20. Make route recalculation on MPC maps behave like City Navigator maps.
21. Remove lithium ion as a battery choice. For 76x add lithium battery choice. Lithium ion batteries have a voltage that is too high and might damage the unit.
-
It was geocaching - saw an article in the Virginia Pilot while at my in-laws in Virginia Beach. Logged on and saw that there were a few caches within walking distance. Looking for any excuse to get out of the house, it took me an hour to get to the boat store, buy my first GPS, and start hunting caches. Since then I've owned three more GPS units (one was a prize in a Magellan contest).
-
I converted from a MeriGold to a 60CSx last year. It took a while to get used to the button layout differences, but I find that the 60CSx gets me to GZ the first time, almost every time, where the MeriGold would let me wander around a bit until I got to the hide area. I consistently get <12ft EPEs, but I usually use the accuracy circle to decide when to stop looking at the GPS and start looking for hollow logs...
One thing that I found is that the 60CSx, and probably other Garmins as well, use the underlying map as part of the accuracy circle. While canoeing along the Canadian border, using the US Topo maps, I found that the accuracy circle widened considerably when I was in "uncharted" Canadian waters, but paddling 20 feet back in the US caused the circle to dramatically decrease in size.
-
Are you set to "normal" or "battery saver" mode under Setup>System?
-
The only way I was able to find xImage was by a google search, and it was a version released in 2005. Garmin doesn't appear to have any links on their site to it. Do they still support it? Is this version from 2005 the most current?
There's a link directly from the 60CSx web page - here. It's the most current, supported, and works fine.
-
CenTexDodger is right on, but if you reload any waypoints that have the numbering, the device will skip them with the next "mark." For example, if you delete all the waypoints, but reload 001 from MapSource, the next time you hit "mark" you'll start at 002.
-
I travel frequently, and use my GPSr in flight when I have a window seat. Throws off the "average" and "maximum" speeds, but hey, it's fun to be going at 520mph. I've never had a problem on NWA, though I have been asked once or twice what it was. The only other (hopefully obvious) caveat is that if you're asked to turn it off, then turn it off and put it away.
-
I think they mean Jan 19 because i was on there a few hours ago and that didn't exist.
The "rgn" file in the download package is dated 12/6/06.
-
Unfortunately, that doesn't always work. The "background" can change depending on location, type of map, etc. For example, you may have a POI that can be in a marsh area, a park area, on "plain" land, in an industrial (grayish) area, or on/near water. All of those backgrounds will be different.
-
It's a firmware bug - should be fixable via programming.
-
Oddly enough, that worked. Night Display of Topaz shows the POIs, and Ruby does not. I have given this issue over to Garmin Tech Support. They had not heard of this before, so perhaps a solution is forthcoming.
Grimm-
First time? I thought you only got one of those...
Was first discussed here in April: Read this.
I know that I personally emailed and called about this back in August when I found another discussion in the forums here. That, and the inability to recognize the "transparent" color in a custom POI icon, were two of the things that Garmin was working on at the time for the "x" series.
Edit: Added link
-
Another Garmin feature that may serve you well is the POI feature. You can create a custom database of lat/longs for hydrants, drafting sources, etc. under "water sources," then add a category for "mutual aid" consisting of neighboring stations or staging points, etc., all of which could then be uploaded to each unit.
-
EPE=Estimated Positioning Error. That value, calculated and reported by the GPSr, is what the unit thinks it's error is in terms of feet/meters. For example, an EPE of 10ft means that the device thinks it could be off by as much as 10 feet in any direction, hence the accuracy circle.
Accuracy is less a function "settings," and more of a function of the number of satellites in view, their position (to give the best geometry), signal strength, lack of multipath signal "reflections," and a bunch of other stuff. The only real "setting" that could affect accuracy is WAAS on or off - which has been the subject of many, many threads.
-
When I go to from GO TO to MAP on my Garmin 60csx there will be a blue circle around the cache location and the back arrow..... sometimes.. not always.
Why is this??
You'll get the accuracy circle when you're zoomed in far enough to see it. If your EPE is high/accuracy is low, then you'll see the circle when zoomed out, and it will be bigger as you zoom in. Basically, when the cache/waypoint you're looking for is inside the circle, stop looking at the screen and start looking for hollow logs.
You won't see the accuracy circle when you're locked to roads.
-
On a related note:
[sarcasm]
Dear Comcast,
Why is my cable bill $15 more than it was last month? Can you please fix this?
Thanks!
[/sarcasm]
Dear Propers,
We apologize for the error. Your cable bill should be $25 more than it was last month. Your next bill will reflect the proper amount, plus interest. Thanks for bringing this to our attention.
-Comcast
-
Hit "Mark" to mark your current location, then edit it.
-
Thanks for the pointer to 5.41 - I didn't think I'd ever see another update for my ol' MeriGold. It doesn't look like they did much, but I'll upload it just the same, since I still use the unit in my boat.
-
Have you seen the "get off at this exit and get back on the highway going in the same direction" thingey yet? Now that's annoying, but somewhere in the mind of my 60CSx it makes sense.
-
To give a little more detail to embra's response, if you have an SD card reader, you can take the firmware file (i.e., mgold540.hex), copy it to the root directory of your SD card, rename it as firmware.hex, then turn the unit on. Works with versions higher than 4.xx already on the unit.
Oregon question
in GPS technology and devices
Posted
Depending on how you cache, it's not that crazy. There are enough changes over a week or so that I need to redo what's on my GPS, whether it's my new Oregon or my old 60CSx. Since found caches or archived caches aren't in my PQ, my weekly download provides up to date information. And since the found caches, as noted in other places on this thread, don't really clutter anything up at this point, I don't feel the need to clean up - and didn't with my 60CSx either.
To me, the ability to generate and import field notes more than makes up for having to drive by open treasure boxes until next Friday.