Hi Mark, thanks for the update. Yes, I noticed these other issues as well. I’m OK with using Logic 1.x, I just always check how my analyzer behaves in Logic 2.x and report any issues.
For my autobaud detection I ran into the issue that I cannot re-run the analyzer in Logic 2. I could solve this issue in my case by measuring the ones and zeros of my 0x55 sync byte at the beginning of each protocol frame. For a generic autobaud detection the existing functions in the API are not well suited in my mind. Being able to get a histogram for a certain pulse range would be the best approach in my mind as mentioned in another topic regarding autobaud. This approach would still require a re-run though.
I ran into an issue with Logic 1.x when I had my NeedsRerun based detection. When the analyzer was already present but without autobaud activated and you activate it later, I couldn’t figure out how to trigger a re-interpretation of the data. See Autobaud detection