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

I want to create function in teststand

January 8, 2019, 12:22 am
$
0
0

int abcd_Gonder(void)
{
unsigned char SerialString[25];
int LengthSerialString;
int CheckSum = 0;
int err = 0;

FlushInQ (x_COMPORT);
FlushOutQ (x_COMPORT);

SerialString[0]= 1;
SerialString[1]= 2;
SerialString[2]= 3;
SerialString[3]= 4;
SerialString[4]= 0x88; //Checksum
SerialString[5]= '\0';

LengthSerialString = 5;

ComWrt(x_COMPORT, SerialString, LengthSerialString);

return err;
}

 

I want to send this message using RS232 port. I have to use teststand parameters to create this function. So I can't write this code in visial studio using class librarry to export dll . I'm new at TestStand and I need help that how can I create a function like this.

↧
Search

Pass / Fail Indicator TestStand GUI

January 8, 2019, 2:31 am
$
0
0

Hi All,

 

Attempting to modifiy the Simple User Interface example that comes with TesStand.

 

I am trying to output the overall test result of the sequence as a PASS / Fail indicator. The indicator is a Labview native indicator.

 

The code runs without errors but it does not appear to update the indicator. Am I doing something wrong?

 

Pass_Fail indicator TestStand GUI.png

 

 

↧
↧

Read Excel Teststand 64bits

January 11, 2019, 8:15 am
$
0
0

Hallo,

 

Im trying to read a selected data from an excel file through TestStand (64bits).

I was trying to use the ActiveX adapter, but i only find as Automation Server "Microsoft Excel 16.0 Object Library (32 bits), and im getting an error. Please see attached.

 

Could you please let me know how can i manage this?

Thanks so much in advance 

↧

Which part of the process model to avoid when changed

January 14, 2019, 10:05 pm
$
0
0

At our factory I need to change the process model, eg. how to extract the part number.

When I change the process model, must I avoid changing the call backs(eg. preUUTloop) in the process model or is it recommended to put the change in the call back?

 

 

↧

Adding comments to new format property loader files

January 15, 2019, 3:39 am
$
0
0

With the old property loader format there was an option with "Skip Rows Beginning With:" which I used to tag property values with requirements. There doesn't seem to be an equivalent with the new file format, is there any syntax to add comments that won't cause an error when the file is loaded?

↧
↧

Old Numeric Limit Test measurement value displayed for Skipped step

January 15, 2019, 4:08 am
$
0
0

I have a TS2012 sequence that is running with the Test UUTs Execution Entry Point within a modified Sequential Model.  The sequence has a number of Numeric Limit Tests that execute conditionally (occasionally for some test runs they will be skipped). 

 

For a single Test UUTs execution; the behaviour we are seeing is that for the first UUT, a particular Numeric Limit Test is run and returns a measurement.  My issue is that if now a second UUT is run and that the Numeric Limit Test that returned a measurement value for the first UUT is conditionally skipped, the step status says Skipped (as expected) but the measured value displayed by TS is the same value as returned for the first UUT.

 

It looks to me like the ResultList is not being cleared correctly at the end of a run and as a consequence contains and displays data from a previous run. 

 

We have modified the Sequential Model so it is possible we have accidentally deleted the step that stops this sort of thing from happening.  Outside of that any suggestions about why this happens and any solutions to stop it would be greatly appreciated.

 

Steve

↧

Errors from Labview VI not displayed in TestStand

January 15, 2019, 8:00 am
$
0
0

Hi,

 

I just installed and started to use TestStand to create testbenches using different VI's. Everything works fine, except for the fact that when there is any error in any VI of the sequence, this is not displayed and the TestStand continues the execution of the tests as if nothing happened.

 

For example, one error could be that a file I want to open in the VI is not found (this error is correctly displayed in Labview by a pop-up window, without using Simple Error Handler or similar).

However, if I run the VI in TestStand, the error won't be displayed and the execution continues.

The option Configure --> Station Options --> Execution --> On Run-Time Error is set to Show Dialog Box.

 

Is there any reason why this happens?

 

Thank you

 

↧

Modify Report File Name

January 15, 2019, 8:21 am
$
0
0

Hi,

 

I'd like to modify the default filename format in the report  options utility.

The default is SeqFileName_Report[Time][Date]_00001.xml.

I'd like to add a variable to the string

SeqFileName_Report[TestPoint][Time][Date]_00001.xml

 

Which callback to I need to use to modify that and how do I do it?

 

Thanks

 

Curt

 

↧
Search

Announcing the TestStand 2019 Beta Program!

