Jump to content

Phillip Brooks

Members
  • Posts

    911
  • Joined

  • Last visited

  • Days Won

    53

Posts posted by Phillip Brooks

  1. 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.

    • Like 2
  2. I agree. NI has some of the best product support I've seen. But getting to talk to the right people, or convincing the right people you know what you're doing, can make the support you get very different.

    I had a memory leak issue when using user events on real time. The issue turned out to be my fault, but I called NI looking for assistance before I knew that. After I explained what I was doing to the first guy I talked to, he told me user events were not allowed on real time. It was at that point I knew I was not talking to the right person.

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

    tech_support.png

    • Like 2
  3. I'm very disappointed you didn't say "%^<%Y-%m-%dT%H:%M:%S%3uZ>T" :rolleyes:

    /J

    Well, the original question was "What are the most common date formatters?" not the most useful date formatter. :P

    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...

    • Like 1
  4. 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

  5. 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

  6. Go a step farther, and make the VI broken. One easy way is to make one input "Required" -- then you can "turn off" the compiler error by creating a constant on that input. This forces yourself to go back and fix it, ensuring you can't forget and, say, make a build without the fix.

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

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.