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
Known Issues on OS X
While testing these issues during the development between 1.2.3 and 1.2.5, we noticed that some of these issues dissipated after updating to OS X 10.10.5 and 10.11. The software release 1.2.5 also goes a long way to improve the reliability of the new products. The OS X update had the biggest impact on the original Logic's maximum sample rate, allowing us to reliably capture for more than 10 seconds on the original Logic at 24 MSPS. Some captures for 60 seconds did fail early, but most completed, which is the expected performance.
We've recently noticed a spike in crashes or sampling errors on our OSX software, which we are working on fixing now.
  1. 1.
    Occasional crashes with the new products when pressing "Start," usually after a number of previous captures.
    Usually, after one or more successful capture, the user might see an error when starting a capture that states there was an error issuing the Start command, queuing the read requests, or configuring the device.
    The very next capture after that error crashes the software.
    After restarting the software, the software asks you to reconnect the device.
    That is caused by a communication synchronization issue. It looks like an edge case that actually affects other platforms and host controllers as well but appears most frequently on OSX over USB 3.0.
    We are working on a software and firmware update right now that will eliminate this problem. It will be released in the next update.
  2. 2.
    Crashes when connecting the original Logic to the software on OS X.
    We've recently seen a new crash in our USB connection code on a number of OS X computers. This crash is platform-specific and will not appear on other platforms.
    We suspect an update to OS X has caused one of the IOKit USB functions we call during the connection process to return an error, which our software does not currently handle.
    We will fix this by handling the returned error properly in the next release.
  3. 3.
    The original Logic cannot keep up reliably at 24 MSPS on recent Apple hardware.
    After testing on the same hardware under windows, it appears that the issue is either software- or driver-related. We are investigating if we can restore the maximum sample rate with a software update now.
Previous
Missing Files: api-ms-win-crt-runtime-l1-1-0.dll or msvcp140.dll
Next
A Measurement Appears Incorrect
Last modified 6mo ago
Copy link
Edit on GitHub