Schenk - BVH2220GB (Fieldbus)

INTECONT® PLUS
Fieldbus Description
we make processes work BV-H2220GB

Contacts, Copyright
Sales: Tel.: +49 (0) 61 51 32 - 10 28

eMail: sales.process@schenck.net
Service: 24h Emergency hotline: +49 (0) 172 - 650 17 00

+49 (0) 171 - 255 11 95 (belt weighers, weighfeeders)
eMail: service.process@ schenck.net
Business Segments and Services:
Heavy Industry
Service Tel.: +49 (0) 61 51 32 - 26 23
Service Fax: +49 (0) 61 51 32 - 32 70
eMail: bvh.process@schenck.net
Light Industry
Service Tel.: +49 (0) 61 51 32 - 25 72
Service Fax: +49 (0) 61 51 32 - 20 72
eMail: bvl.process@schenck.net
Mining (Vibrating Machines)

Service Tel.: +49 (0) 61 51 32 - 35 25
Service Fax: +49 (0) 61 51 32 - 30 96
eMail: bvs.process@schenck.net
Transport & Logistics

Service Tel.: +49 (0) 61 51 32 - 24 48
Service Fax: +49 (0) 61 51 32 - 13 69
eMail: bvt.process@schenck.net
Components & Spares

Service Tel.: +49 (0) 61 51 32 - 17 58
Service Fax: +49 (0) 61 51 32 - 36 32
eMail: bvk.process@schenck.net
© Copyright 2005
SCHENCK PROCESS GmbH
Measuring and Process Systems
Landwehrstraße 55, D-64293 Darmstadt
http://www.schenck-process.com
All rights reserved. Any reproduction of manual, regardless of method, without prior permission by
SCHENCK PROCESS GmbH in writing, even by excerpt, is prohibited.
Subject to change without prior notice.
BV-H2220 GB , 0505 INTECONT PLUS, Fieldbus Description

© SCHENCK PROCESS GmbH, Darmstadt
Table of Contents
1 FIELDBUS DATA ....................................................................................................... 1
1.1 Validity Range ........................................................................................................ 1
1.2 Data Segments ....................................................................................................... 1
1.3 Units ........................................................................................................................ 1
1.4 Numeric Representation ....................................................................................... 2
1.5 User Data Construction......................................................................................... 3

1.5.1 FIXED Mode...................................................................................................... 3
1.5.1.1 FIXED Mode – Detailed Message Sample................................................. 5
1.5.2 General User Data Construction ....................................................................... 6
1.5.2.1 Message Construction................................................................................ 7
1.5.2.2 Parameter Transfer .................................................................................... 9
1.5.2.3 General User Data Construction – Detailed Samples.............................. 11
1.6 User Data Diagnosis ............................................................................................ 13
1.7 Lists of Cyclic Data.............................................................................................. 15

1.7.1 Explanations on Data Lists.............................................................................. 15
1.7.2 Commands ...................................................................................................... 16
1.7.3 Preset Values in Floating Point Format .......................................................... 18
1.7.4 Preset Values in Integer Format (Modbus) ..................................................... 19
1.7.5 Status Information ........................................................................................... 20
1.7.6 Measurement Values in Floating Point Format............................................... 28
1.7.7 Measurement Values in Integer Format (Modbus) ......................................... 31
1.7.8 Values in Long Integer Format....................................................................... 32
1.7.9 Events ............................................................................................................. 33
2 PROFIBUS DP ......................................................................................................... 34
2.1 Commissioning Guideline .................................................................................. 34
2.2 Profibus Module Functionality ........................................................................... 34
2.3 User Data Construction....................................................................................... 34
2.4 Settings on DP-Slave (INTECONT)..................................................................... 35
2.5 Settings on Profibus DP Master ......................................................................... 35
2.6 Diagnosis and Troubleshooting......................................................................... 36

2.6.1 Event Message“Data Link Host” S9 ................................................................ 36
2.6.2 LEDs on Profibus Module ............................................................................... 37
2.6.3 EasyServe Fieldbus View ............................................................................... 37
2.7 Profibus Module (VPB020V) ............................................................................... 37
2.8 For Further Reading ............................................................................................ 38
3 DEVICENET ............................................................................................................. 39
3.1 Commissioning Guideline .................................................................................. 39
INTECONT PLUS, Fieldbus Description BV-H2220 GB , 0505 I

©SCHENCK PROCESS GmbH , Darmstadt
Table of Contents
3.2 DeviceNet Module Functionality .........................................................................39
3.3 User Data Construction .......................................................................................39
3.4 Settings on DeviceNet Slave (INTECONT) .........................................................40
3.5 Settings on DeviceNet Master.............................................................................40
3.6 Diagnosis and Troubleshooting .........................................................................41

3.6.1 Event Message“Data Link Host” S9.................................................................41
3.6.2 EasyServe Fieldbus View ................................................................................41
3.7 DeviceNet Module (VCB020V) .............................................................................41
3.8 For Further Reading .............................................................................................42
4 MODBUS...................................................................................................................43
4.1 Commissioning Guideline ...................................................................................43
4.2 Modbus Module Functionality.............................................................................43
4.3 Data Format...........................................................................................................43
4.4 Function Codes (FC) ............................................................................................44
4.5 Transmission Protection .....................................................................................44
4.6 Error Codes...........................................................................................................44
4.7 Station Addresses ................................................................................................44
4.8 User Data ...............................................................................................................45

4.8.1 Process Values ................................................................................................45
4.8.2 Parameters ......................................................................................................45
4.9 Cyclic Data Exchange Via Modbus.....................................................................45
4.10 Sample Messages...............................................................................................46
4.11 Settings on Modbus Slave (INTECONT)...........................................................46
4.12 Settings on Modbus Master ..............................................................................47
4.13 Diagnosis and Troubleshooting .......................................................................47

4.13.1 Event Message “Host Data Link” S9..............................................................47
4.13.2 EasyServe Fieldbus View ..............................................................................47
4.14 Serial Bus Module (VSS021V) ...........................................................................48
4.15 For Further Reading ...........................................................................................49
5 MODBUS-TCP/IP......................................................................................................50
5.1 Definitions .............................................................................................................50
5.2 Commissioning Guideline ...................................................................................51
II BV-H2220 GB , 0505 INTECONT PLUS, Fieldbus Description

Table of Contents
5.3 Ethernet Module Functions ................................................................................ 51
5.4 Configuring Ethernet Module ............................................................................. 53

5.4.1 MultiServerTools.EXE Program ...................................................................... 53
5.4.1.1 MultiServer Scanner ................................................................................. 54
5.4.1.2 MultiServer Loader ................................................................................... 54
5.4.1.3 MultiServer Mastersimulator..................................................................... 56
5.4.1.4 Setup ........................................................................................................ 57
5.4.2 Parameterizing INTECONT............................................................................. 57
5.4.3 Checking Station Addresses ........................................................................... 59
5.5 Fieldbus Mode...................................................................................................... 60

5.5.1 Station Addresses ........................................................................................... 60
5.5.2 Function Codes (FC)....................................................................................... 60
5.5.3 Transmission Protection.................................................................................. 60
5.5.4 Error Codes ..................................................................................................... 61
5.5.5 Data Formats................................................................................................... 61
5.5.6 Process Values ............................................................................................... 61
5.5.7 Parameters...................................................................................................... 61
5.5.8 Data Exchange Overview................................................................................ 62
5.5.9 Message Samples........................................................................................... 63
5.5.10 Settings on Modbus/TCP Master .................................................................. 63
5.5.11 Diagnosis and Troubleshooting .................................................................... 63
5.5.12 Event Message“Data Link Host” S9.............................................................. 64
5.5.13 EasyServe Fieldbus View ............................................................................. 64
5.5.14 Interface Configuration.................................................................................. 65
5.6 WEB SERVER Mode ............................................................................................ 67

5.6.1 WEB Server Files............................................................................................ 67
5.6.2 Start Page ....................................................................................................... 67
5.6.3 Actual Value Display ....................................................................................... 68
5.6.4 WEB Server Call Conventions ........................................................................ 69
5.6.5 Configuring WEB Page ................................................................................... 70
5.6.6 XML Data Representation............................................................................... 72
5.6.7 HTML Data Representation ............................................................................ 73
5.7 EtherNet Bus Module (VET020V)........................................................................ 73
5.8 For Further Reading ............................................................................................ 74
6 APPENDIX................................................................................................................ 75
6.1 ASCII Table with HTML Codes............................................................................ 75
INTECONT PLUS, Fieldbus Description BV-H2220 GB , 0505 III

Table of Contents
IV BV-H2220 GB , 0505 INTECONT PLUS, Fieldbus Description

Fieldbus Data
1 Fieldbus Data
Before putting into operation one of the protocols described below, always read
Chapter “Fieldbus Data“ and the protocol-specific items.
Decisive for the further procedure is the “User Data Construction” item. You can
select:
FIXED-1/2 mode or
General user data construction
If one of the FIXED modes suits you, you can skip the information on IDs and
parameters.
The FIXED modes shorten the breaking-in time and ease the use of the fieldbus
interface to a considerable extent. Simply read Chapters 1.1-1.4, and item FIXED
MODE; the “Diagnosis and Troubleshooting” item might be useful, too.
1.1 Validity Range

This item describes all data that can be transferred using the various fieldbus
protocols. The data basis is the same for all fieldbuses. Special features are detailed
at the protocol-specific items.
The “Fieldbus Data” chapter holds for the following protocols:

Protocol See:
Profibus DP Chapter 2
DeviceNet Chapter 3
Modbus Chapter 4
Modbus-TCP/IP Chapter 5
For description of protocol S5-RK512 (3964R), see manual FH458.
1.2 Data Segments

The INTECONT system distinguishes the following cyclic data:
Commands (bit or byte information)
Setpoints (floating point values)
Status information (bit or byte information)
Measurement values (floating point values)
Long (INT32) values (integer values)
1.3 Units
INTECONT uses two different unit systems:

SI units
NON-SI units
Changeover takes place using the “Units” parameter.
For the fieldbuses, this means:
Selection SI lets you transfer all unit values in "m, kg and sec"
Selection NON-SI transfers your values in "ft, lb and sec".
INTECONT PLUS, Fieldbus Description BV-H2220 GB , 0505 1

Fieldbus Data
1.4 Numeric Representation
Floating Point Values

INTECONT readies measurement values, setpoints and some parameters in the form
of floating point numbers in the IEEE-754 4-byte format. Depending on protocol and
parameter, these can be converted into another floating point format. For details, see
individual protocol descriptions.
Transmission always starts with MSB.
Example for transmission of value 150.5 in IEEE format (indicating the line sequence):
Byte 1: Byte 2: Byte 3: Byte 4:

Sign/Exponent Mantissa 1 Mantissa 2 Mantissa 3
0x43 0x16 0x80 0x00
Sample floating point numbers

Number IEEE format (HEX) Siemens-KG format (HEX)
1.0 3F800000 01400000
10.0 41200000 04500000
100.0 42C80000 07640000
1000.0 447A0000 0A7D0000
Data (double) words

Data words are standard transmitted using the Motorola format (high byte followed
by low byte).
Depending on protocol and parameter, another byte sequence can be set. For details,
see individual protocol descriptions.
Data type MSB LSB

Int 32 / LONG MSB LSB
Int 16 0 0 MSB LSB
Bit information
Bits are comprised to form words (Modbus, Modbus/TCP) or double words (Profibus,
DeviceNet). The line sequence is as follows:
Ex.: Command ID 0x0140 Comm4_HI Comm4_LO Comm5_HI Comm5_LO

Ex.: Status ID 0x02F0 Status2_HI Status2_LO Status3_HI Status3_LO
2 BV-H2220 GB , 0505 INTECONT PLUS, Fieldbus Description

Fieldbus Data
1.5 User Data Construction
As mentioned above, INTECONT readies two process images:

FIXED-1/2 mode or
General user data construction.
The Fixed modes let you transfer specified data in specified positions from host
system to INTECONT and vice versa.
The FIXED mode is not designed for parameter transfer and data configuration.
The advantage is that profound learning of the principle of data exchange using the
“General User Data Construction” is omitted. This principle enables any data
(including system parameters) to be transferred in any sequence, however, the price
for this flexibility is the exhaustive breaking-in concerning data extent and type of
processing.
The user data constructions of this item apply to the PROFIBUS and DeviceNet
protocols. The Modbus, or Modbus/TCP, protocol is used to transfer continuous data
ranges from Master to scale and vice versa (see protocol-specific items).
1.5.1 FIXED Mode
The data of FIXED-1 mode are optimised for continuous operation; those of FIXED-2
mode are provided for batching. In addition, the data are matched to the particular
scale type. The construction of the data packages is identical for the two modes (see
below). Every value has the size of one data double word (4 bytes). Values not used
are filled with zero. For detailed description of commands and status values, refer to
the lists of cyclic data given at the end of the Fieldbus Data chapter.
NOTE
In preset value 1 (commands 4 + 5) the release bit (in terms of a fieldbus
release) serving for interface monitoring must always be set statically. If this bit
is not set, the subsequent preset values are not evaluated and HOST
communication fault is set.
The table below includes all values transferred with the particular scale type:

Fieldbus Data

Fieldbus Data
1.5.1.1 FIXED Mode – Detailed Message Sample
INTECONT parameters (scale type: VLW)
Configuration FIXED-1
Floating point format IEEE format
Master->Slave Bytes (hex) Meaning (ID value, hex) Current value

Bytes 1-4 00 0C 00 00 Commands 4+5 (0140) Event acknowledged, release set
Bytes 5-8 00 00 00 00 Commands 6+7 (0160) No command active
Bytes 9-12 00 00 00 01 Commands 8+9 (0180) START keyboard mode set
Bytes 13-16 43 16 80 00 Setpoint (0250) 150.5 kg/hr
Bytes 17-20 42 C8 00 00 Batch setpoint (0252) 100 kg
Bytes 21-32 ZERO Standby
Slave->Master Bytes (hex) Meaning (ID value, hex) Current value

Bytes 1-4 01 02 00 00 Status 2+3 (02F0) Normal mode, no release
Bytes 5-8 00 02 00 04 Status 4+5 (0310) Filling system, fill level < Min
Bytes 9-12 13 18 00 00 Most significant error (0610) Event S9 ackn., Warning2
Bytes 13-16 42 C8 00 00 Feed rate actual value (0750) 100 kg/hr
Bytes 17-20 44 9A 40 00 Totalizing counter 1 (0752) 1234 kg
Bytes 21-24 43 AC 80 00 Bin level F (0760) 345 kg
Bytes 25-28 45 F6 90 00 Totalizing counter 2 (0754) 7890 kg
Bytes 29-32 42 C8 00 00 Effective setpoint (0766) 100 kg/hr

