Use USB Auto Update to import a configuration and, optionally, install firmware on a supported RobustOS Device. Prepare the target devices first, then use a USB drive to carry out provisioning.
config.xml exported from a reference device running the same firmware version as the targets, or use a configuration already validated for them.firmware.ruf only if you also need a firmware update. Check the target model and upgrade path before using the image.Choose the route that matches how the devices are delivered. Both routes require USB Auto Update to be enabled and the Key to match the targets.
Agree the firmware version and customised default configuration, including Enable Automatic Upgrade set to ON, at purchase-order stage. Confirm that the Key is generated for the administrator account state the delivered devices will use.
Provision the devices without a factory reset. If a reset is unavoidable, enable USB Auto Update again and check the administrator account state before using the USB drive. Continue with Prepare the Key and USB drive.
Complete this setup on each target device that has not already been prepared. Configuring only a reference device does not enable USB Auto Update or change the administrator credentials on the other devices.
https://192.168.0.1 when the device uses its default LAN address, or use its configured LAN address. Sign in with the applicable administrator credentials.One Key can be reused for a batch only when the devices are of the same series and share the same administrator account state. Keep a validated Key and configuration pair for each account state. Do not retain factory-default credentials simply to reuse a Key.
key with no extension, at the root of the USB drive.router and copy config.xml into it. Add firmware.ruf only when a firmware update is required.USB drive root
├── key
└── router/
├── config.xml
└── firmware.ruf (optional)key and router/config.xml are required for configuration-only provisioning. The Key filename must not gain a suffix such as .txt.
Work through these checks in order. A disabled setting and a Key mismatch can both result in a normal boot with no files imported.
| Check | How to verify | If it fails |
|---|---|---|
| USB Auto Update is enabled | Interface > USB > Enable Automatic Upgrade must read ON | Set ON, choose Save & Apply, and reboot |
| The Key matches the administrator account | Confirm whether the password changed after the Key was generated | Generate the Key again on a device that already carries the final credentials |
| The stick is detected | In the syslog, look for usb 1-1: new high-speed USB device and USB Mass Storage device detected | Try a different, simple, FAT32 stick of 32 GB or less |
| The file layout is correct | key at the root, router/config.xml, and optionally router/firmware.ruf | Rebuild the stick as described above |
| The configuration is valid for this firmware | Export it from a device running the same firmware version | Re-export on the target firmware |
| The device was cold-booted | Power off, insert the stick, power on | Repeat the cold-boot sequence |
| LED behaviour | LEDs cycling means running; USR on means finished | If nothing blinks at all, return to the first four checks |
When contacting Robustel Support, provide: the model and serial number, current firmware version, the firmware versions used to generate the files, whether the administrator password changed before or after Key generation, a diagnostic export and the syslog from the failed attempt. Do not send the Key file.
The USB Automatic Upgrade Key is bound to the administrator account state when it is generated. It is not bound to an individual serial number or firmware version. A password change makes an earlier Key stop matching; changing firmware alone is not a reason to regenerate it.
When the Key does not match, the device boots normally and ignores the USB provisioning files. The mismatch produces no specific error or log entry that identifies the attempt.
For example, a technician signs in to a reference device, completes the forced password change and generates a Key. If the other devices still have their factory-default administrator account state, that Key will not match them. Prepare the target account state before generating and distributing the Key.
| Requirement | Reason |
|---|---|
| Never attach or publish a Key file in a ticket, article, email, chat, shared drive or repository | A Key in circulation is equivalent to a shared write password |
| Do not leave the Key on the provisioning stick after the job, and do not ship the stick or the Key with the device | The stick is the delivery path; leaving the Key on it re-arms the mechanism |
| Never keep devices on factory-default credentials in order to keep an earlier Key working | The first-login password change is a Robustel security measure; do not work around it by retaining default credentials |
| Re-generate and re-distribute the Key after every password change, and withdraw the previous one | Earlier Keys remain valid for as long as the earlier account state exists |
| Turn USB Auto Update off again once provisioning is finished, if the deployment does not need it in production | Reduces the exposure created by leaving the USB provisioning interface enabled |
| Prefer factory pre-configuration or RCMS for large or recurring fleets | Removes the physical-port path from the operational workflow |
| Treat a suspected Key or password leak as a credential leak: change the password, re-generate the Key, re-provision the batch, and report it through the Robustel security contact | A leaked Key behaves exactly like a leaked password |
USB Auto Update is still available on supported devices. It is disabled by default on RobustOS 5.1 and later; RobustOS 3.x and early RobustOS 5.x releases shipped with it enabled. Enable it only for workflows that need it.
| Item | Earlier firmware | Current firmware |
|---|---|---|
| USB Auto Update factory default | ON, on RobustOS 3.x and early RobustOS 5.x | OFF from RobustOS 5.1. On RobustOS 5.5.1, Enable Automatic Upgrade defaults to OFF |
| Administrator password | Default credentials could be used without a forced password change | RobustOS 5.5.x requires a password change on the first Web UI login |
| Firmware downgrade | Availability depends on the model and firmware path | On affected CRA compliance builds, anti-rollback protection can block downgrades to firmware outside the security baseline. Confirm the applicable model and build before planning a rollback. |
A normal firmware upgrade retains the existing configuration, including an enabled USB Auto Update setting. A factory reset, or Restore to factory configuration, returns the setting to its firmware default. On firmware where that default is OFF, enable it again before provisioning. Devices delivered with an agreed customised configuration retain that configuration until a factory reset is performed.
Do not downgrade solely to restore an earlier USB workflow or avoid the first-login password change. Robustel’s CRA readiness information describes anti-rollback protection for affected compliance builds. Downgrades outside the security baseline can be blocked; the applicable restriction depends on the model and firmware build. Confirm the approved recovery path with Robustel Support before attempting a rollback.
When enabled, USB Auto Update checks the USB storage present at boot, imports the expected configuration and optionally installs firmware. The USB operation requires no network connection or login, and does not record who made the change. A matching Key therefore needs the same protection as a shared write credential.
Physical access to equipment in roadside cabinets, substations, factories or vehicles is not always controlled. Leaving USB Auto Update enabled creates a physical provisioning path, and one Key can affect a whole batch that shares the same administrator account state. Prefer factory pre-configuration or RCMS for large or recurring deployments.
The Cyber Resilience Act (CRA), Regulation (EU) 2024/2847, sets cybersecurity requirements for products with digital elements, including secure-by-default configuration and secure software updates. Disabling USB Auto Update by default is Robustel’s security-hardening measure for affected firmware; the CRA does not specifically require manufacturers to disable this feature.
| Date | Milestone |
|---|---|
| 10 December 2024 | CRA entered into force |
| 11 September 2026 | Article 14 vulnerability and incident reporting obligations started to apply |
| 11 December 2027 | Main product cybersecurity requirements apply in full |
See the Cyber Resilience Act and Robustel’s CRA readiness information.
This guide covers USB provisioning on supported RobustOS 5.x devices. The tables below identify USB host interfaces; use the model’s own datasheet to check its interface configuration. RobustOS Pro gateways are outside this procedure.
| Model | USB host port |
|---|---|
| R1520 | 1 x 480 Mbps high-speed USB 2.0 (Type A, 5 V, 500 mA) |
| R1520e Global | 1 x 480 Mbps high-speed USB 2.0 (Type A, 5 V, 500 mA) |
| R2110 | 1 x USB 2.0 host (Type A, 5 V, 500 mA) |
| R2110e | 1 x USB 2.0 host (Type A, 5 V, 500 mA) |
| R2110 5G RedCap | 1 x USB 2.0 host (Type A, 5 V, 500 mA) |
| R3000 | 1 x USB 2.0 host, up to 480 Mbps |
| R3000 Lite | 1 x USB 2.0 host, up to 480 Mbps |
| R3000-Lite 5G RedCap | 1 x USB 2.0 host, up to 480 Mbps |
| R3000-Quad | 1 x USB 2.0 host, up to 480 Mbps |
| R5020 | 1 x USB 2.0 host (Type A, 5 V, 500 mA) |
| R5020e | 1 x USB 2.0 host (Type A, 5 V, 500 mA) |
| R5030 | 1 x USB 2.0 host, 500 mA |
| R5010 | 1 x USB 3.1 Type-C, also documented as USB modem mode; confirm the USB storage use case before relying on it |
On the R1520e, R2110e and R5020e, the USB host port supports batch firmware upgrades but does not send or receive data from slave devices.
| Model | USB host port | Reason |
|---|---|---|
| R1520LG | 1 x USB 2.0 host (Type A, 5 V, 500 mA) | Runs RobustOS Pro, not RobustOS; the behaviour described here does not apply |
| EG3120e, EG5100, EG5101, EG5101P, EG5120, EG5200 | USB 2.0 or USB 3.0 host depending on model | RobustOS Pro gateways |
| LG3120e, LG5100, LG5120 | USB 2.0 or USB 3.0 host depending on model | RobustOS Pro gateways |
For a model not listed here, consult its datasheet. A USB interface listing is not by itself confirmation of USB Auto Update support.