Diagnostics block with visualization via HMI or web browser for AS Interface in the TIA Portal

Transcription

1 Library description 04/2016 Diagnostics block with visualization via HMI or web browser for AS Interface in the TIA Portal AS-Interface

2 Siemens AG 2016 All rights reserved Warranty and Liability Warranty and Liability Note The application examples are not binding and do not claim to be complete with regard to configuration, equipment or any contingencies. The application examples do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible for the correct operation of the described products. 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 we 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 and without prior notice. If there are any deviations between the recommendations provided in this application example and other Siemens publications e.g. Catalogs the contents of the other documents shall have priority. 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 fundamental contractual obligations ( wesentliche Vertragspflichten ). The damages for a breach of a substantial contractual obligation are, however, limited to the foreseeable damage, typical for the type of contract, except in the event of intent or gross negligence or injury to life, body or health. The above provisions do not imply a change of the burden of proof to your detriment. Any form of duplication or distribution of these application examples or excerpts hereof is prohibited without the expressed consent of Siemens AG. Security information Siemens provides products and solutions with industrial security functions that support the secure operation of plants, solutions, machines, equipment and networks. To protect plants, systems, machines and networks against cyber threats, it is necessary to implement (and continuously maintain) a holistic, state-of-the-art industrial security concept. Products and solutions from Siemens are only one part of such a concept. The customer is responsible for preventing unauthorized access to the customer s plants, systems, machines and networks. Systems, machines and components should be connected to the company network or the Internet only if and to the extent necessary and if appropriate protective action (e.g., use of firewalls and network segmentation) was taken. In addition, Siemens recommendations regarding appropriate protective action should be followed. For more information about industrial security, visit Siemens products and solutions undergo continuous development to make them even more secure. Siemens strongly recommends to perform updates as they become available and use only the latest product versions. Using versions that are out of date or no longer supported can increase the risk of cyber threats. To continually stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed under Entry-ID: , V1.0, 04/2016 2

3 Siemens AG 2016 All rights reserved Table of Contents Table of Contents Warranty and Liability Overview Area of application and utility Scope of validity Available code packages Documentation guide Function and effect Effect scheme Information on the program blocks Overview of the blocks The presentation in detail Calling environment Performance data Overview of HMI template The diagnostic screen The statistics screen Overview of the web interface The diagnostic window The control panel The statistics screen Hardware and software components The program blocks in detail The visualization blocks AsiHmiVisu and AsiWebVisu The diagnostic block AsiDiag The raw data of the AsiDiag Overview of diagnostic raw data Overview of statistic raw data The data structure in the instance data block The project example _PROJECT Addresses of hardware components Using the STEP 7 project Operating the STEP 7 project The WinCC configuration Using visualization images Adjusting the AS-i master selection list Changes to the interface The list position entries Adjusting the text display of the selection list Adjusting the AS-i slaves information HTML configuration Using websites Adjusting the AS-i master information Adjusting the AS-i slave information Adjusting the display texts Accessing the user-defined websites The library Using library blocks Initializing the blocks Entry-ID: , V1.0, 04/2016 3

4 Siemens AG 2016 All rights reserved Table of Contents 8 References History Entry-ID: , V1.0, 04/2016 4

5 Siemens AG 2016 All rights reserved 1 Overview 1 Overview 1.1 Area of application and utility AS interface slaves are connected to a SIMATIC control via gateways or communication modules. In case of service support, an individual evaluation of diagnostic data of AS-i masters and slaves in the STEP 7 user program supports the system operator during troubleshooting, so that a smooth operation can be quickly restored. To make the AS-i diagnosis easier for the user, the present example contains a number of blocks for a comfortable evaluation and visualization of the diagnostic data: in the user program: the read AS-i diagnostic data are stored in a data block where they are available for individual further processing. on HMI panels: the library contains blocks that serve as interface between HMI panel and CPU. via web browsers: SIMATIC CPUs with a PROFINET interface offer the option to access CPU tags with the help of individually designed websites, provided and made available by the system. The library contains blocks that serve as interface between user defined websites and CPU. Schematic layout Figure 1-1 The following figure shows a possible hardware structure for the application of the STEP 7 blocks: S CP 343 S HMI-Panel PG PROFIBUS DP PROFINET IE ET 200SP IE/AS-i Link DP/AS-i Link DP/AS-i F-Link DP/AS-i Link 20E AS-Interface Entry-ID: , V1.0, 04/2016 5

6 Siemens AG 2016 All rights reserved 1 Overview The HMI visualization The following figure shows the HMI template for the visual diagnosis of the AS-i masters and slaves: Figure 1-2 The web visualization The following figure shows the web interface for the visual diagnosis of the AS-i masters and slaves: Figure 1-3 Entry-ID: , V1.0, 04/2016 6

7 Siemens AG 2016 All rights reserved 1 Overview 1.2 Scope of validity The AS-i diagnosis has been developed for the following SIMATIC S7 CPUs: SIMATIC S7-300/400 SIMATIC S All current AS-i masters from the SIMATIC product range are supported: DP/AS-i Link 20E DP/AS-i LINK Advanced DP/AS-i F-Link IE/AS-i LINK PN IO CP (P) CM AS-i Master ST for ET 200SP (as from Firmware 1.1) TIA Portal V13 SP 1 Update 7 and WinCC V13 SP1 serve as configuration software. Note Further information about the hardware and software requirements can be found in chapter Available code packages Overview For this example, the following code packages are provided: S7_1500_CODE_TIAV13.zip: This package contains the blocks/ the project for a S control S7_x00_CODE_TIAV13.zip: This package contains the blocks/ the project for a S7-300 or S7-400 control. Both code packages are identical in their function and effect; they were designed and developed for the relevant control only. Contents of code package Every code package contains two parts: 1. A STEP 7 building block library, containing the relevant blocks for diagnosis and an additional file with user-defined websites for the web server of the CPU. This library is intended for creating own AS-i diagnostic applications. 2. A STEP 7 sample project _PROJECT in which the program blocks, the HMI templates and the web-based AS-i diagnosis are used as an example. The following charts briefly summarize the components of the code packages: Entry-ID: , V1.0, 04/2016 7

8 Siemens AG 2016 All rights reserved 1 Overview Table 1-1 Package name Components Application STEP 7 library Folder _LIB: Relevant program blocks for diagnosis, HMI and web visualizations of an AS-i network Folder HTML_FILES: User-specific HTML pages and javascript for the visualization of the diagnostic information and operation of the functions via the web server. Creation of own diagnostic applications Integration into already existing projects Visualization via HTML Visualization via HMI (copy HMI template from STEP 7 project) STEP 7 project _PROJECT All blocks relevant for the diagnosis, as well as the HMI and web visualization, are already integrated into the project and fully configured. Completed STEP 7 project for instant use (possibly requires adjustment of hardware configuration). Entry-ID: , V1.0, 04/2016 8

9 Siemens AG 2016 All rights reserved 1 Overview 1.4 Documentation guide Table -22 This document provides the user with an overview and, if necessary, with detailed descriptions of the library building blocks. Also, short configuration instructions will be given for the following scenarios: How to use and parameterize the AS-i diagnostic blocks in a project. How to use the prefabricated visualization masks. For a comfortable diagnosis of the AS-i slaves and AS-i masters, the prefabricated WinCC projects in connection with the function block AsiHmiVisu can be used. This block processes the raw diagnosis data of the AS-i masters and feeds them to a panel. It is furthermore possible to process the raw diagnosis data in the user program on your own. The supplied visualization capabilities are optional. In this case, some chapters in this document are irrelevant to you. Those chapters are listed in the following chart: Chapter Chapter 2.3 Overview of HMI template Chapter 2.4 Overview of the web interface Visualization HMI panel Visualization web browser Processing user program Chapter 3.1 The visualization blocks "AsiHmiVisu and "AsiWebVisu Chapter 3.2 The diagnostic block "AsiDiag Chapter 3.4 The raw data of the "AsiDiag Chapter 4 Working with the project example Chapter 5 The WinCC configuration Chapter 6 The HTML configuration Chapter 7 The library " Chapter 8 References As supporting literature, the listed documents from chapter 8 are recommended in any case. Entry-ID: , V1.0, 04/2016 9

