Hi,I'm new to the actor framework. I've worked through the hands-on tutorial and looked at various examples.I'm now trying to build my first small application and was hoping for a nodge in the right direction with two main questions. Before going into those I will outline the software.The application is used to calibrate a device. As such it has analogue inputs/outputs but is also using I2C via FTDI.The whole calibration process is strictly scripted.As all of this can be functionally described as the process I wanted launch a process actor. The process actor is then starting a state machine actor as well as an IO management actor which subsequently starts the DAQ and the I2C actors.The top level application is also going to start an error handler as well as a GUI actor.Now for my first question. I only want to show the GUI actor and not the launcher. What is the most elegant way of causing the top level app to shut down from within the GUI actor?I had two approaches:1. generate a user event which gets written into the private class data of the GUI before the actor gets launched. The "send stop" vi is then put into an event structure which waits for the GUI to fire the user event (which is done in the GUI actor from a "panel close?" filter event). I disbanded this approach as I didn't like the fact that I had to pre-initialise the actor with data member access vis before the launch actor vi had even been started. I got the impression that all necessary initialisation should be done from the "pre launch init" as everything else would mean that the actor isn't self contained anymore which is one of the big strengths of the actor framework.2. I've attached screenshots of this approach. As you can see I am now using the actor queue of the top level app. As no other actor is using this queue I use it to signal the shut down by acquiring the caller queue in the GUI and enqueuing a message from within the gui. This seems slightly better than the first attempt as it is self contained but I still don't like it as it feels like a hack, abusing the top level actor queue for a purpose it was not intended for.Now for my second question. This is about implementing the state machine. To me it seems that the most intuitive way of implementing this is by creating a FGV in the state machine class and have authorised actors enqueue commands by using the appropriate message class (third screenshot). Is there a better way of doing this?Thanks a lotMathis

ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

Actor Framework Discussions

Newbie questions about AF

Author

Ohhhh Emmm Geeee

I was totally unaware that existed. This is by far the best LabVIEW has ever looked.

Looking into getting this look into an application as we speak!

Author of the Simple TestStand User Interface API

Message 21 of 22

(1,416 Views)

Mathis_B wrote:
@Dr Powell: I've seen your post about your AF which uses 30k+ actors without performance issues. Impressive feat! Is that available to the public?

I tested up to 10k. Jon_mcbee tested 65K with Actor Framework actors.

My Framework is Messenging, on the LAVA Code Repository.

Message 22 of 22

(1,416 Views)

Actor Framework Discussions

Newbie questions about AF

Re: Newbie questions about AF

Re: Newbie questions about AF