Quantcast
Channel: NI TestStand topics
Viewing all 6525 articles
Browse latest View live

Error while browsing project file.and sub vi's simultaneously

$
0
0

I have one Action(it is labview module) step in my sequence file. So whenever I select action step, in steps setting pane under module tab, when i choose the correct project path I'm unable to choose the (vi path) showing errors for dependencies/file not found.

I have labview runtime installed in my system.

kindly,help me with the issue.


Deployment Build with Installers Failing with no Errors Reported

$
0
0

I have completed development and testing for a couple TestStand sequences I would like to deploy. I want to deploy the TestStand sequences with the necessary installers so I can deploy the entire system on a different test computer to run the deployed sequences with runtime applications. I have completed the Developing Test Programs Using TestStand training provided by National Insturments. This is my first time trying to deploy a sequence to a TestStation with the installers to a different test station so I'm still naive to some aspects of TestStand.

 

I’m using the TestStand Deployment Utility to deploy my sequences with runtime installers for NI-DAQ, NI-VISA, Labview 2016, TestStand 2016 and NI-Sync. My test system consists of  an NI –USB 6343 to get some current and voltage measurements, LabView 2016 to send and read information over serial ports and TestStand 2016 to integrate and run all the LabView VIs I have created. In the installer options pane under Drivers and Components of the TestStand Deployment Utility I have loaded the NI Device Drivers 1 and 2 discs and the NI TestStand 2016 Development System disc to load the runtime applications.

 

When I build the deployment with the installers it fails, but no errors or warning are reported and there are no files in the installer folder to run the setup.exe, which will install the test system to the test station. I have attached the files from the TestStand Deployment Utility log. Can somebody help me understand why the deployment build is failing and not including any of the installer files? I have searched in other online forums for TestStand about deployment, but none seem to provide an answer for my problem. All replies are much appreciated.

Requirements Gateway reports "Can't create a 'TestStand Engine'. Application may not be installed.

$
0
0

And yes, it is Smiley Happy

 

  • NI Requirements Gateway 2014 (x86)
  • TestStand 2016 (x86)

Is there a configuration file somewhere I can edit so RG will "see" TestStand?

.Net Adapter for NI Teststand 2016

$
0
0

Objective: run step by step debug of  visual studio C#  code called by Teststand .net adapter

Teststand version: 2016

Visual studio version: 2017 community

 

Based on forum search, I need to attached visual studio debugger process to Teststand.

http://forums.ni.com/t5/NI-TestStand/Can-t-unload-NET-modules-when-debugging/m-p/972569

However it does not work. May I ask what is the catch?

What's the version number of visual studio that is compatible with NI Teststand 2016?

How to check if USB is plugged into computer/device manager

$
0
0

I am making a teststand code and it utilizes a machine which is plugged into a USB port. In my code, I want to have it check the device manager and be able to see if the USB is plugged in and is detected. Can someone help me?

Announcing the TestStand 2017 Beta Program!

$
0
0

I am pleased to announce the TestStand 2017 Beta for LabVIEW NXG 2.0 Support is now open for registration! The TestStand 2017 Beta focuses on the new features added for early access support for LabVIEW NXG 2.0. Major support features in TestStand 2017 include:

 

  • LabVIEW NXG Adapter – TestStand 2017 Beta adds a new early access adapter for integrating LabVIEW NXG 2.0 code modules into test programs. The adapter will be immediately familiar to anyone with experience using the existing LabVIEW adapter, offering a similar experience with LabVIEW NXG.
  • TestStand LabVIEW NXG Conversion Utility– The new TestStand LabVIEW NXG Conversion Utility will help migrate existing test programs that refer to LabVIEW code modules to refer to converted LabVIEW NXG code modules. The Conversion Utility works with any TestStand Workspace, Sequence File, or Deployment Specification and generates a log to help with any code modules that require manual conversion.
  • TestStand API Integration – The full TestStand API will be available for use in LabVIEW NXG 2.0 Beta. Upon installation of TestStand 2017 Beta, a TestStand palette will be added to LabVIEW NXG 2.0 Beta offering a native interface to the TestStand API.
  • LabVIEW NXG Operator Interfaces – TestStand 2017 Beta includes support for operator interfaces developed in LabVIEW NXG 2.0 Beta. All the familiar TestStand UI elements and supporting API have been brought over to LabVIEW NXG and a new version of the Simple UI written with LabVIEW NXG is included.

A full list of all new features is available in the beta documentation. We encourage you to use this beta to try out simple test system development with LabVIEW NXG 2.0 and integration of new LabVIEW NXG 2.0 features to augment existing test systems.

 

Although the TestStand 2017 Beta software is not available yet, I encourage you to register for the beta now so you can access the software once the beta opens.

 

To sign up for the TestStand 2017 Beta for LabVIEW NXG 2.0 Support, complete the following steps:

  1. Sign up for the LabVIEW NXG 2.0 Beta (ni.com/techpreview). TestStand 2017 Beta requires LabVIEW NXG 2.0 Beta installed on your system.
  2. Navigate to the Beta Program Resource Center (ni.com/beta), select TestStand 2017 from the list of software, and click Submit.
  3. Complete the beta application. This information helps us to understand what features of TestStand are most important to our customers. Please ensure that you read and accept the Terms and Conditions of the beta program so that you can be approved.
  4. After you submit your request, please be patient with us as we process your application. Once you are approved, navigate to the Beta Program Resource Center (ni.com/beta) to access the beta software.

Registration does not necessarily guarantee you a position in the beta program. Determination of acceptance into the program is up to the sole discretion of National Instruments.

