24
At the beginning the hardware and protocols to be used were defined in RTUtil by adding
the items to the network tree and the hardware tree. In the network tree, the RTU and all
the outgoing lines were defined and also the IEDs connected at the other end of those lines.
In the hardware tree the type of RTU was defined and the connected lines were linked. An
I/O bus had to be added to the CMU board in the RTU since it is crucial for the internal
communication to work. PLC, HMI and process archive functions were added to the CMU.
The PLC was also given all the necessary “virtual” objects necessary for the duplication or
modification of signals. Any specific details of the local control PC were not added as it
wasn’t necessary. All added items were given unique names and most were kept at default
settings. Important settings made were IED name, IP address (192.168.0.2) and the
parameter settings for the IEC -101 protocol such as transmission with full timestamp and
how the RTU was to be time synced from the control station. The RTU was also set as
SNTP server so that the relays could be time synced by the RTU. The control authority
timeout for the HMI had a very low setting at default. It was therefore increased to 3600
seconds and that is the time that the HMI user will be able to control the station before
having to request for control authority again.
Once all items and settings were done in RTUtil the next step was to export the Excel files
from RTUtil. These files contain all settings made making it possible to import them into
another project and give that project the same settings. The main idea for the Excel files is
that process objects can be added manually by typing in all object settings row by row, and
when engineering for IEC 61850 communication the process object are inserted
automatically by synchronizing a SCL (.scd) file with the Excel file using RTUtil. After
the export the projects Excel initialization had to be made. The Excel export and Excel
initialization procedure may be viewed in Appendix 1 on page 11 and the synchronization
is explained in section 5.7. An .iid file, containing RTU specific information such as name,
addresses and capabilities, was also exported and renamed to .icd as it is needed later on
when the data sets are assigned to clients in CCT.
5.4.1 Problems with RTUtil
One mistake made early on was using version 9.7.1.0 of RTUtil and since the firmware on
the RTU 560G was 10.0.1.0, the RTU would not accept the configuration files made with
the older version. By acquiring version 10 of RTUtil the problem was solved.
Kommentare zu diesen Handbüchern