BVH2359gb - Komunikace

DISOMAT®Satus , DISOMAT®Opus,
DISOMAT® Tersus
Data Communication
BV-H2359GB
Service
Quality and reliability form the basis for Schenck’s corporate philosophy all over the world. That’s why we offer you
an extensive service strategy starting with our stringent quality control through assembly and commissioning right
down to all-round support. We’re always there for you.
Free Helpdesk (Monday through Friday from at least 8 o’clock to 5 p.m. CET)
Service specialists are available to you in every department during our normal office hours for analying problems
and malfunctions.
Heavy Industry Vibrating & Screening Technology
Building materials, mining, foundry, T +49 61 51 - 32 35 25
steel and cement F +49 61 51 - 32 30 96
T +49 61 51 - 32 31 38 [email protected]
F +49 61 51 - 32 32 70
[email protected]
Light Industry
Chemistry, plastics, foodstuffs and pharmaceuticals
T +49 61 51 - 32 25 71
F +49 61 51 - 32 26 68
[email protected]
Transport Automation
All industries with logistics processes and trains
T +49 61 51 - 32 24 48
F +49 61 51 - 32 13 69
[email protected]
Spare Parts & Components
T +49 61 51 - 32 17 58
F +49 61 51 - 32 36 32
[email protected]
[email protected]
Individual phone consulting (fee required)
(Monday through Friday from at least 8 o’clock to 5 p.m. CET)
Do you want one of our service specialists to give you phone support in commissioning your system or on-line
diagnosis / system optimisation? We’re there for you. Schedule an appointment with us whenever you need it.
Free 24 h Customer Service Hotline
24h Emergency-Hotline: +49 172 – 650 17 00 Transport Automation and

Static Weighing Equipment
+49 171 – 225 11 95 Heavy Industry, Light Industry

excluding Static Weighing Equipment
Copyright 2007
Schenck Process
Pallaswiesenstraße 100, 64293 Darmstadt, Germany
www.Schenckprocess.com
All rights reserved. Any reproduction of this documentation, regardless of method, without prior permission by
Schenck Process in writing, even by excerpt, is prohibited.
Subject to change without prior notice.
Note: Translation of the original instructions

Contents
1 Something about this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2 Safety Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1 Information for operators of . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1 List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2 The interface parameter of DISOMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4 Computer, PC Coupling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1 Protocols ............................................................9
4.1.1 SCHENCK Standard Protocol (DDP 8672). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.2 SCHENCK Poll Protocol (DDP 8785) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1.3 Schenck Minproz. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.1.4 Siemens Protocol 3964R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1.5 ASCII-S5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.1.6 ASCII - Modbus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.2 Message Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.2.1 User Data Construction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.2.2 EDP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.3 Commands Explanations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5 Coupling for SPS and PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.1 Modbus-RTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.1.1 The structure of the data telegrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.1.2 The structure of the fault telegrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.1.3 The address ranges of the coupling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.1.4 Data from the process control system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.1.5 Data on the process control system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.1.6 Modbus interface parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.2 Modbus/TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.2.1 Example telegrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
5.2.2 Diagnosis and Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
5.2.3 Parameterising the controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
5.3 Profibus DP protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5.3.1 Data segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5.3.2 Structure of user data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
5.3.3 Data from the process control system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
5.3.4 Data on the process control system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
5.3.5 Profibus-DP interface parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
5.3.6 Planning aids (drawings, rules) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
5.4 DeviceNet Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
5.4.1 Structure of user data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
DISOMAT Opus, Satus, Tersus, Data Communication BV-H2359GB/0722 I

© Schenck Process
5.4.2 Parameterising DeviceNet interface parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
5.5 Available data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
5.5.1 Setpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
5.5.2 Controller data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
5.5.3 Date/time format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
II BV-H2359GB/0722 DISOMAT Opus, Satus, Tersus, Data Communication

© Schenck Process
Something about this manual
1 Something about this manual

Who is it written for?
This manual is for technicians and programmers who want to control the
equipment described (called DISOMAT or equipment below) with a data
processing unit or create their own function block linkages. The assumption is
made that DISOMAT functions are known and the user has a basic knowledge of
data exchange in local computer networks (point-to-point connections and bus
systems).
Software versions
DISOMAT OPUS starting from version 20700-003
DISOMAT Satus starting from version 20900-001
DISOMAT Tersus starting from version 20450-002
What does this describe?

It describes:
n Procedures
n Data processing commands
n Bus interfaces
n The entire function block strategy
A table of supplementary manuals
Internal numbers
DISOMAT® Opus System Manual BV-H2310GB
DISOMAT® Opus Operating Manual BV-H2313GB
DISOMAT® Satus System Manual BV-H2331GB
DISOMAT® Tersus System Manual BV-H2334GB
DISOMAT® Tersus Operating Manual BV-H2335GB
DISOMAT Opus, Satus, Tersus, Data Communication BV-H2359GB/0722 1

© Schenck Process
Something about this manual
- Reserved for Notes -
2 BV-H2359GB/0722 DISOMAT Opus, Satus, Tersus, Data Communication

© Schenck Process
Safety Instructions
2 Safety Instructions
Intended use
When controlling DISOMAT, please make sure that it is used for the intended
purpose
as described in the manual.
Any use beyond that is considered not for the intended purpose.
General hazards if safety instructions are not obeyed

DISOMAT is reliable state-of-the-art equipment when connected. However, there
might be residual hazards if untrained personnel use it incorrectly.
Safety-conscious work
n Anyone entrusted with the DISOMAT data processing should have read and
understood the manual and in particular the safety instructions.
n Only trained and authorised personnel may connect DISOMAT to a computer
and control it via data lines. The assumption is made that the personnel is
familiar with weighing equipment functions.
n Fault messages may only be acknowledged after the reason for the fault has
been rectified and there is no longer a hazard.
n Fault messages may only be acknowledged with a password after the reason for
the fault has been rectified. Beyond this, if control systems are connected to a
lower order DISOMAT, they have to ensure that the control systems stay in a
safe state after acknowledging default.

© Schenck Process
2.1 Information for operators of Safety Instructions
Labelling residual hazards

Some commands may only be used interactively. This generally applies to all
commands critical to safety such as acknowledging a fault message and
starting feeding.
These commands are marked with the symbol below in this manual.
There might be danger to persons or property
if these commands are carried out without the approval of an operator.
When computer controlling DISOMAT, please make sure that commands critical to
safety are only carried out if they are approved by an operator.
Before giving approval, this operator has to satisfy him or herself that there is no
danger.
If this is not possible, you should avoid using commands critical to safety in
computer control.
Safety notes for the user company

n The user company shall bear the responsibility for proper data processing for the
connected DISOMAT.
n Personnel supervisors should be familiar with the chapter on safety instructions
and the operation and start-up items with an impact on safety.
n Before start-up, supervisors should check whether computer controlled
DISOMAT operation might cause additional hazards in connection with other
machines or plant components . If necessary, supervisors should supplement
safety instructions.
2.1 Information for operators of

calibrated scales
Requirements made of add-on non-verifiable equipment/data processing systems
for recording readings for commercial applications.
Legal provisions
Readings for commercial applications have to be obtained with calibrated
measuring instruments.
The readings may be forwarded to add-on non-verifiable equipment (computer
systems) for creating commercial vouchers assuming that the scale or the
configurable (i.e., approved) add-on equipment records or stores readings in a
non-deletable fashion and without making any changes *)
· and that the readings are accessible to both parties affected by the
measurement.
*) The weights and measures regulations state that add-on equipment is equivalent to the measuring
instruments. The weights and measures act and weights and measures regulations take these circumstances
into consideration by making specific requirements of the data processing equipment and programs used in
commercial applications.
Requirements made of data processing connections/query for recording readings

and creating vouchers:
1. Legal-for-trade reading query (guaranteeing legal-for-trade data storage):

© Schenck Process
Safety Instructions 2.1 Information for operators of
· The legal-for-trade reading has to be queried as per the instructions in

Schenck manuals.
· When changing the prompting mode from DP to scale, always check to see if
data is correctly saved.
· Readings for a commercial voucher may not be further processed without prior
legal-for-trade data storage (for instance, with a fault message). If this is not
respected, this would be a violation of calibration regulations which would be
tantamount to a regulatory offense.
2. Labeling readings:
· Identification features (strings) such as
° Date/Time
° Cons. No.
° Vehicle No.
are or should be assigned to legal-for-trade readings for tracing them from the
legal-for-trade data memory to the commercial voucher.
· The commercial voucher has to have the following note:

“Readings from freely programmable add-on equipment.
These legal-for-trade readings may be inspected.”
3. The duration of legal-for-trade data storage.

The minimum storage period for legal-for-trade readings is 3 months. The oldest
reading is overwritten when storing new readings. Storage periods > 3 months can
be set.
The operator of the scale equipment is responsible for complying with the statutory
requirements.

© Schenck Process
2.1 Information for operators of Safety Instructions

© Schenck Process
Introduction
3 Introduction
Agreements on electrical connections (on the physical level) and data exchange
are necessary if DISOMAT is supposed to be connected to and remote-controlled
by a higher-level data processing system (a process computer, PC or stored
program control).
DISOMAT can be connected into local networks via serial interface and data
exchange is geared towards the normal protocols in the stored program controls
(SPC). They are called procedures in this framework.
Procedures are rules agreed for establishing communication as well as formatting

and coding data including ensuring correct transmission. All procedures applied to
DISOMAT use messages for transmitting or receiving data blocks (telegrams) and
confirming the connection (acknowledging).
What all procedures have in common is the “immediate response” property:
DISOMAT responds immediately to each telegram and transmits another telegram
after execution (such as “taring has been completed”) with commands that require
a certain time for execution.
The data to be transmitted, known as user data, are packed into data telegrams
that also contain control and test characters.
Control characters define the beginning and end of the data telegram.
To do this, either the user data from the beginning and end characters are limited
or the entire length of the data telegram is given by the telegram head.
Block check characters (BCC) are used for data storage because they enable
the recipient to identify faults in data transmission.
The data and user data can be character-coded (such a 7-bit ASCII. 8-bit ASCII)
or transmitted as binary sequences of bits.
Message: Synchronisation Data telegram Data storage

Opening Head User data Ending

© Schenck Process
3.1 List of procedures Introduction
3.1 List of procedures

The list below shows the procedures presently used in DISOMAT
for communication via serial interfaces.
Couplings for computers, PCs

q SCHENCK Standard Procedure; refer to Chapter 4.1.1
q SCHENCK Poll Procedure; refer to Chapter 4.1.2
q SIEMENS 3964R; refer to Chapter 4.1.3
q ASCII-S5; refer to Chapter 4.1.4
q ASCII-Modbus; refer to Chapter 4.1.5
Other procedures may be visible in the selection depending upon the equipment
configuration such as DDP 8672-MS.
These procedures are only of importance in specific applications and they are
documented in each plant description.
q Coupling for SPS and PLC

q Modbus Protocol; refer to Chapter 5.1
q Profibus-DP Protocol; refer to Chapter 5.2
q Interbus-S Protocol; refer to Chapter 5.3
3.2 The interface parameter of DISOMAT

Several parameters have to be set before the interface can be operated.
The parameters can be keyed in or selected with DISOMAT in the menu tree under
the following menu items:
n PERIPHERY /interfaces
n PERIPHERY /COMMUNICATION/ data processing
n PERIPHERY /COMMUNICATION/fieldbus
You can find an exact description of the settings in each operating manual.

© Schenck Process
Computer, PC Coupling 4.1 Protocols
4 Computer, PC Coupling
4.1 Protocols
4.1.1 SCHENCK Standard Protocol (DDP 8672)

Protocol Agreements
Nachricht: Synchronisation Daten-Telegramm Datensicherung

Eröffnung Kopf Nutzdaten Nachspann
<ENQ> <STX> ... <ETX> <BCC>
In the following, the individual data transmission elements are characterized. The
sequence of elements is not to be understood as time sequence.
Enquiry
The sender starts data transmission with control character <ENQ>.
Acknowledgement
The receiver acknowledges the enquiry with
<ACK> (ready to receive)
or <NAK> (not ready).
Data Message
The data messages (send, request and response messages) are constructed as
follows:
<STX> User Data <ETX><BCC>
Acknowledgement
Receiver acknowledges successful data transmission with <ACK>; faulty data
transmission, with <NAK>.
Error Recognition
Receiver acknowledges with <NAK> or one of the two stations fails to send
feedback within preset period of time.

© Schenck Process
4.1 Protocols Computer, PC Coupling
Behaviour Upon Errors In Data Transmission

Upon errors in data transmission, sender repeats sending various times.
With errors in connection set-up, repeats start from enquiry.
With faulty transmission of user data, repeats start with data message.
Synchronization Monitoring Times, Repeats:

Acknowledgement monitoring time tq 2 seconds
Response monitoring time ta 5 seconds
Enquiry monitoring time te 2 seconds
Max. number of enquiry repeats: 3
Max. number of data repeats: 3
Data Protection, Block Check Character Generation

BCC is formed as longitudinal parity over all character sent exclusive of <STX>.
BBC bits complete number of bits 1 of a bit number line to even (s. Example)
parity bit is not formed in accordance with this rule. It is generated from the
7 bits of the BBC itself.
Receiver for his part generates the BCC code and compares it with block check
characters received..
Example: Block check character formation for AB34 data.
Bit No. S A B 3 4 E B
T T C
X X C
7 0 1 1 0 0 0 0
6 0 0 0 1 1 0 0
5 0 0 0 1 1 0 0
4 0 0 0 0 0 0 0
3 0 0 0 0 1 0 1
2 1 0 1 1 0 1 1
1 0 1 0 1 0 1 1
Parity bit 0 0 1 1 0 1 0
Here: Odd
(Longitudinal: Always even and BCC parity same as character parity)

