Question about PC's & USB
-
If a hub is involved, my first suspicion is always power. +5V ain't what is used to be (says an old time engineer). You know where to put the multimeter prods...
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
Yup! 5.00 ish, Plugged into a dodgy hub... Interesting unit can crash and not appear as a com port...
-
Hi All, Odd question, I am having issues with a device plugged into a USB hub of a touch screen PC, when it was connected to an old Win7 desktop via USB it worked with no problem. I'm guessing between 7 and 11 the USB driver changed (it would have to) and now the Win11 the device is unreliable and needs resetting. I wonder is it the device or the driver. It appears that the company does not have any specalised drivers so it's a standard com port. Can this be an issue? Glenn
glenn, it's simpler than that... as soon as I get out of a meeting, I'll give you more details. Lived this for 20 years
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
I am a Linux fan, does Windows have an application to actually monitor / reed / guess the USB device power "in use " ? Never seen such app in Linux, but did not bother to look for it.
It's sometimes hard to say what is windows versus what is a device manufacturer doing something in their driver. I'm pretty sure I have had Windows 10 tell me I was pulling too much current on the USB and shut the port down temporarily (not a timer - it tells you to go turn it back on if it's OK).
-
Hi All, Odd question, I am having issues with a device plugged into a USB hub of a touch screen PC, when it was connected to an old Win7 desktop via USB it worked with no problem. I'm guessing between 7 and 11 the USB driver changed (it would have to) and now the Win11 the device is unreliable and needs resetting. I wonder is it the device or the driver. It appears that the company does not have any specalised drivers so it's a standard com port. Can this be an issue? Glenn
Your question is ambiguous. Bear with me.
-
"when it was connected to an old Win7 desktop via USB it worked with no problem"
Explain this please. device was plugged in directly to the PC? If the PC was old, USB 2.0? -
is the touch screen a real PC running Windows 11? I want to be clear to make sure we're not talking about a WinIOT bastard child or something.
-
Forget about any power issues. The first thing to check is what type of hub are you putting the old device into? USB is allegedly universal, but I've seen issues with older devices.
Note on the power comments: this absolutely used to drive me instance - Windows helping to save power by turning off devices. Its like MS lives in some other dimension. First thing I would do after plugging your device in is go to Device Manager. See if you have a driver issue. Your device may be sol old it's just not supported under Win11. I have a basket full of these things.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
-
Your question is ambiguous. Bear with me.
-
"when it was connected to an old Win7 desktop via USB it worked with no problem"
Explain this please. device was plugged in directly to the PC? If the PC was old, USB 2.0? -
is the touch screen a real PC running Windows 11? I want to be clear to make sure we're not talking about a WinIOT bastard child or something.
-
Forget about any power issues. The first thing to check is what type of hub are you putting the old device into? USB is allegedly universal, but I've seen issues with older devices.
Note on the power comments: this absolutely used to drive me instance - Windows helping to save power by turning off devices. Its like MS lives in some other dimension. First thing I would do after plugging your device in is go to Device Manager. See if you have a driver issue. Your device may be sol old it's just not supported under Win11. I have a basket full of these things.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
Most of your comments make sense. Looking forward to learn new things here ;) Anyway in short: usbser.sys had/has? a lot of issues. Check the comments to this old question (was my old acount): Checking whether usbser.sys is still working/polling a COM port/CDC device[^]
-
-
Your question is ambiguous. Bear with me.
-
"when it was connected to an old Win7 desktop via USB it worked with no problem"
Explain this please. device was plugged in directly to the PC? If the PC was old, USB 2.0? -
is the touch screen a real PC running Windows 11? I want to be clear to make sure we're not talking about a WinIOT bastard child or something.
-
Forget about any power issues. The first thing to check is what type of hub are you putting the old device into? USB is allegedly universal, but I've seen issues with older devices.
Note on the power comments: this absolutely used to drive me instance - Windows helping to save power by turning off devices. Its like MS lives in some other dimension. First thing I would do after plugging your device in is go to Device Manager. See if you have a driver issue. Your device may be sol old it's just not supported under Win11. I have a basket full of these things.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
I need to interface to a very simple device with a USB port on the older Win 7 machine the driver worked, all was good. PC gets changed and upgraded to 11. The software device get tricky to use, I implement a bodge that is documented, but not in the correct place, as I'm not allowed to update the documents, get told off for it as I have modded the software and not updated the documents, told to undo my mods which prevent crashes, Head interfaces to desk. I'm guessing the PC on which it worked was was USB 2, but the powers that be dictate it has to be a touch PC connecting to the companny network able to run Epicore (why?), suddenly my software gets unreliable and starts to crash the device on the other end. As for the power issue, I have checked the power levels and the Hub it was plugged into sits at around 4.5 to 4.8 Volts on the power line, plugged in directly 5.02 Volts, there may be something it. The device appears in Dev Manager and at times disappears and reappears when connected to the hub directly to Com 1, it says connected permantly and it the device occasionally crashes.
-
-
Most of your comments make sense. Looking forward to learn new things here ;) Anyway in short: usbser.sys had/has? a lot of issues. Check the comments to this old question (was my old acount): Checking whether usbser.sys is still working/polling a COM port/CDC device[^]
Thanks for the link, could be a Microchip thinks it's an ATMEL
-
It's sometimes hard to say what is windows versus what is a device manufacturer doing something in their driver. I'm pretty sure I have had Windows 10 tell me I was pulling too much current on the USB and shut the port down temporarily (not a timer - it tells you to go turn it back on if it's OK).
Lost a couple of hours to that this afternoon!
-
Slot in a powered hub? Or I think they still make power injectors - signals straight through, solid +5 comes in the side.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
I will try that... have search my pile for an 9way RS232 cable, 'we don't have those things, why do you want one?'from IT... it gets worse! :omg:
-
Thanks for the link, could be a Microchip thinks it's an ATMEL
Unfortunately the most intersting link (http://www.microchip.com/forums/download.axd?file=0;538194[^]) is not longer available :( That was an explanation of the low level stuff. Maybe I saved some parts of that link, I will search for it. On the other hand, it was before >10 years. Maybe @charlieg has better information. I'm keen on his advices ;)
-
Unfortunately the most intersting link (http://www.microchip.com/forums/download.axd?file=0;538194[^]) is not longer available :( That was an explanation of the low level stuff. Maybe I saved some parts of that link, I will search for it. On the other hand, it was before >10 years. Maybe @charlieg has better information. I'm keen on his advices ;)
Nuts, it would be useful, at least it's not my dodgy code ;)
-
I need to interface to a very simple device with a USB port on the older Win 7 machine the driver worked, all was good. PC gets changed and upgraded to 11. The software device get tricky to use, I implement a bodge that is documented, but not in the correct place, as I'm not allowed to update the documents, get told off for it as I have modded the software and not updated the documents, told to undo my mods which prevent crashes, Head interfaces to desk. I'm guessing the PC on which it worked was was USB 2, but the powers that be dictate it has to be a touch PC connecting to the companny network able to run Epicore (why?), suddenly my software gets unreliable and starts to crash the device on the other end. As for the power issue, I have checked the power levels and the Hub it was plugged into sits at around 4.5 to 4.8 Volts on the power line, plugged in directly 5.02 Volts, there may be something it. The device appears in Dev Manager and at times disappears and reappears when connected to the hub directly to Com 1, it says connected permantly and it the device occasionally crashes.
if you can tell us, what is the USB device? I support or will have supported WinCE devices going back to the earl 2000s. One set of code builds in Xp, debugs in Xp, and I have to remind myself that Xp does not support USB 3.0. If you saw all the cables hanging off the side of my desk..... anyway, sometimes I try to mount usb 3.0 devices inside of my Xp VM. 3 hours of head banging later, I pick the correct device. I have serial, ethernet, RS485 and a few other things. If it is USB 2.0, get a new USB 2.0 hub that has a host USB 3.0 interface.... this smells like a driver issue. Trying to use the old USB 2.0 device in a Windows 11 machine (touch has NOTHING To do with it) simply may not work.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
Nuts, it would be useful, at least it's not my dodgy code ;)
make sure you are checking EVERY return status. Since we have no idea what this USB device is (you can go ahead and admit it's a serial interface ;)), I have found that software people have far more faith than most devout believers.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
if you can tell us, what is the USB device? I support or will have supported WinCE devices going back to the earl 2000s. One set of code builds in Xp, debugs in Xp, and I have to remind myself that Xp does not support USB 3.0. If you saw all the cables hanging off the side of my desk..... anyway, sometimes I try to mount usb 3.0 devices inside of my Xp VM. 3 hours of head banging later, I pick the correct device. I have serial, ethernet, RS485 and a few other things. If it is USB 2.0, get a new USB 2.0 hub that has a host USB 3.0 interface.... this smells like a driver issue. Trying to use the old USB 2.0 device in a Windows 11 machine (touch has NOTHING To do with it) simply may not work.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
Oh, thank you, you have said what I was thinking. Driver issue, If I run the device with lots of message box and delays (Thread.Sleep's) it will go wrong less. Take out the prompts slow down so it runs at full speed the unit crashes the device. With my slow downs the driver will crash and the device go 'hay wire' but it works.
-
make sure you are checking EVERY return status. Since we have no idea what this USB device is (you can go ahead and admit it's a serial interface ;)), I have found that software people have far more faith than most devout believers.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
Yes, its a dodgy com port ( :sigh: ) I think people were expecting it run like native USB.
-
make sure you are checking EVERY return status. Since we have no idea what this USB device is (you can go ahead and admit it's a serial interface ;)), I have found that software people have far more faith than most devout believers.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
You have a serial port which is native a usb, but for your app it is still a serial port: What 'return status' you think you can check, other than the ones from the serial port? In such a case you simply rely on usbser.sys! Sorry, but
Quote:
I have found that software people have far more faith than most devout believers.
is wrong and is just striking. It looks like you just want to appear omniscient here ;)
-
Oh, thank you, you have said what I was thinking. Driver issue, If I run the device with lots of message box and delays (Thread.Sleep's) it will go wrong less. Take out the prompts slow down so it runs at full speed the unit crashes the device. With my slow downs the driver will crash and the device go 'hay wire' but it works.
Please stay away from Thread.Sleep, Application.DoEvents and similar. Let the serial port communicate in a proper way. Read this again ;): Serial Comms in C# for Beginners[^] ;) Here especally how you handled 'private void port_DataReceived_1(object sender, SerialDataReceivedEventArgs e)' ;)
-
Please stay away from Thread.Sleep, Application.DoEvents and similar. Let the serial port communicate in a proper way. Read this again ;): Serial Comms in C# for Beginners[^] ;) Here especally how you handled 'private void port_DataReceived_1(object sender, SerialDataReceivedEventArgs e)' ;)
Oh dear :bob:! I wasnt thinking of that, I will have a better look over the weekend. A timer. and the eNums oh heck!
-
Oh dear :bob:! I wasnt thinking of that, I will have a better look over the weekend. A timer. and the eNums oh heck!
-
If I only could directly contact that Guru, all my problems would be solved! :laugh: