Skip to content

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 open Robot Agent Configuration for the robot, or 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:

  1. 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.
  2. 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.
  3. 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

  1. Open Robot Agent Configuration and choose Add setting, or open robot.toml:

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

  1. Add one [[settings]] entry per key. key and label identify it. default is a tagged value. range, step, and description are optional. The full field list is Robot Configuration → [[settings]].

toml [[settings]] key = "maxSpeedMps" label = "Max speed" default = { type = "number", data = 1.2 } range = [0.0, 3.0] step = 0.1

The default type is string, int, number, bool, or enum. An enum default looks like { type = "enum", data = { value = "MED", options = ["LOW", "MED", "HIGH"] } }.

  1. Save the robot config, or restart the agent on the device so it seeds any new keys:

bash sudo systemctl restart rover-agent

  1. 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.
  • Supported default types are string, int, number, bool, and enum.

Next steps