WXforum.net
May 20, 2013, 07:28:55 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
Members: 6609  •  Posts: 178327  •  Topics: 18104
Please welcome TargY, our newest member.
Welcome to the the new hosting for WXforum.net.
 
   Home   Help Search Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: currdat.lst date format?  (Read 3291 times)
0 Members and 1 Guest are viewing this topic.
summers
Member
*
Offline Offline

Posts: 2



« on: January 06, 2010, 01:09:48 AM »

I am using a La Crosse 2810 and am trying to parse the currdat.lst file in a script.  It appears self-explanatory with the exception of the last_actualisation time value.  I had thought it was epoch time (seconds since 1 Jan 1970),. but when trying to convert it, it appears otherwise.  For instance, the current last_actualisation time is "3471746626".  In epoch time, that would be Saturday, 06 Jan 2080 06:03:46 when it should be Wednesday, 06 Jan 2010 06:03:46 which would be "1262757826".  This is a difference of 2208988800 seconds???  Currently I simply subtract the difference - but why?  What format is that?

Grrr! Please help!  Thanks.

- Summers
Logged
summers
Member
*
Offline Offline

Posts: 2



« Reply #1 on: January 06, 2010, 01:39:15 AM »

After looking at this off and on for a couple hours, I finally figured it out.  The time given is not epoch 1970, it is epoch 1900.  the 70 year difference is approx 2208988800 seconds.

Nothing to see here. Move along. Move along.

- summers
Logged
pschnell
Member
*
Offline Offline

Posts: 26



« Reply #2 on: April 06, 2010, 12:55:55 PM »

Hello,

After some research i have found the format of lct :

seconds from 1/1/1900 00:00:00 (GMT)
It's good for curdat.lst and also for date in file history.dat

Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.186 seconds with 19 queries.
anything