System manual

TEM Evolution System

Data Exchange via Serial Communication Interface Description

Fieldbus Interface Modbus RTU

Release 2.01.00

Last revised on: 2010-02-09

Docu-ID: ModbusRTU-090210EN-CPU-P_CAT

We reserve the right to make technical alterations to the drawings and particulars in this documentation
package, if this should become necessary to improve the engines. Reprints and duplication of any kind, ei-
ther in whole or in part, require or written permission.
This is the translation of the German original document. In case of dispute the German original version will
be taken as a reference.
 Systemhandbuch

This document applies to the following gas engines:

Series
CG132
CG170
CG260

Impressum:
MWM GmbH
Servicedokumentation
Carl-Benz-Str. 1
68167 Mannheim
Deutschland
Tel.: +49 621 384-0
Fax: +49 621 384-8841
www.mwm.net
Printed in Germany
Alle Rechte vorbehalten
Release 2.00.00

© ModbusRTU-090210EN-CPU-P_CAT
 TEM Evolution System

Contents

Contents

Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Validity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1 Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Intended Use . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Safety Instructions . . . . . . . . . . . . . . . . . . . . . 5
1.3 Symbol Explanation . . . . . . . . . . . . . . . . . . . . . 6

2 Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1 Protocol and Supported Functions of the
Modbus RTU interface . . . . . . . . . . . . . . . . . . . 7
2.2 Physical Interface . . . . . . . . . . . . . . . . . . . . . . 7

3 Modbus Functions . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1 Modbus Protocol . . . . . . . . . . . . . . . . . . . . . . 8
3.2 Communication Error. . . . . . . . . . . . . . . . . . . . 9
3.2.1 Exception codes . . . . . . . . . . . . . . . . . . . . . . 9
3.3 Modbus Addresses . . . . . . . . . . . . . . . . . . . . . 10
3.4 Fieldbus Register . . . . . . . . . . . . . . . . . . . . . . 10
3.5 Supported Modbus Functions. . . . . . . . . . . . . . . . 11

4 Modbus Functionality TEM-Evo System. . . . . . . . . . . . . . 12

4.1 List of Addresses of the Process Data . . . . . . . . . . . 12
4.2 Data and Commands . . . . . . . . . . . . . . . . . . . . 14
4.2.1 Command Data Words . . . . . . . . . . . . . . . . . . . 14
4.2.2 Performance Standard . . . . . . . . . . . . . . . . . . . 14
4.2.3 Remote Acknowledgement . . . . . . . . . . . . . . . . . 15

5 Query of State Information . . . . . . . . . . . . . . . . . . . . . 16

5.1 State of the Genset . . . . . . . . . . . . . . . . . . . . . 16
5.2 Power Reduction . . . . . . . . . . . . . . . . . . . . . . 16
5.3 Alarm, Fault, Fault SC . . . . . . . . . . . . . . . . . . . 16
5.3.1 Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.3.2 Faults with Controlled Shutdown . . . . . . . . . . . . . . 17

6 Data Format in Tables . . . . . . . . . . . . . . . . . . . . . . . 18

6.1 Word Information . . . . . . . . . . . . . . . . . . . . . . 18
6.2 Logic Information . . . . . . . . . . . . . . . . . . . . . . 19
6.3 Data and Commands . . . . . . . . . . . . . . . . . . . . 20

© ModbusRTU-090210EN-CPU-P_CAT Seite 3
 TEM Evolution System

Validity

This Manual is part of a commission-specific documentation comprising two

parts.
• Interface description: general part
Specification of the interface and explanation of the Modbus functioning in
the TEM-Evo-System
• Appendix A: commission-specific part
Description of commission-specific telegram data of the engine and its pe-
riphery

Note
This description of the interface is only complete and valid
together with the respective commissions-specific Appendix.

© ModbusRTU-090210EN-CPUP_CAT Seite 4
 TEM Evolution System

Safety

1 Safety

1.1 Intended Use

