Software Command Reference¶
Command-Line Validation Modes¶
Use these modes before powering the gantry:
Mode |
Purpose |
|---|---|
|
Interactive move-by-move mode. It uses the same |
|
Engine-vs-engine dry run. It exercises setup, path planning, capture-slot routing, blocker relocation, and restoration G-code without connected hardware. |
|
Scanner-only mux diagnostic. It initializes the GPIO scanner and prints the BCM/header pin reference plus channel-by-channel mux readings without requiring a gantry serial connection or homing. |
|
Minimal GPIO output test. It opens the same GPIO chip path used by the scanner, requests one BCM GPIO as an output, drives it high for |
Command-line validation modes
Physical Mode Commands¶
Quick reference for all commands available in physical mode:
Command |
Description |
|---|---|
`play [white |
black]` |
`newgame [white |
black]` |
|
Manually enter a move in UCI format (e.g., |
|
Engine makes one move. |
|
Scan and display all 96 sensors (board + storage zones). |
|
Run full sensor diagnostic — reads each sensor individually with channel-by-channel output. |
|
Display the engine’s internal board position. |
|
Display the physical board occupancy tracking. |
|
Set position from a FEN string. |
|
Home the gantry to (0,0). |
|
Run gantry hardware test (move to e4, d5, test magnet). |
|
Exit the program. |
Physical mode commands
Note
The --oled-test command-line flag starts only the OLED test screen. It is useful for verifying display wiring before testing the full physical board. The --sensor-diag command-line flag starts only the GPIO scanner diagnostic, and --gpio-led performs a minimal GPIO output test. The Start, Stop, and Reset buttons mirror safe prompt actions as documented in the Operator UI chapter.