© Schenck Process
Sending Priority
The DISOMAT units always have low priority. If both stations attempt to start data
communication, DISOMAT aborts sending and goes to receiving state.
Sequence
1. Sample Sequence:
DISOMAT with address 01 is to transmit current weight values to EDP.
1) EDP sends command for weigh data transmission to DISOMAT (01#TG#).
Master (EDP) Slave (DISOMAT ) Protocol Element
<ENQ> Enquiry
<ACK> Acknowledgement
<STX>01#TG#<ETX><BCC> Request message
2)
DISOMAT responds with response message comprising net and tare weights,
weight change per time unit (dW/dt) and scale status information.

<ENQ> Enquiry
STX>01#TG#netto#Tare#dg/dt#status#<ETX><BCC> Response message

© Schenck Process
2. Example: Command with delayed response
DISOMAT with address 01 is to be tared remote-controlled via EDP.
1) EDP sends taring command (01#AT#) to DISOMAT.
<ENQ> Enquiry
<STX>01#TG#<ETX><BCC> Request message
2)
Taring is possible only under certain conditions, e.g. DISOMAT must have
recognized no-motion.
This may take some seconds. Therefore, DISOMAT sends an immediate

response message informing EDP that the command is being processed.
<ENQ> Enquiry
<STX>01#TG#<ETX><BCC> Response message direct
S=0: Command execution OK

S¹ 0: Command execution faulty
3)
DISOMAT tries to tare scale and, once command is successfully executed, sends
a response message including the information 01#AT#0# (user data).
If the command could not be performed (DISOMAT has not recognized
no-motion after a certain timeout), the response includes a number unequal to
0, e.g. 01#AT#1#.
<ENQ> Enquiry
<STX>01#TG#<ETX><BCC> Response message delayed

© Schenck Process
4.1.2 SCHENCK Poll Protocol (DDP 8785)

This protocol has been developed from the SCHENCK Standard Protocol (see
Item 4.1.1, or Spec Sheet DDP8 672) and is used for special applications, for
instance, running weight display in superordinate PC.
EDP starts communication direct with request message and DISOMAT responds
with corresponding data record. This is done without acknowledgement and
without repeat in case of error. Transmission of data contents is secured
through block check mechanism (recognition of faulty messages).
Note:
With this protocol, important response messages can get lost, particularly the
delayed response messages whose output time is not exactly predictable.
Examples:
n The feed result message (DO) may be output several hours after start of
feeding.
n The delayed message of the taring command (AT) follows only in no-motion.
Protocol Agreements
Message Synchronization Data Message Data Protection
Enquiry Header User data Ending
STX> <ETX> <BCC>
IIn the following, the individual data transmission elements are characterized. The
sequence of elements is not to be understood as timely sequence.
Enquiry
Omitted!
Data Message
The data messages (send, request and response messages) are constructed as
follows:
<STX> User Data <ETX><BCC>
Acknowledgement
Omitted!
Error Recognition
One of the two stations does not send feedback within preset period of time.

© Schenck Process
Behaviour Upon Errors in Data Transmission

Upon errors in data transmission (timeout), sender retries data request.
Synchronization, Monitoring Times, Repeats:

n No acknowledgement
n Response monitoring time ta : 5 sec.
n No enquiry
n No data repeats
n No EDP error on DISOMAT

See Item 4.1.1, page 7.
Sending Priority
The DISOMAT units always have low priority. If both stations try to start data
communication, DISOMAT aborts sending and goes to receiving state.
Sequence
Example:
EDP sends command for weigh data acquisition and transmission to DISOMAT .
<STX>01#TG#<ETX><BCC>
>
DISOMAT reponds directly with data message.
<STX>01#TG#netto#Tare#dg/dt#status#<ETX><BCC>
<

© Schenck Process
4.1.3 Schenck Minproz

Minproz was consciously developed as a very simple procedure. Its set-up without
character check or block check characters makes it possible to trigger telegrams
from a terminal program for testing purposes (such as Windows Hyperterminal).
The fact that there is no block check means that data can be falsified without
decection. This is the reason why it is not advisable to apply this procedure when
operating the scale.
Master starts communication with the request message direct and DISOMAT
responds with the corresponding data record. On either side, this takes place
without acknowledgement, block check and repeat in case of error.
Protocol Agreements
Synchronisation Data Message Data Saving
Message: Enquiry Header User data Ending
—- <CR>
Enquiry, acknowledgement, error recognition

omitted!
Data message
Data messages (send, request and reponse messages) are constructed as
follows:
User data <CR>
EDP sends command for acquisition and transfer of weigh data to DISOMAT.
01#TG#<CR>
>
DISOMAT responds with data message direct.
< 01#TG#net#tare#dW/dt#status#<CR>

© Schenck Process
4.1.4 Siemens Protocol 3964R

Protocol Agreements
Synchronization Data Message Data Protection
<STX> ... <DLE><ETX> <BCC>
In the following, the individual data transmission elements are characterized. The
Enquiry
Sender starts data transmission with control character <STX>.
Acknowledgement
The receiver acknowledges the enquiry with <DEL> (ready to receive) or
<NAK> (not ready).
Data Message
Data messages (send, request and response messages) are construction as
follows:
User data <DLE><ETX><BCC>
Acknowledgement
Receiver acknowledges successful data transmission with <DLE>; faulty
Error Recognition

Upon errors in data transmission, sender repeats sending various times.
In principle, repeats start from enquiry.
Synchronization, Monitoring Times, Repeats:

n Acknowledgement monitoring time tg 2 sec.
n Response monitoring time ta 5 sec.
n Enquiry monitoring time te 2 sec.
n Max. number of enquiry repeats 5
n Max. number of data repeats 5

© Schenck Process

See Item 4.1.1, page 7.
Sending Priority
DISOMAT aways has low priority. If both stations try to start data communication,
DISOMAT aborts sending and returns to receiving state.
Value Range
The value range of transmitted characters of a data section covers 8 bits, i.e. in
hexadecimal representation 00 to FF.
This value range requires a special treatment of user datas’ end code (<DLE>), if
the bit string of the <DLE> character is included in user data. This is done by
doubling the <DLE><DLE> Doubling<DLE> character.
<DLE> Doubling
<DLE> occurring in user data is doubled by transmitter, for receiver to

completely receive user data.
If two <DLE> codes are received, receiver resets doubling and treats <DLE> as
data byte.

© Schenck Process
Data Request Sequence

Example:
1)1) EDP sends command for weigh data transmission upon no-motion.

<STX> Enquiry
<DLE> Acknowledgement
Response message
01#TS#<DLE><ETX><BCC> <DLE Acknowledgement
2)
EDP receives immediate response that command has understood. The code in
response message stands for the status of the EDP command.
0=OK, 1=Error

© Schenck Process

<STX> Enquiry
01#TS#s#<DLE><ETX><BCC> Response message
s = 0: Command execution OK
s¹ 0: Command execution faulty
3)
Then, DISOMAT sends delayed message. If command can be executed within
preset period of time (20 seconds), delayed message includes requested data,
here: weight values and status. If not, corresponding error message is output after
elapse of preset period of time.
<STX> Enquiry
01#TS#netto#Tare#status<DLE><ETX><BCC> Response message

© Schenck Process
4.1.5 ASCII-S5
The protocol used with SIMATIC S5/S7 differs from the SIEMENS 3964R protocol
by the 10-byte message header ahead of user data which comprises address,
command and length information. In DISOMAT this protocol is called “S5”.
In SIMATIC S5 Mode, all data are transmitted in ASCII code.

Data block or word are represented hexadecimally (0..FF)
To address a scale,
n the data block (DB) for scale number (0...255) must be used and
n the message code must be included in data word (DW).
For corresponding values, see Table “EDP Commands” at Item 4.2.2.
Example: “Request weight in no-motion" to DW=6, “Periodic request” to DW=7.
The address of the AD messages sent from DISOMAT consists of data block
and data word (firmly preset) for the message code. See Item 4.2.2.
Protocol Agreements
Synchronization Data Message Data Protection
<STX> 10 Bytes ... <DLE><ETX> <BCC>
IIn the following, the individual data transmission elements are characterized. The
Enquiry
Sender starts data transmission with control character <STX>.
Data Message
Data messages (send, request and response messages) are constructed as

follows:
Message header User Data <DLE><ETX><BCC>.
Acknowledgement
Receiver acknowledges successful data transmission with <DLE>; faulty data

Error Recognition

© Schenck Process

Upon errors in data transmission, transmitter repeats sending various times.
Repeats always start from enquiry.
Synchronization, Monitoring Times, Repeats

n Acknowledgement monitoring time tq = 2 sec.
n Response monitoring time ta = 5 sec.
n Enquiry monitoring time te = 2 sec.
n Max. number of enquiry repeats: 5
n Max. number of data repeats 5
Sending Priority
DISOMAT always has low priority. If both stations try to start data communication,
DISOMAT aborts sending and goes to receiving state.
Value Range
The value range of transmitted characters of a data section covers 8 bits, i.e. in
hexadecimal representation 00 to FF.
This value range requires a special treatment of user datas’ end code (<DLE>), if
the bit string of the <DLE> character is included in user data. This is done by
doubling the <DLE> character.
<DLE> Doubling
<DLE> occurring in user data is doubled by transmitter, for receiver to com-

pletely receive user data.
If two <DLE> codes are received, receiver resets doubling and treats <DLE> as
data byte.

© Schenck Process
Request Message Header With ”S5” Protocol
In ”S5” mode, all data in the message header are represented in hexadecimal
fashion. All messages start with two zero bytes ( ) followed by message type
(ED or AD), data block address, data word address and two coordination flags.
Byte No. Meaning

1 00
2 00
3
4 Message type (ED or AD)
5 Data block address = Scale number

6 Data word address = Command code
7
8 Data length (> 1) in words
9 Coordination flag
10
To keep configuration work down and ensure maximum data
safety, value FF is expected for every byte.
11 ... Data; length indicated in 7th and 8th byte. (At least one data word must be
sent.)
AD and ED Message Descriptions:

AD messages (SEND messages) consist of message header (10 bytes) followed
by data. Response message contains a 4-byte status information.
ED messages (FETCH messages) consist of message header (10 bytes).

Response message comprises 4-byte status information and requested data.

© Schenck Process
AD Message Construction
AD message in the Clear Tare example (AC)
Request message (SIMATIC DISOMAT )
Byte No. hex. ASCII Meaning

1 00
2 00
3 41 A Vommand: Output
4 44 D Type: Data
5 21 Destination: DB = Scale no., e.g. 33
6 02 Destination: DW = Clear Tare command code
7 00 Number
8 01 Number : 1 DW
9
10
FF
FF
Coordination flag (byte)
Coordination flag (bit) >
11 20 1st data byte — (blank)
12 20 2nd data byte – (blank)
Response message (DISOMAT —> SIMATIC).

Byte No. hex. Meaning
1 00 4-byte fixed length

2 00
< 3
4
00
xx xx= Error code (00 = Job OK; unequal to 00 = Error)
ED Message Construction
ED message in the ”Request Weight” example (TG)
This command returns the weight values to SIMATIC without no-motion inquiry.
SIMATIC can read out scale status (see Item 4.3). In our example, net = -123.5kg,
tare=100.0kg and material flow=12.3kg/sec.
Request message (SIMATIC —> DISOMAT )

1 00
2 00
3 45 E Command: Input
4 44 D Type: Data
5 21 Source: DB = Scale number, e.g. 33
6 02 Source: DW = Request weight command code
7 00 Number
8 0e Number : 14 DW
9 FF Coordination flag (byte)
>
10 FF Coordination flag (bit)

© Schenck Process
Response message (DISOMAT SIMATIC)
Byte No. hex. ASCII

Meaning
1 00
2 00
3 00
4 00 Error number (00 = No error)
5 20 1st data byte

6 2d - 2nd data byte
7 31 1 3rd data byte
8 32 2 4th data byte Net
9 33 3 5th data byte
10 2c 6th data byte
12 23 # 8th data byte - Separator
13 20 9th data byte
14 20 10th data byte
16 30 0 12th data byte Tare
18 2c , 14th data byte
< 23
24
20
31 1
19th data byte
20th data byte
Material flow kg/s
25 32 2 21st data byte

26 2c , 22nd data byte
27 33 3 23rd data byte
29 63 c 25th data byte - Scale status n1
30 30 0 26th data byte - Scale status n0
32 00 28th dummy byte
or, if an error has occurred:

2 00
3 00
< 4 00 xx = error number (00 = OK; not 00 = error)

© Schenck Process
Further Examples
Acquire Tare
Send message AT:
Byte No. Hex. ASCII Meaning

1 00
2 00
3 41 A Command: Output
4 44 D Type: Data
5 21 Destination: DB = Scale number, e.g. 33
6 01 Destination: DW = Tare command code
7 00 Number
8 01 Number : 1 DW
11
12
20
20
1st data byte - blank
2nd data byte - blank
>
Direct response message
Byte No. Hex. Meaning

2 00
< 3
4
00
00 Error code (00 = No error)
Delayed response message
Once weighing system has recognized no-motion or the 20-second no-motion

timeout has elapsed, DISOMAT sends the following message:
Byte No. Hex. ASCII Meaning1

1 00
2 00
4 44 D Type: Data
5 32 Destination: DB settable in menu tree, e.g. 50
6 54 Destination: DW permanently assigned with AT = 84
7 00 Number:
8 01 Number: 1 DW
< 11 30 0 1st data byte - Status 0 = OK 1 = Not effected
12 23 # 2nd data byte - Separator

© Schenck Process
Feeding Stopped
Send message BR:
Byte No. Hex. ASCII Meaning

