Tersus Data Communication Programming Manual

DISOCONT® Tersus
Data Communication
Programming Manual
BV-H2448 GB
PASS - Process Advanced Service System
Services and wearing parts for your applications.
Looking for after-sales solutions? Our comprehensive Process Advanced Service System (PASS) provides you with a customer-
oriented after-sales service tailored to your specific requirements.
Our experienced Schenck Process team will be happy to help you to create PASS packages that satisfy your needs. These packages
can consist of replacement and wear parts and a range of services and other components of the highest quality. We would be happy
to provide you with individual consultation - whether as part of a PASS contract or as an individual enquiry.
Contacts
Find your local contact on our Internet page:
http://www.schenckprocess.com/contact
Schenck Process Europe GmbH Schenck Process LLC

Pallaswiesenstr. 100 7901 NW 107th Terrace
64293 Darmstadt Kansas City, MO 64153
GERMANY USA
T: +49 61 51-15 31 0 T: +1 816-891-9300
F: +49 61 51-15 31 66 F: +1 816-801-3472
sales@schenckprocess.com mktg@schenckprocess.com
Stock Equipment Company Inc. Schenck Process Pty Ltd

16490 Chillicothe Road Ground Floor, 65 Epping Road,
Chagrin Falls, OH 44023 North Ryde, NSW 2113,
USA AUSTRALIA
T: +1 440-543-6000 T: +61 2 98 86 6800
F: +1 440-543-5944 F: +61 2 98 78 44 00
stock.sales@stockequipment.com sales@schenckprocess.com.au
Copyright
All rights reserved. Any reproduction of this documentation, regardless of method, without prior permission in writing, even by excerpt,
is prohibited. Subject to change without prior notice.
(63050394994737163 V8, 19/07/2017)

Translation of Original Document
Table of Contents
Table of Contents
1 Overview.....................................................................................................................................................1
2 Safety Information .....................................................................................................................................3

2.1 Signal Words ..........................................................................................................................................5
2.1.1 Signal Words for Danger Warnings ...............................................................................................5
2.1.2 Signal Words for Usage Instructions ..............................................................................................6
2.2 Five Safety Rules of Electrical Engineering ...........................................................................................6
2.3 Damaged/Defective Electrical Components ...........................................................................................7
3 Database.....................................................................................................................................................9
3.1 General Information ................................................................................................................................9
3.1.1 Data Segments ..............................................................................................................................9
3.1.2 Data Types (Numerical Notation) .................................................................................................10
3.1.3 IDs (Identifiers) .............................................................................................................................12
3.1.4 Dimensions...................................................................................................................................12
3.1.5 Highest Priority Event ...................................................................................................................13
3.1.6 Illustration of the Telegram Bytes on Command ..........................................................................15
3.2 Payload Structure .................................................................................................................................16
3.2.1 Simplified Payload Structure ........................................................................................................17
3.2.1.1 General Information .....................................................................................................................17
3.2.1.2 Payload Scope and Content FIXED Mode...................................................................................18
3.2.1.3 Example of 'FIXED Mode' Telegram ............................................................................................24
3.2.2 General Payload Structure (VARIABLE Mode)............................................................................26
3.2.2.1 General Information .....................................................................................................................26
3.2.2.2 Payload Scope and Content VARIABLE Mode ...........................................................................27
3.2.2.3 Telegram Structure (Variable payload) ........................................................................................29
3.2.2.4 Parameter Transmission ..............................................................................................................35
3.2.2.5 Example Telegrams 'Variable Mode' ...........................................................................................37
3.3 Available Data - Listing .........................................................................................................................50
3.3.1 Cyclical and Acyclical Data Exchanges .......................................................................................50
3.3.1.1 Preset Values ...............................................................................................................................51
3.3.1.2 Read values .................................................................................................................................58
3.3.2 Material-Dependent Parameters (MDP) ....................................................................................105
3.3.2.1 Material-Dependent Parameters (MDP) ....................................................................................129
3.3.3 Events - Overview ......................................................................................................................150
4 Fieldbus Connections .......................................................................................................................... 161

4.1 PROFIBUS DP ...................................................................................................................................161
4.1.1 Guidelines for Commissioning ...................................................................................................162
4.1.2 Functionality of the PROFIBUS Connection ..............................................................................162
4.1.3 Configuration of the PROFIBUS Connection .............................................................................163
4.1.3.1 Settings at the PROFIBUS Slave ...............................................................................................163
4.1.3.2 Settings at the PROFIBUS-Master (PCS)..................................................................................164
4.1.4 PROFIBUS Interface VPB8020 .................................................................................................171
4.1.5 Acyclic Services .........................................................................................................................174
4.1.5.1 Acyclical Data PROFIBUS .........................................................................................................174
4.1.6 Supplementary Documentation ..................................................................................................177
4.2 DeviceNet ...........................................................................................................................................178
4.2.2 Functionality of the DeviceNet Connection ................................................................................178
4.2.3 Configuration of the DeviceNet Connection ...............................................................................179
DISOCONT® Tersus Data Communication, Programming Manual BV-H2448GB, V8

Schenck Process Group -i-
Table of Contents
4.2.3.1 Settings at the DeviceNet Slave ................................................................................................179

4.2.3.2 DeviceNet Master Settings (PCS) ..............................................................................................180
4.2.4 DeviceNet Interface VCB8020 ...................................................................................................182
4.2.5 Acyclical Data DeviceNet ...........................................................................................................184
4.3 PROFINET IO .....................................................................................................................................188
4.3.1 Guidelines for Initial Startup .......................................................................................................189
4.3.2 Functionality of the PROFINET Connection ..............................................................................189
4.3.3 Configuration of the PROFINET Connection .............................................................................191
4.3.3.1 Settings at the PROFINET IO Device ........................................................................................191
4.3.3.2 Settings at the PROFINET IO Controller ...................................................................................192
4.3.4 PROFINET Interface VPN8020 .................................................................................................198
4.3.4.1 PROFINET IO Module ...............................................................................................................198
4.3.4.2 PROFINET IO Network Topology with VPN8020 ......................................................................201
4.3.4.3 Connecting the PROFINET IO Module to the Star Topology ....................................................203
4.3.5 Acyclic Services .........................................................................................................................204
4.3.5.1 Acyclic Data PROFINET ............................................................................................................205
4.4 EtherNet/IP .........................................................................................................................................209
4.4.2 Functionality of the Ethernet Connection ...................................................................................210
4.4.3 Configuration of the Ethernet Connection ..................................................................................210
4.4.3.1 EtherNet/IP Slave Settings.........................................................................................................210
4.4.3.2 Settings at the EtherNet/IP Master (ControlLogix) .....................................................................212
4.4.4 Acyclic Data (Explicit Messages) EtherNet/IP ...........................................................................216
4.4.4.1 Acyclic Data Exchange between PCS and Scales Electronics..................................................218
4.5 Modbus (Serial and Network) .............................................................................................................221
4.5.1 General Information ...................................................................................................................221
4.5.1.1 Guidelines for Commissioning ...................................................................................................222
4.5.1.2 General Telegram Structure.......................................................................................................222
4.5.1.3 Subscriber Addresses ................................................................................................................223
4.5.1.4 Function Codes (FC) ..................................................................................................................223
4.5.1.5 Error Codes ................................................................................................................................224
4.5.1.6 Data Formats .............................................................................................................................224
4.5.1.7 Ensuring Transmission...............................................................................................................224
4.5.1.8 Payload ......................................................................................................................................225
4.5.1.9 Examples of Telegrams (Process Values) .................................................................................225
4.5.1.10 Parameters .................................................................................................................................226
4.5.1.11 Acyclical Data Modbus ...............................................................................................................226
4.5.1.12 Supplementary Documentation ..................................................................................................229
4.5.2 Modbus-TCP ..............................................................................................................................230
4.5.2.1 Functionality of the Modbus-TCP Connection ...........................................................................230
4.5.2.2 Configuration of the Modbus-TCP Connection ..........................................................................230
4.5.2.3 Redundant Modbus-TCP ...........................................................................................................232
4.5.3 Modbus-RTU ..............................................................................................................................233
4.5.3.1 General Information ...................................................................................................................233
4.5.3.2 Functionality of the Modbus-RTU Connection ...........................................................................233
4.5.3.3 Configuration of the Modbus-RTU Connection ..........................................................................233
4.5.3.4 Available Data - Listing ..............................................................................................................235
4.5.3.5 Modbus Interface VSS8020 .......................................................................................................237
5 Diagnosis and Troubleshooting ......................................................................................................... 239

5.1 General Information for all Fieldbus Types ........................................................................................239
5.2 Notes for PROFIBUS DP ....................................................................................................................239
5.3 Notes for DeviceNet ...........................................................................................................................240
BV-H2448GB, V8 DISOCONT® Tersus Data Communication, Programming Manual

- ii - Schenck Process Group
Table of Contents
5.4 Notes for PROFINET IO .....................................................................................................................240

5.5 Notes for EtherNet/IP .........................................................................................................................240
5.6 Notes for Modbus ...............................................................................................................................241
5.7 User Data Diagnosis ...........................................................................................................................241
6 Some Examples of Applications ......................................................................................................... 245

6.1 Zeroing and Taring a Weighfeeder (VWF) .........................................................................................245
6.2 Internal On-Stream Calibration System of a Weighfeeder (VWF)......................................................247
6.3 Taring a Loss-in-Weight Feeder (VLW)..............................................................................................252
6.4 Loss-in-Weight Feeder (VLW) Inlet Gate Control...............................................................................253
6.5 Adjusting Capacity via Fieldbus..........................................................................................................253
7 Appendix ............................................................................................................................................... 257

7.1 Common Abbreviations ......................................................................................................................257
7.2 Abbreviations in the List of Cyclical Data ...........................................................................................258
7.3 Glossary..............................................................................................................................................258
Index ...................................................................................................................................................... 264

Schenck Process Group - iii -
Overview
1 Overview
For whom has this manual been written?
This manual is aimed at the experienced technicians and programmers whose task it is to connect
®
a DISOCONT Tersus system (hereinafter referred to also as weighing electronics, scales or device for the
sake of simplicity) to an existing Process Control System (PCS, system controller).
This requires good working knowledge of both systems and basic knowledge of data exchanges in local
computer networks.
How are both systems connected?
The weighing electronics can communicate with the PCS through an optional fieldbus connection. In this
configuration the PCS is always the bus master and the weighing 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-H2406 System Manual

BV-H2407 Instruction manual for weighfeeder VWF
BV-H2410 Instruction manual for loss-in-weight feeder VLW
BV-H2412 Instruction manual for MULTICOR feeder VWC
BV-H2414 Instruction manual for solids flow feeder MULTISTREAM VIF
BV-H2416 Instruction manual for beltweigher VBW
BV-H2417 Instruction manual for MultiFlex VSF helix weighfeeder
BV-H2185 Schenck Process EasyServe

-2- Schenck Process Group
Safety Information
2 Safety Information
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 the production process.
Password
Passwords safeguard the parameters against unauthorized changes. The measuring system operator has to
ensure that the password is handled responsibly.

Safety Information
Acknowledging Event Messages

Error messages may be acknowledged only after cause of fault has been remedied.
Ensure that any connected peripheral devices are functioning correctly before acknowledging an event. Any
connected control systems in particular must be in safe state.
Service and Maintenance

▪ All attached warning and instruction signs 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.
▪ 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 system 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.

Safety Information
2.1 Signal Words

2.1.1 Signal Words for Danger Warnings
The use of technical equipment always contains potential dangers. 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.
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

Safety Information
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
Notice
The signal word NOTICE is used to highlight information on using the product economically and at an opti-
mal level of efficiency.
For Example:
NOTICE
Take note of the measures listed below to rectify malfunctions.
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.

Safety Information
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
Type 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

- 10 - Schenck Process Group
Database
► 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.
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

Schenck Process Group - 11 -
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).

Database
3.1.5 Highest Priority Event

The information 'highest priority event' is transferred bit-coded in Status 52+53 in the first two bytes
(status 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
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

Database
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.
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'.

Database
3.1.6 Illustration of the Telegram Bytes on Command

e.g. DISOCONT Tersus

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)'.

Database
3.2.1 Simplified Payload Structure

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 :
*)
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!

Database
3.2.1.2 Payload Scope and Content FIXED 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 message and its content can
be adjusted.
A) Selecting a FIXED format
(Condition: Parameter Protocol Type = PROFIBUS DP or PROFINET IO or DeviceNet or EtherNet/IP)
The quantity of the payload to be transmitted can be set using the 'Communication Fieldbus' parameter in
the 'Configuration' block:
The following FIXED formats are available
Format Number of preset values Number of read values
FIXED_8_16 8 16
FIXED_8_8 8 8
FIXED_4_4 4 4
FIXED COMPATIBLE *) 8 16
Tab. 1 : FIXED formats
*) This format is compatible with an earlier DISOCONT model, i.e. any DISOCONT Tersus connected will
behave as a DISOCONT towards the master.
The size of the payload structure can be read directly from the format identifier, e. g.:
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 mes-
sage positions from the 'Fixed mode configuration' block.

Database
The assignment of the individual positions applies to all FIXED formats.

The format FIXED_8_16 transmits the largest possible quantity of data (see image), the other formats trans-
mit less. FIXED_8_8 transmits the preset values 1-8 and the read values 1-8; FIXED_4_4 transmits the pre-
set 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.

Database
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):
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.

Database
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
Assumptions:
Scales type: VLW 20170
Floating point numbers: FLOAT-Format = IEEE
Structure of payload: Configuration = FIXED_8_16
Word and byte sequence: Word Sequence = I:std/L:std

(i.e. 'Big Endian') Byte Sequence = High - Low
Message contents: as per the setting in block Fixed mode configuration

Master → Slave: 32 bytes
Master ← Slave: 64 bytes
***)
Master → Slave Bytes Meaning ID Command or
(hex) (dec/hex) preset value
*)
Byte 1-4 00 0C 00 00 Command 04+05 320 / 0x0140 'Clear Events' and
'Release'
*)
Bytes 5-8 00 00 00 00 Command 06+07 352 / 0x0160 (No command active)

Database
***)
Master → Slave Bytes Meaning ID Command or
(hex) (dec/hex) preset value
*)
Bytes 9-12 00 00 00 01 Command 08+09 384 / 0x0180 'Start Keyboard Mode'
Bytes 13-16 42 C8 00 00 Serial Setpoint 592 / 0x0250 100 kg/h
Bytes 17-20 43 C8 00 00 Serial Batch Setpoint 594 / 0x0252 400 kg
**)
Bytes 21-24 00 01 00 00 Command 00+01 256 / 0x0100 1 'Select MDP Set'
(= No. 1)
Bytes 25-28
Bytes 29-32
*) bit-coded
**) coded as a number
***) but ID will not be transmitted
***)
Master ← Slave Bytes Meaning ID Status or
(hex) (dec/hex) current value
*)
Byte 1-4 00 22 00 00 Status 02+03 752 / 0x02F0 'No Release' and
'Summary Alarm'
*)
Bytes 5-8 00 00 00 00 Status 04+05 784 / 0x0310 (No bit set)
*)
Bytes 9-12 13 18 00 00 Status 52+53 1552 / 0x0610 Acknowledged event:
(Highest priority event) SY09, W2
Bytes 13-16 44 9A 40 00 Feedrate 1872 / 0x0750 1234 kg/h
Bytes 17-20 42 83 66 66 Totalizer 1 1874 / 0x0752 65.7 kg
Bytes 21-24 43 AC 80 00 Fill Weight 1888 / 0x0760 345.0 kg
Bytes 25-28 42 C8 00 00 BIN: Fill Weight 1890 / 0x0762 100 kg
Bytes 29-32 42 C8 00 00 Setpoint 1894 / 0x0766 100 kg/h
*)
Bytes 33-36 00 00 00 00 Status 06+07 816 / 0x0330 (No bit set)
Bytes 37-40 41 D8 00 00 Totalizer 2 1876 / 0x0754 27 kg
Bytes 41-44 41 B0 00 00 Speed 1886 / 0x075E 22 1/min
Bytes 45-48 00 00 00 00 Controller Magnitude 1960 / 0x07A8 0 mA
Bytes 49-52 40 23 D7 0A Batch Actual Value 1896 / 0x0768 2.56 kg
Bytes 53-56 42 C2 E1 48 Batch Resid. Amount 1898 / 0x076A 97.44 kg
)
Bytes 57-60 00 00 02 00 Status 56+57 ** 1616 / 0x0650 'Activated Material' = 2
Bytes 61-64 3F 00 00 00 Deviation 1904 / 0x0770 0.5 %
*) bit-coded
**) coded as a number
***) but ID will not be 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 Scope and Content VARIABLE Mode

(you will have to use the list Available Data - List if you are not using EasyServe.)
You can set both the size of the payload message and its contents.
Selecting a VARIABLE format (PPO type)
Condition: Parameter Protocol Type = PROFIBUS DP or PROFINET IO or DeviceNet 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:
The size of the payload structure can be calculated directly from the format identifier:
TIP
The values Status (0x02F0) and Actual Value (0x0750) are fixed coded in
the telegram in VARIABLE mode 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 message length in bytes.

Database
The following VARIABLE formats are available:
Format Parameter range Process data range

(PPO type) (PKW) (PZD)
Preset values Read IDs

(Order list)
NO_PARA_ID_3_6 *) without 3 6
NO_PARA_ID_4_12 *) without 4 12
PARA_ID_6_15 *) with 6 15
VARIABLE COMPATIBLE **) without | with 2…4 0 … 12
Tab. 2 : VARIABLE formats
*) These formats are semi-variable, i.e. the payload structure is fixed, but the data content (IDs and val-
ues) are variable.
**) This format is compatible with an earlier DISOCONT model, i.e. any DISOCONT Tersus connected will
behave as a DISOCONT towards the master (refer also to the STEP7/CFC modules). Payload struc-
ture and data content (IDs and values) are variable within specific limits and can be set
ing Configuration, Preset Count and READ_ID Count:
TIP
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).
Consequences

Database
3.2.2.3 Telegram Structure (Variable payload)

The following figures show the basic structure of the payload in the DISOCONT Tersus system. The first line
represents the message from the master to the weighing electronics, the second line is the response of the
weighing 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 (small):

Parameter 'Configuration' = 'NO_PARA_ID_3_6'
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 no parameter range (large):

Parameter 'Configuration' = 'NO_PARA_ID_4_12'

Database
NO_PARA - No PKW 0
NO_PARA - No PKW 0
Semi-variable PPO type with parameter range (PKW):

Parameter 'Configuration' = 'PARA_ID_6_15'
PARA Parameter range PKW [8] 8

PARA Parameter range PKW [8] 8


Database
Fully Variable PPO Type (parameter controlled):

Parameter 'Configuration' = 'VARIABLE COMPATIBLE'
Par: Item Comment Bytes
'Parameter' NO No PKW 0
YES with PKW 8
'Preset Count' 2…4 Preset[6] = preset ID [2] + preset value [4]
2 12
3 18
4 24
'READ_ID Count' 0 …12 Read ID[2]
0 0
⋮ ⋮
12 24
Master → Slave 12 ≤ Σ ≤ 56
Par: Item Comment Bytes
'Parameter' NO No PKW 0
YES with PKW 8
'READ_ID Count' 0 …12 Read value[4]
0 0
⋮ ⋮
12 48
Master ← Slave 8 ≤ Σ ≤ 64
Shortest possible message: P(NO,2,0) Longest possible message:

P(YES,4,12)
Number of bytes:
Master → Slave 12 56
Master ← Slave 8 64

Database
Depending on the parameters set, the fieldbus message therefore can be expanded gradually by as many
IDs as required by the current application.
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.
▪ 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
0x09FC hex (2556 dez ). 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.
▪ Parameter transmission (PKW range): IDs from chapter »Material-Dependent Parameters (MDP) [➙
105]« only should be used in the message from the master to the scales electronics. The parameter
IDs already have been assigned the Task Identifiers (TIDs) and are in both decimal and hex format.
The parameters chosen are sufficient to operate a VLW with different materials.

Database
Example 1: Data transmission without parameters and without user-defined read IDs (order list)
(The preset value IDs used are intended as examples only)
This message is the smallest payload message possible.
In addition, the 'DISOCONT Compatible' format must be used and the related parameters set corresponding-
ly:
'Configuration' : VARIABLE COMPATIBLE
'Parameter' : NO
'Preset Count' :2
'READ_ID Count' :0
Example values for (control) commands (hex):
00 01 00 00 Scales start command
00 02 00 00 Scales stop command
00 04 00 00 Acknowledge events
Example 2: Data transmission without parameters and with 6 user-defined read IDs (order list)
(The preset value IDs used are intended as examples only)
This message is the smallest payload message in the 'Variable DISOCONT Tersus Mode'
possible.
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 16' in these settings determine which values are returned:
Fig. 1: Automatic order list
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
NO_PARA_ID_4_12 *) 12
PARA_ID_6_15 *) 15
VARIABLE COMPATIBLE **) 0 … 12
Tab. 3 : VARIABLE formats
*) The last value determines the quantity of read values.

**) The content of the parameter 'READ_ID Count' determines the quantity.
The values 'Status' (0x02F0) and 'Actual Value' (0x0750) have a set coding in the message
and are always returned regardless of the 'order list'.

Database
3.2.2.4 Parameter Transmission

The use of parameter IDs is described in the chapter »General Information [➙9]«. A list of the material-
dependent parameters (MDP) for scales type VLW can be found in chapter »Available Data - Listing [➙50]«.
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 2 7
value (DDW)

Database
Task identifier (AK) Meaning Answer
3 011 Alter parameter value (DDW) 2 7

4 100 Request specifier (DDW) 2 7
Tab. 4 : 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. 5 : 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. 6 : 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.

Database
▪ Bit 15 ... 0:
Parameter value for a 16-Bit parameter or Low component for a 32-Bit parameter
▪ 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. 7 : error codes
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_4_12

Example for PROFIBUS DP using the variable DISOCONT Tersus format 'NO_PARA_ID_4_12'.
Floating point format = IEEE
Example for a process image master → slave (48 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'
value 3
Bytes 15-18 00 02 00 00 Control value for 'Select MDP Set' = 2
Bytes 19+20 02 52 ID=0252 for 'Serial Batch Setpoint' Preset
value 4
Bytes 21-24 42 C8 00 00 100 as setpoint [kg/h]
Order list:

Database
Bytes 25+26 07 52 ID = 0752 for requesting measured value 'Totalizer 1' [kg] ID01
Bytes 27+28 07 5E ID = 075E for requesting measured value 'Speed' [1/min] ID02
Bytes 29+30 07 68 ID = 0768 for requesting measured value 'Batch Actual Value' [kg] ID03
Bytes 31+32 07 6A ID = 076A for requesting measured value 'Batch Resid. Amount' ID04
[kg]
Bytes 33+34 07 60 ID = 0760 for requesting measured value 'Fill Weight' [kg] ID05
Bytes 35+36 06 50 ID=0650 for 'Status 56+57' for requesting the value 'Activated ID06
Material' = current MDP-Index
Bytes 37+38 06 10 ID=0610 for 'Status 52+53' for requesting the highest priority error ID07
Bytes 39+40 03 10 ID=0310 for 'Status 04+05' ID08
Bytes 41+42 03 30 ID=0330 for 'Status 06+07' ID09
Bytes 43+44 00 00 ID = 0000 (reserve) ID10
Example for a process image slave → master (56 Bytes):

*)
Byte 01-0 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 25 + 26, so 'Totalizer 1' [kg] = [ID01]
1234.56
Bytes 13-16 00 00 00 00 Value corresponding to ID in bytes 27 + 28, so 'Speed' [ID02]
Bytes 17-20 42 B3 99 9A Value corresponding to ID in bytes 29 + 30, so 'Batch Actual Val- [ID03]
ue' [kg] = 89.8
Bytes 21-24 41 23 D7 0A Value corresponding to ID in bytes 31 + 32, so 'Batch Resid. [ID04]
Amount' [kg] = 10.24
Bytes 25-28 43 16 80 00 Value corresponding to ID in bytes 33 + 34, so 'Fill Weight' [kg] = [ID05]
150.5
Bytes 29-32 00 00 02 00 Value corresponding to ID in bytes 35+36, so 'Activated Material' [ID06]
=2
Bytes 33-36 01 17 03 15 Value corresponding to ID in bytes 37 + 38, also highest priority [ID07]
error (here: A, SY08, acknowledged)
Bytes 37-40 00 00 00 00 Value corresponding to ID in bytes 39 + 40, so 'Status 04+05' [ID08]
Bytes 41-44 00 00 10 00 Value corresponding to ID in bytes 41 + 42, so 'Status 06+07' [ID09]
Bytes 45-48 00 00 00 00 Value corresponding to ID in bytes 43 + 44 (reserve) [ID10]

Database
*)
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 VARIABLE COMPATIBLE Format without PKW (1)

Example for PROFIBUS DP using the variable DISOCONT-compatible format 'VARIABLE COMPATIBLE'.
Configuration module 'PPO2: 0 PKW, 2 Set, 4 PZD'
Floating point format = SIEMENS-KG
DISOCONT Tersus parameters to be set:
'Parameter' : NO
'Preset Count' :2
*)
'READ_ID Count' :2
*) not 4, because status and actual value are always returned. This must be taken into account when con-
sidering the quantity of read IDs.
Bytes 01+02 02 50 ID=0250 for 'Serial Setpoint' Preset

value 1
Bytes 03-06 0A 7D 00 1000.0 as setpoint [kg/h]
00
value 2
Bytes 09-12 00 01 00 Control value for 'Scales Start Feeder'
00
Order list:
Bytes 13+14 07 52 ID = 0752 for requesting measured value 'Totalizer 1' [kg] ID01
Bytes 15+16 07 5C ID = 075C for requesting measured value 'Belt Speed' [m/s] ID02

*)
Bytes 01-04 01 02 00 Message from 'Status 02+03' = [ID=02F0]
00
**)
Bytes 05-08 43 16 80 Measured value 'Feedrate' [kg/h] = [ID=0750] = 150.5
00
Order list:
Bytes 09-12 07 59 CC Value corresponding to ID in bytes 13+14, so 'Totalizer 1' [kg] = [ID01]
CD 89.8
Bytes 13-16 3F 00 00 Value corresponding to ID in bytes 15 + 16, so 'Belt Speed' [m/s] = [ID02]
00 0.5
*)
'Normal Mode' and 'No Release'.

Database
3.2.2.5.3 VARIABLE COMPATIBLE Format without PKW (2)
Configuration module 'PPO6: 0 PKW, 4 Set, 8 PZD'

DISOCONT Tersus parameters to be set:
'Parameter' : NO
'Preset Count' :4
*)
'READ_ID Count' :6
Bytes 02 50 ID=0250 for 'Serial Setpoint' Preset

01+02 value 1
Bytes 03- 44 7A 00 00 1000.0 as setpoint [kg/h]
06
Bytes 01 40 ID=0140 for 'Command 04+05' Preset
07+08 value 2
Bytes 09- 00 41 00 00 Control value for 'Scales Start Feeder' and 'Reset Totalizer 1'
12
Bytes 01 00 ID=0100 for 'Command 00+01' Preset
13+14 value 3
Bytes 15- 00 02 00 00 Control value for 'Select MDP Set' = 2
18
Bytes 02 52 ID=0252 for 'Serial Batch Setpoint' Preset
19+20 value 4
Bytes 21- 42 C8 00 00 100 as setpoint [kg/h]
24
Order list:
Bytes 07 52 ID = 0752 for requesting measured value 'Totalizer 1' [kg] ID01
25+26
Bytes 07 5E ID = 075E for requesting measured value 'Speed' [1/min] ID02
27+28
Bytes 07 68 ID = 0768 for requesting measured value 'Batch Actual Value' [kg] ID03
29+30
Bytes 07 6A ID = 076A for requesting measured value 'Batch Resid. Amount' ID04
31+32 [kg]
Bytes 07 60 ID = 0760 for requesting measured value 'Fill Weight' [kg] ID05
33+34

Database
Bytes 06 50 ID=0650 for 'Status 56+57' for requesting the value 'Activated ID06
35+36 Material' = current MDP-Index

*)
Bytes 01- 01 1D 00 00 Message from 'Status 02+03' = [ID=02F0]
04
**)
Bytes 05- 00 00 00 00 Measured value 'Feedrate' [kg/h] = [ID=0750]
08
Order list:
Bytes 09- 42 B3 99 9A Value corresponding to ID in bytes 25 + 26, so 'Totalizer 1' [kg] = [ID01]
12 89.8
Bytes 13- 00 00 00 00 Value corresponding to ID in bytes 27 + 28, so 'Speed' [ID02]
16
Bytes 17- 42 B3 99 94 Value corresponding to ID in bytes 29 + 30, so 'Batch Actual Val- [ID03]
20 ue' [kg] = 89.8
Bytes 21- 41 23 D7 0A Value corresponding to ID in bytes 31 + 32, so 'Batch Resid. [ID04]
24 Amount' [kg] = 10.24
Bytes 25- 43 16 80 00 Value corresponding to ID in bytes 33 + 34, so 'Fill Weight' [kg] = [ID05]
28 150.5
Bytes 29- 00 00 02 00 Value corresponding to ID in bytes 35+36, so 'Activated Material' [ID06]
32 =2
*)
'Normal Mode', 'Selected Language OK', 'Volumetric Mode', 'Counter active' and 'Feeder On'.
3.2.2.5.4 VARIABLE COMPATIBLE Format with PKW (Alter Parameter)

Configuration module 'PPO_P0: 4 PKW, 2 Set, 2 PZD' (with 'change parameter')
Task: Set parameter (e.g. VLW) P06.10 'Threshold filling start' to value '15 %'.
A) DISOCONT Tersus parameters to be set
'Parameter' : YES
'Preset Count' :2
*)
'READ_ID Count' :0
B) Determining parameter range (PKW)
1. Parameter ID (PKE)
The parameter has the ID '4613/0x1205' and its value is to be changed.

Database
AK=3 and PNU=0x1205.

This must be coded as follows:
PKE
AK PNU
Bit no. 15 14 13 12 … 0
AK 0 1 1 Task identifier = 3 (→ change parameter)
↓ ↓ ↓
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'.

