BVH2474 GB

INTECONT® Tersus
Data Communication
BV-H2474 GB
PASS - A service you can count on. Fast, comprehensive and anywhere in the world.
Quality and reliability are the cornerstones of our corporate philosophy. That is why we consider a comprehensive service concept
simply par for the course, from strict quality control, installation and commissioning through to seamless support across the entire life
cycle of our products.
With over 30 service stations and over 180 service specialists, you can count on us to be there whenever and wherever you need us.
During business hours, our service specialists from all business areas are ready to analyze problems and find the reasons for failures.
You can find the Schenck Process location nearest to you on our website www.schenckprocess.com.
If you are looking for individualized and tailor-made service solutions, Then our modular PASS service system is just right for you. It
includes the entire range of services from simple inspections all the way down to a complete service programme. Further information
can be found at www.schenckprocess.com.
Heavy Advisory Service about Spare Parts, Maintenance

Cement, Gypsum, Sand & Gravel, Steel and NF-Metals and Components
Coal-Fired Power Plants and related Industry T: +49 6151 1531-3328
T: +49 6151 1531-3138 [email protected]
F: +49 6151-1531-1423
Logistical and Industrial Scales

Railways and Roads
T: +49 6151 1531-2448
F: +49 6151 1531-1423
24h Hotline: +49 172 650 1700

[email protected]
Light
Chemistry, plastics, foodstuffs and pharmaceuticals
T: +49 6151 1531-3138
F: +49 6151 1531-1423
24h Hotline: +49 171 225 1195
[email protected]
Individual phone consulting - fee required

(Mo. - Fr., 8.00 – 17.00 CET)
© by Schenck Process GmbH, Pallaswiesenstraße 100, 64293 Darmstadt, Germany

Phone: +49 6151 1531-0 ; www.schenckprocess.com
All rights reserved. This documentation or excerpts thereof may not be reproduced in any form without prior written permission by
Schenck Process GmbH. Subject to change without prior notice.
Note: The original manual is in German. This is a translation.
(63050395179714059 V8, 01/12/2015)

Table of Contents
Table of Contents
1 Overview.....................................................................................................................................................1
2 Safety Instructions ....................................................................................................................................3

2.1 Signal Words ..........................................................................................................................................4
2.1.1 Signal Words for Danger Warnings ...............................................................................................4
2.1.2 Signal Words for Usage Instructions ..............................................................................................5
2.2 Five Safety Rules of Electrical Engineering ...........................................................................................5
2.3 Damaged/Defective Electrical Components ...........................................................................................6
3 Database.....................................................................................................................................................7
3.1 General Information ................................................................................................................................7
3.1.1 Data Segments ..............................................................................................................................7
3.1.2 Data Types (Numerical Notation) ...................................................................................................8
3.1.3 IDs (Identifiers) ...............................................................................................................................9
3.1.4 Dimensions...................................................................................................................................10
3.1.5 Highest priority event ...................................................................................................................10
3.1.6 Illustration of the Telegram Bytes on Command ..........................................................................12
3.2 Payload Structure .................................................................................................................................14
3.2.1 Simplified Payload Structure (FIXED Mode) ................................................................................14
3.2.1.1 General Information .....................................................................................................................14
3.2.1.2 Payload Range and Content FIXED Mode ..................................................................................15
3.2.1.3 Example of 'FIXED Mode' Telegram (FIXED_8_8) ......................................................................20
3.2.2 General Payload Structure (VARIABLE Mode)............................................................................21
3.2.2.1 General Information .....................................................................................................................22
3.2.2.2 Payload Range and Content VARIABLE Mode ...........................................................................23
3.2.2.3 Telegram Structure (Variable Payload) ........................................................................................24
3.2.2.4 Parameter Transmission ..............................................................................................................30
3.2.2.5 Example Telegrams 'Variable Mode' ...........................................................................................32
3.3 Available Data - List ..............................................................................................................................36
3.3.1 Cyclical Data Exchange ...............................................................................................................36
3.3.1.1 Default Values ..............................................................................................................................37
3.3.1.2 Read Values .................................................................................................................................42
3.3.2 Events - Overview ........................................................................................................................82
4 Fieldbus Connections ............................................................................................................................ 89

4.1 PROFIBUS DP .....................................................................................................................................89
4.1.1 Guidelines for Commissioning .....................................................................................................89
4.1.2 Functionality of the PROFIBUS Connection ................................................................................90
4.1.3 Configuration of the PROFIBUS Connection ...............................................................................90
4.1.3.1 Settings at the PROFIBUS Slave .................................................................................................91
4.1.3.2 Settings at the PROFIBUS Master (PCS) ....................................................................................92
4.1.4 PROFIBUS Module VPB8020 ......................................................................................................98
4.1.5 Acyclical Data PROFIBUS .........................................................................................................100
4.1.6 Supplementary Documentation ..................................................................................................101
4.2 DeviceNet ...........................................................................................................................................102
4.2.1 Guidelines for Commissioning ...................................................................................................102
4.2.2 Functionality of the DeviceNet Connection ................................................................................102
4.2.3 Configuration of the DeviceNet Connection ...............................................................................103
4.2.3.1 DeviceNet Slave Settings...........................................................................................................103
4.2.3.2 DeviceNet Master Settings (PCS) ..............................................................................................104
INTECONT® Tersus Data Communication, BV-H2474GB, V8

Schenck Process Group -i-
Table of Contents
4.2.4 DeviceNet Module VCB8020 .....................................................................................................105

4.2.5 Acyclical Data (Explicit Messages) DeviceNet...........................................................................107
4.2.7 DeviceNet Module VCB 28020 ..................................................................................................109
4.3 PROFINET IO .....................................................................................................................................111
4.3.1 Guidelines for Commissioning ...................................................................................................111
4.3.2 Functionality of the PROFINET Connection ..............................................................................112
4.3.3 Configuration of the PROFINET Connection .............................................................................112
4.3.3.1 Settings at the PROFINET IO Device ........................................................................................113
4.3.3.2 Settings at the PROFINET IO Controller ...................................................................................114
4.3.4 PROFINET Interface VPN8020 .................................................................................................119
4.3.5 PROFINET interface VPN 8020- network topology ...................................................................122
4.3.6 Acyclic Services .........................................................................................................................125
4.3.6.1 Acyclic Data PROFINET ............................................................................................................126
4.3.7 Supplementary Documentation: .................................................................................................128
4.4 EtherNet/IP .........................................................................................................................................128
4.4.1 Guidelines for Startup ................................................................................................................129
4.4.2 Functionality of the Ethernet Connection ...................................................................................129
4.4.3 Configuration of the Ethernet Connection ..................................................................................129
4.4.3.1 EtherNet/IP Slave Settings.........................................................................................................129
4.4.3.2 Settings at the EtherNet/IP Master (ControlLogix) .....................................................................131
4.4.4 Acyclic Data (Explicit Messages) EtherNet/IP ...........................................................................134
4.4.4.1 Acyclical Data Exchanges between PCS and Weighing Electronics .........................................136
4.5 Modbus (Serial and Network) .............................................................................................................140
4.5.1 General Information ...................................................................................................................140
4.5.1.1 Guidelines for Startup ................................................................................................................141
4.5.1.2 General Telegram Structure.......................................................................................................141
4.5.1.3 Subscriber Addresses ................................................................................................................141
4.5.1.4 Function codes (FC)...................................................................................................................142
4.5.1.5 Fault codes .................................................................................................................................143
4.5.1.6 Data Formats .............................................................................................................................143
4.5.1.7 Safeguarding Transmission .......................................................................................................143
4.5.1.8 Payload ......................................................................................................................................143
4.5.1.9 Examples of Telegrams (Process Values) .................................................................................144
4.5.1.10 Parameters .................................................................................................................................145
4.5.1.11 Acyclical Data (Explicit Messages) Modbus ..............................................................................145
4.5.1.12 Supplementary Documentation ..................................................................................................147
4.5.2 Modbus-TCP ..............................................................................................................................147
4.5.2.1 Functionality of the Modbus-TCP Connection ...........................................................................148
4.5.2.2 Configuration of the Modbus-TCP Connection ..........................................................................148
4.5.2.3 Redundant Modbus-TCP ...........................................................................................................150
4.5.3 Modbus-RTU ..............................................................................................................................151
4.5.3.1 General Information ...................................................................................................................151
4.5.3.2 Functionality of the Modbus-RTU Connection ...........................................................................151
4.5.3.3 Configuration of the Modbus-RTU Connection ..........................................................................151
4.5.3.4 Available Data - List ...................................................................................................................153
4.5.3.5 Modbus Module VSS8020 .........................................................................................................154
5 Diagnostics and Troubleshooting ...................................................................................................... 157

5.1 General Information for all Fieldbus Types ........................................................................................157
5.2 Notes for PROFIBUS ..........................................................................................................................157
5.3 Notes for DeviceNet ...........................................................................................................................157
5.4 Notes for PROFINET ..........................................................................................................................158
5.5 Notes for EtherNet/IP .........................................................................................................................158
5.6 Notes for Modbus ...............................................................................................................................158
BV-H2474GB, V8 INTECONT® Tersus Data Communication,

- ii - Schenck Process Group
Table of Contents
5.7 User data diagnosis ............................................................................................................................159
6 Some Examples of Applications ......................................................................................................... 163

6.1 Zeroing and Taring a Beltweigher (Weighfeeder) ..............................................................................163
6.2 Batching per Fieldbus .........................................................................................................................164
7 Appendix ............................................................................................................................................... 167

7.1 Common Abbreviations ......................................................................................................................167
7.2 Abbreviations in the List of Cyclical Data ...........................................................................................167
7.3 Glossary..............................................................................................................................................168
Index ...................................................................................................................................................... 169

Schenck Process Group - iii -
Overview
1 Overview
Who is this manual intended for?
This manual is aimed at the experienced technicians and programmers whose task it is to connect a
®
INTECONT Tersus system (hereinafter referred to also as weighing electronics, scales or device) to an
existing Process Control System (PCS, system controller).
This requires good working knowledge of both systems (collectively referred to as weighing system) and
basic knowledge of data exchanges in local computer networks.
How are both systems connected?

The scales electronics can communicate with the PCS through an optional fieldbus connection. In this con-
figuration the PCS is always the bus master and the scales electronics always the slave.
The following fieldbus types can be used:
▪
1) 1) 1)
'Classic' fieldbus: PROFIBUS DP , DeviceNet and Modbus-RTU
▪
2) 3) 3)
Ethernet based fieldbus (Industrial Ethernet): PROFINET IO , EtherNet/IP and Modbus-TCP
1)
The connection consists of a module fitted to the system unit of the weighing electronics.
2)
It is implemented as a module for performance reasons.
3)
No module required as Ethernet interfaces are included in the standard scope of delivery.
What is described in this manual?

The weighing system makes available a common data model for all protocols. This manual describes in
chapter 'Database' the data model (payload structure) and the data exchange using the various fieldbus
protocols.
Chapter 'Fieldbus Connections' describes in separate subchapters the special properties of each fieldbus
connection.
This is followed by chapter 'Diagnostics and Troubleshooting' with information on each of the fieldbus con-
nections and tips and tricks on avoiding and solving problems.
Chapter 'Example Applications' illustrates fieldbus communication using examples of several typical se-
quences.
Abbreviations and definitions used are explained in chapter 'Appendix'.
Reference is made at several points in this documentation to a Service Tool. This refers to the
software 'Schenck Process EasyServe'.

Schenck Process Group -1-
Overview
Overview of supplementary manuals:
No. Title
BV-H2463 INTECONT Tersus weighfeeder - operating manual
BV-H2464 INTECONT Tersus belt weigher - operating manual
BV-H2465 INTECONT Tersus legal for trade belt weigher - operating manual
BV-H2476 INTECONT Tersus loss-in-weight feeder - operating manual
BV-H2477 INTECONT Tersus MULTICOR - operating manual
BV-H2478 INTECONT Tersus MULTISTREAM - operating manual
BV-H2466AA Weighing processor - Module Description DP-V1
BV-H2473 Step7 Library - CONTI_S7, DISCO_S7, DP-V1, ARM_Controller
BV-H2474 INTECONT Tersus - Data Communication
BV-H2427AA DISOCONT Tersus and INTECONT Tersus, Opus, Satus -

module description for PCS7
BV-H2185 Schenck Process EasyServe - Operating Manual

-2- Schenck Process Group
Safety Instructions
2 Safety Instructions
To avoid personal injury and material damage, follow the safety regulations stated below.
Additionally you should also observe:
▪ Safety information given in order-specific documentation
▪ Safety information relating to mechanical components
▪ Instructions and safety instructions for parts manufactured by third-party suppliers or parts that are not
part of Schenck Process scope of delivery.
When performing installation, commissioning and service work, observe all applicable local regulations.
Intended Use
The supplied system is to be used exclusively for the specified task. Any other use which exceeds this shall
not be considered part of the intended use.
The supplied system may be part of a more complex system. The system operator bears overall responsibil-
ity for the operating safety of the system.
Potential Sources of Danger

Dangers may arise from the machine or from facilities that for example are used in the plant for transport or
feeding if control tasks are taken on by the system.
To avoid dangers the system must correctly be used, operated, monitored and serviced by trained person-
nel. Bear in mind that the system may be part of a more complex plant. It may therefore be necessary to take
more extensive protective measures before working on the plant.
The plant operator is responsible for the safe operation of the plant.
Personnel
Preparation, assembly, commissioning, operation, maintenance and servicing may only be carried out by
qualified personnel.
All persons working on the system are required to observe the safety hints and know the parts of the tech-
nical documentation relevant to their work.
The operating company is responsible for instructing his operators to observe all regulations and instructions
given.
Parameter Changes
The measuring system's functionality is determined by parameters. Only personnel familiar with the device's
mode of operation may alter these parameters (e.g. after training by Schenck Process). Incorrectly set pa-
rameters may cause injury or material damage. if control units are connected. Furthermore they may also
cause considerable disruption to weigh operations.
Password
Passwords safeguard the parameters against unauthorized changes. The measuring system operator has to
ensure that the password is handled responsibly.
Acknowledging Event Messages

Error messages may be acknowledged only after cause of fault has been remedied.

Safety Instructions
Ensure that any connected peripheral devices are functioning correctly before acknowledging an event. Any
connected control systems in particular must be in safe state.
Maintenance and Repair

▪ All warning and instruction signs on the scales must be observed.
▪ The measuring system has to be shut down before working on mechanical equipment or peripheral
systems (control systems in particular). Steps must be taken to ensure the measuring system cannot
be started inadvertently.
▪ Disconnect the power supply before performing work on the electrical equipment (follow your plants
lockout-tagout procedure!).
▪ The devices may be operated only in the housings supplied as there would otherwise be a danger of
coming into contact with live parts.
Moisture and humidity

All scales components, the electrical components in particular, must be protected against moisture and hu-
midity when the housing is open, such as during maintenance and service work. Beyond this, the housing's
protection classes should be complied with.
Design Modifications
If you modify the system or expand it using parts not supplied by Schenck Process, Schenck Process cannot
assume liability for any such modifications. This especially applies to modifications which could affect the
operating safety of the system.
Replacing Components
Spare parts must meet the technical specifications indicated by Schenck Process. To ensure this require-
ment is met, only genuine Schenck Process spare parts should be used. When using other spare parts, the
warranty will be void.
Keeping the Technical Documentation

Keep the technical documentation safe. Hand the technical documentation over to the buyer if the equipment
should be sold on.
2.1 Signal Words
2.1.1 Signal Words for Danger Warnings

Potential dangers will always exist when working with technical devices. Dangers will arise if the machine is
▪ incorrectly installed,
▪ started up incorrectly,
▪ operated by untrained personnel, or
▪ serviced by unqualified personnel.
The following signal words in this manual indicate dangers:
Danger
The signal word DANGER identifies a danger with a high degree of risk that, if not prevented, will cause
grievous injury or death. Follow all instructions to prevent the danger from occurring.

Safety Instructions
Warning
The signal word WARNING identifies a danger with a moderate degree of risk that, if not prevented, may
cause grievous injury or death. Follow all instructions to prevent the danger from occurring.
Caution
The signal word CAUTION identifies a danger with a low degree of risk that, if not prevented, may cause a
minor or moderate injury. Follow all instructions to prevent the danger from occurring.
Format of the Safety Notices
2.1.2 Signal Words for Usage Instructions
Strictly Observe
The signal words STRICTLY OBSERVE identify situations in which material or environmental damage could
occur.
For example:
STRICTLY OBSERVE
Welding on load-bearing parts
Note
The signal word NOTE is used to highlight information on using the product economically and at an optimal
level of efficiency.
Example:
NOTICE
Take note of the measures listed below to rectify malfunctions.

Safety Instructions
2.2 Five Safety Rules of Electrical Engineering

These fives safety rules must be followed in the order shown before work is begun on electrical systems.
Once the work is finished, they are to be applied in reverse order.
DANGER
Electric shock from live components
There is a danger of life from an electric shock.
– Take all possible precautions to ensure safety before work is begun
on live components. Observe, among other things, the following:
1. Disconnect the components.
2. Secure against restart.
3. Ensure that the components have been de-energized.
4. For voltages above 1 kV: Ground and short-circuit cables.
5. Cover or shield adjacent, live components.
2.3 Damaged/Defective Electrical Components
DANGER
Live damaged or defective components
Danger of life from electric shocks.
1. Have trained personnel ensure that all live components are undam-
aged and in proper working order.
2. Have trained personnel replace damaged or defective electrical com-
ponents.

Database
3 Database
3.1 General Information

This manual contains a general description of all data that can be exchanged by means of various fieldbus
protocols between the PCS and the scales electronics. The database is the same for all Fieldbuses. Chapter
'Available Data - List' gives a complete list of the database.
Special features are described in the fieldbus-specific chapter.
3.1.1 Data Segments

The weighing system distinguishes between the following data:
► Cyclic Data (IO data):
The content of the cyclic data exchange is the data that the PCS transmits to the scales electronics (general:
preset values) so that they can be assigned to the outputs and the data that a scales electronics reads in at
its inputs and transmits to the PCS for processing (general: read values). In each cycle therefore a 'cyclical'
data package such as this is sent at regular intervals from the PCS to the weighing electronics and vice-
versa. It contains:
Commands (Bit or byte information)

Preset values (FLOAT format)
Status and event information (Bit or byte information)
Measured values (FLOAT format)
With cyclic data exchanges a further distinction is made between the modes in which the data is transmitted:
▪
*)
FIXED Mode: All information on identifiers and parameters can be ignored.
'
See chapter 'Simplified Payload Structure (FIXED Mode)
*)
No IDs are transmitted in FIXED mode.
▪ VARIABLE Mode: This mode offers flexible methods of structuring the transmission of process data.
See chapter 'General Payload Structure (VARIABLE Mode)'
► Acyclic Data (Explicit Messaging):

There are also acyclic exchanges of data between the PCS and the weighing electronics, used for events
that do not regularly repeat.
Examples of acyclic data exchanges are the transmission of parameterization and configuration data when a
scales electronics starts up, or the transmission during operation of an event message from the weighing
electronics to the PCS:
The parameters
Strings e.g. device name

Database
3.1.2 Data Types (Numerical Notation)

Different data types are exchanged during data transfer.
The following tables show the byte order during transmission. The transmission begins at the
same time as the MSB ('Big Endian' byte order).
Most of the byte strings (telegrams) shown in this manual are based on the assumption that the
byte order has been set as 'Big Endian'. If this should not be the case this will be pointed out
explicitly.
► Floating-point numbers(FLOAT)
Measured values and some parameters are available in the weighing system as single-precision binary float-
ing-point numbers as per the IEEE-754 norm (4 bytes or 32 bits).
This number format is labeled below as FLOAT (often called REAL by controllers).
MSB LSB
Model 1st Byte 2nd Byte 3rd Byte 4th Byte
FLOAT Sign/Exponent Mantissa 1 Mantissa 2 Mantissa 3
Example:
150.5 0x43 0x16 0x80 0x00
A conversion can be made into a different format depending on the parameters and protocol. Further infor-
mation can be found in the descriptions of the individual fieldbus protocols.
Further examples of floating-point numbers

*)
Number IEEE format (hex) Siemens KG format (hex)
1.0 3F 80 00 00 01 40 00 00
10.0 41 20 00 00 04 50 00 00
100.0 42 C8 00 00 07 64 00 00
1000.0 44 7A 00 00 0A 7D 00 00
*)
Used with S5 controllers only
► Integer values (INTEGER)

Data words (INT16) and data double-words (INT32) are transmitted in the so-called 'Motorola format' as
standard (Big Endian, high byte followed by low byte). A different byte order can be set depending on the
protocol and parameters. Further information can be found in the descriptions of the individual fieldbus pro-
tocols.

Database
INT16 0 0 X (MSB) X (LSB)
INT32 (LONG) X (MSB) X X X (LSB)
NOTES:
The existing protocol-dependent parameters Word Sequence and Byte Sequence affect only the transfer of
floating-point numbers and UINT32 parameter values via fieldbus. The standard setting always corresponds
to 'Big Endian'.
All fieldbus protocols can operate with double words, Modbus can also use 16 bit words.
► Bit coded information (BIT)

Bits are compiled together into double words (PROFIBUS DP, DeviceNet, PROFINET IO) or words (Modbus-
RTU/TCP).
MSB LSB
BIT *) Word(x) HI Word(x) LO Word(x+1) HI Word(x+1) LO
Examples
Command ID:
0x0140 Command4 HI Command4 LO Command5 HI Command5 LO
Status ID:
0x02F0 Status2 HI Status2 LO Status3 HI Status3 LO
*) information per bit ('bit coded')
► Character string (STRING)

The following characters are permitted in texts transmitted in ASCII code
Character ASCII code (hex)
Spaces 20
Hyphen - 2D
Point . 2E
Colon : 3A
Digits 0…9 30 … 39
Upper case letters A…Z 41 … 5A
Lower case letters a…z 61 … 7A

Database
3.1.3 IDs (Identifiers)

An ID is a 2 byte identifier that uniquely addresses a 4 byte data block (data double word, DDW).
Type 1st Byte 2nd Byte
ID X (MSB) X (LSB)
*)
The ID determines what information is to be transmitted or requested. The PCS sends this ID to the weigh-
ing electronics and receives the corresponding value in return.
IDs are given in decimal or hexadecimal form, e.g.
decimal: 32 352
hexadecimal: 0x20 0x0160
*)
IDs are always used to address data blocks. However, they are also transmitted in VARIABLE
MODE only, not in FIXED MODE. However, here they can be used to facilitate setting the struc-
ture of the payload (refer to chapter 'Payload Scope and Content FIXED Mode').
3.1.4 Dimensions
The weighing electronics use two systems of units. The parameter Units is used to switch between the two.
For a fieldbus transmission of dimension-related variables, this means:
▪ Setting Metric: Transmit in units m, kg and s (SI units).
▪ Setting English: Transmit in units ft, lb and s (NON-SI units).
3.1.5 Highest priority event

The information 'highest priority event' is transferred bit-coded in Status 52+53 in the first two bytes (sta-
tus 52). The contents of ID 0x0610 / 1552 must be read for this:
MSB LSB
1st Byte 2nd Byte 3rd Byte 4th Byte
Word(x) HI Word(x) LO Word(x+1) HI Word(x+1) LO
Status 52 HI Status 52 LO Status 53 HI Status 53 LO
Conditions: ▪ Event is still pending

▪ Byte order: Big Endian
Status 52 is coded as follows:
Status 52 HI Status 52 LO
Bit: 7 … 4 Bit: 3 … 0 Bit: 7 … 4 Bit: 3 … 0
Ack Class Group Number

- 10 - Schenck Process Group
Database
Codes used (hex/bin):
*)
Ack: Class: Group: Number:
0 / 0000 – NO 1 / 0001 – A 1 / 0001 – SY 0 / 0000 – No. 1

1 / 0001 – YES 2 / 0010 – W1 2 / 0010 – SC 1 / 0001 – No. 2
3 / 0011 – W2 3 / 0011 – WE 2 / 0010 – No. 3
*)
acknowledged 4 / 0100 – IG 4 / 0100 – WM 3 / 0011 – No. 4
5 / 0101 – MF 4 / 0100 – No. 5
6 / 0110 – IL 5 / 0101 – No. 6
7 / 0111 – CO 6 / 0110 – No. 7
8 / 1000 – CH 7 / 0111 – No. 8
9 / 1001 – CA 8 / 1000 – No. 9
A / 1010 – HI 9 / 1001 – No.10
B / 1011 – LO A / 1010 – No.11
B / 1011 – No.12
C / 1100 – No.13
D / 1101 – No.14
E / 1110 – No.15
F / 1111 – No.16
Example of a byte order in a telegram: '13 17 xx xx' (hex)
Ack Class Group Number
0x13 0x17
1 3 1 7
0001 0011 0001 0111
YES W2 SY No. 8
This results in:

'Event SY08 (W2) has been acknowledged'.
Reference to status 53
Status 53 will also always be transferred as the telegram is 4 bytes long (with the exception of Modbus). It
tells (numerically coded) in which parameter the event class for the highest priority event has been deter-
mined.
Bit: 7 … 0 Bit: 7 … 0
Parameter no. Parameter block no.

Schenck Process Group - 11 -
Database
Example of a byte order in a telegram: 'xx xx 03 15' (hex)
Parameter no. Parameter block no.
0x03 0x15
Par. 3 Block 21
This results in:

'The class for the highest priority event has been set in parameter P21.03'.
3.1.6 Illustration of the Telegram Bytes on Command

e.g. DISOCONT Tersus

Database

Database
3.2 Payload Structure

Applies to:
▪ PROFIBUS DP
▪ DeviceNet
▪ PROFINET IO
▪ EtherNet/IP
(for all protocols not based on Modbus)
The use of a fieldbus connection generally requires extensive knowledge and training. However, the entire
available range of options for transferring data is seldom used. A simplified transfer mode (FIXED mode) was
implemented to simplify commissioning and to simultaneously enable data traffic sufficient for most applica-
tions. Therefore, you should decide before using a fieldbus whether you can use it in this 'simplified' mode or
whether you wish to use the more elaborate 'general' mode (VARIABLE mode).
▪ FIXED Mode
In this mode you can ignore all information on identifiers (IDs) and parameters. FIXED mode uses a
*)
limited and static payload structure; parameters cannot be transferred. The information contained in
chapters 'Simplified Payload Structure (FIXED Mode)' 'Diagnostics and Troubleshooting' suffices.
*)
The acyclical services may also be used for this.
▪ VARIABLE Mode
This mode makes all options available to you. A fixed basic content always is transmitted; in order to
receive additional information the PLS must transmit the corresponding IDs.
Some of the basic information on this can be found in chapter 'General Payload Structure (VARIABLE
Mode)'.
3.2.1 Simplified Payload Structure (FIXED Mode)
3.2.1.1 General Information

In FIXED mode, depending on the format selected, specific data are transmitted to specific positions
between the PCS and the weighing electronics. No IDs are transmitted and no parameters can be transmit-
ted. Parameters are used to set the configuration of the contents transmitted.
Several predefined formats that enable the transmission of payload structures of different sizes can be se-
lected. The contents that are transmitted using these structures can easily be altered. You therefore are us-
ing a sort of 'variable FIXED mode'.
The following figure shows the basic structure of the payload for the protocols PROFIBUS DP, DeviceNet,
*)
PROFINET IO and EtherNet/IP on the basis of the formats FIXED_8_8 :

Database
*)
Information on further FIXED formats and on the payload configuration can be found in section 'Payload
Scope and Content in FIXED Mode'.
The figure shows how the data are arranged in the telegram. Each information transmitted consists always of
4 bytes.
A 'preset value' (pres1 ... pres8) is either a command (usually bit-coded) or a numerical value (e.g. setpoint).
A 'read value' (value1 ... value8) is either a status (usually bit-coded) or a numerical value (e. g. measured
value).
The first line represents the telegram from the PCS to the weighing electronics, the second line is the re-
sponse of the weighing electronics.
CAUTION: Bit 3, 'Release', must always be set in preset value 1, (always 'Command 04+05'), as it is
used to monitor the connection.
The following preset values will not be processed and event 'SYxx Event: Cyclic Communica-
tion' will be set if this bit is not set!
3.2.1.2 Payload Range and Content FIXED Mode

