TestStand Error

I get the following error when starting TestStand. Any suggestions on how to clear it, other than reload TestStand? I tried opening SequentialModel.Seq in the sequence editor and resaving it.
Cannot load the sequence file's model entry points.
Type 'TElnf' is invalid because it conflicts with the existing type of that name. To avoid this error message, you should open the file
with the type conflict in the Sequence Editor and resave it.
Error accessing item 'Action.TS'.
The sequence file 'C:\TestStand\Components\NI\Models\TestStandModels\SequentialModel.Seq' could not be loaded.
Error Code: -17329, Invalid type - conflicts with an existing type.
Source: 'TSAPI'

Hi,
Nemo anwers this query which looks too be related.
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=50650000000800000091410000&ECategory=TestStand
Regards
Ray Farmer
Regards
Ray Farmer

Similar Messages

Pass TestStand error type directly into function parameter

Hi,
I am using TestStand 4 and Labwindows CVI 8.5.
I wonder if it is possible to pass Standard Step error type into CVI function parameters.
I think it would be more simple to pass one parameter instead of passing Error code, Error occurred state and Error message into function prototype.
I tried to use tsErrorDataType struct defined into tsutil.h into my function prototype.
In TestStand, I pass Step error type into function parameter but it does not work.
TestStand displays an error meaning parameters does not match function prototype.
Thank you for your help.

Hi Tartempion,
In order to pass the TestStand Error Container as one parameter to a function in a CVI DLL, you must use a struct that is typedef'ed and create an .fp file that is included as a type library for the DLL. When you create a .fp file to add to a DLL, the DLL will not build unless all structs/enums are typedef'ed. Thus, I wouldn't advise using the tsutil.h because you would have to go through and typedef every single struct and enum in the header file.
Instead, you can simply create a typedef'ed struct in your projects header file and create an .fp file with the struct specified as a data type. Then in TestStand, when you call the function you would need to ensure that the parameter is of Category "C Struct", and type "Error". The attached zip file contains a CVI 8.5 project that demonstrates this along with a TestStand 4.0 sequence file that demonstrates how to pass the parameter to the function by reference. In case you run into trouble creating the .fp file please refer to the following KnowledgeBase. The instructions are for enums but easily correspond to structs as well:
TestStand and LabWindows/CVI Enumeration Data Types
Hope this helps!
Manooch H.
National Instruments
Attachments:
PassTSError.zip ‏19 KB

Teststand error states that a vi failed to load in the Labview Run-Time Engine

I am getting an error in teststand that states that a vi failed to load in the Labview Run-Time Engine version '14.0.1'
If I look at the software loaded on my system with the NI Measurement and Automation Explorer I have Labview Run Time engines for version 2009, 2010, 2011, 2012, 2013, & 2014 on my system.
How do I get this VI to run on this system when it is called by test Stand?
Thank you

The RTE 14.0 was loaded as part of my deployment and after I ran this I got an update notice for the F1 patch which I also loaded.
I do not have labview loaded on this system, only the run time engines from running my deployment.
When I launch t he teststand sequence, when it calls the labview VI, I get the following error moessage:
Error: Failed to load VI 'C:\builds\RelayVoltageMeaure.vi' in the LabVIEW Run-Time Engine version '14.0.1'. LabVIEW: The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it. VI Path: C:\builds\RelayVoltageMeaure.vi[Error Code: -17600, Failed to load a required step's associated module. ]
I have attached the teststand sequence if this helps.
Thanks
Attachments:
QuantumDigitalBd.seq ‏13 KB

TestStand Error -17300 while deleting a step

Hi All,
I have created a custom step which gives a LabVIEW pop up on dropping it in the sequence editor. The pop up has an OK and Cancel button. If I hit OK, the step is placed in the sequence and if I hit Cancel, the step is deleted from the sequence. I am doing this by passing the sequence context into the popup vi and then using the sequence method Delete Step.
Now when i do this practically, the step is getting deleted but after that I'm getting an error from TestStand with Error code -17300. Source: 'TSAPI' "Value invalid or out of range".
Can anyone tell me how to resolve this error. I am using TestStand 2010 and LabVIEW 2010
Thanks and regards,
Nitz

This is likely not an anticipated or supported use case. What is likely happening is that TestStand is trying to select the newly inserted step after your substep is done running, but since you deleted it, it does not exist so it gets an "out of range index" error.
I can't think of a good way to fix this short of writing your own code to do the step insertion. The easiest solution probably is to not do the delete when cancel is pressed, but instead to put the step in a state such that it will always generate a runtime error if used without being specified appropriately.
I have recorded this issue as a change request in our tracking database.
-Doug

TestStand Error when using Waveforms

Attached is the error I get. I'm also attaching a labview type def. For some
reason, when I have an array of these clusters in a vi for a custom step type,
when I go to the module adapter and try to assign this array to a station
global I have, when I click on the default checkbox, it throws the error.
What do you think?
Thanks,
Jamie Olive, Randall Consulting Services
- Capture.JPG - Capture2.JPG - PT3838.ini - Get Measurements for Array.vi -
ArrayControl.ctl - ChannelStatus.ctl
Solved!
Go to Solution.
Attachments:
Capture.JPG ‏33 KB
Capture2.JPG ‏61 KB
ChannelStatus.ctl ‏10 KB

Hi JamieO,
I've tried to replicate your steps on my computer and did not see any error. Here is what I did.
1. Place the .ctl file into an array in a blank LabVIEW VI.
2. Use the Connector Pane to specify the array as an input.
3. Add an Action step to a blank TestStand sequence file with the VI specified.
4. Create a new Station Global of type Array of Container.
5. Uncheck the Default box on the Module tab for the input parameter of the Action step.
6. Specify the Station Global as the input.
Please let me know if this step list is accurate for your situation. Also, please answer Anand's questions and let us know what version of TestStand you are using. Provide a .seq file that shows the behavior if possible.
Thanks,
KyleP
Applications Engineer
National Instruments

Teststand error handling Option

Hi all,
I am looking for a way that when a step get error, Sequence will not be terminated but continue to run other steps.
I found no error handle option to fit my need as the below. Value 1 seems to be good but it terminated the sequence. Value 2 sumary test result validate as good which is not useful. is there any way I can change the error handle structure?
RTEOption_Abort–(Value: 3) Instructs the execution to abort the execution.
RTEOption_Continue–(Value: 1) Instructs the execution to process the error by propagating the error to the calling sequence, if one exists. If the current step group is Setup or Main, the execution jumps directly to the Cleanup step group.
RTEOption_Ignore–(Value: 2) Instructs the execution to ignore the error and continue normal execution.
RTEOption_Retry–(Value: 4) Instructs the execution to ignore the error and re-execute the step that caused the error condition. For the StationOptions.RTEOption property, the Execution.RTEOptionForThisExecution property, and the Thread.SetBatchRTEOption method, TestStand interprets the RTEOption_Retry value as RTEOption_Continue.
RTEOption_ShowDialog–(Value: 0) Instructs the execution to launch the Run-Time Error dialog box when an error occurs.
Purpose
Solved!
Go to Solution.

You could use the SequenceFilePostStepRuntimeError callback and handle errors if you need to do something custom.
An example ships with Teststand which will give you some pointers.
http://zone.ni.com/reference/en-XX/help/370052K-01/tssuppref/infotopics/callbacks_sequencefilepostst...
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

Deployment teststand error (labview test - sequence context)

Hello,
I need help by deploying my workspace to the deployment(target)computer. That is what I have done:
- i create a workspace, in this workspace are different sequence files and the vi´s which i have created.
- then i use the deployment tool (teststand) and deploy the workspace to a directory in the network.
- after that i copy the modified SequentialModel.seq to the target maschine.
- now if i want start the sequence file an error occured. Teststand can`t start my vi´s because it can`t find files like LabVIEW Test - Sequence Context, TestStand - Set Property Value (Boolean Array). Choosing the path of the file in the search directory doesn`t help.
Maybe i have made an error with the deployment tool?! How is the right way to deploy in a network without using an installer. Iám using teststand 3.0.
thankyou
Schwede

Hi Schwede
If you want to deploy your Sequence File and the Processmodell you have to copy first your original Processmodell from the NI folder to the user folder.
Than open the deploy-tool and load your workspacefile. Mark the point "deploy files in Teststand user directories" and define the image path. Don't mark the "create installer" field.
You will get and image folder with several subfolder.
In the target subfolder you can find your sequencefile. In the Teststand subfolder you can find your customized Processmodell or Operator Interfaces. Attention, please use relative paths when you create your workspacefile.
hope this helps
Manuel Wielander
National Instruments

Java teststand - Error 1500 Cannot find class

Hi everyone,
I am using TestStand 2010 and Java 1.7.
I try to add a java class in the Computer example folder, and call the method.
The java class is simply like below, because I just want to try calling my own java class.
I have set the Class Path in Start JVM to the directory where the Computer example (which is also the directory where I put my java class) are located.
TestStand can call the Computer's methods, but not mine (got error Error 1500 Cannot find class). I put my my java method calling among the defaults Computer example calls.
Furthermore I have read similiar threads but still I cannot solve the error.
Where is the part I miss, actually? Please share some insights.
Note: I even try to leave the Class Path empty, but TestStand still can call the Computer's methods. Why?
public class TestJava {
public static void main(String[] args) {
public String returnString(boolean a){
return "success";
Solved!
Go to Solution.

In order to load a class that is inside a package you have to use the package notation (or modify the example in order to use it). The path to the class is passed directly to the JVM in order to load the class, but really what is needed is the package from the class path including the full path to the class.
That means you have to do the following:
1. Set the class path to the base directory where you built all your classes, if you have the following structure:
MyFile.java
builds
MyPackage
MyFile.class
You have to set the classpath to the builds directory
2. When you configure your steps, you have to set the path to the class in your Java steps to MyPackage/MyFile.class (note separator is a slash, not the usual Windows backslash, so the browse button doesn't quite help with that).
Another important thing is that when you set the classpath you are deleting the normal class path in Java, if you are using Java classes from the default libraries you might have to add <jre directory>\lib\rt.jar

TestStand Error -17000

TestStand will abort after showing error codes.
My Teststequence open, execute and close a communication channel (RS232) via a C++ DLL very fast.
My Sequence is used to read out some parameters from my DUT.
The error occures mostly on creating the (XML) Report. there are many values to log.
CAN you explain me the errors attached into the JPG Files?
Thanks
Robert
Attachments:
SeqEdit.jpg ‏29 KB
SeqEdit_2.jpg ‏29 KB
OperationFailed.JPG ‏33 KB

duplicate message http://forums.ni.com/ni/board/message?board.id=330&message.id=21084&jump=true
Regards
Ray Farmer

TestStand Error only when using Operator Interface

My testStand sequence runs correctly when I run it from the seqEditor, but when I run it from our Operator Interface (modified version of the simpleOI example), I get the following error,
"Error Message: Parameter 'Input Files': System Level Exception. [Error Code: -17502]
Input Files is a parameter of the LabView vi being called, and is an array of strings. The VI executes correctly even when called fromthe OI, but when it returns to TestStand (when called from the OI) the error occurs.
Thanks for any info and help on this. Also any info on why the simpleOI would cause an error would be appreciated too.

Hi Ray,
Here are some answers to your questions.
This VI that error's, is it part of the simpleOI or part of the Sequence File being run by the simpleOI?
---- The VI is part of a sequence file that is called by the OI.
If it is in a Sequence File, does this run in the default OI?
---- No, it's part of a new set of test sequences for our equipment.
What does the simpleIO do with the data contained in Input Files?
---- The data is just passed to another VI to load our input vectors.
What version's of TestStand and LabVIEW are you running.
---- I believe it's LV 8.5.1 and TestStand 4.0
What sort of modification have you done to the simpleOI example?
---- I think we only added our new sequences, a Operator info popup, and a few more buttons (Pass/Fail light, Change Op Info). And we removed some unused code to make it more simple.
Thanks again for your help.
Billy

[HELP] Teststand error when using labView runtime engine...

I have an extensive TestStand 3.5 project which I am working on. This project uses a large number of LabVIEW 2012 VI’s. (Note: The version of TestStand cannot be changed). When TestStand 3.5 LabVIEW Adaptor is configured to “Development System (Active Version: 12.0)” all the sequence run and perform as expected.
When I change the TestStand 3.5 LabVIEW Adaptor is configured to “LabVIEW Run-Time Engine 12.0” then I get an -18002 error in the first VI called by the sequence and nothing runs. Now this sequence contains a standard library VI in it “Check if File or Folder Exists.vi”.
From research I realised that I needed to deploy the software properly. So created a LabVIEW project with all the sequences and VI’s in it and a “Source Distribution”. I also unchecked “Exclude files from vi.lib”, “Exclude files from instr.lib”, and, “Exclude files from user.lib”. After building the project I get a “data” folder full of VI’s and control files (273 of them).
Next I created an “Installer” and added build to the correct place. I can see the “data” folder in the source files section.
When I install this distribution kit on a PC, which happens to have full LabVIEW 2012 development on it, all the files install but the “data” folder is missed out!!!
If I then attempt to run the installed top level sequence I get the same -18002 broken VI error as before. If I manually copy the “data” folder into the same place as it was built it makes no difference.
Anyone got any suggestions?
Christopher Povey
Senior Test Systems Engineer for BAE Systems.

Bit of additional information:
I created a blank LabVIEW 2012 project. To this I added one VI which included a call to "Check if File or Folder Exists.vi". Then added one TestStand 3.5 Sequence which contained a call to the VI above.
I then added a build to the project and built the project. This resulted in a folder with the sequence file, my VI and a Data folder containing the "Check if File or Folder Exists.vi". When I tried to run the TestStand sequence with LabVIEW Run-Time Engine selected it failed as before.
Next I added another LabVIEW step to my sequence calling "Check if File or Folder Exists.vi" from the "Data" folder. It then worked!
I then modified my VI and added the MD5 checker VI (forget the exact name). It added some files to the dependences in the LabVIEW project. I rebuilt it and ran it again and again it worked. I did not need to add the additional VI's in the "Data" folder to the sequence file.
If I remove the LabVIEW step to my sequence calling "Check if File or Folder Exists.vi" though it breaks again.
This is not ideal though as it is a bit chicken and egg. In order for the project to work I need to add one of the VI's from the generated "Data" folder into a sequence in the project, but I can't do that until I build the project to create the "Data" folder!
Christopher Povey
Senior Test Systems Engineer for BAE Systems.

LabVIEW new "Silver" error cluster and TestStand

I have some new VI's that use the new "Silver" style error controls and indicators. I started calling the VI's from TestStand and noticed that the new VI's were not auto populating the TestStand error to the VI's error out. Not sure how this mechanism works but it doesn't work with the default "Silver" controls. I think it is name based case sensitive and I just have to rename the "Error Out" cluster to be lower case "error out".

Paul -
Can you confirm that the problem you're describing is that because the name of the Silver error cluster is "Error Out", when you configure a LabVIEW step to call a VI that has the Silver error cluster wired to the connect pane, TestStand does not automatically assign Step.Result.Error to that parameter? If so, we have reproduced this behavior and yes, you are correct that it is due to case sensitivity. We have taken note of this in order to fix the problem in a future version of TestStand.
I also just wanted to confirm that the problem is not that the error information is not correctly passed from LabVIEW to TestStand, when you assign Step.Result.Error to a Silver error cluster parameter.
Please let me know.
Manooch H.
National Instruments

Problems with multiple TestStand versions on the same computer

I installed LabVIEW 2014 and TestStand 2014; then later I installed TestStand 2010 SP1 and have been using it since. (I also updated LabVIEW 2014 to 14.0f1; I think I did that after installing TestStand 2010 SP1.) Is this "legal?" I have been seeing strange behavior with TestStand 2010 SP1:
- if I type in any expression text boxes in the Sequence Editor (e.g., for a pre-expression), I periodically get an error dialog as I type:
"The .NET support dll could not be loaded. This is caused by an assembly path that could not be resolved. Error Code: -18700, The .NET support dll could not be loaded. This is caused by an assembly path that could not be resolved! Source: 'TSAPI'
After I acknowledging the dialog, I can contine to type a little more before getting the dialog again, but it doesn't seem to invalidate anything I type.
- If I open the Simple LabVIEW Simple User Interface that ships with TestStand 2014 while TestStand 2010 SP1 is active, LabVIEW immediately crashes. I can open all the subVIs without a problem, but the top-level VI always crashes LabVIEW.
So I used the TestStand Version Switcher to make TestStand 2014 active, opened the top-level Simple UI VI, and deleted all the UI controls. Then I switched back to TestStand 2010 SP1, and then I was able to open the top-level VI. I added back the TestStand UI controls to the VI, and now the VI runs. But many operations return a TestStand error dialog, such as Close Execution ("Value invalid or out of range [Error Code: -17300]"), Logout ("Cannot find item to select in ComboBox [Error Code: -2147467259]"), and (critically) Exit ("Operation Failed. Error Code: -17500]") and the X in the upper right corner of the window ("Operation Failed. Unknown System Error in <VI name>"). So I can't exit without killing LabVIEW.
These two issues may be unrelated. But maybe installing an older version of TS after installing a newer version is not a valid use case? Is the ActiveX error a result of this? Should it be possible to use a (simple) UI written for a newer version of TestStand be able to work with an older version of TestStand?
I have another issue that is probably unrelated, but I'll bring it up here just for completeness. If I right-click on a LV property node or invoke node for a property or method from the TS API and ask for help for the property or method, a command window flashes briefly before showing the TS help window with the top-level item selected (i.e., it doesn't take me to the help for the selected property or method). I have this problem with either version of TS active, and I saw this problem even before I installed TS 2010 SP1. I seem to recall having this problem once before, but I can't find the solution. I don't know if this problem is an indication of some other larger problem.
For what it's worth, I am running WIndows 8.1 on a virtual machine.

Thanks for the information, Doug. Maybe the ActiveX error dialog I get while in the sequence editor is related to the fact that I'm running an unsupported operating system.
So using a UI that was created in a newer version of TS is not supposed to be able to run with an older version of TS. Is there any way to enforce this (like having a dialog appear informing you of the incompatibility when the TS engine is loaded) and avoid an immediate crash? (Maybe the crash has to do with the incomaptible OS as well.)
Is there a way to "relink" a UI to an older version of TestStand? Can you just relink all the ActiveX reference controls/constants to the TS ActiveX servers? As far as I can tell, everything I am trying to do with the new TS version should work with the old version. And also, as far as I can tell, the TS version switcher changes the version of the available ActiveX server; so unless my UI uses a feature unavailable in older TS versions, I would think it shouldn't know the difference. (I'm making a lot of assumptions in that last statement, so I may be totally wrong here.)
Thanks,
Jeff

"please wait while windows configuers NI teststand 3.1"

hi ,
when I open teststand 3.1 it will happen a dialog that show
"please wait while windows configuers NI teststand 3.1"
and never stop if you don't cancle it
so it is virus or miss some files,can you tell me.
Attachments:
teststand error infor.JPG ‏12 KB

That's the Windows installer auto-repair dialog. Your installation of TestStand might have gotten corrupted. You could try manually repairing it with the add/remove programs control panel.
-Doug

Error viewing variables tab after running edit UI

Hi,
I have a problem that seems to be somewhat like this:
http://forums.ni.com/t5/NI-TestStand/Error-viewing-variables-tab-in-Runtime-Operator-Interface/m-p/1...
The VI I am trying to run is an edit substep of a step type. LabVIEW checks to see if the "Step.Setup.ReadMeasName" property exists, populates a listbox with it if it does. Another listbox with all the available measurement names also appears on the UI. The user has an Add and Remove button to remove measurements from the "ReadMeas" listbox or add them to it from the "MeasNames" listbox. Multiple names can be added/removed at once depending on whats selected when the buttons are pressed. Once "Done" is clicked the VI writes the"ItemNames" property of the "ReadMeas" listbox to "Step.Setup.ReadMeasName", using a Set Property Value node which is passed the TestStand Sequence Context. If the property doesn't exist it creates it.
The only time I have any problem is when I try to remove items from the property after it is already initialized (i.e. not empty). In other words, if I run the VI from teststand, put several measurement names into "ReadMeas" click done, run the VI again (the names already added appear in the box when the UI comes up, LabVIEW reads "Step.Setup.ReadMeasName" ), and then remove some of the names. IF I had "ThisContext.Step.Setup.ReadMeasNames" opened in the step "Variables" tab when trying to remove the names this message appears in the Variables tab: "One or more errors have occurred. Please Save your work and restart the application." If I make sure not to have "ThisContext" expaded in the variables tab, but check the property before and after removing names from the list it does work properly and there is no error.
This isn't a big deal becuase I doubt the end-user will be checking to see that the property actually got populated, but I still would like to fix the bug if possible. I've installed the patch for TestStand 2010, and the .Net framwork 4.0. Anyone have any idea what could be going on here?
Thanks,
-Josh
Solved!
Go to Solution.

Josh -
It looks like you're running into a Known Issue 193751, which is documented in the TestStand 2010 and 2010 SP1 Known Issues List. This is an issue that we intend to fix in a future version of TestStand.
I hope this helps and am sorry for any inconvenience this issue may be causing you.
Manooch H.
National Instruments

TestStand Error

Similar Messages

Maybe you are looking for