Fieldbus Data
1.5.2 General User Data Construction
Since there is no specific Weighing profile, data construction uses the existing
Variable Speed Drives profile.
In this profile, user data construction for the cyclic channel is called Parameter
Process Data Object (PPO).
The guideline determines the user data construction for drives a Master can use to
access the drive slaves by means of cyclic data exchange. User data construction in
cyclic data exchange comprises two ranges which can be transmitted in every
message:
• Process Data Range (PZD), i.e. control words and setpoints, or status
information and actual values
• Parameter Range (PKW) for read/write of parameter values, e.g. read-out of
information on parameter characteristics (MIN/MAX values, etc.).
The PPO type used to address the scale from Master can be configured at the time of
bus system commissioning. The PPO type is selected as a function of the scale task
in the automation environment and used to control the scale in the automation
environment, e.g. Start/Stop, Enter Setpoints. The parameter range enables the user
to freely access all scale parameters with the use of the bus system. Thus, further
information for scale visualization can be called up from a host system, e.g. a PC, with
no adverse effects on the efficiency of process data transmission.
All messages used in cyclic data transmission have the following basic construction:
Protocol frame Parameters (PKW) User data Protocol frame

(header) optional Process data (PDR) (trailer)
General message construction
PPO types
The following PPO types can be defined:
User data without parameter range, with three specified preset values and max. 6
additional read values selectable via ID
User data with parameter range, two preset values and four read values.
Parameter range (PKW)

The PKW message part (Parameter Code Value) can be used to monitor and/or
change any scale parameter. The requisite mechanisms of order/reponse IDs are
described at the Parameter Transfer item.
Process data range (PDR)

Using the process data, commands and preset values (Master to scale) or status
words and actual values ( scale to Master response) can be transmitted.
Transmitted process data are immediately effective.

Fieldbus Data
1.5.2.1 Message Construction

The figure below shows the basic construction of user data in the INTECONT system.
The first line shows the message from bus master to scale; the second, the scale
reponse.
User data construction of messages
The maximum size of a user data package is 32 bytes, the construction is invariable,
data contents (IDs and values) are variable.
Note
When using the DeviceNet protocol for transmission, always use 32 bytes as
produced and consumed connection size.
Sample
Data transmission without parameters with 3 preset values, 6 variable
user-defined identifications (IDs) – representation HEX
Note
The preset IDs from Master to scale must originate from the Command or Preset
value ranges. It is possible to preset multiple setpoints (feed rate and batch
setpoint) or multiple commands with different IDs in one and the same cycle.
If one ID is zero, respective value is not evaluated..
If all bytes are set to zero in the presetting message (bus Master to INTECONT),
fieldbus communication fault is set on INTECONT. INTECONT interprets this state
as failure of the bus Master's host CPU whilst the communication processor in
Master is active. The INTECONT timeout monitoring cannot compensate this state
since formally valid data packages are transferred still. At least one preset ID must
have a valid value unequal to zero.

Fieldbus Data
Control and status information is comprised in 4-byte packages. The IDs assigned
to blocks are highlighted in data description. Only these IDs may be used here. If
a different ID is used, data are rejected and an error message is output.
In the response message, status and actual value are identified by their positions
in message. The fixed status has ID 0x2F0; the actual value, ID 0x750.
Through addition of (read) IDs in Master --> scale message, you can cause the
scale to enter the desired values into the response message. Value sequence
corresponds to the ID sequence. If IDs of the Preset value or Command ranges
are entered, the value preset last is reread.
If an ID is identified as wrong, corresponding value in the response is set to zero.
Sample Data transmission with additional parameter block
The (grey) parameter block always precedes the residual data.
Master --> scale message
PKE IND PWE1 PWE2 ID ID Ordering list

Preset Preset value 1 Preset Preset value 2 (read IDs)
value 1 value 2
Scale response
PKE IND PWE1 PWE2 Status infos (2+3) Actual value Values as per ordering list
(4 bytes) (4 bytes)
Note
Parameter evaluation requires considerable expenditure. We suggest to limit data

exchange to parameters of the FLOAT type.
For detailed message samples, see end of item 1.5.

Fieldbus Data
1.5.2.2 Parameter Transfer

Parameter block (PKW)
Parameter block (PKW), 4 words

PKE (1st word) IND (2nd word) PWE (3rd and 4th words)
High Low PWE1 PWE2
Basic construction of parameter block
Parameter ID (PKE),
1st word The parameter ID (PKE) is always a 16-bit value.

Bits 0 to 12 (PNU) include the number of the desired parameter.
Bits 13 to 15 (AK) include the order or response ID.
For the order message (Master scale), the meaning of the order ID
is shown in table.
For the response message (scale Master), the meaning of the

response ID is shown in table. Depending on order ID, only certain
response IDs can be used.
AK PNU
Bit no. 15 14 13 Bit 0-12
Details of parameter ID (PKE)
Order ID Meaning Pos. response Neg. response

0 No order 0 -
1 Request current 2 7
parameter value (double
word)
3 Request parameter value 2 7
(double word)
4 Order description element 2 7
(double word)
Order IDs (AK) Master station —> INTECONT
Response ID Meaning
0 No order
2 Transfer current parameter value / event group (double word)
7 Order cannot be executed (error number in PWE2)
Response IDs (AK) INTECONT —> Master station

Fieldbus Data
Parameter index (IND)

2nd word
The array sub-index (in PROFIBUS profile simply called “sub-index) is
an 8-bit value and transferred upon cyclic data exchange using PPOs
in the most significant byte (bits 8 to 15) of parameter index (IND). The
less significant byte (bits 0 to 7) always has zero value.
IND function
If an order transfers a sub-index with values between 1 and 254, the
desired index of the selected parameter is transferred. For meanings
of single parameter indices, please see the table below.
When a description element is processed, the number of the desired
element is transferred.
Index Meaning
0 Default value
4 Min. value
8 Max. value
12 Unit index (1st word), after-comma places (2nd word)
Index in parameter description (IND) – most significant byte of parameter index
Parameter value (PWE)

3rd and 4th words
The parameter values (PWE) are always transferred in form of a
double word (32 bits). A PPO message can transfer only one
parameter value at a time.
A 32-bit parameter value consists of PWE1 (most significant word, 3rd
word) and PWE2 (less significant word, 4th word).
A 16-bit parameter value is transferred in PWE2 (less significant
word, 4th word). Set PWE1 (most significant word, 3rd word) to 0 value
on Master.
Bits 0 ... 15: Parameter value with 16-bit parameter, or Low portion with
32-bit parameter
Bits 16 ... 31: Value = 0 with 16-bit parameters, or High portion with 32-bit
parameter
Error number Meaning

1 Inadmissible parameter number (parameter not available or preset
value wrong, e.g. MIN/MAX exceeded up/down)
2 MIN/MAX value exceeded up/down
3 No access right
4 Order not possible in current operating state of scale
5 Order not implemented
Error numbers
Error number (PWE2)
If the response ID has value 7 (order cannot be executed), parameter value 2 (PWE2)
includes an error number specified in table.

Fieldbus Data
Order/response processing rules
An order and/or response can refer to a single parameter only.

The Master must repeat the order until receipt of relevant response.
The Master recognises the response on the given order through:
evaluation of response ID
evaluation of parameter number PNU
if necessary, evaluation of parameter index IND
if necessary, evaluation of parameter value PWE.
The complete order must be sent in one message; splitted order messages are not
admitted. The same applies to the response.
If the response message is repeated, the scale responds with the current values.
If no information from PWK interface are needed in cyclic operation (only PZD data
matter), set the order ID to “No Order”.
For samples, see item below.
1.5.2.3 General User Data Construction – Detailed Samples

Sample 1
GSD module: "NO_PARA_ID"

INTECONT parameters Configuration: “NO_PARA_ID”
Process image length Master -> Slave : 30 bytes, Slave -> Master: 32 bytes
Floating point format Siemens-KG-Format
Sample Master->Slave process image:
Bytes 1+2 0250 ID for "Write feed rate setpoint”

Bytes 3-6 0A 7D 00 00 Setpoint 1000.0 kg/hr
Bytes 7+8 0140 ID for "Commands 4+5"
Bytes 9-1 00 41 00 00 Reset control value for scale start and counter 1
Bytes 13+14 0000 Standby
Bytes 15-18 00 41 00 00 Reset control value for scale start and counter 1 (ID=0: not active)
Bytes 19+20 0752 ID to request counter 1 reading
Bytes 21+22 075C ID to request belt speed in m/s
Bytes 25+26 0758 ID to request belt load in kg/m
Sample Slave->Master process image:
Bytes 1-4 01 02 00 00 Always status messages to ID 02F0

Bytes 5-8 00 00 00 00 Always feed rate actual value kg/hr, ID=0750
Bytes 9-12 00 00 00 00 Value for ID in bytes 19+20, i.e. counter 1 reading
Bytes 13-16 00 00 00 00 Value for ID in bytes 21+22, i.e. belt speed

Bytes 21-24 00 00 00 00 Value for ID in bytes 25+26, i.e. belt load
Bytes 25-28 00 00 00 00 Standby
Bytes 29-32 00 00 00 00 Standby
Bytes 1-4 status messages: set are "Normal mode” and “No release” bits
-----------------------------------------------------------------------------------------------------------------------------------------------

Fieldbus Data
Sample 2 (preset parameter)
GSD module: “PARA_ID”

INTECONT parameters Configuration: “PARA_ID”
Process image lenght Master -> Slave : 28 bytes, Slave -> Master: 32 bytes
Floating point format IEEE
Bytes 1-8 7205 0000 4170 0000 Preset parameter "F_Control Min. – Feed Index 1" (value =15 %)
Bytes 9+10 0250 ID for "Write feed rate setpoint "
Bytes 11-14 44 7A 00 00 Setpoints 1000.0 kg/hr
Bytes 15+16 0140 ID for "Control"
Bytes 17-20 00 44 00 00 Acknowledge control value for events and reset counter 1
Bytes 23+24 075C ID to request belt speed in m/s
Bytes 27+28 0758 ID to request belt load in kg/m
Bytes 1-8 5205 0000 4170 0000 Preset parameter value accepted
Bytes 9-12 01 02 00 00 Always status messages to ID 02F0
Bytes 13-16 00 00 00 00 Always feed rate actual value in kg/h, ID=0750
Bytes 21-24 00 00 00 00 Value for ID in bytes 21+22, i.e. belt speed
Bytes 29-32 00 00 00 00 Value for ID in bytes 25+26, i.e. belt load
-----------------------------------------------------------------------------------------------------------------------------------------------
Sample 3 (preset parameter with error response)
GSD module “PARA_ID”

Process image lengths Master -> Slave : 28 bytes, Slave -> Master: 32 bytes
Bytes 1-8 7205 0000 447a 0000 Preset parameter "F_Control Min." (value =1000 %)
... ... ...
Bytes 1-8 F205 0000 4170 1000 Preset parameter value not accepted (value > MAX)
... ... ...
-----------------------------------------------------------------------------------------------------------------------------------------------
Sample 4 (read parameter)
GSD module “PARA_ID”

Process image lengths Master -> Slave : 28 bytes, Slave -> Master: 32 bytes
Bytes 1-8 3205 0000 xxxx xxxx Read parameter "F_Control Min" (xxxx = optional value)
... ... ...
Bytes 1-8 5205 0000 4170 0000 Parameter value = 15%

... ... ...

Fieldbus Data
1.6 User Data Diagnosis

EasyServe readies a very simple form of bus monitor.
Menu “Fieldbus View” lets you go to the dialog window.
The following diagnoses are possible:
Display of first 50 characters of last 50 messages in hex format. Display only shows
the mere user data.
The following errors can be recognised:

Parameter with wrong data format. All floating point numbers are improperly
indicated.
Faulty IDs preset from Master (see Lists of Cyclic Data)
Faulty data contents
Not recognised:
Initialisation error upon connection set-up
Layer 2 issues upon data exchange
Display of EasyServe monitor (Profibus or DeviceNet)
Representation of Modbus messages (incl Modbus frame)
Explanations on EasyServe monitor (Profibus sample)
Master transfers command (ID=0x0140) “Acknowledge event” bit and command

(ID=0x0160). Scale is requested to respond to IDs 0x0758, 0x075E, 0x0310 and
0x0610.

Fieldbus Data
Display meanings
Display shows current fieldbus protocol (see title) and data selected using checkbox.
“==> “ means that Master sends data to scale ( Receive INTECONT).
“<== “ identifies data sent from INTECONT to Master
Selection buttons
Record:
Starts recording on scale
Display:
Data are transferred from scale to PC and then displayed. This process may take
some seconds depending on how many data have been stored yet. Maximum the
last (most recent) 50 messages can be recorded.
Copy:
Lets you mark all (no selection), single or a group of messages by mouse click
and copy them into clipboard. If requested, data can be copied into an editor.
Checkbox:
Lets you select the direction of data and activate a time stamp.
Note
With the Modbus/TCP protocol, the EasyServe monitor displays the data of the
internal interface (scale-EtherNet module). The representation corresponds to the
Modbus sample.

Fieldbus Data
1.7 Lists of Cyclic Data
1.7.1 Explanations on Data Lists
There are separate lists for the various data types.

Each list contains the following information:
ID
Used with protocols:

Modbus for data address
Modbus/TCP for data address
Profibus DP for ID indicating the value to be transferred
DeviceNet s. Profibus
The “ID” value addresses the complete data word. If a bit is to be addressed (as is
possible with MODBUS), add the number before value meaning to the word address.
e.g.: General alarm (data segment "Status")
Word address 0x02F0 + 5 --> bit address 0x02F5
The bold-printed IDs shall be used for:

Profibus DP
DeviceNet
They determine the base address of a double word.
Value
The "Value" column states the meaning of the value in the INTECONT system.
Scale types
The “Type” column indicates whether or not the respective value is available with the
selected scale type. If not available, ZERO value is returned. Preset values relating
to non-existing IDs are not evaluated.
Note:
Non-existing values are possibly available in a later software version (new extension
stage).
Mode (commands only)

Commands can be triggered by level or edge. Letter “D(ynamic)“ indicates that a
change from “0” to “1” triggers the desired action. Letter “S(tatic)“ indicates that the
level determines the function.

Fieldbus Data
1.7.2 Commands
Attention: Special condition or source

parameter for marked values "!". See manual.
(x) Not available with measusing systems

o Reserved for use with EasyServe
Byte- Word- ID ID Rem. Value Mode VBW VDB VLW VMD VDM
Offset Offset (HEX) (DEC)
For Protocol 3964(R), data block 96 HEX

starts here!
0 0 100 256 ! Command 0 (coded as number)
Feed index (Range 1...4)
1 Century x x x x x
2 1 Command 1 (coded as number)

Year x x x x x
3 Month x x x x x
4 2 120 288 Command 2 (coded as number)

Day x x x x x
5 Hour x x x x x
6 3 Command 3 (coded as number)

Minute x x x x x
7 Second x x x x x
8 4 140 320 Command 4 LO (bit-coded)

! 0 – Start Scale (D) x x x x x
! 1 – Stop Scale (D) x x x x x
2 – Clear Events (D) x x x x x
3 – Fieldbus-Release (S) x x x x x
4 – Select Volumetric Mode (D) x x x
! 5 – Select Gravimetric Mode (D) x x x
6 – Reset Totalizer 1 (D) x x x x x
7 – Reset Totalizer 2 (D) x x x x x
9 Command 4 HI (bit-coded)
! 8 – Volum. Synchronous (D) x x
9 – Moisture Corr. ON (D)
A – Moisture Corr. OFF (D)
B – Meas. Drive OFF (D) x
! C – Gate Feedback (S)
D – Open Gate Manual (D)
E – Stop Gate Manual (D)
F – Close Gate Manual (D)
10 5 Command 5 LO (bit-coded)
0 – Select Batch (D) x x x x x
1 – Deselect Batch (D) x x x x x

