SINAUT ST7. SINAUT ST7cc Control Center A I. Manual. Introduction to ST7cc. Installation. Preparation. Working with ST7cc Config

Transcription

1 Introduction to ST7cc 1 Installation 2 SINAUT ST7 SINAUT ST7cc Control Center Manual Preparation Working with ST7cc Config 3 4 ST7cc Config with EXCEL 5 Valid for ST7cc Server 6 Product Software Version SINAUT ST7cc 2.0 This manual is applicable for all software versions up to and including version 2.x. Newer software versions will be supported by online help and readme files prior to publication of updated editions of the manual. Diagnostic and Trace Possibilities 7 The SINAUT hotline can be reached by: Tel: +49 (0) Fax: +49 (0) Hotline.ST@khe.siemens.de PM-AQUA Link 8 Internet: ACRON Link 9 Edition 05/2002 Appendix Index A I

2 SINAUT Documentation Certified Siemens Quality for Software and Training according to DIN ISO 9001, Reg. No This documentation was created with WinWord V 8.0, DesignerV6.0 and the documentation tool, AutWinDoc. The reproduction, transmission or use of this document or its contents is not permitted without express written consent. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. Siemens AG All Rights Reserved. Order No. 6NH7998-7AA11 Printed in the Federal Republic of Germany It is possible that there are operable functions in the system that are not described in this documentation. However, no claims can be made for these functions for new delivery or in cases of servicing. We have checked the contents of this manual for agreement with the hardware and software described. Deviations, however, cannot be entirely precluded. The information in this manual is reviewed regularly and any necessary corrections are included in subsequent editions. Suggestions for improvement are welcomed. Technical data subject to change. Siemens-Aktiengesellschaft.

3 Forward Forward Organization of the Documentation The SINAUT ST7 documentation is organized into: - User documentation - Technical documentation Targeted Readers The documentation presented here is intended for users that wish to connect WinCC to SINAUT ST7 as an operating and monitoring system. Aim of this Manual This manual provides the following know-how through the use of an example project: - Illustration of a SINAUT ST7 configuration in the WinCC data management - Configuration of the communication subscribers and objects - Explanation of WinCC preparations for messaging and archiving - Organizing an installation using typicals - Reusable units in the WinCC operating philosophy SINAUT ST7cc Manual (05/2002) iii

4 Forward Reference Aids The following orientation aids are available in the appendix in addition to the table of contents and the lists of illustrations and tables: 1. List of terms and abbreviations 2. Index Note This documentation uses the following conventions for pointing out information of special importance: Note This symbol draws your attention to information on the product, handling the product, or to a particular part of the documentation.! Important This symbol draws your attention to particularly important information on the product, handling the product, or to a particular part of the documentation. Trademarks IBM is a registered trademark of International Business Corporation. MS-DOS and WINDOWS are a registered trademarks of Microsoft Corporation. WinCC, SIMATIC, SINAUT, SINEC, STEP are trademarks of Siemens. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved iv SINAUT ST7cc Manual (05/2002)

5 Table of Contents Table of Contents Introduction to ST7cc Areas of Application Special Features Functioning as a Telecontrol Center with Convenient Diagnostics Capabilities Preprocessing of Process Data Simple, Consistent Project Engineering Note about Versions Overview of Versions Details of the Function Enhancements User Functions Diagnostic Functions System Functions Notes about Licensing Overview of Chapters Installation Installation Requirements Hardware WindowsNT4.0 Software Windows 2000 Software ST7cc Basic Installation Network Configuration for SIMATIC NET V5.x Integrating ST7cc in NetPro S7 Connection Between the Control Center TIM and ST7cc Time Service of the Control Center TIMs on the MPI Bus Network Configuration for SIMATIC NET V6.x Local Configuration of the MPI Board Integrating ST7cc in NetPro S7 Connection Between the Control Center TIM and ST7cc Time Service of the Control Center TIMs on the MPI Bus SINAUT ST7 Configuration Tools Configuring ST7 Connection to ST7cc Adding Redundant ST7cc SDB Generation of the Control Center TIM SINAUT ST7cc Manual (05/2002) v

6 Table of Contents 2.6 Loading the New SDBs into the Control Center TIM Connecting an Application Access Point Under SIMATIC NET V6.x Under SIMATIC NET V5.x Installation Settings and Base Configuration in ST7cc Config Differences between ST7cc Config Version 2 and Version Starting ST7cc Config Creating a New ST7cc Project ST7cc Administration Reading ST7cc V1 Project Settings Transferring the ST7cc V1 License Copying Faceplates into a WinCC Project Project Settings Project Settings: Server Project Settings: File Paths Project Settings: Communication Project Settings: WinCC Project Settings: Archiving Project Settings: Config Global Settings Global Settings: Computer Global Settings: Project Global Settings: License Global Settings: Redundancy License Preparation Defining Typicals Communication Configuration Use a Defined Number Range for Subscriber Numbers Configuration of Control Center TIMs in Separate Racks Send Time Stamp Automation Device Programming Preparations for WinCC Creating a WinCC Project Linking the ST7 Channel DLL Defining Message Classes and Types Creating Archives Interconnecting User Objects by their Names Working with ST7cc Config Introduction to ST7cc Configuration Terms: Objects and Typicals Term: Tag Term: Tag Typing Term: Processing Term: Typical Template and Subtypical ST7cc Configuration Procedure Naming Convention Specification of the ST7 Subscribers for ST7cc Tasks and Decoding with Object Templates Notes about Object Templates NH7998-7AA11 Siemens AG 2002 All Rights Reserved vi SINAUT ST7cc Manual (05/2002)

7 Table of Contents Dialog Notes about Handling Object Templates Decoding Using Object Templates Dialog Notes for Decoding with Object Templates Notes about Object Templates Dialog Notes about Handling Typical Templates Decoding Using Typical Templates: Dialog Notes for Decoding with Typical Templates Final Notes about Decoding Processing Configuration Message Processing Static Extra Texts Counter Value Processing Measurement Value Processing Archiving WinCC Generation Tag Management Message Management Archives Delta Mode ST7cc Config with EXCEL Erste SectionÜberschrift Erste MapÜberschrift ST7cc Server The Process Image Startup Behavior and Start Order Shutting Down the Server and WinCC Restarting WinCC While the Server is Operating ST7cc Server Status Diagnostic and Trace Possibilities Diagnostics: Log Server Messages Process Image Messages Communication Error Messages Communication Status Messages Time Synchronization Messages Parameter Error Diagnostic Messages WinCC Tag Logging / Alarm Logging Messages PM-AQUA Link Messages Diagnostics: Subscriber Typicals Faceplates: Displays Faceplates: Operator Representation in Tag Management Faceplates: Insertion into the WinCC Project Diagnostics: Server Typicals Faceplates: Displays Representation in Tag Management SINAUT ST7cc Manual (05/2002) vii

8 Table of Contents Faceplates: Detail Display Faceplates: Insertion into the WinCC Project Diagnostics: Trace Trace Output Window Diagnostic: System Typical PM-AQUA Link PM-AQUA Process Links PM-Aqua Configuration with ST7cc Config Configuring the Tags for the PM-AQUA Process Links Archiving Instructions for PM-AQUA Message Types and Data Formats Used Optimization of the Handshake Procedure ACRON Link Importing Historical Files (CSV, DBASE) Background Link for Importing Historical Values Syntax of External Variables Provider Settings Driver Parameters ACRON Project Settings with ST7cc Config ACRON Project Settings with ST7cc Config Archiving Instructions for ACRON Notes Appendix A.1 Terms / Abbreviations Index NH7998-7AA11 Siemens AG 2002 All Rights Reserved viii SINAUT ST7cc Manual (05/2002)

9 To Siemens AG I&S OCW TI D Karlsruhe, Germany Suggestions Corrections Correspondence to: SINAUT ST7 Fehler! Verweisquelle konnte nicht gefunden werden. Manual Sender Name: Address of your company/office Street: Order No.: 6NH7998-7AA11 Edition: 05/2002 If you notice typographical errors in this document please use this form to inform us. We would also be grateful for you suggestions and criticisms. ZIP: Ort: Tel.: / Fax: / Suggestions and/or corrections

10 Introduction to ST7cc 1 Installation 2 SINAUT ST7 SINAUT ST7cc Control Center Manual Preparations Working with ST7cc Config Valid for ST7cc Server 6 Product Software Version SINAUT ST7cc 2.0 This manual is applicable for all software versions up to and including version 2.x. Newer software versions will be supported by online help and readme files prior to publication of updated editions of the manual. Diagnostic and Trace Possibilities 7 The SINAUT hotline can be reached by: Tel: +49 (0) Fax: +49 (0) Hotline.ST@khe.siemens.de PM-AQUA Link 8 Internet: ACRON Link 9 Edition 05/2002 Appendix Index A I

11 SINAUT Documentation Certified Siemens Quality for Software and Training according to DIN ISO 9001, Reg. No This documentation was created with WinWord V 8.0, DesignerV6.0 and the documentation tool, AutWinDoc. The reproduction, transmission or use of this document or its contents is not permitted without express written consent. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. Siemens AG All Rights Reserved. Order No. 6NH7998-7AA11 Printed in the Federal Republic of Germany It is possible that there are operable functions in the system that are not described in this documentation. However, no claims can be made for these functions for new delivery or in cases of servicing. We have checked the contents of this manual for agreement with the hardware and software described. Deviations, however, cannot be entirely precluded. The information in this manual is reviewed regularly and any necessary corrections are included in subsequent editions. Suggestions for improvement are welcomed. Technical data subject to change. Siemens-Aktiengesellschaft.

12 Forward Forward Organization of the Documentation The SINAUT ST7 documentation is organized into: - User documentation - Technical documentation Targeted Readers The documentation presented here is intended for users that wish to connect WinCC to SINAUT ST7 as an operating and monitoring system. Aim of this Manual This manual provides the following know-how through the use of an example project: - Illustration of a SINAUT ST7 configuration in the WinCC data management - Configuration of the communication subscribers and objects - Explanation of WinCC preparations for messaging and archiving - Organizing an installation using typicals - Reusable units in the WinCC operating philosophy SINAUT ST7cc Manual (05/2002) iii

13 Forward Reference Aids The following orientation aids are available in the appendix in addition to the table of contents and the lists of illustrations and tables: 1. List of terms and abbreviations 2. Index Note This documentation uses the following conventions for pointing out information of special importance: Note This symbol draws your attention to information on the product, handling the product, or to a particular part of the documentation.! Important This symbol draws your attention to particularly important information on the product, handling the product, or to a particular part of the documentation. Trademarks IBM is a registered trademark of International Business Corporation. MS-DOS and WINDOWS are a registered trademarks of Microsoft Corporation. WinCC, SIMATIC, SINAUT, SINEC, STEP are trademarks of Siemens. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved iv SINAUT ST7cc Manual (05/2002)

14 Table of Contents Table of Contents Introduction to ST7cc Areas of Application Special Features Telecontrol Master Function with Convenient Diagnostics Capabilities Preprocessing of Process Data Simple, Consistent Project Engineering Note about Versions Overview of Versions Details of the Function Enhancements Notes about Licensing Overview of Chapters Installation Installation Requirements Hardware Windows NT4.0 Software Windows 2000 Software ST7cc Basic Installation Network Configuration for SIMATIC NET V5.x Integrating ST7cc in NetPro S7 Connection Between the Master-TIM and ST7cc Time Service of the Master-TIMs on the MPI Bus Network Configuration for SIMATIC NET V6.x Local Configuration of the MPI Board Integrating ST7cc in NetPro S7 Connection Between the Master-TIM and ST7cc Time Service of the Master-TIMs on the MPI Bus Extension of the SINAUT ST7 Project Configuring ST7 Connection to ST7cc Adding Redundant ST7cc SDB Generation for the Master-TIM Loading the New SDBs into the Master TIM Connecting an Application Access Point Under SIMATIC NET V6.x Under SIMATIC NET V5.x SINAUT ST7cc Manual (05/2002) v

15 Table of Contents 2.7 Installation Settings and Base Configuration in ST7cc Config Differences between ST7cc Config Version 2 and Version Starting ST7cc Config Creating a New ST7cc Project ST7cc Administration Reading ST7cc V1 Project Settings Transferring the ST7cc V1 License Copying Faceplates into a WinCC Project Project Settings Project Settings: Server Project Settings: File Paths Project Settings: Communication Project Settings: WinCC Project Settings: Archiving Project Settings: Config Global Settings Global Settings: Computer Global Settings: Project Global Settings: License Global Settings: Redundancy License Preparation Defining Typicals Communication Configuration Use a Defined Number Range for Subscriber Numbers Configuration of Control Center TIMs in Separate Racks Send Time Stamp Automation Device Programming Preparations for WinCC Creating a WinCC Project Adding the ST7 Channel DLL Defining Message Classes and Types Creating Archives Interconnecting User Objects by their Names Working with ST7cc Config Introduction to ST7cc Configuration Terms: Objects and Typicals Term: Tag Term: Tag Typing Term: Processing Term: Typical Template and Subtypical ST7cc Configuration Procedure Naming Convention Specification of the ST7 Subscribers for ST7cc Tasks and Decoding with Object Templates Notes about Object Templates Dialog Notes about Handling Object Templates Decoding Using Object Templates Dialog Notes for Decoding with Object Templates Notes about Object Templates Dialog Notes about Handling Typical Templates Decoding Using Typical Templates: NH7998-7AA11 Siemens AG 2002 All Rights Reserved vi SINAUT ST7cc Manual (05/2002)

16 Table of Contents Dialog Notes for Decoding with Typical Templates Final Notes about Decoding Processing Configuration Message Processing Static Extra Texts Counter Value Processing Measurement Value Processing Archiving WinCC Generation Tag Management Message Management Archives Delta Mode ST7cc Server The Process Image Startup Behavior and Start Order Shutting Down the Server and WinCC Restarting WinCC While the Server is Operating ST7cc Server Status Diagnostic and Trace Possibilities Diagnostics: Log Server Messages Process Image Messages Communication Error Messages Communication Status Messages Time Synchronization Messages Parameter Error Diagnostic Messages WinCC Tag Logging / Alarm Logging Messages PM-AQUA Link Messages Diagnostics: Subscriber Typicals Faceplates: Displays Faceplates: Operator Representation in Tag Management Faceplates: Insertion into the WinCC Project Diagnostics: Server Typicals Faceplates: Displays Representation in Tag Management Faceplates: Detail Display Faceplates: Insertion into the WinCC Project Diagnostics: Trace Trace Output Window Diagnostic: System Typical PM-AQUA Link PM-AQUA Process Links SINAUT ST7cc Manual (05/2002) vii

17 Table of Contents 8.2 PM-Aqua Configuration with ST7cc Config Configuring the Tags for the PM-AQUA Process Links Archiving Instructions for PM-AQUA Message Types and Data Formats Used Optimization of the Handshake Procedure ACRON Link Importing Historical Files (CSV, DBASE) Background Link for Importing Historical Values Syntax of External Variables Provider Settings Driver Parameters ACRON Project Settings with ST7cc Config ACRON Project Settings with ST7cc Config Archiving Instructions for ACRON Notes Appendix A.1 Terms / Abbreviations Index NH7998-7AA11 Siemens AG 2002 All Rights Reserved viii SINAUT ST7cc Manual (05/2002)

18 To Siemens AG I&S OCW TI D Karlsruhe, Germany Suggestions Corrections Correspondence to: SINAUT ST7 Fehler! Verweisquelle konnte nicht gefunden werden. Manual Sender Name: Address of your company/office Street: Order No.: 6NH7998-7AA11 Edition: 05/2002 If you notice typographical errors in this document please use this form to inform us. We would also be grateful for you suggestions and criticisms. ZIP: Ort: Tel.: / Fax: / Suggestions and/or corrections

19 Introduction to ST7cc Areas of Application Special Features Telecontrol Master Function with Convenient Diagnostics Capabilities Preprocessing of Process Data Simple, Consistent Project Engineering Note about Versions Overview of Versions Details of the Function Enhancements User Functions Diagnostic Functions System Functions Notes about Licensing Overview of Chapters SINAUT ST7cc Manual (05/2002) 1-1

20 Introduction to ST7cc 1.1 Areas of Application SINAUT ST7cc is the ideal Control Center System based on SIMATIC WinCC for both SINAUT ST7 and SINAUT ST1. It is specially tuned to the event-driven and time-stamped data communication of the SINAUT system. It avoids potential data loss arising from cyclic polling in WinCC. It also guarantees for all WinCC alarm, event and archive entries the use of the exact time of events supplied by the SINAUT stations. The process image integrated in ST7cc contains all process data as well as the status of all SINAUT subscribers in the network and makes this data immediately available to WinCC for fast process image application. The ST7ccConfig configuration tool provides the user with comprehensive engineering capability based on the data messages, which have been configured in the SINAUT ST7 or ST1 stations. The configuration of WinCC, including the tag management, is generated automatically and remains consistent when changes are made. The WinCC add-ons PM-AQUA or ACRON are recommended for archiving, logging and reporting based on ATV Report H260 or Hirthammer. ST7cc offers a configurable data interface to these add-ons. ST7cc ST7ccConfig WinCC ST7-Server MPI DCF77 GPS TIM TIM WAN WAN ST7 ST7 ST7 ST1 ST1 ST1 Fig. 1-1 SINAUT ST7cc (single or redundant) with connected ST7 and ST1 stations 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 1-2 SINAUT ST7cc Manual (05/2002)

21 Introduction to ST7cc One or more SINAUT ST7 TIM communication processors can connected directly via the standard S7 MPI bus. Both ST7 and ST1 stations can be connected to these TIMs (see Fig. 1-1). One of the local TIMs should be equipped with a DCF77 receiver in order to provide the current time of day. This TIM will then serve as the central time synchronization source for ST7cc and all stations. (It is not possible to time synchronize the SINAUT network from ST7cc!) Outside the regions where the DCF77 time signal is received, a GPS receiver is recommended to determine the local time through the satellite-based GPS system (Global Positioning System). SINAUT ST7cc Manual (05/2002) 1-3

22 Introduction to ST7cc 1.2 Special Features Telecontrol Master Function with Convenient Diagnostics Capabilities Direct connection of SINAUT ST7 TIMs to ST7cc via MPI. A separate CPU as telecontrol master is not required. Provides the main status information about every SINAUT ST7 or ST1 subscriber with visualization in WinCC using supplied station typicals (faceplates). These station typicals can be used to control the SINAUT subscribers. Marking of process values from subscriber stations with disrupted connections to ST7cc. General requests of affected stations after transmission disruptions have ended for updating the process image in ST7cc. For test purposes: Recording of message traffic with all or with selected SINAUT subscribers Preprocessing of Process Data Preprocessing can be configured for binary, analog and counter values. It takes into account the time of events, and derived alarm, event and archive entries are provided with correct time stamps. Binary information Binary information can be interpreted as single or multi-state signals. Entry of current binary values in the corresponding WinCC tags. Entry of derived events and alarms in the WinCC alarm logging system while taking the time stamps supplied by SINAUT ST7 or ST1 into consideration. Analog values (instantaneous and mean values) Linear scaling (non-scaled value physical value) Entry of scaled analog values in the corresponding WinCC tags Entry of scaled analog values in the WinCC archive while taking the time stamps supplied by SINAUT ST7 or ST1 into consideration Counter values Overflow processing for absolute counters Counter value scaling with factors Formation of correctly timed interval quantities Entry of current accumulate interval quantities in the assigned WinCC tags. Entry of completed interval quantities in the WinCC archive while taking the time stamps supplied by SINAUT ST7 or ST1 into consideration Setpoints Linear scaling (physical value non-scaled value) when required 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 1-4 SINAUT ST7cc Manual (05/2002)

23 Introduction to ST7cc Simple, Consistent Project Engineering ST7ccConfig allows user-friendly configuration of the total system. There is no need for additional WinCC configuration of the tag management, archiving or alarm logging system. SINAUT ST7cc Manual (05/2002) 1-5

24 Introduction to ST7cc 1.3 Note about Versions Overview of Versions ST7cc Version V2.0 can be operated under both Windows NT and Windows In addition to numerous other new functions, ST7cc V2.0 also supports redundant WinCC configurations. New features have been added to both the user and system functions. Table 1-1 ST7cc function enhancements in V2.0 compared to V1.4 Windows NT Windows 2000 Redundant System Single System Function Enhancements Redundant System Single System Function Enhancements Basic Functions Version V Details of the Function Enhancements User Functions The following function enhancements in version V2.0 are available in both Windows NT and Windows bit floating-point values can be received and sent. The tag typing has been supplemented correspondingly: - Type M with subtype 4 for receiving floating-point values - Type A with subtype 4 for sending floating-point values to the automation level. All dialogs for "Project Settings and "Global Settings have been changed. New faceplate for monitoring the server status. New function in the ST7cc configuration tool (ST7ccConfig) for copying all faceplates (station and server faceplates) into the appropriate WinCC project The ST7cc configuration tool (ST7ccConfig) can be started from the WinCC Explorer. Changes are automatically detected when ST7ccConfig is closed. The user is subsequently prompted to save the changes. Single and redundancy licenses are entered in the ST7cc configuration tool. They can no longer be entered in the ST7cc server. The configuration data of the ST7cc server can be opened and edited in EXCEL. Diagnostic Functions Improved trace function: Up to four separate traces can be written to separate trace files. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 1-6 SINAUT ST7cc Manual (05/2002)