2. Parameter index (IND)
Subindex = 0 → The current value of the parameter will be read.
This results in the content '00 00' for IND.
3. Parameter value (PWE)
The decimal number 15 must be converted to IEEE format.
This results in the content '41 70 00 00' for PWE.
C) Example of process images
Master → Slave (20 bytes):
Bytes 01-02 72 05 TID = 3 and ID = 0x1205 (from 1st) → change PKE PKW
Bytes 03-04 00 00 Subindex = 0 (from 2nd) IND
Bytes 05-08 41 70 00 00 Value = 15 (from 3rd) PWE
Bytes 09+10 02 50 ID=0x0250 for 'Serial Setpoint' ID Preset
*)
value 1
Bytes 11-14 44 7A 00 00 1000.0 as setpoint [kg/h] Value
Bytes 15+16 01 40 ID=0x0140 for 'Command 04+05' ID Preset
*)
value 2
Bytes 17-20 00 01 00 00 Control value for 'Scales Start Feeder' Value
*)
Preset value 1 and Preset value 2 are always sent, but the ID can vary.
Slave → Master (16 bytes):
Bytes 01-02 52 05 RID and ID = 0x1205 PKE PKW

Bytes 03-04 00 00 Subindex = 0 IND
Bytes 05-08 41 70 00 00 Value = 15 PWE
*)
Bytes 09-12 01 02 00 00 Message from 'Status 02+03' = [ID=02F0] Value Status
Bytes 13-16 00 00 00 00 Measured value 'Feedrate' [kg/h] = [ID=0750] Value Actual
**)
value

Database
*)
**)
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
AK PNU
Bit no. 15 14 13 12 … 0
AK 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.
3.2.2.5.5 VARIABLE COMPATIBLE Format with PKW ('Change Parameter' with Error Re-
ply)
Configuration module 'PPO_P0: 4 PKW, 2 Set, 2 PZD' (with 'change parameter' and error reply)
Task: Set parameter (e.g. VLW) P06.10 'Threshold filling start' to '1000 %' (→ provoke error).
'Parameter' : YES
'Preset Count' :2
*)
'READ_ID Count' :0

Database

1st Parameter Identifier (PKE)
The parameter has the ID '4613/0x1205' and its value is to be changed.
TID=3 and PNU=0x1205.
They must be encoded as follows:
PKE
AK PNU
Bit no. 15 14 13 12 … 0
↓ ↓ ↓
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

3rd Parameter Value (PWE)
The decimal number 1000 must be converted into IEEE format.
This results in a content for PWE of '44 7A 00 00'.

Database

Byte 01-04 72 05 00 00 ID=0x1205 change (from a.) PKW

byte 05-08 44 7A 00 00 to value = 1000 (from b.)
Bytes 09+10 02 50 ID=0x0250 for 'Serial Setpoint' Preset
value 1
Bytes 15+16 01 40 ID=0x0140 for 'Command 04+05' Preset
value 2
Bytes 17-20 00 01 00 00 Control value for 'Scales Start Feeder'
Byte 01-04 F2 05 00 00 The task could not be carried out PKW

byte 05-08 41 70 00 01 Previous value will be returned; Error number = 1
*)
Bytes 09-12 01 02 00 00 Message from 'Status 02+03' = [ID=02F0]
**)
*)
The byte sequence in PKE = 'F2 05'.
PKE
AK PNU
Bit no. 15 14 13 12 … 0
AK 1 1 1 Reply Identifier = 7 (→ task cannot be executed → error number in
PWE2)
↑ ↑ ↑
Par. ID 0 0 0 1 0 0 1 0 0 0 0 0 0 1 0 1
(hex) 1 2 0 5
PKE 1 1 1 1 0 0 1 0 0 0 0 0 0 1 0 1
(hex) F 2 0 5
Result: Reply Identifier = 7 → parameter could not be changed.

Reason? → Evaluation of the error number from PWE → PWE2:
[PWE2] = '00 01' → 'Min/Max limit exceeded'

Database
3.2.2.5.6 VARIABLE COMPATIBLE Format with PKW ('Change Parameter' - Text Parameter
Type)
Configuration module 'PPO_P0: 4 PKW, 2 Set, 2 PZD' (with change parameter)

Special case: Change text parameter, e.g. floating point format = IEEE → SIEMENS-KG
Task: Set parameter (e.g. VLW) P21.16 'FLOAT-Format' to value 'SIEMENS-KG'
'Parameter' YES
'Preset Count' :2
*)
'READ_ID Count' :0
The parameter has the ID '4540/0x11BC' and the parameter is to be changed.
TID/RID=3 and PNU=0x11BC.
PKE
AK PNU
Bit no. 15 14 13 12 … 0
↓ ↓ ↓
Par. ID 0 0 0 1 0 0 0 1 1 0 1 1 1 1 0 0
(hex) 1 1 B C
PKE 0 1 1 1 0 0 0 1 1 0 1 1 1 0 0 0
(hex) 7 1 B C
This results in a content for PKE of '71 BC'.

The domain of a 'text' type parameter (code letter 'T' in the EasyServe parameter printout) consists always of
a number of list elements. To change a parameter of this type the required element must be selected from
the corresponding list. This is done via fieldbus by sending the ID assigned to that element (refer to the ID
list of all parameters in the appendices).
The IDs of the list for the possible FLOAT formats are:
3608/0x0E18 = SIEMENS-KG

Database
3609/0x0E19 = IEEE
A parameter value is always transmitted as a double word (32 bits); however, here an ID that is 'only' a 16 bit
value is to be transmitted as the parameter value. A parameter value such as this is transmitted in PWE2;
PWE1 must in this case be set to '0'.
This results in a content for PWE of '00 00 0E 18'.
Byte 01-04 71 BC 00 00 ID=0x11BC change (from a. PKW

byte 05-08 00 00 0E 18 )to value = 'SIEMENS-KG' (from b.)
value 1
value 2
Byte 01-04 51 BC 00 00 The preset parameter value has been accepted. PKW
byte 05-08 00 00 0E 18 The new value will be returned
*)
**)
*)
The byte sequence in PKE = '51 BC'.
PKE
AK PNU
Bit no. 15 14 13 12 … 0
AK 0 1 0 Reply Identifier = 2 (→ change accepted)
↑ ↑ ↑
Par. ID 0 0 0 1 0 0 0 1 1 0 1 1 1 1 0 0
(hex) 1 1 B C
PKE 0 1 0 1 0 0 0 1 1 0 1 1 1 1 0 0
(hex) 5 1 B C
Result: Reply Identifier = 2 → parameter has been successfully changed.

Database
3.2.2.5.7 VARIABLE COMPATIBLE Format with PKW (Read Parameter)
Configuration module 'PPO_P0: 4 PKW, 2 Set, 2 PZD' (with 'read parameter')

DISOCONT parameter with parameter block, 0 IDs, 2 preset IDs
Task: Read parameter (e.g. VLW) P06.10 'Threshold filling start'.
'Parameter' : YES
'Preset Count' :2
*)
'READ_ID Count' :0
The parameter has the ID '4613/0x1205' and the parameter is to be read.
TID/RID =1 and PNU=0x1205.
PKE
AK PNU
Bit no. 15 14 13 12 … 0
AK 0 0 1 Task identifier = 1 (→ read parameter)
↓ ↓ ↓
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 0 1 1 0 0 1 0 0 0 0 0 0 1 0 1
(hex) 3 2 0 5

This value is not relevant for reading operations and can by arbitrary. This results in a byte sequence for
PKE of 'xx xx xx xx', where xx = arbitrary.

Database

Byte 01-04 32 05 00 00 (PKE, IND) ID=0x1205 read (from a.) PKW

byte 05-08 xx xx xx xx (PWE1, PWE2) (from b.)
value 1
value 2
Byte 01-04 52 05 00 00 (PKE, IND) PKW

byte 05-08 41 70 00 00 (PWE1, PWE2)
*)
**)
*)
The byte sequence in PKE = '52 05'.
PKE
AK PNU
Bit no. 15 14 13 12 … 0
AK 0 1 0 Reply Identifier = 2 (→ current parameter value was transmitted)
↑ ↑ ↑
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 read, what are its contents?
→ Determining the parameter value (PWE)
PWE supplies the byte sequence '41 70 00 00'. After conversion, this results in the decimal number 15.
The parameter has the current value = 15 %.

Database
3.3 Available Data - Listing

3.3.1 Cyclical and Acyclical Data Exchanges
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 Preset Values
3.3.1.1.1 Write commands
ID (identifier) Value Mode Software
hex dec Commands VLW VWF VBW VMC VSF VIF VBC
Command 0 (coded as number)

0100 00256 Select MDP Set *
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 - Feeder Start (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 - Moisture Active (D) * * * * *
014a 00330 A - Moisture OFF (D) * * * * *
014b 00331 B - Stop Wheel (D) * *
014c 00332 C - PLS Gate Feedback (S) *

Database
014d 00333 D - Open Gate (D) * *

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-
0154 00340 4-
0155 00341 5 - Emergency Setpoint ON (D) * * * * *

0156 00342 6 - Emergency Setpoint OFF (D) * * * * *
0157 00343 7 - Start measuring 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 - Start Zero Check (D) * * * * *

0161 00353 1 - Start Span Check (D) * * * * *
0162 00354 2 - Accept Correction (D) * * * * *
0163 00355 3 - Check Measurement (D) * * * * *
CANCELLED
0164 00356 4 - Source Check Enable (S) * * * * *
0165 00357 5 - Ext. Cor. Tare acqu. (D) * * * * *
0166 00358 6 - Ext.Cor. Range acqu. (D) * * * * *
0167 00359 7 - Start External Check (D) * * * * *
0168 00360 8 - Automatic Bin Control (D) * * * * * *

0169 00361 9 - Manual Bin Control (D) * * * * * *

Database
016a 00362 A - Bin Controller Manual Start (D) * * * * * *

016b 00363 B - Bin Controller Manual Stop (D) * * * * * *
016c 00364 C - CO: BIN Controller Optimization (D) * * * * *
016d 00365 D - Print Check Result (D) * *
016e 00366 E - Time Elements Preassign (D) * * * * *
016f 00367 F - Initialise Time Elements (D) * * * * *
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 - CV: 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 - TB: Tare (D) * * * * * *
017f 00383 F - CB: Weight Check (D) * * * * * *
0180 00384 0 - DO: PLC 1 (S) * * * * * * *

0181 00385 1 - DO: PLC 2 (S) * * * * * * *
0182 00386 2 - DO: PLC 3 (S) * * * * * * *
0183 00387 3 - DO: PLC 4 (S) * * * * * * *
0184 00388 4 - DO: PLC 5 (S) * * * * * * *
0185 00389 5 - DO: PLC 6 (S) * * * * * * *
0186 00390 6 - DO: PLC 7 (S) * * * * * * *
0187 00391 7 - DO: PLC 8 (S) * * * * * * *

Database
0188 00392 8 - Batch Record (D) * * * * * *

0189 00393 9-
018a 00394 A - Totalizer Record (D) * * * * * * *

018b 00395 B-
018c 00396 C-
018d 00397 D-
018e 00398 E - Log-on EasyServe (D)
018f 00399 F - Disconnect EasyServe (not FB) (D)
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 - CFC: Init Check (D) *

0196 00406 6 - Manual Gate Control (D) * *
0197 00407 7 - Automatic Gate Control (D) * *
0198 00408 8 - Dead Time P active (D) * * * *

0199 00409 9 - Dead Time P not act. (D) * * * *
019a 00410 A - Dead Time P Clock ON (D) * * * *
019b 00411 B - Dead Time P Clock OFF (D) * * * *
019c 00412 C - Dead Time ON/OFF active (D) * * * * *
019d 00413 D - Dead Time ON/OFF deactivated (D) * * * * *
019e 00414 E - Dead Time I/O Clock ON (D) * * * * *
019f 00415 F - Dead Time I/O Clock OFF (D) * * * * *
01a0 00416 0-
01a1 00417 1-
01a2 00418 2-
01a3 00419 3-
01a4 00420 4-
01a5 00421 5-
01a6 00422 6-

Database
01a7 00423 7-
01a8 00424 8-
01a9 00425 9-
01aa 00426 A - Reset batch total (D) *

01ab 00427 B - Feeder Stopped (S) * * *
01ac 00428 C - Start Feeder (stat.) (S) * * * * * * *
01ad 00429 D-
01ae 00430 E-
01af 00431 F-
Command 11 LO (coded as num-

ber)
01b0 00432 Ingredient No. *
01b8 00440 8-
01b9 00441 9-
01ba 00442 A-
01bb 00443 B-
01bc 00444 C - Capacity Rate (D) *

01bd 00445 D - Copy MDP Block (D) *
01be 00446 E – CP: Feeder Capacity Adaption (D) *
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-

Database
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-
01cf 00463 F-
01d0 00464 0-
01d1 00465 1-
01d2 00466 2 - TD: Control speed adaption (D) *

01d3 00467 3 - Bin Weigher Adaption (D) *
01d4 00468 4 - TSBW: Tare (D) *
01d5 00469 5 - CSBW: Weight Check (D) *
01d6 00470 6-
01d7 00471 7 - Enable Local Mode (S) * * * * * *

01d8 00472 8-
01d9 00473 9-
01da 00474 A - IDMS Start (D) *

01db 00475 B - IDMS Run Reverse *
01dc 00476 C - IDMS Stop (D) *
01dd 00477 D-
01de 00478 E-
01df 00479 F-
01e0 00480 0-
01e1 00481 1 - Apply density (D) *

01e2 00482 2 - OS: Offset of control magnitude (D)
01e3 00483 3 - BC: Capacity Adaption Feed (D)

Hopper
01e4 00484 4 - Refill Preparation finished (D)
01e5 00485 5-
01e6 00486 6-
01e7 00487 7-

Database
01e8 00488 8-
01e9 00489 9-
01ea 00490 A-
01eb 00491 B-
01ec 00492 C-
01ed 00493 D-
01ee 00494 E-
01ef 00495 F-
Tab. 8 : Fieldbus commands
3.3.1.1.2 Write process values (IEEE format)
ID (identifier) Software
hex dec Default Value Dimension VLW VWF VBW VMC VSF VIF VBC
0250 00592 Serial Setpoint kg/h * * * * *

0252 00594 Serial Batch Setpoint kg * * * * * *
0254 00596
0256 00598 Batch No. *
0258 00600 AO: PLC 1 mA * * * * * * *
025a 00602 AO: PLC 2 mA * * * * * * *
025c 00604 Span Correction Value * * * * *
025e 00606 Zero Correction Value kg/h * * * * *
0260 00608 Difference Flow Rate kg/h * * * *
0262 00610 BIN: Fill Weight kg * * * * * *
0264 00612
0266 00614 BIN: Setpoint kg * * *
0268 00616 MDP block source *
026a 00618 MDP block destination *

026c 00620 QA Serial Setpoint kg/m *
026e 00622
0270 00624
0272 00626 Belt Load 2nd Bridge kg/m *
0274 00628 Weight on 1st LC kg/m * * *
0276 00630 Weight on 2nd LC kg/m *

0278 00632
027a 00634
027c 00636

Database
hex dec Default Value Dimension VLW VWF VBW VMC VSF VIF VBC
027e 00638
Tab. 9 : Fieldbus preset values
3.3.1.2 Read values
3.3.1.2.1 Read status
ID (identifier) Event Software
hex dec Status Group/Class VLW VWF VBW VMC VSF VIF VBC
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 - Local Mode * * * * * * *
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 * * * * * *

Database
0302 00770 2 - Batch Dribble Feed * * * * * *

0303 00771 3-
0304 00772 4 - English units active * * * * * * *

0305 00773 5 - Dead Time active * * * * *
0306 00774 6 - Dead Time Setpoint active * * * *
0307 00775 7 - Dead Time ON/OFF active * * * * *
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 - CV: 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 - Bin Weigher Active * * * * * *

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 - Bin Level MAX * * * * * *
031f 00799 F - Bin Level MIN * * * * * *

Database
0320 00800 0 - Bin Controller ON * * * * *

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 - Expect Acceptance * * * * *
0328 00808 8 - On Stream Calibration * * * * *

0329 00809 9 - Relative Zero Correction Error * * * * *
032a 00810 A - Absolute Zero Correction Error * * * * *
032b 00811 B - Relative Span Correction Error * * * * *
032c 00812 C - Absolute Span Correction Error * * * * *
032d 00813 D - No Check Release * * * * *
032e 00814 E - Prepare Check Measurement * * * * *
032f 00815 F - Check Measurement Active * * * * *
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 - TB: Tare * * * * * *
033c 00828 C - CB: Weight Check * * * * * *
033d 00829 D - CO: BIN Controller Optimization * * * * *
033e 00830 E - 2nd Bridge MAX *

Database
033f 00831 F - 2nd Bridge MIN *

0340 00832 0 - Emergency Setpoint active * * * * *

0341 00833 1-
0342 00834 2-
0343 00835 3-
0344 00836 4 - TSBW: Tare *

0345 00837 5 - CSBW: Weight Check *
0346 00838 6-
0347 00839 7-
0348 00840 8 - Moisture Active * * * * *

0349 00841 9 - Moisture MAX * * * * *
034a 00842 A - Moisture Error * * * * *
034b 00843 B - Belt Load Controller *
034c 00844 C - EasyServe active * * * * * * *
034d 00845 D - EasyServe Logged-in * * * * * * *
034e 00846 E-
034f 00847 F-
0350 00848 0 - Capacity Rate *

0351 00849 1 - DO: Pre-cut-off * *
0352 00850 2-
0353 00851 3-
0354 00852 4 - Bin 2 Filling *

0355 00853 5-
0356 00854 6 - Second Bin Weigher Active *

0357 00855 7 - Bin Filling * * * * *
0358 00856 8 - DO: Control Started * * *

0359 00857 9 - No Summary Alarm * * * * * * *
035a 00858 A - No Summary Warning * * * * * * *
035b 00859 B - Totalizer 1 Output * * * *
035c 00860 C - No Deviation * * *

Database
035d 00861 D - Ready for Start * * * * * *

035e 00862 E - No Relative Zero Correction Error * * *
035f 00863 F - No Absolute Zero Correction * * *
Error
0360 00864 0 - No Relative Span Correction * * * * *

Error
0361 00865 1 - No Absolute Span Correction * * * * *
Error
0362 00866 2 - Bin Weigher Adaption *
0363 00867 3-
0364 00868 4 - CP: Feeder Capacity Adaption *

0365 00869 5 - DI: BIC freeze * *
0366 00870 6 - TD: Control speed adaption *
0367 00871 7-
0368 00872 8-
0369 00873 9-
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 - Event: Communication SY02 (W2) * * * * * *
VCU20100-Unit 2
VCU20100-Unit 3
0373 00883 3 - Event: Communication HMI 1 SY04 (W2) * * * * * * *
0376 00886 6 - Event: Communication VHM SY07 (W2) * * * * * * *
serial
0377 00887 7 - Event: Cyclic Communication SY08 (W2) * * * * * * *

Database
0378 00888 8 - Event: License Violation
0379 00889 9 - Event: Acyclic Communication SY10 (W2) * * * * * * *

037a 00890 A-
037b 00891 B-
037c 00892 C - Event: Bluetooth channel broken SY13 (W2) *

037d 00893 D-
037e 00894 E - Event: Communication SY15 (W2) * * * * * *

VMO20100-Unit 1
037f 00895 F - Event: Communication SY16 (W2) * * * * * *
VMO20100-Unit 2
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 - Event: External Event 3 SC11 (W2) * * * * * * *
038b 00907 B - Event: External Event 4 SC12 (W2) * * * * * * *
038c 00908 C - Event: Discharge Gate SC13 (W2) * *
038d 00909 D - Event: Gate OPEN Time > MAX SC14 (W2) *
038e 00910 E - Event: Batching Time > MAX SC15 (W2) *
038f 00911 F - Event: Wrong Rotation Direction SC16 (W2) *
0390 00912 0 - Event: Power Failure WE01 (W2) * * * * * * *

0391 00913 1 - Event: NAMUR Error VCU1-DI6 WE02 (W2) * * * * * * *
0393 00915 3 - Event: NAMUR Error VCU2-DI6 WE04 (W2) * * * * * *

Database

0397 00919 7 - Event: Analog Input < Offset WE08 (W2) * * * * * *
0398 00920 8-
0399 00921 9-
039a 00922 A-
039b 00923 B-
039c 00924 C - Event: NAMUR Error VMO1-DI7 WE13 (W2) * * * *

039d 00925 D - Event: NAMUR Error VMO2-DI7 WE14 (W2) * * * *
039e 00926 E-
039f 00927 F-
03a0 00928 0 - Event: Limit Switch WM01 (W2) * *

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 - Event: Slip 2 WM05 (W2) * *
03a5 00933 5 - Event: Chain Motion Monitor WM06 (W2) *
03a6 00934 6-
03a7 00935 7-
03a8 00936 8 - Event: Motor Start WM09 (W2) *

03a9 00937 9-
03aa 00938 A-
03ab 00939 B-
03ac 00940 C - Event: Agitator Overload WM13 (W2) *

03ad 00941 D - Event: Feed Air MAX WM14 (W2) *
03ae 00942 E - Event: Motor blocked WM15 (W2) *
03af 00943 F - Event: Motor Protection Switch WM16 (W2) *
03b0 00944 0-
03b1 00945 1-
03b2 00946 2 - Event: Feed Air MIN MF03 (W2) * *

Database
03b3 00947 3 - Event: Purge Air MIN MF04 (W2) * *

03b4 00948 4 - Event: Moisture MAX MF05 (W2) * * * * *
03b5 00949 5 - Event: Out of Tolerance MF06 (W2) * * * * *
03b6 00950 6 - Event: Batch setpoint Limit MF07 (W2) * * * * *
03b7 00951 7 - Event: Communication VVC MF08 (W2) *
03b8 00952 8 - Event: No No-motion MF09 (W2) *

03b9 00953 9 - Event: MAX Tolerance Exceeded MF10 (W2) *
03ba 00954 A - Event: MIN Tolerance Exceeded MF11 (W2) *
03bb 00955 B - Event: Material Amount MF12 (W2) * *
03bc 00956 C - Event: Temperature-MAX MF13 (W2) *
03bd 00957 D-
03be 00958 E - Event: Pressure Blower MF15 (W2) *

03bf 00959 F - Event: Press. Cooling MF16 (W2) *
03c0 00960 0 - Event: Run Disabled IL01 (W2) * * * * * * *

03c1 00961 1 - Event: Mechanics IL02 (W2) * * * * * * *
03c2 00962 2 - Event: Electricity IL03 (W2) * * * * * * *
03c3 00963 3 - Event: Mechatronics IL04 (W2) * * * * * * *
03c4 00964 4 - Event: Not Ready IL05 (W2) * * * * * * *
03c5 00965 5 - Event: Not Ready for Start IL06 (W2) * * * * * * *
03c6 00966 6-
03c7 00967 7-
03c8 00968 8 - Event: Filling disabled IL09 (W2) *

03c9 00969 9 - Event: FCB-Error IL10 (W2) * * * * * * *
03ca 00970 A - Event: Wrong System Time IL11 (W2) * * * * * * *
03cb 00971 B-
03cc 00972 C-
03cd 00973 D-
03ce 00974 E-
03cf 00975 F-
03d0 00976 0 - Event: Controller Limited CO01 (W2) * * * * *

Database
03d1 00977 1 - Event: MIN Flow Gate CO02 (W2) * * *

03d2 00978 2 - Event: MAX Flow Gate CO03 (W2) * * *
03d3 00979 3 - Event: Bin Load MAX Sensor CO04 (W2) * * * * * *
03d4 00980 4 - Event: Volum. caused by LC-error CO05 (W2) * *
03d5 00981 5 -Event: MAX Flow Gate (B) CO06 (W2) * *
03d6 00982 6-
03d7 00983 7-
03d8 00984 8-
03d9 00985 9 - Event: MIN Flow Gate (B) CO10 (W2) *

03da 00986 A - Event: Correction MAX CO11 (W2) *
03db 00987 B - Event: Limit Gain CO12 (W2) *
03dc 00988 C - Event: Vibro Controller VVC CO13 (W2) *
03dd 00989 D-
03de 00990 E-
03df 00991 F-
03e0 00992 0 - Event: Minimum Check Quantity CH01 (W2) * * *

03e1 00993 1 - Event: Minimum Fill Weight CH02 (W2) * * * * *
03e2 00994 2 - Event: Maximum Fill Weight CH03 (W2) * * * * *
03e3 00995 3 - Event: Absolute Zero Correction CH04 (W2) * * * * *
Error
03e4 00996 4 - Event: Relative Zero Correction CH05 (W2) * * * * *
Error
03e5 00997 5 - Event: Absolute Span Correction CH06 (W2) * * * * *
Error
03e6 00998 6 - Event: Relative Span Correction CH07 (W2) * * * * *
Error
03e7 00999 7 - Event: Feeder Not Stopped CH08 (W2) * * * * *
03e8 01000 8 - Event: No Check Enable CH09 (W2) * * * * *

03e9 01001 9 - Event: Prepare Check Measure- CH10 (W2) * * * * *
ment
03ea 01002 A - Event: Expect Acceptance CH11 (W2) * * * * *
03eb 01003 B - Event: Check Gate Error CH12 (W2) * * * * *
03ec 01004 C - Event: Bin Error CH13 (W2) * * * * *
03ed 01005 D - Event: CO-Alarm Tube CH14 (W2) *

Database
03ee 01006 E - Event: Min KME Setpoint CH15 (W2) * *

03ef 01007 F - Event: Limit Tare CH16 (W2) *
03f0 01008 0 - Event: Error LC Input CA01 (W2) * * * * * * *

03f1 01009 1 - Event: Tachometer Input CA02 (W2) * * * * *
03f2 01010 2 - Event: Error LC Input (Bin) CA03 (W2) * * * * * *
03f3 01011 3 - Event: Error LC Input (2nd CA04 (W2) * *
Bridge)
03f4 01012 4 - Event: Linearization Error CA05 (W2) * * * * *
03f5 01013 5 - Event: Zero Correction CA06 (W2) * * * *
03f6 01014 6 - Event: DMS-Input CA07 (W2) * * * * *
03f7 01015 7 - Event: Capacity Calibration CA08 (W2) *
03f8 01016 8-
03f9 01017 9 - Event: Error LC Input (FWC) CA10 (W2) *

03fa 01018 A-
03fb 01019 B-
03fc 01020 C-
03fd 01021 D-
03fe 01022 E - Event: Error LC Input (2nd Bin) CA15 (W2) *

03ff 01023 F - Event: LC Input > MAX (2nd Bin) CA16 (W2) *
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: Hopper overload HI08 (W2) * *
0408 01032 8 - Event: Maximum Load HI09 (W2) *

0409 01033 9 - Event: LC Input > MAX (Bin) HI10 (W2) * * * * * *
040a 01034 A - Event: Bin Level MAX HI11 (W2) * * * * * *

Database
040b 01035 B - Event: Bin Level MAX HI12 (W2) *

040c 01036 C - Event: FC-MAX Limit HI13 (W2) * * *
040d 01037 D - Event: DMS-Input > MAX HI14 (W2) * * * * *
040e 01038 E - Event: MAX (2nd Bin) HI15 (W2) *
040f 01039 F - Event: Pressure-MAX HI16 (W2) * * * * *
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: Hopper load < MIN LO08 (W2) *
0418 01048 8 - Event: MIN (2nd Bin) LO09 (W2) *

0419 01049 9 - Event: DMS-Input < MIN LO10 (W2) * * * * *
041a 01050 A - Event: Bin Level MIN LO11 (W2) * * * * * *
041b 01051 B - Event: 2nd Bridge MIN LO12 (W2) *
041c 01052 C - Event: FC-MIN Limit LO13 (W2) * * *
041d 01053 D - Event: FC-Speed < MIN LO14 (W2) *
041e 01054 E-
041f 01055 F - Event: Pressure-MIN LO16 (W2) * * * * *

0420 01056 0 - Event: Memory SY01 (W1) * * * * * * *

VCU20100-Unit 2
VCU20100-Unit 3
0426 01062 6 - Event: Communication VHM SY07 (W1) * * * * * * *
serial
0427 01063 7 - Event: Cyclic Communication SY08 (W1) * * * * * * *

Database
0428 01064 8-
0429 01065 9 - Event: Acyclic Communication SY10 (W1) * * * * * * *

042a 01066 A-
042b 01067 B-
042c 01068 C - Event: Bluetooth channel broken SY13 (W1) *

042d 01069 D-
042e 01070 E - Event: Communication SY15 (W1) * * * * * *

VMO20100-Unit 1
042f 01071 F - Event: Communication SY16 (W1) * * * * * *
VMO20100-Unit 2
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 - Event: External Event 3 SC11 (W1) * * * * * * *
043b 01083 B - Event: External Event 4 SC12 (W1) * * * * * * *
043c 01084 C - Event: Discharge Gate SC13 (W1) * *
043d 01085 D - Event: Gate OPEN Time > MAX SC14 (W1) *
043e 01086 E - Event: Batching Time > MAX SC15 (W1) *
043f 01087 F - Event: Wrong Rotation Direction SC16 (W1) *
0440 01088 0 - Event: Power Failure WE01 (W1) * * * * * * *


Database

0447 01095 7 - Event: Analog Input < Offset WE08 (W1) * * * * * *
0448 01096 8-
0449 01097 9-
044a 01098 A-
044b 01099 B-
044c 01100 C - Event: NAMUR Error VMO1-DI7 WE13 (W1) * * * *

044d 01101 D - Event: NAMUR Error VMO2-DI7 WE14 (W1) * * * *
044e 01102 E-
044f 01103 F-
0450 01104 0 - Event: Limit Switch WM01 (W1) * *

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 - Event: Slip 2 WM05 (W1) * *
0455 01109 5 - Event: Chain Motion Monitor WM06 (W1) *
0456 01110 6-
0457 01111 7-
0458 01112 8 - Event: Motor Start WM09 (W1) *

0459 01113 9-
045a 01114 A-
045b 01115 B-
045c 01116 C - Event: Agitator Overload WM13 (W1) *

045d 01117 D - Event: Feed Air MAX WM14 (W1) *
045e 01118 E - Event: Motor blocked WM15 (W1) *
045f 01119 F - Event: Motor Protection Switch WM16 (W1) *
0460 01120 0-
0461 01121 1-
0462 01122 2 - Event: Feed Air MIN MF03 (W1) * *

Database
0463 01123 3 - Event: Purge Air MIN MF04 (W1) * *

0464 01124 4 - Event: Moisture MAX MF05 (W1) * * * * *
0465 01125 5 - Event: Out of Tolerance MF06 (W1) * * * * *
0466 01126 6 - Event: Batch setpoint Limit MF07 (W1) * * * * *
0467 01127 7 - Event: Communication VVC MF08 (W1) *
0468 01128 8 - Event: No No-motion MF09 (W1) *

0469 01129 9 - Event: MAX Tolerance Exceeded MF10 (W1) *
046a 01130 A - Event: MIN Tolerance Exceeded MF11 (W1) *
046b 01131 B - Event: Material Amount MF12 (W1) * *
046c 01132 C - Event: Temperature-MAX MF13 (W1) *
046d 01133 D-
046e 01134 E - Event: Pressure Blower MF15 (W1) *

046f 01135 F - Event: Press. Cooling MF16 (W1) *
0470 01136 0 - Event: Run Disabled IL01 (W1) * * * * * * *

0471 01137 1 - Event: Mechanics IL02 (W1) * * * * * * *
0472 01138 2 - Event: Electricity IL03 (W1) * * * * * * *
0473 01139 3 - Event: Mechatronics IL04 (W1) * * * * * * *
0474 01140 4 - Event: Not Ready IL05 (W1) * * * * * * *
0475 01141 5 - Event: Not Ready for Start IL06 (W1) * * * * * * *
0476 01142 6-
0477 01143 7-
0478 01144 8 - Event: Filling disabled IL09 (W1) *

0479 01145 9 - Event: FCB-Error IL10 (W1) * * * * * * *
047a 01146 A - Event: Wrong System Time IL11 (W1) * * * * * * *
047b 01147 B-
047c 01148 C-
047d 01149 D-
047e 01150 E-
047f 01151 F-
0480 01152 0 - Event: Controller Limited CO01 (W1) * * * * *

Database
0481 01153 1 - Event: MIN Flow Gate CO02 (W1) * * *

0482 01154 2 - Event: MAX Flow Gate CO03 (W1) * * *
0483 01155 3 - Event: Bin Load MAX Sensor CO04 (W1) * * * * * *
0484 01156 4 - Event: Volum. caused by LC-error CO05 (W1) * *
0485 01157 5 - Event: MAX Flow Gate (B) CO06 (W1) * *
0486 01158 6-
0487 01159 7-
0488 01160 8-
0489 01161 9 - Event: MIN Flow Gate (B) CO10 (W1) *

048a 01162 A - Event: Correction MAX CO11 (W1) *
048b 01163 B - Event: Limit Gain CO12 (W1) *
048c 01164 C - Event: Vibro Controller VVC CO13 (W1) *
048d 01165 D-
048e 01166 E-
048f 01167 F-
0490 01168 0 - Event: Minimum Check Quantity CH01 (W1) * * *

0491 01169 1 - Event: Minimum Fill Weight CH02 (W1) * * * * *
0492 01170 2 - Event: Maximum Fill Weight CH03 (W1) * * * * *
0493 01171 3 - Event: Absolute Zero Correction CH04 (W1) * * * * *
Error
0494 01172 4 - Event: Relative Zero Correction CH05 (W1) * * * * *
Error
0495 01173 5 - Event: Absolute Span Correction CH06 (W1) * * * * *
Error
0496 01174 6 - Event: Relative Span Correction CH07 (W1) * * * * *
Error
0497 01175 7 - Event: Feeder Not Stopped CH08 (W1) * * * * *
0498 01176 8 - Event: No Check Enable CH09 (W1) * * * * *

0499 01177 9 - Event: Prepare Check Measure- CH10 (W1) * * * * *
ment
049a 01178 A - Event: Expect Acceptance CH11 (W1) * * * * *
049b 01179 B - Event: Check Gate Error CH12 (W1) * * * * *
049c 01180 C - Event: Bin Error CH13 (W1) * * * * *
049d 01181 D - Event: CO-Alarm Tube CH14 (W1) *

Database
049e 01182 E - Event: Min KME Setpoint CH15 (W1) * *

049f 01183 F - Event: Limit Tare CH16 (W1) *
04a0 01184 0 - Event: Error LC Input CA01 (W1) * * * * * * *

04a1 01185 1 - Event: Tachometer Input CA02 (W1) * * * * *
04a2 01186 2 - Event: Error LC Input (Bin) CA03 (W1) * * * * * *
04a3 01187 3 - Event: Error LC Input (2nd CA04 (W1) * *
Bridge)
04a4 01188 4 - Event: Linearization Error CA05 (W1) * * * * *
04a5 01189 5 - Event: Zero Correction CA06 (W1) * * * *
04a6 01190 6 - Event: DMS-Input CA07 (W1) * * * * *
04a7 01191 7 - Event: Capacity Calibration CA08 (W1) *
04a8 01192 8-
04a9 01193 9 - Event: Error LC Input (FWC) CA10 (W1) *

04aa 01194 A-
04ab 01195 B-
04ac 01196 C-
04ad 01197 D-
04ae 01198 E - Event: Error LC Input (2nd Bin) CA15 (W1) *

04af 01199 F - Event: LC Input > MAX (2nd Bin) CA16 (W1) *
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) * * *
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: Hopper overload HI08 (W1) * *
04b8 01208 8 - Event: Maximum Load HI09 (W1) *

