Synopsis
Description
crucihil init is an interactive wizard that creates a rig TOML configuration by walking you through a series of prompts. It is “Path B” of the three rig setup paths:
- Path A — Write the TOML manually (use the Rig Configuration reference)
- Path B — Use
crucihil init(this command — guided prompts, no AI needed) - Path C — Use
crucihil discover(AI-assisted, probes hardware automatically)
crucihil run and crucihil agent.
Options
path
default:"rigs/"
Directory to write the new rig TOML into. Created if it does not exist. Short form:
-d.What the wizard collects
The wizard prompts for:- Rig name — used as the filename (
<name>.toml) and as the identifier in the cloud dashboard - Platform — hardware platform name (e.g.
orin_nx,s32g,custom) - Backend mode —
virtual(no hardware) orhardware - CAN interfaces — auto-detected from
ip link; you confirm or add manually. For each interface: bitrate, CAN-FD, and backend (socketcan,peak,virtual) - Ethernet interfaces — interface name and local IP for DoIP/SOME/IP
- Power backend —
virtual_power,gpio_relay, or skip - GPIO — optional GPIO pin definitions
- DBC paths — paths to
.dbcfiles for CAN and Ethernet signal definitions - ECU entries — logical address, transport (
doiporcan_isotp), boot timeout
Example session
Output
The wizard writes a valid TOML file to the output directory. The file is immediately usable withcrucihil run and crucihil agent.
Example output:
Tips
- If you are not sure about a value, accept the default and edit the TOML later.
- Boot timeouts, bitrates, and IP addresses are platform-specific. They belong in the TOML — never hardcode them in test code.
- After running the wizard, validate the TOML by running a test suite against the virtual backend:
crucihil run --suite suites/smoke.yaml --rig rigs/virtual.toml.
See also
crucihil discover— AI-assisted setup that probes hardware automatically- Rig Configuration Reference — all TOML fields documented
- Rig Backends — available backends for CAN, power, and GPIO