25 Introduction to ST7cc System Functions Projects have to be saved in a project directory. The following files are located in a project directory: Table 1-2 File name ST7_PROJECT.XML ST7_PROJECT.TXT Content of the ST7cc project directory ST7_PROJECT_ENGLISH.TXT ST7_TYPICALS.TXT ST7_TYPICALS_ENGLISH.TXT ST7_PROJECT.MMF ST7_PROJECT_db_queue.mmf ST7_PROJECT_local.mmf ST7_PROJECT_remote.mmf ST7_PROJECT_pma_queue.mmf Description Init file with all project settings ST7cc project file in German ST7cc project file in English ST7cc typical file in German (library) ST7cc typical file in English (library). Process image WinCC data buffer. Message buffer for buffering all process messages when WinCC Runtime is not active Message buffer for updating the remote partner computer (redundancy partner) PM-AQUA data buffer. All project setting previously written to the Windows NT registry are now saved in the init file, ST7_PROJECT.XML, so they are now located in the project directory. All global settings (computer settings) are saved irrespective of the project in various files located in the directory "C:\SIEMENS\ST7CC\base\. The library is displayed only after a project is opened. The library is located in the project directory and is therefore attached to the project. The project init file "ST7_PROJECT.XML has to be selected to open a project. The ST7cc project can be created in the WinCC project directory. An ST7cc directory is automatically created in the WinCC project directory when a WinCC project is created. The ST7cc server and the log server are divided into separate programs. Advantage: The log window remains visible even when the ST7cc server is started in the background. Process communication decoupled from WinCC. Advantage: The communication between ST7cc and the ST7 stations continues even when WinCC is deactivated or closed. All messages are temporarily saved in the local buffer (ST7_PROJECT_local.mmf ). After restart of WinCC the WinCC tag management and the WinCC archives can immediately be updated from this local buffer. A time-consuming data gathering from the telecontrol stations is no more required. SINAUT ST7cc Manual (05/2002) 1-7

26 Introduction to ST7cc 1.4 Notes about Licensing SINAUT ST7cc requires a WinCC Complete Package License *) and runs together with WinCC on a PC under Windows NT or Windows For the redundant ST7cc the WinCC Redundancy Package is required. The following table lists the individual software packages required for single and redundant ST7cc systems. ST7cc Single System Qty. Software Package ST7cc Redundant System Qty. Software Package 1 Windows NT4.0 or Windows NT4.0 or WinCC Complete Package 1 WinCC Complete Package *) 1 SW ST7cc S (with license for 6 stations ) or SW ST7cc M (with license for 12 stations) or SW ST7cc L (with license for > 12 stations ) 1 WinCC Runtime Package 1 WinCC Redundancy Package (with 2 licenses) 1 ST7cc Redundancy Package (with 2 licenses) 2 SW ST7cc S (with license for 6 stations) or SW ST7cc M (with license for 12 stations) or SW ST7cc L (with license for > 12 stations) *) Runtime Package instead of Complete Package possible if there is no need for project configuration on the end-user PC. The following table describes the ST7cc capacity levels (S, M, L) and the corresponding licenses needed. Short name Order No. Description SW ST7CC S 6NH7997-7CA15-0AA1 Software ST7cc as add-on for WinCC (Windows NT/2000), for connecting a max. of 6 SINAUT ST7 and ST1 stations, consists of ST7 server and ST7ccConfig configuration tool. SW ST7CC M SW ST7CC L SW ST7CC R LE ST7CC SM LE ST7CC SL LE ST7CC ML 6NH7997-7CA15-0AA2 6NH7997-7CA15-0AA3 6NH7997-8CA15-0AA0 6NH7997-7AA00-0AD2 6NH7997-7AA00-0AD3 6NH7997-7AA00-0AE3 MANUAL ST7CC D 6NH7998-7AA11 Software ST7cc as add-on for WinCC (Windows NT/2000), for connecting a max. of 12 SINAUT ST7 and ST1 stations, consists of ST7 server and ST7ccConfig configuration tool. Software ST7cc as add-on for WinCC (Windows NT/2000), for connecting any number of SINAUT ST7 and ST1 stations, consists of ST7 server and ST7ccConfig configuration tool. Software ST7cc R (redundancy package, contains 2 licenses) as add-on for the WinCC redundancy package (Windows NT/2000), for connecting SINAUT ST7 and ST1 stations. 2 ST7 server licenses SWST7CC S, M or L, are also required. License upgrade SW ST7CC S to SW ST7CC M (6 substations 12 substations) License upgrade from SW ST7CC S to SW ST7CC L (6 substations unlimited number of substations) License upgrade from SW ST7CC M to SW ST7CC L (12 substations unlimited number of substations) SINAUT ST7cc Manual, German MANUAL ST7CC E 6NH7998-7AA21 SINAUT ST7cc Manual, English 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 1-8 SINAUT ST7cc Manual (05/2002)

27 Introduction to ST7cc 1.5 Overview of Chapters Note about Chapter 2 Chapter 2 describes all of the steps required for installation. ST7cc can be operated under both Windows NT and Windows 2000 operating systems. This requires, however, two different versions of the SIMATIC NET communication software used for the communication between the PC and TIM. Chapter 2 describes the differences between the two installation procedures. The reader should pay special note to these differences. Note about Chapter 3 Chapter 3 deals with the tasks that should be executed before you start working with the ST7cc configuration tool (ST7ccConfig). The main topics are: "Linking the ST7 Channel DLL", "Defining Message Classes and Types", "Configuring Archives", "Creating Faceplates". Note about Chapter 4 Chapter 4 describes The various terms in their context. The background information necessary to understand the mapping of ST7 communication objects to WinCC tags. This mapping is also called "decoding". The dialog routines for the decoding of the ST7 communication objects. The ST7cc preprocessing that is performed during the decoding of the ST7 communication objects. Note about Chapter 6 Chapter 6 explains all the important details of the ST7cc server (components, initial startup and subsequent startup). Note about Chapter 7 In Chapter 7 informs you about the diagnostics and trace functions of ST7cc. Note about Chapter 8 Chapter 8 describes the connection to PM-AQUA. Note about Chapter 9 Chapter 9 describes the connection to ACRON. SINAUT ST7cc Manual (05/2002) 1-9

28 Introduction to ST7cc 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 1-10 SINAUT ST7cc Manual (05/2002)

29 Installation Installation Requirements Hardware Windows NT4.0 Software Windows 2000 Software ST7cc Basic Installation Select Setup Language New Installation Update Installation Network Configuration for SIMATIC NET V5.x Integrating ST7cc in NetPro S7 Connection Between the Master-TIM and ST7cc Time Service of the Master-TIMs on the MPI Bus Network Configuration for SIMATIC NET V6.x Local Configuration of the MPI Board Integrating ST7cc in NetPro S7 Connection Between the Master-TIM and ST7cc Time Service of the Master-TIMs on the MPI Bus Extension of the SINAUT ST7 Project Configuring ST7 Connection to ST7cc Adding Redundant ST7cc SDB Generation for the Master-TIM Loading the New SDBs into the Master TIM Connecting an Application Access Point Under SIMATIC NET V6.x Under SIMATIC NET V5.x Installation Settings and Base Configuration in ST7cc Config Differences between ST7cc Config Version 2 and Version Starting ST7cc Config Creating a New ST7cc Project ST7cc Administration Reading ST7cc V1 Project Settings SINAUT ST7cc Manual (05/2002) 2-1

30 Installation Transferring the ST7cc V1 License Copying Faceplates into a WinCC Project Project Settings Project Settings: Server Time response Options Project Settings: File Paths Process Image Local Buffer Remote Buffer Project Settings: Communication Project Settings: WinCC General WinCC Buffer WinCC Message Blocks Project Settings: Archiving General PM-AQUA ACRON Project Settings: Config General Texts for initializing new objects Global Settings Global Settings: Computer Server Server Activation Global Settings: Project Information Activation Global Settings: License Global Settings: Redundancy License NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-2 SINAUT ST7cc Manual (05/2002)

31 Installation 2.1 Installation Requirements Note to the Reader: SINAUT ST7cc can be installed for both Windows NT4.0 and Windows The chapter heading describing the differences between the installations is given when the procedures deviate from one another Hardware The installation requirements are the same as those for WinCC. In addition the following disk space is needed for ST7cc: ST7cc program: approx. 25 Mbytes ST7cc project: 200 to 400 Mbytes Windows NT4.0 Software The following software is required to install ST7cc for Windows NT4.0: Windows NT4.0 installation with Service Pack 6 or later WinCC V5.0 installation with Service Pack 2 or later SIMATIC NET PB SOFTNET-S7 V5.x installation SINAUT Configuration Tool V3.1.1 or later Windows 2000 Software The following software is required to install ST7cc for Windows 2000: Windows 2000 installation with Service Pack 1 or later WinCC V5.0 installation with Service Pack 2 or later SIMATIC NET PB SOFTNET-S7 V6.x installation SINAUT ST7 Configuration Tool V3.1.1 or later SINAUT ST7cc Manual (05/2002) 2-3

32 Installation 2.2 ST7cc Basic Installation Insert the installation CD into your CD drive and open it with the Explorer, doubleclick on Setup.exe to begin the installation. Note Before starting the ST7cc installation WinCC and the previous version of ST7cc Runtime and ST7cc Config need to be closed, otherwise the new files cannot be copied completely. Select Setup Language You can select the desired setup language in the window that first appears. The following options are offered: German (Germany) English (USA) Fig. 2-1 Language selection for the setup dialog After the selection of the setup language, Setup searches for previous installations on your system and automatically begins an update or new installation. 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-4 SINAUT ST7cc Manual (05/2002)

33 Installation New Installation For a new installation enter your name and the name of your company in the user information window. Fig. 2-2 User information dialog window Update Installation The "base directory contains the existing configuration and is not overwritten when an update installation is performed. All of the files from the ST7cc CD located in the "base directory are copied to "base_default. Some of the files in this directory may be kept. Fig. 2-3 Configuration information for an update installation SINAUT ST7cc Manual (05/2002) 2-5

34 Installation Now select the drive and the directory in which you wish to install ST7cc. Fig. 2-4 Directory selection dialog for the ST7cc installation All of the files are now copied to the hard disk and the various environment variables are set. When copying is completed, you are given the opportunity to read the Readme file. Fig. 2-5 Readme file prompt 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-6 SINAUT ST7cc Manual (05/2002)

35 Installation Once the installation is successfully completed, you need to reboot your computer in order for the new or altered environment variables to take effect. Fig. 2-6 Exit dialog of the setup program SINAUT ST7cc Manual (05/2002) 2-7

36 Installation 2.3 Network Configuration for SIMATIC NET V5.x Integrating ST7cc in NetPro Start the SIMATIC Manager and open your S7 project. Now start the SIMATIC NetPro tool by double-clicking on the "Configure Network" button in the menu bar of the SIMATIC Manager. Insert "PG/PC from your catalog into your network configuration. Double-click on the PG/PC icon to open the configuration window "PG/PC Properties. The following settings can be made in this properties window: General: Interface: Assignment: Change the name from "PG/PC to a descriptive name of your choice. Enter the MPI interface and an MPI address. Assign the PC interface board (e.g. CP5611). Note Two PG/PC stations need to be integrated for redundant ST7cc. The stations are then assigned to a subscriber using the SINAUT Subscriber Administration. This procedure is supported beginning with TIM firmware V3.58 and SINAUT Configuration Tool V3.1. Two PG/PC stations need to be integrated for redundant ST7cc. Fig. 2-7 Integrating ST7cc in NetPro 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-8 SINAUT ST7cc Manual (05/2002)

37 Installation S7 Connection Between the Master-TIM and ST7cc The ST7 configuration tool cannot automatically create connections between ST7cc and the Master-TIMs on the local MPI. These connections therefore need to be manually configured as follows: 1. In NetPro select the Master-TIM on the ST7cc MPI bus to be connected. 2. An empty connection list appears in the lower part of the NetPro window. 3. Click on the connection list with the right mouse button to create a new connection. As the connection partner select 'PG/PC' which is provided for ST7cc and 'S7 connection' as the connection type. 4. Now click on the "Accept button. The subsequent dialog "Properties S7 Connections does not need to be modified. 5. Click on the "Address Details button to check if the following address information is correctly set: Computer A: Fig. 2-8 Displaying the address details for computer A Computer B: Fig. 2-9 Displaying the address details for computer B SINAUT ST7cc Manual (05/2002) 2-9

38 Installation These parameters are referenced in ST7cc's connection database "st7_10.ldb for STEP7 V4 or "st7_11.ldb for STEP7 V5. The entries for the fields "Connection name and "VFD name can be freely selected. Note that the names for computer A and computer B need to be different for redundant ST7cc. Only the following results of the connection configuration for ST7cc are of interest: Subscriber numbers of all the configured subscribers (TIMs and S7 CPUs) MPI addresses of all TIMs addressed by the ST7cc server on the local MPI These numbers can be entered later in the communication settings in ST7cc Config Time Service of the Master-TIMs on the MPI Bus The Master-TIM is the time master on the MPI bus and synchronizes all ST7cc computers connected to this bus. Note The PC cannot be used as the time master. Open the properties menu by double-clicking on the Master-TIM in NetPro. Select the "Time Services" tab in this window. Time synchronization on the MPI/Partyline bus must be to set to a minute. Set the synchronization to a minute scheme. Note The time synchronization interval on the MPI bus must always be to set to one minute for ST7cc. Now save your NetPro configuration changes by clicking on the "Save and Compile button. It suffices to compile only the changes. NetPro can be closed once the compilation has been completed without error. 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-10 SINAUT ST7cc Manual (05/2002)

39 Installation 2.4 Network Configuration for SIMATIC NET V6.x Local Configuration of the MPI Board Start the SIMATIC NET startup wizard by opening "Start/SIMATIC/SIMATIC NET/Settings/Commissioning Wizard. Fig Starting dialog for the SIMATIC NET Commissioning Wizard When the Commissioning Wizard is started for the first time, the program automatically scans for previously installed modules. A configuration window is displayed for each module found. These windows may appear different on your computer depending on the board installed. In the installation example an Ethernet board named " Com Etherlink XL and a "CP5611 MPI board are installed on the computer. Note The module configuration windows shown below no longer appear when the Commissioning Wizard is called up again. SINAUT ST7cc Manual (05/2002) 2-11

40 Installation The Ethernet module is not used for communication between ST7cc and the Master-TIM. Select the line "Use module for PG operation only. Fig SIMATIC NET Ethernet module Select "Use module for productive operation in configured PC station The bus profile has to be "DP. Enter your PC s MPI address here. The transmission speed has to be set to Kbs. Fig SIMATIC NET MPI module The OPC server is not used. Deactivate the line "SIMATIC NET OPC server in configured PC station. Fig SIMATIC NET deactivate OPC server Save the configuration once you have configured the installed boards. Respond to the warning prompt displayed by pressing OK. 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-12 SINAUT ST7cc Manual (05/2002)

41 Installation Fig Saving the module configuration Fig Prompt in the SIMATIC NET Startup Wizard Now open the Configuration Wizard by clicking on the "Configuration Wizard" button in the Startup Wizard. Fig SIMATIC NET Startup Wizard In the window that now appears select Change local settings in the first form, and Change hardware configuration in the second form (Module Properties, DP). SINAUT ST7cc Manual (05/2002) 2-13

42 Installation Fig SIMATIC NCM PC Configuration Wizard Fig Settings in the SIMATIC NET Startup Wizard The hardware configuration is now displayed with a local project. The following must be inserted into the empty rack: An application in slot 1: Name this application ST7. The communication module in slot 4 (e.g. CP5611): The interface should be set as follows: Type: MPI Address: e.g. 30 In network: Yes 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-14 SINAUT ST7cc Manual (05/2002)

43 Installation Note When it is first installed it is usually not possible to select MPI as the interface type. In this case select Profibus as the type. Then call up the object properties in the context menu (right mouse button) and change the interfaces parameter to the setting described above. A station manager in slot 125: This is entered automatically and does not have to be changed. Fig HW Config for the local configuration Once you have saved the hardware configuration of the local project and closed the program, the setup window "Component Configurator" needs to be started using the Configuration Wizard. In the Component Configurator enter the same name for the station (default: PC station) as the one given to the PC Station icon in your project. Note The station name entered here must be identical to the name that is used in Netpro for the PC station in your project. SINAUT ST7cc Manual (05/2002) 2-15

44 Installation Fig Component Configurator After you have closed the Component Configurator, complete the installation of the Startup Wizard using the next to windows that appear. Fig Symbolics for the SIMATIC NET Startup Wizard 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-16 SINAUT ST7cc Manual (05/2002)

45 Installation Fig Completing the SIMATIC NET Startup Wizard You can now check your settings once again in the automatically displayed configuration console "Configure PC Station. To load the updated configuration into the communication module (e.g. CP5611) of your PC you will have to call up HW Config again with the project "locproj. You can use the Startup Wizard again to do this. Load the hardware configuration into the CP5611 module of your PC. Fig HW Config for the local configuration SINAUT ST7cc Manual (05/2002) 2-17

46 Installation Integrating ST7cc in NetPro Start the SIMATIC Manager and open your S7 project. Now start the SIMATIC NetPro tool by double-clicking on the "Configure Network" button in the menu bar of the SIMATIC Manager. Insert a "PG/PC station from your catalog into your network configuration. Open the Object Properties from the context menu (right mouse button) for the installed PC Station and now change the station name to match your entry in Component Configurator. Note The station name entered here must be identical to the name that is used for the PC station in the Component Configurator called up from the Startup Wizard. Make sure that the station names match. Two PC stations need to integrated for redundant ST7cc. Fig NetPro integrating PC stations Double-click on the "PC Station" icon to open the hardware configuration tool HW Config. The following must be inserted into the empty rack: An application in slot 1: Name this application ST7. 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-18 SINAUT ST7cc Manual (05/2002)

47 Installation The communication module in slot 4 (e.g. CP5611): The interface should be set as follows: Type: MPI Address: e.g. 30 In network: Yes (MPI bus) Note When it is first installed it is usually not possible to select MPI as the interface type. In this case select Profibus as the type. Then call up the object properties in the context menu (right mouse button) and change the interfaces parameter to the setting described above. A station manager in slot 125: This is entered automatically and does not have to be changed. Fig HW Config for the configured PC station SINAUT ST7cc Manual (05/2002) 2-19

48 Installation S7 Connection Between the Master-TIM and ST7cc The ST7 configuration tool cannot automatically create connections between ST7cc and the Master-TIMs on the local MPI. These connections therefore need to be manually configured as follows: 1. In NetPro select the "Application" in the ST7cc PC station to be connected. 2. An empty connection list appears in the lower part of the NetPro window. 3. Click on the connection list with the right mouse button to create a new connection. Select "Master-TIM" as the connection partner and "S7 Connection" as the connection type. 4. Now click on the "Close" button to activate the settings and close the window. 5. Open the Object Properties once again from context menu for this entry (right mouse button) and change the name for the local ID as follows: Old entry S7 Connection_1 3_1 New entry (3 is the MPI address of the Master-TIM and has to match the one used in your project) 6. Now click on the "OK" button to activate the settings and close the window. 7. If you are using redundant ST7cc, select the second PC station and repeat steps 1-6. Computer A: Fig S7 connection properties for computer A 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-20 SINAUT ST7cc Manual (05/2002)

49 Installation Computer B: Fig S7 connection properties for computer B Only the following results of the connection configuration for ST7cc are of interest: Subscriber numbers of all the configured subscribers (TIMs and S7 CPUs) MPI addresses of all TIMs addressed by the ST7cc server on the local MPI These numbers can be entered later in the communication settings in ST7cc Config Time Service of the Master-TIMs on the MPI Bus The Master-TIM is the time master on the MPI bus and synchronizes all ST7cc computers connected to this bus. Note The PC cannot be used as the time master. Open the properties menu by double-clicking on the Master-TIM in NetPro. Select the "Time Services" tab in this window. Time synchronization on the MPI/Partyline bus must be to set to a minute. Set the synchronization to a minute scheme. Note The time synchronization interval on the MPI bus must be to set to one minute for ST7cc. Now save your NetPro configuration changes by clicking on the "Save and Compile button. It suffices to compile only the changes. NetPro can be closed once the compilation has been completed without error. SINAUT ST7cc Manual (05/2002) 2-21

50 Installation 2.5 Extension of the SINAUT ST7 Project Configuring ST7 Connection to ST7cc Start the SINAUT ST7 Configuration Tool with the command sequence "Start/Simatic/SINAUT ST7/Configuration. Open your S7 project and select the connection configuration. Now enter all connections between ST7cc and your stations listed in the field "Possible connections into the field "Configured connections. Once you have saved your changes close the "Connection Configuration" window and open the "Subscriber Administration window Adding Redundant ST7cc You can skip this section if you are not using redundant ST7cc. Check all of the subscriber numbers by selecting the node "All SINAUT Subscribers" on the left side of the display window. Any changes necessary can now be made to the SINAUT subscriber numbers. Note The combination of two ST7cc installations to form a single SINAUT subscriber described in the following is supported by SINAUT Configuration Tool V3.1 or later. You can add a redundant ST7cc, as shown in the illustration below, by combining two separate ST7cc subscriber numbers and then assigning an existing subscriber number to one of two combined subscribers. Fig Creating a common subscriber for redundant ST7cc 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-22 SINAUT ST7cc Manual (05/2002)

51 Installation Now both ST7cc installations can be addressed through one subscriber number. Subscriber number for ST7cc_Server1 Subscriber number for ST7cc_Server2 Shared subscriber number for both ST7cc_Servers Fig ST7 Subscriber Administration SDB Generation for the Master-TIM Check all subscriber numbers again and then click on the Save icon to generate and save the SDBs. Fig Subscriber Administration dialog for generating the SDBs for the Master-TIM SINAUT ST7cc Manual (05/2002) 2-23

52 Installation In the window now displayed select System data blocks for TIMs and CPUs SINAUT TD7 blocks for all CPUs Subscriber number as the comment for stations, CPUs and TIMs Once the generation has completed without error or warnings, the SINAUT Configuration tool can be closed Loading the New SDBs into the Master TIM Open the SIMATIC Manager and load your S7 project. Connect your PC to the Master-TIM using MPI. In the SIMATIC Manager select the Master-TIM and load all SDBs. Click on this icon to start the download. Fig Main dialog of the SIMATIC Manager The TIM resets once all of the SDBs have been loaded into it. Once the TIM has restarted, the time of day in the TIM is reset when no DCF module is available. 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-24 SINAUT ST7cc Manual (05/2002)

