Actions
Forum Thread Details
  • State Verified Answer
  • Replies 45 replies
  • Answers 7 answers
  • Subscribers 362 subscribers
  • Views 13210 views
  • Users 0 members are here
Related

Need Windows USB Driver for TENMA 72-13210 (electronic dc-load 30A/120V 300W)

simonwahlmann

Dear all,

does anyone has an idea where to find the "windows usb-driver" for this device?

 

     TENMA 72-13210 (electronic dc-load 30A/120V 300W)

 

It's not present on the attached original CD and I also couldn't find it anywhere in the internet.

 

Thanks for your support!!!

 

UPDATE 17th of Sep. 2018

Thanks for your replies so far!!!

 

The device is listed twice at "other devices" when I plug in the usb-port:

     - SZ KORAD USB Mode

    -  SZ KORAD USB Mode

 

With a CD no driver but a list of commands to control the device is provided.

There is also a Windows executable for a connection test. Its frontend shows three tabs, one for each communication port

     - Ethernet

     - RS232

     - USB

The USB obviously didn't work, because the devices had no drivers installed.

Using an rs232 to usb adapter I was able to control the device via the RS232 port. The device was then listed as "USB Serial Port (COM11)" with an FTDI driver being used.

This might be a workaround but I need to decide whether or not to oder more of these devices. So an inusable usb-port will influence my decission.

 

I tried out some random usb drivers ending up with an immediate system shutdown.

 

