Leaderboard

Hate to burst your bubble, but Darren included a little nugget: <vi.lib>\Utility\High Resolution Relative Seconds.vi I know it's there in 2011 and 2012.

If you click "More Reply Options" on this page, it will take you to the full post editor, which has a panel for uploading attachments. I took a peek at your VI - it does depend on the lvsound2 library. As I mentioned before, my workaround was not elegant; I just multiplied my acquisition duration by a constant to get the right output duration. Do me a favor and report this to NI (http://www.ni.com/support) so they know someone else is running into this problem.

Job Posting We are looking for another LabVIEW developer to join our team near Los Angeles. Here's the short version: We build rockets and spacecraft. We deliver cargo to the International Space Station and we have a contract to demo manned launches. Our goal is people on Mars. Our group writes the software to control the launch pad and rocket before liftoff. We also write the software that commands and monitors our spacecraft in orbit. We use LabVIEW as a general programming language. Our PXI/DAQ components are a small, but mission critical part of the equation. Large application development, object-oriented design, 100+ computers networked across the globe. It's pretty damn cool. Some legalese: To conform to U.S. Government space technology export regulations, applicant must be a U.S. citizen, lawful permanent resident of the U.S., protected individual as defined by 8 U.S.C. 1324b(a)(3), or eligible to obtain the required authorizations from the U.S. Department of State

When I have a file that I would prefer not be deleted by the user (templates, default config, etc.) I usually place the contents inside a string constant inside the program and recreate it that way. One fewer file hanging around, and no chance of a user "accidentally" deleting (or modifying) it. Other than that I agree with Neil: Explicitly bundle. Remember they are called "TYPE"-definitions, they are intended to define type and not value. It is tempting, very tempting, in fact very, very tempting to use those constants to hold values. Works great if the TD never changes, but a TD which never changes, well that is really just a plain old constant.

Late Friday night and almost in sleep mode... AQ said that to really reach out to all customers we really need to give our code to NI, but since LV 2011 we have the LabVIEW Tools Network built in to LabVIEW and this enables each and every user to easily install features they need (from OpenG, LAVA or LVTN). LVTN has no restrictions for licensing that I know of, but NI still reviews and put code under the NI umbrella and even publish some code of their own. I currently know nothing about JSON, but from reading through the threads here at LAVA it is probably something I will look into in the future. And when I do, I like to be able to select the implementation that I want to use; NI version, LAVA version or any other version. Installing these from LVTN/VIPM mean that new features/versions are available to me directly and I don't have to wait until the next LabVIEW release. Bugs detected in LVTN modules are also likely to be fixed much faster since the fix can be released regardless of the LabVIEW release cycle. /J