Fieldbus Data


2 - Abort Batch (D) x x x x x

3 - Next Batch +Clearance (D) x
4 - Make-Up (D) x x x
5 - Emergency Setpoint ON (D)
6 - Emergency Setpoint OFF (D)
7 - Meas. Drive ON (D)
8 - Filling Start (D) x
9 - Filling Stop (D) x
A - Emptying Start (D) x
B - Emptying Stop (D) x
C - Init. Hopper Controller (D)
D - Activate Fill Unit (D)
E - Activate Prefeeder (D) x x x x
F - Stop Prefeeder (D) x x x x
! 0 - Tare (D) x x x x x
! 1 - Zero Set (D) x x x x
! 2 - Weight Check (D) x x x x
! 3 - Pulses/Revolution (D) x x
! 4 - DAE Adjustment (D) x
! 5 - Linearization P1 (D) x
! 9 - Volumetric (D) x
! A - Optimize controller (D) x
B - Calibration Acquire (D) x x x x x
C - Calibration Abort (D) x x x x x
D - Time Acquire (D) x x x x x
! E - Bin: Tare (D)
! F - Bin: Weight Check (D)
! 8 - Print Batch Report (D) x x x x x

Fieldbus Data


9 – Print Status Report (D) x x x x x

A – Print Intermediate Totalizer (D) x x x x x
B – Cancel Printout (D) x x x x x
C – Print Parameters (D) x x x x x
D – Print Parameter Shortlist (D)
E – Reserved (Register EasyServe) (D) o o o o o
F – Reserved (Deregister EasyServe) (D) o o o o o
0 – Start Keyb. Mode (D) x x x x x
1 – Stop Keyb. Mode (D) x x x x x
2 – Start Simulation (D) x x x x
3 – Stop Simulation (D) x x x x
4 – Load Default Parameter (D) x x x x x
5 – Check Meas. Start (D) x
6 – Manual Prefeeder (ES only) (D)
7 – Automatic Prefeeder (ES only) (D)
reserved
1.7.3 Preset Values in Floating Point Format

parameter for marked values "!". See
manual.
Byte- Word- ID ID Bem. Value VLW VBW VDB VMD VDM

For Protocol 3964(R), data block AO

HEX starts here!
0 0 250 592 ! Absolute Setpoint [kg/h] x x x
4 2 252 594 ! Absolute Batch Setpoint [kg] x x x x X
8 4 254 596 Make-Up Setpoint [kg] x x X
12 6 256 598 Batch No. x x x
16 8 258 600 PLC-Analog-OUT 1
20 10 25A 602 PLC-Analog-OUT 2
24 12 25C 604 Span Correction Value
28 14 25E 606 Tare Correction Value

Fieldbus Data
32 16 260 608 ! Difference Feed Rate [kg/h]

36 18 262 610 Hopper Level [kg]
40 20 264 612 ! Setpoint Feeder 2 [kg/h]
44 22 266 614 Setpoint Hopper Level [kg]
48 24 268 616
52 26 26A 618
56 28 26C 620
60 30 26E 622
1.7.4 Preset Values in Integer Format (Modbus)

parameter for marked values "!". See
manual.
Byte- Word- ID ID Value VLW VBW VDB VMD VDM
0 0 20 32 ! Serial Setpoint [kg/h] x x

0 to MAXINCR. = 0 to 300% P
2 1 21 33 ! Serial Batch Setpoint [kg/h] x x x x
0 to MAXINCR. = 0 to 100% P * 8 HRS.
4 2 22 34 Make-Up Setpoint [kg/h] x x x
0 to MAXINCR. = 0 to 100% P

Fieldbus Data
1.7.5 Status Information
Byte- Word- ID ID Value VBW VDB VLW VMD VDM

For Protocol 3964(R), data block 64 HEX

starts here!
0 0 02D0 720 Status 0 (coded as number)
Scale Type (Low Byte) x x x x x
1 Software Revision (High Byte) x x x x x
2 1 Status 1 (coded as number)

Software-Version (Low-Byte) x x x x x
3 Software-Version (High-Byte) x x x x x
4 2 02F0 752 Status 2 LO (bit-coded)

0 – Scale On (measurement active; no motor x x x x x
control in local mode)
1 - No Release x x x x x
2 – Counter Active x x x x x
3 – Volumetric x x x
4 – Select. Language OK x x x x x
5 – Alarm x x x x x
6 – Warning x x x x x
7 – Calibration Active x x x x x
5 Status 2 HI (bit-coded)
8 – Normal Mode x x x x x
9 – Keyboard Mode x x x x x
A – Local Mode
B – Simulation Mode x x x x
C – Volum. Start-Up x x x
D – Meas. Drive ON x
E – Wheel Meas. Drive Delay x
F – Setpoint Limited x x
6 3 Status 3 LO (bit-coded)
0 – Batch Selected x x x x x
1 – Batch Active x x x x x
2 – Batch Dribble Feed (pre-act cont.) x x x x x
3 – Batch + Clearance x
4 – NON-SI active x x x x x
5 – Dead Time active
6 – Dead Time Setpoint active
7 – Dead Time ON/OFF active
8 – Tare x x x x x
9 – Zero Set x x x x
A – Weight Check x x x x
B – Pulses/Revolution x x

Fieldbus Data

C – DAE Adjustment x
D – Auto Zero active x x x
E – Volumetric Adaption x
F – Gravimetric Optimization x
8 4 0310 784 Status 4 LO (bit-coded)

0 – Meas. System x x x
1 – Gain-In-Weight x
2 – Filling Active x
3 – Discharge Active x x x
4 – Gate Open x
5 – Gate Closed x
! 6 – 2nd Batch Unit active (VLW20151 only)
7 – Surge Hopper present
8 – Feed rate > MAX x x x x x
9 – Feed rate < MIN x x x x x
A – Belt load > MAX x x
B – Belt load < MIN x x
C – Speed > MAX x x
D – Speed < MIN x x
E – Bin > MAX
F – Bin < MIN
0 – Bin Level Control existent
1 – Hopper level > MAX x
2 – Hopper level < MIN x
3 – Measured load > MAX x
4 – Measured load < MIN
5 – n > MAX x
6 – n < MIN x x
7 – Check system waits for acknowledgement
8 – Check system available
9 – Rel. tare exceeded
A – Abs. tare exceeded
B – Rel. range exceeded
C – Abs. range exceeded
D – Check meas. announced
E – Prepare check
F – Check active
12 6 0330 816 Status 6 LO (bit-coded)

0 – NON-SI active x x x x x
1 – Waiting for Confirm. x x x x x
2 – Waiting for checkweight x x x x

Fieldbus Data

3 – Param. active to VLB x x x x x

