HIMA X-CPU 01 processor module

HIMA X-CPU 01 processor module

Product description

The data processing within the HIMax system absolutely requires the X-CPU 01 processor module. The processor module is used for:

Can handle up to 32 user programs

Perform all central functions, including communication

Use up to 3 additional processor modules to handle redundancy

Process communication through secure Ethernet.  

Create and store CPU events.  

Store events created by I/O modules.  

This module has obtained T Ü V's safety related application certification, with a maximum of SIL 3 (IEC 61508, IEC 61511, and IEC 62061), Cat. 4 (EN 954-1) and PL e (EN ISO 13849-1).  

The security function of the module

The security features of the processor module include the following:

Processing user program. -If a malfunction occurs: Stop the user program and reset the variable to its initial value - If a malfunction occurs: Reset the processor module to a safe state and report to the CPU

status

Use safety related Ethernet protocols for secure communication between HIMA controllers (HIMax, HIMatrix, and remote I/O modules).   

The data is transmitted through the Ethernet interface of the processor module itself or the Ethernet interface of the COM module.  

Safety functions are executed according to SIL 3.   

The following elements also contribute to achieving security features:

Hardware self-test

Secure communication with I/O modules

Reaction when a malfunction occurs

If a fault is detected in the test harness, the processor module will enter the ERROR STOP state and restart. Diagnostic information can be used to investigate the cause of the malfunction.  

Start after error stop

If the cause of the malfunction still exists, the processor module will avoid restarting and repeating erroneous stops:

After the first error stop, the processor module restarts normally and switches to its system operation.  

After the second error stop, the user must restart the system using PADT after resolving the issue.  

Once the processor module runs for approximately one minute in system operation, the next error stop that occurs is considered the first error stop.

Type label

The type label specifies the following important details:

Product Name

Qualification mark

Barcode (QR code or one-dimensional code)

Part Number (Part Number)

Hardware Revision Index (HW Rev.)

Software Revision Index (SW Rev.)

Working voltage (power)

Explosion proof specifications (if applicable)

Production Year (Production Year:)

Security related processor system

The security related processor module is a 1oo2 processor system. Continuous self inspection ensures safety related operations.  

Features:

Two synchronous microprocessors

Specific DDRAM memory for each microprocessor

Testable hardware comparator for data bus

Watchdog (WD)

Gold capacitors for buffering date/time

LED used to indicate system status

Mode switch used to configure module behavior when voltage is turned on

The processor module compares data between two processors and triggers an interrupt if the following conditions occur Fault occurred.  

The monitor monitors two processors. The self check of the module will also check the watchdog.

system controller

The entire data transmission between various components of the system controller processing module:

Security related processor system

System bus A and B

Ethernet switch with connection interface

memory

This module has RAM and non-volatile memory. Non volatile memory is protected by CRC.  

Non volatile memory contains the following programs and information:

operating system

User project

Enable switch, watchdog time, safety time

Online modification

Variables with RETAIN attribute

Production data, if necessary, trim data

Fault status history

event

At startup, the system transfers program code from non-volatile memory to redundant program and data storage.

Alarm and Events

The processor module records alarms and other events in its non-volatile memory.  

An event is a change in the state of a variable executed by a factory or controller, with a timestamp provided.  

An alert is an event that indicates an increase in potential risk.  

The HIMax system records state changes as events at a specified point in time. The X-OPC server transfers events to other systems that display or evaluate events, such as control systems.  

HIMax distinguishes between Boolean events and scalar events.

Boer Event:

The variation of Boolean variables, such as the variation of numerical inputs.  

Alarm and normal states: They can be arbitrarily assigned to variable states.  

Scalar event:

Exceeding the limit value defined for scalar variables.  

Scalar variables have numerical data types, such as INT and REAL.  

Two upper limits and two lower limits are possible.  

For the limit value, the following conditions must be met:

Maximum limit ≥ upper limit ≥ normal area ≥ lower limit ≥ minimum limit.  

Lag may be effective in the following situations: - if the value is below the upper limit. If the value exceeds the lower limit.