12-06-2013 05:28 AM
NI uses language files for its custom step types :
These language files include error message strings.
When creating our own custom step types, does NI recommend to use such practice to return specific error messages, even if these custom step types have been developed with LabVIEW ?
If so, since there is no error code in this mechanism, what error code range is recommended (in order to avoid using already affected error codes in LabVIEW or TestStand or Add-ons) ?
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 - 2022)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)
12-12-2013 03:34 AM
–8999 through –8000, 5000 through 9999, or 500,000 through 599,999 as discussed in http://zone.ni.com/reference/en-XX/help/371361K-01/lverror/error_code_ranges/
12-16-2013 03:30 AM
Thanks Kate for these LabVIEW error code ranges.
What about TestStand error code ranges and TestStand add-on error code ranges ?
Our question was essentially about the NI recommandations for using external files for TestStand add-ons...
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 - 2022)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)