Cpu 315-2ag - Speed7
Cpu 315-2ag - Speed7
Disclaimer of The contents of this manual were verified with respect to the hard- and
liability software.
However, we assume no responsibility for any discrepancies or errors. The
information in this manual is verified on a regular basis and any required
corrections will be included in subsequent editions.
Suggestions for improvement are always welcome.
Any other trademarks referred to in the text are the trademarks of the
respective owner and we acknowledge their registration.
This manual describes the System 300S SPEED7 CPUs from VIPA with
firmware version 3.0.0 and up. Here you may find -besides of a product
overview- a detailed description of the single modules. You’ll receive
information about the connection and the deployment of the System 300S
CPUs.
Contents
User considerations ................................................................................. 1
Safety information .................................................................................... 2
Chapter 1 Basics .............................................................................. 1-1
Safety Information for Users................................................................. 1-2
Hints for the deployment of the MPI interface....................................... 1-3
Green Cable from VIPA........................................................................ 1-4
General description of the System 300................................................. 1-5
System 300S........................................................................................ 1-6
Hints for the Project Engineering........................................................ 1-10
Operating structure of a CPU ............................................................. 1-14
CPU 31xS Applications ...................................................................... 1-15
Operands of the CPU 31xS ................................................................ 1-15
Chapter 2 Assembly and installation guidelines............................ 2-1
Overview .............................................................................................. 2-2
Installation dimensions ......................................................................... 2-3
Installation Standard-Bus ..................................................................... 2-4
Assembly SPEED-Bus ......................................................................... 2-5
Cabling................................................................................................. 2-8
Installation Guidelines ........................................................................ 2-12
Chapter 3 Hardware description CPU 31xS.................................... 3-1
System Overview ................................................................................. 3-2
Structure .............................................................................................. 3-9
Components....................................................................................... 3-12
In-/Output range CPU 314ST ............................................................. 3-16
Technical Data ................................................................................... 3-19
Chapter 4 Deployment CPU 31xS.................................................... 4-1
Assembly SPEED-Bus ......................................................................... 4-2
Start-up behavior.................................................................................. 4-4
Addressing ........................................................................................... 4-5
Initialization Ethernet PG/OP channel .................................................. 4-8
Access to the internal Web page........................................................ 4-11
Project engineering ............................................................................ 4-13
CPU parameterization ........................................................................ 4-19
Parameterization of modules.............................................................. 4-24
Project transfer................................................................................... 4-25
Operating modes................................................................................ 4-30
Overall reset....................................................................................... 4-33
Firmware update ................................................................................ 4-35
Factory reset ...................................................................................... 4-38
Memory extension with MCC.............................................................. 4-39
Extended know-how protection........................................................... 4-40
MMC-Cmd - Auto commands ............................................................. 4-42
VIPA specific diagnostic entries ......................................................... 4-44
Using test functions for control and monitoring of variables................ 4-48
User considerations
Objective and This manual describes the System 300S SPEED7 CPUs from VIPA. It
contents contains a description of the construction, project implementation and
usage.
Target audience The manual is targeted at users who have a background in automation
technology.
Structure of the The manual consists of chapters. Every chapter provides a self-contained
manual description of a specific topic.
Icons Important passages in the text are highlighted by following icons and
Headings headings:
Danger!
Immediate or likely danger.
Personal injury is possible.
Attention!
Damages to property is likely if these warnings are not heeded.
Note!
Supplementary information and useful tips.
Safety information
Danger!
This device is not certified for applications in
• in explosive environments (EX-zone)
Disposal National rules and regulations apply to the disposal of the unit!
Chapter 1 Basics
Overview This Basics contain hints for the usage and information about the project
engineering of a SPEED7 system from VIPA.
General information about the System 300S like dimensions and
environment conditions will also be found.
The hints for the MPI interface and the Green Cable should be regarded in
this chapter!
Attention!
Personnel and instruments should be grounded when working on
electrostatically sensitive modules.
2
What is MP2I? The MP I jack combines 2 interfaces in 1:
• MPI interface
• RS232 interface
Please regard that the RS232 functionality is only available by using the
Green Cable from VIPA.
Deployment as The MPI interface provides the data transfer between CPUs and PCs. In a
MPI interface bus communication you may transfer programs and data between the
CPUs interconnected via MPI.
Connecting a common MPI cable, the MPI jack supports the full MPI
functionality.
Deployment as For the serial data transfer from your PC, you normally need a MPI
RS232 interface only transducer. Fortunately you may also use the "Green Cable" from VIPA.
via "Green Cable" You can order this under the order no. VIPA 950-0KB00.
The "Green Cable" supports a serial point-to-point connection for data
2
transfer via the MP I jack exclusively for VIPA CPU's.
Please regard the hints for the deployment of the "Green Cable" on the
following page.
What is the The Green Cable is a green connection cable, manufactured exclusively for
Green Cable? the deployment at VIPA System components.
The Green Cable is a programming and download cable for VIPA CPUs
2
with MP I jack and VIPA fieldbus masters. The Green Cable from VIPA is
available under the order no. VIPA 950-0KB00.
The System 300 The System 300 is a modular automation system for middle and high
performance needs, that you can use either central or decentral. The single
modules are directly clipped to the profile rail and are connected together
with the help of bus clips at the backside.
The CPUs of the System 300 are instruction set compatible to S7-300 from
Siemens.
System 300V VIPA differentiates between System 300V and System 300S.
System 300S • System 300V
The System 300V allows you to resolve automation tasks central and
decentral. The single modules of the System 300V from VIPA are
similar in construction to Siemens. Due to the compatible backplane
bus, the modules from VIPA and Siemens can be mixed.
• System 300S
The System 300S extends the central area with high-speed CPUs that
have the integrated SPEED7 chip. Additionally some CPU's have got a
parallel SPEED-Bus that allows the modular connection of fast
peripheral modules like IOs or bus master.
Manual overview This manual describes the System 300S. This includes the SPEED7-CPUs
31xS and the peripheral modules for SPEED-Bus (framed thick green).
The description of the System 300V CPU 31x without SPEED7 and the
concerning peripheral modules like digital and analog in-/output modules,
power supplies and bus coupler is to find in the HB 130.
System 300S
Overview The CPUs 31xS are based upon the SPEED7 technology. This supports
the CPU at programming and communication by means of co-processors
that causes a power improvement for highest needs.
Except of the basic variant, all SPEED7-CPUs are provided with a parallel
SPEED-Bus that enables the additional connection of up to 16 modules
from the SPEED-Bus periphery. While the standard peripheral modules are
plugged-in at the right side of the CPU, the SPEED bus peripheral modules
are connected via a SPEED-Bus bus connector at the left side of the CPU.
CPU 31xS The System 300S series consists of a number of CPUs. These are
programmed in STEP7 from Siemens. For this you may use WinPLC7
from VIPA or the Siemens SIMATIC Manager.
CPUs with integrated Ethernet interfaces or additional serial interfaces
simplify the integration of the CPU into an existing network or the
connection of additional peripheral equipment.
The user application is stored in the battery buffered RAM or on an
additionally pluggable MMC storage module.
Due to the automatic address allocation, the deployment of the CPUs 31xS
allows to address 32 peripheral modules.
Additionally all CPU 31xS except of the basic version have got a parallel
SPEED-Bus that allows the modular connection of fast peripheral modules
like IOs or bus master.
SPEED-Bus The SPEED-Bus is a 32Bit parallel bus developed from VIPA with a
maximum data rate of 40MByte/s. Via the SPEED-Bus you may connect up
to 16 SPEED-Bus modules to your CPU 31xS.
In opposite to the "standard" backplane bus where the modules are
plugged-in at the right side of the CPU by means of single bus connectors,
the modules at the SPEED-Bus are plugged-in at the left side of the CPU
via a special SPEED-Bus rail.
VIPA delivers profile rails with integrated SPEED-Bus for 2, 6, 10 or 16
SPEED-Bus peripheral modules with different lengths.
Memory Every CPU 31xS has an integrated work memory. During program run the
management total memory is divided into 50% for program code and 50% for data.
Starting with CPU firmware 3.0.0 there is the possibility to extend the total
memory to its maximum by means of a MCC memory extension card.
Integrated The CPUs of the System 300S series have an integrated Profibus DP
Profibus master. Via the DP master with a data range of 1kByte for in- and output
DP master you may address up to 125 DP slaves.
The project engineering takes place in WinPLC7 from VIPA or in the
hardware configurator from Siemens.
Integrated Every CPU 31xS has an Ethernet interface for PG/OP communication. Via
Ethernet PG/OP the "PLC" functions you may directly access the Ethernet PG/OP channel
channel and program res. remote control your CPU. A max. of 2 PG/OP
connections is available.
You may also access the CPU with a visualization software via these
connections.
Dimensions/ • Available lengths of the profile rail in mm: 160, 482, 530, 830 and 2000
Weight • Dimensions of the basic enclosure:
1tier width: (HxWxD) in mm: 40x125x120
2tier width: (HxWxD) in mm: 80x125x120
Compatibility Modules and CPUs of the System 300 from VIPA and Siemens may be
used at the "Standard" bus as a mixed configuration.
The project engineering takes place in WinPLC7 from VIPA or in the
hardware configurator from Siemens.
The SPEED7 CPUs from VIPA are instruction compatible to the
programming language STEP®7 from Siemens and may be programmed
via WinPLC7 from VIPA or via the Siemens SIMATIC Manager.
Here the instruction set of the S7-400 from Siemens is used.
Note!
Please do always use the CPU 318-2DP (6ES7 318-2AJ00-0AB0/V3.0)
from Siemens of the hardware catalog to project a SPEED7-CPU from
VIPA.
For the project engineering, a thorough knowledge of the Siemens
SIMATIC Manager and the hardware configurator from Siemens is
required!
Green Cable For project engineering of your DP slave you may transfer your projects
from your PC to the CPU serial via MPI by using the "Green Cable". Please
also regard the hints to the Green Cable in this chapter.
Integrated Every CPU res. bus coupler comes with an integrated power supply. The
power supply power supply has to be supplied with DC 24V. By means of the supply
voltage, the bus coupler electronic is supplied as well as the connected
modules via backplane bus. Please regard that the integrated power supply
may supply the backplane bus the backplane bus (SPEED-Bus and
Standard-Bus) depending on the CPU with a sum with max. 5A.
The power supply is protected against inverse polarity and overcurrent.
Every SPEED-Bus rail has a plug-in option for an external power supply.
This allows you to raise the maximum current at the backplane bus for 6A.
Access options for The following overview shows all access options for project engineering
project engineering and firmware update.
and firmware update
DP Adapter
CPU
DP master
MPI Adapter
Green Cable MP2I CPU DP
RN
PC RS232
Proj. Proj. Firmw.
Power ON RAM Flash
PG/OP
Proj. Firmw.
RAM Proj./Firmw.
RAM Flash
WinPLC7 from VIPA
System data
SIMATIC Manager RN
overall reset Tip Web
from Siemens
ST 3Sec.
MR
Web-Browser MMC TP
RJ45
MMC
Ethernet
Overview For the project engineering of a SPEED7 system please follow this
approach:
Note!
Please do always use the CPU 318-2DP (6ES7 318-2AJ00-0AB0/V3.0)
from Siemens in the hardware catalog to configure a CPU 31xS from VIPA.
For the project engineering, a thorough knowledge of the SIMATIC
Manager and the hardware configurator from Siemens is required!
Bus extension with To extend the bus you may use the IM 360 from Siemens, where 3 further
IM 360 and IM 361 extensions racks can be connected via the IM 361. Bus extensions must be
placed at slot 3.
More detailed information is to be found in the chapter "Deployment CPU
31xS" at "Addressing".
Standard bus
(Extension 1)
Slot Module
1
2
3 IM361
4 CP342-5
5 343-1EX11
6 343-1EX11
7 CP342-5
8
Slot: 108 107 106 105 104 103 102 101 100 Se
ttin
go
f th
9
es
lot
loc
10
at ion
via 11
Pro
fibu
sa
ddr
e ss
DP master system for SPEED-Bus modules
(108) VIPA (106) VIPA (104) VIPA (102) VIPA (100) VIPA
The according module is to be taken over from the HW catalog of vipa_speedbus on slot 0.
Note!
The sequence of the DPM- and CP function groups is insignificant. You
only have to take care to regard the sequence within a function group
(DP1, DP2... res. CP1, CP2 ...).
Project engineering The hardware configuration and Profibus project engineering happens in
of the DP master at the SIMATIC Manager from Siemens. You have to parameterize a virtual
the SPEED-Bus CP 342-5 (342-5DA02 V5.0) for every SPEED-Bus-DP master at the
standard bus following the real modules and connect it with the depending
DP slaves.
Project engineering The project engineering of the CANopen master at the SPEED-Bus
of the CAN master happens in WinCoCT (Windows CANopen Configuration Tool) from VIPA.
at the SPEED-Bus you export your project from WinCoCT as wld-file. This wld-file can be
imported into the hardware configurator from Siemens.
An additional inclusion at the standard bus is not necessary.
Project engineering The project engineering of the IBS master system takes place in your CPU
of the Interbus user application using the VIPA FCs.
master at the An additional inclusion at the standard bus is not necessary.
SPEED-Bus
General The CPU contains a standard processor with internal program memory. In
combination with System 300S peripherals the unit provides a powerful
solution for process automation applications within the System 300S family.
A CPU supports the following modes of operation:
• cyclic operation
• timer processing
• alarm controlled operation
• priority based processing
Cyclic processing Cyclic processing represents the major portion of all the processes that
are executed in the CPU. Identical sequences of operations are repeated in
a never ending cycle.
Timer processing Where a process requires control signals at constant intervals you can
initiate certain operations based upon a timer, e.g. not critical monitoring
functions at one-second intervals.
Alarm controlled If a process signal requires a quick response you would allocate this signal
processing to an alarm controlled procedure. An alarm can activate a procedure in
your program.
Priority based The above processes are handled by the CPU in accordance with their
processing priority. Since a timer or an alarm event requires a quick reaction, the
CPU will interrupt the cyclic processing when these high-priority events
occur to react to the event. Cyclic processing will resume, once the
reaction has been processed. This means that cyclic processing has the
lowest priority.
System routine The system routine organizes all those functions and procedures of the
CPU that are not related to a specific control application.
User application This consists of all the functions that are required for the processing of a
specific control application. The operating modules provide the interfaces
to the system routines.
Process image The user application can quickly access the process image of the inputs
and periphery and outputs PAA/PAE. You may manipulate the following types of data:
• individual Bits
• Bytes
• Words
• Double words
You may also gain direct access to peripheral modules via the bus from
user application. The following types of data are available:
• Bytes
• Words
• Blocks
Bit Memory The bit memory is an area of memory that is accessible by means of
certain operations. Bit memory is intended to store frequently used working
data.
You may access the following types of data:
• individual Bits
• Bytes
• Words
• Double words
Timers and In your program you may load cells of the timer with a value between 10ms
counters and 9990s. As soon as the user application executes a start-operation, the
value of this timer is decremented by the interval that you have specified
until it reaches zero.
You may load counter cells with an initial value (max. 999) and increment
or decrement these when required.
Data Blocks A data block contains constants or variables in the form of bytes, words or
double words. You may always access the current data block by means of
operands.
You may access the following types of data:
• individual Bits
• Bytes
• Words
• Double words
Overview In this chapter you will find all information, required for the installation and
the cabling of a process control with the components of the System 300.
Overview
General Except of the basic variant, all SPEED7-CPUs are provided with a parallel
SPEED-Bus that enables the additional connection of up to 16 modules
from the SPEED-Bus periphery.
While the standard peripheral modules are plugged-in at the right side of
the CPU, the SPEED-Bus peripheral modules are connected via a SPEED-
Bus bus connector at the left side of the CPU.
VIPA delivers profile rails with integrated SPEED-Bus for 2, 6, 10 or 16
SPEED-Bus peripheral modules with different lengths.
Serial The single modules are directly installed on a profile rail and connected via
Standard bus the backplane bus coupler. Before installing the modules you have to clip
the backplane bus coupler to the module from the backside.
The backplane bus coupler are included in the delivery of the peripheral
modules.
Parallel With SPEED-Bus the bus connection happens via a SPEED-Bus rail
SPEED-Bus integrated in the profile rail at the left side of the CPU. Due to the parallel
SPEED-Bus not all slots must be occupied in sequence.
SLOT 1 for additional At SLOT 1 DCDC) you may plug either a SPEED-Bus module or an
power supply additional power supply.
Assembly You may assemble the System 300 horizontally, vertically or lying.
possibilities
vertical
horizontal assembly assembly
Please regard the allowed environment tempera-
tures:
CPU
• horizontal assembly: from 0 to 60°C
SLOT2 SLOT1
• vertical assembly:
DCDC
from 0 to 40°C
• lying assembly: from 0 to 40°C
CPU
lying assembly
SLOT1
DCDC
SLOT2
Installation dimensions
Overview Here follow all the important dimensions of the System 300.
Dimensions
65mm
122mm
40mm
Installation
125mm
dimensions
120mm
125 mm
175mm
Installation Standard-Bus
Approach If you do not deploy SPEED-Bus modules, the assembly at the standard
bus happens at the right side of the CPU with the following approach:
Danger!
• Before installing or overhauling the System 300, the power supplies
must be disconnected from voltage (pull the plug or remove the fuse)!
Assembly SPEED-Bus
CPU
SLOT6 SLOT5 SLOT4 SLOT3 SLOT2 SLOT1
DCDC
Installation of the
profile rail
• Bolt the profile rail with the background (screw
65mm size: M6), so that you still have minimum 65mm
space above and 40mm below the profile rail.
• Please look for a low-impedance connection
between profile rail and background
CPU
SLOT2 SLOT1
DCDC
40mm
Profile rail
Order numberSPEED- A B C
Bus slots
VIPA 390-1AB60 - 160mm 140mm 10mm
VIPA 390-1AE80 - 482mm 466mm 8.3mm
VIPA 390-1AF30 - 530mm 500mm 15mm
122
Installation
SPEED-Bus-
Module
Installation CPU
without Standard-
Bus-Modules
SLOT2 SLOT1
DCDC
CPU
Please regard that only the CPU 317S may be
deployed at the SPEED-Bus!
Installation CPU
with Standard-Bus-
Modules
CPU
SLOT2 SLOT1
DCDC
Installation
Standard-Bus-
Modules
CPU
SLOT2 SLOT1
DCDC
Danger!
• Before installing or overhauling the System 300V, the power supplies
must be disconnected from voltage (pull the plug or remove the fuse)!
Cabling
Overview The power supplies and CPUs are exclusively delivered with CageClamp
contacts. For the signal modules the front connectors are available from
VIPA with screw contacts. In the following all connecting types of the power
supplies, CPUs and input/output modules are described.
Danger!
• Before installation or overhauling, the power supplies must be
disconnected from voltage (pull the plug or remove the fuse)!
CageClamp For the cabling of power supplies, bus couplers and parts of the CPU, gray
technology (gray) connectors with CageClamp technology are used.
2 2
You may connect wires with a cross-section of 0.08mm to 2.5mm . You
can use flexible wires without end case as well as stiff wires.
1
The picture on the left side shows the cabling step by step from top view.
CageClamp For the cabling of e.g. the power supply of a CPU, green plugs with
technology (green) CageClamp technology are deployed.
2
Here also you may connect wires with a cross-section of 0.08mm to
2
2.5mm . You can use flexible wires without end case as well as stiff wires.
The picture on the left side shows the cabling step by step from top view.
2
• For cabling you push the locking vertical to the inside with a suiting
screwdriver and hold the screwdriver in this position.
• Insert the insulation striped wire into the round opening. You may use
wires with a cross-section from 0.08mm2 to 2.5mm2.
• By removing the screwdriver the wire is connected safely with the plug
connector via a spring.
Note!
In opposite to the gray connection clamp from above, the green connection
clamp is realized as plug that can be clipped off carefully even if it is still
cabled.
Front connectors In the following the cabling of the three variants of the front-facing
of the in-/output connector is shown:
modules For the I/O modules the following plugs are available at VIPA:
Strip the insulation of your wires. If needed, use core end cases.
If you want to lead out your cables from the bottom of the module, start with the cabling from
bottom to top, res. from top to bottom, if the cables should be led out at the top.
... continue
20pole screw connection 40pole screw connection
VIPA 392-1AJ00 VIPA 392-1AM00
Push the release key at the front connector on Bolt the fixing screw of the front connector.
the upper side of the module and at the same
time push the front connector into the module
until it locks.
Fill out the labeling strip to mark the single channels and push the strip into the front flap.
Installation Guidelines
General The installation guidelines contain information about the interference free
deployment of System 300 systems. There is the description of the ways,
interference may occur in your control, how you can make sure the
electromagnetic digestibility (EMC), and how you manage the isolation.
Possible Electromagnetic interferences may interfere your control via different ways:
interference • Fields
causes
• I/O signal conductors
• Bus system
• Current supply
• Protected earth conductor
Depending on the spreading medium (lead bound or lead free) and the
distance to the interference cause, interferences to your control occur by
means of different coupling mechanisms.
One differs:
• galvanic coupling
• capacitive coupling
• inductive coupling
• radiant coupling
Basic rules for In the most times it is enough to take care of some elementary rules to
EMC guarantee the EMC. Please regard the following basic rules when installing
your PLC.
• Take care of a correct area-wide grounding of the inactive metal parts
when installing your components.
- Install a central connection between the ground and the protected
earth conductor system.
- Connect all inactive metal extensive and impedance-low.
- Please try not to use aluminum parts. Aluminum is easily oxidizing
and is therefore less suitable for grounding.
• When cabling, take care of the correct line routing.
- Organize your cabling in line groups (high voltage, current supply,
signal and data lines).
- Always lay your high voltage lines and signal res. data lines in
separate channels or bundles.
- Route the signal and data lines as near as possible beside ground
areas (e.g. suspension bars, metal rails, tin cabinet).
• Proof the correct fixing of the lead isolation.
- Data lines must be laid isolated.
- Analog lines must be laid isolated. When transmitting signals with
small amplitudes the one sided laying of the isolation may be
favorable.
- Lay the line isolation extensively on a isolation/protected earth con-
ductor rail directly after the cabinet entry and fix the isolation with
cable clamps.
- Make sure that the isolation/protected earth conductor rail is
connected impedance-low with the cabinet.
- Use metallic or metallized plug cases for isolated data lines.
• In special use cases you should appoint special EMC actions.
- Wire all inductivities with erase links, that are not addressed by the
System 300V modules.
- For lightening cabinets you should prefer incandescent lamps and
avoid luminescent lamps.
• Create an homogeneous reference potential and ground all electrical
operating supplies when possible.
- Please take care for the targeted employment of the grounding
actions. The grounding of the PLC is a protection and functionality
activity.
- Connect installation parts and cabinets with the System 300V in star
topology with the isolation/protected earth conductor system. So you
avoid ground loops.
- If potential differences between installation parts and cabinets occur,
lay sufficiently dimensioned potential compensation lines.
Outline The CPUs 31xS are available in different versions that are described in the
following chapter.
The chapter closes with the technical data.
System Overview
®
SPEED7-CPUs These CPUs are instruction set compatible to STEP 7 from Siemens and
are designed for medium and large applications with integrated 24V power
supply unit. Every CPU has a slot for memory cards at the front side, an
integrated Ethernet interface for PG/OP, a RS485 interface for Profibus DP
master communication and a MPI interface and is developed for future
memory extensions by means of MCC.
You may poll sensors and control actuators via standardized commands
and programs.
Depending on the CPU type you have additionally an integrated CP 343 or
a RS485 interface for communication tasks. This CPU series gains you
access to the peripheral modules of the System 300V for the standard bus.
Additionally all CPUs 31xS except of the basic version provide a parallel
SPEED-Bus that allows you to connect fast peripheral modules like IOs or
bus master modular.
The following descriptions in this manual refers to the complete
SPEED7-CPU family CPU 31xS from VIPA with firmware version 3.0.0
and up if nothing else is mentioned.
X5
X2 X3
X1
DC 24V
+
-
+
-
Ordering data
Type Order number Description
2
315SB/DPM VIPA 315-2AG10 MP I interface, card slot, real time clock, Ethernet interface for
PG/OP, Profibus DP master
315SN/NET VIPA 315-4NE11 MP2I interface, card slot, real time clock, Ethernet interface for
PG/OP, Profibus DP master, CP 343
X5
X2 X3
X1
DC 24V
+
-
+
-
Ordering data
Type Order number Description
315SB/DPM VIPA 315-2AG12 MPI interface, card slot, real time clock, Ethernet interface for
PG/OP, Profibus DP master
315SN/NET VIPA 315-4NE12 MPI interface, card slot, real time clock, Ethernet interface for
PG/OP, Profibus DP master, CP 343
.0 RUN ERR
.1 STOP DE
.2 SF IF
.3 FRCE
.4 MCC
MCC
.5 A
S +
.6 -
.7 RUN
STOP
MRES
DI
X 2
DIO +1 VIPA 314-6CF01 3 4
.0
.1
.2 X1
.3
.4
.5
.6
.7
X2 X3
SF
Ordering data
Type Order number Description
314ST/DPM VIPA 314-6CF01 MP2I interface, card slot, real time clock, Ethernet interface for
PG/OP, Profibus DP master, SPEED-Bus,
DI 8...16xDC24V / DO 8...0xDC24V, 0.5A,
AI 4x12Bit / AO 2x12Bit / AI 1xPt100, 4 Counter
.0 RUN ERR
.1 STOP DE
.2 SF IF
.3 FRCE
.4 MCC
MCC
.5 A
S +
.6 -
.7 RUN
STOP
MRES
DI
X 2
DIO +1 VIPA 314-6CF01 3 4
.0
.1
.2 X1
.3
.4
.5
.6
.7
X2 X3
SF
Ordering data
Type Order number Description
314ST/DPM VIPA 314-6CF02 MPI interface, card slot, real time clock, Ethernet interface for
PG/OP, Profibus DP master, SPEED-Bus,
DI 8...16xDC24V / DO 8...0xDC24V, 0.5A,
AI 4x12Bit / AO 2x12Bit / AI 1xPt100, 4 Counter
X5
X2 X3
X1
DC 24V
+
-
+
-
Ordering data
Type Order number Description
317SE/DPM VIPA 317-2AJ11 MP2I interface, card slot, real time clock, Ethernet interface for
PG/OP, Profibus DP master, SPEED-Bus
2
317SN/NET VIPA 317-4NE11 MP I interface, card slot, real time clock, Ethernet interface for
PG/OP, Profibus DP master, SPEED-Bus, CP 343
X5
X2 X3
X1
DC 24V
+
-
+
-
Ordering data
Type Order number Description
317SE/DPM VIPA 317-2AJ12 MPI interface, card slot, real time clock, Ethernet interface for
PG/OP, Profibus DP master, SPEED-Bus
317SN/NET VIPA 317-4NE12 MPI interface, card slot, real time clock, Ethernet interface for
PG/OP, Profibus DP master, SPEED-Bus, CP 343
Structure
5
for PG/OP channel
2
[7] 315-2AG10 MP I interface
+ 6 315-2AG12 MPI interface
-
X1 7
[8] Profibus DP/PtP interface
X2 X3
MP²I PB-DP
CPU 315SN/NET
315-4NE1x
CPU 314ST/DPM
314-6CF0x
CPU 317SE/DPM
317-2AJ1x
8
X1
+
- X2 X3
DC 24V MP²I PB-DP
9
CPU 317SN/NET
317-4NE1x
Components
CPU 31xS The here mentioned components are part of every CPU 31xS.
LEDs CPU part The CPU has got one row of LEDs on the front side. The following table
shows you the usage of the LEDs and the according colors:
Label Color Meaning
PWR green CPU part is provided with internal 5V
RUN green CPU is in the operating mode RUN
STOP yellow CPU is in the operating mode STOP
SF red On at system errors (hardware defect)
FRCE yellow On as soon as variables are forced (fixed)
MCC yellow Blinks at storage media access
A green Activity: on: physically connected
off: no physical connection
blinks: shows Ethernet activity
S green Speed: on: 100MBit
off: 10MBit
Note!
All LEDs of the CPU part are blinking three times, when accessing an
invalid storage media or when it is pulled out during the reading process.
Storage media slot As external storage medium for applications and firmware you may use a
MMC storage module (Multimedia card) or a MCC memory extension card.
The MCC can additionally be used as an external storage medium.
Both VIPA storage media are pre-formatted with the PC format FAT16 and
can be accessed via a card reader. An access to the storage media always
happens after an overall reset and PowerON.
Power supply The CPU has an integrated power supply. The power supply has to be
provided with DC 24V. For this serves the double DC 24V slot, that is
underneath the flap.
Via the power supply not only the internal electronic is provided with
voltage, but by means of the backplane bus also the connected modules.
The power supply is protected against polarity inversion and overcurrent.
X1
The internal electronic is galvanically connected with the supply voltage.
+ Please regard that the integrated power supply may provide the backplane
- bus (SPEED and standard bus) with a sum of max. 5A depending on the
DC 24V
CPU. Every SPEED-Bus bar has as option a slot for an external power
supply. This allows you to raise the max. current at the backplane bus for 6A.
Operating mode With the operating mode switch you may switch the CPU between STOP
switch and RUN. The operating mode START-UP is driven automatically from the
RUN CPU between STOP and RUN.
STOP Placing the switch to Memory Reset (MRES), you request an overall reset
MRES with following load from MMC (project or firmware update).
Memory Every CPU 31xS has an integrated work memory. During program run the
management total memory is divided into 50% for program code and 50% for data.
Starting with CPU firmware 3.0.0 there is the possibility to extend the total
memory to its maximum by means of a MCC memory extension card.
2
MPI interface The MP I interface handles the data exchange between CPU and PC. Via
2
MP I interface a bus communication you may transfer applications and data with up to
12MBaud between the CPUs that are connected via MPI.
For a serial transfer from your PC you normally need a MPI transducer.
2
The "Green Cable" may be used if your CPU has a MP I interface. The
"Green Cable" is exclusively available from VIPA with order number
950-0KB00. The "Green Cable" may only be used directly and exclusively
2
at CPUs with MP I interface. Please also regard the hints in the chapter
2
"Basics"! With an MP I interface the data transmission rate is limited to
1.5MBaud. The MPI-slot has the following pin assignment:
9pin jack
Pin Assignment
1 reserved (must not be connected) See Hints for the
5 deployment of the MPI interface in chapter "Basics".
9 2 M24V
4
3 RxD/TxD-P (Line B)
8
3 4 RTS
7 5 M5V
2
6 P5V
6
1 7 P24V
8 RxD/TxD-N (Line A)
9 n.c.
Ethernet PG/OP The RJ45 jack serves the interface to the Ethernet PG/OP channel. This
channel interface allows you to program res. remote control your CPU, to access
the internal website or to connect a visualization via up to 2 PG/OP
connections. Here a transfer rate of 10MBit at half duplex is supported.
For online access to the CPU via Ethernet PG/OP channel valid IP address
parameters have to be assigned to this. More may be found at chapter
"Deployment CPU 31xS" at "Initialization Ethernet PG/OP channel".
The jack has the following assignment:
8pin RJ45-slot:
1 2 3 4 5 6 7 8 Pin Assignment Pin Assignment
1 Transmit + 5 -
2 Transmit - 6 Receive -
3 Receive + 7 -
4 - 8 -
Communication Additionally to the Ethernet PG/OP channel the following CPUs provide
components further communication components:
• CPU 315SB/DPM Profibus DP master / PtP via RS485
• CPU 315SN/NET Profibus DP master / PtP via RS485 and CP 343
• CPU 314ST/DPM Profibus DP master / PtP via RS485
• CPU 317SE/DPM Profibus DP master / PtP via RS485
• CPU 317SN/NET Profibus DP master / PtP via RS485 and CP 343
RS485 interface with Every CPU 31xS has a integrated RS485 interface. The functionality of this
configurable interface can be configured by the mean of the parameter "Function
functionality RS485" of the SPEED-Bus CPUs hardware configuration.
PtP functionality Using the PtP functionality the RS485 interface is allowed to connect via
serial point-to-point connection to different source res. target systems.
Here the following protocols are supported:
ASCII, STX/ETX, 3964R, USS and Modbus-Master (ASCII, RTU)
RS485 interface RS485 interface of both functionalities have the same pin assignment:
Communication The CP 343 offers you a communication processor. This serves 8 PG/OP
processor CP 343 channels and 16 configurable connections (max. 8 at CPU 315-4NE11).
The project engineering happens using NetPro from Siemens as CP343-
1EX11.
Via the RJ45 jack you may connect the CP 343 to Twisted-Pair-Ethernet.
The slot has the following pin assignment:
Overview The CPU 314ST has the following integrated analog and digital in- and
output ranges:
+0
CPU314ST
1L+ PWR RUN
2 22
V
3 23
CH0
A
4 24
5 25
V DC 24V
6 26
CH1 DI
A
7 27
8 28
AI V
9 29
CH2
A
10 30 M
11 31 L+
24V DC
V 32
12
CH3
A 33
13
14 Pt100 34
15 CH4
35
16 DIO DC 24V
36
17
CH5
37
AO 18
38
19 CH6
39
20
M ANA
40 M
Analog part The analog part consists of 4 input, 1 Pt100 and 2 output channels. 10byte
for input and 4byte for output are used for the process image.
The channels of the module are galvanically separated from the SPEED-
Bus via DC/DC transducer and optocouplers.
Attention!
Temporarily not used analog inputs with activated channel must be
connected to the concerning ground.
Status indicator
Pin assignment
Note!
To avoid measuring errors, you should connect only one measuring type
per channel.
Digital part The digital part consists of 8 inputs and 8 in-/outputs. Each of this in-/
outputs monitors its state via a LED. Via the parameterization you may
assign alarm properties to every digital input. Additionally the digital inputs
are parameterizable as counter.
The output channels provide a diagnostic function, i.e. as soon as an
output is active, the according input is set to "1". At a short circuit at the
load, the input is pulled to "0" and by evaluating the input, the error may be
recognized. The DIO part has to be provided with external DC 24V.
Status indicator
Pin assignment
Pin Assignment Connection LEDs
DI:
21 Power supply +DC 24V 21 L+ .0 ... .7 LEDs (green)
+0 I+0.0 to I+0.7
22 Input I+0.0 / Counter 0(A) 22
1L+
(each Byte)
23 Input I+0.1 / Counter 0(B) 23
.0 Starting with app.
24 Input I+0.2 / Gate0/Latch0/Reset0 24 .1 15V the signal "1"
25 Input I+0.3 / Counter 1(A) 25 .2 at the input is
DC 24V
26 Input I+0.4 / Counter 1(B) DI 26 .3 recognized and
.0 ... .7
27 .4 the according LED
27 Input I+0.5 / Gate1/Latch1/Reset1
.5
28 Input I+0.6 / Counter 2(A) 28
29
.6
29 Input I+0.7 / Counter 2(B)
.7
30
30 Ground DI M
31 L+
31 Power supply +DC 24V DI DIO:
32
32 I/Q+1.8 / Gate2/Latch2/Reset2 DIO
+1 2L+ LED (green)
33
33 I/Q+1.9 / Counter 3(A) 2L+ L+ Supply voltage
34 I/Q+1.10 / Counter 3(B)
34
.0 available for DIO
35 I/Q+1.11 / Gate3/Latch3/Reset3 35 .1
DIO DC
36 .2
36 I/Q+1.12 / OUT0/Latch0/Reset0 24V
.3 .0 ... .7 LEDs (green)
37 I/Q+1.13 / OUT1/Latch1/Reset1 37
.0 ... .7
.4 I/Q+1.0 to I/Q+1.7
38 I/Q+1.14 / OUT2/Latch2/Reset2 38
.5 on at active
39 I/Q+1.15 / OUT3/Latch3/Reset3 39
.6 output/input
40 Ground DIO 40 M
.7
FF F F LED (red)
01 Overload or short
circuit error
Attention!
Please take care that the voltage at an output channel always is ≤ the
supply voltage via L+.
Further you have to regard that due to the parallel connection of in- and
output channel per group a set output can be provided via a connected
input signal. A thus set output remains active at connected input signal also
the power supply is turned off.
Nonobservance may destroy the module.
Technical Data
CPU 315SB/DPM
RJ45 PG/OP channel PG/OP channel via Ethernet with max. 2 connections
CPU 315SN/NET
RJ45 PG/OP channel PG/OP channel via Ethernet with max. 2 connections
CPU 314ST/DPM
CPU 314ST/PtP
SPEED-Bus
- Data rate 64MBaud
- Current consumption 400mA
Battery buffer / clock Lithium battery, 30 days buffer / yes
Execution time CPU
for bit operation, min. 0.015µs 0,010µs
for word operation, min. 0.015µs 0,010µs
for fixed-point calculation, min. 0.015µs 0,010µs
for floating-point calculation, min. 0.090µs 0,058µs
Flag byte / Timer / Counter 8192 / 512 / 512
Number of blocks FBs 2048, FCs 2048, DBs 4095
CPU 317SE/DPM
CPU 317SN/NET
Overview This chapter describes the employment of a CPU 31xS with SPEED7
technology in the System 300. The description refers directly to the CPU
and to the employment in connection with peripheral modules that are
mounted on a profile rail together with the CPU at SPEED-Bus respectively
standard bus.
Note!
This information is valid for all the CPUs described in this manual, since the
back panel communication between the CPU and the peripheral modules is
the same for all models of CPU!
Assembly SPEED-Bus
horizontal assembly
vertical • At the assembly, please regard the permissible
assembly
environment temperatures:
- horizontal assembly: 0 to 60°C
SLOT2 SLOT1
CPU - vertical/lying assembly: 0 to 40°C
DCDC
profile rail with the ground wire via the dowel pin
2
SLOT2
(min. 10mm ) .
• Mount the power supply left of the SPEED-Bus.
• To install SPEED-Bus modules you put them
between the triangular positioning helps of a slot
65mm labeled with "SLOT ..." and push them
downwards.
• Only "SLOT1 DCDC" allows to mount an
CPU
additional power supply instead of a SPEED-Bus
module.
SLOT2 SLOT1
DCDC
CPU
SLOT2 SLOT1
DCDC
Assembly without
SPEED-Bus
profile rail
Approach • The assembly and grounding of the standard bus
rail happens similar to that of the SPEED-Bus.
• Hang the power supply into position and push it to
the left to app. 5mm before the grounding bolt of
the profile rail.
• Take a bus connector and stick it to the CPU from
the backside like shown.
• Mount the CPU at the right side of the power
supply.
• Repeat this procedure with the peripheral
modules, by clicking a backplane bus coupler,
stick the module right from the modules you've
already fixed, click it downwards and connect it
with the backplane bus coupler of the last module
and bolt it.
• Bolt all modules.
Danger!
• The power supplies must be released before installation and repair
tasks, i.e. before handling with the power supply or with the cabling you
must disconnect current/voltage (pull plug, at fixed connection switch off
the concerning fuse)!
• Installation and modifications only by properly trained personnel!
Start-up behavior
Turn on power After the power supply has been switched on, the CPU changes to the
supply operating mode the operating mode lever shows.
Now you may transfer your project to the CPU via MPI from your
configuration tool res. plug in a MMC with your project and run an overall
reset.
Overall reset The following picture shows the approach once more:
1 2 3 4
3 Sec.
Note!
The transfer of the application program from the MMC into the CPU takes
always place after an overall reset!
Boot procedure with The CPU switches to RUN with the program stored in the battery buffered
valid data in the CPU RAM.
Boot procedure The accumulator/battery is automatically loaded via the integrated power
with empty battery supply and guarantees a buffer for max. 30 days. If this time is exceeded,
the battery may be totally discharged. This means that the battery buffered
RAM is deleted.
In this state, the CPU executes an overall reset. If a MMC is plugged,
program code and data blocks are transferred from the MMC into the work
memory of the CPU.
If no MMC is plugged, the CPU transfers permanent stored "protected"
blocks into the work memory if available.
Information about storing protected blocks in the CPU is to find in this
chapter at "Extended Know-how protection".
Depending on the position of the RUN/STOP lever, the CPU switches to
RUN res. remains in STOP.
This event is stored in the diagnostic buffer as: "Start overall reset
automatically (unbuffered POWER_ON)".
Addressing
Addressing The SPEED7-CPU provides a I/O area (address 0 ... 8191) and a process
Backplane bus image of the in- and outputs (each address 0 ... 255).
I/O devices The process image stores the signal states of the lower address (0 ... 255)
additionally in a separate memory area.
The process image this divided into two parts:
• process image to the inputs (PII)
• process image to the outputs (PIQ)
Up to 32 modules In the hardware configurator from Siemens you may parameterize maximum
in one row up to 8 modules per row. At employment of SPEED7-CPUs you may control
up to 32 modules at the standard bus and 16 further modules at the SPEED-
Bus. CPs and DP masters that are additionally virtual configured at the
standard bus are taken into the count of 32 modules at the standard bus.
For the project engineering of more than 8 modules you may use virtual
line interface connections. For this you set in the hardware configurator the
st
module IM 360 from the hardware catalog to slot 3 of your 1 profile rail.
Now you may extend your system with up to 3 profile rails by starting each
with a IM 361 from Siemens at slot 3.
Define addresses You may access the modules with read res. write accesses to the
by hardware peripheral bytes or the process image.
configuration
To define addresses a hardware configuration via a virtual Profibus system
by including the SPEEDBUS.GSD may be used. For this, click on the
properties of the according module and set the wanted address.
Attention!
Please take care not to configure a double address assignment at
connection via external Profibus-DP masters - required for project
engineering of a SPEED-Bus system! At external DP master systems, the
Siemens hardware configurator does not execute an address check!
Start
Address
digital: 140 136 132 128 0 4 8 12
analog: 2816 2560 2304 2048 256 272 288 304
Example for The following sample shows the functionality of the automatic address
automatic address allocation separated for standard bus and SPEED-Bus:
allocation
Slot number: 1 2 3 4 5
SPEED-Bus
DIO 16xDC24V
Standard bus
DO 16xDC24V
DI 16xDC24V
AO 4x12Bit
CPU 31xS
AI 8x12Bit
PII Address Periphery area Periphery area Address PIQ
0 Input Byte 0
..
Output Byte 8
1
.. Input Byte
.
. Output Byte 9
. .
.. ..
12 Input Byte .
Output Byte 12
13
. Input Byte
.
. Output Byte 13
.
analog digital
analog digital
255 .
up to max 255 255 up to max 255
256 256
. .
. .
.. .
272 Input Byte Output Byte 320
.
.
.. .
. Output Byte 335
287 Input Byte .
.
. .
. .
.. ..
2048 2048
. .
.. .
.
8191 8191
AO 4x12Bit
CPU 31xS
AI 8x12Bit
133
.. Input Byte Output Byte 133
..
.. ..
.. ..
.. ..
.
144 Input Byte Output Byte 136
analog digital
.. ..
.. ..
. .
2048 .. Output Byte 2048 ..
. .
.. ..
. Output Byte 2055
2816 Input Byte ..
.. ..
2831 . ..
. Input Byte .
.. ..
8191 8191
Overview Every CPU 31xS has an integrated Ethernet PG/OP channel. This channel
allows you to program and remote control your CPU with up to 2
connections.
The PG/OP channel also gives you access to the internal web page that
contains information about firmware version, connected I/O devices,
current cycle times etc.
For online access to the CPU via Ethernet PG/OP channel valid IP address
parameters have to be assigned to this by means of the Siemens SIMATIC
manager. This is called "initialization".
Possibilities for There are the following possibilities for assignment of IP address
Initialization parameters (initialization):
• PLC functions with Assign Ethernet address
(starting with firmware V. 1.6.0)
• Hardware project engineering with CP (Minimal project)
Initialization via Please consider that this functionality is supported starting from the
PLC functions firmware version V. 1.6.0. The initialization takes place after the following
proceeding:
• Determine the current Ethernet (MAC) address of your Ethernet PG/OP
st
channel. This always may be found as 1 address under the front flap of
the CPU on a sticker on the left side.
Ethernet address
1. Ethernet PG/OP
2. CP343 (optional)
• Use the [Browse] button to determine the CPU components via MAC
address.
As long as the Ethernet PG/OP channel was not initialized yet, this owns
the IP address 0.0.0.0 and the station name "Onboard PG/OP".
Direct after the assignment the Ethernet PG/OP channel may be reached
by the Siemens SIMATIC manager by means of these IP address
parameters and the Access Path "TCP/IP -> Network card .... Protocol
RFC 1006".
Initialization via • Establish a network connection between Ethernet PG/OP channel of the
minimal project CPU and PC.
• Start the SIMATIC Manager from Siemens and create a new project.
• Add a new System 300 station via Insert > Station > SIMATIC 300-
Station.
• Activate the station "SIMATIC 300" and open the hardware configurator
by clicking on "Hardware".
• Engineer a rack (SIMATIC 300 \ Rack-300 \ Profile rail)
• For the SPEED7-CPUs are configured as CPU 318-2, choose the CPU
318-2 with the order no. 6ES7 318-2AJ00-0AB0 V3.0 from the hardware
catalog. You'll find this at SIMATIC 300 \ CPU 300 \ CPU 318-2.
• Include the CP 343-1EX11 at slot 4 (SIMATIC 300 \ CP 300 \ Industrial
Ethernet \ CP 343-1).
• Type the wanted IP address and subnet mask into the dialog window of
"Properties" of the CP 343-1 and connect the CP with "Ethernet".
• Save and compile your project.
• Transfer your project via MPI or MMC into your CPU. More information
about transfer methods may be found in the chapter "Project transfer".
Direct after the assignment the Ethernet PG/OP channel may be reached
by the Siemens SIMATIC manager by means of these IP address
parameters and the Access Path "TCP/IP -> Network card .... Protocol
RFC 1006".
Access to the The Ethernet PG/OP channel provides a web page that you may access
web page via an internet browser by its IP address. The web page contains
information about firmware versions, current cycle times etc.
The current content of the web page is stored on MMC by means of the
MMC-Cmd WEBPAGE. More information may be found at "MMC-Cmd -
Auto commands".
Web page The access takes place via the IP address of the Ethernet PG/OP channel.
The web page only serves for information output. The monitored values are
not alterable.
... continue
Project engineering
Fast introduction For the employment of the System 300S modules from VIPA at the
SPEED-Bus the inclusion of the System 300S modules via the GSD-file
from VIPA in the hardware catalog is required.
To be compatible with the Siemens hardware configurator the following
steps should be executed:
Standard bus
Slot Module • Start the hardware configurator from Siemens and include the
1 SPEEDBUS.GSD for SPEED7 from VIPA.
2 CPU 318-2
X2 DP • Configure CPU 318-2DP (6ES7 318-2AJ00-0AB0/V3.0) from
X1 MPI/DP Siemens. Configure a possibly existing internal DP master of your
3 SPEED7-CPU via the internal DP master of the CPU 318-2DP. Leave
real Modules MPI/DP of the CPU 318-2DP in MPI mode. The Profibus mode is not
at the standard bus supported.
343-1EX11 • Starting with slot 4, place the System 300 modules in the plugged
(Ethernet PG/OP)
sequence.
343-1EX11
(only CPU 31xSN) • For the internal Ethernet PG/OP channel that every SPEED7-CPU
CPs resp. DP master includes, you have to configure a Siemens CP 343-1 (343-1EX11)
st
at SPEED-Bus as always as 1 module below the really plugged modules.
343-1EX11 resp. 342-5DA02
342-5DA02 V5.0 • If exists the integrated CP 343 of the CPU 31xSN/NET is also
virtual DP master for CPU configured as CP 343-1 (343-1EX11) but always always as 2nd
and every SPEEDbus module module below the before configured PG/OP channel. Else start here
to configure and connect every Ethernet-CP 343 - SPEED-Bus as
Siemens CP 343-1 (343-1EX11) resp. every SPEED-Bus Profibus
(n) VIPA (100) VIPA
DP master as Siemens CP 342-5DA02 V5.0.
... • For the SPEED-Bus you always include, connect and parameterize to
the operating mode DP master the DP master CP 342-5 (342-5DA02
VIPA_SPEEDBUS V5.0) as last module. To this master system you assign every
Slot Order no.
0 CPU at slot 100 SPEED-Bus module as VIPA_SPEEDBUS slave. Here the Profibus
VIPA_SPEEDBUS address corresponds to the slot no. Beginning with 100 for the CPU.
Slot
0
Order no.
Module at slot n Place on slot 0 of every slave the assigned module and alter the
parameters if needed.
• Let with the CPs or DP master (also virtual SPEED-Bus master) at
options the attitude "Save configuration data on the CPU" activated!
Note!
For the project engineering a thorough knowledge of the Siemens
SIMATIC Manager and the hardware configurator from Siemens are
required and assumed!
The GSD files can be found at www.vipa.de at the Service part and at the
VIPA ftp server at ftp.vipa.de/support/profibus_gsd_files.
Steps of the The following text describes the approach of the project engineering in the
project hardware configurator from Siemens at an abstract sample.
engineering The project engineering is separated into 5 parts:
• Project engineering of the CPU
• Project engineering of the real plugged modules at the standard bus
• Project engineering of the PG/OP channel and CP343
(only CPU 31xSN/NET)
• Project engineering of all SPEED-Bus CPs and DP master
• Project engineering of the SPEED-Bus modules in a virtual master
system
Hardware
assembly SPEED-Bus (parallel) Standard bus (serial)
Project • Start the hardware configurator from Siemens with a new project and
engineering insert a profile rail from the hardware catalog.
of the CPU as CPU • Place the following Siemens CPU at slot 2:
318-2DP CPU 318-2DP (6ES7 318-2AJ00-0AB0 V3.0)
• Configure a possibly existing internal DP master of your SPEED7-CPU
via the internal DP master of the CPU 318-2DP. Leave MPI/DP of the
CPU 318-2DP in MPI mode. The Profibus mode is not supported.
Standard bus
DIO DP-Master CP343 CP343 AI AI DP-Master DO CPU 31xS DI DO DIO AI AO Slot Module
1
2 CPU 318-2
X2 DP
X1 MPI/DP
3
Project engineering The modules at the right side of the CPU at the Standard bus are
of the modules at configured with the following approach:
the Standard bus
• Include your System 300 modules at the standard bus in the plugged
sequence starting with slot 4.
• Parameterize the CPU res. the modules where appropriate. The
parameter window opens by a double click on the according module.
Standard bus
Slot Module
1
2 CPU 318-2
X2 DP
X1 MPI/DP
DIO DP-Master CP343 CP343 AI AI DP-Master DO CPU 31xS DI DO DIO AI AO 3
4 DI
5 DO
6 DIO
7 AI
8 AO
9
10
11
Project engineering For the internal Ethernet PG/OP channel that every SPEED7-CPU
of Ethernet PG/OP includes, you have to configure a Siemens CP 343-1 (343-1EX11) always
st
channel and CP 343 as 1 module below the really plugged modules.
as 343-1EX11
If exists the integrated CP 343 of the CPU 31xSN/NET is also configured
and connected as CP 343-1 (343-1EX11) but always below the before
configured PG/OP channel.
Ethernet PG/OP
1
2 CPU 318-2
X2 DP
X1 MPI/DP
CP343
3
4 DI
DIO DP-Master CP343 CP343 AI AI DP-Master DO CPU 31xS DI DO DIO AI AO 5 DO
6 DIO
7 AI
8 AO
Ethernet PG/OP channel
9 343-1EX11
10 343-1EX11
CP 343 (only CPU 31xSN/NET)
11
Set IP parameters Open the property window via double-click on the CP 343-1EX11. Enter
"General" and click at [Properties]. Type in the IP address, subnet mask
and gateway for the CPs and select the wanted subnet.
Project engineering Due to the fact that a Ethernet-CP 343 - SPEED-Bus and SPEED-Bus DP
and networking each master is similar in project engineering and parameterization to the
SPEED-Bus CP 343
and DP master at the
corresponding CP from Siemens, for each SPEED-Bus CP a
Standard bus corresponding Siemens CP is to be placed and networked.
Here the sequence follows the one at the SPEED-Bus from the right to the
left within a function group (CP respectively DP master).
Use for each Ethernet-CP 343 - SPEED-Bus a Siemens CP 343-1 (343-
1EX11) and for each SPEED-Bus Profibus DP master a Siemens CP 342-
5DA02 V5.0.
Bus extension with Since as many as 32 modules can be addressed by the SPEED7 CPU in
IM 360 and IM 361 one row, but only 8 modules are supported by the Siemens SIMATIC
manager, the IM 360 of the hardware catalog can be used as a virtual bus
extension during project engineering. Here 3 further extension racks can
be virtually connected via the IM 361. Bus extensions are always placed at
slot 3. Place the system expansion and project the remaining CPs.
Standard bus
(Extension 1)
Slot Module
1
2
3 IM361
4 CP342-5
5 343-1EX11
6 343-1EX11
7
8
9
10
11
Project engineering The slot assignment of the SPEED-Bus modules and the parameterization
each SPEED-Bus of the I/O devices happens via a virtual Profibus DP master system. For
module in a virtual this, place as last module a DP master (342-5DA02 V5.0) with master
master system system.
For the employment of the System 300S modules at the SPEED-Bus the
inclusion of the System 300S modules into the hardware catalog via the
GSD-file speedbus.gsd from VIPA is required.
After the installation of the speedbus.gsd you may locate at
Profibus DP / Additional field devices / I/O / VIPA_SPEEDbus
the DP slave system vipa_speedbus.
Now include for the CPU and every module at the SPEED-Bus a slave
system "vipa_speedbus".
Set as Profibus address the slot no. 100 for the CPU and 101...116 for the
modules and place the according CPU respectively module from the
hardware catalog of VIPA_speedbus to slot 0 of the slave system.
Note!
Let with the CPs or DP master (also virtual SPEED-Bus master) at options
the attitude "Save configuration data on the CPU" activated!
The following pages show information about parameterizing the CPU and
modules and how to transfer the project into the CPU.
CPU parameterization
Overview Except of the VIPA specific CPU parameters the CPU parameterization
takes place in the parameter dialog of the CPU 318-2DP.
The VIPA specific CPU parameters like the RS485 interface behavior, the
synchronization between CPU and DP master and the behavior of
watchdog interrupt OBs (priority, execution, phase offset) may be
configured in the SPEED-Bus CPU parameter dialog.
Parameterization For the SPEED7-CPUs are configured in the hardware configurator from
via Siemens Siemens as Siemens CPU 318-2DP you may adjust the parameters for the
SPEED7 CPUs at the hardware configuration at "Properties" of the CPU
CPU 318-2DP
318-2DP.
Via a double-click on the CPU 318-2 DP the parameter window of the CPU
can be achieved. Using the registers you get access to all parameters of
the CPU.
Supported The CPU does not evaluate all parameters that can be set at the hardware
parameters configuration. The following parameters are supported at this time:
Object properties
Function RS485 Per default, every CPU 31xS uses the RS485 interface for the Profibus DP
master.
Using this parameter the RS485 interface may be switched to PtP
communication (point to point) respectively the synchronisation between
DP master system and CPU may be set:
Deactivated Deactivates the RS485 interface
PtP With this operating mode the Profibus DP master
is deactivated and the RS485 interface acts as an
interface for serial point to point communication.
Here data may be exchanged between two
stations by means of protocols.
More about this may be found at chapter
"Deployment RS485 for PtP communication" in
this manual.
Profibus-DP async Profibus DP master operation asynchronous to
CPU cycle
Is there a Profibus DP integrated to your CPU
31xS, the RS485 interface is preset to Profibus-
DP async. Here CPU cycle and cycles of every
SPEED-Bus DP master run independently.
Profibus-DP syncIn CPU is waiting for DP master input data
Profbus-DP syncOut DP master system is waiting for CPU output
data.
Profibus-DP syncInOut CPU and DP master system are waiting on each
other and form thereby a cycle.
Default: Profibus-DP async
Synchronization Normally the cycle of CPU and DP master run independently. The cycle
between master time of the CPU is the time needed for one OB1 cycle and for reading
system and CPU respectively writing the inputs respectively outputs. The cycle time of a DP
Master depends among others on the number of connected slaves and the
baud rate, thus every plugged DP master has its own cycle time.
Due to the asynchronism of CPU and DP master the whole system gets
relatively high response times.
The synchronization behavior between every SPEED-Bus Profibus DP
master and the SPEED7 CPU can be configured by means of a hardware
configuration as shown above.
The different modes for the synchronization are in the following described.
SPEED-Bus
Cycle Cycle ... ...
DP master system:
whole cycle
Profibus-DP In this operating mode the cycle time of the SPEED-Bus DP master system
SyncOut depends on the CPU cycle time. After CPU start-up the DP master gets
synchronized.
As soon as their cycle is passed they wait for the next synchronization
impulse with output data of the CPU. So the response time of your system
can be improved because output data were directly transmitted to the DP
master system. If necessary the time of the Watchdog of the bus para-
meters should be increased at this mode.
RUN
Profibus-DP In the operating mode Profibus-DP SyncIn the CPU cycle is synchronized
SyncIn to the cycle of the SPEED-Bus Profibus DP master system.
Here the CPU cycle depends on the speed bus DP master with the longest
cycle time. If the CPU gets into RUN it is synchronized with all speed bus
DP master. As soon as the CPU cycle is passed it waits for the next
synchronization impulse with input data of the DP master system.
If necessary the Scan Cycle Monitoring Time of the CPU should be in-
creased.
RUN
Number Here the number of flag bytes may be set. With 0 the value Retentive
remanence flag memory > Number of memory bytes starting with MB0 set at the
parameters of the Siemens CPU 318-2DP is used. Otherwise the adjusted
value (1 ... 8192) is used.
Default: 0
Phase offset and The CPU offers additional cyclic interrupts which interrupt the cyclic
execution of OB33 processing in certain distances. Point of start of the time interval is the
and OB34 change of operating mode from STOP to RUN.
To avoid that the cyclic interrupts of different cyclic interrupt OBs receive a
start request at the same time and so a time out may occur, there is the
possibility to set a phase offset respectively a time of execution.
The phase offset (0 ... 60000ms) serves for distribution processing times
for cyclic interrupts across the cycle.
The time intervals, in which the cyclic interrupt OB should be processed
may be entered with execution (1 ... 60000ms).
Default: Phase offset: 0
Execution: OB33: 500ms
OB34: 200ms
Priority of OB28, The priority fixes the order of interrupts of the corresponding interrupt OB.
OB29, OB33 and Here the following priorities are supported:
OB34 0 (Interrupt-OB ist deactivated), 2,3,4,9,12,16,17, 24
Default: 24
Parameterization of modules
Approach By using the SIMATIC Manager from Siemens you may set parameters for
configurable System 300 modules at any time.
For this, double-click during the project engineering at the slot overview on
the module you want to parameterize In the appearing dialog window you
may set the wanted parameters.
Parameterization By using the SFCs 55, 56 and 57 you may alter and transfer parameters
during runtime for wanted modules during runtime.
For this you have to store the module specific parameters in so called
"record sets".
More detailed information about the structure of the record sets is to find in
the according module description.
Project transfer
Overview There are the following possibilities for project transfer into the CPU:
• Transfer via MPI respectively Profibus
• Transfer via MMC
• Transfer via integrated Ethernet PG/OP channel (Initialization necessary)
Transfer via MPI For the SPEED7-CPUs provide a MPI respectively Profibus jack you have
respectively the following transfer options:
Profibus • Transfer via MPI Programming cable (MPI/Profibus Communication)
• Only MP2I jack: Transfer with VIPA Green Cable as serial communi-
2
cation via MP I - not Profibus
Transfer with MPI The MPI programming cables are available at VIPA in different variants.
Programming The employment of the cables is identical. The cables provide a bus
2
cable via MPI resp. enabled RS485 plug for the MP I jack of the CPU and a RS232 res. USB
Profibus plug for the PC.
Due to the RS485 connection you may plug the MPI programming cables
directly to a already plugged MPI plug on the MPI jack. Every bus
participant identifies itself at the bus with an unique MPI address, in the
course of which the address 0 is reserved for programming devices. The
structure of a MPI net is in the principal identical with the structure of a
1.5MBaud Profibus net. I.e. the same rules are valid and you use the same
components for the build-up. The single participants are connected with
each other via bus interface plugs and Profibus cables. Your CPU 31xS
supports transfer rates of up to 1.5MBaud. Per default the MPI net runs
with 187.5kBaud. VIPA CPUs are delivered with MPI address 2.
Terminating resistor A cable has to be terminated with its surge impedance. For this you switch
on the terminating resistor at the first and the last participant of a network
or a segment.
Please make sure that the participants with the activated terminating
resistors are always provided with voltage during start-up and operation.
STEP7
from Siemens
Approach transfer Transfer via Profibus is only available by DP master, if projected as master
via Profibus and assigned with a Profibus address before. A maximum of 31 PG/OP
connections is supported by Profibus. The transfer via MPI takes place with
the following proceeding:
• Connect your PC to the Profibus master jack of your CPU via a MPI
programming cable.
• Load your project in the Siemens SIMATIC Manager.
• Choose in the menu Options > Set PG/PC interface
• Select in the according list the "PC Adapter (Profibus)"; if appropriate
you have to add it first, then click on [Properties].
• Set in the register Profibus the transfer parameters of your Profibus net
and type a valid Profibus address. The Profibus address must be
assigned to the DP master by a project before.
• Switch to the register Local connection
• Set the COM port of the PCs and the transfer rate 38400Baud for the
MPI programming cable from VIPA.
• Via PLC > Load to module you may transfer your project via Profibus to
the CPU and save it on a MMC via PLC > Copy RAM to ROM if one is
plugged.
Transfer with The "Green Cable" is a programming and download cable that may
2
Green Cable exclusively be plugged directly to VIPA components with MP I jack. The
(possible only at usage at a "normal" MPI jack is not possible. By plugging the Green Cable
2
2
MP I jack) to a MP I jack you may establish a serial connection between the RS232
2
interface of your PC and the MP I interface of your CPU.
Attention!
Please regard that you may plug the "Green Cable" exclusively directly and
2
only to a MP I interface of VIPA-CPUs!
2
Approach • Connect the RS232 interface of the PC and the MP I interface of the
CPU with the Green Cable.
• Load your project in the SIMATIC Manager from Siemens.
• Choose in the menu Options > Set PG/PC interface
• Select in the according list the "PC Adapter (MPI)"; if appropriate you
have to add it first, then click on [Properties].
• Switch to the register Local connection
• Set the COM port of the PCs and the transfer rate 38400Baud for the
MPI programming cable from VIPA. The settings in the register MPI are
ignored at the usage of the Green Cable.
• Via PLC > Load to module you may transfer your project to the CPU
and save it on a MMC via PLC > Copy RAM to ROM if one is plugged.
STEP7
from Siemens
MPI net
Green Cable
Transfer When the MMC has been installed, the write command stores the content
CPU → MMC of the battery buffered RAM as S7PROG.WLD at the MMC.
The write command is controlled by means of the Siemens hardware
configurator via PLC > Copy RAM to ROM.
During the write process the "MCC"-LED of the CPU is blinking. When the
LED expires the write process is finished.
Process control After a write process on the MMC, an according ID event is written into the
diagnostic buffer of the CPU. To monitor the diagnosis entries, you select
PLC > Module Information in the Siemens SIMATIC Manager. Via the
register "Diagnostic Buffer" you reach the diagnosis window. At a
successful write process the diagnostic buffer contains 0xE200.
When writing on the MMC, the following events may occur:
Event-ID Meaning
0xE100 MMC access error
0xE101 MMC error file system
0xE102 MMC error FAT
0xE200 MMC writing finished
Transfer The transfer of the application program from the MMC into the CPU takes
MMC → CPU always place after an overall reset. The blinking of the LED "MCC" of the
CPU marks the active transfer.
An overall reset of the CPU takes place if the MMC does not contain a valid
application program or if the transfer should fail. The red "STOP"-LED
blinks three times.
Note!
If the size of the user application exceeds the user memory of the CPU, the
content of the MMC is not transferred to the CPU.
Execute a compression before the transfer, for this does not happen
automatically.
Transfer via Ether- For the on-line access to the Ethernet PG/OP channel you have to assign
net PG/OP channel IP address parameters by means of the "initialization".
(initialization After allocation the Ethernet PG/OP canal may be accessed by the IP
necessary) address parameters.
Initialization In the following the steps of initialization are described. More information
may be found at "initialization" of the PG/OP channel.
• Determine the Ethernet (MAC) address of the Ethernet PG/OP channel.
st
This always may be found as 1 address under the front flap of the CPU
on a sticker on the left side.
Ethernet address
1. Ethernet PG/OP
2. CP343 (optional)
Transfer Direct after the assignment the Ethernet PG/OP channel may be reached
by the Siemens SIMATIC manager by means of these IP address
parameters.
The transfer happens in the following approach:
• Open your project in the Siemens SIMATIC manager.
• Set at Siemens SIMATIC manager via Options > Set PG/PC Interface
the access path to "TCP/IP -> Network card .... Protocol RFC 1006".
• Click to PLC > Download → the dialog "Select target module" is opened.
Select your target module and enter the IP address parameters of the
Ethernet PG/OP channel as address for connection. Provided that no
new hardware configuration is transferred to the CPU, the given
Ethernet-PG/OP channel is permanently stored in the project as transfer
channel.
• With [OK] the transfer is started. System dependent you get a message
that the projected system differs from target system. This message may
be accepted by [OK] → your project is transferred and may be executed
in the CPU after transfer.
Operating modes
Operating mode • During the transition from STOP to RUN a call is issued to the start-up
START-UP organization block OB 100. The length of this OB is not limited. The
processing time for this OB is not monitored. The START-UP OB may
issue calls to other blocks.
• All digital outputs are disabled during the START-UP, i.e. outputs are
inhibited.
• RUN-LED blinks
• STOP-LED off
When the CPU has completed the START-UP OB, it assumes the
operating mode RUN.
Operating mode The CPU 31xS gives you the opportunity to define up to 4 breakpoints for
HOLD program diagnosis. Setting and deletion of breakpoints happens in your
programming environment. As soon as a breakpoint is reached, you may
process your program step by step and in- and outputs can be activated.
Behavior in • The LED RUN blinks and the LED STOP is on.
operating state • The execution of the code is stopped. No level is further executed.
HOLD
• All times are frozen.
• The real-time clock runs on.
• The outputs are closed, but may be released for test purposes.
• Passive CP communication is possible.
Note!
The usage of breakpoints is always possible. Switching to the operating
mode test operation is not necessary.
With more than 3 breakpoints, a single step execution is not possible.
Function The CPUs include security mechanisms like a Watchdog (100ms) and a
security parameterizable cycle time surveillance (parameterizable min. 1ms) that
stop res. execute a RESET at the CPU in case of an error and set it into a
defined STOP state.
The VIPA CPUs are developed function secure and have the following
system properties:
Overall reset
Overview During the overall reset the entire user memory (RAM) is erased. Data
located in the memory card is not affected.
You have 2 options to initiate an overall reset:
• initiate the overall reset by means of the function selector switch
• initiate the overall reset by means of the Siemens SIMATIC Manager
Note!
You should always issue an overall reset to your CPU before loading an
application program into your CPU to ensure that all blocks have been
cleared from the CPU.
Overall reset
• Place the function selector in the position MRES and hold it in this
position for app. 3 seconds. → The STOP-LED changes from blinking to
permanently on.
• Place the function selector in the position STOP and switch it to MRES
and quickly back to STOP within a period of less than 3 seconds.
→ The STOP-LED blinks (overall reset procedure).
• The overall reset has been completed when the STOP-LED is on
permanently. → The STOP-LED is on.
1 2 3 4
3 Sec.
Automatic reload At this point the CPU attempts to reload the parameters and the program
from the memory card. → The MCC-LED blinks.
When the reload has been completed the LED expires. The operating
mode of the CPU will be STOP or RUN, depending on the position of the
function selector.
Overall reset
You may request the overall reset by means of the menu command PLC >
Clean/Reset.
In the dialog window you may place your CPU in STOP mode and start the
overall reset if this has not been done as yet.
The STOP-LED blinks during the overall reset procedure.
When the STOP-LED is on permanently the overall reset procedure has
been completed.
Automatic reload At this point the CPU attempts to reload the parameters and the program
from the memory card. → The MCC-LED blinks.
When the reload has been completed, the LED expires. The operating
mode of the CPU will be STOP or RUN, depending on the position of the
function selector.
Set back to factory The following approach deletes the internal RAM of the CPU completely
setting and sets it back to the delivery state.
Please regard that the MPI address is also set back to default 2!
• Push down the reset lever for app. 30 seconds. The ST-LED blinks.
After a few seconds the LED turns to static light. Count the number of
static light phases because now the LED switches between static light
and blinking.
th
• After the 6 static light you release the reset lever and push it down
again shortly. Now the green RUN-LED is on once. This means that the
RAM is totally deleted.
• Turn the power supply off and on again.
More information may be found at the part "Factory reset" further below.
Firmware update
Overview Starting with firmware version 1.0.0 there is the opportunity to execute a
firmware update for SPEED-Bus modules and CPU via MMC.
For this an accordingly prepared MMC must be in the CPU during the
startup.
So a firmware files can be recognized and assigned with startup, a pkg file
name is reserved for each updatable component an hardware release,
which begins with "px" and differs in a number with six digits.
The pkg file name of every updateable component may be found at a label
right down the front flap of the module.
As soon as with startup a pkg file is on the MMC and the firmware is more
current than in the components, all the pkg file assigned components within
the CPU and at the SPEED-Bus get the new firmware.
Latest Firmware at The latest 2 firmware versions are to be find in the service area at
ftp.vipa.de www.vipa.de and at the ftp server at ftp.vipa.de/support/firmware.
For example the following files are necessary for the firmware update of
the CPU 317-4NE11 and its components (Profibus, Ethernet CP 343) with
hardware release 1:
• 317-4NE11, Hardware release 1: Px000035_v142.zip
• Profibus DP-Master (integrated/SPEED-Bus): Px000009_V112.zip
• Ethernet-CP 343 (integrated/SPEED-Bus): Px000005_V179.zip
Attention!
When installing a new firmware you have to be extremely careful. Under
certain circumstances you may destroy the CPU, for example if the voltage
supply is interrupted during transfer or if the firmware file is defective.
In this case, please call the VIPA-Hotline!
Please regard that the version of the update firmware has to be different
from the existing firmware otherwise no update is executed.
Display the Every SPEED7-CPU has an integrated website that monitors information
Firmware version of about firmware version of the SPEED7 components. The Ethernet PG/OP
the SPEED7 system channel provides the access to this web site.
via Web Site
To activate the PG/OP channel you have to enter according IP parameters.
This can be made in Siemens SIMATIC manager either by a hardware
configuration, loaded by MMC respectively MPI or via Ethernet by means of
the MAC address with PLC > Assign Ethernet Address.
After that you may access the PG/OP channel with a web browser via the
IP address of the project engineering. More detailed information is to find in
the manual of your SPEED7 CPU, chapter "Deployment CPU31xS" at
"Access to Ethernet PG/OP channel and website".
Preconditions for ftp For the display of ftp sites in your web browser you may have to execute
access the following adjustments:
Internet Explorer
ftp access only with version 5.5 or higher
Options > Internet options, Register "Advanced" in the area "Browsing":
- activate: "Enable folder view for ftp sites"
- activate: "Use passive ftp ..."
Netscape
ftp- access only with version 6.0 or higher
No further adjustments are required
If you still have problems with the ftp access, please ask your system
operator.
Attention!
With a firmware update an overall reset is automatically executed. If your
program is only available in the load memory of the CPU it is deleted! Save
your program before executing a firmware update! After the firmware
update you should execute a "Set back to factory settings" (see following
page).
Transfer firmware 1. Get the RUN-STOP lever of your CPU in position STOP. Turn off the
from MMC into voltage supply. Plug the MMC with the firmware files into the CPU.
CPU Please take care of the correct plug-in direction of the MMC. Turn on
the voltage supply.
2. After a short boot-up time, the alternate blinking of the LEDs SF and
FRCE shows that at least a more current firmware file was found on
the MMC.
3. You start the transfer of the firmware as soon as you tip the
RUN/STOP lever downwards to MRES within 10s.
4. During the update process, the LEDs SF and FRCE are alternately
blinking and MMC LED is on. This may last several minutes.
5. The update is successful finished when the LEDs PWR, STOP, SF,
FRCE and MCC are on. If they are blinking fast, an error occurred.
6. Turn Power OFF and ON. Now it is checked by the CPU, whether
further current firmware versions are available at the MMC. If so, again
the LEDs SF and FRCE flash after a short start-up period. Continue
with point 3.
If the LEDs do not flash, the firmware update is ready.
Now a factory reset should be executed (see next page). After that the
CPU is ready for duty.
1 2 3 4 5 6
Factory reset
Proceeding With the following proceeding the internal RAM of the CPU is completely
deleted and the CPU is reset to delivery state. Please note that here also
the IP address of the Ethernet PG/OP channel is set to 0.0.0.0 and the MPI
address is reset to the address 2!
A factory reset may also be executed by the MMC-Cmd FACTORY_
RESET. More information may be found at "MMC-Cmd - Auto commands".
1 2 3 4 5
CPU in Request factory reset Start factory reset Factory reset Error: Only
STOP executed overall reset
executed
PLC PLC PLC PLC PLC
PWR PWR PWR PWR PWR
RUN RUN RUN RUN RUN
STOP STOP STOP STOP STOP
SF
Tip RUN
SF
6x SF
RUN Tip RUN
SF SF
FRCE FRCE FRCE FRCE FRCE
STOP STOP STOP
MCC MCC MCC MCC MCC Power
MRES MRES MRES OFF/ON
30 Sec. 1 Sec.
Note!
After the firmware update you always should execute a Factory reset.
Overview Starting with the CPU firmware version 3.0.0 you have the option to extend
the work memory of your CPU.
For this, a MCC memory extension card is available from VIPA. The MCC
is a specially prepared MMC (Multimedia Card). By plugging the MCC into
the MCC slot and then an overall reset the according memory expansion is
released. There may only one memory expansion be activated at the time.
On the MCC there is the file memory.key. This file may not be altered or
deleted. You may use the MCC also as "normal" MMC for storing your
project.
Approach To extend the memory, plug the MCC into the card slot at the CPU labeled
with "MCC" and execute an overall reset.
MMC
memory is extended for the MCC memory
configuration (diagnostic entry 0xE400)
Attention!
Please regard that the MCC must remain plugged when you’ve executed
the memory expansion at the CPU. Otherwise the CPU switches to STOP
after 48h. The MCC can not be exchanged with a MCC of the same
memory configuration.
Behavior When the MCC memory configuration has been taken over you may find
the diagnosis entry 0xE400 in the diagnostic buffer of the CPU.
After pulling the MCC the entry 0xE401 appears in the diagnostic buffer,
the SF-LED is on and after 48h the CPU switches to STOP. A reboot is
only possible after plugging-in the MCC again or after an overall reset.
After re-plugging the MCC, the SF-LED extinguishes and 0xE400 is
entered into the diagnostic buffer.
You may reset the memory configuration of your CPU to the initial status at
any time by executing an overall reset without MCC.
Overview Besides the "standard" Know-how protection the SPEED7-CPUs from VIPA
provide an "extended" know-how protection that serves a secure block
rd
protection for accesses of 3 persons.
Standard protection The standard protection from Siemens transfers also protected blocks to
the PG but their content is not displayed. But with according manipulation
the Know-how protection is not guaranteed.
Extended protection The "extended" know-how protection developed by VIPA offers the
opportunity to store blocks permanently in the CPU.
At the "extended" protection you transfer the protected blocks into a WLD-
file named protect.wld. By plugging the MMC and following overall reset,
the blocks in the protect.wld are permanently stored in the CPU.
You may protect OBs, FBs and FCs.
When back-reading the protected blocks into the PG, exclusively the block
header are loaded. The source remains in the CPU and is thus protected
rd
for accesses of 3 persons.
PC CPU OVERALL_RESET
Tip
Blocks RN
ST
3Sec.
MR
MMC
protect blocks Create a new wld-file in your project engineering tool with File > Memory
with protect.wld Card file > New and rename it to "protect.wld".
Transfer the according blocks into the file by dragging them with the mouse
from the project to the file window of protect.wld.
Transfer Transfer the file protect.wld to a MMC storage module, plug the MMC into
protect.wld to CPU the CPU and execute an overall reset with the following approach:
with overall reset
1 2 3 4
3 Sec.
The overall reset stores the blocks in protect.wld permanently in the CPU
protected from accesses of 3rd persons.
Change respectively Protected blocks in the RAM of the CPU may be substituted at any time by
delete protected blocks with the same name. This change remains up to next overall reset.
blocks Protected blocks may permanently be overwritten only if these are deleted
at the protect.wld before.
By transferring an empty protect.wld from the MMC you may delete all
protected blocks in the CPU.
Usage of Due to the fact that reading of a "protected" block from the CPU monitors
protected blocks no symbol labels it is convenient to provide the "block covers" for the end
user.
For this, create a project out of all protected blocks. Delete all networks in
the blocks so that these only contain the variable definitions in the
according symbolism.
Overview Since firmware version 3.0.8 a command file at a MMC may be started
automatically when the MMC is stuck and the CPU is in STOP. As soon as
the MMC is stuck the command file is once executed at CPU STOP up to
the next Power ON.
The command file is a text file which consists of a command sequence to
be stored as vipa_cmd.mmc in the root directory of the MMC.
The file has to be started by CMD_START as 1st command, followed by
the desired commands (no other text) und must be finished by CMD_END
as last command.
Text after the last command CMD_END e.g. comments is permissible,
because this is ignored. As soon as the command file is recognized and
executed each action is stored at the MMC in the log file logfile.txt. In
addition for each executed command a diagnostics entry may be found in
the diagnostics buffer.
Commands In the following there is an overview of the commands. Please regard the
command sequence is to be started with CMD_START and ended with
CMD_END.
Example 1
Example 2
Note!
The parameters IP address, subnet mask and gateway may be received
from the system administrator.
Enter the IP address if there is no gateway used.
Entries in the You may read the diagnostic buffer of the CPU via the Siemens SIMATIC
diagnostic buffer Manager. Besides of the standard entries in the diagnostic buffer, the VIPA
CPUs support some additional specific entries in form of event-IDs.
The current content of the diagnostics buffer is stored on MMC by means
of the MMC-Cmd DIAGBUF. More information may be found at "MMC-Cmd
- Auto commands".
Monitoring the To monitor the diagnostic entries you choose the option PLC > Module
diagnostic entries Information in the Siemens SIMATIC Manager. Via the register "Diagnostic
Buffer" you reach the diagnostic window:
The diagnosis is independent from the operating mode of the CPU. You
may store a max. of 100 diagnostic entries in the CPU.
The following page shows an overview of the VIPA specific Event-IDs.
Overview of the
Event-IDs
Event-ID Description
0xE003 Error at access to I/O devices
Zinfo1: I/O address
Zinfo2: Slot
0xE004 Multiple parameterization of a I/O address
Zinfo1: I/O address
Zinfo2: Slot
0xE005 Internal error – Please contact the VIPA-Hotline!
0xE006 Internal error – Please contact the VIPA-Hotline!
0xE007 Configured in-/output bytes do not fit into I/O area
0xE008 Internal error – Please contact the VIPA-Hotline!
0xE009 Error at access to standard back plane bus
0xE010 Not defined module group at backplane bus recognized
Zinfo2: Slot
Zinfo3: Type ID
0xE011 Master project engineering at Slave-CPU not possible or wrong slave configuration
0xE012 Error at parameterization
0xE013 Error at shift register access to VBUS digital modules
0xE014 Error at Check_Sys
0xE015 Error at access to the master
Zinfo2: Slot of the master (32=page frame master)
0xE016 Maximum block size at master transfer exceeded
Zinfo1: I/O address
Zinfo2: Slot
0xE017 Error at access to integrated slave
0xE018 Error at mapping of the master I/O devices
0xE019 Error at standard back plane bus system recognition
0xE01A Error at recognition of the operating mode (8 / 9 Bit)
... continue
Event-ID Description
0xE400 Memory expansion MCC has been plugged
0xE401 Memory expansion MCC has been removed
... continue
Event-ID Description
0xEA11 SBUS: Output address outside output area
Zinfo1: I/O address
Zinfo2: Slot
Zinfo3: Data width
0xEA12 SBUS: Error at writing record set
Zinfo1: Slot
Zinfo2: Record set number
Zinfo3: Record set length
0xEA14 SBUS: Multiple parameterization of a I/O address (Diagnostic address)
Zinfo1: I/O address
Zinfo2: Slot
Zinfo3: Data width
0xEA15 Internal error - Please contact the VIPA-Hotline!
0xEA18 SBUS: Error at mapping of the master I/O devices
Zinfo2: Master slot
0xEA19 Internal error - Please contact the VIPA-Hotline!
Overview For troubleshooting purposes and to display the status of certain variables
you can access certain test functions via the menu item Debug of the
Siemens SIMATIC Manager.
The status of the operands and the VKE can be displayed by means of the
test function Debug > Monitor.
You can modify and/or display the status of variables by means of the test
function PLC > Monitor/Modify Variables.
Debug > Monitor This test function displays the current status and the VKE of the different
operands while the program is being executed.
It is also possible to enter corrections to the program.
Note!
When using the test function “Monitor” the PLC must be in RUN mode!
PLC > This test function returns the condition of a selected operand (inputs,
Monitor/Modify outputs, flags, data word, counters or timers) at the end of program-
Variables execution.
This information is obtained from the process image of the selected
operands. During the "processing check" or in operating mode STOP the
periphery is read directly from the inputs. Otherwise only the process
image of the selected operands is displayed.
Control of outputs
It is possible to check the wiring and proper operation of output-modules.
You can set outputs to any desired status with or without a control
program. The process image is not modified but outputs are no longer
inhibited.
Control of variables
The following variables may be modified:
E, A, M, T, Z and D.
The process image of binary and digital operands is modified
independently of the operating mode of the CPU 31xS.
When the operating mode is RUN the program is executed with the
modified process variable. When the program continues they may,
however, be modified again without notification.
Process variables are controlled asynchronously to the execution sequence
of the program.
Outline This chapter contains all information necessary for the employment of the
in-/output periphery of the CPU 314ST. It describes functionality, project
engineering and diagnostic of the analog and digital part.
Overview
General At the CPU 314ST the analog and digital in-/output channels are together
in a 2tier casing.
The following components are integrated:
• Analog input: 4xU/Ix12Bit, 1xPt100
• Analog output: 2xU/Ix12Bit
• Digital input: 16(8)xDC24V with parameterizable counter function
• Digital output: 0(8)xDC24V 1A
• Counter: max. 4 counter with the operating mode endless,
single or periodic count
Project The project engineering takes place in the Siemens SIMATIC manager.
engineering For this the import of the GSD speedbus.gsd is required. After the
installation of the GSD you'll find the CPU in the hardware catalog in the
directory VIPA_SPEEDbus with the corresponding order no..
Counter The here used counters are endless counter where the control happens via
the digital input channels. For the counter you may configure interrupts that
may influence the corresponding digital output channel.
SPEED-Bus The SPEED-Bus is a 32Bit parallel bus developed by VIPA with a max.
data rate of 40MByte/s. Via the SPEED-Bus you have the opportunity to
connect up to 16 SPEED-Bus modules to your CPU 31xS.
In opposite to the "standard" backplane bus where the modules are
plugged at the right side of the CPU via single bus connectors, the SPEED-
Bus manages the connection via a special SPEED-Bus rail at the left side
of the CPU.
You can order profile rails at VIPA with integrated SPEED-Bus for 2, 6, 10
or 16 SPEED-Bus periphery modules in different lengths.
Ordering Data
Type Order number Description
314ST/DPM VIPA 314-6CF01 MP2I interface, MMC slot, real time clock, Ethernet Interface for
PG/OP, Profibus DP master, SPEED-Bus,
DI 8...16xDC24V / DO 8...0xDC24V, 0.5A,
AI 4x12Bit / AO 2x12Bit / AI 1xPt100, 4 counter
In-/Output range
Construction The picture shows the CPU 314ST with open flap.
2 22
V
3 23
CH0
A
4 24
5 25
V DC 24V
6 26
CH1 DI
A
7 27
8 28
AI V
9 29
CH2
A
10 30 M
11 24V DC 31 L+
V 32
12
CH3
A
13 33
14 Pt100 34
15 CH4
35
16 DIO DC 24V
36
17
CH5
37
AO 18
CH6 38
19
39
20
M ANA 40 M
Analog part
Overview The analog part consists of 4 input, 1 Pt100 and 2 output channels. 10Byte
input and 4Byte output data of the process image are used by the analog
part.
The channels of the module are galvanically separated from the SPEED-
Bus via DC/DC transducer and opto couplers.
Attention!
Temporarily not used analog inputs with activated channel must be
connected to the concerning ground.
Status indicator
Pin assignment
Note!
To avoid measuring errors, you should connect only one measuring type
per channel.
Access to the By including the GSD speedbus.gsd into your hardware configurator the
Analog part module is available at the hardware catalog.
You can find the CPU 314ST after GSD installation at Additional filed
devices \ I/O \ VIPA_SpeedBus.
The CPU 314ST creates in the peripheral area 48Byte for data input and
24Byte for data output. Here the analog part occupies 10Byte for analog
input and 4Byte for analog output. Without a hardware configuration the
ranges start at address 1024.
In the following table the according areas are marked :
Input range During the measurement, for every channel the measuring data is stored
as word in the data input range.
Address Access Assignment
+0 Byte Digital Input I+0.0 ... I+0.7
+1 Byte Digital Input I+1.0 ... I+1.7
+2 Word reserved
+4 Word Analog Input CH0
+6 Word Analog Input CH1
+8 Word Analog Input CH2
+10 Word Analog Input CH3
+12 Word Analog Input CH4
+14 Word reserved
+16 Double word Counter 0 / Latch 0
+20 Word reserved
+22 Word Status Counter 0
+24 Double word Counter 1 / Latch 1
+28 Word reserved
+30 Word Status Counter 1
+32 Double word Counter 2 / Latch 2
+36 Word reserved
+38 Word Status Counter 2
+40 Double word Counter 3 / Latch 3
+44 Word reserved
+46 Word Status Counter 3
Output range For the output you enter a value as word into the data output range.
Address Access Assignment
+0 Byte reserved
+1 Byte Digital Output Q+1.0 ... Q+1.7
+2 Word reserved
+4 Word Analog Output CH0
+6 Word Analog Output CH1
+8 Word reserved
+10 Word Status Counter 0
+12 Word reserved
+14 Word Status Counter 1
+16 Word reserved
+18 Word Status Counter 2
+20 Word reserved
+22 Word Status Counter 3
Numeric notation The analog values are represented in two’s complement format.
in Siemens Depending on the parameterized transformation speed the lowest value
S7 format bits of the measuring value are irrelevant. With increasing sampling rate,
the resolution decreases.
The following table lists the resolution in dependence of the sampling rate.
Analog value
High-Byte Low-Byte
Bit number 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Resolution sign Measuring value
15 Bit + sign sign Relevant output value (at 3.7 ... 30Hz)
14 Bit + sign sign Relevant output value (at 60Hz) X*
13 Bit + sign sign Relevant output value (at 120Hz) X X
11 Bit + sign sign Relevant output value (at 170Hz) X X X X
9 Bit + sign sign Relevant output value (at 200Hz) X X X X X X
* The lowest value irrelevant bits of the output value are marked with "X".
Algebraic sign bit Bit 15 serves as algebraic sign bit. Here is:
(sign) Bit 15 = "0" → positive value
Bit 15 = "1" → negative value
Behavior at errors As soon as a measuring value exceeds the overdrive res. underdrive
region, the following value is returned:
Measuring value > Overdrive region: 32767 (7FFFh)
Measuring value < Underdrive region: -32768 (8000h)
Analog part With this record set 9Eh you may de-activate the digital res. analog part.
deactivated Please regard that in spite of the de-activation of the digital res. analog part
the process image for both components remains reserved.
The record set has the following structure:
Byte Bit 15 ... 0
0...1 Bit 15 ... 0: Module selection
0000h = Digital- / Analog part activated (default)
0001h = Digital part de-activated
0002h = Analog part de-activated
Digital/Analog In the following all measuring ranges are listed that are supported by the
conversion analog part.
The here listed formulas allow you to transform an evaluated measuring
value (digital value) to a value assigned to the measuring range and vice
versa.
+/- 10V
Voltage Decimal Hex Formulas for the calculation:
-10V -27648 9400 U 10
-5V -13824 CA00 Value = 27648 ⋅ , U = Value ⋅
10 27648
0V 0 0
+5V 13824 3600
U: voltage, Value: decimal value
+10V +27648 6C00
0...10V
Voltage Decimal Hex Formulas for the calculation:
0V 0 0 U 10
5V 13824 3600
Value = 27648 ⋅ , U = Value ⋅
10 27648
10V 27648 6C00 U: voltage, Value: decimal value
0....20mA
Current Decimal Hex Formulas for the calculation:
0mA 0 0 I 20
Value = 27648 ⋅ , I = Value ⋅
+10mA +13824 3600 20 27648
+20mA +27648 6C00 I: current, Value: decimal value
4....20mA
Current Decimal Hex Formulas for the calculation:
+4mA 0 0 I −4, 16
+12mA +13824 3600 Value = 27648 ⋅ I = Value ⋅ +4
+20mA +27648 6C00 16 27648
I: current, Value: decimal value
+/- 20mA
Current Decimal Hex
Formulas for the calculation:
-20mA -27648 9400
I 20
-10mA -13824 CA00 Value = 27648 ⋅ I = Value ⋅
0mA 0 0 20 , 27648
+10mA +13824 3600 I: current, Value: decimal value
+20mA +27648 6C00
Parameter data 18Byte of parameter data are available for the configuration. By using the
record set B4h of the SFC 55 "WR_PARM" you may alter the
parameterization in the module during runtime. The time needed until the
new parameterization is valid can last up to 50ms. During this time, the
measuring value output is 7FFFFh. The following table shows the structure
of the parameter data:
Diagnostic interrupt
The diagnostic interrupt is global released for the digital and analog part.
More is to be find at "Counter - Parameterization". In case of an error like e.g.
wire break, the superordinated system receives record set 0. For a channel
specific diagnostic you may then call record set 1 (see "Diagnostic data").
Function No.
Here you set the function no. of your measuring res. output function for
every channel. Please see the according table above.
Measuring cycle
Here you may set the transducer velocity for every input channel. Please
regard that a higher transducer velocity causes a lower resolution because
of the lower integration time.
The data transfer format remains unchanged. Only the lower Bits (LSBs)
are not longer relevant for the analog value.
Function no. The assignment of a function no. to a certain channel happens during
assignment parameterization. By setting 00h you may de-activate the according
channel.
Input range
(channel 0 ... 3)
No. Function Input range
19h Voltage ±10V ±11.76V
Siemens S7-format 11.76V= End overdrive region (32511)
-10V...10V = nominal range (-27648...27648)
-11.76 = End underdrive region (-32512)
two’s complement
18h Voltage 0...10V 0...11.76V
Siemens S7-format 11.76V = End overdrive region (32511)
0...10V = nominal range (0...27648)
no underdrive region available
24h Current ±20mA ±23.52mA
Siemens S7-format 23.52mA = End overdrive region (32511)
-20...20mA = nominal range (-27648...27648)
-23.52mA = End underdrive region (-32512)
two’s complement
23h Current 4...20mA 1.185...22.81mA
Siemens S7-format 22.81mA = End overdrive region (32511)
4...20mA = nominal range (0...27648)
1.185mA = End underdrive region (-4864)
two’s complement
22h Current 0...20mA 0...23.52mA
Siemens S7-format 23.52mA = End overdrive region (32511)
0...20mA = nominal range (0...27648)
no underdrive region available
00h Channel not active (turned off)
Input range
(channel 4)
No. Function Measuring range / representation
82h Pt100 in 2wire mode -240...1000°C
1000°C = End overdrive region (10000)
-200...+850°C = nominal range (-2000...8500)
-240°C = End underdrive region (-2400)
two’s complement
85h Pt1000 in 2wire mode -240...600°C
600°C = End overdrive region (6000)
-200...+500°C = nominal range (-2000...5000)
-240°C = underdrive region (-2400)
two’s complement
83h NI100 in 2wire mode -105...295°C
295°C = Ende overdrive region (2950)
-50...+250°C = nominal range (-500...2500)
-105°C = Ende underdrive region (-1050)
two’s complement
86h NI1000 in 2wire mode -105...270°C
270°C = Ende overdrive region (2700)
-50...+250°C = nominal range (-500...2500)
-105 = Ende underdrive region (-1050)
two’s complement
46h Resistance measurement 600Ohm 0...705.5Ω
2wire 705.5Ω = End overdrive region (32511)
0…600Ω = nominal range (0...27648)
no underdrive region available
00h Channel not active (turned off)
Output range
(channel 5, channel 6)
Note!
Leaving the defined range, the output is 0V res. 0A!
Record set 0 After error correction automatically a diagnosticgoing occurs if the diagnostic
Diagnosticgoing interrupt release is still active.
Record set 1 The record set 1 contains the 4Byte of record set 0 and additional 12Byte
channel specific module specific diagnostic data.
diagnosticincoming The diagnostic bytes have the following assignment:
(Byte 0 to 14)
Digital part
Outline The digital part consists of 8 input and 8 in-/output channels. Each of these
channels shows its state via a LED. By means of the parameterization you
may assign interrupt properties to every digital input. Additionally you may
parameterize the digital inputs as counter (max. 15kHz, with release 2 max.
100kHz).
The output channels provide a diagnostic function, i.e. as soon as an
output is active, the concerning input is set to "1". At a short circuit at the
load, the input is set to "0" and the error may be recognized by evaluating
the input. The DIO area has to be provided with external DC 24V.
Pin assignment
Status monitor
Pin Assignment Connection LEDs
DI:
21 Supply voltage +DC 24V 21 L+ .0 ... .7 LEDs (green)
+0 I+0.0 to I+0.7
22 Input I+0.0 / Counter 0(A) 22 1L+
Starting at app. 15V
23 Input I+0.1 / Counter 0(B) 23 .0 the signal "1" is
24 Input I+0.2 / Gate0/Latch0/Reset0 24 .1 recognized at the
25 Input I+0.3 / Counter 1(A) 25 .2 input and the acc.
26 Input I+0.4 / Counter 1(B) 26
DC 24V .3 LED is on
DI .0 ... .7
.4
27 Input I+0.5 / Gate1/Latch1/Reset1 27
.5
28 Input I+0.6 / Counter 2(A) 28
.6
29 Input I+0.7 / Counter 2(B) 29
.7
30 Ground DI 30 M DIO:
31 Supply voltage +DC 24V 31 L+ DI 2L+ LED (green)
32 I/Q+1.0 / Gate2/Latch2/Reset2 32 DIO
+1 Supply voltage for
33 I/Q+1.1 / Counter 3(A) 33 2L+ L+ DIO is present
34 I/Q+1.2 / Counter 3(B) 34
.0
35 I/Q+1.3 / Gate3/Latch3/Reset3 .1
35
36 I/Q+1.4 / OUT0/Latch0/Reset0 DIO DC .2 .0 ... .7 LEDs (green)
36 24V .3 I/Q+1.0 to I/Q+1.7 is
37 I/Q+1.5 / OUT1/Latch1/Reset1 .0 ... .7
37 .4 on at active output
38 I/Q+1.6 / OUT2/Latch2/Reset2 .5 res. input
38
39 I/Q+1.7 / OUT3/Latch3/Reset3 .6
40 Ground DIO
39
.7 F LED (red)
40 M
FF F Error at overload or
01 short circuit
Attention!
Please regard that the voltage at an output channel is always ≤ the supply
voltage connected to L+.
Please regard also that due to the parallel connection of in- and output
channel for each group one set output can be supplied via a connected input
signal.
A thus connected output remains active even with shut down supply voltage.
Non-observance may cause damages of the module.
Access to the By including the GSD speedbus.gsd into your hardware configurator the
digital part module is monitored in the hardware catalog.
After the installation of the GSD you will find the CPU 314ST under
Additional Field devices \ I/O \ VIPA_SpeedBus.
The CPU 314ST creates in its peripheral range 48Byte for data input and
24Byte for data output. Out of this, the digital part occupies 34Byte for
digital input and 18Byte for digital output. Without a hardware configuration
the ranges start at address 1024.
In the following table the according areas are marked :
Output range For the output you enter a Word value into the data output range.
Address Access Assignment
+0 Byte reserved
+1 Byte Digital Output Q+1.0 ... Q+1.7
+2 Word reserved
+4 Word Analog Output CH0
+6 Word Analog Output CH1
+8 Word reserved
+10 Word Status Counter 0
+12 Word reserved
+14 Word Status Counter 1
+16 Word reserved
+18 Word Status Counter 2
+20 Word reserved
+22 Word Status Counter 3
Fast introduction The CPU 314ST has 4 parameterizable counters integrated that may be
controlled separately. During the count process the counter signal is
recognized and evaluated. Every counter occupies one double word in the
input range for the counter register and one word in the in- and output
range for the input res. output status.
Preset res. By including the speedbus.gsd you may preset all counter parameters via a
parameterize hardware configuration. Here you may define among other:
counter • Interrupt behavior
• Assignment I/O (Gate, Latch, Reset, OUT)
• Input filter
• Counter operating mode res. behavior
• Start value for load value, end value and comparison value register
You may alter the parameters during runtime by using the SFC 55, 56, 57
and 58, except of the parameters in record set 0. Here you have to send
the wanted parameters to the counter by means of the user application
using the according SFC and sending the data as record set.
Control counter The counter is controlled via the internal gate (I-gate). The I-gate is the
sum of hardware- (HW) and Software-gate (SW), where the HW-gate
evaluation may be deactivated via the parameterization.
HW-gate: Input at Gatex-input at module
SW-gate: Open (activate): Set once output status Bit 2 in the output range
Close (deactivate): Set output status Bit 10 in the output range
Read counter Depending on the status setting, the counter register contains the recent
counter value (input status Bit 0=0) or the recent Latch value (input status
Bit 0=1).
By setting the output status Bit 8 the recent Latch value is transferred to
the counter register in the input area.
Transfer the recent counter value by setting the output status Bit 0.
Counter status Besides of the counter register in the input area you may find a status word
word for every counter in the in- res. output range. You may monitor the status
or influence the counter by setting according bits like e.g. activate the SW
gate.
Input status word The status word in the input range has the following structure:
Bit Label Function
0 COUNT_LTCH 0: Value in input image is counter value
1: Value in input image is latch value
1 CTRL_Count_DO Is set when the digital output is released
2 STS_SW-GATE Status software gate (set when SW gate active)
3 reserved reserved
4 STS_STRT Status hardware gate (set when HW gate active)
5 STS_GATE Status internal gate (set when internal gate active)
6 STS_DO Status of the digital output of a counter (DO)
7 STS_C_DN Status counter direction backwards
8 STS_C_UP Status counter direction forward
9 STS_CMP* Status Comparison (Compare) is set when counter
value = comparison value. If comparison is
parameterized never, the bit is never set
10 STS_END* Status set when end value is reached
11 STS_OFLW* Status overflow
12 STS_UFLW* Status underrun
13 STS_ZP* Status zero run
14 STS_LTCH Status of the Latch input of a counter
15 NEW_LTCH Is set if value in the Latch register has changed
* The bits remains set until reset with RES (Bit 6 status word output image).
Output status word After setting a bit in the output status word this is immediately set back.
Please regard that setting and resetting of a function at the output status
word takes place with different bits:
Bit Label Function
0 Get _Count_Val Transfer counter value to process image
1 Set_Count_DO Release the digital output for counter
(output only available via counter)
2 Set_SW-Gate Set software gate (not allowed at OB 100)
3 reserved -
4 reserved -
5 Set_Count_Val Set counter temporarily to a value (the counter value
for Zx has to be transferred before via record set
(9A+x)h
6 Reset_STS Reset bits STS_CMP, STS_END, STS_OFLW,
STS_UFLW and STS_ZP
7 reserved -
8 Get_Latch_Val Transfer Latch value to process image
9 Reset_Count_DO Lock digital output for counter
(output available only via process image)
10 Reset_SW_Gate Reset software gate
12 reserved -
... ... ...
15 reserved -
Counter inputs For not all inputs are available at the same time, you may set the input
(Connections) assignment for every counter via the parameterization. For each counter
the following inputs are available:
Counterx (A)
Pulse input for count signal res. track A of an encoder. Here you may
connect encoder with 1-, 2- or 4-tier evaluation.
Counterx (B)
Direction signal res. track B of the encoder. Via the parameterization you
may invert the direction signal.
The following inputs may be assigned to a pin at the module via
parameterization:
Gatex
This input allows you to open the HW gate with a high peek and thus start
a count process.
Latchx
With a positive edge at Latchx the recent counter value is stored in a
memory that you may read at need.
Resetx
As long as Resetx is applied with a positive level the counter is still reset to
the load value.
Counter outputs Every counter has an assigned output channel. The following behavior for
the output channel can be set via parameterization:
• No comparison: output is not headed for
• Count value ≥ comparison value: output is set
• Count value ≤ comparison value: output is set
• Count value = comparison value: output is set
Maximum count At this time the maximum frequency for the release version 1 independent
frequency from the number of activated counters is 15kHz. Starting with release
version 2 a max. of 100kHz is possible.
Counter - Parameterization
Except of the parameter in record set 0, you may transfer the other
parameters during runtime by using the SFC 55, 56, 57 and 58 to the
digital part. For this you have to transfer the wanted parameters to the
counter by using the according SFC in the user application.
Record set 0 Via the record set 0 you may preset a counter mode for every counter as
Counter mode double word. Please regard that the record set 0 may not be transferred
during runtime. Record set 0 has the following structure:
Byte Description
0 ... 3 Counter mode C0
4 ... 7 Counter mode C1
8 ... 11 Counter mode C2
12 ... 15 Counter mode C3
Counter mode The double word for the counter mode has the following structure:
Byte Bit 7 ... 0
0 Bit 2 ... 0: Signal evaluation
000b = Counter de-activated
At de-activated counter the further parameter settings for
this counter are ignored and the according I/O channel is
set as "normal" output if this should be used as output.
001b = Encoder 1-tier (at counterx (Ax) and counterx (Bx))
010b = Encoder 2-tier (at counterx (Ax) and counterx (Bx))
011b = Encoder 4-tier (at counterx (Ax) and counterx (Bx))
100b = Pulse/direction (pulse at counterx (Ax) and direction at
counterx (Bx))
Bit 6 ... 3: Cx input (Function of the counter input as gate,
latch or reset)
0000b = de-activated (counter starts at set SW gate)
0001b = Gatex
The input of counterx serves as gate. High peek at gate
activates the HW gate. The counter may only start when
HW and SW gate are set.
0010b = Monoflop*
0100b = Latchx (Positive edge at input saves counter value)
1000b = Resetx (Positive level at input sets counter back)
Bit 7: Gate function (internal gate)
0 = abort (count process starts again at load value)
1 = interrupt (count process continues with counter value)
1 Bit 2 ... 0: Output set (OUTx of counterx is set when condition is met)
000b = never
001b = counter value >= comparison value
010b = counter value <= comparison value
100b = counter value = comparison value
Bit 3: Count direction
0 = count direction inverted: OFF (count direction at Bx not inverted)
1 = count direction inverted: ON (count direction at Bx inverted)
Bit 7 ... 4: reserved
* not supported at this time continued ...
... continue
Byte Bit 7 ... 0
2 Bit 5 ... 0: Counter function
000000b = Count endless
000001b = Once: forward
000010b = Once: backwards
000100b = Once: no main direction
001000b = Periodic: forward
010000b = Periodic: backwards
100000b = Periodic: no main direction
More details at "Counter - Functions" below.
Bit 7 ... 6: Cx In-/Output (Function of the counter I/O as OUT,
Latch or Reset)
00b = O: OUTx (at comparison function)
01b = I: Latchx (rising edge saves counter value)
10b = I: Resetx (positive level resets counter)
3 Bit 5 ... 0: Interrupt behavior
Bit 0: Proc. interrupt HW gate open
Bit 1: Proc. interrupt HW gate closed
Bit 2: Proc. interrupt overflow
Bit 3: Proc. interrupt underrun
Bit 4: Proc. interrupt comparison value
Bit 5: Proc. interrupt end value
By setting the Bits you may activate the wanted process interrupts.
Bit 7 ... 6: reserved
Record set 7Fh This record set activates res. de-activates the diagnostic function.
Diagnostic interrupt A diagnostic interrupt occurs when during a process interrupt execution
another process interrupt is initialized for the same event.
The record set has the following structure:
Byte Bit 15 ... 0
0...1 Bit 15 ... 0: Diagnostic interrupt
0000h = de-activated
0001h = activated
2...3 Bit 15 ... 0: reserved
Record set 80h Via this record set you may activate a process interrupt for I+0.0 ... I+1.7
Edge selection and define for which edge type of the input signal a process interrupt is
thrown.
The record set has the following structure:
Byte Bit 7 ... 0
0 Bit 1 ... 0: Edge selection I+0.0
00b = de-activated
01b = Process interrupt at rising edge
10b = Process interrupt at falling edge
11b = Process interrupt at rising and falling edge
Bit 7 ... 2: reserved
... ...
15 Bit 1 ... 0: Edge selection I+1.7
00b = de-activated
01b = Process interrupt at rising edge
10b = Process interrupt at falling edge
11b = Process interrupt at rising and falling edge
Bit 7 ... 2: reserved
Record set 81h This record set allows you to preset an input filter in steps of 2.56µs steps
Input filter for I+0.0 ... I+1.7. By preceding a filter you define how long an input signal
must be present before it is recognized as "1" signal. With the help of filters
you may e.g. filter signal peaks at a blurred input signal.
The entry happens as a factor of 2.56µs and is within the range 1 ... 16000
i.e. 2.56µs ... 40.96ms.
The record set has the following structure:
Byte Bit 15 ... 0
0 ... 1 Bit 15 ... 0: Input filter I+0.0 in 2.56µs
2 ... 3 Bit 15 ... 0: Input filter I+0.1 in 2.56µs
4 ... 5 Bit 15 ... 0: Input filter I+0.2 in 2.56µs
... ...
30 ... 31 Bit 15 ... 0: Input filter I+1.7 in 2.56µs
Record set 82 ... 99h Each of the following counter parameters has an assigned record set
Counter parameter depending on the counter number. Additionally for every counter the
parameter are summoned in one record set.
The record sets have the same structure for every counter. Please refer to
the following table for the structure and the according record set number
assignment. The record set has the following structure:
Count. 0 Count. 1 Count. 2 Count. 3 Type Function
87h 8Dh 93h 99h
82h 88h 8Eh 94h Double word Comparison value
83h 89h 8Fh 95h Double word Load value
84h 8Ah 90h 96h Double word End value
85h 8Bh 91h 97h Word Hysteresis
86h 8Ch 92h 98h Word Pulse
… Continue
Record set 82 … 99h
Comparison value Via the parameterization you may preset a comparison value that may
influence the counter output res. throw a process interrupt when compared
with the recent counter value. The behavior of the output res. the process
interrupt has to be set via the record set 0.
Load value, You may define a main counting direction for every counter via the
end value parameterization.
If "none" or "endless" is chosen, the complete counting range is available:
Counter limits Valid value range
31
Lower count limit - 2 147 483 648 (-2 )
Upper count limit + 2 147 483 647 (231-1)
Otherwise you may set an upper and a lower limit by setting a load value
as start and an end value.
Hysteresis The hysteresis serves the avoidance of many toggle processes of the
output and the interrupt, if the counter value is in the range of the
comparison value. You may set a range of 0 to 255. The settings 0 and 1
deactivate the hysteresis. The hysteresis influences zero run, comparison,
over- and underflow.
Pulse The pulse duration tells for what time the output is set when the
(Pulse duration) parameterized comparison criterion is reached res. overstepped. The pulse
duration can be set in steps of 2.048ms between 0 and 522.24ms.
If the pulse duration = 0, the output is set active until the comparison
condition is not longer fulfilled.
Note!
More details are under "Counter – Additional functions" below!
Datensatz 9A ... 9Dh A register can be preset using record set (9A+x)h. The current counter
Set counter value value is replaced by the register value by setting bit 5 of the output status
temporary word without any influence to the load value.
Record set 9Eh Using this record set you can de-activate the digital res. analog part. If a
Module selection part is de-activated the corresponding area of the process image is just
reserved.
The record set has the following structure:
Byte Bit 15 ... 0
0...1 Bit 15 ... 0: Module selection
0000h = Digital / analog part activated (default)
0001h = Digital part de-activated
0002h = Analog part de-activated
Counter - Functions
Outline You may count forward and backwards and choose between the following
counter functions:
• Count endless – e.g. distance measuring with incremental encoder
• Count once – e.g. count to a maximum limit
• Count periodic – e.g. count with repeated counter process
In the operating modes "Count once" and "Count periodic" you may define
a counter range as start and end value via the parameterization.
For every counter additional parameterizable functions are available like
gate function, latch function, comparison, hysteresis and process interrupt.
Main counting Via the parameterization you have the opportunity to define a main
direction counting direction for every counter.
If "none" is chosen, the complete counting range is available:
Count In this operating mode, the counter counts from 0 res. from the load value.
Continuously When the counter counts forward and reaches the upper count limit and
another counting pulse in positive direction arrives, it jumps to the lower
count limit and counts from there on.
When the counter counts backwards and reaches the lower count limit and
another counting pulse in negative direction arrives, it jumps to the upper
count limit and counts from there on.
The count limits are set to the maximum count range.
counter value
upper
overflow
counter limit
load value
0
lower
underflow
counter limit
time
gate start gate stop
upper
overflow
counter limit
load value
0
lower
underflow
counter limit
time
gate start gate stop gate start gate stop
automatically automatically
upper
overflow
counter limit
load value
0
lower
underflow
counter limit
time
gate start gate stop gate start gate stop
automatically automatically
load value
0
lower
underflow
counter limit
time
gate start gate stop gate start gate stop
automatically automatically
upper
counter limit
load value
end value
time
gate start gate stop gate start gate stop
automatically automatically
counter value
upper
overflow
counter limit
load value
0 zero-crossing
lower
underflow
counter limit
time
gate start gate stop
nd value overflow
ad value
0
wer
underflow
ounter limit
time
gate start gate stop
counter value
upper
counter limit
load value
end value
time
gate start gate stop
Outline The following additional functions may be set via the parameterization for
every counter:
• Gate function
The gate function serves the start, stop and interrupt of a count function.
• Latch function
A positive edge at the digital input "Latch" stores the recent counter
value in the latch register.
• Comparison
You may set a comparison value that activates res. de-activates a digital
output res. releases a process interrupt depending on the counter value.
• Hysteresis
The setting of a hysteresis avoids for example a high output toggling
when the value of an encoder signal shifts around a comparison value.
Schematic structure The illustration shows how the additional functions influence the counting
behavior. The following pages describe these functions in detail:
Internal gate
Pulse evaluation
R
Load value e
l
e Process
Comparison value Counter value Latch a interrupt
s
e
Comparision
Hysteresis
Output
Gate function The activation res. de-activation of a counter happens via an internal gate
(I-gate). The I-gate consists of a software gate (SW-gate) and a Hardware
gate (HW-gate). The SW-gate is opened (activated) via your user
application by setting the output status bit 2 for the according counter. The
SW-gate is closed (deactivated) by setting the output status bit 10. The
HW-gate is controlled via the concerning "Gate" input. The parame-
terization allows you to de-activate the consideration of the HW-gate so
that the counter activation can take place only via the SW-gate. The
following states influence the I-gate:
SW-gate HW-gate influences I-gate
0 with positive edge 0
1 with positive edge 1
with positive edge 1 1
with positive edge 0 0
with positive edge de-activated 1
load value
time
gate start gate stopp gate start
• At interrupt function, the counter starts counting with the last recent
counter value after gate restart.
counter value
load value
time
gate start gate stopp gate start
Gate control Gate control via SW/HW gate, operating mode "Count once"
"Count once" If the internal gate has been closed automatically it may only be opened
again under the following conditions:
SW gate HW gate Reaction I gate
1 positive edge 1
positive edge positive edge 1
(after positive edge at
HW gate)
Latch function As soon as during a count process a positive edge is recognized at the
"Latch" input of a counter, the recent counter value is stored in the
according latch register.
You may access the latch register via the "input image". For this set Bit 15
of the output status word.
At a new latch value additionally Bit 13 is set in the input status word. By
setting Bit 15 in the output status word you may read the recent latch value
of the according counter and reset the Bit 13 of the input status word.
Comparison You pre-define the behavior of the counter output via the parameterization:
• output never switches
• output switch when counter value ≥ comparison value
• output switch when counter value ≤ comparison value
• output switch at comparison value
Pulse duration
The pulse duration defines how long the output is set.
it may be preset in steps of 2.048ms between 0 and 522.24ms.
The pulse duration starts with the setting of the according digital output.
The inaccuracy of the pulse duration is less than 2.048ms.
There is no past triggering of the pulse duration when the comparison
value has been left and reached again during pulse output.
Hysteresis The hysteresis serves e.g. the avoidance of many toggle processes of the
output and the interrupt, if the counter value is in the range of the
comparison value. You may set a range of 0 to 255. The settings 0 and 1
deactivate the hysteresis. The hysteresis influences the zero run, over- and
underflow.
An activated hysteresis remains active after a change. The new hysteresis
range is taken over at the next reach of the comparison value.
The following pictures illustrate the output behavior for hysteresis 0 and
hysteresis 3 for the according conditions:
Counter value
8
7 Hysteresis 1 3 5 6
4 7
6
Comparison value 5
4 2
3
2
1
0
Output:
Hysteresis = 0
Hysteresis = 3
4 Leave hysteresis range, output remains set for counter value ≥ comparison value
5 Counter value < comparison value and hysteresis active → output is reset
6 Counter value ≥ comparison value → output is not set for hysteresis active
7 Leave hysteresis range, output remains set for counter value ≥ comparison value
Counter value
8
7 Hysteresis 1 3 5 6
4 7
6
Comparison value 5
4 2
3
2
1
0
Output:
Hysteresis = 0
Hysteresis = 3
Counter value
8
7 Hysteresis 1 3 5 6
4 7
6
Comparison value 5
4 2
3
2
1
0
Output:
Hysteresis = 0
Hysteresis = 3
1 Counter value = comparison value → pulse of the parameterized duration is put out, the
hysteresis is activated and the counting direction stored
2 Leaving the hysteresis range contrary to the stored counting direction → pulse of the
parameterized duration is put out, the hysteresis is de-activated
3 Counter value = comparison value → pulse of the parameterized duration is put out, the
hysteresis is activated and the counting direction stored
4 Leaving the hysteresis range without changing counting direction → hysteresis is de-activated
5 Counter value = comparison value → pulse of the parameterized duration is put out, the
hysteresis is activated and the counting direction stored
6 Counter value = comparison value and hysteresis active → no pulse
7 Leaving the hysteresis range contrary to the stored counting direction → pulse of the
parameterized duration is put out, the hysteresis is de-activated
With reaching the comparison condition the hysteresis gets active and a
pulse of the parameterized duration is put out. As long as the counter value
is within the hysteresis range, no other pulse is put out. With activating the
hysteresis the counting direction is stored in the CPU. If the counter value
leaves the hysteresis range contrary to the stored counting direction, a
pulse of the parameterized duration is put out. Leaving the hysteresis
range without direction change, no pulse is put out.
Outline The parameterization allows you to define the following trigger for a
process interrupt that may initialize a diagnostic interrupt:
• Status changes at an input
• Status changes at the HW-gate
• Over- res. underflow
• Reaching a comparison value
Process interrupt A process interrupt causes a call of the OB 40. Within the OB 40 you may
find the logical basic address of the module that initialized the process
interrupt by using the Local word 6. More detailed information about the
initializing event is to find in the local double word 8.
Local double word 8 The local double word 8 of the OB 40 has the following structure:
of the OB 40 Local byte Bit 7 ... Bit 0
8 Bit 0: Edge at I+0.0
Bit 1: Edge at I+0.1
Bit 2: Edge at I+0.2
Bit 3: Edge at I+0.3
Bit 4: Edge at I+0.4
Bit 5: Edge at I+0.5
Bit 6: Edge at I+0.6
Bit 7: Edge at I+0.7
9 Bit 0: Edge at I+1.0
Bit 1: Edge at I+1.1
Bit 2: Edge at I+1.2
Bit 3: Edge at I+1.3
Bit 4: Edge at I+1.4
Bit 5: Edge at I+1.5
Bit 6: Edge at I+1.6
Bit 7: Edge at I+1.7
10 Bit 0: Gate counter 0 open (activated)
Bit 1: Gate counter 0 closed
Bit 2: Over-/underflow/end value counter 0
Bit 3: Counter 0 reached comparison value
Bit 4: Gate counter 1 open (activated)
Bit 5: Gate counter 1 closed
Bit 6: Over-/underflow/ end value counter 1
Bit 7: Counter 1 reached comparison value
11 Bit 0: Gate counter 2 open (activated)
Bit 1: Gate counter 2 closed
Bit 2: Over-/underflow/end value counter 2
Bit 3: Counter 2 reached comparison value
Bit 4: Gate counter 3 open (activated)
Bit 5: Gate counter 3 closed
Bit 6: Over-/underflow/end value counter 3
Bit 7: Counter 3 reached comparison value
Diagnostic Via the parameterization (record set 7Fh) you may activate a global
interrupt diagnostic interrupt for the analog and digital part.
A diagnostic interrupt occurs when during a process interrupt execution in
OB 40 another process interrupt is thrown for the same event. The
initialization of a diagnostic interrupt interrupts the recent process interrupt
execution in OB 40 and branches in OB 82 to diagnostic interrupt
processingincoming. If during the diagnostic interrupt processing other events
are occurring at other channels that may also cause a process res.
diagnostic interrupt, these are interim stored.
After the end of the diagnostic interrupt processing at first all interim stored
diagnostic interrupts are processed in the sequence of their occurrence
and then all process interrupts.
If a channel where currently a diagnostic interruptincoming is processed res.
interim stored initializes further process interrupts, these get lost. When a
process interrupt for which a diagnostic interruptincoming has been released is
ready, the diagnostic interrupt processing is called again as diagnostic
interruptgoing.
All events of a channel between diagnostic interruptincoming and diagnostic
interruptgoing are not stored and get lost. Within this time window
st
(1 diagnostic interruptincoming until last diagnostic interruptgoing) the SF-LED
of the CPU is on. Additionally for every diagnostic interruptincoming/going an
entry in the diagnostic buffer of the CPU occurs.
Process interrupt:
8 lost lost 3 6 6
Fast memory buffer (FIFO): 3 3 6 14 14
3
lost
8 8 3 3 6
Fast memory buffer Proz (FIFO): 8 3 3 6 6 14 14
6 14 14
8
Fast memory buffer Diag (FIFO): 8 3 3 8 3
Diagnostic interrupt Every OB 82 call causes an entry in the diagnostic buffer of the CPU
processing containing error cause and module address.
By using the SFC 59 you may read the diagnostic bytes.
At de-activated diagnostic interrupt you have access to the last recent
diagnostic event.
If you've activated the diagnostic function in your hardware configuration,
the contents of record set 0 are already in the local double word 8 when
calling the OB 82. The SFC 59 allows you to also read the record set 1 that
contains additional information.
After leaving the OB 82 an clear assignment of the data to the last
diagnostic interrupt is not longer possible.
The record sets of the diagnostic range have the following structure:
Record set 0 After the removing error a diagnostic messagegoing takes place if the
Diagnosticgoing diagnostic interrupt release is still active.
Record set 0 (Byte 0 to 3):
Byte Bit 7 ... 0
0 Bit 0: set at module failure
Bit 1: 0 (fix)
Bit 2: set at external error
Bit 3: set at channel error
Bit 4: set when external auxiliary supply is missing
Bit 7 ... 5: 0 (fix)
1 Bit 3 ... 0: Module class
0101b: Analog module
1111b: Digital
Bit 4: Channel information present
Bit 7 ... 5: 0 (fix)
2 00h (fix)
3 00h (fix)
Diagnostic The record set 1 contains the 4Byte of the record set 0 and additionally
Record set 1 12Byte module specific diagnostic data.
(Byte 0 ... 15) The diagnostic bytes have the following assignment:
Outline Content of this chapter is the deployment of the CPU 31xS with Profibus.
After a short overview the project engineering and parameterization of a
CPU 31xS with integrated Profibus-Part from VIPA is shown.
Further you get information about usage as DP master and DP slave of the
Profibus part.
The chapter is ended with notes to commissioning and start-up.
Overview
CPU with The Profibus DP master is to configure via the hardware configurator from
DP master Siemens. Therefore you have to choose the Siemens-CPU 318-2AJ00 in
the hardware configurator from Siemens.
The transmission of your project engineering into the CPU takes place by
means of MPI, MMC or Ethernet PG/OP channel. This is internally passing
on your project data to the Profibus master part.
During the start-up the DP master automatically includes his data areas
into the address range of the CPU. A project engineering in the CPU is not
required.
As external storage medium the Profibus DP master uses the MMC
(Multi Media Card) together with the CPU.
Deployment of the Via the Profibus DP master up to 125 Profibus DP slaves may be coupled
DP-Master with to the CPU. The DP master communicates with the DP slaves and links up
CPU its data areas with the address area of the CPU. There may be created
maximal 1024Byte Input and 1024Byte Output data.
At every POWER ON res. overall reset the CPU fetches the I/O mapping
data from the master. At DP slave failure, the ER-LED is on and the OB 86
is requested. If this is not available, the CPU switches to STOP and BASP
is set. As soon as the BASP signal comes from the CPU, the DP master is
setting the outputs of the connected periphery to zero. The DP master
remains in the operating mode RUN independent from the CPU.
Profibus address Please regard that the Profibus address 1 is reserved for the system. The
1 is reserved address 1 should not be used!
DP slave operation For the deployment in an super-ordinated master system you first have to
project your slave system as CPU 318-2DP (6ES7 318-2AJ00-0AB0/V3.0)
in Slave operation with configured in-/output areas. Afterwards you
configure your master system. Assign your slave system to your master
system by dragging the "CPU 31x" from the hardware catalog at
Configured stations onto the master system, choose your slave system and
connect it.
Outline For the project engineering of the Profibus DP master you have to use the
hardware manager from Siemens. Your Profibus projects are transferred
via MPI to the CPU by means of the "PLC" functions. The CPU passes the
data on to the Profibus DP master.
Note!
For the project engineering of the CPU and the Profibus DP master a
thorough knowledge of the Siemens SIMATIC manager is required!
Install Siemens The hardware configurator is a part of the Siemens SIMATIC Manager. It
Hardware serves the project engineering. The modules that may be configured here,
configurator are listed in the hardware catalog.
For the deployment of the Profibus DP slaves of the Systems 100V, 200V
and 300V from VIPA you have to include the modules into the hardware
catalog by means of the GSD file from VIPA.
Note!
If you deploy an IM153 from Siemens under a VIPA CPU 31xSx/DPM,
please use the "compatible" DP slave modules.
These are listed in the hardware catalog under
PROFIBUS-DP/Additional Field Devices/
Compatible Profibus-DP-Slaves.
Slave operation You may deploy your Profibus part from your SPEED7-CPU as DP slave.
possible The approach is described on the following page.
Fast introduction The deployment of the Profibus section as "intelligent" DP slave happens
exclusively at master systems that may be configured in the Siemens
SIMATIC manager. The following steps are required:
• Start the Siemens SIMATIC manager and configure a CPU 318-2DP
with the operating mode DP slave.
• Connect to Profibus and configure the in-/output area for the slave
section.
• Save and compile your project.
• Configure another station as CPU 318-2DP with operating mode DP
master.
• Connect to Profibus and configure the in-/output ranges for the master
section
• Save and compile your project.
In the following these steps are more detailed.
Slave section
Project • Insert another SIMATIC 300 station and name it as "...DP master".
engineering of the • Open the hardware configurator and insert a profile rail from the
master section hardware catalog.
• Place the following Siemens CPU at slot 2:
CPU 318-2DP (6ES7 318-2AJ00-0AB0 V3.0)
• Add your modules according to the real hardware assembly.
• Connect the CPU to Profibus, set a Profibus address >1 (preferably 2)
and switch the Profibus section via operating mode to "master
operation"..
• Connect your slave system to the master system by dragging the
"CPU 31x" from the hardware catalog at configured stations onto the
master system and select your slave system.
• Open the Configuration at Object properties of your slave system.
• Via double click to the according configuration line you assign the
according input address area on the master CPU to the slave output
data and the output address area to the slave input data.
• Save, compile and transfer your project. More detailed information about
SPEED-Bus project engineering and project transfer may be found at
chapter "Deployment CPU31xS".
Master section
Standard bus
Slot Module
1
2 CPU 318-2
DP master system
X2 DP
X1 MPI/DP
3 2
I/O devices S7-300
1 ... Hardware catalog: CPU 31x from
configured stations
Object properties
Operating mode: DP master
3
Connect: Profibus Object properties
Profibus address: > 1
Configuration:
Input area slave CPU = Output area master-CPU
Output area slave CPU = Input area Master-CPU
Transfer medium As transfer medium Profibus uses an isolated twisted-pair cable based
upon the RS485 interface.
The RS485 interface is working with voltage differences. Though it is less
irritable from influences than a voltage or a current interface. You are able
to configure the network as well linear as in a tree structure.
Your VIPA CPU 31xS includes a 9pin slot where you connect the Profibus
coupler into the Profibus network as a slave.
Max. 32 participants per segment are permitted. The segments are
connected via repeaters. The maximum segment length depends on the
transfer rate.
Profibus-DP uses a transfer rate between 9.6kBaud and 12MBaud, the
slaves are following automatically. All participants are communicating with
the same baudrate.
The bus structure under RS485 allows an easy connection res.
disconnection of stations as well as starting the system step by step. Later
expansions don’t have any influence on stations that are already
integrated. The system realizes automatically if one partner had a fail down
or is new in the network.
Bus connection The following picture illustrates the terminating resistors of the respective
start and end station.
6 6
P5V P5V
330 330
220 220
330 330
5 5
M5V M5V
Note!
The Profibus line has to be terminated with its ripple resistor. Please make
sure to terminate the last participants on the bus at both end by activating
the terminating resistor.
"EasyConn" Bus In systems with more than two stations all partners are wired in parallel.
connector For that purpose, the bus cable must be feed-through uninterrupted.
Via the order number VIPA 972-0DP10 you may order the bus connector
"EasyConn". This is a bus connector with switchable terminating resistor
and integrated bus diagnostic.
0° 45° 90°
A A A
B B B C
0° 45° 90°
A 64 61 66
B 34 53 40
C 15,8 15,8 15,8
all in mm
Note!
To connect this EasyConn plug, please use the standard Profibus cable
type A (EN50170). Starting with release 5 you also can use highly flexible
bus cable: Lapp Kabel order no.: 2170222, 2170822, 2170322.
Under the order no. 905-6AA00 VIPA offers the "EasyStrip" de-isolating
tool, that makes the connection of the EasyConn much easier.
11 6
Dimensions in mm
Termination with The "EasyConn" bus connector is provided with a switch that is used to
"EasyConn" activate a terminating resistor.
Attention!
The terminating resistor is only effective, if the connector
is installed at a slave and the slave is connected to a
power supply.
Note!
A complete description of installation and deployment of
the terminating resistors is delivered with the connector.
Please note: The green line must be connected to A, the red line to B!
Start-up on In delivery the CPU is overall reset. The Profibus part is deactivated and its
delivery LEDs are off after Power ON.
Online with bus The DP master can be served with bus parameters by means of a
parameter without hardware configuration. As soon as these are transferred the DP master
slave project goes online with his bus parameter. This is shown by the RUN LED. Now
the DP master can be contacted via Profibus by means of his Profibus
address. In this state the CPU can be accessed via Profibus to get
configuration and DP slave project.
Slave If the master has received valid configuration data, he switches to Data
configuration Exchange with the DP Slaves. This is indicated by the DE-LED.
CPU state controls After Power ON respectively a receipt of a new hardware configuration the
DP master configuration data and bus parameter were transferred to the DP master.
The DP master does not have any operation switch. His state is controlled
by the RUN/STOP state of the CPU.
Dependent on the CPU state the following behavior is shown by the DP
master:
Master behavior at • The global control command "Operate" is sent to the slaves by the
CPU RUN master. Here the DE-LED is ON.
• Every connected DP slave is cyclically attended with an output telegram
containing recent output data.
• The input data of the DP slaves were cyclically transferred to the input
area of the CPU.
Master behavior at • The global control command "Clear" is sent to the slaves by the master.
CPU STOP Here the DE-LED is blinking.
• DP slaves with fail safe mode were provided with output telegram length
"0".
• DP slaves without fail safe mode were provided with the whole output
telegram but with output data = 0.
• The input data of the DP slaves were further cyclically transferred to the
input area of the CPU.
Overview Content of this chapter is the employment of the RS485 slot for serial PtP
communication.
Here you’ll find all information about the protocols, the activation and
project engineering of the interface which are necessary for the serial
communication using the RS485 interface.
Fast introduction
General You may de-activate the DP master integrated in the SPEED7-CPU via a
hardware configuration and thus release the RS485 interface for PtP
(point-to-point) communication.
The RS485 interface supports in PtP operation the serial process
connection to different source res. destination systems.
Protocols The protocols res. procedures ASCII, STX/ETX, 3964R, USS and Modbus
are supported.
Switch of RS485 Per default, every CPU 31xS uses the RS485 interface for the Profibus-DP
for point-to-point master. A hardware configuration allows you to switch the RS485 interface
operation to point-to-point operation using Object properties and the parameter
"Function RS485".
Parameterization The parameterization happens during runtime using the SFC 216
(SER_CFG). For this you have to store the parameters in a DB for all
protocols except ASCII.
Communication The SFCs are controlling the communication. Send takes place via
SFC 217 (SER_SND) and receive via SFC 218 (SER_RCV).
The repeated call of the SFC 217 SER_SND delivers a return value for
3964R, USS and Modbus via RetVal that contains, among other things,
recent information about the acknowledgement of the partner station.
The protocols USS and Modbus allow to evaluate the receipt telegram by
calling the SFC 218 SER_RCV after SER_SND.
The SFCs are included in the consignment of the CPU 31xS.
Overview SFCs The following SFCs are used for the serial communication:
for serial
communication
SFC Description
SFC 216 SER_CFG RS485 parameterize
SFC 217 SER_SND RS485 send
SFC 218 SER_RCV RS485 receive
Overview The CPU 31xS supports the following protocols and procedures:
• ASCII communication
• STX/ETX
• 3964R
• USS
• Modbus
ASCII ASCII data communication is one of the simple forms of data exchange.
Incoming characters are transferred 1 to 1.
At ASCII, with every cycle the read-SFC is used to store the data that is in
the buffer at request time in a parameterized receive data block. If a
telegram is spread over various cycles, the data is overwritten. There is no
reception acknowledgement. The communication procedure has to be
controlled by the concerning user application.
An according Receive_ASCII-FB is to find at ftp.vipa.de.
STX/ETX STX/ETX is a simple protocol with start and end ID, where STX stands for
Start of Text and ETX for End of Text.
The STX/ETX procedure is suitable for the transfer of ASCII characters. It
does not use block checks (BCC). Any data transferred from the periphery
must be preceded by an Start followed by the data characters and the end
character.
Depending of the byte width the following ASCII characters can be
transfered: 5Bit: not allowed: 6Bit: 20...3Fh, 7Bit: 20...7Fh, 8Bit: 20...FFh.
The effective data which includes all the characters between Start and End
are transferred to the PLC when the End has been received.
When data is send from the PLC to a peripheral device, any user data is
handed to the SFC 217 (SER_SND) and is transferred with added Start-
and End-ID to the communication partner.
Message structure:
ZVZ
3964R The 3964R procedure controls the data transfer of a point-to-point link
between the CPU 31xS and a communication partner. The procedure adds
control characters to the message data during data transfer. These control
characters may be used by the communication partner to verify the
complete and error free receipt.
The procedure employs the following control characters:
STX
Monitor delayed acknowledgment
DLE
Message-data
DLE
ETX
BCC
Monitor delayed acknowledgment
DLE
Note!
When a DLE is transferred as part of the information it is repeated to
distinguish between data characters and DLE control characters that are
used to establish and to terminate the connection (DLE duplication). The
DLE duplication is reversed in the receiving station.
The 3964R procedure requires that a lower priority is assigned to the
communication partner. When communication partners issue simultaneous
send commands, the station with the lower priority will delay its send
command.
You may connect 1 master and max. 31 slaves at the bus where the single
slaves are addressed by the master via an address sign in the telegram.
The communication happens exclusively in half-duplex operation.
After a send command, the acknowledgement telegram must be read by a
call of the SFC 218 SER_RCV.
The telegrams for send and receive have the following structure:
Master-Slave telegram
STX LGE ADR PKE IND PWE STW HSW BCC
02h H L H L H L H L H L
Slave-Master telegram
STX LGE ADR PKE IND PWE ZSW HIW BCC
02h H L H L H L H L H L
Broadcast with set A request can be directed to a certain slave ore be send to all slaves as
Bit 5 in ADR-Byte broadcast message. For the identification of a broadcast message you
have to set Bit 5 to 1 in the ADR-Byte. Here the slave addr. (Bit 0 ... 4) is
7 6 5 4 3 2 1 0 ignored. In opposite to a "normal" send command, the broadcast does not
1 require a telegram evaluation via SFC 218 SER_RCV. Only write
commands may be send as broadcast.
Broadcast
The request telegrams send by the master and the respond telegrams of a
slave have the following structure:
Broadcast with A request can be directed to a special slave or at all slaves as broadcast
slave address = 0 message. To mark a broadcast message, the slave address 0 is used.
In opposite to a "normal" send command, the broadcast does not require a
telegram evaluation via SFC 218 SER_RCV.
Only write commands may be send as broadcast.
The mode selection happens during runtime by using the SFC 216 SER_CFG.
Supported Modbus The following Modbus Protocols are supported by the RS485 interface
protocols • Modbus RTU Master
• Modbus ASCII Master
Outline Per default, every CPU 31xS uses the RS485 interface for the Profibus-DP
master. A hardware configuration allows you to switch the RS485 interface
to point-to-point operation using Object properties and the parameter
"Function RS485".
Switch to For the usage of the System 300S modules from VIPA at the SPEED-Bus,
PtP operation the inclusion of the System 300S modules in the hardware catalog is
required using the GSD file from VIPA.
The switch to PtP operation has the following approach:
• Start the hardware configurator from Siemens and include the
Standard bus speedbus.gsd for SPEED7 from VIPA.
Slot Module
1 • Configure CPU 318-2DP (6ES7 318-2AJ00-0AB0/V3.0) from
2 CPU 318-2 Siemens.
X2 DP
X1 MPI/DP • Starting with slot 4, place the System 300 modules at the standard
3 bus.
- Standard bus modules
- internal PG/OP, CP • Place and connect below this modules the CPs (internal) and then
- SPEED-Bus CPs, DPMs SPEED-Bus-CPs and DP master.
always as last module • For the SPEED-Bus, include and connect the Siemens DP master
342-5DA02 V5.0 CP 342-5 (342-5DA02 V5.0) always as last module and parameterize
it to the operating mode DP master. For this, the Profibus address
virtual DP-Master for CPU
and all SPEED-Bus modules must be different from the range 100...116. This master system is
used to connect every SPEED-Bus module as VIPA_SPEEDbus
slave. Here, the Profibus address is equivalent to the slot no.
(n) VIPA (100) VIPA
CPU: starting with 100 for the CPU. Place the concerning module at slot 0
... Addr.:100 of every slave and alter if needed the parameters.
VIPA_SPEEDbus
• Place your SPEED7-CPU with Profibus address 100 at slot 0.
• Set in Function RS485 "PtP" in the object properties.
Steckpl. Best.-Nr.
0 CPU at Slot 100
After transferring your project to the CPU together with your PLC
application, the RS485 interface is after the boot sequence available for
PtP communication.
Note!
More detailed information about SPEED-Bus project engineering and
project transfer is in the chapter “Employment CPU31xS"!
Properties RS485 • Logical states represented by voltage differences between the two cores
of a twisted pair cable
• Serial bus connection in two-wire technology using half duplex mode
• Data communications up to a max. distance of 500m
• Data communication rate up to 115.2kBaud
Connection
3
RxD/TxD-P (B) RxD/TxD-P (B)
shield
Periphery
RxD/TxD-P (B)
RxD/TxD-N (A)
Periphery
RxD/TxD-P (B)
RxD/TxD-N (A)
Overview The data transfer is handled during runtime by using SFCs. The principles
of data transfer are the same for all protocols and is shortly illustrated in
the following.
Principle Data that is into the according data channel by the PLC, is stored in a FIFO
send buffer (first in first out) with a size of 2x1024Byte and then put out via
the interface.
When the interface receives data, this is stored in a FIFO receive buffer
with a size of 2x1024Byte and can there be read by the PLC.
If the data is transferred via a protocol, the adoption of the data to the
according protocol happens automatically.
In opposite to ASCII and STX/ETX, the protocols 3964R, USS and Modbus
require the acknowledgement of the partner.
An additional call of the SFC 217 SER_SND causes a return value in
RetVal that includes among others recent information about the
acknowledgement of the partner.
Further on for USS and Modbus after a SER_SND the acknowledgement
telegram must be evaluated by call of the SFC 218 SER_RCV.
IN RS485
SER_RCV RECEIVE 1024Byte
SFC 218
1024Byte
SER_CFG
CFG
SFC 216 OUT
1024Byte
SER_SND
SFC 217 SEND 1024Byte
Parameterization
SFC 216 The parameterization happens during runtime deploying the SFC 216
(SER_CFG) (SER_CFG). You have to store the parameters for STX/ETX, 3964R, USS
and Modbus in a DB.
Parameter All time settings for timeouts must be set as hexadecimal value. Find the
description Hex value by multiplicating the wanted time in seconds with the baudrate.
Protocol Here you fix the protocol to be used. You may choose between:
1: ASCII
2: STX/ETX
3: 3964R
4: USS Master
5: Modbus RTU Master
6: Modbus ASCII Master
Note!
The start res. end sign should always be a value <20, otherwise the sign is
ignored!
Parity The parity is -depending on the value- even or odd. For parity control, the
information bits are extended with the parity bit, that amends via its value
("0" or "1") the value of all bits to a defined status. If no parity is set, the
parity bit is set to "1", but not evaluated.
0: NONE 1: ODD 2: EVEN
StopBits The stop bits are set at the end of each transferred character and mark the
end of a character.
1: 1Bit 2: 1.5Bit 3: 2Bit
Communication
Overview The communication happens via the send and receive blocks SFC 217
(SER_SND) and SFC 218 (SER_RCV).
The SFCs are included in the consignment of the CPU 31xS.
SFC 217 This block sends data via the serial interface.
(SER_SND) The repeated call of the SFC 217 SER_SND delivers a return value for
3964R, USS and Modbus via RetVal that contains, among other things,
recent information about the acknowledgement of the partner station.
The protocols USS and Modbus require to evaluate the receipt telegram by
calling the SFC 218 SER_RCV after SER_SND.
Parameter
Name Declaration Type Comment
DataPtr IN ANY Pointer to Data Buffer for sending data
DataLen OUT WORD Length of data sent
RetVal OUT WORD Error Code ( 0 = OK )
DataPtr Here you define a range of the type Pointer for the send buffer where the
data that has to be send is stored. You have to set type, start and length.
Example: Data is stored in DB5 starting at 0.0 with a length of
124Byte.
DataPtr:=P#DB5.DBX0.0 BYTE 124
STX/ETX
Value Description
9000h Buffer overflow (no data send)
9001h Data too long (>1024Byte)
9002h Data too short (0Byte)
9004h Character not allowed
3964R
Value Description
2000h Send ready without error
80FFh NAK received - error in communication
80FEh Data transfer without acknowledgement of partner or error
at acknowledgement
9000h Buffer overflow (no data send)
9001h Data too long (>1024Byte)
9002h Data too short (0Byte)
Principles of The following text shortly illustrates the structure of programming a send
programming command for the different protocols.
Busy ? J Busy ? J
N N
N N
N N
SFC 218
RetVal 2000h ? J RetVal 2000h ? J
SER_RCV
N N
Data evaluation Data evaluation
End End
ASCII / STX/ETX
SFC 217
SER_SND
RetVal 900xh J
Error evaluation
N
End
SFC 218 This block receives data via the serial interface.
(SER_RCV) Using the SFC 218 SER_RCV after SER_SND with the protocols USS and
Modbus the acknowledgement telegram can be read.
Parameter
Name Declaration Type Comment
DataPtr IN ANY Pointer to Data Buffer for received data
DataLen OUT WORD Length of received data
Error OUT WORD Error Number
RetVal OUT WORD Error Code ( 0 = OK )
DataPtr Here you set a range of the type Pointer for the receive buffer where the
reception data is stored. You have to set type, start and length.
Example: Data is stored in DB5 starting at 0.0 with a length of 124Byte.
DataPtr:=P#DB5.DBX0.0 BYTE 124
Error This word gets an entry in case of an error. The following error messages
may be created depending on the protocol:
ASCII
Bit Error Description
0 overrun Overflow, a sign couldn’t be read fast enough from the
interface
1 framing error Error that shows that a defined bit frame is not
coincident, exceeds the allowed length or contains an
additional Bit sequence (Stopbit error)
2 parity Parity error
3 overflow Buffer is full
STX/ETX
Bit Error Description
0 overflow The received telegram exceeds the size of the receive
buffer.
1 char A sign outside the range 20h...7Fh has been received.
3 overflow Buffer is full
Principles of The following picture shows the basic structure for programming a receive
programming command. This structure can be used for all protocols.
SFC 218
SER_RCV
RetVal 0000h ? J
N Data evaluation
End
RetVal 8xxxh ? J
N
Error evaluation
End
Overview The following chapter describes the deployment of the CPU 31xSN/NET
and the communication using TCP/IP. Please regard the chapter "Fast
introduction" where you find all information compressed required for the
project engineering of the CPU 31xS with CP 343. After the fast
introduction, the mentioned steps are described in detail.
Industrial
Operational layer Plant
computer Ethernet
PPS CAD
Plant-oriented
control computer
Management layer manufacturing, stock,
production data
PPS CAD H1
layer
sensor, actuator, regulator, multiplexer, operating consoles Sensor / actuator
Bus
Industrial Ethernet Industrial Ethernet is an electrical net based on shielded twisted pair
cabling or optical net based on optical fiber.
Industrial Ethernet is defined by the international standard IEEE 802.3. The
net access of Industrial Ethernet corresponds to IEEE 802.3 - CSMA/CD
(Carrier Sense Multiple Access/Collision Detection) scheme: every station
"listens” on the bus cable and receives communication messages that are
addressed to it.
Stations will only initiate a transmission when the line is unoccupied. In the
event that two participants should start transmitting simultaneously, they
will detect this and stop transmitting to restart after a random delay time
has expired.
Using switches there is the possibility for communication without collisions.
Overview The ISO/OSI reference model is based on a proposal that was developed
by the International Standards Organization (ISO). This represents the first
step towards an international standard for the different protocols. It is
referred to as the ISO-OSI layer model. OSI is the abbreviation for Open
System Interconnection, the communication between open systems. The
ISO/OSI reference model does not represent a network architecture as it
does not define the services and protocols used by the different layers. The
model simply specifies the tasks that the different layers must perform.
All current communication systems are based on the ISO/OSI reference
model which is defined by the ISO 7498 standard. The reference model
structures communication systems into 7 layers that cover different
communication tasks. In this manner the complexity of the communication
between different systems is divided amongst different layers to simplify
the task.
The following layers have been defined:
Layer Function
Layer 7 Application Layer
Layer 6 Presentation Layer
Layer 5 Session Layer
Layer 4 Transport Layer
Layer 3 Network Layer
Layer 2 Data Link Layer
Layer 1 Physical Layer
Principles
Network (LAN) A network res. LAN (Local Area Network) provides a link between different
stations that enables them to communicate with each other.
Network stations consist of PCs, IPCs, TCP/IP adapters, etc.
Network stations are separated by a minimum distance and connected by
means of a network cable. The combination of network stations and the
network cable represent a complete segment.
All the segments of a network form the Ethernet (physics of a network).
Twisted Pair In the early days of networking the Triaxial- (yellow cable) or thin Ethernet
cable (Cheapernet) was used as communication medium. This has been
superseded by the twisted-pair network cable due to its immunity to
interference. The CPU 31xSN/NET module has a twisted-pair connector.
The twisted-pair cable consists of 8 cores that are twisted together in pairs.
Due to these twists this system is provides an increased level of immunity
to electrical interference. For linking please use twisted pair cable which at
least corresponds to the category 5.
Where the coaxial Ethernet networks are based on a bus topology the
twisted-pair network is based on a point-to-point scheme.
The network that may be established by means of this cable has a star
topology. Every station is connected to the star coupler (hub/switch) by
means of a separate cable. The hub/switch provides the interface to the
Ethernet.
Hub (repeater) The hub is the central element that is required to implement a twisted-pair
Ethernet network.
It is the job of the hub to regenerate and to amplify the signals in both
directions. At the same time it must have the facility to detect and process
segment wide collisions and to relay this information. The hub is not
accessible by means of a separate network address since it is not visible to
the stations on the network.
A hub has provisions to interface to Ethernet or to another hub res. switch.
Switch A switch also is a central element for realizing Ethernet on Twisted Pair.
Several stations res. hubs are connected via a switch. Afterwards they are
able to communicate with each other via the switch without interfering the
network. An intelligent hardware analyzes the incoming telegrams of every
port of the switch and passes them collision free on to the destination
stations of the switch. A switch optimizes the bandwidth in every connected
segment of a network. Switches enable exclusive connections between the
segments of a network changing at request.
Protocols
TCP/IP TCP/IP protocols are available on all major systems. At the bottom end this
applies to simple PCs, through to the typical mini-computer up to
mainframes.
For the wide spread of internet accesses and connections, TCP/IP is often
used to assemble heterogeneous system pools.
TCP/IP, standing for Transmission Control Protocol and Internet Protocol,
collects a various range of protocols and functions.
TCP and IP are only two of the protocols required for the assembly of a
complete architecture. The application layer provides programs like "FTP"
and "Telnet" for the PC.
The application layer of the Ethernet part of the CPU 31xSN/NET is defined
with the user application using the standard handling blocks.
These user applications use the transport layer with the protocols TCP and
UDP for the data transfer which themselves communicate via the IP
protocol with the internet layer.
IP The internet protocol covers the network layer (Layer 3) of the ISO/OSI
layer model.
The purpose of IP is to send data packages from on PC to another passing
several other PCs. These data packages are referred to as datagrams.
The IP doesn't guarantee the correct sequence of the datagrams nor the
delivery at the receiver.
For the unambiguous identification between sender and receiver at IPv4
32Bit addresses (IP addresses) are used that are written as four octets
(exactly 8Bit), e.g. 172.16.192.11.
These internet addresses are defined and assigned worldwide from the
DDN network (Defense Department Network), thus every user may
communicate with all other TCP/IP users.
One part of the address specifies the network, the rest serves the
identification of the participants inside the network. The boarder between
the network and the host part is variable and depends on the size of the
network.
To save IP addresses, so called NAT router are used that have one official
IP address and cover the network. Then the network can use any IP
address.
TCP The TCP (Transmission Control Protocol) bases directly on the IP and
thus covers the transport layer (layer 4) of the OSI layer model. TCP is a
connection orientated end-to-end protocol and serves the logic connection
between two partners.
TCP guarantees the correct sequence and reliability of the data transfer.
Therefore you need a relatively large protocol overhead that slows down
the transfer speed.
Every datagram gets a header of at least 20Byte. This header also
contains a sequence number identifying the series. This has the
consequence that the single datagrams may reach the destination on
different ways through the network.
Using TCP connections, the whole data length is not transmitted. This
means that the recipient has to know how many bytes belong to a
message. To transfer data with variable length you may begin the user
data with the length information and evaluate this at the counter station.
Properties • Besides of the IP address ports are used for the addressing. A port
address should be within the range of 2000...65535. Partner and local
ports may only be identical at one connection.
• Not depending on the used protocol, the PLC needs the VIPA handling
blocks AG_SEND (FC 5) and AG_RECV (FC 6) for data transfer.
UDP The UDP (User Datagram Protocol) is a connection free transport protocol.
It has been defined in the RFC768 (Request for Comment). Compared to
TCP, it has much fewer characteristics.
The addressing happens via port numbers.
UDP is a fast unsafe protocol for it doesn't care about missing data
packages nor about their sequence.
ISO-on-TCP The TCP transport service works stream orientated. This means that data
RFC1006 packages assembled by the user not necessarily have to receive the
partner in the same packaging. Depending on the data amount, packages
may though come in in the correct sequence but differently packed. This
causes that the recipient may not recognize the package borders anymore.
For example you may send 2x 10Byte packages but the counter station
receives them as 20Byte package. But for most of the applications the
correct packaging is important.
Due to this you need another protocol above TCP. This purpose is defined
in the protocol RFC1006. The protocol definition describes the function of
an ISO transport interface (ISO 8072) basing upon the transport interface
TCP (RFC793).
The basic protocol of RFC1006 is nearly identical to TP0 (Transport
Protocol, Class 0) in ISO 8073.
For RFC1006 is run as protocol for TCP, the decoding takes place in the
data section of the TCP package.
Subnet mask The Host-ID can be further divided into a Subnet-ID and a new Host-ID by
using an bit for bit AND assignment with the Subnet mask.
The area of the original Host-ID that is overwritten by 1 of the Subnet mask
becomes the Subnet-ID, the rest is the new Host-ID.
Address at first At the first start-up of a CPU 31xSN/NET, Ethernet PG/OP channel and
start-up CP 343 part of the CPU 31xSN/NET do not have an IP address. The
assignment takes place using the following possibilities:
• Using Siemens SIMATIC Manager switch PG/PC interface to "TCP/IP...
RFC1006". Via "Assign Ethernet address" search the appropriate CP
and assign IP parameters. After that the CP is directly assigned to the
new IP parameters without any restart of the CPU.
• You may assign an IP address and a subnet mask to your CP with the
help of a "minimum project" and transfer this via MMC or MPI into the
CPU. After a reboot of the CPU and after switching the PG/PC interface
to "TCP/IP... RFC1006" you may now configure your CPU online via the
favored CP.
Address classes For IPv4 addresses there are five address formats (class A to class E) that
are all of a length of 4byte = 32bit.
The classes A, B and C are used for individual addresses, class D for
multicast addresses and class E is reserved for special purposes.
The address formats of the 3 classes A, B, C are only differing in the length
of Network-ID and Host-ID.
Note!
Never choose an IP address with Host-ID=0 or Host-ID=maximum!
(e.g. for class B with subnet mask = 255.255.0.0, the "172.16.0.0" is
reserved and the "172.16.255.255" is occupied as local broadcast address
for this network.)
Network planning
Standards and The applicable rules and regulations have to be satisfied in order to
guidelines establish reliable communications between the different stations.
These agreements define the form of the data protocol, the method of bus
access and other principles that are important for reliable communications.
The VIPA CPU 31xSN/NET was developed in accordance with the standards
defined by ISO.
International and national committees have defined the following standards
and guidelines for networking technologies:
Hub/ Hub/
Switch Switch
Analyzing the • What is the size of the area that must be served by the network?
requirements • How many network segments provide the best solution for the physical
(space, interference related) conditions encountered on site?
• How many network stations (SPS, IPC, PC, transceiver, bridges if
required) must be connected to the cable?
• What is the distance between the different stations on the network?
• What is the expected "growth rate” and the expected number of
connections that must be catered for by the system?
• What data amount has to be handled (band width, accesses/sec.)?
Drawing a Draw a diagram of the network. Identify every hardware item (i.e. station
network diagram cable, hub, switch). Observe the applicable rules and restrictions.
Measure the distance between all components to ensure that the maximum
length is not exceeded.
Linking with Please regard that the following software packages must be installed for
NetPro the project engineering:
• Siemens SIMATIC Manager V. 5.1
• For the project engineering of SPEED7 modules the vipa_speedbus.gsd
is included.
• Siemens SIMATIC NET
Net-Project You may administrate several subnets in one project. Every station has to
variants be created once. A station may be assigned to several subnets by
assigning the CPs accordingly.
In the following typical project variants for networks are listed:
1 subnet - The simplest case is a plant with stations that have to be connected via
1 project one subnet of the type Industrial Ethernet.
For this you create an object "Ethernet". Stations that are created in the
same project refer to this object when they are configured as net knots.
They may then be selected directly. Foreign devices are listed in this
subnet as "Other station" during project engineering.
2 or more subnets - Due to different tasks of the stations or due to the expansion of your plant it
1 project may be necessary to create several nets. Here you may create several
subnets in one project and configure the stations easily for communication.
1 or more subnets – At complex linked plants it is sensible to administrate plant parts in several
several part part projects. Here it may be necessary to create project exceeding
projects connections. For this the Siemens SIMATIC Manager starting with V. 5.2
provides the multi project function. This function allows you to split projects
and join them again. A more detailed description is to be found in the
manual of the Siemens SIMATIC Manager.
Subnet exceeding These are connections that long into another subnet due to the complexity
connections of the plant. The subnets are connected via a router. By setting a router
address during the hardware configuration of your CP you may instruct the
CP to include the according subnet via this router for communication.
Communication The internal CP 343 of the CPU 31xSN/NET is directly connected to the
between CP 343 CPU 31xS via a Dual-Port-RAM. The CPU manages the data exchange
and CPU with the VIPA handling blocks AG_SEND (FC 5) and AG_RECV (FC 6).
The communication via the according protocols are controlled by
connections that are parameterized in the Siemens project engineering tool
NetPro and that may be transferred into the CPU via MMC, MPI or directly
via Ethernet.
For the transfer via Ethernet, your CP must be connected to Ethernet with
valid IP parameters. The assignment takes place either using the
corresponding menu item of the Siemens SIMATIC Manager or via a
minimum project where the IP parameters are defined. This project can be
transferred to the CPU via MMC or MPI.
System 300S
CPU 31xSN/NET
Frames
Switch
Ethernet Additional interfaces
Frames
CPU 31xSN/NET
Frames
CPU CP
Application Connections
program Daten configured
(SEND, RECEIVE) HTBs with NetPro
System 200V
Connection types For the communication the following connection types are available:
• TCP res. ISO-on-TCP for the secured data transfer of related data
blocks between two Ethernet participants.
• UDP for the unsecured data transfer of related data blocks between two
Ethernet.
Connection Using configurable connections there is always one station that actively
establishment establishes a connection. The counter station waits passively for the active
connection. Only then productive data can be transferred.
Operating modes Depending on the connection, the following operating modes are available:
SEND/RECEIVE
The SEND/RECEIVE interface allows the program controlled com-
munication to any partner station via a configured connection. Here the
data transfer happens by call from your user application. The FC 5 and
FC 6 that are part of the VIPA block library are serving as interface.
This enables your control to send messages depending on process events.
FETCH/WRITE PASSIVE
With the help of FETCH/WRITE services partner systems have the direct
access to memory areas of the CPU. This are "passive" communication
connections that have to be configured. The connections are "actively"
established by the connection partner (e.g. Siemens-S5).
FETCH PASSIVE (request data)
FETCH allows a partner system to request data.
WRITE PASSIVE (write data)
This allows a partner system to write data in the data area of the CPU.
Function overview
Outline In the following the functions are listed that are supported by the CP part of
the CPU 31xSN/Net starting with CP firmware version 1.7.4:
Fast introduction
Overview At the first start-up of a CPU 31xSN/NET, Ethernet PG/OP and CP 343 of
the CPU 31xSN/NET do not have any IP address. The assignment takes
place directly via the hardware configuration of the Siemens SIMATIC
Manager. For the project engineering of a CPU 31xS with CP 343 please
follow this approach:
• Assembly and commissioning
• Hardware configuration (Inclusion of CP in CPU)
• CP project engineering via NetPro (connection to Ethernet)
• PLC programming via user application (connection to PLC)
• Transfer of the complete project to CPU
Note
To be compatible to the Siemens SIMATIC Manager, the CPU 31xS from VIPA has to
be configured as
CPU 318-2DP (6ES7 318-2AJ00-0AB0)!
The Ethernet PG/OP channel of the CPU 31xSN/NET is always configured virtually as
1st module after the really plugged modules at the standard bus as CP343-1
(343-1EX11) from Siemens. The CP 343 of a CPU 31xSN/NET has always to be
configured below the before configured CP also as CP343-1 (343-1EX11).
Assembly and • Install your System 300S with the CPU 31xSN/NET.
commissioning • Wire the system by connecting cables for voltage supply, signals and
Ethernet. A detailed description is to be found in the chapter "Assembly
and installation guidelines".
• Switch on the voltage supply. → After a short boot time, the CP is in
idle.
At the first commissioning res. after an overall reset of the CPU,
Ethernet PG/OP channel and CP have no IP address. For control
purposes you may now reach the CP via the MAC address. The MAC
address is to be found beneath the front flap on the left side of the
module at a small label on the module.
Assign IP For the assignment of the IP parameters such as IP address, Subnet mask
parameters etc. you have the following possibilities:
• Online using Siemens SIMATIC Manager via "Assign Ethernet Address"
(at least CP-Firmware 1.7.4)
• with the help of a "minimum project" and transfer this via MMC or MPI
into the CPU. After a reboot of the CPU and after switching the PG/PC
interface to "TCP/IP... RFC1006" you may now configure your CPU
online via the CP.
Address Please regard this functionality is available with firmware version 1.7.4 and
assignment with up.
"Assign Ethernet • Start Siemens SIMATIC Manager
Address"
• Switch to "TCP/IP... RFC1006" using Options > Set PG/PC interface.
• The dialog for initialization of a station opens by PLC > Assign Ethernet
Address.
• To get the stations and their MAC address use the [Browse] button or
type in the MAC Address. The Mac address can be found at a label at
the side of the CPU.
• Choose if necessary the known MAC address of the list of found
stations.
• Either type in the IP configuration like IP address, subnet mask and
gateway. Or your station is automatically provided with IP parameters by
means of a DHCP server. Depending of the chosen option the DHCP
server is to be supplied with MAC address, equipment name or client ID.
The client ID is a numerical order of max. 63 characters. The following
characters are allowed: "hyphen", 0-9, a-z, A-Z
• Confirm with [Assign ...]
Directly after the assignment the CP is online reachable using the set IP
parameters.
Configure The link-up between the stations happens with the graphical interface
connections with NetPro. Start NetPro by clicking on a network in your project res. on
NetPro connections in the CPU directory.
Connections
[5]
Link-up stations For the project engineering of connections, connected stations are
presumed. To link-up stations, point on the colored net mark of the
according CP with the mouse and drag it to the network you want to
assign. The connection is displayed graphically by a line.
Configure For the project engineering of new connections click on the according CPU
connections and choose "Insert new connection” from the context menu.
Station 1
CPU DP MPI CP CP
318-2 343-1 343-1
Via the dialog window you may set the parameters for a connection. The
parameters ID and LADDR are required for the usage on the blocks
AG_SEND res. AG_RECV.
Save and compile Save and compile your project and close NetPro.
connections To store the CP project engineering data in the system data, you have to
activate the option "Save configuration data on the CPU" (default setting)
at object properties area Options in the hardware configuration of the CP.
PLC user For the execution of connection commands at the PLC, your CPU requires
application an user application. For this, exclusively the VIPA handling blocks
AG_SEND (FC 5) and AG_RECV (FC 6) are used. The blocks are part of
the VIPA library that is included in the consignment as CD (SW830).
Specify the according CP via the parameters ID and LADDR by calling
FC 5 res. FC 6.
The following pages provide a more detailed description of the steps of the
fast introduction.
Hardware configuration
Overview For the Hardware configuration the hardware configurator from Siemens is
used. Here you set amongst others the IP address of the CP and configure
the hardware components of your PLC.
Due to the fact that neither the Ethernet PG/OP channel nor the CP 343
have an IP address in delivery state you may engineer the CPU exclusively
via MPI or MMC.
For the access to the CPU via the Ethernet PG/OP channel res. the
CP 343 it is required that the CPU has a hardware project engineering
where IP address and subnet mask for Ethernet PG/OP res. CP 343 are
defined.
Note!
For the project engineering a thorough knowledge of the SIMATIC
Manager and the hardware configurator from Siemens are required and
assumed!
Note
To be compatible to the Siemens SIMATIC Manager, the CPU 31xS from VIPA has to
be configured as
CPU 318-2DP (6ES7 318-2AJ00-0AB0)!
The Ethernet PG/OP channel of the CPU 31xSN/NET is always configured virtually as
1st module after the really plugged modules at the standard bus as CP343-1
(343-1EX11) from Siemens. The CP 343 of a CPU 31xSN/NET has always to be
configured below the before configured CP also as CP343-1 (343-1EX11).
Steps of the The following text shows the approach of the project engineering in the
project hardware configurator from Siemens in an abstract sample.
engineering The project engineering is divided into 3 parts:
• Project engineering of the CPU
• Project engineering of the really plugged modules at the standard bus
• Project engineering Ethernet PG/OP channel and CP 343
Project • Start the hardware configurator from Siemens with a new project and
engineering insert a profile rail from the hardware catalog.
of the CPU • Place the following Siemens CPU at slot 2:
CPU 318-2DP (6ES7 318-2AJ00-0AB0 V. 3.0)
Project The modules at the right side of the CPU at the standard bus are
engineering of the configured with the following approach:
modules at the • Include your System 300V modules at the standard bus in the plugged
standard bus sequence starting with slot 4.
• Parameterize the CPU res. the modules where appropriate. The
parameter window opens by a double click on the according module.
Standard bus
Slot Module
1
2 CPU 318-2
X2 DP
X1 MPI/DP
CPU 31xSN/NET DI DO DIO AI AO 3
4 DI
5 DO
6 DIO
7 AI
8 AO
9
10
11
Project engineering For the internal Ethernet PG/OP channel that every SPEED7-CPU
Ethernet PG/OP includes, you have to configure a Siemens CP 343-1 (SIMATIC 300 \
channel and CP 343 CP 300 \ Industrial Ethernet \CP 343-1 \ 6GK7 343-1EX11 0XE0) always
as 1st module below the really plugged modules.
The integrated CP 343 of the CPU 31xSN/NET is also configured as
CP 343-1 (343-1EX11) but always below the before configured CP 343-1.
2 CPU 318-2
X2 DP
X1 MPI/DP
CPU 31xSN/NET DI DO DIO AI AO 3
4 DI
5 DO
6 DIO
7 AI
8 AO
Ethernet PG/OP channel
9 343-1EX11
10 343-1EX11
CP 343
11
Open the property window via double-click on the CP 343-1EX11 and enter
at properties the IP address, subnet mask and gateway for the CPs and
select the wanted subnet.
Bus extension To extend the bus you may use the IM 360 from Siemens where you can
with IM 360 and connect up to 3 further extension racks via the IM 361. Bus extensions are
IM 361 always placed at slot 3.
Project enginee- Detailed information about project engineering of the SPEED-Bus modules
ring SPEED-Bus and the project transfer may be found at Chapter "Deployment CPU 31xS".
and project
transfer
Configure connections
Outline The project engineering of connections i.e. the "link-up" between stations
happens in NetPro from Siemens. NetPro is a graphical user interface for
the link-up of stations.
A communication connection enables the program controlled communi-
cation between two participants at the Industrial Ethernet. The communi-
cation partners may here be part of the same project or - at multi projects -
separated within related part projects.
Communication connections to partners outside of a project are configured
via the object "In unknown project" or via deputy objects like "Other
stations" or Siemens "SIMATIC S5 Station".
CP Ethernet partner
send receive
Communication
link
receive send
. . .
. . .
. . .
Ethernet partner
send receive
Communication
link
receive send
Requirements • Siemens SIMATIC Manager V. 5.1 or higher and SIMATIC NET are
installed.
• The CP has been engineered at the hardware configuration, entered
into the hardware configuration and linked-up to the Ethernet subnet.
• The CP as bus participant has an IP address.
Note!
All stations outside of the recent project must be configured as
replacement objects like e.g. Siemens "SIMATIC S5" or "other station" or
with the object "In unknown project".
When creating a connection you may also choose the partner type
"unspecified" and set the required remote parameter directly in the
connection dialog.
Work environment For the project engineering of connections, a thorough knowledge with
of NetPro NetPro from Siemens is required! The following passage only describes the
basic usage of NetPro. More detailed information about NetPro is to be
found in the according online manual res. documentation.
Start NetPro by clicking on a "net" in the Siemens SIMATIC Manager or on
"connections" within the CPU.
1 2
Profibus
MPI + Profibus-DP
Profibus-PA
Ethernet + Stationes
+ Subnet
Station 1 Station 2
CPU DP MPI CP CP CPU DP MPI CP CP
318-2 343-1 343-1 318-2 343-1 343-1
PLC stations You receive the following graphical display for every PLC station and their
component. By selecting the single components, the context menu offers
you several functions:
1 1 Station
Station 1 This includes a PLC station with rack, CPU and communication
CPU DP MPI CP CP components. Via the context menu you may configure a station
318-2 343-1 343-1 added from the net objects and its concerning components in
the hardware configurator. After returning to NetPro, the new
configured components are shown.
2 CPU
1 2 3 4 5
A click onto the CPU shows the connection table. The
connection table shows all connections that are configured for
the CPU.
3 Internal communication components
This displays the communication components that are available
in your CPU. For the SPEED7-Net-CPUs are configured as
CPU 318-2DP the internal components do not show the CP.
Due to this, the CPs that are included in the SPEED7-Net-CPU
must be configured as external CPs behind the really plugged
modules. The CPs are then also shown in NetPro as external
CPs (4, 5) in the station.
4 Ethernet PG/OP channel
The internal Ethernet PG/OP channel must always be
configured as 1st CP in the hardware configuration. This CP
only serves the PG/OP communication. You may not configure
connections.
5 CP 343
The internal CP 343 must always be configured as 2nd CP in
the hardware configuration after the Ethernet PG/OP channel.
Link up stations NetPro offers you the option to link-up the communicating stations. You
may link-up the stations via the properties in the hardware configuration or
graphically via NetPro. For this you point the mouse on the colored net
mark of the according CP and drag and drop it to the net you want to link.
Now the CP is linked up to the wanted net by means of a line.
Industrial Ethernet Industrial Ethernet
Station 1 Station 1
CPU DP MPI CP CP CPU DP MPI CP CP
318-2 343-1 343-1 318-2 343-1 343-1
Projecting For the project engineering of connections, open the connection list by
connections selecting the according CPU. Choose Insert new connection in the context
menu:
Station 1
CPU DP MPI CP CP
318-2 343-1 343-1
A dialog window opens where you may choose the connection partner and
the type of the connection.
Highlight the partner station to which you would like to establish a
connection.
Choose at "Type" the connection type to be used.
The following connections are supported by the CP at this time:
ISO-on-TCP (SEND-RECEIVE, FETCH-WRITE PASSIVE)
TCP (SEND-RECEIVE, FETCH-WRITE PASSIVE)
UDP (SEND-RECEIVE)
General information If activated, a properties dialog for the according connection opens. This
ID dialog window is the link to your PLC program. Here you may adjust the
LADDR Local ID and evaluate the LADDR.
Both are parameters that must be given to your PLC application when
using the FC 5 and 6 (AG_SEND, AG_RECEIVE). Please do always use
the VIPA FCs that are delivered with the SW830 as a library.
Note!
Please regard that a CP depending ID is assigned to the connections of
the SEND/RECEIVE interface. This may cause alterations of the ID at
changes of the project. In this case you also have to adjust the interface
supply of AG_SEND res. AG_RECV in the user application.
If a CP is exchanged by another one, this must at least provide the same
services and must at least have the same version level. Only this can
guarantee the connections configured via the CP to remain consistent and
useable.
Route The route allows you to access the concerning CP that should be used for
the connection. By using a CPU 31xSN/NET you must use the 2nd CP of
the path selection for the communication via the internal CP 343. As 1st CP
in the list always the integrated Ethernet PG/OP channel is shown though
this only supports PG/OP communication.
Addresses The register addresses shows the relevant local and partner address
information as suggestion values. Depending on the communication type
you may leave the address information unspecified.
The following table shows the combination options with the different
operating modes:
Address parameter A connection is specified by the local and partner connection end point. At
the project engineering of connections ports/TSAPs must be congruent
crosswise. Depending on the protocol the following parameters define a
connection end point:
Port Ports res. port addresses are defining the access point to the user
application within the station/CPU. These must be unambiguous. A port
address should be within the range of 2000...65535. Foreign and local
ports may only be identical with one connection.
Save and compile After you configured all connections this way, you may save and compile
connections your project and exit NetPro.
To store the CP project engineering data in the system data, you have to
activate the option "Store project data in the CPU" (default setting) at
object properties area Options in the hardware configuration of the CP.
Broadcast By selecting All broadcast stations as connection partner, you define that
stations UDP telegrams are to be send to all available broadcast participants.
Please regard that the CP may exclusively receive broadcast telegrams.
The reception of user data via broadcast is not possible. Per default,
broadcasts that are only serving the Ethernet communication, like e.g.
ARP-Requests (Search MAC <> IP address), are received and accordingly
processed.
For the identification of the broadcast participants within the net, you have
to define a valid broadcast address as partner IP during project engi-
neering of a broadcast connection. Additionally to the broadcast address
you have to set a common port for sender and receiver.
Multicast By selecting All Multicast stations you define that UDP telegrams have to
stations be send res. received by all participants of a multicast group. In opposite to
broadcast here a reception is possible.
For the identification of the multicast participants within the net, you have to
define a valid multicast group address as partner IP during project
engineering of a multicast connection. Additionally to this address you
have to set a common port for sender and receiver.
The maximum number of multicast circles, which are supported by the
Ethernet CP 343 - SPEED-Bus, is identical to the maximum number of
connections.
Overview For the execution of connection commands at the PLC, your CPU requires
an user application. For this, exclusively the VIPA handling blocks
AG_SEND (FC 5) and AG_RECV (FC 6) are used. By including these
blocks into the cycle block OB 1 you may send and receive data cyclic.
The two FCs are part of the VIPA library, that is included in the
consignment as CD (SW830).
Note!
Please regard that you may only use the SEND/RECV-FCs from VIPA in
your user application for the communication with VIPA-CPs. At a change to
VIPA-CPs in an already existing project, the present AG_SEND/ AG_LSEND
res. AG_RECV/AG_LRECV may be replaced by AG_SEND res. AG_RECV
from VIPA without adjustment. Due to the fact that the CP automatically
adjusts itself to the length of the data to transfer, the L variant of SEND res.
RECV is not required for VIPA CPs.
Communication For the communication between CPU and CP, the following FCs are
blocks available:
AG_SEND (FC 5)
This block transfers the user data from the data area given in SEND to the
CP specified via ID and LADDR. As data area you may set a PIQ, bit
memory or data block area. When the data area has been transferred
without errors, "order ready without error” is returned.
AG_RECV (FC 6)
The block transfers the user data from the CP into a data area defined via
RECV. As data area you may set a PII, bit memory or data block area.
When the data area has been transferred without errors, "order ready
without error” is returned.
Status displays The CP processes send and receive commands independently from the
CPU cycle and needs for this transfer time. The interface with the FC
blocks to the user application is here synchronized by means of
acknowledgements/receipts.
For status evaluation the communication blocks return parameters that
may be evaluated directly in the user application.
These status displays are updated at every block call.
Deployment at high Do not use cyclic calls of the communication blocks in OB 1. This causes a
communication load permanent communication between CPU and CP. Program instead the
communication blocks within a time OB where the cycle time is higher than
the time of the OB 1 respectively event controlled.
FC call is faster If a block is called a second time in the user application before the data of
than CP transfer the last time is already completely send res. received, the FC block
time interface reacts like this:
AG_SEND
No command is accepted until the data transfer has been acknowledged
from the partner via the connection. Until this you receive the message
"Order running" before the CP is able to receive a new command for this
connection.
AG_RECV
The order is acknowledged with the message "No data available yet" as
long as the CP has not received the receive data completely.
AG_SEND, The following illustration shows a possible sequence for the FC blocks
AG_RECV in the together with the organizations and program blocks in the CPU cycle:
user application
CPU cycle
PII read
OB User program
AG_RECV
Communication
AG_RECV
connection
AG_SEND
AG_SEND
Communication
connection
AG_RECV
Communication
connection
AG_SEND
PIQ write
AG_SEND (FC 5) By means of AG_SEND the data to send are transferred to the CP.
Parameter
Parameter Declaration Type Description
ACT Input BOOL Activation of the sender
0: Updates DONE, ERROR and STATUS
1: The data area defined in SEND with the length LEN
is send
ID Input INT Connection number 1 ... 16 (identical with ID of NetPro)
LADDR Input WORD Logical basic address of the CP
(identical with LADDR of NetPro)
SEND Input ANY Data area
LEN Input INT Number of bytes from data area to transfer
DONE Output BOOL Status parameter for the order
0: Order running
1: Order ready without error
ERROR Output BOOL Error message
0: Order running (at DONE = 0)
0: Order ready without error (at DONE = 1)
1: Order ready with error
STATUS Output WORD Status message returned with DONE and ERROR. More
details are to be found in the following table
AG_RECV (FC 6) By means of AG_RECV the data received from the CP are transferred to
the CPU.
Parameter
Parameter Declaration Type Description
ID Input INT Connection number 1 ... 16 (identical with ID of NetPro)
LADDR Input WORD Logical basic address of the CP
(identical with LADDR of NetPro)
RECV Input ANY Data area for the received data
NDR Output BOOL Status parameter for the order
0: Order running
1: Order ready data received without error
ERROR Output BOOL Error message
0: Order running (at NDR = 0)
0: Order ready without error (at NDR = 1)
1: Order ready with error
STATUS Output WORD Status message returned with NDR and ERROR. More
details are to be found in the following table.
LEN Output INT Number of bytes that have been received
DONE, ERROR, The following table shows all messages that can be returned by the CP
STATUS after a SEND res. RECV command.
A "-" means that this message is not available for the concerning SEND
res. RECV command.
Status parameter at At a reboot of the CP, the output parameter are set back as follows:
reboot • DONE = 0
• NDR = 0
• ERROR = 8180h (at AG_RECV)
ERROR = 8181h (at AG_SEND)
Check list for This page shall help you with the error diagnostic. The following page lists
error search a number of typical problems and their probable causes:
Siemens NCM The CP supports the Siemens NCM diagnostic tool. The NCM diagnostic
S7 diagnostic tool is part of the Siemens SIMATIC Manager. This tool delivers
information about the operating state of the communication functions of the
online CPs dynamically.
The following diagnostic functions are available:
• Check operating state at Ethernet
• Read the diagnostic buffer of the CP
• Diagnostic of connections
The following pages contain a short description of the NCM diagnostic.
More details about the function range and for the deployment of the
Siemens NCM diagnostic tool is to be found in the according online help
res. the manual from Siemens.
Start NCM There are two options to start the diagnostic tool:
diagnostic • Via Windows-START menu > SIMATIC ... NCM S7 > Diagnostic
• Within the project engineering res. the hardware configuration via the
register "Diagnostic" in the "Property" dialog with [Execute].
Structure The working surface of the diagnostic tool has the following structure:
The navigation area at the left side contains the hierarchical listed
diagnostic objects. Depending on CP type and configured connections
there is an adjusted object structure in the navigation area.
The information area at the right side always shows the result of the
navigation function you chose in the navigation area.
Read diagnostic The CP has a diagnostic buffer. This has the architecture of a ring memory
buffer and may store up to 100 diagnostic messages. The NCM diagnostic allows
you to monitor and evaluate the CP diagnostic messages via the diagnostic
object Diagnostic buffer.
Via a double click on a diagnostic message the NCM diagnostic shows
further information.
Note!
Please always control the preconditions for an operative communication
using the check at the beginning of this chapter.
• Start diagnostic.
• Open the dialog for the online connection with , enter connection
parameters and establish the online connection with [OK].
• Identify the CP and check the recent state of the CP via module status.
• Check the connections for particularities like:
- Connection status
- Receive status
- Send status
• Control and evaluate the diagnostic buffer of the CP via diagnostic
buffer.
• As needed, alter project engineering res. programming and restart
diagnostic.
ORG format The organization format is the abbreviated description of a data source or a
data destination in a PLC environment. The available ORG formats are
listed in the following table.
The ERW-identifier is used for the addressing of data blocks. In this case
the data block number is entered into this identifier. The start address and
quantity provide the address for the memory area and they are stored in
HIGH-/LOW- format (Motorola-formatted addresses)
Start address DBB-No., from where MB-No., from where IB-No., from where the QB-No., from where
significance the data is retrieved or the data is retrieved or data is retrieved or the data is retrieved or
where the data is where the data is where the data is where the data is
saved. saved. saved. saved.
Note!
Information about the valid range can be found at Chapter "Hardware
description of the CPU".
Start address PB-No., from where the data ZB-No., from where the data TB-No., from where the data
Significance can be retrieved or where it can be retrieved or where it can be retrieved or where it
is saved. is saved. is saved.
DBNOnew
High-Byte Low-Byte
0 X X X X X X X X X X X X X X X
If the highest bit of the ORG identifier is set, the Low-Byte of DBNOnew is
defined via DBNO and the High-Byte of DBNOnew via ORG identifier, where
the highest bit of the ORG identifier is eliminated.
The following formula illustrates this:
Structure of PLC- For every FETCH and WRITE the CP generates PLC header for request
Header and acknowledgment messages. Normally the length of these headers is
16Bytes and have the following structure:
Note!
Please regard that in opposite to Siemens-S5 systems, the block
addressing of these CPUs takes the start address as byte number and the
length as number of words.
Overview This chapter provides an introduction to use the TCP/IP bus system for the
System 300S. The object of this chapter is to create a small
communication system between two VIPA CPUs 31xSN/NET that provides
a simple approach to the control of the communication processes.
Hardware
- 2 CPUs 31xSN/NET from VIPA
- 1 PC or PG with Twisted Pair Ethernet connection
Communication line
- 3 bus cables
- 1 Swich/Hub
Addresses
- 4 IP Addresses and subnet masks for each 2 CPs
Software package
- SIMATIC Manager from Siemens V. 5.1 or higher
- SIMATIC NET
Note!
The complete example is to e found as zip at ftp.vipa.de/support/demofiles.
You may transfer the PLC program directly to both CPUs.
Station 2
Structure Station 1
System 300S System 300S
NetPro
CPU31xS-NET CPU31xS-NET
Twisted Pair
Switch
Station tasks The example for the application is based upon a communication task that is
described in detail in the following passage:
Both of the CPUs contain the same PLC program, only the configuration of
the CPs have to be adjusted.
Both stations are sending and receiving 16 data words per second.
• Data block DB 11 transfers the data bytes DBB 0 to DBB 32 at an
interval of 1s. Data byte DBB 0 in DB 11 is used as message counter. It
is only incremented if the preceding transmit command was processed
correctly (completed without error). The remaining data words (DBB 2 to
DBB 32) can be used for the transfer of user data.
• The receiving station stores the data in DB 12 (DBB 0 to DBB 31).
• Using NetPro an active SEND/RECEIVE connection with ID 1 is to be
configured for the 2nd CP. This Connection is established at station 2 as
a passive SEND/RECEIVE connection.
• The source and destination parameters must be configured directly.
At this point the purpose and the required settings have been outlined. The
programs provide additional details of the configuration of the handler
blocks. A detailed description follows.
Steps of project The project engineering is divided into the following steps:
engineering • Project engineering of the CPU
• Project engineering of the really plugged modules at the standard bus
• Project engineering Ethernet PG/OP channel and CP 343
• Project engineering in NetPro
• PLC user application
• Transfer project
Project The modules at the standard bus at the right side of the CPU are
engineering of the configured like this:
modules at the • Include your System 300V modules at the standard bus in the plugged
standard bus sequence starting with plug-in location 4.
• Parameterize the CPU res. the modules if needed. The parameter
window appears as soon as you double click on the according module.
• For bus extension you may use the IM 360 from Siemens where you
may link-up up to 3 extension racks via the IM 361. Bus extensions may
only be placed at plug-in location 3.
11
Project For the internal Ethernet PG/OP channel that is included in every SPEED7-
engineering of the CPU, you have to place as 1st module below the really plugged modules a
integrated CPs Siemens CP 343-1 (343-1EX11).
The integrated CP 343 of the CPU 31xSN/NET is also configured as CP
343-1 but always below the CP 343-1 placed before. Within "Properties"
type a valid IP address, subnet mask and if needed a gateway for the CPs
and connect them via "Ethernet".
Save and compile your project.
Standard bus
Slot Module
1
CP 343
2 CPU 318-2
X2 DP
X1 MPI/DP
CPU 31xSN/NET DI DO DIO AI AO 3
4
... ...
Ethernet PG/OP
10 343-1EX11
11 343-1EX11
CP 343
Project Create, following the approach above, a hardware configuration for the
engineering of the destination CPU and assign the name "Station 2".
CPU of Station 2 For the CPs, use the IP addresses, subnet masks and gateways assigned
to Station 2.
Save and compile your project.
Project engineering Start NetPro by selecting the CPU below Station 1 and clicking on the
with NetPro object "connections".
In NetPro "Station 1" and "Station 2" are listed together with Ethernet.
Ethernet
Station 1 Station 2
CPU DP MPI CP CP CPU DP MPI CP CP
318-2 343-1 343-1 318-2 343-1 343-1
To configure the connection open the connection list. For this you choose
the CPU of Station 1 and call Insert new connection via the context menu:
Station 1
CPU DP MPI CP CP
318-2 343-1 343-1
A dialog window appears where you can select the connection partner and
the type of the connection.
Configure the following connection:
New connection
Connection: TCP connection
Connection partner: Station 2 > CPU 318-2
PLC user program For the processing of connection commands at the PLC, a PLC user
program is necessary in the concerning CPU. For this only the handling
blocks AG_SEND (FC 5) and AG_RECV (FC 6) are used. By including this
blocks into the cycle block OB1 with the parameters ID and LADDR you
may cyclically send and receive data.
The two FCs are part of the VIPA library that is included in the consignment
of the CPU as CD.
OB 1 Via the cycle OB OB 1 the sending and receiving of the data is controlled.
Cycle The OB1 that you may transfer into both CPUs has the following structure:
CALL "AG_RECV"
ID :=1 // Connection number
LADDR :=W#16#110 // Module address
RECV :=P#DB12.DBX100.0 BYTE 32 //Receive buffer
NDR :=#Newdata // NewDataReceived?
ERROR :=M0.1 // RecError
STATUS:=MW2 // Order res. connection state
LEN :=#Reclen // Really received length
NOP 0 // Reclen can be at IsoOnTCP < 32
U #Newdata // when new data received
ZV Z 1 // Increment Receive counter Counter1
L Z 1 // reset counter 1 at overflow
L 999
==I
R Z 1
Monitoring the It is assumed, that the CPs are programmed and that an overall reset was
data transfer in issued to the CPUs, where the RUN/STOP switch must be located in
the Siemens STOP position.
SIMATIC Manager Now load the above PLC programs into both CPUs and switch them into
RUN.
Start the Siemens STEP7 Manager and execute the following steps to
monitor the transmit job:
• PLC > Monitor/Modify Variables
• In the column "Operand" you have to enter the respective data block
number and the data word (DB11.DBB 0-31).
• Establish a connection and click "monitor" .
Entering User data You may enter user data starting with DBB 2. Place the cursor on modify
value and enter the value you wish to transfer, e.g. W#16#1111.
The button transfers the modify value in every cycle and the button
initiates a single transfer.
Appendix
A Index
CPU 314ST
3
Address assignment................. 5-4
3964R ........................................... 7-4 Analog part ...................... 3-17, 5-5
A Access ................................. 5-6
Conversion........................... 5-8
Addressing.................................... 4-5 deactivate ............................ 5-7
automatically............................. 4-6 Diagnostic functions........... 5-13
Example.................................... 4-7 Diagnostic interrupt............ 5-10
AG_RECV (FC 6) ....................... 8-34 Function No. ...................... 5-11
AG_SEND (FC 5) ....................... 8-34 Measuring cycle ................. 5-10
Application layer............................ 8-5 Number representation ........ 5-7
ASCII ............................................ 7-3 Parameters .......................... 5-9
Assembly ........................2-1, 2-4, 4-2 Pin assignment .................... 5-5
CPU 31xS ..........................2-4, 4-2 Resolution............................ 5-7
Dimensions............................... 2-3 STOP reaction ................... 5-10
Direction.................................... 2-2 Substitute value ................. 5-10
SPEED-Bus .............................. 2-5 Wire break recognition....... 5-10
Deployment .............................. 5-1
B Digital part ..................... 3-18, 5-16
Basics ........................................... 1-1 Access ............................... 5-17
Battery buffer ................................ 4-4 Counter .............................. 5-18
Bit communication layer................ 8-4 Comparison ................. 5-35
Breakpoints................................. 4-31 Comparison value ....... 5-25
Count abort.................. 5-26
Broadcast...........................8-16, 8-31 Count continuously ...... 5-27
Count interrupt............. 5-26
C
Count once .................. 5-28
Cabling.......................................... 2-8 Count periodically ........ 5-30
Front connectors..................... 2-10 Diagnostic interrupt...... 5-40
Edge selection ............. 5-24
Communication
End value..................... 5-25
Layers ....................................... 8-2 Fast introduction .......... 5-18
Overview................................. 3-14 Gate function ............... 5-33
PG/OP .............................4-8, 4-29 Hysteresis........... 5-25, 5-36
RS485..................................... 3-14 Input filter..................... 5-24
Latch function .............. 5-35
Profibus .............................. 3-14
Load value ................... 5-25
PtP ..................................... 3-15 Main counting direction 5-26
Compatibility ................................. 1-8 Mode............................ 5-22
Components ............................... 3-12 Parameter.................... 5-21
Connection Process interrupt ......... 5-39
Pulse............................ 5-25
Combination ........................... 8-16 Value set once............. 5-25
configure................................. 8-26 deactivate .......................... 5-25
Establishment ......................... 8-17 Diagnostic interrupt............ 5-23
Operating modes .................... 8-17 Pin assignment .................. 5-16
Partner .................................... 8-16 In-/Output range ..................... 3-16
specified ................................. 8-16 Overview................................... 5-2
Types ...................................... 8-17 Pin assignment......................... 5-3
unspecified ............................. 8-16 CPU 31xSN/NET
Core cross-section........................ 1-8 Communication
HB140E - CPU - Rev. 07/43 A-1
Index Manual VIPA System 300S SPEED7
M.Stich