TestStand Improvement Whishes

1) Get rid of the "Locals." and "Parameters." prefix from variables lookupstrings in Teststand. Since 90% of the commonly used variables in Teststand are either under "Locals" or "Parameters", it will save a lot of time getting rid of them, and in addition the expressions will get much shorter and clearer.
I think it can be done by keeping the existing parameters and locals tabs in seq editor, but in the lookup strings which have no special keyword in front (eg. runstate, globals) should be considered either locals, either parameters. (locals and parameters can have unique names for eg.)
2) The autocomplete feature in the expresion browser, would be of a greater help if it would work like the "Start menu" in Windows, rather then entering a
"." and then try to pick the nest entry. This will be very helpfull for nested properties.
Thank you.
krs

KRS,
I will join Scott in thanking you for your suggestions. We definitely take customer suggestions very seriously and consider them when deciding which features are included in future releases of the product. However, we do have a process for submitting requests that streamline the suggestions directly to someone in our R&D department. If you go to www.ni.com/contact, the bottom left option is for product feedback. This will take you through a few pages that ensure that we have all the information necessary to understand your suggestion and the reasoning behind. Again, we greatly appreciate ideas on how to make our products better, but I would suggest using this process to ensure that your suggestions go directly to the correct people. Thanks and have a great day.
Adam B.
Applications Engineer
National Instruments

Similar Messages

Logging into teststand slow

