# Trigger on multiple bytes

**URL:** <https://discuss.saleae.com/t/trigger-on-multiple-bytes/3619>\
**Category:** Logic 2 Software\
**Created:** [January 21, 2026, 3:08pm UTC](https://discuss.saleae.com/t/trigger-on-multiple-bytes/3619 "2026-01-21T15:08:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![daniel01liden](https://avatars.discourse-cdn.com/v4/letter/d/74df32/32.png) [@daniel01liden](https://discuss.saleae.com/u/daniel01liden)\
**Post date:** [January 21, 2026, 3:08pm UTC](https://discuss.saleae.com/t/trigger-on-multiple-bytes/3619/1 "2026-01-21T15:08:05Z")

</div>

Hi.

Looking at triggers, escpecially on protocol.

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/9/91d348a42b407cd52f25504fa2b1d1fa8f68c867.png)

I can without any problems have one byte as query, in this example 0x04 and then I see a trigger when 0x04 is read.

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/d/dd36422589153f03c0354b8d131608e76d6df8cd.png)

Now I would like to have two bytes trigger, for example 0x04 0x00, so I put “0x04 0x00” as the Query, but no trigger happens. Is there something I have missed, or does this feature simply not exist?

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/d/dc58d9cd264e4f23be7a77b60544d324ecf3bea1.png)

---

<div class="post-metadata">

**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:** [January 23, 2026, 2:05am UTC](https://discuss.saleae.com/t/trigger-on-multiple-bytes/3619/2 "2026-01-23T02:05:27Z")

</div>

@daniel01liden Although our software’s Trigger View doesn’t natively support triggering on a search term spanning multiple frames, you may be able to work around this by utilizing an extension that combines frames, then you could trigger off of the results within a single combined frame.

Here is an example in the image below utilizing the “Time Delimiter Chunking” extension available from our Extensions Marketplace.

 ![Screenshot 2026-01-22 190251](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/1/167b7cb499d0023550eb251045857239e0f45473.png)

Hope this helps!