SAFETY MANUAL - Tuv-fs.com
SAFETY MANUAL - Tuv-fs.com
SAFETY MANUAL - Tuv-fs.com
- No tags were found...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>SAFETY</strong> <strong>MANUAL</strong><br />
3.6.3 Configuration File Verification<br />
The system.ini file defines a number of fundamental safety configuration options. It<br />
is important to ensure that the correct file is downloaded to the system and that this<br />
file represents the correct configuration.<br />
1. The system.ini file may be created using either the configuration tool<br />
or a text editor.<br />
2. Once <strong>com</strong>plete, this file should be downloaded to the system.<br />
3. The system.ini file shall then be uploaded from the system and<br />
checked that it contains the required configuration options. This<br />
ensures that no faults have been introduced by the configuration tool,<br />
the PC itself, or the down/upload process.<br />
4. Following this check the checksum of the file (uploaded with the file)<br />
should be recorded, and used to verify that the file has not changed.<br />
3.7 HIGH DENSITY I/O MODULE CONFIGURATION<br />
3.7.1 Module Characteristics<br />
The High Density I/O range has facilities to allow several of its operating<br />
parameters to be adjusted; examples of these include threshold settings, indicator<br />
operation, update rates, etc. The configuration settings available for each module<br />
type is defined in its corresponding Product Description (PD). In many applications,<br />
the parameter’s default values will provide the required operation.<br />
These parameters may be adjusted within the system.ini file, which shall be<br />
reviewed in a similar manner as other system configuration and programming.<br />
Once the configuration settings for a module have been determined, the checksum<br />
for the configuration data may optionally be calculated and entered into the<br />
system.ini file with the appropriate <strong>com</strong>mand. This provides further protection<br />
against configuration setting changes if desired. The checksum can be uploaded<br />
from the module, once the settings have been verified for <strong>com</strong>pleteness.<br />
3.7.1.1 SYSTEM Section Configuration<br />
The High Density I/O SYSTEM section within the system.ini file allows the internal<br />
bus activity, system watchdog and power failure signal and bypass timeouts to be<br />
adjusted. These may be adjusted for test and development purposes.<br />
Internal Bus Activity (IMBTO)<br />
The default setting (500ms) for the internal bus activity timeout is appropriate for<br />
most applications. This timeout may be adjusted to a shorter period; the adjusted<br />
period shall be shorter than the PST E less the overall system response time.<br />
This setting SHALL NOT be set to zero for operational systems.<br />
System Watchdog Timeout (WDOGTO)<br />
As with the internal bus activity timeout, it is not normally necessary to adjust this<br />
parameter. This value shall not be adjusted for safety-related applications<br />
and shall not be set to zero for operational systems.<br />
Doc Number P8094<br />
Issue 14 September 2003 Page 53 of 67
Change language