11-01-2013 04:50 AM
Hello all,
I am using microchip USB to serial converter and working with VISA. Sometime what happens my application generate this error, but equivalent COM port it shows in device manager, but doesn't shows in VISA resource name after I do referesh also.
Later I simply restart my application, turn OFF and ON the device and it works afterward and after sometime same story
Is this driver problem?
Thanks
11-01-2013 12:20 PM
Nope. not a driver problem.
Windows is shutting down the USB hub power.
11-01-2013 10:09 PM
Thanks, looks like this gonna solve the problem,
But let me ask one more question, I have used till now, silicon,bofa and arduino usb to serial driver and I even downloaded 20min over serial communication never changed this settings and faced any problem, but in this I need to change. Is this becasue of vendor(microchip)?
11-01-2013 10:49 PM
Well if you have something going on continuously such as 20 minutes, windows isn't going to shut down the USB port because it recognizes it is actively being used. Only if the port is being unused for some fixed period of time will Windows shut down the port.
In your application, do you have a shift register on the error wire? If so, don't. Some people will swear to you that is what you should do, but if you don't have proper error handling (as in you detect the error, do something about it, and then clear the error on the wire) one sporadic error such as a timeout. When that error gets put into the shift register, then it is going to be there at the beginning of every loop iteration, and normal function behavior is to not executed a function if there is an incoming error on the wire. So you've basically killed the functioning of your app until you stop and restart it which effectively clears the error going into the shift register.
11-01-2013 11:47 PM
@RavensFan wrote:
Well if you have something going on continuously such as 20 minutes, windows isn't going to shut down the USB port because it recognizes it is actively being used. Only if the port is being unused for some fixed period of time will Windows shut down the port.
In your application, do you have a shift register on the error wire? If so, don't. Some people will swear to you that is what you should do, but if you don't have proper error handling (as in you detect the error, do something about it, and then clear the error on the wire) one sporadic error such as a timeout. When that error gets put into the shift register, then it is going to be there at the beginning of every loop iteration, and normal function behavior is to not executed a function if there is an incoming error on the wire. So you've basically killed the functioning of your app until you stop and restart it which effectively clears the error going into the shift register.
Dear @RavensFan,
How can I handle this error? one thing I can swear is this is not at all becasue of idle timeout, becasue my applcation runs continously. In between it happens. In my application, in the loop I will write and read. Between two write I may take 5-10 sec.
Same logic is implemented on arduino also but never faced this problem.
I cant clear the error if it happens in between becasue I need to restart the application then only it shows?
Any suggestion for that.
11-02-2013 12:09 AM
Even I detect the error but how can I clear it? It doesnt shows in my VISA resource itself.
Any suggestion?
Thanks
11-02-2013 02:11 AM
@JÞB wrote:
Nope. not a driver problem.
Windows is shutting down the USB hub power.
This doesn't solve the problem. Any other suggestion?
Thanks
11-05-2013 08:54 PM
Will unchecking this solve the problem?
11-05-2013 11:19 PM
That's the idea.
But in the previous message you said it didn't help solve the problem.
So which is it?
11-05-2013 11:34 PM - edited 11-05-2013 11:35 PM
Unchecking that didn't solved i.e. USB ROOT HUB PROPERTIES