Table of Contents
Advertisement
the Activity History page when a unit is receiving a
package that will be a downgrade to its firmware.
Figure 5-22 - Select Yes to Allow Downgrade
5. Select a firmware file to transfer from a list of firm-
ware files (Figure 5-21) that are stored on the Site
Manager server.
6. Once the Firmware Update Transfer has been initi-
ated, the Activity Status page will open (Figure 5-
23) and show the progress of the activity:
Figure 5-23 - Firmware Update Transfer Status Page
7. The detailed progress of the Firmware Update
Transfer can be monitored from the Activity History
page (Admin Tools > Activity History > View His-
tory):
Figure 5-24 - Monitor Progress Details of Firmware Update
Transfer from Activity History Page
Firmware Update Transfer
Run Firmware Update Transfer On Schedule
To run Firmware Update Transfer on schedule:
1. If you choose to Run the Firmware Update Transfer
on a schedule (Figure 5-16):
2. Configure the start date/time, hours, minutes, and
more on the Schedule Manager page. Once the
Firmware Update Transfer has been initiated, the
Activity Status page will open and show the prog-
ress of the activity and all unit revisions are con-
firmed.
5.2.1. Downgrading Firmware
Downgrades will be allowed if the Downgrade
Allowed drop-down (Figure 5-22) is set to Yes on the
configuration page, but a warning will appear in the
Activity History page when a unit is receiving a pack-
age that will be a downgrade to its firmware.
If there are any units on a particular Control Sys-
tem that will be downgraded, the entire Control Sys-
tem will be considered a downgrade. Additionally, if
the Downgrade Allowed drop-down was set to No,
the firmware will not be transferred to any controller
on this Control System.
The firmware will be transferred to the gateway
unit, and then the gateway unit will be instructed to
transfer to any other units that are members of the
control system one at a time.
5.2.2. Firmware Update Transfer
Interruption
If the transfer activity is interrupted for any reason
in the middle of attempting a transfer, the activity will
attempt to retry at a maximum of 3 attempts. If the re-
try attempts fail, the activity status will be updated to
Failed.
If this activity is started again at a later time, the
activity will check to see if the package is already on
the controller. If the package file is found to be on the
controller, the package will not be resent, but instead
the transfer will continue from the point where it was
interrupted/stopped earlier.
The last transfer to the Control System is always
saved for future reference.
Firmware Update • 61
Advertisement
Table of Contents
