LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

DISPLAYING ERROR MESSAGE

So my program is basically done, I just have one problem with it. My cases that have error messages are not displaying the error message when there is an error. I got help yesterday and was told to use the selector triangle thing which I am using. I guess take a look and see what I might have wrong possibly...?
0 Kudos
Message 1 of 9
(5,528 Views)

I clicked on your vi to download it, then backed off when I saw it was 2718 KB !  Smiley Surprised Can you pare down just an example of calling your error dialog?

Message Edited by Broken Arrow on 03-10-2009 09:03 AM
Richard






0 Kudos
Message 2 of 9
(5,523 Views)
I just put one case of where Im testing to see if theres an error or not...check it out
0 Kudos
Message 3 of 9
(5,514 Views)

Based on your logic it appears to me that you have all your Select functions wired backwards in terms of the True and False inputs.

 

I'm not sure I understand what you're doing with this array of errors. It appears you're just displaying them on the front panel. I see no dialog, yet your message implies that you're supposed to get a dialog. Also, since you have an uninitialized shift register, the errors from the previous run while the VI was still in memory will still be held. Don't know if this is intentional or not (or useful).

0 Kudos
Message 4 of 9
(5,508 Views)
The selector functions are not wired backwards, it returns the top which is true and bottom is false...How come where a test fails which would send a false to my selectors that it does not display my error message wired to the false port of the selector??? Should it just send that message to my string indicator outside of my shit register????
0 Kudos
Message 5 of 9
(5,504 Views)
Aside from issues with the shift register, which may be because of the way you pared down the original code, I'd be inclined to do what I have attached rather than the empty strings with selectors & build array or 3, etc.
Richard






0 Kudos
Message 6 of 9
(5,501 Views)

Is there a way to salvage what I have because I have about 30 case frames with over half of them with error messages using the selectors. Before I decide to take all that time to go back and redo this can someone give me some more input possibly??

0 Kudos
Message 7 of 9
(5,495 Views)

To clarify a few things:

1) You do realize that the "ERROR" array indicator will not update until the loop is done, right?

2) You are only indexing the top element out of the three possible errors you are building. Only IGNITION COLD will display - this is the behaviour I got when I ran it.

3) When you send the quotes to the array in the event of no error, you are still building an array of three things.

Richard






0 Kudos
Message 8 of 9
(5,469 Views)
Yeah I just realized a lot of the things you pointed out, sorry im newer to labview. I am getting some help straight from a field engineer from National Instruments so hopefully he can get me started in a new approach to doing my error messaging
0 Kudos
Message 9 of 9
(5,463 Views)