Home Community Idea Exchange TestStand Ideas

NI TestStand Idea Exchange

Community Browser
Top Authors
View All
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: 
Post an idea
1 Kudos
manu.NET

Add expressions abilities to the SequenceCall STEP ...

Status: Declined Submitted by Active Participant on 11-24-2011 06:40 AM 1 Comment

Hello,

 

It would be nice to add some more expressions to the SequenceCall STEP, when this one has the "Specify by expression" set to true.

 

I would like to be abble to set the folowing parameter by expressions ...

 

  • Use Current file

 

Manu.net

Labels:
View All (1)
1 Kudos
Perry_S

Save in Previous Version

Status: Declined Submitted by on 10-24-2011 11:18 AM 2 Comment

TestStand can save a sequence file in previous versions but that option is not very evident. Currently when you go to File >> Save As, the option to chose from is "Files of Type". I propose that a change to "Save in Version" or something to that effect be implemented. This change will make things a lot clearer for the user as it will be self explanatory. Another option will be to make it its own menu item under file>>. I hope see this in future versions of TestStand.

1 Kudos
~jiggawax~

Spare Configuration Entry Point in Default Process Model

Status: Declined Submitted by Trusted Enthusiast Trusted Enthusiast on 09-22-2011 11:40 AM 2 Comment

I think it would be a cool idea to put an extra configuration entry point in the Sequential Model (or all the shipped process models) by default.  Inside of it would be a simple call to an empty callback.  This way users can override the callback to get custom sequence file configuration setting. 

 

This would be useful for storing info like: DAQmx addresses, GPIB addresses, etc... off to a file.  Sorta like machine specific configuration info.  That way during execution the file can be read in and used.  However, if it's empty then people can use it for whatever they want. 

 

I understand that I can go in there and edit the process model and make my own but it would be nice to just have the default already there.

 

You could call it Sequence File Configuration or something.

1 Kudos
ATE_Dude_22

Open Reference Identifier

Status: Declined Submitted by Member on 06-23-2011 11:59 AM 1 Comment

Being new to TestStand, this idea may actually already exist, but it would be great if there was a way to show what references are either still open at the end of an execution. I am having the dickens of a time identifying open refernces with very large scale programs, and if the open references overcome TestStand and it crashes, there seems to be no way of finding out why, assuming open references are the major player.

1 Kudos
StephenGerads

Execution Globals

Status: Declined Submitted by Member on 04-19-2011 12:14 PM 6 Comment

globals scoped to an execution

currently I use RunState.Root.FileGlobals as execution globals

but adding a custom global there normally requires modification of the model

Labels:
1 Kudos
EMR

Add API property for User to look up Membership?

Status: Declined Submitted by Member on 02-16-2011 02:51 PM 1 Comment

 

When investigating a specific UserGroup (in the user group list) it is very easy to check the array of Members to find a specific user's name... However, given a specific user, it is a bit of a process to do a reverse lookup and find what group the user is a member of. 

 

While I know that I can always check privileges on specific operations for a user to make an educated guess on what group I belong to, it would be more elegant if I could just access a method or property such as:

 

CurrentUser.Memberof() 

 

and have it return the string for the UserGroup name.  {Operator, Technician, Developer, Administrator etc}

 

 

Labels:
View All (1)
1 Kudos
icastillejos

Execution Object Property

Status: Declined Submitted by Member on 09-17-2010 01:23 PM 2 Comment

This has to be an easy one, could you add a "EntryPoint" property to the execution object that would retrieve the execution entry point. This info is included in the Execution.DisplayName property but it is a little bit of a pain to trim/split the string to get the actual entry point name.

 

Thanks!

 

<< N >>

Labels:
View All (1)
1 Kudos
kekin

Ability to ADD digital signature & PHOTOS to REPORT for both DEFAULT & CUSTOM templates.

Status: Declined Submitted by Member on 08-24-2010 06:23 AM 3 Comment

