Showing results for 
Search instead for 
Did you mean: 

LabVIEW 8.6 stops responding after VI is closed that uses USB communication.

I am using LabVIEW 8.6 with Windows XP.  My VI communicates with an external device via USB.  The VI works fine, but when I close the VI, LabVIEW stops responding.  Any help with this problem would be appreciated.  Thanks.
0 Kudos
Message 1 of 7

Good Morning!

    Can you clarify what you mean by LabVIEW quites responding. Do you mean the rest of a program that uses the Vi, do you mean the whole development environment freezes? Can you attach a screen shot of the vi in question? If so, please make it a png or gif rather than a BMP image, they end up being huge.



Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5

LabVIEW Champion

0 Kudos
Message 2 of 7
Thank you for your response.  The entire LabVIEW development environment freezes up.  I'm sorry but I can't supply a copy of the VI or even a screen shot.  The VI uses a Call Library Function node to link a .dll file to the VI.  The .dll file is the file that provides the USB communication.  I'm wondering if anyone else has experienced similar behavior when using LabVIEW for USB communication.
0 Kudos
Message 3 of 7

Not with USB specifi but dll in general.


Check the docs for your dll and see if you can find a way to shut it down and unload it. It sounds like there is SOMETHING still running and the dll is a likely suspect. You could eleminate all calls to the dll completely to verify that its the dll and not LV causing the hang.


Have fun!



Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 4 of 7

If I open LabVIEW and run a VI that is not dependent on the .dll file, everything works fine.  But if I open a VI that depends on the .dll file, and then close the VI without running the VI, the entire LabVIEW environment ceases to respond.  The freeze up problem exists whether I run the VI or not.

0 Kudos
Message 5 of 7

Hi epsilon,


It sounds like there is some callback from the DLL on load.


The test would be to set up the VI the same way with a call library function node but don't configure the node for your DLL. If that doesn't crash it, but after configuring it does, then it is related to the DLL not LabVIEW. There could be something loading when the DLL is loaded when you open the VI.

Jeff | LabVIEW Software Engineer
0 Kudos
Message 6 of 7

To Jeff and the others who responded,


Thanks for your help and suggestions.  The problem was in the .dll file and I think it is fixed now.



0 Kudos
Message 7 of 7