Application about Communication

Transcription

1 Application about Communication Diagnostic Methods for PROFINET Network Components (PROFINET IO, SNMP, WBM) Volume 1: Diagnostics via S7 PROFINET CPUs Application with Code

2 Application Description Table of Contents Note The Application Examples are not binding and do not claim to be complete regarding the circuits shown, equipping and any eventuality. The Application Examples do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible for ensuring that the described products are correctly used. These Application Examples do not relieve you of the responsibility of safely and professionally using, installing, operating and servicing equipment. When using these Application Examples, you recognize that Siemens cannot be made liable for any damage/claims beyond the liability clause described. We reserve the right to make changes to these Application Examples at any time without prior notice. If there are any deviations between the recommendations provided in these Application Examples and other Siemens publications e.g. Catalogs then the contents of the other documents have priority. Warranty, liability and support We do not accept any liability for the information contained in this document. Any claims against us based on whatever legal reason resulting from the use of the examples, information, programs, engineering and performance data etc., described in this Application Example shall be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German Product Liability Act ( Produkthaftungsgesetz ), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract ( wesentliche Vertragspflichten ). However, claims arising from a breach of a condition which goes to the root of the contract shall be limited to the foreseeable damage which is intrinsic to the contract, unless caused by intent or gross negligence or based on mandatory liability for injury of life, body or health. The above provisions do not imply a change in the burden of proof to your detriment. Copyright 2007 Siemens A&D. It is not permissible to transfer or copy these Application Examples or excerpts of them without first having prior authorization from Siemens A&D in writing. For questions about this document please use the following address: mailto:csweb@ad.siemens.de V2.0 Issue 08/30/07 2/116

3 Application Description Table of Contents Foreword Objective of the application This application shows the different options of diagnosing a PROFINET network. The application is divided into two volumes. Volume 1 shows the PROFINET diagnostic capabilities using a PN CPU. In this case, the PROFINET controller is the actual CPU. Volume 2 is based on the first document and shows how these PROFINET diagnostic capabilities can be realized as a PROFINET controller via a CP. Note Volume 2 is available as a separate document on the download page of this document. Main contents of this application The following main points are described in this application: Integration and configuration of SCALANCE X-200 switches in STEP 7 Integration and configuration of ET 200S PNFO modules via fiber-optic cables Readout and evaluation of received diagnostics information with the aid of the error OBs and system error blocks Graphical representation of the network components on a WinCC flexible user interface and display of the current status with the aid of an SNMP client (SIMATIC NET SNMP OPC server) Display of the diagnostic events in the default diagnostics window of WinCC flexible (Report System Error) Demonstration of the configuration of the X-200 switches via Web-based Management (WBM) Demonstration and configuration of the extended PROFINET diagnostic function Mirroring of the data traffic of a port for the X-200 switches V2.0 Issue 08/30/07 3/116

4 Application Description Table of Contents Delimitation This application does not include a description of the SIMATIC STEP 7 engineering tool the WinCC flexible visualization software SNMP (Simple Network Management Protocol) PROFINET IO Basic knowledge of these topics is required. Document structure The documentation of this application is divided into the following main parts. Part Application Description Principles of Operation and Program Structures Structure, Configuration and Operation of the Application Appendix Description This part provides a general overview of the contents. You are informed on the used components (standard hardware and software components and the specially created user software). This part describes the detailed functional sequences of the involved hardware and software components, the solution structures and where useful the specific implementation of this application. It is required to read this part if you want to familiarize with the interaction of the solution components to use these components, e.g., as a basis for your own developments. This part takes you step by step through structure, important configuration steps, startup and operation of the application. This part of the document includes references for further information. Reference to Automation and Drives Service & Support This entry is from the internet application portal of Automation and Drives Service & Support. The link below takes you directly to the download page of this document. V2.0 Issue 08/30/07 4/116

5 Application Description Table of Contents Table of Contents Table of Contents... 5 Application Description Automation Problem Overview Requirements Automation Solution Overview of the overall solution Description of the core functionality Visualization for the application Required hardware and software components Alternative solutions Principles of Operation and Program Structures General Functional Mechanisms Industrial Ethernet and PROFINET IO basics OPC server basics SNMP basics WBM Web-based Management Functional Mechanisms of this Application Diagnostics via LED Hardware diagnostics in HW Config Topology Editor Evaluation of a diagnostic alarm Report System Error RALRM system function block Diagnostics via SNMP Diagnostics via signal contact Diagnostics via Web-based Management (WBM) Diagnostics via port mirroring Diagnostics via integrated web server of the S7 CPU Explanations of the Example Program Explanations of the STEP 7 program Modifications to the Example Program Modification to the STEP 7 project Modification in WinCC flexible Structure, Configuration and Operation of the Application Installation and Startup Hardware and software installation V2.0 Issue 08/30/07 5/116

6 Application Description Table of Contents 7.2 Application software installation Configuration Configuring Report System Error Configuring the SNMP OPC server Changing the SCALANCE device profiles Connection partner for topology Operation of the Application Error scenarios Link down of a communication port Failure of one of the two power supplies Demand of maintenance of a fiber-optic cable Removing/inserting a module Topology Editor Opening the web page of the modules Triggering a diagnostic alarm Appendix and Literature Literature Bibliographic references Internet links V2.0 Issue 08/30/07 6/116

7 Application Description 0BAutomation Problem 1 Automation Problem 1.1 Overview Introduction Application Description Aside from typical components such as CPUs, CPs, etc., the actual communications network with its components is becoming increasingly important as Industrial Ethernet advances to the field level of automation technology. Therefore, diagnostics of the actual communications network are indispensable. Overview of the automation problem The figure below provides an overview of the automation problem. Figure 1-1 Network management (NM) diagnostics PC / panel / Runtime (RT) / WBM HMI Higher-level network management Central WBM configuration Visualization of the network status PN controller Network components Lower-level cells with S7 controller Diagnostics of the network components Processing of diagnostic messages Detection of the individual events with a program V2.0 Issue 08/30/07 7/116

8 Application Description 0BAutomation Problem Description of the automation problem The automation problem is to monitor a PROFINET I/O system with different network components. The option of individual diagnostics of the components and of detailed diagnostics of the overall system is to be ensured. The focus is on the acquisition and representation of the diagnostics information. In addition, a cell is to be able to react independently by means of a program in the event of network errors. This can, for example, mean that, due to a missing network connection, specific program parts in a controller are no longer executed or that corresponding error messages are reported. V2.0 Issue 08/30/07 8/116

9 Application Description 0BAutomation Problem 1.2 Requirements Table 1-1 Configuration Diagnostics User software HMI Responsible level Requirements Lower-level cell Integration and configuration options of the network components as nodes in a PROFINET IO network in SIMATIC STEP7 HW Config. Higher-level NM Configuration of an HMI station and an SNMP OPC server for an SNMP OPC connection Configuration via Web-based Management (WBM) and storage on a C-PLUG (replaceable memory medium for the configuration data of the switch) Lower-level cell Evaluation of the PN IO diagnostic alarms of the PROFINET devices Individual diagnostics program in STEP 7 Evaluation of the SCALANCE X-2xx switch signal contact Display of the demand of maintenance for fiber-optic cables (POF diagnostics) Mirroring of the data traffic of a port to be monitored to a monitor port. Higher-level NM Display and configuration of the Report System Error messages on a PC with WinCC flexible Runtime Display of diagnostics information via SNMP OPC server on the PC with WinCC flexible RT Representation of a complete overview with the STEP 7 HW Config Topology Editor Lower-level cell Programming of the interrupt OBs (OB 82, OB 86) for evaluating the PROFINET IO diagnostic alarms Transmission of alarm messages for display on the HMI system ( Report System Error ) Higher-level NM Display of the alarm messages from the S7 CPU Graphical representation of the overall system Display of the statuses of the individual components (link down on the port, device failure, redundant power supply, etc.) V2.0 Issue 08/30/07 9/116

10 Application Description 1BAutomation Solution 2 Automation Solution 2.1 Overview of the overall solution Diagrammatic representation The following figure schematically shows the most important components of the solution: Figure 2-1 V2.0 Issue 08/30/07 10/116

11 Application Description 1BAutomation Solution Configuration The following network stations are connected to the SCALANCE X-208 switch via Industrial Ethernet: Port 1: CPU PN/DP via the integrated Ethernet interface Port 2: Visualization PC via an Ethernet network card Port 5: SCALANCE X202-2P IRT The following network stations are connected to the SCALANCE X202-2P IRT switch via Industrial Ethernet and plastic optical fibers: Port 1: Optionally, a PC for port mirroring Port 2: SCALANCE X208 Port 3: ET 200S PNFO via an IM PN FO interface module with integrated optical-fiber interface The second ET 200S PNFO is connected to the first ET 200S PNFO (port 2) on port 1 (integrated optical-fiber interface). The first ET 200S PNFO is equipped with a power module and a digital output module The second ET 200S PNFO is equipped with a power module and a digital input module The signal contacts of the SCALANCEs can optionally be connected to a digital input module of the S7-300 station. Functional assignment The overview in the following table shows which main functions are included in which hardware component. Table 2-1 Component Core function S7 CPU Evaluation of the signal contact Report system error Individual diagnostic alarm program SNMP agent PC station 1 SNMP client OPC server HMI station WinCC flexible RT with OPC client Message sink WBM station PC station 2 Recording of the network traffic SCALANCE modules SNMP agent Signal contact V2.0 Issue 08/30/07 11/116

12 Application Description 1BAutomation Solution Component Core function Triggering of diagnostic messages ET 200 S modules SNMP agent Triggering of diagnostic messages 2.2 Description of the core functionality Aside from the visual diagnostics which displays the current status via LED, the PROFINET devices (SCALANCE and ET 200S) offer the following diagnostic messages: PROFINET IO SNMP Signal contact (only SCALANCE modules) Diagnostic mechanisms When the PROFINET devices send a PROFINET IO diagnostic alarm to the CPU, this alarm is evaluated and processed in a corresponding interrupt OB. Via the Report System Error function, a system message is generated, sent to the HMI system and displayed in this system. Continuous polling ensures that the SNMP client permanently receives current network information, including SNMP diagnostics information from the SCALANCE and ET 200S modules. This information is made available by the OPC client, in this case the WinCC flexible RT HMI system, via the configured OPC variables and used for the display. Optionally, the signal contacts of the SCALANCE modules can be connected to corresponding digital inputs of the S7-300 controller. Via a corresponding optional digital output, an alarm light is controlled according to the switch status. V2.0 Issue 08/30/07 12/116

13 Application Description 1BAutomation Solution 2.3 Visualization for the application WinCC flexible user interface The figure below shows the Diagnostics screen for the plant: Figure 2-2 Table 2-2 No. Element Note 1. Name and IP address The IP address is determined from the SNMP information. of the network stations 2. Network stations The display is controlled by SNMP information; in case of an error or communication trouble, the station and the associated network line are displayed in red. 3. SCALANCE X modules When clicking this element, Web-based Management of the respective module is called. 4. HMI system When clicking this element, the message screen is displayed. 5. Status of the SCALANCE X modules 6. Exit button Exits Runtime. The display of the ports and of the power supply is controlled by SNMP information; in case of an error, the display changes from GREEN to RED, white fields are not used. V2.0 Issue 08/30/07 13/116

