Use the default feature set for local development unless the task specifically needs Linux robot hardware.
cargo fmt
cargo test --lib
cargo build --binsReal hardware builds should be checked on Linux:
cargo build --bins --no-default-features
cargo run --bin hw_probe --no-default-featuresIf autonomous or manual cannot find the config, confirm the process was started from the crate root and that robot/config.json exists.
If logging does not appear where expected, inspect the logging block. For the standard config location, relative log paths resolve from the crate root.
If vision produces no tracks, check that the vision block exists, model paths are valid for the selected backend, and the camera backend can read frames.
If manual does not respond to input, check the configured controller names and codes. In real hardware mode, also confirm the gamepad is visible to gilrs.
If real hardware mode fails on macOS or another non-Linux platform, use the default simulate build or move the check to Linux.