BVH 2448 GB

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-eu@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.
(81064793504219147 V10, 17/09/2018)

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 ..............................................................................................5
2.2 Five Safety Rules of Electrical Engineering ...........................................................................................6
2.3 Damaged/Defective Electrical Components ...........................................................................................6
3 Database.....................................................................................................................................................7
3.1 General Information ................................................................................................................................7
3.1.1 Data Segments ..............................................................................................................................7
3.1.2 Data Types (Numerical Notation) ...................................................................................................8
3.1.3 IDs (Identifiers) .............................................................................................................................10
3.1.4 Dimensions...................................................................................................................................10
3.1.5 Highest Priority Event ...................................................................................................................10
3.1.6 Illustration of the Telegram Bytes on Command ..........................................................................12
3.2 Payload Structure .................................................................................................................................14
3.2.1 Simplified Payload Structure ........................................................................................................15
3.2.1.1 General Information .....................................................................................................................15
3.2.1.2 Payload Scope and Content FIXED Mode...................................................................................15
3.2.1.3 Example of 'FIXED Mode' Telegram ............................................................................................22
3.2.2 General Payload Structure (VARIABLE Mode)............................................................................25
3.2.2.1 General Information .....................................................................................................................25
3.2.2.2 Payload Scope and Content VARIABLE Mode ...........................................................................26
3.2.2.3 Telegram Structure (Variable payload) ........................................................................................28
3.2.2.4 Parameter Transmission ..............................................................................................................34
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) ....................................................................................107
3.3.3 Events - Overview ......................................................................................................................108
4 Fieldbus Connections .......................................................................................................................... 123

4.1 PROFIBUS DP ...................................................................................................................................123
4.1.1 Guidelines for Commissioning ...................................................................................................124
4.1.2 Functionality of the PROFIBUS Connection ..............................................................................124
4.1.3 Configuration of the PROFIBUS Connection .............................................................................125
4.1.3.1 Settings at the PROFIBUS Slave ...............................................................................................125
4.1.3.2 Settings at the PROFIBUS-Master (PCS)..................................................................................126
4.1.4 PROFIBUS Interface VPB8020 .................................................................................................134
4.1.5 Acyclic Services .........................................................................................................................136
4.1.5.1 Acyclical Data PROFIBUS .........................................................................................................137
4.1.6 Supplementary Documentation ..................................................................................................140
4.2 DeviceNet ...........................................................................................................................................140
4.2.2 Functionality of the DeviceNet Connection ................................................................................141
4.2.3 Configuration of the DeviceNet Connection ...............................................................................141
4.2.3.1 Settings at the DeviceNet Slave ................................................................................................141
DISOCONT® Tersus Data Communication, Programming Manual BV-H2448GB, V10

Schenck Process Group -i-
Table of Contents
4.2.3.2 DeviceNet Master Settings (PCS) ..............................................................................................143

4.2.4 DeviceNet Interface VCB8020 ...................................................................................................144
4.2.5 Acyclical Data DeviceNet ...........................................................................................................146
4.3 PROFINET IO .....................................................................................................................................149
4.3.1 Guidelines for Initial Startup .......................................................................................................150
4.3.2 Functionality of the PROFINET Connection ..............................................................................151
4.3.3 Configuration of the PROFINET Connection .............................................................................152
4.3.3.1 Settings at the PROFINET IO Device ........................................................................................152
4.3.3.2 Settings at the PROFINET IO Controller ...................................................................................153
4.3.4 PROFINET Interface VPN8020 .................................................................................................159
4.3.4.1 PROFINET IO Module ...............................................................................................................159
4.3.4.2 PROFINET IO Network Topology with VPN8020 ......................................................................162
4.3.4.3 Connecting the PROFINET IO Module to the Star Topology ....................................................164
4.3.5 Acyclic Services .........................................................................................................................165
4.3.5.1 Acyclic Data PROFINET ............................................................................................................166
4.4 EtherNet/IP .........................................................................................................................................170
4.4.2 Functionality of the Ethernet Connection ...................................................................................171
4.4.3 Configuration of the Ethernet Connection ..................................................................................171
4.4.3.1 EtherNet/IP Slave Settings.........................................................................................................171
4.4.3.2 Settings at the EtherNet/IP Master (ControlLogix) .....................................................................173
4.4.4 Acyclic Data (Explicit Messages) EtherNet/IP ...........................................................................177
4.4.4.1 Acyclic Data Exchange between PCS and Scales Electronics..................................................179
4.5 Modbus (Serial and Network) .............................................................................................................183
4.5.1 General Information ...................................................................................................................183
4.5.1.1 Guidelines for Commissioning ...................................................................................................183
4.5.1.2 General Telegram Structure.......................................................................................................184
4.5.1.3 Subscriber Addresses ................................................................................................................184
4.5.1.4 Function Codes (FC) ..................................................................................................................185
4.5.1.5 Error Codes ................................................................................................................................186
4.5.1.6 Data Formats .............................................................................................................................186
4.5.1.7 Ensuring Transmission...............................................................................................................186
4.5.1.8 Payload ......................................................................................................................................187
4.5.1.9 Examples of Telegrams (Process Values) .................................................................................187
4.5.1.10 Parameters .................................................................................................................................188
4.5.1.11 Acyclical Data Modbus ...............................................................................................................189
4.5.1.12 Supplementary Documentation ..................................................................................................192
4.5.2 Modbus-TCP ..............................................................................................................................193
4.5.2.1 Functionality of the Modbus-TCP Connection ...........................................................................193
4.5.2.2 Configuration of the Modbus-TCP Connection ..........................................................................193
4.5.2.3 Redundant Modbus-TCP ...........................................................................................................196
4.5.3 Modbus-RTU ..............................................................................................................................196
4.5.3.1 General Information ...................................................................................................................196
4.5.3.2 Functionality of the Modbus-RTU Connection ...........................................................................197
4.5.3.3 Configuration of the Modbus-RTU Connection ..........................................................................197
4.5.3.4 Available Data - Listing ..............................................................................................................199
4.5.3.5 Modbus Interface VSS8020 .......................................................................................................201
5 Diagnosis and Troubleshooting ......................................................................................................... 203

5.1 General Information for all Fieldbus Types ........................................................................................203
5.2 Notes for PROFIBUS DP ....................................................................................................................203
5.3 Notes for DeviceNet ...........................................................................................................................204
5.4 Notes for PROFINET IO .....................................................................................................................204
BV-H2448GB, V10 DISOCONT® Tersus Data Communication, Programming Manual

- ii - Schenck Process Group
Table of Contents
5.5 Notes for EtherNet/IP .........................................................................................................................204

5.6 Notes for Modbus ...............................................................................................................................205
5.7 User Data Diagnosis ...........................................................................................................................205
6 Some Examples of Applications ......................................................................................................... 209

6.1 Zeroing and Taring a Weighfeeder (VWF) .........................................................................................209
6.2 Internal On-Stream Calibration System of a Weighfeeder (VWF)......................................................211
6.3 Taring a Loss-in-Weight Feeder (VLW)..............................................................................................216
6.4 Loss-in-Weight Feeder (VLW) Inlet Gate Control...............................................................................217
7 Appendix ............................................................................................................................................... 219

7.1 Common Abbreviations ......................................................................................................................219
7.2 Abbreviations in the List of Cyclical Data ...........................................................................................220
7.3 Glossary..............................................................................................................................................221
Index ...................................................................................................................................................... 227

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:
▪ 'Classic' fieldbus: PROFIBUS DP1), DeviceNet1) and Modbus-RTU1)
▪ Ethernet based fieldbus (Industrial Ethernet): PROFINET IO2), EtherNet/IP3) and Modbus-TCP3)
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-H2185 Schenck Process EasyServe

BV-H2406 System Manual
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-H2591 Instruction manual for loss-in-weight feeder VLW
BV-H2615 Instruction manual for weighfeeder VWF
BV-H2623 Instruction manual for MULTICOR feeder VWC

-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
2.1.2 Signal Words for Usage Instructions

Strictly Observe
The signal words STRICTLY OBSERVE identify situations from which material or environmental damage
could arise.
For example:
STRICTLY OBSERVE
Welding on load-bearing parts

Safety Information
Note
The signal word NOTE is used to highlight information on using the product economically and at an optimal
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 to 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. Electrically isolate the components.
2. Secure against restart.
3. Ensure components are de-energized.
4. For voltages above 1 kV: Ground and short-circuit cables.
5. Cover or shield adjacent, live components.
2.3 Damaged/Defective Electrical Components

DANGER
Live damaged or defective components
Danger to life from electric shock.
1. Get specialized staff to ensure that all live components are undam-
aged and fault-free.
2. Have damaged or defective electrical components replaced by spe-
cialized staff.

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

Database
INT16 0 0 X (MSB) X (LSB)

INT32 (LONG) X (MSB) X X X (LSB)
NOTES:
The existing protocol-dependent parameters Word Sequence and Byte Sequence affect only the transfer of
floating-point numbers and UINT32 parameter values via fieldbus. The standard setting always corresponds
to 'Big Endian'.
All fieldbus protocols can operate with double words, Modbus can also use 16 bit words.
► Bit coded information (BIT)
Bits are compiled together into double words (PROFIBUS DP, DeviceNet, PROFINET IO) or words (Modbus-
RTU/TCP).
MSB LSB
BIT *) Word(x) HI Word(x) LO Word(x+1) HI Word(x+1) LO

Examples
Command ID:
0x0140 Command4 HI Command4 LO Command5 HI Command5 LO
Status ID:
0x02F0 Status2 HI Status2 LO Status3 HI Status3 LO
*) information per bit ('bit coded')
► Character string (STRING)

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

Database
3.1.3 IDs (Identifiers)

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

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

