On Sat, Nov 02, 2013 at 09:54:18AM +0000, Joel Holdsworth wrote: > > > 3. GUI tools that provide a continuously updating display (none > > yet existing but I would like to write one!) > > I plan this for PulseView. Though I didn't expect there would be a > problem with getting the full data of each sweep.
Yeah, that's the fundamental issue here at least with the Rigols. When the scope is running, it's triggering and updating of its own accord, and all you can do on the wire is ask for what's on the screen right now for each channel, one channel at a time. So there's no way to guarantee that you're getting a coherent set of data for a single sweep, unless you stop the scope first and then read out. > I've been wanting to do digital phosphor, but with a time machine type > thing that allows you to step back to viewing earlier sweeps. Digital phosphor would be fine in the "live" mode, but you wouldn't reliably be able to go back through individual sweeps. To do that you'd need to have run the capture in the start-wait-stop-read way. > Still, I do think there's a place to have something different, maybe > something like QtDSO in the sigrok ecosystem. That's the sort of tool I've been meaning to bash out at some point, probably in python using the bindings. Not so much as a finished product but more just as an experiment - I'd be quite happy to see all the functionality just rolled into pulseview eventually. Martin ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
