Error Handling Teststand
Contents |
Федерация 中国 (China) 日本 (Japan) 대한민국 (Korea) 台灣 (Taiwan) See All Countries Toggle navigation INNOVATIONEN PRODUKTE SUPPORT COMMUNITY Deutschland Handle TestStand Runtime Errors Publish
Teststand Error Code
Date: Jun 01, 2016 | 6 Bewertung(en) | 4,50 von 5 | Print sequencefilepoststepruntimeerror | 1 Customer Review | Submit your review Overview It is important to consider what will happen in your test if an unexpected error occurs in your test sequence. TestStand provides built-in error reporting, but you can also implement your own custom error reporting mechanism tailored to your needs. Table of Contents Description 1. Description Errors can occur in a TestStand sequence for a number of reasons, most commonly: A code module returns error information (for example a LabVIEW code module returning an error in the error cluster parameter) A TestStand expression cannot be evaluated (for example, your expression checks the value of Locals.myVariable, but this variable does not exist. It is important to consider how these types of errors are presented to the user, and what options they are provided to handle the error. Built-In Error Handling By default, TestStand will display an error dialog when an error occurs, which provides information about the error and allows the operator to decide how to proceed .Refer to the Runtime Error Dialog Box help topic for more information. In addition, TestStand will include the error information in the test report for future reference. Changing Error Handling Configuration You can configure the behavior when an error occurs using the On Run-Time Error option. This option is located in the Execution tab of the Station options (Configure » Station Options). With this option, you can specify to not display the dialog box, and instead ignore the error, terminate the execution, or abort the execution. Refer to the Station Options help topic for more
ForumsCategoryBoardDocumentsUsers 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: Reply Topic Options Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page All Forum Topics Previous Topic Next Topic TestStand sequence error handling TestStand sequence error handling Timo Sakari Member 01-08-2003 11:11 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator I have a sequence which http://www.ni.com/example/27719/en/ 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 https://forums.ni.com/t5/NI-TestStand/TestStand-sequence-error-handling/td-p/70395 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 problem 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 0 Kudos Message 1 of 5 (939 Views) Reply 0 Kudos Re: TestStand sequence error handling Timo Sakari Member 01-08-2003 12:52 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator Just a quick update: I did some hacking and figured out one solutio
(Windows Only) Purpose This example demonstrates http://zone.ni.com/reference/en-XX/help/370052K-01/tssuppref/infotopics/runtime_errors/ how steps in the Cleanup step group can https://forums.ni.com/t5/NI-TestStand/Error-handling/td-p/3329877 gracefully recover from a serious run-time error. Example File Location
ForumsCategoryBoardDocumentsUsers 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: Reply Topic Options Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page All Forum Topics Previous Topic Next Topic Error handling Error handling GrayJoker Member 08-01-2016 08:23 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator When I use the "Action" to call a LabVIEW VI in TestStand, following error appears.How can I deal with this? 0 Kudos Message 1 of 2 (354 Views) Reply 0 Kudos Re: Error handling bienieck Member 09-13-2016 03:48 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator What VI do you try to call?If you try to operate on the non existing array elements you will receive this error.If you want you can ignore run time errors e.g. like this:http://digital.ni.com/public.nsf/allkb/2C3445A795D7771886256B99007AC7F4or in Step Settings > Run Optins > Ignore Run-Time ErrosIt is also possible to use callback:http://zone.ni.com/reference/en-XX/help/370052P-01/tsexamples/infotopics/callbacks_sequencefileposts... Michał BieńkowskiCLD, CTD 0 Kudos Message 2 of 2 (165 Views) Reply 0 Kudos All Forum Topics Previous Topic Next Topic Privacy | Terms of Use | Other Legal Info | © 2015 National Instruments Corporation. All rights reserved.