Powered caster control reference

Google's powered-caster vehicle repository contains kinematic/dynamic calculations and control code derived from Holomni/XR4000-related research. The source is useful for studying the vehicle/caster model. It is not a complete robot release, supported Google product or ready-to-run hardware driver. [1] [5]

At reviewed revision ad231909e8cbe6785dbf682aac6bbe33797f92c8, Vehicle.cpp contains vehicle-state and matrix/control calculations with Eigen/C++. Inspect its eight-element joint/torque vectors, explicitly indexed four-caster homing and opposite encoder/motor rotation signs before selecting a platform. Match the assumed geometry, motor/encoder conventions and dynamic parameters before adapting the mathematics. The source review did not verify numerical behavior, controller stability or a complete dependency/build route. [5]

Within Vehicle.cpp itself, JointRad zeroes its output and returns before the encoder read and caster-state updates. Adding a hardware adapter alone would leave that path bypassed; inspect it as a source limitation, not an observed runtime result. [5]

The other crucial boundary is explicit in HWInterface.h: it calls itself a starting point to replace with the user's hardware interface. Its declarations are incomplete and do not implement the encoder/DAC/calibration transport needed by a physical system. An available vehicle class cannot substitute for that missing integration. This entry therefore does not claim working hardware communication or a successful upstream build. [4]

The Vehicle destructor also comments that DACs should be zeroed but currently relies on a watchdog instead. That is a source limitation to investigate alongside the missing interface, not proof that a watchdog exists or safely stops any selected hardware. No shutdown/recovery behavior was tested. [5]

A bounded next step is reading the vehicle/caster mathematics and enumerating the actual encoder, DAC, homing, calibration and watchdog requirements for a chosen platform. Implementing that adapter and verifying the real system would be separate work; this catalog entry does not perform or certify it. The Apache-2.0 project notice does not provide physical manufacturing designs or rights over an external robot. [1] [2] [4]

No build, numerical benchmark, hardware adapter, motor command, encoder readout, watchdog or physical vehicle test was run. This is a research-code reference whose missing hardware boundary is central to its scope. [4] [5]