crelf

Why would you want to do that? Some of us are over-rated.

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

Citation please?

Added.

For those who follow our twitter feed (and if you don't, you should¹), 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.

----------

¹ 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:

Possible reason(s):

LabVIEW: File is not a resource file.

=========================

NI-488: Shareable board exclusively owned.

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.

You *could* write calibration routines in LabVIEW, but that doesn't mean you should MAX (Measurement and Automation eXplorer) has the built-in ISO-traceable calibration functionality that you're looking for.

1. How reliable is loading in tolerances using the loader?

Completely reliable.

2. Does the loader have to put into every sequence or can it be loaded once and propagate all sequences?

The property loader will load properties into variables that the sequence it is in can see. eg: if you have seqeunce locals and station globals, it'll populate them - it won't populate some other sequence's locals.

3. Is there a way of checking that the tolerances have been loaded?

Not quite sure what you mean by this. If you're asking "can you see the limits that it populates?", then the answer is yes.

Have you got a thermocouple and something that generates heat? You could put together a quick VI that keeps whatever at a particular temperature (turn on heater when thermocouple reads too low, turn it off when it reads too high). Add a graph, maybe control a fan too (it's on when the heater's off, it's off when the heater's on). For bonus points, add PID to tune the system.

Trying to beat a CAPTCHA?

Constants might only have a label if you've created one (ie: right-click, show label). I've had similar issues when trying to get a caption of a FP control that doesn't have one.

Corrupt inline image removed.

Image removed because LAVA did not like the extenstion.

That's because the NI Forums attachments don't have extensions

Here they are:

In my book the auto-tool helps someone that doesn't know what they need to do next (switch tools)...

I guess I don't know what to do next Actually, I disagree with your statement. If you put the mouse in the right place (like anything new, it takes some practise, and a steady hand sure helps) then it automatically switches to the next tool that *I* want. I know exactly what I want to do, auto-tool does it for me. I used to be a tab-key kinda guy - now all my left hand does on a normal day is space and delete.

...and the QD helps those that know exactly what they want to do faster.

I think in pictures, not words. I missed some questions in a certification exam once because I couldn't remember the names of a few primatives - I knew what they looked like, where they were on the palettes, what they did, and how to use them, but, becuase I didn't know their names, I was screwed (same thing happens every year in "Challenge the Campions" at NI-Week - the noobs get points because they know the names of the Express VI - ugh!). QD is essentially useless to me (unless, and this has happened maybe twice, I completely forget where something is on the palette, but then it takes so long to load it's not worth it - yes, I know I can load it on LabVIEW open, but since I use it so rarely, there's no point - and no, this is not a chicken-and-the-egg situation).

IMO the Enhanced IE 2009 is not crap - sure it could use a little work, like anything else.

You're kidding, right? Sure, I love the new features, but you can't seriously tell me that it's buggy-ness is the same level as everything else in LabVIEW.

And the icon editor is CRAP.

Can't agree more - it looks like it was rushed and is chocked-full o' bugs. I guess that's why there are replacements here and here.

Auto tool (you're welcome asbo).

Auto Tool is a much better feature than Quick Drop.

Yeah, I said it. Have at it.

Can you upload your code?

Best. 5000th. Post. Evar.

Well, I agree that it's the best one so far.

Thanks everyone, although I think reputation points are a much better value metric than total number of posts (besides, then we can actually work out a user's perceived SNR).

Me. Whenever I want a new LabVIEW feature, I just walk over to some C-Monkey's desk and ask him for it.

Heeeey! AQ resembles that remark!

Somehow I figure you for the "cuddlier" type rather than cuter

That all depends on your perspective. So, when do I get my cuddle?

You do have a cool snippet tho, I am leaning towards yours is better

Nahh. Both demonstrate the same point, but yours is neater

But I'm the "I'm a LAVA, not a fighter" guy, so *I'm* cuter!