LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

queued msg handlers and ActionEngines

I am sure the messenger library is cool, but it is OOP, it is for me "dragons ahead!" 🙂

0 Kudos
Message 11 of 15
(1,316 Views)

take a look also at the LabVIEW Core 3 manuals! They build this course on the QMH. 

And yes you are write it is a quite complex structure, where you can send massages to the dedicated loop from all over the programming. The idea is to have an architecture which can be scaled to the moon! An architecture which can do almost anything. 

So if you want to create a small programm you might be better of with a state mashine or a queued producer consumer state mashine. 

If you want to create a structure where you can't access certain cases over the queued massage simply put the reference into a FGV, and write the massages over the FGV. You can build into the FGV that certain massages can only be send inside the library. So you can be sure only once the init case is fired.

 

0 Kudos
Message 12 of 15
(1,306 Views)

I went through the Core 3 online training last year, yes, I know about the QMH, and the other design patterns based on the QMH.

 

The intention is only to ask around what other (more skilled) programmers use in their middle and larger sized applications. I always like to learn from others, specially because I am not a pro programmer but a physicist who uses LabVIEW (beside, some of the end users are our technician staff, so I need to maintain a certain quality, I am not the only user).

0 Kudos
Message 13 of 15
(1,293 Views)

@Blokk wrote:

I am sure the messenger library is cool, but it is OOP, it is for me "dragons ahead!" 🙂


Though built from LVOOP internally, use of Messenger Library requires very minimal use of OOP.  The  Sample project involved making three copies of standard template classes (using "Save as...").  After that two minute operation there was no OOP skills required.   One can even drop the need for copying the template classes if one is willing to have your Acquisition and Logging components be subVIs of the main VI, like in the NI project, rather than dynamically "launched" things.  Perhaps I should rewrite the Sample Project that way.

0 Kudos
Message 14 of 15
(1,273 Views)

Ok, thanks, I will have a deeper look when I have time 🙂

0 Kudos
Message 15 of 15
(1,271 Views)