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

[dario]

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.

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”}

[timreyes]

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

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.

[dario]

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.