(if you are not using the EasyServe service tool you will have to use the list 'Available Data - List').
There are two ways to alter the payload structure. Both the size of the payload telegram and its content can
be adjusted.
A) Selecting a FIXED format
(Condition: Parameter Protocol Type = PROFIBUS DP or DeviceNet or PROFINET IO or EtherNet/IP)
The quantity of payload to be transmitted can be set using the Communication Fieldbus parameter in block
Configuration:

Database
The formats FIXED_8_8 and FIXED_4_4 are available. The size of the payload structure can directly be
read from the format identifier:
In the master you must use the corresponding device master data files (*.gsd for PROFIBUS
DP, *.gsdml for PROFINET IO and *.eds for DeviceNet and EtherNet/IP).
If you have selected a FIXED format you can identify which data will be transmitted to the individual telegram
positions from the Fixed mode configuration block.
The assignment of the individual positions applies to all FIXED formats.

The FIXED_8_8 format transmits the preset values 1-8 and the read values 1-8; FIXED_4_4 transmits the
preset values 1-4 and the read values 1-4.

Database
Displaying parameter assignment

Each parameter has a button that shows the content of the current transmission. The content of the respec-
tive parameter is the ID that addresses this information in the database.
If you move the cursor towards the button and hold it there briefly the ID will appear. It will be shown as a
short help text (yellow) (decimal/hexadecimal and range of possible values), e. g.:
A * symbol in front of a button indicates that the currently active value in this position does not correspond to
the preset value.
B) Adjusting the FIXED format
The fixed mode isn't as 'fixed' as the name suggests. The current assignment of the individual positions can
be adjusted to suit your needs in the 'Fixed mode configuration' block.
IMPORTANT! IMPORTANT! IMPORTANT!

Record any alterations made here at the very latest BEFORE you replace the scales electron-
ics, to ensure that you can set the same payload transmission after replacement.
We recommend that you archive the list of parameters in a file that you can load again at any
time.
Alter a current assignment by pressing the corresponding button; this will call up a list (white area) of all of
the possible settings (IDs). The current assignment is marked and the related functionality will be displayed
to the right of it (yellow area).
The parameter 'ID Preset Value 1' cannot be altered; it is set to Command 04+05 because in it the
bit 3 'Release', that monitors the connection, must always be set. None of the preset values in the
telegram would be processed and event 'SYxx Event: Cyclic Communication' would be set if this bit
were not set.
The following selection list will be shown for all preset values (e. g. with DISOCONT Tersus):

Database
The following selection list will be shown for all read values (e. g. with DISOCONT Tersus):

Database
You can change the parameter by selecting a different ID and confirming with [OK], the label on the button
will have altered correspondingly.
Option '(no value)'
Select entry (no value) if you wish to set a parameter such that it transmits no data. The symbol '- - -' will
appear on the button and the corresponding parameter will be assigned ID = 0. This will transmit 4 zero
bytes at this position in the telegram (00 00 00 00).
Option 'n/a'
This is used for service purposes and is not intended for fieldbus applications. The symbol 'n/a' will appear
on the button.
Displaying or restoring the default settings
The new assignment (modified default settings) of a parameter is depicted by a blue '*' character. If you
move the cursor towards '*' character and hold it there briefly the corresponding default setting will appear.
The value of the default setting is then shown in the form of a short help text (yellow), e. g.
Click the right mouse button and confirm with [OK] if you wish to reset this button to the default settings, e. g.

Database
3.2.1.3 Example of 'FIXED Mode' Telegram (FIXED_8_8)
Assumptions:
Scales type: VLW 20650
Floating point numbers: FLOAT-Format = IEEE
Payload structure: Configuration = FIXED_8_8
Word and byte sequence: Word Sequence = I:std/L:std
(i.e. 'Big Endian') Byte Sequence = High - Low
Content of telegram: as per the setting in block Fixed mode configuration
Master → Slave: 32 byte
Master ← Slave: 32 byte

Database
Master → Slave
**)
Bytes Meaning ID Command or
(Default values) (hex) (dec/hex) default value
*)
1: Byte 1-4 00 0C 00 00 Command 04+05 320 / 0x0140 'Clear Events' and 'Release'
*)
2: Byte 5-8 00 00 00 00 Command 06+07 352 / 0x0160 (No command active)
*)
3: Byte 9-12 00 00 00 01 Command 08+09 384 / 0x0180 'Start Keyboard Mode'
4: Byte 13-16 42 C8 00 00 Serial Setpoint 592 / 0x0250 100 kg/h
5: Byte 17-20 43 C8 00 00 Serial Batch Setpoint 594 / 0x0252 400 kg
6: Byte 21-24 00 00 00 00 --- 0 / 0x0000 n/a
7: Byte 25-28 00 00 00 00 --- 0 / 0x0000 n/a
8: Byte 29-32 00 00 00 00 --- 0 / 0x0000 n/a

*) bit coded
**) ID is not transmitted
Master ← Slave
**)
Bytes Meaning ID Status or
(Read values) (hex) (dec/hex) current value
*)
1: Byte 1-4 00 22 00 00 Status 02+03 752 / 0x02F0 'No Release' and
'Summary Alarm'
*)
2: Byte 5-8 00 00 00 00 Status 04+05 784 / 0x0310 (No bit set)
*)
3: Byte 9-12 13 17 00 00 Status 52+53 1552 / 0x0610 Acknowledged event:
(Highest priority event) SY08, W2
4: Byte 13-16 44 9A 40 00 Feedrate 1872 / 0x0750 1234 kg/h
5: Byte 17-20 42 83 66 66 Totalizer 1 1874 / 0x0752 65.7 kg
6: Byte 21-24 43 AC 80 00 Fill Weight 1888 / 0x0760 345.0 kg
7: Byte 25-28 42 C2 E1 48 Batch Resid. Amount 1898 / 0x076A 97.44 kg
8: Byte 29-32 42 C8 00 00 Setpoint 1894 / 0x0766 100 kg/h

*) bit coded
**) ID is not transmitted

Database
3.2.2 General Payload Structure (VARIABLE Mode)

The data exchange between the master and slaves takes place via the input data field/output data field. The
master writes to the slave output data array and the slave responds by sending the content of its input data
array back to the master. The form of the input data/output data protocol is defined in profiles. The scales
system is based on the structure of the payload of the existing profile 'Alterable-Speed Drives' (3.071
PROFIdrive). The profile determines for the drives the payload structure with which the master can access
the slaves by means of cyclical data transmission.
The telegrams of cyclic data transmission have the basic structure below:
The payload (PPO) form the core. The structure of the payload for the cyclic channel is defined in
PROFIdrive profile version 2.0 and is designated Parameter Process data Object (PPO). Using the PPO, the
master (PCS) accesses the slaves (drives) at cyclic intervals. The PPO is subdivided into two ranges:
▪ PKW area (optional)

Any parameter of the slaves can be monitored and/or altered with the parameter range Parameter
Identifier Value, or 'Parameter Kennung (Identifier) Wert (Value)'. For example, malfunctions or
min/max thresholds can be read out and recipe values can be specified. This allows further infor-
mation for visualization of the scales to be called up from a higher-level system (such as e.g. a PC)
without influencing the performance of the process data transmission.
The PKW range consists of 4 words (8 bytes):

– Parameter Identification, Parameter KEnnung, PKE
– Parameter INDex, IND
– Parameterwert (value) PWE (2 words).
NOTE: There are also PPO types that have no PKW component.

Database
You can find a more detailed description in section 'Parameter Transmission'.
▪ PZD area
Both control words and setpoints (master → slave) and status words and actual values (master ←
slave) can be transmitted in the 'ProZess (Process) Data area (PZD)'. The process data are always
transmitted and are immediately effective. They area used to operate the scales in an automated in-
terlocked facility, e.g. switching on/off, define setpoints etc. As opposed to parameter transmission in
the PKW area in which the parameter to be transmitted is determined in the telegram, the process da-
ta variables to be transmitted in the PZD area are determined by the PPO type or the slave. The
quantity of process data also depends on the PPO type or the slave.
TIP
Deviating from this profile, special PPO types are used for Schenck Process
weighing electronics. These are described in the following chapter.
3.2.2.2 Payload Range and Content VARIABLE Mode

(you will have to use the list 'Available Data - List' if you are not using the service tool 'EasyServe').
There are two ways to alter the payload structure. Both the size of the payload telegram and its content can
be adjusted.
Selecting a VARIABLE format (PPO type)

(Condition: Parameter Protocol Type = PROFIBUS DP or DeviceNet or PROFINET IO or EtherNet/IP)
The quantity of the payload to be transmitted can be influenced by using parameter 'Communication
Fieldbus' in the 'Configuration' block to select a suitable format:
There are several VARIABLE formats available: The size of the payload structure can be calculated directly
from the format identifier:
The values 'Status' (0x02F0) and 'Actual Value' (0x0750) have in VARIABLE mode a set
coding in the telegram and are always returned regardless of the 'order list'. They therefore
are not part of the format identifier but must be incorporated when calculating the telegram
length in bytes.

Database
Format Parameter range Process data range

(PPO type) (PKW) (PZD)
Presets Read value IDs

(ID+Value) ('Order list')
NO_PARA_ID_3_6 (*) without 3 6
PARA_ID_3_6 (*) with 3 6
PARA_ID_2_4 (*) with 2 4
Tab. 1 : VARIABLE formats
(*) These formats are semi-variable, i.e. the payload structure is fixed, but the data content (IDs and val-
ues) are variable.
In the master you must use the corresponding device master data files (*.gsd for PROFIBUS
DP, *.gsdml for PROFINET IO and *.eds for DeviceNet and EtherNet/IP).
3.2.2.3 Telegram Structure (Variable Payload)

The following figures show the basic payload structure in the INTECONT Tersus system. The first line repre-
sents the telegram from the master to the weighing electronics, the second line is the response of the weigh-
ing electronics.
NOTE: The values 'Status' (0x02F0) and 'Actual Value' (0x0750) are additionally always sent from
the scales electronics to the master, regardless of PPO type
Semi-variable PPO type with no parameter range:

Parameter 'Configuration' = 'NO_PARA_ID_3_6'

Database
This PPO type has the following structure
# Item Comment Bytes
NO_PARA - No PKW 0
3 Presets Preset[6] = preset ID [2] + preset value [4] 18
6 Read value IDs Read ID[2] 12
Master → Slave Σ = 30
NO_PARA - No PKW 0
- 2 read values Status[4] and Actual Value[4] (obligatory) 8
6 Read values Read value[4] 24
Master ← Slave Σ = 32
Semi-variable PPO type with parameter range (large):

Parameter 'Configuration' = 'PARA_ID_3_6'
This PPO type has the following structure:
PARA Parameter range PKW [8] 8
3 Defaults Default[6] = default-ID[2] + default-value[4] 18

Database
- 2 read values Status[4] and actual value[4] (obligatory) 8
6 Read Values Read value[4] 24

Database
Semi-variable PPO type with parameter range (small):

Parameter 'Configuration' = 'PARA_ID_2_4'
This PPO type has the following structure:
2 Defaults Default[6] = default-ID[2] + default-value[4] 12
- 2 read values Status[4] and actual value[4] (obligatory) 8
4 Read Values Read value[4] 16
Remarks
▪ The preset value IDs from the master to the scales electronics (preset value 1 ...) must come from the
'Commands' or 'Presets' data segments. Either two setpoints (e.g. setpoint and batch setpoint) or two
commands or, also, setpoints and commands mixed with different IDs can be specified in one cycle.
▪ If a preset value ID is zero, the corresponding value will not be evaluated.
▪ If all bytes have been set to zero in the preset message (bus master to scales electronics), event
'SYxx Event: Cyclic Communication' will be set in the scales. The scales electronics interprets this
state as a failure of the bus master host CPU with a simultaneously active communication processor
in the master. The scales electronics' timeout monitoring cannot trap this state as formally valid data
packets continue to be transmitted. At least one preset value ID therefore must have a valid non-zero
value.

Database
▪ Control and status information are always combined into blocks of 4 bytes (DDW). The IDs assigned
to the blocks are highlighted in bold in the database (e.g. 0x02D0). These IDs only may be used here.
The data will be rejected and an error message sent if a different ID is used.
▪ In the reply telegram, the status and actual values are identified on the basis of their positions in the
telegram. Therefore IDs are superfluous. The fixed IDs for status and actual values are 0x02F0 and
0x0750.
▪ You can make the scales electronics enter the desired values into the reply telegram by adding read
IDs into the telegram from the master to the scales electronics (normal order list). The order of the
values corresponds to the order of the IDs. The read IDs may originate from the data segments 'Sta-
tus' and 'Measured Values'. If IDs from the data segments 'Commands' or 'Preset values' are entered,
the last preset value will be read back.
– Special case 'Variable order list': Normally the read IDs are set once as problems arise (normal or-
der list). If the possibilities of parameterisation are exhausted, you can modify the order list, so that
the read IDs can be varied from cycle to cycle. In this case a special monitoring of the received data
is needed. One of the read IDs has to be used as monitoring ID by occupying this ID with the value
0x09FChex (2556dez). The varied read IDs provide valid data if the value of the monitoring ID has
changed.
▪ If an ID is identified as incorrect, its value in the reply will be set to zero.
For example:
Data transmission without parameters and with 6 user-defined read IDs ('Order List'):
(The default IDs used are intended as examples only)
The variable format NO_PARA_ID_3_6 must be used.

Database
3.2.2.3.1 Automatic Order List
See also 'Normal order list' and 'Variable order list'.
If in variable mode the first read ID is set to zero, the function 'Automatic Order List' will determine which and
how many read words are returned in the reply.
To do this, the function accesses the settings in the 'Fixed mode configuration' block.
The IDs for 'ID Read Value 1' to 'ID Read Value 8' in these settings determine which values are returned:
The type of variable format used determines how many values are returned:
Format Number of read IDs

(PPO type) (as per the 'order list')
NO_PARA_ID_3_6 (*) 6
PARA_ID_3_6 (*) 6
PARA_ID_2_4 (*) 4
Tab. 2 : VARIABLE formats
(*) the last value determines the quantity of read values.
The values 'Status' (0x02F0) and 'Actual Value' (0x0750) have a set coding in the telegram
and are always returned regardless of the 'order list'.

Database
3.2.2.4 Parameter Transmission

The use of parameter IDs is described in chapter 'General Information'.
Example: Data transmission with parameter range and without variable user-defined identifiers (IDs).
The parameter range (PKW) is always put before the other data.
Telegram from master to scales
PKE IND PWE1 PWE2 ID Command Command ID Setpoint Setpoint

(2 Bytes) (4 Bytes) (2 Bytes) (4 Bytes)
PKW Range PZD Range
Scale's Reply
PKE IND PWE1 PWE2 Status Actual values

(4 Bytes) (4 Bytes)
PKW Range PZD Range
3.2.2.4.1 Parameter Range in Detail

Parameter Range (PKW)
PKW (4 data words)
PKE (1st word) IND (2nd word) PWE (3rd and 4th words)
AK PNU High Low PWE1(MSB) PWE2(LSB)
A) Parameter Identifier (PKE)

The parameter identifier (PKE) is always a 16 bit value.
Bits 0 to 12 (PNU) contain the ParameterNUmber of the desired parameter.
Bits 13 to 15 (TID/RID) contain the TaskIDentifier or the ReplyIDentifier.
PKE
AK PNU
Bit no. 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
X X X Parameter number: 1000 … 1FFF *)

*)
parameters 0000 … 0FFF are reserved for cyclic parameters.
The meaning of the order identifier for the task telegram (master → scales) can be found in the correspond-
ing table.
Task identifier (AK) Meaning Answer
dec bin positive negative
0 000 No order 0 -
1 001 Request current parameter value 2 7

(DDW)
3 011 Alter parameter value (DDW) 2 7

Database
Task identifier (AK) Meaning Answer
4 100 Request specifier (DDW) 2 7
Tab.: Master station → scales task identifier (TID)

The meaning of the reply identifier for the reply telegram (scales → master) can be found in the correspond-
ing table. Certain reply identifiers only can be used depending on the task identifier.
Reply Identifier (AK) Meaning
dec bin
0 000 No order
2 010 Transmit current parameter value/event group (DDW)
7 111 Order cannot be executed (error number in PWE2)
Tab.: Reply identifiers (RID) scales → master station

B) Parameter INDex (IND)
The array subindex (referred to only as subindex in the PROFIBUS/PROFINET profile) is an 8 bit word and
is transmitted during cyclical data exchange in the higher-value byte (bits 8 to 15) of the parameter index
(IND). The lower-value byte (bits 0 to 7) always has the value zero.
IND
Subindex (high) N/A (low)
Bit no. 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 0 0 0 X X X X 0 0 0 0 0 0 0 0
Purpose of the IND:

If, in an order, the subindex is passed on with values between 1 and 254 then, if a parameter is indexed, the
required index of that parameter will be transmitted. The meaning of the individual indices of a parameter
can be found in the following table. When processing a specifier the number of the specifier required will be
transmitted.
Subindex Meaning
dec bin
0 0000 0000 Current value
4 0000 0100 Min. value
8 0000 1000 Max. value
Tab.: Index in the parameter description (IND) - higher-value byte of the parameter index
C) Parameter Value (PWE)
The parameter value (PWE) is always transmitted as a double word (32 bit). One parameter value only can
be transmitted per PPO telegram.
A 32 bit parameter value is composed of PWE1 (higher-value word, 3rd word) and PWE2 (lower-value word,
4th word).
A 16 bit parameter value is transmitted in PWE2. In this case, PWE1 must be set to 0 at the master.
▪ Bit 15 ... 0:
Parameter value for a 16-Bit parameter or Low component for a 32-Bit parameter

Database
▪ Bit 31 ... 16:

Value = 0 for a 16-Bit parameter or High component for a 32-Bit parameter
Error Number (PWE2)
If the reply identifier has the value 7 ('order not executable'), then an error number as per the following table
is deposited in parameter value 2 (PWE2).
Error code Meaning
dec bin
1 … 0001 Illegal parameter number (parameter does not exist or incorrect preset value, e.g. min. or max. limit
exceeded)
2 … 0010 Illegal subindex value
Tab.: Error numbers

Rules for Order/Reply Processing
An order or a reply always can relate to one parameter only. The master has to repeat an order until he has
received the appropriate reply. The master recognizes the reply to an order placed as follows:
▪ Reply identifier evaluated
▪ Parameter number PNU evaluated
▪ If appropriate, the parameter index IND and/or the parameter value PWE are evaluated
The order must be sent as a whole in one telegram, as split telegrams are not permissible (consistent data).
The same applies to the reply. With the repetition of the reply telegram, the slave replies with the current
values always. If no information is required (PZD data only are of importance) from the PKW range in cyclic
operation, the task identifier must be set to 'no order'.
3.2.2.5 Example Telegrams 'Variable Mode'
3.2.2.5.1 Format NO_PARA_ID_3_6

Example for PROFIBUS DP using the variable format 'NO_PARA_ID_3_6'.
Floating point format = IEEE
Example for a process image master → slave (30 Bytes):
Bytes 01 + 02 02 50 ID=0250 for 'Serial Setpoint' Preset value

1
Bytes 03 - 06 44 7A 00 00 1000.0 as setpoint [kg/h]
Bytes 07 + 08 01 40 ID=0140 for 'Command 04+05' Preset value

2
Bytes 09-12 00 41 00 00 Control value for 'Scales Start Feeder' and 'Reset Totalizer 1'
Bytes 13+14 00 00 ID=0000 ( → Preset 3 unused ) Preset 3
Bytes 15-18 00 00 00 00 control value 'Null' (not active, because ID=0000)
Order list:
Bytes 19 + 20 07 52 ID = 0752 for requesting measured value 'Totalizer 1' [kg] ID01
Bytes 21+22 07 5E ID = 075E for requesting measured value 'Speed' [1/min] ID02
Bytes 23+24 07 68 ID = 0768 for requesting measured value 'Batch Actual Value' [kg] ID03
Bytes 25+26 07 6A ID = 076A for requesting measured value 'Batch Resid. Amount' [kg] ID04

Database
Bytes 27+28 07 60 ID = 0760 for requesting measured value 'Fill Weight' [kg] ID05
Bytes 29+30 06 10 ID=0610 for 'Status 52+53' for requesting the highest priority error ID06
Example for a process image slave → master (32 Bytes):

*)
Bytes 01-04 01 1D 00 00 Message from 'Status 02+03' = [ ID=02F0 ]
**)
Bytes 05-08 00 00 00 00 Measured value 'Feedrate' [kg/h] = [ ID = 0750 ]
Order list:
Bytes 09-12 44 9A 51 EC Value corresponding to ID in bytes 19 + 20, so '' Totalizer 1 [kg] = [ ID01 ]
1234.56
Bytes 13-16 00 00 00 00 Value corresponding to ID in bytes 21 + 22, so 'Speed' [ ID02 ]
Bytes 17-20 42 B3 99 9A Value corresponding to ID in bytes 23+24, so 'Batch Actual Value' [kg] [ ID03 ]
= 89.8
Bytes 21-24 41 23 D7 0A Value corresponding to ID in bytes 25+26, so 'Batch Resid. Amount' [ ID04 ]
[kg] = 10.24
Bytes 25-28 43 16 80 00 Value corresponding to ID in bytes 27+28, so 'Fill Weight' [kg] = 150.5 [ ID05 ]
Bytes 29-32 01 17 03 15 Value corresponding to ID in bytes 29 + 30, also highest priority error [ ID06 ]
(here: A, SY08, acknowledged)
*)
this status is always returned. [ 02F0 ] means 'Content of Address 02F0'. In this example the bits set are
'Normal Mode', 'Selected Language OK', 'Volumetric Mode', 'Counter active' and 'Feeder On'.
**) this actual value is always returned.
3.2.2.5.2 Format PARA_ID_2_4 with 'Change Parameter'

GSD file: ITE10C9B.GSD → Configuration module 'PARA_ID_2_4'
Floating point format = IEEE
Order: Set parameter P05.09 'Threshold filling start' to value '15 %' (e.g. for VLW20650).
A) INTECONT Tersus parameters to be set

Configuration = PARA_ID_2_4
B) Determining parameter range (PKW)

1st Parameter Identifier (PKE)
The parameter has the ID '4613/0x01205' and the parameter value is to be changed.
TID=3 and PNU=0x1205.
They must be encoded as follows:
PKE
TID/RID PNU
Bit no. 15 14 13 12 … 0
TID/RID 0 1 1 Task identifier = 3 (→ change parameter)
↓ ↓ ↓

Database
Par. ID 0 0 0 1 0 0 1 0 0 0 0 0 0 1 0 1
(hex) 1 2 0 5
PKE 0 1 1 1 0 0 1 0 0 0 0 0 0 1 0 1
(hex) 7 2 0 5
This results in a content for PKE of '72 05'.
2nd Parameter Index (IND)

Subindex = 0 → current value of the parameter will be read.
This results in a content for IND of '00 00'.
3rd Parameter Value (PWE)

The decimal number 15 must be converted into IEEE format.
This results in a content for PWE of '41 70 00 00'.
C) Example of process images

Master → slave (28 bytes):
Bytes 01 - 72 05 TID = 3 and ID = 0x1205 (from 1st) → change PKE PKW

02
Bytes 03 - 00 00 Subindex = 0 (from 2nd) IND

04
Bytes 05 - 41 70 00 00 Value = 15 (from 3rd) PWE

08
Bytes 09 + 02 50 ID=0x0250 for 'Serial Setpoint' ID Default

*)
10 value 1
Bytes 11 - 44 7A 00 00 1000.0 as setpoint [kg/h] Default value

14
Bytes 15 + 01 40 ID=0x0140 for 'Command 04+05' ID Default

*)
16 value 2
Bytes 17 - 00 01 00 00 Control value for 'Scales Start Feeder' Default value

20
Order list:
Bytes 21 - 00 00 00 00 n/a ID01 Read

22 value 1
Bytes 23 - 00 00 00 00 n/a ID02 Read

24 Value 2
Bytes 25 - 00 00 00 00 n/a ID03 Read

26 Value 3
Bytes 27 - 00 00 00 00 n/a ID04 Read

28 Value 4
*)
Default value 1 and default value 2 are always sent, but the ID can vary.
Slave → master (32 bytes):

Database
Bytes 01 - 52 05 RID and ID = 0x1205 PKE PKW

02
Bytes 03 - 00 00 Subindex = 0 IND

04
Bytes 05 - 41 70 00 00 Value = 15 PWE

08
*)
Bytes 09 - 01 02 00 00 'Status 02+03' Messages = [ ID=02F0 ] Status
12
Bytes 13 - 00 00 00 00 Measured value 'Feedrate' [kg/h] = [ ID=0750 ] Actual

**)
16 value
[Order
List]:
Bytes 17 - 00 00 00 00 n/a [ID01] Value1

20
Bytes 21 - 00 00 00 00 n/a [ID02] Value 2

24
Bytes 25 - 00 00 00 00 n/a [ID03] Value3

28
Bytes 29 - 00 00 00 00 n/a [ID04] Value4

32
*)
this status is always returned. [ 02F0 ] means 'Content of Address 02F0'. In this example the bits set are
'Normal Mode' and 'No Release'.
**)
this actual value is always returned.
D) Evaluation of the reply identifier

(from returned content of the PKW → PKE)
The byte sequence in PKE = 52 05.
PKE
TID/RID PNU
Bit no. 15 14 13 12 … 0
TID/RID 0 1 0 Reply Identifier = 2 (→ change accepted)
↑ ↑ ↑
Par. ID 0 0 0 1 0 0 1 0 0 0 0 0 0 1 0 1
(hex) 1 2 0 5
PKE 0 1 0 1 0 0 1 0 0 0 0 0 0 1 0 1
(hex) 5 2 0 5
Result: Reply Identifier = 2 → parameter has been successfully changed.

Database
3.3 Available Data - List
3.3.1 Cyclical Data Exchange

Explanation of the Lists
There are separate lists for the different data types. Each list contains the following information:
a) ID (hex/dec)
Used with the following protocols:
▪ With Modbus-RTU and Modbus-TCP as a data address
▪ With PROFIBUS DP as an identifier to indicate which value is to be transmitted
▪ DeviceNet (see PROFIBUS DP)
▪ PROFINET IO (see PROFIBUS DP)
▪ EtherNet/IP (see PROFIBUS DP)
The value of 'ID' addresses the entire 4 byte data block (data double word).
If a bit is to be addressed, as is possible using Modbus, then the digit in front of the word meaning must be
added to the 'word address'.
Example: Group alarm (data segment 'Status'): Word address 0x02F0 + 5 → Bit address 0x02F5
The bold printed IDs are the ones to be used for the following protocols:
▪ PROFIBUS DP
▪ DeviceNet
▪ PROFINET IO
▪ EtherNet/IP
They each represent the base address of a data double word. These Ids can also be used for all remaining
protocols if the 'General Payload Structure - Variable Mode' is used with them too.
b) Value
The meaning of the value in the weighing system can be found in the 'value' column (commands, presets,
status, measured values, ...).
c) Mode
Mode (commands only): Commands can be level- or edge-triggered.
▪ (S) means that the level determines the function.
▪ (D) indicates that a change from '0' to '1' (positive slope) will trigger the desired action.
CAUTION (applies to FIXED and VARIABLE Mode):
The PCS (master) preset data must be pending for at least 250 ms in order to be clearly identified by
the weighing electronics (slave).
d) Software
This column indicates whether the value concerned is present in this software. If not, the request will be an-
swered with the value ZERO. Presets that refer to non-existent IDs will not be evaluated.

