Caveat: while connected to this 'scope ngscopeclient is spitting errors:
ERROR: RigolOscilloscope::GetInterleaveConflicts not implemented for this model
Reading this thread I gather that means it should be impossible for ngscopeclient to control the timebase, however it does in fact try - with some rather random results.
Sometimes it is possible to get it into a state where it's fetching captures at a rate and depth that's in the right ball park, but each capture appears to be at a different timebase (one of a selection of 3-4 states perhaps) even though the display on the 'scope itself is not changing. The samples within the capture are also seemingly mis-ordered, with a 1KHz square wave turning into something... else.
I hope these screen captures will show the general vibe of what I'm trying to describe, but realise that I'm certainly missing key details. I would be delighted to put some time into debugging this if anyone has a moment to give me some pointers for how to be most helpful!
This behaviour is consistent on a windows machine with ngscopeclient built yesterday (with everything git pulled to head, "0.1-dev+9f2d72b6") and on a linux machine where I last built a while ago ("0.1-dev+b298d22c"), so it's not a recent regression at least. I note the ticket for adding support for these was opened a long time ago with no further comments, so presumably it worked for a while?
Caveat: while connected to this 'scope ngscopeclient is spitting errors:
ERROR: RigolOscilloscope::GetInterleaveConflicts not implemented for this modelReading this thread I gather that means it should be impossible for ngscopeclient to control the timebase, however it does in fact try - with some rather random results.
Sometimes it is possible to get it into a state where it's fetching captures at a rate and depth that's in the right ball park, but each capture appears to be at a different timebase (one of a selection of 3-4 states perhaps) even though the display on the 'scope itself is not changing. The samples within the capture are also seemingly mis-ordered, with a 1KHz square wave turning into something... else.
I hope these screen captures will show the general vibe of what I'm trying to describe, but realise that I'm certainly missing key details. I would be delighted to put some time into debugging this if anyone has a moment to give me some pointers for how to be most helpful!
This behaviour is consistent on a windows machine with ngscopeclient built yesterday (with everything git pulled to head, "0.1-dev+9f2d72b6") and on a linux machine where I last built a while ago ("0.1-dev+b298d22c"), so it's not a recent regression at least. I note the ticket for adding support for these was opened a long time ago with no further comments, so presumably it worked for a while?