Cpu M13-CCF0000 20-02

VIPA System MICRO
CPU | M13-CCF0000 | Manual

HB400 | CPU | M13-CCF0000 | en | 20-02
SPEED7 CPU M13C
YASKAWA Europe GmbH
Ohmstraße 4
91074 Herzogenaurach
Tel.: +49 9132 744 0
Fax: +49 9132 744 186
Email: [email protected]
Internet: www.yaskawa.eu.com
M13-CCF0000_000_CPU M13C,7,EN - © 2020

VIPA System MICRO Table of contents
Table of contents
1 General.................................................................................................................... 9
1.1 Copyright © YASKAWA Europe GmbH............................................................ 9
1.2 About this manual........................................................................................... 10
1.3 Safety information........................................................................................... 11
2 Basics and mounting........................................................................................... 12
2.1 Safety information for users............................................................................ 12
2.2 System conception......................................................................................... 13
2.3 Dimensions..................................................................................................... 14
2.4 Mounting......................................................................................................... 16
2.4.1 Mounting CPU............................................................................................. 16
2.4.2 Mounting the extension module................................................................... 18
2.4.3 Mounting periphery module......................................................................... 19
2.5 Wiring............................................................................................................. 20
2.5.1 Wiring CPU.................................................................................................. 21
2.5.2 Wiring periphery module.............................................................................. 24
2.6 Demounting.................................................................................................... 26
2.6.1 Demounting CPU......................................................................................... 26
2.6.2 Demounting the extension module.............................................................. 30
2.6.3 Demounting periphery module.................................................................... 31
2.7 Installation guidelines..................................................................................... 34
2.8 General data for the System MICRO.............................................................. 36
3 Hardware description........................................................................................... 38
3.1 Properties....................................................................................................... 38
3.2 Structure......................................................................................................... 39
3.2.1 System MICRO CPU M13C........................................................................ 39
3.2.2 Interfaces..................................................................................................... 40
3.2.3 LEDs............................................................................................................ 44
3.2.4 Memory management.................................................................................. 48
3.2.5 Slot for storage media................................................................................. 48
3.2.6 Buffering mechanisms................................................................................. 49
3.2.7 Operating mode switch................................................................................ 49
3.3 Option: Extension module EM M09 2x serial interface .................................. 50
3.4 Technical data................................................................................................. 52
3.4.1 Technical data CPU..................................................................................... 52
3.4.2 Technical data EM M09............................................................................... 65
4 Deployment CPU M13-CCF0000.......................................................................... 66
4.1 Please note!.................................................................................................... 66
4.2 Assembly........................................................................................................ 66
4.3 Start-up behavior............................................................................................ 66
4.4 Addressing...................................................................................................... 67
4.4.1 Overview...................................................................................................... 67
4.4.2 Default address assignment of the I/O part................................................. 67
4.4.3 Option: Addressing periphery modules....................................................... 68
4.5 Hardware configuration - CPU........................................................................ 69
4.6 Hardware configuration - System MICRO modules........................................ 71
4.7 Hardware configuration - Ethernet PG/OP channel........................................ 72
4.7.1 Take IP address parameters in project........................................................ 73
HB400 | CPU | M13-CCF0000 | en | 20-02 3

Table of contents VIPA System MICRO
4.8 Setting standard CPU parameters.................................................................. 77

4.8.1 Parameterization via Siemens CPU............................................................ 77
4.8.2 Parameter CPU........................................................................................... 78
4.9 Setting VIPA specific CPU parameters........................................................... 82
4.9.1 Free Module Mapping (FMM)...................................................................... 84
4.9.2 Access settings............................................................................................ 89
4.10 Project transfer............................................................................................. 89
4.10.1 Transfer via Ethernet................................................................................. 90
4.10.2 Transfer via memory card.......................................................................... 90
4.10.3 Option: Transfer via MPI............................................................................ 91
4.11 Accessing the web server............................................................................. 93
4.11.1 Device web page CPU............................................................................... 93
4.12 Operating modes........................................................................................ 101
4.12.1 Overview.................................................................................................. 101
4.12.2 Function security..................................................................................... 103
4.13 Overall reset............................................................................................... 104
4.14 Firmware update......................................................................................... 106
4.14.1 Firmware update online........................................................................... 107
4.14.2 Firmware update via memory card.......................................................... 108
4.15 Reset to factory settings............................................................................. 109
4.16 Deployment storage media - VSD, VSC..................................................... 110
4.17 Extended know-how protection................................................................... 112
4.18 CMD - auto commands............................................................................... 113
4.19 Control and monitoring of variables with test functions.............................. 115
4.20 Diagnostic entries....................................................................................... 116
5 Deployment I/O periphery.................................................................................. 117
5.1 Overview....................................................................................................... 117
5.2 Address assignment..................................................................................... 118
5.3 Analog input.................................................................................................. 119
5.3.1 Properties.................................................................................................. 119
5.3.2 Analog value representation...................................................................... 119
5.3.3 Wiring........................................................................................................ 120
5.3.4 Parametrization......................................................................................... 121
5.4 Digital input................................................................................................... 122
5.4.1 Properties.................................................................................................. 122
5.4.2 Wiring........................................................................................................ 122
5.4.4 Status indication........................................................................................ 124
5.5 Digital output................................................................................................. 126
5.5.1 Properties.................................................................................................. 126
5.5.2 Wiring........................................................................................................ 126
5.6 Counting....................................................................................................... 129
5.6.1 Properties.................................................................................................. 129
5.6.2 Wiring........................................................................................................ 129
5.6.3 Proceeding................................................................................................ 131
5.6.5 Counter operating modes.......................................................................... 137
4 HB400 | CPU | M13-CCF0000 | en | 20-02

5.6.6 Counter - Additional functions................................................................... 144

5.6.7 Diagnostics and interrupt........................................................................... 150
5.7 Frequency measurement.............................................................................. 151
5.7.1 Properties.................................................................................................. 151
5.7.2 Wiring........................................................................................................ 152
5.7.3 Proceeding................................................................................................ 153
5.8 Pulse width modulation - PWM..................................................................... 157
5.8.1 Properties.................................................................................................. 157
5.8.2 Wiring........................................................................................................ 157
5.8.3 Proceeding................................................................................................ 158
5.9 Pulse train..................................................................................................... 162
5.9.1 Properties.................................................................................................. 162
5.9.2 Wiring........................................................................................................ 163
5.9.3 Proceeding................................................................................................ 163
5.10 Diagnostic and interrupt.............................................................................. 167
5.10.1 Overview.................................................................................................. 167
5.10.2 Process interrupt..................................................................................... 167
5.10.3 Diagnostic interrupt.................................................................................. 169
6 Deployment OPC UA.......................................................................................... 175
6.1 General......................................................................................................... 175
6.2 Basics OPC UA............................................................................................ 176
6.2.1 OPC UA..................................................................................................... 176
6.2.2 Information modeling................................................................................. 177
6.2.3 OPC UA data types and their conversion.................................................. 179
6.2.4 Integrated security concept....................................................................... 181
6.3 Activate OPC UA functionality...................................................................... 184
6.4 Usage in VIPA SPEED7 Studio.................................................................... 184
6.5 Usage in Siemens SIMATIC Manager.......................................................... 184
6.5.1 Precondition............................................................................................... 184
6.5.2 Installation OPC UA Configurator.............................................................. 185
6.5.3 Steps of the OPC UA configuration........................................................... 187
6.6 Usage in Siemens TIA Portal....................................................................... 187
6.6.1 Precondition............................................................................................... 187
6.6.2 Installation OPC UA Configurator.............................................................. 188
6.6.3 Steps of the OPC UA configuration........................................................... 190
6.7 Usage OPC UA Configurator........................................................................ 191
6.7.1 OPC UA Configurator................................................................................ 191
6.7.2 Project tree ............................................................................................ 192
6.7.3 Device properties .................................................................................. 193
6.7.4 Server settings - Connection ................................................................. 195
6.7.5 Server settings - Certificate ................................................................... 197
6.7.6 Data access .......................................................................................... 198
6.7.7 User management ................................................................................ 199
HB400 | CPU | M13-CCF0000 | en | 20-02 5

6.7.8 Role management ................................................................................. 200

6.7.9 Output ................................................................................................... 200
7 Deployment WebVisu - Web visualization........................................................ 201
7.1 WebVisu editor............................................................................................. 201
7.1.1 Working environment................................................................................. 202
7.1.2 Creating a WebVisu project....................................................................... 202
7.2 Activate WebVisu functionality..................................................................... 204
7.3 Start-up of the WebVisu project.................................................................... 204
7.4 Access to the WebVisu................................................................................. 205
7.4.1 Status of the WebVisu............................................................................... 205
8 Deployment PG/OP communication - productive........................................... 206
8.1 Basics - Industrial Ethernet in automation.................................................... 206
8.2 Basics - ISO/OSI reference model............................................................... 207
8.3 Basics - Terms.............................................................................................. 209
8.4 Basics - Protocols......................................................................................... 210
8.5 Basics - IP address and subnet.................................................................... 211
8.6 Fast introduction........................................................................................... 213
8.7 Hardware configuration................................................................................ 213
8.8 Configure Siemens S7 connections............................................................. 214
8.9 Configure Open Communication.................................................................. 219
9 Deployment PG/OP communication - PROFINET............................................ 222
9.1 Basics PROFINET........................................................................................ 222
9.2 PROFINET installation guidelines................................................................ 224
9.3 Deployment as PROFINET IO controller...................................................... 225
9.3.1 Steps of configuration................................................................................ 225
9.3.2 Commissioning and initialization............................................................... 226
9.3.3 Configuration PROFINET IO controller..................................................... 226
9.3.4 Configuration PROFINET IO device.......................................................... 228
9.4 Deployment as PROFINET I-Device............................................................ 229
9.4.1 Steps of configuration................................................................................ 229
9.4.2 Installing the GSDML file........................................................................... 230
9.4.3 Configuration as I-Device.......................................................................... 231
9.4.4 Configuration in the higher-level IO controller........................................... 232
9.4.5 Error behavior and interrupts..................................................................... 233
9.5 MRP.............................................................................................................. 236
9.6 Topology....................................................................................................... 237
9.7 Device replacement without exchangeable medium/PG.............................. 238
9.8 Commissioning and start-up behavior.......................................................... 239
9.9 PROFINET diagnostics................................................................................ 240
9.9.1 Overview.................................................................................................... 240
9.9.2 Diagnostics with the configuration and engineering tool........................... 240
9.9.3 Diagnostics during runtime in the user program........................................ 240
9.9.4 Diagnostics via OB start information......................................................... 242
9.9.5 Diagnostics status indication via SSLs...................................................... 242
9.10 PROFINET system limits............................................................................ 244
10 Option: PtP communication.............................................................................. 245
10.1 Fast introduction......................................................................................... 245
10.2 Principle of the data transfer....................................................................... 246
10.3 PtP communication via extension module EM M09................................... 247
6 HB400 | CPU | M13-CCF0000 | en | 20-02

10.4 Parametrization.......................................................................................... 250

10.4.1 FC/SFC 216 - SER_CFG - Parametrization PtP..................................... 250
10.5 Communication........................................................................................... 251
10.5.1 FC/SFC 217 - SER_SND - Send to PtP.................................................. 251
10.5.2 FC/SFC 218 - SER_RCV - Receive from PtP......................................... 251
10.6 Protocols and procedures........................................................................... 251
10.7 Modbus - Function codes .......................................................................... 255
11 Option: Deployment PROFIBUS communication............................................ 259
11.1 Fast introduction......................................................................................... 259
11.2 PROFIBUS communication........................................................................ 260
11.3 PROFIBUS communication via extension module EM M09....................... 261
11.4 Deployment as PROFIBUS DP slave......................................................... 263
11.4.1 Diagnostic functions................................................................................. 265
11.5 PROFIBUS installation guidelines.............................................................. 268
12 Configuration with VIPA SPEED7 Studio......................................................... 271
12.1 SPEED7 Studio - Overview........................................................................ 271
12.2 SPEED7 Studio - Work environment.......................................................... 272
12.2.1 Project tree ............................................................................................. 274
12.2.2 Catalog ................................................................................................... 275
12.3 SPEED7 Studio - Hardware configuration - CPU....................................... 277
12.4 SPEED7 Studio - Hardware configuration - Ethernet PG/OP channel....... 278
12.5 SPEED7 Studio - Hardware configuration - I/O modules........................... 281
12.6 Deployment I/O periphery........................................................................... 281
12.6.1 Overview.................................................................................................. 281
12.6.2 Analog input............................................................................................. 282
12.6.3 Digital input.............................................................................................. 283
12.6.4 Digital output............................................................................................ 283
12.6.5 Counter.................................................................................................... 284
12.6.6 Frequency measurement......................................................................... 288
12.6.7 Pulse width modulation - PWM................................................................ 290
12.6.8 Pulse train................................................................................................ 292
12.7 Deployment OPC UA.................................................................................. 293
12.8 Deployment WebVisu - Web visualization.................................................. 293
12.9 SPEED7 Studio - Project transfer............................................................... 294
12.9.1 Transfer via MPI...................................................................................... 294
12.9.2 Transfer via Ethernet............................................................................... 295
12.9.3 Transfer via memory card........................................................................ 296
13 Configuration with TIA Portal............................................................................ 298
13.1 TIA Portal - Work environment .................................................................. 298
13.1.1 General.................................................................................................... 298
13.1.2 Work environment of the TIA Portal........................................................ 299
13.2 TIA Portal - Functional limitations............................................................... 300
13.3 TIA Portal - Hardware configuration - CPU................................................ 300
13.4 TIA Portal - Hardware configuration - Ethernet PG/OP channel................ 303
13.4.1 Take IP address parameters in project.................................................... 305
13.5 TIA Portal - Hardware configuration - I/O modules..................................... 308
13.6 TIA Portal - Deployment PG/OP communication - PROFINET.................. 309
13.6.1 Deployment as PROFINET IO controller................................................. 309
13.7 TIA Portal - Option: Deployment PROFIBUS communication.................... 314
HB400 | CPU | M13-CCF0000 | en | 20-02 7

13.7.1 Fast introduction...................................................................................... 314

13.7.2 PROFIBUS communication via extension module EM M09.................... 316
13.7.3 Hardware configuration - CPU................................................................. 317
13.7.4 Deployment as PROFIBUS DP slave...................................................... 318
13.8 Deployment OPC UA.................................................................................. 319
13.9 TIA Portal - VIPA-Include library................................................................. 320
13.10 TIA Portal - Project transfer...................................................................... 321
13.10.1 Transfer via Ethernet............................................................................. 321
13.10.2 Transfer via memory card...................................................................... 321
13.10.3 Option: Transfer via MPI........................................................................ 322
Appendix............................................................................................................. 324
A System specific event IDs............................................................................... 326
B Integrated blocks............................................................................................. 378
C SSL partial list................................................................................................. 381
8 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO General
Copyright © YASKAWA Europe GmbH
1 General
1.1 Copyright © YASKAWA Europe GmbH
All Rights Reserved This document contains proprietary information of YASKAWA and is not to be disclosed
or used except in accordance with applicable agreements.
This material is protected by copyright laws. It may not be reproduced, distributed, or
altered in any fashion by any entity (either internal or external to YASKAWA) except in
accordance with applicable agreements, contracts or licensing, without the express
written consent of YASKAWA and the business management owner of the material.
For permission to reproduce or distribute, please contact: YASKAWA Europe GmbH,
European Headquarters, Hauptstraße 185, 65760 Eschborn, Germany
Tel.: +49 6196 569 300
Fax.: +49 6196 569 398
Internet: www.yaskawa.eu.com
Every effort has been made to ensure that the information contained in
this document was complete and accurate at the time of publishing. Nev-
ertheless, 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.
EC conformity declaration Hereby, YASKAWA Europe GmbH declares that the products and systems are in compli-
ance with the essential requirements and other relevant provisions. Conformity is indi-
cated 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 representative of YASKAWA Europe GmbH.
Trademarks VIPA, SLIO, System 100V, System 200V, System 300V, System 300S, System 400V,
System 500S and Commander Compact are registered trademarks of YASKAWA Europe
GmbH.
SPEED7 is a registered trademark of YASKAWA Europe GmbH.
SIMATIC, STEP, SINEC, TIA Portal, S7-300, S7-400 and S7-1500 are registered trade-
marks of Siemens AG.
Microsoft and 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.
HB400 | CPU | M13-CCF0000 | en | 20-02 9

General VIPA System MICRO
About this manual
Document support Contact your local representative of YASKAWA Europe GmbH if you have errors or ques-
tions regarding the content of this document. If such a location is not available, you can
reach YASKAWA Europe GmbH via the following contact:
YASKAWA Europe GmbH, Ohmstraße 4, 91074 Herzogenaurach, Germany
Fax: +49 9132 744 29 1204
Technical support Contact your local representative of YASKAWA Europe GmbH if you encounter problems
or have questions regarding the product. If such a location is not available, you can reach
the YASKAWA customer service via the following contact:
YASKAWA Europe GmbH,
European Headquarters, Hauptstraße 185, 65760 Eschborn, Germany
Tel.: +49 6196 569 500 (hotline)
1.2 About this manual

Objective and contents This manual describes the CPU M13-CCF0000 of the System MICRO from VIPA. It con-
tains a description of the construction, project implementation and usage.
Product Order number as of state:

CPU-HW CPU-FW
CPU M13C M13-CCF0000 01 V3.0.0
Target audience The manual is targeted at users who have a background in automation technology.
Structure of the manual The manual consists of chapters. Every chapter provides a self-contained description of a
specific topic.
Guide to the document The following guides are available in the manual:
n An overall table of contents at the beginning of the manual
n References with page numbers
Availability The manual is available in:

n printed form, on paper
n in electronic form as PDF-file (Adobe Acrobat Reader)
Icons Headings Important passages in the text are highlighted by following icons and headings:
DANGER!
Immediate or likely danger. Personal injury is possible.
10 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO General
Safety information
CAUTION!
Damages to property is likely if these warnings are not heeded.
Supplementary information and useful tips.
1.3 Safety information

Applications conforming The system is constructed and produced for:
with specifications
n communication and process control
n general control and automation tasks
n industrial applications
n operation within the environmental conditions specified in the technical data
n installation into a cubicle
DANGER!
This device is not certified for applications in
– in explosive environments (EX-zone)
Documentation The manual must be available to all personnel in the

n project design department
n installation department
n commissioning
n operation
CAUTION!
The following conditions must be met before using or commis-
sioning the components described in this manual:
– Hardware modifications to the process control system should only be
carried out when the system has been disconnected from power!
– Installation and hardware modifications only by properly trained per-
sonnel.
– The national rules and regulations of the respective country must be
satisfied (installation, safety, EMC ...)
Disposal National rules and regulations apply to the disposal of the unit!
HB400 | CPU | M13-CCF0000 | en | 20-02 11

Basics and mounting VIPA System MICRO
Safety information for users
2 Basics and mounting

2.1 Safety information for users
Handling of electrostatic VIPA modules make use of highly integrated components in MOS-Technology. These
sensitive modules components are extremely sensitive to over-voltages that can occur during electrostatic
discharges. The following symbol is attached to modules that can be destroyed by elec-
trostatic discharges.
The Symbol is located on the module, the module rack or on packing material and it indi-
cates the presence of electrostatic sensitive equipment. It is possible that electrostatic
sensitive equipment is destroyed by energies and voltages that are far less than the
human threshold of perception. These voltages can occur where persons do not dis-
charge themselves before handling electrostatic sensitive modules and they can damage
components thereby, causing the module to become inoperable or unusable. Modules
that have been damaged by electrostatic discharges can fail after a temperature change,
mechanical shock or changes in the electrical load. Only the consequent implementation
of protection devices and meticulous attention to the applicable rules and regulations for
handling the respective equipment can prevent failures of electrostatic sensitive modules.
Shipping of modules Modules must be shipped in the original packing material.
Measurements and altera- When you are conducting measurements on electrostatic sensitive modules you should
tions on electrostatic sen- take the following precautions:
sitive modules
n Floating instruments must be discharged before use.
n Instruments must be grounded.
Modifying electrostatic sensitive modules you should only use soldering irons with
grounded tips.
CAUTION!
Personnel and instruments should be grounded when working on electro-
static sensitive modules.
12 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO Basics and mounting
System conception
2.2 System conception

Overview
The System MICRO is a modular automation system for assembly on a 35mm mounting
rail. By means of periphery modules this system may be adapted matching to your auto-
mation tasks. In addition, it is possible to expand your CPU by appropriate interfaces. The
wiring complexity is low, because the DC 24V electronic section supply is integrated to
the backplane bus and this allows replacement with standing wire.
Components n CPU
n Extension module
n Power supply
n Periphery module
CPU
With the CPU electronic, input/output components and power supply are integrated to
one casing. In addition, up to 8 periphery modules of the System MICRO can be con-
nected to the backplane bus. As head module via the integrated power module for power
supply CPU electronic and the I/O components are supplied as well as the electronic of
the periphery modules, which are connected via backplane bus. To connect the power
supply of the I/O components and for DC 24V electronic power supply of the periphery
modules, which are connected via backplane bus, the CPU has removable connectors.
By installing of up to 8 periphery modules at the backplane bus of the CPU, these are
electrically connected, this means these are assigned to the backplane bus and con-
nected to the DC 24V electronic power supply.
Extension module
By using extension modules you can extend the interfaces of the CPU. The attachment to
the CPU is made by plugging on the left side of the CPU. You can only connect one
extension module to the CPU at a time.
HB400 | CPU | M13-CCF0000 | en | 20-02 13

Dimensions
Power supply
The power supply can be mounted together with System MICRO components at the
mounting rail. It serves for electronics and power supply.
Periphery module
By means of up to 8 periphery modules, you can extend the internal I/O areas. The
attachment to the CPU is made by plugging them on the right side of the CPU.
2.3 Dimensions
Dimensions CPU M13C
Dimensions in mm
14 HB400 | CPU | M13-CCF0000 | en | 20-02

Dimensions
Dimensions extension
module EM M09
Dimensions in mm
Dimensions power supply
HB400 | CPU | M13-CCF0000 | en | 20-02 15

Mounting > Mounting CPU
Dimensions periphery
module
Dimensions in mm
2.4 Mounting
2.4.1 Mounting CPU
2.4.1.1 Mounting CPU without mounting rail
CAUTION!
Mounting without mounting rail is only permitted, if you only want to use
the CPU without extension and periphery modules. Otherwise, a
mounting rail must always be used for EMC technical reasons.
Proceeding You can screw the CPU to the back wall by means of screws via the locking levers. This
happens with the following proceeding:
Dimensions in mm
16 HB400 | CPU | M13-CCF0000 | en | 20-02

Mounting > Mounting CPU
1. The CPU has a locking lever on the upper and lower side. Pull these levers out-
wards as shown in the figure, until these engage 2x audible.
ð By this openings on the locking levers get visible.
2. Use the appropriate screws to fix your CPU to your back wall. Consider the installa-
tion clearances for the CPU.
ð The CPU is now mounted and can be wired.
2.4.1.2 Mounting with mounting rail

Proceeding
Dimensions in mm
1. Mount the mounting rail. Please consider that a clearance from the middle of the
mounting rail of at least 44mm respectively 55mm above and below exists.
2. The CPU has a locking lever on the upper and lower side. Pull these levers out-
wards as shown in the figure, until these engage audible.
CAUTION!
It is not allowed to mount the module sideways on the mounting rail,
as otherwise the module may be damaged.
3. Plug the CPU from the top onto the mounting rail and turn the CPU downward until
it rests on the mounting rail.
HB400 | CPU | M13-CCF0000 | en | 20-02 17

Mounting > Mounting the extension module
4. Move the CPU on the mounting rail at its position.
5. To fix the CPU at the mounting rail, move the locking levers back to the initial posi-
tion.
ð The CPU is now mounted and can be wired.
2.4.2 Mounting the extension module

Proceeding You have the possibility to extend the interfaces of the CPU by plugging an extension
module. For this the extension module is plugged at the left side of the CPU. The mount-
ings happens with the following proceeding:
1. Remove the bus cover with a screwdriver on the left side of the CPU.
2. The extension module has a locking lever on the upper and lower side. Pull these
levers outwards as shown in the figure, until these engage audible.
CAUTION!
18 HB400 | CPU | M13-CCF0000 | en | 20-02

Mounting > Mounting periphery module
3. To mount plug the extension module from the top onto the mounting rail and turn
the extension module downward until it rests on the mounting rail.
4. Attach the extension module to the CPU by sliding the extension module on the
mounting rail to the right until the interface connector slightly locks into the CPU.
5. To fix the extension module at the mounting rail, move the locking levers back to the
initial position.
2.4.3 Mounting periphery module

Proceeding You have the possibility to extend the periphery area of the CPU by plugging up to 8
periphery modules. For this the periphery modules are plugged at the right side of the
CPU. The mountings happens with the following proceeding:
1. Remove the bus cover with a screwdriver on the right side of the CPU.
2. Each periphery module has a locking lever on its upper and lower side. Pull these
levers outwards as shown in the figure, until these engage audible.
CAUTION!
HB400 | CPU | M13-CCF0000 | en | 20-02 19

Wiring
3. To mount plug the periphery module from the top onto the mounting rail and turn the
periphery module downward until it rests on the mounting rail.
4. Attach the periphery module to the CPU by sliding the periphery module on the
mounting rail to the left until the interface connector slightly locks into the CPU.
5. To fix the periphery module at the mounting rail, move the locking levers back to the
initial position.
6. Proceed in this way with additional periphery modules.
2.5 Wiring
DANGER!
Consider strain relief of the supply lines!
Since the plug for the supply lines of the input voltage has no (double)
insulation, not permanently fixed supply lines must be relieved from push
and pull!
CAUTION!
Consider temperature for external cables!
Cables may experience temperature increase due to system heat dissi-
pation. Thus the cabling specification must be chosen 25°C above
ambient temperature!
CAUTION!
Separate insulation areas!
The system is specified for SELV/PELV environment. Devices, which are
attached to the system must meet theses specifications. Installation and
cable routing other than SELV/PELV specification must be separated
from the system’s equipment!
20 HB400 | CPU | M13-CCF0000 | en | 20-02

Wiring > Wiring CPU
2.5.1 Wiring CPU

CPU connector For wiring the CPU has removable connectors. With the wiring of the connectors a "push-
in" spring-clip technique is used. This allows a quick and easy connection of your signal
and supply lines. The clamping off takes place by means of a screwdriver.
Data
Umax 30V DC
Imax 10A
Cross section 0.2 ... 1.5mm2 (AWG 24 ... 16)
Stripping length 10mm
Use for wiring rigid wires respectively use wire sleeves. When using stranded wires you
have to press the release button with a screwdriver during the wiring.
Wiring procedure
1 Labeling on the casing
2 Status LED
3 Release area
4 Connection hole for wire
5 Pin 1 of the connector is labelled by a white line
Insert wire The wiring happens without a tool.

Determine according to the casing labelling the connection position and insert
through the round connection hole of the according contact your prepared wire until
it stops, so that it is fixed.
ð By pushing the contact spring opens, thus ensuring the necessary contact pres-
sure.
Remove wire The wire is to be removed by means of a screwdriver with 2.5mm blade width.
1. Press with your screwdriver vertically at the release button.
ð The contact spring releases the wire.
2. Pull the wire from the round hole.
HB400 | CPU | M13-CCF0000 | en | 20-02 21

Wiring > Wiring CPU
Standard wiring
(1) X2: 4L+: DC 24V power section supply for integrated outputs
X1: 3L+: DC 24V power section supply for integrated inputs
(2) X6: 1L+ DC 24V for electronic power supply
22 HB400 | CPU | M13-CCF0000 | en | 20-02

Wiring > Wiring CPU
The electronic power section supply is internally protected against higher

voltage by fuse. The fuse is located inside the CPU and can not be
changed by the user.
Fusing
CAUTION!
– The power section supply of the internal DOs is to be externally pro-
tected with a 8A fuse (fast) respectively by a line circuit breaker 8A
characteristics Z.
Remove connector By means of a screwdriver there is the possibility to remove the connectors e.g. for
module exchange with a fix wiring. For this each connector has indentations for unlocking
at the top. Unlocking takes place by the following proceeding:
1. Remove connector:
Insert your screwdriver from above into one of the indentations.
2. Push the screwdriver backwards:

ð The connector is unlocked and can be removed.
CAUTION!
Via wrong operation such as pressing the screwdriver down-
ward, the release lever may be damaged.
3. Plug connector:
The connector is plugged by plugging it directly into the release lever.
HB400 | CPU | M13-CCF0000 | en | 20-02 23

Wiring > Wiring periphery module
2.5.2 Wiring periphery module

Periphery module con- For wiring the periphery module has removable connectors. With the wiring of the con-
nector nectors a "push-in" spring-clip technique is used. This allows a quick and easy connection
of your signal and supply lines. The clamping off takes place by means of a screwdriver.
Data
Umax 240V AC / 30V DC
Imax 10A
Cross section 0.2 ... 1.5mm2 (AWG 24 ... 16)
Stripping length 10mm
Use for wiring rigid wires respectively use wire sleeves. When using stranded wires you
have to press the release button with a screwdriver during the wiring.
Wiring procedure
1 Labeling on the casing
2 Status LED
3 Release area
4 Connection hole for wire
5 Pin 1 of the connector is labelled by a white line
Insert wire The wiring happens without a tool.

Determine according to the casing labelling the connection position and insert
through the round connection hole of the according contact your prepared wire until
it stops, so that it is fixed.
ð By pushing the contact spring opens, thus ensuring the necessary contact pres-
sure.
Remove wire The wire is to be removed by means of a screwdriver with 2.5mm blade width.
1. Press with your screwdriver vertically at the release button.
ð The contact spring releases the wire.
2. Pull the wire from the round hole.
Fusing
CAUTION!
– The power section supply of the output modules DO16 is to be exter-
nally protected with a 10A fuse (fast) respectively by a line circuit
breaker 10A characteristics Z.
– The power section supply of the output part of the DIO8 is to be
externally protected with a 5A fuse (fast) respectively by a line circuit
breaker 5A characteristics Z.
24 HB400 | CPU | M13-CCF0000 | en | 20-02

Wiring > Wiring periphery module

CAUTION!
ward, the release lever may be damaged.
3. Plug connector:
The connector is plugged by plugging it directly into the release lever.
HB400 | CPU | M13-CCF0000 | en | 20-02 25

Demounting > Demounting CPU
2.6 Demounting
2.6.1 Demounting CPU
1. Power-off your system.

CAUTION!
ward, the connector may be damaged!
4. In this way, remove all plugged connectors on the CPU.
CPU replacement (stand- If more modules are connected to the CPU Ä ‘Option: CPU replacement in a system’
alone) page 28. If no other modules are connected to the CPU, the CPU is replaced according
to the following proceeding:
1. Use a screwdriver to pull the locking levers of the CPU outwards until these engage
audible.
2. Remove the CPU with a rotation upwards from the mounting rail.
26 HB400 | CPU | M13-CCF0000 | en | 20-02

3. Pull the locking levers of the CPU outwards until these engage audible.
CAUTION!
as otherwise the module may be damaged!
4. Plug the CPU from the top onto the mounting rail and turn the CPU downward until
it rests on the mounting rail.
5. Move the CPU on the mounting rail at its position.
tion.
7. Remove the connectors, which are not necessary at the CPU.
HB400 | CPU | M13-CCF0000 | en | 20-02 27

8. Plug again the wired connectors.

ð Now you can bring your system back into operation.
Option: CPU replacement In the following the replacement of a CPU in a system is shown:
in a system
1. If there is an extension module connected to the CPU, you have to remove it from
the CPU. For this use a screwdriver to pull the locking levers of the extension
module and CPU outwards until these engage audible.
2. Disconnect all the modules, which are connected to the CPU by moving the CPU
along with the extension module on the mounting rail.
3. Remove the CPU with a rotation upwards from the mounting rail.
4. Pull the locking levers of the CPU outwards until these engage audible.
CAUTION!
5. For mounting pull the locking levers of the CPU outwards until these engage
audible. Plug the CPU from the top onto the mounting rail and turn the CPU down-
ward until it rests on the mounting rail.
28 HB400 | CPU | M13-CCF0000 | en | 20-02

6. Rebind your modules by moving the CPU along with the extension module on the
mounting rail.
tion.
8. Remove the connectors, which are not necessary at the CPU.

HB400 | CPU | M13-CCF0000 | en | 20-02 29

Demounting > Demounting the extension module
2.6.2 Demounting the extension module

Proceeding 1. Power-off your system.
2. Remove the corresponding bus connectors.
3. Use a screwdriver to pull the locking levers of the extension module outwards until
these engage audible.
4. Remove the extension module from the CPU by sliding it on the mounting rail.
5. Remove the extension module with a rotation upwards from the mounting rail.
6. Pull the locking levers of the extension module outwards until these engage
audible.
CAUTION!
7. Plug the extension module from the top onto the mounting rail and turn the exten-
sion module downward until it rests on the mounting rail.
8. Reattach the extension module to the CPU by sliding the extension module on the
mounting rail to the right until the interface connector slightly locks into the CPU.
9. Move the locking levers back to the initial position.

10. Plug the corresponding bus connectors.
30 HB400 | CPU | M13-CCF0000 | en | 20-02

Demounting > Demounting periphery module
2.6.3 Demounting periphery module

1. Power-off your system.
CAUTION!
Make sure that the working contacts from the relay module are dis-
connected from the power supply!

CAUTION!
ward, the connector may be damaged!
4. In this way, remove all plugged connectors on the periphery module.
Replace the periphery

module
1. Remove the modules that are connected to the module to be replaced by pulling
their release levers outwards until these engage audible ...
2. ... and move the modules accordingly.
HB400 | CPU | M13-CCF0000 | en | 20-02 31

3. Remove the periphery module with a rotation upwards from the mounting rail.
4. Pull the locking levers outwards until these engage audible.
CAUTION!
5. Plug the periphery module from the top onto the mounting rail and turn the
periphery module downward until it rests on the mounting rail.
6. Reconnect all modules by pushing them together again on the mounting rail.
7. Move the locking levers back to the initial position.
8. Remove the connectors, which are not necessary.
32 HB400 | CPU | M13-CCF0000 | en | 20-02


2.6.3.1 Easy Maintenance

Overview Easy Maintenance means the support for adding and removing modules during operation
without having to restart the system. There are the following behaviors:
n Periphery module is removed
– The CPU detects a module failure on the backplane bus.
– Diagnostic message ‘System MICRO bus failure’ (0x39D0) is triggered.
– OB 86 is called. If this is not available, the CPU switches to STOP otherwise it
remains in RUN.
– The red LED of the status bar of the CPU lights up.
– The I/O data of all modules become invalid.
n Identical periphery module is plugged
– The CPU detects the module return on the backplane bus.
– The red LED of the status bar of the CPU gets off.
– All green LEDs of the status bars of the peripheral modules get on and all the red
LEDs of the status bars of the peripheral modules get off.
– Diagnostic message ‘System MICRO bus recovery’ (0x38D0) is triggered.
remains in RUN.
– The I/O data of all modules become valid again.
n Wrong periphery module is plugged
– The CPU detects the wrong module.
– Diagnostic message ‘System MICRO bus recovery, but expected configuration
does not match actual configuration’ (0x38D1) is triggered.
– The red LED of the status bar of the CPU remains on.
– The red LED of the status bar of the wrong I/O module flashes.
remains in RUN.
– With the exception of the wrong module, the I/O data of all modules become valid
again.
Please note that the CPU switches to STOP, if there is no OB 86 config-

ured when adding or removing System MICRO modules!
HB400 | CPU | M13-CCF0000 | en | 20-02 33

Installation guidelines
2.7 Installation guidelines

General The installation guidelines contain information about the interference free deployment of a
PLC system. There is the description of the ways, interference may occur in your PLC,
how you can make sure the electromagnetic compatibility (EMC), and how you manage
the isolation.
What does EMC mean? Electromagnetic compatibility (EMC) means the ability of an electrical device, to function
error free in an electromagnetic environment without being interfered respectively without
interfering the environment.
The VIPA components are developed for the deployment in industrial environments and
meets high demands on the EMC. Nevertheless you should project an EMC planning
before installing the components and take conceivable interference causes into account.
Possible interference Electromagnetic interferences may interfere your control via different ways:
causes
n Electromagnetic fields (RF coupling)
n Magnetic fields with power frequency
n Bus system
n Power supply
n 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.
There are:
n galvanic coupling
n capacitive coupling
n inductive coupling
n radiant coupling
Basic rules for EMC In the most times it is enough to take care of some elementary rules to guarantee the
EMC. Please regard the following basic rules when installing your PLC.
n 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 aluminium parts. Aluminium is easily oxidizing and is there-
fore less suitable for grounding.
n 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 respectively 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).
34 HB400 | CPU | M13-CCF0000 | en | 20-02

Installation guidelines
n 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 ampli-
tudes the one sided laying of the isolation may be favourable.
– Lay the line isolation extensively on an isolation/protected earth conductor rail
directly after the cabinet entry and fix the isolation with cable clamps.
– Make sure that the isolation/protected earth conductor rail is connected impe-
dance-low with the cabinet.
– Use metallic or metallised plug cases for isolated data lines.
n In special use cases you should appoint special EMC actions.
– Consider to wire all inductivities with erase links.
– Please consider luminescent lamps can influence signal lines.
n Create a homogeneous reference potential and ground all electrical operating sup-
plies when possible.
– Please take care for the targeted employment of the grounding actions. The
grounding of the PLC serves for protection and functionality activity.
– Connect installation parts and cabinets with your PLC in star topology with the
isolation/protected earth conductor system. So you avoid ground loops.
– If there are potential differences between installation parts and cabinets, lay suffi-
ciently dimensioned potential compensation lines.
Isolation of conductors Electrical, magnetically and electromagnetic interference fields are weakened by means
of an isolation, one talks of absorption. Via the isolation rail, that is connected conductive
with the rack, interference currents are shunt via cable isolation to the ground. Here you
have to make sure, that the connection to the protected earth conductor is impedance-
low, because otherwise the interference currents may appear as interference cause.
When isolating cables you have to regard the following:
n If possible, use only cables with isolation tangle.
n The hiding power of the isolation should be higher than 80%.
n Normally you should always lay the isolation of cables on both sides. Only by means
of the both-sided connection of the isolation you achieve high quality interference
suppression in the higher frequency area. Only as exception you may also lay the iso-
lation one-sided. Then you only achieve the absorption of the lower frequencies. A
one-sided isolation connection may be convenient, if:
– the conduction of a potential compensating line is not possible.
– analog signals (some mV respectively µA) are transferred.
– foil isolations (static isolations) are used.
n With data lines always use metallic or metallised plugs for serial couplings. Fix the
isolation of the data line at the plug rack. Do not lay the isolation on the PIN 1 of the
plug bar!
n At stationary operation it is convenient to strip the insulated cable interruption free
and lay it on the isolation/protected earth conductor line.
n To fix the isolation tangles use cable clamps out of metal. The clamps must clasp the
isolation extensively and have well contact.
n Lay the isolation on an isolation rail directly after the entry of the cable in the cabinet.
Lead the isolation further on to your PLC and don't lay it on there again!
CAUTION!
Please regard at installation!
At potential differences between the grounding points, there may be a
compensation current via the isolation connected at both sides.
Remedy: Potential compensation line
HB400 | CPU | M13-CCF0000 | en | 20-02 35

General data for the System MICRO
2.8 General data for the System MICRO

Conformity and approval
Conformity
CE 2014/35/EU Low-voltage directive
2014/30/EU EMC directive
Approval
UL - Refer to Technical data
others
RoHS 2011/65/EU Restriction of the use of certain hazardous substances in
electrical and electronic equipment
Protection of persons and device protection

Type of protection - IP20
Electrical isolation
to the field bus - electrically isolated
to the process level - electrically isolated
Insulation resistance - -
Insulation voltage to reference earth
Inputs / outputs - AC / DC 50V, test voltage AC 500V
Protective measures - against short circuit
Environmental conditions to EN 61131-2

Climatic
Storage / transport EN 60068-2-14 -25…+70°C
Operation
Horizontal installation hanging EN 61131-2 0…+60°C
Horizontal installation lying EN 61131-2 0…+60°C
Vertical installation EN 61131-2 0…+60°C
Air humidity EN 60068-2-30 RH1 (without condensation, rel. humidity 10…95%)
Pollution EN 61131-2 Degree of pollution 2
Installation altitude max. - 2000m
Mechanical
Oscillation EN 60068-2-6 1g, 9Hz ... 150Hz
Shock EN 60068-2-27 15g, 11ms
36 HB400 | CPU | M13-CCF0000 | en | 20-02

General data for the System MICRO
Mounting conditions
Mounting place - In the control cabinet
Mounting position - Horizontal and vertical
EMC Standard Comment

Emitted interference EN 61000-6-4 Class A (Industrial area)
Noise immunity EN 61000-6-2 Industrial area
zone B EN 61000-4-2 ESD
8kV at air discharge (degree of severity 3),
4kV at contact discharge (degree of severity 2)
EN 61000-4-3 HF field immunity (casing)
80MHz … 1000MHz, 10V/m, 80% AM (1kHz)
1.4GHz ... 2.0GHz, 3V/m, 80% AM (1kHz)
2GHz ... 2.7GHz, 1V/m, 80% AM (1kHz)
EN 61000-4-6 HF conducted
150kHz … 80MHz, 10V, 80% AM (1kHz)
EN 61000-4-4 Burst, degree of severity 3
EN 61000-4-5 Surge, degree of severity 3 *
*) Due to the high-energetic single pulses with Surge an appropriate external protective circuit with lightning protection elements like conductors for lightning and overvoltage is
necessary.
HB400 | CPU | M13-CCF0000 | en | 20-02 37

Hardware description VIPA System MICRO
Properties
3 Hardware description
3.1 Properties
M13-CCF0000 n SPEED7 technology integrated
n Programmable via VIPA SPEED7 Studio, Siemens SIMATIC Manager or Siemens
TIA Portal
n 64kbyte work memory integrated (32kbyte code, 32kbyte data)
n Work memory expandable up to max. 128kbyte (64kbyte code, 64kbyte data)
n 128kbyte load memory integrated
n Slot for external storage media (lockable)
n Status LEDs for operating state and diagnostics
n X1/X5: DI 16xDC24V with status indication integrated
n X2/X6: DO 12xDC24V 0.5A with status indication integrated
n X3/X4: Ethernet PG/OP channel for active and passive Communication integrated
n X6: AI 2x12Bit (single ended) integrated
n Technological functions: 4 channels for counter, frequency measurement and
2 channels for pulse width modulation
n Pulse Train via SFB 49 (PULSE)
n PROFINET IO controller and I-Device via Ethernet PG/OP channel
n OPC UA project via Ethernet PG/OP channel
n WebVisu project via Ethernet PG/OP channel
n Option: Extension module 2xRS485
n Option: max. 8 periphery modules
n I/O address area digital/analog 2048byte
n 512 timer/counter, 8192 flag byte
Ordering data
Type Order number Description

CPU M13C M13-CCF0000 System MICRO CPU M13C with options to extend work memory,
DI 16xDC24V, DO 12xDC24 0.5A, AI 2x12bit and 4 channels
technological functions
EM M09 M09-0CB00 System MICRO extension: Serial interface 2x
(RS485/RS422, MPI, option PROFIBUS DP slave)
38 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO Hardware description
Structure > System MICRO CPU M13C
3.2 Structure
3.2.1 System MICRO CPU M13C
CPU M13-CCF0000
1 Slot for external storage media (lockable)

2 Operating mode switch CPU
3 X3: Ethernet PG/OP channel 1
4 X4: Ethernet PG/OP channel 2
5 X2: Connector DO +0.0 ... DO +0.7
6 X1: Connector DI +0.0 ... DI +0.7
7 Status bar CPU
8 X5: Connector DI +1.0 ... DI +1.7
9 X6: Connector electronic section supply, AI, DO +1.0 ... DO +1.3
10 X2 4L+: LED DC 24V power section supply for on-board DO
11 X2 4M: LED on error, overload respectively short circuit at the outputs
12 X2 DO +0.x: LEDs DO +0.0 ... DO +0.7
13 X1 3L+: LED DC 24V power section supply for on-board DI
14 X1 DI +0.x: LEDs DI +0.0 ... DI +0.7
15 X5 DI +1.x: LEDs DI +1.0 ... DI +1.7
16 X6 1L+: LED DC 24V for electronic section supply
17 X6 DO +1.x: LEDs DO +1.0 ... DO +1.3
18 X3 Ethernet PG/OP channel: LEDs Link/Activity
HB400 | CPU | M13-CCF0000 | en | 20-02 39

Structure > Interfaces
3.2.2 Interfaces
40 HB400 | CPU | M13-CCF0000 | en | 20-02

X1: DI byte 0
X1 Function Type LED Description

green
1 DI 0.7 I Digital input DI 7 / Counter 2 (B) / Frequency 2 *
2 DI 0.6 I Digital input DI 6 / Counter 2 (A) *
3 DI 0.5 I Digital input DI 5
9 0V I 3M: GND for onboard DI power section supply
10 DC 24V I 3L+: DC 24V for onboard DI power section supply
*) Max. input frequency 100kHz otherwise 1kHz.
X2: DO byte 0
HB400 | CPU | M13-CCF0000 | en | 20-02 41


green
1 DO 0.7 O Digital output DO 7
5 DO 0.3 O Digital output DO 3 / Output channel counter 3
7 DO 0.1 O Digital output DO 1 / PWM 1 / Output channel counter 1
9 0V I red 4M: GND for onboard DO power section supply / GND PWM
LED (red) is on at short circuit respectively overload
10 DC 24V I 4L+: DC 24V for onboard DO power section supply
X3/X4: Ethernet PG/OP 8pin RJ45 jack:

channel
n The RJ45 jack serves as interface to the Ethernet PG/OP channel.
n This interface allows you to program respectively remote control your CPU and to
access the internal web server.
n The Ethernet PG/OP channel (X3/X4) is designed as switch. This enables PG/OP
communication via the connections X3 and X4.
n Configurable connections are possible.
n DHCP respectively the assignment of the network configuration with a DHCP server
is supported.
n Default diagnostics addresses: 2025 ... 2040
n At the first commissioning respectively after a factory reset the Ethernet PG/OP
channel has no IP address. For online access to the CPU via the Ethernet PG/OP
channel, valid IP address parameters have to be assigned to this by means of your
configuration tool. This is called "initialization".
n Via the Ethernet PG/OP channel, you have access to:
– Device web page, where you can find information on firmware status, connected
peripherals, current cycle times, etc.
– OPC UA project, which is to be created in the OPC UA Configurator.
– WebVisu project, which is to be created in the SPEED7 Studio.
– PROFINET IO controller or the PROFINET I-Device.
Ä Chap. 4.7 ‘Hardware configuration - Ethernet PG/OP channel’ page 72
Ä Chap. 8 ‘Deployment PG/OP communication - productive’ page 206
X5: DI byte 1
42 HB400 | CPU | M13-CCF0000 | en | 20-02


green
1 - - reserved
2 - - reserved
6 DI 1.3 I Digital input DI 11 / Gate 3 *
10 DI 1.7 I Digital input DI 15 / Latch 3 *
X6: DC 24V, AI, DO byte 1

green
1 1L+ I 1L+: DC 24V for electronic section supply
2 1M I 1M: DC 0V for electronic section supply
3 I Shield
4 2M I 2M: Ground for analog inputs
5 AI 0 I Analog input AI 0
HB400 | CPU | M13-CCF0000 | en | 20-02 43

Structure > LEDs
X6: Electronic power

supply
The CPU has an integrated power supply. The power supply has to be provided with DC
24V. Via the power supply not only the internal electronic of the CPU is provided with
voltage, but also the electronic from the integrated IO components. The power supply is
protected against polarity inversion and over current.
3.2.3 LEDs
1 Status bar CPU
4 X1 DI +0.x: LEDs DI +0.0 ... DI +0.7
5 X1 3L+: LED DC 24V power section supply for on-board DI
6 X2 DO +0.x: LEDs DO +0.0 ... DO +0.7
7 X2 4L+: LED DC 24V power section supply for on-board DO
8 X2 4M: LED on error, overload respectively short circuit at the outputs
9 X5 DI +1.x: LEDs DI +1.0 ... DI +1.7
10 X6 DO +1.x: LEDs DO +1.0 ... DO +1.3
11 X6 1L+: LED DC 24V for electronic section supply
Status bar CPU
Status bar Function

green CPU - RUN: CPU is in state RUN without error. Ä 47
yellow CPU - STOP: CPU is in STOP state. Ä 47
red CPU - system fault: System error occurred. Ä 47
Ethernet PG/OP channel
X3/X4 Function
green Ethernet PG/OP channel X3/X4: Link/Activity Ä 48
yellow Ethernet PG/OP channel X3/X4: Speed Ä 48
44 HB400 | CPU | M13-CCF0000 | en | 20-02

Structure > LEDs
X1 DI +0.x
Digital input LED Description
green
DI +0.0 ... DI +0.7 Digital input I+0.0 ... 0.7 has "1" signal
Digital input I+0.0 ... 0.7 has "0" signal
X1 3L+
Power supply LED Description
green
3L+ DC 24V power section supply inputs OK
DC 24V power section supply inputs not available
X2 DO +0.x
Digital output LED Description
green
DO +0.0 ... DO +0.7 Digital output Q+0.0 ... 0.7 has "1" signal
Digital output Q+0.0 ... 0.7 has "0" signal
X2 4L+
green
4L+ DC 24V power section supply outputs OK
DC 24V power section supply outputs not available
X2 4M
Error LED Description
red
4M Error, overload respectively short circuit on the outputs
no error
X5 DI +1.x
green
HB400 | CPU | M13-CCF0000 | en | 20-02 45

Structure > LEDs
X6 DO +1.x
green
X6 1L+
green
1L+ DC 24V electronic section supply OK
DC 24V electronic section supply not available
46 HB400 | CPU | M13-CCF0000 | en | 20-02

Structure > LEDs
3.2.3.1 Status bar CPU

LED Description
Start-up
LED yellow blinks with 1Hz: State of the CPU after PowerON
LEDs green are blinking with 2Hz: During the start-up (OB 100) the status bar blinks for at least 3s.
Operation
LED yellow on: CPU is in STOP state.
LED red on: CPU is in error state.
LEDs green on: CPU is in RUN state without error.
LED red blinks with 1Hz and LED green is on: CPU is in RUN state with error/warning.
LED red on and LED green blinks with 1Hz: CPU is in STOP state, configured holding point reached.
LED red blinks with 1Hz and LED green blinks with 2Hz: Diagnostic messages detected during start-up.
LED red on and LED yellow on: CPU is in error state. There is a system error or an internal error has occurred.
Here a write access is made to the memory card. As long as the LEDs red and yellow are on, do not remove the
memory card.
LED yellow blinks with 2Hz: Hardware configuration is loaded.
LEDs green are blinking with 1Hz: Blinking test (started via configuration tool)
LED green on and LED green flickers: Access to the memory card in the RUN state.
LED red blinks with 1Hz and LED green flickers: Access to the memory card with CPU is in RUN state with error/
warning.
LED yellow flickers: Access to the memory card in STOP state.
Overall reset
LED yellow blinks with 1Hz: Overall reset is requested
LED yellow blinks with 2Hz: Overall reset is executed.
LED yellow on: Overall reset was successfully finished.
Factory reset
LED yellow blinks with 2Hz: Reset to factory setting is executed.
LED red blinks with 1Hz and LED yellow blinks with 1Hz: Reset to factory settings was finished without errors.
Please perform a power cycle!
Firmware update
LED red and LED yellow are alternately blinking with 1Hz: A new firmware is available on the memory card.
LED yellow blinks with 2Hz: A firmware update is in progress.
LED yellow flickers: Access the memory card during the firmware update.
LED red and LED yellow are blinking with 1Hz: Firmware update finished without error. Please perform a power
cycle!
LED red blinks with 1Hz: Error during Firmware update.
HB400 | CPU | M13-CCF0000 | en | 20-02 47

Structure > Slot for storage media
3.2.3.2 LEDs Ethernet PG/OP channel

X3/X4: LEDs
L/A S Description
Link/Activity Speed
green yellow
X The Ethernet PG/OP channel is physically connected to the Ethernet
interface.
X There is no physical connection.
X Blinking: Shows Ethernet activity.
The Ethernet interface of the Ethernet PG/OP channel has a transfer
rate of 100Mbit.
The Ethernet interface of the Ethernet PG/OP channel has a transfer
rate of 10Mbit.
not relevant: X
3.2.4 Memory management

General The CPU has an integrated memory. Information about the capacity of the memory may
be found at the front of the CPU. The memory is divided into the following parts:
n Load memory 128kbyte
n Code memory (50% of the work memory)
n Data memory (50% of the work memory)
n Work memory 64kbyte
– There is the possibility to extend the work memory to its maximum capacity
128kbyte by means of a VSC.
3.2.5 Slot for storage media

Overview In this slot you can insert the following storage media:
n VSD - VIPA SD-Card
– External memory card for programs and firmware.
n VSC - VIPASetCard
– External memory card (VSD) for programs and firmware with the possibility to
unlock optional functions like work memory and field bus interfaces.
– These functions can be purchased separately. Ä Chap. 4.16 ‘Deployment storage
media - VSD, VSC’ page 110
– To activate the corresponding card is to be installed and a Overall reset is to be
established. Ä Chap. 4.13 ‘Overall reset’ page 104
To avoid malfunctions, you should use memory cards of VIPA. These cor-
respond to the industrial standard. A list of the currently available VSD
respectively VSC can be found at www.vipa.com
48 HB400 | CPU | M13-CCF0000 | en | 20-02

Structure > Operating mode switch
3.2.6 Buffering mechanisms

The CPU has a capacitor-based mechanism to buffer the internal clock in case of power
failure for max. 30 days. With PowerOFF the content of the RAM is automatically stored
in the Flash (NVRAM).
CAUTION!
Please connect the CPU for approximately 1 hour to the power supply, so
that the internal buffering mechanism is loaded accordingly.
In case of failure of the buffer mechanism Date and Time 01.09.2009
00:00:00 set. Additionally, you receive a diagnostics message. Ä Chap.
4.20 ‘Diagnostic entries’ page 116
3.2.7 Operating mode switch

General
n With the operating mode switch you may switch the CPU between STOP and RUN.
n During the transition from STOP to RUN the operating mode START-UP is driven by
the CPU.
n Placing the switch to MR (Memory Reset), you request an overall reset with following
load from memory card, if a project there exists.
HB400 | CPU | M13-CCF0000 | en | 20-02 49

Option: Extension module EM M09 2x serial interface
3.3 Option: Extension module EM M09 2x serial interface

EM M09
Please note that the interface X2 MPI(PB) does not provide DC 24V,
which is necessary for some programming adapters!
X1 PtP (RS422/485) 9pin SubD jack (isolated):

Using the PtP functionality the RS485 interface is allowed to connect via serial point to
point connection to different source res. target systems.
n Protocols:
– ASCII
– STX/ETX
– 3964R
– USS
– Modbus master (ASCII, RTU)
n Serial bus connection
– Full-duplex Four-wire operation (RS422)
– Half-duplex Two-wire operation (RS485)
– Data transfer rate: max. 115 kBaud
Ä Chap. 10 ‘Option: PtP communication’ page 245
50 HB400 | CPU | M13-CCF0000 | en | 20-02

Option: Extension module EM M09 2x serial interface
X2 MPI(PB) 9pin SubD jack (isolated):

The interface supports the following functions, which are switch able:
n MPI (default / after overall reset)
The MPI interface serves for the connection between programming unit and CPU. By
means of this the project engineering and programming happens. In addition MPI
serves for communication between several CPUs or between HMIs and CPU.
Standard setting is MPI address 2.
n PROFIBUS DP slave (optional)
The PROFIBUS slave functionality of this interface can be activated by configuring
the sub module ‘MPI/DP’ of the CPU in the hardware configuration. Ä Chap. 11
‘Option: Deployment PROFIBUS communication’ page 259
To switch the interface X2 MPI(PB) to PROFIBUS functionality you have

to activate the according bus functionality by means of a VSC storage
media from VIPA. By plugging the VSC storage card and then an overall
reset the according functionality is activated. Ä Chap. 4.16 ‘Deployment
storage media - VSD, VSC’ page 110
LEDs
X1 PtP Description
TxD
green flickers Send activity
No send activity
X2 MPI(PB) Description
DE
green n Power supply Expansion module EM M09 available
n Slave is in DE (data exchange)
n Slave exchanges data with the master
n Slave is in RUN state
green flashes n LED flashes at PowerON of EM M09
n No power supply EM M09 available
n Slave has no configuration
HB400 | CPU | M13-CCF0000 | en | 20-02 51

Technical data > Technical data CPU
3.4 Technical data

3.4.1 Technical data CPU
Order no. M13-CCF0000
Type CPU M13C
Module ID -
Technical data power supply
Power supply (rated value) DC 24 V
Power supply (permitted range) DC 20.4...28.8 V
Reverse polarity protection ü
Current consumption (no-load operation) 120 mA
Current consumption (rated value) 360 mA
Inrush current 3A
I²t 0.1 A²s
Max. current drain at backplane bus 1A
Max. current drain load supply -
Power loss 7W
Technical data digital inputs
Number of inputs 16
Cable length, shielded 1000 m
Cable length, unshielded 600 m
Rated load voltage DC 24 V
Reverse polarity protection of rated load voltage ü
Current consumption from load voltage L+ (without load) 25 mA
Rated value DC 24 V
Input voltage for signal "0" DC 0...5 V
Input voltage for signal "1" DC 15...28.8 V
Input voltage hysteresis -
Signal logic input Sinking input
Frequency range -
Input resistance -
Input current for signal "1" 3 mA
Connection of Two-Wire-BEROs possible ü
Max. permissible BERO quiescent current 0.5 mA
Input delay of "0" to "1" 3 µs – 15 ms / 0.5 ms – 15 ms
Input delay of "1" to "0" 3 µs – 15 ms / 0.5 ms – 15 ms
Number of simultaneously utilizable inputs horizontal con- 16
figuration
52 HB400 | CPU | M13-CCF0000 | en | 20-02


Number of simultaneously utilizable inputs vertical configu- 16
ration
Input characteristic curve IEC 61131-2, type 1
Initial data size 16 Bit
Technical data digital outputs
Number of outputs 12
Cable length, unshielded 600 m
Rated load voltage DC 24 V
Reverse polarity protection of rated load voltage ü
Current consumption from load voltage L+ (without load) 20 mA
Total current per group, horizontal configuration, 40°C 6A
Total current per group, horizontal configuration, 60°C 6A
Total current per group, vertical configuration 6A
Output voltage signal "1" at min. current L+ (-0.8 V)
Output voltage signal "1" at max. current L+ (-0.8 V)
Output current at signal "1", rated value 0.5 A
Signal logic output Sourcing output
Output current, permitted range to 40°C 5 mA to 0.6 A
Output current, permitted range to 60°C 5 mA to 0.6 A
Output current at signal "0" max. (residual current) 0.5 mA
Output delay of "0" to "1" 2 µs / 30 µs
Output delay of "1" to "0" 3 µs / 175 µs
Minimum load current -
Lamp load 10 W
Parallel switching of outputs for redundant control of a load not possible
Parallel switching of outputs for increased power not possible
Actuation of digital input ü
Switching frequency with resistive load max. 1000 Hz
Switching frequency with inductive load max. 0.5 Hz
Switching frequency on lamp load max. 10 Hz
Internal limitation of inductive shut-off voltage L+ (-45 V)
Short-circuit protection of output yes, electronic
Trigger level 1A
Number of operating cycle of relay outputs -
Switching capacity of contacts -
HB400 | CPU | M13-CCF0000 | en | 20-02 53


Output data size 12 Bit
Technical data analog inputs
Number of inputs 2
Rated load voltage -
Reverse polarity protection of rated load voltage -
Current consumption from load voltage L+ (without load) -
Voltage inputs ü
Min. input resistance (voltage range) 100 kΩ
Input voltage ranges 0 V ... +10 V
Operational limit of voltage ranges +/-3.5%
Operational limit of voltage ranges with SFU -
Basic error limit voltage ranges +/-3.0%
Basic error limit voltage ranges with SFU -
Destruction limit voltage max. 30V
Current inputs -
Max. input resistance (current range) -
Input current ranges -
Operational limit of current ranges -
Operational limit of current ranges with SFU -
Basic error limit current ranges -
Radical error limit current ranges with SFU -
Destruction limit current inputs (electrical current) -
Destruction limit current inputs (voltage) -
Resistance inputs -
Resistance ranges -
Operational limit of resistor ranges -
Operational limit of resistor ranges with SFU -
Basic error limit -
Basic error limit with SFU -
Destruction limit resistance inputs -
Resistance thermometer inputs -
Resistance thermometer ranges -
Operational limit of resistance thermometer ranges -
Operational limit of resistance thermometer ranges with -
SFU
54 HB400 | CPU | M13-CCF0000 | en | 20-02


Basic error limit thermoresistor ranges -
Basic error limit thermoresistor ranges with SFU -
Destruction limit resistance thermometer inputs -
Thermocouple inputs -
Thermocouple ranges -
Operational limit of thermocouple ranges -
Operational limit of thermocouple ranges with SFU -
Basic error limit thermoelement ranges -
Basic error limit thermoelement ranges with SFU -
Destruction limit thermocouple inputs -
Programmable temperature compensation -
External temperature compensation -
Internal temperature compensation -
Technical unit of temperature measurement -
Resolution in bit 12
Measurement principle successive approximation
Basic conversion time 2 ms
Noise suppression for frequency 40 dB
Initial data size 4 Byte
Technical data analog outputs
Number of outputs -
Cable length, shielded -
Rated load voltage -
Reverse polarity protection of rated load voltage -
Current consumption from load voltage L+ (without load) -
Voltage output short-circuit protection -
Voltage outputs -
Min. load resistance (voltage range) -
Max. capacitive load (current range) -
Max. inductive load (current range) -
Output voltage ranges -
Operational limit of voltage ranges -
Basic error limit voltage ranges with SFU -
Destruction limit against external applied voltage -
Current outputs -
Max. in load resistance (current range) -
HB400 | CPU | M13-CCF0000 | en | 20-02 55


Max. inductive load (current range) -
Typ. open circuit voltage current output -
Output current ranges -
Operational limit of current ranges -
Radical error limit current ranges with SFU -
Destruction limit against external applied voltage -
Settling time for ohmic load -
Settling time for capacitive load -
Settling time for inductive load -
Resolution in bit -
Conversion time -
Substitute value can be applied -
Output data size -
Technical data counters
Number of counters 4
Counter width 32 Bit
Maximum input frequency 100 kHz
Maximum count frequency 400 kHz
Mode incremental encoder ü
Mode pulse / direction ü
Mode pulse ü
Mode frequency counter ü
Mode period measurement ü
Gate input available ü
Latch input available ü
Reset input available -
Counter output available ü
Load and working memory
Load memory, integrated 128 KB
Load memory, maximum 128 KB
Work memory, integrated 64 KB
Work memory, maximal 128 KB
Memory divided in 50% program / 50% data ü
Memory card slot SD/MMC-Card with max. 2 GB
Hardware configuration
Racks, max. 1
56 HB400 | CPU | M13-CCF0000 | en | 20-02


Modules per rack, max. 8
Number of integrated DP master -
Number of DP master via CP -
Operable function modules -
Operable communication modules PtP -
Operable communication modules LAN -
Status information, alarms, diagnostics
Status display yes
Interrupts yes, parameterizable
Process alarm yes, parameterizable
Diagnostic interrupt yes, parameterizable
Diagnostic functions yes, parameterizable
Diagnostics information read-out possible
Supply voltage display green LED
Group error display red LED
Channel error display red LED per group
Isolation
Between channels ü
Between channels of groups to 16
Between channels and backplane bus ü
Between channels and power supply -
Max. potential difference between circuits DC 75 V/ AC 50 V
Max. potential difference between inputs (Ucm) -
Max. potential difference between Mana and Mintern -
(Uiso)
Max. potential difference between inputs and Mana (Ucm) -
Max. potential difference between inputs and Mintern -
(Uiso)
Max. potential difference between Mintern and outputs -
Insulation tested with DC 500 V
Command processing times
Bit instructions, min. 0.02 µs
Word instruction, min. 0.02 µs
Double integer arithmetic, min. 0.02 µs
Floating-point arithmetic, min. 0.12 µs
Timers/Counters and their retentive characteristics
Number of S7 counters 512
HB400 | CPU | M13-CCF0000 | en | 20-02 57


S7 counter remanence adjustable 0 up to 256
S7 counter remanence adjustable C0 .. C7
Number of S7 times 512
S7 times remanence adjustable 0 up to 256
S7 times remanence adjustable not retentive
Data range and retentive characteristic
Number of flags 8192 Byte
Bit memories retentive characteristic adjustable adjustable 0 up to 256
Bit memories retentive characteristic preset MB0 .. MB15
Number of data blocks 1024
Max. data blocks size 64 KB
Max. local data size per execution level 4096 Byte
Blocks
Number of OBs 22
Number of FBs 1024
Number of FCs 1024
Maximum nesting depth per priority class 16
Maximum nesting depth additional within an error OB 4
Time
Real-time clock buffered ü
Clock buffered period (min.) 30 d
Accuracy (max. deviation per day) 10 s
Number of operating hours counter 8
Clock synchronization ü
Synchronization via MPI Master/Slave
Synchronization via Ethernet (NTP) no
Address areas (I/O)
Input I/O address area 2048 Byte
Output I/O address area 2048 Byte
Input process image maximal 2048 Byte
Output process image maximal 2048 Byte
Digital inputs 144
Digital outputs 140
Digital inputs central 144
Digital outputs central 140
Integrated digital inputs 16
58 HB400 | CPU | M13-CCF0000 | en | 20-02


Integrated digital outputs 12
Analog inputs 2
Analog outputs 0
Analog inputs, central 2
Analog outputs, central 0
Integrated analog inputs 2
Integrated analog outputs 0
Communication functions
PG/OP channel ü
Global data communication ü
Number of GD circuits, max. 8
Size of GD packets, max. 54 Byte
S7 basic communication ü
S7 basic communication, user data per job 76 Byte
S7 communication ü
S7 communication as server ü
S7 communication as client -
S7 communication, user data per job 160 Byte
Number of connections, max. 32
PWM data
PWM channels 2
PWM time basis 1 µs / 0.1 ms / 1 ms
Period length -
Minimum pulse width 0...0.5 * Period duration
Type of output Highside
Functionality Sub-D interfaces
Type X1
Type of interface RS422/485 isolated
Connector Sub-D, 9-pin, female
Electrically isolated ü
MPI -
MP²I (MPI/RS232) -
DP master -
DP slave -
Point-to-point interface ü
5V DC Power supply max. 90mA, isolated
HB400 | CPU | M13-CCF0000 | en | 20-02 59


24V DC Power supply -
Type X2
Type of interface RS485 isolated
MPI ü
MP²I (MPI/RS232) -
DP master -
DP slave optional
Point-to-point interface -
5V DC Power supply max. 90mA, isolated
24V DC Power supply -
Functionality MPI
PG/OP channel ü
Routing ü
Global data communication ü
S7 basic communication ü
S7 communication ü
Transmission speed, min. 19.2 kbit/s
Transmission speed, max. 12 Mbit/s
Functionality PROFIBUS slave
PG/OP channel ü
Routing ü
S7 communication ü
Direct data exchange (slave-to-slave communication) -
DPV1 ü
Transmission speed, min. 9.6 kbit/s
Transmission speed, max. 12 Mbit/s
Automatic detection of transmission speed ü
60 HB400 | CPU | M13-CCF0000 | en | 20-02


Transfer memory inputs, max. 244 Byte
Transfer memory outputs, max. 244 Byte
Address areas, max. 32
User data per address area, max. 32 Byte
Functionality RJ45 interfaces
Type X3/X4
Type of interface Ethernet 10/100 MBit Switch
Connector 2 x RJ45
PG/OP channel ü
Productive connections ü
Fieldbus -
Type -
Type of interface -
Connector -
Electrically isolated -
PG/OP channel -
Number of connections, max. -
Productive connections -
Fieldbus -
Point-to-point communication
PtP communication ü
Interface isolated ü
RS232 interface -
RS422 interface ü
RS485 interface ü
Transmission speed, min. 1200 bit/s
Transmission speed, max. 115.2 kbit/s
Cable length, max. 500 m
Point-to-point protocol
ASCII protocol ü
STX/ETX protocol ü
3964(R) protocol ü
HB400 | CPU | M13-CCF0000 | en | 20-02 61


RK512 protocol -
USS master protocol ü
Modbus master protocol ü
Modbus slave protocol ü
Special protocols -
Properties PROFINET I/O-Controller via PG/OP
Realtime Class -
Conformance Class PROFINET IO
Number of PN IO devices 8
IRT support -
Shared Device supported ü
MRP Client supported ü
Prioritized start-up -
Number of PN IO lines 1
Address range inputs, max. 2 KB
Address range outputs, max. 2 KB
Transmiting clock 1 ms
Update time 1 ms .. 512 ms
Isochronous mode -
Parallel operation as controller and I-Device ü
Properties PROFINET I/O controller
Realtime Class -
Conformance Class -
Number of PN IO devices -
IRT support -
Prioritized start-up -
Number of PN IO lines -
Address range inputs, max. -
Address range outputs, max. -
Transmiting clock -
Update time -
Isochronous mode -
Properties PROFINET I-Device via PG/OP
I/O Data range, max. 768 Byte
Update time 1 ms .. 512 ms
Mode as Shared I-Device -
62 HB400 | CPU | M13-CCF0000 | en | 20-02


Management & diagnosis via PG/OP
Protocols ICMP
DCP
LLDP / SNMP
NTP
Web based diagnosis ü
NCM diagnosis -
Ethernet communication via PG/OP
Number of productive connections via PG/OP, max. 2
Number of productive connections by Siemens NetPro, 2
max.
S7 connections BSEND, BRCV, GET, PUT, Connection of active and pas-
sive data handling
User data per S7 connection, max. 64 KB
TCP-connections FETCH PASSIV, WRITE PASSIV, Connection of passive
data handling
User data per TCP connection, max. 8 KB
ISO on TCP connections (RFC 1006) FETCH PASSIV, WRITE PASSIV, Connection of passive
data handling
User data per ISO connection, max. 8 KB
Ethernet open communication via PG/OP
Number of configurable connections, max. 2
ISO on TCP connections (RFC 1006) TSEND, TRCV, TCON, TDISCON
User data per ISO on TCP connection, max. 32 KB
TCP-Connections native TSEND, TRCV, TCON, TDISCON
User data per native TCP connection, max. 32 KB
User data per ad hoc TCP connection, max. 1460 Byte
UDP-connections TUSEND, TURCV
User data per UDP connection, max. 1472 Byte
WebVisu via PG/OP
WebVisu is supported ü
Max. number of connections WebVisu 4
WebVisu supports HTTP ü
WebVisu supports HTTPS ü
OPC UA server via PG/OP
OPC UA server is supported ü
Max. number of connections per interface 4
Services Data Access (Read, Write, Subscribe)
HB400 | CPU | M13-CCF0000 | en | 20-02 63


Security policies None, Basic128Rsa15, Basic256, Basic256Sha256
Authentication Anonymous, username and password
Housing
Material PPE / PPE GF10
Mounting Profile rail 35 mm
Mechanical data
Dimensions (WxHxD) 72 mm x 88 mm x 71 mm
Net weight 230 g
Weight including accessories 230 g
Gross weight 250 g
Environmental conditions
Operating temperature 0 °C to 60 °C
Storage temperature -25 °C to 70 °C
Certifications
UL certification in preparation
KC certification in preparation
64 HB400 | CPU | M13-CCF0000 | en | 20-02

Technical data > Technical data EM M09
3.4.2 Technical data EM M09

Order no. M09-0CB00
Type Micro Extension 2xRS485
Module ID -
Status information, alarms, diagnostics
Status display green LED
Interrupts no
Process alarm no
Diagnostic interrupt no
Diagnostic functions no
Diagnostics information read-out -
Supply voltage display none
Group error display -
Channel error display -
Housing
Material PPE / PPE GF10
Mounting Profile rail 35 mm
Mechanical data
Dimensions (WxHxD) 35 mm x 88 mm x 26 mm
Net weight 56 g
Weight including accessories 56 g
Gross weight 66 g
Environmental conditions
Operating temperature 0 °C to 60 °C
Storage temperature -25 °C to 70 °C
Certifications
UL certification in preparation
KC certification in preparation
HB400 | CPU | M13-CCF0000 | en | 20-02 65

Deployment CPU M13-CCF0000 VIPA System MICRO
Start-up behavior
4 Deployment CPU M13-CCF0000

4.1 Please note!
The following descriptions always refer to the usage in the Siemens

SIMATIC Manager. Information on usage in the VIPA SPEED7 Studio or
Siemens TIA Portal can be found here:
Ä Chap. 12 ‘Configuration with VIPA SPEED7 Studio’ page 271

Ä Chap. 13 ‘Configuration with TIA Portal’ page 298
4.2 Assembly
Information about assembly and cabling Ä Chap. 2 ‘Basics and

mounting’ page 12.
4.3 Start-up behavior

Turn on power supply n The CPU checks whether a project AUTOLOAD.WLD exists on the memory card. If
so, an overall reset is executed and the project is automatically loaded from the
memory card.
n The CPU checks whether a command file with the name VIPA_CMD.MMC exists on
the memory card. If so the command file is loaded from the memory card and the
commands are executed.
n After PowerON and CPU STOP the CPU checks if there is a *.pkb file (firmware file)
on the memory card. If so, this is shown by the status bar of the CPU and the firm-
ware may be installed by an update request. Ä Chap. 4.14 ‘Firmware update’
page 106
n The CPU checks if a previously activated VSC is inserted. If not, this is shown by the
status bar of the CPU and a diagnostics entry is released. The CPU switches to
STOP after 72 hours. With a just installed VSC activated functionalities remain acti-
vated. Ä Chap. 4.20 ‘Diagnostic entries’ page 116
After this the CPU switches to the operating mode, which is set on the operating mode
switch.
Delivery state In the delivery state the CPU is overall reset. After a STOP®RUN transition the CPU
switches to RUN without program.
66 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO Deployment CPU M13-CCF0000
Addressing > Default address assignment of the I/O part
4.4 Addressing
4.4.1 Overview
To provide specific addressing of the installed peripheral modules, certain addresses
must be allocated in the CPU. This address mapping is in the CPU as hardware configu-
ration. If there is no hardware configuration, depending on the slot, the CPU assigns
automatically peripheral addresses for digital in-/output modules starting with 0 and
analog modules are assigned to even addresses starting with 256.
4.4.2 Default address assignment of the I/O part

Sub module Input Access Assignment
address
AI5/AO2 800 WORD Analog input channel 0 (X6)
802 WORD Analog input channel 1 (X6)
Sub module Input Access Description

address
DI24/DO16 136 BYTE Digital input I+0.0 ... I+0.7 (X1)
137 BYTE Digital input I+1.0 ... I+1.7 (X5)

address
Counter 816 DINT Channel 0: Counter value / Frequency value
820 DINT Channel 1: Counter value / Frequency value
Sub module Output Access Description

address
DI24/DO16 136 BYTE Digital output Q+0.0 ... Q+0.7 (X2)
137 BYTE Digital output Q+1.0 ... Q+1.3 (X6)

address
Counter 816 DWORD reserved
820 DWORD reserved
824 DWORD reserved
828 DWORD reserved
HB400 | CPU | M13-CCF0000 | en | 20-02 67

Addressing > Option: Addressing periphery modules
4.4.3 Option: Addressing periphery modules

The CPU M13-CCF0000 provides an I/O area (address 0 ... 2047) and a process image
of the in- and outputs (each address default 0 ... 127). The size of the process image can
be preset via the parameterization. Ä Chap. 4.8 ‘Setting standard CPU parameters’
page 77
The process image is updated automatically when a cycle has been completed. The
process image is divided into two parts:
n process image to the inputs (PII)
n process image to the outputs (PIQ)
1 I/O area: 0 ... 127 (default)

2 I/O area: 0 ... 2047
3 Process image of the inputs (PII): 0 ... 127
4 Process image of the inputs (PII) max.: 2047
5 Process image of the outputs (PIQ): 0 ... 127
6 Process image of the outputs (PIQ) max.: 2047
Max. number of pluggable Up to 8 periphery modules can be connected to the CPU.

modules
Define addresses by hard- You may access the modules with read res. write accesses to the peripheral bytes or the
ware configuration process image. To define addresses a hardware configuration may be used. For this,
click on the properties of the according module and set the wanted address.
Automatic addressing If you do not like to use a hardware configuration, an automatic addressing is established.
Here the address assignment follows the following specifications:
n Starting with slot 1, the central plugged modules are assigned with ascending logical
addresses.
n The length of the memory area corresponds to the size of the process data of the
according module. Information about the sizes of the process data can be found in
the according manual of the module.
n The memory areas of the modules are assigned without gaps separately for input and
output area.
n Digital modules are mapped starting at address 0 and all other modules are mapped
starting from address 256.
n As soon as the mapping of digital modules exceeds the address 256, by regarding
the order, these are mapped starting from address 256.
68 HB400 | CPU | M13-CCF0000 | en | 20-02

Hardware configuration - CPU
4.5 Hardware configuration - CPU

Precondition n The configuration of the CPU takes place at the ‘hardware configurator’ of the Sie-
mens SIMATIC Manager V 5.5 SP2 and up.
n The configuration of the System MICRO CPU happens by means of a virtual
PROFINET IO device ‘VIPA MICRO PLC’ . The ‘VIPA MICRO PLC’ is to be installed
in the hardware catalog by means of the GSDML.
For project engineering a thorough knowledge of the Siemens SIMATIC

Manager and the Siemens hardware configurator is required!
Installing the IO device The installation of the PROFINET IO devices ‘VIPA MICRO PLC’ happens in the hard-
VIPA MICRO PLC ware catalog with the following approach:
1. Go to the service area of www.vipa.com.
2. Load from the download area at ‘Config files è PROFINET’ the according file for
your System MICRO.
3. Extract the file into your working directory.
4. Start the Siemens hardware configurator.
5. Close all the projects.
6. Select ‘Options è Install new GSD file’
7. Navigate to your working directory and install the according GSDML file.
ð After the installation according PROFINET IO device can be found at
‘PROFINET IO è Additional field devices è I/O è VIPA Micro System’
Proceeding In the Siemens SIMATIC Manager the following steps should be executed:
1. Start the Siemens hardware configurator with a new project.
2. Insert a profile rail from the hardware catalog.
3. Place at ‘Slot’ number 2 the CPU 314C-2 PN/DP (314-6EH04-0AB0 V3.3).
4. Click at the sub module ‘PN-IO’ of the CPU.

5. Select ‘Context menu è Insert PROFINET IO System’.
HB400 | CPU | M13-CCF0000 | en | 20-02 69

Hardware configuration - CPU
6. Use [New] to create a new subnet and assign valid IP address data for your
PROFINET system.
With firmware version V2.4.0 and up, you can access the Ethernet
PG/OP channel via this IP address data. The configuration via an
additional CP is no longer required, but still possible. Ä Chap. 4.7
‘Hardware configuration - Ethernet PG/OP channel’ page 72
7. Click at the sub module ‘PN-IO’ of the CPU and open with ‘Context menu
è Properties’ the properties dialog.
8. Enter at ‘General’ a ‘Device name’ . The device name must be unique at the
Ethernet subnet.
9. Navigate in the hardware catalog to the directory ‘PROFINET IO

è Additional field devices è I/O è VIPA Micro System’ and connect the IO device
M13-CCF0000 to your PROFINET system.
ð In the slot overview of the PROFINET IO device ‘VIPA MICRO PLC’ the CPU is
already placed at slot 0.
70 HB400 | CPU | M13-CCF0000 | en | 20-02

Hardware configuration - System MICRO modules
4.6 Hardware configuration - System MICRO modules

System MICRO backplane To connect System MICRO modules, the CPU has a backplane bus, which is supplied by
bus the CPU. Here up to 8 System MICRO modules can be connected.
Proceeding 1. Perform, if not already done, a hardware configuration for the CPU. Ä Chap. 4.5
‘Hardware configuration - CPU’ page 69
2. Starting with slot 1 place in the slot overview of the PROFINET IO device ‘VIPA
MICRO PLC’ your System MICRO modules in the plugged sequence.
3. Parameterize if necessary the modules and assign valid addresses, so that they
can directly be addressed.
HB400 | CPU | M13-CCF0000 | en | 20-02 71

Hardware configuration - Ethernet PG/OP channel
4.7 Hardware configuration - Ethernet PG/OP channel

Overview
Please note!
– At the first commissioning respectively after a reset to factory setting
the Ethernet interface has no IP address.
– For online access, you have to assign valid IP address data to it by
means of "Initialization".
– After initialization, you can transfer the IP address data to your
project.
The CPU has an integrated Ethernet PG/OP channel. This channel allows you to pro-
gram and remote control your CPU.
is supported.
– Device website, where you can find information on firmware status, connected
Assembly and commis- 1. Install your System MICRO with your CPU.
sioning
2. Wire the system by connecting cables for voltage supply and signals.
3. Connect the one of the Ethernet jacks (X3, X4) of the Ethernet PG/OP channel to
Ethernet.
4. Switch on the power supply.
ð After a short boot time the CP is ready for communication. It possibly has no IP
address data and requires an initialization.
72 HB400 | CPU | M13-CCF0000 | en | 20-02

Hardware configuration - Ethernet PG/OP channel > Take IP address parameters in project
"Initialization" via PLC The initialization via PLC functions takes place with the following proceeding:
functions
Determine the current Ethernet (MAC) address of your Ethernet PG/OP channel.
This can be found at the front of your CPU with the name "MAC PG/OP: ...".
X3 PG/OP
X4 PG/OP
MAC PG/OP: 00-20-D5-77-05-10
Assign IP address param- You get valid IP address parameters from your system administrator. The assignment of
eters the IP address data happens online in the Siemens SIMATIC Manager starting with ver-
sion V 5.5 & SP2 with the following proceeding:
1. Start the Siemens SIMATIC Manager and set via ‘Options
è Set PG/PC interface’the access path to ‘TCP/IP -> Network card ....’ .
2. Open with ‘PLC è Edit Ethernet Node n’ the dialog window with the same name.
3. To get the stations and their MAC address, use the [Browse] button or type in the
MAC Address. The Mac address may be found at the 1. label beneath the front flap
of the CPU.
4. Choose if necessary the known MAC address of the list of found stations.
5. Either type in the IP configuration like IP address, subnet mask and gateway.
6. Confirm with [Assign IP configuration].
ð Direct after the assignment the Ethernet PG/OP channel may be reached online
by these address data. The value remains as long as it is reassigned, it is over-
written by a hardware configuration or an factory reset is executed.
4.7.1 Take IP address parameters in project

2 variants for configura- From firmware version V2.4.0 and up, you have the following options for configuring the
tion Ethernet PG/OP channel:
n Configuration via integrated CPU interface (firmware version V2.4.0 and up only).
n Configuration via additional CP (all firmware versions).
HB400 | CPU | M13-CCF0000 | en | 20-02 73

4.7.1.1 Configuration via integrated CPU interface

Proceeding From firmware version V2.4.0 this variant for configuration is recommended. The fol-
lowing advantages result:
n The configuration becomes clearer, because the periphery modules and the
PROFINET IO devices are configured on the PROFINET line of the CPU and no addi-
tional CP is to be configured.
n There are no address collisions, because the S7 addresses for all components are
assigned from the address area of the CPU.
Unless during the hardware configuration of the CPU Ä 69 there was no IP address data
assigned yet or these are to be changed, the configuration happens to the following pro-
ceeding, otherwise the Ethernet PG/OP channel is configured.
1. Open the Siemens hardware configurator and, if not already done, configure the
Siemens CPU 314C-2 PN/DP (314-6EH04-0AB0 V3.3).
2. Open the PROFINET Properties dialog box of the CPU by double-clicking ‘PN-IO’ .
3. Click at ‘General’ .
4. At ‘Properties’ , enter the previously assigned IP address data and a subnet. The IP
address data are not accepted without subnet assignment!
5. Transfer your project.
1 Ethernet PG/OP channel
74 HB400 | CPU | M13-CCF0000 | en | 20-02

4.7.1.1.1 Time-of-day synchronization

NTP method In the NTP mode (Network Time Protocol) the module sends as client time-of-day queries
at regular intervals to all configured NTP servers within the sub net. You can define up to
4 NTP server. Based on the response from the servers, the most reliable and most exact
time-of-day is determined. Here the time with the lowest stratum is used. Stratum 0 is the
time standard (atomic clock). Stratum 1 are directly linked to this NTP server. Using the
NTP method, clocks can be synchronized over subnet boundaries. The configuration of
the NTP servers is carried out in the Siemens SIMATIC Manager via the CP, which is
already configured.
1. Open the Properties dialog by double-clicking ‘PN-IO’ .

2. Select the tab ‘Time-of-day synchronization’ .
3. Activate the NTP method by enabling ‘Activate NTP time-of-day synchronization’ .
4. Click at [Add] and add the corresponding NTP server.
5. Set the ‘Update interval’ you want. Within this interval, the time of the module is
synchronized once.
6. Close the dialog with [OK].
7. Save and transfer your project to the CPU.
ð After transmission, the NTP time is requested by each configured time server
and the best response for the time synchronization is used.
Please note that although the time zone is evaluated, an automatic

changeover from winter to summer time is not supported. Industrial sys-
tems with time-of-day synchronization should always be set in accord-
ance to the winter time.
With the FC 61 you can determine the local time in the CPU. More infor-
mation about the usage of this block may be found in the manual
"SPEED7 Operation List" from VIPA.
4.7.1.2 Configuration via additional CP

Proceeding This is the conventional variant for configuration and is supported by all firmware ver-
sions. If possible, always use the configuration via the internal interface, otherwise the fol-
lowing disadvantages result:
n Address overlaps are not recognized in the Siemens SIMATIC Manager.
n For PROFINET devices only the address range 0 ... 1023 is available.
n The addresses of the PROFINET devices are not checked with the address range of
the CPU by the Siemens SIMATIC Manager for address overlaps.
HB400 | CPU | M13-CCF0000 | en | 20-02 75

The configuration happens according to the following procedure:

1. Open the Siemens hardware configurator and, if not already done, configure the
Siemens CPU 314C-2 PN/DP (314-6EH04-0AB0 V3.3).
2. Place for the Ethernet PG/OP channel at slot 4 the Siemens CP 343-1 (SIMATIC
300 \ CP 300 \ Industrial Ethernet \CP 343-1 \ 6GK7 343-1EX30 0XE0 V3.0).
CAUTION!
Please configure the diagnostic addresses of the CP343-1EX30 for
‘PN-IO’ , ‘Port1’ and ‘Port2’ so that no overlaps occur in the
periphery input area. Otherwise your CPU can not start-up and you
receive the diagnostic entry 0xE904. These addresses overlaps are
not recognized by the Siemens SIMATIC Manager.
3. Open the Properties dialog by double-clicking on ‘PN-IO’ of the CP 343-1EX30 and

enter the previously assigned IP address data and a subnet for the CP at
‘Properties’ . The IP address data are not accepted without subnet assignment!
76 HB400 | CPU | M13-CCF0000 | en | 20-02

Setting standard CPU parameters > Parameterization via Siemens CPU

already configured.
1. Open the properties dialog via double-click on the CP 343-1EX30.

2. Select the tab ‘Time-of-day synchronization’ .
3. Activate the NTP method by enabling ‘Activate NTP time-of-day synchronization’ .
4. Click at [Add] and add the corresponding NTP server.
5. Select your ‘Time zone’ . In the NTP method, UTC (Universal Time Coordinated) is
generally transmitted; this corresponds to GMT (Greenwich Mean Time). By config-
uring the local time zone, you can set a time offset to UTC.
synchronized once.
7. Close the dialog with [OK].

4.8 Setting standard CPU parameters

4.8.1 Parameterization via Siemens CPU
Parametrization via Sie- Since the CPU from VIPA is to be configured as Siemens CPU 314C-2 PN/DP
mens CPU 314-6EH04 (314-6EH04-0AB0 V3.3) in the Siemens hardware configurator, the standard parameters
of the VIPA CPU may be set with "Object properties" of the CPU 314C-2 PN/DP during
hardware configuration. Via a double-click on the CPU 314C-2 PN/DP the parameter
window of the CPU may be accessed. Using the registers you get access to every
standard parameter of the CPU.
HB400 | CPU | M13-CCF0000 | en | 20-02 77

Setting standard CPU parameters > Parameter CPU
4.8.2 Parameter CPU

Supported parameters The CPU does not evaluate each parameter, which may be set at the hardware configu-
ration. The parameters of the following registers are not supported: Synchronous cycle
interrupts, communication and web. The following parameters are currently supported:
General n Short description

– The short description of the Siemens CPU is CPU 314C-2 PN/DP
(314-6EH04-0AB0 V3.3).
n Order No. / Firmware
– Order number and firmware are identical to the details in the "hardware catalog"
window.
n Name
– The Name field provides the short description of the CPU.
– If you change the name the new name appears in the Siemens SIMATIC Man-
ager.
n Plant designation
– Here is the possibility to specify a plant designation for the CPU.
– This plant designation identifies parts of the plant according to their function.
– Its structure is hierarchic according to IEC 81346-1.
n Location designation
– The location designation is part of the resource designation.
– Here the exact location of your module within a plant may be specified.
n Comment
– In this field information about the module may be entered.
Startup n Startup when expected/actual configuration differs

– If the checkbox for ‘Startup when expected/actual configuration differ’ is dese-
lected and at least one module is not located at its configured slot or if 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.
n Monitoring time for ready message by modules [100ms]
– This operation specifies the maximum time for the ready message of every con-
figured module after PowerON.
– Here connected PROFIBUS DP slaves are also considered until they are parame-
terized.
– If the modules do not send a ready message to the CPU by the time the moni-
toring time has expired, the actual configuration becomes unequal to the preset
configuration.
n Monitoring time for transfer of parameters to modules [100ms]
– The maximum time for the transfer of parameters to parameterizable modules.
– Here connected PROFINET IO devices also considered until they are parameter-
ized.
– If not every module has been assigned parameters by the time this monitoring
time has expired; the actual configuration becomes unequal to the preset configu-
ration.
78 HB400 | CPU | M13-CCF0000 | en | 20-02

Cycle / Clock memory n Update OB1 process image cyclically

– This parameter is not relevant.
n Scan cycle monitoring time
– Here the scan cycle monitoring time in milliseconds may be set.
– If the scan 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
n Minimum scan cycle time
– This parameter is not relevant.
n Scan cycle load from Communication
– Using this parameter you can control the duration of communication processes,
which always extend the scan cycle time so it does not exceed 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 influ-
enced by asynchronous events (e.g. hardware interrupts) as well.
n Size of the process image input/output area
– Here the size of the process image max. 2048 for the input/output periphery may
be fixed (default: 256).
n OB85 call up at I/O access error
– The preset reaction of the CPU may be changed to an I/O access error that
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.
n Clock memory
– Activate the check box if you want to use clock memory and enter the number of
the memory byte.
The selected memory byte cannot be used for temporary data storage.
Retentive Memory n Number of Memory bytes from MB0

– Enter the number of retentive memory bytes from memory byte 0 onwards.
n Number of S7 Timers from T0
– Enter the number of retentive S7 timers from T0 onwards. Each S7 timer occu-
pies 2bytes.
n Number of S7 Counters from C0
– Enter the number of retentive S7 counter from C0 onwards.
n Areas
– This parameter is not supported.
Interrupts n 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 n Priority

– This value is fixed to 2.
n Active
– By enabling ‘Active’ the time-of-day interrupt function is enabled.
HB400 | CPU | M13-CCF0000 | en | 20-02 79

n 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.
n Start date/time
– Enter date and time of the first execution of the time-of-day interrupt.
n Process image partition
Cyclic interrupts n Priority

– Here the priorities may be specified according to which the corresponding cyclic
interrupt is processed.
n Execution
– Enter the time intervals in ms, in which the watchdog interrupt OBs should be pro-
cessed.
– The start time for the clock is when the operating mode switch is moved from
STOP to RUN.
n 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.
n Process image partition
Diagnostics/Clock n Report cause of STOP

– Activate this parameter, if the CPU should report the cause of STOP to PG
respectively OP on transition to STOP.
n Number of messages in the diagnostics buffer
– This parameter is ignored. The CPU always has a diagnostics buffer (circular
buffer) for 100 diagnostics messages.
n Synchronization type
– Here you specify whether clock should synchronize other clocks or not.
– as slave: The clock is synchronized by another clock.
– as master: The clock synchronizes other clocks as master.
– none: There is no synchronization
n Time interval
– Time intervals within which the synchronization is to be carried out.
n Correction factor
– Lose or gain in the clock time may be compensated within a 24 hour period by
means of the correction factor in ms.
– If the clock is 1s slow after 24 hours, you have to specify a correction factor of
"+1000" ms.
80 HB400 | CPU | M13-CCF0000 | en | 20-02

Protection n 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
HB400 | CPU | M13-CCF0000 | en | 20-02 81

Setting VIPA specific CPU parameters
4.9 Setting VIPA specific CPU parameters

Overview Except of the VIPA specific CPU parameters the CPU parametrization takes place in the
parameter dialog of the CPU 314C-2 PN/DP (314-6EH04-0AB0 V3.3) from Siemens.
After the hardware configuration of the CPU you can set the parameters of the CPU in
the virtual IO device ‘VIPA MICRO PLC’ . Via double-click at ‘VIPA MICRO PLC M13-
CCF0000’ the properties dialog is opened.
Here the following parameters may be accessed:

n Diagnostics
– Diagnostics interrupt DI power section supply
– Diagnostics interrupt DO power section supply
– Diagnostics interrupt DO short circuit/overload
n Retentive data
– Additional retentive memory, timer respectively counter
n OB
– Call OB 80 on cyclic interrupt
n Miscellaneous
– PN MultipleWrite
– Free Module Mapping Ä 84
– Reduced PDU size
n Access settings Ä 89
CPU
– Activation of interfaces and ports
– Activation of protocols
82 HB400 | CPU | M13-CCF0000 | en | 20-02

Setting VIPA specific CPU parameters
Parameter The following parameters may be accessed by means of the properties dialog of the
CPU.
n Diagnostics interrupt (default: deactivated)
– Diagnostic interrupt DI power section supply
Error: 3L+ (Dc 24v power section supply) missing respectively < 19 V
– Diagnostic interrupt DO power section supply
Error: 4L+ (DC 24V DO power section supply) missing respectively < 19 V
– Diagnostics interrupt DO short circuit/overload
Error: Short circuit or overload of a digital output respectively current exceeds
0.5A
Retentive data
n Additional retentive memory
– Here enter the number of memory bytes. With 0 the value ‘Retentive memory
è Number of memory bytes starting with MB0’ is set, which is pre-set at the
parameters of the Siemens CPU.
– Range of values: 0 (default) ... 8192
n Additional retentive timer
– Enter the number of S7 timers. With 0 the value ‘Retentive memory
è Number S7 timers starting with T0’ is set, which is pre-set at the parameters of
the Siemens CPU.
n Additional retentive counter
– Enter the number of S7 counter. With 0 the value ‘Retentive memory
è Number S7 counters starting with C0’ is set, which is pre-set at the parameters
of the Siemens CPU.
OB
n OB 80 for cyclic interrupt error
– Here you can set for which cyclic interrupt OB 80 (time error) should be called.
– Range of values: Deactivated (default), selection of the corresponding OB
Miscellaneous
n PN MultipleWrite
– In the activated state, parameter record sets are combined at PROFINET to one
or more Ethernet frames during the connection setup. This speeds up the connec-
tion setup, since a separate Ethernet frame is not used for each parameter record
set.
n Free Module Mapping Ä 84
– When activated, you can use your CPU in different hardware variants.
– You specify the mapping at runtime with record set 0x7F.
n Reduced PDU size
– When activated, the PDU size is reduced accordingly.
– For some protocols, some configuration tools require a reduced PDU size. For
example, in the Siemens TIA Portal for variable forcing, the PDU size must be
reduced. For the processing of single steps at several breakpoints, the PDU size
must also be reduced.
Access settings Ä 89
n When activated, you have access to the interface or the corresponding communica-
tion protocol.
n By default, there is no access restriction.
HB400 | CPU | M13-CCF0000 | en | 20-02 83

Setting VIPA specific CPU parameters > Free Module Mapping (FMM)
4.9.1 Free Module Mapping (FMM)

4.9.1.1 Overview
n With FMM you can use your CPU in different hardware variants without adapting your
user program. You only have to adapt the FMM configuration in the CPU when config-
uring the hardware variants. Here you have the following possibilities:
– Modules from the target configuration can be divided in any order to the slots of
the actual configuration.
– Modules from the target configuration may be missing in the actual configuration.
– Individual slots of the target configuration can be deactivated, on which modules
are located in the actual configuration.
n FMM is a functionality of VIPA and is only supported by VIPA modules.
n By default, FMM is disabled. To use FMM mapping, you must enable the CPU param-
eter ‘Free Module Mapping’ .
n For the FMM the mapping of the slots is to be specified via the record set 0x7F.
n For commissioning, you have to enable the parameter ‘Startup when expected/actual
configuration differs’ in your CPU.
n If FMM is activated and configured correctly, the system reacts as follows:
– During start-up, no target/actual difference of the hardware is diagnosed.
– Output data of missing modules are ignored and not output.
– Input data of missing modules are set to 0.
84 HB400 | CPU | M13-CCF0000 | en | 20-02

4.9.1.2 FMM configuration

Configuration n The mapping of the modules is defined as configuration by the 64byte record set
0x7F.
n The data record is retentively stored in the CPU.
n The record set must be transferred to the CPU by the user program by means of a
write command.
n With the record set read command parts of the active configuration can be read. You
have always to write the complete record set.
n Each written and valid configuration is only saved if a difference to the existing config-
uration exists.
Record set 0x7F Record set 0x7F

Byte 0 1 2 3 ... 63
Mapping
n The record 0x7F has a length of 64Byte, where Byte 0 ... 63 corresponds to the slot
1 ... 64 of the target configuration.
n For the FMM configuration, you must specify for each used slot of the target configu-
ration at ‘Mapping’ the corresponding value that corresponds to the actual configura-
tion.
The following values can be entered at Mapping:
n 0 (0x00) - module is ignored
– If modules of the target configuration are to be ignored, the value 0x00 must be
used. In this way, gaps can be projected.
n 1 ... 64 (0x01 ... 0x40) - position of the module in the actual configuration
– ‘Mapping’ corresponds to the value of Slotactual i.e. the slot of the actual configura-
tion on which the module of the target configuration is located.
n 255 (0xFF) - virtual module
– If a module from the target configuration is missing, for Mapping the value 255 for
"virtual module" is to be used.
– Behaviour of a virtual module:
- The input area always has the value 0, regardless of its size.
- The writing to the output area has no effect.
Commissioning The target configuration serves as template for the configuration of hardware variants.
1. Configure your system with a hardware configuration as target configuration and
create your user program. The target configuration represents a superset of all
available hardware variants.
2. Activate the parameter ‘Free Module Mapping’ in your CPU.
3. Activate the parameter ‘Startup when expected/actual configuration differs’ in your
CPU.
4. Create the configuration by defining the deviation of the actual and target configura-
tion for the current hardware configuration in record set 0x7F.
5.
Transfer this record set via write command to your CPU.
n For this use SFB 53 or SFB 58.
n The address to be used is the diagnostic address of the CPU in the virtual IO
device ‘VIPA MICRO CPU’ .
ð The configuration is permanently stored in the CPU and immediately active.
HB400 | CPU | M13-CCF0000 | en | 20-02 85

4.9.1.3 Examples
(1): Target configuration Slottarget

1
2
3
4
5
6
Slottarget - The mapping always refers to the slot of the target configuration.
Based on the target configuration, the following examples show how to determine the
mapping values for the hardware variants.
4.9.1.3.1 Examples of hardware variants

Variant 1: Same type and number of modules but reversed slots
(1): Target configuration Slottarge Slotactua Record set 0x7F

(2): Actual configuration t l
Byte Mapping
1 2 0 0x02
2 1 1 0x01
3 3 2 0x03
4 5 3 0x05
5 6 4 0x06
6 4 5 0x04
Determination of Mapping values of record set 0x7F:

n Byte 0: The module of Slottarget = 1 is in the actual configuration at Slotactual = 2 à Mapping = 0x02
Slotactual - Slot of the actual configuration on which the module of the target configura-
tion is located.
Mapping - For variant 1, Mapping corresponds to Slotactual, i.e. slot of the actual configu-
ration on which the module of the target configuration is located.
86 HB400 | CPU | M13-CCF0000 | en | 20-02

Variant 2: Reversed slots and modules are missing

Byte Mapping
1 1 0 0x01
2 - 1 0xFF
3 2 2 0x02
4 3 3 0x03
5 4 4 0x04
6 - 5 0xFF

n Byte 1: The module of Slottarget = 2 is not available in the actual configuration à Mapping = 0xFF
n Byte 5: The module of Slottarget = 6 is not available in the actual configuration à Mapping = 0xFF
tion is located.
Mapping - For variant 2, Mapping corresponds to the value of Slotactual , i.e. slot of the
actual configuration on which the module of the target configuration is
located. If a module from the target configuration is missing, for Mapping the
value 0xFF for "virtual module" is to be used.
HB400 | CPU | M13-CCF0000 | en | 20-02 87

Variant 3: Modules are ignored

Byte Mapping
1 empty 0 0x00
2 empty 1 0x00
3 3 2 0x03
4 4 3 0x04
5 5 4 0x05
6 6 5 0x06

n Byte 0: The module of Slottarget = 1 is ignored in the actual configuration à Mapping = 0x00
n Byte 1: The module of Slottarget = 2 is ignored in the actual configuration à Mapping = 0x00
tion is located.
Mapping - For variant 3, Mapping corresponds to the value of Slotactual , i.e. slot of the
actual configuration on which the module of the target configuration is
located. If modules of the target configuration are to be ignored, for Mapping
the value 0x00 is to be used.
The presence of gaps in the System MICRO is not allowed! But you can
place modules and define them via the configuration as empty slot for the
target hardware configuration.
88 HB400 | CPU | M13-CCF0000 | en | 20-02

Project transfer
4.9.2 Access settings

Overview n The ‘Access setting’ allows you to disable access to ports or protocols.
n The CPU has an integrated Device web page that shows information about the
access ways via ‘Access Ways’ . Ä Chap. 4.11.1 ‘Device web page CPU’ page 93
Ethernet Port Here you can disable individual Ethernet interfaces.
Please note that by disabling e.g. the Ethernet PG/OP channel after
transferring the hardware configuration, the CPU can no longer be config-
ured via this Ethernet PG/OP channel. The access setting can be reset
by an overall reset.
Ethernet protocol Here you can disable Ethernet protocols. If a protocol is disabled, requests via the disa-
bled protocol will be rejected.
n TCP/UDP/IP services
– NTP protocol - protocol for time synchronization between the stations.
– OPC UA - protocol for access to an OPC UA project in the CPU.
– Open communication - protocol for communication via the user program when
using handling blocks.
– Device WebSite - protocol for access to the integrated web server.
– Web Visu - protocol for access to the Web visualization in the CPU, which can be
configured accordingly.
n S7 connections
– PG/OP protocol - protocol for PG/OP communication via Siemens S7 connec-
tions.
– PG/OP Routing - routing requests via Siemens S7 connections.
– NetPro connections - protocol for communication between PLC systems based on
Siemens STEP®7 by means of configured communication connections.
n Other services
– DCP - frame for determining accessible nodes on PROFINET
– LLDP - frame for determining the topology on PROFINET
– Field bus PN - protocols for communication via PROFINET
MPI/PB protocol via X3 Here you can deactivate protocols for the MPI(PB) interface X3. If a protocol is disabled,
requests via the disabled protocol will be rejected.
n MPI(PB) PG/OP protocol - protocol for PG/OP communication via the MPI(PB) inter-
face X3.
n MPI(PB) Routing - routing requests via the MPI(PB) interface X3.
n Global data communication - Global data communication - protocol for cyclic data
exchange between CPUs via the MPI interface.
4.10 Project transfer

Overview There is the following possibility for project transfer into the CPU:
n Transfer via Ethernet
n Transfer via memory card
n Option: Transfer via MPI Ä Chap. 4.10.3 ‘Option: Transfer via MPI’ page 91
HB400 | CPU | M13-CCF0000 | en | 20-02 89

Project transfer > Transfer via memory card
4.10.1 Transfer via Ethernet

Initialization So that you may access the according Ethernet interface you have to assign IP address
parameters by means of the "initialization".
n X3/X4: Ethernet PG/OP channel
– Ä Chap. 4.7 ‘Hardware configuration - Ethernet PG/OP channel’ page 72
Transfer 1. For the transfer, connect, if not already done, the appropriate Ethernet port to your
Ethernet.
2. Open your project with the Siemens SIMATIC Manager.
3. Set via ‘Options è Set PG/PC Interface’ the access path to "TCP/IP ® Network
card .... ".
4. Click to ‘PLC è Download’ Download ® the dialog "Select target module" is
opened. Select your target module and enter the IP address parameters of the
Ethernet PG/OP channel for connection. Provided that no new hardware configura-
tion is transferred to the CPU, the entered Ethernet connection is permanently
stored in the project as transfer channel.
5. 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.
4.10.2 Transfer via memory card

Proceeding transfer via The memory card serves as external storage medium. There may be stored several proj-
memory card ects and sub-directories on a memory card. Please regard that your current project is
stored in the root directory and has one of the following file names:
n S7PROG.WLD
n AUTOLOAD.WLD
1. Start the Siemens SIMATIC Manager with your project
2. Create with ‘File è Memory Card File è New’ a new wld file.
3. Copy the blocks from the project blocks folder and the System data into the wld file.
4. Copy the wld file at a suited memory card. Plug this into your CPU and start it
again.
ð The transfer of the application program from the memory card into the CPU
takes place depending on the file name after an overall reset or PowerON.
S7PROG.WLD is read from the memory card after overall reset.
AUTOLOAD.WLD is read from the memory card after PowerON.
The flickering of the yellow LED of the status bar of the CPU
marks the active transfer. Please regard that your user memory serves for
enough space for your user program, otherwise your user program is not com-
pletely loaded and the red LED of the status bar lights up.
90 HB400 | CPU | M13-CCF0000 | en | 20-02

Project transfer > Option: Transfer via MPI
4.10.3 Option: Transfer via MPI

General For the transfer via MPI the use of the optionally available extension module EM M09 is
required. The extension module provides the interface X2: MPI(PB) with fixed pin assign-
ment. Ä Chap. 2.4 ‘Mounting’ page 16
Net structure 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 deliv-
ered with MPI address 2.
MPI programming cable The MPI programming cables are available at VIPA in different variants. The cables pro-
vide 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 termi-
nating 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 sup-
plied. Otherwise it may cause interferences on the bus.
1 MPI programming cable

2 Activate the terminating resistor via switch
3 MPI network
Proceeding enabling the A hardware configuration to enable the MPI interface is not necessary. By installing the
interface extension module EM M09 the MPI interface is enabled.
1. Turn off the power supply.
2. Mount the extension module. Ä Chap. 2.4 ‘Mounting’ page 16
HB400 | CPU | M13-CCF0000 | en | 20-02 91

Project transfer > Option: Transfer via MPI

ð After a short boot time the interface X2 MPI(PB) is ready for MPI communica-
tion with the MPI address 2.
Approach transfer via MPI 1. Connect your PC to the MPI jack of your CPU via a MPI programming cable.
interface
2. Load your project in the SIMATIC Manager from Siemens.
3. Choose in the menu ‘Options è Set PG/PC interface’.
4. Select in the according list the "PC Adapter (MPI)"; if appropriate you have to add it
first, then click on [Properties].
5. Set in the register MPI the transfer parameters of your MPI net and type a valid
address.
6. Switch to the register Local connection.
7. Set the COM port of the PCs and the transfer rate 38400baud for the MPI program-
ming cable.
8. Transfer your project via ‘PLC è Load to module’ via MPI to the CPU and save it
with ‘PLC è Copy RAM to ROM’ on a memory card if one is plugged.
92 HB400 | CPU | M13-CCF0000 | en | 20-02

Accessing the web server > Device web page CPU
4.11 Accessing the web server

Overview The CPU has a web server integrated. This provides access to:
n Device web page
n OPC UA project Ä Chap. 4.11.1.1.1 ‘Tab: ‘OPC UA’ ’ page 96
n WebVisu project Ä Chap. 4.11.1.1.2 ‘Tab: ‘WebVisu’ ’ page 97
4.11.1 Device web page CPU

Overview n Dynamic web page, which exclusively outputs information.
n On the device web page you will find information about your CPU, the connected
modules and your WebVisu project.
– CPU
– the connected modules
– OPC UA project
– WebVisu project
n The shown values cannot be changed.
n Access is via the IP address of the Ethernet PG/OP channel.
n You can access the IP address with a web browser.
It is assumed that there is a connection between PC and CPU with web

browser via the Ethernet PG/OP channel. This may be tested by Ping to
the IP address of the Ethernet PG/OP channel.
4.11.1.1 Web page with selected CPU

Tab: ‘Info’
Name Value
Ordering Info M13-CCF0000 Order number of the CPU
Serial ... Serial number of the CPU
Version 01V... Version number of the CPU
HW Revision 01 CPU hardware revision
HB400 | CPU | M13-CCF0000 | en | 20-02 93

Name Value
Software 3.0.0 CPU firmware version
Package Pb000292.pkb File name for the firmware update
[Expert View] takes you to the advanced "Expert View".
Runtime Information CPU
Operation Mode RUN Mode

Mode Switch RUNP
System Time 14.03.19 08:34:14:486 Date, time
Up Time 0 days 02 hrs 07 min 08 sec Time to change the operating mode
Last Change to RUN n/a

Last Change to STOP 14.03.19 16:09:03:494
OB1-Cycle Time cur = 0us, min = 0us, max = 0us, Cyclic time:
avg = 0us
min = minimum
cur = current
max = maximum
avg = average
Interface Information Interface
X1/X5 DI 16 Address 136..137 Digital input

AI 2 Address 800..803 Analog input
Counter Address 816..831 Counter
X2/X6 DO 12 Address 136..137 Digital output
Counter Address 816..831 Counter
X3 PG/OP Ethernet Port 1 Address 2025 ... 2040 Ethernet PG/OP channel
X4 PG/OP Ethernet Port 2 Address 2025 ... 2040
Serial X1 PTP PtP: Point to point operation (RS422/485)
Serial X2 MPI Address 2047 Operating mode RS485

MPI: MPI operation
or
PROFIBUS DP slave mode
Card Information
No card inserted Information about the memory card
Active Feature Set Information
No feature activated Information about enabled functions
94 HB400 | CPU | M13-CCF0000 | en | 20-02

Memory Usage CPU
free used max Information on the memory expansion
LoadMem 128.0 kByte 0 byte 128.0 kByte Load memory, working memory (code/data)
WorkMemCode 32.0 kByte 0 byte 32.0 kByte

WorkMemData 32.0 kByte 0 byte 32.0 kByte
PG/OP Network Information Ethernet PG/OP channel
Device Name Onboard PG/OP Name

IP Address 172.20.139.76 Address information
Subnet Mask 255.255.255.0
Gateway Address 172.20.139.76
MAC Address 00:20:D5:02:6C:27
Link Mode X3 100 Mbps - Full Duplex Link Mode and speed
Link Mode X4 Not Available
CPU Firmware Information CPU
File System V1.0.2 Name, firmware version, package

PRODUCT VIPA M13-CCF0000
V3.0.0
Px000292.pkg
HARDWARE V0.1.0.0 Information for the support
5852A-V11
MX000313.102
BOOTLOADER Bx000715 V126
Bx000501 V2.2.5.0
Ax000136 V1.0.6.0
Ax000150 V1.1.4.0
fx000018.wld V1.0.2.0
syslibex.wld n/a
Protect.wld n/a
ARM Processor Load CPU
Measurement Cycle Time 100 ms Information for the support

Last Value 9%
Average Of Last 10 Values 9%
Minimum Load 9%
Maximum Load 26%
Tab: ‘IP’ Here the IP address data of your Ethernet PG/OP channel are shown.
HB400 | CPU | M13-CCF0000 | en | 20-02 95

Tab: ‘Firmware’ As of CPU firmware version V3.0.0, you can transfer the firmware file online to the CPU
via the ‘Firmware’ tab. The firmware update in the CPU is triggered by means of the
operating mode switch. Ä Chap. 4.14 ‘Firmware update’ page 106
Tab: ‘Access Ways’ As of CPU firmware version V3.0.0, information about access settings is shown here. In
the delivery state, there are no restrictions. You can specify access to interfaces, ports
and protocols via the parametrization. Ä Chap. 4.9 ‘Setting VIPA specific CPU parame-
ters’ page 82
4.11.1.1.1 Tab: ‘OPC UA’

As of CPU firmware version V3.0.0, information about the OPC UA project is shown here.
Ä Chap. 6 ‘Deployment OPC UA’ page 175
For your CPU can process a OPC UA project, you have to activate the
OPC UA functionality. Ä Chap. 6.3 ‘Activate OPC UA functionality’
page 184
Start Conditions Here the start conditions for the OPC UA server are listed:
n Conflicting projects
– Simultaneous use of an OPC UA and WebVisu project via the same interface is
not permitted and results in the message ‘conflicting project on card’ .
– The status ‘no conflicting project on card’ indicates that there is no conflict with a
WebVisu project on the same interface.
n Feature Set activated
– yes: The OPC UA functionality is activated.
– no: The OPC UA functionality is not activated.
– Ä Chap. 6.3 ‘Activate OPC UA functionality’ page 184
n Allowed by User
– yes: The OPC UA server is activated and access to it is allowed. As soon as an
OPC UA project is found on the memory card, it is automatically started and ena-
bled for access.
– no: You can disable and stop the OPC UA server by means of the CMD - auto
command ‘OPCUA_PGOP_DISABLE’ . With ‘OPCUA_PGOP_ENABLE’ you can
enable to restart the OPC UA server.
– Ä Chap. 4.18 ‘CMD - auto commands’ page 113
96 HB400 | CPU | M13-CCF0000 | en | 20-02

n Allowed by Access Ways

– yes: By default, the OPC UA protocol is enabled.
– no: The OPC UA protocol is disabled. You can deactivate or activate the OPC UA
protocol by means of the parameter ‘OPC UA’ in the ‘Access settings’ .
n Hardware configured
– yes: A hardware configuration as a precondition for the OPC UA communication
is loaded. The hardware configuration is checked for validity elsewhere.
– no: A hardware configuration is not loaded e.g. after an overall reset.
– Ä Chap. 4.5 ‘Hardware configuration - CPU’ page 69
n OPC UA project
– loaded: An OPC UAOPC UA project is loaded.
– not loaded: An OPC UAOPC UA project is not loaded.
– Ä Chap. 6 ‘Deployment OPC UA’ page 175
Server n State
– Running: The start conditions are fulfilled and the OPC UA server is started.
– Stopped: The OPC UA server is stopped.
– Startup failure: The OPC UA server can not be started.
– Starting: The OPC UA server currently starts up.
– Stopping: The OPC UA server currently stopps.
n Endpoint URL
– As soon as the OPC UA server is started, the endpoint URL of the OPC UA
server is listed here.
4.11.1.1.2 Tab: ‘WebVisu’

Information about the web visualization ( ‘WebVisu’ ) are shown here. The creation of a
‘WebVisu’ project is only possible with the SPEED7 Studio V1.7.0 and up. Ä Chap. 7
‘Deployment WebVisu - Web visualization’ page 201
For your CPU can process a WebVisu project, you have to activate the
WebVisu functionality. Ä Chap. 7.2 ‘Activate WebVisu functionality’
page 204
HB400 | CPU | M13-CCF0000 | en | 20-02 97

General Information n Feature

– activated: The WebVisu functionality is activated.
– not activated: The WebVisu functionality is not activated.
n Status
– The status of your WebVisu project is shown here. Ä Chap. 4.11.1.1.2.1 ‘Status
of the WebVisu’ page 98
n User authentication
– activated: User authentication is activated. Access to the WebVisu happens via a
login by user name and password.
– not activated: User authentication is de-activated. Access to the WebVisu is unse-
cured.
Statistics Statistical information about your WebVisu project are shown here.
n Sessions: Number of sessions, i.e. online connections to this WebVisu project. A ses-
sion corresponds to an open window or tab in a web browser.
– free: Number of sessions still possible.
– used: Number of active sessions. For the number of active sessions, it is not rele-
vant whether the sessions were started by the same or different users.
– max.: Number of sessions still possible. The maximum number of sessions is
device specific and specified in the technical data.
n Subscribed items: Number of variables.
– free: Here nothing is shown.
– used: Number of variables used.
– max.: Here nothing is shown.
n WebVisu Project: Information on the memory allocation for the WebVisu project.
– free: Still free space for the WebVisu project.
– used: Size of the current WebVisu project.
– max.: Maximum available space for a WebVisu project.
Link In Status ‘running’ the links to access your WebVisu are listed here.
Status of the WebVisu

On the device web page at the tab ‘WebVisu’ via ‘Status’ you get the status of your
WebVisu project.
Status Meaning
running WebVisu is active / has started-up and can be opened
loading webvisu project Loading WebVisu project
shutting down WebVisu server shuts down
stop requested WebVisu STOP requested
stopped WebVisu server is down
webvisu feature not activated WebVisu not activated, memory card is not inserted
webvisu is disabled by the user WebVisu was disabled by the user
no webvisu project file found No WebVisu project found
no hardware configuration loaded No hardware configuration is loaded
98 HB400 | CPU | M13-CCF0000 | en | 20-02

Status Meaning
invalid configuration Invalid WebVisu configuration
internal error: filesystem Error initializing the file system
webvisu project file too large Error loading WebVisu project, project file too large
loading webvisu project file Error loading WebVisu project, project file may be damaged
deleting webvisu project Failed to delete the WebVisu project
internal error: file system - delete WebVisu project to be deleted was not found in the memory
CRC mismatch CRC of the WebVisu project file is not correct
webvisu stopped WebVisu server has terminated unexpectedly
internal error 1 Internal error - initialization failed step 1
internal error 2 Internal error - initialization failed step 2
internal error 3 Unexpected internal error
unknown error General error
4.11.1.1.3 Tab: ‘Port Mirroring’

Overview n Port Mirroring offers the possibility to diagnose the communication without additional
hardware effort.
n The Ethernet PG/OP interface is designed as switch.
n When Port Mirroring of the PG/OP2: X4 (Mirror Port) interface is activated, all tele-
grams received and sent via the PG/OP1: X3 interface are mirrored to the PG/OP2:
X4 interface and vice versa.
n When Port Mirroring is activated, for diagnostics with diagnostics software such as
Wireshark, you can connect your PC directly to the 2. interface.
n The next power-cycle will automatically disable Port Mirroring.
Enable Port Mirroring When enabled, you can set the parameters for Port Mirroring.
PG/OP1: X3 When enabled the frames of PG/OP2: X4 are mirrored to PG/OP1: X3.
PG/OP2: X4 When enabled the frames of PG/OP1: X3 are mirrored to PG/OP2: X4.
Disable communication on When enabled additional communication via the mirrored interface (Mirror Port) is pre-
the Mirror Port vented.
Save With Save, the setting are taken and activated. The next power-cycle will automatically
disable Port Mirroring.
HB400 | CPU | M13-CCF0000 | en | 20-02 99

4.11.1.2 Web page with selected module
Tab: ‘Info’ Here product name, order number, serial number, firmware version and hardware state
number of the according module are listed.
Tab: ‘Data’ Here the address and the state of the inputs respectively outputs are listed. Please note
with the outputs that here exclusively the states of outputs can be shown, which are
within the OB 1 process image.
Tab: ‘Parameter’ With parametrizable modules e.g. analog modules the parameter setting is shown here.
These come from the hardware configuration.
100 HB400 | CPU | M13-CCF0000 | en | 20-02

Operating modes > Overview
4.12 Operating modes

4.12.1 Overview
The CPU has 4 operating modes:
n Operating mode STOP
n Operating mode START-UP
(OB 100 - restart / OB 102 - cold start *)
n Operating mode RUN
n Operating mode HOLD
Certain conditions in the operating modes START-UP and RUN require a specific reaction
from the system program. In this case the application interface is often provided by a call
to an organization block that was included specifically for this event.
Operating mode STOP n The application program is not processed.

n If there has been a processing before, the values of counters, timers, flags and the
process image are retained during the transition to the STOP mode.
n Command output disable (BASP) is activated this means the all digital outputs are
disabled.
n : The yellow LED of the status bar lights up in the STOP state.
Operating mode START- n : After PowerON the yellow LED of the status bar blinks in the STOP
UP state.
n : After a short time the flashing changes to a steady light.
n During the transition from STOP to RUN a call is issued to the 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, this means BASP is acti-
vated.
– : The green LEDs 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.
– : The green LEDs of the status bar lights up when the START-UP is
completed and the CPU is in the RUN state.
* OB 102 (Cold start)

If there is a "Watchdog" error the CPU still remains in STOP state. With
such an error the CPU must be manually started again. For this the
OB 102 (cold start) must exist. The CPU will not go to RUN without the
OB 102. Alternatively you can bring your CPU in RUN state again by an
overall reset respectively by reloading your project.
Please consider that the OB 102 (cold start) may exclusively be used for
treatment of a watchdog error.
Operating mode RUN n : The green LED lights up when the CPU is in the RUN state.
n The application program in OB 1 is processed in a cycle. Under the control of alarms
other program sections can be included in the cycle.
n All timers and counters being started by the program are active and the process
image is updated with every cycle.
n BASP is deactivated, i.e. all outputs are enabled.
HB400 | CPU | M13-CCF0000 | en | 20-02 101

Operating modes > Overview
Operating mode HOLD The CPU offers up to 3 breakpoints to be defined for program diagnosis. Setting and
deletion of breakpoints happens in your programming environment. As soon as a break-
point is reached, you may process your program step by step.
Precondition For the usage of breakpoints, the following preconditions have to be fulfilled:
n Testing in single step mode is possible with STL. If necessary switch the view via
‘View è STL’ to STL.
n The block must be opened online and must not be protected.
Approach for working with 1. Activate ‘View è Breakpoint Bar’.

breakpoints
2. Set the cursor to the command line where you want to insert a breakpoint.
3. Set the breakpoint with ‘Debug è Set Breakpoint’.
ð The according command line is marked with a circle.
4. To activate the breakpoint click on ‘Debug è Breakpoints Active’.
ð The circle is changed to a filled circle.
5. Bring your CPU into RUN.
ð When the program reaches the breakpoint, your CPU switches to the state
HOLD, the breakpoint is marked with an arrow and the register contents are
monitored.
6. Now you may execute the program code step by step via ‘Debug
è Execute Next Statement’ or run the program until the next breakpoint via ‘Debug
è Resume’.
7. Delete (all) breakpoints with the option ‘Debug è Delete All Breakpoints’.
Behavior in operating n Red LED is on and green LED blinks with 1Hz: CPU is in STOP state,
state HOLD configured holding point reached.
n The execution of the code is stopped. No level is further executed.
n All times are frozen.
n The real-time clock runs is just running.
n The outputs were disabled (BASP is activated).
n Configured CP connections remain exist.
The usage of breakpoints is always possible. Switching to the operating

mode test operation is not necessary.
With more than 2 breakpoints, a single step execution is not possible.
102 HB400 | CPU | M13-CCF0000 | en | 20-02

Operating modes > Function security
4.12.2 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 devel-
oped function secure and have the following system properties:
Event concerns Effect

RUN ® STOP general BASP (Befehls-Ausgabe-Sperre, i.e. command output lock)
is set.
central digital outputs The outputs are disabled.
central analog outputs The outputs are disabled.
n Voltage outputs issue 0V
n Current outputs 0...20mA issue 0mA
n Current outputs 4...20mA issue 4mA
If configured also substitute values may be issued.
decentral outputs Same behaviour as the central digital/analog outputs.
decentral inputs The inputs are cyclically be read by the decentralized station
and the recent values are put at disposal.
STOP ® RUN res. Pow- general First the PII is deleted, then OB 100 is called. After the execu-
erON tion of the OB, the BASP is reset and the cycle starts with:
Delete PIO ® Read PII ® OB 1.
decentral inputs The inputs are be read by the decentralized station and the
recent values are put at disposal.
RUN general The program is cyclically executed:
Read PII ® OB 1 ® Write PIO.
PII = Process image inputs
PIO = Process image outputs
HB400 | CPU | M13-CCF0000 | en | 20-02 103

Overall reset
4.13 Overall reset

Overview During the overall reset the entire user memory is erased. Data located in the memory
card is not affected. You have 2 options to initiate an overall reset:
n Overall reset by means of the operating mode switch
n Overall reset by means of a configuration tool like e.g. the Siemens SIMATIC Man-
ager
You should always establish 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 by means of

the operating mode switch
1. Your CPU must be in STOP mode. For this switch the operating mode switch of the
CPU to STOP.
ð Status bar:
2. Switch the operating mode switch to MR position for about 3 seconds.

ð The yellow LED blinks with 1Hz and changes from repeated
blinking to permanently on.
3. Place the operating mode switch in the position STOP and switch it to MR and
quickly back to STOP within a period of less than 3 seconds.
ð The overall reset is carried out. Here the yellow LED blinks with 2Hz
.
4. The overall reset has been completed when the yellow LED is on permanently
.
Overall reset by means of For the following proceeding you must be online connected to your CPU.
the Siemens SIMATIC
Manager 1. For an overall reset the CPU must be switched to STOP state. You may place the
CPU in STOP by the menu command ‘PLC è Operating mode’.
2. You may request the overall reset by means of the menu command ‘PLC
è Clean/Reset’.
ð A dialog window opens. Here you can bring your CPU in STOP state, if not
already done, and start the overall reset. During the overall reset the yellow
LED of the status bar blinks with 2Hz . The overall reset has been
completed when the yellow LED is on permanently .
Activating functionality by If there is a VIPA VSC plugged, after an overall reset the according functionality is auto-
means of a VSC matically activated. Ä Chap. 4.16 ‘Deployment storage media - VSD, VSC’ page 110
Automatic reload If there is a project S7PROG.WLD on the memory card, after an overall reset the CPU
attempts to reload this project from the memory card. Here the yellow LED of the status
line flickers . The operating mode of the CPU will be STOP respectively
RUN, depending on the position of the operating mode switch.
104 HB400 | CPU | M13-CCF0000 | en | 20-02

Overall reset
Reset to factory setting The Reset to factory setting deletes completely the internal RAM of the CPU and resets
this to delivery state. Please regard that the MPI address is also set back to default 2!
Ä Chap. 4.15 ‘Reset to factory settings’ page 109
HB400 | CPU | M13-CCF0000 | en | 20-02 105

Firmware update
4.14 Firmware update

Overview You can find current firmware versions at www.vipa.com in the service area. There are
the following possibilities for the firmware update:
n Firmware update online - from FW V3.0.0 Ä Chap. 4.14.1 ‘Firmware update online’
page 107
– Transfer of the firmware file to the CPU via the CPU web page.
– Triggering the firmware update by means of the operating mode switch.
n Firmware update via memory card Ä Chap. 4.14.2 ‘Firmware update via memory
card’ page 108
– Transfer of the firmware file to a memory card.
– The identification of a firmware file on the memory card takes place by means of a
defined naming convention.
– After PowerON and operating mode switch in the STOP position, the firmware
update can be triggered by means of operating mode switch.
Show the firmware version The CPU has an integrated Device web page that also shows information about the firm-
via web page ware version via ‘Info’ . Here you will also find information about the required firmware
‘Package’ . With [Expert View] you can access the extended "Expert" overview. Ä Chap.
4.11.1 ‘Device web page CPU’ page 93
Tab: ‘Info’
Name Value
Ordering Info M13-CCF0000 Order number of the CPU
Serial ... Serial number of the CPU
Version 01V... Version number of the CPU
HW Revision 01 CPU hardware revision
Software 3.0.0 CPU firmware version
Package Pb000292.pkb File name for the firmware update
Current firmware at The latest firmware versions can be found in the service area at www.vipa.com. For
www.vipa.com example the following file is necessary for the firmware update of the CPU M13-CCF0000
and its components with hardware release 01:
n CPU M13C, Hardware release 01: Pb000292.pkb
106 HB400 | CPU | M13-CCF0000 | en | 20-02

Firmware update > Firmware update online
CAUTION!
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 defec-
tive. In this case, please call our hotline!
Please regard that the version of the update firmware has to be different
from the existing firmware otherwise no update is executed.
4.14.1 Firmware update online

Precondition n Access is via the IP address of the Ethernet PG/OP channel.
n You can access the IP address with a web browser.
It is assumed that there is a connection via the Ethernet PG/OP channel

between the PC with web browser and the CPU. This may be tested by
Ping to the IP address of the Ethernet PG/OP channel.
Load firmware and store it 1. Go to www.vipa.com.

in working directory
2. Click at ‘Service/Support è Downloads è Firmware’.
3. Via ‘System MICRO è CPU’ navigate to your CPU and download the zip file to
your PC.
4. Extract the zip file into your working directory.
CAUTION!
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!
Perform firmware update

1. Switch the operating mode switch of your CPU in position STOP.
2. Execute an overall reset. Ä Chap. 4.13 ‘Overall reset’ page 104
3. Open the CPU web page and select the ‘Firmware’ tab.
4. Click at ‘Browse ...’ and navigate to the firmware file in your working directory.
5. Click at ‘Upload’ .
ð The firmware file is checked for plausibility and transmitted to the CPU. After the
transfer, the firmware versions are matched and listed with the note if a firm-
ware update is possible.
6. You start the firmware update by tipping the operating mode switch downwards to
MR and then leaving the switch in STOP position.
ð During the update process, the yellow LED of the status bar flashes or flickers
. This may last several minutes.
HB400 | CPU | M13-CCF0000 | en | 20-02 107

Firmware update > Firmware update via memory card
7. The update is completed without errors when the red and yellow LEDs of the status
bar are flashing (1Hz) . If only the red LED of the status bar
is flashing, an error has occurred.
8. Turn power OFF and ON.
ð After the start-up, the CPU is ready for operation with the new firmware. The
current firmware version can be determined via the web page of the CPU.
4.14.2 Firmware update via memory card

Overview n For the firmware update via memory card an accordingly prepared memory card must
be in the CPU during the start-up.
n So a firmware files can be recognized and assigned with start-up, a pkb file name is
reserved for each hardware revision, which begins with "pb" and differs in a number
with 6 digits.
n In the VIPASystem MICRO CPU, the pkb file name can be shown via the web page.
n After PowerON and operating mode switch of the CPU in STOP, the CPU checks if
there is a pkb file at the memory card. 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.
The procedure here describes the update from the CPU firmware version
V2.4.0. The update of an older version to the firmware version V2.4.0 has
to be done via pkg files. For this refer to the corresponding manual for
your CPU version.
Load firmware and 1. Go to www.vipa.com

transfer it to memory card
2. Click at ‘Service Support è Downloads è Firmware’.
3. Via ‘System MICRO è CPU’ navigate to your CPU and download the zip file to
your PC.
4. Unzip the zip file and copy the pgb file to the root directory of your memory card.
CAUTION!
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 a firmware
update you should execute a "Reset to factory setting". Ä Chap. 4.15
‘Reset to factory settings’ page 109
Transfer firmware from

memory card into CPU
1. Switch the operating mode switch of your CPU in position STOP.
108 HB400 | CPU | M13-CCF0000 | en | 20-02

Reset to factory settings
3. Plug the memory card with the firmware file into the CPU. Please take care of the
correct plug-in direction of the memory card.

ð After a short boot-up time, the alternate blinking of the red and yellow LED
of the status bar shows that at least a more current firmware file
was found at the memory card.
5. You start the transfer of the firmware as soon as you tip the operating mode switch
downwards to MR within 10s and then leave the switch in STOP position.
6. During the update process, the yellow LED of the status bar flashes or flickers
. This may last several minutes.
7. The update is completed without errors when the red and yellow LEDs of the status
bar are flashing (1Hz) . If only the red LED of the status bar
is flashing, an error has occurred.
ð After the start-up, the CPU is ready for operation with the new firmware. The
current firmware version can be determined via the web page of the CPU.
4.15 Reset to factory settings

Proceeding n With the following proceeding the internal RAM of the CPU is completely deleted and
the CPU is reset to delivery state.
n Please regard that the MPI address is also reset to default 2 and the IP address of
the Ethernet PG/OP channel is reset to 0.0.0.0!
n A factory reset may also be executed by the command FACTORY_RESET. Ä Chap.
4.18 ‘CMD - auto commands’ page 113
1. Switch the CPU to STOP.
2. Push the operating mode switch down to position MR for 30 seconds. Here the
yellow LED of the status bar blinks . After a few seconds the LED
changes to static light. Now the LED changes between static light and blinking.
Start here to count the static light of the LED.
3. After the 6. static light release the operating mode switch and tip it downwards to
MR.
ð To confirm the reset process the yellow LED of the status bar blinks (2Hz)
. This means that the RAM was deleted completely.
If the yellow LED of the status bar is on , only an

overall reset has been performed and the reset to factory set-
ting has been failed. In this case you can repeat the procedure.
A factory reset can only be executed if the yellow LED has
static light for exact 6 times.
4. The reset process is completed when the red and yellow LEDs of the status bar are
blinking (1Hz) .
HB400 | CPU | M13-CCF0000 | en | 20-02 109

Deployment storage media - VSD, VSC
4.16 Deployment storage media - VSD, VSC

Overview At the front of the CPU there is a slot for storage media. Here the following storage media
can be plugged:
n VSD - VIPA SD-Card
– External memory card for programs and firmware.
n VSC - VIPASetCard
– External memory card (VSD) for programs and firmware with the possibility to
unlock optional functions like work memory and field bus interfaces.
– These functions can be purchased separately.
– To activate the corresponding card is to be installed and a Overall reset is to be
established. Ä Chap. 4.13 ‘Overall reset’ page 104
To avoid malfunctions, you should use memory cards of VIPA. These cor-
respond to the industrial standard. A list of the currently available VSD
respectively VSC can be found at www.vipa.com
You can cause the CPU to load a project automatically respectively to execute a com-
mand file by means of pre-defined file names.
VSD VSDs are external storage media based on SD memory cards. VSDs are pre-formatted
with the PC format FAT 16 (max. 2GB) and can be accessed via a card reader. After
PowerON respectively an overall reset the CPU checks, if there is a VSD with data valid
for the CPU.
Push the VSD into the slot until it snaps in leaded by a spring mechanism. This ensures
contacting. By sliding down the sliding mechanism, a just installed VSD card can be pro-
tected against drop out.
To remove, slide the sliding mechanism up again and push the storage media against the
spring pressure until it is unlocked with a click.
CAUTION!
If the media was already unlocked by the spring mechanism, with shifting
the sliding mechanism, a just installed memory card can jump out of the
slot!
VSC The VSC is a VSD with the possibility to enable optional functions. Here you have the
opportunity to accordingly expand your work memory respectively enable field bus func-
tionalities. Information about the enabled functions can be shown via the web page.
Ä Chap. 4.11 ‘Accessing the web server’ page 93
110 HB400 | CPU | M13-CCF0000 | en | 20-02

Deployment storage media - VSD, VSC
CAUTION!
Please regard that the VSC must remain plugged when you’ve enabled
optional functions at your CPU. Otherwise the red LED of the status bar
blinks in RUN with 1Hz and the CPU goes into STOP after 72
hours. As long as an activated VSC is not plugged in, the LED blinks and
the "TrialTime" timer counts from 72 hours down to 0. The CPU then goes
into STOP mode. By inserting the VSC, the LED goes out and the CPU
runs again without restrictions.
The VSC cannot be exchanged with a VSC of the same optional func-
tions. The activation code is fixed to the VSD by means of an unique
serial number. Here the functionality as an external memory card is not
affected.
Accessing the storage To the following times an access takes place on a storage medium:
medium
After overall reset
n The CPU checks if a VSC is inserted. If so, the corresponding optional functions are
enabled.
n The CPU checks whether a project S7PROG.WLD exists. If so, it is automatically
loaded.
After PowerON
n The CPU checks whether a project AUTOLOAD.WLD exists. If so, an overall reset is
executed and the project is automatically loaded.
n The CPU checks whether a command file with the name VIPA_CMD.MMC exists. If
so the command file is loaded and the commands are executed.
n After PowerON and CPU STOP the CPU checks if there is a *.pkb file (firmware file).
If so, this is shown by the CPU by blinking LEDs and the firmware may be installed by
an update request. Ä Chap. 4.14 ‘Firmware update’ page 106
In STOP state when inserting a memory card
n If a memory card is plugged in STOP state, which contains a command file
VIPA_CMD.MMC, the command file is loaded and the containing instructions are exe-
cuted.
The FC/SFC 208 ... FC/SFC 215 and FC/SFC 195 allow you to include
the memory card access into your user application. More can be found in
the manual operation list (HB00_OPL_SP7) of your CPU.
HB400 | CPU | M13-CCF0000 | en | 20-02 111

Extended know-how protection
4.17 Extended know-how protection

Overview
Please note that this functionality is not supported by the Siemens TIA
Portal!
Besides the "standard" Know-how protection the CPUs from VIPA provide an "extended"
know-how protection that serves a secure block protection for accesses of 3. persons.
n 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.
n Extended protection
– The "extended" know-how protection developed by VIPA offers the opportunity to
store blocks permanently in the CPU.
– With the "extended" protection you transfer the protected blocks to a memory card
into a WLD-file named protect.wld.
– By plugging the memory card and then an overall reset the blocks in the pro-
tect.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 block code that is to be protected remains in the CPU and cannot
be read.
Protect blocks with pro- 1. Create a new wld file in the Siemens SIMATIC Manager with ‘File
tect.wld è Memory Card file è New’.
2. Rename the wld file to "protect.wld".
3. Transfer the according blocks into the file by dragging them with the mouse from
the project to the file window of protect.wld.
4. Transfer the file protect.wld to a memory card.
5. Plug the memory card into the CPU and execute an overall reset. Ä Chap. 4.13
‘Overall reset’ page 104
ð The overall reset stores the blocks in protect.wld permanently in the CPU pro-
tected from accesses of 3. persons.
Protection behaviour Protected blocks are overwritten by a new protect.wld. Using a PG 3. persons may
access protected blocks but only the block header is transferred to the PG. The block
code that is to be protected remains in the CPU and cannot be read.
Change respectively Protected blocks in the RAM of the CPU may be substituted at any time by blocks with
delete protected blocks the same name. This change remains up to next overall reset. Protected blocks may per-
manently be overwritten only if these are deleted at the protect.wld before. A factory reset
does not affect the protected blocks. By transferring an empty protect.wld from the
memory card with an overall reset, you may delete all protected blocks in the CPU.
Usage of protected blocks Due to the fact that reading of a "protected" block from the CPU monitors no symbol
labels it is convenient to provide the "block covers" for the end user. For this, create a
project of all protected blocks. Delete all networks in the blocks so that these only contain
the variable definitions in the according symbolism.
112 HB400 | CPU | M13-CCF0000 | en | 20-02

CMD - auto commands
4.18 CMD - auto commands

Overview A Command file at a memory card is automatically executed under the following condi-
tions:
n CPU is in STOP and memory card is plugged
n After each PowerON
Command file n 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 memory card.
n The file has to be started by CMD_START as 1. command, followed by the desired
commands (no other text) and must be finished by CMD_END as last command.
n Text after the last command CMD_END e.g. comments is permissible, because this is
ignored.
n As soon as the command file is recognized and executed each action is stored at the
memory card in the log file logfile.txt.
n For each executed command a diagnostics entry may be found in the diagnostics
buffer.
Commands Please regard the command sequence is to be started with CMD_START and ended with
CMD_END.
Command Description Diagnostics

entry
CMD_START In the first line CMD_START is to be located. 0xE801
There is a diagnostics entry if CMD_START is missing. 0xE8FE
WAIT1SECOND Waits about 1 second. 0xE803
LOAD_PROJECT The function "Overall reset and reload from memory card" 0xE805
is executed. The wld file located after the command is
loaded else "s7prog.wld" is loaded.
SAVE_PROJECT The recent project (blocks and hardware configuration) is 0xE806
stored as "s7prog.wld" at the memory card. If the file just
exists it is renamed to "s7prog.old". If your CPU is pass-
word protected so you have to add this as parameter. Oth-
erwise there is no project written.
Example: SAVE_PROJECT password
FACTORY_RESET Executes "factory reset". 0xE807
DIAGBUF The current diagnostics buffer of the CPU is stored as "dia- 0xE80B
gbuff.txt" at the memory card.
SET_NETWORK IP parameters for Ethernet PG/OP channel may be set by 0xE80E
means of this command. The IP parameters are to be
given in the order IP address, subnet mask and gateway in
the format x.x.x.x each separated by a comma. Enter the
IP address if there is no gateway used.
CMD_END In the last line CMD_END is to be located. 0xE802
WEBPAGE Saves all information on the device web page (Expert- 0xE804
View) as webpage.txt on the memory card Ä Chap. 4.11
‘Accessing the web server’ page 93
WEBVISU_PGOP_ENABLE Enable WebVisu project via Ethernet PG/OP channel 0xE82C
WEBVISU_PGOP_DISABLE* Disable WebVisu project via Ethernet PG/OP channel 0xE82D
HB400 | CPU | M13-CCF0000 | en | 20-02 113

CMD - auto commands
Command Description Diagnostics

entry
OPCUA_PGOP_ENABLE Enable OPC UA project via Ethernet PG/OP channel 0xE830
OPCUA_PGOP_DISABLE Disable OPC UA project via Ethernet PG/OP channel 0xE831
*) After a power cycle or loading a hardware configuration, the settings are retained. With reset to the factory settings or over all reset, the WebVisu
project is set to the default value "enabled".
Examples The structure of a command file is shown in the following. The corresponding diagnostics
entry is put in parenthesizes.
Example 1
CMD_START Marks the start of the command sequence (0xE801)
LOAD_PROJECT proj.wld Execute an overall reset and load "proj.wld" (0xE805)
WAIT1SECOND Wait ca. 1s (0xE803)
DIAGBUF Store diagnostics buffer of the CPU as "diagbuff.txt" (0xE80B)
CMD_END Marks the end of the command sequence (0xE802)
... arbitrary text ... Text after the command CMD_END is not evaluated.
Example 2
CMD_START Marks the start of the command sequence (0xE801)
LOAD_PROJECT proj2.wld Execute an overall reset and load "proj2.wld" (0xE805)
IP parameter (0xE80E)
SET_NETWORK 172.16.129.210,255.255.224.0,172.16.129.210
DIAGBUF Store diagnostics buffer of the CPU as "diagbuff.txt" (0xE80B)
CMD_END Marks the end of the command sequence (0xE802)
... arbitrary text ... Text after the command CMD_END is not evaluated.
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.
114 HB400 | CPU | M13-CCF0000 | en | 20-02

Control and monitoring of variables with test functions
4.19 Control and monitoring of variables with test functions

Overview n 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 Man-
ager.
n The status of the operands and the RLO can be displayed by means of the test func-
tion ‘Debug è Monitor’.
n The status of the operands and the RLO can be displayed by means of the test func-
tion ‘PLC è Monitor/Modify Variables’.
‘Debug è Monitor’ n This test function displays the current status and the RLO of the different operands
while the program is being executed.
n It is also possible to enter corrections to the program.
n The processing of the states may be interrupted by means of jump commands or by
timer and process-related interrupts.
n At the breakpoint the CPU stops collecting data for the status display and instead of
the required data it only provides the PG with data containing the value 0.
n The interruption of the processing of statuses does not change the execution of the
program. It only shows that the data displayed is no longer valid.
When using the test function "Monitor" the PLC must be in RUN mode!
For this reason, jumps or time and process alarms can result in the value displayed
during program execution remaining at 0 for the items below:
n the result of the logical operation RLO
n Status / AKKU 1
n AKKU 2
n Condition byte
n absolute memory address SAZ. In this case SAZ is followed by a "?".
HB400 | CPU | M13-CCF0000 | en | 20-02 115

Diagnostic entries
‘PLC This test function returns the condition of a selected operand (inputs, outputs, flags, data
è Monitor/Modify word, counters or timers) at the end of program execution. This information is obtained
Variables’ from the corresponding area of the selected operands. During the controlling of variables
respectively in operating mode STOP the input area is directly read. Otherwise only the
process image of the selected operands is displayed.
n Control of outputs
– Serves to check the wiring and proper operation of output modules.
– If the CPU is in RUN mode, so only outputs can be controlled, which are not con-
trolled by the user program. Otherwise values would be instantly overwritten.
– If the CPU is in STOP - even without user program, so you need to disable the
command output lock BASP ( ‘Enable PO’ ). Then you can control the outputs
arbitrarily
n Controlling 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.
n Forcing variables
– You can pre-set individual variables of a user program with fixed values so that
they can not be changed or overwritten by the user program of the CPU.
– By pre-setting of variables with fixed values, you can set certain situations for
your user program and thus test the programmed functions.
CAUTION!
– Please consider that controlling of output values represents a poten-
tially dangerous condition.
– Even after a power cycle forced variables remain forced with its
value, until the force function is disabled.
– These functions should only be used for test purposes respectively
for troubleshooting. More information about the usage of these func-
tions may be found in the manual of your configuration tool.
4.20 Diagnostic entries

Accessing diagnostic data Ä Appendix A ‘System specific event IDs’ page 326
n You may read the diagnostics buffer of the CPU via the Siemens SIMATIC Manager.
Besides of the standard entries in the diagnostics buffer, the VIPA CPUs support
some additional specific entries as Event-IDs.
n To monitor the diagnostics entries you choose in the Siemens SIMATIC manager
‘PLC è Module information’. Via the register "Diagnostics Buffer" you reach the diag-
nostics window.
n The current content of the diagnostic buffer is stored at the memory card by means of
the CMD DIAGBUF. Ä Chap. 4.18 ‘CMD - auto commands’ page 113
n The diagnostic is independent from the operating mode of the CPU. You may store a
max. of 100 diagnostic entries in the CPU.
116 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO Deployment I/O periphery
Overview
5 Deployment I/O periphery

5.1 Overview
Project engineering and n On this CPU the connectors for digital respectively analog signal and Technological
parametrization functions are combined in a one casing.
n The project engineering happens in the Siemens SIMATIC Manager as Siemens CPU
314C-2 PN/DP (314-6EH04-0AB0 V3.3). Here the CPU M13-CCF0000 is parameter-
ized via the ‘Properties’ dialog of the Siemens CPU 314C-2 PN/DP
(314-6EH04-0AB0 V3.3).
n For parametrization of the digital I/O periphery and the technological functions the
corresponding sub modules of the CPU 314C-2 PN/DP (314-6EH04-0AB0 V3.3) is to
be used.
n The controlling of the operating modes of the technological functions happens by
means of handling blocks of the user program.
I/O periphery n The integrated I/Os of the CPU may be used for technological functions or as
standard periphery.
n Technological functions and standard periphery may be used simultaneously with
appropriate hardware.
n Read access to inputs used by technological functions is possible.
n Write access to used outputs is not possible.
n Ä Chap. 5.3 ‘Analog input’ page 119
– AI 2xUx12Bit (0 ... 10V)
– The analog channels of the module are not isolated to the electronic power
supply.
– The analog part has no status indication
n Ä Chap. 5.4 ‘Digital input’ page 122
– DI 16xDC 24V
– Interrupt functions parameterizable
– Status indication via LEDs
n Ä Chap. 5.5 ‘Digital output’ page 126
– DO 12xDC 24V, 0.5A
– Status indication via LEDs
Technological functions n Ä Chap. 5.6 ‘Counting’ page 129

– 4 channels
– Count once
– Count continuously
– Count Periodically
– Control by the user program (SFB 47)
n Ä Chap. 5.7 ‘Frequency measurement’ page 151
– 4 channels
n Ä Chap. 5.8 ‘Pulse width modulation - PWM’ page 157
– 2 channels
n Ä Chap. 5.9 ‘Pulse train’ page 162
– 2 channels
HB400 | CPU | M13-CCF0000 | en | 20-02 117

Deployment I/O periphery VIPA System MICRO
Address assignment
5.2 Address assignment

address

address

address
Counter 816 DINT Channel 0: Counter value / Frequency value

address
820 DWORD reserved
824 DWORD reserved
828 DWORD reserved

address
118 HB400 | CPU | M13-CCF0000 | en | 20-02

Analog input > Analog value representation
5.3 Analog input

5.3.1 Properties
n 2xUx12Bit (0 ... 10V) fixed.
n The analog channels of the module are not isolated to the electronic power supply.
n The analog part has no status indication.
Temporarily not used analog inputs must be connected to the concerning

ground.
5.3.2 Analog value representation

Number representation in
Siemens S7 format
Resolu- Analog value - twos complement
tion
High byte (byte 0) Low byte (byte 1)
Bit number 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Value SG 214 213 212 211 210 29 28 27 26 25 24 23 22 21 20
11Bit+sign SG Measuring value X* X* X* X*
*) The lowest value irrelevant bits of the output value (0) are marked with "X".
Sign bit (SG) Here it is essential:

n Bit 15 = "0": à positive value
n Bit 15 = "1": à negative value
Behavior at error As soon as a measured value exceeds the overdrive region respectively falls below the
underdrive region, the following value is issued:
n Measuring value > end of overdrive region:
32767 (7FFFh)
n Measuring value < end of underdrive region:
-32768 (8000h)
At a parameterization error the value 32767 (7FFFh) is issued.
When leaving the defined range during analog output 0V respectively 0A is issued.
HB400 | CPU | M13-CCF0000 | en | 20-02 119

Analog input > Wiring
Voltage measurement
0 ... 10V
Measuring range Voltage Decimal Hex Range Formulas

(U) (D)
0 ... 10V > 11.759V 32767 7FFFh overflow
11.759V 32511 7EFFh overdrive range
10V 27648 6C00h nominal range
5V 13824 3600h
0V 0 0000h
D: decimal value
-0.8V -2212 F75Ch underdrive range
U: voltage value
< -0.8V -32768 8000h underflow
5.3.3 Wiring
X6: DC 24V, AI, DO byte 1

green
1 1L+ I 1L+: DC 24V for electronic section supply
2 1M I 1M: DC 0V for electronic section supply
3 I Shield
4 2M I 2M: Ground for analog inputs
Cables for analog signals For the analog signals you have to use isolated cables. With this the interferences can be
reduced. The shield of the analog cables should be grounded at both ends. If there are
potential differences between the cables, a potential compensation current can flow,
which could disturb the analog signals. In this case, you should only ground the shield at
one end of the cable.
120 HB400 | CPU | M13-CCF0000 | en | 20-02

Analog input > Parametrization
Temporarily not used analog inputs must be connected to the concerning

ground.
5.3.4 Parametrization
5.3.4.1 Address assignment

address
5.3.4.2 Filter
Parameter hardware con- The analog input part has a filter integrated. The parametrization of the filter happens in
figuration the Siemens SIMATIC Manager via the parameter ‘Integration time’ . The default value of
the filter is 1000ms. The following values can be entered:
n ‘Input 0 ≙ Channel 0’
‘Input 1 ≙ Channel 1’
– ‘Integration time 2.5ms’ ≙ 2ms (no filter)
– ‘Integration time 16.6ms’ ≙ 100ms (small filter)
– ‘Integration time 20ms’ ≙1000ms (medium filter)
Parametrization during By using the record set 1 of the SFC 55 "WR_PARM" you may alter the parametrization
runtime in the module during runtime.
The time needed until the new parametrization is valid can last up to 2ms.
During this time, the measuring value output is 7FFFFh.
Record set 1
Byte Bit 7 ... Bit 0 Default

0 Bit 7...0: reserved 00h
1 Filter 10h
n Bit 1, 0: Analog input channel 0
Bit 3, 2: Analog input channel 1
– 00b: ‘Integration time 2.5ms’ ≙ 2ms (no filter)
– 01b: ‘Integration time 16.6ms’ ≙ 100ms (small filter)
– 10b: ‘Integration time 20ms’ ≙ 1000ms (medium filter)
n Bit 7...4: reserved
2...12 Bit 7...0: reserved
HB400 | CPU | M13-CCF0000 | en | 20-02 121

Digital input > Wiring
5.4 Digital input

5.4.1 Properties
n 16xDC 24V
n Maximum input frequency
– 10 inputs: 100kHz
– 6 inputs: 1kHz
n Interrupt functions parameterizable
n Status indication via LEDs
5.4.2 Wiring
X1: DI byte 0

green
122 HB400 | CPU | M13-CCF0000 | en | 20-02

Digital input > Parametrization
X5: DI byte 1

green
1 - - reserved
2 - - reserved
5.4.3.1 Adress assignment

address
5.4.3.2 Hardware interrupt

Parameter hardware con- With the parameter ‘Hardware interrupt at ...’ you can specify a hardware interrupt for
figuration each input for the corresponding edge. The hardware interrupt is disabled, if nothing is
selected (default setting). A diagnostics interrupt is only supported with Hardware inter-
rupt lost. Select with the arrow keys the input and enable the according hardware inter-
rupts.
Here is valid:
n Rising edge: Edge 0-1
n Falling edge: Edge 1-0
HB400 | CPU | M13-CCF0000 | en | 20-02 123

Digital input > Status indication
5.4.3.3 Input delay

Parameter hardware con- n The input delay can be configured per channel in groups of 4.
figuration n An input delay of 0.1ms is only possible with "fast" inputs, which have a max. input
frequency of 100kHz Ä Chap. 5.4 ‘Digital input’ page 122. Within a group, the input
delay for slow inputs is limited to 0.5ms.
n Range of values: 0.1ms / 0.5ms / 3ms / 15ms
5.4.4 Status indication

green

green
1 - - reserved
2 - - reserved
124 HB400 | CPU | M13-CCF0000 | en | 20-02

Digital input > Status indication
DI +x
green
DI +0.0 DI +0.7 Digital I+0.0 ... 0.7 has "1" signal
Digital I+0.0 ... 0.7 has "0" signal
xL+
green
1L+ DC 24V electronic section supply
xF
green / red
no error
HB400 | CPU | M13-CCF0000 | en | 20-02 125

Digital output > Wiring
5.5 Digital output

5.5.1 Properties
n 12xDC 24V, 0.5A
n Status indication via LEDs
5.5.2 Wiring
X2: DO byte 0

green
126 HB400 | CPU | M13-CCF0000 | en | 20-02

Digital output > Status indication

address

green
DO +x
green
HB400 | CPU | M13-CCF0000 | en | 20-02 127

Digital output > Status indication
xL+
green
xF
green / red
no error
128 HB400 | CPU | M13-CCF0000 | en | 20-02

Counting > Wiring
5.6 Counting
5.6.1 Properties
n 4 channels
n Various counting modes
– once
– continuously
– periodically
n Control by the user program via blocks
5.6.2 Wiring
5.6.2.1 Counter inputs
X1: DI byte 0

green
1 DI 0.7 I Counter 2 (B) *
2 DI 0.6 I Counter 2 (A) *
9 0V I 3M: GND for counter
10 DC 24V I 3L+: DC 24V power section supply for counter
HB400 | CPU | M13-CCF0000 | en | 20-02 129

Counting > Wiring
X5: DI byte 1

green
6 DI 1.3 I Gate 3 *
10 DI 1.7 I Latch 3 *
Input signals The following sensors can be connected

n 24V incremental encoders with two phase-shifted by 90° tracks
n 24V pulse encoder with direction signal
n 24V initiator as BERO or beam sensor
For not all inputs are available at the same time, for every counter you may define the
input assignment via the parameterization for the following input signals:
n Counterx (A)
– Pulse input for counter signal respectively track A of an encoder for 1-, 2- or 4-fold
evaluation.
n Counterx (B)
– Direction signal respectively track B of the encoder. Via the parameterization you
may invert the direction signal.
n Gate 3
– Via this input you can if parameterized open the HW gate of Counter 3 with edge
0-1 and start counting.
n Latch 3
– Via this input via edge 0-1 the current counter value of Counter 3 is stored in a
memory that you may read if needed.
130 HB400 | CPU | M13-CCF0000 | en | 20-02

Counting > Proceeding
5.6.2.2 Counter outputs

X2: DO byte 0

green /
red
5 DO 0.3 O Output channel counter 3
9 0V I 4M: GND for output channel counter

10 DC 24V I 4L+: DC 24V power section supply for output channel counter
Output channel Counterx Every counter has an assigned output channel. For each counter you can specify the
behavior of the counter output via the parametrization with ‘Characteristics of the output’
and ‘Pulse duration’ . Ä Chap. 5.6.4.3 ‘Counter’ page 133
5.6.3 Proceeding
Hardware configuration In the Siemens SIMATIC Manager the following steps should be executed:
1. Perform a hardware configuration for the CPU. Ä Chap. 4.5 ‘Hardware configura-
tion - CPU’ page 69
2. Double-click the counter sub module of the CPU 314C-2 PN/DP (314-6EH04-0AB0
V3.3).
ð The dialog ‘Properties’ is opened.
3. As soon as you select the operating mode for the corresponding channel, a dialog
box with default values for this counter mode is created and shown.
4. Perform the required parameter settings.
5. Safe your project with ‘Station è Safe and compile’.
6. Transfer your project to your CPU.
User program n The SFB 47 should cyclically be called (e.g. OB 1) for controlling the counter func-
tions.
n The SFB is to be called with the corresponding instance DB. Here the parameters of
the SFB are stored.
HB400 | CPU | M13-CCF0000 | en | 20-02 131

Counting > Parametrization
n Among others the SFB 47 contains a request interface. Hereby you get read and
write access to the registers of the appropriate counter.
n So that a new job may be executed, the previous job must have be finished with
JOB_DONE = TRUE.
n Per channel you may call the SFB in each case with the same instance DB, since the
data necessary for the internal operational are stored here.
n Writing accesses to outputs of the instance DB is not permissible.
n Starting, stopping and interrupting a count function of Counter 0 to Counter 2 exclu-
sively happens via the SW gate by setting the SW gate of the SFB 47.
You can also activate input ‘Gate 3’ via the parametrization for Counter 3.
More information about the usage of this block may be found in the
manual "VIPA SPEED7 Operation List".

address
Counter 816 DINT Channel 0: Counter value
820 DINT Channel 1: Counter value

address
820 DWORD reserved
824 DWORD reserved
828 DWORD reserved
132 HB400 | CPU | M13-CCF0000 | en | 20-02

5.6.4.2 Interrupt selection

Via ‘Basic parameters’ you can reach ‘Select interrupt’ . Here you can define the inter-
rupts the CPU will trigger. The following parameters are supported:
n None: The interrupt function is disabled.
n Process: The following events of the counter can trigger a hardware interrupt (select-
able via ‘Count’ ):
– Hardware gate opening
– Hardware gate closing
– On reaching the comparator
– on Counting pulse
– on overflow
– on underflow
n Diagnostics+process: A diagnostics interrupt is only triggered when a hardware inter-
rupt was lost.
5.6.4.3 Counter
Parameter hardware con- Default values and structure of this dialog box depend on the selected ‘Operating mode’ .
figuration
Please consider that the range of values could be limited due to the used
projecting tool. With the VIPA SPEED7 Studio there are no limitations.
Ä Chap. 12 ‘Configuration with VIPA SPEED7 Studio’ page 271
Parameter overview
Operating parameters Description Assignment

Main count direction n None No restriction of the counting range n None
n Up: Restricts the up-counting range. The counter starts
from 0 or load value, counts in positive direction up to
the declaration end value -1 and then jumps back to
load value at the next positive transducer pulse.
n Down: Restricts the down-counting range. The counter
starts from the declared start value or load value in
negative direction, counts to 1 and then jumps to start
value at the next negative encoder pulse. Function is
disable with count continuously.
Gate function n Cancel count: The count starts when the gate opens Abort count process
and resumes at the load value when the gate opens
again.
n Stop count: The count is interrupted when the gate
closes and resumed at the last actual counter value
when the gate opens again.
Ä Chap. 5.6.6.2 ‘Gate function’ page 144
Start value Start value with counting direction backward. 2147483647 (231-1)
End value End value with main counting direction forward.
Range of values: 2...2147483647 (231-1)
HB400 | CPU | M13-CCF0000 | en | 20-02 133


Comparison value The count value is compared with the comparison value. 0
See also the parameter "Characteristics of the output":
n No main counting direction
– Range of values: -2)31 to +2)31-1
n Main counting direction forward
– Range of values: -231 to end value-1
n Main counting direction backward
– Range of values: 1 to +231-1
Hysteresis The hysteresis serves the avoidance of many toggle pro- 0
cesses of the output, if the counter value is in the range of
the comparison value.
0, 1: Hysteresis disabled
Range of values: 0 to 255
Input Description Assignment

Signal evaluation Specify the signal of the connected encoder: Pulse/direction
n Pulse/direction At the input count and direction signal
are connected
n At the input there is an encoder connected with the fol-
lowing evaluation:
– Rotary encoder single
– Rotary encoder double
– Rotary encoder quadruple
Hardware gate Gate control exclusively via channel 3: disabled
n enabled: The gate control for channel 3 happens via
SW and HW gate
n disabled: The gate control for channel 3 exclusively
happens via SW gate
Count direction inverted Invert the input signal ‘Direction’ : disabled
n enabled: The input signal is inverted
n disabled: The input signal is not inverted
134 HB400 | CPU | M13-CCF0000 | en | 20-02

Output Description Assignment

Characteristics of the output The output and the "Comparator" (STS_CMP) status bit No comparison
are set, dependent on this parameter.
n No comparison: The output is used as normal output
and STS_CMP remains reset.
n Comparator
– Counter value ³ Comparison value
– Counter value £ Comparison value
n Pulse at comparison value
– To adapt the used actuators you can specify a
pulse duration. The output is set for the specified
pulse duration when the counter value reaches the
comparison value. When you've set a main
counting direction the output is only set at reaching
the comparison value from the main counting direc-
tion.
Pulse duration Here you can specify the pulse duration for the output 0
signal.
n The pulse duration starts with the setting of the
according digital output.
n The inaccuracy of the pulse duration is less than 1ms.
n There is no past triggering of the pulse duration when
the comparison value has been left and reached again
during pulse output.
n If the pulse duration is changed during operation, it will
take effect with the next pulse.
n If the pulse duration = 0, the output is set until the com-
parison condition is not longer fulfilled.
Range of values: 0...510ms in steps of 2ms
Hardware interrupt Description Assignment

Hardware gate opening Hardware interrupt by edge 0-1 exclusively at HW gate disabled
channel 3
n enabled: Process interrupt by edge 0-1 exclusively at
HW gate channel 3 with open SW gate
n disabled: no hardware interrupt
Hardware gate closing Hardware interrupt by edge 1-0 exclusively at HW gate disabled
channel 3
On reaching comparator Hardware interrupt on reaching comparator disabled
n enabled: Hardware interrupt when comparator is trig-
gered, can be configured via ‘Characteristics of the
output’
HB400 | CPU | M13-CCF0000 | en | 20-02 135


Overflow Hardware interrupt overflow disabled
n enabled: Hardware interrupt on overflow the upper
counter limit
Underflow Hardware interrupt on underrun disabled
n enabled: Hardware interrupt on underflow the lower
counter limit
Max. frequency Description Assignment

Counting signals/HW gate Specify the max. frequency for track A/pulse, 60kHz
track B/direction and HW gate
Frequency shortest permissible count pulse
1kHz 400µs
2kHz 200µs
5kHz 80µs
10kHz 40µs
30kHz 13µs
60kHz 6.7µs
Latch Specify the max. frequency for the latch signal 10kHz
Frequency shortest permissible Latch pulse
1kHz 400µs
2kHz 200µs
5kHz 80µs
10kHz 40µs
30kHz 13µs
60kHz 6.7µs
136 HB400 | CPU | M13-CCF0000 | en | 20-02

Counting > Counter operating modes
5.6.5 Counter operating modes

5.6.5.1 Count continuously
n In this operating mode the counter counts starting with the load value.
n 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.
n 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.
n The counter limits are fix set to maximum range.
n With overflow or underflow the status bits STS_OFLW respectively STS_UFLW in the
SFB 47 are set. These bits remain set until these are reset with RES_STS. If enabled
additionally a hardware interrupt is triggered.
Limits Valid range of values

Lower count limit -2 147 483 648 (-231)
Upper count limit +2 147 483 647 (231 -1)
HB400 | CPU | M13-CCF0000 | en | 20-02 137

5.6.5.2 Count once

5.6.5.2.1 No main counting direction
n The counter counts once starting with load value.
n It is counted forward or backward.
n At over- or underflow at the count limits, the counter jumps to the according other
count limit and the gate is automatically closed.
n To restart the count process, you have to generate an edge 0-1 at the gate Ä Chap.
5.6.6.2 ‘Gate function’ page 144.
n With the configured ‘Gate function’ ‘Interrupt count’ the counting is continued with
current Counter value.
n With configured ‘Gate function’ ‘Cancel count’ the counter starts with the Load value.

Interrupting gate control
Aborting gate control
138 HB400 | CPU | M13-CCF0000 | en | 20-02

5.6.5.2.2 Main counting direction forward

n The counter counts forward starting with the load value.
n When the counter reaches the End value -1 in positive direction, it jumps to the load
value at the next count pulse and the gate is automatically closed.
5.6.6.2 ‘Gate function’ page 144. The counter counts starting with the load value.
n You may exceed the lower count limit.

End value -2 147 483 647 (-231 +1)
up to +2 147 483 647 (231 -1)
HB400 | CPU | M13-CCF0000 | en | 20-02 139

5.6.5.2.3 Main counting direction backward

n The counter counts backward starting with the load value.
n When the counter reaches the End value +1 in positive direction, it jumps to the load
value at the next count pulse and the gate is automatically closed.
5.6.6.2 ‘Gate function’ page 144. The counter counts starting with the load value.
n You may exceed the upper count limit.

End value -2 147 483 648 (-231)
up to +2 147 483 646 (231 -2)
140 HB400 | CPU | M13-CCF0000 | en | 20-02

5.6.5.3 Count periodically

5.6.5.3.1 No main counting direction
n The counter counts forward or backwards starting with the load value.
n At over- or underrun at the count limits, the counter jumps to the load value and con-
tinues counting. If enabled additionally a hardware interrupt is triggered.

HB400 | CPU | M13-CCF0000 | en | 20-02 141

5.6.5.3.2 Main counting direction forward

n The counter counts forward starting with the load value.
n When the counter reaches the end value -1 in positive direction, it jumps to the load
value at the next positive count pulse and continues counting. If enabled additionally
a hardware interrupt is triggered.
n You may exceed the lower count limit.

End value -2 147 483 647 (-231 +1)
up to +2 147 483 647 (231 -1)
142 HB400 | CPU | M13-CCF0000 | en | 20-02

5.6.5.3.3 Main counting direction backward

Main counting direction backward
n The counter counts backward starting with the load value.
n When the counter reaches the end value +1 in positive direction, it jumps to the load
value at the next negative count pulse and continues counting. If enabled additionally
a hardware interrupt is triggered.
n You may exceed the upper count limit.

End value -2 147 483 648 (-231)
up to +2 147 483 646 (231 -2)
HB400 | CPU | M13-CCF0000 | en | 20-02 143

Counting > Counter - Additional functions
5.6.6 Counter - Additional functions

5.6.6.1 Overview
Schematic structure The illustration shows how the additional functions influence the counting behavior. The
following pages describe these additional functions in detail:
5.6.6.2 Gate function

Function n Starting, stopping and interrupting a count function of counter 0 to counter 2 exclu-
sively happens via the SW gate by setting the SW gate of SFB 47.
n Starting, stopping and interrupting a count function of counter 3 happens via the
internal gate (I gate). The i gate is the result of logic operation of HW gate and SW
gate. The HW gate evaluation of the connection ‘Gate 3’ may be deactivated by the
parametrization. With a de-activated HW gate evaluation the triggering exclusively
happens by setting the SW gate of SFB 47.
Gate function abort and The parametrization defines if the gate interrupts or aborts the counter process.
interrupt
n At abort function the counter starts counting with the load value after gate restart.
144 HB400 | CPU | M13-CCF0000 | en | 20-02

n At interrupt function, the counter starts counting with the last recent counter value
after gate restart.
Counter 0 ... 2
SW gate Gate function Reaction counter 0 ... 2

Edge 0-1 Abort count process Restart with load value
Edge 0-1 Interrupt count process Continue
5.6.6.3 Comparator
Function In the CPU a comparison value may be stored. During the counting procedure the
counter value is compared with the comparative value. Depending on the result of the
comparison the output channel of the counter and the status bit of STS_CMP of SFB 47
can be set. In addition, you can configure a hardware interrupt. A comparison value can
be specified via the parametrization respectively the job interface of SFB 47.
HB400 | CPU | M13-CCF0000 | en | 20-02 145

5.6.6.4 Additional functions counter 3

Exclusively counter 3 has the following additional functions:
n HW gate via Gate 3
n Latch function
5.6.6.4.1 HW gate via Gate 3

Starting, stopping and interrupting a count function of counter 3 happens via the internal
gate (I gate). The i gate is the result of logic operation of HW gate and SW gate. The HW
gate evaluation of the connection ‘Gate 3’ may be deactivated by the parametrization.
With a de-activated HW gate evaluation the triggering exclusively happens by setting the
SW gate of the SFB 47.
Counter 3:
SW gate HW gate Gate function Reaction counter 3:

Edge 0-1 de-activated Abort count process Restart with load value
Edge 0-1 de-activated Interrupt count process Continue
Edge 0-1 1 Abort count process Continue
1 Edge 0-1 Abort count process Restart with load value
Edge 0-1 1 Interrupt count process Continue
1 Edge 0-1 Interrupt count process Continue
Counter 3 - count once
If the internal gate has been closed automatically it may only be opened again under the following conditions:
SW gate HW gate I gate
1 Edge 0-1 1
Edge 0-1 (after edge 0-1 at HW gate) Edge 0-1 1
5.6.6.4.2 Latch function

Function n As soon as during a count process an edge 0-1 is recognized at the "Latch" input of
counter 3, the current counter value is stored in the according latch register.
n You may access the latch value via the parameter LATCHVAL of the SFB 47.
n A just in LATCHVAL loaded value remains after a STOP-RUN transition.
146 HB400 | CPU | M13-CCF0000 | en | 20-02

5.6.6.5 Counter output channel

Characteristics of the Each counter has an output channel. You pre-define the behavior of the counter output
output via the parametrization:
n no comparison:
– The output is used as normal output.
– SFB 47:
The input parameter CTRL_DO is effect less.
The status bits STS_DO and STS_CMP (status comparator in the instance DB)
remain reset.
n Counter value ³ comparison value respectively counter value £ comparison value
– The output remains set as long as the counter value is higher or equal compar-
ison value respectively lower or equal comparison value.
– SFB 47:
Control bit CTRL_DO must be set.
The comparison result is shown by the status bit STS_CMP. This status bit may
only be reset if the comparison condition is no longer fulfilled.
– When the counter reaches the comparison value the output is set for the parame-
trized pulse duration. When you've set a main counting direction the output is only
set at reaching the comparison value from the main counting direction.
If the pulse duration = 0, the output is set until the comparison condition is not
longer fulfilled.
– SFB 47:
Control bit CTRL_DO must be set.
The status of the digital output may be shown by the status bit ST_DO.
The comparison result is shown by the status bit STS_CMP. The bit may only be
reset if the pulse duration has expired.
n Pulse duration
– The pulse duration starts with the setting of the according digital output.
– The inaccuracy of the pulse duration is less than 1ms.
– There is no past triggering of the pulse duration when the comparison value has
been left and reached again during pulse output.
– If the pulse duration is changed during operation, it will take effect with the next
pulse.
– If the pulse duration = 0, the output is set until the comparison condition is not
longer fulfilled.
– Range of values: 0...510ms in steps of 2ms
5.6.6.6 Hysteresis function

Hysteresis n 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.
n For the hysteresis you may set a range of 0 to 255.
n The settings 0 and 1 deactivate the hysteresis.
n The hysteresis influences zero run, comparison, over- and underflow.
n An activated hysteresis remains active after a change. The new hysteresis range is
activated with the next hysteresis event.
The following pictures illustrate the output behavior for hysteresis 0 and hysteresis 3 for
the according conditions:
HB400 | CPU | M13-CCF0000 | en | 20-02 147

Effect at counter value ³

comparison value
1 Counter value ³ comparison value ® output is set and hysteresis activated

2 Leave hysteresis range ® output is reset
3 Counter value ³ comparison value ® output is set and hysteresis activated
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
With reaching the comparison condition the hysteresis gets active. At active hysteresis
the comparison result remains unchanged until the counter value leaves the set hyste-
resis range. After leaving the hysteresis range a new hysteresis is only activated with
again reaching the comparison conditions.
Effect at pulse at compar-

ison value with pulse
duration Zero
1 Counter value = comparison value ® output is set and hysteresis activated

2 Leave hysteresis range ® output is reset and counter value < comparison value
148 HB400 | CPU | M13-CCF0000 | en | 20-02


4 Output is reset for leaving hysteresis range and counter value > comparison value
6 Counter value = comparison value and hysteresis active ® output remains set
7 Leave hysteresis range and counter value > comparison value ® output is reset
With reaching the comparison condition the hysteresis gets active. At active hysteresis
the comparison result remains unchanged until the counter value leaves the set hyste-
resis range. After leaving the hysteresis range a new hysteresis is only activated with
again reaching the comparison conditions.
Effect at pulse at compar-

ison value with pulse
duration not zero
1 Counter value = comparison value ® pulse of the parameterized pulse 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 pulse duration is put out, the hysteresis is de-activated
4 Leaving the hysteresis range without changing counting direction ® hysteresis is de-
activated
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 pulse duration is put out, the hysteresis is de-activated
With reaching the comparison condition the hysteresis gets active and a pulse of the par-
ameterized 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 module. 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.
HB400 | CPU | M13-CCF0000 | en | 20-02 149

Counting > Diagnostics and interrupt
5.6.7 Diagnostics and interrupt

Overview GSDML
n Edge at an digital interrupt input
Via the hardware configuration you can define the following trigger for a hardware inter-
rupt that can trigger a diagnostics interrupt:
n Reaching the comparison value
n Overflow respectively at overrun upper counter limit
n Underflow respectively at underrun lower counter limit
n Opening the HW gate with open SW gate - except for counter 3
n Closing the HW gate with open SW gate - except for counter 3
150 HB400 | CPU | M13-CCF0000 | en | 20-02

Frequency measurement > Properties
5.7 Frequency measurement

5.7.1 Properties
n In this operating mode the CPU counts the incoming pulses during a specified inte-
gration time and outputs them as frequency value.
n Integration time 10ms ... 10000ms in steps of 1ms configurable
n Control by the user program via SFB 48
1 Integration time
2 Counting pulse
3 SW gate
4 Frequency measurement start
5 Frequency measurement stop
Measuring procedure n The measurement is carried out during the integration time and is updated after the
integration time has expired.
n If the period of the measured frequency exceeds the assigned integration time, this
means there was no edge 0-1 during the measurement, the measurement value 0 is
returned.
n The calculated frequency value is supplied in "mHz" units.
n The measurement value can be read with MEAS_VAL from SFB 48.
n As long as the SW gate is open, you can request the calculated frequency.
n The number of activated channels does not influence the max. frequency, which is
defined in the technical data.
1 Integration time
2 Counting pulse
3 SW gate
4 Evaluated frequency
The counting function is disabled during the pulse width modulation on

the same channel.
HB400 | CPU | M13-CCF0000 | en | 20-02 151

Frequency measurement > Wiring
5.7.2 Wiring
5.7.2.1 Frequency measurement inputs
Connect the signal to be measured at input B of the corresponding counter.
X1: DI byte 0

green
1 DI 0.7 I Frequency measurement 2 *
9 0V I 3M: GND for frequency measurement
10 DC 24V I 3L+: DC 24V power section supply for frequency measurement
X5: DI byte 1

green
152 HB400 | CPU | M13-CCF0000 | en | 20-02

Frequency measurement > Parametrization
5.7.3 Proceeding
Hardware configuration In the Siemens SIMATIC Manager the following steps should be executed:
2. Double-click the counter sub module of the CPU 314C-2 PN/DP (314-6EH04-0AB0
V3.3).
box with default values for this counter mode is created and shown. Select for the
corresponding channel the operating mode ‘Frequency counting’ .
User program n The SFB 48 should cyclically be called (e.g. OB 1) for controlling the frequency meas-
urement.
the SFB are stored.

address
Counter 816 DINT Channel 0: Frequency value
820 DINT Channel 1: Frequency value

address
820 DWORD reserved
824 DWORD reserved
828 DWORD reserved
HB400 | CPU | M13-CCF0000 | en | 20-02 153

Frequency measurement > Parametrization
5.7.4.2 Interrupt selection

Via ‘Basic parameters’ you can reach ‘Select interrupt’ . Here you can define the inter-
n None: The interrupt function is de-activated.
n Process: The following events of the frequency measurement can trigger a hardware
interrupt (selectable via ‘Frequency counting’ ):
– End of measurement
n Diagnostics and process: A diagnostics interrupt is only triggered when a hardware
interrupt was lost.
5.7.4.3 Frequency measurement

figuration The following parameters are relevant for frequency measurement, which must be speci-
fied or determined:
1 Integration time
2 Counting pulse
3 SW gate
Parameter overview

Integration time Specify the integration time 100ms
Range of values: 10ms ... 10000ms in steps of 1ms
max. counting frequency ... Specify the max. frequency for the corresponding input 60kHz
1kHz 400µs
2kHz 200µs
5kHz 80µs
10kHz 40µs
30kHz 13µs
60kHz 6.7µs

End of measurement Hardware interrupt at end of measurement de-activated
154 HB400 | CPU | M13-CCF0000 | en | 20-02

Frequency measurement > Status indication

green

green
1 - - reserved
2 - - reserved
DI +x
green
DI +0.0 DI +0.7 Digital I+0.0 ... 0.7 has "1" signal
Digital I+0.0 ... 0.7 has "0" signal
HB400 | CPU | M13-CCF0000 | en | 20-02 155

Frequency measurement > Status indication
xL+
green
xF
green / red
no error
156 HB400 | CPU | M13-CCF0000 | en | 20-02

Pulse width modulation - PWM > Wiring
5.8 Pulse width modulation - PWM

5.8.1 Properties
n By presetting of time parameters, the CPU evaluates a pulse sequence with
according pulse/pause ratio and outputs it via the according output channel.
n Channel 0 and 1 are supported
1 Period
2 On-delay
3 Pulse duration
4 Pulse pause
The counting function is disabled during the pulse width modulation on

the same channel.
5.8.2 Wiring
5.8.2.1 Pulse width modulation outputs
X2: DO byte 0
HB400 | CPU | M13-CCF0000 | en | 20-02 157

Pulse width modulation - PWM > Parametrization

green
red
7 DO 0.1 O PWM 1
8 DO 0.0 O PWM 0
9 0V I 4M: GND for PWM

10 DC 24V I 4L+: DC 24V power section supply for PWM
5.8.3 Proceeding
Hardware configuration PWM and pulse train output use the same hardware configuration. Switching between
these modes is done within the SFB 49. In the Siemens SIMATIC Manager the following
steps should be executed:
2. Double-click the counter sub module of the CPU 314C-2 PN/DP.
box with default values for this counter mode is created and shown. For PWM
respectively pulse train output select for the corresponding channel the operating
mode ‘Pulse width modulation - PWM’ .
User program n The SFB 49 should cyclically be called (e.g. OB 1) for controlling the pulse width
modulation.
– The SFB 49 is used for PWM and pulse train output.
– The switching between the modes takes place by the presetting of the pulse
number (JOB_ID = 08h/09h). As soon as you specify a pulse number > 0, you
switch to the pulse train mode, otherwise PWM is active.
the SFB are stored.

address
Counter 816 DINT reserved
820 DINT reserved
824 DINT reserved
828 DINT reserved
158 HB400 | CPU | M13-CCF0000 | en | 20-02

Pulse width modulation - PWM > Parametrization

address
820 DWORD reserved
824 DWORD reserved
828 DWORD reserved
5.8.4.2 Pulse width modulation

figuration The following parameters are relevant for PWM, which must be specified or determined:
1 Period
2 On-delay
3 Pulse duration
4 Pulse pause
Parameter overview

Output format Here specify the range of values for the output. The CPU Per mil
hereby determines the pulse duration:
n Per mil
– Output value is within 0 ... 1000
– Pulse duration = (Output value / 1000) x Period
n S7 Analog value:
– Output value is Siemens S7 analog value 0 ...
27648
Time base Here you can set the time base, which will apply for resolu- 0.1ms
tion and range of values of the period duration, minimum
pulse duration and on-delay.
n 1ms: Die Time base is 1ms
n 0.1ms: Time base is 0.1ms
On-delay Enter here a value for the time to expire from the start of 0
the output sequence to the output of the pulse. The pulse
sequence is output at the output channel, on expiration of
the on-delay.
Range of values: 0 ... 65535 from this there are the fol-
lowing effective values:
n Time base 1ms: 0 ... 65535ms
n Time base 0.1ms: 0 ... 6553.5ms
HB400 | CPU | M13-CCF0000 | en | 20-02 159

Pulse width modulation - PWM > Status indication

Period With the period you define the length of the output 50*
sequence, which consists of pulse duration and pulse
pause.
Range of values:
Time base 1ms: 1 ... 87ms
Time base 0.1ms: 0.4 ... 87.0ms
Minimum pulse duration With the minimum pulse duration you can suppress short 2
output pulses and short pulse pauses. All pulses or
pauses, which are smaller than the minimum pulse dura-
tion, are suppressed. This allows you to filter very short
pulses (spikes), which can not be recognized by the
periphery.
Range of values:
Time base 1ms: 0 ... Period / 2 * 1ms
Time base 0.1ms: 2 ... Period / 2 * 0.1ms
*) This value can vary depending on the configuration tool and can be out of range. Values, which are out of range are invalid and must be adjusted accordingly!

green
DO +0.0 PWM 0 has "1" signal
PWM 0 has "0" signal
DO +0.1 PWM 1 has "1" signal
PWM 1 has "0" signal
160 HB400 | CPU | M13-CCF0000 | en | 20-02

Pulse width modulation - PWM > Status indication
xL+
green
xF
green / red
no error
HB400 | CPU | M13-CCF0000 | en | 20-02 161

Pulse train > Properties
5.9 Pulse train

5.9.1 Properties
n By presetting of time parameters, the CPU evaluates a pulse sequence with
according pulse/pause ratio and outputs it via the according output channel.
n The output is as a pulse-direction command (P/D).
– Output frequency pattern via pulse train channel
– To output the direction, an additional output is to be used, which is to be con-
trolled via your user program.
1 Number of pulses
2 Period duration
3 Pulse duration
4 Pulse pause
The counting function is disabled during the pulse train output on the
same channel.
162 HB400 | CPU | M13-CCF0000 | en | 20-02

Pulse train > Proceeding
5.9.2 Wiring
5.9.2.1 Pulse train outputs
X2: DO byte 0

green
red
7 DO 0.1 O Pulse train 1
8 DO 0.0 O Pulse train 0
9 0V I 4M: GND for pulse train

10 DC 24V I 4L+: DC 24V power section supply for pulse train
5.9.3 Proceeding
Hardware configuration PWM and pulse train output use the same hardware configuration. Switching between
these modes is done within SFB 49. In the Siemens SIMATIC Manager the following
steps should be executed:
2. Double-click the counter sub module of the CPU 314C-2 PN/DP.
box with default values for this counter mode is created and shown. For PWM
respectively pulse train output select for the corresponding channel the operating
mode ‘Pulse width modulation - PWM’ .
HB400 | CPU | M13-CCF0000 | en | 20-02 163

Pulse train > Parametrization
User program n The SFB 49 should cyclically be called (e.g. OB 1) for controlling the pulse train
output.
– The SFB 49 is used for PWM and pulse train output.
– The switching between the modes takes place by the presetting of the pulse
number (JOB_ID = 08h/09h). As soon as you specify a pulse number > 0, you
switch to the pulse train mode, otherwise PWM is active.
the SFB are stored.

address
Counter 816 DINT reserved
820 DINT reserved
824 DINT reserved
828 DINT reserved

address
820 DWORD reserved
824 DWORD reserved
828 DWORD reserved
5.9.4.2 Pulse train output

figuration For pulse train following parameters are relevant, to be specified or determined:
164 HB400 | CPU | M13-CCF0000 | en | 20-02

Pulse train > Parametrization
1 Number of pulses
2 Period duration
3 Pulse duration
4 Pulse pause
Parameter overview

n Per mil
– Pulse duration = (Output value / 1000) x period
duration
n S7 Analog value:
27648
– Pulse duration = (Output value / 27648) x period
duration
n 1ms: The time base is 1ms
n 0.1ms: Time base is 0.1ms
On-delay This parameter is ignored. 0
Period duration With period duration you define the length of the output 50*
pause.
Range of values:
Time base 1ms: 1 ... 87ms
Time base 0.1ms: 0.4 ... 87.0ms
HB400 | CPU | M13-CCF0000 | en | 20-02 165

Pulse train > Status indication

periphery.
Range of values:
Time base 1ms: 0 ... Period duration / 2 * 1ms
Time base 0.1ms: 2 ... Period duration / 2 * 0.1ms
*) This value can vary depending on the configuration tool and can be out of range. Values, which are out of range are invalid and must be adjusted accordingly!

green
DO +0.0 Pulse train 0 has "1" signal
Pulse train 0 has "0" signal
DO +0.1 Pulse train 1 has "1" signal
Pulse train 1 has "0" signal
xL+
green
xF
green / red
no error
166 HB400 | CPU | M13-CCF0000 | en | 20-02

Diagnostic and interrupt > Process interrupt
5.10 Diagnostic and interrupt

5.10.1 Overview
Hardware interrupt The parametrization allows you to define the following trigger for a hardware interrupt:
n Edge at an digital interrupt input
n Reaching the comparison value
n Overflow respectively at overrun upper counter limit
n Underflow respectively at underrun lower counter limit
n Opening the HW gate with open SW gate - except for counter 3
n Closing the HW gate with open SW gate - except for counter 3
Diagnostics interrupt The VIPA specific parameters allow you to define the following trigger for a diagnostics
interrupt Ä Chap. 4.9 ‘Setting VIPA specific CPU parameters’ page 82:
n Hardware interrupt lost
n Error: 4L+ DC 24V DO power section supply
n Error: 3L+: DC 24V DI power section supply
n Short circuit overload: DO
5.10.2 Process interrupt
An interrupt for the corresponding channel operating mode can only be

triggered if you have additionally parameterized ‘Diagnostics+Process’ at
‘Select interrupt’ of the ‘Basic parameters’ .
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. The assignment of local double word 8 depends on the parameterized operating mode
of each channel.
HB400 | CPU | M13-CCF0000 | en | 20-02 167

Diagnostic and interrupt > Process interrupt
Local double word 8 of OB 40 at Alarm Inputs
Local byte Bit 7...0

8 n Bit 0: Edge at I+0.0
n Bit 1: Edge at I+0.1
9 n Bit 0: Edge at I+1.0
10...11 n Bit 7 ... 0: reserved
Local double word 8 of OB 40 at counter function

8 n Bit 1, 0: 0 (fix)
n Bit 2: Over-/underflow value counter 0
n Bit 3: Counter 0 reached comparison value
n Bit 7 ... 4: 0 (fix)
9 n Bit 1, 0: 0 (fix)
n Bit 7 ... 4: 0 (fix)
10 n Bit 1, 0: 0 (fix)
n Bit 7 ... 4: 0 (fix)
11 n Bit 0: Gate counter 3 open (activated)
n Bit 1: Gate counter 3 closed
n Bit 4: Counter 3 new latch value
n Bit 7 ... 5: 0 (fix)
168 HB400 | CPU | M13-CCF0000 | en | 20-02

Diagnostic and interrupt > Diagnostic interrupt
Local double word 8 of OB 40 at frequency measurement

8 n Bit 0: End of measurement channel 0 (end of the integration time)
n Bit 7 ... 1: 0 (fix)
n Bit 7 ... 1: 0 (fix)
n Bit 7 ... 1: 0 (fix)
n Bit 7 ... 1: 0 (fix)
5.10.3 Diagnostic interrupt

Function
An interrupt for the corresponding channel operating mode can only be
triggered if you have additionally parameterized ‘Diagnostics+Process’ at
‘Select interrupt’ of the ‘Basic parameters’ .
Via the parameterization (record set 7Fh) you may activate a global diagnostic interrupt
for the module. 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 diag-
nostic interrupt interrupts the recent process interrupt execution in OB 40 and branches in
OB 82 to diagnostic interrupt processingincoming. If during the diagnostic interrupt pro-
cessing 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 pro-
cessing 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 inter-
ruptoutgoing. All events of a channel between diagnostic interruptincoming and diagnostic inter-
ruptoutgoing are not stored and get lost. Within this time window (1. diagnostic inter-
ruptincoming until last diagnostic interruptoutgoing) the SF-LED of the CPU is on. Additionally
for every diagnostic interruptincoming/outgoing an entry in the diagnostic buffer of the CPU
occurs.
HB400 | CPU | M13-CCF0000 | en | 20-02 169

Example:
Diagnostic interrupt pro- Every OB 82 call causes an entry in the diagnostic buffer of the CPU containing error
cessing 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 a clear assignment of the data to the last diagnostic interrupt is not longer pos-
sible. The record sets of the diagnostic range have the following structure:
Record set 0 Diag- Byte Bit 7...0

nosticincoming
0 n Bit 0: set at module failure
– Counter/Frequency measurement: Process interrupt lost
– Digital input: Process interrupt lost
– Missing power supply DI or DO
– Digital output: short circuit/overload
n Bit 1: set at internal error
n Bit 2: set at external error
n Bit 3: set at channel error
n Bit 4: set at missing external power supply
n Bit 7 ... 5: 0 (fix)
1 n Bit 3 ... 0: Module class
– 1111b: Digital module
or
– 1000b: Function module
n Bit 4: Channel information present
n Bit 7 ... 5: 0 (fix)
170 HB400 | CPU | M13-CCF0000 | en | 20-02

Byte Bit 7...0

2 n Bit 3 ... 0: 0 (fix)
n Bit 4: set at missing internal power supply
n Bit 7 ... 5: 0 (fix)
3 n Bit 5 ... 0: 0 (fix)
n Bit 6: Process interrupt lost
n Bit 7: 0 (fix)
Record set 0 Diagnosticout- After the removing error a diagnostic messageoutgoing takes place if the diagnostic interrupt
going release is still active.
Byte Bit 7...0

0 n Bit 0: set at module failure
n Bit 1: set at internal error
n Bit 2: set at external error
n Bit 3: set at channel error
n Bit 4: set at missing external power supply
n Bit 7 ... 5: 0 (fix)
1 n Bit 3 ... 0: Module class
– 1111b: Digital module
or
– 1000b: Function module
n Bit 4: Channel information present
n Bit 7 ... 5: 0 (fix)
2 n Bit 3 ... 0: 0 (fix)
n Bit 4: set at missing internal power supply
n Bit 7 ... 5: 0 (fix)
3 n Bit 7 ... 0: 0 (fix)
The record set 0 of the alarm interrupts, counter function, frequency

measurement and pulse width modulation has the same structure. There
are differences in the structure of record set 1.
HB400 | CPU | M13-CCF0000 | en | 20-02 171

Diagnostic record set 1 at The record set 1 contains the 4byte of the record set 0 and additionally 12byte module
Alarm Inputs specific diagnostic data. The diagnostic bytes have the following assignment:
Byte Bit 7...0

0 ... 3 Content record set 0 Ä ‘Record set 0 Diagnosticincoming’ page 170
4 n Bit 6 ... 0: Channel type (here 70h)
– 70h: Digital input
n Bit 7: More channel types present
– 0: no
– 1: yes
5 Number of diagnostic bits per channel (here 08h)
6 Number of channels of a module (here 08h)
7 n Bit 0: Error in channel group 0 (I+0.0 ... I+0.3)
n Bit 1: Error in channel group 1 (I+0.4 ... I+0.7)
n Bit 7 ... 4: reserved
8 Diagnostic interrupt due to "process interrupt lost" at...
n Bit 0: ... input I+0.0
n Bit 1: 0 (fix)
n Bit 3: 0 (fix)
n Bit 5: 0 (fix)
n Bit 7: 0 (fix)
n Bit 1: 0 (fix)
n Bit 3: 0 (fix)
n Bit 5: 0 (fix)
n Bit 7: 0 (fix)
n Bit 1: 0 (fix)
n Bit 3: 0 (fix)
n Bit 5: 0 (fix)
n Bit 7: 0 (fix)
172 HB400 | CPU | M13-CCF0000 | en | 20-02

Byte Bit 7...0

n Bit 1: 0 (fix)
n Bit 3: 0 (fix)
n Bit 5: 0 (fix)
n Bit 7: 0 (fix)
12 ... 15 n Bit 7 ... 0: reserved
Diagnostic record set 1 at The record set 1 contains the 4byte of the record set 0 and additionally 12byte module
counter function specific diagnostic data. The diagnostic bytes have the following assignment:
Byte Bit 7...0

– 76h: Function module
– 0: no
– 1: yes
7 n Bit 0: Error in channel group 0 (Counter 0)
n Bit 1: Error in channel group 1 (Counter 1)
n Bit 7 ... 4: reserved
n Bit 1, 0: reserved
n Bit 2: Over-/underflow/end value counter 0
n Bit 7 ... 4: 0 (fix)
n Bit 7 ... 4: 0 (fix)
n Bit 7 ... 4: 0 (fix)
HB400 | CPU | M13-CCF0000 | en | 20-02 173

Byte Bit 7...0

n Bit 0: Gate counter 3 open (activated)
n Bit 1: Gate counter 3 closed
n Bit 4: Counter 3 new latch value
n Bit 7 ... 5: 0 (fix)
12 ...15 n Bit 7 ... 0: reserved
Diagnostic Record set 1 at The record set 1 contains the 4byte of the record set 0 and additionally 12byte module
frequency measurement specific diagnostic data. The diagnostic bytes have the following assignment:
Byte Bit 7...0

– 76h: Function module
– 0: no
– 1: yes
7 n Bit 0: Error in channel group 4 (Frequency meter 0)
n Bit 1: Error in channel group 5 (Frequency meter 1)
n Bit 7 ... 4: 0 (fix)
n Bit 0: End of measurement channel 0 (End of integration time)
n Bit 7 ... 1: 0 (fix)
n Bit 7 ... 1: 0 (fix)
n Bit 7 ... 1: 0 (fix)
n Bit 7 ... 1: 0 (fix)
12 ... 15 0 (fix)
174 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO Deployment OPC UA
General
6 Deployment OPC UA
Please note that the simultaneous use of OPC UA and WebVisu on the
same interface is not supported! When attempting to activate them, both
servers are stopped and the diagnostic message 0xE989 or 0xE9AB is
output.
n With an OPC UA project there is the possibility to configure an OPC UA server on

your CPU.
n The configuration of an OPC UA project is only possible with the SPEED7 Studio
V1.8.6 and up.
n Since a OPC UA project is only executable by memory card, a VIPA memory card
(VSD, VSC) of YASKAWA must be plugged. Please note that you must always use a
VSC card suitable for your CPU. Ä Chap. 4.16 ‘Deployment storage media - VSD,
VSC’ page 110
n If the memory card is removed for a short time, the SF LED gets on. This indicates
that a feature is missing and the OPC UA server will quit after 72 hours.
n When the project is transferred from the SPEED7 Studio, the OPC UA project is auto-
matically transferred as TAR file to the inserted memory card.
n The OPC UA server must be activated in the CPU. Ä Chap. 7.2 ‘Activate WebVisu
functionality’ page 204
n The access is made with an OPC UA client via the ‘Endpoint URL’ of the corre-
sponding interface. The ‘Endpoint URL’ can be found on the Device web page of the
CPU. Ä Chap. 4.11.1.1.1 ‘Tab: ‘OPC UA’ ’ page 96
6.1 General
Term definitions n OPC - Open Platform Communications
– OPC is an interoperability standard for secure and reliable data exchange in
industrial automation.
– OPC is platform-independent and ensures a seamless flow of information
between devices from different manufacturers.
n UA - Unified Architecture
– UA specifies security features and data modeling based on a service-oriented
architecture (SOA).
HB400 | CPU | M13-CCF0000 | en | 20-02 175

Deployment OPC UA VIPA System MICRO
Basics OPC UA > OPC UA
Precondition n VIPA SPEED7 Studio from Version V1.8.6

– The functionality for the OPC UA configuration is integrated in the SPEED7
Studio.
n Siemens SIMATIC Manager from version V5.5 and VIPA SPEED7 Studio from ver-
sion V1.8.6
– The OPC UA configuration is done with the OPC UA Configurator. This is part of
the VIPA SPEED7 Studio from version V1.8.6.
– When calling the OPC UA Configurator, the SPEED7 Studio opens with function-
ality limited to OPC UA configuration.
– The OPC UA Configurator is to be called from the Siemens SIMATIC Manager as
external device tool.
– To be able to call the OPC UA Configurator as an external device tool, you must
first register it in the Siemens SIMATIC Manager. This is done with SPEED7 Tools
Integration, which is automatically installed during the installation of the SPEED7
Studio.
– The OPC UA Configurator is to be called from the Siemens SIMATIC Manager
after project creation and online configuration.
– The OPC UA Configurator automatically imports the data for the OPC UA configu-
ration from the project data of the Siemens SIMATIC Manager.
– The OPC UA configuration is transferred online from the OPC UA Configurator.
The OPC UA Configurator automatically imports the data for the OPC UA configu-
ration from the project data of the Siemens SIMATIC Manager.
n Siemens TIA Portal from version V15.0 and VIPA SPEED7 Studio from version
V1.8.6
– The OPC UA configuration is done with the OPC UA Configurator. This is part of
the VIPA SPEED7 Studio from version V1.8.6.
– When calling the OPC UA Configurator, the SPEED7 Studio opens with function-
ality limited to OPC UA configuration.
– The OPC UA Configurator is to be called from the Siemens TIA Portal as external
device tool.
– To be able to call the OPC UA Configurator as an external device tool, you must
first register it in the Siemens TIA Portal. This is done with SPEED7 Tools Integra-
tion, which is automatically installed during the installation of the SPEED7 Studio.
– The OPC UA Configurator is to be called from the Siemens TIA Portal after
project creation and online configuration.
– The OPC UA Configurator automatically imports the data for the OPC UA configu-
ration from the project data of the Siemens TIA Portal.
– The OPC UA configuration is transferred online from the OPC UA Configurator.
The OPC UA Configurator automatically imports the data for the OPC UA configu-
ration from the project data of the Siemens TIA Portal.
6.2 Basics OPC UA

6.2.1 OPC UA
Standard for data and OPC UA defines a common standard for data and information exchange in an ‘Industry
information exchange 4.0’ environment. Due to the platform independence, the integrated security concept and
the data type information supplied with the data, OPC UA provides the basis for machine-
readable and cross-level communication.
OPC - Open Platform n Classic variant not scalable and exclusively for Microsoft WindowsÒ
Communications n For each type of data transfer, such as real-time data, history data, interrupts, events,
etc., a separate solution with its own semantics is required, such as OPC DA, OPC
HDA, OPC A&E, etc.
n Separate and complex effort required for security settings.
176 HB400 | CPU | M13-CCF0000 | en | 20-02

Basics OPC UA > Information modeling
n OPC requires a complex DCOM configuration.

n OPC requires separate complex firewall settings.
OPC UA - Open Platform n Scalable and platform-independent communication standard specified in IEC 62541.
Communications Unified n Standardization of classic OPC specifications with integrated security concept.
Architecture n The OPC UA security concept includes user and application authentication, message
signing, and encryption of transmitted data.
n IP-based, optimized, binary protocol for Internet and firewall communication via one
port (4840).
n With OPC UA, any type of information is available at any time and place for any
authorized application and authorized person. For example, raw data and prepro-
cessed information can be transported safely from the sensor and field level to the
control system and into the production planning systems.
n SOA (Service Oriented Architecture) replaces the Microsoft DCOM technology with
open, platform-independent protocols with integrated security mechanisms.
– Communication takes place via standardized services based on the Information
model of OPC UA.
– The services are divided into different task groups.
– Based on a basic model, arbitrarily complex, object-oriented extensions of the
services can be carried out, without affecting interoperability.
OPC UA server n An OPC UA server provides information within a network that can be retrieved from
an OPC UA client.
n The data exchange can take place via security certificates, which have to be stored
accordingly in the server.
n The OPC UA server provides basic services such as data exchange or navigation
through the address space.
n The OPC UA configuration is used to define the variables or contents that an
OPC UA server should provide.
n The OPC UA configuration is done via an external tool such as for VIPA CPUs the
VIPA OPC UA Configurator.
OPC UA client OPC UA clients are programs with the following functionality:
n Read or write access to information of the OPC UA server.
n Access is controlled by access rights.
n Execute services on the OPC UA server.
Communication types n Client/Server

– An OPC UA client accesses information from the OPC UA server via services,
provided by the OPC UA server. Here a fix defined connection is used.
– Example: OPC UA client retrieves status of an input in the CPU.
n Publisher/Subscriber
– A Publisher sends to unknown Subscriber (clients) without a fixed connection.
– Example: Sensors send data to the cloud.
6.2.2 Information modeling

Information model n Information models are used to describe devices and their data.
n The basis is the Core specification. The Core specification describes the structure of
the address range and of the services, such as the entry points for the clients in the
address space of an OPC UA server.
HB400 | CPU | M13-CCF0000 | en | 20-02 177

Basics OPC UA > Information modeling
n In an information model, the content of the address space of the OPC UA server is
described.
n The Information models are structured in layers. Each higher-order type is based on
certain basic rules. Thus, clients who only know the basic rules can still edit complex
information models, e.g. navigate through the address space and read or write data
variables.
n In the address space, all information is represented by Nodes, which are intercon-
nected via references.
n A node is always an instance of a NodeClass.
n OPC UA offers basic services such as data exchange or navigation through the
address space. The services are grouped in Service Sets.
Node classes The following NodeClasses are defined in the OPC UA specification:
n Variable - class of variables
n Method - class of functions
n Object - class of objects
n View - Class of view of a subset of nodes
n DataType - Class of the data types of the value of a variable
n VariableType - Class of the data types of a variable
n ObjectType - class of object types
n ReferenceType - class of reference types
Node attributes Each node consists of attributes and references. Some attributes may also be optional.
The following attributes of each NodeClass must be published:
n NodeID - Unique identifier of a nodes in the address space
n NodeClass - class of node instance
n BrowseName - name of the node in plain text
n DisplayName - display name of the Node for the user
n Description - Description of the node (optional)
OPC UA services n OPC UA services are abstract descriptions defined by request and response mes-
sages.
n The available services of an OPC UA server are defined in the server profile and
grouped together in service sets.
Basic service sets n Discovery Service Set

– Services for discovering existing servers and endpoints.
n SecureChannel Service Set
– Services for opening and closing secure communication channels.
n Session Service Set
– Services for the client to create and manage a session.
n NodeManagement Service Set
– Services for creating and deleting nodes and references.
n View Service Set
– Services for the client to navigate in the address space or in the view.
n Query Service Set
– Services for search queries in the address space.
n Attribute Service Set
– Services for accessing attributes of nodes.
n Method Service Set
– Service for calling a method of an object.
178 HB400 | CPU | M13-CCF0000 | en | 20-02

Basics OPC UA > OPC UA data types and their conversion
n MonitoredItem Service Set

– Services for the client to create and manage monitored items.
– Monitored items are used to log in for data and event notifications.
n Subscription Service Set
– Services for the client to create and manage subscriptions.
– Subscriptions control the way of the data and event notification.
Access n To access an OPC UA server, the endpoint must be known.

n You can navigate via the endpoint using the navigation function through the address
space of the OPC UA server. Here you receive information about the OPC UA server
and the CPU and have access to the objects created in the OPC UA configuration,
such as tags, data blocks, etc.
n Lower network load through ‘subscriptions’
– If variables are to be transmitted only if their value has changed, you have to use
subscriptions.
– To activate a subscription, enter the transmission interval "Publishing Interval" in
the OPC UA client.
– When the subscription is created, tell the server which variables to monitor.
Among other things, you can specify the amount by which a value must change in
order a transfer takes place.
– Since only a change in value of a transmission takes place, the use of subscrip-
tions leads to a reduced network load.
n Fast access through ‘registration’
– Normally the addressing takes place by means of identifier strings. By using a
numeric identifier access can be accelerated. For this reason, you should use the
registration for regular access to certain variables.
– During registration, the OPC UA client assigns the variable to the OPC UA server.
The OPC UA server then generates a numeric identifier and sends it back to the
OPC UA client.
– The numerical identifier is valid for the duration of the session.
– In the properties of the CPU, you can set the maximum number of registered
nodes. This must be taken into account by the OPC UA clients.
– Since the registration takes time, you should put them in the start-up phase of the
OPC UA server.
Due to the system, access to data in complex structures is not consistent.
Setting the sampling intervals (sampling interval, publishing interval) too

short may cause too much network load. Always choose intervals that are
still sufficient for your application.
6.2.3 OPC UA data types and their conversion

Siemens S7 data types are mapped in the namespace via SPEED7 PLC OPC UA data
types. Siemens S7 data types do not always match the OPC UA built-in data types. The
CPU provides variables to the OPC UA server as an OPC UA built-in data type so that
OPC UA clients can access these variables with OPC UA built-in data types via the
server interface. A client can read the "DataType" attribute from such a variable and
reconstruct the original data type.
HB400 | CPU | M13-CCF0000 | en | 20-02 179

Basics OPC UA > OPC UA data types and their conversion
Data type mapping
Siemens S7 data type SPEED7 PLC OPC UA data type OPC UA built-in data type
BOOL BOOL Boolean
BYTE BYTE Byte
WORD WORD UInt16
DWORD DWORD UInt32
INT INT Int16
DINT DINT Int32
REAL REAL Float
S5TIME S5TIME UInt16
à à
TIME TIME Int32
DATE DATE UInt16
TIME_OF_DAY (TOD) TIME_OF_DAY UInt32
CHAR CHAR Byte
COUNTER COUNTER UInt16 (Only valid values)
TIMER TIMER UInt16 (Only valid values)
STRING STRING String
DT DT Byte[8]
Particularities
n String
– The data type STRING in Siemens S7 is a byte array in which the maximum
length and the current length are stored in the first 2 bytes. The other bytes store
the string.
– The OPC UA data type String should be defined in the same way.
n Array
– A read or write job in OPC UA is always an Array access, i.e. always provided
with index and length.
– A single variable is a special case of an Arrays (index 0 and length 1). On the line,
the data type is simply sent several times in succession. For the variable, the
DataType attribute points to the base data type. The ValueRank and ArrayDimen-
sions attributes determine if it is an array and how large the array is.
n Structure
– A structure describes a complex data type.
– You can describe your own structures as a subtype of the abstract data type
Structures, which inherits from the data type BaseDataType.
– Since a client may not know user-specific structures, the variables of the data
type of this structure are uniformly published in an ExtensionObject. The structure
ExtensionObject can be read by any client and also publishes the DataTypeId of
the user-specific structure.
– All structures that are not described by structures of the basic data types are pub-
lished on the server in a TypeDictionary.
– With the description of the structure by the TypeDictionary and the DataTypeId,
which is published by the ExtensionObject, the structure of the ExtensionObject
can be decoded by a client.
– If a client knows in advance the description of a user-specific structure, it can be
decoded without reading the TypeDictionary. In this approach, a client needs to
read and decode the entire tree to access individual elements.
180 HB400 | CPU | M13-CCF0000 | en | 20-02

Basics OPC UA > Integrated security concept
6.2.4 Integrated security concept

Generals to data security The topic of data security and access protection have become increasingly important in
the industrial environment. The increased networking of entire industrial systems to the
network levels within the company together with the functions of remote maintenance
have all served to increase vulnerability. Threats can arise from internal manipulation like
technical errors, operator and program errors respectively from external manipulation like
software viruses and worms, trojans and password phishing.
The most important precautions to prevent manipulation and loss of data security in the
industrial environment are:
n Encrypting the data traffic by means of certificates.
n Filtering and inspection of the traffic by means of VPN - "Virtual Private Networks".
n Identification of the nodes by "Authentication" via save channels.
n Segmenting in protected automation cells, so that only devices in the same group can
exchange data.
Guidelines for information With the "VDI/VDE 2182 sheet 1", Information Security in the Industrial Automation - Gen-
security eral procedural model, VDI guidelines, the VDI/VDE society for measuring and automa-
tion engineering has published a guide for implementing a security architecture in the
industrial environment. The guideline can be found at www.vdi.de PROFIBUS &
PROFINET International (PI) can support you in setting up security standards by means
of the "PROFINET Security Guideline". More concerning this can be found at the corre-
sponding web site such as www.profibus.com
Security mechanisms in n Verifying the identity of OPC UA servers and clients.

OPC UA n Checking the identity of the users.
n Signed and encrypted data exchange between OPC UA server and clients.
n In the connection settings in the OPC UA Configurator, you can specify how a user of
an OPC UA client must legitimize access to the OPC UA server.
Safety rules:
n Only activate ‘Anonymous-Login’ or ‘Unsecured data traffic’ in exceptional cases.
n Only allow access to variables and data blocks via OPC UA if it is actually required.
Activate only security guidelines that are compatible with the protection
concept for your machine or Application. Deactivate all other security
guidelines.
X.509 certificates OPC UA has integrated security mechanisms in multiple layers. An important component
here are X.509 certificates, which are also used in the PC world. When using certificates,
the OPC UA server delivers data to the client only if the security certificate has been
accepted as valid on both sides. An X.509 certificate includes the following information:
n Version and serial number of the certificate.
n Name of the certification authority.
n Information about the algorithm used by the certification authority to sign the certifi-
cate.
n Start and end of the validity of the certificate.
n Name of the program, person, or organization for which the certificate was signed by
the certification authority.
n The public key of the program, person or organization.
HB400 | CPU | M13-CCF0000 | en | 20-02 181

OPC UA uses three types of X.509 certificates when establishing a client-to-server con-
nection:
n OPC UA application certificates
n OPC UA software certificates
n OPC UA user certificates
n Check when establishing a connection

– When establishing a connection between client and server, the participants check
all information from the certificate that is required to establish integrity.
– Among other things, the period of validity which is stored in the certificate is
checked. Please ensure that the date and time are set correctly for the partici-
pants, otherwise no communication can take place.
n Sign and encrypt
– To avoid tampering, certificates are signed.
– Within the OPC UA Configurator, you can use the ‘Server settings’ to import cer-
tificates or create and sign them yourself.
n Self-signed certificate
– Each participant generates his own certificate and signs it.
– Self-signed certificates are to be transferred to the CPU.
– From a self-signed certificate no new certificates can be derived.
– Sample applications: Static configuration with limited number of communication
participants.
n CA certificate:
– All certificates are created and signed by a certification authority.
– Only the derived and signed certificate of the certification authority is to be trans-
ferred to the CPU.
– The certification authority can generate new certificates. Adding partner devices is
possible at any time.
– Sample applications: Dynamically growing plants.
Digital signature The signature can be used to prove the integrity and origin of a message.
1. The sender forms a hash value as a check value from the clear message.
2. The hash value and a private key result in the digital signature.
3. The clear message is sent to the recipient together with the digital signature.
4. The recipient decrypts the received signature with the public key and thus gets back
the original hash value.
5. The receiver also forms a hash value from the clear message and checks it with the
original hash value. The public key and hash method are included in the X.509 cer-
tificate.
ð n If both hash values are identical, sender and clear message were not
manipulated.
n If both hash values are not identical, the clear message was manipulated or
falsified during transmission.
Encrypting n X.509 certificates are not encrypted; they are public and anyone can see them.
n Encrypting data prevents unauthorized users from knowing the content.
n When encrypting, the sender encrypts the clear message with the recipient's public
key from the X.509 certificate.
n The recipient decrypts the message with his private key. Each owner of the private
key can decrypt a received message.
182 HB400 | CPU | M13-CCF0000 | en | 20-02

Secure Channel n OPC UA uses private and public keys to establish secure channels between client
and server
n Once a secure connection is established, the client and server generate a shared pri-
vate key for signing and encrypting messages.
Security policies OPC UA uses the following security policies to protect messages:
n No security
All messages are unsecured. To use these security policies, connect to a "None" end-
point of a server.
n Sign
All messages are signed. This allows the integrity of the received messages to be
checked. Manipulations are detected. To use these security policies, connect to a
"Sign" endpoint of a server.
n Sign & encrypt
All messages are signed and encrypted. This allows the integrity of the received mes-
sages to be checked. Manipulations are detected. Due to the encryption, no attacker
can read the content of the message. To use these security policies, connect to a
"Sign & Encrypt" endpoint of a server.
The security guidelines are additionally named according to the algorithms used.
Example: "Basic256Sha256 - Sign & Encrypt" means: Secure Endpoint, supports a
set of algorithms for 256-bit hashing and 256-bit encryption.
Please note that the encryption of the communication can affect CPU
performance and therefore the response time of the entire system!
HB400 | CPU | M13-CCF0000 | en | 20-02 183

Usage in Siemens SIMATIC Manager > Precondition
6.3 Activate OPC UA functionality

Proceeding For your CPU can process a OPC UA project, you have to activate the OPC UA function-
ality.
1. Insert a VIPA memory card (VSD, VSC) into your CPU. Please note that you must
always use a VSC card suitable for your CPU. Ä Chap. 4.16 ‘Deployment storage
2. Turn on the CPU, to activate the OPC UA functionality, you have to establish an
Overall reset.
ð As long as the memory card is inserted, the OPC UA functionality remains acti-
vated even after a power cycle. When the project is transferred from the OPC
UA Configurator, the OPC UA project is automatically transferred to the inserted
memory card.
Please regard that the memory card must remain plugged when
you’ve executed activated the OPC UA functionality. Otherwise
the SF LED is on and the OPC UA functionality is deactivated
after 72 hours. As long as an activated memory card is not
inserted, the SF LED is on and the "TrialTime" timer counts
from 72 hours down to 0. After that the OPC UA functionality is
de-activated. By inserting the memory card, the LED goes off
and the CPU runs again without restrictions.
Please note that the use of a OPC UA project, depending on

the scope of the OPC UA project and the PLC project, can influ-
ence the performance and thus the response time of your appli-
cation.
6.4 Usage in VIPA SPEED7 Studio

Precondition n VIPA SPEED7 Studio from Version V1.8.6
– The functionality for the OPC UA configuration is integrated in the SPEED7
Studio. For more information, see the according online help.
6.5 Usage in Siemens SIMATIC Manager

6.5.1 Precondition
Siemens SIMATIC Manager from V5.5 and VIPA SPEED7 Studio from V1.8.6
n The OPC UA configuration happens by the external VIPA OPC UA Configurator.
n The OPC UA Configurator is the SPEED7 Studio reduced to OPC UA functionality.
n The OPC UA Configurator can be registered in the Siemens SIMATIC Manager by
means of the SPEED7 Tools Integration.
n The OPC UA Configurator is to be called from the Siemens SIMATIC Manager after
project creation and online configuration.
n The OPC UA Configurator automatically imports the data for the OPC UA configura-
tion from the project data of the Siemens SIMATIC Manager.
n The OPC UA configuration is transferred online from the OPC UA Configurator. The
OPC UA Configurator automatically imports the data for the OPC UA configuration
from the project data of the Siemens SIMATIC Manager.
184 HB400 | CPU | M13-CCF0000 | en | 20-02

Usage in Siemens SIMATIC Manager > Installation OPC UA Configurator
Please note that only the objects of the LD, FBD and IL languages can be
transferred to the OPC UA Configurator.
6.5.2 Installation OPC UA Configurator

Proceeding
Installation and activation The OPC UA Configurator is part of the SPEED7 Studio with OPC UA functionality. With
of SPEED7 Studio the SPEED7 Tools Integration, which is also installed when installing the SPEED7 Studio
the OPC UA Configurator is to be registered in the Siemens SIMATIC Manager as
external tool.
1. The latest version of the SPEED7 Studio can be found in the download area of
www.vipa.com. Double-click on the installation program an follow the instructions on
the monitor.
The use of the SPEED7 Studio requires that you agree with the
license agreement. During installation, you must confirm this.
Further components are required in order to operate SPEED7 Studio. If the fol-
lowing programs are not already present on your PC, they are automatically
installed:
n Microsoft .NET Framework 4.52
n Microsoft SQL Server© 2014 SP1
n WinPcap
2. You can use a 30-day demo version or activate a license.
In order to use SPEED7 Studio without restrictions, you require a licence, which you
can obtain from your local YASKAWA customer service organisation.
If the PC, on which you would like to use the SPEED7 Studio, is connected to the
Internet, you can activate the licence online. If no license is activated, the dialog box
for activating the license opens with each new start of SPEED7 Studio.
Click on ‘Yes’ .
ð The ‘Product activation’ dialog window will open.
3. Enter the serial number that you received with your order of SPEED7 Studio in the
‘Licence key’ input field.
4. Enter your name in the ‘Your name’ input field.
5. If you enter your e-mail address in the ‘E-mail address’ input field, you receive an
e-mail confirmation regarding the product activation.
6. Click at ‘Activate’ .
ð The licence is activated and the SPEED7 Studio is started.
HB400 | CPU | M13-CCF0000 | en | 20-02 185

Usage in Siemens SIMATIC Manager > Installation OPC UA Configurator
Registration of SPEED7 SPEED7 Tools Integration is automatically listed in the Windows Start menu during the
Studio in the Siemens installation of the SPEED7 Studio.
SIMATIC Manager as
1. To start the SPEED7 Tools Integration, click in the Windows Start menu on ‘VIPA ...
OPC UA Configurator.
è SPEED7 Tools Integration’.
ð For SPEED7 Tools Integration can start, you have to acknowledge the security
prompt to change the data on your computer with ‘Yes’ . Afterwards
SPEED7 Tools Integration will be started.
2. Click at ‘GSDML ...’ .

3. Navigate to your GSDML file of your VIPA CPU, which you also use for your config-
uration in the Siemens ‘SIMATIC Manager’ . Select these and click at ‘Confirm’ .
You can also select and use several GSDML files.
ð The identified GSDML files are listed and the selection for the configuration
tools is enabled.
4. Select the Siemens ‘SIMATIC Manager’ , in which the SPEED7 Studio is to be reg-
istered as OPC UA Configurator.
5. Click on ‘Start’ .
ð n SPEED7 Studio is registered in the Windows registry as
n In the Siemens SIMATIC Manager the OPC UA Configurator is registered
as externally callable program.
n All changes are recorded in a log file, which you can output via ‘Log file’ .
6. ‘Close’ closes SPEED7 Tools Integration.
ð With the next start of the Siemens hardware configurator, the SPEED7 Studio
can be called as OPC UA Configurator with to OPC UA configuration limited
functions. More information about the usage can be found in the in the online
help of the OPC UA Configurator.
186 HB400 | CPU | M13-CCF0000 | en | 20-02

Usage in Siemens TIA Portal > Precondition
6.5.3 Steps of the OPC UA configuration

Steps of configuration When using the Siemens SIMATIC Manager, the OPC UA configuration happens by the
following steps:
1. Create your project in the Siemens SIMATIC Manager with the corresponding hard-
ware configuration. Ä Chap. 4.5 ‘Hardware configuration - CPU’ page 69
2. Configure the corresponding Ethernet connection for PG/OP communication and
establish an online connection. Ä Chap. 4.7 ‘Hardware configuration - Ethernet
PG/OP channel’ page 72
3. Save translate and transfer your project. Ä Chap. 4.10 ‘Project transfer’ page 89
4. Call the external OPC UA Configurator from the Siemens SIMATIC Manager. For
this click in the hardware configurator on the VIPA CPU and select
‘Start Device Tool è VIPA Framework è OPC UA Configurator’.
5. Confirm to start an external program with [YES].
NOTICE!
Data exchange between platforms of different vendors
If you allow access, you permit the exchange of data between
OPC UA Configurator and your project data of the Siemens
SIMATIC Manager.
– Ensure that the necessary security guidelines are complied
with.
ð The OPC UA Configurator is started. For the OPC UA configuration, the data is
taken from the Siemens SIMATIC Manager project and listed in the table for the
OPC UA configuration.
Please note that only the objects of the LD, FBD and IL lan-
guages can be transferred to the OPC UA Configurator.
6. Configure the OPC UA server and the data for the OPC UA communication.
7. In the OPC UA Configurator switch to the online dialog and transfer the OPC UA
configuration. For communication the IP address data are taken from the Siemens
SIMATIC Manager project.
ð The OPC UA configuration is now complete. For check you will find information
about your OPC UA configuration on the device web page at ‘OPC UA’ .
Ä Chap. 4.11.1.1.1 ‘Tab: ‘OPC UA’ ’ page 96
6.6 Usage in Siemens TIA Portal

6.6.1 Precondition
Siemens TIA Portal from version V15.0 and VIPA SPEED7 Studio from V1.8.6
n The OPC UA configuration happens by the external VIPA OPC UA Configurator.
n The OPC UA Configurator is the SPEED7 Studio reduced to OPC UA functionality.
n The OPC UA Configurator can be registered in the Siemens TIA Portal by means of
the SPEED7 Tools Integration.
n The OPC UA Configurator is to be called from the Siemens TIA Portal after project
creation and online configuration.
HB400 | CPU | M13-CCF0000 | en | 20-02 187

Usage in Siemens TIA Portal > Installation OPC UA Configurator
n The OPC UA Configurator automatically imports the data for the OPC UA configura-
tion from the project data of the Siemens TIA Portal.
n The OPC UA configuration is transferred online from the OPC UA Configurator. For
the communication the OPC UA Configurator automatically uses the IP address data
of the Siemens TIA Portal project.
Please note that only the objects of the LD, FBD and IL languages can be
transferred to the OPC UA Configurator.
6.6.2 Installation OPC UA Configurator

Proceeding
Installation and activation The OPC UA Configurator is part of the SPEED7 Studio with OPC UA functionality. With
of SPEED7 Studio the SPEED7 Tools Integration, which is also installed when installing the SPEED7 Studio
the OPC UA Configurator is to be registered in the Siemens TIA Portal as external tool.
1. The latest version of the SPEED7 Studio can be found in the download area of
www.vipa.com. Double-click on the installation program an follow the instructions on
the monitor.
The use of the SPEED7 Studio requires that you agree with the
license agreement. During installation, you must confirm this.
Further components are required in order to operate SPEED7 Studio. If the fol-
lowing programs are not already present on your PC, they are automatically
installed:
n Microsoft .NET Framework 4.52
n Microsoft SQL Server© 2014 SP1
n WinPcap
2. You can use a 30-day demo version or activate a license.
In order to use SPEED7 Studio without restrictions, you require a licence, which you
can obtain from your local YASKAWA customer service organisation.
If the PC, on which you would like to use the SPEED7 Studio, is connected to the
Internet, you can activate the licence online. If no license is activated, the dialog box
for activating the license opens with each new start of SPEED7 Studio.
Click on ‘Yes’ .
ð The ‘Product activation’ dialog window will open.
3. Enter the serial number that you received with your order of SPEED7 Studio in the
‘Licence key’ input field.
4. Enter your name in the ‘Your name’ input field.
5. If you enter your e-mail address in the ‘E-mail address’ input field, you receive an
e-mail confirmation regarding the product activation.
6. Click at ‘Activate’ .
ð The licence is activated and the SPEED7 Studio is started.
188 HB400 | CPU | M13-CCF0000 | en | 20-02

Usage in Siemens TIA Portal > Installation OPC UA Configurator
Registration of SPEED7 SPEED7 Tools Integration is automatically listed in the Windows Start menu during the
Studio in the Siemens TIA installation of the SPEED7 Studio.
Portal as
1. To start the SPEED7 Tools Integration, click in the Windows Start menu on ‘VIPA ...
OPC UA Configurator
è SPEED7 Tools Integration’.
ð For SPEED7 Tools Integration can start, you have to acknowledge the security
prompt to change the data on your computer with ‘Yes’ . Afterwards
SPEED7 Tools Integration will be started.
2. Click at ‘GSDML ...’ .

3. Navigate to your GSDML file of your VIPA CPU, which you also use for your config-
uration in the Siemens ‘TIA Portal’ . Select these and click at ‘Confirm’ . You can
also select and use several GSDML files.
ð The identified GSDML files are listed and the selection for the configuration
tools is enabled.
4. Select ‘TIA Portal’ , in which the SPEED7 Studio is to be registered as
5. Click on ‘Start’ .
ð n SPEED7 Studio is registered in the Windows registry as
n In the Siemens TIA Portal the OPC UA Configurator is registered as exter-
nally callable program.
n The current Windows user is registered in the user group Siemens TIA
Openness of the Siemens TIA Portal.
n All changes are recorded in a log file, which you can output via ‘Log file’ .
6. ‘Close’ closes SPEED7 Tools Integration.
ð With the next start of the Siemens TIA Portal, the SPEED7 Studio can be called
as OPC UA Configurator with to OPC UA configuration limited functions. More
information about the usage can be found in the in the online help of the
HB400 | CPU | M13-CCF0000 | en | 20-02 189

Usage in Siemens TIA Portal > Steps of the OPC UA configuration
6.6.3 Steps of the OPC UA configuration

Steps of configuration When using the Siemens TIA Portal, the OPC UA configuration happens by the following
steps:
1. Create your project in the Siemens TIA Portal with the corresponding hardware con-
figuration. Ä Chap. 13.3 ‘TIA Portal - Hardware configuration - CPU’ page 300
2. Configure the corresponding Ethernet connection for PG/OP communication and
establish an online connection. Ä Chap. 13.4 ‘TIA Portal - Hardware configuration -
Ethernet PG/OP channel’ page 303
3. Save translate and transfer your project. Ä Chap. 13.10 ‘TIA Portal - Project
transfer’ page 321
4. Call the external OPC UA Configurator from the Siemens TIA Portal. For this click
at ‘Devices & networks’ on the VIPA CPU and select ‘Start device tool’ .
ð A dialog window opens. Select ‘OPC UA Configurator’ and click [Start].
5. Ignore the query ‘Set interface’ with [OK]
ð The OPC UA Configurator is started.
6. If not yet confirmed, you will now receive an access request in the TIA Portal.
Please note that due to the software the access request does not
appear in the foreground. To show the access request, you must
again bring the Siemens TIA Portal to the foreground. Once the
access has been selected, you must again bring the ‘OPC UA
Configurator’ to the foreground.
You have the following options for access:

n ‘No’ : Deny access - the OPC UA Configurator is not started.
n ‘Yes’ : Access is permitted once and the OPC UA Configurator is started.
n ‘Yes to all’ : Access is permitted and the OPC UA Configurator is started. At the
next call, the access request is no longer shown.
Allow access with ‘Yes’ respectively ‘Yes to all’ .
ð
NOTICE!
Data exchange between platforms of different vendors
If you allow access, you permit the exchange of data between
OPC UA Configurator and your project data of the Siemens TIA
Portal.
– Ensure that the necessary security guidelines are complied
with.
For the OPC UA configuration, the data is taken from the Siemens TIA Portal
project and listed in the table for the OPC UA configuration.
Please note that only the objects of the LD, FBD and IL lan-
guages can be transferred to the OPC UA Configurator.
7. Configure the OPC UA server and the data for the OPC UA communication.
190 HB400 | CPU | M13-CCF0000 | en | 20-02

Usage OPC UA Configurator > OPC UA Configurator
8. In the OPC UA Configurator switch to the online dialog and transfer the OPC UA
configuration. For communication the IP address data are taken from the TIA Portal
project.
ð The OPC UA configuration is now complete. For check you will find information
about your OPC UA configuration on the device web page at ‘OPC UA’ .
Ä Chap. 4.11.1.1.1 ‘Tab: ‘OPC UA’ ’ page 96
You can use the CMD auto commands OPCUA_PGOP_ENABLE and

OPCUA_PGOP_DISABLE to enable or disable OPC UA. After a power
cycle or loading a hardware configuration, the settings are retained. With
reset to the factory settings or over all reset, the OPC UA project is set to
the default value "enabled". Ä Chap. 4.18 ‘CMD - auto commands’
page 113
6.7 Usage OPC UA Configurator

6.7.1 OPC UA Configurator
The user interface of the OPC UA Configurator is divided into the following areas:
1 Menu bar
2 Toolbar
3 Project tree
4 Workspace
5 Output area
Menu bar In the menu bar you will find a few general commands on the OPC UA Configurator. Fur-
ther commands can be called up via context menus with the right mouse button, e.g.
functions for an object in the project tree.
Toolbar
Store OPC UA configuration
Compile OPC UA configuration
HB400 | CPU | M13-CCF0000 | en | 20-02 191

Usage OPC UA Configurator > Project tree
Transfer OPC UA configuration into the control
Project tree The Project tree gives you access to the ‘Device properties’ and to the following areas of
the ‘OPC UA configuration’ :
n Server settings
n Data access
n User management
Workspace In the Work space, you can edit the settings in the following areas of the OPC UA config-
uration:
n Device properties - General
– Information about the CPU such as device name, name and firmware version.
n Device properties - Communication
– Configuration of the interface for data exchange.
– The IP address data are automatically imported from the project when the OPC
UA Configurator is called and can be viewed here.
n Device properties - Server configuration
– Administration and interface assignment of the OPC UA server in the Project tree
n Server settings - Connection
– Legitimation of the user for access to the OPC UA server.
– Port for communication.
– Security policy for encryption and corresponding exceptions.
n Server settings - Certificate
– Create, view, import or export X.509 ITU-T standard certificate.
– Re-creating or importing replaces an existing certificate.
n Data access
– Selection of the variables that can be accessed via OPC UA.
– Filter option to limit the selection.
n User management
– Creation of a user list with password and role assignment.
Output area The output area shows information about activities performed and background opera-
tions.
6.7.2 Project tree

You can edit the OPC UA configuration via the project tree. The project tree contains the
OPC UA configurations, which you have created. You can create a maximum of two
OPC UA configurations: One configuration for the CPU and one configuration for the CP
(if exists).
Show project tree If the project tree is not shown select ‘View è Project tree’ or press [Strg]+[Shift]+[P].
Show/hide objects The objects in the project tree are arranged in a tree structure. You can show or hide
objects:
Hide all objects (‘Project è Collapse project tree’)
Show all objects (‘Project è Expand project tree’)
Hide slave objects / close folder
192 HB400 | CPU | M13-CCF0000 | en | 20-02

Usage OPC UA Configurator > Device properties
Show slave objects / open folder
Edit configurations and

OPC UA configuration
Device properties
Device properties n Edit device name and comment Ä Chap. 6.7.3.2 ‘General device
properties’ page 193
n Perform communication settings Ä Chap. 6.7.3.3 ‘Communication
settings’ page 194
n Create OPC UA configuration Ä Chap. 6.7.3.4 ‘Server configuration’
page 195
OPC UA
Server settings Ä Chap. 6.7.4 ‘Server settings - Connection ’ page 195
Ä Chap. 6.7.5 ‘Server settings - Certificate ’ page 197
Data access Ä Chap. 6.7.6 ‘Data access ’ page 198
User management Ä Chap. 6.7.7 ‘User management ’ page 199
Ä Chap. 6.7.8 ‘Role management ’ page 200
6.7.3 Device properties

6.7.3.1 Overview
Here you can edit the device name and the comment, perform the communication set-
tings as well as create the OPC UA configuration.
Click in the project tree at ‘Device properties’ .
ð The ‘Device properties’ editor opens.
The ‘Device properties’ editor is divided into several sections:

n Ä Chap. 6.7.3.2 ‘General device properties’ page 193
n Ä Chap. 6.7.3.3 ‘Communication settings’ page 194
n Ä Chap. 6.7.3.4 ‘Server configuration’ page 195
6.7.3.2 General device properties

To show or change the device properties, proceed as follows:
1. Click in the project tree at ‘Device properties’ .
ð The editor of the ‘Device properties’ opens.
2. Select the area ‘General’ .
‘Device type’ - Name of the CPU

‘Firmware’ - Firmware version of the CPU
‘Name’ - Device name: This name is shown in the project tree.
‘Author’ - Name of the responsible person who created the device
‘Comment’ - Any comment, e.g. an annotation or explanation
HB400 | CPU | M13-CCF0000 | en | 20-02 193

Usage OPC UA Configurator > Device properties
Click on the input field and enter any comment, e.g. an annotation or explanation.
With the [Enter] key, you can add a new line to the input field.
6.7.3.3 Communication settings

The communication settings are used to configure the interface for the data exchange
between programming device and destination station. Since the IP address parameters
for the OPC UA configuration are imported from the project, you simply have to set the
interface via which you are connected to the destination station.

2. Select the area ‘Communication settings’ .
Setting the Ethernet inter- 1. ‘Active PC interface’ : Select ‘Ethernet interface’ .

face
2. ‘PC interface’ : Select the network adapter for the communication connection from
the list.
ð If an IP address is already configured in the network adapter, it is shown under
the input field ‘IP address’ . If necessary, select a different IP address.
3. ‘CPU interface’ : Select the interface of the control from the list.
ð Since the IP address is imported from the project, it is shown below the input
field.
4. To configure further settings of the interface, click on ‘Interface configuration’ .
ð The ‘Interface properties’ dialog window will open.
194 HB400 | CPU | M13-CCF0000 | en | 20-02

Usage OPC UA Configurator > Server settings - Connection
5. In order to check whether a connection between the programming device and the
control can be established with the selected communication settings, click on ‘Verify
connection’ .
ð You can see in the status line, whether the connection could be established suc-
cessfully.
6. In order to check whether your programming device is connected with the correct
control, you can retrieve information from the connected control. For this click on
‘Accessible partners’ .
ð The ‘Search for accessible partners’ dialog window will open.
6.7.3.4 Server configuration
Here you can create the OPC UA configurations.

2. Select the area ‘Server configuration’ .
You can create a maximum of two OPC UA configurations: One configuration for the CPU
and one configuration for the CP (if exists).
Create configuration
1. Select in the selection field ‘OPC UA Configuration’ and click on ‘Add Server’ .
ð A new OPC UA configuration is created and listed in the project tree.
2. Click in the selection field ‘Active server CP’ or ‘Active server CP’ and choose
which configuration is to be assigned. With the selection ‘None’ the configuration
remains saved in the project. However, it is not transferred to the device.
To swap the two configurations for CP and CPU, click on the button .
You can create a maximum of two OPC UA configurations.
Remove server Right-click on the OPC UA configuration (PLC) in the project tree and select
‘Remove OPC UA server’.
6.7.4 Server settings - Connection

Here you can perform the connection settings of the OPC UA server.
1. Under Project tree at ‘OPC UA configuration’ click on ‘Server settings’ .
ð The ‘Server settings editor’ editor opens.
2. Select the area ‘Connection’ .
HB400 | CPU | M13-CCF0000 | en | 20-02 195

Usage OPC UA Configurator > Server settings - Connection
General You can set for the OPC UA server how a user of an OPC UA client must prove their
identity for access to the server. Select at least one of the following login methods. You
can also combine the two login methods with each other.
n ‘Activate anonymous login’
– The OPC UA server does not check the authorisation of the OPC UA client.
n ‘Activate user/password login’
– The OPC UA server checks using the user name and password whether the
access of the OPC UA client is authorised. To do this, the server evaluates the
role assigned to the user. Ä Chap. 6.7.8 ‘Role management ’ page 200
n ‘Allow obsolete security guideline’
– Allows the selection of the two obsolete security guidelines ‘Basic128Rsa15’ and
‘Basic256’ (not recommended)
n ‘Application name’
– Clear identification of the application in the OPC name space.
Network n ‘End point port’

– TCP port for binary data exchange (standard: 4840).
Security
Activate only security guidelines that are compatible with the protection
concept for your machine or system. Deactivate all other security guide-
lines.
n ‘None’
– Insecure data traffic between server and client.
n ‘Basic128Rsa15’
– Secured data traffic, 128-bit encoding with key wrap algorithm RSA-15, (allow
option with ‘Allow obsolete security guideline’ see above).
n ‘Basic256’
– Secured data traffic, 256-bit encoding (allow option with ‘Allow obsolete security
guideline’ see above).
n ‘Basic256Sha256’
– Secured data traffic, 256-bit encoding with hash algorithm SHA-256 (recom-
mended).
Encoding:
n ‘Sign’
– Endpoint secures the integrity of the data through signing.
n ‘SignAndEncrypt’
– Endpoint secures the integrity and confidentiality of the data through signing and
encoding.
n ‘Both’
– The OPC UA server offers both encryption methods ‘Sign’ and
‘SignAndEncrypt’ . The OPC UA client can use one of the two encoding methods.
Security Check Overrides Here you can allow various exceptions in the security check, in order to increase the error
tolerance.
196 HB400 | CPU | M13-CCF0000 | en | 20-02

Usage OPC UA Configurator > Server settings - Certificate
6.7.5 Server settings - Certificate

A secure connection between the OPC UA client and the server can only be established
if the server classifies and accepts the client's digital certificate as trusted. Currently, the
server accepts every valid client certificate. The server accepts self-signed certificates. In
addition, the client also checks the server's certificate.
Here you can create, show, import or export an ITU-T standardized X.509 certificate for
the OPC UA server. The certificate shown here is transferred into the OPC UA server.
1. Under Project tree at ‘OPC UA configuration’ click on ‘Server settings’ .

ð The ‘Server settings’ editor opens.
2. Select the area ‘Certificate’ .
The current X.509 certificate is shown in the work space. If you create or import a new
certificate, the previously shown certificate is replaced.
Toolbar
Create new certificate: Opens the dialog window ‘Create new certificate’
Display certificate: Shows information on the current certificate
Export certificate: Opens the dialog window ‘Save certificate’
Import certificate: Opens the dialog window ‘Open certificate’
Create new certificate 1. Click on to create a new certificate.

ð The dialog window ‘Create new certificate’ opens.
2. Enter the data for the certificate and click on ‘OK’ .
ð The previously shown certificate is replaced by the new certificate.
Display certificate Click on to show information about the current certificate.

ð The dialog window ‘Certificate’ opens.
Export certificate You can export the current certificate e.g. to use it on different computers.
1. Click on .
ð The dialog window ‘Save certificate’ opens.
2. Select a directory and enter a file name.
3. Click on ‘Save’ .
ð The current certificate is saved in the export file (pfx file format).
Import certificate You can import a certificate, e.g. to use it for the current OPC UA configuration. For a
successful import, the certificate must have the following characteristics:
n The certificate must be available as a PFX file.
n The ‘Common name’ and ‘Organization’ fields must be completed.
HB400 | CPU | M13-CCF0000 | en | 20-02 197

Usage OPC UA Configurator > Data access
n The maximum key strength must not exceed 2048bit.

n The certificate must contain a valid Private key.
1. Click at .
ð The dialog window ‘Open certificate’ opens.
2. Select the desired certificate (pfx file format).
3. Click on ‘Open’ .
ð The previously shown certificate is replaced by the imported certificate.
6.7.6 Data access

Here you can select the variables belonging to the CPU or CP (if exists) that can be
accessed via OPC UA.
Under Project tree at ‘OPC UA configuration’ click on ‘Data access’ .
ð The editor for ‘Data access’ opens.
Toolbar
Refresh variables: Apply changed filter settings to the result table.
Filter settings Here you can select the operands and address ranges that will be shown in the results
table.
1. Activate ‘All operand areas’ or individual operand ranges to be shown in the
result table.
2. To limit the addresses of an operand range, enter the start and end byte addresses
in the two adjacent fields, e.g. 0 to 1000.
3. Click on or activate ‘Apply filter changes immediately’ .
ð The result table is updated with the filter settings.
Result In the results table, select the variables that are to be used in the OPC UA configuration.
OPC UA clients may access these variables.
Activate ‘OPC UA’ of the desired variables.
Group operands For a better overview, you can sort the table entries by groups.
(1) Select column (hold left mouse button down)

(2) Drag the column
(3) Drop column in the field (release mouse button)
1. Drag the desired column header into the field above the table.
ð The contents of the column will be grouped. The number of lines is shown for
each group.
198 HB400 | CPU | M13-CCF0000 | en | 20-02

Usage OPC UA Configurator > User management
2. Click on to open the group. Click on to close the group.
You can repeat steps 1 to 2 in order to structure the group into further sub-groups.
In order to cancel a grouping, click on the close icon next to the group name.
6.7.7 User management

The user management allows you to create a user list. For each user, you can define a
password and a role.
1. Under Project tree at ‘OPC UA configuration’ click on ‘User management’ .
ð The editor for ‘User management’ opens.
2. Select the area ‘User management’ .
Toolbar
Add new user: Input mode for new user
Remove user: Deletes the selected user
Edit current user: Input mode for selected user
Save input: Save input Save user settings
Cancel input: Cancel user settings without saving
Adding a user 1. Click on .

2. Enter the desired user name in the input field ‘Name’ .
3. Enter the password in the input field ‘Password’ and repeat the input under ‘Re-
enter password’ .
4. Select a role for the user. With this role, the access rights to the OPC UA server are
established.
5. Click on .
ð The user will be entered in the user list.
Edit user 1. In the user list, select the user whose data you want to change.
2. Click on .
3. Enter the desired changes and click on .
Removing a user 1. In the user list, select the user you want to delete.
2. Click on .
ð A dialog box opens where you can choose whether the user should be deleted
or not.
HB400 | CPU | M13-CCF0000 | en | 20-02 199

Usage OPC UA Configurator > Output
6.7.8 Role management

Here you establish the roles and access rights that you can assign to the users. When
you activate the authentication via User/password login Ä Chap. 6.7.4 ‘Server settings -
Connection ’ page 195, the access rights to the OPC UA server are issued using the
logged-in user and the assigned role.
Example: Role: Operator

Username: "I myself"
Server settings: User/password login activated
The user "Me Self" receives write permission and reading rights to the OPC UA server
when he has successfully logged in with the password.
1. Under Project tree at ‘OPC UA configuration’ click on ‘User management’ .

ð The editor for ‘User management’ opens.
2. Select the area ‘Role management’ .
Configure roles The following two roles are currently available for selection; further roles can not be
added at the moment.
n Operator: Write permission and reading rights
n Observer: Reading rights only
6.7.9 Output
Information on executed activities and background operations are displayed in the
"Output" window.
(1) Delete all messages in the output window
200 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO Deployment WebVisu - Web visualization
WebVisu editor
7 Deployment WebVisu - Web visualization

Please note that the simultaneous use of OPC UA and WebVisu on the
same interface is not supported! When attempting to activate them, both
servers are stopped and the diagnostic message 0xE989 or 0xE9AB is
output.
n With a WebVisu project there is the possibility to configure a web visualization on your
CPU.
n The configuration of a WebVisu project is only possible with the SPEED7 Studio
V1.7.0 and up.
n Since a WebVisu project is only executable by memory card, a VIPA memory card
(VSD, VSC) of YASKAWA must be plugged. Please regard that you always use a
VSC card that fits to your CPU. Ä Chap. 4.16 ‘Deployment storage media - VSD,
VSC’ page 110
n If the memory card is removed for a short time, the SF LED lights up. This indicates
that a feature is missing and the WebVisu will quit after 72 hours.
n The WebVisu functionality must be activated in the CPU. Ä Chap. 7.2 ‘Activate Web-
Visu functionality’ page 204
n When the project is transferred from the SPEED7 Studio, the WebVisu project is auto-
matically transferred as TAR file to the inserted memory card.
n Access to the WebVisu project of the CPU happens by the IP address of the Ethernet
PG/OP channel and the correspondingly configured port or via the device web page
of the CPU.
n You can access your web visualization via a web browser. Web browsers based on
Windows CE are currently not supported.
Please note that the use of a WebVisu project, depending on the scope of
the WebVisu project and the PLC project, can influence the performance
and thus the response time of your application.
7.1 WebVisu editor

The configuration of a WebVisu project is shown below. This is only the basic use of the
WebVisu editor in the SPEED7 Studio together with the VIPA CPU. Please note that soft-
ware changes can not always be considered and it may thus be deviations to the descrip-
tion.
For more information on the SPEED7 Studio and how to use the Web-
Visu editor, refer to its online help.
HB400 | CPU | M13-CCF0000 | en | 20-02 201

Deployment WebVisu - Web visualization VIPA System MICRO
WebVisu editor > Creating a WebVisu project
7.1.1 Working environment
(1) Toolbar
(2) Editor surface
(3) Status bar
(4) Catalog
(5) Properties window
(1) Toolbar The toolbar provides important commands for working with the WebVisu editor.
(2) Editor area The editor area is your workspace. Here you can place and edit texts and graphics
objects.
(3) Status bar With a slider you can enlarge or reduce your view.
(4) Catalog Via Catalog you can access all the WebVisu elements. You can use Drag & Drop to place
them on the Editor surface and adjust them using properties.
(5) Properties window By enabling ‘View è Properties’ the ‘Properties’ are shown. The properties of the
selected element are shown here. You can adjust these if necessary.
7.1.2 Creating a WebVisu project

Add WebVisu 1. Start the SPEED7 Studio with your project for the CPU for which a WebVisu project
is to be created.
2. If not already done, add a CPU by clicking ‘Add new device’ .
3. Click in the ‘Project tree’ at the CPU and select ‘Context menu
è Device properties’.
ð The ‘Device properties’ of your CPU opens.
202 HB400 | CPU | M13-CCF0000 | en | 20-02

WebVisu editor > Creating a WebVisu project
4. Here click at ‘WebVisu configuration’

ð In this settings window, you can create a WebVisu project for your CPU.
5. To create a WebVisu project, click at [ Add WebVisu ].

ð A new WebVisu project is created and listed in the ‘Project tree’ . At ‘WebVisu -
general configurations’ and ‘WebVisu - SSL configurations’ , you can make fur-
ther settings.
WebVisu - general configurations

n Port number
– Enter the port number under which the WebVisu should be accessible.
– Port number: 8080 (default): The WebVisu can be accessed via the IP address
and port 8080. The Device web page can be accessed via the IP address and
port 80.
– Port number: 80: The WebVisu can be accessed via the IP address and port 80.
The Device web page can be accessed via the IP address and port 8080.
n Polling interval (ms)
– Enter here the interval for the cyclical refresh of the web content.
n Execution device
– Select ‘CPU’ as device on which this WebVisu project is to be executed.
– WebVisu projects for Ethernet CPs are not supported by this CPU.
WebVisu - SSL configurations
n Enabling encoding
– When enabled, you have SSL-encrypted access to your WebVisu.
n Disable HTTP
– When activated, the access happens via HTTPS.
n SSL port number
– SSL port number 443 (default): The secure access to the WebVisu takes place
via the IP address and port 443. The Device web page can be accessed via the
IP address of the CPU and port 8080.
n Original path of the certificate used
– Here you can upload a security certificate.
– Only security certificates in PEM format are supported.
– The file must contain the certificate and the private key.
Delete WebVisu Click in the ‘Project tree’ at WebVisu Project and select ‘Context menu
è Delete WebVisu’.
ð The WebVisu project is removed from the configuration.
HB400 | CPU | M13-CCF0000 | en | 20-02 203

Deployment WebVisu - Web visualization VIPA System MICRO
Start-up of the WebVisu project
Edit WebVisu
In the ‘Project tree’ , navigate to ‘WebVisu Project > Images’ and click at ‘Main’ .
Select ‘Context menu è Open image’
ð The WebVisu editor opens. Here, you can configure your web visualization by
dragging and dropping elements from the ‘Catalog’ onto the editor area and
using the ‘Properties’ to interconnect them with a variable.
7.2 Activate WebVisu functionality

Proceeding For your CPU can process a WebVisu project, you have to activate the WebVisu function-
ality.
1. Insert a VIPA memory card (VSD, VSC) into your CPU. Please note that you must
always use a VSC card suitable for your CPU. Ä Chap. 4.16 ‘Deployment storage
2. Turn on the CPU, to activate the WebVisu functionality, you have to establish an
Overall reset.
ð As long as the memory card is inserted, the WebVisu functionality remains acti-
vated even after a power cycle. When the project is transferred from the
SPEED7 Studio, the WebVisu project is automatically transferred to the inserted
memory card.
Please regard that the memory card must remain plugged when
you’ve executed activated the WebVisu functionality. Otherwise
the SF LED is on and the WebVisu functionality is deactivated
after 72 hours. As long as an activated memory card is not
inserted, the SF LED is on and the "TrialTime" timer counts
from 72 hours down to 0. After that the WebVisu functionality is
de-activated. By inserting the memory card, the LED goes off
and the CPU runs again without restrictions.
7.3 Start-up of the WebVisu project

The following preconditions must be fulfilled for the WebVisu project to start-up:
1. Activate WebVisu functionality if not already done. Ä Chap. 7.2 ‘Activate WebVisu
functionality’ page 204
2. Configure your CPU and perform a hardware configuration.
3. Configure your WebVisu project.
4. Safe and translate your project.
5. If you are online connected to your CPU, you can transfer your project to the CPU
with ‘AG è Transfer all’.
ð Here the configuration is transferred in the CPU and the WebVisu project is
transferred to the memory card. Immediately after the transfer you have access
to your WebVisu.
204 HB400 | CPU | M13-CCF0000 | en | 20-02

Access to the WebVisu > Status of the WebVisu
You can use the CMD auto commands WEBVISU_PGOP_ENABLE and

WEBVISU_PGOP_DISABLE to enable or disable the WebVisu. After a
power cycle or loading a hardware configuration, the settings are
retained. With reset to the factory settings or over all reset, the WebVisu
project is set to the default value "enabled". Ä Chap. 4.18 ‘CMD - auto
commands’ page 113
7.4 Access to the WebVisu

n When connected via Ethernet PG/OP channel, you have access to the WebVisu and
Device web page of the CPU, controlled via ports.
n Access to the WebVisu can be password-protected and encrypted by means of SSL
certificates. If you want to use SSL certificates, you must integrate them in the
SPEED7 Studio accordingly.
n You can create users in the SPEED7 Studio via ‘WebVisu project > User
administration’ , who can access the WebVisu.
n Via ‘Device properties > WebVisu configuration’ you can specify the port, the Web-
Visu can be accessed and upload SSL certificates. This changes the port for
accessing the device web page.
– Port number: 8080 (default): The WebVisu can be accessed via the IP address
and port 8080. The Device web page can be accessed via the IP address and
port 80.
– Port number: 80: The WebVisu can be accessed via the IP address and port 80.
The Device web page can be accessed via the IP address and port 8080.
– SSL port number 443 (default): The secure access to the WebVisu takes place
via the IP address and port 443. The Device web page can be accessed via the
IP address and port 8080.
– Please note that once you have made adjustments to the user man-
agement, you will need to restart your web browser. Otherwise you
receive system-related error messages about invalid user informa-
tion!
– Please note that the encryption of the communication can affect CPU
performance and therefore the response time of the entire system!
7.4.1 Status of the WebVisu

On the device web page at the tab ‘WebVisu’ via ‘Status’ you get the status of your
WebVisu project. Ä Chap. 4.11.1.1.2 ‘Tab: ‘WebVisu’ ’ page 97
HB400 | CPU | M13-CCF0000 | en | 20-02 205

Deployment PG/OP communication - productive VIPA System MICRO
Basics - Industrial Ethernet in automation
8 Deployment PG/OP communication - productive

8.1 Basics - Industrial Ethernet in automation
Overview The flow of information in a company presents a vast spectrum of requirements that must
be met by the communication systems. Depending on the area of business the bus
system or LAN must support a different number of users, different volumes of data must
be transferred and the intervals between transfers may vary, etc. It is for this reason that
different bus systems are employed depending on the respective task. These may be
subdivided into different classes. The following model depicts the relationship between
the different bus systems and the hierarchical structures of a company:
Industrial Ethernet Industrial Ethernet is an electrical net based on shielded twisted pair cabling or optical net
based on optical fibre. 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:
n Every station "listens” on the bus cable and receives communication messages that
are addressed to it.
n Stations will only initiate a transmission when the line is unoccupied.
n 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.
n Using switches there is the possibility for communication without collisions.
206 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO Deployment PG/OP communication - productive
Basics - ISO/OSI reference model
8.2 Basics - ISO/OSI reference model

Overview The ISO/OSI reference model is based on a proposal that was developed by the Interna-
tional Standards Organization (ISO). This represents the first step towards an interna-
tional 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 sys-
tems 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:
n Layer 7 - Application Layer
n Layer 6 - Presentation Layer
n Layer 5 - Session Layer
n Layer 4 - Transport Layer
n Layer 3 - Network Layer
n Layer 2 - Data Link Layer
n Layer 1- Physical Layer
Depending on the complexity and the requirements of the communication mechanisms a
communication system may use a subset of these layers.
Layer 1 - Bit communica- The bit communication layer (physical layer) is concerned with the transfer of data bits via
tion layer (physical layer) the communication channel. This layer is therefore responsible for the mechanical, elec-
trical and the procedural interfaces and the physical communication medium located
below the bit communication layer:
n Which voltage represents a logical 0 or a 1?
n The minimum time the voltage is present to be recognized as a bit.
n The pin assignment of the respective interface.
Layer 2 - Security layer This layer performs error-checking functions for bit strings transferred between two com-
(data link layer) municating partners. This includes the recognition and correction or flagging of communi-
cation errors and flow control functions. The security layer (data link layer) converts raw
communication data into a sequence of frames. This is where frame limits are inserted on
the transmitting side and where the receiving side detects them. These limits consist of
special bit patterns that are inserted at the beginning and at the end of every frame. The
security layer often also incorporates flow control and error detection functions. The data
security layer is divided into two sub-levels, the LLC and the MAC level. The MAC (Media
Access Control) is the lower level and controls how senders are sharing a single transmit
channel. The LLC (Logical Link Control) is the upper level that establishes the connection
for transferring the data frames from one device into the other.
Layer 3 - Network layer The network layer is an agency layer. Business of this layer is to control the exchange of
binary data between stations that are not directly connected. It is responsible for the log-
ical connections of layer 2 communications. Layer 3 supports the identification of the
single network addresses and the establishing and disconnecting of logical communica-
tion channels. Additionally, layer 3 manages the prior transfer of data and the error pro-
cessing of data packets. IP (Internet Protocol) is based on Layer 3.
Layer 4 - Transport layer Layer 4 connects the network structures with the structures of the higher levels by
dividing the messages of higher layers into segments and passes them on to the network
layer. Hereby, the transport layer converts the transport addresses into network
addresses. Common transport protocols are: TCP, SPX, NWLink and NetBEUI.
HB400 | CPU | M13-CCF0000 | en | 20-02 207

Basics - ISO/OSI reference model
Layer 5 - Session layer The session layer is also called the communication control layer. It relieves the communi-
cation between service deliverer and the requestor by establishing and holding the con-
nection if the transport system has a short time fail out. At this layer, logical users may
communicate via several connections at the same time. If the transport system fails, a
new connection is established if needed. Additionally this layer provides methods for con-
trol and synchronization tasks.
Layer 6 - Presentation This layer manages the presentation of the messages, when different network systems
layer are using different representations of data. Layer 6 converts the data into a format that is
acceptable for both communication partners. Here compression/decompression and
encrypting/decrypting tasks are processed. This layer is also called interpreter. A typical
use of this layer is the terminal emulation.
Layer 7 - Application layer The application layer is the link between the user application and the network. The tasks
of the application layer include the network services like file, print, message, data base
and application services as well as the according rules. This layer is composed from a
series of protocols that are permanently expanded following the increasing needs of the
user.
208 HB400 | CPU | M13-CCF0000 | en | 20-02

Basics - Terms
8.3 Basics - Terms

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 con-
nected by means of a network cable. The combination of network stations and the net-
work 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 (Cheap-
ernet) was used as communication medium. This has been superseded by the twisted-
pair network cable due to its immunity to interference. The CPU has a twisted-pair con-
nector. 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 interfer-
ence. 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 net-
work 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 net-
work. 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 inter-
face 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 analyses 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.
HB400 | CPU | M13-CCF0000 | en | 20-02 209

Basics - Protocols
8.4 Basics - Protocols

Overview Protocols define a set of instructions or standards that enable computer to establish com-
munication connections and exchange information as error free as possible. A commonly
established protocol for the standardization of the complete computer communication is
the so called ISO/OSI layer model, a model based upon seven layers with rules for the
usage of hardware and software Ä Chap. 8.2 ‘Basics - ISO/OSI reference model’
page 207
The following protocols are used:
n Siemens S7 connections
n Open communication
– TCP native according to RFC 793
– ISO on TCP according to RFC 1006
– UDP according to RFC 768
Siemens S7 connections With the Siemens S7 connection large data sets may be transferred between PLC sys-
tems based on Siemens STEP®7. Here the stations are connected via Ethernet. Precon-
dition for the Siemens S7 communication is a configured connection table, which contains
the defined connections for communication. Here NetPro from Siemens may be used.
Properties:
n A communication connection is specified by a connection ID for each connection
partner.
n The acknowledgement of the data transfer is established from the partner station at
level 7 of the ISO/OSI reference model.
n At the PLC side FB/SFB VIPA handling blocks are necessary for data transfer for the
Siemens S7 connections.
More information about the usage of these blocks may be found in the
210 HB400 | CPU | M13-CCF0000 | en | 20-02

Basics - IP address and subnet
Open communication In the ‘open communication’ the communication takes place via the user program by
means of handling blocks. These blocks are also part of the Siemens SIMATIC Manager.
You will find these in the ‘Standard Library’ at ‘Communication Blocks’ .
n Connection-oriented protocols:
Connection-oriented protocols establish a (logical) connection to the communication
partner before data transmission is started. And if necessary they terminate the con-
nection after the data transfer was finished. Connection-oriented protocols are used
for data transmission when reliable, guaranteed delivery is of particular importance. In
general, many logical connections can exist on one physical line. The following con-
nection-oriented protocols are supported with FBs for open communication via Indus-
trial Ethernet:
– TCP native accord. to RFC 793:
During data transmission, no information about the length or about the start and
end of a message is transmitted. However, the receiver has no means of
detecting where one message ends in the data stream and the next one begins.
The transfer is stream-oriented. For this reason, it is recommended that the data
length of the FBs is identical for the sending and receiving station. If the number
of received data does not fit to the preset length you either will get not the whole
data, or you will get data of the following job.
– ISO on TCP accord. to RFC 1006:
During data transmission, information on the length and the end of the message
is also transmitted. If you have specified the length of the data to be received
greater than the length of the data to be sent, the receive block will copy the
received data completely into the receive range.
n Connection-less protocol:
There is thus no establishment and termination of a connection with a remote partner.
Connection-less protocols transmit data with no acknowledge and with no reliable
guaranteed delivery to the remote partner.
– UDP accord. to RFC 768:
In this case, when calling the sending block you have to specify the address
parameters of the receiver (IP address and port number). During data transmis-
sion, information on the length and the end of the message is also transmitted. In
order to be able to use the sending and receiving blocks first you have to con-
figure the local communications access point at both sides. With each new call of
the sending block, you re-reference the remote partner by specifying its IP
address and its port number.
8.5 Basics - IP address and subnet

IP address structure Exclusively IPv4 is supported. At IPv4 the IP address is a 32bit address that must be
unique within the network and consists of 4 numbers that are separated by a dot. Every
IP address is a combination of a Net-ID and a Host-ID and has the following
Structure: xxx.xxx.xxx.xxx
Range: 000.000.000.000 to 255.255.255.255
Net-ID, Host-ID The Network-ID identifies a network res. a network controller that administrates the net-
work. The Host-ID marks the network connections of a participant (host) to this network.
Subnet mask The Host-ID can be further divided into a Subnet-ID and a new Host-ID by using a 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.
HB400 | CPU | M13-CCF0000 | en | 20-02 211

Basics - IP address and subnet
Subnet mask binary all "1" binary all "0"

IPv4 address Net-ID Host-ID
Subnet mask and IPv4 address Net-ID Subnet-ID new Host-ID
Address at first start-up At the first start-up of the CPU, the Ethernet PG/OP channel does not have an IP
address.
Information about the assignment of IP address data to the Ethernet PG/OP channel may
be found in Ä Chap. 4.7 ‘Hardware configuration - Ethernet PG/OP channel’ page 72.
Address classes For IPv4 addresses there are five address formats (class A to class E) that are all of a
length of 4byte = 32bit.
Class A 0 Network-ID (1+7bit) Host-ID (24bit)

Class B 10 Network-ID (2+14bit) Host-ID (16bit)
Class C 110 Network-ID (3+21bit) Host-ID (8bit)
Class D 1110 Multicast group
Class E 11110 Reserved
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.
Private IP networks These addresses can be used as net-ID by several organizations without causing con-
flicts, for these IP addresses are neither assigned in the Internet nor are routed in the
Internet. To build up private IP-Networks within the Internet, RFC1597/1918 reserves the
following address areas:
Network class from IP to IP Standard subnet

mask
A 10.0.0.0 10.255.255.255 255.0.0.0
B 172.16.0.0 172.31.255.255 255.255.0.0
C 192.168.0.0 192.168.255.255 255.255.255.0
(The Host-ID is underlined.)
Reserved Host-IDs Some Host-IDs are reserved for special purposes.
Host-ID = "0" Identifier of this network, reserved!

Host-ID = maximum (binary complete "1") Broadcast address of this network
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.)
212 HB400 | CPU | M13-CCF0000 | en | 20-02

Hardware configuration
8.6 Fast introduction

Overview At the first commissioning respectively after an overall reset with PowerON again of the
CPU, the Ethernet PG/OP channel has no IP address. This can only be reached by its
MAC address. By means of the MAC address, which is printed at the front as ‘MAC PG/
OP:...’ , you can assign IP address data. The assignment takes place directly via the
hardware configuration of the Siemens SIMATIC Manager.
Steps of configuration For the configuration of the Ethernet PG/OP channel for productive connections please
follow the following approach:
n Hardware configuration - CPU
n Hardware configuration - Ethernet PG/OP channel
n Configure connections
– Siemens S7 connections
(Configuration via Siemens NetPro, communication via VIPA handling blocks)
– Open communication
(Configuration and communication happens by standard handling blocks)
n Transfer of the complete project to CPU
8.7 Hardware configuration

Overview At the first commissioning respectively after an overall reset with PowerON again of the
CPU, the Ethernet PG/OP channel has no IP address. This can only be reached by its
MAC address. By means of the MAC address, which is printed at the front as ‘MAC PG/
OP:...’ , you can assign IP address data. The assignment takes place directly via the
hardware configuration of the Siemens SIMATIC Manager.
n CPU
Ä Chap. 4.5 ‘Hardware configuration - CPU’ page 69
n Ethernet PG/OP channel
HB400 | CPU | M13-CCF0000 | en | 20-02 213

Configure Siemens S7 connections
8.8 Configure Siemens S7 connections

Overview 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 communication between two
participants at the Industrial Ethernet. The communication partners may here be part of
the same project or - at multi projects - separated within related part projects. Communi-
cation 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 Sta-
tion". The communication is controlled by the user program with VIPA handling blocks. To
use this blocks, configured communication connections are always necessary in the
active station.
Ä ‘Link-up stations’ page 215
Ä ‘Projecting connections’ page 216
Ä ‘Siemens S7 connection - Communication functions’ page 218
Properties communication The following properties are characterizing a communication connection:

connection
n One station always executes an active connection establishment.
n Bi-directional data transfer (Send and receive on one connection)
n Both participant have equal rights, i.e. every participant may initialize the send res.
receive process event controlled.
n Except of the UDP connection, at a communication connection the address of the
communication partner is set via the project engineering. Here the connection is
active established by one station.
Requirements n Siemens SIMATIC Manager V 5.5 SP2 or higher and SIMATIC NET are installed.
n With the hardware configuration the according CP was assigned with IP address data
by its properties.
Every station outside of the recent project must be configured as replace-

ment 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 param-
eter directly in the connection dialog.
214 HB400 | CPU | M13-CCF0000 | en | 20-02

Work environment of For the project engineering of connections, a thorough knowledge with NetPro from Sie-
NetPro mens 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. doc-
umentation. Start NetPro by clicking on a "net" in the Siemens SIMATIC Manager or on
"connections" within the CPU.
The environment of NetPro has the following structure:
1 Graphic net view: All stations and networks are displayed in a graphic view. By
clicking on the according component you may access and alter the concerning prop-
erties.
2 Net objects: This area displays all available net objects in a directory view. By drag-
ging a wanted object to the net view you may include further net objects and open
them in the hardware configurator.
3 Connection table: The connection table lists all connections in a table. This list is only
shown when you highlighted a connectable module like e.g. a CPU. You may insert
new connections into this table with the according command.
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 Station: This includes a PLC station with rack, CPU and communication components.
Via the context menu you may configure a station 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: 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. The PROFINET IO controller is to be configured by
the PN-IO component.
4 Ethernet PG/OP channel: The internal Ethernet PG/OP channel must always be con-
figured as external CP in the hardware configuration.
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 coloured 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.
HB400 | CPU | M13-CCF0000 | en | 20-02 215

Projecting connections
1. For the project engineering of connections, open the connection list by selecting the
according CPU. Choose Insert new connection in the context menu:
n Connection partner (partner station)
A dialog window opens where you may choose the connection partner and the
connection type.
n Specified connection partner
Each station configured in the Siemens SIMATIC Manager is listed in the table
of connection partner. These stations are unique specified by an IP address and
a subnet mask.
n Unspecified connection partner
Here the connection partner may exist in the current project or in an unknown
project. Connection jobs to an unknown project must be defined by an unique
connection name, which is to be used in the projects of both stations. Due to
this allocation the connection remains unspecified.
2. Choose the connection partner and the type of connection and confirm with [OK].
ð If activated, a properties dialog for the according connection opens as link to
your PLC user program.
3. After every connection was configured by this way, you may save and compile your
project and exit NetPro.
216 HB400 | CPU | M13-CCF0000 | en | 20-02

Connection types With this CPU exclusively Siemens S7 connection may be configured with Siemens
NetPro.
Siemens S7 connection n For data transfer with Siemens S7 connections the FB/SFB VIPA handling blocks are
necessary; the deployment is described in the manual "Operation list" of your CPU.
n At Siemens S7 connections the communication connections are specified by a con-
nection ID for each communication partner.
n A connection is specified by the local and partner connection end point.
n At Siemens S7 connections the TSAPs must be congruent crosswise. The following
parameters define a connection end point:
The following parameters define a connection end point:
Station A Station B
remote TSAP à Siemens à local TSAP
local TSAP ß S7 connection ß remote TSAP
ID A ID B
Combination options with deployment of the FB/SFB VIPA handling blocks
Connection partner Connection establishing Connection

specified in NetPro active/passive specified
(in the current project)
unspecified in NetPro active specified
(in the current project) passive unspecified
unspecified in NetPro active/passive specified (connection name in an other
project)
(in the unknown project)
HB400 | CPU | M13-CCF0000 | en | 20-02 217

In the following every relevant parameter of a Siemens S7 connection is described:

n Local connection end point:
Here you may define how the connection is to be established. Since the Siemens
SIMATIC Manager can identify the communication options by means of the end
points, some options are already preset and may not be changed.
– Establish an active connection:
An established connection is precondition for data transfer. By activating the
option Establish an active connection the local station establishes the connection.
Please regard not every station is able to establish a connection. Here the job is
to be made by the partner station.
– One-way:
If activated only one-way communication blocks like PUT and GET may be used
for communication in the user program. Here the partner station acts as server,
which neither may send active nor receive active
n Block parameters
– Local ID:
The ID is the link to your PLC program. The ID must be identical to the ID of the
call interface of the FB/SFB VIPA handling block.
– [Default]:
As soon as you click at [Default], the ID is reset to system generated ID.
n Connection path:
In this part of the dialog window the connection path between the local and the
partner station may be set. Depending on the linking of the modules the possible
interfaces for communication are listed in a selection field.
– [Address details]:
With this button a dialog window is opened, which shows address information
about the local and partner station. The parameters may also be changed.
– TSAP:
With Siemens S7 connections a TSAP is automatically generated of the connec-
tion resource (one-way/two-way) and state of place (rack/slot respectively system
internal ID at PC stations).
– Connection resource:
The connection resource is part of the TSAP of the local station respectively of
the partner. Not every connection resource may be used for every connection
type. Depending on the connection partner and the connection type the range of
values is limited respectively the connection resource is fix specified.
Siemens S7 connection - With the VIPA SPEED7 CPUs there are two possibilities for the deployment of the com-
Communication functions munication functions:
n Siemens S7-300 communication functions:
By integration of the VIPA function blocks FB 12 ... FB 15 you may access the Sie-
mens S7-300 communication functions.
n Siemens S7-400 communication functions:
For the Siemens S7-400 communication functions the SFB 12 ... SFB 15 are to be
used, which were integrated to the operating system of the CPU. Here copy the inter-
face description of the SFBs from the standard library at system function block to the
directory container, generate an instance data block for each call and call the SFB
with the associated instance data block.
218 HB400 | CPU | M13-CCF0000 | en | 20-02

Configure Open Communication
Function blocks
FB/SFB Label Description

FB/SFB 12 BSEND Sending data in blocks:
FB/SFB 12 BSEND sends data to a remote partner FB/SFB of the type BRCV
(FB/SFB 13). The data area to be transmitted is segmented. Each segment is sent
individually to the partner. The last segment is acknowledged by the partner as it is
received, independently of the calling up of the corresponding FB/SFB/FB BRCV.
With this type of data transfer, more data can be transported between the communi-
cations partners than is possible with all other communication FBs/SFBs for config-
ured S7 connections, namely 65534bytes.
FB/SFB 13 BRCV Receiving data in blocks:
The FB/SFB 13 BRCV can receive data from a remote partner FB/SFB of the type
BSEND (FB/SFB 12). The parameter R_ID of both FB/SFBs must be identical. After
each received data segment an acknowledgement is sent to the partner FB/SFB and
the LEN parameter is updated.
FB/SFB 14 GET Remote CPU read:
The FB/SFB 14 GET can be used to read data from a remote CPU. The respective
CPU must be in RUN mode or in STOP mode.
FB/SFB 15 PUT Remote CPU write:
The FB/SFB 15 PUT can be used to write data to a remote CPU. The respective
CPU may be in RUN mode or in STOP mode.
8.9 Configure Open Communication

You can use Open Communication to communicate with other users on the Ethernet via
your user program. For this the following protocols are available.
Connection-oriented pro- n Connection-oriented protocols establish a (logical) connection to the communication

tocols partner before data transmission is started.
n And if necessary they terminate the connection after the data transfer was finished.
n Connection-oriented protocols are used for data transmission when reliable, guaran-
teed delivery is of particular importance.
n In general, many logical connections can exist on one physical line.
HB400 | CPU | M13-CCF0000 | en | 20-02 219

The following connection-oriented protocols are supported with FBs for open communica-
tion via Industrial Ethernet:
n TCP/IP native according to RFC 793 (connection types 01h and 11h):
– During data transmission, no information about the length or about the start and
end of a message is transmitted.
– The receiver has no means of detecting where one message ends in the data
stream and the next one begins.
– The transfer is stream-oriented. For this reason, it is recommended that the data
length of the FBs is identical for the sending and receiving station.
– If the number of received data does not fit to the preset length you either will get
not the whole data, or you will get data of the following job. The receive block
copies as many bytes into the receive area as you have specified as length. After
this, it will set NDR to TRUE and write RCVD_LEN with the value of LEN. With
each additional call, you will thus receive another block of sent data.
n ISO on TCP according to RFC 1006:
– During data transmission, information on the length and the end of the message
is also transmitted.
– The transfer is block-oriented
– If you have specified the length of the data to be received greater than the length
of the data to be sent, the receive block will copy the received data completely
into the receive range. After this, it will set NDR to TRUE and write RCVD_LEN
with the length of the sent data.
– If you have specified the length of the data to be received less than the length of
the sent data, the receive block will not copy any data into the receive range but
instead will supply the following error information: ERROR = 1, STATUS = 8088h.
Connection-less protocol n There is thus no establishment and termination of a connection with a remote partner.
n Connection-less protocols transmit data with no acknowledge and with no reliable
guaranteed delivery to the remote partner.
The following connection-oriented protocol is supported with FBs for open communication
via Industrial Ethernet:
n UDP according to RFC 768 (with connection type 13h):
– In this case, when calling the sending block you have to specify the address
parameters of the receiver (IP address and port number).
– During data transmission, information on the length and the end of the message
is also transmitted.
– In order to be able to use the sending and receiving blocks first you have to con-
figure the local communications access point at both sides.
– With each new call of the sending block, you re-reference the remote partner by
specifying its IP address and its port number.
– If you have specified the length of the data to be received greater than the length
of the data to be sent, the receive block will copy the received data completely
into the receive range. After this, it will set NDR to TRUE and write RCVD_LEN
with the length of the sent data.
– If you have specified the length of the data to be received less than the length of
the sent data, the receive block will not copy any data into the receive range but
instead will supply the following error information: ERROR = 1, STATUS = 8088h.
Handling blocks Those in the following listed UTDs and FBs serve for "open communication" with other
Ethernet capable communication partners via your user program. These blocks are part
of the Siemens SIMATIC Manager. You will find these in the "Standard Library" at "Com-
munication Blocks". Please consider when using the blocks for open communication that
the partner station does not have to be configured with these blocks. This can be config-
ured with AG_SEND/AG_RECEIVE or IP_CONFIG. First you have to establish a hard-
ware configuration of the CPU and Ethernet PG/OP channel before you can use the han-
dling blocks.
220 HB400 | CPU | M13-CCF0000 | en | 20-02

Hardware configuration:
n CPU
Ä Chap. 4.5 ‘Hardware configuration - CPU’ page 69
n Ethernet PG/OP channel
To specify the Ethernet PG/OP channel, the following values are defined in the UDT 65:
n local_device_id
– 00h: Ethernet PG/OP channel of the CPU
n next_staddr_len
n next_staddr
UDTs
FB Designation Connection-oriented protocols: Connectionless protocol: UDP

TCP native as per RFC 793, ISO according to RFC 768
on TCP as per RFC 1006
UDT 65* TCON_PAR Data structure for assigning connec- Data structure for assigning parameters
tion parameters for the local communications access point
UDT 66* TCON_ADR Data structure for assigning addressing
parameters for the remote partner
*) More information about the usage of these blocks may also be found in the manual "SPEED7 Operation List" from VIPA.
FBs
FB Designation Connection-oriented protocols: Connectionless protocol: UDP

TCP native as per RFC 793, ISO according to RFC 768
on TCP as per RFC 1006
FB 63* TSEND Sending data
FB 64* TRCV Receiving data
FB 65* TCON Establishing a connection Configuring the local communications
access point
FB 66* TDISCON Terminating a connection Closing the local communications access
point
FB 67* TUSEND Sending data
FB 68* TURCV Receiving data
*) More information about the usage of these blocks may also be found in the manual "SPEED7 Operation List" from VIPA.
HB400 | CPU | M13-CCF0000 | en | 20-02 221

Deployment PG/OP communication - PROFINET VIPA System MICRO
Basics PROFINET
9 Deployment PG/OP communication - PROFINET

– With firmware version V2.4.0, there is a PROFINET IO controller
available via the Ethernet PG/OP channel.
– As soon as you use the PROFINET functionality via the Ethernet
PG/OP channel, this affects the performance and response time of
your system and due to the system the cycle time of the OB1 is
extended by 2ms.
9.1 Basics PROFINET

General n PROFINET is an open Industrial Ethernet Standard from PROFIBUS & PROFINET
International (PI) for automation.
n PROFINET is standardized in the IEC 61158.
n PROFINET uses TCP/IP and IT standards and supplements the PROFIBUS tech-
nology for applications, where fast data communication with industrial IT functions is
demanded.
There are 2 PROFINET function classes:

n PROFINET IO
n PROFINET CBA
These may be realized in 3 performance steps:
n TCP/IP communication
n RT communication
n IRT communication
PROFINET IO n With PROFINET IO an I/O data sight to the distributed periphery is described.
n PROFINET IO describes the whole data transfer between IO controller and IO device.
n PROFINET is configured like PROFIBUS.
n PROFINET IO always contains the real time concept.
n Contrary to the master-slave procedure of PROFIBUS, PROFINET uses the provider-
consumer model. This supports the communication relations (AR = Application Rela-
tion) between equal participants in the Ethernet. Here the provider sends its data
without a request of the communication partner.
n Apart from the user data exchange also functions for parametrization and diagnostics
are supported.
PROFINET CBA n PROFINET CBA means Component Based Automation.

n This component model describes the communication between autonomously working
stations.
n It makes a simple modularization of complex plants possible, by distributed intelli-
gence by means of graphic configuration for communication of intelligent modules.
TCP/IP communication This is the open communication via Ethernet TCP/IP without any demand on real-time.
RT Communication n RT means Real-Time.

n The RT communication represents the basics for data transfer at PROFINET IO.
n Here RT data are handled with higher priority.
222 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO Deployment PG/OP communication - PROFINET
Basics PROFINET
IRT Communication n IRT means Isochronous Real-Time.

n With the IRT communication the bus cycle begins clock-exactly i.e. with a maximum
permissible tolerance and is again synchronized. Thereby the time-controlled and
synchronous transfer of data is guaranteed.
n Here sync telegrams of a sync master in the network serve for.
Properties of PROFINET PROFINET of IEC 61158 has the following properties:

n Full-duplex transfer with 100MBit/s via copper respectively fibre optics.
n Switched Ethernet
n Auto negotiation (negotiates the transfer parameters)
n Auto crossover (transmission and receipt lines are crossed automatically if neces-
sary)
n Wireless communication via WLAN
n UDP/IP is used as overlaid protocol. UDP means User Datagram Protocol and con-
tains the unprotected connectionless broadcast communication within IP.
PROFINET devices Like PROFIBUS DP also with PROFINET IO the following devices are classified
according to their tasks:
n IO controller
– The IO controller is equivalent to the master of PROFIBUS.
– This is the PLC with PROFINET connection, in which the PLC program runs.
n IO device
– The IO device is a distributed I/O field device, which is connected to PROFINET.
– The IO device is equal to the slave of PROFIBUS.
n IO supervisor
– The IO supervisor is an engineering station as e.g. programming unit, PC or HMI
interface for commissioning and diagnostics.
AR AR (Application Relation) corresponds to a connection to an IO controller or IO super-

visor.
API n API means Application Process Identifier and defines besides Slot and Subslot a fur-
ther addressing level.
n With this additional addressing mode with using of different applications, the overlap-
ping of data areas can be prevented.
n The following APIs are currently supported by the VIPA PROFINET IO devices:
– DEFAULT_API (0x00000000 )
– DRIVE_API (0x00003A00)
– ENCODER_API (0x00003D00)
– FIELDBUS_INTEGRATION_API (0x00004600)
– PROFINET_IO_LINK_API (0x00004E01)
– RFID_READER_API (0x00005B00)
– BARCODE_READER_API (0x00005B10)
– INTELLIGENT_PUMP_API (0x00005D00)
– PROCESS_AUTOMATION_API (0x00009700)
GSDML file n To configure a device I/O connection in your own configuration tool, you’ve got all the
information about your PROFINET components in form of a GSDML file. This file may
be found for System MICRO in the download area of www.vipa.com at‘Config files
è PROFINET’.
n Please install the GSDML file in your configuration tool.
HB400 | CPU | M13-CCF0000 | en | 20-02 223

PROFINET installation guidelines
n More information about installing the GSDML file may be found at the manual of the
according engineering tool.
n Structure and content of the GSDML file are defined by IEC 61158.
Addressing In contrast to the PROFIBUS address, in PROFINET each device may be definitely iden-
tified with its PROFINET interface:
n Device name
n IP address respectively MAC address
Transfer medium PROFINET is compatible to Ethernet in accordance with the IEEE standards. The con-
nection of the PROFINET IO field devices is exclusively established via switches as net-
work components. This is made either as star via multi-port switches or as line by means
of switches, integrated to the field devices.
9.2 PROFINET installation guidelines

Generals to data security The topic of data security and access protection have become increasingly important in
the industrial environment. The increased networking of entire industrial systems to the
network levels within the company together with the functions of remote maintenance
have all served to increase vulnerability. Threats can arise from internal manipulation like
technical errors, operator and program errors respectively from external manipulation like
software viruses and worms, trojans and password phishing.
Precautions The most important precautions to prevent manipulation and loss of data security in the
industrial environment are:
n Encrypting the data traffic by means of certificates.
n Filtering and inspection of the traffic by means of VPN - "Virtual Private Networks".
n Identification of the nodes by "Authentication" via save channels.
n Segmenting in protected automation cells, so that only devices in the same group can
exchange data.
Guidelines for information With the "VDI/VDE 2182 sheet 1", Information Security in the Industrial Automation - Gen-
security eral procedural model, VDI guidelines, the VDI/VDE society for measuring and automa-
tion engineering has published a guide for implementing a security architecture in the
industrial environment. The guideline can be found at www.vdi.de PROFIBUS &
PROFINET International (PI) can support you in setting up security standards by means
of the "PROFINET Security Guideline". More concerning this can be found at the corre-
sponding web site e.g. www.profibus.com
Industrial Ethernet n Due to the open standard of PROFINET standard Ethernet components may be used.
n For industrial environment and due to the high transfer rate of 100MBit/s your
PROFINET system should consist of Industrial Ethernet components.
n All the devices interconnected by switches are located in one and the same network.
All the devices in a network can communicate directly with each other.
n A network is physically limited by a router.
n If devices need to communicate beyond the limits of a network, you have to configure
the router so that it allows this communication to take place.
224 HB400 | CPU | M13-CCF0000 | en | 20-02

Deployment as PROFINET IO controller > Steps of configuration
Topology n Linear
– With the linear structure all the communication devices are connected via a linear
bus topology.
– Here the linear bus topology is realized with switches that are already integrated
into the PROFINET device.
– If a communication member fails, communication across the failed member is no
longer possible.
n Star
– If you connect communication devices to a switch with more than 2 PROFINET
interfaces, you automatically create a star network topology.
– If an individual PROFINET device fails, this does not automatically lead to failure
of the entire network, in contrast to other structures.
– It is only if a switch fails that part of the communication network will fail as well.
n Ring
– In order to increase the availability of a network the both open ends of a linear
bus topology may be connected by a switch.
– By configuring the switch as redundancy manager on a break in the network it
ensures that the data is redirected over an intact network connection.
n Tree
– If you interconnect several star structures, you obtain a tree network topology.
9.3 Deployment as PROFINET IO controller

9.3.1 Steps of configuration

extended by 2ms.
Range of functions
Please regard that the PROFINET IO controller supports only the
PROFINET functions, which are described in this manual, even if the Sie-
mens CPU, which is used for configuration, offers further functions! To
use some described PROFINET functions, it is necessary to deploy
another Siemens CPU for configuration. Here, however, is pointed to
explicitly.
The configuration of the PROFINET IO controller for PROFINET communication should

be done by the following procedure:
1. Commissioning and Initialization (assignment IP address data)
2. Hardware configuration - CPU
3. Configuration PROFINET IO controller
4. Configuration PROFINET IO devices
With the Siemens SIMATIC Manager, the CPU M13-CCF0000 from VIPA
is to be configured as!
CPU 314C-2 PN/DP (314-6EH04-0AB0 V3.3)
HB400 | CPU | M13-CCF0000 | en | 20-02 225

Deployment as PROFINET IO controller > Configuration PROFINET IO controller
9.3.2 Commissioning and initialization

sioning
2. Wire the system by connecting cables for voltage supply and signals
3. Connect your PROFINET IO controller with Ethernet.
ð After a short boot time, the CP is in idle.
At the first commissioning respectively after an overall reset of the CPU, the
PROFINET IO controller has no IP address.
Assign IP address param- This function is supported only if the PROFINET IO controller is not yet configured. You
eters get valid IP address parameters from your system administrator. The assignment of the
IP address data happens online in the Siemens SIMATIC Manager starting with version V
5.5 & SP2 with the following proceeding:
1. Start the Siemens SIMATIC Manager.
2. Switch to "TCP/IP -> Network card .... " using ‘Options è Set PG/PC interface è ’.
3. Open the dialog for initialization of a station with ‘PLC è Edit Ethernet node’.
4. To get the stations and their MAC address, use the [Browse] button or type in the
MAC address. The Mac address may be found at the front of the CPU.
5. Choose if necessary the known MAC address of the list of found stations. To check
this with [Blink] you may cause the MT LED to blink.
6. 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
Directly after the assignment the PROFINET IO controller is online reachable using the
set IP address data. You can take the IP address data to your project by means of the
hardware configuration. Ä Chap. 4.5 ‘Hardware configuration - CPU’ page 69
9.3.3 Configuration PROFINET IO controller

9.3.3.1 Precondition
To parameterize the PROFINET IO controller of the CPU, the following conditions must
be fulfilled:
n The PROFINET IO controller is online reachable, this means an initialization was
established.
n The hardware configuration described before was established and the PROFINET IO
controller is networked.
Proceeding Open the properties dialog of the PROFINET IO controller by a double-click at PN-
IO.
226 HB400 | CPU | M13-CCF0000 | en | 20-02

Deployment as PROFINET IO controller > Configuration PROFINET IO controller
The PROFINET interface of the PROFINET IO controller is parameterized with PN-IO,

the port with Port 1. In the following these parameters for PN-IO and Port 1 are
described.
9.3.3.2 PN-IO
Tab: ‘General’
Short description Designation of the IO controller. For the IO controller of VIPA, the short description is
"PN-IO".
Device name The device name on the Ethernet subnet must be unique. During initialization the device
name is derived from the short description. You can change this at any time.
Support device replace- This parameter is not evaluated. With configured topology the device replacement without
ment without exchange- exchangeable medium is supported. Ä Chap. 9.7 ‘Device replacement without exchange-
able medium able medium/PG’ page 238
Properties With properties you can enter the IP address, subnet mask and gateway for the
PROFINET interface and select the subnet to be connected.
Tab: ‘Addresses’ The CPU reports errors of the IO controller via the interface address, as soon as e.g. an
error during synchronization of the IO controller occurs. With the PROFINET IO system
address the CPU reports e.g. failure/return of the PROFINET IO system. This address is
also used to identify the IO system to which the device belongs, if an IO device fails.
Tab: ‘PROFINET’ With the operation field "OB82 / I/O fault task..." you can cause the CPU to call the OB 82
at an error event of the PROFINET interface. An entry to the diagnostics buffer is always
done. The other parameters here are not relevant for the use of the VIPA PROFINET
CPU.
Tab: ‘I-Device’ These settings are not required for the use of the PROFINET IO controller as an I-Device
and should not be changed. Ä Chap. 9.4 ‘Deployment as PROFINET I-Device’ page 229
Tab: ‘Synchronization’ These settings are not relevant and should not be changed.
Tab: ‘Media Redundancy’ MRP is supported exclusively as a redundancy client. Ä Chap. 9.5 ‘MRP’ page 236
(MRP)
Tab: ‘Time-of-day In this area you can configure time-of-day master for time-of-day synchronization in the
synchronization’ network. Ä Chap. 4.7.1.1.1 ‘Time-of-day synchronization’ page 75
HB400 | CPU | M13-CCF0000 | en | 20-02 227

Deployment as PROFINET IO controller > Configuration PROFINET IO device
Tab: ‘Options’
Interval Here you can set the interval time with which "Keep-Alive" telegrams are to be sent to a
connection partner. This ensures that a communication partner can still be reached
because the connection resources are automatically released again after the expiration
interval time.
9.3.3.3 Port 1
Tab: ‘General’ Shown is the short name "Port...". In the field Name another designation may be selected,
which is also shown in the configuration table At comment you may describe your entry
near more. The comment also appears in the configuration table.
Tab: ‘Addresses’ Via the port address the diagnostics information of the IO controller may be accessed.
Tab: ‘Topology’ These parameters serve for the port setting for topology. Ä Chap. 9.6 ‘Topology’
page 237
Tab: ‘Options’ These parameters serve for the port setting. Here the following parameters are sup-
ported:
n Connection
– Here you can make settings for transmission medium and type. Ensure that the
setting for the local port and the partner port are identical.
– PROFINET requires 100Mbit/s in duplex mode.
n Boundaries
– Boundaries are limitations for the transfer of certain Ethernet frames. The fol-
lowing Boundaries are supported:
‘End of detection of accessible nodes’ : DCP frames for detecting accessible
nodes are not forwarded. When enabled, participants which are lying behind this
port, are no longer recognized and can not be reached by the controller.
‘End of topology discovery’ : When enabled, this port does not support topology
discovery, i.e. LLDP frames are not forwarded.
9.3.4 Configuration PROFINET IO device

Precondition The modules, which may be configured here are listed in the hardware catalog.
n For the deployment of the PROFINET IO devices from VIPA you have to include the
modules into the hardware catalog by means of the GSDML file from VIPA.
n After the installation of the GSDML file the PROFINET IO devices from VIPA may be
found in the hardware catalog at ‘PROFINET IO è Additional field devices è I/O
è VIPA ... ’
Configure IO devices Now the project engineering of the PROFINET IO controller is finished. Please link up
now your IO devices with periphery to your IO controller.
1. For the project engineering of PROFINET IO device you search the concerning
PROFINET IO device in the hardware catalog at PROFINET-IO and drag&drop it in
the subnet of your IO controller.
2. Assign a name to the IO device. The configured name must match the name of the
device. Information about setting the device name can be found in the manual of
the IO device.
228 HB400 | CPU | M13-CCF0000 | en | 20-02

Deployment as PROFINET I-Device > Steps of configuration
3. Enter a valid IP address. The IP address is normally assigned automatically by the

hardware configurator. If this is not desired, you can assign the IP address man-
ually.
4. Link up the modules of your IO device in the plugged sequence and add the
addresses that should be used by the modules.
5. If needed, parametrize the modules.
6. Save, compile and transfer your project. Ä Chap. 4.10 ‘Project transfer’ page 89
9.4 Deployment as PROFINET I-Device

9.4.1 Steps of configuration
Functionality
available via the Ethernet PG/OP channel, which can be configured
as I-Device.
extended by 2ms.
Range of functions
explicitly.
HB400 | CPU | M13-CCF0000 | en | 20-02 229

Deployment as PROFINET I-Device > Installing the GSDML file
The I-Device (Intelligent IO device) functionality of a CPU allows data to be exchanged

with an IO controller, which are preprocessed by the CPU. In this case, the I-Device is
connected as an IO device to a higher-level IO controller. The process values recorded in
central or decentralized periphery can be preprocessed via a user program and made
available to the higher-level PROFINET IO controller by means of PROFINET.
n The configuration of the integrated PROFINET IO controller of the VIPA CPU as an I-
Device is made via a virtual PROFINET devices, which is to be installed by means of
a GSDML from VIPA in the hardware catalog.
n The communication takes place via input/output areas, which are defined in the I-
Device.
n The size of the areas for input and output data is max. 768byte.
n The I-Device is made available to a deterministic PROFINET IO system via a
PROFINET IO interface and thus supports the real-time communication Real-Time.
n The I-Device functionality meets the requirements of the RT class I (A) and corre-
sponds to the PROFINET specification version V2.3.
n The configuration of a VIPA PROFINET CPU as an IO controller and at the same time
as an I-Device is possible. The influence of the I-Device configuration on the system
limits or performance of the PROFINET controller is equated with that of a device.
This means that when the IO controller and I-Device are used at the same time on the
PROFINET controller, the I-Device is to be regarded as an additional device for deter-
mining the system limits.
n In order for the higher-level IO controller to communicate with the VIPA I-Device, the
following must be observed:
– I-Device and higher-level IO controllers must be configured in different networks.
Their IP addresses must be in the same IP circuit.
– The device name of the PROFINET controller of the I-Device must match the
device name of the I-Device at the higher-level IO controller.
Configuration The configuration of the PROFINET IO controller as I-Device should be done by the fol-
lowing procedure:
1. Installation of the GSDML files
2. Configuration as I-Device
3. Configuration in the higher-level IO controller
9.4.2 Installing the GSDML file

The following GSDML files are required for configuring the integrated PROFINET IO con-
troller of the VIPA CPU as I-Device in the Siemens SIMATIC Manager:
n GSDML for I-Device
n GSDML for I-Device at IO controller
Proceeding
1. You can find the GSDML files in the download area of www.vipa.com. Load the file
and unzip it on your PC.
2. Start the Siemens SIMATIC Manager and install via ‘Options
è Install new GSD file’ both GSD files.
ð After the installation you can find the following virtual devices in the hardware
catalog at ‘PROFINET IO è Additional field devices è ...
è VIPA MICRO System’:
n PN I-Device for VIPA CPU
– This allows you to configure the Input/output areas in the I-Device of the
VIPA CPU.
n PN I-Device for higher-level CPU
– This allows you to connect the VIPA I-Device to the higher-level IO con-
troller.
230 HB400 | CPU | M13-CCF0000 | en | 20-02

Deployment as PROFINET I-Device > Configuration as I-Device
9.4.3 Configuration as I-Device

It is assumed that a hardware configuration of the CPU exists. Ä Chap. 4.5 ‘Hardware
configuration - CPU’ page 69
1. For the project engineering of PROFINET I-Device you have to search the virtual
device ‘PN I-Device for VIPA CPU’ in the hardware catalog at PROFINET-IO and
drag&drop it in the PROFINET subnet.
2. Open the properties dialog of the PROFINET IO controller of the CPU by a double-
click at ‘PN-IO’ and assign the name for the I-Device.
Write down the Name. This name must also be specified as the
‘device name’ of the I-Device for the higher-level IO controller.
3. For ‘PN-IO’ at ‘slot’ ‘X...’ assign an IP address via the properties dialog.
HB400 | CPU | M13-CCF0000 | en | 20-02 231

Deployment as PROFINET I-Device > Configuration in the higher-level IO controller
4. Create the transfer areas by dragging them to the ‘slots’ as I/O areas from the
hardware catalog. There must be no gaps in the slots. To create the transfer areas,
the following input and output areas are available that can be assigned to the virtual
I-Device:
n Input: 1, 8, 16, 32, 64, 128, 256, 512 byte
n Output: 1, 8, 16, 32, 64, 128, 256, 512 byte
The data direction for Input or Output refers to the view of the I-Device.
n Input areas define data that are sent from the higher-level IO controller to the I-
Device and which are mapped to the input address area of the CPU.
n Output areas define data that are sent to the higher-level IO controller and
which are to stored in the output address area of the CPU.
9.4.4 Configuration in the higher-level IO controller

It is assumed that a CPU is configured with IP address with the higher-level IO controller.
The IP address must be in the same IP circuit as the IP address of the I-Device.
1. Open the project of the CPU with the higher-level IO controller.
2. For the project engineering of VIPA I-Device in the high-level IO controller you have
to search the device ‘PN I-Device for high-level CPU’ in the hardware catalog at
PROFINET-IO and drag&drop it in the PROFINET subnet.
232 HB400 | CPU | M13-CCF0000 | en | 20-02

Deployment as PROFINET I-Device > Error behavior and interrupts
3. Open the properties dialog by double-clicking ‘PN-I-Device’ and enter at ‘device

name’ the previously noted name of the VIPA I-Device.
The configured name must match the name of the PROFINET IO

controller ‘PN-IO’ of the I-Device CPU, which you have noted
before! Ä Chap. 9.4.3 ‘Configuration as I-Device’ page 231
4. Configure an input area of the same size for each output area of the I-Device in the
IO controller and vice versa. Here also no gaps may arise. In particular, make sure
that the order of the transfer areas matches that of the I-Device configuration. The
following transfer units are available:
n Input: 1, 8, 16, 32, 64, 128, 256, 512 byte per slot
n Output: 1, 8, 16, 32, 64, 128, 256, 512 byte per slot
ð Your VIPA PROFINET controller is now connected as an I-Device to the higher-
level PROFINET IO controller.
I-Device with S7 routing

S7 routing is not possible with the procedure above. S7 routing is only
possible if the I-Device and the higher-level I/O controller are configured
in the same network. The device names must not be identical. By using
identical names and extending the name of the I-Device with "-x", this is
detected internally and used appropriately for S7 routing.
9.4.5 Error behavior and interrupts

Error behavior The system shows the following error behavior ...
n ... at gaps in the ‘slot’ configuration:
– If the configuration of the I-Device contains gaps in the ‘slot’ configuration (i.e.
there are free ‘slots’ before used ‘slots’ ), the configuration is rejected and
0xEA64 is returned as a configuration error in the diagnostic buffer.
– If the configuration of the higher-level IO controller contains gaps in the ‘slot’ con-
figuration (i.e. there are free ‘slots’ before used ‘slots’ ), the connection is rejected
with the PN IO Status ErrorCode1 = 0x40 and ErrorCode2 = 0x04
(AR_OUT_OF_RESOURCE).
n ... at modules, which differ from the configured:
– A ModuleDiffBlock is generated and the wrong modules are not served.
HB400 | CPU | M13-CCF0000 | en | 20-02 233

n ... if the number of configured modules in the IO controller is greater than the number
of configured modules in the I-Device:
– The IO controller receives a ModuleDiffBlock with ModuleStatus "NoModule" for
modules that are not configured in the I-Device. The I-Device sets the status of
the non-configured modules to "bad".
n ... if the number of configured modules in the I-Device is greater than the number of
configured modules in the IO controller:
– The IO controller does not receive an error because the additional modules are
unknown.
Starting position IO controller in RUN, I-Device in RUN

Event I-Device CPU goes to STOP
Reaction n An OB 85 is called in the IO controller for each input and output transfer
area, which is located in the process image, if messages of process image
transfer errors are parametrized. Ä 79
n An OB 122 is triggered in the IO controller for each peripheral direct access
to an input or output transfer area.

Event IO controller goes to STOP
Reaction n An OB 85 is called in the I-Device for each input transfer area, which is
located in the process image, if messages of process image transfer errors
are parametrized. Ä 79
n In the I-Device, an OB 122 is triggered for each peripheral direct access to
an input transfer area.
Note: Output transfer areas can still be accessed!

Event Station failure I-Device, e.g. by bus interruption
Condition I-Device must remain operational without a bus connection, i.e. the power
supply must further exist.
Reaction n An OB 86 (station failure) is called up in the IO controller.
n An OB 85 is called in the IO controller for each input and output transfer
n An OB 122 is triggered in the IO controller for each peripheral direct access
to an input or output transfer area.
n An OB 86 (station failure) is called up in the I-device.
n In the I-device, an OB 122 is triggered for each peripheral direct access to
an input or output transfer area.
234 HB400 | CPU | M13-CCF0000 | en | 20-02


Event Station recovery
Reaction n An OB 86 (recovery) is called in the IO controller.
n An OB 85 is called in the IO controller until the OB 86 has been called, for
each input and output transfer area, which is in the process diagram, if
messages of process image transfer errors are parametrized. Ä 79
n An OB 122 is triggered in the IO controller until the OB 86 is called, for
each peripheral direct access to an input or output transfer area.
n An OB 86 (return) is called in the I-Device.
n An OB 83 (sub module recovery) is called for each input transfer area in
the I-Device.
n In the I-device, an OB 85 is called for each input transfer area, which is in
the process image, if messages of process image transfer errors are para-
metrized and the corresponding OB 83 has not yet been called. Ä 79
n An OB 122 is triggered in the I-Device for each peripheral direct access to
an input transfer area, until the corresponding OB 83 has been called.
Starting position Controller in RUN, I-Device in STOP

Event I-Device starts
Reaction n The OB 100 (start-up) is called in the I-Device.
n The OB 83 (Return-of-Submodule) for input sub modules of the transfer
areas to the higher-level IO controller is called in the I-Device.
n An OB 85 is called in the I-device for each input transfer area, which is
located in the process image, if messages of process image transfer errors
are parametrized. Ä 79
n In the I-Device, an OB 122 is triggered for each peripheral direct access to
an input transfer area.
n OB 83 (Return-of-Submodule) for input and output sub modules of the
transfer areas to the I-Device is called in the IO controller.
area, which is located in the process diagram, if messages of process
image transfer errors are parametrized and the corresponding OB 83 has
not yet been called. Ä 79
n In the IO controller, an OB 122 is triggered for each peripheral direct
access to an input or output transfer area until the corresponding OB 83
has been called.
Starting position IO controller is in STOP, I-Device in RUN

Event IO controller starts
Reaction n The OB 83 (Return-of-Submodule) for input sub modules of the transfer
areas to the higher-level IO controller is called in the I-Device.
n An OB 85 is called for each transfer area, which is located in the process
image, in the I-device if messages of process image transfer errors are par-
ametrized and the corresponding OB 83 has not yet been called. Ä 79
n An OB 122 is triggered in the I-Device for each peripheral direct access to
an input transfer area, until the corresponding OB 83 has been called.
n The OB 100 (startup) is called in the IO controller.
HB400 | CPU | M13-CCF0000 | en | 20-02 235

MRP
9.5 MRP
Overview To increase the network availability of an industrial Ethernet network, you can connect a
line topology together to a ring topology. To set up a ring topology with media redun-
dancy, you have to bring together the two free ends of a linear bus topology in one
device. Closing the linear bus topology to form a ring is achieved with two ports (ring
ports) of a device in the ring. At least one device of the ring takes the role of the redun-
dancy manager. All other devices in the ring are redundancy clients. A standard media
redundancy method is MRP (Media Redundancy Protocol). Up to 50 devices per ring can
participate. The MRP (Media Redundancy Protocol) is specified in the standard IEC
61158 Type 10 "PROFINET".
Precondition
n The ring in which you want to use MRP may consist only of devices that support this
function.
n "MRP" must be activated for all devices in the ring.
n All devices must be connected via their ring ports.
n The ring may contain max. 50 devices.
n The connection setting (transmission medium/duplex) must be set to "full duplex" and
at least 100Mbit/s for all ring ports. Otherwise there may be a loss of data traffic.
Function n The data paths between the individual devices are automatically reconfigured if the
ring is interrupted at any point. After reconfiguration, the devices are accessible
again.
n In the redundancy manager, one of the both ring ports are blocked for uninterrupted
network operation for normal communication so that no data telegrams are circulated.
In terms of data transmission, the ring topology is a linear bus topology.
n The redundancy manager monitors the ring for interruptions. For this he sends test
frames from both ring port 1 and ring port 2. The test frames run through the ring in
both directions until they arrive at the other ring port of the redundancy manager.
n As soon as the interruption is removed, the original transmission paths are restored,
the two ring ports of the redundancy manager are disconnected and the redundancy
clients informed of the change. The redundancy clients then use the new paths to the
other devices.
Reconfiguration time The time between the ring interruption and restoration of a functional linear topology is
known as the reconfiguration time. At MRP the reconfiguration time is typically 200ms.
VIPA PROFINET CP as MRP is only supported as redundancy client. If the ring is opened or closed, you will be
redundancy client informed via the OB 82 "Neighbourhood change". With SFB 54 you can get more infor-
mation.
The use of MRP in the operating mode I-Device is not permissible and is
rejected during the configuration!
236 HB400 | CPU | M13-CCF0000 | en | 20-02

Topology
9.6 Topology
Overview By configuring the topology you specify for the PROFINET IO controller the physical con-
nections between the stations in your PROFINET IO system These "neighbourhood rela-
tions" are used among others at "Device replacement without exchangeable medium".
Here by comparison of target and current topology, the IO device without a name is
detected and automatically integrated to the user data traffic. By configuring the topology
you have the following options:
n You can evaluate topological errors in your application program
n You have greater flexibility in planning and expansion of a plant
Support Topology editor is limited

Please consider that the support for the topology editor of the Siemens
SIMATIC Manager is limited. Here you have only the possibility to con-
figure the target topology offline. An online matching is currently not pos-
sible. An interconnection of the ports is also possible by means of the
port properties!
Interconnection by means 1. Click in the hardware configurator at the according PROFINET port and open the
of the Port properties properties dialog via ‘Context menu è Object properties’ and select the register
‘Topology’ .
ð The properties dialog to interconnect the ports is opened.
2. Here you have the following parameters:
n Port interconnection
– Local port: Name of the local port
– Medium: Specifying the line type (copper, fibre optic cable). Currently, this
parameter is not evaluated.
– Cable name Specifying a cable name
n Partners
– Partner port: Name of the port to which the selected port is interconnected.
– Alternating partner ports: By specifying at ‘Partner port’ "Any partner", you
can configure alternating partner ports for the I/O devices. Currently, this
parameter is not evaluated.
n Cable data
– Cable length: Depending on the port medium you can set in the select list
the cable length, if the medium between two stations does not change. Here
the signal delay time is automatically calculated. Currently, this parameter is
not evaluated.
– Signal delay time: If the medium between two stations changes, a signal
delay time can be defined here. Currently, this parameter is not evaluated.
3. Close the properties dialog with [OK] again.
HB400 | CPU | M13-CCF0000 | en | 20-02 237

Device replacement without exchangeable medium/PG
9.7 Device replacement without exchangeable medium/PG

Overview IO devices, which support the PROFINET function Device replacement without
exchangeable medium/PG get their device name from the controller with the exchange.
These can be replaced without installing an "exchangeable medium" (memory card) with
the stored device name respectively without assigning a device name by a PG. To assign
the device name the IO controller uses the configured Topology and the "neighbourhood
relationship", which is determined by the IO devices.
Thus the Device replacement without exchangeable medium/PG is possible, the following
requirements must be met:
n The Topology of your PROFINET IO system with the corresponding IO devices must
be configured.
n The IO controller and the respective adjacent to the unit to be replaced IO device
must support the functionality Device replacement without exchangeable medium/PG.
n In the IO controller in the ‘Properties’ the option Support device replacement without
exchangeable medium must be enabled.
n The replaced device must be reset to delivery state, before.
Configuring the function The configuration of the function Device replacement without exchangeable medium/PG
in your PROFINET IO system happens with the following approach:
1. Double-click at the PROFINET interface of the IO controller of the CPU.
ð The properties dialog of this PROFINET interface is opened
2. Enable in the register ‘General’ the option ‘Support device replacement without
exchangeable medium’ .
3. Apply the settings with [OK].
4. Safe and translate the hardware configuration.
5. Configure your Topology. Ä Chap. 9.6 ‘Topology’ page 237
6. Transfer your project to the CPU.
Prepare the replace device For the replacement the "replace device" must be in "delivery state". If you have not
received a new "replace device" from VIPA, you have to prepare this with the following
approach:
1. For this connect your "replace device" local at your PG.
2. Start the Siemens SIMATIC Manager and execute ‘PLC è Edit Ethernet node’
3. Click at ‘Nodes accessible online’ at [Browse].
4. Select the according IO device, which you identify as your "replace device".
5. Click at ‘Reset to factory settings’ at [Reset].
ð Your IO device is now reset and has then "delivery state".
Replace device For the replacement the "replace device" must be in "delivery state".
1. Disconnect if not already done your device to be exchanged from power.
2. Replace this by your "replace device".
3. Connect the "replaced device" to power and turn it ON.
ð Here by comparison of target and current topology, the "replaced device" is
automatically detected by the IO controller and automatically integrated to the
user data traffic.
238 HB400 | CPU | M13-CCF0000 | en | 20-02

Commissioning and start-up behavior
9.8 Commissioning and start-up behavior

Start-up on delivery state In the delivery state the CPU is overall reset. After power ON the PROFINET part has no
configuration the PROFINET has no configuration. The PROFINET part is passive and
can be found by the device search.
Online with bus parame- n For the communication between IO controller and IO device the ways for the commu-
ters without project nication are to be defined before. For the clear specification of the communication
ways, these are established during the start-up by the IO controller, based on the
project data. Here the configuration takes place by a hardware configuration.
n As soon as the project data were transmitted, the IO controller performs a new
system start-up.
n In this state the IO controller may be accessed and its CPU may be configured via
Ethernet by the IO controller by means of the IP address.
IO device configuration n The PROFINET IO controller is configured by a hardware configuration. After the
transmission of the project into the IO controller, the IO controller has the whole infor-
mation for the addressing of and the data exchange with the IO devices.
n During the system start-up of the IO controller the IO devices are supplied with their
configured IP address by means of the DCP protocol. After PowerON and after trans-
mitting a new hardware configuration, due to the project data the system start-up of
the IO controller is initialized and it runs automatically. During the system start-up the
IO controller establishes a clear communication relation (CR) and an application rela-
tion (AR) to an IO device. Here the cyclic IO data, the acyclic R/W services and the
expected modules/sub modules are specified.
n The PROFINET IO controller does not have any physical LEDs to show the status.
The status information are stored as virtual LED states. During runtime, you can
determine their status using the SSL partial lists xy19h or xy74h. Ä Chap. 9.9.5 ‘Diag-
nostics status indication via SSLs’ page 242
– The BF3 LED is on when a PROFINET IO device is configured as "linked" but o
bus cable is connected.
– If the IO controller has received a valid configuration with at least one IO device,
the BS2-LED gets on.
– With Ethernet interface parameters, which are unsuitable for PROFINET opera-
tion, the BS2-LED flashes at 1Hz.
– If the IP address of the IO controller can not be used because e.g. it is duplicated,
the BS2-LED flashes at 0.5Hz.
– If at least one IO device is not in cyclic data exchange after the start-up, the BF3
LED blinks.
– If all IO devices are in cyclic data exchange, the BF3 LED gets off. After a suc-
cessful system start-up the system is ready for communication.
CPU state influences the After PowerON respectively a receipt of a new hardware configuration the configuration
IO process data data are automatically transferred to the IO controller. Dependent on the CPU state the
following behavior is shown by the IO controller:
n Behavior at CPU STOP
– In the STOP state of the CPU an output telegram is further cyclically sent, but the
contained data are marked as "invalid" and as output data zeros are transmitted.
– The IO controller further receives the input data of the IO devices and transfers
them cyclically to the input area of the CPU.
n Behavior at CPU RUN
– The IO controller cyclically reads the output data from the CPU and transfers
these as telegram to the configured IO devices.
– The IO controller receives the input data of the IO devices and transfers them
cyclically to the input area of the CPU.
HB400 | CPU | M13-CCF0000 | en | 20-02 239

PROFINET diagnostics > Diagnostics during runtime in the user program
9.9 PROFINET diagnostics

9.9.1 Overview
There are the following possibilities to get diagnostics information from your system:
n Diagnostics with the configuration and engineering tool
n Diagnostics during runtime in the user program (OB 1, SFB 52)
n Diagnostics via OB start information
n Diagnostics status indication via SSLs
9.9.2 Diagnostics with the configuration and engineering tool

If you are connected from your configuration respectively engineering tool via Ethernet
with the PROFINET IO controller, online diagnostics information may be accessed.
E.g. with ‘Station è Open online’ you get information about the state of your system.
Here missing respectively faulty components are shown by symbols.
In the following figure e.g. there is shown that the configured device 3 is missing and
device 4 reports an error.
9.9.3 Diagnostics during runtime in the user program

With SFB 52 RDREC (read record) you can access diagnostics data from your user pro-
gram e.g. in OB 1. The SFB 52 RDREC operates asynchronously, that is, processing
covers multiple SFB calls.
240 HB400 | CPU | M13-CCF0000 | en | 20-02

PROFINET diagnostics > Diagnostics during runtime in the user program
Example OB 1 For the cyclic access to the diagnostics data of the counter module 050-1BA00 the fol-
lowing example may be used in the OB 1:
AN M10.3 'If the reading terminated (BUSY=0) and

AN M10.1 'there is no job triggered (REQ=0) then
S M10.1 'start transfer of record (REQ:=1)
L W#16#4000 'Number of record set (0x4000)
T MW12
CALL SFB 52, DB52 'Call SFB 52 with Instance DB
REQ :=M10.1 'Trigger flag
ID :=DW#16#0018 'Smaller addr. of mixed module
INDEX :=MW12
MLEN :=14 'Length record set 0x4000
'with 1 entry
VALID :=M10.2 'Validity of the record set
BUSY :=M10.3 'Flag job just running
ERROR :=M10.4 'Error bit during read access
STATUS :=MD14 'Error codes
LEN :=MW16 'Length of the read record set
RECORD :=P#M 100.0 Byte 40
'Target (MB100, 40byte)
U M10.1
R M10.1 'Reset REQ
Diagnostics data The counter module 050-1BA00 serves for 20byte diagnostics data. The diagnostics data
of the module 050-1BA00 have the following structure:
Name: Bytes Function Default

ERR_A 1 Diagnostics 00h
MODTYP 1 Module information 18h
ERR_C 1 reserved 00h
ERR_D 1 Diagnostics 00h
CHTYP 1 Channel type 76h
NUMBIT 1 Number diagnostics bits per channel 08h
NUMCH 1 Number channels of the module 01h
CHERR 1 Channel error 00h
CH0ERR 1 Channel-specific error 00h
CH1ERR…CH7ERR 7 reserved 00h
DIAG_US 4 µs ticker 00h
HB400 | CPU | M13-CCF0000 | en | 20-02 241

PROFINET diagnostics > Diagnostics status indication via SSLs
More information about the diagnostics data may be found in the System
SLIO manual HB300_FM_050-1BA00.
9.9.4 Diagnostics via OB start information

n On an error the faulty system generates a diagnostics message for the CPU. Then
the CPU calls the according diagnostics OB. Here the CPU operating system trans-
fers start information to the local data of the OB.
n By evaluating the start information of the according OB you can get information about
cause and location of the error.
n During runtime you can access the start information with the system function SFC 6
RD_SINFO.
n Please consider that you can even read the start information in the OB himself,
because the data are temporary data.
Depending on the type of error, the following OBs are called in a diagnostics event:
n OB 82 on an error of an module at the IO device (Diagnostics interrupt)
n OB 83 on inserting respectively removing a module on a IO device
n OB 86 on failure respectively return of a IO device
More information about the OBs and their start information may be found
in the online help of your programming tool and in the manual "SPEED7
Operation List" from VIPA.
9.9.5 Diagnostics status indication via SSLs

The PROFINET IO controller does not have any physical LEDs to show the status. The
status information are stored as virtual LED states. During runtime, you can determine
their status using the SSL partial lists xy19h or xy74h. More can be found in the manual
operation list (HB00_OPL_SP7) of your CPU.
Virtual LEDs PROFINET

BF3 BS2 MT2 Meaning
(bus error) (Bus status) (Maintenance)
PROFINET is not configured.
PROFINET is configured with valid Ethernet interface parameter, valid IP

address and at least one IO device.
X X n Bus error, no connection to sub net/switch.
n Wrong transfer rate
n Full-duplex-transmission is not activated.
X X n Failure of a connected IO device.

2Hz n At least one IO device is not access-able.
n Faulty configuration
n I device is configured, but no connection exists yet.
242 HB400 | CPU | M13-CCF0000 | en | 20-02

PROFINET diagnostics > Diagnostics status indication via SSLs
BF3 BS2 MT2 Meaning

(bus error) (Bus status) (Maintenance)
X X n Ethernet interface parameter are not valid.
1Hz n I-Device is configured and Link mode does not correspond to ‘100 Mbps
full duplex’ .
X X There was no IP address assigned.
0.5Hz
X X Maintenance event of an IO device is pending respectively an internal error
happened.
X Simultaneous blinking indicates a not valid configuration.
4s on, 1s off 4s on, 1s off
The alternate blinking indicates that a firmware update of the PROFINET IO
controller is executed.
4Hz 4Hz
Firmware update of the PROFINET IO controller is finished without error.
X X With a suited configuration tool you can cause the MT LED to blink by means
of the function ‘Member blink test’ . This can be useful for e.g. identification of
2Hz the module.
on: | off: | blinking: | not relevant: X
Deployment BS LED - Bus n BS LED: off

status – PROFINET is not configured.
n BS LED: blinks with 1Hz
– Ethernet interface parameter are not valid.
n BS LED: blinks with 0.5Hz
– There was no IP address assigned.
n BS LED: on
– PROFINET is configured with valid Ethernet interface parameter, valid IP address
and at least one IO device.
Deployment of the MT LED n MT LED: off

- Maintenance – There is no maintenance event pending.
n MT LED: on
– Maintenance event of an IO device is pending respectively an internal error hap-
pened.
– Here in the diagnostic buffer of the CPU, an entry was created, where you can
find more information about the maintenance event and to resolve it. Ä Chap.
4.20 ‘Diagnostic entries’ page 116
Resolve the error and execute PowerOFF/ON.
– Currently you need to perform a power cycle, to switch the MT-LED off again.
n MT LED: blinks
– With a suited configuration tool you can cause the LED to blink by means of the
function ‘Member blink test’ . This can be useful for e.g. identification of the
module.
– Simultaneous blinking together with BF2 LED (4s on, 1s off) indicates that the
configuration is invalid.
– The alternate blinking with BF2 LED with 4Hz indicates that a firmware update of
the PROFINET IO controller is executed.
HB400 | CPU | M13-CCF0000 | en | 20-02 243

PROFINET system limits
9.10 PROFINET system limits

Maximum number devices Based on the devices, which have to communicate with the IO controller per ms, you can
and configurable connec- determine the maximum number of devices. This also results in the maximum number of
tions configurable connections. The Devices per ms can be determined by the sum formula of
the individual refresh times (A).
D Devices per ms
n Number of devices
A Refresh time device
Please note that the value D must always be rounded to the nearest
smaller integer!
The PROFINET IO controller has the following system limits

Devices per ms (D) Max. number of devices Max. number of configu-
rable connections
3 8 0
2 8 2
1 8 2
0 8 2
Output bytes per ms

O Output bytes per ms
n Number of devices
B Number output bytes per device
A Refresh time per device
The PROFINET IO controller has the following system limits:
n Max. Number output bytes per ms: 800
n Max. Number output bytes per device: 768
Input bytes per ms

I Input bytes per ms
n Number of devices
C Number input bytes per device
A Refresh time per device
The PROFINET IO controller has the following system limits:
n Max. number input bytes per ms: 800
n Max. number input bytes per device: 768
244 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO Option: PtP communication
Fast introduction
10 Option: PtP communication

General For the PtP communication the use of the optionally available extension module EM M09
is required. The extension module provides interface X1: PtP (RS422/485) with fixed pin
assignment. Ä Chap. 2.4 ‘Mounting’ page 16
n PtP functionality
– Using the PtP functionality the interface is allowed to connect via serial point-to-
Protocols The protocols respectively procedures ASCII, STX/ETX, 3964R, USS and Modbus are
supported.
Parametrization The parametrization of the serial interface happens during runtime using the FC/SFC 216
(SER_CFG). For this you have to store the parameters in a DB for all protocols except
ASCII.
Communication The FCs/SFCs are controlling the communication. Send takes place via FC/SFC 217
(SER_SND) and receive via FC/SFC 218 (SER_RCV). The repeated call of the FC/SFC
217 SER_SND delivers a return value for 3964R, USS and Modbus via RetVal that con-
tains, 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 FC/SFC 218 SER_RCV after SER_SND. The FCs/SFCs are included in the consign-
ment of the CPU.
Use FCs instead SFCs

Please regard that the special VIPA SFCs are not shown in the CPU.
Please use for programming tools e.g. Siemens SIMATIC Manager and
TIA Portal the according FCs of the VIPA library.
Overview FCs/SFCs for The following FCs/SFCs are used for the serial communication:
serial communication
FC/SFC Description
FC/SFC 216 SER_CFG RS485 parameterize
FC/SFC 217 SER_SND RS485 send
FC/SFC 218 SER_RCV RS485 receive
HB400 | CPU | M13-CCF0000 | en | 20-02 245

Option: PtP communication VIPA System MICRO
Principle of the data transfer
10.2 Principle of the data transfer

RS485 PtP communication The data transfer is handled during runtime by using FC/SFCs. The principle of data
transfer is the same for all protocols and is shortly illustrated in the following.
n Data, which are written into the according data channel by the CPU, is stored in a
FIFO send buffer (first in first out) with a size of 2x1024byte and then put out via the
interface.
n 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 CPU.
n If the data is transferred via a protocol, the embedding of the data to the according
protocol happens automatically.
n In opposite to ASCII and STX/ETX, the protocols 3964R, USS and Modbus require
the acknowledgement of the partner.
n An additional call of the FC/SFC 217 SER_SND causes a return value in RetVal that
includes among others recent information about the acknowledgement of the partner.
n Further on for USS and Modbus after a SER_SND the acknowledgement telegram
must be evaluated by a call of the FC/SFC 218 SER_RCV.
1 Program
2 Protocol
3 FIFO buffer
4 Interface
246 HB400 | CPU | M13-CCF0000 | en | 20-02

PtP communication via extension module EM M09
10.3 PtP communication via extension module EM M09

X1 PtP (RS422/485)
9pin SubD jack: (isolated)
Using the PtP functionality the RS485 interface is allowed to connect via serial point-to-
n Protocols:
– ASCII
– STX/ETX
– 3964R
– USS
– Modbus master (ASCII, RTU)
n Serial bus connection
– Full-duplex Four-wire operation (RS422)
– Half-duplex Two-wire operation (RS485)
– Data transfer rate: max 115 kBaud
Enable PtP functionality A hardware configuration to enable the PtP functionality is not necessary.

3. Establish a cable connection to the communication partner.

ð After a short boot time the interface X1 PtP is ready for PtP communication.
HB400 | CPU | M13-CCF0000 | en | 20-02 247

RS485 cabling with

PROFIBUS cable
1 X1 PtP interface
2 Periphery
– *) For traffic-free data transfer use a terminating resistor of approxi-

mately 120W.
– Never connect the cable shield and the M5V (pin 5) together, due to
the compensation currents the interfaces could be destroyed!
248 HB400 | CPU | M13-CCF0000 | en | 20-02

RS485 cabling with For isolated interfaces you have 5V (P5V) isolated at pin 6 and the corresponding ground
defined static voltage (M5V) at pin 5. With this isolated voltage, you can assign defined static voltage levels to
levels the signal lines and so ensure a low reflection level.
1 X1 PtP interface
2 Periphery
RS422 cabling
1 X1 PtP interface
2 Periphery
3 Send
4 Receive
*) For line lengths >50m, you have to solder a terminating resistor of approx. 330W on
the receiver side for traffic-free data transfer.
HB400 | CPU | M13-CCF0000 | en | 20-02 249

Parametrization > FC/SFC 216 - SER_CFG - Parametrization PtP
RS422 cabling with For isolated interfaces you have 5V (P5V) isolated at pin 6 and the corresponding ground
defined static voltage (M5V) at pin 5. With this isolated voltage, you can assign defined static voltage levels to
levels the signal lines and so ensure a low reflection level.
1 X1 PtP interface
2 Periphery
3 Send
4 Receive
*) For line lengths >50m, you have to solder a terminating resistor of approx. 330W on
the receiver side for traffic-free data transfer.
Status indication
X1 PtP Description
TxD
green flickers Send activity
No send activity
10.4 Parametrization
10.4.1 FC/SFC 216 - SER_CFG - Parametrization PtP
The parametrization happens during runtime deploying the FC/SFC 216 (SER_CFG). You
have to store the parameters for STX/ETX, 3964R, USS and Modbus in a DB.
250 HB400 | CPU | M13-CCF0000 | en | 20-02

Protocols and procedures
10.5 Communication
10.5.1 FC/SFC 217 - SER_SND - Send to PtP
This block sends data via the serial interface. The repeated call of the FC/SFC 217
SER_SND delivers a return value for 3964R, USS and Modbus via RETVAL that con-
tains, 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 FC/SFC 218 SER_RCV after SER_SND.
10.5.2 FC/SFC 218 - SER_RCV - Receive from PtP

This block receives data via the serial interface. Using the FC/SFC 218 SER_RCV after
SER_SND with the protocols USS and Modbus the acknowledgement telegram can be
read.
10.6 Protocols and procedures

Overview The CPU supports the following protocols and procedures:
n ASCII communication
n STX/ETX
n 3964R
n USS
n Modbus
ASCII ASCII data communication is one of the simple forms of data exchange. Incoming char-
acters are transferred 1 to 1. At ASCII, with every cycle the read FC/SFC is used to store
the data that is in the buffer at request time in a parametrized receive data block. If a tele-
gram 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. For this you can use the FB 1 - Receive_ASCII.
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.
n Any data transferred from the periphery must be preceded by a Start followed by the
data characters and the end character. Depending of the byte width the following
ASCII characters can be transferred: 5bit: not allowed: 6bit: 20...3Fh, 7bit: 20...7Fh,
8bit: 20...FFh.
n The effective data, which includes all the characters between Start and End are trans-
ferred to the CPU when the End has been received.
HB400 | CPU | M13-CCF0000 | en | 20-02 251

n When data is send from the CPU to a peripheral device, any user data is handed to
the FC/SFC 217 (SER_SND) and is transferred with added Start- and End-ID to the
communication partner.
n You may work with 1, 2 or no Start- and with 1, 2 or no End-ID.
n If no End-ID is defined, all read characters are transferred to the CPU after a parame-
terizable character delay time (Timeout).
As Start-res. End-ID all Hex values from 01h to 1Fh are permissible. Characters above
1Fh are ignored. In the user data, characters below 20h are not allowed and may cause
errors. The number of Start- and End-IDs may be different (1 Start, 2 End res. 2 Start, 1
End or other combinations). For not used start and end characters you have to enter FFh
in the hardware configuration.
Message structure:
3964 The 3964R procedure controls the data transfer of a point-to-point link between the CPU
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:
n STX: Start of Text
n DLE: Data Link Escape
n ETX: End of Text
n BCC: Block Check Character
n NAK: Negative Acknowledge
You may transfer a maximum of 255byte per message.
Procedure
When a DLE is transferred as part of the information it is repeated to dis-

tinguish 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 simulta-
neous send commands, the station with the lower priority will delay its
send command.
252 HB400 | CPU | M13-CCF0000 | en | 20-02

USS The USS protocol (Universelle serielle Schnittstelle = universal serial interface) is a serial
transfer protocol defined by Siemens for the drive and system components. This allows to
build-up a serial bus connection between a superordinated master and several slave sys-
tems. The USS protocol enables a time cyclic telegram traffic by presetting a fix telegram
length.
The following features characterize the USS protocol:
n Multi point connection
n Master slave access procedure
n Single master system
n Max. 32 participants
n Simple and secure telegram frame
It is essential:
n You may connect 1 master and max. 31 slaves at the bus
n The single slaves are addressed by the master via an address sign in the telegram.
n The communication happens exclusively in half-duplex operation.
n After a send command, the acknowledgement telegram must be read by a call of the
FC/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
with
STX - Start sign
STW - Control word
LGE - Telegram length
ZSW - State word
ADR - Address
HSW - Main set value
PKE - Parameter ID
HIW - Main effective value
IND - Index
BCC - Block Check Character
PWE - Parameter value
HB400 | CPU | M13-CCF0000 | en | 20-02 253

Broadcast with set bit 5 in

ADR byte
A request can be directed to a certain slave ore be send to all slaves as broadcast mes-
sage. 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 FC/SFC 218 SER_RCV. Only
write commands may be sent as broadcast.
Modbus n The Modbus protocol is a communication protocol that fixes a hierarchic structure
with one master and several slaves.
n Physically, Modbus works with a serial half-duplex connection. There are no bus con-
flicts occurring, because the master can only communicate with one slave at a time.
n After a request from the master, this waits for a preset delay time for an answer of the
slave. During the delay time, communication with other slaves is not possible.
n After a send command, the acknowledgement telegram must be read by a call of the
FC/SFC 218 SER_RCV.
n The request telegrams send by the master and the respond telegrams of a slave have
the following structure:
Telegram structure
Start sign Slave address Function Code Data Flow control End sign
Broadcast with slave n A request can be directed to a special slave or at all slaves as broadcast message.
address = 0 n To mark a broadcast message, the slave address 0 is used.
n In opposite to a "normal" send command, the broadcast does not require a telegram
evaluation via FC/SFC 218 SER_RCV.
n Only write commands may be sent as broadcast.
ASCII, RTU mode Modbus offers 2 different transfer modes. The mode selection happens during runtime by
using the FC/SFC 216 SER_CFG.
n ASCII mode: Every byte is transferred in the 2 sign ASCII code. The data are marked
with a start and an end sign. This causes a transparent but slow transfer.
n RTU mode: Every byte is transferred as one character. This enables a higher data
pass through as the ASCII mode. Instead of start and end sign, a time control is used.
Supported Modbus proto- The following Modbus Protocols are supported by the RS485 interface:
cols
n Modbus RTU Master
n Modbus ASCII Master
254 HB400 | CPU | M13-CCF0000 | en | 20-02

Modbus - Function codes
10.7 Modbus - Function codes

Naming convention Modbus has some naming conventions:
n Modbus differentiates between bit and word access; bits = "Coils" and words = "Reg-
ister".
n Bit inputs are referred to as "Input-Status" and bit outputs as "Coil-Status".
n word inputs are referred to as "Input-Register" and word outputs as "Holding-Reg-
ister".
Range definitions Normally the access at 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 VIPA CPs is not differentiating digital and analog data, the following assignment is
valid:
0x - Bit area for master output data
Access via function code 01h, 05h, 0Fh
1x - Bit area for master input data

Access via function code 02h
3x - word area for master input data

Access via function code 04h
4x - word area for master output data

Access via function code 03h, 06h, 10h
A description of the function codes follows below.
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:
Code Command Description

01h Read n bits Read n bits of master output area 0x
02h Read n bits Read n bits of master input area 1x
HB400 | CPU | M13-CCF0000 | en | 20-02 255

Code Command Description

03h Read n words Read n words of master output area 4x
04h Read n words Read n words master input area 3x
05h Write 1 bit Write 1 bit to master output area 0x
06h Write 1 word Write 1 word to master output area 4x
0Fh Write n bits Write n bits to master output area 0x
10h Write n words Write n words to master output area 4x
Point of View of "Input" and "Output" data

The description always takes place from the point of view of the master. Here data, which
were sent from master to slave, up to their target are designated as "output" data (OUT)
and contrary slave data received by the master were designated as "input" data (IN).
Respond of the slave If the slave announces an error, the function code is send back with an "ORed" 80h.
Without an error, the function code is sent back.
Slave answer: Function code OR 80h ® Error

Function code ® OK
Byte sequence in a word 1 word

High-byte Low-byte
Check sum CRC, RTU, The shown check sums CRC at RTU and LRC at ASCII mode are automatically added to
LRC every telegram. They are not shown in the data block.
Read n bits 01h, 02h Code 01h: Read n bits of master output area 0x
Code 02h: Read n bits of master input area 1x
256 HB400 | CPU | M13-CCF0000 | en | 20-02

Command telegram
Slave address Function code Address 1. bit Number of bits Check sum
CRC/LRC
1byte 1byte 1word 1word 1word
Respond telegram
Slave address Function code Number of Data 1. byte Data 2. byte ... Check sum
read bytes CRC/LRC
1byte 1byte 1byte 1byte 1byte 1word
max. 250byte
Read n words 03h, 04h 03h: Read n words of master output area 4x
04h: Read n words master input area 3x
Command telegram
Slave address Function code Address 1. bit Number of words Check sum
CRC/LRC
Respond telegram
Slave address Function code Number of Data 1. word Data 2. word ... Check sum
read bytes CRC/LRC
1byte 1byte 1byte 1word 1word 1word
max. 125words
Write 1 bit 05h Code 05h: Write 1 bit to master output area 0x
A status change is via "Status bit" with following values:
"Status bit" = 0000h ® Bit = 0
"Status bit" = FF00h ® Bit = 1
Command telegram
Slave address Function code Address bit Status bit Check sum
CRC/LRC
Respond telegram
Slave address Function code Address bit Status bit Check sum
CRC/LRC
HB400 | CPU | M13-CCF0000 | en | 20-02 257

Write 1 word 06h Code 06h: Write 1 word to master output area 4x
Command telegram
Slave address Function code Address word Value word Check sum
CRC/LRC
Respond telegram
Slave address Function code Address word Value word Check sum
CRC/LRC
Write n bits 0Fh Code 0Fh: Write n bits to master output area 0x
Please regard that the number of bits has additionally to be set in byte.
Command telegram
Slave Function Address 1. Number of Number of Data 1. Data 2. ... Check sum
address code bit bits bytes byte byte CRC/LRC
1byte 1byte 1word 1word 1byte 1byte 1byte 1byte 1word
max. 250byte
Respond telegram
Slave address Function code Address 1. bit Number of bits Check sum
CRC/LRC
Write n words 10h Code 10h: Write n words to master output area 4x
Command telegram
Slave Function Address 1. Number of Number of Data 1. Data 2. ... Check sum
address code word words bytes word word CRC/LRC
1byte 1byte 1word 1word 1byte 1word 1word 1word 1word
max. 125words
Respond telegram
Slave address Function code Address 1. word Number of words Check sum
CRC/LRC
258 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO Option: Deployment PROFIBUS communication
Fast introduction
11 Option: Deployment PROFIBUS communication

Overview For the PROFIBUS communication the use of the optionally available extension module
EM M09 is required. The extension module provides interface X2: MPI(PB) with fixed pin
assignment. Ä Chap. 2.4 ‘Mounting’ page 16 The PROFIBUS DP slave is to be config-
ured in the hardware configurator from Siemens. Here the configuration happens by the
sub module X1 (MPI/DP) of the Siemens CPU.

Steps of configuration The configuration of the PROFIBUS DP slave should be done with the following
approach:
n Activating bus functionality by means of a VSC
n Use as DP slave
– With activating the bus functionality ‘PROFIBUS DP slave’ by means of a VSC,
the bus functionality ‘PROFIBUS DP slave’ is unlocked.
n Transfer of the entire project to the CPU
With the Siemens SIMATIC Manager, the CPU M13-CCF0000 from VIPA
is to be configured as
CPU 314C-2 PN/DP (314-6EH04-0AB0 V3.3)
The PROFIBUS DP slave is to be configured and connected via the sub
module X1 (MPI/DP).
HB400 | CPU | M13-CCF0000 | en | 20-02 259

Option: Deployment PROFIBUS communication VIPA System MICRO
PROFIBUS communication
11.2 PROFIBUS communication

PROFIBUS DP n PROFIBUS is an international standard applicable to an open and serial field bus for
building, manufacturing and process automation that can be used to create a low
(sensor-/actuator level) or medium (process level) performance network of program-
mable logic controllers.
n PROFIBUS comprises an assortment of compatible versions. The following details
refer to PROFIBUS DP.
n PROFIBUS DP is a special protocol intended mainly for automation tasks in a manu-
facturing environment. DP is very fast, offers Plug'n'Play facilities and provides a cost-
effective alternative to parallel cabling between PLC and remote I/O. PROFIBUS DP
was designed for high-speed data communication on the sensor-actuator level.
n The data transfer referred to as "Data Exchange" is cyclical. During one bus cycle,
the master reads input values from the slaves and writes output information to the
slaves.
DP slave operation For the deployment in a super-ordinated master system you first have to project your
slave system as Siemens CPU in slave operation mode with configured in-/output areas.
Afterwards you configure your master system. Couple 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.
Operating mode DP slave: There is the possibility to enable the option ‘Test, commissioning, routing’ in the hard-
Test, commissioning, ware configuration by means of the properties dialog of the PROFIBUS via the register
routing (active/passive) ‘Operating mode’ at ‘DP slave’ . The activation affects as follows:
n The PROFIBUS interface gets an "active" PROFIBUS node, this means it is involved
in the token rotation.
n Via this interface you have PG/OP functions (programming, status request, control,
test).
n The PROFIBUS interface serves as a gateway (S7 routing).
n The bus rotation time can exceed.
When disabled, the PROFIBUS interface operates as passive DP slave with the following
characteristics:
n The PROFIBUS interface gets an "passive" PROFIBUS node, this means it is not
involved in the token rotation.
n Bus rotation time is not influenced.
n S7 routing is not possible.
260 HB400 | CPU | M13-CCF0000 | en | 20-02

PROFIBUS communication via extension module EM M09
11.3 PROFIBUS communication via extension module EM M09

X2 MPI(PB)
The interface supports the following functionalities, which are switch able by an hardware
configuration:
n PROFIBUS DP slave (option)
the sub module ‘MPI/DP’ of the CPU in the hardware configuration.
Enable PROFIBUS func- The activation of the PROFIBUS functionality of the extension module EM M09 happens
tionality with the following proceeding:

To switch the interface X2 MPI(PB) to PROFIBUS functionality

you have to activate the according bus functionality by means
of a VSC storage media from VIPA. By plugging the VSC
storage card and then an overall reset the according function-
ality is activated. Ä Chap. 4.16 ‘Deployment storage media -
VSD, VSC’ page 110
HB400 | CPU | M13-CCF0000 | en | 20-02 261

PROFIBUS communication via extension module EM M09
1 RS485 interface
2 Periphery
Never connect the cable shield and the M5V (pin 5) together, since the
interfaces could be destroyed!
Status indication
DE
green n Slave is in DE (data exchange).
n Slave exchanges data with the master.
green blinking n Slave CPU is in state start-up.
n Slave-CPU is without master.
n There is no power supply.
n Slave has no configuration.
262 HB400 | CPU | M13-CCF0000 | en | 20-02

Deployment as PROFIBUS DP slave
11.4 Deployment as PROFIBUS DP slave

Fast introduction In the following the deployment of the PROFIBUS section as "intelligent" DP slave on
master system is described, which exclusively may be configured in the Siemens
SIMATIC Manager. The following steps are required:
1. Configure a station with a CPU with operating mode DP slave.
2. Connect to PROFIBUS and configure the in-/output area for the slave section.
3. Save and compile your project.
4. Configure another station with another CPU with operating mode DP master.
5. Connect to PROFIBUS and configure the in-/output ranges for the master section.
6. Save, compile and transfer your project to your CPU.
Project engineering of the 1. Start the Siemens SIMATIC Manager and configure a CPU as described at "Hard-
slave section ware configuration - CPU".
2. Designate the station as "...DP slave".
3. Add your modules according to the real hardware assembly.
4. Open the properties dialog of the DP interface of the CPU by means of a double-
click at ‘MPI/DP’ .
5. Set Interface type to "PROFIBUS".
6. Connect to PROFIBUS and preset an address (e.g. 3) and confirm with [OK].
7. Switch at Operating mode to "DP slave" .
8. Via Configuration you define the in-/output address area of the slave CPU, which
are to be assigned to the DP slave.
1 Standard bus: Object properties

Operating mode: DP slave
Connect: PROFIBUS
PROFIBUS address > 1
2 Configuration
Input area
Output area
Project engineering of the 1. Insert another station and configure a CPU.

master section
2. Designate the station as "...DP master".
3. Add your modules according to the real hardware assembly.
HB400 | CPU | M13-CCF0000 | en | 20-02 263

Deployment as PROFIBUS DP slave
4. Open the properties dialog of the DP interface of the CPU by means of a double-
click at ‘MPI/DP’ .
5. Set Interface: type to "PROFIBUS".
6. Connect to PROFIBUS and preset an address (e.g. 2) and confirm with [OK].
7. Switch at Operating mode to "DP master" and confirm the dialog with [OK].
8. Connect your slave system to this master system by dragging the "CPU 31x" from
the hardware catalog at Configured stations onto the master system and select your
slave system to be coupled.
9. Open the Configuration at Object properties of your slave system.
10. 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.
1 Standard bus: Object properties from ‘Configured stations’

Operating mode: DP master 3 DP master system: Object properties
PROFIBUS address > 1 Input area slave CPU = Output area master CPU
2 Hardware catalog: CPU 31x Output area slave CPU = Input area master CPU
264 HB400 | CPU | M13-CCF0000 | en | 20-02

Deployment as PROFIBUS DP slave > Diagnostic functions
11.4.1 Diagnostic functions

Overview PROFIBUS DP provides an extensive set of diagnostic functions for quick error localiza-
tion. Diagnostic messages are transferred via the bus and collected by the master. In the
operating mode DP slave the CPU sends diagnostic data when requested by the master
or in case of an error. Since a part of the diagnostic data (Byte 11 ... 15) is located in the
peripheral address area of the CPU, you may start the diagnostics and modify the diag-
nostic data. Diagnostic data consist of:
n Standard diagnostic data (Byte 0 ... 5),
n Device specific diagnostic data (Byte 6 ... 15).
Structure The diagnostic data have the following structure:
Standard diagnostic data
Byte 0 Station status 1

Byte 3 Master address
Byte 4 Ident number (low)
Byte 5 Ident number High
Device specific diagnostic data
Byte 6 Length and code device specific diagnostic

Byte 7 Device specific diagnostic messages
Byte 8... reserved
Byte 10
Byte 11 ... Byte 15 User-specific diagnostic data is mapped into the
peripheral addressing range of the CPU and may be
modified and sent to the master.
HB400 | CPU | M13-CCF0000 | en | 20-02 265

Standard diagnostic data More detailed information to the structure of the slave standard diagnostic data can be
found in the standard papers of the PROFIBUS User Organization. The slave diagnostic
data have the following structure:
Byte Bit 7 ... Bit 0

0 n Bit 0: 0 (fix)
n Bit 1: Slave is not yet ready for data exchange
n Bit 2: Configuration data are not identical
n Bit 3: Slave has external diagnostic data
n Bit 4: Slave does not provide this function
n Bit 5: 0 (fix)
n Bit 6: Wrong parametrization
n Bit 7: 0 (fix)
1 n Bit 0: Slave needs new parametrization
n Bit 1: Static diagnostic
n Bit 2: 1 (fix)
n Bit 3: Response monitoring active
n Bit 4: Freeze command received
n Bit 5: Sync command received
n Bit 6: reserved
n Bit 7: 0 (fix)
2 n Bit 0 ... Bit 6: reserved
n Bit 7: Diagnostic data overflow
3 Master address after parametrization
4 ID number high byte
5 ID number low byte
266 HB400 | CPU | M13-CCF0000 | en | 20-02

Device specific diagnostic The device related diagnostic data provide detailed information on the slave and the
data peripheral modules. The length of the device related diagnostic data is fixed at 10byte

6 n Bit 0 ... 5: Length device specific diagnostic data
– 001010: Length 10byte (fix)
n Bit 6 ... 7: Code for device specific diagnostic
– 00: Code 00 (fix)
7 n Device specific diagnostic message
– 12h: Error: Data length parameters
– 13h: Error: Data length configuration data
– 14h: Error: Configuration entry
– 15h: Error: VPC3 buffer calculation
– 16h: Missing configuration data
– 17h: Error: Comparison DP parametrization and configuration
– 40h: User specific diagnostic data is valid
8 ...10 reserved
11 ...15 User specific diagnostic data that are stored behind the diagnostic
status byte in the process picture of the CPU.
This data may be overwritten and forwarded to the master.
Release diagnostic n In case of a diagnostic the contents of Byte 11 ... 15 of the device specific diagnostic
data will be transferred to the process image of the CPU and this preceded by a
status byte.
n Where this diagnostic block with a length of 6byte is located in the process image can
be defined via the CPU parameters.
n You start diagnostics by means of a status change from 0 à 1 in the diagnostic status
byte.
n This transmits the respective diagnostic message to the master.
n A status of 0000 0011 is ignored!
The diagnostic block of the CPU has the following structure:

0 Diagnostic status byte
n Bit 0: User specific diagnostic data
– 0: Invalid diagnostic data
– 1: Valid diagnostic data
(starting a diagnostic)
n Bit 1: Delete diagnostic
– 0: Diagnostic deletion not valid
– 1: Diagnostic deletion valid
n Bit 2 ... Bit 7: reserved
1 ... 5 User specific diagnostic data equal to
Byte 11 ... 15 of device specific diagnostic
HB400 | CPU | M13-CCF0000 | en | 20-02 267

PROFIBUS installation guidelines
11.5 PROFIBUS installation guidelines

PROFIBUS in general n A PROFIBUS DP network may only be built up in linear structure.
n PROFIBUS DP consists of minimum one segment with at least one master and one
slave.
n A master has always been deployed together with a CPU.
n PROFIBUS supports max. 126 participants.
n Per segment a max. of 32 participants is permitted.
n The max. segment length depends on the transfer rate:
9.6 ... 187.5bit/s ® 1000m
500kbit/s ® 400m
1.5Mbit/s ® 200m
3 ... 12Mbit/s ® 100m
n Max. 10 segments may be built up. The segments are connected via repeaters. Every
repeater counts for one participant.
n The bus respectively a segment is to be terminated at both ends.
n All participants are communicating with the same transfer rate. The slaves adjust
themselves automatically on the transfer rate.
Transfer medium n As transfer medium PROFIBUS uses an isolated twisted-pair cable based upon the
RS485 interface.
n 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.
n Max. 32 participants per segment are permitted. Within a segment the members are
linear connected. The segments are connected via repeaters. The maximum segment
length depends on the transfer rate.
n PROFIBUS DP uses a transfer rate between 9.6kbit/s and 12Mbit/s, the slaves are
following automatically. All participants are communicating with the same transfer
rate.
n The bus structure under RS485 allows an easy connection res. disconnection of sta-
tions 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.
268 HB400 | CPU | M13-CCF0000 | en | 20-02

The PROFIBUS line has to be terminated with its ripple resistor. Please
make sure to terminate the last participants on the bus at both ends by
activating the terminating resistor.
EasyConn bus connector

In PROFIBUS all participants are wired parallel. For that purpose, the bus cable must be
feed-through. Via the order number 972-0DP10 you may order the bus connector "Easy-
Conn" from YASKAWA. This is a bus connector with switchable terminating resistor and
integrated bus diagnostic.
Dimensions in mm 0° 45° 90°

A 64 61 66
B 34 53 40
C 15.8 15.8 15.8
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 cable order no: 2170222, 2170822, 2170322.
With the order no. 905-6AA00 YASKAWA offers the "EasyStrip" de-iso-
lating tool that makes the connection of the EasyConn much easier.
Dimensions in mm
Termination with "Easy- The "EasyConn" bus connector is provided with a switch that is used to activate a termi-
Conn" nating resistor.
HB400 | CPU | M13-CCF0000 | en | 20-02 269

Wiring
[1] 1./last bus participant

[2] further participants
CAUTION!
The terminating resistor is only effective, if the connector is installed at a
bus participant and the bus participant is connected to a power supply.
The tightening torque of the screws to fix the connector to a device must
not exceed 0.02Nm!
A complete description of installation and deployment of the terminating

resistors is delivered with the connector.
Assembly
1. Loosen the screw.
2. Lift contact-cover.
3. Insert both wires into the ducts provided (watch for the correct line colour as below!)
4. Please take care not to cause a short circuit between screen and data lines!
5. Close the contact cover.

6. Tighten screw (max. tightening torque 0.08Nm).
The green line must be connected to A, the red line to B!
270 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO Configuration with VIPA SPEED7 Studio
SPEED7 Studio - Overview
12 Configuration with VIPA SPEED7 Studio

12.1 SPEED7 Studio - Overview
SPEED7 Studio - Working In this part the project engineering of the VIPA CPU in the VIPA SPEED7 Studio is
environment shown. Here only the basic usage of the SPEED7 Studio together with a VIPA CPU is
shown. Please note that software changes can not always be considered and it may thus
be deviations to the description. In the SPEED7 Studio your VIPA PLCs may be config-
ured and linked. For diagnostics online tools are available.
More information can be found in the online help respectively in docu-

mentation of the SPEED7 Studio.
Starting the SPEED7

Studio
Click at the button. You can find SPEED7 Studio in Windows Start at ‘VIPA’.
ð SPEED7 Studio is started. The start page is opened.
(1) Start You can create a new project, open a saved project, or delete projects.
(2) Project If a project is open, you can open the ‘Project overview’ or add a new
device.
(3) Last projects Here recently opened projects are listed.
You can repeatedly run SPEED7 Studio in order to work with

different projects. You can not open the same project in the var-
ious instances of SPEED7 Studio.
HB400 | CPU | M13-CCF0000 | en | 20-02 271

Configuration with VIPA SPEED7 Studio VIPA System MICRO
SPEED7 Studio - Work environment
End SPEED7 Studio

Select one of the following options if you want to end the program:
n Main window: Click on the Close button of the SPEED7 Studio program
window.
n Menu bar Select ‘File è Exit’.
n Keyboard: Press [Alt] + [F4].
After you have made changes to the project, a dialogue window opens where you
can select whether to save or ignore the changes.
ð SPEED7 Studio is ended.
12.2 SPEED7 Studio - Work environment
(1) Menu bar (5) Area of operations

(2) Toolbar (6) Output range
(3) CPU control centre (7) Catalog/properties
(4) Project tree (8) Status line
You can show and hide additional windows and the arrangement and size of the windows
can be adjusted.
272 HB400 | CPU | M13-CCF0000 | en | 20-02

SPEED7 Studio - Work environment
(1) Menu bar Most of the commands you need for working with SPEED7 Studio are provided in the
menu bar. Further commands can be accessed via the context menus using the right
mouse button, e.g. functions of a device in the project tree.
The menu commands ‘Project’ and ‘Device’ are only shown if a project is open. The
menu commands ‘Image’ is only shown if a HMI image is open.
You can use the menus with the mouse or the keyboard.
(2) Toolbar Important commands you need for working with SPEED7 Studio are provided in the
toolbar. More commands can be accessed via the toolbars and push buttons of different
editors.
Some of the commands in the toolbar are only shown if a project is open.
(3) CPU control centre In the CPU control centre, you can view the current mode and other control data and con-
trol the CPU.
(4) Project tree Any project device and project data can be accessed via the project tree. The project tree
includes any object which you have created in the project, e.g. devices, components, pro-
gram blocks, HMI images. Here you can add or remove devices and components. Fur-
thermore, you can open editors in order to edit settings, configurations, the control pro-
gram and visualisation.
(5) Area of operations Devices and project data can be edited in the area of operations. You can open different
editors for this purpose. The register in the area of operations is divided into two register
levels. You can switch through the editors in the area of operations via the tabs.
(6) Output range Information on executed activities and background operations are displayed on the output
range.
(7) Catalog/properties Devices and components which you want to add to the project can be selected in the cat-
alog. You can also select objects which you want to add to the PLC program or to HMI
images.
(8) Status line The version of SPEED7 Studio is displayed at the left edge of the status line. The pro-
gress bar for background operations and status messages is shown at the right edge. As
long as there are no background operations, the status message created at last is shown.
HB400 | CPU | M13-CCF0000 | en | 20-02 273

SPEED7 Studio - Work environment > Project tree
12.2.1 Project tree

(1) Title and author
(2) Project
(3) Documentation
(4) PLC
(5) Motion Control
(6) PLC program
(7) Local components
(8) Field periphery
(9) HMI
In the project tree, you can access commands in order to add or delete objects, e.g. add/
delete devices or add/delete blocks.
You can open editors via the project tree if you want to edit settings, configurations, the
control program and visualisation.
Moreover, you can retrieve information, e.g. project overview, device properties or proper-
ties of the bus system.
Show project tree If the project tree is not displayed, you must select either ‘View è Project tree’ or press
[Strg]+[Shift]+[P].
Show projects in the In order to display the project in the project tree, you must create a new project or open a
project tree stored project.
It is not possible to edit several projects at the same time. It is possible to run
SPEED7 Studio simultaneously several times on one PC if you want to use it for various
projects.
Show/hide objects The objects in the project tree are arranged in a tree structure. You can show or hide
objects:
Hide all objects (‘Project è Reduce project tree’)
Show all objects (‘Project è Expand project tree’)

Recognise object state Icons behind an object in the project tree provide indications of the object state.
274 HB400 | CPU | M13-CCF0000 | en | 20-02

SPEED7 Studio - Work environment > Catalog
12.2.2 Catalog
(1) Switching to another view
(2) Register
(3) Show/hide objects
(4) Search
(5) Filter
(6) Objects
(7) Catalog information
Devices and components which you want to add to the project can be selected in the cat-
alog. You can also select objects which you want to add to the PLC program or to HMI
images.
Show catalog:
If the catalog is not displayed, you must select either ‘View è Catalog’ or press [Strg]+
[Shift]+[C].
(1) Switch to another view If the properties are displayed instead of the catalog, you must click on ‘Catalog’ at the
lower screen edge.
(2) Register Certain tabs are displayed in the catalog, depending on which editor window is opened in
the foreground.
(3) Show/hide objects The objects in the catalog are arranged in a tree structure. You can show or hide objects:
Hide all objects (‘Project è Reduce project tree’)
Hide all objects (‘Project è Reduce catalog tree’)
Show all objects (‘Project è Expand catalog tree’)

HB400 | CPU | M13-CCF0000 | en | 20-02 275

SPEED7 Studio - Work environment > Catalog
(4) Search
You can search for certain objects in the catalog.
1. Enter a search text in the input field.
ð Only those objects are displayed in the catalog which contain the search text.
2. Click on to delete the search text.
ð All objects are displayed in the catalog.
(5) Filter With ‘enabled’ Filter, only these modules are shown in the Catalog which are relevant for
configuration
(6) Add object

Drag the desired object from the catalog to a suitable position.
ð The object is added.
Example
(1) Select the desired object (hold left mouse button down)
(2) Drag the object
(3) Drop the object at a suitable place (release the mouse button)
(4) The object is added
(7) Catalog information The catalog information shows detailed information of the selected object, e.g. name, pro-
ducer, version and order information.
276 HB400 | CPU | M13-CCF0000 | en | 20-02

SPEED7 Studio - Hardware configuration - CPU
12.3 SPEED7 Studio - Hardware configuration - CPU

Precondition
For project engineering a thorough knowledge of the SPEED7 Studio is
required!
Proceeding 1. Start the SPEED7 Studio.

2. Create a new project in the Work area with ‘New project’ .
ð A new project is created and the view ‘Devices and networking’ is shown.
3. Click in the Project tree at ‘Add new device ...’ .
ð A dialog for device selection opens.
4. Select from the ‘Device templates’ your CPU and click at [OK].
ð The CPU is inserted in ‘Devices and networking’ and the ‘Device configuration’
is opened.
Device configuration
Slot Module ... ... ... ...

0 CPU M13-CCF0000
-X2 MPI interface
-X3 PG_OP_Ethernet
... ... ...
HB400 | CPU | M13-CCF0000 | en | 20-02 277

SPEED7 Studio - Hardware configuration - Ethernet PG/OP channel
12.4 SPEED7 Studio - Hardware configuration - Ethernet PG/OP channel

Overview
Please note!
project.
is supported.
sioning
Ethernet.
278 HB400 | CPU | M13-CCF0000 | en | 20-02

"Initialization" The assignment of IP address data takes place via the MAC address. The IP address of
your Ethernet PG/OP channel for the interfaces X3 and X4 can be found on the front of
your CPU with the name "MAC PG/OP: ...".
X3 PG/OP
X4 PG/OP
MAC PG/OP: 00-20-D5-77-05-10
The assignment of the IP address data happens online in the SPEED7 Studio with the
following proceeding:
1. Start the SPEED7 Studio with your project.
2. Click in the Project tree at ‘Devices and networking’ .
ð You will get a graphical object view of your CPU.
3. Click at the network ‘PG_OP_Ethernet’ .

4. Select ‘Context menu è Determine accessible partner’.
ð A dialog window opens.
HB400 | CPU | M13-CCF0000 | en | 20-02 279

5. Select the according network interface card, which is connected to the Ethernet
PG/OP channel and click at ‘Search’ to determine the via MAC address reachable
device.
ð The network search is started and the found stations are listed in a table.
6. Devices... IP... MAC... Device... ... ...
1 172.20. .. 00:20: ... VIPA ...
2 ... ... ...
Click in the list at the module with the known MAC address. This can be found at
the front of the CPU labelled as "MAC PG/OP: ...".
7. Click at ‘Set IP address’ . Now set the IP configuration by entering ‘IP address’ ,
‘Subnet mask’ and ‘Gateway’ . You get valid IP address parameters from your
system administrator.
8. Click at ‘Set IP address’ .
ð The IP address is transferred to the module and the list is refreshed. Directly
after the assignment the Ethernet PG/OP channel is online reachable using the
set IP address data. The value remains as long as it is reassigned, it is over-
written by a hardware configuration or a factory reset is executed.
9. With clicking at ‘Apply settings’ the IP address data are stored in the project.
Take IP address parame- If you are not online, you can assign IP address data to your Ethernet PG/OP channel
ters in project with following proceeding:
2. Click in the Project tree at ‘Devices and networking’ .
ð You will get a graphical object view of your CPU.
3. Click at the network ‘PG_OP_Ethernet’ .

4. Select ‘Context menu è Interface properties’.
ð A dialog window opens. Here you can enter the IP address data for your
Ethernet PG/OP channel.
5. Confirm with [OK].
ð The IP address data are stored in your project listed in ‘Devices and
networking’ at ‘Local components’ .
After transferring your project your CPU can be accessed via Ethernet PG/OP
channel with the set IP address data.
Local components
Slot Module ... ... ...IP address ...

0 CPU M13-CCF0000 ...
... ... ...
-X3 PG_OP_Ethernet 172.20.120.40
... ... ...
280 HB400 | CPU | M13-CCF0000 | en | 20-02

Deployment I/O periphery > Overview
12.5 SPEED7 Studio - Hardware configuration - I/O modules

Hardware configuration of 1. Click in the ‘Project tree’ at ‘PLC... > Device configuration’ .
the modules
2. Starting with slot 1 place in the ‘Device configuration’ yourSystem MICRO modules
in the plugged sequence. For this drag from the hardware catalog the corre-
sponding module to the corresponding position in the Device configuration.
Parametrization For parametrization double-click in the ‘Device configuration’ on the module you want to
parametrize. Then the parameters of the module are shown in a dialog. Here you can
make your parameter settings.
Parametrization during By using the SFCs 55, 56 and 57 you may alter and transfer parameters for wanted
runtime 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.
12.6 Deployment I/O periphery

12.6.1 Overview
Project engineering and n On this CPU the connectors for digital respectively analog signal and Technological
parametrization functions are combined in one casing.
n Die Project engineering happens in the VIPA SPEED7 Studio as CPU M13-CCF0000.
n For parametrization of the digital I/O periphery and the technological functions the
corresponding sub modules of the CPUM13-CCF0000 are to be used.
n The controlling of the operating modes of the technological functions happens by
means of handling blocks of the user program.
HB400 | CPU | M13-CCF0000 | en | 20-02 281

Deployment I/O periphery > Analog input
12.6.2 Analog input

12.6.2.1 Overview
n 2xUx12Bit (0 ... 10V)
n Sub module ‘AI2’
n Ä Chap. 5.3 ‘Analog input’ page 119
12.6.2.2 Parametrization in SPEED7 Studio

12.6.2.2.1 ‘I/O addresses’
Sub module Input address Access Assignment

AI2 800 WORD Analog input channel 0 (X4)
12.6.2.2.2 ‘Parameter’
‘Filtering channel 0/1’ The analog input part has a filter integrated. The parametrization of the filter happens via
the parameter ‘Filter channel 0/1’ . The default value of the filter is 1000ms. The following
values can be entered:
n 2ms: no filter
n 100ms: small filter
n 1000ms: medium filter
n 10000ms: maximum filter
282 HB400 | CPU | M13-CCF0000 | en | 20-02

Deployment I/O periphery > Digital output
12.6.3 Digital input

12.6.3.1 Overview
n 16xDC 24V
n Sub module ‘DI16/DO12’
n Ä Chap. 5.4 ‘Digital input’ page 122


12.6.3.2.2 ‘Inputs’
‘Trigger for process Here you can specify a hardware interrupt for each input in groups of 2 channels for the
interrupt’ corresponding edge. The hardware interrupt is disabled, if nothing is selected (default
setting). A diagnostics interrupt is only supported with Hardware interrupt lost.
Here is valid:
n Rising edge: Edge 0-1
n Falling edge: Edge 1-0
Input delay n The input delay can be configured per channel in groups of 4.
n An input delay of 0.1ms is only possible with "fast" inputs, which have a max. input
frequency of 100kHz Ä Chap. 5.4 ‘Digital input’ page 122. Within a group, the input
delay for slow inputs is limited to 0.5ms.
n Range of values: 0.1ms / 0.5ms / 3ms / 15ms
12.6.4 Digital output

12.6.4.1 Overview
n 12xDC 24V, 0.5A
n Sub module ‘DI16/DO12’
n Ä Chap. 5.5 ‘Digital output’ page 126

Sub module Output address Access Assignment

HB400 | CPU | M13-CCF0000 | en | 20-02 283

Deployment I/O periphery > Counter
12.6.5 Counter
12.6.5.1 Overview
n 4 channels
n Sub module: ‘Count’
n Ä Chap. 5.6 ‘Counting’ page 129


Count 816 DINT Channel 0: Counter value / Frequency value
12.6.5.2.2 Basic parameters

Select interrupt Via ‘Basic parameters’ you can reach ‘Select interrupt’ . Here you can define the inter-
n Process: The following events of the counter can trigger a hardware interrupt (select-
able via ‘Count’ ):
– Hardware gate opening
– Hardware gate closing
– On reaching the comparator
– on Counting pulse
– on overflow
– on underflow
rupt was lost.
12.6.5.2.3 ‘Channel x’
Operating mode Select via ‘Channel’ the channel select via ‘Operating’ the counter operating mode. The
following counter operating modes are supported:
n Not parametrized: Channel is de-activated
n Count endless
n Count once
n Count periodical
Counter
Operating mode Default values and structure of this dialog box depend on the selected ‘Operating mode’ .
284 HB400 | CPU | M13-CCF0000 | en | 20-02

Parameter overview

Main count direction n None No restriction of the counting range n None
n Up: Restricts the up-counting range. The counter starts
from 0 or load value, counts in positive direction up to
the declaration end value -1 and then jumps back to
load value at the next positive transducer pulse.
n Down: Restricts the down-counting range. The counter
starts from the declared start value or load value in
negative direction, counts to 1 and then jumps to start
value at the next negative encoder pulse. Function is
disable with count continuously.
Gate function n Cancel count: The count starts when the gate opens Abort count process
and resumes at the load value when the gate opens
again.
n Stop count: The count is interrupted when the gate
closes and resumed at the last actual counter value
when the gate opens again.
Start value Start value with counting direction backward. 2147483647 (231-1)
End value End value with main counting direction forward.
Range of values: 2...2147483647 (231-1)
Comparison value The count value is compared with the comparison value. 0
See also the parameter "Characteristics of the output":
n No main counting direction
– Range of values: -2)31 to +2)31-1
n Main counting direction forward
– Range of values: -231 to end value-1
n Main counting direction backward
– Range of values: 1 to +231-1
Hysteresis The hysteresis serves the avoidance of many toggle pro- 0
cesses of the output, if the counter value is in the range of
the comparison value.
0, 1: Hysteresis disabled
Range of values: 0 to 255
HB400 | CPU | M13-CCF0000 | en | 20-02 285

Input Description Assignment

Signal evaluation Specify the signal of the connected encoder: Pulse/direction
n Pulse/direction At the input count and direction signal
are connected
n At the input there is an encoder connected with the fol-
lowing evaluation:
– Rotary encoder single
– Rotary encoder double
– Rotary encoder quadruple
Hardware gate Gate control exclusively via channel 3: disabled
n enabled: The gate control for channel 3 happens via
SW and HW gate
n disabled: The gate control for channel 3 exclusively
happens via SW gate
Count direction inverted Invert the input signal ‘Direction’ : disabled
n enabled: The input signal is inverted
n disabled: The input signal is not inverted
Output Description Assignment

Characteristics of the output The output and the "Comparator" (STS_CMP) status bit No comparison
are set, dependent on this parameter.
n No comparison: The output is used as normal output
and STS_CMP remains reset.
n Comparator
– Counter value ³ Comparison value
– Counter value £ Comparison value
– To adapt the used actuators you can specify a
pulse duration. The output is set for the specified
pulse duration when the counter value reaches the
comparison value. When you've set a main
counting direction the output is only set at reaching
the comparison value from the main counting direc-
tion.
Pulse duration Here you can specify the pulse duration for the output 0
signal.
n The pulse duration starts with the setting of the
according digital output.
n The inaccuracy of the pulse duration is less than 1ms.
n There is no past triggering of the pulse duration when
the comparison value has been left and reached again
during pulse output.
n If the pulse duration is changed during operation, it will
take effect with the next pulse.
n If the pulse duration = 0, the output is set until the com-
parison condition is not longer fulfilled.
Range of values: 0...510ms in steps of 2ms
286 HB400 | CPU | M13-CCF0000 | en | 20-02

Frequency Description Assignment

Max. counting fre- Specify the max. frequency for track A/pulse, track B/direction, Latch 60kHz
quency and HW gate
1kHz 400µs
2kHz 200µs
5kHz 80µs
10kHz 40µs
30kHz 13µs
60kHz 6.7µs
100kHz 4µs

Hardware gate opening Hardware interrupt by edge 0-1 exclusively at HW gate disabled
channel 3
Hardware gate closing Hardware interrupt by edge 1-0 exclusively at HW gate disabled
channel 3
On reaching comparator Hardware interrupt on reaching comparator disabled
n enabled: Hardware interrupt when comparator is trig-
gered, can be configured via ‘Characteristics of the
output’
Overflow Hardware interrupt overflow disabled
n enabled: Hardware interrupt on overflow the upper
counter limit
Underflow Hardware interrupt on underrun disabled
n enabled: Hardware interrupt on underflow the lower
counter limit
HB400 | CPU | M13-CCF0000 | en | 20-02 287

Deployment I/O periphery > Frequency measurement
12.6.6 Frequency measurement

12.6.6.1 Overview
n 4 channels
n Sub module ‘Counter’
n Ä Chap. 5.7 ‘Frequency measurement’ page 151


Count 816 DINT Channel 0: Counter value / Frequency value

Count 816 DWORD reserved
820 DWORD reserved
824 DWORD reserved
828 DWORD reserved
12.6.6.2.2 Basic parameters

Select interrupt Via ‘Basic parameters’ you can reach ‘Select interrupt’ . Here you can define the inter-
n Process: The following events of the frequency measurement can trigger a hardware
interrupt (selectable via ‘Frequency counting’ ):
– End of measurement
rupt was lost.
12.6.6.2.3 ‘Channel x:’

Operating mode Select via ‘Channel’ the channel and select for frequency measurement via ‘Operating
mode’ the operating mode ‘Frequency counting’ . Default values and structure of this
dialog box depend on the selected ‘Operating mode’ . The following parameters are sup-
ported:
288 HB400 | CPU | M13-CCF0000 | en | 20-02

Deployment I/O periphery > Frequency measurement
1 Integration time
2 Counting pulse
3 SW gate
Parameter overview

Integration time Specify the integration time 100ms
Range of values: 10ms ... 10000ms in steps of 1ms
max. counting frequency ... Specify the max. frequency for the corresponding input 60kHz
1kHz 400µs
2kHz 200µs
5kHz 80µs
10kHz 40µs
30kHz 13µs
60kHz 6.7µs
100kHz 4µs

End of measurement Hardware interrupt at end of measurement de-activated
HB400 | CPU | M13-CCF0000 | en | 20-02 289

Deployment I/O periphery > Pulse width modulation - PWM
12.6.7 Pulse width modulation - PWM

12.6.7.1 Overview
n Sub module ‘Count’
n Ä Chap. 5.8 ‘Pulse width modulation - PWM’ page 157


Count 816 DINT reserved
820 DINT reserved
824 DINT reserved
828 DINT reserved

820 DWORD reserved
824 DWORD reserved
828 DWORD reserved
12.6.7.2.2 ‘Channel x’
Operating mode PWM and pulse train output use the same hardware configuration. Switching between
these modes is done within the SFB 49. Select via ‘Channel x’ the channel and select for
pulse width modulation via ‘Operating mode’ the operating mode ‘Pulse width
modulation’ Default values and structure of this dialog box depend on the selected
‘Operating mode’ . The following parameters are relevant for PWM, which must be speci-
fied or determined:
1 Period
2 On-delay
3 Pulse duration
4 Pulse pause
290 HB400 | CPU | M13-CCF0000 | en | 20-02

Deployment I/O periphery > Pulse width modulation - PWM
Parameter overview

n Per mil
n S7 Analog value:
27648
n 0.1ms: The time base is 0.1ms
n 1µs: The time base is 1µs
On-delay Enter here a value for the time to expire from the start of 0
the output sequence to the output of the pulse. The pulse
sequence is output at the output channel, on expiration of
the on-delay.
Range of values: 0 ... 65535 from this there are the fol-
lowing effective values:
n Time base 0.1ms: 0 ... 6553.5ms
n Time base 1µs: 0 ... 65535µs
Period With the period you define the length of the output 20000
pause.
Range of values:
n Time base 0.1ms: 0.4 ... 87.0ms
periphery.
Range of values:
n Time base 1ms: 0 ... Period / 2 * 1ms
n Time base 0.1ms: 2 ... Period / 2 * 0.1ms
n Time base 1µs: 0 ... Period / 2 * 1µs
HB400 | CPU | M13-CCF0000 | en | 20-02 291

Deployment I/O periphery > Pulse train
12.6.8 Pulse train

12.6.8.1 Overview
n 2 channels
n Sub module ‘Count’
n Ä Chap. 5.9 ‘Pulse train’ page 162


Count 816 DINT reserved
820 DINT reserved
824 DINT reserved
828 DINT reserved

820 DWORD reserved
824 DWORD reserved
828 DWORD reserved
12.6.8.2.2 ‘Channel x’
Operating mode PWM and pulse train output use the same hardware configuration. Switching between
these modes is done within the SFB 49. Select via ‘Channel x’ the channel and select for
pulse train via ‘Operating mode’ the operating mode ‘Pulse width modulation’ . Default
values and structure of this dialog box depend on the selected ‘Operating mode’ . The fol-
lowing parameters are relevant for pulse train, which must be specified or determined:
1 Number of pulses
2 Period duration
3 Pulse duration
4 Pulse pause
292 HB400 | CPU | M13-CCF0000 | en | 20-02

Deployment WebVisu - Web visualization
Parameter overview

n Per mil
n S7 Analog value:
27648
n 0.1ms: The time base is 0.1ms
n 1µs: The time base is 1µs
On-delay This parameter is ignored. 0
Period With the period you define the length of the output 50
pause.
Range of values:
n Time base 0.1ms: 0.4 ... 87.0ms
periphery.
Range of values:
n Time base 1ms: 0 ... Period / 2 * 1ms
n Time base 0.1ms: 2 ... Period / 2 * 0.1ms
n Time base 1µs: 0 ... Period / 2 * 1µs
12.7 Deployment OPC UA

12.8 Deployment WebVisu - Web visualization

Ä Chap. 7 ‘Deployment WebVisu - Web visualization’ page 201
HB400 | CPU | M13-CCF0000 | en | 20-02 293

SPEED7 Studio - Project transfer > Transfer via MPI
12.9 SPEED7 Studio - Project transfer

Overview There are the following possibilities for project transfer into the CPU:
n Transfer via MPI
12.9.1 Transfer via MPI

MPI programming cable The MPI programming cables are available at YASKAWA in different variants. 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.

3 MPI network
Proceeding transfer via 1. Connect your PC to the MPI jack of your CPU via a MPI programming cable.
MPI
2. Switch-ON the power supply of your CPU and start the SPEED7 Studio with your
project.
3. Set at ‘Active PC interface’ the "Serial interface".
294 HB400 | CPU | M13-CCF0000 | en | 20-02

SPEED7 Studio - Project transfer > Transfer via Ethernet
4. Click in the ‘Project tree’ to your project and select ‘Context menu è Recompile’.
ð Your project will be translated and prepared for transmission.
5. To transfer the user program and hardware configuration click in the Project tree at
your CPU and select ‘Context menu è Transfer all’.
ð A dialog window for project transfer opens
6. Select the ‘Port type’ "Serial interface" and start the transfer with ‘Transfer’ .
7. Confirm the request that the CPU is to be brought into the state STOP.
ð The user program and the hardware configuration are transferred via MPI to the
CPU.
8. Close after transmission the dialog.
9. With ‘Context menu è Copy RAM to ROM’ you can save your project on a memory
card, if one is plugged.

Proceeding transfer via For transfer via Ethernet the CPU has an Ethernet PG/OP channel. For online access to
Ethernet this, you have to assign IP address parameters to this by means of "initialization" and
transfer them into your project. For the transfer, connect, if not already done, the Ethernet
PG/OP channel jack to your Ethernet. The connection happens via an integrated 2-port
switch (X3, X4).
1. Switch-ON the power supply of your CPU and start the SPEED7 Studio with your
project.
2. Set at ‘Active PC interface’ the "Ethernet interface".
3. Click in the ‘Project tree’ to your project and select ‘Context menu è Recompile’.
ð Your project will be translated and prepared for transmission.
HB400 | CPU | M13-CCF0000 | en | 20-02 295

SPEED7 Studio - Project transfer > Transfer via memory card
4. To transfer the user program and hardware configuration click in the Project tree at
your CPU and select ‘Context menu è Transfer all’.
ð A dialog window for project transfer opens
5. Select the ‘Port type’ "Ethernet interface" and start the transfer with ‘Transfer’ .
6. Confirm the request that the CPU is to be brought into the state STOP.
ð The user program and the hardware configuration are transferred via Ethernet
to the CPU.
7. Close after transmission the dialog.
8. With ‘Context menu è Copy RAM to ROM’ you can save your project on a memory
card, if one is plugged.

Proceeding transfer via The memory card serves as external storage medium. There may be stored several proj-
memory card ects and sub-directories on a memory card. Please regard that your current project is
n S7PROG.WLD
n AUTOLOAD.WLD
2. Click in the ‘Project tree’ at the CPU.
3. Create in the SPEED7 Studio with ‘Context menu
è Export device configuration (WLD)’ a wld file.
ð The wld file is created. This contains the user program and the hardware config-
uration
296 HB400 | CPU | M13-CCF0000 | en | 20-02

SPEED7 Studio - Project transfer > Transfer via memory card
again.
HB400 | CPU | M13-CCF0000 | en | 20-02 297

Configuration with TIA Portal VIPA System MICRO
TIA Portal - Work environment > General
13 Configuration with TIA Portal

13.1 TIA Portal - Work environment
13.1.1 General
General In this chapter the project engineering of the VIPA CPU in the Siemens TIA Portal is
shown. Here only the basic usage of the Siemens TIA Portal together with a VIPA CPU is
shown. Please note that software changes can not always be considered and it may thus
be deviations to the description. TIA means Totally integrated Automation from Siemens.
Here your VIPA PLCs may be configured and linked. For diagnostics online tools are
available.
Information about the Siemens TIA Portal can be found in the online help
respectively in the according online documentation.
Starting the TIA Portal To start the Siemens TIA Portal with Windows select ‘Start è Programs
è Siemens Automation è TIA ...’
Then the TIA Portal opens with the last settings used.
Exiting the TIA Portal With the menu ‘Project è Exit’ in the ‘Project view’ you may exit the TIA Portal. Here
there is the possibility to save changes of your project before.
298 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO Configuration with TIA Portal
TIA Portal - Work environment > Work environment of the TIA Portal
13.1.2 Work environment of the TIA Portal

Basically, the TIA Portal has the following 2 views. With the button on the left below you
can switch between these views:
Portal view The ‘Portal view’ provides a "task oriented" view of the tools for processing your project.
Here you have direct access to the tools for a task. If necessary, a change to the Project
view takes place automatically for the selected task.
Project view The ‘Project view’ is a "structured" view to all constituent parts of your project.
Areas of the Project view The Project view is divided into the following areas:
1 Menu bar with toolbars

2 Project tree with Details view
3 Project area
4 Device overview of the project respectively area for block programming
5 Properties dialog of a device (parameter) respectively information area
6 Hardware catalog and tools
7 "Task-Cards" to select hardware catalog, tasks and libraries
8 Jump to Portal or Project view
HB400 | CPU | M13-CCF0000 | en | 20-02 299

TIA Portal - Hardware configuration - CPU
13.2 TIA Portal - Functional limitations

Limitation of performance Please note that the performance data of the VIPA CPU is limited to the performance
data data of the Siemens CPU used for the configuration.
No ‘Upload device as new Due to the system ‘Upload device as new station...’ is currently not supported. Instead,
station...’ use the backup and restore functions in the Siemens TIA Portal:
1. To backup an online connected CPU, select ‘Online è Backup from online device’.
ð A backup object is created and stored in the project navigation at ‘Online
backups’ . The backup contains all blocks of the project and the current device
status.
2. To restore into an online connected CPU it must be overall reset first. Then click in
the project navigation under ‘Online backups’ on the created backup and select
‘Context menu è Download to device’.
ð The backup data is transferred online to the CPU.
No online blocks Due to the system, online blocks of CPUs connected via ‘Accessible devices’ are cur-
rently not listed.
13.3 TIA Portal - Hardware configuration - CPU

Overview The hardware configuration of the CPU happens in the Siemens TIA Portal by means of a
virtual PROFINET IO device. For the PROFINET interface is standardized software sided,
the functionality is guaranteed by including a GSDML file into the Siemens TIA Portal.
The hardware configuration of the CPU is divided into the following parts:
n Installation GSDML ‘VIPA MICRO PLC’ for PROFINET
n Configuration Siemens CPU
n Connection ‘VIPA MICRO PLC’ as PROFINET IO device
Installation GSDML CPU The installation of the PROFINET IO devices ‘VIPA MICRO PLC’ happens in the hard-
for PROFINET ware catalog with the following approach:
1. Go to the service area of www.vipa.com.
2. Load from the download area at ‘Config files è PROFINET’ the according file for
your System MICRO.
3. Extract the file into your working directory.
4. Start the Siemens TIA Portal.
5. Close all the projects.
6. Switch to the Project view.
7. Select ‘Options è Install general station description file (GSD)’.
8. Navigate to your working directory and install the according GSDML file.
ð After the installation the hardware catalog is refreshed and the Siemens TIA
Portal is finished.
After restarting the Siemens TIA Portal the according PROFINET IO device can
be found at Other field devices > PROFINET > IO > VIPA ... > VIPA Micro
System.
300 HB400 | CPU | M13-CCF0000 | en | 20-02

Thus, the VIPA components can be displayed, you have to deactivate the
"Filter" of the hardware catalog.
Configuration CPU With the Siemens TIA Portal, the CPU from VIPA is to be configured as CPU 314C-2
PN/DP (314-6EH04-0AB0 V3.3) from Siemens.
2. Create a new project in the Portal view with ‘Create new project’ .
4. Click in the Project tree at ‘Add new device’ .
5. Select the following CPU in the input dialog:
SIMATIC S7-300 > CPU 314C-2 PN/DP (314-6EH04-0AB0 V3.3)
ð The CPU is inserted with a profile rail.
Device overview:
Module ... Slot ... Type ...

PLC ... 2 CPU 314C-2PN/DP
MPI interface... 2 X1 MPI/DP interface
PROFINET inter- 2 X2 PROFINET interface
face
DI24/DO16 25 DI24/DO16
AI5/AO2... 26 AI5/AO2
Counter... 27 Counter
...
HB400 | CPU | M13-CCF0000 | en | 20-02 301

– For parametrization of the digital I/O periphery and the technological

functions the corresponding sub modules of the CPU 314C-2 PN/DP
(314-6EH04-0AB0 V3.3) is to be used.
– The controlling of the operating modes of the technological functions
happens by means of handling blocks of the user program.
Setting standard CPU Since the CPU from VIPA is configured as Siemens CPU, so the setting of the non- VIPA
parameters specific parameters takes place via the Siemens CPU. For parametrization click in the
Project arearespectively in the Device overview at the CPU part. Then the parameters of
the CPU part are shown in the Properties dialog. Here you can make your parameter set-
tings. Ä Chap. 4.8 ‘Setting standard CPU parameters’ page 77
Connection CPU as 1. Switch in the Project area to ‘Network view’ .

PROFINET IO device
2. After installing the GSDML the IO device for the CPU may be found in the hardware
catalog at Other field devices > PROFINET > IO > VIPA ... > VIPA MICRO PLC.
Connect the slave system to the CPU by dragging&dropping it from the hardware
catalog to the Network view and connecting it via PROFINET to the CPU.
3. Click in the Network view at the PROFINET part of the Siemens CPU and enter at
valid IP address data in ‘Properties’ at ‘Ethernet address’ in the area ‘IP protocol’ .
4. Enter at ‘PROFINET’ a ‘PROFINET device name’ . The device name must be
unique at the Ethernet subnet.
5. Select in the Network view the IO device ‘VIPA MICRO PLC’ and switch to the
Device overview.
ð In the Device overview of the PROFINET IO device ‘VIPA MICRO PLC’ the
CPU is already placed at slot 0. From slot 1 you can place your Extension
module.
302 HB400 | CPU | M13-CCF0000 | en | 20-02

TIA Portal - Hardware configuration - Ethernet PG/OP channel
Setting VIPA specific CPU For parametrization click at the CPU at slot 0 in the Device overview of the PROFINET IO
parameters device ‘VIPA MICRO PLC’ . Then the parameters of the CPU part are shown in the Prop-
erties dialog. Here you can make your parameter settings. Ä Chap. 4.9 ‘Setting VIPA
specific CPU parameters’ page 82
13.4 TIA Portal - Hardware configuration - Ethernet PG/OP channel

Overview
Please note!
project.
is supported.
sioning
Ethernet.
HB400 | CPU | M13-CCF0000 | en | 20-02 303

TIA Portal - Hardware configuration - Ethernet PG/OP channel
"Initialization" The assignment of IP address data takes place via the MAC address. The IP address of
your Ethernet PG/OP channel for the interfaces X3 and X4 can be found on the front of
your CPU with the name "MAC PG/OP: ...".
X3 PG/OP
X4 PG/OP
MAC PG/OP: 00-20-D5-77-05-10
"Initialization" The assignment of the IP address data happens online in the Siemens TIA Portal with the
following proceeding:
2. Switch to the ‘Project view’ .
3. Click in the ‘Project tree’ at ‘Online access’ and choose here by a doubleclick your
network card, which is connected to the Ethernet PG/OP channel.
4. To get the stations and their MAC address, use the ‘Accessible device’ . This can
be found at the front of the CPU labelled as "MAC PG/OP: ...".
5. Choose from the list the module with the known MAC address (Onboard PG/OP
[MAC address]) and open with "Online & Diagnostics" the diagnostics dialog in the
Project area.
6. Navigate to Functions > Assign IP address. Type in the IP configuration like IP
address, subnet mask and gateway.
ð Directly after the assignment the Ethernet PG/OP channel is online reachable
using the set IP address data. The value remains as long as it is reassigned, it
is overwritten by a hardware configuration or an factory reset is executed.
304 HB400 | CPU | M13-CCF0000 | en | 20-02

TIA Portal - Hardware configuration - Ethernet PG/OP channel > Take IP address parameters in project
Due to the system you may get a message that the IP address could not
be assigned. This message can be ignored.
13.4.1 Take IP address parameters in project

2 variants for configura- From firmware version V2.4.0 and up, you have the following options for configuring the
tion Ethernet PG/OP channel:
n Configuration via integrated CPU interface (firmware version V2.4.0 and up only).
n Configuration via additional CP (all firmware versions).
13.4.1.1 Configuration via integrated CPU interface

Proceeding From firmware version V2.4.0 this variant for configuration is recommended. The fol-
lowing advantages result:
n The configuration becomes clearer, because the periphery modules and the
PROFINET IO devices are configured on the PROFINET line of the CPU and no addi-
tional CP is to be configured.
n There are no address collisions, because the S7 addresses for all components are
assigned from the address area of the CPU.
Unless during the hardware configuration of the CPU Ä 300 there was no IP address
data assigned yet or these are to be changed, the configuration happens to the following
proceeding, otherwise the Ethernet PG/OP channel is configured.
1. Open the Siemens TIA Portal and, if not already done, configure the Siemens CPU
314C-2 PN/DP (314-6EH04-0AB0 V3.3).
2. Click in the Network view at the PROFINET part of the Siemens CPU and enter the
previous assigned IP address data and subnet in ‘Properties’ at ‘Ethernet address’
in the area ‘IP protocol’ . The IP address data are not accepted without subnet
assignment!

already configured.
1. In the ‘Device configuration’ , click at ‘PROFINET interface’ of the Siemens CPU
and open the ‘Properties’ dialog.
2. In the ‘Properties’ , select ‘Time-of-day synchronization’ .
3. Enable the NTP method.
4. Add the appropriate NTP servers by specifying their IP addresses.
synchronized once.
HB400 | CPU | M13-CCF0000 | en | 20-02 305



13.4.1.2 Configuration via additional CP

Proceeding This is the conventional variant for configuration and is supported by all firmware ver-
sions. If possible, always use the configuration via the internal interface, otherwise the fol-
lowing disadvantages result:
n Address overlaps are not recognized in the Siemens TIA Portal.
n For PROFINET devices only the address range 0 ... 1023 is available.
n The addresses of the PROFINET devices are not checked with the address space of
the CPU from the Siemens TIA portal for address overlaps.
The configuration happens according to the following procedure:
1. Open your project.
2. If not already done, configure in the ‘Device configuration’ a Siemens CPU 314C-2
PN/DP (314-6EH04-0AB0 V3.3).
3. As Ethernet PG/OP channel place at slot 4 the Siemens CP 343-1 (6GK7
343-1EX30 0XE0 V3.0).
CAUTION!
Please configure the diagnostic addresses of the CP343-1EX30 for
‘PN-IO’ , ‘Port1’ and ‘Port2’ so that no overlaps occur in the
periphery input area. Otherwise your CPU can not start-up and you
receive the diagnostic entry 0xE904. Address overlaps are not rec-
ognized in the Siemens TIA Portal.
4. Open the ‘Property’ dialog by clicking on the CP 343-1EX30 and enter for the CP
at ‘Properties’ at ‘Ethernet address’ the IP address data and subnet, which you
have assigned before. The IP address data are not accepted without subnet assign-
ment!
306 HB400 | CPU | M13-CCF0000 | en | 20-02

Device overview

PLC ... 2 CPU 314C-2 PN/DP
MPI/DP interface 2 X1 MPI/DP interface
face
... ... ...
CP 343-1 4 CP 343-1
... ... ...

already configured.
1. In the ‘Device configuration’ , click the CP 343-1EX30.
2. Click on ‘PROFINET interface’ in the ‘Device overview’ .
3. In the ‘Properties’ , select ‘Time-of-day synchronization’ .
4. Enable the NTP method by enabling ‘Activate time-of-day synchronization’ and
selecting ‘NTP’ at ‘Method’ .
5. Add the appropriate NTP servers by specifying their IP addresses.
6. Select your ‘Time zone’ . In the NTP method, UTC (Universal Time Coordinated) is
generally transmitted; this corresponds to GMT (Greenwich Mean Time). By config-
uring the local time zone, you can set a time offset to UTC.
synchronized once.
HB400 | CPU | M13-CCF0000 | en | 20-02 307

TIA Portal - Hardware configuration - I/O modules


13.5 TIA Portal - Hardware configuration - I/O modules

Hardware configuration of Starting with slot 1 place in the Device overview of the PROFINET IO device ‘VIPA Micro
the modules CPU’ your System Micro modules in the plugged sequence. For this drag from the hard-
ware catalog the corresponding module to the corresponding position in the Device over-
view.
Parametrization To provide specific addressing of the installed peripheral modules, certain addresses
must be allocated in the CPU. For parametrization click in the Device overview at the
module you want to parametrize. Then the parameters of the module are shown in the
Properties dialog. Here you can make your parameter settings.
308 HB400 | CPU | M13-CCF0000 | en | 20-02

TIA Portal - Deployment PG/OP communication - PROFINET > Deployment as PROFINET IO controller
13.6 TIA Portal - Deployment PG/OP communication - PROFINET

your system and due to the system the cycle time of the OB 1 is
extended by 2ms.
13.6.1 Deployment as PROFINET IO controller

13.6.1.1 Steps of configuration
Range of functions
explicitly.
The configuration of the PROFINET IO controller for PROFINET communication should

be done by the following procedure:
1. Commissioning and Initialization (assignment IP address data)
2. Hardware configuration - CPU
3. Configuration PROFINET IO controller
4. Configuration PROFINET IO device
With the Siemens TIA Portal, the VIPA CPU M13-CCF0000 is to be con-
figured as
CPU 314C-2 PN/DP (314-6EH04-0AB0 V3.3)!
13.6.1.2 Commissioning and initialization

sioning
2. Wire the system by connecting cables for voltage supply and signals
3. Connect your PROFINET IO controller with Ethernet.
ð After a short boot time, the CP is in idle.
At the first commissioning respectively after an overall reset of the CPU, the
PROFINET IO controller has no IP address.
HB400 | CPU | M13-CCF0000 | en | 20-02 309

Assign IP address param- This function is supported only if the PROFINET IO controller is not yet configured. You
eters get valid IP address parameters from your system administrator. The assignment of the
IP address data happens online in the Siemens TIA Portal with the following proceeding:
2. Switch to the ‘Project view’ .
3. Click in the ‘Project tree’ at ‘Online access’ and choose here by a doubleclick your
network card, which is connected to the PROFINET interface.
4. To get the stations and their MAC address, use the ‘Accessible device’ . This can
be found at the front of the CPU labelled as "MAC ETH: ...".
5. Choose from the list the module with the known MAC address and open with
"Online & Diagnostics" the diagnostics dialog in the Project area.
6. Navigate to Functions > Assign IP address. Type in the IP configuration like IP
address, subnet mask and gateway.
ð Directly after the assignment the PROFINET IO controller is online reachable
using the set IP address data. The hardware configuration allows you to transfer
the IP address data to your project. Ä Chap. 13.3 ‘TIA Portal - Hardware config-
uration - CPU’ page 300
13.6.1.3 Configuration PROFINET IO controller

13.6.1.3.1 Proceeding
Precondition To parametrize the PROFINET IO controller of the CPU, the following conditions must be
fulfilled:
n The PROFINET IO controller is online reachable, this means an initialization was
established.
n The hardware configuration described before was established and the PROFINET IO
controller is networked.
Proceeding
1. For parametrization click in the Project area at the CPU part.
2. Click on ‘PROFINET interface’ in the Device overview.
ð The parameters of the PROFINET interface are listed in the properties dialog.
310 HB400 | CPU | M13-CCF0000 | en | 20-02

3. Open the properties dialog of the PROFINET IO controller by a double-click at PN-

IO.
n The PROFINET interface of the PROFINET IO controller is parametrized with
‘PROFINET interface_...’ .
n With ‘Port_1’ the port of the PROFINET interface of the PROFINET IO con-
troller is parametrized.
Device overview

PLC ... 2 CPU 314C-2 PN/DP
MPI/DP interface 2 X1 MPI/DP interface
face
... ... ...
13.6.1.3.2 PROFINET interface

General n Name
– Here you can change the name of the interface.
n Comment
– Here you can describe the interface in more detail.
Time-of-day synchroniza- n NTP method

tion – In this area you can configure time-of-day master for time-of-day synchronization
in the network.
HB400 | CPU | M13-CCF0000 | en | 20-02 311

Ethernet address n Interface networked with

– Here you can connect the PROFINET interface to the desired subnet.
n IP protocol
– Here you can specify the IP address, subnet mask and gateway for the
PROFINET interface.
n PROFINET
– Here you can specify a ‘PROFINET device name’ . On the Ethernet subnet, the
‘PROFINET device name’ must be unique. For an integrated PROFINET inter-
face the ‘PROFINET device name’ is derived from the short description. You can
change this at any time.
Operating mode n Operating mode

– You should not change anything here, as the settings for using the PROFINET IO
controller as an I-Device are not relevant.
PROFINET interface - Advanced options

Interface Options n Support device replacement without exchangeable medium
– This parameter is not evaluated. With configured topology the device replacement
without exchangeable medium is supported.
PROFINET interface - Advanced options Port ...1

General n Name
– Here you can change the name of the port, which is also shown in the configura-
tion table.
n Comment
– Here you can describe the port in more detail. The comment also appears in the
configuration table.
Port interconnection These parameters serve for the port setting of the topology.
Port options These parameters serve for the port setting. Here the following parameters are sup-
ported:
n Connection
– Here you can make settings for transmission medium and type. Ensure that the
setting for the local port and the partner port are identical.
– PROFINET requires 100Mbps in duplex mode.
n Boundaries
– Boundaries are limitations for the transfer of certain Ethernet frames. The fol-
lowing Boundaries are supported:
‘End of detection of accessible nodes’ : DCP frames for detecting accessible
nodes are not forwarded. When enabled, participants which are lying behind this
port, are no longer recognized and can not be reached by the controller.
‘End of topology discovery’ : When activated, this port does not support topology
detection, i.e. the LLDP telegrams are not forwarded.
312 HB400 | CPU | M13-CCF0000 | en | 20-02

Diagnostic addresses n Start address

– The CPU reports errors of the IO controller via the ‘Start address’ , as soon as
e.g. an error during synchronization of the IO controller occurs. This address is
also used to identify the IO system to which the device belongs, if an IO device
fails.
13.6.1.4 Configuration PROFINET IO device

Precondition n The modules, which may be configured here are listed in the hardware catalog.
n For the deployment of the PROFINET IO devices from VIPA you have to include the
modules into the hardware catalog by means of the GSDML file from VIPA.
n After the installation of the GSDML file the PROFINET IO devices from VIPA may be
found in the hardware catalog at Additional field devices > PROFINET > IO > VIPA ...
> VIPA Micro System
Thus, the VIPA components can be shown, you have to deactivate the
"Filter" of the hardware catalog.
HB400 | CPU | M13-CCF0000 | en | 20-02 313

TIA Portal - Option: Deployment PROFIBUS communication > Fast introduction
Configure IO devices Now the project engineering of the PROFINET IO controller is finished. Please link up
now your IO devices with periphery to your IO controller.
1. For the project engineering of the PROFINET IO device you search the concerning
PROFINET IO device in the hardware catalog at PROFINET-IO and drag&drop it in
the subnet of your IO controller.
2. Assign a name to the IO device. The configured name must match the name of the
device. Information about setting the device name can be found in the manual of
the IO device.
3. Enter a valid IP address. The IP address is normally assigned automatically by the
hardware configurator. If this is not desired, you can assign the IP address man-
ually.
4. Link up the modules of your IO device in the plugged sequence and add the
addresses that should be used by the modules.
5. If needed, parametrize the modules.
6. Save, compile and transfer your project. Ä Chap. 13.10 ‘TIA Portal - Project
transfer’ page 321
Device overview

...IO device.. ... 0 ... ...IO device.. ...
... ... 0 ... ... ...
Module ... 1 ... Periphery modules ...
... ... 2 ... ... ...
... ... ... ... ... ...
13.7 TIA Portal - Option: Deployment PROFIBUS communication

13.7.1 Fast introduction
Overview For the PROFIBUS communication the use of the optionally available extension module
EM M09 is required. The extension module provides interface X2: MPI(PB) with fixed pin
assignment. Ä Chap. 2.4 ‘Mounting’ page 16 The PROFIBUS DP slave is to be config-
ured in the Project view from Siemens. Here the configuration happens by the sub
module X1 (MPI/DP) of the Siemens CPU.
314 HB400 | CPU | M13-CCF0000 | en | 20-02

TIA Portal - Option: Deployment PROFIBUS communication > Fast introduction

Steps of configuration The configuration of the PROFIBUS DP slave should be done with the following
approach:
n Activating bus functionality by means of a VSC
n Use as DP slave
– With activating the bus functionality ‘PROFIBUS DP slave’ by means of a VSC,
the bus functionality ‘PROFIBUS DP slave’ is unlocked.
n Transfer of the entire project to the CPU
With the Siemens TIA Portal, the CPU M13-CCF0000 from VIPA is to be
configured as
CPU 314C-2 PN/DP (314-6EH04-0AB0 V3.3)
The PROFIBUS DP slave is to be configured and connected via the sub
module X1 (MPI/DP).
HB400 | CPU | M13-CCF0000 | en | 20-02 315

TIA Portal - Option: Deployment PROFIBUS communication > PROFIBUS communication via extension module EM M09
13.7.2 PROFIBUS communication via extension module EM M09

X2 MPI(PB)
The interface supports the following functionalities, which are switch able by an hardware
configuration:
n PROFIBUS DP slave (option)
the sub module ‘MPI/DP’ of the CPU in the hardware configuration.
Enable PROFIBUS func- The activation of the PROFIBUS functionality of the extension module EM M09 happens
tionality with the following proceeding:

To switch the interface X2 MPI(PB) to PROFIBUS functionality

you have to activate the according bus functionality by means
of a VSC storage media from VIPA. By plugging the VSC
storage card and then an overall reset the according function-
ality is activated. Ä Chap. 4.16 ‘Deployment storage media -
VSD, VSC’ page 110
316 HB400 | CPU | M13-CCF0000 | en | 20-02

TIA Portal - Option: Deployment PROFIBUS communication > Hardware configuration - CPU
1 RS485 interface
2 Periphery
Never connect the cable shield and the M5V (pin 5) together, since the
interfaces could be destroyed!
Status indication
DE
green n Slave is in DE (data exchange).
n Slave exchanges data with the master.
green blinking n Slave CPU is in state start-up.
n Slave-CPU is without master.
n There is no power supply.
n Slave has no configuration.
13.7.3 Hardware configuration - CPU

Perform a hardware configuration for the CPU. Ä Chap. 13.3 ‘TIA Portal - Hardware con-
figuration - CPU’ page 300
HB400 | CPU | M13-CCF0000 | en | 20-02 317

TIA Portal - Option: Deployment PROFIBUS communication > Deployment as PROFIBUS DP slave
13.7.4 Deployment as PROFIBUS DP slave

Fast introduction In the following the deployment of the PROFIBUS section as "intelligent" DP slave on
master system is described, which exclusively may be configured in the Siemens TIA
Portal. The following steps are required:
1. Configure a station with a CPU with operating mode DP slave.
2. Connect to PROFIBUS and configure the in-/output area for the slave section.
3. Save and compile your project.
4. Configure another station with another CPU with operating mode DP master.
5. Connect to PROFIBUS and configure the in-/output ranges for the master section.
Configuration of the 1. Start the Siemens TIA Portal and configure a CPU.
master part
2. Designate the station as "... DP master".
3. Integrate the modules according to the hardware configuration of the master
system.
4. Select the PROFIBUS interface of the master CPU and select ‘Context menu
è Properties’.
ð The ‘Properties’ dialog is shown.
5. Set at interface: Type "PROFIBUS".
6. Connect to PROFIBUS and preset an address (e.g. 2).
7. Switch at Operating mode to "DP master".
Configuration of the slave 1. Configure a Siemens CPU 314C-2 PN/DP (314-6EH04-0AB0 V3.3) as another CPU
part Ä Chap. 13.3 ‘TIA Portal - Hardware configuration - CPU’ page 300
2. Designate the station as "... DP slave".
3. Integrate your modules according to your hardware configuration.
4. Select the PROFIBUS interface of your CPU and select ‘Context menu
è Properties’.
ð The ‘Properties’ dialog is shown.
5. Set at interface: Type "PROFIBUS".
6. Connect to PROFIBUS and preset an address (e.g. 3).
7. Switch at ‘Operating mode’ to "DP slave".
8. Under ‘Assigned DP master’ , select your master system.
9. Use ‘Transfer area’ to define the I/O address areas of the slave CPU that are to be
assigned to the DP slave.
10. Save, translate and transfer the respective project into the corresponding master or
slave CPU.
318 HB400 | CPU | M13-CCF0000 | en | 20-02

Deployment OPC UA
13.8 Deployment OPC UA

HB400 | CPU | M13-CCF0000 | en | 20-02 319

TIA Portal - VIPA-Include library
13.9 TIA Portal - VIPA-Include library

Overview n The VIPA specific blocks can be found in the "Service" area of www.vipa.com as
library download file at Downloads > VIPA LIB.
n The library is available as packed zip file for the corresponding TIA Portal version.
n As soon as you want to use VIPA specific blocks you have to import them into your
project.
Execute the following steps:
– Load an unzip the file ...TIA_Vxx.zip (note TIA Portal version)
– Open library and transfer blocks into the project
Unzip ...TIA_Vxx.zip Start your un-zip application with a double click on the file TIA_Vxx.zip and copy all the
files and folders in a work directory for the Siemens TIA Portal.
Open library and transfer 1. Start the Siemens TIA Portal with your project.
blocks into the project
3. Choose "Libraries" from the task cards on the right side.
4. Click at "Global libraries".
5. Click at "Open global libraries".
6. Navigate to your directory and load the file ...TIA.alxx.
7. Copy the necessary blocks from the library into the "Program blocks" of the Project
tree of your project. Now you have access to the VIPA specific blocks via your user
application.
320 HB400 | CPU | M13-CCF0000 | en | 20-02

TIA Portal - Project transfer > Transfer via memory card
13.10 TIA Portal - Project transfer

Overview There are the following possibilities for project transfer into the CPU:
n Option: Transfer via MPI

Transfer via Ethernet For transfer via Ethernet the CPU has the following interface:
n X3/X4: Ethernet PG/OP channel via an integrated 2-port switch
Initialization So that you may the according Ethernet interface, you have to assign IP address parame-
ters by means of the "initialization". Ä Chap. 13.4 ‘TIA Portal - Hardware configuration -
Ethernet PG/OP channel’ page 303
Please consider to use the same IP address data in your project for the CP 343-1.
Transfer 1. For the transfer, connect, if not already done, the appropriate Ethernet jack to your
Ethernet.
2. Open your project with the Siemens TIA Portal.
3. Click in the Project tree at Online access and choose here by a double-click your
network card, which is connected to the Ethernet PG/OP interface.
4. Select in the Project tree your CPU and click at [Go online].
5. Set the access path by selecting "PN/IE" as type of interface, your network card and
the according subnet. Then a net scan is established and the corresponding station
is listed.
6. Establish with [Connect] a connection.
7. Click to ‘Online è Download to device’.
ð The according block is compiled and by a request transferred to the target
device. Provided that no new hardware configuration is transferred to the CPU,
the entered Ethernet connection is permanently stored in the project as transfer
channel.

Proceeding The memory card serves as external storage medium. There may be stored several proj-
ects and sub-directories on a memory card. Please regard that your current project is
n S7PROG.WLD
n AUTOLOAD.WLD
1. Start the Siemens TIA Portal with your project.
2. Create a wld file with ‘Project è Memory card file è New’.
ð The wld file is shown in the Project tree at "SIMATIC Card Reader" as "Memory
card file".
3. Copy the blocks from the Program blocks to the wld file. Here the hardware configu-
ration data are automatically copied to the wld file as "System data".
HB400 | CPU | M13-CCF0000 | en | 20-02 321

TIA Portal - Project transfer > Option: Transfer via MPI
again.
13.10.3 Option: Transfer via MPI


3 MPI network
Proceeding enabling the A hardware configuration to enable the MPI interface is not necessary. By installing the
interface extension module EM M09 the MPI interface is enabled.
322 HB400 | CPU | M13-CCF0000 | en | 20-02

TIA Portal - Project transfer > Option: Transfer via MPI

Proceeding transfer via Currently the VIPA programming cables for transfer via MPI are not supported. This is
MPI interface only possible with the programming cable from Siemens. 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.
1. Establish a connection to your extension module via MPI with an appropriate pro-
gramming cable. Information may be found in the corresponding documentation of
the programming cable.
2. Start the Siemens TIA Portal with your project.
3. Select in the Project tree your CPU and choose ‘Context menu
è Download to device è Hardware configuration’ to transfer the hardware configu-
ration.
4. To transfer the PLC program choose ‘Context menu è Download to device
è Software’. Due to the system you have to transfer hardware configuration and
PLC program separately.
HB400 | CPU | M13-CCF0000 | en | 20-02 323

Appendix VIPA System MICRO
Appendix
324 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO Appendix
Content
A System specific event IDs.............................................................................. 326

B Integrated blocks............................................................................................ 378
C SSL partial list................................................................................................. 381
HB400 | CPU | M13-CCF0000 | en | 20-02 325

System specific event IDs VIPA System MICRO
A System specific event IDs

Event IDs Ä Chap. 4.20 ‘Diagnostic entries’ page 116
Event ID Description
0x115C Manufacture interrupt (OB 57) for EtherCAT
OB: OB number
ZINFO1: Input / Output address
ZINFO2: Interrupt type
0: Reserved
1: Diagnostic interrupt (incoming)
2: Process interrupt
3: Pull interrupt
4: Plug interrupt
5: Status interrupt
6: Update interrupt
7: Redundancy interrupt
8: Controlled by the supervisor
9: Enabled
10: Wrong sub module plugged
11: Recovery of the sub module
12: Diagnostic interrupt (outgoing)
13: Cross traffic connection message
14: Neighbourhood change message
15: Synchronisation message (bus)
16: Synchronisation message (device)
17: Network component message
18: Clock synchronisation message (bus)
31: Pull interrupt component
32: Vendor-specific interrupt min.
33: Vendor-specific interrupt topology change
127: Vendor-specific interrupt max.
ZINFO3: CoE error code
DatID: Input
DatID: Output
0x38D0 Bus recovery
0: OB
PK: Priority class
ZINFO1: Logical address of the IO system
ZINFO2: Logical address of the virtual device
326 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO System specific event IDs
ZINFO3 - Position 0: Station number
ZINFO3 - Position 11: IO system ID
ZINFO3 - Bit 15: System ID DP/PN
0x38D1 Bus recovery, but expected configuration does not match actual configuration
0: OB
PK: Priority class
0x39D0 Bus failure
OB: OB number
PK: Priority class
0x454B STOP: Maximum number of time-outs of a synchronous OB reached
OB: CPU mode
PK:
ZINFO1: ZInfo1
ZINFO2: ZInfo2
ZINFO3: ZInfo3
DatID: Block type
0x49CA PROFINET IO system failure (Watchdog)
0: OB
1: Cyclic program (OB 1)
16: Time of day interrupt OB (OB 16)
17: Time of day interrupt OB (OB 17)
32: Cyclic interrupt OB (OB 32)
HB400 | CPU | M13-CCF0000 | en | 20-02 327

64: Synchronous cycle interrupt (OB 64)
65: Synchronous technology interrupt (OB 65)
80: Time error OB (OB 80)
81: Power supply error OB (OB 81)
82: Diagnostic interrupt OB (OB 82)
83: Plug/Pull OB (OB 83)
85: Program sequence error OB (OB 85)
86: Component rack failure OB (OB 86)
PK: Priority class
ZINFO2: Interrupt reason
0: Unknown
1: Alarm overflow
2: Message box overflow
3: Cyclic data not in bus cycle
4: Application bus cycle error
5: Watchdog
6: Error handler
7: Time-out when receiving cyclic data
8: No not-IO-task available
0xE003 Error in access to periphery
ZINFO1: Transfer type
ZINFO2: Periphery address
ZINFO3: Slot
0xE004 Multiple configuration of a periphery address
ZINFO2: Slot
0xE005 Internal error - Please contact the hotline!
ZINFO1: Not user relevant
0xE007 Configured input/output bytes do not fit in the periphery area
0xE009 Error on accessing the standard backplane bus
0xE010 Non-defined component recognised at the standard backplane bus
328 HB400 | CPU | M13-CCF0000 | en | 20-02

ZINFO2: Slot
ZINFO3: Type identifier
0xE011 Master project engineering at slave CPU not possible or wrong slave configuration
0xE012 Error at configuration standard backplane bus
0xE013 Error at shift register access to standard backplane bus digital modules
0xE014 Error in Check_Sys
0xE015 Error in access to master
ZINFO2: Slot of the master
ZINFO2: Page frame master
0xE016 Maximum block size exceeded in master transfer
ZINFO2: Slot
0xE017 Error in access to integrated slave
0xE018 Error in mapping the master periphery
0xE019 Error on standard backplane bus system detection
0xE01A Error at detection of the operating mode (8/9 bit)
0xE01B Error: Maximum number of plug-in components exceeded
0xE020 Error: Interrupt information undefined
ZINFO1: Rack/Slot
ZINFO3: Error type
4: Rack/Slot (in ZINFO1) undefined
5: Alarm type (in DatID) undefined
DatID: Interrupt type
0xE030 Error of the standard backplane bus
0xE0B0 SPEED7 is not stoppable
DatID: Not user relevant
0xE0C0 Not enough memory space in the working memory for code block (block too large)
0xE0CB Error on SSL access
ZINFO1: Error
4: SSL wrong
5: Sub-SSL wrong
6: Index wrong
ZINFO2: SZL-ID
ZINFO3: Index
HB400 | CPU | M13-CCF0000 | en | 20-02 329

0xE0CC Communication error
ZINFO1: Error code
1: Wrong priority
2: Buffer overrun
3: Telegram format error
4: Wrong SSL request (SSL-ID invalid)
5: Wrong SSL request (SSL-Sub-ID invalid)
6: Wrong SSL request (SSL-Index invalid)
7: Wrong value
8: Wrong return value
9: Wrong SAP
10: Wrong connection type
11: Wrong sequence number
12: Faulty block number in the telegram
13: Faulty block type in the telegram
14: Inactive function
15: Wrong size in the telegram
20: Error in writing on MMC
90: Faulty buffer size
98: Unknown error
99: Internal error
0xE0CD Error at DP-V1 job management
0xE0CE Error: Time out when sending I-Slave diagnostics
0xE100 Memory card access error
0xE101 Memory card error file system
0xE102 Memory card error FAT
0xE104 Memory card error at saving
0xE200 Memory card writing finished (Copy Ram2Rom)
OB: Not user relevant
PK: Not user relevant
0xE210 Memory card reading finished (reload after memory reset)
330 HB400 | CPU | M13-CCF0000 | en | 20-02

ZINFO1 - Position 0: Not user relevant
0xE21D Memory card reading: Error on reload (after memory reset), error in the block header
ZINFO1: Block type
56: OB
65: DB
66: SDB
67: FC
68: SFC
69: FB
70: SFB
97: VDB
98: VSDB
99: VFC
100: VSFC
101: VFB
102: VSFB
111: VOB
ZINFO2: Block number
ZINFO3: Block length
0xE21E Memory card reading: Error in recharging (after memory reset), "Protect.wld" file too large
0xE21F Memory card reading: Error at reload (after memory reset), checksum error when reading
ZINFO2: Block type
56: OB
65: DB
66: SDB
67: FC
68: SFC
69: FB
70: SFB
97: VDB
98: VSDB
99: VFC
100: VSFC
101: VFB
HB400 | CPU | M13-CCF0000 | en | 20-02 331

102: VSFB
111: VOB
0xE300 Internal flash writing completed (copy Ram2Rom)
0xE310 Internal flash reading completed (recharging after battery failure)
0xE400 FSC card was plugged
OB: FSC activated from this slot (PK)
OB: The inserted FSC is the activated FSC
OB: The inserted FSC is compatible with the CPU
PK: FSC source
0: CPU
1: Card
ZINFO1: FSC(CRC)
1146: 955-C000070
1736: 955-C0NE040
2568: FSC-C0ME040
3450: 955-C000M30
3903: 955-C000S30
4361: FSC-C000M30
4940: FSC-C000S30
5755: 955-C0ME040
6843: FSC-C0NE040
8561: FSC-C000S20
9012: FSC-C000M20
13895: 955-C000060
15618: 955-C000S20
16199: 955-C000M20
17675: FSC-C000S00
18254: FSC-C000M00
20046: FSC-C000040
21053: 955-C000040
22904: 955-C000S00
23357: 955-C000M00
24576: 955-C000050
35025: 955-C00MC10
36351: FSC-C000S40
36794: FSC-C000M40
37260: 955-C000S40
332 HB400 | CPU | M13-CCF0000 | en | 20-02

37833: 955-C000M40
38050: FSC-C00MC10
41460: 955-C000M50
41526: 955-C0PE040
42655: FSC-C00MC00
47852: 955-C00MC00
48709: FSC-C0PE040
50574: 955-C000M70
52366: 955-C000030
53501: FSC-C000030
58048: FSC-C000020
63411: 955-C000M60
65203: 955-C000020
ZINFO2: FSC serial number (high word)
ZINFO3: FSC serial number (low word)
0xE401 FSC card was removed
OB: Action after the end of the trial time
0: No action
1: CPU STOP
2: CPU STOP and FSC deactivated
3: Factory reset
255: FSC was not activated
PK: FSC source
0: CPU
1: Card
ZINFO1: FSC(CRC)
1146: 955-C000070
1736: 955-C0NE040
2568: FSC-C0ME040
3450: 955-C000M30
3903: 955-C000S30
4361: FSC-C000M30
4940: FSC-C000S30
5755: 955-C0ME040
6843: FSC-C0NE040
8561: FSC-C000S20
9012: FSC-C000M20
13895: 955-C000060
HB400 | CPU | M13-CCF0000 | en | 20-02 333

15618: 955-C000S20
16199: 955-C000M20
17675: FSC-C000S00
18254: FSC-C000M00
20046: FSC-C000040
21053: 955-C000040
22904: 955-C000S00
23357: 955-C000M00
24576: 955-C000050
35025: 955-C00MC10
36351: FSC-C000S40
36794: FSC-C000M40
37260: 955-C000S40
37833: 955-C000M40
38050: FSC-C00MC10
41460: 955-C000M50
41526: 955-C0PE040
42655: FSC-C00MC00
47852: 955-C00MC00
48709: FSC-C0PE040
50574: 955-C000M70
52366: 955-C000030
53501: FSC-C000030
58048: FSC-C000020
63411: 955-C000M60
65203: 955-C000020
DatID: FeatureSet Trialtime in minutes
0xE402 A configured functionality is not activated. The configuration is accepted, but the PLC can not go to RUN.
ZINFO1: Required FSC: PROFIBUS
ZINFO1: Required FSC: MOTION
ZINFO2: Number of released axes
ZINFO3: Number of configured axes
0xE403 FSC can not be activated in this CPU
OB: FCS error code
PK: FSC source
0: CPU
334 HB400 | CPU | M13-CCF0000 | en | 20-02

1: Card
ZINFO1: FSC(CRC)
1146: 955-C000070
1736: 955-C0NE040
2568: FSC-C0ME040
3450: 955-C000M30
3903: 955-C000S30
4361: FSC-C000M30
4940: FSC-C000S30
5755: 955-C0ME040
6843: FSC-C0NE040
8561: FSC-C000S20
9012: FSC-C000M20
13895: 955-C000060
15618: 955-C000S20
16199: 955-C000M20
17675: FSC-C000S00
18254: FSC-C000M00
20046: FSC-C000040
21053: 955-C000040
22904: 955-C000S00
23357: 955-C000M00
24576: 955-C000050
35025: 955-C00MC10
36351: FSC-C000S40
36794: FSC-C000M40
37260: 955-C000S40
37833: 955-C000M40
38050: FSC-C00MC10
41460: 955-C000M50
41526: 955-C0PE040
42655: FSC-C00MC00
47852: 955-C00MC00
48709: FSC-C0PE040
50574: 955-C000M70
52366: 955-C000030
53501: FSC-C000030
58048: FSC-C000020
HB400 | CPU | M13-CCF0000 | en | 20-02 335

63411: 955-C000M60
65203: 955-C000020
0xE404 Feature set deleted due to CRC error
0xE405 The trial time of a feature set/memory card has expired
OB: Action after the end of the trial time
0: No action
1: CPU STOP
2: CPU STOP and FSC deactivated
3: Factory reset
255: FSC was not activated
PK: FSC source
0: CPU
1: Card
ZINFO1: FSC(CRC)
1146: 955-C000070
1736: 955-C0NE040
2568: FSC-C0ME040
3450: 955-C000M30
3903: 955-C000S30
4361: FSC-C000M30
4940: FSC-C000S30
5755: 955-C0ME040
6843: FSC-C0NE040
8561: FSC-C000S20
9012: FSC-C000M20
13895: 955-C000060
15618: 955-C000S20
16199: 955-C000M20
17675: FSC-C000S00
18254: FSC-C000M00
20046: FSC-C000040
21053: 955-C000040
22904: 955-C000S00
23357: 955-C000M00
24576: 955-C000050
35025: 955-C00MC10
336 HB400 | CPU | M13-CCF0000 | en | 20-02

36351: FSC-C000S40
36794: FSC-C000M40
37260: 955-C000S40
37833: 955-C000M40
38050: FSC-C00MC10
41460: 955-C000M50
41526: 955-C0PE040
42655: FSC-C00MC00
47852: 955-C00MC00
48709: FSC-C0PE040
50574: 955-C000M70
52366: 955-C000030
53501: FSC-C000030
58048: FSC-C000020
63411: 955-C000M60
65203: 955-C000020
DatID: FeatureSet Trialtime in minutes
0xE406 The inserted feature set is corrupt
PK: FSC source
0: CPU
1: Card
0xE410 A CPU feature set was activated
PK: FSC source
0: CPU
1: Card
ZINFO1: FSC(CRC)
1146: 955-C000070
1736: 955-C0NE040
2568: FSC-C0ME040
3450: 955-C000M30
3903: 955-C000S30
4361: FSC-C000M30
4940: FSC-C000S30
5755: 955-C0ME040
6843: FSC-C0NE040
8561: FSC-C000S20
HB400 | CPU | M13-CCF0000 | en | 20-02 337

9012: FSC-C000M20
13895: 955-C000060
15618: 955-C000S20
16199: 955-C000M20
17675: FSC-C000S00
18254: FSC-C000M00
20046: FSC-C000040
21053: 955-C000040
22904: 955-C000S00
23357: 955-C000M00
24576: 955-C000050
35025: 955-C00MC10
36351: FSC-C000S40
36794: FSC-C000M40
37260: 955-C000S40
37833: 955-C000M40
38050: FSC-C00MC10
41460: 955-C000M50
41526: 955-C0PE040
42655: FSC-C00MC00
47852: 955-C00MC00
48709: FSC-C0PE040
50574: 955-C000M70
52366: 955-C000030
53501: FSC-C000030
58048: FSC-C000020
63411: 955-C000M60
65203: 955-C000020
0xE500 Memory management: Deleted block without corresponding entry in BstList
ZINFO2: Block type
56: OB
65: DB
66: SDB
67: FC
68: SFC
69: FB
338 HB400 | CPU | M13-CCF0000 | en | 20-02

70: SFB
97: VDB
98: VSDB
99: VFC
100: VSFC
101: VFB
102: VSFB
111: VOB
0xE501 Parser error
ZINFO1: Error code
1: Parser error: SDB structure
2: Parser error: SDB is not a valid SDB type
ZINFO2: SDB type
ZINFO3: SDB number
0xE502 Invalid block type in protect.wld (block was not loaded)
ZINFO2: Block type
56: OB
65: DB
66: SDB
67: FC
68: SFC
69: FB
70: SFB
97: VDB
98: VSDB
99: VFC
100: VSFC
101: VFB
102: VSFB
111: VOB
0xE503 Inconsistency of code sizes and block sizes in the working memory
ZINFO1: Code size
ZINFO2: Block size (high word)
ZINFO3: Block size (low word)
0xE504 Additional information for CRC error in the working memory
ZINFO2: Block address (high word)
HB400 | CPU | M13-CCF0000 | en | 20-02 339

ZINFO3: Block address (low word)
ZINFO1: Cause for MemDump
0: Unknown
1: Manual request
2: Invalid OP value
3: CRC code error
4: Processor exception
5: Processor exception with dump after reboot
6: Block-CRC error
0xE604 Multiple configuration of a periphery address for Ethernet PG/OP channel
ZINFO3: 0: periphery address is input, 1: periphery address is output
0xE605 Too many productive connections configured
ZINFO1: Interface slot
ZINFO2: Number of configured connections
ZINFO3: Number of admissible connections
0xE610 On-board PROFIBUS/MPI: Bus error removed
ZINFO1: Interface
0: Master system ID
ZINFO2: Slave address
0xE705 Too many PROFIBUS slaves configured
ZINFO1: Diagnostic address of the PROFIBUS master
ZINFO2: Number of configured slaves
340 HB400 | CPU | M13-CCF0000 | en | 20-02

ZINFO3: Number of admissible slaves
0xE70A PROFIBUS configured, but access way disabled
ZINFO1: Logical base address of the DP master
ZINFO2 - Position 8: DP master system ID
0xE710 On-board PROFIBUS/MPI: Bus error occurred
ZINFO1: Interface
ZINFO1: Slave no
DatID: Master system ID
PK: Error code
1: Error when assigning diagnostic address for slave (no. in ZINFO3)
2: Error when assigning diagnostic address for master
3: Error when assigning logical address when de/activating for slave (no. in ZINFO3)
4: Error when assigning slots for slave (no. in ZINFO3)
5: Error in DPV1 configuration (inputs) for slave (no. in ZINFO3)
6: Error in DPV1 configuration (outputs) for slave (no. in ZINFO3)
7: SubnetID for master (in ZINFO2) invalid
8: Slave (no. in ZINFO3) could not be configured (CFG length in OB)
ZINFO2: Master system ID
ZINFO1: Channel-Event
0: Channel offline
1: Bus error
2: Internal error
ZINFO1: Error code
HB400 | CPU | M13-CCF0000 | en | 20-02 341

1: Parameter error
2: Configuration error
0xE780 Error in configuration of a process image
ZINFO2: Logical address
ZINFO3: IO Flag
0xE781 Address range exceeds process image limit
ZINFO1: Address
ZINFO2: Length of the address range
ZINFO3: Size of the process image
DatID: Address range
0xE801 CMD - auto command: CMD_START recognized and executed
0xE802 CMD - auto command: CMD_End recognized and executed
0xE803 CMD - auto command: WAIT1SECOND recognized and executed
0xE804 CMD - auto command: WEBPAGE recognized and executed
0xE805 CMD - auto command: LOAD_PROJECT recognized and executed
0xE806 CMD - auto command: SAVE_PROJECT recognized and executed
ZINFO3: Status
0: Error
1: OK
32768: Wrong password
0xE807 CMD - auto command: FACTORY_RESET recognized and executed
0xE808 Internal message
0xE80A Internal message
ZINFO3: Status
0: OK
65153: File create error
65185: File writing error
65186: Odd address for reading
0xE80B CMD - auto command: DIAGBUF recognized and executed
ZINFO3: Status
0: OK
342 HB400 | CPU | M13-CCF0000 | en | 20-02

0xE80C Internal message
ZINFO3: Status
0: OK
0xE80D Internal message
0xE80E CMD - auto command: SET_NETWORK recognized and executed
0xE80F Internal message
ZINFO3: Status
0: OK
0xE814 CMD - auto command: SET_MPI_ADDRESS identified
0xE816 CMD - auto command: SAVE_PROJECT recognized but not executed, because the CPU memory is
empty
0xE82A CMD - auto command: CPUTYPE_318 recognized and executed
ZINFO3: Error code
0xE82B CMD - auto command: CPUTYPE_ORIGINAL recognized and executed
HB400 | CPU | M13-CCF0000 | en | 20-02 343

ZINFO3: Error code
0xE82C CMD - auto command: WEBVISU_PGOP_ENABLE recognized and executed
0xE82D CMD - auto command: WEBVISU_PGOP_DISABLE recognized and executed
0xE82E CMD - auto command: WEBVISU_CP_ENABLE recognized and executed
0xE82F CMD - auto command: WEBVISU_CP_DISABLE recognized and executed
0xE830 CMD - auto command: OPCUA_PGOP_ENABLE recognized and executed
0xE831 CMD - auto command: OPCUA_PGOP_DISABLE recognized and executed
0xE832 CMD - auto command: OPCUA_CP_ENABLE recognized and executed
0xE833 CMD - auto command: OPCUA_CP_DISABLE recognized and executed
0xE8FB CMD - auto command: Error: Initialization of the Ethernet PG/OP channel by means of SET_NETWORK is
faulty
0xE8FC CMD - auto command: Error: Some IP parameters missing in SET_NETWORK
0xE8FE CMD - auto command: Error: CMD_START not found
0xE8FF CMD - auto command: Error while reading CMD file (memory card error)
0xE901 Checksum error
0xE904 PG/OP: Multiple parametrization of a peripheral address
ZINFO1: Peripheral address
ZINFO2: Slot
ZINFO3: Data width
DatID: 0x54 Peripheral address is input address
DatID: 0x55 Peripheral address is output address
0xE90A PROFINET configured, but access way disabled
ZINFO3: Station number
ZINFO3: IO system ID
ZINFO3: System ID DP/PN
0xE910 PG/OP: Input peripheral address out of peripheral area
ZINFO2: Slot
ZINFO3: Data width
0xE911 PG/OP: Output peripheral address out of peripheral area
344 HB400 | CPU | M13-CCF0000 | en | 20-02

ZINFO2: Slot
ZINFO3: Data width
0xE920 Configuration error PROFINET
ZINFO1 - Position 0: Error code
1: Double IP/PROFINET configuration in slot 2 and 4
2: PROFINET IO system configured in slot 4
3: Too many PROFINET IO controller configured
4: Virtual device multiple configured
5: EtherCAT devices for PROFINET CP configured
6: PROFINET devices for EtherCAT CP configured
7: PROFINET CP configured at slot 2, although this is not supported
8: A PROFINET IO system (I-Device) must not be configured on the CP on slot 4
9: A PROFINET IO system (controller) must not be configured on the CP on slot 4
0xE980 Error when loading the WebVisu project file
ZINFO1: Platform
0xE981 Error in the configuration of the WebVisu project
ZINFO1: Platform
0xE982 Internal error of the WebVisu server
ZINFO1: Platform
0xE983 Hardware configuration of the control is not loaded, WebVisu is not started
ZINFO1: Platform
0xE984 WebVisu is blocked by the user, start of the WebVisu was prevented
ZINFO1: Platform
0xE985 WebVisu was started
ZINFO1: Platform
0xE986 WebVisu was stopped
ZINFO1: Platform
0xE987 WebVisu was enabled by the user
ZINFO1: Platform
0xE988 WebVisu was disabled by the user
ZINFO1: Platform
0xE989 WebVisu and OPC UA project not allowed at the same time
ZINFO1: Platform
0xE9A0 Error when loading the OPC UA project file
ZINFO1: Platform
ZINFO3 - Bit 0: Error code
0xE9A1 OPC UA: No FSC enabled
ZINFO1: Platform
HB400 | CPU | M13-CCF0000 | en | 20-02 345

0xE9A2 OPC UA: TAR file invalid
ZINFO1: Platform
ZINFO3: Error code
0xE9A3 OPC UA: Internal error of the OPC UA server
ZINFO1: Platform
ZINFO3: Error code
0xE9A4 OPC UA: Hardware configuration of the control is not loaded, Server is not started
ZINFO1: Platform
0xE9A5 OPC UA blocked by user, start of the server was prevented
ZINFO1: Platform
0xE9A6 OPC UA server was started
ZINFO1: Platform
0xE9A7 OPC UA server was stopped
ZINFO1: Platform
0xE9A8 OPC UA was disabled by the user
ZINFO1: Platform
0xE9A9 OPC UA was enabled by the user
ZINFO1: Platform
0xE9AA OPC UA: Lock by S7 configuration (access settings)
ZINFO1: Platform
0xE9AB OPC UA and WebVisu project not allowed at the same time
ZINFO1: Platform
0xEA00 Internal error - Please contact the hotline!
PK: Not relevant to user
ZINFO1: Slot
0xEA02 SBUS: Internal error (internal plugged sub module not recognized)
ZINFO1: Slot
ZINFO2: Type identifier target
0xEA03 SBUS: Communication error between CPU and IO controller
OB: Operating mode
0: Configuration in operating condition RUN
346 HB400 | CPU | M13-CCF0000 | en | 20-02

1: STOP (update)
2: STOP (memory reset)
3: STOP (auto initialization)
4: STOP (internal)
5: STARTUP (cold start)
6: STARTUP (restart/warm start)
7: STARTUP (hot restart)
9: RUN
10: HALT
11: COUPLING
12: UPDATING
13: DEFECTIVE
14: Error search mode
15: De-energised
253: Process image release in STOP
254: Watchdog
255: Not set
ZINFO1: Slot
ZINFO2: Status
0: OK
1: Error
2: Empty
3: Busy
4: Time out
5: Internal blocking
6: Too many telegrams
7: Not Connected
8: Unknown
0xEA04 SBUS: Multiple configuration of a periphery address
ZINFO2: Slot
ZINFO3: Data width
0xEA08 SBUS: Configured input data width not the same as the connected input data width
ZINFO1: Configured input data width
HB400 | CPU | M13-CCF0000 | en | 20-02 347

ZINFO2: Slot
ZINFO3: Input data width of the connected component
0xEA09 SBUS: Configured output data width not the same as the connected output data width
ZINFO1: Configured output data width
ZINFO2: Slot
ZINFO3: Output data width of the plugged component
0xEA0A SBUS: Internal error (internal plugged sub module wrong)
ZINFO1: Slot
ZINFO2: Type identifier target
3: PROFINET-CPU
4: EtherCAT-CPU
3: PROFINET-CPU
4: EtherCAT-CPU
0xEA10 SBUS: Input periphery address outside the periphery area
ZINFO2: Slot
ZINFO3: Data width
0xEA11 SBUS: Output periphery address outside the periphery area
ZINFO2: Slot
ZINFO3: Data width
0xEA12 SBUS: Error in writing dataset
ZINFO1: Slot
ZINFO2: Dataset number
ZINFO3: Dataset length
0xEA14 SBUS: Multiple configuration of a periphery address (diagnostic address)
ZINFO2: Slot
ZINFO3: Data width
0xEA18 SBUS: Error in mapping the master periphery
348 HB400 | CPU | M13-CCF0000 | en | 20-02

ZINFO2: HW slot
ZINFO3: Interface type
0xEA1A SBUS: Error in access to SBUS FPGA address table
ZINFO2: HW slot
ZINFO3: Table
0: Read
1: Writing
0xEA20 Error: RS485 interface is not pre-set to PROFIBUS DP master bus a PROFIBUS DP master is configured
0xEA21 Error: Configuration RS485 interface X2/X3: PROFIBUS DP master is configured but missing
ZINFO2: Interface X is configured incorrectly
0xEA22 Error: Configuration RS485 interface X2: Value is outside the limits
ZINFO2: Configuration for X2
0xEA23 Error: Configuration RS485 interface X3: Value is outside the limits
0xEA24 Error: Configuration RS485 interface X2/X3: Interface/protocol missing, default settings are used
ZINFO1: Status
OB: Slot of the CP
PK: File number
ZINFO1: Version of the CP
DatID: Line
OB: Slot of the CP
PK: File number
ZINFO1: Version of the CP
DatID: Line
HB400 | CPU | M13-CCF0000 | en | 20-02 349

0xEA50 PROFINET IO controller: Error in the configuration
ZINFO1: Rack/slot of the controller
ZINFO2: Device number
ZINFO3: Slot at the device
0xEA51 PROFINET IO controller: There is no PROFINET IO controller at the configured slot
ZINFO2: Recognized type identifier at the configured slot
0xEA52 PROFINET IO controller: Too many configured PROFINET IO controllers
ZINFO1: Number of configured controllers
ZINFO2: Slot of the excessively configured controller
0xEA53 PROFINET IO controller: Too many configured PROFINET IO devices
ZINFO1: Number of configured devices
ZINFO2: Slot
ZINFO3: Maximum possible number of devices
0xEA54 PROFINET IO controller: Multiple configuration of a periphery address or range too long
0: Error type
0: No error
1: Range too long
2: Input address already used
3: Output address already used
ZINFO3: Base address of the block which is too large
0xEA55 PROFINET IO controller: Too many slots or too high slot number configured
ZINFO3: Number of configured slots or too high slot number
0xEA56 PROFINET IO controller: Too many subslots or too high sub slot number configured
350 HB400 | CPU | M13-CCF0000 | en | 20-02

ZINFO3: Number of configured subslots or too high sub slot number
0xEA57 PROFINET IO controller: The port configuration in the virtual device has no effect.
OB: File number
PK: Slot of the controller
ZINFO1: Firmware major version
ZINFO2: Firmware minor version
DatID: Line
OB: File number.
DatID: Line
OB: File number
DatID: Line
0xEA64 PROFINET IO controller/EtherCAT-CP: Error in configuration
PK: Interface
ZINFO1 - Bit 0: Too many devices
ZINFO1 - Bit 1: Too many devices per second
ZINFO1 - Bit 2: Too many input bytes per millisecond
ZINFO1 - Bit 3: Too many output bytes per millisecond
ZINFO1 - Bit 4: Too many input bytes per device
ZINFO1 - Bit 5: Too many output bytes per device
ZINFO1 - Bit 6: Too many productive connections
ZINFO1 - Bit 7: Too many input bytes in the process image
ZINFO1 - Bit 8: Too many output bytes in the process image
ZINFO1 - Bit 9: Configuration not available
ZINFO1 - Bit 10: Configuration invalid
ZINFO1 - Bit 11: Refresh interval too small
ZINFO1 - Bit 12: Refresh interval too large
ZINFO1 - Bit 13: Invalid device number
ZINFO1 - Bit 14: CPU is configured as an I device
HB400 | CPU | M13-CCF0000 | en | 20-02 351

ZINFO1 - Bit 15: Assume IP address in another way. Is not supported for the IP address of the controller.
ZINFO2 - Bit 0: Incompatible configuration (SDB version not supported)
ZINFO2 - Bit 1: EtherCAT: EoE configured but not supported (Possible cause is a too short cycle time of
the EtherCAT master system. When using EoE terminals, at least a cycle time of 4ms must be config-
ured.)
ZINFO2 - Bit 2: DC parameter invalid
ZINFO2 - Bit 3: I device configuration invalid (slot gap)
ZINFO2 - Bit 4: MRP configuration invalid (client)
ZINFO2 - Bit 5: Transfer rate 10 MBit (HD/FD) configured but not supported
PK: Platform
0: none
8: CP
9: Ethernet CP
10: PROFINET CP
12: EtherCAT CP
16: CPU
ZINFO1: ServiceID in which the error occurred
ZINFO2: Command in which the error occurred
1: Request
2: Connect
3: Error
0xEA66 PROFINET IO controller: Error in the communication stack
OB: StackError.Service
PK: Rack/slot
ZINFO1: StackError.Error.Code
ZINFO2: StackError.Error.Detail
ZINFO3 - Position 0: StackError.Error.AdditionalDetail
ZINFO3 - Position 8: StackError.Error.AreaCode
DatID: StackError.DeviceRef
0xEA67 PROFINET IO controller: Error reading dataset
OB: Rack/slot of the controller
PK: Error type
0: Dataset error local
1: Dataset error stack
2: Dataset error station
ZINFO2: Dataset handle (caller)
ZINFO3: Internal error code from PN stack
352 HB400 | CPU | M13-CCF0000 | en | 20-02

DatID: Device
0xEA68 PROFINET IO controller: Error writing dataset
OB: Rack/slot of the controller
PK: Error type
0: Dataset error local
1: Dataset error stack
2: Dataset error station
ZINFO2: Dataset handle (caller)
ZINFO3: Internal error code from PN stack
DatID: Device
ZINFO1: Minimum version for the FPGA
ZINFO2: Loaded FPGA version
0xEA6A PROFINET IO controller: Service error in the communication stack
OB: Service ID
PK: Rack/slot
ZINFO1: ServiceError.Code
ZINFO2: ServiceError.Detail
ZINFO3 - Position 0: ServiceError.AdditionalDetail
ZINFO3 - Position 8: ServiceError.AreaCode
0xEA6B PROFINET IO controller: Incorrect Vendor-ID
OB: Operating mode
1: STOP (update)
4: STOP (internal)
9: RUN
10: HALT
11: COUPLING
12: UPDATING
13: DEFECTIVE
15: De-energised
HB400 | CPU | M13-CCF0000 | en | 20-02 353

254: Watchdog
255: Not set
PK: Rack/slot
ZINFO1: Device ID
0xEA6C PROFINET IO controller: Incorrect Device-ID
OB: Operating mode
1: STOP (update)
4: STOP (internal)
9: RUN
10: HALT
11: COUPLING
12: UPDATING
13: DEFECTIVE
15: De-energised
254: Watchdog
255: Not set
PK: Rack/slot
ZINFO1: Device ID
0xEA6D PROFINET IO controller: No empty name
OB: Operating mode
1: STOP (update)
4: STOP (internal)
354 HB400 | CPU | M13-CCF0000 | en | 20-02

9: RUN
10: HALT
11: COUPLING
12: UPDATING
13: DEFECTIVE
15: De-energised
254: Watchdog
255: Not set
PK: Rack/slot
ZINFO1: Device ID
0xEA6E PROFINET IO controller: Wait for RPC response
OB: Operating mode
1: STOP (update)
4: STOP (internal)
9: RUN
10: HALT
11: COUPLING
12: UPDATING
13: DEFECTIVE
15: De-energised
254: Watchdog
255: Not set
PK: Rack/slot
HB400 | CPU | M13-CCF0000 | en | 20-02 355

ZINFO1: Device ID
0xEA6F PROFINET IO controller: PROFINET module deviation
OB: Operating mode
1: STOP (update)
4: STOP (internal)
9: RUN
10: HALT
11: COUPLING
12: UPDATING
13: DEFECTIVE
15: De-energised
254: Watchdog
255: Not set
PK: Rack/slot
ZINFO1: Device ID
0xEA70 PROFINET IO controller: PROFINET stack configuration error
OB: UnsupportedApiError.api
PK: Rack/slot
ZINFO1: UnsupportedApiError.slot
ZINFO2: UnsupportedApiError.subslot
DatID: UnsupportedApiError.deviceID
PK: Rack/slot
ZINFO1: functionIndex
356 HB400 | CPU | M13-CCF0000 | en | 20-02

OB: Connection number
ZINFO1: Error cause
129: PNIO
207: RTA error
218: AlarmAck
219: IODConnectRes
220: IODReleaseRes
221: IOD/IOXControlRes
222: IODReadRes
223: IODWriteRes
ZINFO2: ErrorDecode
128: PNIORW: Service Read Write
129: PNIO: Other Service or internal e.g. RPC errors
130: Vendor specific
ZINFO3: Error code (PN spec. V2.722 chapter 5.2.6)
DatID: Device ID
ZINFO1: Filenamehash[0-3]
ZINFO3: Line
DatID: SvnRevision
ZINFO3: Line
DatID: SvnRevision
HB400 | CPU | M13-CCF0000 | en | 20-02 357

ZINFO3: Line
DatID: SvnRevision
OB: Current OB number
PK: Core status
0: INIT
1: STOP
2: READY
3: PAUSE
4: RUN
ZINFO3: Line
DatID: Current job number
PK: Core status
0: INIT
1: STOP
2: READY
3: PAUSE
4: RUN
ZINFO3: Line
PK: Core status
0: INIT
1: STOP
2: READY
3: PAUSE
4: RUN
ZINFO3: Line
358 HB400 | CPU | M13-CCF0000 | en | 20-02

ZINFO3: Slot
0xEA98 Error in file reading via SBUS
ZINFO3: Slot
0xEA99 Parameter assignment job could not be executed
ZINFO1: File version on MMC/SD (if not 0)
ZINFO2: File version of the SBUS module (if not 0)
ZINFO3: Slot
0xEAA0 Internal error - Please contact the hotline!
OB: Current operating mode
1: STOP (update)
4: STOP (internal)
9: RUN
10: HALT
11: COUPLING
12: UPDATING
13: DEFECTIVE
15: De-energised
254: Watchdog
255: Not set
ZINFO1: Diagnostic address of the master
ZINFO3: Number of errors which occurred
0xEAB0 Invalid link mode
OB: Current operating mode
HB400 | CPU | M13-CCF0000 | en | 20-02 359

1: STOP (update)
4: STOP (internal)
9: RUN
10: HALT
11: COUPLING
12: UPDATING
13: DEFECTIVE
15: De-energised
254: Watchdog
255: Not set
ZINFO2: Current connection mode
1: 10Mbit half-duplex
2: 10Mbit full-duplex
3: 100Mbit half-duplex
4: 100Mbit full-duplex
5: Connection mode undefined
6: Auto Negotiation
0xEAC0 Internal error - Please contact the hotline!
ZINFO1: Error code
2: Internal error
3: Internal error
4: Internal error
5: Internal error
6: Internal error
7: Internal error
8: Internal error
8: Internal error
0xEAD0 SyncUnit configuration error
ZINFO1: Status
0xEB02 System error: Preset configuration does not match actual configuration
360 HB400 | CPU | M13-CCF0000 | en | 20-02

ZINFO1: Bit mask slots 1-16
DatID: Bit mask slots 49-64
0xEB03 System error: IO mapping
ZINFO1: Error type
1: SDB parser error
2: Configured address already used
3: Mapping error
ZINFO2: Slot (0=cannot be determined)
0xEB04 Bus: Multiple configuration of a periphery address
ZINFO2: Slot
DatID: Input
DatID: Output
0xEB05 System error: Bus structure for isochronous process image not suitable
ZINFO2: Slot (0=cannot be determined)
0xEB06 System error: Timeout with the isochronous process image
0xEB10 System error: Bus error
ZINFO1: Error type
96: Bus enumeration error
128: General error
129: Queue execution error
130: Error interrupt
ZINFO2: Error on bus enumeration error (ZINFO1)
0xEB11 System error: Error during bus initialization
0xEB15 Bus FMM message
ZINFO1: FMM message
0xEB20 System error: Interrupt information undefined
0xEB21 System error: Accessing configuration data
HB400 | CPU | M13-CCF0000 | en | 20-02 361

0xEC02 EtherCAT: Configuration warning
ZINFO1: Error code
1: Number of slave stations is not supported
2: Master system ID invalid
3: Slot invalid
4: Master configuration invalid
5: Master type invalid
6: Slave diagnostic address invalid
7: Slave address invalid
8: Slave module IO configuration invalid
9: Logical address already in use
10: Internal error
11: IO mapping error
12: Error
13: Error in initialising the EtherCAT stack (is entered by the CP)
14: Slave station number already occupied by virtual device
0xEC03 EtherCAT: Configuration error
ZINFO1: Error code
1: Number of slave stations is not supported
2: Master system ID invalid
3: Slot invalid
4: Master configuration invalid
5: Master type invalid
6: Slave diagnostic address invalid
7: Slave address invalid
8: Slave module IO configuration invalid
9: Logical address already in use
10: Internal error
11: IO mapping error
12: Error
13: Error in initialising the EtherCAT stack (is entered by the CP)
14: Slave station number already occupied by virtual device
362 HB400 | CPU | M13-CCF0000 | en | 20-02

0xEC04 EtherCAT: Multiple configuration of a periphery address
ZINFO2: Slot
DatID: Input
DatID: Output
0xEC05 EtherCAT: Check the set DC mode of the YASKAWA Sigma 5/7 drive
OB: Operating mode
1: STOP (update)
4: STOP (internal)
9: RUN
10: HALT
11: COUPLING
12: UPDATING
13: DEFECTIVE
15: De-energised
254: Watchdog
255: Not set
ZINFO1: Station address of the EtherCAT device
ZINFO2: Error code
1: WARNING: For the drive the DC Beckhoff mode is recommended (DC reference clock is not in
Beckhoff Mode)!
2: NOTE: For the drive the DC Hilscher mode is recommended (DC reference clock is not in Beckhoff
Mode)!
3: The station address could not be determined for checking (station address in ZINFO1 is accordingly 0)
4: The slave information could not be determined for checking (station address in ZINFO1 is accordingly
0)
5: The EtherCAT status of the drive could not be determined
HB400 | CPU | M13-CCF0000 | en | 20-02 363

6: Error when sending the SDO request (for further information, the (subsequent) event with the ID
0xED60 is to be analysed on the CP)
7: Drive returns error in the SDO response (for further information, the (subsequent) event with the ID
0xED60 is to be analysed on the CP)
8: SDO time out, DC mode could not be determined (for further information, the (subsequent) event with
the ID 0xED60 is to be analysed on the CP)
0xEC10 EtherCAT: Recovery bus with all slaves
ZINFO1 - Position 0: New status
0: Undefined/Unkown
1: Init
2: PreOp
3: Bootstrap
4: SafeOp
8: Op
ZINFO1 - Position 8: Previous status
0: Undefined/Unkown
1: Init
2: PreOp
3: Bootstrap
4: SafeOp
8: Op
ZINFO2: Diagnostic address of the station
ZINFO3: Number of stations, which are not in the same state as the master
DatID: Station not available
DatID: Station available
DatID: Input address
DatID: Output address
0xEC11 EtherCAT: Recovery bus with missing slaves
0: Undefined/Unkown
1: Init
2: PreOp
3: Bootstrap
4: SafeOp
8: Op
0: Undefined/Unkown
1: Init
364 HB400 | CPU | M13-CCF0000 | en | 20-02

2: PreOp
3: Bootstrap
4: SafeOp
8: Op
ZINFO3: Number of stations which are not in the same state as the master
0xEC12 EtherCAT: Recovery slave
0: Undefined/Unkown
1: Init
2: PreOp
3: Bootstrap
4: SafeOp
8: Op
0: Undefined/Unkown
1: Init
2: PreOp
3: Bootstrap
4: SafeOp
8: Op
ZINFO3: AL status code
0xEC30 EtherCAT: Topology OK
0xEC40 Bus cycle time infringement resolved
0xEC50 EtherCAT: Distributed clocks (DC) out of sync
OB: Operating mode
HB400 | CPU | M13-CCF0000 | en | 20-02 365

1: STOP (update)
4: STOP (internal)
9: RUN
10: HALT
11: COUPLING
12: UPDATING
13: DEFECTIVE
15: De-energised
254: Watchdog
255: Not set
ZINFO3: DC state change
0: DC master out of sync
1: DC slave stations out of sync
0xEC80 EtherCAT: Bus error resolved
0xED10 EtherCAT: Breakdown bus
0: Undefined/Unkown
1: Init
2: PreOp
3: Bootstrap
4: SafeOp
8: Op
0: Undefined/Unkown
1: Init
2: PreOp
366 HB400 | CPU | M13-CCF0000 | en | 20-02

3: Bootstrap
4: SafeOp
8: Op
0xED12 EtherCAT: Breakdown slave
0: Undefined/Unkown
1: Init
2: PreOp
3: Bootstrap
4: SafeOp
8: Op
0: Undefined/Unkown
1: Init
2: PreOp
3: Bootstrap
4: SafeOp
8: Op
ZINFO3: AlStatusCode
0: No error
1: Unspecified error
17: Invalid requested status change
18: Unknown requested status
19: Bootstrap not supported
20: No valid firmware
22: Invalid mailbox configuration
23: Invalid sync manager configuration
24: No valid inputs available
25: No valid outputs available
26: Synchronisation error
27: Sync manager watchdog
HB400 | CPU | M13-CCF0000 | en | 20-02 367

28: Invalid sync manager types
29: Invalid output configuration
30: Invalid input configuration
31: Invalid watchdog configuration
32: Slave station needs cold start
33: Slave station needs to be in INIT state
34: Slave station needs to be in PreOp state
35: Slave station needs to be in SafeOp state
45: Invalid output FMMU configuration
46: Invalid input FMMU configuration
48: Invalid DC Sync configuration
49: Invalid DC Latch configuration
50: PLL error
51: Invalid DC IO error
52: Invalid DC time out error
66: Error in acyclic data exchange Ethernet Over EtherCAT
67: Error in acyclic data exchange CAN Over EtherCAT
68: Error in acyclic data exchange Fileaccess Over EtherCAT
69: Error in acyclic data exchange Servo Drive Profile Over EtherCAT
79: Error in acyclic data exchange Vendorspecific Over EtherCAT
0xED20 EtherCAT: Bus state change without calling OB86
0: Undefined/Unkown
1: Init
2: PreOp
3: Bootstrap
4: SafeOp
8: Op
0: Undefined/Unkown
1: Init
2: PreOp
3: Bootstrap
4: SafeOp
368 HB400 | CPU | M13-CCF0000 | en | 20-02

8: Op
0xED21 EtherCAT: Incorrect bus status change
0: Undefined/Unkown
1: Init
2: PreOp
3: Bootstrap
4: SafeOp
8: Op
0: Undefined/Unkown
1: Init
2: PreOp
3: Bootstrap
4: SafeOp
8: Op
ZINFO3: Error code
4: Cancel (master state change)
8: Busy
11: Invalid parameters
14: Invalid status
16: Time out
0xED22 EtherCAT: Slave status change that does not generate an OB86
0: Undefined/Unkown
1: Init
2: PreOp
HB400 | CPU | M13-CCF0000 | en | 20-02 369

3: Bootstrap
4: SafeOp
8: Op
0: Undefined/Unkown
1: Init
2: PreOp
3: Bootstrap
4: SafeOp
8: Op
0: No error
50: PLL error
370 HB400 | CPU | M13-CCF0000 | en | 20-02

0xED23 EtherCAT: Time out while changing the master state to OP, after CPU has changed to RUN
OB: Operating mode
1: STOP (update)
4: STOP (internal)
9: RUN
10: HALT
11: COUPLING
12: UPDATING
13: DEFECTIVE
15: De-energised
254: Watchdog
255: Not set
ZINFO1: Master status
0: Undefined/Unkown
1: Init
2: PreOp
3: Bootstrap
4: SafeOp
8: Op
ZINFO2: EtherCAT configuration present
HB400 | CPU | M13-CCF0000 | en | 20-02 371

0: There is no EC configuration
1: There is an EC configuration
ZINFO3: DC in sync
0: Not in sync
1: In sync
0xED30 EtherCAT: Topology deviation
0xED31 EtherCAT: Overflow of the interrupt queue
0xED40 Bus cycle time infringement occurred
0xED50 EtherCAT: Distributed clocks (DC) in sync
OB: Operating mode
1: STOP (update)
4: STOP (internal)
9: RUN
10: HALT
11: COUPLING
12: UPDATING
13: DEFECTIVE
15: De-energised
254: Watchdog
255: Not set
ZINFO3: DC state change
0: Master
1: Slave
0xED60 EtherCAT: Diagnostic buffer CP: Slave status change
OB: Operating mode
372 HB400 | CPU | M13-CCF0000 | en | 20-02

1: STOP (update)
4: STOP (internal)
9: RUN
10: HALT
11: COUPLING
12: UPDATING
13: DEFECTIVE
15: De-energised
254: Watchdog
255: Not set
0: Undefined/Unkown
1: Init
2: PreOp
3: Bootstrap
4: SafeOp
8: Op
ZINFO2: Slave address
0: No error
HB400 | CPU | M13-CCF0000 | en | 20-02 373

50: PLL error
DatID: Cause for slave status change
0: Regular slave status change
1: Slave failure
2: Recovery slave
3: Slave is in an error state
4: Slave has unexpectedly changed its status
0xED61 EtherCAT: Diagnostic buffer CP: CoE emergency
OB: EtherCAT station address (high byte)
PK: EtherCAT station address (low byte)
ZINFO1 - Position 0: Error register
ZINFO1 - Position 8: MEF-Byte1
DatID: Error code
0xED62 EtherCAT: Diagnostic buffer CP: Error on SDO access
374 HB400 | CPU | M13-CCF0000 | en | 20-02

ZINFO1: Index
ZINFO2: SDO error code (high word)
ZINFO3: SDO error code (low word)
DatID: Sub index
0xED63 EtherCAT: Diagnostic buffer CP: Error in the response to an INIT command
ZINFO1: Error type
0: Not defined
1: No response
2: Validation error
3: INIT command failed, requested station could not be reached
0xED70 EtherCAT: Diagnostic buffer CP: Twofold hot connect group recognised
OB: Operating mode
1: STOP (update)
4: STOP (internal)
9: RUN
10: HALT
11: COUPLING
12: UPDATING
13: DEFECTIVE
15: De-energised
254: Watchdog
255: Not set
ZINFO2: EtherCAT station address
0xED80 Bus error occurred (receive time-out)
HB400 | CPU | M13-CCF0000 | en | 20-02 375

0xEE00 Additional information at UNDEF_OPCODE
0xEE01 Internal error - Please contact the hotline!
ZINFO3: SFB number
0xEEEE CPU was completely deleted, since after PowerON the start-up could not be finished
0xEF00 Internal error - Please contact the hotline!
0xEFFE Internal error - Please contact the hotline!
0xEFFF Internal error - Please contact the hotline!
0xF9C1 Restart of the component
OB: NCM_EVENT
1: OVS: Component start-up request was denied
3: Component data basis invalid
6: IP_CONFIG: New IP address assigned by STEP7 configuration
10: IP_CONFIG: A non-configured new IP address was assigned
13: HW reset at P bus (for CPU memory reset)
19: Switch actuation from STOP to RUN causes the restart of the component
20: MGT: PG command causes the restart of the component
376 HB400 | CPU | M13-CCF0000 | en | 20-02

21: MGT: Take-over of component data basis causes the hot restart of the component
23: Stopping the sub-system after having loaded the already existing consistency-secured SDBs xxxx by
the rack component
25: The SIMATIC procedure has been selected for the time synchronisation of the component.
26: Component actively established a connection
28: The SDB xxxx loaded by the rack component is the consistency securing object (SDB type 0x3118)
29: The component actively disconnected the system connection to the CPU
31: Inconsistency of the component data base by loading SDB xxxx by the rack component (SDB type
0x3100)
32: Periphery enabled by S7-CPU
33: Periphery disabled by S7-CPU
34: Component STOP due to switch actuation
35: Component STOP due to invalid configuration
36: Component STOP due to PG command
38: SDB xxxx is not registered in the still valid consistency securing object, or it has an incorrect time
stamp (SDB type 0x3107), the error is being corrected
40: Memory reset executed
44: Consistency of the data base achieved after loading the SDBs xxxx by the rack component (SDB type
xxxx)
45: Remanent part of the component data base is deleted by the rack component after being loaded
70: Restore factory defaults (same as memory reset of CPU!)
83: Network interface: automatic configuration, TP/ITP with 10 Mbit/s semi-duplex
96: The MAC address was retrieved from the system SDB. This is the configured address.
97: The MAC address was retrieved from the boot EPROM. This is the factory-provided address.
100: Restart of the component
101: Component STOP due to deletion of system SDBs
104: PG command start was denied due to missing or inconsistent configuration
105: Component STOP due to double IP address
107: Start-up request by switch actuation was denied due to missing or inconsistent configuration
PK: NCM_SERVICE
2: Management
3: Object management system
6: Time synchronisation
10: IP_CONFIG
38: SEND/RECEIVE
HB400 | CPU | M13-CCF0000 | en | 20-02 377

Integrated blocks VIPA System MICRO
B Integrated blocks
OB Name Description
OB 1 CYCL_EXC Program Cycle
OB 10 TOD_INT0 Time-of-day Interrupt
OB 20 DEL_INT0 Time delay interrupt
OB 21 DEL_INT1 Time delay interrupt
OB 32 CYC_INT2 Cyclic interrupt
OB 40 HW_INT0 Hardware interrupt
OB 80 CYCL_FLT Time error
OB 81 PS_FLT Power supply error
OB 82 I/O_FLT1 Diagnostics interrupt
OB 83 I/O_FLT2 Insert / remove module
OB 85 OBNL_FLT Priority class error
OB 86 RACK_FLT Slave failure / restart
OB 100 COMPLETE RESTART Start-up
OB 102 COLD RESTART Start-up
OB 121 PROG_ERR Programming error
OB 122 MOD_ERR Periphery access error
SFB Name Description

SFB 0 CTU Up-counter
SFB 1 CTD Down-counter
SFB 2 CTUD Up-down counter
SFB 3 TP Create pulse
SFB 4 TON On-delay
SFB 5 TOF Create turn-off delay
SFB 7 TIMEMESS Time measurement
SFB 12 BSEND Sending data in blocks
SFB 13 BRCV Receiving data in blocks:
SFB 14 GET Remote CPU read
SFB 15 PUT Remote CPU write
SFB 32 DRUM Realize a step-by-step switch
SFB 47 COUNT Control counter
SFB 48 FREQUENC Frequency measurement
378 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO Integrated blocks
SFB Name Description

SFB 49 PULSE Pulse width modulation
SFB 52 RDREC Read record set
SFB 53 WRREC Write record set
SFB 54 RALRM Receiving an interrupt from a periphery module
SFC Name Description

SFC 0 SET_CLK Set system clock
SFC 1 READ_CLK Read system clock
SFC 2 SET_RTM Set run-time meter
SFC 3 CTRL_RTM Control run-time meter
SFC 4 READ_RTM Read run-time meter
SFC 5 GADR_LGC Logical address of a channel
SFC 6 RD_SINFO Read start information
SFC 7 DP_PRAL Triggering a hardware interrupt on the DP master
SFC 12 D_ACT_DP Activating and deactivating of DP slaves
SFC 13 DPNRM_DG Read diagnostic data of a DP salve
SFC 14 DPRD_DAT Read consistent data
SFC 15 DPWR_DAT Write consistent data
SFC 17 ALARM_SQ ALARM_SQ
SFC 18 ALARM_SQ ALARM_S
SFC 19 ALARM_SC Acknowledgement state last alarm
SFC 20 BLKMOV Block move
SFC 21 FILL Fill a field
SFC 22 CREAT_DB Create a data block
SFC 23 DEL_DB Deleting a data block
SFC 24 TEST_DB Test data block
SFC 28 SET_TINT Set time-of-day interrupt
SFC 29 CAN_TINT Cancel time-of-day interrupt
SFC 30 ACT_TINT Activate time-of-day interrupt
SFC 31 QRY_TINT Query time-of-day interrupt
SFC 32 SRT_DINT Start time-delay interrupt
SFC 33 CAN_DINT Cancel time-delay interrupt
SFC 34 QRY_DINT Query time-delay interrupt
SFC 36 MSK_FLT Mask synchronous errors
SFC 37 MSK_FLT Unmask synchronous errors
SFC 38 READ_ERR Read error register
SFC 39 DIS_IRT Disabling interrupts
HB400 | CPU | M13-CCF0000 | en | 20-02 379

Integrated blocks VIPA System MICRO
SFC Name Description

SFC 40 EN_IRT Enabling interrupts
SFC 41 DIS_AIRT Delaying interrupts
SFC 42 EN_AIRT Enabling delayed interrupts
SFC 43 RE_TRIGR Re-trigger the watchdog
SFC 44 REPL_VAL Replace value to ACCU1
SFC 46 STP STOP the CPU
SFC 47 WAIT Delay the application program
SFC 49 LGC_GADR Read the slot address
SFC 51 RDSYSST Read system status list SSL
SFC 52 WR_USMSG Write user entry into diagnostic buffer
SFC 53 µS_TICK Time measurement
SFC 54 RD_DPARM Reading predefined parameters
SFC 55 WR_PARM Write dynamic parameter
SFC 56 WR_DPARM Write default parameter
SFC 57 PARM_MOD Parametrize module
SFC 58 WR_REC Write record set
SFC 59 RD_REC Read record set
SFC 64 TIME_TCK Read system time tick
SFC 65 X_SEND Sending data
SFC 66 X_RCV Receiving data
SFC 67 X_GET Read data
SFC 68 X_PUT Write data
SFC 69 X_ABORT Disconnect
SFC 70 GEO_LOG Determining the start address of a module
SFC 71 LOG_GEO Determining the slot belonging to a logical address
SFC 81 UBLKMOV Copy data area without gaps
SFC 101 HTL_RTM Handling runtime meters
SFC 102 RD_DPARA Reading predefined parameters
SFC 105 READ_SI Reading dynamic system resources
SFC 106 DEL_SI Releasing dynamic system resources
SFC 107 ALARM_DQ ALARM_DQ
SFC 108 ALARM_DQ ALARM_DQ
380 HB400 | CPU | M13-CCF0000 | en | 20-02

VIPA System MICRO SSL partial list
C SSL partial list

More information about this may be found in the manual "VIPA SPEED7
Operation List".
SSL-ID SSL partial list

xy11h Module identification
xy12h CPU characteristics
xy13h User memory areas
xy14h System areas
xy15h Block Types
xy19h Status of all LEDs
xy1Ch Identification of the component
xy22h Interrupt status
xy32h Communication status data
xy37h Ethernet details of the module
xy3Ah Status of the TCON Connections
xy3Eh Web server diagnostic information
xy3Fh Configuration of Access settings
xy74h Status of the LEDs
xy91h Status information CPU
xy92h Stations status information (DPM)
xy94h Stations status information (DPM, PROFINET IO and EtherCAT)
xy95h Status information (DPM-, PROFINET IO system)
xy96h Module status information (PROFIBUS DP, PROFINET IO, EtherCAT)
xyA0h Diagnostic buffer of the CPU
xyB3h Module diagnostic information (record set 1) via logical address
xyB4h Diagnostic data of a DP slave
xyE0h Information EtherCAT master/slave
xyE1h EtherCAT bus system
xyFAh Statistics information to OBs
xyFCh Status of the VSC features from the System MICRO CPU
HB400 | CPU | M13-CCF0000 | en | 20-02 381

Cpu M13-CCF0000 20-02

Uploaded by

Copyright:

Available Formats

Cpu M13-CCF0000 20-02

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cpu M13-CCF0000 20-02

Uploaded by

Copyright:

Available Formats

VIPA System MICRO

CPU | M13-CCF0000 | Manual

M13-CCF0000_000_CPU M13C,7,EN - © 2020

HB400 | CPU | M13-CCF0000 | en | 20-02 3

4.8 Setting standard CPU parameters.................................................................. 77

4 HB400 | CPU | M13-CCF0000 | en | 20-02

5.6.6 Counter - Additional functions................................................................... 144

HB400 | CPU | M13-CCF0000 | en | 20-02 5

6.7.8 Role management ................................................................................. 200

6 HB400 | CPU | M13-CCF0000 | en | 20-02

10.4 Parametrization.......................................................................................... 250

HB400 | CPU | M13-CCF0000 | en | 20-02 7

13.7.1 Fast introduction...................................................................................... 314

8 HB400 | CPU | M13-CCF0000 | en | 20-02

HB400 | CPU | M13-CCF0000 | en | 20-02 9

1.2 About this manual

Product Order number as of state:

Availability The manual is available in:

10 HB400 | CPU | M13-CCF0000 | en | 20-02

Supplementary information and useful tips.

1.3 Safety information

Documentation The manual must be available to all personnel in the

HB400 | CPU | M13-CCF0000 | en | 20-02 11

2 Basics and mounting

Shipping of modules Modules must be shipped in the original packing material.

12 HB400 | CPU | M13-CCF0000 | en | 20-02

2.2 System conception

HB400 | CPU | M13-CCF0000 | en | 20-02 13

14 HB400 | CPU | M13-CCF0000 | en | 20-02

Dimensions power supply

HB400 | CPU | M13-CCF0000 | en | 20-02 15

16 HB400 | CPU | M13-CCF0000 | en | 20-02

2.4.1.2 Mounting with mounting rail

HB400 | CPU | M13-CCF0000 | en | 20-02 17

4. Move the CPU on the mounting rail at its position.

2.4.2 Mounting the extension module

18 HB400 | CPU | M13-CCF0000 | en | 20-02

2.4.3 Mounting periphery module

HB400 | CPU | M13-CCF0000 | en | 20-02 19

20 HB400 | CPU | M13-CCF0000 | en | 20-02

2.5.1 Wiring CPU

Insert wire The wiring happens without a tool.

HB400 | CPU | M13-CCF0000 | en | 20-02 21

22 HB400 | CPU | M13-CCF0000 | en | 20-02

The electronic power section supply is internally protected against higher

2. Push the screwdriver backwards:

HB400 | CPU | M13-CCF0000 | en | 20-02 23

2.5.2 Wiring periphery module

Insert wire The wiring happens without a tool.

24 HB400 | CPU | M13-CCF0000 | en | 20-02

2. Push the screwdriver backwards:

HB400 | CPU | M13-CCF0000 | en | 20-02 25

3. Push the screwdriver backwards:

4. In this way, remove all plugged connectors on the CPU.

26 HB400 | CPU | M13-CCF0000 | en | 20-02

5. Move the CPU on the mounting rail at its position.

7. Remove the connectors, which are not necessary at the CPU.

HB400 | CPU | M13-CCF0000 | en | 20-02 27

8. Plug again the wired connectors.