- Deterministic, software-based control—The real-time controller executes the control algorithm at rates exceeding 1 kHz.
- User interface—The user interface VI interacts with the real-time controller and displays data from the control loop. This VI can disconnect from the device and reconnect at any time without affecting the control loop.
- Error handling—The application reports and logs all errors from the real-time controller, shutting down on any critical error.
This sample project is based on the Simple State Machine and Queued Message Handler templates. Refer to the Simple State Machine and Queued Message Handler templates and their documentation, available from the Create Project dialog box, for information about how these templates work.
2. System Requirements
- LabVIEW Full or Professional Development System
- LabVIEW Real-Time Module
- NI-DAQmx device driver software
Real-Time Target, such as an NI PXI Chassis with a Real-Time Controller
- LabVIEW Real-Time
- Network Streams
- Network Variable Engine
- NI System Configuration
- Hardware: A DAQ device. This sample project is designed for an NI PXI DAQ device with at least four analog input channels and four analog output channels, such as the NI PXIe-6363.
This sample project consists of eight parallel loops on two execution targets. The following loops run in parallel on the desktop computer:
- Handling events from the user interface (UI Main.vi - Event Handling Loop)—Produces messages to the UI Message Loop based on front panel events.
- Handling messages from the user interface and the real-time controller (UI Main.vi - UI Message Loop)—Receives and responds to messages from the Event Handling Loop and, using network streams, the RT Message Handling Loop.
- Displaying messages and data from the real-time controller (UI Main.vi - Monitoring Loop)—Displays the latest values of information acquired from RT Loop - System Health and FPGA Monitoring.vi.
The following loops run in parallel on the real-time controller:
- Controlling the plant (RT Loop - DAQ Control.vi)—Reads from the DAQ input channels, applies a control algorithm to each channel, and writes to the DAQ output channels. The control algorithm uses setpoint data and PID gains sent from the user interface.
- Handling commands from the user interface (RT Loop - UI Commands.vi)—Reads commands that are sent from UI Main.vi, using network streams, and produces the appropriate messages.
- Handling messages from all loops on the real-time controller (RT Main.vi - Message Handling Loop)—Consumes messages from all loops that run on the real-time controller.
- Ensuring the RT controller remains responsive (RT Loop - Watchdog.vi)—Pets the watchdog, ensuring the RT controller remains responsive.
- Monitoring diagnostic information from the real-time controller (RT Loop - System Health and Monitoring.vi)—Monitors CPU and memory usage of the real-time controller and information about the control algorithm. This information is written to network-published shared variables and appears on the Data Monitoring and System Monitoring tabs of UI Main.vi.
4. Running This Sample Project
- Adapt the sample project to your hardware.
- In the Project Explorer window, run RT PXI Target»RT Main.vi. This VI initializes the DAQ device and runs the control algorithm.
- Open and run My Computer»UI Main.vi.
- Enter the IP address of the RT controller in the Controller Address text box and click Connect.
- After you are connected, click either Run Control (on the Control Settings page) or Run Manual (on the Manual Settings page).
- Adjust the channel values as necessary and view the outputs on the Data Monitoring page. Until you define a control algorithm, all Control Output Values will read 0.
5. Modifying This Sample Project
Adapting the Sample Project to Your Hardware
- Ensure all devices are configured and connected to the same network as the development computer.
- In the Project Explorer window, add or discover your RT target to the to the top-level project item.
- Drag the following project items from the default RT target to the one you added in step 2:
- Error Handlers folder
- Globals folder
- RT Loops folder
- Support VIs folder
- Type Definitions folder
- Deterministic Loop Variables.lvlib
- Shared Variables.lvlib
- RT Main.vi
- Delete the default RT target project item that no longer has any VIs associated with it.
- Customize the code in the following places to communicate with your DAQ device:
- DAQ Close.vi
- DAQ Initialize.vi
- DAQ Read.vi
- DAQ Write Safe Outputs.vi
- DAQ Write.vi
- DAQ Tasks.ctl
Defining a Control Algorithm
Locate the Control (PID) subdiagram of the Case structure in RT Loop - DAQ Control.vi and modify this subdiagram to apply a control algorithm. For example, you can use the PID VI that is included with the NI LabVIEW PID & Fuzzy Logic Toolkit. By default, this algorithm returns a constant value of 0 on all output channels. You can perform a different algorithm on each individual channel.
Although this sample project is designed to implement a PID algorithm, you can modify the sample project to use any algorithm.
Defining Safe Values for Hardware Connected to the DAQ Device
The Safe Output Value in Global - Configuration Options.vi defines the value that is considered safe for the hardware connected to the output channels of the DAQ device. The Safe State, Default subdiagram of the Case structure in RT Loop - DAQ Control.vi writes this value to all DAQ output channels. By default, this safe state is a value of 0.
Configuring the Application
In the Project Explorer window, open My Computer»Globals»Global - Configuration Options.vi and configure the sample project settings.
6. Important Information
© 2012 National Instruments. All rights reserved.
Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including photocopying, recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of National Instruments Corporation.
National Instruments respects the intellectual property of others, and we ask our users to do the same. NI software is protected by copyright and other intellectual property laws. Where NI software may be used to reproduce software or other materials belonging to others, you may use NI software only to reproduce materials that you may reproduce in accordance with the terms of any applicable license or other legal restriction.
End-User License Agreements and Third-Party Legal Notices
You can find end-user license agreements (EULAs) and third-party legal notices in the following locations:
- Notices are located in the <National Instruments>\_Legal Information and <National Instruments> directories.
- EULAs are located in the <National Instruments>\Shared\MDF\Legal\license directory.
- Review <National Instruments>\_Legal Information.txt for information on including legal information in installers built with NI products.
LabVIEW, National Instruments, NI, ni.com, the National Instruments corporate logo, and the Eagle logo are trademarks of National Instruments Corporation. Refer to the Trademark Information at ni.com/trademarks for other National Instruments trademarks.
Other product and company names mentioned herein are trademarks or trade names of their respective companies.
For patents covering the National Instruments products/technology, refer to the appropriate location: Help»Patents in your software, the patents.txt file on your media, or the National Instruments Patent Notice at ni.com/patents.