Finger Trouble with References

[alecjcook]

Hi,

   I have an automated test system set up. Here is a snapshot of a standard VI I use to create my results files at the end of the test (This VI is called at the end of each one of my test VIs)

Now this works fine, until. I have started trying to chain my test VIs together from one location.

I have a "Host" application that calls my test VIs one by one. This works fine, but I am finding my results files do not get saved, UNLESS I, by hand, OPEN the front panel of the "save results" vi, before i run the tests. Does anyone have any idea why this is happening?

Here is what i am doing to load the VIs:

Many thanks, Alec

[ShalimarA]

Hi Alec,

Can you confirm my understanding of your code. From your main VI, you're opening a reference to the 'save results' vi, activating the front panel, running the VI (to write the results), then closing the reference. As it is, the saving doesn't actually occur unless you open the front panel of the 'save results' vi. 

Essentially, the problem is that the front panel doesn't open automatically. Is that correct? If so, you may just need to remove the 'FP Open' invoke node, as I've found that it's made redundant by the 'Run VI' invoke node. Let me know if that makes any difference.

[alecjcook]

I think it's the "Link" object.

I suspect that this object behaves differently if a reference is opened to the vi that contains it, as apposed to double clicking to open the vi.

can anyone confirm this? and confirm HOW it actually works?

Cheers, Alec

[nathand]

The "Link" is the Call Chain function. I don't think that's your problem, although it might return different results when you call a VI dynamically versus when you call a VI directly. If I'm not mistaken, a VI that is loaded and run dynamically using the Run VI method, as you're doing, becomes a new top-level VI instead of a child of the VI that called it.

I would throw a Simple Error Handler after the close reference, and also a one-button dialog that displays the path that you receive from the property node, in that logging subVI. Then run your tests with the front panel open and closed, and see what path is returned and whether any errors are generated.