What else could I try?

  • 0 in reply to simonwahlmann

    I have examined the drivers and they are as I expected - just basic INFs to get a USB CDC recognized with Windows' own usbser.sys driver. Unfortunately the ones there have NOT got your VID/PID pair covered, hence you probably don't see any difference with the install of the drivers as they won't be picked up.

     

    I've modified the inf to cover your VID/PID pair and uploaded the pair of files. Please unzip into a folder, head to the "Unknown Device" in Device Manager, choose to select driver manually/have disk from the location, then select the resulting device and install. Ignore any errors about signing issues with the driver (which may occur as I have modified the .inf). As I don't have the device in question, I have no idea whether this will or will not work, or whether it will even install, but it's worth a shot.

     

    - Gough

    Attachments:
    VCOM-Modified-by-GoughLui.zip
  • 0 in reply to simonwahlmann

    Just had mine delivered today! Have you had any luck with USB drivers or LAN?

     

    The 72-13210.exe test tool doesn't discover the Load using the 'Network Debugger' tab, although I can Ping the IP address and get a response, so its on my network!

     

    Bit disappointed to be honest, my whole test setup is automated over LAN. USB I could have worked with, but when neither seem to work out of the box (and no real supporting documentation), its quite frustrating. I've currently got an FTDI USB to RS232 adapter on the serial port and testing things out that way.

     

    It doesn't respond to the LXI Discovery tool over LAN either.

     

    I contacted Element14 Support this morning and they said they would get back to me once that have spoken to the supplier regarding the USB Drivers. That was before I tried the LAN ... so, will be contacting them again later!

     

    VCOM Drivers posted by Gough Lui only address one of the listed Serial devices (SZ KORAD USB Mode) and whilst the 72-13210.exe test tool discovers one port, it doesn't connect. Also editing to add the other USB desciptor (%DESCRIPTION% = NuvotonCDC_DEV, USB\VID_0416&PID_5011&MI_00) which Gough missed results in an error loading the driver!

     

    Starting to feel like I should have spend a bit more and bought something else.

     

    UPDATE - 18/09/2018 @ 22:45 : Contacted Tech Support at Farnell (Element14) twice this morning, both time they said they would get back to me today .... NOTHING! Did find a USB driver that is supplied with KORAD PSU's (and re badge'd as the Velleman PS3005D). The CD for that PSU has the same USB Driver instructions and the DC Load and the CD has the 'USB Driver' folder with a single .INF file (NuvotonCDC.inf). There is no .CAT file, so it just references standards builtin Windows USB drivers. HOWEVER ! Still doesn't work. Still errors when you try and install a driver for the second 'SZ KORAD USB Mode' device. So, back to the drawing board and waiting for Tech support to respond !

  • 0 in reply to sjbaxter

    Ah how unfortunate ... I thought I might have been onto something ... so it comes up as two ports is a bit unusual.

     

    Normally you can work with test instruments over LAN just by addressing commands straight to Port 5025 (SCPI Direct). You could perhaps try using PuTTY configured in the Raw mode to see if you can get any result from an *IDN?

     

    You could also try talking over the available port using PuTTY in the Serial mode by putting COM4 (or whatever the port number is) and a sensible baud rate. Many USB CDC peripherals ignore this, so you might be safe to try 9600, 19200, 38400, 57600 or 115200 and see if you can get a response either.

     

    Barring no response either way, perhaps you might need to check the newline termination. Some devices need \r\n, others like \n only. Further to that, some devices have timing requirements (i.e. command has to be delivered in a single "burst" rather than being interactively typed in) - so perhaps copying and pasting the command in and seeing if it makes any difference.

     

    It is rather surprising how much trouble you're all having ... a product shouldn't be like this ... *shakes head*.

     

    - Gough

  • 0 in reply to Gough Lui

    Hey Gough,

    thanks for your effort, I tried it but it doesen't work either.

     

    Currently I try to get the device controlled with LabView via rs232 using the rs232-usb adapter. That's the least that should work for me. Let's see...

  • 0 in reply to michaelkellett

    Unfortunately I haven't got a response yet, but let you know if it happens...

  • 0 in reply to Gough Lui

    The default LAN port is 18190 unless you set it to 5025 via the serial port.

     

    Trying LAN using PuTTY in RAW or Telnet mode are both unresponsive and the PuTTY window gets closed after about 10 seconds (connection timeout? connection closed by the Load??).

     

    PuTTY in Serial mode (set at the default 115200) works fine. Which is evident from the test application. This works at typing speed, so burst is not required.

  • 0 in reply to sjbaxter

    Maybe then it's using its own LAN protocol or has a timeout of sorts ... very unusual. All devices I've used tend to keep the TCP socket open forever, except for maybe when another open comes into the socket from another process. If the PuTTY window closes, it's usually a sign that the TCP connection was reset/closed by the peer (i.e. the load).

     

    Sorry I couldn't be of more help. Clearly this is an odd beast and the guys at element14/Korad will have to provide the details.

     

    - Gough

  • 0

    I've got a copy of the CD supplied with the KORAD KEL-103 (direct from KORAD support) and the 'USB driver' is under 'Software'. (Attached). Sadly, it doesn't do anything to improved the USB situation !!!

     

    I've also queried why there are 2 devices shown in the device manager and why the LAN doesn't work with the Assistant application, still waiting on feedback.

     

    Not heard anything from the 2 support chaps at Element14 that I reported the issues to yesterday and the day before! NOT IMPRESSED!

     

    Simon.

     

    UPDATE 20/09/2018 @18:47 :

     

    Hey, I discovered why the LAN discovery tool doesn't work! They discover the devices by broadcasting a UDP message with the string 'find_ka000' on port 18191.

     

    However, they use the IP address of 255.255.255.255 as the broadcast address. THIS DOES NOT WORK! They need to work out the broadcast address from the hosts IP address (your computer) and the network mask.

     

    Examples :

     

    Host IP = 10.0.0.56, Mask = 255.255.255.0 -> The broadcast address = 10.0.0.255.

    Host IP = 10.0.0.56, Mask = 255.255.0.0 -> The broadcast address = 10.0.255.255.

     

    255.255.255.255 would only work if your network mask is 0.0.0.0.

     

    The device then returns a UDP packet from each of the discovered device IP's to the host IP which contains a 48 byte long payload of...

     

    IPAddress<0x0A>MACAddress<0x0A>DevicePort<0x0A> and padded out with zeros (0x00).

     

    Example :

     

    10.0.0.200<Linefeed>7f-45-12-cd-89-a2<Linefeed>18190<Linefeed><Zeros>

     

    At least I'm half way to writing my own app to communicate over LAN :-)

     

    I'll relay this to KORAD tomorrow and see what their response is!

    Attachments:
    USB driver.zip
  • 0 in reply to sjbaxter

    If Korad is using a Dual RS-232/USB device (such as FT2232), then I would have expected to see two ports there. In the drivers directory, is there any .inf file? Perhaps you could try to find what are the driver files used (if it is something like ftdi*.sys or dll)

     

    I suspect the OEM never cared to test/implement this functionality, or the precise model was not supposed to have programmability enabled (another thread comes to mind in this regard, where minimal changes on the model number make the whole difference). That or the manufacturer forgot to flash the microcontroller or USB bridge IC that performs this functionality.

     

    At any rate, good luck with your investigation.

  • 0 in reply to rsjsouza

    They don't use a USB to UART converter (like FTDI), the USB DP and DM go straight into the STM32F107 microprocessor, so all the USB is hosted in the application firmware.

     

    For info, they also seem to use a Texas Instruments DP83848 Transceiver for the LAN PHY and the Ethernet stack is also in their application firmware.

     

    I have Element14 sending me another CD, so we'll see what that has to offer!