04b9 01209 9 - Event: LC Input > MAX (Bin) HI10 (W1) * * * * * *
04ba 01210 A - Event: Bin Level MAX HI11 (W1) * * * * * *

Database
04bb 01211 B - Event: 2nd Bridge MAX HI12 (W1) *

04bc 01212 C - Event: FC-MAX Limit HI13 (W1) * * *
04bd 01213 D - Event: DMS-Input > MAX HI14 (W1) * * * * *
04be 01214 E - Event: MAX (2nd Bin) HI15 (W1) *
04bf 01215 F - Event: Pressure-MAX HI16 (W1) * * * * *
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: Hopper load < MIN LO08 (W1) *
04c8 01224 8 - Event: MIN (2nd Bin) LO09 (W1) *

04c9 01225 9 - Event: DMS-Input < MIN LO10 (W1) * * * * *
04ca 01226 A - Event: Bin Level MIN LO11 (W1) * * * * * *
04cb 01227 B - Event: 2nd Bridge MIN LO12 (W1) *
04cc 01228 C - Event: FC-MIN Limit LO13 (W1) * * *
04cd 01229 D - Event: FC-Speed < MIN LO14 (W1) *
04ce 01230 E-
04cf 01231 F - Event: Pressure-MIN LO16 (W1) * * * * *

04d0 01232 0 - Event: Memory SY01 (A) * * * * * * *

04d1 01233 1 - Event: Communication SY02 (A) * * * * * *
VCU20100-Unit 2
04d2 01234 2 - Event: Communication SY03 (A) * * * * * *
VCU20100-Unit 3
04d3 01235 3 - Event: Communication HMI 1 SY04 (A) * * * * * * *
04d6 01238 6 - Event: Communication VHM SY07 (A) * * * * * * *
serial
04d7 01239 7 - Event: Cyclic Communication SY08 (A) * * * * * * *

Database
04d8 01240 8-
04d9 01241 9 - Event: Acyclic Communication SY10 (A) * * * * * * *

04da 01242 A-
04db 01243 B-
04dc 01244 C - Event: Bluetooth channel broken SY13 (A) *

04dd 01245 D-
04de 01246 E - Event: Communication SY15 (A) * * * * * *

VMO20100-Unit 1
04df 01247 F - Event: Communication SY16 (A) * * * * * *
VMO20100-Unit 2
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 - Event: External Event 3 SC11 (A) * * * * * * *
04eb 01259 B - Event: External Event 4 SC12 (A) * * * * * * *
04ec 01260 C - Event: Discharge Gate SC13 (A) * *
04ed 01261 D - Event: Gate OPEN Time > MAX SC14 (A) *
04ee 01262 E - Event: Batching Time > MAX SC15 (A) *
04ef 01263 F - Event: Wrong Rotation Direction SC16 (A) *
04f0 01264 0 - Event: Power Failure WE01 (A) * * * * * * *

04f1 01265 1 - Event: NAMUR Error VCU1-DI6 WE02 (A) * * * * * * *
04f2 01266 2 - Event: NAMUR Error VCU1-DI7 WE03 (A) * * * * * * *
04f3 01267 3 - Event: NAMUR Error VCU2-DI6 WE04 (A) * * * * * *

Database

04f7 01271 7 - Event: Analog Input < Offset WE08 (A) * * * * * *
04f8 01272 8-
04f9 01273 9-
04fa 01274 A-
04fb 01275 B-
04fc 01276 C - Event: NAMUR Error VMO1-DI7 WE13 (A) * * * *

04fd 01277 D - Event: NAMUR Error VMO2-DI7 WE14 (A) * * * *
04fe 01278 E-
04ff 01279 F-
0500 01280 0 - Event: Limit Switch WM01 (A) * *

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 - Event: Slip 2 WM05 (A) * *
0505 01285 5 - Event: Chain Motion Monitor WM06 (A) *
0506 01286 6-
0507 01287 7-
0508 01288 8 - Event: Motor Start WM09 (A) *

0509 01289 9-
050a 01290 A-
050b 01291 B-
050c 01292 C - Event: Agitator Overload WM13 (A) *

050d 01293 D - Event: Feed Air MAX WM14 (A) *
050e 01294 E - Event: Motor blocked WM15 (A) *
050f 01295 F - Event: Motor Protection Switch WM16 (A) *
0510 01296 0-
0511 01297 1-
0512 01298 2 - Event: Feed Air MIN MF03 (A) * *

Database
0513 01299 3 - Event: Purge Air MIN MF04 (A) * *

0514 01300 4 - Event: Moisture MAX MF05 (A) * * * * *
0515 01301 5 - Event: Out of Tolerance MF06 (A) * * * * *
0516 01302 6 - Event: Batch setpoint Limit MF07 (A) * * * * *
0517 01303 7 - Event: Communication VVC MF08 (A) *
0518 01304 8 - Event: No No-motion MF09 (A) *

0519 01305 9 - Event: MAX Tolerance Exceeded MF10 (A) *
051a 01306 A - Event: MIN Tolerance Exceeded MF11 (A) *
051b 01307 B - Event: Material Amount MF12 (A) * *
051c 01308 C - Event: Temperature-MAX MF13 (A) *
051d 01309 D-
051e 01310 E - Event: Pressure Blower MF15 (A) *

051f 01311 F - Event: Press. Cooling MF16 (A) *
0520 01312 0 - Event: Run Disabled IL01 (A) * * * * * * *

0521 01313 1 - Event: Mechanics IL02 (A) * * * * * * *
0522 01314 2 - Event: Electricity IL03 (A) * * * * * * *
0523 01315 3 - Event: Mechatronics IL04 (A) * * * * * * *
0524 01316 4 - Event: Not Ready IL05 (A) * * * * * * *
0525 01317 5 - Event: Not Ready for Start IL06 (A) * * * * * * *
0526 01318 6-
0527 01319 7-
0528 01320 8 - Event: Filling disabled IL09 (A) *

0529 01321 9 - Event: FCB-Error IL10 (A) * * * * * * *
052a 01322 A - Event: Wrong System Time IL11 (A) * * * * * * *
052b 01323 B-
052c 01324 C-
052d 01325 D-
052e 01326 E-
052f 01327 F-
0530 01328 0 - Event: Controller Limited CO01 (A) * * * * *

Database
0531 01329 1 - Event: MIN Flow Gate CO02 (A) * * *

0532 01330 2 - Event: MAX Flow Gate CO03 (A) * * *
0533 01331 3 - Event: Bin Load MAX Sensor CO04 (A) * * * * * *
0534 01332 4 - Event: Volum. caused by LC-error CO05 (A) * *
0535 01333 5 -Event: MAX Flow Gate (B) CO06 (A) * *
0536 01334 6-
0537 01335 7-
0538 01336 8-
0539 01337 9 - Event: MIN Flow Gate (B) CO10 (A) *

053a 01338 A - Event: Correction MAX CO11 (A) *
053b 01339 B - Event: Limit Gain CO12 (A) *
053c 01340 C - Event: Vibro Controller VVC CO13 (A) *
053d 01341 D-
053e 01342 E-
053f 01343 F-
0540 01344 0 - Event: Minimum Check Quantity CH01 (A) * * *

0541 01345 1 - Event: Minimum Fill Weight CH02 (A) * * * * *
0542 01346 2 - Event: Maximum Fill Weight CH03 (A) * * * * *
0543 01347 3 - Event: Absolute Zero Correction CH04 (A) * * * * *
Error
0544 01348 4 - Event: Relative Zero Correction CH05 (A) * * * * *
Error
0545 01349 5 - Event: Absolute Span Correction CH06 (A) * * * * *
Error
0546 01350 6 - Event: Relative Span Correction CH07 (A) * * * * *
Error
0547 01351 7 - Event: Feeder Not Stopped CH08 (A) * * * * *
0548 01352 8 - Event: No Check Enable CH09 (A) * * * * *

0549 01353 9 - Event: Prepare Check Measure- CH10 (A) * * * * *
ment
054a 01354 A - Event: Expect Acceptance CH11 (A) * * * * *
054b 01355 B - Event: Check Gate Error CH12 (A) * * * * *
054c 01356 C - Event: Bin Error CH13 (A) * * * * *
054d 01357 D - Event: CO-Alarm Tube CH14 (A) *

Database
054e 01358 E - Event: Min KME Setpoint CH15 (A) * *

054f 01359 F - Event: Limit Tare CH16 (A) *
0550 01360 0 - Event: Error LC Input CA01 (A) * * * * * * *

0551 01361 1 - Event: Tachometer Input CA02 (A) * * * * *
0552 01362 2 - Event: Error LC Input (Bin) CA03 (A) * * * * * *
0553 01363 3 - Event: Error LC Input (2nd CA04 (A) * *
Bridge)
0554 01364 4 - Event: Linearization Error CA05 (A) * * * * *
0555 01365 5 - Event: Zero Correction CA06 (A) * * * *
0556 01366 6 - Event: DMS-Input CA07 (A) * * * * *
0557 01367 7 - Event: Capacity Calibration CA08 (A) *
0558 01368 8-
0559 01369 9 - Event: Error LC Input (FWC) CA10 (A) *

055a 01370 A-
055b 01371 B-
055c 01372 C-
055d 01373 D-
055e 01374 E - Event: Error LC Input (2nd Bin) CA15 (A) *

055f 01375 F - Event: LC Input > MAX (2nd Bin) CA16 (A) *
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: Hopper overload HI08 (A) * *
0568 01384 8- *
0569 01385 9 - Event: LC Input > MAX (Bin) HI10 (A) * * * * * *
056a 01386 A - Event: Bin Level MAX HI11 (A) * * * * * *

Database
056b 01387 B - Event: 2nd Bridge MAX HI12 (A) *

056c 01388 C - Event: FC-MAX Limit HI13 (A) * * *
056d 01389 D - Event: DMS-Input > MAX HI14 (A) * * * * *
056e 01390 E - Event: MAX (2nd Bin) HI15 (A) *
056f 01391 F - Event: Pressure-MAX HI16 (A) * * * * *
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: Hopper load < MIN LO08 (A) *
0578 01400 8 - Event: MIN (2nd Bin) LO09 (A) *

0579 01401 9 - Event: DMS-Input < MIN LO10 (A) * * * * *
057a 01402 A - Event: Bin Level MIN LO11 (A) * * * * * *
057b 01403 B - Event: 2nd Bridge MIN LO12 (A) *
057c 01404 C - Event: FC-MIN Limit LO13 (A) * * *
057d 01405 D - Event: FC-Speed < MIN LO14 (A) *
057e 01406 E-
057f 01407 F - Event: Pressure-MIN LO16 (A) * * * * *

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-
0588 01416 8-

Database
0589 01417 9-
058a 01418 A-
058b 01419 B-
058c 01420 C-
058d 01421 D - VCU1 DI6 Error * * * * * * *

058e 01422 E - VCU1 DI7 Error * * * * * * *
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-
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 * * * * * * *

Database
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 - VCU2 DI1 * * * * * * *

05b1 01457 1 - VCU2 DI2 * * * * * * *
05b2 01458 2 - VCU2 DI3 * * * * * * *
05b3 01459 3 - VCU2 DI4 * * * * * * *
05b4 01460 4 - VCU2 DI5 * * * * * * *
05b5 01461 5 - VCU2 DI6 * * * * * * *
05b6 01462 6 - VCU2 DI7 * * * * * * *
05b7 01463 7-
05b8 01464 8-
05b9 01465 9-
05ba 01466 A-
05bb 01467 B-
05bc 01468 C-
05bd 01469 D - VCU2 DI6 Error * * * * * * *

05be 01470 E - VCU2 DI7 Error * * * * * * *
05bf 01471 F-
05c0 01472 0 - VMO1 DI1 * * * * * * *

05c1 01473 1 - VMO1 DI2 * * * * * * *
05c2 01474 2 - VMO1 DI3 * * * * * * *
05c3 01475 3 - VMO1 DI4 * * * * * * *
05c4 01476 4 - VMO1 DI5 * * * * * * *
05c5 01477 5 - VMO1 DI6 * * * * * * *

Database
05c6 01478 6 - VMO1 DI7 * * * * * * *

05c7 01479 7-
05c8 01480 8-
05c9 01481 9-
05ca 01482 A-
05cb 01483 B-
05cc 01484 C-
05cd 01485 D-
05ce 01486 E - VMO1 DI7 Error * * * * * * *

05cf 01487 F-
05d0 01488 0 - VCU2 DO1 * * * * * * *

05d1 01489 1 - VCU2 DO2 * * * * * * *
05d2 01490 2 - VCU2 DO3 * * * * * * *
05d3 01491 3 - VCU2 DO4 * * * * * * *
05d4 01492 4 - VCU2 DO5 * * * * * * *
05d5 01493 5 - VCU2 DO6 * * * * * * *
05d6 01494 6 - VCU2 DO7 * * * * * * *
05d7 01495 7 - VCU2 DO8 * * * * * * *
05d8 01496 8 - VMO1 DO1 * * * * * * *

05d9 01497 9 - VMO1 DO2 * * * * * * *
05da 01498 A - VMO1 DO3 * * * * * * *
05db 01499 B - VMO1 DO4 * * * * * * *
05dc 01500 C - VMO1 DO5 * * * * * * *
05dd 01501 D-
05de 01502 E-
05df 01503 F-
05e0 01504 0 - VCU3 DI1 * * * * * * *

05e1 01505 1 - VCU3 DI2 * * * * * * *
05e2 01506 2 - VCU3 DI3 * * * * * * *
05e3 01507 3 - VCU3 DI4 * * * * * * *

Database
05e4 01508 4 - VCU3 DI5 * * * * * * *

05e5 01509 5 - VCU3 DI6 * * * * * * *
05e6 01510 6 - VCU3 DI7 * * * * * * *
05e7 01511 7-
05e8 01512 8-
05e9 01513 9-
05ea 01514 A-
05eb 01515 B-
05ec 01516 C-
05ed 01517 D - VCU3 DI6 Error * * * * * * *

05ee 01518 E - VCU3 DI7 Error * * * * * * *
05ef 01519 F-
05f0 01520 0 - VMO2 DI1 * * * * * * *

05f1 01521 1 - VMO2 DI2 * * * * * * *
05f2 01522 2 - VMO2 DI3 * * * * * * *
05f3 01523 3 - VMO2 DI4 * * * * * * *
05f4 01524 4 - VMO2 DI5 * * * * * * *
05f5 01525 5 - VMO2 DI6 * * * * * * *
05f6 01526 6 - VMO2 DI7 * * * * * * *
05f7 01527 7-
05f8 01528 8-
05f9 01529 9-
05fa 01530 A-
05fb 01531 B-
05fc 01532 C-
05fd 01533 D-
05fe 01534 E - VMO2 DI7 Error * * * * * * *

05ff 01535 F-
0600 01536 0 - VCU3 DO1 * * * * * * *

0601 01537 1 - VCU3 DO2 * * * * * * *

Database
0602 01538 2 - VCU3 DO3 * * * * * * *

0603 01539 3 - VCU3 DO4 * * * * * * *
0604 01540 4 - VCU3 DO5 * * * * * * *
0605 01541 5 - VCU3 DO6 * * * * * * *
0606 01542 6 - VCU3 DO7 * * * * * * *
0607 01543 7 - VCU3 DO8 * * * * * * *
0608 01544 8 - VMO2 DO1 * * * * * * *

0609 01545 9 - VMO2 DO2 * * * * * * *
060a 01546 A - VMO2 DO3 * * * * * * *
060b 01547 B - VMO2 DO4 * * * * * * *
060c 01548 C - VMO2 DO5 * * * * * * *
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-
061d 01565 D-
061e 01566 E-
061f 01567 F-

Database
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 Activated Material *
0670 01648 0 - Reserved * * * * * * *

0671 01649 1-
0672 01650 2-
0673 01651 3-

Database
0674 01652 4-
0675 01653 5-
0676 01654 6-
0677 01655 7-
0678 01656 8 - Reserved * * * * * * *

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 - Current Ingredient *

0691 01681 1-

Database
0692 01682 2-
0693 01683 3-
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 - Ingredient No. 1 ON *

06a6 01702 6 – Ingredient No. 7 ON *

06aa 01706 A - Full Feed ON *
06ab 01707 B - Dribble Feed Sequential ON *
06ac 01708 C - Agitator ON *
06ad 01709 D - Batch active *
06ae 01710 E-
06af 01711 F-

Database
06b0 01712 0-
06b1 01713 1-
06b2 01714 2-
06b3 01715 3-
06b4 01716 4-
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-

Database
06cf 01743 F-
06d0 01744 0 - Setpoint via OP *

06d1 01745 1 - OS: Offset of control magnitude *
06d2 01746 2 - BC: Capacity Adaption Feed *
Hopper
06d3 01747 3 - TD: Control speed adaption *
06d4 01748 4-
06d5 01749 5 - Events are acknowleged * * * * * * *

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 - Calibration Success * *
06dc 01756 C - Calibration Fail * *
06dd 01757 D - Refill Preparation *
06de 01758 E - Refillsequence active *
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-

Database
06ec 01772 C-
06ed 01773 D-
06ee 01774 E-
06ef 01775 F-
06f0 01776 0 - MDP Bit 1 *

06f1 01777 1 - MDP Bit 2 *
06f2 01778 2 - MDP Bit 3 *
06f3 01779 3 - MDP Bit 4 *
06f4 01780 4 - MDP Bit 5 *
06f5 01781 5-
06f6 01782 6-
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-

Database
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 * * * * * * *
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 * * * * * * *

Database
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 - FCB_DO 01 * * * * * * *

0731 01841 1 - FCB_DO 02 * * * * * * *
0732 01842 2 - FCB_DO 03 * * * * * * *
0733 01843 3 - FCB_DO 04 * * * * * * *
0734 01844 4 - FCB_DO 05 * * * * * * *
0735 01845 5 - FCB_DO 06 * * * * * * *
0736 01846 6 - FCB_DO 07 * * * * * * *
0737 01847 7 - FCB_DO 08 * * * * * * *
0738 01848 8 - FCB_DO 09 * * * * * * *

0739 01849 9 - FCB_DO 10 * * * * * * *
073a 01850 A - FCB_DO 11 * * * * * * *
073b 01851 B - FCB_DO 12 * * * * * * *
073c 01852 C - FCB_DO 13 * * * * * * *
073d 01853 D - FCB_DO 14 * * * * * * *
073e 01854 E - FCB_DO 15 * * * * * * *
073f 01855 F - FCB_DO 16 * * * * * * *
0740 01856 0 - FCB_DO 17 * * * * * * *

0741 01857 1 - FCB_DO 18 * * * * * * *
0742 01858 2 - FCB_DO 19 * * * * * * *
0743 01859 3 - FCB_DO 20 * * * * * * *
0744 01860 4 - FCB_DO 21 * * * * * * *
0745 01861 5 - FCB_DO 22 * * * * * * *
0746 01862 6 - FCB_DO 23 * * * * * * *

Database
0747 01863 7 - FCB_DO 24 * * * * * * *

0748 01864 8 - FCB_DO 25 * * * * * * *

0749 01865 9 - FCB_DO 26 * * * * * * *
074a 01866 A - FCB_DO 27 * * * * * * *
074b 01867 B - FCB_DO 28 * * * * * * *
074c 01868 C - FCB_DO 29 * * * * * * *
074d 01869 D - FCB_DO 30 * * * * * * *
074e 01870 E - FCB_DO 31 * * * * * * *
074f 01871 F - FCB_DO 32 * * * * * * *
Tab. 10 : Fieldbus status
3.3.1.2.2 Read process values (IEEE format)
hex dec Process values Dimension VLW VWF VBW VMC VSF VIF VBC
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 1/min * * *
0760 01888 Fill Weight kg * *
0762 01890 BIN: Fill Weight kg * * * * * *
0764 01892 Belt Load 2nd Bridge kg/m *
0766 01894 Setpoint kg/h * * * * *
0768 01896 Batch Actual Value kg * * * * * *
076a 01898 Batch Resid. Amount kg * * * * * *
076c 01900 Perc. setpoint % * * * * *
076e 01902 Flow Gate Position % * * *
0770 01904 Deviation % * * * * *
0772 01906 Moisture % * * * * *
0774 01908 Corrected Feedrate kg/h * * * * *

Database
0776 01910 Totalizer 1 corrected kg * * * * *

0778 01912 Totalizer 2 corrected kg * * * * *
077a 01914 Totalizer 3 corrected kg * * * * *
077c 01916 BIN: Relative Fill Weight % * * * * * *
077e 01918 BIN: Setpoint kg * * * * *
0780 01920 Analog Output 1 mA * * * * * * *
0782 01922 Analog Input 1 mA * * * * * * *
0784 01924 Analog Output 3 mA * * * * * * *
0786 01926 VCU2: Analog Output 1 mA * * * * * * *
0788 01928 Analog Input 2 mA * * * * * * *
078a 01930 VCU2: Analog Output 2 mA * * * * * * *
078c 01932 VCU3: Analog Output 1 mA * * * * * * *
078e 01934 VCU2: Analog Input 1 mA * * * * * * *
0792 01938 Belt Slip mA * *
0794 01940 Belt Drift * *
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 Controller Magnitude mA * * * *
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 *

Database
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 Controller Mag. Yz mA *
07d2 02002 Controller Mag. Yzi % *
07d4 02004 Nominal Load kg * *
07d6 02006 Unlin. Flow Rate kg/h * *
07d8 02008 Actual Tare kg/h * * * * *
07da 02010 BIN: Utilization LC % * * * * * *
07dc 02012 BIN: Loadcell mV/V * * * * * *
07de 02014 Controller Mag. Yb mA * * * * *
07e0 02016 Controller Mag. Ybi mA * * * * *
07e2 02018
07e4 02020 Relative Zero Correction % * * * * *

07e6 02022 Relative Span Correction % * * * * *
07e8 02024 Contin. Result Z kg * * * * *
07ea 02026 Check Result F/Z * * * * *
07ec 02028 Check Meas. Time h * *
07ee 02030 Check Belt Length m * * *
07f0 02032 Relative Load 2nd Bridge % *
07f2 02034 2.Br. Loadcell mV/V *
07f4 02036 2.Bridge Utilization LC % *
07f6 02038 Controller Mag. Y2 % *
07f8 02040 Difference Flow Rate kg/h * * *
07fa 02042 Relative Setpoint % * * * * *
07fc 02044 Relative Load % * *

Database
07fe 02046
0800 02048 Check Measurem. Window % * * * * *

0802 02050 AO: Controller Magnitude *
0804 02052 Batch No. *
0806 02054 Ingredient total 1 kg *
080a 02058 Ingredient total 3 kg *
080c 02060 Ingredient total 4 kg *
080e 02062 Ingredient total 5 kg *
081a 02074 Batch total kg *
081c 02076 Tachometer 2 Hz *
081e 02078 Corr. Rel. Feedrate % * * * * *
0820 02080 Belt Load Unlin. kg/m * *
0822 02082 2-Sensor Slip % * *
0824 02084 Batch Setpoint kg *
0826 02086 Batch No. *
0828 02088 Ingredient No. *
082a 02090
082c 02092
082e 02094
0830 02096
0832 02098
0834 02100
0836 02102
0838 02104
083a 02106
083c 02108
083e 02110
0840 02112

Database
0842 02114
0844 02116
0846 02118
0848 02120
084a 02122
084c 02124
084e 02126
0850 02128
0852 02130
0854 02132
0856 02134
0858 02136
085a 02138
085c 02140
085e 02142
0860 02144
0862 02146
0864 02148
0866 02150 Analog Output 2 mA * * * * * * *

0868 02152 Analog Input 1 mA * * * * * * *
086a 02154
086c 02156
086e 02158 Pulses Sensor PULSE * *

0870 02160
0872 02162 FC act. Deviation % * *

0874 02164
0876 02166 Compensation Weight kg * * * *

0878 02168 Utilize Pressure Sensor % * * * *
087a 02170 Fill Weight not comp kg * * * *
087c 02172 Compensation Weight Bar * * * *
087e 02174 Pressure: Raw mV/V * * * *
0880 02176 Frequence DI_7 Hz * *
0882 02178
0884 02180

Database
0886 02182 Helix Speed Setpoint % *

0888 02184 Helix Setpoint S1 % *
088a 02186 Helix Setpoint S2 % *
088c 02188 Deviation S1 % * *
088e 02190 Deviation S2 % *
0890 02192 Controller Mag. S1 mA * *
0892 02194 Controller Mag. S2 mA *
0894 02196 Load Helixinlet kg *
0896 02198 Helix Load (raw) kg *
0898 02200 Total Weight kg *
089a 02202
089c 02204
089e 02206
08a0 02208
08a2 02210
08a4 02212 Analog Output 2 mA * * * * * * *

08a6 02214 Analog Input 1 mA * * * * * * *
08a8 02216 VCU2: Analog Output 2 mA * * * * * * *
08aa 02218 VCU2: Analog Input 1 mA * * * * * * *
08ac 02220 Deviation abs. % * * * * *
08ae 02222 VCU3: Analog Input 1 mA * * * * * * *
08b0 02224 Loadcell 1 mV/V * *
08b2 02226 Loadcell 2 mV/V * *
08b4 02228 Utilization LC 2 % * *
08b6 02230
08b8 02232
08ba 02234
08bc 02236
08be 02238 Analog Input 2 mA * * * * * * *

08c0 02240
08c2 02242
08c4 02244
08c6 02246
08c8 02248

Database
08ca 02250
08cc 02252
08ce 02254
08d0 02256 Analog Output 3 mA * * * * * * *

08d2 02258
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 VCU2: Analog Input 2 mA * * * * * * *
0900 02304 VCU3: Analog Input 2 mA * * * * * * *
0906 02310
0908 02312
090a 02314 Temperature °C * * * * * * *

090c 02316 Belt Speed % * *

Database
090e 02318
0910 02320 LC-Raw Helixinlet mV/V *

0912 02322