10 Siemens AG 2016 All rights reserved 2 Function and effect 2 Function and effect 2.1 Effect scheme Figure 2-1 The following figure schematically illustrates the functionality of the blocks for the AS-i diagnosis: SIMATIC station User program AS-i Master 1 AS-i Master 2 Reading & Saving diagnostic data AsiDiag Processing & Display ASiHmiVisu HMI Panel ASiWebVisu Webbrowser AS-i Master n Master n Master 1 Master 2 Entry-ID: , V1.0, 04/

11 Siemens AG 2016 All rights reserved 2 Function and effect 2.2 Information on the program blocks Overview of the blocks The following figure shows the blocks in their entirety. All blocks listed here are integrated into the library. Figure 2-2 AsiDiag Diagnostic AsiHmiVisu AsiWebVisu AsiWebInterface WWW HMI-Panel Visualization Webbrowser Central diagnostic block Visualization blocks The central block AsiDiag ist used for reading out and evaluating the status of the AS interface slaves and masters. The AsiDiag supplies the status bits for each AS interface line (masters and slaves) and stores the diagnostic data in the instance data block. Per AS-i master, one call of the AsiDiag with a separate instance data block is required. To display the diagnostic data in a WinCC environment on a panel and/or in a web browser, the related visualization blocks can be used optionally. AsiHmiVisu for the visualization on a HMI panel AsiWebVisu for the visualization via web. Note The data exchange between HMI panel and CPU is done via the instance data block of the AsiHmiVisu. With user-defined websites, an instance data block as interface for data exchange is not admissible. Therefore, the web visualization interacts with an external set of tags, which in this example are stored in the global data block AsiWebInterface (see chapter on web blocks ). Web blocks STEP 7 saves the user-defined websites as control DB and DB fragments. In the user program, the command WWW is used for calling up the encoded and Entry-ID: , V1.0, 04/

12 Output Input Siemens AG 2016 All rights reserved 2 Function and effect fragmented data blocks and for the interaction between website and STEP 7 user program. The command WWW is part of the standard library of the TIA portal. Next to the above named diagnostic and visualization blocks, the global data block AsiWebInterface is used to access the CPU tags The presentation in detail AsiDiag The following chart shows the block as LAD presentation: Figure 2-3 Table -21 The parameters have the following meaning: Type Tag Data type Default value masteraddress HW_IO or DINT Meaning L#0 S7-1500: HW-ID of AS-i master S7-x00: Logical address of master module as Long INT e.g. L#1. asiwebdb DINT L#0 Optional web visualization: Number of instance data block of AsiWebVisu. asipaneldb DINT L#0 Optional HMI visualization: Number of instance data block of AsiHmiVisu. masterid INT L#0 Device type of As-i master; The following applies 1: IE/AS-i Link Advanced 2: DP/AS-i (F-)Link, CP343-2 (P), DP/AS-I Link (Adv.) 3: ET 200SP -AS-i master req BOOL 1 Request Bit; on a positive edge at REQ, the block is processed. busy BOOL 0 True, if the block is processed. error BOOL 0 True, if an error occurred. Entry-ID: , V1.0, 04/

13 Siemens AG 2016 All rights reserved 2 Function and effect AsiWebVisu The following chart shows the block in LAD presentation: Figure 2-4 Table 2-2 Type Tag Data type Default value Meaning Input/Out put WebInterface Data typewebi nterfaceda ta L#0 Tag set for data exchange between website and CPU. AsiHmiVisu The following chart shows the block in LAD presentation: Figure 2-5 The block has no parameters WWW command The following figure shows the WWW command in FBD presentation Figure 2-6 Table 2-3 Type Tag Data type Default value Meaning Input CTRL_DB DINT L#0 Number of control data block Output RET_VAL DWORD 0 Contains an error code in case of an error Entry-ID: , V1.0, 04/

14 Siemens AG 2016 All rights reserved 2 Function and effect Calling environment Overview The AsiDiag has to be called in the cyclic OB 1 and is activated by the parameter input req (positive edge). In this, the trigger of the parameter input can be executed cyclically (e.g. through a clock memory) and/or in an error or cyclic interrupt organization block (OB). Activating the AsiDiag via the error or cyclic interrupt OBs has the advantage, that the block will only be processed in certain situations (error or cyclic interrupt). This action saves an unnecessary processing of the diagnostic block on the cyclic process level. Note Activate all AsiDiag already in the start-up OB (OB 100). This ensures a uniform default state of all AsiDiag. Note The error/cyclic interrupt/start-up OB are active for one cycle only; however, the AsiDiag needs more cycles for execution. That is why in these OBs, the block is only initiated (meaning, a positive edge is created at the req input). Further processing is done by the cyclic OB 1. For the visualization, it is sufficient to call up the respective blocks one time in the cyclic process level OB 1. Namely, those are the blocks For the HMI visualization: AsiHmiVisu For the web visualization: AsiWebVisu WWW Performance data Number of AS-i master The visualization requires one AsiDiag per AS-i master. Which master stores its data under which instance data block number is stored internally in lists in AsiHmiVisu or AsiWebVisu. In the AsiHmiVisu, there is room for 255 list entries which means 255 AS-i master or AS-i lines. In the AsiWebVisu, the number of list entries is limited to 20 due to lack of performance. The actual maximum number of AsiDiag in the project strongly depends on the general conditions. These include factors such as CPU used and its computing power Type of FB calls (restrictions on the number of simultaneously running SFB 52/SFB 53 tasks) Maximum OB 1 cycle time Size of the CPUs working memory Entry-ID: , V1.0, 04/

15 Siemens AG 2016 All rights reserved 2 Function and effect Watchdog timer AS-i performance data To prevent the diagnostic FB from hanging in an infinite loop in case of an error, there is a watchdog timer. It is preset to 400ms. If these 400ms are exceeded, the program processing aborts. Per AS-i line, up to 62 slaves can be connected which are addressed with the addresses of 1 (A) - 31 (A) and 1B - 31B. According to the specifications, the update time is 5ms for 31 slaves and 10ms at maximum condiguration. Capacity in load memory The user-defined websites are coded in data blocks, fragmented, and stored in the CPU load memory. The size of the storage space depends on the content of the websites. The internal load memory of the CPU can be increased via pluggable memory cards. Restrictions on reading/writing a data set and command interface Information on the status of the AS-i slaves are requested and read in the library block AsiDiag via data sets, or via the commando interface in the respective master. This is done by the system functions SFB 52 (RDREC; read data set) and SFB 53 (WRREC; write data set). Depending on the CPU type, only a certain number of SFB and therefore AsiDiag calls can be processed simultaneously. The number for simultaneous calls varies between four (for smaller CPUs) and eight (for bigger CPUs). More information can be found in the FAQ with the BID: Note In most cases, there is no particular need for action; if there is, please observe the procedure given in chapter 7.3. Entry-ID: , V1.0, 04/

16 Siemens AG 2016 All rights reserved 2 Function and effect 2.3 Overview of HMI template WinCC provides the possibility to visualize the AS-i network via a panel. Note All functions described in this chapter only work in conjunction with the function blocks AsiDiag AsiHmiVisu NOTICE An error-free visualization is only possible, if 1. For every AS-i master involved, a separate AsiDiag has been created and all AsiDiag have been called up at least once (initialization phase); this can be ensured by calling it up in the start-up OB. 2. For all AS-i masters involved, information (instance data block number and display text) are stored in WinCC The diagnostic screen Layout overview of the AS-i master diagnosis The diagnostic page clearly and graphically displays the status of the configured AS-i masters and their slaves, thus allowing a comfortable diagnostic overview. The data required for this are read via the AsiDiag from the AS-i master and are prepared by the AsiHmiVisu. The image of the AS-i diagnosis is divided into three areas: Figure The meaning of each area is illustrated in the following chart: Entry-ID: , V1.0, 04/

17 Siemens AG 2016 All rights reserved 2 Function and effect Table 2-4 No. Function 1. Selection of the AS-i master; each AS-i master is displayed with its bus. 2. Status of the AS-i master according to AS-i specification. 3. Overview and conditions of the slaves connected to the bus. 4. Menu fields Selecting the AS-i master The selection of the AS-i masters is done via a selection list. The following screenshot shows the list with two example entries: Figure 2-8 In the selection list, only those AS-i masters appear that have previously logged into the AsiHmiVisu via the AsiDiag with their instance data block number. More information can be found in chapter (Initialization phase). Note Please refer to chapter 5 (The WinCC configuration) on how to change the display texts and on how to add additional AS-i masters. Status of AS-i masters Information can be read or written via data blocks or command calls from all AS-i master interfaces. Next to information on connected slaves, the AS-i master also provides separate status flags according to the AS-i specification. The flags of the selected AS-i masters are read and -depending on the statushighlighted in color in WinCC. Figure 2-9 The meaning of each status information is illustrated in the following chart: Table 2-5 Display text Auto-addressing enabled Offline, no cyclic data exchange. Meaning The flag indicates, whether auto-addressing is disabled (Bit = 0) or enabled (Bit = 1) by the user. The flag is set, if the offline phase is active. In the offline phase, the AS-i master does not transmit any cyclic input and output data from or to the slaves. The offline phase is Entry-ID: , V1.0, 04/