Status 52 HI Status 52 LO Status 53 HI Status 53 LO
Conditions: ▪ Event is still pending

▪ Byte order: Big Endian

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

Schenck Process Group - 11 -
Database
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'.
3.1.6 Illustration of the Telegram Bytes on Command

e.g. DISOCONT Tersus

Database

Database
3.2 Payload Structure

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

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

Database
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

Database
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 'Relea-
se'
Bytes 5-8 00 00 00 00 Command 06+07 *) 352 / 0x0160 (No command active)
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

Database
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 using Configu-
ration, 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 De-
viceNet 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

Fully Variable PPO Type (parameter controlled):

Parameter 'Configuration' = 'VARIABLE COMPATIBLE'

Database
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
Depending on the parameters set, the fieldbus message therefore can be expanded gradually by as many
IDs as required by the current application.

Database
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
0x09FChex (2556dez). The varied read IDs provide valid data if the value of the monitoring ID has
changed.
▪ If an ID is identified as incorrect, its value in the reply will be set to zero.
▪ Parameter transmission (PKW range): IDs from chapter »Material-Dependent Parameters (MDP) [➙
107]« 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.
Example 1: Data transmission without parameters and without user-defined read IDs (order list)
(The preset value IDs used are intended as examples only)

Database
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

Database
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'.
3.2.2.4 Parameter Transmission

The use of parameter IDs is described in the chapter »General Information [➙7]«. 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

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

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

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

Database
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]
*)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.

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

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

Database
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
B) Determining parameter range (PKW)
1. Parameter ID (PKE)
The parameter has the ID '4613/0x1205' and its value is to be changed.
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.

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

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

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

Database
014a 00330 A - Moisture OFF (D) * * * * *

014b 00331 B - Stop Wheel (D) * *
014c 00332 C - PLS Gate Feedback (S) *
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 - CANCEL Check Meas. (D) * * * * *
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) * * * * *

Database
0168 00360 8 - Automatic Bin Control (D) * * * * * *

0169 00361 9 - Manual Bin Control (D) * * * * * *
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) * * * * * * *

Database
0187 00391 7 - DO: PLC 8 (S) * * * * * * *

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-

Database
01a5 00421 5-
01a6 00422 6-
01a7 00423 7-
01a8 00424 8-
01a9 00425 9-
01aa 00426 A - Reset batch total (D) *

01ab 00427 B - Echo: Bin Filling 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-

Database
01c8 00456 8-
01c9 00457 9-
01ca 00458 A-
01cb 00459 B - Start Data Logging (D) * * * * * * *

01cc 00460 C - Stop Data Logging (D) * * * * * * *
01cd 00461 D - Clear Data Log File (D) * * * * * * *
01ce 00462 E-
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-

Database
01e6 00486 6-
01e7 00487 7-
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

Database
hex dec Default Value Dimension VLW VWF VBW VMC VSF VIF VBC
027a 00634
027c 00636
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 * * * * *

Database
0300 00768 0 - Batch selected * * * * * *

0301 00769 1 - Batch active * * * * * *
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 System * * * *

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

Database
031f 00799 F - Bin Level MIN * * * * * *

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 Meas. * * * * *
032f 00815 F - Check Meas. 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 * * * * * *

Database
033d 00829 D - CO: BIN Controller Optimization * * * * *

033e 00830 E - 2nd Bridge MAX *
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 * * * * * * *

Database
035b 00859 B - Totalizer 1 Output * * * * * *

035c 00860 C - No Deviation * * * * *
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

Database
0377 00887 7 - Event: Cyclic Communication SY08 (W2) * * * * * * *

0378 00888 8 - Event: EtherNet/IP not licensed
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) * * * * * * *

Database
0393 00915 3 - Event: NAMUR Error VCU2-DI6 WE04 (W2) * * * * * *


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-

Database
03b1 00945 1-
03b2 00946 2 - Event: Feed Air MIN MF03 (W2) * *
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: No Release 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 – Event: Communic. Bluetooth IL07 (W2) *

Channel 1
03c7 00967 7 - Event: Communic. Bluetooth IL08 (W2) *
Channel 2
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 - Event: Adjustment terminated IL13 (W2) * * * * * * *
03cd 00973 D - Event: Protection Interlocking not IL14 (W2) *

act.

Database
03ce 00974 E - Event: No Bin-Cone-Aeration IL15 (W2) *

Release
03cf 00975 F-
03d0 00976 0 - Event: Controller Limited CO01 (W2) * * * * *
03d1 00977 1 - Event: Flow Gate MIN CO02 (W2) * * *

03d2 00978 2 - Event: Flow Gate MAX CO03 (W2) * * *
03d3 00979 3 - Event: Bin Level MAX Sensor CO04 (W2) * * * * * *
03d4 00980 4 - Event: Volum. caused by LC-error CO05 (W2) * *

03d5 00981 5 -Event: Flow Gate MAX (B) CO06 (W2) * *
03d6 00982 6-
03d7 00983 7-
03d8 00984 8-
03d9 00985 9 - Event: Flow Gate MIN (B) CO10 (W2) *

03da 00986 A - Event: Correction MAX CO11 (W2) *
03db 00987 B - Event: Limit Gain CO12 (W2) *

03dc 00988 C - Event: ShakeControl VVC CO13 (W2) *
03dd 00989 D - Event: Helix Speed Limited CO14 (W2) *
03de 00990 E - Event: Intermediate circuit volt- CO15 (W2) *

age VVC
03df 00991 F - Event: Short circuit VVC CO16 (W2) *

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: Bin Filling Not Stopped CH08 (W2) * * * * *
03e8 01000 8 - Event: No Check Enable CH09 (W2) * * * * *

Database
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 Silo CH14 (W2) *

03ee 01006 E - Event: Check Setpoint MIN 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: Pressure Transmitter fault 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) * *

Database
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) * * * * * *
040b 01035 B - Event: Bin Level MAX HI12 (W2) *
040c 01036 C - Event: FC-MAX Limit HI13 (W2) * * *

040d 01037 D - Event: Pressure Transmitter > HI14 (W2) * * * * *
MAX
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: Pressure Transmitter < LO10 (W2) * * * * *

MIN
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

Database

0426 01062 6 - Event: Communication VHM SY07 (W1) * * * * * * *

serial
0427 01063 7 - Event: Cyclic Communication SY08 (W1) * * * * * * *

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

Database
0440 01088 0 - Event: Power Failure WE01 (W1) * * * * * * *


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

Database
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) * *
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: No Release 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 - Event: Communic. Bluetooth IL07 (W1) *
Channel 1
0477 01143 7 - Event: Communic. Bluetooth IL08 (W1) *
Channel 2
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) * * * * * * *

Database
047b 01147 B-
047c 01148 C - Event: Adjustment terminated IL13 (W1) * * * * * * *
047d 01149 D - Event: Protection Interlocking not IL14 (W1) *

act.
047e 01150 E - Event: No Bin-Cone-Aeration IL15 (W1) *
Release
047f 01151 F-
0480 01152 0 - Event: Controller Limited CO01 (W1) * * * * *
0481 01153 1 - Event: Flow Gate MIN CO02 (W1) * * *
0482 01154 2 - Event: Flow Gate MAX CO03 (W1) * * *

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

048a 01162 A - Event: Correction MAX CO11 (W1) *
048b 01163 B - Event: Limit Gain CO12 (W1) *
048c 01164 C - Event: ShakeControl VVC CO13 (W1) *

048d 01165 D - Event: Helix Speed Limited CO14 (W1) *
048e 01166 E - Event: Intermediate circuit volt- CO15 (W1) *
age VVC
048f 01167 F - Event: Short circuit VVC CO16 (W1) *
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

Database
0497 01175 7 - Event: Bin Filling 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 Silo CH14 (W1) *

049e 01182 E - Event: Check Setpoint MIN 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: Pressure Transmitter fault 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: Error LC Input 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) * *

Database
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) * * * * * *
04bb 01211 B - Event: 2nd Bridge MAX HI12 (W1) *
04bc 01212 C - Event: FC-MAX Limit HI13 (W1) * * *

04bd 01213 D - Event: Pressure Transmitter > HI14 (W1) * * * * *
MAX
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: Pressure Transmitter < LO10 (W1) * * * * *
MIN
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) * * * * * * *

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

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

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


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-

Database
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) * *
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: No Release 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 - Event: Communic. Bluetooth IL07 (A)

Channel 1
0527 01319 7 - Event: Communic. Bluetooth IL08 (A)
Channel 2
0528 01320 8 - Event: Filling disabled IL09 (A) *

Database
0529 01321 9 - Event: FCB-Error IL10 (A) * * * * * * *

052a 01322 A - Event: Wrong System Time IL11 (A) * * * * * * *
052b 01323 B- IL12 (A)
052c 01324 C - Event: Adjustment terminated IL13 (A) * * * * * * *

052d 01325 D - Event: Protection Interlocking not IL14 (A) *
act.
052e 01326 E - Event: No Bin-Cone-Aeration IL15 (A) *
Release
052f 01327 F-
0530 01328 0 - Event: Controller Limited CO01 (A) * * * * *

0531 01329 1 - Event: Flow Gate MIN CO02 (A) * * *
0532 01330 2 - Event: Flow Gate MAX CO03 (A) * * *
0533 01331 3 - Event: Bin Level MAX Sensor CO04 (A) * * * * * *
0534 01332 4 - Event: Volum. caused by LC-error CO05 (A) * *
0535 01333 5 -Event: Flow Gate MAX (B) CO06 (A) * *

0536 01334 6-
0537 01335 7-
0538 01336 8-
0539 01337 9 - Event: Flow Gate MIN (B) CO10 (A) *
053a 01338 A - Event: Correction MAX CO11 (A) *

