The main changes to BenchPod. Something missing or broken? Tell us.
Docs grouped by topic
Web app
The docs menu now groups the pages by topic: Get started, The pod, Your board, Use the bench, Tests, CLI and MCP, Cloud and CI, Help, and PCB checks. The group of the page you read is open and highlighted, and a click opens any other group. On a phone the menu opens at the page you are on. Every page keeps its address, and the two EMI Analyzer guides are now in the menu too.
Wiring profiles live on the pod, and nothing is wired by default
Firmware
Web app
SDK and CLI
AI agent
Desktop app
A pod now keeps up to 16 named wiring profiles itself, one of them the default, so the web app, BenchPod Desktop, the CLI, the SDK and an AI agent all see the same ones over the LAN, USB and the cloud. Saving is always something you do, and it never changes the default. Nothing is wired until you say so: a pin that is not in the profile stays unconnected, and a call that needs it says what to pass. The pins the pod used to assume are the embeddedci-reference preset. Turning the board on shows the profile it uses and sets that profile's I/O voltage first, and the Wiring dialog shows the profiles with a diagram of the wiring. Needs pod firmware 3.10.8 with SDK and MCP 3.0.0, CLI 0.9.0 or BenchPod Desktop 0.1.9; scripts that relied on the old default pins need one change, described in the upgrade guide.
When the pod refuses a command it now sends a stable code, such as BP0009, with the values that go with it. Every code is explained on the error codes page, with the fix. In the SDK it is exc.code, benchpod explain BP0009 prints the explanation, and the MCP gives an AI agent the fix to try. Match the code in your scripts, not the message text, which can change. Needs pod firmware 3.10.8.
The UART console and UART captures take even or odd parity and 2 stop bits, for devices that are not 8N1, such as 8E1 or 8N2, and a wrong parity bit is flagged. The pod's pins are 1.8 or 3.3 V: a 5 V serial device needs a level shifter, and Modbus RTU over RS-485 needs a 3.3 V RS-485 transceiver between the pod and the bus. In the web terminal, and in the SDK and MCP 3.0.0, with pod firmware 3.10.8.
The pod's MAC addresses, for networks that register devices
Firmware
Web app
SDK and CLI
Some networks give an address only to a device whose MAC is registered first. The pod's Ethernet and Wi-Fi MAC addresses are now in its status, in benchpod status and benchpod discover, in bp.mac_addresses() and on the pod's page in the web app. A pod that never joined a Wi-Fi network learns its Wi-Fi MAC from a Wi-Fi scan. Needs pod firmware 3.10.8.
Flash ESP32 boards, and Wi-Fi updates go straight into the Wi-Fi chip
Firmware
SDK and CLI
The pod can flash ESP32-family boards through their own UART bootloader, with no esptool and no USB cable to the board: wire its serial pins, its boot pin and EN, then run benchpod flash --target esp32 or flash(target="esp32", ...). adc_read now reads to the microvolt. Updates for the pod's own Wi-Fi are written straight into its Wi-Fi chip in about 2 minutes, and updates over Ethernet or Wi-Fi need a signed image, which every published release has. Needs pod firmware 3.10.7, CLI 0.8.11 and SDK 2.13.20.
Pre-trigger on the web, a quicker confirmation, and an I2C tab that remembers
Web app
A triggered logic capture on the Capture tab keeps 10 % of the capture from before the trigger (choose 0 to 50 %), and the trigger is marked on its lane, so a UART decode gets its first byte. The confirmation dialog shows at once. In the Drive tab, "Switch them on and open" asks once, the pull-up hint says whether they are on, and an I2C session stays shown as open when you come back to the tab.
Closing CAN switches the termination off
Firmware
SDK and CLI
Desktop app
Closing CAN now also switches the 120 ohm termination off. When another app or script holds the pod’s I2C master, the SDK says so instead of pointing at your script. BenchPod Desktop 0.1.7 brings the bus console fixes: CAN IDs in hex, fewer and clearer confirmations, the pull-ups offered when I2C needs them, pytest exports that switch them off again, a pre-trigger in captures and a dark waveform view. Needs pod firmware 3.10.6 or SDK and MCP 2.13.16.
Capture triggers, a console that waits for the AI HIL tab, and asks before power and outputs
Web app
The Capture tab can wait for an edge or level on any LA pin before it records, so it catches a UART reply or an I2C START over the cloud too. Switching LA + ADC to LA keeps the last capture. The workspace asks before it turns target power on or off, starts a DAC output or an emulated sensor, as the Drive tab and the desktop app do, and stopping the last emulated sensor puts the pod back on its control-loop image. Your own AI HIL agent and Drive tab no longer lock your page out of your pod, and others see them as your web workspace. On the AI HIL tab the DUT console pauses, keeping its screen, and connects again when you leave. An I2C session left open in the Drive tab keeps working after a long pause. On a phone all four tabs fit and a reload opens the page, not the pane. In the Drive tab, plain reads and scans of an open bus no longer ask while writes still do, the confirmation shows addresses in hex and every byte, each pod keeps its own log, and a pin warning no longer moves the tabs. Pod settings says whether the firmware is a signed release.
The Drive tab lets go of the pod after an I2C scan
Web app
AI agent
An I2C master opened in the Drive tab no longer keeps your pod: it is let go a few seconds after the last call and opens again with the next one, so the CLI, SDK and CI on the same pod wait seconds, not most of a minute. While the Drive tab or the AI HIL agent holds the pod, a LAN client that is turned away now sees at most 20 seconds left, renewed while the tab is in use, instead of two minutes.
Drive tab fixes: the pod is free sooner, narrow windows, clearer charts
Web app
The Drive tab and the AI HIL agent now let go of your pod a few seconds after the last call (or when you close the page), so the CLI, CI and your team can use it right away; an open UART, CAN or I2C session keeps it until you close it. A call the server could not take is tried once more, and a failed call shows its own error in the tab. On windows around 800 px wide the board pane gives the task room, and the log puts each call on its own lines with the bytes kept whole. Analog axes near 0 V read in millivolts. Every field in the Drive tab is named for screen readers.
A clearer pod page: your task on the left, your board on the right
Web app
A pod’s page now has four tabs for what you are doing: AI HIL, Capture, Drive (the bus console) and Simulate (emulated sensors, and on the analog board the signal generator). Your board sits in a pane on the right, the same on every tab: the serial console, the pins in plain words with the wiring under them, power and flashing. On AI HIL the pane also shows the agent’s console and captures. Drag the pane wider, or hide it to a slim rail. Pod settings open from the gear in the header. Old links still land in the right place.
Saved sequences in the bus console
Web app
Desktop app
Tick rows in the bus console’s log and save them as a named sequence: run it again with one click (each step asks the same confirmations as by hand, and a read that returns something new is flagged), or export it as a pytest file for the SDK, with an assert per read. Sequences are yours; share one and your organization can run and export it. In the desktop app they are kept on your computer, and sharing needs an EmbeddedCI API key.
A new Drive tab with the bus console, the same as in the desktop app: the pod as I2C master (send, read, scan) and GPIO, and one log of every transaction. Calls that drive your board ask first. Needs pod firmware 3.10.4 or later for the I2C master.
A capture of an emulated I2C sensor now waits for your firmware’s next transaction (up to 2 s by default) instead of recording whatever the bus does at that moment, so one call holds a complete read. If your firmware never touches the bus, you get a clear timeout. After you stop the I2C, SPI and UART sensors, the web Generator’s control loop and full-length replay work again: it switches the pod back from the emulation image by itself. Needs pod firmware 3.10.4 and SDK 2.13.12 or later.
The pod is now an I2C master on any two LA pins at 100 kHz, 400 kHz or 1 MHz: read and write a chip’s registers or scan the bus from pytest, the CLI or the agent. SPI runs in all four modes. A logic capture can send one I2C, SPI or GPIO transaction right after it arms, so you see your own traffic on the wire. Tell the pod which pins your board drives, and it refuses to drive against them. Needs pod firmware 3.10.4, SDK 2.13.13 and CLI 0.8.9 or later.
If the activation code for your BenchPod account expired or stopped working, click "Email me a new code" on the activation page. A new code is on its way in a minute. If your account is already activated, that email holds a link to reset your password instead.
Define your own sensors
Web app
Firmware
The Simulate tab plays any I2C, SPI, UART or analog sensor you describe in a short YAML file. Start from the sensor library, see what your firmware will read as you type, change readings live, inject faults and script values over time. Needs pod firmware 3.10.3 or later.
BenchPod Desktop 0.1.3 adds the pod’s own settings: Wi-Fi, network access, HTTPS-only, the USB network adapter and the signature policy. It also stores the pod’s calibration from your multimeter and programs SPI flash chips on four LA pins.
BenchPod Desktop now has bench controls beside the agent: the board’s console, logic and analog captures with zoom and protocol decoding, the signal generator with a waveform library on your computer, flashing your board from a file, the wiring and power. It finds your pod over USB or your network on first start, needs no account, and runs without a model if you only want the controls. It can also update the pod’s own firmware, even with no internet.
Ask for more than 12 MS/s and the pod records only the moments a channel changes, at 48, 24 or 16 MS/s. The capture call stays the same and you get the usual samples back. A triggered capture can also keep what happened just before the trigger.
The BenchPod page opens the workspace of the pod you used last. Switch between pods from the menu next to its name; adding, renaming and removing pods moved to Settings.
AI HIL tab and a live demo
AI agent
Web app
Describe a test in plain words and an AI agent runs it on your pod: flashing, power, UART, captures. Every tool call is shown as it happens. No pod yet? Try the agent on a simulated pod in the live demo.
The pod lists the Wi-Fi networks it can see, strongest first, so joining one no longer means guessing the name. A pod can also store its own calibration from two multimeter readings per output.
The pod also serves its API over TLS, with a certificate it makes on first boot. An HTTPS-only setting turns the plain port off on the network. First Wi-Fi setup is faster and no longer blocks the API.
Sine, square and sawtooth now play at the full 16 bits of the DAC and use the pod’s calibration. Give the waveform in volts, or in microamps on the 4-20 mA output.
The pod’s USB-C port is now also a network adapter: power and the full API over one cable, with no Ethernet or Wi-Fi. Use --connection usb in the CLI or BenchPod("usb") in Python. The CLI can also carry the pod’s cloud link through your computer.
Next to the BMP280, the pod emulates a BME280, an SHT4x and an MPU-6050 on I2C, and a GPS receiver sending NMEA on a UART. Change the readings while your firmware runs.
Updating a pod from the web app shows how far it got, and an update that loses its connection picks up where it stopped.
Signed firmware and LAN lock-down
Firmware
Releases are signed and the pod checks each update. You can lock the LAN API down to reads and captures, and the cloud link works behind a company proxy with your own CA.