From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
12-02-2017 04:05 PM - edited 12-02-2017 04:19 PM
I'm writing a VI Analyzer test that involves detecting items within a subdiagram (like a case of a case structure) that might be broken. So just checking if the VI is broken isn't granular enough, I want to know the broken things on a certain subdiagram. Here are the things I can think of that I could detect through scripting that would tell me a subdiagram is broken:
1. Broken wire
2. Broken subVI (including a bad subVI linkage)
3. Unwired required parameter on a function/subVI
Can y'all think of anything else?
12-04-2017 09:34 AM
Array constant undefined type
12-04-2017 09:44 AM
and a few more:
missing SubVI (probably falls into broken SubVI)
format string problems with "Format into String" node
missing type definitions / other type definition problems for constants.
Scratching my head a bit around bundle/unbundle. I think most of these errors would be found through broken wire checks.
12-06-2017 11:19 PM
Thanks, Warren. I've added your suggestions to my test. Let me know if you (or anybody else reading this) can think of other broken items I can check for.