Page 1 VIPA System 300S CPU | 317-4PN23 | Manual HB140 | CPU | 317-4PN23 | en | 18-01 SPEED7 CPU 317PN www.vipa.com/en/service-support/manuals...
Page 2 VIPA GmbH Ohmstr. 4 91074 Herzogenaurach Telephone: 09132-744-0 Fax: 09132-744-1864 Email: [email protected] Internet: www.vipa.com 317-4PN23_000_CPU 317PN,2,EN - © 2018...
Page 3: Table Of Contents
VIPA System 300S Table of contents Table of contents General........................6 1.1 Copyright © VIPA GmbH ................. 6 1.2 About this manual..................... 7 1.3 Safety information..................... 8 Basics........................9 2.1 Safety information for users................9 2.2 Operating structure of a CPU................. 10 2.2.1 General......................
Page 4 Table of contents VIPA System 300S 5.10.1 Proceeding....................56 5.10.2 VIPA specific parameters................57 5.11 Project transfer..................... 61 5.11.1 Transfer via MPI/PROFIBUS..............61 5.11.2 Transfer via Ethernet................. 62 5.11.3 Transfer via memory card................63 5.12 Accessing the web server................64 5.13 Operating modes..................
Page 5 VIPA System 300S Table of contents 8.11 NCM diagnostic - Help for error diagnostic..........127 Deployment Ethernet communication - PROFINET........130 9.1 Basics PROFINET..................130 9.2 PROFINET installation guidelines..............132 9.3 PROFINET system limits................133 9.4 Fast introduction PROFINET................ 135 9.5 Commissioning and Initialization..............
Page 6: General
General VIPA System 300S Copyright © VIPA GmbH General 1.1 Copyright © VIPA GmbH All Rights Reserved This document contains proprietary information of VIPA and is not to be disclosed or used except in accordance with applicable agreements. This material is protected by the copyright laws. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to VIPA), except in accord- ance with applicable agreements, contracts or licensing, without the express written con- sent of VIPA and the business management owner of the material.
Page 7: About This Manual
VIPA System 300S General About this manual VIPA GmbH, Ohmstraße 4, 91074 Herzogenaurach, Germany Telefax: +49 9132 744-1204 EMail: [email protected] Technical support Contact your local VIPA Customer Service Organization representative if you encounter problems with the product or have questions regarding the product. If you are unable to locate a customer service centre, contact VIPA as follows: VIPA GmbH, Ohmstraße 4, 91074 Herzogenaurach, Germany Tel.: +49 9132 744-1150 (Hotline)
Page 8: Safety Information
General VIPA System 300S Safety information Supplementary information and useful tips. 1.3 Safety information Applications conforming The system is constructed and produced for: with specifications communication and process control general control and automation tasks industrial applications operation within the environmental conditions specified in the technical data installation into a cubicle DANGER! This device is not certified for applications in...
Page 9: Basics
VIPA System 300S Basics Safety information for users Basics 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.
Page 10: Operating Structure Of A Cpu
Basics VIPA System 300S Operating structure of a CPU > Operands 2.2 Operating structure of a CPU 2.2.1 General The CPU contains a standard processor with internal program memory. In combination with the integrated SPEED7 technology the unit provides a powerful solution for process automation applications within the System 300S family.
Page 11 VIPA System 300S Basics Operating structure of a CPU > Operands Process image and The user application can quickly access the process image of the inputs and outputs PIO/ periphery PII. You may manipulate the following types of data: individual Bits Bytes Words Double words...
Page 12: Cpu 317-4Pn23
Basics VIPA System 300S CPU 317-4PN23 2.3 CPU 317-4PN23 Overview The CPU 317-4PN23 bases upon the SPEED7 technology. This supports the CPU at pro- gramming and communication by means of co-processors that causes a power improve- ment for highest needs. Ò...
Page 13 VIPA System 300S Basics CPU 317-4PN23 Memory 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: Load memory 8Mbyte Code memory (50% of the work memory) Data memory (50% of the work memory) Work memory 4Mbyte...
Page 14: General Data
Basics VIPA System 300S General data 2.4 General data Conformity and approval Conformity 2014/35/EU Low-voltage directive 2014/30/EU EMC directive Approval 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...
Page 15 VIPA System 300S Basics General data Mounting conditions Mounting place In the control cabinet Mounting position Horizontal and vertical 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 8kV at air discharge (degree of severity 3), 4kV at contact discharge (degree of severity 2) EN 61000-4-3 HF field immunity (casing)
Page 16: Assembly And Installation Guidelines
Assembly and installation guidelines VIPA System 300S Overview Assembly and installation guidelines 3.1 Overview General This CPU is provided with a parallel SPEED-Bus that enables the additional connection of up to 10 modules from the SPEED-Bus periphery. While the standard peripheral modules are plugged-in at the right side of the CPU, the SPEED-Bus peripheral modules are connected via a SPEED-Bus bus connector at the left side of the CPU.
Page 17: Installation Dimensions
VIPA System 300S Assembly and installation guidelines Installation dimensions 3.2 Installation dimensions Dimensions Basic enclo- 2tier width (WxHxD) in mm: 80 x 125 x 120 sure Installation dimensions HB140 | CPU | 317-4PN23 | en | 18-01...
Page 18: Assembly Speed-Bus
Assembly and installation guidelines VIPA System 300S Assembly SPEED-Bus 3.3 Assembly SPEED-Bus Pre-manufactured SPEED- For the deployment of SPEED-Bus modules, a pre-manufactured SPEED-Bus rail is Bus profile rail required. This is available mounted on a profile rail with 2, 6 or 10 extension slots. Dimensions Order Number of modules SPEED-...
Page 19 VIPA System 300S Assembly and installation guidelines Assembly SPEED-Bus Installation of the profile Bolt the profile rail with the background (screw size: M6), so that you still have min- rail imum 65mm space above and 40mm below the profile rail. Please look for a low- impedance connection between profile rail and background.
Page 20 Assembly and installation guidelines VIPA System 300S Assembly SPEED-Bus To connect the SPEED-Bus modules, plug it between the triangular positioning helps to a slot marked with "SLOT ..." and pull it down. Only the "SLOT1 DCDC" allows you to plug-in either a SPEED-Bus module or an additional power supply.
Page 21: Assembly Standard Bus
VIPA System 300S Assembly and installation guidelines Assembly standard bus CAUTION! – The power supplies must be released before installation and repair tasks, i.e. before handling with the power supply or with the cabling you must disconnect current/voltage (pull plug, at fixed connection switch off the concerning fuse)! –...
Page 22 Assembly and installation guidelines VIPA System 300S Assembly standard bus Bus connector For the communication between the modules the System 300S uses a backplane bus connector. Backplane bus connectors are included in the delivering of the peripheral modules and are clipped at the module from the backside before installing it to the profile rail.
Page 23 VIPA System 300S Assembly and installation guidelines Assembly standard bus Assembly possibilities Please regard the allowed environment temperatures: horizontal assembly: from 0 to 60°C vertical assembly: from 0 to 50°C lying assembly: from 0 to 55°C Approach Bolt the profile rail with the background (screw size: M6), so that you still have min- imum 65mm space above and 40mm below the profile rail.
Page 24: Cabling
Assembly and installation guidelines VIPA System 300S Cabling 3.5 Cabling CAUTION! – The power supplies must be released before installation and repair tasks, i.e. before handling with the power supply or with the cabling you must disconnect current/voltage (pull plug, at fixed connection switch off the concerning fuse)! –...
Page 25: Installation Guidelines
VIPA System 300S Assembly and installation guidelines Installation guidelines 3.6 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.
Page 26 Assembly and installation guidelines VIPA System 300S Installation guidelines 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. –...
Page 27: Hardware Description
VIPA System 300S Hardware description Properties Hardware description 4.1 Properties CPU 317-4PN23 SPEED7 technology and SPEED-Bus integrated 4Mbyte work memory integrated (2Mbyte code, 2Mbyte data) Work memory expandable to max. 8Mbyte (4Mbyte code, 4Mbyte data) 8Mbyte load memory X3: PROFIBUS DP/PtP interface: PROFIBUS DP master (DP-V0, DP-V1) X8: PROFINET IO controller: PROFINET in accordance with conformance class A with integrated Ethernet CP X5: Ethernet PG/OP channel...
Page 28: Structure
Hardware description VIPA System 300S Structure > Interfaces 4.2 Structure 4.2.1 General CPU 317-4PN23 LED status indication PROFIBUS DP master Storage media slot (lockable) LED status indication CPU part LED status indication PROFINET IO controller Operating mode switch CPU X5: Ethernet PG/OP channel X2: MPI interface X3: PROFIBUS DP/PtP interface X8: PROFINET IO controller...
Page 29 VIPA System 300S Hardware description Structure > Interfaces X2: MPI interface 9pin SubD jack: The MPI interface serves for the connection between programming unit and CPU. By means of this the project engineering and programming happens. MPI serves for communication between several CPUs or between HMIs and CPU. Standard setting is MPI Address 2.
Page 30: Memory Management
Hardware description VIPA System 300S Structure > Battery backup for clock and RAM 4.2.3 Memory management Memory 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: Load memory 8Mbyte Code memory (50% of the work memory) Data memory (50% of the work memory)
Page 31: Operating Mode Switch
VIPA System 300S Hardware description Structure > Operating mode switch 4.2.6 Operating mode switch With the operating mode switch you may switch the CPU between STOP and RUN. During the transition from STOP to RUN the operating mode START-UP is driven by the CPU.
Page 32: Leds
Hardware description VIPA System 300S Structure > LEDs 4.2.7 LEDs LEDs CPU Meaning (RUN) (STOP) (SFAIL) (FRCE) (MMC) green yellow yellow yellow Boot-up after PowerON - as soon as the CPU is supplied with 5V, the green PW-LED (Power) is on. Firmware is loaded.
Page 33 VIPA System 300S Hardware description Structure > LEDs Ethernet PG/OP channel Meaning (Link/Activity) (Speed) green green The Ethernet PG/OP channel is physically connected to Ethernet. There is no physical connection. Shows Ethernet activity. flickers The Ethernet interface of the Ethernet PG/OP channel has a transfer rate of 100Mbit.
Page 34 Hardware description VIPA System 300S Structure > LEDs Meaning (RUN) (ERR) green green Alternate blinking at configuration faults. Slave exchanges data with the master. LEDs PROFINET IO con- troller X8 MT (Maintenance) BF (Bus error) Meaning yellow Bus error, no connection to sub net/switch wrong transfer rate Full-duplex-transmission is not activated Failure of a connected IO device...
Page 35: Technical Data
VIPA System 300S Hardware description Technical data 4.3 Technical data Order no. 317-4PN23 Type CPU 317PN SPEED-Bus ü 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) 270 mA Current consumption (rated value)
Page 36 Hardware description VIPA System 300S Technical data Order no. 317-4PN23 Supply voltage display green LED Group error display red SF LED Channel error display none Command processing times Bit instructions, min. 0.01 µs Word instruction, min. 0.01 µs Double integer arithmetic, min. 0.01 µs Floating-point arithmetic, min.
Page 37 VIPA System 300S Hardware description Technical data Order no. 317-4PN23 Time Real-time clock buffered ü Clock buffered period (min.) Type of buffering Vanadium Rechargeable Lithium Battery Load time for 50% buffering period 20 h Load time for 100% buffering period 48 h Accuracy (max.
Page 38 Hardware description VIPA System 300S Technical data Order no. 317-4PN23 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.
Page 39 VIPA System 300S Hardware description Technical data Order no. 317-4PN23 S7 basic communication ü S7 communication ü S7 communication as server ü S7 communication as client Transmission speed, min. 19.2 kbit/s Transmission speed, max. 12 Mbit/s Functionality PROFIBUS master Number of connections, max. PG/OP channel ü...
Page 40 Hardware description VIPA System 300S Technical data Order no. 317-4PN23 Transfer memory inputs, max. 244 Byte Transfer memory outputs, max. 244 Byte Address areas, max. User data per address area, max. 32 Byte Point-to-point communication PtP communication ü Interface isolated ü...
Page 41 VIPA System 300S Hardware description Technical data Order no. 317-4PN23 Isochronous mode Parallel operation as controller and I-Device Functionality RJ45 interfaces Type Type of interface Ethernet 10/100 MBit Connector RJ45 Electrically isolated ü PG/OP channel ü Number of connections, max. Productive connections Fieldbus Type...
Page 42 Hardware description VIPA System 300S Technical data Order no. 317-4PN23 UDP-broadcast-connections Ethernet open communication Number of connections, max. ISO on TCP connections (RFC 1006) TSEND, TRCV, TCON, TDISCON User data per ISO on TCP connection, max. 8 KB TCP-Connections native TSEND, TRCV, TCON, TDISCON User data per native TCP connection, max.
Page 43: Deployment Cpu 317-4Pn23
VIPA System 300S Deployment CPU 317-4PN23 Start-up behavior Deployment CPU 317-4PN23 5.1 Assembly Ä Chapter 3 ‘Assembly and Information about assembly and cabling: installation guidelines’ on page 16 5.2 Start-up behavior Turn on power supply After the power supply has been switched on, the CPU changes to the operating mode the operating mode lever shows.
Page 44: Addressing
Deployment CPU 317-4PN23 VIPA System 300S Addressing 5.3 Addressing Backplane bus periphery The CPU 317-4PN23 provides an I/O area (address 0 ... max. peripheral address) and a process image of the in- and outputs (each address 0 ... 255). The process image stores the signal states additionally in a separate memory area.
Page 45 VIPA System 300S Deployment CPU 317-4PN23 Addressing SPEED-Bus DIOs: Start address = 4×(slot-101)+128 AIOs, FMs, CPs: Start address = 256×(slot-101)+2048 HB140 | CPU | 317-4PN23 | en | 18-01...
Page 46 Deployment CPU 317-4PN23 VIPA System 300S Addressing Example for automatic The following sample shows the functionality of the automatic address allocation sepa- address allocation rated for standard bus and SPEED-Bus: HB140 | CPU | 317-4PN23 | en | 18-01...
Page 47: Hardware Configuration - Cpu
VIPA System 300S Deployment CPU 317-4PN23 Hardware configuration - CPU 5.4 Hardware configuration - CPU Precondition The configuration of the CPU takes place at the Siemens ‘hardware configurator’ . The hardware configurator is part of the Siemens SIMATIC Manager. It serves for project engi- neering.
Page 48: Hardware Configuration - I/O Modules
Deployment CPU 317-4PN23 VIPA System 300S Hardware configuration - I/O modules 5.5 Hardware configuration - I/O modules Hardware configuration of After the hardware configuration place the System 300 modules in the plugged sequence the modules starting with slot 4. Parametrization For parametrization double-click during the project engineering at the slot overview on the module you want to parameterize.
Page 49: Hardware Configuration - Ethernet Pg/Op Channel
VIPA System 300S Deployment CPU 317-4PN23 Hardware configuration - Ethernet PG/OP channel 5.6 Hardware configuration - Ethernet PG/OP channel Overview The CPU 317-4PN23 has an integrated Ethernet PG/OP channel. This channel allows you to program and remote control your CPU. The PG/OP channel also gives you access to the internal web page that contains information about firmware version, connected I/O devices, current cycle times etc.
Page 50: Hardware Configuration - Communication
Deployment CPU 317-4PN23 VIPA System 300S Hardware configuration - SPEED-Bus > Preconditions Take IP address parame- Open the Siemens hardware configurator und configure the Siemens CPU 317-2 ters in project PN/DP (6ES7 317-2EK14-0AB0 V3.2). Configure the modules at the standard bus. For the Ethernet PG/OP channel you have to configure a Siemens CP 343-1 (SIMATIC 300 \ CP 300 \ Industrial Ethernet \CP 343-1 \ 6GK7 343-1EX11 0XE0) always below the really plugged modules.
Page 51: Proceeding
VIPA System 300S Deployment CPU 317-4PN23 Hardware configuration - SPEED-Bus > Proceeding Installation of the The GSD (Geräte-Stamm-Datei) is online available in the following language versions. SPEEDBUS.GSD Further language versions are available on inquires: Name Language SPEEDBUS.GSD German (default) SPEEDBUS.GSG German SPEEDBUS.GSE English...
Page 52: Setting Standard Cpu Parameters
Deployment CPU 317-4PN23 VIPA System 300S Setting standard CPU parameters > Parameters CPU 5.9 Setting standard CPU parameters 5.9.1 Parameterization via Siemens CPU Parameterization via Sie- Since the CPU is to be configured as Siemens CPU 317-2 PN/DP (6ES7 mens CPU 317-2EK14-0AB0 V3.2) in the Siemens hardware configurator, the standard parameters of the VIPA CPU may be set with "Object properties"...
Page 53 VIPA System 300S Deployment CPU 317-4PN23 Setting standard CPU parameters > Parameters CPU Startup 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.
Page 54 Deployment CPU 317-4PN23 VIPA System 300S Setting standard CPU parameters > Parameters CPU The selected memory byte cannot be used for temporary data storage. Retentive Memory Number of Memory bytes from MB0 – Enter the number of retentive memory bytes from memory byte 0 onwards. Number of S7 Timers from T0 –...
Page 55: Parameters For Dp
VIPA System 300S Deployment CPU 317-4PN23 Setting standard CPU parameters > Parameters for DP Diagnostics/Clock Report cause of STOP – Activate this parameter, if the CPU should report the cause of STOP to PG respectively OP on transition to STOP. Number of messages in the diagnostics buffer –...
Page 56: Parameters For Mpi/Dp
Deployment CPU 317-4PN23 VIPA System 300S Setting VIPA specific CPU parameters > Proceeding 5.9.4 Parameters for MPI/DP The properties dialog of the MPI interface is opened via a double click to the sub module MPI/DP. General Short description: Here the short description "MPI/DP" for the MPI interface is speci- fied.
Page 57: Vipa Specific Parameters
VIPA System 300S Deployment CPU 317-4PN23 Setting VIPA specific CPU parameters > VIPA specific parameters Installation of the The GSD (Geräte-Stamm-Datei) is online available in the following language versions. SPEEDBUS.GSD Further language versions are available on inquires: Name Language SPEEDBUS.GSD German (default) SPEEDBUS.GSG German...
Page 58 Deployment CPU 317-4PN23 VIPA System 300S Setting VIPA specific CPU parameters > VIPA specific parameters 5.10.2.1 Function RS485 X3 Using this parameter the RS485 interface may be switched to PtP communication (point to point) respectively the synchronization between DP master system and CPU may be set: Deactivated Deactivates the RS485 interface.
Page 59 VIPA System 300S Deployment CPU 317-4PN23 Setting VIPA specific CPU parameters > VIPA specific parameters PROFIBUS DP SyncOut In this operating mode the cycle time of the VIPA DP master system depends on the CPU cycle time. After CPU start-up the DP master gets synchronized. As soon as their cycle is passed they wait for the next synchronization impulse with output data of the CPU.
Page 60 Deployment CPU 317-4PN23 VIPA System 300S Setting VIPA specific CPU parameters > VIPA specific parameters 5.10.2.2 Token Watch By presetting the PROFIBUS bus parameters within the hardware configuration a token time for the PROFIBUS results. The token time defines the duration until the token rea- ches the DP master again.
Page 61: Project Transfer
VIPA System 300S Deployment CPU 317-4PN23 Project transfer > Transfer via MPI/PROFIBUS 5.11 Project transfer Overview There are the following possibilities for project transfer into the CPU: Transfer via MPI/PROFIBUS Transfer via Ethernet Transfer via memory card 5.11.1 Transfer via MPI/PROFIBUS General For transfer via MPI/PROFIBUS the CPU has the following interface: X2: MPI interface...
Page 62: Transfer Via Ethernet
Deployment CPU 317-4PN23 VIPA System 300S Project transfer > Transfer via Ethernet Set in the register MPI the transfer parameters of your MPI net and type a valid address. Switch to the register Local connection. Set the COM port of the PC and the transfer rate 38400baud for the MPI program- ming cable.
Page 63: Transfer Via Memory Card
VIPA System 300S Deployment CPU 317-4PN23 Project transfer > Transfer via memory card 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.
Page 64: Accessing The Web Server
Deployment CPU 317-4PN23 VIPA System 300S Accessing the web server 5.12 Accessing the web server Access to the web server There is a web server, which can be accessed via the IP address of the Ethernet PG/OP channel with an Internet browser. At the web page information about the CPU and its connected modules can be found.
Page 65 VIPA System 300S Deployment CPU 317-4PN23 Accessing the web server X2 (RS485/COM1) Operating mode RS485 MPI: MPI operation X3 (RS485/COM2) DPM-async DPM: DP master operation or PtP: point to point operation PG/OP Ethernet Port PROFINET Port Card Information Type Product S/N 6BC34010 Size 493617152 bytes...
Page 66 Deployment CPU 317-4PN23 VIPA System 300S Accessing the web server Data Currently nothing is displayed here. Parameter Currently nothing is displayed here. Here the IP address data of your Ethernet PG/OP channel are shown. Info - Overview DP master Info - Expert View Internal Information Slot 201 VIPA 342-1DA70...
Page 67 VIPA System 300S Deployment CPU 317-4PN23 Accessing the web server Info - Overview PROFINET-IO controller Info - Expert View Internal Information CPU component: 31x-PN Module Type 0xACDB0080 Information for support Module Firmware Information Bb000429 V1.1.0.12 AB000125 V0.1.0.3 PRODUCT VIPA 31x-PN V1.1.2.0 Px000300.pkg Hx000075...
Page 68 Deployment CPU 317-4PN23 VIPA System 300S Accessing the web server Hardware Last value Average of last 10 values Minimum load Maximum load Network IP address 172.16.129.210 Subnet mask 255.255.255.0 Gateway address 172.16.129.210 MAC address 00:20:D5:77:91:10 Link mode 100 Mbps - Full duplex EMAC statistics Frames Transmitted OK Single Collision Frame...
Page 69 VIPA System 300S Deployment CPU 317-4PN23 Accessing the web server Data - Input data Offset Width Value (dec) Value (hex) Data - Output data Offset Width Value (dec) Value (hex) New Value (hex) HB140 | CPU | 317-4PN23 | en | 18-01...
Page 70: Operating Modes
Deployment CPU 317-4PN23 VIPA System 300S Operating modes > Overview 5.13 Operating modes 5.13.1 Overview The CPU can be in one of 4 operating modes: Operating mode STOP Operating mode START-UP Operating mode RUN Operating mode HOLD Certain conditions in the operating modes START-UP and RUN require a specific reaction from the system program.
Page 71 VIPA System 300S Deployment CPU 317-4PN23 Operating modes > Overview Set the breakpoint with ‘Debug è Set Breakpoint’. ð The according command line is marked with a circle. To activate the breakpoint click on ‘Debug è Breakpoints Active’. ð The circle is changed to a filled circle. Bring your CPU into RUN.
Page 72: Function Security
Deployment CPU 317-4PN23 VIPA System 300S Operating modes > Function security 5.13.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.
Page 73: Overall Reset
VIPA System 300S Deployment CPU 317-4PN23 Overall reset 5.14 Overall reset Overview During the overall reset the entire user memory is erased. Data located in the memory card is not affected. If you have assigned IP address data to your PROFINET IO con- troller, these remain until there is a new PowerON.
Page 74: Firmware Update
Deployment CPU 317-4PN23 VIPA System 300S Firmware update 5.15 Firmware update Overview There is the opportunity to execute a firmware update for the CPU and its compo- nents via memory card. For this an accordingly prepared memory card must be in the CPU during the startup.
Page 75 VIPA System 300S Deployment CPU 317-4PN23 Firmware update Navigate via ‘System 300S è CPU’ to your CPU and download the zip file to your Extract the zip file and copy the extracted pkg files to 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 the firm- Ä...
Page 76: Reset To Factory Settings
Deployment CPU 317-4PN23 VIPA System 300S Reset to factory settings 5.16 Reset to factory settings Proceeding With the following proceeding the internal RAM of the CPU is completely deleted and the CPU is reset to delivery state. 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! A factory reset may also be executed by the command FACTORY_RESET.
Page 77: Deployment Storage Media - Mmc, Mcc
VIPA System 300S Deployment CPU 317-4PN23 Deployment storage media - MMC, MCC 5.17 Deployment storage media - MMC, MCC Overview At this slot the following storage media can be plugged: SD respectively MMC (Multimedia card) – External memory card for programs and firmware. MCC - Memory configuration card –...
Page 78 Deployment CPU 317-4PN23 VIPA System 300S Deployment storage media - MMC, MCC You may use the MCC also as "normal" MMC for storing your project. If the memory expansion on the MCC exceeds the maximum extendible memory range of the CPU, the maximum possible memory of the CPU is automatically used. You may determine the recent memory extension and the remaining time after pulling the MCC via the integrated web page.
Page 79: Extended Know-How Protection
VIPA System 300S Deployment CPU 317-4PN23 Extended know-how protection 5.18 Extended know-how protection Overview Besides the "standard" Know-how protection the SPEED7 CPUs from VIPA provide an "extended" know-how protection that serves a secure block protection for accesses of 3. persons. Standard protection –...
Page 80: Cmd - Auto Commands
Deployment CPU 317-4PN23 VIPA System 300S CMD - auto commands 5.19 CMD - auto commands Overview A command file at a memory card is automatically executed under the following condi- tions: CPU is in STOP and memory card is stuck After each PowerON Command file The command file is a text file, which consists of a command sequence to be stored as...
Page 81: Diagnostic Entries
VIPA System 300S Deployment CPU 317-4PN23 Diagnostic entries 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) WEBPAGE Store web page as "webpage.htm" (0xE804) DIAGBUF Store diagnostics buffer of the CPU as "diagbuff.txt"...
Page 82: Control And Monitoring Of Variables With Test Functions
Deployment CPU 317-4PN23 VIPA System 300S Control and monitoring of variables with test functions 5.21 Control and monitoring of variables with test functions Overview For troubleshooting purposes and to display the status of certain variables you can access certain test functions via the menu item Debug of the Siemens SIMATIC Man- ager.
Page 83 VIPA System 300S Deployment CPU 317-4PN23 Control and monitoring of variables with test functions ‘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’...
Page 84: Deployment Ptp Communication
Deployment PtP communication VIPA System 300S Deployment PtP communication HB140 | CPU | 317-4PN23 | en | 18-01...
Page 85: Fast Introduction
VIPA System 300S Deployment PtP communication Fast introduction 6.1 Fast introduction General The CPU has a PROFIBUS/PtP interface with a fix pinout. After an overall reset the inter- face is deactivated. By appropriate configuration the PtP function (point to point) can be enabled: PtP functionality –...
Page 86: Principle Of The Data Transfer
Deployment PtP communication VIPA System 300S Deployment of RS485 interface for PtP 6.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. 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.
Page 87 VIPA System 300S Deployment PtP communication Deployment of RS485 interface for PtP Installation of the The GSD (Geräte-Stamm-Datei) is online available in the following language versions. SPEEDBUS.GSD Further language versions are available on inquires: Name Language SPEEDBUS.GSD German (default) SPEEDBUS.GSG German SPEEDBUS.GSE English...
Page 88 Deployment PtP communication VIPA System 300S Deployment of RS485 interface for PtP Setting PtP parameters By double clicking the CPU 317-4PN23 placed in the slave system the properties dialog of the CPU may be opened. Switch the Parameter ‘Function RS485 X3’ to ‘PtP’ . Properties RS485 Logical states represented by voltage differences between the two cores of a twisted pair cable...
Page 89: Parametrization
VIPA System 300S Deployment PtP communication Communication > FC/SFC 217 - SER_SND - Send to PtP Connection RS485 interface Periphery *) For traffic-free data transfer use a terminating resistor of approximately 6.4 Parametrization 6.4.1 FC/SFC 216 - SER_CFG - Parametrization PtP The parametrization happens during runtime deploying the FC/SFC 216 (SER_CFG).
Page 90: Fc/Sfc 218 - Ser_Rcv - Receive From Ptp
Deployment PtP communication VIPA System 300S Protocols and procedures 6.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.
Page 91 VIPA System 300S Deployment PtP communication Protocols and procedures 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.
Page 92 Deployment PtP communication VIPA System 300S Protocols and procedures Max. 32 participants Simple and secure telegram frame It is essential: You may connect 1 master and max. 31 slaves at the bus The single slaves are addressed by the master via an address sign in the telegram. The communication happens exclusively in half-duplex operation.
Page 93 VIPA System 300S Deployment PtP communication Protocols and procedures After a send command, the acknowledgement telegram must be read by a call of the FC/SFC 218 SER_RCV. The request telegrams send by the master and the respond telegrams of a slave have the following structure: Telegram structure Start sign...
Page 94: Modbus - Function Codes
Deployment PtP communication VIPA System 300S Modbus - Function codes 6.7 Modbus - Function codes Naming convention Modbus has some naming conventions: Modbus differentiates between bit and word access; bits = "Coils" and words = "Reg- ister". Bit inputs are referred to as "Input-Status" and bit outputs as "Coil-Status". word inputs are referred to as "Input-Register"...
Page 95 VIPA System 300S Deployment PtP communication Modbus - Function codes Code Command Description Read n bits Read n bits of master output area 0x Read n bits Read n bits of master input area 1x Read n words Read n words of master output area 4x Read n words Read n words master input area 3x Write 1 bit...
Page 96 Deployment PtP communication VIPA System 300S Modbus - Function codes 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.
Page 97 VIPA System 300S Deployment PtP communication Modbus - Function codes 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 1byte 1byte 1word 1word 1word Respond telegram...
Page 98: Modbus - Example Communication
Deployment PtP communication VIPA System 300S Modbus - Example communication 6.8 Modbus - Example communication Overview The example establishes a communication between a master and a slave via Modbus. The following combination options are shown: CPU 31xS as Modbus RTU master CPU 21xSER-1 as Modbus RTU slave Siemens SIMATIC Manager and possibilities for the project transfer Modbus cable connection...
Page 99 VIPA System 300S Deployment PtP communication Modbus - Example communication HB140 | CPU | 317-4PN23 | en | 18-01...
Page 100: Deployment Profibus Communication
Deployment PROFIBUS communication VIPA System 300S Overview Deployment PROFIBUS communication 7.1 Overview PROFIBUS DP 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.
Page 101: Fast Introduction
VIPA System 300S Deployment PROFIBUS communication Fast introduction 7.2 Fast introduction Overview The PROFIBUS DP master is to be configured in the hardware configurator. Here the configuration happens by means of the sub module X1 (DP) of the Siemens CPU. Steps of configuration For the configuration of the PROFIBUS DP master please follow the following approach: Hardware configuration - CPU...
Page 102: Hardware Configuration - Cpu
Deployment PROFIBUS communication VIPA System 300S Hardware configuration - CPU 7.3 Hardware configuration - CPU Precondition The configuration of the CPU takes place at the Siemens ‘hardware configurator’ . The hardware configurator is part of the Siemens SIMATIC Manager. It serves for project engi- neering.
Page 103: Deployment As Profibus Dp Master
VIPA System 300S Deployment PROFIBUS communication Deployment as PROFIBUS DP master 7.4 Deployment as PROFIBUS DP master Precondition The hardware configuration described before was established. Proceeding Open the properties dialog of the DP interface of the CPU by means of a double- click at ‘MPI/DP’...
Page 104: Deployment As Profibus Dp Slave
Deployment PROFIBUS communication VIPA System 300S Deployment as PROFIBUS DP slave 7.5 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.
Page 105 VIPA System 300S Deployment PROFIBUS communication Deployment as PROFIBUS DP slave Switch at Operating mode to "DP master" and confirm the dialog with [OK]. 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.
Page 106: Profibus Installation Guidelines
Deployment PROFIBUS communication VIPA System 300S PROFIBUS installation guidelines 7.6 PROFIBUS installation guidelines PROFIBUS in general A PROFIBUS DP network may only be built up in linear structure. PROFIBUS DP consists of minimum one segment with at least one master and one slave.
Page 107 VIPA System 300S Deployment PROFIBUS communication PROFIBUS installation guidelines 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.
Page 108 Deployment PROFIBUS communication VIPA System 300S PROFIBUS installation guidelines 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...
Page 109: Commissioning And Start-Up Behavior
VIPA System 300S Deployment PROFIBUS communication Commissioning and Start-up behavior 7.7 Commissioning and Start-up behavior Start-up on delivery In delivery the CPU is overall reset. The PROFIBUS part is deactivated and its LEDs are off after Power ON. Online with bus parameter The DP master can be served with bus parameters by means of a hardware configura- without slave project tion.
Page 110: Deployment Ethernet Communication - Productive
Deployment Ethernet communication - productive VIPA System 300S Basics - Industrial Ethernet in automation Deployment Ethernet 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.
Page 111: Basics - Iso/Osi Reference Model
VIPA System 300S Deployment Ethernet 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.
Page 112 Deployment Ethernet communication - productive VIPA System 300S 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.
Page 113: Basics - Terms
VIPA System 300S Deployment Ethernet communication - productive 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.
Page 114: Basics - Protocols
Deployment Ethernet communication - productive VIPA System 300S 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 Ä...
Page 115: Basics - Ip Address And Subnet
VIPA System 300S Deployment Ethernet communication - productive 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’...
Page 116 Deployment Ethernet communication - productive VIPA System 300S 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 and the PROFINET IO con- troller do not have an IP address.
Page 117: Fast Introduction
VIPA System 300S Deployment Ethernet communication - productive Commissioning and initialization 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.) 8.6 Fast introduction Overview...
Page 118: Hardware Configuration - Cpu Via Ethernet
Deployment Ethernet communication - productive VIPA System 300S Hardware configuration - CPU via Ethernet 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.3 &...
Page 119 VIPA System 300S Deployment Ethernet communication - productive Hardware configuration - CPU via Ethernet Parametrization of the IP Open the property window of the internal PROFINET IO controller via double-click on the address data for the component PN-IO: PROFINET IO controller At ‘General’...
Page 120: Configure Siemens S7 Connections
Deployment Ethernet communication - productive VIPA System 300S Configure Siemens S7 connections 8.9 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.
Page 121 VIPA System 300S Deployment Ethernet communication - productive Configure Siemens S7 connections 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.
Page 122 Deployment Ethernet communication - productive VIPA System 300S Configure Siemens S7 connections Projecting connections For the project engineering of connections, open the connection list by selecting the according CPU. Choose Insert new connection in the context menu: Connection partner (partner station) A dialog window opens where you may choose the connection partner and the connection type.
Page 123 VIPA System 300S Deployment Ethernet communication - productive Configure Siemens S7 connections Connection types With this CPU exclusively Siemens S7 connection may be configured with Siemens NetPro. Siemens S7 connection For data transfer with Siemens S7 connections the FB/SFB VIPA handling blocks are necessary;...
Page 124 Deployment Ethernet communication - productive VIPA System 300S Configure Siemens S7 connections In the following every relevant parameter of a Siemens S7 connection is described: 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.
Page 125 VIPA System 300S Deployment Ethernet communication - productive Configure Siemens S7 connections 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.
Page 126: Configure Open Communication
Deployment Ethernet communication - productive VIPA System 300S Configure Open Communication 8.10 Configure Open Communication Connection-oriented pro- Connection-oriented protocols establish a (logical) connection to the communication tocols partner before data transmission is started. And if necessary they terminate the connection after the data transfer was finished. Connection-oriented protocols are used for data transmission when reliable, guaran- teed delivery is of particular importance.
Page 127: Ncm Diagnostic - Help For Error Diagnostic
VIPA System 300S Deployment Ethernet communication - productive NCM diagnostic - Help for error diagnostic 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.
Page 128 Deployment Ethernet communication - productive VIPA System 300S NCM diagnostic - Help for error diagnostic Please always enter for the PROFINET IO controller as destination parameter 0 as module rack and 125 as slot. The CP can be reached exclusively with these settings. The following pages contain a short description of the NCM diagnostic.
Page 129 VIPA System 300S Deployment Ethernet communication - productive NCM diagnostic - Help for error diagnostic Set the following parameters at destination station: Attachment...: Ind. Ethernet TCP/IP Node addr.: Enter the IP address of the CP Rack/slot: For the VIPA PROFINET IO controller please enter 0 for module rack and 125 as slot.
Page 130: Deployment Ethernet Communication - Profinet
Deployment Ethernet communication - PROFINET VIPA System 300S Basics PROFINET Deployment Ethernet communication - PROFINET 9.1 Basics PROFINET General PROFINET is an open Industrial Ethernet Standard from PROFIBUS & PROFINET International (PI) for automation. PROFINET is standardized in the IEC 61158. 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.
Page 131 VIPA System 300S Deployment Ethernet communication - PROFINET Basics PROFINET Wireless communication via Bluetooth respectively WLAN 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: IO controller IO device...
Page 132: Profinet Installation Guidelines
Deployment Ethernet communication - PROFINET VIPA System 300S PROFINET installation guidelines 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 mainte- nance have all served to increase vulnerability.
Page 133: Profinet System Limits
VIPA System 300S Deployment Ethernet communication - PROFINET PROFINET system limits Tree If you interconnect several star structures, you obtain a tree network topology. Example network 9.3 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.
Page 134 Deployment Ethernet communication - PROFINET VIPA System 300S PROFINET system limits The PROFINET IO controller has the following system limits: Max. Number output bytes per ms: 800 Max. Number output bytes per device: 256 Input bytes per ms Input bytes per ms Number of devices C Number input bytes per device A Refresh time per device...
Page 135: Fast Introduction Profinet
VIPA System 300S Deployment Ethernet communication - PROFINET Fast introduction PROFINET 9.4 Fast introduction PROFINET Overview 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.
Page 136: Commissioning And Initialization
Deployment Ethernet communication - PROFINET VIPA System 300S Commissioning and Initialization 9.5 Commissioning and Initialization Assembly and commis- Install your System 300S with your CPU. sioning Wire the system by connecting cables for voltage supply and signals Connect your PROFINET IO controller with Ethernet. Switch on the power supply.
Page 137: Hardware Configuration - Cpu
VIPA System 300S Deployment Ethernet communication - PROFINET Hardware configuration - CPU 9.6 Hardware configuration - CPU Precondition The configuration of the CPU takes place at the Siemens ‘hardware configurator’ . The hardware configurator is part of the Siemens SIMATIC Manager. It serves for project engi- neering.
Page 138: Parameters - Profinet Io Controller
Deployment Ethernet communication - PROFINET VIPA System 300S Parameters - PROFINET IO controller > PN-IO 9.7 Parameters - PROFINET IO controller 9.7.1 Precondition To parametrize the PROFINET IO controller of the CPU, the following conditions must be fulfilled: The PROFINET IO controller is online reachable, this means an initialization was established.
Page 139: Port 1
VIPA System 300S Deployment Ethernet communication - PROFINET Parameters - PROFINET IO controller > Port 1 Synchronization This tab shows the synchronization properties of the IO controller. Here nothing can be changed. Time-of-day synchroniza- Here you can configure time-of-day master for time-of-day synchronization in the network. tion NTP (Network Time Protocol) is used to implement a TCP/IP protocol for time-of-day syn- chronization in networks.
Page 140: Configuration Profinet Io Device
Deployment Ethernet communication - PROFINET VIPA System 300S Configuration PROFINET IO device 9.8 Configuration PROFINET IO device Install GSDML The modules, which may be configured here are listed in the hardware catalog. 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.
Page 141: Configuration Profinet-I-Device / Shared-Device
VIPA System 300S Deployment Ethernet communication - PROFINET Configuration PROFINET-I-Device / Shared-Device 9.9 Configuration PROFINET-I-Device / Shared-Device General I-Device (Intelligent device) offers PROFINET I/O communication of a CPU with I/O periphery as "intelligent device" to a higher-lever CPU. Here the communication hap- pens by means of an I/O area, which was defined in the I-Device, before.
Page 142: Topology - Configuration
Deployment Ethernet communication - PROFINET VIPA System 300S Device replacement without exchangeable medium/PG 9.10 Topology - Configuration 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"...
Page 143 VIPA System 300S Deployment Ethernet communication - PROFINET 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.
Page 144: Replace Device
Deployment Ethernet communication - PROFINET VIPA System 300S Device replacement without exchangeable medium/PG > Replace device 9.11.1 Replace device 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: For this connect your "replace device"...
Page 145: Commissioning And Start-Up Behaviour
VIPA System 300S Deployment Ethernet communication - PROFINET Commissioning and start-up behaviour 9.12 Commissioning and start-up behaviour Start-up on delivery In the delivery state the CPU is overall reset. The PROFINET part is deactivated and its LEDs are off after PowerON. Online with bus parame- For the communication between IO controller and IO device the ways for the commu- ters without project...
Page 146: Profinet Diagnostics
Deployment Ethernet communication - PROFINET VIPA System 300S PROFINET diagnostics > Diagnostics during runtime in the user program 9.13 PROFINET diagnostics 9.13.1 Overview There are the following possibilities to get diagnostics information from your system: Diagnostics with the configuration and engineering tool Diagnostics during runtime in the user program (OB 1, SFB 52) Diagnostics via OB start information Diagnostics via status LEDs...
Page 147 VIPA System 300S Deployment Ethernet communication - PROFINET PROFINET diagnostics > Diagnostics during runtime in the user program Example OB1 For the cyclic access to the diagnostics data of the system SLIO module 050-1BA00 the following 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 M10.1 'start transfer of record (REQ:=1)
Page 148: Diagnostics Via Ob Start Information
Deployment Ethernet communication - PROFINET VIPA System 300S PROFINET diagnostics > Diagnostics via OB start information 9.13.4 Diagnostics via OB start information 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.
Page 149: Diagnostics Via Status Leds
VIPA System 300S Deployment Ethernet communication - PROFINET PROFINET diagnostics > Diagnostics via status LEDs 9.13.5 Diagnostics via status LEDs LEDs PROFINET IO con- troller X8 MT (Maintenance) BF (Bus error) Meaning yellow Bus error, no connection to sub net/switch wrong transfer rate Full-duplex-transmission is not activated Failure of a connected IO device...
Page 150: Configuration With Tia Portal
Configuration with TIA Portal VIPA System 300S TIA Portal - Work environment > Work environment of the TIA Portal Configuration with TIA Portal 10.1 TIA Portal - Work environment 10.1.1 General General In this chapter the project engineering of the VIPA CPU in the Siemens TIA Portal is shown.
Page 151 VIPA System 300S Configuration with TIA Portal TIA Portal - Work environment > Work environment of the TIA Portal Areas of the Project view The Project view is divided into the following areas: Menu bar with toolbars Project tree with Details view Project area Device overview of the project respectively area for block programming Properties dialog of a device (parameter) respectively information area...
Page 152: Tia Portal - Hardware Configuration - Cpu
Configuration with TIA Portal VIPA System 300S TIA Portal - Hardware configuration - CPU 10.2 TIA Portal - Hardware configuration - CPU Configuration Siemens With the Siemens TIA Portal the CPU from VIPA is to be configured as CPU 317-2 PN/DP (6ES7 317-2EK14-0AB0 V3.2) from Siemens.
Page 153: Tia Portal - Hardware Configuration - I/O Modules
VIPA System 300S Configuration with TIA Portal TIA Portal - Hardware configuration - I/O modules 10.3 TIA Portal - Hardware configuration - I/O modules Hardware configuration of After the hardware configuration of the CPU place the System 300 modules at the bus in the modules the plugged sequence.
Page 154: Tia Portal - Hardware Configuration - Ethernet Pg/Op Channel
Configuration with TIA Portal VIPA System 300S TIA Portal - Hardware configuration - Ethernet PG/OP channel 10.4 TIA Portal - Hardware configuration - Ethernet PG/OP channel Overview The CPU has an integrated Ethernet PG/OP channel. This channel allows you to pro- gram and remote control your CPU.
Page 155 VIPA System 300S Configuration with TIA Portal TIA Portal - Hardware configuration - Ethernet PG/OP channel Confirm with [Assign IP configuration]. ð 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.
Page 156: Tia Portal - Hardware Configuration - Pg/Op Via Profinet
Configuration with TIA Portal VIPA System 300S TIA Portal - Hardware configuration - PG/OP via PROFINET Device overview: Module Slot Type PLC... CPU ... DI... DI... DO... DO... DIO... DIO... AI... AI... AO... AO... CP 343-1 CP 343-1 10.5 TIA Portal - Hardware configuration - PG/OP via PROFINET Overview The CPU has an Ethernet interface X8 integrated for PROFINET.
Page 157 VIPA System 300S Configuration with TIA Portal TIA Portal - Hardware configuration - PG/OP via PROFINET 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 TIA Portal with the following pro- ceeding: Start the Siemens TIA Portal.
Page 158: Tia Portal - Setting Vipa Specific Cpu Parameters
Configuration with TIA Portal VIPA System 300S TIA Portal - Setting VIPA specific CPU parameters Take IP address parame- Open your project. ters in project If not already done, configure in the ‘Device configuration’ a Siemens CPU 317-2 PN/DP (6ES7 317-2EK14-0AB0 V3.2). Open the "Property"...
Page 159 VIPA System 300S Configuration with TIA Portal TIA Portal - Setting VIPA specific CPU parameters Installation of the The GSD (Geräte-Stamm-Datei) is online available in the following language versions. SPEEDBUS.GSD Further language versions are available on inquires: Name Language SPEEDBUS.GSD German (default) SPEEDBUS.GSG German...
Page 160 Configuration with TIA Portal VIPA System 300S TIA Portal - Setting VIPA specific CPU parameters Device overview Module Slot Type PLC... CPU ... DI... DI... DO... DO... DIO... DIO... AI... AI... AO... AO... CP 343-1 CP 343-1 CP 342-5 CP 342-5 Thus, the VIPA components can be displayed, you have to deactivate the "Filter"...
Page 161 VIPA System 300S Configuration with TIA Portal TIA Portal - Setting VIPA specific CPU parameters Click at the slave system and open the ‘Device overview’ in the Project area. Configure at slot 1 the VIPA CPU 317-4PN23 of the hardware catalog from VIPA_SPEEDbus.
Page 162: Tia Portal - Vipa-Include Library
Configuration with TIA Portal VIPA System 300S TIA Portal - VIPA-Include library 10.7 TIA Portal - VIPA-Include library Overview The VIPA specific blocks can be found in the "Service" area of www.vipa.com as library download file at Downloads > VIPA LIB. The library is available as packed zip file for the corresponding TIA Portal version.
Page 163: Tia Portal - Project Transfer
VIPA System 300S Configuration with TIA Portal TIA Portal - Project transfer 10.8 TIA Portal - Project transfer Overview There are the following possibilities for project transfer into the CPU: Transfer via MPI Transfer via Ethernet Transfer via memory card Transfer via MPI Currently the VIPA programming cables for transfer via MPI are not supported.
Page 164 Configuration with TIA Portal VIPA System 300S TIA Portal - Project transfer Transfer via memory card 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 stored in the root directory and has one of the following file names: S7PROG.WLD AUTOLOAD.WLD...
Page 165: Appendix
VIPA System 300S Appendix Appendix HB140 | CPU | 317-4PN23 | en | 18-01...
Page 166 Appendix VIPA System 300S Content System specific event IDs Integrated blocks SSL partial list HB140 | CPU | 317-4PN23 | en | 18-01...
Page 167: A System Specific Event Ids
VIPA System 300S System specific event IDs System specific event IDs Ä Chapter 5.20 ‘Diagnostic entries’ on page 81 Event IDs Event ID Description 0x115C Manufacture interrupt for EtherCAT / PROFINET IO OB: OB number ZINFO1: Logical address of the slave station that triggered the interrupt ZINFO2: Interrupt type 0: Reserved 1: Diagnostic interrupt (incoming)
Page 168 System specific event IDs VIPA System 300S Event ID Description 0xE005 Internal error - Please contact the hotline! ZINFO1: Not user relevant ZINFO2: Not user relevant ZINFO3: Not user relevant 0xE007 Configured input/output bytes do not fit in the periphery area 0xE008 Internal error - Please contact the hotline! 0xE009...
Page 169 VIPA System 300S System specific event IDs Event ID Description ZINFO1: Error 4: SSL wrong 5: Sub-SSL wrong 6: Index wrong ZINFO2: SZL-ID ZINFO3: Index 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)
Page 170 System specific event IDs VIPA System 300S Event ID Description 0xE200 Memory card writing finished (Copy Ram2Rom) OB: Not user relevant PK: Not user relevant 0xE210 Memory card reading finished (reload after memory reset) OB: Not user relevant PK: Not user relevant ZINFO1 - Position 0: Not user relevant 0xE21D Memory card reading: Error on reload (after memory reset), error in the block header...
Page 171 VIPA System 300S System specific event IDs Event ID Description 70: SFB 97: VDB 98: VSDB 99: VFC 100: VSFC 101: VFB 102: VSFB 111: VOB ZINFO3: Block number 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)
Page 172 System specific event IDs VIPA System 300S Event ID Description 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...
Page 173 VIPA System 300S System specific event IDs Event ID Description 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...
Page 174 System specific event IDs VIPA System 300S Event ID Description 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 1: Card ZINFO1: FSC(CRC) 1146: 955-C000070 1736: 955-C0NE040...
Page 175 VIPA System 300S System specific event IDs Event ID Description 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) 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...
Page 176 System specific event IDs VIPA System 300S Event ID Description 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...
Page 177 VIPA System 300S System specific event IDs Event ID Description 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...
Page 178 System specific event IDs VIPA System 300S Event ID Description 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 ZINFO3: Block number 0xE501 Parser error ZINFO1: Error code...
Page 179 VIPA System 300S System specific event IDs Event ID Description 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) ZINFO3: Block address (low word) 0xE505...
Page 180 System specific event IDs VIPA System 300S Event ID Description ZINFO3: Not user relevant DatID: Not user relevant 0xE705 Too many PROFIBUS slaves configured ZINFO1: Diagnostic address of the PROFIBUS master ZINFO2: Number of configured slaves ZINFO3: Number of admissible slaves 0xE710 On-board PROFIBUS/MPI: Bus error occurred PK: Not user relevant...
Page 181 VIPA System 300S System specific event IDs Event ID Description 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...
Page 182 System specific event IDs VIPA System 300S Event ID Description 0xE80E CMD - auto command: SET_NETWORK recognized and executed 0xE80F Internal error - Please contact the hotline! ZINFO3: Status 0: OK 65153: File create error 65185: File writing error 65186: Odd address for reading 0xE810 Internal error - Please contact the hotline! 0xE811...
Page 183 VIPA System 300S System specific event IDs Event ID Description 0xE901 Checksum error ZINFO1: Not user relevant ZINFO2: Not user relevant DatID: Not user relevant 0xE902 Internal error - Please contact the hotline! ZINFO1: Not user relevant ZINFO2: Not user relevant DatID: Not user relevant 0xE904 PG/OP: Multiple parametrization of a peripheral address...
Page 184 System specific event IDs VIPA System 300S Event ID Description ZINFO1: Slot DatID: Not user relevant 0xEA02 SBUS: Internal error (internal plugged sub module not recognized) PK: Not user relevant ZINFO1: Slot ZINFO2: Type identifier target ZINFO3: Type identifier DatID: Not user relevant 0xEA03 SBUS: Communication error between CPU and IO controller OB: Operating mode...
Page 185 VIPA System 300S System specific event IDs Event ID Description 7: Not Connected 8: Unknown DatID: Not user relevant 0xEA04 SBUS: Multiple configuration of a periphery address ZINFO1: Periphery address ZINFO2: Slot ZINFO3: Data width 0xEA05 Internal error - Please contact the hotline! 0xEA07 Internal error - Please contact the hotline! 0xEA08...
Page 186 System specific event IDs VIPA System 300S Event ID Description PK: Not user relevant ZINFO2: HW slot ZINFO3: Interface type DatID: Not user relevant 0xEA1A SBUS: Error in access to SBUS FPGA address table PK: Not user relevant ZINFO2: HW slot ZINFO3: Table 0: Read 1: Writing...
Page 187 VIPA System 300S System specific event IDs Event ID Description DatID: Line 0xEA50 PROFINET IO controller: Error in the configuration OB: Not user relevant PK: Not user relevant ZINFO1: Rack/slot of the controller ZINFO2: Device number ZINFO3: Slot at the device DatID: Not user relevant 0xEA51 PROFINET IO controller: There is no PROFINET IO controller at the configured slot...
Page 188 System specific event IDs VIPA System 300S Event ID Description OB: File number PK: Slot of the controller ZINFO1: Firmware major version ZINFO2: Firmware minor version DatID: Line 0xEA62 Internal error - Please contact the hotline! OB: File number. PK: Slot of the controller ZINFO1: Firmware major version ZINFO2: Firmware minor version DatID: Line...
Page 189 VIPA System 300S System specific event IDs Event ID Description ZINFO2 - Bit 2: DC parameter invalid ZINFO2 - Bit 3: I device configuration invalid (slot gap) ZINFO2 - Bit 4: MRP configuration invalid (client) 0xEA65 Internal error - Please contact the hotline! PK: Platform 0: none 8: CP...
Page 190 System specific event IDs VIPA System 300S Event ID Description 1: Dataset error stack 2: Dataset error station ZINFO1: Dataset number ZINFO2: Dataset handle (caller) ZINFO3: Internal error code from PN stack DatID: Device 0xEA69 Internal error - Please contact the hotline! ZINFO1: Minimum version for the FPGA ZINFO2: Loaded FPGA version 0xEA6A...
Page 191 VIPA System 300S System specific event IDs Event ID Description ZINFO2: Not user relevant ZINFO3: Not user relevant DatID: Not user relevant 0xEA6C PROFINET IO controller: Incorrect Device-ID OB: Operating mode 0: Configuration in operating condition RUN 1: STOP (update) 2: STOP (memory reset) 3: STOP (auto initialization) 4: STOP (internal)
Page 192 System specific event IDs VIPA System 300S Event ID Description 12: UPDATING 13: DEFECTIVE 14: Error search mode 15: De-energised 253: Process image release in STOP 254: Watchdog 255: Not set PK: Rack/slot ZINFO1: Device ID ZINFO2: Not user relevant ZINFO3: Not user relevant DatID: Not user relevant 0xEA6E...
Page 193 VIPA System 300S System specific event IDs Event ID Description OB: Operating mode 0: Configuration in operating condition RUN 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...
Page 194 System specific event IDs VIPA System 300S Event ID Description 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.
Page 195 VIPA System 300S System specific event IDs Event ID Description 0: INIT 1: STOP 2: READY 3: PAUSE 4: RUN ZINFO1: Filenamehash[0-3] ZINFO2: Filenamehash[4-7] ZINFO3: Line DatID: Current job number 0xEA92 Internal error - Please contact the hotline! OB: Current OB number PK: Core status 0: INIT 1: STOP...
Page 196 System specific event IDs VIPA System 300S Event ID Description DatID: Not user relevant 0xEA99 Parameter assignment job could not be executed PK: Not user relevant ZINFO1: File version on MMC/SD (if not 0) ZINFO2: File version of the SBUS module (if not 0) ZINFO3: Slot DatID: Not user relevant 0xEAA0...
Page 197 VIPA System 300S System specific event IDs Event ID Description 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: Diagnostic address of the master...
Page 198 System specific event IDs VIPA System 300S Event ID Description PK: Not user relevant ZINFO1: Error type 1: SDB parser error 2: Configured address already used 3: Mapping error ZINFO2: Slot (0=cannot be determined) DatID: Not user relevant 0xEB04 SLIO-Bus: Multiple configuration of a periphery address ZINFO1: Periphery address ZINFO2: Slot DatID: Input...
Page 199 VIPA System 300S System specific event IDs Event ID Description 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...
Page 200 System specific event IDs VIPA System 300S Event ID Description 0xEC05 EtherCAT: Check the set DC mode of the YASKAWA Sigma 5/7 drive OB: Operating mode 0: Configuration in operating condition RUN 1: STOP (update) 2: STOP (memory reset) 3: STOP (auto initialization)
Page 201 VIPA System 300S System specific event IDs Event ID Description 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...
Page 202 System specific event IDs VIPA System 300S Event ID Description DatID: Input address DatID: Output address 0xEC12 EtherCAT: Recurrence slave 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...
Page 203 VIPA System 300S System specific event IDs Event ID Description 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 ZINFO2: Diagnostic address of the master ZINFO3: DC state change 0: DC master out of sync 1: DC slave stations out of sync...
Page 204 System specific event IDs VIPA System 300S Event ID Description DatID: Output address 0xED12 EtherCAT: Breakdown slave 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...
Page 205 VIPA System 300S System specific event IDs Event ID Description 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...
Page 206 System specific event IDs VIPA System 300S Event ID Description 0xED21 EtherCAT: Incorrect bus status change 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...
Page 207 VIPA System 300S System specific event IDs Event ID Description 3: Bootstrap 4: SafeOp 8: Op ZINFO2: Diagnostic address of the station 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 22: Invalid mailbox configuration...
Page 208 System specific event IDs VIPA System 300S Event ID Description DatID: Station not available DatID: Station available DatID: Input address DatID: Output address 0xED23 EtherCAT: Time out while changing the master state to OP, after CPU has changed to RUN OB: Operating mode 0: Configuration in operating condition RUN 1: STOP (update)
Page 209 VIPA System 300S System specific event IDs Event ID Description ZINFO2: Diagnostic address of the master 0xED31 EtherCAT: Overflow of the interrupt queue ZINFO2: Diagnostic address of the master 0xED40 Bus cycle time infringement occurred ZINFO1: Logical address of the IO system 0xED50 EtherCAT: Distributed clocks (DC) in sync OB: Operating mode...
Page 210 System specific event IDs VIPA System 300S Event ID Description 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 - Position 0: New status 0: Undefined/Unkown 1: Init...
Page 211 VIPA System 300S System specific event IDs Event ID Description 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...
Page 212 System specific event IDs VIPA System 300S Event ID Description 0xED63 EtherCAT: Diagnostic buffer CP: Error in the response to an INIT command OB: EtherCAT station address (high byte) PK: EtherCAT station address (low byte) ZINFO1: Error type 0: Not defined 1: No response 2: Validation error 3: INIT command failed, requested station could not be reached...
Page 213 VIPA System 300S System specific event IDs Event ID Description ZINFO2: Not user relevant ZINFO3: Not user relevant DatID: Not user relevant 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! DatID: Not user relevant...
Page 214 System specific event IDs VIPA System 300S Event ID Description 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...
Page 215: B Integrated Blocks
VIPA System 300S Integrated blocks Integrated blocks More information about this may be found in the manual "SPEED7 Oper- ation List" from VIPA. 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...
Page 216 Integrated blocks VIPA System 300S Name Description SFB 5 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 Remote CPU read SFB 15 Remote CPU write SFB 31 NOTIFY8P Messages without acknowledge display (8x)
Page 217 VIPA System 300S Integrated blocks Name Description 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 25...
Page 218 Integrated blocks VIPA System 300S Name Description 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...
Page 219: Cssl Partial List
VIPA System 300S SSL partial list SSL partial list More information about this may be found in the manual "SPEED7 Oper- ation List" from VIPA. SSL-ID SSL partial list xy11h Module identification xy12h CPU characteristics xy13h User memory areas xy14h System areas xy15h Block Types...

YASKAWA VIPA System 300S+ Manual

1 General

2 Basics

3 Assembly and Installation Guidelines

4 Hardware Description

5 Deployment CPU 317-4PN23

6 Deployment Ptp Communication

7 Deployment PROFIBUS Communication

8 Deployment Ethernet Communication - Productive

9 Deployment Ethernet Communication - PROFINET

10 Configuration with TIA Portal

Appendix

Quick Links

Related Manuals for YASKAWA VIPA System 300S+

Summary of Contents for YASKAWA VIPA System 300S+

Table of Contents