Quantcast
Channel: All NI TestStand posts
Viewing all 24566 articles
Browse latest View live

Re: Implement buttons in Test Stand Sequence

$
0
0

So if I understand you correctly, once a step fails you would like the user to be prompted with a dialog box with three buttons. Depending on what button the user selects the sequence will either continue stepping, terminate the sequence, or repeat the step that failed. 

 

You should be able to achieve these features by adding a SequenceFilePostStepFailure callback. This callback sequence will run every time a step in the sequence file fails.

  • Add a Message Popup with the buttons you mentioned
  • Implement an if/if else/else-statement and identify what button has been pressed as Captain_Jack suggests
  • Then add action steps for each case
    • The RunState.Execution Object has multiple methods for you to explore. See Execution for a detailed list.
    • For instance you can call the method Execution.terminate to terminate the sequence, or Execution.resume to continue the stepping.

The KnowledgeBase Article I linked before is good as a reference:

Programmatically Abort Execution upon Step Failure

 

Cheers!

//Marcus Bengths


Running multiple sequence on NI TestSatnd

$
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.

 

 

Re: Running multiple sequence on NI TestSatnd

$
0
0

I threw together a little example that demonstrates this.  Let me know if you have questions.

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

$
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

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

$
0
0

There's actually a built-in way to export limits:

  • Tools » Import Export Properties
  • Choose Export in the tree
  • Fill in a Destination Location
  • On the Property Selector tab, click the filters icon
  • Choose Limit Properties
  • Check the steps/limits you care about and hit Export.Export.PNG

 

If you still want to go the API route, you need to get a reference to the Step object, and there is a limits container under that.

 

Hope this helps!

Trent

Re: Which part of the process model to avoid when changed

$
0
0

Hi,

 

That's what I was concerned about, thank you for your time.

 

Bart

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

$
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?

 

 

 

 

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

$
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

$
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. 

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

$
0
0

sorry I submitted it the question twice. I tried to delete this one since I posted all of the screenshots in the other

Re: Disable sequence analyzer in teststand

$
0
0

Hello,

 

Thanks for the information. My colleague who had worked on a similar issue informed me of the following information. I hope it helps!

 

The programmatic way to disable the sequence analyzer is through the XML file that corresponds to your UI. There is no way to do this through the API, so it will need to be done through a code module. The SeqEdit.xml can be modified programmatically to disable the sequence analyzer before the sequence editor initializes as shown below:

<AnalyzeSeqFileBeforeExecutingOption classname='Bool'> 
<value>false</value> 
</AnalyzeSeqFileBeforeExecutingOption>

 

Note that the file is located in a user-specific file which means that it will change if another user logs in to the machine

C:\Users\%userprofile%\AppData\Local\National Instruments\TestStand 2017\SeqEdit.xml

 

Best,

Ben

Re: Running multiple sequence on NI TestSatnd

$
0
0

Hi Jigg,

 

Many thanks for your example. The system i am working has Test Stand version 2013f1 (5.1.0240). Can you resend the same file for this compatible version?

 

Thanks!

Re: Trouble switching adapter from LabVIEW development to runtime engine

$
0
0

Hey Bill,

 

Have you seen this KB

 

From the error in TestStand, it looks like you have a dependency that is not compiled for LabVIEW 17.0. Depending on how you mass compiled, LabVIEW may not have recompiled that dependency for LabVIEW 17.0. Did you mass compile from the project or mass compile from a directory? 

 

One thing I would recommend doing is building a PPL out of your source code VIs. This can be done with LabVIEW application builder. This should help reduce the load time and help you find where that dependency that's giving you errors is. 

 

Let me know what you find out,

Roxy

Re: Trouble switching adapter from LabVIEW development to runtime engine

$
0
0

I'm mass compiling from the project. It is strange to me that every VI that is used in the TestStand Sequence is giving the same error when trying to convert from development mode to runtime. 

Re: How to access CVI UUT Dialog from LabVIEW Module


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

$
0
0

I want to perform it in a automatic way, so there's not an object reference that point to the step limits in the API.

A century of famous business plans some big battery moves

$
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.

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

Re: How to access CVI UUT Dialog from LabVIEW Module

$
0
0

I should have provided a little more information.

I am familiar with calling DLLs from LabVIEW; however, when I try to call the modelsupport2.dll within LV I get a -4 error/response from the dll(The dll does not return a LV error, this is the response from the dll). I am assuming that is error is because I do not Initialize or call the setup of the dll from LV; therefore the dll is not loaded into memory nor configured correctly for LabVIEW to call it?

So what do I have to do to call the dll from LabVIEW?

Re: How to access CVI UUT Dialog from LabVIEW Module

$
0
0

Hey Matthew, 

 

Can you show the block diagram portion of how you're calling modelsupport2 or share that part of your code?

 

Thanks,

Roxy

Viewing all 24566 articles
Browse latest View live


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