The Modbus RTU interface is a fieldbus interface.
This interface serves for the communication of the TEM-Evo System with a su-
perior site control via Modbus protocol. The superior site control requests via
commands e. g. data and measured values, that are collected by the TEM-Evo-
System.
see »Modbus Functions« on page 8

Information

 For detailed information concerning the Modbus functions refer

to www.modbus-ida.org.

1.2 Safety Instructions

Further documents During the operation of TEM-Evo-Systems the following additional documents
must be observed:
• Manufacturer‘s documentation concerning the genset
• Manufacturer‘s documentation of the plant
• Operating instructions of the TEM-Evo-System
• Provisions of the regulatory authorities and professional associations
Personnel The operation of a TEM-Evo-System requires comprehensive knowledge of the
design, function and operation method of the entire plant. Inappropriate inter-
vention may jeopardize the reliable and safe operation of the plant or cause
damage to the plant.
Thus only a skilled and accordingly trained personnel must be charged with the
installation and operation of TEM-Evo-Systems.

© ModbusRTU-090210EN-CPUP_CAT Seite 5
 TEM Evolution System

Safety

1.3 Symbol Explanation

Symbol Meaning Explanation

Safety You will find this symbol at all safety instructions.

Observe these notes carefully.
Give safety instructions to the operating personnel.

Note Important note concerning functioning.

Disregarding can lead to malfunctions.

Information Further information. Read carefully the indicated system manuals.


 Precondition Preconditions are marked by a tick.
They must be fulfilled before any actions may be carried out.

 Instruction Instructions are marked by an arrow.

Observe these instructions carefully.

Result Normally an instruction is followed by one or more results.

© ModbusRTU-090210EN-CPUP_CAT Seite 6
 TEM Evolution System

Specification

2 Specification

2.1 Protocol and Supported Functions of the Modbus

RTU interface
• Fieldbus type: Modbus RTU
• Supported Modbus functions: 2, 3, 4, 6, 16

2.2 Physical Interface

• Transfer medium: RS-485 in bus topology
• Cable: shielded copper cable consisting of a twisted pair of cables
• Connection:
- Terminal strip in the TEM-Evo genset cabinet, terminal assignment de-
scribed in commission-specific wiring diagram
- interface HOST on the CPU-P Comm-adaptor
• Activation of the communication via Modbus RTU is carried out via Oper-
ating PC Software Package
- Parameter »26001 Fieldbus type«: setting »2«
• Definition of the Modbus RTU interface:
- Parameter »26020 Modbus slave address«
- Parameter »26021 Modbus baud rate«
- Parameter »26022 Modbus communication format«

Note concerning the termination

The RS-485 interface standard specifies a termination of the
conductors (of the bus system) on the two ends of the transmis-
sion network. The termination prevents reflexions into the cable.
In the TEM-Evo System termination occurs via bridge in the ter-
minal strip (see commission-specific wiring diagram).
In the TEM-Evo System for the Modbus RTU a specified idle
state is required, as long as no data transmitter is active. For this
purpose, on at least one point of the bus a bias must be applied
on the data line. This may be performed by means of external
pull up or pull down resistors.

Information

 For further information with regard to the termination refer to:

http://www.modbus.org/docs/Modbus_over_serial_line_V1
_02.pdf

© ModbusRTU-090210EN-CPUP_CAT Seite 7
 TEM Evolution System

Modbus Functions

3 Modbus Functions

Information

 For detailed information concerning the Modbus functions refer

to www.modbus-ida.org.

3.1 Modbus Protocol

The Modbus protocol is a communication protocol basing on a master/slave ar-
chitecture. The bus consists of one »master« and several »slaves« (max. 247).
The communication is exclusively controlled via the »master«, the »slaves« ex-
ecute the instructions.
Communication Modbus RTU disposes of two basical communication mechanisms:
mechanisms
• Query/reply (polling):
The »master« emits a query telegramme to any »slave« and waits for the
answer.
• Broadcast:
The »master« emits a command to all the »slaves« within the bus, this or-
der is executed by the slaves without a feedback.
TEM-Evo System in the In a Modbus architecture the TEM-Evo System always acts as a »slave«, the
Modbus architecture superior site control is the »master«.
Modbus RTU A telegram in Modbus RTU format comprises:
• Address field
• Functional field
• Data field
• Check sum field
Between 2 consecutive telegrams a pause must follow of at least the 3.5 fold
length of the signs.
When a pause within the telegram exceeds the length of 1.4 signs, the opened
message is revoked.

