Quantcast
Channel: LabVIEW topics
Viewing all articles
Browse latest Browse all 66666

Architecture for Data Acquisition, sending commands, and polymorphism

$
0
0

Hi all,

 

I have a project which is beyond my current (very basic) labview skills and I am looking for some advice on the best way to structure my code as well as some functions and resources that I may find useful. I would like to learn as much as possible about good labview coding practices, how to implement design patterns in labview etc. I have Lab View 2013

 

 

I need to do the following:

  • Continuously receive messages over a serial port, parse them, and update values which I will use in several realtime plots  and to write to a file
  • Be able to send messages when the user presses a button, even while the program is receiving messages.
  •  Be able to easily swap out the message parsing code and change the values that are used for plotting without huge amount of rework. I have 2 custom devices that although similar have slightly different message structure and contents. eg, one version of the software will need to interface with device 1, that sends 3 temperature values and one pressure value- Version 2 of the software will need to interface with device 2 that sends 2 temperature values, 2 pressure values, and a power value.
  •  It would be nice, in the future, to have some sort of plug ins feature where i could choose to use different vis for added functionality.

I've been reading a bit about actors and message queues and think that actors might be quite useful for point number 3 but am struggling a bit to see how to use them.

 

Any advice is greatly appreciated. Thanks in advance


Viewing all articles
Browse latest Browse all 66666

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>