Saleae Support
HomeDownloadUser ForumContact Us
  • Saleae Support
  • Orders & Shipping
    • Place an Online Order
    • Place a Purchase Order (PO)
    • Get a Quote
    • Check your Order Status
    • Distributors
    • Pricing and Availability
    • Discounts
    • Tax & VAT Exemption
    • Saleae Business Information
    • Shipping Policy
    • Receiving Invoices
    • Sales FAQ
      • What Is Included with the Product?
      • What Accessories Should I Purchase with My Device?
      • Is the Saleae Software Sold Separately?
      • Does Saleae Have a Trade-In or Upgrade Plan?
      • How Can I Find the Current Status of My Order?
      • Part Numbers, ECCN, HS Codes, and Country of Origin
      • Discontinued Products
      • International Customs and Duty Information
      • Does Saleae Offer Demo Units or Units on Loan?
      • When Is My Card Charged?
      • Unable to Ship to PO Box Error
      • Referred a Friend? Email Us!
      • Does Saleae Provide Drop-Shipping Service?
  • Getting Started
    • Setup
    • Configure
    • Record
    • Navigate
    • Measure
    • Trigger
    • Protocols
  • User Guide
    • Product Summary
    • Safety & Warranty
    • Supported Voltages
    • Device Calibration
    • Using Logic
      • Navigating the Software
      • Connecting the Logic Analyzer
      • Logic Accessories
      • Device Settings
      • Capture Modes
      • Navigating Your Data
      • Time Bar Settings
      • Measurements, Timing Markers & Notes
      • Capture & Preset File Management
      • Exporting Data
      • Delete Part of your Capture
      • Analyzers
      • Data Table & Terminal View
      • Color Themes
      • Demo Mode
      • Software Glitch Filter
      • Keyboard Shortcuts
      • Automatic Updates
      • Message Us Directly
  • Software
    • Supported Operating Systems
    • Download
    • Installation
    • Firmware Updates
    • Driver Install
    • Legacy Software
      • Logic 1.x Download (Deprecated)
      • Logic 1.x Installation (Deprecated)
      • Logic 1.x Changelog (Deprecated)
      • Logic 1.x User Guide (Deprecated)
  • Protocol Analyzers
    • Supported Protocols
    • Analyzer User Guides
      • Async Serial Analyzer - User Guide
        • Decode UART
        • Decode RS-232, RS-485, & RS-422
      • SPI Analyzer - User Guide
      • I2C Analyzer - User Guide
      • CAN Analyzer - User Guide
      • Simple Parallel Analyzer - User Guide
      • I2S / PCM Analyzer - User Guide
      • DMX-512 Analyzer - User Guide
      • SMBus Analyzer - User Guide
      • Decode Differential and High Voltage Data
  • Software Extensions
    • Extension Installation
    • Create and Use Extensions
    • High-Level Analyzer (HLA) Extensions
      • Shared High Level Analyzers (HLAs)
    • Measurement Extensions
      • Analog Measurement Extensions
      • Digital Measurement Extensions
    • Extension File Format
    • About Third-Party Extensions
    • Disabling Marketplace Extensions
    • Publish an Extension
    • HLA - Analyzer Frame Format
      • Async Serial - Frame Format
      • I2C - Frame Format
      • SPI - Frame Format
      • CAN - Frame Format
      • Manchester - Frame Format
      • 1-Wire - Frame Format
      • Async RGB LED - Frame Format
      • Simple Parallel - Frame Format
      • LIN - Frame Format
      • I2S - Frame Format
    • API Documentation
  • Automation & Analyzer SDK
    • Automation API - Logic 2
    • Automation API - Legacy Logic 1.x
    • Protocol Analyzer SDK
      • FrameV2 / HLA Support - Analyzer SDK
      • Rename a Custom Analyzer
    • More Information on our SDKs
      • Can I Access Raw Data in Real Time?
      • Migrate Code to the New Analyzer SDK
      • Sharing Custom Low-Level Analyzer (LLA) Code
      • VB.NET Support for Automation
  • Datasheets & Specifications
    • Datasheets
    • Logic Hardware Revisions
    • Logic Dimensions
    • Compliance Documents
  • 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
    • Location of Your Config File
    • 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 device was found, but the software was unable to access 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 and Other GPU Issues
    • 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
    • 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%
    • This Analyzer's Native Export is Not Supported in Logic 2
    • Mouse Scrolling Issues
    • Error: A device was found, but it was removed before initialization completed
    • Error: An unknown error occurred during device connection
    • Visual Studio Error: Failed to Launch Debug Adapter
    • VS Code Fails to Launch Python Automation API Script
    • Analog Waveforms Do Not Appear on Linux
    • Reinstall USB Host Controller Drivers
  • FAQ
    • Technical FAQ
      • System Requirements for Saleae Products
      • What Is the Normal Behavior of the LED?
      • What Is the Difference between Logic/Logic16 (Gen1) and Logic 8/Pro 8/Pro 16 (Gen2)?
      • Recommended USB 3.0 Host Controller Cards
      • Device Settings Configuration Tips
      • What Is the Worst Case Channel to Channel Skew?
      • What is Asynchronous Sampling?
      • Which Saleae Products Can Decode 4-Bit Parallel LCD Communications?
      • How Can I Compare Two Clock Signals for Synchronization and Drift?
      • Converting I2S/PCM Captures into Audio
      • My Capture Shows an Uneven Duty Cycle
      • Can I Create or Edit .logicdata Files?
      • Can Saleae Logic Run on ARM / Apple Processors?
      • What Annotations Are Supported?
      • Time & Memory Saving Tools
      • How Can I Record Power Consumption?
      • Moving Logic to Its Own Host Controller
      • How Long Does It Take to Save a File?
      • XMonad on Linux Causes Issues
      • What Is the Maximum Bandwidth of Logic?
      • How Long Can I Record Data?
      • Can I Export Protocol Results Between Timing Markers?
      • Can I Generate an Analog Graph from Digital Data?
      • Time Measurement Error
      • Can These Products Replace an Oscilloscope?
      • Can I Use Multiple Logics on a Single PC?
      • Native Windowing Features Are Not Working Such as Snap or Gestures
      • Opening .logicdata Capture Files
      • How to Choose the Right Logic Analyzer for You
      • Saleae Open Source Support
      • How to Trigger the End of a Capture Instead of the Start
      • Using the Hardware with USB Extension Cables, Through Virtual Machines, or Ethernet Extenders
      • Are the Ground Pins Required for Each Input Used?
      • Can Saleae Products Output Data?
      • Resolution of the Analog Inputs
      • What Sampling Rate Should I Use?
      • Can I Share Data Captures with Others?
      • Binary Export Format (Digital) - Logic 1.x
      • MATLAB Data Export Format - Legacy Logic 1.x
      • Recording Multiple Protocols at the Same Time
      • Changing the Display Radix (Base)
      • Which Logic Analyzer Should I Get?
      • How to View and Debug Firmware Variables, State, and Function Calls
      • Using Saleae Logic Devices with Third-Party Pattern Generators
      • Can Logic Operate with a Full-Speed USB Isolator?
      • Which Saleae Devices Support Analog Recording?
      • How to Manage Protocol Analyzers when Using the Socket API
      • How to Export Serial Protocol Results to a Raw Binary File
      • How to Trigger On a Pulse with No Maximum Time Limit - Logic 1.x
      • Finding Your USB 3.0 Host Controller Information
      • Logic Reports Different USB Current Requirements
      • Is It Possible to Adjust the Logic Thresholds for the Digital Inputs?
      • Why Does Channel 0 Use a Black Wire?
      • Software Shows Multiple Logic Analyzers Attached
      • Are the Input Channels Isolated from Each Other?
      • Are There Feature Differences in the Software when Different Logic Analyzers Are Used?
      • Packet Level Decoding Support in the Analyzer SDK
      • What Higher-Level Protocol Analysis Features Are Available?
      • Support for USB 3.0 and USB 3.1
      • How Can I Compare Signals from Different Captures?
      • Do the Saleae Logic Analyzers Support Trigger Out?
      • Why is the Length of my Capture Incorrect?
      • The Options Button is Missing
      • Can I Change the Voltage Range of the Analog Inputs?
      • How Does the ASCII Radix Display Characters?
      • Do I Have a USB 3.0 Port?
      • What Is the Best Way to Compare Similar Sequences of Protocol Data?
      • Which Version of the Software Should I Use?
      • Import Custom Low Level Analyzer
      • OSX Analyzer SDK Xcode Setup
      • Can Custom Analyzers Process Analog Channels?
      • Automating Long Overnight Captures
      • What Options Are There to Export Multiple Protocol Analyzer Results into the Same File?
      • Do the Saleae Devices Support AC Coupling?
      • Suggestions for Capturing Multiple Instances of a Triggered Event Automatically
      • How Many Protocol Analyzers Can Be Used at Once?
      • Is It Possible to Run the Saleae Software on a PC without SSE2 Instructions?
      • Is It Possible to Import Data into the Logic Software?
      • How Do I Convert Exported CSV Analog Data in Voltages?
      • Is There Cross-Platform Support for the SaleaeSocketApi C# Project
      • Why Does Logic Get Warm?
      • Binary Export Format (Analog) - Logic 1.x
      • Electrical Isolation Suggestions
      • FCC and CE Testing Recommendations
      • 'Save Capture' and 'Export Data' is Disabled in the Software
      • File Format Description for Exporting Protocol Analyzer Results
      • Is There a Newer Version of the Software Available?
      • Is There a Way to Change the Window Resolution?
      • How Can I Extract Recorded Data Using Socket API?
      • Does the Software Support Windows 10 Tablets or Windows RT Tablets?
      • Standalone Software Information
      • Does the Saleae Software Support the Original Logic and Logic 16?
      • Timing Markers Disappear When I Start a New Capture
      • What Sample Rate Settings Are Available? Can I Sample at a Slower Rate?
      • How Do I Differentiate Data in the Export File when Duplicate Analyzers Are Used?
      • Running Multiple Versions of the Software
      • Test Clip Differences - Gen 1 & Gen 2
      • USB-C Cable Recommendations
      • Is My Capture Data Private?
      • Ethernet Connectivity Suggestions
      • Binary Export Format - Logic 2
      • Viewing I2C Addresses as 8-bit
      • Can I use Python Packages in my Custom Extension?
      • Are the Inputs Synchronously Sampled or Sweep Sampled?
      • Is Logic Affected by the Log4j Exploit?
      • Connecting Remotely with SSH
      • Is Silent Installation Supported?
      • Is the .sal File Format Documented?
      • Export Data via Socket API
      • Running Logic in a CI Environment on Windows with the SYSTEM Account
    • General FAQ
      • How Do I Get More Help on an Issue That's Outside the Scope of Saleae Support?
      • How to Identify Each Saleae Device
      • License for the Saleae Logic Software, SDKs, and APIs
      • How Do You Pronounce Saleae?
      • How to Create Project Content for Saleae
  • Returns & Warranty
    • Submit a Warranty Claim
  • Community
    • Ideas & Feedback
    • User Forum
    • Community Projects
    • Community Created Accessories
    • Community Shared Analyzers
  • Tutorials
    • Oscilloscope Tutorial
    • Logic Analyzer Tutorial
    • Learning Portal
      • Digital Protocols
        • Learn Asynchronous Serial
        • Learn I2C - Inter-Integrated Circuit
        • Learn SPI - Serial Peripheral Interface
        • Learn CAN – Controller Area Network
        • Digital MultipleX (DMX512)
        • Manchester
        • 1-Wire
        • Learn I2S / PCM
        • Management Data Input/Output (MDIO)
        • BiSS C
        • HDMI Consumer Electronics Control (CEC)
        • PS/2 Keyboard/Mouse
        • Universal Serial Bus (USB) 2.0
        • Single-Wire Interface (SWI)
        • Simple Parallel
        • Local Interconnect Network (LIN)
        • Joint Test Action Group (JTAG)
      • Common Acronyms and Definitions
      • What is a Glitch?
      • What is RAM? Why Does Logic Use it?
      • What is a Display Radix?
      • What is Data Bandwidth? Can I Reduce this in Logic?
    • Example Projects
      • STM32 Nucleo Board - Digital Signals
      • STM32 Nucleo Board - Analog Signals
      • STM32 Nucleo Board - Analyzing UART
      • STM32 Nucleo Board - Analyzing SPI
      • STM32 Nucleo Board - Analyzing I2C
