Capability 04 / 05

Uses your scope, logic analyzer and power profiler.

The agents connect to the instruments on your bench, set them up, capture and decode signals and read the true state of the hardware: voltages, timing and current.

J1U1STM32F407U2LSM6DSOY1C1C2TP1TP2R1D1J2IMU NODE · REV ASCOPE · CH1 · TP1 SCK10.5 MHzovershoot 0.2 VLOGIC · SPI DECODEWHO_AM_I 0x6CCSSCKMOSIMISOPOWER · J2sleep 2.1 µA · peak 12.4 mAMEASUREMENTSSCK 10.5 MHzrise 3.1 nsovershoot 0.2 VWHO_AM_I 0x6Cactive 12.4 mAsleep 2.1 µAsaved as evidence
enlab — instruments · bench

›

Illustrative session

See it run

Measured, not guessed.

The agents set the scope’s trigger, decode the SPI bus on the logic analyzer and capture active and sleep current, then save every capture as evidence.

Why it matters

Code can lie. Signals do not.

Most AI tools stop at the compiler and guess what the hardware does.

EnLab measures it: every conclusion rests on a real capture you can open and check.

What it does

Drives your instruments, with EnLab IDE.

  • Oscilloscope

    Probes set up, triggers placed, and edges, levels and timing measured.

  • Logic analyzer

    SPI, I2C, UART and CAN captured and decoded.

  • Power profiler

    Active and sleep current measured on the real board.

  • Evidence kept

    Every capture is time-stamped and saved with the session.

Questions

Asked a lot.

Which instruments does it work with?
Oscilloscopes, logic analyzers, power profilers, serial consoles and CAN interfaces on your bench.
Does it set up the instruments itself?
Yes. It configures channels and triggers, then captures and decodes on its own.
Can I see the raw captures?
Yes. Every capture is saved as evidence you can open.
How do I try it?
Request access for EnLab IDE.

Bring up your next board with EnLab IDE.

Request access for EnLab IDE