06-07-2007 03:52 PM
06-07-2007 06:28 PM
06-08-2007 07:39 AM
Thanks for the feedback. I will probably make use of the AE concept. My only concern is whether the LabVIEW engine or TestStand engine will queue up requests to execute the non-reentrant VI from separate threads. I assume this must be handled somehow - it wouldn't be particularly intelligent to rely on non-reentrance to lock a resource if it throws an error every time two code modules attempt to access it in parallel. I tried to search for some info on how LabVIEW manages this, but maybe I was using the wrong keywords. In general though, action engines seem to be the way to go - it's almost like forcing LabVIEW against its will to be object-oriented. 🙂
06-08-2007 10:29 AM
06-08-2007 10:56 AM
One detail .... AE or other....
If the the AE is unloaded from memory in-between steps, care should be taken to ensure the default value are not used.
In that case, a config file (ini) can be used to store the values and a stategic use of "first Call" to ensure the AE (or whatever) has the proper values.
I am not a TestStand guy but I believe it is possible to launch a VI that runs in the background to keep the AE valid.
Ben