I've inherited a project that uses the LabVIEW UIs with TestStand. This project uses a PLC to do most of the machine control functions with an HMI type layer running on the main computer. There is a watchdog routine on the HMI side sending an "I'm still here" message to PLC at a rate I haven't dug into yet (looks like in the 3-5 second range) and what happens is when I Test UUTs the .seq and it loads the VIs, the watchdog routine occasionally gets paused long enough that the PLC will go into a shut down mode thinking the main PC has locked up.
The VIs that are being loaded are under a directory that is placed in the 'Always Included' section of the build but they certainly won't be directly linked to the Main.vi that is in Startup VIs. Are these 'Always Included' vis getting compiled but it still takes time for the runtime engine to pull them into memory? I've noticed the preload process is actually faster if rather than running the .exe I just open Main.vi and run it via the run button.
I'll probably end up just changing it so when the user clicks Test UUTs I'll momentarily pause the watchdog...but I wanted to understand what is going on with the vi loading before I monkey with what is essentially a safety feature with the watchdog.
