Saleae Support
HomeDownloadUser ForumContact Us
Search…
Saleae Support
Orders & Shipping
Getting Started
User Guide
Software
Software Extensions
Protocol Analyzers
Analyzer SDK & Automation
Datasheets & Specifications
Troubleshooting
Installation Errors
The Software Fails to Launch
The Software Crashes
Logic is Not Detected
Getting your Machine ID
Getting your Software Crash Logs
Getting the Console Output
Error Message: ReadTimeout
The Captured Data Looks Incorrect
The Captured Data is Corrupted
A Protocol Analyzer Produces Unexpected Results
The 'Waiting for Trigger' Window Never Closes
Device USB VID and PID Information
Error Message: Out of Memory Exception Was Thrown
PC Performance Issues with Logic
Data Export Is Not Working
Error Message: A Logic Device Was Found, but There Was a Problem Connecting to It
Trouble Downloading the Latest Software
Logic Does Not Connect over USB 3.0
Why Am I Seeing Spikes in the Digital Capture?
Logic Interferes with My Circuit Operation
The Add Analyzer Menu Is Not Displaying
Other Drivers Interfere with Logic's Operation
The Maximum Sample Rate is Not Selectable
The Digital and Analog Recording on the Same Channel Appear Different
Advanced USB Debugging for USB 3.0 Users with Linux Kernels 3.3 and Older
Saving or Loading Anything Crashes the Software
Error Message: The application was unable to start correctly (0xc0000005)
Memory Usage with Triggered Captures
The Cabinet File disk1.cab has an Invalid Digital Signature (Logic 1.x)
Software Crashes with Virtual Desktops
Pre-Trigger Buffer is Incomplete
Linux Shared Memory Crash
Missing Files: api-ms-win-crt-runtime-l1-1-0.dll or msvcp140.dll
Known Issues on OS X
A Measurement Appears Incorrect
All Known Issues
USB 3.0 Cable Customer Notice (2017)
Warning Message: Logic Pro is running as a USB 2.0 device
Software Issues with Encryption Products
Linux Permission Requirements for Logic Software
My Rise Time and Fall Time Measurements Seem Incorrect
The Analog Waveform Loads Very Slowly after Capture Is Complete
Input Channels are Missing
Exported MATLAB File Does Not Open
Saleae Logic LED Blinks Red
Crashes Caused by macOS Mojave (10.14)
Troubleshooting Signal Crosstalk
Error Message: DeviceSetupFailure
Error Message: Unable to detect WebGL
Warning Message: Unsupported Version
Error Function: Device2::SetupDevice
Warning Message: Possible USB Host Controller Problem Detected
Error Message: StartCommandError
Logic 2 Error Messages
PC Detection Test
Apple M1 Support
CentOS Compatibility Issues
Error Message: Failed to Load Extension
CSV Export is Slow
Set an Analyzer Starting Point in your Capture
Logic 2 is Consuming Disk Space
Connection Conflicts with USB Debuggers
PC Restart Causes Logic to Disconnect
HLA Fails to Display Special Characters
Data Table Shows Incorrect Values
Error Message: Failed to Load Custom Analyzer
Error Message: Capture Stopped
Error Loading Marketplace Extensions
Error: Capture stopped because backlog data exceeded 90%
Mouse Scrolling Issues
FAQ
Returns & Warranty
Community
Tutorials
Oscilloscope Tutorial
Logic Analyzer Tutorial
Learning Portal
Example Projects
Powered By GitBook
Set an Analyzer Starting Point in your Capture
There are times where you may need to manually set the starting point in time for your protocol analyzer to begin decoding data.
Our protocol analyzers are designed to decode all captured data from beginning to end. Manually setting the starting point for an analyzer may fix issues such as data offsets, especially in cases where your capture begins right in the middle of a data message, which potentially causes errors for decoding the rest of your data.
One way to manually set the starting and ending points for protocol analyzer decoding is to delete portions of your capture as per the instructions below, such that the data that is left over is the relevant data that you need to decode.

Why Would I Need to Do This?

One common scenario for this need is when the beginning of your data capture occurs right in the middle of a data transaction/message as mentioned above.
In this case, our protocol analyzers don't have a way of determining if your capture begins right in the middle of a data transaction/message. It will simply begin decoding the moment it starts seeing digital transitions in your data. This can sometimes cause issues with decoding data, and may cause your decoded data to be incorrect, or offset in time.
For example, take a look at the ideal capture case below. The capture begins before the data begins. Therefore, the protocol analyzer is able to decode the entire message correctly.
Data capture begins before the Serial Message Begins
But... what happens if the capture began right in the middle of a data message, such as in the below image? In this case, it's possible that all subsequent decoded data may be incorrectly decoded due to the offset this causes.
Data capture begins in the middle of a Serial Message
By deleting the portions of your data that might be causing this issue (most commonly the beginning of data captures being located right in the middle of a data message), this issue will most likely be solved.
We're looking into ways to improve the behavior of our analyzers with respect to detecting these conditions and correcting for it automatically.
If you have any feedback, feel free to let us know below!
Previous
CSV Export is Slow
Next
Logic 2 is Consuming Disk Space
Last modified 6mo ago
Copy link
Edit on GitHub
Contents
Why Would I Need to Do This?