© ModbusRTU-090210EN-CPUP_CAT Seite 8
 TEM Evolution System

Modbus Functions

3.2 Communication Error

Normal communication When the »master« addresses a certain »slave« an answer is expected. Usu-
ally the »slave« sends a reply message.
Disturbed communica- The causes for communication errors and the possible reactions of the »slave«
tion are shown in Table 1:

Fault Reaction of the »slave«

The »slave« cannot receive the query telegram. No response

The »slave« receives the query telegram with a No response

communication error (parity, CRC).

When receiving the query telegram the »slave« The »slave« sends an
is not in a position to answer (e.g. reading a not exception code.
existent register). see »Exception codes« on
page 9

Table 1: Communication errors between »master« and »slave«

3.2.1 Exception codes

The »slave« transmits an exception code to the »master« in case that a com-
mand or a query cannot be answered. The cause for the communication error
is communicated to the »master« in encrypted form.
The following exception codes are supported:

CODE Designation Description

01 »Impermissible The functional code that was received

function« together with the query represents an
impermissible action to the »slave«.

02 »Impermissible data The data address in the query is

address« regarded by the slave unit as an imper-
missible or unknown address.

03 »Impermissible data A value in the query data field is an

value« impermissible value for the slave unit.

04 »Unit fault« During treatment of the message an

error occured.
The query telegram does not conform to
the Modbus specification.

Table 2: Exception codes

© ModbusRTU-090210EN-CPUP_CAT Seite 9
 TEM Evolution System

Modbus Functions

3.3 Modbus Addresses

The address field of a Modbus telegram comprises 1 byte.
The »master« approaches a certain »slave« by inserting the 8-bit slave address
number in the address field of the query telegram. The »slave«, inserts this
(slave number) 8-bit address in the address field of the reply message. Thus the
»master« may recognize the »slave« that is sending the reply.
Address range The valid addresses are in the range from 1 to 247.
Address 0 The address »0« is reserved as a broadcast address. It may be recognized by
all the »slaves« within a network.

Note
The »slave« does not send any reply to a broadcast message.

3.4 Fieldbus Register

Modbus units (»slaves«) store the measured values, set values and status in-
formation in fieldbus registers, thus allowing for the access to this information.
Via Modbus functions the »master« accesses the fieldbus registers in order to
monitor, configurate and control the individual »slaves«.
As per Modbus convention fieldbus registers are gathered in groups (depending
on reference types). The reference type is identified by the first figure of the ref-
erence address.

Reference Function Function in the TEM-Evo System

0xxxx Coil state Reading digital data

1xxxx Input state Reading digital data

3xxxx Input register Reading analogue data

4xxxx Holding register Reading/writing analogue data

Table 3: Reference types (as per Modbus addresses) and their

functionality in the TEM-Evo System

Note
The "x" behind the first sign represents a four digit addressee in
the user data memory.

© ModbusRTU-090210EN-CPUP_CAT Seite 10
 TEM Evolution System

Modbus Functions

3.5 Supported Modbus Functions

The Modbus RTU interface of the TEM-Evo System supports the following func-
tions:

Functional code Function Reference

02 (02H) Read discrete inputs 1xxxx

03 (03H) Read Holding Register 4xxxx

04 (04H) Read input Registers 3xxxx

06 (06H) Write single register 4xxxx

16 (10H) Write multiple registers 4xxxx

Table 4: Supported Modbus functions

© ModbusRTU-090210EN-CPUP_CAT Seite 11
 TEM Evolution System

Modbus Functionality TEM-Evo System

4 Modbus Functionality TEM-Evo System

4.1 List of Addresses of the Process Data