1 00
2 00
4 44 D Type: Data
5 32 Destination: DB settable in menu tree, e.g. 50
6 50 Destination: DW = perm. assigned with BR = 80
7 00 Number:
8 01 Number : 1 DW
11
12
31
23
1
#
Feeding Stopped code
Separato
>
Response message:
Byte No. Hex. Meaning

2 00
3 00
< 4 00 Error code
DISOMAT automatically sends this message to SIMATIC provided that feeding

has been started by SIMATIC and the data block address has been entered at
DISOMAT menu item EDP Configuration in decimal fashion (e.g. 50, hex 32).
This message is output if:
n First HA command (Stop Feeding) from SIMATIC

n AB command (Abort Feeding) from SIMATIC
n First stop via keyboard or input contact
n Error in feeding operation.
Restart stopped feeding operation with ‘Start Feeding’ (”GO”, hex 24).
4.1.6 ASCII - Modbus

The ASCII-Modbus protocol corresponds to the message construction described
at Item 5.2. The user data, however, are in the ASCII format.
For type and address values, see “ZDV Commands” table at Item 4.2.2.

© Schenck Process
Computer, PC Coupling 4.2 Message Descriptions
4.2 Message Descriptions
4.2.1 User Data Construction

Data construction in protocol frame is organized as follows:
Address # EDP Command# Specific Data#
Address Meaning
Used to distinguish multiple scales or DISOMAT units operating in group mode,
the scale address must have two digits, e.g. 04 and an ASCII code.
DISOMAT units equipped with two channels reserve 4 addresses/channel.
Enter scale address in menu tree at Item ‘4431:EDP’.
1st address identifies the displayed scale.
2nd address …Scale 1
3rd address …Scale 2
4th address …Twin-unit scale
EDP Commands
The ”EDP Command” field consists of a 2-digit ASCII code used as abbreviation
of the command to be executed on DISOMAT , see Table at Item 4.2.2.
Example: AT Aquire Tare
ES Enter Setpoint
For ASCII-S5, the ‘Address #EDP Command#‘ sequence is replaced by the
message header of SEND/FETCH (AD/ED) messages.
The ”EDP Command” field is converted into data words within the addressed data
block.
The ‘Specific Data‘ are transmitted as user data in the ASCII code.
Specific Data
This part of the user data is variable and corresponds to the parameters sent to
DISOMAT using the relevant EDP command.
The Address and EDP Command fields are separated by #.
Example:
Scale adress 1 means:
Adress 1 = displayed scale
Adress 2 = Scale 1
Adress 3 = Scale 2
Adress 4 = Twin unit scale
If multiple devices are present on a bus, next DISOMAT receives scale address 5.

© Schenck Process
4.2 Message Descriptions Computer, PC Coupling
4.2.2 EDP Commands
Table of DISOMAT EDP Commands

Command Identifier (ASCII Type with Data word DW with Type addres
telegram) SIMATIC S5 SIMATIC S5/S7 with s with
J-Bus J-Bus
* = not DW Data length
implemented
dec. hex. dec. hex. dec. dec.
Group of ‘Scale Commands’:
Taring AT AD 1 1 6 1
Clear tare Key in tare AC AD 2 2 6 2
14 16
Zero setting ET AD 3 3 6 3
Connect scale AZ AD 4 4 4
WN AD 10 0a 0e
Query weight and dG/dt

Query weight in the no-motion state TG ED 5 5 3 5
TS AD 6 6 * *
Start cyclical output
*
SZ AD 7 7 *
‘Feeding’ group:
Specify setpoint ES AD 32 20 5 5 16 32
Query setpoint AS ED 33 21 3 33
Specify material number and setpoint SE AD 41 29 7 7 16 41
Query current material number and SR ED 42 2a 3 42
setpoint SD AD 43 2b 16 43
Specify data for specific sorts SA *
Query data for specific sorts 9 9
GB ED 34 22 50 32 3 34
Query balance SB ED 40 28 3 40
Read sort balances BL AD 35 23 6 35
Delete balances
Start feeding with current data GO AD 36 24 6 36
Start feeding data for specific sorts SG AD 45 2d 16 45
Stop feeding HA AD 37 25 6 37
Cancel feeding AB AD 38 26 6 38
Query feeding status
Query extended feeding status DG ED 39 27 9 9 3 39
DA *
‘General Control’ group:
Read all contacts TK ED 64 65 40 25 19 3 64
Set data processing contacts 68
EK AD 41 16 65
Contact status TA ED 66 44 53 35 * *
gaps S ED 67 21
Query faults 15
Acknowledge fault QU AD 42 3 66
Disomat B compatible * 43 6 67
Read function block parameters AP * 71
Set function block parameters EP AD * *
Disomat *
87 47 16 71
Read function block parameters PL *
Set function block parameters PS AD 74
* *
Start ‘Processing Function Block’ FS AD 57 16 87
77 4a 0e 6 74
PLC order telegram (bits) SS316 78 14
AD
PLC read telegram (bits) SL ED 4d 16 77
4e 3 78
‘General Control’ group:

© Schenck Process
Computer, PC Coupling 4.2 Message Descriptions
Set fast comparator SK AD 79 F 16 79

Read fast comparator GK * * * *
>Block keyboard LK AD 81 51 6 81
>Release keyboard UK AD 82 52 6 82
Weight telegram for legal-for-trade PC

PC * * * *
‘Paramerterising’ group:
Query equipment ID ID ED 128 80 43 B 3 128
Read form format DL * * * *

Set form format DS AD 130 82 16 130
Set time EU AD 131 83 16 131

Read maximum values LM ED 138 8a 15 F 3 138
Set maximum values SM AD 139 B 16 139
Read fixed tare values LF ED 144 90 50 32 3 144

Set fixed tare values SF AD 145 91 16 145
‘Printing’ group:
Specify string 1 EB AD 96 60 16 96
Specify one of five strings EI AD 98 62 16 98
printing telegram DR AD 97 61 16 97
There are a series of telegrams sent on the initiative of DISOMAT along with the previously described telegrams, all of which were
initiated by the data processing partners.
Note:
This does not apply to Modbus operatioon (DISOMAT is always slave here). These telegrams are only sent in SIMATIC S5
operation if the target data module that can be entered in the DISOMAT dialog is not equal to zero. Then the telegrams are
sent to the data word in this target data module with a fixed offset.
Feeding ended DO1 AD 0 0 12 0c
Weight in the no-motion state TS AD 16 10 10 0a
Periodical weight transmission TG AD 32 20 14 0e
Feeding interrupted BR AD 80 50 1 1
Taring carried out AT AD 84 54 1 1
Zero setting carried out AZ AD 88 58 1 1
Print-out ended
DR AD 100 64
1 is only sent if it was started via telegram
(GO or SG).
^^
1 wird nur gesendet, wenn über Telegramm gestartet wurde (GO bzw. SG).

© Schenck Process
4.2 Message Descriptions Computer, PC Coupling

© Schenck Process
Computer, PC Coupling
The table of command formats for the data processing commands in DISOMAT
Command Identifier Send or request telegram Reply telegram direct delayed
Group of scale commands:
Taring AT WN#AT# WN#AT#s# The telegram is being processed WN#AT#s# Command executed
Clear tare AC WN#AC# WN#AC#s#
Key in tare ET WN#ET#tara# WN#ET#s# S 0 with the MT scale when the tare value
Tare = tare weight is greater than the small range.
Zero setting AZ WN#AZ# WN#AZ#s# The telegram is being processed WN#AZ#s# Command executed
Connect scaleNot WN WN#WN# * WN#WN#w# w: currently connected scale

available for Opus
Query weight TG $) WN#TG# WN#TG#netto#tara#dG/dt#status#
net: Net (7-digit)

tare: tare (7-digit)
dG/dt: dG/dt (7-digit)
status: Scale status (refer to Chapter 4.3)
such as # -123,5# 50,0# 0,0#c0#

kg/t/g depending on the scale adjustment
Query weight in the TS) WN#TS# WN#TS#s# ? The telegram is being processed WN#TS#netto#tara#status#
no-motion state This telegram is sent after the weighing facility has
identified the no-motion state or the waiting time of
10 seconds is over.

© Schenck Process
The table of command formats for the data processing commands in DISOMAT
Start cyclical output SZ WN#SZ#w# WN#SZ#s# cyclical:

The telegram is being processed WN#TG#netto#tara#dG/dt#status#
w: Period in multiples of
0.1 seconds
acceptable values: 0 or 5-99
(w=0 turns off output)
* WN = 00 leaves the connected scale

WN = 01, 02, 03 connects the addressed scale.
$) Note: The TG and TS commands do not trigger weight registration in DISOMAT (printout and legal-for-trade memory). This is why they never may be used for triggering legal-for-trade weighing. Please
only use the DR command for this.
^^

© Schenck Process
Table of the command formats of data processing commands in DISOMAT

Feeding group:
Specify setpoint ES WN#ES#g# WN#ES#s#
g: Setpoint
for sort 1 (max. 7 digits)
such as #100# kg/t/g/ depending upon

scale adjustment
Not available for

Opus
Query setpoint AS WN#AS# WN#AS#g#
g: Setpoint (8-digit, right-justified 3
Not available for positions after the decimal point)
Opus
such as # 100.000# kg/t/g/ depending upon scale
adjustment
Specify material number and SE WN#SE#n#soll#ak# WN#SE#s#
setpoint n: Material number 1-10
target: Setpoint (max. 7 digits)
ak: optional order identifier,
maximal 25 characters of text
= string 5
such as #1#100#xy# kg/t/g depending on
scale adjustment
Query current material SR WN#SR# WN#SR#n#soll#
number and setpoint n: Material numbers 1-10 /Opus 1-2
target: setpoint
such as # 1# 100,0# kg/t/g depending upon
scale adjustment

© Schenck Process

Feeding group:
Specify data for sort SD WN#SD#n#vf#vk#hk#tol#opt#soll# WN#SD#s#
n: Material number 1-10
vf: Pre-fill switching threshold
vk: Pre-contact switching threshold
hk: Main contact switching theshold
tol: Tolerance range
opt: Optimisation factor target: *
such as #1#10#20#10#5#0,1#
kg/t/g depending upon scale adjustment
Query data for sort SA WN#SA#n# WN#SA#vf#vk#hk#tol#opt#soll#
n: Material numbers 1-10/Opus 1-2 Refer to command SA for parameters
Query balance GB WN#GB# WN#GB#g#w#
g: Balance total (11-digit, right-justified,
with 2 positions after the decimal point)
w: Number of bulk solids dumps (max. 5-digit)
Read the sort balances SB-0016 WN#SB# WN#SB#sb1#sb2#...#sb10#
sb1-sb10 : Sort balance (9-digit right-justified,
positions after the decimal point and
shown as in the display format)
such as # 123,4#...kg/t/g depending upon scale
adjustment
Clear balance BL WN#BL# WN#BL#s#
Start feeding with current GO WN#GO# WN#GO#s#
data

© Schenck Process

Feeding group:
Trigger feeding start SG WN#SG#n#soll#ak# WN#SG#s#
for specific n : Material numbers 1-10/Opus 1-2
sorts
target : Setpoint
ak: optional order identifier
maximal 25 characters
text = string 5
Stop feeding HA WN#HA# WN#HA#s# Reply: WN#BR#feeding is stopped
Cancel feeding AB WN#AB# WN#AB#s# Reply: WN#BR#Feeding interrupted
and WN#DO# feeding ended
Query feeding status DG WN#DG# WN#DG#stat#ist#soll#
stat: feeding status 0/1/2 “ none / active /
stopped
actual: actual value
target: setpoint
Query extended feeding DA WN#DA# WN#DA#stat#istg#sollg#sn#ist#soll#fg#ak#fk#
status stat: feeding status 0/1/2 “ none / active / stopped
istg: total actual value
sollg: total setpoint
sn: material number
actual: actual value of current bulk solids dump
target: setpoint of current bulk solids dump
fg: release status 1= feeding can be started
ak: order identifier max. 25 characters
text = string 5
fk: function block identifier (configuration
identifier) max. 10 characters text such as
‘acceptance scale’

© Schenck Process
Table of the command formats of the data processing commands in DISOMAT

General control group:
Read all contacts TK WN#TK# WN#TK#x1#x2#x3#x4#x5#x6#x7#x8#x9#x10#x11#x12#x
13#x14#a1#a2#
X1..x4: position of input contacts 1-4

x5..x10: position of output contacts 1-6
x11..x14: position of virtual data processing contacts 1-4
a1,a2: analog data processing outputs (10-digit,
right-justified, 3 positions after the decimal point)
(contact set = 1, contact not set = 0)

© Schenck Process

Contact status TA WN#TA# WN#TA#Netto#Tara#Status#WK#
Int-In-W#Int-In-Ä#
ICP-In-W#ICP-In-Ä#
Int-Out-W#Int-Out-Ä#
ICP-Out-W#ICP-Out-Ä#
PLS-In-W#PLS-In-Ä#
PLS-Out-W#PLS-Out-Ä#
data processing contacts#
net: display format, 7-digit
tare: display format, 7-digit
status: 4-digit, hex, bit-coded
WK:scale identifier 1 (scale 1), 2 (scale 2), 3 (twin-unit)
Int-In-X: internal input contacts, 2-digit, hex, bit-coded
X == W: current values
X == Ä: change since last telegram
ICP-In-X: OK extension to input contacts, 4-digit, hex, bit-coded
Int-Out-X: internal output contacts, 2-digit, hex, bit-coded
ICP-Out-X: OK extension to output contacts, 4-digit, hex, bit-coded
PLS-In-X: PLS inputs, 4-digit, hex, bit-coded
PLS-Out-X: PLS outputs, 4-digit, hex, bit-coded
data processing contacts: as with TK telegram

© Schenck Process

