Hi, I am trying to develop an ESS test sequence (for temp and vibe) in TestStand. I have developed two actors; one which is the top level root that acts as a GUI and launches a nested actor which is used to sample/monitor daqmx analog input data and pipe it back to the top level GUI actor through abstract messaging. It is working great when I launch the actors on their own from LabVIEW (a "Launch.vi"). However, I am trying to figure out how to spawn/launch the root actor from TestStand. What happens now is I call the "Launch.vi" from TestStand and it launches the actor OK, but then just keeps going and finishes the sequence while the actor continues to run. What I would like to do is launch it while TestStand waits for the actor to complete (probably VIA operator pressing stop button or similar) and pipe back the results from the actor to TestStand. The reason I'd like to use TestStand for this is that I have already created a full ambient ATP sequence which is working great. I'd like to have an ESS sequence for that portion of testing so I can continue to leverage TestStand reporting and database logging which I am currently doing. I realize I don't necessarily HAVE to use actors for this, but I'd like to if this is something that is possible and considering it is working really well on it's own. This may just be something simple, but I'm fairly new to actors and have been looking for excuses to implement them in my development and deployment. Thanks for any help.

I use TestStand for exactly the same thing, ATP and Qual of components in thermal, vibe, and other environments. When dealing with actors in a sequential application like TestStand, the best course of action is build interface classes for your actors that can be used like traditional railroad track vi's. For example, you can have a start DAQ vi that launches the actor and stores it's enqueuer in the private data of the interface class. You then have a vi that is "set chamber temperature". That vi sends a message to the actor and then sits and waits for the actor to report that the temperature has be achieved. In TestStand, this will block the seq until that vi receives appropriate confirmation. Add more commands as required. Then your "stop daq.vi" would "Send Normal Stop" to the actor. The method for getting data into the synchronous interface class is typically done with a proxy actor. I'll try to find a good example on the forum of the proxy...I think justACS has posted several things on it.

Actor Framework Discussions

Launch an actor from TestStand

Solved!

Is there any example code how to send message from teststand to actor and return value from actor to Teststand?

what if my actor is built as an application?

how do I use it with Teststand?

Any example code would be very much appreciated. Thanks!

Message 11 of 11

(475 Views)

Actor Framework Discussions

Launch an actor from TestStand

Re: Launch an actor from TestStand