Why does it seem so difficult to find error codes?

[ewtotem]

Perhaps I missed the sign pointing me in the right direction, but error codes should easily found on your site without turning into a reseach project.

http://zone.ni.com/reference/en-XX/help/371361D-01/lverror/error_code_ranges/

[chilly_charly]

What do you mean ? Are you trying to get a list of all error codes ? Or do you just need to understand the meanning of a specific error code ? Try to be more explicit please...

[shoneill]

Well the link in the original post actually points to all the error codes, so I have trouble believing that's the question.

Personally, I would like something telling me which LabVIEW primitives can return which errors so that anticipating errors before they actually happen would be a lot easier.  Maybe I'm just lazy.....

Maybe this is the deeper meaning behind the originalpost?

Shane.

[TCPlomp]

I think the original poster had a hard time to find the error codes and generously shares the result of his research with us.

Kudos in that case

Ton

[shoneill]

Ton,

that is of course a thoroughly plausible explanation.

Shane.

[LabViewGuruWannabe]

That's funny, it seems the link posted is the same information as opening LabVIEW Help and looking at the Index tab for error codes. I also sometimes use the Explain Error popup if my program doesn't have an error cluster.

The pen is mightier than the sword, unless error 18 occurs...






Message Edited by LabViewGuruWannabe on 11-05-2007 07:06 AM

[ewtotem]

Thank you for your, comments.

Yes, I wanted to provide what I found to help everyone else out there who might be looking for what there error code means - suspect this is not uncommon.

as mentioned, I would also like a more thorough explanation of a given error code, but have come to except that such wishes are never fufilled by any software group.  Perhaps an error driven solution such as eventid.net for Labview errors would do the trick. Point:  Instead of combing through a soup of message threads - have a Error code driven solution system.  Put in the error code, have answers revolve around the error code(s) -- better search tools, and more logical ways to seach. Sometimes I get better results using Goolge to comb through the forum than the native search tool.

That aside, when I go to NI, I would like to go to the Labview support page and find a link to all error code listings. Error codes are a fundamnetal starting point.

Incidentally, I'm alway running into exceptions:  I recently encounter error -107413509, you will note that it's not referenced on the master list range.

[Dennis_Knutson]

If you have an error indicator, you can simply right click on it and select 'Explain Error'. The actual error codes are in files in your \resource\errors\English folder. They are also listed in the on-line help. The link you posted has the same exact information as the on-line help.

Where exactly did you get this error? It's possible that whoever wrote the VI created an error code that did not follow the guidelines or was written before some of the guidelines were in place.

Message Edited by Dennis Knutson on 11-06-2007 10:30 AM

[smercurio_fc]

My guess is that it's coming from a Toolkit or other add-on. I believe those error codes are just the ones from LabVIEW, and not from toolkits.

[ewtotem]

Thank you again.

Dennis, Thank you for your reference. I am running Labview 7.1 Expess Development. Although esentially the same, the list seems slightly dated.  I don't believe the list is updated in anyway.

Most of the time, I can read the error out message. Having reference to the a main list can help sort out heirarchy and come up with other ideas.

I still believe it's better to start with one updated master list that can be searched and explored on the NI site.

The particular error -107413509, came from an Initialize.vi from a California Instrument 3091LD load. If the ID query is set to 'True',. I imagib=ne that is very possible the error was created before the convention; however, it would be nice to enter error -1074132509 on a specific error driven search engine to discover that fact.

Error -1074135039.  Paramter not allowed. This was followed by a device error desplaced on the instrument display "error 108" p164 of the users manual states: "108: A parameter was sent with the command, but none was expected". The VI works fine as long as this parameter is false.

To separate this particualr device error from the general discussion of error code help, I posted a device specific thread for that specific issue: http://forums.ni.com/ni/board/message?board.id=170&thread.id=282723

My point is that I encounter errors that I do not have reference too often and would appreciate a central managed clearing house. Again, take a look at eventid.net as a reference. People pay money for membership to this site because they cannot find Windows help they need within this pools of message threads available, Microsoft based or not.