The following table shows the preferred address ranges of the Modbus ad-
dresses with the respective function codes for the TEM-Evo System.
Modbus RTU master, that do not support the defined address ranges are able
to access the process data of the TEM-Evo System via alternative addresses.
The preferred address ranges are shown with bold types.
The complete lists of addresses for the preferred address ranges are ordered
by subjects and stated in the commission-specific Appendix A.

Functional Code Preferred Alternative

Modbus address Modbus address1

Start End Start End

Logic information 2 (Read discrete inputs) 10001 11024 40001 40064

(messages,
alarms, faults,
fault SC)

Word information 4 (Read input registers) 30201 30712 40201 40712

Data and 3 (Read holding register) 41025 41036

Commands 6 (Write single register)
16 (Write multiple registers)

1) only with function code 3 (Read holding Register)

Table 5: Address ranges of the Modbus addresses

Note
Queries for undefined information (e.g. reading of a not existing
coil or register) are followed by an error telegram.
see »Communication Error« on page 9
Queries for defined information that is not described in this
document are reserved for internal purpose, only. They can
adopt values that are not equal to zero. These information
points must be ignored.

© ModbusRTU-090210EN-CPUP_CAT Seite 12
 TEM Evolution System

Modbus Functionality TEM-Evo System

16-bit values When accessing bit values as 16-bit values the bits are stored in the words in
ascending order.
To write set values and commands is only posssible via the 4xxxx addresses.

MSB LSB
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Address 10016 10009 10008 10001
1xxxxx
Address Register 40001
4xxxxx

© ModbusRTU-090210EN-CPUP_CAT Seite 13
 TEM Evolution System

Modbus Functionality TEM-Evo System

4.2 Data and Commands

4.2.1 Command Data Words

Only the following command data words can be used:
• 10E1h(4321d)
• 0FA0h(4000d)
All the other values are ignored by the TEM-Evo System.

4.2.2 Performance Standard

The TEM-Evo System distinguishes three types of performance standard for
the genset (types of demand). With type of demand »Serial« the performance
standard is set via Modbus interface.
The following conditions must be fulfilled:
• Parameter »13010 Type of demand« is set to value »3«.
• The system control sends as a set power of the genset a value that is high-
er than 30 % of the rated power.
• The system control closes the potential-free »Demand« contact.

Note
If the genset must be started exclusively via the Modbus
interface, the »Demand« contact may be bridged.

© ModbusRTU-090210EN-CPUP_CAT Seite 14
 TEM Evolution System

Modbus Functionality TEM-Evo System

4.2.3 Remote Acknowledgement

All alarms and some faults can be remotely acknowledged by the site control.

Note
Pending faults or alarms cannot be remotely acknowledged.

Command data word As a command data word of the remote control the following is defined for the
TEM-Evo System:
• 10E1h: set

Note
A continuous transmission of the value 10E1h does not lead to
further acknowledgements. Only after transmission of a value
that is not equal to 10E1h, a new acknowledgement can be
released (edge triggering).

Register
remote acknowledge-
Modbus Instruction/set value
ment
41030 Remote acknowledgement fault, fault SC, alarm

Faults Faults that may be remotely controlled are mentioned in the list of faults under
column »FQ«.
• »X«: The fault may be undefinetly remotely acknowledged.
• »10h«: The fault may be remotely acknowledged once within 10 hours.

© ModbusRTU-090210EN-CPUP_CAT Seite 15
 TEM Evolution System

Query of State Information

5 Query of State Information

5.1 State of the Genset

The state of a genset may be queried via the following Modbus addresses:
Modbus addresses • Modbus address »30279« State of the genset
»30279« and »30280« • Modbus address »30280« State of the genset with dual gas operation (op-
tional)

5.2 Power Reduction

Modbus address In different situations the TEM-Evo System restricts the maximum power of the
»30230« genset to a defined value. This value may be queried via the following Modbus
address:
• Modbus address »30230«
Maximum permissible power of the genset, with a power reduction by the
TEM-Evo System.