Database
TIP
Non-existent values may be available in a later version of the software (fur-
ther expansion stage).
3.3.1.1 Default Values
3.3.1.1.1 Write Commands
ID (Identifier) Value Mode Feeder Type
hex dec Commands Mode VBW VBW VWF VLW VIF VMC
20650 20660 20650 20650 20650 20650
Command 0 (coded as number)
0100 00256
0108 00264 Century * * * * * *
0110 00272 Year * * * * * *
0118 00280 Month * * * * * *
0120 00288 Day * * * * * *
0128 00296 Hour * * * * * *
0130 00304 Minute * * * * * *
0138 00312 Second * * * * * *
Command 4 LO (coded as bit)
0140 00320 0 - Start Feeder (D) * * * * * *
0141 00321 1 - Stop Feeder (D) * * * * * *
0142 00322 2 - Clear Events (D) * * * * * *
0143 00323 3 - Release (S) * * * * * *
0144 00324 4 - Volumetric Mode (D) * * * *
0145 00325 5 - Gravimetric (D) * * * *
0146 00326 6 - Reset Totalizer 1 (D) * * * * * *
0147 00327 7 - Reset Totalizer 2 (D) * * * * * *
Command 4 HI (coded as bit)
0148 00328 8 - Volumetric Synchronous (D) * * *
0149 00329 9-
014a 00330 A-
014b 00331 B - Stop Wheel (D) *
014c 00332 C-
014d 00333 D - Open Gate (D) * *

Database
20650 20660 20650 20650 20650 20650
014e 00334 E - STOP Gate (D) * *
014f 00335 F - Close Gate (D) * *
0150 00336 0 - Select Batch (D) * * * * * *
0151 00337 1 - Deselect Batch (D) * * * * * *
0152 00338 2 - Abort Batch (D) * * * * * *
0153 00339 3 - Next with Belt Empty (D) * * *
0154 00340 4 - Reload (D) * * * *
0155 00341 5-
0156 00342 6-
0157 00343 7 - Start Wheel (D) *
0158 00344 8 - Filling Start (D) *
0159 00345 9 - Filling Stop (D) *
015a 00346 A - Emptying Start (D) *
015b 00347 B - Emptying Stop (D) *
015c 00348 C-
015d 00349 D-
015e 00350 E - Particip. Prefeeder (D) * * * * *
015f 00351 F - Stop Prefeeder (D) * * * * *
0160 00352 0-
0161 00353 1-
0162 00354 2-
0163 00355 3-
0164 00356 4-
0165 00357 5-
0166 00358 6-
0167 00359 7-
0168 00360 8-
0169 00361 9-
016a 00362 A-
016b 00363 B-
016c 00364 C-
016d 00365 D-
016e 00366 E-

Database
20650 20660 20650 20650 20650 20650
016f 00367 F-
0170 00368 0 - TW: Tare (D) * * * * * *
0171 00369 1 - >0< Zero Set (D) * * * * *
0172 00370 2 - CW: Span Calibration (D) * * * * *
0173 00371 3 - LB: Pulses/Belt (D) * * * * *
0174 00372 4 - DAE Adjustment (D) *
0175 00373 5 - Linearization P1 (D) *
0179 00377 9 - Vol. Discharge Adaption (D) *
017a 00378 A - CG: Optimize Controller (D) *
017b 00379 B - Apply (D) * * * * * *
017c 00380 C - Cancel (D) * * * * * *
017d 00381 D - Time Acquire (D) * * * * * *
017e 00382 E-
017f 00383 F-
0180 00384 0-
0181 00385 1-
0182 00386 2-
0183 00387 3-
0184 00388 4-
0185 00389 5-
0186 00390 6-
0187 00391 7-
0188 00392 8 - Batch Record (D) * * * * * *
0189 00393 9 - Print Status Report (D) * * * * *
018a 00394 A - Totalizer Record (D) * * * * * *
018b 00395 B - Kill Printout (D) * * * *
018c 00396 C - Print Parameters (D) * * * * *
018d 00397 D-
018e 00398 E- *
018f 00399 F- *

Database
20650 20660 20650 20650 20650 20650
0190 00400 0 - Start Keyboard Mode (D) * * * * * *
0191 00401 1 - Stop Keyboard Mode (D) * * * * * *
0192 00402 2 - Start Simulation (D) * * * * * *
0193 00403 3 - Stop Simulation (D) * * * * * *
0194 00404 4 - Load Factory Defaults (D) * * * * * *
0195 00405 5 - Start Check Feed Constancy (D) *
0196 00406 6 - Manual Gate Control (D) * *
0197 00407 7 - Automatic Gate Control (D) * *
0198 00408 8-
0199 00409 9-
019a 00410 A-
019b 00411 B-
019c 00412 C-
019d 00413 D-
019e 00414 E-
019f 00415 F-
01a0 00416 0-
01a1 00417 1-
01a2 00418 2-
01a3 00419 3-
01a4 00420 4-
01a5 00421 5-
01a6 00422 6-
01a7 00423 7-
01a8 00424 8-
01a9 00425 9-
01aa 00426 A-
01ab 00427 B-
01ac 00428 C-
01ad 00429 D-
01ae 00430 E-
01af 00431 F-

Database
20650 20660 20650 20650 20650 20650
01b0 00432 0-
01b1 00433 1-
01b2 00434 2-
01b3 00435 3-
01b4 00436 4-
01b5 00437 5-
01b6 00438 6-
01b7 00439 7-
01b8 00440 8-
01b9 00441 9-
01ba 00442 A-
01bb 00443 B-
01bc 00444 C-
01bd 00445 D-
01be 00446 E-
01bf 00447 F - DI: BIC freeze (S) * *
01c0 00448 0-
01c1 00449 1 - Load Custom Defaults (D) * * * * * *
01c2 00450 2-
01c3 00451 3-
01c4 00452 4-
01c5 00453 5-
01c6 00454 6-
01c7 00455 7-
01c8 00456 8-
01c9 00457 9-
01ca 00458 A-
01cb 00459 B - Start Data Logging (D) * * * * * *
01cc 00460 C - Stop Data Logging (D) * * * * * *
01cd 00461 D - Clear Data Log File (D) * * * * * *
01ce 00462 E - Print Route 1 (D) * * * *
01cf 00463 F - Print Route 2 (D) * * * *
Tab. 3 : Fieldbus Commands

Database
3.3.1.1.2 Write IEEE Values
ID (Identifier) Value Dimension Feeder Type
hex dec Presets Dimension VBW VBW VWF VLW VIF VMC
20650 20660 20650 20650 20650 20650
0250 00592 Serial Setpoint kg/h * * * *
0252 00594 Serial Batch Setpoint kg * * * * * *
0254 00596 Reload Setpoint kg * * * *
0256 00598 Batch No. * * * *
0258 00600
025a 00602
025c 00604
025e 00606
0260 00608
0262 00610
0264 00612
0266 00614
0268 00616
026a 00618
026c 00620
026e 00622
0270 00624
0272 00626
0274 00628
0276 00630
0278 00632
027a 00634
027c 00636
027e 00638
Tab. 4 : Fieldbus Presets

Database
3.3.1.2 Read Values
3.3.1.2.1 Read Status
ID (Identifier) Value Event Feeder Type
hex dec Status Group/Class VBW VBW VWF VLW VIF VMC
20650 20660 20650 20650 20650 20650
Status 0 (coded as number)
02d0 00720 Feeder Type * * * * * *
02d8 00728 SW Revision * * * * * *
02e0 00736 SW Version (LOW) * * * * * *
02e8 00744 SW Version (HIGH) * * * * * *
Status 2 LO (coded as bit)
02f0 00752 0 - Feeder On * * * * * *
02f1 00753 1 - No Release * * * * * *
02f2 00754 2 - Counter active * * * * * *
02f3 00755 3 - Volumetric Mode * * * *
02f4 00756 4 - Selected Language OK * * * * * *
02f5 00757 5 - Summary Alarm * * * * * *
02f6 00758 6 - Summary Warning * * * * * *
02f7 00759 7 - Calibration active * * * * * *
Status 2 HI (coded as bit)
02f8 00760 8 - Normal Mode * * * * * *
02f9 00761 9 - OP Mode * * * * * *
02fa 00762 A-
02fb 00763 B - Simulation Mode * * * * * *
02fc 00764 C - Volumetric Start-Up * * * *
02fd 00765 D - Wheel Running *
02fe 00766 E - Measuring Delay *
02ff 00767 F - Event: Setpoint Limited * * * *
0300 00768 0 - Batch selected * * * * * *
0301 00769 1 - Batch active * * * * * *
0302 00770 2 - Batch Dribble Feed * * * * * *
0303 00771 3 - Batch discharge * * * *
0304 00772 4 - English units active * * * * * *
0305 00773 5-
0306 00774 6-
0307 00775 7-

Database
20650 20660 20650 20650 20650 20650
0308 00776 8 - TW: Tare * * * * * *
0309 00777 9 - >0< Zero Set * * * * *
030a 00778 A - CW: Span Calibration * * * * *
030b 00779 B - LB: Pulses/Belt * * *
030c 00780 C - DAE Adjustment *
030d 00781 D - Auto Zero Active * * * *
030e 00782 E - Vol. Discharge Adaption *
030f 00783 F - CG: Optimize Controller *
0310 00784 0 - Measuring Sytem * * *
0311 00785 1 - Measuring Direction UP *
0312 00786 2 - Filling active *
0313 00787 3 - Discharging active * * * *
0314 00788 4 - Gate open *
0315 00789 5 - Gate closed *
0316 00790 6-
0317 00791 7-
0318 00792 8 - Limit: Actual Flow Rate MAX * * * * * *
0319 00793 9 - Limit: Actual Flow Rate MIN * * * * * *
031a 00794 A - Limit: Load MAX * * *
031b 00795 B - Limit: Load MIN * * *
031c 00796 C - Limit: Speed MAX * * *
031d 00797 D - Limit: Speed MIN * * *
031e 00798 E-
031f 00799 F-
0320 00800 0-
0321 00801 1 - Max Value: Fill Weight *
0322 00802 2 - Min Value: Fill Weight *
0323 00803 3 - Event: Maximum Load *
0324 00804 4-
0325 00805 5 - Speed-Max Value *
0326 00806 6 - Speed-Min Value * *
0327 00807 7-

Database
20650 20660 20650 20650 20650 20650
0328 00808 8-
0329 00809 9-
032a 00810 A-
032b 00811 B-
032c 00812 C-
032d 00813 D-
032e 00814 E-
032f 00815 F-
0330 00816 0 - English units active * * * * * *
0331 00817 1 - Waiting for Confirmation * * * * * *
0332 00818 2 - Checkweight Up/Down * * * * * *
0333 00819 3 - Parameterization active * * * * * *
0334 00820 4 - Linearization P1 *
0338 00824 8 - DO: Gate *
0339 00825 9 - DO: Clean Inlet *
033a 00826 A - Manual Gate Control * *
033b 00827 B-
033c 00828 C-
033d 00829 D-
033e 00830 E-
033f 00831 F-
0340 00832 0-
0341 00833 1-
0342 00834 2-
0343 00835 3-
0344 00836 4-
0345 00837 5-
0346 00838 6-
0347 00839 7-
0348 00840 8-

Database
20650 20660 20650 20650 20650 20650
0349 00841 9-
034a 00842 A-
034b 00843 B-
034c 00844 C - EasyServe active * * * * * *
034d 00845 D - EasyServe Logged-in * * * * * *
034e 00846 E-
034f 00847 F-
0350 00848 0-
0351 00849 1-
0352 00850 2-
0353 00851 3-
0354 00852 4-
0355 00853 5 - Reload active * * * *
0356 00854 6-
0357 00855 7-
0358 00856 8-
0359 00857 9-
035a 00858 A-
035b 00859 B-
035c 00860 C-
035d 00861 D-
035e 00862 E-
035f 00863 F-
0360 00864 0-
0361 00865 1-
0362 00866 2-
0363 00867 3-
0364 00868 4-
0365 00869 5 - DI: BIC freeze * *
0366 00870 6-
0367 00871 7-
0368 00872 8-
0369 00873 9-

Database
20650 20660 20650 20650 20650 20650
036a 00874 A-
036b 00875 B-
036c 00876 C-
036d 00877 D-
036e 00878 E-
036f 00879 F-
0370 00880 0 - Event: Memory SY01 (W2) * * * * * *
0371 00881 1-
0372 00882 2-
0373 00883 3-
0374 00884 4-
0375 00885 5-
0376 00886 6-
0377 00887 7 - Event: Cyclic Communication SY08 (W2) * * * * * *
0378 00888 8 - Event: License Violation SY09 (W2) * * * * * *
0379 00889 9 - Event: Acyclic Communication SY10 (W2) * * * * * *
037a 00890 A-
037b 00891 B-
037c 00892 C-
037d 00893 D - Event: Simulation active SY14 (W2) * * * * * *
037e 00894 E-
037f 00895 F-
0380 00896 0 - Event: Setpoint Limited SC01 (W2) * * * *
0381 00897 1 - Event: Stand-By SC02 (W2) * * * *
0382 00898 2 - Event: Maint.Feeder Run SC03 (W2) * * * * * *
0383 00899 3 - Event: Maint. Electric SC04 (W2) * * * * * *
0384 00900 4 - Event: External Event 1 SC05 (W2) * * * * * *
0386 00902 6 - Event: DAE active SC07 (W2) *
0387 00903 7 - Event: DAE Fault SC08 (W2) *
0388 00904 8 - Event: Gate Feedback SC09 (W2) *
0389 00905 9 - Event: T_Volum. SC10 (W2) *
038a 00906 A-

Database
20650 20660 20650 20650 20650 20650
038b 00907 B-
038c 00908 C-
038d 00909 D-
038e 00910 E-
038f 00911 F-
0390 00912 0 - Event: Power Failure WE01 (W2) * * * * * *
0391 00913 1-
0392 00914 2-
0393 00915 3-
0394 00916 4-
0395 00917 5-
0396 00918 6-
0397 00919 7-
0398 00920 8 - Event: NAMUR Error Tacho WE09 (W2) * * * *
0399 00921 9 - Event: NAMUR Error Sensor WE10 (W2) * * *
039a 00922 A - Event: NAMUR Error Tacho (2nd) WE11 (W2) *
039b 00923 B - Event: LFT-Memory WE12 (W2) *
039c 00924 C-
039d 00925 D-
039e 00926 E-
039f 00927 F-
03a0 00928 0-
03a1 00929 1 - Event: Slip WM02 (W2) * *
03a2 00930 2 - Event: Belt Skew WM03 (W2) * *
03a3 00931 3 - Event: Belt Drift WM04 (W2) * *
03a4 00932 4-
03a5 00933 5-
03a6 00934 6-
03a7 00935 7-
03a8 00936 8-
03a9 00937 9-
03aa 00938 A-
03ab 00939 B-

Database
20650 20660 20650 20650 20650 20650
03ac 00940 C-
03ad 00941 D-
03ae 00942 E-
03af 00943 F-
03b0 00944 0-
03b1 00945 1-
03b2 00946 2-
03b3 00947 3-
03b4 00948 4-
03b5 00949 5 - Event: Out of Tolerance MF06 (W2) * * * * * *
03b6 00950 6-
03b7 00951 7-
03b8 00952 8-
03b9 00953 9-
03ba 00954 A-
03bb 00955 B-
03bc 00956 C-
03bd 00957 D-
03be 00958 E-
03bf 00959 F-
03c0 00960 0 - Event: Run Disabled IL01 (W2) * * * * * *
03c1 00961 1-
03c2 00962 2-
03c3 00963 3-
03c4 00964 4-
03c5 00965 5-
03c6 00966 6-
03c7 00967 7-
03c8 00968 8-
03c9 00969 9-
03ca 00970 A-
03cb 00971 B-
03cc 00972 C-

Database
20650 20660 20650 20650 20650 20650
03cd 00973 D-
03ce 00974 E-
03cf 00975 F-
03d0 00976 0 - Event: Controller Limited CO01 (W2) * * * *
03d1 00977 1 - Event: MIN Flow Gate CO02 (W2) * *
03d2 00978 2 - Event: MAX Flow Gate CO03 (W2) * *
03d3 00979 3-
03d4 00980 4-
03d5 00981 5-
03d6 00982 6 - Event: Batch Setpoint MIN CO07 (W2) *
03d7 00983 7 - Event: Batch Actual Value MIN CO08 (W2) *
03d8 00984 8 - Event: Batch > Setpoint CO09 (W2) * *
03d9 00985 9-
03da 00986 A-
03db 00987 B-
03dc 00988 C-
03dd 00989 D-
03de 00990 E-
03df 00991 F-
03e0 00992 0-
03e1 00993 1-
03e2 00994 2-
03e3 00995 3-
03e4 00996 4-
03e5 00997 5-
03e6 00998 6-
03e7 00999 7-
03e8 01000 8-
03e9 01001 9-
03ea 01002 A-
03eb 01003 B-
03ec 01004 C-
03ed 01005 D-

Database
20650 20660 20650 20650 20650 20650
03ee 01006 E-
03ef 01007 F-
03f0 01008 0 - Event: Error LC Input CA01 (W2) * * * * * *
03f1 01009 1 - Event: Tachometer Input CA02 (W2) * * * *
03f2 01010 2-
03f3 01011 3-
03f4 01012 4 - Event: Linearization Error CA05 (W2) * * * * * *
03f5 01013 5 - Event: Tare Correction CA06 (W2) * * * *
03f6 01014 6-
03f7 01015 7-
03f8 01016 8-
03f9 01017 9-
03fa 01018 A - Event: Tachometer Input (2nd) CA11 (W2) *
03fb 01019 B - Event: Tare Difference > MAX CA12 (W2) * * *
03fc 01020 C - Event: Time elapsed CA13 (W2) * * *
03fd 01021 D - Event: Tacho Comparison CA14 (W2) *
03fe 01022 E-
03ff 01023 F-
0400 01024 0 - Event: LC Input > MAX HI01 (W2) * * * * * *
0401 01025 1 - Event: Actual Flow Rate MAX HI02 (W2) * * * * * *
0402 01026 2 - Event: Load MAX HI03 (W2) * * *
0403 01027 3 - Event: Speed MAX HI04 (W2) * * *
0404 01028 4 - Event: Deviation HI05 (W2) * * * *
0405 01029 5 - Event: Fill Weight-Max HI06 (W2) *
0406 01030 6 - Event: Speed-Max HI07 (W2) *
0407 01031 7 - Event: HUBmax HI08 (W2) *
0408 01032 8 - Event: Maximum Load HI09 (W2) *
0409 01033 9-
040a 01034 A-
040b 01035 B-
040c 01036 C - Event: FC-MAX Limit HI13 (W2) *
040d 01037 D-
040e 01038 E-

Database
20650 20660 20650 20650 20650 20650
040f 01039 F-
0410 01040 0 - Event: LC Input < MIN LO01 (W2) * * * * * *
0411 01041 1 - Event: Actual Flow Rate MIN LO02 (W2) * * * * * *
0412 01042 2 - Event: Load MIN LO03 (W2) * * *
0413 01043 3 - Event: Speed MIN LO04 (W2) * * *
0414 01044 4-
0415 01045 5 - Event: Fill Weight-Min LO06 (W2) *
0416 01046 6 - Event: Speed-Min LO07 (W2) * *
0417 01047 7 - Event: AMOUNT min LO08 (W2) *
0418 01048 8-
0419 01049 9-
041a 01050 A-
041b 01051 B-
041c 01052 C - Event: FC-MIN Limit LO13 (W2) *
041d 01053 D-
041e 01054 E-
041f 01055 F-
0420 01056 0 - Event: Memory SY01 (W1) * * * * * *
0421 01057 1-
0422 01058 2-
0423 01059 3-
0424 01060 4-
0425 01061 5-
0426 01062 6-
0427 01063 7 - Event: Cyclic Communication SY08 (W1) * * * * * *
0428 01064 8 - Event: License Violation SY09 (W1) * * * * * *
0429 01065 9 - Event: Acyclic Communication SY10 (W1) * * * * * *
042a 01066 A-
042b 01067 B-
042c 01068 C-
042d 01069 D - Event: Simulation active SY14 (W1) * * * * * *
042e 01070 E-
042f 01071 F-

Database
20650 20660 20650 20650 20650 20650
0430 01072 0 - Event: Setpoint Limited SC01 (W1) * * * *
0431 01073 1 - Event: Stand-By SC02 (W1) * * * *
0432 01074 2 - Event: Maint.Feeder Run SC03 (W1) * * * * * *
0433 01075 3 - Event: Maint. Electric SC04 (W1) * * * * * *
0436 01078 6 - Event: DAE active SC07 (W1) *
0437 01079 7 - Event: DAE Fault SC08 (W1) *
0438 01080 8 - Event: Gate Feedback SC09 (W1) *
0439 01081 9 - Event: T_Volum. SC10 (W1) *
043a 01082 A-
043b 01083 B-
043c 01084 C-
043d 01085 D-
043e 01086 E-
043f 01087 F-
0440 01088 0 - Event: Power Failure WE01 (W1) * * * * * *
0441 01089 1-
0442 01090 2-
0443 01091 3-
0444 01092 4-
0445 01093 5-
0446 01094 6-
0447 01095 7-
0448 01096 8 - Event: NAMUR Error Tacho WE09 (W1) * * * *
0449 01097 9 - Event: NAMUR Error Sensor WE10 (W1) * * *
044a 01098 A - Event: NAMUR Error Tacho (2nd) WE11 (W1) *
044b 01099 B - Event: LFT-Memory WE12 (W1) *
044c 01100 C-
044d 01101 D-
044e 01102 E-
044f 01103 F-

Database
20650 20660 20650 20650 20650 20650
0450 01104 0-
0451 01105 1 - Event: Slip WM02 (W1) * *
0452 01106 2 - Event: Belt Skew WM03 (W1) * *
0453 01107 3 - Event: Belt Drift WM04 (W1) * *
0454 01108 4-
0455 01109 5-
0456 01110 6-
0457 01111 7-
0458 01112 8-
0459 01113 9-
045a 01114 A-
045b 01115 B-
045c 01116 C-
045d 01117 D-
045e 01118 E-
045f 01119 F-
0460 01120 0-
0461 01121 1-
0462 01122 2-
0463 01123 3-
0464 01124 4-
0465 01125 5 - Event: Out of Tolerance MF06 (W1) * * * * * *
0466 01126 6-
0467 01127 7-
0468 01128 8-
0469 01129 9-
046a 01130 A-
046b 01131 B-
046c 01132 C-
046d 01133 D-
046e 01134 E-
046f 01135 F-
0470 01136 0 - Event: Run Disabled IL01 (W1) * * * * * *

Database
20650 20660 20650 20650 20650 20650
0471 01137 1-
0472 01138 2-
0473 01139 3-
0474 01140 4-
0475 01141 5-
0476 01142 6-
0477 01143 7-
0478 01144 8-
0479 01145 9-
047a 01146 A-
047b 01147 B-
047c 01148 C-
047d 01149 D-
047e 01150 E-
047f 01151 F-
0480 01152 0 - Event: Controller Limited CO01 (W1) * * * *
0481 01153 1 - Event: MIN Flow Gate CO02 (W1) * *
0482 01154 2 - Event: MAX Flow Gate CO03 (W1) * *
0483 01155 3-
0484 01156 4-
0485 01157 5-
0486 01158 6 - Event: Batch Setpoint MIN CO07 (W1) *
0487 01159 7 - Event: Batch Actual Value MIN CO08 (W1) *
0488 01160 8 - Event: Batch > Setpoint CO09 (W1) * *
0489 01161 9-
048a 01162 A-
048b 01163 B-
048c 01164 C-
048d 01165 D-
048e 01166 E-
048f 01167 F-
0490 01168 0-
0491 01169 1-

Database
20650 20660 20650 20650 20650 20650
0492 01170 2-
0493 01171 3-
0494 01172 4-
0495 01173 5-
0496 01174 6-
0497 01175 7-
0498 01176 8-
0499 01177 9-
049a 01178 A-
049b 01179 B-
049c 01180 C-
049d 01181 D-
049e 01182 E-
049f 01183 F-
04a0 01184 0 - Event: Error LC Input CA01 (W1) * * * * * *
04a1 01185 1 - Event: Tachometer Input CA02 (W1) * * * *
04a2 01186 2-
04a3 01187 3-
04a4 01188 4 - Event: Linearization Error CA05 (W1) * * * * * *
04a5 01189 5 - Event: Tare Correction CA06 (W1) * * * *
04a6 01190 6-
04a7 01191 7-
04a8 01192 8-
04a9 01193 9-
04aa 01194 A - Event: Tachometer Input (2nd) CA11 (W1) *
04ab 01195 B - Event: Tare Difference > MAX CA12 (W1) * * *
04ac 01196 C - Event: Time elapsed CA13 (W1) * * *
04ad 01197 D - Event: Tacho Comparison CA14 (W1) *
04ae 01198 E-
04af 01199 F-
04b0 01200 0 - Event: LC Input > MAX HI01 (W1) * * * * * *
04b1 01201 1 - Event: Actual Flow Rate MAX HI02 (W1) * * * * * *
04b2 01202 2 - Event: Load MAX HI03 (W1) * * *

Database
20650 20660 20650 20650 20650 20650
04b3 01203 3 - Event: Speed MAX HI04 (W1) * * *
04b4 01204 4 - Event: Deviation HI05 (W1) * * * *
04b5 01205 5 - Event: Fill Weight-Max HI06 (W1) *
04b6 01206 6 - Event: Speed-Max HI07 (W1) *
04b7 01207 7 - Event: HUBmax HI08 (W1) *
04b8 01208 8 - Event: Maximum Load HI09 (W1) *
04b9 01209 9-
04ba 01210 A-
04bb 01211 B-
04bc 01212 C - Event: FC-MAX Limit HI13 (W1) *
04bd 01213 D-
04be 01214 E-
04bf 01215 F-
04c0 01216 0 - Event: LC Input < MIN LO01 (W1) * * * * * *
04c1 01217 1 - Event: Actual Flow Rate MIN LO02 (W1) * * * * * *
04c2 01218 2 - Event: Load MIN LO03 (W1) * * *
04c3 01219 3 - Event: Speed MIN LO04 (W1) * * *
04c4 01220 4-
04c5 01221 5 - Event: Fill Weight-Min LO06 (W1) *
04c6 01222 6 - Event: Speed-Min LO07 (W1) * *
04c7 01223 7 - Event: AMOUNT min LO08 (W1) *
04c8 01224 8-
04c9 01225 9-
04ca 01226 A-
04cb 01227 B-
04cc 01228 C - Event: FC-MIN Limit LO13 (W1) *
04cd 01229 D-
04ce 01230 E-
04cf 01231 F-
04d0 01232 0 - Event: Memory SY01 (A) * * * * * *
04d1 01233 1-
04d2 01234 2-
04d3 01235 3-

Database
20650 20660 20650 20650 20650 20650
04d4 01236 4-
04d5 01237 5-
04d6 01238 6-
04d7 01239 7 - Event: Cyclic Communication SY08 (A) * * * * * *
04d8 01240 8 - Event: License Violation SY09 (A) * * * * * *
04d9 01241 9 - Event: Acyclic Communication SY10 (A) * * * * * *
04da 01242 A-
04db 01243 B-
04dc 01244 C-
04dd 01245 D - Event: Simulation active SY14 (A) * * * * * *
04de 01246 E-
04df 01247 F-
04e0 01248 0 - Event: Setpoint Limited SC01 (A) * * * *
04e1 01249 1 - Event: Stand-By SC02 (A) * * * *
04e2 01250 2 - Event: Maint.Feeder Run SC03 (A) * * * * * *
04e3 01251 3 - Event: Maint. Electric SC04 (A) * * * * * *
04e4 01252 4 - Event: External Event 1 SC05 (A) * * * * * *
04e5 01253 5 - Event: External Event 2 SC06 (A) * * * * * *
04e6 01254 6 - Event: DAE active SC07 (A) *
04e7 01255 7 - Event: DAE Fault SC08 (A) *
04e8 01256 8 - Event: Gate Feedback SC09 (A) *
04e9 01257 9 - Event: T_Volum. SC10 (A) *
04ea 01258 A-
04eb 01259 B-
04ec 01260 C-
04ed 01261 D-
04ee 01262 E-
04ef 01263 F-
04f0 01264 0 - Event: Power Failure WE01 (A) * * * * * *
04f1 01265 1-
04f2 01266 2-
04f3 01267 3-
04f4 01268 4-

Database
20650 20660 20650 20650 20650 20650
04f5 01269 5-
04f6 01270 6-
04f7 01271 7-
04f8 01272 8 - Event: NAMUR Error Tacho WE09 (A) * * * *
04f9 01273 9 - Event: NAMUR Error Sensor WE10 (A) * * *
04fa 01274 A - Event: NAMUR Error Tacho (2nd) WE11 (A) *
04fb 01275 B - Event: LFT-Memory WE12 (A) *
04fc 01276 C-
04fd 01277 D-
04fe 01278 E-
04ff 01279 F-
0500 01280 0-
0501 01281 1 - Event: Slip WM02 (A) * *
0502 01282 2 - Event: Belt Skew WM03 (A) * *
0503 01283 3 - Event: Belt Drift WM04 (A) * *
0504 01284 4-
0505 01285 5-
0506 01286 6-
0507 01287 7-
0508 01288 8-
0509 01289 9-
050a 01290 A-
050b 01291 B-
050c 01292 C-
050d 01293 D-
050e 01294 E-
050f 01295 F-
0510 01296 0-
0511 01297 1-
0512 01298 2-
0513 01299 3-
0514 01300 4-
0515 01301 5 - Event: Out of Tolerance MF06 (A) * * * * * *

Database
20650 20660 20650 20650 20650 20650
0516 01302 6-
0517 01303 7-
0518 01304 8-
0519 01305 9-
051a 01306 A-
051b 01307 B-
051c 01308 C-
051d 01309 D-
051e 01310 E-
051f 01311 F-
0520 01312 0 - Event: Run Disabled IL01 (A) * * * * * *
0521 01313 1-
0522 01314 2-
0523 01315 3-
0524 01316 4-
0525 01317 5-
0526 01318 6-
0527 01319 7-
0528 01320 8-
0529 01321 9-
052a 01322 A-
052b 01323 B-
052c 01324 C-
052d 01325 D-
052e 01326 E-
052f 01327 F-
0530 01328 0 - Event: Controller Limited CO01 (A) * * * *
0531 01329 1 - Event: MIN Flow Gate CO02 (A) * *
0532 01330 2 - Event: MAX Flow Gate CO03 (A) * *
0533 01331 3-
0534 01332 4-
0535 01333 5-
0536 01334 6 - Event: Batch Setpoint MIN CO07 (A) *

Database
20650 20660 20650 20650 20650 20650
0537 01335 7 - Event: Batch Actual Value MIN CO08 (A) *
0538 01336 8 - Event: Batch > Setpoint CO09 (A) * *
0539 01337 9-
053a 01338 A-
053b 01339 B-
053c 01340 C-
053d 01341 D-
053e 01342 E-
053f 01343 F-
0540 01344 0-
0541 01345 1-
0542 01346 2-
0543 01347 3-
0544 01348 4-
0545 01349 5-
0546 01350 6-
0547 01351 7-
0548 01352 8-
0549 01353 9-
054a 01354 A-
054b 01355 B-
054c 01356 C-
054d 01357 D-
054e 01358 E-
054f 01359 F-
0550 01360 0 - Event: Error LC Input CA01 (A) * * * * * *
0551 01361 1 - Event: Tachometer Input CA02 (A) * * * *
0552 01362 2-
0553 01363 3-
0554 01364 4 - Event: Linearization Error CA05 (A) * * * * * *
0555 01365 5 - Event: Tare Correction CA06 (A) * * * *
0556 01366 6-
0557 01367 7-

Database
20650 20660 20650 20650 20650 20650
0558 01368 8-
0559 01369 9-
055a 01370 A - Event: Tachometer Input (2nd) CA11 (A) *
055b 01371 B - Event: Tare Difference > MAX CA12 (A) * * *
055c 01372 C - Event: Time elapsed CA13 (A) * * *
055d 01373 D - Event: Tacho Comparison CA14 (A) *
055e 01374 E-
055f 01375 F-
0560 01376 0 - Event: LC Input > MAX HI01 (A) * * * * * *
0561 01377 1 - Event: Actual Flow Rate MAX HI02 (A) * * * * * *
0562 01378 2 - Event: Load MAX HI03 (A) * * *
0563 01379 3 - Event: Speed MAX HI04 (A) * * *
0564 01380 4 - Event: Deviation HI05 (A) * * * *
0565 01381 5 - Event: Fill Weight-Max HI06 (A) *
0566 01382 6 - Event: Speed-Max HI07 (A) *
0567 01383 7 - Event: HUBmax HI08 (A) *
0568 01384 8 - Event: Maximum Load HI09 (A) *
0569 01385 9-
056a 01386 A-
056b 01387 B-
056c 01388 C - Event: FC-MAX Limit HI13 (A) *
056d 01389 D-
056e 01390 E-
056f 01391 F-
0570 01392 0 - Event: LC Input < MIN LO01 (A) * * * * * *
0571 01393 1 - Event: Actual Flow Rate MIN LO02 (A) * * * * * *
0572 01394 2 - Event: Load MIN LO03 (A) * * *
0573 01395 3 - Event: Speed MIN LO04 (A) * * *
0574 01396 4-
0575 01397 5 - Event: Fill Weight-Min LO06 (A) *
0576 01398 6 - Event: Speed-Min LO07 (A) * *
0577 01399 7 - Event: AMOUNT min LO08 (A) *

Database
20650 20660 20650 20650 20650 20650
0578 01400 8-
0579 01401 9-
057a 01402 A-
057b 01403 B-
057c 01404 C - Event: FC-MIN Limit LO13 (A) *
057d 01405 D-
057e 01406 E-
057f 01407 F-
0580 01408 0 - DI1 * * * * * *
0581 01409 1 - DI2 * * * * * *
0582 01410 2 - DI3 * * * * * *
0583 01411 3 - DI4 * * * * * *
0584 01412 4 - DI5 * * * * * *
0585 01413 5 - DI6 * * * * * *
0586 01414 6 - DI7 * * * * * *
0587 01415 7 - DI8 *
0588 01416 8-
0589 01417 9-
058a 01418 A-
058b 01419 B - DI4 Error * * * * * *
058c 01420 C - DI5 Error * * * * * *
058d 01421 D-
058e 01422 E-
058f 01423 F-
0590 01424 0-
0591 01425 1-
0592 01426 2-
0593 01427 3-
0594 01428 4-
0595 01429 5-
0596 01430 6-
0597 01431 7-
0598 01432 8-

Database
20650 20660 20650 20650 20650 20650
0599 01433 9-
059a 01434 A-
059b 01435 B-
059c 01436 C-
059d 01437 D-
059e 01438 E-
059f 01439 F-
05a0 01440 0 - DO1 * * * * * *
05a1 01441 1 - DO2 * * * * * *
05a2 01442 2 - DO3 * * * * * *
05a3 01443 3 - DO4 * * * * * *
05a4 01444 4 - DO5 * * * * * *
05a5 01445 5 - DO6 * * * * * *
05a6 01446 6 - DO7 * * * * * *
05a7 01447 7 - DO8 * * * * * *
05a8 01448 8-
05a9 01449 9-
05aa 01450 A-
05ab 01451 B-
05ac 01452 C-
05ad 01453 D-
05ae 01454 E-
05af 01455 F-
05b0 01456 0-
05b1 01457 1-
05b2 01458 2-
05b3 01459 3-
05b4 01460 4-
05b5 01461 5-
05b6 01462 6-
05b7 01463 7-
05b8 01464 8-
05b9 01465 9-

Database
20650 20660 20650 20650 20650 20650
05ba 01466 A-
05bb 01467 B-
05bc 01468 C-
05bd 01469 D-
05be 01470 E-
05bf 01471 F-
05c0 01472 0-
05c1 01473 1-
05c2 01474 2-
05c3 01475 3-
05c4 01476 4-
05c5 01477 5-
05c6 01478 6-
05c7 01479 7-
05c8 01480 8-
05c9 01481 9-
05ca 01482 A-
05cb 01483 B-
05cc 01484 C-
05cd 01485 D-
05ce 01486 E-
05cf 01487 F-
05d0 01488 0-
05d1 01489 1-
05d2 01490 2-
05d3 01491 3-
05d4 01492 4-
05d5 01493 5-
05d6 01494 6-
05d7 01495 7-
05d8 01496 8-
05d9 01497 9-
05da 01498 A-

Database
20650 20660 20650 20650 20650 20650
05db 01499 B-
05dc 01500 C-
05dd 01501 D-
05de 01502 E-
05df 01503 F-
05e0 01504 0-
05e1 01505 1-
05e2 01506 2-
05e3 01507 3-
05e4 01508 4-
05e5 01509 5-
05e6 01510 6-
05e7 01511 7-
05e8 01512 8-
05e9 01513 9-
05ea 01514 A-
05eb 01515 B-
05ec 01516 C-
05ed 01517 D-
05ee 01518 E-
05ef 01519 F-
05f0 01520 0-
05f1 01521 1-
05f2 01522 2-
05f3 01523 3-
05f4 01524 4-
05f5 01525 5-
05f6 01526 6-
05f7 01527 7-
05f8 01528 8-
05f9 01529 9-
05fa 01530 A-
05fb 01531 B-

Database
20650 20660 20650 20650 20650 20650
05fc 01532 C-
05fd 01533 D-
05fe 01534 E-
05ff 01535 F-
0600 01536 0-
0601 01537 1-
0602 01538 2-
0603 01539 3-
0604 01540 4-
0605 01541 5-
0606 01542 6-
0607 01543 7-
0608 01544 8-
0609 01545 9-
060a 01546 A-
060b 01547 B-
060c 01548 C-
060d 01549 D-
060e 01550 E-
060f 01551 F-
0610 01552 0 - 1.Event: Number+Group * * * * * *
0611 01553 1-
0612 01554 2-
0613 01555 3-
0614 01556 4-
0615 01557 5-
0616 01558 6-
0617 01559 7-
0618 01560 8 - 1.Event: Class + Quit * * * * * *
0619 01561 9-
061a 01562 A-
061b 01563 B-
061c 01564 C-

Database
20650 20660 20650 20650 20650 20650
061d 01565 D-
061e 01566 E-
061f 01567 F-
0620 01568 0-
0621 01569 1-
0622 01570 2-
0623 01571 3-
0624 01572 4-
0625 01573 5-
0626 01574 6-
0627 01575 7-
0628 01576 8-
0629 01577 9-
062a 01578 A-
062b 01579 B-
062c 01580 C-
062d 01581 D-
062e 01582 E-
062f 01583 F-
0630 01584 Century * * * * * *
0638 01592 Year * * * * * *
0640 01600 Month * * * * * *
0648 01608 Day * * * * * *
0650 01616 Hour * * * * * *
0658 01624 Minute * * * * * *
0660 01632 Second * * * * * *
0668 01640
0670 01648 0 - Event logger: Number+Group * * * * * *
0671 01649 1-
0672 01650 2-

Database
20650 20660 20650 20650 20650 20650
0673 01651 3-
0674 01652 4-
0675 01653 5-
0676 01654 6-
0677 01655 7-
0678 01656 8 - Event logger: Class + Quit * * * * * *
0679 01657 9-
067a 01658 A-
067b 01659 B-
067c 01660 C-
067d 01661 D-
067e 01662 E-
067f 01663 F-
0680 01664 0-
0681 01665 1-
0682 01666 2-
0683 01667 3-
0684 01668 4-
0685 01669 5-
0686 01670 6-
0687 01671 7-
0688 01672 8-
0689 01673 9-
068a 01674 A-
068b 01675 B-
068c 01676 C-
068d 01677 D-
068e 01678 E-
068f 01679 F-
0690 01680 0-
0691 01681 1-
0692 01682 2-
0693 01683 3-

Database
20650 20660 20650 20650 20650 20650
0694 01684 4-
0695 01685 5-
0696 01686 6-
0697 01687 7-
0698 01688 8-
0699 01689 9-
069a 01690 A-
069b 01691 B-
069c 01692 C-
069d 01693 D-
069e 01694 E-
069f 01695 F-
06a0 01696 0-
06a1 01697 1-
06a2 01698 2-
06a3 01699 3-
06a4 01700 4-
06a5 01701 5-
06a6 01702 6-
06a7 01703 7-
06a8 01704 8-
06a9 01705 9-
06aa 01706 A-
06ab 01707 B-
06ac 01708 C-
06ad 01709 D-
06ae 01710 E-
06af 01711 F-
06b0 01712 0-
06b1 01713 1-
06b2 01714 2-
06b3 01715 3-
06b4 01716 4-

Database
20650 20660 20650 20650 20650 20650
06b5 01717 5-
06b6 01718 6-
06b7 01719 7-
06b8 01720 8-
06b9 01721 9-
06ba 01722 A-
06bb 01723 B-
06bc 01724 C-
06bd 01725 D-
06be 01726 E-
06bf 01727 F-
06c0 01728 0-
06c1 01729 1-
06c2 01730 2-
06c3 01731 3-
06c4 01732 4-
06c5 01733 5-
06c6 01734 6-
06c7 01735 7-
06c8 01736 8-
06c9 01737 9-
06ca 01738 A-
06cb 01739 B-
06cc 01740 C-
06cd 01741 D-
06ce 01742 E-
06cf 01743 F-
06d0 01744 0-
06d1 01745 1-
06d2 01746 2-
06d3 01747 3-
06d4 01748 4-
06d5 01749 5 - Events are acknowleged * * * * * *

Database
20650 20660 20650 20650 20650 20650
06d6 01750 6 - Summary Warning 1 * * * * * *
06d7 01751 7 - Summary Warning 2 * * * * * *
06d8 01752 8-
06d9 01753 9 - MIN Control Level *
06da 01754 A - MAX Control Level *
06db 01755 B-
06dc 01756 C-
06dd 01757 D-
06de 01758 E-
06df 01759 F-
06e0 01760 0-
06e1 01761 1-
06e2 01762 2-
06e3 01763 3-
06e4 01764 4-
06e5 01765 5-
06e6 01766 6-
06e7 01767 7-
06e8 01768 8-
06e9 01769 9-
06ea 01770 A-
06eb 01771 B-
06ec 01772 C-
06ed 01773 D-
06ee 01774 E-
06ef 01775 F-
06f0 01776 0-
06f1 01777 1-
06f2 01778 2-
06f3 01779 3-
06f4 01780 4-
06f5 01781 5-
06f6 01782 6-

Database
20650 20660 20650 20650 20650 20650
06f7 01783 7-
06f8 01784 8-
06f9 01785 9-
06fa 01786 A-
06fb 01787 B-
06fc 01788 C-
06fd 01789 D-
06fe 01790 E-
06ff 01791 F-
0700 01792 0-
0701 01793 1-
0702 01794 2-
0703 01795 3-
0704 01796 4-
0705 01797 5-
0706 01798 6-
0707 01799 7-
0708 01800 8-
0709 01801 9-
070a 01802 A-
070b 01803 B-
070c 01804 C-
070d 01805 D-
070e 01806 E-
070f 01807 F-
0710 01808 0 - FB Event 01 * * * * * *
0711 01809 1 - FB Event 02 * * * * * *
0712 01810 2 - FB Event 03
0713 01811 3 - FB Event 04 * * * * * *
0714 01812 4 - FB Event 05 * * * * * *
0715 01813 5 - FB Event 06 * * * * * *
0716 01814 6 - FB Event 07 * * * * * *
0717 01815 7 - FB Event 08 * * * * * *

Database
20650 20660 20650 20650 20650 20650
0718 01816 8 - FB Event 09 * * * * * *
0719 01817 9 - FB Event 10 * * * * * *
071a 01818 A - FB Event 11 * * * * * *
071b 01819 B - FB Event 12 * * * * * *
071c 01820 C - FB Event 13 * * * * * *
071d 01821 D - FB Event 14 * * * * * *
071e 01822 E - FB Event 15 * * * * * *
071f 01823 F - FB Event 16 * * * * * *
0720 01824 0 - FB Event 17 * * * * * *
0721 01825 1 - FB Event 18 * * * * * *
0722 01826 2 - FB Event 19 * * * * * *
0723 01827 3 - FB Event 20 * * * * * *
0724 01828 4 - FB Event 21 * * * * * *
0725 01829 5 - FB Event 22 * * * * * *
0726 01830 6 - FB Event 23 * * * * * *
0727 01831 7 - FB Event 24 * * * * * *
0728 01832 8 - FB Event 25 * * * * * *
0729 01833 9 - FB Event 26 * * * * * *
072a 01834 A - FB Event 27 * * * * * *
072b 01835 B - FB Event 28 * * * * * *
072c 01836 C - FB Event 29 * * * * * *
072d 01837 D - FB Event 30 * * * * * *
072e 01838 E - FB Event 31 * * * * * *
072f 01839 F - FB Event 32 * * * * * *
0730 01840 0-
0731 01841 1-
0732 01842 2-
0733 01843 3-
0734 01844 4-
0735 01845 5-
0736 01846 6-
0737 01847 7-

Database
20650 20660 20650 20650 20650 20650
0738 01848 8-
0739 01849 9-
073a 01850 A-
073b 01851 B-
073c 01852 C-
073d 01853 D-
073e 01854 E-
073f 01855 F-
0740 01856 0-
0741 01857 1-
0742 01858 2-
0743 01859 3-
0744 01860 4-
0745 01861 5-
0746 01862 6-
0747 01863 7-
0748 01864 8-
0749 01865 9-
074a 01866 A-
074b 01867 B-
074c 01868 C-
074d 01869 D-
074e 01870 E-
074f 01871 F-
Tab. 5 : Fieldbus Status

Database
3.3.1.2.2 Read IEEE Values
hex dec Measurement Values Dimension VBW VBW VWF VLW VIF VMC
20650 20660 20650 20650 20650 20650
0750 01872 Feedrate kg/h * * * * * *
0752 01874 Totalizer 1 kg * * * * * *
0754 01876 Totalizer 2 kg * * * * * *
0756 01878 Totalizer 3 kg * * * * * *
0758 01880 Belt Load kg/m * * *
075a 01882 Load kg * *
075c 01884 Belt Speed m/s * * *
075e 01886 Speed rpm * *
0760 01888 Fill Weight kg *
0762 01890
0764 01892
0766 01894 Setpoint kg/h * * * *
0768 01896 Batch Actual Value kg * * * * * *
076a 01898 Batch Residual Amount kg * * * * * *
076c 01900 Perc. setpoint factor % * * * *
076e 01902 * *
0770 01904 Deviation % * * * *
0772 01906
0774 01908
0776 01910
0778 01912
077a 01914
077c 01916
077e 01918
0780 01920 Analog Output 1 mA * * * * * *
0782 01922
0784 01924
0786 01926
0788 01928
078a 01930
078c 01932
078e 01934
0790 01936
0792 01938 Belt Slip % * *
0794 01940 Belt Drift cm * *

Database
20650 20660 20650 20650 20650 20650
0796 01942 Relative Feedrate % * * * * * *
0798 01944 Relative Belt Load % * * *
079a 01946 External Setpoint kg/h * * * *
079c 01948 Batch Setpoint kg * * * * * *
079e 01950 Tachometer 1 Hz * * * * *
07a0 01952 Utilization LC % * * * * * *
07a2 01954 Loadcell VAP mV/V * * *
07a4 01956 Loadcell BIC mV/V * *
07a6 01958 Loadcell mV/V * * * * * *
07a8 01960 External Setpoint kg/h * * * *
07aa 01962 Relative Fill Weight % *
07ac 01964 Calibration Display 1 * * * * * *
07ae 01966 Calibration Display 2 * * * * * *
07b0 01968 Ys before Linearization % *
07b2 01970 Ys after Linearization % *
07b4 01972 DAE Utilization % *
07b6 01974 Differential of F kg/h *
07b8 01976 Bypass Adaptation *
07ba 01978
07bc 01980
07be 01982
07c0 01984 CFC: Measurement Time s *
07c2 01986 CFC: Number of Measurements *
07c4 01988 CFC: Current No *
07c6 01990 CFC: Mean Delta-F kg *
07c8 01992 CFC: Mean Flow Rate kg/h *
07ca 01994 CFC: Feed Constancy % *
07cc 01996 Nominal Belt Load kg/m * * *
07ce 01998 CFC: Feed Constancy g *
07d0 02000
07d2 02002
07d4 02004 Nominal Load kg * *
07d6 02006 Unlin. Flow Rate kg/h * *
07d8 02008 Actual Tare kg/m * * * * *
07da 02010
07dc 02012
07de 02014

Database
20650 20660 20650 20650 20650 20650
07e0 02016
07e2 02018
07e4 02020
07e6 02022
07e8 02024
07ea 02026
07ec 02028
07ee 02030
07f0 02032
07f2 02034
07f4 02036
07f6 02038
07f8 02040
07fa 02042 Relative Setpoint % * * * *
07fc 02044 Relative Load % * *
07fe 02046
0800 02048
0802 02050
0804 02052 Batch No. * * * *
0806 02054
0808 02056
080a 02058
080c 02060
080e 02062
0810 02064
0812 02066
0814 02068
0816 02070
0818 02072
081a 02074
081c 02076 Tachometer 2 Hz *
081e 02078
0820 02080 Belt Load Unlin. kg/m * * *
0822 02082
0824 02084
0826 02086
0828 02088

Database
20650 20660 20650 20650 20650 20650
082a 02090
082c 02092
082e 02094
0830 02096
0832 02098
0834 02100
0836 02102
0838 02104
083a 02106
083c 02108
083e 02110
0840 02112
0842 02114
0844 02116
0846 02118
0848 02120
084a 02122
084c 02124
084e 02126
0850 02128
0852 02130
0854 02132
0856 02134 Reload Setpoint kg * * * *
0858 02136 Reload Amount kg * * * *
085a 02138
085c 02140
085e 02142
0860 02144
0862 02146
0864 02148
0866 02150
0868 02152
086a 02154
086c 02156
086e 02158 Pulses Sensor PULS * *
0870 02160 BIC act. Tara mV/V * *
0872 02162 FC act. Deviation % *

Database
20650 20660 20650 20650 20650 20650
0874 02164 act. Number LFT-Mem. *
0876 02166
0878 02168
087a 02170
087c 02172
087e 02174
0880 02176
0882 02178
0884 02180
0886 02182
0888 02184
088a 02186
088c 02188 Deviation S1 % *
088e 02190
0890 02192 Controller Mag. S1 mA *
0892 02194
0894 02196
0896 02198
0898 02200
089a 02202
089c 02204
089e 02206
08a0 02208
08a2 02210
08a4 02212 Analog Output 2 mA * * * * * *
08a6 02214 Analog Input 1 mA * * * * * *
08a8 02216
08aa 02218
08ac 02220 Deviation abs. % * * *
08ae 02222
08b0 02224
08b2 02226
08b4 02228
08b6 02230
08b8 02232
08ba 02234
08bc 02236

Database
20650 20660 20650 20650 20650 20650
08be 02238 Analog Input 2 mA * * * * * *
08c0 02240 Analog Input 3 mA * * * * * *
08c2 02242
08c4 02244
08c6 02246
08c8 02248
08ca 02250
08cc 02252
08ce 02254
08d0 02256 Analog Output 3 mA * * * * * *
08d2 02258 Analog Output 4 mA * * * * * *
08d4 02260
08d6 02262
08d8 02264
08da 02266
08dc 02268
08de 02270
08e0 02272
08e2 02274
08e4 02276
08e6 02278
08e8 02280
08ea 02282
08ec 02284
08ee 02286
08f0 02288
08f2 02290
08f4 02292
08f6 02294
08f8 02296
08fa 02298
08fc 02300 Belt Load (average) kg/m *
08fe 02302
0900 02304
0902 02306
0904 02308
0906 02310

Database
20650 20660 20650 20650 20650 20650
0908 02312
090a 02314 Temperature °C * * * * * *
090c 02316
090e 02318 Totalizer 1 rounded * * * * *
0910 02320
0912 02322
0914 02324
0916 02326
0918 02328
091a 02330
091c 02332
091e 02334
0920 02336
0922 02338
0924 02340
0926 02342
0928 02344 Pulses Belt PULS * *
092a 02346 Rel. Batch Actual Value % * * * * * *
092c 02348
092e 02350
Tab. 6 : Fieldbus Measurement Values

Database
3.3.2 Events - Overview

Event VBW VBW VWF VLW VIF VMC
20650 20660 20650 20650 20650 20650
SY System Message
SY01 Event: Memory P14.02 P14.02 P13.02 P06.02 P11.02 P12.02
SY02
SY03
SY04
SY05
SY06
SY07
SY08 Event: Cyclic Communication P19.03 P19.03 P19.03 P18.03 P17.03 P18.03
SY09 Event: License Violation P14.13 P14.13 P13.14 P06.14 P11.11 P12.11
SY10 Event: Acyclic Communication P19.04 P19.04 P19.04 P18.04 P17.04 P18.04
SY11
SY12
SY13
SY14 Event: Simulation active P14.10 P14.10 P13.10 P06.10 P11.07 P12.07
SY15
SY16
SC Sequence Monitoring
SC01 Event: Setpoint Limited P13.11 P06.11 P11.08 P12.08
SC02 Event: Stand-By P06.14 P08.14 P06.06 P06.10
SC03 Event: Maint.Feeder Run P11.04 P11.04 P11.04 P16.04 P10.04 P11.04
SC04 Event: Maint. Electric P11.02 P11.02 P11.02 P16.02 P10.02 P11.02
SC05 Event: External Event 1 P14.11 P14.11 P13.12 P06.12 P11.09 P12.09
SC06 Event: External Event 2 P14.12 P14.12 P13.13 P06.13 P11.10 P12.10
SC07 Event: DAE active P11.09
SC08 Event: DAE Fault P11.10
SC09 Event: Gate Feedback P05.15
SC10 Event: T_Volum. P05.16
SC11
SC12
SC13
SC14
SC15

Database

20650 20660 20650 20650 20650 20650
SC16
WE Electrical System
WE01 Event: Power Failure P14.01 P14.01 P13.01 P06.01 P11.01 P12.01
WE02
WE03
WE04
WE05
WE06
WE07
WE08
WE09 Event: NAMUR Error Tacho P14.04 P14.04 P13.04 P06.04
WE10 Event: NAMUR Error Sensor P14.05 P13.05 P06.05
WE11 Event: NAMUR Error Tacho (2nd) P14.15
WE12 Event: LFT-Memory P25.03
WE13
WE14
WE15
WE16
WM Mechanic
WM01
WM02 Event: Slip P13.14 P12.14
WM03 Event: Belt Skew P13.12 P12.12
WM04 Event: Belt Drift P13.10 P12.10
WM05
WM06
WM07
WM08
WM09
WM10
WM11
WM12
WM13
WM14
WM15
WM16

Database

20650 20660 20650 20650 20650 20650
MF Material Flow
MF01
MF02
MF03
MF04
MF05
MF06 Event: Out of Tolerance P09.06 P09.06 P09.05 P15.08 P09.05 P09.05
MF07
MF08
MF09
MF10
MF11
MF12
MF13
MF14
MF15
MF16
IL Interlock
IL01 Event: Run Disabled P14.07 P14.07 P13.07 P06.07 P11.04 P12.04
IL02
IL03
IL04
IL05
IL06
IL07
IL08
IL09
IL10
IL11
IL12
IL13
IL14
IL15
IL16
CO Controller
CO01 Event: Controller Limited P14.10 P09.25 P12.09 P13.09

Database