Since reports are to certify the test results, it would be nice to have DIGITAL SIGNATURE option to give it FORMAL touch.

It will also help in organizations to authenticate the result.

 

It will be also nice to add some PPT or PHOTOS to report to describe the test setup & UUT.

1 Kudos
Eugene12

MySequenceFile About box splash screen

Status: Declined Submitted by Member on 07-22-2010 11:23 AM 2 Comment

Even though we already have an About box for TestStand, it would also be nice to have one for the active TestSequence file as well. The Help menu would have a new item called "About MySequenceFile ...".

 

MySequenceFile About box splash screen:

19679i37712516107E8A41

 

The information in this screen should be loaded directly from a single FileGlobal string whenever a sequence file is made active. This can probably be done already by those that know how, but it should be already part of TestStand by default.

 

 

Eugene

View All (12)
1 Kudos
Eugene12

A TestStand configuration wizard

Status: Declined Submitted by Member on 06-29-2010 10:28 AM 3 Comment

A TestStand configuration wizard

 

I would like to see a TestStand configuration wizard that would walk a developer through a checklist of all of the most important configuration settings and generate recommended changes.

 

It is best for a developer to be already familiar with Best Practices as in the following link:

 

Best Practices for Improving NI TestStand System Performance

http://zone.ni.com/devzone/cda/tut/p/id/7559

 

However, it would also be nice to have assistance in recording WHY certain choices are made as shown in this image:

17669iC6E2378DE5CA3B29

 

 

Eugene

View All (3)
1 Kudos
asbo

Visualization of Sequence properties through the Sequence's icon

Status: Declined Submitted by Member on 06-17-2010 04:42 PM 3 Comment

Everyone should be familiar with the Sequences pane. In it, we get fancy icons for certain callbacks, but I'd also like each sequence reveal more information about the sequence's settings, and my first thought was to use helpful overlays for the icon. If you take a peek in the Sequence Properties dialog, you'll see there's three different tickboxes there that (can) radically change how a sequence executes. Unfortunately, I don't have any awesome ideas on how these could be presented (especially all at once) - it'd be pretty tough to fit all that discernably into a 16x16 icon. Both Comments and Requirements are visualized clearly, but I would just as soon trade the Comment column for a way to display these settings.

 

sequenceicons.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 I'd be even more thrilled if the SequenceCall step type could also find some visual way to display this information, but I guess we should probably take this a step at a time 😉

View All (4)
0 Kudos
SSPTest

Develop a tool to migrate TS2017 Custom Python step type to TS2019 built-In python step type

Status: Declined Submitted by Member on 05-20-2024 10:25 AM 1 Comment

Several Customers may benefit from a tool that can be able to migrate TS2017 Custom Python step type to TS2019 built-In python step type.

Some TS sequnces may have hundreds of sequences and test steps that required a lot of work for the migration.

Labels:
View All (1)
0 Kudos
TiRodrigues22

Labview Error in Test Stand

Status: Declined Submitted by Member on 01-15-2024 05:38 AM 1 Comment

Hello all,

 

I'm starting to do some Test Stand sequences, and I'm having a Fatal Error that is always forcing me to close the program. This error always happens in the first run and I just can avoid it by deactivate and activate one option in the adapters configurations tab.

 

The error that I'm having is the next one ->  "labviewv.lib was unable to locate a suitable location to resolve "MGApp". This may happen when too many instances of labview have been loaded into the same process."

 

Can someone help me to correct this error?

Labels:
0 Kudos
Mario_Diaz5551

Modificacion de variables en un vi.exe

Status: Declined Submitted by Member on 05-28-2021 04:18 AM 1 Comment

Hola

 

Estoy haciendo un proyecto, que basicamente son rutas o accesos directos a URLs en linea

 

el detalle es que, me gustaria que en mi programa pudiera modificar los URL cuando yo quiera, aun estando ejecutandose el programa

 