18 Siemens AG 2016 All rights reserved 2 Function and effect Display text Ground fault detected AS-i master in configuration mode Auto-addressing executable Slave with address 0 detected Configuration error Meaning generally gone through at start-up only and is finished automatically. The flag is set, if a connection between the AS-i positive lead and earth, or between AS-i negative lead and earth has been detected. The flag is set in configuration mode and reset in protected mode The flag is set, if auto-addressing can be executed (i.e. a failed slave unit can be replaced by a brand new slave unit of the same type, whereby the AS-i address is automatically assigned.). The flag is set, if an AS-i slave with address 0 has been detected The flag is set, if the actual configuration of the slave units at the AS-i cable does not match the set configuration. Status of slaves In the area status of slaves, an overview of the slaves is displayed. A maximum of 62 slaves (31 A-slaves and 31 B-slaves) can be diagnosed. If a slave with address 0 is detected, an additional diagnostic field for address 0 will be displayed. The status of the slaves is read via data sets or command calls from the AS-i masters. With the function Read_Lists_and_Flags and -if required- Read Peripheral Error List, the following information are read from the AS-i master: The list of active AS-i slaves (LAS) The list of detected AS-i slaves (LDS) The list of planned AS-i slaves (LPS) The list of peripheral faults of activated AS-i slaves (LPF) The flags of the AS-i master according to AS-i specification. For the ET 200SP AS-i master, the following lists are read in addition: List of multiple addressing List of failed slaves List of failed slaves List of surplus slaves List of configured ID = A List of actual ID = A Entry-ID: , V1.0, 04/

19 Siemens AG 2016 All rights reserved 2 Function and effect With the help of WinCC, the statuses of the slaves are indicated via various background colors. Figure 2-10 In this, the following attributions apply: Table 2-6 Green Color Yellow Orange Red Gray Purple Dark green Meaning The slave has been recognized, configured and activated. It does not signal peripheral errors. The slave has been recognized, but not configured and activated. The slave signals a peripheral error. The slave is configured, but failed. The slave does not exist and is not configured. A wrong slave has been inserted. This status is not supported by all AS-i masters. It is available, for example, on the ET 200SP AS-i master. The AS-i master has recognized a multiple assignment of this address. This function is not supported by all AS-i masters. This function is available, for example, on the ET 200SP AS-i master. After clicking on the button Legend, this color-coding appears as pop-up window in the WinCC display. Figure 2-11 Entry-ID: , V1.0, 04/

20 Siemens AG 2016 All rights reserved 2 Function and effect For every slave, a detailed description (e.g. article number, location, function) can be stored. By simply clicking on a slave, the stored information as well as the current status will be displayed in clear text in the output field. Figure 2-12 Note Refer to chapter 5.4 (Adjusting the AS-I slaves information) on how to store additional information on slaves. Additional states Next to the states of the AS-i masters and AS-i slaves, errors from the visualization environment are also displayed. This includes messages such as The connection between CPU and visualization interrupted; The CPU is stopped; No data from AsiHmiVisu ; The messages are displayed in clear text in the visualization. The table shows the possible statuses and the cause: Table 2-7 CPU stopped Message text Missing data from the HMI block No connection to CPU Trigger No value change occurs on the meter in the AsiHmiVisu. The AS-i Master has not logged into the AsiHmiVisu or reports an internal error in the AsiDiag. The AsiHmiVisu receives no information or faulty information. The connection between CPU and panel is interrupted. As soon as the CPU stops or the data block of the AsiHmiVisu no longer provides any data, the statuses of the slaves switch to gray. Menu fields The menu field serves to switch languages, to switch screens and to exit runtime. Note The menu field AS-i statistics cannot be selected, if the currently selected AS-i master is a PROFIBUS/ AS-i link or CP (masterid=2). Entry-ID: , V1.0, 04/

21 Siemens AG 2016 All rights reserved 2 Function and effect The statistics screen Layout overview of the AS-i master statistics The statistics screen displays the error counters of the AS-i masters and AS-i slaves. The error counters of the AS-i slaves are visible only with the ET 200SP AS-i master. The values are read via the AsiDiag from the AS-i master and are processed by the AsiHmiVisu. The reset buttons reset all error counters of the selected AS-i masters back to zero. Figure 2-13 Note Further information on the error counters can be found in the manual of the AS-i master. Entry-ID: , V1.0, 04/

22 Siemens AG 2016 All rights reserved 2 Function and effect 2.4 Overview of the web interface The combination of HTML and Javascript provides the possibility to create userdefined websites for the PROFINET CPUs and, via them, to diagnose the AS-i network web-based and to execute online functions. All files needed for the presentation (HTML, images, Javascript, etc.) are converted to control DBs and fragmented DBs. The command WWW provides a cyclic update of the website. Note The following blocks are required for all functions described in this chapter: AsiDiag AsiWebVisu WWW All control DBs and fragmented DBs of the websites AsiWebInterface NOTICE An error-free visualization is only possible, if 1. For every AS-i master involved, a separate AsiDiag has been created and all AsiDiag have been called up at least once (initialization phase); this can be ensured by calling it up in the start-up OB. 2. For all AS-i master involved, information (instance data block number and display text) are stored in the XML file. Entry-ID: , V1.0, 04/

23 Siemens AG 2016 All rights reserved 2 Function and effect The diagnostic window Layout overview of the AS-i master diagnosis The diagnostic page clearly and graphically displays the status of the configured AS-i masters and their slaves, thus allowing a comfortable diagnostic overview. The data required for this are read from the AS-i master via the AsiDiag, processed via the AsiWebVisu and made available for the website via the interface AsiWebInterface. The image of the AS-i web diagnosis is divided into three areas: Figure The meaning of each area is illustrated in the following chart: Table 2-8 No. Function 1. Selection of the AS-i master; each AS-i master is displayed with its bus. 2. Status of the AS-i master according to AS-i specification. 3. Overview and conditions of the slaves connected to the bus. 4. Menu fields Entry-ID: , V1.0, 04/

24 Siemens AG 2016 All rights reserved 2 Function and effect Selecting the AS-i master The selection of the AS-i master is done via a selection list and is transferred to the CPU via the adjacent button. The current AS-i master is displayed in a text field. The following screenshot shows the list: Figure 2-15 Status of AS-i master Via a data set, information on the AS-i master interface can be read or written. Next to information on connected slaves, the AS-i master also provides separate status flags according to the AS-i specification. The flags of the selected AS-i masters are read and -depending on the statushighlighted in color in the web interface. Figure 2-16 Status of slaves The meaning of every status information corresponds with those of the HMI visualization (see chart 2-6). In the area status of slaves, an overview of the configured slaves is displayed. A maximum of 62 slaves (31 A-slaves and 31 B-slaves) can be diagnosed. If a slave with address 0 is detected, an additional diagnostic field for address 0 will be displayed. The status of the slaves is read via a data set from the AS-i master. With the function Read_Lists_And_Flags and, if required, Read Peripheral Error List, the following information are read from the AS-i master: The list of active AS-i slaves (LAS) The list of detected AS-i slaves (LDS) The list of planned AS-i slaves (LPS) The list of peripheral faults of the activated AS-i slaves (LPF) The flags of the AS-i master according to AS-i specification. For the ET 200SP AS-i master, the following lists are read in addition: Entry-ID: , V1.0, 04/

25 Siemens AG 2016 All rights reserved 2 Function and effect List of multiple addressing List of failed slaves List of failed slaves List of surplus slaves List of configured ID = A List of actual ID = A With the help of Javascript, the statuses of the slaves are indicated via various background colors. Figure 2-17 The color-coding corresponds to the color-coding of the HMI visualization (see chart 2-7). For every slave, a detailed description (e.g. article number, location, function) can be stored. By simply clicking on a slave, the stored information as well as the current status will be displayed in clear text in the output field below the area status of slaves. Figure 2-18 Note Refer to chapter 6.3 (Adjusting the AS-I slaves information) on how to store additional information on slaves. Menu fields If the CPU or the AS-i master can no longer be accessed, the statuses of the slaves switch to gray. The menu field serves for switching pages and languages. Entry-ID: , V1.0, 04/