14 Application Description 1BAutomation Solution No. Element Note 7. Cell status This display is controlled via an SNMP variable that displays the overall error status of the SCALANCE X208 switch. The internal cell is connected to the controller via this switch. The cell status is thus closely connected with the overall status of the SCALANCE X208 switch. Message window The currently pending messages, which the HMI system receives from the CPU, are displayed in a message window. Figure 2-3 HW Config In the HW Config online view, all modules affected by the diagnostic alarm are provided with a diagnostics symbol. Figure 2-4 V2.0 Issue 08/30/07 14/116

15 Application Description 1BAutomation Solution Module Information Module Information provides detailed diagnostics information. Figure 2-5 Web-based Management Clicking a SCALANCE module in the Diagnostics screen of the plant opens the default browser, e.g. Internet Explorer, with the IP address of the SCALANCE module. This starts the access to the SCALANCE module via Web-based Management. V2.0 Issue 08/30/07 15/116

16 Application Description 1BAutomation Solution Topology Figure 2-6 The PROFINET IO Topology Editor displays the failure of a port and / or the loss of a component by new colors and diagnostics symbols. Summary The table below shows the diagnosable errors and the corresponding visualization user interfaces: Table 2-3 Visualization user interface Diagnosable error Diagnostics screen in WinCC flexible RT SNMP diagnostics information Message window in WinCC flexible RT Report system error HW Config Diagnostic alarms Module Information Diagnostic message in plain text Web-based Management Status information Port status Topology Editor Diagnostic alarm Current interconnections V2.0 Issue 08/30/07 16/116

17 Application Description 1BAutomation Solution 2.4 Required hardware and software components Hardware components Table 2-4 Component No. MLFB / order number Note PS 307 5A 1 6ES EA00-0AA0 Alternatively, another power supply can also be used. CPU PN/DP 1 6ES EL00-0AB0 Alternatively, another PROFINET CPU can also be used. Micro Memory Card 1 6ES LL11-0AA0 At least 2MB for S7 CPU Micro Memory Card 2 6ES LF11-0AA0 At least 64KB for ET200 S PNFO SM322 digital output module 1 6ES BH01-0AA0 DO 16x24VDC/0.5A SCALANCE X GK BA10-2AA3 Firmware version 2.1 or higher SCALANCE X202-2P IRT 1 6GK BH00-2BA3 Firmware version 2.1 or higher IM151-3 PN FO 2 6ES BB22-0AB0 Firmware version 5.0 or higher PM-E 24VDC 2 6ES CA01-0AA0 Terminal module for 2 6ES CD20-0AA0 power module DI HF digital electronic 1 6ES BD01-0AB0 Unit pack of 5 module DO digital electronic module 1 6ES BD01-0AA0 Unit pack of 5 Terminal module for electronic modules 2 6ES CB20-0AA0 Unit pack of 5 Programming unit (PU) or PC with Ethernet network card, 100Mbps full duplex 2 Second PC only if you want to test port mirroring. DIN rail 1 E.g. 6ES AE80- Length 480mm 0AA0 Standard 35mm DIN rail 1 6ES MA11 E.g., length 483mm V2.0 Issue 08/30/07 17/116

18 Application Description 1BAutomation Solution Ethernet connecting cables Table 2-5 Component No. MLFB / order number Note IE FC Standard Cable GP 2x2 1 6XV AH10 Minimum order quantity: 20m IE FC RJ45 Plug GK BB10-2AA0 IE Stripping Tool 1 6GK GA00 Stripping tool for Ethernet cable Fiber-optic cables Table 2-6 Component No. MLFB / order number Note POF Standard Cable GP 980/ XV A Order quantity: Approx. 3m IE SC RJ POF Plug 1 6GK MB00-0AC0 20 per package IE Termination Kit SC RJ POF Plug Standard software components Table GK ML00-0AA0 Termination kit for POF SC RJ connectors. Component No. MLFB / order number Note SIMATIC STEP 7 V5.4 SP 2 1 6ES7810-5CC10-0YC5 Or higher SIMATIC NET SOFTNET S7 LEAN 2006 SIMATIC NET IE SNMP OPC SERVER BASIC/2006 SIMATIC WinCC flexible 2005 Advanced SP1 HF7 1 6GK1704-1LW64-3AA0 Maximum of 8 connections The SIMATIC NET software CD is included in the delivery. 1 6GK1706-1NW64-3AA0 1 6AV6613-0AA01-1CA5 Network sniffer 1 E.g. Wireshark Example files and projects The following list includes all files and projects that are used in this example. Table 2-8 Component _DIAG_NETWORK_CODE_BAND1_v20.zip _DIAG_NETWORK_DOKU_BAND1_v20_e.pdf Note This zip file contains the STEP 7 project with integrated HMI station. This document. V2.0 Issue 08/30/07 18/116

19 Application Description 1BAutomation Solution 2.5 Alternative solutions SCALANCE X208 Alternatively to the SCALANCE X208 switch, a SCALANCE X206-1 or a SCALANCE X204-2 can be used. The diagnostics of the optical ports are identical to the diagnostics of the electrical ports. SCALANCE X202-2P IRT Alternatively to the SCALANCE X202-2P IRT Industrial Ethernet switch, a SCALANCE X201-3P IRT can be used. S7 station Alternatively to the CPU PN/DP, a CPU PN/DP or a CPU PN/DP can be used (firmware 2.5 or higher). An S7-400 station can also be used. As a CPU, a CPU PN/DP, CPU PN/DP or CPU 416F-3 PN/DP can be used (firmware 5.0 or higher). Note When changing the specified modules, the hardware configuration in STEP 7 has to be adjusted to the new modules. PROFINET controller Alternatively to a PROFINET CPU as a PROFINET controller, a communications processor (CP) can also be used provided that the CP can perform the function of the PROFINET controller. Note The example with a CP as a PROFINET controller is described in Volume 2 that is available as a separate document on the download page of this document. V2.0 Issue 08/30/07 19/116

20 Principles of Operation and Program Structures 2BGeneral Functional Mechanisms Principles of Operation and Program Structures 3 General Functional Mechanisms 3.1 Industrial Ethernet and PROFINET IO basics Industrial Ethernet Industrial Ethernet is a network consisting of terminals and network components (switches, routers) that are connected via twisted pair copper cables or fiber-optic cables with a transmission rate of 100 Mbps (Fast Ethernet) or more. Unlike PROFIBUS, the network consists of point-to-point connections that are connected to one another via active network components. Since separate lines are available for sending and receiving, the network can be operated in full duplex mode without causing collisions of the data packets, i.e. simultaneous receiving and sending with 100Mbps each is possible. In contrast to shared media as e.g. used by PROFIBUS or an Ethernet network with repeaters or hubs, this switched media principle is the present state of the art. Switching Switching uses the address information in the data packet to directly forward/switch data packets from the input port to the corresponding output port. Switches allow, as it were, a direct switching method. The basic functions of switches are listed in the following: Connection of collision domains / subnetworks: Since repeaters / hubs operate at the physical level, their use is limited to the length of a collision domain. Switches connect collision domains. Consequently, their use is not restricted to the maximum length of a repeater network. Rather very large networks with lengths of 150km and more can be set up using switches. Load separation: Filtering the data traffic using the Ethernet (mac) addresses ensures that local data traffic remains local. Unlike repeaters, which distribute the data unfiltered to all ports / network stations, switches allow a direct connection. Only data to nodes of another subnetwork are transported from the input port to the corresponding output port of the switch. To ensure this, the switch sets up one table of the Ethernet (mac) addresses per port (learning table) in autodidactic mode. Limiting the error spread to the affected subnetwork: By checking the validity of a data packet using the checksum contained in each data packet, the switch ensures that the transport of erroneous data packets is stopped. Collisions in a network segment are also not forwarded to other segments. Parallel communication: One property of switches is that they process several data packets between different network segments or nodes V2.0 Issue 08/30/07 20/116

21 Principles of Operation and Program Structures 2BGeneral Functional Mechanisms Figure 3-1 simultaneously. Depending on the number of its ports, the switch temporarily and dynamically establishes several connections between different pairs of network segments/terminals. This ensures that an enormous increase in the data throughput in the network and thus a considerable increase in network efficiency can be achieved. Data traffic V2.0 Issue 08/30/07 21/116

22 Principles of Operation and Program Structures 2BGeneral Functional Mechanisms Table 3-1: Switched LAN Each individual segment features the full performance / data rate Simultaneous data traffic in several segments; several message frames Filtering: Local data traffic remains local; only selected data packets exceed the segment limits Shared LAN All nodes of the network share the network performance / data rate All data packets pass through all segments Only one message frame in the network at a time Collisions reduce the efficiency of the network to approximately 40% (if there is heavy data traffic). PROFINET and PROFINET IO At production management level, Industrial Ethernet has established itself as a communications standard. But communication at field and cell level requires much more, e.g. real-time capability, integration of distributed field devices, industry-standard installation technology, etc. PROFINET, the open Industrial Ethernet standard of the PROFIBUS user organization for automation, meets these requirements and thus ensures integrated communication from the office world to the field level. Within the scope of PROFINET, the interfacing of the distributed I/O is realized by PROFINET IO. Based on a real-time driver, PROFINET IO defines the communication with the connected distributed I/O devices. PROFINET IO describes the entire data exchange between controllers (similar to the PROFIBUS DP master) and devices (similar to the PROFIBUS DP slaves), as well as configuration and diagnostics. Configuring a PROFINET IO system in STEP 7 is almost identical to the configuration of PROFIBUS. The interfaces known from PROFIBUS are available in PROFINET IO basically without changes: The cyclic data can be transferred and received as usual. The alarm processing allows a simple interface for the different events. The acyclic jobs are mapped via read/write services (here Record Data ). The configuration enables a simple model for small, compact devices but also allows various options of structuring for more powerful devices. PROFINET IO in this application In this application, a CPU PN/DP was used as a PROFINET IO controller. The used PROFINET IO devices are the two ET200 S PNFO and SCALANCE X202-2P IRT representing the distributed I/O within the automation cell and the SCALANCE-X208, which, with its diagnostic capabilities, is the focal point of this application. V2.0 Issue 08/30/07 22/116

23 Principles of Operation and Program Structures 2BGeneral Functional Mechanisms 3.2 OPC server basics In recent years, the OPC Foundation (an interest club of well-known manufacturers for the definition of standard interfaces) has defined a large number of software interfaces to standardize the information flow from the process level to the management level. According to the different requirements within an industrial application, four different OPC specifications have been developed: Data Access (DA) describes the access to process data, Alarm&Events (A&E) describes an interface for event-based information including acknowledgement, Historical Data Access (HDA) describes functions for archived data, Data exchange (DX) defines a server to server cross-communication. This example uses exclusively the OPC Data Access interface. The detailed documentation is available on the SIMATIC NET Docu CD. For further information, please refer to /8/ What is OPC? OPC is a manufacturer-independent software interface that enables data exchange between hardware and software also of different manufacturers. Before OPC, it was very complicated to control the hardware of different manufacturers using software applications. A large number of different systems and protocols existed. Users had to use special software for accessing the specific interfaces and drivers for each manufacturer and each protocol. Due to this fact, the user programs depended on manufacturer, protocol or system. As a standardized software interface independent of manufacturer, OPC based on COM or DCOM has revolutionized the data exchange in automation technology. The figure below provides an overview of the performance capability and flexibility of OPC. V2.0 Issue 08/30/07 23/116

