Training Center
Power Plant Course-Level 1
IndustrialNetwork
Oct2007Rev.1
Page 1 of 293
1. SIMATIC NET Profibus
7. Configuring the CP
Industrial Networks
8. Programming with the SEND/RECEIVE
Interface
Page 2 of 293
PROCESS FIELD BUS
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.1
Contents:
Basic Properties of PROFIBUS........................................................................................... 2
Access Procedure ............................................................................................................... 3
PROFIBUS Profiles FMS and DP ....................................................................................... 4
Communication with PROFIBUS-DP ..................................................................................5
Communication with PROFIBUS-FMS ............................................................................... 7
FMS, the PROFIBUS User Interface .................................................................................. 8
Combimaster Operation ......................................................................................................9
Segment Configuration ....................................................................................................... 10
Range of a Network Segment (Two-Wire Cable) ............................................................... 11
SIMATIC NET PROFIBUS: FO (Fiber Optic) .....................................................................12
SIMATIC NET PROFIBUS Properties: FO OLM .............................................................. 13
SIMATIC NET PROFIBUS: FO OLM - Bus Configuration ................................................. 16
SIMATIC NET PROFIBUS: FO OLM - Double Ring Configuration ................................... 17
SIMATIC NET PROFIBUS: FO OLM/S-1300 .................................................................... 18
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 3 of 293
page 1
The PROFIBUS PROCESS FIELD BUS
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.2
Master Devices Master devices take the initiative in data traffic on the bus. A master may send messages
without an external request, if it has authorization to access the bus (token). Masters are
also designated as active nodes in the PROFIBUS protocol.
Slave Devices Slave devices are simple input/output devices I/Os. Typical slave devices are sensors,
actuators, and transducers. Slave devices do not receive bus access authorization. Slave
devices may only acknowledge messages received or send messages to a master upon
request. Slaves are also referred to as passive nodes. Slaves require only a small part of
the bus protocol. This makes it particularly uncomplicated to implement the bus protocol.
Transmission Speed 9.6 - 19.2 - 93.75 - 187.5 - 500 - 1500 Kbit/s , 3 - 6 - 12Mbit/s adjustable in steps.
Max. Bus Length 100m at 12Mbit/s, 200m at 1500 Kbit/s, 1200m at 93.75 Kbit/s
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 4 of 293
page 2
PROCESS FIELD BUS
The PROFIBUS
Access Procedure
(1)
(2)
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.3
PROFIBUS Data The Data Link Layer implements the function of bus access control, data protection,
Link Layer handling the transmission protocols, and the message frames. The Data Link Layer
(Layer 2) is referred to as a Fieldbus Data Link (FDL) in PROFIBUS.
Bus Access Control The bus access control system specifies the procedure which determines the time when a
bus node (station) can send data. The bus access control system must ensure that only
one node has send authorization at a given time.
Bus Access Control Two significant requirements were taken into consideration for the PROFIBUS
Requirements protocol: On the one hand, for communication between complex, programmable logic
controllers of equal status (Masters) it must be ensured that each node has sufficient
opportunity to carry out its communication tasks within a defined timebase.
On the other hand, cyclic data exchange with as few requirements as possible must be
implemented for communication between a complex programmable logic controller and
the simple I/O devices assigned to it (Slaves).
Token Passing The token passing procedure guarantees the allocation of the bus access
Procedure authorization (the Token) within a set time. The token frame, a special message frame for
transferring the send authorization from one master to the next master, must be passed to
all masters once in sequence within a (parameter-assignable) maximum token rotation
time. The token passing procedure is used only between complex nodes (masters) in
PROFIBUS.
Master-Slave The master-slave procedure makes it possible for the master (active node), currently
Procedure in possession of the send authorization, to address the slave devices (passive nodes)
assigned to this master. The master can send messages to the slaves or fetch messages
from the slaves.
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 5 of 293
page 3
PROCESS FIELD BUS
The PROFIBUS
PROFIBUS-FMS
PROFIBUS-DP
DP Distributed I/Os
FMS Fieldbus Message Specification
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.4
PROFIBUS-DP PROFIBUS-DP was conceived for fast data exchange at the sensor-actuator level. Central
control devices (such as programmable logic controllers) communicate here by means of
a fast, serial connection with distributed input and output devices. Data exchange with
these devices primarily takes place cyclically.
The central controller (master) reads the input information from the slaves and writes the
output information to the slaves.
The bus cycle time must be shorter than the program cycle time of the central controller.
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 6 of 293
page 4
PROCESS FIELD BUS
The PROFIBUS
Communication with PROFIBUS DP
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.5
System ConfigurationThe specifications for the system configuration consist of the number of stations, the
assignment of the station address to the I/O addresses, data consistency in the I/O data,
diagnostics message format, and the bus parameters used.
Device Types Each PROFIBUS-DP system consists of different types of devices. Three device types
are differentiated, depending on the respective task definition:
DP Master Class 1 This is a central controller that exchanges information with the distributed stations (DP
slaves) in a specified message cycle. Typical devices, for example, are programmable
logic controllers (PLC), computerized numeric controls (CNC), or robotic controls (RC).
DP Master Class 2 Devices of this type are programming devices, configuring devices, or diagnostics
devices. These devices are used during start-up to create the configuration of the DP
system.
DP Slaves A DP slave is an I/O device (sensor/actuator) that reads in input information from and
outputs output information to the process.
The amount of input information and output information depends on the device.
Mono-Master System There is only one active master on the bus in this system configuration. The shortest bus
cycle time is attained with this operating mode.
Multi-Master System There are several masters, such as additional configuring devices and diagnostics
devices, or several subsystems independent of each other, on a bus.
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 7 of 293
page 5
PROCESS FIELD BUS
The PROFIBUS
PROFIBUS DP
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.6
Data Exchange DP Master1 (DPM1) handles data exchange between itself and the DP slaves assigned to
it automatically in a specified, constantly recurring sequence. During bus system
configuration, the user specifies that a DP slave belongs to DPM1.
Data Traffic Phases Data traffic between DPM1 and the DP slaves is divided into the parameter assignment
phase, the configuring phase, and the data transfer phase.
Before a DP slave can be included in the data transfer phase, DPM1 checks whether the
setpoint configuration coincides with the actual device configuration during the parameter
assignment and configuring phase.
The device type, format information, length information, and the number of inputs and
outputs must be in agreement during this check.
Combi Operation The common operation of PROFIBUS-FMS and PROFIBUS-DP components on one
DP/FMS bus is a particular advantage of PROFIBUS. Combi operation is possible for applications
with less exacting system response time requirements.
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 8 of 293
page 6
PROCESS FIELD BUS
The PROFIBUS
Multi-Master operation:
Slave Slave Send authorization passes from
one master to the other
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.7
FMS Communication FMS enables object-oriented communication. The following terms are significant for
Terminology understanding FMS communication:
Application association between two partners
Virtual field device (VFD)
Communications objects in the object list
Object access (for example, variables)
Services (Variable services)
Client-Server A client is an application process that accesses objects in the partner by means of.
Relationship requests.
A server is a service provider which makes the communications objects available to the
client.
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 9 of 293
page 7
PROCESS FIELD BUS
The PROFIBUS
FMS, the PROFIBUS User Interface
User services:
Variable Access
(reading and writing variables)
Program Invocation
(combining domains to form a program and controlling program
execution)
Domain Management
(loading logically connected memory areas: domains)
Event Management
(services for user-controlled interrupt processing)
Management services:
VFD Support (services providing information about the device)
Object list management (reading/writing the object list)
Context Management (establishing, clearing and cancelling a
connection)
VFD= Virtual Field Device
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.8
FMS Communication To enable universal application of the bus system, PROFIBUS-FMS specifies a very
wide function range.
The FMS services are divided into the following groups:
Context Managament Services make it possible to set up and end logical connections,
as well as to reject non-permissible services.
Variable Access Services make access to simple variables, records, arrays, and
variable lists possible.
Domain Management Services make it possible to transfer contiguous memory areas.
During the transfer, large amounts of data from the application process are subdivided
into segments.
Program Invocation Management Services make program control possible
(START,STOP, etc.)
Event Management Services make transfer of interrupt messages possible.
The VFD Support Services make identification and status scanning of a device
possible.
OL Management Services make reading and writing object lists possible.
Profiles It is necessary to coordinate the range of functions actually required with the concrete
requirements for the various application areas.
Application-specific specifications (profiles) make this selection.
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 10 of 293
page 8
PROCESS FIELD BUS
The PROFIBUS
Combimaster Operation
only S5
for example, FMS and DP interface
Combi- Combi- SIMATIC S7 in one master module:
FMS with
master master Transfer of larger amounts of data
FMS-CP between the masters with FMS
DP Connecting I/Os with DP
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.9
Mixed Operation The common operation of PROFIBUS-FMS and PROFIBUS-DP components on one bus
is a particular advantage PROFIBUS offers. Mixed operation of PROFIBUS-FMS and
PROFIBUS-DP components on one bus is possible and advisable for applications which
make less exacting demands on the system response time. Even the simultaneous
operation of both protocol versions in one device is possible.
Combimaster The communications processors (CP) with these two protocol versions are referred to as
combimasters.
Combislave Slave interfaces with these two protocol versions are called combislaves
(ET200U DP/FMS).
Device Variety The variety of devices is reduced, because the same device can be used either for fast,
cyclic data transfer with PROFIBUS-DP or with the powerful PROFIBUS-FMS services.
Task Division For example, the FMS services can be used for non-time critical parameter assignment
during commissioning, and the fast DP functions for the cyclic transfer of user data in the
operating phase of a closed-loop controller.
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 11 of 293
page 9
PROCESS FIELD BUS
The PROFIBUS
Segment Configuration
Repeater
Bus terminal
...
Bus connector
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.10
Electrical Network The basic version of PROFIBUS uses closed-circuit transmission, according to the EIA
RS-485 US standard. This version is used for applications in the area of production
engineering, building services management systems, and drives engineering.
Two-Wire Cable The electrical PROFIBUS network is a shielded, twisted, two-wire cable. The RS 485
interface works with voltage differential signals.
Connection System The nodes are connected to the PROFIBUS bus system by means of a bus connector or a
bus terminal.
Segment Length The maximum segment length depends on the transmission speed.
Transmission Speed The transmission speed can be adjusted in steps from 9.6 Kbit/s to 1.5Mbit/s. Additional
transmission speeds of 3.6 and 12Mbits/s are possible for extremely time-critical DP
applications and shorter distances.
12 Mbit Repeater Up to 9 repeater cascades are possible with the 12 Mbit repeater.
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 12 of 293
page 10
PROCESS FIELD BUS
The PROFIBUS
Range of a Network Segment (Two-Wire Cable)
9.6 1000
19.2 1000
93.75 1000
187.5 800
500 400
1500 200
3,6,12000 100
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.11
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 13 of 293
page 11
PROCESS FIELD BUS
The PROFIBUS
SIMATIC NET PROFIBUS: FO (Fiber Optic)
Star, bus, and ring structures with Optical Link Modules OLM
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.12
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 14 of 293
page 12
PROCESS FIELD BUS
The PROFIBUS
SIMATIC NET PROFIBUS Properties: FO OLM
Cascading
OLM = Optical Link Module
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.13
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 15 of 293
page 13
PROCESS FIELD BUS
The PROFIBUS
SIMATIC NET PROFIBUS Properties: FO OLM
Control functions
Connectable echo function, continuous signal monitoring
Automatic network test during start-up
Operational signalling and error signalling
IP 40 degree of protection
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.14
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 16 of 293
page 14
PROCESS FIELD BUS
The PROFIBUS
V O LT A G E
SE LE C TO R
230V
CH 3 CH 4 CH 3 CH 4 CH 3 CH 4
L1
115/230V AC
N
CH 1 CH 1 CH 1
L+
24V DC
M A A A
CH 2 CH 2 CH 2
B B B
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.15
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 17 of 293
page 15
PROCESS FIELD BUS
The PROFIBUS
SIMATIC NET PROFIBUS: FO OLM - Bus
Configuration
CH 1 CH 1 CH 1 CH 1
CH 4 CH 3 CH 4 CH 3 CH 4
CH 2 CH 2 CH 2 CH 3
CH 2
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.16
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 18 of 293
page 16
The PROFIBUS PROCESS FIELD BUS
CH 1 CH 1 CH 1 CH 1
CH 3 CH 4 CH 3 CH 4 CH 3 CH 4
CH 2 CH 2 CH 2 CH 3 CH 4
CH 2
Max. distances between two OLMs (max. 7 OLMs cascaded, max. 10 km ring circumference)
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.17
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 19 of 293
page 17
PROCESS FIELD BUS
The PROFIBUS
CH 3 CH 3 CH 3
max. 15 km max. 15 km
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7Kdp_Ov.18
Trainings-Center 7Kdp_Ov
for Automation and Drives Page 20 of 293
page 18
Integrated PROFIBUS Interface
PROFIBUS
Contents: Page
PROFIBUS
Interfaces.......................................................................................................... 2 Example
of a PROFIBUS Application ................................................................................. 3
Available DP
Slaves............................................................................................................. 4 Inserting
DP Slaves.............................................................................................................. 5
Assigning
Parameters to DP Slaves ................................................................................... 6 Placing
the Module for the Modular DP Slave..................................................................... 7
Activating the
PROFIBUS-DP-Application........................................................................... 8
Display Elements for PROFIBUS ...................................................................................... 9
Exercise 1: Outputting to a DP Slave.................................................................................9
Error/fault Analysis in OB86 when Slave Failure Occurs.....................................................12 Slave
diagnosis(1)............................................................................................................... 13 Slave
diagnosis(2)............................................................................................................... 14
Online diagnosis ............................................................................................................... 15
DP - Diagnosis blocks (1) .................................................................................................. 16
DP - Diagnosis blocks (2) ................................................................................................... 17
Exercise 2: Slave Diagnosis............................................................................................... 18
Writing
Consistent Data to DP Standard Slaves.................................................................. 20
Reading
Consistent Data from DP Standard Slaves........................................................... 21
Trainings-Center 7KdpInt
for Automation and Drives
Page 21 of 293
page 1
PROFIBUS Interfaces
PS SIEMENS IM
(maximum
8 units)
ET200M
DP-Slave
IM
153-1
S7-300 S7-300
The CPUs with an integrated PROFIBUS master interface make is possible to have a distributed
programmable logic controller configuration with a high speed and easy handling.The distributed
peripheral is treated like a central peripheral from the users viewpoint, that is, the same configuring,
addressing, and programming.
Trainings-Center 7KdpInt
for Automation and Drives
Page 22 of 293
page 2
Example of a PROFIBUS Application
SIMATIC S7-400
PG
PS S7 S7 S7
10A 400 Master
PG 720
CPU
414-
2 DP
MPI cable
PROFIBUS DP
DP
STAND. DP
SLAVE STAND.
SLAVE
CP 342-5DP, CP 443-5DP
The option software NCM S7 is requried for parameter assignment, commissioning and
test.
Trainings-Center 7KdpInt
for Automation and Drives
Page 23 of 293
page 3
Available DP- Slaves
consists of an interface module and
modules from the S7- 300 module spectrum
ET 200M
Trainings-Center 7KdpInt
for Automation and Drives
Page 24 of 293
page 4
Inserting DP Slaves
Inserting DP Slaves
To nsert and configure DP slaves, proceed as follows:
A configuration table is attached to the symbol, that represents the I/O design of the DP
slave.
Trainings-Center 7KdpInt
for Automation and Drives
Page 25 of 293
page 5
Assigning Parameters to DP Slaves
You can read, enter, or change DP Slave parameters in the register "General".
Diagnostics Address In this field STEP 7 gives a default address for diagnostics, which you can also change. In
the case of a fault, an interrupt is signalled in the CPU giving this address. The CPU then
starts OB 86 Rack-/DP-Slave failure.
Nodes In "Nodes" you find the command button "PROFIBUS ...". If you have already assigned a
Profibus address to the module, then the Profibus address appears next to the command
button.
With this, the properties of the corresponding subnets can be changed, if necessary.
Response With response monitoring, it is possible for the DP Slave to react to a fault
Monitoring from the DP-Master or to an interruption of the data exchange on the bus.
If the DP-Slave has no response within the configured response monitoring time, then it
goes into the secure state (all outputs are set to 0 or substitute value output).
Trainings-Center 7KdpInt
for Automation and Drives
Page 26 of 293
page 6
Placing the Module for the Modular DP Slave
With modular DP slaves, the possible modules in the window Hardware Catalog are
placed underneath the associated DP slave Family!
2. Drag the module per Drag&Drop into the associated rack line
(Configuration table).
3. Repeat steps 1 and 2, until the rack is completely fitted with components.
I/O Addresses Every input /output is assigned exactly one address, via which the input/output responds.
This address is automatically assigned by STEP 7 (can naturally be changed) and is
entered in the configuration table under "I-Addr" or "Q-Addr" as well as "Length".
Trainings-Center 7KdpInt
for Automation and Drives
Page 27 of 293
page 7
Activating the PROFIBUS-DP-Application
e.g. CPU 315-2 DP
Slot for
SIEMENS Memory Card
SF SF DP
BATF BUSF
DC5V
FRCE
RUN
STOP
RUN-P 9-pole
RUN interfaces
o
STOP
Compartment for MRES
Backup Battery
or Accu
Procedure: Using the PG, download the configuration that was created with STEP7 into the CPU
(e.g.CPU 315-2 DP). The mode selector must be in the STOP position for this.
Switch on all DP-Slaves.
Switch the CPU from STOP to RUN.
CPU Behaviour During Start-up:
During start-up the CPU compares the set configuration with the actual configuration. The
duration of the comparison is set by you in the CPU Properties/Start-up.
If the set configuration = actual configuration, the CPU goes into RUN.
If the set configuration >< actual configuration, then the behaviour of the CPU depends on
the parameter setting "Start-up for set >< actual configuration" .
Start-up = yes: CPU goes into the RUN state.
Start-up = no: CPU remains in Stop. After the default monitoring time
has elapsed, the BUSF-LED flashes. This means that the
configuration differs from the set configuration or at least
one slave does not respond.
Trainings-Center 7KdpInt
for Automation and Drives
Page 28 of 293
page 8
Display Elements for PROFIBUS
This table describes the LEDs allocated to the PROFIBUS DP when the
CPU 315-2 DP has been configured as a DP - Master.
Trainings-Center 7KdpInt
for Automation and Drives
Page 29 of 293
page 9
Exercise 1:
Place the clock memory byte on the
ET 200M.
Trainings-Center 7KdpInt
for Automation and Drives
Page 30 of 293
page 10
Exercise 1: Output to the DP Slave
Trainings-Center 7KdpInt
for Automation and Drives
Page 31 of 293
page 11
Error/fault Analysis in OB 86 when Slave Failure Occurs
The CPU operating system (CPU 315-2DP or S7-400) activates the OB86, if it recognizes the failure
of a rack, a subnet or a distributed I/O station not only in a coming but also a going event.
If you have not programmed the OB86 and such an error arises, the CPU goes into the STOP mode.
Bit 0 to 7:
Contents:
!!
Number of the DP-Station (PROFIBUS-Address)
Bit 8 to 15: DP-Subnet-ID
Bit 16 to 30: Logical base address of theDP-Slave
(Diagnostics address)
Bit 31: I/O identifier
Trainings-Center 7KdpInt
for Automation and Drives
Page 32 of 293
page 12
Slave diagnosis(1)
Slave Diagnosis With SFC 13 "DPNRM_DG" (read diagnosis data of a DP slave), you read the diagnosis
data for a DP slave in the form specified by DIN 19245, Part 3, Profibus. After fault-free
data transfer, the read data are entered in the destination area set up by RECORD (OUT
2).
You start the read procedure by assigning 1 to the REQ (IN0) input parameter during the
SFC 13 call-up.
Trainings-Center 7KdpInt
for Automation and Drives
Page 33 of 293
page 13
Slave diagnosis(2)
Slave Diagnostics You can refer to the following table for the configuration of slave diagnostics
Configuration data in principle. Refer to the manuals for the DP slaves for additional information.
Byte Significance
0 Station status 1
1 Station status 2
2 Station status 3
3 Master station number
4 Manufacturers ID (high byte)
5 Manufacturers ID (low byte)
6... Additional slave-specific diagnostics
Trainings-Center 7KdpInt
for Automation and Drives
Page 34 of 293
page 14
Online diagnosis
Diagnosis Hardware This button opens the accessible online station configuration. Information about the status
or operating mode of the module is displayed in the module symbol. F5 updates the
display.
Trainings-Center 7KdpInt
for Automation and Drives
Page 35 of 293
page 15
DP - Diagnosis blocks (1)
Diagnosis Blocks For the diagnostic evaluation of a distributed configuration with PROFIBUS-DP and
SIMATIC S7, there are two different blocks available in the Internet for the user program:
z FC 99 is the simpler version and only evaluates the information "which bus node has
failed or malfunctioned. Detailed information cannot be displayed with this block.
Call in STEP 7 Both blocks are jointly offered as an archived Step 7 - Project as a self-extracting file
"diag_12.exe. A double-click results in the Project "Diag_12, which can be opened with
the SIMATIC Manager. Inserting the desired blocks into the respective user program is
then easily possible with "Copy.
Attention These blocks support all masters with the exception of CP 342-5.
Trainings-Center 7KdpInt
for Automation and Drives
Page 36 of 293
page 16
DP - Diagnosis blocks (2)
FB 99 The DP diagnosis block FB99 carrys out the detailed evaluation of a DP master system.
This block determines interrupt-driven, failed and malfunctioned DP slaves including the
cause of the malfunction. All interrupts are delayed during FB processing.
This call (including the same instance data block number and the same user current
address) must, in each case, be made in the organization blocks OB1, OB82 and OB86.
The sequence and the contents of the 20 byte temporary local data of the three
organization blocks may not be changed, can however be expanded at any time.
At the same time, up to 16 diagnostic messages can be evaluated via the OB82. If more
than 16 diagnostic messages are received at the same time, the DIAG_OVERFLOW bit
(diagnostic overflow) is set. The messages greater than 16 can no longer be evaluated. In
this case it is recommended that a RESET be performed so that the evaluation is re-
initialized.
FC 99 The DP diagnosis block FC99 carrys out the evaluation of a DP master system. This block
determines cyclically the failed or malfunctioned slaves. The use of this block is
recommended, in particular, when only one overview diagnosis of the entire bus system is
to be displayed.
Trainings-Center 7KdpInt
for Automation and Drives
Page 37 of 293
page 17
Exercise 2:
Trainings-Center 7KdpInt
for Automation and Drives
Page 38 of 293
page 18
Exercise 2: Slave Error Analysis
Trainings-Center 7KdpInt
for Automation and Drives
Page 39 of 293
page 19
Writing Consistent Data to DP Standard Slaves
You need SFC 15 "DPWR_DAT," because you can write a maximum
of four bytes contiguously with the transfer commands that access
the peripheral or the process-image input table.
Function With SFC 15 "DPWR_DAT" (write consistent data to a DP standard slave), you transfer
the data in the RECORD consistently to the addressed DP standard slave. The data
length must be three or more than four bytes. The maximum length is specified CPU
specifically. You can refer to the technical data of your CPU for this information. Data
transfer takes place synchronously, that is, the write procedure concludes after the SFC
ends.
The source area must have the same length you configured for the selected module with
STEP 7.
You can access only one module from the DP slave for a DP standard slave with a
modular configuration.
Example
Trainings-Center 7KdpInt
for Automation and Drives
Page 40 of 293
page 20
Reading Consistent Data from DP Standard Slaves
You need SFC 14 "DPRD_DAT," because you can only read out a
maximum of four bytes contiguously with the load commands that
access the peripheral or the process image input table.
Function With SFC 14 "DPRD_DAT" (read consistent data of a DP standard slave), you read out
the consistent data of a DP standard slave. The data length must be three or more than
four bytes, and the maximum length is CPU specific. You can refer to the technical data
for your CPU for more information. If no error occurred during the data transfer, the read
in data are entered in the destination area that RECORD set up.
The destination area must have the same length you configured for the selected module
with STEP 7.
With a SFC 14 call-up, you can access only the data for a module/DP identifier under the
configured start address for a DP standard slave with a modular configuration.
Example
Trainings-Center 7KdpInt
for Automation and Drives
Page 41 of 293
page 21
Configuring FDL Connections
(PLC-PLC)
PLC 1 PLC 2
CP CP
PROFIBUS
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7KdpPlc.1
Contents
Overview.............................................................................................................................. 3
PLC - PLC Connections ..................................................................................................... 4
Configuring, drawing a "wiring diagram.............................................................................. 6
Communication relationships ..............................................................................................7
LSAPs for FDL connections ................................................................................................ 8
FDL connection between 2 PLCs ....................................................................................... 9
Appendix ............................................................................................................................. 14
Trainings-Center 7KdpPlc
for Automation and Drives Page 42 of 293
page 1
Communication
SIMATIC S7 / PROFIBUS
Task
A certain amount of data is to be transmitted from a data block (DB11) in PLC 1 to a vacant
space in a data block (DB12) in PLC 2.
PLC 1 PLC 1
CP CP
PROFIBUS
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7KdpPlc.2
Trainings-Center 7KdpPlc
for Automation and Drives Page 43 of 293
page 2
Communication
Overview
CP 342-5 CP 342-5
PROFIBUS
PLC CP CP PLC
Communi- Communi-
CPU cations cations CPU
processor processor
FC FC
"SEND" "RECEIVE"
PROFIBUS
Data Data
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7KdpPlc.3
Trainings-Center 7KdpPlc
for Automation and Drives Page 44 of 293
page 3
Communication
PLC - PLC Connections
S7 - 300 S5
S5-115U/135U/155U
PROFIBUS
DATA
"FDL connection"
DATA
DATA
"FDL connection"
DATA
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7KdpPlc.4
Trainings-Center 7KdpPlc
for Automation and Drives Page 45 of 293
page 4
Communication
PROFIBUS: Transmitting data via an FDL connection
SIMATIC PLC 1 SIMATIC PLC 2
Program Program
in the CPU CP342-5 CP342-5 in the CPU
FC FC
240-byte 240-byte
data Acknowledgement data
source destination
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7KdpPlc.5
Trainings-Center 7KdpPlc
for Automation and Drives Page 46 of 293
page 5
Communication
Configuring, drawing a "wiring diagram"
PLC 1
CP342-5
Conn 1
Conn 2
Conn 3
PROFIBUS
Conn 4
Conn 5
Conn 9
Conn 6 Conn 7 Conn 8
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7KdpPlc.6
Trainings-Center 7KdpPlc
for Automation and Drives Page 47 of 293
page 6
Communication
Communication relationships
x
User program User program
y
Communication relationships Communication relationships
ID Connection x Connection x ID
ID-1 S Connection y Connection y R ID-1
ID Connection z Connection z ID
CP342-5 CP342-5
PROFIBUS
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7KdpPlc.7
Trainings-Center 7KdpPlc
for Automation and Drives Page 48 of 293
page 7
Communication
Example: FDL connection between 2 PLCs
+1
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7KdpPlc.8
Trainings-Center 7KdpPlc
for Automation and Drives Page 49 of 293
page 8
Communication
Example: FDL connection between 2 PLCs
PLC 1
Advantages:
PLC 2
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7KdpPlc.9
Trainings-Center 7KdpPlc
for Automation and Drives Page 50 of 293
page 9
Communication
Example: FDL connection between 2 PLCs
CP 1 CP 2
Local Local
LSAP:6 LSAP:2
"House number" "House No."
PROFIBUS ADDR: "Mailbox" PROFIBUS
"Mailbox"
1 ADDR: 5
PROFIBUS
FDL connection
Data
Data
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7KdpPlc.10
Trainings-Center 7KdpPlc
for Automation and Drives Page 51 of 293
page 10
Communication
Example: FDL connection between 2 PLCs
Example of an
FDL connection
PLC 1 CP 1 CP 2 PLC
Sending and receiving
PROFIBUS ADDR: 1 via an LSAP PROFIBUS ADDR:5
LSAP 6 LSAP 2
ID 1 1 1 1 ID
FC DATA FC
SEND SEND RECEIVE
RECEIVE
Acknowledgement
ID 1 1 DATA 1 1 ID
FC RECEIVE Acknowledgement
FC
RECEIVE SEND SEND
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7KdpPlc.11
Trainings-Center 7KdpPlc
for Automation and Drives Page 52 of 293
page 11
Communication
Example: FDL connection between 2 PLCs
CPU
CP 342-5
Network parameters
HSA , baud rate , profile
FC Connection table
FC local ID local ID
1 n
RECEIVE
PROFIBUS station address
PROFIBUS
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7KdpPlc.12
Trainings-Center 7KdpPlc
for Automation and Drives Page 53 of 293
page 12
Communication
Example: FDL connection between 2 PLCs
1. Assign parameters to CP
PG
NCM S7 for
CP 342-5
PROFIBUS
package
2. Program CPU
PG
STEP 7
CPU
package
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7KdpPlc.13
Trainings-Center 7KdpPlc
for Automation and Drives Page 54 of 293
page 13
Communication
Appendix
Data transmission via FDL connections using FCs
Short ACK
SEND Destination
TOKEN
Trigger: SEND RECV
TOKEN
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7KdpPlc.14
Trainings-Center 7KdpPlc
for Automation and Drives Page 55 of 293
page 14
Communication
Appendix
Data transmission via FDL connections using FCs (special cases)
Source
SDA low
SEND
Trigger: SEND TOKEN
PROFIBUS
header SDA low
TOKEN
SIMATIC NET
Siemens AG 1998. All rights reserved.
date: 27.12.2004
Information- and Trainings-Center
Knowledge for automation
file: 7KdpPlc.15
Trainings-Center 7KdpPlc
for Automation and Drives Page 56 of 293
page 15
Introduction to SIMATIC NET Industrial Ethernet
ISO/OSI
Contents: Page
Data flow
Planning
- Management
- Production
Production management
Process control
Local control
Sensors, COROSOP15
actuators, K1 K2 K3 K4
K5 K6 K7 K8
8 DEL
drives K9 3
HELP
SHIFT
Ethernet, The bus systems of the SIMATIC NET family are ideally suited for this
PROFIBUS, purpose.
AS Interface
PLC, PC
Field Level Drives
Valves
Actuator- Actuators
Sensor- Sensors
Level
Actuator-
Sensor Bits Milliseconds Milliseconds
Level
Cell Level
PROFIBUS
Field Level
Actuator- Actuator-
Sensor Sensor
Interface Level
Cost Savings
Savings on installation and cabling costs
Flexibility
Fast "rewiring"
Maximum Reliability
Optimized for industrial use:
Shielded cables or fiber-optic cables
Special protocols for the requirements of industry
Powerful Test and Diagnostics Functions
Fast configuration testing
Startup simplified by diagnostics functions
Optimized
The right network for every application
Standardized
Ethernet, PROFIBUS, AS Interface
Open
Customers are not dependent on one manufacturer
Popular
Already being used by a large number of customers
Future-Oriented
Innovation and continuous product improvement
Triaxial cable
Fan-out
Star unit
coupler
KYDE
Technical Specifications
SIEMENS SIEMENS
ET200C ET200C
Line
Ring
RS 485
FO
OLM
Actuator / Sensor
with AS-I-ASIC AS-I Hub
AS Interface AS Interface
Slave ASIC Bus Cable
Technical Specifications
Protocols AS Interface
Application-oriented
Transport-oriented
Application Layer The communication task to be performed and the functions and services
-7- to be provided for it are established here.
Presentation Layer The communication partner needs to be told how the data it is about to
-6- receive is presented (for example, whether a circle is to be interpreted as a circle,
a letter O or as the figure 0). The "private" data presentation of the individual
nodes is converted to the standard presentation of the communication system.
Session Layer This layer provides functions necessary for opening, correctly conducting and
-5- terminating a communication session. It provides facilities for structured,
controlled transmission of large quantities of data.
Transport Layer This layer provides error detection and correction facilities to ensure smooth
-4- transport of messages between nodes (e.g. acknowledgement and repetition). It
also includes control of the flow of information in accordance with the capacity of
the receiver to receive and process it (flow control).
Network Layer The routes to be taken and the addresses to be used for transmitting the
-3- messages through the various stages of its journey (LANs, postal networks, etc.)
are defined here.
Data Link Layer This is where arrangements are made for accessing common communication
-2- media and the reliability of the physical layer between the communication
partners is ensured.
Physical Layer This layer is concerned with the physical conditions for transmitting a
-1- message, e.g. the speed (which varies according to the transmission medium
used), etc.
Industrial Ethernet
Communication
partner
AG
DP - RAM
CP
Layer n + 1
Service interface n
Service interface n - 1
Principle A working unit in layer n receives a job from layer n+1 via the n/n+1 interface. To
carry out the job, it uses its own resources and those provided by layer n-1 in
response to the relevant job orders.
Apart from communicating with layers n+1 and n-1 (via the n+1/n and n/n-1
interfaces respectively), layer n can communicate with its "partner layer" n' in
another system. This communication does not take place direct, but always via
the route n-1, n-2, ..., 1, 1 ... n'-2, n'- 1 , where ' indicates the layers of the other
system.
In accordance with the definition, only layers n and n' can communicate with one
another horizontally. Communication between corresponding layers n and n' is
also referred to as virtual.
n+1 n+1
n n
n-1 n-1
Terminology In order to understand the layer model, it is important to know the meaning of the
following terms:
z Protocol
z Service
z Interface
In addition to addressing the nodes and controlling the flow of data, one of the
main purposes of protocols in data communication between different computers
is to provide services to ensure the integrity of the data transmission.
The two types usually differ in the quantity of security functions, which, in turn,
has an effect on their efficiency. A connection-oriented protocol with a large
number of security functions entails a greater processing overhead in the
computer than a connectionless protocol.
The partners introduce themselves and exchange certain formalities before the
actual data interchange begins. The connection is not interrupted until both sides
are sure that they have correctly understood the information exchanged. For this
reason, connection-oriented protocols are also said to establish "virtual circuits".
Virtual circuits are used when the context of the information is important, when
the connection is to be maintained for a relatively long time, or when the integrity
of the data to be transmitted is essential. One physical (real) line can normally
carry several virtual (logical) connections.
n+1 n+1
n n
n-1 n-1
Services Services are the functions a layer in a communication partner can perform for the
next highest layer. Services can either be performed by the working units of the
layer itself or they can be ordered from the layer below.
z Establishment of a connection
Examples z Connection clearance
z Data transmission
z Addressing
z Error handling
z Segmenting
z Reassembly
z Multiplexing
z Splitting
z Expediting
z Routing
z Synchronization
z Compiling
z Coding
z Compression
:
:
:
ASAP
Medium
SERVICE z Services of subordinate layers are accessed via service access points.
ACCESS POINT z Each service access point within a computer network has a unique name,
SAP which is its
SERVICE ACCESS POINT ADDRESS
z Service requests and indications always use the service access point
address.
z Each application is assigned certain SAPs, which are unique within the
system.
z The OSI model does not stipulate how the service access points should be
Implementation
implemented in a system.
n+1 n+1
Layer n + 1
n n Service.request Service.indication
Service.confirm
Layer n
n-1 n-1
Interfaces Interfaces specify the procedures and data structures between the layers of one
communication partner.
The protocols and services for the various layers are standardized by the
ISO, but the interfaces are not!
z XTI
Examples
X/OPEN Transport Interface
published in the
X/OPEN Portability Guide 3 (PG3)
z TLI
Transport Layer Interface
in UNIX System V Release 4.0
z Socket interface
in BSD 4.2 / 4.3 - UNIX
z Handling block interface in CP 1430 for S5 PLCs
(Standard function blocks CPs)
z SEND-RECEIVE interface in CP443-1 and CP 343-1
for S7 PLCs
7 7
6 6
5 5
4 4
3 3
2 2
1 1
Sender Receiver
Medium
User Information Whilst it is being processed in the direction n, n-1, ... , 1 a message
on its Way through has further, layer-specific information added to it, which is chiefly
the Layers relevant for the transport of the message. When a message is processed in the
direction 1, ... , n-1, n, the additional information is "used up". In practice
allowance is made for this fact by putting the message in a new wrapper in every
layer and removing it again in the corresponding layer of the partner.
The major proportion of the jobs for a layer consist of passing on data again, with
modifications which do not affect its meaning. This data is not interpreted in the
layer. It may be modified (by coding or being put into a packet) and have one or
more wrappers put round it. Only the corresponding layer in the destination node
can remove the wrapper and reverse the modification (decode it, reassemble it),
so that the contents can be interpreted by the layer above.
(N) - PDU
Layer N
Layer N - 1
(N-1) - PDU
Data Structure When data is passed from one layer to another it receives a new designation.
Protocol Data Unit The protocol data unit of layer N+1, (N+1) - PDU, receives the name
Service Data Unit service data unit ((N) - SDU) in the layer below, layer N.
Protocol Control The protocol control information of this layer ((N) - PCI) is put together and
Information placed in front of the service data unit. The whole element has now become the
protocol data unit ((N) - PDE) of layer N.
This entire block of data is then passed on to the next lowest layer, layer N - 1
and receives the name service data unit ((N - 1) - SDU).
LINK Header
Network Header
Transmission Header
User Data
Link Trailer
14 Dest ADR 6
Header Source ADR
IEEE 802.3 6
Length Field 2
Data
ISO 8073
CRC Field 4
PREAMBLE 7 bytes
SFD 1 byte
DESTINATION 6 bytes
ADDRESS
SOURCE 6 bytes
ADDRESS
LENGTH 2 bytes
<46 >=46
LLC bytes bytes
min: 46 bytes
DATA max:1500 bytes
PAD
FCS 4 bytes
z The preamble and the SFD field are not strictly part of the MAC frame.
Note
z When specifying the length of MAC frames, the preamble and the SFD field
are not normally counted.
PREAMBLE 7 bytes
SFD 1 byte
DESTINATION 6 bytes
ADDRESS
SPOURCE 6 bytes
ADDRESS
LENGTH 2 bytes
<46 >=46
LLC bytes bytes
min: 46 bytes
DATA max:1500 bytes
PAD
FCS 4 bytes
I/G U/L
48 bits
Ethernet Address
Physical module address on the Ethernet. The Ethernet address is pre-assigned as follows:
Byte 4
Number for the SIEMENS "AUT" Group
Byte 1 ... 3
Number for SIEMENS
Station 1
Individual addr. 1
Multicast addr. 1
Broadcast
Station 0
Station 2 Individual addr. 0
Multicast addr. 2
Broadcast
Station 4
Individual addr. 4
Multicast addr. 2
Broadcast
Stations (nodes)
accessible Basic channel Receiver
from Station 0
1 Station 1
2 Station 2
3 Station 1 and 2
4 Stations 2, 3 and 4
5 Station 4
6 Stations 1, 2, 3 and 4
Individual address:
080006018010
Sender
09000601FFEF
is used for transmitting and receiving time-of-day message frames with the
SINEC clock transmitter or CP.
This address is fixed by the firmware and cannot be configured.
CRC CRC
Length Field z The length field takes up 2 bytes of the MAC frame
z The length field specifies the number of bytes of user data (LLC data) in the
following data field.
z The high-order byte is transmitted first.
z Caution: The length field has a different meaning in the original
Ethernet protocol.
2b LLC 802.2
2a MAC
1 Physical 802.1
802.1 802.14
802.14
IEEE 802.2 IEEE 802 divides ISO layer 2 (Link Layer) into two parts
Sublayer 2a (Medium Access Control)
Sublayer 2b (Logical Link Control)
z The LLC sublayer (IEEE 802.2) is based on the MAC sublayer and ensures:
Security of data communication
Provision of logical channels
z The MAC sublayer handles the details of the access mechanism. Its tasks
are:
Data formatting (frame creation, error protection)
Access control
2b LLC 802.2
2a MAC
1 Physical 802.1
802.1 802.14
N Integer >= 0
Nmax: Selectable, but must be compatible with the relevant MAC sublayer
0 0 0 0 0 0 0 0
The Network Layer According to the ISO reference model, the main function of layer 3 (network
Layer) is the routing of the message frames.
PREAMBLE 7 bytes
SFD 1 byte
DESTINATION 6 bytes
ADDRESS
SOURCE 6 bytes
ADDRESS
LENGTH 2 bytes
LLC
min: 46 bytes
DATA
max: 1500 bytes
PAD
FCS 4 bytes
Baseband transmission
Destin-
Destin-
Message 2 Message 1 ation 1
ation 2
A C D F
A F C E B D
B E
000000000 000000000
0 0 0 0 0 0 0 0 0
Manchester Code for duration "0"
111111111 111111111
1 1 1 1 1 1 1 1 1
Manchester Code for duration "1"
010101010 010101010
0 1 0 1 0 1 0 1 0
Manchester Code for "0" and "1" alternately
001111011 001111011
0 0 1 1 1 1 0 1 1
Manchester Code for the bit battern shown
ETHERNET ETHERNET
Local Communication Local Communication
Controller Controller
LCC/82586 LCC/82586
Manchester Code
A serial bus as transmission medium, however, only has one transmission line.
It is therefore necessary to code the timing and data information in one signal in
such a way that the receiver can reconstruct both the timing pulse and the data at
the other end.
This procedure (at the sending end) is referred to as signal formatting or bit
coding.
One of the possible codes is the Manchester Code.
Coding Convention In the first half of the pulse width for 1 bit the inverted value of the bit status is
transmitted and in the second half the non-inverted value.
1.
Check whether the line is clear, then transmit
2.
3.
CSMA/CD Whenever a node wants to transmit data, it ascertains whether the transmission
channel is clear.
(CS = Carrier Sense)
If another node has started transmitting data (almost) at the same time,
(MA = Multiple Access)
a collision occurs, which must be detected.
(CD = Collision Detect)
For a short time jamming signals are transmitted to enable the other nodes to
detect the collision.
The node then waits for a random length of time and then tries again to make the
transmission.
1.
2.
Collision detected
3.
Messages cancelled
Attempt repeated after allocated random time
SCOPE H1
z Reflectometers
Other Test
Equipment z Fiber-optic measuring instruments
Contents: Page
LEDs
Mode selector
AUI/ITP interface
15-pin sub-D
with slide lock
Functions
z SEND/RECEIVE interface
Provides a simple, optimized interface based on OSI Layer 4 for data
communication via ISO transport connections.
This is used for communication between SIMATIC S7 and
- SIMATIC S7-300/-400
- SIMATIC S5
- Computer/PC
z S7 functions
For communication between SIMATIC S7 and
- Other SIMATIC S7 stations
(S7-300 server only,
S7-400 client and server)
- HMI devices
- PCs with SOFTNET S7
This type of communication requires no further configuring of the CP443-1.
Remote programming of the CPU via the network is also implemented
(PG functions).
z Clock synchronization
The CP passes on clock synchronization frames in the following directions:
From the CPU to Industrial Ethernet via the K bus (communication bus), if
the local CPU is clock master
From Industrial Ethernet to the CPU via the K bus, if
- the remote CPU or
- a SINEC real-time transmitter or
- a CP 1430 TF
is clock master.
z Ethernet LAN
When configuring via Industrial Ethernet, you must first enter the
Ethernet (MAC) address of the CP ("node initialization").
Slots The CP can be plugged into any rack whose slots have P and K bus connections.
That is: - Central Rack CR2
- Universal Rack UR1 or UR 2
as either central controller or expansion unit
The CP can be plugged into all slots in the rack which have P and K bus
connections, apart from the slots for the power supply and the main CPU.
Note A K bus connection is essential when using Universal Rack UR1 or UR2 as an
expansion rack!
Transceiver cable
727-1 drop cable
Transceiver
Triax-Cable
Star coupler
Optical plug-in
Star coupler
Transceiver cable
Fiber-optic cable
Optical transceiver
Optical Connection The CP is connected via the AUI interface and the transceiver cable to the optical
transceiver, which, in turn, is connected via a fiber-optic cable to an optical plug-
in in the star coupler.
The TPETXD / TPETXD_N and TPERXD / TPERXD-N signals form the ITP interface
Item Quantity
LEDs
Mode selector
AUI/ITP interface
15-pin sub-D
with slide lock
Functions
z SEND/RECEIVE interface
Provides a simple, optimized interface based on OSI Layer 4 for data
communication via ISO transport connections.
This is used for communication between SIMATIC S7 and
- SIMATIC S7-300/-400
- SIMATIC S5
- Computer/PC
z S7 functions
For communication between SIMATIC S7 and
- Other SIMATIC S7 stations
(S7-300 server only,
S7-400 client and server)
- HMI devices
- PCs with SOFTNET S7
This type of communication requires no further configuring of the CP343-1.
Remote programming of the CPU via the network is also implemented
(PG functions).
z Ethernet LAN
When configuring via Industrial Ethernet, you must first enter the
Ethernet (MAC) address of the CP ("node initialization").
Installation
z Plug in the CP and screw it tight
z Connect the CP to Industrial Ethernet
z Provide 24V voltage supply
Notes
z You must use the same voltage source that is used for the CPU or IM361
z The two flaps at the front must be kept closed during operation.
When installing the module, ensure that the ventilation slits at the top and
bottom are not covered and that the air can circulate freely.
Transceiver cable
727-1 drop cable
Transceiver
Triax-Cable
The CP generates the power supply for the external transceiver and makes it
available at the AUI connection.
This 15 V voltage supply provides a current of at least 500 mA .
Optical plug-in
Star coupler
Transceiver cable
Fiber-optic cable
Optical transceiver
Optical Connection The CP is connected via the AUI interface and the transceiver cable to the optical
transceiver, which, in turn, is connected via a fiber-optic cable to an optical plug-
in in the star coupler.
The TPETXD / TPETXD_N and TPERXD / TPERXD-N signals form the ITP interface
Item Quantity
Contents Page
Ethernet CP
S7-400
S7
S7single-system
single-system SEND-RECEIVE
SEND-RECEIVE
communication
communication interface
interface
SEND-RECEIVE interface
PC
S7-300 S7-400 S5-115 to155U/H
S7-300
SEND-RECEIVE S7 protocol SEND-RECEIVE S7 protocol
SEND-RECEIVE SEND-RECEIVE
S7/M7-400
S7 protocol S7 protocol SEND-RECEIVE S7 protocol
SEND-RECEIVE SEND-RECEIVE SEND-RECEIVE
Communication The diagram shows the communication facilities possible with the
Facilities S7 protocol and SEND-RECEIVE interface.
Configuration and For connecting and configuring the Ethernet CP you need the
Diagnostics NCM S7 for Industrial Ethernet configuring software.
NCM S7 for Industrial Ethernet is installed in the same way as a STEP 7 option
package and can be called up from STEP 7.
NCM S7 for Industrial Ethernet also provides extensive diagnostics facilities for
the different types of communication.
Client Server
Ethernet
SIEMENS HMI
STEP 7 Control
NCM S7
PG 740
or
Ethernet
The CP acts as an S7 communication relay, passing on CFB
communications on Ethernet.
STEP 7
MPI connection
NCM S7 PG 720
or
Ethernet connection
Generate configuration data for each CP
and download to Ethernet CPs
Ethernet
Ethernet CP
The physical Ethernet connection between the PG with Ethernet CP and the
SIMATIC S7 with Ethernet CP must be established.
3. Make the appropriate settings in the Windows 95 Control Panel for the
the PG/PC interface to suit the CPs available on your PG and the bus
connection. The integrated help will give you detailed information.
When you have done this, the PG or STEP 7 will automatically find the way via
Ethernet to all intelligent modules in the SIMATIC S7 station.
Client Server
Ethernet
HMI
Control
PC with Ethernet CP
Requirements The physical Ethernet connection between the Ethernet CPs of the PC and S7
station to communicate with one another must be established.
Procedure To use the S7 communication facilities with a SIMATIC S7 from a PC, specify the
address of the CPU module in the SIMATIC S7 you want to access via Ethernet
in your PC application.
Client Server
Ethernet
OP
Meaning / S7 communication via Ethernet enables you to operate and monitor all the
Advantages modules in the SIMATIC S7 from HMI (human-machine interface) devices.
Requirements The physical Ethernet connection between the Ethernet CPs of the HMI device
and S7 station to communicate with one another must be established.
Procedure To use the S7 communication facilities you must specify the address of the
required module in the SIMATIC S7 on your HMI device. For more detailed
information see the manual for your HMI device (operator panel).
Client Server
Ethernet
Requirements The physical Ethernet connection between the Ethernet CPs of the two SIMATIC
S7 stations must be established.
Procedure To use the S7 communication facilities for exchanging data between two
SIMATIC S7 stations you use the connections configured in STEP 7.
Ethernet
SIMATIC S5
with Ethernet CP PG/PC with Ethernet connection
Application Data transfer via a configured transport connection is suitable for transferring a
series of data units from one Ethernet node to another.
Send-Receive Data is transferred when triggered by the user program. The interface with
Interface the user program in the SIMATIC S7 is provided by special SIMATIC S7 blocks
of the type FC (functions).
S7-400/1 S7-300/1
"Production"
system Other station
SINEC H1 subnet 1
(Industrial Ethernet)
SIMATIC S5
S7-300/2
Contents Page
Network/Project Type : More than One Subnet in More than One Project.................................. 8
1. You create one or more subnets of the required type in the project;
2. You define properties of the subnets; the default settings are usually
sufficient;
3. You establish a logical connection between the stations and the subnet;
SIMATIC Manager
The SIMATIC Manager provides all the facilities necessary for configuring
and documenting simple, modest-sized networks.
Different Types In order to be able to configure networks in STEP 7, you need to know how
of Network different types of network are represented in a STEP 7 project. The table above
shows typical configurations for stations networked using CPs.
S7-400/1 S7-300/1
"Production"
system
Ethernet (1)
(Industrial Ethernet)
S7-300/2
System In the simplest case, your system will consist of SIMATIC S7 stations that
Configuration you want to link together in one subnet, using Ethernet for example.
STEP 7 Project To do this, you create an Ethernet object in the STEP 7 project.
Representation Stations created in the same project refer to this object as soon as they are
configured as network nodes.
Production Project
Ethernet (1)
Network
objects
+ S7-400/1
+ S7-300/1
+ S7-300/2
S7-400/1 S7-300/1
"Production"
system Other station
Ethernet (1)
(Industrial Ethernet)
SIMATIC S5
S7-300/2
System Your system may contain not only SIMATIC S7 stations but also
Configuration SIMATIC S5 stations and non-SIMATIC stations.
Production Project
Ethernet (1)
Network
SIMATIC S5 objects
Other Station 1
+ S7-400/1
+ S7-300/1
+ S7-300/2
S7-400/1
Ethernet (1)
Production and (Industrial Ethernet) Ethernet CP
Plant Management
S7-400/2
System
PROFIBUS CP
PROFIBUS (1)
S7-300/1 S7-300/2
System The different functions of the stations or the size of the system may make
Configuration it necessary to have more than one network.
STEP 7 Project You can put all the subnets in one STEP 7 project. This is the simplest
Representation way of configuring the stations for communication.
Ethernet (1)
Network
PROFIBUS (1) objects
- S7-400/1
- S7-400/2
- S7-300/1
- S7-300/2
A station can be included in more than one subnet by assigning the CPs
accordingly.
S7-400/1 S7-400/2
Ethernet (1)
System For complex networks it may be more practical to divide the stations into
Configuration different objects to facilitate management.
STEP 7 Project In order to be able to address stations in other projects (e.g. Production 2),
Representation they are also configured as Other Stations in the rest of the projects (e.g.
Production 1).
Production 1
Production 2
Ethernet (1)
Ethernet (1)
Ethernet (1)
(Industrial Ethernet) Cell level
S7-400/1 Ethernet CP
PROFIBUS CP
Field level
PROFIBUS (1)
S7-300/1 S7-300/2
System If the different functions of the stations or the size of the system make it
Configuration necessary to have different types of network and you want to use different
projects to manage them, the stations in other projects can also be accessed by
configuring Other Stations.
Ethernet (1)
- S7-400/1
PROFIBUS (1)
- S7-300/1
- S7-300/2
Ethernet CP
S7-400/1
Ethernet (1)
Router
Ethernet (1)
S7-300/1
Ethernet CP
S7-400/1
S7-300/1
System If the different functions of the stations or the size of the system make
Configuration connections with stations in network structures connected by routers necessary,
the stations in other projects can be accessed by configuring "Other Stations".
Project
Ethernet (1)
- S7-400/1
Project
ETHERNET (1)
- S7-400/1
- S7-300/1
S7-400/1
Ethernet (1)
WAN
Internet
Router
Ethernet (1)
S7-300/1
Ethernet CP
S7-400/1
S7-300/1
System If the different functions of the stations or the size of the system make
Configuration connections with stations in unknown network structures necessary, the stations
in other projects can be accessed by configuring "Unspecified" connections.
Project
Ethernet (1)
- S7-400/1
Project
ETHERNET (1)
- S7-400/1
- S7-300/1
Contents Page
In NCM S7 the buttons below the tab pages apply to all tabs. This means:
CP-specific dialogs in tab index form, which are called from the
Properties dialog fields for the modules.
- Help Functions
- Readme
Startup / diagnostics
The CP in the CPs are managed in a STEP 7 project like any other SIMATIC S7 module.
STEP 7 Project The hardware is configured and the user software created and managed with
STEP 7.
Create
new
project
New Project In the SIMATIC Manager select the menu options File...New...Project or simply
click this icon. A window for a new project showing the existing projects appears.
As the default, new projects are stored in the folder c:\SIEMENS\STEP7\s7proj.
You can select a different folder by clicking the "Browse" button. You must then
enter the project name.
Do not change the ending s7p ! You click "OK" to save the new, empty project.
The window is closed.
Creating a Station Click the project with the right mouse button, choose Insert New Object
(See screenshot) and select the required station, e.g. SIMATIC 400 Station.
Click the + sign to display the new station. The individual hardware components
must be entered in this station. To do this, you must first open the station:
You can either select the menu options Edit....Open Object or
click the station with the right mouse button and select Open Object:
HW Config This automatically starts the hardware configuration tool, HW Config, with which
you enter and configure the components.
Catalog You click the Catalog icon to activate or deactivate the hardware catalog. When
you have selected a system, e.g. SIMATIC 300, the details are displayed:
Rack First you select a rack, e.g. a rail, and open it in the configurator by clicking the +
sign. The slots are then displayed. You then allocate the components, such as
power supply, CPU, CPs, signal modules, etc. to the slots.
Positioning You first select the slot and then drag and drop the required component,
Components e.g. PS407 20A, from the catalog into the rack. It is even quicker to double-click
the required component in the catalog.
The hardware configuration tool rejects most positioning errors.
Configuration data
in STEP 7 project
Purpose In order to connect your SIMATIC stations to a subnet, you must create an object
for the subnet in your project. This enables all parameters relating to the subnet
as a whole to be stored centrally.
Procedure It is advisable to create the subnet before configuring the stations, because the
SIMATIC stations can then be assigned almost automatically.
Proceed as follows:
Result: An object of the Network type is created in the project. All the
SIMATIC stations created in the project can then be connected to this
subnet.
Procedure Most of the parameters describing the properties of the Ethernet subnet have
been assigned default values. Proceed as follows to check the settings and
adjust them to suit your requirements:
1. Select the network object in the SIMATIC Manager and choose the
options Edit>Object Properties.
2. Enter an appropriate name for your subnet and any other information to
describe it in the General tab page.
The Base MAC Address is the starting address for automatic assignment of all
addresses within a project.
Since the Base MAC Address only applies to one project, you should establish
a Base MAC Address structure when you start configuring, in order to avoid
overlap with other projects.
Procedure When you install the Ethernet CP in the rack of a SIMATIC station and assign it,
you establish the logical connection between Ethernet CP and subnet.
1. Select the station in your project that you want to connect to Industrial
Ethernet via the Ethernet CP.
You select the CPs using the brief description and order number given in
the hardware catalog. The CPs are included in the catalog and available
for selection when NCM S7 is installed.
Subnet In order to activate the network connection of the Ethernet CP, proceed as
Connection follows after including the CP in the hardware configuration:
2. If required, enter a suitable name for the CP and any other information
in the Comment field.
3. Under Nodes click the "Ethernet" button for the subnet type.
4. If you have not yet created a subnet in the project or have not yet created
the required subnet, you can create a subnet now by clicking the New
button.
5. Check the address (es) and change it (them) if necessary. The next free
address (es) is (are) entered automatically as a default.
6. Activate the The node is connected to the selected network button and
select the required subnet from the Industrial Ethernet list box. Make
this selection even if the Networked button is already activated.
7. You can display the Properties dialog for the selected subnet by clicking
the relevant button.
9. Confirm your entry with OK, otherwise the network connection will not
be made.
Result: The CP is now configured as the network node for its S7 station.
Procedure You can easily obtain an overview of the network connections configured for a
SIMATIC station.
Proceed as follows:
1. In the SIMATIC Manager select the station in your project that you want to
check up on.
You will be shown the subnet connections configured for the SIMATIC
station.
You can use the check boxes under Subnet Type to select a display.
Your selection will not become effective until you click the Update
button.
Overview In addition to setting the network connection, you can also make other module-
specific settings and call up functions.
2. Choose Edit > Object Properties. A dialog box appears containing the
"General" tab page and the following tabs:
- Addresses
- Time
- Diagnostics
Addresses Tab Page The Addresses tab page shows you the address by which the user program can
address the module. You need this address when calling the FC blocks for
transport connections.
Time Tab Page You use the Time tab page to specify whether the CP is to pass on the time-of-
day synchronization frames. You need this function when there is more than one
CP in one station, because only one CP is allowed to pass on the time
synchronization messages.
Diagnostics Tab Page You can start the NCM S7 Ethernet diagnostics for the Ethernet CP from the
Diagnostics tab page.
"Production 1 "Production 2
PC/PG
S7-400/1 S7-400/2 S7-400/4
PG 720
Other
station
SINEC H1 subnet 1
S7-400/3 S7-400/5
SIMATIC S5
Overview Substitute objects must be included in a project for the following nodes in the
Ethernet subnet:
SIMATIC S5 stations
PC/PG
Connecting a One of the next steps is to assign "substitute objects" to the subnet:
Non-S7 Station
to the Subnet 1. Select the required object in the project and choose
Edit > Object Properties.
2. In the "Properties" dialog box that appears, click the "New" button on the
Node List tab page.
3. Select a subnet.
Result: The Properties - Ethernet Nodes" dialog box appears. Here you
can select the subnet, connect the station to the network and set the
address (MAC,IP). All the SIMATIC stations in the project can establish
communication connections with this substitute object.
The addresses (MAC, IP) assigned to the substitute object must also be set on
the actual station using the relevant tools (e.g. COM 1430).
Principle The configuration data for the Ethernet CP is downloaded from the hardware
configuration. All the configuration data of the S7 station is downloaded, including
the central configuration, the configuration of all the relevant DP master systems
and all parameters.
Connection Type You can download the configuration data to the S7 station via the MPI connection
or via Ethernet.
You can only use Ethernet if you have previously carried out "node initialization"
Node Initialization "Node initialization" is when you first assign a MAC or Internet address to the
Ethernet CP.
When you have performed the steps in the boxes with solid lines in the flowchart
on Pages 8 and 9, you have configured the CP sufficiently to be able to carry out
further configuration steps from the PG connected to Ethernet.
Non-Volatile In the course of downloading you can decide whether you want to download
Storage of the the configuration data all at once or step-by-step. When downloading step-by-
Configuration Data step, you will be requested to start downloading for each module separately. You
must choose this method if you want to put the configuration data into non-
volatile storage in the Ethernet CP. To do this check Copy to ROM in the
"Download" dialog for the CP.
Note
If you have assigned a new address to the Ethernet CP and have also configured
connections, you must always also download the connection configuration.
Note
When you "drag and drop" a CP to a different slot, the connection configuration
data is automatically updated. You must, however, download it again!
Overview When you select Station > Print from the Hardware Configuration dialog you can
choose one of the following options for printing out configuration data:
"All" option
Prints all the configuration data for the selected S7 station, regardless of
any other selections made.
- "Overview" option
Prints out the most important configuration data for the selected S7
station, regardless of any other selections made.
"Selection" option
Prints out all the configuration data for the selected component. This
enables you to print out only the configuration data for the Ethernet CP,
for example, by selecting it in the hardware configuration.
You can obtain more information on what to do from the integral Help.
Please note that you can only download the configuration data to the CP if you
had a valid license to use the NCM S7 option package when carrying out the
configuration.
______________________________________________________________
Note
For test or demonstration purposes you can install the option package without
a license, in order to familiarize yourself with NCM S7. Any configuration data
generated in this way can, however, never be downloaded to the CP, not even
if the software is subsequently licensed.
______________________________________________________________
Contents Page
Subnet 1
Ethernet CP
* TCP/IP only
Subnet 2
S7-400 Ethernet CP
Ethernet node
Data transfer is bidirectional, i.e. data can be sent and received at the
same time via the connection.
The two nodes have equal rights, i.e. either node can initiate Send or
Receive activities as events demand.
Data Volume and For the number of communication connections supported by each Ethernet
Number of CP please refer to the chapter on the hardware of the Ethernet CP. You can
Connections increase the number of connections per station by adding more CPs.
The Ethernet CP can send and receive 240 bytes respectively per job and
connection.
Accepts data from the user data area in the CPU and
sends it via Ethernet.
Overview For S7 communication connections the Ethernet CP has the task of sending and
receiving data via Ethernet and exchanging data with the user program in the S7
CPU.
Functions of the The Ethernet CP performs the following functions for handling data transfer
Ethernet CP via a connection:
Receives data from the Ethernet and passes it on to the user data area in
the CPU.
Accepts data from the user data area in the CPU and sends it via
Ethernet.
Configuration The Ethernet CP must be configured with the other hardware, entered in the
Requirements hardware configuration and connected to the Ethernet subnet.
Note: All stations outside the project must have dummy objects configured for
them, e.g. S5 or Other Station.
Overview of The diagram above shows the action to be taken in order to operate
Procedure connections in the SIMATIC S7 with the Ethernet CP.
Remark When configuring connections, you can normally adopt the default values.
Remote Local
TSAP TSAP
ISO transport
Local connection Remote
TSAP TSAP
MAC MAC
address address
A B
Address Parameters A connection is defined by specifying its local and remote end points.
of an ISO Transport
Connection Local addresses:
Local MAC address and local TSAP
(Transport Service Access Point)
Remote addresses:
Remote MAC address and remote TSAP
The address parameters are assigned with NCM S7 and stored in the CP
database. This enables changes or extensions to the Ethernet network topology
to be made without affecting the user program in the CPU.
Note
When configuring the Ethernet CPs in the local and destination stations, the
TSAPs of an ISO transport connection must be reversed:
Remote TSAP (on CP in local station) = local TSAP (in destination station);
Local TSAP (on CP in local station) = remote TSAP (in destination station);
Remote Local
TSAP TSAP
ISO-on-TCP
Local connection Remote
TSAP TSAP
IP IP
address address
A B
Address Parameters A connection is defined by specifying its local and remote end points.
Local addresses:
Local IP address and local TSAP
(Transport Service Access Point)
Remote addresses:
Remote IP address and remote TSAP
The address parameters are assigned with NCM S7 and stored in the CP
database. This enables changes or extensions to the Ethernet network topology
to be made without affecting the user program in the CPU.
Note
When configuring the Ethernet CP and the destination station on Ethernet, the
TSAPs of an ISO-on-TCP connection must be reversed:
Remote TSAP (in Ethernet CP) = local TSAP (in destination station)
Local TSAP (in Ethernet CP) = remote TSAP (in destination station)
New Connection
Change Connection Partner
Properties - ISO Connection
Properties - ISO-on-TCP Connection
Delete
Save
Download
Exit
Print
Help
On-line functions
Connections within Connections between stations within an S7 project are configured by starting
a Project with the local station and selecting another station in the project. Both stations
have a defined address, i.e. the local and remote addresses are taken from the
hardware configuration and the default values are generally used to specify the
local/remote TSAPs at both ends of the connection.
Connections with Connections with stations outside a project or with non-SIMATIC stations
Non-S7 Stations are configured by starting with the local station and selecting a station of the type
SIMATIC S5, Other Station or PG/PC. The end point contains the local and
remote addresses. Connections with non-S7 stations are generated as partially
unspecified connections, i.e. the remote TSAP is missing. The full details of these
connections must be specified in the Properties dialog.
Unspecified Connections with a device which is not yet known (e.g. diagnostics device)
Connections are configured as (unspecified) connections and the details can be specified
later in the Properties dialog.
The local MAC address is specified, but the local TSAP, the remote MAC
address and the remote TSAP are missing.
Local Node A separate connection table showing connection partners and connection types
is created for each programmable module (CPU).
The module (CPU), for which you have selected the connection table is also
called the local node.
2. In the Station input field select the station to which you want to create a
connection.
3. In the Module input field select the CPU in the station to which you want
to create a connection.
4. In the Type input field select the type of connection you want to use, in
this case ISO transport connection.
When you confirm your entry with Add, the new connection is created and the
"New Connection" dialog box remains open. This enables you to create more
connections without having to open the dialog box again. The list of connections
is also updated at the same time. When you have created all the new
connections, you can close the dialog box by clicking the OK button.
Connection All the remote partners in the S7 project of the local station you have selected
Partner are displayed showing all their programmable modules (CPUs) for you to make
your selection. Select the programmable module to which you want to create a
connection.
With OK the connection is entered in the list, the dialog is closed and the display
in the main dialog updated.
With Cancel the dialog is closed and the connection is not entered in the list.
Note
For the number of connections possible with each Ethernet CP please see the
chapter on the CP hardware. If several CPs are installed in one station, the next
one is automatically selected. You can rearrange the connections in the
Properties dialog.
Apart from creating new connections you can also change the connection partner
for any connection already configured.
Calling the Dialog To obtain the dialog for changing the connection partner, proceed as follows:
Connection In the same way as for creating new connections, all the stations in the S7
Partner project are displayed for selection. Select the programmable module to which you
want to create the connection.
With OK the connection is entered in the list, the dialog is closed and the display
in the main dialog updated.
With Cancel the dialog is closed and the alteration is not entered in the list.
The Properties dialog is clearly divided into separate tab pages, each
containing a group of parameters that go together.
General
Global parameters of the connection and local name of the ISO transport
connection
Addresses
Information about local and remote addresses
Dynamics
The relevant timers and counters
Overview
Overview of all the ISO transport connections configured for the selected
S7 station together with the relevant parameters and the connection
status.
Apart from entering a connection in the connection table you can also change
certain properties of each connection configured.
In this dialog you can alter individual connection parameters for which the default
was entered in the New Connection dialog.
Calling the Dialog Proceed as follows to obtain the dialog for the specific properties of a connection:
General Tab Page This tab page in the Properties dialog shows global parameters for the
connection and the local name of the ISO transport connection. The local ID is
identical to the ID in the connection list and is displayed here for clarity.
SIMATIC
Attribute NET Industrial Ethernet
Description
Siemens AG 1997. All rights reserved.
Date : 01.08.1997 Access
File No. : 7KE_PISO.15
Connection
Endpoint
Name Suggested name. Can be changed by the user as required. You Modifiable
use this field to identify the partner in the case of unspecified
connections.
Via CP If there are several CPs of the same type in the station, which are Selectable
all connected to the same subnet, you can select the one you want
to use for the connection here.
If no CP is assigned (e.g. because it has been deleted), None
appears here.
If there is only one CP in the station, selection is not possible. Read only
ID This value must be entered for the block call parameter ID in the Read only
user program to identify the connection.
LADDR Entry of this block call parameter is mandatory in the FC call in the Read only
user program to identify the connection.
Addresses Tab Page The Addresses tab page gives suggested values for the relevant local and
remote addresses. In the case of connections with non-S7 stations you can set
the TSAPs individually.
TSAP Format ISO transport connections have a TSAP length of between 1 and 32 bytes. The
current length is automatically displayed on entry (visible display: 20 ASCII
characters). Both local and remote TSAPs can be entered either as a
hexadecimal value or as an ASCII string. If you enter in ASCII, the characters
you enter are also displayed in hexadecimal form. If you enter in hexadecimal,
printable characters are displayed as the ASCII equivalent. If you enter non-
printable characters, the ASCII display becomes gray (ASCII input not possible)
and the non-printable characters appear as a period.
Local and Remote The remote and local TSAPs can be identical because the connection is
TSAPs uniquely identified by the different MAC addresses. If you want to make more
than one connection between two stations, the TSAPs must be different.
Default TSAPs When you are configuring the local and remote TSAPs, default values are
proposed (e.g. ISO-1 for the first connection between two partners). If more
connections are configured between the same partners, the default values are
automatically incremented (e.g. ISO-2 etc.).
For a new connection with a new partner, the default proposals start again at
ISO-1.
The dialog box above shows a case of this kind where the remote MAC address
is not specified and the remote TSAP has just been entered.
Dynamics Tab Page The Dynamics tab page shows the relevant timers and counters of the
connection. You can adopt the defaults.
If necessary (e.g. connections with non-SIMATIC systems) you can adjust the
timers and counters individually and change the dynamic behavior of the
connection.
Connection
Establishment
Data Transfer
Max. Count The maximum count is the number of transmission attempts Modifiable
including the first attempt (1 - 100, default 5).
Inactivity Time The inactivity time specifies the interval after which the Modifiable
connection is to be cleared if no further sign of life is
received from the partner
(6 - 180 s, default 30 s).
Window Time The window time specifies the interval for sending sign-of- Read only
life frames. The window time is fixed at 1/3 of the inactivity
time for SIMATIC NET CPs (2 - 60 s, default 10 s). Sign-of-
life frames are sent in order to be able to check the connection
for transmission of frames even when there is no data traffic.
The partner station sends a frame in response to a sign-of-life frame. These are
therefore sent to the partner station after the window time. In order to prevent
connections from being cleared unnecessarily, the inactivity time should be at
least three times as long as the window time.
Overview Tab Page The overview shows all the ISO transport connections in this station configured
so far together with their parameters (cannot be changed).
Parameter Description
Conn. Name Connection name entered. This identifies the ISO transport connection (default
length 8 characters).
Remote Address Remote MAC address of the connection on the Ethernet subnet.
Local TSAP Local connection end point (Transport Service Access Point).
The Properties dialog is clearly divided into separate tab pages, each
containing a group of parameters that go together.
General
Global parameters of the connection and local name of the ISO-on-TCP
connection
Addresses
Information about local and remote addresses
Overview
Overview of all the ISO-on-TCP connections configured for the selected
S7 station together with the relevant parameters and the connection
status.
Apart from entering a connection in the connection table you can also alter
individual connection parameters for each configured connection for which the
defaults were entered in the New dialog.
Calling the Dialog Proceed as follows to obtain the dialog for the specific properties of a connection:
General Tab Page This tab page in the Properties dialog shows the parameters for the connection
and the local name of the ISO-on-TCP connection. The local ID is identical to the
ID in the connection list (STEP 7 connection configuration) and is displayed here
for clarity.
Endpoint
Name Suggested name, plus connection number suffix. Can be changed Modifiable
by the user as required (max. 24 characters).
Via CP If there are several CPs of the same type in the station, which are Selectable
all connected to the same subnet, you can select the one you want
to use for the connection here.
If no CP is assigned (e.g. because it has been deleted), None
appears here.
If there is only one CP in the station, selection is not possible. Read only
ID Entry of this block call parameter is mandatory in the FC call in the Read only
user program to identify the connection. (The ID changes changes
when the local ID is changed.)
LADDR Entry of this block call parameter is mandatory in the FC call in the Read only
user program to identify the connection.
Addresses Tab Page The Address tab page gives suggested values for the relevant local and remote
addresses. You can set the TSAPs individually.
TSAP Format ISO-on-TCP connections have a TSAP length of between 1 and 32 bytes. The
current length is automatically displayed on entry (visible display: 20 ASCII
characters). Both local and remote TSAPs can be entered either as a
hexadecimal value or as an ASCII string. If you enter in ASCII, the characters
you enter are also displayed in hexadecimal form. If you enter in hexadecimal,
printable characters are displayed as the ASCII equivalent (8 hexadecimal
characters visible). If you enter non-printable characters, the ASCII display
becomes gray (ASCII input not possible) and the non-printable characters appear
as a period.
Local and Remote The remote and local TSAPs can be identical because the connection is
TSAPs uniquely identified by the different IP addresses. If you want to make more than
one connection between two stations, the TSAPs must be different.
Default TSAPs For configuring the local and remote TSAPs, there is a default value "TCP-1" for
the first connection between the two partners (this can be changed). For another
connection between the same partners, the default value "TCP-2" is proposed.
For a new connection with a new partner, TCP-1 is proposed again.
For connections not included in an S7 project you can enter the IP address and
TSAP (complete address) of the partner here.
Overview Tab Page The overview shows all the ISO-on-TCP connections in this station configured
so far, together with their parameters (cannot be changed).
Parameter Description
Conn. Name Connection name entered. This identifies the ISO-on-TCP connection (default
length 8 characters).
R/S Rack/slot of the local CP, used for the connection. (Hardware configuration)
Local TSAP Local Transport Service Access Point (default length 8 characters).
Remote TSAP Remote Transport Service Access Point (default length 8 characters).
Download Help
The toolbar of the connection configuration dialog box offers the following functions:
Save To save the connection you have configured you can either select the Save
function or click the save icon (diskette symbol).
Print You can print out the whole connection table or selected sections of it. Select the
Print function or click the Print icon (printer symbol).
Undo The Undo function allows you to cancel actions you have performed. You can
either select the Undo function or click the Undo icon.
Change Connection You can assign a new partner station to the selected connection.
Partner
Important!
Remember that this also changes the partner ID for connections using the
SEND-RECEIVE interface.
Download Help
Download For downloading the connection table to the PLC. You will find further information
in the integral Help.
Help If you need help or additional information you can either select the Help function
or click the Help icon (? symbol).
The Help icon offers you context-sensitive help and the Help function shows you
a Help dialog which will be familiar to you from other Windows applications.
The actions which can cause configured connections to lose their assignment to
the CP or to be deleted are outlined on the next page.
Note
Action Moving the CP (module) to a different place in the hardware configuration (using
drag and drop).
Effect on the The connections are retained. The connections IDs are updated
Connections automatically.
How to Reinstate 1. Adjust the module starting address LADDR in the user program
the Connection
2. Download the connection configuration to the CP again.
Effect on the The connections are retained, but are not assigned to a CP in the
Connections connection table. The connections are marked with an "!" on the Overview tab
page in the connection properties dialog.
How to Reinstate When you have positioned a CP in the hardware configuration and connected
the Connection it to the network:
1. Assign the CP to the connection using the "Addresses" tab in the Properties
dialog for the connection;
or
reassign the connection with the function Edit> Connection Partner.
2. Change the connection IDs in the user program.
3. Download the connection configuration to the CP again.
Effect on the The connections between the stations in the project and the remote station
Connections are retained, but are not assigned in the connection table. The connections are
marked with an "!" on the "Overview" tab page in the connection properties
dialog.
How to Reinstate Assign a new remote station (or local station) to the connection with the
the Connection function Edit> Connection Partner.
Effect on the The connections that were assigned via the CP are retained, but are not
Connections assigned in the connection table. The connections are marked with an "!" on the
"Overview" tab page in the connection properties dialog.
How to Reinstate Reassign the connections with the function Edit > Connection Partner or
the Connection using the "Addresses" tab in the Properties dialog for the connection concerned.
If you replace a CP, the replacement must at least provide the same
services and the version must be the same or higher.
All connections are lost if you replace a CPU.
Contents Page
CP
CP
STEP
STEP77 database
user database
userprogram
program
User
Userdata
databuffer
buffer
User
Userdata
data
areas
areas
AG_SEND Send
Communication
connection
AG_RECV Receive
FC Blocks Two blocks of type FC are available for handling communication via configured
connections:
AG_SEND
This block passes the user data from the specified user data area to the
Ethernet CP for transmission.
AG_RECV
This block puts the user data received into the user data area specified in
the call.
The diagram above illustrates this procedure: The user program uses the FC
blocks AG_SEND and AG_RECV to instruct the Ethernet CP to send or receive
data via the configured connection.
Data Exchange Data is exchanged between CPU and Ethernet CP as dictated by the calls
S7 CPU <-> to the FC blocks AG_SEND and AG_RECV in the CPU program.
Ethernet CP
The Ethernet CP processes the Send and Receive jobs independently of the
CPU cycle and the transmission takes a certain amount of time. The interface
with the FC blocks in the user program is synchronized by means of
acknowledgements. There are two possibilities:
FC Calls faster than If a block is called again in the user program before all the data has been
the Transmission sent or received, the following happens at the interfaces to the FC blocks:
Time
AG_SEND:
No further job is accepted until the transmission of the data on the
connection has been acknowledged by the Ethernet station. During this
time, the user programm receives the message "job active" until the
Ethernet CP can accept the next job on the same connection.
AG_RECV:
The job is acknowledged with the message no data available yet" if there
are no received data on the Ethernet CP. The user program receives this
message in the CPU cycle until the Ethernet CP has received data again
on the connection.
FC Calls slower than If a block is called again before the data were completely transferred or
the Transmission received, the procedure is as follows on the interfaces of the FC blocks:
Time
AG_SEND:
The job is positively acknowledged. The Ethernet CP is ready to
receive a new send job (at the earliest however with the next call).
AG_RECV:
The job is acknowledged with New data received when the data have
been transferred to the user program. Following this, the FC call can be
repeated.This is controlled by the flow control of the protocol.
Process image
Alternative Different data areas in the CPU can be used for communication via
Data Areas configured connections. Your choice of data area depends on the type of CPU
and the task involved. The alternatives are:
Process image:
This choice is only possible if continuous Send and Receive areas can be
reserved in the process image of the S7 CPU. The capacity may be
restricted by the capabilities of the CPU and by the number of central
signal modules.
Principle of job The user program triggers the transfer of the user data areas
and data transfer by means of FC block calls and monitors the execution by
evaluating the condition bits returned by the FCs. The
parameters assigned to the FC blocks when they are called
include:
- AG_RECV for entering the data received from the Ethernet CP into
the user data area;
AG_RECV
Connection
AG_RECV
Connection
AG_SEND
AG_RECV
Connection
AG_SEND
The user program, which can consist of any number of blocks (OBs, FBs
or FCs), accesses several connections.
The user program can send data via connections by means of AG_SEND
calls at any point (event-driven and program-controlled execution).
The user program can accept data received via connections by means of
AG_RECV calls at any point in the CPU cycle.
Note: The blocks can be called more than once in one cycle for the same connection.
The FC blocks are supplied with the NCM S7-Ethernet configuring software.
Result:
The currently existing libraries are displayed.
Result:
The library SIMATIC NET CP is now created in the STEP 7 library.
In order to be able to use the FC blocks for writing your user program, proceed
as follows:
1. Open the library in the SIMATIC Manager with File >Open >
Library.
Result:
The currently existing libraries are displayed.
2. Search for the directory Simnetcp in STEP 7\S7libs and select or open
the file CP.S7L in it.
Result:
The library SIMATIC NET CP is now created in the STEP 7 library.
Specifying the When you call an FC block you assign the starting address of the CP module
CP Address to the LADDR parameter. You can obtain the starting address of the Ethernet CP
module from the S7 configuration dialog or calculate it as follows.
Querying the The module starting address can be determined from the slot-oriented
CP Address address assignment for signal modules. The rules for analog modules apply to
the Ethernet CP.
When configuring the CP with the STEP 7 hardware configuration tool, the
starting address of the module appears in the configuration table.
Specifying the When you call an FC block you also enter the address and length of the data
Data Area on the area in the CPU. Don't forget that the maximum length of the data area is
CPU 240 bytes.
DONE = 0
NDR = 0
ERROR = 0
Error Response
CP address points to a non-existent CPU remains in Stop state due to a system error.
CP module or digital module.
If the S7 CPU cannot communicate with the Ethernet CP at the specified module
starting address, the result is as shown above.
Note:
Example in STL
STL Explanation
Purpose of The FC block AG_SEND passes on data to the Ethernet CP for transmission
the Block via a configured connection.
The data area specified can be an area in the process image, a bit memory
address area or a data block area.
Successful execution is signalled when the complete user data area has been
transmitted via Ethernet.
DONE OUTPUT BOOL 0: Job in This parameter indicates whether or not the
progress job has been completed without errors. As
1: New data long as DONE=0, no new job can be started.
The CP sets DONE to 0 when it accepts a
job.
For meanings in conjunction with the
ERROR and STATUS parameters, see the
Condition Codes table.
Supply AG_SEND
ACT = 0
AG_SEND Startup phase
0, 1, 8181 1)
AG_SEND
1, 0, 0000 1)
Supply AG_SEND
with data X
ACT = 1
AG_SEND
0, 0, 8181 1)
Supply AG_SEND
ACT = 0 Transmission of X
via Ethernet
AG_SEND active Key:
0, 0, 8181 1) 1) Parameter transfer
DONE, ERROR, STATUS
AG_SEND
1, 0, 0000 1)
The diagram above shows the normal execution sequence of a data transfer
initiated by AG_SEND in the user program.
The status indicators can be updated without issuing a new Send job by setting
the ACT parameter = 0.
INT BOOL
ID NDR
WORD BOOL
LADDR ERROR
ANY WORD
RECV STATUS
LEN INT
Example in STL
STL Explanation
Purpose of The FC block AG_RECV receives the data transferred via a configured
the Block connection from the Ethernet CP.
The data area specified as the data destination can be an area in the process
image, a bit memory address area or a data block area.
Successful execution is signalled when the data have been received from the
Ethernet CP.
AG_RECV Transmission of A
0, 1, 8180 1) via Ethernet
in progress
AG_RECV
1, 0, 0000 1)
Accept/evaluate
received data A Transmission of B
via Ethernet
AG_RECV in progress
0, 0, 8180 1)
AG_RECV
1, 0, 0000 1)
Accept/evaluate
received data B Key:
Transmission of C 1) Parameter transfer
via Ethernet NDR, ERROR, STATUS
AG_RECV
in progress
.
.
.
The diagram above shows the normal execution sequence for data acceptance
initiated by AG-RCVE in the user program.
Overview
Please also have a look at the diagnostics repeater which in addition to the normal repeater functionality
also has comprehensive diagnostics functions for physical line diagnosis. It is described under
"Distributed I/O/Diagnostics/Diagnostics repeater for PROFIBUS DP".
Application
The RS 485 IP20 repeater connects two PROFIBUS or MPI bus segments using the RS 485 system
with up to 32 stations. Data transmission rates of 9.6 kbit/s to 12 Mbit/s are then possible.
Design
Function
Mode of operation
Technical specifications
972-0AA01-0XA0 6ES7
voltages Supply
value Rated
DC V 24 Yes
consumption Current
max. consumption, Current 200 mA
system Connection
lines Bus blocks terminal 2
supply Power block Terminal
DP PROFIBUS
max. rate, Transmission Mbit/s 12 to Kbit/s 9.6 12 Mbit/s;
requirements Environmental
temperatu Operatingre
max. 60 C
temperature Storage/transportation
min. -40 C
max. 70 C
humidity Relative
max. Operation, C 25 at 95%;
Ordering data
For constructing PROFIBUS networks (line, star and ring) with glass, PCF and plastic fiber-
optic cables
High availability can be achieved using redundant power supply and redundant cable routes
Function monitoring through signaling contact
All PROFIBUS data rates from 9.6 kbit/s to 12 Mbit/s including 45.45 kbit/s for PROFIBUS PA
The fiber-optic routes can be checked with a voltmeter
Benefits
Application
With the PROFIBUS OLM (Optical Link Modules) Version 3, optical PROFIBUS networks can be
established in linear bus, star and redundant ring topologies.
The data transmission rate of a fiber optic line is independent of the distance and can be up to 12 Mbit/s.
Possible applications for OLMs include:
The OLMs have a compact metal housing. It is suitable for mounting on a standard mounting rail and for
fixed mounting.
The 24 V supply is provided through a terminal block. Redundant power supply configurations are
supported.
The signal contact can be used to transfer a digital signal for evaluation purposes to controllers or
operator control and monitoring systems.
OLMs can be combined with each other and individual stations or whole electrical segments integrated
in the optical PROFIBUS network through an electrical interface .
The OLMs are available with one or two FOC interfaces with BFOC connection method for various types
of FO cables:
Plastic FO cables (980/1000 m) can be used for single line lengths up to 80 m. They can also
be preassembled on site with BFOC connectors .
PCF FO cables (200/230 m) can be used for single line lengths up to 400 m. They are
available preassembled with 4 BFOC connectors and an insertion assistance.
Glass fiber multimode FO cables (62.5/125 m) like the SIMATIC NET fiber-optic cables can
be used for long distances up to 3000 m. These cables are available preassembled with 4 BFOC
plugs.
Single mode FO cables (10/125 m fibers) can be used for very long distances up to 15 km.
They are available on request.
Function
Automatic recognition of all PROFIBUS transmission rates: 9.6 Kbit/s to 12 Mbit/s including
45.45 Kbit/s (PROFIBUS PA)
Configuration of the following network topologies: line, star, redundant ring
High availability through media redundancy. The distance between two OLMs in the redundant
ring is limited only by the optical sensing range of the modules.
Segmentable RS485 interface (Sub-D connector)
Unlimited multimaster mode: extended segmenting function for error localization on fiber-optic
cable and RS 485 segments
Fast localization of faults:
Indication of module status through isolated signaling contact.
Inspection of the fiber-optic cable quality: measuring output for optical receivers for
logging and validity check of the FOC line attenuation with a voltmeter
High cascading depth: line and redundant ring up to 124 OLM (only limited by monitoring
times)
Integration
Technical specifications
Technical specifications
Interfaces
Construction
Page 235 of 293
Technical specifications
Ordering data
Overview
The unmanaged Industrial Ethernet Entry Level Switch SCALANCE X005 is optimized for low-
cost installation of small Industrial Ethernet networks with 10/100 Mbit/s in a line and star topology
Five electrical nodes or network connections
Rugged metal housing for space-saving cubicle mounting on standard rails, S7-300 DIN rail or
for wall mounting
Rugged, industry-standard station connections with PROFINET-compatible RJ45 connectors
that offer additional strain relief and bending strain relief thanks to latching on the housing
Diagnostics on the device by means of LEDs (power, link status, data communication)
Benefits
Ideal solution for configuring Industrial Ethernet star and line topologies
Space-saving installation in the cabinet thanks to the compact design in S7-300 format
Secure data communication by means of industry-standard device interface using PROFINET-
compliant plug-in connector IE FC RJ45 Plug 180 and additional strain relief by latching the
connector to the housing
Installation is possible without a patch field by means of IE FC RJ45 Plug 180 and IE FC
Standard Cable
Simple and fast diagnosis via LED on device
Uncrossed connecting cables can be used due to the integrated Autocrossover function
Simple network configuration without runtime calculation
Application
Design
The SCALANCE Industrial Ethernet switches with a rugged metal housing are optimized for mounting
on a standard rail and an S7-300 DIN rail. Direct wall mounting in various positions is also possible. Due
to the housing dimensions that correspond to those of the SIMATIC S7-300, the devices are ideally
suited for integration into an automation solution using S7-300 components.
The SCALANCE X005 Switch is equipped with:
Function
Uncrossed connecting cables can be used due to Autocrossover function integrated in the
ports
Load disconnection through integral switch functionality
Port status
Data communication
Interfaces
Current consumption 80 mA
Power loss at 24 V DC 2W
Construction
Weight 550 g
Approvals
CE EN 61000-6-2, EN 61000-6-4
Ordering data
Unit
Order no. Article description
price
SIMATIC NET, SCALANCE X005, IE ENTRY LEVEL SWITCH
6GK5005 -0BA00 - UNMANAGED 5 X 10/100MBIT/S RJ45 PORTS, LED
1AA3 DIAGNOSTICS, IP30, 24 V DC POWER SUPPLY, PROFINET
COMPLIANT SLEEVE, WITH MANUAL
Overview
The unmanaged Industrial Ethernet switches of the SCALANCE X-100 product line are
optimized for installing Industrial Ethernet networks with 10/100 Mbit/s in a line and star topology
Electrical or optical connection to stations or network in accordance with the port type of the
devices
Rugged metal housing for space-saving cabinet mounting on standard rails, S7-300 DIN rail or
for wall mounting
Rugged, industry-standard station connections with PROFINET-compatible RJ45 connectors
that offer additional strain relief and bending strain relief thanks to latching on the housing
Redundant power supply
Diagnostics on the device by means of LEDs (power, link status, data communication)
Error signaling contact with easy adjustment using the SET button
Benefits
Ideal solution for configuring Industrial Ethernet star and line topologies
Space-saving installation in the cabinet thanks to the compact design in S7-300 format
Secure data communication by means of industry-standard device interface using PROFINET-
compliant plug-in connector (IE FC RJ45 Plug 180) and additional strain relief by latching the
connector to the housing
Installation is possible without a patch field by means of IE FC RJ45 Plug 180 and IE FC
Standard Cable
Simple and fast diagnosis via LED on device and signaling contact
Uncrossed connecting cables can be used due to the integrated Autocrossover function
Simple network configuration without runtime calculation
Application
The switches of the SCALANCE X-100 series are used for cost-effective configuration of Industrial
Ethernet line or star topologies with switching functionality. They are designed for installation in the
control cabinet.
Product versions
SCALANCE X104-2 / SCALANCE X106-1
Design
The SCALANCE Industrial Ethernet switches with a rugged metal housing are optimized for mounting
on a standard rail and an S7-300 DIN rail. Direct wall mounting in various positions is also possible. Due
to the housing dimensions that correspond to those of the S7-300, the devices are ideally suited for
integration into an automation solution using
S7-300 components.
The SCALANCE X-100 switches feature:
Function
Electrical and optical line topologies with SCALANCE X108 and SCALANCE X104-2
Diagnostics
The following information is displayed by LEDs on the equipment:
Power
Port status
Data communication
The Industrial Ethernet switches of the SCALANCE X-100 line can also be monitored using the floating
signaling contact.
Technical specifications
Interfaces
Network extension
parameter /
TP cable length
0 85 m IE FC IE FC IE FC
Marine/Trailing Marine/Trailing Marine/Trailing
Cable with IE FC Cable with IE FC Cable with IE FC
RJ45 Plug or RJ45 Plug or RJ45 Plug
0 75 m IE FC 0 75 m IE FC or
Marine/Trailing Marine/Trailing 0 75 m IE FC
Cable + 10 m TP Cable + 10 m TP Marine/Trailing
Cord Cord Cable + 10 m TP
Cord
Permissible ambient
conditions
Relative humidity < 95%, non- < 95%, non- < 95%, non-
during operation condensing condensing condensing
Design
Assembly Standard rail, S7- Standard rail, S7- Standard rail, S7-
300 rail, wall 300 rail, wall 300 rail, wall
mounting mounting mounting
Approvals
Ordering data
Unit
Order no. Article description
price
SIMATIC NET, SCALANCE X104-2, UNMANAGED IE SWITCH, 4 X
10/100MBIT/S RJ45 PORTS, 2 X 100 MBIT/S MULTIMODE BFOC,
6GK5104 -2BB00 -
LED DIAGNOSTICS, FAULT SIGNAL. CONTACT WITH SET on request
2AA3
BUTTON, REDUNDANT VOLTAGE SUPPLY, W. ELECTRONIC
MANUALS ON CD
Overview
The managed Industrial Ethernet switches of the SCALANCE X-200 product line are optimized
for installing Industrial Ethernet networks with 10/100 Mbit/s in a line, star and ring topology
Electrical or optical connection to stations or network in accordance with the port type of the
devices
Rugged metal housing in S7-300 format for mounting on standard rail, S7-300 standard
mounting rail or for direct wall mounting in various positions
Rugged, industry-standard station connections with PROFINET-compatible RJ45 connectors
that offer additional strain relief and bending strain relief thanks to latching on the housing
Redundant power supply
Diagnostics on the device by means of LEDs (power, link status, data communication)
Error signaling contact with easy adjustment using the SET button
The devices feature PROFINET diagnostics, SNMP access, integral Web server and automatic
e-mail sending function for remote diagnosis and signaling over the network.
Benefits
Ideal solution for configuring Industrial Ethernet line, star and ring topologies
Reliable data communication thanks to rugged device connection using PROFINET-compatible
plug-in cables that offer additional strain relief and bending strain relief thanks to latching on the
housing.
High network availability through configuration of redundant ring topologies with SCALANCE X-
400, SCALANCE X-200IRT or OSM/ESM as redundancy managers
Fast and easy diagnosis with LEDs on the device, through the integral Web server and through
signaling contacts
Integration of the SCALANCE X-200 switches in the existing network management
infrastructure through SNMP access point
Easy integration in the process diagnosis and system diagnosis with PROFINET
Configuration and diagnostics integrated into STEP 7 provide significant benefits during the
engineering, start-up and operating phases of a plant
Uncrossed connecting cables can be used due to the integrated Autocrossover function
Module replacement without the need for a programming device, using the C-PLUG swap
media for backing up the configuration data
Arrangement possible without control cabinet since devices with high IP65 degree of protection
Application
The SCALANCE X-200 Industrial Ethernet switches permit cost-effective configuration of Industrial
Ethernet line, star or ring topologies with switching functionality where high network availability or
remote diagnostics options are required. The devices with degree of protection IP30 have been
designed for use in the control cabinet. The SCALANCE X208PRO, is designed to degree of protection
IP65 for installation outside the control cabinet.
Product versions
Diagnostics access via SNMP and Web browser with SCALANCE X204-2 and SCALANCE X208
SCALANCE X208 / SCALANCE X208PRO (IP65 degree of protection)
For configuring electrical Industrial Ethernet line, star or ring topologies (8 electrical ports):
SCALANCE X208 for installation in the switchgear cabinet
SCALANCE X208PRO, specially for use outside the switchgear cabinet
Device diagnostics with LEDs (power, link status, data communication)
Remote diagnosis with signaling contact (for SCALANCE X208: signal mask can be set locally
using buttons), PROFINET, SNMP and Web browser
The eight RJ45 sockets of the SCALANCE X208 are industry-standard and feature additional
retaining collars for connection to the IE FC RJ45 Plug 180
The eight PROFINET-compatible M12 sockets of the SCALANCE X208PRO are designed with
degree of protection IP65 for connection to the IE M12 Plug PRO or the pre-assembled IE M12
cable
The SCALANCE X208PRO can be mounted on a DIN rail or S7-300 rail or direct on the
equipment or machine in a space-saving, horizontal or vertical design;
the status information can be read off regardless of the mounting position thanks to the angled LED
strip.
Power can also be supplied to the SCALANCE X208PRO from outside the control cabinet from
the PS791-1PRO power supply module at 230 V AC.
The SCALANCE X-200 Industrial Ethernet switches with a rugged metal housing are optimized for
mounting on a standard rail and an S7-300 rail. Direct wall mounting in various positions is also
possible. With the S7-300 housing format, the devices are optimized for integration in an automation
solution with S7-300 components.
The switches are equipped with
Function
Configuring electrical and optical Industrial Ethernet line, star and ring topologies
Use in ring topologies (100 Mbit/s) together with SCALANCE X-400, SCALANCE X-200IRT or
OSM/ESM as redundancy manager
Uncrossed connecting cables can be used due to Autocrossover function integrated in the
ports
Load disconnection through integral switch functionality
Easy diagnostics using signaling contact, SNMP and Web browser
Easy copper cable diagnostics with Web browser for localizing cable breaks
Integration into the diagnostics of a PROFINET IO-Controllers for a consistent diagnostics
concept, including network infrastructure
Diagnosis of data traffic by means of a parameterizable mirror port with a standard commercial
network analyzer
Optimized support of PROFINET real-time communication (RT) through prioritizing
Fast device replacement in the event of a fault by using the optional C-PLUG swap medium
(not included in scope of supply)
Star network topology with SCALANCE X208PRO outside the control cabinet and 230 V AC power supply
Power
Port status
Data traffic
Signaling contact
The Industrial Ethernet switches of the SCALANCE X-200 line can also be monitored using the floating
signaling contact.
Technical specifications
Interfaces
Network
extension
0 85 IE FC IE FC IE FC IE FC
m Marine/Trailing/Fl Marine/Trailing/Fl Marine/Trailing/Fl Marine/Trailing/Fl
exible Cable with exible Cable with exible Cable with exible Cable with
IE FC RJ45 Plug IE FC RJ45 Plug IE FC RJ45 Plug IE FC RJ45 Plug
IE FC IE FC IE FC IE FC
marine/trailing/flex marine/trailing/flex marine/trailing/flex marine/trailing/flex
ible cable (0 75 ible cable (0 75 ible cable (0 75 ible cable (0 75
m) m) m) m)
+ 10 m TP cord + 10 m TP cord + 10 m TP cord + 10 m TP cord
Permissible
ambient
conditions
Relative < 95%, non- < 95%, non- < 95%, non- < 95%, non-
humidity condensing condensing condensing condensing
during
operation
Design
Assembl Standard rail, S7- Standard rail, S7- Standard rail, S7- Standard rail, S7-
y 300 rail, wall 300 rail, wall 300 rail, wall 300 rail, wall
mounting mounting mounting mounting
Approvals
Interfaces
Communication
connection,
optical
Power loss at 24 V DC 4W 4W
Network extension
parameter /
TP cable length
0 85 m IE FC IE FC
Marine/Trailing/Flexible Cable marine/trailing/flexible
with IE FC RJ45 Plug cable with
IE M12 plug PRO
IE FC
marine/trailing/flexible cable
(0 75 m)
+ 10 m TP cord
0 3000 m
Permissible ambient
conditions
Design
Approvals
FM FM 3611 FM 3611
Ordering data
Overview
The SCALANCE X-400 product range comprises modular Industrial Ethernet switches
expandable by various media modules and extenders. It supports 10/100/1000-Mbit technology for
various transmission media (twisted pair, fiber optic) and increased port requirements. The main
applications are high-performance plant networks (control level). Thanks to its partly modular design,
the X-400 product line is also designed for future requirements and can be adapted to the relevant
task.
The X414-3E switch has two integral Gigabit Ethernet twisted pair interfaces (10/100/1000
Mbit/s) for connecting a number of switches to one another. Nodes are connected via 12 Fast
Ethernet twisted pair ports (10/100 Mbit/s) integrated into the switch.
Another eight stations can be connected via extender modules on the right of the switch. The
following extender modules are available:
Extenders with eight Fast Ethernet twisted-pair ports
Extenders with four media module slots for up to eight Fast Ethernet fiber optic ports
The integrated redundancy manager facilitates high-speed media redundancy even for large
networks, both for Gigabit Ethernet (SCALANCE X-400 switches in the ring) and for Fast Ethernet
(SCALANCE X-400 switches in the ring in combination with SCALANCE X-200 switches or
OSM/ESM).
For the construction of optical Gigabit Ethernet rings, both integrated Gigabit Ethernet ports
can be converted to fiber optic via a 2-port Gigabit Ethernet media module MM. Module versions are
offered for multimode (up to 750 m fiber-optic cable length) and single-mode (up to 10 km).
By means of a pluggable 2-port Fast Ethernet media module for multimode or alternatively
single-mode fiber-optic cable, SCALANCE X-400 switches can also be integrated into 100-Mbit/s
rings, e.g. with SCALANCE X204-2 or OSM.
A second pluggable 2-port Fast Ethernet fiber-optic media module enables remote nodes to be
connected optically.
Remote diagnosis is possible by means of PROFINET diagnosis (available soon), Web
browser or SNMP.
Switches of the SCALANCE X-400 product line support IT standards and thus permit seamless
integration of automation networks into existing corporate networks. Virtual networks (VLAN) can be
set up.
The support of standardized redundancy procedures (Rapid Spanning Tree Protocol) permits
the redundant integration into higher level enterprise networks.
Through learning the Multicast sources and targets (IGMP (Internet Group Management
Protocol snooping), SCALANCE X-400 switches can also filter Multicast data traffic and therefore
limit the load in the network.
Layer 3 routing (static, RIP v1/2, OSPF) supports communication between different IP
subnetworks
Benefits
Flexible configuration of electrical or optical Industrial Ethernet networks; the network topology,
type and number of ports can be adapted easily to the structure of the plant.
High availability of the network thanks to:
redundant power supply
redundant network structures based on fiber-optic or twisted pair cables (redundancy
manager, standby function and RSTP are integrated)
replacement and extension of media and expansion modules during operation
Page 264 of 293
easy device replacement by means of plug-in C-PLUG swap medium
Reliable communication thanks to very fast reconfiguration of the network in the event of a fault
(<0.3 seconds)
Simple fiber optic connection technology by means of SC sockets (Gigabit Ethernet), BFOC
sockets (Fast Ethernet) and prefabricated fiber optic cables
Twisted pair ports readily accessible from the front, 10/100 Mbit/s;
ports with sleeve for rugged, industry-compatible station connection for direct connections up to
100 m in conjunction with the PROFINET-compatible IE FC RJ45 Plug 180 or IE FC RJ45 Plug 145
connector
Easy network configuration without runtime calculation also for extremely large networks
Simple monitoring and diagnosis by means of signaling contact, digital inputs, SNMP and e-
mail; PROFINET IO diagnostics (available soon)
Reduced engineering expenditure for PLC/HMI due to integration into the SIMATIC system
fault message concept SFM (available soon)
Due to the integrated Layer 3 function (IP routing), a separate router in the network is not
essential
Investment protection for existing networks due to
effortless connection of existing 10 Mbit/s data terminals or network segments to Fast
Ethernet networks with 100 Mbit/s
increase in performance through load decoupling and data transfer rates of 100 Mbit/s
and 1000 Mbit/s
easy integration into existing network management infrastructures by means of SNMP
Support of VLAN permits integration into Enterprise Security Policies
Limiting of load on application of Multicast-based protocols (e.g. video transmission) through
IGMP (Internet Group Management Protocol) snooping or GMRP (GARP Multicast Registration
Protocol)
Protection of network against overload by setting of port thresholds
Operating temperature range from 0 C to +60 C
Low-maintenance operation thanks to fanless construction
Application
SCALANCE X-400 products permit the configuration of switched networks at the control level, which not
only demands high availability of the network and extensive diagnostic options, but also a high number
of ports, high transfer rate and the support of fiber optic and twisted-pair transmission media.
SCALANCE X-400 products are designed with IP20 degree of protection for installation in control
cabinets.
SCALANCE X414-3E
Design
SCALANCE X414-3E
The Industrial Ethernet Switch SCALANCE X414-3E forms the core of the SCALANCE X-400 product
line. It contains the switching functionality and is responsible for the diagnosis.
The SCALANCE X414-3E has two integrated Gigabit Ethernet twisted-pair ports (10, 100 or
1000 Mbit/s, RJ45 sockets) for connecting the SCALANCE X-400 switches to one another and 12
integrated Fast Ethernet twisted-pair ports (10 or 100 Mbit/s, RJ45 sockets with sleeves) for connecting
stations. Both Gigabit Ethernet ports can be converted to fiber-optic connections with optical Gigabit
Ethernet media modules.
In addition, two slots are available for optical Fast Ethernet media modules with two ports.
By means of an extender interface SCALANCE X414-3E can be extended by a further 8 Fast Ethernet
ports (twisted pair or fiber-optic, depending on extender version). In this way, a maximum configuration
Page 265 of 293
of two Gigabit Ethernet Ports (electrical or optical) and up to 24 Fast Ethernet Ports (of which between 4
and 12 can be optical) is possible. The installation width including extender is max. 19".
Interfaces
Extensive operating mode and status information is displayed via LEDs and selection pushbuttons.
The SCALANCE X414-3E is supplied with 24 V DC. To protect against power failure, two infeeds are
provided.
SCALANCE X-400 media modules (MM)
Using media modules, the Industrial Ethernet Switch SCALANCE X414-3E can be equipped with fiber
optic cables. Media modules are available for both multimode and single-mode optical fibers. They can
be added or replaced during network operation. The SCALANCE X414-3E basic unit supports two
optical Gigabit Ethernet ports and up to four additional optical Fast Ethernet ports.
The following media modules are available:
MM491-2;
2 fiber optic ports (BFOC sockets) 100 Mbit/s for distances up to 3 km with multimode fiber-optic
conductors
MM491-2LD;
2 fiber optic ports (BFOC sockets) 100 Mbit/s for distances up to 26 km with single-mode fiber-optic
conductors
MM492-2;
2 fiber optic ports (SC sockets) 1 Gbit/s for distances up to 750 m with multimode fiber-optic
conductors (when using SIMATIC NET FO cable 50/125m)
MM492-2LD;
2 fiber optic ports (SC sockets) 1 Gbit/s for distances up to 10 km with single-mode fiber-optic
conductors
One plug-in media module for Gigabit Ethernet converts the Gigabit Ethernet twisted pair-ports included
in the switch to optical mode. The two Gigabit ports can then be used as either twisted-pair or fiber-optic
ports. Optical media modules for Fast Ethernet each generate two additional ports per slot.
SCALANCE X-400 extender modules (EM)
An optional extender module with up to 8 further Fast Ethernet ports can be mounted next to the
expansion interface of the SCALANCE X414-3E.
Versions:
EM495-8;
with 8 twisted pair ports (RJ45 sockets with sleeves) 10/100 Mbit/s; this enables the 12 onboard Fast
Ethernet twisted pair ports of the SCALANCE X414-3E to be expanded to a total of 20 ports.
EM496-4;
with a further four media module slots for Fast Ethernet media modules for up to 8 optical Fast
Ethernet ports
The structure of the SCALANCE X-400 product line offers the following advantages:
Function
When configuring the network, it is necessary to observe the following boundary conditions:
Maximum line length between two modules for multi-mode fiber-optic conductors:
3000 m at 100 Mbit/s
750 m at 1 Gbit/s
Maximum line length between two modules for single-mode fiber-optic conductors:
26 km at 100 Mbit/s
10 km at 1 Gbit/s
Maximum line length for twisted pairs:
100 m
Network management
The network management provides the following functions:
Page 270 of 293
Password-protected dial-up for "Administrator" (read and write authorization) and "User" (read
only)
Read-out of version and status information
Setting the signal and standby mask and address information
Fixed parameterization of the ports (data rates, half/full duplex)
Setting parameters of the VLANs and multicast services
Configuration of the IP routing function (static routing, RIP v1/2, OSPF)
Parameterization of the standby connections for a redundant ring link
Setting of Rapid Spanning Tree parameters
Parameterization of user administration of SNMP V1, V2c, V3
Output of statistics information
Diagnosis of data traffic by means of a parameterizable mirror port with a standard commercial
network analyzer
Loading of new firmware or the configuration data via the network by a TFTP server
Saving the configuration data or log table via the network on a TFTP server
If faults occur in the network, the SCALANCE X-400 switch can send error messages (traps) to a
network management system or also e-mails to a predefined network administrator.
The remote monitoring (RMON) offers the following functions:
The SCALANCE X-400 switch can collect statistics information according to the RMON groups 1
through 4. These include, for example, fault statistics that are kept for each port. This information can be
read out through Web-based management in the statistics sub-area.
Integration
SCALANCE X-400 switches without extenders are used for connecting high-availability
SIMATIC controllers (H-systems). On failure of an individual controller or switch, the plant section
remains functional.
One SCALANCE X414-3E with extender (high number of ports) is used for the star-format
connection of controllers.
Technical specifications
Interfaces
Design
Weight 3.4 kg
Approvals
FM FM 3611,
FM hazardous location
CE EN 61000-6-2, EN 61000-6-4
Ordering data
Overview
The Electrical Lean Switches ELS TP40 / ELS TP40M are optimized for creating Industrial
Ethernet networks with 10/100 Mbit/s in a line topology, but they can also be used as a single star
point.
The ELS TP40s are connected to each other via the IE FC 2 x 2 by means of integral
insulation-piercing contacts.
One or two stations or a station and a programming device are connected over two RJ45
sockets.
ELS TP40M with an additional integral Web server, SNMP access and e-mail function for
remote diagnostics and signaling over the network.
The Electrical Lean Switch ELS TP80 is used to create networks with a star topology
comprising up to 8 stations over RJ45 sockets or to expand the number of ports in OSM/ESM
applications.
Benefits
Application
They are used to construct Industrial Ethernet line topologies or small neutral points.
Device diagnostics with LEDs (power, link status, data communication).
Two RJ45 sockets are available for connecting stations and two interfaces with insulation-
piercing contacts for direct connection of the Industrial Ethernet FC TP cables.
ELS TP40M
They are used to construct Industrial Ethernet line topologies or small star neutral points.
Device diagnostics and signaling with LEDs (power, link status, data communication) and
remote diagnostics using a Web browser, SNMP (Simple Network Management Protocol) and E-
mail function.
Two RJ45 sockets for connecting stations and two interfaces with insulation-piercing contacts
for direct connection of the Industrial Ethernet FC TP cables
ELS TP80
Used to construct star structures or to extend the number of ports in conjunction with
OSM/ESM or ELS TP40 applications.
Device diagnostics is possible with LEDs (power, link status, data communication).
Eight RJ45 sockets are available for connecting stations.
Design
The ELS modules in the rugged metal casing are suitable for simple mounting onto standard rails. All
modules feature a 3-pole terminal block that is used to connect the supply voltage (24 V DC). The status
10/100BaseTX RJ45
RJ45 socket, automatic detection of the data transmission rate (10 or 100 Mbit/s), with Autosensing
and Autocrossing function for connecting TP cables (e.g TP Cords).
10/100BaseTX insulation-piercing contacts
Insulation-piercing contact element for direct connection to IE FC Cables 2 x 2 up to 100 m with
Autosensing and Autocrossing function for setting up line topologies.
Function
Power
Port status
Data communication
The ELS TP40M can also be integrated in a network management system using the standardized
SNMP (Simple Network Management Protocol) In the event of a fault in the device, the ELS TP40M can
send error messages (SNMP traps) to a network system or as e-mail to a specified network manager.
Diagnostic data for the device (statistical information) can also be obtained over the integral Web server
using a standard browser.
Technical specifications
Interfaces
Connection of 2 x insulation -
Industrial Ethernet FC TP displacement contacts
cables (10/100 Mbit/s)
Perm. ambient
conditions
Construction
Approvals
FM FM 3611 FM 3611
CE Yes Yes
Overview
The managed Industrial Ethernet OSM and ESM switches are used to construct Industrial
Ethernet networks at the control level
The modules are interconnected (backbone) at 100 Mbit/s over
Glass fiber-optic cables for OSM
Twisted pair cables for ESM
Connection of data terminals or network segments depending on the OSM/ESM type through
2 to 8 Twisted Pair ports in RJ45 or 9-pole Sub D version with 10/100 Mbit/s
3 or 8 fiber-optic ports with 100 Mbit/s
Integrated redundancy manager supports high-speed media redundancy also for large
networks
Very easy network configuration and network extension without complex configuration rules or
parameterization
SNMP and Web-based Management and RMON
Error signaling by e-mail
Integration of digital signals, e.g. door switch, temperature monitoring or signaling contacts into
the management system by means of digital inputs
Benefits
Reliable communication due to very fast reconfiguration of the network in event of fault
(<0.3 seconds)
Security of investment for existing networks due to
effortless connection of existing 10 Mbit/s data terminals or subnetworks to Fast
Ethernet networks with 100 Mbit/s
Enhanced performance thanks to load decoupling and a data rate of 100 Mbit/s
Easy network configuration without runtime calculation also for extremely large networks
High availability of the network due to:
Redundant voltage feed
Application
The Industrial Ethernet OSM (Optical Switch Module) and ESM (Electrical Switch Module) are used in
the construction of switched networks with data transmission rates of 100 Mbit/s in the control level
range, in which strict demands are placed on network availability and comprehensive diagnostics are
required.
In existing networks, load decoupling and thus increased network performance can be achieved by
creating segments (subdividing a network into subnetworks/segments) and connecting these segments
to an OSM/ESM.
The redundancy manager integrated into OSM/ESM allows redundant Industrial Ethernet rings to be
constructed in switching technology with high-speed media redundancy (reconfiguration time 0.3
seconds max.).
The data transmission rate in the ring is 100 Mbit/s; for each ring, up to 50 Industrial Ethernet OSMs
(optical ring) or ESMs (electrical ring) can be used. Apart from the 2 ring ports, OSM/ESM has other
ports (with either RJ45, ITP or BFOC interfaces) to which data terminals or network segments can be
connected.
With Industrial Ethernet OSM BC08 and media converters Industrial Ethernet OMC TP11, "Fiber to the
machine" concepts can be implemented, so that the advantages of optical transmission technology can
be utilized both for the backbone area and for station connection:
High-speed station connection (100 Mbit/s Full Duplex) over Industrial Ethernet OSM BC08
and media converter Industrial Ethernet OMC TP11 (fiber-optic cable through to the control cabinet)
in an environment subjected to strong electromagnetic fields
Bridging of large distances of up to 3 km between two OSM BC08 modules or from an
OSM BC08 to a distant station
Equipotential bonding measures or lightning protection measures are not necessary thanks to
fiber-optic cables.
Industrial Ethernet OSM TP22 or ESM TP40 modules are ideal for installation in the control cabinet with
1 or 2 stations connected (low equipment density).
With Industrial Ethernet OSM/ESM (devices with 8 ports), several rings can be redundantly
interconnected using the integrated standby function.
Apart from the 2 ring ports, Industrial Ethernet OSM/ESM modules are equipped with other ports to
which both data terminals and network segments can be connected.
OSM/ESM offer the following three error signaling functions:
Signals such as signaling contacts from PROFIBUS OLM or door contacts can be connected to
Industrial Ethernet OSM/ESM through digital inputs. These digital inputs can be monitored using
network management functions (read out status, e-mail on status change, create trap or log table entry).
Design
OSM/ESM have a stable metal casing. They are suitable for the following installation types:
Standard rail
Wall mounting
Page 285 of 293
Mounting in 19-inch racks (when 2 modules are used)
a 6-pole terminal block for connecting the supply voltage (redundant 24 V DC infeed) and the
floating signaling contact as well as
one or two 6-pole terminal blocks for connecting four digital inputs in each case
The operating mode and status information are displayed by LEDs and a selection button.
Modules with 8 ports also have a standby interface that is used to synchronize two modules when
coupling redundant rings.
Using the serial interface, Industrial Ethernet OSM/ESM can be parameterized, diagnosed or upgraded
to the latest firmware status. The firmware can also be upgraded over the network.
Industrial Ethernet OSM/ESM is available with 4 or 8 ports. They are equipped with the following types
of ports depending on the variant:
Function
OSM TP22 2 2
OSM ITP53 5 3
OSM ITP62- 6 2
LD
OSM BC08 8
ESM Control 4 4
TP40 level
ESM TP80 8 8
ESM ITP80 8 8
optical line and star topology with OSM, SCALANCE X204-2 or SCALANCE X414-3E and
optical-fiber media module 100 Mbit/s:
The cascade depth and network extension are only limited by the signal propagation delay; the
overall extension can be up to 150 km.
electrical line and star topologies with ESM, SCALANCE X208 or SCALANCE X414-3E:
The cascading depth and network extension are only limited by the signal propagation time, the
overall network extension can be up to 5 km.
Structuring of existing networks by connecting individual subnetworks to OSM/ESM
Optical 100 Mbit/s rings with high-speed media redundancy (up to 50 Industrial Ethernet OSM,
SCALANCE X204-2 or SCALANCE X414-3E per ring; reconfiguration time is max. 0.3 seconds)
Electrical 100 Mbit/s rings with high-speed media redundancy (up to 50 ESM, SCALANCE
X208 or SCALANCE X414-3E per ring; reconfiguration time is max. 0.3 seconds)
Hierarchic redundant rings:
Individual redundant rings (10 Mbit/s or 100 Mbit/s) are connected over two OSM or ESM modules to
a higher-level 100 Mbit/s ring. High-speed media redundancy can be achieved for the individual
rings and for their redundant coupling.
When configuring the network, it is necessary to observe the following boundary conditions:
Network configuration rules such as "Propagation time equivalence" and "Variability value" end at the
port of the switch and have no influence on the cascading of switches.
Redundancy manager RM
When setting up a ring, a module in the ring is switched into RM mode.
The non-ring ports of the RM can be used for the connection of data terminals and networks.
Standby function (for OSM/ESM with 8 ports)
In the case of a redundantly coupled ring, a module in the ring that is linked to the neighboring
module over a standby link is switched to standby mode by means of a switch.
Signal mask;
the signal mask is set to the current status of the module (setpoint) by pushbutton operation. The
signal mask defines which ports and which voltage feeders are to be monitored. The signal contact
only reports an error, if a monitored port or a monitored feeder fails (deviation of setpoint/actual
status).
Industrial Ethernet OSM/ESM can also be monitored by means of network management. The following
interfaces are provided for this:
Network management
Network management offers the following functions:
Password-protected dialup for "Administrator" (read and write authorization) and "User" (read
only)
Reading of version and status information
Setting the signal and standby mask and address information
Permanent parameterization of the ports and filter tables (filter tables only for OSM/ESM with 8
ports)
Output of statistical information
Diagnosis of data traffic by means of a parameterizable mirror port with a standard commercial
network analyzer
Loading of new firmware or the configuration data via the network by a TFTP server
Saving the configuration data or log table via the network on a TFTP server
If faults occur in the network, the OSM/ESM can send error messages (traps) to a network management
system or also e-mails to a predefined network administrator.
Remote Monitoring (RMON) offers the following functions for OSM/ESM modules with 8 ports:
The OSM/ESM can collect statistical data in accordance with RMON Standards 1 to 3. These include,
for example, fault statistics that are kept for each port.
This information can be read out from the OSM/ESM through Web-based management in the statistics
sub-area.
Technical specifications
Technical specifications
Input voltage:
Rated value 24 V DC
Power loss at 24 V DC 20 W
Cable length with RJ45 0 to 100 m with FC RJ45 Plug 180 and FC
connection method cables
0 to 10 m with TP Cord
Cascading depth
Construction
Approvals
UL 1950
Ordering data