VIPA 21x-2BS33 Manual
VIPA 21x-2BS33 Manual
CPU | Manual
HB97E_CPU | RE_21x-2BS33 | Rev. 12/22
June 2012
Copyright © VIPA GmbH. All Rights Reserved.
This document contains proprietary information of VIPA and is not to be disclosed or used except in accordance with applicable
agreements.
This material is protected by the copyright laws. It may not be reproduced, distributed, or altered in any fashion by any entity (either
internal or external to VIPA), except in accordance with applicable agreements, contracts or licensing, without the express written
consent of VIPA and the business management owner of the material.
For permission to reproduce or distribute, please contact:
VIPA, Gesellschaft für Visualisierung und Prozessautomatisierung mbH
Ohmstraße 4, D-91074 Herzogenaurach, Germany
Tel.: +49 (91 32) 744 -0
Fax.: +49 9132 744 1864
EMail: [email protected]
http://www.vipa.com
Note
Every effort has been made to ensure that the information contained in this document was complete and accurate at the time of
publishing. Nevertheless, the authors retain the right to modify the information. This customer document describes all the hardware units
and functions known at the present time. Descriptions may be included for units which are not present at the customer site. The exact
scope of delivery is described in the respective purchase contract.
CE Conformity
Hereby, VIPA GmbH declares that the products and systems are in compliance with the essential requirements and other relevant
provisions of the following directives:
• 2004/108/EC Electromagnetic Compatibility Directive
• 2006/95/EC Low Voltage Directive
Conformity is indicated by the CE marking affixed to the product.
Conformity Information
For more information regarding CE marking and Declaration of Conformity (DoC), please contact your local VIPA customer service
organization.
Trademarks
VIPA, SLIO, System 100V, System 200V, System 300V, System 300S, System 400V, System 500S and Commander Compact are
registered trademarks of VIPA Gesellschaft für Visualisierung und Prozessautomatisierung mbH.
SPEED7 is a registered trademark of profichip GmbH.
SIMATIC, STEP, SINEC, S7-300 and S7-400 are registered trademarks of Siemens AG.
Microsoft und Windows are registered trademarks of Microsoft Inc., USA.
Portable Document Format (PDF) and Postscript are registered trademarks of Adobe Systems, Inc.
All other trademarks, logos and service or product marks specified herein are owned by their respective companies.
Technical support
Contact your local VIPA Customer Service Organization representative if you encounter problems with the product or have questions
regarding the product. If you are unable to locate a customer service center, contact VIPA as follows:
VIPA GmbH, Ohmstraße 4, 91074 Herzogenaurach, Germany
Telephone: +49 9132 744 1150 (Hotline)
EMail: [email protected]
Manual VIPA System 200V Contents
Contents
This manual describes the System 200V CPU 21x-2BS33 from VIPA. Here
you may find every information for commissioning and operation.
Objective and This manual describes the System 200V CPU 21x-2BS33 from VIPA.
contents It contains a description of the construction, project implementation and
usage.
This manual is part of the documentation package with order number
HB97E_CPU and relevant for:
Product Order number as of state:
CPU-HW CPU-FW
21xSER VIPA CPU 21x-2BS33 01 V 4.1.7
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!
Overview The focus of this chapter is on the introduction of the VIPA System 200V.
Here you will find the information required to assemble and wire a controller
system consisting of System 200V components.
Besides the dimensions the general technical data of System 200V will be
found.
Measurements and When you are conducting measurements on electrostatic sensitive modules
alterations on you should take the following precautions:
electrostatic
sensitive modules • Floating instruments must be discharged before use.
• Instruments must be grounded.
Modifying electrostatic sensitive modules you should only use soldering
irons with grounded tips.
Attention!
Personnel and instruments should be grounded when working on
electrostatic sensitive modules.
System conception
R RN
ST 1 1 1 1
S MR
.0 2 .0 2 .0 2 .0 2
MMC .1 3 .1 3 .1 3 .1 3
PW .2 4 .2 4 .2 4 .2 4
SF .3 5 .3 5 .3 5 .3 5
FC .4 6 .4 6 .4 6 .4 6
M
2
MC P .5 7 .5 7 .5 7 .5 7
I
.6 8 .6 8 .6 8 .6 8
.7 9 .7 9 .7 9 .7 9
X1
DC I0 I0 I0 I0
24V + 1
X 2 - 2 X 2 X 2 X 2 X 2
3 4 3 4 3 4 3 4 3 4
VIPA 215-1BA03 VIPA 221-1BF00 VIPA 221-1BF00 VIPA 221-1BF00 VIPA 221-1BF00
DE
D
P
connected periphery modules.
MC I
X1
X1
DC + 1 DC + 1
24V 24V
X 2 - 2 - 2
X 8
3 4 9 10
VIPA 214-1BC03 VIPA 253-1DP00
1
plane bus.
DC 24V
- 2
+ 3
DC 24V
- 4
X 2
3 4
VIPA 207-1BA00
X 2
3 4
VIPA 201-1AA00
Installation Please note that you can only install header modules, like the CPU, the PC
and couplers at slot 1 or 1 and 2 (for double width modules).
1 2 3
[1] Head module
(double width)
[2] Head module
(single width)
4 [3] Periphery module
[4] Guide rails
Note
0 1
A maximum of 32 modules can
be connected at the back plane
bus. Take attention that here the
maximum sum current of 3.5A
is not exceeded.
Please install modules with a
D
P
high current consumption direct-
ly beside the header module.
Clack
Dimensions
Installation
dimensions
80 mm
60 mm
Installed and wired
dimensions
In- / Output 85 mm
84 mm
modules 74 mm
cm
2,77mm
24
76 mm
76,62 mm
88 mm
ca. 110 mm
Function modules/ 89 mm
88 mm
Extension modules 85 mm
84,46 mm
11
4,66mm
mm
27 mm
24
768 mm
cm
CPUs (here with 91mm
89 mm
EasyConn from 85 mm
VIPA)
11 mm
5 mm
mm
27 mm
24
768mm
cm
65 mm
12 cm
125 mm
Installation
General The modules are each installed on a 35mm profile rail and connected via a
bus connector. Before installing the module the bus connector is to be
placed on the profile rail before.
Profile rail For installation the following 35mm profile rails may be used:
35 mm
1,5 mm
35 mm
1 mm
15 mm
7,5 mm
27 mm 27 mm
Bus connector System 200V modules communicate via a backplane bus connector. The
backplane bus connector is isolated and available from VIPA in of 1-, 2-, 4-
or 8tier width.
The following figure shows a 1tier connector and a 4tier connector bus:
The bus connector is to be placed on the profile rail until it clips in its place
and the bus connections look out from the profile rail.
Order number Label Description
290-0AA10 Bus connector 1tier
290-0AA20 Bus connector 2tier
290-0AA40 Bus connector 4tier
290-0AA80 Bus connector 8tier
Installation on a The following figure shows the installation of a 4tier width bus connector in
profile rail a profile rail and the slots for the modules.
The different slots are defined by guide rails.
1 2 3
[1] Header module
(double width)
[2] Header module
(single width)
[3] Peripheral module
[4] Guide rails
PW
ER
RD
BA
ADR. 0 1
DC24V
+ 1
- 2
R
S
MMC
PW
SF
FC
MC
Assembly
possibilities
hoizontal assembly vertical Please regard the allowed environmental temperatures:
assembly
• horizontal assembly: from 0 to 60°C
• vertical assembly: from 0 to 40°C
• lying assembly:
0 1
from 0 to 40°C
lying assembly The horizontal assembly always starts at the left side with
a header module, then you install the peripheral modules
beside to the right.
You may install up to 32 peripheral modules.
0 1
any modules!
• Make sure that a clearance of at least 60mm exists
above and 80mm below the middle of the profile rail.
60 mm
Note!
A maximum of 32 modules can be connected at the back plane bus. Take
attention that here the maximum sum current of 3.5A is not exceeded.
Assembly
procedure
• Install the profile rail. Make sure that a clearance of at least 60mm
exists above and 80mm below the middle of the profile rail.
• Press the bus connector into the profile rail until it clips securely into
place and the bus-connectors look out from the profile rail. This
provides the basis for the installation of your modules.
• Start at the outer left location with the installation of your header
module and install the peripheral modules to the right of this.
1 2 3 [1] Header module
(double width)
[2] Header module
(single width)
[3] Peripheral module
[4] Guide rails
4
• Insert the module that you are installing into the profile rail at an angle
of 45 degrees from the top and rotate the module into place until it
clicks into the profile rail with an audible click. The proper connection
to the backplane bus can only be guaranteed when the module has
properly clicked into place.
Attention!
Power must be turned off before modules are
installed or removed!
Clack
Attention!
Power must be turned off before modules are installed or
removed!
Please regard that the backplane bus is interrupted at the point
where the module was removed!
Wiring
Overview Most peripheral modules are equipped with a 10pole or a 18pole connector.
This connector provides the electrical interface for the signaling and supply
lines of the modules.
The modules carry spring-clip connectors for interconnections and wiring.
The spring-clip connector technology simplifies the wiring requirements for
signaling and power cables.
In contrast to screw terminal connections, spring-clip wiring is vibration
proof. The assignment of the terminals is contained in the description of the
respective modules.
You may connect conductors with a diameter from 0.08mm2 up to 2.5mm2
(max. 1.5mm2 for 18pole connectors).
The following figure shows a module with a 10pole connector.
Note!
The spring-clip is destroyed if you push the screwdriver into the wire port!
Make sure that you only insert the screwdriver into the square hole of the
connector!
Wiring procedure
• Install the connector on the module until it locks with an audible click.
For this purpose you press the two clips together as shown.
The connector is now in a permanent position and can easily be wired.
The following section shows the wiring procedure from top view.
• Insert the stripped end of the wire into the round opening. You can use
wires with a diameter of 0.08mm2 to 2.5mm2
(1.5mm2 for 18pole connectors).
• By removing the screwdriver the wire is connected safely with the plug
connector via a spring.
Note!
Wire the power supply connections first followed by the signal cables
(inputs and outputs).
Installation guidelines
General The installation guidelines contain information about the interference free
deployment of System 200V 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.
What means EMC? Electromagnetic digestibility (EMC) means the ability of an electrical device,
to function error free in an electromagnetic environment without being
interferenced res. without interferencing the environment.
All System 200V components are developed for the deployment in hard
industrial environments and fulfill high demands on the EMC. Nevertheless
you should project an EMC planning before installing the components and
take conceivable interference causes into account.
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 an 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 metalized plug cases for isolated data lines.
• In special use cases you should appoint special EMC actions.
- Wire all inductivities with erase links.
- Please consider luminescent lamps can influence signal lines.
• Create a 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 200V 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.
General data
Overview Here the hardware components of the CPU are described. The technical
data are at the end of the chapter.
Properties
R RN R RN
ST ST
S MR S MR
MMC MMC
PW PW
Rx SF Rx SF
Tx C FC Tx C FC
O M O M
2 2
M MC P M MC P
I I
X1 X1
DC DC
24V + 1 24V + 1
X 2
3 4
- 2 X 2
3 4
- 2
VIPA 214-2BS33 VIPA 215-2BS33
Structure
COM MP 2 I
Interfaces RS485
1 n. c. 1 reserved
5
2 n. c. 5
2 M24V
9 3 RxD/TxD-P (line B) 9 3 RxD/TxD-P (line B)
4 4
8
4 RTS 8
4 RTS
3 5 M5V 3 5 M5V
7 7
2
6 P5V 2
6 P5V
6 7 n. c. 6 7 P24V
1 1
8 RxD/TxD-N (line A) 8 RxD/TxD-N (line A)
9 n.c. 9 n.c.
X1
+ 1 + DC 24 V
- 2 0V
Power supply The CPU has an internal power supply. This is connected to an external
supply voltage via two terminals located on the front of the unit.
The power supply requires DC 24V (20.4 ... 28.8V). In addition to the
electronic circuitry of the CPU this supply voltage is used for the modules
connected to the backplane bus.
The electronic circuitry of the CPU is not dc-insulated from the supply
voltage. The power supply is protected against reverse polarity and short
circuits.
Note!
Please ensure that the polarity of the supply voltage is correct.
MP2I interface The MPI unit provides the link for the data transfer between the CPU and
the PC. Via bus communication you are able to exchange programs and
data between different CPUs that are linked over MPI.
For a serial exchange between the partners you normally need a special
MPI-converter. But now you are also able to use the VIPA "Green Cable"
(Order-No. VIPA 950-0KB00), which allows you to establish a serial peer-
to-peer connection over the MPI interface.
Please regard the "Hints for the deployment of the MPI interface" in chapter
"Deployment CPU 21x".
RS485 interface Additional to the components described before, the CPU has a RS485
interface.
Via the 9pin interface you may establish a serial RS485 bus connection
Note!
More information about the serial communication may be found in the
chapter "Serial communication".
Memory The CPUs have an integrated work and a load memory. The memories are
management battery-buffered.
In the load memory there are program code and blocks stored together with
the header information.
The program parts and blocks, which are relevant for the running program,
are loaded to the work memory during the program sequence.
Operating mode With the operating mode switch you may switch the CPU between STOP
switch and RUN.
During the transition from STOP to RUN the operating mode START-UP is
driven by the CPU.
RN
ST By Switching to MR (Memory Reset) you request an overall reset with
MR
following load from MMC, if a project there exists.
MMC slot You may install a VIPA MMC memory card in this slot as external storage
memory card device (Order No.: VIPA 953-0KX10).
The access to the MMC takes always place after an overall reset.
Battery backup for A rechargeable battery is installed on every CPU 21x to safeguard the
clock and RAM contents of the RAM when power is removed. This battery is also used to
buffer the internal clock.
The rechargeable battery is maintained by a charging circuit that receives
its power from the internal power supply and that maintain the clock and
RAM for a max. period of 30 days.
Attention!
Please connect the CPU at least for 24 hours to the power supply, so that
the internal accumulator/battery is loaded accordingly.
After a power reset and with an empty battery the CPU starts with a BAT
error and executes an overall reset.
The BAT error can be deleted again, if once during power cycle the time
between switching on and off the power supply is at least 30sec. and the
battery is fully loaded.
Otherwise with a short power cycle the BAT error still exists and an overall
reset is executed.
LEDs CPU The CPU has got LEDs on its front side. In the following the usage and the
according colors of the LEDs is described.
LEDs RS485 The LEDs of the RS485 interface are located in the left half of the front
panel and they are used for diagnostic purposes. The following table shows
the color and the significance of these LEDs.
Technical Data
Type COM
Type of interface RS485
Connector Sub-D, 9-pin, female
Electrically isolated 9
MPI -
MP²I (MPI/RS232) -
DP master -
DP slave -
Point-to-point interface 9
CAN -
Type COM
Type of interface RS485
Connector Sub-D, 9-pin, female
Electrically isolated 9
MPI -
MP²I (MPI/RS232) -
DP master -
DP slave -
Point-to-point interface 9
CAN -
Type -
Type of interface -
HB97E - CPU - RE_21x-2BS33 - Rev. 12/22 2-11
Chapter 2 Hardware description Manual VIPA System 200V
Overview This chapter describes the deployment of the CPU in the System 200V.
The description refers directly to the CPU and to the deployment in
connection with peripheral modules, mounted on a profile rail together with
the CPU at the backplane bus.
Assembly
Note!
Information about assembly and cabling may be found at chapter "Basics
and Assembly".
Start-up behavior
Turn on power When the CPU is delivered it has been reset. After the power supply has
supply been switched on, the CPU changes to the operating mode the operating
mode lever shows. After a STOP→RUN transition the CPU switches to
RUN without program.
Note!
Please connect the CPU at least for 24 hours to the power supply, so that
the internal accumulator/battery is loaded accordingly.
Boot procedure with The CPU switches to RUN with the program stored in the battery buffered
valid data in the RAM.
CPU
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.
Depending on the position of the operating mode switch, the CPU switches
to RUN res. remains in STOP.
This event is stored in the diagnostic buffer as: "Start overall reset
automatically (unbuffered PowerON)".
Attention!
After a power reset and with an empty battery the CPU starts with a BAT
error and executes an overall reset.
The BAT error can be deleted again, if once during power cycle the time
between switching on and off the power supply is at least 30sec. and the
battery is fully loaded.
Otherwise with a short power cycle the BAT error still exists and an overall
reset is executed.
Addressing
Signaling states in The signaling states of the lower addresses (0 ... 127) are additionally
the process image saved in a special memory area called the process image.
The process image is divided into two parts:
• process image of the inputs (PII)
• process image of the outputs (PIQ)
Read/write access You may access the modules by means of read or write operations on the
peripheral bytes or on the process image.
Note!
Please remember that you may access different modules by means of read
and write operations on the same address.
The addressing ranges of digital and analog modules are different when
they are addressed automatically.
Digital modules: 0 ... 127
Analog modules: 128 ... 1023
Example for auto- The following figure illustrates the automatic allocation of addresses:
matic address
allocation
Slot: 1 2 3 4 5 6
DIO 8xDC24V
DO 8xDC24V
DI 16xDC24V
DI 8xDC24V
AO 4x12Bit
AI 4x12Bit
CPU 21x
PII rel. Addr. Peripheral area Peripheral area rel. Addr PIQ
0 Input byte 0 Output byte 0 0
. . . .
. . . .
. . . .
analog digital
128 Input byte 0 Output byte 0 128
. .
. .. .. .. .
. . .
. .
135 Input byte 7 Output byte 7 135
Modifying allocated You may change the allocated addresses at any time by means of the
addresses by Siemens SIMATIC manager. In this way you may also change the addres-
configuration ses of analog modules to the range covered by the process image
(0 ... 127) and address digital modules above 127.
The following pages describe the required preparations and the procedure
for this type of configuration.
Deployment as The MP interface provides the data transfer between CPUs and PCs. In a
MP 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.
Overview For the project engineering of the CPU 21x and the other System 200V
modules connected to the same VIPA bus, the hardware configurator from
Siemens is to be used.
To address the directly plugged peripheral modules, you have to assign a
special address in the CPU to every module.
The address allocation and the parameterization of the modules takes
place in the Siemens SIMATIC manager as a virtual PROFIBUS system.
For the PROFIBUS interface is standardized software sided, the
functionality is guaranteed by including a GSD-file into the Siemens
SIMATIC manager.
Transfer your project into the CPU via the MPI interface.
Note!
The configuration of the CPU requires a thorough knowledge of the
Siemens SIMATIC manager and the hardware configurator!
Including the • Go to www.vipa.com > Service > Download > GSD- und EDS-Files >
GSD-file PROFIBUS and download the file Cx000023_Vxxx.
• Extract the file to your work directory. The vipa_21x.gsd (German)
respectively vipa_21x.gse (English) can be found at the directory
VIPA_System_200V.
• Start the Siemens hardware configurator and close every project.
• Go to Options > Install new GSD file
• Navigate to the directory System_200V and choose the corresponding
file vipa_cpu21x.gsd (German) or vipa_cpu21x.gse (English)
Now the modules of the VIPA System 200V are integrated in the hardware
catalog at PROFIBUS-DP \ Additional field devices \ I/O \
VIPA_System_200V.
Proceeding To be compatible with the Siemens SIMATIC manager the following steps
should be executed:
R
S
RN
MR
MMC
ST
Hardware After the hardware configuration of the CPU place the System 200V
configuration of modules in the plugged sequence.
the modules In order to address the installed peripheral modules individually, specific
addresses in the CPU have to be assigned to them.
Slot Module
1
2 CPU 315-2DP PROFIBUS (1): DP master system (1)
X2 DP
3
R
S
RN
MR
MMC
ST
PW
SF
FC 2
MC
DIO 8xDC24V
DO 8xDC24V
DI 8xDC24V
Parameter DIO
AO 4x12Bit
AI 4x12Bit
Parameterization For parameterization 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 for
during runtime 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.
Parameterization Since the CPU from VIPA is to be configured as Siemens CPU 315-2DP
via Siemens (315-2AF03 0AB00 V1.2) in the Siemens hardware configurator, the
CPU 315-2AF03 parameters of the VIPA CPU may be set with "Object properties" of the
CPU 315-2DP during hardware configuration.
Via a double-click on the CPU 315-2DP the parameter window of the CPU
may be accessed.
Using the registers you get access to every standard parameter of the
CPU.
Parameter CPU
(1) VIPA_CPU
CPU 214
CPU 21x
RN
R ST
S MR
MMC
PW
SF
FC 2
MC
Supported The CPU does not evaluate each parameter, which may be set at the
parameters hardware configuration.
The following parameters are supported by the CPU at this time:
General
Short description The short description of the Siemens CPU 315-2AF03 is CPU 315-2DP.
Order No. / Order number and firmware are identical to the details in the "hardware
Firmware catalog" window.
Name The Name field provides the short description of the CPU. If you change
the name the new name appears in the Siemens SIMATIC manager.
Startup
Startup when If the checkbox for "Startup when expected/actual configuration differ" is
expected/actual deselected and at least one module is not located at its configured slot or if
configuration differs another type of module is inserted there instead, then the CPU does not
switch to RUN mode and remains in STOP mode.
If the checkbox for "Startup when expected/actual configuration differ" is
selected, then the CPU starts even if there are modules not located in their
configured slots of if another type of module is inserted there instead, such
as during an initial system start-up.
HB97E - CPU - RE_21x-2BS33 - Rev. 12/22 3-9
Chapter 3 Deployment CPU 21x-2BS33 Manual VIPA System 200V
Monitoring time for This operation specifies the maximum time for the ready message of every
ready message by configured module after PowerON. Here connected PROFIBUS DP slaves
modules [100ms] are also considered until they are parameterized. If the modules do not
send a ready message to the CPU by the time the monitoring time has
expired, the actual configuration becomes unequal to the preset
configuration.
Monitoring time for The maximum time for the transfer of parameters to parameterizable
transfer of modules. If not every module has been assigned parameters by the time
parameters to this monitoring time has expired; the actual configuration becomes unequal
modules [100ms] to the preset configuration.
Cycle/Clock
memory
Update OB1 This parameter is not relevant.
process image
cyclically
Scan cycle Here the scan cycle monitoring time in milliseconds may be set. If the scan
monitoring time cycle time exceeds the scan cycle monitoring time, the CPU enters the
STOP mode. Possible reasons for exceeding the time are:
• Communication processes
• a series of interrupt events
• an error in the CPU program
Scan cycle load Using this parameter you can control the duration of communication
from Communi- processes, which always extend the scan cycle time so it does not exceed
cation a specified length.
If the cycle load from communication is set to 50%, the scan cycle time of
OB 1 can be doubled. At the same time, the scan cycle time of OB 1 is still
being influenced by asynchronous events (e.g. hardware interrupts) as well.
OB85 call up at I/O The preset reaction of the CPU may be changed to an I/O access error that
access error occurs during the update of the process image by the system.
The VIPA CPU is preset such that OB 85 is not called if an I/O access error
occurs and no entry is made in the diagnostic buffer either.
Clock memory Activate the check box if you want to use clock memory and enter the
number of the memory byte.
Note!
The selected memory byte cannot be used for temporary data storage.
Retentive Memory
Number of Memory Enter the number of retentive memory bytes from memory byte 0 onwards.
Bytes from MB0
Number of S7 Enter the number of retentive S7 timers from T0 onwards. Each S7 timer
Timers from T0 occupies 2bytes.
Interrupts
Priority Here the priorities are displayed, according to which the hardware interrupt
OBs are processed (hardware interrupt, time-delay interrupt, async. error
interrupts).
Time-of-day
interrupts
Priority Here the priorities may be specified according to which the time-of-day
interrupt is processed.
With priority "0" the corresponding OB is deactivated.
Active Activate the check box of the time-of-day interrupt OBs if these are to be
automatically started on complete restart.
Execution Select how often the interrupts are to be triggered. Intervals ranging from
every minute to yearly are available. The intervals apply to the settings
made for start date and time.
Start date / time Enter date and time of the first execution of the time-of-day interrupt.
Cyclic interrupts
Priority Here the priorities may be specified according to which the corresponding
cyclic interrupt is processed. With priority "0" the corresponding interrupt is
deactivated.
Execution Enter the time intervals in ms, in which the watchdog interrupt OBs should
be processed. The start time for the clock is when the operating mode
switch is moved from STOP to RUN.
Phase offset Enter the delay time in ms for current execution for the watch dog interrupt.
This should be performed if several watchdog interrupts are enabled.
Phase offset allows to distribute processing time for watchdog interrupts
across the cycle.
Protection
Level of protection Here 1 of 3 protection levels may be set to protect the CPU from
unauthorized access.
Protection level 1 (default setting):
• No password adjustable, no restrictions
Protection level 2 with password:
• Authorized users: read and write access
• Unauthorized user: read access only
Protection level 3:
• Authorized users: read and write access
• Unauthorized user: no read and write access
Project transfer
Overview There are the following possibilities for project transfer into the CPU:
• Transfer via MPI
• Transfer via MMC when using a MMC programmer
Transfer via MPI The structure of a MPI net is electrically identical with the structure of a
PROFIBUS net. This means 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. Per default
the MPI net runs with 187.5kbaud. VIPA CPUs are delivered with MPI
address 2.
MPI programming The MPI programming cables are available at VIPA in different variants.
cable The cables provide a RS232 res. USB plug for the PC and a bus enabled
RS485 plug for the CPU.
Due to the RS485 connection you may plug the MPI programming cables
directly to an already plugged plug on the RS485 jack. Every bus
participant identifies itself at the bus with an unique address, in the course
of the address 0 is reserved for programming devices.
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 power supplied. Otherwise it may cause interferences
on the bus.
Transfer with MPI programming cable (MPI communication)
STEP7
from Siemens
VIPA
USB -MPI Ad apter
MPI
Error
Active
Power
MPI net
Green Cable
Configure MPI Hints for configuring a MPI interface are to find in the documentation of
your programming software.
The "Green Cable" has the order number VIPA 950-0KB00.
Attention!
Please regard, that you may use the "Green Cable" exclusively at VIPA
CPUs with MP2I-interface!
Please regard the hints for deploying the Green Cable and the MP2I jack!
Approach transfer • Connect your PC to the MPI jack of your CPU via a MPI programming
via MPI interface 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].
• Set in the register MPI the transfer parameters of your MPI net and type
a valid address.
• Switch to the register Local connection
• Set the COM port of the PC and the transfer rate 38400Baud for the MPI
programming cable from VIPA.
• Via PLC > Load to module you may transfer your project via MPI to the
CPU and save it on a MMC via PLC > Copy RAM to ROM if one is
plugged.
Note!
Please make sure to adjust the transfer rate to 38400Baud when using the
"Green Cable" from VIPA.
Hints for 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
MP2I jack and VIPA field bus masters. The Green Cable from VIPA is
available under the order no. VIPA 950-0KB00.
Transfer via The MMC (Memory Card) serves as external transfer and storage medium.
MMC There may be stored several projects and sub-directories on a MMC
storage module. Please regard that your current project is stored in the root
directory and has one of the following file names:
• S7PROG.WLD
• AUTOLOAD.WLD
With File > Memory Card File > New in the Siemens SIMATIC manager a
new wld file may be created. After the creation copy the blocks from the
project blocks folder and the System data into the wld file.
Transfer The transfer of the application program from the MMC into the CPU takes
MMC → CPU place depending on the file name after an overall reset or PowerON.
• S7PROG.WLD is read from the MMC after overall reset and transferred
into the battery buffered RAM and additionally into the Flash memory. .
• AUTOLOAD.WLD is read after PowerON from the MMC and transferred
into the battery-buffered RAM .
During the transfer the "MC" LED blinks. Please regard that your user
memory serves for enough space, otherwise your user program is not
completely loaded and the SF LED gets on. Execute a compression before
the transfer, for this does not happen automatically.
Transfer When the MMC has been installed, the write command stores the content
CPU → MMC of the battery buffered RAM as S7PROG.WLD on the MMC.
The write command is controlled by means of the block area of the
Siemens SIMATIC manager PLC > Copy RAM to ROM. During the write
process the "MC"-LED of the CPU is blinking. When the LED expires the
write process is finished.
If this project is to be loaded automatically from the MMC with PowerON,
you have to rename this on the MMC to AUTOLOAD.WLD.
Transfer control After a MMC access, an ID 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.
When accessing a 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
0xE300 Internal Flash writing finished
0xE310 Internal Flash reading finished (reload after battery failure)
Operating modes
Operating mode • During the transition from STOP to RUN the system calls the start-up
START-UP organization block OB 100. 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 as soon as the OB 100 is operated and for at least
3s, even if the start-up time is shorter or the CPU gets to
STOP due to an error. This indicates the start-up.
• STOP-LED off
When the CPU has completed the start-up OB, it assumes the operating
mode RUN.
Function security The CPUs include security mechanisms like a watchdog (100ms) and a
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:
Firmware update
Overview There is the opportunity to execute a firmware update for the CPU and its
components 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 file
name is reserved for each updateable component (see table below).
After PowerON and CPU STOP the CPU checks if there is a firmware file
on the MMC. If this firmware version is different to the existing firmware
version, this is indicated by blinking of the LEDs and the firmware may be
installed by an update request.
Latest Firmware at The latest firmware versions are to be found in the service area at
www.vipa.com www.vipa.com
Find out CPU A label on the rear of the module indicates the firmware version.
firmware version You may display the current firmware version of your CPU via the Siemens
SIMATIC manager. To display the firmware version, you go online with the
CPU via your PG or PC and start the Siemens SIMATIC manager.
Via PLC > Module status, register "General", the current firmware version is
evaluated and displayed.
Reserved file By means of a reserved file name in the CPU 21x-2BS33 you may transfer
names a firmware per MMC:
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.
Transfer firmware 1. Switch the operating mode switch of your CPU in position ST. Turn off
from MMC into the 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 FC
shows that at least a differing firmware file was found on the MMC.
3. You start the transfer of the firmware as soon as you tip the operating
mode switch lever downwards to MR within 10s and leave it in ST
position.
4. During the update process, the LEDs SF and FC are alternately blinking
and MC LED is on. This may last several minutes.
5. The update is successful finished when the LEDs PW, S, SF, FC and
MC 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 FC 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
PW PW PW PW PW PW
Tip RN RN
SF SF SF SF SF SF
MMC stecken ST
FC FC ST FC FC FC FC Power
MC MC MR MR MC MC MC MC OFF/ON
Power OFF/ON 10 Sec.
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 MPI address is reset to the address 2!
1 2 3 4 5
R R R R R
S S S S S
PW
Tip RN
PW
6x PW
RN Tip RN
PW PW
SF SF SF SF SF
ST ST ST
FC FC FC FC FC Power
MC MR MC MC MR MR MC MC OFF/ON
30 Sec. 1 Sec.
Note!
After the firmware update you always should execute a Factory reset.
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.
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:
Module information
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)
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:
I, Q, M, T, C and D.
The process image of binary and digital operands is modified independently
of the operating mode of the CPU.
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.
Overview Content of this chapter is the usage of the serial RS485 interface of the
CPU. Here you’ll find all information about the deployment of the serial
interfaces of the CPU.
Fast introduction
General The CPU 21xSER provides serial interfacing facilities between the
processes of different source and destination systems. For the serial
communication the CPU 21x-2BS33 has got a RS485 interface.
Protocols The CPU supports the ASCII, STX/ETX, 3964R, USS and Modbus
protocols and procedures.
Parameterization The parameterization happens during runtime by means of the SFC 216
(SER_CFG). The parameters for STX/ETX, 3964R, USS and Modbus have
to be stored in a DB.
Communication With the help of SFCs you control the communication. The sending is
executed with the SFC 217 (SER_SND) and the reception via SFC 218
(SER_RCV).
Another call of the SFC 217 SER_SND, 3964R, USS and Modbus provides
you via RetVal with a return value which contains among others recent
information about the acknowledgement of the partner.
The protocols USS and Modbus allows you to read the acknowledgement
telegram by calling the SFC 218 SER_RCV after a SER_SND.
The SFCs are included in the consignment of the CPU 21xSER.
Overview over the The following SFCs are deployed for the serial communication:
SFCs for the serial
communication
SFC Description
SFC 216 SER_CFG Parameterization of the serial interface
SFC 217 SER_SND Send via serial interface
SFC 218 SER_RCV Receive via serial interface
SFC 207 SER_CTRL Modem functionality
Overview The CPU 21xSER 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 be found at the service area at www.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 on the byte width the following ASCII characters can be
transferred: 5Bit: not allowed: 6Bit: 20...3Fh, 7Bit: 20...7Fh, 8Bit: 20...FFh.
The user data which includes all the characters between Start and End are
transferred to the CPU when the End has been received.
When data is send from the CPU 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:
STX1 STX2 Z1 Z2 Zn ETX1 ETX2
ZVZ
3964R The 3964R procedure controls the data transfer of a point-to-point link
between the CPU 21xSER 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
ignored. 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.
7 6 5 4 3 2 1 0
1
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.
Overview The CPU 21x-2BS33 has a RS485 interface. The interface is described in
the following.
RS485 • Logical states represented by voltage differences between the two cores
interface 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
4 RTS Periphery
7 n.c.
8 RxD/TxD-N (Line A) Periphery
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 2x256Byte and then put out via
the interface.
When the interface receives data, this is stored in a FIFO receive buffer
with a size of 2x256Byte and can there be read by the PLC.
If the data is transferred via a protocol, the adaption of the data to the
according protocol happens automatically.
In opposite to ASCII and STX/ETX, the protocols 3964R, USS and Modbus
master 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 master after a SER_SND the
acknowledgement telegram must be evaluated by call of the SFC 218
SER_RCV.
CPU 21xSER
Program Protocol FIFO buffer Interface
IN RS485
SER_RCV RECEIVE 256byte
SFC 218
256byte
SER_CFG
CFG
SFC 216 OUT
256byte
SER_SND
SFC 217 SEND 256byte
Principles for Data that the CPU has to provide for the Modbus master are stored in a
Modbus Slave FIFO send buffer (first in first out) with a size of 2x256Byte. In opposite to
the other protocols the data remain in the send buffer until they are reques-
ted by the Modbus master via a read command (function code 01h, 03h).
If the interface receives data from the master (function code 05h, 06h, 10h)
these are stored in a FIFO receive buffer with a size of 2x256Byte and may
there be read by the CPU.
The embedding of the data into the Modbus protocol happens
automatically.
Please regard that the Modbus master may access the IN res. OUT buffer
by according presetting of the read function code. By means of a read
access to the IN buffer (function code 02h, 04h) the master may read data
that it has sent to the Modbus slave before. The data remain in the buffer
until they are overwritten by the Modbus master.
The following picture shows the communication principle. More information
is also to be found in the chapter "Modbus slave function codes" further
below.
CPU 21xSER
Program Protocol FIFO Buffer Interface
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.
Please regard that not all protocols support the complete value range of the
parameters. More detailed information is to be found in the description of
the according parameter.
Note!
Please regard that the SFC 216 is not called again during a communication
because as a result of this all buffers are cleared.
If you don’t want to alter the communication parameter any more, you
should place the call of the SFC 216 in the start-up OB OB 100.
Parameters
Name Declaration Type Description
PROTOCOL IN BYTE Number of the protocol
PARAMETER IN ANY Pointer to protocol-parameters
BAUDRATE IN BYTE No of baudrate
CHARLEN IN BYTE Number of Data bits
PARITY IN BYTE Parity
STOPBITS IN BYTE Number of stop bits
FLOWCONTROL IN BYTE Flow control (1 fixed)
RETVAL OUT WORD Return value ( 0 = OK )
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
7: Modbus RTU Slave
8: Modbus ASCII Slave
Note!
The start res. end sign should always be a value <20, otherwise the sign is
ignored!
With not used IDs please always enter FFh!
Supported values:
Bit ASCII STX/ETX 3964R USS Modbus RTU Modbus ASCII
5 x x
6 x x x
7 x x x x
8 x x x x x x
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
1.5Bit can only be used with CHARLEN 5 at this number of data 2Bit is not
allowed.
FLOWCONTROL With this bit you affect the behavior from signal Request to send.
0: RTS off
1: RTS is "0" at Receive (AutoRTS)
RTS is "1" at Send (AutoRTS)
2: HW flow (only at ASCII protocols)
Note!
Note: For RS485 FLOWCONTROL is not evaluated.
It is set automatically to "1" (AutoRTS)!
Communication
Overview The communication happens via the send and receive blocks SFC 217
(SER_SND) and SFC 218 (SER_RCV).
If data is transferred by means of a protocol, the embedding of the data into
the according protocol happens automatically. Depending on the protocol
you have to regard the following aspects
ASCII With ASCII res. STX/ETX the sending of the data happens without
STX/ETX acknowledgement of the partner.
3964R Another call of the SFC 217 SER_SND provides you via RetVal with a
return value which contains among others recent information about the
acknowledgement of the partner.
Modbus master Sending happens with acknowledgement of the partner. Another call of the
USS SFC 217 SER_SND provides you via RetVal with a return value which
contains among others recent information about the acknowledgement of
the partner. After the transfer with SER_Send you receive the
acknowledgement telegram of the partner by calling the SFC 218
SER_RCV.
Note!
Please regard that the SFC 216 is not called again during a communication
because as a result of this all buffers are cleared.
SFC 217 This block allows to send data via the serial interface.
(SER_SND)
Parameters
Name Declaration Type Description
DATAPTR IN ANY Pointer to Data Buffer for sending data
DATALEN OUT WORD Length of data to send
RETVAL OUT WORD Return value (0 = OK)
DATAPTR Here you define a range of the type Pointer for the send buffer where the
data that has to be sent 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 (>256Byte)
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 (>256Byte)
9002h Data too short (0Byte)
USS
Value Description
2000h Send ready without error
8080h Receive buffer overflow (no space for receipt)
8090h Acknowledgement delay time exceeded
80F0h Wrong checksum in respond
80FEh Wrong start sign in respond
80FFh Wrong slave address in respond
9000h Buffer overflow (no data send)
9001h Data too long (>256Byte)
9002h Data too short (<2Byte)
Principles of The following text shortly illustrates the structure of programming a send
programming command for the different protocols.
RetVal 700xh ? J
Busy ? J
N
N
RetVal 8xxxh /
J Error evaluation End
RetVal 8xxxh / 90xxh ?
J
90xxh ?
N
N
Error evaluation
SFC 218
RetVal 2001h ? J Error evaluation End
SER_RCV
RetVal 2001h ? J
End N
SFC 218
RetVal 2000h ? J Data evaluation End
SER_RCV
RetVal 2000h ? J
N Ende
N
Data evaluation
End
SFC 217
SER_SND
RetVal 900xh J
Error evaluation
N RetVal 700xh ? J
End
SFC 218
RetVal 0000h ? J
SER_RCV
SFC 218 This block receives data via the serial interface.
(SER_RCV)
Parameters
Name Declaration Type Description
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 Return value ( 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 At ASCII, this word gets an entry in case of an error. The following error
messages are possible:
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
Range definitions Normally the access under Modbus happens by means of the ranges 0x,
1x, 3x and 4x.
0x and 1x gives you access to digital bit areas and 3x and 4x to analog
word areas.
For the CPU 21xSER from VIPA is not differentiating digital and analog
data, the following assignment is valid:
1x0001
1x0002 1x0022
1x0003
IN
3x0001 3x0002 3x0003
0x0001
0x0002 0x0022
0x0003
OUT
4x0001 4x0002 4x0003
Overview With the following Modbus function codes a Modbus master can access a
Modbus slave. The description always takes place from the point of view of
the master:
Point of View of The description always takes place from the point of view of the master.
"Input" and Here data, which were sent from master to slave, up to their target are
"Output" data designated as "output" data (OUT) and contrary slave data received by the
master were designated as "input" data (IN).
Write to master If you "OR" the FC 0 parameter ANZ with 4000h the slave data to send
output area were not transferred to the master input area but to the master output area.
Since this area can be read by the master by means of function codes this
functionality can be used for example for the direct error transmission to the
master.
Respond of the If the slave announces an error, the function code is send back with an
slave "ORed" 80h. Without an error, the function code is sent back.
Coupler answer: Function code OR 80h → Error
Function code → OK
Byte sequence For the Byte sequence in a word is always valid: 1 Word
in a word High Low
Byte Byte
Command telegram
RTU/ASCII Slave Function Address Number of RTU/ASCII
frame address code 1. Bit Bits frame
1Byte 1Byte 1Word 1Word 1Word
Respond telegram
RTU/ASCII Slave Function Number of Data Data ... RTU/ASCII
frame address code read Bytes 1. Byte 2. Byte frame
1Byte 1Byte 1Byte 1Byte 1Byte 1Word
max. 252Byte
Command telegram
RTU/ASCII- Slave- Functions Address Number of RTU/ASCII
frame address code 1. Word words frame
1Byte 1Byte 1Word 1Word 1Word
Respond telegram
RTU/ASCII Slave Functions No. of read Data Data RTU/ASCII
frame address code Bytes 1. Word 2. Word ... frame
1Byte 1Byte 1Byte 1Word 1Word 1Word
max. 125 Words
Command telegram
RTU/ASCII Slave Function Address Status RTU/ASCII
frame address code Bit Bit frame
1Byte 1Byte 1Word 1Word 1Word
Respond telegram
RTU/ASCII Slave Function Address Status RTU/ASCII
frame address code Bit Bit frame
1Byte 1Byte 1Word 1Word 1Word
Command telegram
RTU/ASCII Slave Function Address Value RTU/ASCII
frame address code Word Word frame
1Byte 1Byte 1Word 1Word
Respond telegram
RTU/ASCII Slave Function Address Value RTU/ASCII
frame address code Word Word frame
1Byte 1Byte 1Word 1Word
Command telegram
RTU/ASCII Slave Functions Address Number Number of Data Data RTU/ASCII
frame address code 1. Word of words Bytes 1. Word 2. Word ... frame
1Byte 1Byte 1Word 1Word 1Byte 1Word 1Word 1Word 1Word
max. 124Words
Respond telegram
RTU/ASCII Slave Functions Address Number of RTU/ASCII
frame address code 1. Word words frame
1Byte 1Byte 1Word 1Word 1Word
M: CPU 21xSER The following components are required for this example:
S: CPU 21xSER • 2 CPU 21xSER as Modbus RTU master res. Modbus RTU slave
• Siemens SIMATIC manager and possibilities for the project transfer
• Modbus cable connection
The following page shows the structure for the according PLC programs for
master and slave.
Master Slave
OB100:
Start Start
N
N
OB1:
SFC 217
SER_SND
(mit Slave-Nr., Code,
Bereich) SFC 217
SER_SND
RetVal 700xh? J
RetVal 8xxxh /
J Error evaluation
90xxh ?
RetVal 0000h ? J
N
RetVal 2001h ? J
N
SFC 218
SER_RCV
N N
RetVal 0000h ? J
N
RetVal 8xxxh ? J Error evaluation
SER_SND Data evaluation
N
RetVal 2001h ?
N
J
M: CPU 21xSER The following components are required for the example:
S: CP 240 • 1 CPU 21xSER as Modbus RTU master
• 1 System 200V with CP 240 as Modbus RTU slave
• Siemens SIMATIC manager and options for project transfer
• Modbus cable connection
The course of a This is the course a communication between master and slave happens:
communication
Master Send block Using this Send DB the master sends 16Byte user data to the slave with
as DB10 address 5:
Master Receive If there is no error the following data are transferred to the master by the
block as DB11 slave: