Finally! Hantek HDM3065 6.5 Digit DMM

[infino]

I've posted the link for the FW above, just check the earlier messages.

Thank you, I saw your files, but I thought there might be something more recent, and my multimeter didn’t want to update. The problem turned out to be that it requires a 2GB flash drive — it could see my 8GB one, but it wouldn’t update from it. And nowadays, it’s not so easy to find a 2GB flash drive )).
I updated the device, everything is working perfectly. Thank you for your help

[infino]

After almost a year of using the device, it stopped saving settings and screenshots to an external USB flash drive. When a flash drive is connected, the device reports that a U-disk is connected, but it does not save any data. It also does not save measurement results or settings to the internal memory. Has anyone encountered a similar issue? Thank you.

[infino]

I’ll answer my own question. For those who have this device, it’s a good idea to save the calibration settings to a USB drive for future use. To do this, insert a USB drive with a capacity of up to 2 GB, then press the Shift button followed by OK (you can also try holding the buttons). The settings will be saved to the USB drive as .ini files.

The manufacturer also provided software with firmware for recovery. To put the device into boot mode, with the device powered off, hold the DCV button and the “-” key, then turn it on — it will enter boot mode. After that, connect it to a computer via USB and run the manufacturer’s software. The script mfgtool2-yocto-mx-evk-nand.vbs will start, and the program will automatically reflash the NAND memory. Once the process is complete, the device will be restored.

After that, you should install the latest firmware and restore the calibration settings or recalibrate the device

[infino]

Hello everyone who’s reading this—though for now I’m replying to myself.

As I wrote above, the device support team sent me software that helped solve the problem, and they also provided a new firmware version: htdmm55_V2004(2510111618)_20251011.up. Unfortunately, with the new firmware, the program at the following link stopped working:
https://lygte-info.dk/project/TestControllerIntro%20UK.html

This is probably the only decent software that previously worked with the HDM3055. After reverting to the previous firmware, compatibility with the program was restored.

I asked the support team whether they plan to fix this issue, and received the following response from Hantek: “No compatible firmware available; we have no plans to fix this issue for now.”

It’s quite disappointing to see this level of support for the device. I’ll probably start looking for a replacement, although it’s hard to find something comparable at Hantek’s price point.

[Microcheap]

Hantek has no relation whatsoever with TestController, it's very likely that they don't even know what it is so, no surprise that they can't help.

I made the HDM3000 configuration for TestController. So maybe I can help.

How are you trying to connect? Serial or LAN? Can you connect to the multimeter using the Keysight Connection Expert?

If so, what's the reply for the command "*IDN?" ? It should be something like "Hantek, HDM3055, CNxxxxxxxxxxxxx"

[infino]

So maybe I can help.

I understand that Hantek is not related to TestController. The issue is that their original software, HDM3000 Ver1.7, does not work correctly with the device — the panel always shows “Overload” (in all versions).

TestController used to work perfectly, but after the latest update it stopped functioning.

Here is the connection log when it does not work:

; jSerialComm version: 2.11.2
;; Start thread for: COM1
;; Start thread for: COM10
;; COM1: Set params: 9600
;; COM10: Set params: 9600
;; COM1: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM10: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM10: Rx: <Hantek,HDM3055,CN214xxxxxxxxxxxx,2.0.0.4>
;; USB Serial Converter (COM10) Did not find any match for: Hantek,HDM3055,CN214xxxxxxxxx,2.0.0.4
;; COM10: Close
;; Stopping thread for: COM10

And here is the connection log when everything works (with the previous firmware version of the device):

;; jSerialComm version: 2.11.2
;; Start thread for: COM1
;; Start thread for: COM10
;; COM1: Set params: 9600
;; COM10: Set params: 9600
;; COM10: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM1: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM10: Rx: <Hantek, HDM3055, CN214xxxxxxxx, 2.0.0.4>
;; COM10: Tx <*RST>
;; COM10: Tx <*CLS>
;; COM10: Tx <*OPC?>
;; COM10: Rx: <1>
;; Found Hantek HDM3055 on USB Serial Converter (COM10) sn: CN214xxxxxxxx
;; HDM3055: Tx SENSe:FUNCtion?
;; HDM3055: Rx <"VOLT">

ps I have a version of the device with a COM port and USB, but unfortunately no LAN. I cannot connect to TestController via USB — I’m connecting through the COM port, as shown in the terminal log.

[KungFuJosh]

Do you have Scan serial ports checked in the Load devices tab? If so, disable it.

If something changed on the device, and TC stopped detecting it correctly, remove the device from TC and add it again fresh and see if that fixes the problem.

Thanks,
Josh

[Kean]

It looks like the response to the *IDN? query no longer has the spaces after the commas.
Look closely at the differences in the two responses below.  That should be easy to fix in the TestController definition.

;; COM1: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM10: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM10: Rx: <Hantek,HDM3055,CN214xxxxxxxxxxxx,2.0.0.4>

;; COM10: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM1: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM10: Rx: <Hantek, HDM3055, CN214xxxxxxxx, 2.0.0.4>

[infino]

I’ll be working tomorrow and will turn on the device to double-check the logs — maybe some spaces appeared when copying the text.

[Kean]

I’ll be working tomorrow and will turn on the device to double-check the logs — maybe some spaces appeared when copying the text.

No, it looks like Hantek removed the spaces in the newer firmware.  They ideally should not have been there in the first place.

[Microcheap]

I understand that Hantek is not related to TestController. The issue is that their original software, HDM3000 Ver1.7, does not work correctly with the device — the panel always shows “Overload” (in all versions).

