+Timpat Posted March 2, 2008 Share Posted March 2, 2008 Today, March 1st, I was out caching and snowshoeing with my 300. I turned the 300 on, and as usual the time displayed was from the last time I had it on with a fix, the day before. Since the clock does not keep time between sessions, every time, I thought not much of it. Is this clock issue still a problem? And can it be fixed with a firmware update? I've looked for the topic on the clock issue and can't seem to find anything on it. The 300 got a good fix with WAAS corrections so off I went on my 4 mi hike in the forest. It performed perfectly for the entire outing. The Eneloop AAs even held up very well in the cold using minimal backlighting, WAAS, no compass. I have 2.40. Here's the strange part. Upon returning home and downloading my tracklog of my hike from the Current.gpx file, the time stamp and date was Feb 28th, not March 1st. Now why would it record that date? Since if goofed up, why not the previous date of Feb 29th? Did Leap Day flip it out? It seems to have realized what day it is now. Quote Link to comment
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.