24 Principles of Operation and Program Structures 2BGeneral Functional Mechanisms Figure 3-2 OPC interface The OPC interface is part of the software that runs on a PC as a platform for operator control and monitoring systems or other applications. As an industry standard, OPC defines the exchange of information for different applications in the industrial environment. The applications of the OPC interface are based on the client-server model. One component provides its services to other components as a server (e.g. SNMP OPC server) via interfaces. Another component utilizes the services as a client (e.g. WinCC flexible). An application can determine which OPC servers are installed in a system. It can address one or more of these servers and check which services are provided by the server. Since several different OPC clients can simultaneously access the same OPC server, the same data source can be used for any OPC-compliant application. OPC server Manufacturers of modules providing process data (communications systems, measuring instruments, etc.) provide an OPC server for their module which connects it to the corresponding data source. Aside from services, the OPC server provides information from any data source to the OPC client; these sources can be hardware-driven data sources or software components. Each OPC server has a unique name for identification. V2.0 Issue 08/30/07 24/116

25 Principles of Operation and Program Structures 2BGeneral Functional Mechanisms SNMP OPC server The SNMP OPC server enables the user to monitor SNMP-capable network components and IP devices such as the SCALANCE X208 switch also in plants. The SNMP OPC server is used as a compiler from SNMP to the OPC interface of the HMI system. Read and partial write access to the respective device information is possible. This enables diagnostics of individual devices up to the complete network infrastructure and a control (only possible during write access) of device properties, e.g. activating and deactivating individual ports. 3.3 SNMP basics What is SNMP? SNMP Simple Network Management Protocol is a UDP-based protocol that was specified specifically for the administration of data networks and has established itself also as a de facto standard for TCP/IP devices in the meantime. The individual nodes in the network network components or terminals feature an SNMP agent that provides information in a structured form. This structure is referred to as MIB Management Information Base. In the network node, the agent is usually realized as a firmware functionality. The figure below shows the data flow for SNMP. Figure 3-3 Manager Cyclic data communication controlled by manager Polling MIB Trap MIB Event-controlled by agent Agent V2.0 Issue 08/30/07 25/116

26 Principles of Operation and Program Structures 2BGeneral Functional Mechanisms A network management solution based on SNMP operates according to the client-server model. The management station (SNMP client) can poll information from the agents to be controlled that act as servers. The MIB information is cyclically called from the management station and visualized if required. In addition, the nodes are also capable of reporting specific statuses to the network management station via traps without explicit requests. SNMP enables not only the monitoring of the nodes but also instructions for controlling the devices. These instructions include activating or deactivating a port on a network component. The communication between agents and network management station is performed in the background and loads the network only insignificantly. Management Information Base MIB An MIB (Management Information Base) is a standardized data structure consisting of different SNMP variables that are described by a language independent of the target system. The cross-vendor standardization of the MIBs and the access mechanisms enable the user to monitor and control also a heterogeneous network with components of different manufacturers. If component-specific, non-standardized data are required for network monitoring, these data can be described by the manufacturers in private MIBs. Figure Standardized data System information such as network statistics, counters, tables 2 3 Extended standardized data E.g., data on the network load (TMON) for switches Device-specific data E.g., status of the redundant power supply 4 Bridge MIB E.g., topological view view by means of an office tool V2.0 Issue 08/30/07 26/116

27 Principles of Operation and Program Structures 2BGeneral Functional Mechanisms Figure 3-5 An MIB describes the entity of all SNMP objects (SNMP variables) that are located in the network. The MIB information structure is similar to the Windows registry structure. The figure below shows the standard MIB (MIB-2) structure: The OID (Object Identifier) describes the address of the MIB object. The address of standardized MIB objects is preset. Private MIB objects are always stored in the Enterprise directory. The manufacturer is responsible for the addresses in this structure. It is only required that the manufacturer number is registered. Device profiles A device profile describes the scope of the variables of a device, e.g. the SCALANCE X208 switch, that are displayed on the OPC server. Only variables included in the device profile can be integrated into an application. V2.0 Issue 08/30/07 27/116

28 Principles of Operation and Program Structures 2BGeneral Functional Mechanisms The SNMP OPC server additionally includes an MIB compiler that is used to adapt existing device profiles or to create new device profiles. This is done by entering the required SNMP variables from the public and, if necessary, private MIBs in the profile. SIMATIC devices featuring special SNMP agents, e.g. switches (SCALANCE X, SCALANCE W), the CP1616, CP443-1 Industrial Ethernet communications processors, etc., are already included in the STEP 7 directory with their device profiles. For IP-capable devices without individual SNMP agent, the SNMP manager can at least determine the IP address and the status of the connection to this network station using the common TCP/IP ping status check and make this information available to the SNMP OPC server. Note The prepared device profiles are located in the following directory: <STEP 7InstallationDirectory>/S7DATA/snmp/profile 3.4 WBM Web-based Management Web-based Management enables the parameterization and monitoring of network nodes network components such as the SCALANCE modules or terminals via standard internet browsers such as Firefox or Internet Explorer. Figure 3-6 Office WAN WAN Home Process Router V2.0 Issue 08/30/07 28/116

29 Principles of Operation and Program Structures 2BGeneral Functional Mechanisms Via a browser, HTML pages containing the desired information are called in the nodes. The corresponding module dynamically supplies these HTML pages with information. This requires only the IP address of the SCALANCE module and a password to be able to perform a read and/or write access to the information as a user or administrator. Note In Web-based Management, no proxy server must be set in the connection properties of the internet browser. V2.0 Issue 08/30/07 29/116

30 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application 4 Functional Mechanisms of this Application Note In this application, network components mean PROFINET IO devices! 4.1 Diagnostics via LED Note Most modules of the SIMATIC family feature an LED display for status and error display on the housing. Depending on status and error, one LED or several LEDs light up. The meaning of the individual LEDs or their combination differs from module to module. For information on the meaning of the LED display, please refer to the module manual. 4.2 Hardware diagnostics in HW Config Aside from the visual diagnostics via LED, STEP 7 provides the Online view. If an error or a fault occurs in a module and if diagnostics information is available, the status of the faulty module is displayed with the aid of diagnostics symbols (menu: Station -> Open Station Online). Diagnostics symbols Diagnostics symbols facilitate troubleshooting in the event of a fault. If there is no module fault, only the module type symbol is displayed. If, however, a fault has occurred, the module type symbol is displayed with an additional diagnostics symbol. V2.0 Issue 08/30/07 30/116

31 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application The table below shows the meaning of the diagnostics symbols: Table 4-1 Symbol Meaning Diagnostics symbols for modules Target/actual deviation from the configuration: The configured module does not exist or another module type has been inserted. Error: Module faulted. Possible causes: Detection of a diagnostic alarm, an I/O access error or an error LED. Diagnostics are not possible since there is no online connection or since the CPU does not provide diagnostics information. Startup Diagnostics symbols for modes Stop Stop; triggered by STOP mode of another CPU in multicomputing mode Run Hold Diagnostics symbols for maintenance information Maintenance request Demand of maintenance Diagnostics symbols are displayed in the project window in the Online view and, after calling the Hardware Diagnostics function, in the Quick or Diagnostics View. Quick View The Quick View only displays components that are faulty or that have reported an error. The following information is displayed: Data on the online connection to the CPU Diagnostics symbol for the CPU and modules for which the CPU has detected a fault. Module type and module address (rack, slot, PN IO system with station number) V2.0 Issue 08/30/07 31/116

32 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Figure 4-1 Diagnostics View Unlike Quick View, Diagnostics View displays the entire station configuration that can be accessed online. The following information is displayed: Configuration of the racks Diagnostics symbols for all configured modules. They indicate the status of the corresponding module and for CPU modules additionally the mode. Module type, order number and address, comments on the configuration V2.0 Issue 08/30/07 32/116

33 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Figure 4-2 Diagnostics information The diagnostics information available for a faulty module can be read out using the Module Information function. The following table lists the most important information provided by Module Information: Table 4-2 Information function General Diagnostic buffer Diagnostic alarm Memory Information Identification data of the selected module (type, order number, revision level, status, slot in the rack) Overview of the events in the diagnostic buffer and detailed information on the selected event. Diagnostics data of the selected module Memory configuration, current main memory utilization, load memory and retentive memory, data of the selected CPU or M7 FM. V2.0 Issue 08/30/07 33/116

34 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Figure 4-3 Schematic diagram Figure 4-4 SIMATIC MANAGER Project S7 program Station Module Accessible nodes Accessible nodes CPU 319 CP343-1 CPU 319 CP343-1 Hardware Diagnostics command or online view Quick View CPU + faulty modules Diagnostics View Module Information V2.0 Issue 08/30/07 34/116

35 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application 4.3 Topology Editor With version V5.4 SP 2, a display enabling a topological view of components with extended PROFINET diagnostics has been integrated into STEP 7. This Topology Editor enables an overview of all ports of the configured Ethernet modules in the project. an interconnection table of the ports with the corresponding partner port. a graphical overview screen with all STEP 7 devices and modules and their ports. The interconnections of the ports are displayed as a connecting line. an automatic detection of all nodes and their port interconnections. integrated diagnostics. HW Config vs. Topology Editor The STEP 7 hardware configuration symbolically attaches all components that belong to a network to the corresponding system (PROFINET IO system or DP master system). It does not show the actual connection among the nodes. Figure 4-5 The actual connection among the nodes with all port interconnections is made visible by the Topology Editor. This enables a more exact system planning and configuration. V2.0 Issue 08/30/07 35/116

36 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Figure 4-6 PROFINET topology requirements To operate the PROFINET modules in the environment of the topology, the device must meet the following requirements: SNMP = Simple Network Management Protocol LLDP = Link Layer Discovery Protocol PDEV = Physical Device DCP = Discovery and Configuration Protocol Principle of operation of LLDP LLDP is a protocol that allows to discover the next neighbor. It operates with its own Management Information Base (MIB) in which the data on the local agent and the discovered neighboring agents are stored and used for configuring LLDP. To this end each device sends LLDP data packets to all neighboring devices that are connected to its physical interfaces and sets up the local LLDP MIB with the data from the received packets. Each connection point in a topology is unique and is uniquely identified as a Media Service Access Point (MSAP). An MSAP consists of a unique chassis ID and a port ID that is unique at least for this device. The network management system (STEP 7, SNMP client ) reads out the LLDP MIB from all devices via SNMP. This unique assignment of the MSAPs enables the network management system to determine the network topology. V2.0 Issue 08/30/07 36/116

37 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Figure 4-7 STEP 7 network management system Readout of the LLDP MIB with the aid of SNMP and display of the topology LLDP MIB LLDP MIB Process/subnetwork LLDP MIB LLDP MIB LLDP MIB Independent LLDP exchange between the network nodes LLDP data packets Unanswered LLDP data packets since the partner is not a PROFINET device Topology Editor structure The Topology Editor consists of the following three tabs: Table view tab Graphic view tab Offline/online comparison tab Table view tab This tab shows the PROFINET modules and their ports in a table. Interconnections can be created or edited manually. The Online button can be used to check whether the configured devices and interconnections exist in the connected system; the status of the V2.0 Issue 08/30/07 37/116

