Configure Robot Settings

Goal: Manage the robot's settings key/value store: seed it from robot.toml and update it from the fleet manager or robot software.

Before you begin

The agent is installed and enrolled (see Install the Agent).
You can edit <state_dir>/robot.toml (default /var/lib/rdyn/robot/robot.toml) as root.

How settings work

Settings are a per-robot key/value store the agent persists locally. Each entry has a value, a type, when it was last updated, and who updated it.

There are three sources, in order of when they apply:

Seed from robot.toml — at startup the agent loads the settings declared in robot.toml into the store on an insert-if-not-exists basis. Existing values are not overwritten on restart.
Fleet manager updates — operators can change settings from Rover Nexus; these arrive over the cloud downlink and are recorded as updated by the fleet manager.
Robot software updates — your robot software can update settings over local Zenoh; these are recorded as updated by the robot.

Because seeding is insert-if-not-exists, robot.toml provides initial defaults, while later changes from the fleet manager or robot software take precedence and persist.

Steps

Open robot.toml:

bash sudo nano /var/lib/rdyn/robot/robot.toml

Add your initial settings as key/value entries in the settings section. A reference for the exact section name and key/value syntax for settings in robot.toml is coming soon.
Restart the agent so it seeds any new keys:

bash sudo systemctl restart rover-agent

To change a value later, update it from the fleet manager in the web app, or have the robot software publish the update over local Zenoh. These updates persist across restarts and are not reset by the robot.toml seed.

Notes

Editing robot.toml only affects keys that do not already exist in the store; to change an existing value, update it via the fleet manager or robot software.
A reference of the supported value types for settings is coming soon.

Next steps