4 – Linearization P1 x
8 – Open Gate x
9 – Blow-out ON x
A – Manual Prefeeder
B - Bin: Tare
C - Bin: Weight Check
D – Optimization Bin Controller
E - 2nd Bridge > MAX
F - 2nd Bridge < MIN
0 – Emergency Setpoint active
1 – Trend active
2-
3-
4-
5-
6-
7-
8 – Moisture Corr. Active
9 – Moisture > MAX
A – Moisture Meas. Faulty
B – PreFeed Control Active
C – EasyServe active x x x x x
D – EasyServe announced x x x x x
! E – Feeder 1 Active (VLW20152 only)
! F – Feeder 2 Active (VLW20152 only
16 8 0350 848 Status 8

0 – Calibr. Set Nominal Feed Rate
1 - Dig. Output Pre-cut-off Amount
2 – MAX Limit Value
3 - MIN Limit Value
4 – VSM 20110 (DISOCONT L)
5 – Refilling Active x x x x
6 – VSM 20107 (Pulverized Coal)
7 – Fill Bin Weigher
17 Reserved
8-
9-

Fieldbus Data

A-
B-
C-
D-
E-
F-
9 Status 9
18 Reserved
19 Reserved
The events defined in a type of scale react on

the event-bits. Bits not used are send with the
value Null.
20 10 0370 880 Event S1-S8

0 – Event Warning 2 S1 x x x x x
21 Event S9
9-
A-
B-
C-
D-
E-
F-
22 11 --
23 --
24 12 0390 912 Event Warning 2 E1-E8 x x x x x

25 Event Warning 2 E9 x x x x x
26 13 --
27 --
28 14 03B0 944 Event Warning 2 B1-B8 x x x x x

29 Event Warning 2 B9 x x x x x
30 15 --
31 --
32 16 03D0 976 --

Fieldbus Data

33 --
34 17 --
35 --
36 18 03F0 1008 Event Warning 2 C1-C8 x x x x x

37 Event Warning 2 C9 x x x x x
38 19 Event Warning 2 H1-H8 x x x x x

39 Event Warning 2 H9 x x x x x
40 20 0410 1040 Event Warning 2 L1-L8 x x x x x

41 Event Warning 2 L9 x x x x x
42 21 Event Warning 1 S1-S8 x x x x x

43 Event Warning 1 S9 x x x x x
44 22 0430 1072 --
45 --
46 23 Event Warning 1 E1-E8 x x x x x

47 Event Warning 1 E9 x x x x x
48 24 0450 1104 --
49 --
50 25 Event Warning 1 B1-B8 x x x x x

51 Event Warning 1 B9 x x x x x
52 26 0470 1136 --
53 --
54 27 --
55 --
56 28 0490 1168 --
57 --
58 29 Event Warning 1 C1-C8 x x x x x

59 Event Warning 1 C9 x x x x x
60 30 04B0 1200 Event Warning 1 H1-H8 x x x x x

61 Event Warning 1 H9 x x x x x
31 Event Warning 1 L1-L8 x x x x x

62 Event Warning 1 L9 x x x x x
63
64 32 04D0 1232 Event Alarm S1-S8 x x x x x
65 Event Alarm S9 x x x x x

Fieldbus Data

66 33 --
67 --
68 34 04F0 1264 Event Alarm E1-E8 x x x x x

69 Event Alarm E9 x x x x x
70 35 --
71 --
72 36 0510 1296 Event Alarm B1-B8 x x x x x

73 Event Alarm B9 x x x x x
74 37 --
75 --
76 38 0530 1328 --
77 --
78 39 --
79 --
80 40 0550 1360 Event Alarm C1-C8 x x x x x

81 Event Alarm C9 x x x x x
82 41 Event Alarm H1-H8 x x x x x

83 Event Alarm H9 x x x x x
84 42 0570 1392 Event Alarm L1-L8 x x x x x

85 Event Alarm L9 x x x x x
86 43 Digital Inputs
0 – DI1 x x x x x
1 – DI2 x x x x x
2 – DI3 x x x x x
3 – DI4 x x x x x
4 – DI5 x x x x x
5 – DI6 x x x x x
6 – DI7 x x x x x
7-
87 Digital Inputs: Error Bits

8 – DI1 Error
9 – DI2 Error
A –DI3 Error
B – DI4 Error
C – DI5 Error
D – DI6 Error x x x x x
E – DI7 Error x x x x x
F-

Fieldbus Data

88 44 0590 1424
89
90 45 Digital Outputs
0 - DO1 x x x x x
1 - DO2 x x x x x
2 - DO3 x x x x x
3 - DO4 x x x x x
4 - DO5 x x x x x
5 - DO6 x x x x x
6 - DO7 x x x x x
7 - DO8 x x x x x
91
92 46 05B0 1456
93
94 47
95
96 48 05D0 1488
97
98 49
99
100 50 05F0 1520

101
102 51
103
104 52 0610 1552 Highest-Priority Event (LO) x x x x x

Bit 0 – 3 Event number
Range 0 – 8
corresponds to displays 1 - 9
Bit 4 – 7 Event group

Range 1 – 12
S = 1, E = 3, B=5, C=9, H=10, L=11
105 Highest-Priority Event (HI) x x x x x

Bit 8 – 11 Event class
Range 1 – 4
A=1, W1=2, W2=3, (IG=4)
Bit 12 - 15 Acknowledge event

Range 0 – 1
Acknowledged = 1, Not acknowledged = 0

Fieldbus Data

106 53 Parameter block of the event class

107 Parameter block number
108 54 0630 1584 Century x x x x x

109 Year x x x x x
110 55 Month x x x x x
111 Day x x x x x
112 56 0650 1616 Hour x x x x x

113 Minute x x x x x
114 57 Second x x x x x
115 Feed index
116 58 0670 1648 Next Event from error logger (LO) x x x x x

(Zero if list is empty)
Bit 0 - 3 Event number

Range 0 - 8
corresponds to displays 1 - 9
Bit 4 - 7 Event group

Range 1 - 12
S = 1, E = 3, B=5, C=9, H=10, L=11
117 Next Event from error logger (HI) x x x x x
Bit 8 - 11 Event class

Range 1 - 4
A=1, W1=2, W2=3, (IG=4)
Bit 12 Acknowledge event

Range 0 - 1
Acknowledged = 1, Not acknowledged = 0
Bit 13 New Event

Range 0 - 1
New = 1
Bit 14 Reset Event

Range 0 - 1 (Reset = 1)
Bit 15 Time: am /pm

Range 0 - 1 (am = 0, pm = 1)
118 59 Time stamp event logger x x x

119 Time stamp event logger x x x
Bit 0- 5: Seconds (0-59)
Bit 6-11: Minutes (0-59)
Bit 12-15: Hours (0-11)

Fieldbus Data
1.7.6 Measurement Values in Floating Point Format

For Protocol 3964(R), data block 6E HEX

starts here!
0 0 0750 1872 Feed Rate [kg/h] x x x x x
4 2 0752 1874 Totalizer 1 [kg] x x x x x
16 8 0758 1880 Belt Load [kg/m] x x
20 10 075A 1882 Measured load [kg] x x
24 12 075C 1884 Belt Speed [m/s] x x
28 14 075E 1886 Speed [1/min] x x
32 16 0760 1888 Fill Weight [kg] x
36 18 0762 1890 Surge Hopper [kg]
40 20 0764 1892 2nd Platform [kg/m]
44 22 0766 1894 Actual Setpoint [kg/h] x x x
48 24 0768 1896 Batch Feed Rate [kg] x x x x x
52 26 076A 1898 Batch Res. Amount [kg] x x x x x
56 28 076C 1900 Relative Setpoint [%] x x x
60 30 076E 1902 Prefeeder Position [%]
64 32 0770 1904 Deviation [%] x x x
68 34 0772 1906 Moisture [%]
72 36 0774 1908 Feed Rate Moisture Corr. [kg/h]
76 38 0776 1910 Totalizer 1 Corr. [kg]
80 40 0778 1912 Totalizer 2 Corr. [kg]
84 42 077A 1914 Totalizer 3 Corr. [kg]
88 44 077C 1916 Rel. Bin Weight
92 46 077E 1918 Setpoint Bin Level
96 48 0780 1920 VSE1: Analog Output [mA] x x x x x
100 50 0782 1922 VEA1: Analog Input [mA] x x x x x
104 52 0784 1924 VEA1: Analog Output [mA] x x x x x
108 54 0786 1926 VSE2: Analog Output [mA]
112 56 0788 1928 VEA2: Analog Input [mA]
116 58 078A 1930 VEA2: Analog Output [mA]
120 60 078C 1932 VSE3: Analog Output [mA]
124 62 078E 1934 VEA3: Analog Input [mA]
128 64 0790 1936 VEA3: Analog Output [mA]
132 66 0792 1938 Belt Slip [%] x x
136 68 0794 1940 Belt Drift [cm] x x
140 70 0796 1942 Relative Feed Rate [%] x x x x x
144 72 0798 1944 Relative Belt Load [%] x x
148 74 079A 1946 External Setpoint [kg/h] x x x
152 76 079C 1948 Batch Setpoint [kg] x x x x x
156 78 079E 1950 Tacho [Hz] x x x x
160 80 07A0 1952 Utilize L/C [%] x x x x x
164 82 07A2 1954 Load Cell Raw VAP [mV/V] x x
168 84 07A4 1956 Load Cell Raw BIC [mV/V] x x

Fieldbus Data

172 86 07A6 1958 Load Cell Raw [mV/V] x x x x x

176 88 07A8 1960 Controller Magnitude [mA] x x x
180 90 07AA 1962 Rel. Fill Weight [%] x
184 92 07AC 1964 Calibration Result 1 -Current Upper Value x x x x x
188 94 07AE 1966 Calibration Result 2 - Current Lower Value x x x x x
192 96 07B0 1968 Y_unlin x
196 98 07B2 1970 Y_lin x
200 100 07B4 1972 DAE Utilization [%] x
204 102 07B6 1974 Differential of F [kg/h] x
208 104 07B8 1976 Adaption Factor Index 1 x
212 106 07BA 1978 Adaption Factor Index 2
216 108 07BC 1980 Adaption Factor Index 3
220 110 07BE 1982 Adaption Factor Index 4
224 112 07C0 1984 CM Meas. Time [s] x
228 114 07C2 1986 Number of all CM x
232 116 07C4 1988 Curr. No. x
236 118 07C6 1990 CM: Mean Delta-F [kg] x
240 120 07C8 1992 CM Mean Feed Rate [kg/h] x
244 122 07CA 1994 Feed Constancy [%] x
248 124 07CC 1996 Nominal Belt Load [kg/m] x x
252 126 07CE 1998 Feed Constancy [g] x
256 128 07D0 2000 Control Magnitude Yz [mA]
260 130 07D2 2002 Control Magnitude Yzi [%]
264 132 07D4 2004 Nominal Measured Load [kg] x x
268 134 07D6 2006 Actual Value, not linearized [kg/h] x x
272 136 07D8 2008 Actual Tare [kg] x x x x
276 138 07DA 2010 Bin: Utilize L/C [%]
280 140 07DC 2012 Bin: Load Cell Raw [mV/V]
284 142 07DE 2014 Control Magnitude Yb [mA]
288 144 07E0 2016 Control Magnitude Ybi [mA]
292 146 07E2 2018 Analog Input DI4 [mA]
296 148 07E4 2020 Check: Relative Tare [%]
300 150 07E6 2022 Check: Relative Span [%]
304 152 07E8 2024 Check: Continuous Totalizer Z [kg]
308 154 07EA 2026 Check: Result F/Z
312 156 07EC 2028 Check: Measurement Time [h]
316 158 07EE 2030 Check: Belt Length [m]
320 160 07F0 2032 2nd Bridge: Relative Belt Load [%]
324 162 07F2 2034 2nd Bridge: Load Cell Raw [mV/V]
328 164 07F4 2036 2nd Bridge: Utilize L/C [%]
332 166 07F6 2038 Control Magnitude Y2 [%]
336 168 07F8 2040 Difference Feed Rate [kg/h]
340 170 07FA 2042 Rel. Actual Setpoint [%] x x x
344 172 07FC 2044 Rel. Measured Load [%] x x
348 174 07FE 2046 Bin Feed Rate [kg/h]
352 176 0800 2048 Check Meas. Monitoring [%]
356 178 0802 2050 Component Control Magnitude [mA]
360 180 0804 2052 Current Batch-No. x x x
364 182 0806 2054 Totalizer Component 1 [kg]

Fieldbus Data

372 186 080A 2058 Totalizer Component 3 [kg]

376 188 080C 2060 Totalizer Component 4 [kg]
380 190 080E 2062 Totalizer Component 5 [kg]
404 202 081A 2074 Totalizer Sum of all Batches [kg]
408 204 081C 2076 Tacho Input VSE 2 [Hz]
412 206 081E 2078 Corr. Feed Rate rel. [%]
416 208 0820 2080 Belt Load [kg/m] non-linearized x
420 210 0822 2082 2-Sensor Slip [%]
424 212 0824 2084 Setpoint last / act. Batch [kg]
428 214 0826 2086 Current No. of last / act. Batch
432 216 0828 2088 Component No. of last / act. Batch
436 218 082A 2090 EIO: Analog Output 1 [mA]
440 220 082C 2092 EIO: Analog Output 2 [mA]
444 222 082E 2094 EIO: Analog Output 3 [mA]
448 224 0830 2096 EIO: Analog Output 4 [mA]
452 226 0832 2098 EIO: Analog Input 1 [mA]
468 234 083A 2106 Setpoint Feeder 1 [kg/h]
472 236 083C 2108 Setpoint Feeder 2 [kg/h]
476 238 083E 2110 Nominal Feed Rate Total [kg/h]
480 240 0840 2112 Contr. Magnit. 2nd Feeder [mA]
484 242 0842 2114 Speed 2nd Feeder [1/min]
488 244 0844 2116 Feed Rate 2nd Feeder [kg/h]
492 246 0846 2118 Fill-Weight 2nd Feeder [kg]
496 248 0848 2120 Counter 2nd Feeder
500 250 084A 2122 Check Weigher Print Value 1 x
504 252 084C 2124 Check Weigher Print Value 2 x
508 254 084E 2126 Check Weigher Print Value 3 x
512 256 0850 2128 Check Weigher Actual Value [%] x
516 258 0852 2130 Check Weigher Variance
520 260 0854 2132 L/C Resistance [ohms] x x x x x
524 262 0856 2134 Make-up Setpoint [kg] x x x
528 264 0858 2136 Make-up Residual Amount [kg] x x x
532 266 085A 2138 Mean Value I [%] x
536 268 085C 2140 Variance I [%] x
540 270 085E 2142 Belt Load QMAX [%] x
544 272 0860 2144 Time QMIN [%] x
548 274 0862 2146 Taring Result 1 [%] x
552 276 0864 2148 Taring Result 2 [%] x
556 278 0866 2150 Taring Result 3 [%] x
560 280 0868 2152 Taring Result 4 [%] x
564 282 086A 2154 Taring Result 5 [%] x
568 284 086C 2156 Check Weigher Print Value 4 x

Fieldbus Data

572 286 086E 2158 Pulse Sensor x x
1.7.7 Measurement Values in Integer Format (Modbus)

0 0 30 48 Actual value [kg/h] x x x x x

0 to MAXINCREMENTS = 0 to 300% P
0 to MAXINCREMENTS = 0 to P * 8 Hours
8 4 34 52 Belt Load [kg/m] x x
0 to MAXINCREMENTS = 0 to 200% Q
10 5 35 53 Measured Load [kg] x x
0 to MAXINCREMENTS = 0 to 200% Q
12 6 36 54 Speed [m/s] x x
0 to MAXINCREMENTS = 0 to 100%V [cm/s]
14 7 37 55 RPM [1/min] x x
0 to MAXINCREMENTS = 0 to 100% N
16 8 38 56 Hopper [kg] x
0 to MAXINCREMENTS = 0 to 100% F
18 9 39 57 Surge Hopper [kg]
0 to MAXINCREMENTS = 0 to 100% B
20 10 3A 58 Surge Hopper [kg]
0 to MAXINCREMENTS = 0 to 200 % Q
22 11 3B 59 Effective Setpoint [kg/h] x x x
0 to MAXINCREMENTS = 0 to 300% P
24 12 3C 60 Batch Actual Value [kg] x x x x x
26 13 3D 61 Batch Residual Amount [kg] x x x x x
28 14 3E 62 Procental Setpoint Evaluation [%] x x
0 to MAXINCREMENTS = 0 to 100 %
30 15 3F 63 Prefeeder Position [%]
32 16 40 64 Deviation [%] x x

Fieldbus Data
1.7.8 Values in Long Integer Format

For Protocol 3964(R), data block C8 HEX

starts here!
0 0 0980 2432 Pulses still output
4 2 0982 2434 Pulses output x x x x x
8 4 0984 2436 Time Voltage ON [h] x x x x x
12 6 0986 2438 Time Scale ON [h] x x x x x
16 8 0988 2440 Reserved x
20 10 098A 2442 Selected Options x x x x x
24 12 098C 2444 Status Bit Field 1 for Commands 4 and 5 x x x x x
28 14 098E 2446 Status Bit Field 2 for Commands 6 and 7 x x x x x
32 16 0990 2448 Status Bit Field 3 for Commands 8 and 9 x x x x x
36 18 0992 2450 Status Bit Field 4 for Commands 10 and 11 x x x x x
40 20 0994 2452 Calibration Result 1 – Text ID x x x x x
44 22 0996 2454 Calibration Result 1 –Unit ID x x x x x
48 24 0998 2456 Calibration Result 2 – Text ID x x x x x
52 26 099A 2458 Calibration Result 2 – Unit ID x x x x x
56 28 099C 2460 Calibration Result 1 – After -comma-places x x x x x
ID
60 30 099E 2462 Calibration Result 2 – After-comma-places ID x x x x x
64 32 09A0 2464 Calibration Error Text ID x x x x x
68 34 09A2 2466 Para-Checksum x x x x x
72 36 09A4 2468 Software Date x x x x x
76 38 09A6 2470 Flash-Checksum x x x x x
80 40 09A8 2472 Flash-Checksum calculated x x x x x
84 42 09AA 2474 Hardware-Version x x x x x
88 44 09AC 2476 Option Card Version x x x x x
92 46 09AE 2478 Pulses Output x x x x x

Fieldbus Data
1.7.9 Events
The input in table references the parameter used to change the event class.
System Message (S-1) VBW VLW VDB VMD VDM
S1 Memory Error O 02 Q 02 N 02 M 02 M 02
S2 No Release O 07 Q 07 N 07 M 06 M 04
S3 Maintenance STR-Meter K 04 K 04 K 04 K 04 K 04
S4 Maintenance Interval Electric K 02 K 02 K 02 K 02 K 02
S5 RESERVE
S6 RESERVE
S7 Simulation active Q 10 N 10 M 08 M 07
S8 Setpoint limited Q 11 N 11 M 09
S9 Data Link Host L 03 L 03 L 03 L 03 L 03
Electrical System (E-3) VBW VLW VDB VMD VDM

E1 Power Failure O 01 Q 01 N 01 M 01 M 01
E2 Namur Error Tacho O 04 Q 04 N 04 M 04
E3 Namur Error Belt O 05 Q 05 N 05
E4 RESERVE
E5 Stand-By F 14 F 14 F 10
E6 External Input F 15 M 10 M 08
E7 RESERVE
E8 RESERVE
E9 RESERVE
Material Flow (B-5) VBW VLW VDB VMD VDM

B1 Out of Tolerance I 06 I 05 I 05 I 05 I 05
B2 Control Deviation R 24 O 08 N 06
B3 Controller Ltd. R 25 O 09 N 07
B4 Max BATCH Act. Value I 08
B5 DAE active O 08
B6 DAE Time O 09
B7 T_Gate H 16
B8 T_Volumetric H 17
B9 Linearization S 10 P 10 O 10 N 10
Calibration (C-9) VBW VLW VDB VMD VDM

C1 L/C Input O 06 Q 06 N 06 M 05 M 03
C2 Tacho Input O 03 Q 03 N 03 M 03
C3 Belt Skew N 12 M 12
C4 Belt Drift N 10 M 10
C5 Tare Correction > MAX H 05 H 04 H 04
C6 RESERVE
C7 Set Time To Zero H 07
C8 Slip Error N 14 M 14
C9 Tare Diff. > MAX H 12
Maximum (H-10) VBW VLW VDB VMD VDM

H1 I > MAX F 04 F 04 F 04 F 04 F 04
H2 Load > MAX F 08 F 08
H3 v > MAX F 12 F 12
H4 L/C Input > MAX O 08 Q 08 N 08 M 07 M 05
H5 F > MAX F 08
H6 Wheel Overload F 06
H7 n > MAX F 12
H8 F > Fo H 09
H9 RESERVE
Minimum (L-11) VBW VLW VDB VMD VDM

L1 I < MIN F 02 F 02 F 02 F 02 F 02
L2 Load < MIN F 06 F 06
L3 v < MIN F 10 F 10
L4 L/C Input < MIN O 09 Q 09 N 09 M 06
L5 F < MIN F 06
L6 RESERVE
L7 n < MIN F 10 F 08
L8 F < Buffer MIN H 07
L9 RESERVE

PROFIBUS DP
2 PROFIBUS DP
This chapter describes the interfacing of the INTECONT Profibus slave to a Profibus
Master assembly.
Described is the functionality of the Profibus module, the data exchange between
Profibus Master and INTECONT, fault diagnosis and troubleshooting. The Profibus
hardware is described at the “Profibus Module VPB020V“ item.
Designed to assist the S7 programmer in commissioning, Manual BVH2204 describes
the use of the general user data construction at the DISOCONT example. However,
data construction is identical for INTECONT.
2.1 Commissioning Guideline
1. Prepare hardware as described at the “Profibus Module VPB020V“item.

2. Determine data to be transferred. Check to see if the data of FIXED mode 1/2
suffice to meet your requirements. If YES, select desired process image at
“Fieldbus Communication Configuration”. If NO, configure your process image by
input of requisite IDs (see “Fieldbus Data” chapter).
3. Set INTECONT “Address” parameter.
4. Generate Master parameter records using the GSD file.
5. Start communication through Master.
2.2 Profibus Module Functionality
Module certified to EN 50170

Cyclic user data exchange with Master (DP-V0)
Automatic baud rate recognition
Bus interface monitoring
Easy parameterisation of VPB 020V using base unit control station or EasyServe
diagnostic tool
Support of PROFIBUS control command SYNC for synchronised data transfer
from Master to various slaves
Support of PROFIBUS control command FREEZE for synchronised data transfer
from various slaves to Master
No user-specific diagnostic functions
Fail Safe: clear state supported
No change of station address via bus
For details and examples on user data construction, see “Fieldbus Data” chapter.

PROFIBUS DP
2.4 Settings on DP-Slave (INTECONT)
For parameterisation, you can use the Operator Panel or the EasyServe tool.
The parameter description holds for either unit.
Parameter Value range Default Explanation
Protocol type all fieldbus protocols NO Select protocol: here

Profibus-DP
Timeout Host 0 ... 300 s 10 s Designed for interface
monitoring.
ZERO value means that
interface is not activated.
Communication W2 (Warning 2), IG Class of communication
Host W1 (Warning 1), error
A(LARM),
IG(nore)
Address 0 ... 126 126 Slave address on Profibus
Configuration FIXED-1, FIXED-1 Lets you set construction

FIXED-2, and meaning of user data.
NO_PARA_ID,
PARA_ID
Float format Siemens-KG, IEEE IEEE Format for all setpoints,
measurement values and
floating point parameters.
Note
Any change to a grey-marked parameter resets the field connection, i.e. the slave
is excluded from user data exchange for approx. 4 sec.
2.5 Settings on Profibus DP Master
Device Master File (GSD)
INTECONT is a modular slave whose properties are described by 3 modules.
Note:
You will find the INTECONT configuration in the S7 hardware configurator at
“Profibus-DP/Further Fieldbuses/Controller/INTECONT”.
You can download the current GSD file (ICV10524.GSD) from the Schenck-
Process service web-page (www.schenck-process.de, Path: Service-Download-
Bus systems-Profibus).
Reading/writing of double words in S7 systems: please note that the INTECONT
double words can neither be read nor written using function modules SFC14 and
SFC15 of S7 systems. Access the peripherals direct.

PROFIBUS DP
2.6 Diagnosis and Troubleshooting
If you have selected one of the fieldbuses, any malfunction is reported by event
message "Communication Host” (S9) provided that this message is assigned to an
event class other than IG(NORE). The message is output both on display and on
EasyServe. If only the display is available, read the next two items. The EasyServe, if
present, provides further information on fault diagnosis.
2.6.1 Event Message“Data Link Host” S9
The event message is designed to report any error concerning the fieldbus module:
Different station address on Master and scale
Cable connection between fieldbus module and base board faulty. Watch LEDs on
module. In case of doubt, restart system, and module is initialised provided that
parameters are properly set (red LED flashes).
Fieldbus cable defective or improperly connected. For proper connection, see
“Fieldbus Hardware” chapter.
Fieldbus hardware bus termination is not (or various times) available.
Check resistors on module (supplied state: "Not activated") and on bus
connectors. For details, see “Fieldbus Hardware” chapter.
Selected protocol type does not correspond to the extension board. Change
parameterisation or replace module.
Timeout parameter value too small. Change scale parameterisation.
Scale configuration differs from Master configuration. Change GSD module or
scale parameterisation.
Inadmissible ID detected in Master --> scale message (only use bold-printed IDs).
All preset IDs in message from host system have zero value (communication
between Master-CPU and communication processor (CP) failed). Minimum one
preset ID must be unequal to zero, or – in FIXED mode – the release bit must be
set.

PROFIBUS DP
2.6.2 LEDs on Profibus Module
Lighting on Profibus module (VPB020V):
H1 (red) Flashing: if fieldbus module is freshly initialised, e.g.

after power-on and change of certain fieldbus
parameters (highlighted grey).
OFF: if initialisation is complete and user data exchange OK
H2 ON: if user data are being sent
(green) OFF: if module is not yet initialised or fieldbus faulty
If no LED lights, check parameterisation and cabling to base board.
2.6.3 EasyServe Fieldbus View
The representation of cyclic user data is the same for all protocols. For details, see
“Fieldbus Data” chapter.
2.7 Profibus Module (VPB020V)

To provide an interface to the Profibus, the module can be attached to the INTECONT
cover. The module is certified to EN 50170, the protocol used is DP-V0.
Bus termination:
Activate the bus terminals resistors on first and the last stations on bus. To do so, set
all plug-in jumpers on board to position 1-2. On standard, the resistors are not
activated (position 2-3).
Bus address:
Set address via parameter.
LED
Status LED for communication OK (green)
Bus error or configuration display (red)
X20

PROFIBUS DP
Connector assignment
Pin Signal Signal

(X20, 9-pin Sub-D-female) (XP3, 5-pin Phoenix MSTB 3.5
max. 1.5mm²)
Not used in INTECONT
1 - B-Line, positive RS485 RxD/TxD *
2 - A-Line, negative RS485 RxD/TxD
**
3 B-Line, Positive RS485 RxD/TxD * GND BUS
4 RTS, Request To Send +5V BUS
5 GND BUS Screening
6 +5V BUS -
7 - -
8 A-Line, Negative RS485 RxD/TxD ** -
9 - -
Housing Bus Cable Shield -
* red wire
** green wire
Characteristics
Isolation optocouplers
Voltage supply 5V DC internal
Current supply max. 310mA
Connectors 5-pin Phoenix MSTB 3.5 max. 1.5mm²
9-pin Sub-D-female
2.8 For Further Reading

Profibus standard EN 50170
Profibus user organisation www.profibus.com
PROFIBUS-DP/DPV1, Grundlagen, Manfred Popp, Hüthig Verlag , 2000
Tipps und Tricks für Anwender
HMS documentation on Anybus-IC www.hms-networks.com
BVH2204 Commissioning aid for S7 programmers
BVH2098AA EASYSERVE

DeviceNet
3 DeviceNet
The present chapter describes the interfacing of the INTECONT DeviceNet slave to a
DeviceNet Master assembly.
Described is the functionality of the DeviceNet module, the data exchange between
DeviceNet Master and INTECONT, diagnosis and troubleshooting.
For DeviceNet hardware, see “DeviceNet Module VCB020V“ item.
Prepare hardware as described at the “DeviceNet Module VCB020V“ item.

Determine data to be transferred using data IDs (see “Fieldbus Data”).
Generate Master parameter records using EDS file.
Set INTECONT parameter “Slave Address”.
Start communication through Master.
3.2 DeviceNet Module Functionality
Module certified to DeviceNet specification 2.0

Cyclic exchange of user data with Master. As a rule, the POLL mode is used for
transfer of I/O data.
Easy parameterisation of VCB020V via base unit control station or EasyServe
diagnostic tool.

For details and samples on general user data construction, see “Fieldbus Data”
chapter.

DeviceNet
3.4 Settings on DeviceNet Slave (INTECONT)

For parameterisation, use Operator Panel or EasyServe tool.
The parameter description holds for both units.
Protocol type all fieldbus NO Select protocol: here

protocols DeviceNet
monitoring.
interfance is not activated.
Communication W2 (Warning 2), IG Class of communication error
Host W1 (Warning 1),
A(LARM),
IG(nore)
Address 1 ... 63 63 Slave address on DeviceNet
Baud rate 125k, 250k, 500k 125k DeviceNet baud rate
Configuration FIXED-1, FIXED-1 Lets you set construction and

FIXED-2, meaning of user data
NO_PARA_ID,
PARA_ID
DVN byte High-Low Low-High Byte sequence within a data
sequence Low-High word
DVN word I:std / L:std I:std / Word sequence within a data
sequence I:swp / L:std L:std double word, separately
I:std / L:swp settable for floating point
I:swp / L:swp values I(EEE) and integer
values L(ONG)
Note
Any change to a grey-marked parameter resets the field connection, i.e. the slave
is excluded from user data exchange for approx. 4 sec.
3.5 Settings on DeviceNet Master

Electronic Data Sheet (EDS)
The description file files (EDS_ABIC_DEV_V_1_02.EDS/Intecont.EDS) can be found

at the Schenck Process GmbH service side (www.schenck-process.de, path: Service-
Download-Bus systems-DeviceNet). The download file includes a Readme with
detailed information.
Independent of configuration, always 32 bytes are transmitted per data direction
(produced connection size = consumed connection size = 32).

DeviceNet

If you have selected one of the fieldbuses, any malfunction is reported by event
message "Communication Host (S9) provided that this message is assigned to an
event class other than IG(NORE). The message is output both on display and on
EasyServe. If only the display is available, read the next two items. The EasyServe, if
present, provides further information on fault diagnosis.

The event message is designed to report any error concerning the fieldbus module:
Different baud rate on Master and scale
Cable connection between fieldbus module and base board faulty.
Fieldbus cable defective or improperly connected. For proper connection, see
“Fieldbus Hardware”.
Fieldbus hardware bus termination is not (or various times) available. Check
resistors on module (supplied state: "Not activated") and on bus connectors. For
details, see “Fieldbus Hardware”.
Selected protocol type does not correspond to the extension board. Change
parameterisation or replace module.
Timeout parameter value too small. Change scale parameterisation.
Inadmissible ID detected in Master --> scale message (only use bold-printed IDs).
All preset IDs in message from host system have zero value (communication
between Master-CPU and communication processor (CP) failed). Minimum one
preset ID must be unequal to zero, or – in FIXED mode – the release bit must be
set.
The representation of cyclic user data is the same for all protocols. For details, see
“Fieldbus Data” chapter.
3.7 DeviceNet Module (VCB020V)

To provide an interface to CAN bus using the DeviceNet protocol, you can attach the
module to the INTECONT cover.
Bus termination
Activate the bus terminals resistors on first and the last stations on bus. To do so,
set the plug-in jumper W160 on board to position 1-2. On standard, the resistors
are not activated (position 2-3).
Baud rate and bus address are set via parameter.

DeviceNet
X20
Set jumper W100 (Power supply source) to position 2-3.
Connector assignment
Pin Signal X20

1 V-
2 CAN_L
3 screening
4 CAN_H
5 V+
Characteristics
Isolation optocouplers
Connectors Phoenix MSTB 5 max. 2.5mm²
Phoenix MSTB 5 max. 1.5mm²

DeviceNet specification Version 2.0 (ODVA)
Bosch CAN specification Version 2.0, Sept. 1991
DeviceNet user organisation www.odva.com
HMS documentation on Anybus-IC www.hms-networks.com
BVH2098AA EASYSERVE

Modbus
4 Modbus
The present chapter describes the interfacing of the INTECONT Modbus slave with a
Modbus Master assembly and describes the Modbus in the form activated by the
MODBUS selection. The previous version of the INTECONT-compatible Modbus
(MODCOMP) is described in Manual FH525.
Described is the functionality of the Modbus module, the data exchange between
Modbus Master and INTECONT, diagnosis and troubleshooting. The hardware of the
Modbus module is described at the end of this chapter.

Prepare the hardware as described in the “Fieldbus Hardware” chapter.
Determine data to be transferred using the data IDs (see “Fieldbus Data”).
Set INTECONT parameters “Slave Address” and “Data Format”.
Start communication through Master.
4.2 Modbus Module Functionality
Connection via RS422 (4-wire bus) or RS485 (2-wire bus, also called J-Bus).
Select physical properties by parameter setting. Connection via RS232 is also
possible.
Cyclic user data exchange with Master
Easy parameterisation of VSS021V using base unit control station or EasyServe
tool
Modbus mode: RTU
4.3 Data Format

Transmission starts with MSB. Setpoints and measurement values can be transmitted
both in the IEEE float format (IEEE754, 32 bits) and in the integer format. The integer
format readies a 16-bit word whose resolution can be set in the range of 0 ....
MAXINCREMENTS. The maximum resolution is 215 increments. Integer and IEEE
format are addressed using different data addresses.
For every parameter, the IEEE format can be swapped wordwise. All control
information and statusses are represented in the form of a binary signal using the 8
data bits of each character. In addition, all control and status information can be
treated as single bit information.

Modbus
4.4 Function Codes (FC)

The table below lists the codes used and explains their meanings.
FC [dec] Meaning
1 Bitwise re-reading of control information (one/multiple bits)
2 Bitwise reading of status information (one/multiple bits)
3 Wordwise (re)reading of setpoints, measurement values, LONG values and
parameters (one/multiple words)
4 Wordwise reading of status information (one/multiple words)
5 Bitwise (re)setting of control information (always 1 bit)
6 Wordwise writing of control bits or setpoints (always 1 data word)
8 Diagnosis (only sub-codes 0 and 1)
15 Bitwise writing of control information (one/multiple bits)
16 Wordwise writing of commands (one/multiple data words)
23 Reading and writing of multiple data words in one cycle. This function code may
be used in all cases where FC3 or FC16 can be used.
4.5 Transmission Protection

The characters are protected by a parity bit (see MODBUS specification).
The messages are protected by check sum (CRC16) (see MODBUS specification).
The MODBUS specification determines the reaction on transmission errors (see 2-1
EXCEPTION RESPONSE).
4.6 Error Codes

Used are only error codes 01 to 03. Upon CRC error no response is sent.
All errors described below are comprised in device in the form of general error
message ‘Communication Host’. The message includes the timeout.
Error code Meaning

1 Station does not support requested function (FC).
2 Faulty data address
ID or SC out of range
Data offset + length excessive
3 Wrong data type
Wrong data with FC 5 (admissible: 0xff00 and 0x0000)
Data length < 0
Requested length excessive
Data address with IEEE or INT32 values odd
4.7 Station Addresses

Each scale receives a slave address starting from 1 in rising sequence. In the
following text, the highest settable address is called MAXSLAVE. The address is set
on scale or EasyServe in the dialog mode. MAXSLAVE has value 254. Address 0 is
the boradcast address. In this case, the slaves do not return any response.

Modbus
4.8 User Data
4.8.1 Process Values

Every cyclic data segment includes values of the same type. The addresses of the
data within a segment are added in continuous succession. The data of a segment
can be read or written using a message.
4.8.2 Parameters
All parameters can be read and written. In contrast to cyclic values, only one
parameter per message can be processed. Transmission requires the parameter ID
unique throughout the system. For some important parameters of wagon type VLW,
these IDs can be found in the list of fieldbus data. For the residual parameters,
EasyServe can create a list including the IDs.
Note: Menu item “EXTRAS-OPTIONS-PARAMETER-Print SysID” lets you activate
printout of the IDs to be used for data address of the Modbus protocol. Please note
that the modification of the selection parameters requires special knowledge. Floating
point and/or integer values can be read and written without any problems. The data
formats correspond to those of the cyclic values.
4.9 Cyclic Data Exchange Via Modbus

Use of function codes in transmission of cyclic data
FC Data segment Data direction Smallest data Data format
unit
P = Preset
R = Read
R = Re-read
15 Command P bit
5 Command P bit
1 Command R bit
16 Command P word
6 Command P word
3 Command R word
16 Setpoints P double word IEEE, normal or swapped wordwise

16 Setpoints P word Integer format
6 Setpoints P word Integer format
3 Setpoints R (double) word IEEE, normal or swapped wordwise,
integer format
2 STATUS R bit
4 STATUS R word
3 STATUS R word
3 MEAS. VALUES R word Integer format

4 MEAS. VALUES R word Integer format
3 MEAS. VALUES R double word IEEE, normal or swapped wordwise

4 MEAS. VALUES R double word IEEE, normal or swapped wordwise
3 LONG R double word INT32

4 LONG R double word INT32

Modbus
Note:
In many cases, the host system must add a so-called segment address (depending on
function code) to the described data address. Furthermore, the data address must be
incremented by 1 since the Modbus protocol’s register addresses start from 1.
So the data address is configured like this:
Data address = segment address + INTECONTaddress + 1.
4.10 Sample Messages

The following lines show the construction of the Modbus messages. The first column
represents the message from bus Master to scale; the second, the scale response.
Floating point values are represented in the form of an (unswapped) IEEE number.
Data to scale Scale response Meaning

01 05 0140 ff00 8C12 01 05 0140 ff00 8C12 Start scale (single-bit command)
01 05 0141 ff00 DDD2 01 05 0141 ff00 DDD2 Stop scale (single-bit command)
01 06 0140 0040 8812 01 06 0140 0040 8812 Reset counter 1 (preset word)
01 03 02F0 0004 4582 01 03 08 xx xx xx xx xx xx xx xx Read 4 words of status information
cc cc xx = data, cc = CRC16
01 03 1082 0002 60E3 01 03 04 42C8 0000 6FB5 Read parameter (nominal feed rate,
ID=1082 (hex), value = 100))
01 10 1082 0002 04 4323 5678 01 10 1082 0002 E520 Write parameter (value =163.34)
6C1A
4.11 Settings on Modbus Slave (INTECONT)

