2 diagnostic access, 3 configuration file verification – Rockwell Automation T8094 8000 Series TMR System Safety Manual User Manual

Page 54

Advertising
background image

SAFETY MANUAL

D oc N umber T8094
I ssue 27 – June 2013

Page 33 of 103

3.6.2 Diagnostic Access

The TMR Processor supports comprehensive diagnostic facilities. Some of these
facilities have the capability of modifying the system’s operation and are therefore
password protected, to provide access protection in addition to that afforded by
physical access to the system.

The password is defined in the Security section of the system.ini file. The password is
encoded and is not readily decodable from the system.ini text file.

A default password is implemented automatically, however it is recommended
that a specific password be defined within the system.ini file. It is important that
this password be made available only to personnel requiring access to the
additional diagnostic capabilities (typically only Rockwell Automation
personnel).
If this password is lost, there is no capability of accessing these functions
without reconfiguring the system.

3.6.3 Configuration File Verification

The system.ini file defines a number of fundamental safety configuration options. It is
important to ensure that the correct file is downloaded to the system and that this file
represents the correct configuration.

1. The system.ini file may be created using either the configuration tool or

a text editor.

2. Once complete, this file should be downloaded to the system.

3. The system.ini file shall then be uploaded from the system and checked

that it contains the required configuration options. This ensures that no
faults have been introduced by the configuration tool, the PC itself, or
the down/upload process.

4. Following this check the checksum of the file (uploaded with the file)

should be recorded, and used to verify that the file has not changed.

3.7 HIGH DENSITY I/O MODULE CONFIGURATION

3.7.1 Module Characteristics

The High Density I/O range has facilities to allow several of its operating parameters to
be adjusted; examples of these include threshold settings, indicator operation, update
rates, etc. The configuration settings available for each module type is defined in its
corresponding Product Description (PD). In many applications, the parameter’s default
values will provide the required operation.

These parameters may be adjusted within the system.ini file, which shall be reviewed
in a similar manner as other system configuration and programming.

Once the configuration settings for a module have been determined, the checksum for
the configuration data may optionally be calculated and entered into the system.ini file
with the appropriate command. This provides further protection against configuration
setting changes if desired. The checksum can be uploaded from the module, once the
settings have been verified for completeness.

Advertising