Their software has a bug and won't work correctly if the locate settings in windows is set to use comma as decimal separator (their power supply software has the same issue): https://www.eevblog.com/forum/testgear/hantek-hdm3055/msg5882732/#msg5882732

Regrading the connection with TC, Kean already pointed the issue. Apparently Hantek changed the response for the query *IDN? in this last firmware. The fix is very simple:

 - Look for the file "HantekHDM3000.txt" in the folder "../TestController/Devices/" and search for the line (30) "#idString Hantek, HDM3055," in this file. Now change it to match the new reply of your dmm: "#idString Hantek,HDM3055,". Save it and restart TestController.
It should connect now.

[infino]

I understand that Hantek is not related to TestController. The issue is that their original software, HDM3000 Ver1.7, does not work correctly with the device — the panel always shows “Overload” (in all versions).

Their software has a bug and won't work correctly if the locate settings in windows is set to use comma as decimal separator (their power supply software has the same issue): https://www.eevblog.com/forum/testgear/hantek-hdm3055/msg5882732/#msg5882732

Regrading the connection with TC, Kean already pointed the issue. Apparently Hantek changed the response for the query *IDN? in this last firmware. The fix is very simple:

 - Look for the file "HantekHDM3000.txt" in the folder "../TestController/Devices/" and search for the line (30) "#idString Hantek, HDM3055," in this file. Now change it to match the new reply of your dmm: "#idString Hantek,HDM3055,". Save it and restart TestController.
It should connect now.

I fixed it, but it didn’t help.

Starting
;; jSerialComm version: 2.11.2
;; Start thread for: COM1
;; Start thread for: COM10
;; COM1: Set params: 9600
;; COM10: Set params: 9600
;; COM1: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM10: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM10: Rx: <Hantek,HDM3055,CN214xxxxxxxx,2.0.0.4> 48 61 6E 74 65 6B 2C 48 44 4D 33 30 35 35 2C 43 4E 32 31 34 30 30 33 30 30 30 34 36 32 2C 32 2E 30 2E 30 2E 34
;; USB Serial Converter (COM10) Did not find any match for: Hantek,HDM3055,CN214xxxxxxxx,2.0.0.4
;; COM10: Close
;; Stopping thread for: COM10
;; COM10: Close
;; COM1: Rx: timeout
;; COM1: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM1: Rx: timeout
;; Stopping thread for: COM1
;; COM1: Close


In Agilent-HP emulation mode.
Starting
;; jSerialComm version: 2.11.2
;; Start thread for: COM1
;; Start thread for: COM10
;; COM1: Set params: 9600
;; COM10: Set params: 9600
;; COM10: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM1: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM10: Rx: <HEWLETT-PACKARD,34401A,0,9-4-1> 48 45 57 4C 45 54 54 2D 50 41 43 4B 41 52 44 2C 33 34 34 30 31 41 2C 30 2C 39 2D 34 2D 31
;; COM10: Tx <SerialInit>
;; COM10: Script start
;; COM10: Tx <SYST:REM>
;; COM10: Tx: <SYST:REM.> 53 59 53 54 3A 52 45 4D 0A
;; COM10: Delay: 20ms
;; COM10: Script end <>
;; Found Agilent 34401A on USB Serial Converter (COM10)
;; COM1: Rx: timeout
;; COM1: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM1: Rx: timeout
;; Stopping thread for: COM1
;; COM1: Close
;; HP34401A: Tx <FUNC?>
;; COM10: Tx: <FUNC?.> 46 55 4E 43 3F 0A
;; COM10: Rx: <"VOLT"> 22 56 4F 4C 54 22
;; HP34401A: Rx <"VOLT">
;; HP34401A: Tx <READ?>

[infino]

Everything is working now — it was my mistake. After editing, I didn’t save the file, and the editor was reading it from cache and showing it as if it had been modified.

Thank you for your help, and thanks to everyone who responded to the issue.

[likun123]

the latest official firmware for Hantek HDM3065.
htdmm65_V2006(2510231115)_2026041

[infino]

I can’t find the update versions on the official website. Where do you check or find these versions?

[frankzoe]

I’ll answer my own question. For those who have this device, it’s a good idea to save the calibration settings to a USB drive for future use. To do this, insert a USB drive with a capacity of up to 2 GB, then press the Shift button followed by OK (you can also try holding the buttons). The settings will be saved to the USB drive as .ini files.

The manufacturer also provided software with firmware for recovery. To put the device into boot mode, with the device powered off, hold the DCV button and the “-” key, then turn it on — it will enter boot mode. After that, connect it to a computer via USB and run the manufacturer’s software. The script mfgtool2-yocto-mx-evk-nand.vbs will start, and the program will automatically reflash the NAND memory. Once the process is complete, the device will be restored.

After that, you should install the latest firmware and restore the calibration settings or recalibrate the device

This feature is very useful. I have successfully backed up the calibration files. In addition, a USB drive no larger than 2GB is not necessary; I use a 16GB USB 2.0 drive. Simply formatting the drive to the Fat32 file system allows it to work properly, whether for software upgrades or backing up calibration files.

[infino]

Saving calibration files is definitely a very good practice. It’s a pity that I didn’t know about this option from the very beginning and only learned about it when Hantek sent me instructions on how to restore the device.

As for USB flash drive capacity: initially, my HDM3055 did not work with drives larger than 4 GB. More precisely, you could take a flash drive of any size, even 32 GB, create a 4 GB FAT32 partition on it, and then it would work. That’s exactly what I did.

After restoring the device and installing the latest software 2.0.0.4(2510111618), firmware 01.03.0601-22-02.05-02, I haven’t yet checked how it works with 8, 16, or 32 GB flash drives.

The main thing is that I managed to fully restore the device’s functionality — it now works perfectly with the testController software.