Motion and sensing
How machines know where they are and move where they should: estimation, control loops, motors and drives.
Our own studies in this area are under neural networks for motion and sensing.
Notes 12
Choosing the MotorPicking a motor for a robot joint or a drive? Torque decides, not RPM. A gearbox trades speed for torque, so size from the load first, then choose between stepper, BLDC with FOC, servo and brushed DC, joint by joint.24 minPID Is Not a GuessA PID controller is three knobs: now, always, and what's coming. Guessing them burns motors. Ziegler–Nichols (1942) still works, Tyreus–Luyben trades speed for zero overshoot, and the whole argument is settled in simulation before anything moves.11 minRobot arm controlA robot arm runs one loop, sense, decide, move, and the human is the gate before the risky move. ISO 10218:2025 (Feb 2025) folds the old ISO/TS 15066 limits into the standard and makes force validation mandatory: a chest takes 140 N before it hurts, a face 65 N, and a 20 kg arm moving toward a chest must stay under 0.24 m/s. The safe speed costs 2.55 seconds a move, and the log is what proves the arm asked.14 minThe Arm That FeelsFour ways to make a robot arm touch things without breaking them, direct force control, impedance, admittance, and hybrid position/force, with a real contact simulation on a bench arm.22 minThe Axis That Doesn't BacklashA linear axis misses position, whips at speed, or drops its load on power loss, and the fault is usually the architecture, not the motor. Ball screw vs lead screw vs belt vs rack vs linear motor, the five numbers that decide, and a worked Z-axis sizing.16 minThe Drive StageA BLDC driver is five sections, six switches, and one rule that matters more than the rest: the two devices in a half-bridge must never conduct together. This is how the drive stage works, how it dies, and the arithmetic that keeps it alive, with a worked 48 V design.30 minThe Encoder Is the LoopAn encoder is the sensor that tells the controller where the shaft is, that is the whole job. Incremental counts pulses and forgets everything on power loss; absolute reads a unique code for every angle and knows where it is the instant power returns. This is what resolution buys, why it is not accuracy, why velocity comes from differentiating position and gets noisy at low speed, and what Example Labs' bench arm needs on each of its four joints.24 minThe Gearbox Is the JointPlanetary, harmonic, and cycloidal gearboxes compared on the four numbers that decide a robot joint, backlash, stiffness, efficiency, and cost, with a worked demo on a real arm.18 minThe Motor That Doesn't HumYour motor hums because the drive is switching in blocks, and the torque dips at every 60° boundary. Field-oriented control holds the current exactly 90° ahead of the rotor flux, so the ripple falls from about 14% to under 1%, and the harmonics stop becoming heat. Here is the arithmetic, and the one place trapezoidal still wins.27 minThe Shape of the MoveYour arm arrives on time and then shakes for two seconds. The move was never the problem, the shape of the move was. Trapezoidal is faster on paper; S-curve is faster on the machine, and here is the arithmetic that proves it.19 minLiDAR vs Time-of-FlightLiDAR and time-of-flight both measure distance by timing light, but they are not the same sensor. Direct ToF times each laser pulse; indirect ToF measures a phase shift. One reaches 200 metres, the other reads a room at 240 Hz. This is how to choose by range, accuracy, sunlight, and surface, with Example Labs' warehouse robot as the worked example.23 minSensor Fusion and the Kalman FilterOne sensor is never enough: GPS is honest but slow, an IMU is fast but drifts 15 metres in 30 seconds. A Kalman filter is a running best guess that weighs each reading by how much it trusts it, an idea from 1960 that flew Apollo to the Moon on 2k of RAM.11 min