53 Installation 2.6 Connecting an Application Access Point Under SIMATIC NET V6.x You can skip this section if you are using SIMATIC NET V6.x. In SIMATIC NET V6.x the application access point is configured by the Startup Wizard and should already be available if all of the steps described above have been performed correctly. This can be checked with the SIMATIC NET tool "Configure PC Station. CP_L2_1: Application access point for ST7cc. "CP5611(Profibus) is always displayed as the interface parameter although MPI is set. Fig SIMATIC NET V.6 access points SINAUT ST7cc Manual (05/2002) 2-25

54 Installation Diagnostics for the local MPI board Fig SIMATIC NET V.6 network diagnostics Display of all accessable MPI addresses. Fig SIMATIC NET V.6 available bus subscribers It is not necessary to create the file "ST7.ldb as a connection database. The connection database is created automatically by the SIMATIC NET Startup Wizard. The files created have the name extension "xdb". 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-26 SINAUT ST7cc Manual (05/2002)

55 Installation Under SIMATIC NET V5.x In this step you will need to connect the access point CP_L2_1 with the MPI driver of your communication processor. To do this start the program "Configure PG/PC Interface from the menu "Start / Settings / Control Panel. Once the program has started select the access point CP_L2_1; if the access point does not yet exist select the menu command Interface "Add/Remove to create this access point. Fig Dialog for configuring the PG/PC interface Click on the "Properties" button to set the MPI address and the SAPI-S7 database for this PC. Enter the MPI address in the "MPI tab. Enter the same MPI address as the one set for ST7cc in Netpro. The connection database, st7_10.ldb or st7_11.ldb, supplied for SAPI-S7 has to be specified in the "SAPI-S7 tab. To do this click on the "Browse button and select the desired file from your directory "c:\siemens\st7cc\ldb. For redundant computers the st7_10.ldb file should be selected for Computer_A and the st7_11.ldb file for Computer_B. Note There is no "SAPI-S7 tab when "SIMATIC NET PB SOFTNET-S7 V5.x is not installed. SINAUT ST7cc Manual (05/2002) 2-27

56 Installation Once the settings have been made the connection can be tested. To do this click on the "Diagnostics" button in the main window of the "Access Path". Fig Dialog for configuring and testing connections Now when you press the "Test button, the operating status of the connection will be tested and displayed. Click on the "Read" button to display the MPI addresses of all the available bus subscribers. 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-28 SINAUT ST7cc Manual (05/2002)

57 Installation 2.7 Installation Settings and Base Configuration in ST7cc Config Differences between ST7cc Config Version 2 and Version 1 Projects have to be saved in a project directory. The following files are located in a project directory: Table 2-1 File name ST7_PROJECT.XML ST7_PROJECT.TXT Content of the ST7cc project directory ST7_PROJECT_ENGLISH.TXT ST7_TYPICALS.TXT ST7_TYPICALS_ENGLISH.TXT ST7_PROJECT.MMF ST7_PROJECT_db_queue.mmf ST7_PROJECT_local.mmf ST7_PROJECT_remote.mmf ST7_PROJECT_pma_queue.mmf Description Init file with all project settings ST7cc project file in German ST7cc project file in English ST7cc typical file in German (library) ST7cc typical file in English (library). Process image WinCC data buffer. Message buffer for buffering all process messages when WinCC runtime in not active Message buffer for updating the remote partner computer (redundancy partner) PM-AQUA data buffer. All project settings, which were previously written in the Windows NT registry, are now saved in the init file, ST7_PROJECT.XML, so they are now located in the project directory. All global settings (computer settings) are saved individually for each project in various files located in the directory "C:\SIEMENS\ST7CC\base\. All data entry forms for "Project Settings and "Global Settings have been changed. Single and redundancy licenses are entered in the ST7ccConfig tool. They can no longer be entered in the ST7cc server. New faceplate for monitoring the ST7cc server Function for copying all faceplates (station and server faceplates) into the WinCC project. The library is displayed only after a project is opened. The library is located in the project directory and is therefore attached to the project. The project init file "ST7_PROJECT.XML has to be selected to open a project. The ST7cc project can be created in the WinCC project directory. An ST7cc directory is automatically created in the WinCC project directory when a WinCC project is created. ST7cc Config can be started from the WinCC Explorer. Changes are automatically detected when ST7ccConfig is closed. You are prompted to save your changes in the next dialog window. SINAUT ST7cc Manual (05/2002) 2-29

58 Installation Fig Dialog for selecting the ST7cc data records to be saved Starting ST7cc Config Start "ST7cc Config with the menu sequence displayed below. Fig Starting the ST7cc Configuration Tool "ST7ccConfig" ST7ccConfig is always started without a loaded project. 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-30 SINAUT ST7cc Manual (05/2002)

59 Installation Creating a New ST7cc Project To create a new ST7cc project select the menu command File / New. If you want to save the project in the WinCC project directory, change to the directory "ST7cc in your WinCC project as shown in the illustration below. Select here the "ST7cc" directory in the WinCC project. A file name is not required. This entry field should not be modified. Fig. 2-39: Dialog for selecting an ST7cc project in the WinCC project Now click on the "Open" button to create the project. After this the window will be closed automatically. If you want to save the project in a special project directory, create a new directory as shown in the illustration below. Button for creating a new project directory. A file name is not required. This entry field should not be modified. Fig. 2-40: Dialog for creating a new project directory Now open the new directory by double-clicking on the directory name and then press the "Open button to create the project. After this the window will be closed automatically. SINAUT ST7cc Manual (05/2002) 2-31

60 Installation Once the project is created the library and the internal system subscriber 0 System are displayed. Two objects are located under Subscriber 0 : The tags in Object 1 allow you to display the server status of Server1 and Server2 in the faceplates supplied in WinCC. The typical instance Server2 can be deleted if you are not using a redundant system. Object 10 in Subscriber 0 is reserved for PM-AQUA. This object can be deleted if you are not using PM-AQUA ST7cc Administration The "Admin" menu offers you the following options: Read ST7cc V1 project options... Transfer ST7cc V1 license... Copy faceplates to WinCC project... Fig Options of the "Admin" menu The individual options are described below Reading ST7cc V1 Project Settings The function "Read ST7cc V1 Project Settings" enables you to transfer all project settings of a Version 1 project, that is available on the PC, into a Version 2 project. All project settings from the Windows NT registry will be transfered into the init file, "ST7_PROJECT.XML of the Version 2 project. Before the project settings can be transfered it is required that a new Version 2 project has been created (see 2.7.3). After that the transfer into the new created project can be started via Admin / Read ST7cc V1 project options... Note No files are copied into the newly created project directory. Only the file paths are adapted to the old directory (e.g. D:\Siemens\St7cc\Data). If you want to have the specific project files to be located in the new project directory, they will need to be copied manually into the project directory. The file paths then have to be adapted to the new directory (see ).! Important After importing a project from ST7cc Version 1, the project must be saved in "ST7ccConfig, closed and restarted. The project and its object tree can only be displayed after the restart of the configuration tool. 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-32 SINAUT ST7cc Manual (05/2002)

61 Installation Transferring the ST7cc V1 License Select the command "Transfer ST7cc V1 License in the "Administration menu. Pay heed to the warning illustrated below. However, if you have just upgraded your computer from ST7cc Version 1 to Version 2, acknowledge the warning by pressing the OK button. Fig. 2-42: Warning about transfer of a license from Version V1 to V Copying Faceplates into a WinCC Project Select the command "Copy faceplates into WinCC project in the "Administration menu. In the window that appears search for your WinCC project directory and select the MCP project file. Fig Dialog for selecting the WinCC project file The following faceplate files are now copied into your WinCC project: Name Station_typical.pdl Fpl_1.pdl Fpl_1_english.pdl Server_typical.pdl Server_fpl1.pdl Server_fpl1_english.pdl Description Faceplate for monitoring stations and Master TIMs (Station Typical). Pop-up menu for Station Typical (in German). Pop-up menu for Station Typical (in English). Faceplate for monitoring the ST7cc Server (Server Typical). Pop-up menu for Server Typical (in German). Pop-up menu for Server Typical (in English). SINAUT ST7cc Manual (05/2002) 2-33

62 Installation Project Settings The project settings can be opened by the "Edit/Project Settings" menu command or with "F2. The following sections describe the range of settings under the individual registry tabs Project Settings: Server Fig Project settings for the ST7cc server Time response Function: Possible settings: Default: Description: Max. time deviation of received messages Positive time in seconds Negative time in days + 60 seconds 30 days If the time of day is running more than 60 sec. ahead in the Master-TIM or station, the time synchronization no longer works. The clock has to be reset manually to the correct time. The event time stamp of the message may not be older than 30 days. Function: Timeout subscriber status Possible settings: Time in seconds Default: 30 seconds Description: Setting without function beginning with Version 2. 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-34 SINAUT ST7cc Manual (05/2002)

63 Installation Function: Possible settings: Default: Description: Function: Possible settings: Default: Description: Function: Possible settings: Default: Description: Timeout GR start Time in seconds 60 seconds Maximum time until GR start is reported back by station. This time should be increased for dial-up stations. Timeout GR end Time in seconds 60 seconds Maximum transmission time between GR start and GR end Save process images Time in minutes 1 minute Process image is saved every minute on the disk as ST7_PROJECT.MMF. This setting should not be changed. Function: ST1 AE1 max. object no. Possible settings: --- Default: 100 Description: Maximum object number. Only relevant for ST1 with extended addresses. Function: ST1 AE1 index multiplier Possible settings: --- Default: 100 Description: Index multiplicator. Only relevant for ST1 with extended addresses. Options Function: Possible settings: Default: Description: Function: Possible settings: Default: Description: Function: Possible settings: Default: Description: Configuration is redundant active not active not active Activate update to redundancy partner WinCC channel DLL active active not active active This function can be deactivated when WinCC is not used as a control and monitoring system. The two functions "WinCC channel DLL active and "WinCC ODK active should always have the same status. WinCC ODK active active not active active This function can be deactivated when WinCC is not used as a control and monitoring system. The two functions "WinCC channel DLL active and "WinCC ODK active should always have the same status. SINAUT ST7cc Manual (05/2002) 2-35

64 Installation Function: Possible settings: Default: Description: Function: Possible settings: Default: Description: Function: Possible settings: Default: Description: Function: Possible settings: Default: Description: Function: Possible settings: Default: Description: Function: Possible settings: Default: Description: Time synchronization active not active active The system clock of the PC is synchronized by the time master. The time master is always the Master-TIM on the shared MPI bus. The PC currently cannot be configured as the time master. Close button active not active active The "ST7cc Server cannot be closed when this function is activated. Run without window active not active not active ST7cc server runs completely in the background. It does not appear in the task bar and cannot be displayed on the monitor. The log window remains visible since it is started with a separate program. PM-AQUA active active not active not active This function needs to be activated if data is transmitted over a raw data channel with PM-AQUA. Acron Not active CSV archiving active CSV data logger active TAG log archiving active not active There are three options available for transferring data with ACRON: CSV archiving active: By assigning an archive block with the name "ACRON to an ST7cc tag, all the archive values of this tag will be written to a CSV file in ACRON measurement format. There is no transfer into tag logging. CSV data logger active: All messages are written to a CSV file, e.g. for connecting a third-party control system. Tag log archiving active: By assigning an archive block with the name "ACRON to an ST7cc tag, Acron takes the data from the WinCC dbase archive. The archive name has to be specified in the tag logging. Communication statistics active not active not active The availability of the system status tags in WinCC can be activated or deactivated. 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-36 SINAUT ST7cc Manual (05/2002)

65 Installation Function: Possible settings: Default: Description: Server information active not active active The availability of the server status tags in WinCC can be deactivated. SINAUT ST7cc Manual (05/2002) 2-37

66 Installation Project Settings: File Paths Fig Dialog for setting the file paths Process Image Local Buffer File: Object list Default: --- Description: Name and path of the project file File: Library Default: --- Description: Name and path of the typical file File: Process Image Default: --- Description: Name and path of the process image file Parameter: Count of messages Default: Description: Size of the local buffer for temporary storage of all process messages during the time WinCC runtime is deactivated. Approx. 10 Mb of disk space is needed for messages. File: Path Default: --- Description: Name and path of the file for the local buffer 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-38 SINAUT ST7cc Manual (05/2002)

67 Installation Remote Buffer Parameter: Count of messages Default: Description: Size of the remote buffer for storing all process messages for possible updating with a redundancy partner. This buffer is only active when ST7cc redundancy is activated. All process messages are stored, regardless whether or not a redundancy failure occurs. This buffer operates according to the circulation principle and is always 100% full after initial fill phase. Approx. 10 Mb of disk space is needed for messages. File: Path Default: --- Description: Name and path of the remote buffer SINAUT ST7cc Manual (05/2002) 2-39

68 Installation Project Settings: Communication The computer name is taken from the "Global Settings and is only displayed here. The computer name cannot be changed in this window. Subscriber number of ST7cc Server 2. Only relevant when redundancy is used. Subscriber number of ST7cc Server 1 Subscriber number and MPI address of all Master-TIMs connected to the MPI bus. New TIM subscribers can be entered or existing TIM subscribers can be modified by clicking on the buttons "New", "Edit and "Delete. Fig Dialog for setting the communication parameters of the ST7cc server 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-40 SINAUT ST7cc Manual (05/2002)

69 Installation Project Settings: WinCC General Fig Dialog for the WinCC project settings Function: WinCC program name Possible settings: No entry: WinCC is not started automatically MCP.exe: WinCC Version 4 WinCC Explorer.exe: WinCC Version 5 AutostartRT.exe: WinCC Runtime V5 without WinCC Explorer Default: winccexplorer.exe Description: When the default name is complete, WinCC is started automatically by the ST7cc server during startup. The ST7cc server always has to be started before WinCC Runtime, otherwise the process images cannot be updated. When the optional "AutostartRT.exe setting is used, an entry is mandatory for the start parameter. Function: Possible settings: Default: Description: WinCC start parameter No entry e.g.: D:\Siemens\WinCC\WinCCProjects\ST7ccRed\ ST7ccRed.mcp /Activ:yes /LANG:DEU When AutostartRT.exe is used, the start parameter above has to be entered. SINAUT ST7cc Manual (05/2002) 2-41

70 Installation WinCC Buffer Function: Wait after archiving Possible settings: Time in milliseconds Default: 0 Description: This value should not be changed. Function: Size of buffer Possible settings: Maximum number of messages Default: Description: Temp buffer for transferring data to WinCC Function: Buffer path Default: --- Description: Name and path of the WinCC temp buffer WinCC Message Blocks Function: Subscriber name Possible settings: 1-10 Default: 2 Description: Entry of the ST7cc "Subscriber name field in the WinCC user text block 2 Function: Group name Possible settings: 1-10 Default: 3 Description: Entry of the ST7cc "Group name field in the WinCC user text block 3 Function: Variable name Possible settings: 1-10 Default: 4 Description: Entry of the ST7cc "Tag name field in the WinCC user text block 4 Function: Location Possible settings: 1-10 Default: 5 Description: Entry of the ST7cc "Location information field in the WinCC user text block 5 Function: Message text Possible settings: 1-10 Default: 1 Description: Entry of the ST7cc "Message text field in the WinCC user text block 1 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-42 SINAUT ST7cc Manual (05/2002)

71 Installation Project Settings: Archiving Fig Dialog of the project settings for archiving General Function: Possible settings: Default: Description: PM-AQUA Fill empty intervals with last value when archiving active not active not active If a value is missing for a compression interval, ST7cc fills this interval slot with the most recent valid value. Function: Number of process channels Possible settings: 0-10 Default: 0 Description: If the raw data channel is used for PM-AQUA, enter the number of available process data channels. The value 0 means no process data channel is used. Function: Size of buffer per channel Possible settings: Default: 0 Description: If the raw data channel is used for PM-AQUA, enter the maximum number of messages in the temporary buffer. The value 0 means no process temporary buffer is used. SINAUT ST7cc Manual (05/2002) 2-43

72 Installation Function: Buffer path Default: --- Description: Name and path of the temp buffer ACRON Function: Switch time Possible settings: At least 60 seconds Default: 60 Description: If the ACRON CSV interface is used, this parameter is used to set the restore cycle of the individual CSV files. Function: Possible settings: Default: Description: Directory Project directory e.g.:d:\siemens\wincc\winccprojects\st7ccred \ST7cc Directory in which the CSV files should be saved. 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-44 SINAUT ST7cc Manual (05/2002)

73 Installation Project Settings: Config This function should always be activated during the initial operation phase. Fig Dialog for ST7cc Config project settings General Function: Possible settings: Default: Description: Accept changes automatically active not active active Changes to the object parameters are applied automatically. When this function is deactivated, changes are lost when the window is closed unless the "Apply changes button is pressed. Function: Possible settings: Default: Description: Message number format sssoooimm ssssooimm sssoooimm The following convention is released in order to ensure unique message numbers throughout the project:! Important The total number of places (sssoooimm = 9 places) may not be changed. SINAUT ST7cc Manual (05/2002) 2-45

74 Installation sssoooimm Structure Description Possible number range sss Subscriber number (station number) ooo Object number i Typical instance number 1-9 mm Number of the message block 1-99 ssssooimm Structure Description Possible number range ssss Subscriber number (station number) oo Object number 1-99 i Typical instance number 1-9 mm Number of the message block 1-99 Texts for initializing new objects Function: Default: Description: Function: Default: Description: Function: Default: Description: Function: Default: Description: Function: Default: Description: Function: Default: Description: Function: Default: Description: Subscriber Station Default for creating a new subscriber. Group Group Default for creating a new typical tag Instance Instance Default for creating a new typical instance Variable Variable Default of the tag name when creating a new tag. Archive Archive Default of the archive name when creating a new archive block Message class Class Default of the message class when creating a new message block Message type Type Default of the message type when creating a new message block. 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-46 SINAUT ST7cc Manual (05/2002)

75 Installation Global Settings The global settings can be opened from the "Edit/Global Settings" menu command or with "F3. The following sections describe the range of settings under the individual registry tabs Global Settings: Computer This button has to be pressed once the computer name and IP address have been entered. All changes to the server settings must be completed by clicking on OK. Fig Dialog for the global settings of the PC/PG Server 1 Function: Default: Description: Function: Default: Description: Computer name Enter the Windows network name here IP address Enter the IP address of your computer here Server 2 Function: Default: Description: Computer name Enter the Windows network name here. Only when using a redundant server. SINAUT ST7cc Manual (05/2002) 2-47

76 Installation Function: Default: Description: IP address Enter the IP address of your computer here Only when using a redundant server. Activation Function: Description: Add server information to system Pressing this button applies all of the entries and changes in the system and ST7cc for the specific computer Note This button is only activated when the computer name of Server1 or Server2 matches the actual network name. You should also check to see if all modifications have been completed by pressing the OK button. 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-48 SINAUT ST7cc Manual (05/2002)

77 Installation Global Settings: Project Currently loaded project in the ST7ccConfig tool. Currently activated project in the ST7cc Server. All changes must be completed by clicking on OK. Fig Dialog for the global settings of the project Information Function: Description: Function: Description: Project opened in ST7cc Config This displays the project currently loaded in the ST7cc Config. No entry can be made here. Activate current project for ST7cc Runtime This displays the project currently loaded in the ST7cc Server. No entry can be made here. Activation Function: Description: Activate current project for ST7cc Runtime When this button is pressed the currently loaded project in the configuration tool will be automatically loaded the next time the ST7cc Server is started. Note You should check to see if all modifications have been completed by pressing the OK button. SINAUT ST7cc Manual (05/2002) 2-49

78 Installation Global Settings: License Enter the license period in days (normally "10000" for an unlimited license period). Enter the number of stations: Small license: 6 stations Medium license: 12 stations Large license: unlimited number of stations Press "Generate it" to create a registry key. Activation key 2 is currently not used. Enter the activation key you have received from the SINAUT Hotline service and test it by clicking on the "Test it" button. Fig Dialog for the global settings of the ST7cc license 6NH7998-7AA11 Siemens AG 2 All Rights Reserved 2-50 SINAUT ST7cc Manual (05/2002)

79 Installation Global Settings: Redundancy License Enter the license period in days (normally "10000" for an unlimited license period). Press "Generate it" to create a registry key. Activation key 2 is currently not used. Enter the activation key you have received from the SINAUT Hotline service and test it by clicking on the "Test it" button. Fig Dialog for the global settings of the ST7cc redundancy license The redundancy license is only needed when it is activated. Note When redundancy is activated and you do not have a redundancy license, the ST7cc server automatically goes into single operation mode at startup. SINAUT ST7cc Manual (05/2002) 2-51

80 Preparations Defining Typicals Description of Control Functions Description of Communication Functions Description of Operating Functions Communication Configuration Use a Defined Number Range for Subscriber Numbers Configuration of Control Center TIMs in Separate Racks Send Time Stamp Automation Device Programming Preparations for WinCC Creating a WinCC Project Set the language Adding the ST7 Channel DLL Defining Message Classes and Types Creating Archives Creating Faceplates Interconnecting User Objects by their Names SINAUT ST7cc Manual (05/2002) 3-1

