Transcription

1 Inter-Station Communication between S Stations Using TCSB V3.1 via CP V2 CP V2, TCSB V3.1 Siemens Industry Online Support

2 Legal information Legal information Use of application examples Application examples illustrate the solution of automation tasks through an interaction of several components in the form of text, graphics and/or software modules. The application examples are a free service by Siemens AG and/or a subsidiary of Siemens AG ("Siemens"). They are non-binding and make no claim to completeness or functionality regarding configuration and equipment. The application examples merely offer help with typical tasks; they do not constitute customer-specific solutions. You yourself are responsible for the proper and safe operation of the products in accordance with applicable regulations and must also check the function of the respective application example and customize it for your system. Siemens grants you the non-exclusive, non-sublicensable and non-transferable right to have the application examples used by technically trained personnel. Any change to the application examples is your responsibility. Sharing the application examples with third parties or copying the application examples or excerpts thereof is permitted only in combination with your own products. The application examples are not required to undergo the customary tests and quality inspections of a chargeable product; they may have functional and performance defects as well as errors. It is your responsibility to use them in such a manner that any malfunctions that may occur do not result in property damage or injury to persons. Disclaimer of liability Siemens shall not assume any liability, for any legal reason whatsoever, including, without limitation, liability for the usability, availability, completeness and freedom from defects of the application examples as well as for related information, configuration and performance data and any damage caused thereby. This shall not apply in cases of mandatory liability, for example under the German Product Liability Act, or in cases of intent, gross negligence, or culpable loss of life, bodily injury or damage to health, non-compliance with a guarantee, fraudulent non-disclosure of a defect, or culpable breach of material contractual obligations. Claims for damages arising from a breach of material contractual obligations shall however be limited to the foreseeable damage typical of the type of agreement, unless liability arises from intent or gross negligence or is based on loss of life, bodily injury or damage to health. The foregoing provisions do not imply any change in the burden of proof to your detriment. You shall indemnify Siemens against existing or future claims of third parties in this connection except where Siemens is mandatorily liable. By using the application examples you acknowledge that Siemens cannot be held liable for any damage beyond the liability provisions described. Other information Siemens reserves the right to make changes to the application examples at any time without notice. In case of discrepancies between the suggestions in the application examples and other Siemens publications such as catalogs, the content of the other documentation shall have precedence. The Siemens terms of use ( shall also apply. Security information Siemens provides products and solutions with Industrial Security functions that support the secure operation of plants, systems, machines and networks. In order 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. Siemens products and solutions constitute one element of such a concept. Customers are responsible for preventing unauthorized access to their plants, systems, machines and networks. Such systems, machines and components should only be connected to an enterprise network or the Internet if and to the extent such a connection is necessary and only when appropriate security measures (e.g. firewalls and/or network segmentation) are in place. For additional information on industrial security measures that may be implemented, please visit Siemens products and solutions undergo continuous development to make them more secure. Siemens strongly recommends that product updates are applied as soon as they are available and that the latest product versions are used. Use of product versions that are no longer supported, and failure to apply the latest updates may increase customer s exposure to cyber threats. To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed at: Entry-ID: , V1.1, 06/2018 2

3 Table of contents Table of contents Legal information Task Solution Overview Description of the core functionality Overview and description of the user interface Hardware and software components Validity Components used Principle of Operation Complete overview of the data flow Station 2, "Stormwater Overflow", program overview Global data block: "SndRcvData" (DB1) Functionality of Station 2, "Stormwater Overflow" Program details on the "SimProgSO" FB Call of the "SimProgSO" FB in OB Partner status CP diagnostics Configuration and Project Engineering Configuring the "Inspection Shaft"/"Stormwater Overflow" station Configuring the data points "Inspection Shaft" station "Stormwater Overflow" station Configuring TeleControl Server Basic (TCSB) Installation and Startup Installing the hardware "Inspection Shaft" hardware configuration "Stormwater Overflow" hardware configuration Master station hardware configuration Installing the software Installing the application software Startup Setting the IP addresses Assigning the IP address to the engineering station Configuring the DSL router Inserting a backup copy of the " _S7-1200_InterCom.bak" database into TCSB V Configuring the IP address and the ports of TeleControl Server Basic V Loading the "Inspection Shaft" and "Stormwater Overflow" stations Operation of the Application Overview HMI menu Watch tables The "Inspection Shaft" station cyclically requests data from the "Stormwater Overflow" station The "Stormwater Overflow" station sends data to the "Inspection Shaft" station on an "event-triggered" basis Entry-ID: , V1.1, 06/2018 3

4 Table of contents 7 Appendix Service and support Links & Literature History Entry-ID: , V1.1, 06/2018 4

5 1 Task 1 Task Introduction The infrastructure of a sewage treatment plant contains two SIMATIC S substations. Both stations are to exchange data with each other. Both stations are connected to a master station on which the TeleControl Server Basic V3.1 software is installed. Inter-station communication takes place only via the master station. The Internet-based GPRS service is the data transfer medium to be used. Overview of the automation task The figure below provides an overview of the automation task. Figure 1-1 Master station TCSB WinCC Internet Fill level Inflow Inspection Shaft Stormwater Overflow Requirements This application example is intended to meet the following requirements: The "Inspection Shaft" station (Station 1) cyclically requests data from the "Stormwater Overflow" station (Station 2). The "Stormwater Overflow" station sends data to the "Inspection Shaft" station on an "event-triggered" basis. The master station monitors the status of the connected substations. The process in the remote stations is operated and controlled with the aid of visualization software. Entry-ID: , V1.1, 06/2018 5

6 2 Solution 2 Solution 2.1 Overview Diagrammatic representation The diagrammatic representation below shows the most important components of the solution: Figure 2-1 Master station TCSB SCALANCE M816 Tunnel connection Internet Cellular network Station 1 Station 2 S with S with CP V2 CP V2 Configuration TeleControl Server Basic V3.1 (TCSB) in the master station allows inter-station communication between the two S stations. The TCSB V3.1 s counterpart is the CP V2 included in each substation. For test purposes, the two stations are connected to the master station. Communication takes place via the cellular network and the Internet. The application is visualized using WinCC Advanced. Entry-ID: , V1.1, 06/2018 6

7 2 Solution Note For information on the data communication between S stations and TeleControl Server Basic, please refer to this application example: "Data communication between S stations and TeleControl Server Basic V3.1 via CP V2 and CP1243-1" (see \7\). Advantages The solution presented here offers the following advantages: TeleControl Server Basic V3.1 enables economic data communication between remote stations. The core application areas are industrial applications where the objective is to send data in a cost-effective way on a wireless basis, for example in water treatment plants, for water purification or in pumping stations. GPRS and Internet: Always-on functionality. To increase reliability, the CPs can, in the event of a connection failure, buffer the data of events of different classes and transfer the aggregated data to the TeleControl Server. Scope This application does not include a description of SIMATIC NET TeleControl Server Basic. See document \3\. SIMATIC HMI operator panels. the LAD/FBD/STL/SCL programming languages. Basic knowledge of these topics is required. Entry-ID: , V1.1, 06/2018 7

8 2 Solution 2.2 Description of the core functionality Functions implemented The following core functions are implemented in the application example: Table 2-1 Function Time-triggered Station Station 1 "Inspection Shaft" Station 2 "Stormwater Overflow" Master station Event-triggered Status monitoring Time-triggered The "Inspection Shaft" station cyclically requests data from the "Stormwater Overflow" station (polling). It cyclically sends a bit to the "Stormwater Overflow" station and the "Stormwater Overflow" station responds with the requested data. Event-triggered The "Stormwater Overflow" station sends data to the "Inspection Shaft" station. The data is sent when a configured trigger signal is triggered. Status monitoring The master station monitors the status of the connected substations. Note For a more detailed description of these functions, please refer to Chapter 3 and the following chapters. Entry-ID: , V1.1, 06/2018 8

9 2 Solution 2.3 Overview and description of the user interface The application example is visualized with WinCC Advanced using two configured screens: "TCSB Communication" and "S Application". "TCSB Communication" The "TCSB Communication" screen shows the status of the connection to the two substations. Figure Table 2-2 Item Description 1. Communication Status: Connectionstate SignalQuality PLCConnected PLCCpuState PartnerStatus NetworkStatus 2. Communication Status: Connectionstate SignalQuality PLCConnected PLCCpuState PartnerStatus NetworkStatus Information about the communication status of the "Inspection Shaft" station. TCSB itself determines the values (Connectionstate, SignalQuality, PLCConnected, PLCCpuState). Information about the communication status of the "Stormwater Overflow" station. TCSB itself determines the values (Connectionstate, SignalQuality, PLCConnected, PLCCpuState). 3. Change screen Click the buttons to display the appropriate screens. Entry-ID: , V1.1, 06/2018 9

10 2 Solution "S Application" The "S Application" screen visualizes the processes of the "Inspection Shaft" and "Stormwater Overflow" stations. Figure Table 2-3 Item Description 1. "Polling Data" "Activate Polling" Click the button to activate requesting the fill level from the "Stormwater Overflow" station. "Deactivate Polling" Click the button to deactivate requesting the fill level from the "Stormwater Overflow" station. 2. "Partner data" "PartnerFillLevel" Current fill level of the "Stormwater Overflow" station. "Overflow" Green: Inflow of "Stormwater Overflow" station less than limit value. Red: Inflow of "Stormwater Overflow" station greater than limit value. 3. "FillLevel" Current fill level of "Stormwater Overflow" station. 4. "Inflow" Current inflow of station. 5. "InflowUp" Inflow limit value of "Stormwater Overflow" station. Entered manually by the user. The start value is set to 25%. 6. Change screen Click the buttons to display the appropriate screens. Entry-ID: , V1.1, 06/

11 2 Solution 2.4 Hardware and software components Validity This application is valid for CP V2 with Firmware V3.1 or higher STEP 7 V15 S CPU V4.1 or higher TCSB V Components used This application was created with the following components: Station 1 hardware components Table 2-4 Component Article number Note S PM EP1332-1SH71 Power supply SIMATIC S CPU 1217C DC/DC/DC CP V2 COMMUNICATIONS PROCESSOR ANT794-4MR ANTENNA SIMATIC Memory Card 1 6ES7217-1AG40-0XB0 Any S CPU V4.1 or higher can be used. 1 6GK7242-7KX31-0XE0 Firmware V3.1 or higher 1 6NH9860-1AA00 GSM quad-band and UMTS 1 6ES7954-8LF01-0AA0 Memory card for the S CPU Station 2 hardware components Table 2-5 Component Article number Note S PM EP1332-1SH71 Power supply SIMATIC S CPU 1217C DC/DC/DC CP V2 COMMUNICATIONS PROCESSOR ANT794-4MR ANTENNA SIMATIC Memory Card 1 6ES7217-1AG40-0XB0 Any S CPU V4.1 or higher can be used. 1 6GK7242-7KX31-0XE0 Firmware V3.1 or higher 1 6NH9860-1AA00 GSM quad-band and UMTS, LTE 1 6ES7954-8LF01-0AA0 Memory card for the S CPU Entry-ID: , V1.1, 06/

12 2 Solution Accessories Table 2-6 Component Article number Note SIM card 2 Available from your mobile service provider DSL router + modem Static IP address for DSL or DynDNS Enabled for data communication 1 Specialist retailers SCALANCE M816 1 Can be requested from your service provider Software components Table 2-7 Component Article number Note STEP 7 Professional V15 1 6ES7822-1AA05-0YA5 TCSB 8 V NH9910-0AA31-0AA0 Number of connectable stations: 8. The product is available in other configurations and license options, see document \3\. WinCC Advanced V15 1 6AV2102-0AA05-0AA5 Sample files and projects The following list contains all files and projects that are used in this example. Table 2-8 Component _S7-1200_InterCom_PROJ_V11.zip _S7-1200_InterCom_DOC_V11_en.pdf Note This zip file contains: The STEP 7 V15/ WinCC Advanced project TCSB project This document. Entry-ID: , V1.1, 06/

13 3 Principle of Operation 3 Principle of Operation Key points of this application example: Configuration of the "Inspection Shaft" station (S and CP V2) for inter-station communication with the "Stormwater Overflow" station (S and CP V2). Configuration of TeleControl Server Basic in the master station. Functional data exchange between the two stations. 3.1 Complete overview of the data flow To transfer the data between the station and the communication partner, the CP requires no programming. The data areas in the memory of the CPU intended for communication with the partner are configured in the CP on a data point-related basis. In this configuration, each data point is linked to a PLC tag or data block in the CPU. In this example, the current fill level and the alarm bit of the "Stormwater Overflow" station are read and transferred by the CP to the "Inspection Shaft" station via TCSB V3.1. The following transfer methods are set in the data configuration in STEP 7: Time-triggered The "Inspection Shaft" station cyclically requests the current fill level of the "Stormwater Overflow" station. The "Inspection Shaft" station cyclically sends (1x per minute) a bit ("reqfilllevel") to the "Stormwater Overflow" station. Then the "Stormwater Overflow" station sends the current fill level ("filllevel") back to the "Inspection Shaft" station. Event-triggered The "Stormwater Overflow" station sends the alarm bit to the "Inspection Shaft" station. If the current inflow exceeds the set limit value, a trigger signal is triggered, which transfers the alarm bit. This transfer of the alarm bit resets the trigger signal. Entry-ID: , V1.1, 06/

14 3 Principle of Operation The following figure shows the data flow and the configuration points of the S stations for inter-station communication via the master station. Figure 3-1 Station 1 Inspection Shaft Station 2 Stormwater Overflow 1 =True reqfilllevel 1 min receivereqfilllevel partnerfilllevel filllevel Send automatic Reset stattriggerfilllevel Set 2 Manual inflow inflowup > partneroverflow Reset automatic stattriggeroverflow overflow (=True) Set Send 1 min Configured in the CP as a cyclic data point Configured in the CP as an event-triggered data point Table 3-1 Station 1 Station 2 1. a. The "reqfilllevel" data point in the CP V2 of Station 1 (Inspection Shaft) is configured with the "reqfilllevel" PLC tag in the CPU with the cyclically time-triggered transfer method. b. The "filllevel" data point in the CP of Station 2 (Stormwater Overflow) is configured with the "filllevel" PLC tag in the CPU with the event-triggered transfer method. c. The "Inspection Shaft" station cyclically sends a bit (reqfilllevel) to the "Stormwater Overflow" station. d. Then the "Stormwater Overflow" station sends the current fill level back to the "Inspection Shaft" station. e. The current fill level (filllevel) is sent to Remote Station 1 via the master station. Entry-ID: , V1.1, 06/

15 3 Principle of Operation Station 1 Station 2 2. a. The "overflow" data point in the CP V2 of Station 2 is configured with the "overflow" tag (true if inflow > limit value) in the CPU with the eventtriggered transfer method. b. If the inflow value of Station 2 is greater than the limit value (inflow > inflowup), a timer will be started in the user program. When the time has elapsed, the "stattriggeroverflow" trigger signal will be set in the user program and the alarm bit ("overflow") will be sent to Remote Station 1 via the master station. c. This transfer of the alarm bit resets the trigger signal. Note It is recommended to set the trigger signal with a delay of approx. 500 ms to ensure that the value change of the PLC tags is reliably applied to the appropriate data point. Note Inter-station communication requires that a partner be activated in the data point configuration. Partners set in the table of the parameter group can be selected (see Table 4-1, Step 11). Entry-ID: , V1.1, 06/

16 3 Principle of Operation Station 2, "Stormwater Overflow", program overview The following figure shows the important elements of the program of the "Stormwater Overflow" station. In this application example, no program is implemented in the "Inspection Shaft" station. Communication with the "Stormwater Overflow" station does not require a program block. This is done via the data point configuration. Figure 3-2 Main SimProg SO instdbsim ProgSO Data points SndRcv Data User block Data blocks Station 1: CP V2 Station 2: CP V2 Table 3-2 Item Symbolic name Description OB1 Main Cyclic OB: Call of the user program FB1 SimProgSO The "SimProgCPx" FB contains the described functions (Table 3-1, Step 3). DB2 instdbsimprogso Instance data block of the user block DB1 SndRcvData Global data block for saving the data: Send data Status tags Trigger signals Data points Configured data points for data exchange between the "Stormwater Overflow" station and the "Inspection Shaft" station. Entry-ID: , V1.1, 06/

17 3 Principle of Operation Global data block: "SndRcvData" (DB1) "Inspection Shaft" station The DB contains the PLC tags necessary for the data configuration of the CP V2 in the "Inspection Shaft" station and the status tags. Figure 3-3 Table 3-3 Name Data type Description reqfilllevel Bool Cyclic sending to the "Stormwater Overflow" station to request the current fill level. partnerfilllevel Real Current fill level received from the "Stormwater Overflow" station. partneroverflow Bool Alarm bit received from the "Stormwater Overflow" station. True: Current inflow has exceeded the limit value. False: Current inflow less than limit value. partnerstatus Word Status of connection to TCSB (see Chapter 3-3). networkstatus UInt Status of connection to data service in cellular network (see Chapter 3-4). triggerdiag Bool Diagnostics trigger tag. Set when the sample plant is started for the first time to enable the CP V2 s advanced diagnostics (networkstatus). Entry-ID: , V1.1, 06/

18 3 Principle of Operation "Stormwater Overflow" station The DB contains the PLC tags necessary for the data configuration of the CP V2 in the "Stormwater Overflow" station and the status tags. Figure 3-4 Table 3-4 Name Data type Description filllevel Real Current fill level of the "Stormwater Overflow" station. inflow Real Current inflow of the "Stormwater Overflow" station. inflowup Real Inflow limit value of the "Stormwater Overflow" station. overflow Bool Alarm bit of the "Stormwater Overflow" station. True: Current inflow has exceeded the limit value. False: Current inflow less than limit value. receivereqfilllevel Bool Bit received from the "Inspection Shaft" station. True: The "Inspection Shaft" station cyclically requests data from the "Stormwater Overflow" station. Only for one cycle. partnerstatus Word Status of connection to TCSB (see Chapter 3-3). networkstatus UInt Status of connection to data service in cellular network (see Chapter 3-4). triggerdiag Bool Diagnostics trigger tag. Set when the sample plant is started for the first time to enable the CP V2 s advanced diagnostics (networkstatus). done Bool True: The data was successfully transferred to the CP. Only valid for one cycle. Entry-ID: , V1.1, 06/

19 3 Principle of Operation 3.2 Functionality of Station 2, "Stormwater Overflow" Program details on the "SimProgSO" FB The "SimProgSO" FB sets the trigger signals for sending the current fill level (filllevel) of the "Stormwater Overflow" station to the "Inspection Shaft" station when a request ("receivereqfilllevel") is received from the "Inspection Shaft" station. the alarm bit (overflow) of the "Stormwater Overflow" station to the "Inspection Shaft" station if the current inflow is greater than the limit value. Figure 3-5 Inflow Limit Value Start Inflow <> InflowOld no Partner Request Inflow > Limit Value 500-ms Delay yes yes no yes Set Trigger Signals End Note The trigger signals are automatically reset when the data is transferred to the CP. Note In the function block, the trigger signals are set with a 500-ms delay so that the value change of the "filllevel" and "overflow" tags is reliably applied to the appropriate data points ("DP, filllevel" and "DP, overflow"). Entry-ID: , V1.1, 06/

20 Out InOut Siemens AG 2018 All rights reserved Input 3 Principle of Operation The following figure and table show the call interface of the user block FB, "SimProgSO" (FB1), of the "Stormwater Overflow" station. Figure 3-6 Table 3-5 Name Data type Description filllevel Real Current fill level of the "Stormwater Overflow" station. inflow Real Current inflow of the "Stormwater Overflow" station. inflowup Real Inflow limit value of the "Stormwater Overflow" station. Entered manually by the user. Set to 25% when starting the sample plant for the first time. overflow Bool Alarm bit: Current inflow status. True: Current fill level has exceeded the limit value. False: Current fill level less than limit value. receivereqfilllevel Bool True: The "Inspection Shaft" station requests data from the "Stormwater Overflow" station. Only valid for one cycle. done Bool True: The data was successfully transferred to the CP. Only valid for one cycle. Entry-ID: , V1.1, 06/

21 3 Principle of Operation Call of the "SimProgSO" FB in OB1 The "SimProgSO" FB (FB1) is called cyclically in OB1. The input and output parameters are stored in the global data block, "SndRcvData". Figure 3-7 Entry-ID: , V1.1, 06/

22 3 Principle of Operation 3.3 Partner status Using the "Report partner status" function in the CP configuration, the CP signals the status of the communication with TCSB to the CPU. This information is written to the "partnerstatus" PLC tag in the "SndRcvData" DB. The following figure shows the bit assignment of the "partnerstatus" tag (Word). Figure 3-8 Byte1 Byte 0 Not assigned Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Not assigned 0: Partner unreachable 1: Partner reachable 0: All paths to partner OK 1: All paths to partner not OK 0: Send buffer OK 1: Send buffer overflow imminent (above 80% of fill level) 3: Send buffer overflow imminent (above 100% of fill level) Bit 2 and 3 will be reset to 0 as soon as the value is below 50% of the fill level. 3.4 CP diagnostics Advanced "CP diagnostics" in the CP configuration (see \5\) allows you to read the status of the connection to the data service in the cellular network out of the CP. This information is written to the "networkstatus" PLC tag (UInt) in the "SndRcvData" DB. Table 3-6 networkstatus Meaning 0 Cellular network status: not connected 1 Wrong PIN number 2 SIM card missing or defective 3 Waiting for PIN to be entered 4 Cellular network status: connected Entry-ID: , V1.1, 06/

23 4 Configuration and Project Engineering 4 Configuration and Project Engineering Note In the project, the configuration and project engineering have already been fully implemented. This chapter is for information only. The configuration is performed in the following configuration tools (first STEP 7, then TeleControl Server Basic): STEP 7 V15: Configuring the "Inspection Shaft" and "Stormwater Overflow" stations Configuring the data points for both stations TeleControl Server Basic: Creating and configuring the project Creating and configuring connections Configuring general parameters 4.1 Configuring the "Inspection Shaft"/"Stormwater Overflow" station The following table shows you how to configure an S station with the CP GPRS V2 for inter-station communication with a second S station. Table Create a STEP 7 V15 project. 2. Insert the S CPU (V4.1 or higher) for the "Inspection Shaft" SIMATIC station. 3. Insert the CP GPRS V2 into the station. Entry-ID: , V1.1, 06/

24 4 Configuration and Project Engineering 4. Double-click the CP GPRS V2 to open its properties. Activate telecontrol communication and S7 communication: "Properties > General > Communication types". 5. Make the required mobile wireless communications settings: "Properties > Mobile wireless communications settings": Activate PIN Enable data services and GPRS Enter the APN settings you obtained from your service provider (APN settings). 6. Enable the security functions. Create a user for the security functions. "Properties > Security > Security properties". Entry-ID: , V1.1, 06/

25 4 Configuration and Project Engineering 7. Configure the CP parameters required to configure the TeleControl Server: "Properties > Partner stations > Connection to partner" Partner IP address (a static IP address must be requested from the provider) Partner port WAN-IP-ADDRESS "Properties > Security > CP identification" Project number Station number Telecontrol password ("Inspection Shaft": CP1242-7_1, "Stormwater Overflow": CP1242-7_2) The parameters assigned here must be identical to the parameters in TCSB. 8. Check Report partner status: "Properties > Partner stations > Advanced settings" Link a PLC tag you have created in the user program. Entry-ID: , V1.1, 06/

26 4 Configuration and Project Engineering 9. Check Enable advanced CP diagnostics: "Properties > Communication with the CPU > CP diagnostics". Link the "diagnostics trigger tag" and the PLC tags you want to read out of the CP GPRS V Repeat steps 1 through 9 for the "Stormwater Overflow" station. 11. For the CP of each station, define the communication partners for inter-station communication: "Properties > Partner stations > Partner for inter-station communication" Enter the project number of the CP in the partner station Enter the station number of the CP in the partner station Enter the slot number of the CP in the partner station Check Send buffer. 12. Configure the desired data points for the "Inspection Shaft" station (see Table 4-2 and Table 4-3) and the "Stormwater Overflow" station (see Table 4-4 and Table 4-5). 13. Download the project data to the stations. Entry-ID: , V1.1, 06/

27 4 Configuration and Project Engineering 4.2 Configuring the data points For the CP GPRS V2, it is not necessary to program program blocks in order to transfer user data between the stations. The data areas in the memory of the CPU intended for inter-station communication are configured in the CP GPRS V2 on a data point-related basis. In this configuration, each data point is linked to a PLC tag in the CPU (see Figure 3-1) "Inspection Shaft" station Data point for the send data to the "Stormwater Overflow" station Table Open the data point configuration editor. 2. Insert the "reqfilllevel" data point as a digital input and link it to the "SndRcvData.reqFillLevel" PLC tag. 3. Set the transfer method for this data point (here: Current value triggered). 4. Set the data point index (here: 0). Note: The index of a data point of the Input type must be unique over all data point types (digital inputs, analog inputs, etc.). The data point index must match the one in "Stormwater Overflow". Entry-ID: , V1.1, 06/

28 4 Configuration and Project Engineering 5. As the communication partner, select "Inter-station communication". 6. Configure the "Time trigger": "Properties > General > Trigger > Time trigger" 7. Configure the partner stations. "Properties > General > Partner stations > Partner for inter-station communication" For the partner number, please refer to the CP configuration (see Table 4-1, Step 11). Data points for the receive data from the "Stormwater Overflow" station Table In the data point configuration editor, insert the "partnerfilllevel" data point as an analog output and link it to the "SndRcvData.partnerFillLevel" PLC tag. 2. Set the transfer method for this data point (here: Transfer after call). Entry-ID: , V1.1, 06/

29 4 Configuration and Project Engineering 3. Set the data point index (here: 1). The data point index must match the one in "Stormwater Overflow". 4. As the communication partner, select "Inter-station communication". 5. Configure the partner stations. "Properties > General > Partner stations > Partner for inter-station communication" For the partner number, please refer to the CP configuration (see Table 4-1, Step 11). 6. In the data point configuration editor, insert the "partneroverflow" data point as a digital output and link it to the "SndRcvData.partnerOverflow" PLC tag. 7. Set the transfer method for this data point (here: Transfer after call). 8. Set the data point index (here: 2). The data point index must match the one in "Stormwater Overflow". 9. As the communication partner, select "Inter-station communication". Entry-ID: , V1.1, 06/

30 4 Configuration and Project Engineering 10. Configure the partner stations. "Properties > General > Partner stations > Partner for inter-station communication" For the partner number, please refer to the CP configuration (see Table 4-1, Step 11) "Stormwater Overflow" station Data points for the receive data from the "Inspection Shaft" station Table Open the data point configuration editor. 2. Insert the "recreqfilllevel" data point as a digital output and link it to the "SndRcvData.receiveReqFillLevel" PLC tag. Entry-ID: , V1.1, 06/

31 4 Configuration and Project Engineering 3. Set the transfer method for this data point (here: Transfer after call). 4. Set the data point index (here: 0). The data point index must match the one in "Inspection Shaft". 5. As the communication partner, select "Inter-station communication". 6. Configure the partner stations. "Properties > General > Partner stations > Partner for inter-station communication" For the partner number, please refer to the CP configuration (see Table 4-1, Step 11). Entry-ID: , V1.1, 06/

32 4 Configuration and Project Engineering Data point for the send data to the "Inspection Shaft" station Table In the data point configuration editor, insert the "filllevel" data point as an analog input and link it to the "SndRcvData.fillLevel" PLC tag. 2. Set the transfer method for this data point (here: Current value triggered). 3. Set the data point index (here: 1). Note: The index of a data point of the Input type must be unique over all data point types (digital inputs, analog inputs, etc.). The data point index must match the one in "Inspection Shaft". 4. As the communication partner, select "Inter-station communication". 5. Configure the "Event trigger": "Properties > General > Trigger > Event trigger" In the user program, create a trigger tag and link it to the "event trigger" ("instdbsimprogso.stattriggerfilllevel"). Entry-ID: , V1.1, 06/

33 4 Configuration and Project Engineering 6. Configure the partner stations. "Properties > General > Partner stations > Partner for inter-station communication" For the partner number, please refer to the CP configuration (see Table 4-1, Step 11). 7. In the data point configuration editor, insert the "overflow" data point as a digital input and link it to the "SndRcvData.overflow" PLC tag. 8. Set the transfer method for this data point (here: Current value triggered). 9. Set the data point index (here: 2). Note: The index of a data point of the Input type must be unique over all data point types (digital inputs, analog inputs, etc.). The data point index must match the one in "Inspection Shaft". 10. As the communication partner, select "Inter-station communication". Entry-ID: , V1.1, 06/

34 4 Configuration and Project Engineering 11. Configure the "Event trigger": "Properties > General > Trigger > Event trigger" In the user program, create a trigger tag and link it to the "event trigger" (here: "instdbsimprogso.stattriggeroverflow"). 12. Configure the partner stations. "Properties > General > Partner stations > Partner for inter-station communication" For the partner number, please refer to the CP configuration (see Table 4-1, Step 11). Note Each trigger signal should be linked to a static tag in the instance data block in the CPU. If the trigger signal is interconnected with a global tag, it is possible that the trigger signal may not be automatically reset. This is due to the runtime differences between the CPU cycle and the CP cycle. It is recommended to set the trigger tag with a delay of approx. 500 ms to ensure that the value change of the fill level is reliably applied to the appropriate data point. Entry-ID: , V1.1, 06/

35 4 Configuration and Project Engineering 4.3 Configuring TeleControl Server Basic (TCSB) Table Start the configuration and monitoring user interface of TCSB (CMT): "Windows Start menu > All Programs > Siemens Automation > SIMATIC > TCS Basic > Config and Monitoring Tool" 2. After starting the program, the CMT Logon window opens. Enter your logon data to log on. Default logon data: User name: administrator Password: Create a new project: In the navigation pane, select the "Projects" item. In the command bar, click the "Add" button. The new project appears in the navigation pane and in the object pane. 4. Configure the new project: In the navigation pane or object pane, select the project and click the "Settings" tab. 5. Enter the following project parameters: "Project name", "Project number", "Server password". Click "Create". 6. "Save & activate" the configuration to activate the configuration data for connection establishment. Entry-ID: , V1.1, 06/

36 4 Configuration and Project Engineering 7. Create a new connection for Station 1: In the navigation pane, select a project for which you want to create a new connection. In the command bar, select the required connection type from the "Connection type" drop-down list. In the object pane, select the "Add" button from the command bar. Select the desired CP. The new connection appears in the object pane. 8. Save the changes and activate the project. Entry-ID: , V1.1, 06/

37 4 Configuration and Project Engineering 9. Configure the new connection: Select the connection. In the object pane, select the "Connections" tab. 10. In the "General" parameter group, enter the parameters for Station 1: "Station name" "Station number" "Telecontrol password" Note: The parameters assigned here must be identical to the ones in the STEP 7 V15 project. 11. Repeat steps 7 through 10 for Station Configure the IP address and the ports of the TeleControl Server: "TCSB system > "TCM" tab > General > Address TCM 1". 13. Save the changes and activate the project. Note If you create a new TCSB project for this application example, modify the relevant HMI tags in the visualization software accordingly. Entry-ID: , V1.1, 06/

38 5 Installation and Startup 5 Installation and Startup 5.1 Installing the hardware For the necessary hardware components, please refer to Chapter 2.4. Note Always follow the installation guidelines for all components. NOTICE Before you switch on the power supply, complete and check the installation! "Inspection Shaft" hardware configuration The figure below shows the hardware configuration of the "Inspection Shaft" station. S CPU to the CP GPRS V2. Figure 5-1 CP GPRS V2 CPU 1217C Engineering station 24 V Industrial Ethernet Table Insert your SIM card into the CP GPRS V2. 2. Attach the individual modules to a suitable rack. 3. Connect the CPU to the CP GPRS V2. 4. Connect the antenna to the CP GPRS V2. 5. Connect the engineering PG to the PROFINET interface of the S7 CPU. 6. Connect the CPU 1217C and the CP GPRS V2 to a 24 V DC power source. 7. Connect the DC power source to the power grid (220 / 230 V AC). Entry-ID: , V1.1, 06/

39 5 Installation and Startup "Stormwater Overflow" hardware configuration The figure below shows the hardware configuration of the "Stormwater Overflow" station. S CPU to the CP GPRS V2. Figure 5-2 CP GPRS V2 CPU 1217C Engineering station 24 V Industrial Ethernet Table Insert your SIM card into the CP GPRS V2. 2. Attach the individual modules to a suitable rack. 3. Connect the CPU to the CP GPRS V2. 4. Connect the antenna to the CP GPRS V2. 5. Connect the engineering PG to the PROFINET interface of the S7 CPU. 6. Connect the CPU 1217C and the CP GPRS V2 to a 24 V DC power source. 7. Connect the DC power source to the power grid (220 / 230 V AC). Entry-ID: , V1.1, 06/

40 5 Installation and Startup Master station hardware configuration The figure below shows the hardware configuration of the master station. Figure 5-3 Master station DSL router TCSB V3.1 Static IP address Internet (DSL line) Industrial Ethernet Table Connect your PC on which TeleControl Server Basic is installed to the router via Ethernet. 2. If the DSL modem is not integrated in the router, connect the router to the DSL modem. 5.2 Installing the software Engineering PC/PG Table 5-4 Comment 1. Install STEP 7 V Install WinCC Advanced V15. PC/PG as the master station Table 5-5 Follow the instructions of the installation program. Comment 1. Install TeleControl Server Basic V3.1. Follow the instructions of the installation program. Entry-ID: , V1.1, 06/

41 5 Installation and Startup 5.3 Installing the application software Unzip the " _S7-1200_InterCom_PROJ_V11.zip" file. This folder contains: The archived STEP 7 project, " _S7-1200_InterCom_CODE_V11.zip": "Inspection Shaft" Station 1 project "Stormwater Overflow" Station 2 project "Data communication TCSB" WinCC project " _S7-1200_InterCom.bak" TCSB configuration file 5.4 Startup Setting the IP addresses The following table shows the configured IP addresses. Table 5-6 Module IP address Subnet mask "Inspection Shaft": CPU 1217C DC/DC/DC "Stormwater Overflow": CPU 1217C DC/DC/DC Engineering PC/PG SIMATIC HMI TP700 Comfort PC/PG master station Assigning the IP address to the engineering station The following table shows the network settings to which you have to change the engineering station: Table Open the Internet Protocol (TCP/IP) Properties: "Start > Settings > Network Connection >Local Connections". 2. In the open window, select Internet Protocol (TCP/IP) and open Properties. Entry-ID: , V1.1, 06/

42 5 Installation and Startup 3. Select the "Use the following IP address" radio button and fill out the field as shown in the screenshot. Select "OK" to close the dialogs. 4. If your PG has an IWLAN interface, disable it Configuring the DSL router For the configuration, no specific router will be discussed as the screen forms will differ from router to router. Note To configure the router, you have to assign an IP address to your PG/PC that is in the router s internal network. Table Open the router s configuration user interface. 2. Enter the access data for your Internet account. This can be additional software, "Telnet" or a Web page. Login, password, etc. you received from your provider. 3. Enter your DNS server. The address is provided with your access data. 4. Assign a LAN IP address to the router. In this example: Forward TCP port to port of Entry-ID: , V1.1, 06/

43 5 Installation and Startup Inserting a backup copy of the " _S7-1200_InterCom.bak" database into TCSB V3.1 Table Stop the existing database by stopping the "TCS Basic Database Service" service using Windows Task Manager in the "Services" tab (as an administrator). Entry-ID: , V1.1, 06/

44 5 Installation and Startup 2. Start SQL Server Management Studio as an administrator: "Start > All Programs > Microsoft SQL Server 2008 R2 > SQL Server Management Studio". The "Connect to Server" dialog opens with the following settings: Server type: Database Engine Server name: <PC name>\tcsb Authentication: Windows Authentication 3. Keep all settings and click "Connect". SQL Server Management Studio opens with the database s object navigation. 4. Select the "Databases" item. Entry-ID: , V1.1, 06/

45 5 Installation and Startup 5. Right-click "Restore Database...". The "Restore Database - TCSB" dialog opens. 6. In the "Destination for restore" field, select the "TCSB" database ("To database"). In the "Source for restore" field, select the "From device" option and use the "..." button to open the "Specify Backup" dialog. Select the " _S7-1200_InerCom.bak" backup copy by first opening the file browser using the "Add" button. 7. In the "Restore Database - TCSB" dialog, select the selected "backup set" in the "Restore" column and click "OK". 8. Click "OK" to close Management Studio. 9. Restart the computer. Entry-ID: , V1.1, 06/

46 5 Installation and Startup Configuring the IP address and the ports of TeleControl Server Basic V3 Table Start the configuration and monitoring user interface of TCSB (CMT): "Windows Start menu > All Programs > Siemens Automation > SIMATIC > TCS Basic > Config and Monitoring Tool". 2. After starting the program, the CMT Logon window opens. User name: administrator Password: administrator Enter the IP address or the TeleControl Server name resolvable by DNS. Computer name or IP address (default IP address: ) 3. Configure the IP address and the ports of the TeleControl Server: "TCSB system > "TCM" tab > General > Address TCM 1". 4. Save the changes and activate the project. 5. Restart the computer. Entry-ID: , V1.1, 06/

47 5 Installation and Startup Loading the "Inspection Shaft" and "Stormwater Overflow" stations Requirements A connection has been established between your engineering station and the CPU (for example, via the PROFINET interface). The CPU must be in a mode that allows downloading. Before downloading the user program, a general reset of the CPU should be performed to ensure that no "old" blocks are on the CPU. Table Unzip the " _S7-1200_InterCom_CODE_V11.zip" project. 2. Open the "S with TCSB_interCom.ap15" STEP 7 V15 project. 3. Following dialog appears: Log on with the following data: User name: administrator Password: administrator 4. Customize the mobile wireless communications settings of the CP GPRS V2 for both stations: "Properties > Mobile wireless communications settings": Change the PIN Change the APN settings Entry-ID: , V1.1, 06/

48 5 Installation and Startup 5. For both stations, change the partner IP address (static IP address of your DSL router) required for the connection to the TeleControl Server in the master station: "Properties > Partner stations > Connection to partner" WAN IP ADDRESS 6. Select the "Inspection Shaft" or "Stormwater Overflow" station. 7. Download the project to the "Inspection Shaft" or "Stormwater Overflow" station. 8. Repeat steps 6 and 7 for the other station. Entry-ID: , V1.1, 06/

49 6 Operation of the Application 6 Operation of the Application 6.1 Overview HMI menu The application is visualized with WinCC Advanced using two configured screen forms: "TCSB Communication" and "S Application". Figure 6-1 Main menu TCSB Communication S Application Main menu The main menu allows you to open the application example and toggle between "TCSB Communication" and "S Application". "TCSB Communication" screen The "TCSB Communication" screen shows the status of the connection to the substations. You can toggle between "main menu" and "S Application". "S Application" screen The "S Application" screen visualizes the process of the "Inspection Shaft" and "Stormwater Overflow" stations. You can toggle between "main menu" and "TCSB Communication". Note The HMI is only used to test the application in the local network. Entry-ID: , V1.1, 06/

50 6 Operation of the Application Watch tables As an alternative to the HMI, you can use the "Watch_table_IS" / "Watch_table_SO" tables to monitor or modify the tags of the "SndRcvData" DB. For a description of the tags, please refer to Chapter "Inspection Shaft" station Figure 6-2 "Stormwater Overflow" station Figure 6-3 Entry-ID: , V1.1, 06/

51 6 Operation of the Application 6.2 The "Inspection Shaft" station cyclically requests data from the "Stormwater Overflow" station The "Inspection Shaft" station requests the fill level of the "Stormwater Overflow" station at a defined interval (1 minute). The "Stormwater Overflow" station responds with the requested data. The following table provides instructions for this job. Table Click the "Start Simulation" icon to start the WinCC Advanced simulation. 2. Open the "TCSB Communication" screen. Make sure that the connection between the stations has been established: PartnerStatus: 0003 (see Chapter 3.3) NetworkStatus: 4 (see Chapter 3.4) Entry-ID: , V1.1, 06/

52 6 Operation of the Application 3. Open the "S Application" screen and activate the polling process. 4. Enter the fill level of the "Stormwater Overflow" station. 5. After 1 minute, the fill level is transferred to the "Inspection Shaft" station. Note You can change the time interval in the data point configuration as needed: "Inspection Shaft > Local modules > CP > Data points > PollingData". Entry-ID: , V1.1, 06/

53 6 Operation of the Application 6.3 The "Stormwater Overflow" station sends data to the "Inspection Shaft" station on an "event-triggered" basis If the inflow of the "Stormwater Overflow" station exceeds a maximum value, an alarm bit will be sent to the "Inspection Shaft" station. The following table provides instructions for this job. The WinCC Advanced simulation was started (see Table 6-1, Step 1). Table Open the "TCSB Communication" screen. Make sure that the connection between the stations has been established: PartnerStatus: 0003 (see Chapter 3.3) NetworkStatus :4 (see Chapter 3.4) 2. Open the "S Application" screen and enter an inflow value that exceeds the maximum inflow value ("InflowUp") (e.g., 30%). Note: When starting the simulation, the limit value is set to 25%. You can change this value as needed. Entry-ID: , V1.1, 06/

54 6 Operation of the Application 3. The overflow alarm bit is set immediately and transferred to the "Inspection Shaft" station. 4. Enter an inflow value that is less than the maximum inflow value (e.g., 15%). 5. The overflow alarm bit is reset immediately and transferred to the "Inspection Shaft" station. Entry-ID: , V1.1, 06/