For parameterisation, you can use the Operator Panel or the EasyServe tool.
The parameter description holds for either unit.
Protocol type all fieldbus protocols NO Select protocol: here

Modbus
monitoring.
interface is not activated.
Communication W2 (Warning 2), IG Class of communication
Host W1 (Warning 1), error
A(LARM),
IG(nore)
Modbus address 1 ... 254 1 Slave address on Modbus
Modbus 1 ... 32767 4096 Indicates maximum number

resolution of increments of value in
analog, or integer, format.
Modbus IEEE I:std / L:std I:std / Determines the word
format I:swp / L:std L:std sequence for transmission
I:std / L:swp of measurement values in
I:swp / L:swp the I(EEE)/L(ONG) format.
Modbus baud 9.6 19.2 38.4 kBaud 9.6 kBaud Baud rate
rate
Modbus data 8-O-1 8-O-1 Modbus normally uses an
format 8-E-1 11-bit character frame, e.g.
8-N-2 8-O-1
8-N-1 (10-bit frame) 1 start bit, 8 data bits, odd
parity, 1 stop bit

Modbus
Note
Used for message end identification, the Modbus idle time is defined with 3.5
characters as a function of selected baud rate, and corresponds to approx. 4
milliseconds at 9600 baud. For adaptation to specific device configurations, this time
can be set in the EasyServe block. The setting acts both on EasyServe and fieldbus
interfaces.
Selected baud rate Modbus idle time in milliseconds