053b 01339 B - Event: Limit Gain CO12 (A) *
053c 01340 C - Event: ShakeControl VVC CO13 (A) *
053d 01341 D - Event: Helix Speed Limited CO14 (A) *
053e 01342 E - Event: Intermediate circuit volt- CO15 (A) *
age VVC
053f 01343 F - Event: Short circuit VVC CO16 (A) *
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

Database
0545 01349 5 - Event: Absolute Span Correction CH06 (A) * * * * *

Error
0546 01350 6 - Event: Relative Span Correction CH07 (A) * * * * *

Error
0547 01351 7 - Event: Bin Filling 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 Silo CH14 (A) *
054e 01358 E - Event: Check Setpoint MIN 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: Pressure Transmitter fault 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) * * * * * * *

Database
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) * * * * * *
056b 01387 B - Event: 2nd Bridge MAX HI12 (A) *
056c 01388 C - Event: FC-MAX Limit HI13 (A) * * *
056d 01389 D - Event: Pressure Transmitter > HI14 (A) * * * * *
MAX
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: Pressure Transmitter < LO10 (A) * * * * *

MIN
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-

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

Database
059d 01437 D-
059e 01438 E-
059f 01439 F-
05a0 01440 0 - DO1 * * * * * * *
05a1 01441 1 - DO2 * * * * * * *
05a2 01442 2 - DO3 * * * * * * *

05a3 01443 3 - DO4 * * * * * * *
05a4 01444 4 - DO5 * * * * * * *
05a5 01445 5 - DO6 * * * * * * *

05a6 01446 6 - DO7 * * * * * * *
05a7 01447 7 - DO8 * * * * * * *
05a8 01448 8-
05a9 01449 9-
05aa 01450 A-
05ab 01451 B-
05ac 01452 C-
05ad 01453 D-
05ae 01454 E-
05af 01455 F-
05b0 01456 0 - 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-

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

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

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

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

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

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


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

Database
06c4 01732 4-
06c5 01733 5-
06c6 01734 6-
06c7 01735 7-
06c8 01736 8-
06c9 01737 9-
06ca 01738 A-
06cb 01739 B-
06cc 01740 C-
06cd 01741 D-
06ce 01742 E-
06cf 01743 F-
06d0 01744 0 - 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-

Database
06e1 01761 1-
06e2 01762 2-
06e3 01763 3-
06e4 01764 4-
06e5 01765 5-
06e6 01766 6-
06e7 01767 7-
06e8 01768 8-
06e9 01769 9-
06ea 01770 A-
06eb 01771 B-
06ec 01772 C-
06ed 01773 D-
06ee 01774 E-
06ef 01775 F-
06f0 01776 0 - 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-

Database
0700 01792 0-
0701 01793 1-
0702 01794 2-
0703 01795 3-
0704 01796 4-
0705 01797 5-
0706 01798 6-
0707 01799 7-
0708 01800 8-
0709 01801 9-
070a 01802 A-
070b 01803 B-
070c 01804 C-
070d 01805 D-
070e 01806 E-
070f 01807 F-
0710 01808 0 - FB Event 01 * * * * * * *
0711 01809 1 - FB Event 02 * * * * * * *

0712 01810 2 - FB Event 03 * * * * * * *
0713 01811 3 - FB Event 04 * * * * * * *
0714 01812 4 - FB Event 05 * * * * * * *
0715 01813 5 - FB Event 06 * * * * * * *
0716 01814 6 - FB Event 07 * * * * * * *
0717 01815 7 - FB Event 08 * * * * * * *

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

Database
071e 01822 E - FB Event 15 * * * * * * *

071f 01823 F - FB Event 16 * * * * * * *
0720 01824 0 - FB Event 17 * * * * * * *

0721 01825 1 - FB Event 18 * * * * * * *
0722 01826 2 - FB Event 19 * * * * * * *
0723 01827 3 - FB Event 20 * * * * * * *

0724 01828 4 - FB Event 21 * * * * * * *
0725 01829 5 - FB Event 22 * * * * * * *
0726 01830 6 - FB Event 23 * * * * * * *

0727 01831 7 - FB Event 24 * * * * * * *
0728 01832 8 - FB Event 25 * * * * * * *

0729 01833 9 - FB Event 26 * * * * * * *
072a 01834 A - FB Event 27 * * * * * * *
072b 01835 B - FB Event 28 * * * * * * *
072c 01836 C - FB Event 29 * * * * * * *
072d 01837 D - FB Event 30 * * * * * * *
072e 01838 E - FB Event 31 * * * * * * *
072f 01839 F - FB Event 32 * * * * * * *
0730 01840 0 - 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 * * * * * * *

Database
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 * * * * * * *
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 * * * * * * *
6370 25456 0 - Event: VCU23160-Measure Unit SY17 (W2) *

VME
6372 25458 2 - Event: IP Address Conflict SY19 (W2) * * * * * * *
6380 25472 0 –Event: External Event 5 SC17 (W2) *
6381 25473 1 - Event: External Event 6 SC18 (W2) *
63d0 25552 0 - Event: Overcurrent VVC CO17 (W2) *

63d1 25553 1 - Event: Outside Frequency VVC CO18 (W2) *
63d2 25554 2 - Event: Sensor error MEMS VVC CO19 (W2) *
63d3 25555 3 - Event: Deviation VVC CO20 (W2) *

Database
63d4 25556 4 - Event: Parametrization VVC CO21 (W2) *

63d5 25557 5 - Event: Sensor ID VVC CO22 (W2) *
6400 25600 0 -Event: Deviation (Pre-Warning) HI17 (W2) * * *

6401 25601 1 -Event: Feed Pressure MAX HI18 (W2) *
6411 25617 0 - Event: Feed Pressure MIN LO18 (W2) *
6420 25632 0 - Event: VCU23160-Measure Unit SY17 (W1) *

VME
6422 25634 2 - Event: IP Address Conflict SY19 (W1) * * * * * * *
6480 25728 0 - Event: Overcurrent VVC CO17 (W1) *
6481 25729 1 - Event: Outside Frequency VVC CO18 (W1) *

6482 25730 2 - Event: Sensor error MEMS VVC CO19 (W1) *
6483 25731 3 - Event: Deviation VVC CO20 (W1) *
6484 25732 4 - Event: Parametrization VVC CO21 (W1) *

6485 25733 5 - Event: Sensor ID VVC CO22 (W1) *
64b0 25776 0 - Event: Deviation (Pre-Warning) HI17 (W1) * *
64b1 25777 1 - Event: Feed Pressure MAX HI18 (W1) *
64c1 25793 1 - Event: Feed Pressure MIN LO18 (W1) *
64d0 25808 0 - Event: VCU23160-Measure Unit SY17 (A) *

VME
64d2 25810 2 - Event: IP Address Conflict SY19 (A) * * * * * * *
64e0 25824 0 - Event: External Event 5 SC17 (A) *

64e1 25825 1 - Event: External Event 6 SC18 (A) *
6530 25904 0 - Event: Overcurrent VVC CO17 (A) *

Database
6531 25905 1 - Event: Outside Frequency VVC CO18 (A) *

6532 25906 2 - Event: Sensor error MEMS VVC CO19 (A) *
6533 25907 3 - Event: Deviation VVC CO20 (A) *
6534 25908 4 - Event: Parametrization VVC CO21 (A) *

6535 25909 5 - Event: Sensor ID VVC CO22 (A) *
6560 25952 0 - Event: Deviation (Pre-Warning) HI17 (A) * *

6561 25953 1 - Event: Feed Pressure MAX HI18 (A) *
6571 25969 1 -Event: Feed Pressure MIN LO18 (A) *
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 % * * * * *

Database
0774 01908 Corrected Feedrate kg/h * * * * *

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 *

Database
07b8 01976 Bypass Adaptation *

07ba 01978
07bc 01980
07be 01982
07c0 01984 CFC: Measurement Time s *
07c2 01986 CFC: Number of Measurements *
07c4 01988 CFC: Current No *

07c6 01990 CFC: Mean Delta-F kg *
07c8 01992 CFC: Mean Flow Rate kg/h *
07ca 01994 CFC: Feed Constancy % *

07cc 01996 Nominal Belt Load kg/m * *
07ce 01998 CFC: Feed Constancy g *
07d0 02000 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 % * * * * *

Database
07fc 02044 Relative Load % * *

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

Database
0840 02112
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 Pressure Bar * * * *
087e 02174 Pressure: Raw mV/V * * * *

0880 02176 Frequence DI_7 Hz * *
0882 02178

Database
0884 02180
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

Database
08c8 02248
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 Belt Motion Counter
0908 02312 Digital Mode output
090a 02314 CPU Temperature °C * * * * * * *

Database
090c 02316 Belt Speed % * *

090e 02318 Totalizer 1 rounded
0910 02320 LC-Raw Helixinlet mV/V *
0912 02322 Beladung Abzug
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 *

Database
0950 02384 TN_act s *

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 *

Database
1d14 07444 QA-Setpoint kg/m *

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 Loadcell LCT
1d34 07476 Actual Tare 2
1d36 07478 Actual Tare LCT
1d38 07480 Belt Load Unlin. 2
1d3a 07482 Utilization LCT
1d3c 07484 Belt Load Unlin. LCT
1d3e 07486 Delta W2-W1 filtered
1d40 07488 Delta W2-W1
1d42 07490 Residual Runtime
1d44 07492 Tare Error LCT (MV)
1d46 07494 Deviation QC/QS -1
1d48 07496 Loadcell 1 (delayed)
1d4a 07498 Rotation Speed IDMS 1/min *
1d4c 07500 Rotation Speed Rel. % *
1d4e 07502 Feeding Pressure Bar *
1d50 07504 Scale 1
1d52 07506 Scale 2
1d54 07508 Delta W2 - W1 (QC)
1d56 07510 Tare Error Scale 0

