First Queued Message Handler Template

[SeSandoval]

Hi everyone,

I've been working in this template all this day and i'd like to get some feedback about my QMH Template. I used the QMH Template from NI (Continuous Measurement and Logging) to start, and i did some modifications to it.

Are those modifications good? I'm missing something? How can i improve my architecture?. 

If you have any better ideas of what can i change from my template, i'll do it.

I will give kudos to all the good answers and opinions.

[wiebe@CARYA]

You need to make changes to facilitate your needs. We don't know your needs, so it's hard to tell what changes make sense.

You've decoupled some other processes (DAQ, logging, error handling). Are you sure you require a QMH in the main? What would it do? Some parallel processes are already running parallel. The QMH is used to let processes run in parallel. I've seen QMH's being applied without needing it. It only adds complexity, and quite a bit as well. I'd consider if the event structure could simply control the parallel VI's, and see if I could dump the main consumer. Less is more...

[SeSandoval]

Hello, and sorry for not answering until now.

I didn't see it before.

I just wanted to create a QMH template in case i need it someday.

In some applications i do need to use the QMH.

For example, in one application that i developed weeks ago i used it to acquire data from a scanner via TCP/IP. The problem was that i didn't developed ALL of the application. I only developed one loop for the scanner communication, and it was a big problem, because the other loops were so fuzzy and nothing scalable.

Either way, this is not the final version of the template. It's just the first version.

I'll be working on the second one this week.

Thanks for answer, by the way.