Where to define user error codes.

[jvh75021]

I am getting reports from the field about what seem to be user defined error codes, in the range of 50-60. Is there a standard place where LV programmers tend to list and define their error codes? I could check all the front panels but there are 1600 of them.

thanks,

jvh

[LV_Pro]

There are "standard" places to store the user defined error codes, LabVIEW actually allows you to incorporate them in a user defined error "database", but it would appear this wasn't done. Also 50 - 60 would be outside the NI define numerical area for user defined codes, -8999 to -8000, 5000 to 9999 or 500,000 to 599,999. You could do a string search for the number that you are seeing, but I suspect that, if you have any .dll's or .NET type calls that may be where they are coming from. I have seen a lot of .dll driver type calls that return undefined numbers, frequently in the lower range.

[jvh75021]

---

@LV_Pro wrote:

There are "standard" places to store the user defined error codes, LabVIEW actually allows you to incorporate them in a user defined error "database", but it would appear this wasn't done. Also 50 - 60 would be outside the NI define numerical area for user defined codes, -8999 to -8000, 5000 to 9999 or 500,000 to 599,999. You could do a string search for the number that you are seeing, but I suspect that, if you have any .dll's or .NET type calls that may be where they are coming from. I have seen a lot of .dll driver type calls that return undefined numbers, frequently in the lower range.

---

Thanks for the post. Regarding the user defined error "database", would it be a vi, in a project file, etc?

[smercurio_fc]

The user-defined error codes file would be contained in your project and be distributed along with the application. So, if you didn't create a custom error codes file for your project then there wouldn't be one. Check the LabVIEW Help on distributing custom error code files.

[LV_Pro]

But since you are getting errors in the 50 - 60 range I suspect that it is coming from a .dll, or non-NI instrument driver. Some instruments return error codes that may be put onto the "error chain" in the code. Not sure how you will narrow it down if the resulting error message doesn't help. I try to have mine include the "call chain" which shows the heirarchy of vi's back to the source one, but it doesn't sound like is the case here. I'm afraid that the previous posters recommendations will help you make your system more robust, once you find the current source of errors. If they can narrow down what the program is doing when it throws the error it may help narrow it down a bit as to where to look. I've had similar problems in the past where I got a non-standard error numbers form instruments, etc.

[jvh75021]

---

@smercurio_fc wrote:

The user-defined error codes file would be contained in your project and be distributed along with the application. So, if you didn't create a custom error codes file for your project then there wouldn't be one. Check the LabVIEW Help on distributing custom error code files.

---

Apparently the creator didn't create a custom error codes file as I don't see one in the .lvproj file. Thanks for the LV help reference. I can learn from my predecessor's mistakes as well as my own.

jvh

[jvh75021 · Accepted solution]

All your replies were helpful so forgive me for not accepting one as the solution.

jvh

[LV_Pro]

Kudo's are nice 😉    Part of the reason to mark one of them as a solution is to show at the higher forum level that there is a solution, allowing others who may not be following the entire conversation a chance to benefit.

But thank you for thanking us. Good Luck in your "wiring"

[jvh75021]

Yeah, I usually kudo but in the heat of battle I fergotted.

[jvh75021]

Here's the error message from the data sheet. I says user defined error code but sure looks like a LV error message to me.

Error: TCP Open Connection in NI_InternetTK_Core_VIs.lvlib:Telnet Open Connection.vi->TelnetCommunicator.lvlib:TnCom_Connect.vi->TelnetCommunicator.lvlib:TelnetCommunicator.vi->MvTrafficController.lvclass:ConnectTelnet.vi->MvTrafficController.lvclass:GetRevisionData.vi->MvTrafficController.lvclass:ConfigureSystem.vi->MvTrafficController.lvclass:Initialize.vi->MvTrafficController.lvclass:MvTrafficController.vi->MvTrafficController.lvclass:MvTrafficController.vi.ProxyCaller
LabVIEW: The network is down, unreachable, or has been reset. [Error Code: 59, User-defined error code.]