81 Preparations 3.1 Defining Typicals The first step in your project should be to identify the typical elements based on the process specifications of the plant. Define the processes required for the automation level as well as the operating and monitoring levels. Typical elements, for example, are motors, pumps and slide valves; they can also be "simple" objects with special processing tasks (for example, measurement values with rounding and limit value monitoring in an automation device) or even abstract objects (for example, locks, sequences, etc.). This step may not appear to be necessary, but it will make your later work considerably easier. The more careful you work in this phase of the project, the less you will have to change and correct in the final phase of the project. The resulting definitions are "typicals", generally applicable processing instructions that summarize the control, communication and technical operating aspects of such typical plant element. As these aspects are interrelated, it makes sense to define the typicals before configuring the automation devices. Once typicals are defined, they can be used again in subsequent projects. This results in a rationalization effect across the projects. It also provides for a uniform operating interface. However, it should also be mentioned that not all processes can be "typed" by the definition of a recurring model. In such cases the communication and messaging functions can be saved as special processing instructions. ST7cc object templates, which are saved in a library similar to the typicals, form the basis for these individual sets of processing instructions. Chapter 4 "Working with ST7cc Config" deals with the work involved with objects and typical templates. Description of Control Functions The description of the control functions of a typical is usually made in the form of a function block in the automation device. Details about this are not the subject of this documentation, however. Description of Communication Functions In ST7cc Config the communication and messaging functions of a typical can be saved in a library. They are called from the library in your project file. The following example should give you a rough idea about how such a description appears. For more detailed information refer to Chapter 4. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 3-2 SINAUT ST7cc Manual (05/2002)

82 Preparations The header: Type Subtype Name Pump_messages means that the description can be called up as a typical template (type) 100, subtypical (type) 1 and applies to the message bits of a pump. The corresponding attribute description: No. Name Cat. Subcat. Byte index Bit index Length 1 Operating S mode specifies that the single bit 0 of byte 0 should be decoded into the decoded area as a signal (S) with subcategory 1 and the name "Operating mode". The resulting message description: Attribute no. Value No. Class Cat. Message text: Operation N "Auto operating mode" specifies that when the value 0 is received through this bit, message no. 1 with the text "Auto operating mode" and the specified WinCC message class and category should be sent. Description of Operating Functions The description of the operating functions of a typical usually consists of a tag icon and an operating pop-up. Such combinations are also referred to as 'Faceplates. Icons and operating pop-ups can be created as WinCC user objects. For those who are experienced in programming it is also possible to write the typical's operating functions in the form of an OLE control (OCX) in Visual Basic or Visual C++. The software package "IndustrialX" is available as support. SINAUT ST7cc Manual (05/2002) 3-3

83 Preparations 3.2 Communication Configuration Define the individual subscribers and communication arrangements of your plant. The following STEP 7 tools are available to help you in this: HWConfig, NetPro and the integrated SINAUT ST7 configuration utility, ST7Pro.! Important The following information is highly important Use a Defined Number Range for Subscriber Numbers In ST7cc Config the individual WinCC messages are defined by configuring the message blocks (message processing). ST7cc Config automatically assigns (per algorithm) the WinCC message numbers for this purpose. The algorithm is described in Chapter 2 section "Project Settings: Config". To avoid subsequent problems in the configuration of the messages, the subscriber numbers are defined within number ranges, e.g., or depending on the message number format selected Configuration of Control Center TIMs in Separate Racks Each of the TIM units connected to the local MPI bus of the ST7cc server need to be configured in HWConfig in such a way that it can be addressed as an individual module in slot 4 of its own respective rack Send Time Stamp All ST7 objects must be sent with a time stamp for ST7cc to be able to evaluated them. Therefore, always set the 'time stamp' parameter in your ST7 function block call to 'TRUE'. 3.3 Automation Device Programming Programming of the automation device (not explained in detail here) involves defining the control and communication aspects of the processing with STEP 7 and software package TD7. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 3-4 SINAUT ST7cc Manual (05/2002)

84 Preparations 3.4 Preparations for WinCC ST7cc Config always works with the most recent WinCC project when generating, for example, the tag management. The archives, message classes and types to which the processing instructions refer should also be defined Creating a WinCC Project Set the language First create a project in WinCC.! Important Please make sure that the correct language is set at the beginning of the project and do not change the language thereafter. The names of the message classes and types depend on the language and you may have problems later when generating messages Adding the ST7 Channel DLL Add the ST7 channel DLL (file name: ST7.CHN) to your project. It makes the channel unit 'ST7 server' available to the project. Fig. 3-1 Adding the ST7cc driver to WinCC SINAUT ST7cc Manual (05/2002) 3-5

85 Preparations Defining Message Classes and Types Define the message classes and types that you need. Message classes essentially define the acknowledgment scheme and message types determine the appearance of the message windows. For more information about this topic refer to Chapter Creating Archives Define the archives that you need, for example, a short, medium and long-term archive. Note that the size of the archive can be easily adjusted later. It may be difficult, on the other hand, to 'bend' the archiving rules for other archives later Creating Faceplates Create the icons and pop-ups as user objects or use the OLE controls. Ideally, you can copy these objects from other projects. The following section is intended to help you create optimal icons and pop-ups. For more information refer to the WinCC Configuration Manual Interconnecting User Objects by their Names WinCC supports user objects to display groups of objects including their dynamic properties as a single object. Creating a user object also includes specifying the dynamic object properties for this object's group by which such user objects are to be seen by the outside world. For more details refer to the WinCC documentation. In C actions for dynamization of such properties, in lpszobjectname, the name of the user object is passed instead of the name of a partial object. If you adhere to the following convention that is supported by ST7cc Config, you can interconnect user objects by their names with the corresponding set of process tags. For every instance of a typical there is a corresponding set of process tags defined within a group. The group contains the names of the typical instance and every tag name within this group begins with the name of the group. Example: Pump01 Tag group for Pump 1 Pumpe01_temp Tag for temperature of Pump 1 Pumpe01_press Tag for pressure of Pump 1 For example, to determine the temperature in the user object with the name of "Pump01", the corresponding C action for static interconnection would appear as follows: { 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 3-6 SINAUT ST7cc Manual (05/2002)

86 Preparations } return GetTagDouble("Pump01_temp"); For dynamic interconnection, the name of the tag actually used must first be determined from the name "Pump01" of the user object. This is read from the parameter, lpszobjectname: { } // make indirect tag reference static char varname[100]; sprintf(varname, "%s_temp", lpszobjectname); return GetTagDouble (varname); This may appear complicated at first glance, but it has the advantage that all dynamics established in such a way can be automatically interconnected to new destinations when the user object is renamed. The performance is only marginally effected. As the code used always appears the same, it is very easy to later supplement an action created with the Dynamic Wizard with a static interconnection. It is therefore best when creating a user object to first establish the dynamization statically using the Dynamic Wizard. Thereafter, the dynamization can be called up as a C action and supplemented with the dynamic interconnection.! Important Be sure to use the cycle trigger instead of the tag trigger even though this is not recommended in the WinCC documentation. Since the user object is connected dynamically, it will not function correctly with a static tag trigger! You can also use this method to create operating pop-ups. The operating pop-up, however, is connected to a tag set during run-time and you therefore have to use a dynamic property instead of an object name. Determine the value of the property with GetPropertyChar() to dynamically assemble the tag name to be used. Note You can analyze the subscriber faceplate delivered with ST7cc as an example of the use of these methods. For experienced C programmers: Assign a type property to each user object. If you are forced to change all instances of one type of user object, you can then use this property to automate the changes within a C script. SINAUT ST7cc Manual (05/2002) 3-7

87 Working with ST7cc Config Introduction to ST7cc Configuration Terms: Objects and Typicals Term: Tag Term: Tag Typing Term: Processing Term: Typical Template and Subtypical ST7cc Configuration Procedure Naming Convention Specification of the ST7 Subscribers for ST7cc Tasks and Decoding with Object Templates Notes about Object Templates Dialog Notes about Handling Object Templates Decoding Using Object Templates Decoding: Using Object Templates Dialog Notes for Decoding with Object Templates Notes about Object Templates Dialog Notes about Handling Typical Templates Decoding Using Typical Templates: Dialog Notes for Decoding with Typical Templates Final Notes about Decoding Processing Configuration Message Processing Message Number Message Class Message Type Message Code Value / Trigger value: Message Text Static Extra Texts Counter Value Processing Calculation of Interval Quantities: Interval Definition Calculation of Interval Quantities: Use of Differences and Handling Overruns Calculation of Interval Quantities: Proportional Distribution SINAUT ST7cc Manual (05/2002) 4-1

88 Working with ST7cc Config Calculation of Interval Quantities: Example Measurement Value Processing Adjusting Raw Values Interval Based Compression Archiving WinCC Generation Tag Management Tag List(Preview) Generation Variants Generation of the Logical Connections Generation of the Tag Groups Generation of the Individual Tags Editing Generated Tags Message Management Generation Variants Message Numbers Assignment of Message Text Blocks Special Notes Archives Generation Variants Generated Archive Tags Special Notes Delta Mode NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-2 SINAUT ST7cc Manual (05/2002)

89 Working with ST7cc Config 4.1 Introduction to ST7cc Configuration As mentioned in Chapter 1, ST7cc is a software package for connecting SINAUT ST7 and ST1 telecontrol stations to WinCC through TIM modules. The package contains: Runtime software for controlling modules and preprocessing the process data using the transmitted time stamps Configuration software for configuring Display of the ST7 data management in the WinCC data management for message and command routing Configuration of the preprocessing in the ST7cc server for WinCC Configuration of the processing in WinCC Generation of the WinCC message set Tag management WinCC ST7cc Data management (image) of the ST7cc server Configuration data ST7 ST7 data management (communication objects) Configuration Configuration of the display of the ST7 data management in the WinCC data management Configuration of the preprocessing in the ST7cc server for WinCC Configuration of the WinCC processing Data management of the automation functions (including technological objects) Fig. 4-1 Configuration in ST7cc The configuration data is a collection of the imaging instructions describing how to display communication objects from the TD7 environment in WinCC's tag management while taking the preprocessing (message processing, archiving) required for WinCC into consideration. SINAUT ST7cc Manual (05/2002) 4-3

90 Working with ST7cc Config Over time the term decoding or coding has come into use to refer to imaging instructions because the term better expresses the fact that, in addition to simple imaging of data, the declaration of the additionally require processes are involved. Decoding describes the imaging of ST7 data management in WinCC data management. Coding involves the reverse data flow direction for the command output. In the following we only refer to decoding or imaging to simplify the descriptions. Point of View: The communication objects of the ST7 environment are the starting point for the decoding task. Decoding describes how the content of the communication objects (structures / substructures) are displayed as WinCC tags Terms: Objects and Typicals Since working with SINAUT ST7, ST7cc and WinCC involves differing points of view and terminology, we would like to offer an explanation of the conventions used here at the outset. The following illustration shows the automation processing of an actual object, such as a door, slide valve, motor, measured value (e.g. temperature, pressure etc.). The part of the process close to the process itself occurs on the automation level. Extended processing (such as the archiving of an object's process data, the display of the object's process status, its operation etc.) is usually performed on the control level. ST7 data management (communication objects) represent data between the automation and control levels to be communicated. With the aid of object-oriented faceplates, the operator addressed the technological processes, e.g. pumps, motors, etc. By assigning suitable names, the communication objects decoding enables the object model to be mirrored in the WinCC data management. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-4 SINAUT ST7cc Manual (05/2002)

91 Working with ST7cc Config WinCC tag name: group name_tag name Operator thinks 'object-oriented' A suitable naming convention for WinCC tags supports 'object-oriented' control. Pump1_OFF Pump1_BART Pump1_BMOD Pump1_ON Pump1_OILPRESS Pump1_RESET Pump1_FAULT Pump1_TEMPERATURE Pump1_STAT HMI Tag management WinCC Processing on the control level (WinCC) Data management (image) of the ST7cc server ST7cc Configuration of the ST7cc Server Processing on the automation level ST7 data management (communication objects) Data management of the automation functions ST7 Object in the real world Fig. 4-2 Environment for imaging the ST7 data management in the WinCC data management. The following illustration depicts and offers an explanation of the terms, data point typical, structured typical, technological typical, technological object and communication object. SINAUT ST7cc Manual (05/2002) 4-5

92 Working with ST7cc Config Tag management WinCC Control level (Integrated) process image of the ST7cc server ST7cc Decoding of the ST7 data management ST7 data management Station 1 ST7 data management Station i Automation level ST7 data management Station n e.g. Bin04B_S e.g. Ana04W_S Data point typical e.g. Dat12D_S Communication objects e.g. 'flow rate measurement' (communication: result and parameters) Structured typical (*) Technological objects e.g. 'flow rate measurement' (calculation procedure i) Technological typical (*) 'Instancing' means the creation of a DB instance (*) in planning Fig. 4-3 Illustration of the terminology. The background part corresponds to the ST7cc point of view. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-6 SINAUT ST7cc Manual (05/2002)

93 Working with ST7cc Config With SINAUT TD7 (components from SINAUT ST7) the user creates the communication part of his automation program. SINAUT TD7 is responsible for the change-driven data transmission between the individual CPUs and to ST7cc. Data point typicals: In addition to the basic and auxiliary blocks, data point typicals are also available in TD7; they are integrated into the CPU program depending on the data types and quantities to be transmitted. They assemble messages for data changes and output received process data. In addition to the monitoring of data changes, some data point typicals may contain other processes such as the calculation of mean values for Ana04W_S. An essential characteristic of a data point typical is that its processing is based on data types, for example 32-bit, 4 analog values etc. Data point typicals are not oriented to technological objects. They are designed to use CPU in an optimal manner and to minimized the message traffic. Structured Typicals: A structured typical, in contrast to a data point typical, is designed to receive the data of a technological object and to process it for communication. A structured typical therefore contains a variety of data types for communication in both the sending and receiving direction. Similar to data point typicals, the typical is mainly responsible for processing the communication of the data. Technological Typicals: A technological typical contains the processing for technological objects close to the process. A technological object can be a motor, a temperature to be measured or a calculation (e.g. a flow calculation). In some cases, which cannot be ruled out, a technological typical can contain its own communication processing. The ST7 strategy is currently designed in such a way that technological and communication processing is performed by separate typicals. This makes it easier for the user to design the technological processing with his customized typicals / blocks and perform the communication with ST7 standards. Communication Objects: A communication object represents the content of a data buffer in the automation device. The structure of the data buffer can be described in the form of tags (specifically: ST7cc tags). A communication object can represent the data from one or more objects. The data of an object, however, may (very often) be spread over several communication objects. The following section provides more details about this. Creating a Communication Object : Communication objects are created through instancing (creation of a DB instance based on data point or structured typicals). Instancing of technological typicals creates technological objects. The data of a technological object, which communicates with other subscribers (CPU, ST7cc), are passed to the communication objects. A technological object may sometime contain its communication data. SINAUT ST7cc Manual (05/2002) 4-7

94 Working with ST7cc Config Working with Communication Objects Based on Data Point Typicals Since there are currently no structured typicals available to the user, communication is carried out exclusively through the communication objects of the data point typicals. Data point typicals based on communication objects will continue to be used in future because they enable optimal use of the CPU memory. Many information units of a technical process have a very simple structure (e.g. only 2 or 4 bits) or are unique in the sense of a repeating structure so that typing is not worth the effort. The following illustrations show typically occurring constellations of communication object based on data points for technological objects. Door1 Door2 Lamp1 Lamp2 Obj. 50 (Type: Bin04B_S) Case 1: Data from several objects in a single communication object Pump 1 free free free Obj. 50 (Type: Bin04B_S) Pump 1 Obj. 51 (Type: Cmd01B_R) Case 2: Data from a technological objects distributed between two communication objects Pump1 Pump 2 Slide valve Lamp Obj. 50 (Type: Bin04B_S) Pump 1 Obj. 51 (Type: Cmd01B_R) Pump 2 Obj. 52 (Type: Cmd01B_R) Slide valve etc. Case 3: Realistic combination of Cases 1 and 2 Fig. 4-4: Writing data from a technological object to communication objects based on data point typicals The ST7cc configuration tool is designed to handle almost any constellation arising from planning sketches of combined operation (see Case 3 in Figure 4-4). The use of data point typicals usually does not automatically guarantee objectoriented operation. The next section shows how a kinde of object-orientated operation can be achieved by implementing a suitable naming convention for WinCC tag management. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-8 SINAUT ST7cc Manual (05/2002)

95 Working with ST7cc Config Term: Tag ST7 Data Management ST7cc group name, e.g. Pump 1 WinCC tag name, e.g. Pump1_BTYP ST7cc tag name, e.g. BTYP Communication objects Bit7: Bit6: Bit5: Pump1 FAULT '3 bit' tag Messages of Motor1. Obj. 50 (Type: Bin04B_S) Bit4: Bit3: Pump1 STAT '2 bit' tag Bit2: Bit1: Pump1 BMOD '2 bit' tag Bit0: Pump1 BTYP '1 bit' tag Bit7 (byte 2): Obj. 51 (Type: Cmd01B_R) Bit7: Pump1 RESET Bit6: Bit5: Bit4: Pump1 OFF Bit3: Pump1 ON Bit2: Bit1: Bit0: '1 bit' tag '1 bit' tag '1 bit' tag Commands of Motor1. Obj. 52 (Type: Ana04W_S) Value1: Pump1 TEMPERATURE Value2: Pump1 OILPRESS Value3: Value4: '1 word' tag '1 word' tag Analog values of Motor1 Fig. 4-5: Tag definition for displaying the content of communication objects in WinCC tag management Tags: Tags are atomic components of a communication object that are subject to the processing instructions (e.g. as signals, measured values, counter values, setpoints, commands). They take the form of WinCC tags in the process image of the WinCC data manager and archive tags in WinCC tag logging. SINAUT ST7cc Manual (05/2002) 4-9

96 Working with ST7cc Config ST7cc group name, e.g. Pump 1 WinCC tag name, e.g. Pump1_BTYP ST7cc tag name, e.g. BTYP Tag management WinCC (Integrated) process image of the ST7cc server Pump1_OFF Pump1_BTYP Pump1_BMOD Pump1_ON Pump1_OILPRESS Pump1_RESET Pump1_FAULT Pump1_TEMPERATURE Pump1_STAT Decoding of communication object information for: a) Definition of the WinCC Tag management and b) Assignment of the preprocessing in the ST7cc server for WinCC ST7 data management Obj. 50 (Type: Bin04B_S) Communication objects Obj. 51 (Type: Cmd01B_R) Bit7: Bit6: Bit5: Pump1 FAULT Bit4: Bit3: Pump1 STAT Bit2: Bit1: Pump1 BMOD Bit0: Pump1 BTYP Bit7 (byte 2): : Bit0 (byte 4): Bit7: Pump1 RESET Bit6: Bit5: Bit4: Pump1 OFF Bit3: Pump1 ON Bit2: Bit1: Bit0: Messages of Pump1. Commands of Pump1. Obj. 52 (Type: Ana04W_S) Value1: Pump1 TEMPERATURE Value2: Pump1 OILPRESS Value3: Value4: Analog values of Pump1. Fig. 4-6 Tag definition with display in the WinCC tag management Note about the example above: The name component 'Pump1 is entered in the configuration dialogs as the 'Group name. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-10 SINAUT ST7cc Manual (05/2002)

97 Working with ST7cc Config Term: Tag Typing The display of ST7 communication objects as ST7cc and WinCC tags was described in the previous sections. Other components in the ST7cc configuration are: Configuration of the preprocessing in the ST7cc server for WinCC Configuration of the processing in WinCC Generation of the WinCC message set Typing means assigning a tag a new type and a subtype for further division. Typing determines the depiction and processing that is possible for a tag. It is done by specifying a - tag type (capital letter) - tag subtype (number of a process variant) Once the processing for a tag has been defined by typing, the detailed processing parameters are specified in the next step of the configuration. See section 4.3 for more information in this regard. The available types and subtypes are listed in the following table. In order to fully understand the table, interested readers should note that the typing defines the processing of a tag. The measured value processing of a given tag may use an Ana04W_S or Bin04B_S communication object as the data source, for example. Example 1: Tag type M, 2, 32-bit: The 32 bits of the tag are interpreted and processed as a prefixed integer by the ST7cc measured value processing. For the decoding it does not matter if these 32 bits come from a Bin04B_S or a Dat12D_S. Example 2: Tag type M, 1, 16-bit: 16 bits are interpreted and processed as a non-prefixed integer by the ST7cc measured value processing. For other ST7cc processes it does not matter if these 16 bits come from an ST7 Ana04W_S or a Bin04B_S. Example 3: Tag type A, 4, 32-bit: 32 bits are output by ST7cc to the automation level as information in floating point format. The data destination needs to be able to accept the 32 bits, e.g. a Bin04B_R. In this case Set01W_R cannot be the data destination of the setpoint output. SINAUT ST7cc Manual (05/2002) 4-11

98 Working with ST7cc Config Overview of Available Tag Types and Subtypes Type Subtype Permitted lengths Description M 1 16, 32 bits 16, 32 bits are interpreted as non-prefixed integers. 2 16, 32 bits 16, 32 bits are interpreted as prefixed integers. The highest valued bit is interpreted as a prefix bits The 16 bits are interpreted as ST1 measured value (left-justified prefixed value, bits 0,1,2 of the right byte of the S5 data word contain status displays) bits Measured value as floating point number. S 1 1 to 32 bits A 1 to 32-bit (max.) data area can be defined as a tag. Z 1 32 bits Counter value represents an absolute value (28-bit value, 4-bit status) bits Counter value represents a difference value (28-bit value, 4-bit status) bits Counter value represents an absolute value (32-bit value, no status) bits Counter value represents a difference value (32-bit value, no status). A 1 16 bits 16-bit integer 2 16, 32 bits 16 bits when ST1 setpoint block is used as a data destination. 32 bits when, for example, a binary value block is the data destination. 3 - Not used 4 32 bits 32 bits floating point number D 1 1 or 8 bits Command output: sent as two mirrored command bytes (default). 2 8 bits Command output: sent as a non-mirrored organization command. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-12 SINAUT ST7cc Manual (05/2002)

