NoCap Robotics · Power & control electronics
We build the two boards an AGV's power bus actually depends on: the controller that drives the motors, and the breaker that protects the bus and tells you why it tripped. Every number we publish carries the evidence for it.
The lineup
We ship narrow. Pulse handles motor control; the SSCB handles what happens when the bus faults. Everything past those two is stated as a plan, not a product — we don't pre-sell roadmap.
ROS_BOARD_DC_V1
The integrated, galvanically isolated DC motor controller for commercial AMRs and AGVs. MCU, 4-channel drive, IMU, power and isolated telemetry on one manufacturing-grade PCB — micro-ROS native, so there's no translation layer between your ROS 2 graph and the motors.
48 V SOLID-STATE CIRCUIT BREAKER
A resettable circuit breaker for the 48 V robot bus — no fuses, no contactors, no field swaps. Microsecond fault interruption, CAN telemetry on every trip, and remote reset, replacing the fuse-plus-contactor stack robots have used for decades.
EDU_KIT · built on ROS_BOARD_DC_V1
The same industrial board, packaged for the teaching bench: a
validated reference pairing, three structured lab exercises, and
the documentation to run a real ros2_control course —
not a tabletop toy.
Motor-control roadmap — increasing sophistication
Pulse
DC · direct drive
V1 pre-production. The wedge product.
Phase
BLDC · 3-phase commutation
Planned. Unlocks once Pulse repeatably sells.
Flux
PMSM · field-oriented control
Later. Same safety architecture, more control.
Pulse → Phase → Flux is a deliberate progression, not a shipping date. The SSCB sits on a separate protection line and moves independently of it. Specs over hype.
How we publish numbers
Design System v2.0 gives us one rule and two marks. A value we measured on our own rig is marked one way, a value we took from a component datasheet is marked the other, and the sample size is printed beside it. If we can't name the sample size, the mark isn't earned.
We tested it, on our rig. The number beside the mark is how many units.
Taken from a component datasheet and not verified by us. Printed at full strength — you decide what to do with it.
Pulse · ROS_BOARD_DC_V1
The typical AGV control stack runs across four or five separate breakout boards. Pulse consolidates the MCU, four-channel motor drive, IMU and isolated power onto one industrial PCB — and puts a physical isolation barrier between the motor side and your ROS logic.
Every wire between boards is a failure point. Every extra board is a sourcing dependency, and a BOM built from development boards isn't a manufacturing BOM — it's a shopping list.
Power spikes from the motor side reach the MCU. Vibration loosens crimped joints. Nothing in that stack was designed to be built a thousand times.
Pulse is one part number, laid out for volume manufacture, with the isolation barrier drawn into the board rather than bolted on afterwards.
Architecture, not measurements — these carry no mark.
| Isolation | 2.5 kV RMS200 — measured in-house across 200 units |
|---|---|
| Quiescent draw | 42 mADS — supplier figure, component datasheet |
| Peak drive current, per channel | 80 ADS — supplier figure, component datasheet |
| Inertial measurement | 6-axisDS — supplier figure, component datasheet |
SSCB · 48 V solid-state circuit breaker
A solid-state circuit breaker purpose-built for 48 V AGV/AMR power buses — microsecond fault interruption, CAN telemetry, and auto-retry, replacing the fuse-plus-contactor stack robots have used for decades.
The problem
There's no affordable, CAN-connected, resettable breaker built specifically for 48 V robot buses. Chip-level eFuses exist, but you have to design a board around them. Commercial smart breakers either don't reach this voltage and current class or aren't built for mobile robots. That gap is what we're building for.
Cheap, but non-resettable. One field fault means a technician physically swapping a part — which means downtime.
Mechanical, bulky, they wear out, and they tell you nothing about why they tripped.
When something trips, you find out from a robot that stopped moving — not from a log entry with a timestamp.
What it does
Drop-in replacement footprint for a fuse-and-contactor pair, with the failure information you never got from either.
Specification
| Bus voltage | 48 V nominal (39 – 54.6 V) |
|---|---|
| Continuous current | 30 – 45 A |
| Fault interruption | ~1.2 µs detection |
| Overcurrent trip | ~45.6 A, programmable |
| Short-circuit trip | ~70 A, programmable |
| Telemetry | CAN 2.0B · 1 Mbit/s |
| Logged data | V, I, trip type, timestamp |
| Fault behaviour | Latch-off, remote CAN reset |
| Load compatibility | No inductance limit |
Who it's for
If you're running a 48 V bus and something on it needs protecting — especially if that something is currently a fuse — you're who we're building this for.
Running 48 V power buses, where a field trip to swap a fuse costs more than the fuse ever did.
Who need protection downstream of the pack, with a fault record you can actually read afterwards.
Needing resettable, loggable protection at this voltage and current class.
Design partners
Tell us about your power bus — voltage, current draw, what protects it today — and we'll follow up to see if there's a fit. No pricing conversation, no order form; this is us learning whether the thing we're building matches the thing you actually need.
For engineering & procurement
Datasheets, volume conversations and integration questions go straight to the engineers who drew the board — not to a sales desk.
Talk to engineeringFor labs & universities
Pulse Learn is the same industrial board with a curriculum around it — three graded lab exercises and a validated reference pairing.
Talk to the education team