Powered by GitBook
On this page
  • The Capture Fails with an Error Message
  • The Captured Data is Corrupted
  • The Analog Capture Looks Extremely Noisy
Edit on GitHub
Export as PDF
  1. Troubleshooting

The Captured Data Looks Incorrect

PreviousError Message: ReadTimeoutNextThe Captured Data is Corrupted

Last updated 3 years ago

Before troubleshooting any further, please make sure you are using the .

Below is a list of all known reasons and corresponding solutions or next steps that can cause this particular issue. Please check each one, skipping any items that are not relevant (such as issues specific to an operating system you are not using).

For each item, first perform the test. If the test result is positive (the test condition was met), then attempt the corrective action.

The Capture Fails with an Error Message

If the issue you are experiencing is that some or all of your capture attempts immediately fail with the error message shown in the link below, please read the below article.

The Captured Data is Corrupted

If the software is able to capture data, but the captured data looks random or completely incorrect:

  1. Make sure the software detects the Logic hardware properly (the top bar of the software should display "Connected").

  2. Check your USB Host Controller driver. There is a known issue with VIA USB host controllers. See below.

The Analog Capture Looks Extremely Noisy

Even with the Logic hardware inputs disconnected, the analog capture may look like the image below. The solution is to simply download the . We made some incremental changes to the Logic hardware (no new functionality) that makes it incompatible with Logic software versions prior to 1.2.15.

