Archives

Response in the Event of a Fault

If faults occur, the module enters the temporary STOP_ERROR state. The module is then

rebooted and restarted from the INIT state.

No process data is exchanged with external communication partners in the STOP_ERROR

state. No process data is transferred to the process module.

Scope of Delivery

To operate, the module must be installed on a matching connector board. The connector board

is described in Chapter 3.7.

The connector board is not included within the scope of delivery of the module.

The module can be equipped with fieldbus submodules ex-factory. The specifications are made

with the order using the module’s part number; refer to the communication manual for more

details (HI 801 101 E).

Processor System

The processor system uses self-tests to control and monitor communication. Data is exchanged

between communication and processor modules via the redundant system bus. The system bus

has a redundant structure for reasons of availability. Redundancy is only ensured if both system

bus modules are inserted in the base plates and configured accordingly.

The operating system and the error code history are stored in a non-volatile memory and can be

read in SILworX via the diagnostics

Replacement and Compatibility

An X‑COM 01 E module has more memory capacity than an X-COM 01 module. This is a

prerequisite for new protocols such as the PROFINET IO Controller V2.4+.

An X‑COM 01 E module can replace an X-COM 01 module installed in an existing system. To

ensure compatibility, observe the following points:

▪ The new X-COM 01 E module must be equipped with the same fieldbus submodules used

for the X-COM 01 module to replace.

▪ The X-COM 01 E operating system supports all protocols that were operated in the X-COM

01 module. Exception: PROFINET IO Controller V2.2. see Chapter 3.1.1.

▪ The existing X-CB 001 02 connector board can continue to be used with an X‑COM 01 E

module for all protocols. Exception: PROFINET IO Controller V2.4+.

▪ When using the PROFINET IO Controller V2.4+ protocol, the X-CB 001 04 connector board

is to be used instead of the X-CB 001 02 connector board.

Downgrade

If the PROFINET IO V2.2 protocol is to be used in an X‑COM 01 E module, then downgrade the

X‑COM 01 E module to an X-COM 01 operating system ≤ V14.12.

Refer to the maintenance manual for details on how to load operating systems.

Product Description

The X‑COM 01 E communication module is intended for use in the programmable electronic

system (PES) HIMax.

The module can be inserted into any of the base plate slots with the exception of the slots

reserved for system bus modules. Refer to the system manual (HI 801 001 E) for details.

The module is approved for use in the safety-related HIMax system and can be employed to

transport safety-related protocols.

The module ensures communication with systems via Ethernet and fieldbus interfaces with

SafeEthernet and diverse standard protocols.

Safety Function

No safety function is performed by the communication module.

Response in the Event of a Fault

If faults occur, the module enters the temporary STOP_ERROR state. The module is then

rebooted and restarted from the INIT state.

No process data is exchanged with external communication partners in the STOP_ERROR

state. No process data is transferred to the process module.

Hardware Features

• The 32-channel HART module can have a HIMax baseplate inserted

in any of the slots, with the exception of the slot reserved for the system

bus module.

• The module can be combined with analog input or output modules in

a mono or redundant design by using connector boards.

• HART communication for up to 3200 I/Os per HIMax system (calculated

based on HIMax performance:

100 I/O modules + 100 X-HART modules x 32 field instruments)

HIMax HART Package

• Import data for predefined HART variables + CUT LDB

• Predefined library of modules for all standard HART commands – 15

implemented commands

• Simple base for building your own command modules on the application

level, including possibility for command sequences

HIMax HART Data Tunneling

• HART data is transmitted from the X-HART modules via the internal system

bus to the assigned X-COM module.

• From the X-COM module, HART data is transferred via HART over IP Protocol

version 7 (IPv7) to the asset management system or the HART OPC server.

Benefits

• Less engineering required

• Faster commissioning

• Less maintenance required

• Additional trend information

• And more…

Supported Asset

Management Systems

• PACTWARE

• FIELDCARE

• Honeywell FDM

• Yokogawa FieldMate

• Others available on request

Transform Standard Diagnostic Data into Valuable Information

The HIMax HART solution from HIMA enables plant operators

to use diagnostic data captured by field devices for the asset

management system. Unauthorized changes to the devices are

recognized and prevented by write protection.

This particularly reduces the potential danger of cyber attacks.

The solution comprises the HIMax X-HART 32 01 module and

the HIMax HART package. The software bundle enables usage

of HART data in the application program, supplies a predefined

library of functions, and can be extended with your own libraries.

Specific commands from any device manufacturer can be

quickly implemented. This makes particularly complicated

tasks, such as evaluations and reports, significantly easier.

Even complex command sequences can be mapped.

Standards/Certificates/SIL Design

• TÜV certified up to SIL 3 (IEC 61508. IEC 61511. IEC 62061)

• Write protection can be deactivated for parameter adjustment

by module

• Deactivation of HART communication per channel