project closes after I run and close certain VIs

[JBART]

I am running LabVIEW 2009 9.0f3 and am running into a couple odd things, I wanted to check if anyone else has seen this.  If I open the project it will close after closing certain VIs after they are run.  If I have a second VI open the project will remain open upon closing the VI.  This does not happen with all of the VIs in the project, only a couple of them.  This will also not happen unless the VI is run.

If anyone has ran into this and figured out how to fix it, or just has some ideas. I apreciate the input.

Thanks,

John

[JBART]

One more comment on this, if there are unsaved changes to the project it will not close as stated above, it will lock up labview instead of closing.

[Taki1999]

Do any of your VIs have cleanup routines that call Exit LabVIEW?

Seems like a Panel close event is triggering a LabVIEW shutdown.

[JBART]

No, I am not callang Exit LabVIEW.  I have attached a screen shot of one of the VIs.

[Taki1999]

Hmm. . .

Are all of the problematic VIs related to the 1553 device?

I'm wondering if there might be something bad happening with memory buffers crashing.

[JBART]

The 1553 device is not the problem, I have tested all of the dll calls with other VIs that do not have this issue.

Thanks for the suggestion though.

[Taki1999]

Just another shot in the dark.

Do the affected VI's all have that Node Reg reference?

I'm wondering if closing one of those VIs causes a problem by wiping out or corrupting that reference.

[JBART · Accepted solution]

I don't know why this solved the problem, but If I release the board before the program terminates then LabVIEW works just fine.  I was able to fix it and now everything is working fine.  Thanks for the input.

As for the Node Reg reference it is a reference into the XML file and is not supposed to cause any problems if it is not killed.  I kill the references on the internal VIs, just not the testing VIs.  I have read on this forum that the references will release their memory when they are killed or the program terminates.

[Taki1999]

Sounds like it might be a bug in the 1553 driver.  I'd report it to AIM and see if they've seen similar behavior.

( A little bit self serving, since I'm expecting to have to work with MIL-1553 systems on my next project.) 😛

[JBART]

Taki,

We might cross paths in the future then.  I'd be interested to hear a little about your next project, but I can't figure out how to PM on this forum.