Actions
Forum Thread Details
  • Replies 5 replies
  • Subscribers 353 subscribers
  • Views 2340 views
  • Users 0 members are here
Related

Need Windows 10 USB driver for TENMA 72-2930 PSU

kevin014

Hi,

 

I am trying to get my TENMA 72-293072-2930 Programmable DC Power Supply to show up as a USB device so that I can control it in LabVIEW.

 

I tried installing the USB driver from here, but the device still shows up as "Unknown USB Device (Configuration Descriptor Request Failed)".

I also followed the instructions from this post, but this didn't solve the issue.

 

Where I can find the correct USB driver for my PSU?

 

Thanks

  • "Unknown USB Device (Configuration Descriptor Request Failed)" normally points to a USB communications issue and is not necessarily driver related.

     

    I'd first try a different cable and see if it resolves the issue. Perhaps try a different port and not going through any hubs. If not, it could be that your particular USB controller has compatibility issues (I've met some devices that just wouldn't work on one PC but were fine on another), so perhaps also try plugging it into another PC.

     

    Configuration Descriptor Request Failed normally means that the USB controller on the PC couldn't request the necessary data to set up the USB device in the first place. The device has to be configured correctly on the bus before a driver can take over, so it's almost certainly a lower-level issue than that of the PSU driver. Perhaps you may need to update the USB drivers for your particular host controller on your PC.

     

    - Gough

  • in reply to Gough Lui

    Hi Gough,

     

    Thanks for the pointers. I tried a different cable and different ports, but this didn't fix the issue. I have yet to try this on a different PC with Windows 10 installed so this will be my next step.

    I also have a TENMA load bank which is using a KORAD USB driver, and this is detected and works as expected on all ports.

     

    I am doubtful if the issue is to do with my laptop's USB controller like you are suggesting as sometimes the PSU shows up with a different name but still cannot be communicated with. I'll have to get it to show up again under this name so that I can post some screenshots here.

     

    I find it a bit strange that a device advertised as programmable does not ship with a USB driver, and there is no official documentation on the issue.

  • in reply to kevin014

    Well, the other possibility is that the device itself doesn't have a correctly programmed USB controller or out of tolerance timing crystal. I've met some faulty devices that provoke such errors. I've also met it while trying to use devices through VMs. But until the device can be properly enumerated, no amount of driver twiddling is likely to solve it as the error still implies a problem with communication at the fundamental level required to "onboard" the device onto the USB bus and then the driver takes over communicating with the endpoints on the device.

     

    Unfortunately, with lower cost "programmable" devices, they are not always of high quality, not exactly well supported a lot of the time and use strange custom protocols (some use variants of AT commands for example, instead of SCPI). Best of luck nonetheless.

     

    - Gough

     

    EDIT: In case you are not familiar with the steps taken to enumerate and onboard a USB device onto the bus, a simplified explanation from FTDI is given here: https://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_113_Simplified%20Description%20of%20USB%20Device%20Enumeration.pdf

  • in reply to Gough Lui

    I got in contact with technical support and they sent me a USB driver for this device which works, and now I am up and running.