TestStand Sequence Editor message

When TestStand is launched, getting a popup window - 'Value must be at least 0'. What does that mean?
Will it make any effect on test sequence execution?

This is a rather unusual error--I have not heard of it before, so we'll need to do a bit of further debugging to determine the cause. Here are a few questions that might help us narrow this down:
Could you attach a screenshot of the error message?
Does it occur before or after you see the login dialog in TestStand?
Has this always occurred, or did it recently start occurring?
Which version of TestStand are you using, and on which operating system?
Thanks!
Daniel E.
TestStand Product Support Engineer
National Instruments

Similar Messages

  • Teststand Sequence Editor has stopped working

    I get the following message and error code when running my sequence file. This sequence files works ok on another machine. It is a display message to the screen for user input. Software version is 4.2.1
    Teststand Sequence Editor has stopped working. 
    Problem signature:
    Problem Event Name: CLR20r3
    Problem Signature 01: seqedit.exe
    Problem Signature 02: 4.2.1.83
    Problem Signature 03: 4af027d1
    Problem Signature 04: PresentationFramework
    Problem Signature 05: 3.0.0.0
    Problem Signature 06: 4f350630
    Problem Signature 07: 6263
    Problem Signature 08: e1
    Problem Signature 09: System.Windows.Markup.XamlParse
    OS Version: 6.1.7601.2.1.0.256.4
    Locale ID: 1033

    Kingme wrote:
    I get the following message and error code when running my sequence file. This sequence files works ok on another machine. It is a display message to the screen for user input. Software version is 4.2.1
    Teststand Sequence Editor has stopped working. 
    Problem signature:
    Problem Event Name: CLR20r3
    Problem Signature 01: seqedit.exe
    Problem Signature 02: 4.2.1.83
    Problem Signature 03: 4af027d1
    Problem Signature 04: PresentationFramework
    Problem Signature 05: 3.0.0.0
    Problem Signature 06: 4f350630
    Problem Signature 07: 6263
    Problem Signature 08: e1
    Problem Signature 09: System.Windows.Markup.XamlParse
    OS Version: 6.1.7601.2.1.0.256.4
    Locale ID: 1033
    Do your code modules use System.Windows.Markup.XamlParse? Is the process close to running out of memory (i.e. over 1GB of memory used)? Do you have any DLLImprorts (if C#) or any native code (i.e. C/C++) being called by your sequences? Does the error happen every time you run? Always on the same step? If so, what is that step doing? Have you tried to debug the process?
    -Doug

  • Programatically select a step in a sequence in a sequence file loaded in TestStand sequence editor using C#

    Hi all,
    I have written C# code to load a sequence file dynamically in TestStand Sequence editor. The code is as follows...
    myEngine.PostUIMessage(mySequenceContext.Execution, mySequenceContext.Thread, UIMessageCodes.UIMsg_OpenWindows, 0, null, mySequenceFile, true );
    The code is working fine and I could view the Sequence file opened in TestStand Sequence editor.
    Now, I wish to select one sequence in the opened sequence file to get the details of  the sequence programatically. In other words, I want to simulate a mouse click to a sequence and view the steps associated with that sequence.
    Can anybody give some clues...
    Thanks in advance.

    Hi,
    Also I am getting error like "Index out of range. Source:  TSUISUPP.SelectedSteps   at NationalInstruments.TestStand.Interop.UI.Support.SelectedSteps.AddStep(Step val)". Error code: "-17500; Operation Failed." My code is like
    mySequenceFile = myEngine.GetSequenceFileEx(@"D:\dynamic loaded sequence.seq", 0, TypeConflictHandlerTypes.ConflictHandler_UseGlobalType);
    mySequence = mySequenceFile.GetSequenceByName("First");
    Step myStep = mySequence.GetStep(2, StepGroups.StepGroup_Main);
    SequenceContext mySequenceContext = mySequenceFile.NewEditContext();
    mySequenceContext .AsPropertyObject();
    myEngine.PostUIMessage(mySequenceContext .Execution, mySequenceContext .Thread, UIMessageCodes.UIMsg_OpenWindows, 0, null, mySequenceFile, true);
    ApplicationMgr applicationMgr = (ApplicationMgr)myEngine.GetInternalOption(InternalOptions.InternalOption_ApplicationManager);
    SequenceFileViewMgr sequenceFileViewMgr = (SequenceFileViewMgr)applicationMgr.GetSequenceFileViewMgr(mySequenceFile);
    sequenceFileViewMgr.SelectedSequences.Clear();
    sequenceFileViewMgr.SelectedSequences.AddSequence(mySequence);
    sequenceFileViewMgr.SelectedSteps.AddStep(myStep);
    I am sure that my Sequence selected in the Sequence file loaded has more than 2 steps. Please help me in solving this problem and that in the previous post.
    Thanks,
    Biju kuttan

  • How to add a top level menu to TestStand Sequence Editor

    Hi,
    Am unable to add a new top level menu item like File, Edit, Tools, Windows in Sequence Editor. Is it possible to add the same? Can anyone share code snippet to use TestStand API so that a new menu is created?
    Please find the attached snapshot and am trying to add "NewMenu" to SeqEdit. 
    TestStand Version is 4.0 
    Thanks
    Mrm 
    Attachments:
    NewtopLevelMenu.JPG ‏184 KB

    Hello Mrm,
    Adding a new menu is not going to be possible since the source code of the Sequence Editor is not accessible. However, you do have a few options:
    1) Add a new toolbar
    2) Create and entry point (configuration or execution) that will show in one of the existing menus. Here is a KnowledgeBase article that describes this more.
    3) Customize the right click context menus.
    4) Build your own UI or customize one of the shipping UI's (since you have access to that source code).
    What is the overall goal in doing this? Let me know so I can assist you further if needed.
    With warm regards,
    David D.

  • How do I process user command line arguments inside of the Sequence Editor?

    Using TestStand 4.0, how would I go about storing "extra" command line arguments processed from the /runentrypoint command in the Sequence Editor specifically?

    djdewitt -
    TestStand 4.2 does not have this feature; however, we do have an internal issue (#163169) to track this request. You can actually get the commandline passed to the TestStand Sequence Editor using the below psuedo code in a sequence; however, currently the TestStand Sequence Editor displays a prompt when it does not recognize a custom token on the command-line and there is no way to suppress this.
    Locals.AppMgrRef = RunState.Engine.GetInternalOption(InternalOption_ApplicationManager);
    Locals.CommandsRef = Locals.AppMgrRef.CommandLineArguments;
    Locals.CountNum = Locals.CommandRef.Count;
    For i=0 to Locals.CountNum - 1
        Locals.CommandString = Locals.CommandRef.Item(i);
    End
    One suggestion is to use a batch file to write the commands to a dedicated text file and then launch the sequence editor. You can then use a sequence in the sequence editor to read from the file.
    Lastly, I just tried something and I do not necessarily recommend this, but I noticed that the Sequence Editor does not prompt when using the /goto token, so if I use the below command-line, it seems that no prompt appears, the goto command does nothing, and the psuedo code accesses the command-line tokens: 
    "C:\PathToApp\SeqEdit.exe" /goto "location tokens that do nothing" /run MainSequence "C:\PathToSequenceFile\GetCommandLineArgs.seq"
    Keep in mind that NI does not necessarily support this but it does seem to work for now.
    Scott Richardson
    National Instruments

  • TestStand 4.0 Sequence Editor Comments

    We are in the process of upgrading from TestStand 3.5 to 4.0.
    We use mostly Custom Steps and the Comments in the steps are used as "Help" instructions for each Custom Step Type.
    In TestStand 4.0, the comments show up in the Sequence Editor and for us are mostly repeatative. 
    Is there a way to suppress the comments from showing up on the Sequence Editor but still allow reading them in the Step properties? 
    I searched through the Station Options and other system configuration options but can't find anything.
    Mike

    Check out:
    http://forums.ni.com/ni/board/message?board.id=330&message.id=15113#M15113

  • TestStand 3.1 doesn't launch sequence editor

    TestStand doesn't launch sequence editor, it is not coming up with login screen.

    Hi,
    Need a little bit more help.
    Any there any errors generated. Is the TestStand Splash screen seen?
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • Teststand 2010 SP1 Sequence Editor Lauch Error

    Hi, everyone.
    Today I have installed the Teststand 2010 SP1 eval version on Windows XP but an error pops up when I run the sequence editor, as per shown in the attached screenshot.
    Hopefully, someone can help and advise me on this.
    Thanks.
    Attachments:
    Error.JPG ‏16 KB

    Yes, there is an error.
    Please refer to the attached picture.
    When I tried to make active of Teststand 2010 SP1, there is also an error.
    Attachments:
    error4.JPG ‏5 KB
    error5.JPG ‏7 KB
    error2.JPG ‏89 KB

  • Distributed TestStand vs. Sequence Editor

    I am having problems with TestExec that I created a distribution for.  The executable that I created and distributed, will not run, for failing to find or open a DLL.  However, when I run the same sequence using the Sequence Editor that I also included in the distribution, it works fine.  I have checked and it appears that all setting are the same on both the Executable and the Sequence Editor, can anyone explaion this.

    Hi greggj_00,
    Did you follow the directions in this article to include your search directories and configuration in your deployment?  I'm assuming this is a DLL which is called by by one of the steps in your sequence.  Where is this DLL placed on the file system in relation to the sequence file?  Also could you post some more info on the error like snowpunter suggested?
    Justin D
    Applications Engineer
    National Instruments
    http://www.ni.com/support/

  • TestStand sequence error handling

    I have a sequence which calls DLL steps and subsequencies (which also call DLL steps). I would like to know which is the best way to handle DLL error return values. My DLL's return non-zero values on error and also error message string.
    I have configured all my DLL steps as Actions. In the "Post Action" of each DLL step I have set a custom condition: "If Locals.status != 0 Goto destination (end_ERROR)". In each of my sequence I have end_ERROR and end_OK labels at the end. In the end_ERROR block I store the DLL numeric error code and error string to StationGlobal variables (StationGlobals.system_error and StationGlobals.error_msg), which I then display in the Cleanup Group of my main sequence, if StationGlobals.system_error != 0.
    My prob
    lem is basically this: How can I tell the end user the DLL step name which returned error code, and also tell in which sequence the error occurred. Currently I only get error codes and strings from DLL's but there will be so many DLL calls, so knowing the exact location would be usefull.
    I am not sure whether this is the most pratical way to do this. Are there any built-in mechanisms in TestStand to do this? Should I change my DLL steps to Pass/Fail Tests? There seems to be TestStand property RunState/PreviousStep? Maybe I could somehow use this in my end_ERROR label to check where the error occurred.
    Any help would be greatly appreciated.
    BR,
    Timo Sakari

    I'm not sure of the prototype of your dll functions as far as how the error code and message are returned, but there is an easier solution that involves the use of built-in properties of the action steptype.
    When you are "specifying the module" of a DLL Flexible Prototype Adapter step, you can specify that the return value or any output parameter (those passed by reference) can be assigned to the Step.Result.Error.Code property value. You can also specify that if this value falls within a predetermined range it will cause the Step.Result.Error.Occurred boolean value to be set to true. If this property is set to true, the specific step will be marked as causing an error in the report and the error message will be reported to the user as it happens. If you want to
    see examples (including DLL source code examples) that are structured to more efficiently use these properties, take a look at the examples C-DLL based examples in the \Examples\AccessingPropertiesAndVariables.
    For more information on using the DLL Flexible Prototype Adapter (more specifically the parameter settings mentioned above), take a look at Chapter 13 of the TestStand User Manual (available via the Sequence Editor's Help menu).
    Jason F.
    Applications Engineering
    National Instruments
    www.ni.com/ask

  • LabVIEW VI with Report Generation Toolkit elements in a TestStand sequence does not run with a LabVIEW 8.5 Run-Time Engine

    Hi all,
    I am using LabVIEW 8.5.1 and TestStand 4.1. I have done a TestStand sequence with a VI in it, which uses Report Generation Toolkit elements. On my machine I am using LabVIEW and TestStand with a Development System license. On the other machine I am using TestStand with a Base Deployment license and I have chosen the LabVIEW 8.5 Run-Time Engine in the Adapter Configuration. Everything is running well except of this VI with Report Generation Toolkit elements. The error message is showing that the VI is not executable. It works well only after I have installed LabVIEW with an Evaluation license and chosen LabVIEW 8.5 Development System in the Adapter Configuration.
    I have found other posts and a document in the KnowledgeBase with a similar problem: http://digital.ni.com/public.nsf/allkb/8A0E6274D9B​D7B1986256F62006AD402?OpenDocument But I am not using EXE files in my sequence, so I don't know how to solve mine. Anybody has an idea?
    Solved!
    Go to Solution.

    Hello guys,
    thank you very much for your answers!
    @Ruediger:
    I tried to follow the instruction for Method 2 in the mentioned document: http://digital.ni.com/public.nsf/allkb/F3DC40A6E3F​3B25B862570AD005D1D3D?OpenDocument, but the steps on my machine are different starting from step 4. After I click "Continue..." in step 3, I dont get a window, the system just makes a new folder with the same VI. 
    To be honest, I am new to LabVIEW and have some difficulties at this time. What I understood from your reply is, that I need to make a LLB-File, where the files from Report Generation Toolkit are in!?
    @GovBob:
    I was following the instruction in the document: http://digital.ni.com/public.nsf/allkb/9E00E7EFE06​35E678625734600779EFE, but it wasnt working. Can you please tell me how I can check if the VI Server is installed and running on the machine?
    I am using LabVIEW 8.5.1 and TestStand 4.1 on my machine, on the deploy machine there is TestStand 4.1.1. The version of my Report Generation Toolkit is 1.1.2.
    Kind regards, Roman

  • How to call a python script from a TestStand sequence?

    Please tell me how is it possible to call a python script from a TestStand sequence.
    Thank for your help in advance.
    Imre

    Here you can find some information about Python and LabVIEW:
    http://forums.ni.com/ni/board/message?board.id=170​&message.id=124424&query.id=149647#M124424
    If you have LabVIEW, you could use LabVIEW steps to call your Phyton Scipts.
    Another solution would be, to do, what is decriibed in the thread directly in TestStand:
    You can call a dll or .NET assemblies directly from teststand, or use the "Call Executable" TestStep.

  • Preuut and postuut sequences are not executing when run using UI. They run when using the sequence editor.

    I am using TestStand 3.5 and LabVIEW 8 in a Windows XP environment.
    I have a sequence that runs properly when run from the sequence editor.  I have made a few minor mods to the simple Operator Interface that ships with TestStand.  When I run my sequence using the modified Operator Interface, the PreUUT and PostUUT sequences do not execute.  Only the main sequence executes.  This also happens when I run the demo sequences that ship with TestStand.
    What am I missing?

    Hi,
    It sound like you are executing the sequences without the process model, do you get a report at the end of the execution?
    What are these minor mods you have done?
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • Insert menu item blank in sequence editor for new sequence

    In TestStand 2.0.1, when I create a new sequence file using the sequence editor and right-click to insert a step, the Insert menu is greyed out.
    If I open an existing sequence file, copy a step from it, and paste it into the empty sequence, then whatever that step was (let's say Action) becomes available on the Insert menu.
    Is there any way to fix this other than re-installing TestStand? Any idea why this is happening?
    Thanks,
    Gizmogal

    Hi,
    This sounds like you have a problem with your type Palette files in sowe way.
    Check out if you can read the ini files found in teststand\cfg\TypePalettes.
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • Send UI meassages from teststand sequence to Simple CVI Operator Interface with Asynchronous Timer

    Hello,
    Is it possible and how is it possible to send UI meassages from a teststand sequence to the Simple CVI Operator Interface with Asynchronous Timer which could be downloaded from NI Hompage. I use this problems because it is more stable than the standard OIs
    regards samuel

    This post could help:
    http://forums.ni.com/ni/board/message?board.id=330&message.id=7567
    Regards.

Maybe you are looking for