I have experience my capture to stop before the number of samples I had
configured in Pulseview was reached. This was most likely caused by some
error on the USB bus, caused by electromagnetic interference (EMI) or an
electrostatic discharge event (ESD). I manually started a new capture,
and got the information I need.
Now I would like to capture data for a longer period (days), with a low
sample rate (100Hz). I'm not present to restart the capture if stuff
goes wrong.
Is it possible to setup Pulseview to automatically resume or start a new
capture if stuff goes wrong until the configured number of samples has
been reached?
Is this possible in sigrok-cli by using --continuous and restarting the
process with some bash magic?
Is this the best place to ask these questions?
Versions, libraries and features:
PulseView
0.5.0-git-7e5c839
Qt
5.7.1
glibmm
2.42.0
Boost
1_60
exprtk
20200101
libsigrok
0.6.0-git-6dc55e4/4:0:0 (rt: 0.6.0-git-6dc55e4/4:0:0)
- glib
2.44.1 (rt: 2.44.1/4401:1)
- zlib
1.2.11
- libzip
1.5.2
- minilzo
2.10
- 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.6.0-git-24ba9e1/4:0:0 (rt: 0.6.0-git-24ba9e1/4:0:0)
- 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
Kind regards,
Cedric
_________________________________________________________________
________________________________________________________
Your E-Mail. Your Cloud. Your Office. eclipso Mail & Cloud.
https://www.eclipso.de
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
