Labview Handling errors

[RRN1971]

Is there any method that can automatically find and solve the error in Labview?

[RavensFan]

What is "the error in LabVIEW"?

Your question is very nebulous.  Please provide details as to what you are trying to do.

[Bob_Schor]

... and for such a nebulous question, it would really help us (to help you!) if you would attach your code (and please, attach the actual .vi files).

Bob Schor

[RRN1971]

Let me clarify because is not nebulous question. This is my first time using labview and I'm learning using 2 book that I have. I'm working/learning how to uses the tools to handling error example: 

Automatic Error Handling
Manual Error Handling
Error Clusters
Explain Error
Using While Loops for Error Handling

My question is a general question. LabVIEW has any other tool that can detect an error and automatic fixed the error like example word processor an auto correct. I know that automatic error handling tell you what error code possible solution and also stop the Vi in the point where the error happen.

Thanks

[RavensFan · Accepted solution]

It was a nebulous question when you first asked it.

Now you have added some details to put a little more context to it.

There are a few things you can do to "automatically" fix errors.  For example, you can right click. a broken wire that describe it is part of a cycle, and choose to insert feedback node.  But that is not going to be "automatic", because I sure don't want LabVIEW "fixing" things in a way that I might not want.  That is why I turned off automatic feedback node insertion.

Remember, you are a programmer creating something original from nothing.  There are millions of possible errors.  How do you expect the creators of LabVIEW to  detect those and provide the right "fix" for all of them?

Auto-correct is a bad comparison.  Words are either spelled right or spelled wrong.  It is easy to highlight something is wrong and provide a few alternatives.  With programming, the problems and solutions are exponential.

[RRN1971]

Thanks for your time and clarification. 

[cbutcher]

Note that although I think this question is focused on programming errors (which are difficult to correct in general), examples like Spell Checking or providing valid options for a user to input at runtime are both possible and useful.

You just have to program them 😕

In some cases this is very much worth the effort. In others, it might be more productive to manually fix issues. In the case of programming errors, the latter is almost always true (I also dislike the autoinsert feedback nodes option and immediately disable it).

[billko]

---

@cbutcher wrote:

Note that although I think this question is focused on programming errors (which are difficult to correct in general), examples like Spell Checking or providing valid options for a user to input at runtime are both possible and useful.

You just have to program them 😕

In some cases this is very much worth the effort. In others, it might be more productive to manually fix issues. In the case of programming errors, the latter is almost always true (I also dislike the autoinsert feedback nodes option and immediately disable it).

---

That option is on top of my hit list of things to change, right next to "view terminals as icons".

"Auto-groan" (Auto-grow) is also not useful to me, although just as many people find it extremely useful as find it annoying.