I tried to create a template based on OOP for QMH. During development I have been confronted with infinite crashes of LabVIEW so I decided to slow down with this project and open it to the community. I finished my working example and stopped for now.
So if anyone is interested to play around with the code, see attached ZIP file (LV 2020).
Manufacturing a satellite or a simple pen require to test the quality of the product before delivery to the customer.
LabVIEW is widely used for that purpose. Since 20 years of LabVIEW development I saw numerous test framework. I was wondering if people where interested to work in a collective and open source test framework.
Per example the following feature can be included:
HAL (hardware abstraction layer)
Database to record test results with the data viewer (PostgreSQL)
Image analysis (open CV) + bar code reader
User access level
Jig identification to prevent user error (testing the wrong product with the wrong jig/test sequence)
and so on....
I often have to create interfaces for power supplies. I often use the QMH for my overall architecture.
I have created a QMH that controls multiple power supplies. It was designed in such a way that it takes a minute to add an additional power supply. Of course I am using Dynamic Dispatch to use multiple types of power supplies. It works quite well.
I am trying to get better at LVOOP and plug-ins. I was thinking of creating an abstract class that contains a QMH for just one power supply. Of course I would create children for several types of power supplies. My plan with the single QMH for each power supply would be to use it as a plug-in or use a sub panel so that all the QMHs are on one UI.
If anyone has any advice on the methodology please feel free to comment. Also I am new to LAVA so I hope I am not asking something that has already been solved.
I've been maintaining and improving a LabVIEW project which controls and automates a prototype microscope array for 2 years. I'm an engineering apprentice so I don't have that much experience with LabVIEW.
The current framework of the project is a simple "Producer/Consumer" which has served well but is no longer future proof and scalable. I want to revamp the program which is quite big and complex. And I need help since this will be the first time of actually starting a real project from the ground up.
The most modular and scalable framework I found was the QMH (Queued Message Handler). It's similar to the basic P/C loop and has the possibility to have multiple parallel consumer loops. But I have no experience on starting from 0.
If any you have docs or give advice on starting the project would be appreciated. Especially something on codding with a QMH structure would be helpful.
Cheers from France!
My concern is about object based framework.
I'd like to talk about a "sensitive" subject, which divides people around me.
I'm sure there are a plenty of objects aficionados here.
A few years ago, LabVIEW give us the first object based template : the Actor Framework, which is certainly powerfull
When I conduct Core3 training, I'm tempted to show what could be an object based framework in LabVIEW, then I remember how the actor framework looks, then I decide to make my trainies continue to use LabVIEW, and finally I don't show the actor framework.
When will NI provide a SIMPLE object based framework in the TEMPLATES ?
Something like the command patern exposed here by Elijal Kerry :
or in a the test executive example of the PTP sequencer :
I still use the "old" QSM (please Daklu, don't bite me), for sure it is not an ideal solution...
I love objects, I used them a lot in my code, but not currently for my high level code.
Any links or suggestions ?