Set data processing EK WN#EK#x1#x2#x3#x4# oder WN#EK#s#
contacts WN#EK#x1#x2#x3#x4#abcd#
X1-x4: contacts 1-4
Set contact = 1,
Do not set contact=0
abcd: PLS input function blocks, hex,
bit-coded, such as 000f#
DISOMAT automatically resets any data
processing contact set after reading.
Query fault gaps S WN#AF# WN#AF#E-Text#
E-Text: Result number and text as display (max. 40 characters)

Acknowledge fault QU WN#QU# WN#QU#s#
You can only acknowledge faults of the message, warning and

alarm classes. You have to acknowledge malfunction class faults in
the menu tree of DISOMAT (after keying in your password) .
Read DISOMAT AP WN#AP#b# WN#AP#b#p1#..#pn#
compatible
function block
parameters b: Function block identifier b: Function block identifier
Not available for (refer to the Data Communication p1..pn: Parameters
Opus manual
DKI116 Chapter 6.4 )
*: Sollwert, nur bei SWA VKD204000

© Schenck Process

Set DISOMAT EP WN#EP#b#p1#...#pn# WN#EP#s#
compatible
function block
parameters b: Function block identifier
(refer to the Data Communication
manual
DKI116 Kap. 6.4 )
Not available for p1-pn: Parameter

Opus
Read DISOMAT PL WN#PL#b# WN#PL#b#p1#...#pu#
_function block
parameters b: Refer to the function block description b: Function block identifier
Read DISOMAT for the function block identifier p1...pn: Parameter values of the function block
function block Refer to the function block description for
parameters the number
Not available for

Opus
Set DISOMAT PS WN#PS#b#p1#...#pn# WN#PS#s#
function block
parameters b: Function block identifier s ¹ 0: Feed operation active,
p1...pn: Parameter values no parameter change available now
Not available for
Opus
PLC order telegram SS316 WN#SS#XX# WN#SS#s# Other reply telegrams depending upon
(bits) requirements: WN#AT#s#, WN#AZ#s#,
Not available for WN#BR#s#, etc.
Opus XX=2 Order bytes (refer to Chapter 4.3, page
47
for an explanation)

© Schenck Process

PLC read telegram SL WN#SL# WN#SL#B1B2B3#netto#brutto#dg/dt#
(bits)
Not available for B1: Byte 1 = scale status

Opus B2: Byte 2 = data processing and input contacts
B3: Byte 3 = output contacts
(refer to Chapter , page for the meaning)
Net: Net (7-digit)
Gross: gross (7-digit)
dG/dt: dG/dt (7-digit)
Set fast comparator SK WN#SK#n#e#ein#aus# WN#SK#s#
n: Comparator number 1-6

e: activate: 0/1 no/yes
Not available for on: turn-on value
Opus
on: turn-off value
Read fast GK WN#GK#n# WN#GK#n#e#ein#aus#
comparator n: Comparator number Refer to command SK for parameters
Not available for

Opus
Block the keyboard LK WN#LK# WN#LK#s
for 1 minute
Release keyboard UK WN#UK# WN#UK#s

© Schenck Process
The table of command formats for data processing commands in DISOMAT

Paramerterising group:
Query equipment ID WN#ID# WN#ID#t sk sd sn#
ID
T: Text DISOMAT
Schenck Process GmbH
sk: software identifier
sd: date written
sn: equipment serial number
Read form format DL WN#DL#nr# WN#DL#nr#muster#
nr: Number of form format 1/2/3/4 nr: Numbers 1-3 = printing format 1-3
Number 4 = data processing format
(variable part)
Number 5 = side head format
Number 6 = legal-for-trade memory
format (variable part)
Numbers 7-9 = format of printing 4-6
Pattern: format string of the
printing pattern
Set form format DS WN#DS#nr#muster# WN#DS#s#
Refer to under DL for parameters
Set time EU WN#EU#TT.MM.JJ#hh:mm:ss# WN#EU#s#
Tag.Monat.Jahr#Stunde:Minute:Sekunde
Read maximum LM WN#LM# WN#LM#dg#bl#sch#

values
Dg: Max. dG/dt (10-digit, right-justified, 3
Not available for positions after the decimal point)
Opus bl: Max. balance (12-digit, right-justified,
2 positions after the decimal point)
sch: Max. bulk solids dumps (5-digit)

© Schenck Process

Set maximum SM WN#SM#dg#bl#sch# WN#SM#s#
values Refer to command LM for parameters
Not available for

Opus
Read fixed tare LF WN#LF# WN#LF#w1#...#w9#
w1-w9: fixed tare values
Set fixed tare SF WN#SF#w1#...#w9# WN#SF#s#
values w1-w9: fixed tare values
‘Printing’ group:
Specify string 1 EB WN#EB#text# WN#EB#s#
text: max. 30 character of text
Specify one of five EI WN#EI#n#text WN#EI#s
strings n: string numbers 1-5
text: max 25 characters

© Schenck Process

Printing telegram DR WN#DR#n#text# WN#DR#s# After printing:
n: * Number of the printing pattern If s ¹ 0, it is still moving (send it again later). WN#DR#n#x#status#string#
0-6 n= Number of the printing pattern
text: string texts
(max. 25 characters) X=0 No fault when printing
X=1 Faults occurred when printing
or with several strings X=2 Faults with data in the legal-for-trade memory
WN#DR#n#text1#text2#...#text5# Status= Refer to Chapter , page for the scale status.
String= formated string.
text1-text5: max. 25 characters per
string text Refer to Chapter 5.2.1.5 in the Operating Manual for an example,
The weight description is generally constant in its length, but it is

dependent on the system configuration, such as:
n = 0: Registering in the 1-scale system, legal-for-trade brackets, Dimension “t”

legal-for-trade memory # <0,00t> B # -> length 17
n = 1...6: printing pattern 1-scale system, no legal-for-trade brackets, Dimension “kg”
# 150.0kg B # -> length 15
2-scale system, legal-for-trade bracket, Dimension “t”
# <17.34t> B 1# -> length 17
The texts are printed if the BZ1-BZ5 string

identifier is also entered in the corresponding
printing pattern.
The DR command triggers weight registration in DISOMAT (printer and legal-for-trade memory). This is why it can be used to trigger legal-for-trade weighing. Please read the notes in Chapter 2.1 if weight is
further processed in non-legal-for-trade plant components.

© Schenck Process

DISOMAT message group: DISOMAT sends a telegram.
Feeding DO WN#DO#g1#g2#g3#
ended
g1: actual value
g2: actual value - setpoint
g3: optimised main contact
This telegram is only sent if feeding was

started per telegram (GO or SG).
Interrupt BR WN#BR#
feeding
^^

© Schenck Process
Computer, PC Coupling 4.3 Commands Explanations
4.3 Commands Explanations

WN Scale number always in 2-digit form, e.g. 01
s Codes number of EDP command status
If the code number unequals 0, command was not properly executed.
S = 0: Command execution OK
s>< 0: Command execution faulty
status Scale status in hexadecimal format
Bit No. Meaning
0 Underrange
1 Overrange (weight > full scale value)
2 Tare computed
3 Exact zero
4 —- Not used —-
5 Weight invalid
6 Tare acquired
7 No-motion recognized
With 16-bit status:
Bit No. Meaning
8 Initialisation
9 —- Not used —-
10,11 Range (1,2,3)
12 In zeroing range
13 Twin-unit scale
14 Multi-divisional scale
15 Multi-range scale
Example: Status ”c0” is interpreted as hexadecimal number 0xc0 and

converted into binary 1100 0000.
Bit: 76543210 Bits 6 and 7 are set, i.e. tare is acquired;

Value: 11000000 no-motion, recognized.
Note:Hexadecimal numbers a...f are always transmitted as lower-case letters.

© Schenck Process
4.3 Commands Explanations Computer, PC Coupling
SS vUsed in PLC order message

Message type: Bit output
Data block: Scale number
Data word: 4d (hex)
Message construction: 16 bits, each bit coding an order to connected

scale.
Bit setting starts order. Meaning of individual bits:
Bit No. Meaning
0 Acquire tare
1 Clear tare
2 Set to zero
3 Start feeding
4 Stop feeding
5 Abort feeding
6 Clear balance
7 Acknowledge error
8-15 Standby
Selected command is executed only upon first sending of message (”rising edge”).
To have command executed, reset relevant signal..

© Schenck Process
Computer, PC Coupling 4.3 Commands Explanations
SL Used in PCL read message
Byte Explanation Bit No. Meaning

0 Underrange
1 Scale status
1 Overrange
2 Tare computed
3 Exact zero
4 Resolved mode
5 Weight invalid
6 Tare acquired
7 No-motion
8 Contact 1
2 Output of DISOMAT
physical input
9 Contact 2
10 Contact 3
11 Contact 4
12 EDP 1
13 EDP 2
Output of DISOMAT
virtual (EDP) outputs statusses:
14 EDP 3
15 EDP 4
16 Contact 1
3 Output of DISOMAT
physical output contact statusses
17 Contact 2
18 Contact 3
19 Contact 4
20 Contact 5
21 Contact 6
22 Standby
23 Standby
Sequence in message:
Bytes: 1 2 3
Bits: 76543210 15...8 23...16

© Schenck Process
4.3 Commands Explanations Computer, PC Coupling
- Reserved for user’s notes -

© Schenck Process
Coupling for SPS and PLC 5.1 Modbus-RTU
5 Coupling for SPS and PLC

This chapter describes coupling between an SPS/PLC and the equipment.
· DISOMAT Satus (only for the process image “No text/4ID” with Profibus and
DeviceNet)
· DISOMAT Opus
· DISOMAT Tersus
The equipment is called the controller below. The text will explicitly point out
whether parts of this description are only for one specific piece of equipment.
Note:
· The BV-H2331 System Manual describes the standard and short process
images of DISOMAT Satus that are compatible with DISOMAT T.
· The description of the Profibus is based upon the VPB8020 hardware.
· The description of DeviceNet is based upon the VCB8020 hardware.
· You can find the common database for all controllers and protocols in the
chapter on “Available Data” at the end of this document.
5.1 Modbus-RTU
The general specification of the Modbus protocol describes two ways to code data:
n 7-bit ASCII framing

n RTU framing
The controllers only work with RTU framing.

The specification below describes the special properties for coupling a process
control system (PLS) and the controller.
Terminology
The following chapters describe:
HEXADECIMAL values in the form of 0x1234 and
DECIMAL values in the form of 1234.
Logical hierarchy
The process control system is bus master and the controllers are treated as
individual slaves.
One telegram cycle always consists of a query from the master (PLS) and a reply
from the slave. The reply is either the acknowledgment to an order from the
master or a data record that the master requested in its query.
Physical arrangement
The best way to couple the bus is via RS485 (2- or 4-wire) interface.
This is interface S3 with DISOMAT Satus and Opus while interfaces S1 or S2 are
available for DISOMAT Tersus.
You can find the connection diagram in the system manual.
DISOMAT ® Opus, Satus, Tersus, Datenkommunikation BV -H2359DE/0722 49

Schenck Process
5.1 Modbus-RTU Coupling for SPS and PLC
Data format and data signaling rate

This uses the RTU format with an 11-Bit character frame. The data format, baud
rate and interface physics are set in the interfaces menu item.
Data position
The transmission begins at the same time as the MSB.
The setpoints and readings are transmitted both in the IEEE float format (IEEE
754, 32 bits) and in the integer format. You have a 16-Bit word available with the
integer format and you can adjust its resolution over a range of 0-MAXTEILE while
maximum resolution is 215-1 parts.
Here is an example of transmitting the value 150.5 in the IEEE format (this gives
the sequence in the circuit):
Byte 1: sign / Byte 2: Byte 3 Byte 4:

exponent Mantissa 1 Mantissa 2 Mantissa 3
0x43 0x16 0x80 0x00
All control information and statuses 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
information.
Guaranteeing Transmission
The characters are secured by a parity bit (see MODBUS specifications).
The telegrams are secured by a checksum (CRC16; see Modbus specifications).
The Modbus specification defines the reaction to transmission errors.
You can guarantee the transmission between the controller and the control system
in the controller via TIMEOUT. Then, the controller expects a telegram from the
control system at specific intervals. The type of telegram is not important here.
You can set both the interval and the type of reaction from the controller to no
telegram on the controller via parameters and you can find the events notes in
each operating manual of the controller. The TIMEOUT = 0 setting means that the
data flow between the controller and master is not monitored by the controller.
Routines
Any routines important for specifying data are described in each section.
Subscriber addresses
Every controller is given a slave address beginning with 1 in ascending order. The
highest address it is possible to set is labeled MAXSLAVE in the following text.
You can set the address by dialog on the controller. MAXSLAVE has a value of
254. Address 0 is the broadcast address..

© Schenck Process
5.1.1 The structure of the data telegrams

The data are transmitted in separate telegrams arranged according to data types
(binary or analog) to make it easier to process the data in PLS.
All programs have the following structure:
T1 T2 T3 Slave Function Data Check T1 T2 T3

Address Code CRC16
Break 8 bits 8 bits n * 16 bits 16 bits Break
Several readings can be transmitted simultaneously.

The start address of the data registers and then the data are arranged in the ‘Data’
field. The number of data is defined by the LENGTH field (word count or byte
count). This information depends upon the function code and direction of
transmission at various points (explicit or implicit length information). No length
information is given if a single reading is transmitted (function codes 5 or 6).
Function codes:
Function Description
code
1 Bitwise reverse reading of control information (one or several bits)
2 Bitwise reading of status information (one or several bits)
3 Wordwise (reverse) reading of setpoints and readings (one or several words)
4 Wordwise reading of status information (one or several words)
5 Bitwise (re)setting of control information (always one bit)
6 Wordwise writing of control bits or setpoint values (always one data word)
15 Bitwise writing of control information (one or several bits)
16 Wordwise writing of setpoints in the IEEE format (one or several data words)
Note:
Often, the control system should add what is known as a “segment address”
(depending upon the function code) to the data address to be described.
Furthermore, the data address should be set up one because the register
addresses start at 1 with the Modbus protocol. In other words, the rule for
configuring the data address is:
The data address = segment address + controller address + 1.