9600 4
19200 2
38400 1
When operating the EasyServe interface using a radio converter, the times stated in
table may be longer.
4.12 Settings on Modbus Master

If data from various segments (see Fieldbus Data) are used, every segment needs
at least one message.
Set correct byte sequence with values in the IEEE and LONG formats.
Maximum admissible message length is 256 bytes including header and trailer
bytes.

If you have activated (selected) one of the eligible fieldbus modules, any malfunction
is reported by event message "Host Data Link (S9) provided that message is assigned
an event class other than IG(NORE). Message is output on display and EasyServe. If
only the display is available, continue reading from next chapter. The EasyServe tool
provides further information on error diagnosis.
4.13.1 Event Message “Host Data Link” S9

Designed as general message for any fieldbus connection faults, this message reports
the following errors:
Different baud rates on Master and scale
Cable connection between fieldbus module and base board faulty
Fieldbus cable defective or improperly connected; for proper connection, see
“Fieldbus Hardware“ item.
Bus termination absent or present multiple times. Check the jumpers in the
fieldbus connectors on the module. For details, see “Fieldbus Hardware“ item.
Selected protocol type does not correspond to add-on card. Change
parameterization or exchange module.
Timeout parameter value too small. Change scale parameterization.
Inadmissible ID detected in Master -> scale message.
See also “Error Codes“ item.

The representation of cyclic user data for all protocols is explained at the „Fieldbus
Data“ item.

Modbus
4.14 Serial Bus Module (VSS021V)

To provide a serial interface to the fieldbus Master, you can attach the module to the
INTECONT cover.
Bus termination
The bus termination is realized using jumpers in the fieldbus connectors.

This ensures that the termination is preserved upon replacement of card.
Am Busmaster sollten Sie einen 220 Ohm-Widerstand zur Terminierung
verwenden.
Baud rate, bus address, interface physics, data format
All values are set via parameters. Depending on selected physics,

different connections must be realized on fieldbus connector (see below).
X20
Connector assignment X20
Pin No. RS 232 RS 422 RS 485

1 GND GND GND
2 TX TX- -
3 RX RX- RX-/TX-
4 - RX+ RX+/TX+
5 - TX+ -
6 - Bus termination Bus termination
7 - Bus termination Bus termination

Modbus
Jumpers for interface physics and bus termination with RS485 (2-wire)
Bus terminal jumpers with RS422 (4-wire)
Characteristics
Isolation Optocouplers
Connectors Phoenix MSTB 5 max. 1.5mm²

Modicon Modbus Protocol Reference Guide PI-MBUS-300 Rev. J/1996
BVH2098AA EASYSERVE

Modbus-TCP/IP
5 Modbus-TCP/IP
This chapter describes the functionality of INTECONT used as server on Ethernet.
In detail:
Ethernet module (“Ethernet Bus Module VET020V“ item)
Ethernet module configuration (determine characteristics and assign station
addresses)
FIELDBUS mode: Data exchange between Ethernet client and INTECONT via
Modbus/TCP
WEB SERVER mode: Preparation and call of a WEB page
Diagnosis and troubleshooting.
NOTE
In addition to the Normal mode, the following items describe the Expert mode of the
MultiServerTools PC software. Changeover to Expert mode takes place upon program
start by way of an additional parameter you can request using the service telephone
numbers. The individual items include information on the modes in which the
individual functions can be used.
5.1 Definitions
Client
Refers to the computer or application using the server’s capabilities.
In the present documentation, the term “client” normally refers to a PC or control
system using the data and services of the Ethernet interface module (VET010V,
sometimes also called “Beck chip“) or displaying the data of the latter. Single PC
applications, e.g. FTP, Internet Explorer, Telnet can enter into a client-server
relationship using the relevant VET010V server programs.
Server
Normally refers to the general VET010V applications, e.g. the WEB server readies its
services to the Internet Explorer, and the FTP server communicates with the
corresponding client on PC in order to load (multiserver) programs and configuration
data into VET010V.
MultiServer
Refers to the application program (Multisrv.exe) executed on VET010V. The term
MULTI suggests that multiple servers are running quasi in parallel and that, in case of
the fieldbus server, multiple channels can be served at the same time.
BIOS/Firmware
Refers to the basic software of Messrs. BECK, comprising real-time operating system
and some basic applications, e.g. FTP server, Telnet, TCP/IP software.
MultiServer Tools
Refers to the PC program denoted VPC28000-xx xxxx.
The MultiServer Scanner program module assists the operator wishing to use
INTECONT with Ethernet as WEB Server in quick selection of device and display of
Web pages.
The MultiServer Loader module helps the commissioner load new software, create
data, edit web pages, etc.
The MultiServer Mastersimulator module lets you test fieldbus channels.

Modbus-TCP/IP
Modbus/TCP
Uses the TCP/IP standard for data transmission; the application data present
themselves in the form of a Modbus RTU frame.

Prepare hardware as described at “Ethernet Bus Module VET020V“ item.
Activate protocol type Modbus-TCP on INTECONT.
Parameterize Ethernet address on module.
In FIELDBUS mode: Determine data to be transferred – data IDs required (s.
“Fieldbus Data“ item).
Start communication through Master (FIELDBUS mode).
Call WEB page in WEB SERVER mode.
5.3 Ethernet Module Functions
Connect module using RJ45 connector.

In FIELDBUS mode, server can exchange data with up to 3 clients. If the
EasyServe commissioning tool is used, it can occupy one of the 3 eligible
channels if interfacing is done via network. Data are sent in the form of
Modbus(RTU)/TCP packages, and/or expected from outside in this form. The
functionality is detailed below.
Several easy-to-configure, dynamic WEB page indicates optional INTECONT
process values or parameters. Values are standard represented in the XML
format. A user-specific style sheet lets you realize any desired form of
representation. For browsers incapable of interpreting XML data, conversion into
standard HTML can be selection optionally.
Easy parameterization of VET020V using base unit control station or EasyServe
diagnostic tool.
The MultiServerTools PC program supports the user during commissioning and
in normal WEB SERVER mode.

Modbus-TCP/IP
Overview of MultiServer functions

Modbus-TCP/IP
5.4 Configuring Ethernet Module
The Ethernet module is equipped with an independent processor system needing a

current firmware and configuration files for its operation. Every module comes with a
set of files enabling the device to be instantly used as TCP server. This applies to its
use as FIELDBUS or WEB server. The “MultiServerTools.EXE“ program lets you
change firmware and configuration data. The fieldbus module can be used only if all
downloads are performed using this program. The program functions are detailed
below. The end user, or operator, can modify certain files.
5.4.1 MultiServerTools.EXE Program
This program consists of various subroutines. The two most important modules are
depicted below (applicable to Expert mode).
The “Download Options“, “Diagnosis“, “Telnet“ and “Webserver“ frames are visible
only in Expert mode. In Normal mode, the depicted settings apply.

Modbus-TCP/IP
5.4.1.1 MultiServer Scanner

The right window shows the MultiServerScanner used for acquisition of all Ethernet
modules available in network. All modules responding to search are entered into a list,
and let you select a device and start the Web browser using the right mouse button.
The start page displayed lets you select a web page and view the cyclically refreshed
values. Key F5 (Update) lets you add new devices to list. Further functions can be
called only after password input.
For every device, the list offers the following entries:
SNr: serial number of Ethernet chip imprinted on side of chip
Device Name: can be changed by the commissioning engineer before loading the
application software. Its length is limited to 20 digits.
IP Name: assigned by the system administrator and firmly linked with the IP
address. If no IP name has been assigned, display shows the IP address.
Network parameters: IP address, net mask and gateway address
Alternatively or parallely, the Chip tool of Messrs. Beck can be used for scanner.
5.4.1.2 MultiServer Loader

The MultiServer Loader subroutine lets you add some commissioning and service
functions to the scanner. Start program using the “Start MultiServer Loader“ button
and enter password “network“.
This subroutine prompts for input all parameters required to perform a download:
Language used in all WEB server displays

Device family used
If necessary, special scale type as a function of device family
Options
Tick checkbox PDA, operate web server in HTML mode, and lines in table
fade out and spaces are minimized. Select small font and codes in your
configuration file, and you can operate web server also on a PDA.
In XML mode, adapt style sheet file to produce the desired form of
representation.
Diagnostics, however, this function should be actived only at the time of
commissioning. To activate diagnostics, set parameter TELNET to Enable.
Checkboxes designed to (de)activate certain features, e.g.
TELNET: should be disabled in normal mode (see above)
WEB server: can be deactivated if exclusively fieldbus channels are
used
Device name used to identify device; max. 20 digits.
IP address used as unique address of Ethernet module in network.
Note:
Go to scanner module, click on line indicating name and IP address of desired device,
and all values are transferred to the Loader module. If required, values can be
adjusted before next download.
To be able to start a download, enter at least the IP address. The Download

Application button lets you start transfer of desired files. Active transmission is
reported by the hourglass pointer and displayed in the program status line. If transfer
is complete, connection terminates automatically and all inputs remain stored, so that
a further device with the same settings can be loaded. All status messages are

Modbus-TCP/IP
recorded by program and can be viewed in service menu at the “Show FTPLogFile“
entry.
TOOLS Menu
This menu item comprises further useful tools for WEB server and fieldbus mode:
MultiServer Mastersimulator: lets you check fieldbus channels for proper
functioning. All requisite parameters are preset by the Loader module.
Internet Explorer: lets you try to start Microsoft Internet Explorer using preset
address
Telnet: lets you start TeraTerm program using TELNET setting and selected IP
address
Upload: lets you start browser as FTP client. The drag & drop function lets you
shift or copy selected files from module to PC.
Note:
In Normal mode, only menu item “Internet Explorer“ is visible.
You can also reach the Tools menu using the right mouse button.
The Tools menu is also available in the Scanner module and can be reached using
the right mouse button. If started via Scanner module, the address of the line
selected last is valid.
SERVICE Menu
The SERVICE menu offers some commissioning aids that are but seldom used.
In Normal mode, only menu items “Edit Configuration“ and “Show FTP LogFile“ are
visible.
Change Network Parameters: lets you preset IP address, net mask and
gateway address of the Ethernet module. However, this menu item should be
used only if the chip on the Ethernet module is loaded with the use of a program
for the very first time.
Load BIOS: lets you load a new firmware. This should be done only after prior
consulting with Schenck. After every BIOS update, the application software must
be reloaded, and complete device has to be reset.
Edit Configuration: lets you edit the Web pages. Display shows the directory
tree as created by the setup program. Select file, and edit using the editor.
The editor’s SAVE function lets you store the changed file in the same location
on directory. The SAVE AS function lets you add a new file in the same or
another location on the directory tree.
Please note that changes in the INTECONT standard directory can produce
errors in the ACTUAL VALUES display. Preferably use an existing file as pattern
and store the changed file in the CUSTOMER_INTECONT directory using the
SAVE AS function. The name of the new file should start with “CU_“ (for

Modbus-TCP/IP
Customer) and meet the DOS name convention “8+3“. This also ensures that
after reloading of application software the newly added file is entered into the
WEB server’s start page and can be started from there via mouse click.
Show FTPLogFile: lets you check loading process (s. MultiServer Loader)
Note
The freshly loaded Multiserver version is active only after reset (power-up) of
INTECONT. If Web server is active during download, update (F5 button) may be
necessary.
For more information on WEB server files, see relevant item of the present
chapter.
5.4.1.3 MultiServer Mastersimulator

The Mastersimulator help system lets you check fieldbus channels for proper
functioning. Used in place of a PC or control system as Modbus TCP client, the
simulator lets you create Modbus TCP messages (Port 502) and display the response
of the test unit in hexadecimal fashion.
Activate proper device family and IP address in the Loader module before calling
Mastersimulator, and simulator starts operating using the device-specific settings.
Simply establish connection using the OPEN button, and data transfer starts
immediately. The following test functions are available, for you to choose:
Read FC 3
Lets you poll status and measurement values using the data start address on the right
(see Data Lists item) and Modbus function code 3.
Write FC 16
Lets you transmit one or multiple preset values to scale. This command can be used
both for setpoints and commands. The length information to be entered into message
is computed automatically from entered preset values.
RW FC 23
Function code 23 lets you write and read values in a cycle. The input fields correspond
to those of FC3 and 16.
Write FC 5
Function code 5 lets you set or delete single command bits.
Note
You can specify a cycle time on the upper right (default: 1000 milliseconds).
The function selected last is executed using the specified cycle time.
If you wish to send off single messages, set cycle time to ZERO.
The two buttons on the lower left let you translate the read values from
hexadecimal format into normal clear text. However, this works only for the
specified data segments ‘measurement values = data address 750hex ff., as well as
for status ID 02F0 most frequently used.
Tick checkbox “Simulate Configuration Tool“, and you can simulate the EasyServe
behaviour on one of the eligible fieldbus channels.
You can open the Mastersimulator window up to three times corresponding to the
number of eligible fieldbus channels.

Modbus-TCP/IP
5.4.1.4 Setup
The MultiServer Tools program starts from a fixed directory structure. The latter is
determined by the setup program and must not be changed in order to ensure peak
functionality of Loader module and commissioning tools.
Depending on operating system version and selected language, the paths are
selected so that all invariable subroutines are installed using the program path preset
by Microsoft (CSIDL_PROGRAM_FILES); and all variable files, using the All Users
application files path (CSIDL_COMMON_APPDATA ). For clear orientation, use the
HELP INFO of the MultiServer tool to view the paths.
5.4.2 Parameterizing INTECONT
Your INTECONT can be parameterized using the INTECONT control unit or the
EasyServe tool.
The parameter description holds for either system.
Parameter Value Range Default Explanation
Protocol Type Any fieldbus NO Select protocol: here TCP