38 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Figure 4-8 devices can also be checked. In addition, the Module Information can be called for each module. The columns have the following meaning: Table 4-3 Column Meaning Port Display of all configured modules with their ports Status Connection status Symbol Meaning Bedeu Status OK Status OK Status information not available Statusinformation Device in stop Gerät in Stopp Partner port Device faulty Maintenance request Demand of maintenance Communication error Connection partner via this port Gerät gestört Wartungsanforder Wartungsbedarf Kommunikationsfe V2.0 Issue 08/30/07 38/116

39 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Column Attenuation value in db Comment Meaning Attenuation value of the POF cable Comment Note To display the interconnections of the ports among one another, it is either required to apply the interconnections that have been determined online to the assignment table of the Topology Editor ( Offline/Online View tab) or to manually enter the port interconnections in the hardware configuration (Port Properties Topology). Graphic view tab This tab displays the PROFINET modules and their ports in a graphical representation. The interconnections of the ports are indicated by connecting lines. This tab also comprises two modes: Offline mode displays the current STEP 7 project. The following functions are available in this mode: Creating, deleting and changing the port interconnections Editing the properties of devices, modules and port interconnections in the corresponding dialog boxes Adding and deleting passive components (media converters and switches of the SCALANCE X-100 and SCALANCE W series) Changing the view (moving components, enlarging the view, etc.) Inserting a background image The Online view is opened by selecting the Online button. In this view, the STEP 7 devices of the connected system are displayed that have been detected after a lifelist broadcast call and assigned to the project devices. Additional detected devices are listed. The following functions are available: Diagnostics of modules, ports and cables V2.0 Issue 08/30/07 39/116

40 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Figure 4-9 Offline/online comparison tab In this tab, the devices of the STEP 7 project (Offline view) can be compared to the actually connected devices (Online view). The interconnection data of the ports of PROFINET-capable devices can be applied to the STEP 7 project. The tab is divided into two columns: The Configured topology (offline) list is shown on the left of the window and the Detected topology (online) list is displayed on the right. LLDP is used for the detection of the actual topology. Device names, module types, port number and order number are if possible used to automatically assign between configured and detected topology. If it is not possible to uniquely detect a partner port, a manual assignment of this port is possible. The interconnections of assigned online devices can be applied to the Topology Editor assignment table and the STEP 7 project. V2.0 Issue 08/30/07 40/116

41 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Figure 4-10 Table 4-4 Entry offline The colors of the lines indicate the comparison result. The table below shows the meaning of the colors: Entry online Meaning Green Green A configured module and a module that has been detected online could be assigned to one another (identical module type, identical device name, identical order number, identical number of ports, identical port interconnection) Yellow Yellow A configured module and a module that has been detected online could be assigned to one another (identical module type, identical device name, identical order number, identical number of ports), but there are differences in the interconnection Orange - A configured module could not be assigned to a detected module; the corresponding list section of the Online topology is empty. - Orange A detected module could not be assigned to a configured module. White White A configured module and a module that has been detected online could be assigned to one another. However, these modules do not include topological information. - White A module was detected that does not correspond to a configured module and does not include topological information. V2.0 Issue 08/30/07 41/116

42 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application 4.4 Evaluation of a diagnostic alarm If a channel error occurs, e.g. link down of a port, the faulty component generates a diagnostic alarm to the IO controller, in this application an S7 CPU. This alarm calls a corresponding program routine in the user program of the CPU (error OB) to be able to handle the error accordingly. With the aid of the SFB 54 system function block, further information can be requested from the component triggering the alarm, e.g. channel number, incoming or outgoing alarm, etc. Activation of error OB 82 To ensure that the error OB 82 is called in the event of a diagnostic alarm, it has to be activated in HW Config: Figure 4-11 V2.0 Issue 08/30/07 42/116

43 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Report System Error Messages from the CPU error memory are automatically displayed in plain text on HMI clients with the Report System Error function. The required program is automatically generated by STEP 7 and the associated blocks are called in the error OBs. Components The following SIMATIC components support the Report System Error function: S7-400, S7-300, WinAC HMI devices PG/ STEP 7 Note Further information on the Report System Error function is available in the STEP 7 help. Schematic diagram The figure below schematically shows the way of a PROFINET IO diagnostic alarm from a PROFINET device via the controller to the HMI system. V2.0 Issue 08/30/07 43/116

44 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Figure 4-12 PG/PC WinCC flexible RT Report System Error (Alarm S) IE/PN S7 station S7 program SCALANCE X208 IE/PN OB1/82/83/86 IE/PN PROFINET IO diagnostic alarm SCALANCE X202 IE/PN POF ET200 S POF ET200 S POF V2.0 Issue 08/30/07 44/116

45 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Functional sequence Table 4-5 The following step table shows the sequence of Report System Error : Action Note 1. A diagnostic alarm occurs. E.g., by removing/inserting a module or link down on a port. 2. The user program is interrupted and a corresponding error OB is called. All necessary information is stored in the error memory. 3. The Report System Error program in the error OBs reads the error information from the error memory. 4. This information is sent to the logged on clients (HMI). 5. The clients process this information and convert it to a plain-text message. Note This information includes error code, time stamp, source of error Via the ALARM S interface The plain-text message can then, for example, be output in message windows The display of Report System Error on an HMI client requires that the WinCC flexible project is integrated into the STEP 7 project. The STEP 7 project directory includes a database file with an assignment of the error information to the corresponding plain-text message. The integrated WinCC flexible project can access this file. Configuration of Report System Error Table 4-6 Action Note 1. Configuration in the CPU hardware configuration 2. Automatic generation of the blocks Diagnostics FB, including instance DB, error OBs, user FC 3. Loading the generated and changed blocks to the CPU Note For step-by-step instructions for configuring Report System Error, please refer to chapter 8.1. V2.0 Issue 08/30/07 45/116

46 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Display on the HMI system On the HMI system (WinCC flexible RT), all pending messages are displayed in an automatically displayed message window. Figure 4-13 Figure 4-14 In addition, all incoming and outgoing messages are stored and can be displayed in an additional message screen RALRM system function block If an alarm occurs in a PROFINET component, the associated error OB is called. The RALRM (SFB54) system function block enables the user to read out further information from the I/O module triggering the alarm or from a PROFINET device. This additional information allows an error analysis that is more exact and an individual reaction to the error. Schematic diagram The figure below schematically shows the way of a PROFINET IO diagnostic alarm from a PROFINET device to the controller. An error OB is called and the error analysis is started. V2.0 Issue 08/30/07 46/116

47 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Figure 4-15 PG/PC WinCC flexible RT IE/PN S7 station S7 program OB1/82/83/86 RALRM block IE/PN SCALANCE X208 IE/PN PROFINET IO diagnostic alarm SCALANCE X202 IE/PN POF ET200 S POF ET200 S POF V2.0 Issue 08/30/07 47/116

48 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Functional sequence The following step table shows the sequence of the error analysis: Table 4-7 Action Note 1. A diagnostic alarm occurs. E.g., by removing/inserting a module or link down on a port. 2. The user program is interrupted and a corresponding error OB is called. All necessary information is stored in the error memory. 3. With the aid of SFB54, the program requests further information from the device triggering the alarm. 4. This more detailed information can be used to program an error analysis that is more exact and an individual reaction to the error. This information includes error code, time stamp, source of error This information includes channel number, slot number, alarm type, incoming / outgoing alarm Call parameters SFB54 RALRM provides all information that has been read out as output parameters. The following parameters are used for the call: Figure 4-16 The EN and EN0 parameters are only visible in the Graphic view. V2.0 Issue 08/30/07 48/116

49 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Table 4-8 The meanings of the individual parameters are listed in the following table: Parameter Type Meaning MODE INT Mode F_ID DWORD Logical address of the component triggering the alarm In this application: The diagnostic address MLEN INT Maximum length of the alarm information to be received TINFO ANY Destination area for OB start information and management information AINFO ANY Destination area for header information and additional alarm information NEW BOOL A new alarm has been received. STATUS DWORD SFB error code ID DWORD Logical address of the component triggering the alarm In this application: Diagnostic address LEN INT Length of the received alarm information Note Examples of calling the system function blocks in this application are listed in chapter 5.1. V2.0 Issue 08/30/07 49/116

50 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application 4.5 Diagnostics via SNMP Schematic diagram Figure 4-17 The figure below schematically describes how the SNMP diagnostics information is transferred from the components to the HMI system via the SNMP OPC server. PG/PC WinCC flexible RT OPC client OPC variable SNMP OPC server S7 station IE/PN SNMP client IE/PN SCALANCE X208 IE/PN MIB SNMP agent PROFINET IO diagnostic alarm SCALANCE X202 IE/PN POF MIB SNMP agent ET200 S ET200 S POF POF MIB SNMP agent MIB SNMP agent V2.0 Issue 08/30/07 50/116

51 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application SNMP diagnostics information When configuring the SNMP OPC server, all SNMP data from the MIBs of the SNMP-capable devices are defined that are to be mapped to OPC variables. This information is automatically polled by the SNMP OPC server by regular polling of the SNMP agents of the accessible devices. OPC variable The SNMP OPC server provides the data received as described above to the OPC client in this case the HMI system (WinCC flexible RT) via the OPC variables. If the connection to one or several devices is interrupted, e.g. by link down of the HMI port on the SCALANCE X208 switch, the OPC variables that are now no longer supplied are marked as invalid. However, the OPC server permanently provides variables on the status of the connection. In the figure below, the first two variables (marked in green) indicate the status of the connection to the SCALANCE X208 switch, the third variable (marked in red) is currently invalid. Figure 4-18 Display on the HMI system In the display image of WinCC flexible RT, the OPC variables were used in both the schematic representation of the SCALANCE modules and in the cell overview. V2.0 Issue 08/30/07 51/116

52 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Figure 4-19 SNMP variables for the schematic representation Table 4-9 The variables of the X208 Port x or X202 Port x type and the X208 Power Supply or X202 Power Supply variable are used for switching over between green and red for link down of the port or the power supply status. No. Name Data type OPC item ID 1. X208 Port 1 Long SNMP:[x-208]ifOperStatus.1 2. X208 Port 2 Long SNMP:[x-208]ifOperStatus.2 3. X208 Port 3 Long SNMP:[x-208]ifOperStatus.3 4. X208 Port 4 Long SNMP:[x-208]ifOperStatus.4 5. X208 Port 5 Long SNMP:[x-208]ifOperStatus.5 6. X208 Port 6 Long SNMP:[x-208]ifOperStatus.6 7. X208 Port 7 Long SNMP:[x-208]ifOperStatus.7 8. X208 Port 8 Long SNMP:[x-208]ifOperStatus.8 9. X208 Power Supply State Long SNMP:[x-208]snX200PowerSupplyState 10. X202 Port 1 Long SNMP:[x-202]ifOperStatus.1 V2.0 Issue 08/30/07 52/116

