Page 2 of 2   << first < 1 2
Bookmark this page: Add Did something roll over on about Aug 19th   to Yahoo MyWeb Add Did something roll over on about Aug 19th   to Google Bookmarks Add Did something roll over on about Aug 19th   to Windows Live Add Did something roll over on about Aug 19th   to Del.icio.us Digg Did something roll over on about Aug 19th  ! Add Did something roll over on about Aug 19th   to Netscape
  •  
  • Subject
  • Author
  • Date
If you were  Registered and logged in, you could reply and use other advanced thread options
Posted by Sam Wormley on August 29, 2010, 11:50 pm


On 8/29/10 10:27 AM, spam_from_google@chezphil.org wrote:
> Hi Everyone,
> My Sony GPS-CS1 has been misbehaving since Aug 19th. Since then it
> has been recording dates in April 2030. It looks as if it is adding
> 0x1c00 days to the dates that it is recording.
> Is anyone aware of some sort of roll-over in the GPS date format that
> could have triggered this?
> Is there anyone else with this device (or another device - I bet that
> a lot of the code is shared) who has seen the same problem?
> Many thanks, Phil.

Similar situation for me a couple of years ago with my Trimble
Scoutmaster. This PDF file from Trimble was applicable.
http://trl.trimble.com/dscgi/ds.py/Get/File-322744/MGIS_SprtNote_GeoExplorerI&II_IncorrectDate.pdf



Posted by Sam Wormley on August 29, 2010, 11:52 pm


On 8/29/10 10:50 PM, Sam Wormley wrote:
> On 8/29/10 10:27 AM, spam_from_google@chezphil.org wrote:
>> Hi Everyone,
>> My Sony GPS-CS1 has been misbehaving since Aug 19th. Since then it
>> has been recording dates in April 2030. It looks as if it is adding
>> 0x1c00 days to the dates that it is recording.
>> Is anyone aware of some sort of roll-over in the GPS date format that
>> could have triggered this?
>> Is there anyone else with this device (or another device - I bet that
>> a lot of the code is shared) who has seen the same problem?
>> Many thanks, Phil.
> Similar situation for me a couple of years ago with my Trimble
> Scoutmaster. This PDF file from Trimble was applicable.
>
http://trl.trimble.com/dscgi/ds.py/Get/File-322744/MGIS_SprtNote_GeoExplorerI&II_IncorrectDate.pdf

Four years ago next month--My error.


Posted by Ed M. on August 30, 2010, 10:54 am


> On 8/29/10 10:50 PM, Sam Wormley wrote:
> > On 8/29/10 10:27 AM, spam_from_goo...@chezphil.org wrote:
> >> Hi Everyone,
> >> My Sony GPS-CS1 has been misbehaving since Aug 19th. Since then it
> >> has been recording dates in April 2030. It looks as if it is adding
> >> 0x1c00 days to the dates that it is recording.
> >> Is anyone aware of some sort of roll-over in the GPS date format that
> >> could have triggered this?
> >> Is there anyone else with this device (or another device - I bet that
> >> a lot of the code is shared) who has seen the same problem?
> >> Many thanks, Phil.
> > Similar situation for me a couple of years ago with my Trimble
> > Scoutmaster. This PDF file from Trimble was applicable.
> >http://trl.trimble.com/dscgi/ds.py/Get/File-322744/MGIS_SprtNote_GeoE ...
> =A0 =A0Four years ago next month--My error.

Sounds like Dogbert was manning the support desk when they wrote that:

"Solution - Ignore the displayed date"

For the Sony set, looks like the problem may be more of show-stopper.

http://www.docs.sony.com/release/GPSCS1_position-addendum.pdf

Apparently the camera's clock is used to apply a date/time to each
photo, while GPS date/time is recorded on the CS-1 memory stick along
with position. Afterward the software correlates the two dates/times
to match the stored position with a picture.

Manual has notes about resetting time zone info, etc.

So with a 19+ year offset, there may be no way to match the positions
and pictures using the software.

