Anyone know why the vi niFgen Allocate Waveform.vi causes a second instance of LabVIEW to open in Windows

[ATE_Dude_22]

I have a large scale ATE written in LabVIEW 2011, using TestStand 2010 SP1 as the test executive that works just fine until the test sequence ends. For some reason when I close the completed executions from the Sequence Editor, a second instance of LabVIEW that gets launched when this vi executes stops responding, and I have to kill all LabVIEW processes to be able to run another execution.

I can't figure out why this vi is causing a second instance of LabVIEW to start, much less why it causes LabVIEW to hang.

Any ideas? I've included a screen capture of the implementation being used (the vi between the two breakpoints is when this second instance of LabVIEW launches)

[JÞB]

I'm not sure what else is going on but, you are wiring a waveform name out of that function to the Chanel name in of write waveform.  I'm surprised that isn't throughing an error since the Fgen probasbly does not have a "MyWaverorm" Chanel.

[ATE_Dude_22]

No, it's wired from Waveform Name Out to Waveform Name, not Channel Name

[JÞB]

Really?

How?

[ATE_Dude_22]

Yep, really. I am using LabVIEW 2011

[JÞB]

Thanks for clearing that up.  I would suggest updating NI-Fgen. There are a few known issues that "Might" be related.

[ATE_Dude_22]

Therein lies the problem. This ATE is a PXI configuration, using the PXI-8106 Controller, but the system recently crashed and we did a recovery using the Acronis image. I can't for certain say what version of NI-FGEN this application was developed in originally. I agree with you, I think upgrading the development system is the way to go, but I have been requested by my boss to try and get it working with the IDE our documentation last showed it in.

Thanks for your suggestions though, appreciate it.