08-29-2014 08:01 AM - edited 08-29-2014 08:04 AM
I suppose you could use a case statement with a case for each of your error codes and use the error ring to generate a corresponding error code. That's like what you want to do. Use the error ring to select the error you want to generate.
08-29-2014 08:21 AM
@billko wrote:
I suppose you could use a case statement with a case for each of your error codes and use the error ring to generate a corresponding error code. That's like what you want to do. Use the error ring to select the error you want to generate.
The problem with that is that it is extremely difficult to cover all errors. That's why I recommended the Create Error From Error Code and then use the General Error Handler to do the actual looking up of the error code for you.
08-30-2014 01:31 PM
I see. I was thinking that he just needed a few error codes - but your solution is much more scalable.
09-02-2014 03:43 AM
Hey ph1,
i found something in our support portal, which might help you with your problem. I attach the document.
I hope that will help you with your problem.
Best regards
Dominik
09-02-2014 03:48 AM - edited 09-02-2014 03:49 AM
Hi Dominik,
oh, those were the days! 😄
1997 edition of LabVIEW error codes. Wow! (I guess the changes are rather small in the last 17 years.)
Did I mention the LabVIEW help before? Something like the list of VISA error codes?
09-02-2014 10:21 AM
i found something in our support portal, which might help you with your problem. I attach the document.
Hello Dominik,
I have found this document, too, some times ago but where "discourages" by it's age.
EPH
09-02-2014 10:24 AM
Did I mention the LabVIEW help before? Something like the list of VISA error codes?
Hello GerdW,
after an intensive search in the help (I don't now, why it is so confusing) I was able to find the VISA-Error-codes there. This works fine. To my luck I only need the VISA-codes and not all the others...
EPH