# Saleae team - we would love samples of protocol captures! **URL:** \ **Category:** Uncategorized\ **Created:** [May 15, 2020, 10:48pm UTC](https://discuss.saleae.com/t/saleae-team-we-would-love-samples-of-protocol-captures/520 "2020-05-15T22:48:18Z")\ **Posts on this page:** 1\ **Showing post:** 34
**Author:** ![huffman](https://avatars.discourse-cdn.com/v4/letter/h/71e660/32.png) [@huffman](https://discuss.saleae.com/u/huffman)\ **Post date:** [June 29, 2020, 11:47pm UTC](https://discuss.saleae.com/t/saleae-team-we-would-love-samples-of-protocol-captures/520/34 "2020-06-29T23:47:24Z")
Ideally with the generator case you would have one generator per state, which I believe Mark’s did. There’s a benefit there to keeping the relevant data for the current state within the current scope, but the awkwardness of using yield to both send and receive frames made it a bust in our opinion. Looking forward to seeing how you setup all the flags! Are there any features that you think would have been helpful? For instance, we don’t have native support for bitfields, and if you break them out into separate data.\* fields, it can create quite a few columns in the data table. --- _[View the full topic](https://discuss.saleae.com/t/saleae-team-we-would-love-samples-of-protocol-captures/520)._