VIPA System 300S CPU | 315-4PN33 | Manual HB140 | CPU | 315-4PN33 | GB | 14-43
VIPA GmbH Ohmstr. 4 91074 Herzogenaurach Telephone: 09132-744-0 Fax: 09132-744-1864 email: info@vipa.com Internet: www.vipa.
VIPA System 300S Table of contents Table of contents 1 General...................................................................................... 1.1 Copyright © VIPA GmbH ................................................... 1.2 About this manual.............................................................. 1.3 Safety information.............................................................. 2 Basics..................................................................................... 2.
Table of contents VIPA System 300S 5.9.3 Transfer via MMC.......................................................... 5.10 Access to the internal Web page................................... 5.11 Operating modes............................................................ 5.11.1 Overview..................................................................... 5.11.2 Function security......................................................... 5.12 Overall reset........................................................
VIPA System 300S Table of contents 9 8.8 Configuration PROFINET IO device.............................. 8.9 Configuration PROFINET I Device / Shared Device...... 8.10 Topology - Configuration.............................................. 8.11 Device replacement without exchangeable medium/ PG................................................................................ 8.11.1 Replace device.......................................................... 8.12 Commissioning and start-up behaviour..............
General VIPA System 300S Copyright © VIPA GmbH 1 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.
VIPA System 300S General About this manual Trademarks VIPA, SLIO, System 100V, System 200V, System 300V, System 300S, System 400V, System 500S and Commander Compact are registered trademarks of VIPA Gesellschaft für Visualisierung und Prozessautomatisierung mbH. SPEED7 is a registered trademark of profichip GmbH. SIMATIC, STEP, SINEC, TIA Portal, S7-300 and S7-400 are registered trademarks of Siemens AG. Microsoft and Windows are registered trademarks of Microsoft Inc., USA.
General VIPA System 300S Safety information Guide to the document The following guides are available in the manual: n An overall table of contents at the beginning of the manual n References with page numbers Availability The manual is available in: n printed form, on paper n in electronic form as PDF-file (Adobe Acrobat Reader) Icons Headings Important passages in the text are highlighted by following icons and headings: DANGER! Immediate or likely danger. Personal injury is possible.
VIPA System 300S General Safety information CAUTION! The following conditions must be met before using or commissioning the components described in this manual: – Hardware modifications to the process control system should only be carried out when the system has been disconnected from power! – Installation and hardware modifications only by properly trained personnel. – The national rules and regulations of the respective country must be satisfied (installation, safety, EMC ...
Basics VIPA System 300S Operating structure of a CPU > General 2 Basics 2.1 Safety information for users Handling of electrostatic sensitive modules VIPA modules make use of highly integrated components in MOSTechnology. These components are extremely sensitive to over-voltages that can occur during electrostatic discharges. The following symbol is attached to modules that can be destroyed by electrostatic discharges.
VIPA System 300S Basics Operating structure of a CPU > Operands Cyclic processing Cyclicprocessing represents the major portion of all the processes that are executed in the CPU. Identical sequences of operations are repeated in a never-ending cycle. Timer processing Where a process requires control signals at constant intervals you can initiate certain operations based upon a timer, e.g. not critical monitoring functions at one-second intervals.
Basics VIPA System 300S CPU 315-4PN33 You may also gain direct access to peripheral modules via the bus from user application. The following types of data are available: n Bytes n Words n Blocks Bit Memory The bit memory is an area of memory that is accessible by means of certain operations. Bit memory is intended to store frequently used working data.
VIPA System 300S Basics CPU 315-4PN33 Access Please always use the CPU 315-2 PN/DP (6ES7 315-2EH13-0AB0 V2.6) from Siemens of the hardware catalog to project this CPU from VIPA. For the project engineering, a thorough knowledge of the Siemens SIMATIC Manager and the hardware configurator from Siemens is required! Memory The CPU has an integrated memory. Information about the capacity of the memory may be found at the front of the CPU.
Basics VIPA System 300S General data Operation Security n Wiring by means of spring pressure connections (CageClamps) at the front connector n Core cross-section 0.08...2.5mm2 n Total isolation of the wiring at module change n Potential separation of all modules to the backplane bus Dimensions/ Weight Dimensions of the basic enclosure: n 2tier width: (WxHxD) in mm: 80x125x120 Integrated power supply The CPU comes with an integrated power supply. The power supply is to be supplied with DC 24V.
VIPA System 300S Basics General data Protection of persons and device protection Inputs / outputs - AC / DC 50V, test voltage AC 500V Protective measures - against short circuit Environmental conditions to EN 61131-2 Climatic Storage / transport EN 60068-2-14 -25…+70°C Horizontal installation EN 61131-2 0…+60°C Vertical installation EN 61131-2 0…+60°C Air humidity EN 60068-2-30 RH1 Operation (without condensation, rel.
Basics VIPA System 300S General data EMC Standard Comment EN 61000-4-5 Surge, installation class 3 * *) Due to the high-energetic single pulses with Surge an appropriate external protective circuit with lightning protection elements like conductors for lightning and overvoltage is necessary.
VIPA System 300S Assembly and installation guidelines Installation dimensions 3 Assembly and installation guidelines 3.
Assembly and installation guidelines VIPA System 300S Assembly standard bus 3.2 Assembly standard bus General Profile rail The single modules are directly installed on a profile rail and connected via the backplane bus connector. Before installing the modules you have to clip the backplane bus connector to the module from the backside. The backplane bus connector is delivered together with the peripheral modules. Order number A B C 390-1AB60 160 140 10 390-1AE80 482 466 8.
VIPA System 300S Assembly and installation guidelines Cabling Assembly possibilities Please regard the allowed environment temperatures: n horizontal assembly: from 0 to 60°C n vertical assembly: from 0 to 40°C n lying assembly: from 0 to 40°C Approach 1. 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. 2.
Assembly and installation guidelines VIPA System 300S Cabling Here wires with a cross-section of 0.08mm2 to 2.5mm2 may be connected. You can use flexible wires without end case as well as stiff wires. 1 Test point for 2mm test tip 2 Locking (orange) for screwdriver 3 Round opening for wires The picture on the left side shows the cabling step by step from top view. Front connectors of the in-/output modules 20 1.
VIPA System 300S Assembly and installation guidelines Cabling 20pole screw connection 392-1AJ00 1. Open the front flap of your I/O module. 2. Bring the front connector in cabling position. For this you plug the front connector on the module until it locks. In this position the front connector juts out of the module and has no contact yet. 3. De-isolate your wires. If needed, use core end cases. 4. Thread the included cable binder into the front connector. 5.
Assembly and installation guidelines VIPA System 300S Installation guidelines 40pole screw connection 392-1AM00 1. Open the front flap of your I/O module. 2. Bring the front connector in cabling position. For this you plug the front connector on the module until it locks. In this position the front connector juts out of the module and has no contact yet. 3. De-isolate your wires. If needed, use core end cases. 4.
VIPA System 300S Assembly and installation guidelines Installation guidelines What does EMC mean? Electromagnetic compatibility (EMC) means the ability of an electrical device, to function error free in an electromagnetic environment without being interfered respectively without interfering the environment. The components of VIPA are developed for the deployment in industrial environments and meets high demands on the EMC.
Assembly and installation guidelines VIPA System 300S Installation guidelines n In special use cases you should appoint special EMC actions. – Consider to wire all inductivities with erase links. – Please consider luminescent lamps can influence signal lines. n Create a homogeneous reference potential and ground all electrical operating supplies when possible. – Please take care for the targeted employment of the grounding actions.
VIPA System 300S Hardware description Properties 4 Hardware description 4.
Hardware description VIPA System 300S Structure > Interfaces 4.2 Structure 4.2.1 General CPU 315-4PN33 1 2 3 4 5 6 7 8 9 Storage media slot (lockable) LEDs of the CPU part LEDs of the PROFINET IO controller Operating mode switch CPU Twisted pair interface for Ethernet PG/OP channel Slot for DC 24V power supply MPI interface PtP interface Twisted Pair interface for PROFINET IO controller The components 5 - 9 are under the front flap! 4.2.
VIPA System 300S Hardware description Structure > Memory management n The power supply is protected against polarity inversion and overcurrent. n The internal electronic is galvanically connected with the supply voltage. MPI interface X2 9pin SubD jack: n The MPI interface serves for the connection between programming unit and CPU. n By means of this the project engineering and programming happens. n MPI serves for communication between several CPUs or between HMIs and CPU.
Hardware description VIPA System 300S Structure > Battery backup for clock and RAM 4.2.4 Storage media slot n As external storage medium for applications and firmware you may use a MMC storage module (Multimedia card). n The VIPA storage media are pre-formatted with the PC format FAT16 and can be accessed via a card reader. n After PowerON respectively an overall reset the CPU checks, if there is a storage medium with data valid for the CPU.
VIPA System 300S Hardware description Structure > LEDs 4.2.6 Operating mode switch n With the operating mode switch you may switch the CPU between STOP and RUN. n During the transition from STOP to RUN the operating mode START-UP is driven by the CPU. n Placing the switch to MRES (Memory Reset), you request an overall reset with following load from MMC, if a project there exists. 4.2.7 LEDs LEDs CPU RN As soon as the CPU is supplied with 5V, the green PW-LED (Power) is on.
Hardware description VIPA System 300S Structure > LEDs RN ST SF FC (RUN) (STOP) (SFAIL) (FRCE) MC Meaning (MMC) ○ ● BB BB ● The alternate blinking indicates that there is new firmware on the memory card. ○ ○ BB BB ● The alternate blinking indicates that a firmware update is executed. ○ ● ● ● ● Firmware update finished without error. ○ BB* BB* BB* BB* * Blinking with 10Hz: Error during Firmware update.
VIPA System 300S Hardware description Technical data 4.3 Technical data Order no. 315-4PN33 Type CPU 315SN/PN ECO 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) 200 mA Current consumption (rated value) 0.7 A Inrush current 11 A I²t 0.4 A²s Max. current drain at backplane bus 2A Power loss 5.
Hardware description VIPA System 300S Technical data Order no. 315-4PN33 S7 counter remanence adjustable 0 up to 512 S7 counter remanence adjustable C0 .. C7 Number of S7 times 512 S7 times remanence adjustable 0 up to 512 S7 times remanence adjustable not retentive Data range and retentive characteristic Number of flags 8192 Byte Bit memories retentive characteristic adjustable adjustable 0 up to 8192 Bit memories retentive characteristic preset MB0 ..
VIPA System 300S Hardware description Technical data Order no.
Hardware description VIPA System 300S Technical data Order no. 315-4PN33 Type of interface RS485 Connector Sub-D, 9-pin, female Electrically isolated ü MPI ü MP²I (MPI/RS232) - DP master - DP slave - Point-to-point interface - Type X3 Type of interface RS485 Connector Sub-D, 9-pin, female Electrically isolated ü MPI - MP²I (MPI/RS232) - DP master - DP slave - Point-to-point interface ü Functionality MPI Number of connections, max.
VIPA System 300S Hardware description Technical data Order no. 315-4PN33 Activation/deactivation of DP slaves - Direct data exchange (slave-to-slave communication) - DPV1 - Transmission speed, min. - Transmission speed, max. - Number of DP slaves, max. - Address range inputs, max. - Address range outputs, max. - User data inputs per slave, max. - User data outputs per slave, max.
Hardware description VIPA System 300S Technical data Order no. 315-4PN33 Point-to-point protocol ASCII protocol ü STX/ETX protocol ü 3964(R) protocol ü RK512 protocol - USS master protocol ü Modbus master protocol ü Modbus slave protocol - Special protocols - Functionality PROFINET I/O controller Realtime Class - Conformance Class PROFINET IO Number of PN IO devices 128 IRT support - Prioritized start-up - Number of PN IO lines 1 Address range inputs, max.
VIPA System 300S Hardware description Technical data Order no. 315-4PN33 Ethernet communication CP Number of productive connections, max. 8 Number of productive connections by Siemens NetPro, max. 8 S7 connections BSEND, BRCV, GET, PUT, Connection of active and passive data handling User data per S7 connection, max. 32 KB TCP-connections FETCH PASSIV, WRITE PASSIV, Connection of passive data handling User data per TCP connection, max.
Deployment CPU 315-4PN33 VIPA System 300S Start-up behavior 5 Deployment CPU 315-4PN33 5.1 Assembly Information about assembly and cabling: Ä Chapter 3 ‘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. Default boot procedure, as delivered When the CPU is delivered it has been reset.
VIPA System 300S Deployment CPU 315-4PN33 Addressing > Addressing Backplane bus I/O devices 5.3 Addressing 5.3.1 Overview To provide specific addressing of the installed peripheral modules, certain addresses must be allocated in the CPU. At the start-up of the CPU, this assigns automatically peripheral addresses for digital in-/ output modules starting with 0 and ascending depending on the slot location.
Deployment CPU 315-4PN33 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.
VIPA System 300S Deployment CPU 315-4PN33 Hardware configuration - I/O modules For project engineering a thorough knowledge of the Siemens SIMATIC Manager and the Siemens hardware configurator is required. Please consider that this SPEED7-CPU has 4 ACCUs. After an arithmetic operation (+I, -I, *I, /I, +D, -D, *D, /D, MOD, +R, -R, *R, /R) the content of ACCU 3 and ACCU 4 is loaded into ACCU 3 and 2. This may cause conflicts in applications that presume an unmodified ACCU 2.
Deployment CPU 315-4PN33 VIPA System 300S Hardware configuration - Ethernet PG/OP channel Bus extension with IM 360 and IM 361 For the project engineering of more than 8 modules you may use line interface connections. For this you set in the hardware configurator the module IM 360 from the hardware catalog to slot 3 of your 1. profile rail. Now you may extend your system with up to 3 profile rails by starting each with an IM 361 from Siemens at slot 3. Considering the max.
VIPA System 300S Deployment CPU 315-4PN33 Hardware configuration - Ethernet PG/OP channel Assign IP address parameters You get valid IP address parameters from your system administrator. The assignment of the IP address data happens online in the Siemens SIMATIC Manager starting with version V 5.3 & SP3 with the following proceeding: 1. Start the Siemens SIMATIC Manager and set via ‘Options è Set PG/PC interface’the access path to ‘TCP/IP -> Network card ....’ . 2.
Deployment CPU 315-4PN33 VIPA System 300S Setting standard CPU parameters > Parameters CPU 5.7 Setting standard CPU parameters 5.7.1 Parameterization via Siemens CPU Parameterization via Siemens CPU 315-2EH13 Since the CPU is to be configured as Siemens CPU 315-2 PN/DP (6ES7 315-2EH13-0AB0 V2.6) in the Siemens hardware configurator, the standard parameters of the VIPA CPU may be set with "Object properties" of the CPU 315-2PN/DP during hardware configuration.
VIPA System 300S Deployment CPU 315-4PN33 Setting standard CPU parameters > Parameters CPU Startup n 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.
Deployment CPU 315-4PN33 VIPA System 300S Setting standard CPU parameters > Parameters CPU n Number of S7 Counters from C0: Enter the number of retentive S7 counter from C0 onwards. n Areas: This parameter is not supported. Interrupts n Priority: Here the priorities are displayed, according to which the hardware interrupt OBs are processed (hardware interrupt, timedelay interrupt, async. error interrupts).
VIPA System 300S Deployment CPU 315-4PN33 Setting VIPA specific CPU parameters > Proceeding Protection n Level of protection: Here 1 of 3 protection levels may be set to protect the CPU from unauthorized access.
Deployment CPU 315-4PN33 VIPA System 300S Setting VIPA specific CPU parameters > Proceeding Installation of the SPEEDBUS.GSD The GSD (Geräte-Stamm-Datei) is online available in the following language versions. Further language versions are available on inquires: Name Language SPEEDBUS.GSD 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: 1.
VIPA System 300S Deployment CPU 315-4PN33 Project transfer > Transfer via MPI 1. Perform a hardware configuration for the CPU. Ä Chapter 5.4 ‘Hardware configuration - CPU’ on page 40 2. Configure always as last module a Siemens DP master CP 342-5 (342-5DA02 V5.0). Connect and parametrize it at operation mode "DP-Master". 3. Connect the slave system "VIPA_SPEEDbus". After installing the SPEEDBUS.
Deployment CPU 315-4PN33 VIPA System 300S Project transfer > Transfer via Ethernet Net structure The structure of a MPI net is electrically identical with the structure of a PROFIBUS net. This means the same rules are valid and you use the same components for the build-up. The single participants are connected with each other via bus interface plugs and PROFIBUS cables. Please consider with the CP 315-4PN33 that the total extension of the MPI net does not exceed 50m.
VIPA System 300S Deployment CPU 315-4PN33 Project transfer > Transfer via MMC Initialization So that you may access the Ethernet PG/OP channel you have to assign IP address parameters by means of the "initialization". Ä Chapter 5.6 ‘Hardware configuration - Ethernet PG/OP channel’ on page 42 Transfer 1. For the transfer, connect, if not already done, the appropriate Ethernet port to your Ethernet. 2. Open your project with the Siemens SIMATIC Manager. 3.
Deployment CPU 315-4PN33 VIPA System 300S Access to the internal Web page The write command is controlled by means of the block area of the Siemens SIMATIC Manager ‘PLC è Copy RAM to ROM’. During the write process the MC LED of the CPU is blinking. When the LED expires the write process is finished. If this project is to be loaded automatically from the MMC with PowerON, you have to rename this on the MMC to AUTOLOAD.WLD.
VIPA System 300S Deployment CPU 315-4PN33 Access to the internal Web page Slot 100 OnBoardEthernet : MacAddress : 0020D50144C1, IPAddress : 172.20.120.62, SubnetMask : 255.255.255.0, Gateway : 172.20.120.
Deployment CPU 315-4PN33 VIPA System 300S Operating modes > Overview Standard Bus Modules at the standard bus ModuleType:9FC3: Digital Input 32 Type of module Baseaddress Input 0 Configured base address if exists firmware no. and package Rack 1 /Slot 5 ... 5.11 5.11.1 Rack no.
VIPA System 300S Deployment CPU 315-4PN33 Operating modes > Overview n RUN-LED on n STOP-LED off Operating mode HOLD The CPU offers up to 3 breakpoints to be defined for program diagnosis. Setting and deletion of breakpoints happens in your programming environment. As soon as a breakpoint is reached, you may process your program step by step. Precondition For the usage of breakpoints, the following preconditions have to be fulfilled: n Testing in single step mode is possible with STL.
Deployment CPU 315-4PN33 VIPA System 300S Overall reset 5.11.2 Function security The CPUs include security mechanisms like a Watchdog (100ms) and a parametrizable cycle time surveillance (parametrizable min. 1ms) that stop res. execute a RESET at the CPU in case of an error and set it into a defined STOP state. The VIPA CPUs are developed function secure and have the following system properties: Event concerns Effect RUN ® STOP general BASP (Befehls-Ausgabe-Sperre, i.e.
VIPA System 300S Deployment CPU 315-4PN33 Overall reset You should always issue an overall reset to your CPU before loading an application program into your CPU to ensure that all blocks have been cleared from the CPU. Overall reset by means of the operating mode switch Precondition The operating mode of the CPU is to be switched to STOP. For this switch the operating mode switch of the CPU to "STOP". ð The STOP-LED is on. Overall reset 1.
Deployment CPU 315-4PN33 VIPA System 300S Firmware update ® The MC LED is on. When the reload has been completed the LED expires. The operating mode of the CPU will be STOP respectively RUN, depending on the position of the operating mode switch. Reset to factory setting 5.13 The Reset to factory setting deletes completely the internal RAM of the CPU and resets this to delivery state. Please regard that the MPI address is also set back to default 2! Ä Chapter 5.
VIPA System 300S Deployment CPU 315-4PN33 Firmware update CAUTION! When installing a new firmware you have to be extremely careful. Under certain circumstances you may destroy the CPU, for example if the voltage supply is interrupted during transfer or if the firmware file is defective. In this case, please call the VIPA-Hotline! Please regard that the version of the update firmware has to be different from the existing firmware otherwise no update is executed.
Deployment CPU 315-4PN33 VIPA System 300S Reset to factory setting 6. Turn Power OFF and ON. Now it is checked by the CPU, whether further current firmware versions are available at the MMC. If so, again the LEDs SF and FC flash after a short startup period. Continue with point 3. ð If the LEDs do not flash, the firmware update is ready. Now a factory reset should be executed (see next page). After that the CPU is ready for duty. 5.
VIPA System 300S Deployment CPU 315-4PN33 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.15 Slot for storage media Overview At the front of the CPU there is a slot for storage media. As external storage medium for applications and firmware you may use a multimedia card (MMC).
Deployment CPU 315-4PN33 VIPA System 300S Extended know-how protection 5.16 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. But with according manipulation the Know-how protection is not guaranteed.
VIPA System 300S Deployment CPU 315-4PN33 MMC-Cmd - Auto commands Protection behavior Protected blocks are overwritten by a new protect.wld. Using a PG 3. persons may access protected blocks but only the block header is transferred to the PG. The block code that is to be protected remains in the CPU and cannot be read. Change respectively delete protected blocks Protected blocks in the RAM of the CPU may be substituted at any time by blocks with the same name.
Deployment CPU 315-4PN33 VIPA System 300S MMC-Cmd - Auto commands Command Description SAVE_PROJECT The recent project (blocks and hardware config- 0xE806 uration) is stored as "s7prog.wld" at the MMC.If the file just exists it is renamed to "s7prog.old". If your CPU is password protected so you have to add this as parameter. Otherwise there is no project written. Example: SAVE_PROJECT password FACTORY_RESET Executes "factory reset".
VIPA System 300S Deployment CPU 315-4PN33 VIPA specific diagnostic entries CMD_END Marks the end of the command sequence (0xE802) ... arbitrary text ... Text after the command CMD_END is not evaluated. The parameters IP address, subnet mask and gateway may be received from the system administrator. Enter the IP address if there is no gateway used. 5.18 VIPA specific diagnostic entries Entries in the diagnostic buffer You may read the diagnostic buffer of the CPU via the Siemens SIMATIC Manager.
Deployment CPU 315-4PN33 VIPA System 300S VIPA specific diagnostic entries The diagnosis is independent from the operating mode of the CPU. You may store a max. of 100 diagnostic entries in the CPU. The following page shows an overview of the VIPA specific Event-IDs.
VIPA System 300S Deployment CPU 315-4PN33 VIPA specific diagnostic entries Event-ID Description 0xE01B Error - Maximum number of plug-in modules exceeded 0xE020 Error - Interrupt information is not defined 0xE030 Error of the standard bus 0xE033 Internal error - Please contact the VIPA Hotline! 0xE0B0 SPEED7 is not stoppable (Probably undefined BCD value at timer) 0xE0C0 Not enough space in work memory for storing code block (block size exceeded) 0xE0CB Error at SSL access ZInfo1: 4=SSL wro
Deployment CPU 315-4PN33 VIPA System 300S VIPA specific diagnostic entries Event-ID Description 0xE101 Memory card error file system 0xE102 Memory card error FAT 0xE104 Memory card error at saving 0xE200 Memory card writing finished (Copy Ram2Rom) 0xE210 Memory card reading finished (reload after overall reset) 0xE21E Memory card reading: Error at reload (after overall reset), file "Protect.
VIPA System 300S Deployment CPU 315-4PN33 VIPA specific diagnostic entries Event-ID Description 0xE804 CMD - Auto command: WEBPAGE recognized and successfully executed 0xE805 CMD - Auto command: LOAD_PROJECT recognized and successfully executed 0xE806 CMD - Auto command: SAVE_PROJECT recognized and successfully executed 0xE807 CMD - Auto command: FACTORY_RESET recognized and successfully executed 0xE80B CMD - Auto command: DIAGBUF recognized and successfully executed 0xE80E CMD - Auto command
Deployment CPU 315-4PN33 VIPA System 300S VIPA specific diagnostic entries Event-ID Description 0xEA09 SBUS: Parametrized output data width unequal to plugged output data width ZInfo1: Parametrized output data width ZInfo2: Slot ZInfo3: Output data width of the plugged module 0xEA10 SBUS: Input periphery address outside the periphery area ZInfo1: Periphery address ZInfo2: Slot ZInfo3: Data width 0xEA11 SBUS: Output periphery address outside the periphery area ZInfo1: Periphery address ZInfo2: Slot
VIPA System 300S Deployment CPU 315-4PN33 VIPA specific diagnostic entries Event-ID Description 0xEA30 Internal error - Please contact the VIPA Hotline! 0xEA40 Internal error - Please contact the VIPA Hotline! 0xEA41 Internal error - Please contact the VIPA Hotline! 0xEA50 Error - PROFINET configuration ZInfo1: User slot of the PROFINET I/O controller ZInfo2: IO-Device-No.
Deployment CPU 315-4PN33 VIPA System 300S VIPA specific diagnostic entries Event-ID Description 0xEA64 PROFINET/EtherCAT CP Configuration error: Zinfo1: Bit 0: Too many devices Bit 1: Too many devices per ms Bit 2: Too many input bytes per ms Bit 3: Too many output bytes per ms Bit 4: Too many input bytes per device Bit 5: Too many output bytes per device Bit 6: Too many productive connections Bit 7: Too many input bytes in the process image Bit 8: Too many output bytes in the process image Bit 9: Con
VIPA System 300S Deployment CPU 315-4PN33 VIPA specific diagnostic entries Event-ID Description 0xEA68 Error - PROFINET IO controller - writing record set PK: Error type 0: DATA_RECORD_ERROR_LOCAL 1: DATA_RECORD_ERROR_STACK 2: DATA_RECORD_ERROR_REMOTE OBNo: PROFINET IO controller slot DatId: Device-No.
Deployment CPU 315-4PN33 VIPA System 300S VIPA specific diagnostic entries Event-ID Description 0xEA6D PROFINET IO controller No empty name PK: Rackslot OBNo: PLC Mode DatId: 0 ZInfo1: Device ID ZInfo2: ZInfo3: - 0xEA6E PROFINET IO controller RPC response missing PK: Rackslot OBNo: PLC Mode DatId: 0 ZInfo1: Device ID ZInfo2: ZInfo3: - 0xEA6F PROFINET IO controller PN module mismatch PK: Rackslot OBNo: PLC-Mode DatId: 0 ZInfo1: Device ID ZInfo2: ZInfo3: - 0xEA97 Storage error SBUS service channel
VIPA System 300S Deployment CPU 315-4PN33 VIPA specific diagnostic entries Event-ID Description 0xEAA0 Emac Error occurred OBNo: Current PLC mode ZInfo1: Diagnostics address of the master / controller ZInfo2: 0: None Rx queue is full 1: No send buffer available 2: Send stream was cut off; sending failed 3: Exhausted retries 4: No receive buffer available in Emac DMA 5: Emac DMA transfer aborted 6: Queue overflow 7: Unexpected frame received ZInfo3: Number of errors, which occurred 0xEAB0 Link mode no
Deployment CPU 315-4PN33 VIPA System 300S VIPA specific diagnostic entries Event-ID Description 0xEC03 EtherCAT: Configuration error ZInfo1: Errorcode 1: NUMBER_OF_SLAVES_NOT_SUPPORTED 2: SYSTEM_IO_NR_INVALID 3: INDEX_FROM_SLOT_ERROR 4: MASTER_CONFIG_INVALID 5: MASTER_TYPE_ERROR 6: SLAVE_DIAG_ADDR_INVALID 7: SLAVE_ADDR_INVALID 8: SLAVE_MODULE_IO_CONFIG_INVALID 9: LOG_ADDR_ALREADY_IN_USE 10: NULL_PTR_CHECK_ERROR 11: IO_MAPPING_ERROR 12: ERROR 0xEC04 EtherCAT: Multiple configuration of a periphery add
VIPA System 300S Deployment CPU 315-4PN33 VIPA specific diagnostic entries Event-ID Description 0xEC11 EtherCAT: Restoration bus with missing slaves OB start Info (Local data) StartEvent and Eventclass: 0xEC11 DatID: 0xXXYY: XX=0x54 with input address in ZInfo1, XX=0x55 with output address.
Deployment CPU 315-4PN33 VIPA System 300S VIPA specific diagnostic entries Event-ID Description 0xED12 EtherCAT: Failure slave OB start Info (Local data) StartEvent and Eventclass: 0xED12 DatID: 0xXXYY: XX=0x54 with input address in ZInfo1, XX=0x55 with output address.
VIPA System 300S Deployment CPU 315-4PN33 VIPA specific diagnostic entries Event-ID Description 0xED22 EtherCAT: Bus state change without calling OB86 OB start Info (Local data) StartEvent and Eventclass: 0xED22 DatID: 0xXXYY: XX=0x54 with input address in ZInfo1, XX=0x55 with output address.
Deployment CPU 315-4PN33 VIPA System 300S VIPA specific diagnostic entries Event-ID Description 0xED61 EtherCAT: Diagnostics buffer CP: CoE emergency PK: EtherCAT station address (low byte) OB: EtherCAT station address (high byte) DatID 1/2: Error code ZInfo1: 0xYYZZ: YY: Error register ZZ: MEF byte 1 ZInfo 2: 0xYYZZ: YY: MEF byte 2 ZZ: MEF byte 3 ZInfo3: 0xYYZZ: YY: MEF byte 4 ZZ: MEF byte 5 0xED62 EtherCAT: Diagnostics buffer CP: Error on SDO access during state change PK: EtherCAT station address
VIPA System 300S Deployment CPU 315-4PN33 Control and monitoring of variables with test functions Event-ID Description 0xEFFF Internal error - Please contact the VIPA Hotline! PK: C-Source module number | DatID: Line number 5.19 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 Manager.
Deployment CPU 315-4PN33 VIPA System 300S Control and monitoring of variables with test functions It is possible to check the wiring and proper operation of output modules. You can set outputs to any desired status with or without a control program. The process image is not modified but outputs are no longer inhibited. Control of variables The following variables may be modified: I, Q, M, T, C and D.
VIPA System 300S Deployment PtP communication Principle of the data transfer 6 Deployment PtP communication 6.1 Fast introduction General With this CPU the integrated RS485 interface is fix set to PtP (pointto-point) communication. n PtP functionality – For operation there is no further configuration in the hardware configurator required. – Using the PtP functionality the RS485 interface is allowed to connect via serial point-to-point connection to different source respectively target systems.
Deployment PtP communication VIPA System 300S Deployment of RS485 interface for PtP n In opposite to ASCII and STX/ETX, the protocols 3964R, USS and Modbus require the acknowledgement of the partner. n An additional call of the FC/SFC 217 SER_SND causes a return value in RetVal that includes among others recent information about the acknowledgement of the partner. n Further on for USS and Modbus after a SER_SND the acknowledgement telegram must be evaluated by a call of the FC/SFC 218 SER_RCV. 6.
VIPA System 300S Deployment PtP communication Parametrization > FC/SFC 216 - SER_CFG Pin RS485 8 RxD/TxD-N (Line A) 9 n.c. Connection 6.4 Parametrization 6.4.1 FC/SFC 216 - SER_CFG Description The parametrization happens during runtime deploying the FC/SFC 216 (SER_CFG). You have to store the parameters for STX/ETX, 3964R, USS and Modbus in a DB.
Deployment PtP communication VIPA System 300S Parametrization> FC/SFC 216 - SER_CFG All time settings for timeouts must be set as hexadecimal value. Find the Hex value by multiply the wanted time in seconds with the baudrate. Example: Wanted time 8ms at a baudrate of 19200baud Calculation: 19200bit/s x 0.008s ≈ 154bit → (9Ah) Hex value is 9Ah. PROTOCOL Here you fix the protocol to be used.
VIPA System 300S Deployment PtP communication Parametrization > FC/SFC 216 - SER_CFG DBB4: CharTimeout WORD (Char.
Deployment PtP communication VIPA System 300S Communication> FC/SFC 217 - SER_SND Error code Description 0000h no error 809Ah Interface not found e. g. interface is used by PROFIBUS In the VIPA SLIO CPU with FeatureSet PTP_NO only the ASCII protocol is configurable. If another protocol is selected the FC/SFC216 also left with this error code.
VIPA System 300S Deployment PtP communication Communication > FC/SFC 217 - SER_SND Parameters Parameter Declaration Data type Description DATAPTR IN ANY Pointer to Data Buffer for sending data DATALEN OUT WORD Length of data sent RETVAL OUT WORD Return value (0 = OK) DATAPTR Here you define a range of the type Pointer for the send buffer where the data to be sent are stored. You have to set type, start and length. Example: Data is stored in DB5 starting at 0.0 with a length of 124byte.
Deployment PtP communication VIPA System 300S Communication> FC/SFC 217 - SER_SND Protocol specific RETVAL values ASCII Value Description 9000h Buffer overflow (no data send) 9002h Data too short (0byte) STX/ETX Value Description 9000h Buffer overflow (no data send) 9001h Data too long (>1024byte) 9002h Data too short (0byte) 9004h Character not allowed 3964R Value Description 2000h Send ready without error 80FFh NAK received - error in communication 80FEh Data transfer without ac
VIPA System 300S Deployment PtP communication Communication > FC/SFC 217 - SER_SND Modbus RTU/ASCII Master Error code Description Principles of programming 2000h Send ready (positive slave respond) 2001h Send ready (negative slave respond) 8080h Receive buffer overflow (no space for receipt) 8090h Acknowledgement delay time exceeded 80F0h Wrong checksum in respond 80FDh Length of respond too long 80FEh Wrong function code in respond 80FFh Wrong slave address in respond 9000h Buffer over
Deployment PtP communication VIPA System 300S Communication> FC/SFC 217 - SER_SND USS / Modbus ASCII / STX/ETX 92 HB140 | CPU | 315-4PN33 | GB | 14-43
VIPA System 300S Deployment PtP communication Communication > FC/SFC 218 - SER_RCV 6.5.3 FC/SFC 218 - SER_RCV Description 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.
Deployment PtP communication VIPA System 300S Communication> FC/SFC 218 - SER_RCV STX/ETX Bit Error Description 0 overflow The received telegram exceeds the size of the receive buffer. 1 char A sign outside the range 20h ... 7Fh has been received. 3 overflow Buffer is full. 3964R / Modbus RTU/ASCII Master RETVAL FC/SFC 218 (Return value) Bit Error Description 0 overflow The received telegram exceeds the size of the receive buffer.
VIPA System 300S Deployment PtP communication Protocols and procedures Principles of programming The following picture shows the basic structure for programming a receive command. This structure can be used for all protocols. 6.6 Protocols and procedures Overview The CPU supports the following protocols and procedures: n n n n n ASCII communication STX/ETX 3964R USS Modbus ASCII ASCII data communication is one of the simple forms of data exchange. Incoming characters are transferred 1 to 1.
Deployment PtP communication VIPA System 300S Protocols and procedures n Any data transferred from the periphery must be preceded by a Start followed by the data characters and the end character. Depending of the byte width the following ASCII characters can be transferred: 5bit: not allowed: 6bit: 20...3Fh, 7bit: 20...7Fh, 8bit: 20...FFh. n The effective data, which includes all the characters between Start and End are transferred to the CPU when the End has been received.
VIPA System 300S Deployment PtP communication Protocols and procedures When a DLE is transferred as part of the information it is repeated to distinguish between data characters and DLE control characters that are used to establish and to terminate the connection (DLE duplication). The DLE duplication is reversed in the receiving station. The 3964R procedure requires that a lower priority is assigned to the communication partner.
Deployment PtP communication VIPA System 300S Protocols and procedures with STX - Start sign STW - Control word LGE - Telegram length ZSW - State word ADR - Address HSW - Main set value PKE - Parameter ID HIW - Main effective value IND - Index BCC - Block Check Character PWE - Parameter value Broadcast with set bit 5 in ADR byte A request can be directed to a certain slave ore be send to all slaves as broadcast message.
VIPA System 300S Deployment PtP communication Modbus - Function codes ASCII, RTU mode Modbus offers 2 different transfer modes. The mode selection happens during runtime by using the FC/SFC 216 SER_CFG. n ASCII mode: Every byte is transferred in the 2 sign ASCII code. The data are marked with a start and an end sign. This causes a transparent but slow transfer. n RTU mode: Every byte is transferred as one character. This enables a higher data pass through as the ASCII mode.
Deployment PtP communication VIPA System 300S Modbus - Function codes A description of the function codes follows below. Overview With the following Modbus function codes a Modbus master can access a Modbus slave: With the following Modbus function codes a Modbus master can access a Modbus slave.
VIPA System 300S Deployment PtP communication Modbus - Function codes Without an error, the function code is sent back. Slave answer: Function code OR 80h ® Error Function code ® OK Byte sequence in a word 1 word High-byte Low-byte Check sum CRC, RTU, LRC The shown check sums CRC at RTU and LRC at ASCII mode are automatically added to every telegram. They are not shown in the data block.
Deployment PtP communication VIPA System 300S Modbus - Function codes 04h: Read n words master input area 3x Command telegram Slave address Function code Address 1. bit Number of words Check sum CRC/ LRC 1byte 1byte 1word 1word 1word Respond telegram Slave address Function code Number of read bytes Data 1. word Data 2. word 1byte 1byte 1byte 1word 1word ... Check sum CRC/LRC 1word max.
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 Slave address Function code Address word Value word Check sum CRC/ LRC 1byte 1byte 1word 1word 1word Respond telegram Write n bits 0Fh Code 0Fh: Write n bits to master output area 0x Please regard that the number of bits has addition
Deployment PtP communication VIPA System 300S Modbus - Example communication Write n words 10h Code 10h: Write n words to master output area 4x Command telegram Slave address Function code 1byte 1byte Address Number Number 1. word of words of bytes 1word 1word 1byte Data 1. word Data 2. word ... Check sum CRC/ LRC 1word 1word 1word 1word max. 125words Respond telegram Slave address Function code Address 1.
VIPA System 300S Deployment PtP communication Modbus - Example communication 3. Execute the project engineering of the slave! The PLC user application at the slave has the following structure: n OB 100: Call SFC 216 (configuration as Modbus RTU slave) with timeout setting and Modbus address in the DB and error evaluation. n OB 1: Call SFC 217 (SER_SND) for data transport from the slave CPU to the output buffer. Call SFC 218 (SER_RECV) for the data transport from the input buffer to the CPU.
Deployment PtP communication VIPA System 300S Modbus - Example communication 106 HB140 | CPU | 315-4PN33 | GB | 14-43
VIPA System 300S Deployment Ethernet communication - productive Basics - Industrial Ethernet in automation 7 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.
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 developed by the International Standards Organization (ISO). This represents the first step towards an international standard for the different protocols. It is referred to as the ISO-OSI layer model. OSI is the abbreviation for Open System Interconnection, the communication between open systems.
VIPA System 300S Deployment Ethernet communication - productive Basics - Terms Layer 3 - Network layer The network layer is an agency layer. Business of this layer is to control the exchange of binary data between stations that are not directly connected. It is responsible for the logical connections of layer 2 communications. Layer 3 supports the identification of the single network addresses and the establishing and disconnecting of logical communication channels.
Deployment Ethernet communication - productive VIPA System 300S Basics - Protocols coaxial Ethernet networks are based on a bus topology the twistedpair network is based on a point-to-point scheme. The network that may be established by means of this cable has a star topology. Every station is connected to the star coupler (hub/switch) by means of a separate cable. The hub/switch provides the interface to the Ethernet.
VIPA System 300S Deployment Ethernet communication - productive Basics - Protocols More about the usage of the handling blocks may be found in the manual Operation list HB00_OPL_SP7 in chapter "VIPA specific blocks". Open communication In the ‘open communication’ the communication takes place via the user program by means of handling blocks. These blocks are part of the Siemens SIMATIC Manager. You will find these in the ‘Standard Library’ at ‘Communication Blocks’ .
Deployment Ethernet communication - productive VIPA System 300S Basics - IP address and subnet 7.5 Basics - IP address and subnet IP address structure Exclusively IPv4 is supported. At IPv4 the IP address is a 32bit address that must be unique within the network and consists of 4 numbers that are separated by a dot. Every IP address is a combination of a Net-ID and a Host-ID and has the following Structure: xxx.xxx.xxx.xxx Range: 000.000.000.000 to 255.255.255.
VIPA System 300S Deployment Ethernet communication - productive 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 IPNetworks within the Internet, RFC1597/1918 reserves the following address areas: Network class from IP to IP Standard subnet mask A 10.0.0.0 10.255.255.255 255.0.0.0 B 172.16.0.0 172.31.255.
Deployment Ethernet communication - productive VIPA System 300S Commissioning and initialization n Configure connections – Siemens S7 connections (Configuration via Siemens NetPro, communication via VIPA handling blocks) – Open communication (Configuration and communication happens by standard handling blocks) n Transfer of the complete project to CPU To be compatible to the Siemens SIMATIC Manager, the CPU 315-4PN33 from VIPA is to be configured as CPU 315-2 PN/DP (6ES7 315-2EH13-0AB0 V2.
VIPA System 300S Deployment Ethernet communication - productive Hardware configuration - CPU 5. Either type in the IP configuration like IP address, subnet mask and gateway. Or your station is automatically provided with IP parameters by means of a DHCP server. Depending of the chosen option the DHCP server is to be supplied with MAC address, equipment name or client ID. The client ID is a numerical order of max. 63 characters. The following characters are allowed: "hyphen", 0-9, a-z, A-Z 6.
Deployment Ethernet communication - productive VIPA System 300S Configure Siemens S7 connections 7.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.
VIPA System 300S Deployment Ethernet communication - productive Configure Siemens S7 connections Work environment of NetPro For the project engineering of connections, a thorough knowledge 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. documentation. Start NetPro by clicking on a "net" in the Siemens SIMATIC Manager or on "connections" within the CPU.
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 configuration or graphically via NetPro. For this you point the mouse on the coloured net mark of the according CP and drag and drop it to the net you want to link. Now the CP is linked up to the wanted net by means of a line. Projecting connections 1.
VIPA System 300S Deployment Ethernet communication - productive Configure Siemens S7 connections 2. Choose the connection partner and the type of connection and confirm with [OK]. ð If activated, a properties dialog for the according connection opens as link to your PLC user program. 3. Connection types After every connection was configured by this way, you may save and compile your project and exit NetPro. Exclusively Siemens S7 connection may be configured with NetPro.
Deployment Ethernet communication - productive VIPA System 300S Configure Siemens S7 connections Combination options with deployment of the FB/SFB VIPA handling blocks 120 Connection partner Connection establishing Connection specified in NetPro (in the current project) active/passive specified unspecified in NetPro active (in the current passive project) specified unspecified in NetPro active/passive (in the unknown project) specified (connection name in an other project) unspecified HB140
VIPA System 300S Deployment Ethernet communication - productive Configure Siemens S7 connections In the following every relevant parameter of a Siemens S7 connection is described: n Local connection end point: Here you may define how the connection is to be established. Since the Siemens SIMATIC Manager can identify the communication options by means of the end points, some options are already preset and may not be changed.
Deployment Ethernet communication - productive VIPA System 300S Configure Open Communication Siemens S7 connection - Communication functions With the SPEED7 CPUs of VIPA there are two possibilities for the deployment of the communication functions: n Siemens S7-300 communication functions: By integration of the function blocks FB 8 ... FB 15 from VIPA you may access the Siemens S7-300 communication functions.
VIPA System 300S Deployment Ethernet communication - productive Configure Open Communication The following connection-oriented protocols are supported with FBs for open communication via Industrial Ethernet: n TCP/IP native according to RFC 793 (connection types 01h and 11h): – During data transmission, no information about the length or about the start and end of a message is transmitted. – The receiver has no means of detecting where one message ends in the data stream and the next one begins.
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: n UDP according to RFC 768 (with connection type 13h): – In this case, when calling the sending block you have to specify the address parameters of the receiver (IP address and port number). – During data transmission, information on the length and the end of the message is also transmitted.
VIPA System 300S Deployment Ethernet communication - productive NCM diagnostic - Help for error diagnostic FB Label Connection-oriented protocols: Connectionless protocol: UDP TCP native as per RFC 793, as per RFC 768 ISO on TCP as per RFC 1006 FB 65 TCON Establishing a connection Configuring the local communications access point FB 66 TDISCON Terminating a connection Closing the local communications access point FB 67 TUSEND Sending data FB 68 TURCV Receiving data 7.
Deployment Ethernet communication - productive VIPA System 300S NCM diagnostic - Help for error diagnostic Structure The working surface of the diagnostic tool has the following structure: n The ‘navigation area’ at the left side contains the hierarchical listed diagnostic objects. Depending on CP type and configured connections there is an adjusted object structure in the navigation area.
VIPA System 300S Deployment Ethernet communication - productive 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. The NCM diagnostic allows you to monitor and evaluate the diagnostic messages via the diagnostic object Diagnostic buffer. Via a double click on a diagnostic message the NCM diagnostic shows further information.
Deployment Ethernet communication - PROFINET VIPA System 300S Basics PROFINET 8 Deployment Ethernet communication - PROFINET 8.1 Basics PROFINET General n PROFINET is an open Industrial Ethernet Standard from PROFIBUS & PROFINET International (PI) for automation. PROFINET is standardized in the IEC 61158. n PROFINET uses TCP/IP and IT standards and supplements the PROFIBUS technology for applications, where fast data communication with industrial IT functions is demanded.
VIPA System 300S Deployment Ethernet communication - PROFINET Basics PROFINET Properties of PROFINET PROFINET of IEC 61158 has the following properties: n Full-duplex transfer with 100MBit/s via copper respectively fibre optics. n Switched Ethernet n Auto negotiation (negotiates the transfer parameters) n Auto crossover (transmission and receipt lines are crossed automatically if necessary) n Wireless communication via Bluetooth respectively WLAN n UDP/IP is used as overlaid protocol.
Deployment Ethernet communication - PROFINET VIPA System 300S PROFINET installation guidelines 8.2 PROFINET installation guidelines Generals to data security n The topic of data security and access protection have become increasingly important in the industrial environment. The increased networking of entire industrial systems to the network levels within the company together with the functions of remote maintenance have all served to increase vulnerability.
VIPA System 300S Deployment Ethernet communication - PROFINET PROFINET system limits Star n If you connect communication devices to a switch with more tan 2 PROFINET ports, you automatically create a star network topology. n If an individual PROFINET device fails, this does not automatically lead to failure of the entire network, in contrast to other structures. It is only if a switch fails that part of the communication network will fail as well.
Deployment Ethernet communication - PROFINET VIPA System 300S PROFINET system limits The PROFINET IO controller has the following system limits Devices per ms Max. number of devices Max. number of configurable connections 1 128 20 0 0 24 Output bytes per ms O n B A Output bytes per ms Number of devices Number output bytes per device Refresh time per device The PROFINET IO controller has the following system limits: n Max. Number output bytes per ms: 800 n Max.
VIPA System 300S Deployment Ethernet communication - PROFINET Commissioning and Initialization 8.4 Fast introduction 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 Siemens CPU, which is used for configuration, offers further functions! To use some described PROFINET functions, it is necessary to deploy another Siemens CPU for configuration. Here, however, is pointed to explicitly.
Deployment Ethernet communication - PROFINET VIPA System 300S Hardware configuration - CPU Assign IP address parameters This function is supported only if the PROFINET IO controller is not yet configured. You get valid IP address parameters from your system administrator. The assignment of the IP address data happens online in the Siemens SIMATIC Manager starting with version V 5.3 & SP3 with the following proceeding: 1. Start the Siemens SIMATIC Manager. 2. Switch to "TCP/IP -> Network card ....
VIPA System 300S Deployment Ethernet communication - PROFINET Parameters - PROFINET IO controller > Precondition Please consider that this SPEED7-CPU has 4 ACCUs. After an arithmetic operation (+I, -I, *I, /I, +D, -D, *D, /D, MOD, +R, -R, *R, /R) the content of ACCU 3 and ACCU 4 is loaded into ACCU 3 and 2. This may cause conflicts in applications that presume an unmodified ACCU 2.
Deployment Ethernet communication - PROFINET VIPA System 300S Parameters - PROFINET IO controller > Port 1 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 integrated PROFINET interface the device name is derived from the short description. Comment Here the purpose may be entered for which the IO controller is being used.
VIPA System 300S Deployment Ethernet communication - PROFINET Configuration PROFINET IO device Addresses Via the port address the diagnostics information of the IO controller may be accessed. Topology These parameters serve for the handling of the ports and should not be changed. Options These parameters serve for the handling of the ports and should not be changed. 8.8 Configuration PROFINET IO device Install GSDML n The modules, which may be configured here are listed in the hardware catalog.
Deployment Ethernet communication - PROFINET VIPA System 300S Configuration PROFINET I Device / Shared Device 8.9 Configuration PROFINET I Device / Shared Device General n I-Device (intelligent device) offers PROFINET I/O communication of a CPU with I/O periphery as "intelligent device" to a higherlever CPU. Here the communication happens by means of an I/O area, which was defined in the I-Device, before.
VIPA System 300S Deployment Ethernet communication - PROFINET Topology - Configuration Create an I-Device GSD file and install it at your hardware catalog with ‘Options è Create GSD file for I-Device’. Open the hardware configuration of your higher-lever VIPA CPU and connect your IDevice from ‘Preconfigured Stations’ . IO controller which supports I- and SharedDevices The PROFINET CPU from VIPA can not be configured as I-Device but it supports I- and Shared-Devices.
Deployment Ethernet communication - PROFINET VIPA System 300S Device replacement without exchangeable medium/PG 2. Here you have the following parameters: n Port interconnection – Local port: Name of the local port – Medium: Specifying the line type (copper, fibre optic cable). Currently, this parameter is not evaluated. – Cable name Specifying a cable name n Partners – Partner port: Name of the port to which the selected port is interconnected.
VIPA System 300S Deployment Ethernet communication - PROFINET Commissioning and start-up behaviour Configuring the function The configuration of the function Device replacement without exchangeable medium/PG in your PROFINET IO system happens with the following approach: 1. Double-click at the PROFINET interface of the IO controller of the CPU. ð The properties dialog of this PROFINET interface is opened 8.11.1 2.
Deployment Ethernet communication - PROFINET VIPA System 300S Commissioning and start-up behaviour Online with bus parameters without project n For the communication between IO controller and IO device the ways for the communication are to be defined before. For the clear specification of the communication ways, these are established during the start-up by the IO controller, based on the project data. Here the configuration takes place by a hardware configuration.
VIPA System 300S Deployment Ethernet communication - PROFINET PROFINET diagnostics > Diagnostics during runtime in the user program 8.13 8.13.1 PROFINET diagnostics Overview There are the following possibilities to get diagnostics information from your system: n n n n 8.13.
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 AN M10.1 'there is no job triggered (REQ=0) then S M10.
VIPA System 300S Deployment Ethernet communication - PROFINET PROFINET diagnostics > Diagnostics via status LEDs 8.13.4 Diagnostics via OB start information n On an error the faulty system generates a diagnostics message for the CPU. Then the CPU calls the according diagnostics OB. Here the CPU operating system transfers start information to the local data of the OB. n By evaluating the start information of the according OB you can get information about cause and location of the error.
Deployment Ethernet communication - PROFINET VIPA System 300S PROFINET diagnostics > Diagnostics via status LEDs MT BF (Maintenance) (Bus error) BB X Meaning With a suited configuration tool you can cause the LED to blink by means of the function ‘member blink test’ . This can be usefull for e.g. identification of the module.
VIPA System 300S Configuration with TIA Portal TIA Portal - Work environment > Work environment of the TIA Portal 9 Configuration with TIA Portal 9.1 TIA Portal - Work environment 9.1.1 General General In this chapter the project engineering of the VIPA CPU in the Siemens TIA Portal is shown. Here only the basic usage of the Siemens TIA Portal together with a VIPA CPU is shown. TIA means Totally integrated Automation from Siemens. Here your VIPA PLCs may be configured and linked.
Configuration with TIA Portal VIPA System 300S TIA Portal - Hardware configuration - CPU Areas of the Project view The Project view is divided into the following areas: 1 2 3 4 5 6 7 8 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 Hardware catalog and tools "Task-Cards" to select hardware catalog, tasks and libraries Jump to Portal or Proje
VIPA System 300S Configuration with TIA Portal TIA Portal - Hardware configuration - I/O modules Device overview: Module Setting standard CPU parameters ... Slot ... Type PLC ... 2 CPU 315-2 PN/DP MPI/DP interface 2 X1 MPI/DP interface PROFINET interface 2 X2 PROFINET interface ... ... ... ... Since the CPU from VIPA is configured as Siemens CPU, so the setting of the parameters takes place via the Siemens CPU.
Configuration with TIA Portal VIPA System 300S TIA Portal - Hardware configuration - Ethernet PG/OP channel Device overview Module ... Slot ... Type PLC... 2 CPU ... ... ... ... ... 3 Parametrization DI... 4 DI... DO... 5 DO... DIO... 6 DIO... AI... 7 AI... AO... 8 AO... For parametrization click in the Project area respectively in the Device overview on the module you want to parameterize. The parameters of the module appear in the Properties dialog.
VIPA System 300S Configuration with TIA Portal TIA Portal - Hardware configuration - Ethernet PG/OP channel Assembly and commissioning 1. Install your System 300S with your CPU. 2. Wire the system by connecting cables for voltage supply and signals. 3. Connect the Ethernet jack of the Ethernet PG/OP channel to Ethernet. 4. Switch on the power supply. ð After a short boot time the CP is ready for communication. He possibly has no IP address data and requires an initialization.
Configuration with TIA Portal VIPA System 300S TIA Portal - Hardware configuration - Ethernet PG/OP channel Due to the system you may get a message that the IP address could not be assigned. This message can be ignored. Take IP address parameters in project 1. Open your project. 2. If not already done, configure in the ‘Device configuration’ a Siemens CPU 315-2 PN/DP (6ES7 315-2EH13-0AB0 V2.6). 3. Configure the System 300 modules. 4.
VIPA System 300S Configuration with TIA Portal TIA Portal - Hardware configuration - PG/OP via PROFINET 9.5 TIA Portal - Hardware configuration - PG/OP via PROFINET Overview The CPU has a twisted pair interface integrated for PROFINET This interface allows you to program and remote control your CPU. n The PROFINET interface also gives you access to the internal web page that contains information about firmware version, connected I/O devices, current cycle times etc.
Configuration with TIA Portal VIPA System 300S TIA Portal - Hardware configuration - PG/OP via PROFINET 7. Confirm with [Assign IP configuration]. ð Directly after the assignment the PROFINET interface 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. Due to the system you may get a message that the IP address could not be assigned. This message can be ignored.
VIPA System 300S Configuration with TIA Portal TIA Portal - Setting VIPA specific CPU parameters Device overview: Module ... Slot ... Type PLC... 2 CPU ... MPI/DP interface 2 X1 MPI/DP interface PROFINET interface 2 X2 PROFINET interface DI... 4 DI... DO... 5 DO... DIO... 6 DIO... AI... 7 AI... AO... 8 AO... ... ... ... ... 9.
Configuration with TIA Portal VIPA System 300S TIA Portal - Setting VIPA specific CPU parameters Installation of the SPEEDBUS.GSD The GSD (Geräte-Stamm-Datei) is online available in the following language versions. Further language versions are available on inquires: Name Language SPEEDBUS.GSD 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: 1.
VIPA System 300S Configuration with TIA Portal TIA Portal - Setting VIPA specific CPU parameters Device overview Module ... Slot ... Type PLC... 2 CPU ... ... ... ... ... 3 DI... 4 DI... DO... 5 DO... DIO... 6 DIO... AI... 7 AI... AO... 8 AO... CP 343-1 9 CP 343-1 CP 342-5 10 CP 342-5 Thus, the VIPA components can be displayed, you have to deactivate the "Filter" of the hardware catalog. Connect VIPA_SPEEDbus 1. Switch in the Project area to Network view. 2.
Configuration with TIA Portal VIPA System 300S TIA Portal - Include VIPA library 4. Click at the slave system and open the ‘Device overview’ in the Project area. 5. Configure at slot 1 the VIPA CPU 315-4PN33 of the hardware catalog from VIPA_SPEEDbus. 6. By double clicking the placed CPU 315-4PN33 the properties dialog of the CPU is showed. Device overview Module ... Slot ... Type Slave ... 0 VIPA SPEEDbus 315-4PN33 1 315-4PN33 ... ...
VIPA System 300S Configuration with TIA Portal TIA Portal - Project transfer Open library and transfer blocks to project 1. Start the Siemens TIA Portal with your project. 2. Select the Project view. 3. Choose "Libraries" from the Task cards on the right side. 4. Click at "Global libraries". 5. Click at "Open global library". 6. Navigate to your directory and load the file VIPA_TIA.al11. 7.
Configuration with TIA Portal VIPA System 300S TIA Portal - Project transfer Transfer via Ethernet For transfer via Ethernet the CPU has the following interface: n 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". Please consider to use the same IP address data in your project for the CP 343-1. Transfer 1.
VIPA System 300S Configuration with TIA Portal TIA Portal - Project transfer Transfer CPU ® Memory card When a memory card has been installed, the write command stores the content of the RAM as S7PROG.WLD on the memory card. The write command can be found in the Siemens TIA Portal in the Task card "Online tools" in the command area at "Memory" as button [Copy RAM to ROM]. The MC LED blinks during the write access. When the LED expires, the write process is finished.
