Created attachment 741 [details] Error output of acquisition command When trying to capture samples with the sigrok-cli from a Metrahit 29S multimeter, via a COM-port, the cli can not open a port for acquisition after successfully detecting the multimeter. Same error on two different computers with serial ports and when using a USB-to-Serial adapter. See attached file for the error output. -V Version information: sigrok-cli 0.7.2 Libraries and features: - libsigrok 0.5.2/5:1:1 (rt: 0.5.2/5:1:1). - Libs: - glib 2.44.1 (rt: 2.44.1/4401:1) - libzip 1.5.2 - libserialport 0.1.1/1:0:1 (rt: 0.1.1/1:0:1) - libusb-1.0 1.0.20.11003-rc3 API 0x01000104 - hidapi 0.8.0-rc1 - libftdi 1.4 - Host: x86_64-w64-mingw32.static.posix, little-endian. - SCPI backends: TCP, serial, USBTMC. - libsigrokdecode 0.5.3/6:1:2 (rt: 0.5.3/6:1:2). - Libs: - glib 2.44.1 (rt: 2.44.1/4401:1) - Python 3.4.4 / 0x30404f0 (API 1013, ABI 3) - Host: x86_64-w64-mingw32.static.posix, little-endian.
Operating system is Windows 10 18363.1646 and 19042.1110
This specific driver appears to open the serial port during scan but won't close it. Which means that the port still "is busy" when data acquisition is about to start. Somebody with access to the sources and to the device needs to look into that issue.
If the dont-scan feature would disable the scan for the specific driver, it will work for me, even though, that the underlying problem is not fixed. I will happyly to assist in testing, if non of the developers has a Metrahit 2xS lying around.