[sigrok-devel] Strange device connect on nightly build Pulseview en Sigrok-cli

[Marchel H <mar...@gm...>]

Hi All,

I see a strange problem, when using the windows build of Pulseview and
Sigrok-cli.
When using network connection scan, I see that it tries to use the serial
open:

sr: [00:15.501000] scpi: Opening serial device vxi/192.168.2.31/5555.
sr: [00:15.503000] serial: Opening serial port 'vxi/192.168.2.31/5555'
(flags 1).
sr: [00:15.506000] serial: Error opening port (3): Path not found..
sr: [00:15.508000] scpi: Couldn't open SCPI device.
sr: [00:15.510000] hwdriver: Scan found 0 devices (siglent-sds).

However on linux it is connecting using vxi:

sr: [00:23.427549] scpi: Opening VXI device vxi/192.168.2.31/5555.
sr: [00:23.437616] siglent-sds: Device probing decode...
sr: [00:23.437667] siglent-sds: Setting Communication Headers to off
sr: [00:23.439572] scpi_vxi: Successfully sent SCPI command: 'CHDR OFF'.
sr: [00:23.441405] scpi_vxi: Successfully sent SCPI command: '*IDN?'.
sr: [00:23.443253] scpi: Got response:
'SIGLENT,SDS1102X+,SDS1XDBXXXXXXX,1.1.2.15 R3', length 44.
sr: [00:23.443272] scpi: Got IDN string:
'SIGLENT,SDS1102X+,SDS1XDBXXXXXXX,1.1.2.15 R3'
sr: [00:23.443289] siglent-sds: Decoded Manufacturer: SIGLENT
sr: [00:23.443297] siglent-sds: Decoded Model: SDS1102X+


Is this something I have to do in this driver? Or is there some strange
thing going with the latest builds?

Greetings,
Marchel.