Example Project in LVOOP

[Voklaif]

Hello all,

I am programming with LabVIEW for around 2 years and was recently stumbled upon LVOOP.

I am required to write a communication protocol to work with a micro-controller, which later will be also used for ATP and debug purposes.
I want to build the program "correctly" from the beginning so it will be maintainable and flexible to additions and changes.

My natural way of building a program would have been a queued state machine, with several loops, each loop is in charge of a different module (one for GUI obviously), but as I stated in the beginning, I want to use LVOOP.

Does anyone have a LVOOP project I can use as reference? I've searched online and found some nice examples, but they are small and teach you the basic stuff.
For me it's important to see the how to use the project tree wisely, where to place the classes, see the managing loop and to learn as much as possible before I create one of my own.

Thanks in advance,
Voklaif

[crossrulz]

I still maintain that using parallel loops is greatly beneficial to you here.  But if you insist on LVOOP, you should have a nice long look at the Actor Framework.

[MikaelH]

You can alwasy look at OpenGDS and the examples it comes with and the demo videos :-)
http://opengds.github.io/

http://www.youtube.com/watch?v=UcUj_Gl1JdI
https://www.youtube.com/watch?v=hdcHYS_ZFr8
http://www.youtube.com/watch?v=_BvIiU2VMAU
http://www.youtube.com/watch?v=ZWeO_wPe-VQ
http://www.youtube.com/watch?v=OunqB9UdR6o
http://www.youtube.com/watch?v=VncaD_pKe_s
http://www.youtube.com/watch?v=i77lHDIMs_s

 

[smithd]

17 hours ago, Voklaif said:

I want to build the program "correctly" from the beginning so it will be maintainable and flexible to additions and changes.

...but as I stated in the beginning, I want to use LVOOP.

I feel like you are conflating OOP with "correct". OOP is a way to accomplish tasks, but it is not the only good way. More to the point, if you don't know much about how to implement it, it seems to be a better plan to code the way you know as a starting point, while simultaneously trying to learn from other example applications what problems OOP solves. Then if you reach one of those problems in your code you can just refactor the code enough to solve the problem. The alternative, deciding "I want to use oop" and then building your code can be successful, but it can just as easily end up in a big mess.

You also appear to consider a queued message handler and OOP as mutually exclusive, which they are not. Actor framework is a queued message handler solution with the message handling components implemented by OOP, but there is nothing stopping you from using a more traditional string-based approach with messages handled by an object, or somewhere in between a la http://sine.ni.com/nips/cds/view/p/lang/en/nid/213091 . In fact, outside of a library like actor framework where the object includes not only your code but also the control flow, you will still always need some sort of control flow structure to give activity to the object. I believe this is what delacor's qmh does although its been a while and I may be mis-remembering, and if you watch mikael's videos you'll see the same

If you want to learn actor framework a good go-to is this https://forums.ni.com/t5/LabVIEW-Development-Best/Measurement-Abstraction-Plugin-Framework-with-Optional-TestStand/ta-p/3531389 which also has various blog posts from Eli about how he built it: https://labviewguru.com/2013/03/28/designing-a-labview-measurement-system-with-multiple-abstraction-layers/

 

Edited August 2, 2018 by smithd

[Voklaif]

Thank you for your advises, I will look into the tools that has been offered here.