Getting Started with a Logic Analyzer: Wiring, Capture and Decoding

Before installing software, identify the exact analyzer model, hardware revision, operating system and CPU architecture. Check the manufacturer or application support list. PulseView support is device-specific; a similar-looking enclosure or USB connector does not establish compatibility. Driver installation and acquisition modes also vary.

Start with a development board producing a documented test sequence. Verify the analyzer input limits and logic threshold range. Connect the circuit reference and one signal first, keeping leads short. Avoid mains, high-energy circuits and unknown voltages. A USB connection can join the circuit ground to your computer and other earthed equipment.

Choose a supported sample rate and capture length, then record a repeatable signal with an immediate capture. Inspect transitions before adding a decoder. If the trace is flat, verify pin numbering, firmware output and trigger state. If it is noisy, check contact, grounding and threshold compatibility. The maximum rate printed on the product page may depend on the number of active channels and acquisition mode. Use the current application documentation to establish what is available in your configuration.

For SPI, assign clock, chip select, MOSI and MISO as needed. Match clock polarity, clock phase, bit order and word size to the peripheral datasheet. Known expected bytes make a better first exercise than an unknown failing circuit. For I2C, assign SDA and SCL, then inspect address, acknowledgment and stop conditions. Check whether the application displays a seven-bit address or the address byte including the read/write bit. A decoder cannot confirm analog voltage margin; use a scope if electrical behavior is in doubt.

Once an immediate capture works, add a simple edge trigger. Confirm whether your device supports pre-trigger data and how it allocates memory. Advanced protocol triggers are not universal. Reproduce the event after acquisition is armed. Save the original capture with sample rate, channel mapping, trigger settings, board firmware and expected transaction. Keep a known-good reference from the same setup. That makes future comparisons meaningful and prevents a changed decoder setting from masquerading as a new circuit fault.

This is an instructional example, not a personal lab report. No captured waveform, measured repair result or product ownership is claimed. Exact logic-analyzer sample modes, thresholds, input limits and application support must be checked for the chosen hardware, operating system and software build. A successful protocol decode does not prove electrical compliance.

Use the [sigrok supported-hardware list](https://sigrok.org/wiki/Supported_hardware), [PulseView documentation](https://sigrok.org/wiki/PulseView), and the [Saleae Logic documentation](https://support.saleae.com/) for application-specific instructions. For a USB oscilloscope, consult the exact [Hantek 6022BE model and downloads](https://www.hantek.com/products/detail/31) or manufacturer manual. Generic USB connectivity is not a guarantee of operating-system or decoder compatibility.