Set Up SystemLink to Use Tags and Messages with cRIO

Updated Oct 30, 2020



  • LabVIEW SystemLink Toolkit


  • NI CompactRIO

This tutorial shows you how to install and configure SystemLink to use tags and messages on a CompactRIO with LabVIEW NXG.


Make sure you have LabVIEW NXG and the latest compatible version of the NI-CompactRIO driver installed.


Install the LabVIEW SystemLink Toolkit

  1. Launch NI Package Manager and search for "SystemLink". Select LabVIEW SystemLink Toolkit.

  1. Follow the prompts to complete installation.

Configure NI Web Server

  1. After you install the LabVIEW SystemLink Toolkit, launch NI Web Server Configuration.

  2. Select Secure remote access and click Next.

  3. Create a password and click Next.


  1. Select a HTTPS certificate and click Next.

  2. Review the Configuration summary and click Finish to start the web server.

  1. The NI Web Server is now running.


If you arrived here from the LabVIEW NXG example code, return to your project. Otherwise, complete the following steps to create a new project.


Create and Configure a New Project in LabVIEW NXG

  1. Launch LabVIEW NXG and navigate to the Learning tab.

  2. Navigate to the Examples tab and select the Programming CompactRIO folder.

  1. Select Tags and Messages with CompactRIO.

  1. Name your project and click Create.

  1. After the project opens, set up how you want to authenticate credentials when the VI runs.

Choose from the following options. See below for more detailed information about these authentication credentials.

  • Auto (selected by default)

All data communication happens between the target and host machine. The host acts as the SystemLink Server in this case. Data can be shared between applications running on the host and all targets connected to the host. The credentials and HTTPS certificate (if any) are managed automatically so the target can securely connect to the host.




  • SystemLink Server

Communicates with a server machine with SystemLink Server installed using HTTP credentials specified when opening the configuration. These credentials should be securely deployed to the target rather than hard-coded on the diagram. The target does not need to be managed by the server in this case. If the server is using HTTS with a certificate that is not signed by a commercial CA, you need to either:

    • Export the certificate from the server, deploy it with your VI, and reference the certificate when opening the configuration

    • Disable server verification when opening the configuration, which opens the data communication to man in the middle attacks.




  • SystemLink Cloud

Communicates with instead of an on-premise installation of SystemLink Server. This requires going to SystemLink Cloud and generating an API key to reference when opening the configuration. This key should be securely deployed to the target rather than hard-coded on the diagram.





Now that we’ve set up the Authentication Credentials, you can run the VI and begin using SystemLink Tags and Messages. For more information on communicating with tags, refer to the SystemLink Manual.