Skip to main content
Use a logic analyzer to check what actually crossed the pins: bus traffic, timing between edges, and handshakes between chips. Tell Embedder the channels, protocol settings, capture length, and the event you expect. The capture opens in the Monitor’s Logic tab.

Choose an instrument

Saleae Logic

Timed or manual captures through Logic 2, Logic 2’s own decoders, and .sal files.

Digilent WaveForms

Digital capture with edge, level, or external triggers, plus analog inputs, waveform outputs, and supplies.

DSLogic

Buffer, streaming, and repeated captures, multi-stage triggers, and saved-capture analysis in the Monitor.

PicoScope MSO

Fixed-duration digital captures with pattern triggers on a model with a digital pod.
All four capture from the Monitor’s Logic tab, when you ask Embedder, or from a hardware script. They differ in what they capture, decode, and need installed: Channels, thresholds, and sample rates depend on the model and, for some analyzers, the USB connection. Ask Embedder to check the connected device before you plan a capture. A DSLogic can also capture on another machine through a remote bridge.

Set up the analyzer

Follow the setup for your instrument: If more than one logic analyzer is connected, say which one to use. In a hardware script, set logic_provider in the capture profile to saleae, dslogic, digilent, or picoscope.

Capture a bus

  1. Connect the analyzer’s ground to the target’s ground, then connect the signal inputs.
  2. Check that the signal voltage is within the analyzer’s input limits.
  3. Tell Embedder the channel assignments, logic voltage, expected bus rate, and capture length.
  4. Add a trigger when the capture must start at a particular event. Use one your instrument supports.
  5. Run the capture, then check the sample rate and duration Embedder reports.
Sample at least four times the fastest bus clock so edges land where you expect them. Use the reported rate, not the requested one, when you calculate timing. To capture without asking Embedder, select + in the Monitor and open Logic Analyzer under Views. Choose the analyzer from the device chip at the start of the toolbar. Next to it, the Logic setup chip shows a summary of the current settings; select it to set up the capture. Then select Single or Run. From the Monitor, Saleae, Digilent, and PicoScope captures start immediately or on one edge. For their other triggers, ask Embedder or use a script. A DSLogic offers all of its trigger types in the Monitor. For the full steps, see the guide for Saleae, Digilent, PicoScope, or DSLogic.

Decode and inspect

Give Embedder the channel roles and protocol settings for each bus: Each analyzer has its own decoder list and options. See Saleae, Digilent, or DSLogic. PicoScope digital captures aren’t decoded; export the raw transitions instead. Keep the raw signals next to the decoded rows. If decoded bytes look wrong, the raw edges show whether the problem is in the wiring, the decoder settings, or the firmware. Saleae, Digilent, and DSLogic decode CAN frames. To turn frames into named application signals with your project’s database, use CAN Monitor. Use the controls above the waveform, or click the waveform and use the keyboard: To jump to exact positions, choose Go to sample range… from the View actions menu, or drag the Overview bar.

Save and compare

  1. Save the capture in the instrument’s own format, where it has one, plus raw and decoded CSV exports.
  2. Record the firmware revision, channel map, trigger, and reported sample rate with the result.
  3. Repeat the same capture after a change and compare the two.
Embedder keeps captures in your project under .embedder/captures/. In the Logic tab, select Capture history to reopen earlier captures, grouped by chat session. You don’t need the analyzer connected to reopen one. A logic analyzer shows when a signal crosses a threshold, not its voltage. Use an oscilloscope to check rise time, ringing, or voltage levels.

Troubleshoot

  • Decoded bytes are wrong: check the channel numbering first. Embedder counts channels from 0, even when the analyzer’s housing labels start at 1. Then check baud rate, framing, SPI mode, and bit order before you change firmware.
  • Edges are missing or timing is uneven: raise the sample rate or reduce the number of enabled channels.
  • Embedder reports several analyzers: name the one to use, or set logic_provider in the capture profile.
For connection, threshold, or capture-mode errors, see the troubleshooting for Saleae, Digilent, DSLogic, or PicoScope.
Last modified on November 13, 2026