Download Links
Check out the Saleae Logic 2 Extension Marketplace! - Read more about the Marketplace on the Saleae blog!
2.3.49
What’s New
Measurement API
We’ve expanded the capabilities of the Measurement API with a focus on Analog channels as part of a longer term product development plan to help our customers verify, debug and test analog problems such as signal integrity issues and many more. Please keep in mind that this API is a preview-release, and we’re planning on making breaking changes before it’s finalized. Because of this, measurements utilizing the new API can’t be published to the marketplace. We’d love to hear your feedback on these changes.
- Measurements now include the ability to display annotations to help visually aid in the understanding of a measurement. We currently support showing or hiding annotations for all measurements enabled for a range.
- Each range can have its own set of measurements
- We’ve updated the styling of measurements in the sidebar
- The measurement API has new capabilities more details can be found here
Note: In order to test the new capabilities of the Measurement API you will need to set an environment variable in your shell or command prompt and start the app from the terminal.
Windows:
If using Command Prompt:
set ENABLE_MEASUREMENTS_V2=1
C:\Program Files\Logic\Logic.exe
If using Powershell:
$env:ENABLE_MEASUREMENTS_V2=“1”
C:\Program Files\Logic\Logic.exe
Mac:
export ENABLE_MEASUREMENTS_V2=1
/Applications/Logic2.app/Contents/MacOS/Logic
Linux:
export ENABLE_MEASUREMENTS_V2=1
./Logic-2.3.48-master.AppImage
Jump to Time
- You can now jump to a specific time in your capture using Ctrl+J
Improvements
- Edit channel names quickly in the left channel name area using the
Tab
key - Added preference (off by default) to change tab name automatically when saving a capture. This complements the existing feature which names the capture filename using the tab name.
- Data Table search string is now persisted for a tab between captures
Bug Fixes
- Fixed issue where in some cases opening a capture would yield in the analyzer getting stuck at 0
- While not part of the application, we fixed an issue in the marketplace web service where some extensions were not updating correctly
- Fixed issue where some html tags were not rendered correctly for extension README.md files
- Fixed issue with 2.3.48 where opening a saved capture would not display all data
- Fixed issue with 2.3.48 where data exports were corrupted
- Fixed issue with 2.3.48 where the horizontal scroll bar was hidden if an analyzer trigger was enabled