20650 20660 20650 20650 20650 20650
CO02 Event: MIN Flow Gate P22.09 P24.09
CO03 Event: MAX Flow Gate P22.11 P24.11
CO04
CO05
CO06
CO07 Event: Batch Setpoint MIN P09.14
CO08 Event: Batch Actual Value MIN P09.15
CO09 Event: Batch > Setpoint P09.08 P09.08
CO10
CO11
CO12
CO13
CO14
CO15
CO16
CH Check Measurement
CH01
CH02
CH03
CH04
CH05
CH06
CH07
CH08
CH09
CH10
CH11
CH12
CH13
CH14
CH15
CH16
CA Calibration
CA01 Event: Error LC Input P14.06 P14.06 P13.06 P06.06 P11.03 P12.03
CA02 Event: Tachometer Input P14.03 P14.03 P13.03 P06.03
CA03

Database

20650 20660 20650 20650 20650 20650
CA04
CA05 Event: Linearization Error P15.10 P15.10 P15.10 P10.10 P13.10 P14.10
CA06 Event: Tare Correction P08.05 P08.05 P08.04 P08.04
CA07
CA08
CA09
CA10
CA11 Event: Tachometer Input (2nd) P14.14
CA12 Event: Tare Difference > MAX P08.10 P08.10 P08.06
CA13 Event: Time elapsed P08.07 P08.07
CA14 Event: Tacho Comparison P14.16
CA15
CA16
HI MAX
HI01 Event: LC Input > MAX P14.08 P14.08 P13.08 P06.08 P11.05 P12.05
HI02 Event: Actual Flow Rate MAX P06.04 P06.04 P06.04 P08.04 P06.04 P06.04
HI03 Event: Load MAX P06.08 P06.08 P06.08
HI04 Event: Speed MAX P06.12 P06.12 P06.12
HI05 Event: Deviation P14.09 P09.24 P12.07 P13.07
HI06 Event: Fill Weight-Max P08.08
HI07 Event: Speed-Max P08.12
HI08 Event: HUBmax P05.08
HI09 Event: Maximum Load P06.06
HI10
HI11
HI12
HI13 Event: FC-MAX Limit P21.06
HI14
HI15
HI16
LO MIN
LO01 Event: LC Input < MIN P14.09 P14.09 P13.09 P06.09 P11.06 P12.06
LO02 Event: Actual Flow Rate MIN P06.02 P06.02 P06.02 P08.02 P06.02 P06.02
LO03 Event: Load MIN P06.06 P06.06 P06.06
LO04 Event: Speed MIN P06.10 P06.10 P06.10
LO05

Database

20650 20660 20650 20650 20650 20650
LO06 Event: Fill Weight-Min P08.06
LO07 Event: Speed-Min P08.10 P06.08
LO08 Event: AMOUNT min P05.06
LO09
LO10
LO11
LO12
LO13 Event: FC-MIN Limit P21.05
LO14
LO15
LO16
Tab. 7 : Fieldbus Events

Fieldbus Connections
4 Fieldbus Connections
This chapter describes the functionality of the fieldbus connections, an option that can be selected for the
weighing system.
Whereas previous chapters described the similarities with respect to the database, from this point on the
special characteristics of the different connections will be described in separate subsections.
Each fieldbus description contains information on commissioning, functionality, data exchange, payload
structure and parameterization.
In fieldbus mode the plant control system (PLC/PCS) behaves as a master and a connected scales controller
as a server.
4.1 PROFIBUS DP
PROFIBUS DP is the abbreviation of 'Process field bus Decentralized Periphery'. This is not to be confused
with the PROFINET standard for industrial Ethernet networks.
The PROFIBUS protocol is specified by the standard EN 50170. There are three main specifications for
PROFIBUS (communication protocols):
1. PROFIBUS FMS (Fieldbus Message Specification)
2. PROFIBUS DP (Decentralized Periphery)
3. PROFIBUS PA (Process Automation)
Of these the scales electronics supports only PROFIBUS DP (-V0, -V1).
The fieldbus interface used in the weighing electronics for a PROFIBUS connection is described in chapter
'PROFIBUS Module VPB 28020'.
A twisted cable pair based on the RS485 standard is the physical transmission medium for the bus. The
maximum length depends on the baud rate and is between 100 and 1200 meters.
32 nodes can be connected in the same network segment without a repeater. Up to 127 nodes can be con-
nected in the network if repeaters are used, including the repeater itself and the master stations.
Repeaters do not require a distinct station address but they nevertheless count when
determining the maximum number of devices permitted in a segment.
If a new node is added the master must be informed of its characteristics. This is done by installing a *.gsd
configuration file. This file contains information on the new node's available functions. Further information
can be found in the chapter 'PROFIBUS-Master Settings'.
The slave settings are made using parameters. Further information can be found in the chapter 'PROFIBUS
Slave Settings'.

4.1.1 Guidelines for Commissioning

1. The hardware is prepared as per the system description (see 'PROFIBUS Interface VPB 28020').
2. Determine the payload structure (as described above).
3. In PROFIBUS DP mode: determine the data to be transmitted - the identifiers (IDs) of the data will be
required.
4. Create the master parameter sets using the GSD file.
5. Setting up device parameters.
Important: The transmission of the parameters onto the interface module can last up to 30 s!
.Verify: the 'Status' LED (H110 or H120 above) on interface module VPB8020 must be a steady
green, i.e. status = 'initialized'.
6. The master will begin communication.
7. Use the service tool to monitor the interface.
Please refer to chapter 'Notes on PROFIBUS' for diagnostics and troubleshooting.
4.1.2 Functionality of the PROFIBUS Connection

▪ Certified connection as per standard EN 50170.
▪ Cyclic (DP-V0) and optional acyclic (DP-V1) payload data exchange with the master.
▪ Automatic baud rate detection.
▪ Bus interface monitoring.
▪ Simple parameterization of the VPB 28020 using the operating panel or the service tool.
▪ PROFIBUS control command SYNC support for synchronized data transmission from master to sev-
eral slaves.
▪ PROFIBUS control command FREEZE support for synchronized data transmission from several
slaves to the master.
▪ 'Fail-safe: Clear' state supported.
▪ No operator-specific diagnostic functions.
▪ No alteration of the station address via bus.
▪ The bus termination can be realized at the interface connection or externally.

4.1.3 Configuration of the PROFIBUS Connection
4.1.3.1 Settings at the PROFIBUS Slave

Parameterization can be done both from the operating console and the 'EasyServe' service tool. The param-
eter description applies to both options.
The settings for fieldbus communication can be monitored via WEB server.
NOTE: Detailed description of the parameters:

Refer to the chapter 'Parameters' in the respective INTECONT Tersus operating manu-
al.
Settings in the block ' Communication Fieldbus '
The parame- Value range Default value Explanation

ters
1)
Protocol Type NO NO Selects the protocol
Modbus-RTU here: PROFIBUS DP
PROFIBUS DP
DeviceNet
Modbus-TCP
PROFINET IO
EtherNet/IP
Timeout Host 1 … 600 s 5s Monitors the interface
Event: Cyclic A (Alarm) A Sets the event class for 'Error Range Un-
Communication W1 (Warning 1) derrun/Exceeded during Cyclic Communication +
W2 (Warning 2) Timeout + ID Verification'
IG (Ignore)
Event: Acyclic W2 (Warning 2) A Set the event class for 'Error Range Un-
Communication W1 (Warning 1) derrun/Exceeded during Acyclic Communication'
IG (Ignore)
A (Alarm)
Check in Key- NO YES The fieldbus communication monitoring in keyboard

board Mode YES mode can be activated/deactivated.
1)
Configuration NO_PARA_ID_3_6 FIXED_8_8 Used to configure the structure and meaning of the
PARA_ID_2_4 payload in the transmission protocol.
PARA_ID_3_6 Selection process image :
FIXED_8_8 FIXED …: Transmission via '»Simplified Payload
FIXED_4_4 Structure (FIXED Mode) [➙14]«'
All others: Transmission using '»General Payload
Structure (VARIABLE Mode) [➙21]«'
1)
Address 0 … 126 16 Address of the INTECONT Tersus (slave) at the
PROFIBUS
FLOAT-Format SIEMENS-KG IEEE Format for FLOAT values (all setpoints, measured
IEEE values, floating point parameters)


ters
Compatiblity NO NO This parameter ensures the compatibility to earlier

INTECONT YES devices (INTECONT PLUS). This means that any
connected INTECONT Tersus will behave as a mas-
ter towards the INTECONT PLUS.
If YES is chosen the PROFIBUS ident number 0C9B
will be replaced with 0524 Es sind die GSD-Datei und
die Bausteine (CFC & STEP7) für das Vorgängermo-
dell zu verwenden. The GSD file and the modules
(CFC & STEP7) must be used for the earlier model.
Identifier format BYTE BYTE This parameter will lead to another description of the
WORD data structure of every input data and source data
If the program is in the INTECONT PLUS compatibil-
ity mode this parameter should only be switched to
WORD under certain conditions.
Mind the notes on GSD files.
PA32 compatib- NO NO The selection of YES will ensure the compatibility to

2)
le YES preceding hardware components (VPB020) by ex-
panding the process images (PA) NO_PARA_ID_3_6
and PARA_ID_2_4 to 32 Bytes in the INTECONT
PLUS compatibility mode.
1)
these parameters are subject to the 30 s condition for transfer to the interface card (see chapter
'»Guidelines for Commissioning [➙89]«').
2)
This parameter is shown only if parameter Compatiblity INTECONT = YES.
4.1.3.2 Settings at the PROFIBUS Master (PCS)

The characteristic communication features of a PROFIBUS device are specified in the form of an electronic
device data sheet, the so-called GeräteStammDaten file (Device Master Data file), or 'GSD file' for short.
This file is the obligatory 'identity card' of every PROFIBUS component and is supplied by the device manu-
facturer. It contains all of the characteristics of a device such as specifications, protocols, details on its com-
munication capabilities and other information on e.g. diagnostics values. GSD files allow the possibility of an
open configuration tool by reading the device information and identifying the device characteristics. The for-
mat of GSD files is clearly defined by the PROFIBUS standard. The configuration tool loads the GSD files
into its internal database and incorporates all of the characteristics of the individual devices. This has the
advantage of greatly simplifying configuration, allowing it to be made using a manufacturer-independent con-
figuration tool.
Where can I find the device configuration files?

A) These files for your device can be downloaded at the following internet address:
http://support.schenckprocess.com
1. You can use the 'Product Family Filter' to facilitate finding the desired data packet. Open the list and
mark the corresponding product family.
2. Click onto the magnifying-glass symbol (on the corresponding one if there are multiple entries), open-
ing a link to the related archive file (*.ZIP).

3. Click on the link to begin the download.

4. *) Select [Save] and then the target directory for the archive file.
5. *) Select [Open] to unzip the program.
6. Extract the contents of the archive file to the desired location.
*) The dialog steps described above may not appear and the contents of the archive file may be
listed immediately depending on your Windows configuration.
B) In tandem with this, DISOCONT Tersus and INTECONT Tersus store the current device configuration file
'On Board'. You can download this file using the service tool 'EasyServe' as follows:
1. Use menu item ' | | ' to show the device's 'Home Page'.
2. Click 'Fieldbus Configuration' in the navigation bar and select whether you wish to download or open
the file.
3. Extract the files from the archive file that correspond to your fieldbus.
How do I use the device master data files?

In a GSD file, each selectable payload format is described by exactly one GSD module ('PPO type').
The following table shows the correct use of the files:
File PROFIBUS mode Structure of the user data for the scales elec- Step7 or CFC
tronics
ITE10C9B.GSD PROFIBUS DP-V1 INTECONT Tersus: VSP 28002

General and fixed payload structure VPD 28002
(DP-V1 → Cyclic and acyclic services)
So-called 'identifier bytes' are transmitted in the PROFIBUS DP master configuration telegram with which the
PPO type of the payload telegram is established.
If an unknown identifier-byte combination is received, the module VPB 28020 will set the 'Con-
figuration Error' bit in the diagnostics telegram to the PROFIBUS DP master (refer to the LEDs
at the interface).

4.1.3.2.1 Integration Slave

The slave (in this case: INTECONT Tersus) is integrated using the program 'SIMATIC Hardware Configura-
tor'. You can find the components required (configuration) via the tree structure as follows (see figure):
PROFIBUS DP | Further FIELD DEVICES | Controller | INTECONT Tersus | …
Integration is a two-part process using Drag & Drop:
1. 'Hook' the IO device into the bus line (black dash)
2. Enter the payload structure into the table (→ module from GSD file)
(Example uses DISOCONT Tersus)

Notes (all modes) on S7:

▪ Reading-writing of double words in S7 systems:
Please note that the INTECONT Tersus double words cannot be read or written with
the S7 system function blocks SFC14 or SFC15. Instead, use direct peripheral ac-
cess.
A) How can I tell which GSD module has been selected as per the current parameter settings at the
slave and that needs to be set at the master?
Start the function 'Browse Controller' in the EasyServe menu under 'Tools' → 'Start' and select 'Identifica-
tion & Maintenance' to call up the following notice:

In the 'Fieldbus' section the relevant module name can be read in the line 'GSD/GSDML Module', e.g.
FIXED_8_8.

B) An overview of the GSD modules:

1) PROFIBUS DP VARIABLE Mode (general payload structure)
GSD module:
NO_PARA_ID_3_6 No parameter range 3 presets 6 read values

PARA_ID_3_6 With parameter range 3 presets 6 read values
PARA_ID_2_4 With parameter range 2 presets 4 read values
2) PROFIBUS DP → FIXED Mode (Fixed payload structure)

GSD module:
FIXED_8_8 No parameter range 8 presets 8 read values

FIXED_4_4 No parameter range 4 presets 4 read values
3) Relationship between INTECONT Tersus parameter 'Configuration' and the GSD module with
PROFIBUS DP
There is exactly one GSD module for each selectable payload format. The names of the modules have been
selected so that they suggest the size of the transmitted payload.
Structure of the GSD module name for INTECONT Tersus Payload Formats:
FIXED mode, e. g.:
VARIABLE mode, e. g.:
Format as per par. 'Configuration': → GSD module name:
FIXED_4_4 FIXED_4_4
FIXED_8_8 FIXED_8_8
NO_PARA_ID_3_6 NO_PARA_ID_3_6
PARA_ID_3_6 PARA_ID_3_6
It is not difficult here to identify the correct GSD module.

4.1.4 PROFIBUS Module VPB8020

The module can be attached to the mainboard to create an interface to the PROFIBUS.
Module properties
Galvanic isolation Optocoupler
Power supply +5 VDC internal
Power supply max. 310 mA
Plug connector to the bus activation XP1: D-Sub 9-pole

XP3: clamp 5-pole
Arrangement of the components
Fig. 1: VPB 28020 PROFIBUS module layout drawing
Settings
W100 Determining the power supply:

The W100 jumper must be plugged in position 2 - 3
W150 Bus termination:

The bus termination resistances must be activated at the first and last station of the bus. This is done by
W151
setting all 3 jumpers on the board (W150, W151, W152) to position 1 - 2. By default the resistances are not
W152 activated (position 2 - 3).
Bus address:
The address is set using parameters.
Pin XP1 XP3

Signal Signal
*)
1 - B, RxD/TxD-P
**)
2 - A, RxD/TxD-N
*) ***)
3 B, RxD/TxD-P DGND (0 V)
***)
4 CNTR-P (Control-P) VP (+5 V)
***)
5 DGND (0 V) SHIELD
***)
6 VP (+5 V) -
7 - -

Pin XP1 XP3

Signal Signal
**)
8 A, RxD/TxD-N -
9 - -
Housing SHIELD -
Tab. 8 : 'Bus activation' connector
*)
Colour of conductor red
**)
Colour of conductor green
***)
Power supply for external bus terminal
We recommend that the bus cable shield is attached to the fitting panel at the intended points (provided on
almost all Schenck Process electronic components). Then the connection to the SHIELD contact of the
XP1/XP3 connectors can be omitted.
LEDs H110, H120

There is one identical-function double-LED (H110, H120) for each connection to the bus activation (XP1,
XP3).
Example H110:
Fig. 2: Light-emitting diodes – VPB 28020 front view
Status Display
off not online/no power supply
green online, data transfer
green, flashing online, clear mode
red, flashing (1 Hz) parameterization fault
red, blinking (2 Hz) configuration error
Tab. 9 : LED 'Operating Mode' (below)
Status Display
off no power supply or not initialized
green initialized
green, flashing initialized, result of diagnostic test pending
red exception error
Tab. 10 : LED 'Status' (above)

4.1.5 Acyclical Data PROFIBUS

Data instance Model Example Byte Index Direction
(Typical response or explanation) (Specified payload) count *)
Class 162/A2
Slot 0 hex dec dec/hex
Read device name ASCII 40 128/0x80 S→M
Write device name *)

ASCII 4D 79 20 46 65 65 64 65 72 40 178/0xB2 M→S
(e.g. 'My Feeder')
Read the scales' software version ASCII 40 134/0x86 S→M
Highest-priority event – read short text ASCII 12 121/0x79 S→M

(e.g. 'WE01')
Highest-priority event - read long text ASCII 40 122/0x7A S→M

(e.g. 'Event: Power Failure')
Highest-priority event - read short and long ASCII 68 135/0x87 S→M

texts
(e.g. 'WE01 Event: Power Failure')
Read all displayed events - short text ASCII 68 131/0x83 S→M

Max. 17 events, 4 characters/event
(e.g. 'WE01 …')
Call up the time, number and the counter value ASCII 2014-05-21 14:12:03 68 140/0x8C S→M
of the most recent log in the legal-for-trade No: 137
memory with an acyclic telegram. CR: 888170 kg
Read all displayed events Binary 68 132/0x84 S→M

Max. 17 events, 4 bytes per event
Event group, number, class, acknowledgement
(e.g. '03 01 01 00 … ')
Write a process or parameter value *) Binary 0250 42C80000 6 174/0xAE M→S

(ID, Value)
(e.g. 'Serial Setpoint = 100 kg/h')
Write one or multiple process or parameter Binary 0250 42C80000 66 175/0xAF M→S
values*) 0252 41200000
(ID, Value; ID, Value; … ) 0000 00000000 ….
Max. 11 values
The evaluation ends at the next ID with a ZERO
value.
(e.g. 'Serial Setpoint = 100 kg/h,
Serial Batch Setpoint = 10 kg')


(Typical response or explanation) (Specified payload) count *)
Class 162/A2
Slot 0 hex dec dec/hex
Write a read ID 1) *) Binary 0250 2 176/0xB0 M→S

Subsequently the ID can be read multiple times
(see next line)
Read a process or parameter value whose ID Binary 6 126/0x7E S→M

was sent beforehand 1)
[ID Value]
Read all preset value IDs of the parameter Binary 16 129/0x81 S→M
block 'Fixed mode configuration'
(e.g. '0140 0160 0180 0250 0252 0100 …')
Set all preset values IDs of the parameter block Binary 0140 01A0 … 16 179/0xB3 M→S
'Fixed mode configuration' *) CAUTION: The 1st transmitted
ID must always be 0140
(→'Fieldbus Clearance')
Read all read IDs of the parameter block 'Fixed Binary 32 130/0x82 S→M
mode configuration'
(e.g. '02F0 0310 0610 0750 …')
Set all read IDs of the parameter block 'Fixed Binary 0752 0754 … 32 180/0xB4 M→S
mode configuration' *)
Read date and time Binary 0C030F 0B1000 6 138/0x8A S→M

(yymmdd hhmmss)
Write date and time *) Binary 0C030F 0B1000 6 188/0xBC M→S

(yymmdd hhmmss)
*)
The quantity of bytes given in the 'Byte Count' column must always be sent when performing a write opera-
tion. Unused bytes must be replaced by zero if the information to be transmitted is shorter.
1)
The read ID must be written before the data can be read.

4.1.6 Supplementary Documentation
European Standard EN50170

PROFIBUS user organization www.profibus.com
*)
BV-H2387AA CFC module description
*)
BV-H2245AA CFC module description(INTECONT)
*)
BV-H2426 STEP7 library
*)
BV-H2427AA Module description for PCS7
*)
BV-H2315 STEP7 library
BV-H2466AA DP-V1 component, manual
*)
PB Siemens S7
4.2 DeviceNet

1. Preparation of the hardware as described in the system manual.
Refer to chapter 'Fieldbus Interface', section 'DeviceNet Interface VCB 28020'.
2. Determine the payload structure (as described above).
3. In DeviceNet mode: determine the data to be transmitted – the identifiers (IDs) of the data will be re-
quired.
4. Creating master parameter sets using the EDS file.
5. Setting the controller parameters.
Important: The transmission of modified parameters to the interface card can take up to 30 s!
Verification: the led 'Module Status' (H110 below or H120 below) on the interface card VCB 28020
must light a steady green, i. e. status = 'initialized'.
6. The master will begin communication.
7. Use the service tool to monitor the interface.
Please refer to chapter 'Notes on DeviceNet' for diagnostics and troubleshooting.
4.2.2 Functionality of the DeviceNet Connection

▪ Certified connection in accordance with DeviceNet specification 2.0
▪ Data is exchanged with the master cyclically. As a rule the POLL mode is used for transmitting I/O
data.
▪ Monitoring the bus interface
▪ Simple parameterization of the VCB 28020 using the operating panel or the service tool.
▪ The bus termination can be realized at the interface connection or externally.
▪ Acyclic data exchange (Explicit Messaging) is supported.

The process control system (PCS) is the bus master and the controllers are treated as individual slaves. One
telegram cycle always consists of a query from the bus master and a reply from the slave. The bus master
cyclically acquires a process image of the controller and cyclically transmits a command telegram to the con-
troller.
4.2.3 Configuration of the DeviceNet Connection
4.2.3.1 DeviceNet Slave Settings

Parameterization can be done both from the operating console and the 'EasyServe' service tool. The para-
meter description applies to both options.

Refer to chapter 'Parameter' in the INTECONT Tersus operating manual.
The parameters Value range Default value Explanation

1)
Modbus-RTU here: DeviceNet
PROFIBUS DP
DeviceNet
Modbus-TCP
PROFINET IO
EtherNet/IP
Event: Cyclic A (ALARM) A Sets the event class for 'Error Range Un-
IG (Ignore)
IG (Ignore)
A (ALARM)

Word Sequence I:std/L:std I:std/L:std Establish the word sequence during the transmission
I:swp/L:std of measured values in IEEE/LONG format
I:std/L:swp
I:swp/L:swp
Byte Sequence High - Low High - Low Establish the byte sequence within a data word
Low - High


1)
PARA_ID_3_6 Selection process image :
FIXED_8_8 FIXED …: Transmission via 'Simplified Payload
FIXED_4_4 Structure'
All others: Transmission using 'General Payload
Structure (VARIABLE Mode)'

If YES is chosen the product code of the INTECONT
PLUS is used. The EDS file for the preceding model
must be used.
PA32 compatible NO NO under circumstances the process images (PA)

2)
YES NO_PARA_ID_3_6 and PARA_ID_2_4 must be filled
up to 32 bytes in the INTECONT PLUS compatibility
mode. This ensures the compatibility to earlier hard-
ware components.
1)
Address 0 … 126 63 Address of the INTECONT Tersus (slave) at the
CAN bus
Baud rate 125K 125K The baudrate must match that of the master system.
250K
500K
1)
these parameters are subject to the 30 s condition for transfer to the interface card (see chapter 'Guide-
lines for Commissioning').
2)
This parameter is shown only if parameter Compatiblity INTECONT = YES.
4.2.3.2 DeviceNet Master Settings (PCS)

Every manufacturer of a DeviceNet device must provide the device with an electronic device data sheet, a
so-called EDS file (Electronic Data Sheet).
The EDS file describes in a standardized text format all communications parameters such as e.g. the baud
rates supported by the device.
Configuration tools can read EDS files and, with their help, communicate with the respective device and pa-
rameterize it if required.

the file.
How do I use the device configuration files?

File DeviceNet mode Structure of the user data for the scales electronics
INTECONT_Tersus_EDS.zi INTECONT Tersus:

p General and fixed payload structure
Intecont_eds2.zip compatible modules with INTECONT PLUS
4.2.4 DeviceNet Module VCB8020

The module can be attached to the mainboard to create an interface to the DeviceNet.
Module properties
Plug connector to the bus activation XC1: Clamp 5-pole

XC3: clamp 5-pole

Fig. 3: VCB 28020 DeviceNet module layout drawing
Settings


applying the W160 jumper to the position 1 - 2.
By default the resistances are not activated (Position 2 - 3).
Bus addresses and baud rate:

Both values are set using parameters.
Pin XC1 XC3

Signal Signal
1 V-
2 CAN_L
ditto.
3 Shielding
4 CAN_H
5 V+
LEDs H110, H120

There is one identical-function double-LED (H110, H120) for each connection to the bus activation (XC1,
XC3).
Example H110:
Fig. 4: VCB 28020:XC1 DeviceNet module front view
Network status Display
green online, one or more connections established

green, flashing online, no connection
red critical connection error
red, flashing (1 Hz) one or more connections have been timed out
alternating red-green self-test
Tab. 12 : LED 'Network Status' (above)
Module status Display
off no power supply
green exchange of user data
green, flashing incorrect configuration
red non-repairable error
red, flashing repairable error
Tab. 13 : LED 'Module Status' (below)
4.2.5 Acyclical Data (Explicit Messages) DeviceNet

Data instance Model Example Byte count Instance Service
*)
(Typical response or explanation) (Specified payload)
Class 162/A2
Attribute 5 hex dec dec/hex dec/hex
Read device name ASCII 40 129/0x81 14/0x0E
write device name *) ASCII 4D 79 20 46 65 65 64 65 72 40 179/0xB3 16/0x10

(e.g. 'My Feeder')
Read the scales' software version ASCII 40 135/0x87 14/0x0E
Highest-priority event – read short text ASCII 12 122/0x7A 14/0x0E

(e.g. 'WE01')
Highest-priority event - read long text ASCII 40 123/0x7B 14/0x0E

Highest-priority event - read short and ASCII 68 136/0x88 14/0x0E

long texts
Read all displayed events - short text ASCII 68 132/0x84 14/0x0E

(e.g. 'WE01 …')


*)
Class 162/A2
Call up the time, number and the counter ASCII 2014-05-21 14:12:03 68 141/0x8D 14/0x0E
value of the most recent log in the legal- No: 137
for-trade memory with an acyclic tele- CR: 888170 kg
gram.
Read all displayed events Binary 68 133/0x85 14/0x0E

Event group, number, class, acknowl-
edgement
(e.g. '03 01 01 00 … ')
Write a process or parameter value *) Binary 0250 42C80000 6 175/0xAF 16/0x10

(ID, Value)
Write one or multiple process or parame- Binary 0250 42C80000 66 176/0xB0 16/0x10
ter values*) 0252 41200000
(ID, Value; ID, Value; … ) 0000 00000000 …
Max. 11 values
The evaluation ends at the next ID with a
ZERO value.
Write a read ID 1) *) Binary 0250 2 177/0xB1 16/0x10

Subsequently the ID can be read multiple
times (see next line)
Read a process or parameter value Binary 6 127/0x7F 14/0x0E

whose ID was sent beforehand 1)
[ID Value]
Read all preset value IDs of the parame- Binary 16 130/0x82 14/0x0E
ter block 'Fixed mode configuration'
(e.g. '0140 0160 0180 0250 0252 0100
…')
Set all preset values IDs of the parameter Binary 0140 01A0 … 16 180/0xB4 16/0x10
block 'Fixed mode configuration' *) CAUTION: The 1st transmitted ID must
always be 0140 (→'Fieldbus Clear-
ance')
Read all read IDs of the parameter block Binary 32 131/0x83 14/0x0E
'Fixed mode configuration'
(e.g. '02F0 0310 0610 0750 …')


*)
Class 162/A2
Set all read IDs of the parameter block Binary 0752 0754 … 32 181/0xB5 16/0x10
'Fixed mode configuration' *)
Read date and time Binary 0C030F 0B1000 6 139/0x8B 14/0x0E

