Benchtop Measurement and Test
Distributed Measurement and Control
Systems Engineering Software
Perspectives showcases how NI sees what’s next in the world of test and technology.
You can request repair, RMA, schedule calibration, or get technical support. A valid service agreement may be required.
Provides support for NI data acquisition and signal conditioning devices.
Provides support for Ethernet, GPIB, serial, USB, and other types of instruments.
Provides support for NI GPIB controllers and NI embedded controllers with GPIB ports.
I'm declining this due to lack of community support and the ease of a workaround. Also, a relevant feature was added in 2017 to log any crash info (not exactly the same, but harder to workaround):
Under Station Options, Preferences, add selector for error logging to:
Client SequenceFile Directory
check box for: one file for each error
check boxes for parameters to log:
I think this could be achieve by linking TestStand errors with the generation of OutputMessages. If an OutputMessage was generated for every error then most of the information requested above is already in an OutputMessage.
However a feature to TestStand to log OutputMesages to a file would be needed. Maybe even allow the file path to be specified using macros like the report filename expression to allow different files per execution, thread, category,severity, etc if desired. If feel this option would have the same development effort and provide a full event/error logging capability that could be tailored to suite many applications.
This is really easy to do with a custom result processor that just logs errors. (starting with TestStand 2012). Pretty much just a text style report with a custom filter expression.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What do you need our team of experts to assist you with?
We'll be in touch soon!