Problem with error handling

[truskawka]

Hello, I have a little problem with error handling. I have shared example of my main vi and error handling vi.

All the components in the main vi has wrong port numbers, all will give errors

Program should work in this way: When the program runs it will display errors from 3 of those components (i blocked to display the same error while the loop is running in the Error Handling.vi). If the errors not acknowledged ACK column will be X, if the error acknowledged it will be ACK. When you acknowledge the errors, errors will be acknowledged but if those errors are still ongoing and not fixed it should be displaying as a new one. All the active errors should be displayed again as not acknowledged. 

Program working in this way: It displays all the errors in the beginning, but when i acknowledged the errors it doesnt display ongoing errors again and displaying one of the active errors.

You can find my Main.vi Error_handling.vi and Visa_error_list.txt attached. please copy this Visa_error_list.txt into main directory of the C drive and it will work perfectly. 

Written in LabVIEW 2015

[altenbach]

You really need to start again with some basic LabVIEW tutorials.

• Why is there a timeout event it it does not do anything?
• Why all these local variables (and their indicators disconnected!). Typically you would keep state in a shift register.
• Why all thee "error array" value properties?
• Why is there a time delay in the error handler?
• If you would wire the error across your time delays, you could eliminate all sequence structures.
• You are hammering listbox properties. Firing events from secondary loops via signaling properies is like the tail wagging the dog.
• ...
• ...

Maybe you should move all error maintenance in an action engine that maintains the error list. It would accepts new errors and outputs the current list and metadata when called without inputs.

[truskawka]

the vi i shared is not my main vi. I cut other stuffs. and i reconfigured to explain problem. 

---

Maybe you should move all error maintenance in an action engine that maintains the error list. It would accepts new errors and outputs the current list and metadata when called without inputs.

---

I'll try in this way, thx