crelf

Absolutely! You see some of our solutions all the time - but I can't tell you that they're ours

You don't watch Mythbusters?!?! We've done a bunch of high-visibility LabVIEW applications, but we can't talk about them

Update: Have been using InnoSetup for a while now, and love it! It's got most of the features that I want, and those it doesn't I have been able to work around. InnoIDE, on the other hand, is pretty buggy - I'm using it, but mostly for the syntax highlighting of my innoscripts. Thanks everyone

tru dat. You should be able to see a list of members by reputation on the right of the main LAVA page (unless you've minimized it).

I don't think I've ever worked with a thermocouple that has a response that fast - the thermocouple itself has always been the limiting temporal factor...

When we want to put together a QSM, we use an internal reuse package that uses a string-based queue. Having it in a reuse package allows us to include other features, like state transition logging. It's currently passing around a dqGOOP reference, so we can use it in producer/consumer architectures, although I guess we could update that to a DVR-wrapped LVOOP class someday, but we haven't seen the need to.

BSD everything

Added.

For those who follow our twitter feed (and if you don't, you should1), we're making a small change to the content that we're going to post. In the past, the feed has been a mash-up of all things LabVIEW, but now that @vishots is online, we're going to limit the @lavag feed to link only to content on lavag.org. What does this mean in practice? If you're looking for a feed that lists hot topics and advanced threads, as well as admin info about lavag.org's health, then continue to follow @lavag. Also, if you want something to go out on the @lavag feed then it needs to link back to a post on lavag.org (eg: if you have a new idea in the NI Idea Exchange, post about it here at lavag.org too, and we'll pick it up from there - feel free to send us a twitter DM if there's something you think we should tweet). If you also want to know about all things LabVIEW (new releases, training, cool apps, etc) that aren't on lavag.org then follow @vishots too - it's run by our very own founder Mike, and is chocked-full of LabVIEW goodness. Why are we doing this? To avoid duplication. We're concentrating @lavag on lavag.org content so we don't cross the streams with @vishots. We expect that everyone will follow both feeds, and it gets annoying when you often see duplicate posts coming in from both feeds (it's like that joke someone emailed to you years ago that now everyone in your family emails to you again as they discover the internet). In summary, for the richest online LabVIEW experience follow @lavag and @vishots. There's also a list of other resources that you might be interested in here. ---------- 1 Relf, C. G. et al, "LAVA - LabVIEW Advanced Virtual Architects", 09 February 2010, Forum | Site News | Don't forget to follow @lavag on Twitter ( http://lavag.org/topic/11901-dont-forget-to-follow-lavag-on-twitter/ )

Error 13 (you can find error code descriptions under Help > Explain Error, or by right-clicking on an error cluster code and choosing "Explain Error") means: It fails when you run it, or is the run arrow broken?

I'm not so sure about the secutiry clearance, unless you want to actively pursue work within an organization that requires it - I assume you already have the most often required clearance: ITAR. Also, as Ben said, security clearance isn't easy to get - and you'd need to convince your current comapny that you need it to execute your job. I'd take a good strong look at TestStand and PXI. ...and, since your profile lists your LabVIEW version as 8.6, I'd start playing around with the latest version.

Don't power the motor directly from the USB box - control a relay with it. ie: turn the coil of a realy on and off with the USB box, and then wire the motor with its own power supply to the NO (normally open) contacts of the relay. Now, when you make the digital oputput of the USB box go high, the contacts on the realy will close (just like a switch) and the motor will turn on.

Rather than write it yourself, you could use the Blue Ridge Test Biometric Login Toolkit.