# Missing Data in single shot in MSO **URL:** \ **Category:** Logic MSO\ **Created:** [August 28, 2026, 3:17pm UTC](https://discuss.saleae.com/t/missing-data-in-single-shot-in-mso/3799 "2026-08-28T15:17:29Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![sebastian.wissig](https://avatars.discourse-cdn.com/v4/letter/s/e47774/32.png) [@sebastian.wissig](https://discuss.saleae.com/u/sebastian.wissig)\ **Post date:** [August 28, 2026, 3:17pm UTC](https://discuss.saleae.com/t/missing-data-in-single-shot-in-mso/3799/1 "2026-08-28T15:17:29Z")
Hello, we have several years experience with Logic analyzers and we now got the MSO be able to measure analog and digital together. Using an extra scope makes timing measurements always difficult. It seems the hardware is very capable but the software needs some tuning. Since the digital single shot feature did not yet make it into the MSO software (at least not as comfortable as on the Logic versions) we were using the analog input as a trigger. Long story short, it did not work that well. We hocked up one analog channel to the 1 kHz reference clock to create a trigger signal while also capturing two digital one. We see gaps in the digital trace. ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/2/2b38f21edb257d0ac613ffb670a073a173613e52.png) ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/b/b3a4bd52afc6ac423f0b05f4dcd47c7baa39953e.png) We also have the bug that single shot is set, but the trace runs forever. ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/e/ea9933f045a2a0c0bd688f9e8c1f1cb3f637abc6.png) Well, no. At least not every time I have confidence that the MSO software will reach the same maturity as the as the standard logic versions. Best regards Basti ---
**Author:** ![BitBob](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/bitbob/32/2292_2.png) [@BitBob](https://discuss.saleae.com/u/BitBob)\ **Post date:** [August 28, 2026, 7:12pm UTC](https://discuss.saleae.com/t/missing-data-in-single-shot-in-mso/3799/2 "2026-08-28T19:12:52Z")
> [@sebastian.wissig](#): > > We also have the bug that single shot is set, but the trace runs forever. This seems similar to my post (issue #2: **One Shot Trigger Problems** ) … you might be able work around the one shot trigger issue by extending the holdoff, as long as your capture buffer/transfer time is less than the holdoff time. If sampling at maximum sample rates and capturing multiple channels, you might not be able to get it to trigger & stop. > [@Limitations of Logic MSO digital streaming (derived from analog)?](https://discuss.saleae.com/t/limitations-of-logic-mso-digital-streaming-derived-from-analog/3733): > > I was running into some problems trying to decode a quad-SPI flash memory device. Specifically, I was trying to configure a ‘one shot’ capture of the entire power-up transaction, but running into two problems: The digital data packet loss on derived digital signals (even though all analog data was captured successfully) The ‘one shot’ trigger failed to actually STOP the capture properly Background: Initial serial communications is ~ 5 MHz SPI, but switches to ~20 MHz QSPI mode. The SPI is n… Meanwhile, regarding: > [@sebastian.wissig](#): > > We see gaps in the digital trace. … are the gaps all ~12ms wide at start of capture? If so, I think it is a known issue, per: > [@Repeatable "Channel Inactive" "blips" on digital channels cause SPI decoder to be thrown off](https://discuss.saleae.com/t/repeatable-channel-inactive-blips-on-digital-channels-cause-spi-decoder-to-be-thrown-off/3660): > > 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). … And > [@Single shot oddities](https://discuss.saleae.com/t/single-shot-oddities/3685): > > Logic MSO just arrived today but not getting it to do what I need. I saw some of the prior questions in the forum that explain what I need - single shot with controlled capture length (pre and post trigger) from a digital input(s) is not available yet. I think this older forum post covers my use case: [Single Shot Recording duration settings and few other questions - #2 by timreyes](https://discuss.saleae.com/t/single-shot-recording-duration-settings-and-few-other-questions/3658/2) in which case this is sort of a me too post - though I’m trying to work around it by using the scope to trigger. … ---
**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:27am UTC](https://discuss.saleae.com/t/missing-data-in-single-shot-in-mso/3799/3 "2026-09-25T05:27:13Z")
Came here to say that the 12ms digital channel issue is causing issues for our small fleet of MSOs that we’re evaluating where I work. Overall, I’m surprised that the MSO seems to suffer from a major feature regression compared to the Logic Pro line wrt digital captures. ---
**Author:** ![markgarrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/markgarrison/32/23_2.png) [@markgarrison](https://discuss.saleae.com/u/markgarrison)\ **Post date:** [October 7, 2026, 8:22pm UTC](https://discuss.saleae.com/t/missing-data-in-single-shot-in-mso/3799/4 "2026-10-07T20:22:52Z")
Hello all, We just shipped 2.4.48, which contains a fix for the gap in digital channels that occurred every time the channel was enabled. That release contains a large number of other fixes too. Please update and let me know if you are still experiencing issues! > [@Logic 2.4.48](https://discuss.saleae.com/t/logic-2-4-48/3820): > > 2.4.48 Download Links [Windows [x86\_64]](https://downloads2.saleae.com/logic2/Logic-2.4.48-windows-x64.exe)[Windows [Arm64]](https://downloads2.saleae.com/logic2/Logic-2.4.48-windows-arm64.exe)[Linux [x86\_64]](https://downloads2.saleae.com/logic2/Logic-2.4.48-linux-x64.AppImage)[Linux [Arm64]](https://downloads2.saleae.com/logic2/Logic-2.4.48-linux-arm64.AppImage)[MacOS [x86\_64]](https://downloads2.saleae.com/logic2/Logic-2.4.48-macos-x64.zip)[MacOS [Apple Silicon]](https://downloads2.saleae.com/logic2/Logic-2.4.48-macos-arm64.zip)2.4.48 Welcome to the 2.4.48 release of Logic! As always, [feedback is very welcome](https://www.saleae.com/contact)! You might notice that we’ve skipped Logic 2.4.47. We decided to cancel that release, but still sent it out to a few users who needed priority bug fixes. The release notes below contain changes from both releases. What’s New Add support for new Logic Pro 16 hardware revisions. (Minor suppl…