Hello Uwe, I compiled the Sigrok project with sigrok-cli and pulseview from the Git version. The change in the dslogic driver works for me.
From the version sigrok-cli 0.8.0-git-49e9f06 Libraries and features: - libsigrok 0.6.0-git-cdb134e / 4: 0: 0 (rt: 0.6.0-git-cdb134e / 4: 0: 0). - Libs: - glib 2.42.1 (rt: 2.42.1 / 4201: 1) - libzip 0.11.2 - libserialport 0.1.1 / 1: 0: 1 (rt: 0.1.1 / 1: 0: 1) - libusb-1.0 1.0.18.10866 - libftdi 1.4 - Host: x86_64-unknown-linux-gnu, little-endian. - SCPI backends: TCP, RPC, serial, USBTMC. - libsigrokdecode 0.6.0-git-cb67584 / 4: 0: 0 (rt: 0.6.0-git-cb67584 / 4: 0: 0). - Libs: - glib 2.42.1 (rt: 2.42.1 / 4201: 1) - Python 3.4.2 / 0x30402f0 (API 1013, ABI 3) - Host: x86_64-unknown-linux-gnu, little-endian. it is no longer absolutely necessary to specify a threshold as a program parameter. The default threshold of the driver is used. Maybe a suggestion on the website https://sigrok.org/wiki/DreamSourceLab_DSLogic under Capabilities the indication that a threshold is only necessary if one wants to deviate from the default value. And the hint that a Threshold with stepping 0.1V only with Pro and Plus version is possible. greetings Jörg > > Can you confirm that (with your patch) sigrok-cli works fine now and > shows no issues anymore? > > > Cheers, Uwe. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