26 Siemens AG 2016 All rights reserved 2 Function and effect The control panel Note The control panel is only operable with a CM AS-i master for ET 200SP. Layout overview of the AS-i control panel For the ET 200SP AS-i master, the TIA portal offers a control panel in online mode, to execute functions directly from the portal. This control panel is recreated in the web interface. The following functions are available: Change of operation mode Acceptance of slave configuration Change of AS-i slave address Via the interface AsiWebInterface, the function commands are transmitted to the user program, processed, and sent to the AS-i master. The image of the AS-i control panel is divided into three areas: Figure 2-19 The meaning of each area is illustrated in the following chart: Table 2-9 No. Function 1. Status of AS-i master and change of operating mode 2. Acceptance of slave configuration 3. Change of AS-i slave address Entry-ID: , V1.0, 04/

27 Siemens AG 2016 All rights reserved 2 Function and effect The statistics screen Note The statistics overview is not operable with a PROFIBUS/ AS-i link or CP (P). Layout overview of the AS-i master statistics The statistics screen displays the error counters of the AS-i masters and AS-i slaves. Figure 2-20 The values are read from the AS-i master via the AsiDiag, processed via the AsiWebVisu and made available for the website via the interface AsiWebInterface. The reset buttons reset all error counters of the selected AS-i masters back to zero. Note Further information on the error counters can be found in the manual of the AS-i master. Entry-ID: , V1.0, 04/

28 Siemens AG 2016 All rights reserved 2 Function and effect 2.5 Hardware and software components Software Control These program blocks apply to STEP 7 V13 SP 1 Update 7 For this example, the following code packages are provided: S7_1500_CODE_TIAV13.zip: This package contains the blocks/ the project for a SIMATIC S from FW 1.7 onwards S7_x00_CODE_TIAV13.zip: This package contains the blocks/ the project for a SIMATIC S7-300 from FW 3.2 onwards SIMATIC S7-400 from FW 6.0 onwards Visualization The visualization screens of WinCC were optimized for the operating device TP700 Comfort 7 (800 x 480 pixel). The user-defined websites were designed for Internet Explorer 8 and Firefox 11. Javascript is used for interaction on the website. To use the web visualization properly, Javascript needs to be activated in your browser. AS-i master The following AS-i masters are supported: DP/AS-i Link 20E (6GK AA10) DP/AS-i LINK Advanced single master (6GK BA10) DP/AS-i LINK Advanced double master (6GK BA20) DP/AS-i F-Link (3RK CD10 / 3RK CD10) IE/AS-i LINK single master (6GK AB10) IE/AS-i LINK double master (6GK AB20) CP (6GK AH01-0XA0) CP 343-2P (6GK AH11-0XA0) ET 200SP AS-i master (from FW 1.1 onwards) (3RK7137-6SA00-0BC1) Entry-ID: , V1.0, 04/

29 Siemens AG 2016 All rights reserved 3 The program blocks in detail 3 The program blocks in detail This chapter provides a detailed description of the library blocks in terms of core functionality and internal operation sequences. Also, content and structure of the diagnostic information read from the AS-i master are explained. This knowledge is vital for working without visualization. 3.1 The visualization blocks AsiHmiVisu and AsiWebVisu Note The visualization blocks AsiHmiVisu and AsiWebVisu are identical in their functionality. Due to their intended use ( AsiHmiVisu for the HMI panel and AsiWebVisu for the web interface) they only differ in the type of data processing. The function blocks AsiHmiVisu and AsiWebVisu have two important tasks: Management of configured AS-i master with the corresponding instance data block number. Supply of data for the images of the AS-i master visualization in WinCC and in the web browser. The management of the AS-i masters For the storage of diagnostic information and the status on itself and on its connected slaves, every AS-i master needs the AsiDiag with a separate instance data block. For the visualization in WinCC or in the web browser, the AsiHmiVisu or AsiWebVisu accesses the respective instance data block, reads the information and copies it to its own instance data block. For the attribution AS-i master instance data block number the visualization blocks manage a master list, to which all AsiDiag logon with the respective instance data block number. The following screenshot displays the master list with four logged on AsiDiag blocks: Figure 3-1 The master list only displays the position of the respective data block number. It does not provide information on the AS-i master itself. In this, the type (IE/AS-i Link, PB/AS-i Link, CP 343-2, ET 200SP) is stored in the respective asidiag instance data block via the input parameter masterid. Entry-ID: , V1.0, 04/

30 Siemens AG 2016 All rights reserved 3 The program blocks in detail Using this list, WinCC and the web page create the display texts of the selection list for the AS-i master diagnostic screen (see chapter 5.3 Adjusting the AS-i master selection list as well as chapter 6.2 Adjusting the AS-i master information). Note The positions on the master list determine the sequence of the AS-i masters on the selection list in the visualization interfaces. The AS-i master that has logged into the master list first, also appears in the first position on the selection list. Data supply of the visualization screens (HMI, Web) The second task of the visualization blocks is to supply the visualization screens with the desired data. On the visualization screens, the user has the possibility via a selection list to select an AS-i master that has been configured in STEP 7. Depending on from which AS-i master data is required, the raw information is taken from the respective AsiDiag instance data block in the respective visualization block and is subsequently processed for the display. Reset after CPU restart For the removal of old data from the instance data blocks of the AsiHmiVisu and AsiWebVisu blocks, the block properties of STEP 7 are relied upon. Via the remanence behavior, it can be determined, if the instance data shall be reset to load value (not remanent) after every time, the main supply is switched on or switched off and after every time, the CPU has changed from STOP to RUN mode, or if the data shall be kept (remanent). Via the access mode standard of the superordinate function block, only one collective configuration of all instance data is possible. Deactivate the corresponding option box in the properties of the instance data block. Figure 3-2 Entry-ID: , V1.0, 04/

31 Siemens AG 2016 All rights reserved 3 The program blocks in detail Process The following procedure shows the visualization, using the example of an HMI panel. Figure 3-3 The AsiDiag logs into the AsiHmiVisu one time. The instance DBno is saved in a free position of the master list. WinCC fills the selection list analogous to the master list of the AsiHmiVisu For every instance DBno involved, there is a display text stored in WinCC; the order of the selection list corresponds to that of the master list On the panel, an AS-i master is selected from the selection list The panel transmits the position to the AsiHmiVisu AsiHmiVisu identifies the according instance DBno from the master list Master/selection list are identical in terms of the order of the AS-i masters AsiHmiVisu reads the raw data from the detected instance DB Slave statuses and master flags are contained in this; they are read (a)cyclically by the AsiDiag AsiHmiVisu processes the data for WinCC Statuses of slaves and flags are displayed. Entry-ID: , V1.0, 04/

32 Siemens AG 2016 All rights reserved 3 The program blocks in detail 3.2 The diagnostic block AsiDiag The function block AsiDiag has two core functions: Organization of own initialization. The AS-i master logs into the visualization blocks, if desired. Reading of diagnostic information and flags from the AS.i master. The read data are processed, assorted, and stored in a separate instance data block in the AS-i master. As every AS-i master supplies different data, it is mandatory to assign a separate instance data block of the AsiDiag to every AS-i master. The initialization phase The AS-i master is initialized once after calling a block. This is necessary for a later processing for the WinCC/web display as well as for reading the diagnostic information. If a visualization is desired, the AsiDiag logs into the master list of the visualization block in this phase, by storing its instance data block. The following agreement applies: Table 3-1 Input parameters Value Reaction of the AS-i master block AsiWebDB >0 Login to the master list of AsiWebVisu. AsiWebDB 0 No login to AsiWebVisu ; a visualization via web is not desired. AsiHmiDB >0 Login to the master list of AsiHmiVisu. AsiHmiDB 0 No login to AsiHmiVisu ; a visualization via the HMI panel is not desired. Entry-ID: , V1.0, 04/