protocol
Host Timeout 5 ... 300 s 10 s Serves for interface monitoring.
Values less than 5 are limited to
the minimum value.
Host Data Link W2 (Warning 2), IG Class of communication error
W1 (Warning 1),
A(LARM),
IG(nore)
WEB Coding HTML, XML XML Determines type of WEB page
coding. If XML is selected, data in
browser are represented by the
style sheet.
DHCP NO NO The IP address is assigned on
device or configuration tool
(EasyServe).

Modbus-TCP/IP
Parameter Value Range Default Explanation
IP Address 1 0 – 255 192 Lets you key in IP address
Net mask 1 0 – 255 255 Determines sub-net mask
Gateway 1 0 – 255 192 Determines standard gateway

address
address
address
address
Byte sequence High-Low High- Swaps byte sequence in every user
Low-High Low data word
Word sequence I:std / L:std I:std / Determines the word sequence
I:swp / L:std L:std during transmission of
I:std / L:swp measurement values in the
I:swp / L:swp I(EEE)-/L(ONG) format. Also swaps
analog preset values.
Configuration FIXED1, FIXED1 Not used with Modbus/TCP
FIXED2,
NO_PARA_ID,
PARA_ID
Note
If you operate your INTECONT units on a local sub-network with specific network
card, we suggest to set the PC network adapter to the following values:
IP address: 192.168.240.254
Net mask: 255.255.255.0
Gateway: 192.168.240.0
INTECONT 1-n: 192.168.240.x wo x=1-n
Always use unique IP addresses. Ask your system administrator for available
addresses.

Modbus-TCP/IP
5.4.3 Checking Station Addresses
The network parameterization described above can be checked using the Scanner
module or the CHIP tool of Messrs. BECK accessible using program path …\ Modbus-
TCP\chiptool\chiptool.exe.
Scanner and Chip tool acquire all BECK chips located in network via UDP broadcast
and supply current settings in tabulated form.
You can also check network parameters using the PING command available on any
PC, e.g. “ping 192.168.240.1”
If check is successful, reponse time of the final unit is displayed.

Modbus-TCP/IP
5.5 Fieldbus Mode
In FIELDBUS mode, INTECONT behaves like a Modbus/TCP server in accordance

with standard “OPEN MODBUS/TCP SPECIFICATION, Release 1.0, 29 March 1999“
and masters all function codes of Classes 1 and 2 (save FC7) as well as the most
significant codes of Class 2 (FC15 and 23).
Data representation is totally oriented to the Modbus standard. The TCP safety layer
performs the function of the check sum (CRC16) of the Modbus message. Of the 6-
byte message header defined in the OPEN MODBUS standard, INTECONT only uses
the 6th byte to transfer the data length. The residual bytes are returned in the response
in ratio 1:1.
To enable later extensions, these header bytes (1-5) should not be used; set them to
ZERO.
5.5.1 Station Addresses
In the Ethernet network, all stations are clearly identified by their IP addresses.
Therefore the Modbus slave address can always be set to value 1.
5.5.2 Function Codes (FC)
The list below explains the codes used:
FC [dec] Meaning
1 Bitwise re-reading of control information (one/multiple bits)
2 Bitwise re-reading of status information (one/multiple bits)
3 Wordwise (re)reading of setpoints, measurement, LONG and parameter
values (one/multiple words)
4 Wordwise reading of status information (one/multiple words)
5 Bitwise (re)setting of control information (always 1 bit)
6 Wordwise writing of control bits or setpoints (always 1 data word)
8 Diagnosis (sub-codes 0 and 1 only)
15 Bitwise writing of control information (one/(multiple bits)
16 Wordwise writing of commands (one/multiple data words)
23 Wordwise writing and simultaneous reading of data (one/multiple data
words)
5.5.3 Transmission Protection
With Modbus/TCP, the transmission is protected by the safety measures of the TCP
layer.

Modbus-TCP/IP
5.5.4 Error Codes
Only error codes 01 to 03 are used. Upon CRC error, no reponse is sent.
All errors described below are comprised in system in the form of general error
message “Data Link Host“. This message includes the timeout.
Error Code Meaning

1 Station does not support requested function (FC).
2 Wrong data address
ID or SC out of range
Data offset + length excessive
3 Wrong data type
Wrong data with FC 5 (admissible: 0xff00 and 0x0000)
Data length < 0
Requested length exceeded
Data address with IEEE or INT32 values odd
5.5.5 Data Formats
Transmission starts with MSB. Setpoints and measurement values are transferred in
the IEEE float format (IEEE754, 32 bits). All control information and statusses are
represented in form of a binary signal using the 8 data bits of each character. In
addition, all control and status information can be treated as single bit information.
5.5.6 Process Values
Every cyclic data segment includes values of the same type. The addresses of the
data within a segment are consecutively added. The data of a segment can be read or
written using a single message.
5.5.7 Parameters
All parameters can be read and written. In contrast to cyclic values, however, only one
parameter per message can be processed. Transmission requires the parameter ID
unique throughout the system. For some significant parameters of scale type VLW,
these IDs can be found in the list of fieldbus data. For residual parameters, EasyServe
can prepare a list complete with IDs.
Note: Menu item “EXTRAS-OPTIONS-PARAMETERS-Print SysID” lets you activate
printout of IDs to be used for data address of the Modbus protocol. Please note that
special knowledge is required to edit the selection parameters. Floating point and/or
integer values can be read and written without any problems. The data formats
correspond to those of the cyclic values.
Note:
Parameters preset via fieldbus are accepted only if parameter mode is not active at
the same time.

Modbus-TCP/IP
5.5.8 Data Exchange Overview
Function Codes Used In Cyclic Data Transmission

FC Data Segment Data Direction Smallest Data Unit Data Format
P = Preset
L = Read
R = Re-read
15 Command P Bit
5 Command P Bit
1 Command RR Bit
16 Command P Word
6 Command P Word
3 Command RR Word
16 Setpoints P Double word IEEE

3 Setpoints RR Double word IEEE
2 STATUS R Bit
4 STATUS R Word
3 STATUS R Word
3 MEAS. VALUES R Double word IEEE

4 MEAS. VALUES R Double word IEEE
3 LONG R Double word INT32

4 LONG R Double word INT32
Note
In many cases, the host system must add a so-called segment address (depending
on function code) to the described data address. Furthermore, the data address must
be incremented by 1 since the Modbus protocol’s register addresses start from 1.
So the data address is configured like this:
Data address = segment address + INTECONTaddress + 1.

Modbus-TCP/IP
5.5.9 Message Samples
The following lines show the construction of the Modbus/TCP messages. The first
column represents the message from bus Master to scale; the second, the scale
response.
Data to scale Scale response Meaning
00 00 00 00 00 06 00 00 00 00 00 06 Start scale (single-bit command)
01 05 0140 ff00 01 05 0140 ff00
00 00 00 00 00 06 00 00 00 00 00 06 Stop scale (single-bit command)
01 05 0141 ff00 01 05 0141 ff00
00 00 00 00 00 06 00 00 00 00 00 06 Reset counter 1 (preset word)
01 06 0140 0040 01 06 0140 0040
00 00 00 00 00 06 00 00 00 00 00 0B Read 4 words of status information
01 03 02F0 0004 01 03 08 xx xx xx xx xx xx xx xx xx = data, cc = CRC16
00 00 00 00 00 06 00 00 00 00 00 07 Read parameter (nominal feed rate,
01 03 1082 0002 01 03 04 42C8 0000
ID=1082 (hex), value = 100))
00 00 00 00 00 0B 00 00 00 00 00 06 Write parameter (value =163.34)
01 10 1082 0002 04 4323 5678 01 10 1082 0002
5.5.10 Settings on Modbus/TCP Master
If data from various segments are used (s. Fieldbus Data), every segment needs
at least one message.
Set correct byte sequence for values in the IEEE and LONG formats.
Maximum admissible message length is 256 bytes including header and trailor
bytes.
5.5.11 Diagnosis and Troubleshooting
If you have activated (selected) one of the eligible fieldbus modules, any malfunction
is reported by event message "Host Data Link (S9) provided that message is assigned
an event class other than IG(NORE). Message is output on display and EasyServe. If
only the display is available, continue reading from next chapter. The EasyServe tool
provides further information on error diagnosis.
Note
An internal communication fault (fieldbus card – INTECONT main board) produces a
timeout on fieldbus Master. To remove, restart your INTECONT.

Modbus-TCP/IP
Designed as general message for any fieldbus connection faults, this message reports
the following errors:
Cable connection between fieldbus module and base board faulty
Fieldbus cable defective or improperly connected; for proper connection, see
“Fieldbus Hardware“ item.
Selected protocol type does not correspond to add-on card. Change
parameterization or exchange module.
Timeout parameter value too small. Change scale parameterization.
Inadmissible ID (data address) detected in Master -> scale message.
See also “Error Codes“ and „Interface Configuration“ items.
The representation of cyclic user data for all protocols is explained at the “Fieldbus
Data“ item.
Note
To be able to watch the data exchange between a fieldbus client and the Ethernet
module, perform a new download using the following Loader settings:
When download is complete, start Telnet. The Telnet window lets you see data
exchanged via fieldbus and store them in a LOG file (see Telnet: File Menu).
Checkbox “Other“ is reserved for internal outputs.
Tick checkbox “Log-File“, and you can record all connection attempts in a
Connect.log file on the Ethernet chip.
Outputs use the following form:
02.03.2004 08:27:55 Closing connection 0 192.168.240.254 Socket Descriptor 10

02.03.2004 08:27:56 Accecpt Connection 0 192.168.240.254 Socket Descriptor 11 Port 27916
02.03.2004 08:28:02 Closing connection 0 192.168.240.254 Socket Descriptor 11
02.03.2004 08:28:03 Accecpt Connection 0 192.168.240.254 Socket Descriptor 12 Port 28172

Modbus-TCP/IP
5.5.14 Interface Configuration
The Application Data directory offers for every scale type a configuration file named
TRANSFER.CFG (path …\CUSTOMER_xxx) that lets you effect the following settings:
Configure internal interface
Determine timeout for fieldbus interfaces
For every setting option, the file offers an individual section as shown below:
[SerialCommunication]
1=720,1712,1 ;Status
2=1872,1994,1 ;Measure1
3=2432,2478,1 ;Long
4=1996,2118,1 ;Measure2
[ClientConnection]
1=60 ; Timeout in sec
As a rule: space and comment lines (preceding semicolon) are admitted anywhere.
Interpreted is the part from equals sign through line end, or start of comment.
Line numbering must be kept as shown above.
Only the data supplied by the scale can influence configuration.
Configuring internal interface [SerialCommunication]
Every line comprises:
Line number = ID1, ID2, counter; comments, if necessary.
ID1 is the decimal code determining the start of a data segment.

Transmitted are all data from ID1 onward including the data
associated with ID1.
ID2 is the decimal code determining the end of a data segment.
Transmitted are all data through to ID2 including the data associated
with ID2.
For values of ID1 and ID2, see Data List item.
Counter The counter indicates how many times the values are exchanged
between scale and communication card VET020V.
Value 1 indicates that the message in question is transmitted in every
cycle; counter reading 10 means that data are updated in every 10th
cycle. Zero reading cuts off transmission; maximum counter reading is
255. A cycle normally comprises all messages stated in the above
example. If required, a parameter message is added in every cycle.
The cycle time is thus determined by transmission time = length of
messages at a constant rate of 38400 baud and the processing time
within the two communication partners.
The default setting has been selected so that almost any data a scale
can supply are refreshed in every cycle.
Internal sequences require the following conditions to be observed upon configuration:

Line 1: IDs 720 and 752 always set to active
Line 3: ID 2466 always set to active
Never deactivate the two measurement value messages at the same time.
Please bear in mind that this configuration influences both webpage and fieldbus
data.

Modbus-TCP/IP
Configuring external interface [ClientConnection]
A common timeout value can be assigned to all fieldbus interfaces.

Value range is from 1 second to 8 hours; input is always in seconds.
Within set timeout period, a response in form of a valid ModbusTCP/IP package is
expected. If the client does not respond within set timeout, the respective channel
closes automatically. The function code the client uses to report is irrelevant. Before
next user data exchange, new connection setup is required. This procedure ensures
that connections inadvertently terminated or no longer used do not block the server at
a later time.
Note:
The TIMEOUT parameter value on scale only determines the period after which
external timeouts are indicated. In addition, scale uses this value to monitor the
internal communication beween scale and VET020V.
Assigning access rights
Every connected fieldbus client has the right to read server data. By definition, the first
client sending a valid presettings package is granted the right to write. For assignment
of access rights, the data included in presettings package are irrelevant. Once the
access right is assigned, write attempts of residual cients are responded with error
package ILLEGAL FUNCTION: Code 01. Function code 23 (write and read in a cycle)
behaves so that only the reading function is executed. The right to write can be
reassigned only after abort of connection.
Monitoring fieldbus channels
When fieldbus channels are monitored for error message and safety cut-off of scale,
only the channel with WRITE rights is monitored. Communication errors are displayed
only for this very channel. If the event class for “Communication Error Host“ is set to
ALARM, scale cuts off and all static command bits go to the safe state.
Exception: if no fieldbus channel has been granted presetting rights yet and fieldbus
is already activated, “Communication Error Host“ is displayed. In this case, error
message can be suppressed only by setting the event class to IGNORE.
According to this monitoring strategy, EasyServe is not considered as fieldbus client.

To EasyServe, the special settings of the relevant parameter block apply, and the
rules for log-on and log–out are the same as defined for a serial interface.

Modbus-TCP/IP
5.6 WEB SERVER Mode
The WEB SERVER mode uses the HTTP protocol. Using a standard browser (e.g.
Microsoft Internet Explorer), optional INTECONT process data and parameters can
be displayed.
5.6.1 WEB Server Files
The MultiServer Loader program automatically loads the specific device files onto the
Ethernet module. These files can be started from the start page using the references.
All INTECONT standard files are stored write-protected in the
“…\Modbus-TCP\Conti\Intecont\…“ directory.
To ensure peak functionality of your system, never change these files. If you wish to
create further files (WEB pages), use the CUSTOMER_INTECONT directory. To this
directory, the following rules apply:
Ensure that all names of user-defined configuration files designed to appear as links
on the device start page start with CU_ (CUstomer). The residual 5 name digits can
be assigned at will (e.g. CU_STAT1.TXT). File extension TXT is a must.
Stylesheet file DATA.XSL ensures desired representation of values provided that
WEB-CODING parameter is set to XML. To change the form of data representation,
create a stylesheet file using the name of the configuration file and add data
extension XSL. If no special stylesheet file is available, standard stylesheet
DATA.XSL is used. Store stylesheet file on the Customer_INTECONT directory.
For construction of configuration files, see separate item.
5.6.2 Start Page
If all files are loaded and the IP address has been entered into the brower’s address
field, e.g. http://192.168.240.11, start page is displayed and comprises:
in 2nd line: information assigned by the commissioner, i.e. device name, device
family, designation of WEB page (common or scale-type specific page, e.g. VDB)
reference to actual values corresponding to the input in line 2
if necessary, reference to user-defined WEB pages (smaller letters, starting with
CU_)
reference to chip configuration page
link to information page, display of current program version and settings at the
time of download

