Understanding LabVIEW Programming Patterns and Frameworks

[@jacquesdejager5362]

Thank you very much, this was really informative and useful.

[@CK-or3jf]

thanks for the explaination

[@sprezzaturarrd]

I'm not sure I understand using G-code to generate a customize error. If I need to create a unique error that occurs - for example, a routine for testing a device in production needs to pass or fail. If fail, I need to stop further testing and send a failure message along in the program - using the error bundle allows me to do that. It seems like I would do the same with the g-code object shown at 24:57

[@dnatt2]

If you use Error Cluster From Error Code.vi, it will programmatically generate the call chain and include it in the error source string, which is more dependable than putting your own VI name (or worse, no VI name at all) in the source string with a Bundle function. The Error Cluster From Error Code.vi has an "error message" input that allows you to pass along any additional debug information within the error cluster. I discuss these topics in much greater detail in my "What To Expect When You're Expecting an Error" presentation here: th-cam.com/video/UlOFcmwrsBA/w-d-xo.html