Operating Instructions: Vegacom 557 Siemens 3964 and 3964 R Procedure With RK 512
Operating Instructions: Vegacom 557 Siemens 3964 and 3964 R Procedure With RK 512
Operating Instructions: Vegacom 557 Siemens 3964 and 3964 R Procedure With RK 512
Operating Instructions
VEGACOM 557
Siemens 3964 and 3964 R procedure
with RK 512
PC
BA
on
557
in out
Contents
Contents
1 Product description
1.1 Application ............................................................................ 4
1.2 Configuration ........................................................................ 4
1.3 Function ................................................................................. 4
1.4 Complete measuring system with digital
communication and networking .......................................... 6
1.5 Technical data ....................................................................... 7
1.6 Dimensions ........................................................................... 9
4 Setup
4.1 Check list ............................................................................ 16
4.2 Parameter setting CP 524 ................................................. 16
5 S5 functional component
5.1 Synchron order .................................................................. 22
5.2 Handling components for reading in of data
(indicating values) ............................................................. 23
5.3 Reading in data (indicating values) .................................. 25
6 Supplement
6.1 Short description of the standard interfaces
RS 232, RS 422 and RS 485 ............................................. 33
6.2 Complete overview on process image of
measured values in VEGACOM ....................................... 36
1 Product description
1.1 Application 1.2 Configuration
With VEGACOM 557 an efficient interface The component VEGACOM 557 is designed
converter (Gateway) is available. It is used in 19" technology with 5 TE width (1 TE =
for VEGA specific protocols of the DISBUS 5.08 mm) acc. to DIN 41 494. It can be used:
and LOGBUS into standard data formats. - in carrier BGT 596
- in VEGALOG 571 carrier BGT LOG 571
The existing version is used for connection of - in housing type 505.
level and pressure measuring systems to
PLC systems with Siemens communication The electrical connection is made via a plug
processors CP 524 and CP 525. The proce- connector acc. to DIN 41 612 on the rear of
dures 3964 and 3964 R are supported. the component. The connection to LOGBUS
is made via an additional 5-pole plug connec-
This conversion of the protocol formats ena- tor mounted to the DIN plug connector.
bles to call up measured data and status
information of the measuring systems via A 9-pole SUB-D plug marked "PC" is located
PLC/DCS. This bidirectional data traffic re- in the front plate of VEGACOM 557. It is used
quires respective measures on the PLC/DCS for connection of a PC to VEGACOM 557 via
side which are described in this instruction. RS 232 C.
additional plug
The data received in the PLC can be further Basic board Add. board connector for
processed by the user program, i.e. for LOGBUS
example visualised or used for control pur-
PC Supply
poses. interface
DISBUS
In a planned further stage, signal condition-
ing instrument-specific parameters can be Siemens 3964
outputted, modified and returned. and 3964 R
VEGACOM 557 receives as participants on From this buffer memory, the data set is
the DISBUS these data in a DCS telegram. transferred into a process image. The protec-
The telegrams are written in VEGACOM 557 tion converter software enquires the individual
into a buffer memory. storage section cyclically for the saved val-
ues. The data sets are tested and converted
DISBUS into the Siemens 3964 or 3964 R data format.
After this conversion, the data are transferred
into the transmission memory and further
Simatic CP
524/525 transferred to the communication processor.
S5
Proce- There, they are read in via a S5 PLC func-
Instru- dure tional component and saved in a data compo-
ment 3964 /R
interface nent for further processing.
RS 232/RS485/ VEGACOM 557 1 ………… 15
RS 422/TTY with additional VEGAMET DISBUS Buffer Proc- Trans- CP524/
board S5 memory ess mis- CP525
LOGBUS image Test sion
Connection VEGACOM 557 on DISBUS conver-
memory
sion
LOGBUS
DISBUS
on
% % % % % % % %
100 100 100 100 100 100 100 100
- + - + - + - + - + - + - + - +
! ! ! ! ! ! ! !
on on on on on on on on
VEGAMET VEGAMET VEGAMET VEGAMET VEGAMET VEGAMET VEGAMET VEGAMET
513 513 513 513 513 513 513 513
Modbus system
4
3
PC
VVO
BA
!
on
VEGACOM
557
LOGBUS
1
5
4 PC
on
VEGALOG
571
VV
5
1 2
PC interface
Interface standard RS 232 C
Cable length max. 15 m (up to 9600 baud)
Connection cable 3-wire, if necessary screened
Transmission rate 300, 600, 1200, 2400, 4800, 9600, 19200 Bit/s
Transmission format 8 data bits, 1 stop bit, even/no parity
Galvanic separation up to 0.5 kV
Electrical connection
Power supply
Meas. data inputs multiple plug acc. to DIN 41 612, series F,
48-pole, d, b, z
PC interface D-SUB plug connector, 9-pole pin in
front plate
Indicating elements
LED in front plate
- green "BA" signal for active communication via
3964/3964 R
- red (flashing) DISBUS/LOGBUS failure
- red (on) failure
- green "on" operating condition
Ambient conditions
Permissible ambient temperature -20°C … +60°C
Storage and transport temperature -20°C … +85°C
Moisture 93 %, T = 40°C acc. to DIN/IEC 68-2-3
Shock load 2 … 100 Hz, 0.7 g
Mechanical data
Series module card for
- carrier BGT 596
- carrier BGT LOG 571
- housing type 505
Dimensions, not mounted W = 25.4 mm (5 TE), H = 128.4 mm,
D = 166 mm + strap
Weight approx. 200 g
CE conformity
VEGACOM 557 meets the protective regulations of EMC (89/336/EWG) and NSR
(73/23/EWG). Conformity has been judged acc. to the following standards:
EMC Emission EN 50 081 - 1: 1993
Susceptibility EN 50 082 - 2: 1995
NSR EN 61 010 - 1: 1993
1.6 Dimensions
front RS 232C interface (PC) Multiple plug
Circuit board 100 x 160 x 1.5
European size LOGBUS 5 TE
plug
128,4
100
BA
on
557
15
Coding
pin
3…5
Siemens S5 P3
d b z
2 L1 (+) RS 232
Supply voltage
2 N (-) 1
6 CTS
2
7 RxD
3 TxD
8
4 RTS
TTY RS 232 RS 485 RS 422 9
16 GND GND GND GND
5 GND
18 T+ TxD
18 R+ RxD
20 R–
20 T–
Pin Description I/O
32
/DATA /RX
32 /TX
ON
1 2 3 4
LR LR OFF ON ON free
ON OFF OFF free
= Activation of the TTY interface ON OFF ON (ASCII)
ON ON OFF Siemens 3964,
3964 R
2 1
ON ON ON (MODBUS RTU/
ASCII)
LR LR
= Activation of the RS 232 interface
(factory setting)
2 1
Note:
L = position left, R = position right
The factory setting of the 8 bridges is 1 - 2, The mode half duplex must be set on the
except bridge Br4 (2 - 3). RS 422/485 module.
4 Setup
4.1 Check list
The check list gives a short overview on the activities required for configuration. A detailed
description of the individual items is made in this document.
• Equip VEGACOM 557 with the additional board S5 (for communication with procedure
3964 /R).
• Equip communication processor CP with the necessary interface (RS232, RS422/485 or
TTY). Set interface number
• Adjust VEGACOM DIL switches and hook switches. Interface parameters must be adjusted.
Make sure that the same interface is selected which is used on the CP.
• Connect CP to VEGACOM.
• Create a program for configuration of the CP with the programming package COM 525.
• Load the created program with an EPROM programming device to the EPROM module.
• Insert the EPROM module into the memory shaft of the communication processor.
• A SYNCHRON order must be called up in the organisation components OB 20,21 and 22 for
synchronisation of the CP with the S5 application.
• Integrate FETCH and RECEIVE calls in the S5 user program to read in indicating values of
VEGAMET or VEGALOG in data component 3.
For communication with Simatic S5 via procedure 3964 R / 3964, VEGACOM supports the
Fetch function (fetch data). This function can be called up by the PLC function block to read in
the indicating values and save them in data component 3.
Before the Fetch function can be applied, the parameter setting for the communication proces-
sor CP must be done. For this purpose, the S5 programming package COM 525 is available.
After calling up the programming package COM 525 in the S5 program in menu Change/
further… (directory: \STEP 5) the following points must be processed:
Activity Purpose
Basic pattern Creating of a new CP program
Fetch order Definition and determination of orders where data (indicating values) are
saved
Procedure Activate procedure 3964 R and set transmission parameters
Interpreter Activate, to process communication orders
Basic pattern
To create a new program, you have to enter the file and system name in the basic pattern. As
component, you have to choose RK (for computer link).
DRIVE: C
PROGRAM NAME: PROGR 1
COMPONENTE: RK
PG Datue - Time: T M J H M
08.11.94 - 10:42
F1 | F2 | F3 | F4 | F5 | F6 | F7 | F8
| | | | | | |
CHOICE | | | | | | HELP | EXIT
DRIVE: C
PROGRAM NAME: PROGR 1
COMPONENTE: RK
F1 | F2 | F3 | F4 | F5 | F6 | F7 | F8
USER DATA| TRANS- | | | | | |
PROGRAM. | MIT | DELETE | INFO |COMPRESS. |CONTINUE | | EXIT
After F1 selection (see previous pattern) the adjustment of the order number is expected,
here e.g. 1. For parameter setting of order number 1, function key F5 (Order Progr.) must be
selected:
In this pattern it will be determined that order no. 1 is a Fetch order (fetch data). The data to
be received should be fetched by source data component 3 from source word address 0.
Coordination markers are not required.
O R D E R
Order: FETCH
CPU - no: 1
DB - no: 003
F1 | F2 | F3 | F4 | F5 | F6 | F7 | F8
TO | BACK- | FOR- | | DELETE |TAKE OVER | |
PRINTER | WARDS | WARD | | ORDER |ORDER | HELP | EXIT
The relays are saved in data component DB5. Therefore it is necessary to enter this data
component in the order. The order number has been set to 2 as we assumed that already an
order for reading the measured values is available.
O R D E R
Order: FETCH
CPU - no: 1
DB - no: 005
F1 | F2 | F3 | F4 | F5 | F6 | F7 | F8
TO | BACK- | FOR- | | DELETE |TAKE OVER | |
PRINTER | WARDS | WARD | | ORDER |ORDER | HELP | EXIT
Procedure
For determination of the procedure with the transmission parameters, the procedure compo-
nents can be taken over out of the programming library COMLIB02.
Change to the transmission menu: Basic pattern F1 -> Choice F2 -> Transfer F5 -> FD-FD.
The menu appears:
Source: Destination:
VOLUME: FD FD
DRIVE: C C
INTERFACE NO.:
PROGRAM NAME: COMLIB02 PROGR1
COMPONENT: RK
F1 | F2 | F3 | F4 | F5 | F6 | F7 | F8
| | INTER- | | PRINT | ORDER | |
| | PRETER |PROCEDURE | PARAM. | BLOCK | HELP | EXIT
Select with F7 in the field program name the program library COMLIB02. Push F4 to select the
procedure:
-> PROGRAM CHOICE -> CHOICE-> TRANSMIT –> SIMATIC S5 / COM 525
P R O C E D U R E
—————————————————————————————————————
Source: Destination:
VOLUME: FD FD
DRIVE: C C
INTERFACE NO.:
PROGRAM NAME: COMLIB02 PROGR1
COMPONENT: RK
F1 | F2 | F3 | F4 | F5 | F6 | F7 | F8
TRANS- | | | | | | |
MIT | | | | | | HELP | EXIT
Select with F7 in the field component the procedure 3964 R and transfer with F1 to the own file
(here PROGR1 ).
Procedure transmission parameter.
Change to the parameter menu: Basic pattern F1 -> Choice F2 -> F6 Continue F2 Procedure
parameter. The character length must be set to 8, the number of stop bits to 1 and the parity to
EVEN.
Interpreter
The interpreter component can be taken over from the program library COMLIB02 to load the
interpreter RK512. Change to the transmission menu: Basic pattern F1 -> Choice F2 -> Trans-
fer F5 -> FD-FD. The menu appears:
Source: Destination:
VOLUME: FD FD
DRIVE: C C
INTERFACE NO.:
PROGRAM NAME: COMLIB02 PROGR1
COMPONENT: RK
F1 | F2 | F3 | F4 | F5 | F6 | F7 | F8
| | INTER- | | PRINT | ORDER | |
| | PRETER |PROCEDURE | PARAM. | BLOCK | HELP | EXIT
Select with F7 in the field program name the programming library COMLIB02. For interpreter
selection push F3:
-> PROGRAM CHOICE -> CHOICE-> TRANSMIT –> SIMATIC S5 / COM 525
P R O C E D U R E
—————————————————————————————————————
Source: Destination:
VOLUME: FD FD
DRIVE: C C
INTERFACE NO.:
PROGRAM NAME: COMLIB02 PROGR1
COMPONENT: RK
F1 | F2 | F3 | F4 | F5 | F6 | F7 | F8
TRANS- | | | | | | |
MIT | | | | | | HELP | EXIT
VOLUME: FD
DRIVE: C
PROGRAM NAME: PROGR1
COMPONENT: RK
F1 | F2 | F3 | F4 | F5 | F6 | F7 | F8
SHORT | | | | ORDER | | |
DESCR. | | | | BLOCK | | HELP | EXIT
5 S5 functional component
For the STEP 5 user program, internal functional components (HTB handling components)
HTB SYNCHRON, HTB FETCH and HTB RECEIVE are required. To call up the internal function
components, these must be loaded first from the automation device AG S5. The menu selec-
tion is then as follows: Object > Components > Transfer > AG file.
After the starting-up phase, the CP expects a SYNCHRON order. This is necessary for the
handling of the FETCH / SEND orders. The SYNCHRON component is generally called up with
the STEP 5 user program in the organisation components OB20, OB21 and OB22.
Example:
OB 20
C:CP524_ST.S5D LAE=11
Network 1 0000 Output
:SPA FB 249
Name :SYNCHRON
SSNR : KY 0,0
BLGR : KY 0,4 Block size 128
PAFE : MB 50 Parameter failure in tag byte 50
:BE
For reading in the indicating values from the VEGAMET instruments and saving them in a PLC
data component, the handling component HTB FETCH is necessary to place orders and the
HTB RECEIVE to fetch and save data.
The FETCH component gives the order to the CP to fetch data of a communication partner. The
receipt of the data however is carried out by the component RECEIVE.
Note:
The RECEIVE component communicates with the CP only if the linking result VKE is 1 before
calling up the component. This can be forced with the instruction
O M 1.1
ON M 1.1.
The indicating values are saved in a PLC data component of the S5 data memory. It is obliga-
tory to state DB3 in the programming package COM 525 when determining the orders for
measurement loops 1 … 128 and DB4 for measurement loops 129 … 255. See also chapter
5.1. Here also the data destination, e.g. source data component 3 from source word address
0 is stated.
The data words 0 to 12 are reserved and are not used. 2 data words (4 bytes) are required
per indicating value. Each VEGAMET provides 7 indicating values. These are saved in the
data component as follows:
DW
0 00 00 00 80
14 HB LB ME STAT
26 HB LB ME STAT
210 HB LB ME STAT
222 HB LB ME STAT
Explanation:
Status values:
STAT Meaning
00 H Valid value
01 H Simulated value
80 H Value not available
FF H General error
The data word address of the first indicating value of VEGAMET to address is determined as
follows:
VEGAMET (DISBUS): Data word address = VEGAMET address • 14 – Source word address • 2
Data word 0 is reserved. One data word will be reserved per VEGAMET. In total 15 + 1 are
covered by VEGAMET.
DW VEGAMET address
0 reserved
1 1
2 2
3 3
4 4
… …
15 15
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Status reser- reser- reser- reser- reser- Relay Relay Relay Relay Relay Relay Relay Relay Relay Rel.
ved ved ved ved ved 10 9 8 7 6 5 4 3 2 1
2 data words (4 bytes) are required per indicating value. These are saved in the PLC data
component DB as follows:
DW
248 HB LB ME STAT
250 HB LB ME STAT
Explanation:
Status values:
STAT Meaning
00 H Valid value
01 H Simulated value
80 H Value not available
FF H General error
1 data word will be reserved per LOGBUS card. In total, 32 data words will be covered by
VEGALOG.
DW Card address
0 1
1 2
2 3
3 4
4 5
… …
31 32
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Status reser- reser- reser- reser- reser- Relay Relay Relay Relay Relay Relay Relay Relay Relay Rel.
ved ved ved ved ved 10 9 8 7 6 5 4 3 2 1
ZLAE is an important parameter, indicating the length of the data block. The value is depend-
ent on the number of indicating values:
SSNR: The interface number corresponds to the switch position in the CP (standard feature
= 0)
A-NR: The order number corresponds to the setting in the programming package COM
525
ANW: Statement of a double marker word for status description
ZTYP: KC DB Data destination is data component
DBNR: KY 0 Data component number
ZANF: KF +0 Initial word in DB is data word 0. With != 0 the data sector is shifted by
this value.
ZLAE : KF +value data length in bytes value = see above
PAFE : Statement of a marker byte for indication of parameter setting failures
The information on the data destination, parameter : ZTYP, DBNR, ZANF and ZLAE are irrel-
evant as this information was already defined in the programming package COM 525 with the
order determination.
SSNR: The interface number corresponds to the switch positions in the CP.
(standard feature = 0)
A-NR: The order number corresponds to the setting in the programming package COM
525
ANW: Statement of a double marker word for status description
ZTYP: KC DB Data destination is data component
DBNR: KY 0,0 Data component number, here irrelevant
ZANF: KF +0 Initial word in DB, here irrelevant
ZLAE: KF +0 Data length in bytes, here irrelevant
PAFE: Statement of a marker byte for indication of parameter setting failures
OB 20
C:CP524_ST.S5D LAE=11
Network 1 0000 Output
:SPA FB 249
Name :SYNCHRON
SSNR : KY 0,0
BLGR : KY 0,3 Block size 64
PAFE : MB 50 Parameter error in merker byte 50
:BE
Call up of the Fetch and Receive component for the indicating values
The program reads in the indicating values for the VEGAMET instruments (DISBUS) or
VEGALOG instruments (LOGBUS). The Fetch order was determined in the programming
package COM 525 with order number 1. The statements on the data destination had been
carried out in the programming package with the order determination. Therefore the destina-
tion parameters ZTYP, DBNR, ZANF and ZLAE are negligible when calling up the RECEIVE
component.
FB 1 C:CP524_ST.S5D LAE = 62
Network 1 0000 Output
Name :TEST
:O M 1.1
:ON M 1.1 VKE = 1 force, so that FETCH
: is worked on in any case
:
:SPA FB 246 enquire FETCH-component
Name :FETCH
SSNR : KY 0,0 Interface no. = 0
A-NR : KY 0,1 Order number = 1
ANZW : MW 10 Indication double word up from MW10
ZTYP : KC DB Data destination (of indication values) in data component
DBNR : KY 0,3 ... number 3
ZANF : KF +0 Data destination to DW0
ZLAE : KF +42* fetch 6 indication values (of 2 signal conditioning instruments
VEGAMET 1 and 2)
PAFE : MB 2 Parametr. failure in MB 2
:
:
:
:
:
:
:
:O M 1.1
:ON M 1.1 VKE = 1 force, so that FETCH
: is worked on in any case
:
:SPA FB 245 enquire RECEIVE-component
Name :RECEIVE
SSNR : KY 0,0 Interface no. = 0
A-NR : KY 0,0 Order number = 1
ANZW : MW 12 Indication double word up from MW12
ZTYP : KC DB Data destination in data component
DBNR : KY 0,0
ZANF : KF +0
ZLAE : KF +0
PAFE : MB 3
:
:
:
:
:
:
:BE
* 6DW as offset (see page 23), 6DW for VEGAMET 1, 6DW for VEGAMET 2
Call up of the Fetch and Receive component for the relay information
...
FB 2 C:CP524_ST.S5D LAE = 62
Network 1 0000 Output
Name :REL
:O M 1.1
:ON M 1.1 VKE = 1 force, so that FETCH
: is worked on in any case
:
:SPA FB 246 enquire FETCH-component
Name :FETCH
SSNR : KY 0,0 Interface no. = 0
A-NR : KY 0,2 Order number = 2 for relay information
ANZW : MW 11 Indication double word up from MW11
ZTYP : KC DB Data destination(the indication values) in data component
DBNR : KY 0,4 ... Number 3
ZANF : KF +0 Data destination to DW0
ZLAE : KF +32 32 words (all relays)
PAFE : MB 4 Parametr.failure in MB 4
:
:
:
:
:
:
:
:O M 1.1
:ON M 1.1 VKE = 1 force, so that FETCH
: is worked on in any case
:
:SPA FB 245 enquire RECEIVE-component
Name :RECEIVE
SSNR : KY 0,0 Interface no. = 0
A-NR : KY 0,0 Order number = 1
ANZW : MW 12 Indication double word up from MW12
ZTYP : KC DB Data destination in data component
DBNR : KY 0,0
ZANF : KF +0
ZLAE : KF +0
PAFE : MB 3
:
:
:
:
:
:
:BE
Note:
In the total program only one RECEIVE necessary.
Data word
DW
0 00 00 00 80
7 pieces
2 00 00 00 80 reserved, are not used
12 00 00 00 80
14 HB LB ME STAT
7 pieces
16 HB LB ME STAT VEGAMET address 1
18 HB LB ME STAT
20 HB LB ME STAT
7 pieces
22 HB LB ME STAT VEGAMET address 2
24 HB LB ME STAT
up to 40
Data word
DW
0 HB LB ME STAT DCS 1
2 HB LB ME STAT DCS 2
4 HB LB ME STAT DCS 3
6 HB LB ME STAT DCS
8 HB LB ME STAT DCS 5
10 HB LB ME STAT DCS 6
up to 40 up to DCS 21
Explanation:
6 Supplement
MSB = most significant bit Both levels are related to a common signal
LSB = least significant bit ground (GND). The permissible, ohmic load
Number of data bits = 8
must be more than 3 kOhm, the permissible
Standard data transmission capacitive load can be max. 2500 pF.
A parity bit can follow the last data bit which Main characters of a RS 232 interface are
is used for detection of transmission errors. - reduced cable length (max. 15 m to
The parity bit ensures that with 9600 baud)
- EVEN parity always an even number of bits - low data rates (max. 19200 baud)
- ODD parity always an odd number of bits - only point-to-point connection
is transmitted.
For industrial applications, the provided
A so-called handshake can be used to re- handshake signals are not necessary. For
lease or interrupt the data transmission. this, the handshake inputs are just connected
to the handshake outputs of the same instru-
ment (release level).
The interface RS 422 transfers the data as To be neutral against (inevitable for large
voltage difference between two correspond- distances) potential shifts, a galvanic isolation
ing cables. Signal earth as grounding is not of the transmission/receipt component is
required. One pair of wires is required for the recommended. A termination is generally
transmitting as well as for the receipt signal, necessary, independent on data rate and
consisting of an inverted and a non-inverted distance.
signal cable. Possible common-mode inter-
ferences cause a symmetric shift of the volt- Partly also interfaces TTY (also called 20 mA
age level and cannot deteriorate the useful or Current Loop) are used. The data are
signal. transmitted by switching on and off a current
of 20 mA in a cable loop in the cycle of the
Thanks to the higher interference immunity data bits. This interface however is not sub-
compared to RS 232, distances up to 1200 m jected to a standardisation so that the use
and high data rates up to 10 Mbits can be must be projected in detail. With galvanic
reached. The interference immunity is also separation, distances up to 1000 m with data
visible on the permissible voltage levels: with rates of 300 … 9600 baud can be transmitted
an output level of the transmitter under load safely.
of ±2 V the receiver components accept a
level of ±200 mV still as valid signal.
Conclusion
Special feature of the RS 422 is that it allows
the unidirectional connection of up to 10 re- Main features for interfaces acc. to RS 232
ceivers on one transmitter. With higher trans- are:
mission rates and/or large distances, a - reduced cable lengths
termination (adaption of the wave resistance) - low data rates
is necessary and a galvanic separation of the - only point-to-point connection
transmitter/receiver components is absolutely
recommended. Main features for interfaces acc. to RS 422
and RS 485 are:
The interface RS 485 means an extension of - large cable lengths
the RS 422 concept to a bus-compatible - high data rates
system, whereby the physical differences - basis for bus systems
are neglicible.
Emitter
Permissible driver
output voltage ±25 V –0.25…6 V –7…12 V
Driver output signal
- without load ±15 V ±5V ±5V
- with load ±5V ±2V ±1.5 V
Driver load 3…7 kOhm 100 Ohm 54 Ohm
Receiver
Input voltage ±15 V ±7 V –7…12 V
Sensitivity ±3 V ±200 mV ±200 mV
Input resistance 3…7 kOhm 4 kOhm 12 kOhm
10km
1,2km
1km
Distance
100m
RS 422-A
RS 485
30m
RS 232-C
15m
Transmission rate
DB3 DW 0 DCS 1 - - - -
DB3 DW 2 DCS 2 - - CH1 MET1 DCS1 MET1
DB3 DW 4 DCS 3 - - CH1 MET2 DCS1 MET2
DB3 DW 6 DCS 4 MET1 CH1 - CH1 MET3 DCS1 MET3
DB3 DW 8 DCS 5 MET1 CH2 - CH1 MET4 DCS1 MET4
DB3 DW 10 DCS 6 MET1 CH3 - CH1 MET5 DCS1 MET5
DB3 DW 12 DCS 7 MET2 CH1 - CH1 MET6 DCS1 MET6
DB3 DW 14 DCS 8 MET2 CH2 MET1 DCS1 CH1 MET7 DCS1 MET7
DB3 DW 16 DCS 9 MET2 CH3 MET1 DCS2 CH1 MET8 DCS1 MET8
DB3 DW 18 DCS 10 MET3 CH1 MET1 DCS3 CH1 MET9 DCS1 MET9
DB3 DW 20 DCS 11 MET3 CH2 MET1 DCS4 CH1 MET10 DCS1 MET10
DB3 DW 22 DCS 12 MET3 CH3 MET1 DCS5 CH1 MET11 DCS1 MET11
DB3 DW 24 DCS 13 MET4 CH1 MET1 DCS6 CH1 MET12 DCS1 MET12
DB3 DW 26 DCS 14 MET4 CH2 MET1 DCS7 CH1 MET13 DCS1 MET13
DB3 DW 28 DCS 15 MET4 CH3 MET2 DCS1 CH1 MET14 DCS1 MET14
DB3 DW 30 DCS 16 MET5 CH1 MET2 DCS2 CH1 MET15 DCS1 MET15
DB3 DW 32 DCS 17 MET5 CH2 MET2 DCS3 CH2 MET1 -
DB3 DW 34 DCS 18 MET5 CH3 MET2 DCS4 CH2 MET2 DCS2 MET1
DB3 DW 36 DCS 19 MET6 CH1 MET2 DCS5 CH2 MET3 DCS2 MET2
DB3 DW 38 DCS 20 MET6 CH2 MET2 DCS6 CH2 MET4 DCS2 MET3
DB3 DW 40 DCS 21 MET6 CH3 MET2 DCS7 CH2 MET5 DCS2 MET4
DB3 DW 42 DCS 22 MET7 CH1 MET3 DCS1 CH2 MET6 DCS2 MET5
DB3 DW 44 DCS 23 MET7 CH2 MET3 DCS2 CH2 MET7 DCS2 MET6
DB3 DW 46 DCS 24 MET7 CH3 MET3 DCS3 CH2 MET8 DCS2 MET7
DB3 DW 48 DCS 25 MET8 CH1 MET3 DCS4 CH2 MET9 DCS2 MET8
DB3 DW 50 DCS 26 MET8 CH2 MET3 DCS5 CH2 MET10 DCS2 MET9
DB3 DW 52 DCS 27 MET8 CH3 MET3 DCS6 CH2 MET11 DCS2 MET10
DB3 DW 54 DCS 28 MET9 CH1 MET3 DCS7 CH2 MET12 DCS2 MET11
DB3 DW 56 DCS 29 MET9 CH2 MET4 DCS1 CH2 MET13 DCS2 MET12
DB3 DW 58 DCS 30 MET9 CH3 MET4 DCS2 CH2 MET14 DCS2 MET13
DB3 DW 60 DCS 31 MET10 CH1 MET4 DCS3 CH2 MET15 DCS2 MET14
DB3 DW 62 DCS 32 MET10 CH2 MET4 DCS4 CH3 MET1 DCS2 MET15
DB3 DW 64 DCS 33 MET10 CH3 MET4 DCS5 CH3 MET2 -
DB3 DW 66 DCS 34 MET11 CH1 MET4 DCS6 CH3 MET3 DCS3 MET1
DB3 DW 68 DCS 35 MET11 CH2 MET4 DCS7 CH3 MET4 DCS3 MET2
DB3 DW 70 DCS 36 MET11 CH3 MET5 DCS1 CH3 MET5 DCS3 MET3
DB3 DW 72 DCS 37 MET12 CH1 MET5 DCS2 CH3 MET6 DCS3 MET4
DB3 DW 74 DCS 38 MET12 CH2 MET5 DCS3 CH3 MET7 DCS3 MET5
DB3 DW 76 DCS 39 MET12 CH3 MET5 DCS4 CH3 MET8 DCS3 MET6
DB3 DW 78 DCS 40 MET13 CH1 MET5 DCS5 CH3 MET9 DCS3 MET7
DB3 DW 80 DCS 41 MET13 CH2 MET5 DCS6 CH3 MET10 DCS3 MET8
DB3 DW 82 DCS 42 MET13 CH3 MET5 DCS7 CH3 MET11 DCS3 MET9
DB3 DW 84 DCS 43 MET14 CH1 MET6 DCS1 CH3 MET12 DCS3 MET10
DB3 DW 86 DCS 44 MET14 CH2 MET6 DCS2 CH3 MET13 DCS3 MET11
DB3 DW 88 DCS 45 MET14 CH3 MET6 DCS3 CH3 MET14 DCS3 MET12
DB3 DW 90 DCS 46 MET15 CH1 MET6 DCS4 CH3 MET15 DCS3 MET13
DB3 DW 92 DCS 47 MET15 CH2 MET6 DCS5 - DCS3 MET14
DB3 DW 94 DCS 48 MET15 CH3 MET6 DCS6 - DCS3 MET15
DB3 DW 96 DCS 49 - MET6 DCS7 - -
DB3 DW 98 DCS 50 - MET7 DCS1 - DCS4 MET1
DB3 DW 100 DCS 51 - MET7 DCS2 - DCS4 MET2
DB3 DW 102 DCS 52 - MET7 DCS3 - DCS4 MET3
DB3 DW 104 DCS 53 - MET7 DCS4 - DCS4 MET4
DB3 DW 106 DCS 54 - MET7 DCS5 - DCS4 MET5
DB3 DW 108 DCS 55 - MET7 DCS6 - DCS4 MET6
DB3 DW 110 DCS 56 - MET7 DCS7 - DCS4 MET7
DB3 DW 112 DCS 57 - MET8 DCS1 - DCS4 MET8
DB3 DW 114 DCS 58 - MET8 DCS2 - DCS4 MET9
DB3 DW 116 DCS 59 - MET8 DCS3 - DCS4 MET10
DB3 DW 118 DCS 60 - MET8 DCS4 - DCS4 MET11
DB3 DW 120 DCS 61 - MET8 DCS5 - DCS4 MET12
DB3 DW 122 DCS 62 - MET8 DCS6 - DCS4 MET13
DB3 DW 124 DCS 63 - MET8 DCS7 - DCS4 MET14
DB3 DW 126 DCS 64 - MET9 DCS1 - DCS4 MET15
DB3 DW 128 DCS 65 - MET9 DCS2 - -
DB3 DW 130 DCS 66 - MET9 DCS3 - DCS5 MET1
DB3 DW 132 DCS 67 - MET9 DCS4 - DCS5 MET2
DB3 DW 134 DCS 68 - MET9 DCS5 - DCS5 MET3
DB3 DW 136 DCS 69 - MET9 DCS6 - DCS5 MET4
DB3 DW 138 DCS 70 - MET9 DCS7 - DCS5 MET5
DB3 DW 140 DCS 71 - MET10 DCS1 - DCS5 MET6
DB3 DW 142 DCS 72 - MET10 DCS2 - DCS5 MET7
DB3 DW 144 DCS 73 - MET10 DCS3 - DCS5 MET8
DB3 DW 146 DCS 74 - MET10 DCS4 - DCS5 MET9
DB3 DW 148 DCS 75 - MET10 DCS5 - DCS5 MET10
DB3 DW 150 DCS 76 - MET10 DCS6 - DCS5 MET11
DB3 DW 152 DCS 77 - MET10 DCS7 - DCS5 MET12
DB3 DW 154 DCS 78 - MET11 DCS1 - DCS5 MET13
DB3 DW 156 DCS 79 - MET11 DCS2 - DCS5 MET14
DB3 DW 158 DCS 80 - MET11 DCS3 - DCS5 MET15
DB3 DW 160 DCS 81 - MET11 DCS4 - -
DB3 DW 162 DCS 82 - MET11 DCS5 - DCS6 MET1
DB3 DW 164 DCS 83 - MET11 DCS6 - DCS6 MET2
DB3 DW 166 DCS 84 - MET11 DCS7 - DCS6 MET3
DB3 DW 168 DCS 85 - MET12 DCS1 - DCS6 MET4
DB3 DW 170 DCS 86 - MET12 DCS2 - DCS6 MET5
DB3 DW 172 DCS 87 - MET12 DCS3 - DCS6 MET6
DB3 DW 174 DCS 88 - MET12 DCS4 - DCS6 MET7
DB3 DW 176 DCS 89 - MET12 DCS5 - DCS6 MET8
ISO 9001