Why can not I get error message when using errorMessage.vi of various instrument dirver?

[yangyang-rexxar]

Hi all

I have a strange situation when I call "errorMessage.vi" in various instrument drivers.

If we use an instrument driver which delivered by vendor always has a group vi to operate instrument such as "init.vi","open.vi","close.vi" and usually a "errorMessage.vi" to deal with "error status code" which has been transferred by other VIs and translated by "errorMessage.vi" as an user readable string. e.g. if "init.vi" pass a code "-107354001" and "errorMessage.vi" accept this code and popup a "check your instrument connection."

Just not only when using Agilent drivers but also occur in other instruments.

Please have a look for the attachment1, when I push the statuscode from "initilize.vi" to "errorMessage.vi" the message port show nothing for me, but if not connect the "errorMessage.vi" to accept the statuscode, LabVIEW show a popup message give a right statuscode and message, this is not my expected way to show message, I do not to use LabVIEW warning message, I just want to show the message on UI.

I can use "initialize" and "errorMessage" very well in LabwindowsCVI, the "errorMessage" function show me right message, LabVIEW invoke the same dll, why not show the message on output port of "errorMessage.vi"

[Dennis_Knutson]

To use the error message function, you have to wire the error code input. Unbundle it from the error cluster. Look inside the VI and you'll probably see that it is the code and not the error cluster that is passed to the dll.

[yangyang-rexxar]

Hi Dennis

I ensure that I have tried the two methods and can not get right message.

Please have a look at attachment, whether I pass status code or unbundled error cluster to errormessage.vi, I can not get the errormessage output.

If you have an instrument driver no matter what is it, please have a try and give me a successful screen shot,

Thanks very much

[Dennis_Knutson]

I have no idea what you are passing in ErrorMessage1.jpg. It kind of looks like it's a number from thje Initialize function but they don't typically return a number. Like I said, try unbundling the error status.

Message Edited by Dennis Knutson on 01-21-2007 06:20 PM

[Liming]

Hi paulbin,
I did a test, I think we could make use of Simple Error Handle.vi. Please see the attachment.