© Schenck Process
The structure of the data field:
The data telegram from PLS
ADDRESS HI start address of the data registers

ADDRESS LO start address of the data registers
VALUE HI content of the data registers
VALUE LO content of the data registers
The request telegram from PLS
ADDRESS HI start address of the data registers

ADDRESS LO start address of the data registers
LENGTH HI number of the data fields in words
LENGTH LO number of the data fields in words
The readings telegram from the controller
LENGTH number of the data fields in bytes

VALUE 1 HI content of the data registers
VALUE 1 LO
...
VALUE n HI
VALUE n LO
All fields are 8 bits long.

© Schenck Process
5.1.2 The structure of the fault telegrams

The fault telegrams have the following structure
T1 T2 T3 Slave Function Error CRC16 T1 T2 T3

Address Code Code
Break 8 bits 8 bits 8-bits 16-bits Break
The value 0x80 is added to the ‘Function Code’ value from the request in the fault
telegram. You can see the meaning of the fault codes in the table below.
Error Code This means
1 The subscriber does not support the function requested (FC)
2 Faulty data address such as

- data address out of range
- data address with IEEE or odd
- data offset + length too long
3 The wrong data type such as

- The wrong data with FC 5 (0xFF00 and 0x0000 are acceptable)
- The data length is smaller than 0
- The length requested is too long
5.1.3 The address ranges of the coupling

The following data ranges are defined for Modbus coupling.
The writing range with

- controll information and
- setpoints (in IEEE or integer format)
- predetermination values in the LONG integer format)
- text (not with DISOMAT Satus) and the reading range with
- status information and
- readings (in IEEE or integer format)
- readings in the LONG integer format
- text (not with DISOMAT Satus)

© Schenck Process
5.1.4 Data from the process control system

The data from the control system can always be assigned to one of the groups
specified:
· Control bits -The information transmitted is assigned to one of the 16 bits of the
PLS-DIn1-16 function blocks. What effect the control information has depends
upon how the function block is wired. Please ensure that the desired function
block is also loaded (with the Load Fixed Linkage function). The positive flank
had this effect on all control bits and the status has to be pending for at least
100 ms to be identified unambiguously. The bit should be taken back after
carrying out the control function. A bit number (which of the possible 16 bits
should be changed) may be calculated from the four lowest-value bits in the
data address LO. If, for instance, the database address is 0x1010, this
references bit 0 while bit 7 is addressed in Highbyte with the address 0x101F.
The value 0xFF in Highbyte of the control word sets the flag while the value
0x00 deletes the flag (function code 5).
· Commands- A 16-bit data word is always transmitted as a command. There

has to be a change for a command to be effective. If you would like to execute
the same command several times, you have to transmit the ZERO command
between commands.
· Analog predetermination values - These values can be transmitted as an IEEE

floating point value (4-byte) or an integer (2-byte).
· (String) texts (not with DISOMAT Satus)
Control information (PLS-DIn 1-16 and commands)

The telegram to the controller (function codes 5, 15, 6,16) has binary information
that you can read back with function codes 1 and 3.
Bus address 1... MAXSLAVE
Function codes 1, 5, 15 bit operations
Function codes 3, 6, 16 word operations
basic data address 0x0010 commands

0x0020 PLS-DIn 1-16
The number of data words / bits 0x0002 / 0x0020

© Schenck Process
General control telegram: (commands)

Slave FC Data address Data CRC
address (1 byte) (2 bytes) (2 bytes) (2 bytes)
(1 byte)
Wordwise presetting of commands:

Slave FC Data address Data CRC
address 0x06 0x0010 (1 Wort)
0x01-0xfe
For example, wordwise presetting (commands):

Slave FC Data address Data CRC Meaning
address
0x06 0x0010 0x0001 Taring
0x01 0x06 0x0010 0x0002 Clear tare
0x01 0x06 0x0010 0x0003 Zero setting
0x01 0x06 0x0010 0x0080 Acknowledge
0x01 0x06 0x0010 0x0000 error
0x01 Reset
Note:
You can only specify commands with FC 6 or 16 because this is a number, not
bit-coded data. This means that only one command can be executed per
transmission.
For example, for bitwise presetting via function block (PLS-DIn 1-16):
Slave address FC Data address Data CRC Meaning
0x01 0x05 0x0020 0xFF00 Set PLS-DIn 1

0x01 0x05 0x0020 0x0000 Reset PLS-DIn 1
0x01 0x06 0x0020 0x0010 Set PLS-DIn 5
Data addresses Meaning
0x0010 Low Byte Command number (refer to the chapter on

Available Data Specifications)
0x0020 Low Byte function blocks PLS -DIn-1 bit address 0x0020
PLS -DIn-2 0x0021
PLS -DIn-3 0x0022
PLS -DIn-4 0x0023
PLS -DIn-5 0x0024
PLS -DIn-5 0x0024
PLS -DIn-6 0x0025
PLS -DIn-7 0x0026
PLS -DIn-8 0x0027
0x0020 High Byte function blocks PLS -DIn-9 bit address 0x0028
PLS -DIn-10 0x0029
PLS -DIn-11 0x002A
PLS -DIn-12 0x002B
PLS -DIn-13 0x002C
PLS -DIn-14 0x002D
PLS -DIn-15 0x002E
PLS -DIn-16 0x002F

© Schenck Process
Predetermination values in the IEEE format

A telegram to the controller (function code 16) has predetermination values in the
IEEE format. You can read back this information with function code 3.
Function codes 16, 3
basic data address 0x0x100
Number of data words 0x0012
The general telegram in the IEEE format:

Slave FC Data address Length in Byte count Data/ CRC
address words Value
(1 byte) (1 byte) (2 bytes) (2 bytes) (1 byte) (4 bytes) (1 byte)
The setpoint value in the IEEE format:

Slave FC Data address Number in Byte Data CRC
address words count
0x01-0xfe 0x10 0x0100 0x0012 0x0024
An example of a setpoint telegram

(manual tare 1 = 100 kg for slave1):
Slave FC Data address Length in Byte Data CRC
address words count
0x01 0x10 0x0100 0x0002 0x04 0x42c80000
Refer to the chapter on Available Data Settings

© Schenck Process
The predetermination values in the integer format

You can also transmit the IEEE setpoints with the 6/16 function codes in the
integer format always using the final value set in the parameters as the reference
value
For example: 0 ... MAXTEILE correspond to 0 ... scale final values in kg.
You can read back this information with function code 3.
Function codes 6, 16, 3
basic data address 0x0200
Refer to the chapter on Available Data Settings for the table of valid addresses
Note:
Integer format values are always positive while negative values are set to zero.
Setpoints in the LONG integer format

Refer to the chapter on Available Data Settings for the table of valid addresses

© Schenck Process
Transmitting texts to the controller

For instance, this telegram can be used to transmit formatted texts (such as
printing strings) to the controller with a maximum text length of 32 characters per
string.
The print form further processes 25 of these 32 characters. The rest is not used
and is replaced by the zero value when reading back. You can also combine all
strings into one setpoint telegram by filling up each partial string to 32 bytes.
Number of data words 0x0010 (words per string)
The following text specifications are implemented:

Meaning Text ID
String text 1 1 (basic data address 0x0600)
The general telegram format:

Slave FC Data address Length in words Byte Data/text CRC
address count
(1
(1 byte) byte) (2 Byte) (2 bytes) (1 byte) ( as much as 160 (2 bytes)
bytes)
Some examples of text setpoint telegrams for slave 1.

n String text 1
n String text 3
n All string texts (1-5)
Slave FC Data address Length in words Byte Data CRC

address count
0x01 0x10 0x0600 0x0010 0x20 0x41424344...

0x01 0x10 0x0620 0x0010 0x20 0x41424344...
0x01 0x10 0x0600 0x0050 0xA0 0x41424344..
If the number of text bytes is odd, fill up the text with a space at the end.

© Schenck Process
5.1.5 Data on the process control system

Status information
The following telegram is used for requesting status information. Status
information may be requested wordwise (function code 4) or bitwise (function code
2). FC3 can also be used instead of FC4.
Function codes 2, 4, (3)
The number of data words / bits 0x0018/0x0180
The general request telegram
Slave address FC Data address Length CRC

(1 byte) (1 byte) (2 bytes) (2 bytes) (2 bytes)
Wordwise request of status information
Slave address FC Data address Length in words CRC

0x01-0xfe 0x04 0x1300 0x0018
Bitwise request of status information
Slave address FC Data address Number of bits CRC

0x01-0xfe 0x02 0x1300 0x0180
An example of a request (status word):

0x01 0x04 0x1300 0x0001
0x01 0x02 0x1300 0x0010
Refer to the chapter on Available Data for the Controller Data for the list of valid
addresses

© Schenck Process
Readings in the IEEE format

The control system can request readings with the following telegram in the IEEE
format.
The dimensions of these readings are always kg or kg/second.
Function codes 4, (3)
Number of data words 0x00D0
The general request telegram:

Readings request in the IEEE format
Slave address FC Data address Length in words CRC

0x01-0xfe 0x03 0x0700 0x007C
An example for requesting the gross weight on scale 1:

0x01 0x03 0x0700 0x0002
addresses

© Schenck Process
Readings in the integer format

The host system can request the IEEE readings in the integer format with the
following telegram using the final value set in the parameters as the reference
value.
The dimensions of these readings are always kg or kg/second.
Bus address 1..MAXSLAVE
The base data address can be calculated from the IEEE address according to the
formula (refer to the section on available data for the controller data).
For example: rated weight, unrounded, kg
400HEX + (736HEX - 700HEX) /2 =
400HEX + 36HEX / 2 = 400HEX + 1BHEX = 41BHEX
Note:
Integer format values are always positive while negative values are set to zero.
Readings in the LONG integer format

Number of data words 0x000E
addresses

© Schenck Process
Read the texts of the controller

For instance, this telegram can be used to read formatted texts (such as printing
strings) with a maximum text length of 32 characters per string.
Number of data words 0x0010, data words per string
The general request telegram::

An example of request for text

0x01 0x03 0x0500 0x0010

© Schenck Process
5.1.6 Modbus interface parameters
What the parameters mean:
q Internal address defining the bus address (0-254)
q Reference value for converting a physical quantity into parts that are
transmitted (1-32767)
such as 10,000,000 kg <> 32 767 parts.
q Final value the maximum value to be transmitted when the

quantity to be transmitted reaches a reference value.
q Interface selecting the fieldbus interface
q Timeout for monitoring the interface in seconds;
0 s = no monitoring
1-300s = value range
q Swapping order of bytes for floating point numbers and words
on the bus (BIG Endian, BYTE Swap, WORD Swap,
LITTLE Endian)
Note:
If monitoring is activated
-address errors
-function code errors, and
- incorrect length information
are also shown as communication errors in the controller’s display.

© Schenck Process
5.2 Modbus/TCP
5.2 Modbus/TCP
The chapter below describes the functionality of the controllers as servers on
Ethernet.
The following are described in detail::

n Server configuration
n Data exchange between an Ethernet client and the controller per Modbus/TCP,
n Notes for troubleshooting and diagnosis
n It is connected via RJ45 plug on the VFE xx.
n The server can exchange data with as many as 3 clients simultaneously. If the
DISOPLAN start-up tool is used, it can occupy one of the three available
channels if coupling is performed via network. The data are either sent as
Modbus/TCP packets or are expected as such from outside. The function scope
is identical with that of Modbus-RTU excepting the Modbus/TCP header (refer to
Chapter 5.1.1–5.1.5).
n The controller functions like a Modbus/TCP server as per the standard OPEN
MODBUS/TCP SPECIFICATION, Release 1.0,’ 29th March, 1999. It can handle
all class 1 and 2 function codes (except for FC7) and the most important class 2
codes (FC15 and FC23).
n This data representation is based entirely on the Modbus standard. The TCP
safety layer takes on the role of the Modbus telegram check sum (CRC 16). The
controllers evaluate the length field and protocol identifier and all other bytes are
sent back in the reply unchanged.
n Customer applications should always set the protocol identifier to zero.

© Schenck Process
5.2 Modbus/TCP
All stations in the Ethernet network are unambiguously identified via IP address.
This is the reason why the Modbus slave address can always be set to 1.
5.2.1 Example telegrams

The lines below show the structure of the Modbus/TCP telegrams. The first
column is the telegram of the bus master to the scale and the second column is
the scale’s reply.
Data to Scales Scale’s Reply Meaning

00 00 00 00 00 06 00 00 00 00 00 06 Taring
01 06 0010 0001 01 06 0010 0001
00 00 00 00 00 06 00 00 00 00 00 05 Read group status
01 03 0300 0001 01 03 02 xx xx
00 00 00 00 00 06 00 00 00 00 00 23 Read gross weights on channels 1-8
01 03 0748 0010 01 03 20 xx ..... xx
00 00 00 00 00 0B 00 00 00 00 00 06 Write setpoint (value = 163.34)
01 10 0110 0002 04 4323 5678 01 10 0110 0002
5.2.2 Diagnosis and Troubleshooting

The event message is a group message for all faults concerning the fieldbus
connection. These are:
n Different station addresses sent to the master and scales.
n There is a problem with the cabling between the fieldbus connection and main
board.
n The fieldbus cable is defective or incorrectly connected.
n The timeout parameter has been set at too small a value. Change the
parameterisation of the scales.
n An unacceptable ID (data address) was identified in the telegram of the master
to the scale.
Also refer to the section on fault codes (also refer to Modbus-RTU).

