System settings
The remaining Robot Configuration controls: which software the Robot runs, which messages it stops showing you, and moving a whole configuration between Robots.
Update Channel
Selects which release of RobFlow the Robot runs:
| Channel | Contains |
|---|---|
| Stable | The latest stable features |
| Beta | Pre-release features, in addition |
Switching to Beta asks for confirmation.
What the Beta channel unlocks
The update channel does more than choose an update stream — several features are gated on it and simply do not appear on Stable:
- RobSafety — the whole view.
- Robot Calibration — the Calibration tab.
- OPC UA — the certificate management tab.
- The Calibration (Beta) and Configure Pallet (Beta) Dashboard Widgets — see the Widget reference.
If a feature described in this documentation is missing from your Robot, check this tab first. Beta-gated features are absent rather than disabled, so there is nothing grayed out to hint that a channel switch is what is needed.
Beta features are pre-release. Weigh that against the fact that RobSafety — which configures the Robot's safety behavior — is currently among them, and plan a validation pass after any channel change.
Suppressed Messages
Messages you have chosen to stop seeing are listed here. A message is suppressed from the message log itself, not from this tab; this tab is where you review what has been suppressed and undo it.
Clear all un-suppresses everything, and the tab tells you when there are no suppressed messages yet.
Suppression is for genuinely uninformative noise. It is worth reviewing this list occasionally: a message suppressed during commissioning to reduce clutter may be exactly the one that would have explained a later fault.
Messages a Flow raises itself come from the Message Log Node, and the log is visible on a Dashboard through the Message Log Widget — see Robot State Widgets.
Import and export
The header of Robot Configuration offers Import Robot Configuration and Export Robot Configuration, which move the entire configuration as one file — Tools, Workspaces, Modbus and SQL connections, CSV configs, RobVision devices, I/O naming and Variables.
This is how you commission a second identical cell, or restore a Robot after a replacement.
On import, collisions with what already exists are resolved per entity, so importing does not silently overwrite a Robot's own configuration.
Robot Configuration also shows a Last saved timestamp, and an overwrite offers an Undo — useful when an import turns out not to be what you wanted.
An exported configuration contains stored credentials, including SQL Connection passwords. Treat the file as a secret: it is not sanitized on export.
The export carries connection definitions, not reachability. After importing on another Control Unit, check that the Modbus, SQL and RobVision addresses resolve from that Robot's peripheral port before running a Flow that depends on them.
When a configuration change is blocked
Most tabs are read-only while a Flow is running, since changing a Tool or a Workspace mid-run would invalidate what the Flow is doing. The Calibration tab stays interactive during a run, because running a calibration Flow is exactly how a calibration is performed.
A Flow can also verify the configuration it expects before it starts, with a Robot configuration check.