Technical Specifications

FAQ

1. What is the HIMA F60 CPU 01 used for?

The HIMA F60 CPU 01 is the central processing module of the HIMatrix F60 safety-related automation system. It performs the main control functions of the controller, including execution of the operating system and user program, processing of I/O data, system diagnostics, and communication with programming devices and other connected systems. The CPU also monitors important operating conditions such as supply voltage and temperature. Because it serves as the central processing unit, the CPU 01 works together with the F60 power supply, communication interfaces, and I/O modules to form a complete safety-related control system.

2. What communication interfaces are available on the F60 CPU 01?

The CPU 01 provides four RJ-45 Ethernet interfaces supporting 10/100Base-TX communication through an integrated switch. These interfaces can be used for communication with programming and diagnostic equipment as well as other compatible systems. The module also provides two 9-pin D-sub fieldbus interfaces designated FB1 and FB2. Depending on the installed fieldbus submodule and system configuration, these interfaces can support fieldbus communication such as PROFIBUS DP. The available communication functions should always be configured according to the installed hardware and the requirements of the specific F60 application.

3. Which programming tools can be used with the F60 CPU 01?

The F60 CPU 01 can be used with HIMA programming environments including SILworX and ELOP II Factory, depending on the CPU and operating system version. The programming environment is used to configure the controller, develop or manage the user application, establish module parameters, and perform diagnostic activities. When commissioning an existing CPU 01, the installed firmware and the programming environment should be checked before attempting to load or modify an application. Using compatible software and firmware versions is important for maintaining reliable communication with the controller and avoiding configuration conflicts.

4. How does the F60 CPU 01 monitor its own operation?

The CPU 01 incorporates monitoring functions for important controller operations. It monitors the correct sequence and logical execution of the operating system and user program and performs hardware and software self-tests. The CPU cycle, I/O processing, operating voltage, and operating temperature are also monitored. If a relevant internal fault is detected, the controller can initiate the appropriate safety response according to the system architecture and configured application. Status LEDs on the front of the module provide useful information for identifying operating conditions and faults, making them an important first diagnostic point during commissioning or troubleshooting.

5. What should be checked if the F60 CPU 01 reports a fault?

Start by checking the front-panel status indicators and identifying whether the problem is related to the CPU, power supply, communication interfaces, or connected I/O modules. The 24 VDC supply should be verified to ensure that it is within the permitted operating range. The CPU temperature and module installation should also be checked. If the controller is unable to execute the application correctly, diagnostic information from the programming environment should be reviewed to identify hardware, configuration, communication, or application-related faults. Field wiring and connected modules should also be inspected when an I/O or communication fault is indicated. Troubleshooting should follow the system’s safety procedures because the CPU is part of a safety-related control system.

6. How should the F60 CPU 01 be installed in an HIMatrix F60 system?

The CPU 01 is installed in the designated CPU position of the HIMatrix F60 rack, directly next to the power supply module. Before installation, the system should be de-energized and appropriate ESD precautions should be taken. The module should be correctly seated in the rack and secured according to the manufacturer’s installation procedure. After physical installation, the communication connections, fieldbus interfaces, power supply, and associated I/O modules should be checked. The controller can then be configured using the appropriate programming tool. Before placing the system into normal operation, the complete configuration and diagnostic status should be verified.

7. What safety functions are associated with the F60 CPU 01?

The CPU 01 is designed for safety-related applications within the HIMatrix F60 platform. It continuously monitors the execution of the operating system and user program, performs internal hardware and software checks, and monitors important operating conditions. The module is certified for safety-related applications up to SIL 3, Cat. 4 and PL e under applicable standards and configurations. The actual safety capability of a complete installation depends on the complete system architecture, application program, I/O modules, field devices, configuration, and safety requirements. Therefore, the CPU should always be evaluated as part of the complete safety system rather than as an isolated component.

8. What are the common causes of communication problems with the F60 CPU 01?

Communication problems can be caused by incorrect Ethernet configuration, damaged network cables, incorrect fieldbus settings, incompatible fieldbus modules, incorrect addressing, or configuration mismatches between the controller and connected equipment. For Ethernet communication, the RJ-45 connections, network configuration, IP parameters, and link status should be checked first. For fieldbus communication, the corresponding FB1 or FB2 interface, installed fieldbus submodule, station configuration, and communication parameters should be verified. If communication is available but data exchange is unreliable, diagnostic information from the programming environment should be reviewed. Checking the physical connections first and then moving through the configuration and software layers is an effective way to isolate communication faults.