NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Text in Error-Display

Solved!
Go to solution

Hello,

i created in a Labview-Vi an error that is returned to teststand.

Only the black-part in the first line is the error-message that i defined.

 

But: Where is the the text in the red-marked part coming from? It is not coming from labview?

 

Thanks for ideas

 

0 Kudos
Message 1 of 5
(3,315 Views)

Hi,

 

That looks like the text you get from one of the VISA / GPIB function calls and as it says LabVIEW then it must be a labVIEW version of the call.

 

 

Regards
Ray Farmer
0 Kudos
Message 2 of 5
(3,309 Views)

Yes, but there is no VISA-call in the labview-action.

It only returns an error to teststand if one of the inputs is zero.

0 Kudos
Message 3 of 5
(3,296 Views)
Solution
Accepted by topic author OnlyOne

Hi,

 

When a VI returns an error within the error cluster, labview will fillin or append to the msg text some meaningful words found from the default error code database. Somewhere in the VI Properties->Execution you can turn off the automatic error handling, in which case the VI will only return the text defined in the Error Msg string. If its values from 5000, this is where the user defined error codes start. Check out the LabVIEW help on how to enter User Defined Error codes and text.

 

Therefore if you return error code 1 it will probably have some text such as

"An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @." 

 

combined with

 

"Command requires GPIB Controller to be Controller-In-Charge. This error occurs when the board is not the Controller-In-Charge and any board-level function requiring controller capability is called or when any device-level function that affects the GPIB is called and the driver cannot make the board the Controller-In-Charge."

 

for error code 0 you might see;

 

"Error connecting to driver or device. This error might be caused by a failure to find or properly open the GPIB device driver."

 

I hope this helps

 

 

Regards
Ray Farmer
Message 4 of 5
(3,277 Views)

Thanks for this help.

After i changed the error-code to something >= 5000 everything is ok.

0 Kudos
Message 5 of 5
(3,272 Views)