The SINAUT Configuration Tool
6.7 Saving and generating system data
TIM DNP3
236 System Manual, 12/2015, C79000-G8976-C253-04
The consistency check is always started automatically before you use the generate/compile
functions in subscriber administration to prevent SDBs or DBs being created with
inconsistent data.
The consistency check can also be started as a separate function using the
SINAUT / Check
consistency...
menu in subscriber administration.
Errors detected during the consistency check are displayed to the user in an error list.
Image 6-25 Example of an error list after running the consistency check
If inconsistent connections are found, the error list indicates that cause will be diagnosed in
the connection configuration in the
Invalid connections
dialog.
After eliminating an error, you must save prior to the next consistency check otherwise be
eliminated error will still be reported.
Generating system data after changing the configuration of an existing system
Generating system data after changing the configuration of an existing system
Changes to an existing system made in
NetPro
or in
HW Config
are stored there. The new
system data blocks, on the other hand, can be generated in various configuration tools.
In the following situations, after changes have been made to the project configuration, the
SINAUT configuration tool should be started to generate the system data blocks (SDBs) in
the
Subscriber Administration
:
● After changing the configuration of a TIM module
● After changing the configuration of a configured connection to a subscriber
● After changing communications parameters of a DNP3 master station
After changing or adding new subscribers or connections, the connection configuration and
then the subscriber administration must be called in the SINAUT configuration tool to
generate the SDBs there.
The activities required following a configuration change are summarized in the section
Changing the configuration (Page 237).
To Next Page
Loading...
Need help?
General