Database
1d58 07512 Belt Load Tare-Scale
1d5a 07514 Belt Load Scale 1
1d5c 07516 Belt Load Scale 2
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 Exciter % *
1d8c 07564 Voltage Max
1d8e 07566 Belt Length m *
1d90 07568 Load kg *
1d92 07570 B: virtual Buffer kg * *
1d94 07572 Bin Load Adaption % * *
1d96 07574 B: Coefficient (raw) %/mA * *

1d98 07576 Controller Mag. Yb delayed mA *
1d9a 07578 Controller Mag. Yb Mean mA *

Database
1d9c 07580 Perc. Controller Magnitude % *

1d9e 07582 B: calculated infeed *
1da8 07592 Total Motor Rotations *
1db4 07604 VME LC mV/V *
1db6 07606 VME Temp. °C *
1db8 07608 VME: Cycle Time ms *

1dbe 07614 Controller Mag. Yb (raw) mA * *
1dc0 07616 P-QA-Setpoint % *
1dc2 07618 Deviation Belt Load kg/h *

1dc4 07620 VME: Response Time ms *
1dc6 07622 Feedrate (raw) kg/h *
1dc8 07624 Feed Pressure bar *
1dcc 07628 Feedrate_F kg/h *
1dce 07630 Controller Coefficient (kg/h) /mA *
1dd0 07632 Bypass Factor *
1dd2 07634 Feed Pressure Load kg *
1dd4 07636 B: Coefficient (kg/h) /mA *
1dd6 07638 Controller Mag. YV % *
1dd8 07640 Controller Mag. YR % *
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.
The allocation of parameters in the basic parameter set to the parameter in the material-dependent set takes
place via Parameter Block 35.
50 materials can be defined. 32 parameters can be defined for each material. The ID numbers for parameter
N in material M are calculated as follows:
ID = 31024 + 32 * (M – 1) + (N – 1)

Database
3.3.3 Events - Overview
Software
Identifier Event VLW VWF VBW VMC VSF VIF VBC
SY System
message
SY01 Event: Me- P08.15 P07.09 P07.06 P07.14 P07.14 P07.14 P07.06
mory Error
SY02 Event: P01.06 P01.06 P01.06 P01.06 P01.06 P01.06 P01.06
Communi-
cation
VCU20100-
Unit 2
SY03 Event: P01.10 P01.10 P01.10 P01.10 P01.10 P01.10 P01.10
Communi-
cation
VCU20100-
Unit 3
SY04 Event: P02.06 P02.06 P02.06 P02.06 P02.06 P02.06 P02.06
Communi-
cation HMI
1
SY05 Event: P02.08 P02.08 P02.08 P02.08 P02.08 P02.08 P02.08
Communi-
cation HMI
2
SY06 Event: P02.10 P02.10 P02.10 P02.10 P02.10 P02.10 P02.10
Communi-
cation HMI
3
SY07 Event: P02.11 P02.11 P02.11 P02.11 P02.11 P02.11 P02.11
Communi-
cation VHM
serial
SY08 Event: Cycl. P21.03 P20.03 P19.03 P18.03 P16.03 P18.03 P16.03
communi-
cation
SY09
SY10 Event: P21.04 P20.04 P19.04 P18.04 P16.04 P18.04 P16.04
Acyclical
Communi-
cation

Database
Software
SY11
SY12
SY13 Event: P05.12
Bluetooth
connection
interrupted
SY14
SY15 Event: P01.13 P01.13 P01.13 P01.13 P01.13 P01.13 P01.13
Communi-
cation
VMO20100
-Unit 1
SY16 Event: P01.15 P01.15 P01.15 P01.15 P01.15 P01.15 P01.15
Communi-
cation
VMO20100
-Unit 2
SY17 Event: P01.17
VCU23160
measuring
unit VME
SY18
SY19 Event: IP P21.25 P20.25 P18.25
address
conflict
SC Sequence
monitoring
SC01 Event: Set- P08.07 P07.07 P07.06 P07.07 P07.06
point limited
SC02 Event: P08.01 P07.01 P07.01 P07.01 P07.01
Standby
SC03 Event: Sca- P19.04 P16.04 P15.04 P16.04 P14.04 P16.04 P14.04
le ON
SC04 Event: Vol- P19.02 P16.02 P15.02 P16.02 P14.02 P16.02 P14.02
tage ON
SC05 Event: Ex- P16.01 P13.01 P12.01 P13.01 P12.01 P13.01 P12.03
ternal event
1

Database
Software
ternal event
2
SC07 Event: DAE P14.09
active
SC08 Event: DAE P14.10
fault
SC09 Event: Flap P06.16 P06.16
return sig-
nal
SC10 Event: P06.23 P06.04
T_Volum.
ternal event
3
ternal event
4
SC13 Event: P07.05
Discharge
gate
SC14 Event: Time P06.18
flap OPEN
> MAX
SC15 Event: Bat- P06.20
ching time
> MAX
SC16 Event: Di- P36.37
rection of
rotation
SC17 Event: Ex- P13.23
ternal event
5
SC18 Event: Ex- P13.25
ternal event
6
WE Electrical
Systems

Database
Software
WE01 Event: P08.08 P07.08 P07.05 P07.07 P07.08 P07.07 P07.05

Power failu-
re
WE02 Event: P16.09 P13.13 P12.11 P13.09 P12.13 P13.09 P12.12
NAMUR
error
VCU1-DI6
WE03 Event: P16.10 P13.14 P12.12 P13.10 P12.14 P13.10 P12.13
NAMUR
error
VCU1-DI7
WE04 Event: P16.11 P13.15 P12.13 P13.11 P12.15 P13.11
NAMUR
error
VCU2-DI6
WE05 Event: P16.12 P13.16 P12.14 P13.12 P12.16 P13.12
NAMUR
error
VCU2-DI7
WE06 Event: P16.13 P13.17 P12.15 P13.13 P12.17 P13.13
NAMUR
error
VCU3-DI6
WE07 Event: P16.14 P13.18 P12.16 P13.14 P12.18 P13.14
NAMUR
error
VCU3-DI7
WE08 Event: Ana- P08.16 P07.12 P07.07 P07.15 P07.15 P07.15
log input <
offset
WE09
WE10
WE11
WE12
WE13 Event: P16.30 P13.24 P12.22 P13.19 P13.21
NAMUR
error
VMO1-DI7

Database
Software
WE14 Event: P16.31 P13.25 P12.23 P13.20 P13.22

NAMUR
error
VMO2-DI7
WE15
WE16
WM Mechanical
Systems
WM01 Event: Limit P13.22 P12.20
switch
WM02 Event: Belt P18.12 P17.12
creep
WM03 Event: Pro- P18.10 P17.10
cedure
WM04 Event: Off- P18.08 P17.08
track run-
ning
WM05 Event: P34.08 P30.08
Slippage 2
WM06 Event: P06.10
Scraper
WM07 Event: Ob- P12.25
struction
discharge
WM08
WM09 Event: Mo- P36.31
tor Start
WM10
WM11
WM12
WM13 Event: Agi- P28.16
tator over-
load
WM14 Event: P36.35
Conveying
air MAX

Database
Software
WM15 Event: Dri- P36.36

ve blocked
WM16 Event: Mo- P36.32
tor protecti-
ve switch
MF Material
flow
MF01
MF02
MF03 Event: P32.06 P36.34
Conveying
air MIN
MF04 Event: Se- P32.04 P36.33
aling air
MIN
MF05 Event: Mo- P30.10 P27.10 P27.10 P23.10 P25.10
isture MAX
MF06 Event: Out P18.21 P15.15 P14.15 P15.15 P15.21
of tolerance
MF07 Event: P18.25 P15.19 P14.19 P15.17 P15.25
Batch set-
point limit
MF08 Event: P01.17
Communi-
cation VVC
MF09 Event: No P06.03
No-motion
MF10 Event: To- P06.04
lerance
exceeded
MF11 Event: To- P06.05
lerance
undercut
MF12 Event: Ma- P18.22 P06.10
terial quan-
tity

Database
Software
MF13 Event: P31.08

Tempera-
ture MAX
MF14
MF15
MF16
IL Interlo-
cking
IL01 Event: No P04.06 P04.04 P04.03 P04.06 P04.06 P04.06 P04.08
release
IL02 Event: Me- P29.10 P24.10 P23.10 P33.10 P19.10 P28.10 P22.10
chanical
equipment
IL03 Event: P29.12 P24.12 P23.12 P33.12 P19.12 P28.12 P22.12
Electrical
equipment
IL04 Event: Me- P29.15 P24.15 P23.15 P33.15 P19.15 P28.15 P22.15
chatronics
IL05 Event: Not P29.17 P24.17 P23.17 P33.17 P19.17 P28.17 P22.17
ready
IL06 Event: Not P29.19 P24.19 P23.19 P33.19 P19.19 P28.19 P22.19
ready to
switch on
IL07 Event: *
Communic.
Bluetooth
channel 1
IL08 Event: *
Communic.
Bluetooth
channel 2
IL09 Event: Fil- P07.17
ling blocked
IL10 Event: FKB P27.22 P36.22 P32.22 P34.22 P31.22 P29.22 P20.22
error
IL11 Event: In- P19.05 P16.05 P15.05 P16.05 P14.05 P16.05 P14.05
correct
system time

Database
Software
IL12 Event: DI P26.10 P26.10