53 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application No. Name Data type OPC item ID 11. X202 Port 2 Long SNMP:[x-202]ifOperStatus X202 Port 3 Long SNMP:[x-202]ifOperStatus X202 Port 4 Long SNMP:[x-202]ifOperStatus X202 Power Supply State Long SNMP:[x-202]snX200PowerSupplyState IP addresses of the network stations Table 4-10 The IP addresses of the network stations are displayed via the following variables. No. Name Data type OPC item ID 15. CPU319 IP-Address String SNMP:[PN-IO]&ipaddress() 16. HMI IP-Address String SNMP:[IE general]&ipaddress() 17. SCALANCE X208 IP-Address String SNMP:[x-208]&ipaddress() 18. SCALANCE X202 IP-Address String SNMP:[x-202]&ipaddress() 19. ET200S_2 IP-Address String SNMP:[IM151-3PNFOV50-1]&ipaddress() 20. ET200S_1 IP-Address String SNMP:[IM151-3PNFOV50]&ipaddress() Device / connection status The variables listed in the following table control whether the respective network station and the corresponding connection are displayed as interrupted, thus red. Table 4-11 No. Name Data type OPC item ID 21. SCALANCE X208 SNMP State Byte SNMP:[x-208]&statepathval() 22. CPU319 SNMP State Byte SNMP:[PN-IO]&statepathval() 23. SCALANCE X202 SNMP State Byte SNMP:[x-202]&statepathval() 24. ET200S_1 SNMP State Byte SNMP:[IM151-3PNFOV50]&statepathval() 25. ET200S_2 SNMP State Byte SNMP:[IM151-3PNFOV50-1]&statepathval() Overall cell status The overall error status of the SCALANCE X208 switch provides information on both the monitored ports and the power supply status; it is therefore particularly suitable for controlling the overall status of the cell. Table 4-12 No. Name Data type OPC item ID 26. Status_X208 Long SNMP:[x-208]snX200FaultState V2.0 Issue 08/30/07 53/116

54 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application 4.6 Diagnostics via signal contact The signal contacts of the SCALANCE modules can be directly connected to a digital input of the S7-300 station. Since it is wire break-safe, i.e. high level means error-free, the value read into the CPU has to be invertedly connected to a digital output. The output can be directly wired to an alarm light. Figure 4-20 Alarm light SCALANCE X208 SCALANCE X202 S7 station PS CPU DI DO Wiring of the signal contact 4.7 Diagnostics via Web-based Management (WBM) All switches of the SCALANCE X-200/ X-300/ X-400 family can be configured and diagnosed via Web-based Management. Web-based Management displays the current status of the SCALANCE module in several sections. The following screen shots were taken from WBM of the SCALANCE X208 switch as examples. Simulation of the light-emitting diodes Independently of the current position in the menu tree, the top part of the window always displays an image of the SCALANCE LED statuses. The following excerpt shows the status of the light-emitting diodes in the event of a link down on port 1. V2.0 Issue 08/30/07 54/116

55 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Figure 4-21 X208 Status screen form Figure 4-22 This screen form provides a verbal description of the current SCALANCE X208 status. Switch Ports Status screen form Among other things, this screen form describes the link status of the SCALANCE X208 ports. The following excerpt shows the status of the light-emitting diodes in the event of a link down on port 5. Figure 4-23 Statistics screen form The X-200 IE switches count the number of sent and received message frames for each port. Overview tables are available that list V2.0 Issue 08/30/07 55/116

56 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Figure 4-24 the total number of message frames and the data volume the message frame length the message frame type the faulty message frames POF screen form This screen form is only visible for switches with POF port. The currently available optical loss budget is displayed as a numerical value for each POF port. Figure 4-25 When clicking one of the displayed ports, the LWL POF Diagnose screen form is displayed. This screen form displays information on the time history of the available optical loss budget. V2.0 Issue 08/30/07 56/116

57 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Figure 4-26 Available optical loss budget Maintenance request (2db<budget >0db) Sending a PN IO maintenance alarm Display of a yellow wrench (HW Config, Topology Editor) Fiber-optic LEDs on the relevant port light up Incoming maintenance alarm Outgoing maintenance alarm Incoming maintenance alarm Outgoing maintenance alarm Maintenance request (Budget < = 0db) Sending a PN IO maintenance alarm Operation ensured Critical range Module failure Display of an orange wrench (HW Config, Topology Editor) Fiber-optic LEDs on the relevant port light up V2.0 Issue 08/30/07 57/116

58 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application 4.8 Diagnostics via port mirroring Switches of the X-200 family also feature a port mirroring functionality. This means that the data traffic is mirrored from a mirror port to a monitor port. If a PC with network sniffer software is connected to the monitor port, the data traffic via the mirror port can be followed. Note Only firmware V2.2.1 or higher supports port mirroring for the SCALANCE X208 switch. The firmware update can be downloaded from Product Support free of charge. Activating port mirroring The port mirror function is activated in WBM of the SCALANCE. Mirror port and monitor port are also set here. Figure 4-27 In this example, port 2 (mirrored port) of the SCALANCE X202 switch is mirrored to port 1 (monitor port), i.e. the data traffic from and to port 2 is also simultaneously transmitted to port 1. V2.0 Issue 08/30/07 58/116

59 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application 4.9 Diagnostics via integrated web server of the S7 CPU The web server provides the option of monitoring the CPU via the internet or the company-internal intranet. This enables the user to perform evaluations and diagnostics over long distances and from any location with internet access. Components The following list shows all products with web server functionality (as at August 2007) Table 4-13 SIMATIC family S7-400 CPU firmware V 5.0 or higher S7-300 CPU firmware V 2.5 or higher Product CPU414-3 PN/DP CPU416-3 PN/DP CPU416F-3 PN/DP CPU319-3 PN/DP CPU315-2 PN/DP CPU315F-2 PN/DP CPU317-2 PN/DP CPU317F-2 PN/DP Activating the web interface To be able to access the web server of the CPU, the web interface has to be activated in HW Config of STEP 7. V2.0 Issue 08/30/07 59/116

60 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Figure 4-28 Advantages of the web interface The web interface enables the user to conveniently access the diagnostics data of the CPU from any location with access to the internet. The following data can be read out: V2.0 Issue 08/30/07 60/116

61 Principles of Operation and Program Structures 3BFunctional Mechanisms of this Application Table 4-14 Diagnostics data Module identity (MLFB, firmware revision level, etc.) Example Status, diagnostic buffer Display of messages (Report System Error, Alarm S) Monitor variable V2.0 Issue 08/30/07 61/116

62 Principles of Operation and Program Structures 4BExplanations of the Example Program 5 Explanations of the Example Program 5.1 Explanations of the STEP 7 program Overview Figure 5-1 The figure below shows the most important program parts and the call structure of the STEP 7 program. DB 51 FB 51 OB 1 OB 82 OB 83 OB 86 CELL FC 1 ALARM_TRIGGER DB 49 FB 54 SFM_DB SFB 54 RALRM DB 1 ADDRESS& STATUS DB 50 SFM_GLOBAL _DB FC 49 SFM_FC DB 17 DB 16 DB 18 User program Messages Alarm evaluation/ individual error diagnostics V2.0 Issue 08/30/07 62/116

63 Principles of Operation and Program Structures 4BExplanations of the Example Program Explanations of the program structure Table 5-1 Block The following table shows the used STEP 7 blocks and their functionality. Description OB 1 If no link down on port 5 of the SCALANCE X208 switch was reported, FB 51 is called for control of the process in the cell. The status of port 5 is displayed by an output bit (output bit flashes in the event of a link down) The blocks for the Report System Error function are called. Block FC 1 is called. OB 82 I/O_FLT1 OB 83 I/O_FLT2 OB 86 RACK_FLT SFB 54 RALRM FB 51, IDB 51 CELL FC 1 ALARM_TRIGGER FB 49, IDB 49, FC 49, DB 50 DB 1 ADDRESS&STATUS DB 16 DB_OB86_INFO DB 17 DB_OB82_INFO Is called by the S7 program as soon as a diagnostic alarm has occurred. All relevant information (e.g., address of the component triggering the alarm, incoming or outgoing alarm) is copied to DB 17 (DB_OB82_INFO). The blocks for the Report System Error function are called. Is called by the S7 program when removing/inserting a module. To evaluate the PROFINET IO diagnostic alarm, SFB 54 is called and all relevant information is saved in DB 18 (DB_OB83_INFO). The blocks for the Report System Error function are called. Is called by the S7 program in the event of a module failure. To evaluate the PROFINET IO diagnostic alarm, SFB 54 is called and all relevant information is saved in DB 16 (DB_OB86_INFO). The blocks for the Report System Error function are called. SFB 54 determines extended data on the received PROFINET IO diagnostic alarm. FB 51 includes the control of the cell (flashing LEDs on the ET 200S PNFO). An active cell is also symbolized via a running light on the S7-300 station. Evaluation of the information of OB 82/83/86 from the DB16/17/18 data blocks The status of the individual modules is indicated by means of output bits (output set if module cannot be accessed) If a link down is detected on port 5 of the SCALANCE X208 switch, a flag is set. Generated blocks for the Report System Error function Contains all diagnostic addresses from HW Config Storage of the alarm information returned by the SFB 54 (RALRM) alarm block in OB 86. Storage of the alarm information returned by the SFB 54 (RALRM) alarm block in OB 82. V2.0 Issue 08/30/07 63/116

64 Principles of Operation and Program Structures 4BExplanations of the Example Program Block DB 18 DB_OB83_INFO Description Storage of the alarm information returned by the SFB 54 (RALRM) alarm block in OB 83. Response to a PROFINET IO diagnostic alarm If a module with diagnostics capability for which you have enabled the diagnostic alarm detects an error, it sends a diagnostic alarm to the CPU (for both an incoming and an outgoing event). Subsequently, the user program calls the corresponding error OB. When a diagnostic alarm is detected, OB 82 (I/O_FLT_1) is called When an Insert/remove module alarm is detected, OB 83 (I/O_FLT_2) is called In the event of a failure or communication error of a module, OB 86 (RACK_FLT) is called. OB 82 program description The user program calls OB 82 as soon as a diagnostic alarm is detected by the CPU. In this example, OB 82 is used to detect a link down on a port. Table 5-2 NW Explanation Code 1 OB 82 provides the logical start address of the component / port triggering the alarm. It additionally provides information on whether the alarm is incoming or outgoing. The cause of the error (local byte 8 and local word 10) and the module type are copied to DB 17 (DB_OB82_INFO). 2 The blocks for the system error messages are automatically called in OB 82. V2.0 Issue 08/30/07 64/116

65 Principles of Operation and Program Structures 4BExplanations of the Example Program Description of the STEP 7 code of OB 83 As soon as a module is removed or inserted during runtime, the operating system calls OB 83. In this example, OB 83 is used to detect the removing and inserting of a module of the ET200 S PNFO. Table 5-3 NW Explanation Code 1 The blocks for the system error messages are automatically placed and called in OB OB 83 provides the logical start address of the component causing the alarm as a word and has to be converted to a DWORD. SFB 54 supplies extended information that is stored in DB 18 (DB_OB83_INFO). If SFB 54 returns an error, the alarm processing is canceled. V2.0 Issue 08/30/07 65/116