0916 02326 Helix Load kg *
0918 02328 rel. Helix Load % *
091a 02330 Pulses Helix 1 Imp *
091c 02332 Pulses/Revolution Helix 1 Imp *
091e 02334 Pulses Helix 2 Imp *
0920 02336 Pulses/Revolution Helix 2 Imp *
0922 02338 Difference-Pulses Helix 1/2 Imp *
0924 02340 Pulses/Revolution Helix 1/2 Imp *
0926 02342 Difference-Angle Helix 1/2 Degrees *
0928 02344 Pulses Belt PULSE * *
092a 02346 Relative Batch Actual Value % * * * * *
092c 02348 Process Temperature °C *
092e 02350 Bluetooth 1 LC mV/V *
0930 02352 Bluetooth 2 LC mV/V *
0932 02354 Bluetooth 1 Temp. °C *
0934 02356 Bluetooth 2 Temp.. °C *
0936 02358 B:Flow Gate Position % * *
0938 02360
093a 02362
093c 02364
093e 02366
0940 02368
0942 02370 B-S: Deviation % * *

0944 02372 B: Deviation kg * *
0946 02374 Bluetooth 1 Reset *
0948 02376 Bluetooth 2 Reset *
094a 02378
094c 02380 BROH before band rejection kg *

094e 02382 TDIFF_act s *
0950 02384 TN_act s *

Database
0952 02386 BIN 2: Fill Weight kg *

0954 02388 BIN 2: Relative Fill Weight % *
0956 02390
0958 02392 FCB_AO 01 * * * * * * *

095a 02394 FCB_AO 02 * * * * * * *
095c 02396 FCB_AO 03 * * * * * * *
095e 02398 FCB_AO 04 * * * * * * *
0960 02400 FCB_AO 05 * * * * * * *
0962 02402 FCB_AO 06 * * * * * * *
0964 02404 FCB_AO 07 * * * * * * *
0966 02406 FCB_AO 08 * * * * * * *
0968 02408 FCB_AO 09 * * * * * * *
096a 02410 FCB_AO 10 * * * * * * *
096c 02412 FCB_AO 11 * * * * * * *
096e 02414 FCB_AO 12 * * * * * * *
0970 02416 FCB_AO 13 * * * * * * *
0972 02418 FCB_AO 14 * * * * * * *
0974 02420 FCB_AO 15 * * * * * * *
0976 02422 FCB_AO 16 * * * * * * *
0978 02424 FCB_AO 17 * * * * * * *
097a 02426 FCB_AO 18 * * * * * * *
097c 02428 FCB_AO 19 * * * * * * *
097e 02430 FCB_AO 20 * * * * * * *
1d00 07424 BIN: Error Roh kg/h *
1d02 07426 BIN: Error kg/h *
1d04 07428 Contin. Result F kg *
1d06 07430 Correction Gain *
1d08 07432 Correction Tare kg *
1d0a 07434 BIN Adaption (raw) *
1d0c 07436 BIN Adaption *
1d0e 07438 QA: Coefficient (kg/h)/mA *
1d10 07440 QA: Coefficient-RAW (kg/h)/mA *
1d12 07442 Difference 1.WB-2.WB kg/m *
1d14 07444 QA-Setpoint kg/m *

Database
1d16 07446 Input of Differential Filter kg/h *

1d18 07448 VMO1: Analog Output 1 mA * * * * * * *
1d1a 07450 VMO1: Analog Output 2 mA * * * * * * *
1d1c 07452 VMO1: Analog Output 3 mA * * * * * * *
1d1e 07454 VMO1: Analog Input 1 mA * * * * * * *
1d20 07456 VMO1: Analog Input 2 mA * * * * * * *
1d22 07458 VMO1: Analog Input 3 mA * * * * * * *
1d2a 07466 VMO2: Analog Input 1 mA * * * * * * *
1d2c 07468 VMO2: Analog Input 2 mA * * * * * * *
1d2e 07470 VMO2: Analog Input 3 mA * * * * * * *
1d30 07472 Belt Load (Controller) kg/m *
1d32 07474
1d34 07476
1d36 07478
1d38 07480
1d3a 07482
1d3c 07484
1d3e 07486
1d40 07488
1d42 07490
1d44 07492
1d46 07494
1d48 07496
1d4a 07498 Rotation Speed IDMS 1/min *

1d4c 07500 Rotation Speed Rel. % *
1d4e 07502 Feeding Pressure Bar *
1d50 07504
1d52 07506
1d54 07508
1d56 07510
1d58 07512

Database
1d5a 07514
1d5c 07516
1d5e 07518
1d60 07520
1d62 07522 Amount kg *

1d64 07524 VVC: Actual Frequency Hz *
1d66 07526 KME: Fill Weight kg *
1d68 07528 KME: Relative Fill Weight % *
1d6a 07530 Check Measurem. Window (B 2) % *
1d6c 07532 VVC: Actual Amplitude % *
1d6e 07534 VCU2: Cycle Time ms * * * * * * *
1d70 07536 VCU3: Cycle Time ms * * * * * * *
1d72 07538 VMO1: Cycle Time ms * * * * * * *
1d74 07540 VMO2: Cycle Time ms * * * * * * *
1d76 07542 Cycle Time Measuring ms * * * * * * *
1d78 07544 VCU2: Response Time ms * * * * * * *
1d7a 07546 VCU3: Response Time ms * * * * * * *
1d7c 07548 VMO1: Response Time ms * * * * * * *
1d7e 07550 VMO2: Response Time ms * * * * * * *
1d80 07552 VVC: Cycle Time ms *
1d82 07554 VVC: Response Time ms *
1d84 07556 VVC: Amplitude Setpoint % *
1d86 07558 VVC: Control Deviation % *
1d88 07560 VVC: Current Max % *
1d8a 07562 VVC: Thermal Load % *
1d8c 07564
1d8e 07566 Belt Length m *

1d90 07568 Load kg *
1d92 07570 B: virtual Buffer kg *
1d94 07572 Bin Load Adaption % *
1d96 07574 B: Coefficient %/mA *
1d98 07576 Controller Mag. Yb delayed mA *
1d9a 07578 Controller Mag. Yb Mean mA *
1d9c 07580 Perc. Controller Magnitude % *

Database
1d9e 07582
Tab. 11 : Fieldbus measured values
3.3.2 Material-Dependent Parameters (MDP)

(MDP = Material-Dependent Parameters)
Note: This chapter is only relevant for software VLW because only the material-dependent parameters exist
here.
Modbus-RTU and All other Protocols

Modbus-TCP
Use ID as Data Read Aktual Value Modify Value

address (AK=1) (AK=3)
Name Parame- Typ dec hex dec hex dec hex

ter
MDP-Set = 1
Nominal Flow Rate P03.03 FLT 6464 1940 14656 3940 31040 7940
Io
Nominal Amount Fo P03.04 FLT 6465 1941 14657 3941 31041 7941
F_CONTROLmin P06.10 FLT 6466 1942 14658 3942 31042 7942
F_CONTROLmax P06.11 FLT 6467 1943 14659 3943 31043 7943
F-Max Value P10.07 FLT 6468 1944 14660 3944 31044 7944
Tare P11.03 FLT 6469 1945 14661 3945 31045 7945
T-Differential P09.01 FLT 6470 1946 14662 3946 31046 7946
Fuzzy MIN P14.03 FLT 6471 1947 14663 3947 31047 7947
P-Component KP P12.01 FLT 6472 1948 14664 3948 31048 7948
I-Component TN P12.02 FLT 6473 1949 14665 3949 31049 7949
Bypass P12.03 FLT 6474 194a 14666 394a 31050 794a
Controller Magnitu- P12.04 FLT 6475 194b 14667 394b 31051 794b
de Offset
Controller Index P12.18 INT 6476 194c 14668 394c 31052 794c
Linearization Y1 P13.02 FLT 6477 194d 14669 394d 31053 794d
Linearization I1 P13.03 FLT 6478 194e 14670 394e 31054 794e
Linearization Y2 P13.04 FLT 6479 194f 14671 394f 31055 794f
Linearization I2 P13.05 FLT 6480 1950 14672 3950 31056 7950

Database

Modbus-TCP


ter
Linearization Y3 P13.06 FLT 6481 1951 14673 3951 31057 7951

Setpoint Range P04.03 FLT 6485 1955 14677 3955 31061 7955
Flow Rate Range P15.06 FLT 6486 1956 14678 3956 31062 7956
Fill Weight Range P15.09 FLT 6487 1957 14679 3957 31063 7957
START Agitator P06.03 FLT 6488 1958 14680 3958 31064 7958
Correction Amount P18.04 FLT 6489 1959 14681 3959 31065 7959
Bypass Adaptation P12.21 FLT 6490 195a 14682 395a 31066 795a
AMOUNTmin P06.05 FLT 6491 195b 14683 395b 31067 795b
F-Min Value P10.05 FLT 6492 195c 14684 395c 31068 795c
Filling Control P06.09 TXT 6493 195d 14685 395d 31069 795d
MDP-Set = 2
Name Parame- Typ dez hex dez hex dez hex
ter
Io
F-Max Value P10.07 FLT 6500 1964 14692 3964 31076 7964
Tare P11.03 FLT 6501 1965 14693 3965 31077 7965
Fuzzy MIN P14.03 FLT 6503 1967 14695 3967 31079 7967
Bypass P12.03 FLT 6506 196a 14698 396a 31082 796a

Database

Modbus-TCP


ter
de Offset
MDP-Set = 3
ter
Io
F-Max Value P10.07 FLT 6532 1984 14724 3984 31108 7984

Database

Modbus-TCP


ter
Tare P11.03 FLT 6533 1985 14725 3985 31109 7985

Fuzzy MIN P14.03 FLT 6535 1987 14727 3987 31111 7987
Bypass P12.03 FLT 6538 198a 14730 398a 31114 798a
de Offset
MDP-Set = 4
ter

Database

Modbus-TCP


ter
Nominal Flow Rate P03.03 FLT 6560 19a0 14752 39a0 31136 79a0
Io
Nominal Amount Fo P03.04 FLT 6561 19a1 14753 39a1 31137 79a1
F_CONTROLmin P06.10 FLT 6562 19a2 14754 39a2 31138 79a2
F_CONTROLmax P06.11 FLT 6563 19a3 14755 39a3 31139 79a3
F-Max Value P10.07 FLT 6564 19a4 14756 39a4 31140 79a4
Tare P11.03 FLT 6565 19a5 14757 39a5 31141 79a5
T-Differential P09.01 FLT 6566 19a6 14758 39a6 31142 79a6
Fuzzy MIN P14.03 FLT 6567 19a7 14759 39a7 31143 79a7
P-Component KP P12.01 FLT 6568 19a8 14760 39a8 31144 79a8
I-Component TN P12.02 FLT 6569 19a9 14761 39a9 31145 79a9
Bypass P12.03 FLT 6570 19aa 14762 39aa 31146 79aa
Controller Magnitu- P12.04 FLT 6571 19ab 14763 39ab 31147 79ab
de Offset
Controller Index P12.18 INT 6572 19ac 14764 39ac 31148 79ac
Linearization Y1 P13.02 FLT 6573 19ad 14765 39ad 31149 79ad
Linearization I1 P13.03 FLT 6574 19ae 14766 39ae 31150 79ae
Linearization Y2 P13.04 FLT 6575 19af 14767 39af 31151 79af
Linearization I2 P13.05 FLT 6576 19b0 14768 39b0 31152 79b0
Linearization Y3 P13.06 FLT 6577 19b1 14769 39b1 31153 79b1
Setpoint Range P04.03 FLT 6581 19b5 14773 39b5 31157 79b5
Flow Rate Range P15.06 FLT 6582 19b6 14774 39b6 31158 79b6
Fill Weight Range P15.09 FLT 6583 19b7 14775 39b7 31159 79b7
START Agitator P06.03 FLT 6584 19b8 14776 39b8 31160 79b8
Correction Amount P18.04 FLT 6585 19b9 14777 39b9 31161 79b9
Bypass Adaptation P12.21 FLT 6586 19ba 14778 39ba 31162 79ba
AMOUNTmin P06.05 FLT 6587 19bb 14779 39bb 31163 79bb

Database

Modbus-TCP


ter
F-Min Value P10.05 FLT 6588 19bc 14780 39bc 31164 79bc
Filling Control P06.09 TXT 6589 19bd 14781 39bd 31165 79bd
MDP-Set = 5
ter
Nominal Flow Rate P03.03 FLT 6592 19c0 14784 39c0 31168 79c0
Io
Nominal Amount Fo P03.04 FLT 6593 19c1 14785 39c1 31169 79c1
F_CONTROLmin P06.10 FLT 6594 19c2 14786 39c2 31170 79c2
F_CONTROLmax P06.11 FLT 6595 19c3 14787 39c3 31171 79c3
F-Max Value P10.07 FLT 6596 19c4 14788 39c4 31172 79c4
Tare P11.03 FLT 6597 19c5 14789 39c5 31173 79c5
T-Differential P09.01 FLT 6598 19c6 14790 39c6 31174 79c6
Fuzzy MIN P14.03 FLT 6599 19c7 14791 39c7 31175 79c7
P-Component KP P12.01 FLT 6600 19c8 14792 39c8 31176 79c8
I-Component TN P12.02 FLT 6601 19c9 14793 39c9 31177 79c9
Bypass P12.03 FLT 6602 19ca 14794 39ca 31178 79ca
Controller Magnitu- P12.04 FLT 6603 19cb 14795 39cb 31179 79cb
de Offset
Controller Index P12.18 INT 6604 19cc 14796 39cc 31180 79cc
Linearization Y1 P13.02 FLT 6605 19cd 14797 39cd 31181 79cd
Linearization I1 P13.03 FLT 6606 19ce 14798 39ce 31182 79ce
Linearization Y2 P13.04 FLT 6607 19cf 14799 39cf 31183 79cf
Linearization I2 P13.05 FLT 6608 19d0 14800 39d0 31184 79d0
Linearization Y3 P13.06 FLT 6609 19d1 14801 39d1 31185 79d1
Linearization Y4 P13.08 FLT 6611 19d3 14803 39d3 31187 79d3
Setpoint Range P04.03 FLT 6613 19d5 14805 39d5 31189 79d5

Database

Modbus-TCP


ter
Flow Rate Range P15.06 FLT 6614 19d6 14806 39d6 31190 79d6
Fill Weight Range P15.09 FLT 6615 19d7 14807 39d7 31191 79d7
START Agitator P06.03 FLT 6616 19d8 14808 39d8 31192 79d8
Correction Amount P18.04 FLT 6617 19d9 14809 39d9 31193 79d9
Bypass Adaptation P12.21 FLT 6618 19da 14810 39da 31194 79da
AMOUNTmin P06.05 FLT 6619 19db 14811 39db 31195 79db
F-Min Value P10.05 FLT 6620 19dc 14812 39dc 31196 79dc
Filling Control P06.09 TXT 6621 19dd 14813 39dd 31197 79dd
MDP-Set = 6
ter
Nominal Flow Rate P03.03 FLT 6624 19e0 14816 39e0 31200 79e0
Io
Nominal Amount Fo P03.04 FLT 6625 19e1 14817 39e1 31201 79e1
F_CONTROLmin P06.10 FLT 6626 19e2 14818 39e2 31202 79e2
F_CONTROLmax P06.11 FLT 6627 19e3 14819 39e3 31203 79e3
F-Max Value P10.07 FLT 6628 19e4 14820 39e4 31204 79e4
Tare P11.03 FLT 6629 19e5 14821 39e5 31205 79e5
T-Differential P09.01 FLT 6630 19e6 14822 39e6 31206 79e6
Fuzzy MIN P14.03 FLT 6631 19e7 14823 39e7 31207 79e7
P-Component KP P12.01 FLT 6632 19e8 14824 39e8 31208 79e8
I-Component TN P12.02 FLT 6633 19e9 14825 39e9 31209 79e9
Bypass P12.03 FLT 6634 19ea 14826 39ea 31210 79ea
Controller Magnitu- P12.04 FLT 6635 19eb 14827 39eb 31211 79eb
de Offset
Controller Index P12.18 INT 6636 19ec 14828 39ec 31212 79ec
Linearization Y1 P13.02 FLT 6637 19ed 14829 39ed 31213 79ed
Linearization I1 P13.03 FLT 6638 19ee 14830 39ee 31214 79ee
Linearization Y2 P13.04 FLT 6639 19ef 14831 39ef 31215 79ef

Database

Modbus-TCP


ter
Linearization I2 P13.05 FLT 6640 19f0 14832 39f0 31216 79f0

Linearization Y3 P13.06 FLT 6641 19f1 14833 39f1 31217 79f1
Linearization Y4 P13.08 FLT 6643 19f3 14835 39f3 31219 79f3
Setpoint Range P04.03 FLT 6645 19f5 14837 39f5 31221 79f5
Flow Rate Range P15.06 FLT 6646 19f6 14838 39f6 31222 79f6
Fill Weight Range P15.09 FLT 6647 19f7 14839 39f7 31223 79f7
START Agitator P06.03 FLT 6648 19f8 14840 39f8 31224 79f8
Correction Amount P18.04 FLT 6649 19f9 14841 39f9 31225 79f9
Bypass Adaptation P12.21 FLT 6650 19fa 14842 39fa 31226 79fa
AMOUNTmin P06.05 FLT 6651 19fb 14843 39fb 31227 79fb
F-Min Value P10.05 FLT 6652 19fc 14844 39fc 31228 79fc
Filling Control P06.09 TXT 6653 19fd 14845 39fd 31229 79fd
MDP-Set = 7
ter
Io
Tare P11.03 FLT 6661 1a05 14853 3a05 31237 7a05
Bypass P12.03 FLT 6666 1a0a 14858 3a0a 31242 7a0a

Database

Modbus-TCP


ter
Controller Magnitu- P12.04 FLT 6667 1a0b 14859 3a0b 31243 7a0b
de Offset
Controller Index P12.18 INT 6668 1a0c 14860 3a0c 31244 7a0c
Linearization Y1 P13.02 FLT 6669 1a0d 14861 3a0d 31245 7a0d
Linearization I1 P13.03 FLT 6670 1a0e 14862 3a0e 31246 7a0e
Linearization Y2 P13.04 FLT 6671 1a0f 14863 3a0f 31247 7a0f
Linearization I2 P13.05 FLT 6672 1a10 14864 3a10 31248 7a10
Linearization Y3 P13.06 FLT 6673 1a11 14865 3a11 31249 7a11
Setpoint Range P04.03 FLT 6677 1a15 14869 3a15 31253 7a15
Flow Rate Range P15.06 FLT 6678 1a16 14870 3a16 31254 7a16
Fill Weight Range P15.09 FLT 6679 1a17 14871 3a17 31255 7a17
START Agitator P06.03 FLT 6680 1a18 14872 3a18 31256 7a18
Correction Amount P18.04 FLT 6681 1a19 14873 3a19 31257 7a19
Bypass Adaptation P12.21 FLT 6682 1a1a 14874 3a1a 31258 7a1a
AMOUNTmin P06.05 FLT 6683 1a1b 14875 3a1b 31259 7a1b
F-Min Value P10.05 FLT 6684 1a1c 14876 3a1c 31260 7a1c
Filling Control P06.09 TXT 6685 1a1d 14877 3a1d 31261 7a1d
MDP-Set = 8
ter
Io

Database

Modbus-TCP


ter
Tare P11.03 FLT 6693 1a25 14885 3a25 31269 7a25

de Offset
MDP-Set = 9
ter

Database

Modbus-TCP


ter
Io
Tare P11.03 FLT 6725 1a45 14917 3a45 31301 7a45
de Offset

Database

Modbus-TCP


ter
MDP-Set = 10
ter
Io
Tare P11.03 FLT 6757 1a65 14949 3a65 31333 7a65
de Offset

Database

Modbus-TCP


ter
MDP-Set = 11
ter
Io
Tare P11.03 FLT 6789 1a85 14981 3a85 31365 7a85
de Offset

Database

Modbus-TCP


ter

MDP-Set = 12
ter
Nominal Flow Rate P03.03 FLT 6816 1aa0 15008 3aa0 31392 7aa0
Io
Nominal Amount Fo P03.04 FLT 6817 1aa1 15009 3aa1 31393 7aa1
F_CONTROLmin P06.10 FLT 6818 1aa2 15010 3aa2 31394 7aa2
F_CONTROLmax P06.11 FLT 6819 1aa3 15011 3aa3 31395 7aa3
F-Max Value P10.07 FLT 6820 1aa4 15012 3aa4 31396 7aa4
Tare P11.03 FLT 6821 1aa5 15013 3aa5 31397 7aa5
T-Differential P09.01 FLT 6822 1aa6 15014 3aa6 31398 7aa6
Fuzzy MIN P14.03 FLT 6823 1aa7 15015 3aa7 31399 7aa7
P-Component KP P12.01 FLT 6824 1aa8 15016 3aa8 31400 7aa8
I-Component TN P12.02 FLT 6825 1aa9 15017 3aa9 31401 7aa9
Bypass P12.03 FLT 6826 1aaa 15018 3aaa 31402 7aaa

Database

Modbus-TCP


ter
Controller Magnitu- P12.04 FLT 6827 1aab 15019 3aab 31403 7aab
de Offset
Controller Index P12.18 INT 6828 1aac 15020 3aac 31404 7aac
Linearization Y1 P13.02 FLT 6829 1aad 15021 3aad 31405 7aad
Linearization I1 P13.03 FLT 6830 1aae 15022 3aae 31406 7aae
Linearization Y2 P13.04 FLT 6831 1aaf 15023 3aaf 31407 7aaf
Linearization I2 P13.05 FLT 6832 1ab0 15024 3ab0 31408 7ab0
Linearization Y3 P13.06 FLT 6833 1ab1 15025 3ab1 31409 7ab1
Linearization Y4 P13.08 FLT 6835 1ab3 15027 3ab3 31411 7ab3
Setpoint Range P04.03 FLT 6837 1ab5 15029 3ab5 31413 7ab5
Flow Rate Range P15.06 FLT 6838 1ab6 15030 3ab6 31414 7ab6
Fill Weight Range P15.09 FLT 6839 1ab7 15031 3ab7 31415 7ab7
START Agitator P06.03 FLT 6840 1ab8 15032 3ab8 31416 7ab8
Correction Amount P18.04 FLT 6841 1ab9 15033 3ab9 31417 7ab9
Bypass Adaptation P12.21 FLT 6842 1aba 15034 3aba 31418 7aba
AMOUNTmin P06.05 FLT 6843 1abb 15035 3abb 31419 7abb
F-Min Value P10.05 FLT 6844 1abc 15036 3abc 31420 7abc
Filling Control P06.09 TXT 6845 1abd 15037 3abd 31421 7abd
MDP-Set = 13
ter
Nominal Flow Rate P03.03 FLT 6848 1ac0 15040 3ac0 31424 7ac0
Io
Nominal Amount Fo P03.04 FLT 6849 1ac1 15041 3ac1 31425 7ac1
F_CONTROLmin P06.10 FLT 6850 1ac2 15042 3ac2 31426 7ac2
F_CONTROLmax P06.11 FLT 6851 1ac3 15043 3ac3 31427 7ac3
F-Max Value P10.07 FLT 6852 1ac4 15044 3ac4 31428 7ac4

Database

Modbus-TCP


ter
Tare P11.03 FLT 6853 1ac5 15045 3ac5 31429 7ac5

T-Differential P09.01 FLT 6854 1ac6 15046 3ac6 31430 7ac6
Fuzzy MIN P14.03 FLT 6855 1ac7 15047 3ac7 31431 7ac7
P-Component KP P12.01 FLT 6856 1ac8 15048 3ac8 31432 7ac8
I-Component TN P12.02 FLT 6857 1ac9 15049 3ac9 31433 7ac9
Bypass P12.03 FLT 6858 1aca 15050 3aca 31434 7aca
Controller Magnitu- P12.04 FLT 6859 1acb 15051 3acb 31435 7acb
de Offset
Controller Index P12.18 INT 6860 1acc 15052 3acc 31436 7acc
Linearization Y1 P13.02 FLT 6861 1acd 15053 3acd 31437 7acd
Linearization I1 P13.03 FLT 6862 1ace 15054 3ace 31438 7ace
Linearization Y2 P13.04 FLT 6863 1acf 15055 3acf 31439 7acf
Linearization I2 P13.05 FLT 6864 1ad0 15056 3ad0 31440 7ad0
Linearization Y3 P13.06 FLT 6865 1ad1 15057 3ad1 31441 7ad1
Linearization Y4 P13.08 FLT 6867 1ad3 15059 3ad3 31443 7ad3
Setpoint Range P04.03 FLT 6869 1ad5 15061 3ad5 31445 7ad5
Flow Rate Range P15.06 FLT 6870 1ad6 15062 3ad6 31446 7ad6
Fill Weight Range P15.09 FLT 6871 1ad7 15063 3ad7 31447 7ad7
START Agitator P06.03 FLT 6872 1ad8 15064 3ad8 31448 7ad8
Correction Amount P18.04 FLT 6873 1ad9 15065 3ad9 31449 7ad9
Bypass Adaptation P12.21 FLT 6874 1ada 15066 3ada 31450 7ada
AMOUNTmin P06.05 FLT 6875 1adb 15067 3adb 31451 7adb
F-Min Value P10.05 FLT 6876 1adc 15068 3adc 31452 7adc
Filling Control P06.09 TXT 6877 1add 15069 3add 31453 7add
MDP-Set = 14
ter

Database

Modbus-TCP


ter
Nominal Flow Rate P03.03 FLT 6880 1ae0 15072 3ae0 31456 7ae0
Io
Nominal Amount Fo P03.04 FLT 6881 1ae1 15073 3ae1 31457 7ae1
F_CONTROLmin P06.10 FLT 6882 1ae2 15074 3ae2 31458 7ae2
F_CONTROLmax P06.11 FLT 6883 1ae3 15075 3ae3 31459 7ae3
F-Max Value P10.07 FLT 6884 1ae4 15076 3ae4 31460 7ae4
Tare P11.03 FLT 6885 1ae5 15077 3ae5 31461 7ae5
T-Differential P09.01 FLT 6886 1ae6 15078 3ae6 31462 7ae6
Fuzzy MIN P14.03 FLT 6887 1ae7 15079 3ae7 31463 7ae7
P-Component KP P12.01 FLT 6888 1ae8 15080 3ae8 31464 7ae8
I-Component TN P12.02 FLT 6889 1ae9 15081 3ae9 31465 7ae9
Bypass P12.03 FLT 6890 1aea 15082 3aea 31466 7aea
Controller Magnitu- P12.04 FLT 6891 1aeb 15083 3aeb 31467 7aeb
de Offset
Controller Index P12.18 INT 6892 1aec 15084 3aec 31468 7aec
Linearization Y1 P13.02 FLT 6893 1aed 15085 3aed 31469 7aed
Linearization I1 P13.03 FLT 6894 1aee 15086 3aee 31470 7aee
Linearization Y2 P13.04 FLT 6895 1aef 15087 3aef 31471 7aef
Linearization I2 P13.05 FLT 6896 1af0 15088 3af0 31472 7af0
Linearization Y3 P13.06 FLT 6897 1af1 15089 3af1 31473 7af1
Linearization Y4 P13.08 FLT 6899 1af3 15091 3af3 31475 7af3
Setpoint Range P04.03 FLT 6901 1af5 15093 3af5 31477 7af5
Flow Rate Range P15.06 FLT 6902 1af6 15094 3af6 31478 7af6
Fill Weight Range P15.09 FLT 6903 1af7 15095 3af7 31479 7af7
START Agitator P06.03 FLT 6904 1af8 15096 3af8 31480 7af8
Correction Amount P18.04 FLT 6905 1af9 15097 3af9 31481 7af9
Bypass Adaptation P12.21 FLT 6906 1afa 15098 3afa 31482 7afa
AMOUNTmin P06.05 FLT 6907 1afb 15099 3afb 31483 7afb

Database

Modbus-TCP


ter
F-Min Value P10.05 FLT 6908 1afc 15100 3afc 31484 7afc
Filling Control P06.09 TXT 6909 1afd 15101 3afd 31485 7afd
MDP-Set = 15
ter
Nominal Flow Rate P03.03 FLT 6912 1b00 15104 3b00 31488 7b00
Io
Nominal Amount Fo P03.04 FLT 6913 1b01 15105 3b01 31489 7b01
F_CONTROLmin P06.10 FLT 6914 1b02 15106 3b02 31490 7b02
F_CONTROLmax P06.11 FLT 6915 1b03 15107 3b03 31491 7b03
F-Max Value P10.07 FLT 6916 1b04 15108 3b04 31492 7b04
Tare P11.03 FLT 6917 1b05 15109 3b05 31493 7b05
T-Differential P09.01 FLT 6918 1b06 15110 3b06 31494 7b06
Fuzzy MIN P14.03 FLT 6919 1b07 15111 3b07 31495 7b07
P-Component KP P12.01 FLT 6920 1b08 15112 3b08 31496 7b08
I-Component TN P12.02 FLT 6921 1b09 15113 3b09 31497 7b09
Bypass P12.03 FLT 6922 1b0a 15114 3b0a 31498 7b0a
Controller Magnitu- P12.04 FLT 6923 1b0b 15115 3b0b 31499 7b0b
de Offset
Controller Index P12.18 INT 6924 1b0c 15116 3b0c 31500 7b0c
Linearization Y1 P13.02 FLT 6925 1b0d 15117 3b0d 31501 7b0d
Linearization I1 P13.03 FLT 6926 1b0e 15118 3b0e 31502 7b0e
Linearization Y2 P13.04 FLT 6927 1b0f 15119 3b0f 31503 7b0f

Database

Modbus-TCP


ter
Bypass Adaptation P12.21 FLT 6938 1b1a 15130 3b1a 31514 7b1a
AMOUNTmin P06.05 FLT 6939 1b1b 15131 3b1b 31515 7b1b
F-Min Value P10.05 FLT 6940 1b1c 15132 3b1c 31516 7b1c
Filling Control P06.09 TXT 6941 1b1d 15133 3b1d 31517 7b1d
MDP-Set = 16
ter
Io
Tare P11.03 FLT 6949 1b25 15141 3b25 31525 7b25
de Offset

Database

Modbus-TCP


ter

MDP-Set = 17
ter
Io
Tare P11.03 FLT 6981 1b45 15173 3b45 31557 7b45

Database

Modbus-TCP


ter
de Offset
MDP-Set = 18
ter
Io

Database

Modbus-TCP


ter
Tare P11.03 FLT 7013 1b65 15205 3b65 31589 7b65

de Offset
MDP-Set = 19
ter

Database

Modbus-TCP


ter
Io
Tare P11.03 FLT 7045 1b85 15237 3b85 31621 7b85
de Offset

Database

Modbus-TCP