At least the wrong date isn't being inserted on the picture itself.



Posted by Wayne R. on August 30, 2010, 11:21 am


wrote (with clarity & insight):

>> On 8/29/10 10:50 PM, Sam Wormley wrote:
>> > On 8/29/10 10:27 AM, spam_from_goo...@chezphil.org wrote:
>> >> Hi Everyone,
>> >> My Sony GPS-CS1 has been misbehaving since Aug 19th. Since then it
>> >> has been recording dates in April 2030. It looks as if it is adding
>> >> 0x1c00 days to the dates that it is recording.
>> >> Is anyone aware of some sort of roll-over in the GPS date format that
>> >> could have triggered this?
>> >> Is there anyone else with this device (or another device - I bet that
>> >> a lot of the code is shared) who has seen the same problem?
>> >> Many thanks, Phil.
>> > Similar situation for me a couple of years ago with my Trimble
>> > Scoutmaster. This PDF file from Trimble was applicable.
>> >http://trl.trimble.com/dscgi/ds.py/Get/File-322744/MGIS_SprtNote_GeoE ...
>>    Four years ago next month--My error.
>Sounds like Dogbert was manning the support desk when they wrote that:
>"Solution - Ignore the displayed date"
>For the Sony set, looks like the problem may be more of show-stopper.
>http://www.docs.sony.com/release/GPSCS1_position-addendum.pdf
>Apparently the camera's clock is used to apply a date/time to each
>photo, while GPS date/time is recorded on the CS-1 memory stick along
>with position. Afterward the software correlates the two dates/times
>to match the stored position with a picture.
>Manual has notes about resetting time zone info, etc.
>So with a 19+ year offset, there may be no way to match the positions
>and pictures using the software.
>At least the wrong date isn't being inserted on the picture itself.

RoboGEO will accommodate a "camera offset" so you can manually sync
camera clock to GPS clock. It's in +/- seconds - no idea if it can
handle the offset you're talking about though.

With RoboGEO, any regular GPS with a tracklog is
usable/non-proprietary.

Posted by Sam Wormley on August 30, 2010, 11:26 am


On 8/30/10 9:54 AM, Ed M. wrote:
>> On 8/29/10 10:50 PM, Sam Wormley wrote:
>>> On 8/29/10 10:27 AM, spam_from_goo...@chezphil.org wrote:
>>>> Hi Everyone,
>>>> My Sony GPS-CS1 has been misbehaving since Aug 19th. Since then it
>>>> has been recording dates in April 2030. It looks as if it is adding
>>>> 0x1c00 days to the dates that it is recording.
>>>> Is anyone aware of some sort of roll-over in the GPS date format that
>>>> could have triggered this?
>>>> Is there anyone else with this device (or another device - I bet that
>>>> a lot of the code is shared) who has seen the same problem?
>>>> Many thanks, Phil.
>>> Similar situation for me a couple of years ago with my Trimble
>>> Scoutmaster. This PDF file from Trimble was applicable.
>>> http://trl.trimble.com/dscgi/ds.py/Get/File-322744/MGIS_SprtNote_GeoE ...
>> Four years ago next month--My error.
> Sounds like Dogbert was manning the support desk when they wrote that:
> "Solution - Ignore the displayed date"
> For the Sony set, looks like the problem may be more of show-stopper.
> http://www.docs.sony.com/release/GPSCS1_position-addendum.pdf
> Apparently the camera's clock is used to apply a date/time to each
> photo, while GPS date/time is recorded on the CS-1 memory stick along
> with position. Afterward the software correlates the two dates/times
> to match the stored position with a picture.
> Manual has notes about resetting time zone info, etc.
> So with a 19+ year offset, there may be no way to match the positions
> and pictures using the software.
> At least the wrong date isn't being inserted on the picture itself.

The crux of the problem is that there are no bits in the GPS
Navigation Message to indicate what rollover cycle is current.
Most products were not envisioned to be functioning over multiple
19+ year cycles.


Page 2 of 2   << first < 1 2