jcarmody

[...] Style: Did not use local variables, used producer consumer and display loop, was comparitively neater. But used many references in the

consumer loop and property nodes in the display loop. Are these acceptable?

I recall that a P-C architecture was more complicated than necessary for my exam and the practice problems. It might have led you into using references/property nodes unnecessarily.

[...] Personally, I think that your consumer should not be interacting with controls at all. The producer should read values, and pass the data with the command to the consumer. Since you have a display loop, the consumer loop shouldn't have any terminals, references, locals or property nodes in it. For example, you have a subVI which uses a references to change the blinking property of the Pilot boolean.

Hello everybody.

I have test tomorrow [...]

How'd it go?

I'm not clear on your problem, but I see that you don't respond to events for anything except the 'Shutdown' boolean. The Case Structure in your consumer loop is looking for the 'Consumer Command' from the producer, which never comes.

Que` pasa? I am able to use the tool, but installing it wasn't clean. I like the way you think

Here's how I found all Free Labels on all Block Diagrams below one top-level VI:

Then, I looped through them looking for the tag I was interested in:

Be careful while scripting, not because of the "rusty nails" but more because it could be more fun than what you're supposed to be working on...

A hairy yak is a happy yak ~ unknown, circa 2000 BC

Cross-posted on NI here.

I just witnessed a 4-wire resistance measurement across the barrel of a metalized connector made with a standard set of alligator clip-like probes.

One operator makes this particular measurement with the clips only slightly opened, and the resistance exceeds the test limits. This triggered the Manufacturing Engineer to get involved and his habit is to make this measurement with the clips almost fully opened. The resistance, when doing it this way, is about 1/3 of the first operators method.

I tried to imagine why this might occur, but I'm stumped. I thought about the length of the current paths through the material and how the corresponding change in distance would increase the resistance when the probes are closer together, but this doesn't explain the 3x factor. This would also imply that turning one clip 180 degrees should result in a change in the opposite direction, but this isn't observed. I'll keep guessing.

Have you seen this? Can you explain it?

I'm one of those people that won't open Word documents from people I don't know. As of this posting, however, I can see that (at least) two people don't have the same concerns. If you'd post the questions instead of the attachment...

Here's an absurd scenario:

Me to LAVA: How do I do something?

LAVA to me: Like this.

Me to LAVA: Oh, thank you so much! That's just what I was looking for. That was fast; you folks are the best.

.

.

.

<some time later...>

Me to myself: I can't use that code, because the author has a copyright...

Here's an article that explains the difficulties, inherent in copyright laws, for even the most libertarian among us to give away our work.

Well, then, why don’t you just “make it public domain,” some then, a bit unreflectively, retort. The problem is, there is no clear and good way to do this.If you use a Creative Commons license, you are actually employing the copyright the state grants you–you are putting conditions or limitations on what others may do with your works. Even if you use the least restrictive type, “Attribution,” you are requiring others to do something to avoid being liable for copyright infringement.

TestStand uses a database schema that I've grown fond of. It does the things ShaunR describes.

Default TestStand Table Schemas

Creating a TestStand Database Schema from Scratch

The second link contains more information.

Yes, please post in LabVIEW 2009 (however, I understand that you may not be able to)

You can if you use the Code Capture Tool. Something could be said about eating dog food...

My knee-jerk reaction was "you could write a script for that"!

I have an idea sitting on my shelf (or a back-burner, I can't remember where I left it) that will require me to find dynamically called VIs.

I just tried my Lab Python vi.

I finish reading this thread, pop over to try something and experience the same thing.

Could you use Lab Python? I wrote a small example here.

[edit - fixed link to original discussion in the NI Forum]

I'm not sure I understand what you're trying to do, but this may help you get started.

The Tree Control API can be found right here, on LAVA.

Benchmarking nugget - http://forums.ni.com...de/td-p/1179349

That's a lot of Local Variables...

I use Control Value: Set Method.

If people approve and think it's useful, I will add it to the SQLite API for Labview as an example.

I was hoping you would post this; it will be useful in my next project. Thanks.

What if you enclosed the contents with another frame (say a sequence), then moved that. The Scripting Tools have some functions that might help, from which this clip was extracted:

Does that make it easier to do what you want?

Yes, but I couldn't get it to work with a Sequence structure. It worked fine with a Diagram Disable, though.

Thank you.

[...]

But wait! The CCT dropped a wire... Bug?

I seem to have lost that wire when I edited your snippet. My BD is missing it, too.

[...]

Turns out you can't make a snippet use linked references, even if you include the terminal.

It turns out YOU can't do that, but if you use the Code Capture Tool you could.

I want to be able to move the contents of a frame in an Event structure to a frame in a Case structure. I've only been able to move them individually, but I want to accomplish this without losing the wiring. Is it possible to do this in one move, or will I need to move and then rewire them?