66 Principles of Operation and Program Structures 4BExplanations of the Example Program OB 86 program description The user program calls OB 86 in the event of a module failure or a communication error. In this example, OB 86 is used to locate modules that cannot be accessed. Table 5-4 NW Explanation Code 1 The blocks for the system error messages are automatically placed and called in OB OB 86 provides the logical start address of the component causing the alarm as a word and has to be converted to a DWORD. SFB 54 supplies extended information that is stored in DB 16 (DB_OB86_INFO). If SFB 54 returns an error, the alarm processing is canceled. V2.0 Issue 08/30/07 66/116

67 Principles of Operation and Program Structures 4BExplanations of the Example Program FC 1 program description FC 1 (ALARM_TRIGGER) is called cyclically and evaluates the alarm information of the error OBs that has been read out. Depending on the error, LEDs on the digital output module or a flag are/is set. Each module and each port has its own diagnostic address that corresponds to the logical address of the component causing the alarm. This diagnostic address, which is unique in the STEP 7 project, enables the user to quickly detect the defective module. Note All diagnostic addresses from HW Config are stored in DB 1. Table 5-5 NW Explanation Code 1 Network 1 checks whether the alarm of OB 86 was incoming or outgoing and performs a change to the corresponding network. 2 If the alarm was an incoming alarm, this networks uses the diagnostic address to check which component has caused the alarm. If the defective component has been found, the corresponding output bit is set. Bit 1 corresponds to PROFINET IO address 1, bit 2 to PROFINET IO address 2, etc. V2.0 Issue 08/30/07 67/116

68 Principles of Operation and Program Structures 4BExplanations of the Example Program NW Explanation 3 When the component returns, the alarm is marked as outgoing. This network uses the diagnostic address to check which component has returned. If the component has been found, the corresponding bit is reset. Code 4 The last network checks the alarm information of OB 82. This network is processed when the module address corresponds to the diagnostic address of port 5 of the SCALANCE X208 switch. If the alarm was incoming, the communication to the cell is interrupted. The CELL_LinkDown flag is set. If an outgoing was identified, the flag is reset. V2.0 Issue 08/30/07 68/116

69 Principles of Operation and Program Structures 5BModifications to the Example Program 6 Modifications to the Example Program 6.1 Modification to the STEP 7 project Aside from the HMI and the CPU port, only one port of a cell is monitored in this application. To include further ports in the monitoring (e.g., to connect an additional cell to the SCALANCE X208 switch), only a few settings are required. SCALANCE X208 configuration in HW Config When you select SCALANCE X208 in HW Config, the 8 ports of the module are displayed in addition to interface module in the configuration table in the bottom part of the window. Figure 6-1 V2.0 Issue 08/30/07 69/116

70 Principles of Operation and Program Structures 5BModifications to the Example Program Figure 6-2 To monitor ports in addition to port 1, port 2 and port 5, you have to adjust the port properties. In the Options tab, change the properties of the port as follows: Transmission medium / duplex: Automatic settings (monitor). Save and compile HW Config. SCALANCE X202 configuration in HW Config The SCALANCE X202 is configured analogously to the SCALANCE X208. Again change the properties of the port you want to additionally monitor as described. Adaptation of the blocks in the STEP 7 project As soon as the port is monitored, the corresponding error OB is automatically called in the event of a link down. All available diagnostic addresses have already been inserted into DB 1 that includes all diagnostic addresses. FC 1 (ALARM_TRIGGER) is responsible for the alarm evaluation. If you want to react to a link down of new port to be monitored, you have to provide a corresponding reaction in this block. You can use the already existing code as a template and insert the new diagnostic address. All necessary SNMP variables have already been loaded to the SNMP OPC server. No changes are required. After all changes have been made, reboot the controller. V2.0 Issue 08/30/07 70/116

71 Principles of Operation and Program Structures 5BModifications to the Example Program 6.2 Modification in WinCC flexible Figure 6-3 The schematic representation of the SCALANCE modules in the HMI system has already been designed for the status display of all ports and only has to be activated. Open the WinCC flexible project via STEP 7 and open IE_Network. When you select the port whose status you want to graphically display in the schematic representation of the SCALANCE modules, the properties for this rectangle appear in the bottom part of the window. In the properties window in the Animations group, click Appearance. Activate the Enable checkbox and then save the project. V2.0 Issue 08/30/07 71/116

72 Structure, Configuration and Operation of the Application 6BInstallation and Startup Structure, Configuration and Operation of the Application 7 Installation and Startup 7.1 Hardware and software installation This chapter describes which hardware and software components have to be installed. The descriptions and manuals as well as delivery information included in the delivery of the respective products should be observed in any case. Hardware installation The hardware components are listed in chapter 2.4. For the hardware configuration, please follow the instructions listed in the table below: WARNING Only switch on the power supply after the last step has been completed! Preparing the necessary connecting cables Table 7-1 No. Instruction Remark 1. Prepare four Ethernet cables from the specified accessories for the Ethernet connecting cables. 2. Prepare two POF cables from the specified accessories for the fiber-optic cables. Alternatively, you can also use pre-assembled Ethernet cables. Alternatively, you can also use pre-assembled POF cables. Installing the PC module Table 7-2 No. Instruction Remark 1. Install the Ethernet card in the PG/PC. When you are using a field PG, this card already exists. V2.0 Issue 08/30/07 72/116

73 Structure, Configuration and Operation of the Application 6BInstallation and Startup Installing the controller components Table 7-3 No. Instruction Remark 1. Mount the SCALANCE-X208 and SCALANCE X202 switches on the S7-300 DIN rail. 2. Mount the power supply, the CPU and the SM322 DO module of the S7-300 on the S7-300 DIN rail. 3. Mount the two ET200S PNFO on the 35mm top-hat rail. 4. Attach the following modules and the corresponding terminal modules to the first ET 200S PNFO head module in the following order: PM 24VDC 4 DO 24VDC 0.5A 5. Attach the following modules and the corresponding terminal modules to the second ET 200S PNFO head module in the following order: PM 24VDC 2 DI 24VDC 6. Ensure the power supply with 24VDC for SCALANCE X208, SCALANCE X202, CPU, SM322 DO module and the two ET 200S PNFO. 7. Supply the power supply with 230VAC. 8. Use the Ethernet cables to network CPU, PG and SCALANCE X 202 with the SCALANCE X208 switch. 9. Use the POF cable to network the first ET 200S PNFO with the SCALANCE X202 switch. 10. Optional: Connect a second PC to the SCALANCE X202 switch for port mirroring 11. Use the POF cable to network the second ET200S PNFO with the first ET 200S PNFO. Connect PIN 2 (L1) and PIN 3 (M) of the power module to a 24V power supply. You can pick up the 24V from the head module. Connect PIN 2 (L1) and PIN 3 (M) of the power module to a 24V power supply. You can pick up the 24V from the head module. Port 1 CPU Port 2 HMI station / PG Port 5 SCALANCE X202 port 2 Port 3 of the SCALANCE X202 switch with port 1 of the ET 200S PNFO PC to port 1 of the SCALANCE X202 switch Port 2 of the first ET 200S PNFO with port 1 of the second ET 200S PNFO Note The installation guidelines for SIMATIC S7 and SIMATIC NET always have to be observed. V2.0 Issue 08/30/07 73/116

74 Structure, Configuration and Operation of the Application 6BInstallation and Startup Installing the standard software Table 7-4 No. Instruction Remark 1. Install STEP 7 V5.4 SP2. Follow the instructions of the installation program. 2. Install SIMATIC NET Edition Follow the instructions of the installation program. 3. Install WinCC flexible 2005 SP1 HF7. Follow the instructions of the installation program. 4. Install network sniffer software. Only if you want to listen in on the data traffic via the mirror port. 5. Transfer all required licenses. 7.2 Application software installation General preparations Unzip this file: _DIAG_NETWORK_CODE_BAND1_V20.zip. This folder contains the archived Diagnostic.zip STEP 7 project the device profiles for the SCALANCE X208 and X202 switches. V2.0 Issue 08/30/07 74/116

75 Structure, Configuration and Operation of the Application 6BInstallation and Startup Changing the IP address of the PG The figure below shows the network setting to which you have to change the PG/the PC: Table 7-5 No. Instruction Remark / note 1. Open the Internet Protocol (TCP/IP) Properties by selecting Start -> Settings -> Network Connection ->Local Connections. Select the Use the following IP address check box and fill out the field as shown in the screen shot on the right. Close the dialog boxes with OK. Assigning name and IP address of the PROFINET nodes To ensure the PROFINET functionality, all network stations require unique names that are identical in the device and in the configuration of the S7 CPU. To assign these names and the IP addresses, follow the instructions listed in the table below. The following table provides an overview of the used PROFINET device names and IP addresses: Table 7-6 Module Device name IP address CPU PN/DP pn_io SCALANCE X208 scalance-x SCALANCE X202 scalance-x202-2pirt ET 200S PNFO im151-3pnfov ET 200S PNFO im151-3pnfov HMI station V2.0 Issue 08/30/07 75/116

76 Structure, Configuration and Operation of the Application 6BInstallation and Startup Table 7-7 No. Instruction Remark 1. Open the SIMATIC MANAGER and in Options -> Set PC/PG Interface set the S7 ONLINE interface to the Ethernet card connected to the SCALANCE X208 switch and to TCP/IP. Click OK to close the dialog box. 2. In the SIMATIC MANAGER, select PLC -> Edit Ethernet Node. Click the Browse button to start the search for further nodes. V2.0 Issue 08/30/07 76/116

77 Structure, Configuration and Operation of the Application 6BInstallation and Startup No. Instruction 3. A new dialog box with all nodes that have been found in the network appears. Select the CPU (device type: S7-300) and click OK. Remark 4. Enter the IP address as listed in Table 7-6 and the appropriate subnet mask and assign them to the device by clicking the Assign IP Configuration button. V2.0 Issue 08/30/07 77/116

78 Structure, Configuration and Operation of the Application 6BInstallation and Startup No. Instruction 5. In the lower part of the dialog box, enter the device name as listed in Table 7-6 and assign it to the device by selecting Assign Name. Remark 6. Perform steps 2 through 5 for the SCALANCE X208 switch (device type: SCALANCE X200). For the IP address and the device name of this module, please refer to Table 7-6. Note: When performing step 3, please observe the specified mac address to distinguish between the SCALANCE modules! V2.0 Issue 08/30/07 78/116

79 Structure, Configuration and Operation of the Application 6BInstallation and Startup No. Instruction 7. Perform steps 2 through 5 for the SCALANCE X202 switch (device type: SCALANCE X200). For the IP address and the device name of this module, please refer to Table 7-6. Note: When performing step 3, please observe the specified mac address to distinguish between the SCALANCE modules! Remark 8. Perform steps 2 through 5 for the first ET 200S PNFO (device type: ET 200S). For the IP address and the device name of this module, please refer to Table 7-6. Note: When performing step 3, please observe the specified mac address to distinguish between the two ET 200S PNFO modules! V2.0 Issue 08/30/07 79/116

80 Structure, Configuration and Operation of the Application 6BInstallation and Startup No. Instruction 9. Perform steps 2 through 5 for the second ET 200S PNFO (device type: ET 200S). For the IP address and the device name of this module, please refer to Table 7-6. Note: When performing step 3, please observe the specified mac address to distinguish between the two ET 200S PNFO modules! Remark Loading the STEP7 project to the CPU Table 7-8 No. Instruction Remark 1. Open the SIMATIC MANAGER and retrieve the Diagnostic.zip STEP 7 project. 2. Select the SIMATIC 300 S7 station and use PLC-> Download to load the entire project to your CPU. File -> Retrieve V2.0 Issue 08/30/07 80/116

