Sorry for digging up old threads, but it seemed most relevent, and I always figure it's best to add onto old then start new. For ease of the next persons search.
So anywho, My first question is... I assume it is not necessary to open and close VISA sessions to USB ports, right?
I am having an issue where my device doesn't like to work unless a specific series of events take place... very unlike USB Devices in my experience. For instance, if you have the said device plugged in, and you turn it on, then open labview. It will spit out garbage. If you close labview, do nothing else, and open labview up... it will spit out the same garbage. ( by garbage i mean a series of y's with dots over it, and odd looking p's ... you know the kind of letters you get by pressing alt+###... i think in hex it winds up spitting out something like FF EF FF FF FF EF EF ) .... now, if from this current state, I unplug the USB and plug it back into the device, it will finally start to communicate properly.
Im curious why either labview or the computer itself are not recognizing the device on the USB port properly unless it is unplugged and then plugged back in. Ive tried to do reading on USB, and got all sorts of interesting tid bits of somewhat useless information. Im trying to determine if this is something I am not doing in labview, or if this device should have a driver to register with windows, or what exactly the issue is... Just a little background, I do explicitly know all the individual commands to this device so it is not an issue to communicate with it directly through visa...
Thought some of you might have insight or some similar USB experiences....
Message Edited by MJBrehm on 10-02-2006 02:17 PM
Message Edited by MJBrehm on 10-02-2006 02:19 PM
