New Sigrok/PulseView hardware support (Siglent SDS HD, Rigol DHO800...)

[dpenev]

Thanks Furna,
I have  followed the procedure I have described two messages back and the log attached.
 

...
sr: scpi_tcp: Successfully sent SCPI command: ':TDIV? '.
sr: scpi: Got response: 'DAT2,#9000000000 AVEDESC1.00E+075.00E-04', length 40.
sr: session: bus: Received SR_DF_HEADER packet.
sr: scpi_tcp: Successfully sent SCPI command: 'WAV:MAXP? '.
sr: scpi: Got response: '5.00E-04', length 8.
sr: scpi: get_int: non-integer rational=500/1000000
sr: session: Could not start siglent-sds device tcp-raw/192.168.1.6/5025 acquisition.
...

'DAT2,#9000000000 AVEDESC1.00E+075.00E-04' looks a concatenation of few responses.

5.00E-04 is my current timing resolution 500us/div

WAV:MAXP?  if sent separately to the oscilloscope returns 10000000 but I don't see it in the log.

 

[Furna]

Thanks Furna,
I have  followed the procedure I have described two messages back and the log attached.
 

...
sr: scpi_tcp: Successfully sent SCPI command: ':TDIV? '.
sr: scpi: Got response: 'DAT2,#9000000000 AVEDESC1.00E+075.00E-04', length 40.
sr: session: bus: Received SR_DF_HEADER packet.
sr: scpi_tcp: Successfully sent SCPI command: 'WAV:MAXP? '.
sr: scpi: Got response: '5.00E-04', length 8.
sr: scpi: get_int: non-integer rational=500/1000000
sr: session: Could not start siglent-sds device tcp-raw/192.168.1.6/5025 acquisition.
...

'DAT2,#9000000000 AVEDESC1.00E+075.00E-04' looks a concatenation of few responses.

5.00E-04 is my current timing resolution 500us/div

WAV:MAXP?  if sent separately to the oscilloscope returns 10000000 but I don't see it in the log.

Can you try with a different resolution? I was succesfull with 10mV/div with SDS824X HD

See also
https://www.eevblog.com/forum/testgear/new-sigrokpulseview-hardware-support-(siglent-sds-hd-rigol-dho800-)/msg5605601/#msg5605601
With SDS2104X+ it is not possible to go lower than 10mV/div and fredo_ is looking at it.

[dpenev]

Seems not related with Voltage resolution. I have tested with 1V/div and still similar behavior.
| am attaching another log for someone to check. I have a feeling that it is a timing issue in the the communication.
Assuming that the software is working fine for someone else with SDS2000X+
In my case both the PC running PV and the scope are in the same LAN connected directly in the same router, 1,2m LAN cables.

Pinging 192.168.1.6 with 32 bytes of data:
Reply from 192.168.1.6: bytes=32 time<1ms TTL=64
Reply from 192.168.1.6: bytes=32 time<1ms TTL=64
Reply from 192.168.1.6: bytes=32 time<1ms TTL=64
Reply from 192.168.1.6: bytes=32 time<1ms TTL=64

[fredo_]

Hi @dpenev and thank you for your investigations !

Seems not related with Voltage resolution. I have tested with 1V/div and still similar behavior.
| am attaching another log for someone to check. I have a feeling that it is a timing issue in the the communication.
Assuming that the software is working fine for someone else with SDS2000X+
In my case both the PC running PV and the scope are in the same LAN connected directly in the same router, 1,2m LAN cables.

No it doesn't seem to be a timing issue, the problem comes from the response of the scope to the ACQ:POIN? command.
You scope gives a ".9" reply while the Sigrok (and the documentation) expects something of the form "1.25E+08".
This command returns the number of points of the current waveform. Can you check the memory depth of the scope and maybe the value returned by ACQ:POIN? SCPI command form web control ?

[fredo_]

Oh and @dpenev, you may want to try and reboot your scope (including removing the powder cable).
It happened to me a few times: I started having very strange SCPI responses from the scope, and after a full reboot, everything went back to normal  .