© Schenck Process
5.2 Modbus/TCP
5.2.3 Parameterising the controller

Parameterising should be carried out with controllers both with the operator panel
and DISOPLAN.
The parameter description applies to both pieces of equipment.

© Schenck Process
5.2 Modbus/TCP
Parameters Value range Default value Explanation

Protocol type All fieldbus protocols OFF Protocol selection: in this case, Modbus/TCP
Timeout Host 0-300 s 0s The parameter is used for interface monitoring.
ZERO meansthatthe interface is not
monitored.
IP address 192.168.240.1 Manual IP address assignment
Network mask 255.255.255.0 Delegating the subnetwork masks
Gateway 0.0.0.0 Delegating the standard gateway address
Notes
If you operate the controller on a local subnetwork with an internal network card for this network, it
would make sense to set the PC network adapter as follows:
n IP address: 192.168.240.254
n Network mask: 255.255.255.0
n Gateway: 0.0.0.0
n Controller 1-n: 192.168.240.n
where n=1-253
n IP addresses have to be unambiguous. This is why you should ask your system
administrator for valid addresses that are not in use.

© Schenck Process
5.2 Modbus/TCP
- Reserved for user’s notes

© Schenck Process
5.3 Profibus DP protocol

The general specification of the Profibus-DP protocol is in EN50170. The
specification below describes the special properties for coupling a process control
system and the controller.
IMPORTANT:
Please remember that the last physical subscriber has to terminate the Profibus
with a terminating resistor. There may be communication malfunctions if this
subscriber is taken by the bus.
Terminology
Logical hierarchy
The process control system is bus master and the controllers are treated as
individual slaves.
from the slave (controller). The bus master cyclically acquires a process image of
the controller of no more than 70 bytes and cyclically transmits a command
telegram to the controller of no more than 56 bytes. The master is notified of the
current size of the process image by the selection of the correct modules from the
equipment master data file (refer to the table on ‘Assigning the Parameter Setting
of the Profibus Interface to Modules in the GSD File’ at the end of the chapter).
Important:
The controller is modeled as a modular slave. If a new module is activated on the

master, the same set of parameters has been activated on the controller. The
reverse is also true.
For example:
Set of parameters number ID 4
Text block 4-byte text
Module (refer to GSD) “Short Text - 4ID”

© Schenck Process
Data format
The setpoints and readings are transmitted in the IEEE float format (IEEE 754, 32
bits) or the Siemens float format.
The transmission always begins at the same time as the MSB..
The transmission between the controller and the control system can be secured in
the controller by TIMEOUT.
The controller expects a telegram from the control system at certain intervals. Both
the interval and the type of controller’s reaction
to no telegrams (refer to the chapter on Event Messages in the operating manual)
can be set on the controller via parameters. The setting TIMEOUT = 0 means that
the data flow between the controller and control system is not monitored by the
controller.
Routines
Any routines important for specifying data are described in each section.
highest address it is possible to set is labeled MAXSLAVE in the following text.
You can set the address by dialog on the controller and MAXSLAVE has the value
126.
5.3.1 Data segments

We distinguish:
The writing range with

n control information,
n predetermination values in the IEEE format,
n Setpoints in the LONG integer format
n Texts from the master to the controller (not with DISOMAT Satus)
and the reading range with

n status information
n Readings in the IEEE format
n Readings in the LONG integer format
n The controller’s texts
Blocks of four bytes each can be unambiguously addressed with a two-byte

identifier (ID; refer to the tables on “Available Data”).

© Schenck Process
5.3.2 Structure of user data

This means that the telegrams of cyclical data transmission have the basic
structure below:
Protocol frame Texts (TXT) User data Protocol frame

(Header) Optional Process data (Trailer)
Figure 1 The basic structure of the Profibus telegrams
The types below have been defined:

n User data without a text range and with defined setpoint and process data
(white) and as many as 8 additional values that can be selected via ID (grey).
Also refer to Figure 2
n User data with a text range and with the selection of process data described
above.
Text range (TXT)
You can read or write texts with as many as 128 bytes with the TXT telegram part.
The section on “Text Transmission via Profibus DP” describes the necessary
mechanisms of order/reply identifiers.
We distinguish 4-and 20-byte text blocks where the longer variant should only be
used with greater quantities of text to keep the transmission period low.
Process data range
You can use the process data to transmit control words and setpoints (orders:
master —> 6 controller) or state words and actual values (replies: controller —>
master).
The process data transmitted go into effect immediately.

© Schenck Process
72
Data packets without text block
32 Bytes
max. Paketlängen
C
F P- P- 16 - 32 Bytes
o Preset Preset ID ID ID ID ID ID ID ID
C ID ID
m value 1 value 2 1 2 3 4 5 6 7 8
B 1 2
m
S Gross
F Gross
t ID in
C unroun Value1 Value2 Value3 Value4 Value5 Value6 Value7 Value8 14 - 46 Bytes
a 1 display
B ded
t format
Data packets with 4-Byte text block 32 Bytes
C
F P- P- 24 - 40 Bytes
BV-H2359GB/0722
Text block C ID ID
m value 1 value 2 1 2 3 4 5 6 7 8
B 1 2
m
S Gross
F Gross
t ID in
Text block C unroun display Value1 Value2 Value3 Value4 Value5 Value6 Value7 Value8 22 - 54 Bytes
a 1
B ded
t format
Text
Text Header
4 Byte
4 Byte
Data packets with 20-Byte text block 32 Bytes
Figure 2 The user data structure of Profibus telegrams

C
F P- P- 40 - 56 Bytes
Text block C ID ID
m value 1 value 2 1 2 3 4 5 6 7 8
B 1 2
m
S Gross
F Gross
t ID in
Text block C unroun Value1 Value2 Value3 Value4 Value5 Value6 Value7 Value8 38 - 70 Bytes
a 1 display
B ded
t format
Text Header Text

4 Byte 20 Byte
© Schenck Process
DISOMAT Opus, Satus, Tersus, Data Communication
The bright areas are the minimum parts of the telegram and they cannot be
changed. You can add as many IDs piecewise to the telegrams (depending upon
the set parameters) as needed in the current application.
Note:
Reading-writing in double words in S7 systems: please remember that the double
words cannot be read or written with the SFC14 and SFC15 function modules of
the S7 systems. Instead, use direct peripheral access.
Examples of telegrams
The following figure shows the basic structure of Profibus telegrams. The first line
is the telegram from the bus master to the controller and the second line is the
controller’s reply.
Example 1: Data transmission without a text block and without variable

user-defined identifiers (ID)
Parameter settings:
Text block no
number ID 0
Telegram master to the controllers.
FKB Commands ID Manual tare or ID Manual tare or FKB

bin. out FKB analog analog
(2
bytes) (2 bytes) (2 bytes) (4 bytes) (2 bytes) (4 bytes)
Reply of the controller
FKB bin Status Mirror-ID Scale showed Gross

in Scale in this gross Scale displayed
displayed case: zero rounded off in the
display format
(2
bytes) (2 bytes) (2 bytes) (4 bytes) (4 bytes) (2 bytes)
The commando telegram that changes manual tare for scale/group 1 and specifies
the first analog value of the analog function block:
FKB binary command ID manual tare1 value of manual tare 1 ID FKB1/1

value
xx xx xx xx xx xx 2000 42 10 00 00 200C 42 C8 00 00
The values for (control) commands

00 01 Taring on the scale displayed
00 02 Clear tare on the scale displayed
00 03 Zero setting on the scale displayed

© Schenck Process
Remarks
The identifier and corresponding values in the telegram from the master to the
controller are always expected in precisely this order and position. If an ID is
zero,the corresponding value will not be evaluated. The control and status
information is always combined into packets of four bytes. If the wrong identifier is
used, the datawill be rejected.
These specification data have to be pending at least 100 ms to ensure that the
controller can identify them without any problems.
The values in the reply telegram are identified using the position in the telegram.
This is the reason why identifiers are not needed.
Example 2: Data transmission without a text block and with 2 variable user-defined
identifiers (ID)
Parameter settings
Text block no
number ID 2
Telegram of master to the controller
FKB Comma ID Manual tare or ID Manual tare ID1 ID 2

PLS-DIn nds FKB analog or FKB
1-16 analog
(2 (2 (2
bytes) bytes) bytes) (4 bytes) (2 bytes) (4 bytes) (2 bytes) (2
bytes)
FKB The Mirror-ID Gross Gross Value Value

PLS- status on = ID 1 on the scale The scale ID 1 ID 2
DOut the scale displayed displayed rounded
1-16 displayed in the display
format
(2 (2 (2
Byte) (2 bytes) bytes) (4 bytes) (4 bytes) (2 bytes) bytes)
Remarks:
You can make the controller enter the desired values into the reply telegram by
adding identifiers in the telegram of the master to the controller. The order of
values corresponds to the order of the identifiers. The identifiers may come from
all data segments, which enables you to read back the predetermination values.
If an identifier is identified as incorrect, its value in the reply will be set to zero.
The identifiers should not be changed in regular user data operation because this
would make it impossible to unambiguously assign the ID to the value at the
switch-over point.
Example 3: Data transmission with text blocks and without variable user-defined
identifiers (ID).
Parameter settings:

© Schenck Process
Text block 4-byte text block (not with DISOMAT Satus)
The text block is always set in front of the other data.
Telegram of master to the controller
Text header Text-user data FKB PLS-DIn Commands ID Manual tare or ID Manual tare
FKB analog or FKB
analog
(2
4 bytes 4 bytes (2 bytes) (2 bytes) bytes) (4 bytes) (2 bytes) (4 bytes)
Text header Text-user data FKB PLS- The status on Mirror-ID Gross Gross
Dout the scale in this case: on the scale The scale
displayed ZERO displayed displayed in the
display format
4 Byte rounded
4 bytes (2 bytes) (2 bytes) (2 bytes) (4 bytes) 4 bytes)
Text transmission via Profibus DP

All explanations in this chapter relate to the 4-byte text block and the same applies
correspondingly to the 20-byte text block. It only differs in the number of text-user
data that can be transmitted per cycle.
Text header Text-user data
AK Text-ID AKT MAX As much as 4- or 20-byte text-user data

(unused bytes should filled with zero)
Figure 3 The basic structure of the text block
The meaning of the byte in the text header

AK The first byte contains the order or reply identifier
Refer to the table further below for details.
Text-ID The second byte contains the text identifier (1-5) that specifies the text to be transmitted in greater
detail.
Refer to the Text-ID table for details.
AKT AKT specifies the current index value in texts that cannot be transmitted in one cycle.
If you select short (4-byte) text, this gives you the sequence 0,4,8,... for the index value.
If you select long (20-byte) text, this gives you the sequence 0,20,40,... for the Index Value.
Important: AKT has to accept the value of MAX at the end of the text transmission for least one
telegram cycle. This indicates to the controller that all text segments were transmitted and that the
text should now be accepted in the controller.
MAX The byte always contains the total length of the text user data in bytes.

© Schenck Process
The following text types are implemented:
Meaning Text-ID
String text 1 1
String text 2 2
String text 3 3
String text 4 4
String text 5 5
You can find the meaning of the order identifier in Table 1 for the order telegram
(master —> controller).
Order identifier Meaning
0 No order
1 Read the text from the scale
2 Write the text for the scale
Tab. 1 Order identifiers (AK) master station -> DISOMAT
You can find the meaning of the reply identifier in Table 2 for the reply telegram
(controller —> master).
Reply identifier Meaning
0 No order
2 Text fragment successfully transmitted
7 Order cannot be executed
Tab. 2 Reply identifiers (AK) DISOMAT -> master station
The master has to repeat an order until he has received the appropriate reply.
The master recognises the reply to an order placed by evaluating the reply
identifier
If text information is not needed in cyclical operation, the order identifier has to be
set to “no order”.

© Schenck Process
Read text (controller text transmitted to the master)

If there is a new text, the text is requested piecewise, but no more than 4 or 20
bytes per cycle. While the maximum index always gives the length of the text,
n the current index has the sequence 0, 4, 8 with the 4-byte text block to the
maximum index.
n and the current index has the sequence 0, 20, 40 in the 20-byte text block to the
maximum index.
Example:
Reading a text 21 bytes long with the 4-byte text block
(“This is an example”)
xx any characters
01 01 00 12 xx xx xx xx 1. request
02 01 00 12 54 68 69 73 1. reply (This)
02 01 04 12 20 69 73 20 2. reply ( is )
02 01 08 12 61 6E 20 65 3. reply (an e)
01 01 0C 12 xx xx xx xx 4. request
02 01 0C 12 78 61 6D 70 4. reply (xamp)
02 01 10 12 6C 65 00 00 5. reply (le)
01 01 12 12 xx xx xx xx end telegram
(The master has read the entire text)

© Schenck Process
Write a text (transmit the text of the master to the

controller)
The text is transmitted piecewise, no more than 4 or 20 bytes per cycle. While the
maximum index always give the length of the text,
n the current index has the sequence 0, 4, 8 in the 4-byte text block to the
maximum index.
n and the current index has the sequence 0, 20, 40 in the 20-byte text block to the
maximum index.
Example:
Specifying a text 21 bytes long with the 4-byte text block
(“This is an example”)
(The replies of the controller are not described)

02 01 00 12 54 68 69 73 (This)
02 01 04 12 20 69 73 20 ( is )
02 01 08 12 61 6E 20 65 (an e)
02 01 0C 12 78 61 6D 70 (xamp)
02 01 10 12 6C 65 00 00 (le)
01 01 12 12 xx xx xx xx end telegram
(The application
accepts the text)
The end telegram where the current index is set equal to the maximum index
always has to transmit regardless of the length of the text. It is only transmitted to
the scale after transmitting this packet..

© Schenck Process
5.3.3 Data from the process control system

