Utama Core now treats the setup around a real robot test as something software must verify continuously. Its new field check watches the camera stream, reported field size, each configured robot's identity and position, and radio feedback. If a required check fails during a real run, the referee issues a halt command before the next control tick can send motion.
The same change adds a two-robot test program with the field, visible camera half, robot identifiers, working hardware, and tactics collected in one configuration block. Every camera run can be recorded in the RoboCup game-log format with raw vision and radio traffic on one clock. A calibration mode then drives fixed moves and estimates control delay, speed gain, acceleration, missed detections, vision noise, and kick speed from the recording. In a synthetic test, the tool recovered delay within 10 milliseconds and speed gain within 1 percent.
Robotics teams often lose field time to setup mistakes that look like planner or controller bugs. Utama's approach makes those conditions visible on the dashboard and stops unsafe motion without relying on an operator noticing first. A team adopting it can rehearse the same robot profiles in simulation, then carry the configuration and recorded evidence onto the field instead of rebuilding the test procedure from memory.