Users Manual

Warning: Do not close the web browser tab which contains the Web GUI or press the renew button on
this tab, because it will abort the update procedure. In that case, repeat the update procedure from the
beginning.
Step 3: Reboot the rc_visard. To apply a firmware update to the rc_visard device, a reboot is required after
having uploaded the new image version.
Note: The new image version is uploaded to the inactive partition of the rc_visard. Only after rebooting
will the inactive partition be activated, and the active partition will become inactive. If the updated
firmware image cannot be loaded, this partition of the rc_visard remains inactive and the previously
installed firmware version from the active partition will be used automatically.
As for the REST-API, the reboot can be performed by the PUT /system/reboot request.
After having uploaded the new firmware via the Web GUI, a context window is opened as shown in Fig.
9.3.3 offering to reboot the device immediately or to postpone it. To reboot the rc_visard at a later time, use
the Reboot button on the Web GUI’s System tab.
Step 4: Confirm the firmware update. After rebooting the rc_visard, please check the firmware image version
number of the currently active image to make sure that the updated image was successfully loaded. You can
do so either via the Web GUI’s System tab or via the REST-API’s GET /system/update request.
Please contact Roboception in case the firmware update could not be applied successfully.
9.4 Restoring the previous firmware version
After a successful firmware update, the previous firmware image is stored on the inactive partition of the rc_visard
and can be restored in case needed. This procedure is called a rollback.
Note: Using the latest firmware as provided by Roboception is strongly recommended. Hence, rollback func-
tionality should only be used in case of serious issues with the updated firmware version.
Rollback functionality is only accessible via the rc_visard’s REST-API interface (Section 8.2) using the PUT /
system/rollback request. It can be issued using any HTTP-compatible client or using a web browser as de-
scribed in Swagger UI (Section 8.2.4). Like the update process, the rollback requires a subsequent device reboot
to activate the restored firmware version.
Warning: Like during a firmware update, all software components’ parameters will be reset to their defaults.
Please make sure these settings are persisted on the application-side or client PC (e.g., using the REST-API
interface, Section 8.2) prior to executing the rollback.
9.5 Rebooting the rc_visard
An rc_visard reboot is necessary after updating the firmware or performing a software rollback. It can be issued
either programmatically, via the rc_visard’s REST-API interface (Section 8.2) using the PUT /system/reboot
request, or manually on the Web GUI’s (Section 4.5) System tab. The reboot is finished when the LED turns green
again.
9.6 Updating the software license
Licenses that are purchased from Roboception for enabling additional features can be installed via the Web GUI’s
(Section 4.5) System panel. The rc_visard has to be rebooted to apply the licenses.
9.4. Restoring the previous firmware version 175