LabVIEW 2013 13.01f2 64 bit appears not to release USB device

[GleMunyan]

As I attempt to migrate  to 64 bit version I have a problem where it appears (for a lack of a better word) LabVIEW does not release the USB device properly when I programatically turn the power off for the USB device I am using (a spectrometer).  This software works fine on the 32 bit version.  The ONLY way I can get my device to work is by exiting either the EXE or the LabVIEW development system.  Upon "wakeup" that is powering up the device, the DLL calls partially work, don't report errors but the device will not function properly.  This a bit of a gray area since the company who wrote the DLL does not support the LabVIEW part very well and their example code works, but they don't power cycle the device.  

Wish there was some sort of purge or release function.  I have looked at the Know issues and I also put in a service request with NI.  

If I don't get a fix for this I will have to abandon the sleep mode code.  

Any help would be appreciated.  

[billko]

---

@GleMunyan wrote:

As I attempt to migrate  to 64 bit version I have a problem where it appears (for a lack of a better word) LabVIEW does not release the USB device properly when I programatically turn the power off for the USB device I am using (a spectrometer).  This software works fine on the 32 bit version.  The ONLY way I can get my device to work is by exiting either the EXE or the LabVIEW development system.  Upon "wakeup" that is powering up the device, the DLL calls partially work, don't report errors but the device will not function properly.  This a bit of a gray area since the company who wrote the DLL does not support the LabVIEW part very well and their example code works, but they don't power cycle the device.  

Wish there was some sort of purge or release function.  I have looked at the Know issues and I also put in a service request with NI.  

If I don't get a fix for this I will have to abandon the sleep mode code.  

Any help would be appreciated.  

---

Was there a compelling reason to migrate to LV 64-bit?  Were you feeling constrained by the 4GB memory limit?  That would be one reason I would switch.  (The other is if the equipment I was controlling only had 64-bit dlls). LV 64-bit has only limited support compared to LV 32-bit.

[GleMunyan]

There are 3 1/2 compelling reasons.  1) it is getting increasingly difficult to buy a Windows machine with 32 bit installed and 2) More than once I have had customers who wanted to have my device and their memory hungry applications share the same space 3) I am about get a dual HD video acquisition project and would like to keep in my back pocket the option of adding my device to the mix 4) Yes to feeling constrained by 4GB.

The other equipment has 32 bit dll's also.  It has not been fun working with their DLL's though, the header file usually needs some editing to get the wizard to import them and I still need to do some tweaking. 

[cheggers]

I have to add a comment on your first reason: I guess most of the peoples (including myself) are using 64 bit Windows machines but with LabVIEW 32 bit installed (Windows-on-Windows), please see

Using National Instruments Products on 32-bit and 64-bit Windows
http://www.ni.com/white-paper/10339/en/

Of course you're right, today it's difficult to get a 32 bit machine but since LabVIEW both 32 bit and 64 bit can run on a 64 bit machine you are not forced to buy a 32 bit machine.