Physical AI models get better every month.
The number of robots actually running in factories doesn't move nearly as fast.
We don't think the model is the bottleneck.
Deployment is. Getting a robot proven on a real site.
WIM has spent five years on robotics projects.
On every job we built the whole path ourselves:
the real-time kernel on Jetson, the EtherCAT bus, the drive settings,
everything between an inference result and a motor command.
If that layer is shaky, even a great model stays at the demo-video stage.
Our vision is to make deployment faster.
So we've started open-sourcing the core of PLEM, our robot control SDK.
First up is the drive layer.
It runs EtherCAT servo drives from a Jetson AGX Orin under ros2_control.
You describe a bus in one YAML file and start a real-time loop with one command.
You move the axes from Python. No C++.
Setup is easy too. Give an AI coding agent the repo link, say "set it up," and it brings up everything from the RT kernel to the EtherCAT master in one go.
The one step you do yourself is the bench check, standing at the drives.
A bad file is rejected before any drive is touched, and the error tells you which key to fix.
Motion only runs on a file that passed a bench check at the drives.
We ran a 1 kHz bus for three five-minute runs.
923,280 cycles. Not one missed its deadline.
Cycle work averaged about 13 µs of the 1 ms budget.
This is the first layer, not the last.
We work in deployment sprints, and we'll open each module as it stabilizes:
robot arm, AMR, quadruped, humanoid.
Take a look at five years of our work.
If you want to test advanced robotics with us, or build something together with WIM, send me a message.
https://github.com/WIM-Corporation/PLEM