LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

time stamp bug

The UTC would not change the time by 1 second..

(should not change it by 1 sec)



Message Edited by JoeLabView on 07-03-2008 08:30 AM
0 Kudos
Message 11 of 17
(1,395 Views)

My problem is related to the time stamp indicator/control

Please note that 00:10:00,0000 (and many other time combinations around 1970) also do not work Smiley Sad

0 Kudos
Message 12 of 17
(1,379 Views)
I don't have the full answer but Unix started counting time 1-1-1970 00h00 (GMT).

I think there are computational problems around that time.

Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 13 of 17
(1,367 Views)
I tested the VI above and had the same problem as well. GMT +2 here. Running LV 8.5.1 and Vista 64bit.
0 Kudos
Message 14 of 17
(1,364 Views)
Remember the CPU bug with some of the first Pentiums (75MHz?)
 
It does seem like a computational error.  Have you tried it on another PC?  One that has a different hardware?
 
R
0 Kudos
Message 15 of 17
(1,353 Views)
I think thins one is a LabView error....
 
I have personally tried in on three separate machines (2 with XP + 1 with vista) and at least two other users from around the world have verified the error...
 
By the way, look at the Y2K38 bug (http://en.wikipedia.org/wiki/Year_2038_problem) - seems like LabVIEW suffers from the Y2K70 bug as the clock used on linux starts at 1st Jan 2007 and stops at Jan 19th 2038 (for what I can see 2038 seems OK on LabVIEW).  My problem is I need to synchronise a linux database (UTC time staring 1970-01-01) with LabVIEW (UTC time starting in 1904-01-01).
 
We had a another theory - Does anyone know how LabVIEW handles leap seconds with regards to UTC time (http://en.wikipedia.org/wiki/Leap_seconds)?  Seems like there are a bunch of seconds that simply dissapear from the UTC clock every so often!
0 Kudos
Message 16 of 17
(1,327 Views)

I just came across this bug as well, dates around 1970-01-01 seem problematic. I cannot set the time to 00:00:00 on that day.

 

Additionally, it seems 'labview epoch' at 1904-01-01 also is problematic. When I set the timestamp to 00:00:00 1904-01-01, the timestamp returns -3600. If I set it to 01:00:00, the timestamp widget resets itself (while the value returned should be 0). I suspect these issues are related.

 

Summarizing theseissues:

 

1) Set timestamp date to 1970-01-01 00:00:00

2) Input is ignored and set the date/time to 1970-01-01 01:00:00

3) I expect it to return the date/time I entered

 

1) Set timestamp to 1904-01-01 00:00:00

2) Timestamp returns -3600

3) I expect it to return 0

 

1) Set timestamp to 1904-01-01 01:00:00

2) Timestamp resets itself (i.e. 00:00:00 YYYY-MM-DD)

3) I would expect it to return 3600

 

System used: LabVIEW 2009 SP1, Windows 7 64bit

0 Kudos
Message 17 of 17
(1,070 Views)