helix with
center rod
1/2
IL13 Event: Ad- P10.22
justment
canceled
IL14 Event: Pro- P45.07
tective lock
inactive
IL15 Event: No P28.16
ventilation
release
IL16
CO Regulators
CO01 Event: Con- P08.14 P11.10 P07.13 P07.13
trol system
limited
CO02 Event: Dis- P33.07 P40.09 P34.09
tributor
position
MIN
CO03 Event: Dis- P33.09 40.11 P34.11
tributor
position
MAX
CO04 Event: Fill- P25.29 P26.29 P24.29 P22.29 P20.29 P22.29
level MAX
sensor
CO05 Event: Vo- P06.17
lum. be-
cause of
load cell
error
CO06 Event: Dis- P23.40 P23.40
tributor
position
MAX (B)
CO07

Database
Software
CO08
CO09
CO10 Event: Dis- P23.38
tributor
position
MIN (B)
CO11 Event: Cor- P22.46
rection
MAX
CO12 Event: Limi- P22.49
ter range
CO13 Event: P08.17
ShakeCon-
trol VVC
CO14 Event: Helix P26.12
with center
rod rotatio-
nal speed
limited
CO15 Event: in- P08.18
termediate
circuit vol-
tage VVC
ALARM
CO16 Event: P08.19
Short circuit
VVC
ALARM
CO17 Event: P08.20
Overcurrent
VVC
ALARM
CO18 Event: P08.21
Outside
Frequency
VVC W1

Database
Software
CO19 Event: P08.22

Sensor
error
MEMS VVC
W1
CO20 Event: De- P08.23
viation VVC
W1
CO21 Event: Pa- P08.24
rametrizati-
on VVC W1
CO22 Event: P08.25
Sensor ID
VVC
ALARM
CH Check
measure-
ment sys-
tem
CH01 Event: P29.16 P26.16 P22.17
Check
quantity too
little
CH02 Event: P29.18 P26.18 P25.15 P22.19 P24.14
Check fill
level too
little
CH03 Event: P29.20 P26.20 P25.17 P22.21 P24.16
Check fill
level too
large
CH04 Event: Cor- P29.32 P26.32 P25.28 P22.32 P24.27
rection
error tare
value abso-
lute

Database
Software

rection
error tare
value relati-
ve
rection
error range
absolute
rection
error range
relative
CH08 Event: P29.25 P26.25 P25.21 P22.25 P24.20
Conveying
element not
off
CH09 Event: Con- P29.06 P26.06 P25.07 P22.07 P24.06
trol measu-
rement: No
release
CH10 Event: Pre- P29.26 P26.26 P25.22 P22.26 P24.21
pare check
CH11 Event: Wait P29.28 P26.28 P25.24 P22.28 P24.23
for acknow-
ledgement
CH12 Event: Con- P29.42 P26.42 P25.38 P22.42 P24.37
trol flap
CH13 Event: Ves- P29.44 P26.44 P25.40 P22.44 P24.39
sel fault
CH14 Event: CO- P26.02
Alarm Tube
CH15 Event: Min P26.10
KME set-
point
CH16 Event: Limi- P22.52
ter tare
value
CA Adjustment

Database
Software
CA01 Event: Error P08.04 P07.04 P07.02 P07.04 P07.04 P07.03 P07.01
load cell
input
CA02 Event: Ta- P08.03 P07.03 P07.01 P07.03 P07.03
chometer
input
CA03 Event: Error P25.07 P26.07 P24.07 P22.07 P20.07 P22.07
load cell
input (ves-
sel)
CA04 Event: Error P28.07
LC input
(2nd plat-
form)
CA05 Event: Li- P13.10 P32.10 P29.10 P39.10 P33.10
nearization
CA06 Event: Tare P06.13 P06.07 P28.03 P26.03
value cor-
rection
CA07 Event: DMS P35.06 P31.06 P29.06 P25.06
input
CA08 Event: P11.09
Capacity
adjustment
CA09
LC input
(FGK)
CA11
CA12
CA13
CA14
load cell
input (2nd
vessel)

Database
Software
CA16 Event: LC P24.10

input >
MAX (2nd
vessel)
HI maximum
HI01 Event: LC P08.06 P07.06 P07.04 P07.05 P07.06 P07.05 P07.03
Input >
MAX
HI02 Event: Ac- P10.04 P09.04 P09.04 P09.04 P09.04 P09.04 P09.04
tual feedra-
te MAX
HI03 Event: Load P09.08 P09.08 P09.08
MAX
HI04 Event: Belt P09.12 P09.12
speed MAX
HI05 Event: De- P08.13 P11.09 P07.12 P07.13 P07.12
viation
HI06 Event: Fill P10.08 P09.08
level Max
HI07 Event: Ro- P10.12 P09.12
tational
speed max.
HI08 Event: P03.05 P07.04
Feed hop-
per over-
filled
HI09 Event: Max. P09.06
measuring
load
HI10 Event: LC P25.08 P26.08 P24.08 P22.08 P20.08 P22.08
input >
MAX (ves-
sel)
HI11 Event: Ves- P25.19 P26.19 P24.19 P22.19 P20.19 P22.19
sel MAX
HI12 Event: 2nd P28.12
platform
MAX

Database
Software
HI13 Event: FC- P30.17 P32.18 P29.13

MAX limit
HI14 Event: DMS P35.07 P31.07 P29.07 P25.07
input >
MAX
HI15 Event: MAX P24.21
(2nd ves-
sel)
HI16 Event: P35.15 P31.15 P29.15 P25.15
Pressure
MAX
HI17 Event: De- P08.29 P11.34 P07.19
viation (ad-
vance
warning)
HI18 Event: P45.14
Feed pres-
sure MAX
LO minimum
LO01 Event: LC P08.05 P07.05 P07.03 P07.05 P07.04 P07.02
Input < MIN
LO02 Event: Ac- P10.02 P09.02 P09.02 P09.02 P09.02 P09.02 P09.02
tual feedra-
te MIN
LO03 Event: Load P09.06 P09.06 P09.06
MIN
LO04 Event: Belt P09.10 P09.10
speed MIN
LO05
LO06 Event: Fill P10.06 P09.06
level min.
LO07 Event: Ro- P10.10 P09.08 P09.10
tational
speed min.
LO08 Event: Fill P06.08
level MIN
LO09 Event: Ves- P24.18
sel MIN

Database
Software
LO10 Event: DMS P35.08 P31.08 P29.08 P25.08

input < MIN
LO11 Event: MIN P25.16 P26.16 P24.16 P22.16 P20.16 P22.16
(2nd ves-
sel)
LO12 Event: 2nd P28.09
platform
MIN
LO13 Event: FC- P30.16 P32.17 P29.12
MIN limit
LO14 Event: FC P30.15
speed <
MIN
LO15
LO16 Event: P35.12 P31.12 P29.12 P25.12
Pressure
MIN
LO17
LO18 Event: P45.12
Feed pres-
sure MIN
Tab. 12 : 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 weighing 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

pe1) 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.
Configurati- NO_PARA_ID_3_6 FIXED_8_16 This is used to configure the structure and the
on1) 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 [➙15]«
FIXED COMPATIBLE All others: Transmission by means of »General
VARIABLE COMPATIBLE Payload Structure (VARIABLE Mode) [➙25]«
Supplement 'COMPATIBLE': Compatibility with
an earlier DISOCONT model
Address1) 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)
Parameter1) 2) NO NO Select whether or not the payload package con-
YES tains a parameter block
Preset Count1) 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-
Count1) 2) 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)

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
Mode):
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
Mode):
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 Download Device Configuration Files (GSD, GSDML, EDS)
Save location How can I download configuration files?
In the weighing electronics 1. Connecting weighing electronics to a PC via an Ethernet

interface.
2. Enter into the browser the IP address of the weighing elec-

tronics.
► You will find the device configuration files at Information >

Identifikation > fieldbus configurations.
http://support.schenckprocess.com Select Weighing Electronics under Product Family Filter >

download the file by clicking on the button .
Tab. 13 : Download device configuration files (GSD, GSDML, EDS)

4.1.3.2.2 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 example
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 can be attached to the mainboard to create an interface to the PROFIBUS.
Module properties
Galvanic isolation Optocoupler

Power Supply +5 VDC internal
Power supply max. 310 mA
Plug connector to the bus activation XP1: D-Sub 9-pole
XP3: clamp 5-pole
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. 14 : '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. 15 : LED 'Operating Mode' (below)

Status Display
off no power supply or not initialized

green initialized
green, flashing initialized, result of diagnostic test pending
red Exception error
Tab. 16 : 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. 17 : 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. 18 : 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 … ')
Write a process or parameter value *) Binary 0250 42C80000 6 174/0xAE M → S

(ID, Value)
(e.g. 'Serial Setpoint = 100 kg/h')


*)
(Typical response or explanation) (Specified payload) count tion
Class 162/A2
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')
Write a read ID 1) *) 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
whose ID was sent beforehand 1)
[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)
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
ters, part 1 2) *)
Write the value of the basic parameter Binary 42C80000 64 204/0xAE M → S
sets of all material-dependent parame- 43440000 …
ters, part 2 2) *)
Read the value of the base parameter Binary 64 153/0x7B S → M
sets of all material-dependent parame-
ters, part 1 2)
Read the value of the base parameter Binary 64 154/0x7C S → M
sets of all material-dependent parame-
ters, part 2 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
subsequently can be read 1) *)
Read the material name the ID of ASCII 1C00 Name_1 42 137/0x89 S → M
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
Protocol Type1) 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
Configuration1) 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 proto-
PARA_ID_6_15 col.
VARIABLE Payload Structure (VARIABLE Mode) [➙25]«
COMPATIBLE Supplement 'COMPATIBLE': Compatibility with
an earlier DISOCONT model
Address1) 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
Parameter1) 2) NO NO Select whether or not the payload package con-
Preset Count1) 2) 2 … 4 2 The number of preset values per message from
master → scales
READ_ID 0 … 12 6 Number of freely selectable read values (meas-
Count1) 2) 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

