From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Home Community Idea Exchange TestStand Ideas Idea

NI TestStand Idea Exchange

Top Authors
View All
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
PhillipBrooks

Add a native DateTime data type to the TestStand Engine

Submitted by Active Participant on ‎07-06-2010 10:51 AM 3 Comments (3 New)
Status: New

See this post

 

Testing date / time values (Specifically from .NET)

 

 

 

Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.

"You are what you don't automate"
Inplaceness is synonymous with insidiousness
Labels:
3 Comments
Jean-Louis
Member
Member
‎08-04-2011 11:21 AM
‎08-04-2011 11:21 AM

This DateTime type should be equivalent to LabVIEW Timestamp.

 

Until now, LabVIEW Timestamp is considered as a string in TestStand which includes date and time formatting, depending on regional options.

Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 - 2022)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)

0 Kudos
PhillipBrooks
Active Participant
Active Participant
‎05-09-2012 09:28 PM
‎05-09-2012 09:28 PM
How I feel about working with date time stamps between LV and TS http://forums.ni.com/t5/BreakPoint/There-s-One-In-Every-Crowd/m-p/1698598#M16552
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.

"You are what you don't automate"
Inplaceness is synonymous with insidiousness
0 Kudos
LVB
Active Participant
Active Participant
‎09-17-2012 05:41 PM
‎09-17-2012 05:41 PM

It would be nice to have a universal Timestamp type in TestStand.  This is definitely something that is over-complicated.

 

Since LabVIEW and TestStand are both NI products, my vote would be to have TestStand use the same format as LabVIEW.  Determining the time between a LabVIEW timestamp and TestStand step start time should be as easy as subtracting two variables.

CLA, CTA