33 Siemens AG 2016 All rights reserved 3 The program blocks in detail The following chart outlines this phase: Figure 3-4 Skip initialization phase yes As-i Master initialized? no Master list in AsiWebVisu idbnr Entry into the master list of AsiWebVisu yes IN Parameter AsiWebDB >0 Master list in AsiHmiVisu idbnr Entry into the master list of AsiHmiVisu yes IN Parameter AsiHmiDB >0 Reading the diagnostic information The requirement for reading the diagnostic data is the initialization phase and the statement of the type of the AS-i master via the input parameter masterid. There are significant differences between the AS-i masters in how they read diagnostic information and flags from the AS-i master. With the IE/AS-i link ( masterid = 1) and ET 200SP AS-i master ( masterid =3), the reading is done via a single read data set command (data set number 84) bzw. (Data set number 92). PROFIBUS/ AS-i link and CP (P) ( masterid = 2) have a command interface by which acyclic services are processed. The command interface is accessed via the commands read data set and write data set and with data set number 2. Note With the PROFIBUS/ AS-i link or CP (P), this sequence does not have to be executed separately in the user program, but can also be done via the block ASI-CTRL. This block processes the command protocol independently and also allows the parameterization on SIMATIC AS-i masters as well as the reading of information data. Notes on this can be found here: The ASI_CTRL is already integrated into the AsiDiag. Note Another call of the block ASI_CTRL in the rest of the user program is not allowed, because the commands overwrite each other. The AS-i master is addressed via the input parameter masteraddress, which is parameterized with the according hardware identifier. The content of the data set is stored in the instance data block of the AS-i master. Entry-ID: , V1.0, 04/

34 Siemens AG 2016 All rights reserved 3 The program blocks in detail Reset after CPU restart For the removal of old data from the instance data blocks AsiDiag, the block properties of STEP 7 are relied upon. Via the remanence behavior, it can be determined, if the instance data shall be reset to load value (not remanent) after every time, the main supply is switched on or switched off and after every time, the CPU has changed from STOP to RUN mode, or if the data shall be kept (remanent). Via the access mode standard of the superordinate function block, only one collective configuration of all instance data is possible. Deactivate the corresponding option box in the properties of the instance data block. Figure 3-5 The watchdog timer Processing conditions To prevent the AsiDiag from hanging in an infinite loop in case of an error, there is a watchdog timer. If, due to an error, the program freezes during the processing and the defined delay time (400ms) elapses, the program processing is aborted. This action prevents a program from being stuck in an operation sequence. Because one cycle does not suffice for the processing of the AsiDiag, an integration of the AsiDiag in the OB 1 is mandatory. The function block is equipped with a req input parameter, which ensures program processing. It must be triggered by a positive edge, otherwise, the block will not be processed. In an error or cyclic interrupt OB, this can be done either manually or via a time trigger. Note Activate all AsiDiag already in the start-up OB (OB 100). This ensures a uniform default state of all AsiDiag. Entry-ID: , V1.0, 04/

35 Siemens AG 2016 All rights reserved 3 The program blocks in detail 3.3 The raw data of the AsiDiag To process the diagnostic raw data in the user program, it is necessary to know, which information is provided by the system are where it can be found in the instance data block of the AsiDiag Overview of diagnostic raw data Diagnostic data set The statuses of the slaves and of the AS-i masters are read via data sets or command calls from the AS-i masters. Depending on the AS-i master, the length of the read diagnostic data varies: Table 3-2 AS-i master CM AS-i Master ST for ET 200SP PROFIBUS/ AS-i Link, CP (without LPF) PROFIBUS/ AS-i Link, CP (LPF) The flags of the AS-i master according to AS-i specification. 88 bytes 48 bytes 14 bytes 2 bytes Data length With the function Read_Lists_And_Flags and, if required, Read Peripheral Error List, the following entries are provided: The list of active AS-i slaves (LAS) The list of detected AS-i slaves (LDS) The list of planned AS-i slaves (LPS) The list of peripheral faults of activated AS-i slaves (LPF) The flags of the AS-i master according to AS-i specification. For the ET 200SP AS-i master, the following lists are read in addition: List of multiple addressing List of failed slaves List of failed slaves List of surplus slaves List of configured ID = A List of actual ID = A Every slave occupies one bit per list, therefore, one list occupies 8 byte of the data read. Entry-ID: , V1.0, 04/

36 Siemens AG 2016 All rights reserved 3 The program blocks in detail Order of slaves in the lists With the IE/AS-i Link and CM AS-i Master ST the slaves are addressed in ascending bit address order. The following attribution applies: Table 3-3 Slave no Address (Byte x List start) 0A Byte x, Bit 0 1A Byte x, Bit 1 2A Byte x, Bit 2 8A Byte (x+1), Bit 0 9A Byte (x+1), Bit 1 10A Byte (x+1), Bit 2 0B Byte (x+4), Bit 0 1B Byte (x+4), Bit 1 2B Byte (x+4), Bit 2 8B Byte (x+5), Bit 0 9B Byte (x+5), Bit 1 10B Byte (x+5), Bit 2 With all other AS-i masters, the slaves are addressed in descending bit address order. The following attribution applies: Table -34 Slave no 0A Byte x, Bit 7 1A Byte x, Bit 6 2A Byte x, Bit 5 8A Byte (x+1), Bit 7 9A Byte (x+1), Bit 6 10A Byte (x+1), Bit 5 0B Byte (x+4), Bit 7 1B Byte (x+4), Bit 6 2B Byte (x+4), Bit 5 8B Byte (x+5), Bit 7 9B Byte (x+5), Bit 6 10B Byte (x+5), Bit 5 Address (Byte x List start) Entry-ID: , V1.0, 04/

37 Siemens AG 2016 All rights reserved 3 The program blocks in detail Note The exact bit assignment of the lists is described in detail in the manual of the respective AS-i master. Master flags The flags of the AS-i master occupy a maximum of two bytes, according to AS-i specification. Not every AS-i master provides 12 flags (2 byte = 16bit). The chart lists the most common flags: Table 3-5 Flag KONFIG_OK LDS_0 AUTO_ADDR_ASSIGN AUTO_ADDR_AVAIL OPERATION MODE NORMAL_OPERATION APF (AS-i Power Fail) OFFLINE_READY PERIPHERY_OK DATA_EXCHANGE_ ACTIVE OFFLINE AUTO_ADDR_ENABLE MP (Master_Power_on) GROUND FAULT EPROM_OK Description The flag is set, if the configured SET configuration matches the ACTUAL configuration. The flag is set, if an AS-i slave with address 0 has been detected The flag is set, if auto-addressing is enabled. E.g., AUTO_ADDR_ENABLE = 1 is connected to the AS interface, not a false AS-i slave. The flag is set, if auto-addressing is executed, as soon as a slave with valid configuration is connected to address zero. The flag is set in configuration mode and reset in protected mode. The flag is set, if the AS-i master is in protected mode. The flag is set, if the voltage in the AS-i cable is too low, or if a power down has been detected during a data transmission. The flag is set, if the offline phase is active. The flag is set, if no AS-i slave signals a peripheral error. The flag is set, if cyclic data traffic is going on during normal operation. The flag is set, if the operation mode OFFLINE is supposed to be active, or if it is active already. The flag indicates, whether auto-addressing is disabled (Bit = 0) or enabled (Bit = 1) by the user. The flag is set after switching on the supply voltage. The flag is set, if the AS-i cable is ground-faulted. The flag is set, if the EPROM of the device is okay. Note The exact bit assignment of the flags is described in detail in the manual of the respective AS-i master. Entry-ID: , V1.0, 04/

38 Siemens AG 2016 All rights reserved 3 The program blocks in detail Overview of statistic raw data Error counter AS-i line The error counter of the AS-i line for the statistic display is read via a data set from the CM AS-i master ST or IE/AS-i link. The data set read AS-i master error counter reads AS-i line-specific error counters. The count starts from zero each time, the device is started up. Table 3-6 AS-i Power Fail Ground fault Slave failure Information Missing slave-telegram Faulty slave-telegram Peripheral error Protocol error Faulty master telegram Master telegrams sent Double address available (only CM AS-i master ST) Duplicate (only CM AS-i master ST) Meaning The AS-i voltage supply is missing, too low, or not stable. The slave was connected to the frame ground (earth) from the AS-i cable A or B. After multiple successive timeouts, the slave has been signed out from the list of activated AS-i slaves (LAS). Absence of slave reply from an existing slave. The slave reply of a slave is garbled or distorted. Replying to Read_Status, the slave signals Peripheral Fault. Error in data transfer after CTT1 5, e.g. Wrong or missing toggle-bit. The AS-i master detects errors in own send-telegram. Number of master telegrams This counter counts all telegrams sent by the master, regardless of whether a slave reply has been received or not. By dividing the absolute values of the error counters by the number of master telegrams, the percentage error and therefore the error frequency can be calculated. The total number of master telegrams is calculated as follows: MT_CNT_TOTAL = (MT_CNT_HIGH x MT_CNT_BASE) + MT_CNT_LOW The error count starts from zero, each time, the device is started up. Multiple address assignment available Bit 0 is set (= 1), if at least one double address has been detected. Double address detected For multiple assignments of AS-i addresses, the respective bit is set Error counter AS-i slaves The error counter of the AS-i slave for the statistic display is read via multiple data sets from the CM AS-i master ST. The data set read AS-i slave error counter reads the slave-specific error counters. Table -37 Slave failure Information Meaning After multiple successive timeouts, the slave has been signed out from the list of activated AS-i slaves (LAS). Entry-ID: , V1.0, 04/