Pin XC1 XC3

Signal Signal
3 Shielding
4 CAN_H
5 V+
Tab. 19 : '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. 20 : 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. 21 : 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 value Binary 0250 42C80000 6 175/0xAF 16/0x10

*)
(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.
Write a read ID 1) *) Binary 0250 2 177/0xB1 16/0x10

Subsequently the ID can be read
multiple times (see next line)
Read a process or parameter value Binary 6 127/0x7F 14/0x0E
[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
block 'Fixed mode configuration' *)


*)
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)
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
parameters 2) *)
Read the value of the base parame- Binary 128 124/0x7C 14/0x0
ter sets of all material-dependent E
parameters 2)
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
subsequently can be read 1) *)
Read the material name the ID of ASCII 1C00 Name_1 42 138/0x8A 14/0x0
which was written beforehand 1) E

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
The MULTICASTservices may overload the electronics processor if
MULTICAST services (e.g. webcam streams) are operated within the elec-
tronic network. Use only Switche in the electronics network that support
protocols IGMP (Internet Group Management Protocol) for IPv4 or
MLD (Multicast Listener Discovery) for IPv6.
In a closed Ethernet ring there may be a flood of messages because some
participants send messages to all the others. These messages are forward-
ed by a Switch in the network to all participants. If two Switche are connect-
ed to each other via two different paths (closed loop) this results in them
continuously sending the messages back and forth to each other. This leads
to an overloaded network. The connected controls can be overloaded by the
flood of messages and cease operation. Therefore closed Ethernet loop
structures are not permitted.
The overload can be identified by the unusual high-frequency blinking LED
at the switch. The LED are allocated to the Ethernet plugs.
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 [➙159]«.
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 [➙152]«.
See also
 Settings at the PROFINET IO Controller [➙153]

4.3.1 Guidelines for Initial Startup

Preparation of the hardware as per the system description (see »PROFINET Interface VPN8020 [➙159]«).
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 [➙169]«.
2. Specifying the payload structure (see parameter Configuration in chapter »Settings at the PROFINET
IO Device [➙152]«). 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 [➙204]« 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

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.
Configuration1) 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 [➙15]«
PARA ..... transmission by means of »General Payload
Structure (VARIABLE Mode) [➙25]«
1)
These parameters are subject to the 30 s condition for transfer to the interface card, see chapter
»Guidelines for Initial Startup [➙150]«.
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 [➙
153]« 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:
▪ At least one AR1) 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
OFF * TPS-12) 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.

LED Color Status Description
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 com-
ponents which have been specified for PROFINET. In order to guarantee
fault-free operation in CC-B any other components (e. g. external switches)
used within the network must be certified for PROFINET.
In any case, only industry-appropriate products may be used.
Star Topology
Fig. 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,
Writing a read ID 1) *) Binary 0250 2 176/0xB0 M → S

Read a process or parameter value Binary 6 126/0x7E S → M
[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


Slot 0
hex dec dec/hex
Write the value of the base parameter sets of Binary 42C80000 128 173/0xA M→S
all material-dependent parameters 2) *) 43440000 … D
Read the value of the base parameter sets Binary 128 123/0x7B S → M
of all material-dependent parameters 2)
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 read
1) *)
Read the material name the ID of which was ASCII 1C00 Name_1 42 137/0x89 S → M
written beforehand 1)

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
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 [➙204]« 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.
▪ Bus interface monitoring.
▪ 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
Protocol Type NO NO Selects the protocol

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)
IG (Ignore)
A (ALARM)


lue

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)
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 proto-
PARA_ID_6_15 col.
VARIABLE Payload Structure (VARIABLE Mode) [➙25]«
COMPATIBLE Supplement 'COMPATIBLE': Compatibility with an
earlier DISOCONT model
Parameter1) NO NO Select whether or not the payload package con-
Preset Count1) 2…4 2 The number of preset values per message from
master → scales
READ_ID 0 … 12 6 Number of freely selectable read values (measured
Count1) 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
Fig. 12: ControlLogix_regGeneral_connection options_DISOCONT Tersus_new

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.
Write a read ID 1) *) Binary 0250 2 177/0xB1 16/0x10

Read a process or parameter value Binary 6 127/0x7F 14/0x0E
[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


*)
Class 4
Write the value of the base parameter sets Binary 42C80000 43440000 … 128 174/0xAE 16/0x10
of all material-dependent parameters 2) *)
Read the value of the base parameter sets Binary 128 124/0x7C 14/0x0E
of all material-dependent parameters 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
sequently can be read 1) *) C
Read the material name the ID of which ASCII 1C00 Name_1 42 138/0x8A 14/0x0E
was written beforehand 1)
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 = 0250hex from the table 'Write IEEE Values'
Preset value = 42 c8 00 00(hex) = 100.0
The instruction 'Write a process or parameter value' is used for this. You will find the value 175dec (AFhex) in
the column 'Instance' of the list of 'Acyclic Data (Explicit Messages) Ethernet/IP'.
Therefore set the configuration dialog for this task as follows:
▪ Select the 'Set Attribute Single' entry from the 'Service Type' list. The corresponding 'Service Code' is
10hex.
▪ Enter the decimal value into the 'Instance' field, in this case 175.
▪ The other settings are shown in the figure

Preset ID and preset value are entered as follows:
4.4.4.1.2 Example for '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 131dec (83hex) in the column 'Instance' of the list of 'Acyclic Data (Explicit Messages).
Therefore set the configuration dialog for this task as follows:
▪ Select the 'Get Attribute Single' entry from the 'Service Type' list. The corresponding 'Service Code' is
0Ehex.
▪ Enter the decimal value into the 'Instance' field, in this case 131.
▪ The other settings are shown in the figure

The data received in this task are e.g.:
EtherNet/IP specifications www.odva.org
Network analyzer 'WireShark' (Freeware) www.wireshark.org

4.5 Modbus (Serial and Network)
4.5.1 General Information

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

In this mode the data are sent as binary code. This gives a larger data throughput, but
the data is not directly legible and must first be converted into a legible format.
Modbus-TCP Modbus-TCP is very similar to RTU but TCP/IP packets are used to transmit the data,
though the data presents itself to the application as a Modbus-RTU frame.
Communication channels:
TCP ports 502 and 503 are reserved for Modbus-TCP communication.
The most common modes for weighing controllers are Modbus-RTU and Modbus-TCP only.
4.5.1.1 Guidelines for 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 the IDs, can be created using the service tool 'EasyServe' by pressing
'Print| file'. The requirement is that the checkbox 'Print SysID' is activated via the menu 'Tools' | 'Options…' in
the 'Format' tab. To use German umlauts and special characters, the character format of the printer must be
set to CP ISO-Latin-1.
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 FC

(Typical response or explana- (Request Modbus frame in count address
*)
tion) hex)
Slave address 1 (dec/hex) (dec/
dec hex)
Read device name ASCII 01 03 2079 0014 40 8303/0x207 3

(e.g. 'My Feeder') 9
Write device name *) ASCII 01 10 2079 0014 28 41 42 43 … 40 8303/0x207 16/0x10

9
Read the scales' software ver- ASCII 01 03 2297 0014 40 8855/0x229 3

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

short text 0
(e.g. 'WE01')
Highest-priority event - read long ASCII 01 03 2206 0014 40 8710/0x220 3
text 6
Highest-priority event - read ASCII 01 03 22AB 0022 68 8875/0x22A 3
short and long texts B
(e.g. 'WE01 Event: Power Fail-
ure')
Read all displayed events - short ASCII 01 03 223F 0022 68 8767/0x223 3

text F
Max. 17 events, 4 charac-
ters/event
(e.g. 'WE01 …')
Call up the time, number and the ASCII 2014-05-21 14:12:03 68 9279/0x243f 3
counter value of the most recent No.: 137
log in the legal-for-trade memory CR: 888170 kg
with an acyclic telegram.


*)
tion) hex)
dec hex)
Read all displayed events Binary 01 03 2261 0022 68 8801/0x226 3

Max. 17 events, 4 bytes per 1
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/0x204 16/0x10

value *) 42C80000 0
(ID, Value)
Write one or multiple process or Binary 01 10 2043 0022 44 0250 66 8249/0x204 16/0x10
parameter values*) 42c80000 0252 41200000 0000 3
(ID, Value; ID, Value; … ) 00000000 ….
Max. 11 values
The evaluation ends at the next
ID with a ZERO value.
Write a read ID 1) *) Binary 01 10 2064 0001 02 0250 2 8282/0x206 16/0x10

Subsequently the ID can be read 4
multiple times (see next line)
Read a process or parameter Binary 01 03 221A 0003 6 8730/0x221 3
value whose ID was sent before- A
hand 1)
[ID Value]
Read all preset value IDs of the Binary 01 03 208D 0008 16 8323/0x208 3
parameter block 'Fixed mode D
configuration'
(e.g. '0140 0160 0180 0250 0252
0100 …')


*)
tion) hex)
dec hex)
Set all preset values IDs of the Binary 01 10 208D 0008 10 0140 01A0 16 8323/0x208 16/0x10
parameter block 'Fixed mode … D
configuration' *) CAUTION: The 1st transmitted
ID must always be 0140
(→'Fieldbus Release')
Read all read IDs of the parame- Binary 01 03 2095 0010 32 8331/0x209 3
ter block 'Fixed mode configura- 5
tion'
(e.g. '02F0 0310 0610 0750 …')
Set all read IDs of the parameter Binary 01 10 2095 0010 20 0752 0754 32 8331/0x209 16/0x10
block 'Fixed mode configuration' … 5
*)
Read variables lists using the Binary 01 03 2400 0022 64 9216/0x240 3

