crelf

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.

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

That's because the NI Forums attachments don't have extensions Here they are:

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

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.

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 is a much better feature than Quick Drop. Yeah, I said it. Have at it.

Can you upload your code?

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). Heeeey! AQ resembles that remark!

Me.

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

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

Can you reporduce the issue with a smaller subset of your application? Maybe narrow it down to the VI or a group of VIs that the documentation generator is bugging out on? If so, can you post the Vis?

That's fair. Sounds like the progression of most relationships. Or is it the opposite?

No, not a touchy-feely post about love amongst mankind, but a philisopical question about access scope. I have two classes: Class1 (contains MethodA) and Class2 (contains MethodB). When I set MethodA's scope to community, and I want to put it on the block diagram of MethodB, I need to make MethodB friends with Class1. Why can't I just make MethodB friends with MethodA?