德国申克皮带秤 for Modbus

we make processes work
Contacts, Copyright
Sales:Tel.:+49 (0) 61 51 32 - 10 28
eMail:sales.process@
Service:24h Emergency hotline:+49 (0) 172 - 650 17 00
+49 (0) 171 - 255 11 95 (belt weighers, weighfeeders) eMail:service.process@
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@
Light Industry
Service Tel.:+49 (0) 61 51 32 - 25 72
Service Fax:+49 (0) 61 51 32 - 20 72
eMail:bvl.process@
Mining (Vibratory Machines)
Service Tel.:+49 (0) 61 51 32 - 35 25
Service Fax:+49 (0) 61 51 32 - 30 96
eMail:bvs.process@
Transport & Logistics
Service Tel.:+49 (0) 61 51 32 - 24 48
Service Fax:+49 (0) 61 51 32 - 13 69
eMail:bvt.process@
Components & Spares
Service Tel.:+49 (0) 61 51 32 - 17 58
Service Fax:+49 (0) 61 51 32 - 36 32
eMail:bvk.process@
© Copyright 2005
SCHENCK PROCESS GmbH
Measuring and Process Technologiess
Landwehrstraße 55, D-64293Darmstadt
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 , 0536INTECONT 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.2 General User Data Construction (6)
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.2Profibus Module Functionality (34)
2.3 User Data Construction (34)
2.4Settings on DP-Slave (INTECONT PLUS) (35)
2.5Settings on Profibus DP Master (35)
2.6 Diagnosis and Troubleshooting (36)
2.6.1 Event Message“Communication Error Host” (36)
2.6.2 LEDs on Profibus Module (37)
2.6.3 EasyServe Fieldbus View (37)
2.7Profibus Module (VPB020V) (37)
2.8 For Further Reading (38)
3 DEVICENET (39)
3.1 Commissioning Guideline (39)
3.2 DeviceNet Module Functionality (39)
3.3 User Data Construction (39)
INTECONT PLUS, Fieldbus Description BV-H2220 GB , 0536I ©SCHENCK PROCESS GmbH , Darmstadt
Table of Contents
3.4Settings on DeviceNet Slave (INTECONT PLUS) (40)
3.5Settings on DeviceNet Master (40)
3.6 Diagnosis and Troubleshooting (41)
3.6.1 Event Message“Communication Error Host” (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.11Settings on Modbus Slave (INTECONT PLUS) (46)
4.12Settings on Modbus Master (47)
4.13Diagnosis and Troubleshooting (47)
4.13.1 Event Message “Communication Error Host” (47)
4.13.2 EasyServe Fieldbus View (47)
4.14Serial Bus Module (VSS021V) (48)
4.15 For Further Reading (49)
5 ETHERNET (50)
5.1 Definitions (50)
5.2 Configuring Ethernet Module (51)
5.2.1 MultiServerTools Program (51)
5.2.2 Parameterizing INTECONT PLUS (58)
5.2.3 Checking Station Addresses (59)
II BV-H2220 GB , 0536INTECONT PLUS, Fieldbus Description
© SCHENCK PROCESS GmbH, Darmstadt
Table of Contents
5.3 Modbus-TCP/IP (60)
5.3.1 Commissioning Guideline (60)
5.3.2 Ethernet Module Functions (60)
5.3.3 Fieldbus Mode (62)
5.3.4 WEB Server Mode (70)
5.3.5 Ethernet Bus Module(VET020V) (76)
5.3.6 For Further Reading (77)
5.4 Ethernet/IP (78)
5.4.1 Commissioning Guidelines (78)
5.4.2 Ethernet Module Functions (78)
5.4.3 Fieldbus Mode (79)
5.4.4WEB Server Mode (81)
5.4.5 Ethernet Bus Module(VET022V) (82)
5.4.6 For Further Reading (83)
6 APPENDIX (84)
6.1ASCII Table with HTML Codes (84)
INTECONT PLUS, Fieldbus Description BV-H2220 GB , 0536III ©SCHENCK PROCESS GmbH , Darmstadt
Table of Contents
IV BV-H2220 GB , 0536INTECONT PLUS, Fieldbus Description
© SCHENCK PROCESS GmbH, Darmstadt
Fieldbus Data
1 Fieldbus Data
Before putting into operation one of the protocols described below, always read Item “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 Items 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” item holds for the following protocols:
Protocol See:
Profibus DP Chapter 2
DeviceNet Chapter3
Modbus Chapter4
Modbus-TCP/IP and Ethernet/IP Chapter 5
For description of protocol S5-RK512 (3964R), see manual FH458.
1.2 Data Segments
The INTECONT PLUS 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 PLUS 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 , 05361©SCHENCK PROCESS GmbH , Darmstadt
Fieldbus Data 1.4 Numeric Representation
Floating Point Values
INTECONT PLUS 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.5in IEEE format (indicating the line sequence):
Byte 1: Sign/Exponent
Byte 2:
Mantissa1
Byte 3:
Mantissa 2
Byte 4:
Mantissa3
0x430x160x800x00 Sample floating point numbers
Number IEEE format (HEX)Siemens-KG format (HEX) 1.03F80000001400000
10.04120000004500000
100.042C8000007640000
1000.0447A00000A7D0000
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 1600MSB 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 0x0140Comm4_HI Comm4_LO Comm5_HI Comm5_LO
Ex.: Status ID 0x02F0Status2_HI Status2_LO Status3_HI Status3_LO
2BV-H2220 GB , 0536INTECONT PLUS, Fieldbus Description
© SCHENCK PROCESS GmbH, Darmstadt
Fieldbus Data
1.5 User Data Construction
As mentioned above, INTECONT PLUS 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 PLUS 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-2mode 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
item.
NOTE
preset value 1 (commands 4 + 5) the release bit (in terms of a fieldbus lease)serving for interface monitoring must always be set statically. If this bit The table below includes all values transferred with the particular scale type:In re is not set, the subsequent preset values are not evaluated and HOST
ommunication fault is set.
c INTECONT PLUS, Fieldbus Description BV-H2220 GB , 0536
3
©SCHENCK PROCESS GmbH , Darmstadt
Fieldbus Data
4BV-H2220 GB , 0536INTECONT PLUS, Fieldbus Description
© SCHENCK PROCESS GmbH, Darmstadt
1.5.1.1 FIXED Mode – Detailed Message Sample
INTECONT PLUS 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 00Commands 6+7(0160)No command active
Bytes 9-12 00 00 00 01Commands 8+9(0180)START keyboard mode set Bytes 13-1643 16 80 00Setpoint(0250)150.5kg/hr
Bytes 17-2042 C8 00 00 Batch setpoint(0252)100kg
Bytes 21-32ZERO Standby
Slave->Master Bytes (hex) Meaning (ID value, hex) Current value
Bytes 1-401 02 00 00Status 2+3 (02F0)Normal mode, no release
Bytes 5-8 00 02 00 04Status 4+5 (0310)Filling system, fill level < Min Bytes 9-12 13 18 00 00Most significant error(0610)Event S9 ackn.,Warning2
Bytes 13-1642 C8 00 00 Feed rate actual value(0750)100kg/hr
Bytes 17-2044 9A 40 00 Totalizing counter 1(0752)1234kg
Bytes 21-2443 AC 80 00Bin level F(0760)345kg
Bytes 25-2845 F6 90 00Totalizing counter 2(0754)7890kg
Bytes 29-3242 C8 00 00 Effective setpoint(0766)100kg/hr
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 er 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 (header)Parameters (PKW)
optional
User data
Process data (PDR)
Protocol frame
(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.
.
6BV-H2220 GB , 0536INTECONT PLUS, Fieldbus Description
1.5.
2.1 Message Construction
The figure below shows the basic construction of user data in the INTECONT PLUS system.The first line shows the message from bus master to scale; the second, the
scale reponse.
User data construction of messages
he 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
T Not cle. CONT
PLUS), fieldbus communication fault is set on INTECONT PLUS. INTECONT e
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 cy If one ID is zero, respective value is not evaluated..
If all bytes are set to zero in the presetting message (bus Master to INTE PLUS interprets this state as failure of the bus Master's host CPU whilst the communication processor in Master is active. The INTECONT PLUS 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.
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
, ID 0x750. Through addition of (read) IDs in Master --> scale message,you can cause the
d values into th
e response message. Value sequence corresponds to the ID sequence. I
f IDs of the Preset value or Command ranges re red a s If an ID is identified as wrong, correspondin
g value in the response is set to zero.
le r et rey) parameter block always precedes the residual data. in message. The fixed status has ID 0x2F0; the actual value scale to enter the desire a ente , the v lue pre et last is reread. Samp Data t ansmission with additional param er block
The (g Master --> scale message
PKE
IND
PWE1
PWE2
ID Preset value 1
Preset value 1ID
Preset
value 2
Preset value 2 Ordering list
(read IDs)
Scale response
PKE
IND
PWE1
PWE2
Status infos (2+3)(4 bytes)Actual value (4 bytes)
Values as per ordering list
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.
8BV-H2220 GB , 0536
INTECONT PLUS, Fieldbus Description
1.5.
2.2Parameter Transfer
Parameter block (PKW)
Parameter block (PKW), 4 words
PKE (1st word)IND (2nd word) PWE (3rd and 4th words)
High Low PWE1PWE2
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. 151413Bit 0-12 Details of parameter ID (PKE)
Order ID Meaning Pos. response Neg. response 0No order0-
27
1Request current
parameter value (double
word)
27
3Write (change) parameter
value (double word)
27
4Order description element
(double word)
Order IDs (AK)Master station —> INTECONT PLUS
Response ID Meaning
0No order
2Transfer current parameter value/ event group (double word) 7Order cannot be executed (error number in PWE2) Response IDs (AK)INTECONT PLUS —>Master station
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 between1 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
0Default value
4Min. value
8Max. value
12Unit 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= 0with 16-bit parameters, or High portion with 32-bit
parameter
Error number Meaning
1Inadmissible parameter number (parameter not available or preset
value wrong, e.g. MIN/MAX exceeded up/down)
2MIN/MAX value exceeded up/down
3No access right
4Order not possible in current operating state of scale
5Order 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.
10BV-H2220 GB , 0536INTECONT PLUS, Fieldbus Description
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 PLUS
Configuration: “NO_PARA_ID”
parameters
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 0250ID for"Write feed rate setpoint”
Bytes 3-6 0A 7D 00 00 Setpoint 1000.0kg/hr
Bytes 7+8 0140ID for"Commands 4+5"
Bytes 9-1 00 41 00 00 Reset control value for scale start and counter 1
Bytes 13+14 0000Standby
Bytes 15-18 00 41 00 00 Reset control value for scale start and counter 1 (ID=0: not active)
Bytes 19+20 0752ID to request counter 1 reading
Bytes 21+22 075C ID to request belt speed in m/s
Bytes 23+24 0754ID to request counter 2 reading
Bytes 25+26 0758ID to request belt load in kg/m
Bytes 27+28 0000Standby
Bytes 29+30 0000Standby
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 17-20 00 00 00 00 Value for ID in bytes 23+24, i.e.counter 2 reading
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
-----------------------------------------------------------------------------------------------------------------------------------------------
Sample 2 (preset parameter)
GSD module:“PARA_ID”
Configuration: “PARA_ID”
INTECONT PLUS
parameters
Process image lenght Master -> Slave : 28 bytes, Slave -> Master: 32 bytes
Floating point format IEEE
Sample Master->Slave process image:
Bytes 1-8 7205 0000 4170 0000 Preset parameter"F_Control Min.– Feed Index 1" (value =15 %) Bytes 9+100250ID for"Write feed rate setpoint "
Bytes 11-14 44 7A 00 00 Setpoints 1000.0kg/hr
Bytes 15+16 0140ID for"Control"
Bytes 17-20 00 44 00 00 Acknowledge control value for events and reset counter 1
Bytes 21+22 0752ID to request counter 1 reading
Bytes 23+24 075C ID to request belt speed in m/s
Bytes 25+26 0754ID to request counter 2 reading
Bytes 27+28 0758ID to request belt load in kg/m
Sample Slave->Master process image:
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 17-20 00 00 00 00 Value for ID in bytes 19+20, i.e.counter 1 reading
Bytes 21-24 00 00 00 00 Value for ID in bytes 21+22, i.e. belt speed
Bytes 25-28 00 00 00 00 Value for ID in bytes 23+24, i.e.counter 2 reading
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”
Configuration: “PARA_ID”
INTECONT PLUS
parameters
Process image lengths Master -> Slave : 28 bytes, Slave -> Master: 32 bytes
Floating point format IEEE
Sample Master->Slave process image:
Bytes 1-8 7205 0000 447a 0000 Preset parameter"F_Control Min." (value =1000 %) .........
Sample Slave->Master process image:
Bytes 1-8 F205 0000 4170 1000 Preset parameter value not accepted (value > MAX) .........
-----------------------------------------------------------------------------------------------------------------------------------------------
Sample 4 (read parameter)
GSD module“PARA_ID”
INTECONT PLUS parameters Configuration: “PARA_ID”
Process image lengths Master -> Slave : 28 bytes,Slave -> Master: 32 bytes
Floating point format IEEE
Sample Master->Slave process image:
Bytes 1-8 3205 0000 xxxx xxxx Read parameter "F_Control Min" (xxxx = optional value) .........
Sample Slave->Master process image:
Bytes 1-8 5205 0000 4170 0000 Parameter value = 15%
.........
12BV-H2220 GB , 0536INTECONT PLUS, Fieldbus Description
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)
” bit and command D=0x0160).Scale is requested to respond to IDs 0x0758,0x075E,0x0310 and Explanations on EasyServe monitor (Profibus sample)
Master transfers command (ID=0x0140) “Acknowledge event (I 0x0610.
Display meanings
Dis “==“<=aster uttons
R Starts recording on scale
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 t (most recent) 50 messages can be recorded.k 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.
play shows current fieldbus protocol (see title) and data selected using checkbox.> “ means that Master sends data to scale ( Receive INTECONT PLUS).= “ identifies data sent from INTECONT PLUS to M Selection b ecord :
Display :
las Copy :
Lets you mar 14BV-H2220 GB , 0536
INTECONT PLUS, Fieldbus Description
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 PLUS 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.
INTECONT PLUS, Fieldbus Description BV-H2220 GB , 053615©SCHENCK PROCESS GmbH , Darmstadt。