99 Working with ST7cc Config Term: Processing Typing implicitly defines the processing permitted for a tag specific to its type (M, S, A, Z, D). The configuring engineer selects a tag and then assigns the desired process and the parameters for the process. Section 4.3 and the following pages provides a detailed description of the various processes. ST7cc Config currently recognizes the following processes: MB: Message processing which treats status changes of the tags as messages and passes them to WinCC. TB: Text block input which allows supplementary texts (text blocks) to be entered for message processing. AB: Configuration of the archive processing. Archiving can be used for all tag types. The results of the processing are always archived. PB: Configuration of the actual value processing for the specific tag, e.g. measured value processing, counter value processing. Type Subtype Permitted lengths Permitted processes M 1 16, 32 bits MB, TB, AB, PB 2 16, 32 bits MB, TB, AB, PB 3 16 bits MB, TB, AB, PB 4 32 bits MB, TB, AB, PB S 1 1 to 32 bits MB, TB, AB Z 1 32 bits MB, TB, AB, PB 2 32 bits MB, TB, AB, PB 3 32 bits MB, TB, AB, PB 4 32 bits MB, TB, AB, PB A 1 16 bits MB, TB, AB, PB 2 16, 32 bits MB, TB, AB, PB bits MB, TB, AB, PB D 1 1 or 8 bits MB, TB, AB Table : 2 8 bits MB, TB, AB Permitted processes for tag types SINAUT ST7cc Manual (05/2002) 4-13

100 Working with ST7cc Config Tag with typing, e.g. type S: Assignment of the permitted processing. Assignment of the processing for a tag depending on type ST7 data management Obj. 50 (Type: Bin04B_S) Communication objects Obj. 51 (Type: Cmd01B_R) Bit7: Bit6: Bit5: Pump1 FAULT Bit4: Bit3: Pump1 STAT Bit2: Bit1: Pump1 BMOD Bit0: Pump1 BTYP Bit7 (byte 2): MB Message processing TB Text block input AB Archive processing Messages of Pump1. Obj. 52 (Type: Ana04W_S) MB: TB: AB: PB: Message block for configuring the message processing Text block for entering supplementary text blocks for message processing Archive block for configuring the archiving Parameter block for configuring the processing specific to the object type, e.g. measured value processing. Fig. 4-7 Tag definition with assignment of the processing The illustration above shows that a tag can be assigned optional processing. The appropriate parameter fields are displayed in the dialog window when processes are assigned. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-14 SINAUT ST7cc Manual (05/2002)

101 Working with ST7cc Config Term: Typical Template and Subtypical The previous section offered an overview of what is involved in the decoding process, e.g. definition of tags, their typing, assignment of processing and the entry of the parameters. Typical templates offer a way to efficiently organize the decoding of the ST7 tag list in an object-oriented manner using model templates / subtypicals. The use of model templates requires that sufficient analysis be carried out during the planning stage of the solution design to identify repeating structures for an object-oriented basis. Name component that will later be appear from the configuration of the 'Group name. Repeating structure within a communication object representing the 'messaging response' e.g. of a 'Pump' object. ST7 data management in Station i Obj. 50 (Type: Bin04B_S) Obj. 51 (Type: Cmd01B_R) Bit7: Bit6: Bit5: Pump1 FAULT Bit4: Bit3: Pump1 STAT Bit2: Bit1: Pump1 BMOD Bit0: Pump1 BTYP Bit7 (byte 2): : Bit0 (byte 4): Bit7: Pump1 RESET Bit6: Bit5: Bit4: Pump1 OFF Bit3: Pump1 ON Bit2: Bit1: Bit0: Parameters for decoding: Group name: e.g. Pump1 Tag name: ON Location information for messages: Byte index: 0 Bit index: 3 Length: 1 Type: D Subtype: 1 Parameters for other processing: MB Message processing TB Text block input AB Archive processing Repeating structure within a communication object representing the 'command response' e.g. of a 'Pump' object. Typical (template): collection of model subdecoding routines, e.g. for an object. Subtypical 1: contains the decoding for a repeating structure, e.g. the messaging response of an object Subtypical 2: contains the decoding for a repeating structure, e.g. the command response of an object Fig. 4-8 Depiction of terms: typical (template) and subtypical SINAUT ST7cc Manual (05/2002) 4-15

102 Working with ST7cc Config Subtypical: A subtypical is a model decoding including parameter defaults for repeating structures with a communication object. The decoding of an entire communication object can be described by a subtypical or it may only describe a section, e.g. a byte that contains the status display of a technological object. Typical template: A typical template forms logical parentheses to allow a subtypical to be handled in an 'object-oriented' manner. In this light the sum of the subtypical decoding of the subtypicals represents the model decoding of a technological object. The typical template provides consistent support for the object-oriented thought process of the user. A typical template may consist of 1 to 99 subtypicals.! Important Changing the decoding of a subtypical has an effect on any other decoding that references this subtypical due to internal references. Typical ID (= number) and typical name Typical template consisting of 1 to 99 subtypicals Subtypical ID (= number) Tag ID (= number) Messages for pump type A Tag1: BTYP Tag2: BMOD Tag3: STAT Tag4: FAULT MB Message processing TB Text block input AB Archive processing Commands for pump type A Tag1: OFF Tag2: ON Tag3: RESET Subtypical Subtypical Analog values for pump type Tag1: Tag2: OILPRESS Subtypical The model decoding template can be uniquely identified by the ID of the typical (template) (e.g. 100 ) and subtypical ID (e.g. 1 ). Fig. 4-9: Components of a typical template 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-16 SINAUT ST7cc Manual (05/2002)

103 Working with ST7cc Config 4.2 ST7cc Configuration ST7cc configuration involves the decoding of the communication objects and the technical system objects (stations, ST7 server, system, PM-AQUA channel, etc.). The configuration can be carried out in the ST7cc Config program or in Excel. The following sections only deal with configuration using ST7cc Config. The configuration engineer is presented with a dialog window for ST7cc configuration when the ST7cc Config starts. The configuration engineer can then create or open a project file using the menu commands 'File - New', 'File - Open' or 'File - Last opened'. Menus bars Window for displaying the object tree Fig Example: selecting the most recently opened project file Selecting the project file implicitly creates or opens two files. These are the library and the actual project file which takes on the decoding. The library contains the object and typical templates, the project file contains the decoding. The library and project file are located in the project directory. Changes made to the library therefore only applied to the project at hand. The object and typical templates and the decoding are referred to as objects in order to guarantee uniform menu forms for them. The following illustration shows the dialog window after the selection of a project file. The object templates can be changed or supplemented with other templates. When referring to typical templates we differentiate between technical system templates (system typical) and user-oriented templates (typicals). User-oriented typical templates (or simply typicals) begin with the typical number 100. They can be changed or supplemented with other templates. System typical should not be changed! System typicals have typical number smaller than 100. SINAUT ST7cc Manual (05/2002) 4-17

104 Working with ST7cc Config Template library Key information Icon bar Object template tags ST7cc object templates CC TIM Sub. 102 TIM TIM typical template CPU CPU CPU Sub. 11 Sub. 12 Sub. 13 Decoding Objects: object & typical templates, decoding Fig Main dialog for ST7cc configuration The project library contains the decoding of the ST7 communication objects and implicitly the decoding of the subscribers. Subscribers are the CPUs that are connected to ST7cc by their TIMs and the control center TIMs. The subscribers with the number 0 represent ST7cc as a system. The object no. 0 (subscriber 0) with the object name 'System' is setup automatically. The configuration engineer has to configure the decoding - based on the current system installation - using the system typicals. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-18 SINAUT ST7cc Manual (05/2002)

105 Working with ST7cc Config Procedure Preparations: Analysis of the tasks needed: Plan for modification and supplements to the object templates Plan for modification and supplements to the typical templates Check / modify the ST7cc Config settings Configuration steps: A top-down method is used in the ST7cc configuration: Opening or creating of the project file (see text above) Specification of the ST7 subscribers for ST7cc Tasks and decoding with object templates Tasks and decoding with typical templates Decoding 'System' Generation of the WinCC tag list SINAUT ST7cc Manual (05/2002) 4-19

106 Working with ST7cc Config Naming Convention Naming is necessary for calling up decoding information within the WinCC tag list. It is done on two levels by specifying a: Group name and a Tag name This allows the data points in WinCC to be regrouped according to technological criteria. Example: The tags identified by the group name "Pump1 and the tag name "Status are assigned within the WinCC tag list to the logic group "Pump1 and to the WinCC tag "Pump1_Status. Note The use of names in WinCC causes the following restrictions: 1. The combination of a group name and tag name has to be unique throughout the project. Follows (2). 2. A specific group name can only be used in the objects of a subscriber. 3. Names cannot contain a period or a space character.! Important Erfolgt die Decodierung von neuen Objekten durch 'Copy and Insert an object tree branch' ist darauf zu achten, daß die Gruppennamen nachbearbeitet werden, um die projektweite Eindeutigkeit der WinCC Namen zu erreichen. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-20 SINAUT ST7cc Manual (05/2002)

107 Working with ST7cc Config Specification of the ST7 Subscribers for ST7cc A new subscriber can be configured in ST7cc with the menu command 'Edit - New Subscriber'. Enter the subscriber name Fig Dialog window for entering a new subscriber SINAUT ST7cc Manual (05/2002) 4-21

108 Working with ST7cc Config The number of the subscriber corresponds to the ST7 subscriber number of a control center TIM or a CPU. The decoding of the ST7 communication object is configured under the subscriber. Meaning of the Subscriber Name The required tags for displaying the status of a subscriber in the WinCC tag list are implicitly generated by the decoding for the WinCC tag generation. The technical system typical template 'Subscribers' is used as the basis for this tag generation. The names of the WinCC tags are formed by the subscriber name entered above and the ST7cc tag name of the typical. The order criterion, subscriber number, is in the ST7cc object tree. In the WinCC tag list the sorting is carried out alphabetically with the tag names. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-22 SINAUT ST7cc Manual (05/2002)

109 Working with ST7cc Config Tasks and Decoding with Object Templates Working with object templates means: Changing existing object templates by: - Inserting, configuring or deleting tags - Inserting, configuring or deleting messages Adding new object templates - Copying and inserting existing object templates - Inserting an empty object (base for an object template) Deleting an object template Decoding with object templates means: Creating of the decoding for ST7 communication object. Changing the decoding Deleting the decoding Notes about Object Templates Many ST7 communication objects have no repeating structures in regard to their content to be decoded. For such cases it is not worth the effort to define and manage numerous individual typical templates or subtypicals. For this reason object templates with simple, non-exemplary, decoding are provided to demonstrate the principle of the decoding. The configuration engineer can use these templates to decode ST7 communication objects (copying object tree branches, inserting object tree branches) and change their parameters as needed. The currently available object and typical templates are listed in the following table. It is not worth explaining every template in detail since the default settings become self-explanatory to the configuration engineer when he selects a given dialog. Notes about Object Templates Object Template 0: Object 0 is an empty object template. In some cases it is easier to use an empty object template for the decoding of communication objects and to enter the tag definitions individually than go through numerous steps to change the existing decoding in an object template. Empty decoding can also be inserted without having to copy an empty template by creating a 'New Object'. Refer to the dialog examples below for more details. The templates in the library are labeled and organized as 'OB for object templates and 'TY for typical templates. SINAUT ST7cc Manual (05/2002) 4-23

110 Working with ST7cc Config Library Templates consist of: Object templates Obj (object template without decoding) Obj. 1 Bin04B_S VA 1 Bit1 with: byte index 0, bit index 0, length 1, type S, subtype 1 VA 2 Bit2 with: byte index 0, bit index 1, length 1, type S, subtype 1 : VA 32 Bit32 with: byte index 3, bit index 7, length 1, type S, subtype 1 Obj. 2 Ana04W_S Obj. 3 Cnt01D_S Obj. 4 Set01W_R Obj. 5 Cmd01B_R Obj. 6 Dat12D_S VA 1 DINT_Val1 with: byte index 0, bit index 0, length 32, type S, subtype 1 VA 2 REAL_Val1 with: byte index 0, bit index 0, length 32, type M, subtype 4 VA 3 DINT_Val2 with: byte index 4, bit index 0, length 32, type S, subtype 1 VA 4 REAL_Val2 with: byte index 4, bit index 0, length 32, type M, subtype 4 : Obj. 7 Par12D_S VA 1 Local_Operation with: byte index 0, bit index 0, length 1, type S, subtype 1 VA 2 Return_value1 with: byte index 2, bit index 0, length 32, type M, subtype 4 : VA 13 Return_value12 with: byte index 46, bit index 0, length 32, type M, subtype 4 VA 14 Setpoint1 with: byte index 50, bit index 0, length 32, type A, subtype 4 : VA 25 Setpoint12 with: byte index 94, bit index 0, length 32, type A, subtype 4 Typical Templates T 1.0 System T 1.1 Subscriber T 2.1 PM_Aqua_Channel T 3.1 ServerStatus T Pump_messages T Pump_commands T Mot2V2R_messages T Mot2V2R_commands T Slide_valve_messages T Slide_valve_commands T Fig Library elements as the starting basis for configuration of the ST7cc server Object template Bin04B_S The object template Obj. 1 Bin04B_S is intended for a 32-bit data area as found, for example, in an ST7 communication object based on a Bin04B_S data point typical. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-24 SINAUT ST7cc Manual (05/2002)

111 Working with ST7cc Config Data area of a message block Bin04B_S Byte 1 Byte 2 Byte 3 Byte 4 Byte index Bit index Bit length Tag between 1 and 8, length of the area in bits beginning with byte index and bit index in the direction of ascending indexes. The first bit of a message block (lowest bit of the first byte), for example, is identified by byte index 0, bit index 0 and bit length 1. The object template Obj. 1 Bin04B_S contains a decoding in which each bit is displayed as a tag of the type S (Signal as a 1 to 32-bit complete bit area) with the length of 1 (bit). If this default setting is applicable to the case at hand, the configuration engineer only needs to set the group and tag names. The configuration engineer usually needs to set the "length" parameter and the group and tag names based on the data structure at hand. Tags that are not needed should be deleted to avoid the generation of unnecessary WinCC tags later. Object template Ana04W_S The object template Obj. 2 Ana04W_S is intended for a 4 word (each 16 bits) data area as found, for example, in an ST7 communication object based on a Ana04W_S data point typical. Data area of a message block Ana04W_S Word 1 Word 2 Word 3 Word 4 Byte index Bit index Bit length The four words of an analog value block are identified by byte index 0, 2, 4 and 6, bit index 0 and bit length 16. Object template Cnt01D_S The object template Obj. 3 Cnt01D_S is intended for a 1 double word (each 32 bits) data area as found, for example, in an ST7 communication object based on a Cnt01D_S data point typical. Data area of a counter block Cnt01D_S Double word 1 Byte index 0 Bit index 0 Bit length 32 The counter value of a counter block is identified by byte index 0, bit index 0, bit length 32. SINAUT ST7cc Manual (05/2002) 4-25

112 Working with ST7cc Config Object template Cmd01B_R The object template Obj. 5 Cmd01B_R is intended for a 2-byte data area as found, for example, in an ST7 communication object based on a Cmd01B_R data point typical. Data area of a command block Cmd01B_R Byte 1 Byte 2 Byte index 0 Returned automatically Bit index in command processing Bit length 1 or 8 (type D, subtype 1) A 1 can be written for single bit addressing (bit length = 1) to set the respective command bit. For complete addressing (bit length = 8) a number between 0 and 7 is passed during the command processing to indicate the number of the bit to be set. Organizational commands for communication subscribers can be issued by using subtype 2 of the command processing. The command bit is not returned in this case. Object template Set01W_R The object template Obj. 4 Set01W_R is intended for a 3 word (each 16 bits) data area as found, for example, in an ST7 communication object based on a Set01W_R data point typical. Data area of a setpoint block Set01W Local value Return value Setpoint _R Byte index Bit index Bit length In contrast to the other blocks, the setpoint block contains both send and receive data. The first word (byte index 0, bit index 0, bit length 16) may contain a code that is set locally for the setpoint. The second word (byte index 2, bit index 0, bit length 16) contains the returned setpoint. It can be processed like a measured value. The actual setpoint is addresses as byte index 4, bit index 0, bit length 16. Object template Dat12D_S The object template Obj. 6 Dat12D_S is intended for a 12 double word (each 32 bits) data area as found, for example, in an ST7 communication object based on a Dat12D_S data point typical. Data area of a message block Dat12D_S D word 1 D word 2 D word 3... D word 12 Byte index Bit index Bit length NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-26 SINAUT ST7cc Manual (05/2002)

113 Working with ST7cc Config In principle, the information and structure in the double word of the communication object may vary from one double word to another. The data area of a double word is defined twice in the template, in other words, the configuration engineer is offered a 32-bit data area below the description (Type S, Length 32, Subtype 1) as a doubly long integer and below (Type M, Length 32, Subtype 4) as a real number. There is no intended overlay of structures behind this (it is purely for demonstration). If the default is not suitable for the application at hand, the user will need to change the parameters for all of the tag descriptions. The tag descriptions that are not required should be deleted during the decoding of communication object. Object template Par12D_S The object template Obj. 7 Par12D_S is intended for a data area that is sent and returned as a double word with 12 parameters/setpoints. The first word (byte index 0, bit index 0, bit length 16) may contain a code that is set locally for the setpoint/parameter. In principle, the information and structure in the double word of the communication object may vary from one double word to another. Data area of a message block Par12D_S Word 1 D word 1... D word 12 D word D word 24 Meaning Local_ Return value 1 Return value 12 Setpoint 1 Setpoint 12 Operation Byte index Bit index Bit length Note the internal circumstance in the example for object template Obj. 7 Par12D_R. Tag 1 'Local_Operation' should not be changed since this tag is reserved for the internal system function (local settings). The data area that can be used by the configuration engineer first begins with byte index 2 and then extends twelve double words which contain the return valves (for ST7cc), and index 50 extending twelve double words which contains the locally entered setpoints / parameters or the setpoints / parameters to be sent to the automation level by ST7cc. SINAUT ST7cc Manual (05/2002) 4-27

114 Working with ST7cc Config Dialog Notes about Handling Object Templates The following eight dialog steps show how to enter a new object template and configure it. The interactive dialog for changing an object template is selfexplanatory for the configuration engineer. 1. Select the library. 2. Context menu with right mouse button 3. Enter the name of the new object template and enter (optional) application comments. 4. Context menu with right mouse button for entering the tags of the template Fig Dialog steps 1 to 4 for entering a new object template 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-28 SINAUT ST7cc Manual (05/2002)

115 Working with ST7cc Config Refer to Section for more information about the parameters "Type" and "Subtype" for the tag description. See Section 4.3 and the following pages for more information about the parameters of the message block. 5. Select the tags. 6. Configuration of the tags 7. Dialog for entering the 'Number of the message' 8. Configuration of the message block Fig Dialog steps 5 to 8 for entering a new object template SINAUT ST7cc Manual (05/2002) 4-29

116 Working with ST7cc Config Decoding Using Object Templates The Templates library offers the configuration engineer the available object and typical templates. Empty object templates (templates with the name OB 0) do not contain decoding. A communication object from the ST7 environment can be uniquely identified by its subscriber and object number. This fact is also reflected in the interactive dialog. The configuration engineer first sets up the subscribers (stations) (menu: 'Edit', command: 'New Subscriber'), and then assigns decoding for the subscriber. Notes about subsequent dialogs: New, empty decoding is created below a subscriber with the menu command Insert 'New Object'. Specifying the object number of the communication object gives the decoding a unique identity (subscriber number, object number). Copying and inserting designates an object template and existing decoding as an 'object' and an 'object tree branch'. Decoding: Using Object Templates Starting basis: ST7cc 'Object Templates' library Insert 'new object Select object templates. Copy an object tree branch Insert an object tree branch Select existing decoding Copy an object tree branch Insert an object tree branch Decoding for object m Decoding for object n Decoding for object n Decoding for object q Project library Complete creation of the decoding with entering the parameters. Adapt copied template and enter the parameters. Adapt copied decoding and enter the parameters. Method 1 Method 2 Method 3 Fig Methods for inserting decoding 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-30 SINAUT ST7cc Manual (05/2002)

117 Working with ST7cc Config Entering the object number establishes an address reference to the communication object (subscriber number, object number). This is followed by the actual decoding and configuration of the tags (entering the group names, tag names, location information, byte index, bit index, length, typing etc. and possibly parameters for other processing). The byte index, bit index and length parameters sets the information unit to be decoded in the communication object. Using object templates usually means having to rename the group and tag names, adapt the parameters and delete the tags in the template that are not required. An experienced configuration engineer may find it easier to simply use an empty template and enter the information from scratch rather than change all of the parameters and delete the unneeded tags. Steps (1) and (2): Select and copy a template, e.g. 'Bin04B_S', Insert the template below 'Station i', Enter Object number 50 Step (3): Definition of the tags (group name, tag name, typing) and entering all of the parameters. Communication object of Station i Obj. 50 (Type: Bin04B_S) Bit7: Bit6: Bit5: Pump1 FAULT Bit4: Bit3: Pump1 STAT Bit2: Bit1: Pump1 BMOD Bit0: Pump1 BTYP Bit7 (byte 2): : Bit0 (byte 4): Decoding Parameters Group name: Pump1 Tag name: FAULT Location information for messages: Byte index: 0 Bit index: 5 Length: 3 Type: S Subtype: 1 Parameters for other processing: MB Message processing TB Text block input AB Archive processing Fig. 4-17: Example for inserting decoding SINAUT ST7cc Manual (05/2002) 4-31

118 Working with ST7cc Config Dialog Notes for Decoding with Object Templates The following eight dialog steps show how to enter a new object template and configure it. The interactive dialog for changing an object template is selfexplanatory for the configuration engineer. 1. Select and copy the object template. 2. Select the subscriber and insert the previously copied object template. 3. Configure the 'default' tags, e.g. Tag 1.! The combination of a group name and tag name has to be unique throughout the project. Fig Dialog steps 1 to 3 for decoding an ST7 communication object using an object template Note about name the decoding / of the object: 'Ana04W_S' was taken from the object template and can be changed when it is inserted into the template. The decoding/object name is not included in any other processing at this time. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-32 SINAUT ST7cc Manual (05/2002)