DP write register (control information and analog predetermination values)
Description without a text block
byte Code Contents
0-1 0x1002 Function block PLS-DIn 1-16

PLS-DIn 9-16 is transmitted first followed by PLS-DIn 1-8
2-3 0x1000 1 byte unused

Command number in LOW-byte (1 byte)
Refer to the list of available data
4-5 ID1 analog specification (refer to the list)
6-9 Value for the ID1 analog specification
10 - 11 ID2 analog specification (refer to the list)
12 - 15 Value for the ID2 analog specification
16 - 17 ID1
18 - 19 ID2
20 - 21 ID3
22 - 23 ID4
24 - 25 ID5
26 - 27 ID6
28 - 29 ID7
30 - 31 ID8
The commands on the scale displayed

Please key in the coding of the command into the command byte. This action is
immediately triggered after correct reception. When giving be ‘Clear Tare’
command, please remember that the manual tare value is set to ZERO at the
same time as the command.
The identifiers for PLS-DIn 1-16 and the commands are not transmitted. They are
only used to refer to the list of the “Available Data”.
Refer to the chapter on Available Data Settings for valid setpoints
The procedure for specifying the values via fieldbus

The values addressed above can be specified by one of the following sources:
n Data processing procedure
n Local operating panel (menu tree or function key(s))
n Fieldbus

© Schenck Process
1. Setpoint and material number:

The fieldbus is always the sole determinant source when the ID in the telegram
assigned to the value is transmitted from the master to the controller. Any
values from other sources are then overwritten in the next fieldbus cycle.
If you want to use the fieldbus to change the value, set the desired value in the
fieldbus protocol and then transmit it to the controller together with its ID. To
allow other sources to specify, the IDs for setpoint or material number have to
be set to zero or the ID on of a different value in the fieldbus telegram. That
means that the specification IDs determine which source has priority.
2. Other values:
The controller accepts the manual tare of the scale displayed and the data
PLS-AIN-1 - PLS-AIN-4 after changing the corresponding values.
The controller requires at least 100 ms to accept. It can be accepted by waiting

this period or also by reading back current values. Reading back is done by setting
the corresponding read-ID.

© Schenck Process
5.3.4 Data on the process control system

DP read register (status information and readings)
Description without a text block
byte Identifier Contents
0-1 0x300C Function block PLS-Dout 1-16
2-3 0x3000 The scale status on the scale displayed
4-5 0x3002 Request (ID1 mirrored)
6-9 0x4000 Gross weight on the scale displayed

unrounded in kg
10 - 13 0x4010 Gross weight on the scale displayed

rounded off in the display format
14 - 17 See list for ID Value 1
18-21 See list for ID Value 2
Word = 16-bit data word

Long = data double word
Note:
When range 1 and range 2 are set, the scale is in range 3.
The bold print identifiers are not transmitted and they are only used to refer to the
list of the “Available Data”.
Refer to the chapter on Available Data for the Controller Data for the reading ID list

© Schenck Process
5.3.5 Profibus-DP interface parameters
q Internal address ? station address for the Profibus (0-126)
q Number of IDs identifiers of all values that should be requested for

specific customers (0-8).
q Text block This parameter defines whether a fixed text block is

put ahead of the normal user data and, if this is the
case, its size (off, 4 bytes, 20 bytes).
q Data format The format for all floating point numbers

(IEEE, SIEMENS-KG)

0s = no monitoring
1-300 s = value range
The number of IDs, text block and internal address parameters are only used after
reset and the old (i.e., effective) values are showed until then.
Note:
If monitoring is activated, the controller shows both timeouts and faulty identifiers
(ID) as communication malfunctions.

© Schenck Process
5.3.6 Planning aids (drawings, rules)

You can load the appropriate Profibus planning file (.gsd) from the address below:
http://support.schenckprocess.com- Steuerungen\Profibus.
You can find the controller in the hardware configurator of an S7 under:

Profibus-DP/weitere Feldgeräte/Regler/DISOMAT xxxx
The names of the GSD modules are structured according to the following scheme:
Text block, number IDs
For example:
· No Text, 0 ID
· No Text, 4 ID
· Short Text, 2 ID
· Long Text, 4 ID usw.

© Schenck Process

© Schenck Process
5.4 DeviceNet Protocol

Terminology
Logical hierarchy
The process control system is the bus master and the controllers are treated as
individual slaves.
from the slave. The bus master cyclically acquires a process image of the
controller and cyclically transmits a command telegram to the controller
Data Format
The setpoints and readings are transmitted in the IEEE float format (IEEE 754, 32
bits) or the Siemens float format.
They are transmitted according to standard procedure starting with the MSB.
You can use the swapping parameter to change the order all bytes.
Timeout can guarantee transmission between the controller and control system in
the controller so that the controller expects a telegram from the control system at
particular intervals. You can use parameters to set both the interval and the type of
reaction from the controller to no telegram on the controller. The setting TIMEOUT
= 0 means that the data flow between the controller and control system is not
monitored by the controller.
Routines
Any routines important for specifying data are described in the specific section.
highest address that can be set is marked in the following text as MAXSLAVE.
You can set the address by dialog on the controller. MAXSLAVE is 63.

© Schenck Process
5.4.1 Structure of user data

The data content is identical to the Profibus-DP coupling (refer to the chapter on
Data Segments and User Data).
5.4.2 Parameterising DeviceNet interface parameters

q Internal address station address for DeviceNet (0-63)
0s = no monitoring
1-300 s = value range
q Baud rate on the DeviceNet (125 kB, 250 kB and 500 kB)
q User data “no text/4 ID”, “text/2 ID”, establishing the
composition of the data to be requested via
DeviceNet.
4 customised data can be requested WITHOUT text
and 2 customised data can be requested WITH text.
q Data format Format for all floating point numbers

(IEEE, SIEMENS-KG)
q Swapping order of bytes for the floating point numbers and
words on the bus
(BIG Endian, BYTE Swap, WORT Swap,
LITTLE Endian)
The setting LITTLE Endian make sense in
connection with ROCKWELL control systems.
Note:
When monitoring is activated, both timeouts and faulty identifiers (ID) are shown
as communication malfunctions.

© Schenck Process
5.5 Available data
5.5.1 Setpoint
WRITE fieldbus
Identifiers Identifiers Data Type Meaning Added Information DISOMAT Satus DISOMAT Opus DISOMAT Tersus
Profibus Modbus
DeviceNet Modbus/TCP
(hex) (dec) (hex) (dec)
Commands
1000 4096 10 16 Num. DW Command number X X X
The meaning of the command numbers

DW 1 Taring Scale displayed Scale displayed Scale displayed
DW 2 Clear tare Scale displayed Scale displayed Scale displayed
DW 3 Zero setting Scale displayed Scale displayed Scale displayed
DW 4 Taring Scale 1 Scale 1 Scale 1
DW 5 Clear tare Scale 1 Scale 1 Scale 1
DW 6 Zero setting Scale 1 Scale 1 Scale 1
DW 7 Taring Scale 2
DW 8 Clear tare Scale 2
DW 9 Zero setting Scale 2
DW 10 Taring Twin-unit
DW 11 Clear tare Twin-unit

© Schenck Process
Profibus Modbus
DW 12 Zero setting Twin-unit
DW 13 Taring
DW 14 Clear tare
DW 15 Zero setting
DW 16 Taring
DW 17 Clear tare
DW 18 Zero setting
DW 19 Taring
DW 20 Clear tare
DW 21 Zero setting
DW 22 Taring
DW 23 Clear tare
DW 24 Zero setting
DW 25 Taring
DW 26 Clear tare
DW 27 Zero setting
DW 71 Connect scale Scale 1
DW 72 Connect scale Scale 2
DW 73 Connect scale Twin-unit
DW 74 Connect scale
DW 75 Connect scale

© Schenck Process
Profibus Modbus
DW 76 Connect scale
DW 77 Connect scale
DW 78 Connect scale
DW 80 Register Scale displayed Scale displayed Scale displayed
DW 81 Register Scale 1
DW 82 Register Scale 2
DW 83 Register Twin-unit
DW 84 Register
DW 85 Register
DW 86 Register
DW 87 Register
DW 88 Register
DW 128 Acknowledging the highest X X X
pending fault
1002 4098 20 32 DW Function blocks Refer to the loaded function X X
(16 bits) block linkage
PLS-DIn-xx for the meaning of the bits
Predetermination values (floating point values, IEEE)
2000 8192 100 256 DDW Manual tare Scale displayed Scale displayed Scale displayed
2004 8196 102 258 DDW unused
2008 8200 104 260 DDW unused
200C 8204 106 262 DDW PLS -AIn-1 X X X
2010 8208 108 264 DDW PLS -AIn-2 X X X

