Configuration
The agent reads three configuration files plus a state directory. This page covers the most useful fields.
The files
| File | What it holds |
|---|---|
/etc/rdyn/agent.toml |
Agent-level settings loaded once at startup: robot identity, server URLs, TLS paths, and the [zenoh] fallback. |
<state_dir>/robot.toml |
Per-robot transport, the uplink topic, command topics, command policy, motion, capabilities, and initial settings. |
/etc/rdyn/zenoh_config.json5 |
Zenoh networking config (JSON5). |
/etc/rdyn/ca_root.pem |
CA root: default trust anchor for verifying the cloud. |
The default state directory is /var/lib/rdyn/robot. All config is loaded through the agent's central config loader, so you only need to edit these files.
Identity and TLS
These fields live in agent.toml and tell the agent which certificate and key represent this robot. Most are written automatically during enrollment.
- CA root: trust anchor for the cloud. Precedence:
ca_rootinagent.toml>RDYN_CA_ROOTenv var > default/etc/rdyn/ca_root.pem. - Device certificate:
device_certinagent.toml, or<state_dir>/device.crt. - Private key:
key_privateinagent.toml, or<state_dir>/id_ed25519(Ed25519) or<state_dir>/robot.key.
If both a certificate and key are present, the agent uses mTLS. Otherwise it falls back to a development mode without client authentication.
State directory
The state directory holds identity files and the local SQLite database (assets.db, WAL mode). Override it with the RDYN_STATE_DIR env var if needed. Local data includes scheduled missions, features, objects, field rules, and settings.
Cameras
The agent auto-discovers V4L2 cameras on the host, and the operator selects a specific camera (or pair) during a teleop session. See Cameras and the integrator guide Configure a camera. Detailed camera configuration options (where selection and device/format preferences are set) are coming soon.
Editing robot.toml
Signed-in users edit this file in Rover Nexus.
- One robot. Open the robot's detail and choose Robot Agent Configuration. The page title is
Robot Agent Configurationplus the robot's name. When remote read is allowed, the form loads the file on the device. Save Config to Robot writes the whole file back when remote write is allowed. - A reusable preset. Robot Configuration Profiles is the same form with no robot selected. Add Robot links to it as Create a profile or Create or edit profiles. A profile is a named
robot.tomlowned by an organization. - A file only. The public Robot Config Tool is the same form in the browser. Generate robot.toml builds the file. Copy or download it and install it on the device. Nothing is saved to a robot from that page.
The agent reads robot.toml once at startup. Leave Restart the agent after saving so the new config applies immediately unchecked and the saved file applies on the next restart. Check it and the agent restarts after the write: the robot goes offline briefly, and a mission it is running is interrupted. The checkbox starts off.
Save motion stores turning radius, brake rate, and footprint for that robot and leaves the file on the device unchanged. Save Config stores those same values and sends the file.
If the robot does not allow remote config access, or the page cannot reach it, the form starts from defaults. You can still generate a file, download it, and edit <state_dir>/robot.toml on the device.
Lines that match the agent's default are written as comments. A brand-new form sets allow_remote_config_read and allow_remote_config_write to true, which is also what the installer writes, so Rover Nexus can load and save the file. An absent key on the agent means false.
You can load an existing file, or paste its text, and the form fills from it. Commented lines are treated as defaults.
Configuration profiles
Pick a profile in Add Robot (hidden for a simulator). The device receives that file as it enrolls, so the agent's first startup already uses it. Editing the profile afterward does not replace the file on robots that already enrolled. Open Robot Agent Configuration on that robot to update it.
Turning radius and footprint from the Add Robot form replace those keys in the delivered file when you set them. Brake rate always replaces the profile's brake rate. A blank turning radius, or a footprint that is not a valid outline, leaves the profile's value. A robot with no profile keeps the file the installer wrote. The motion values you enter are still stored on the robot.
A new robot, including a simulator, starts with a 1 m × 1 m square centered on the origin (+Y forward). Choosing a profile that has its own footprint replaces that square in the form. Clearing the drawing saves the square, and that square replaces the profile's footprint in the file delivered at enrollment.
Saving or deleting a profile needs permission to edit robot profiles in that organization. The profile's organization is fixed when you create it. Anyone who can add a robot can select a saved profile.
Capabilities and settings
robot.toml declares the robot's actions, sensors, settings, resource producers, events, and the initial settings values. Settings are seeded into the local database at first startup (insert-if-not-exists) and can then be updated from the fleet manager or from robot software. The Robot Agent Configuration form edits each of these, and each action and sensor row previews the robot-detail control as you edit it. See Declare capabilities and Capabilities.
Zenoh
/etc/rdyn/zenoh_config.json5 configures the agent's Zenoh networking (router endpoints, mode, etc.). If it is absent, the agent falls back to a [zenoh] section in agent.toml. For background, see Zenoh. The Zenoh router endpoints for your deployment are provided by the web app; for help, contact [email protected].