119 Working with ST7cc Config Note about subscriber names: The subscriber name is relevant during the generation of the WinCC tags for the tags of the system typical, 'Subscriber'. It is not relevant for the decoding of the ST7 communication objects. The subordinate processing can be displayed by double-clicking on the tag. 4. Select the tag and press the right mouse button. Processing that can be assigned to a tag. Fig Dialog steps 1 to 3 for decoding an ST7 communication object using an object template The configuration of the message, text, archive and parameter blocks is described in detail under Section 4.3. SINAUT ST7cc Manual (05/2002) 4-33

120 Working with ST7cc Config Notes about Object Templates Tags of the 'System' system typical Definition and default settings for tags which cannot be changed once they have been decoded using typical templates. Subtypical 1 of typical 100 Subtypical 2 of typical 100 Fig. 4-20: Overview of currently available typical templates. The number range 1 to 99 is reserved for system objects (hardware and software components) in typical templates. The tag description of these typical templates should not be changed. Typical templates with numbers >= 100 are templates that are provided as 'decoding models' and may be modified by the user. The user can define other typical templates based on any applicable repeating structures. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-34 SINAUT ST7cc Manual (05/2002)

121 Working with ST7cc Config Dialog Notes about Handling Typical Templates As explained in section 4.1.5, a typical is like logical parentheses for up to 99 subtypicals. The subtypicals represent the actual default models. The name of the subtypical is not used in subsequent processing and is primarily intended to provide the configuration engineer with verbal information about the subtypical and therefore allow an overview. Select 'Library' and press the right mouse button. Select Subtypical T103.1 and press the right mouse button. Parameters entered during decoding Parameters of tags which cannot be changed during subsequent decoding Fig. 4-21: Dialog steps for creating a typical template SINAUT ST7cc Manual (05/2002) 4-35

122 Working with ST7cc Config Decoding Using Typical Templates: Decoding using typical templates involves the use of typical templates and their subtypicals (see below) for decoding of the communication objects to take advantage of the default models they provide. T 'Messages pump type A' Messages for pump type A Tag1: BTYP Tag2: BMOD Tag3: STAT Tag4: FAULT Subtypical 1 of typical template 100 T Commands pump type A Instance 1 of decoding for Pump 1 with offset 0 Pump1 etc. corresponding to the 'Group name' Instance 1 of decoding for Pump 2 with offset 1 Commands for pump type A Tag1: OFF Tag2: ON Tag3: RESET Instance 2 of decoding for Pump 1 with offset 0 Subtypical 2 of typical template 100 Pump1 Pump 2 Pump 3 Pump 4 Obj. 50 (Type: Bin04B_S) Pump1 Obj. 51 (Type: Cmd01B_R) Obj. 52 (Type: Cmd01B_R) Pump2 Pump3 etc. Instance 2 of decoding for Pump 2 with offset 0 Fig. 4-22: Defining decoding using a subtypical 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-36 SINAUT ST7cc Manual (05/2002)

123 Working with ST7cc Config The illustration above shows the essential context of decoding based on typical templates. Note 1: A typical template consisting of two subtypicals is defined for decoding Pump i with pump type A. A subtypical is uniquely identified by the typical template number and subtypical number. Note 2: Communication objects are decoded just as before. By decoding Object 50, the first repeating partial structure is described by subtypical T100.1, in other words. an instance (copy) of the required subtypical is created. More instances based on this subtypical are created for other repeating structures in Object 50. The individual instances of a decoding are assigned numbers (instance numbers). The offset indicates the byte address where an instanced subtypical begins. If Object 50 in the example above contains the messages of four pumps, the decoding of this objects will contain four subtypical instances. Steps (1) and (2): Insert object below 'Station i', Enter Object number 50 Step (3): 'Instancing of the subtypical', i.e. a corresponding subtypical is instanced (inserted) for each repeating structure. Group name entered during the instancing of the subtypical. Part of tag name taken from subtypical Communication objects of Station i Obj. 50 (Type: Bin04B_S) Bit7: Bit6: Bit5: Pump1 FAULT Bit4: Bit3: Pump1 STAT Bit2: Bit1: Pump1 BMOD Bit0: Pump1 BTYP First repeating structure that is described by a subtypical (including defaults for all parameters). Typical instance 1 Offset for typical instance 2 Second repeating structure that is described by a subtypical (including defaults for all parameters). Typical instance 2 Typical instance i (with i <=9) Fig. 4-23: Parameters (subset) for the decoding of tags Note that typical and object templates can be combined for decoding a communications object when the communication object contains the appropriate combination of information.! Important Wegen der automatischen Erzeugung der Meldenummern muß die maximale Typical-Instanz i <= 9 sein. Man vergleiche Kap SINAUT ST7cc Manual (05/2002) 4-37

124 Working with ST7cc Config Dialog Notes for Decoding with Typical Templates The following eight dialog steps show how to enter a new object template and configure it. The interactive dialog for changing an object template is selfexplanatory for the configuration engineer. Note Whereas an object template is copied and inserted, a typical template and its subtypicals are referenced. 1. Select the subscriber for assigning the decoding. 2. Open the context menu with the right mouse button. 3. Definition of an objects (decoding) to hold several typical templates (subtypicals) 4. Open the context menu with the right mouse button. Typical instance i (with i <=9) 5. Up to 99 subtypicals can be used for the decoding. Type: Number of the typical Subtype: Number of the subtypical within a typical template Fig Dialog steps 1 to 3 for decoding using typical templates 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-38 SINAUT ST7cc Manual (05/2002)

125 Working with ST7cc Config The temporary default, Instance1, is overwritten when the group name is entered. Fig Dialog steps for decoding using typical templates If any tags in the decoding are assigned for further processing, e.g. archive processing (AB), other text entries for message processing (TB) or technological processing (PB), this has to be carried out individually for each tag since such processing is contained in the typical templates. SINAUT ST7cc Manual (05/2002) 4-39