Check the Ground Connection

Please verify the following:

  • At least one ground pin from the logic analyzer is connected to the ground on your device under test.

  • Verify that the wire you are using is the ground wire from the logic analyzer. On the new units, the ground wire is black with black heat-shrink and no label. On the older units, the ground wire is grey and has a white label with "ground" printed on it.

Check to See If the Device Records Correctly when No Signals Are Connected

  • Test: Remove the wire harness(es) from the front of the device so all inputs are floating and no grounds are connected. Perform a short capture using all channels at any sample rate.

    If you are using the original Logic (8 channel, digital only), then all signals should be high during the duration of the capture.

    If you are using any of the other devices (Logic16, Logic 4, Logic 8, Logic Pro 8, or Logic Pro 16), all inputs should be low.

    All analog channels should be approximately 0 volts, +/- 0.02 volts. If any of the signals are off by as much as 0.2 volts, that could mean a calibration problem. If any analog signal is off by more than 0.2 volts, it could indicate device failure.

Perform a Basic Channel Functional Test

  • Test: If you are using a Logic16, Logic 4, Logic 8, Logic Pro 8, or Logic Pro 16, you will need a voltage source, preferably between 3.3 volts and 5.0 volts.

    If you are using the original Logic (8 channels, digital only), you do not need a voltage source.

    Set up a capture on all channels (digital and analog) and set the recording time for 15–30 seconds. Make sure to set the analog sample rate to a low setting, preferably 1 kSPS. Any digital sample rate is acceptable.

    Start a capture. During the capture, take each input, one at a time, starting with input 0 and going in order to the last input, and short that input to the voltage source (or a ground pin in the case of the original Logic).

    You can end the capture early if you finish before the capture completes. If you are unable to finish testing all the channels within the capture time, either repeat the process faster or extend the capture time.

    In the capture, verify that each channel is initially low (high in the case of the original Logic.) Verify that only one channel goes high at a time and that the channels go high in order from 0 to the last channel. Make sure that none of the high pulses are out of order, such as channel 2 going high before channel 1. Note that since the original Logic's inputs are pulled up internally and the test is performed with ground, the pulses in question should be low and not high. If the device used has analog channels, make sure the analog channels display the same behavior.