81 Structure, Configuration and Operation of the Application 6BInstallation and Startup Configuring the Station Configuration Editor Table 7-9 No. Instruction Note 1. Open the Station Configuration Editor by selecting Start -> Station Configurator or by double-clicking the icon in the taskbar. Select the Import Station button. 2. Navigate to the directory of the STEP 7 project and open the XDBs folder. 3. Open the HmiS_2.xdb file and click OK after the station has been imported. V2.0 Issue 08/30/07 81/116

82 Structure, Configuration and Operation of the Application 6BInstallation and Startup No. Instruction 4. The HMI station is now configured. Note 5. Select the Station Name button to change the name to HMI-Station. Click OK to close the dialog box. V2.0 Issue 08/30/07 82/116

83 Structure, Configuration and Operation of the Application 6BInstallation and Startup Starting HMI Table 7-10 No. Instruction Remark 1. Below the HMI station, select WinCC flexible RT. Use the right mouse button -> Open Object to open the WinCC flexible project. 2. Recompile the WinCC flexible project by selecting Project -> Compile -> Rebuild All. 3. Start WinCC flexible Runtime. 4. WinCC flexible RT connects to the S7-300 station and displays the current status of the modules and ports. V2.0 Issue 08/30/07 83/116

84 Structure, Configuration and Operation of the Application 7BConfiguration 8 Configuration 8.1 Configuring Report System Error Setting the Report System Error STEP 7 function Table 8-1 These instructions show you the steps that are necessary to set the Report System Error function. This function has already been configured in the STEP 7 code included in the delivery. No. Instruction Note 1. Open the hardware configuration of the SIMATIC 300 station. 2. Select the CPU and open the dialog box in Options > Report System Error. 3. In the General tab, you can determine the numbers of the diagnostic blocks. STEP 7 provides default values you can change. In this example, the block numbers were not changed. V2.0 Issue 08/30/07 84/116

85 Structure, Configuration and Operation of the Application 7BConfiguration No. Instruction 4. In the OB Configuration tab, you define in which OBs the Report System Error call is to be performed. The most important OBs are OB 82, OB 83, OB 86 and OB 1. Note 5. In the CPU in Stop tab, you specify when the CPU is to go to stop. 6. Click the Generate button to generate the blocks in the project and to set the calls in the OBs. V2.0 Issue 08/30/07 85/116

86 Structure, Configuration and Operation of the Application 7BConfiguration Setting up the SFM alarm in Runtime Table 8-2 No. Instruction Note 1. Open the WinCC flexible project via STEP In the WinCC flexible project tree, go to Alarm Management -> Settings -> Alarm Settings. In Alarm Procedure, set SIMATIC SFM to ON. 3. When inserting a message window, the event type to be displayed can be selected. 8.2 Configuring the SNMP OPC server Preparations in STEP 7 To be able to configure the SNMP OPC server, create an HMI station in the Simatic Manager, select the WinCC flexible RT device type and activate S7RTM in the Configuration tab of the HMI station properties. In the hardware configuration of the HMI station, insert the network card you are using and network it with the already configured S7-300 CPU and the other modules. Private MIB of the SCALANCE-X2xx To be able to use all SNMP information provided by the SCALANCE X modules, you require the private MIB. V2.0 Issue 08/30/07 86/116

87 Structure, Configuration and Operation of the Application 7BConfiguration The private MIB is identical for the SCALANCE X208 and X202. It is thus sufficient to load only one from a SCALANCE module. The private MIB is available via Web-based Management by entering the following URL in a web browser (e.g. Internet Explorer): Display the source text of the received page (in Internet Explorer in the View -> Source menu) and save this text as a text file under the name PrivateMIBX200.mib. Note The standard MIBs are stored in the following directory: <STEP7InstallationDirectory>\S7DATA\snmp\mib Device profiles You can either create device profiles yourself or use already existing profiles. Device profiles that have already been prepared for all modules are located in the STEP 7 installation directory. Prepared device profiles for the SCALANCE modules already include integration of the private MIB. To ensure that only the SNMP variables that are actually required are loaded to the SNMP OPC server, it is useful to create a device profile. Note The prepared device profiles are stored in the following directory: <STEP7InstallationDirectory>\S7DATA\snmp\profile V2.0 Issue 08/30/07 87/116

88 Structure, Configuration and Operation of the Application 7BConfiguration Configuring the SNMP OPC server Table 8-3 Instruction To configure the SNMP OPC server, select the HMI station in STEP 7 and open the Configuration. Open the OPC Server Properties and in the SNMP tab select the Edit Plant Configuration button. Remark In the plant configuration, import all configured network stations with name and IP address using the Import button. Alternatively, the devices to be monitored can also be manually entered with Add. To assign a separate SNMP device profile to the devices to be monitored, select the device. Use the Create Profile button to open the corresponding dialog box. V2.0 Issue 08/30/07 88/116

89 Structure, Configuration and Operation of the Application 7BConfiguration Instruction To create a profile for a SCALANCE X module, load the MIB-II_V10.txt profile as a basis. This profile is located in the STEP 7 installation directory in the S7DATA/snmp/profile folder. Remark As soon as the profile has been loaded, change to the MIB modules tab. To be able to use the SCALANCE module-specific SNMP variables, reload its private MIB. To do this, click the Load MIB button. Navigate to the directory in which you have stored the PrivateMIBX200.mib private MIB, select the file and open it. The private MIB is loaded. V2.0 Issue 08/30/07 89/116

90 Structure, Configuration and Operation of the Application 7BConfiguration Instruction After selecting the Variables tab, you can open a tree structure in the left part of the window in which the general SNMP variables are located at the mib-2 branch and the specific variables at the iscalancex200 branch. The right part of the window displays the variables already selected for the OPC server. To improve clarity, you can also combine the variables in groups. Remark In mib-2 in interfaces, you find the ifoperstatus variable that includes the current status of the SCALANCE module ports. This variable is an instanced variable which makes it necessary to indicate the desired instances. For the SCALANCE X208, select the instances 1 8 for the ports 1 8, for the SCALANCE X202 the instances 1 4. From the private SCALANCE variables, select snx200faultstate for the overall status and snx200powersupplystate for the status of the redundant power supply. V2.0 Issue 08/30/07 90/116

91 Structure, Configuration and Operation of the Application 7BConfiguration Instruction Store this newly created profile under any name in the STEP 7 installation directory in the S7DATA/snmp/user_profile folder and exit the Create Profile dialog box. Remark You can now select the newly created profile as a device profile for the SCALANCE module and use it. To do this, select and double-click the device. In the Edit node dialog box, you can select the created profile or already existing profiles. After exiting the dialog boxes with OK and save and compiling the station, the configuration of the SNMP OPC server is complete and the station can be loaded. Note The ET 200S PNFO modules have no private MIB. It is not required to create a separate profile. You can use the already existing MIB-II-V10.txt profile. V2.0 Issue 08/30/07 91/116

92 Structure, Configuration and Operation of the Application 7BConfiguration 8.3 Changing the SCALANCE device profiles Table 8-4 After generation as a text file the device profiles are only stored in the STEP 7 installation directory in the S7DATA/snmp/user_profile folder and not in the STEP 7 project directory. The XDB file generated after saving and compiling the HMI station contains the necessary information. If you want to change the device profiles, you need the text file. The code folder included in the delivery contains the device profiles of the two SCALANCE modules as a text file. Instruction Save the device profiles in your STEP 7 installation directory in the S7DATA/snmp/user_profile folder. To change the device profiles, select the HMI station in STEP 7 and open the Configuration. Open the OPC Server Properties and in the SNMP tab select the Edit Plant Configuration button. Select a SCALANCE. Use the Create Profile button to open the dialog box required for the change. Remark Load the respective device profile from the S7DATA/snmp/user_profile folder. V2.0 Issue 08/30/07 92/116

93 Structure, Configuration and Operation of the Application 7BConfiguration Instruction Change the device profile as desired and save it. Exit the dialog box by clicking OK. Remark After saving and compiling the station, the SNMP OPC server has been configured and the station can be loaded. V2.0 Issue 08/30/07 93/116

94 Structure, Configuration and Operation of the Application 7BConfiguration 8.4 Connection partner for topology Table 8-5 STEP 7 provides the option of manually entering the partner that is connected to a port of a component. This is particularly useful if there is no online access to the configured components and if it is thus not possible to detect the actual connections via LLDP. No. Instruction Note 1. Open the hardware configuration of the STEP 7 project. 2. Select a PROFINET device. Aside from the interface module, the information displayed in the lower part of the window in the configuration table also includes the module ports. 3. Select a port and open the properties by double-clicking it. Change to the Topology tab. The Partner Port drop-down list displays all free ports of all components in this project. As soon as you have selected a partner port, the port you have just edited is automatically entered as a partner in the partner port properties. V2.0 Issue 08/30/07 94/116

95 Structure, Configuration and Operation of the Application 8BOperation of the Application 9 Operation of the Application Note Before operating the application, please check whether the diagnostic addresses stored in DB 1 correspond to the addresses from HW Config and correct them if necessary. 9.1 Error scenarios Two different types of errors can be diagnosed for the SCALANCE modules: Failure of one of the two redundant power supplies Link down of a communication port, i.e. an interruption of the communication connection to the port The ET 200S PNFO modules integrated into the PROFINET IO system via fiber-optic cables can also be diagnosed. The following types of errors can be diagnosed: Link down of a communication port of the integrated 2-port switch Removing/inserting a module Demand of maintenance/maintenance request of a fiber-optic cable In this application, diagnostics of eight different error conditions were implemented. These conditions are listed in the following. V2.0 Issue 08/30/07 95/116

96 Structure, Configuration and Operation of the Application 8BOperation of the Application Link down of a communication port Link down on port 3 of the SCALANCE X202-2P IRT Aside from two electrical ports, the SCALANCE X202-2 switch also features two optical ports. Via the optical port 3, the two ET 200S PNFO are connected to the PROFINET IO system via fiber-optic cables. Table 9-1 Explanation Via SNMP, the OPC server receives the message that port 3 on the SCALANCE X202 has failed. This causes a change of the value of the OPC variables in the HMI system: 1. X202 status: The display for port 3 changes to RED 2. Network screen: The two ET 200S PNFO and their network connection are displayed in RED The PROFINET IO alarm is evaluated in the CPU and an alarm message is sent to the HMI system. In the HW Config online view, all modules affected by the diagnostic alarm are provided with a diagnostics symbol. Graphic view V2.0 Issue 08/30/07 96/116

97 Structure, Configuration and Operation of the Application 8BOperation of the Application Explanation The Module Information of the SCALANCE X202 provides detailed diagnostics information. Graphic view The PROFINET IO Topology Editor displays the failure of port 3 on the SCALANCE X202 and the loss of the two ET 200S PNFO by new colors and diagnostics symbols. Link down on port 2 of the first ET200 S PNFO The IM151-3 PN FO features two integrated interfaces for plastic optical fibers (POF). This provides the option of connecting an additional ET 200S PNFO in series. All alarm messages of the second ET 200S PNFO are forwarded to the PROFINET IO system via the first ET 200S PNFO and detected by the CPU. V2.0 Issue 08/30/07 97/116