39 Siemens AG 2016 All rights reserved 3 The program blocks in detail Information Missing slave telegram Faulty slave telegram Peripheral error Protocol error Faulty master telegram Master telegrams sent Meaning Absence of slave reply from an existing slave. The slave reply of a slave is garbled or distorted. Replying to Read_Status, the slave signals Peripheral Fault. Error in data transfer after CTT1 5, e.g. Wrong or missing toggle-bit. The AS-i master detects errors in own send-telegram. Number of master telegrams This counter counts all telegrams sent by the master, regardless of whether a slave reply has been received or not. By dividing the absolute values of the error counters by the number of master telegrams, the percentage error and therefore the error frequency can be calculated. The total number of master telegrams is calculated as follows: MT_CNT_TOTAL = (MT_CNT_HIGH x MT_CNT_BASE) + MT_CNT_LOW The error count starts from zero, each time, the device is started up The data structure in the instance data block For the storage of the AS-i master diagnostic data in the function block AsiDiag, multiple areas have been declared with the help of data types. This was done due to mismatches in the read data length and in the bit assignment: Table -38 Tag statflagsasislavedetailversionie statflagsasislavedetailversionpb statperipheryfaultasislaveversionpb statflagsasislavedetailversionet 200SP Data type typeasiflagsdetailversionstandard typeasiflagsdetailversionid2 typeasislaveperipheryfaultversionpb typeasiflagsdetailversionid3 Entry-ID: , V1.0, 04/

40 Siemens AG 2016 All rights reserved 3 The program blocks in detail Structure of statflagsasislavedetailversionie With the IE/AS-i link, all lists required for the diagnosis (LAS, LDS, LPS, LPF and AS-i master flags) are read with a single call ( Read_Lists_And_Flags ) and are stored in the data area statflagsasislavedetailversionie. The following figure shows the structure of the 36 Bytes for statflagsasislavedetailversionie : Figure The following table illustrates the correlation: Table 3-9 Number Name Description 1 active List of active slaves (LAS) 2 known List of detected slaves (LDS) 3 configured List of planned slaves (LPS) 4 peripheriefault The list of peripheral faults of activated AS-i slaves (LPF) 5 Master Flags Entry-ID: , V1.0, 04/

41 Siemens AG 2016 All rights reserved 3 The program blocks in detail Structure of statflagsasislavedetailversionpb With the PROFIBUS/ AS-i link and CP (P), the lists required for the diagnosis (LAS, LDS, LPS and AS-i master flags) are read via the command Read_Lists_And_Flags and are stored in the data area statflagsasislavedetailversionpb. The following figure shows the structure of the 32 Bytes for statflagsasislavedetailversionpb : Figure The following table illustrates the correlation: Table -310 Number Name Description 1 active List of active slaves (LAS) 2 known List of detected slaves (LDS) 3 configured List of planned slaves (LPS) 4 MasterFlags Entry-ID: , V1.0, 04/

42 Siemens AG 2016 All rights reserved 3 The program blocks in detail Structure of typeasislaveperipheryfaultversionpb With the PROFIBUS/ AS-i link and the CP (P), the missing LPF list is read separately via the command Read_Peripheral Error List and are stored in the data area statperipheryfaultasislaveversionpb. Figure The following table illustrates the correlation: Table 3-11 Number Name Description 1 peripheryfault List of active slaves (LAS) Entry-ID: , V1.0, 04/

43 Siemens AG 2016 All rights reserved 3 The program blocks in detail Structure of typeasiflagsdetailversionid3 With the CM AS-i master ST, all lists required for the diagnosis are read with a single call ( Read_Lists_And_Flags ) and stored in the data area statflagsasislavedetailversionet 200SP. The following figure shows the structure of the 88 Bytes for statflagsasislavedetailversionet 200SP : Figure Entry-ID: , V1.0, 04/

44 Siemens AG 2016 All rights reserved 3 The program blocks in detail The following table illustrates the correlation: Table 3-12 Number Name Description 1 Master Flags 2 active List of active slaves (LAS) 3 failed List of failed slaves 4 wrong List of wrongly inserted slave 5 known_configured List of surplus slaves 6 ma List of multiple addressing 7 peripheryfault The list of peripheral faults of activated AS-i slaves (LPF) 8 configuredid List of configured ID = A 9 actualid List of actual ID = A 10 known List of detected slaves (LDS) 11 configured List of planned slaves (LPS) Entry-ID: , V1.0, 04/

45 Siemens AG 2016 All rights reserved 4 The project example _PROJECT 4 The project example _PROJECT This chapter shows, how the supplied STEP 7 project _PROJECT can be used without the need for modification. 4.1 Addresses of hardware components Figure 4-1 The SIMATIC station, the panel and the AS-i components have been configured with the following addresses: Entry-ID: , V1.0, 04/

46 Siemens AG 2016 All rights reserved 4 The project example _PROJECT 4.2 Using the STEP 7 project Components of the STEP 7 project The STEP 7 project _PROJECT contains the following elements: Blocks to comfortably provide diagnostic information of one or more AS-i master systems for further evaluations in the STEP 7 user program and for the display on an HMI panel or web browser. HMI templates to visualize the diagnostic information on an HMI panel. User-defined websites to visualize the diagnostic data via the web server of the CPU. This project can be found in the download area of this document (see chapter 9). Installation of STEP 7 project Note In the following installation manual, it is assumed, that you use the STEP 7 project without any modifications. Changes in the hardware configuration and to the addresses require an adjustment of the WinCC projects (see chapter 5). To use the STEP 7 project _PROJECT, the following steps have to be carried out: 1. Adjust your network according to the guidelines chapter 4.1 (Addresses of hardware components). 2. Connect one AS-i network per AS-i master with any AS-i slave. 3. If you do not configure your AS-i slaves in the project directly, the ACTUAL configuration has to be adopted as SET configuration with all AS-i masters. The procedure is described in the respective manual (see chapter 8 References). 4. Unzip the ZIP archive S7_x00_CODE_TIAV13.zip or S7_1500_CODE_TIAV13.zip to a directory of your choice. 5. Open the TIA project in the directory _PROJECT. 6. Check the module address or hardware identifier of your AS-i masters. If they differ from the configured address, the block parameter masteraddress of the AsiDiag has to be adjusted on every call in the organization blocks. 7. In the project tree, select the controller and load the project to the controller. 8. In the project tree, select the panel and load the project into the component or start the simulation.. Entry-ID: , V1.0, 04/

47 Siemens AG 2016 All rights reserved 4 The project example _PROJECT 4.3 Operating the STEP 7 project In this project example, due to the connection of both, the AsiWebDB and the AsiHmiDB input, both visualization types are activated. Visualization via the HMI panel By loading the HMI project to the panel, the runtime with the start screen is automatically started up. Figure 4-2 The AS-i master configured in this project have logged into the master list of the AsiHmiVisu and appear in the selection list. Figure 4-3 Visualization via web Select an AS-i master. The diagnostic information of the selected AS-i master will be graphically displayed at the next update. All the files required for the visualization have already been converted to data blocks and, upon loading the controller, transmitted to the CPU memory. Enter the address into a web browser. The website of the CPU opens. Log on with the following data: User name: admin Password: asi Open the web visualization via CustomerPages > Entry-ID: , V1.0, 04/

