Capt. Bob

Accuracy is a human failure. Precision is a machine’s virtue. Precision: GPSr’s are mini-computers and their CPUs are very precise. In other words, two + two will always equal four, it will not equal five no matter how much the user thinks it should. Accuracy: It all starts with engineers (yes, they’re humans) who are great compromisers seeking a balance between usability, accuracy and cost as they try to tame nature. It ends with users (most are human) who don’t read instruction manuals, have short attention spans and cry when they can’t get what they want. The User's Options: Usability, accuracy, or cost - pick the one.

I found my Delorme PN-60w will still generate accurate coordinates if used often. However, if not used for several days it will fail to find some satellites and a large estimated positional errors (EPE) will occur. In that case it needs a Non Volatile Memory (NVM) reboot to acquire all the available satellites. According to this excellent article of the End of Week (EOW) rollover problem (http://www2.unb.ca/gge/Resources/gpsworld.november98.pdf) the satellite acquisition issue may get worse over time or even totally fail. It will be interesting to see what other non-compliant GPSr’s will fail in the April 2019 EOW rollover.

I am beginning to see other problems with the PN-60w that seem to be getting worse. It now takes a long time to acquire satellites which implies the almanac data isn't being read properly. Also the ephemeris data must be affected because once satellites have been acquired the EPE varies wildly over time. (solved the problem with a NVM reboot) It's a shame that Garmin/Delorme won't undertake revising the firmware to correct the date issue. It's irresponsible of them to not notify users of the problem particularly those users, like me, who are paired to inReach. It could be a life threatening situation. I suppose somewhere in their multi-paged legal agreement they are absolved of any liabilities so they don't care.

I contacted support@Delorme.com about the 1999 problem and here is their reply. Hello Robert Thank you for contacting Garmin Product Support and I apologize for the issue experienced with your DeLorme PN-Series GPS device. Due to how the device uses Global Positioning Satellites to set its own time and how technology changes rapidly over the years, the PN-Series GPS will unfortunately no longer display the current correct time. We sincerely apologize for this inconvenience. At this point; due to the number of improvements and the plethora of additional features and functions, we would recommend upgrading to a newer Garmin Handheld GPS. Please review the links below for some models comparable to your older DeLorme PN-Series GPS. InReach Explorer + – Maps with premium satellite communications. https://buy.garmin.com/en-US/US/p/561269/pn/010-01735-10# GPSMap 66S – Premium rugged (MIL-STD-810G) handheld GPS. https://buy.garmin.com/en-US/US/p/598408/pn/010-01918-10#overview Instinct (It’s MORE than just a watch!…and as a wearable…it can always be on you…surf, hike, train and work…it’s the ultimate tool for its price point) https://buy.garmin.com/en-US/US/p/621802 Again, I apologize for the issue with your PN-Series GPS and hope with the overabundance of high-end rugged GPS devices Garmin provides, something will fulfill your navigation needs. Your older inReach does not need to Sync. Those older devices only did a Sync to update firmware and you have the latest for that older device. Please let us know if you have additional questions or concerns. Regards, Kurt Ringrose Product Support, Garmin Outdoor (inReach) Garmin International http://support.garmin.com The GPSMap 66S will be available in 5-8 weeks and costs $449.99. The inReach Explorer + costs $449.99. It will cost me $900.00 + shipping to duplicate what I have now. CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be Garmin confidential and/or Garmin legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication (including attachments) by someone other than the intended recipient is prohibited. Thank you.

I have the same issue on my PN-60w. I noticed it when I downloaded my recent tracks which are defined by date they are all the same date such as 1999-03-10, XXXXXX.gpx. With Field Notes I use a text editor to correct the dates prior to downloading because Geocache will not recognize old dated Notes. I went to Garmin's "Migrating from old Delorme Forum" looking for an answer but none posted. Of more concern to me is how will the affect my inReach messages. I have the older model transceiver paired to my PN. Sent a message to myself and it wasn't received. Garmin.inreach could not help with legacy inReach and recommended sending a email to support@delorme.com which I did. Now I wait.

Try copying the coordinates as you usually do, then paste them to a text editor like Notepad. When I do this I get two blank lines, which are actually two CR LF (carriage return, line feed) characters, prior to the actual coordinates, but I don't know why it happens. One way around this is to click the pencil symbol next to the coordinates and copy the original coordinates.

Adding newly published caches happens quite often for me. I run a PQ overnight then I check for new caches prior to leaving. I want the new caches to be in context with the original PQ’s area that I intended to visit, which is the purpose of the PN-XX’s file system, i.e., to keep things organized for easy retrieval and display. By putting newly published caches in differently named files defeats that purpose. I realize the OP doesn’t want to run PQ’s, but with the loss of “Send to my GPS” capabilities, using “GPX file” will create individual files in the PN-XX and cause more confusion in the long run.

The way I get around the “send to GPS” issue is I have several identical pocket queries for the same area using the same query name for them. Here is how I do it. First, make sure the “Include Pocket Query Name” is checked in the Pocket Query form then make two identical queries with the same title but with the leading number in one query being even and the other odd. So, for instance, one query’s title may be called “XXXXXX1-HomeTown” and the other “XXXXXX2-HomeTown” (Groundspeak controls the numbers so it may take several tries to get an odd/even combo). For normal operations run the odd number query then remove the number from the title leaving just “HomeTown” prior to drag & dropping it into the PN-XX unit. Now, if there is a need to run a second query, run the even numbered one. There will be no 24 hour delay. As before, remove the number from the newest query’s title and drag & drop. It will replace the previous query in the unit. I, in fact, have four (two odd, two even) “HomeTown” queries ready to go just in case one of Groundspeak’s servers goes down. I have no intentions of throwing away a perfectly good GPSr that has served me well for so many years as long as I can adapt.

It’s a Javascript issue in Firefox. You can disable Javascript then the scroll bar is made wider and it will function properly but the map will not display. Isn’t that just great! If you want to try it, while in Firefox, type ‘About:Config’ (use a colon not a dot) and you will get a warning message. Click ok. Next type ‘Javascript:enabled’ and click it to disable. Reload Geocache.com and look at the map page again. Now the scroll bar works properly. Repeat the above to restore Javascript and live with it.

My computer (Lenovo Yoga 14) does the same thing. The map page does not respond to the scroll wheel or Click & Drag on the scroll bar, but it does scroll when using the touch screen.

Load Topo10 onto your new laptop from the discs. All your tracks, projects, downloads, etc. can be transferred from your old computer’s main drive to the new computer. They are located here: Windows(C:) > Delorme Docs.

This is an interesting site: https://ngmdb.usgs.gov/topoview/viewer/#7/41.968/-75.449 It is also handy for historical references.

In England the phase often heard is “Nettle in, Dock out.” The sting in Stinging Nettle is caused by formic acid (same as in ants). Curled Dock (Rumex Crispus) usually grows in the same area as the nettles. Just crush and rub the Curled Dock leaves on the affected area for quick relief.

Suspect the cable because the cable’s plugs are designed to fail before the device’s USB receptacles. The Nuvi 54LM uses a standard cable with Mini B to Type A plugs. You should be able to troubleshoot the problem. · If you have another device that uses a similar cable you can try the ‘suspected’ cable on that device, or use the other device’s cable on the Nuvi. · If you have a multi-meter you can check the continuity between the plug’s contacts. Google ‘USB Connectors’ to understand which pins to test. Over flexing or poor strain relief at the plug-wire interface can cause the internal wires (+5vdc, Data -, Data+, GND) to break. Usually the cable is at fault, but new third party replacement cables are cheap and plentiful. If the Nuvi’s receptacle is at fault then you can try repairing (soldering usually required) the receptacle, else buy a new unit.

What version of Topo North America do you have? TNA 9.0 works on Windows 10.

Did you try a NVM reset? After removing the batteries press and hold the 'Start' button for about 10 seconds. Replace the batteries (be careful of the polarity!). Make sure the battery contacts are secure, they are known to get bent over time, then try one of the following procedures. Trouble acquiring a satellite fix or the device is resetting while viewing the satellite page 1.Turn the Earthmate PN-Series GPS off. 2.Hold down the PAGE, MENU and Power buttons. 3.Once you see the dark blue Warning screen, release the Power, PAGE and MENU buttons. 4.Press ENTER. 5.Scroll to System and press ENTER. 6.Scroll to NVM reset and press ENTER. 7.Scroll to Yes and press ENTER. Note: If using a PN-60 or PN-60w, press ENTER when 'Operation Successfully Completed' appears. 8.Press the QUIT button. 9.Scroll to Reboot and press ENTER. 10.Give the device a full ten minutes to download the latest satellite constellation information and to acquire a 3D fix. Troubleshooting poor or incorrect electronic compass readings Only the Earthmate GPS PN-40, PN-60, and PN-60w devices have an electronic compass. PN-20 and PN-30 devices will not have the ability to debug a compass. 1.Turn the Earthmate PN-Series GPS off. 2.Hold down the PAGE, MENU and Power buttons. 3.Once you see the dark blue Warning screen, release the Power, PAGE and MENU buttons. 4.Press ENTER. 5.Scroll to Test and press ENTER. 6.Scroll to Debug Compass and press ENTER. 7.Set the device on a level, non-magnetic surface and press ENTER. 8.After 10 seconds, press the MENU button. 9.After 10 seconds, press the PAGE button. 10.After 10 seconds, press the QUIT button twice. 11.Scroll to Reboot and press ENTER. 12.Calibrate the electronic compass and test the unit. Reformatting the Earthmate PN-Series GPS Device (Last Resort!) If the GPS has an issue unresolved by the steps above and the latest firmware has already been installed, a reformat of the device could correct the issue. Performing this reset will delete all data and maps installed to the internal memory of the device. Back up any of this data you are interested in saving! 1.Turn the Earthmate PN-Series GPS off. 2.Hold down the PAGE, MENU and Power buttons. 3.Once you see the dark blue Warning screen, release the Power, PAGE and MENU buttons. 4.Press ENTER. 5.Scroll to Media and press ENTER. 6.Scroll to Low-level Internal Reformat... and press ENTER. 7.Scroll to Yes and press ENTER Note: If using a PN-60 or PN-60w, press ENTER when 'Operation Successfully Completed' appears. 8.Press the QUIT button. 9.Scroll to Reboot and press ENTER. 10.Install the latest version of the firmware.

Yes it’s been working without an issue for many years, not one pin failure. It isn’t that difficult if you have a little soldering skill. It’s a matter of carefully removing the back cover, removing the old potting compound and old pins, replacing with new pins, re-solder the wires, replace the cover and fill with epoxy. I have step-by-step write-up. If you would like a copy let me know. In any case I would start with the re-charging cable first, it only has two wires as shown below. The two main failure points are the pins, they have poor range of motion, and the wire connection, the wires fatigue and break. Using the newer pins and applying the shrink tube solves these issues.

A little off topic but about six years ago I had a similar problem with my cables, mainly the pins made poor contact. I found new, larger pins with a longer stroke and replaced them on the USB and Recharging cables. I haven't had any issues since.

I’ve learned from years of sailing that anything near the water will eventually end up in the water. I tether everything from eyeglasses to binoculars (and even myself at night) when at sea. I apply the same reasoning to my GPSr where I use an old boot lace threaded through the GPSr and a lanyard breakaway connector (repurposed from a lanyard received at the last Geobash event I attended) to prevent choking hazards. Using a carabiner attached directly to a GPSr with a built in compass may cause deviation errors due to the steel spring. All my shirts have breast pockets large enough to hold the GPSr but my body blocks half the sky and attenuates signal acquisition. I only hold the GPSr when on final approach to a waypoint where accuracy is important. Once there, back into the pocket it goes. The only problem with this technique is I have no excuses to buy a newer unit.

If your GPSr has a barometer and you are at a constant elevation (e.g. on the water or at camp) then you can get an indication using the 345 rule-of-thumb, i.e., 4 or 5 millibar drop in pressure over 3 hours indicates approaching foul weather, and any drop greater than 5 mb / 3 hrs indicates the severity of the approaching storm. A rising pressure indicates fair weather approaching, and a rise greater the 5 mb / 3 hrs expect windy but fair conditions.

Is it really about the money or is it, as B.B. King would say, "The Thrill is Gone"?

A word of advice I received from a local while caching in Iceland. “If you ever find yourself lost in the woods in Iceland just stand up.”

Have your tried this site? Use "#11-Intersection point of three circles".

Quite interesting. Many years ago I was taught to perform cause and effect analyses by using the two basket methodology. Using this approach, I put all similarly defined variables in one basket and all others, in the second basket. Applying that here, I assume two baskets, one of error sources internal to a subject GPSr, and the second basket contains all others (in this case this would be error sources external to a GPSr. Specifically: Basket of Internal Sources: I assume that the source of the Receiver Noise error is internal to the GPSr, and Basket of External Sources: I consequently assume that the other error sources listed are external the the GPSr. After reading your post I had a thought. Because I feel it is impossible to quantify accuracy (because of the user variable), perhaps a comparison is the only reasonable method. A test that negates as many uncontrollable variables as possible would test just the units themselves. If two different GPSrs that have been correctly setup, are placed on the ground, with open access to the sky and oriented to maximize their antenna radiation patterns, i.e. helical-vertical and patch-horizontal, most uncontrollable variables would cancel out including with the biggest potential variable HDOP. It would measure only how well they deal with multi-paths receptions and effects of the receiver. If left to run for fifteen minutes at a sample rate of five seconds, 180 track lines would be displayed. The “birds nest” of lines and EPE would visually indicate the precision of each unit under similar conditions. A more detailed analysis would require the data to be downloaded to a spread sheet, the mean determined (RMS), standard deviation, and the variance from the mean at the 2-sigma (95%) level for each data set. The results would indicate which unit performed best. Just a thought, I can’t afford two GPSrs.

Which is why I said "generally, less is better" I have no information from ANY handheld consumer GPSr manufacturer that the 95% actually applies to their particular algorithm on a particular model or even firmware level. That's the problem. Two teams can take exactly the same information and depending upon their own preferences and experience and 'suggestions' from the marketing department, arrive at a different set of numbers. So it remains a somewhat useful relative measure and that's about all. I would imagine that some 'estimates' are better than others. As to "signal bounce", there are claims by some chip manufacturers that they manage multipath issues better than the competition, but it would be nice to see a white paper that defends those claims by drawing hard comparisons between the performance of different chips using some of the different algorithms (I've seen at least half a dozen different approaches explained). We'd be smarter for it, I think. Probably out there somewhere in someone's desk drawer. You are correct, I don’t know if a 95% confidence level is used by all manufacturers and who knows what evil lurks in the heart of marketing personnel (assuming they have a heart). However a 2-Sigma span gives a good representative sample of the dataset. A normally distributed curve depends on the data set from which a standard deviation unit can be derived. A 1-sigma (68% or one standard deviation) sample would produce a very small error circle because of the narrow span near the top of the curve. Also, a 3-sigma (99.7%) would make a huge error circle and it would include outliers that really should be filtered out. Therefore, 2-Sigma (95%) seems appropriate.