Modbus-TCP/IP
Sample start page
5.6.3 Actual Value Display
Sample dynamic WEB page

Modbus-TCP/IP
5.6.4 WEB Server Call Conventions
The start page already references the standard and user-defined configuration files.
To be able to use the additional capabilities of the WEB server, the present item
describes the manual browser inputs.
The following codes are used:
DCVxxyy.txt scale-type specific configuration file

CU_xxxxx.txt user-specific configuration file
Datax.txt optional configuration file
NoXSL argument used to read the mere XML data of scale via HTTP protocol.
Data are supplied once-only / call and can be used, for instance, to
further process data using another program. For construction of return
files, see “Representation of XML Data” item.
Call without arguments IP/data (data refers to the point of entry into the CGI
table and is therefore invariable).
Standard call implicitly searches for scale-type specific
configuration file DCVxxyy.TXT and tries to represent
data using stylesheet file DATA.XSL (or HTML file).
Call with arguments Arguments are separated from one another using a
question mark:
IP/data?abc?NoXSL (argument means:
configuration file ”abc.txt”, no stylesheet)
The table below shows some examples for correct and faulty (grey) calls.
Call Configuration Stylesheet Comments

file (.txt) (.xsl)
IP/data?data CommonDE.txt Data.xsl Shows data from
CommonDE.txt file using
stylesheet data.xsl
(standard call)
IP/data?data ICVxxyy.txt Data.xsl Shows data from
DCVxxyy.txt file using
stylesheet data.xsl
(standard call with scale-
type specific data)
IP/data1?data1 CU_Data1.txt CU_Data1.xsl Displays data from
CU_Data1.txt file using
user-specific stylesheet
CU_Data1.xsl. Files are
loaded from
CUSTOMER_INTECONT
directory
IP/data?data1?NoXSL Data1.txt -- No stylesheet is used.
XML raw data are sent to
browser.
IP/NoXSL Inadmissible call CGI
input not available
IP/Data?vdb Inadmissible; CGI input
case-sensitive!
IP/data?vdb?NOXSL Inadmissible; NoXSL case-
sensitive!
IP/data?NoXSL Expected result not
supplied. NoXSL can be
used as second argument.
only. Display: Data.txt with
Data.xsl

Modbus-TCP/IP
Note:
Abort cyclic browser outputs by (repeated) operation of ESC key.
Key F5 (Update) lets you resume cyclic processing.
Shortcut ALT-Pos1 lets you go to the browser start page.
Please note that browser stores some files in the TEMPORARY INTERNET
FILES directory. In case of doubt, delete these files before going on.
The names of configuration and stylesheet files should meet the 8+3 name
convention.
5.6.5 Configuring WEB Page
To be able to represent a page, the browser needs to know

1. what data are to be represented
2. how these data shall be represented.
The information on point 1 are comprised in the DATA.TXT file. In the case of the
above page, the data are represented as follows (the line numbers are not included in
file; they merely serve as reference for the explanation of the contents):
Line No. Contents

1 ;ID, Type, Text, Unit, Precision
2 0001,HEAD,-,-,-
3 0001,HEAD,Name,Value,Unit
4 ,,,,
5 ,,,,
6 0752,BOOL,Scale On
7 0761,BOOL,Keyboard Mode
8 0763,BOOL,Simulation Active
9 0768,BOOL,Batch Selected
10 1552,EVENT,Most Significant Event
11 ,,,,
12 ,,,,
13 ;4226,FLOAT,Nominal Value,kg/h,2
14 1872,FLOAT,Feed Rate,kg/h,3
15 1942,FLOAT,Relative Feed Rate,%2
16 1880,FLOAT,Belt Load,kg/m,2
17 1944,FLOAT,Relative Belt Load,%,2
18 1884,FLOAT,Speed,m/s,1
19 1874,FLOAT,Totalizer 1,kg,3
22 1948,FLOAT,Batch Setpoint,kg,2
23 1898,FLOAT,Batch Res. Amount,kg,2
24 1896,FLOAT,Batch Feed Rate,kg,2
25 2052,FLOAT,Current Batch-No.
Changes made to this file automatically acquire all language-dependent and national
particularities (e.g. different units). If NON-SI units are used, adapt corresponding
parameter accordingly. If NON-SI is selected, the “t” unit is automatically converted
into Amercian short tons.

Modbus-TCP/IP
Explanations on data construction
General
All lines starting with a semicolon are comment lines.
Separate all line inputs by comma.
4 blank fields generate a separator line (e.g. lines 4 and 5).
Enter special characters see appendix:
The WEB server can process the following information:
Program automatically recognizes umlauts and special characters and translates
them into respective HTML codes.
ID(s) Value ID in IDs unmistakably identify an INTECONT process

INTECONT value or parameter.
(Data) type Enter one of the data Always use upper-case characters!
types below:
HEAD Identifies one the two table headlines
The 1st line contains 3 blank fields automatically
filled with program version and IP address.
The 2nd field can be optionally filled with a title text,
e.g. 0001,HEAD,-,Actual Data INTECONT 1,-
Determines that exactly one bit from the process

BOOL
image is to be viewed. The bit status is
represented by YES (bit=1) or NO (bit=0).
UINT8-H One data byte is displayed in hexadecimal

fashion.
UINT8 See above, however, decimal representation
UINT16-H One 16-Bit data word is displayed in hexadecimal

fashion.
UINT32-H Represents a 32-bit data word in hexadecimal fashion

(ID bold-appearing in data list)
FLOAT Corresponding value is shown in the floating

point format. The precision can be set separately (s.
Precision).
EVENT Event is represented in the form of:
group-number-class-status of acknowledgement,
e.g. S09 AL quit
EVTEXT Event message in clear text
PCONF Represents a parameter of the T_KONF type
PEVCLASS Represents a parameter of the T_ERROR type
PSELECT Represents a parameter of the T_TEXT type

Text Refers to the value
to follow
Unit Unit, if required
Precision Number of after- Acts only on floating point values
comma places

Modbus-TCP/IP
An XML file with current values is generated by interpretation of the DATA.TXT file.
Notes
The EVENT and EVTEXT data types are useful only in conjunction with ID 610
(hex.)
The PCONF, PEVCLASS and PSELECT types are reserved for the described
parameter types. The EasyServe menu item FILE-PRINT-PAGE VIEW lets you
find the required IDs in no time.
Depending on the input in the first headline of the configuration file, the Webserver
can display the IP address or the device name.
e.g.: display of ID address

0001,HEAD,-,Parameter INTECONT,IP
0001,HEAD,-,Parameter INTECONT,- compatible variant
e.g.: display of device name

0001,HEAD,-,Parameter INTECONT,Name
5.6.6 XML Data Representation
To display the XML file generated by the Ethernet module, you need a browser
capable of interpreting XML, e.g. IE5 plus option pack and IE6 (on standard). Other
potentially suitable browsers have not been explored. To update your Internet Explorer
Version 5, a service pack is available (s. “For Further Reading“ item).
To represent the data of the XML file, the browser still needs an XSL file (style sheet)
that informs him HOW the data are to be displayed. The file supplied readies the data
in form of a table. However, any other representation including backgrounds, etc. can
also be generated. If need be, load further graphics files into the Ethernet module.
The XML file printout below shows the keywords (TP, XVal, XNam and XDim) used to
prepare an own style sheet. The header lines feature HD in place of ID with data lines.
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="data.xsl"?>
<Values>
<HD No="0001" TP="HEAD" XVal="IP" XNam=" INTECONT PLUS VBW20600-01 2413"
XDim="192.168.240.3"> </HD>
<HD No="0001" TP="HEAD" XVal="Value" XNam="Name" XDim="Unit"> </HD>
<ID No=""> </ID>
<ID No=""> </ID>
<ID No="0752" TP="BOOL" XVal="NO" XNam="Scale On"> </ID>
<ID No="0761" TP="BOOL" XVal="NO" XNam="Keyboard Mode"> </ID>
<ID No="0763" TP="BOOL" XVal="NO" XNam="Simulation aktive"> </ID>
<ID No="0768" TP="BOOL" XVal="NO" XNam="Batch Selected"> </ID>
<ID No="1552" TP="BOOL" XVal=" " XNam="Most Significant Event"> </ID>
<ID No=""> </ID>
<ID No=""> </ID>
<ID No="1872" TP="FLOAT" XVal=" 48.56" XNam="Feedrate" XDim="kg/h"> </ID>
<ID No="1942" TP="FLOAT" XVal=" 0.00" XNam="Relative Feed Rate" XDim="%"> </ID>
<ID No="1880" TP="FLOAT" XVal=" 0.00" XNam="Belt Load" XDim="kg/m"> </ID>
<ID No="1944" TP="FLOAT" XVal=" 0.00" XNam="Relative Belt Load" XDim="%"> </ID>
<ID No="1884" TP="FLOAT" XVal=" 0.00" XNam="Speed" XDim="m/s"> </ID>
<ID No="1874" TP="FLOAT" XVal=" 0.00" XNam="Totalizer 1" XDim="kg"> </ID>
<ID No="1876" TP="FLOAT" XVal=" 0.00" XNam=" Totalizer 2" XDim="kg"> </ID>
<ID No="1878" TP="FLOAT" XVal=" 0.00" XNam=" Totalizer 3" XDim="kg"> </ID>
<ID No="1948" TP="FLOAT" XVal=" 0.00" XNam="Batch Setpoint" XDim="kg"> </ID>
<ID No="1898" TP="FLOAT" XVal=" 0.00" XNam="Batch Res. Amount" XDim="kg"> </ID>
<ID No="1896" TP="FLOAT" XVal=" 0.00" XNam="Batch Feed Rate" XDim="kg"> </ID>
<ID No="2052" TP="FLOAT" XVal=" 0.00" XNam="Current Batch-No." XDim=" "> </ID>
</Values>
Download the standard XSL file from the EtherNet module onto your PC via UPLOAD
command.

Modbus-TCP/IP
5.6.7 HTML Data Representation
While XML data and their representation are separate and processing takes place in
the browser, a HTML page is completely generated in module and only displayed by
the browser.
The advantage is that the selected tabulated form can be represented without any
problems by virtually any browser.
5.7 EtherNet Bus Module (VET020V)

Module is optionally affixed to the INTECONT cover in order to provide an EtherNet
interface to the TCP client. Set jumper W100 (Power supply source) according to the
attached illustration.
X20
Set jumper W100 to position 2-3.
Connector Assignment X20 (RJ45)
Pin Meaning
1 TX+
2 TX-
3 RX+
4 --
5 --
6 RX-
7 --
8 PE

Modbus-TCP/IP
Features
Separation Yes
Voltage supply 5V DC internally
Connector RJ45
OPEN MODBUS/TCP SPECIFICATION Schneider Electric, Release 1.0,

29 March 1999
Modicon Modbus Protocol Reference Guide PI-MBUS-300 Rev. J/1996
BVH2098AA EASYSERVE
HTML documents of Messrs. BECK http://www.beck-ipc.com
Beck Chiptool See note
XML service pack for Microsoft Internet Explorer
Sample files
Note
Any external document, update and sample can be downloaded from the Schenck
Process Service Page (www.schenck-process.de, Path: Service-Download-Bus
Systems-TCP).

Appendix
6 Appendix
6.1 ASCII Table with HTML Codes

Appendix

Measuring and Process Systems
SCHENCK PROCESS GmbH

D-64273 Darmstadt
Phone: +49 (0) 6151-32 10 28
Fax: +49 (0) 6151-32 11 72
E-Mail: sales.process@schenck.net
www.schenck-process.net
The Group

Schenk - BVH2220GB (Fieldbus)

Uploaded by

Copyright:

Available Formats

Schenk - BVH2220GB (Fieldbus)

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

Schenk - BVH2220GB (Fieldbus)

Uploaded by

Copyright:

Available Formats

INTECONT® PLUS

we make processes work BV-H2220GB

Sales: Tel.: +49 (0) 61 51 32 - 10 28

Service: 24h Emergency hotline: +49 (0) 172 - 650 17 00

Business Segments and Services:

Mining (Vibrating Machines)

Transport & Logistics

Components & Spares

Subject to change without prior notice.

BV-H2220 GB , 0505 INTECONT PLUS, Fieldbus Description

1 FIELDBUS DATA ....................................................................................................... 1

1.1 Validity Range ........................................................................................................ 1

1.2 Data Segments ....................................................................................................... 1

1.3 Units ........................................................................................................................ 1

1.4 Numeric Representation ....................................................................................... 2

1.5 User Data Construction......................................................................................... 3

1.6 User Data Diagnosis ............................................................................................ 13

1.7 Lists of Cyclic Data.............................................................................................. 15

2.1 Commissioning Guideline .................................................................................. 34

2.2 Profibus Module Functionality ........................................................................... 34

2.3 User Data Construction....................................................................................... 34

2.4 Settings on DP-Slave (INTECONT)..................................................................... 35

2.5 Settings on Profibus DP Master ......................................................................... 35

2.6 Diagnosis and Troubleshooting......................................................................... 36

2.7 Profibus Module (VPB020V) ............................................................................... 37

2.8 For Further Reading ............................................................................................ 38

3.1 Commissioning Guideline .................................................................................. 39

INTECONT PLUS, Fieldbus Description BV-H2220 GB , 0505 I

3.2 DeviceNet Module Functionality .........................................................................39

3.3 User Data Construction .......................................................................................39

3.4 Settings on DeviceNet Slave (INTECONT) .........................................................40

3.5 Settings on DeviceNet Master.............................................................................40

3.6 Diagnosis and Troubleshooting .........................................................................41

3.7 DeviceNet Module (VCB020V) .............................................................................41

3.8 For Further Reading .............................................................................................42

4.1 Commissioning Guideline ...................................................................................43

4.2 Modbus Module Functionality.............................................................................43

4.3 Data Format...........................................................................................................43

4.4 Function Codes (FC) ............................................................................................44

4.5 Transmission Protection .....................................................................................44

4.6 Error Codes...........................................................................................................44

4.7 Station Addresses ................................................................................................44

4.8 User Data ...............................................................................................................45

4.9 Cyclic Data Exchange Via Modbus.....................................................................45

4.10 Sample Messages...............................................................................................46

4.11 Settings on Modbus Slave (INTECONT)...........................................................46

4.12 Settings on Modbus Master ..............................................................................47

4.13 Diagnosis and Troubleshooting .......................................................................47

4.14 Serial Bus Module (VSS021V) ...........................................................................48

4.15 For Further Reading ...........................................................................................49

5.1 Definitions .............................................................................................................50

5.2 Commissioning Guideline ...................................................................................51

II BV-H2220 GB , 0505 INTECONT PLUS, Fieldbus Description

5.3 Ethernet Module Functions ................................................................................ 51

5.4 Configuring Ethernet Module ............................................................................. 53

5.5 Fieldbus Mode...................................................................................................... 60

5.6 WEB SERVER Mode ............................................................................................ 67

5.7 EtherNet Bus Module (VET020V)........................................................................ 73

5.8 For Further Reading ............................................................................................ 74