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

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

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

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

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

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

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

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

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

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

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 !

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

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...

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

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.

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

Through a bit of reverse engineering and an old Laptop running Win XP and Network Monitor 3.4, I've discovered a number of issues, but now have it working over LAN with a plugin I have written for my automation test suite. It basically uses raw UDP packets for both discovery and command/query. The discovery is done on port 18191 and the command/query is on the port you set (default 18190).

The Test Connection tool basically uses INET_BROADCAST (255.255.255.255) which doesn't work on anything newer than WinXP SP3, unless your luck and the first network adaptor in your PC is handling the broadcast. If not, then the adaptor doesn't forward it on to the network! Tried altering static routing i my Win7 Pro machine, but that made no difference. The answer is to query the adaptor for the net-mask and create the broadcast address based on that plus your local host IP address (i.e use the subnet-broadcast for the active adapter).

Has been reported to both Farnell tech support and KORAD support, so hopefully, they fix that one!

Broadcast address forwarding was quite ubiquitous until a few years ago. In a test equipment connected to a network segregated from the internet, I think that safety concerns can be minimized.

My guess is that the firmware was tested only with Windows XP and never touched again. Hopefully they address this, but TBH I wouldn't hold my breath.

Some details about broadcasting on Windows XP and 7 that may be interesting:

https://social.technet.microsoft.com/Forums/windows/en-US/72e7387a-9f2c-4bf4-a004-c89ddde1c8aa/how-to-fix-the-global-bro…