126 Working with ST7cc Config Final Notes about Decoding Note 1: Object and typical templates can be used together in order to decode all of the information units of an ST7 communication object. The two procedures do not hinder one another in a single decoding. Note 2: The essential difference between decoding based on typical template and using object templates is that subsequent changes in a typical template have an effect on all instances (included decoding). Note 3: The decoding of ST7 communication objects can also be performed by copying ('Copy - Object Tree Branch') and inserting ('insert - Object Tree Branch existing configured decoding. In this case the optional processing (AB, TB, PB) is also included. Note 4: The combination of a group name and tag name has to be unique throughout the project. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-40 SINAUT ST7cc Manual (05/2002)

127 Working with ST7cc Config 4.3 Processing Configuration Processing for individual tags is defined by processing instructions. The following processes will be explained in detail: - Message processing - Supplementary texts (entered by user text blocks during message processing) - Raw value adjustment - Counter value processing - Archiving These processes are carried out using the message time stamp provided by the automation device Message Processing The ST7cc server and the WinCC messaging system work together to perform the tag processing. ST7cc Functions: Input of the parameters required for message processing in the parameter blocks MB and TB. Each tag can be assigned with several message and text blocks as required by the technical process in order to be able to subsequently report a variety of events. Generation of individual WinCC messages and their import into WinCC. This is performed during the generation of the WinCC tag list based on the ST7cc parameter data. Generation of message triggers: When new process information is passed to the ST7cc server, the server in addition to its other duties checks if a message trigger should be generated based on the current process value and the message configuration ('trigger value' parameter and 'code') and sent to the WinCC messaging system for execution (assembly of the concrete message, display and archiving). WinCC Functions: Import of the individual messages generated by ST7cc Config. This configuration data can be 'post-processed' in WinCC. Note, however, that regeneration of the tag list by ST7cc means that the WinCC postprocessing will be lost. It is recommended to carry out any required postprocessing with scripts that can be reused after any ST7cc generation. Receiving of the message trigger generated by the ST7cc server and the generation of the actual message including its insertion into the message window and its archiving. Messages can be configured for types of tags (M, S, Z, A and D). SINAUT ST7cc Manual (05/2002) 4-41

128 Working with ST7cc Config Message Number The configured messages can be uniquely identified in WinCC by their number. The message number therefore has a crucial value in the WinCC message system. Note Since various number ranges for message numbers are reserved by WinCC and ST7cc is designed to save the user from having to manually enter message numbers by using an algorithm, a value range from approximately 2 million to 500 million is available message number configured by ST7cc. In WinCC the message is deposited with a WinCC message number unique within project and formed by the: Subscriber number of the communication subscriber Number of the communication object Number of the subtypical instance (or 0 for tags that are not linked to an instance, i.e. for decoding using object templates) ST7 message number (sequential numbering of tag messages) The exact definition for forming this number can be globally configured by the message number format. Possible values are: sssoooimm Structure Description Possible number range sss Subscriber number (station number) ooo Object number I Typical instance number 1-9 mm Number of the message block 1-99 ssssooimm Structure Description Possible number range ssss Subscriber number (station number) oo Object number 1-99 I Typical instance number 1-9 mm Number of the message block 1-99 The total number of places (sssoooimm = 9 places) may not be changed. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-42 SINAUT ST7cc Manual (05/2002)

129 Working with ST7cc Config User text that can be inserted into the message, e.g. in user text block 'No. 5' (location information). Subscriber number Object number User text that can be inserted into the message, e.g. in user text block 'No. 1' (message text). Number of the message block (numbering of the message 'within' the tag Example of this message number: sss ooo i mm The typical instance number equals 0 since this is decoding using an object template. Fig Example dialog showing the formation of a message number. The message text section provides an explanation about the meaning of the user text blocks. Message Class Message classes in WinCC are used to define the following for all message types belonging to a class: - Acknowledgment scheme - Status texts for 'incoming, 'outgoing, 'acknowledged and 'incoming/outgoing - Output of optical / acoustical signals Each message is assigned to a WinCC message class. This assignment is carried out in the parameter field 'Class' in the MB parameter block ('Details for Message Block'). It should be apparent to the reader at this point why the definition of message classes is important as a "preparatory task" in WinCC. SINAUT ST7cc Manual (05/2002) 4-43

130 Working with ST7cc Config Message Type Message Code A message is assigned to a message type with a WinCC message class. This defines the text and background color of a message in WinCC in its various states: 'incoming, 'outgoing and 'acknowledged. The assignment of a message type to a message class is made in the parameter field 'Type' in the MB parameter block ('Details for Message Block'). It should be apparent to the reader at this point why the definition of message types is important as a "preparatory task" in WinCC. The message code specifies if a message (i.e. an ST7cc message trigger) should be generated only when entering or exiting a state (e.g. when a specific value appears or disappears) or if it should also be generated when any new value appears within the configured permitted value range. * means: The message is generated as 'incoming when the signal a specific value appears; it is generated as 'outcoming when the value disappears.! means: The message is generated again as 'incoming when a new value remains within the value range. Value / Trigger value: A message is generated as 'incoming when the value takes on a specific state which is characterized by a defined range of values. It is generated as 'outgoing when the signal exits the state, i.e. when it takes on a value outside of this value range. The value range can be defined as: - Single value (single number) - Value range (number1 number2) - Listing of single values and value ranges (separated by a comma) Example for value range of a tag with the type 'M': The value range might describe a temperature range of a medium which should trigger a message when it appears. By specifying a second value range (second MB parameter block) of , a more narrow monitoring range can be defined for triggering another message from ST7cc. With this method the value range can be used to signal attainment of a first upper limit and the value range can be used to signal attainment of a second upper limit. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-44 SINAUT ST7cc Manual (05/2002)

131 Working with ST7cc Config Example for value range of a tag with the type 'S': Signals can be - binary (i.e. either value 0 or 1) or - polyvalent (i.e. values from a bit range corresponding to a tag length) Reference is made to multiple pole signals, whereby the number of poles represent a number of bits that code the signal value. The value range 0,3-5,7, for example, indicates the signal state of a 3-pole signal (bit area of three bits) that is active when the signal takes on a value of 0, 3, 4, 5 or 7. Message Text The actual text of the message. In addition to this text, the context information, which is provided by the assignment of the message to a tag (subscriber name, group name and tag name), is also made available in WinCC. Other static extra text can also be defined. Display of a message in ST7cc Config: Typical instance number User text that can be inserted into the message, e.g. in user text block 'No. 1' (message text). Number of the message block (numbering of the message 'within' the tag Fig Details of a message SINAUT ST7cc Manual (05/2002) 4-45

132 Working with ST7cc Config Static Extra Texts A message in WinCC can contain up to 10 user text blocks as well as information text (text block 11). The following text blocks are set by default: Block 1: Block 2: Block 3: Block 4: Block 5: Message text Subscriber name. In many applications the subscriber name indicates the location / installation site of the subscriber. Group name Tag name Location information: This is actually a free text field that should contain additional information for the user. When text block 2 already provides sufficient information about the location, entering locational information here would be redundant. By defining supplementary texts you can fill extra blocks for all messages of a tag or replace the default content. You can define a extra text by specifying the block number (block number 11 indicates informational text) and then entering the text itself. Extra text is displayed in ST7cc Config as follows: Block numbers 1 to 5 are set by default. Extra user blocks therefore begin with number 6. 'Extra' user text block for displaying extra information in a message. Fig Details of extra text 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-46 SINAUT ST7cc Manual (05/2002)

133 Working with ST7cc Config Counter Value Processing A counter value is sent as an absolute counter state and recalculated into a physical value by multiplication with a factor. If a counter value is also displayed and/or saved as an absolute value (counter value subcategory 1), the counter value processing is thereby ended. Calculation of Interval Quantities: Interval Definition Interval quantities are defined by an interval duration and a start time within the interval. The time units that can be used are: Week, Day, hour, minute, second. The following values are allowed as interval durations: 1W, 1D, 1h, 30m, 20m, 15m, 12m, 10m, 6m, 5m, 4m, 3m, 2m, 1m The unit for the start time must be smaller than the interval duration and the start time must be within the interval duration. Examples: An interval of 1D with a start time at 6h defines a 24 hour period beginning at 6:00 am. An interval duration of 2m with a start time at 15s defines an interval of 2 minutes duration that begins at the 15th second of the current minute. Note The changeover from daylight saving time to standard time is carried out as follows: The intervals 1W and 1D are increased or reduced by one hour. For all other intervals, additional interval entries are made or the corresponding entries are left out. Calculation of Interval Quantities: Use of Differences and Handling Overruns Calculation of interval quantity begins by determining the difference to the last absolute counter state (preliminary sum). An overrun of the counter is detected when there is a lower counter state than the one previously sent. In this case an overrun value can be used to correct the difference. If the transmitted counter state is marked as the first value by the TD7 software in the automation device (for example, when the counter is replaced), the calculation of the difference is skipped but counter state is internally noted for later difference calculation. SINAUT ST7cc Manual (05/2002) 4-47

134 Working with ST7cc Config Calculation of Interval Quantities: Proportional Distribution After calculation of the preliminary sum, it is determined if the interval limit between current transmission and the last transmission of the value (minimal) has been exceeded. If exceeded, the preliminary sum is proportionally distributed over the intervals involved, i.e., each of the involved intervals is assigned a portion of the preliminary sum that represents its share of the elapsed time. The parameters of the counter value processing are displayed as follows in ST7cc Config: Fig Details of counter value processing Calculation of Interval Quantities: Example The following physical absolute values of a volume counter are transmitted for an interval of 1h with a start time at 0m: Time Absolute value Preliminary sum Time difference 01: liters 01: liters 1000 liters 30 min. 02: liters 1500 liters 45 min. 04: liters 4000 liters 120 min. Archived: Archiving Archived Interval Description Time time stamp quantity 02:15 02: liters 1000 liters for the first half hour and 2/3 of 1500 liters for the second half hour 04:15 03: liters 1/3 of 1500 liters for the first quarter hour and 3/8 of 4000 liters for the following three quarters hour 04:15 04: liters 1/2 of 4000 liters The display of the interval quantity counter is only updated when a new value is transmitted; the displayed quantity shows: Time Interval quantity in the current interval 01:00 0 liters 01: liters 02: liters 04: liters 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-48 SINAUT ST7cc Manual (05/2002)

135 Working with ST7cc Config Note The interpretation of the displayed interval quantity is difficult without a time stamp if the new absolute states do not quickly arrive after the interval begins. The automation device should be configured in such a way that a transmission is triggered each time the interval begins Measurement Value Processing Adjusting Raw Values Raw value adjustments can be defined for measurement values and setpoints. For counter values this occurs during the counter value processing. The adjustment involves converting the raw value integer to a physical value with a floating point format by a linear interpolation between two reference points in the message direction (measurement value, returned setpoint value) before display or archiving. In the command direction (setpoint) the adjustment is performed in reverse. Example: Raw value adjustment for a pressure gauge Physical value Fig Low reference Raw value Raw value adjustment by linear interpolation High reference SINAUT ST7cc Manual (05/2002) 4-49

136 Working with ST7cc Config Interval Based Compression The definition of compressed intervals is similar to that for counter value processing. The following types of compression can be set: - MIN: Archives the interval minimum - MAX: Archives the interval maximum - MOM: Archives the current value at the end of the interval - AVG: Archives the mean value calculated by weighting the individual values with their respective validity duration. This assumes a threshold controlled transmission, i.e., the value is valid in the future beginning with the transmission time stamp. - AV2: Archives the mean value from the means values calculated in the automation device. These values are valid for the interval occurring since the last transmission, not for the future one as is the case with a threshold controlled transmission. It is important here that the mean value calculation is reset in the automation device after every transmission (even, for example, in the case of a general request). A compression interval is thereby completed controlled by the process time. This means that the compression value is calculated when the first value of a new interval arrives and thereby indicates that no other values for the compression interval will be received. For intervals to which no value is added, the most recent valid value is entered as the compression value. The current intermediate result of the compression is always used for the WinCC display. The measurement value processing in ST7cc Config is displayed as follows: Fig Details of measurement value processing 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-50 SINAUT ST7cc Manual (05/2002)

137 Working with ST7cc Config Archiving Archiving can be used for all tag categories; it involves archiving the results of the processing and the signal values for signals. For archiving the tag must be assigned a WinCC archive using an archive name and a archive tag name. Additional information that can be evaluated through the WinCC curve display: - - Name of the physical units of the adjusted value - - Low limit of the scale - - High limit of the scale The following illustration shows how this data can be edited in ST7cc Config: Fig Details of the archiving block SINAUT ST7cc Manual (05/2002) 4-51

138 Working with ST7cc Config 4.4 WinCC Generation Before generating tags, messages or archives, please insure that the following criteria are met: - The project in which you wish to generate is set as the current WinCC project. - The standard language of the project is active. - The channel DLL for the ST7 server (ST7.DLL) is specified in the project. - WinCC is either in the design mode or not started. During the first generation run ST7cc Config reports to all WinCC components. It logs off when you close the generation dialog or activate the WinCC project. Please note the following points as long as ST7cc Config is reporting to WinCC: - If you open the Alarm Logging Editor or the Tag Logging Editor, do not close them. ST7cc Config will not be able to continue generating and cannot log off correctly. - The generated entries cannot be immediately displayed in all editors. If necessary, select the Update command in the menu Tag Management Tag List(Preview) Before beginning the generation press the Tag list button or select the menu command View Tag list to check which tags are present and for duplicate names. Duplicate names are marked in the tag list by two prefixed exclamation marks!!. During the generation, only the first tag with this name is created; name conflicts must be resolved by renaming one of the tags. The tag list can also serve you as a navigation aid to find logically related tags in various communication objects. The current tag selection is maintained when switching between the tag list and the object tree. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-52 SINAUT ST7cc Manual (05/2002)

139 Working with ST7cc Config Generation Variants You can trigger the generation for: - All tags of the project (selected in the main menu) - The tags for one subscriber (selected in the subscriber context menu) - The tags for an object (selected in the object context menu) - Specific tags (selected in the tag context menu) You can also use the delta generation (see section 3.4.4). Generation of the Logical Connections Before generating the tags of a subscriber, a logical connection within the channel unit ST7 server is created under the name of this subscriber along with a tag group of the same name that contains the status tags relevant to the communication for the subscriber. This logical connection is then assigned the newly created tags. The logical connection receives the subscriber address of the subscriber as the address parameter. Existing tags are not changed during the generation. Generation of the Tag Groups The group name is used by WinCC to form tag groups and as the name prefix for the WinCC tag names. For typical-based tags, the name of the typical instance defines the group names. Note If a tag group in WinCC is already defined as an internal group or within another logical connection, the tags cannot be created even if the tag name itself has not yet been used in WinCC. Generation of the Individual Tags The WinCC tag name is derived from the combination of a group name and a tag name in ST7cc Config. The data type of the tags is derived from the processing type in the ST7 server: - Measurement values, counter values and analog signals: 64-bit floating point number - Signals and digital output: 8-bit integers without a sign The channel-based address information of the tags is a combination of the number of the communication object, the number of the typical instance (or 0 for tags not based on typicals) and the consecutive number of the tags. SINAUT ST7cc Manual (05/2002) 4-53

140 Working with ST7cc Config Note Address duplicates may occur if there are tags with the same address information in WinCC that you may have forgotten to delete. The result is that the only tags updated in the data manager are those reported most recently to it by the ST7 server. Editing Generated Tags You can edit the generated tags, for example, to specify a starting value or to carry out a limit value check in the WinCC data manager. If you forego editing there is no reason to use the delta mode (see section 3.4.4). Simply delete all the tags of the channel if you wish and generate everything again. In some circumstances, of course, the delta mode offers time-saving advantages. The following is an example of how the generated tag management in WinCC appears: ST7 channel DLL + unit Logical connection Variable Variable group Fig WinCC tag management Message Management Generation Variants Before generating messages make sure that all message classes and message types used in the project are defined. You can trigger the generation for: - All messages of the project (selected in the main menu) - The messages for one subscriber (selected in the subscriber context menu) - The messages for an object (selected in the object context menu) - The messages for one tag (selected in the tag context menu) You can also use the delta generation (see section 3.4.4). 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-54 SINAUT ST7cc Manual (05/2002)

141 Working with ST7cc Config Message Numbers The message number format specified in the settings determines how the message numbers are formed for the messages to be created. This systematic determination ensures that: - The message numbers in WinCC are unique throughout the project - The WinCC message can be assigned to the object in the object tree For more information about message number format and assignment of text blocks refer to section Message Processing. Note Note that the message number format with which you generate the messages is the same as that entered in the initialization file of the ST7cc server. Avoid possible conflicts in assigning message numbers if you manually create your own messages in WinCC. Assignment of Message Text Blocks The following texts can be configurably assigned to the available message text blocks: subscriber name, group name, tag name, location information, message text. It is recommended to set the message text to text block 1 (WinCC default). Text block 2 (disruption location) can be assigned with either the location information or, if several texts are assigned to the same text block, with these texts assembled in consecutive order from the top down. SINAUT ST7cc Manual (05/2002) 4-55

142 Working with ST7cc Config Special Notes The generated messages are not assigned to any data manager tags since the messaging system operates independent from the data manager and the acknowledgment is performed locally in WinCC. The following example shows an excerpt from the generated message management: Subscriber name (Block 2) Group name Tag name Fig WinCC message management Archives Generation Variants Before generating archive tags make sure that all archives used in the project are defined. You can trigger the generation for: - All archives of the project (selected in the main menu) - The archives for one subscriber (selected in the subscriber context menu) - The archives for an object (selected in the object context menu) - The archives for one tag (selected in the tag context menu) You can also use the delta generation (see section 3.4.4). 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-56 SINAUT ST7cc Manual (05/2002)

143 Working with ST7cc Config Generated Archive Tags The following fields for archive tags are filled out during the generation according to the processing instructions: - Name - Unit - Lower / upper scale limits The name of the data manager tags is entered as a comment. The following example shows an excerpt from the generated archive assignments: Fig WinCC archive assignments Special Notes The archive tag is not assigned to any data manager tags since the archiving system operates independent from the data manager. Acyclical is always entered as the archive type and analog as the tag type. For archives that are filled by the ST7cc server, the curve information is not updated online at present. To get the most recent values, therefore, the dynamic updating of the curve must be turned off and then manually updated by scrolling to the end of the display area. SINAUT ST7cc Manual (05/2002) 4-57

144 Working with ST7cc Config Delta Mode Enter the delta mode by pressing the Delta mode button menu item Edit Delta Mode. or selecting the The changes to the tree are marked as follows in this mode: Blue + : Red - : Green x : a new tree branch has been inserted a tree branch has been deleted an object has been changed Returning to the normal mode by clicking on the button once again or selecting the menu item again allows you to review the changes in WinCC. Changed objects are thereby deleted and regenerated in WinCC. Note The markings cannot be saved for later review in WinCC. It is therefore necessary to exit the program, enter the normal mode and review the changes immediately. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 4-58 SINAUT ST7cc Manual (05/2002)

145 Working with ST7cc Config SINAUT ST7cc Manual (05/2002) 4-59

146 ST7cc Config with EXCEL First Sectioncaption First Mapcaption SINAUT ST7cc Manual (05/2002) 5-1

147 ST7cc Config with EXCEL 5.1 First Sectioncaption First Mapcaption3 First Blocklabelcaption4 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 5-2 SINAUT ST7cc Manual (05/2002)

148 ST7cc Config with EXCEL SINAUT ST7cc Manual (05/2002) 5-3

149 ST7cc Server The Process Image Startup Behavior and Start Order Shutting Down the Server and WinCC Restarting WinCC While the Server is Operating ST7cc Server Status Description for the individual status values SINAUT ST7cc Manual (05/2002) 6-1

150 ST7cc Server 6.1 The Process Image The ST7cc server maintains a persistent process image, i.e., values from the process tags are kept when the server is restarted. When the configuration is changed, the process image is regenerated. The values of variables are taken from the old process image if their type and address information has not changed. This means that after a restart: - Processing of measurement and counter values can be correctly continued. - The only messages triggered are those with a changed output value. 6.2 Startup Behavior and Start Order At startup the ST7cc server carries out the following tasks: - Evaluates the configuration settings - Possible wait for Windows to load completely - Possible start of WinCC - Dynamic link to the active libraries (channel DLL, ODK, SAPI-S7) - Loading of the process image - Deletes all the old WinCC tag lists in the process image - Releases the channel DLL for new WinCC tag lists - Waits for successful logon to the WinCC tag logging and alarm logging - Releases the communication - Sends a lifebeat message to the locally connected TIMs - General request to the locally connected TIMs when the lifebeat message is acknowledged - Detects the subscribers available through the locally connected TIMs - General request to the available subscribers - After a timeout period, sends a disruption message for subscribers for whom no TIM has declared itself responsible Correct operation of the channel DLL can only be guaranteed when WinCC is started by the server. 6.3 Shutting Down the Server and WinCC At shutdown the ST7cc server carries out the following tasks: - Closes down the communication and delete the network management structures - Reports to WinCC that the server is no longer active - Releases the dynamically linked program libraries - Closes the logging system - Saves the process image 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 6-2 SINAUT ST7cc Manual (05/2002)

151 ST7cc Server 6.4 Restarting WinCC While the Server is Operating You can close and restart WinCC while the server is operating. 6.5 ST7cc Server Status You can display the St7cc server status. The status display contains all of the important information about local and remote servers. None of the status displays that are relevant for redundant operation are shown in the status display for single operation. Fig. 6-1 Display of the ST7cc server status Description for the individual status values Status value: Explanation: Status value: Explanation: Status value: Explanation: Number of ST7cc servers Number of configured ST7cc servers. Server start time Starting time of the "ST7 Server program. Current time Current time of the PC. SINAUT ST7cc Manual (05/2002) 6-3

152 ST7cc Server Status value: Displays possible: Explanation: Status value: Explanation: Status value: Displays possible: Explanation: Status value: Displays possible: Explanation: Status value: Explanation: Status value: Displays possible: Explanation: TCO communication active YES NO Indicates if the "tco server program is started. This program is started upstream from the "ST7 Server program and handles the communication between the "Control Center TIM and the "ST7 Server program. Last received message Time stamp of the message most recently received by the control center TIM. WinCC communication active YES NO Indicates if WinCC Runtime is activated. remote server communication active YES NO Indicates if redundant partner PC can be reached and if ST7cc Runtime is running on this computer. last life beat from remote server Time stamp of most recently sent lifebeat message from the remote partner PC. Local buffer active YES NO If WinCC Runtime is not running, all messages are temporarily saved in the local buffer. This buffer is only active when ST7cc Runtime is deactivated. Status value: fill grade local buffer Default: 0 % Explanation: Percentile and absolute display of the number of temporarily saved messages in the local buffer. Status value: fill grade remote buffer Default: 100 % Explanation: Percentile and absolute display of the number of messages sent to the remote buffer. All messages from the control center TIM are saved in this buffer when a redundancy update is carried out between the two server PC. This buffer is always 100% full after initial fill phase. Status value: Explanation: capacity of remote buffer (hh:mm) Time past in hours and minutes for the oldest message in the remote buffer. This allows you to use the remote buffer to determine any downtime that has occurred. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 6-4 SINAUT ST7cc Manual (05/2002)

153 ST7cc Server Status value: fill grade WinCC buffer Default: 0 % Explanation: Percentile and absolute display of the number of temporarily saved messages in the WinCC buffer. When messages are sent by the control center TIM faster than they can be received by WinCC Runtime, they are temporarily saved in the WinCC buffer. Status value: Explanation: Number of local TIMs Number of configured "Control Center TIMs on the MPI bus. Status value: Completion after downtime Displays possible: --- Started when Running remote Waiting Preparing Running local Unknown Explanation: Current status display for a failure update after restarting ST7cc Runtime. Status value: Explanation: Status value: Explanation: Status value: Explanation: downtime start Time when the remote partner failed. The down computer is first displayed after ST7cc Runtime restarts. downtime end Time when the remote partner started running again. The down computer is first displayed after ST7cc Runtime restarts. Index Indicates the current data record number in the remote buffer being updated. SINAUT ST7cc Manual (05/2002) 6-5

154 Diagnostic and Trace Possibilities Diagnostics: Log Server Messages Process Image Messages Sharing violation Create process image from existing memory mapped file At least one client is still attached to the renamed old shared memory file --> sending a detach request now!!! No process image to compare with No object list available No typical list available Copy present process image as reference image Object list is newer than process image Configuration change detected - Server will be restarted in 5 seconds 7-5 Process image is created Create completely new process image There is a process image to compare with Server is newer than process image Typical list is newer than process image WinCC registry entries are discarded WinCC registry entries will be kept WinCC registry entries will be discarded now Communication Error Messages ## Wrong time stamp for message %d/%d (%s) ## ## Partner %d: not available in the process image ## ## Subscriber %d: GR end timeout ## ## Subscriber %d: GR start timeout ## ## Subscriber %d: not available ## ## TIM %d: GR end timeout ## ## TIM %d: GR start timeout ## ## TIM %d: not available ## ## Time marked invalid for message %d/%d ## dll_s7_get_brcv_ind: Error Fifo backlog Communication Status Messages No connection to subscriber %d Communication started Subscriber %d: available via TIM %d Subscriber %d: GR end Subscriber %d: GR start Subscriber %d: GR requested TIM %d (MPI %d): Transport connection established TIM %d (MPI %d): Transport connection not established TIM %d (MPI %d): Connection canceled TIM %d (MPI %d): Connection processing job TIM %d (MPI %d): Connection valid TIM %d: available TIM %d: GR end TIM %d: GR start TIM %d: GR requested SINAUT ST7cc Manual (05/2002) 7-1

155 Diagnostic and Trace Possibilities Received unhandled S7 message Waiting for WinCC startup Time Synchronization Messages ## Time sync message missing! ## Time synchronization active Time for synchronization differs by %d seconds from current time! Please exit WinCC and correct the computer clock!! Parameter Error Diagnostic Messages Subscriber %d: GR complete ## Subscriber %d: GR not completed ## ## Object %d tag %d (%s.%s) not transferred during GR ## ## Partner %d, object %d: not present in process image ## WinCC Tag Logging / Alarm Logging Messages ## Tag logging archive %s tag %s: archiving failed with error code %d (%s) ## ## Message number format error: s = %d o = %d i = %d v = %d m = %d ## ## Alarm logging: creation of message %d failed with error code %d (%s) ## PM-AQUA Link Messages The queue for PM-AQUA archive requests is full.new archive requests will be rejected ## PM-AQUA connection: %d wrong index: %d ## ## PM-AQUA connection: %d Index: %d Time stamp: %s already processed ## ## PM-AQUA connection: %d Index: %d Time stamp: %s invalid (e.g. in the future) ## ## PM-AQUA connection: %d Index: %d PM-AQUA indicated error %d for raw data interface ## Diagnostics: Subscriber Typicals Faceplates: Displays Faceplates: Operator Representation in Tag Management Faceplates: Insertion into the WinCC Project Diagnostics: Server Typicals Faceplates: Displays Representation in Tag Management Faceplates: Detail Display Description for the individual status values Faceplates: Insertion into the WinCC Project Diagnostics: Trace Trace Output Window Information in the Trace Lines Diagnostic: System Typical Messages_per_second Messages_per_minute Message_total database_queue_length Timesync_difference NH7998-7AA11 Siemens AG 2002 All Rights Reserved 7-2 SINAUT ST7cc Manual (05/2002)

156 Diagnostic and Trace Possibilities 7.1 Diagnostics: Log Server Messages The log message are displayed in a separate program, "FEP LOG Server. The log window therefore remains visible even when the ST7cc server is running in the background. Fig. 7-1 Messages displayed in the FEP LOG Server The log messages are used for displaying events during startup of the server and for diagnosing connection states during normal operation. Typical error situations can be easily recognized and corrected by tracking the log messages. During normal server operation no pop-up messages are generated unless there is an attempt to send commands to a subscriber that cannot be reached. Fatal errors during startup of the server (missing program libraries, incomplete installation) result in pop-up messages and the server shuts down once such a message is acknowledged. SINAUT ST7cc Manual (05/2002) 7-3

157 Diagnostic and Trace Possibilities Process Image Messages Sharing violation The process image is contained in a memory mapped file. The following messages about the process image can be generated: The memory mapped file is in use by another program and cannot be opened. Create process image from existing memory mapped file The server found a valid memory mapped file at startup and is using it to build the process image. At least one client is still attached to the renamed old shared memory file --> sending a detach request now!!! Another program was connected with the existing memory mapped file when the server started. The server reorganized due to a change in the process image and therefore the program must attach to the currently valid memory mapped file. No process image to compare with There is no memory mapped file for the process image until now or the existing file has been deleted by the user. No object list available A process image cannot be generated because the object list is missing. Please check the server settings for the object list. No typical list available A process image cannot be generated because the typical list (library) is missing. Please check the server settings for the library. Copy present process image as reference image A memory mapped file has been found but it is no longer valid. The server builds a new process image but uses those values from the old memory mapped file that have not changed in regard to their address or processing. Object list is newer than process image The object list is newer as the most recently saved process image. The process image must be built again based on this object list. Configuration change detected - Server will be restarted in 5 seconds While checking the object list the server detected that a reconfiguration has taken place. It initiates a restart to rebuild the process image. Process image is created The process image has been successfully built. Create completely new process image... The process image is being regenerated and filled with zeros as initial values. There is a process image to compare with An existing process image has been found and its validity is being checked. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 7-4 SINAUT ST7cc Manual (05/2002)

158 Diagnostic and Trace Possibilities Server is newer than process image The process image found is invalid because a new program version was installed. The process image must be built again based on the object list. Typical list is newer than process image The object list is newer as the most recently saved process image. The process image must be built again based on this object list. WinCC registry entries are discarded Existing WinCC tag links still in the process image were deleted after a complete restart of the server. WinCC registry entries will be kept Existing WinCC tag links still in the process image were kept after a restart of the server. WinCC registry entries will be discarded now Existing WinCC tag links still in the process image are being deleted after a complete restart of the server. SINAUT ST7cc Manual (05/2002) 7-5

159 Diagnostic and Trace Possibilities Communication Error Messages Communication error messages are framed by hashes to make them easier to recognize. ## Wrong time stamp for message %d/%d (%s) ## A subscriber has sent a message with an implausible time stamp (too far in the future or in the past). The limits for the plausibility check can be specified in the server settings. ## Partner %d: not available in the process image ## The server has received a message from a subscriber that is not in the process image. The configuration should be checked. ## Subscriber %d: GR end timeout ## The finished message for the general request of a subscriber did not arrive in time, i.e., the general request took too long. The length of timeout can be specified in the server settings. ## Subscriber %d: GR start timeout ## The start message for the general request of a subscriber did not arrive in time after the request was triggered. The length of timeout can be specified in the server settings. ## Subscriber %d: not available ## A subscriber on the WAN can no longer be reached because it has been switched off or all connections have failed. ## TIM %d: GR end timeout ## The finished message for the general request of a local TIM subscriber did not arrive in time, i.e., the general request took too long. The length of timeout can be specified in the server settings. ## TIM %d: GR start timeout ## The start message for the general request of a subscriber did not arrive in time after the request was triggered. The length of timeout can be specified in the server settings. ## TIM %d: not available ## A TIM subscriber on the MPI bus can no longer be reached perhaps because it has been switched off. ## Time marked invalid for message %d/%d ## A subscriber was not able to synchronize its time after a complete restart; it can therefore not load its data although the connection has been correctly established and data can be transmitted. dll_s7_get_brcv_ind: Error Fifo backlog This is a fatal internal error. Please contact the support department. There is an overflow in an internal queue. This may be an overload problem. Please contact the support department. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 7-6 SINAUT ST7cc Manual (05/2002)

160 Diagnostic and Trace Possibilities Communication Status Messages No connection to subscriber %d A subscriber is cannot be reached at the moment. Communication started The communication is activated after a complete restart of the server. This usually occurs after a successful startup of WinCC Runtime. Subscriber %d: available via TIM %d A WAN subscriber is reported as available by a local TIM. Subscriber %d: GR end A WAN subscriber has reported the end of a general request. Subscriber %d: GR start A WAN subscriber has reported the start of a general request. Subscriber %d: GR requested A WAN subscriber has been requested by a general request to send its data. TIM %d (MPI %d): Transport connection established The configured S7 connection to a local TIM subscriber has been established. TIM %d (MPI %d): Transport connection not established The configured S7 connection to a local TIM subscriber could not be established. TIM %d (MPI %d): Connection canceled The configured S7 connection to a local TIM subscriber has been canceled. TIM %d (MPI %d): Connection processing job A send job to the connection for a local TIM subscriber is being processed. TIM %d (MPI %d): Connection valid TIM %d: available TIM %d: GR end TIM %d: GR start The ST7 connection to a local TIM subscriber is valid (i.e., the transport connection is established and the TIM subscriber answers the lifebeat message). A local TIM subscriber reports itself as available. A local TIM subscriber has reported the end of a general request. A local TIM subscriber has reported the start of a general request. SINAUT ST7cc Manual (05/2002) 7-7

161 Diagnostic and Trace Possibilities TIM %d: GR requested A local TIM subscriber has been requested by a general request to send its subscriber records. Received unhandled S7 message A received S7 message is of a type that was not planned for ST7cc. It is ignored. Waiting for WinCC startup ST7cc is waiting for the start of WinCC Runtime to be able to begin communication. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 7-8 SINAUT ST7cc Manual (05/2002)

162 Diagnostic and Trace Possibilities Time Synchronization Messages ## Time sync message missing! ## The time message was not received as planned in the minute cycle. Time synchronization active A valid time message has been received. The server automatically begins with the time synchronization. The system time of the WinCC PC is reset by 'advancing' or 'holding back' the clock by up to 5 seconds per minute to avoid a time jump. Time for synchronization differs by %d seconds from current time! Please exit WinCC and correct the computer clock!! The received time message differs too much from the system time and therefore a gradual adjustment using the synchronization function cannot be used. There is also the danger that messages may be canceled due to an implausible time stamp. For this reason the system time of the computer should be adjusted manually. The maximum time difference for the time synchronization corresponds to the parameter 'Maximum time deviation in the future' in the server settings. SINAUT ST7cc Manual (05/2002) 7-9

163 Diagnostic and Trace Possibilities Parameter Error Diagnostic Messages The following errors can be found by analyzing the results of a general request: a) Objects that are in the automation device and are transmitted but cannot be configured in ST7cc. b) Variables that are configured in ST7cc but not transmitted by the automation device (either because the object does not exist or the configured data area is not included). You therefore have the possibility to check the consistency of the configuration in the automation device and in ST7cc in both directions. Subscriber %d: GR complete All of the values configured for this subscriber were sent for the general request. ## Subscriber %d: GR not completed ## Not all of the values configured for this subscriber were sent for the general request. You then see a list of the objects / tags that were not sent. ## Object %d tag %d (%s.%s) not transferred during GR ## Note which objects / data areas are not present in the automation device. ## Partner %d, object %d: not present in process image ## The data received from the specified subscriber cannot not been assigned to a configured object. Configure the object concerned for this subscriber. If you have already configured the object and this error continues to appear, check if the ST7 server is operating with the correct project file (object list). 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 7-10 SINAUT ST7cc Manual (05/2002)

164 Diagnostic and Trace Possibilities WinCC Tag Logging / Alarm Logging Messages ## Tag logging archive %s tag %s: archiving failed with error code %d (%s) ## Tag logging was not able to fulfill the archiving job for the specified tag. It is possible that the archive tag here was not generated. Generate it if necessary. ## Message number format error: s = %d o = %d i = %d v = %d m = %d ## A part of the message number (s = subscriber number, o = object number, i = typical instance number, v = variable number, m = consecutive message number) does not fit your message numbering convention. The message was not sent in order to avoid accidentally generating a wrong message. Check that the object concerned conforms to the numbering convention. ## Alarm logging: creation of message %d failed with error code %d (%s) ## Alarm logging was not able to generate the message. It is possible that the message here was not generated. Generate it if necessary. SINAUT ST7cc Manual (05/2002) 7-11

165 Diagnostic and Trace Possibilities PM-AQUA Link Messages The queue for PM-AQUA archive requests is full.new archive requests will be rejected. This message appears as a pop-up. Either PM-AQUA is presently not processing any archiving requests, for example, because the runtime has not started, or too many requests have been issued in too short a time. You may wish to increase the size of the archiving buffer. ## PM-AQUA connection: %d wrong index: %d ## It was attempted to access an index that is not configured in PM-AQUA within a process link. ## PM-AQUA connection: %d Index: %d Time stamp: %s already processed ## PM-AQUA denied an archiving request because it is busy with the same or a newer value. This message may also appear after a complete restart if the initial value was entered in the queue from PM-AQUA before it shut down but was not acknowledged and was therefore sent a second time. ## PM-AQUA connection: %d Index: %d Time stamp: %s invalid (e.g. in the future) ## PM-AQUA denied an archiving request because the time stamp was invalid. ## PM-AQUA connection: %d Index: %d PM-AQUA indicated error %d for raw data interface ## An unexpected error code was returned by PM-AQUA. Please look this error code up in the PM-AQUA manual. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 7-12 SINAUT ST7cc Manual (05/2002)

166 Diagnostic and Trace Possibilities 7.2 Diagnostics: Subscriber Typicals Subscriber typicals are used for displaying the most important communication states and allow manual operation of communication functions (for example, general requests, switching to permanent connections) Faceplates: Displays The following faceplate is used to display the communication states of a subscriber. It is linked to the correct tags automatically by changing the object name to the name of the subscriber to be displayed: Fig. 7-2 Faceplate for subscriber displays The meanings of the individual display LEDs in relation to the linked tags are explained in the section after next Faceplates: Operator The following pop-up windows appears by clicking on the faceplate: Fig. 7-3 Faceplates - operator The meaning of the display can be read in plain text in this operation window. It is also possible to enter a command by selecting and clicking on the "OK" button. SINAUT ST7cc Manual (05/2002) 7-13

167 Diagnostic and Trace Possibilities Representation in Tag Management A subscriber typical is represented in the WinCC tag management by the following tags each with their respective values (I = input, O = output): Tg name I/O Value / LED color / LED blinking Description or Message text Data path I 0 Red N No connection (in the faceplate 1 Yellow N Redundancy disrupted connection) 3 Green N Connection OK GR I 0 Off N No GR 1 Yellow N GR requested 2 Yellow Y GR start 3 Green N GR end 4 Red N GR start timeout 5 Red N GR end timeout clock I 0 Red N Time invalid 1 Green N Time is valid Dialup_Connection I 0 Off N No connection 1 Green Y Outgoing call activated 2 Green N Incoming call established 3 Green N Outgoing call established Permanent_connection I 0 Off N No permanent connection 1 Green Y Permanent connection reported 2 Green Y Permanent connection canceled 3 Green N Permanent connection established GR_requested O Request general request Perm_Connection_Online O Switch on permanent connection Perm_Connection_Offline O Switch off permanent connection You can also use these tags in your graphics to display the status of a subscriber Faceplates: Insertion into the WinCC Project The following files are copied into the 'Data' subdirectory of your ST7cc installation directory: "stations_typical.pdl" and "fpl_1.pdl". To be able to use the faceplates in your WinCC project, carry out the following steps: 1) Copy the file "fpl_1.pdl" into the subdirectory "GraCS" of your WinCC project. 2) Open the graphic in the Graphics Designer where you wish to place your station typical. 3) Also open the "stations_typical.pdl" graphic in the Graphics Designer and copy the faceplate into it. 4) Insert the faceplate into your destination graphic and change the object name to the name for the subscriber to be displayed (group name of the subscriber tags in the WinCC tag management). 5) Paste a copy of the "FPL" object in your destination graphic. You only need one copy even if you wish to display several subscribers. 6) If the tags are already generated you can now start WinCC Runtime and test your graphic! 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 7-14 SINAUT ST7cc Manual (05/2002)

