📖HomeBack The downloading of configuration from ClearSCADA to a SCADAPack E-Series outstation is initiated by calling or selecting the download configuration method on a SCADAPack E-Series Outstation database object. This behavior is controlled by using the Configuration Setup dialog that can be opened from the object menu of the SCADAPack E-Series Outstation object.
When the download configuration method is initiated, you may be prompted to select either "Download Changes" or "Full Configuration Download" from the pull down list. This depends on whether changes have been made to the outstation configuration in ClearSCADA.
The configuration download method on a SCADAPack E-Series Outstation performs several tasks in the following order:
If there are configuration files attached to the outstation at the beginning or end of the download, these files are firstly concatenated with the ClearSCADA generated configuration file and the complete concatenated file is named SCXConfig.rtu. This contains text based configuration instructions that allow the SCADAPack E-Series Outstation to modify its configuration when commanded.
This SCXConfig.rtu file is then downloaded from ClearSCADA to the outstation file system using a DNP3 file write command (object 70 Version 1).
When the outstation indicates that it has successfully received the new file, it is stored to the outstation file system.
ClearSCADA then sends the outstation a command line instruction to tell it to re-configure itself using the file downloaded and stored in the file system. This command is sent via the DNP3 file write command (o70v1). The command is "restart config SCXConfig.rtu".
After the outstation restarts the configuration file (note this is not the same as a the cold or warm restart referred to later) it responds to the master station that the re-start is complete.
The SCADAPack E-Series Outstation stores an additional file in its file system named "config.log". This file contains the results of the outstation parsing the downloaded configuration.
Should there be duplicate instructions in the downloaded file (due to combinations of additional files attached to the outstation), the last read instruction will be the instruction used for the final configuration.
This file is usually quite small (5 lines) if there is no incorrect configuration instructions in the SCXConfig.rtu file.
If there is faulty configuration in the SCXConfig.rtu file, then additional information will be contained in this log and this can be used for troubleshooting. There can be either fatal errors or information only warnings reported in this file.
The user can view the config.log file from the outstation outstation configuration setup dialog.
ClearSCADA sends a request to the outstation to forward the config.log file so that it can determine if the downloaded configuration was successful or contained warnings. ClearSCADA will raise suitable alarms indicating if there are errors or warnings in the log file.
ClearSCADA next issues a command to the outstation file system to delete the previous SCXConfig.log file (if one exists).
ClearSCADA then issues a command to rename the config.log file in the file system to SCXConfig.log. This is done so that troubleshooting can be performed at the outstation, and the user can determine which configuration was generated by ClearSCADA and whether the current configuration of the outstation was downloaded from ClearSCADA or from the E-Series Configurator software.
Depending on the restart level settings on the configuration files, ClearSCADA will issue either a cold or a warm restart. The outstation responds with the expected time that is required to perform the restart, which allows ClearSCADA to hold off from polling the outstation for this period.
When the outstation has restarted, it will confirm to ClearSCADA that it is ready to go. This may occur before the above time delay has occurred. Note: Changing the configuration settings for the communication port that the outstation and ClearSCADA are communicating through, may cause ClearSCADA to be unable to communicate further with the outstation. Regaining communications may require configuration changes to be made to the channel object to match the configuration in the outstation, or manual outstation reconfiguration if the downloaded configuration was unsuitable for the system.
ClearSCADA will then commence polling the outstation on the configured schedule, or receive unsolicited messages from the outstation as required by normal operation.
The above description covers the situation where the user has not appended files other than RTU configuration files. In the case where other types of files (such as profiles, IsaGraf, NTP configurations, binary format and feature licence files) are downloaded, a similar procedure will be followed. The typical order for downloading these files will be:
Profile files downloaded and profiles are restarted.
RTU configuration files downloaded and configuration restarted.
SCXConfig.log is uploaded.
IsaGraf files downloaded to IsaGraf targets.
NTP configuration files and Licence files download.
The outstation is restarted (either via warm or cold restart). It is not until this step that the changes take effect.
Please refer to the online help in the SCADAPack E-Series DNP3 Driver guide for configuration instructions.