ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

Home Community Example Programs Example Code Document

Example Code

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
ASK A QUESTION

Using the NI VeriStand .NET API in LabVIEW to Control a VeriStand System

by: Active Participant
‎10-15-2013 07:01 PM
Last Edited by: Active Participant Ryan_S ‎01-30-2017 09:25 AM

Products and Environment

This section reflects the products and operating system used to create the example.

To download NI software, including the products shown below, visit ni.com/downloads.

    Software

  • LabVIEW
  • Veristand

Code and Documents

Attachment

Overview

This example combines multiple shipping examples, as well as some custom code, to perform various actions on a VeriStand system using the VeriStand .NET API in LabVIEW.

Description

This example is intended to give a full picture view of a typical implementation of the VeriStand API. This code demonstrates the following:

  • Deploy a System Definition File
  • Get a list of model parameters
  • Read & Modify model parameters
  • Monitor model state and model time
  • Read multiple channel values
  • Un-deploy the System Definition File

Requirements

Software

  • LabVIEW 2013 or compatible
  • VeriStand 2013 or compatible

Hardware

  • None


Steps to Implement or Execute Code

  1. Open the attached VI
  2. Using the file path control, browse to the Sinewave Delay.nivssdf example
  3. Specify the IP Address of your Gateway
  4. Run the VI
  5. Modify different model parameters and observe the affects of the changes on the channel outputs

Additional Information or References


fp.pngbd.png

**This document has been updated to meet the current required format for the NI Code Exchange.**

Example code from the Example Code Exchange in the NI Community is licensed with the MIT license.

Comments
Nico_EMC
Member
Member
on
‎03-25-2014 08:04 AM
‎03-25-2014 08:04 AM

I think you've forget to let the "attached VI"

But it's easy to recreate it with the diagram picture, so thanks for this exemple

0 Kudos
Ryan_S
Active Participant
Active Participant
on
‎03-25-2014 09:07 AM
‎03-25-2014 09:07 AM

Hey Nico,

I'm not sure what happened, I think the file used to be there. I re-made it real quick so the file won't look identical to the pictures but it should work properly. Enjoy!

0 Kudos
Nico_EMC
Member
Member
on
‎03-25-2014 09:33 AM
‎03-25-2014 09:33 AM

Thank you, it works well

0 Kudos
beavercreek
Member
Member
on
‎09-16-2015 09:57 AM
‎09-16-2015 09:57 AM

I created a 2012 version of the vi.  Any reason it should not work?

0 Kudos
Ryan_S
Active Participant
Active Participant
on
‎09-17-2015 09:34 AM
‎09-17-2015 09:34 AM

It should work. The API calls made in the example would be the same for 2012 as in 2013+. However, if you "created" the VI by doing a "save for previous" you may need to re-link the .NET assemblies to the function calls. If it's not working, I'd recommend contacting support.

0 Kudos
meBaga
Member Member
Member
on
‎02-10-2017 05:38 AM
‎02-10-2017 05:38 AM

Hi Ryan,

How can I use the same if my veristand project is running in RT. I have posted the problem statement Here. Can you please look into that once?

0 Kudos
Contributors