취소
다음에 대한 결과 표시 
다음에 대한 검색 
다음을 의미합니까? 

LabVIEW General Error Handler User Defined Codes

해결 완료!
솔루션으로 이동

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 포인트
1/10 메시지
4,435 조회수

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 포인트
2/10 메시지
4,419 조회수

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 포인트
3/10 메시지
4,398 조회수

@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 ===
========================
4/10 메시지
4,392 조회수

 

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

 

General Error Handler Issue Snippet.png

0 포인트
5/10 메시지
4,386 조회수
솔루션
주제 작성자 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.

스포일러
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

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.

6/10 메시지
4,383 조회수

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.
7/10 메시지
4,354 조회수

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

0 포인트
8/10 메시지
4,318 조회수

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.

9/10 메시지
4,282 조회수

Thanks! Upgrading to LV2021 SP1 fixed the issue!

As stated by Redhawk above.

0 포인트
10/10 메시지
4,281 조회수