(yymmdd hhmmss)
Write date and time *) Binary 0C030F 0B1000 6 189/0xBD 16/0x10

(yymmdd hhmmss)
*)
1)
DeviceNet specification Version 2.0 (ODVA)

Bosch CAN specification Version 2.0 (Sept. 1991)
DeviceNet user organization www.odva.com
4.2.7 DeviceNet Module VCB 28020

The module can be attached to the mainboard to create an interface to the DeviceNet.
Module properties
Plug connector to the bus activation XC1: Clamp 5-pole

XC3: clamp 5-pole
Fig. 5: VCB 28020 DeviceNet module layout drawing

Settings


applying the W160 jumper to the position 1 - 2.
By default the resistances are not activated (Position 2 - 3).
Bus addresses and baud rate:

Both values are set using parameters.
Pin XC1 XC3

Signal Signal
1 V-
2 CAN_L
ditto.
3 Shielding
4 CAN_H
5 V+
LEDs H110, H120

There is one identical-function double-LED (H110, H120) for each connection to the bus activation (XC1,
XC3).
Example H110:
Fig. 6: VCB 28020:XC1 DeviceNet module front view
green online, one or more connections established
green, flashing online, no connection
red critical connection error
red, flashing (1 Hz) one or more connections have been timed out
Tab. 15 : LED 'Network Status' (above)
off no power supply
green exchange of user data

green, flashing incorrect configuration
red non-repairable error
red, flashing repairable error
Tab. 16 : LED 'Module Status' (below)
4.3 PROFINET IO
NOTICE
MULTICAST services may overload the network!
MULTICAST services (e.g. webcam streams) may overload the weighing
electronics processor if they are used within the weighing electronics net-
work. Use only switches in the weighing electronics network that support
IGMP (Internet Group Management Protocol) for IPv4 or MLD (Multicast
Listener Discovery) for IPv6.
The PROFINET IO protocol is specified by the IEC 61158 standard.

The fieldbus interface used in the weighing electronics for a PROFINET IO connection is described in chap-
ter 'PROFINET Interface VPN8020'.
If a new node is added the IO controller must be informed of its properties. This is done by installing a
*.GSDML configuration file. This file contains information on the new node's available functions. Further in-
formation can be found in the chapter 'Settings at the PROFINET IO Controller'.
The IO device is set via parameters. Further information can be found in the chapter 'Settings at the
PROFINET IO Device'.

Preparation of the hardware as per the system description (see PROFINET Interface VPN8020). All stand-
ard, screened cables with an RJ45 plug that conform to ISO/IEC 11801 Version 2.0, Category 5 can be
used. The integrated switch supports the implementation either of a line, star or ring topology and offers au-
to-crossing functionality, i.e. either patch or crossover cables can be used to make the connection with the
next Ethernet subscriber.
Note: Details about the possible topologies, see System Manual.
The maximum cable length for 10/100 Mbps Ethernet (10BASE-T/100BASE-T) is 100 m.
1. Ensure that the bus cable is installed and screened correctly. The steps to be taken are described in
detail in the PROFIBUS user organization guidelines. Detailed information on the wiring and use of
switches can be found in the brochures 'Installation Guideline PROFINET' and 'Part2: Network Com-
ponents'.
Refer also to chapter Supplementary Documentation.
2. Specifying the payload structure (see parameter Configuration in chapter Settings at the PROFINET
IO Device). The identifiers (IDs) of the data will be required.
3. Creating IO controller parameter sets using the GSDML file.

4. Setting the device parameters.

Important: The transfer to the interface card of modified parameters can take up to 30 s!
5. PROFINET IO controller starts communication.
6. Monitoring of the interface using the service tools EasyServe or DISOPLAN (depending on the weigh-
ing electronics).
Alternatively the external tool Wireshark can be used.
Please refer to chapter Notes for PROFINET IO for diagnostics and troubleshooting.
4.3.2 Functionality of the PROFINET Connection

▪ The properties of the interface board VPN8020 conform to IEC 61158. It supports:
– Communication Class RT
– Conformance Class B
– Redundancy Class MRP (200 ms)
▪ Cyclic (IODATA) and optional acyclic (RECORD DATA) payload exchange with the IO controller
▪ Data rate: 100 Mbps Full Duplex
▪ The operating console or service tool EasyServe or DISOPLAN (depending on the weighing electron-
ics) can be used to easily parameterize the VPN8020
▪ No operator-specific diagnostic functions
▪ The station name and IP parameters are set by the PROFINET IO-Controller gesetzt.
▪ The replaced IO device is assigned the device name from the IO-Controller, provided that the new
PROFINET hardware has the status "factory settings", i.e., IP address and name are deleted. The IO-
Controller uses the projected topology for this and the neighbor relationships calculated by the IO de-
vices.
Note:
So that the equipment swap works without removable medium, the topology of the system must be
projected correctly. Use the topology editor to do this.
▪ The device model is based on slot and subslot mechanisms with which modular devices can be as-
sembled using slots for modules and submodules. The devices are designed as compact devices, i.e.
a module is always 'plugged' into a slot (slot1) in which all input and output data are mapped.
*) Not to be confused with the values shown in EasyServe menu ' | '.

4.3.3 Configuration of the PROFINET Connection
4.3.3.1 Settings at the PROFINET IO Device

Parameterization can be done both from the operating console (VHM) and the 'EasyServe' service tool. The
parameter description applies to both options.

Refer to chapter 'Parameter' in the INTECONT Tersus operating manual
Settings in the blockCommunication Fieldbus

ters
1)
Modbus-RTU here: PROFINET IO
PROFIBUS DP
DeviceNet
Modbus-TCP
PROFINET IO
EtherNet/IP
Timeout Host 1 … 600 s 10 s Monitors the interface
Event: Cyclic A (Alarm) IG Sets the event class for 'Error Range Un-
IG (Ignore)
Event: Acyclic W2 (Warning 2) IG Set the event class for 'Error Range Un-
IG (Ignore)
A (Alarm)

1)
Configuration PARA_ID_3_6 FIXED_8_8 Used to configure the structure and meaning of the
FIXED_8_8 payload in the transmission protocol.
Auswahl Prozessabbild:
FIXED …: Übertragung mittels 'Simplified Payload
Structure (Fixed Mode)'
PARA ….: Übertragung mittels 'General Payload
Structure (Variable Mode)'
1)
these parameters are subject to the 30 s condition for transfer to the interface card (see chapter
'»Guidelines for Commissioning [➙111]«').
With PROFINET IO the IP address parameters are set by the DCP (Discovery and Configuration Protocol)
protocol. DCP uses device names. The device name identifies uniquely a PROFINET IO subscriber in the
network. It is communicated by the PROFINET IO controller when the subscriber is projected and also set in
the PROFINET IO device using the project planning software. When the device is starting up its device name
is identified by the controller which then sends the corresponding IP address parameters. Settings need

therefore no longer be made directly at the slave but can be monitored there on the 'Identification & Mainte-
nance' website. The general approach is described in chapter 'Settings at the PROFINET IO Controller' by
means of an example using a SIMATIC S7.
4.3.3.2 Settings at the PROFINET IO Controller

The characteristic communication features of a PROFINET device are specified in the form of an electronic
device data sheet, the so-called General Station Description file, or 'GSDML file' for short. This file is the
obligatory 'identity card' of each PROFINET assembly and is supplied by the device manufacturer. It contains
all of the characteristics of a device such as specifications, protocols, details on its communication capabili-
ties and other information on e.g. diagnostics values. GSDML files allow the possibility of an open configura-
tion tool by reading the device information and identifying the device characteristics. The format of GSDML
files is clearly defined by the PROFINET standard. The configuration tool loads the GSDML files into its in-
ternal database and incorporates all of the characteristics of the individual devices. This has the advantage
of greatly simplifying configuration, allowing it to be made using a manufacturer-independent configuration
tool.

the file.
How do I use the device configuration files?

In a GSDML file, each selectable payload format is described by exactly one GSDML module ('PPO type').

File PROFINET mode Structure of the user data for the scales elec- Step7 or CFC
tronics
GSDML-V2.2- PROFINET IO INTECONT Tersus:

Schenck-Process- (Cyclic and acyclic services)
GmbH- ▪ Simplified Payload Structure (Fixed Mode):
INTECONT_Tersus- for type PPO:FIXED_8_8
20130301.xml ▪ General Payload Structure (Variable Mode):
for type PPOPARA_ID_3_6
4.3.3.2.1 Integrating the IO Device

The IO device (in this case: INTECONT Tersus) is integrated using the program 'SIMATIC Hardware Config-
urator'. You can find the components required (configuration) via the tree structure as follows (see figure):
PROFINET IO | Further FIELD DEVICES | I/O | INTECONT Tersus | …
Integration is a two-part process using Drag & Drop:
1. 'Hook' the IO device into the bus line (black dash)
2. Enter the payload structure into the table (→ module from GSDML file)
Example shows DISOCONT Tersus
A) How can I tell which GSDML module has been selected as per the current parameter settings at
the IO device and that needs to be set at the IO controller?
Start the function 'Browse Controller' in the EasyServe menu under 'Extras' → 'Start' and select 'Identification
& Maintenance' to call up the following notice:

In the 'Fieldbus' section the relevant module name can be read in the line 'GSD/GSDML Module', e.g.
FIXED_8_8.
B) An overview of the GSDML modules:
1) PROFINET IO – VARIABLE Mode (general payload structure)

Example for normal mode:
With parameter transmission, 3 preset values and 6 read values
→ GSDML module 'PARA_ID_3_6'
Meaning: Including parameter block, 3 preset values, in total 8 process data read values (6 + 2 fixed)

2) PROFINET IO – FIXED-Mode (fixed payload structure)

Example for normal mode:
→ GSDML module 'FIXED_8_8'
Meaning: No ID transmission, 8 preset values and 8 read values
3) Relationship between INTECONT Tersus parameters 'Configuration' and GSDML module with
PROFINET IO
There is exactly one GSDML module for each selectable payload format. The names of the modules have
been selected so that they suggest the size of the transmitted payload.
Structure of the GSDML module name for INTECONT Tersus payload formats:
e.g.
Format as per parameter ' Configuration': → GSDML module name:
FIXED_8_8 FIXED_8_8

4.3.3.2.2 Issue IP Address and Name for PROFINET IO Subscriber

Select 'Target System' - 'Edit Ethernet Subscriber' and click on the button [Search] in the 'Ether-
net Subscribers' frame.
A list of all subscribers available online will be compiled.
Select a subscriber and close the dialog with [OK].

Now enter the device name into the field 'Device Name' in the 'Assign Device Name' screen and confirm with
[Assign Name]. The device name is now transmitted to the subscriber and stored there. It may be up to 255
characters long.
Enter an IP address, a subnet mask and, if required, a router address in the 'Set IP Configuration' screen
and confirm with the button [Assign IP Configuration]. Alternatively the IP address can be given by a DHCP
server.

The device supports a minimum refresh time of 100 ms.

Load the projection into the SIMATIC S7 and start the assembly. The controller error LED now should go
out.
The LEDs of the module VPN8020 should have the following states:
LED_READY_OUT: H414 Glows green

LED_BF_OUT: H412 Off
LINK_PHYx: RJ45 Glows green
ACT_PHYx: RJ45 Blinks (rapidly) yellow ("Continuous Light")
If this is not the case inspect the subscriber projection, in particular the device names and the IP address.

4.3.4 PROFINET Interface VPN8020

The optional module can be installed onto the device mainboard to create an interface to the PROFINET.
Properties
RJ45 connector to bus activation X316: 1

X316: 2
Layout of the Components
Settings
- none –
Positions W200 … W203 are not jumpers and may not have anything fitted there!
LEDs on the Board

LED Color Status Description
H412 red System error:

LED_SF_OUT
ON PROFINET diagnostics exist:
▪
1)
At least one AR is not involved in the exchange of data
▪ Defective cable connection/bus plug
OFF * No fault.
▪ All ARs are exchanging data and there are no errors.
H413 yellow Maintenance:

LED Color Status Description

LED_MT_OUT ON Maintenance necessary:
Manufacturer-specific – depending on the abilities of the sub-system
▪ At least one AR is involved in exchange of data and one of the fol-
lowing errors has occurred → coming
– At least one submodule in the device has registered 'Mainte-
nance required or demanded'
▪ Other maintenance events are pending
OFF * No other maintenance events are pending
H414 green Component ready:

LED_READY_OUT 2)
OFF * TPS-1 did not start correctly
flashing TPS-1 is waiting for synchronisation of the Host CPU (firmware start is
complete)
ON ▪ The CPU has started up internally. The CPU can move to exchang-
ing data and order the ARs to the projected field devices.
▪ The CPU is exchanging data
H411 red Bus error:

LED_BF_OUT ▪ An Ethernet connection has a fault (e.g.: the bus connecting plug has
ON
no contact).
▪ If the IP address/NameOfStation is present more than once in the
network, this means that there is at least one other device with the
same IP address/NameOfStation as the device in question.
▪ As yet no IP address set.
flashing ▪ When field devices begin to initialize (IO controllers, IO devices, ...).
▪ At least one projected AR is no longer involved in data exchange.
OFF * No error is pending.

▪ All ARs are configured and working correctly.
H415 yellow System clock:

SYSCLK
OFF Communication processor CP not active or has been reset
flashing Communication processor CP not active (should always blink)
H416 green Supply voltage:

3.3 V
ON OK (should always be lit)
OFF No supply voltage
H410 red 'Flash' function:

FLASHSEL
OFF * Normal operation
ON For internal purposes only!
* Initial state
1)
AR = Application Relation
2)
Single-chip device interface for PROFINET

LEDs in the Ethernet Connection (RJ45)
Port LED Color Description
1 LINK_PHY1 green An Ethernet connection is available
off There is no Ethernet connection
ACT_PHY1 yellow Currently data is being exchanged via the Ethernet
2 LINK_PHY2 as Port 1 as Port 1
ACT_PHY2

4.3.5 PROFINET interface VPN 8020- network topology

This section describes the possible topology of PROFINET networks with Schenck Process weighing elec-
tronics using the PROFINET fieldbus interface module VPN8020 (VPN for short).
NOTICE
Quality of the components used
The PROFINET fieldbus interface module VPN8020 can be operated in the
conformity classes CC-A/CC-B. In CC-A, the PROFINET specification re-
quires IEEE 802.1D (Auto Crossover, Auto Negotiation) / Q (prioritization) /
AB (neighbor detection). In this case, we therefore recommend using com-
ponents which have been specified for PROFINET. In order to guarantee
fault-free operation in CC-B any other components (e. g. external switches)
used within the network must be certified for PROFINET.
In any case, only industry-appropriate products may be used.
Star Topology
Fig. 7: PROFINET star topology
The network participants are connected with the PROFINET-capable switch in a star shape. In this topology,
weighing electronics can be configured via the PROFINET network.

Line Topology
Fig. 8: PROFINET line topology
In the line topology, the bus subscribers are arranged consecutively. The internal VPN switch is used to for-
ward the fieldbus.
The drawback of this topology: if one of the front network participants fails, the entire downstream network is
affected.
Ring Topology
Fig. 9: PROFINET ring topology
The advantage of the ring topology is that each fieldbus subscriber can be reached in one of two ways. This
means that the no-motion state of a connection or participant does not lead to the total failure of the system.
Redundancy Manager 'Ring Manager'

In order to avoid circulating telegrams in the ring topology, a ring participant must be defined as Redundancy
Manager. This Redundancy Manager unravels the ring as long as the system is functioning completely and
in the event of an error closes the connection.

The ring can either be formed by a master with two ports or via a stub to a switch. All ring participants must
master the MRP (Media Redundancy Protocol). The VPN switch can do this.
The PROFINET fieldbus interface module VPN8020 cannot be used as a Redundancy Manager.
4.3.6 Acyclic Services

In addition to cyclic IO data communication, the devices also support the lower-priority acyclic 'Read Record'
and 'Write Record' services. The devices are controlled with cyclic process data via a PROFINET controller.
This controller (usually a PLC) can also access the PROFINET devices via 'Read Record' and 'Write Record'
to parameterize. The parameters written are stored in non-volatile memory in the device.
The timing of the acyclic data exchange sequence is monitored by the RPC timeout.
The payload transmitted by an acyclic PROFINET service are summarized in the form of a dataset. Each
dataset is uniquely addressed by the following properties:
API fixed to '0'

Slot number fixed to '1'
Subslot number fixed to '1'
Index Varies according to the desired dataset (see table)
List of return codes:

0 Transmission successful
176 illegal index value

4.3.6.1 Acyclic Data PROFINET

*)
(Typical response or explanation) (Specified payload) count
Slot 0 / SubSlot 1
hex dec dec/hex
Read device name ASCII 40 128/0x80 S→M
M→S
*)
Write device name ASCII 4D 79 20 46 65 65 64 65 72 40 178/0xB2
(e. g. 'My Feeder')
Read the scales' software version ASCII 40 134/0x86 S→M
Highest-priority event - read short text ASCII 12 121/0x79 S→M

(e. g. 'WE01')
Highest-priority event - read long text ASCII 40 122/0x7A S→M

(e. g. 'Event: Power Failure')
Highest-priority event - read short and long ASCII 68 135/0x87 S→M

texts
(e. g. 'WE01 Event: Power Failure')
All displayed events - read short text ASCII 68 131/0x83 S→M

max. 17 events, 4 characters/event
(e. g. 'WE01 …')
Call up the time, number and the counter ASCII 2014-05-21 14:12:03 68 140/0x8C S→M
value of the most recent log in the legal- No: 137
for-trade memory with an acyclic telegram. CR: 888170 kg
Read all displayed events Binary 68 132/0x84 S→M

max. 17 events, 4 Bytes per event
edgement
(e. g. '03 01 01 00 … ')
M→S
*)
Write a process or parameter value Binary 0250 42C80000 6 174/0xAE
(ID, value)
(e. g. 'Serial Setpoint = 100 kg/h')


*)
(Typical response or explanation) (Specified payload) count
Slot 0 / SubSlot 1
hex dec dec/hex
Write one or more process or parameter Binary 0250 42C80000 66 175/0xAF M→S
*)
values 0252 41200000
(ID, value; ID, value; … ) 0000 00000000 ….
max. 11 values
The evaluation stops when the next ID has
the value ZERO.
(e. g. 'Serial Setpoint = 100 kg/h,
M→S
1) *)
Writing a read ID Binary 0250 2 176/0xB0
Read a process or parameter value whose Binary 6 126/0x7E S→M

1)
ID was sent beforehand
[ID value]
Read all preset value IDs of the parameter Binary 16 129/0x81 S→M
block 'Fixed mode configuration'
(e. g. '0140 0160 0180 0250 0252 0100
…')
Set all preset values IDs of the parameter Binary 0140 01A0 … 16 179/0xB3 M→S
*)
block 'Fixed mode configuration' CAUTION: The 1st transmit-
ted ID must always be 0140
Read all read IDs of the parameter block Binary 32 130/0x82 S→M
(e. g. '02F0 0310 0610 0750 …')
Set all read IDs of the parameter block Binary 0752 0754 … 32 180/0xB4 M→S
*)
Read date and time Binary 0C030F 0B1000 6 138/0x8A S→M

(yymmdd hhmmss)
M→S
*)
Read date and time Binary 0C030F 0B1000 6 188/0xBC
(yymmdd hhmmss)
*)
1)

4.3.7 Supplementary Documentation:
European standard IEC 61158

INTECONT: BV-H2185 EasyServe Operating Manual
DISOMAT: BV-H2461 DISOPLAN VPL 20430 – Operating Manual
WireShark network analyzer *) (Freeware) www.wireshark.org
*) The GSDML file is supplied with a file containing recommended filter and color settings.
Documents of the PROFIBUS User Organization (PNO)
(www.profibus.com)
PN-Cabling-Guide_2252_V301_Oct11.pdf
PN_Netw_Comp_2252p2_V101_feb04.pdf
PROFINET-ConfClass_7042_V10_Dec07_GB.pdf
PROFINET_Commissioning_8082_V101_Jul10.pdf
PROFINET_Design_guideline_8062_V104_Nov10_1_[1].pdf
PROFINET_Guideline_Assembly_8072_V10_Jan09.pdf
PN_Comm_Checkl_8092_V101_Jul10.doc
PROFINET-ConfClass_7041_v10_Dez07_DE.pdf
PROFINET_Inbetriebnahme_8081_V101_Jul10.pdf
PROFINET_Montagerichtlinie_8071_V10__Jan09.pdf
PROFINET_Planungsrichtlinie_8061_V104_Nov10.pdf
PN_Inbetriebn_Checkl_8091_V101_Jul10.doc
4.4 EtherNet/IP
NOTICE
*)
EtherNet/IP is based on the tried and tested fundamental Ethernet-TCP/IP technology for client-server
communication.
EtherNet/IP adds Common Industrial Protocol (CIP) to the standard Ethernet. This is the same application
protocol and object model used by DeviceNet. CIP facilitates interoperability between devices from different
manufacturers and sub-networks.

*)
Here the abbreviation IP means Industrial Protocol and should not be confused with TCP/IP, where IP
stands for Internet Protocol. It is therefore common also to use the term 'Industrial Ethernet'.
4.4.1 Guidelines for Startup

1. Preparation of the hardware as per the system description.
The hardware for the Ethernet interface already is contained in the basic configuration (RJ45). The
'EtherNet/IP' protocol is supported.
2. Activation of the protocol 'Ethernet/IP' in the weighing electronics.
3. Parameterization of the Ethernet address at the connection.
4. Selection the process image and definition of the data to be transmitted.
5. Start of the communication by the master ('fieldbus' operating mode).
6. Monitoring of the interface with the service tool ('fieldbus' view).
Please refer to chapter 'Notes on Ethernet/IP' for diagnostics and troubleshooting.
4.4.2 Functionality of the Ethernet Connection

▪ The server can exchange simultaneously data with a client through up to 16 connections in 'Fieldbus'
operating mode. The 'EtherNet/IP' protocol can be used. There is no locking of write accesses, i.e. the
client which lasts sends setpoints, wins.
▪ The device can be employed as a group 2 and group 3 server in the EtherNet/IP network. Further in-
formation can be found on the ODVA website.
▪ Simple parameterization using the operating panel or the service tool.
▪ The connection supports I/O messaging and explicit messaging only with the ControlLogix processor
family (Allen Bradley). I/O messaging only, no explicit messaging, can be used to communicate with
PLC-5, SLC500 or the Micrologix processor series.
▪ Example codes for specific PCS are available to facilitate commissioning.
4.4.3 Configuration of the Ethernet Connection
4.4.3.1 EtherNet/IP Slave Settings


Refer to chapter 'Parameter' in the INTECONT Tersus operating manual


Modbus-RTU here: EtherNet/IP
PROFIBUS DP
DeviceNet
Modbus-TCP
PROFINET IO
EtherNet/IP
IG (Ignore)
IG (Ignore)
A (ALARM)

Word Sequence I:std/L:std I:std/L:std Establish the word sequence during the transmission
I:swp/L:std of measured values in IEEE/LONG format here:
I:std/L:swp I:swp/L:swp ('Little Endian')
I:swp/L:swp
Byte Sequence High - Low High - Low Establish the byte sequence within a data word
Low - High here: Low - High('Little Endian')
PARA_ID_3_6 Selection of process image:
FIXED_8_8 FIXED …: Transmission via simplified payload struc-
FIXED_4_4 ture (FIXED Mode):
All others: Transmission via general payload struc-
ture (VARIABLE Mode):

If YES is chosen the PROFIBUS ident number 0C9B
will be replaced with 0524 Es sind die GSD-Datei
und die Bausteine (CFC & STEP7) für das Vorgän-
germodell zu verwenden. The GSD file and the mod-
ules (CFC & STEP7) must be used for the earlier
model.

PA32 compatible NO NO under circumstances the process images (PA)

1)
YES NO_PARA_ID_3_6 and PARA_ID_2_4 must be filled
up to 32 bytes in the INTECONT PLUS compatibility
mode. This ensures the compatibility to earlier hard-
ware components.
1)
This parameter is shown only if Compatiblity INTECONT = YES
Settings in the 'Ethernet' block
Parameter Value range Default value Explanation
IP Address Freely selectable 192.168.240.1 Manual allocation of the IP address.
Net Mask Freely selectable 255.255.255.0 Delegating the subnetwork masks
Gateway Freely selectable 0.0.0.0 Specify the standard gateway address
The device must be restarted if a network parameter has been altered (switch OFF/ON) !
IP addresses have to be unambiguous. Ask your system administrator for valid addresses that
are not in use.
Notes
The following settings are useful for the PC network adapter if you are operating the subscriber in a local
subnetwork with a separate network card for this network:
▪ Network parameters:
IP Address: 192.168.240.254 (PC)
Net Mask: 255.255.255.0
Gateway: 0.0.0.0
▪ IP addresses subscriber 1 … n:
192.168.240.x, where x = 1 … n
Verifying the subscriber addresses
One way of verifying the network parameters is by using a PC PING command, e.g. 'ping 192.168.240.1',
which is available in the command console of every PC.
If successful, the response time of the terminal will be shown.

4.4.3.2 Settings at the EtherNet/IP Master (ControlLogix)
▪ Setting up a new project in the RSLogix program

▪ Configuration of the controller
▪ Selection and configuration of the EtherNet/IP-Bridge
▪ Adding the INTECONT Tersus to the I/O configuration
▪ Adding a 'Generic Ethernet Module'
The example applies to: FIXED_8_8
▪ Configuration of the new EtherNet/IP module
A) Setting the connection options for the controller:

B) Useful configuration of the query cycle for operation with weighing controllers:
After preparing the controller with shown settings, the configuration have to be loaded into the controller
(download).

C) Display of the data of an INTECONT Tersus in ContolLogix:
I.Data are the input data of the INTECONT Tersus (8 read values).
O.Data are the output data to the INTECONT Tersus (8 preset values).

4.4.4 Acyclic Data (Explicit Messages) EtherNet/IP

Data instance Model Example byte Instance Service
(Typical response or explanation) (Specified payload) Coun
Class 4 t *)
Attribute 3 hex dec/hex dec/hex
dec
Read device name ASCII 40 129/0x81 14/0x0E

*)
Write device name ASCII 4D 79 20 46 65 65 64 65 72 40 179/0xB3 16/0x10
(e.g. 'My Feeder')
Read the scales' software version ASCII 40 135/0x87 14/0x0E
Highest-priority event – read short text ASCII 12 122/0x7A 14/0x0E

(e.g. 'WE01')
Highest-priority event - read long text ASCII 40 123/0x7B 14/0x0E

Highest-priority event - read short and long texts ASCII 68 136/0x88 14/0x0E
Read all displayed events - short text ASCII 68 132/0x84 14/0x0E

(e.g. 'WE01 …')
Call up the time, number and the counter value of ASCII 2014-05-21 14:12:03 68 141/0x8D 14/0x0E
the most recent log in the legal-for-trade memory No.: 137
with an acyclic telegram. CR: 888170 kg
Read all displayed events Binary 68 133/0x85 14/0x0E

Event group, number, class, acknowledgement
(e.g. '03 01 01 00 … ')
Write a process or parameter value *) Binary 0250 42C80000 6 175/0xAF 16/0x10

(ID, Value)
Write one or multiple process or parameter val- Binary 0250 42C80000 66 176/0xB0 16/0x10
ues*) 0252 41200000
(ID, Value; ID, Value; … ) 0000 00000000 …
Max. 11 values
The evaluation ends at the next ID with a ZERO
value.

Data instance Model Example byte Instance Service

(Typical response or explanation) (Specified payload) Coun
Class 4 t *)
Attribute 3 hex dec/hex dec/hex
dec
Write a read ID 1) *) Binary 0250 2 177/0xB1 16/0x10

Subsequently the ID can be read multiple times
(see next line)
Read a process or parameter value whose ID was Binary 6 127/0x7F 14/0x0E

