It is not possible to use time bases larger than 50 ms. Affects both USB & LAN connection. In PulseView when you select time base larger than 50 ms and press the run button, nothing happens and after 10-15 it is possible to press the stop button. There is probably a bug in the communication protocol as the scope sends a wrong answer to the trigger command.
I attach a log level 5 from pulseview, where I first capture data using 5 ms base and then 100 ms base.
I have something similar happening:
Setup is Windows7 machine, DS1102d, Pulseview.
I am reading an I2C signal in a well-proven target system as a test for
Pulseview and to be used later in real troubleshooting elsewhere once I get it all
to perform as hoped.
If I set the timebase to greater than 50uS I cannot reliably read and decode
the SCL / SDA stream. This also sets the maximum capture period to 600uS and I
don't see a way to increase this. The result is I can only read and decode a couple of bytes and not a whole data handshake.
Maybe I'm overlooking something simple. Any ideas anyone?
*** Bug 1108 has been marked as a duplicate of this bug. ***
Here is the log: https://files.honzamrazek.cz/5ms_100ms.txt (cannot be uploaded here as it has more than 1 MB)