98 Structure, Configuration and Operation of the Application 8BOperation of the Application Table 9-2 Explanation Via SNMP, the OPC server receives the message that port 2 on the first ET 200S PNFO has failed. This causes a change of the value of the OPC variables in the HMI system: In the network screen, the second ET 200S PNFO and its network connection are displayed in RED. Graphic view The PROFINET IO alarm is evaluated in the CPU and an alarm message is sent to the HMI system. In the HW Config online view, all modules affected by the diagnostic alarm are provided with a diagnostics symbol. V2.0 Issue 08/30/07 98/116

99 Structure, Configuration and Operation of the Application 8BOperation of the Application Explanation The Module Information of the ET 200S PNFO provides detailed diagnostics information. Graphic view The PROFINET IO Topology Editor displays the failure of port 2 of the ET 200S PNFO and the loss of the second ET 200S PNFO by new colors and diagnostics symbols. Link down on port 5 of the SCALANCE X208 The cell-internal I/O, represented by a SCALANCE X202 and two ET 200S PNFO modules, is connected to port 5 of the SCALANCE X208 switch. In the event of a link down (broken cable, plug removed, etc.), all diagnostic mechanisms are available. V2.0 Issue 08/30/07 99/116

100 Structure, Configuration and Operation of the Application 8BOperation of the Application Table 9-3 Explanation Via SNMP, the OPC server receives the message that port 5 on the SCALANCE X208 has failed. This causes a change of the value of the OPC variables in the HMI system: 1. X208 status: The display for port 5 changes to RED 2. Network screen: The cell-internal I/O (SCALANCE X202 and the two ET 200S PNFO) and their network connections are displayed in RED. 3. Cell status: The status of the cell changes to RED The PROFINET IO alarm is evaluated in the CPU and an alarm message is sent to the HMI system. In the HW Config online view, all modules affected by the diagnostic alarm are provided with a diagnostics symbol. Graphic view V2.0 Issue 08/30/07 100/116

101 Structure, Configuration and Operation of the Application 8BOperation of the Application Explanation The Module Information of the SCALANCE X208 provides detailed diagnostics information. Graphic view The PROFINET IO Topology Editor displays the failure of port 5 on the SCALANCE X208 and the loss of the cell-internal I/O by new colors and diagnostics symbols. Link down on port 2 of the SCALANCE X208 The HMI system is connected to port 2, i.e. only the HMI system can detect that the connection is interrupted in the event of a link down on this port. However, alarm messages of the CPU are still acquired after reestablishing the connections and can be checked in the message screen. Note The online view in HW Config, Module Information and the Topology Editor require that an online access to the plant via STEP 7 exists. In this scenario, the connection to the controller is interrupted. Consequently, the diagnostic capabilities listed above are not available. V2.0 Issue 08/30/07 101/116

102 Structure, Configuration and Operation of the Application 8BOperation of the Application Table 9-4 Explanation Via SNMP, the OPC server receives the message that the connection to the SCALANCE X208 has failed. This causes a change of the value of the OPC variables in the HMI system: 1. Status of the SCALANCE modules: The status displays flash RED 2. Network screen: All network components that are not accessible and their connections are displayed in RED 3. Cell status: The status of the cell changes to RED The HMI system reports that the connection to the S7-300 CPU is interrupted. Graphic view Link down on port 1 of the SCALANCE X208 The S7-300 CPU is connected to port 1 of the SCALANCE X208. Also in this case, the alarm messages of the CPU are only displayed after the connection has been reestablished. However, diagnostics of the SCALANCEs via SNMP are still possible. Note The online view in HW Config, Module Information and the Topology Editor require that an online access to the plant via STEP 7 exists. In this scenario, the connection to the controller is interrupted. Consequently, the diagnostic capabilities listed above are not available. V2.0 Issue 08/30/07 102/116

103 Structure, Configuration and Operation of the Application 8BOperation of the Application Table 9-5 Explanation Via SNMP, the OPC server receives the message that port 1 on the SCALANCE X208 has failed. This causes a change of the value of the OPC variables in the HMI system: 1. X208 status: The display for port 1 changes to RED 2. Network screen: The S7 station and its network connection are displayed in RED. 3. Cell status: The status of the cell changes to RED Graphic view The HMI system reports the missing connection to the S7 CPU. V2.0 Issue 08/30/07 103/116

104 Structure, Configuration and Operation of the Application 8BOperation of the Application Failure of one of the two power supplies Table 9-6 In the event of a failure of a power supply on the SCALANCE modules, complete diagnostics are still available. Explanation Via SNMP, the OPC server receives the message that one of the two power supplies on the SCALANCE X208 has failed. This causes a change of the value of the OPC variables in the HMI system: In the network screen, the Power Supply display changes to RED. Graphic view The PROFINET IO alarm is evaluated in the CPU and an alarm message is sent to the HMI system. In the HW Config online view, all modules affected by the diagnostic alarm are provided with a diagnostics symbol. V2.0 Issue 08/30/07 104/116

105 Structure, Configuration and Operation of the Application 8BOperation of the Application Explanation The Module Information of the SCALANCE X208 provides detailed diagnostics information. Graphic view The PROFINET IO Topology Editor indicates the failure of a power supply by new colors and diagnostics symbols Demand of maintenance of a fiber-optic cable Specific PROFINET components can display information on whether preventive maintenance is required and, if this is the case, how urgent it is. This is very useful when using a POF fiber-optic cable. Note The Diagnostics screen in WinCC flexible RT is controlled via SNMP variables. No SNMP variable includes maintenance information. Consequently, preventive maintenance information cannot be visualized in RT but only displayed as a system message. V2.0 Issue 08/30/07 105/116

106 Structure, Configuration and Operation of the Application 8BOperation of the Application Table 9-7 Explanation The PROFINET IO alarm indicating preventive maintenance is evaluated in the CPU and an alarm message is sent to the HMI system. Graphic view In the HW Config online view, the preventive maintenance information is symbolized by wrenches. Module Information provides detailed diagnostics information. V2.0 Issue 08/30/07 106/116

107 Structure, Configuration and Operation of the Application 8BOperation of the Application Explanation The PROFINET IO Topology Editor indicates the maintenance information by wrenches and by displaying the currently available optical loss budget. Graphic view Web-based Management of the SCALANCE X202 displays the currently available optical loss budget for each POF port as a numerical value. It additionally graphically displays the time history of the optical loss budget. Note The optical loss budget is a measure for the attenuation that can still be bridged on the connection between transmitter and receiver. The higher the budget, the larger the bridgeable attenuation of the link. When the budget decreases, the attenuation of the transmission link has increased. V2.0 Issue 08/30/07 107/116

108 Structure, Configuration and Operation of the Application 8BOperation of the Application Removing/inserting a module Note The Diagnostics screen in WinCC flexible RT is controlled via SNMP variables. The ET 200S PNFO do not feature private SNMP variables in which information on the submodules, etc. could be stored. Consequently, removing/inserting cannot be visualized in RT but only displayed as a system message. Table 9-8 Explanation The PROFINET IO alarm indicating that a module of the ET 200S PNFO has been removed/inserted is evaluated in the CPU and an alarm message is sent to the HMI system. In the HW Config online view, all modules affected by the diagnostic alarm are provided with a diagnostics symbol. Graphic view V2.0 Issue 08/30/07 108/116

109 Structure, Configuration and Operation of the Application 8BOperation of the Application Explanation Module Information provides detailed diagnostics information. Graphic view The PROFINET IO Topology Editor indicates the failure of a module by new colors and diagnostics symbols. V2.0 Issue 08/30/07 109/116

110 Structure, Configuration and Operation of the Application 8BOperation of the Application 9.2 Topology Editor Table 9-9 This section shows how you can read out the current interconnection with the aid of the Topology Editor. No. Instruction Remark 1. Open HW Config and select a PROFINET device, e.g. the SCALANCE X Right-click the selected component and select PROFINET IO Topology. 3. The Topology Editor opens. Change to the Offline/Online Comparison tab. The left side of the dialog box lists all configured modules. The color orange indicates that the module is not assigned to a detected module. To determine the current interconnection, click the start button. V2.0 Issue 08/30/07 110/116

111 Structure, Configuration and Operation of the Application 8BOperation of the Application No. Instruction 4. The right side of the dialog box lists all modules that have been detected online. If a port of the module is interconnected, the connection partner is indicated. The meaning of the colors of the lines is described in chapter 4.3. Remark 5. Assign the connections that have been detected online to the configured offline modules. Select the module to be assigned in both offline and online topology. Apply this assignment by using the Apply button. 6. The Graphic view tab graphically displays the currently assigned interconnections. Alternatively to the Offline/Online Comparison tab, you can also interconnect the ports here. To do this, drag the pressed mouse pointer from a port of a device to the connection partner and release the mouse pointer over the partner port. Exit the Editor with OK. V2.0 Issue 08/30/07 111/116

112 Structure, Configuration and Operation of the Application 8BOperation of the Application No. Instruction Remark 7. Save and recompile HW Config. Subsequently, the partner port is automatically entered in HW Config in the Port Properties. 9.3 Opening the web page of the modules Note To access Web-based Management of the SCALANCE modules or the web page of the CPU, two options exist in this example: Via a web browser Via WinCC flexible RT No proxy server must be set in the connection properties of the internet browser. Table 9-10 No. Instruction Remark 1. 1 st option: Open a web browser, for example Internet Explorer, and enter the IP address of the SCALANCE module or the CPU. 2. The start page is loaded. Log on to Web-based Management with name and password. V2.0 Issue 08/30/07 112/116

113 Structure, Configuration and Operation of the Application 8BOperation of the Application No. Instruction Remark 3. 2 nd option: In WinCC flexible RT, click the SCALANCE modules or the CPU. The web browser with the corresponding module IP address opens automatically. 9.4 Triggering a diagnostic alarm Table 9-11 As soon as a link down is detected on a monitored port, the monitored redundant power supply is missing, a module is removed or inserted or the POF cable requires maintenance, a diagnostic alarm is sent to the CPU. No. Action Remark 1. Remove, for example, the Ethernet cable from port 5 of the SCALANCE X The evaluation of the diagnostic alarm detects a link down on port 5. The running light of the DO module on the controller stops. One output bit lights up for each module that is no longer accessible. The bit number corresponds to the respective PROFINET IO device number. The SCALANCE X202 and the two ET 200S PNFO can no longer be accessed. V2.0 Issue 08/30/07 113/116

114 Structure, Configuration and Operation of the Application 8BOperation of the Application No. Action Remark 3. Further diagnostic capabilities are available to you. Removing/inserting a module Table 9-12 WinCC flexible RT Report System Error HW Config online view Topology Editor Module Information No. Action Remark 1. Remove a module, for example the DO, from one of the two ET200 S PNFO. 2. The CPU receives a diagnostic alarm. 3. Further diagnostic capabilities are available to you. Please note chapter Report System Error HW Config online view Topology Editor Module Information V2.0 Issue 08/30/07 114/116