sent beforehand 1)
[ID Value]
Read all preset value IDs of the parameter block Binary 16 130/0x82 14/0x0E
(e.g. '0140 0160 0180 0250 0252 0100 …')
Set all preset values IDs of the parameter block Binary 0140 01A0 … 16 180/0xB4 16/0x10
'Fixed mode configuration' *) CAUTION: The 1st transmitted
ID must always be 0140
Read all read IDs of the parameter block 'Fixed Binary 32 131/0x83 14/0x0E
mode configuration'
(e.g. '02F0 0310 0610 0750 …')
Set all read IDs of the parameter block 'Fixed Binary 0752 0754 … 32 181/0xB5 16/0x10
mode configuration' *)
Read date and time Binary 0C030F 0B1000 6 139/0x8B 14/0x0E

(yymmdd hhmmss)
Write date and time *) Binary 0C030F 0B1000 6 189/0xBD 16/0x10

(yymmdd hhmmss)
*)
1)

4.4.4.1 Acyclical Data Exchanges between PCS and Weighing Electronics

The message command (MSG) is used in the ControlLogix process control system to send and receive acy-
clic data (Explicit Messages), e. g.:
Below is one example each of writing and reading acyclic data.
4.4.4.1.1 Example for 'Write a Process or Parameter value'

Task: set parameter 'Serial Setpoint' to 100 kg/h.
This results in the following preset value:
Preset ID = 0250hex from the table 'Write IEEE Values'
Preset value = 42 c8 00 00 (hex) = 100.0
The instruction 'Write a process or parameter value' is used for this. You will find the value 175dec (AFhex) in
the column 'Instance' of the list of 'Acyclic Data (Explicit Messages) Ethernet/IP'.
Therefore set the configuration dialog for this task as follows:
▪ Select the 'Set Attribute Single' entry from the 'Service Type' list. The corresponding 'Service Code' is
10hex.
▪ Enter the decimal value into the 'Instance' field, in this case 175.
▪ The other settings are shown in the figure

Preset ID and preset value are entered as follows:

4.4.4.1.2 Example for 'Displays of Fixed Mode Configuration'

Task: Read the current 'Fixed mode configuration'
To do this use the instruction 'Read all Read IDs of Parameter Block Fixed mode configuration'. You will find
the value 131dec (83hex) in the column 'Instance' of the list of 'Acyclic Data (Explicit Messages).
Therefore set the configuration dialog for this task as follows:
▪ Select the 'Get Attribute Single' entry from the 'Service Type' list. The corresponding 'Service Code' is
0Ehex.
▪ Enter the decimal value into the 'Instance' field, in this case 131.
▪ The other settings are shown in the figure
The data received in this task are e.g.:

EtherNet/IP specifications www.odva.org

Network analyzer 'WireShark' (Freeware) www.wireshark.org
4.5 Modbus (Serial and Network)
4.5.1 General Information

The Modbus protocol is a communication protocol based on a master-slave architecture.
Modbus can connect a master (e.g. a PCS) to several slaves (weighing controller).
There are two versions of Modbus, one for the serial interface (EIA 232 and EIA 485) and one for Ethernet.
A distinction is made when transmitting data between three different modes of operation:
Modbus ASCII In this mode ASCII code is transmitted rather than a binary sequence. This makes it
legible for operators but the data throughput is lower than when using RTU.
Modbus-RTU (RTU: Remote Terminal Unit)
In this mode the data are sent as binary code. This gives a larger data throughput, but
the data is not directly legible and must first be converted into a legible format.

Modbus-TCP Modbus-TCP is very similar to RTU but TCP/IP packets are used to transmit the data,
though the data presents itself to the application as a Modbus-RTU frame.
Communication channels:
TCP ports 502 and 503 are reserved for Modbus-TCP communication.
The most common modes for weighing controllers are Modbus-RTU and Modbus-TCP only.
4.5.1.1 Guidelines for Startup

▪ Preparation of the hardware as per the system description:
– Modbus-RTU: The 'Modbus Interface VSS8020' is used for serial Modbus.
– Modbus-TCP: If using Modbus via internet the hardware for the Ethernet interface is contained in the
basic configuration.
▪ Activation of the protocol type: Modbus RTU or Modbus TCP in the weighing electronics.
▪ Parameterize the serial or Ethernet addresses.
▪ Defining the data to be transmitted.
▪ The master will begin communication.
▪ Monitor the interface using Service Tool → 'Fieldbus' view (refer to chapter 'Diagnostics and Trouble-
shooting').
▪ Ensure you use the correct bus termination for the serial connection.
4.5.1.2 General Telegram Structure

The following graphic representation shows the difference between the Modbus standard telegram and the
Modbus-TCP telegram.
Whereas with Modbus standard communication the slave address and a CRC checksum are transmitted in
addition to the order code and the data, in Modbus-TCP this function is performed by the subordinate TCP
protocol.

4.5.1.3 Subscriber Addresses

Modbus-TCP:
All stations in an ethernet network have unique IP addresses. This is the reason why the Modbus slave ad-
dress can always be set to 1.
Modbus-RTU:
Each bus subscriber has a slave address which begins at 1 and continues in ascending sequence. The
highest address that can be set is subsequently referred to as MAXSLAVE. The address can be set using
the dialog window on the scales operating console or using the 'EasyServe' service tool. MAXSLAVE has a
value of 254. Address 0 is the broadcast address. In this case, the slaves send no reply.
4.5.1.4 Function codes (FC)

The Weighing Controller behaves as a Modbus-TCP server, after the 'OPEN MODBUS-TCP
SPECIFICATION, Release 1.0,' 29th March 1999 standard. This data representation is based entirely on the
Modbus standard.
Overview: Modbus function codes sorted by the type of access (reading or writing)
Internal designation Protocol-specific designa- Segment address (dec) Corresponding Controller

tion Address Range
(dec/hex)
Read (back) multiple digital FC01: Read coils 00001 -09999 256 - 463 / 0x0100-0x01CF
outputs
Read multiple digital inputs FC02: Read discrete inputs 10001 -19999 720 - 1885 / 0x02D0-0x073F
Write a digital output FC05: Write single coil 00001 -09999 256 - 463 / 0x0100-0x01CF
Write multiple digital outputs FC15: Write multiple coils 00001 -09999 256 - 463 / 0x0100-0x01CF
Read multiple analog out- FC03: Read holding regis- 40001 -49999 592 - 638 / 0x0250-0x027E
puts ters 32 - 33 / 0x20-0x21)
Read multiple analog out- FC04: Read input registers 30001 -39999 1872 - 2428 / 0x0750-
puts 0x097C
48 - 69 / 0x30-0x45
Write an analog output FC06: Write single register 40001 -49999 32 - 33 / 0x20-0x21
Write multiple analog out- FC16: Write multiple regis- 40001 -49999 592 - 638 / 0x0250-0x027E
puts ters 32 - 33 / 0x20-0x21)
Read and write multiple FC23: Read/write multiple Combination of FC04 and See FC04 and FC16
analog outputs in one com- registers FC16
mand
1)
Modbus-RTU only
Special features of the controller:
▪ Diagnostics using FC08 (subcode 0 and 1)
▪ FC03 can also be used wherever FC04 is used as default.
▪ Data that are read with FC02 by default can also be read with FC03/FC04
▪ Parameters and acyclical data can be rad with FC03/FC04 and written with FC16

Often, the control system will add a so-called 'segment address' (function-code dependent) to the
data address to be described. Also the data address must be increased by 1, because the registry
Modbus protocol addresses start at 1. In other words, the rule for configuring the data address is:
Data address = segment address + controller address + 1
4.5.1.5 Fault codes

Only the error codes 01 to 03 are used. No reply is sent with CRC errors. All of the errors described below
are combined in the weighing electronics to the system error 'SYxx Event: Cyclic Communication'. This
group error message also includes the Timeout.
Faultcode Meaning
1 The requested function (FC) is not supported by the subscriber.
2 Incorrect data address:

▪ ID or SC out of range
▪ Data offset + length too large
3 Incorrect data type:

▪ Incorrect data for FC05 (0xFF00 and 0x0000 are permitted)
▪ Data length < 0
▪ Requested length too long
▪ Data address of the IEEE or INT32 value is odd-numbered
4.5.1.6 Data Formats

The transmission begins at the same time as the MSB. Setpoints and measured values are transmitted in
IEEE format (IEEE754, 32 bit). All control and status information are represented as a binary signal with the
8 data bits of each character. Additionally, all control and status information can be treated as single-bit in-
formation.
4.5.1.7 Safeguarding Transmission

Modbus-TCP:
The safety measures of the TCP layer ensure the reliability of Modbus-TCP transmission.
Modbus-RTU:
The characters are safeguarded by a parity bit, the telegrams are safeguarded by a checksum (CRC16) (see
Modbus specifications). The Modbus specifications determine the response to a transmission error (see
EXCEPTION RESPONSE).

4.5.1.8 Payload
A distinction is made in Modbus between master and slave devices. The weighing electronics with the
fieldbus interface card VSS 28020 always acts at the bus as a slave. The weighing electronics receives data
from the master and then transmits its data to the bus master. It is always a passive bus subscriber.
The payload is arranged as follows:
▪ Process data range for cyclic exchange of the process values
▪ Parameter range for reading/writing acyclic parameter values
Every segment of the cyclic payload contains values of the same type. From an address standpoint, the data
within a segment line up with no gap. The data of a segment can be read or written with one telegram each.
Data from different segments can be combined into lists of variables. This reduces the effort required to
transmit cyclic values to two telegrams (request/preset value).
The corresponding data addresses can be found in the following table.
Data Address Meaning
hex dec
0x21E0 8672 Write all process values, as configured in block 'Fixed mode configuration’ (ID Preset Value 1 - 8).
Writing is performed with function code 16.
0x2400 9216 Read all process values, as configured in block 'Fixed mode configuration’ (ID Read Value 1 -
*)
16 ). Reading is performed with function codes 3 or 4.
*)
8 for INTECONT Tersus
The parameter area gives the user optional access via the bus system to all parameters in the scales.
4.5.1.9 Examples of Telegrams (Process Values)

The lines below show the structure of Modbus telegrams. The first line shows the telegram from the bus
master to the scales and the second line shows the scales' reply. The examples contain the Modbus frame.
A FC Data Function
01 05 0140 FF00 Start the scales (single bit command)

01 05 0140 FF00
01 05 0141 FF00 Stop the scales (single bit command)

01 05 0141 FF00
01 06 0140 0040 Reset counter 1 (word setpoint)

01 06 0140 0040
01 10 0250 0002 04 42C80000 Setpoint in IEEE format with no word turning

01 10 0250 0002
01 03 02F0 0004 Read 4 words status information

01 03 08 xx xx xx xx xx xx xx xx xx = Data
A: Address; FC: Function Code

4.5.1.10 Parameters
All parameters can be read and written. As opposed to cyclic values however, one parameter only can be
processed per telegram. The system-wide unique parameter ID is required for transmission. Use these IDs
as Modbus protocol data addresses.
A list of the parameters including IDs can be printed using the command 'File | Print' in the service tool
'EasyServe'. Condition is that the checkbox 'Print SysID' has been activated in the menu item 'Tools
| Options ...' in the 'Format' tab.
Please note that specialized knowledge is required to change selectable parameters. Floating point and in-
teger values, on the other hand, can be read and written with no trouble.
The data formats correspond to those of the cyclic values. Function codes 3 or 4 are used to read the current
parameter value; function code 16 is used to write the current parameter value. Each current parameter val-
ue consists of a data double word (4 bytes). Floating point values are coded according to the IEEE-754-4-
byte standard.
Examples of parameter telegrams (Modbus only):
Modbus-Master → Scales Scales reply Comment
01 03 1082 0002 01 03 04 42C8 0000 Read parameters

(Maximum Flow Rate Io , ID = 0x1082, value = 100)
01 10 1082 0002 04 4323 5678 01 10 1082 0002 Write parameter (value = 163.34)
4.5.1.11 Acyclical Data (Explicit Messages) Modbus

Data instance Model Example Byte Data address FC
(Typical response or explanation) (Request Modbus frame in hex) count *)
Slave address 1 (dec/hex)
dec (dec/
hex)
Read device name ASCII 01 03 2079 0014 40 8303/0x2079 3

(e.g. 'My Feeder')
Write device name *) ASCII 01 10 2079 0014 28 41 42 43 … 40 8303/0x2079 16/0x10
Read the scales' software version ASCII 01 03 2297 0014 40 8855/0x2297 3
Highest-priority event – read short text ASCII 01 03 2200 0006 12 8704/0x2200 3

(e.g. 'WE01')
Highest-priority event - read long text ASCII 01 03 2206 0014 40 8710/0x2206 3

Highest-priority event - read short and ASCII 01 03 22AB 0022 68 8875/0x22AB 3

long texts
Read all displayed events - short text ASCII 01 03 223F 0022 68 8767/0x223F 3
(e.g. 'WE01 …')


dec (dec/
hex)
Call up the time, number and the counter ASCII 2014-05-21 14:12:03 68 9279/0x243f 3
value of the most recent log in the legal- No.: 137
for-trade memory with an acyclic tele- CR: 888170 kg
gram.
Read all displayed events Binary 01 03 2261 0022 68 8801/0x2261 3

edgement
(e.g. '03 01 01 00 … ')
Write a process or parameter value *) Binary 01 10 2040 0003 06 0250 42C80000 6 8246/0x2040 16/0x10
(ID, Value)
Write one or multiple process or parame- Binary 01 10 2043 0022 44 0250 42c80000 66 8249/0x2043 16/0x10
ter values*) 0252 41200000 0000 00000000 ….
(ID, Value; ID, Value; … )
Max. 11 values
The evaluation ends at the next ID with a
ZERO value.
Write a read ID 1) *) Binary 01 10 2064 0001 02 0250 2 8282/0x2064 16/0x10

Read a process or parameter value Binary 01 03 221A 0003 6 8730/0x221A 3

whose ID was sent beforehand 1)
[ID Value]
Read all preset value IDs of the parame- Binary 01 03 208D 0008 16 8323/0x208D 3
ter block 'Fixed mode configuration'
(e.g. '0140 0160 0180 0250 0252 0100
…')
Set all preset values IDs of the parameter Binary 01 10 208D 0008 10 0140 01A0 … 16 8323/0x208D 16/0x10
block 'Fixed mode configuration' *) CAUTION: The 1st transmitted ID must
always be 0140 (→'Fieldbus Clearance')
Read all read IDs of the parameter block Binary 01 03 2095 0010 32 8331/0x2095 3
(e.g. '02F0 0310 0610 0750 …')


dec (dec/
hex)
Set all read IDs of the parameter block Binary 01 10 2095 0010 20 0752 0754 … 32 8331/0x2095 16/0x10
'Fixed mode configuration' *)
Read variables lists using the Modbus Binary 01 03 2400 0022 64 9216/0x2400 3
protocol
Write variables lists using the Modbus Binary 01 10 21E0 0010 20 00010000 … 32 8672/0x21E0 16/0x10
protocol
(e.g. 'Commands 4+5: Start Command')
Read date and time Binary 0C030F 0B1000 6 9272/0x2438 3

(yymmdd hhmmss)
Write date and time *) Binary 0C030F 0B1000 6 9272/0x2438 16/0x10

(yymmdd hhmmss)
*)
1)
4.5.1.12 Supplementary Documentation
OPEN MODBUS/TCP SPECIFICATION www.modbus.org

BV-H2185 EasyServe operating Manual

4.5.2 Modbus-TCP
NOTICE
Communication Channels
TCP ports 502 and 503 are reserved for Modbus-TCP communication.
4.5.2.1 Functionality of the Modbus-TCP Connection

▪ The server can exchange data with as many as 16 clients simultaneously. The data are either sent as
Modbus-TCP packets or are expected as such from outside. The functional range is described in
more detail below.
▪ The Ethernet interface is easily parameterized using the basic device's operating console or the
'EasyServe' service tool.
▪ Modbus master simulator (provides testing support for commissioning)
▪ Read mode runs parallel to all other protocols
4.5.2.2 Configuration of the Modbus-TCP Connection

Each bus subscriber must have a unique address. The IP address, network mask and gateway are entered
in the 'Ethernet' parameter block.
Please refer to chapter 'Notes on Modbus' for diagnostics and troubleshooting.
4.5.2.2.1 Settings at the Modbus-TCP Slave




1)
Modbus-RTU here: Modbus-TCP
PROFIBUS DP
DeviceNet
Modbus-TCP
PROFINET IO
EtherNet/IP
Communication W1 (Warning 1) derrun/Exceeded during Cyclic Communication
W2 (Warning 2) + Timeout + ID Verification'
IG (Ignore)
Communication W1 (Warning 1) derrun/Exceeded during Acyclic Communica-
IG (Ignore) tion'
A (ALARM)
Check in Key- NO YES The fieldbus communication monitoring in key-

board Mode YES board mode can be activated/deactivated.
Compatibility NO NO Compatibility setting towards the DISOCONT

DISOCONT Mas- YES master
ter
Word Sequence I:std/L:std I:std/L:std Establish the word sequence during the trans-
I:swp/L:std mission of measured values in IEEE/LONG
I:std/L:swp format
I:swp/L:swp
Access Rights NO NO Determines for the Modbus-TCP protocol which

Limitation FB FIRST WRITE master system may execute controlling func-
REMOTE IP tions:
NO: Each master system may give preset val-
ues. The most recent value is effective.
FIRST WRITE: The master system that first
sends a preset value telegram is given write
access.
REMOTE IP: Only the master system whose IP
address was explicitly given can send preset
values.
Remote IP 192168240250 192168240250 IP address of the subscriber with control rights

2)
Address FB
1)
This parameter is subject to the 30 s condition for transfer to the interface card (see chapter 'Guideline for
commissioning').
2)
This parameter is shown only if Access Rights Limitation FB = REMOTE IP is selected.

Settings in the block ' Ethernet '
IP Address 192.168.240.x 192.168.240.1

with x = 1 … 254
Net Mask 255.255.255.0 255.255.255.0
Gateway 0.0.0.0 0.0.0.0
IP addresses have to be unambiguous. Ask your system administrator for valid addresses that
are not in use.
Notes
If you are operating the INTECONT Tersus devices in a local subnetwork with an internal network card for
this network, we recommend that you use the following settings for the PC network adapter:
▪ Network parameters:
IP Address: 192.168.240.254 (PC)
Net Mask: 255.255.255.0
Gateway: 0.0.0.0
▪ IP addresses of the INTECONT Tersus 1 … n:
192.168.240.x mit x = 1 … n
Verifying the subscriber addresses

One way of verifying the network parameters is by using a PC PING command, e.g. 'ping 192.168.240.1'.
If successful, the response time of the terminal will be shown.
4.5.2.2.2 Modbus-TCP Master Settings

If data from several segments are used (see fieldbus data), each segment requires at least one telegram.
Exception: See the variables lists in chapter 'Payload'.
Setting the correct byte sequence with values in IEEE and LONG format.
The maximum permissible telegram length is 256 bytes, including header and trailer bytes.
The INTECONT Tersus uses only the sixth byte of the 6 byte telegram header defined in the OPEN
MODBUS standard to transmit the data length. All other bytes are sent back 1:1 in the reply. The protocol ID
should not be used to allow subsequent expansion, it must be set to ZERO!
4.5.2.3 Redundant Modbus-TCP

The controller supports redundancy in the fieldbus wiring and control system. Along with standard port 502,
port 503 can be used for the redundant connection. All process signals are available at both ports. The most
recent control command determines the system behavior. This allows the second channel seamlessly to
assume the functions of the potentially malfunctioning first channel.

4.5.3 Modbus-RTU

Each bus subscriber must have a unique address. Address 0 is reserved for a broadcast. Each subscriber
may send messages through the bus. However, this is generally initiated by the master and an addressed
slave will reply.
Structure of the Modbus-RTU Protocol
Begin of transmission in Modbus-RTU is marked by a pause in transmission of at least 3.5 characters in
length. The length of the pause thus depends on the transmission speed. The address field consists of 8 bits
that represent the receiver address. In its reply to the master the slave includes this address so that the mas-
ter can identify the sender. The function field consists of 8 bits. If the slave receives correctly the request
from the master it will reply with the same function code. If an error occurs, the slave will change the function
code by setting the highest-value bit in the function field to '1'. The data field contains information on which
register the slave is to read out and at which address it begins. The slave will put the read-out data (e.g.
measured values) there before sending it to the master. If an error occurs an error code will be transmitted
there. The field for the check sum calculated by CRC is 16 bits long. The entire telegram must be transmitted
in a continuous stream of data. If an interruption longer than 1.5 characters occurs between two characters,
the telegram will be considered incomplete and should be rejected by the receiver.
Start Address Function Data CRC16 End
Timeout 1 byte 1 byte n bytes 2 bytes Timeout

(min. 3.5 characters) (min. 3.5 characters)
4.5.3.2 Functionality of the Modbus-RTU Connection

▪ Connection using RS422 (point-to-point or 4-wire bus) or RS485 (2-wire bus, also called J-bus).
▪ Data is exchanged with the master cyclically.
▪ Simple parameterization of the interface using the operating console or the service tool.
Modbus mode: RTU
4.5.3.3 Configuration of the Modbus-RTU Connection
Refer to chapter 'Notes on Modbus' for diagnostics and troubleshooting.
4.5.3.3.1 Settings at the Modbus-RTU Slave



Settings in the 'Fieldbus Communication' block
Parameter Value range Default value Explanation

1)
Modbus-RTU here: Modbus-RTU
PROFIBUS DP
DeviceNet
Modbus-TCP
PROFINET IO
EtherNet/IP
IG (Ignore)
Event: Acyclic W2 (Warning 2) A Set the event class for 'Error Range Underrun/Exceeded
Communication W1 (Warning 1) during Acyclic Communication'
IG (Ignore)
A (ALARM)

Compatibility NO NO Compatibility setting towards the DISOCONT master

DISOCONT YES
Master
Word Sequence I:std/L:std I:std/L:std Establish the word sequence during the transmission of
I:swp/L:std measured values in IEEE/LONG format
I:std/L:swp
I:swp/L:swp
Address 1 … 254 1 Address of the slave at the Modbus
Resolution 1 ... 32767 4096 In analog or integer format this parameter gives the max-
imum number of characters of the transmitted value.
See chapter 'INTEGER Tables'
Baud rate 2400 19200 Data transmission rate

4800
9600
19200
38400
Data Format 8-O-1 8-O-1 Modbus always uses an 11 bit frame

8-E-1
8-N-1
Physics RS232 RS232 Select the type of electrical interface

RS485-2-wire
RS485-4-wire

4.5.3.3.2 Modbus-RTU Master Settings

▪ Configuration of the telegrams. If data from several segments is used, each segment requires at least
one telegram.
▪ Setting the correct byte sequence with values in IEEE and LONG format.
▪ Ensure that the data addresses are correctly configured. Some master stations send with the address
set + 1! In this case the slave will send an error telegram. A quick look at the diagnosis using either
the terminal's program or the service tool will identify the cause of the problem immediately.
▪ The maximum permissible telegram length is 256 bytes, including header and trailer bytes.
4.5.3.4 Available Data - List
4.5.3.4.1 Default values INTEGER
ID (Identifier) Value Value Feeder Type
hex dec Presets Value of VBW VBW VWF VLW VIF VMC
Integer For- 20650 20660 20650 20650 20650 20650
mat
0020 32 Serial Setpoint [kg/h] 0 to * * * *

MAXINCR = 0
to 300% P
0021 33 Serial Batch Setpoint [kg] 0 to * * * * * *

MAXINCR. =
0 to 100% P *
8 STD
Tab. 17 : Fieldbus Presets Integer format
4.5.3.4.2 Read values INTEGER (Measured values)
ID (Identifier) Value Calculation Feeder Type
hex dec Read Values Calculation VBW VBW VWF VLW VIF VMC
in Integer 20650 20660 20650 20650 20650 20650
Format
30 48 Feedrate [kg/h] 0 to * * * * * *
MAXINCR = 0
to 300% P
31 49 Totalizer 1 [kg] 0 to * * * * * *
MAXINCR = 0
to P * 8 STD
32 50 Totalizer 2 [kg] 0 to * * * * * *
MAXINCR = 0
to P * 24 STD
33 51 Totalizer 3 [kg] 0 to * * * * * *
MAXINCR = 0
to P * 720
STD

ID (Identifier) Value Calculation Feeder Type
hex dec Read Values Calculation VBW VBW VWF VLW VIF VMC
in Integer 20650 20660 20650 20650 20650 20650
Format
34 52 Belt Load [kg/m] 0 to * * *

MAXINCR = 0
to 200% Q
36 54 Belt Speed [m/s] 0 to * * *

MAXINCR = 0
to 100%V
[cm/s]
37 55 Speed [1/min] 0 to * *
MAXINCR = 0
to 100% N
38 56 Fill Weight [kg] 0 to *

MAXINCR = 0
to 100% F
3B 59 Setpoint [kg/h] 0 to * * * *
MAXINCR = 0
to 300% P
3C 60 Batch Actual Value [kg] 0 to * * * * * *

MAXINCR = 0
to P * 8
Stunden
3D 61 Batch Residual Amount [kg] 0 to * * * * * *

MAXINCR = 0
to P * 8
Stunden
3E 62 Perc. setpoint factor [%] 0 to * * * *

MAXINCR = 0
to 100 %
40 64 Deviation [%] 0 to * * * *
MAXINCR = 0
to 100 %
Tab. 18 : Fieldbus: Meas. Values Integer format

4.5.3.5 Modbus Module VSS8020

The interface card is an isolated, serial interface. The type of the interface is set using control unit parame-
ters and using jumpers in the plug. Both plugs are electrically parallel.
Module properties
Power supply Max. 250 mA
Plug connector to the bus activation XS2: clamp 7-pole

XS3: clamp 7-pole
Tab. 19 : Modbus module properties
Fig. 10: VSS 28020 Modbus module layout drawing
Serial interfaces pin assignment

Pin RS232 RS422 RS485
1 GND GND GND
2 TX Tx A RTx B
3 RX Rx A Jumper to pin 2
4 Rx B Jumper to pin 5
5 Tx B RTx A
6 Jumper to pin 4 for bus termination
7 Jumper to pin 3 for bus termination
Tab. 20 : Modbus serial interface pin assignment

Diagnostics and Troubleshooting
5 Diagnostics and Troubleshooting
5.1 General Information for all Fieldbus Types

If you have activated one of the fieldbuses, every error will be registered by the 'SYxx
*)
Event: Cyclic Communication' event message if this message has been assigned to an
event class not equal to IG(NORE).
The message is visible at the operating console and in the 'EasyServe' service tool.
EasyServe directly supplies further information for troubleshooting.
*)
'SYxx Event: Acyclic Communication' for acyclical data exchanges
Meaning of the event message

The event message is a group message for all errors relating to fieldbus operation. In detail these are:
▪ Different station addresses for master (PCS) and slave (weighing electronics).
▪ The fieldbus cable is defective or incorrectly connected.
▪ The protocol type selected odes not correspond to that of the interface card.
→ Change the parameterization or replace the interface connection.
▪ Timeout parameter has been set too low.
→ Change the parameterization of the slave.
5.2 Notes for PROFIBUS

Meaning of the event message:
▪ 'Mode of Operation' LED on the VPB 28020 (below) blinks red with 2 Hz, i.e. the configuration of the
slave does not agree with that of the master:
→ Change the incorrect GSD module or the parameterization of the slave.
▪ There is a problem with the cabling between the fieldbus connection and main board:
→ Observe the LEDs at the connection. If in doubt, turn the power off and on, if the parameterization
has been performed correctly the connection will be initialized (green LED will light continuously on
successful initialization).
▪ The bus termination is either absent or is present multiple times:
→ Check the resistances at the connection (the state upon delivery is 'not activated') and possibly the
resistances in the bus plugs.
▪ An impermissible ID has been identified in the telegram from the master to the slave:
→ Use IDs listed in bold face only!
▪ All preset value IDs in the telegram from the master have the value '0':
→ Communication between the master CPU and the communication processor CP has failed. At least
one preset value ID must have a correct, non-zero value or in FIXED mode the release bit must be
set.
5.3 Notes for DeviceNet