Modbus protocol 0
Write variable lists for each Mod- Binary 01 10 21E0 0010 20 00010000 32 8672/0x21E 16/0x10
bus log 2) … 0
(e.g. 'Commands 4+5: Start
Command')
Read date and time Binary 0C030F 0B1000 6 9272/0x243 3

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

(yymmdd hhmmss) 8
tion. Unused bytes must be replaced by '0' if the information to be transmitted is shorter.
2) An incorrect data length in the telegram can lead to an error unnoticed by the coupling Q-bus.

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/0x2 16/0x10
rameter sets of all material- nary 000
dependent parameters 2) *)
Read the value of the base Bi- 01 03 2000 0040 128 8192/0x2 3
parameter sets of all material- nary 000
dependent parameters 2)
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 read nary
1) *)
Read the material name the ID ASC 1C00 Name_1 42 0x2420 3

of which was written beforehand II
1)
4.5.1.12 Supplementary Documentation
OPEN MODBUS-TCP SPECIFICATION www.modbus.org
BV-H2185 EasyServe operating Manual

4.5.2 Modbus-TCP
NOTICE
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 [➙205]« for diagnostics and troubleshooting.

4.5.2.2.1 Settings at the Modbus-TCP Slave


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


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 [➙199]«
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. 22 : 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]
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

hex dec Read Values Calculation of In- VLW VWF VB VMC VSF VIF VBC
teger-Format W
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. 23 : 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. 24 : Modbus module properties
Fig. 13: 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
5 Tx B RTx A
6 Jumper to pin 4 for bus termination
7 Jumper to pin 3 for bus termination
Tab. 25 : 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. 26 : 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. 27 : 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 [➙
159]«).
▪ 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 must be greater than 0
because the belt runs proportionally
to the setpoint. If P = Po, then v = vo.
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 result 379 0x017B Or continue with 12b

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 Meas. 814 0x032E Prepare KME.
KME is in the preparatory phase (hopper being filled;
when filled, remove filling contact)
Check Meas. Active 815 0x032F KME is running.
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.
CANCEL Check Meas. 355 0x0163 Stop KME.
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.
Echo: Bin Filling 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: Bin Filling 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 value Max-
imum 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 TW: Tare 776 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 result 379 0x017B Or continue with 8b
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).


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

Appendix
7.3 Glossary
Item Explanation
GSD File PROFIBUS-specific configuration file in ASCII format containing information on node
(General Station properties, e.g. supported baud rates and other properties. If a new node is added
Description 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)
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. 28 : Terms and abbreviations used

List of Figures
List of Figures
Fig. 1 Automatic order list ............................................................................................................................. 33
Fig. 2 SIMATIC S7 HW Configurator [PROFIBUS] ....................................................................................... 129
Fig. 3 VPB 28020 PROFIBUS module layout drawing ................................................................................. 134
Fig. 4 Light-emitting diodes – VPB 28020 front view .................................................................................... 135
Fig. 5 VCB 28020 DeviceNet module layout drawing ................................................................................... 144
Fig. 6 VCB 28020:XC1 DeviceNet module front view ................................................................................... 145
Fig. 7 Program: SIMATIC S7 HW Config...................................................................................................... 154
Fig. 8 PROFINET star topology .................................................................................................................... 162
Fig. 9 PROFINET line topology .................................................................................................................... 163
Fig. 10 PROFINET ring topology .................................................................................................................... 163
Fig. 11 VCU 20100 Connecting VPN 28020 to VCU 20100 ........................................................................... 164
Fig. 12 ControlLogix_regGeneral_connection options_DISOCONT Tersus_new .......................................... 174
Fig. 13 VSS 28020 Modbus module layout drawing ....................................................................................... 201

List of Tables
List of Tables
Tab. 1 FIXED formats .................................................................................................................................... 16
Tab. 2 VARIABLE formats ............................................................................................................................. 27
Tab. 3 VARIABLE formats ............................................................................................................................. 34
Tab. 4 Master station → scales task identifier (TID) ..................................................................................... 35
Tab. 5 Reply identifiers (RID) scales master station ...................................................................................... 35
Tab. 6 Index in the parameter description (IND) - higher-value byte of the parameter index......................... 36
Tab. 7 error codes ......................................................................................................................................... 36
Tab. 8 Fieldbus commands ........................................................................................................................... 51
Tab. 9 Fieldbus preset values ........................................................................................................................ 57
Tab. 10 Fieldbus status ................................................................................................................................... 58
Tab. 11 Fieldbus measured values .................................................................................................................. 96
Tab. 12 Event overview ................................................................................................................................... 108
Tab. 13 Download device configuration files (GSD, GSDML, EDS) ................................................................ 128
Tab. 14 'Bus activation' connector ................................................................................................................... 134
Tab. 15 LED 'Operating Mode' (below) ............................................................................................................ 135
Tab. 16 LED 'Status' (above) ........................................................................................................................... 136
Tab. 17 Cable parameters ............................................................................................................................... 136
Tab. 18 Cable lengths per segment ................................................................................................................. 136
Tab. 19 'Bus activation' connector ................................................................................................................... 144
Tab. 20 LED 'Network Status' (above) ............................................................................................................. 145
Tab. 21 LED 'Module Status' (below)............................................................................................................... 145
Tab. 22 Fieldbus Presets Integer Format ........................................................................................................ 199
Tab. 23 Fieldbus Meas. Values Integer format ................................................................................................ 199
Tab. 24 Modbus module properties ................................................................................................................. 201
Tab. 25 Pin assignment Modbus serial interface ............................................................................................. 202
Tab. 26 Cable parameters ............................................................................................................................... 202
Tab. 27 Cable lengths per segment ................................................................................................................. 202
Tab. 28 Terms and abbreviations used ........................................................................................................... 221

List of Tables

Index
Index
Abbreviations in the List of Cyclical Data ................. 220 Explicit Messaging ........................................................ 7
Acknowledging Event Messages.................................. 4 Fieldbus Connections ............................................... 123
Acyclic Data (Explicit Messages) EtherNet/IP .......... 177 Fig. 1: Automatic order list .......................................... 33
Acyclic Data Exchange between PCS and Scales Fig. 10: PROFINET ring topology ............................. 163
Electronics............................................................ 179 Fig. 11: VCU 20100 Connecting VPN 28020 to
Acyclic Data PROFINET .......................................... 166 VCU 20100 ........................................................... 164
Acyclic Services ............................................... 136, 165 Fig. 12: ControlLogix_regGeneral_connection
Acyclical Data DeviceNet ......................................... 146 options_DISOCONT Tersus_new......................... 174
Acyclical Data Modbus ............................................. 189 Fig. 13: VSS 28020 Modbus module layout drawing 201
Acyclical Data PROFIBUS ....................................... 137 Fig. 2: SIMATIC S7 HW Configurator [PROFIBUS] .. 129
Appendix .................................................................. 219 Fig. 3: VPB 28020 PROFIBUS module layout drawing
Application Relation ................................................. 160 ............................................................................. 134
Automatic Order List .................................................. 33 Fig. 4: Light-emitting diodes – VPB 28020 front view135
Available Data - Listing....................................... 50, 199 Fig. 5: VCB 28020 DeviceNet module layout drawing
Caution ......................................................................... 5 ............................................................................. 144
Closed Loop ............................................. 149, 170, 193 Fig. 6: VCB 28020:XC1 DeviceNet module front view
Common Abbreviations ............................................ 219 ............................................................................. 145
Configuration of the DeviceNet Connection ............. 141 Fig. 7: Program: SIMATIC S7 HW Config................. 154
Configuration of the Ethernet Connection ................ 171 Fig. 8: PROFINET star topology ............................... 162
Configuration of the Modbus-RTU Connection......... 197 Fig. 9: PROFINET line topology ............................... 163
Configuration of the Modbus-TCP Connection ......... 193 Five Safety Rules of Electrical Engineering .................. 6
Configuration of the PROFIBUS Connection............ 125 fives safety rules ........................................................... 6
Configuration of the PROFINET Connection ............ 152 Format NO_PARA_ID_4_12 ...................................... 37
Connecting the PROFINET IO Module to the Star Format of the Safety Notices ........................................ 5
Topology .............................................................. 164 Function Codes (FC) ................................................ 185
Connection to a star topology – VCU 20100 with board Functionality of the DeviceNet Connection ............... 141
VPN8020 .............................................................. 164 Functionality of the Ethernet Connection .................. 171
Cover or shield ............................................................. 6 Functionality of the Modbus-RTU Connection .......... 197
Cyclical and Acyclical Data Exchanges ...................... 50 Functionality of the Modbus-TCP Connection .......... 193
Damaged/Defective Electrical Components ................. 6 Functionality of the PROFIBUS Connection ............. 124
Danger ......................................................................... 5 Functionality of the PROFINET Connection ............. 151
Data Formats ........................................................... 186 General Information .......................... 7, 15, 25, 183, 196
Data Segments ............................................................ 7 General Information for all Fieldbus Types ............... 203
Data Types (Numerical Notation) ................................. 8 General Payload Structure (VARIABLE Mode) .......... 25
Database ...................................................................... 7 General Telegram Structure ..................................... 184
Design Modifications .................................................... 4 Glossary ................................................................... 221
DeviceNet................................................................. 140 GSD.......................................................................... 128
DeviceNet Interface VCB8020 ................................. 144 GSDML ..................................................................... 128
DeviceNet Master Settings (PCS) ............................ 143 Guidelines for Commissioning .......... 124, 140, 170, 183
Diagnosis and Troubleshooting ................................ 203 Guidelines for Initial Startup ..................................... 150
Dimensions ................................................................ 10 Highest Priority Event ................................................. 10
Download ................................................................. 128 IDs (Identifiers) ........................................................... 10
Download Device Configuration Files (GSD, GSDML, IGMP (Internet Group Management Protocol) . 149, 170,
EDS)..................................................................... 128 193
EDS .......................................................................... 128 Illustration of the Telegram Bytes on Command ......... 12
electric shock ............................................................... 6 Integrating the IO Device .......................................... 154
electrical components................................................... 6 Integration Slave ...................................................... 129
Ensuring Transmission ............................................. 186 Intended Use ................................................................ 3
Error Codes .............................................................. 186 Internal On-Stream Calibration System of a
Ethernet loop structures Weighfeeder (VWF) .............................................. 211
MULTICAST ......................................... 149, 170, 193 IP Address and Name for PROFINET IO Subscriber 157
EtherNet/IP............................................................... 170 Keeping the Technical Documentation ......................... 4
EtherNet/IP Slave Settings ....................................... 171 Layout of the Components ............... 134, 144, 159, 201
Events - Overview .................................................... 108 LEDs H110, H120 ............................................ 135, 145
Example for 'Display Fixed Mode Configuration' ...... 181 LEDs in the Ethernet Connection (RJ45).................. 161
Example of 'FIXED Mode' Telegram .......................... 22 LEDs on the Board ................................................... 160
Example of 'Writing a Process or Parameter Value' . 180 Line Topology ........................................................... 163
Example Telegrams 'Variable Mode' .......................... 37 Live parts ...................................................................... 6
Examples of Telegrams (Process Values) ............... 187 Loss-in-Weight Feeder (VLW) Inlet Gate Control ..... 217
Explicit Messages .................................................... 179 Material-Dependent Parameters (MDP) ................... 107

