Dashboard

Your whole lab.
One tab.

Your remote lab for embedded development: book a board, talk to it, power it and keep every result. Included on every cloud plan, and on-premise on your own servers.

The WisentWire dashboard for one unit: serial console, power supply, telemetry and GPIO.

One day with a board
that lives in another room.

Here is a normal day for a firmware engineer whose prototype sits on a bench in another building. Everything below happens in one browser tab.

Coffee first.
Then the whole fleet.

The first screen shows every CoreUnit in your organisation: how many are online, which are physical or virtual, and which board is free right now.

Fleet overview: six CoreUnits, one online, with their status, target MCU and reservation.

The fleet at a glance. Total units, how many are online, and how many are physical hardware or cloud-backed.

Every unit on one card. Status, target MCU and who has it reserved, before you open anything.

Flash, debug, power. Quick actions on each card, one click from the overview.

Book the board.
Like a meeting room.

Shared test bench booking replaces the chat thread about who has the prototype. Pick a unit and a time slot, add a note, and it is yours until the slot ends.

New Reservation dialog: date, custom time 09:00 to 15:00, description "Running EMC tests", unit and who it is reserved by.

A week at a glance. Every reservation for every unit, so you can see when the board is free before you ask.

A slot or the whole day. Book exactly the hours you need, with a note like “Running EMC tests”.

Nobody steps on your run. While the slot is yours, nobody else can flash or power the board.

Open the unit.
Everything is already there.

One page per CoreUnit, with everything wired to it side by side. Point at a number to see what it does.

The unit page of the WisentWire dashboard.
  1. 1Serial console

    Every byte in and out of the board, with timestamps.

  2. 2Power supply

    Turn it on and off, set voltage and current limit.

  3. 3Telemetry

    Voltage and current over 5 minutes, 30 minutes or the whole session.

  4. 4GPIO

    Pins drawn the way they sit on the unit.

  5. 5Unit tabs

    General, Flash, Debug, Work Setup, Device Registry and Log History.

  6. 6Workbench

    Device registry, firmware registry, frame definitions and calendar.

  7. 7Live status

    Online state and when the unit was last seen.

Flash a build
you can name.

Every binary your team uploads lands in one firmware registry, with its version, target and notes. You flash a build you can find again, not a file from someone’s Downloads folder.

Firmware Registry: ELF files with version, target MCU such as STM32G030K8 and STM32H563ZI, notes, tags, size and upload time.

Search, sort and filter. By file name, target MCU or tag, across every build your organisation has uploaded.

Version and target on every file. Know which binary belongs on which board before it is flashed.

Notes and tags. “ds18b20 on pb0”, “rtt logs 1s interval”: the context stays with the build.

Talk to it.
Keep every byte.

The remote UART console logs both directions with timestamps, so the conversation you had with the board is still there tomorrow.

Serial console with a timestamped TX/RX log and the Save logs menu: ASCII, Hex and Hexdump.

Read it your way. Hex, ASCII or a hexdump, with absolute timestamps. Pause, auto-scroll or clear.

Send it your way. Hex or ASCII with validation, a choice of line ending, and the arrow keys for history.

Take it with you. Save the log as text with timestamps, raw hex bytes or an xxd-style dump.

Frame Definitions: binary protocol frame structures such as AT-Commands and dut1-motor-control with their fields.

Speak your protocol, not raw hex.

Frame definitions describe the binary frames your device under test understands, field by field, so commands and replies read as CMD and VALUE instead of bytes.

Power it.
Watch what it draws.

The supply of the board under test, in the same tab as its console. Every change shows up on the chart within a second.

Full-screen telemetry: voltage and current over time, with a hover readout of 7.400 V and 0.981 A.

Voltage and current limit, on sliders. 0 to 12 V and 0 to 3 A, with presets for 3.3, 5 and 6 V.

Locked while it runs. Settings cannot change while the supply is on, so a test cannot be disturbed halfway.

Zoom into any moment. Hover for exact readings, drag the range bar, or open the chart full screen.

Plug in the supply you own.

Bench supplies from Rigol, KORAD and Siglent register once in the Device Registry. Plug one into a CoreUnit and it drives that unit’s power, along with the programmer next to it.

See what is plugged in where, across the whole fleet or per unit, and which device is active on which CoreUnit.

Device Registry: power supplies Rigol DP832, KORAD and Siglent SPD1000X, with which CoreUnit each is active on.

Wire it once.
Name it once.

GPIO is drawn as the connector you are looking at. Give pins the names of your signals and everyone sees BOOT and RESET instead of OUT1 and OUT2.

GPIO panel in socket view: inputs with pull settings, outputs with toggles, 3V3 and GND.

Inputs at a glance. HIGH or LOW for every input, with pull-up, pull-down or no pull.

Outputs on a toggle. Drive reset, boot and enable lines with a click.

Socket or plug view. Flip the drawing to match the side you are wiring from.

The test fails.
The evidence is already there.

No one has to reproduce the bug to start looking at it. Log History keeps the power supply and every GPIO input of the unit, for the last hour or the last week.

Log History of a unit over 4 hours: power supply voltage and current, and GPIO inputs Reset, IN1 and IN2 as timing traces.

Power and pins, side by side. Voltage, current and every GPIO edge on the same time axis, so cause and effect line up.

1 hour to 7 days. Zoom out to see when it started, zoom in to the moment it broke.

Download all. Export the traces and attach them to the bug report.

Attach the debugger.
From your desk.

Start a GDB server on the unit with one click and connect from your IDE. Add a SEGGER RTT channel alongside it, or run RTT on its own.

Debug tab: flasher selection with target STM32F103C8, ST-Link v2 over SWD and the probe-rs toolchain, a GDB server with an RTT option and port 21377, and the OpenOCD console.

GDB server, one click. Pick the port, press Start Server, and point arm-none-eabi-gdb or your IDE at the unit.

RTT with it, or alone. A SEGGER RTT channel next to GDB, or RTT over telnet without a debugger attached.

Your probe, your toolchain. The flasher shows target, programmer, interface and toolchain: probe-rs, OpenOCD or J-Link.

Go home.
The tests keep running.

Everything you did by hand today is an API call. Hand the board to your CI pipeline overnight, to an AI agent while you sleep, and soon to your Robot Framework suites.

Your servers or ours.
The same dashboard.

Cloud. We host it and keep it up to date. Reach every bench from anywhere.

On-premise. The same dashboard on your own servers, with roles and an audit log.

Self-hosted. Free and feature-limited: the CLI, the Python SDK and the MCP server on one machine, for a single user. The web dashboard is not part of it.