→ Observe the LEDs at the connection. If in doubt, turn the power off and on, if the parameterization

has been performed correctly the connection will be initialized (green LED will light continuously on
successful initialization).
▪ The bus termination is either absent or is present multiple times:
→ Check the resistances at the connection (the state upon delivery is 'not activated') and possibly the
resistances in the bus plugs.
one preset value ID must have a correct, non-zero value or in FIXED mode the clearance bit must be
set.
5.4 Notes for PROFINET

Meaning of the event message
▪ Check GSDML module or the parameterization.
→ Monitor the LEDs at the interface connection (see chapter PROFINET Interface VPN8020).
▪ An impermissible ID has been identified in the telegram from the IO controller to the IO device:
→ use only IDs printed in bold type!
▪ All preset IDs in the telegram from the IO controller have the value '0':
→ Communication between the master CPU and the communication processor CP has been inter-
rupted. At least one preset value ID must have a correct, non-zero value or in FIXED mode the re-
lease bit must be set.
5.5 Notes for EtherNet/IP

one preset value ID must have a correct, non-zero value or in FIXED mode the clearance bit must be
set.
5.6 Notes for Modbus

▪ Different station addresses are sent to the master and scales.
▪ Different baud rate settings are sent to the master and scales.
▪ The bus termination is either absent or is present multiple times. Check the wire jumpers in the con-
nection plug.
▪ The timeout parameter has been set at too small a value. Change the parameterisation of the scales.
▪ An improper ID has been identified in the telegram from the master to the scales.

5.7 User data diagnosis

The service tool 'EasyServe' can assist with the diagnostics by means of a variable display and filtering of
the protocol. All data streams are transmitted to EasyServe using the UDP protocol.
The dialog window can be opened via the menu 'View | Fieldbus'.
Depiction of external data
from 2012, calendar week 11 onwards (using the example of PROFIBUS DP):
(applies to all devices and the fieldbus types PROFIBUS DP, DeviceNet, PROFINET IO and EtherNet/IP)
up to 2012, calendar week 11 (Modbus-TCP example):

(valid for all devices and fieldbus types)

1 Call up master simulator (Modbus-TCP) 4 Direction of data flow and channel information
2 Active only when EasyServe is connected serially 5 Time accurate to the millisecond (device)
3 Date and time (PC) 6 Telegram display:

Modbus + Modbus-TCP: Modbus frame
PROFIBUS DP + DeviceNet: User data
EtherNet/IP: User data
In newer software versions diagnostic outputs with the identifier 'H' replace those with identifier 'O'.
They also display the selected user data structure and in FIXED mode the identifier 'participating'
*)
in round brackets at each start , e. g. (0140).
*)
This ID was not transmitted, however; it is shown here for diagnostics purposes only.
The upper row indicates actions that can be taken, the selection fields in the lower row allow the selection
(filtering) of particular data after recording has been stopped.
1) Meaning of the buttons in the upper row:
Button Function
[Record] Begin data logging
[Display] Stop data logging

Stop
[Copy] All telegrams (not a selection), individual telegrams or a group of telegrams can be selected with the
mouse. These are then stored in the clipboard and can be transferred to the windows editor
(NOTEPAD) to be edited.
Select whether data flow in this direction should be logged (scales → fieldbus).
*)
⊠ Transmit
Select whether data flow in this direction should be logged (fieldbus → scales).
*)
⊠ Receive
*)
⊠ Time Select whether the duration between telegrams (in ms) of the telegrams is to be logged (activate
time stamp).
*)
active only when EasyServe is connected serially

2) Meaning of the buttons in the lower row:

The direction filter ('Filter') offers the following possible selections:
… All
< or { Send (from point of view of controller)
> or } Reception
The two channel filters ('Channel') show all of the channels that appear in the log.
… All
T Communication EasyServe
U Acyclic fieldbus communication
H Cyclic fieldbus communication
O Cyclic fieldbus communication (up to 2012, CW11)
L Optional local bus communication
The data of two host channels can be filtered out by combining the channel filters.

Some Examples of Applications
6 Some Examples of Applications
6.1 Zeroing and Taring a Beltweigher (Weighfeeder)

This section describes the steps required to adjust a weighfeeder via fieldbus.
Primarily, the IDs of the commands and the statuses of the fieldbuses will be presented and described in
more detail. Detailed documentation on adjustment can be found in the 'Operating Manual INTECONT Ter-
sus Weighfeeder VWF' (BV-H2463).
Step ID (hex) ID (dec) Comment
Exit normal operation and prepare zeroing/taring
1 Stop Feeder 0x0141 321 To ensure that the 'Batch' function can be de-
selected.
2 Abort Batch 0x0152 338 ditto.
3 Deselect Batch 0x0151 337
4 Volumetric Mode 0x0144 324 Activate volumetric mode (speed ~ setpoint)
5 Stop Prefeeder 0x015F 351 The prefeeder and the feed gate will remain
closed even if the setpoint is non-zero.
6 Start Feeder 0x0140 320
The setpoint does not have to be 0. The belt will run proportionally to the setpoint.
If P=Po then v=vo; if P=Pn then v=vn.
Allow the belt to run until the belt load is approximately 0.
7 Belt Load 0x0758 1880 Read value
Decide whether to 'Tare' or 'Zero':
If taring:
8 TW: Tare 0x0170 368 Start
9 TW: Tare 0x0308 776 Verify status bit. This status must remain until
taring is complete.
if zeroing:
8 >0< Zero Set 0x0171 369 Start
9 >0< Zero Set 0x0309 777 Verify status bit. This status must remain until
zeroing is complete.
continue:
10 Waiting for Confirmation 0x0331 817 Wait for status change
if zeroing:
11 Results of the adjustment are con- 0x07AC 1964 Calibration Display 1

tained in the measured values Difference to previous zeroing or taring
If taring:
11 0x07AE 1966 Calibration Display 2

New value for Basic Tare (P09.04) or Tare
Correction(P09.05)

Step ID (hex) ID (dec) Comment
continue:
Acquire adjustment result:
12a Check adjustment result Apply 0x017B 379 Or continue with 12b
and
0x0758 1880 The measured value of the belt load must be
Belt Load
zero if you select apply! (fluctuate around
zero)
12b Cancel 0x017C 380 Reject results of the adjustment and cancel
Return to normal operation:
13 Stop Feeder 0x0141 321
14 Select Batch 0x0150 336 Activate batch (if required)
15 Particip. Prefeeder 0x015E 350
16 Gravimetric 0x0145 325 Activate gravimetric mode
17 Enter the desired setpoint and, if required, the batch setpoint
18 Continue in normal operation
Using CFC:
4 preset values: 1. 2. 3. 4.
fixed fixed fixed Apply DP_ID_V3

to
0x0160
This makes 'Multiplex Mode', by switching the read IDs, unnecessary.
6.2 Batching per Fieldbus

Please note that not all actions are available for every scales model. You can refer to the list of cyclical data
to check the availability.
Step Data Type ID (hex) ID (dec) Comment
Preparations:
Block 'Rated Data': Parameter 'Feeder Start' = FB
Block 'Batch Mode': Parameter 'Batch Setpoint Source' = FB
1 Select Batch Command 0x0150 336 Activate batching mode

(positive slope).
Will be retained by the scales in case of
a loss of power.
2 Serial Batch Setpoint Setpoint 0x0252 594 Specify the batch setpoint [kg].
(IEEE float) Setpoints that are transmitted during a
running batch will take effect only when
the next batch is started!
3 Batch No. Setpoint 0x0256 598 Specify the batch number.

(IEEE float)
4 Start Feeder Command 0x0140 320 Start batch

(positive slope).

Step Data Type ID (hex) ID (dec) Comment
5 Batch active Status 0x0301 769 Test 'Batch active'.

Log. '1' during coarse/dribble feed and
follow-up time.
6 Batch Dribble Feed Status 0x0302 770 Test batch pre-contact,

dribble feed active.
7 Status 44+45 Status 0x0590 1424 Query the digital outputs of the scales
(e.g. scales on/off, prefeeder on/off).
8 Stop Feeder Command 0x0141 321 Interrupt batching

(positive slope).
The running batch can be continued
with the start command.
9 Start Feeder Command 0x0140 320 Allow batching to continue

(positive slope).
10 Abort Batch Command 0x0152 338 End batching

(positive slope).
A subsequent start command will begin
a new batch, the previous batch will not
be continued!
11 Batch Resid. Amount Measured 0x076A 1898 Query the residual batch quantity [kg].
values Quantity yet to be discharged.
(IEEE float)
12 Batch Actual Value Measured 0x0768 1896 Batch actual value [kg].
values Quantity already discharged.
(IEEE float)
13 Deselect Batch Command 0x0151 337 Deactivates batch mode.

(positive slope).
Telegram with PPO type: NO_PARA_ID_3_6
ID hex dec Value Task
Presets:
ID1 0x0140 320 Command 04+05 Start, stop, reset counter,

etc.
ID2 0x0160 352 Command 06+07 Due to start zeroing

scales + acquire adjust-
ment result/abort adjust-
ment
ID3 0x0252 594 Serial Batch Setpoint
Read values:

ID hex dec Value Task
ID1 0x0310 784 Status 04+05 Due to query scales

whether batch with 'run
empty' is active
ID2 0x0330 816 Status 06+07 Due to scales adjustment

+ wait for acknowledge-
ment
ID3 0x0590 1424 Status 44+45 Due to scales on/off +

prefeeder on/off
ID4 0x0768 1896 Batch Actual Value
ID5 0x0752 1874 Totalizer 1
ID6 0x0610 1552 Status 52+53 Highest priority event

Appendix
7 Appendix
7.1 Common Abbreviations

MAXPARTS Maximum number of parts Refer to the parameter Modbus
AK Task Identifier or Reply Identifier 3 bits, part of the parameter identifier
CP Communication Processor Communication component for control systems, PC or pe-

ripheral devices
DU Data Unit Payload; 1 to 246 bytes
ID Identifier 16 bit identifier in the weighing system for all values
IND Index in the expanded parameter block Indicates which part of the parameter description will be
transmitted
PKE Parameter ID Consists of PNU and AK
PKW Parameter – Identifier - Value Parameter range of the cyclical payload exchange
PNU Parameter number 13 bit, corresponds to the PZK in the weighing system
PZD Process Data Range Current control, setpoint, status and measured value data
PPO Parameter process-data object Total payload information of a cyclical data packet
PWE Parameter value Current parameter value or part of the parameter descrip-
tion, depends on the PKE
PZK Process data identifier System-wide unique identifier for all values in the weighing
system
VLW Loss-in-weight feeder
VWF Weighfeeder
VBW Belt weigher
VCM Mass-flow feeder
VIF Flow feeder
VKD Component feeder
7.2 Abbreviations in the List of Cyclical Data

Shortcut Identifier (ID) dec. Type Meaning
P 4226 Parameters Maximum Flow Rate Io
Q 1996 Measured Nominal Belt Load (belt-supported systems)

2004 values Nominal Load
Measured
values
V 4227 Parameters Nominal Speed
F 4258 Parameters LC Rated Capacity (Feed hopper)
N 4643 Parameters Nominal Speed

Appendix
7.3 Glossary
Item Explanation
GSD file PROFIBUS-specific configuration file in ASCII format containing information on node proper-
(General Station De- ties, e.g. supported baud rates and other properties. If a new node is added the master must
scription file) be informed of the change in the network. This is done by installing a *.GSD configuration file.
This file contains information on the new node's available functions.
(also: device configuration file)
GSDML file PROFINET-specific configuration file

Generic Station Description Markup Language: GSDML is the description language for creat-
ing a GSD file. It is XML-based.
(also: device configuration file)
Cyclic Data Information sent to and from nodes at regular intervals. This information usually contains start
and stop values, setpoints and other control values; items that must continuously be updated.
Cyclic data are also called process data.
Acyclic Data Information sent to and from nodes at irregular intervals. This information usually includes
configuration data, e.g. the specifications of a motor. This information need not be transmitted
regularly as it does not change.
Master Central unit that controls the system, usually a PLC. In a PROFIBUS network a master is often
referred to as an 'Active Station'.
PROFINET IO: specified as an IO controller
Slave Weighing electronics, controller

PROFINET IO: specified as an IO device
(Bus) termination Method of damping a signal at the end of a cable to avoid reflections. A simple terminating
resistor is usually used.
PE Protective earth; connecting point to which the earth of the network is connected.
PROFIBUS DP Decentralized periphery ('classic' fieldbus)
PROFINET PROFIBUS user organization open industrial Ethernet standard for automation (Ethernet-
based fieldbus)
IO Input-output (input and output unit), also the code designation for the PROFINET standard in
this field
IO controller Device (typically a controller) that initiates I/O data communication
IO device Process-oriented PROFINET device used to connect the IO controller to the process.
Tab. 21 : Terms and abbreviations used

Index
Index
Abbreviations in the List of Cyclical Data ........................................................................................................................ 161
Acknowledging Event Messages......................................................................................................................................... 3
Acyclic Data (Explicit Messages) EtherNet/IP ................................................................................................................. 130
Acyclic Data PROFINET ................................................................................................................................................. 122
Acyclic Services .............................................................................................................................................................. 121
Acyclical Data (Explicit Messages) DeviceNet ................................................................................................................ 104
Acyclical Data (Explicit Messages) Modbus .................................................................................................................... 140
Acyclical Data Exchanges between PCS and Weighing Electronics ............................................................................... 132
Acyclical Data PROFIBUS ................................................................................................................................................ 97
Appendix ......................................................................................................................................................................... 161
Application Relation ........................................................................................................................................................ 117
Arrangement of the components ............................................................................................................... 95, 102, 106, 150
Automatic Order List ......................................................................................................................................................... 27
Available Data - List .................................................................................................................................................. 35, 148
Batching per Fieldbus...................................................................................................................................................... 158
Caution ................................................................................................................................................................................ 5
Common Abbreviations ................................................................................................................................................... 161
Communication Channels ............................................................................................................................................... 142
Configuration of the DeviceNet Connection ...................................................................................................................... 99
Configuration of the Ethernet Connection ....................................................................................................................... 125
Configuration of the Modbus-RTU Connection................................................................................................................ 146
Configuration of the Modbus-TCP Connection ................................................................................................................ 143
Configuration of the PROFIBUS Connection..................................................................................................................... 88
Configuration of the PROFINET Connection ................................................................................................................... 109
Cyclical Data Exchange .................................................................................................................................................... 35
Damaged/Defective Electrical Components ........................................................................................................................ 6
Danger ................................................................................................................................................................................ 4
Data Formats .................................................................................................................................................................. 138
Data Segments ................................................................................................................................................................... 7
Data Types (Numerical Notation) ........................................................................................................................................ 8
Database ............................................................................................................................................................................. 7
Default Values ................................................................................................................................................................... 36
Default values INTEGER................................................................................................................................................. 148
Design Modifications ........................................................................................................................................................... 4
DeviceNet.......................................................................................................................................................................... 99
DeviceNet Master Settings (PCS) ................................................................................................................................... 101
DeviceNet Module VCB 28020........................................................................................................................................ 106
DeviceNet Module VCB8020........................................................................................................................................... 102
DeviceNet Slave Settings .................................................................................................................................................. 99
Diagnostics and Troubleshooting .................................................................................................................................... 151
Dimensions ....................................................................................................................................................................... 10
EtherNet/IP...................................................................................................................................................................... 124
EtherNet/IP Slave Settings .............................................................................................................................................. 125
Events - Overview ............................................................................................................................................................. 81
Example for 'Displays of Fixed Mode Configuration' ....................................................................................................... 133
Example for 'Write a Process or Parameter value' .......................................................................................................... 132
Example of 'FIXED Mode' Telegram (FIXED_8_8) ............................................................................................................ 20
Example Telegrams 'Variable Mode' ................................................................................................................................. 31
Examples of Telegrams (Process Values) ...................................................................................................................... 139
Explicit Messages ........................................................................................................................................................... 132
Explicit Messaging .............................................................................................................................................................. 7
Fault codes...................................................................................................................................................................... 138
Fieldbus Connections ........................................................................................................................................................ 87
Fig. 1: VPB 28020 PROFIBUS module layout drawing ..................................................................................................... 95
Fig. 10: VSS 28020 Modbus module layout drawing ....................................................................................................... 150
Fig. 2: Light-emitting diodes – VPB 28020 front view ........................................................................................................ 96
Fig. 3: VCB 28020 DeviceNet module layout drawing ..................................................................................................... 102
Fig. 4: VCB 28020:XC1 DeviceNet module front view .................................................................................................... 103
Fig. 5: VCB 28020 DeviceNet module layout drawing ..................................................................................................... 106
Fig. 6: VCB 28020:XC1 DeviceNet module front view .................................................................................................... 107
Fig. 7: PROFINET star topology ...................................................................................................................................... 119
Fig. 8: PROFINET line topology ...................................................................................................................................... 120
Fig. 9: PROFINET ring topology ...................................................................................................................................... 120
Five Safety Rules of Electrical Engineering......................................................................................................................... 5
Format NO_PARA_ID_3_6 ................................................................................................................................................ 31

Index
Format of the Safety Notices ............................................................................................................................................... 5

Format PARA_ID_2_4 with 'Change Parameter' ............................................................................................................... 32
Function codes (FC) ........................................................................................................................................................ 137
Functionality of the DeviceNet Connection........................................................................................................................ 99
Functionality of the Ethernet Connection......................................................................................................................... 125
Functionality of the Modbus-RTU Connection ................................................................................................................. 146
Functionality of the Modbus-TCP Connection ................................................................................................................. 143
Functionality of the PROFIBUS Connection ...................................................................................................................... 88
Functionality of the PROFINET Connection .................................................................................................................... 109
General Information ................................................................................................................................ 7, 14, 21, 135, 145
General Information for all Fieldbus Types...................................................................................................................... 151
General Payload Structure (VARIABLE Mode) ................................................................................................................. 21
General Telegram Structure ............................................................................................................................................ 136
Glossary .......................................................................................................................................................................... 162
Guidelines for Commissioning............................................................................................................................. 87, 99, 108
Guidelines for Startup.............................................................................................................................................. 125, 136
Highest priority event ........................................................................................................................................................ 10
IDs (Identifiers) .................................................................................................................................................................... 9
Illustration of the Telegram Bytes on Command ............................................................................................................... 12
Integrating the IO Device................................................................................................................................................. 112
Integration Slave ............................................................................................................................................................... 91
Intended Use ....................................................................................................................................................................... 3
Issue IP Address and Name for PROFINET IO Subscriber............................................................................................. 114
Keeping the Technical Documentation ................................................................................................................................ 4
Layout of the Components .............................................................................................................................................. 117
LEDs H110, H120 ............................................................................................................................................. 96, 103, 107
LEDs in the Ethernet Connection (RJ45) ........................................................................................................................ 118
LEDs on the Board .......................................................................................................................................................... 117
Line Topology.................................................................................................................................................................. 120
Maintenance and Repair ..................................................................................................................................................... 4
Message Command ........................................................................................................................................................ 132
Modbus (Serial and Network) .......................................................................................................................................... 135
Modbus Module VSS8020............................................................................................................................................... 149
Modbus-RTU ................................................................................................................................................................... 145
Modbus-RTU Master Settings ......................................................................................................................................... 147
Modbus-TCP ................................................................................................................................................................... 142
Modbus-TCP Master Settings ......................................................................................................................................... 145
Moisture and humidity ......................................................................................................................................................... 4
Monitoring ID ..................................................................................................................................................................... 26
Note..................................................................................................................................................................................... 5
Notes for DeviceNet ........................................................................................................................................................ 151
Notes for EtherNet/IP ...................................................................................................................................................... 152
Notes for Modbus ............................................................................................................................................................ 152
Notes for PROFIBUS ...................................................................................................................................................... 151
Notes for PROFINET....................................................................................................................................................... 152
Order list............................................................................................................................................................................ 23
order list, automatic ........................................................................................................................................................... 27
order list, normal ............................................................................................................................................................... 26
order list, variable .............................................................................................................................................................. 26
Overview ............................................................................................................................................................................. 1
Parameter Changes ............................................................................................................................................................ 3
Parameter Range in Detail ................................................................................................................................................ 29
Parameter Transmission ................................................................................................................................................... 28
Parameters...................................................................................................................................................................... 140
Password ............................................................................................................................................................................ 3
Payload ........................................................................................................................................................................... 139
Payload Range and Content FIXED Mode ........................................................................................................................ 15
Payload Range and Content VARIABLE Mode ................................................................................................................. 23
Payload Structure .............................................................................................................................................................. 14
Personnel ............................................................................................................................................................................ 3
Potential Sources of Danger ............................................................................................................................................... 3
PROFIBUS DP .................................................................................................................................................................. 87
PROFIBUS Module VPB8020 ........................................................................................................................................... 95
PROFINET interface VPN 8020- network topology ......................................................................................................... 119
PROFINET Interface VPN8020 ....................................................................................................................................... 116
PROFINET IO ................................................................................................................................................................. 108
Read IEEE Values ............................................................................................................................................................ 74
Read Status ...................................................................................................................................................................... 42

Index
Read Values...................................................................................................................................................................... 42
Read values INTEGER (Measured values) ..................................................................................................................... 148
Redundancy Manager 'Ring Manager' ............................................................................................................................ 120
Redundant Modbus-TCP................................................................................................................................................. 145
Replacing Components ....................................................................................................................................................... 4
Ring Topology ................................................................................................................................................................. 120
Safeguarding Transmission............................................................................................................................................. 138
Safety Instructions ............................................................................................................................................................... 3
Serial interfaces pin assignment ..................................................................................................................................... 150
Settings ..................................................................................................................................................... 95, 102, 106, 117
Settings at the EtherNet/IP Master (ControlLogix) .......................................................................................................... 127
Settings at the Modbus-RTU Slave ................................................................................................................................. 146
Settings at the Modbus-TCP Slave ................................................................................................................................. 143
Settings at the PROFIBUS Master (PCS) ......................................................................................................................... 90
Settings at the PROFIBUS Slave ...................................................................................................................................... 88
Settings at the PROFINET IO Controller ......................................................................................................................... 110
Settings at the PROFINET IO Device.............................................................................................................................. 109
Signal Words ....................................................................................................................................................................... 4
Signal Words for Danger Warnings ..................................................................................................................................... 4
Signal Words for Usage Instructions ................................................................................................................................... 5
Simplified Payload Structure (FIXED Mode) ..................................................................................................................... 14
Some Examples of Applications ...................................................................................................................................... 157
Star Topology .................................................................................................................................................................. 119
Strictly Observe ................................................................................................................................................................... 5
Subscriber Addresses ..................................................................................................................................................... 136
Supplementary Documentation ................................................................................................................. 98, 105, 135, 142
Supplementary Documentation: ...................................................................................................................................... 124
Tab.1: VARIABLE formats................................................................................................................................................. 24
Tab.10: LED 'Status' (above) ............................................................................................................................................ 96
Tab.11: 'Bus activation' connector................................................................................................................................... 103
Tab.12: LED 'Network Status' (above) ............................................................................................................................ 103
Tab.13: LED 'Module Status' (below) .............................................................................................................................. 103
Tab.14: 'Bus activation' connector................................................................................................................................... 107
Tab.15: LED 'Network Status' (above) ............................................................................................................................ 107
Tab.16: LED 'Module Status' (below) .............................................................................................................................. 107
Tab.17: Fieldbus Presets Integer format ......................................................................................................................... 148
Tab.18: Fieldbus: Meas. Values Integer format............................................................................................................... 149
Tab.19: Modbus module properties................................................................................................................................. 149
Tab.2: VARIABLE formats................................................................................................................................................. 28
Tab.20: Modbus serial interface pin assignment ............................................................................................................. 150
Tab.21: Terms and abbreviations used ........................................................................................................................... 162
Tab.3: Fieldbus Commands .............................................................................................................................................. 41
Tab.4: Fieldbus Presets .................................................................................................................................................... 41
Tab.5: Fieldbus Status ...................................................................................................................................................... 74
Tab.6: Fieldbus Measurement Values ............................................................................................................................... 81
Tab.7: Fieldbus Events...................................................................................................................................................... 86
Tab.8: 'Bus activation' connector....................................................................................................................................... 96
Tab.9: LED 'Operating Mode' (below) ............................................................................................................................... 96
Telegram Structure (Variable Payload) ............................................................................................................................. 24
User data diagnosis ........................................................................................................................................................ 153
Warning ............................................................................................................................................................................... 5
Write Commands .............................................................................................................................................................. 36
Write IEEE Values ............................................................................................................................................................. 41
Zeroing and Taring a Beltweigher (Weighfeeder)............................................................................................................ 157


BVH2474 GB

Uploaded by

Copyright:

Available Formats

BVH2474 GB

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BVH2474 GB

Uploaded by

Copyright:

Available Formats

INTECONT® Tersus

Heavy Advisory Service about Spare Parts, Maintenance

Logistical and Industrial Scales

24h Hotline: +49 172 650 1700

Individual phone consulting - fee required

© by Schenck Process GmbH, Pallaswiesenstraße 100, 64293 Darmstadt, Germany

Note: The original manual is in German. This is a translation.

(63050395179714059 V8, 01/12/2015)

2 Safety Instructions ....................................................................................................................................3

4 Fieldbus Connections ............................................................................................................................ 89

INTECONT® Tersus Data Communication, BV-H2474GB, V8

4.2.4 DeviceNet Module VCB8020 .....................................................................................................105

5 Diagnostics and Troubleshooting ...................................................................................................... 157

BV-H2474GB, V8 INTECONT® Tersus Data Communication,

5.7 User data diagnosis ............................................................................................................................159

6 Some Examples of Applications ......................................................................................................... 163

7 Appendix ............................................................................................................................................... 167

Index ...................................................................................................................................................... 169

INTECONT® Tersus Data Communication, BV-H2474GB, V8

How are both systems connected?

What is described in this manual?

INTECONT® Tersus Data Communication, BV-H2474GB, V8

Overview of supplementary manuals:

BV-H2463 INTECONT Tersus weighfeeder - operating manual

BV-H2464 INTECONT Tersus belt weigher - operating manual

BV-H2476 INTECONT Tersus loss-in-weight feeder - operating manual

BV-H2477 INTECONT Tersus MULTICOR - operating manual

BV-H2478 INTECONT Tersus MULTISTREAM - operating manual

BV-H2466AA Weighing processor - Module Description DP-V1

BV-H2473 Step7 Library - CONTI_S7, DISCO_S7, DP-V1, ARM_Controller

BV-H2474 INTECONT Tersus - Data Communication

BV-H2427AA DISOCONT Tersus and INTECONT Tersus, Opus, Satus -

BV-H2185 Schenck Process EasyServe - Operating Manual

BV-H2474GB, V8 INTECONT® Tersus Data Communication,

Potential Sources of Danger

Acknowledging Event Messages

INTECONT® Tersus Data Communication, BV-H2474GB, V8

Maintenance and Repair

Moisture and humidity

Keeping the Technical Documentation

2.1 Signal Words

2.1.1 Signal Words for Danger Warnings

BV-H2474GB, V8 INTECONT® Tersus Data Communication,

Format of the Safety Notices

2.1.2 Signal Words for Usage Instructions

INTECONT® Tersus Data Communication, BV-H2474GB, V8

2.2 Five Safety Rules of Electrical Engineering

2.3 Damaged/Defective Electrical Components

BV-H2474GB, V8 INTECONT® Tersus Data Communication,

3.1 General Information

3.1.1 Data Segments

Commands (Bit or byte information)

► Acyclic Data (Explicit Messaging):

INTECONT® Tersus Data Communication, BV-H2474GB, V8

3.1.2 Data Types (Numerical Notation)

FLOAT Sign/Exponent Mantissa 1 Mantissa 2 Mantissa 3

150.5 0x43 0x16 0x80 0x00

Further examples of floating-point numbers

► Integer values (INTEGER)