Phillip Brooks

Just found this while waiting for a test to run (had some spare time to read about time) http://infiniteundo.com/post/25326999628/falsehoods-programmers-believe-about-time

http://forums.ni.com/t5/LabVIEW/New-LV2010-VI-High-Resolution-Relative-Seconds/td-p/1213011

:shudder: Do I hit the Like This button, or not?

Keep in mind that the implementations so far all read the complete file into memory then decode. Not an issue for a few hundred KB or even MB, but If you try to do this with really big files and then combine these in RAM for writing to disk as a single file then you may run into problems.

Pimping my ideas... http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Add-Block-Diagram-design-for-typedefs/idi-p/940093

You didn't use the correct secret code word...

Another date/time related Idea Exchange entry: Time Stamp Properties Dialog - Persist the selected container type (Absolute or Relative Time) http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Time-Stamp-Properties-Dialog-Persist-the-selected-container-type/idi-p/2180840

Well, the original question was "What are the most common date formatters?" not the most useful date formatter. Maybe someone else here could chime in regarding Oracle, but I just spent the last three hours querying and dumping results using Oracle Apps and the date/time format was: 09-OCT-2012 08:59:28 which works out to %<%d-%b-%Y %H:%M:%S>T except for the capitalization. I'm guessing that the month name is localized to the default language setting for the profile of the user...

As a U.S. LabVIEW for Windows user, I most often see people use the the Format Date/Time String function with no input for default string (default is %c or locale specific). The Default locale info on Windows with a setting of English (United States) looks like this: 10/5/2012 1:10:42 PM The equivalent LabVIEW string would be %<%m/%d/%Y %I:%M:%S %p>T In LabVIEW 8.6, the string I provided always includes two digits for the day, month and hours, yet the default output Format Date/Time String with the default %c returns two digits only when > 9. 10/5/2012 1:10:42 PM 10/05/2012 01:10:42 PM

Have you seen this post on the NI forums? High Resolution Relative Seconds It was reported as having an open loop resolution of ~ 1.2u sec W/R/T resolution of a timestamp, this is documented here: http://www.ni.com/white-paper/7900/en You might try typcasting the timestamps as arrays of U64 and then performing addition and subtraction on those. After performing the integer operations, the U64 that represents the fractional seconds can be converted back by multiplying it by 2-64 http://forums.ni.com/t5/LabVIEW/Unable-to-replicate-frations-of-seconds-when-reading-a-timestamp/m-p/2116706#M687792

Or maybe a required output? Don't know if this is still possible...

Add a native DateTime data type to the TestStand Engine http://forums.ni.com/t5/NI-TestStand-Idea-Exchange/Add-a-native-DateTime-data-type-to-the-TestStand-Engine/idi-p/1171261 How I feel about it... http://forums.ni.com/t5/BreakPoint/There-s-One-In-Every-Crowd/m-p/1698598#M16552

If you use Chrome, I've installed this extension and it seems to work pretty good. https://chrome.google.com/webstore/detail/limjcpdphjbhdldhiahblmfadfaciaok It replaces the shortened link with the original URL. This is displayed in the lower left of the browser window, out you can right-click copy and paste to the URL field.

Maybe someone who is connected on LinkedIn with Brian Tyler could share this discussion with him and ask if the terminals had a purpose...

Not mine, but an excellent one. Make units work all the way or skip them! http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Make-units-work-all-the-way-or-skip-them/idi-p/1803510

TCP/IP is not a serial interface. It does not use the same flow control standards.

What would stop a user from setting the computer's date/time to say, October 21, 2015 and then opening the VI? (I gotta get me a hover board!)

It's in my profile. We have so much code and libraries that we don't upgrade very often. The last upgrade happened when we went from 7.0 to 8.6 in December of 2008. I try to participate in the betas and keep up on things, but I'm falling behind the times. I did download 2012 today, but won't do much with it until the end of the year. We might start our next project on 2012, the latest TestStand and win7

Anyone have any opinion on the tool bar changes? I've been running LV 8.6 so I can't recall if the change happened in 2009,10 or 11 but the color change (yellow and green to yellow and cyan) along with sort of a 'flat look' is almost a bit too retro for my taste.

Be careful about error clusters that do nothing. I updated some low-level internal libraries a couple of years ago and had a bunch of developers get mad at me. Basically, if you do add the error in / error out terminals to your connector pane for 'future use', make sure you place an Always Copy node on the Error wire or any caller could require a recompile if you make changes...