Thanks @P.Jaquiery, feel free to send a google drive link here or via support - https://contact.saleae.com/hc/en-us/requests/new - just mention that it’s a sample for the software team and we’ll get it.
Python support for raw data access in analyzers is a big part of our plans, but it’s quite a ways out. There are a lot of challenges there, performance not the least of them. In the short term, it should be pretty easy to write a C++ analyzer that simply forwards edges into the new FrameV2 format, which can be consumed by python analyzers. Next week we’ll be working on the ability for a python high level analyzer (HLA) to receive data from multiple input analyzers.
Custom python measurements might be another good solution for looking at performance statistics. It won’t integrate with analyzers, and they can only be applied two a single channel at a time, but custom python measurements is an easy way to run some math on top of all the digital transitions over a span of time. We won’t be working on measurements again for a little while, since we have our work cut out for us just with analyzers though.
The more captures we can get the better! Especially if they contain complete transactions, for instance starting the recording before any initialization communication occurs.
Also any description of what we’re looking at would help.