January 15, 2019, 1:04 pm
$
0
0

I am pleased to announce that we plan to release a beta version of TestStand 2019 in the latter half of January. Additions to TestStand’s features include:

  • Adapter Support for Python – TestStand 2019 beta will offer native support for calling Python modules developed in Python 2.7 or 3.6. The familiar experience of TestStand Action, Pass/Fail, Numeric Limit, Multiple Numeric Limit, and String Value Test now supports Python code. The adapter support calls into module functions, getting/setting module attributes, creating class instances, calls into class member or static functions, and getting/setting class member or static attributes. Data is converted to each environment's native structures, such as mapping Python tuples to TestStand containers. You can also store and reuse Python objects in TestStand object reference variables. Python scripts will run outside the TestStand process, in a separate process that hosts the CPython interpreter. Use the advanced session management options to support running multiple instances of the interpreter to enable parallel testing with Python.
  • Parametric Sweep and Stream Loop Step Types – The Stream Loop is an enhanced version of the For Each loop in the 2017 Data Streams feature.  The loop iterates over an input file and can additionally write to an output csv file each time it reaches the end step, no longer requiring the addition of a Write Record step. Similarly, the new Sweep Loop introduces the ability to specify parameters, and natively sweep over the parameters in TestStand.  
  • Multicore Scaling Improvements – TestStand 2019 includes extensive optimizations for multicore processors. These improvements can significantly increase throughput for systems with high core counts running short duration tests on multiple UUTs in parallel. Performance improvements depend heavily on the design of your system.
  • Enhanced Support for LabVIEW – LabVIEW adapter allows you to switch between VI or PPL and helps in seamless debugging of PPL. With this new feature, LabVIEW adapter allows you to override the module settings to run either VI or PPL from the adapter configuration dialog for all LabVIEW steps. The adapter also provides the option of auto building the PPL.
  • Reporting Improvements: Default report formats now include an option to save a PDF copy of the report. The TSGraphControl ActiveX control has been replaced with an HTML5 graph control.
  • Improved Integration with CVI: When used with CVI 2019 or later, TestStand 2019 supports source code navigation, auto-creation of TestStand Enums from structs, and the ability to distinguish pointers from arrays in the Module tab. To test this out, sign up for the CVI 2019 beta at ni.com/beta. 
  • Addition of Quick Drop - You can now use Ctrl+Space to access the quick search dialog box to easily insert steps, sequences, and variables into the Sequence Editor.
  • Support for NXG 3.0/3.1 


A full list of all new features will be available in the beta documentation, which will be available when the beta begins. Although the TestStand 2019 beta software is not available yet, I encourage you to pre-sign up for the beta now so that you can access the software immediately once the beta opens.

To sign up for TestStand Beta, complete the following steps:

  1. Navigate to the Beta Program Resource Center (ni.com/beta), select TestStand 2019 from the list of software, and click Submit.
    2. 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.
    3. 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.

 
A follow up email will be sent when the beta is available for download. I look forward to working with you during this Beta, and please let me know if you have any questions!

Roxy 
Automated Test Software R&D 

↧
↧

Using LabVIEW to check if postBatch.seq within Batch Process Model has finished executing?

January 16, 2019, 4:22 am
$
0
0

Hello all,

I am trying to programmatically enable a button on my user interface when the Post Batch sub sequence has finished executing from the Batch Model.seq.

 

Originally I thought of adding a custom UI message and then programmatically enabling the button when that custom UI message is sent however I would rather not add this extra dependency.

 

Is there any way of checking if the Post Batch sub sequence has finished using the already supplied UI messages from TestStand?

 

Any suggestions would be most appreciated.

↧

Implement buttons in Test Stand Sequence

January 16, 2019, 8:41 am
$
0
0

Hi

I would like to find out how I could implement some buttons within my sequence. I am taking a measurement, if that measurement fails I want the user to be prompted to either 'continue through the sequence' or 'repeat the step' or 'terminate the sequence'. 

 

I have set up my 'if statement' and the three button options 'continue', 'repeat' and terminate', now I need some help to discover how to execute the buttons to do what is mentioned above. 

 

Thanks

↧

How to access CVI UUT Dialog from LabVIEW Module

January 17, 2019, 8:01 am
$
0
0

Object: I want to update custom controls on the parallel UUT Dialog from a LabVIEW module.