Index
MDP = Material-Dependent Parameters (Material- Service and Maintenance ............................................. 4

Dependent Parameters) ....................................... 107 Settings .................................................... 134, 144, 159
Message Command ................................................. 179 Settings at the DeviceNet Slave ............................... 141
MLD (Multicast Listener Discovery) .......... 149, 170, 193 Settings at the EtherNet/IP Master (ControlLogix) .... 173
Modbus (Serial and Network) ................................... 183 Settings at the Modbus-RTU Slave .......................... 197
Modbus Interface VSS8020 ..................................... 201 Settings at the Modbus-TCP Slave .......................... 194
Modbus RTU Master Settings .................................. 198 Settings at the PROFIBUS Slave ............................. 125
Modbus-RTU ............................................................ 196 Settings at the PROFIBUS-Master (PCS) ................ 126
Modbus-TCP ............................................................ 193 Settings at the PROFINET IO Controller .................. 153
Modbus-TCP Master Settings .................................. 196 Settings at the PROFINET IO Device ....................... 152
Moisture and humidity .................................................. 4 Signal Words ................................................................ 5
Monitoring ID .............................................................. 31 Signal Words for Danger Warnings .............................. 5
MULTICAST ............................................. 149, 170, 193 Signal Words for Usage Instructions ............................ 5
Network Overload .................................... 149, 170, 193 Simplified Payload Structure ...................................... 15
Note.............................................................................. 6 Some Examples of Applications ............................... 209
Notes for DeviceNet ................................................. 204 Star Topology ........................................................... 162
Notes for EtherNet/IP ............................................... 204 Strictly Observe ............................................................ 5
Notes for Modbus ..................................................... 205 Subscriber Addresses .............................................. 184
Notes for PROFIBUS DP ......................................... 203 Supplementary Documentation 140, 149, 169, 182, 192
Notes for PROFINET IO ........................................... 204 Tab.1: FIXED formats ................................................. 16
Order list..................................................................... 27 Tab.10: Fieldbus status .............................................. 96
order list, automatic .................................................... 33 Tab.11: Fieldbus measured values .......................... 107
order list, normal ........................................................ 31 Tab.12: Event overview ............................................ 122
order list, variable ....................................................... 31 Tab.13: Download device configuration files (GSD,
Overload................................................... 149, 170, 193 GSDML, EDS) ...................................................... 128
Overview ...................................................................... 1 Tab.14: 'Bus activation' connector ............................ 135
Parameter Changes ..................................................... 3 Tab.15: LED 'Operating Mode' (below)..................... 135
Parameter Range in Detail ......................................... 35 Tab.16: LED 'Status' (above).................................... 136
Parameter Transmission ............................................ 34 Tab.17: Cable parameters ........................................ 136
Parameters............................................................... 188 Tab.18: Cable lengths per segment ......................... 136
Password ..................................................................... 3 Tab.19: 'Bus activation' connector ............................ 145
Payload .................................................................... 187 Tab.2: VARIABLE formats .......................................... 27
Payload Scope and Content FIXED Mode ................. 15 Tab.20: LED 'Network Status' (above)...................... 145
Payload Scope and Content VARIABLE Mode .......... 26 Tab.21: LED 'Module Status' (below) ....................... 145
Payload Structure ....................................................... 14 Tab.22: Fieldbus Presets Integer Format ................. 199
Personnel ..................................................................... 3 Tab.23: Fieldbus Meas. Values Integer format ......... 200
Potential Sources of Danger ........................................ 3 Tab.24: Modbus module properties .......................... 201
Preset Values ............................................................. 51 Tab.25: Pin assignment Modbus serial interface ...... 202
Preset values INTEGER........................................... 199 Tab.26: Cable parameters ........................................ 202
PROFIBUS DP ......................................................... 123 Tab.27: Cable lengths per segment ......................... 202
PROFIBUS Interface VPB8020 ................................ 134 Tab.28: Terms and abbreviations used .................... 221
PROFINET Interface VPN8020 ................................ 159 Tab.3: VARIABLE formats .......................................... 34
PROFINET IO .......................................................... 149 Tab.4: Master station → scales task identifier (TID) ... 35
PROFINET IO Module.............................................. 159 Tab.5: Reply identifiers (RID) scales master station . 35
PROFINET IO Network Topology with VPN8020 ..... 162 Tab.6: Index in the parameter description (IND) -
Read process values (IEEE format) ........................... 96 higher-value byte of the parameter index ............... 36
Read status ................................................................ 58 Tab.7: error codes ...................................................... 36
Read values ............................................................... 58 Tab.8: Fieldbus commands ........................................ 57
Read values INTEGER (Measured values) .............. 199 Tab.9: Fieldbus preset values .................................... 58
Redundancy Manager 'Ring Manager' ..................... 164 Taring a Loss-in-Weight Feeder (VLW) .................... 216
Redundant Modbus-TCP.......................................... 196 Telegram Structure (Variable payload) ....................... 28
Replacing Components ................................................ 4 User Data Diagnosis................................................. 205
Ring Topology .......................................................... 163 VARIABLE COMPATIBLE Format with PKW (Alter
Safety Parameter) ............................................................. 42
Environmental damage ............................................ 5 VARIABLE COMPATIBLE Format with PKW ('Change
Material damage ...................................................... 5 Parameter' - Text Parameter Type) ........................ 46
Safety instruction - Setup ......................................... 5 VARIABLE COMPATIBLE Format with PKW ('Change
Signal word "Caution"............................................... 5 Parameter' with Error Reply) .................................. 44
Signal word "Danger" ............................................... 5 VARIABLE COMPATIBLE Format with PKW (Read
Signal word "Notice" ................................................. 5 Parameter) ............................................................. 48
Signal word "Warning".............................................. 5 VARIABLE COMPATIBLE Format without PKW (1)... 39
Signal words "Strictly Observe" ................................ 5 VARIABLE COMPATIBLE Format without PKW (2)... 40
Safety Information ........................................................ 3 voltages above 1 kV ..................................................... 6
Secure against restart .................................................. 6 Warning ........................................................................ 5
Serial Interfaces Pin Assignment ............................. 202 Write commands ........................................................ 51

Index
Write process values (IEEE format) ........................... 57 Zeroing and Taring a Weighfeeder (VWF)................ 209


BVH 2448 GB

Uploaded by

Copyright:

Available Formats

BVH 2448 GB

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BVH 2448 GB

Uploaded by

Copyright:

Available Formats

DISOCONT® Tersus

Schenck Process Europe GmbH Schenck Process LLC

Stock Equipment Company Inc. Schenck Process Pty Ltd

(81064793504219147 V10, 17/09/2018)

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

4 Fieldbus Connections .......................................................................................................................... 123

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

4.2.3.2 DeviceNet Master Settings (PCS) ..............................................................................................143

5 Diagnosis and Troubleshooting ......................................................................................................... 203

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

5.5 Notes for EtherNet/IP .........................................................................................................................204

6 Some Examples of Applications ......................................................................................................... 209

7 Appendix ............................................................................................................................................... 219

Index ...................................................................................................................................................... 227

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

What is described in this manual?

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

Overview of supplementary manuals

BV-H2185 Schenck Process EasyServe

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

Potential Sources of Danger

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

Acknowledging Event Messages

Service and Maintenance

Moisture and humidity

Keeping the Technical Documentation

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

2.1 Signal Words

Format of the Safety Notices

2.1.2 Signal Words for Usage Instructions

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

2.2 Five Safety Rules of Electrical Engineering

2.3 Damaged/Defective Electrical Components

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

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, V10

3.1.2 Data Types (Numerical Notation)

FLOAT Sign/Exponent Mantissa 1 Mantissa 2 Mantissa 3

Further examples of floating-point numbers

Number IEEE format (hex) Siemens KG format *) (hex)

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

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, V10

3.1.3 IDs (Identifiers)

Type 1st Byte 2nd Byte

hexadecimal: 0x20 0x0160

3.1.5 Highest Priority Event

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