5.3 Alarm, Fault, Fault SC

Information concerning an existent alarm, fault or fault SC may be queried via
the following Modbus RTU addresses.

Note
The meaning of the feedback is inverted.
• FALSE: An alarm, fault, fault SC is applied.
• TRUE: No alarm, fault, fault SC is applied.

Modbus Meaning

10027 Collective fault SC (controlled shutdown active)

10028 Collective alarm (at least one alarm is active)

10029 Collective fault (genset shuts off)

Table 6: State query alarm, fault, SC fault

5.3.1 Faults
Modbus address When a SC fault is existent this is signalled to the SCADA system via Modbus
»10029« address »10029«.
With an active event of the type »fault« the genset is immediately shut off.
The state of the genset switches to »fault« state

© ModbusRTU-090210EN-CPUP_CAT Seite 16
 TEM Evolution System

Query of State Information

5.3.2 Faults with Controlled Shutdown

Modbus address When a SC fault is existent this is signalled to the SCADA system via Modbus
»10027« address »10027«.
With an active event of type » SC fault« the genset is shut down with a delay
via load ramp.
The state of the genset turns first to state »Shutdown due to SC fault«.
Modbus address The remaining time until the power is reduced can be requested via Modbus ad-
»30347« dress »30347«.

Modbus address Meaning

»30347«

-1 No event of type »SC fault«

>0 Remaining time until the power is decreased

0 Genset is shut down or stopped

Table 7: Feedback of time until controlled shutdown is performed via

Modbus address »30347«
After shutdown of the load the genset switches off with »fault« state.

© ModbusRTU-090210EN-CPUP_CAT Seite 17
 TEM Evolution System

Data Format in Tables

6 Data Format in Tables

6.1 Word Information

Word information such as measured values or similar variables are transmitted
as integral numbers of 16 bit with signs. Each value is stored right-aligned in the
word. The superior byte is transmitted before the inferior byte.
The list of the word information in the commission-specific Appendix A compris-
es 4 columns with the following meaning:

Column Designation Meaning

Column 1 »Modbus« Modbus address

Column 2 »Factor« Scaling of the size

Column 3 »Unit« Unit of the size

Column 4 »Designation« Designation of the word information

Table 8: Explanation of table word information

Calculation of the data The value of a data word is calculated as follows:
word
• Value = factor x data word

Note
Word information which is defined but not used or required is
reserved for internal purposes and may adopt non-zero values.
These information points must be ignored.

© ModbusRTU-090210EN-CPUP_CAT Seite 18
 TEM Evolution System

Data Format in Tables

6.2 Logic Information

The lists of the messages and alarms in the commission-specific Appendix A
comprises 5 columns.
In the list of the faults there is provided an additional column 6.

Column Designation Meaning

Column 1 »Modbus« Modbus address

Column 2 »Type« Message, alarm, fault or SC fault

Column 3 »Logic 0« Meaning of logic 0

Column 4 »Logic 1« Meaning of logic 1

Column 5 »Designation« Designation of the logic information

Column 6 »FQ« Faults that may be remotely acknowl-

edged see
see Chapter »Remote Acknowl-
edgement« on page 15

Table 9: Explanation of table logic information

Note
Parameterisable messages and limit value monitoring of the
parameterisable measured values and control circuits may be
set in the TEM-Evo System as a message, alarm or fault.

Note
Logic information which is defined but not used or required is
reserved for internal purposes and may adopt non-zero values.
These information points must be ignored.

© ModbusRTU-090210EN-CPUP_CAT Seite 19
 TEM Evolution System

Data Format in Tables

6.3 Data and Commands

The list of data and commands in the commission-specific Appendix comprises
five columns.

Column Designation Meaning

Column 1 »Modbus« Modbus address

Column 2 »Designation« Designation of the value or command

Column 3 »Factor« Scaling of the variable

Column 4 »Unit« Unit of the variable

Column 5 »Meaning« Assignment of the command data

word

Table 10: Explanation of the data and commands table

© ModbusRTU-090210EN-CPUP_CAT Seite 20