ter
MDP-Set = 20
ter
Nominal Flow Rate P03.03 FLT 7072 1ba0 15264 3ba0 31648 7ba0
Io
Nominal Amount Fo P03.04 FLT 7073 1ba1 15265 3ba1 31649 7ba1
F_CONTROLmin P06.10 FLT 7074 1ba2 15266 3ba2 31650 7ba2
F_CONTROLmax P06.11 FLT 7075 1ba3 15267 3ba3 31651 7ba3
F-Max Value P10.07 FLT 7076 1ba4 15268 3ba4 31652 7ba4
Tare P11.03 FLT 7077 1ba5 15269 3ba5 31653 7ba5
T-Differential P09.01 FLT 7078 1ba6 15270 3ba6 31654 7ba6
Fuzzy MIN P14.03 FLT 7079 1ba7 15271 3ba7 31655 7ba7
P-Component KP P12.01 FLT 7080 1ba8 15272 3ba8 31656 7ba8
I-Component TN P12.02 FLT 7081 1ba9 15273 3ba9 31657 7ba9
Bypass P12.03 FLT 7082 1baa 15274 3baa 31658 7baa
Controller Magnitu- P12.04 FLT 7083 1bab 15275 3bab 31659 7bab
de Offset
Controller Index P12.18 INT 7084 1bac 15276 3bac 31660 7bac
Linearization Y1 P13.02 FLT 7085 1bad 15277 3bad 31661 7bad
Linearization I1 P13.03 FLT 7086 1bae 15278 3bae 31662 7bae
Linearization Y2 P13.04 FLT 7087 1baf 15279 3baf 31663 7baf
Linearization I2 P13.05 FLT 7088 1bb0 15280 3bb0 31664 7bb0
Linearization Y3 P13.06 FLT 7089 1bb1 15281 3bb1 31665 7bb1
Linearization Y4 P13.08 FLT 7091 1bb3 15283 3bb3 31667 7bb3
Setpoint Range P04.03 FLT 7093 1bb5 15285 3bb5 31669 7bb5

Database

Modbus-TCP


ter
Flow Rate Range P15.06 FLT 7094 1bb6 15286 3bb6 31670 7bb6
Fill Weight Range P15.09 FLT 7095 1bb7 15287 3bb7 31671 7bb7
START Agitator P06.03 FLT 7096 1bb8 15288 3bb8 31672 7bb8
Correction Amount P18.04 FLT 7097 1bb9 15289 3bb9 31673 7bb9
Bypass Adaptation P12.21 FLT 7098 1bba 15290 3bba 31674 7bba
AMOUNTmin P06.05 FLT 7099 1bbb 15291 3bbb 31675 7bbb
F-Min Value P10.05 FLT 7100 1bbc 15292 3bbc 31676 7bbc
Filling Control P06.09 TXT 7101 1bbd 15293 3bbd 31677 7bbd
Tab. 12 : Fieldbus Material Dependent Parameters
3.3.2.1 Material-Dependent Parameters (MDP)

There are only material-dependent parameters in software type VLW. The allocation of parameters in the
basic parameter set to the parameter in the material-dependent set takes place via Parameter Block 35.
Modbus-RTU and Modbus-TCP All other logs
Use ID as data address Read current value (AK=1) Change value (AK=3)
Parameters dec hex dec hex dec hex
MDP Set = 1
Parameter 1 6464 1940 14656 3940 31040 7940
Parameter 2 6465 1941 14657 3941 31041 7941
Parameter 3 6466 1942 14658 3942 31042 7942
Parameter 4 6467 1943 14659 3943 31043 7943
Parameter 5 6468 1944 14660 3944 31044 7944
Parameter 6 6469 1945 14661 3945 31045 7945
Parameter 7 6470 1946 14662 3946 31046 7946
Parameter 8 6471 1947 14663 3947 31047 7947
Parameter 9 6472 1948 14664 3948 31048 7948
Parameter 10 6473 1949 14665 3949 31049 7949
Parameter 11 6474 194a 14666 394a 31050 794a
Parameter 12 6475 194b 14667 394b 31051 794b
Parameter 13 6476 194c 14668 394c 31052 794c

Database
Parameter 14 6477 194d 14669 394d 31053 794d

Parameter 15 6478 194e 14670 394e 31054 794e
Parameter 16 6479 194f 14671 394f 31055 794f
Parameter 17 6480 1950 14672 3950 31056 7950
Parameter 18 6481 1951 14673 3951 31057 7951
Parameter 19 6482 1952 14674 3952 31058 7952
Parameter 20 6483 1953 14675 3953 31059 7953
Parameter 21 6484 1954 14676 3954 31060 7954
Parameter 22 6485 1955 14677 3955 31061 7955
Parameter 23 6486 1956 14678 3956 31062 7956
Parameter 24 6487 1957 14679 3957 31063 7957
Parameter 25 6488 1958 14680 3958 31064 7958
Parameter 26 6489 1959 14681 3959 31065 7959
Parameter 27 6490 195a 14682 395a 31066 795a
Parameter 28 6491 195b 14683 395b 31067 795b
Parameter 29 6492 195c 14684 395c 31068 795c
Parameter 30 6493 195d 14685 395d 31069 795d
MDP Set = 2
Parameter 1 6496 1960 14688 3960 31072 7960
Parameter 2 6497 1961 14689 3961 31073 7961
Parameter 3 6498 1962 14690 3962 31074 7962
Parameter 4 6499 1963 14691 3963 31075 7963
Parameter 5 6500 1964 14692 3964 31076 7964
Parameter 6 6501 1965 14693 3965 31077 7965
Parameter 7 6502 1966 14694 3966 31078 7966
Parameter 8 6503 1967 14695 3967 31079 7967
Parameter 9 6504 1968 14696 3968 31080 7968
Parameter 10 6505 1969 14697 3969 31081 7969
Parameter 11 6506 196a 14698 396a 31082 796a
Parameter 12 6507 196b 14699 396b 31083 796b

Database
Parameter 13 6508 196c 14700 396c 31084 796c

Parameter 14 6509 196d 14701 396d 31085 796d
Parameter 15 6510 196e 14702 396e 31086 796e
Parameter 16 6511 196f 14703 396f 31087 796f
Parameter 17 6512 1970 14704 3970 31088 7970
Parameter 18 6513 1971 14705 3971 31089 7971
Parameter 19 6514 1972 14706 3972 31090 7972
Parameter 20 6515 1973 14707 3973 31091 7973
Parameter 21 6516 1974 14708 3974 31092 7974
Parameter 22 6517 1975 14709 3975 31093 7975
Parameter 23 6518 1976 14710 3976 31094 7976
Parameter 24 6519 1977 14711 3977 31095 7977
Parameter 25 6520 1978 14712 3978 31096 7978
Parameter 26 6521 1979 14713 3979 31097 7979
Parameter 27 6522 197a 14714 397a 31098 797a
Parameter 28 6523 197b 14715 397b 31099 797b
Parameter 29 6524 197c 14716 397c 31100 797c
Parameter 30 6525 197d 14717 397d 31101 797d
MDP Set = 3
Parameter 1 6528 1980 14720 3980 31104 7980
Parameter 2 6529 1981 14721 3981 31105 7981
Parameter 3 6530 1982 14722 3982 31106 7982
Parameter 4 6531 1983 14723 3983 31107 7983
Parameter 5 6532 1984 14724 3984 31108 7984
Parameter 6 6533 1985 14725 3985 31109 7985
Parameter 7 6534 1986 14726 3986 31110 7986
Parameter 8 6535 1987 14727 3987 31111 7987
Parameter 9 6536 1988 14728 3988 31112 7988
Parameter 10 6537 1989 14729 3989 31113 7989
Parameter 11 6538 198a 14730 398a 31114 798a

Database
Parameter 12 6539 198b 14731 398b 31115 798b

Parameter 13 6540 198c 14732 398c 31116 798c
Parameter 14 6541 198d 14733 398d 31117 798d
Parameter 15 6542 198e 14734 398e 31118 798e
Parameter 16 6543 198f 14735 398f 31119 798f
Parameter 17 6544 1990 14736 3990 31120 7990
Parameter 18 6545 1991 14737 3991 31121 7991
Parameter 19 6546 1992 14738 3992 31122 7992
Parameter 20 6547 1993 14739 3993 31123 7993
Parameter 21 6548 1994 14740 3994 31124 7994
Parameter 22 6549 1995 14741 3995 31125 7995
Parameter 23 6550 1996 14742 3996 31126 7996
Parameter 24 6551 1997 14743 3997 31127 7997
Parameter 25 6552 1998 14744 3998 31128 7998
Parameter 26 6553 1999 14745 3999 31129 7999
Parameter 27 6554 199a 14746 399a 31130 799a
Parameter 28 6555 199b 14747 399b 31131 799b
Parameter 29 6556 199c 14748 399c 31132 799c
Parameter 30 6557 199d 14749 399d 31133 799d
MDP Set = 4
Parameter 1 6560 19a0 14752 39a0 31136 79a0
Parameter 2 6561 19a1 14753 39a1 31137 79a1
Parameter 3 6562 19a2 14754 39a2 31138 79a2
Parameter 4 6563 19a3 14755 39a3 31139 79a3
Parameter 5 6564 19a4 14756 39a4 31140 79a4
Parameter 6 6565 19a5 14757 39a5 31141 79a5
Parameter 7 6566 19a6 14758 39a6 31142 79a6
Parameter 8 6567 19a7 14759 39a7 31143 79a7
Parameter 9 6568 19a8 14760 39a8 31144 79a8
Parameter 10 6569 19a9 14761 39a9 31145 79a9

Database
Parameter 11 6570 19aa 14762 39aa 31146 79aa

Parameter 12 6571 19ab 14763 39ab 31147 79ab
Parameter 13 6572 19ac 14764 39ac 31148 79ac
Parameter 14 6573 19ad 14765 39ad 31149 79ad
Parameter 15 6574 19ae 14766 39ae 31150 79ae
Parameter 16 6575 19af 14767 39af 31151 79af
Parameter 17 6576 19b0 14768 39b0 31152 79b0
Parameter 18 6577 19b1 14769 39b1 31153 79b1
Parameter 19 6578 19b2 14770 39b2 31154 79b2
Parameter 20 6579 19b3 14771 39b3 31155 79b3
Parameter 21 6580 19b4 14772 39b4 31156 79b4
Parameter 22 6581 19b5 14773 39b5 31157 79b5
Parameter 23 6582 19b6 14774 39b6 31158 79b6
Parameter 24 6583 19b7 14775 39b7 31159 79b7
Parameter 25 6584 19b8 14776 39b8 31160 79b8
Parameter 26 6585 19b9 14777 39b9 31161 79b9
Parameter 27 6586 19ba 14778 39ba 31162 79ba
Parameter 28 6587 19bb 14779 39bb 31163 79bb
Parameter 29 6588 19bc 14780 39bc 31164 79bc
Parameter 30 6589 19bd 14781 39bd 31165 79bd
MDP Set = 5
Parameter 1 6592 19c0 14784 39c0 31168 79c0
Parameter 2 6593 19c1 14785 39c1 31169 79c1
Parameter 3 6594 19c2 14786 39c2 31170 79c2
Parameter 4 6595 19c3 14787 39c3 31171 79c3
Parameter 5 6596 19c4 14788 39c4 31172 79c4
Parameter 6 6597 19c5 14789 39c5 31173 79c5
Parameter 7 6598 19c6 14790 39c6 31174 79c6
Parameter 8 6599 19c7 14791 39c7 31175 79c7
Parameter 9 6600 19c8 14792 39c8 31176 79c8

Database
Parameter 10 6601 19c9 14793 39c9 31177 79c9

Parameter 11 6602 19ca 14794 39ca 31178 79ca
Parameter 12 6603 19cb 14795 39cb 31179 79cb
Parameter 13 6604 19cc 14796 39cc 31180 79cc
Parameter 14 6605 19cd 14797 39cd 31181 79cd
Parameter 15 6606 19ce 14798 39ce 31182 79ce
Parameter 16 6607 19cf 14799 39cf 31183 79cf
Parameter 17 6608 19d0 14800 39d0 31184 79d0
Parameter 18 6609 19d1 14801 39d1 31185 79d1
Parameter 19 6610 19d2 14802 39d2 31186 79d2
Parameter 20 6611 19d3 14803 39d3 31187 79d3
Parameter 21 6612 19d4 14804 39d4 31188 79d4
Parameter 22 6613 19d5 14805 39d5 31189 79d5
Parameter 23 6614 19d6 14806 39d6 31190 79d6
Parameter 24 6615 19d7 14807 39d7 31191 79d7
Parameter 25 6616 19d8 14808 39d8 31192 79d8
Parameter 26 6617 19d9 14809 39d9 31193 79d9
Parameter 27 6618 19da 14810 39da 31194 79da
Parameter 28 6619 19db 14811 39db 31195 79db
Parameter 29 6620 19dc 14812 39dc 31196 79dc
Parameter 30 6621 19dd 14813 39dd 31197 79dd
MDP Set = 6
Parameter 1 6624 19e0 14816 39e0 31200 79e0
Parameter 2 6625 19e1 14817 39e1 31201 79e1
Parameter 3 6626 19e2 14818 39e2 31202 79e2
Parameter 4 6627 19e3 14819 39e3 31203 79e3
Parameter 5 6628 19e4 14820 39e4 31204 79e4
Parameter 6 6629 19e5 14821 39e5 31205 79e5
Parameter 7 6630 19e6 14822 39e6 31206 79e6
Parameter 8 6631 19e7 14823 39e7 31207 79e7

Database
Parameter 9 6632 19e8 14824 39e8 31208 79e8

Parameter 10 6633 19e9 14825 39e9 31209 79e9
Parameter 11 6634 19ea 14826 39ea 31210 79ea
Parameter 12 6635 19eb 14827 39eb 31211 79eb
Parameter 13 6636 19ec 14828 39ec 31212 79ec
Parameter 14 6637 19ed 14829 39ed 31213 79ed
Parameter 15 6638 19ee 14830 39ee 31214 79ee
Parameter 16 6639 19ef 14831 39ef 31215 79ef
Parameter 17 6640 19f0 14832 39f0 31216 79f0
Parameter 18 6641 19f1 14833 39f1 31217 79f1
Parameter 19 6642 19f2 14834 39f2 31218 79f2
Parameter 20 6643 19f3 14835 39f3 31219 79f3
Parameter 21 6644 19f4 14836 39f4 31220 79f4
Parameter 22 6645 19f5 14837 39f5 31221 79f5
Parameter 23 6646 19f6 14838 39f6 31222 79f6
Parameter 24 6647 19f7 14839 39f7 31223 79f7
Parameter 25 6648 19f8 14840 39f8 31224 79f8
Parameter 26 6649 19f9 14841 39f9 31225 79f9
Parameter 27 6650 19fa 14842 39fa 31226 79fa
Parameter 28 6651 19fb 14843 39fb 31227 79fb
Parameter 29 6652 19fc 14844 39fc 31228 79fc
Parameter 30 6653 19fd 14845 39fd 31229 79fd
MDP Set = 7
Parameter 1 6656 1a00 14848 3a00 31232 7a00
Parameter 2 6657 1a01 14849 3a01 31233 7a01
Parameter 3 6658 1a02 14850 3a02 31234 7a02
Parameter 4 6659 1a03 14851 3a03 31235 7a03
Parameter 5 6660 1a04 14852 3a04 31236 7a04
Parameter 6 6661 1a05 14853 3a05 31237 7a05
Parameter 7 6662 1a06 14854 3a06 31238 7a06

Database
Parameter 8 6663 1a07 14855 3a07 31239 7a07

Parameter 9 6664 1a08 14856 3a08 31240 7a08
Parameter 10 6665 1a09 14857 3a09 31241 7a09
Parameter 11 6666 1a0a 14858 3a0a 31242 7a0a
Parameter 12 6667 1a0b 14859 3a0b 31243 7a0b
Parameter 13 6668 1a0c 14860 3a0c 31244 7a0c
Parameter 14 6669 1a0d 14861 3a0d 31245 7a0d
Parameter 15 6670 1a0e 14862 3a0e 31246 7a0e
Parameter 16 6671 1a0f 14863 3a0f 31247 7a0f
Parameter 17 6672 1a10 14864 3a10 31248 7a10
Parameter 18 6673 1a11 14865 3a11 31249 7a11
Parameter 19 6674 1a12 14866 3a12 31250 7a12
Parameter 20 6675 1a13 14867 3a13 31251 7a13
Parameter 21 6676 1a14 14868 3a14 31252 7a14
Parameter 22 6677 1a15 14869 3a15 31253 7a15
Parameter 23 6678 1a16 14870 3a16 31254 7a16
Parameter 24 6679 1a17 14871 3a17 31255 7a17
Parameter 25 6680 1a18 14872 3a18 31256 7a18
Parameter 26 6681 1a19 14873 3a19 31257 7a19
MDP Set = 8
Parameter 1 6688 1a20 14880 3a20 31264 7a20
Parameter 2 6689 1a21 14881 3a21 31265 7a21
Parameter 3 6690 1a22 14882 3a22 31266 7a22
Parameter 4 6691 1a23 14883 3a23 31267 7a23
Parameter 5 6692 1a24 14884 3a24 31268 7a24
Parameter 6 6693 1a25 14885 3a25 31269 7a25

Database
Parameter 7 6694 1a26 14886 3a26 31270 7a26

Parameter 8 6695 1a27 14887 3a27 31271 7a27
Parameter 9 6696 1a28 14888 3a28 31272 7a28
Parameter 10 6697 1a29 14889 3a29 31273 7a29
Parameter 17 6704 1a30 14896 3a30 31280 7a30
Parameter 18 6705 1a31 14897 3a31 31281 7a31
Parameter 19 6706 1a32 14898 3a32 31282 7a32
Parameter 20 6707 1a33 14899 3a33 31283 7a33
Parameter 21 6708 1a34 14900 3a34 31284 7a34
Parameter 22 6709 1a35 14901 3a35 31285 7a35
Parameter 23 6710 1a36 14902 3a36 31286 7a36
Parameter 24 6711 1a37 14903 3a37 31287 7a37
Parameter 25 6712 1a38 14904 3a38 31288 7a38
Parameter 26 6713 1a39 14905 3a39 31289 7a39
MDP Set = 9
Parameter 1 6720 1a40 14912 3a40 31296 7a40
Parameter 2 6721 1a41 14913 3a41 31297 7a41
Parameter 3 6722 1a42 14914 3a42 31298 7a42
Parameter 4 6723 1a43 14915 3a43 31299 7a43
Parameter 5 6724 1a44 14916 3a44 31300 7a44

Database
Parameter 6 6725 1a45 14917 3a45 31301 7a45

Parameter 7 6726 1a46 14918 3a46 31302 7a46
Parameter 8 6727 1a47 14919 3a47 31303 7a47
Parameter 9 6728 1a48 14920 3a48 31304 7a48
Parameter 10 6729 1a49 14921 3a49 31305 7a49
Parameter 17 6736 1a50 14928 3a50 31312 7a50
Parameter 18 6737 1a51 14929 3a51 31313 7a51
Parameter 19 6738 1a52 14930 3a52 31314 7a52
Parameter 20 6739 1a53 14931 3a53 31315 7a53
Parameter 21 6740 1a54 14932 3a54 31316 7a54
Parameter 22 6741 1a55 14933 3a55 31317 7a55
Parameter 23 6742 1a56 14934 3a56 31318 7a56
Parameter 24 6743 1a57 14935 3a57 31319 7a57
Parameter 25 6744 1a58 14936 3a58 31320 7a58
Parameter 26 6745 1a59 14937 3a59 31321 7a59
MDP Set = 10
Parameter 1 6752 1a60 14944 3a60 31328 7a60
Parameter 2 6753 1a61 14945 3a61 31329 7a61
Parameter 3 6754 1a62 14946 3a62 31330 7a62
Parameter 4 6755 1a63 14947 3a63 31331 7a63

Database
Parameter 5 6756 1a64 14948 3a64 31332 7a64

Parameter 6 6757 1a65 14949 3a65 31333 7a65
Parameter 7 6758 1a66 14950 3a66 31334 7a66
Parameter 8 6759 1a67 14951 3a67 31335 7a67
Parameter 9 6760 1a68 14952 3a68 31336 7a68
Parameter 10 6761 1a69 14953 3a69 31337 7a69
Parameter 17 6768 1a70 14960 3a70 31344 7a70
Parameter 18 6769 1a71 14961 3a71 31345 7a71
Parameter 19 6770 1a72 14962 3a72 31346 7a72
Parameter 20 6771 1a73 14963 3a73 31347 7a73
Parameter 21 6772 1a74 14964 3a74 31348 7a74
Parameter 22 6773 1a75 14965 3a75 31349 7a75
Parameter 23 6774 1a76 14966 3a76 31350 7a76
Parameter 24 6775 1a77 14967 3a77 31351 7a77
Parameter 25 6776 1a78 14968 3a78 31352 7a78
Parameter 26 6777 1a79 14969 3a79 31353 7a79
MDP Set = 11
Parameter 1 6784 1a80 14976 3a80 31360 7a80
Parameter 2 6785 1a81 14977 3a81 31361 7a81
Parameter 3 6786 1a82 14978 3a82 31362 7a82

Database
Parameter 4 6787 1a83 14979 3a83 31363 7a83

Parameter 5 6788 1a84 14980 3a84 31364 7a84
Parameter 6 6789 1a85 14981 3a85 31365 7a85
Parameter 7 6790 1a86 14982 3a86 31366 7a86
Parameter 8 6791 1a87 14983 3a87 31367 7a87
Parameter 9 6792 1a88 14984 3a88 31368 7a88
Parameter 10 6793 1a89 14985 3a89 31369 7a89
Parameter 17 6800 1a90 14992 3a90 31376 7a90
Parameter 18 6801 1a91 14993 3a91 31377 7a91
Parameter 19 6802 1a92 14994 3a92 31378 7a92
Parameter 20 6803 1a93 14995 3a93 31379 7a93
Parameter 21 6804 1a94 14996 3a94 31380 7a94
Parameter 22 6805 1a95 14997 3a95 31381 7a95
Parameter 23 6806 1a96 14998 3a96 31382 7a96
Parameter 24 6807 1a97 14999 3a97 31383 7a97
Parameter 25 6808 1a98 15000 3a98 31384 7a98
Parameter 26 6809 1a99 15001 3a99 31385 7a99
MDP Set = 12
Parameter 1 6816 1aa0 15008 3aa0 31392 7aa0

Database

Parameter 11 6826 1aaa 15018 3aaa 31402 7aaa
Parameter 12 6827 1aab 15019 3aab 31403 7aab
Parameter 13 6828 1aac 15020 3aac 31404 7aac
Parameter 14 6829 1aad 15021 3aad 31405 7aad
Parameter 15 6830 1aae 15022 3aae 31406 7aae
Parameter 16 6831 1aaf 15023 3aaf 31407 7aaf
Parameter 17 6832 1ab0 15024 3ab0 31408 7ab0
Parameter 27 6842 1aba 15034 3aba 31418 7aba
Parameter 28 6843 1abb 15035 3abb 31419 7abb
Parameter 29 6844 1abc 15036 3abc 31420 7abc
Parameter 30 6845 1abd 15037 3abd 31421 7abd
MDP Set = 13
Parameter 1 6848 1ac0 15040 3ac0 31424 7ac0

Database

Parameter 11 6858 1aca 15050 3aca 31434 7aca
Parameter 12 6859 1acb 15051 3acb 31435 7acb
Parameter 13 6860 1acc 15052 3acc 31436 7acc
Parameter 14 6861 1acd 15053 3acd 31437 7acd
Parameter 15 6862 1ace 15054 3ace 31438 7ace
Parameter 16 6863 1acf 15055 3acf 31439 7acf
Parameter 17 6864 1ad0 15056 3ad0 31440 7ad0
Parameter 27 6874 1ada 15066 3ada 31450 7ada
Parameter 28 6875 1adb 15067 3adb 31451 7adb
Parameter 29 6876 1adc 15068 3adc 31452 7adc
Parameter 30 6877 1add 15069 3add 31453 7add
MDP Set = 14

Database
Parameter 1 6880 1ae0 15072 3ae0 31456 7ae0

Parameter 11 6890 1aea 15082 3aea 31466 7aea
Parameter 12 6891 1aeb 15083 3aeb 31467 7aeb
Parameter 13 6892 1aec 15084 3aec 31468 7aec
Parameter 14 6893 1aed 15085 3aed 31469 7aed
Parameter 15 6894 1aee 15086 3aee 31470 7aee
Parameter 16 6895 1aef 15087 3aef 31471 7aef
Parameter 17 6896 1af0 15088 3af0 31472 7af0
Parameter 27 6906 1afa 15098 3afa 31482 7afa
Parameter 28 6907 1afb 15099 3afb 31483 7afb
Parameter 29 6908 1afc 15100 3afc 31484 7afc
Parameter 30 6909 1afd 15101 3afd 31485 7afd

Database
MDP Set = 15
Parameter 1 6912 1b00 15104 3b00 31488 7b00
Parameter 2 6913 1b01 15105 3b01 31489 7b01
Parameter 3 6914 1b02 15106 3b02 31490 7b02
Parameter 4 6915 1b03 15107 3b03 31491 7b03
Parameter 5 6916 1b04 15108 3b04 31492 7b04
Parameter 6 6917 1b05 15109 3b05 31493 7b05
Parameter 7 6918 1b06 15110 3b06 31494 7b06
Parameter 8 6919 1b07 15111 3b07 31495 7b07
Parameter 9 6920 1b08 15112 3b08 31496 7b08
Parameter 10 6921 1b09 15113 3b09 31497 7b09
Parameter 11 6922 1b0a 15114 3b0a 31498 7b0a
Parameter 12 6923 1b0b 15115 3b0b 31499 7b0b
Parameter 13 6924 1b0c 15116 3b0c 31500 7b0c
Parameter 14 6925 1b0d 15117 3b0d 31501 7b0d
Parameter 15 6926 1b0e 15118 3b0e 31502 7b0e
Parameter 16 6927 1b0f 15119 3b0f 31503 7b0f
Parameter 17 6928 1b10 15120 3b10 31504 7b10
Parameter 18 6929 1b11 15121 3b11 31505 7b11
Parameter 19 6930 1b12 15122 3b12 31506 7b12
Parameter 20 6931 1b13 15123 3b13 31507 7b13
Parameter 21 6932 1b14 15124 3b14 31508 7b14
Parameter 22 6933 1b15 15125 3b15 31509 7b15
Parameter 23 6934 1b16 15126 3b16 31510 7b16
Parameter 24 6935 1b17 15127 3b17 31511 7b17
Parameter 25 6936 1b18 15128 3b18 31512 7b18
Parameter 26 6937 1b19 15129 3b19 31513 7b19

Database
MDP Set = 16
Parameter 1 6944 1b20 15136 3b20 31520 7b20
Parameter 2 6945 1b21 15137 3b21 31521 7b21
Parameter 3 6946 1b22 15138 3b22 31522 7b22
Parameter 4 6947 1b23 15139 3b23 31523 7b23
Parameter 5 6948 1b24 15140 3b24 31524 7b24
Parameter 6 6949 1b25 15141 3b25 31525 7b25
Parameter 7 6950 1b26 15142 3b26 31526 7b26
Parameter 8 6951 1b27 15143 3b27 31527 7b27
Parameter 9 6952 1b28 15144 3b28 31528 7b28
Parameter 10 6953 1b29 15145 3b29 31529 7b29
Parameter 17 6960 1b30 15152 3b30 31536 7b30
Parameter 18 6961 1b31 15153 3b31 31537 7b31
Parameter 19 6962 1b32 15154 3b32 31538 7b32
Parameter 20 6963 1b33 15155 3b33 31539 7b33
Parameter 21 6964 1b34 15156 3b34 31540 7b34
Parameter 22 6965 1b35 15157 3b35 31541 7b35
Parameter 23 6966 1b36 15158 3b36 31542 7b36
Parameter 24 6967 1b37 15159 3b37 31543 7b37
Parameter 25 6968 1b38 15160 3b38 31544 7b38
Parameter 26 6969 1b39 15161 3b39 31545 7b39

Database
MDP Set = 17
Parameter 1 6976 1b40 15168 3b40 31552 7b40
Parameter 2 6977 1b41 15169 3b41 31553 7b41
Parameter 3 6978 1b42 15170 3b42 31554 7b42
Parameter 4 6979 1b43 15171 3b43 31555 7b43
Parameter 5 6980 1b44 15172 3b44 31556 7b44
Parameter 6 6981 1b45 15173 3b45 31557 7b45
Parameter 7 6982 1b46 15174 3b46 31558 7b46
Parameter 8 6983 1b47 15175 3b47 31559 7b47
Parameter 9 6984 1b48 15176 3b48 31560 7b48
Parameter 10 6985 1b49 15177 3b49 31561 7b49
Parameter 17 6992 1b50 15184 3b50 31568 7b50
Parameter 18 6993 1b51 15185 3b51 31569 7b51
Parameter 19 6994 1b52 15186 3b52 31570 7b52
Parameter 20 6995 1b53 15187 3b53 31571 7b53
Parameter 21 6996 1b54 15188 3b54 31572 7b54
Parameter 22 6997 1b55 15189 3b55 31573 7b55
Parameter 23 6998 1b56 15190 3b56 31574 7b56
Parameter 24 6999 1b57 15191 3b57 31575 7b57
Parameter 25 7000 1b58 15192 3b58 31576 7b58
Parameter 26 7001 1b59 15193 3b59 31577 7b59

Database

MDP Set = 18
Parameter 1 7008 1b60 15200 3b60 31584 7b60
Parameter 2 7009 1b61 15201 3b61 31585 7b61
Parameter 3 7010 1b62 15202 3b62 31586 7b62
Parameter 4 7011 1b63 15203 3b63 31587 7b63
Parameter 5 7012 1b64 15204 3b64 31588 7b64
Parameter 6 7013 1b65 15205 3b65 31589 7b65
Parameter 7 7014 1b66 15206 3b66 31590 7b66
Parameter 8 7015 1b67 15207 3b67 31591 7b67
Parameter 9 7016 1b68 15208 3b68 31592 7b68
Parameter 10 7017 1b69 15209 3b69 31593 7b69
Parameter 17 7024 1b70 15216 3b70 31600 7b70
Parameter 18 7025 1b71 15217 3b71 31601 7b71
Parameter 19 7026 1b72 15218 3b72 31602 7b72
Parameter 20 7027 1b73 15219 3b73 31603 7b73
Parameter 21 7028 1b74 15220 3b74 31604 7b74
Parameter 22 7029 1b75 15221 3b75 31605 7b75
Parameter 23 7030 1b76 15222 3b76 31606 7b76
Parameter 24 7031 1b77 15223 3b77 31607 7b77
Parameter 25 7032 1b78 15224 3b78 31608 7b78
Parameter 26 7033 1b79 15225 3b79 31609 7b79

