sigrok-cli, sigrok-meter, ut-do4 and ut71(c)

[alm]

@ Alm: no driver named: .......
the problem was an additional ut, so uni-t-ut71c-ser, instead of uni-t-71c-ser you typed the second time.. this should teach me to not just copy/past easy enough typ-o to make.

True! I guess the uni-t-ut feels redundant (like the Hewlett Packard HP15c).

tried running it as sudo: (felt like a permission problem)

Agreed. Adding yourself to plugdev (sudo adduser $USER plugdev or however you do that through the GUI) might help. Sudo is not a good long term solution, but is fine for troubleshooting.

sr: uni-t-dmm: HID feature report error: LIBUSB_ERROR_PIPE.
sr: uni-t-dmm: HID chip init failed: -1.

Looks related to this bug. Seems like the cable gets confused by the scanning. My suggestion would be to unplug the cable, power off the meter, reboot the computer and then just try:

Code: [Select]

sigrok-cli -d uni-t-ut71c:conn=1a86.e008 --scan

If that works without errors, then:

Code: [Select]

sigrok-cli -d uni-t-ut71c:conn=1a86.e008 -O analog --samples 5

your are propbably right.. just want to make sure it is all working fine.. so i know i can rely on the idea that when something goes wrong trying to use it. it is user error and not installation or hardware error.

From the bug report, this sounds like a hardware bug in the Uni-T cable. But not severe if it only shows up when scanning.

the other thing is..  i need to study for an important exam so.. that should have president.!

True.

[abraxa]

My apologies for leading you down the wrong path with serial-dmm. Looks like I'm mistaken at how libsigrok handles the individual models.

As for the bug in the cable that alm mentioned, I'd like you to try these workarounds when your exam is over:

http://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=README.devices;h=584899e2b0648ed65aae7c39cbbdf083a46db24f;hb=HEAD#l307
http://sigrok.org/wiki/Device_cables/Info#UNI-T_UT-D04

I wonder if that makes it work for you.

[spikey1973]

@Alm: indeed very redundant, i completely agree there

anyway.. i turned of the meter and unplugged the meter and rebooted my pc.
afterwards. plugged in the cable and turned on the meter. (does any of the unplug and turn off routine have a necessairy specific order, as i was not specific with that.)

cd sigrock_build
~/sigrock_build$ sigrok-cli -d uni-t-ut71c:conn=1a86.e008 --scan

The following devices were found:
uni-t-ut71c - UNI-T UT71C with 1 channel: P1

~/sigrock_build$ sigrok-cli -d uni-t-ut71c:conn=1a86.e008 -O analog --samples 5

sr: usb: Failed to open device: LIBUSB_ERROR_ACCESS.
Failed to open device.

seems the same as before to me.

@abraxa:
about this work around.. going from a freshly booted laptop.. and cable disconnected and a dmm turned off.
is there a specific order in which i should do this?

my personal choice was:
reboot.
plug in usb cable
turn on dmm
run script
~/sigrock_build$ sigrok-cli -d uni-t-ut71c:conn=1a86.e008 -O analog --samples 5
please correct if wrong.

anyway.. i tried it and didn't work.. but tried again and it seems to work ,
no error.. just a kinda waiting for a sample.  maybe i did something wrong the first time. anyway. i repeated it a couple of times and it works.. well seems to anyway.
made a text file executable so i don't have to keep typing the same everytime (batch file like) 

so if it works.. i now need to figure out how to send dat from the dmm itself.. outwards.
just realise that i haven't looked into that part yet. shouldn't be to difficult though. but that is for tomorrow.
also i will need to look into how to use sigrok-cli.. and also sigrok-meter ofcourse.
but got a hell of a lot further today.. Thank you very much, both!

for now i still have the following information if still interested:

lsusb -vvv. (cut out the other usb devices, just left the 1a86:e0008 device, if you need all. please let me know)

i noticed that the following is different compared to the data on the website.

idVendor           0x1a86 QinHeng Electronics
idProduct          0xe008 HID-based serial adapater
bcdDevice           13.00
iManufacturer           1

Bus 002 Device 005: ID 1a86:e008 QinHeng Electronics HID-based serial adapater
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x1a86 QinHeng Electronics
  idProduct          0xe008 HID-based serial adapater
  bcdDevice           13.00
  iManufacturer           1
  iProduct                2
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           41
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          4
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.00
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      37
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               5
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               5

[spikey1973]

@abraxa:

something completely off context but as a owner of a dpscope.. i was wondering if there has ever been any development in support of the dpsope?

https://sourceforge.net/p/sigrok/mailman/message/32448553/

anyway.. if interested i'm willing to do some testing..

[abraxa]

about this work around.. going from a freshly booted laptop.. and cable disconnected and a dmm turned off.
is there a specific order in which i should do this?

The order in which you're doing it is fine, what matters is that you run the script before using sigrok-cli or sigrok-meter. No need to reboot, by the way

something completely off context but as a owner of a dpscope.. i was wondering if there has ever been any development in support of the dpsope?

No, there hasn't. As Peter wrote in response to the guy asking on the mailing list, the sigrok core dev team has to decide whether they want to spend time working on device support or working on bugfixes or working on new features. That is an unfortunate situation for everyone involved, but that's how it is and the result is that devices which aren't too widespread are put on the waiting list - especially if the specs are weak. Both criteria are true for the dpscope, so unless someone else writes a driver, it won't be supported, I'm afraid.

[spikey1973]

i understand.. but are the specs really so bad?

unfortunately i am willing but haven't got nearly the skills otherwise i would. would be a good experience.

ps: i finished the additional answer om my question on askubuntu also concering this issue with a "small" tutorial for every one facing the same problems, in the hope it helps them.
ofcourse i added special thanks to you.