Ladislav,

Thanks for this.

Unfortunately I have now established, with the help of copilot AI, that the four north, east, south, west buttons manipulate menus, and the right-most soft button under the display is the enter button.

And as I am blind, I will not be able to navigate those menus to know when the USB option is selected nor whether to press the button.

I might be able to give the meter to a friend at my local Linux User Group and ask him to write a 'menu road map'. But it is going to be difficult to work. If I could establish whether the USB option persists between power cycles, it might be that turning it on once is enough.

But, as Dan has suggested it is TX only, I will probably need to write a continuous reader of my own. Possibly compile in the eSpeak library to make it speak measurements.

Thanks for your help with udev, I had forgotten all about that.

Mike


On 25/11/2025 12:32, Ladislav Laska wrote:
Hi Michael,

first of all, cool use case! Unfortunately, I don't have a HID meter to
test with. However, I have two ideas (that might be totally wrong):

1. Check if you have installed the udev rules. By default, sigrok
installs udev rules to mark all known vids/pids with ID_SIGROK=1 and
only auto scans those. UT612 is expected under 10c4:ea80.

2. Check if you have permissions to open the device. The default sigrok
udev rules grant permissions to users in the "plugdev" group.

... I suggest you also run `lsusb` to check what vid/pid we're dealing
with (ideally before and after you've connected to usb).


Since the chip is HID, it will not show up as /dev/tty*, but it still
needs permissions. Additionally, the libserialport-dev is likely not
needed (I'm not sure and don't want to spend time to search for it. It's
safer to have it), since it will be handled by serial_hid_cp2110.c driver.

This depends on:

#ifdef HAVE_SERIAL_COMM
#ifdef HAVE_LIBHIDAPI

It will require libhidapi-dev. Is this installed and compiled with?

Best regards,
Ladislav


On Tue, Nov 25, 2025 at 12:04:39PM +0000, Michael A Ray via sigrok-devel wrote:


Dan,

Thanks. I saw that in the log. Mathias' note about libserialport-dev lead me
to install that, and rebuild libsigrok, but still nothing. However I have
used other UniT kit, like the UT60A dmm with both RS232 and USB adapters
even before installing libserialport-dev.

I'm now not confident that I have the right button presses to enable USB.

AI is never going to take over the world if it can't help me enable USB on
the UT612 :-)

Mike


On 25/11/2025 11:33, Dan Horák wrote:
On Tue, 25 Nov 2025 11:07:04 +0000
Michael A Ray <[email protected]> wrote:



Dan,

Here below is the text of the log created.

This might sound like a really stupid question, but I have no sighted
assistance here. Copilot AI is telling me the right way to enable the
meter for USB connectivity is to turn it on, then press the right-most
soft button on the row of four buttons under the display. Is that right?
Copilot has been known to tell me nonsense before now.

