Hi,
I'm not sure which forum to post this to because it involves a combination of labview and teststand. The error I'm getting is more teststand related so it is here.
In our application, we have a labview queued state machine launched by a teststand step using "launch vi asynchronously". In one of the states of this state machine, we are looping grabbing frames from a camera, querying a teststand using "get property value (string)", to overylay on the video on each frame. This is so when we post process the video, we can tell what step(s) teststand was performing (we are writing a status string to a property from teststand as well). Since this string has to be overlayed on the video for each frame to be visible when played back, this happens many many thousands of times over the multi hour test runs of the platform.
My problem is, after 22 hours or so of running, I get an error generated from the "get property value (string)", saying cannot create any more threads. The only thing wired to this tool in our vi is sequence context, which is passed in when the vi is launched from teststand. When opening the "get property value (string)" vi itself, it is very simple, consisting of a "aspropertyvalue" casting, reading of the string from the proprety, closing the aspropertyvalue reference, and exiting. It does not seem like there should be any "threads" being created here, except for perhaps the vi itself executing. But in that case I would assume the OS itself would clean up after itself.
BTW, the OS I am testing on is win7 x64. I did see this though running on our xp box once as well though, same amount of time. It is very repeatable. My next plan is to disable this get property value using a disable case, and run again, but I"m still wondering why this error is occurring. Any help or insight will be appreciated.
Thanks
David Jenkinson
Hi,I'm not sure which forum to post this to because it involves a combination of labview and teststand. The error I'm getting is more teststand related so it is here.
In our application, we have a labview queued state machine launched by a teststand step using "launch vi asynchronously". In one of the states of this state machine, we are looping grabbing frames from a camera, querying a teststand using "get property value (string)", to overylay on the video on each frame. This is so when we post process the video, we can tell what step(s) teststand was performing (we are writing a status string to a property from teststand as well). Since this string has to be overlayed on the video for each frame to be visible when played back, this happens many many thousands of times over the multi hour test runs of the platform. My problem is, after 22 hours or so of running, I get an error generated from the "get property value (string)", saying cannot create any more threads. The only thing wired to this tool in our vi is sequence context, which is passed in when the vi is launched from teststand. When opening the "get property value (string)" vi itself, it is very simple, consisting of a "aspropertyvalue" casting, reading of the string from the proprety, closing the aspropertyvalue reference, and exiting. It does not seem like there should be any "threads" being created here, except for perhaps the vi itself executing. There seems to be something going on behind the scenes of this get property value tool that isn't cleaning up after itself?
BTW, the OS I am testing on is win7 x64. I did see this though running on our xp box once as well though, same amount of time. It is very repeatable. My next plan is to disable this get property value using a disable case, and run again, but I"m still wondering why this error is occurring. Any help or insight will be appreciated.
Thanks
David Jenkinson
