Discussion:
USB to Serial interface problem ?VISA device busy occurs after several hours of continous use.
(too old to reply)
mattster
2008-08-07 11:40:07 UTC
Permalink
I am using LabVIEW8.5 to communicate with a USB device using a FTDI FT232BL 648-1 controller (chip).  The USB serial converter driver is the latest version available (2.04.06 March 2008).  The USB serial device is sending packets of data at approximately 1s intervals.  OS is win XP with all the latest service packs installed.

 

My problem is that that VISA/LabVIEW loses contact with this device after several hours (or up to three days was the longest continuous run).  The error I get (from the Measurement & Automation Explorers ?Open VISA test panel?) is:

 

Unable to open session to ?ASRL11:INSTR?

 

Return status code 0Xbfff0072

Status name: VI_ERROR_RSRC_BUSY

 

The resource is valid, but VISA cannot currently access it?.

 

 

During this time I have nothing else trying to communicate with this device and the computer is not being used.  Below is some code to demonstrate how I communicate with this device.

 

<img src="Loading Image...">

I have two "solutions" to gain access to "COM10"&nbsp;again:

-
Restart windows

-
Remove USB cable, delete the USB Serial Port from the Windows Device Manager, then re-insert USB cable (i.e. reinstall USB&nbsp;Com&nbsp;port)


note:&nbsp;Restarting LabView or removing the USB and re-inserting it does not help.

&nbsp;

&nbsp;

Any help&nbsp;or advice&nbsp;would be appreciated!
MikeS81
2008-08-07 11:40:07 UTC
Permalink
Hi mattster,
i think after you lose the connection, LabVIEW doesn´t close the VISA connection and this can be the problem. Did you try to run only the close function with your com port connected?
&nbsp;
Hope it helps.Mike
mattster
2008-08-07 12:10:05 UTC
Permalink
Hello Mike,
&nbsp;
Thanks for you fast reply and&nbsp;solution to my problem :smileyhappy:
&nbsp;
I did exactly as you suggested and&nbsp;then I could access the port again.
&nbsp;
I will modify the code so that when&nbsp;the error occurs again (port not found) I will force the port to close and then re-open it...
&nbsp;
&nbsp;
Many thanks,
&nbsp;
Matthew
mattster
2008-08-09 09:10:05 UTC
Permalink
This post might be inappropriate. Click to display it.
Loading...