BenchPod pin-out

Where everything is on the board, and what each pin does. Both diagrams look down at the pod in the same orientation, so the LA1 corner of the header points at the SMA end in each of them.

J1: the logic-analyzer header

A 2×11 header carrying the LA channels plus power, ground, CAN, an LA-bank voltage reference and target reset. Even pins run down one side and odd pins down the other, with pin 1 (LA1) at the bottom right: the square pad, at the ADC/DAC end of the board. The LA channels have no role-named pins: there is no pin marked SWCLK, so you choose which channel carries which signal and record that mapping once, in the pod's wiring profile (stored on the pod and edited in the web app's Pins pane, whose Visualize button draws your profile on this header), which tests read as benchpod_wiring. A channel the profile does not name is not wired: the pod leaves it floating and never drives it on its own.

BenchPod J1 header pinoutA 2 by 11 header shown with pin 1 at the bottom right, on the ADC and DAC side of the pod. Even pins 2 to 22 run down the left, along the board edge, and odd pins 1 to 21 down the right. From the bottom, the left column is LA2, LA4, LA6, LA8, LA10, LA12, LA14, then pin 16 ground, pin 18 plus 1.8 volts, pin 20 CAN minus and pin 22 NRST_CONTROL, the pod's dedicated target-reset line. From the bottom, the right column is LA1, LA3, LA5, LA7, LA9, LA11, LA13, then pin 15 ground, pin 17 plus 3.3 volts, pin 19 CAN plus and pin 21 LA_REF, a reference output at the LA bank's configured voltage. LA1 to LA6 have pull-up resistors, LA7 and LA8 have pull-downs, and LA9 to LA14 have neither. LA13 and LA14 need firmware 3.1 or newer.pull-upspull-downsNRST_CONTROL2221LA_REFCAN−2019CAN++1V81817+3V3GND1615GNDLA141413LA13LA121211LA11LA10109LA9LA887LA7LA665LA5LA443LA3LA221LA1board edge▼ ADC / DAC side of the podpin 1 (LA1) is the square pad (bottom right, at the ADC/DAC end)LA1–LA6 pull-ups (to the I/O voltage), LA7/LA8 pull-downs; LA9–LA14 neitherLA13 / LA14 need firmware 3.1 or newerLA_REF (21) is the LA reference; NRST_CONTROL (22) drives resetJ1, looking down at the pod: LA1 at the bottom right

Eight of the fourteen channels carry a fixed bias network, and they do not all pull the same way: LA7 and LA8 pull down. Each is switched in and out individually; all of them are off (high-Z) at boot.

LA channelNetworkValueGood for
LA1, LA2pull-up4.7kOpen-drain buses: an emulated or real I2C bus goes here
LA3, LA4pull-up2.2k
LA5, LA6pull-up10k
LA7, LA8pull-down10kHolding a line low by default, such as a boot-mode or enable strap
LA9 – LA14none—Anything that must float; nothing biases these

You ask for a direction, up, down or off, and the pod picks the resistor and reports its value: set_pull(n, "up") in the SDK and MCP, benchpod la pull n up in the CLI. Which way each channel can pull depends on the board, and the pod says it per channel (la_pins, pull_status). On today's boards it is the table above: asking LA7 to pull up is refused with BP0024 ("LA7 supports pull-down only on this board"), and up or down on LA9–LA14 with BP0023. Off works on every channel. The pull-ups go to the LA bank rail and the pull-downs to ground, so a pull-up holds the line at the I/O voltage, 1.8 V or 3.3 V, and pulls stay on when the bank switches. Firmware 3.10.12 and older engaged them only at 3.3 V: at 1.8 V it refused a request and released anything already on. In a test, pins.has_pullup(n) and pins.has_pulldown(n) answer this per channel rather than hard-coding it.enable_pullup(n) and enable_pulldown(n) are shortcuts for set_pull(n, "up") and set_pull(n, "down").

The wiring profile checks its assignments against this table. It warns when I2C sits on LA9–LA14 (no pod pull-up, so the bus needs external pull-ups) or on LA7/LA8 (pull-downs, so keep them disabled on an open-drain bus), and when UART RX is on LA7/LA8 (the UART idles high, so keep the pull disabled). Two signals on one channel is an error.

