Logger Date Wrong

[F Rim]

I ran my GiSTEQ (CD-111) today and the log file did not show up in the software after the download, I found the file and loaded it into the software and the date was 12/31/2041. When I use the Syc to camera function the date showing was 2041. It has now changed to 2099.

Help.

[nutcase]

I have the CD-110BT and it thinks it's currently September 8, 2041. I'm hoping it's a sort of "one-time" (or "one-day") problem related the change of year and that everything will work itself out later. But it is annoying that no pictures taken today can be geocoded.

(My timezone is GMT-8, Pacific, for what it's worth).

[edit: PhotoTrackr time is also 1 hour later than local time; showed 09:30 when local time was 08:30]

[F Rim]

Thank you, I never gave it a thought that it was the last day of the year. Also didn't consider it wasn't my tracker. I guess wait and see is a good plan.

If you want to use the tracker change the camera date. Only my date has changes from 2041 to 2099.

[shaberer]

same problem here (actually all day), local timezone is GMT+1
Logger shows 09/08/2041 21:00
PC clock says 12/31/2007 20:00
Lets all hope this goes away tomorrow...

[Anacapa]

I have the same problem when I use "Sync Camera Time".
It reports the GPS Logger Time and Date as 09/08/2041 15:55:04
Correct date and time is 12/31/2007 14:55:04

A friend has the same problem.
He is using version 2.1, I am using version 1.5 of the program.

Any answers?

[VolkerS]

I'm having the same problem!! Wondering if this is indeed an issue due to the end of the year or a firmware problem? Has any one been able to get the right date and time after it read 9/8/2041 and +1 hour??

[nutcase]

Has any one been able to get the right date and time after it read 9/8/2041 and +1 hour??

Yes, and I'd bet it's back to "normal" for everyone now.

I had a reply from GiSTEQ support to take out the battery for an hour, put the battery back in, then take it outside and get a satellite fix. Unfortunately, I forgot to have it tell me the time once it got a fix so I don't know if the Trackr knew the right time but the log was wrong (meaning a software issue) or if the Trackr had the wrong time (meaning a firmware issue).

Seeing that it wasn't going to be too long before it would become 2008 in GMT (and playing a hunch), I went for little trip.

After I got home and loaded up the log file, here's what I found: at the instant GMT became 2008, the log file (viewed in PhotoTrackr) went from 9/8/2041 16:59:59 (2041 +1 hour) to 12/31/2007 16:00:00 (right date and time).

The only tools I've found to grab the raw log directly from the Trackr only run under Linux (and I don't have a spare drive around here to install Linux into). I kept the log on my Trackr for now in case someone can figure out how to grab the raw log under Windows.

[edit: Looking at the .GPS file that the PhotoTrackr program saved, the GMT times are right, but the date is wrong (i.e. it goes from 23:59:59 080941 to 00:00:00 010108). I suspect the reason that it showed up as +1 hour in the logs and "Camera Sync" is that September is still in "Daylight Saving Time" so, for me (for instance), 22:00 GMT is 15:00 PDT but 14:00 PST. The program, thinking it's September, does the "correct" conversion based on Daylight Saving Time and tells me it's an hour later than it is.

This seems to be a "boundary condition" problem somewhere, but I can't tell if it's software or firmware related. Did anyone have the Trackr speak the time after 12/31/07 00:00 local time but before 1/1/8 00:00 GMT? Did it tell you the right time or was it an hour off? If the Trackr spoke the right time, it would seem to be a software issue; if it spoke the wrong time, it's likely a firmware problem.

At least now I know that "all" I have to do to use the logs is cobble together a program to change the dates in the NMEA log and recalculate a checksum, and add the leading "---," that GiSTEQ adds to their .GPS files.]

[nutcase]

[edit: It seems a simple search/replace in the log files will fix the problem; replace 080941 with 311207 and you should be good to go. Just remember to make a backup copy before you edit the file, and be sure to save your updated as version as text-only. Also, make sure to work with the "most recent" version of the log; look for "_1" or something like that at the end of the filename.]

[VolkerS]

Definitely had to be a software problem as mine is reading the correct date and time this morning on the "Sync Camera Time". Doesn't appear to be firmware related as I had also called Tech. support also and they advised me to do the same routine of removing the battery for an hour and then getting a new sat fix and if that did work to reinstall the units firmware. Even with this the time and date was still wrong on the software however the unit was giving the correct time!! Guess a new software update is in order to correct this bug!! I'm just glad it's back to normal for now because I'm off for a 2 week vacation in Hawaii where I'll be putting this unit through it's paces!!

[nutcase]

I did a little sleuthing and it does, in fact, seem to be a firmware issue.

The raw log files show up with September 8, 2041 dates right up to the changeover at GMT 00:00:00.

I'll send my results to GiSTEQ, maybe they'll be interested.