Datasheet

Modbus TCP Communication HIMA H41q/H51q ↔

↔↔

↔ Emerson DeltaV

Definition of the H41q/H51q´s IP Address:

The IP address of an H41q/H51q safety PES is defined through its resource name in ELOP II and

consists of two subsequent addresses in network 192.168.0.x. The resource name must have eight

alphanumeric characters and mustn’t contain any spaces. For IP addressing the last two characters

must be numbers. When you take XXXXXXnn as a resource name X represents an alphanumeric

character and n represents a single digit number. The IP address of a communication module next to

CPU 1 (channel 1) is calculated as (2•nn+1) while the IP address of a communication module next to

CPU 2 (channel 2) is calculated as (2•nn+2). Valid resource names as example and corresponding IP

addresses are listed in Table 2.1.

Resource Name IP Address ch1 IP Address ch2

Burner01

192.168.0.3 192.168.0.4

V40a__02

192.168.0.5 192.168.0.6

H41qX_04

192.168.0.9 192.168.0.10

vessel05

192.168.0.11 192.168.0.12

Table 2.1: Example of IP address calculation

Declaration of BUSCOM data:

Each variable of type “VAR” or “VAR GLOBAL“ which is listed in the variable list can be communicated

via the standard communication protocols of H41q/H51q (Modbus via RS-485, Modbus TCP, Profibus

DP and OPC DA). Binary variables can also be defined as “Events” and can be transmitted via OPC

A&E. These BUSCOM declarations are the same for all communication protocols so exchanging

protocols needs no additional effort besides exchange of the communication module if required.

The declaration of BUSCOM variables and events takes place in the Variable Declaration dialog which

is available through double clicking the desired variable or selection of the appropriate tab when

creating a new variable.

Figure 2.3: Declaration of BUSCOM variables and events

Boolean, Integer and Real variables can be declared as Export, Import or Import/Export beneath the

“BUSCOM” tab of the Variable Declaration dialog. If necessary you can also declare specific

addresses under which the data should be communicated. When not specified the variables

addresses are automatically assigned by ELOP II during compilation. As preparation for Modbus TCP

communication you should define fixed addresses to your communication variables to keep track of

your used communication address space.