Overview: I have a simple TestStand sequence using the Parallel Process Model, and modified the UUT Information Dialog in CVI to graph the values of the UUT during the test. I have successfully added custom controls and can even modify the values of the custom control calling my custom function in the modelsupport2.dll with the C/C++ module.
CustomUUTDialog.PNG
I have validated that the same values are being passed to my LabVIEW VI and my call to the modelsupport2.dll. I am assuming that it has to do something with TestStand loading the modelsupport2.dll into memory and therefore it works calling the dll from TestStand but not LabVIEW.

The custom function currently takes only 2 parameters (int panelId, int testSocketIndex), and I am calling the same dll and function.


Question: How to I call the modelsupport2.dll within LabVIEW to update the the UUT Information Dialog?

Thanks in advance
Matthew

↧

Running multiple sequence on NI TestSatnd

January 17, 2019, 10:30 am
$
0
0

Hi 

I am working on a task in which i need to run two sequence simultaneously, one to run the DUT and other to acquire the data both triggered at the same time. I am begginer to the NI teststand. 

 

Is there a way to trigger both the sequence at the same time?

 

Capture1.PNG

 

Thanks.

 

 

↧
↧

How can I access to the limits of a numeric limit test with TestStand API?

January 17, 2019, 3:03 pm
$
0
0

I need to acces and save all the limits of a teststand sequence and save it to a log file, I export the documentation to a text file but doesn't import the limits just the name and description.

 

I read that I can access to them with the TestStand API, but there's an infinite number of propertys on the sequence context in property node and I don't find the correct one to save the limits. Can it be done with the API?

limits.PNG

↧

how to make container uninitialized container? like for array we have Locals.arrData={}

January 18, 2019, 4:22 am
$
0
0

I am having one container it has complex data like cluster.

It has byte 1 , byte 2, byte 3 ..and so on upto 8.

In one test case it is expected that there will no response from DUT.

And the received container remains uninitialized. like uninitialized array.

In that scenario I want to set expected container container as uninitialized container.

but when I create a local variable in teststand for that container it shall have some numeric value like '0'.

 

 

I know for array we can set as locals.arrData={},

 

Can anyone tell me how to set for container?

 

 

 

 

↧
Search

Errors when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

January 18, 2019, 4:49 am
$
0
0

Hello,

 

I have an issue with a sequence file that I'm trying to move to a deployment environment. The Seq runs great when the LabView adapter is in development mode but when I try to switch to the runtime adapter the following is happening:

1. All VI's will not load so the switch takes hours to analyze and complete loading.

2. I have mass complied all of my Vi's on my computer, (vi.lib, user.lib, instr.lib, my project folder, all directories of the Teststand 2016 directories)

3. LabView or TestStand x64 bit is not loaded on my PC so there is no interaction there

 

I suspect it is a global setting in the environment or something high level like. 

 

↧

Trouble switching adapter from LabVIEW development to runtime engine

January 18, 2019, 5:03 am
$
0
0

Hello,

I'm having an issue on 2 different development machines with switching a seq from development mode to runtime mode in the adapter. The seq runs perfect in development mode but when I switch to runtime mode it takes LabVIEW hours to go through the analysis and then return the error codes for each VI in the sequence. I have attempted the following so far and again this is happing on 2 different development machines.

 

1. Mass compiled everything (vi.lib, user.lib, instr.lib, Teststand 2016 directory, my LabView project directory)

2. Reloaded every VI in the project

 

Below are some screen shots of my environment settings and I'm running LV 2017 and TestStand 2016

 

It must be an environment setting or something. Any help would be greatly appreciated. 

↧
↧

A century of famous business plans some big battery moves

January 20, 2019, 7:43 pm
$
0
0

Toyota plans some big battery moves by 2020.

: in the early 2020s, Toyota and Panasonic will seek to mass-produce batteries at 50 times the current capacity of batteries for hybrid cars, with the aim of reducing production costs by increasing output. Grepow, a big battery maker in China, is also making them.

↧

Terminate & CustomizeReport Callback

January 7, 2019, 5:50 am
$
0
0

Hi All 

When I "Terminate "  a Sequence  in the middle of running  the Sequence stops and Terminate , but the sequence still runs the "CustomizeReport"  Callback and generate a report  . 

How do I prevent  it ?  I don't want to generate a report during Termination .

Thanks 

Benny  

 

↧

frontend.dll is missing

January 21, 2019, 9:42 am
$
0
0

Teststand could not login anymore due to missing frontend dll. It pops a file explorer to find the file but it is not present in the directory. Complete deletion of TS 2016 SP1 folder and reinstallation of 64 bit does not fix the problem and I am not running any custom frontend sequence

 frontend dll on disk.JPG

 

↧
Viewing all 6527 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>