wishfulthings
-
Posts
4 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Gallery
Posts posted by wishfulthings
-
-
-
QUOTE (crelf @ Feb 17 2009, 04:07 PM)
That's not a stupid question at all (I actually did the same thing yesterday), but you may not like the answer: there is a way to get the block diagram property node, but it's a private method - http://forums.lavag.org/VI-Scripting-Readme-First-t1207.html' target="_blank">read here for more information on how to get access to private methods.Thanks for the info. I've now got it working perfectly
-
This is exactly what I want to do but I'm using 8.6 and can't seem to get access to the Block Diagram property node. Is there a similar method I can use for 8.6.
This is my first post and I only have a few months Labview experience so hopefully this isn't a stupid question
Read the Frame names of a case structure
in VI Scripting
Posted
QUOTE (crelf @ Feb 24 2009, 04:00 PM)
I have attached a number of VIs and will attempt to explain their operation. Download File:post-14706-1235987484.vi
Download File:post-14706-1235988461.vi
Download File:post-14706-1235988471.vi
I have been tasked with trying to make a sequencer using a state machine with perhaps 100s of cases. I decided it would be nice to split the cases into groupings which were more logical, ie all cases relating to GPIB instruments together in a seperate VI, cases for switching in another vi etc... In doing this my difficulty was to then know in which vi a case resided. This was necessary as to open each vi sequentially and then look for a case was causing unacceptable delays when running the application. So I needed to create a look up so I would know exactly where to find each case. This was how I did it but there may be a much cleaner way.
Firstly the "Read Case Names.vi" reads all the cases in the vis located in a test sequences subdirectory up from my working directory and writes them to a cases.txt file.
Then the "Write Case Locations.vi" writes the cases and their locations to two seperate arrays.
These have been incorporated into a "Create Control.vi" which then creates a control for all the cases which enables me to use the cases as strict typedef enum which I can use to then select my next state(s) in the state machine.