+Henne1312 Posted March 9, 2022 Share Posted March 9, 2022 Hi, I had a problem with my 66s (FW 9.90) last week, that pc-mueller had as well: Startet a Multi, got the coordinates of stage 2, entered them, GPSr showed the new coordinates, and I went to stage 2. At stage 2, found and entered the coordinates for stage 3, but the GPSmap didnt't show these coordinates, it showed the listed coordinates instead. Tried several times, but everytime I entered the coordinates of stage 3, the 66s changed them to the listed coordinates. I couldn't find this issue on GPSrchive, or maybe I missed it. Has anyone else ever had this problem with the 66s or any other Garmin GPSr or is this a known issue of FW 9.90 and 9.60? pc-mueller downgraded to FW 7.60, and it works now. But downgrading the FW isn't really what I wanna do, maybe there's another solution. Thank you! Quote Link to comment
+Atlas Cached Posted March 11, 2022 Share Posted March 11, 2022 On 3/9/2022 at 12:20 PM, Henne1312 said: Has anyone else ever had this problem with the 66s or any other Garmin GPSr The Montana 7x0 has a similar issue (Common Issues - Bug 98), and they do all share some common code, so I am not surprised to hear that you are experiencing this behavior on the GPSMAP 66. Quote Link to comment
+Henne1312 Posted March 13, 2022 Author Share Posted March 13, 2022 Thanks for your answer! Didn’t know the Montana had a similar issue, but found out the Oregon 600 had this issue years ago and it has been resolved (bug no. 65). So it’s a comeback… Quote Link to comment
+Atlas Cached Posted March 14, 2022 Share Posted March 14, 2022 On 3/13/2022 at 4:28 AM, Henne1312 said: So it’s a comeback… ...or a FlashBack! Quote Link to comment
+geoidhn Posted February 5 Share Posted February 5 I know this an old thread but I think I have somehow pin-pointed this problematic behaviour. As far I see it happens after when one downloads coordinates from geocaching.com. After that the coordinates don't update at all. BUT if I reboot the GPSr the coordinate changes work again. At least so far I have always been able to heal (or rather bu-pass) the problem by restarting the unit. h Quote Link to comment
+Atlas Cached Posted February 6 Share Posted February 6 16 hours ago, geoidhn said: I know this an old thread but I think I have somehow pin-pointed this problematic behaviour. An old thread for an issue that was resolved with Firmware version 10.10, released 01JUN22. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.