Verify That the Load Impedance of the Logic Analyzer Will Not Interfere with Your Circuit

  • Test: Most Saleae devices have an input impedance of 1 Meg ohm in parallel with 10 pF. If your circuit has a very high output impedance, the logic analyzer may cause issues with the operation of your circuit.

  • Corrective Action: Either buffer the signals you need to record with an even higher input impedance buffer or find another method of recording the signals.

Check for Ground Loops or Common Mode Ground Voltage Problems

  • Test: Check to see how your device under test is powered, and check to see how the host PC is powered. Then check for other devices connecting from the host PC to the device under test.

    None of the Saleae devices are electrically isolated. That means that the ground pins on the Saleae device are connected to the USB ground. When you connect the logic analyzer to the device, you will effectively connect the device's ground to the PC's ground. If your device and PC are powered from AC main power, they will probably already be common grounded. In this scenario, if the ground pin from the logic analyzer is connected to any voltage other than ground on your device, ground current will occur and can potentially damage your device under test, the Logic analyzer, or the host PC, or harm the user.

  • Corrective Action: Avoid ground loops. If this is not possible, use extra care to ensure that the ground pin from the Logic analyzer is only connected to the same ground reference on your device under test.

Test for an Internal Enclosure Short Defect

  • Test: Disconnect the logic analyzer from the PC and the device under test. Measure the resistance from each input pin to the metal enclosure.

    The anodized areas of the enclosure are not conductive. The logo on the bottom of the product is laser etched and conductive. Probe against this logo to test for resistance.

    The large logo badge on the top is not electrically connected to the case. Be sure to use the laser etched logo on the bottom.

    The original Logic and Logic 16 are not subject to this issue.

  • Corrective Action: Contact Saleae support right away. Provide the measured resistance between each input pin (and optionally ground pin) to the metal enclosure. Also, include a phone number and shipping address.

    If any input pin has a noticeably low resistance to the metal case, that could indicate a short inside the case due to a manufacturing tolerance issue in the metal case.

