VIPA System 300S Manual
  1. Manuals
  2. Brands
  3. VIPA Manuals
  4. Control Unit
  5. System 300S
  6. Manual

VIPA System 300S Manual

Hide thumbs Also See for System 300S:
Table of Contents

Advertisement

Quick Links

See also: Manual
+
VIPA System 300S
CPU | 315-4PN43 | Manual
HB140 | CPU | 315-4PN43 | GB | 16-36
SPEED7 CPU 315PN

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the System 300S and is the answer not in the manual?

Questions and answers

Related Manuals for VIPA System 300S

Summary of Contents for VIPA System 300S

  • Page 1 VIPA System 300S CPU | 315-4PN43 | Manual HB140 | CPU | 315-4PN43 | GB | 16-36 SPEED7 CPU 315PN...
  • Page 2 VIPA GmbH Ohmstr. 4 91074 Herzogenaurach Telephone: 09132-744-0 Fax: 09132-744-1864 Email: info@vipa.com Internet: www.vipa.com 315-4PN43_000_CPU 315PN,1,GB - © 2016...

  • Page 3: Table Of Contents

    Table of contents VIPA System 300S Table of contents General..................6 1.1 Copyright © VIPA GmbH ........... 6 1.2 About this manual.............. 7 1.3 Safety information.............. 8 Basics..................10 2.1 Safety information for users..........10 2.2 Operating structure of a CPU........... 11 2.2.1 General................
  • Page 4 Table of contents VIPA System 300S 5.9.1 Proceeding..............50 5.9.2 VIPA specific parameters..........52 5.10 Project transfer............... 52 5.10.1 Transfer via MPI............53 5.10.2 Transfer via Ethernet........... 54 5.10.3 Transfer via memory card........... 54 5.11 Accessing the web server..........55 5.12 Operating modes............
  • Page 5 168 9.5 TIA Portal - Hardware configuration - PG/OP via PRO- FINET................171 9.6 TIA Portal - Setting VIPA specific CPU parameters..173 9.7 TIA Portal - VIPA-Include library........176 9.8 TIA Portal - Project transfer..........177 HB140 | CPU | 315-4PN43 | GB | 16-36...

  • Page 6: General

    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 agree- ments. This material is protected by the copyright laws. It may not be repro-...

  • Page 7: About This Manual

    Tel.: +49 9132 744-1150 (Hotline) EMail: support@vipa.de 1.2 About this manual Objective and contents This manual describes the SPEED7 CPU 315-4PN43 of the System 300S from VIPA. It contains a description of the construction, project implementation and usage. Product Order no. as of state:...

  • Page 8: Safety Information

    General VIPA System 300S Safety information Structure of the manual The manual consists of chapters. Every chapter provides a self-con- tained description of a specific topic. Guide to the document The following guides are available in the manual: An overall table of contents at the beginning of the manual...
  • Page 9 General VIPA System 300S Safety information Documentation The manual must be available to all personnel in the project design department installation department commissioning operation CAUTION! The following conditions must be met before using or commissioning the components described in this manual: –...

  • Page 10: Basics

    Safety information for users Basics 2.1 Safety information for users Handling of electro- VIPA modules make use of highly integrated components in MOS- static sensitive modules Technology. These components are extremely sensitive to over-vol- tages that can occur during electrostatic discharges. The following symbol is attached to modules that can be destroyed by electrostatic discharges.

  • Page 11: Operating Structure Of A Cpu

    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. A CPU supports the following modes of operation: cyclic operation...

  • Page 12: Operands

    Basics VIPA System 300S Operating structure of a CPU > Operands 2.2.3 Operands The following series of operands is available for programming the CPU: Process image and periphery Bit memory Timers and counters Data blocks Process image and The user application can quickly access the process image of the periphery inputs and outputs PIO/PII.

  • Page 13: Cpu 315-4Pn43

    SIMATIC Manager or TIA Portal from Siemens. Here the instruction set of the S7-400 from Siemens is used. Modules and CPUs of the System 300S from VIPA and Siemens may be used at the bus as a mixed configuration.

  • Page 14: General Data

    Basics VIPA System 300S General data 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 1MB...
  • Page 15 Basics VIPA System 300S General data Conformity and approval others RoHS 2011/65/EU Product is lead-free; 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...
  • Page 16 Basics VIPA System 300S General data Standard Comment Emitted interfer- EN 61000-6-4 Class A (Industrial area) ence 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...

  • Page 17: Assembly And Installation Guidelines

    Assembly and installation guidelines VIPA System 300S Installation dimensions Assembly and installation guidelines 3.1 Installation dimensions Dimensions Basic 2tier width (WxHxD) in mm: 80 x 125 x 120 enclosure Dimensions Installation dimensions HB140 | CPU | 315-4PN43 | GB | 16-36...

  • Page 18: Assembly Standard Bus

    *) Unit pack: 10 pieces Measures in mm 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 19: Cabling

    Assembly and installation guidelines VIPA System 300S Cabling Assembly possibilities Please regard the allowed environment temperatures: 1 horizontal assembly: from 0 to 60°C 2 vertical assembly: from 0 to 50°C 3 lying assembly: from 0 to 55°C Approach Bolt the profile rail with the background (screw size: M6), so that you still have minimum 65mm space above and 40mm below the profile rail.

  • Page 20: Installation Guidelines

    Assembly and installation guidelines VIPA System 300S Installation guidelines CageClamp technology For the cabling of power supply of a CPU, a green plug with Cage- (green) Clamp technology is deployed. The connection clamp is realized as plug that may be clipped off carefully if it is still cabled.
  • Page 21 The components of VIPA are developed for the deployment in indus- trial environments and meets high demands on the EMC. Neverthe- less you should project an EMC planning before installing the compo- nents and take conceivable interference causes into account.
  • Page 22 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 amplitudes the one sided laying of the isolation may be favourable.
  • Page 23 Assembly and installation guidelines VIPA System 300S Installation guidelines To fix the isolation tangles use cable clamps out of metal. The clamps must clasp the isolation extensively and have well contact. Lay the isolation on an isolation rail directly after the entry of the cable in the cabinet.

  • Page 24: Hardware Description

    Hardware description VIPA System 300S Properties Hardware description 4.1 Properties CPU 315-4PN43 SPEED7 technology integrated 512kbyte work memory integrated (256kbyte code, 256kbyte data) Work memory expandable to max. 1MB (512kbyte code, 512kbyte data) 1MB load memory X3: PtP interface X8: PROFINET IO controller: PROFINET in accordance with con-...

  • Page 25: Structure

    Hardware description VIPA System 300S Structure > Interfaces 4.2 Structure 4.2.1 General CPU 315-4PN43 1 Storage media slot (lockable) 2 LED status indication CPU part 3 LED status indication PROFINET IO controller 4 Operating mode switch CPU 5 X5: Ethernet PG/OP channel...

  • Page 26: Memory Management

    Hardware description VIPA System 300S Structure > Memory management X2: MPI interface 9pin SubD jack: The MPI interface serves for the connection between program- ming unit and CPU. By means of this the project engineering and programming hap- pens. MPI serves for communication between several CPUs or between HMIs and CPU.

  • Page 27: Storage Media Slot

    Via this slot as external storage medium for applications and firm- ware you may use a memory card (MMC respectively SD). The VIPA storage media are pre-formatted with the PC format FAT and can be accessed via a card reader.

  • Page 28: Operating Mode Switch

    Hardware description VIPA System 300S Structure > LEDs CAUTION! – After a power reset and with an empty battery the CPU starts with a BAT error and executes an overall reset. The loading procedure is not influ- enced by the BAT error.
  • Page 29 Hardware description VIPA System 300S Structure > LEDs Meaning (RUN) (STOP) (SFAIL) (FRCE) (MMC) ● There is a system fault. More information may be found in the diagnostics buffer of the CPU. ● Variables are forced. ● Access to the memory card.

  • Page 30: Technical Data

    Hardware description VIPA System 300S Technical data LEDs PROFINET IO controller X8 Meaning (Mainte- (Bus error) nance) yellow ● Bus error, no connection to sub net/switch wrong transfer rate Full-duplex-transmission is not activated Failure of a connected IO device At least one IO device is not access-able Faulty configuration ●...
  • Page 31 Hardware description VIPA System 300S Technical data Order no. 315-4PN43 Inrush current 11 A I²t 0.4 A²s Max. current drain at backplane bus Max. current drain load supply Power loss 5.5 W Load and working memory Load memory, integrated 1 MB...
  • Page 32 Hardware description VIPA System 300S Technical data Order no. 315-4PN43 Number of flags 8192 Byte Bit memories retentive characteristic adjustable adjustable 0 up to 8192 Bit memories retentive characteristic preset MB0 .. MB15 Number of data blocks 4095 Max. data blocks size...
  • Page 33 Hardware description VIPA System 300S Technical data Order no. 315-4PN43 Output I/O address area 2048 Byte Process image adjustable ü Input process image preset 256 Byte Output process image preset 256 Byte Input process image maximal 2048 Byte Output process image maximal...
  • Page 34 Hardware description VIPA System 300S Technical data Order no. 315-4PN43 Electrically isolated ü ü MP²I (MPI/RS232) DP master DP slave Point-to-point interface 5V DC Power supply max. 90mA, isolated 24V DC Power supply max. 100mA, non-isolated Type Type of interface...
  • Page 35 Hardware description VIPA System 300S Technical data Order no. 315-4PN43 S7 basic communication S7 communication S7 communication as server S7 communication as client Activation/deactivation of DP slaves Direct data exchange (slave-to-slave communi- cation) DPV1 Transmission speed, min. Transmission speed, max.
  • Page 36 Hardware description VIPA System 300S Technical data Order no. 315-4PN43 RS422 interface RS485 interface ü Connector Sub-D, 9-pin, female Transmission speed, min. 150 bit/s Transmission speed, max. 115.5 kbit/s Cable length, max. 500 m Point-to-point protocol ASCII protocol ü STX/ETX protocol ü...
  • Page 37 Hardware description VIPA System 300S Technical data Order no. 315-4PN43 Productive connections Type Type of interface Ethernet 10/100 MBit Connector RJ45 Electrically isolated ü PG/OP channel ü Number of connections, max. Productive connections ü Ethernet communication CP Number of productive connections, max.
  • Page 38 Hardware description VIPA System 300S Technical data Order no. 315-4PN43 UDP-connections TUSEND, TURCV User data per UDP connection, max. 1472 Byte Housing Material Mounting Rail System 300 Mechanical data Dimensions (WxHxD) 80 mm x 125 mm x 120 mm Weight...

  • Page 39: Deployment Cpu 315-4Pn43

    Deployment CPU 315-4PN43 VIPA System 300S Start-up behavior Deployment CPU 315-4PN43 5.1 Assembly Ä Chapter 3 Information about assembly and cabling: ‘Assembly and installation guidelines’ on page 17 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 40: Addressing

    IM 361 from Siemens at slot 3. Considering the max total current with the CPU 315-4PN43 from VIPA up to 32 mod- ules may be arranged in a row. Here the installation of the line con- nections IM 360/361 from Siemens is not required.

  • Page 41: Hardware Configuration - Cpu

    Deployment CPU 315-4PN43 VIPA System 300S Hardware configuration - CPU Automatic addressing If you do not like to use a hardware configuration, an automatic addressing comes into force. At the automatic address allocation DIOs occupy depending on the slot location always 4byte and AIOs, FMs, CPs always 16byte at the bus.

  • Page 42: Hardware Configuration - I/O Modules

    ACCU 2. For more information may be found in the manual "VIPA Operation list SPEED7" at "Differences between SPEED7 and 300V programming". Proceeding To be compatible with the Siemens SIMATIC Manager the following steps should be executed: Start the Siemens hardware configurator with a new project.

  • Page 43: Hardware Configuration - Ethernet Pg/Op Channel

    Now you may extend your system with up to 3 profile rails by starting each with an IM 361 from Siemens at slot 3. Considering the max. total current with the VIPA SPEED7 CPUs up to 32 modules may be arranged in a row. Here the installation of the line connections IM 360/361 from Siemens is not required.
  • Page 44 Deployment CPU 315-4PN43 VIPA System 300S Hardware configuration - Ethernet PG/OP channel "Initialization" via PLC The initialization via PLC functions takes place with the following pro- functions ceeding: Determine the current Ethernet (MAC) address of your Ethernet PG/OP channel. This always may be found as 1. address under the front flap of the CPU on a sticker on the left side.

  • Page 45: Hardware Configuration - Communication

    Siemens CPU (6ES7 315-2EH14-0AB0 V3.2) in the Siemens hardware configurator, the standard parameters of the VIPA CPU may be set with "Object properties" of the CPU during hardware configuration. Via a double- click on the CPU 315-2 PN/DP (6ES7 315-2EH14-0AB0 V3.2) the parameter window of the CPU may be accessed.

  • Page 46: Parameters Cpu

    Deployment CPU 315-4PN43 VIPA System 300S Setting standard CPU parameters > Parameters CPU 5.8.2 Parameters CPU Supported parameters The CPU does not evaluate each parameter, which may be set at the hardware configuration. The following parameters are supported by the CPU at this time:...
  • Page 47 Deployment CPU 315-4PN43 VIPA System 300S Setting standard CPU parameters > Parameters CPU Startup Startup when expected/actual configuration differs: If the checkbox for ‘Startup when expected/actual configuration differ’ is deselected 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 48 – 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.
  • Page 49 Deployment CPU 315-4PN43 VIPA System 300S Setting standard CPU parameters > Parameters CPU Cyclic interrupts Priority – Here the priorities may be specified according to which the corresponding cyclic interrupt is processed. – With priority "0" the corresponding interrupt is deactivated.

  • Page 50: Parameters For Mpi/Dp

    Name: At Name "MPI/DP" for the MPI interface is shown. If you change the name, the new name appears in the Siemens SIMATIC Manager. Type: Please regard only the type "MPI" is supported by the VIPA CPU. Interface: Here the MPI address is shown.
  • Page 51 German (default) SPEEDBUS.GSG German SPEEDBUS.GSE English The GSD files may be found at www.vipa.com at the "Service" part. The integration of the SPEEDBUS.GSD takes place with the following proceeding: Browse to www.vipa.com Click to ‘Service è Download è GSD- and EDS-Files è...

  • Page 52: Vipa Specific Parameters

    "DP-Master". Connect the slave system "VIPA_SPEEDbus". After installing the SPEEDBUS.GSD this may be found in the hardware catalog at Profibus-DP / Additional field devices / I/O / VIPA / VIPA_SPEEDBUS. For the slave system set the PROFIBUS address 100.

  • Page 53: Transfer Via Mpi

    Please consider with the CPU 315-4PN43 that the total exten- sion of the MPI net does not exceed 50m. Per default the MPI net runs with 187.5kbaud. VIPA CPUs are delivered with MPI address 2. MPI programming cable The MPI programming cables are available at VIPA in different var- iants.

  • Page 54: Transfer Via Ethernet

    Deployment CPU 315-4PN43 VIPA System 300S Project transfer > Transfer via memory card Via ‘PLC è Load to module’ via MPI to the CPU and save it on a memory card via ‘PLC è Copy RAM to ROM’ if one is plugged.

  • Page 55: Accessing The Web Server

    Deployment CPU 315-4PN43 VIPA System 300S Accessing the web server With ‘File è Memory Card File è New’ in the Siemens SIMATIC Manager a new wld file may be created. After the creation copy the blocks from the project blocks folder and the System data into the wld file.
  • Page 56 Deployment CPU 315-4PN43 VIPA System 300S Accessing the web server Info - Overview Here order number, serial number and the version of firmware and hardware of the CPU are listed. [Expert View] takes you to the advanced "Expert View". Info - Expert View...
  • Page 57 Deployment CPU 315-4PN43 VIPA System 300S Accessing the web server Active Feature Set Information Status Memory Extension present Memory Usage LoadMem 0 / 4194304 Bytes CPU: Information to memory configuration WorkMemCode 0 / 524288 Bytes Load memory, working WorkMemData 0 / 524288 Bytes...
  • Page 58 Deployment CPU 315-4PN43 VIPA System 300S 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...
  • Page 59 Deployment CPU 315-4PN43 VIPA System 300S Accessing the web server Hardware CPU load Measurement cycle time 100 ms 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...

  • Page 60: Operating Modes

    Deployment CPU 315-4PN43 VIPA System 300S Operating modes > Overview Data - Input data Offset Width Value (dec) Value (hex) Data - Output data Offset Width Value (dec) Value (hex) New Value (hex) 5.12 Operating modes 5.12.1 Overview The CPU can be in one of 4 operating modes:...
  • Page 61 Deployment CPU 315-4PN43 VIPA System 300S Operating modes > Overview Operating mode START- 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.

  • Page 62: Function Security

    (parameterizable min. 1ms) that stop res. execute a RESET at the CPU in case of an error and set it into a defined STOP state. The VIPA CPUs are developed func- tion secure and have the following system properties:...

  • Page 63: Overall Reset

    Deployment CPU 315-4PN43 VIPA System 300S Overall reset Event concerns Effect STOP ® RUN res. general First the PII is deleted, then OB 100 is PowerON called. After the execution of the OB, the BASP is reset and the cycle starts with: Delete PIO ®...
  • Page 64 Deployment CPU 315-4PN43 VIPA System 300S Overall reset The overall reset has been completed when the STOP-LED is on permanently. ð The ST-LED is on. The following figure illustrates the above procedure: Overall reset by means Precondition The operating mode of the CPU is to be switched to of the Siemens SIMATIC STOP.

  • Page 65: Firmware Update

    Latest firmware at The latest firmware versions are to be found in the service area at www.vipa.com www.vipa.com. For example the following files are necessary for the firmware update of the CPU 315-4PN43 and its components with hardware release 1: 315-4PN43, Hardware release 1: Px000309.pkg...
  • Page 66 Click on ‘Service è Download è Firmware’. card Navigate via ‘System 300S è CPU’ to your CPU and download the zip file to your PC. Extract the zip file and copy the extracted pkg files to your memory card.

  • Page 67: Reset To Factory Settings

    Deployment CPU 315-4PN43 VIPA System 300S Reset to factory settings Turn Power OFF and ON. Now it is checked by the CPU, whether further current firmware versions are available at the memory card. If so, again the LEDs SF and FC flash after a short start-up period.

  • Page 68: Slot For Storage Media

    Deployment CPU 315-4PN43 VIPA System 300S Slot for storage media The proceeding is shown in the following Illustration: After the firmware update you always should execute a Reset to factory setting. 5.16 Slot for storage media Overview At the front of the CPU there is a slot for storage media. Via this slot as external storage medium for applications and firmware you may use a memory card (MMC respectively SD).

  • Page 69: Memory Extension

    Overview In front of the CPU there is a slot for storage media. For this, a MCC memory extension card is available from VIPA. The MCC is a spe- cially prepared MMC (Multimedia Card). By plugging the MCC into the MCC slot and then an overall reset the according memory expan- sion is released.

  • Page 70: Extended Know-How Protection

    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 The standard protection from Siemens transfers also protected blocks to the PG but their content is not displayed.
  • Page 71 Deployment CPU 315-4PN43 VIPA System 300S Extended know-how protection Protect blocks with pro- Create a new wld-file in your project engineering tool with ‘File tect.wld è Memory Card file è New’ and rename it to "protect.wld". Transfer the according blocks into the file by dragging them with the mouse from the project to the file window of protect.wld.

  • Page 72: Cmd - Auto Commands

    Deployment CPU 315-4PN43 VIPA System 300S CMD - auto commands Usage of protected Due to the fact that reading of a "protected" block from the CPU moni- blocks tors no symbol labels it is convenient to provide the "block covers" for the end user.
  • Page 73 Deployment CPU 315-4PN43 VIPA System 300S CMD - auto commands Command Description Diagnostics entry SET_NETWORK IP parameters for Ethernet PG/OP channel may be set 0xE80E by 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...

  • Page 74: Diagnostic Entries

    You may read the diagnostics buffer of the CPU via the Siemens data SIMATIC Manager. Besides of the standard entries in the diagnos- tics buffer, the VIPA CPUs support some additional specific entries as Event-IDs. To monitor the diagnostics entries you choose in the Siemens SIMATIC manager ‘PLC è...
  • Page 75 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 0x0C: Diagnostic interrupt (outgoing) 0x0D: Cross traffic connection message 0x0E: Neighbourhood change message 0x0F: Synchronisation message (bus) 0x10: Synchronisation message (device) 0x11: Network component message 0x12: Clock synchronisation message (bus)
  • Page 76 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 0xE020 Error - Interrupt information undefined ZInfo2 : Slot ZInfo3 : Not relevant to the user DatID : Interrupt type 0xE030 Error of the standard bus 0xE033 Internal error - Please contact the hotline! 0xE0B0 SPEED7 is not stoppable (e.g.
  • Page 77 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 98: Unknown error 99: Internal error 0xE0CD Error at DP-V1 job management ZInfo1 : Not relevant to the user ZInfo2 : Not relevant to the user ZInfo3 : Not relevant to the user...
  • Page 78 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 0xE21E Memory card reading: Error at reload (after overall reset), file "Protect.wld" too big OB : Not relevant to the user 0xE21F Memory card reading: Error at reload (after overall reset), checksum error at reading...
  • Page 79 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description ZInfo3 : Source of the FSC 0: CPU 1: Card 0xE402 A configured functionality is not activated ZInfo1 : FCS ErrorCode 1: The PROFIBUS functionality is disabled The interface acts further as MPI interface...
  • Page 80 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description ZInfo3 : SDB number ZInfo1 : ErrorCode 1: Parser error: SDB structure 2: Parser error: SDB is not a valid SDB type. ZInfo2 : SDB type 0xE502 Invalid block type in protect.wld...
  • Page 81 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description ZInfo1 : Interface ZInfo2 : Not relevant to the user ZInfo3 : Not relevant to the user PK : Not relevant to the user DatID : Not relevant to the user...
  • Page 82 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 0xE80C Internal error - Please contact the hotline! 0xE80D Internal error - Please contact the hotline! 0xE80E CMD - Auto command: SET_NETWORK recognized and successfully executed 0xE80F Internal error - Please contact the hotline!
  • Page 83 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description ZInfo2 : Not relevant to the user DatID : Not relevant to the user 0xE902 Internal error - Please contact the hotline! 0xEA00 Internal error - Please contact the hotline!
  • Page 84 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 12: UPDATING 13: DEFECTIVE 14: Troubleshooting 15: Without power 0xFD: Process image enabled in STOP 0xFE: Watchdog 0xFF: Not set 0xEA04 SBUS: Multiple configuration of a periphery address ZInfo1 : Periphery address...
  • Page 85 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 0xEA18 SBUS: Error at mapping of the master periphery ZInfo2 : Slot of the master 0xEA19 Internal error - Please contact the hotline! 0xEA1A SBUS: Error at access to the FPGA address table...
  • Page 86 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description ZInfo2 : Slot ZInfo3 : Maximum possible number of devices 0xEA54 PROFINET IO controller: IO controller reports multiple parametrization of a periphery address ZInfo1 : Periphery address ZInfo2 : Slot...
  • Page 87 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description ZInfo3 : StackError.Error.AdditionalDetail ZInfo3 : StackError.Error.AreaCode 0xEA67 PROFINET IO controller: Error reading record set PK : Error type 0: Record set error local 1: Record set error stack 2: Record set error station...
  • Page 88 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 3: STOP (own initialization) 4: STOP (internal) 5: Start-up (cold start) 6: Start-up (cold restart/warm start) 7: Start-up (restart) 8: RUN 9: RUN (redundant operation) 10: HALT 11: COUPLING...
  • Page 89 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 0xFD: Process image enabled in STOP 0xFE: Watchdog 0xFF: Not set 0xEA6D PROFINET IO controller: No empty Name ZInfo1 : Device ID ZInfo2 : Not relevant to the user...
  • Page 90 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 4: STOP (internal) 5: Start-up (cold start) 6: Start-up (cold restart/warm start) 7: Start-up (restart) 8: RUN 9: RUN (redundant operation) 10: HALT 11: COUPLING 12: UPDATING 13: DEFECTIVE...
  • Page 91 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 0xFD: Process image enabled in STOP 0xFE: Watchdog 0xFF: Not set PK : Rack/slot DatID : Not relevant to the user 0xEA70 PROFINET stack error in configuration ZInfo1 : UnsupportedApiError.slot ZInfo2 : UnsupportedApiError.subslot...
  • Page 92 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 0x06: Auto Negotiation OB : Current operation mode 0: Configuration in operation mode RUN 1: STOP (update) 2: STOP (overall reset) 3: STOP (own initialization) 4: STOP (internal) 5: Start-up (cold start)
  • Page 93 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description DatID : Not relevant to the user ZInfo2 : Slot (0=not be determined) 0xEB10 SLIO error: Bus error ZInfo1 : Type of error 0x60: Bus enumeration error 0x80: General error...
  • Page 94 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description ZInfo1 : Periphery address ZInfo2 : Slot PK : Not relevant to the user DatID : Not relevant to the user 0xEC05 EtherCAT: Check the set DC mode of the YASKAWA Sigma 5/7 drive...
  • Page 95 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 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 timeout, DC mode could not be determined (for further information, the (subsequent)
  • Page 96 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 0x04: SafeOp 0x08: Op ZInfo2 : Diagnostics address of the master ZInfo3 : Number of stations, which are not in the same state as the master DatID : Input address...
  • Page 97 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 1: STOP (update) 2: STOP (overall reset) 3: STOP (own initialization) 4: STOP (internal) 5: Start-up (cold start) 6: Start-up (cold restart/warm start) 7: Start-up (restart) 8: RUN 9: RUN (redundant operation)
  • Page 98 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description DatID : Station available 0xED12 EtherCAT: Slave failure ZInfo1 : Old status 0x00: Undefined/Unkown 0x01: INIT 0x02: PreOp 0x03: BootStrap 0x04: SafeOp 0x08: Op ZInfo1 : New status 0x00: Undefined/Unkown...
  • Page 99 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 0x0023: Slave needs SafeOp 0x002D: Invalid output FMMU configuration 0x002E: Invalid input FMMU configuration 0x0030: Invalid DC Sync configuration 0x0031: Invalid DC Latch configuration 0x0032: PLL error 0x0033: Invalid DC IO error...
  • Page 100 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 0xED21 EtherCAT: Faulty bus status change ZInfo1 : Old status 0x00: Undefined/Unkown 0x01: INIT 0x02: PreOp 0x03: BootStrap 0x04: SafeOp 0x08: Op ZInfo1 : New status 0x00: Undefined/Unkown 0x01: INIT...
  • Page 101 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 0x03: BootStrap 0x04: SafeOp 0x08: Op ZInfo2 : Diagnostics address of the station ZInfo3 : AlStatusCode 0x0000: No Error 0x0001: Unspecified error 0x0011: Invalid requested status change 0x0012: Unknown requested status...
  • Page 102 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description DatID : Input address DatID : Output address DatID : Station not available DatID : Station available 0xED23 EtherCAT: Timeout while changing the master status to OP, after CPU has changed to RUN...
  • Page 103 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 0xED30 EtherCAT: Topology deviation ZInfo2 : Diagnostics address of the master 0xED31 EtherCAT: Overflow of the interrupt queue ZInfo2 : Diagnostics address of the master 0xED50 EtherCAT: DC slaves in sync...
  • Page 104 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 7: Start-up (restart) 8: RUN 9: RUN (redundant operation) 10: HALT 11: COUPLING 12: UPDATING 13: DEFECTIVE 14: Troubleshooting 15: Without power 0xFD: Process image enabled in STOP 0xFE: Watchdog...
  • Page 105 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description 0x0020: Slave needs cold start 0x0021: Slave needs INIT 0x0022: Slave needs PreOp 0x0023: Slave needs SafeOp 0x002D: Invalid output FMMU configuration 0x002E: Invalid input FMMU configuration 0x0030: Invalid DC Sync configuration...
  • Page 106 Deployment CPU 315-4PN43 VIPA System 300S Diagnostic entries Event ID Description ZInfo3 : SDOErrorCode (low word) 0xED63 EtherCAT: Diagnostics buffer CP: Error in the response to an INIT command PK : EtherCAT station address (low byte) OB : EtherCAT station address (high byte)

  • Page 107: Control And Monitoring Of Variables With Test Functions

    Deployment CPU 315-4PN43 VIPA System 300S Control and monitoring of variables with test functions Event ID Description 0xEE01 Internal error - Please contact the hotline! 0xEEEE CPU was completely overall reset, since after PowerON the start-up could not be finished...
  • Page 108 Deployment CPU 315-4PN43 VIPA System 300S Control and monitoring of variables with test functions ‘PLC This test function returns the condition of a selected operand (inputs, è Monitor/Modify outputs, flags, data word, counters or timers) at the end of program Variables’...

  • Page 109: Deployment Ptp Communication

    Deployment PtP communication VIPA System 300S Fast introduction Deployment PtP communication 6.1 Fast introduction General With this CPU the integrated RS485 interface is fix set to PtP (point- to-point) communication. PtP functionality – For operation there is no further configuration in the hardware configurator required.

  • Page 110: Principle Of The Data Transfer

    Deployment PtP communication VIPA System 300S Deployment of RS485 interface for PtP 6.2 Principle of the data transfer Overview 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.

  • Page 111: Parametrization

    Deployment PtP communication VIPA System 300S Parametrization > FC/SFC 216 - SER_CFG - Parametrization PtP RS485 9pin SubD jack RS485 n.c. M24V RxD/TxD-P (Line B) P24V RxD/TxD-N (Line A) n.c. Connection 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 112: Communication

    There is no reception acknowledgement. The communication procedure has to be controlled by the concerning user application. An according Receive_ASCII FB may be found within the VIPA library in the service area of www.vipa.com. 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.
  • Page 113 Deployment PtP communication VIPA System 300S Protocols and procedures 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:...
  • Page 114 Deployment PtP communication VIPA System 300S 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 115 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.

  • Page 116: Modbus - Function Codes

    Deployment PtP communication VIPA System 300S Modbus - Function codes Modbus The Modbus protocol is a communication protocol that fixes a hierarchic structure with one master and several slaves. Physically, Modbus works with a serial half-duplex connection. There are no bus conflicts occurring, because the master can only communicate with one slave at a time.
  • Page 117 0x and 1x gives you access to digital bit areas and 3x and 4x to analog word areas. For the CPs from VIPA is not differentiating digital and analog data, the following assignment is valid: 0x - Bit area for master output data...
  • Page 118 Deployment PtP communication VIPA System 300S Modbus - Function codes Code Command Description Write 1 bit Write 1 bit to master output area 0x Write 1 word Write 1 word to master output area 4x Write n bits Write n bits to master output area 0x...
  • Page 119 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 Function Number of Data 1. Data 2.
  • Page 120 Deployment PtP communication VIPA System 300S Modbus - Function codes Respond telegram Slave address Function code Address bit Status bit Check sum CRC/LRC 1byte 1byte 1word 1word 1word Write 1 word 06h Code 06h: Write 1 word to master output area 4x...

  • Page 121: Modbus - Example Communication

    Deployment PtP communication VIPA System 300S Modbus - Example communication Command telegram Slave Func- Address Number Number Data 1. Data 2. Check address tion 1. word of bytes word word code words CRC/LRC 1byte 1byte 1word 1word 1byte 1word 1word...
  • Page 122 Deployment PtP communication VIPA System 300S Modbus - Example communication Structure for the according PLC programs for master and slave: HB140 | CPU | 315-4PN43 | GB | 16-36...

  • Page 123: Deployment Ethernet Communication - Productive

    Deployment Ethernet communication - productive VIPA System 300S Basics - Industrial Ethernet in automation Deployment Ethernet communication - productive 7.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 124: Basics - Iso/Osi Reference Model

    Deployment Ethernet communication - productive VIPA System 300S Basics - ISO/OSI reference model 7.2 Basics - ISO/OSI reference model Overview The ISO/OSI reference model is based on a proposal that was devel- oped by the International Standards Organization (ISO). This repre- sents the first step towards an international standard for the different protocols.

  • Page 125: Basics - Terms

    Deployment Ethernet communication - productive VIPA System 300S Basics - Terms Layer 3 - Network layer The network layer is an agency layer. Business of this layer is to con- trol the exchange of binary data between stations that are not directly connected.

  • Page 126: Basics - Protocols

    Deployment Ethernet communication - productive VIPA System 300S Basics - Protocols Twisted Pair In the early days of networking the Triaxial- (yellow cable) or thin Ethernet cable (Cheapernet) was used as communication medium. This has been superseded by the twisted-pair network cable due to its immunity to interference.
  • Page 127 The acknowledgement of the data transfer is established from the partner station at level 7 of the ISO/OSI reference model. At the PLC side FB/SFB VIPA handling blocks are necessary for data transfer for the Siemens S7 connections. More about the usage of the handling blocks may be found in the manual Operation list HB00_OPL_SP7.

  • Page 128: Basics - Ip Address And Subnet

    Deployment Ethernet communication - productive VIPA System 300S 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 129 Deployment Ethernet communication - productive VIPA System 300S Basics - IP address and subnet 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 network. The Host-ID marks the network connec- tions of a participant (host) to this network.

  • Page 130: Fast Introduction

    Deployment Ethernet communication - productive VIPA System 300S Fast introduction Private IP networks These addresses can be used as net-ID by several organizations without causing conflicts, for these IP addresses are neither assigned in the Internet nor are routed in the Internet. To build up private IP-...

  • Page 131: Commissioning And Initialization

    Transfer of the complete project to CPU To be compatible to the Siemens SIMATIC Manager, the CPU 315-4PN43 from VIPA is to be configured as CPU 315-2 PN/DP (6ES7 315-2EH14-0AB0 V3.2)! The PROFINET IO controller is to be configured via the CPU sub module X2 (PN-IO).

  • Page 132: Hardware Configuration - Cpu

    Deployment Ethernet communication - productive VIPA System 300S Hardware configuration - CPU 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.

  • Page 133: Configure Siemens S7 Connections

    "In unknown project" or via deputy objects like "Other stations" or Siemens "SIMATIC S5 Station". The communication is controlled by the user program with VIPA han- dling blocks. To use this blocks, configured communication connec- tions are always necessary in the active station.
  • Page 134 Deployment Ethernet communication - productive VIPA System 300S Configure Siemens S7 connections Work environment of For the project engineering of connections, a thorough knowledge NetPro with NetPro from Siemens is required! The following passage only describes the basic usage of NetPro. More detailed information about NetPro is to be found in the according online manual res.
  • Page 135 Deployment Ethernet communication - productive VIPA System 300S Configure Siemens S7 connections 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 config- uration 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.
  • Page 136 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; the deployment is described in the manual "Operation list" of your CPU.
  • Page 137 Deployment Ethernet communication - productive VIPA System 300S Configure Siemens S7 connections 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...
  • Page 138 Block parameters – Local ID: The ID is the link to your PLC program. The ID must be iden- tical 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 gen- erated ID.

  • Page 139: Configure Open Communication

    Siemens S7-300 communication functions: By integration of the function blocks FB 12 ... FB 15 from VIPA you may access the Siemens S7-300 communication functions. Siemens S7-400 communication functions: For the Siemens S7-400 communication functions the SFB 12 ...
  • Page 140 Deployment Ethernet communication - productive VIPA System 300S Configure Open Communication The following connection-oriented protocols are supported with FBs for open communication via Industrial Ethernet: 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.
  • Page 141 Deployment Ethernet communication - productive VIPA System 300S Configure Open Communication The following connection-oriented protocol is supported with FBs for open communication via Industrial Ethernet: 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).

  • Page 142: Ncm Diagnostic - Help For Error Diagnostic

    7.11 NCM diagnostic - Help for error diagnostic Siemens NCM S7 diag- The VIPA PROFINET IO controller supports the Siemens NCM diag- nostic nostic tool. The NCM diagnostic tool is part of the Siemens SIMATIC Manager. This tool delivers information about the operating state of the communication functions of the online CPs dynamically.
  • Page 143 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. Set your PG/PC interface to "TCP/IP -> Network card ..". Via [OK] you start the online diag- nostic.
  • Page 144 Deployment Ethernet communication - productive VIPA System 300S NCM diagnostic - Help for error diagnostic Read diagnostic buffer The PROFINET IO controller has a diagnostic buffer. This has the architecture of a ring memory and may store up to 100 diagnostic messages.

  • Page 145: Deployment Ethernet Communication - Profinet

    Deployment Ethernet communication - PROFINET VIPA System 300S Basics PROFINET Deployment Ethernet communication - PROFINET 8.1 Basics PROFINET General PROFINET is an open Industrial Ethernet Standard from PRO- FIBUS & PROFINET International (PI) for automation. PROFINET is standardized in the IEC 61158.
  • Page 146 Subslot a further addressing level. With this additional addressing mode with using of different appli- cations, the overlapping of data areas can be prevented. Currently PROFINET IO devices from VIPA support API 0. HB140 | CPU | 315-4PN43 | GB | 16-36...

  • Page 147: Profinet Installation Guidelines

    PROFINET installation guidelines GSDML file From VIPA there is a GSDML files for your IO device available. This file may either be found on the supplied storage media or at the download area of www.vipa.com. Please install the GSDML file in your configuration tool.
  • Page 148 Deployment Ethernet communication - PROFINET VIPA System 300S PROFINET installation guidelines Industrial Ethernet Due to the open standard of PROFINET standard Ethernet com- ponents may be used. For industrial environment and due to the high transfer rate of 100MBit/s you PROFINET system should consist of Industrial Ethernet components.

  • Page 149: Profinet System Limits

    Deployment Ethernet communication - PROFINET VIPA System 300S PROFINET system limits 8.3 PROFINET system limits Maximum number Based on the devices, which have to communicate with the IO con- devices and configu- troller per ms, you can determine the maximum number of devices.

  • Page 150: Fast Introduction

    Deployment Ethernet communication - PROFINET VIPA System 300S Fast introduction Exceeding the max. With the following conditions there is the possibility to increase the number of bytes number of bytes up to 512 input and 512 output bytes per device, with it your project still runs.

  • Page 151: Commissioning And Initialization

    VIPA System 300S Commissioning and Initialization To be compatible with the Siemens SIMATIC Manager the CPU 315-4PN43 from VIPA is to be configured as CPU 315-2 PN/DP (6ES7 315-2EH14-0AB0 V3.2)! The Ethernet PG/OP channel of the CPU 315-4PN43 is to be configured as 1. module as CP343-1 (343-1EX11) from Siemens after the really plugged modules at the standard bus.

  • Page 152: Hardware Configuration - Cpu

    ACCU 2. For more information may be found in the manual "VIPA Operation list SPEED7" at "Differences between SPEED7 and 300V programming". Proceeding To be compatible with the Siemens SIMATIC Manager the following steps should be executed: Start the Siemens hardware configurator with a new project.

  • Page 153: Parameters - Profinet Io Controller

    PN-IO and Port 1 are described. 8.7.2 PN-IO General Short description Designation of the IO controller. The IO controller from VIPA always has the short description "PN-IO". Device name The device name on the Ethernet subnet must be unique. For an inte- grated PROFINET interface the device name is derived from the short description.

  • Page 154: Port 1

    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 ... ’ HB140 | CPU | 315-4PN43 | GB | 16-36...

  • Page 155: Configuration Profinet-I-Device / Shared-Device

    CPU. Here the communication happens by means of an I/O area, which was defined in the I-Device, before. Thus the higher-lever CPU can communicate with the I/O area VIPA specific settings are necessary in the I-Device. HB140 | CPU | 315-4PN43 | GB | 16-36...
  • Page 156 After you have defined the I/O area for data transfer of the I-Device I-Devices the following VIPA specific functions are to be activated in the proper- ties of the corresponding I-Device: ‘I-Device è I-Device mode’: ‘Parameter assignment for the PN interface and its ports on the higher-lever IO controller’...

  • Page 157: Topology - Configuration

    Deployment Ethernet communication - PROFINET VIPA System 300S Topology - Configuration 8.10 Topology - Configuration Overview By configuring the topology you specify for the PROFINET IO con- troller the physical connections between the stations in your PRO- FINET IO system These "neighbourhood relations" are used among others at "Device replacement without exchangeable medium".

  • Page 158: Device Replacement Without Exchangeable Medium/Pg

    Deployment Ethernet communication - PROFINET VIPA System 300S Device replacement without exchangeable medium/PG 8.11 Device replacement without exchangeable medium/PG Please consider that for this function the Siemens CPU 315-2 PN/DP (6ES7 315-2EH14-0AB0 V3.2) is to be used of the hardware catalog. For this the Siemens SIMATIC Manager V 5.5, SP2 and up is to be used.

  • Page 159: Replace Device

    For the replacement the "replace device" must be in "delivery state". device 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" local at your PG.

  • Page 160: Profinet Diagnostics

    Deployment Ethernet communication - PROFINET VIPA System 300S PROFINET diagnostics > Overview IO device configuration The PROFINET IO controller is configured by a hardware configu- ration. After the transmission of the project into the IO controller with connected IO devices, the IO controller has the whole infor- mation for the addressing of and the data exchange with the IO devices.

  • Page 161: Diagnostics With The Configuration And Engineering Tool

    SFB calls. More information about the usage of the SFB 52 may be found in the online help of your programming tool or in the manual "SPEED7 Operation list" from VIPA. HB140 | CPU | 315-4PN43 | GB | 16-36...
  • Page 162 Deployment Ethernet communication - PROFINET VIPA System 300S 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...

  • Page 163: Diagnostics Via Ob Start Information

    Deployment Ethernet communication - PROFINET VIPA System 300S PROFINET diagnostics > Diagnostics via OB start information 8.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.

  • Page 164: Diagnostics Via Status Leds

    Deployment Ethernet communication - PROFINET VIPA System 300S PROFINET diagnostics > Diagnostics via status LEDs 8.13.5 Diagnostics via status LEDs LEDs PROFINET IO controller X8 Meaning (Mainte- (Bus error) nance) yellow ● Bus error, no connection to sub net/switch wrong transfer rate...

  • Page 165: Configuration With Tia Portal

    9.1.1 General General In this chapter the project engineering of the VIPA CPU in the Sie- mens TIA Portal is shown. Here only the basic usage of the Siemens TIA Portal together with a VIPA CPU is shown. Please note that soft- ware changes can not always be considered and it may thus be devi- ations to the description.

  • Page 166: Tia Portal - Hardware Configuration - Cpu

    8 Jump to Portal or Project view 9.2 TIA Portal - Hardware configuration - CPU Configuration Siemens With the Siemens TIA Portal the CPU from VIPA is to be configured as CPU 315-2 PN/DP (6ES7 315-2EH14-0AB0 V3.2) from Siemens. Start the Siemens TIA Portal.

  • Page 167: Tia Portal - Hardware Configuration - I/O Modules

    PROFINET interface interface Setting standard CPU Since the CPU from VIPA is configured as Siemens CPU, so the set- parameters ting of the parameters takes place via the Siemens CPU. For para- metrization click in the Project arearespectively in the Device over- view at the CPU part.

  • Page 168: Tia Portal - Hardware Configuration - Ethernet Pg/Op Channel

    Configuration with TIA Portal VIPA System 300S TIA Portal - Hardware configuration - Ethernet PG/OP channel Device overview Module Slot Type PLC... CPU ... DI... DI... DO... DO... DIO... DIO... AI... AI... AO... AO... Parametrization For parametrization click in the Project area respectively in the Device overview on the module you want to parameterize.
  • Page 169 Configuration with TIA Portal VIPA System 300S TIA Portal - Hardware configuration - Ethernet PG/OP channel Assembly and commis- Install your System 300S with your CPU. sioning Wire the system by connecting cables for voltage supply and signals. Connect the Ethernet jack of the Ethernet PG/OP channel to Ethernet.
  • Page 170 Configuration with TIA Portal VIPA System 300S 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 171: Tia Portal - Hardware Configuration - Pg/Op Via Profinet

    IP address parameters have to be assigned to this. This is called "initialization". This can be done with the Siemens TIA Portal. Assembly and commis- Install your System 300S with your CPU. sioning Wire the system by connecting cables for voltage supply and signals.
  • Page 172 Configuration with TIA Portal VIPA System 300S TIA Portal - Hardware configuration - PG/OP via PROFINET Assign IP address You get valid IP address parameters from your system administrator. parameters The assignment of the IP address data happens online in the Sie- mens TIA Portal with the following proceeding: Start the Siemens TIA Portal.

  • Page 173: Tia Portal - Setting Vipa Specific Cpu Parameters

    9.6 TIA Portal - Setting VIPA specific CPU parameters Requirements Since the VIPA specific CPU parameters may be set, the installation of the SPEEDBUS.GSD from VIPA in the hardware catalog is neces- sary. The CPU may be configured in a PROFIBUS master system and the appropriate parameters may be set after installation.

  • Page 174: Thus, The Vipa Components Can Be Displayed, You

    German (default) SPEEDBUS.GSG German SPEEDBUS.GSE English The GSD files may be found at www.vipa.com at the "Service" part. The integration of the SPEEDBUS.GSD takes place with the following proceeding: Browse to www.vipa.com Click to ‘Service è Download è GSD- and EDS-Files è...
  • Page 175 Connect the slave system "VIPA_SPEEDbus". After installing the SPEEDBUS.GSD this may be found in the hardware catalog at: Other field devices > PROFIBUS DP > I/O > VIPA GmbH > VIPA_SPEEDbus. Set for the SPEEDbus slave system the PROFIBUS address 100.

  • Page 176: Tia Portal - Vipa-Include Library

    Downloads > VIPA LIB. The library is available as packed zip file for the corresponding TIA Portal version. As soon as you want to use VIPA specific blocks you have to import them into your project. Execute the following steps: –...

  • Page 177: Tia Portal - Project Transfer

    Transfer via Ethernet Transfer via memory card Transfer via MPI Currently the VIPA programming cables for transfer via MPI are not supported. This is only possible with the programming cable from Sie- mens. Establish a connection to the CPU via MPI with an appropriate programming cable.
  • Page 178 Configuration with TIA Portal VIPA System 300S TIA Portal - Project transfer Transfer via Ethernet For transfer via Ethernet the CPU has the following interface: X5: Ethernet PG/OP channel Initialization So that you may the according Ethernet interface, you have to assign IP address parameters by means of the "initialization".
  • Page 179 Configuration with TIA Portal VIPA System 300S TIA Portal - Project transfer The blinking of the MC LED 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 completely loaded and the SF LED gets on.

This manual is also suitable for:

Cpu 315-4pn43

Table of Contents