168 Diagnostic and Trace Possibilities 7.3 Diagnostics: Server Typicals Server typicals are use to visualize the important server states and to provide information about any updates made after failures occur Faceplates: Displays The following faceplate is used to display the server status. It is connected with the appropriate tags by changing the object name of the name of the server to be displayed (name must be identical to the name in ST7cc Config): Fig. 7-4 Faceplate for ST7cc server status Representation in Tag Management A subscriber typical is represented in the WinCC tag list by the following tags each with their respective values (I = input): Tag name I/O Value / LED color / LED blinking _Quantity_of_ST7cc_Ser vers Description or Message text I Number of ST7cc servers _Quantity_of_local_TIMs I Number of local TIMs _update_after_downtime I 0 Gray N No redundancy I 1 Green N Not used I 2 Yellow Y Started when I 3 Green Y Running remote I 4 Yellow Y Waiting I 5 Yellow Y Preparing I 6 Green Y Running local I 7 Yellow N Unbekannt _TCO_communication_a ctive _WinCC_communication _active _Remote_server_commu nication_active I 0 Yellow N Unbekannt I 1 Red N Not active I 2 Green N Active I 3 Gray N Not used I 0 Yellow N Unbekannt I 1 Red N Not active I 2 Green N Active I 3 Gray N Not used I 0 Yellow N Unbekannt I 1 Red N Not active I 2 Green N Active I 3 Gray N Not used SINAUT ST7cc Manual (05/2002) 7-15

169 Diagnostic and Trace Possibilities You can also use these tags elsewhere in your faceplates to display the status of a server Faceplates: Detail Display The following pop-up windows appears by clicking on the faceplate: Fig. 7-5 Faceplate detail display The meaning of the display can be read in plain text in this detail window. Description for the individual status values Status value: WinCC tag: Explanation: Status value: WinCC tag: Explanation: Status value: WinCC tag: Explanation: Status value: WinCC tag: Displays possible: Explanation: Quantity of ST7cc servers: _Quantity_of_ST7cc_Servers Number of configured ST7cc servers. Server start time: _Server_Start_Time Starting time of the "ST7 Server program. Current time: _Current_Time Current time of the PC. TCO communication active: _TCO_communication_active YES NO Indicates if the "tco server program is started. This program is started upstream from the "ST7 Server program and handles the communication between the "Control Center TIM and the "ST7 Server program. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 7-16 SINAUT ST7cc Manual (05/2002)

170 Diagnostic and Trace Possibilities Status value: WinCC tag: Explanation: Status value: WinCC tag: Displays possible: Explanation: Status value: WinCC tag: Displays possible: Explanation: Status value: WinCC tag: Explanation: Status value: WinCC tag: Displays possible: Explanation: Last received telegram: _Last_received_telegram Time stamp of the message most recently received by the control center TIM. WinCC communication active: _WinCC_communication_active YES NO Indicates if WinCC Runtime is activated. remote server communication active: _remote_server_communication_active YES NO Indicates if redundant partner PC can be reached and if ST7cc Runtime is running on this computer. Last life beat from remote server: _Last_lifebeat_from_remote_server Time stamp of most recently sent lifebeat message from the remote partner PC. Local buffer active: _Local_buffer_active YES NO If WinCC Runtime is not running, all messages are temporarily saved in the local buffer. This buffer is only active when ST7cc Runtime is deactivated. Status value: Fulls level of local buffer: WinCC tag: _fulls_level_of_local_buffer Max_fulls_level_of_local_buffer Default: 0 % Explanation: Percentile and absolute display of the number of temporarily saved messages in the local buffer. Status value: Fulls level of remote buffer: WinCC tag: _fulls level_of_remote_buffer _ max_fulls level_of_remote_buffer Default: 100 % Explanation: Percentile and absolute display of the number of messages sent to the remote buffer. All messages from the control center TIM are saved in this buffer when a redundancy update is carried out between the two server PC. This buffer is always 100% full after the initial fill phase. Status value: WinCC tag: Explanation: Capacity of remote buffer (hh:mm): _capacity_of_remote_buffer Time past in hours and minutes for the oldest message in the remote buffer. This allows you to use the remote buffer to determine any downtime that has occurred. SINAUT ST7cc Manual (05/2002) 7-17

171 Diagnostic and Trace Possibilities Status value: Fulls level of WinCC buffer: WinCC tag: _fulls_level_of_wincc_buffer _Max_ fulls_level_of_wincc_buffer Default: 0 % Explanation: Percentile and absolute display of the number of temporarily saved messages in the WinCC buffer. When messages are sent by the control center TIM faster than they can be received by WinCC Runtime, they are temporarily saved in the WinCC buffer. Status value: WinCC tag: Explanation: Quantity of local TIMs: _quantity_of_local_tims Number of configured "Control Center TIMs on the MPI bus. Status value: Update after downtime: WinCC tag: _update_after_downtime Displays possible: --- Started when Running remote Waiting Preparing Running local Unbekannt Explanation: Current status display for a failure update after restarting ST7cc Runtime. Status value: WinCC tag: Explanation: Status value: WinCC tag: Explanation: Status value: WinCC tag: Explanation: Downtime start: _downtime_start Time when the remote partner failed. The down computer is first displayed after ST7cc Runtime restarts. Downtime end: _downtime_end Time when the remote partner started running again. The down computer is first displayed after ST7cc Runtime restarts. Index: _Index Indicates the current data record number in the remote buffer being updated. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 7-18 SINAUT ST7cc Manual (05/2002)

172 Diagnostic and Trace Possibilities Faceplates: Insertion into the WinCC Project In ST7cc Config you can copy all faceplates into your WinCC project by using the menu command "Administration / Copy Faceplates to WinCC Project. To be able to use the faceplates in your WinCC project, carry out the following steps: 1) Open the graphic in the Graphics Designer where you wish to place your server typical. 2) Also open the "server_typical.pdl" graphic in the Graphics Designer and copy the faceplate into it. 3) Insert the faceplate into your destination graphic and change the object name to the name for the server to be displayed. 4) Paste a copy of the "FPL" object in your destination graphic. You only need one copy even if you wish to display several servers. 5) If the tags are already generated you can now start WinCC Runtime and test your graphic! 7.4 Diagnostics: Trace The trace function is started in a separate program with the name "trhi.exe. This trace can be called up by the following menu command: Fig. 7-6 Starting the Trace program SINAUT ST7cc Manual (05/2002) 7-19

173 Diagnostic and Trace Possibilities All of the started programs are displayed in the basic window of Trace. Up to four separate programs can be simultaneously written to different trace output files. To activate the trace for a program, select the program and switch on the trace from the context menu (right mouse button). Note When the trace diagnostics is completed, the trace output for this program has to be deactivated as well. Activated trace points for the selected program ST7cc Server program Activate and deactivate the trace function Activates the trace output files Displays the program that is being traced Fig. 7-7 Basic window of the Trace program 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 7-20 SINAUT ST7cc Manual (05/2002)

174 Diagnostic and Trace Possibilities Trace Output Window The output window is a list field with the trace data and the following check boxes: - (De) activate automatic scrolling for new messages - Clear all message in the output window Fig. 7-8 Trace window with output Information in the Trace Lines Each trace line contains: - The time information - Information about the triggering trace point: = ST7 message trace as well as other trace points for internal diagnostics - A function call ID: - E = Enter - T = Text - R = Return - An English trace text that begins with the name of the called function. The trace example shows the analysis of the content and the processing of a time synchronization message. SINAUT ST7cc Manual (05/2002) 7-21

175 Diagnostic and Trace Possibilities 7.5 Diagnostic: System Typical The system typical allows you to display of some of the performance statistics of the system. The system typical requires that subscriber 0 (system subscriber) is assigned as subtype 0. The following tags are generated and configured for this subscriber: Messages_per_second Number of received messaged within the last second Messages_per_minute Message_total Number of received messaged within the last minute Total number of messages received since the start of the server database_queue_length Timesync_difference Length of the queue for values to archive still in the tag logging Difference in seconds between the computer's system time and the time according to the time master TIM 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 7-22 SINAUT ST7cc Manual (05/2002)

176 Diagnostic and Trace Possibilities SINAUT ST7cc Manual (05/2002) 7-23

177 PM-AQUA Link PM-AQUA Process Links Process Link Process Link Number Index The Data Transmission Process PM-Aqua Configuration with ST7cc Config Configuring the Tags for the PM-AQUA Process Links Archiving Instructions for PM-AQUA Message Types and Data Formats Used Optimization of the Handshake Procedure SINAUT ST7cc Manual (05/2002) 8-1

178 PM-AQUA Link 8.1 PM-AQUA Process Links Process Link The connection between ST7cc and PM-AQUA is made via PM-AQUA process links (see "PM-AQUA Configuration Instructions and Description of Run-time Module V3.0", February 1999 issue, Chapter 8 "Process Links"). This chapter is a brief summary of the referenced chapter and does not intend to provide the complete details. A process link uses raw data tags to transmit process-controlled data from WinCC to PM-AQUA. 'Process-controlled' here means that ST7cc determines the point in time when the data is transferred. Three WinCC tags per connection are needed to perform the data transmission: One raw data tag through which the data message is sent, and two 16-bit tags that are used for the handshake between the PC program and the automation system (AS). The convention for the WinCC tags is defined as follows: "PM-AQUAxxASPC": 16-bit word tag for handshake from ST7cc "PM-AQUAxxPCAS": 16-bit word tag for handshake from PM-AQUA "PM-AQUAxxDATA1": Raw data tag (filled by ST7cc with a value + time stamp) xx in the tag name is a wildcard for the process link number. Process Link Number Index A process link is identified by a process link number. ST7cc Config supports process links 1 9. The data transmitted through a process link are identified by an index. A processcontrolled measurement value or maintenance counter has exactly one index designation within a process link. Any index can be assigned but for clarity's sake it is best to use consecutive numbers within a station. The Data Transmission Process ST7cc fills the raw data tag PM-AQUAXXDATA1 with data. ST7cc writes the bits in PM-AQUAXXASPC Bit 1 is set to indicate that the data should be archived. Bit 0 is set to indicate that the data is complete. PM-AQUA accepts the data. PM-AQUA sets PM-AQUAXXPCAS with the error number. PM-AQUA sets PM-AQUAXXPCAS bit 0 to indicate the data is accepted. ST7cc evaluates the error number and deletes PM-AQUAXXASPC bit 0 / 1. PM-AQUA deletes PM-AQUAXXPCAS bit 0. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 8-2 SINAUT ST7cc Manual (05/2002)

179 PM-AQUA Link 8.2 PM-Aqua Configuration with ST7cc Config Configuring the Tags for the PM-AQUA Process Links A subscriber with the subscriber number 0 (system subscriber as container for the system object) must be created. Object 10 for PM-AQUA process links is reserved within this subscriber. For the process links there is typical type 2, subtype 1 which must be instanced once for each connection used within object 10. The number of the instance must be identical with the number of the process link, the name of the instance must be PM-AQUA0x, whereby x stands for the number of the process link. Fig. 8-1 Configuring the tags for the PM-AQUA process links The tags for the PM-AQUA process link can then be generated like any other tag. SINAUT ST7cc Manual (05/2002) 8-3

180 PM-AQUA Link Archiving Instructions for PM-AQUA If an archiving instruction refers to the archive name PM-AQUA0x and contains a valid index number within the PM-AQUA process link instead of a tag name, the archiving is performed through PM-AQUA instead of WinCC. No WinCC archive tag is created in the generation. The unit field of the archiving instruction can contain an interval duration specification. This consists of a number followed by one of the time units, s, m, h, d, for seconds, minutes, hours and days. For example, valid interval durations might be: 15s, 1m, 5m, 1h, 1d, etc. The interval duration information is interpreted as a notification period if the value is a measurement. Since PM-AQUA interprets the time stamp as the time of the interval start when the mean value is sent, and the archiving functions of ST7cc in contrast normally uses the transmission time stamp (time stamp of interval end), this information is used by ST7cc to correct the time stamp for PM-AQUA. If the value is from a counter, the interval duration information is sent to PM-AQUA as value resolution information. The other parameters of the archiving instructions (scale information) are ignored. Fig.8-2 Archiving instructions for PM-AQUA The preprocessing functions of ST7cc (raw value adjustment, interval-based compression) can be optionally used. It is recommended to compress the process data in the PM-AQUA basic cycle (15 minutes) to reduce the archiving load on the system (see also section 5.3). 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 8-4 SINAUT ST7cc Manual (05/2002)

181 PM-AQUA Link Message Types and Data Formats Used Measurement values and signals are forwarded to PM-AQUA as measurement values (message type 0x02), counter values as counter values (message type 0x23). If the unit field contains a valid interval duration specification, a counter value is sent to PM-AQUA as a counter status for operational hours using the interval duration information as value resolution information (message type 0x21). Only one value per message without the status is sent as an S7 float value in each case. The S7 time format is used as the time stamp format. All values sent to PM-AQUA are generally assigned an archiving ID. 8.3 Optimization of the Handshake Procedure PM-AQUA is configured by default to monitor the handshake variables in a time cycle of 2 seconds. This results in a total duration for the handshake procedure of 4 seconds per value. To optimize the handshake for ST/cc, the following registry DWORD entries for PM-AQUA should be entered and set to the value 0: HKEY_LOCAL_MACHINE\SOFTWARE\SIEMENS\PM\DMSYSTEM\ChangeCycle HKEY_LOCAL_MACHINE\SOFTWARE\SIEMENS\PM\DMSYSTEM\CycleCycle Valid values for these entries for monitoring the handshake variables: 0 = Upon change 1 = 250 ms 2 = 500 ms 3 = 1 s 4 = 2 s Setting the value to 0 enables the optimum reaction times. As long as the PM-AQUA raw data interface is operated only in connection with ST7cc, no side effects should be expected. Even so, expect on a typical system (for example, Pentium II-300, 128 MB RAM) a throughput of not more than 1 to 2 values per second. SINAUT ST7cc Manual (05/2002) 8-5

182 PM-AQUA Link 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 8-6 SINAUT ST7cc Manual (05/2002)

183 ACRON Link Importing Historical Files (CSV, DBASE) Background Link for Importing Historical Values Syntax of External Variables Provider Settings Driver Parameters ACRON Project Settings with ST7cc Config ACRON Project Settings with ST7cc Config Archiving Instructions for ACRON Notes SINAUT ST7cc Manual (05/2002) 9-1

184 ACRON Link 9.1 Importing Historical Files (CSV, DBASE) Background The ACRON provider is used by all interfaces to receive data from the process. This also applies to the file interface. The imported files are saved to a configured path (import path). The provider cyclically checks if a new file is available in this path. If so, the data from such a file is automatically entered into the ACRON database. The file is then deleted by the ACRON provider once the data has been successfully imported. Any errors that occur are logged to a file ("File_name.CS_"). This log file is in the CSV format and can be imported again by renaming the "File_name.CSV". Measurement values, maintenance counter values and alarms can be imported. Maintenance pulses cannot be imported! The maintenance count has to be generated in the PLC for this Link for Importing Historical Values All data is usually imported. Existing data with the same time stamp is overwritten. Two formats are used for importing data: DBASE format with the file extension " *.DBF" and CSV format with the file extension " *.CSV". The file names have to begin with the letters "A" or "B" in order to be able to distinguish between value files and historical alarm files. The table structure is the same for both formats and appears as follows: Field name Field type Comments DATETIME Char, max. 30 The time and date appear as a character string with characters the format: VARIABLE Char, max. 64 characters VALUE Char, max. 64 characters YYYY-MM-DD SS:MM:HH This shows the name of an external variable configured in ACRON. This shows the currently entered value of the variable as a character string. Both a period and a comma are accepted as the decimal separator. Scientific notation is also accepted. The valid value range is between -10^34 and +10^34 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 9-2 SINAUT ST7cc Manual (05/2002)

185 ACRON Link Other optional fields Status Numeric, 1 character MEANTIME Char, max. 32 characters Type Char, 1 character 0: Value is invalid 1: Value is valid When this entry is not present or is "0", ACRON assumes that this is a single value.when the entry is > 0, the value applies for a period of seconds counting backwards from the time sent. Indicates the type of variable. A: Mean value or current value M: Minimum X: Maximum Any number of records can be contained in a table. ACRON deletes each entry once it has been successfully imported. The complete table is deleted once all entries have been successfully imported. The name of table has to begin with the letters "A" or "B", the file extension has to be either " *.DBF " or " *.CSV ". A semicolon is used as the separator character for the fields. Example: :23:00;Received; :23:00;Sent; :10:00;Received; :10:00;Sent; :12:00;Received;110.5;1;0;X :12:00;Sent;202.5;1;86400;A Any lines in the file that do not begin with a number are ignored. Field bracketing characters such as or " are accepted Syntax of External Variables Enter the name of variables in the ACRON Designer exactly as they appear in the DBASE or CSV file. SINAUT ST7cc Manual (05/2002) 9-3

186 ACRON Link Provider Settings Write interval This setting has no relevance for importing historical files. First value: Recommended setting: 0 sec. Measurement interval Recommended setting: 60 sec. Max./Min. evaluation This option is not supported by this link Driver Parameters 1. Parameter: Path for saving files 2. Parameter: Time tolerance. If the historical data was measured at another point in time as the automatic data, this parameter can be used to specify a time tolerance in seconds for sorting the existing data. This saves disk space since no new records for historical data needs to be written when the records within this tolerance range already exist. However, if you wish to log historical data only or need the time of the measurement to the exact second, you will need to enter zero seconds here. 30 seconds is a good value in most other circumstances. If you are already using a provider with another link in order to record data, you should enter one half of the write interval of this provider. 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 9-4 SINAUT ST7cc Manual (05/2002)

187 ACRON Link 9.2 ACRON Project Settings with ST7cc Config In order for ST7cc together with ACRON to be able to generate files in CSV format, the following project settings have to be made in ST7cc Config: 1. Create a directory for saving generated CSV files with the Windows Explorer. You can also use the default directory "c:\siemens\st7cc\acron that is created automatically during the installation of ST7cc. 2. Activate the function "Write to CSV files. Here you can also select if you wish to write only the configured ACRON archive blocks or the entire message traffic in the CSV file. Only archive blocks with the archive name ACRON are written in the CSV file. The entire message traffic is written in the CSV file. Fig. 9-1 Activate the function "Write to CSV files SINAUT ST7cc Manual (05/2002) 9-5

188 ACRON Link 3. Enter the name of the directory you have created. All CSV files will be saved in this directory. 4. Set the restore cycle in seconds for the current CSV files. Fig. 9-2 Setting the ACRON directory and the restore cycle 6NH7998-7AA11 Siemens AG 2002 All Rights Reserved 9-6 SINAUT ST7cc Manual (05/2002)

189 ACRON Link 9.3 ACRON Project Settings with ST7cc Config Archiving Instructions for ACRON When an archive instruction refers to the archive name ACRON, the archiving is written to a file in CSV format instead of being performed through WinCC. No WinCC archive variable is created in the generation. The unit field of the archiving instruction can contain specification of interval duration in seconds. When the entry is >0, the value applies for a time period in seconds counting backwards from the time sent. When this entry is not present or is "0, ACRON assumes this is a single value. Fig. 9-3 Archiving Instructions for ACRON The preprocessing functions of ST7cc (raw value adjustment, interval-based compression) can be optionally used. It is recommended to precompress the process data for ACRON in order to reduce the system load for archiving. SINAUT ST7cc Manual (05/2002) 9-7