48 Siemens AG 2016 All rights reserved 5 The WinCC configuration 5 The WinCC configuration To allow a diagnosis of your own AS-i environment, it is necessary to make adjustments in WinCC. This chapter describes the required, individual adjustment of the HMI templates and the configuration steps in WinCC. 5.1 Using visualization images To allow a diagnosis of your own AS-i environment, it is necessary to make adjustments in WinCC. Connection between CPU and panel The tag access between CPU and panel is carried out via an HMI connection. The HMI connection is already contained in the supplied project and can be viewed in the tabular section of the network view on the tab Connections. In the table, check the connection parameters and -if necessary- change the address parameters in the inspector window to the requirements of your project. Figure 5-1 Adjustment of the area pointer With the area pointer of WinCC, it can be discovered, if the connection to the CPU is established or interrupted. Under Connections, open the tab Area pointer. Under coordination, change the address of the tags as follows: %DB <instance data block number of your AsiHmiVisu >.DBW738 Figure 5-2 Entry-ID: , V1.0, 04/

49 Siemens AG 2016 All rights reserved 5 The WinCC configuration Coordinating the tag access The images for displaying the AS-i line status are controlled via the tags from the instance data block of the AsiHmiVisu. The make the project as flexible as possible for the user, the tags are not directly linked to an address (e.g. DB2.DBW2), but are instead linked indirectly via variable multiplexing. This means, that the tag address is adjusted to the runtime in relation to the value of the index variable AsiHmiVisuDB. Tag multiplexing has the advantage, that the instance data block number of the AsiHmiVisu can be flexibly determined by the user. Instead of adjusting all WinCC tags, it suffices to change the index tag only. For this, open the tag list. Select the index tag AsiHmiVisuDB and, in the tag properties, enter the number of your instance data block for the AsiHmiVisu as start value. Figure 5-3 Entry-ID: , V1.0, 04/

50 Siemens AG 2016 All rights reserved 5 The WinCC configuration 5.2 Adjusting the AS-i master selection list In the next step, the WinCC project will be expanded by the number of selectable AS-i master. This requires an adjustment in several places of the project. The selection of the AS-i masters is done via a selection list. Here, all AS-i masters are displayed, whose AsiDiag has logged into the master list of the AsiHmiVisu. NOTICE An error-free visualization is only possible, if 1. For every AS-i master involved, a separate AsiDiag has been created and all AsiDiag have been called up at least once (initialization phase); this can be ensured by calling it up in the start-up OB). 2. For all AS-i masters involved, information (instance data block number and display text) are stored in WinCC Changes to the interface Per default settings, the selection list can manage up to eight AS-i master. If more devices are managed, the limits have to be adjusted. Figure The list position entries Every AS-i master is represented by a tag ( AsiDiagInstDBMasterx ), which points to a position in the master list of the AsiHmiVisu. As described in chapter 3.1, the AS-i master blocks log into the master list via their instance data block number. The list position tags in WinCC refer to this information. The assignment between list position tags in WinCC and the master list needs to be as follows: Entry-ID: , V1.0, 04/

51 Siemens AG 2016 All rights reserved 5 The WinCC configuration Figure 5-5 Masterliste AsiHmiVisu Angemeldete AS-i Master Variablen in WinCC Listenplatzvariablen For the first positions in the master list, the according tags have already been integrated into WinCC. If you have more AS-i master, you need to create more list position tags. Open HMI tags in WinCC. For a better overview, sort the column Name alphabetically by clicking on the column header. By this, the five list position tags are listed in a row. Figure 5-6 The easiest way to insert new list position tags is the following one: Select the line with the already configured tags and duplicate it with Copy&Paste. WinCC adds the tag at the end of the tag chart and automatically designates it with the next sequence number. All you have to do is to increment the address by two further bytes. Figure 5-7 You also have the possibility to create a new tag. Please note that the tag name corresponds to the form AsiDiagInstDBMasterx and that the tag address refers to the next list position in the master list. Entry-ID: , V1.0, 04/

52 Siemens AG 2016 All rights reserved 5 The WinCC configuration Adjusting the text display of the selection list Functional diagram The display texts of the AS-i master in the selection list are dynamically managed via the text lists Master and Master_Name. While the order of the selection list is determined via the master text list, the text list Master_Name manages the fitting display text for every occurring instance data block number. Behind every line of the Master text list, there is the WinCC tag AsiDiagInstDBMasterx, which references to an entry of the master list of the AsiHmiVisu and therefore contains the instance data block number as information. With the text list Master_Name, the fitting display text is output for every occurring instance data block number. Both text lists are dynamically interconnected between each other and, during runtime, provide the display of the AS-i master in the correct order and the correct text in the selection list. Example: Diagnostic data of an IE/AS-i link are to be read and displayed. For this, an AsiDiag with instance data block number 7 has been called in the OB 1 and parameterized accordingly. Figure 5-8 The block is processed by a positive flank at the req input; it goes through the initialization phase and first logs into the master list of the AsiHmiVisu with the instance data block number 7. Position 1 of the master list has thus been occupied by the number 7. In the tag chart of WinCC, tags have been defined for the first positions of the AsiHmiVisu master list ( AsiDiagInstDBMaster1...6 ), which refer to the respective address of the master list (Position 1...6). For this example, the HMI tag AsiDiagInstDBMaster1 contains the instance data block number of the IE/AS-i link ( 7 ). By internal linking, the text lists Master and Master_Name allow finding the fitting display text. Entry-ID: , V1.0, 04/

53 Siemens AG 2016 All rights reserved 5 The WinCC configuration Figure 5-9 Platz in der Auswahlliste 0: Platz 1 Variable AsiDiagInstDB1 1: Platz 2 Variable AsiDiagInstDB2 Variable AsiDiagInstDB1 = 7 Anzeigetext in der Auswahlliste: IE/Asi Link Integration of additional AS-i masters into the selection list The text list Master defines the number of AS-i masters appearing in the selection list. Accordingly, every AS-i master must have its own entry in the text list. In case you have less AS-i masters, redundant entries have to be deleted. With more AS-i masters, the list has to be expanded. For this, open the text list Master. Figure 5-10 Entry-ID: , V1.0, 04/

54 Siemens AG 2016 All rights reserved 5 The WinCC configuration To add additional AS-i masters, select the last entry in the text list, duplicate it via Copy&Paste and increment the entry under Value. The column Value corresponds to the order in the selection list and at the same time reflects the list positions in the master list of the AsiHmiVisu. Every line of the text list is linked with a tag of the type AsiDiagInstDBMasterx, which, as mentioned, represents a list position of the master list and contains the instance data block number of the logged in AS-i master as information. Select the column Text in the line just inserted and assign the next available list position tag. Figure 5-11 Defining the text display for the selection list In the user program of STEP 7, an AsiDiag call with a separate instance data block is required for every AS-i master. For all AS-i master, write down the respective number of the instance data block generated by STEP 7. Now, open the text list Master_name. Here, the instance data block numbers are assigned to the text to be displayed. In the column Value, correct the number and enter the respective display text into Text. Figure 5-12 For further entries, select an empty line and add new entries via the context menu. The column Value is automatically incremented by WinCC. Entry-ID: , V1.0, 04/

55 Siemens AG 2016 All rights reserved 5 The WinCC configuration 5.3 Adjusting the AS-i slaves information Similar to the AS-i master, user-defined information can also be stored for the AS-i slaves. During runtime, they appear in an output field by clikcing with the mouse on a slave. For this, a main list Slave_Description and several slave sublists Slave_NW_X are configured in WinCC. For the slaves of an AS-i master, the sublists manage the information. The text list Slave_Description coordinates the sublist of the AS-i slaves belonging to an AS-i master (referenced via its instance data block number). Both text lists are dynamically linked with each other and provide the display of the AS-i slave information during runtime. Accordingly, every AS-i master, whose slaves are to display information, must have its own entry in the text list Slave_Description. Changes in the main list Open the text lists under Text and graphic lists and select the text list Slave_Description. For two AS-i lines, the entries in the main list have already been defined and the slave sublists have been created. Should you have less AS-i masters, you can delete the redundant entries. With more, the list has to be expanded or corrected. Correct the column Value. For this, use the numbers of the instance data blocks for the AS-i masters from your STEP 7 project. Figure 5-13 For further entries, select the last entry and add additional entries via Copy&Paste. Adjust the column Value. If you want to use an already existing slave sublist for this AS-i master as well, select it in the column Text. Otherwise, leave the Text column as it is, since a new slave sublist has to be created first. Inserting a new slave sublist For a new slave sublist, switch to the text list overview and select the last slave sublist Slave_NW_x. Insert a new list via Copy&Paste. WinCC automatically increments the index x. Switch back to the Slave_Description and change the entry column in the line you just added. Entry-ID: , V1.0, 04/

