You will also need my LabVIEW SQL Toolkit, which you find on my Database Communication in LabVIEW web site.įor more advanced applications and examples, see Datalogging and Monitoring page.
In that way you use or deploy your applications so that they can be used without having the LabVIEW software installed on the computer you shall use them. Here I have created executables for both the Control Application and the OPC UA Server Application. If you use the Project Explorer during development of your LabVIEW Application it becomes easy to make an Executable Applications.
Making Executable Applications (EXE Applications):
Here is the different DAQ, PID, OPC, and Database settings stored.
In that way you can create executable applications that can be used without having the LabVIEW software.īelow you see the Configuration.ini file. You can also easily make changes to the configuration without changing the block diagram/your code. Under Configuration you can configure the DAQ settings, the Database connection, OPC settings, etc.Īll these values are stored in a configuration file, which means the values you enter here will remain the same next time you open the application. Here you also see an "Event" structure which makes it easy to handle different events like button clicks, etc. It is also easier to maintain, finding and fixing bugs, etc. Basically, a "State-machine" is a Case structure within a While Loop, which makes it easy and very flexible to make larger LabVIEW Applications. Here you can also see the "State-machine" principle. To run the application, you need to start the OPC UA server first, and you also need to setup your SQL Database (which is included in the download package, see below).īelow you see the Block Diagram for the Control Application: It is also easier to maintain, finding and fixing bugs, etc.īelow we see the main User Interface for the Control Application: Here you see the "State-machine" principle. This is a basic example only providing one tag, but you can easly extend the program if needed.īelow you see the Block Diagram for the OPC UA Server Application:
Optionally, the data can also stored in a SQL Server.īelow we see the main OPC UA Server User Interface: The OPC UA Server is created with the LabVIEW OPC UA Toolkit.
You only need the LabVIEW Run-Time Engine, which you can download and use for free without having a LabVIEW license. If you are using the Project Explorer, it is also very easy to make executables, i.e., create professional applications which you can use and distribute without the need of having LabVIEW installed on the computer.
It is also a good idea to structure your code using the Project Explorer in LabVIEW. The video is also available from my official YouTube Channel: Your browser does not support the video tag. The LabVIEW Application Examples are presented in the Video below: Control Application, which get data from a DAQ device (a USB-6008 has been used, but other DAQ devives can also be used), Controls a given process (or a simulator), sends the data to the OPC UA server, and optionally write data to a SQL Server Database and a Measurement File.Optionally, the data can also stored in a SQL Server. OPC UA Server, which is created with the LabVIEW OPC UA Toolkit.Here I will present 2 different LabVIEW Applications: Even for small LabVIEW applications, the "State-machine" principle is easy to use.īelow you can download the code and use it as a template for your own application(s). Using the "State-machine" principle makes it easier to create more complex LabVIEW Applications, it makes it easier to extend and maintain your application in the future. Here I will present some LabVIEW applications where I have used the "State-machine" principle to make the LabVIEW Block Diagrams.