On 28.11.2015 18:53, Aurelien Jacobs wrote: > I think you should be able to get sigrok-cli to grab your data the way > you want, with appropriate parameters. > For example you should use --config data_source=Memory to grab the whole > memory instead of just the visible screen.
Interesting -- are the whole features of the driver documented anywhere? Because I searched and couldn't find anything. Above all, to be honest, this was the reason for doing my own thing. I was just not able to find documentation on how to capture traces with sigrok and when I tried the only examples I found (http://sigrok.org/wiki/Rigol_DS2072) they automatically messed up all my measurement settings (i.e. memory depth), so I immediately discarded this. Now that I'm writing these words, I was doubting myself and thought, well, maybe I just did a shitty search. But to be honest, I can reproduce the "not finding anything" experience: I find this: http://sigrok.org/wiki/Getting_started Where both links of the "Using sigrok with an oscilloscope" section aren't written yet. "sigrok oscilloscope trace" finds two blog entries, both of which deal with logic analyzers. "sigrok oscilloscope example" finds http://sigrok.org/wiki/Oscilloscopes which deals with the internal storage format. "sigrok oscilloscope capture" finds links that are already all purple (combination of the above two). To me, this lack of documentation is probably the biggest problem that sigrok has. I also tried building pulseview (because I think it does some capture "under the hood"), but couldn't build it successfully. Maybe I'll start another thread on the mailing list. > You can have a look a the driver source to get an idea of the options > you can set: > http://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=src/hardware/rigol-ds/api.c;h=1f784cfce344177d997a08d5fc73e5a8f0f8e76a;hb=HEAD#l639 Yup, seems to support everything (setting memory depth), even with the stupid Rigol workaround (:RUN before :ACQ:MDEP). But one has to know how to use it :-/ > Not sure why you didn't go straight to the latest version (03.04): > http://beyondmeasure.rigoltech.com/acton/fs/blocks/showLandingPage/a/1579/p/p-001a/t/page/fm/0 Short answer: Because I'm a fucking idiot. Sure enough, I downloaded 03.04 and flashed my oscilloscope with it and all the bugs are fixed. It really were firmware bugs :-/ Don't know where I pulled the old firmware from, to be honest. Thank you so much for that hint, I was really getting super despearate. > It may already work... Yup, pretty sure. I think I'll give it another shot. > I hope this helped at least a little bit. > > Let us know if you manage to do what you want, and tell us what > improvement you would need from sigrok for your use case. Feedback is > always useful. Sure, the sigrok crew is always super helpful and I really appreciate the project. I'll happily provide feedback, it really doesn't fall on deaf ears with you guys. Best regards and thanks again, Johannes ------------------------------------------------------------------------------ _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
