01-10-2013 09:03 AM
I know this is an old post. Will repost if necessary.
What is meant by :
"...you have to drop a TestSTand local variable..." I don't know what a TestSt is.
I know I haven't posted the code but why would I have an output from a LV2012 prototype adapter that writes to a locals.x but nothing is written to locals.x?? My code is very similar to the one in this post. When I put a STOP on the next line after the vi call and look at locals.x in the variables tab it equals 0.
I don't have the propert loader step in my code. What is that for??
Thanks..
01-11-2013 10:05 AM
@clint100 wrote:
I know this is an old post. Will repost if necessary.
What is meant by :
"...you have to drop a TestSTand local variable..." I don't know what a TestSt is.
I know I haven't posted the code but why would I have an output from a LV2012 prototype adapter that writes to a locals.x but nothing is written to locals.x?? My code is very similar to the one in this post. When I put a STOP on the next line after the vi call and look at locals.x in the variables tab it equals 0.
I don't have the propert loader step in my code. What is that for??
Thanks..
The "TestSTand" thing is likely just a typo. They are just saying you need to specify the teststand variable path in the module specification pane. Without more details about what you are doing it is hard to say why it's not working for you. You might have the module specified incorrectly, or the vi might not be doing what you think it's doing. There are many possibilities.
-Doug
01-12-2013 07:06 AM
Hey Doug,
Thanks.. I revisited my vi and compared it to the old post. Again, I know I haven't included the vi but this is what it did. It was a very simple vi to try and popup the lv front panel, ask the operator for input then close. Upon closing pass the values back to Teststand ( locals.x) No problem w opening LV then closing it. What I found was I had the variables outside the do/while loop in LV2012. Once I moved them inside the do/while loop the values were there and visible in TS. Apparently LV reinitializes the values when it returns to TS...I guess.
Do you know what the property loader does in the old post??
Thanks
01-14-2013 10:01 AM - edited 01-14-2013 10:01 AM
The property loader is a step type and utilities designed for loading the values of properties from a file or database at runtime. Typically someone would use this to load varying sets of limits at run-time, but it's not limited to loading limits, you can load other kinds of property values as well.
-Doug