Adam's state is visible, and it can be stopped
The PNDbotics Adam gains three read-only telemetry cards — per-joint motor state, whole-robot state, and 12-channel feedback per hand at 50 Hz — plus an emergency stop. Its communication interface is now configurable for wired sites.

This round for the PNDbotics Adam is about two things: seeing what it is doing, and stopping it.
Low-level state is visible now
Three new read-only telemetry cards, live on the canvas once wired up:
| Card | Contents |
|---|---|
motor_state | Per-joint motor state |
robot_state | Whole-robot state |
hand_state | 12 channels per hand, left and right, at 50 Hz |
This data was always flowing inside the robot; it simply had no way out. With it exposed, the agent can tell what posture it is in and whether a hand has actually closed on something — and when something goes wrong there is a record, rather than inferring the process from the result.
All three are read-only sensor cards: available to any role, no operator permission required.
Emergency stop
An e-stop is now available — one command brings it to a halt.
Wired deployments no longer collide
Adam's communication interface is configurable. It used to be pinned to one interface, which collided with other links in wired setups; now you point it at whatever the site is actually cabled for.