the wiki page (https://sigrok.org/wiki/UNI-T_UT612) talks about only
TX connected, perhaps there is some oddity how it communicates with
tools like sigrok-cli

Log:

sr: [00:00.000032] log: libsigrok loglevel set to 5.
sr: [00:00.000050] backend: libsigrok 0.6.0-git-0bc24877/4:0:0.
sr: [00:00.000095] backend: Libs: glib 2.64.6 (rt: 2.64.6/6406:6), zlib
1.2.11, libzip 1.5.1, minilzo 2.10, libserialport 0.1.1/1:0:1 (rt:
0.1.1/1:0:1), libusb-1.0 1.0.23.11397 API 0x01000107, hidapi 0.9.0,
libftdi 1.4, librevisa 0.0.20130812.
sr: [00:00.000108] backend: Host: x86_64-pc-linux-gnu, little-endian.
sr: [00:00.000119] backend: SCPI backends: TCP, RPC, serial, VISA, USBTMC.
sr: [00:00.000127] backend: Firmware search paths:
sr: [00:00.000147] backend:  - /home/mike/.local/share/sigrok-firmware
sr: [00:00.000156] backend:  - /usr/local/share/sigrok-firmware
sr: [00:00.000165] backend:  - /usr/local/share/sigrok-firmware
sr: [00:00.000173] backend:  - /usr/share/sigrok-firmware
sr: [00:00.000181] backend:  - /var/lib/snapd/desktop/sigrok-firmware
sr: [00:00.000210] backend: Sanity-checking all drivers.
sr: [00:00.000224] backend: Sanity-checking all input modules.
sr: [00:00.000233] backend: Sanity-checking all output modules.
sr: [00:00.000247] backend: Sanity-checking all transform modules.
srd: libsigrokdecode loglevel set to 5.
sr: [00:00.003443] hwdriver: Scan found 0 devices (agilent-dmm).
sr: [00:00.003455] hwdriver: Scan found 0 devices (appa-55ii).
sr: [00:00.003464] hwdriver: Scan found 0 devices
(arachnid-labs-re-load-pro).
sr: [00:00.003474] serial: No serial device specified.
sr: [00:00.003484] asix-omega-rtm-cli: Vendor application executable:
omegartmcli
posix_spawn avoided (fd close requested)
sr: [00:00.004331] asix-omega-rtm-cli: External RTM CLI execution failed.
sr: [00:00.004347] hwdriver: Scan found 0 devices (asix-omega-rtm-cli).
sr: [00:00.004380] hwdriver: Scan found 0 devices (asix-sigma).
sr: [00:00.004390] serial: No serial device specified.
sr: [00:00.004399] hwdriver: Scan found 0 devices (atorch).
sr: [00:00.004408] hwdriver: Scan found 0 devices (atten-pps3203).
sr: [00:00.004540] hwdriver: Scan found 0 devices (baylibre-acme).
sr: [00:00.004557] hwdriver: Scan found 0 devices (beaglelogic).
sr: [00:00.004567] hwdriver: Scan found 0 devices (bkprecision-1856d).
sr: [00:00.004576] hwdriver: Scan found 0 devices (cem-dt-885x).
sr: [00:00.004585] hwdriver: Scan found 0 devices (center-309).
sr: [00:00.004594] hwdriver: Scan found 0 devices (voltcraft-k204).
sr: [00:00.004603] serial: No serial device specified.
sr: [00:00.004616] hwdriver: Scan found 0 devices (chronovu-la).
...
sr: [00:00.100744] hwdriver: Scan found 0 devices (voltcraft-vc960-ser).
sr: [00:00.100751] hwdriver: Scan found 0 devices (voltcraft-vc870-ser).
sr: [00:00.100758] hwdriver: Scan found 0 devices (voltcraft-vc96).
sr: [00:00.100772] hwdriver: Scan found 0 devices (deree-de5000).
sr: [00:00.100778] hwdriver: Scan found 0 devices (mastech-ms5308).
sr: [00:00.100784] hwdriver: Scan found 0 devices (peaktech-2170).
sr: [00:00.100790] hwdriver: Scan found 0 devices (uni-t-ut612).

^^^ it is trying ...

sr: [00:00.100796] hwdriver: Scan found 0 devices (peaktech-2165).
sr: [00:00.100802] hwdriver: Scan found 0 devices (voltcraft-4080).
sr: [00:00.100808] serial: No serial device specified.
...
sr: [00:00.131195] hwdriver: Scan found 0 devices (zketech-ebd-usb).
sr: [00:00.131222] hwdriver: Cleaning up all drivers.
The following devices were found:
demo - Demo device with 13 channels: D0 D1 D2 D3 D4 D5 D6 D7 A0 A1 A2 A3 A4


                Dan



On 25/11/2025 10:43, Dan Horák wrote:
On Tue, 25 Nov 2025 10:28:40 +0000
Michael A Ray via sigrok-devel <[email protected]>
wrote:


Hello all,

I’ve been experimenting with a UNI-T UT612 LCR meter that uses the
CP2110 HID-UART bridge (USB VID:PID 10c4:ea80). I’ve built libsigrok and
sigrok-cli from current master, with HIDAPI detected at configure time.
However, sigrok-cli --scan only shows the demo device, and the
uni-t-ut612 driver appears to expect a serial port (/dev/ttyUSB*).

please post the output of "sigrok-cli -l 5 --scan", so we get the
verbose logs


                Dan
Could someone clarify the current status of HID support for the UT612?

• Has HID binding for the UT612 driver been merged, or is it still pending?
• Is there a development branch or patchset I should test?
• Any guidance on decoding the HID frames directly would also be
appreciated.

I’d be happy to test experimental code or contribute logs from my device
if that helps move HID support forward.

Thanks for your time and for all the work on sigrok.

sigrok-cli is an absolute Godsend to me as a totally blind hacker.

Mike


--
Michael A. Ray
Software engineer
Witley, Surrey, South-east UK

He/him

"Perfection is achieved, not when there is nothing more to add, but when
there is nothing left to take away." -- A. de Saint-Exupery





_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel


--
Michael A. Ray
Software engineer
Witley, Surrey, South-east UK

He/him

"Perfection is achieved, not when there is nothing more to add, but when
there is nothing left to take away." -- A. de Saint-Exupery




_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel


--
Michael A. Ray
Software engineer
Witley, Surrey, South-east UK

He/him

"Perfection is achieved, not when there is nothing more to add, but when
there is nothing left to take away." -- A. de Saint-Exupery




_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel



--
Michael A. Ray
Software engineer
Witley, Surrey, South-east UK

He/him

"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -- A. de Saint-Exupery




_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Reply via email to