© Schenck Process
Profibus Modbus
2014 8212 10A 266 DDW PLS -AIn-3 X X X
2018 8216 10C 268 DDW PLS -AIn-4 X X X
200C 8220 10E 270 DDW Material number 1 X X X
2020 8224 110 272 DDW Setpoint 1 in kg X X X
2024 8228 112 274 DDW Material number 2 X
2028 8232 114 276 DDW Setpoint 2 in kg X
Texts/string (ASCI
600 1536 String 1 A maximum of 25 A maximum of 25 A maximum of 25
characters characters characters
Predetermination values (integers, ULONG)
8000 32768 800 2048 DDW Date and coding as per Profibus specifications X X X
8004 32772 802 2050 DDW Time and coding as per Profibus specifications X X X
8008 32776 804 2052 DDW Material number 1 X X X

© Schenck Process
5.5.2 Controller data
READ fieldbus
Profibus Modbus
Status information
3000 12288 1300 4864 DW Status (as data word, 16 its) Scale displayed Scale displayed Scale displayed
1300 4864 The scale is in the underrange X X X
1301 4865 The scale is in the overrange X X X
1302 4866 Manual or fixed tare is set X X X
1303 4867 Scale is exactly zero X X X
1304 4868 X X X
1305 4869 The weight is not valid X X X
1306 4870 Scale tared X X X
1307 4871 Scale in no-motion X X X
1308 4872 Measuring is being initialised: X X X
No weights are being established
1309 4873 X X X
130A 4874 The scale is in range 1 X X X
130B 4875 The scale is in range 2 X X X
130C 4876 The scale is in the zero setting range X X X
130D 4877 X X X
130E 4878 This is a multi-interval scale X X X
130F 4879 This is a multi-range scale X X X

© Schenck Process
Profibus Modbus
3002 12290 1310 4880 Num. DW Mirror-ID (first requested ID) X X X
3004 12292 1320 4896 Num. DW The fault class of the highest pending fault X X X
0:no result
1:message
2:warning
3:alarm
4:fault
3006 12294 1330 4912 Num. DW The fault number of the highest pending fault X X X
3008 12296 1340 4928 Num. DW The LE group of the highest pending fault X X X
300A 12298 1350 4944 Num. DW Fault ident X X X
300C 12300 1360 4960 DW Binary function blocks (16 bits) PLS-DOut-xx X X X
Refer to the loaded function block linkage for the
meaning of the bits
300E 12302 1370 4976 DW Status (refer to status ID 1300 for details) Scale 1 Scale 1 Scale 1
3010 12304 1380 4992 DW Status (refer to status ID 1300 for details) Scale 2
3012 12306 1390 5008 DW Status (refer to status ID 1300 for details) Twin-unit
3014 12308 13A0 5024 DW Status (as a double word, 16 bits) Disobox 1 channels
1-2
13A0 5024 Initialising channel 1 X
13A1 5025 X
13A2 5026 X
13A3 5027 Measuring signal to large channel 1 X
13A4 5028 The load cell cable is broken to channel 1 X
13A5 5029 X
13A6 5030 X

© Schenck Process
Profibus Modbus
13A7 5031 X
13A8 5032 Initialising channel 2 X
13A9 5033 X
13AA 5034 X
13AB 5035 Measuring signal to large channel 2 X
13AC 5036 The load cell cable is broken to channel 2 X
13AD 5037 X
13AE 5038 X
13AF 5039 X
3016 12310 13B0 5040 DW Status (refer to status ID 13A0 for details) Disobox 1 channels
3-4
3018 12312 13C0 5056 DW Status (refer to status ID 13A0 for details) Disobox 1 channels
5-6
301A 12314 13D0 5072 DW Status (refer to status ID 13A0 for details) Disobox 1 channels
7-8
301C 12316 13E0 5088 DW Status (refer to status ID 13A0 for details) Disobox 2 channels
1-2
301E 12318 13F0 5104 DW Status (refer to status ID 13A0 for details) Disobox 2 channels
3-4
3020 12320 1400 5120 DW Status (refer to status ID 13A0 for details) Disobox 2 channels
5-6
3022 12322 1410 5136 DW Status (refer to status ID 13A0 for details) Disobox 2 channels
7-8
3024 12324 1420 5152 DW Dimension (0:kg 1:g 2:t 3:lb) X X X
High-Word/Low-Byte

© Schenck Process
Profibus Modbus
3026 12326 1430 5168 DW Status (refer to status ID 1300 for details)
3028 12328 1440 5184 DW Status (refer to status ID 1300 for details)
302A 12330 1450 5200 DW Status (refer to status ID 1300 for details)
302C 12332 1460 5216 DW Status (refer to status ID 1300 for details)
302E 12334 1470 5232 DW Status (refer to status ID 1300 for details)
3030 12336 1480 5248 DW Physical digital inputs X X X
3032 12338 1490 5264 DW Physical digital outputs X X X
3034 12340 14A0 5280 DW Feed status of feed operation 1 X X X
3036 12342 14B0 5296 DW Feed status of feed operation 2 X
Texts/string (ASCII)
Readings (floating point values, IEEE)
4000 16384 700 1792 DDW GROSS weight unrounded in kg Scale displayed Scale displayed Scale displayed
4004 16388 702 1794 DDW TARE weight unrounded in kg Scale displayed Scale displayed Scale displayed

© Schenck Process
Profibus Modbus
4008 16392 704 1796 DDW dW/dt unrounded in kg Scale displayed Scale displayed Scale displayed
400C 16396 706 1798 DDW NET weight unrounded in kg Scale displayed Scale displayed Scale displayed
4010 16400 708 1800 DDW GROSS weight Rounded in the display Scale displayed Scale displayed Scale displayed
format
4014 16404 70A 1802 DDW TARE weight Rounded in the display Scale displayed Scale displayed Scale displayed
format
4018 16408 70C 1804 DDW dW/dt Rounded in the display Scale displayed Scale displayed Scale displayed
format
401C 16412 70E 1806 DDW NET weight Rounded in the display Scale displayed Scale displayed Scale displayed
format
4020 16416 710 1808 DDW Balance (total) 100000 rest (kg) X X X
4024 16420 712 1810 DDW Balance (total) 100000 multiple (kg) X X X
4028 16424 714 1812 DDW Balance (current sort) 100000 rest (kg) X X X
402C 16428 716 1814 DDW Balance (current sort) 100000 multiple (kg) X X X
4030 16432 718 1816 DDW PLS -AOut-1 X X X
4034 16436 71A 1818 DDW PLS -AOut-2 X X X
4038 16440 71C 1820 DDW PLS -AOut-3 X X X
403C 16444 71E 1822 DDW PLS -AOut-4 X X X
4040 16448 720 1824 DDW Registered tare rounded in the display format X X X
4044 16452 722 1826 DDW Registered net rounded in the display format X X X
4048 16456 724 1828 DDW Registered consecutive number (integer data format) X X X
404C 16460 726 1830 DDW Registered consecutive number (float data format) X X X
4050 16464 728 1832 DDW Material number Feed operation 1 X X X

© Schenck Process
Profibus Modbus
4054 16468 72A 1834 DDW Setpoint in kg Feed operation 1 X X X
4058 16472 72C 1836 DDW Material number Feed operation 2 X
405C 16476 72E 1838 DDW Setpoint in kg Feed operation 2 X
4060 16480 730 1840 DDW GROSS weight unrounded in kg Scale 1 Scale 1 Scale 1
4064 16484 732 1842 DDW TARE weight unrounded in kg Scale 1 Scale 1 Scale 1
4068 16488 734 1844 DDW dG/dt unrounded in kg Scale 1 Scale 1 Scale 1
406C 16492 736 1846 DDW NET weight unrounded in kg Scale 1 Scale 1 Scale 1
4070 16496 738 1848 DDW GROSS weight unrounded in kg Scale 2
4074 16500 73A 1850 DDW TARE weight unrounded in kg Scale 2
4078 16504 73C 1852 DDW dG/dt unrounded in kg Scale 2
407C 16508 73E 1854 DDW NET weight unrounded in kg Scale 2
4080 16512 740 1856 DDW GROSS weight unrounded in kg Twin-unit
4084 16516 742 1858 DDW TARE weight unrounded in kg Twin-unit
4088 16520 744 1860 DDW dG/dt unrounded in kg Twin-unit
408C 16524 746 1862 DDW NET weight unrounded in kg Twin-unit
4090 16528 748 1864 DDW GROSS weight unrounded in kg Disobox1-Channel 1
4094 16532 74A 1866 DDW GROSS weight unrounded in kg Disobox1-Channel 2
4098 16536 74C 1868 DDW GROSS weight unrounded in kg Disobox1-Channel 3
409C 16540 74E 1870 DDW GROSS weight unrounded in kg Disobox1-Channel 4
40A0 16544 750 1872 DDW GROSS weight unrounded in kg Disobox1-Channel 5

© Schenck Process
Profibus Modbus
40AC 16556 756 1878 DDW GROSS weight unrounded in kg Disobox1-Channel 8
40B0 16560 758 1880 DDW GROSS weight Rounded in the display Scale 1 Scale 1 Scale 1
format
40B4 16564 75A 1882 DDW TARE weight Rounded in the display Scale 1 Scale 1 Scale 1
format
40B8 16568 75C 1884 DDW dG/dt Rounded in the display Scale 1 Scale 1 Scale 1
format
40BC 16572 75E 1886 DDW NET weight Rounded in the display Scale 1 Scale 1 Scale 1
format
40C0 16576 760 1888 DDW GROSS weight Rounded in the display Scale 2
format
40C4 16580 762 1890 DDW TARE weight Rounded in the display Scale 2
format
40C8 16584 764 1892 DDW dG/dt Rounded in the display Scale 2
format
40CC 16588 766 1894 DDW NET weight Rounded in the display Scale 2
format
40D0 16592 768 1896 DDW GROSS weight Rounded in the display Twin-unit
format
40D4 16596 76A 1898 DDW TARE weight Rounded in the display Twin-unit
format
40D8 16600 76C 1900 DDW dG/dt Rounded in the display Twin-unit
format
40DC 16604 76E 1902 DDW NET weight Rounded in the display Twin-unit
format
40E0 16608 770 1904 DDW GROSS weight unrounded in kg Disobox 2 channel 1

© Schenck Process
Profibus Modbus
40EC 16620 776 1910 DDW GROSS weight unrounded in kg Disobox 2 channel 4
40F0 16624 778 1912 DDW GROSS weight unrounded in kg Disobox 2 channel 5
40F4 16628 77A 1914 DDW GROSS weight unrounded in kg Disobox 2 channel 6
40F8 16632 77C 1916 DDW GROSS weight unrounded in kg Disobox 2 channel 7
40FC 16636 77E 1918 DDW GROSS weight unrounded in kg Disobox 2 channel 8
4100 16640 780 1920 DDW GROSS weight unrounded in kg
4104 16644 782 1922 DDW TARE weight unrounded in kg
4108 16648 784 1924 DDW dG/dt unrounded in kg
410C 16652 786 1926 DDW NET weight unrounded in kg
4114 16660 78A 1930 DDW TARE weight unrounded in kg
4118 16664 78C 1932 DDW dG/dt unrounded in kg
411C 16668 78E 1934 DDW NET weight unrounded in kg
4124 16676 792 1938 DDW TARE weight unrounded in kg
4128 16680 794 1940 DDW dG/dt unrounded in kg
412C 16684 796 1942 DDW NET weight unrounded in kg
4134 16692 79A 1946 DDW TARE weight unrounded in kg

© Schenck Process
Profibus Modbus
4138 16696 79C 1948 DDW dG/dt unrounded in kg
413C 16700 79E 1950 DDW NET weight unrounded in kg
4140 16704 7A0 1952 DDW GROSS weight unrounded in kg
4144 16708 7A2 1954 DDW TARE weight unrounded in kg
4148 16712 7A4 1956 DDW dG/dt unrounded in kg
414C 16716 7A6 1958 DDW NET weight unrounded in kg
4150 16720 7A8 1960 DDW GROSS weight Rounded in the display
format
4154 16724 7AA 1962 DDW TARE weight Rounded in the display
format
4158 16728 7AC 1964 DDW dG/dt Rounded in the display
format
415C 16732 7AE 1966 DDW NET weight Rounded in the display
format
4160 16736 7B0 1968 DDW GROSS weight Rounded in the display
format
4164 16740 7B2 1970 DDW TARE weight Rounded in the display
format
4168 16744 7B4 1972 DDW dG/dt Rounded in the display
format
416C 16748 7B6 1974 DDW NET weight Rounded in the display
format
4170 16752 7B8 1976 DDW GROSS weight Rounded in the display
format
4174 16756 7BA 1978 DDW TARE weight Rounded in the display
format

© Schenck Process
Profibus Modbus
4178 16760 7BC 1980 DDW dG/dt Rounded in the display
format
417C 16764 7BE 1982 DDW NET weight Rounded in the display
format
4180 16768 7C0 1984 DDW GROSS weight Rounded in the display
format
4184 16772 7C2 1986 DDW TARE weight Rounded in the display
format
4188 16776 7C4 1988 DDW dG/dt Rounded in the display
format
418C 16780 7C6 1990 DDW NET weight Rounded in the display
format
4190 16784 7C8 1992 DDW GROSS weight Rounded in the display
format
4194 16788 7CA 1994 DDW TARE weight Rounded in the display
format
4198 16792 7CC 1996 DDW dG/dt Rounded in the display
format
419C 16796 7CE 1998 DDW NET weight Rounded in the display
format
41A0 16800 7D0 2000 DDW dW/dt kg / 100 ms
41A4 16804 7D2 2002 DDW dW/dt kg / 100 ms
41A8 16808 7D4 2004 DDW dG/dt kg / 100 ms
41AC 16812 7D6 2006 DDW dW/dt kg / 100 ms
41B0 16816 7D8 2008 DDW dW/dt kg / 100 ms

© Schenck Process
Profibus Modbus
41B4 16820 7DA 2010 DDW dW/dt kg / 100 ms
41B8 16824 7DC 2012 DDW dW/dt kg / 100 ms
41BC 16828 7DE 2014 DDW dW/dt kg / 100 ms
41C0 16832 7E0 2016 DDW Current actual value Feed operation 1 X X X
41C4 16836 7E2 2018 DDW Current residual value Feed operation 1 X X X
41C8 16840 7E4 2020 DDW unused
41CC 16844 7E6 2022 DDW unused
41D0 16848 7E8 2024 DDW Current actual value Feed operation 2 X
41D4 16852 7EA 2026 DDW Current residual value Feed operation 2 X
41D8 16856 7EC 2028 DDW unused
41DC 16860 7EE 2030 DDW unused
Readings (integers, ULONG)
7000 28672 900 2304 DDW The current date X X X
Coding according to the Profibus specifications
7004 28676 902 2306 DDW The current time X X X
Coding according to the Profibus specifications
7008 28680 904 2308 DDW Registration date X X X
700C 28684 906 2310 DDW Registration time X X X
7010 28688 908 2312 DDW Consecutive registration number X X X
7014 28692 90A 2314 DDW Material number feed operation 1 X X

© Schenck Process

© Schenck Process
5.5.3 Date/time format
DISOMAT ® B plus, Opus, DISOBOX, Datenkommunikation BV -H2316DE/0715 103

Schenck Process

© Schenck Process

BVH2359gb - Komunikace

Uploaded by

Copyright:

Available Formats

BVH2359gb - Komunikace

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

BVH2359gb - Komunikace

Uploaded by

Copyright:

Available Formats

DISOMAT®Satus , DISOMAT®Opus,

Free 24 h Customer Service Hotline

24h Emergency-Hotline: +49 172 – 650 17 00 Transport Automation and

+49 171 – 225 11 95 Heavy Industry, Light Industry

Note: Translation of the original instructions

5 Coupling for SPS and PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

DISOMAT Opus, Satus, Tersus, Data Communication BV-H2359GB/0722 I

II BV-H2359GB/0722 DISOMAT Opus, Satus, Tersus, Data Communication

1 Something about this manual

What does this describe?

A table of supplementary manuals

DISOMAT® Opus System Manual BV-H2310GB

DISOMAT® Opus Operating Manual BV-H2313GB

DISOMAT® Satus System Manual BV-H2331GB

DISOMAT® Tersus System Manual BV-H2334GB

DISOMAT® Tersus Operating Manual BV-H2335GB

DISOMAT Opus, Satus, Tersus, Data Communication BV-H2359GB/0722 1

- Reserved for Notes -

2 BV-H2359GB/0722 DISOMAT Opus, Satus, Tersus, Data Communication

General hazards if safety instructions are not obeyed

DISOMAT Opus, Satus, Tersus, Data Communication BV-H2359GB/0722 3

Labelling residual hazards

Safety notes for the user company

2.1 Information for operators of

Requirements made of data processing connections/query for recording readings

4 BV-H2359GB/0722 DISOMAT Opus, Satus, Tersus, Data Communication

· The legal-for-trade reading has to be queried as per the instructions in

· The commercial voucher has to have the following note:

3. The duration of legal-for-trade data storage.

DISOMAT Opus, Satus, Tersus, Data Communication BV-H2359GB/0722 5

- Reserved for Notes -

6 BV-H2359GB/0722 DISOMAT Opus, Satus, Tersus, Data Communication

Procedures are rules agreed for establishing communication as well as formatting

Message: Synchronisation Data telegram Data storage

DISOMAT Opus, Satus, Tersus, Data Communication BV-H2359GB/0722 7

3.1 List of procedures

Couplings for computers, PCs

q SCHENCK Poll Procedure; refer to Chapter 4.1.2

q SIEMENS 3964R; refer to Chapter 4.1.3

q ASCII-S5; refer to Chapter 4.1.4

q ASCII-Modbus; refer to Chapter 4.1.5

q Coupling for SPS and PLC

3.2 The interface parameter of DISOMAT

8 BV-H2359GB/0722 DISOMAT Opus, Satus, Tersus, Data Communication

4.1.1 SCHENCK Standard Protocol (DDP 8672)

Nachricht: Synchronisation Daten-Telegramm Datensicherung

<ENQ> <STX> ... <ETX> <BCC>

DISOMAT Opus, Satus, Tersus, Data Communication BV-H2359GB/0722 9

Behaviour Upon Errors In Data Transmission

Synchronization Monitoring Times, Repeats:

Response monitoring time ta 5 seconds

Enquiry monitoring time te 2 seconds

Max. number of enquiry repeats: 3

Max. number of data repeats: 3

Data Protection, Block Check Character Generation

Example: Block check character formation for AB34 data.

(Longitudinal: Always even and BCC parity same as character parity)

10 BV-H2359GB/0722 DISOMAT Opus, Satus, Tersus, Data Communication

1) EDP sends command for weigh data transmission to DISOMAT (01#TG#).