56 Siemens AG 2016 All rights reserved 5 The WinCC configuration Changes in the sublists Per AS-i master, one sublist can be created to save user-defined information about the AS-i slaves. After specification, an AS-i line can manage up to 62 slaves (among which 31 are A slaves and 31 B slaves). Since in the column Value, WinCC only expects integers, the slaves cannot be addressed with A or B. Therefore, the following assignments have been defined: Slave 1 31: The slaves are addressed in WinCC with the respective address (1 31). Slave 1B 31B: The slaves are addressed with the value: [Address] A slave with address 2B therefore has the value [2] + 32 = 34 in WinCC. Open a sublist and enter the slave number under Value. Under Text, enter the accompanying text. Entry-ID: , V1.0, 04/

57 Siemens AG 2016 All rights reserved 6 HTML configuration 6 HTML configuration To allow a diagnosis of your own AS-i environment, the websites have to be adjusted to your hardware configuration. This chapter describes the required individual adjustments: 6.1 Using websites Note The websites as well as the required files are coded and fragmented as data blocks. Changes in these files always require a regeneration of the web data blocks. The exact procedure can be found in the manual of the CPU. Overview of editable parameters The information of the slaves, the designation, the addressing and the image of the AS-i master, as well as the display texts for tool tips and legends are controlled via XML files. The following XML files are used: Table 6-1 SlavesX.xml File name Responsible for... Slave information (e.g. MLFB, place of use etc.) Master.xml Display text in the AS-i master selection list Building block address of AS-i master Path information of AS-i master screen Texte_de.xml Texte_en.xml Tooltip texts Status display texts Entry-ID: , V1.0, 04/

58 Siemens AG 2016 All rights reserved 6 HTML configuration Structure of an XML file The structure of an XML file is specified and must not be altered. An XML file consists of multiple elements, which are headed by a root element. Every element is integrated into the XML structure via a start <> and end tag and can be equipped with specific attributes for meta-information. Taking the XML file Master.xml as an example, this structure presents itself as follows: Figure 6-1 Table 6-2 Structure element <Infos> </Infos> <Master id= 1 > </Master> <DB_Nr> </DB_Nr> Description Root element: outer element of XML structure First element; additional attribute for clear identification. Second child element of <Master> 1 Text content of child element The following specific characteristics must be considered: Every XML element must have a start tag and an end tag, XML differs between lower case and upper case letters (e.g. <DB_NR> cannot be closed with </db_nr>). An XML structure must be headed by a single root element only. Umlauts and special characters are not allowed in XML and require special formatting. Entry-ID: , V1.0, 04/

59 Siemens AG 2016 All rights reserved 6 HTML configuration 6.2 Adjusting the AS-i master information NOTICE An error-free visualization is only possible, if 1. For every AS-i master involved, a separate AsiDiag has been created and all AsiDiag have been called up at least once (initialization phase); this can be ensured by calling it up in the start-up OB). 2. For all AS-i master involved, information (instance data block number and display text) are stored in the XML file. To diagnose your AS-i network, the instance data block number of the AS-i master must be correctly stored in the XML file Master.xml. 1. In the directory _PROJECT > HTML_FILES, all the files required for the user-defined websites are contained. 2. Select the XML file Master.xml and open it with an editor, for example, Notepad. As an example, two AS-i master are entered here. 3. If required, add additional masters with the same structure as the existing ones, or delete redundant ones. Changing the instance data block number Change the instance data block number within the child element <DB_NR> according to your standards. Adjusting the AS-i master display The child element <Name> contains the name of the AS-i master on the web interface and <Image> the path information for the AS-i master image. Alter these child elements according to your needs and save the XML file. Note The images./masterx.gif are in the HTML directory. If you want to use another image than the default one, be sure that this image is placed and integrated with the correct path information (starting from the HTML directory). Entry-ID: , V1.0, 04/

60 Siemens AG 2016 All rights reserved 6 HTML configuration 6.3 Adjusting the AS-i slave information Similar to the AS-i master, user-defined information can also be stored for the AS-i slaves. Those appear in an output field by clicking with the mouse on a slave. The slave information is stored in the XML file SlavesX.xml, wherein the X stands for the respective master. The assignment is analogous to the master list of the AsiWebVisu (see chapter The management of the AS-I masters): Table 6-3 XML file name Master Slaves0.xml Master 1 Slaves1.xml Master 2 Slaves2.xml Master 3 For every slave, there is a separate element reserved, which can be clearly assigned to a slave via the attribute id. The following classification applies: Table 6-4 Id area id = 1 to id = 31 slave 1 to slave 31 id = 32 Slave 0 id = 33 to id = 63 slave 1B to slave 31B Slave: Alter these slave information according to your needs and save the XML file. Note Elements which are not used must not be deleted, but have to be defined with a blank string (e.g. <Slave id = 4 ></Slave>). 6.4 Adjusting the display texts The tool tip texts and the status texts in the web visualization are likewise controlled via a XML file (Texte_xx.xml) and can be adjusted, if required. The element <Tooltip> contains the splitted tool tip text, which appears when the mouse is moved over a slave button. In the element <Statustext>, the display texts for the various slave statuses are stored. Alter these elements according to your needs and save the XML file. Entry-ID: , V1.0, 04/

61 Siemens AG 2016 All rights reserved 6 HTML configuration 6.5 Accessing the user-defined websites By loading the web blocks into the CPU and by activating the web server, you have the possibility to access the default or user-defined websites. The following manual illustrates the procedure: 1. Make sure that the controller and the PC share a joint ethernet network or are directly connected to each other via a common ethernet cable. 2. Open a web browser and the the URL address of CPU>. The introduction page of the web server opens. 3. To perform specific actions in the CPU or to write tags into the CPU, you have to log into the web server. For this example, enter the name: siemens and as password: asi. 4. In the navigation menu, switch to Customer pages. The web browser calls up the page, which provides access to the default page of the user-defined web application. Click on the link. The start page of the AS-i diagnosis is opened in a separate window. Entry-ID: , V1.0, 04/

62 Siemens AG 2016 All rights reserved 7 The library 7 The library 7.1 Using library blocks Overview of blocks This chapter describes how the library is integrated into STEP 7 and how the blocks are integrated into the user program. To integrate the diagnostic functions described in this document into your own STEP 7 project, the following blocks are required. AsiDiag AsiHmiVisu (optional for the HMI visualization) AsiWebVisu, AsiWebInterface, WWW (optional for web visualization) User-defined data types These blocks are included in the STEP 7 block library. This library can be found in the download area of this document (see chapter 8). Requirements for using the blocks The use of the blocks from the library requires that a STEP 7 project with the respective hardware configuration exists. In addition, you should ensure that the diagnostic interrupts for the AS-i masters and, if necessary, autoaddressing are activated. the respective error OBs or cyclic interrupts are integrated into the project. the web servers are activated, should you desire a web visualization. a user account with the appropriate rights has been created. The HTML files from the directory > HTML_FILES have been accordingly adjusted and coded into data blocks via the TIA portal. Opening the library The library file.ap13 is in the directory > _LIB. 1. Open your TIA project in the project view. 2. Open the library file via the palette Global library and the symbol Open global library. 3. Per Drag&Drop, drag the required blocks into the block directory of your configured CPU. 4. Also, drag the data types used into the appropriate directory of your configured CPU. Entry-ID: , V1.0, 04/

63 Siemens AG 2016 All rights reserved 7 The library 7.2 Initializing the blocks By using a call, the following manual shows how to integrate the library blocks into your project and parameterize them. Calling the AsiDiag blocks If more than one AS interface line shall be diagnosed in a project, a separate AsiDia with a specific instance data block is required for every single line. All AsiDiag blocks are called in the organization block OB 1. For the processing, the req input requires a connection with a positive edge. This trigger can be executed in the error or cyclic interrupt OBs. Note Activate all AsiDiag already in the start-up OB (OB 100). This ensures a uniform default state of all AsiDiag (initialization phase). Note The diagnostic data are read from the modules via SFB 52/SFB 53 (read/write data set). Depending on the CPU type, only a certain number of SFB calls can be processed simultaneously. More information can be found in the FAQ with the BID: Changing the remanence properties To delete old data from the instance data blocks of the block ( AsiDiag, AsiHmiVisu, AsiWebVisu ), after loss of current supply or a stopped CPU, the remanent behaviour has to be switched to not remanent. De-select the corresponding attribute in the properties of the instance data block. Figure 7-1 Entry-ID: , V1.0, 04/