44 Replies Latest reply on Nov 12, 2018 1:37 PM by rsjsouza

    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?

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

          This is quite similar to the Korad KEL-103, but even this model does not have drivers on its website and its manual makes no mention of the USB.

           

          When you connect it to the host, what kind of device is enumerated? Is it a standard USB-RS232 port from FTDI, Prolific or other?

           

          If nothing shows up, then it is possible the USB is either non-functional or fictitious.

          2 of 2 people found this helpful
          • Re: Need Windows USB Driver for TENMA 72-13210 (electronic dc-load 30A/120V 300W)
            lui_gough

            It would be good to know what the PID/VID combination of the USB device is. Under Windows, you can find this in the Device Manager in the properties for the Unknown Device under Details (Tab) / Hardware ID (Property). If you have Linux, it may even be better to run lsusb -vv and provide us the results.

             

            It could be a USB to Serial adapter as many lower-end units may have - depending on which chipset, you might need drivers from FTDI, Prolific, SiLabs, WinChipHead amongst others.

             

            If it is a "higher end" unit, it could actually be a USB Test and Measurement class device, which will need a VISA layer installed as the IVI driver comes bundled with the VISA layer. You could try National Instruments VISA (NI-VISA), although other VISA implementations are available (e.g. Keysight I/O Libraries, R&S VISA, Tek VISA, etc). Otherwise, it may be possible to use something like pyhon-usbtmc under Linux.

             

            Unfortunately, without further information such as a programming manual that lists the commands, their format and their values ... it's not going to be easy to get this to work. Ironically, you may end up learning more about the device if it has LXI-compatible LAN, which you can probably learn some details about the commands from. I wonder if there's even anything useful on the supplied CD - but not owning such a unit, I have no idea.

             

            Maybe if you could list the files on the CD, that could help as well.

             

            - Gough

            2 of 2 people found this helpful
              • Re: Need Windows USB Driver for TENMA 72-13210 (electronic dc-load 30A/120V 300W)
                simonwahlmann

                Thanks for your reply!!!

                 

                Well there are two different entries for each of the two devices:

                Device 1 "SZ KORAD USB Mode"

                     USB\VID_0416&PID_5011&REV_0200&MI_00

                     USB\VID_0416&PID_5011&MI_00

                 

                Device 2 "SZ KORAD USB Mode"

                     USB\VID_0416&PID_5011&REV_0200&MI_01

                     USB\VID_0416&PID_5011&MI_01

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

                    From some quick digging, it seems that the PID/VID belong to Winbond/Nuvoton and likely is a virtual COM port:

                     

                    0x0416    0x5011    Winbond Electronics Corp.  Virtual Com Port

                     

                    It doesn't seem drivers for this are available online - the only reference I found was this Chinese site which needs a login, but if it is USB CDC-class compliant, it should install automatically (similarly to Arduino Leonardo boards). Otherwise, it could be some very small .inf files on the CD-ROM that will be the appropriate drivers - if you can, could you list all the files/explore the CD-ROM? You can do that using the Command Prompt under Windows with the following command (assuming D: is your CD-ROM drive, creating a file called listing.txt in the current directory):
                    tree /f D: > listing.txt

                    and upload the list here?

                     

                    - Gough

                    2 of 2 people found this helpful
                      • Re: Need Windows USB Driver for TENMA 72-13210 (electronic dc-load 30A/120V 300W)
                        simonwahlmann

                        Here we go - (sorry didn't find a way to attache the text-file)

                         

                        I do recognize some visa files...

                         

                        BR Simon

                         

                        E:\

                        ³   72-13210 Communication Commands with Computer.pdf

                        ³   USB Driver installation.pdf

                        ³  

                        ÃÄÄÄSoftware

                        ³   ³   nidist.id

                        ³   ³   setup.exe

                        ³   ³   setup.ini

                        ³   ³  

                        ³   ÃÄÄÄbin

                        ³   ³   ÃÄÄÄdp

                        ³   ³   ³       data.cab

                        ³   ³   ³       DevPartDef.xml

                        ³   ³   ³       install.msi

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp0

                        ³   ³   ³   ÀÄÄÄMU

                        ³   ³   ³           MetaUninstaller.msi

                        ³   ³   ³           MetaUninstallerR1.cab

                        ³   ³   ³           MetaUninstaller_mft.cab

                        ³   ³   ³          

                        ³   ³   ÃÄÄÄp1

                        ³   ³   ³       EULADep2.cab

                        ³   ³   ³       EULADepot2.msi

                        ³   ³   ³       EULADepot2_mft.cab

                        ³   ³   ³       NIYouLAs.bin

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp10

                        ³   ³   ³       CVI_LowLevelDriverOriginal.msi

                        ³   ³   ³       CVI_LowLevelDriverOriginal_mft.cab

                        ³   ³   ³       CVI_LowLevelDriverUpdated.msi

                        ³   ³   ³       lldrvo.cab

                        ³   ³   ³       lldrvu.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp11

                        ³   ³   ³       niqpxi32.cab

                        ³   ³   ³       niqpxi32.msi

                        ³   ³   ³       niqpxi32_mft.cab

                        ³   ³   ³       niqpxi64.cab

                        ³   ³   ³       niqpxi64.msi

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp12

                        ³   ³   ³       NITra00.cab

                        ³   ³   ³       NITra01.cab

                        ³   ³   ³       NITraceEngine.msi

                        ³   ³   ³       NITraceEngine64.msi

                        ³   ³   ³       NITraceEngine_mft.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp13

                        ³   ³   ³       mDNSResponder.msi

                        ³   ³   ³       mDNSResponder_W64.msi

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp14

                        ³   ³   ³       NI_Sy00.cab

                        ³   ³   ³       NI_Sy01.cab

                        ³   ³   ³       NI_SysStatePub.msi

                        ³   ³   ³       NI_SysStatePub64.msi

                        ³   ³   ³       NI_SysStatePub_mft.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp15

                        ³   ³   ³       palerr.cab

                        ³   ³   ³       palerr64.cab

                        ³   ³   ³       palerri.msi

                        ³   ³   ³       palerri64.msi

                        ³   ³   ³       palerri_mft.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp16

                        ³   ³   ³       NIER_Interface.msi

                        ³   ³   ³       NIER_Interface64.msi

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp17

                        ³   ³   ³   ÀÄÄÄLVRT_00

                        ³   ³   ³           LVRT_00.cab

                        ³   ³   ³           LVRT_00_chs.mst

                        ³   ³   ³           LVRT_00_deu.mst

                        ³   ³   ³           LVRT_00_fra.mst

                        ³   ³   ³           LVRT_00_jpn.mst

                        ³   ³   ³           LVRT_00_kor.mst

                        ³   ³   ³           LVRT_NBFifo_2014.msi

                        ³   ³   ³           LVRT_NBFifo_2014_mft.cab

                        ³   ³   ³          

                        ³   ³   ÃÄÄÄp18

                        ³   ³   ³       niorb.cab

                        ³   ³   ³       niorb64.cab

                        ³   ³   ³       niorbi.msi

                        ³   ³   ³       niorbi64.msi

                        ³   ³   ³       niorbi_mft.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp19

                        ³   ³   ³       rpcSetup.msi

                        ³   ³   ³       rpcSetup64.msi

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp2

                        ³   ³   ³       VC2010MSMs_x64.msi

                        ³   ³   ³       VC2010MSMs_x86.msi

                        ³   ³   ³       VC2010MSMs_x86_mft.cab

                        ³   ³   ³       x64.cab

                        ³   ³   ³       x86.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp20

                        ³   ³   ³       niauth.cab

                        ³   ³   ³       niauth.msi

                        ³   ³   ³       niauth64.cab

                        ³   ³   ³       niauth64.msi

                        ³   ³   ³       niauth_mft.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp21

                        ³   ³   ³       nicurl.cab

                        ³   ³   ³       nicurl.msi

                        ³   ³   ³       nicurl64.cab

                        ³   ³   ³       nicurl64.msi

                        ³   ³   ³       nicurl_mft.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp22

                        ³   ³   ³   ÀÄÄÄsvcloc

                        ³   ³   ³           nisvcloc.msi

                        ³   ³   ³           nisvcloc_mft.cab

                        ³   ³   ³           svcloc.cab

                        ³   ³   ³           svcloc_chs.mst

                        ³   ³   ³           svcloc_deu.mst

                        ³   ³   ³           svcloc_fra.mst

                        ³   ³   ³           svcloc_jpn.mst

                        ³   ³   ³           svcloc_kor.mst

                        ³   ³   ³          

                        ³   ³   ÃÄÄÄp23

                        ³   ³   ³       nixerces27_win32.msi

                        ³   ³   ³       nixerces27_win32_mft.cab

                        ³   ³   ³       nixerces27_win64.msi

                        ³   ³   ³       Xerce00.cab

                        ³   ³   ³       Xerce01.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp24

                        ³   ³   ³       dimSetup.msi

                        ³   ³   ³       dimSetup64.msi

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp25

                        ³   ³   ³       nipal.cab

                        ³   ³   ³       nipal64.cab

                        ³   ³   ³       palSetup.msi

                        ³   ³   ³       palSetup64.msi

                        ³   ³   ³       palSetup64_chs.mst

                        ³   ³   ³       palSetup64_deu.mst

                        ³   ³   ³       palSetup64_fra.mst

                        ³   ³   ³       palSetup64_jpn.mst

                        ³   ³   ³       palSetup64_kor.mst

                        ³   ³   ³       palSetup_chs.mst

                        ³   ³   ³       palSetup_deu.mst

                        ³   ³   ³       palSetup_fra.mst

                        ³   ³   ³       palSetup_jpn.mst

                        ³   ³   ³       palSetup_kor.mst

                        ³   ³   ³       palSetup_mft.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp26

                        ³   ³   ³       LOGOS00.cab

                        ³   ³   ³       LogosXT.msi

                        ³   ³   ³       LogosXT64.msi

                        ³   ³   ³       LogosXT_mft.cab

                        ³   ³   ³       LOGOS_XT.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp27

                        ³   ³   ³   ÀÄÄÄLabVI00

                        ³   ³   ³           LabVI00.cab

                        ³   ³   ³           LabVI00_chs.mst

                        ³   ³   ³           LabVI00_deu.mst

                        ³   ³   ³           LabVI00_fra.mst

                        ³   ³   ³           LabVI00_jpn.mst

                        ³   ³   ³           LabVI00_kor.mst

                        ³   ³   ³           NIWebServer_LVRTE.msi

                        ³   ³   ³           NIWebServer_LVRTE_mft.cab

                        ³   ³   ³          

                        ³   ³   ÃÄÄÄp28

                        ³   ³   ³   ÀÄÄÄni_error

                        ³   ³   ³           ni_error.cab

                        ³   ³   ³           ni_error_chs.mst

                        ³   ³   ³           ni_error_deu.mst

                        ³   ³   ³           ni_error_fra.mst

                        ³   ³   ³           ni_error_jpn.mst

                        ³   ³   ³           ni_error_kor.mst

                        ³   ³   ³           ni_error_report.msi

                        ³   ³   ³           ni_error_report_mft.cab

                        ³   ³   ³          

                        ³   ³   ÃÄÄÄp29

                        ³   ³   ³       activ32.cab

                        ³   ³   ³       activ32_chs.mst

                        ³   ³   ³       activ32_deu.mst

                        ³   ³   ³       activ32_fra.mst

                        ³   ³   ³       activ32_jpn.mst

                        ³   ³   ³       activ32_kor.mst

                        ³   ³   ³       activ64.cab

                        ³   ³   ³       activ64_chs.mst

                        ³   ³   ³       activ64_deu.mst

                        ³   ³   ³       activ64_fra.mst

                        ³   ³   ³       activ64_jpn.mst

                        ³   ³   ³       activ64_kor.mst

                        ³   ³   ³       activex.msi

                        ³   ³   ³       activex64.msi

                        ³   ³   ³       activex_mft.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp3

                        ³   ³   ³   ÀÄÄÄVC2008MSMs

                        ³   ³   ³           VC2008MSMs_x64.msi

                        ³   ³   ³           VC2008MSMs_x86.msi

                        ³   ³   ³           VC2008MSMs_x86_mft.cab

                        ³   ³   ³           x64.cab

                        ³   ³   ³           x86.cab

                        ³   ³   ³          

                        ³   ³   ÃÄÄÄp30

                        ³   ³   ³       ni_ssl.msi

                        ³   ³   ³       ni_ssl64.msi

                        ³   ³   ³       ni_ssl_mft.cab

                        ³   ³   ³       ssl.cab

                        ³   ³   ³       ssl64.cab

                        ³   ³   ³       ssl64_chs.mst

                        ³   ³   ³       ssl64_deu.mst

                        ³   ³   ³       ssl64_fra.mst

                        ³   ³   ³       ssl64_jpn.mst

                        ³   ³   ³       ssl64_kor.mst

                        ³   ³   ³       ssl_chs.mst

                        ³   ³   ³       ssl_deu.mst

                        ³   ³   ³       ssl_fra.mst

                        ³   ³   ³       ssl_jpn.mst

                        ³   ³   ³       ssl_kor.mst

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp31

                        ³   ³   ³       tdms.cab

                        ³   ³   ³       tdms.msi

                        ³   ³   ³       tdms64.cab

                        ³   ³   ³       tdms64.msi

                        ³   ³   ³       tdms64_chs.mst

                        ³   ³   ³       tdms64_deu.mst

                        ³   ³   ³       tdms64_fra.mst

                        ³   ³   ³       tdms64_jpn.mst

                        ³   ³   ³       tdms64_kor.mst

                        ³   ³   ³       tdms_chs.mst

                        ³   ³   ³       tdms_deu.mst

                        ³   ³   ³       tdms_fra.mst

                        ³   ³   ³       tdms_jpn.mst

                        ³   ³   ³       tdms_kor.mst

                        ³   ³   ³       tdms_mft.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp32

                        ³   ³   ³   ÀÄÄÄMDF

                        ³   ³   ³           MDFSupport.msi

                        ³   ³   ³           MDFSupport1.cab

                        ³   ³   ³           MDFSupport_mft.cab

                        ³   ³   ³          

                        ³   ³   ÃÄÄÄp33

                        ³   ³   ³       mkl.msi

                        ³   ³   ³       MKL2000.cab

                        ³   ³   ³       MKL2000_chs.mst

                        ³   ³   ³       MKL2000_deu.mst

                        ³   ³   ³       MKL2000_fra.mst

                        ³   ³   ³       MKL2000_jpn.mst

                        ³   ³   ³       MKL2000_kor.mst

                        ³   ³   ³       MKL2014.cab

                        ³   ³   ³       MKL2014_chs.mst

                        ³   ³   ³       MKL2014_deu.mst

                        ³   ³   ³       MKL2014_fra.mst

                        ³   ³   ³       MKL2014_jpn.mst

                        ³   ³   ³       MKL2014_kor.mst

                        ³   ³   ³       mkl64.msi

                        ³   ³   ³       mkl_mft.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp34

                        ³   ³   ³       mxs.msi

                        ³   ³   ³       mxs1.cab

                        ³   ³   ³       mxs64.msi

                        ³   ³   ³       mxs_mft.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp35

                        ³   ³   ³   ÀÄÄÄlvrteres

                        ³   ³   ³           LV2014rteres.msi

                        ³   ³   ³           LV2014rteres_mft.cab

                        ³   ³   ³           lvrteres.cab

                        ³   ³   ³           lvrteres_chs.mst

                        ³   ³   ³           lvrteres_deu.mst

                        ³   ³   ³           lvrteres_fra.mst

                        ³   ³   ³           lvrteres_jpn.mst

                        ³   ³   ³           lvrteres_kor.mst

                        ³   ³   ³          

                        ³   ³   ÃÄÄÄp36

                        ³   ³   ³       logos.cab

                        ³   ³   ³       logos.msi

                        ³   ³   ³       logos64.cab

                        ³   ³   ³       logos64.msi

                        ³   ³   ³       logos64_chs.mst

                        ³   ³   ³       logos64_deu.mst

                        ³   ³   ³       logos64_fra.mst

                        ³   ³   ³       logos64_jpn.mst

                        ³   ³   ³       logos64_kor.mst

                        ³   ³   ³       logos_chs.mst

                        ³   ³   ³       logos_deu.mst

                        ³   ³   ³       logos_fra.mst

                        ³   ³   ³       logos_jpn.mst

                        ³   ³   ³       logos_kor.mst

                        ³   ³   ³       logos_mft.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp37

                        ³   ³   ³       LV2014rtdnet.msi

                        ³   ³   ³       LV2014runtime.msi

                        ³   ³   ³       LV2014runtime_mft.cab

                        ³   ³   ³       lvrte.cab

                        ³   ³   ³       lvrtenet.cab

                        ³   ³   ³       lvrte_chs.mst

                        ³   ³   ³       lvrte_deu.mst

                        ³   ³   ³       lvrte_fra.mst

                        ³   ³   ³       lvrte_jpn.mst

                        ³   ³   ³       lvrte_kor.mst

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp38

                        ³   ³   ³       MStudioCW3DGraph.cab

                        ³   ³   ³       MStudioCW3DGraph.msi

                        ³   ³   ³       MStudioCW3DGraph_mft.cab

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp4

                        ³   ³   ³       SigningCA.msi

                        ³   ³   ³       SigningFakeFeature.msi

                        ³   ³   ³       SigningMain.msi

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp5

                        ³   ³   ³       LegacyGPIBVXI.msi

                        ³   ³   ³       LegacyGPIBVXI1.cab

                        ³   ³   ³       LegacyGPIBVXI_chs.mst

                        ³   ³   ³       LegacyGPIBVXI_deu.mst

                        ³   ³   ³       LegacyGPIBVXI_fra.mst

                        ³   ³   ³       LegacyGPIBVXI_jpn.mst

                        ³   ³   ³       LegacyGPIBVXI_kor.mst

                        ³   ³   ³       NIVISAruntime.msi

                        ³   ³   ³       NIVISAruntime1.cab

                        ³   ³   ³       NIVISAruntime64.msi

                        ³   ³   ³       NIVISAruntime641.cab

                        ³   ³   ³       NIVISAruntime_chs.mst

                        ³   ³   ³       NIVISAruntime_deu.mst

                        ³   ³   ³       NIVISAruntime_fra.mst

                        ³   ³   ³       NIVISAruntime_jpn.mst

                        ³   ³   ³       NIVISAruntime_kor.mst

                        ³   ³   ³       NIVISAruntime_mft.cab

                        ³   ³   ³       visasc32.cab

                        ³   ³   ³       visasc64.cab

                        ³   ³   ³       VisaSharedComponents32.msi

                        ³   ³   ³       VisaSharedComponents64.msi

                        ³   ³   ³       VisaSharedComponentsWrapper32.msi

                        ³   ³   ³       VisaSharedComponentsWrapper64.msi

                        ³   ³   ³      

                        ³   ³   ÃÄÄÄp6

                        ³   ³   ³   ÀÄÄÄsslLVRTE

                        ³   ³   ³           sslLVRTE.cab

                        ³   ³   ³           ssl_LVRTEsupp.msi

                        ³   ³   ³           ssl_LVRTEsupp_mft.cab

                        ³   ³   ³          

                        ³   ³   ÃÄÄÄp7

                        ³   ³   ³   ÀÄÄÄNI_De00

                        ³   ³   ³           dep_framework.msi

                        ³   ³   ³           dep_framework_mft.cab

                        ³   ³   ³           NI_De00.cab

                        ³   ³   ³          

                        ³   ³   ÃÄÄÄp8

                        ³   ³   ³       rpcSetupLVRT.msi

                        ³   ³   ³      

                        ³   ³   ÀÄÄÄp9

                        ³   ³           KillBit.msi

                        ³   ³           KillBit64.msi

                        ³   ³           KillBit_mft.cab

                        ³   ³          

                        ³   ÃÄÄÄlicense

                        ³   ³       Apache 2.0 License - English.pdf

                        ³   ³       Boost 1.0 License - English.pdf

                        ³   ³       BSD 3-clause License - English.rtf

                        ³   ³       Code Project Open License - English.rtf

                        ³   ³       CryptoPP 5.6 License - English.pdf

                        ³   ³       FreeType License - English.txt

                        ³   ³       GNU Lesser General Public License 2.1 - English.rtf

                        ³   ³       IVI Foundation Inc License Agreement - English.rtf

                        ³   ³       LLVM License - English.rtf

                        ³   ³       MARS 1.0 License - English.pdf

                        ³   ³       MD5 Message Digest Algorithm License - English.rtf

                        ³   ³       Microsoft Limited Public License MSDN - English.rtf

                        ³   ³       Microsoft Platform SDK Server 2003 SP1 License - English.rtf

                        ³   ³       Microsoft Public License_license.pdf

                        ³   ³       Microsoft Windows Driver Kit License - English.rtf

                        ³   ³       MIT 1.0 License - English.rtf

                        ³   ³       MIT-X License.rtf

                        ³   ³       MIT-X YAJL Style License.rtf

                        ³   ³       Mozilla Public License 2.0.rtf

                        ³   ³       NI Released License Agreement - English.rtf

                        ³   ³       NI Released License Agreement - French.rtf

                        ³   ³       NI Released License Agreement - German.rtf

                        ³   ³       NI Released License Agreement - Italian.rtf

                        ³   ³       NI Released License Agreement - Japanese.rtf

                        ³   ³       NI Released License Agreement - Korean.rtf

                        ³   ³       NI Released License Agreement - Simplified Chinese.rtf

                        ³   ³       NI Released License Agreement - Spanish.rtf

                        ³   ³       NICTA 1.0 License - English.pdf

                        ³   ³       OPC Classic COM License - English.pdf

                        ³   ³       OpenSSL 1.0 License - English.pdf

                        ³   ³       STLPort 1.0 License - English.pdf

                        ³   ³       UPX 1.0 license - English.pdf

                        ³   ³       WordNet 2.1 License - English.txt

                        ³   ³       wxWindows 3.1 License - English.pdf

                        ³   ³       zlib License - English.pdf

                        ³   ³      

                        ³   ÀÄÄÄsupportfiles

                        ³           customResource0009.dll

                        ³           merged.cab

                        ³           niPie.exe

                        ³           nistdtrans0007.mst

                        ³           nistdtrans0012.mst

                        ³           nistdtrans0017.mst

                        ³           nistdtrans0018.mst

                        ³           nistdtrans2052.mst

                        ³           nistdtransbase.mst

                        ³           updateInfo.xml

                        ³          

                        ÀÄÄÄTest Command

                                72-13210.exe

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

                            It looks like mostly an old version of NI-VISA but hey - at least the 72-13210 Communication Commands with Computer.pdf and USB Driver installation.pdf look interesting. What do they tell you about installing the driver? I also suspect Test Command\72-13210.exe could be an installer bundle that contains a basic remote control application and driver bundled together (fingers crossed) so could be worth examining.

                             

                            Otherwise, do install NI-VISA (probably best from National Instruments directly for the latest/most stable version) and see if the IVI driver picks up your electronic load. If it does, then it will become a USB Test and Measurement Device (IVI) - from my machine:

                            While the CD does seem somewhat confusing, don't write it off just yet . Best of luck.

                             

                            - Gough

                            1 of 1 people found this helpful
                              • Re: Need Windows USB Driver for TENMA 72-13210 (electronic dc-load 30A/120V 300W)
                                simonwahlmann

                                Thanks Gough,

                                well

                                1. NI LabView 2018 is already freshly installed including all updates an doesn't recognize the device at all.
                                2. The "USB Driver installation.pdf" is worthless, because it claims the driver would be on the CD but obviously isn't.
                                3. The executable "Test Command\72-13210.exe" is the test-program I metionned in the update of my question and is no installer but really just to test the connection sending the commands described in "72-13210 Communication Commands with Computer.pdf".

                                 

                                One thing I did recognize at second view of the "USB Driver installation.pdf" is that the driver should be a "nuvoton virtual com port" driver. This is visible on one of the screenshots. Also The OS of the given example is Windows XP. So all in all this is a quiet old description.

                                 

                                I managed to download such a driver from nuvoton as mentionned here

                                 

                                     NuTiny-SDK-N76E003-V2.1 Virtual COM port issues ? - NuForum

                                 

                                     Driver:

                                     http://www.nuvoton.com/hq/resource-download.jsp?tp_GUID=SW0520150729202535

                                 

                                but it didn't work yet.

                                 

                                Any further ideas?

                                 

                                BR Simon

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

                                    What does Farnell's tech help say about this - they really ought to be able to come up with something.

                                     

                                    Are you able to try the LAN port ?

                                     

                                    A lot of things default to port 5025 for SCPI commands.

                                     

                                    If the load is any good it's pretty cheap even if you have to buy a USB <-> RS232 converter as well, although you really shouldn't have to.

                                     

                                    MK

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

                                      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

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

                                        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 !

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

                                            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

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

                                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!

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

                                    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.

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

                                      The use of UDP for remote control commands seems a bit unusual and potentially unreliable (although, in reality on a non-congested network it probably will work okay). Not the best design and not something I've seen before - what a surprise!

                                       

                                      - Gough

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

                                          I agree that it is very unusual to use UDP but  I think it is the ideal protocol to support SCPI style commands.

                                           

                                          Pretty much everyone else uses TCP/IP and sockets, which is a streaming protocol and a fairly poor fit with the discrete message format of SCPI. In order to support the features of TCP/IP they frequently end up with a complex OS on an instrument with no other need for it - with all the attendant problems of maintenance and security..

                                           

                                          A really good reason for using just UDP is the simplicity possible in the test gear software - this can be used to achieve very fast performance (not relevant in this case) or very low cost of implementation (probably why used in this case) or very good stability/predictability/security of the software.

                                           

                                          It is a great shame that the Tenma PSU isn't better documented - that seems to be the biggest shortcoming and it would be so cheap an easy to put right.

                                           

                                          MK

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

                                              Its certainly easy to implement and as every command (which has no response) has a matching query (returns the set data), so its easy enough to write then query the setting to ensure its been received and set.

                                              I agree the documentation is a joke. Much of it doesn't make sense and the examples in the 'steps' don't reflect what you would see on the display. I've figured it all out by writing my own LAN application and 2 days playing around with the unit to work out exactly how the battery and pulse functionality works and the manual does not reflect what it does or can do!

                                               

                                              <rant>

                                               

                                              Element14 need to step up their game if they want to take a product and slap their brand on it. Documentation is useless, software does not work out of the box (unless you have Win98 or WinXP!), No USB drivers supplied and the ones that have been by support and KORAD still don't work and the lack of documentation regarding the programming is diabolical.

                                               

                                              I've essentially had to reverse engineer a brand new product in order to get it working for me! I say brand new, but it has been out as the KORAD KEL-103 since last year and passed its EMC for export back in Dec 2017 ... so its not new, its a mature product!

                                               

                                              </rant>

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

                                                I agree that UDP is much simpler in implementation, and could be faster (which is one reason I do use it for some data acquisition tasks), but if we account for all the nasty things UDP could have happen to it, then it's not so clear, especially if sending SCPI commands over the link.

                                                 

                                                For example, if we are sending an enquiry, then that's no big deal as we know if it succeeded depending on whether a reply was received. No reply, retry again.

                                                 

                                                But some other SCPI commands are more problematic - for example, setting a parameter where no reply is expected. You could query the device to check the present value, but that now adds overhead which you wouldn't have with TCP as you know the device has got it based on packet-level acknowledgement. Likewise, unlike GPIB, there is no dedicated lines for the instrument requesting attention from the host (SRQ), so if this is being emulated over UDP, there's a chance that such requests could go missing.

                                                 

                                                Another issue is that UDP could be dropped/re-ordered in transit and does not guarantee any reassembly order. Perhaps the instrument is streaming a chunk of data back to the machine that spans multiple packets. If anything gets reordered, your data will probably be hosed depending on what format it is. Other times, maybe you need to rapid-fire configure the device through setting mode, setting values, etc - if the instrument receives the commands in the wrong order, then it may not accept the command as it's not in the right mode.

                                                 

                                                While TCP is heavier, there are chips with basic TCP stacks onboard and it can be handled by some low-cost micros without great difficulty especially when we're talking about a device that may need to be configured only occasionally and have read-outs every second or so. It adds peace of mind that things remain ordered and that commands are sent or received as expected. With the lack of state on UDP-based connection, the instrument could be lost/powered down and the software has no timely way of knowing except to retry and time-out after not hearing a response.

                                                 

                                                Of course, for something simple like this, I don't see it as a major problem, but I'd rather things stick with the "standard" so as to avoid making integration more difficult than it should be. I have a set of power supplies that use AT commands for configuration, but without line termination ... instead detecting the end of a command through a time-out. Needless to say, this was a rather annoying thing to get used to ... I very much prefer my USB-TMC/LXI-LAN capable PSU over that.

                                                 

                                                - Gough

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

                                                    You are not quite clear here:

                                                     

                                                     

                                                    Another issue is that UDP could be dropped/re-ordered in transit and does not guarantee any reassembly order. Perhaps the instrument is streaming a chunk of data back to the machine that spans multiple packets. If anything gets reordered, your data will probably be hosed depending on what format it is. Other times, maybe you need to rapid-fire configure the device through setting mode, setting values, etc - if the instrument receives the commands in the wrong order, then it may not accept the command as it's not in the right mode.

                                                     

                                                     

                                                    In an RFQ compliant system:

                                                     

                                                    A multi fragment UDP will be received complete, fragments in order or not at all.

                                                    UDPs may not be received in the order they were transmitted.

                                                     

                                                    There is no re-assembly of packets. Of course if you devise a multiple UDP protocol it's up to you to keep the messages in order (in real life I've NEVER seen a single switch re-order UDPs, although I've often seen them dropped.) If you sent such messages to a remote location through complex routes and multiple routers it can happen. The implication of this is that your top level protocol must deal with out of order UDPs but in sensible case this is not very hard to do.

                                                     

                                                    SCPI is not the ideal high level protocol for UDP (or TCP/IP) (or probably anything else but it's what we are stuck with.) Instruments quite often seem to ignore commands, so regular status checking as Simon describes is a good plan even when TCP is used.

                                                     

                                                    In real life I've had fewer problems with UDP based systems than with TCP/IP, but I agree that it's a pain when one manufacturer goes a different way from (nearly) all the others.

                                                     

                                                    MK

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

                                                        A multi-fragment UDP would be a single transmission that contains more than the maximum payload for a single packet (MTU - headers). However, there is a size limit to even this fragmented UDP of about 64kB. As it now requires multiple packets to make it in transit for an "all or nothing" scenario, it is a bit risky.

                                                         

                                                        However, some instruments may return their data one line at a time (e.g. a matrix data dump from a VNA) which if it exceeds this size, would (theoretically) require either multiple UDP transmissions (each which could suffer re-ordering or dropping). Likewise, when sending SCPI commands, unless you are concatenating multiple commands into a single "line" using the semicolon, each command may be sent in its own transmission, occupying a single packet at a time. I tend to prefer sending each line separately (e.g. "TRIG:SOUR BUS" and "RANG:DC:AUTO ON" being two separate messages for example) as some instruments have very limited buffer room for parsing commands - if each of these are sent in separate UDP packets, there could be reordering as a result.

                                                         

                                                        I've seen packets dropped and I've seen them reordered but only under very specific scenarios. One way this can be achieved is when the packets have to traverse a stressed routing queue into a router which may have load-balancing across several paths to the same destination. Very unlikely for most applications, but still a possibility.

                                                         

                                                        Status checking is always a good idea but one I rarely use it out of laziness Something I should probably change I've never had too many dramas with TCP/IP aside from occasional hiccups due to transport layer packet drops and retries but that's by design I like UDP too especially for streaming raw data where losses won't matter But doing remote commanding just seems somewhat non-ideal But then again  RS-232RS-232 never had any acknowledgements either .

                                                         

                                                        - Gough

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

                                                            I think it's easy to get lulled into a false sense of security when talking to instruments in a lab - on a nice small, fast and closed network everything Ethernet works really nicely and the reserve capacity is huge. I find that in my own lab sending a UDP to an instrument is just as reliable as using a direct wired connection - but put that same thing out on decent sized factory's network and it's a different story.

                                                             

                                                            I see you are about to play with the Hameg/RS 4 channel power supply -  it seems to be SCPI over TCP. Their example code illustrates the problem you mentioned -

                                                            they use INST OUTx to select channel

                                                            and then maybe set the current using CURR i,

                                                            check with CURR?,

                                                            and it replies with i,

                                                            if it missed the INST OUTx you would have set and checked the current on an unknown channel.

                                                             

                                                            MK

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

                                                                Totally agree. I even get away with running sensors on UDP from ESP8266 boards over Wi-Fi and maybe see one or two lost packets a day on a one-packet-per-second rate. It's especially nice when sending to broadcast to allow multiple network users to access the latest readings from my outdoor weather station. When I bought the same prototype to a busy hospital - aside from being kicked from the APs due to deauthentication to protect from rogue wireless devices, even inside meeting rooms, the interference was enough to cause noticeable loss of packets. I've also met some consumer Wi-Fi gear that couldn't handle high rate UDP in any way - 7 packets per second was all it would do before choking up. No wonder I couldn't get any VoIP working over that unit!

                                                                 

                                                                The Hameg/RS supply should very much be capable of standard SCPI direct (5025/TCP). I guess checking helps, but so does concatenating commands so (hopefully) the instrument either gets the whole batch and actions it, it gets lost in transit entirely, or it "beeps" (or something to that effect) and logs a SCPI error to say it's not happy. Something akin to sending "INST OUT1;CURR i" should be valid SCPI syntax, albeit one I've never tried until I thought about this issue just now!

                                                                 

                                                                Thanks for the discussion though - I think we both agree that it's odd but for many cases, UDP will work although.

                                                                 

                                                                - Gough

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

                                                    cstanton  Hi Chris, Are you able to get one of your colleagues to provide drivers and USB installation instructions for Simon?

                                                     

                                                    Hopefully it's not a tricky one where one has to install the USB drivers prior to plugging in for the first time.

                                                     

                                                    Thanks!

                                                     

                                                    Compact

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

                                                        > Hi Chris, Are you able to get one of your colleagues to provide drivers and USB installation instructions for Simon?

                                                         

                                                        The stellar efforts by the persons involved in this thread has practically exhausted every avenue I can already attempt.

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

                                                            Being a TENMA it's an Element14 product.

                                                            Can you contact your purchasing dept or TENMA branding dept to contact the actual manufacturer?

                                                            To simplify access for TENMA and other e14 brand support can e14 provide a tech support download page?

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

                                                                COMPACT , reading the thread above, it appears this has/is already being attempted via contacting Technical Support who have the appropriate contacts to do that.

                                                                 

                                                                element14 provides a limited technical support for the products that are distributed, and technical support requests for the products are monitored, assessed and reacted to via the technical support live chat, support and similar channels on the online store website.

                                                                 

                                                                The community team, nor social media team, have access to the system that the technical support use to monitor and log problems and reports of problems so it is the best way to try to get support like this so it's logged and fed back to the product managers, purchasing department, etc.

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

                                                                  Already spoken to Element14 support on numerous occasions and they supplied a new CD which still doesn't address the USB issue.

                                                                   

                                                                  I spend 3 days last week talking to KORAD (the manufacturer) and they were very supportive (supplied the CD image for the KEL-103) up to the point where I described the 2 devices in device manager (SZ KORAD USB Mode) and the LAN discovery tool not working on Win7/Win10. At that point they have stopped responding. I suspect they have had an oh s**t! moment and are currently trying to address the problems ... or at least you hope so!

                                                                   

                                                                  This should have been sorted out by Element14 quality and support BEFORE being released to customers!

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

                                                                      Keep chasing it up. It's possible that it's fallen off their radar.

                                                                      Korad's download tab for the DC Load on Korad's website is empty (& main URL koradtechnology.com seems not to exist).

                                                                      I had to download the manual from another source.

                                                                       

                                                                      Unless your problems are sorted out promptly you should be able to return the product because it is "Not fit for purpose".

                                                                      I fanned through the manual an it says nothing useful about the USB interface nor how to install the drivers. It says "Please refer to the Communication Protocol." which is ambiguous and meaningless.

                                                                       

                                                                      It's pretty disappointing considering I'm currently happy using a Korad (TENMA) PC programmable power supply with USB and RS232 interface.

                                                                       

                                                                      For highest quality customer service there's a saying that sums up the actions that should be followed: "TOFU - Take Ownership and Follow Up for your customers irrespective whether it's your area's responsibility or not."

                                                                      What you have experienced should not occur with one let alone two ISO900x accredited companies.

                                                                       

                                                                      BTW - These DC Electronic Loads are on special at e14 in Oz at the moment. Are you going to buy one Gough? Or will you hold off until Simon's problem is sorted.

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

                                                                So this may be a bit obvious but I have to ask.

                                                                You've tried running the setup.exe listed with CD contents ...??

                                                                 

                                                                It seems there are various msi and cab files which are windows based files to load something.

                                                                 

                                                                Mark

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

                                                                    The setup.exe just installs a NI Labview application to drive the Load remotely. But it only supports RS232 and USB (not LAN) and does not install any USB drivers, so the USB doesn't work on that application either. It does install a 2014 Labview core and VISA libraries, but the application doesn't actually use those!

                                                                     

                                                                    I have had an email from KORAD support saying that they have just supplied Farnell Tech Support with a solution. I don't know if thats the one that Farnell sent to me last week or something newer based on the detailed information I have supplied. If it's the one I got last week, that doesn't work either, so we'll wait and see if Farnell come up with something newer that finally addresses this.

                                                                    1 of 1 people found this helpful
                                                                      • Re: Need Windows USB Driver for TENMA 72-13210 (electronic dc-load 30A/120V 300W)
                                                                        mcb1

                                                                        Oh ...

                                                                         

                                                                        I've found hat the PID and VID direct Windows where to find the details for a device.

                                                                        Obviously it isn't working and most likely because of the hoops Windows would make the vendor jump through.

                                                                         

                                                                        Typically you can tell Windows that you're installing a generic device, and choose Com Port/Modem, which then allows you to get down to the actual file, but in your case it looks like the ini file isn't there.

                                                                        You can often default it to a COM port, and it will simply behave as one, but you'll need to set the speed.

                                                                         

                                                                        It's strange they have these two entries

                                                                        ³   ³       Microsoft Windows Driver Kit License - English.rtf

                                                                        ³   ³       OPC Classic COM License - English.pdf

                                                                        Hopefully they have a more user friendly solution.

                                                                         

                                                                        Mark

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

                                                                      Hi all

                                                                      i have finally got this all to work after some digging by Devinder from farnell tech suppoprt

                                                                      the zip file a pdf on how to resolve the usb in device manager

                                                                      and a folder with the serial port driver file

                                                                      all the best

                                                                      Chris

                                                                      3 of 3 people found this helpful