skyrift,
The original buffer draw code has a shed load of bugs in it
More news shortly
skyrift:
Got my DSO Quad a few weeks ago, and it has so far been brilliant. There seems to be something wierd going on when using normal or single mode though, where even though the screen refreshes as soon as the trigger fires, it still shows the old trace. This is particularly noticeable when the time scale is changed to try and look at a feature in the pulse properly, the trigger fires again on the pulse, but the even though i’ve changed the time scale, the waveform looks the same. Playing around a bit more, it looks like it might have something to do with filling the buffer, when the time per div is set to 100ms or so, i can take some time for the buffer to completely fill, or something. Using the scan mode at this sort of resolution is particularly useless. On a similiar note, when a trace has been caught, trying to scroll through the buffer doesn’t always work, the trigger line and the background scrolls, but the trace doesn’t. Again, only with certain timescales, above a few ms per div, i think. Anyway, just thought i’d post to see if anyone else can confirm this behaviour, and if we can get a fix.
Thanks!
. The capture buffer is correct but when it is drawn and scrolled it does not update the window region correctly. I have re-written the screen write for the real time DSO buffer, and this will be in the first release (coming soon) of an alternative DSO software for the Quad.
.