LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

local time to us timezone

Also remember that LabVIEW routinely draws a distinction between what a value really is and the way it is displayed to the user. For example, integers can have different radixes, strings have a variety of formats, and timestamps can display 12 or 24 hour clocks -- all without changing the underlying data.

 

Mike.


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 11 of 20
(1,653 Views)

At this point it is a preferences thing, especially since the compiler will optomize away the constants, and addition, but I prefer a single constant, it takes up less space, and my brain is used to seeing times in the HH: MM: SS format.

 

 Example_VI_BD.png

Message 12 of 20
(1,651 Views)

Can you post the vi of this bro? 

0 Kudos
Message 13 of 20
(1,219 Views)

@Stem162 wrote:

Can you post the vi of this bro? 


Who are you related to in this thread?

 

If you are asking Hooovahh, I didn't know he was your brother.  His image is even enough to create from scratch.  And BONUS, it is a VI snippet which means you can save the image to your hard drive, then drag and drop that into your block diagram.

 

If someone else in this thread is your brother, than tell us who's VI you want.

Message 14 of 20
(1,213 Views)

De he already finished the vi? I just wanna know how he did it and whats the functions are used in creating that vi wherein he use minus and plus to change the timezone

0 Kudos
Message 15 of 20
(1,195 Views)

If you are referring to someone else let me know.  All my VI does is add a value to a time stamp.  This is the normal Add function on the functions palette.  I dropped down a double constant and right clicked it, then went to Properties then Display Format, and selected Relative Time, then changed to the HH:MM:SS format.

0 Kudos
Message 16 of 20
(1,183 Views)

Here's a general solution

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 17 of 20
(1,171 Views)

Tried this (I put "Now", from Zone -4 in DST), and when I specified Zone 0, Standard Time, I got 4 hours later (as expected).  But when I specified Zone 0, DST, I got really weird values (4:47 PM, 3/26/2018 became 5:47 AM, 10/24/2010).  LabVIEW 2016, 32-bit on 64-bit Windows 10.  Other Time Zones (than 0) seem to behave OK (didn't test exhaustively).  [I'm supposed to be unpacking house-hold items from many boxes, so I'm not going to poke around and try to figure this out right now ...].

 

Bob Schor

0 Kudos
Message 18 of 20
(1,168 Views)

@Bob_Schor wrote:

Tried this (I put "Now", from Zone -4 in DST), and when I specified Zone 0, Standard Time, I got 4 hours later (as expected).  But when I specified Zone 0, DST, I got really weird values (4:47 PM, 3/26/2018 became 5:47 AM, 10/24/2010).  LabVIEW 2016, 32-bit on 64-bit Windows 10.  Other Time Zones (than 0) seem to behave OK (didn't test exhaustively).  [I'm supposed to be unpacking house-hold items from many boxes, so I'm not going to poke around and try to figure this out right now ...].

 

Bob Schor


Fixed.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 19 of 20
(1,150 Views)

Thanks.  Sneaky how those Conversions can mess us up at times ...

 

Bob Schor

0 Kudos
Message 20 of 20
(1,145 Views)