# Protocol trigger with custom analyzer **URL:** \ **Category:** Support\ **Created:** [September 30, 2021, 11:46pm UTC](https://discuss.saleae.com/t/protocol-trigger-with-custom-analyzer/1212 "2021-09-30T23:46:22Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![pat.summers](https://avatars.discourse-cdn.com/v4/letter/p/bbce88/32.png) [@pat.summers](https://discuss.saleae.com/u/pat.summers)\ **Post date:** [September 30, 2021, 11:46pm UTC](https://discuss.saleae.com/t/protocol-trigger-with-custom-analyzer/1212/1 "2021-09-30T23:46:22Z")
Hi all, I have written a custom analyzer to interpret Dshot signals. This was based on the SampleAnalyzer project (with the Analyzer2 class) and appears to work correctly. At least is identifies the 16 bits of a frame, tests the checksum, and displays the correct 11bit value (as a number) above each frame in the display. However, when I turn on the Trigger view in Logic 2.3.27, select my Dshot analyzer and supply a specific Query value (usually 48, but I have tried several others), it doesn’t seem to trigger. As I record a session, it reports a Live Trigger in the bottom left and in the bottom right it always says ‘Looking for first trigger’ despite reporting 48 as the frame value multiple times in the recording. What is wrong here? Is Protocol Triggering even possible with custom\_analyzers? It’s identifying the frame values. Is something else needed to allow it to trigger? Do I need to set an additional member or make a specific call to allow triggering? Beyond that, will it only trigger on a pattern match? Or can you apply some Boolean logic? For example, I would like it to trigger on any value above 48. Thanks, Pat ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [October 1, 2021, 11:18pm UTC](https://discuss.saleae.com/t/protocol-trigger-with-custom-analyzer/1212/2 "2021-10-01T23:18:09Z")
@pat.summers Sorry for the confusion caused by this. We certainly need to do a better job of highlighting the limitations of Trigger View. I’ll make sure to get our support articles updated. In summary, custom analyzers are currently not supported by Trigger View. The main reason is because our Trigger View currently relies on a new low level analyzer framing format that we call “frame v2.” Only a handful of analyzers support “frame v2” at the moment, and these are the analyzers that work with Trigger View. HLAs attached to these analyzers are also supported. Namely, the analyzers listed below: > **[HLA - Analyzer Frame Format](https://support.saleae.com/extensions/analyzer-frame-types)** > > Documentation for output produced by Saleae's built-in Analyzers We definitely need to extend support for Trigger View. As such, I’ve created a brand new idea post to start tracking user need for this. Trigger View is quite a powerful tool, and I’d suspect we would want to get to 100% compatibility across all analyzers at some point, including useful features such as the ability to one-shot trigger with it. > **[Trigger View Support for More Analyzers - Logic 2 - Ideas and Feature Requests...](https://ideas.saleae.com/b/feature-requests/trigger-view-support-for-more-analyzers)** > > Currently, custom analyzers are currently not supported by Trigger View. This includes analyzers that are still formatted as "frame v1." > > The main reason is because our Trigger View currently relies on a new low level analyzer framing format th ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [October 1, 2021, 11:23pm UTC](https://discuss.saleae.com/t/protocol-trigger-with-custom-analyzer/1212/3 "2021-10-01T23:23:00Z")
For your question below: > Beyond that, will it only trigger on a pattern match? Or can you apply some Boolean logic? For example, I would like it to trigger on any value above 48. We currently only pattern match, and we don’t have a way of setting the trigger to search for a range of values. I think this could be quite useful - something like allowing “greater than”, “less than”, “contains”, and other ways of triggering on a range of data. I’ve noted a comment on this in the idea post below. > **[More Complex Digital Triggers (One Shot, Protocol Results / Errors, State...](https://ideas.saleae.com/b/feature-requests/more-complex-triggering/)** > > I'm very happy using the Saleae analyzer > One missing feature (even on the new software logic 2.3.8) is having the possibility to not only trigger on rising or falling edge of the signal > but also trigger on sequential condition or bus value > The NCI ---
**Author:** ![bruce.p.clemens](https://avatars.discourse-cdn.com/v4/letter/b/da6949/32.png) [@bruce.p.clemens](https://discuss.saleae.com/u/bruce.p.clemens)\ **Post date:** [July 31, 2025, 12:18pm UTC](https://discuss.saleae.com/t/protocol-trigger-with-custom-analyzer/1212/4 "2025-07-31T12:18:01Z")
Is the feature to trigger from within the High Level Analyzer available? ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [August 1, 2025, 12:05am UTC](https://discuss.saleae.com/t/protocol-trigger-with-custom-analyzer/1212/5 "2025-08-01T00:05:51Z")
@bruce.p.clemens Thanks for writing in! This is not yet possible, however, the two posts below are where we are currently tracking this request. > **[More Complex Digital Triggers (One Shot, Protocol Results / Errors, State...](https://ideas.saleae.com/b/feature-requests/more-complex-triggering/)** > > I'm very happy using the Saleae analyzer > One missing feature (even on the new software logic 2.3.8) is having the possibility to not only trigger on rising or falling edge of the signal > but also trigger on sequential condition or bus value > The NCI > **[Allow trigger from HLA - Logic 2 - Ideas and Feature Requests - Saleae](https://ideas.saleae.com/b/feature-requests/allow-trigger-from-hla/)** > > Extend the HLA API to allow HLAs to produce trigger events based on the contents of an AnalyzerFrame. I’ve added a comment for you on both posts so we can track your need for this to be implemented. Feel free to add your vote to the above posts in case you wanted to receive any email updates on these!