HIMA HIMatrix series compact safety controller

Mode 1: Unused time is used to reduce CPU cycles. After the user program is fully processed, it immediately starts processing the next user program, reducing the total cycle time.

Mode 2: The unused time of lower priority user programs is allocated to higher priority user programs to ensure high availability.

Mode 3: Do not use unexecuted time to execute user programs, but wait for the maximum duration of each cycle of the user program, and then start processing the next user program, generating CPU cycles of the same duration.

7.5 Overload Function - with L3

If the user program is modified, the changes can be transmitted to PES during runtime. The operating system checks and activates the modified user program, which then takes over control tasks.

Successful overloading requires planning sufficient reserves when the watchdog time is determined, or temporarily increasing the controller's watchdog time reserve. Any temporary increase in watchdog time must be coordinated with the responsible testing agency.

When overloaded, global and local variables are assigned the values of the corresponding variables from the previous project version. Renaming and deleting variables, as well as creating new variables, have the same effect and can lead to the initialization process.

Mandatory feature management

Forcing refers to the process of replacing the current value of a variable with a forced value, used to test user programs or simulate unavailable sensors.

8.1 Mandatory Warning

Warning: Mandatory values may cause personal injury! Existing mandatory restrictions can only be removed with the consent of the testing agency responsible for final system acceptance testing. Mandatory values can only be obtained with the consent of the testing agency. When mandatory, the responsible person must take further technical and organizational measures to ensure that the process is adequately monitored in terms of safety.

Attention: Mandatory values may compromise security integrity! Forcing values may result in incorrect output values. Forcing an extension of the cycle time may result in the watchdog time exceeding the limit.

8.2 Mandatory time limit - CPU-OS V7 and above

Different time limits can be enforced globally or locally. After the time limit expires, the controller stops forcing values. The behavior when the time limit expires can be defined:

Global forcing: Resource stops or continues to run

Local forcing: User program stops or continues to run

8.3 Forcefully disabling system variables

The Force Deactivation system variable can be assigned to a digital input connected to a key switch to immediately stop forcing:

Layout effect description

L3 Force Deactivation prevents global and local forced startup and stops the ongoing forced process

L2 Force Deactivation prevents global forced start and stops the ongoing forced process; Suppress the command to edit local process values, but do not reset the changed local variables to their previous process values

Startup and Configuration

9.1 Installation and Wiring

Installed on a horizontal DIN rail, maintain a minimum distance of 100mm between the top and bottom of the equipment

Connect input and output circuits through pluggable terminals

Grounding: Installed on a grounded DIN rail to ensure sufficient grounding connection; There is also a grounding screw on the upper left side of the shell

Power supply: Use a 24 VDC power supply with safety isolation, compliant with SELV or PELV requirements, and externally protected by a 10A delay fuse

9.2 SILworX Configuration - CPU-OS V7 and above

Resource allocation parameters (partial):

System ID [SRS]: Unique value in the network

Safety Time [ms]: Safety time, 20-22500 ms

Watchdog Time [ms]: Watchdog time, 8-5000 ms

AutoStart: Does the user program automatically start after connecting to the power supply

Global Forcing allowed: Is global forcing allowed

Multitasking Mode: Multitasking Mode (L3 only)

Hardware system variables:

Force Deactivation: Used to prevent coercion and immediately stop it

Emergency Stop 1-4: Emergency Stop Switch

Reload Deactivation: Block execution of overload (L3 only)

User LED 1-2: Activate the corresponding LED (L3 only)

9.3 Reset button function

If the compact system is turned on while holding down the reset button, it will restart and reset the connection parameters and user account to default values. After restarting with the reset button released, the original values will be used.

Diagnosis and maintenance

10.1 LED indicator light

RUN: Running status indicator

ERROR: Error stop status indication

PROG: Configure loading status indication

Fault: I/O fault indication

OSL/BL: Operating System Emergency Loader Status

10.2 Diagnostic History

Diagnostic history records various states of the processor and communication system, and stores them in non-volatile memory. The number of entries depends on the hardware layout and processor operating system version:

L3: 700 long-term diagnoses (CPU)/300 short-term diagnoses (COM), 700 short-term diagnoses

CPU-OS V7 and above: 300/230 long-term diagnoses, 210/655 short-term diagnoses

CPU-OS V7 and below: 500/200-250 long-term diagnoses, 300/700-800 short-term diagnoses