# Repeatable "Channel Inactive" "blips" on digital channels cause SPI decoder to be thrown off

**URL:** <https://discuss.saleae.com/t/repeatable-channel-inactive-blips-on-digital-channels-cause-spi-decoder-to-be-thrown-off/3660>\
**Category:** Logic MSO\
**Created:** [March 7, 2026, 12:34am UTC](https://discuss.saleae.com/t/repeatable-channel-inactive-blips-on-digital-channels-cause-spi-decoder-to-be-thrown-off/3660 "2026-03-07T00:34:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dario](https://avatars.discourse-cdn.com/v4/letter/d/bc79bd/32.png) [@dario](https://discuss.saleae.com/u/dario)\
**Post date:** [March 7, 2026, 12:34am UTC](https://discuss.saleae.com/t/repeatable-channel-inactive-blips-on-digital-channels-cause-spi-decoder-to-be-thrown-off/3660/1 "2026-03-07T00:34:16Z")

</div>

Hi All,

Everytime I use a digital channel in a free running capture there seems to always be a drop in communication (or something) towards the beginning of the capture. This seems to happen towards the beginning of the capture and has a tendency to throw of the SPI decode (SPI with no CS) and can’t be easily recovered since deleting data before/after a point in the capture is not yet possible with the Logic MSO app (deleting data before/after tended to resolve framing issues on the logic pro).

Note that this does not seem to happen in triggered mode, at least as far as I have seen.

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

| Model | Logic MSO |
| --- | --- |
| Serial Number | 7USVN |
| Hardware Revision | Rev0B/Rev0F |
| Analog Channels | 4 |
| Analog Bandwidth | 200 MHz |
| Analog Sample Rate | 1.6 GS/s |
| Analog Vertical Resolution | 12 Bit |
| Maximum Analog Buffer Size | 1 Billion Samples |
| Firmware Version | 1.0.54 |

{“Environment”:“production”,“Branch”:“master”,“Commit”:“a2af641e0c8b389637c5f0f2cbd390b7d33f5ee3”,“Version”:“2.4.42”,“AutomationVersion”:“1.0.0”,“MachineID”:“7e272189-c463-4698-a587-4ba447ab2844”,“PID”:70275,“LaunchId”:“9d6cef73-e3f8-423a-8596-e5e15faa4f2b”,“Architecture”:“arm64”}

---

<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:** [March 12, 2026, 3:21am UTC](https://discuss.saleae.com/t/repeatable-channel-inactive-blips-on-digital-channels-cause-spi-decoder-to-be-thrown-off/3660/2 "2026-03-12T03:21:04Z")

</div>

@dario Sorry about this issue! Are the gaps rougly 12ms long like in the image below?

 ![Screenshot 2026-03-11 211851](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/7/790c098ce1ea0e143502cda44415b62138ab0bac.png)

If so, the gaps at the data start are unfortunately a known issue right now. We do plan to get it fixed! Let me check on our timeline for that and we can provide an update on that for you.

---

<div class="post-metadata">

**Author:** ![dario](https://avatars.discourse-cdn.com/v4/letter/d/bc79bd/32.png) [@dario](https://discuss.saleae.com/u/dario)\
**Post date:** [April 19, 2026, 6:18pm UTC](https://discuss.saleae.com/t/repeatable-channel-inactive-blips-on-digital-channels-cause-spi-decoder-to-be-thrown-off/3660/3 "2026-04-19T18:18:59Z")

</div>

Yep exactly 12ms. Thanks for the the info on this.

The main issue with this is when there’s a digital decode enabled it can get misaligned with the data if it’s a decode like SPI without a CS.

Being able to trim the data like with Logic Analyzer UI would help get things re-aligned (protocol analyzer wise) in the meantime.

This does not happen in trigger mode so when I really need it to decode stuff properly I can go about it that way.

---

<div class="post-metadata">

**Author:** ![gary.grimm](https://avatars.discourse-cdn.com/v4/letter/g/ecae2f/32.png) [@gary.grimm](https://discuss.saleae.com/u/gary.grimm)\
**Post date:** [September 25, 2026, 5:24am UTC](https://discuss.saleae.com/t/repeatable-channel-inactive-blips-on-digital-channels-cause-spi-decoder-to-be-thrown-off/3660/4 "2026-09-25T05:24:12Z")

</div>

Looks like this is still an issue. I bought 4x MSOs earlier this year but folks on my team are refusing to use these and stealing oscilloscopes from the lab due to issues like this. This really makes it difficult to use analyzers with the MSO. To see this reported as a known issue back in April with no fix in September is beyond disappointing.