Database

MDP Set = 19
Parameter 1 7040 1b80 15232 3b80 31616 7b80
Parameter 2 7041 1b81 15233 3b81 31617 7b81
Parameter 3 7042 1b82 15234 3b82 31618 7b82
Parameter 4 7043 1b83 15235 3b83 31619 7b83
Parameter 5 7044 1b84 15236 3b84 31620 7b84
Parameter 6 7045 1b85 15237 3b85 31621 7b85
Parameter 7 7046 1b86 15238 3b86 31622 7b86
Parameter 8 7047 1b87 15239 3b87 31623 7b87
Parameter 9 7048 1b88 15240 3b88 31624 7b88
Parameter 10 7049 1b89 15241 3b89 31625 7b89
Parameter 17 7056 1b90 15248 3b90 31632 7b90
Parameter 18 7057 1b91 15249 3b91 31633 7b91
Parameter 19 7058 1b92 15250 3b92 31634 7b92
Parameter 20 7059 1b93 15251 3b93 31635 7b93
Parameter 21 7060 1b94 15252 3b94 31636 7b94
Parameter 22 7061 1b95 15253 3b95 31637 7b95
Parameter 23 7062 1b96 15254 3b96 31638 7b96
Parameter 24 7063 1b97 15255 3b97 31639 7b97
Parameter 25 7064 1b98 15256 3b98 31640 7b98
Parameter 26 7065 1b99 15257 3b99 31641 7b99

Database

MDP Set = 20
Parameter 1 7072 1ba0 15264 3ba0 31648 7ba0
Parameter 11 7082 1baa 15274 3baa 31658 7baa
Parameter 12 7083 1bab 15275 3bab 31659 7bab
Parameter 13 7084 1bac 15276 3bac 31660 7bac
Parameter 14 7085 1bad 15277 3bad 31661 7bad
Parameter 15 7086 1bae 15278 3bae 31662 7bae
Parameter 16 7087 1baf 15279 3baf 31663 7baf
Parameter 17 7088 1bb0 15280 3bb0 31664 7bb0

Database

Parameter 27 7098 1bba 15290 3bba 31674 7bba
Parameter 28 7099 1bbb 15291 3bbb 31675 7bbb
Parameter 29 7100 1bbc 15292 3bbc 31676 7bbc
Parameter 30 7101 1bbd 15293 3bbd 31677 7bbd
Tab. 13 : Material-Dependent Parameters
3.3.3 Events - Overview
Software
Code Event VLW VWF VBW VMC VSF VIF VBC
SY System message
SY01 Event: Memory Error P08.15 P07.09 P07.06 P07.14 P07.14 P07.14 P07.06
SY02 Event: Communica- P01.06 P01.06 P01.06 P01.06 P01.06 P01.06 P01.06
tion VCU20100-Unit
2
tion VCU20100-Unit
3
tion HMI 1
tion HMI 2
tion HMI 3
tion VHM serial
SY08 Event: Cycl. com- P21.03 P20.03 P19.03 P18.03 P16.03 P18.03 P16.03
munication
SY09
SY10 Event: Acyclical P21.04 P20.04 P19.04 P18.04 P16.04 P18.04 P16.04
communication
SY11
SY12

Database
Software
SY13 Event: Bluetooth P05.12

connection interrup-
ted
SY14
tion VMO20100-Unit
1
tion VMO20100-Unit
2
SC Sequence monito-
ring
SC01 Event: Setpoint li- P08.07 P07.07 P07.06 P07.07 P07.06
mited
SC02 Event: Standby P08.01 P07.01 P07.01 P07.01 P07.01
SC03 Event: Scale ON P19.04 P16.04 P15.04 P16.04 P14.04 P16.04 P14.04
SC04 Event: Voltage ON P19.02 P16.02 P15.02 P16.02 P14.02 P16.02 P14.02
SC05 Event: External P16.01 P13.01 P12.01 P13.01 P12.01 P13.01 P12.03
event 1
event 2
SC07 Event: DAE active P14.09
SC08 Event: DAE fault P14.10
SC09 Event: Flap return P06.16 P06.16
signal
SC10 Event: T_Volum. P06.23 P06.04
event 3
event 4
SC13 Event: Discharge P07.05
gate
SC14 Event: Time flap P06.18
OPEN > MAX
SC15 Event: Batching time P06.20
> MAX

Database
Software
SC16 Event: Direction of P36.37

rotation
WE Electrical equipment
WE01 Event: Power failure P08.08 P07.08 P07.05 P07.07 P07.08 P07.07 P07.05
WE02 Event: NAMUR error P16.09 P13.13 P12.11 P13.09 P12.13 P13.09 P12.12
VCU1-DI6
WE03 Event: NAMUR error P16.10 P13.14 P12.12 P13.10 P12.14 P13.10 P12.13
VCU1-DI7
WE04 Event: NAMUR error P16.11 P13.15 P12.13 P13.11 P12.15 P13.11
VCU2-DI6
VCU2-DI7
VCU3-DI6
VCU3-DI7
WE08 Event: Analog input P08.16 P07.12 P07.07 P07.15 P07.15 P07.15
< offset
WE09
WE10
WE11
WE12
WE13 Event: NAMUR error P16.30 P13.24 P12.22 P13.21
VMO1-DI7
WE14 Event: NAMUR error P16.31 P13.25 P12.23 P13.22
VMO2-DI7
WE15
WE16
WM Mechanical
equipment
WM01 Event: Limit switch P13.22 P12.20
WM02 Event: Belt creep P18.12 P17.12
WM03 Event: Procedure P18.10 P17.10

Database
Software
WM04 Event: Off-track run- P18.08 P17.08

ning
WM05 Event: Slippage 2 P34.08 P30.08
WM06 Event: Scraper P06.10
WM07
WM08
WM09 Event: Motor Start P36.31
WM10
WM11
WM12
WM13 Event: Agitator over- P28.16
load
WM14 Event: Conveying air P36.35
MAX
WM15 Event: Drive blocked P36.36
WM16 Event: Motor protec- P36.32
tive switch
MF Material flow
MF01
MF02
MF03 Event: Conveying air P32.06 P36.34
MIN
MF04 Event: Sealing air P32.04 P36.33
MIN
MF05 Event: Moisture P30.10 P27.10 P27.10 P23.10 P25.10
MAX
MF06 Event: Out of tole- P18.21 P15.15 P14.15 P15.15 P15.21
rance
MF07 Event: Batch set- P18.25 P15.19 P14.19 P15.17 P15.25
point limit
MF08 Event: Communica- P01.17
tion VVC
MF09 Event: No No-motion P06.03
MF10 Event: Tolerance P06.04
exceeded

Database
Software
MF11 Event: Tolerance P06.05

undercut
MF12 Event: Material P18.22 P06.10
quantity
MF13 Event: Temperature P31.08
MAX
MF14
MF15 Event: Pressure P32.24
blower
MF16 Event: Pressure P31.13
monitoring
IL Locking mechanism
IL01 Event: No release P04.06 P04.04 P04.03 P04.06 P04.06 P04.06 P04.08
IL02 Event: Mechanical P29.10 P24.10 P23.10 P33.10 P19.10 P28.10 P22.10
equipment
IL03 Event: Electrical P29.12 P24.12 P23.12 P33.12 P19.12 P28.12 P22.12
equipment
IL04 Event: Mechatronics P29.15 P24.15 P23.15 P33.15 P19.15 P28.15 P22.15
IL05 Event: Not ready P29.17 P24.17 P23.17 P33.17 P19.17 P28.17 P22.17
IL06 Event: Not ready to P29.19 P24.19 P23.19 P33.19 P19.19 P28.19 P22.19
switch on
IL07 Event: Communic.
Bluetooth channel 1
IL08 Event: Communic.
Bluetooth channel 2
IL09 Event: Filling blo- P07.17
cked
IL10 Event: FKB error P27.22 P36.22 P32.22 P34.22 P31.22 P29.22 P20.22
IL11 Event: Incorrect P19.05 P16.05 P15.05 P16.05 P14.05 P16.05 P14.05
system time
IL12
IL13
IL14
IL15
IL16

Database
Software
CO Control system
CO01 Event: Control sys- P08.14 P11.10 P07.13 P07.13
tem limited
CO02 Event: Distributor P33.07 P40.09 P34.09
position MIN
CO03 Event: Distributor P33.09 40.11 P34.11
position MAX
CO04 Event: Fill-level MAX P25.29 P26.29 P24.29 P22.29 P20.29 P22.29
sensor
CO05 Event: Volum. be- P06.17
cause of load cell
error
CO06 Event: Distributor P23.40 P23.40
position MAX (B)
CO07
CO08
CO09
CO10 Event: Distributor P23.38
position MIN (B)
CO11 Event: Correction P22.46
MAX
CO12 Event: Limiter range P22.49
CO13 Event: Vibration P08.17
controller VVC
CO14
CO15
CO16
CH Check measurement
system
CH01 Event: Check quanti- P29.16 P26.16 P22.17
ty too little
CH02 Event: Check fill P29.18 P26.18 P25.15 P22.19 P24.14
level too little

Database
Software
CH03 Event: Check fill P29.20 P26.20 P25.17 P22.21 P24.16

level too large
CH04 Event: Correction P29.32 P26.32 P25.28 P22.32 P24.27
error tare value ab-
solute
error tare value rela-
tive
error range absolute
error range relative
CH08 Event: Conveying P29.25 P26.25 P25.21 P22.25 P24.20
element not off
CH09 Event: Control P29.06 P26.06 P25.07 P22.07 P24.06
measurement: No
release
CH10 Event: Prepare P29.26 P26.26 P25.22 P22.26 P24.21
check
CH11 Event: Wait for ack- P29.28 P26.28 P25.24 P22.28 P24.23
nowledgement
CH12 Event: Control flap P29.42 P26.42 P25.38 P22.42 P24.37
CH13 Event: Vessel fault P29.44 P26.44 P25.40 P22.44 P24.39
CH14 Event: CO-Alarm P26.02
Tube
CH15 Event: Min KME P26.10
setpoint
CH16 Event: Limiter tare P22.52
value
CA Adjustment
CA01 Event: Error load cell P08.04 P07.04 P07.02 P07.04 P07.04 P07.03 P07.01
input
CA02 Event: Tachometer P08.03 P07.03 P07.01 P07.03 P07.03
input
CA03 Event: Error load cell P25.07 P26.07 P24.07 P22.07 P20.07 P22.07
input (vessel)

Database
Software
CA04 Event: Error LC input P28.07

(2nd platform)
CA05 Event: Linearization P13.10 P32.10 P29.10 P39.10 P33.10
CA06 Event: Tare value P06.13 P06.07 P28.03 P26.03
correction
CA07 Event: DMS input P35.06 P31.06 P29.06 P25.06
CA08 Event: Capacity P11.09
adjustment
CA09
CA10 Event: Error LC input P24.05
(FGK)
CA11
CA12
CA13
CA14
CA15 Event: Error load cell P24.09
input (2nd vessel)
CA16 Event: LC input > P24.10
MAX (2nd vessel)
HI Maximum
HI01 Event: LC Input > P08.06 P07.06 P07.04 P07.05 P07.06 P07.05 P07.03
MAX
HI02 Event: Actual feedra- P10.04 P09.04 P09.04 P09.04 P09.04 P09.04 P09.04
te MAX
HI03 Event: Load MAX P09.08 P09.08 P09.08
HI04 Event: Belt speed P09.12 P09.12
MAX
HI05 Event: Deviation P08.13 P11.09 P07.12 P07.13 P07.12
HI06 Event: Fill level Max P10.08 P09.08
HI07 Event: Rotational P10.12 P09.12
speed max.
HI08 Event: Feed hopper P03.05 P07.04
over-filled
HI09 Event: Max. measu- P09.06
ring load

Database
Software
HI10 Event: LC input > P25.08 P26.08 P24.08 P22.08 P20.08 P22.08
MAX (vessel)
HI11 Event: Vessel MAX P25.19 P26.19 P24.19 P22.19 P20.19 P22.19
HI12 Event: 2nd platform P28.12
MAX
HI13 Event: FC-MAX limit P30.17 P32.18 P29.13
HI14 Event: DMS input > P35.07 P31.07 P29.07 P25.07
MAX
HI15 Event: MAX (2nd P24.21
vessel)
HI16 Event: Pressure P35.15 P31.15 P29.15 P25.15
MAX
LO Minimum
LO01 Event: LC Input < P08.05 P07.05 P07.03 P07.05 P07.04 P07.02
MIN
LO02 Event: Actual feedra- P10.02 P09.02 P09.02 P09.02 P09.02 P09.02 P09.02
te MIN
LO03 Event: Load MIN P09.06 P09.06 P09.06
LO04 Event: Belt speed P09.10 P09.10
MIN
LO05
LO06 Event: Fill level min. P10.06 P09.06
LO07 Event: Rotational P10.10 P09.08 P09.10
speed min.
LO08 Event: Fill level MIN P06.08
LO09 Event: Vessel MIN P24.18
LO10 Event: DMS input < P35.08 P31.08 P29.08 P25.08
MIN
LO11 Event: MIN (2nd P25.16 P26.16 P24.16 P22.16 P20.16 P22.16
vessel)
LO12 Event: 2nd platform P28.09
MIN
LO13 Event: FC-MIN limit P30.16 P32.17 P29.12
LO14 Event: FC speed < P30.15
MIN

Database
Software
LO15
LO16 Event: Pressure MIN P35.12 P31.12 P29.12 P25.12
Tab. 14 : Event overview

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 baudrate and is between 100 ... 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 determin-
ing 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. Set the device parameters.
Important: The transmission of modified parameters to the interface card can take up to 30 s!
Control: the led 'Status' (H110 above or H120 above) on the interface card VPB 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 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 (VHM) and the 'EasyServe' service tool. The
parameter description applies to both options.
NOTE: Detailed description of the parameters:

Refer to chapter 'Parameter' in the DISOCONT Tersus operating manual
Settings in the 'Fieldbus Communication' block
Parameter Value range Default va- Explanation

lue
Protocol Ty- NO NO Selects the protocol

1)
pe Modbus-RTU here: PROFIBUS DP
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 Exceed-
Communicati- W1 (Warning 1) ed/Underrun during Cyclic Communication +
on W2 (Warning 2) Timeout + ID Verification'
IG (Ignore)
Event: Acyclic W2 (Warning 2) IG Sets the event class for 'Error Range Exceed-
Communicati- W1 (Warning 1) ed/Underrun during Acyclic Communication +
on IG (Ignore) Timeout + ID Verification'
A (Alarm)
Check in Key- NO YES The fieldbus communication monitoring in key-
board Mode YES board mode can be activated/deactivated.
1
Configuration NO_PARA_ID_3_6 FIXED_8_16 This is used to configure the structure and the
)
NO_PARA_ID_4_12 meaning of the payload in the transmission
PARA_ID_6_15 protocol.
FIXED_8_16 Process image selection:
FIXED_8_8 FIXED …: transmission by means of »Simplified
FIXED_4_4 Payload Structure [➙17]«
FIXED COMPATIBLE All others: Transmission by means of »General
VARIABLE COMPATIBLE Payload Structure (VARIABLE Mode) [➙26]«
Supplement 'COMPATIBLE': Compatibility with
an earlier DISOCONT model
1)
Address 0 … 126 10 Address of the DISOCONT Tersus (slave) at the
PROFIBUS


lue
FLOAT- SIEMENS-KG IEEE Format for FLOAT values (all setpoints, meas-
Format IEEE ured values, floating point parameters)
1) 2)
Parameter NO NO Select whether or not the payload package con-
YES tains a parameter block
1)
Preset Count 2…4 2 The number of preset values per message from
2)
master → scales
READ_ID 0 … 12 6 Number of freely selectable read values (meas-
1) 2)
Count ured and status values) per message from
scales → master
1)
these parameters are subject to the 30 s condition for transfer to the interface card (see chapter Guidelines
for Commissioning).
2)
These parameters are shown only if 'VARIABLE COMPATIBLE' is selected (see chapter Payload Scope
and Content).
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 'Tools | Start | Browse Controller' 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 configuration files?
The following table shows the correct use of the files:
File PROFIBUS mode Structure of the payload for the scales Step7 or CFC
electronics
DCT20B07.GSD PROFIBUS DP-V1 DISOCONT Tersus: VSP 28002

(DP-V1 → Cyclic and acyclic services) VPD 28002
▪ Simplified payload structure (Fixed
Mode):
For PPO types:
FIXED_4_4
FIXED_8_8
FIXED_8_16
▪ General payload structure (Variable Mo-
de):
For PPO types:
NO_PARA_ID_3_6
NO_PARA_ID_4_12
PARA_ID_6_15
DCV10456.GSD PROFIBUS DP-V0 DISOCONT: VSP 28000

(DP-V0 → Cyclic services only) VPD 28001
▪ General payload structure (Variable Mo-
de):
For PPO type: VARIABLE COMPATIBLE
FIX10456.GSD PROFIBUS DP FIX DISOCONT: ---

▪ Simplified payload structure (Fixed
Mode):
For PPO type: FIXED COMPATIBLE
In a GSD file, each selectable payload format is described by exactly one GSD module ('PPO type').
So-called 'identifier bytes' are transmitted in the PROFIBUS DP master configuration message with which
the PPO type of the payload message is established.
If an unknown identifier-byte combination is received, the module VPB 28020 will set the 'Con-
figuration Error' bit in the diagnostics message to the PROFIBUS DP master (refer to the LEDs
at the interface).

4.1.3.2.1 Integration Slave
The slave (in this case: DISOCONT 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 | DISOCONT Tersus | …
Integration is a two-part process using Drag & Drop:
1. 'Hook' the slave into the bus line (black dash)
2. Enter the payload structure into the table (→ module from GSD file)
Fig. 2: SIMATIC S7 HW Configurator [PROFIBUS]
Notes (all modes) for S7

▪ Reading-writing of double words in S7 systems:
Please note that the DISOCONT double words cannot be read or written with the S7
system function blocks SFC14 or SFC15. Instead, use direct peripheral access.

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 'Tools' in the EasyServe menu under 'Start' → 'Browse Controller' 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 Module', e. g. FIXED_8_16.

B) An overview of the GSD modules:

1) PROFIBUS DP Variable Mode (general payload structure)
Example for normal mode:
With parameter transmission, 6 preset values and 15 read values
→ GSD module "PARA_ID_6_15"
Meaning: With parameter block, 6 preset values, 17 process data read values in total (15 + 2 fixed)
Examples for the DISOCONT-compatible mode:
► Parameter set 1 (default setting):
Par. 'Parameter': NO
Par. 'Preset Count': 2
Par. 'READ_ID Count': 6
→ GSD module 'PPO6: 0 PKW, 2 Set, 8 PZD'
Meaning:
PPO6 : 6 per ID freely selectable values from DISOCONT (order list)
0 PKW: No parameter block
2 Set : 2 preset values
8 PZD : A total of 8 process data values ('READ_ID Count' + actual value and status)
► Parameter set 2:
Par. 'Parameter': YES
Par. 'Preset Count': 3
Par. 'READ_ID Count': 8
→ GSD module 'PPO_P8: 4 PKW, 3 Set, 10 PZD'
Meaning:
PPO_P8: 8 per ID freely selectable values from DISOCONT (order list)
4 PKW: With parameter block
3 Set : 3 preset values
10 PZD: A total of 10 process data read values ('READ_ID Count' + actual value and status)
2) PROFIBUS DP Fixed Mode (fixed payload structure)
Examples for normal mode:
→ GSD module "FIXED_8_16", "FIXED_8_8" and "FIXED_4_4"
Meaning: No ID transmission, 8 / 8 / 4 preset values and 16 / 8 / 4 read values
Example for the DISOCONT-compatible mode:
In FIXED mode there is exactly one module that describes uniquely the transmitted process image.
→ GSD module 'FIXED Mode Module' (equivalent to FIXED_8_16 with DISOCONT Tersus)
Meaning: No ID transmission, 8 preset values and 16 read values

3) Relationship between DISOCONT 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.
a. Structure of the GSD Module Name for DISOCONT Tersus Payload Formats:
e. g.
Format as per par. 'Configuration': → GSD Module name
FIXED_4_4 FIXED_4_4
FIXED_8_8 FIXED_8_8
FIXED_8_16 FIXED_8_16
NO_PARA_ID_3_6 NO_PARA_ID_3_6
NO_PARA_ID_4_12 NO_PARA_ID_4_12
PARA_ID_6_15 PARA_ID_6_15
It is not difficult here to identify the correct GSD module.

b. Structure of the GSD Module Name for Payload Format VARIABLE COMPATIBLE:
The following additional parameters will be displayed for this format:
'Parameter'
'Preset Count'
'READ_ID Count'
A particular GSD module must then be assigned based on the content of these parameters (in this exam-
ple YES; 4; 6).
General structure of a GSD module name:
c. Parameter Combinations and Corresponding GSD Modules:
Parameter Abb. Value range
Parameter Par *) NO | YES

Preset Count AzVg 2…4
READ_ID Count AzLw 0 … 12
Examples:
*)
NO → 0 PKW; YES → '_P' and 4 PKW

4.1.4 PROFIBUS Interface VPB8020

There are two different connections for bus activation on the VCU 20100:
X21 (corresponds to VPB:XP1)
X20 (corresponds to VPB:XP3)
X21 is the one generally used.
The interface assembly VPB 28020 contains the circuit board VPB8020 and incidentals for fitting.
The module may be attached to the base card of the device to make an interface with 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
Layout of the Components
Fig. 3: 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
W151
done by setting all 3 jumpers on the board (W150, W151, W152) to position 1 - 2. By default the
W152 resistances are not 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)

Pin XP1 XP3

Signal Signal
***)
4 CNTR-P (Control-P) VP (+5 V)
***)
5 DGND (0 V) SHIELD
***)
6 VP (+5 V) -
7 - -
**)
8 A, RxD/TxD-N -
9 - -
Housing SHIELD -
Tab. 15 : '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. 4: 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. 16 : LED 'Operating Mode' (below)
Status Display
off no power supply or not initialized

green initialized
green, flashing initialized, result of diagnostic test pending

Status Display
Red Exception error

Tab. 17 : LED 'Status' (above)
Cable specification:
The cable parameters for the standard cable of cable type A are listed in the following table.
Parameters Cable type A
Impedance (Ω) 135 … 165, with a frequency of 3 … 20 MHz

Mutual capacitance (pF/m) ≤ 30
Loop resistance (Ω/km) ≤ 110
Wire diameter (mm) > 0.64 *)
Wire cross-section (mm²) > 0.34 *)
Tab. 18 : Cable parameters
*) The wire cross-sections used must match the available connections at the bus plug.
The specified cable parameters of the standard cable (type A) give in the following table the specified linear
extensions of a bus segment for the respective transfer speed.
Transfer rate (kBit/s) 9.6 19.2 45.45 93.75 187.5 500 1500 3000 6000 12000
Max. segment length (m) 1200 1200 1200 1200 1000 400 200 100 100 100
Tab. 19 : Cable lengths per segment
Important: Only one transfer speed can be chosen within a fieldbus system that is supported by all field
devices. The segment lengths given result from the selected transfer speed.

4.1.5 Acyclic Services

In addition to cyclic IO data communication, the devices also support the lower-priority acyclic
RD_REC(SFC59) and WR_REC(SFC58) services. The devices are controlled with cyclic process data via a
PROFIBUS controller. This controller (usually a PLC) can also access the PROFIBUS devices via
RD_REC(SFC59) and WR_REC(SFC58) to parameterize. The parameters written are stored in non-volatile
memory in the device.
The payload transmitted by an acyclic PROFIBUS service are summarized in the form of a dataset.
4.1.5.1 Acyclical Data PROFIBUS
These data can be transmitted in DP-V1 mode only.
Data instance Type Example Byte Index Direc-

*)
(Typical response or explanation) (Specified payload) count tion
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 ASCII 68 135/0x87 S → M
long 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 ASCII 2014-05-21 14:12:03 68 140/0x8C S → M
counter value of the most recent log in No: 137
the legal-for-trade memory with an CR: 888170 kg
acyclic telegram.
Read all displayed events Binary 68 132/0x84 S → M

Max. 17 events, 4 bytes per event
Event group, number, class, acknowl-
edgement
(e.g. '03 01 01 00 … ')


*)
Class 162/A2
*)
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 pa- Binary 0250 42C80000 66 175/0xAF M → S

*)
rameter 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')
1) *
Write a read ID ) Binary 0250 2 176/0xB0 M → S
Subsequently the ID can be read mul-
tiple times (see next line)
Read a process or parameter value Binary 6 126/0x7E S → M
1)
whose ID was sent beforehand
[ID Value]
Read all preset value IDs of the pa- Binary 16 129/0x81 S → M

rameter block 'Fixed mode configura-
tion'
(e.g. '0140 0160 0180 0250 0252
0100 …')
Set all preset values IDs of the pa- Binary 0140 01A0 … 16 179/0xB3 M → S
rameter block 'Fixed mode configura- CAUTION: The 1st transmit-
*)
tion' ted ID must always be 0140
(→'Fieldbus Clearance')
Read all read IDs of the parameter Binary 32 130/0x82 S → M

block 'Fixed mode configuration'
(e.g. '02F0 0310 0610 0750 …')
Set all read IDs of the parameter block Binary 0752 0754 … 32 180/0xB4 M → S
*)
'Fixed mode configuration'
Read date and time Binary 0C030F 0B1000 6 138/0x8A S → M

(yymmdd hhmmss)


*)
Class 162/A2
*)
Write date and time Binary 0C030F 0B1000 6 188/0xB M→S
(yymmdd hhmmss) C
*)
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.

*)
Class 162/A2
Write the value of the basic parameter Binary 42C80000 64 203/0xA M→S
sets of all material-dependent parame- 43440000 … D
2) *)
ters, part 1
Write the value of the basic parameter Binary 42C80000 64 204/0xAE M → S
sets of all material-dependent parame- 43440000 …
2) *)
ters, part 2
Read the value of the base parameter Binary 64 153/0x7B S → M
sets of all material-dependent parame-
2)
ters, part 1
Read the value of the base parameter Binary 64 154/0x7C S → M
sets of all material-dependent parame-
2)
ters, part 2
*)
Write a material name ASCII 1C00 Name_1 42 186/0xBA M → S
Write a read ID the contents of which Binary 1C00 2 187/0xBB M → S
1) *)
subsequently can be read
Read the material name the ID of ASCII 1C00 Name_1 42 137/0x89 S → M
1)
which was written beforehand
*)
1)
2)
Available only if the device has material-dependent parameters (MDP).

4.1.6 Supplementary Documentation
European standard EN50170
PROFIBUS user organization www.profibus.com
BV-H2406 DISOCONT Tersus - System Manual
BV-H2185 Schenck Process EasyServe - Operating Manual

*)
BV-H2427AA CFC (DISOCONT Tersus)
*)
BV-H2155AA CFC (DISOCONT)
*)
BV-H2473GB STEP7 (DISOCONT Tersus)
*)
BV-H2473GB STEP7 (DISOCONT)
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 Settings at the DeviceNet Slave

Refer to chapter 'Parameter' in the DISOCONT Tersus instruction manual.
Parameter Value range Default value Explanation

1)
Protocol Type NO NO Selects the protocol
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 Exceed-
Communication W1 (Warning 1) ed/Underrun during Cyclic Communication +
W2 (Warning 2) Timeout + ID Verification'
IG (Ignore)
Event: Acyclic W2 (Warning 2) A Sets the event class for 'Error Range Exceed-
Communication W1 (Warning 1) ed/Underrun during Acyclic Communication +
IG (Ignore) Timeout + ID Verification'
A (ALARM)
Word Sequence I:std/L:std I:std/L:std Establish the word sequence during the transmis-
I:swp/L:std sion 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)
NO_PARA_ID_4_12 meaning of the payload in the transmission proto-
PARA_ID_6_15 col.
VARIABLE Payload Structure (VARIABLE Mode) [➙26]«
COMPATIBLE Supplement 'COMPATIBLE': Compatibility with
an earlier DISOCONT model
1)
Address 0 … 126 10 Address of the DISOCONT Tersus (slave) at the
CAN bus
Baud rate 125K 125K The baudrate must match that of the master sys-
250K tem.
500K
1) 2)
1) 2)
master → scales
READ_ID 0 … 12 6 Number of freely selectable read values (meas-
1) 2)
Count ured and status values) per message from scales
→ master
1)
these parameters are subject to the 30 s condition for transfer to the interface card (see chapter Guidelines
for Commissioning).
2)
these parameters are shown only if 'VARIABLE COMPATIBLE' is selected (see chapter Payload Scope
and Content)
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.
File DeviceNet mode Structure of the payload for the scales electronics
disocont_tersus_01.eds DISOCONT Tersus:

General and fixed payload structure
disocont.eds DISOCONT:
General payload structure
disocont.eds DISOCONT:
Fixed payload structure

4.2.4 DeviceNet Interface VCB8020

X21 (corresponds to VCB:XC1)
X20 (corresponds to VCB:XC3)
X21 is the one generally used.
The interface subassembly VCB 28020 contains the circuit board VCB8020 and fitting materials.
The module can be attached to the mainboard to create an interface to the DeviceNet.
Module properties

Power supply max. 250 mA
Plug connector to the bus activation XC1: Clamp 5-pole
XC3: clamp 5-pole
Fig. 5: VCB 28020 DeviceNet module layout drawing
Settings
W100 Determining the power supply:

The W100 jumper must be plugged in position 2 - 3
W160 Bus termination:
The bus termination resistances must be activated at the first and last station of the bus. This is
done by 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

Pin XC1 XC3

Signal Signal
4 CAN_H
5 V+
Tab. 20 : 'Bus activation' connector
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
Network status Display
off not online/no power supply

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. 21 : 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
alternating red-green Self-test
Tab. 22 : LED 'Module Status' (below)

4.2.5 Acyclical Data DeviceNet
Data instance (Typical response Type Example Byte Instance Service

*)
or explanation) (Specified payload) count
Class 162/A2
Attribute 5 hex dec dec/hex dec/he
x
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 ASCII 12 122/0x7A 14/0x0E

text
(e.g. 'WE01')
Highest-priority event - read long ASCII 40 123/0x7B 14/0x0E
text
Highest-priority event - read short ASCII 68 136/0x88 14/0x0E
and long texts
Read all displayed events - short ASCII 68 132/0x84 14/0x0E
text
(e.g. 'WE01 …')
Call up the time, number and the ASCII 2014-05-21 14:12:03 68 141/0x8D 14/0x0E
counter value of the most recent No: 137
log in the legal-for-trade memory CR: 888170 kg
with an acyclic telegram.
Read all displayed events Binary 68 133/0x85 14/0x0E

