129 (148)
/device-info/
update/url
Write the URL of the update package (e.g. http://www.company.com/download/firmware.cup) to this
node before starting the remote update.
/device-info/
update/status
This node is used to trigger and monitor the update process. Write one of the trigger values (see
below) to this node in order to start the update. The node will then show the current state of the
update process:
•
0 – No update has been started. This is also the state you will see, after the update has been
applied and the device has restarted.
•
1 – Must be written to trigger download and installation of a remote update.
•
9 – Must be written to trigger download of an update package from a remote web server. After
the update package has been downloaded, the state will change to 11. The installation of the
update package must then be triggered by writing 10.
•
10 – Must be written to trigger installation of an update package downloaded from a remote
web server after the state has changed to 11.
•
2 – The update package is being loaded via the local web server.
•
3 – The update package is being loaded from a remote web server.
•
11 – The update package has been successfully downloaded from a remote web server.
Installation of the update package must now be started by writing 10.
•
4 – The update package is being checked.
•
5 – The update package is being unpacked.
•
6 – The update package is being programmed.
•
7 – The system is being cleaned up.
•
8 – The update module is shutting down.
•
-1 – Error: Loading the update package failed.
•
-2 – Error: The update package did not pass the check. Reasons may be:
–
Illegal update package
–
The update package was intended for another firmware.
–
The update package required another existing firmware version.
•
-3 – Error: Unpacking the update package failed.
•
-4 – Error: Programming the update package failed.
•
-5 – Error: Cleaning up failed.
•
-6 – Error: Loading the update package failed, because the target directory does not exist.
Maybe an external medium is missing or write-protected.
•
-7 – Error: Loading the update package failed, because the target file already exists, but could
not be overwritten. Maybe an external medium is write-protected.
•
-8 – Error: Loading the update package failed. Socket error.
•
-9 – Error: Loading the update package failed. Could not connect to server.
•
-10 – Error: Loading the update package failed. SSL/TLS error.
•
-11 – Error: Loading the update package failed. Could not send request.
•
-12 – Error: Loading the update package failed. Could not receive reply.
•
-13 – Error: Loading the update package failed. Internal buffer is too small.
•
-14 – Error: Loading the update package failed. Could not resolve host name.
•
-15 – Error: Loading the update package failed. File I/O error.
•
-16 – Error: Loading the update package failed. Protocol error.
•
-17 – Error: Loading the update package failed. Timeout.
•
-18 – Error: Loading the update package failed. Out of memory.
/device-info/
update/counter
This node holds a counter that simply will be incremented on each successful update. So if you apply
an update package without any visible effect - such as a change in the firmware version - you can use
this counter to check if the update package has been successfully applied.
Anybus Edge Gateway Reference Guide
SCM-1202-154 1.0 en-US
