LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW General Error Handler User Defined Codes

Solved!
Go to solution

The General Error Handler in LabVIEW 2020 is not working as expected, It does not generate the type of dialog selected, source output is blank when error source is designated (input), a generic, non-specific msg is displayed, and there is a ambivalent pop-up window which does not correspond to user-defined error.

sfrosty_0-1630607687848.png

 

0 Kudos
Message 1 of 10
(3,540 Views)

I could never get that to work as expected either...

 

I ended up dealing with it further upstream using the "Error Ring".

 

eringCapture.PNG

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 2 of 10
(3,524 Views)

It did work for me in another app. Not sure of the LabVIEW version. Maybe LabVIEW version has something to do with it, because it did work in the past. Thanks for your suggestion! 😉

Oh, never saw that pop-up screen (issue 4) before - totally weird!

0 Kudos
Message 3 of 10
(3,503 Views)

@sfrosty wrote:

 

Oh, never saw that pop-up screen (issue 4) before - totally weird!


Drop the error ring on the block diagram and click on it.

 

 

========================
=== Engineer Ambiguously ===
========================
Message 4 of 10
(3,497 Views)

 

Oh, I was referring to my pop-up window, depicted below in grey, but thanks for that!

 

General Error Handler Issue Snippet.png

0 Kudos
Message 5 of 10
(3,491 Views)
Solution
Accepted by topic author sfrosty

Have you upgraded to Service Pack 1? At the very least, for me the dialog appears somewhat correctly and the Continue/Stop buttons are there. Issues 2 and 3 are still present however.

Spoiler
FireFistRedhawk_1-1630614401042.png

 

Edit: Issue 3 resolves itself for me if I hit Continue instead of Stop (goofball moment there). Issue 2 resolution is a bit weird... The "source out" indicator only populates with the contents of "[error source]" in the case where "error in" does not contain an error but "[error code]" does contain a nonzero number. 

 

I don't see why they wouldn't just populate the source out indicator in either case, but alas, that's what I found.

 

Edit 2: It must be the end of the day... "source out" populates correctly for me in either case, IF I hit Continue instead of Stop. If "error in" does contain an error, "source out" will display the source from the error cluster. If there is no incoming error on the error wire, then it will look at "[error code]" and "[error source]" and display those.

Redhawk
Test Engineer at Moog Inc.

Saying "Thanks that fixed it" or "Thanks that answers my question" and not giving a Kudo or Marked Solution, is like telling your waiter they did a great job and not leaving a tip. Please, tip your waiters.

Message 6 of 10
(3,488 Views)

Hve you tried using the Simple Error Handler instead?  I know it incorporates the General Error Handler as a subVI, but it always seemed to work for me.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
Message 7 of 10
(3,459 Views)

Thank you, but the General Error Handler doesn't support using custom codes, which my app requires.

0 Kudos
Message 8 of 10
(3,423 Views)

Found that there is a bug regarding the "LabVIEW General Error Handler" in LabVIEW version 2020. I verified that the General Error Handler works as specified in LV2018 and LabVIEW 2020 SP1.

As stated by Redhawk above.

Message 9 of 10
(3,387 Views)

Thanks! Upgrading to LV2021 SP1 fixed the issue!

As stated by Redhawk above.

0 Kudos
Message 10 of 10
(3,386 Views)