Hardware Bench

• Agents that can see the bench

  Without physical senses, your agent has one hand tied behind its back. A camera over the workbench lets an agent look before it concludes: Is the LED flashing? Did the LCD screen update? Access to lab instruments lets your agent adjust voltage, monitor power consumption, capture an oscilloscope waveform, and more so it knows exactly what the hardware is doing.

• Measurements, not guesses

  An agent that cannot measure reasons from the schematic alone and tells you what should be happening. With the oscilloscope, the electronic load, and the power profiler in reach, your agent measures what is happening: the real rail voltage at power-up, the real current in sleep, the real edge on the bus. Every conclusion arrives with the capture that supports it, attached to the issue for you to check.

• From symptom to fix

  A fault report is only the start. Electronics skills carry the loop through: your agent traces the net in the schematic, reads the datasheet, forms a diagnosis, and changes the firmware or the design. Then it flashes the board, measures again, and keeps going around until the readings say the bug is gone. You get the fix with its before and after, not a list of things to try.

1. ObserveYour agent can pan, tilt, and zoom the camera, take a frame, and read the board and the screens.
2. MeasureIt sets up the instrument, captures the waveform or the current, and attaches the result to the issue.

1. ReasonIt traces the net in the schematic, reads the datasheet, and forms a diagnosis.
2. ChangeIt edits the firmware or the design. Changing power or wiring waits for your approval.

1. IterateIt measures again, compares before and after, and goes around again while the readings are still wrong.
2. TroubleshootThis is closed-loop troubleshooting: Hapimatic makes a change to the device, observes the consequences of that change, and continues to iterate until the bugs are solved.

PCB: a KiCad demo board, CERN-OHL-P-2.0 (notices)