As with the previous TestStand Beta programs, the TestStand 2017 Beta program will use a private discussion forum specifically for the Beta. Once approved for the Beta, you will shortly after gain access to this forum from http://forums.ni.com/. Please direct any conversations/comments/questions regarding the TestStand 2017 Beta to this private forum only or email me directly. Please do not use this forum for any communication regarding this Beta.

 

I look forward to working with you during this Beta, and please let me know if you have any questions!

 

Kevin F.

Product Support Engineer | Automated Test Software

National Instruments

Have ModelOptions callback execute every batch

$
0
0

The ModelOptions callback is a great way for example to set the number of sockets in the batch model dynamically.

 

The issue is that this is set once and for all when the sequence is loaded.

 

Is there a way to set the number of batch sockets between batches?

 

I would like for our operators to be able to test 5 units one batch, then 4 the next, ...

 

 

Import and exporting steps in TestStand

$
0
0

Hi,
I have created some steps with properties, variables in my subSequence, using the Tools>import/export properties, I exported the sequence and its properties to a.txt file. The txt files contains the corresponding sequence, step type, and other property related values. I plan to use this txt file as a Template for my future sequences by just importing the file back to a new Sequence.

After importing the txt file, to the new sequence only the variables were imported, and the new sequence step field was empty and no steps were imported.

I also tried writing a code module in labview that adds a new sequence to an existing sequence file using invoke and property nodes but couldn't find the option of loading existing steps.

Does anyone know how I can successfully export and import steps to testStand? or an alternative solution without having to manually having to copy and renaming subsequences.

 

Thanks
David


Variable from teststand to scapy

$
0
0

Need to pass variable from Teststand to Scapy python script and build the packet in one step. http: Ether()/IP(dst=server)/TCP(dport=80)/"GET /index.html HTTP/1.0"

 

#!/usr/bin/env python
import sys

Ether()/IP(dst=argv[0])/TCP(dport=argv[1])/argv[2]"

using sys.argv[n], is correct?

Report Options Specify Report File By Expression

$
0
0

Using TestStand 12; how do I set the report file path via a fileglobal variable within the sequence? I can set a static filepath by using the Report Options: 'Specify Report File By Expression' that seems to work, but what do I need to put in there for a variable filepath?

My guess is to use the ReportOptions Callback somehow but am unsure how; anyone managed to do this?

Programatically passing Image to TestStand variable (of type LabVIEWIOControl)

$
0
0

I would like to pass NI Vision Image data from a LabVIEW VI/DLL to TestStand property (for example FileGlobal) of type LabVIEWIOControl. I understand that if I have a NI Vision Image data on the connector pane of the VI I can directly pass it to the TS property of type LabVIEWIOControl. But my requirement is slightly different. I am creating custom StepType in which there is edit UI where the user can choose the desire variable for the image data. That UI object is a TS Expression edit control of type LabVIEWIOControl. I would like to set the value of the variable programatically similar to "TestStand - Set Property Value.vi". Is there way to implement this? I tried using Invoke Node SetValVariant but to no success. I would appreciate if anyone could help me on this. 

Run mode = skip to a specific module in multiple sequences

$
0
0

My goal is to skip a specific module that is used in multiple sequences. I am looking for a method that easily finds a module in each of my tests in Main. 

TestStand Version Selector - mfc140.dll is missing

$
0
0

Dear TestStand community,

 

recently I've faced the following problem. I install TestStand 2016 (32 and 64 bits, both) on Windows 7, SP1. Installation goes smooth, but after restart of PC, I get the message that "... mfc140.dll is missing".

When I start TestStand Sequence Editor, then I recevie message "TestStand 2016 (16.0.0.185) must be active version of TestStand to use the Sequence Editor". When I start TS Version Selector, I get message that mfc140.dll is missing.

Reinstall does not help. The situation is similar for 32 and 64 bits versions. 

Also, I installed separately (from distribution folder) TS Tool (like repair of the installation). It didn't help.

 

Could anyone, please, help me with this issue and suggest, what can cause it?

 

Thanks a lot in advance!

 

Sincerely, kosist90

 

logos_middle.jpg

 

Check out new feature of LabVIEW 2017!

How to get real time of teststand program to compare with another value

$
0
0

I want to compare two time values, one is to get the time right when teststand begins to run, and the other from a VI. I was wondering how to get real time from teststand

NI TESTSTAND

$
0
0

How to create a sequence file?
How to open a sequence file?


How to specify environment when using custom interface

Sequence file

$
0
0

I am new to NI teststand so when I try to open It is coming in some XMl format which is not understandable.so how i can see the backend code.

pass 3 variable from Teststand to python,

$
0
0
I want to ask how to pass 3 variable from teststand to python.
<Step1>
Create Call executable. Expression, Locals.ln
create standard output, Locals.out
 

<Step2>

FileGlobal--
Payload(var3) - 'Hello World'
SourceIP(var2)- "192.168.1.1"
DestIP(var3)- "192.168.1.4"

 

 

<Step3>

#!/usr/bin/python
print(var1)
print(var2)
print(var3)

 

TestStand 2016 SP1 is Now Available

$
0
0

NI is excited to announce the availability of TestStand 2016 SP1, a service pack release on top of TestStand 2016.

 

Continue to take advantage of new features implemented in the 2016 release, such as TestStand Environments, native enumeration support, and a redesigned Property Loader, while enjoying a greater degree of stability with 2016 SP1 bug fixes.

 

To learn what technical issues were identified, prioritized, and addressed based on input from the TestStand Community, check out the List of Bug Fixes for 2016 SP1. Refer to the Release Notes to learn more about installing or upgrading to TestStand 2016 SP1.

How to convert into time format from Seconds() function

$
0
0

I used the seconds() function to get the time when I ran the TestStand sequence. How do I convert this number of seconds into a hr:min:sec format?

Viewing all 6525 articles
Browse latest View live


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