HIMA HIMatrix F30 Safety Manual

7 Software for HIMatrix Systems HIMatrix
Page 40 of 72 HI 800 023 E Rev. 1.01
 Compiling the program twice and comparing the two CRC checksums ensures that data
corruption in the application is detected that can result from random faults in the PC in
use.
When starting up a safety-related controller for the first time, a comprehensive function test
to verify the safety of the entire system must be performed.
Function Test of the Controller
1. Verify that the tasks to be performed by the controller were properly implemented using
the data and signal flows
2. Perform a comprehensive function test of the logic by trial (see Testing the configuration
and the appl.).
The controller and the application are sufficiently tested.
If a user program is modified, only the program components affected by the change must
be tested.
Versions beyond 7
The safe revision comparator in SILworX can be used to determine and display all changes
relative to the previous version.
7.3.2 Verifying the Configuration and the User Program
To verify that the user program created performs the required safety function, suitable test
cases must be created for the required system specification.
An independent test of each loop (consisting of input, the key interconnections in the
application and output) is usually sufficient. The programming tool and the measures
defined in this safety manual make it sufficiently improbable that a code generated properly
from a semantic and syntactic view point can still contain undetected systematic faults
resulting from the code generation process.
Suitable test cases must also be created for the numerical evaluation of formulas.
Equivalence class tests are convenient which are tests within defined ranges of values, at
the limits of or within invalid ranges of values. The test cases must be selected such that
the program logic can be proven to be correct. The required number of test cases depends
on the program logic used and must include critical value pairs.
An active simulation with data sources is the only way to prove that the sensors and
actuators in the system (also those connected to the system via communication with
remote I/Os) are properly wired. This is also the only way to verify the system configuration.
This procedure must be followed both when creating the user program for the first time and
when modifying it.
7.3.3 Archiving a Project
HIMA recommends archiving the project every time the program is loaded into the
controller by performing a download or a reload.
The procedure for archiving a project is radically different in ELOP II Factory and SILworX.
Archiving a Project - Versions Beyond 7
SILworX creates a project in a project file. This must be suitably stored, e.g., on a storage
medium.
Archiving a Project - Versions Prior to 7
ELOP II Factory creates a project in a structure of sub-directories. To archive the project,
ELOP II Factory can store the content of this structure to an archive file, the project archive.
This project archives must be suitably stored, e.g., on a storage medium.

HIMA HIMatrix F30 Specifications

General

Brand	HIMA
Model	HIMatrix F30
Category	Controller
Language	English