On 01/08/2013 07:23 AM, Lior Elazary wrote: > Here is an example of what I mean. Let say you have a device that outputs > different SPI data every 500ms to communicate with another device. So > device A will output 0x01 <wait 500ms> 0x02 <wait 500ms> 0x03 etc... Now > the mso19 does not have a sufficient buffer to get the whole set of data, > but I could set up a trigger to get the first data, rearm the trigger and > get the second data, etc... Therefore there will be a gap in the data > were the trigger had to rearm, but I dont care about that time, as long > as that time is sufficiently short between dead zones. So it would be > nice if I can just collect all the data from this device and use a > protocol decoder to see what is this data is without having to have a > huge sample buffer. Is there another way to achieve this?
Ok, that is an entirely different use case indeed. This is entirely up to the frontend to drive. Effectively it needs to start a new acquisition whenever the old one ends, optionally keeping the old one on screen or scrollable or something. sigrok-cli doesn't have such a mode currently, but it should be pretty easy to implement. > Thanks, this helps. However, my question was more on how to pass the > value to the horiz_triggerpos from the GUI. Since this scope has only > 1024 samples buffer, I may want to get 50 samples before the trigger and > then 974 samples after the trigger. For now you can specify > horiz_triggerpos=50 in sigrok client, but how would I do that in the GUI? > It would be nice if there was a vertical line you can drag. I don't think pulseview supports this yet. Joel, care to comment? Incidentally, horiz_triggerpos (SR_HWCAP_HORIZ_TRIGGERPOS) is intended for use with analog (scope) data, for logic data SR_HWCAP_CAPTURE_RATIO is used. I remember thinking at the time that the two are really the same thing -- how much data to capture before the trigger -- but was unsure if there was perhaps some reason to keep them separate. If anyone has further insights in this, please comment. To make matters worse, SR_HWCAP_CAPTURE_RATIO is specified as a number from 0-100, and SR_HWCAP_HORIZ_TRIGGERPOS as a number from 0.0-1.0. Oh, the humanity. -- Bert Vermeulen [email protected] email/xmpp ------------------------------------------------------------------------------ Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 _______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