Check for Cross Talk

  • Test: Are you seeing short pulses in your capture that you do not expect to be there? Are these pulses lined up in time with transitions on one or more other channels?

    Cross talk occurs when changes in one signal are electrically coupled to another signal. That can cause glitches (narrow pulses) to appear in neighboring channels with the source channel (aggressor).

  • Corrective Action: Physically separate the flying lead probes in the wire harness between the logic analyzer and your device.

    If you are not using all the inputs on the logic analyzer, consider moving the used channels further away. For instance, instead of using channels 0, 1, and 2, use channels 0, 2, and 4.

    If the Logic analyzer model you are using supports multiple voltage thresholds, make sure you have the most applicable threshold option selected.

Verify That the IO Voltages Used Are Compatible with the Logic Analyzer

  • Test: First, check the supported IO standards for the Logic analyzer that you are using below.

  • Verify that the logic high voltage is above the logic high threshold, and make sure that the logic low voltage (usually 0 volts) is below the logic low threshold voltage of the device.

  • Some of the Saleae devices have selectable IO thresholds. First, try the IO threshold that best matches your application, but if it does not appear correct, also try other threshold settings.

  • Corrective Action: You may need to level shift your signal before it reaches the logic analyzer or provide additional over-voltage protection. In the case of the original Logic, you should not connect RS-232 signals directly to the device.

Verify That the Bandwidth of Your Sample Rate Is Fast Enough to Properly Capture Your Signal

If your digital capture looks correct but the analog capture does not, please see this article:

See this article for more information about the maximum digital and analog bandwidth for each device:

For more information about the bandwidth requirements for any given signal, please see this article:

Corrective Action: about a warranty repair or replacement.

Corrective Action: Any issues in the recorded capture could indicate damaged input buffers, shorted channels, or other problems. If any results found are unexpected, please about a warranty repair or replacement.

If you are unable to avoid common mode ground voltage or require isolation, please consider this digital isolation evaluation kit:

Contact support
contact support
http://www.digikey.com/product-detail/en/SI84XXISO-KIT/336-1765-ND/2170672
Supported Voltages
The Digital and Analog Recording on the Same Channel Appear Different
What Is the Maximum Bandwidth of Logic?
What Sampling Rate Should I Use?
latest version of Logic software
Error Message: ReadTimeout
The Captured Data is Corrupted
latest version of Logic software