Emerson Site Manager, User Manual

Page: 72 / 130

64 • Site Manager User Manual 026-1012 Rev 3 06-DEC-2011
firmware apply.
• If the firmware version match is not located, the sta-
tus of the activity will attempt to determine what
version of firmware it does have and report that in
the activity status. The activity history will then up-
date to Failed.
• If there is a complete match of firmware versions on
all the units, the version of the firmware packages on
the units will be compared to the firmware package
version of the last firmware transfer that is stored in
the database.
5.3.3. Downgrades and Setpoint
Clean-Out
If the firmware package version precedes the con-
troller version, this is a considered a downgrade.
Downgrading of firmware will result with a down-
grade warning reported in the activity history. There
will be additional warnings in the activity history stat-
ing that the units will be cleaned out of all setpoints
that are currently in the controller, which will be set
back to its original factory settings.
5.3.4. Non-Gateway Controllers
First, Gateway Last
• The Firmware Apply activity will start the process
on all of the non-gateway controllers and process
each one at a time. Only after all non-gateway con-
trollers have successfully completed will the Gate-
way controller will have the firmware applied. The
reason to apply the Gateway last is the connection to
the gateway unit will be lost once the firmware ap-
ply has been initiated.
• Once the activity has started to apply the firmware
packages, the activity will attempt to reconnect to
the device every 30 seconds for 15 minutes, or until
it has been reconnected. If the firmware activity is
unable to reconnect to the unit the Firmware Apply
status will result in a failed status.
5.3.5. Firmware Matching
• Upon acknowledgment from the controller, the
Firmware Apply activity will check and attempt to
find a match between the existing firmware version
of the controller and the version of the firmware
package being applied. If the controller’s current
firmware version matches the firmware package
version being applied, the record for the controller in
the database will be updated to reflect the new ver-
sion. The activity history will also be updated with
the new firmware version.
• The final status of the firmware apply for the target
control system will be considered successful, and all
other conditions such as database update failure or
program faults will result in a failed status.
5.3.6. Successful or Failed Results
• The status of the Firmware Apply process for each
controller will be checked for a successful result.
• If the Firmware Apply was successful, the apply
process will continue with the next controller (if ap-
plicable).
• If the Firmware Apply was not successful, the ap-
ply process for the entire control system will result
as failed and will stop the apply process for any sub-
sequent controllers on the schedule.
• Any condition of the apply process that results in a
status that is not successful will result in a failed
status.
• The activity history will be updated with the non
successful status and the reason for failure.
• The last message in the activity history will report
the warning message stating that the controller may
not be working properly or that the controller is un-
stable and should be evaluated immediately.