Event group, number, class,
acknowledgement
(e.g. '03 01 01 00 … ')


*)
Class 162/A2
x
Write a process or parameter val- Binary 0250 42C80000 6 175/0xAF 16/0x10

*)
ue
(ID, Value)
Write one or multiple process or Binary 0250 42C80000 66 176/0xB0 16/0x10

*)
parameter values 0252 41200000
(ID, Value; ID, Value; … ) 0000 00000000 …
Max. 11 values
with a ZERO value.
1) *
Write a read ID ) 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
1)
[ID Value]
Read all preset value IDs of the Binary 16 130/0x82 14/0x0E

parameter block 'Fixed mode con-
figuration'
(e.g. '0140 0160 0180 0250 0252
0100 …')
Set all preset values IDs of the Binary 0140 01A0 … 16 180/0xB4 16/0x10
parameter block 'Fixed mode con- CAUTION: The 1st transmitted
*)
figuration' ID must always be 0140
Read all read IDs of the parameter Binary 32 131/0x83 14/0x0E

(e.g. '02F0 0310 0610 0750 …')
Set all read IDs of the parameter Binary 0752 0754 … 32 181/0xB5 16/0x10
*)


*)
Class 162/A2
x
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)
Data instance Type Example Byte Instance Service

*)
(Typical response or explanation) (Specified payload) count
Class 162/A2
x
Write the value of the base parame- Binary 42C80000 43440000 … 128 174/0xAE 16/0x10
ter sets of all material-dependent
2) *)
parameters
Read the value of the base parame- Binary 128 124/0x7C 14/0x0
ter sets of all material-dependent E
2)
parameters
*)
Write a material name ASCII 1C00 Name_1 42 187/0xBB 16/0x10
Write a read ID the contents of which Binary 1C00 2 188/0xBC 16/0x10
1) *)
subsequently can be read
Read the material name the ID of ASCII 1C00 Name_1 42 138/0x8A 14/0x0
1)
which was written beforehand E
*)
1)
2)

DeviceNet specification Version 2.0 (ODVA)
Bosch CAN specification Version 2.0 (Sept. 1991)
DeviceNet user organization www.odva.com
BV-H2406 DISOCONT Tersus System Manual
BV-H2185 Schenck Process EasyServe - Operating Manual

4.3 PROFINET IO
NOTICE
MULTICAST services or closed ring may overload the network
MULTICAST services (e.g. webcam streams) may overload the electronics
processor if they are used within the electronics network. Use
ly switches in the electronics network that support IGMP (Internet Group
Management Protocol) for IPv4 or MLD (Multicast Listener Discovery) for
IPv6.
Consequences
In a closed Ethernet ring, a flood of messages may occur as some partici-
pants send messages to all participants. These messages are to be for-
warded by a switch in the network to all participants. If two switches are
connected with each other via two different paths (closed ring), this leads to
them permanently sending each other the messages. This leads to overload
on the network. The connected control systems may be overloaded by this
flood of messages and stop working completely. Therefore closed Ethernet
ring structures are not admissible.
You can recognise the overload when the LEDs start to flash significantly
more frequently than usual. The LEDs are assigned to the Ethernet connec-
tors.
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 [➙198]«.
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 [➙191]«.
See also
 Settings at the PROFINET IO Controller [➙192]

4.3.1 Guidelines for Initial Startup

Preparation of the hardware as per the system description (see »PROFINET Interface VPN8020 [➙198]«).
All standard, 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
auto-crossing functionality, i.e. either patch or crossover cables can be used to make the connection with the
next Ethernet subscriber.
Notice: 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 [➙208]«.
2. Specifying the payload structure (see parameter Configuration in chapter »Settings at the PROFINET
IO Device [➙191]«). 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 controller).
Alternatively the external tool Wireshark can be used.
Please refer to chapter »Notes for PROFINET IO [➙240]« for diagnostics and troubleshoot-
ing.
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 control-
ler) 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.
▪ 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 under the menu item 'View | Service Values'.

4.3.3 Configuration of the PROFINET Connection

4.3.3.1 Settings at the PROFINET IO Device

Refer to chapter 'Parameter' in the DISOCONT Tersus instruction manual

1)
Modbus-RTU here: PROFINET IO
PROFIBUS DP
DeviceNet
Modbus-TCP
PROFINET IO
EtherNet/IP
Event: Cyclic A (Alarm) IG Sets the event class for 'Error Range Exceed-
Communication W1 (Warning 1) ed/Underrun during Cyclic Communication + Timeout +
W2 (Warning 2) ID Verification'
IG (Ignore)
Event: Acyclic W2 (Warning 2) IG Sets the event class for 'Error Range Exceed-
Communication W1 (Warning 1) ed/Underrun 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 PARA_ID_6_15 FIXED_8_16 This is used to configure the structure and the meaning
FIXED_8_16 of the payload in the transmission protocol.
Process image selection:
FIXED …: transmission by means of »Simplified Pay-
load Structure [➙17]«
PARA ..... transmission by means of »General Payload
Structure (VARIABLE Mode) [➙26]«
1)
These parameters are subject to the 30 s condition for transfer to the interface card, see
ter »Guidelines for Initial Startup [➙189]«.
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 [➙
192]« by means of the example of 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.
In a GSDML file, each selectable payload format is described by exactly one GSDML module ('PPO type').

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

Schenck-Process- (Cyclic and acyclic services)
GmbH-
▪ Simplified payload structure (Fixed Mode):
DISOCONT_Ters
For PPO type: FIXED_8_16
us-20130131.xml
▪ General payload structure (Variable Mode):
For PPO type: PARA_ID_6_15
4.3.3.2.1 Integrating the IO Device
The IO device (in this case: DISOCONT Tersus) is integrated using the program 'SIMATIC Hardware Con-
figurator'. You can find the components required (configuration) via the tree structure as follows (see figure):
PROFINET IO | Further FIELD DEVICES | I/O | DISOCONT 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)
Fig. 7: Program: SIMATIC S7 HW Config
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 'Tools' in the EasyServe menu under 'Start' → 'Browse Controller' 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_16.
B) An overview of the GSDML modules
1) PROFINET IO – VARIABLE Mode (general payload structure)
With parameter transmission, 6 preset values and 15 read values
→ GSDML module 'PARA_ID_6_15'
Meaning: With parameter block, 6 preset values, 17 process data read values in total (15 + 2 fixed)

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

→ GSDML module 'FIXED_8_16'
Meaning: No ID transmission, 8 preset values and 16 read values
3) Relationship between DISOCONT 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 DISOCONT Tersus payload formats:
e. g.
Format as per parameter ' Configuration': → GSDML Module name
FIXED_8_16 FIXED_8_16
PARA_ID_6_15 PARA_ID_6_15

4.3.3.2.2 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 in the 'Device name' input field in the 'Input device name' frame and confirm with
[Assign name]. The device name is now applied to the participant and is saved there. It can 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 project proposal to SIMATIC S7 and start the assembly. The error LED on the controls should now
be off.
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 flashes yellow very quickly (permanent 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

4.3.4.1 PROFINET IO Module
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
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_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 following 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
exchanging data and order the ARs to the projected field de-
vices.
▪ The CPU is exchanging data
H411 red Bus error:

LED_BF_OUT
ON ▪ An Ethernet connection has a fault (e.g.: the bus connecting
plug has 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 devic-

es, ...).
▪ At least one projected AR is no longer involved in data ex-
change.
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.4.2 PROFINET IO Network Topology with VPN8020

This section describes the possible topology of PROFINET networks with Schenck Process weighing and
condition monitoring electronics 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
components which have been specified for PROFINET. In order to guaran-
tee 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.
Where IP66 protection class is required, an optional cabinet with inspection window to the VOP and an ex-
ternal IP66 keypad is available.
Star Topology
Fig. 8: PROFINET star topology
The network participants are connected with the PROFINET-capable switch in a star shape. In this topology,
Schenck Process devices (example A, B) can be configured via the PROFINET network.

Line Topology
Fig. 9: 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. 10: 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.4.3 Connecting the PROFINET IO Module to the Star Topology
Connection to a star topology – VCU 20100 with board VPN8020
NOTICE
The patch cable described below is supplied with the fieldbus module
VPN 28020.
Fig. 11: VCU 20100 Connecting VPN 28020 to VCU 20100
■ Board VPN8020 already has been installed in the DISOCONT Tersus.

1. Plug the fieldbus cable (PROFINET IO) into the switch of board VPN8020, e. g. into the den RJ45
connector X316: 1.
2. Plug the patch cable into the RJ45 connector X316: 2.
3. Plug the patch cable into one of the interfaces VCU:X93|X94|X95.
► The hardware preconditions for configuring the network through Ethernet have been met.

4.3.5 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.5.1 Acyclic Data PROFINET

*)
Slot 0 / SubSlot 1
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 ASCII 68 135/0x87 S → M
long 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 ASCII 2014-05-21 14:12:03 68 140/0x8C S → M
counter value of the most recent log in No: 137
acyclic telegram.
Read all displayed events Binary 68 132/0x84 S → M

max. 17 events, 4 Bytes per event
edgement
(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')


*)
Slot 0 / SubSlot 1
hex dec dec/hex
Write one or more process or parame- Binary 0250 42C80000 66 175/0xAF M → S

*)
ter 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,
1) *)
Writing a read ID Binary 0250 2 176/0xB0 M → S
Read a process or parameter value Binary 6 126/0x7E S → M
1)
[ID value]
Read all preset value IDs of the pa- Binary 16 129/0x81 S → M

tion'
(e. g. '0140 0160 0180 0250 0252
0100 …')
Set all preset values IDs of the pa- Binary 0140 01A0 … 16 179/0xB3 M → S
*)
Read all read IDs of the parameter 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)
*)
Read date and time Binary 0C030F 0B1000 6 188/0xB M→S
(yymmdd hhmmss) C
*)

1)

*)
Slot 0
hex dec dec/hex
Write the value of the base parameter sets of Binary 42C80000 128 173/0xA M→S
2) *)
all material-dependent parameters 43440000 … D
Read the value of the base parameter sets Binary 128 123/0x7B S → M
2)
of all material-dependent parameters
*)
Write a material name ASCII 1C00 Name_1 42 186/0xBA M → S
Write a read ID the Binary 1C00 2 187/0xBB M → S
contents of which subsequently can be
1) *)
read
Read the material name the ID of which was ASCII 1C00 Name_1 42 137/0x89 S → M
1)
written beforehand
*)
1)
2)

BV-H2406 DISOCONT Tersus - System Manual
European standard IEC 61158
INTECONT: BV-H2185 EasyServe Operating Manual
DISOMAT: BV-H2461 DISOPLAN VPL 20430 – Instruction 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
IPv6.
Consequences
tors.
*)
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'.

1. Preparation of the hardware as per BV-H2406:
The hardware for the Ethernet interface already is contained in the basic configuration. One of the
plugs X93 - X95 (RJ 45) can be freely selected. The EtherNet/IP protocol is supported.
2. Activate the EtherNet/IP protocol type in the DISOCONT Tersus.
3. Parameterize the Ethernet address at the interface.
4. Selection the process image and definition of the data to be transmitted.
5. The master will begin communication (fieldbus mode of operation).
6. Monitor the interface using EasyServe ('Fieldbus' view).

Please refer to chapter »Notes for EtherNet/IP [➙240]« 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 DISOCONT Tersus instruction manual

lue

Modbus-RTU here: EtherNet/IP
PROFIBUS DP
DeviceNet
Modbus-TCP
PROFINET IO
EtherNet/IP
Communication W1 (Warning 1) ed/Underrun during Cyclic Communication +
W2 (Warning 2) Timeout + ID Verification'
IG (Ignore)


lue
IG (Ignore)
A (ALARM)
Word Sequence I:std/L:std I:std/L:std Establish the word sequence during the transmis-
I:swp/L:std sion of measured values in IEEE/LONG format
I:std/L:swp In this case: I:swp/L:std (Little Endian)
I:swp/L:swp
Byte Sequence High - Low High - Low Establish the byte sequence within a data word
Low - High In this case: Low - High(Little Endian)
NO_PARA_ID_4_12 meaning of the payload in the transmission proto-
PARA_ID_6_15 col.
VARIABLE Payload Structure (VARIABLE Mode) [➙26]«
COMPATIBLE Supplement 'COMPATIBLE': Compatibility with an
earlier DISOCONT model
1)
1)
master → scales
READ_ID 0 … 12 6 Number of freely selectable read values (measured
1)
Count and status values) per message from scales →
master
1)
These parameters are shown only if VARIABLE COMPATIBLE is selected, see chapter Payload Scope
and Content.
Settings in the 'Ethernet' block
Parameters 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.
In accordance with the specifications on certification, PING requests are only answered if they come from
their own sub-network.
4.4.3.2 Settings at the EtherNet/IP Master (ControlLogix)

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.
▪ Setting up a new project in the RSLogix program
▪ Configuration of the controller
▪ Selection and configuration of the EtherNet/IP-Bridge
▪ Adding the DISOCONT Tersus to the I/O configuration
▪ Adding a 'Generic Ethernet Module'
The example applies to: FIXED_8_16
▪ Configuration of the new EtherNet/IP module
A) Setting the connection options for the controller

B) Expedient 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) Depiction of the data of a DISOCONT Tersus in ContolLogix
I Data are the input data from the DISOCONT Tersus (16 read values).
O Data are the output data to the DISOCONT Tersus (8 preset values).

4.4.4 Acyclic Data (Explicit Messages) EtherNet/IP
Data instance Type Example byte Instance Service

(Typical response or explanation) (Specified payload) Count
*)
Class 4
Attribute 3 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 …')
Call up the time, number and the ASCII 2014-05-21 14:12:03 68 141/0x8D 14/0x0E
counter value of the most recent log in No.: 137
acyclic telegram.
Read all displayed events Binary 68 133/0x85 14/0x0E

edgement
(e.g. '03 01 01 00 … ')
*)
Write a process or parameter value Binary 0250 42C80000 6 175/0xAF 16/0x10
(ID, Value)


*)
Class 4
Write one or multiple process or pa- Binary 0250 42C80000 66 176/0xB0 16/0x10
*)
rameter values 0252 41200000
(ID, Value; ID, Value; … ) 0000 00000000 …
Max. 11 values
with a ZERO value.
1) *
Write a read ID ) Binary 0250 2 177/0xB1 16/0x10
Read a process or parameter value Binary 6 127/0x7F 14/0x0E
1)
[ID Value]
Read all preset value IDs of the pa- Binary 16 130/0x82 14/0x0E
tion'
(e.g. '0140 0160 0180 0250 0252
0100 …')
Set all preset values IDs of the pa- Binary 0140 01A0 … 16 180/0xB4 16/0x10
*)
Read all read IDs of the parameter Binary 32 131/0x83 14/0x0E

(e.g. '02F0 0310 0610 0750 …')
Set all read IDs of the parameter block Binary 0752 0754 … 32 181/0xB5 16/0x10
*)
Read date and time Binary 0C030F 0B1000 6 139/0x8B 14/0x0E

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

*)
1)

*)
Class 4
Write the value of the base parameter sets Binary 42C80000 43440000 … 128 174/0xAE 16/0x10
2) *)
Read the value of the base parameter sets Binary 128 124/0x7C 14/0x0E
2)
*)
Write a material name ASCII 1C00 Name_1 42 187/0xBB 16/0x10
Write a read ID the contents of which sub- Binary 1C00 2 188/0xB 16/0x10
1) *)
sequently can be read C
Read the material name the ID of which ASCII 1C00 Name_1 42 138/0x8A 14/0x0E
1)
was written beforehand
*)
1)
2)
4.4.4.1 Acyclic Data Exchange between PCS and Scales 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 of 'Writing a Process or Parameter Value'
Task: set parameter 'Serial Setpoint' to 100 kg/h.

This results in the following preset value:
Preset ID = 0250 hex 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 175 dec (AF hex ) 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
10 hex .
▪ 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 'Display 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 131 dec (83 hex ) 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
0E hex .
▪ 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 Commissioning

▪ Prepare the hardware as described in BV-H2406:
– Modbus-RTU: The 'Modbus Interface VSS 28020' is used for serial Modbus (refer to chapter
'Fieldbus Interface').
– Modbus-TCP: If using Modbus via internet the hardware for the Ethernet interface is contained in the
basic configuration. One of the plugs X93 - X95 (RJ 45) can be freely selected.
▪ Activate the Modbus-RTU or Modbus-TCP protocol types in the DISOCONT Tersus.
▪ Parameterize the serial or Ethernet addresses.
▪ Defining the data to be transmitted.
▪ The master will begin communication.
▪ Monitor the interface using EasyServe → 'Fieldbus' view (refer to chapter 'Diagnostics and Trouble-
shooting').
▪ Ensure the correct bus termination if using the serial connection (refer to chapter 'Fieldbus Interface').
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 desig- Segment Corresponding Controller

nation address (dec) 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 out- FC15: Write multiple coils 00001 -09999 256 - 463 / 0x0100-0x01CF
puts
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-0x097C
puts 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 See FC04 and FC16
analog outputs in one registers FC04 and FC16
command
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 Error 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 Ensuring Transmission

Modbus-TCP:
The TCP layer safety measures safeguard transmission for the Modbus-TCP.
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 = Data
xx
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 01 10 1082 0002 Write parameter (value = 163.34)
5678
4.5.1.11 Acyclical Data Modbus
Data instance Type Example Byte Data address FC

(Typical response or explana- (Request Modbus frame in count
*)
tion) hex) (dec/hex)
Slave address 1 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 ver- ASCII 01 03 2297 0014 40 8855/0x2297 3

sion
Highest-priority event – read ASCII 01 03 2200 0006 12 8704/0x2200 3

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


*)
)
Highest-priority event - read ASCII 01 03 22AB 0022 68 8875/0x22AB 3
short and long texts
(e.g. 'WE01 Event: Power Fail-
ure')
Read all displayed events - ASCII 01 03 223F 0022 68 8767/0x223F 3

short text
Max. 17 events, 4 charac-
ters/event
(e.g. 'WE01 …')
Call up the time, number and ASCII 2014-05-21 14:12:03 68 9279/0x243f 3

the counter value of the most No.: 137
recent log in the legal-for-trade CR: 888170 kg
memory with an acyclic tele-
gram.
Read all displayed events Binary 01 03 2261 0022 68 8801/0x2261 3

Max. 17 events, 4 bytes per
event
Event group, number, class,
acknowledgement
(e.g. '03 01 01 00 … ')
Write a process or parameter Binary 01 10 2040 0003 06 0250 6 8246/0x2040 16/0x10

*)
value 42C80000
(ID, Value)
(e.g. 'Serial Setpoint = 100
kg/h')
Write one or multiple process or Binary 01 10 2043 0022 44 0250 66 8249/0x2043 16/0x10
*)
parameter values 42c80000 0252 41200000
(ID, Value; ID, Value; … ) 0000 00000000 ….
Max. 11 values
The evaluation ends at the next
ID with a ZERO value.


*)
)
1)
Write a read ID *) Binary 01 10 2064 0001 02 0250 2 8282/0x2064 16/0x10
Subsequently the ID can be
read multiple times (see next
line)
Read a process or parameter Binary 01 03 221A 0003 6 8730/0x221A 3
value whose ID was sent be-
1)
forehand
[ID Value]
Read all preset value IDs of the Binary 01 03 208D 0008 16 8323/0x208D 3
parameter block 'Fixed mode
configuration'
(e.g. '0140 0160 0180 0250
0252 0100 …')
Set all preset values IDs of the Binary 01 10 208D 0008 10 0140 16 8323/0x208D 16/0x10
parameter block 'Fixed mode 01A0 …
*)
configuration' CAUTION: The 1st transmit-
ted ID must always be 0140
Read all read IDs of the param- Binary 01 03 2095 0010 32 8331/0x2095 3
eter block 'Fixed mode configu-
ration'
(e.g. '02F0 0310 0610 0750 …')
Set all read IDs of the parame- Binary 01 10 2095 0010 20 0752 32 8331/0x2095 16/0x10
ter block 'Fixed mode configura- 0754 …
*)
tion'
Read variables lists using the Binary 01 03 2400 0022 64 9216/0x2400 3

Modbus protocol
Write variables lists using the Binary 01 10 21E0 0010 20 32 8672/0x21E0 16/0x10
Modbus protocol 00010000 …
(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)
Data instance Ty- Example Byte Data FC

(Typical response or explana- pe (Request Modbus frame in hex) count address
*)
tion) Slave address 1
dec (dec/hex) (dec/hex)
Write the value of the base pa- Bi- 01 10 2000 0040 80 42C80000 128 8192/0x20 16/0x10
rameter sets of all material- nary … 00
2)
dependent parameters *)
Read the value of the base Bi- 01 03 2000 0040 128 8192/0x20 3
parameter sets of all material- nary 00
2)
dependent parameters
*)
Write a material name ASC 1C00 Name_1 42 0x2420 16/0x10
II
Write a read ID the contents of Bi- 1C00 2 0x2436 16/0x10
which subsequently can be nary
1) *)
read
Read the material name the ID ASC 1C00 Name_1 42 0x2420 3
of which was written before- II
1)
hand
*)
1)
2)
4.5.1.12 Supplementary Documentation
OPEN MODBUS-TCP SPECIFICATION www.modbus.org
BV-H2185 EasyServe operating Manual

4.5.2 Modbus-TCP
NOTICE
IPv6.
Consequences
tors.
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 for Modbus [➙241]« 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
IG (Ignore)
Communication W1 (Warning 1) ed/Underrun during Acyclic Communication + Timeout +
IG (Ignore) ID Verification'
A (ALARM)
Emulation Mo- NO NO Compatibility setting towards the DISOCONT master
de Vxx 20150 YES
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
Access Rights NO NO Determines for the Modbus-TCP protocol which master
Limitation FB FIRST WRITE system may execute controlling functions:
REMOTE IP NO: Each master system may give preset values. The
most recent value is effective.
FIRST WRITE: The master system that first sends a
preset message is given write access.
REMOTE IP: Only the master system whose IP address
was explicitly given can send preset values.
Remote IP 192168240250 19216824025 IP address of the subscriber with control rights
)
Address FB * 0
*)
This parameter is shown only if 'REMOTE IP' is selected.

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

where 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 DISOCONT 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 DISOCONT Tersus 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'.
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 DISOCONT 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
Please refer to chapter 'Notes on Modbus' for diagnostics and troubleshooting.
4.5.3.3.1 Settings at the Modbus-RTU Slave




1)
Modbus-RTU here: Modbus-RTU
PROFIBUS DP
DeviceNet
Modbus-TCP
PROFINET IO
EtherNet/IP
IG (Ignore)
IG (Ignore)
A (ALARM)
Emulation Mo- NO NO Compatibility setting towards the DISOCONT master
de Vxx 20150 YES
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
maximum number of characters of the transmitted val-
ue.
Refer to chapter »Available Data - Listing [➙235]«
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
(RS422)
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 - Listing
4.5.3.4.1 Preset values INTEGER
ID (Identifier) Value Calculation Feeder Type
hex dec Presets Calculation of In- VLW VWF VB VMC VSF VIF VBC
teger-Format W
0020 32 Serial Setpoint [kg/h] 0 to MAXINCR. = 0 * * * * * *

to 300% P
0021 33 Serial Batch Setpoint 0 to MAXINCR. = 0 * * * * * *
[kg] to 100% P * 8 HRS.
Tab. 23 : Fieldbus Presets Integer Format
4.5.3.4.2 Read values INTEGER (Measured values)
hex dec Read Values Calculation of In- VLW VWF VB VMC VSF VIF VBC
teger-Format W
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
to P * 24 STD
to P * 720 STD
34 52 Belt Load [kg/m] 0 to MAXINCR. = 0 *
to 200% Q
35 53 Measured load [kg] 0 to MAXINCR. = 0 * *
to 200% Q
36 54 Belt Speed [m/s] 0 to MAXINCR. = 0 * *
to 100%V [cm/s]

hex dec Read Values Calculation of In- VLW VWF VB VMC VSF VIF VBC
teger-Format W
37 55 Speed [1/min] 0 to MAXINCR. = 0 * * *

to 100% N
38 56 Fill Weight [kg] 0 to MAXINCR. = 0 * *
to 100% F
39 57 B: Fill Weight [kg] 0 to MAXINCR. = 0 * * * * * *
to 100% B
3A 58 2nd Platform [kg/m] 0 to MAXINCR. = 0 *
to 200 % Q
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 0 to MAXINCR. = 0 * * * * * *
[kg] to P * 8 Stunden
3E 62 Perc. setpoint factor [%] 0 to MAXINCR. = 0 * * * * *
to 100 %
3F 63 Prefeeder Position [%] 0 to MAXINCR. = 0 * * * *
to 100 %
40 64 Deviation [%] 0 to MAXINCR. = 0 * * * * *
to 100 %
41 65 Moisture [%] 0 to MAXINCR. = 0 * * * * *
to 100 %
42 66 Corrected Feedrate 0 to MAXINCR. = 0 * * * * *
[kg/h] to 100% P
43 67 Totalizer 1 corrected 0 to MAXINCR. = 0 * * * * *
[kg] to P * 8 STD
[kg] to P * 24 STD
[kg] to P * 720 STD
Tab. 24 : Fieldbus Meas. Values Integer format

4.5.3.5 Modbus Interface VSS8020

X21 (corresponds to VSS: XS2)
X20 (corresponds to VSS: XS3)
Plug X20 is used in the DISOCONT Tersus.
The interface assembly VSS 28020 contains the circuit board VSS8020 and incidentals for fitting.
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. 25 : Modbus module properties
Fig. 12: VSS 28020 Modbus module layout drawing
Serial Interfaces Pin Assignment
Pin RS232 RS485-4-wire RS485-2-wire

(RS422)
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

Pin RS232 RS485-4-wire RS485-2-wire

(RS422)
5 Tx B RTx A
6 Jumper to pin 4 for bus termination
7 Jumper to pin 3 for bus termination
Tab. 26 : Pin assignment Modbus serial interface
Cable specification
The cable parameters for the standard cable of cable type A are listed in the following table.
Parameters Cable type A
Impedance (Ω) 135 … 165, with a frequency of 3 … 20 MHz

Mutual capacitance (pF/m) ≤ 30
Loop resistance (Ω/km) ≤ 110
Wire diameter (mm) > 0.64 *)
Wire cross-section (mm²) > 0.34 *)
Tab. 27 : Cable parameters
*) The wire cross-sections used must match the available connections at the bus plug.
The specified cable parameters of the standard cable (type A) give in the following table the specified linear
extensions of a bus segment for the respective transfer speed.
Transfer rate (kBit/s) 9.6 19.2 45.45 93.75 187.5 500 1500 3000 6000 12000
Max. segment length (m) 1200 1200 1200 1200 1000 400 200 100 100 100
Tab. 28 : Cable lengths per segment
Important: Only one transfer speed can be chosen within a fieldbus system that is supported by all field
devices. The segment lengths given result from the selected transfer speed.

Diagnosis and Troubleshooting
5 Diagnosis 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 DP

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 IO

Meaning of the event message
▪ Check GSDML module or the parameterization.
→ Monitor the LEDs at the interface connection (see chapter »PROFINET Interface VPN8020 [➙
198]«).
▪ 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 infor-
mation
2 Active only when EasyServe is connected 5 Time accurate to the millisecond (device)
serially
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 se-
lected with the mouse. These are then stored in the clipboard and can be transferred to
the windows editor (NOTEPAD) to be edited.
*)
⊠ Transmit Select whether data flow in this direction should be logged (scales → fieldbus).
*)
⊠ Receive Select whether data flow in this direction should be logged (fieldbus → scales).
*)
⊠ 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 Weighfeeder (VWF)

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 the adjustment can be found in BV-H2407.
Step ID (dec) ID (hex) Comment
1 Stop Feeder 321 0x0141 To ensure that the 'Batch' function

can be de-selected.
2 Abort Batch 338 0x0152 ditto.
3 Deselect Batch 337 0x0151
4 Volumetric Mode 324 0x0144 Activate volumetrically (speed is
proportional to the setpoint)
5 Stop Prefeeder 351 0x015F The prefeeder and the feed gate will
remain closed even if the setpoint
is ≠ 0.
6 Start Feeder 320 0x0140
The setpoint does not have to be 0.
The belt will run proportionally to the
setpoint. If P = P o , then v = v o.
7 Belt Load 1880 0x0758 Read value
Decide whether to 'Tare' or to 'Zero' and proceed accordingly:
Tare
8 TW: Tare 368 0x0170 Start
9 TW: Tare 776 0x0308 Verify status bit. This status must
remain until taring is complete.
Zeroing
8 >0< Zero Set 369 0x0171 Start
9 >0< Zero Set 777 0x0309 Verify status bit. This status must
remain until zeroing is complete.
10 Waiting for Confirmation 817 0x0331 Wait for status change
11 Results of the adjustment are 1964 0x07AC Calibration Display 1
contained in the measured Difference to previous zeroing or
values taring
1966 0x07AE Calibration Display 2
New value for Basic Tare (P09.04)
or Zero Correction(P09.05)

12a Check adjustment re- 379 0x017B Or continue with 12b

sult Apply
1880 0x0758 The measured value of the belt load
and
must be zero if you select apply!
Belt Load
(fluctuate around zero)
12b Cancel 380 0x017C Reject results of the adjustment and
cancel
13 Stop Feeder 321 0x0141
14 Select Batch 336 0x0150 Activate batch (if required)
15 Particip. Prefeeder 350 0x015E
16 Gravimetric 325 0x0145 Activate gravimetric mode
17 Enter the desired setpoint
and, if required, the batch
setpoint
18 Continue in normal operation
Implementation with CFC
4 preset values: 1. 2. 3. 4.
Fixed Fixed Fixed Apply DP_ID_V4 to 0x0160
This makes 'Multiplex Mode', by switching the read IDs, unnecessary.

6.2 Internal On-Stream Calibration System of a Weighfeeder

