Jump to content

Recommended Posts

Hi guys,

I'm back again with my questions.

Following this article http://zone.ni.com/devzone/cda/tut/p/id/3209 on the NI web site, using the error code file editor, I have created my own custom error file. It was my first time! The file is txt format and it is located at user.lib path. I've already restarted labview (2011 version) but I'm not able to raise an error which is handled by the txt file I have created. If I set the error code on the error cluster with a code handled by my custom file, I receive a non defined error message from labview but this isn't the truth! So here my question:

how can I raise a error which is handled by a custom error file?

Does someone help me?

Thank you in advance.

Link to comment

Again, I've solved the problem. Here the solution to allow others people to do not waste time with this stupid thing. The problem was due to the name of error file I've created. To be loaded from the IDE, it must be named as you want except for the last part of the name which have to be "-errors" and which you have to insert before of the "txt", the extension of the file. This is required but no one says it to you!

Anyway, thank you for the support you've given me many times.

Link to comment

Again, I've solved the problem. Here the solution to allow others people to do not waste time with this stupid thing. The problem was due to the name of error file I've created. To be loaded from the IDE, it must be named as you want except for the last part of the name which have to be "-errors" and which you have to insert before of the "txt", the extension of the file. This is required but no one says it to you!

Anyway, thank you for the support you've given me many times.

Good job on solving your issues.

Here is a KB on custom error files that may provide more info for others (that includes links to other resources at bottom).

Link to comment

Again, I've solved the problem. Here the solution to allow others people to do not waste time with this stupid thing. The problem was due to the name of error file I've created. To be loaded from the IDE, it must be named as you want except for the last part of the name which have to be "-errors" and which you have to insert before of the "txt", the extension of the file. This is required but no one says it to you!

Ummm... right in the article that you linked to it says:

"The file must be named xxx-errors.txt, where xxx is the supplied name"

And, in the LabVIEW Help for the page that discusses the custom error codes file it says:

6. When you are done editing the error codes file, click the
Save
button to save the error codes file in the labviewuser.liberrors directory. You must save the error codes file in the format xxx-errors.txt, where xxx is a name that you supply.

Edited by Saverio
Link to comment

Ummm... right in the article that you linked to it says:

"The file must be named xxx-errors.txt, where xxx is the supplied name"

And, in the LabVIEW Help for the page that discusses the custom error codes file it says:

6. When you are done editing the error codes file, click the
Save
button to save the error codes file in the labviewuser.liberrors directory. You must save the error codes file in the format xxx-errors.txt, where xxx is a name that you supply.

Saverio, you're right, it was my fault, I think such as everybody here I do not have a lot of time to spend to read the articles of NI carefully and some time I have to skip some parts of them and this is an error which can make you to waste time after.
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.