Table of Contents
Advertisement
Power-up and Restart
The MCOM LED (see LED description in Table 17-1) on the expansion module indicates the
connection status between the expansion module and the main CPU and expansion frame
initialization progress.
The main CPU expects the expansion frames to complete the initialization within a
configurable period of time (60 seconds default). After this period of time elapses, the main
CPU will operate normally with the connected frames and their I/O modules. Any expansion
frame that has not completed initialization within that time (e.g. because it was connected later
to the RTU) will be ignored until the next main CPU restart.
Note that after the main CPU starts up, it waits for the expansion modules to complete the
initialization process. The wait time is derived from the number of expansion frames
configured in the RTU. After all the expansion frames have completed the initialization, the
main CPU will continue its system startup. The main CPU will wait 60 seconds (default) for
all expansion frames to connect.
Restart after Firmware Download
After a new version of the firmware is downloaded to the main CPU, the CPU and all
expansion modules will restart (as with configuration download or main CPU power reset.)
Note that the restart includes the time to identify all expansion frames, as described above.
After a new version of the Expansion Loader firmware is downloaded to the expansion module
(using the STS Hardware Test feature), the expansion module will restart itself. For
information on upgrading the Expansion Loader firmware, see the ACE3600 STS User Guide.
Restart after Configuration Download
After a site configuration is downloaded to the main CPU, the CPU will restart and will
instruct the expansion modules to restart as well. Note that the restart includes the time to
identify all expansion frames, as described above. For information on downloading to the
RTU, see the Operation chapter of the ACE3600 STS User Guide.
If the RTU fails to restart after the user-defined site configuration was downloaded, a unique
LED display (in the range of the PI1-TX and SI2-RX LEDs) will follow. The RST LED will
turn RED and the RTU will restart itself with the previous "good" configuration. The
expansion module will be restarted. The following message will appear in the RTU Error
Logger "Configuration file was deleted due to failure in startup. Rolling back to the last
configuration file." Errors can be retrieved from the RTU using the ACE3600 STS Error
Logger utility.
If the newly-downloaded configuration has a problem which prevents the expansion module
from connecting to the main CPU, the expansion module is restarted, and will operate in
Expansion Loader mode. It will restart every two minutes, and be unable to perform
discovery/load image from main CPU. If the site's I/O configuration includes one or more
frames, a warning is displayed in the main CPU. If no frames were configured for the site, the
main CPU will ignore all Expansion Loader discovery requests.
If the startup succeeds after configuration download but has errors, these errors are reported in
the RTU Error Logger. It is, therefore, recommended to check for errors after downloading a
configuration file to the RTU. Errors can be retrieved from the RTU using the ACE3600 STS
Error Logger utility.
17-5
Expansion Module
Advertisement
Table of Contents