A profile can also say which pull resistors are on: its pulls key lists the channels, for example {"pulls": [1, 2]} for the I2C pull-ups on LA1 and LA2. Powering the board on with the profile (the web app's power switch, bp.power_on(), the MCP server's power_on) switches exactly those on and the other pull resistors off, after the I/O voltage and before the rail. A profile without the key leaves them as they are. In the Pins pane, click a pin and switch its pull-up or pull-down: a red dot on the pin is a pull-up that is on, an indigo dot a pull-down.

Pin directions

The wiring profile also says which way each wired signal goes, seen from the board: a board output (the board drives it), a board input (the pod drives it) or bidirectional. With firmware 3.10.4 or newer the pod refuses to drive a board output with a push-pull driver (a GPIO output, UART TX, the SPI clock, data out and chip select, SWD, an emulated sensor's outputs), because two push-pull outputs on one wire drive against each other. Open drain (I2C) and inputs still work. There is no override: fix the direction in the wiring if it is wrong.

This is on by default. Every wired role and signal has a direction, and the server, the SDK, the MCP server and the desktop app send them to the pod whenever the wiring is applied: when the pod or a session connects, and when the wiring is saved. The pod forgets them on a reboot, so they are sent again on the next connect. Older firmware is skipped.

WiringDefault direction
uart_rx, spi_misoboard output
uart_tx, spi_sclk, spi_mosi, spi_cs, swd_swclkboard input
i2c_sda, i2c_scl, swd_swdiobidirectional
a signal with direction input (the pod watches it)board output
a signal with direction output (the pod drives it)board input
a signal with direction open_drain or bidirbidirectional

The direction follows from what a pin is used for: in the Pins pane, a signal's "The pod" choice (reads it, drives it, or both ways open drain) is its direction. Profiles saved by older versions may carry a dut_dirs key that overrides the defaults; it is still honored, but the editors no longer write it, so set the signal's direction instead. A pin that is driven when the directions are sent keeps its old mark until it is released; the SDK reports it in bp.pin_directions_status and the MCP server in status.

Two more pins sit past CAN: LA_REF (21) is a reference output at the LA bank's configured voltage (1.8 V or 3.3 V), useful as a logic reference for external circuitry, and NRST_CONTROL (22) is the pod's dedicated target-reset line, the same one driven by flash(nreset=True) and reset_target.

Connectors on the board

The same view, zoomed out to the whole pod:

BenchPod connector layoutThe pod seen from above, drawn to scale. Along the top edge, left to right: an RJ45 Ethernet jack, a USB-C connector that carries the console, a green 5 volt output screw terminal whose positive pin is on the left and negative on the right, and a USB-A connector wired to that same 5 volt output. Both are the same rail behind one on/off switch, just two different connectors. Along the bottom edge, left to right: a green 4 to 20 milliamp output screw terminal whose minus pin is on the left and positive pin on the right, then four SMA connectors sticking out past the edge, each in its own color and each with a small test-point pair just to its right, close to the board edge, whose top pin repeats that connector's color and whose bottom pin is gray for ground: 0 to 3.3 volt DAC in blue, 0 to 5 volt DAC in indigo, plus or minus 12 volt DAC in violet, and plus or minus 30 volt ADC in pink. Finally a green 4 to 20 milliamp measurement screw terminal whose ground pin is on the left and positive pin on the right. Every screw terminal's ground or minus pin is gray and its positive pin is red. On the right edge near the top are two green screw terminals: the upper one is the output, which passes the input's supply through a switch, and the lower one is the 5 to 20 volt input; both have ground on their lower pin. On the left edge, in the middle, is the J1 logic-analyzer header, with LA1 at its bottom right corner nearest the SMA end. Inside the board are the RESET and BOOT buttons and the status LED.RJ45USB-C5V out+−USB-Asame railone switchOutputpasses input+GNDInput2.7–20 V+GNDJ1: LA headerLA1 at the bottom-right ↘RESETBOOTstatus LED−+4-20 mAoutputGND+4-20 mAmeasurement0–3V3DAC0–5VDAC±12VDAC±30VADCLooking down at the podgreen = screw terminalgray = GND / minus, on every terminal, header and test point in this diagramred = + on every screw terminal; USB-A carries the same rail as 5V outeach SMA and its test point's top pin share a color, so a probe traces straight back0–3V3 DAC0–5V DAC±12V DAC±30V ADC
  • Top edge: the RJ45 jack (wired Ethernet, the pod's primary network interface), the USB-C connector that carries the console, a green 5V out screw terminal (positive on the left; negative, the black lead, on the right), and a USB-A connector wired to that same 5V rail. The screw terminal and the USB-A port are the same output behind one on/off switch, just two different connectors for it.
  • Right edge, towards the top: two green screw terminals. The upper one is the switched output, which passes the input's voltage to the target; the one below it is the input, which accepts 2.7–20 V. Both have GND on their lower pin.
  • Bottom edge: a green 4–20 mA output screw terminal (minus on the left, plus on the right; plus goes to the loop supply), then four SMA connectors, each drawn in its own color (0–3V3 DAC blue, 0–5V DAC indigo, ±12V DAC violet, ±30V ADC pink), and finally a green 4–20 mA measurement screw terminal (GND on the left, plus on the right). Each SMA has its own small test-point pair just to its right, close to the board edge. The top pin repeats that SMA's color, and the bottom pin is gray for GND. Gray marks GND or minus on every terminal in this diagram, and red marks plus.
  • Left edge, middle: J1, the LA header above, with LA1 at the corner nearest the SMA end.

Some boards have a small blue trimmer in the analog section, near the ±30V ADC input. It sets how the ADC handles fast signals (above about 10 kHz) and has no effect on DC readings. Leave it as it is. Not every board has one: newer boards use a fixed capacitor instead.

Readings right at 0 V skip a small step: the ADC has a gap of about 3 counts at its zero crossing (about 3 mV in the normal range). A signal crossing 0 V jumps by that much, and one resting at 0 V can flip across it, which looks like extra noise. Readings away from 0 V are not affected. It comes with the ADC, so calibration does not remove it.

Choosing the DAC output

Connect your board to the one DAC SMA its pin tolerates, and pick the same output on the Generator and Capture tabs. A 3.3 V MCU pin belongs on 0–3V3: the 0–5V and ±12V outputs can drive more than it takes. The web app starts on the 3.3 V output until you pick another one, then remembers your choice for that pod in your browser. If the bench has a control loop output stage in its wiring, it starts on the stage's output instead.

What the 4–20 mA ports are for

4–20 mA is the standard industrial current loop: a sensor or transmitter reports a reading as a current, 4 mA for 0% and 20 mA for 100% of its range, so it survives long cables and a broken wire (0 mA) is easy to spot. PLCs, process controllers and data loggers read these loops. The two terminals are for testing boards like that. They are not a power output: use TARGET POWER (5V or EXT) to power a board.

  • 4–20 mA output: the pod plays the sensor. It acts as a two-wire transmitter in your board's loop, so you can feed its loop input any reading, ramp it, or fake a fault (below 4 mA, above 20 mA) and check what the firmware does.
  • 4–20 mA measurement: the pod reads your board's loop. Wire it in series with your board's transmitter output and capture the current in mA, the same way the ADC captures a voltage.
Output (pod as the sensor), one series loop:
  loop supply +  ->  pod OUT +
  pod OUT -      ->  your board's loop input
  loop input     ->  loop supply -

Measurement (pod reads your board):
  your board's 4-20 mA output  ->  pod IN +
  pod IN GND                   ->  your board's GND

Wiring the 4–20 mA output

The output is a two-wire transmitter. It does not source current. An external loop supply of 12–30 V powers the loop, and the pod sets how much current flows: supply plus to the plus pin, the minus pin through the receiver to supply minus. The current follows the DAC, from about 4 mA at zero to 20 mA at full scale, whichever DAC output is selected. The analog v3r2 board (board_rev v3r2 in the pod's status) has a DAC channel for each output instead, so there the loop current and the voltage outputs are independent: setting a current leaves the voltage outputs as they are. To set it in mA, pick 4-20 mA output (J9) as the output on Simulate (Signals). To read a loop on the measurement terminal in mA, pick 4-20 mA input (J8) as the ADC input on the Capture tab.