Bug 730 - Rigol VS 5000 Series not working
Summary: Rigol VS 5000 Series not working
Status: CONFIRMED
Alias: None
Product: libsigrok
Classification: Unclassified
Component: Driver: rigol-ds (show other bugs)
Version: unreleased development snapshot
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-04 06:35 CET by Chris Heldeis
Modified: 2016-01-06 09:13 CET (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Heldeis 2016-01-04 06:35:48 CET
D:\Developer\Tools\Measurements\sigrok\sigrok-cli>sigrok-cli -d rigol-ds:conn=tcp-rigol/172.16.15.119/19 -l 5 --show
sr: [00:00.000000] log: libsigrok loglevel set to 5.
sr: [00:00.001000] backend: libsigrok 0.4.0-git-fa69e19/2:0:0 (rt: 0.4.0-git-fa69e19/2:0:0).
sr: [00:00.003000] backend: Libs: glib 2.44.1 (rt: 2.44.1/4401:1), libzip 0.11.2, libserialport 0.1.1/0:0:0 (rt: 0.1.1/0:0:0), libusb-1.0 1.0.20.11003-rc3, libftdi 1.2.
sr: [00:00.007000] backend: Host: i686-w64-mingw32.static.posix, little-endian.
sr: [00:00.008000] backend: SCPI backends: TCP, serial, USBTMC.
sr: [00:00.009000] backend: Sanity-checking all drivers.
sr: [00:00.010000] backend: Sanity-checking all input modules.
sr: [00:00.012000] backend: Sanity-checking all output modules.
sr: [00:00.013000] backend: Sanity-checking all transform modules.
srd: libsigrokdecode loglevel set to 5.
sr: [00:00.018000] hwdriver: Initializing driver 'rigol-ds'.
Driver functions:
    Oscilloscope
    Frame limit
    Time base
    Trigger source
    Trigger slope
    Horizontal trigger position
    Number of horizontal divisions
    Sample rate
    Data source
sr: [00:00.029000] hwdriver: sr_config_list(): key 2147418112 (NULL) sdi 00000000 cg NULL -> [uint32 20000, 20001]
Scan options:
    conn
    serialcomm
sr: [00:00.034000] hwdriver: Initializing driver 'rigol-ds'.
sr: [00:00.035000] hwdriver: sr_config_list(): key 2147418112 (NULL) sdi 00000000 cg NULL -> [uint32 20000, 20001]
sr: [00:00.038000] scpi: Opening RIGOL TCP device tcp-rigol/172.16.15.119/19.
sr: [00:00.068000] scpi_tcp: Successfully sent SCPI command: '*IDN?'.
sr: [00:00.316000] scpi: Got response: 'RIGOL TECHNOLOGIES,VS5202D,VS5C123500040,02.03.02', length 49.
sr: [00:00.318000] scpi: Got IDN string: 'RIGOL TECHNOLOGIES,VS5202D,VS5C123500040,02.03.02'
sr: [00:00.320000] hwdriver: Scan of 'rigol-ds' found 1 devices.
rigol-ds - Rigol VS5202D 02.03.02 with 18 channels: CH1 D0 CH2 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 D14 D15
sr: [00:00.337000] scpi_tcp: Successfully sent SCPI command: ':CHAN1:DISP?'.
sr: [00:01.338000] scpi: Timed out waiting for SCPI response.
sr: [00:01.341000] rigol-ds: Failed to get device config: generic/unspecified error.
Comment 1 Chris Heldeis 2016-01-04 06:38:59 CET
Hi,

As discovered in another bug, where SCPI TCP Backend did not on Windows, here is the report for a bug which was found after the original Bug was solved.

If any Help is needed I can do so, I can also offer a Portmapping to access a VS5202D (2 Analog + 16 Digial).
Comment 2 Martin Ling 2016-01-04 10:25:02 CET
(In reply to comment #1)
> If any Help is needed I can do so, I can also offer a Portmapping to access
> a VS5202D (2 Analog + 16 Digial).

I'm the author of the rigol-ds driver - if you contact me off bugzilla I'm happy to have a look at this remotely as you suggest.
Comment 3 Chris Heldeis 2016-01-04 13:47:50 CET
Hi Martin,

Ok, wll do that, I'll send you an Email once I have prepared it

Chris
Comment 4 Martin Ling 2016-01-04 15:56:47 CET
For those reading along - Christophe set me up with remote access to his scope but I wasn't able to reproduce the problem, running current git master of sigrok-cli and libsigrok on Linux.

So we know that the problem is not the SCPI commands used - ':CHAN1:DISP?' is indeed perfectly valid for this scope.

My guess is that we're dealing with a Windows-specific issue in the scpi_tcp backend, although there could also be some timing/fragmentation/etc difference related to my accessing the scope remotely rather than directly across a LAN.
Comment 5 Chris Heldeis 2016-01-06 09:13:16 CET
This is indeed a Timing Problem.

I have a second Unit of VS5202D, which is physically located in Asia, and I tried the same thing via VPN. The VPN has a ~300ms latency. It works with the command but in the local network it does not work. 


D:\Developer\Tools\Measurements\sigrok\sigrok-cli>sigrok-cli -d rigol-ds:conn=tcp-rigol/172.16.16.140/19 -l 5 --show
sr: [00:00.000000] log: libsigrok loglevel set to 5.
sr: [00:00.001000] backend: libsigrok 0.4.0-git-fa69e19/2:0:0 (rt: 0.4.0-git-fa69e19/2:0:0).
sr: [00:00.003000] backend: Libs: glib 2.44.1 (rt: 2.44.1/4401:1), libzip 0.11.2, libserialport 0.1.1/0:0:0 (rt: 0.1.1/0:0:0), libusb-1.0 1.0.20.11003-rc3, libftdi 1.2.
sr: [00:00.007000] backend: Host: i686-w64-mingw32.static.posix, little-endian.
sr: [00:00.009000] backend: SCPI backends: TCP, serial, USBTMC.
sr: [00:00.010000] backend: Sanity-checking all drivers.
sr: [00:00.011000] backend: Sanity-checking all input modules.
sr: [00:00.012000] backend: Sanity-checking all output modules.
sr: [00:00.013000] backend: Sanity-checking all transform modules.
srd: libsigrokdecode loglevel set to 5.
sr: [00:00.017000] hwdriver: Initializing driver 'rigol-ds'.
Driver functions:
    Oscilloscope
    Frame limit
    Time base
    Trigger source
    Trigger slope
    Horizontal trigger position
    Number of horizontal divisions
    Sample rate
    Data source
sr: [00:00.028000] hwdriver: sr_config_list(): key 2147418112 (NULL) sdi 00000000 cg NULL -> [uint32 20000, 20001]
Scan options:
    conn
    serialcomm
sr: [00:00.031000] hwdriver: Initializing driver 'rigol-ds'.
sr: [00:00.033000] hwdriver: sr_config_list(): key 2147418112 (NULL) sdi 00000000 cg NULL -> [uint32 20000, 20001]
sr: [00:00.036000] scpi: Opening RIGOL TCP device tcp-rigol/172.16.16.140/19.
sr: [00:00.343000] scpi_tcp: Successfully sent SCPI command: '*IDN?'.
sr: [00:00.728000] scpi: Got response: 'RIGOL TECHNOLOGIES,VS5202D,VS5C124400049,02.03.02', length 49.
sr: [00:00.731000] scpi: Got IDN string: 'RIGOL TECHNOLOGIES,VS5202D,VS5C124400049,02.03.02'
sr: [00:00.734000] hwdriver: Scan of 'rigol-ds' found 1 devices.
rigol-ds - Rigol VS5202D 02.03.02 with 18 channels: CH1 D0 CH2 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 D14 D15
sr: [00:01.043000] scpi_tcp: Successfully sent SCPI command: ':CHAN1:DISP?'.
sr: [00:01.420000] scpi: Got response: 'ON', length 2.
sr: [00:01.423000] scpi_tcp: Successfully sent SCPI command: ':CHAN2:DISP?'.
sr: [00:01.802000] scpi: Got response: 'ON', length 2.
sr: [00:01.805000] rigol-ds: Current analog channel state:
sr: [00:01.808000] rigol-ds: CH1 on
sr: [00:01.810000] rigol-ds: CH2 on
sr: [00:01.811000] scpi_tcp: Successfully sent SCPI command: ':LA:DISP?'.
sr: [00:02.189000] scpi: Got response: 'ON', length 2.
sr: [00:02.190000] rigol-ds: Logic analyzer enabled, current digital channel state:
sr: [00:02.192000] scpi_tcp: Successfully sent SCPI command: ':DIG0:TURN?'.
sr: [00:02.573000] scpi: Got response: 'ON', length 2.
sr: [00:02.575000] rigol-ds: D0: on
sr: [00:02.576000] scpi_tcp: Successfully sent SCPI command: ':DIG1:TURN?'.
sr: [00:03.055000] scpi: Got response: 'OFF', length 3.
sr: [00:03.056000] rigol-ds: D1: off
sr: [00:03.057000] scpi_tcp: Successfully sent SCPI command: ':DIG2:TURN?'.
sr: [00:03.447000] scpi: Got response: 'OFF', length 3.
sr: [00:03.448000] rigol-ds: D2: off
sr: [00:03.448000] scpi_tcp: Successfully sent SCPI command: ':DIG3:TURN?'.
sr: [00:03.836000] scpi: Got response: 'OFF', length 3.
sr: [00:03.838000] rigol-ds: D3: off
sr: [00:03.839000] scpi_tcp: Successfully sent SCPI command: ':DIG4:TURN?'.
sr: [00:04.216000] scpi: Got response: 'OFF', length 3.
sr: [00:04.217000] rigol-ds: D4: off
sr: [00:04.218000] scpi_tcp: Successfully sent SCPI command: ':DIG5:TURN?'.
sr: [00:04.601000] scpi: Got response: 'OFF', length 3.
sr: [00:04.602000] rigol-ds: D5: off
sr: [00:04.603000] scpi_tcp: Successfully sent SCPI command: ':DIG6:TURN?'.
sr: [00:04.984000] scpi: Got response: 'OFF', length 3.
sr: [00:04.985000] rigol-ds: D6: off
sr: [00:04.986000] scpi_tcp: Successfully sent SCPI command: ':DIG7:TURN?'.
sr: [00:05.390000] scpi: Got response: 'OFF', length 3.
sr: [00:05.391000] rigol-ds: D7: off
sr: [00:05.392000] scpi_tcp: Successfully sent SCPI command: ':DIG8:TURN?'.
sr: [00:05.775000] scpi: Got response: 'OFF', length 3.
sr: [00:05.777000] rigol-ds: D8: off
sr: [00:05.778000] scpi_tcp: Successfully sent SCPI command: ':DIG9:TURN?'.
sr: [00:06.151000] scpi: Got response: 'OFF', length 3.
sr: [00:06.152000] rigol-ds: D9: off
sr: [00:06.153000] scpi_tcp: Successfully sent SCPI command: ':DIG10:TURN?'.
sr: [00:06.527000] scpi: Got response: 'OFF', length 3.
sr: [00:06.529000] rigol-ds: D10: off
sr: [00:06.530000] scpi_tcp: Successfully sent SCPI command: ':DIG11:TURN?'.
sr: [00:06.924000] scpi: Got response: 'OFF', length 3.
sr: [00:06.925000] rigol-ds: D11: off
sr: [00:06.926000] scpi_tcp: Successfully sent SCPI command: ':DIG12:TURN?'.
sr: [00:07.299000] scpi: Got response: 'OFF', length 3.
sr: [00:07.301000] rigol-ds: D12: off
sr: [00:07.302000] scpi_tcp: Successfully sent SCPI command: ':DIG13:TURN?'.
sr: [00:07.683000] scpi: Got response: 'OFF', length 3.
sr: [00:07.684000] rigol-ds: D13: off
sr: [00:07.685000] scpi_tcp: Successfully sent SCPI command: ':DIG14:TURN?'.
sr: [00:08.165000] scpi: Got response: 'OFF', length 3.
sr: [00:08.167000] rigol-ds: D14: off
sr: [00:08.168000] scpi_tcp: Successfully sent SCPI command: ':DIG15:TURN?'.
sr: [00:08.540000] scpi: Got response: 'OFF', length 3.
sr: [00:08.542000] rigol-ds: D15: off
sr: [00:08.543000] scpi_tcp: Successfully sent SCPI command: ':TIM:SCAL?'.
sr: [00:08.924000] scpi: Got response: '2.00e-04', length 8.
sr: [00:08.925000] rigol-ds: Current timebase 0.0002
sr: [00:08.927000] scpi_tcp: Successfully sent SCPI command: ':CHAN1:SCAL?'.
sr: [00:09.303000] scpi: Got response: '2.000e-01', length 9.
sr: [00:09.304000] scpi_tcp: Successfully sent SCPI command: ':CHAN2:SCAL?'.
sr: [00:09.703000] scpi: Got response: '2.000e-01', length 9.
sr: [00:09.705000] rigol-ds: Current vertical gain:
sr: [00:09.706000] rigol-ds: CH1 0.2
sr: [00:09.708000] rigol-ds: CH2 0.2
sr: [00:09.710000] scpi_tcp: Successfully sent SCPI command: ':CHAN1:OFFS?'.
sr: [00:10.091000] scpi: Got response: '4.000e-01', length 9.
sr: [00:10.093000] scpi_tcp: Successfully sent SCPI command: ':CHAN2:OFFS?'.
sr: [00:10.504000] scpi: Got response: '2.880e-01', length 9.
sr: [00:10.507000] rigol-ds: Current vertical offset:
sr: [00:10.509000] rigol-ds: CH1 0.4
sr: [00:10.510000] rigol-ds: CH2 0.288
sr: [00:10.512000] scpi_tcp: Successfully sent SCPI command: ':CHAN1:COUP?'.
sr: [00:10.911000] scpi: Got response: 'DC', length 2.
sr: [00:10.915000] scpi_tcp: Successfully sent SCPI command: ':CHAN2:COUP?'.
sr: [00:11.331000] scpi: Got response: 'DC', length 2.
sr: [00:11.333000] rigol-ds: Current coupling:
sr: [00:11.335000] rigol-ds: CH1 DC
sr: [00:11.337000] rigol-ds: CH2 DC
sr: [00:11.339000] scpi_tcp: Successfully sent SCPI command: ':TRIG:EDGE:SOUR?'.
sr: [00:11.727000] scpi: Got response: 'CHANNEL2', length 8.
sr: [00:11.729000] rigol-ds: Current trigger source CHANNEL2
sr: [00:11.731000] scpi_tcp: Successfully sent SCPI command: ':TIM:OFFS?'.
sr: [00:12.124000] scpi: Got response: '8.00e-04', length 8.
sr: [00:12.126000] rigol-ds: Current horizontal trigger position 0.0008
sr: [00:12.129000] scpi_tcp: Successfully sent SCPI command: ':TRIG:EDGE:SLOP?'.
sr: [00:12.511000] scpi: Got response: 'NEGATIVE', length 8.
sr: [00:12.512000] rigol-ds: Current trigger slope NEGATIVE
Channel groups:
    CH1: channel CH1
    CH2: channel CH2
    LA: channels D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 D14 D15
Supported configuration options across all channel groups:
    (null):
    limit_frames:
    timebasesr: [00:12.524000] hwdriver: sr_config_get(): key 30010 (timebase) sdi 017BBF80 cg NULL -> (uint64 200, uint64 1000000)
sr: [00:12.528000] hwdriver: sr_config_list(): key 30010 (timebase) sdi 017BBF80 cg NULL -> [(uint64 2, uint64 1000000000), (5, 1000000000), (10, 1000000000), (20, 1000000000), (50, 1000000000), (100, 1000000000), (500, 1000000000), (1, 1000000), (2, 1000000), (5, 1000000), (10, 1000000), (20, 1000000), (50, 1000000), (100, 1000000), (200, 1000000), (500, 1000000), (1, 1000), (2, 1000), (5, 1000), (10, 1000), (20, 1000), (50, 1000), (100, 1000), (200, 1000), (500, 1000), (1, 1), (2, 1), (5, 1), (10, 1), (20, 1), (50, 1)]
 - supported values:
      2 ns
      5 ns
      10 ns
      20 ns
      50 ns
      100 ns
      500 ns
      1 us
      2 us
      5 us
      10 us
      20 us
      50 us
      100 us
      200 us (current)
      500 us
      1 ms
      2 ms
      5 ms
      10 ms
      20 ms
      50 ms
      100 ms
      200 ms
      500 ms
      1 s
      2 s
      5 s
      10 s
      20 s
      50 s
    triggersource: sr: [00:12.562000] hwdriver: sr_config_get(): key 30007 (triggersource) sdi 017BBF80 cg NULL -> 'CHANNEL2'
sr: [00:12.565000] hwdriver: sr_config_list(): key 30007 (triggersource) sdi 017BBF80 cg NULL -> ['CH1', 'CH2', 'CH3', 'CH4', 'EXT', 'AC Line', 'D0', 'D1', 'D2', 'D3', 'D4', 'D5', 'D6', 'D7', 'D8', 'D9', 'D10', 'D11', 'D12', 'D13', 'D14', 'D15']
CH1, CH2, CH3, CH4, EXT, AC Line, D0, D1, D2, D3, D4, D5, D6, D7, D8, D9, D10, D11, D12, D13, D14, D15
    triggerslope: sr: [00:12.580000] hwdriver: sr_config_get(): key 30004 (triggerslope) sdi 017BBF80 cg NULL -> 'f'
sr: [00:12.585000] hwdriver: sr_config_list(): key 30004 (triggerslope) sdi 017BBF80 cg NULL -> ['r', 'f']
r, f (current)
    horiz_triggerpos:
    num_hdiv
    samplerate
    data_source: sr: [00:12.591000] hwdriver: sr_config_get(): key 40004 (data_source) sdi 017BBF80 cg NULL -> 'Live'
sr: [00:12.593000] hwdriver: sr_config_list(): key 40004 (data_source) sdi 017BBF80 cg NULL -> ['Live']