I have noticed a change in the time it takes to login to TestStand and to run sequences. Has anybody noticed a longer delay in which TestStand operates. I notice the speed of TestStand improves maybe 10-fold when it is disconnected from the network? (maybe it's just my network is slow)

Check your search paths (Configure>>Search Directories) to make sure that you do not have any network paths in the list. This includes any network drives mapped to a local drive letter. If you must have a network path in the list, move it to the end of the list and make sure you do not select the Search Subdirectories option for the path unless you really need it.

Add-on step types for TestStand?

I am almost certainly reinventing some wheels with Teststand by creating some basic test types.
For example, I just wrote a custom step type for taking an analog measurement from a DAQmx instrument. Surely someone has done this before, and surely someone will want to do it again. There's nothing proprietary about code that simple, and I'd be happy to give it away if there was a place to post it.
Two questions:
1. Is there an open-source repository for sharing custom step types?
2. Are there add-ons for purchase with canned step types beyond those which come with TestStand?
-Arthur

Hi Jigg,
I looked at Averna.com, and I don't see any add-ins available on their website. It looks like they offer services mostly.
It's a good point about TS projects being so varied and customized. However, if custom step types are well architected, as the built-in step types are, then they ought to be reusable by others.
You're right also that I can accomplish my DAQmx steps easily using an Action step with the LV adapter. My motivation for the custom step is to improve the interface for setting up such an action. In particular, when using an IO channel in TS, I have to manually type in a text string for the DeviceName value, whereas I'd like to choose from a list of global names (e.g. with the global channel list control in LV). I can get this affect by using an Enum in a wrapper VI, which maps to an array of channel constants; but this is fragile if the available channels are changed (e.g. added, removed or renamed in MAX).
Additionally, a custom step type is better than a step template for my purposes, because I can propagate changes in the step type to instances of steps throughout the test. This is incredibly valuable to me during development and debugging. It saves me time when I want to update a step that I've used many times throughout a test sequence. Although TS isn't itself a programming language, I find that I expect it to share certain traits with programming languages to facilitate development, such as type abstractions and a strict enforcement of congruency between types and instances. But I digress....
Thanks for your suggestions.

Reporting pass/fail information from threads in Teststand logs

I am fairly new to Teststand. I am just getting started on threading techniques in TestStand. Previously, task A and B were running sequentially. To improve program run time, I am splitting the tasks into thread A and thread B. In the sequential version of the program, task B is running certain steps and logging to a Teststand log file. After I split the tasks into their threads, thread B does not perform the logging feature. Before the thread split, task B would log each error using
RunState.Step.Result.ReportText feature. This logging thread is the last step before thread A and B rendezvous. How do
I enable the logging in Teststand for thread B?

I'm not sure if you need the rondezvous or not without knowing your program design. It may not be neccessary. Any sequence call that calls into a new thread will need a Wait step if you want if you want it in the report. It sounds like you don't need the rendezvous without knowing any more information.

TestStand 4.0 Watch Expression Panel Patch

There is a patch available for TestStand 4.0. This patch improves the performance of the Watch Expression in the TestStand 4.0 Sequence Editor. For more information regarding this patch, please see the Readme.
http://joule.ni.com/nidu/cds/view/p/id/878/lang/en
Message Edited by AllenP on 08-30-2007 01:04 PM

Hi,
The TS is a hidden property of the Step.
You can unhid this property by a setting in the Station Options select the Preference Tab.
You actually dont need to enable this setting, you could of just typed it in (, the .TS.id I mean). But when learning it is handy to see all the properties.
Regards
Ray Farmer
Regards
Ray Farmer

TestStand 4.0.1f1 Evaluation and 4.0.1f1 Patch Available for Download

NI TestStand 4.0.1f1 has been released and is available for download.
This release fixes the incorrect behavior of the Insertion Palette control and Variables View control when used in User Interfaces after .NET Framework 2.0 Service Pack 1 or later has been installed.
If you have previously installed TestStand 4.0.1, you may simply install the patch linked from this KnowledgeBase to fix the behavior. Distributions built from patched development machines will include the fix in their deployments.
If you have not installed TestStand 4.0.1 on your computer, you may install the evaluation of 4.0.1f1 and activate it with your TestStand development serial number. The evaluation includes the fixed components from the patch above. Upgrading from 4.0 to 4.0.1f1 is free and includes many bug fixes and improvements.
TestStand 4.0.1f1 Evaluation Software
If you require this patch for TestStand 4.0, please contact National Instruments Support to request it.
Message Edited by Josh W. on 02-05-2008 09:48 AM
Josh W.
Certified TestStand Architect
Formerly blue

LabVIEW 7.1.1 is the oldest supported version of LabVIEW for TestStand 4.0.
Allen P.
NI

TestStand 4.0.1 Available for Download

NI TestStand 4.0.1 has been released and is available for download.
If you have previously purchased TestStand 4.0, you may upgrade to 4.0.1 free. This version builds upon the improvements introduced in TestStand 4.0 and includes the watch expression patch for 4.0.
TestStand 4.0.1 Evaluation Software
Also, the NI TestStand Type Differ tool is compatible with 4.0.1 so download the Type Differ at NI Labs and tell us what you think!
Josh W.
Certified TestStand Architect
Formerly blue

On Wed, 31 Mar 2010 13:27:32 +0000, Karim C Kronfli wrote:
> Don't Bother, the newer Nokias don't work with GMS, Believe me I have
> tried, wait a little while longer for the Mobility Pack
And of course the technology preview of Mobility is available to download
from here.
http://www.novell.com/promo/data_synchronizer.html
Joe Marton
Novell Knowledge Partner

Change the HTML Report format the same as TestStand 2010 SP1 in TestStand 2012

I have a lot of test steps (~10K) that gets executed and the indentations on HTML report format in TestStand 2012 gets too deep. I have to slide the horizontal bar to the right to see the report when l'm in the middle. I did not have this issue in TestStand 2010 SP1.
Is ther a way to change the HTML Report format (style) the same as TestStand 2010 SP1 in TestStand 2012?

dexrays:
We are currently investigating this issue. In order to help us with the investigation could you post a sequence file and configuration that reproduce the problem? The configuration file is located in C:\ProgramData\National Instruments\TestStand 2012\Cfg\ModelPlugins\ResultProcessing.cfg for Windows Vista / Windows 7 or you can use the Cfg link in the TestStand 2012 installation directory.
You can use the Legacy Model Switcher (included in TestStand 2012) to use the legacy models instead of the new models. The legacy models are more backward compatible, however, this also means that you will not be able to use the improvements in the new models (for example, the new plug-in architecture). If this is acceptable then you can use the legacy model switcher to switch to the legacy models. The Legacy Model Switcher is located in the Start Menu under Programs->National Instruments->TestStand 2012->Tools->Compatibility. For more information on Legacy Model Switcher please read the online help.
Thanks for your report and for your help with diagnosing this issue.
- Francisco

NI TestStand Advanced Architecture Series Has Two New Articles!

The NI TestStand Advanced Architecture Series consists of documents covering topics of interest to advanced NI TestStand developers. The series' authors are NI TestStand architects and developers who provide insightful content that goes beyond basic documentation by offering best practices for large and complex projects. The series will release new documents quarterly so check back to see what's new in a few months!
The NI TestStand Advanced Architecture Series has two new documents offering best practices for large and complex projects.
Best Practices for Improving NI TestStand System Performance discusses best practices for optimizing the performance of test stations developed with National Instruments TestStand software.
Best Practices for NI TestStand User Interface Development explains the best practices to design and develop your TestStand User Interface.
Both articles can be found in the NI TestStand Advanced Architecture Series.
Josh W.
Certified TestStand Architect
Formerly blue

I like the download price!
I've shared this doc with some friends already, thanks for the good work!
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

Job opening in Ottawa: Teststand test software developer. Permanent postion

Averna is an expert in the design and manufacturing of high performance test solutions used by R&D and hi-tech manufacturing companies worldwide. Our goal is to improve and optimize their engineering, production and repair activities. Our solutions accompany our customers through the lifecycle of their commercialized products, from design simulation and software load validation to product functional test and post-delivery troubleshooting and repair.
Responsibilities:
As part of the Engineering team, you will be involved in the development and integration of various software programs for validation systems. These systems are renowned for providing fast data throughput and extreme data integrity, while accelerating design cycles and reducing prototyping costs. The Engineering team develops a range of custom data acquisition systems to help our customers to obtain accurate measurements and results.
Requirements:
University degree or college diploma in electrical engineering, software engineering or physics, Masters degree (asset);
2 to 5 years experience in software development with Teststand (preferably CTD)
Experience in software development with C# or VB.Net is an asset;
Knowledge of LabVIEW (Preferably CLD) is an asset;
Knowledge of the manufacturing environment;
Be comfortable with clients;
Available to travel regularly;
Professionalism, strong communication skills and interpersonal skills;
Team-player, autonomous, self-starter;
To apply:
Please send your resume to [email protected] and mention the title of the position and the code: NI-Teststand-OT.
We will like to thank you for the interest towards Averna, please note that only those candidates being considered for the position will be contacted.

Sir,
Have sent you my CV. Please do check & revert..
Contact No: 9768773040
Regards,
Shilpa.M

Can I reduce the execution time for a step in a TestStand ?

Hi,
I calculated the a single step execution time for TestStand Ver 2.0. It comes to around 20 milliseconds/step. Can I reduce this excution time ?
Are there any settings available for configuring execution time parameters except result logging and exception handlings to reduce the execution time ?

It's difficult to tell how you what time you are reporting for your step. Clearly we don't have control of the time it takes your code to execute. However, we are constantly working on reducing the overhead of calling the code. In addition, you don't mention the type of step you are calling. One way to have a common reference is to use the example \Examples\Benchmarks\Benchmarks.seq. Below have have posted the results of running this sequence with both tracing and result collection enabled and then disabled. I have a 700 MHz, 128 MB RAM, Dell PIII laptop. In this example there is no code within the code modules. You notice that calling a DLL has the least overhead with a minimum of 7.459 ms with tracing and results enabled and 0.092 ms with tracing and results disabled. Although not included below, if I enable results be disable tracing I get a minimum time of 0.201 ms, a 100x improvement on your time.
With Results and Tracing enabled.
7.578 milliseconds per step for CVI Standard Prototype - Object File
7.579 milliseconds per step for CVI Standard Prototype - DLL
7.459 milliseconds per step for DLL Flexible Prototype
8.589 milliseconds per step for DLL Flexible Prototype Numeric Limit
9.563 milliseconds per step for DLL Flexible Prototype Numeric Limit with Precondition
10.015 milliseconds per step for DLL Flexible Prototype Numeric Limit with Precondition and 4 Parameters
7.868 milliseconds per step for ActiveX Automation
8.892 milliseconds per step for LabVIEW Standard Prototype
With tracing and results disabled.
0.180 milliseconds per step for CVI Standard Prototype - Object File
0.182 milliseconds per step for CVI Standard Prototype - DLL
0.092 milliseconds per step for DLL Flexible Prototype
0.178 milliseconds per step for DLL Flexible Prototype Numeric Limit
0.277 milliseconds per step for DLL Flexible Prototype Numeric Limit with Precondition
0.400 milliseconds per step for DLL Flexible Prototype Numeric Limit with Precondition and 4 Parameters
0.270 milliseconds per step for ActiveX Automation
1.235 milliseconds per step for LabVIEW Standard Prototype

TestStand 4.1 Available for Download

NI TestStand 4.1 has been released and is available for download.
If your copy of NI TestStand has an active service and support contract (SSP) you will automatically receive the latest version, or you can download TestStand 4.1 from our website.
TestStand 4.1 Evaluation Software.
NI TestStand Resource Profiler : The NI TestStand resource profiler analyzes test system execution and identifies instruments bottlenecks to help optimize test sequences.
Intuitive Switch Management: With the new Switch Executive 3.0 developers can create switching code more intuitively with a graphical interface for creating new switch connections and routes.
Hierarchical View of Sequences- The hierarchical view displays a graph containing all sequence calls starting at a given sequence or sequences.
Customizable Result Collection: The new additional results step pane allows developers to add any code module parameter to the result list. A new step type facilitates adding properties and variables to the result list.
New Tcl Step Types: The new version of NI TestStand includes integration with Tcl scripts through customized step types that allow developers to call Tcl code stored in a script files or evaluate Tcl expressions. These step types are provided as examples, including source code, allowing customers to customize them for their particular Tcl implementation.
Windows Vista Compatibility: NI TestStand 4.1 supports Windows Vista by running the NI TestStand user interfaces as non-administrator users, and supporting the UI enhancements in Microsoft’s new operating system.
Multicore Support for Parallel Execution: Like LabVIEW, NI TestStand is based on a multi-threaded architecture that can take advantage of multi-core processors. Developers can use the parallel process models to test multiple units in parallel on different processor cores.
Simple Updating of LabVIEW VIs: With the new Update VI Calls tool developers can easily update the prototypes of all LabVIEW VI’s, including Express VI’s, in a sequence
Improved Advanced Step Settings Editing: Advanced step types, such as those for synchronization, now provide configurable panes that allow users to modify multiple steps at the same time and see the outcome of step properties automatically
TestStand 4.1 Evaluation Software.
Josh W.
Certified TestStand Architect
Formerly blue

Hi Thomas,
I agree. On my site there will be only 10+ Testers. This week i have received the 4.1.1. SSP paket from NI. At the monenten they were closed!
From upgrading TS2, TS3, to TS4 i dont uninstalled. I just upgraded. So all versions are present on the maschine !
With VersionSelector i switch through the versions i like and figure out if everything is working well under latest version.
Another thing NI should think about is LabViewVersions and TS:
I have TS2.0 programms that use dll from VC6,8 or CVI6,7,8 in the same file. They run under all new TS versions without any modifications!!
But it is impossible to run vis from LV6,7,8 under the same TS. Well masscompile ! but then they wont run under old stuff.
Well i am not afraid of upgrading TS. But of masscompiling a !!TESTED!! vi to new vi-version.
Greetings
Juergen
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=

TestStand 4.1.1 is now available for SSP customers

TestStand 4.1.1 is available for download. TestStand 4.1.1 includes many bug fixes and some performance improvements. Refer to the TestStand 4.1.1 Readme.html file for information on using TestStand 4.1.1 side-by-side with previous versions of TestStand or on upgrading prior versions of TestStand to 4.1.1.
TestStand 4.1.1 requires activation, so you must have SSP. You can also purchase an upgrade to TestStand 4.1.1. You can download 4.1.1 here: TestStand 4.1.1 Evaluation.
Note: If you use the TestStand Deployment Utility to create installers that include custom commands, refer to KB 4RI8D1T3 for information about a known issue in TestStand 4.1.1.
Josh W.
Certified TestStand Architect
Formerly blue

Hi Thomas,
I agree. On my site there will be only 10+ Testers. This week i have received the 4.1.1. SSP paket from NI. At the monenten they were closed!
From upgrading TS2, TS3, to TS4 i dont uninstalled. I just upgraded. So all versions are present on the maschine !
With VersionSelector i switch through the versions i like and figure out if everything is working well under latest version.
Another thing NI should think about is LabViewVersions and TS:
I have TS2.0 programms that use dll from VC6,8 or CVI6,7,8 in the same file. They run under all new TS versions without any modifications!!
But it is impossible to run vis from LV6,7,8 under the same TS. Well masscompile ! but then they wont run under old stuff.
Well i am not afraid of upgrading TS. But of masscompiling a !!TESTED!! vi to new vi-version.
Greetings
Juergen
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=

TESTSTAND 4.1 VERY UNSTABLE COMPARED TO TS4.0

HELLO ALL,
SORRY FOR THIS .BUT ITS VERY TRUE THAT TS4.1 CRASHES ERYFREQUENTLY COMPARED TO 4.0
AND U DONT HAVE THE SAME FEEL THAT WAS THEIR ON TS 4.0
IT HAS SOME GUI RELATED ISSUES ALSO.ETC ETC WHICH WAS VERY FINE ON TS 4.0
PLEASE IMPROVE FAST OR SEND SOME HOT FIXES

Kulwant,
When you complain of 'seriously degraded' performance, what aspect of performance are you talking about? Is it how long it takes for your application to launch? How long it takes to execute a sequence? How long it takes to display a dialog box?
Is the performance degredation confined to a specific sub-set of functionality? By that I mean, do only .NET steps slow down? Are other steps affected? Does the problem occur only in the Sequence Editor, or in every UI? The more detail you can give us, the better the chance of us being able to fix the problem.
When you complain of the 'GUI behaving unexpectedly' what behavior happens? Is it a hang or a crash? Do windows move unexpectedly? What is the problem you are having?
As far as the TestStand Sequence Editor behaving differently in 4.0 versus 4.1, I was not able to reproduce the behavior that you are describing. I tried creating many blank sequence files in both 4.0 and 4.1, and I got the same behavior in both. Do you have screenshots of the problem?
Also, in case you are not aware, the Sequence Editor display can be customized. You can choose to Tile or Cascade windows in the Window menu, and in Configure»Sequence Editor Options... there are many settings that you can use to change how information is displayed.
Josh W.
Certified TestStand Architect
Formerly blue

TestStand report shows a passing value as a fail

I ran into a possible bug that I'd like to get some feed back on. Attached is a sequence and VI that when run in test UUT every other iterations value for the step (i.e. next UUT) the result is maintained from the last UUT and it show up in the report. Iit is a stripped-down-to-nothing version from the acutal test sequence on the floor with some stuff to simulate the error.
The step does have the ignore error on and this situation happens when an error occurs but I would not expect the previous test result value to show up. Run the sequence and see what I mean. It generated a report that makes my manufacturing floor question the stability of TS.
PS. LV 8.5 TS 4.0
Message Edited by paulmw on 03-04-2009 12:31 PM
Solved!
Go to Solution.
Attachments:
Report Error.zip ‏24 KB
PassAsFail.JPG ‏36 KB

Paul -
The reason are getting failed with a measurement from the last good UUT is because of many compounding issues. The sequence has the default setting of "Optimize non-reentrant calls to this sequence", which basically tells TestStand to cache the runtime copy of the steps in this sequence to improve performance for each subsequent call to the sequence. So the Step.Result.Numeric value will not only be maintained each time you call the step within an instance of the sequence, but now also subsequent sequencial invocations. Next, notice that the report says that you had 10 iterations executed with 0 passed and 0 failed. This means that you got errors on all iterations. Now a looping step reuses the step result as it executes each loop, and the final summary result is a snapshot of the last iteration. Since you are ignoring errors, the numeric value on the step result never gets updated, so the final summary step result is the same as the last UUT. The looping code then sets the loop status to Failed because no iterations passed.
Look at the attached report to illustrate the behavior. The report shows you the results from each iteration as well as the parent summary result.
In general ignoring errors is a bad idea, but assuming that you want to continue to ignore errors, you can do one of the following in order or ease and best behavior:
1) Add a preexpression to set Step.Result.Numeric to a failing value, such as zero or NAN
2) Uncheck the "Optimize non-reentrant calls to this sequence" setting, so that a default value of zero will be used for Step.Result.Numeric
3) Add another step after the one you are running to see if at least one iteration passed or failed.
Scott Richardson
National Instruments
Attachments:
Full Example Report.zip ‏2 KB

TestStand Improvement Whishes

Similar Messages

Maybe you are looking for