If you get memory problems, you had to tune your reports options, result collecting, load / unload modules ....
These tasks are very long, you have to point all memory consumers first ... It pollutes your test sequence only for memory purposes !
When you try to modify the result reccording, you will also have problems for your report generation ...
It should be nice to add a new feature allowing an automatic result list removing, after onTheFly reporting, ontheFly database writing have treted them ...
A kind of "OnTheFly and remove unused results"
When ontheFly reporting, and The OnTheFly database writing are over, the treated resultList should be put in a garbage structure !
Older test results could be removed if memory is needed ...
I know this could be not simple ... but this could help very much, for big sequences creation.
Thanks a lot.
Manu.net (TestStand memory dustman !)
It would be nice to have a tool such "Trace Toll kit" for TestStand, in order to be abble to view the currently loaded modules.
When you have big Sequences, with many loops, you can get memory problems.
Then you'll have to play with the load options, the results recording, the on the fly reporting ....
It should be nice to had a tools which could show us the memory used by every modules, structures, Globals, fileGlobals, parameters, locals ...
So it would be easier to point to the main memory consumers !!!!
Or better ... let TestStand access the 64bit world !
Get rid of the ActivX architecture !
Memory management should not influence Test creation ...
Thanks a lot.
This post is just in order to know why there is a user interface available in LabVIEW language (simple or full-featured) suitable for sequential model and NOT for Batch and Parallel models, while these are available in CVI language ?
The customer, who is an allaince member and a famous TestStand user (MESULOG) submitted this idea because he had to translate code from CVI to LabVIEW, and thnik this would be a great thing to add to the next release.
Currently Custom Icon can only be placed under
C:\Users\Public\Documents\National Instruments\TestStand 2014 (32-bit)\Components\Icons
C:\Program Files\TestStand 2014\Components\Icons
and also from
search directory option for icon (New Idea)
If icons can also be loaded in path mentioned search directory, It help a lot in handling things among a large ATE Team (50 Test Developers)
Sometimes it is useful to be able to search for instances of custom data types. Unfortunately, there doesn't appear to be a way to do this in TestStand. It would be really nice if you could search for instances of types in the Types window or perhaps through the Find/Replace utility:
Because of the way .NET applications and assemblies are invoked in TestStand they are a child process of TestStand. This means that they share TestStand's resources. For most applications this is not an issue but if the application or library being instrumented by TestStand is resource intensive this creates a significant problem. In the scenario that served as the impetus for this suggestion we saw performance 1/10 that when running the target application outside of TestStand.
To correct this I recommend the .NET adapter architecture be changed or be able to be configured such that instead of directly instantiating target applications a call to create an object with a .NET adapter would create a separate process that consisted of a TestStand WCF client wrapper process that would host the target .NET process and communicate with the parent TestStand instance via WCF.
Here is a simple block diagram of the intended architecture:
Expressions offer the following exponential and logarithmic functions:
Exp() -> Exponential (base e)
Log() -> Logarithm (base e)
Log10() -> Logarithm (base 10)
Computers always calculating digital. I have to handle binary values very often. Please add the following functions for calculating with binary values:
Exp2() -> Exponential (base 2)
Log2() -> Logarithm (base 2)
The current placement creates confusion about what you’re actually closing out of when you click it. It makes me hesitate and wonder what I am about to close.
If you click it when there are multiple files open, it just closes out of the tab on top. If you click it when there is only one file open, it closes out of the whole pane, including the Sequences and Variables windows.
It would eliminate any ambiguity if the X for each file were on the tab for that file and if there were a separate X for the pane, like you typically see in tabbed programs.
You could also just put an X next to the pin on each little window instead, like the X in the Step Settings pane and the Insertion Palette in the screenshot above.
According to this forum discussion the Flow step types behave different compared to other step types, making customization hard:
Rectifying the behaviour of the Step types may be out of reach as this would dig too deep into architecture.
But there is a lack of documentation of the behaviour of these steps. E.g. just to mention the fact that step type functionality is in those cases tied to the step type name would help a lot.
When opening a version of TestStand which is not the current version, an error dialog shows. It would be helpful if this dialog included a button to open the version selector and/or a button to open the active version.
The settings field can easily become too long to see every active option and there's not necesarily any consistency between steps if they have differing options. What I mean by that is if you only set the "Do Not Record Result" (my favorite) option in one step, it will be on the left of the settings field. But if you now set several options on another step, the settings are not lined up so that it becomes hard to see at a quick glance which steps I forgot to not record (because TS still doesn't default to not recording steps). You have to analyze the settings line for each step.
I propose something more graphical and ordered. Here's my idea of at least ordered. The text could be replaced with icons representing each setting.
Then it would be graphical, ordered, and concise. What more can you ask for?
Can we have the UI show a different status for a disabled socket? It shows the socket as "Completed [Passed]" if I disable a socket when running the batch model. This seems misleading. It should say "disabled" and maybe have a null symbol icon or something to signify that it didn't actually pass any test.
Since not every path on the hard drive can be in the drop down list, and some may be higher up in the tree from paths that are in the drop down list (and some may not be there at all) it would be great if we could specify relative paths and/or environment variables.
TestStand Application Data (for Windows 7) = "C:\ProgramData\National Instruments\TestStand". But, I want to install a file structure starting at "C:\ProgramData". Currently, my only options are to write a custom command to copy the files over after install to some other directory that's in the combo box. But this isn't great because things can be easily left behind on uninstall.
With a relative path, I could specify the subdirectory of to be "..\.." and with Windows environment variable support, I could specify %ALLUSERSPROFILE%. Either would take me to "C:\ProgramData".
Having tried both of these in TS2010sp1 installer builds, neither of these seem to be supported, and it would be awesome if they were in the future.
The Start Modal Dialog VI currently needs to be placed on the block diagram of the VI that needs to be modal. This means that you can't put it in a subVI with logic around it. If a VI reference input were added to the VI (with the default being the calling VI) then you could keep the same functionality but have the option of calling this from a subVI.
For those that are running into this, there used to be a workaround here:
But the link in this forum is now broken. I'll post back if I find the answer.
Right now, you really can't reliably use anything other than a basic ASCII character set in TestStand, which means that some SI units (such as ohms) cannot be represented in their preferred way (with an omega). It also means that you can't put non-english characters in your sequence file and reliably have them show up if your sequence file is opened on a different computer with a different language localization (which causes a huge problem if your customer demands support for non-English languages, and has more than one site -- that speaks a different language -- around the world).
Make TestStand support Unicode, so we can use the full greek character set for things like units, and so we can type characters from any language in our sequence files, and not have them change to a different character if we open them on a computer with a different localization.
Often working with Full Featured UI and Simple UI codes to create custom interfaces for TS, I noticed that the versions shipped with LV2012 are full of deprecated functions.
Also, most of their implementation go against good LV coding rules.
Re-writing them could be a great idea !
Find yourself placing a Sequence Call step and trying to determine the appropriate value to enter for a numeric parameter called "Direction"? Tired of creating sequences with numeric parameters named like the following: "Direction_0_Up_1_Down_2_Left_3_Right"?
The solution is to support the creation of variables with enumerated type within TestStand. Enums could be created as custom variables and then used as wherever a self-documenting variable is required.
Enum type creation:
As seen from a Sequence Call step to a subsequence that uses an Enum as a parameter:
When creating custom step types, it is highly recommended to use Post-Step for calling execution module instead of Default Module.
Thus, when instanciating a custom step type, parameters passing is not saved within the sequence but only in the step type definition.
This allows to change parameters passing without having to update all the step types instances.
In some big test benches, it is intersesting to have low-level step types and high step types based on low level step types.
High level step types execution modules are sequences using low level step types.
Since sequence adapter is not available for Post-Step, we are obliged to call the sequence through Default Module.
Thus it can generate problems when adding parameters in sequence call.
I suggess to allow Sequence Call in SubStep creation :
Jean-Louis Schricke, MESULOG
It isn't uncommon to deploy customized TestStand options, such as search directories, on a deployment computer. It would be much easier to do this if the search directories in TestStand were stored in their own .ini file rather than in TestExec.ini. You can obviously set the search directories in TestExec.ini quickly using the built-in search directories GUI, but when distributing the TestExec.ini file to the deployment computer, you have to be careful that none of the other options contained in the file don't inadvertently cause problems when executing TestStand deployments. A separate .ini file for search directories would clearly remedy this situation.
For the moment the runtime error handling can be managed by using ...
It should be nice to add such a kind TRY CATCH block, in order to modify the error handling in a local section of a sequence.
case 35 // Error code = 35
case default // All other error codes
Doing so, could be a way to handle runtime errors, in an other way that the global configured way.
The TestStand R&D team is committed to reviewing every idea submitted via the TestStand Idea Exchange. However, we cannot guarantee the implementation of any TestStand Idea Exchange submission until further documented.