Bug - Incorrect Trigger handling with Analyzers

Software Info

  • Environment: production
  • Branch: master
  • Commit: f7301b3b38816555bc63015a328a6c76985a2d78
  • Version: 2.4.22
  • AutomationVersion: 1.0.0

Tested Analyzers

  • Async Serial
  • SPI

Issues

The following issues were seen while using a triggered capture with the aforementioned analyzers.

  • Panning to the right is restricted to whatever is smaller between the following two situations:
    1. The region of the window based on the current zoom centered around the final bit parsed by an analyzer.
    2. When the left edge of the window touches the left edge of the capture (very noticable when using the “Trim pre-trigger data” option).
  • Data outside of the “Capture duration after trigger” window is still parsed and displayed.

Steps to Reproduce

  1. Enable required digital channels to analyze UART or SPI.
  2. Configure the analyzer to work with the selected digital channels.
  3. Select “Trigger” as your capture type.
  4. Set the “Pattern and Channel” setting to detect a falling edge of either the UART RX or the SPI CSN digital channel.
  5. Set the “Capture duration after trigger” setting to something like “20 ms”.
  6. Set the “Trim pre-trigger data” value to something like “1 ms”.
  7. Start the capture.
  8. Send a single byte of data.
  9. Notice the following:
    • The duration of the capture after the trigger is reduced to a few milliseconds.
    • Panning to the right stops once the left side of the window touches the start of the trimmed data.
    • Zooming toward the right side of the capture is centered around the final bit of data analyzed and gets smaller as you zoom in.
  10. Start the capture again.
  11. Send a stream of bytes that would exceed the configured capture duration.
  12. Notice the following:
    • The analyzer still displays the data that was captured outside of the configured “Capture duration after trigger” setting.
    • Zooming in is still centered around the final bit of data analyzed but now extends past the actual signal displayed.

Images

See comment about feature-requests version.

Note that I also posted this on feature-requests and it has images: Bug - Incorrect Trigger handling with Analyzers - Logic 2 - Ideas and Feature Requests - Saleae

@ccarrmcmahon Thanks for the detailed report of the bug, and sorry for the trouble with that! We’ll get this on our backlog for further investigation.