Comments on: Error Handling in a Sequence of Critical Tasks http://blog.jki.net/labview/error-handling-in-a-sequence-of-critical-tasks/ Pushing the Limits of LabVIEW Tue, 29 Nov 2011 20:21:49 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Michael http://blog.jki.net/labview/error-handling-in-a-sequence-of-critical-tasks/comment-page-1/#comment-2102 Michael Sat, 29 May 2010 14:05:56 +0000 http://blog.jkisoft.com/?p=1390#comment-2102 Definitely good practice. However only works if you know ahead of time how many tasks there are to perform. A third example would be good, where you make a subVI which would effectively replace the Clear Errors.vi, where it merges them in place and then allows you to query the error state(s) when ready. This either requires a second wire to transmit the merged info, or a action-engine style implementation if you're sure the VI will only be called from this call chain. Definitely good practice. However only works if you know ahead of time how many tasks there are to perform.

A third example would be good, where you make a subVI which would effectively replace the Clear Errors.vi, where it merges them in place and then allows you to query the error state(s) when ready. This either requires a second wire to transmit the merged info, or a action-engine style implementation if you’re sure the VI will only be called from this call chain.

]]>