On Tue, Aug 2, 2016 at 7:33 AM Bert Vermeulen <b...@biot.com> wrote: > They were originally intended for the specific case of oscilloscope output. > Scopes do a capture to an internal buffer, then send that buffer to the > sigrok host, and then wait for a trigger to do it all over. That means the > second batch of data is not contiguous with the one before it, or the one > after -- it's a frame i.e. internal buffer worth of data. >
Ah! I think that solves an issue with the jyetech dos112A driver. It needs to add frame marks. Just around each packet, as it does small frames. The next question is then how do I tell pulseview to show me the next frame in a multi-frame capture? Also, this is something I can handle in gnuplot output. It has a way of representing "discontinuous" data. Not sure how to do that in a csv file, or if it even makes sense. For vcd - well, I'll investigate. > I'm thinking some kind of framing is needed for mixed signal devices, > > because you need multiple packets to build a sample across all the > sensors. > Yes, it does make some sense to re-use them for this. The Arachnid re:load > pro does this to group voltage and current measurements of a sample > iteration. Probably the scpi-pps driver should do this too, can't remember > why I didn't put that in there. > This is also important to me. One of the things I use sigrok for is capturing the chatter between the µcu & rf module in RC transmitters. I bought a USBeeAX clone so I could capture the relevant analog stick movement at the same time (unfortunately, it seems that analog input isn't working). I'll come back to this after I've got the tools I need for working with analog values, though.
------------------------------------------------------------------------------
_______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