esto, porque si llegase a cambiar el link al que me quiero dirigir, lo pueda cambiar desde el el mismo exe sin necesidad de volver a hacer el programa

 

NOTA: los URL los tengo ya registrados en el bloque de diagramas

 

Saludos.

Labels:
0 Kudos
Beutlich

Save As Previous Version for Deployment Utility

Status: Declined Submitted by Member on 03-14-2019 10:03 AM 1 Comment

If you create a *.tsd file, there is no way of reverting back to older formats of the deployment utility. We should have a Save As feature for converting these build definitions to older versions of TestStand, just like the Save As feature for normal sequence files.

0 Kudos
gooohestpoo

Hide skipped stuff

Status: Declined Submitted by Member on 12-19-2017 06:09 PM 3 Comment

Hi,

 

Test tand is very useful to me and always feel thanks. Nevertheless sometimes I feel that how about hide skipped steps, sequence and something like that. If there is a function of "Hide skipped step or Hide skipped all", I will obviously use them every 50 times. 🙂 

How do you think about this suggestion?

 

Thanks in advance.

Labels:
0 Kudos
dshao

Test TamTam plugin to support TortoiseSVN integration with TestStand

Status: Declined Submitted by Member on 02-21-2017 09:09 AM 1 Comment

TortoiseSVN is an easy to use Source Code Control tool. However, it needs a MSSCC API plugin in order to be integrated with TestStand. On NI web page, PushOK is listed as a tested plugin with TortoiseSVN by NI tech team. PushOK is made by a Russian company. Another AgentSVN plugin is made by an Australia company. From an end user perspective, the time zone difference will cause some difficulty to access tech support in case it is needed. I used TamTamSVN 1.4.9 plugin for TortoiseSVN integration with TestStand and it worked fine. TamTamSVN plugin is made by an US company located near NYC area. I will suggest NI Tech team to test TamTamSVN plugin for TortoiseSVN integration with TestStand to ensure its features and functionality are acceptable to NI applications. If it pass the test, please add it into tested list. 

Labels:
0 Kudos
vanisivanantham

TestStand Deployment Utility: Support VIs issue

Status: Declined Submitted by Member on 09-02-2016 01:28 AM 1 Comment

Hi All, My code module to be deployed uses some VI's from user.lib. When I'm trying to create the deployment, in LabVIEW options I'm excluding all files from vi.lib,user.lib and instr.lib. After creating the deployment, still my code module looks for the VI's from user.lib in SupportVIs folder which is parallel to the deployed folder. I don't know why it is still looking in SupportVIs folder instead of taking it from user.lib. Please share your thoughts about this.

 

Thanks in advance!

Regards,

vani

0 Kudos
csduetto

HW query capability in Sequence File

Status: Declined Submitted by Member on 08-23-2016 07:29 AM 1 Comment

For one of our test racks we have a PXI Rack that is full of Measurement HW devices from NI.  Recently tow of the cards in the rack were returned to us from the calibration house with OOT (Out of Tolerance) as found readings.  This put into question the product tested and shipped in the past year.  Since the test fixture is used to test 14 different assemblies, I wanted to use Teststand to generate a report that told me what hardware was being utilized during the sequence of each assembly that is tested on this fixture.  It appears that unless one intentionally adds certain system configuration information into the VI that can be read in as a variable in Teststand, that this process will be very tedious in looking at each vi called out by the sequence file and looking for HW callouts.  It would be great to have this capability baked into the handshaking between VI's and Teststand to allow for a simple query within TestStand.  c.S.

0 Kudos
MimiKLM

Developers should be able to edit the sequence file whilst executing.

Status: Declined Submitted by Active Participant on 05-21-2015 06:09 AM 3 Comment

Hi,

 

Why the edit sequence file functionality is disabled during execution?

 

I think that developers should be able to edit the sequence file in sequence editor whilst the file is executing.

Labels:
View All (4)