ELOP II-NT is a programming tool developed by HIMA for H41q and H51q series safety programmable electronic systems, which complies with the IEC 61131-3 standard. This system provides a complete engineering environment and supports full lifecycle management from hardware configuration, logic programming to online debugging. Through ELOP II-NT, engineers can efficiently build safety control applications that comply with SIL 3 levels and ensure the reliability and maintainability of the system.
HIMA PES and H41q/H51q system family
HIMA PES mainly consists of two system families, H41q and H51q, both of which adopt a modular structure and support single channel and redundant configurations. H41q is a compact system that integrates the central unit, power supply, and I/O modules into a 5U height 19 inch subrack, suitable for small and medium-sized applications with no more than 192 I/O points. H51q is a modular system consisting of a 5U central rack and up to 16 4U I/O sub racks, supporting up to 256 I/O modules, suitable for large distributed control systems.
According to security level and availability requirements, the system can be divided into three types: single channel (M), high availability (H), and extremely high availability (HR), and can meet the highest AK 6 requirements through T Ü V certified MS, HS, and HRS models.
Resource allocation and hardware definition
3.1 Creating Configuration and Bus Definitions
Configuration is the highest level of structural tool that organizes the PES resources of the entire system together. In ELOP II-NT, first create a configuration and then define a bus system (such as HIBUS). HIBUS is used for communication between PES and programming units, supporting master/slave mode and up to 31 logic stations. Bus parameters such as baud rate, stop bits, and parity can be uniformly set in the properties and automatically applied to each resource.
3.2 Resource Types and Cabinet Editing
Resources represent a specific PES, and the resource type (such as H41q-M, H51q HRS, etc.) is selected through "RT allocation". In the "Edit Cabinet" dialog box, you can intuitively define the modules of the central rack, I/O sub rack, and each slot. Module parameters (such as baud rate and protocol of serial interface) can be configured in the properties. I/O channels can assign symbol labels and associate them with variables in program instances, thereby achieving hardware and logic mapping.
3.3 Resource Attribute Configuration
The resource attributes include multiple key tabs:
I/O parameters: Define the response of PES to I/O faults, such as noise suppression cycles, shutdown behavior of faulty modules (display only, emergency stop, or normal operation).
Redundancy: Set the behavior of the redundant central unit in case of failure (immediate shutdown, limited time single channel operation, etc.).
Security: Configure security time, watchdog time, requirement level, and restrict online changes, mandatory and testing modes, and other operations.
Programming unit: Define communication parameters with PADT.
Code Generator: Control code generation options, including generating reloadable code, comparing object code, comparing code images, etc.
Programming and Variable Management
4.1 Program instances and variable types
Create program instances under resources to implement the functionality of program types. Variables support multiple types such as BOOL, UINT, INT, WORD, and can be assigned initial values. Global variables can exchange data between different program organizations and function blocks.
4.2 System Variables and Parameters
System variables are predefined and used to access or control the state of PES in user programs, such as I/O errors, forced states, running versions, etc. System parameters are used to configure resource behavior, such as safe time, watchdog time, mandatory permission, etc.
4.3 Event Creation
The variable can be configured as' event driven 'to record state changes with timestamps. Events can be divided into Boolean events (changes in switch values) and scalar events (numerical exceedance). Events are stored in non-volatile buffers and can be transmitted to the upper system through X-OPC servers.

Communication configuration
5.1 HIBUS and HIPRO Protocol
HIBUS is a proprietary bus of HIMA, supporting HIPRO-S (safety related) and HIPRO-N (non safety) protocols. HIPRO-S is used for secure data exchange between PES, using a point-to-point connection where data is directly transmitted from the sender to the receiver and protected by code and signature. HIPRO-N is operated by the PES master station as the data center, collecting data from slave stations and distributing it to other master stations.
5.2 PES main station
The PES master station is a coprocessor module in the H51/H51q system, capable of managing up to 31 slave stations. The main station program needs to be compiled and downloaded to the coprocessor module. The master station can be configured as a time master station, synchronizing the time of all PES on the bus.
5.3 Communication with External Systems