(VWF)
This section describes the sequence through which the internal on-stream calibration system ('Kontrollmes-
seinrichtung', or KME) of a weighfeeder cycles via fieldbus.
Primarily, the IDs of the commands and the statuses and measured values of the fieldbuses will be present-
ed and described in more detail. Detailed documentation on the process, the parameters and the measured
values can be found in the manual BV-H2407.

Status ID (dec) ID (hex) Comment
Expect Acceptance 807 0x0327 KME is waiting for acknowledgement.

Identical toCH11: KME measuring phase finished. Results
are available. Must now be acknowledged.
On Stream Calibration 808 0x0328 KME is in the system (KME can be run). A KME need not
have been started.
Relative Zero Correction 809 0x0329 KME tare has been exceeded in a relative sense.
Error Identical to CH05: Tare threshold has been exceeded
relatively
Absolute Zero Correction 810 0x032A KME tare has been exceeded in an absolute sense.
Error Identical to CH04: Tare threshold has been exceeded
absolutely
Relative Span Correction 811 0x032B KME range has been exceeded in a relative sense.
Error Identical to CH07: Range threshold has been exceeded
relatively
Absolute Span Correction 812 0x032C KME range has been exceeded in an absolute sense.
Error Identical to CH06: Range threshold has been exceeded
absolutely
No Check Release 813 0x032D KME measurement has been registered.
Identical to CH09: KME has been started and is waiting
for release
Prepare Check Measure- 814 0x032E Prepare KME.
ment KME is in the preparatory phase (hopper being filled;
when filled, remove filling contact)
Check Measurement Acti- 815 0x032F KME is running.
ve KME in the measuring phase. Z, L and T are determined
continuously.
Measured values ID (dec) ID (hex) Comment
Relative Zero Correction 2020 0x07E4 Result of the KME: Relative tare ((Z - F) / L) * (100 / Qo).
Will be calculated at the end of the measuring phase.
Relative Span Correction 2022 0x07E6 Result of the KME: Range relative (1 - F/Z) * 100: will be
calculated at the end of the measuring phase.
Contin. Result Z 2024 0x07E8 KMW continuous result Z in kg (determined by the scales
during the measuring phase)
Check Result F/Z 2026 0x07EA Result of the KME: F/Z (determined continuously during
the measuring phase)
Check Meas. Time 2028 0x07EC Current running time of the KME in [h]. (determined con-
tinuously during the measuring phase) VIF and VCM
Check Belt Length 2030 0x07EE Current length of the KME belt in [m] (determined continu-
ously during the measuring phase) VWF and VBW

Commands ID (dec) ID (hex) Comment
Start Zero Check 352 0x0160 Start internal KME for 'Tare'.
Source must be set to fieldbus. KME block must be active.
Start Span Check 353 0x0161 Start internal KME for 'Range'.
Accept Correction 354 0x0162 Apply the result of the internal KME.
KME must have ended.
Check Measurement 355 0x0163 Stop KME.
CANCELLED Source must be set to fieldbus. Ended KME will not be
applied. Ongoing KME will be canceled.
Source Check Enable 356 0x0164 Clear KME.
Source must be set to fieldbus. KME will be canceled.
Static signal !
Ext. Cor. Tare acqu. 357 0x0165 Apply external correction factor for tare.
External KME must be active. Applied via fieldbus only.
Ext.Cor. Range acqu. 358 0x0166 Apply external correction factor for range.
External KME must be active. Applied via fieldbus only.
Start External Check 359 0x0167 External KME must be active.
Can only be started via fieldbus.
Print Check Result 365 0x016D Parallel sources. Last KME values will be printed.
Feeder Stopped 427 0x01AB Echo conveyer unit OFF.
Source must be set to fieldbus.
Static signal that indicates that the conveyor unit is off.
The KME will be canceled if the signal is absent.
Setpoints ID (dec) ID (hex) Comment
Span Correction Value 604 0x025C External KME must be active. Range correction value for
the external KME (see command 0x0166)
Zero Correction Value 606 0x025E External KME must be active. Tare correction value for the
external KME (see command 0x0165)
Event group: Check measurement system
CH01 Event: Minimum Check Quantity (P27.17)

At the end of the measurement the bin weigher has ascertained a smaller control quantity than the speci-
fied minimum quantity (P27.16). The check was canceled.
Either the number of belt circuits (P27.12, 13) or the belt load is too small.
CH02 Event: Minimum Fill Weight (P27.19)

The fill level dropped below the permissible lower limit Minimum Fill Weight (P27.18) during the measuring
procedure. The procedure will be canceled.
The cause could either be a too-large control setpoint or a too-small Storage Quantity (P27.15).

CH03 Event: Maximum Fill Weight (P27.21)

Storage Quantity (P27.15) greater than Maximum Fill Weight (P27.20). The check will be canceled just after
it starts.
In case of an error, check the magnitude of both parameters.
CH04 Event: Absolute Zero Correction Error (P27.33)

This correction makes the sum of all zero-point corrections greater than the threshold P27.31. Correction is
not automatic. The operator can acknowledge the message and enter the result manually.
Monitoring and messaging occur in the acknowledgement phase.
The correction weighting factor P27.37 is not taken into account in the error analysis.
TK = P09.05 (tare correction) in kg/m

Qo = Rated bridge load in kg/m
N = Calculated zero-point error (Z-F)/L in kg/m
F = Control quantity in the bin weigher (setpoint)
Z = Control quantity in the weighfeeder (actual value)
L = Length of belt that passed over the weighbridge during the control.
CH05 Event: Relative Zero Correction Error (P27.34)

The relative zero-point error, i.e. the error determined during the most recent check, exceeds the threshold
P27.32.
For further details see parameter P27.33
CH06 Event: Absolute Span Correction Error (P27.35)

This correction makes the sum of all range shifts exceed the threshold P27.31.
B = Range error determined F/Z

F = Control quantity in the bin weigher (setpoint)
Z = Control quantity in the weighfeeder (actual value)
K = Parameter P09.01 (range correction)
1 = Default value of parameter P09.01
For further details see parameter P27.33
CH07 Event: Relative Span Correction Error (P27.36)

The relative range error, i.e. the error determined during the most recent check, exceeds the threshold
P27.32.
The values Brel, Trel, B and Z will be displayed during acknowledgement.
CH08 Event: Feeder Not Stopped (P27.26)

1. The echo (P 27.25) was not returned within 3 s of the 'Stop Filling' command.
The control will not be canceled but will wait for the echo.
2. If the echo is absent during the measuring phase, i. e. if filling is registered the check will be interrupted
without sending a message.
CH09 Event: No Check Enable (P27.07)

The KME was started but release is absent.
This message is given whether the scales are on or off.
CH10 Event: Prepare Check Measurement (P27.27)

The check procedure is in the filling phase, the Damping Time or the fill level is greater than the
ue Maximum Fill Weight (P27.20).
CH11 Event: Expect Acceptance (P27.29)

The KME is waiting for input from the operator.
a) apply correction
b) reject correction and cancel
If Auto Correction (P27.02 = YES), the operator need act only if a tolerance threshold is exceeded.
CH12 Event: Check Gate Error (P27.43)
CH13 Event: Bin Error (P27.45)

On the second attempt the measurement error at the bin exceeded the tolerance limit (P27.44).
The control will be canceled.
The check will also be canceled if the event class is event class IG.

6.3 Taring a Loss-in-Weight Feeder (VLW)

This section describes the steps required to tare a loss-in-weight feeder via fieldbus. Primarily, the IDs of the
commands and the statuses of the fieldbuses will be presented and described in more detail. Further infor-
mation on taring can be found in manual BV-H2410.
1 Stop Feeder 321 0x0141 To ensure that the 'Batch' function

can be de-selected.
2 Abort Batch 338 0x0152 ditto.
3 Deselect Batch 337 0x0151
4 TW: Tare 368 0x0170 Start
5 >0< Zero Set 777 0x0308 Verify status bit. This status must
remain until taring is complete.
6 Waiting for Confirmation 817 0x0331 Wait for status change
7 Results of the adjustment are 1964 0x07AC Calibration Display 1
contained in the measured Difference to previous taring
values
1966 0x07AE Calibration Display 2
New current value for Basic Tare
(P09.03)
8a Check adjustment re- 379 0x017B Or continue with 8b
sult Apply
1888 0x0760 The measured value of the fill level
and
= 0 (fluctuates around zero) once
Fill Weight
the result has been accepted
8b Cancel 380 0x017C Reject results of the adjustment and
cancel
9 Select Batch 336 0x0150 Activate batch
10 Enter the desired setpoint
and, if required, the batch
setpoint
11 Continue in normal operation
TIP
Notice: Step 7 is optional, it is sufficient to check the fill level (8a).

6.4 Loss-in-Weight Feeder (VLW) Inlet Gate Control

This section describes the steps required to control the inlet gates of a loss-in-weight feeder 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 the inlet gate controller can be found in manual BV-H2410.

*)
1 Filling Start 344 0x0158 This will manually begin a fill operation .
2 DO: Gate 824 0x0338 Open gate. The PLC should open the inlet gate without
delay as soon as this bit is set to 1 at the fieldbus. This
bit corresponds to the fill contact at the DISOCONT.
3 DO: Gate 824 0x0338 Close gate. The PLC should close the gate instantly as
soon as this bit is set to 0 on the fieldbus.
*)
We differentiate between fill procedures started automatically or manually; also refer to BV-H2410, Chapter
Appendix → Fill weighing: START/STOP filling.
Usually the fill operations are started and monitored by DISOCONT itself. Fill operations can be canceled via
fieldbus at any time using the command Filling Stop (345/0x0159).
6.5 Adjusting Capacity via Fieldbus

TIP
Refer to manual BV-H2410 for an explanation of the function 'Adjusting
Capacity'.
▪ Status information and the adjustment values can be read cyclically in order to keep a 'live display' up-
to-date (also refer to EasyServe).
▪ The commands need only be entered at the start and when the corresponding status bit is set.
▪ The adjustment program automatically will stop if the max. runtime (90 s) is exceeded (see step 2).
You therefore may need to make P11.07 (capacity adjustment) less sensitive.
– The adjustment program also automatically will stop if the parameter ranges are underrun or ex-
ceeded.
– The adjustment program also automatically will stop if the tolerance check (steps 7 - 10) indicates
out-of-range.
▪ At the end all altered parameters can be read back for control
es P03.03/P03.04/P11.16/P12.04 and P12.05 .
Conditions:
Parameters Setting
P11.05 (Automatic NO
capacity adjustment) If YES the threshold values of all parameters will be checked and if required au-
tomatically accepted once the new nominal feedrate has been determined.
P11.15 (known density) YES
If NO then steps 11-16 will be skipped

Description of the Adjustment Steps
Step Function
1-2 Transport material to the discharge point

3-4 Determine the actuating variable offset for the controller (initialization and measurement)
5 Determine the actuating variable offset for the controller (Wait for acknowledgement – Dis-
play the result – Adjustment value 2 = Actuating variable offset [mA])
6 Determine the actuating variable offset for the controller (accepting the value into P12.04 &
P12.05)
7-8 Determine the new nominal feedrate (initialization and measurement)
9 Determine the new nominal feedrate (display the new value - adjustment value 2)
10 Determine the new nominal feedrate (accept or cancel the calculated value)
11 - 12 Calculate and display the density
13 - 14 Accept or reject the density
15 Manual correction of the density value (from operator panel only)
16 Accept or reject the density (from operator panel only)
17 Adjustment program finished
Actions Required of the External Controller
Action ID ID (hex) Comment

(dec)
Command: Capacity 446 0x01BE Begin the adjustment program

adjustment (D)
Read IEEE values: Ad- 1964 0x07AC Read out adjustment value 1
justment display 1 Different values depending on the current step.
Read IEEE values: Ad- 1966 0x07AE Read out adjustment value 2
justment display 2 At the end of the corresponding step the result will appear in
this value that may be copied into a parameter. Only 90% of
the value displayed will be entered into the parameter during
a capacity adjustment.
Read status: capacity 868 0x0364 Capacity adjustment active
adjustment (during the entire adjustment program)
Read status: wait for 817 0x0331 This status bit indicates that the commands Activate or Can-
acknowledgement cel must be activated.

Action ID ID (hex) Comment

(dec)
Command: Accept (D) 379 0x017B Accepts the value from step 3 and uses it to calculate the
value 'Feed rate lo_new'. The new and the previous values
are displayed in the next phase. The newly-calculated value
will be compared to the parameter thresholds (P03.03 ). The
adjustment program will stop if the value lies outside of this
range.
Command: Cancel (D) 380 0x017C Ends the adjustment program or the adjustment step
Read the adjustment 2544 0x09f0 Displays the current adjustment step and the linearization
step (32 bit integer value) point for a multiple-point adjustment
Bit 0...15 adjustment step, bit 16...31 lin. point
Set parameter: P11.16 6396 0x18FC May be used optionally to set the parameter to the desired
(material density) value by fieldbus

Appendix
7 Appendix
7.1 Common Abbreviations

MAXPART Maximum number of parts Refer to the parameter Modbus
S
AK Task Identifier or Reply Identifier 3 bits, part of the parameter identifier
CP Communication Processor Communication component for control systems, PC or
peripheral 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 Indicates which part of the parameter description will
block 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 de-
scription, 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

Appendix
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
7.3 Glossary
Item Explanation
GSD File PROFIBUS-specific configuration file in ASCII format containing information on node
(General Station Des properties, e.g. supported baud rates and other properties. If a new node is added
cription file) the master must 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 creating 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 con-
tains start and stop values, setpoints and other control values; items that must con-
tinuously 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 mas-
ter 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 termi-
nating resistor is usually used.
PE Protective earth; connecting point to which the earth of the network is connected.
PROFIBUS DP Decentralized periphery ('classic' fieldbus)

Appendix
Item Explanation
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. 29 : Terms and abbreviations used

List of Figures
List of Figures
Fig. 1 Automatic order list ............................................................................................................................. 34
Fig. 2 SIMATIC S7 HW Configurator [PROFIBUS] ....................................................................................... 166
Fig. 3 VPB 28020 PROFIBUS module layout drawing ................................................................................. 171
Fig. 4 Light-emitting diodes – VPB 28020 front view .................................................................................... 172
Fig. 5 VCB 28020 DeviceNet module layout drawing ................................................................................... 182
Fig. 6 VCB 28020:XC1 DeviceNet module front view ................................................................................... 183
Fig. 7 Program: SIMATIC S7 HW Config...................................................................................................... 193
Fig. 8 PROFINET star topology .................................................................................................................... 201
Fig. 9 PROFINET line topology .................................................................................................................... 202
Fig. 10 PROFINET ring topology .................................................................................................................... 202
Fig. 11 VCU 20100 Connecting VPN 28020 to VCU 20100 ........................................................................... 203
Fig. 12 VSS 28020 Modbus module layout drawing ....................................................................................... 237

List of Tables
List of Tables
Tab. 1 FIXED formats .................................................................................................................................... 18
Tab. 2 VARIABLE formats ............................................................................................................................. 28
Tab. 3 VARIABLE formats ............................................................................................................................. 34
Tab. 4 Master station → scales task identifier (TID) ..................................................................................... 35
Tab. 5 Reply identifiers (RID) scales master station ...................................................................................... 36
Tab. 6 Index in the parameter description (IND) - higher-value byte of the parameter index......................... 36
Tab. 7 error codes ......................................................................................................................................... 37
Tab. 8 Fieldbus commands ........................................................................................................................... 51
Tab. 9 Fieldbus preset values ........................................................................................................................ 57
Tab. 10 Fieldbus status ................................................................................................................................... 58
Tab. 11 Fieldbus measured values .................................................................................................................. 94
Tab. 12 Fieldbus Material Dependent Parameters .......................................................................................... 105
Tab. 13 Material-Dependent Parameters......................................................................................................... 129
Tab. 14 Event overview ................................................................................................................................... 150
Tab. 15 'Bus activation' connector ................................................................................................................... 171
Tab. 16 LED 'Operating Mode' (below) ............................................................................................................ 172
Tab. 17 LED 'Status' (above) ........................................................................................................................... 172
Tab. 18 Cable parameters ............................................................................................................................... 173
Tab. 19 Cable lengths per segment ................................................................................................................. 173
Tab. 20 'Bus activation' connector ................................................................................................................... 182
Tab. 21 LED 'Network Status' (above) ............................................................................................................. 183
Tab. 22 LED 'Module Status' (below)............................................................................................................... 183
Tab. 23 Fieldbus Presets Integer Format ........................................................................................................ 235
Tab. 24 Fieldbus Meas. Values Integer format ................................................................................................ 235
Tab. 25 Modbus module properties ................................................................................................................. 237
Tab. 26 Pin assignment Modbus serial interface ............................................................................................. 237
Tab. 27 Cable parameters ............................................................................................................................... 238
Tab. 28 Cable lengths per segment ................................................................................................................. 238
Tab. 29 Terms and abbreviations used ........................................................................................................... 258

Index
Index
Abbreviations in the List of Cyclical Data ................. 247 Fig. 2: SIMATIC S7 HW Configurator [PROFIBUS] .. 162
Acknowledging Event Messages.................................. 4 Fig. 3: VPB 28020 PROFIBUS module layout drawing
Actions Required of the External Controller ............. 246 ............................................................................. 167
Acyclic Data (Explicit Messages) EtherNet/IP .......... 206 Fig. 4: Light-emitting diodes – VPB 28020 front view168
Acyclic Data Exchange between PCS and Scales Fig. 5: VCB 28020 DeviceNet module layout drawing
Electronics............................................................ 209 ............................................................................. 176
Acyclic Data PROFINET .......................................... 196 Fig. 6: VCB 28020:XC1 DeviceNet module front view
Acyclic Services ............................................... 169, 195 ............................................................................. 177
Acyclical Data DeviceNet ......................................... 177 Fig. 7: Program: SIMATIC S7 HW Config................. 185
Acyclical Data Modbus ............................................. 216 Fig. 8: PROFINET star topology ............................... 193
Acyclical Data PROFIBUS ....................................... 169 Fig. 9: PROFINET line topology ............................... 193
Adjusting Capacity via Fieldbus ............................... 244 Five Safety Rules of Electrical Engineering .................. 6
Appendix .................................................................. 247 Format NO_PARA_ID_4_12 ...................................... 35
Application Relation ................................................. 190 Format of the Safety Notices ........................................ 5
Automatic Order List .................................................. 31 Function Codes (FC) ................................................ 213
Available Data - Listing....................................... 47, 226 Functionality of the DeviceNet Connection ............... 173
Caution ......................................................................... 5 Functionality of the Ethernet Connection .................. 201
Common Abbreviations ............................................ 247 Functionality of the Modbus-RTU Connection .......... 224
Configuration of the DeviceNet Connection ............. 173 Functionality of the Modbus-TCP Connection .......... 221
Configuration of the Ethernet Connection ................ 201 Functionality of the PROFIBUS Connection ............. 158
Configuration of the Modbus-RTU Connection......... 224 Functionality of the PROFINET Connection ............. 182
Configuration of the Modbus-TCP Connection ......... 221 General Information .......................... 7, 14, 23, 212, 224
Configuration of the PROFIBUS Connection............ 158 General Information for all Fieldbus Types ............... 231
Configuration of the PROFINET Connection ............ 183 General Payload Structure (VARIABLE Mode) .......... 23
Connecting the PROFINET IO Module to the Star General Telegram Structure ..................................... 212
Topology .............................................................. 194 Glossary ................................................................... 248
Connection to a star topology – VCU 20100 with board Guidelines for Commissioning .......... 157, 172, 200, 212
VPN8020 .............................................................. 194 Guidelines for Initial Startup ..................................... 181
Cyclical and Acyclical Data Exchanges ...................... 47 Highest Priority Event ................................................. 10
Damaged/Defective Electrical Components ................. 6 IDs (Identifiers) ............................................................. 9
Danger ......................................................................... 5 Illustration of the Telegram Bytes on Command ......... 12
Data Formats ........................................................... 214 Integrating the IO Device .......................................... 185
Data Segments ............................................................ 7 Integration Slave ...................................................... 161
Data Types (Numerical Notation) ................................. 8 Intended Use ................................................................ 3
Database ...................................................................... 7 Internal On-Stream Calibration System of a
Description of the Adjustment Steps ........................ 245 Weighfeeder (VWF) .............................................. 238
Design Modifications .................................................... 4 IP Address and Name for PROFINET IO Subscriber 187
DeviceNet................................................................. 172 Keeping the Technical Documentation ......................... 4
DeviceNet Interface VCB8020 ................................. 175 Layout of the Components ............... 167, 176, 190, 228
DeviceNet Master Settings (PCS) ............................ 175 LEDs H110, H120 ............................................ 168, 177
Diagnosis and Troubleshooting ................................ 231 LEDs in the Ethernet Connection (RJ45).................. 192
Dimensions ................................................................ 10 LEDs on the Board ................................................... 190
Ensuring Transmission ............................................. 215 Line Topology ........................................................... 193
Error Codes .............................................................. 214 Loss-in-Weight Feeder (VLW) Inlet Gate Control ..... 244
EtherNet/IP............................................................... 200 Material-Dependent Parameters (MDP) ........... 102, 126
EtherNet/IP Slave Settings ....................................... 201 MDP = Material-Dependent Parameters (Material-
Events - Overview .................................................... 147 Dependent Parameters) ....................................... 102
Example for 'Display Fixed Mode Configuration' ...... 210 Message Command ................................................. 209
Example of 'FIXED Mode' Telegram .......................... 21 Modbus (Serial and Network) ................................... 212
Example of 'Writing a Process or Parameter Value' . 209 Modbus Interface VSS8020...................................... 227
Example Telegrams 'Variable Mode' .......................... 35 Modbus RTU Master Settings .................................. 226
Examples of Telegrams (Process Values) ............... 215 Modbus-RTU ............................................................ 224
Explicit Messages .................................................... 209 Modbus-TCP ............................................................ 221
Explicit Messaging ....................................................... 7 Modbus-TCP Master Settings .................................. 223
Fieldbus Connections ............................................... 157 Moisture and humidity .................................................. 4
Fig. 1: Automatic order list.......................................... 32 Monitoring ID .............................................................. 30
Fig. 10: PROFINET ring topology ............................. 194 Notes for DeviceNet ................................................. 232
Fig. 11: VCU 20100 Connecting VPN 28020 to Notes for EtherNet/IP ............................................... 232
VCU 20100........................................................... 195 Notes for Modbus ..................................................... 233
Fig. 12: VSS 28020 Modbus module layout drawing 228 Notes for PROFIBUS DP.......................................... 231

Index
Notes for PROFINET IO ........................................... 232 Signal Words for Danger Warnings .............................. 4
Notice ........................................................................... 5 Signal Words for Usage Instructions ............................ 5
Order list..................................................................... 25 Simplified Payload Structure ...................................... 14
order list, automatic .................................................... 31 Some Examples of Applications ............................... 237
order list, normal ........................................................ 30 Star Topology ........................................................... 193
order list, variable ....................................................... 30 Strictly Observe ............................................................ 5
Overview ...................................................................... 1 Subscriber Addresses .............................................. 213
Parameter Changes ..................................................... 3 Supplementary Documentation 172, 180, 199, 211, 220
Parameter Range in Detail ......................................... 33 Tab.1: FIXED formats ................................................. 16
Parameter Transmission ............................................ 32 Tab.10: Fieldbus status .............................................. 91
Parameters............................................................... 216 Tab.11: Fieldbus measured values .......................... 102
Password ..................................................................... 3 Tab.12: Fieldbus Material Dependent Parameters ... 126
Payload .................................................................... 215 Tab.13: Material-Dependent Parameters ................. 147
Payload Scope and Content FIXED Mode ................. 15 Tab.14: Event overview ............................................ 156
Payload Scope and Content VARIABLE Mode .......... 25 Tab.15: 'Bus activation' connector ............................ 167
Payload Structure ....................................................... 14 Tab.16: LED 'Operating Mode' (below)..................... 168
Personnel ..................................................................... 3 Tab.17: LED 'Status' (above).................................... 168
Potential Sources of Danger ........................................ 3 Tab.18: Cable parameters ........................................ 168
Preset Values ............................................................. 48 Tab.19: Cable lengths per segment ......................... 169
Preset values INTEGER........................................... 226 Tab.2: VARIABLE formats .......................................... 26
PROFIBUS DP ......................................................... 157 Tab.20: 'Bus activation' connector ............................ 176
PROFIBUS Interface VPB8020 ................................ 166 Tab.21: LED 'Network Status' (above)...................... 177
PROFINET Interface VPN8020 ................................ 190 Tab.22: LED 'Module Status' (below) ....................... 177
PROFINET IO .......................................................... 181 Tab.23: Fieldbus Presets Integer Format ................. 226
PROFINET IO Module.............................................. 190 Tab.24: Fieldbus Meas. Values Integer format ......... 227
PROFINET IO Network Topology with VPN8020 ..... 192 Tab.25: Modbus module properties .......................... 228
Read process values (IEEE format) ........................... 91 Tab.26: Pin assignment Modbus serial interface ...... 228
Read status ................................................................ 55 Tab.27: Cable parameters ........................................ 229
Read values ............................................................... 55 Tab.28: Cable lengths per segment ......................... 229
Read values INTEGER (Measured values) .............. 226 Tab.29: Terms and abbreviations used .................... 249
Redundancy Manager 'Ring Manager' ..................... 194 Tab.3: VARIABLE formats .......................................... 32
Redundant Modbus-TCP.......................................... 223 Tab.4: Master station → scales task identifier (TID) ... 33
Replacing Components ................................................ 4 Tab.5: Reply identifiers (RID) scales master station . 34
Ring Topology .......................................................... 194 Tab.6: Index in the parameter description (IND) -
Safety higher-value byte of the parameter index ............... 34
Damage to Environment........................................... 5 Tab.7: error codes ...................................................... 35
Damage to property.................................................. 5 Tab.8: Fieldbus commands ........................................ 54
Safety instruction - Setup ......................................... 4 Tab.9: Fieldbus preset values .................................... 55
Signal word "Caution"............................................... 4 Taring a Loss-in-Weight Feeder (VLW) .................... 243
Signal word "Danger" ............................................... 4 Telegram Structure (Variable payload) ....................... 26
Signal word "Notice" ................................................. 5 User Data Diagnosis................................................. 233
Signal word "STRICTLY OBSERVE" ....................... 5 VARIABLE COMPATIBLE Format with PKW (Alter
Signal word "Warning".............................................. 4 Parameter) ............................................................. 39
Safety Information ........................................................ 3 VARIABLE COMPATIBLE Format with PKW ('Change
Serial Interfaces Pin Assignment ............................. 228 Parameter' - Text Parameter Type) ........................ 43
Service and Maintenance ............................................. 4 VARIABLE COMPATIBLE Format with PKW ('Change
Settings .................................................... 167, 176, 190 Parameter' with Error Reply) .................................. 41
Settings at the DeviceNet Slave ............................... 173 VARIABLE COMPATIBLE Format with PKW (Read
Settings at the EtherNet/IP Master (ControlLogix) ... 203 Parameter) ............................................................. 45
Settings at the Modbus-RTU Slave .......................... 224 VARIABLE COMPATIBLE Format without PKW (1)... 37
Settings at the Modbus-TCP Slave .......................... 221 VARIABLE COMPATIBLE Format without PKW (2)... 37
Settings at the PROFIBUS Slave ............................. 158 Warning ........................................................................ 5
Settings at the PROFIBUS-Master (PCS) ................ 160 Write commands ........................................................ 48
Settings at the PROFINET IO Controller .................. 184 Write process values (IEEE format)............................ 54
Settings at the PROFINET IO Device....................... 183 Zeroing and Taring a Weighfeeder (VWF)................ 237
Signal Words ................................................................ 4


Tersus Data Communication Programming Manual

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Tersus Data Communication Programming Manual

Încărcat de

Drepturi de autor:

Formate disponibile

DISOCONT® Tersus

Schenck Process Europe GmbH Schenck Process LLC

Stock Equipment Company Inc. Schenck Process Pty Ltd

(63050394994737163 V8, 19/07/2017)

2 Safety Information .....................................................................................................................................3

4 Fieldbus Connections .......................................................................................................................... 161

DISOCONT® Tersus Data Communication, Programming Manual BV-H2448GB, V8

4.2.3.1 Settings at the DeviceNet Slave ................................................................................................179

5 Diagnosis and Troubleshooting ......................................................................................................... 239

BV-H2448GB, V8 DISOCONT® Tersus Data Communication, Programming Manual

5.4 Notes for PROFINET IO .....................................................................................................................240

6 Some Examples of Applications ......................................................................................................... 245

7 Appendix ............................................................................................................................................... 257

Index ...................................................................................................................................................... 264

DISOCONT® Tersus Data Communication, Programming Manual BV-H2448GB, V8

What is described in this manual?

DISOCONT® Tersus Data Communication, Programming Manual BV-H2448GB, V8

Overview of supplementary manuals

BV-H2406 System Manual

BV-H2448GB, V8 DISOCONT® Tersus Data Communication, Programming Manual

Potential Sources of Danger

DISOCONT® Tersus Data Communication, Programming Manual BV-H2448GB, V8

Acknowledging Event Messages

Service and Maintenance

Moisture and humidity

Keeping the Technical Documentation

BV-H2448GB, V8 DISOCONT® Tersus Data Communication, Programming Manual

2.1 Signal Words

Format of the Safety Notices

DISOCONT® Tersus Data Communication, Programming Manual BV-H2448GB, V8

2.1.2 Signal Words for Usage Instructions

2.2 Five Safety Rules of Electrical Engineering

BV-H2448GB, V8 DISOCONT® Tersus Data Communication, Programming Manual

2.3 Damaged/Defective Electrical Components

DISOCONT® Tersus Data Communication, Programming Manual BV-H2448GB, V8

3.1 General Information

3.1.1 Data Segments

Commands (Bit or byte information)

Preset values (FLOAT format)

Status and event information (Bit or byte information)

Measured values (FLOAT format)

► Acyclic Data (Explicit Messaging):

Strings e.g. device name

DISOCONT® Tersus Data Communication, Programming Manual BV-H2448GB, V8

3.1.2 Data Types (Numerical Notation)

FLOAT Sign/Exponent Mantissa 1 Mantissa 2 Mantissa 3

Further examples of floating-point numbers

BV-H2448GB, V8 DISOCONT® Tersus Data Communication, Programming Manual

► Integer values (INTEGER)

Type 1st Byte 2nd Byte 3rd Byte 4th Byte

INT16 0 0 X (MSB) X (LSB)

BIT *) Word (x) HI Word (x) LO Word (x+1) HI Word (x+1) LO

► Character string (STRING)

Character ASCII code (hex)

DISOCONT® Tersus Data Communication, Programming Manual BV-H2448GB, V8

3.1.3 IDs (Identifiers)

Type 1st Byte 2nd Byte

hexadecimal: 0x20 0x0160

BV-H2448GB, V8 DISOCONT® Tersus Data Communication, Programming Manual

3.1.5 Highest Priority Event

Word (x) HI Word (x) LO Word (x+1) HI Word (x+1) LO

Conditions: ▪ Event is still pending

Status 52 is coded as follows:

Bit: 7 … 4 Bit: 3 … 0 Bit: 7 … 4 Bit: 3 … 0