12-10-2020 11:05 AM
@drjdpowell wrote:
You actual did get the vi reference, and proved it by getting its clone name. Your issue is that your vi is called before its front panel is loaded, which means the controls that are input terminals weren't updated with copies of the input values. When you use a Value property node, you are reading the front panel's copy of the input, not the value used by the executing code.
Ok....Thank you all so much for the help on this one. I got what I needed. Not sure I like the solution but it works. I misunderstood that it actually was the clone reference. It looks like most of the API calls revert to the default VI if the FP wasn't opened. My guess is LabVIEW does this to keep memory down and possibly impact to performance. We'll see what my fix does to memory and performance.
This does work. And doesn't flash as you suggested.
12-10-2020 01:17 PM
OK I lied. This doesn't work! The first time it uses the original VIs information. Every time after that it uses the clone.. my guess is because the FP of the clone was now loaded by the subVI into memory and it uses the same clone the second time.... hmmm..
Any thoughts?