Advertisement
SCADA interface
configuration
Configuration settings fall into three classes:
Site-specific data that need to be
changed on a per-site basis such as the
DNP3 slave address.
Those that must be set for correct
operation, but which remain constant
across all sites. An example might be the
radio power supply voltage.
Those that should be left as the default
settings unless there is a need to change
them. Examples are the more involved
DNP3 library settings.
Standard RCU configurations for a utility are
held in a configuration template file that
Siemens will set up according to the user
requirements defined in their RCU
configuration specification form
(KMS-3100).
The process to develop the template is as
follows:
1. The user completes an RCU
configuration specification form and
returns to Siemens. This form contains
all configuration settings required for
the RCU and the communications
protocol. The form also details which
settings will be visible to the field user
and which settings can be changed by
the field user. Since most settings are
fixed for a utility, they will usually be
hidden from the field user.
2. Siemens creates the utility specific RCU
configuration file and returns it to the
user.
3. Using the RCU Connect utility, the user
configures the protocol mapping (which
points are to be sent to the SCADA
system) and workshop tests the SCADA
protocol with the RCU Probe PC utility to
be certain that the RCU is working as
expected with the SCADA system.
The user now has a "template" configuration
file for the population of RCUs. Using this
template makes site commissioning easier
by minimizing the amount of site-specific
data required.
This manual lists all the configuration
settings that relate to the SCADA interface,
including the radio power supply, the radio
data interface and the DNP3 protocol. Other
settings that relate to the Fusesaver site are
detailed in the RCU operating instructions
(IC1000-F320-A198-X-XXXX).
11
Advertisement
