Skip to content

Siglent: Using SDS1104X-E through usbtmc not always work #652

Description

@racerxdl

As discussed here (https://twitter.com/azonenberg/status/1544476705842049024) using a SDS1104X-E through usbtmc mostly dont work (glscope client correctly detects, and sometimes the trace appears on it).

So I made some usb captures, logging and everything to try to help debugging the issue. Funny enough, through ethernet everything seens to work fine (I have some issues setting up the triggers correctly, but I'm not sure is a communication issue). I always though it might be a linux usbtmc driver issue since sigrok sort of works correctly, but it does by using libusb to connecting directly to the oscilloscope instead using usbtmc.

Here are some logs from initialization. The traces do appear once in the glscopeclient, but then everything stops working and I need to remove the usb cable and put again so I can get the trace again (just restarting glscopeclient does not help)

usbcapture_filtered.pcapng.gz
dmesg.log
sds1104x-e.log

I'm currently on x86-64 ubuntu 22.04 (kernel 5.15.0). Once I managed to completely freeze the osciloscope trying to capture from glscopeclient (I had to hardreset the osciloscope to get back), but I really dont remember what I did to cause that.

My oscilloscope is a Siglent SDS1104X-E key-upgraded to SDS1204X-E running latest firmware (8.1.6.1.37R9)

Might be related #214

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions