4 SINAUT ST7 Software 5 - Siemens AG · Preface 1 Configuration software for SINAUT ST7 2 SINAUT TD7 software package for the CPU 3 SINAUT Diagnostics and Service tool 4 SINAUT PG

Preface 1

Configuration software for SINAUT ST7

2SINAUT TD7 software package for the CPU

3SINAUT Diagnostics and Service tool

4

SINAUT PG Routing 5

SIMATIC NET

SINAUT ST7 Software

System Manual

05/2007 C79000-G8976-C222-06

Volume 2: Software

Safety Guidelines This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are graded according to the degree of danger.

DANGER indicates that death or severe personal injury will result if proper precautions are not taken.

WARNING indicates that death or severe personal injury may result if proper precautions are not taken.

CAUTION with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.

CAUTION without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.

NOTICE indicates that an unintended result or situation can occur if the corresponding information is not taken into account.

If more than one degree of danger is present, the warning notice representing the highest degree of danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage.

Qualified Personnel The device/system may only be set up and used in conjunction with this documentation. Commissioning and operation of a device/system may only be performed by qualified personnel. Within the context of the safety notes in this documentation qualified persons are defined as persons who are authorized to commission, ground and label devices, systems and circuits in accordance with established safety practices and standards.

Prescribed Usage Note the following:

WARNING This device may only be used for the applications described in the catalog or the technical description and only in connection with devices or components from other manufacturers which have been approved or recommended by Siemens. Correct, reliable operation of the product requires proper transport, storage, positioning and assembly as well as careful operation and maintenance.

Trademarks All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.

Disclaimer of Liability We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions.

Siemens AG Automation and Drives Postfach 48 48 90437 NÜRNBERG GERMANY

Ordernumber: C79000-G8976-C222 Ⓟ 05/2007

Copyright © Siemens AG 2007. Technical data subject to change

Software System Manual, 05/2007, C79000-G8976-C222-06 3

Table of contents 1 Preface ................................................................................................................................................. 15 2 Configuration software for SINAUT ST7 ................................................................................................ 17

2.1 Overview ......................................................................................................................................17 2.1.1 The SINAUT ST7 configuration software in the SIMATIC world .................................................17 2.1.2 Working with the SINAUT ST7 configuration tool ........................................................................18 2.1.3 Sequence of configuration of a telecontrol system......................................................................19 2.2 Creating a project in the SIMATIC Manager................................................................................20 2.3 Creating stations and networks in network configuration ............................................................21 2.3.1 The network and station catalog ..................................................................................................21 2.3.2 Creating networks and stations....................................................................................................22 2.3.3 Creating non-STEP 7 stations .....................................................................................................23 2.4 Configuring stations in hardware configuration............................................................................25 2.4.1 The module catalog .....................................................................................................................25 2.4.2 Installing racks and modules........................................................................................................26 2.4.3 Setting module parameters..........................................................................................................28 2.4.4 Setting TIM module parameters...................................................................................................28 2.5 Configuring networks in network configuration ............................................................................46 2.5.1 Generating network attachments .................................................................................................47 2.5.2 Setting parameters for MPI networks...........................................................................................49 2.5.3 Setting parameters for Industrial Ethernet the .............................................................................51 2.5.4 Setting parameters for SINAUT networks....................................................................................52 2.5.5 Setting parameters for MPI network nodes .................................................................................61 2.5.6 Setting parameters for Ethernet nodes........................................................................................63 2.5.7 Setting parameters for WAN network nodes ...............................................................................65 2.5.8 Plausibility check of the network configuration ............................................................................79 2.6 Configuring connections in the SINAUT Configuration Tool........................................................80 2.6.1 The SINAUT Configuration Tool ..................................................................................................80 2.6.2 Configuring SINAUT connections ................................................................................................82 2.6.3 Invalid Connections......................................................................................................................85 2.6.4 Recovering lost connections ........................................................................................................87 2.6.5 Printing connection lists ...............................................................................................................87 2.7 Subscriber administration in the SINAUT configuration tool........................................................88 2.7.1 Subscriber list...............................................................................................................................89 2.7.2 Parameters for individual subscribers..........................................................................................91 2.7.3 Printing subscriber lists ..............................................................................................................107 2.8 TD7onTIM software package.....................................................................................................108 2.8.1 Introduction ................................................................................................................................108 2.8.2 Basic functions and components of TD7onTIM .........................................................................108 2.8.3 Parameter assignment dialogs for TD7onTIM ...........................................................................110 2.8.4 Basic settings for TIM subscribers with TD7onTIM ...................................................................114 2.8.5 Subscriber-specific parameters of TD7onTIM ...........................................................................117 2.8.6 Configuring SINAUT objects ......................................................................................................120 2.8.7 Setting parameters for system objects ......................................................................................123

Table of contents

Software 4 System Manual, 05/2007, C79000-G8976-C222-06

2.8.8 Basic parameters of the data objects........................................................................................ 128 2.8.9 Channel overview and functions of channel parameter assignment ........................................ 133 2.8.10 Mandatory parameters of the send channels............................................................................ 135 2.8.11 Mandatory parameters of the receive channels........................................................................ 138 2.8.12 Specific channel parameters of the data objects ...................................................................... 139 2.8.13 Synchronization of the CPU time with TD7onTIM .................................................................... 150 2.9 Saving and generating system data.......................................................................................... 151 2.9.1 Saving subscriber data.............................................................................................................. 151 2.9.2 Generating system data blocks................................................................................................. 153 2.9.3 Compiling SINAUT TD7 blocks for the CPU............................................................................. 154 2.9.4 Creating SINAUT subscriber numbers as comments ............................................................... 156 2.10 SINAUT ST1 - Configuration Overview..................................................................................... 157 2.10.1 Differences between SINAUT ST1 and SINAUT ST7 .............................................................. 157 2.10.2 ST1 configuration rules ............................................................................................................. 157 2.10.3 Consistency check .................................................................................................................... 161 2.10.4 ST1 configuration overview....................................................................................................... 161 2.11 Change matrix ........................................................................................................................... 163 2.12 Version information ................................................................................................................... 165 2.13 Configuration practice ............................................................................................................... 166 2.13.1 Downloading data blocks to the CPU ....................................................................................... 166 2.13.2 Downloading system data blocks to the TIM ............................................................................ 166 2.13.3 Uploading stations with the Upload Station to PG function ...................................................... 167 2.13.4 Changing the MPI address of the CPU..................................................................................... 167 2.13.5 Copying projects in the SIMATIC Manager............................................................................... 167 2.13.6 Avoiding time stamp conflicts.................................................................................................... 168

3 SINAUT TD7 software package for the CPU ....................................................................................... 171 3.1 Overview ................................................................................................................................... 171 3.1.1 SINAUT TD7 Library ................................................................................................................. 174 3.1.2 Block overview .......................................................................................................................... 177 3.1.3 Changing SINAUT block numbers ............................................................................................ 181 3.1.4 Copying programs..................................................................................................................... 189 3.1.5 Using online help....................................................................................................................... 191 3.2 Principle of communication between SINAUT objects.............................................................. 194 3.3 Structure of the SINAUT user program..................................................................................... 201 3.3.1 SINAUT startup program in OB100 .......................................................................................... 201 3.3.2 Cyclic SINAUT program in OB1................................................................................................ 201 3.3.3 Time-driven SINAUT program in a cyclic interrupt OB ............................................................. 208 3.3.4 SINAUT test routine in the programming error OB121 ............................................................. 210 3.4 Basic blocks .............................................................................................................................. 211 3.4.1 FC Startup ................................................................................................................................. 211 3.4.2 FC BasicTask............................................................................................................................ 211 3.4.3 DB BasicData............................................................................................................................ 213 3.4.4 FB XCom................................................................................................................................... 214 3.4.5 DB XComData........................................................................................................................... 214 3.4.6 FB-PCom................................................................................................................................... 215 3.4.7 DB PComData........................................................................................................................... 215 3.4.8 FB BCom................................................................................................................................... 215 3.4.9 DB BComData........................................................................................................................... 215 3.4.10 FC Create.................................................................................................................................. 216 3.4.11 FC Distribute ............................................................................................................................. 216

Table of contents


3.4.12 FC Search ..................................................................................................................................216 3.4.13 FC Diagnose ..............................................................................................................................216 3.5 Data point typicals......................................................................................................................217 3.5.1 ST7 binary information typical FB Bin04B_S .............................................................................221 3.5.2 ST7 binary information typical FB Bin04B_R.............................................................................227 3.5.3 ST1 binary information typicals FB MTZ01 and FB MTZ02 ......................................................229 3.5.4 ST1 binary information typicals FB MTA01 and FB MTA02 ......................................................241 3.5.5 ST7 analog value typical FB Ana04W_S ...................................................................................245 3.5.6 ST7 analog value typical FB Ana04W_R...................................................................................256 3.5.7 ST1 analog value typicals FB ATZ01 and FB ATZ03................................................................259 3.5.8 ST1 analog value typicals FB ATA01 and FB ATA02................................................................272 3.5.9 ST7 counted value typicals FB Cnt01D_S and FB Cnt04D_S...................................................277 3.5.10 ST7 counted value typicals FB Cnt01D_R and FB Cnt04D_R ..................................................283 3.5.11 ST1 counted value typicals FB ZTZ01, FB ZTZ02 and FB ZTZ03 ............................................288 3.5.12 ST1 counted value typicals FB ZTA01, FB ZTA02 and FB ZTA03 ...........................................298 3.5.13 ST7 command typical FB Cmd01B_S........................................................................................305 3.5.14 ST7 command typical FB Cmd01B_R .......................................................................................308 3.5.15 ST1 command typical FB BTZ01...............................................................................................313 3.5.16 ST1 command typical FB BTA01...............................................................................................317 3.5.17 ST7 setpoint typical FB Set01W_S............................................................................................321 3.5.18 ST7 setpoint typical FB Set01W_R............................................................................................326 3.5.19 ST7 parameter typical FB Par12D_S.........................................................................................335 3.5.20 ST7 parameter typical FB Par12D_R.........................................................................................346 3.5.21 ST1 setpoint typical FB STZ01 ..................................................................................................357 3.5.22 ST1 setpoint typical FB STA01 ..................................................................................................364 3.5.23 ST7 data typical FB Dat12D_S ..................................................................................................368 3.5.24 ST7 data typical FB Dat12D_R..................................................................................................375 3.5.25 ST1 data typical FB STKOP26W...............................................................................................379 3.5.26 ST1 data typical FB ETKOP26W...............................................................................................389 3.6 Blocks for optional expansion ....................................................................................................395 3.6.1 FC ListGenerator300, FC ListGenerator400..............................................................................395 3.6.2 FC TimeTask..............................................................................................................................397 3.6.3 FC Trigger ..................................................................................................................................399 3.6.4 FC PulseCounter........................................................................................................................403 3.6.5 FC Safe ......................................................................................................................................405 3.6.6 FC PartnerStatus .......................................................................................................................408 3.6.7 FC PartnerMonitor......................................................................................................................409 3.6.8 FC ST7ObjectTest .....................................................................................................................414 3.6.9 FB SMS_Control ........................................................................................................................415 3.6.10 DB SMS_Data ............................................................................................................................421 3.7 Test blocks .................................................................................................................................426 3.7.1 FC TestCopy ..............................................................................................................................426 3.7.2 DB TestCopyData ......................................................................................................................428 3.8 SFC / SFB system blocks used .................................................................................................432

4 SINAUT Diagnostics and Service tool ................................................................................................. 435 4.1 Overview of the functions and operation of the SINAUT Diagnostics and Service tool ............435 4.1.1 Starting the program and types of access .................................................................................435 4.1.2 Access to SINAUT subscribers and working with the diagnostics dialogs ................................438 4.1.3 Functions of the Diagnostics and Service tool...........................................................................439 4.2 STEP 7 diagnostics....................................................................................................................441 4.2.1 CPU messages ..........................................................................................................................441 4.2.2 Module information ....................................................................................................................443

Table of contents


4.2.3 Operating mode ........................................................................................................................ 449 4.2.4 Setting the time ......................................................................................................................... 450 4.3 SINAUT diagnostics .................................................................................................................. 451 4.3.1 TIM Diagnostics ........................................................................................................................ 451 4.3.2 TIM diagnostics - IP Parameters tab......................................................................................... 460 4.3.3 TIM Diagnostics - Statistics tab................................................................................................. 461 4.3.4 TIM subscriber diagnostics ....................................................................................................... 461 4.3.5 TIM diagnostic messages ......................................................................................................... 466 4.3.6 TIM Message Monitor ............................................................................................................... 470 4.3.7 TD7 CPU Diagnostics ............................................................................................................... 472 4.3.8 TD7 Block Structure .................................................................................................................. 473 4.3.9 TD7 Block Structure for all CPUs.............................................................................................. 478 4.3.10 TD7 CPU Program Comparison ............................................................................................... 481 4.3.11 TD7 Check of the Communication Configuration ..................................................................... 483 4.3.12 TD7onTIM diagnostics .............................................................................................................. 485 4.3.13 SDB Viewer ............................................................................................................................... 488 4.4 Service functions....................................................................................................................... 497 4.4.1 Download SDB.......................................................................................................................... 497 4.4.2 Firmware update ....................................................................................................................... 498 4.4.3 Repair........................................................................................................................................ 500 4.5 Message protocol diagnostics................................................................................................... 502 4.5.1 Testcopy DB.............................................................................................................................. 503 4.5.2 ST7cc / ST7sc protocol ............................................................................................................. 504 4.5.3 TIM message protocol............................................................................................................... 505 4.5.4 Diagnostics of the TIM message protocol................................................................................. 505 4.6 Messages in the diagnostic buffer of the TIM ........................................................................... 514 4.6.1 Diagnostic messages of the TIM............................................................................................... 514 4.7 Messages in the diagnostic buffer of the CPU.......................................................................... 528 4.7.1 SINAUT diagnostic messages of TD7onCPU........................................................................... 528

5 SINAUT PG Routing ........................................................................................................................... 533 5.1 What is PG Routing?................................................................................................................. 533 5.1.1 Introduction................................................................................................................................ 533 5.1.2 Examples of configuration for PG routing ................................................................................. 534 5.1.3 Range of functions of PG routing.............................................................................................. 537 5.1.4 Properties and restrictions of PG routing .................................................................................. 538 5.2 System requirements for PG routing......................................................................................... 539 5.2.1 STEP 7 ...................................................................................................................................... 539 5.2.2 The SINAUT software package ................................................................................................ 540 5.2.3 RMOS operating system of the TIM 3 / TIM 4 .......................................................................... 540 5.2.4 TIM firmware for TIM 3 / TIM 4.................................................................................................. 541 5.2.5 Settings for SINAUT networks .................................................................................................. 541 5.2.6 Recompiling system blocks....................................................................................................... 541 5.2.7 Downloading newly compiled SDBs to TIM modules ............................................................... 541 5.2.8 Central SDB download using PG routing.................................................................................. 542 5.3 Application of PG routing .......................................................................................................... 546 5.3.1 Properties of the PG/PC interface............................................................................................. 546 5.3.2 PG/PC assignment in the SINAUT network.............................................................................. 547 5.3.3 PG routing in dial-up networks.................................................................................................. 549 5.3.4 Canceling the PG/PC attachment in the SINAUT network ....................................................... 550

Glossary ............................................................................................................................................. 551

Table of contents


Index................................................................................................................................................... 565

Tables

Table 2-1 Overview of the permitted WAN protocols with various modes...................................................56 Table 2-2 Symbols in the connection list of the connection configuration ...................................................83 Table 2-3 Overview of the Properties dialog tabs according to subscriber type..........................................91 Table 2-4 Symbols of SMS Configuration ..................................................................................................102 Table 2-5 Overview of the SINAUT objects for TD7onTIM ........................................................................121 Table 2-6 Format of the time information in the inputs of the I/O addresses of the TIM ...........................150 Table 2-7 Status bits of the time (low nibble of byte no. 8) ........................................................................151 Table 2-8 Basic blocks of TD7onCPU........................................................................................................155 Table 2-9 Change matrix............................................................................................................................163 Table 3-1 SINAUT TD7 Library: Block overview........................................................................................178 Table 3-2 SINAUT blocks that are always required ...................................................................................187 Table 3-3 Structure of 8-character typical names ......................................................................................217 Table 3-4 Overview of the available data point typicals.............................................................................218 Table 3-5 Conversion of ST7 to ST1 raw value format for unipolar and life-zero analog values ..............269 Table 3-6 Conversion of ST7 to ST1 raw value format for bipolar analog values .....................................269 Table 3-7 Conversion of ST1 to ST7 raw value format, unipolar and bipolar values ................................276 Table 3-8 Conversion of ST1 to ST7 raw value format, life-zero values ...................................................277 Table 3-9 Conversion of ST7 to ST1 raw value format for unipolar and life-zero setpoints ......................361 Table 3-10 Conversion of ST7 to ST1 raw value format for bipolar setpoints .............................................362 Table 3-11 Conversion from ST1 to ST7 raw value format..........................................................................367 Table 3-12 The exact assignment of the data words with data, time of day and time status: .....................398 Table 3-13 Assignment of the 4 time status bits: .........................................................................................398 Table 3-14 Structure of an SMS object in DB SMS_Data............................................................................422 Table 4-1 Overview of the diagnostic and service functions of the SINAUT Diagnostics and Service

tool .............................................................................................................................................440 Table 4-2 Symbols indicating subscriber availability in subscriber diagnostics .........................................462 Table 4-3 Diagnostic areas of the TIM 3 / TIM 4........................................................................................467 Table 4-4 Diagnostic areas of the Ethernet TIMs ......................................................................................468 Table 4-5 Significance of the comparison symbols for components in a CPU program comparison........481 Table 4-6 Significance of the comparison symbols for parameters in a CPU program comparison .........482 Table 4-7 Comparison symbol for components of the TD7 check of the communication configuration....483 Table 4-8 Comparison symbol for parameters of the TD7 check of the communication configuration .....484 Table 4-9 Example of the information of a WAN data SDB (type 3202) ....................................................490 Table 4-10 Example of the information of a subscriber data SDB (type 3203)............................................492

Table of contents


Table 4-11 Example of the information of a connection data SDB (type 3205) .......................................... 492 Table 4-12 Example of the information of a LAN connection SDB (type 3201) .......................................... 493 Table 4-13 Example of the information of a TD7onTIM data SDB (type 3206) .......................................... 493 Table 4-14 Example of the information of an Ethernet data SDB (type 3100)............................................ 495 Table 4-15 Example of the information of a routing data SDB (type 3002) ................................................ 496 Table 4-16 Example of the information of a connection data (PBC) SDB (type 700) ................................. 496 Table 4-17 Example of the information of a consistency SDB (type 3118)................................................. 496 Table 4-18 Global classification of the TIM diagnostic messages .............................................................. 515 Table 4-19 Diagnostic messages of the TIM............................................................................................... 515 Table 4-20 Classification of the group error messages of the TIM ............................................................. 527 Table 4-21 Global classification of the SINAUT diagnostic messages of TD7onCPU................................ 528 Table 4-22 SINAUT diagnostic messages of TD7onCPU........................................................................... 529 Table 5-1 Communication path of PG routing........................................................................................... 537 Table 5-2 Overview of routing-compliant communication paths ............................................................... 537 Table 5-3 Abbreviations/acronyms:........................................................................................................... 538 Table 5-4 Overview of the SDBs ............................................................................................................... 540

Figures

Figure 2-1 The SINAUT ST 7 configuration software within the overall system .......................................... 17 Figure 2-2 Sequence of configuration of a telecontrol system ..................................................................... 19 Figure 2-3 New project in the SIMATIC Manager in the Details view .......................................................... 20 Figure 2-4 Catalog for network configuration - NetPro................................................................................. 21 Figure 2-5 Project window for network configuration - NetPro..................................................................... 22 Figure 2-6 Creating interfaces or network nodes for ST1 stations............................................................... 24 Figure 2-7 The module catalog in the hardware configuration..................................................................... 26 Figure 2-8 The station window of hardware configuration with a SIMATIC 300 rack and various

modules....................................................................................................................................... 27 Figure 2-9 Properties - TIM dialog, General tab........................................................................................... 29 Figure 2-10 Properties - TIM dialog, Addresses tab....................................................................................... 30 Figure 2-11 Properties - TIM dialog, Special tab............................................................................................ 31 Figure 2-12 Properties - TIM dialog, Time Service tab................................................................................... 33 Figure 2-13 Example of time synchronization: Network section 1 - MPI / classic WAN ................................ 35 Figure 2-14 Example of time synchronization: Network section 2 - Ethernet................................................. 37 Figure 2-15 Properties - TIM dialog, Interfaces tab for an Ethernet TIM........................................................ 40 Figure 2-16 Properties - TIM dialog, WAN Access tab................................................................................... 43 Figure 2-17 Properties - TIM dialog, Options tab ........................................................................................... 44

Table of contents


Figure 2-18 Icon of a master TIM station in the project window of the network configuration containing a TIM module and 3 network nodes.............................................................................................47

Figure 2-19 Station with three network nodes, two of which are networked...................................................47 Figure 2-20 Networked sample project ...........................................................................................................48 Figure 2-21 Properties - MPI dialog, General tab............................................................................................49 Figure 2-22 Properties - MPI dialog, Network Settings tab .............................................................................50 Figure 2-23 Properties - Industrial Ethernet dialog, General tab.....................................................................51 Figure 2-24 Properties - SINAUT Dedicated Line dialog, General tab ...........................................................53 Figure 2-25 Properties - SINAUT Dedicated Line dialog, Network Settings tab .............................................54 Figure 2-26 Properties - SINAUT Dedicated Line dialog, Time Service tab ...................................................58 Figure 2-27 Properties - SINAUT Dedicated Line dialog, Node List tab .........................................................59 Figure 2-28 Properties - SINAUT Dedicated Line dialog, Time Slots tab .......................................................60 Figure 2-29 Properties - MPI interface dialog, General tab.............................................................................61 Figure 2-30 Properties - MPI interface dialog, Parameters tab.......................................................................62 Figure 2-31 Properties - Ethernet interface dialog, General tab .....................................................................63 Figure 2-32 Properties - Ethernet interface dialog, Parameters tab................................................................64 Figure 2-33 Properties - SINAUT Dedicated Line TIM dialog, General tab ....................................................66 Figure 2-34 Properties - SINAUT Dedicated Line TIM dialog, Network Connection tab ................................67 Figure 2-35 Properties - SINAUT Dedicated Line TIM dialog, Basic Param. tab............................................68 Figure 2-36 Properties - SINAUT Dedicated Line TIM dialog, Dedicated Line tab .........................................71 Figure 2-37 Main cycle - sub-cycle..................................................................................................................73 Figure 2-38 Properties - SINAUT Dedicated Line TIM dialog, Dial-up Network tab .......................................74 Figure 2-39 Properties - SINAUT Dedicated Line TIM dialog, Dialing Param. tab .........................................76 Figure 2-40 Properties - SINAUT Dedicated Line TIM dialog, AT Initialization...............................................78 Figure 2-41 Selection dialog of the SINAUT Configuration Tool.....................................................................81 Figure 2-42 Example of a SINAUT ST7 connection from the master station to station 1...............................82 Figure 2-43 The Connection Configuration window of the SINAUT Configuration Tool .................................83 Figure 2-44 Invalid Connections dialog ...........................................................................................................86 Figure 2-45 Windows of subscriber administration .........................................................................................89 Figure 2-46 Properties of subscriber dialog (CPU), Info tab ...........................................................................92 Figure 2-47 Properties of subscriber dialog (CPU), Connections tab .............................................................93 Figure 2-48 Properties - Local Connection dialog (TIM) .................................................................................94 Figure 2-49 Properties - Local Connection dialog (CPU)................................................................................95 Figure 2-50 Properties of subscriber dialog (TIM), Polling List tab .................................................................96 Figure 2-51 Properties- Poll list entry dialog ...................................................................................................97 Figure 2-52 Properties of subscriber dialog (TIM), Telephone Directory tab ..................................................98 Figure 2-53 Properties- Telephone Number dialog .........................................................................................99

Table of contents


Figure 2-54 Properties of subscriber dialog (CPU), DB Configuration tab................................................... 100 Figure 2-55 Properties of subscriber dialog (CPU), SMS Configuration tab ................................................ 101 Figure 2-56 SMS CPU configuration dialog.................................................................................................. 103 Figure 2-57 SMS DB data dialog.................................................................................................................. 104 Figure 2-58 SMS Message data dialog ........................................................................................................ 106 Figure 2-59 SINAUT ST7 subscriber administration with the TIMs with TD7onTIM directory selected,

the list box and the parameter assignment window of the basic settings for TIM with TD7onTIM ................................................................................................................................. 111

Figure 2-60 Selected data object Bin04B_R with selected channel in the list box and the parameter assignment window of a receive channel ................................................................................. 112

Figure 2-61 Parameter assignment dialog for basic settings for TIM subscribers with TD7onTIM.............. 114 Figure 2-62 Directory tree, list box, and parameter assignment dialog of the destination subscriber-

specific parameters of TD7onTIM for a destination subscriber ................................................ 118 Figure 2-63 Window of the standard library of SINAUT objects for TD7onTIM ........................................... 120 Figure 2-64 TIM with selected system object WatchDog and the corresponding parameter assignment

dialog......................................................................................................................................... 124 Figure 2-65 Parameter assignment dialog of the PartnerStatus system object ........................................... 125 Figure 2-66 Parameter assignment dialog of the OpInputMonitor system object ........................................ 127 Figure 2-67 Subscriber administration with the parameter assignment dialog of the basic parameters

of a data object.......................................................................................................................... 129 Figure 2-68 Selected object Bin04B_R with Binary receive channel selected in the list box and its

parameter assignment dialog.................................................................................................... 134 Figure 2-69 Parameter assignment dialog of a send channel based on the example of Counted value

send........................................................................................................................................... 135 Figure 2-70 Parameter assignment dialog of the Binary receive receive channel ....................................... 138 Figure 2-71 The Masks area in the parameter assignment dialog of the Binary send channel type ........... 140 Figure 2-72 Section of the parameter assignment dialog of the channel type Data send with the

Number parameter .................................................................................................................... 142 Figure 2-73 The Options dialog after selecting the Save function ............................................................... 152 Figure 2-74 Status dialog after saving and generating the system data ...................................................... 153 Figure 2-75 ST1 configuration rules: Connections ....................................................................................... 158 Figure 2-76 Excerpt of some of the ST1 configuration rules relating to subscribe number and WAN

address...................................................................................................................................... 160 Figure 2-77 Example of an error list after running the consistency check ................................................... 161 Figure 2-78 The SINAUT ST1 configuration overview ................................................................................. 162 Figure 2-79 SINAUT ST7 version information.............................................................................................. 165 Figure 2-80 Save project as dialog for copying objects................................................................................ 168 Figure 3-1 Basic and auxiliary blocks in the blocks program directory ...................................................... 173 Figure 3-2 TD7_UserSource im Programmverzeichnis Quellen ................................................................ 173 Figure 3-3 Opening the SINAUT library SINAUT TD7 Library ................................................................... 175

Table of contents


Figure 3-4 Components of the SINAUT TD7 library....................................................................................176 Figure 3-5 Source STL files Basic01_Source_de/_en in the SINAUT TD7 library ......................................176 Figure 3-6 Blocks of the SINAUT TD7 library in block format .....................................................................176 Figure 3-7 The symbol table Symbols in the SINAUT TD7 library ..............................................................177 Figure 3-8 Example of a project (SINAUT basic blocks already present) ...................................................182 Figure 3-9 Renaming blocks in the dialog ...................................................................................................183 Figure 3-10 Renaming with automatic symbol assignment...........................................................................183 Figure 3-11 Example of a project (still without user or SINAUT program) ....................................................185 Figure 3-12 Dialog for triggering compilation of the SINAUT TD7 blocks.....................................................186 Figure 3-13 Selecting the program of the source CPU .................................................................................190 Figure 3-14 Starting the online help from the SINAUT TD7 library ...............................................................191 Figure 3-15 Starting the online help from the block directory of the user program.......................................192 Figure 3-16 Starting online help while creating programs.............................................................................192 Figure 3-17 Example of a help text ...............................................................................................................193 Figure 3-18 Selecting help topics ..................................................................................................................194 Figure 3-19 The principle of object communication ......................................................................................195 Figure 3-20 Object communication over WAN..............................................................................................196 Figure 3-21 Object communication in the LAN (MPI)....................................................................................198 Figure 3-22 Object communication with several operator subscribers .........................................................199 Figure 3-23 Interaction of the blocks (based on the example of the process end) .......................................200 Figure 3-24 Changing the time interval for cyclic interrupt OB35..................................................................209 Figure 3-25 DB-BasicData, DW60 CurrentComDB Number of the current communication DB ...................213 Figure 3-26 Current communication DB, DW10 CurrentReceivedMessage, Pointer to the start of the

current received message in the receive buffer.........................................................................213 Figure 3-27 TIM parameter assignment tabs - setting the synchronization on the MPI / party line..............397 Figure 3-28 DB BasicData, CurrentDate and CurrentTime...........................................................................398 Figure 4-1 The Accessible Nodes dialog of a sample installation...............................................................436 Figure 4-2 The SINAUT subscriber list of a sample project ........................................................................437 Figure 4-3 CPU Messages dialog ...............................................................................................................442 Figure 4-4 Module Information dialog, Diagnostic Buffer tab ......................................................................445 Figure 4-5 Module Information dialog, IP Parameter tab ............................................................................447 Figure 4-6 Module Information dialog, Network Connection tab .................................................................448 Figure 4-7 Module Information dialog, Statistics tab ...................................................................................449 Figure 4-8 Set Time of Day dialog...............................................................................................................450 Figure 4-9 SINAUT Diagnostics dialog, Memory tab ..................................................................................452 Figure 4-10 TIM Diagnostics - Message buffer tab .......................................................................................453 Figure 4-11 SINAUT Diagnostics dialog, Communication tab ......................................................................456

Table of contents


Figure 4-12 SINAUT Diagnostics dialog, Time Synchronization tab............................................................ 457 Figure 4-13 SINAUT Diagnostics dialog, Time tab....................................................................................... 458 Figure 4-14 SINAUT Diagnostics dialog, Filesystem tab ............................................................................. 459 Figure 4-15 SINAUT Diagnostics dialog, IP Parameters tab........................................................................ 460 Figure 4-16 TIM Subscriber Diagnostics dialog, Status tab ......................................................................... 463 Figure 4-17 TIM Subscriber Diagnostics dialog, Partner tab........................................................................ 464 Figure 4-18 TIM Subscriber Diagnostics dialog, Dialing extern tab ............................................................. 465 Figure 4-19 TIM Subscriber Diagnostics dialog, Polling intern tab .............................................................. 466 Figure 4-20 TIM Extended Diagnostics dialog ............................................................................................. 468 Figure 4-21 TIM Message Monitor dialog..................................................................................................... 471 Figure 4-22 SINAUT Diagnostics dialog of the TD7 CPU Diagnostics function........................................... 473 Figure 4-23 SINAUT TD7 Block Structure dialog, Statistics tab................................................................... 475 Figure 4-24 SINAUT TD7 Block Structure dialog, Block tree tab................................................................. 476 Figure 4-25 SINAUT TD7 Block Structure dialog, Block list tab................................................................... 477 Figure 4-26 SINAUT TD7 Block Structure dialog, Plausibility tab................................................................ 478 Figure 4-27 CPU Program Compare Result dialog ...................................................................................... 482 Figure 4-28 CPU Program Compare Result dialog ...................................................................................... 484 Figure 4-29 TD7onTIM Diagnostics dialog with system object numbers based on the example

WatchDog.................................................................................................................................. 486 Figure 4-30 TD7onTIM Diagnostics dialog with channel parameters based on the example of the

Analog send channel................................................................................................................. 487 Figure 4-31 SDB Viewer dialog. In the example, SDB1000 - WAN data is selected. .................................. 489 Figure 4-32 Firmware Update dialog ............................................................................................................ 498 Figure 4-33 Update details dialog of the Firmware Update function ............................................................ 500 Figure 4-34 Open dialog of the Testcopy DB function ................................................................................. 503 Figure 4-35 The TIM Message Protocol dialog ............................................................................................ 506 Figure 4-36 Details dialog, Message Header tab ......................................................................................... 508 Figure 4-37 Details dialog, Net Data tab ...................................................................................................... 509 Figure 4-38 Details dialog, TIM Routing Infos tab ........................................................................................ 510 Figure 4-39 Details dialog, Hex tab .............................................................................................................. 511 Figure 4-40 Details dialog, Source/Destination/Time stamp tab .................................................................. 512 Figure 4-41 Statistics dialog, Subscriber tab................................................................................................ 513 Figure 5-1 Basic configuration of PG routing ............................................................................................. 534 Figure 5-2 PG routing from a SINAUT ST7cc control center with SIMATIC STEP 7................................. 535 Figure 5-3 Indirect PG routing over a remote PC / laptop with remote access.......................................... 536 Figure 5-4 Indirect PG routing over a remote PG/PC with SIMATIC STEP 7 ............................................ 536 Figure 5-5 Step 1 of central SDB download in the sample configuration................................................... 543

Table of contents


Figure 5-6 Step 2 of central SDB download in the sample configuration....................................................544 Figure 5-7 Step 3 of central SDB download in the sample configuration....................................................545 Figure 5-8 Step 4 of central SDB download in the sample configuration....................................................546 Figure 5-9 Properties dialog of the interface in the Control Panel ..............................................................547 Figure 5-10 Properties - PG/PG dialog / Assignment tab in NetPro .............................................................548 Figure 5-11 Project view in NetPro with assigned PG/PC ............................................................................549


Preface 1What's new in SINAUT ST7?

● New product "TIM 4R-IE" for connecting SINAUT over WAN and Ethernet ● New product version "SINAUT ST7 configuration software for the PG/PC" V4.1

Purpose of this documentation The SINAUT ST7 system manual is split into two complementary volumes. Volume 1: System & Hardware This documentation will support you on your way to successful application of SINAUT ST7. This introduces you to the topic in clear and straightforward steps and provides you with an overview of the hardware components of the SINAUT ST7 station control system. You will be supported during the planning of network structures and topologies and will see how to install and configure individual components based on the installation guidelines. You will also find this documentation useful when installing and commissioning the SINAUT modules. Volume 2: Software This documentation provides you with an overview of the software components of the SINAUT ST7 station control system. You will learn how to install and configure individual components and which diagnostic and service options are available.

Validity of the documentation This manual relates to the following software versions ● SINAUT ST7 configuration software for the PG/PC V4.1 ● SINAUT TD7 library for the CPU V2.2 ● SINAUT TIM firmware V4.3.7 for the TIM 3 / TIM 4 ● SINAUT TIM firmware V1.2 for the TIM 3V-IE variants ● SINAUT TIM firmware V1.0 for the TIM 4R-IE

SIMATIC Technical Support You can contact Technical Support for all A&D products ● Phone: +49 (0) 180 5050 222 ● Fax: +49 (0) 180 5050 223 You will find further information on our Technical Support on the Web at http://www.support.automation.siemens.com

http://www.support.automation.siemens.com

Preface


Service & Support on the Internet In addition to our documentation services, you can also make use of all our knowledge on the Internet: http://www.siemens.com/automation/service&support Here, you will find: ● Up-to-date product information (Updates), FAQs (Frequently Asked Questions),

Downloads, Tips and Tricks. ● The Newsletter keeps you constantly up to date with the latest information on the

products you use. ● The Knowledge Manager will find the documents you need. ● In the Forum, users and specialists exchange information and experience. ● You can find your local contact for Automation & Drives in our contacts database. ● You will find information on local service, repairs, spares and much more under the rubric

"Service". Do you still have questions relating to the use of the products described in the manual? If so, then please talk to your local Siemens contact. You will find the addresses in the following sources: ● On the Internet at: http://www.siemens.com/automation/partner ● On the Internet at http://www.siemens.com/simatic-net specifically for SIMATIC NET

products ● In the catalog CA 01 ● In the catalog IK PI specifically for SIMATIC NET products

SIMATIC training center To familiarize you with the systems and products, we offer a range of courses. Please contact your regional training center or the central training center in D-90327 Nuernberg. Phone: +49 (911) 895-3200 http://www.sitrain.com

SIMATIC NET training center For courses specifically on products from SIMATIC NET, please contact: SIEMENS AG Siemens AG, A&D Informations- und Trainings-Center Dynamostr. 4 D-68165 Mannheim Phone: +49 (621) 4 56-23 77 Fax: +49 (621) 4 56-32 68

http://www.siemens.com/automation/service&support

http://www.siemens.com/automation/partner

http://www.siemens.com/simatic-net

http://www.sitrain.com


Configuration software for SINAUT ST7 22.1 Overview

2.1.1 The SINAUT ST7 configuration software in the SIMATIC world The SINAUT ST 7 configuration software represents the user interface for parameter assignment of SINAUT telecontrol systems. With this software, the user can implement and set the parameters for the telecontrol components in a STEP 7 project. The following figure shows where the SINAUT ST7 configuration software fits into the overall system of the SIMATIC world. The areas with the "cloud" behind them are covered by the SINAUT ST 7 configuration software.

Figure 2-1 The SINAUT ST 7 configuration software within the overall system



The STEP 7 package provides the tools for configuring LANs. The SINAUT ST7 software also allows the configuration of ● SINAUT networks and WAN network nodes, ● SINAUT TIM modules and ● SINAUT connections. To help the user to become familiar with the SINAUT software as simply as possible, the SINAUT tools are always integrated wherever possible in the STEP 7 software. This applies in particular to the parameter assignment of the TIM modules, the SINAUT networks and WAN network nodes.

2.1.2 Working with the SINAUT ST7 configuration tool The SINAUT ST 7 configuration software fits into the familiar Windows sequences. This means that functions such as ● Window technology ● Menu bar ● Toolbar ● Online help for the dialogs of the configuration software ● Online help for the TD7 blocks ● Printing are integrated according to the Windows and STEP 7 standards. Working with the configuration tool is explained in the individual sections of the chapter.

General information on working with the tool You select a menu or a graphic object by clicking once with the left mouse button. Further functions for this object are then available over the menu bar, over the buttons of the toolbar or often over a context menu that opens when you select an object with the right mouse button. The buttons for the properties dialogs available for configuration have the following functions: ● OK: Confirms the entries made and closes the dialog. ● Cancel: Entries made are ignored and the dialog is closed.

The Cancel button is not available in the dialogs for subscriber administration in the SINAUT configuration tool. In this case, the dialog is closed without entering changes by clicking on the close button [x] in the right-hand top corner of the header line of the dialog.

● Help: Opens the online help.



2.1.3 Sequence of configuration of a telecontrol system The configuration of a SINAUT telecontrol system is demonstrated below step-by-step based on an example. The dialogs of the SINAUT configuration tool are also explained.

Figure 2-2 Sequence of configuration of a telecontrol system

When configuring a new SINAUT telecontrol system, the SINAUT configuration tool must be started after the network has been configured to allow configuration of the connections and then the data of the subscribers. Following each step, the configured data must be saved. Finally, the system data blocks for TIM and CPU modules and the SINAUT TD7 software blocks must be generated and then downloaded to the relevant modules.

Note The language for all STEP 7 applications including the configuration tools can be changed in the SIMATIC Manager in the Options / Customize / Language menu.

Generating system data after changing the configuration of an existing system Changes to an existing system made in the network configuration NetPro or in the hardware configuration HW Configare saved there. The new system data blocks, on the other hand, can be generated in various configuration tools.

Configuration software for SINAUT ST7 2.2 Creating a project in the SIMATIC Manager


In the following situations, after changes have been made to the project configuration, the SINAUT configuration tool should be started to generate the system data blocks (SDB) in the Subscriber Administration: ● After changing the configuration of a TIM module ● After changing the configuration of a configured connection to a SINAUT subscriber ● After changing SINAUT parameters of a PC station After changing or adding new subscribers or connections, the connection configuration and then the subscriber administration must be called in the SINAUT configuration tool to generate the SDBs there. The activities required following a configuration change are summarized in the change matrix in this section.

2.2 Creating a project in the SIMATIC Manager The first step in configuring a new installation is to create a new project in the STEP 7 SIMATIC Manager. This project serves as a directory for all the configuration data of the installation. You create the project in the SIMATIC Manager by selecting the File / New... menu and entering the name of the project. After creating the project, the SIMATIC Manager displays the following dialog:

Figure 2-3 New project in the SIMATIC Manager in the Details view

The newly generated project is empty except for one MPI network. During configuration, the project will be gradually filled with other stations and networks. Double-clicking on the MPI network opens the NetPro network configuration tool.

Configuration software for SINAUT ST7 2.3 Creating stations and networks in network configuration


2.3 Creating stations and networks in network configuration The STEP 7 NetPro tool is used for graphic configuration of network topologies. During network configuration, networks and stations are added to a new project, given parameter settings, and interconnected. The various network types and stations are available in the network and station catalog. The basic functions and possible settings are described in the STEP 7 documentation.

2.3.1 The network and station catalog The catalog for network configuration contains the following: ● PROFIBUS DP objects ● PROFIBUS PA objects ● PROFINET IO objects ● The possible station types ● The known network types including the SINAUT networks When you select an object, a brief description appears in the lower part of the catalog window. The following figure shows an example of the catalog window.

Figure 2-4 Catalog for network configuration - NetPro



2.3.2 Creating networks and stations There are two ways of creating networks and stations in the network configuration: ● Double-clicking on a catalog entry creates the required object at a free position in the

project area. ● Dragging a catalog entry to the project area places the object at the required position. The position of inserted objects can be changed at any time by dragging them with the mouse. The following figure shows a project after adding several stations and networks.

Figure 2-5 Project window for network configuration - NetPro

In this example, 4 stations, a dedicated line network and a dial-up network have been added to the existing MPI network. The stations are two telecontrol stations (Station 1 and Station 2) and a telecontrol center consisting of the S7-400 station Control Center and the S7-300 as rack for accommodating master TIMs (stand-alone). By selecting object with the right-hand mouse button, a context menu opens display in the available options for this object. The following functions are available for objects in the context menu: ● Open object (for stations only):

This starts HW Config for this station.



● Copy / Paste: Copies or pastes objects.

● Delete: Deletes the selected object after confirmation in a user prompt.

● Object properties: Opens the specific properties dialog for parameter assignment of the relevant object. Here, the name and comment for an object can be entered. As long as interfaces exist, they are displayed. With networks, network wide valid parameters are set here that are relevant to the continued configuration.

2.3.3 Creating non-STEP 7 stations

Creating non-STEP 7 stations SINAUT ST7 supports the configuration of different types of non-STEP 7 stations. These include SINAUT ST1 devices, a SINAUT ST7cc control center or an SMS center. As with the STEP 7 stations, they are created by double-clicking on the icon in the station catalog or by dragging them to the project window. The following objects must be selected for these subscribers: ● For a SINAUT ST7cc/ST7sc control center: SIMATIC PC station ● For a SINAUT ST1 device: SIMATIC S5 ● For an SMS center Other station

Note The non-STEP 7 stations listed above are used as placeholders in the network configuration.Hardware configuration of the non-STEP 7 stations of the type SINAUT ST1 device and SMS center is not possible since their content is unknown to STEP 7.

To attach created stations to the networks of the project, communication-compliant modules are first configured for the STEP 7 stations in HW Config so that the required interfaces can then be configured. With non-STEP 7 stations, the interfaces can be created immediately.

Creating the interfaces for non-STEP 7 stations ST1 subscriber: If you want to connect ST1 devices (stations, centers, node stations) to the configured network, they must be inserted as SIMATIC S5. For the ST1 stations, node stations, or master stations created as SIMATIC S5, the required interfaces for the networks to be connected are generated using the Object Properties context menu. In the Interfaces tab of the Properties - SIMATIC S5 dialog that then opens, you can insert a new interface with the New... button. The New Interface - Type Selection dialog opens.



Figure 2-6 Creating interfaces or network nodes for ST1 stations

If you intend to use the station as an ST1 subscriber, it must only contain SINAUT WAN network nodes. For example, an ST1 node station normally has two network nodes, one of the type node station and one of the type master for the underlying network. At the maximum configuration, and ST1 master can have up to 15 attachments; other words can have a maximum of 15 TIM modules installed. Configuring a network node as a station, node station, or master is explained along with the parameter settings for network nodes. You will find important information on configuring ST1 stations in the ST1 configuration rules. SMS center: An SMS center (SMSC) configured as an other station is configured in the Properties dialog available over the context menu with exactly 1 SINAUT dial-up network node. ST7cc / ST7sc control center: A SINAUT ST7cc or ST7sc control center configured as a SIMATIC PC station is equipped with the suitable communications module in hardware configuration and attached to the master TIM over the MPI network. The station is then recognized as a SINAUT control center PC. For detailed information on configuring a single or redundant ST7cc/ST7sc control center, refer to the SINAUT ST7cc or ST7sc documentation.

Configuration software for SINAUT ST7 2.4 Configuring stations in hardware configuration


2.4 Configuring stations in hardware configuration The hardware configuration program HW Config is used to install hardware components in stations. The HW Config program is opened by double-clicking on one of the station icons configured in the network configuration. The module catalog in the window on the right of HW Config contains the available objects. For SINAUT networks, these are: ● Racks ● Power supplies ● CPU modules ● SINAUT ST7 modules ● Other modules ● Applications for control centers in the SIMATIC PC station directory The devices are installed in the station from the module catalog. Possible slot restrictions are checked and reported immediately during configuration of the object. This makes an incorrect hardware configuration impossible. The installation rules include, for example: ● S7-300 + S7-400: Power supply permitted only in slot 1 ● S7-300: CPU permitted only in slot 2 ● S7-300: IM module permitted only in slot 3 ● S7-300: Function modules (CPs, I/O, FMs, TIMs) permitted in slots 4 - 11 ● S7-300: There must be no gaps between the modules inserted in slots 4 - 11 The installation rules for function modules are different in the expansion racks depending on the interface module (IM) with which the expansion rack is connected to the basic rack.

2.4.1 The module catalog The catalog of the hardware configuration contains hardware from the following system families: ● PROFIBUS DP ● SIMATIC 300 ● SIMATIC 400 ● SIMATIC PC-based Control 300/400 ● SIMATIC PC station The SIMATIC 300 / SINAUT ST7 directory contains the TIM modules of the SINAUT range.



Figure 2-7 The module catalog in the hardware configuration

If you select a catalog entry, a brief explanation of the object appears below the catalog.

2.4.2 Installing racks and modules The editing window of hardware configuration is in two parts. In the upper part of the window, you can see all the existing racks with the modules they contain. If you have a DP network, this is also visualized here. In the lower part of the window, you will see a precise listing of the modules used in the current rack along with the order number and the MPI or I/O addresses.



Figure 2-8 The station window of hardware configuration with a SIMATIC 300 rack and various

modules

Racks are either created by double-clicking on a rack entry in the catalog or by dragging the rack entry, for example a standard rail for S7-300, to the station. Since the system type SIMATIC 300 or SIMATIC 400 is already specified by the selection of the station, only suitable racks can be installed. Modules are installed in the rack in one of two alternative ways: ● Selecting a suitable slot in the station window and double-clicking are a catalog entry

or ● Dragging a catalog entry to the required slot in the station window In both cases, the system checks immediately whether the module is permitted in the slot. Modules can be moved to a new suitable slot at any time with the mouse. Once a station is complete and has all the required modules, it must be saved with the Station / Save menu. When you close hardware configuration, a dialog opens automatically prompting you to save your entries. When you save, the consistency of your entries is checked and a message output in the configuration errors are detected. With the Station / Print... menu, you can print out the configured data of the station.



2.4.3 Setting module parameters When you double-click on one of the modules installed in the rack in the hardware configuration, or when you select Object Properties in the context menu, the Properties dialog is opened allowing you to set parameters for a module. Here, users can adapt the properties of the particular object precisely to their requirements. The content of the Properties dialog depends on the module type. Only practical parameters for this type are displayed. Since each module has a set of default parameters, it is not absolutely necessary to set parameters at this point. The same Properties dialog can also be opened following hardware configuration in the network configuration phase.

Note At least all the TIM modules of the project should have parameters set using the Properties dialog, for example to create the interfaces. Setting parameters in the Properties dialog is possible both in hardware configuration or in network configuration.

2.4.4 Setting TIM module parameters The parameters for a TIM module are divided among various tabs of the Properties - TIM dialog. The following tabs are available: ● General

tab with general information and for modifying the module name or adding comments ● Addresses

tab with information on I/O address areas of the CPU ● Special

tab for setting parameters for an ST1 master in a dial-up network and for the diagnostic buffer

● Time Service tab for assigning parameters for time synchronization of a TIM module on the MPI bus or an Ethernet TIM (TIM 3V-IE variants, TIM 4R-IE) on Ethernet

● Interfaces tab for configuring the Ethernet and WAN interface(s) This tab exists only with Ethernet TIMs

● WAN Access tab for creating WAN interfaces of the TIM modules of type TIM 3/TIM 4

● Options tab with options for assigning parameters for the message memory and the message indicating a failed local subscriber to substations over a dial-up network

Note Communication-specific parameters are entered in the Properties dialogs for network and network node parameter assignment. These are explained in the relevant sections.



General tab The General tab informs you about the general properties of a TIM module.

Figure 2-9 Properties - TIM dialog, General tab

This tab contains the following output boxes and parameter assignment options: ● Short Designation: output area This displays the module type and a brief outline of the

hardware configuration. ● The Order No. output box displays the order number of the module. ● The Name: input box allows you to change the name of the module. ● As default, the Interface area shows the address and the networking status of the MPI

interface. With the Properties button, you can open a dialog for setting parameters of the MPI node of the module. This is described in detail in the section on network node parameter assignment. Modules of the type series TIM 3 are also assigned an MPI address as default, even if this does not physically exist. If you click the Properties button, the parameters of the MPI interface are not available for these modules in the next dialog.

● The Comment: input box allows you to enter comments, for example on the purpose of the module. The SINAUT subscriber number of the TIM module that can be generated as a comment in the Subscriber Administration of the SINAUT configuration software is then displayed in this comment box.



Addresses tab

Figure 2-10 Properties - TIM dialog, Addresses tab

The Addresses tab provides information on the address areas occupied by the TIM module in the I/O from the perspective of the CPU. These addresses are only relevant to you when the SINAUT program is configured on the TIM (TD7onTIM, possible with Ethernet TIMs) and when the CPU is supplied with the date and time by the TIM. In this case, the TIM supplies the time data to the inputs specified here. This is described in detail elsewhere (refer to the section: Synchronization of the CPU time with TD7onTIM . The start address and length of the address ranges are assigned by the system. As an alternative, you can change the inputs and outputs by disabling the system selection option and entering the start address in the input box manually. Since the addresses are always set consistently by the system and are not generally used, it is not normally necessary to make a change.

Special tab TheSpecial tab shows the SINAUT subscriber number of the TIM module and you can set the size and configuration of the diagnostic buffer. In ST1 dial-up networks, the SINAUT ST1 master number must be specified for the TIM modules.



Figure 2-11 Properties - TIM dialog, Special tab

This tab contains the following parameter assignment options: ● SINAUT subscriber number box:

The project-wide unique SINAUT subscriber number is displayed here. For more data of information, refer to the configuration of the subscriber administration in the SINAUT configuration tool.

● SINAUT ST1 master number box: This parameter is used only in conjunction with a master on a dial-up network with the ST1 protocol. The parameter is set on an ST1 network for the ST 7 stations and ST 7 masters. In an ST1 installation, the ST1 master number is in the range 1...8 and is unique for communication in the ST1 dial-up network. In the case of an ST1 subnet, the field interface of the node station counts as the ST1 master for the underlying ST1 network. If an ST7 master is connected to a dial-up network and uses the ST1 protocol, the master TIM connected to the dial-up network must be assigned the ST1 master number from the STEP 5 configuration. This ST1 master number must also be configured for all TIM modules of ST7 subscribers to this ST1 dial-up network. The ST1 drivers of the TIM modules then use this master number for addressing when communicating with the master. A WAN address configured in the WAN network nodes of the ST1 master is then no longer used by the TIM modules.



One special case is an ST1 master with several interfaces to one dial-up network: If an ST1 master (SIMATIC S5 station in NetPro) is attached to an ST1 dial-up network with several interfaces (TIM modules), it is given a different WAN address in the ST7 configuration. The master can only be addressed in networks with the ST1 protocol using a WAN address. In this case, the lowest WAN address of the dial-up network interfaces of the master must be assigned as the ST1 master number for all the ST7 TIM modules connected to this dial-up network. For more detailed information on configuring ST1 networks, refer to the ST1 configuration rules. Range of values: 1 ... 8 Default value: 1

● Diagnostics buffer size box: The diagnostics buffer is organized as a circulating buffer and can hold the specified number of messages. Range of values: 10 ... 100 Default value: 50

● Diagnostics level: The diagnostics messages required for normal operation are generated in the Operating mode. In Service mode, additional diagnostics messages are generated.

Time Service tab In the Time Service tab, you decide how the TIM will react to time synchronization on its interfaces: ● Time synchronization on the Ethernet interface(s) ● Time synchronization on the S7-300 backplane bus when the TIM is inserted in an

S7-300 ● Time synchronization on the MPI bus (with the TIM 4) Here, it is not possible to set the time synchronization of the network attachments to a SINAUT dedicated line or a SINAUT dial-up network (RS-232/RS-485 port on the TIM). You make these settings in the properties dialog of the relevant dedicated line or dial-up network (refer to the section: Setting parameters for SINAUT networks, Time Services tab). There is no setting per network node in this tab because the hierarchical distribution of the time is specified automatically during parameter assignment (master/node station/station). The figure below shows the tab for an Ethernet TIM (TIM 3V-IE variants and TIM 4R-IE).



Figure 2-12 Properties - TIM dialog, Time Service tab

The interfaces for which you can set parameters are listed in an overview box. If you click on one of the interfaces, the parameters for time synchronization appear below the box for the interface.

Note In the overview box of the TIM 4R-IE, the "S7-300 backplane bus" interface is always displayed. Parameters can, however, only be set for this interface if the TIM 4R-IE is inserted in an S7-300 as a CP.

With a TIM 3 or TIM 4 module without an Ethernet interface, the overview box is not displayed. Here, you can only set parameters for time synchronization on the MPI bus or S7-300 backplane bus. The same parameters are displayed as for an Ethernet TIM if the "S7-300 backplane bus" is selected there. If a TIM is inserted in an S7-300 as a CP, time synchronization on the "S7-300 backplane bus" specifies when the time synchronization of the local S7-300 CPU is performed. If other TIMs are inserted in the same S7 rack, these are also synchronized at the same intervals as set here. For a TIM 4 with MPI interface, the parameter settings for synchronization of the SINAUT nodes attached to the MPI bus apply (PCs, S7-300 and S7-400 CPUs and any other TIM 4 modules connected to the MPI bus).



The following rule applies if there are several TIMs in the S7-300 rack or several TIMs on the MPI bus: 1. Time synchronization must be enabled for all TIMs and set to the same time interval.

After startup, only one of the TIMs will actually behave as the time master. This is negotiated automatically by the TIMs. The TIM acting as time master synchronizes all the local SINAUT nodes known to it. The other TIMs act as slaves and allow themselves to be synchronized by the current master. If the TIM acting as master fails, one of the other TIMs automatically takes over the time master function until the failed master TIM is available again.

While the "time master" or "time slave" roles are negotiated automatically on the S7-300 backplane bus or MPI, with the Ethernet interfaces of the TIM, the role of master or slave must be specified explicitly. The following rules apply: 1. If the Ethernet port of the TIM is connected to an Ethernet on which there is also an

ST7cc or ST7sc PC, the PC in this network is always time master, in other words, the relevant Ethernet port of the TIM must be set to the "slave" function.

2. In an Ethernet network without ST7cc or ST7sc PC, the Ethernet port of one of the TIMs must be set to master and all others to slave. If the master function is set for more than one TIM on the Ethernet network, an error message is generated during the verification performed in the SINAUT node management.

3. Each Ethernet port to be synchronized by a master must be enabled as a slave. Otherwise synchronization is not accepted on this port. The setting of the synchronization interval or time of a slave should be identical to that of the master on the Ethernet network because the slave monitors whether or not the synchronization takes place at the specified intervals or at the specified time. Setting a shorter interval or a different time would lead to error messages in the diagnostic buffer of the TIM.

Note The error message is not generated at the precise moment when the interval has elapsed or the time has passed. If an interval is selected, the error message is generated after 2.5 times the selected interval has elapsed. Example: At an interval of 2 hours, the error message is entered only after 5 hours. If a specific time is selected, a tolerance of 2.5 hours is allowed before the error is signaled.

The following figure illustrates where and which time synchronization setting must be made based on an excerpt of a SINAUT project.



Example of time synchronization It is assumed that all SINAUT nodes in the network need to be synchronized.

Figure 2-13 Example of time synchronization: Network section 1 - MPI / classic WAN

● ST7cc No settings are necessary here.

● Master TIM 4R / master TIM 4RD Time synchronization on the MPI bus must be enabled for both TIMs. An interval of 1 minute is recommended.

Note ST7cc and ST7sc expect time synchronization on the MPI bus at intervals of 1 minute or less. Longer intervals cause error messages.

In this example, the "master TIM 4RD" takes over the master function after startup because it has a DCF77 receiver. Once this TIM has received a valid time of day, the ST7cc PC and the "master TIM 4R" are synchronized over MPI. If the TIM with a DCF77 receiver fails, the "master TIM 4R" can take over the master function.



Both TIMs synchronize the stations connected over a dedicated line or dial-up network by synchronizing the TIMs in the stations that, in turn, supply their own CPU. In these networks, you do not need to make settings for the TIMs. These TIMs obtain their parameters from the time parameter settings made centrally for the particular SINAUT network (dedicated line or dial-up network) refer to the section: Setting parameters for SINAUT networks, Time Services tab).

● Station1, TIM 32 Time synchronization on the S7-300 backplane bus must be enabled for this TIM; in other words, the TIM then supplies the S7-300 CPU with the current time over the backplane bus. An interval of 1 minute is recommended.

Note If a TIM synchronizes an S7-300 CPU over the backplane bus, no synchronization settings are necessary for the S7-300 CPU in HW Config. The SINAUT software on the CPU (TD7onCPU, FC TimeTask) handles the synchronization by using the synchronization message of the TIM to set the CPU clock.

● Station 2, TIM 3V-IE Here, there are two situations to be taken into account: – A SINAUT program (TD7onCPU) is running on the CPU:

You set the time synchronization on the S7-300 backplane for the TIM. – The SINAUT program is configured on the TIM 3V-IE (TD7onTIM):

You do not need to enable time synchronization on the TIM. Although there is no SINAUT program on the CPU, the CPU can nevertheless by supplied with the time of day when necessary. In this case, the TIM supplies the time data to its inputs. This is explained in detail elsewhere (refer to the section: Synchronization of the CPU time with TD7onTIM .

● TIM Station 3 This TIM handles the SINAUT communication for the S7-400 "Station 3". Here, you will need to enable time synchronization on the relevant Ethernet interface of the TIM as master. An interval of 1 minute is recommended.

● Station 3 No settings need to be made for the S7-400 CPU nor for the CP 443 in HW Config. The SINAUT software on the CPU (TD7onCPU, FC TimeTask) handles the synchronization by using the synchronization message of the TIM to set the CPU clock.



The next figure shows a further excerpt from the sample project which will be used to explain further details on synchronization, particularly in an Ethernet network.

Figure 2-14 Example of time synchronization: Network section 2 - Ethernet



● ST7cc No settings need to be made in an Ethernet network in which ST7cc (or ST7sc) is always time master.

● Station 10, TIM 3V-IE This TIM is connected directly to ST7cc, the time master, over Ethernet. You will therefore need to enable the Ethernet port of the TIM as slave for time synchronization. An interval of 1 minute is recommended. For the CPU in station 10, you may want to enable synchronization on the S7-300 backplane bus. Refer to the notes above in the section "Station 2, TIM 3V-IE".

Note If the station is connected to an Ethernet network for which fees are charged, for example via GPRS, it may be more economic to set an interval longer than 1 minute.

● Master TIM 4R-IE This TIM has two networked Ethernet accesses. Make the following settings. – On Ethernet(1):

There is an ST7cc computer (= time master) on this Ethernet network. Enabling the interface as time slave. An interval of 1 minute is recommended.

– On Ethernet(3): Enable the interface of the TIM as time master on this Ethernet network. Here, you can set an interval different from the interval for the slave interface on Ethernet(1).

Apart from synchronizing the stations connected to Ethernet(3), the TIM also supplies the stations in the dedicated line or dial-up network by synchronizing the TIMs in these stations that, in turn, supply their CPUs. In these networks, you do not need to make settings for the TIMs. These TIMs obtain their parameters from the time parameter settings made centrally for the particular SINAUT network (dedicated line or dial-up network) refer to the section: Setting parameters for SINAUT networks, Time Services tab).

● Station 11, TIM 3V-IE / station 12, TIM 3V-IE Advanced The TIMs in both stations are attached to Ethernet(3) in which the "master TIM 4R-IE" is enabled as time master. This means that you will need to enable both TIMs as time slaves. The interval should be identical to that on the time master on Ethernet(3). For the CPU in station 11 or 12, you may want to enable synchronization on the S7-300 backplane bus. Refer to the notes above in the section "Station 2, TIM 3V-IE".

● Station 13, two TIM 3V-IE Advanced modules This station functions as a node station. Each of the two TIMs has a network access to Ethernet that you enable as time slave for the TIM on Ethernet(3) and as time master on the other TIM on Ethernet(4). To allow the TIM connected to Ethernet(4) to adopt the role of time master, it must be synchronized by the TIM connected to Ethernet(3). The TIMs are synchronized over the S7-300 backplane bus. To allow this, you will need to enable time synchronization over the S7-300 backplane bus on both TIMs. The hierarchical structure of the time synchronization network is continued here. If necessary, you can set an interval for the master interface (right-hand TIM) that differs from the interval for the slave interface (left-hand TIM).



Parameter settings for time synchronization You can set the following options for the Synchronization cycle parameter: ● No synchronization:

There is no time synchronization on the relevant network. ● Hour scheme:

The number of hours between synchronization activities can be set in the "Hour scheme" drop-down list box. – Start time:

If the cycle for time synchronization is longer than 1 hour, you can set a start time for time synchronization in the "Start time" drop-down list box.

● Minute scheme: The number of minutes between synchronization activities can be set in the "Minute scheme" drop-down list box.

● Second scheme: The number of seconds between synchronization activities can be set in the "Second scheme" drop-down list box.

● Time of day: Synchronization takes place once a day. Set the time of day for the synchronization in the "Time of day" drop-down list box (for example 01:00)

● Synchronization master (only for Ethernet port) Here, you can decide whether the TIM module adopts the master role for time synchronization (setting "yes") or not (setting "no"). If "no" is set, the TIM is a time slave. You will find more information on setting the time master or slave in the explanations above.



Interfaces tab The Interfaces tab is available only for Ethernet TIMs. It displays a list of interfaces of the TIM module.

Figure 2-15 Properties - TIM dialog, Interfaces tab for an Ethernet TIM

If you click on an interface, the parameter boxes for the interface are displayed below the list: ● MPI

Ethernet TIMs do not have an MPI interface. If a TIM is inserted in an S7-300 as a CP, the list displays the "MPI" interface. If you select this by clicking on it with the mouse, you can configure the internal station MPI address of the TIM using the Properties button.

Note The MPI interface is displayed only when one of the following CPU types is inserted: • All variants of the CPUs 312, 312C, 313C, 314 and 314C • The CPUs 315-2 DP and 315F-2 DP

● WAN 1 / 2 The parameters of the WAN interfaces correspond to those of the TIM modules of the type TIM 3/TIM 4. You will find a description in the WAN access tab.

● Ethernet 1 / 2 The parameters of the Ethernet interface are displayed below the list.



In the list box for the Ethernet interface, "Ethernet 1" (or "Ethernet 2") is selected as default. You can change the parameter settings of the Ethernet interface with the Properties... button. This is described along with the configuration of the networks and network nodes.

Note The two Ethernet ports of a TIM 4R-IE are not designed as a switch, but are intended for connection to different networks. Operation in the same Ethernet network is not permitted. If this is ignored, it will not be possible to generate SDBs for the TIM. This is detected during the verification in SINAUT node management and signaled. The IP addresses of the two interfaces must therefore differ in at least one of the three leftmost decimal (separated by a period) numbers (applies to the usual subnet mask 255.255.255.0).

When an Ethernet interface is selected, you still have the option of setting the following parameters: ● Send Keepalives for Connections - Interval [s] (0-65535, 0 = off):

This value specifies the interval in seconds at which keepalives are sent. If the value is set to 0, no keepalive messages are sent. For GPRS connections, a value of 120 seconds is recommended. The value can also be selected here depending on the period in which the "conditional spontaneous" frames stored on the TIM must be sent (see parameter Send conditional messages as blocks). The keepalive interval should always be shorter than the interval for "dead peer detection" (DPD) on the MD740-1 modem. On the MD740-1, the default DPD interval is 150 seconds.

● Ethernet timeout for sending of messages [s] (0-255, 0 = default): This value specifies the monitoring time in seconds when sending messages (also applies to the sent keepalive messages). The acknowledgment of the message just sent must arrive within the monitoring time defined here. If the value is set to 0, the internal TIM default value is used (1 second). In GPRS networks, a message is usually acknowledged within 1 to 2 seconds. This may take longer depending on the load on the GPRS network. Experience has shown that an Ethernet timeout of 10 seconds is practical in GPRS networks.

● GPRS connection mode In contrast to a normal "flat" Ethernet network in which every connected subscriber can communicate with every other subscriber, there are only point-to-point connections between station and master in GPRS networks. Direct connections from station to station are not possible and must be routed via the master in GPRS networks. To allow this, an Ethernet TIM can be used in the master to handle the routing of data messages between stations. To be able to establish the correct route in the GPRS network during configuration of the SINAUT connections, you will need to assign one of the following options to the Ethernet interface of the TIM on the GPRS network: – No GPRS connection

No subscriber is connected over GPRS to the Ethernet interface of the TIM. – GPRS master

In the role of "GPRS master", the Ethernet interface represents the highest level in the GPRS network hierarchy. Messages from TIMs in the role of "GPRS station" or



"GPRS node station" to other stations in the network can then be routed over this interface.

– GPRS node station In the role of "GPRS node station", the Ethernet interface is subordinate to the "GPRS master". This setting is normally selected for a TIM located in a node station; in other words, in a station to which other stations are connected over a different network. Messages to be sent from this node station interface to other stations in the network are routed via the TIM with the interface role "GPRS master".

– GPRS station In the role of "GPRS station", the Ethernet interface is subordinate to the "GPRS master". Messages to be sent from this station interface to other stations in the network are routed via the TIM with the interface role "GPRS master". Send conditional messages as blocks:

● Send conditional messages as blocks Data transmission over a GPRS network is subject to fees depending on the amount of data transmitted. To minimize costs, smaller data packets can be collected and transferred in larger blocks if these messages are assigned the "conditional" priority; in other words, they do not need to be sent immediately (refer to the SINAUT-TD7 Software, section Basic parameters of the data objects (Page 128) or section Data point typicals (Page 217)). If the Send conditional messages as blocks option is enabled, the TIM transmits "conditional" messages in the following situations: – When the collected messages reach or exceed a size of 202 bytes. – If an important message needs to be transmitted immediately, "conditional

spontaneous" messages already in memory are transmitted along with it. – If the collected messages have not reached a size of 202 bytes, but the TCP/IP

keepalive interval has elapsed, the stored messages are sent instead of the keepalive

WAN Access tab In the WAN Access tab, you can configure the following WAN interfaces of the TIM modules of types TIM 3 and TIM 4: The parameters correspond to the WAN parameters of the Interfaces tab for the Ethernet TIMs: ● The internal interface that is normally assigned to a modem installed on the module. ● The external interface that must be set up by the user by selecting the required network

type and clicking on the New... button. Behind each interface that is to be connected with a network, there must be a network node of the corresponding type and this can be recognized by the Properties button being available for selection.



Figure 2-16 Properties - TIM dialog, WAN Access tab

For each of the two WAN accesses, you can make the following entries depending on the display in the internal/external WAN interface: ● Interface list box disabled with Dedicated line, spontaneous network or dial-up network:

There is already a network node for this interface. Using the Properties... button, you can branch to the Properties dialog of the network node to make parameter settings. With the Delete... button, you can remove the network node. The Properties dialog of the interface is written when you set parameters for the network node.

● Interface list box selectable when dedicated line, spontaneous network or dial-up network is displayed: There is not yet a network node for this interface. To create a network node, you must select the corresponding interface type in the Internal/external WAN interface list box. With the New... button, you create a network node of the type displayed in the interface list box.

● Interface list box disabled with the display Not available: This interface cannot be operated by the current TIM module, no further parameter assignment possible.

The type of connector modem is displayed for each interface Modem type If a modem exists on the TIM module or can be connected externally. This type cannot be changed for the internal interface. The type of a modem on the external interface must be configured over the list box.



The modem type is checked during the plausibility checks to establish whether or not it is compatible with the current network parameters. In addition to this, a default AT string for a SINAUT dial-up modem or GSM module is derived from the mode type and the network parameters Baud rate, Message format and Connection type (duplex, half duplex).

Options tab In the Options tab, you can set parameters for the message memory.

Figure 2-17 Properties - TIM dialog, Options tab

The following parameters can be set in the Global message memory area: ● Size:

This is the size of the memory in which the messages to be transmitted are stored for all configured WAN drivers. If the value 0 is entered here, the entire free memory following startup is used. Range of values: 0 ... 1024 Kbytes Default: 0

● Size of memory block: This is the size of the blocks into which the global message memory is segmented. Each message to be transmitted occupies at least this space in memory. The size should be matched up with the size of the messages most commonly transmitted. If the size is set too small, longer messages must be distributed over several blocks. If the



size is set too large, memory space is wasted with many of the messages. Range of values: 48 ... 65535 bytes Default: 64

● RAM drive: In this input box, you set the size of the RAM drive. The RAM drive is a restricted area in the main memory of the TIM module that can be created for special test purposes. The memory cannot be used for normal operation and is deleted again when the TIM module is restarted. On the TIM 3V-IE, the RAM drive is already set up at 100 Kbytes, the value 0 is displayed here and cannot be modified. On the TIM 3V-IE Advanced and the TIM 4R-IE, the RAM drive (100 Kbytes) can be modified. Range of values: 0 .. 1024 Kbytes Default: 0

In the Replace module without PG box, you can enable the following option for the Ethernet TIMs: ● Save configuration data on the CPU: (Ethernet TIMs only):

If you enable this option, the system data blocks (SDBs) of the TIM module are stored on the CPU. If the TIM module fails, the defective TIM can be replaced by a TIM of the same type without leading to download the SDBs to the TIM using a PG. The TIM module obtains its SDBs from its local CPU during startup. If the TIM is configured as a standalone TIM without a CPU in the rack, this function is not available.

Note If there is no C-PLUG inserted in a TIM 4R-IE, the configuration data is stored in flash memory. If there is a C-PLUG inserted in the TIM 4R-IE, the configuration data is stored automatically on the C-PLUG when it is downloaded. If you replace the module, you can insert the C-PLUG with the configuration data in the new module.

In the Local Subscribers box, you can enable the following option for the TIM 4R-IE: ● Send information about disrupted local subscribers vial dial-up networks:

If this option is enabled, the TIM signals the failure of local subscribers over connected dial-up networks to the substations. To reduce costs resulting from the automatic connection establishment in dial-up networks when subscribers drop out, this option can be disabled.

Saving and consistency check Once you have completed the parameter assignment in the hardware configuration, the current version must be saved with the Station / Save menu. You can generate system data blocks (SDBs) using the Save and compile menu later since there are still other configuration steps necessary before the SDBs can be generated completely. When you close hardware configuration, a dialog opens automatically prompting you to save your entries. When you select the Save and compile... function, a consistency check is run and a message is displayed if configuration errors are detected.

Configuration software for SINAUT ST7 2.5 Configuring networks in network configuration


Note To be able to acquire all the configured parameters for the TD7 software following changes in the hardware configuration of existing SINAUT installations when the system data is generated, the SINAUT configuration tool must first be started with connection configuration and then with subscriber administration. The project should be saved there, and the SDBs should be generated exclusively in subscriber administration.

Printing module information The information on all configured modules in the current rack or for a selected module can be printed out using the Station / Print... menu.

2.5 Configuring networks in network configuration For the following configuration steps, ● Configuring SINAUT connections ● Configuring SINAUT subscriber data ● Configuring SINAUT objects of an Ethernet TIM ● Generating system data blocks (SDBs) and data blocks (DBs) a fully configured network is required. During the initial network configuration, the following tasks are performed: ● The modules with network capability are connected to the networks ● A graphic view of the network consisting of one or more subnets is created ● The required properties and parameters for each subnet and each networked module are

specified ● The network configuration is documented

Starting the parameter assignment dialogs for networks and network nodes If you double-click on a network or network node icon or select the Object Properties menu in the context menu (right-hand mouse button), the Properties dialog opens to allow you to set parameters. Here, you can connect modules with networking capability with the networks and adapt the properties of the relevant object to your requirements. All parameters have default settings that simplify parameter assignment. First the network attachments are made.



2.5.1 Generating network attachments To network a project, the communication-compliant modules (for example CPU or TIM) must be connected to suitable networks. The modules in the station icons in the project window of the network configuration include interface and network node icons displayed in different colors according to the network type.

Figure 2-18 Icon of a master TIM station in the project window of the network configuration

containing a TIM module and 3 network nodes.

The station icon shows a master to containing a communication-compliant TIM 44D module. This module has three network nodes, visible as small squares in the module icon. If these network nodes are not connected to a network as in the example, the relevant network node is not networked. You connect network nodes with the networks using the mouse by dragging the network node icons to the line of the required network.

Figure 2-19 Station with three network nodes, two of which are networked

As an alternative you can attach to a network in the Properties dialog of the module available with the context menu (right-hand mouse button) and selecting the Object Properties... menu. The dialog is described in the section dealing with parameter assignment of network nodes. With the simpler technique of dragging network node icons to the network line, only suitable partners can be networked; in other words an MPI node can only be connected to an MPI network. This makes incorrect attachment impossible.



Figure 2-20 Networked sample project

The following network attachments were made in the sample project: ● The control center with the CPU 412 was connected to the MPI network ● The ST7cc control center created as a PC station was connected to the MPI network ● The master TIM 44D was connected to the MPI network, dedicated line 1 and the dial-up

network ● The TIM 32 of station 1 was connected to dedicated line 1 ● The TIM 42D of the node station was connected to dedicated line 1 and dedicated line 2 ● The TIM 34 of station 2 was connected to the entire network ● The TIM 32 of station 3 was connected to dedicated line 2 The blue WAN connections of the master TIM and the connection of the node station to dedicated line 2 are shown in dark blue and indicate a connection in which the connected interface for the relevant subnet was configured as a control center. This is explained in the description of the network node parameter assignment.



Note After changing connections, even if these are re-established again later, the SINAUT configuration tool with the connection configuration and thesubscriber administration must be called.

Printing network information The project can be printed and documented as a graphic or as text using the Network / Print menu.

2.5.2 Setting parameters for MPI networks To set parameters for MPI networks, you open the Properties - MPI dialog by double-clicking on the MPI network, or using the Object Properties... context menu.

General tab

Figure 2-21 Properties - MPI dialog, General tab

The following parameters are available in this tab: ● Name:

The default entry in the Name input box is the default name of the network. You can



change this to suit your purposes. A new, modified name appears in the SIMATIC Manager and in the network configuration.

● S7 subnet ID: The subnet ID is made up of two numbers separated by a dash: – The number for the project – The number for the subnet If you want to go online with a PG without a consistent project, you must know the subnet ID. The subnet ID is also printed out when you print the network configuration.

● The Project path is displayed. ● The Storage location of the project is displayed. ● In the Author input box, you can enter the person who created the configuration. ● The Date created is displayed. ● The Date of the last modification is displayed. ● In the Comment input box, you can enter comments of up to 254 characters.

Network Settings tab

Figure 2-22 Properties - MPI dialog, Network Settings tab

The following parameters are available: ● The Highest MPI address is displayed.

This is used to optimize the MPI network. It is advisable to retain the highest MPI address proposed by STEP 7.



● The Change option: By activating the option, you can modify the highest MPI address.

● Transmission rate: The setting of the transmission rate of the MPI network depends on the properties of the MPI subscribers used and must not be higher than the slowest subscriber. The default can normally be accepted.

2.5.3 Setting parameters for Industrial Ethernet the

General tab You set the parameters for Industrial Ethernet in the Properties - Industrial Ethernet dialog.

Figure 2-23 Properties - Industrial Ethernet dialog, General tab


The default entry in the Name input box is the default name of the network. You can change this to suit your purposes. A new, modified name appears in the SIMATIC Manager and in the network configuration.

● S7 subnet ID: The subnet ID is made up of two numbers separated by a dash: – The number for the project



– The number for the subnet If you want to go online with a PG without a consistent project, you must know the subnet ID. The subnet ID is also printed out when you print the network configuration.


2.5.4 Setting parameters for SINAUT networks You set parameters for SINAUT networks (WANs) in the Properties - SINAUT Dedicated Line or in the Properties - SINAUT Dial-up Network dialog. The parameters to be set in the following tabs always apply to the entire network and are identical for all attached network nodes or communication partners: ● General

tab with general information and for modifying the module name or adding comments ● Network settings

for setting the communication parameters of the current SINAUT network ● Time Service

tab for setting parameters for time synchronization on the SINAUT network ● Node List

tab with the list of all subscribers on the current SINAUT network ● Time Slots tab (only for the corresponding polling mode)

to specify the time slots for polling



General tab

Figure 2-24 Properties - SINAUT Dedicated Line dialog, General tab


The default entry in the Name input box is the default name of the network. You can change this to suit your purposes. A new, modified name appears in the SIMATIC Manager and in the network configuration.

● S7 subnet ID: The S7 subnet ID is made up of two numbers, one for the project and one for the subnet separated by a dash. If you want to go online with a PG without a consistent project, you must know the subnet ID. The subnet ID is also printed out when you print the network configuration.




Network Settings tab The Network Settings tab specifies the basic communication parameters for the current network.

Figure 2-25 Properties - SINAUT Dedicated Line dialog, Network Settings tab

The following parameters are available: ● The Operating mode list box in the Mode area with the options:

– Polling (dedicated lines only): In polling mode that is used with dedicated lines, the data exchange is is controlled by the master TIM. This polls the connected stations and node stations one after the other. Stations with data to transmit send it as soon as they are polled. Stations that do not currently have any data acknowledge the poll. Only data to be sent from the master TIM to the stations can be transferred at any time between two individual polls.

– Polling with time slots (dedicated lines only): This mode differs from the polling mode because time slots are defined in which the polls take place. Each minute is divided into a selectable number of time slots. When using external wireless networks, the number of time slots per minute is generally prescribed by the relevant regulatory bodies. You configure the time slots to be used in the Time Slots tab.

– Multi-master polling with time slots (dedicated lines are only): In this mode, the polls originate from several masters, once again in time slots. Here, various masters can be assigned different time slots for their polling. Multi-master polling with time slots is available only for ST7 networks with the FT2 message format with long acknowledgment. You configure the time slots in the Time Slots tab.



– Spontaneous (dial-up networks only): Spontaneous mode is intended for data exchange in the public telephone network, the ISDN network, or the GSM network. Only the TIM with an important data change transfers its data spontaneously and waits for an acknowledgment from the partner. Prior to the actual data transfer, the TIM must first establish a dial-up connection to the partner. Following successful transmission of the data, the TIM waits for the acknowledgment. Following this, the dial-up connection is terminated immediately again if the partner does not use the existing connection to transfer any existing data.

In the Message parameters area, you can set the following parameters: ● Message format:

The message format corresponds to IEC 870-5-1. The selection FT1.2 or FT2 depends on the modem. The standard modems MD2 - MD4 can handle both message formats, the GSM modules M20, TC35 and MC45 only FT2. Default: FT1.2 – FT1.2 (8E1):

Character format 8 data bits, even parity, 1 start bit, 1 stop bit Modem setting: Data format 11 bits

– FT2 (8N1): Character format 8 data bits, no parity, 1 start bit, 1 stop bit Modem setting: Data format 10 bits

Note For more detailed information on setting the message format, refer to the section on installing and putting a SINAUT modem into operation in the description of the displays and the connectors accessible from above.

● Acknowledgment: The type of an acknowledgment does not depend on the modem used. It is set dependent on the quality of the transmission line. Default: short acknowl. – short acknowl.:

consists of one byte. – long acknowl.:

consists of 5 bytes. The long acknowledgment is advisable in applications when interference produces spurious characters on the transmission line that could be interpreted by the TIM as a short acknowledgment. example: Bad wireless link

● WAN protocol: The WAN protocol is configured for the specific network. Default: ST7 – ST7:

The ST7 protocol is used as the WAN protocol. They should be the setting in all purely ST7 networks of an ST7 installation.

– ST1: The ST1 protocol is used as the WAN protocol. This is required for communication in networks with old ST1 installations and in networks in which both ST7 subscribers and ST1 subscribers are connected.



In a SINAUT dedicated line and dial-up network, either the ST1 or the ST7 protocol can be used. The selected network protocol applies to all subscribers attached to the relevant network or subnet. Restrictions for the mixed use of ST1 and ST7 protocols in one project are explained in the section Invalid connections. The following combinations of WAN protocol and mode with the dependent frame format are permitted:

Table 2-1 Overview of the permitted WAN protocols with various modes

Network type Mode WAN protocol Asynchronous characters

Message format

Dedicated line / wireless network

Polling ST1 11 bits FT1.2


Polling ST7 11 or 10 bits FT1.2 or FT2


Polling with time slots ST1 11 bits FT1.2


Polling with time slots ST7 11 or 10 bits FT1.2 or FT2


Multi-master polling with time slots

ST7 10 bits FT2

Dial-up network Spontaneous ST1 11 or 10 bits FT1.2 or FT2 Dial-up network Spontaneous ST7 11 or 10 bits FT1.2 or FT2

● Retry factor:

This value decides how often a message that has not been acknowledged positively is repeated. Range of values 0 .. 15 Default value in dedicated lines and in the spontaneous network: 3 Default in dial-up network: 7

● Max. message length (in bytes): The maximum message length is based on the longest ST7/ST1 message length within a network. Time values (for example sender retry time) for internal monitoring functions are derived from this information. Range of values: 40 .. 240 Default: 240

Note The default of 240 for the maximum message length should, whenever possible, not be changed since PG routing will not work with a maximum message length less than 240.

● Connection type:

Range of values: Half duplex, duplex Default: Duplex

● Baud rate: This is the speed at which the TIM and modem communicate. The transmission rate in



the current network is decided by the modem and is normally identical to that of the modem. If you want to operate the modem at a speed that is not one of the default speeds, set the next higher speed here (for example 19200 bauds with the modem operating and 14400 bauds). – Range of values on dedicated lines and in the spontaneous network:

50, 100, 150, 200, 300, 600, 1200, 2400, 4800, 9600, 19200, 38400 bauds – Range of values in the dial-up network:

1200, 2400, 4800, 9600, 19200, 38400 bauds – Default: 1200 bauds

● Cancel parameter (with dial-up networks only): This is the number of attempted dialing attempts until the attempt is finally aborted. Range of values: 0 ... 127 Default: 0 – Cancel parameter = 0:

The call attempts are finally aborted when a connection was established 127 times in a row but no data could be transferred.

– Cancel parameter = 1 ... 127: The call attempts are finally aborted when a connection was unsuccessful n times in a row, regardless of whether a connection could be established at all or whether data could not be transferred on an established connection.

● Redialing attempts (with dial-up networks only): This is the number of attempted calls until until a disruption is reported. Range of values: 1 ... 127 Default: 3

● Customer identification (with dial-up networks only): The customer identification is used to specify whether connections can only be established to partners permitted for the network. The customer identification has the function of password protection in the relevant network. Range of values: 0 ... 65535 Default: 0

Note With the SINAUT ST1 protocol, the customer identification is displayed in hexadecimal code. Here, a customer identification higher than 0 must be entered even if the partner station works without customer identification. When expanding older installations, the hexadecimal code for the customer identification of the ST1 subscriber must be converted to decimal code and entered.

Time Service tab The Time Service tab specifies the extent to which time synchronization services will be executed by the master or in the case of a subnet by the node station in this network. Time synchronization for TIM modules is described in the tab of the same name in the properties dialog of the TIM (refer to the section "Setting TIM module parameters").



Figure 2-26 Properties - SINAUT Dedicated Line dialog, Time Service tab

You can set the following options for the Synchronization cycle parameter: ● No synchronization:

There is no time synchronization on the relevant network. ● Hour scheme:

The number of hours between synchronization activities can be set in the "Hour scheme" drop-down list box. – Start time:

If the cycle for time synchronization is longer than 1 hour, you can set a start time for time synchronization in the "Start time" drop-down list box.

● Minute scheme: The number of minutes between synchronization activities can be set in the "Minute scheme" drop-down list box.

● Second scheme: The number of seconds between synchronization activities can be set in the "Second scheme" drop-down list box.

● Time of day: Synchronization takes place once a day. Set the time of day for the synchronization in the "Time of day" drop-down list box (for example 01:00)

On dedicated lines, a synchronization cycle of 1 hour is recommended and in dial-up networks, once a day, for example at 01:00 a.m. In dial-up networks, time synchronization can also be used to check the availability of a subscriber and to fetch data.



Which TIM is synchronization master on this WAN is decided automatically based on the configuration of the network attachments in the properties dialog of the network node.

Node List tab The node list displays all the communication subscribers connected to the current network; in other words, TIM modules. It also lists the station name, the WAN address and the configured node type making it easy to check these parameters throughout the network.

Figure 2-27 Properties - SINAUT Dedicated Line dialog, Node List tab

Note If there is an asterisk after one or two addresses, the WAN address is not unique and must be changed.

Time Slots - Only in networks with a suitable polling mechanism In the Time Slots tab, you can specify which time slots are used for transmission in the Polling with time slots and Multi-master polling with time slots modes. To allow communication, at least one time slot must be selected since the master can only poll within the selected time range.



Figure 2-28 Properties - SINAUT Dedicated Line dialog, Time Slots tab

When setting the parameters for time slots, follow the steps below: 1. Specify the No. of time slots per minute. The Length of one time slot is calculated from

this. 2. In the Master stations list, in the Stat. Addr. column, select the station address of the

master station of the subnet. 3. In the Time slots list, in the sec to sec column, select the required time slot for calling this

master station. 4. Click the assign station # to slots to assign the selected time slot to the selected master

station. Repeat this procedure if you want to use more than one time slot per minute. In the multi-master polling with time slots mode, this must be done for each of the polling masters with different time slots. You can delete a selected time slot again with the remove assignment button.



2.5.5 Setting parameters for MPI network nodes

General tab The General tab informs you about general parameters of the MPI interface.

Figure 2-29 Properties - MPI interface dialog, General tab

The following parameters are available: ● Name:

The Name box displays the name of the module in SIMATIC stations. You can only change the default interface name in SIMATIC PC stations and other stations. A new, modified name appears in the SIMATIC Manager and in the network configuration.




Parameters tab

Figure 2-30 Properties - MPI interface dialog, Parameters tab

The Parameters tab provides the following parameters: ● The network address in the local MPI network.

The address of the network node can be modified. There is a consistency check which blocks network addresses that have already been assigned.

● The highest MPI address in the network is displayed. ● The transmission rate:

Just like the highest MPI address, this cannot be modified here but only in the parameter assignment of the MPI network.

● The Subnet: This lists all the networks of this type in the project. If the subscriber is not connected, the row ----not networked---- is shown as selected in the Subnet list. – If the current subscriber is connected, the row of the relevant network is shown as

selected. You can set parameters for the current network with the Properties button. – If no connection exists, a network connection can be set up using the New button. – An existing connection can be deleted with the Delete button.



2.5.6 Setting parameters for Ethernet nodes This type of interface is available among the SINAUT subscribers only for the Ethernet TIMs.

General tab

Figure 2-31 Properties - Ethernet interface dialog, General tab

The General tab informs you about general parameters of the Ethernet interface. ● Name:

The Name box displays the name of the module. ● The Project path is displayed. ● The Storage location of the project is displayed. ● In the Author input box, you can enter the person who created the configuration. ● The Date created is displayed. ● The Date of the last modification is displayed. ● In the Comment input box, you can enter comments of up to 254 characters.



Parameters tab

Figure 2-32 Properties - Ethernet interface dialog, Parameters tab

The Parameters tab provides the following parameters: ● Set MAC address / use ISO protocol:

Since an Ethernet TIM does not use the ISO protocol but TCP/IP, this option remains disabled.

● The IP address: This cannot be changed here.

● The Subnet mask: This has the default value 255.255.0.0 and cannot be changed, in other words restricted here.

● In the Gateway box, you have the option of specifying whether data transmission is over a router. If a router exists, the IP address of the router is entered in the Address box.





2.5.7 Setting parameters for WAN network nodes You set parameters for SINAUT WAN networks in the Properties - SINAUT Dedicated Line or in the Properties - SINAUT Dial-up Network dialog in the following tabs; ● General

tab with general information on the network node and entry of comments ● Network Connection

tab for setting the most important network properties ● Basic Param.

tab for setting the basic communication parameters ● Dedicated Line

tab with parameters specifically for dedicated lines ● Dial-up Network

tab with parameters specifically for dial-up networks ● Call Parameters

tab with parameters specifically for call numbers ● AT Initialization

tab for setting special AT strings when they are required The relevant tabs are displayed depending on the network type.

Note When setting parameters for network nodes, only the parameters that are practicable for the particular combination can be modified. This depends on the following: • Network node type specified in the Properties Network Node dialog, Network Connection

tab and the

• Operating mode specified in the Properties Network dialog, Network Settings tab.



General tab

Figure 2-33 Properties - SINAUT Dedicated Line TIM dialog, General tab

The following parameters are available in the General tab: ● The Name box displays the name of the module in SIMATIC stations. You can only

change the default interface name in SIMATIC PC stations and other stations. A new, modified name appears in the SIMATIC Manager and in the network configuration.




Network Connection tab The Network Connection tab allows you to set the most important networking properties of the WAN network node.

Figure 2-34 Properties - SINAUT Dedicated Line TIM dialog, Network Connection tab

The parameters here are: ● The node type selected in the list box:

– The master station is the highest hierarchic level in the network. It generally collects information from the underlying network nodes and specifies settings for the nodes in the field.

– A node station is at a hierarchically lower level than the master station or another node station and is at a higher level than one or more other stations.

– A station is at a level close to the field and hierarchically below a master station or node station.

● The WAN address in the network. The unique WAN address of the node can be modified. A consistency check ensures that WAN addresses that have already been assigned cannot be selected.



Note Assigning the station addresses of ST1 subscribers The station number of ST1 subscribers is always the same as the SINAUT subscriber number and the WAN address. If ST1 subscribers (S5 stations) are connected to a SINAUT network, the existing ST1 station addresses should, where possible, be entered as the station addresses from the range 1 to 254. The master station number in ST1 networks is assigned when setting parameters for TIM modules in the Properties dialog, Special tab. For more detailed information on configuring ST1 subscribers, refer to the ST1 configuration rules in the SINAUT ST1 configuration overview.



Basic Param. tab The Basic Param. tab contains the communication parameters for the selected WAN node.

Figure 2-35 Properties - SINAUT Dedicated Line TIM dialog, Basic Param. tab



The following parameters are available: ● Interface:

This output box indicates whether the current node is operated on the internal or the external WAN interface of the TIM.

● Interface type (TIM 4R-IE only): Here, you set the type of interface: RS-232 or RS-485 mode

● RS-485 termination (TIM 4R-IE only): Activation of the terminating resistor for the RS-485 bus

Note If the interface is set to "RS-485", you will need to set the internal terminating resistor of the module for the RS-485 bus. If the TIM 4R-IE is at the start of the RS-485 bus, which is normally the case, select the setting "yes". Otherwise select "no".

● Operating mode: This setting specifies whether the interface connected to the current node will be operated in interrupt or in DMA mode. Only one of the two interfaces of a TIM module may be operated in DMA mode. Range of values: Interrupt (block), DMA, Interrupt (single characters) Default: Interrupt (block) – Operating mode = Interrupt (block)

This operating mode applies to the transmit and receive direction. The default mode Interrupt (block) is suitable for all connections. Four characters are transferred per block. Following this, there is an interrupt. The received characters are checked only after a complete message has arrived.

– Operating mode = DMA This operation mode applies to the transmit and receive direction. The DMA mode should be used for connections with a high baud rate or heavy message traffic, however not for GSM networks. Only one of the two interfaces of a TIM module may be operated in DMA mode.

– Operating mode = Interrupt (single characters) This operating mode is used only in the receive direction. In the transmit direction, the block mode continues to the used. This interrupt mode is suitable for extremely bad lines. An interrupt is triggered per transmitted character and each character this analyzes immediately after it is received allowing extremely good diagnostics of transmission errors. This mode is more reliable than the block mode but is slower.

● Extra transm. time: This is an offset added to the transmit retry time. The send retry time is calculated automatically on the TIM. From the Extra transm. time parameter, the character delay time can also be calculated (character delay time = extra transm. time divided by 5). An offset time should be entered in the Extra transm. time input box, for example when the send retry time cannot be calculated completely as is the case with satellite transmissions or wireless links over repeaters. Range of values: 0 .. 65535 ms Default: 0 (for M1 or M20 module: 400 ms)



● Number of spontaneous messages: This function is available only for the station and node station node types. Range of values: 0 .. 255 Default for dedicated lines: 20 Default for dial-up networks: 200 – Number = 0 in polling mode:

All spontaneous messages pending at the time of the first polling message are transferred.

– Number = 1 .. 255 in polling mode: Maximum 1-255 spontaneous messages pending at the time of the first polling message are transferred.

In a dial-up station, the Number of spontaneous messages parameter decides after how many messages the master station has the opportunity of transferring its pending messages to the station.

● Limit for locked messages: This parameter can only be set for dial-up networks and specifies the maximum percentage of locked messages in the send buffer. If this percentage is exceeded, the image method will be used for all new locked messages arriving. This prevents an overflow of the send buffer. Messages are marked as locked if they can no longer be transferred to the addressees due to communication problems (known as the data brake). Range of values: 0 ... 90% (If 0 is entered, the default setting is used) Default: 50%



Dedicated Line tab The Dedicated Line tab contains special parameters required only when using dedicated lines.

Figure 2-36 Properties - SINAUT Dedicated Line TIM dialog, Dedicated Line tab

The parameters for dedicated lines include: ● RTS/CTS delay time:

Setting the RTS/CTS delay time is required, for example when connecting a modem to the RS-485 port of the TIM module. The value is necessary for the RTS/CTS delay time can be found in the descriptions of the modems. Range of values: 0 .. 65535 ms Default: 0 – RTS/CTS delay time = 0:

After setting the RTS signal, transmission only starts when the CTS signal was set by the modem.

– RTS/CTS delay time > 0: Transmission is not delayed until the CTS signal of the modem. After the RTS signal has been set, transmission is delayed for the selected time and then started immediately.

● Polling monitoring time: Specifies the latest time after which a station or node station TIM expects to be polled. If the TIM is not called after this time, it sends a message to its local CPU indicating that the master station is disrupted. Range of values: 0 .. 65535 s Default: 0 (0 means no monitoring)



Even if no monitoring is set here, the TIM module registers the message traffic over the WAN and automatically sends the same fault message to its CPU if it does not register any message traffic for several seconds. If a maximum message length of 240 bytes is set, a with a retry factor of 3 and a transmission rate of 9600 bauds, the message is sent after approximately 4 seconds without message traffic, and at a transmission rate of 1200 bauds, after approximately 32 seconds.

● Send delay time: The send delay time is used only when the CTS signal comes from the modem (RTS/CTS time delay parameter = 0). As soon as the CTS signal comes from the modem, the send delay time is started. Data transmission is started only after this time elapses. This parameter is required, for example, when additional offset times are required to allow repeaters to start up on wireless links prior to starting data transmission. If 0 is entered, no send delay time is used. Range of values: 0 .. 65535 ms Default: 0

● Max. allowed disruption time (TIM 4R-IE only): Here, you can enter the tolerance time for a connection disruption detected by the TIM. If there is still a disruption on the connection when the set time has elapsed, the disruption is signaled to all connection partners of the disrupted station. Range of values: 0 ... 255 seconds Default: 0 If disruptions occur frequently in networks (for example in some wireless networks), it may be helpful to increase the allowed disruption time without increasing the repetition factor for messages (see also properties dialog Dedicated line, Network settings tab). Increasing the allowed disruption time delays signaling of station failures and so reduces the number of organizational messages when stations return.

● Ratio polling / spontaneous: This output box displays the number of spontaneous messages that can be sent by a master station between two polls. Range of values: 0 .. 255 Default: 1

● Number of stations in sub-cycle: This output box displays how many stations in the sub-cycle should be polled per main cycle. Range of values: 0 .. 250 Default: 0 The schematic shows a configuration with stations in the main and sub-cycle and the resulting polling order if 1 is set for the Number of stations in sub-cycle parameter.



Figure 2-37 Main cycle - sub-cycle

● Transfer mode:: This parameter specifies the form in which ST7 data messages are sent when using the ST7 protocol. Range of values: - transfer data as blocks of single messages - transfer data as blocks of multiple messages Default: Single messages



Dial-up Network tab The Dial-up Network tab contains special parameters required only when using dial-up networks lines.

Figure 2-38 Properties - SINAUT Dedicated Line TIM dialog, Dial-up Network tab

The dial-up network parameters include: ● Transmission criteria:

This setting controls connection establishment for the transmission of conditional spontaneous messages. The transmission criterion for conditional spontaneous messages can only be set for stations and node stations. Standard conditions, fill level, time of day, time scheme Default: Standard conditions – Standard conditions:

A connection is not established for existing conditional spontaneous messages. The conditional spontaneous messages are sent only when a connection is established for sending unconditional spontaneous messages or a buffer overflow is threatening or the connection is established by the other end.

– Fill level: When the send buffer is filled to the specified level with conditional spontaneous messages, the TIM module automatically attempts to establish a connection and to transmit the messages. - Input box %: Entry of the send buffer fill level as a percentage (default: 50%)

– Time of day: A connection is automatically established and the messages sent at the specified time of day. The time must be entered:



- Input box Hours Entry of the time (hour) - Input box Minutes Entry of the time (minute)

– Time scheme: A connection is automatically established and the messages sent at the specified time intervals. The interval must be entered: - Input box Hours Entry of the hour value for the send interval - Input box Minutes: Entry of the minute value for the send interval

● Call answer delay: This sets the time that the WAN driver waits before answering an incoming call. This allows time to answer a telephone call if a telephone is attached parallel with the TIM on a shared telephone connection. The value 0 means there is no call answer delay. Range of values: 0 ... 60 s Default: 0 s

● Min. connection duration: Here, the minimum connection duration of a dial-up connection can be set. This may be required in fast dial-up networks to be able to wait for the response of subscribers during a GR before the connection is terminated. Range of values: 0 ... 65535 s Default: 5 s 0 means that there is no minimum connection duration.

● Dialing test interval: This specifies the time in minutes for a test interval. A test interval is started when no connection to a particular subscriber could be established from a master TIM after the specified number of retries. Following the test interval, the WAN driver automatically reattempts to establish a connection to the specified subscriber. If a connection cannot be established, the test interval starts again. If the test interval is running and the WAN driver gets a new message to be sent to the disrupted subscriber, it does not wait for the test interval to end but attempts to establish a connection immediately and to send the message. Range of values: 0 ... 255 minutes Default: 5 minutes

● Cancel delay time: This parameter specifies how long a dial-up connection is retained when the send buffers of the TIM module are full and it can send no further messages or data to the CPU. All messages received over the WAN interface are acknowledged negatively until this time has elapsed. Due to the negative acknowledgment of the previously sent message, the communication partner will repeat the message after the send retry time. If the cancel delay time has elapsed, the connection is terminated. Range of values: 0 ...255 seconds Default: 0

● Transfer mode:: This parameter specifies the form in which ST7 data messages are sent when using the ST7 protocol. Range of values: - transfer data as blocks of single messages - transfer data as blocks of multiple messages Default: Single messages



Dialing Param. tab The Dialing Param. tab appears only with dial-up network nodes and includes all parameters specific to call-numbers.

Figure 2-39 Properties - SINAUT Dedicated Line TIM dialog, Dialing Param. tab

The parameters here are: ● Configured modem:

The modem specified in the hardware configuration is displayed. ● Dialing mode:

Specifies how the modem is controlled. Note that only the AT mode can be used on the internal interface of the TIM. A choice between AT mode and V.25bis is possible only for the external WAN interface. Range of values: AT mode, V.25bis Default: AT mode

● Dialing format: The data format of the dial-up phase depends on the type of modem. The following settings are possible: 8 data bits, no parity, 1 stop bit 8 data bits, odd parity, 1 stop bit 8 data bits, even parity, 1 stop bit 8 data bits, no parity, 2 stop bits 8 data bits, odd parity, 2 stop bits 8 data bits, even parity, 2 stop bits 7 data bits, no parity, 1 stop bit 7 data bits, odd parity, 1 stop bit 7 data bits, even parity, 1 stop bit 7 data bits, no parity, 2 stop bits



7 data bits, odd parity, 2 stop bits 7 data bits, even parity, 2 stop bits Default: - in AT mode: 8 data bits, no parity, 1 stop bit - with V.25bis: 7 data bits, even parity, 1 stop bit

Note The data listed above applies only to the dialing phase. The data format in the data phase is set at switch 5 on the MD3 modem. It is only necessary to set the dialing format on older modems that do not support "Autoband". With "Autoband", the modem can determine the character and data format in the dialing phase automatically based on the first AT string.

● Dialing command: This is the dialing command for the local modem. The following dialing commands are possible: – D (AT command) – DP (AT command, pulse dialing) – DT (AT command, tone dialing) – CRN (V.25bis) – CRNP (V.25bis, pulse dialing) – CRNT (V.25bis, tone dialing) Default: D. This default modem dialing command should be used where possible.

● Dialing prefix: This is the access number (outside line) for a private branch exchange (typical entry 0 or 9) or for an alternative telephone provider. A number up to 12 digits long can be specified. With direct connection to the dial-up network and without an alternative telephone provider, this parameter can remain empty. The dialing prefix can be changed again in the Properties of subscriber dialog.

● Own tel. number: Here, you enter your own telephone number for the network node including the area code. This telephone number can no longer be changed later in the Properties of subscriber dialog.

Note In dial-up networks, in which another subscriber within the same local network cannot be dialed with the local area code, it is advisable to enter your own telephone number in the Own tel. number box without area code and to specify the area code in Dialing prefix.

● PIN number: Here, the PIN number for a GSM module must be entered so that this can be transferred from the TIM module to the module.

CAUTION

If an incorrect PIN number is entered, the D1 or D2 card in the module might be disabled. If the fault LED lights up during connection establishment, the diagnostic buffer of the TIM must be checked because an entry for a bad PIN number is generated here.



● Special service: The following special services are available: – No special service – SMS in the D1 network (TAP protocol) – SMS in the D2 network (UCP protocol) – SMS digital access

Note If two MD3 modems communicate with each other, they must not be operated in the 1200 baud, half-duplex, AT mode mode.

AT Initialization tab The AT Initialization tab appears only in dial-up network nodes and when the AT mode is selected as Dialing mode in the Dialing parameters tab. The string stored here is formed automatically from the previously set dial-up network parameters and the SINAUT dial-up modem selected for the network node (MD3, MD4 or GSM modem TC35, MC45, MD720-1). If "third-part modem" is set for the network node, no initialization string is displayed. You will then need to enter the correct string for the modem you are using. The initialization string set here is transferred to the modem operating in AT mode only when the TIM starts up.

Figure 2-40 Properties - SINAUT Dedicated Line TIM dialog, AT Initialization



● Initialization string input box: In the left input box, the AT string is displayed as text and in the right-hand box in hexadecimal notation. No entries can be made in the right-hand box. In the left-hand box, a string can only be entered when either no entry can be found for the current combination of modem and network parameters in the SINAUT modem database or the User defined option was set. Otherwise the valid string is taken from the database.

● User defined option: It allows the manual entry of AT Initialization strings for the basic settings of the modem.

● Type of string output box: This box displays the content of the current string.

Special features of the MD4 modem On the MD4 modem, the standard string is ATS45=83$P1\N0&W$M=n. The part string $P1 defines the V.110 mode at a transmission rate of 9600 bauds. The n character at the end of the string is the placeholder for the MSN (last digit of the telephone number) of the subscriber. The stored standard string allows only transmission rates of 9600 and 19200 bauds, no other rates are not supported. This standard setting does, however, allow communication with the following subscribers: ● Old ISDN modems installed with SINAUT ST1 devices ● GSM stations ● SMS centers: When using MD4 modems in ISDN networks, it is only possible to operate at a transmission speed of 9600 bauds with the standard setting and not at the maximum speed of 38000 bauds. If the maximum speed of 38000 bauds is to be used with MD4 modems in pure ISDN networks, the $P1 entry in the standard string must be replaced by $P5. This changes from the V.110 transmission mode to the X.75 mode allowing a transmission rate up to 38000 bauds. When using MD4 modems, note the following if you change the telephone number later:

Note Since the MSN number is automatically added to the generated AT string with the MD4 modem, if you change the telephone number later, remember that the MSN number in the AT string for the MD4 modem may need to be modified manually.

2.5.8 Plausibility check of the network configuration A plausibility check of the configured network is performed either when the network is stored with the Save and Compile... function or when the consistency check is started directly from the Network / Check Consistency menu. The following is reported: ● Subscribers not connected to a any subnet ● Subnets with only one subscriber

Configuration software for SINAUT ST7 2.6 Configuring connections in the SINAUT Configuration Tool


● Inconsistent connections, for example due to the wrong WAN protocol The following are also checked for SINAUT networks: ● Compatibility of the connected modem types with each other ● Compatibility of the connected modem types with the network parameters The following is checked for SINAUT dedicated line networks: ● The parameter assignment of a master station for the dedicated line network ● The existence of more than one master station for the dedicated line network in polling

mode

Note If SIMATIC S7-300 stations are connected only over the WAN, the following warning may be displayed for the non-connected MPI nodes of a CPU in older STEP 7 versions: "CPU... (Station ..): The subscriber (...) is not connected to a network." This warning can be ignored.

To complete network configuration, the configured version must be saved with the Network / Save menu to allow other STEP 7 and SINAUT applications access to the configured data. Configuration continues by calling the SINAUT configuration tool.

Note From the network configuration, not only the Save but also the Save and Compile... function can be called that generates the system data blocks (SDB) after saving the configuration. To acquire all the configured parameters of the TD7 software when generating the SDBs both in new projects or when making modifications to the configuration of existing SINAUT installations, the generation of SDBs for SINAUT networks should only be performed in the Subscriber Administration of the SINAUT configuration tool.

2.6 Configuring connections in the SINAUT Configuration Tool

2.6.1 The SINAUT Configuration Tool

Introduction The SINAUT ST 7 Configuration Tool is started in the Start / SIMATIC / SINAUT ST7 / Configuration menu.



At the start of configuration, you open a project with the Project / Recently Used menu or the Open Project button in the toolbar. After selecting the project, the SINAUT ST7: Configuration dialog opens making the three following main functions of the SINAUT Configuration Tool available: ● Connection Configuration for SINAUT connections ● Subscriber Administration for SINAUT subscribers ● SINAUT ST1 - Configuration Overview

Figure 2-41 Selection dialog of the SINAUT Configuration Tool

To continue configuration, first select the Connection Configuration option. When the SINAUT Configuration Tool is open, you can change between the three functions using: ● The SINAUT / ... menu, ● The corresponding buttons in the toolbar or ● the following function keys:

– F3 for Connection Configuration – F4 for Subscriber Administration – F5 for the SINAUT ST1 - Configuration Overview

Program information and SINAUT Internet pages You can display program version and copyright information in the About dialog of the SINAUT configuration tool that can be opened using the Help / About menu. With the Internet address www.sinautst.de at the top right in the SINAUT About dialog, you can open the SINAUT home page directly.



2.6.2 Configuring SINAUT connections

The SINAUT ST7 connections In SINAUT ST7 installations, connections are always configured between the following subscribers: ● From CPU to CPU ● From CPU to a SINAUT ST7cc/ST7sc control center ● From a CPU to an ST1 device

Figure 2-42 Example of a SINAUT ST7 connection from the master station to station 1

The connection shown in dark red from the master station to station 1 is not visualized in this form in the network configuration with NetPro. This is taken into account in the connection configuration that allows the user ● to configure connections without knowing the exact connection path and ● to view the exact connection path over a list of used network nodes. The degree of detail

of the connection information can be set by users themselves.



View of the Connection Configuration window After opening the connection configuration, the configuration window opens.

Figure 2-43 The Connection Configuration window of the SINAUT Configuration Tool

In the right-half of the window, the possible connections are listed in a tree structure resulting from the network configuration in NetPro. The connections actually required and used for communication in the SINAUT installation must be transferred from the right-hand to the left-hand window Configured connections. The two lists display the number of connections involved. The entries in the connection tables must be interpreted as follows:

Table 2-2 Symbols in the connection list of the connection configuration

Level Symbol Meaning

1 Connection starting point

2 Connection end point

3 Alternative path

4 Connection node over which the connection runs

Invalid connections are displayed in red as shown in the example of a connection that no longer exists due to reconfiguration. The labeling of the individual connection point in the basic setting describes the relevant subscriber with: Subscriber number / Station name / Module / Interface. Example: 5 / Station 3 / CPU 312 / MPI (2)



The representation can be set to meet individual requirements using the Extras / Options menu.

Functions of connection configuration To make configuration of the required connections as simple as possible for the user, the SINAUT Configuration Tool uses the following strategy: ● The entire currently configured network is analyzed. All potential communication

subscribers from the SINAUT perspective are assigned a subscriber number if they do not already have one. The subscriber numbers for CPU modules and third-party stations are assigned starting at no. 1, for TIM modules there are assigned starting at no. 1001.

● A tracking algorithm detects ALL connections in the current network. These connections can also extend over several LANs and SINAUT networks. The connections permitted based on specified rules are represented on the right as possible connections in a tree structure.

● SINAUT connections that have already been configured are displayed in the left-hand window for configured connections. Each of the connections loaded there is then checked to establish whether its configured parameters match the current network and hardware configuration. If this is not the case, and error message indicating incorrect connections is displayed as soon as the connection configuration is opened and the bad connection is displayed in red in the configured connections window.

If a station of the type other station or SIMATIC S5 was configured in NetPro, connections from the stations to stations of the type ST7, PG/PC, or an ST7cc control center are not displayed. This does not, however, mean that these connections do not exist. These connections are in fact displayed in the opposite direction; this means, for example, from an ST7 station to a station of the type other station or SIMATIC S5. As a general rule, a connection displayed in the configured connections in only one direction, works in both directions.

Selecting the required CPU-CPU connections If no connections are displayed in the left-hand window, the required connections must be transferred from the right-hand window. Follow the steps outlined below: 1. Expand the tree structure by clicking on the branch symbol (+) or by double-clicking on

the connection group. The tree structure opens. 2. Select a possible connection in the right-hand window. 3. Enter the possible connection as a configured connection in the left-hand window by

– selecting the Edit / Apply menu or – pressing the right mouse button and selecting Apply in the displayed context menu.

If alternative communication paths exist and you want to use them, expand the possible connection structure in the possible connections by double-clicking on it and select the connection and apply it. Redundant connections: With redundant connections, for example those of a redundant ST7cc/ST7sc control center, the upper connection in the tree structure is the preferred path and the lower connection is the substitute path. The connection with the preferred path should therefore be applied first.



Connections that are not required can be removed from the list of configured connections at any time. To do this, select the connection in the configured connections and select the Edit / Delete menu or select Delete in the displayed context menu (right mouse button) Bad connections displayed in the configured connections window are shown in red and can result from bad configuration or subsequent changes to a configuration. If there is an incorrect connection between two nodes, the old and no longer valid connection must be deleted from the configured connections and the current connection must be taken from the list of possible connections again.

Note If a connection configured in the network configuration is not included in the list of possible connections because it is invalid, this is displayed in the list of invalid connections. The invalid connections dialog is described separately and contains information on connections that do not conform with SINAUT.

Saving the connection configuration Once any invalid connections have been checked and removed and all required connections configured so that they appear in the left-hand window, the connection configuration must be saved with the SINAUT / Save menu or the Save button in the toolbar. Saving is necessary to store the connections permanently. If a message is displayed during saving indicating that a connection between two stations configured in NetPro could not be found, the connection must be checked in NetPro and reconfigured. After saving the connection configuration, open Subscriber Administration of the SINAUT Configuration Tool to configure the subscriber data and to generate the system data blocks there.

Changing the connection configuration By opening the connection configuration again, you can change the scope of the configured connections at any time. By changing parameter settings or by reconfiguring, it is possible that a previously configured connection no longer exists. This then appears in the Recover lost connections list that is described separately. After changing the connection configuration, this must be saved, Subscriber Administration must be called and the generation of the system data blocks started.

2.6.3 Invalid Connections With its algorithms, connection configuration finds all the possible connections in the current project. Connections that do not meet certain rules are displayed for the user in the Invalid Connections dialog. The connections contained here are then not included in the list of possible connections. The Invalid Connections dialog is displayed using the SINAUT / Show Invalid Connections menu or the Show Invalid Connections button in the toolbar.



Figure 2-44 Invalid Connections dialog

If you expand a connection structure in the list of invalid connections by double-clicking on it and if you then select a single connection, the reason for the invalidity and a note on how to remedy the situation are displayed in the lower part of the dialog. The note might, for example, inform you that the connection should be configured in the reverse direction. Within SINAUT ST7, permitted connections must adhere to the following rules: ● A connection must not run through ST1 and ST7 networks. This can occur when a

connection runs through several WANs in which different WAN protocols are configured. ● A connection must not run through an inconsistent network. Examples are described

along with the plausibility check in the network configuration. ● A connection must not run through a WAN sub-connection on which two MD3 modems

communication each other using 1200 bauds / half duplex / AT mode. ● In an ST1 network, a connection must not run from a station or node station TIM to

another station or node station TIM (direct communication). ● A connection should not run from a station or node station TIM to a master TIM. The

reverse direction is preferable. Connections between two ST1 subscribers can be configured in the SINAUT ST7 configuration tool and are therefore not included as invalid connections.



Note To avoid including large numbers of connections unnecessarily in the list of possible and configured connections, some connections used between two subscribers in both directions are shown only in one direction. A connection displayed in the configuration tool is always valid in both directions.

2.6.4 Recovering lost connections If changes are made to connections in a project, it is advisable to open the Recover lost connections window afterwards. You can do this with: ● The SINAUT / Recover lost connections menu or ● The Recover lost connections button on the right of the toolbar If changes to the connection configuration, previously existing connections were modified and either linked to other objects or completely deleted, connection configuration has algorithms with which to find these lost connections in the project. Deleted connections are displayed in red in the left-hand part of the Recover lost connections window. Connections that are similar to the deleted connections may also be listed in the right-hand part of the window. This allows you to check whether there is a substitute or successor to the last connection. If you no longer require the lost connections in the left-hand part of the window, you can delete these by selecting and clicking the Delete lost connections button. If connections are displayed in the right-hand part of the window that are similar to the last connections you can insert these again if you have accidentally deleted connections and still require them. To do this, select the connection in the right-hand part of the window and click the Recover connections button.

2.6.5 Printing connection lists To document the configured ST7 connections, the SINAUT configuration tool allows connection lists to be printed in two formats. You start a printout with the Project / Print menu. Before printing, you can use a print preview function to check the printout using the Project / Print Preview menu.

Print connection list - overview format SINAUT ST7 - list of configured ST7 connections - overview format No. of CPU ST7 sbscr Station to CPU ST7 sbscr Station # Concts. 1 CPU414-1 5 Ctrl Cent 4 SIMATIC S5(1) 1 2 CPU414-1 5 Ctrl Cent CPU314 6 Station 1 2 3 CPU414-1 5 Ctrl Cent CPU314 7 Station 2 1

Configuration software for SINAUT ST7 2.7 Subscriber administration in the SINAUT configuration tool


Print connection list - full format SINAUT ST7 - list of configured ST7 connections - full format Connection 1 CPU ST7 sbsc Station Network from CPU414-1 5 Ctrl Cent MPI via TIM 42 MPI 3 TIM Rack Ctrl Cent MPI via TIM 42 MPI 3 TIM Rack Ctrl Cent Dial-up network via 4 SIMATIC S5(1) Dial-up network to 4 SIMATIC S5(1) Partyline Connection 2 CPU ST7 sbsc Station Network from CPU414-1 5 Ctrl Cent MPI via TIM 42 MPI 3 TIM Rack Ctrl Cent MPI via TIM 42 MPI 3 TIM Rack Ctrl Cent Dedicated line via TIM 42 1 Station 1 Dedicated line via TIM 42 1 Station 1 Partyline to CPU314 6 Station 1 Partyline Connection 3 CPU ST7 sbsc Station Network from CPU414-1 5 Ctrl Cent MPI via TIM 42 MPI 3 TIM Rack Ctrl Cent MPI via TIM 42 MPI 3 TIM Rack Ctrl Cent Dial-up network via TIM 42 1 Station 1 Dial-up network via TIM 42 1 Station 1 Partyline to CPU314 6 Station 1 Partyline Connection 4 CPU ST7 sbsc Station Network from CPU414-1 5 Ctrl Cent MPI via TIM 42 MPI 3 TIM Rack Ctrl Cent MPI via TIM 42 MPI 3 TIM Rack Ctrl Cent Dedicated line via TIM 32 2 Station 2 Dedicated line via TIM 32 2 Station 2 Partyline to CPU314 7 Station 2 Partyline

2.7 Subscriber administration in the SINAUT configuration tool Once the SINAUT ST7 connections have been configured, all the requirements are met so that you can ● create, ● display, ● process and ● pack the subscriber data for the ST 7 communication subscribers so that it can be

understood by the hardware components; in other words, in data blocks (DBs) or system data blocks (SDBs).



Processing is always necessary when data needs to be acquired that is connection-related; in other words cannot be assigned to a particular subscriber. Processing of subscriber data is also necessary when SINAUT data is stored for non-SINAUT objects, for example the DB configuration for the CPU modules and SMS messages. How to set parameters for this data in the subscriber administration of the SINAUT configuration tool is described below. After starting subscriber administration, first the previously known data of the subscribers is loaded from the data management and then updated. The following data is updated: ● Subscriber information: Which subscribers exist? ● Networking information: Who communicates with whom over which connections? ● DB configuration information: Which data blocks are generated for a CPU? The subscriber list always shows the latest situation in the SINAUT subscriber world.

2.7.1 Subscriber list

Information in the subscriber list In the left-hand window, the subscriber administration contains a tree structure of the subscribers of the project (Subscriber types) and in the right-hand window the subscriber list itself.

Figure 2-45 Windows of subscriber administration

By making a selection in the directory tree in the left-hand window, only certain subscriber types can be displayed in the subscriber list. The TD7 on TIM folder in the directory tree is used to configure the TD7 software for an Ethernet TIM and is not relevant for the subscriber parameter assignment described here.



In the subscriber list on the right, you will see the following entries for the SINAUT ST7 communication subscribers: ● Subscriber no.: The subscriber number of the SINAUT subscriber that is unique

throughout the project and is required for WAN communication. This has an extra check box to allow the CPU modules to be selected for system data generation.

● Red. Subscriber no.: The Redundant subscriber number parameter is used only when there is a redundant partner for the subscriber in question. The number specifies the common subscriber number under which the redundant system can be addressed by other subscribers.

● Subscriber no. of red. Partner: The Subscriber number of the redundant partner parameter is used only when there is a redundant partner for this subscriber. The parameter specifies which of the subscribers belong to a redundant relationship.

● Subscriber type: The subscriber type specifies the class of subscriber involved. This cannot be changed by the user.

● Module: The module, application or PC/PG name. This can be changed in the configuration. As default, this is the name of the module type or the application as specified in the configuration.

● Station: Name of the station assigned in the network configuration in NetPro. ● SINAUT connected: Specifies whether a SINAUT connection was configured for the

subscriber. ● SINAUT library: Name of the SINAUT software block library for CPU and TD7onTIM-

compliant TIM modules. The setting of the subscriber-related properties is made in the Properties of subscriber dialog that is opened when you double-click on one of the subscribers in the list.

Marking for selective system data generation In the subscriber administration, it is possible to select any CPU subscriber for later selective generation of the software blocks. To select a subscriber, click in the check box in front of the subscriber number (a check mark is set). The number of selected CPU modules is displayed in the text box Selected CPUs: above the list. You can remove the check mark again by clicking with the mouse.

Changing the subscriber number To change the subscriber number, click on the required subscriber. By clicking again on the subscriber number, by typing Alt+Return, by pressing function key F2 or by selecting the menu Edit / Change Subscriber, the Subscriber number field becomes editable. The user can then enter any unassigned subscriber number as required. This may be necessary, for example, when connecting older installations (SINAUT ST1).

Generating a redundant ST7cc/sc control center If two SIMATIC PC stations were configured for a redundant SINAUT ST7cc/sc control center, the assignment of the two redundant partners is made at this point. Right-click on the directory tree and select Add redundant ST7cc/ST7sc... in the context menu. For detailed information on configuring a single or redundant ST7cc/ST7sc control center, refer to the SINAUT ST7cc or ST7sc documentation.



Dialogs below the subscriber list Any dialogs displayed below the subscriber list are used for configuring the TD7 software for the TIM (TD7onTIM) that can only be configured for TD7onTIM-compliant TIM modules. These dialogs are not available for other subscribers. The TD7onTIM is configured and the parameter settings made following this in the subscriber parameter assignment.

2.7.2 Parameters for individual subscribers

Overview of the tabs of the Properties of subscriber dialog By double-clicking on a subscriber number or by selecting the Edit / Properties menu, the Properties of subscriber dialog is displayed. The content and number of the tabs of the Properties of subscriber dialog depend on the subscriber type.

Table 2-3 Overview of the Properties dialog tabs according to subscriber type

Tab CPU TIM Other station, SIMATIC S5, PC station, PG

Names of follow-up dialogs

Info Yes Yes Yes - Connections Yes Yes - Properties - Local Connection Polling List - Master TIM - Properties - Poll list entry Telephone Directory

- When necessary

- Properties - Telephone number

DB Configuration

Yes - - -

SMS Configuration

When SMS master configured

- - SMS CPU Configuration, SMS DB Data, SMS Message Data

Library Information

Yes - - -



Info tab

Figure 2-46 Properties of subscriber dialog (CPU), Info tab

The Info tab displays the following information on the selected subscriber: ● Name shows the default name of the module or the name assigned in network

configuration ● Station displays the set network node type ● The subscriber number is displayed. ● Status from displays the date of the last configuration ● The date created is displayed. ● Basic type displays the network object type from the network configuration ● Extended type displays the extended network object type adopted in the network

configuration (for example ST7-CPU, ST7-TIM, ST1 subscriber, ST7cc or SMS master)



Connections tab This tab lists all the configured local connections over LAN along with their most important properties for the current subscriber.

Note During the analysis of the subscriber data, if the configuration software detects that STEP 7 homogeneous connections are necessary for processing a SINAUT ST7 connection, these are created automatically. These are connections from the S7-400 CPU to a TIM module and from TIM to TIM module over the MPI bus and over communication block connections. As an alternative, the user can create these connections manually during network configuration. Existing connections are automatically used by the SINAUT configuration tool.

Figure 2-47 Properties of subscriber dialog (CPU), Connections tab

Here, you can configure the following: ● The length of the CPU send buffer for any existing communication function block

connections of a CPU. This is the same for all communication function block connections of the current CPU. Range of values: 202 .. 65208 bytes Default: 2020 bytes.

By double-clicking on a subscriber row in the local connections output box, you open the Properties - Local Connection dialog for this connection.



Properties - Local Connection dialog for the TIM This dialog displays the properties of the local LAN connection of a TIM module to its CPU.

Figure 2-48 Properties - Local Connection dialog (TIM)

For the local connection of the TIM module, you can set the following here: ● Send Keepalives for this connection:

If this option is enabled, keepalive messages are sent on this connection at the intervals set in the network configuration for the TIM.

● Queue entries [number]: Range of values: 10 .. 256 Default: 64 The number of queue entries is the number of messages that the TIM module can buffer prior to transmission. In general, you do not need to change the default setting. It may be useful to increase the value for a master TIM to relieve message traffic if there is a heavy load at certain times due to the transfer of large amounts of data, for example archive data.

Properties - Local Connection dialog for the CPU This dialog visualizes the properties of a local LAN connection of a CPU and allows the following properties to the selected: ● CPU modules with X connections / P bus connections:

– The length of the send buffer [bytes] for these connections Range of values: 76 ... 65382 bytes



Default: 760 bytes This parameter is not relevant for PBC connections.

– The Connection monitoring time [s]; in other words, the time that must elapse before dummy messages are sent to check the connection. Range of values: 1 ... 32 s Default: 5 s

● CPU modules with PBC connections: – The Connection monitoring time [s],

Range of values: 1 ... 32 s Default: 5 s

Figure 2-49 Properties - Local Connection dialog (CPU)



Polling List tab

Figure 2-50 Properties of subscriber dialog (TIM), Polling List tab

This tab for a TIM module displays the TIM modules that can be polled by this station in polling mode with the subscriber name, station address, ID for main cycle poll, enable status offline, enable status online, module name, and station name. By clicking adopt online state, the entire online status is adopted in the configuration. This function is available only for the TIM 4R-IE. By double-clicking on a subscriber role in the internal interface or external interface output box, the Properties - Poll list entry dialog for this connection opens.



Properties- Poll list entry dialog

Figure 2-51 Properties- Poll list entry dialog

The Identification area displays the following properties: ● subscriber:

The subscriber output box displays the polling subscriber (master TIM) with its subscriber number, module name, and station name.

● polls subscriber: The polls subscriber output box displays the polled subscriber with its subscriber number, module name, and station name.

● station address: The station address output box displays the station address of the polled subscriber.

● interface: The interface output box displays the interface type (internal/external) of the polled subscriber.

The Properties area displays the following options: ● polling in:

Options: main cycle, sub cycle Depending on the selected option, the CPU module is polled in the main or sub cycle.

● polling is: Options: enabled, disabled If the enabled option is selected, polling the CPU module in polling mode is enabled. Otherwise polling is disabled.



Telephone Directory tab This tab of a TIM module displays the subscribers of a dial-up network with the subscriber number, station address, dial string, enable status offline, enable status online (TIM 4R-IE only), module name and station name. If the TIM module is connected to two dial-up networks as is the case with a node station, the subscribers of both dial-up networks are listed.

Figure 2-52 Properties of subscriber dialog (TIM), Telephone Directory tab

By clicking adopt online state, the entire online status is adopted in the configuration. This function is available only for the TIM 4R-IE. Double-clicking on a subscriber in the internal interface output box opens the Properties - Telephone Number dialog for the connection of the subscriber selected in subscriber administration to the subscriber selected here in the Telephone Directory tab.



Properties- Telephone Number dialog

Figure 2-53 Properties- Telephone Number dialog

Double-clicking on a subscriber in the list in the Telephone Directory tab opens the Properties - Telephone Number dialog. This dialog is used when connection-specific modifications to the telephone number are necessary. Examples might be the unlocking of telephone numbers using AT commands or the use of different telephone service providers for connections. The Identification area at the top displays the following information: ● from subscriber:

Source subscriber of the connection ● to subscriber:

Destination subscriber of the connection ● station address:

Station address of the destination subscriber ● interface:

Interface type (internal/external) of the destination subscriber In the lower Properties area, you set the following properties: ● AT commands:

Here, you can set the connection-specific initialization of the modem. The specified AT command is output before the dial command for this number. The AT commands entered must be specified without the AT string.



● Dial command: Displays the configured dial command.

● Dial prefix: Displays the configured dial prefix. This can be modified.

● Tel. number: Displays the telephone number of the destination subscriber entered in the network configuration.

● dialing is: Options: enabled, disabled if the enabled option is selected, the dial-up connection is enabled. Otherwise, the dial-up connection is disabled. This function is available only for the TIM 4R-IE.

DB Configuration tab This tab displays the type and number of data blocks required for this CPU type.

Figure 2-54 Properties of subscriber dialog (CPU), DB Configuration tab

The following is displayed: ● CPU type:

Type of the current CPU ● Data blocks max.:

Maximum number of data blocks for this CPU (highest DB no.)



● Available data blocks: DB no. and name (header) of the existing data blocks in the offline data management of this CPU. These DB numbers can no longer be assigned.

● SINAUT data blocks to generate: – DB no. and name (header) of the DB BasicData:

This number is either read from the symbol table or is assigned the default 127. The number can only be modified if the complete SINAUT program with the supplied sources is recompiled.

– DB no. and name (header) of the communication data blocks and in the column to TIM the subscriber number of the partner TIM. Based on the existing blocks and the maximum value, the program proposes the numbers for all required data blocks. The user can change these numbers when necessary.

SMS Configuration tab In the SMS Configuration tab, you configure all the SMS messages required for the current CPU. This is only possible if the corresponding DB SMS_Control was created on the CPU. Several SMS data blocks can be defined per CPU and these can in turn contain several SMS messages.

Figure 2-55 Properties of subscriber dialog (CPU), SMS Configuration tab



In the tree display on the left-hand side, you can see the configured SMS messages in a tree structure with the following information: ● The highest level of the tree displays the current CPU with the text:

STEP 7 name of the CPU / type of the CPU / CPU short name ● The second level contains the configured data blocks with the text:

Block number / DB short name ● The third level lists the messages of the relevant DB with the text:

Message number - signal address (byte.bit) - "message text" In the tree display, the status of the object is indicated by the type of symbol used.

Table 2-4 Symbols of SMS Configuration

Correctly configured DB, data will be generated

Incompletely configured DB, data will not be generated

Activated SMS message

Deactivated or empty SMS message

Activated SMS message with incoming/outgoing status

Deactivated or empty SMS message with incoming/outgoing status

Below the tree display there is an information area in which the following characteristic data of the object selected in the list is displayed: ● CPU selected:

Subscriber number and current size of an SMS message ● DB selected:

Number of signals, current DB size, message numbers in this DB, main mobile number and backup mobile number

● Message selected: Signal address type and message text

To the right of the tree display of the messages, there are buttons that are triggered the available processing functions. The available functions can also be started using the context menu (right mouse button) when an object is selected. Functions are only possible when a CPU, a DB, or a message was selected in the SMS messages list. The range of active functions depends on the selected object. The functions available in SMS configuration are as follows: ● + DB (Add DB) :

A new data block is added. A free number is searched for as the DB number, starting at the maximum number for the current CPU.

● + Message(Add Msg) : A new enter message is added to the current DB. New messages are deactivated as default and must be activated before they can be sent.

● Edit... : The CPU, a DB or an SMS can be edited. Depending on the selected object, one of the following dialogs opens when the Edit function is activated: – Edit CPU: The SMS CPU Configuration dialog opens.



– Edit DB: The SMS DB Configuration dialog opens. – Edit SMS: The SMS Message Configuration dialog opens.

● Cut: The currency selected message is cut and can be inserted again later with the Paste function.

● Copy: The selected message is copied.

● Paste: The last message to be copied or cut is inserted.

● Import: A file created with the export function is imported into the selected DB.

● Export: The data of the current DB is exported to a file. The file format used is the Excel-compatible CSV format; in other words, the exported data can be edited in Excel.

● Remove: The current object is deleted. With data blocks, you are prompted for confirmation; messages are deleted immediately.

SMS CPU configuration dialog If you select a station in the SMS Configuration tab and click on the Edit button, the SMS CPU configuration dialog opens. Here, you can see the data of the current CPU that are relevant for SMS configuration.

Figure 2-56 SMS CPU configuration dialog

For the CPU, you can specify a name with up to eight characters (CPU short name). This short name can be inserted with a placeholder string in SMS messages later during SMS message configuration. As default, the short name has the first eight characters of the CPU name.



SMS DB data dialog If you select an SMS DB in the SMS Configuration tab and click on the Edit button, the SMS DB data dialog opens. This dialog displays and allows you to configure the data of the selected SMS DB.

Figure 2-57 SMS DB data dialog

The following parameters are available: ● DB No.:

The number used for the SMS DB. The number can be modified, the availability of the specified number on the current CPU is checked. If the number is already assigned by a DB of the CPU user program, an error message is displayed. SMS DBs on the other hand can be overwritten.

● DB short name: As default, the SMS DB short name has the first eight characters of the CPU name. For the SMS DB, you can specify a DB Short name with up to eight characters. This DB short name can be inserted with a placeholder string in the message text of SMS messages later during SMS message configuration.

● In the field Main SMS address: – SMSC subscriber no.: The subscriber number of the SMSC configured in subscriber

administration. – mobile phone no.: The mobile phone number to be used for the SMS recipient – acknowl. possible: The recipient can acknowledge (option selected) or not



● In the field Backup SMS address (optional): – SMSC subscriber no.: The subscriber number of the SMSC configured in subscriber

administration. – mobile phone no.: The mobile phone number to be used for the SMS recipient – acknowl. possible: The recipient can acknowledge (option selected) or not

● In the field Signal address: The signal address triggers the SMS message. As signal address, bits of a data block (DB), inputs or memory bits can be used. Per SMS data block, the data type of the signals (address type), the DB no. and the start address within the data field (address) must be specified. The signals must be located in a contiguous data field, for example in a data block. The first bit triggers the first SMS message, the nth bit triggers the nth SMS message. – Address type (DB, Input, Memory) – DB no. (only with an addressed type DB) – Address (Byte.Bit)

● In the field Parameter: – Valid period:

The period of validity specifies the time within which an SMS message should be delivered and, if selected in the SMS Message Configuration dialog, must also be acknowledged. If this has not taken place when the time expires, a diagnostic message is entered in the diagnostic buffer of the CPU.

– Add creation time stamp to messages option: In addition to the time added by the SMS control center, the creation time of the triggering event can also be sent if this option is selected.

● In the Lengths field: Here, the length of the DB to be created is calculated based on the currently available data and the resulting Load memory and the Work memory requirements. There is no check to make sure that the DB can actually be loaded on the CPU. This is the responsibility of the user.

SMS Message data dialog When configuring SMS messages, a function is available with which you can check the SMS character set. When entering text for SMS messages, this function blocks certain special characters that can cause problems with some SMS providers. Before you configure SMS messages for a subscriber, you should decide whether or not this function should be activated. If you activate the function, you can only enter the following characters: - All numbers - All letters except for umlauts ö, Ö, ü, Ü, ä and Ä - The special characters ! # % & / ( ) ? * + - . , : ; < = > and the blank. All other special characters are blocked. The function is activated in the subscriber administration in the Extras / Options menu. If you select a message in the SMS Configuration tab and click on the Edit button, the SMS Message data dialog opens. You configure an SMS message in this dialog.



Figure 2-58 SMS Message data dialog

The configuration options are available: ● Text:

The message text of the SMS message is entered in the Text input box. 120 characters can be entered.

● Insert replacement string: With this list box, you can insert replacement strings as keywords in the text of the SMS. The following replacement strings can be inserted in the text: – CPU short name ($CPUNAM$):

The CPU short name is configured in the SMS CPU configuration dialog – DB short name ($DBNAME$):

The DB short name is configured in the SMS DB data dialog – Message no. ($SMS$):

The message number is a unique number per CPU that is assigned by the SINAUT configuration tool. It can be seen in the tree display of the SMS messages list of the Properties of subscriber dialog.

The replacement strings are replaced by the actual values when the SMS is generated. By specifying the 3 strings, every SMS message in an S7 project can be uniquely identified.

● Request acknowledgment option: You can specify whether or not an acknowledgment is required for this message.

● Message is disabled option: If message output is activated, this option must be deselected (no check mark).

● Send SMS message: The list box indicates whether the message is sent on an event entering state (coming) or an event leaving state (going).



Library Info tab This tab shows the name, path, version, date of creation and source information for the German and English version of the SINAUT TD7 library with which system data for the current CPU will be generated.

2.7.3 Printing subscriber lists To provide users with an overview of the existing SINAUT subscribers, the SINAUT configuration tool provides the option of printing out the list of subscribers. A print preview function is available to check the output before printing.

Print subscriber list - Overview format SINAUT ST7 - list of configured ST7 subscribers - overview format ST7 sbscr Type Name Station Date: 1 SINAUT ST7 TIM TIM 42 Station 1 06/29/98 11:38 2 SINAUT ST7 TIM TIM 32 Station 2 06/29/98 11:38 3 SINAUT ST7 TIM TIM 42 MPI Tim Rack Ctrl Cent 06/29/98 11:38 4 SIMATIC S5 SIMATIC S5(1) 06/29/98 11:38 5 CPU414-1 CPU414-1 Ctrl Cent 06/29/98 11:38 6 CPU314 CPU314 Station 1 06/29/98 11:38 7 CPU314 CPU314 Station 2 06/29/98 11:38

Print subscriber list - Long format SINAUT ST7 - list of configured ST7 subscribers - long format ST7 sbscr Name Station Date: 1 TIM 42 Station 1 06/29/98 11:33 Type: SINAUT ST7 TIM Extended type: ST7 TIM local connection: to sbscr 6, X connection , not configured, Queue entries 256 Telephone numbers: external interface, list 0, STA 0, Tel.No. 5951358 external interface, list 1, STA 1, Tel.No. ATDP59553811 ST7 sbscr Name Station Date: 2 TIM 32 Station 2 06/29/98 11:33 Type: SINAUT ST7 TIM Extended type: ST7 TIM local connection: to sbscr 7, X connection , not configured, Queue entries 256

Configuration software for SINAUT ST7 2.8 TD7onTIM software package


2.8 TD7onTIM software package

2.8.1 Introduction SINAUT communication between the CPU modules or between CPU modules and a control center is implemented with the aid of TIM modules. The organization of SINAUT communication is handled by the SINAUT TD7 software package. In a SINAUT station, the TD7 software must be available either on the CPU or on a TIM. For these two situations, the SINAUT TD7 software is available in two variants: ● TD7onCPU:

The TD7onCPU software package is used on the CPU and is mandatory in all stations with TIM modules that do not have TD7onTIM. In stations with TD7-compliant TIM modules, it can be used on the CPU modules. You configure in the STEP 7 Editor in STL (Statement list), FBD (Function Block Diagram) or LAD (Ladder Logic). TD7onCPU is described in a separate section.

● TD7onTIM: The TD7onTIM software package is available only for TIM modules that are TD7onTIM-compliant (for example TIM 3V-IE) and is part of the TIM firmware. If you use TD7onTIM, little or no work memory is required on the CPU. You configure in the subscriber administration of the SINAUT ST7 configuration tool.

Note TD7onTIM cannot be used if the TIM sends or receives ST1 messages. In this case, you must use TD7onCPU

This section deals only with configuration of TD7onTIM. If the SINAUT project you are editing does not contain TD7onTIM-compliant TIM modules, you can skip this section and continue configuration with saving and generating system data. If the project you are editing contains TD7onTIM-compliant TIM modules, on which you want to configure the TD7onTIM software, you do this in the subscriber administration of the SINAUT ST7 configuration tool.

2.8.2 Basic functions and components of TD7onTIM

Basic functions and components of TD7onTIM TD7onTIM handles the sending and receiving of process data for the local CPU. Data to be sent by TD7onTIM, is read by the TIM over the backplane bus of the CPU, received data is written to the CPU. SINAUT communication makes use of SINAUT objects: Which data is to be sent or received can be configured over standardized data objects. These are collected in the TD7onTIM standard library. This library also contains the system objects with which system information is displayed and with which system functions are activated and set.



The parameter assignment for TD7onTIM is made in the subscriber administration of the SINAUT ST7 configuration tool in the following steps: ● Setting basic parameters for TD7onTIM ● Specifying the parameters specific to the destination subscribers ● Inserting system objects and assigning parameters to them ● Inserting data objects including their send and receive channels and assigning

parameters to them

The basic settings for TIM subscribers with TD7onTIM For each TIM with TD7onTIM, several settings must be made that are always required when working with TD7onTIM, for example specifying the read/write cycle. The settings are made in the basic settings for TIM subscribers with TD7onTIM.

The parameters specific to the destination subscribers Each TIM with TD7onTIM can exchange data with one or more partners, known as destination subscribers. Which subscribers in the project are suitable as destination subscribers depends on the connection configuration. Here, you specify which TIM with TD7onTIM will have a connection with which SINAUT subscriber in the network. Several settings are required for each of the possible destination subscribers that apply to data traffic between the TD7onTIM of a project and this subscriber, for example whether the subscriber expects data messages with a time stamp. This information is specified in the parameters specific to destination subscribers.

The system objects The system objects provide system-relevant information for the CPU user program. Configuration of the system objects is optional. ● The WatchDog:

The WatchDog indicates to the CPU program whether the communication between CPU and local TIM is still working; in other words, whether TD7onTIM is still reading from and writing to the memory areas of the CPU.

● The PartnerStatus: The PartnerStatus indicates to the CPU program whether communication with its partners (other ST7 CPUs or ST7cc/sc control centers) is OK or disrupted.

● The OpInputMonitor: This indicates the status of operating input to the CPU program (with command, setpoint, and parameter input).

The data objects The sending and receiving of process data is configured with the aid of standardized data objects. According to the two transmission directions, these are divided into: ● Data objects for acquiring and sending data,

Their names have the ending _S for Send.



● Data objects for receiving and outputting data, Their names have the ending _R for Receive.

In terms of the names, the data objects of TD7onTIM are identical with those of the data objects of TD7onCPU. In terms of functionality, they are compatible with each other; in other words, communication between data objects of TD7onTIM and the corresponding data objects of TD7onCPU is guaranteed. The data objects are available in a standard library and are inserted from the library into the TD7onTIM configuration. An example of a data object is Ana04W_S that organizes the transmission of 4 analog values. Each data object contains one or more send or receive channels. The number and type of send and receive channels per data object cannot be modified.

The send and receive channels The send and receive channels of the data objects are responsible for the processing of an individual process value, for example for processing and sending an analog value or receiving and outputting a message byte. The data object Ana04W_S, for example, has 4 send channels of the type send analog value.

2.8.3 Parameter assignment dialogs for TD7onTIM

Calling and appearance of the parameter assignment dialogs Information on displaying and assigning parameters with the TD7onTIM software is divided into three areas of subscriber administration: ● The directory tree in the left-hand part of subscriber administration ● The list box at the top right ● The parameter assignment window below the list box



Figure 2-59 SINAUT ST7 subscriber administration with the TIMs with TD7onTIM directory selected,

the list box and the parameter assignment window of the basic settings for TIM with TD7onTIM

You can change the size of the three windows in subscriber administration. The vertical and horizontal divisions between the windows can be moved with the mouse.

The directory tree The TD7-compliant TIM modules of a project are shown in the directory tree in the TIMs with TD7onTIM directory. If you expand the directory with the (+) symbol or double-click on the directory, the following contents are displayed: ● The All Destination Subscribers directory ● The directories of all TIMs with TD7onTIM If you expand a single TIM directory, the data objects already configured on this TIM are displayed.

The list box At the top right of the subscriber administration there is a list box that lists certain subscriber types, objects, or send/receive channels depending on what is selected in the directory tree. By successively expanding the TIMs with TD7onTIM directory, the list box displays the following content: ● The TD7-compliant TIMs of the project ● The destination subscribers with which the TD7-compliant TIMs can communicate



● The system and data objects of a TD7-compliant TIM ● The channels of a data object The SINAUT objects are displayed with the following symbols: ● Blue symbols: System objects ● Yellow symbols: Data objects

Figure 2-60 Selected data object Bin04B_R with selected channel in the list box and the parameter

assignment window of a receive channel

The parameter assignment windows In the parameter assignment windows below the list box, you set the parameters for the TD7onTIM-relevant subscribers, objects and channels. Depending on what is selected in the directory tree or in the list box, the following dialogs are displayed: ● Parameter assignment dialog of the basic parameters for a TD7-compliant TIM ● Parameter assignment dialog of a destination subscriber ● Parameter assignment dialog of a system or data object ● Parameter assignment dialog of a send or receive channel

– Send channels are displayed with an outgoing arrow. – Receive channels are displayed with an incoming arrow.



To open a parameter assignment dialog, select the relevant subscriber, object or channel in the list box. If a subscriber or object is selected in the directory tree, the parameter assignment dialog of the first object of the subscriber or the first channel of the data object is displayed.

Parameter entries To simplify data entry, the parameter assignment dialogs are not opened or closed using separate buttons or menus but are displayed automatically when a subscriber, object or channel is selected with the mouse in the list box above. The entries in the parameter assignment dialogs are not applied using a separate button, but immediately: ● When you activate or deactivate an option ● After entering data when you exit the input box with the mouse or tab key The entries are applied permanently using the Save function.



2.8.4 Basic settings for TIM subscribers with TD7onTIM To make the basic settings for the TD7 software of the individual TIM subscribers, you first select the TIMs with TD7onTIM directory in the directory tree. The list box then displays all the TD7-compliant TIM modules of the project. Below the list box, the parameter assignment dialog appears for the TIM selected either automatically or with the mouse.

Figure 2-61 Parameter assignment dialog for basic settings for TIM subscribers with TD7onTIM

The parameters of the basic settings for TIM subscribers with TD7onTIM relate to ● The configuration of the read/write cycle of the TIM and ● Checking the source address when a message is received

The read/write cycle Data to be sent by TD7onTIM, is read by the TIM over the backplane bus of the CPU and received data is written to the CPU. The TIM also writes system information to the CPU (see system objects Watchdog, PartnerStatus and OpInputMonitor) and certain data is reset; in other words, 0 is written. In the latter situation, this involves send trigger and command information that was read from the memory bit area or data blocks. TD7onTIM ensures that these are reset to 0 automatically after they have been acquired. All of these procedures take place within a defined and selectable read/write cycle.



The writing and reading of data takes place in consecutive read/write cycles. A basic cycle of the read/write cycle of TD7onTIM is made up as follows: 1. Write all pending system information (see system objects) to the CPU and reset all

currently acquired send triggers and commanded entries. If no such data is currently pending, there is no write procedure in the basic cycle.

2. Read all data of the send objects that were assigned to the fast cycle. If no objects were configured for the fast cycle, this read procedure is omitted in the basic cycle.

3. Read data from some of the send objects that were assigned to the normal cycle. How many objects per basic cycle will be read can be set by the user. Refer to the Max. read parameter below.

4. Write data of some of the currently pending receive objects. How many objects this can be as a maximum per basic cycle can be selected by the user. Refer to the Max. write parameter below. If less received data is currently pending than his permitted as maximum per basic cycle, only this subset is written in the basic cycle. If there are currently no received data from the remote partner, this write procedure is omitted in the basic cycle.

5. Cycle pause (optional) to relieve the TIM and backplane bus communication. With the Max. read and Max. write parameters and by specifying how many objects are assigned to the fast cycle, the user can determine the duration of a basic cycle. Essentially, this specifies how fast the fast cycle really is: It is identical with the duration of the basic cycle. With the default 1 for the Max. read and Max. write parameters, the basic cycle has the shortest possible duration. It must also be taken into account that the make-up of the basic cycle decides how long TD7onTIM requires to read all the data of the objects assigned to the normal cycle once. If, for example, 12 objects are assigned to the normal cycle and if Max. read is set to 2 objects per basic cycle, it takes 6 basic cycle is until all the data of the 12 objects have been read once completely from the memory areas of the CPU.

Parameters in the read/write cycle field

Name: Max. write Range of values:

1 ... 32000

Default: 1 Explanation: This is the maximum number of (different) data objects whose data is

written to the CPU per basic cycle. If there are several messages of the same receive object in the buffer, only the data of one message of this object is written per basic cycle. As information, the number of receive objects configured for the TIM in total by the user is displayed above the input box beside Number of configured receive objects.



Name: Max. read Range of values:

0 ... 32000

Default: 1 Explanation: This is the maximum number of data objects whose data is read from the

CPU per basic cycle. As information, above the input field beside Number of configured send objects, you can see how many send objects the user configured for the TIM - in the normal cycle and - in the fast cycle .

Name: Cycle pause Range of values:

0 ... 32000 [ms]

Default: 1 Explanation: This parameter specifies the duration of an optional pause between 2 basic

cycles. A pause may be necessary if communication of other modules on the backplane bus is disrupted too much by the write and read jobs between the TIM and CPU. This also applies to subscribers on the MPI bus (further CPUs or PG) if the backplane bus is implemented as a party line. By setting a suitable time for the pause, the other bus subscribers have time for their communication. Specifying a cycle pause may also be necessary to relieve the TIM itself; in other words, when it becomes clear that it has too little time for other tasks due to the fast read/write cycle.

Parameters in the Message receive area

Name: Check of source address Range of values:

Function active, function deactivated

Default: Function active Explanation: With this parameter, you specify whether or not the source address of the

sending subscriber is checked prior to accepting data from a received message. If the function is activated, all messages that do not originate from the configured partner are discarded. Note: If a data object receives messages from several partners, the check of the source address must be deactivated.



Copying basic settings to other TIMs Once the basic settings of a subscriber with TD7onTIM have been made, the settings can also be transferred to other TIMs that require the same parameters. Follow the steps outlined below: 1. Select a TIM for which you have already set the parameters in the list box. 2. Select Copy in the context menu (right mouse button). 3. Select a second TIM. 4. Transfer the parameters to this second TIM using Paste in the context menu.

2.8.5 Subscriber-specific parameters of TD7onTIM Each TIM with TD7onTIM can exchange data with one or more partners, known as destination subscribers. Which subscribers in the project are suitable as destination subscribers depends on the connection configuration. Here, you specify which TIM with TD7onTIM will have a connection with which SINAUT subscriber in the network. Several settings are required for each of the possible destination subscribers that apply to data traffic between the TD7onTIM of a project and this subscriber, for example whether the subscriber expects data messages with a time stamp. To set the parameters specific to destination subscribers, open the TD7 on TIM directory and select the All Destination Subscribers directory. The list displays all potential destination subscribers of the TD7-compliant TIM modules. These are: ● SIMATIC S7 CPU modules ● SINAUT ST7cc/sc control centers Below the list box, the parameter assignment dialog of the destination subscriber (selected automatically or with the mouse) opens.



Figure 2-62 Directory tree, list box, and parameter assignment dialog of the destination subscriber-

specific parameters of TD7onTIM for a destination subscriber

The parameters to be entered here are valid in terms of communication with the configured communication partners (destination subscribers) for all TD7-compliant TIM modules of the project. The parameter assignment dialog for the destination subscriber-specific parameters is opened and the parameters are set for every configured destination subscriber. The following destination subscriber-specific parameters are available:

Name: General request supervision time Range of values:

10 ... 32000 s

Default: 900 s



Explanation: The General request supervision time is the maximum time required by a destination subscriber to respond fully to a general request (GR). If the GR response has not arrived completely at the requesting TIM module when the supervision time has expired, a message is entered in the diagnostic buffer of this TIM module and an ID in the objects of the TD7onTIM involved. A TIM can only send requests to SINAUT stations with TD7 software; in other words, a CPU with TD7onCPU or a CPU with a local TIM with TD7onTIM. The time should be set generously. Particularly with dial-up connections, remember that the time for connection establishment is also included in the supervision time. In addition to this, on dial-up stations with messages stored in the send buffer, the GR can be further delayed because the requested messages are entered after all other messages in the send buffer.

Name: Time stamp Range of values:


Default: Function deactivated Explanation: This parameter specifies whether or not messages with a time stamp are

sent to this destination subscriber. If this is the case, the Timestamp option must be activated. TD7onTIM can send either all messages with or all messages without a time stamp to a destination subscriber. Mixing messages to a destination subscriber with and without time stamps is not possible.

Copying parameters to other destination subscribers Once the destination subscriber-specific parameters have been set for a destination subscriber, they can be transferred to other destination subscribers that require the same parameters. Follow the steps outlined below: 1. Select a destination subscriber for which you have already set the parameters in the list

box. 2. Select Copy in the context menu (right mouse button). 3. Select a second destination subscriber in the list box. 4. Transfer the parameters to this second destination subscriber using Paste in the context

menu.



2.8.6 Configuring SINAUT objects

Open in the standard library of TD7onTIM After setting the basic parameters of TD7onTIM and the destination subscriber-specific parameters, the SINAUT objects of TD7onTIM are configured. To do this, a TIM module is selected in the directory tree. If no SINAUT objects have yet been configured for the TIM (as is the case in a new project), the directory of the TIM cannot be expanded any further and the list box is empty. The standard library can be opened either using: ● The Standard library button in the toolbar ● The SINAUT / Standard Library for the TIM menu ● The F7 function key Every TIM with TD7onTIM now has the required SINAUT objects added from the standard library.

Figure 2-63 Window of the standard library of SINAUT objects for TD7onTIM



Overview of the SINAUT objects The following data objects are available for TD7onTIM:

Table 2-5 Overview of the SINAUT objects for TD7onTIM

Object type Name Explanation System objects System object WatchDog Monitoring of the CPU-TIM connection System object PartnerStatus Displays connection status for up to 8 SINAUT

subscribers System object OpInputMonitor Signals detection of hardware entries Message objects Message object for send direction

Bin04B_S Send 4 bytes of messages/binary information

Message object for receive direction

Bin04B_R Receive 4 bytes of messages/binary information

Analog value / mean value objects Analog value object for send direction

Ana04W_S Send 4 analog values (16-bit value in the INT format)

Analog value object for receive direction

Ana04W_R Receive 4 analog values (16-bit value in the INT format)

Mean value object for send direction

Mean04W_S Send 4 mean values (16-bit value in the INT format)

Mean value object for receive direction

Mean04W_R Receive 4 mean values (16-bit value in the INT format)

Counted value objects Counted value object for send direction

Cnt01D_S Send 1 counted value (32-bit SINAUT format).

Counted value object for receive direction

Cnt01D_R Receive 1 counted value (32-bit SINAUT format)

Counted value object for send direction

Cnt04D_S Send 4 counted values (32-bit SINAUT format)

Counted value object for receive direction

Cnt04D_R Receive 4 counted values (32-bit SINAUT format)

Command objects Command object for send direction

Cmd01B_S Send 1 byte commands (1-out-of-8 SINAUT format)

Command object for receive direction

Cmd01B_R Receive 1 byte commands (1-out-of-8 SINAUT format)

Setpoint/parameter objects Setpoint object for send direction

Set01W_S Send 1 setpoint (16 bits), object with 3 channels : - operating mode status local - returned value - setpoint entry

Setpoint object for receive direction

Set01W_R Receive 1 setpoint (16 bits), object with 3 channels : - operating mode local - local setpoint entry - setpoint output



Object type Name Explanation Parameter object for send direction

Par12D_S Send max. 12 double words with parameters or setpoints, object with 3 channels: - operating mode status local - returned parameters - parameter entry

Parameter object for receive direction

Par12D_R Receive max. 12 double words with parameters or setpoints, object with 3 channels: - operating mode local - local parameter entry - parameter output

Other data objects Data object for send direction

Dat12D_S Send max. 12 double words (at least 1 double word) with any information

Data object for receive direction

Dat12D_R Receive max. 12 double words (at least 1 double word) with any information

The endings _S and _R in in the object names mean Send or Receive. The functions of the individual objects are described in detail in the section on setting parameters for the send and receive channels.

Inserting objects in the project To insert new SINAUT objects in the TD7onTIM of a subscriber, follow the steps outlined below: 1. Go to the directory tree and select the TIM for which you want to configure the SINAUT

objects. 2. Open the standard library with the F7 key, the Standard library button in the toolbar or

using the SINAUT / Standard Library for the TIM menu. The library is opened in a separate window. The objects are listed with the object name and a brief object description.

3. In the standard library window, select an object with the mouse. To insert several objects at the same time, select an object and press the arrow up or down key while holding the Shift key or select distributed objects one after the other while holding down the Ctrl key. All selected objects are shown on a colored background.

4. In the standard library window, click on the Paste button or select Paste in the context menu (right mouse button). The selected objects are then added to TD7onTIM. They are all displayed in the list box. Only the data objects are displayed in the directory tree below the selected TIM.

5. You can delete an object you do not require from the TIM directory by selecting it in the directory tree or in the list box and then selecting Deletein the context menu (right mouse button).

6. Close the standard library with the Close button when you no longer require it.

Note A maximum of 100 objects can be configured per TD7onTIM.



Copying objects to other TIMs Once all the SINAUT objects for a TIM have been configured and have had then parameters assigned, you can copy the objects and the parameter assignments to another TIM in the project that requires the same or similar objects. Follow the steps outlined below: 1. Select the objects in the list box while pressing the Shift key and then press the arrow up

or down key or select the objects while pressing the Ctrl key. 2. Select Copy in the context menu (right mouse button). 3. Select another TIM in the TIMs with TD7onTIM directory. 4. Add the selected objects to this TIM with Paste in the context menu. The objects along with their entire parameter assignment are adopted by the TD7onTIM of the other TIM. In the copied object and its channels, it may be necessary to adapt the subscriber-specific parameter assignment (for example the input and output addresses). If the complete parameter assignment of TD7onTIM is required for other TIM modules, you can also transfer the entire SINAUT objects to a different TIM. Follow the steps outlined below: 1. Select a TIM in the TIMs with TD7onTIM directory. 2. Select Copy in the context menu (right mouse button). 3. Select another TIM in the TIMs with TD7onTIM directory. 4. Add all objects to the other TIM with Paste in the context menu.

2.8.7 Setting parameters for system objects After the SINAUT objects for the individual subscribers have been configured, you set the parameters for the system objects. Follow the steps outlined below: 1. Select a subscriber in the tree directory. 2. Select the required system object in the list.

The corresponding parameter assignment dialog is opened below the object list. 3. You set the parameters in this dialog.



Figure 2-64 TIM with selected system object WatchDog and the corresponding parameter

assignment dialog

The WatchDog system object The WatchDog system object can be included as an option. The WatchDog indicates to the CPU program whether the communication between CPU and local TIM is still working; in other words, whether TD7onTIM is still reading from and writing to the memory areas of the CPU. As long as communication is functioning correctly, a selectable output bit changes state at five second intervals. The constant status change can be evaluated by the CPU user program. Parameters in the Output Bit area

Name: Output bit Memory area: The following options are available:

- DB: Data block - Memory bit: Memory area - Output: Process output image (PIQ)

DB No.: Specifies the DB number in the CPU if the data block memory area (DB) was selected

Address [Byte.Bit]:

Input fields for the byte and bit number in the selected memory area

The PartnerStatus system object The optional PartnerStatus object can be used to monitor the availability of up to 8 communication partners. A partner can be an ST7 CPU or an ST7cc/sc control center to which a connection was configured. TIM modules cannot be monitored with the



PartnerStatus object. The status is made available to the CPU user program in an output byte. One bit per communication partner is reserved in the output byte to indicate the status of the respective partner: ● Status 0: Problem on partner or corresponding bit not assigned to any partner ● Status 1: Partner OK If TD7onTIM has a connection to more than 8 partners whose status needs to be monitored, the PartnerStatus system object is configured more than once.

Figure 2-65 Parameter assignment dialog of the PartnerStatus system object

Name: Status output byte Memory area: The following options are available:



Address [Byte]:

Input field for the byte number in the selected memory area

Name: Partner Explanation: In the list boxes, the 8 status bits of the output byte are assigned to the

communication partners to be monitored. The partners can be selected in the 8 list boxes. The list boxes display only the partners with which the TIM can actually communicate; in other words, to which a connection was configured.

Bit status: Status = 0: Problem on partner or bit not assigned Status = 1: Partner OK



The OpInputMonitor system object The OpInputMonitor indicates the status of operator input to the CPU (with command, setpoint, and parameter input). The current status can be displayed to the operator for each user program in a suitable form, for example using the LEDs, on an operator panel etc.

Note The OpInputMonitor system object can only be included once per TD7onTIM.

TD7onTIM should therefore have the OpInputMonitor system object added when one or more of the following objects is used with this TD7onTIM: ● Cmd01B_S (Command object for send direction) ● Set01W_S (Setpoint object for send direction) ● Par12D_S (Parameter object for send direction) The OpInputMonitor is recommended particularly when commands are entered over digital inputs, for example using buttons connected to them. This also applies to the situation when setpoint and parameter entries are transmitted as the result of the send trigger signal and when this triggering is over a digital input, for example, once again using a button. Using OpInputMonitor reduces the risk of incorrect input when the entries are made over digital inputs. For these inputs, a Minimum input time can be specified for OpInputMonitor, in other words, the button must be pressed for the minimum time. Accidental activation of a button does not then lead to unwanted command, setpoint or parameter transfer. When the minimum input time has elapsed and the button can be released, OpInputMonitor indicates this with its operator input status byte in the Input OK bit. Apart from the minimum duration, a maximum input time can also be set for digital inputs. This allows a button that is sticking or defective digital inputs that supply a permanent 1 signal to be detected in good time. Such errors are once again indicated in the operator input status byte of OpInputMonitor, in this case in the input error bit. The two times and the code bits mentioned above are relevant only for operator input over digital inputs. For all types of operator input, in other words both for input over digital inputs as well as input over the memory or data blocks, OpInputMonitor also returns the error status 1 out-of-n error. This is set when TD7onTIM has detected one of the following input errors: ● More than 1 bit was set in the input byte of the command object Cmd01B_S. To increase

reliability of command input, only one bit may ever be set with this object. If two or more bits are set at the same time, the command input is rejected

● If increased reliability is required for the input of commands, setpoints and parameters, all objects with which this data is sent should be assigned to the fast cycle. All command, setpoint and parameter objects in the fast cycle are subjected to a 1-out-of-n check; in other words, at the end of the fast cycle there is a check to make sure that there is a command, setpoint or parameter entry for only one of the acquired objects. Only then is the corresponding entry processed and transferred. If there is more than one entry, the entries are rejected. A new command, setpoint or parameter is processed only when previously no entry was acquired in at least one fast cycle.



Note If commands are entered over a memory or data byte, or a setpoint or parameter entry is enabled by a memory or data bit (over the send trigger Triggersignal), the set command bit or trigger signal is automatically reset to zero by TD7onTIM. If, however, a 1-out-of-n error is detected, these bits are not automatically reset. They must then be reset by the user or the user program.

Figure 2-66 Parameter assignment dialog of the OpInputMonitor system object

Parameter settings in the operator input status byte:

Name: Operator input status byte Memory area: The following options are available:



Address [Byte]:


Explanation: The operator input status byte is the output by of the OpInputMonitor system object. In the operator input status byte, the next 3 bits are assigned (explanation see above).

Byte assignment of the operator input status byte Bit: .7 .6 .5 .4 .3 .2 .1 .0 Status: 8 7 6 5 4 1-out-of-

n error Input error

Input OK

For value:

0 0 0 0 0 1 1 1

Unused bits are set to 0



Parameter settings in the Hardware input area:

Name: Max. Input Time Range of values:

Enter value x 1 [s] (10 corresponds to 10 seconds)

Default: 0 Explanation: Monitoring time for commands entered over hardware inputs, or setpoints

and parameters whose transmission is triggered over a hardware input. If the 1 signal is set at these hardware inputs for longer than defined in Max. Input Time, then the input error bit is set in the operator input status byte. Further hardware entries are not processed as long as the input error bit is set. The Max. Input Time is specified in seconds. A time of at least 30 seconds is recommended (entry: 30). 0 (zero) can be entered if the parameter is not required.

Name: Min. Input Time Range of values:

Enter value x 0.1 [s] (10 corresponds to 1 second)

Default: 0 Explanation: Delay time for commands entered over hardware inputs, or setpoints and

parameters whose transmission is triggered over a hardware input. The message is entered in the send buffer of the TIM only if the currently entered command, setpoint for parameter remains unchanged for the specified delay time and no other command or setpoint input is detected during this time. The Min. Input Time is specified in tenths of seconds. A time of at least 1 second is recommended (entry: 10). 0 (zero) can be entered if the parameter is not required.

2.8.8 Basic parameters of the data objects The parameters for data objects are set in two phases: 1. Setting of the basic parameters of the data objects (for example partners to which the

data of the object is sent or from which it is received) 2. Setting of the channel-specific properties for the individual send and receive channels This section first describes setting the basic parameters of the data objects. Follow the steps outlined below: 1. Select a TIM with TD7onTIM in the directory tree. 2. Select the required data object in the list box. The corresponding parameter assignment

dialog opens. 3. You set the parameters in this dialog.



Figure 2-67 Subscriber administration with the parameter assignment dialog of the basic parameters

of a data object

Parameters in the Object area

Name: Object no. Range of values:

1 ... 32000

Explanation: The source object number of this TIM module is set in the input box. The configuration tool proposes a consecutive number that can be modified. An inconsistent duplicate assignment of numbers is prevented.

Parameters in the Partner area The Available partners list box shows all the partners configured for the TIM along with their subscriber numbers and station names. The communication partners for the relevant data object are selected from this list and added to the Selected partners list.

Note All partners from which data of the object is received or to which it is sent must be added to the Selected partners list. If no partner is entered in the Selected partners list, the object is not processed.



Name: Selected partners Explanation: The Selected partners list displays the communication partners for the

relevant data object. These are selected from the Available partners list box. Partners are entered in the Selected partners list by selecting one or more (using the Ctrl key) partners in the Available partners list and clicking on the button with the arrow pointing to the right. The selected partners are then entered in the Selected partners list. The button with the double arrow is is used to enter all available partners. Partners are removed from the Selected partners list using the button with the arrow pointing left. Up to 15 partners can be configured per data object.

Name: Partner object no. Range of values:

0 ... 32000

Default: 0 Explanation: In this input box, you assign the data object to the corresponding partner

object of all selected communication partners when the partner object number is identical for all partners. Otherwise set 0 (zero). Note: There is no object no. for objects of an ST7cc/sc control center! For a send object of TD7onTIM that transfers data to ST7cc/sc, a partner object no. = 0 can be set since the specified partner object no. is not evaluated by ST7cc/sc. For a receive object of TD7onTIM that receives data from ST7cc/sc, the partner object no. = 0 must be set. After object no. = 0 for send objects: The partner object no. = 0 must be set if the object data will be sent to several partners and the receiving objects on these partners have different object numbers. If partner object no. = 0 is specified and if TD7onCPU is used on the partner, the ListGenerator must be installed on the partner. Only then can the corresponding receive object to be recognized on this partner. Partner object no. = 0 for receive objects: The partner object no. = 0 must be set in the object receives data from several partners and the sending objects on these partners have different object numbers. Note: If partner object no. is specified for at least one received object, the option Check of source address must be deactivated in the basic settings of this TD7onTIM. Otherwise, messages intended for these receive objects will be rejected.

Note With data objects of the type Command snd, Setpoint send and Parameter send, partner object no. 0 (zero) is not permitted.



The Send parameters area:

Name: Image memory Range of values:

Function active: Send using the image memory principle Function deactivated: Send using the send buffer principle

Default: In general: Function active With Cmd01B_S, Set01W_S and Par12D_S: Function deactivated and setting cannot be changed

Explanation: The basic setting for saving messages in the send buffer of the TIM prior to transmission is the image memory method set as default in the Image memory parameter. As long as a message has not been sent, the process data in the message waiting to be sent is updated by current process data if this changes. This setting is practical for most data. It ensures efficient use of memory for storing messages on the TIM and produces as little message traffic on the WAN link as possible. Generally, the default setting for the Image memory parameter only needs to be changed to the Send buffer method with a few objects whose data changes must be stored individually on the TIM and sent individually to the partner, for example alarms with a time stamp or analog values with a time stamp for entry in archives. With the Bin04B_S object, selected individual binary inputs can be transmitted using the send buffer method even if the Image memory function is active. You make this setting during the parameter assignment of the channel type Binary send in the Send buffer principle mask parameter.

Name: Conditional spontaneous Range of values:

Function active: Transmission is conditional spontaneous Function deactivated: The transmission is unconditional spontaneous

Default: Function active Explanation: If the function is activated (transmission is conditional spontaneous), the

message does not trigger connection establishment in dial-up networks. When using a dedicated lines or Ethernet, this parameter has no significance since transmission is then always immediate. If the function is deactivated (transmission is unconditional spontaneous), the message triggers connection establishment immediately in dial-up networks. In the Bin04B_S object, even if the Conditional spontaneous function is activated, selected individual binary inputs can trigger unconditional spontaneous transmission. You make this setting during the parameter assignment of the channel type Send binary value in the Alarm mask parameter.



Name: High priority Range of values:


Default: Function deactivated Explanation: Important process data can be given higher priority than the messages

waiting in the send buffer. If you activate the High priority function, the messages of this object are given a higher priority and sent before the other buffered messages. Note: In dial-up networks, the High priority function does not necessarily lead to immediate connection establishment. This happens only when the Conditional spontaneous function has been deactivated for this object.

Volatile storage mode output box: The Volatile storage mode output box indicates that a message already stored in the send buffer of the TIM will be deleted if the subscriber is not available. As long as a subscriber is disrupted, no new non-retentive messages for this subscriber can be entered in the send buffer of the TIM. The volatile storage mode applies only to the send messages of the following objects: - Cmd01B_S - Set01W_S - Par12D_S By deleting command, setpoint and parameter messages, you avoid out-of-date commands, setpoints all parameters being sent to the destination subscriber when a connection is re-established following a failure. The messages of all other send objects are not deleted when there is a connection failure and further messages can be entered in the send buffer of the TIM during a disruption.

Name: Read cycle Range of values:

1: Normal cycle 2: Fast cycle

Default: Normal cycle Explanation: Each data object that sends data must be assigned to one of the two read

cycles. The normal cycle is the most suitable selection for most process data. Data that must be acquired quickly such as alarms and pulse messages are suitable for assignment to the fast cycle. Command, setpoint and parameter objects for which a 1-out-of-n check is required, must be assigned to the fast cycle. If these objects are acquired in the normal cycle, they are not included in the 1-out-of-n check. All send channels of a data object are included in the same read cycle. The parameters of the read/write cycle themselves are set in the basic settings of TD7onTIM.



2.8.9 Channel overview and functions of channel parameter assignment

Overview of the channel types Each data object has a defined number of channels with default parameters. The number of channels and the data type cannot be changed for an individual data object. Apart from the setpoint and parameter objects, all data objects have one or more channels of the same type. The channel types differ in the transmission direction relative to the communication partner and fall into the two classes Send and Receive channels: ● Send channels for the send data function:

– Binary send – Analog send – Data send – Mean value send – Counted value send – Command send – Setpoint send

● Receive channels for the receive data function: – Binary receive – Analog receive – Data receive – Mean value receive – Counted value receive – Command receive – Setpoint receive

Dialogs for setting channel parameters To set the parameters for the channels, you select the data object of a TIM with TD7onTIM in the directory tree. The list box displays the channels of this object with the channel name and channel type. If channels have already had parameters set, the input or output address is displayed in the list. Below the list box, there is a parameter assignment dialog for the channel selected automatically or with the mouse in the list box.



Figure 2-68 Selected object Bin04B_R with Binary receive channel selected in the list box and its

parameter assignment dialog

Activating channels Prior to parameter assignment, the send and receive channels are not yet active, the input boxes in the dialog are disabled. Each required channel must be enabled in its parameter assignment dialog using the Channel active option. If certain channels of a data object are not required, they can be ignored. If users are not sure whether they actually require a channel that has already had parameters set, or when they want to disable a channel later (perhaps temporarily), they can deactivate each individual channel here without losing the parameter settings.

Copying channels To simplify parameter assignment, channels along with their parameter assignment can be copied. If a data object requires more than one channel with the same parameter assignment (except for the input or output address) and if the parameter settings have been completed for one channel, this channel along with its parameters can be copied. Follow the steps outlined below: 1. Select a channel in the list box. 2. Select Copy in the context menu (right mouse button).



3. Select a different channel of the same object or the channel of another data object of the same type.

4. Insert the channel with its parameters using the Paste context menu (right mouse button). The selected channel is overwritten by the channel and its parameters.

Note When you copy channels, the channel you are copying is not added to the existing channels since the number of channels is fixed per data object. The channel selected prior to paste is overwritten by the copied channel and its parameters.

2.8.10 Mandatory parameters of the send channels During the parameter assignment of each send channel, you must first set the mandatory parameters Input address and Send trigger.

Figure 2-69 Parameter assignment dialog of a send channel based on the example of Counted value

send

The input address Data transferred from TD7onTIM to a communication partner is first read from the work memory of the CPU. For each send channel, the source address (input address) must be specified in the relevant memory area of work memory on the local CPU module from which the data will be read.



Name: Input address Memory area: The following options are available for the source address:

- DB: Data block - Memory bit: Memory area - Input: Process input image (PII)

Data type: The output box displays the default data format of the corresponding channel type: - Binary send: BYTE - Analog send: WORD - Data send: DWORD (double word) - Mean value send: WORD - Counted value send: WORD - Command send: BYTE - Setpoint send (object Set01W_S): WORD - Setpoint send (object Par12D_S): DWORD


Address [Byte]:

Input field for the byte number in the selected memory area. For data types involving more than one byte (WORD, DWORD), the least significant byte number must be entered as in STEP 7.

Number: The number of double words included in the array (maximum 12). The parameter is available only with the following channel types: - Data send with the object Dat12D_S - Setpoint send with object Par12D_S The parameter is explained along with these object-specific channels.

Note Only the specified address areas can be read by TD7onTIM. Data from other areas, for example analog values acquired over peripheral input words (PIW) must be mapped to the bit memory or data block area by the user program.

The send trigger The second mandatory parameter that must be set for send channels specifies when the data will be sent. This setting is made in the Send trigger area. Four options are available for the send trigger. For each channel, you can configure a single option or a combination of different options.

Note The send trigger can be set individually for each channel. If an object has more than one channel, remember that the activation of the send trigger of one of the object channels will transmit all channels of the data object. Since the various options of the send trigger must be activated alternatively or additionally with most channel types, the parameter setting should selected to produce practical results.



Name: Send at change of Range of values:

In general: 0 ... 32767 Channel type Command send (objectCmd01B_S): 0 or 1 Channel type Data send (object Dat12D_S): 0 or 1 Channel type Setpoint send (object Set01W_S or Par12D_S) 0 or 1

Defaults: - for binary value, counted value, data and command channels: 1 - For mean value and setpoint channels: 0 - For analog value channels: 270 (1% of the raw value of S7 analog input modules, 27648 = 100%)

Explanation: The value must be entered (as an integer) in the input field by which the process value must change so that it is transferred again. If you enter 0 (zero), the function is deactivated.

The Time trigger area provides two alternatives Time of day or Time scheme. A combination of both is not possible. The time trigger send trigger is activated with the Active option.

Name: Time of day Range of values:

Time of day (hour and minute)

Default: Function not active Explanation: If the send trigger is triggered by a time of day, the data is read out at the

selected time of day and a message is sent.

Name: Time scheme Range of values:

Time scheme (hour, minute or second)

Default: Function not active with the exception of Mean value send (Mean04W_S): Function active, time scheme: 15 minutes

Explanation: If the send trigger is triggered by a time scheme, the data is read out at the selected time interval and a message is sent.

If the time trigger is, for example, initially set to time of day and then to time scheme, the previously set times are replaced by dashes (- - -). The Trigger signal area includes the option of an external send trigger that can be activated with the Active option.

Name: Trigger signal Memory area: The following options are available for the source address:


Default: Function deactivated




Address [Byte]:


Explanation: If a trigger signal is specified, the data of the object is transferred when the trigger signal changes from 0 to 1. If the trigger signal is a memory or data bit, it is automatically reset after it has been read. The reset can, if necessary, be evaluated by the user program, for example to display that the message was triggered.

2.8.11 Mandatory parameters of the receive channels When you set parameters for each receive channel, the Output address parameter must be set as a mandatory parameter. This is the address in the memory area of the local CPU to which the received data will be written by TD7onTIM. As an example of the Output address area, we have taken the parameter assignment dialog of the Binary receive channel type.

Figure 2-70 Parameter assignment dialog of the Binary receive receive channel

The output address The destination address in the memory area of the CPU is set in the Output address area by specifying the following information:



Name: Output address Memory area: The following options are available for the destination address:


Data type: The output box displays the default data format of the corresponding channel type: - Binary receive: BYTE - Analog receive: WORD - Data receive: DWORD (double word) - Mean value receive: WORD - Counted value receive: DWORD - Command receive: BYTE - Setpoint receive (object Set01W_R): WORD - Setpoint receive (object Par12D_R): DWORD


Address [Byte]:

Input field for the byte number in the selected memory area. For data types involving more than one byte (WORD, DWORD), the least significant byte number must be entered as in STEP 7.

Number: The number of double words included in the array (maximum 12). The parameter is available only with the following channel types: - Data receive with object Dat12D_R - Setpoint receive with object Par12D_R The parameter is explained along with these object-specific channels.

Note Only the specified address areas can be written by TD7onTIM. Data for other areas, for example analog values output over peripheral output words (PQW) must be mapped over the bit memory or data block area by the user program.

Apart from these generally valid channel parameters, most send and receive channels have specific parameters that are described below based on the individual data objects.

2.8.12 Specific channel parameters of the data objects

Object type Bin04B_S ● Channel type: Binary send:

The Masks field provides three options for transmitting binary value messages. You can specify bit-by-bit whether certain bits do not trigger message transmission or which bits trigger a different type of transmission than was specified in the basic parameters of the object. This setting is made in the Masks area.



Figure 2-71 The Masks area in the parameter assignment dialog of the Binary send channel type

Name: Alarm mask Range of values:

Mask in hexadecimal format

Default: 00 (hex) Explanation: Changes in masked bits in the byte of the Binary send channel cause an

unconditional spontaneous message transmission. Changes from 0 to 1 and from 1 to 0 are evaluated. The corresponding bits are masked in hexadecimal format. The alarm mask is only practical when the object is transmitted over a dial-up network and the option Conditional spontaneous was activated in the basic parameters of the object.

Name: Send buffer principle mask Range of values:


Default: 00 (hex) Explanation: Changes in masked bits in the byte of the Binary send channel cause a

message transmission according to the send buffer principle. Changes from 0 to 1 and from 1 to 0 are evaluated. The corresponding bits are masked in hexadecimal format. TheSend buffer principle mask is only practical when the option Image memory was activated in the basic parameters of the object.

Name: Disable mask Range of values:


Default: 00 (hex) Explanation: Masked bits in the byte of the Binary send channel are ignored when

changes are checked. This means that changes to the masked bits for this channel do not trigger message transmission. A masked bit always has the value 0 in the message. The corresponding bits are masked in hexadecimal format.



The bits are masked as shown in the following example in which the hexadecimal value A3 is entered in the input field of the parameter assignment dialog. The bits with the value 1 are masked; in other words bits no. 0, 1, 5 and 7 cause the relevant function in the described masks.

Byte assignment Bit: .7 .6 .5 .4 .3 .2 .1 .0 Masked 1 0 1 0 0 0 1 1 Hex mask A 3

Object type Bin04B_R ● Channel type: Binary receive:

This channel type has no specific parameters.

Object type Ana04W_S ● Channel type: Analog send:

The following parameters are available in the Processing parameters area:

Name: Unipolar analog value Range of values:


Default: Function active Explanation: If the function is activated, negative analog values are corrected to the

value zero. The error ID 8000h (-32768), that is displayed, for example, if there is a wire break in life zero inputs, is nevertheless transmitted.

Name: Smoothing factor Range of values:

1 = none, 4 = weak, 32 = medium, 64 = strong

Default: 1 Explanation: Using the smoothing factor, quickly fluctuating analog values can be

smoothed to a greater or lesser extent depending on the parameter setting. It may then be possible to set a lower value for the send trigger Send at change of. The smoothing factors are identical to the smoothing factors that are configured for some S7 analog input modules. The smoothing in the channel functions according to the same formula as on an input module:

1y x k yk

nn n

=+ − −( )1

where yn = smoothed value in the current cycle n

yn = acquired value in the current cycle n k = smoothing factor



Name: Fault suppression time Range of values:

0 ... 32767 [s]

Default: 0 Explanation: Transmission of an analog value located in the overflow or underflow range

(7FFFh or 8000h) is suppressed for the time period specified here. The value 7FFFh or 8000h is only sent after this time has elapsed, if it is still pending. If the value returns to below 7FFFh or above 8000h again before this time elapses, it is immediately sent again as normal. The suppression time is started again for the full duration the next time 7FFFh or 8000h is received. This is typically used for temporary suppression of current values that may occur when powerful motors are started. The analog input may exceed several times the maximum range under some circumstances. Suppression prevents these values from being signaled as faults in the control center system. The suppression is adjusted to analog values that are acquired by the S7 analog input modules as raw values. These modules return the specified values for the overflow or underflow range for all input ranges (also for life-zero inputs). When the user provides specific values, fault suppression is only possible if these also adopt the values 7FFFh or 8000h when the permitted ranges are exceeded. If this is not the case, the parameter does not need to have a value entered.

Object type Ana04W_R ● Channel type: Analog receive:


Object type Dat12D_S ● Channel type: Data send:

With the channel type Data send, a data field of a maximum of 12 double words can be sent. This setting is made with the Number parameter in the Input address area.

Figure 2-72 Section of the parameter assignment dialog of the channel type Data send with the

Number parameter



Name: Number Range of values:

1 ... 12

Default: 12 Explanation: The parameter decides the size of the data field in double words. This

allows the message length to be reduced to the length actually required. This saves transmission time.

Object type Dat12D_R ● Channel type: Data receive:

With the channel type Data receive, a data field of a maximum of 12 double words can be received. This setting is made with the Number parameter in the Output address area.


1 ... 12

Default: 12 Explanation: The parameter specifies the size of the data field in double words that must

be identical to the data field size of the sending partner object Dat12D_S.

Object type Mean04W_S ● Channel type: Mean value receive:

This channel type has no specific parameters. The duration of the interval for forming an individual mean value is determined by the Time trigger specified for the Mean value send channel. If the mean value is to be entered in an archive in the control center, the Mean04W_S object should be transmitted according to the send buffer principle.

Object type Mean04W_R ● Channel type: Mean value receive:


Object types Cnt01D_S and Cnt04D_S The object type Cnt01D_S sends a counted value, Cnt04D_S sends four counted values. ● Channel type: Counted value send:

This channel type has no specific parameters. The counted value read in from the CPU must be made available by a software counter of the CPU in the WORD format. In TD7onTIM, the value originating from the CPU counter is compared with the value last read from the object and the difference is added to the SINAUT counted value maintained internally in the Cnt01D_S or Cnt04D_S object. An overflow of the CPU counter at 65535 is detected by the counted value object and taken into account. The internally formed SINAUT counted value is stored by TD7onTIM in DWORD format and transmitted.



Object types Cnt01D_R and Cnt04D_R The object type Cnt01D_R receives a counted value, Cnt04D_R receives four counted values. ● Channel type: Counted value receive:

The SINAUT counted value received from the partner object is compared with the last received counted value and the difference is added to the value at CountedValueOutput. The value is output in DWORD format so that the maximum displayable counted value is 2,147,483,647. If the maximum value that can be represented is exceeded, the counted value starts again at 0 and counting continues in the positive numeric range. Reset: If the counted value at CountedValueOutput is reset to zero, when the next counted value is received, the difference is added to zero. To reset, a bit in a memory area of the CPU is defined in the Reset field. The reset takes place on a signal edge change from 0 to 1.

Name: Reset Memory area: The following options are available for the address:


Default: Function inactive DB No.: Specifies the DB number in the CPU if the data block memory area (DB)

was selected Address [Byte.Bit]:

Input fields for the byte and bit number in the selected memory area

Object type Cmd01B_S If increased reliability is required for the input of commands, setpoints and parameters, all objects with which this data is sent should be assigned to the fast cycle. All command, setpoint and parameter objects in the fast cycle are subjected to a 1-out-of-n check; in other words, at the end of the fast cycle there is a check to make sure that there is a command, setpoint or parameter entry for only one of the acquired objects. Only then is the corresponding entry processed and transferred. If there is more than one entry, the entries are rejected. A new command, setpoint or parameter is processed only when previously no entry was acquired in one fast cycle. The error status is indicated in the output byte of the OpInputMonitor system object using the 1-out-of-n error bit. ● Channel type: Command send:

Only one input may be set at the same time for command input. This is verified by the 1-out-of-8 check. If a 1-out-of-8 error is detected, the entered commands are not processed further. A new command is only processed again when there was previously no command pending for one read cycle. The error status is displayed in the output byte of the OpInputMonitor system object in bit 2 (1-out-of-n error). The bit remains set until the error is corrected. If the command is entered over digital inputs, for example using a button connected to them, the button must remain pressed until it is acquired by TD7onTIM. The output byte of the OpInputMonitor system object indicates when the command has been acquired in the Input OK bit. OpInputMonitor also takes into account any minimum input time that has been set for it; in other words the button must be pressed at least as long as this selected time. Only then is Input OK indicated.



If the commands are input over memory or data bits, the set bit is automatically reset by TD7onTIM as soon as it is acquired. Here, there is noInput OK display. Successful acquisition can, however, be recognized indirectly because the command bit was reset. Special feature of send trigger: For the Send at change of send trigger, only the values 0 and 1 can be set. Values higher than 1 are meaningless for command input. Disable mask: For the Command send channel type, individual bits can be masked for command acquisition. You do this in the Disable mask:

Name: Disable mask Range of values:


Default: 00 (hex) Explanation: Masked bits in the byte of the Command send channel are ignored when

changes are checked. This means that changes to the masked bits for this channel do not trigger message transmission. A masked bit always has the value 0 in the message. The corresponding bits are masked in hexadecimal format.

The bits are masked as shown in the following example in which the hexadecimal value A3 is entered in the input field of the parameter assignment dialog. The bits with the value 1 are masked; in other words bits no. 0, 1, 5 and 7 are ignored in command acquisition.

Byte assignment Bit: .7 .6 .5 .4 .3 .2 .1 .0 Masked 1 0 1 0 0 0 1 1 Hex mask A 3

Object type Cmd01B_R ● Channel type: Command receive:

Name: Command output time Range of values:

0 ... 50 [s x 0.1] (5 = 0.5 seconds)

Default: 5 Explanation: This is the command output time for the command outputs of the channel.

When the set time has elapsed, the command output is reset again by TD7onTIM. The command output time applies to all 8 command outputs of the Command receive channel. If the command output time is set to 0, a set command output is not reset by TD7onTIM. Resetting the command output to zero must then be implemented in the user program.



Object type Set01W_S, the setpoint object for the send direction The object type Set01W_S sends 1 setpoint. The setpoint assignment status 'local' and the locally valid setpoint can also be indicated by this object. If increased reliability is required for the input of commands, setpoints and parameters, all objects with which this data is sent should be assigned to the fast cycle. All command, setpoint and parameter objects in the fast cycle are subjected to a 1-out-of-n check; in other words, at the end of the fast cycle there is a check to make sure that there is a command, setpoint or parameter entry for only one of the acquired objects. Only then is the corresponding entry processed and transferred. If there is more than one entry, the entries are rejected. A new command, setpoint or parameter is processed only when previously no entries were acquired in one fast cycle. The error status is indicated in the output byte of the OpInputMonitor system object using the 1-out-of-n error bit. If a setpoint entry is transmitted as a result of the Trigger signal send trigger, and if this is triggered over a digital input, for example by a connected button, the button must remain activated until the signal has been acquired by TD7onTIM. The operator input status byte of the OpInputMonitor system object indicates whether the entry has been acquired using the Input OK bit. OpInputMonitor takes into account any minimum input time; in other words, the button must be kept pressed for at least as long as the time set with this parameter. Only then is Input OK indicated. If the trigger signal is a memory or data bit, the bit is automatically reset by TD7onTIM as soon as it is acquired. Successful acquisition can be recognized indirectly because the trigger bit was reset. ● Channel name: LocalOperation - Setpoint assignment status 'local'

(Channel type: Binary receive): The return message from the partner object that the local object is set to 'local operation' is sent over this channel. The LocalOperation channel is used only for signaling. It can but does not necessarily need to be used. A setpoint can also be set locally at the partner object that receives the setpoint. As information, the input parameter Local can then be set to 'local' locally on the partner object. The current status of the Local input parameter is reported by the partner object and displayed here at the LocalOperation output. An interlock of the remote and local setpoint assignment must be implemented by the user program; in contrast to TD7onCPU, in TD7onTIM, this parameter (or the Local parameter of the partner object Set01W_R) does not cause an interlock with local setpoint assignment. After the local or the partner CPU has started up or after the return of the connection, a general request makes sure that the current valid status of the partner is indicated in LocalOperation. If you do not require the parameter, leave it inactive. This channel type has no specific parameters.

● Channel name: ReturnedSetpoint - returned setpoint (channel type: Data receive): In TD7onTIM, the partner object receiving the setpoint reports back the currently valid local setpoint when the LocalSetpointInput channel is set there. This returned value is displayed at the ReturnedSetpoint output. If the partner object is set to 'local' and if a new entry is made there, the setpoint changed there is indicated at ReturnedSetpoint if the Local channel is set on the partner object. After the local or partner CPU has started up or after return of the connection, an automatic general request makes sure that the currently valid local setpoint is indicated at ReturnedSetpoint.



If you do not require the parameter, leave it inactive. This channel type has no specific parameters.

● Channel name: SetpointInput - Setpoint input (channel type: Setpoint send): The setpoint to be sent to the partner object is entered over this channel. This channel type has no specific parameters.

Object type Set01W_R, the setpoint object for the receive direction The object type Set01W_R receives 1 setpoint. The object also has an input over which the locally valid setpoint can be returned. ● Channel name: Local - Setpoint assignment 'local'

(Channel type: Message send): The information as to whether the locally set setpoint or the remote setpoint is valid can be signaled over this input. The current status of the Local input and a copy of the current local setpoint is returned (mirrored) to the partner. A setpoint sent by the remote partner (for example, master station) can also be accepted when Local is set. In contrast to TD7onCPU, the Local cannel here is only for information. An interlock with the remote setpoint assignment must be implemented in the user program. If you do not require the parameter, leave it inactive. This channel type has no specific parameters.

● Channel name: LocalSetpointInput - Local setpoint input (channel type: Data send): A locally active setpoint can be returned over the LocalSetpointInput input to the send block. If you do not require the parameter, leave it inactive. This channel type has no specific parameters.

● Channel name: SetpointOutput - Setpoint output (channel type: Setpoint receive): The setpoint sent by the partner object or entered locally at LocalSetpointInput is output at SetpointOutput. This channel type has no specific parameters.

Object type Par12D_S, the parameter object for the send direction The object type Par12D_S sends 1 to 12 parameters. The setpoint assignment status 'local' and the locally valid parameters can also be indicated by this object. If increased reliability is required for the input of commands, setpoints and parameters, all objects with which this data is sent should be assigned to the fast cycle. All command, setpoint and parameter objects in the fast cycle are subjected to a 1-out-of-n check; in other words, at the end of the fast cycle there is a check to make sure that there is a command, setpoint or parameter entry for only one of the acquired objects. Only then is the corresponding entry processed and transferred. If there is more than one entry, the entries are rejected. A new command, setpoint or parameter is processed only when previously no entry was acquired in one fast cycle. The error status is indicated in the output byte of the OpInputMonitor system object using the 1-out-of-n error bit.



If a parameter entry is transmitted as a result of the Trigger signal send trigger, and if this is triggered over a digital input, for example by a connected button, the button must remain activated until the signal was acquired by TD7onTIM. The operator input status byte of the OpInputMonitor system object indicates whether acquisition was successful in the Input OK bit. OpInputMonitor also takes into account any minimum input time that has been set for it; in other words the button must be pressed at least as long as this selected time. Only then is Input OK indicated. If the trigger signal is a memory or data bit, the bit is automatically reset by TD7onTIM as soon as it is acquired. Successful acquisition can be recognized indirectly because the trigger bit was reset. ● Channel name: LocalOperation - Setpoint assignment status 'local'

(Channel type: Binary receive): The return message from the partner object that the local object is set to 'local operation' is sent over this channel. The LocalOperation channel is used only for signaling. It can but does not necessarily need to be used. A parameter can also be entered locally at the partner object that receives the parameter. As information, the input channel Local can then be set to 'local' locally on the partner object. The current status of the Local input channel is reported by the partner object and displayed here at the LocalOperation output. An interlock of the remote and local setpoint assignment must be implemented by the user program; in contrast to TD7onCPU, in TD7onTIM, this parameter (or the Local parameter of the partner object Par12D_R) does not cause an interlock with local setpoint assignment. After the local or the partner CPU has started up or after the return of the connection, a general request makes sure that the current valid status of the partner is indicated in LocalOperation. If you do not require the parameter, leave it inactive. This channel type has no specific parameters.

● Channel name: ReturnedParameter - Returned parameters (Channel type: Data receive): In TD7onTIM, the partner object receiving the parameter values reports back the currently valid local parameter values when the LocalParameterInput channel is set there. These returned values are displayed at the ReturnedParameter output. If the partner object is set to 'local' and if a new entry is made there, the parameters changed there are indicated at ReturnedParameter if the Local channel is set on the partner object. After the local or partner CPU has started up or after return of the connection, an automatic general request makes sure that the currently valid local parameters are indicated at ReturnedParameter. If you do not require the parameter, leave it inactive. This channel type has no specific parameters.

● Channel name: ParameterInput - Parameter input (Channel type: Setpoint send): The parameters to be sent to the partner object are entered over this channel. The content per double word can be a value in double word format (DWORD), however, a mixture of other formats is permitted if they in turn result in a double word, for example - 4 bytes or - 2 words or - 2 bytes plus 1 word. The number of required double words, in other words the size of the data field is set in the Number input box.




1 ... 12

Default: 12 Explanation: The parameter decides the size of the data field in double words. This

allows the message length to be reduced to the length actually required. This saves transmission time.

Object type Par12D_R, the parameter object for the receive direction The Par12D_R object type receives 1 to 12 parameters, for example setpoints. The object also has an input channel over which the locally valid parameters can be returned. ● Channel name: Local - Parameter assignment 'local'

(Channel type: Binary value send): The information as to whether the locally set parameters or the remote parameters are valid can be signaled over this input. The current status of the Local input and a copy of the local parameters is returned (mirrored) to the partner. A parameter record send by the remote partner (for example, master station) can also be accepted when Local is set. In contrast to TD7onCPU, the channel here is only for information. An interlock with the remote setpoint assignment must be implemented in the user program. If you do not require the parameter, leave it inactive. This channel type has no specific parameters.

● Channel name: LocalParameterInput - Local parameter input (Channel type: Data send): Local active parameters can be returned to the send block over the LocalParameterInput input. The data area corresponds to the data area set for ParameterOutput of the same object. If you do not require the parameter, leave it inactive. This channel type has no specific parameters.

● Channel name: ParameterOutput - Parameter output (Channel type: Setpoint receive): The parameters sent by the partner object or enter the local at LocalParameterInput are output at ParameterOutput. The data area can vary length between 1 and 12 double words. The content per double words can be a value in double word format, however, a mixture of other formats his permitted if they in turn result in a double word, for example - 4 bytes or - 2 words or - 2 bytes plus 1 word.


1 ... 12

Default: 12 Explanation: The parameter decides the size of the ParameterOutput data field in

double words. This must be identical to the data field size of the sending partner object Par12D_S.



2.8.13 Synchronization of the CPU time with TD7onTIM

Time information provided by the TIM The synchronization of the time on stations is selected in HW Config in the properties dialog of the TIM, Time Service tab (refer to the section " Setting TIM module parameters (Page 28)"). If the "TD7onCPU" TD7 software is running on an Ethernet TIM (TIM 3V-IE variant or TIM 4R-IE) and the TIM's time is synchronized by a master computer, the TIM acts as time master and synchronizes its local CPU (using FC TimeTask) over the backplane bus. If the "TD7onTIM" TD7 software is running on an Ethernet TIM and the time on the TIM is synchronized by a master computer, the TIM makes the time available to its local CPU at the I/O addresses. The CPU user program can then read and evaluate the time there. The I/O addresses of the CPU available for the date and time information from the TIM are set in HW Config in the properties dialog of the TIM, Addresses tab (refer to the section "Setting TIM module parameters (Page 28)"). The time information of a time-synchronized TIM module with TD7onTIM is stored in 8 bytes of the peripheral "inputs". The time information has an offset of 8 bytes from the base value of the inputs. The following table shows the assignment of the 8 bytes of time information.

Time-of-day format

Table 2-6 Format of the time information in the inputs of the I/O addresses of the TIM

Byte No. Offset [bytes]

Significance High nibble Low nibble

Value Range of values

(decimal)

Value Range of values

(decimal) 1 +8 Year tens 0...9 ones 0...9 2 +9 Month tens 0...9 ones 0...9 3 +10 Tag tens 0...9 ones 0...9 4 +11 Hour tens 0...9 ones 0...9 5 +12 Minute tens 0...9 ones 0...9 6 +13 Second tens 0...9 ones 0...9 7 +14 Millisecond hundreds 0...9 tens 0...9 8 +15 Millisecond ones 0...9 Status bit coded

Meaning of the entries in the table: ● Offset: Offset to the base value of the peripheral inputs in bytes ● High nibble: Bits 4 -7: ● Low nibble: Bits 0-3 ● Value: Position of the relevant number

– Year, month, day, hour, minute and second are two-digit (tens + ones) – Milliseconds are three-digit (hundreds + tens + ones)

● Status: Status of the time information

Configuration software for SINAUT ST7 2.9 Saving and generating system data


Format of "Status" The status of the time information is available in the four bits of the low nibble of byte 8. The following table shows the meaning and the values of the status.

Table 2-7 Status bits of the time (low nibble of byte no. 8)

Bit No. 3 2 1 0 Significance Prewarning bit Not defined Daylight saving

time (DS), standard time (ST)

Validity of the time

Value 0 = - 1 = prewarning: Changeover at the next full hour (DS -> ST or ST -> DS)

0 = ST 1 = DS

0 = invalid 1 = time valid

Initial setting of the time The user program that reads out the time on the CPU should only do this when the validity bit is set. This is the case as soon as the TIM is synchronized the first time, either by the time master in the SINAUT network or by the PG.

Note If the time on the TIM was set from a PG, this is always indicated as standard time (status bit 1 has the value "0").

2.9 Saving and generating system data When including ST1 networks in SINAUT ST7 projects, prior to saving the system data, you should check whether any further configuration steps are necessary for the ST1 subscribers. You will find information on this in the ST1 configuration rules.

2.9.1 Saving subscriber data You save the data from subscriber administration using the Save button in the toolbar or with the SINAUT / Save menu. The Options dialog opens in which you specify the scope of the system data to be saved, process and prepared.



Figure 2-73 The Options dialog after selecting the Save function

The Options dialog provides the following convenient functions in the Generation / Compilation options area: ● Generate System data blocks for TIMs and CPUs ● Generate SINAUT TD7 source files for CPUs The other options relate to the scope of system data generation ● for all CPUs or ● for selected CPUs (selected in the subscriber list) The third option relates to generating ● Subscriber number as comment for stations, CPUs and TIMs The convenient functions described below represent the automation of several steps in the STEP 7 system. These functions always relate to all SINAUT networked subscribers; in other words, to subscribers involved in at least one SINAUT connection. Regardless of the selected generation options, the internal data is saved and a consistent version is always available later. After saving the internal data, a consistency check determines whether the user data is free of errors. If this is the case, the required functions are executed.



If problems are detected during the consistency check, the functions are not executed. An error list is displayed as well as a message indicating the functions that have not been executed. As soon as the generation has been completed successfully, this is indicated by a status dialog.

Figure 2-74 Status dialog after saving and generating the system data

2.9.2 Generating system data blocks All the parameters of the TIM module from the hardware setting to information on communication partners or local connections are packed in system data blocks (SDBs). SDBs with numbers starting at 1000 are used. If S7-homogeneous connections (communication block connections) are used for communication between TIM and TIM or between TIM and CPU, their data is packed in SDBs starting at no. 700. If the Generate System data blocks for TIMS and CPUs option is selected in the Options dialog, this system data is saved for all the SINAUT-networked TIM and CPU modules in the subscriber list and saved in the offline data management.

Note The SDBs must be transferred to the modules either in the SIMATIC Manager or using the SINAUT Diagnostics and Service tool.



2.9.3 Compiling SINAUT TD7 blocks for the CPU The following descriptions of the TD7 software relate only to the TD7 software for the CPU. If the Compile SINAUT TD7 source files for CPUs option is selected in the Options dialog, several compile functions will be activated for all SINAUT-networked CPU modules or only for the CPU modules selected in the subscriber list. These compilation functions include: ● Entry of dynamic data for the SINAUT TD7 software in the form of data blocks in the

source file and generation of symbolic entries for the communication DBs. ● Entry of SINAUT TD7 basic blocks that do not exist in the source file or of blocks that

exist in a version earlier than or equal to the library version. ● Entry of CPU-specific SINAUT TD7 blocks in the source file according to the user

selection (CPU-specific blocks) ● Adoption of all the entries for SFCs or SFBs from the symbol table of the SINAUT TD7

library in all CPU modules involved if they do not already exist there. ● Synchronization of the time stamps of the compiled blocks with those of the library blocks

to prevent time stamp conflicts in the TD7 section. The compilation functions described create the corresponding ST7 blocks as a source file and store the source file in the Sources directory of the relevant CPU. The source file created in this way is then compiled and the blocks entered in the block directory.

Note Only for installations with - SINAUT TD7 library lower than version 2.0 and - SINAUT configuration software lower than version 2.0: If you want to change the STEP 7 user interface to English (in the SIMATIC Manager, Options/Settings menu), the Mnemonic option must not be changed to IEC! This must remain set to SIMATIC. Otherwise there will be compilation errors when generating the SINAUT program!

Dynamic data All dynamic data required by the SINAUT TD7 software for the CPU is stored in the following data blocks: ● 1 DB BasicData ● n communication DBs ● m SMS data DBs The quantity and numbers of the DBs are preset by the system. The numbers of the communication DBs as well as the quantity and numbers of the SMS data DBs can be modified in the DB configuration or SMS configuration tabs of the Properties of subscriber dialog that can be opened with the Properties context menu of the CPU modules in the subscriber list.



Basic blocks When you compile for a CPU, a check is made to determine whether all the blocks are present that are required for the SINAUT ST7 software to run. The basic blocks are:

Table 2-8 Basic blocks of TD7onCPU

Block name Block type Default block number SubscriberObject UDT UDT127 ConnectionDescription UDT UDT126 Bcom FB FB127 Xcom FB FB126 Pcom FB FB125 SMS_Ctrl * FB FB124 BasicTask FC FC127 Search FC FC126 Diagnose FC FC125 Distribute FC FC124 Create FC FC123 Startup FC FC122

* Only if SMS messages were configured. For each block there is a check to determine the following ● whether a symbol table entry exists for it and if it does ● whether the block exists in the user program If there is no symbol table entry, a free block number for the relevant type is searched for, a suitable entry made in the symbol table and the block is entered in the source file for the current CPU. If a symbol table entry already exists, but the corresponding block does not exist or only in a version lower than or equal to the library version, there is only an entry made in the source file. In both cases, the compilation results in an executable TD7 program in the block directory. The selected sequence also ensures that any blocks that have been removed are always added again.

CPU-specific blocks For all the blocks required dependent on the configuration, users can have them copied to the relevant CPU automatically from the SINAUT TD7 master source file. This function is controlled by the symbol table in the relevant CPU. The user enters the required SINAUT TD7 blocks there. If, during compilation, it is determined that ● a symbol table entry exists for a single block, ● this block, however, does not exist in the user program of the CPU, This block will be included in the generated source file.



The user can use the symbol table as a list of requirements. This makes it unnecessary to put together the CPU program by copying source files or blocks. You will find an overview of the blocks generated in this way either in the SINAUT TD7 documentation, in the SINAUT TD7 master source file or in the symbol table of the SINAUT TD7 library.

Further user activities The user now only needs to call FC BasicTask in OB1 and FC Startup in OB100 to activate the basic functionality of SINAUT TD7.

Note For more detailed information on this and setting parameters for the data messages, refer to the description of the TD7onCPU software package.

With the generation/compilation functions, the user can also completely recompile the SINAUT program with the block numbers stored in the symbol table by deleting all SINAUT blocks in the user program and recompiling the source file.

2.9.4 Creating SINAUT subscriber numbers as comments To make the subscriber numbers that are important for SINAUT communication visible in the SIMATIC Manager or in the hardware configuration, subscriber administration allows you to enter the subscriber number of SINAUT-networked components in the comment field of the properties. The function is activated by selecting the option Subscriber number as comment for stations, CPUs and TIMs in the Options dialog when you call the Save function in the Options dialog. With the following subscribers networked over SINAUT, the subscriber number is entered in the comment bar of the SIMATIC Manager: ● Stations: ● CPU modules ● TIM modules ● Third-party stations The comments are visible in the SIMATIC Manager when you select the View / Details menu. The TIM modules are visible after expanding the tree structure and selecting a station.

Note Creating the subscriber number when generating the system data overwrites comments previously entered in the network configuration without any possibility of restoring them.

Configuration software for SINAUT ST7 2.10 SINAUT ST1 - Configuration Overview


2.10 SINAUT ST1 - Configuration Overview

2.10.1 Differences between SINAUT ST1 and SINAUT ST7 The behavior of ST7 TIM modules in ST1 networks described below is caused by the following:

ST1 installations: ● In ST1 installations, every ST1 station or ST1 node station (CPU + all TIMS) has exactly

one station number. This is in the range between 1 and 254. ● ST1 master stations (CPU + all TIMs) are given a master station number ranging from 1

to 8 instead of the station number. ● The number ranges of the station and master station numbers can overlap. ● The station numbers and master station numbers are unique within an ST1 project. ● There is no separate WAN address for the WAN attachment of an ST1 TIM. An ST1 TIM

is always addressed using its ST1 station or master station number.

ST7 installations: ● In ST7 installations, each ST7 communication subscriber has its own subscriber number

that is unique within the project; in other words a CPU, a TIM or an ST7cc/sc PC has its own subscriber number.

● Each WAN attachment of an ST7 TIM module (a TIM 4 has two attachments) is given an ST7 WAN address that is unique only for the relevant subnet.

Note With ST7 subscribers, the WAN address is also synonymous with the network addresses, known as the station address (STA no.) in the SINAUT Diagnostics and Service tool.

2.10.2 ST1 configuration rules To be able to perform the tasks set in the configuration, certain rules must be adhered to during the configuration of ST1 stations with the ST7 configuration tool. These are:

Protocol selection ● Networks to which both ST7 and ST1 subscribers are connected must be operated

according to the ST1 protocol.



Connections ● Connections between ST7 subscribers running over a maximum of one ST1 node station

can be configured in the ST7 configuration tool just as connections between an ST1 master station and an ST1 station running over one ST7 node station.

● On the other hand, connections between pure ST1 devices (ST1 station with ST1 master station or ST1 station with ST1 node station) are not available in the connection configuration of the SINAUT ST7 configuration tool even if they exist in an existing ST1 installation. These connections are configured with STEP 5.

● Connections between stations or node stations (direct communication) are not possible in an ST1 network. Such connections count as invalid connections.

Figure 2-75 ST1 configuration rules: Connections

SINAUT subscriber numbers ● An ST7 CPU that forms an ST1 station or node station is given a SINAUT subscriber

number in the range from 1 to 254. If an ST1 station or node station is replaced by an ST7 device, the old ST1 station number should be adopted as the SINAUT subscriber number.



● An ST7cc/sc PC or an ST7 CPU that forms an ST1 master station is given a SINAUT subscriber number in the range from 1 to 8. If an ST1 master station is replaced by an ST7 device, the old ST1 master station number should be adopted as the SINAUT subscriber number.

● All existing ST1 stations and ST1 node stations have and ST1 station number in the range from 1 to 254. The SINAUT subscriber number for these devices must be identical to the ST1 station number.

● An ST7 TIM connected to an ST1 network is given a SINAUT subscriber number higher than 255.

WAN address ● The WAN address of an ST1 station TIM or ST1 node station TIM must be identical to the

ST1 station number. ● The WAN address of an ST7 station or node station TIM connected to an ST1 network

must be identical to the SINAUT subscriber number of its local CPU. ● The WAN address of an ST7 master station TIM connected to an ST1 network must be

identical to the SINAUT subscriber number of its local CPU; in other words, to the previous ST1 master station number. If several master TIMs exist, each master TIM is given the same WAN address. Exception: When both WAN interfaces of an ST7 master TIM are attached to the same dial-up network, the two WAN addresses cannot be identical. The WAN address of the second interface must then be higher than the ST1 master station number. With all ST7 master TIMs connected to an ST1 network, the SINAUT ST1 master number must be configured the same as the ST1 master number in NetPro in the Special tab of the Properties TIM dialog.

● The WAN address of an ST1 master TIM must be identical to its ST1 master station number. If several master TIMs exist, each master TIM is given the same WAN address. Exception: When two or more ST1 master TIMs are attached to the same dial-up network, the WAN addresses of these TIMs cannot be identical. The WAN address of one of these TIMs must be identical to the ST1 master station number, the WAN addresses of the other master TIMs must be higher.

● The WAN address of an ST7 master TIM located in a node station and connected to an ST1 network must be identical to the ST1 master number of the actual ST1 master station.

● The WAN address of an ST1 master TIM located in a node station must be identical to the ST1 master number of the actual ST1 master station.



Figure 2-76 Excerpt of some of the ST1 configuration rules relating to subscribe number and WAN

address

Recommendation: If there is no local CPU in an ST7 node station connected to an ST1 network, it is advisable to specify a free SINAUT subscriber number in the range from 1 to 254 for the WAN address of the ST7 node TIM so that a CPU can be added to the node station later without any great configuration effort. In a network with the ST1 protocol, when you save in subscriber administration or in the ST1 configuration overview of the SINAUT configuration tool, there is a check made to determine whether the WAN address assigned for a TIM module matches that of its local CPU. Even if the subsequent consistency check does not report errors, the special ST1 configuration rules must nevertheless be adhered to.



2.10.3 Consistency check The consistency check is always started automatically before you use the generate/compile functions in subscriber administration to prevent SDBs or DBs being created with inconsistent data. The consistency check can also be started as a separate function using the SINAUT / Check consistency... menu in subscriber administration and in the ST1 configuration overview. Errors detected during the consistency check are displayed to the user in an error list.

Figure 2-77 Example of an error list after running the consistency check

If inconsistent connections are found, the error list indicates that cause will be diagnosed in the connection configuration in the Invalid connections dialog. Errors resulting from violating the ST1 configuration rules can be eliminated in the SINAUT ST1 configuration overview of the SINAUT configuration tool. After eliminating an error, you must save prior to the next consistency check otherwise be eliminated error will still be reported.

2.10.4 ST1 configuration overview The ST1 configuration overview is opened in the SINAUT configuration tool with one of the following alternative methods: ● The SINAUT / SINAUT ST1 - configuration overview menu ● The SINAUT ST1 - configuration overview button ● The F4 function key In the SINAUT ST1 configuration overview, you can see all the SINAUT subscribers (ST1 and ST7) with their subscriber numbers, the ST1 subscribers are also shown with their WAN network addresses. The module name, the station, the connected SINAUT network and the network node type are also displayed. All potentially incorrect data can be modified in the list. If the row of an ST1 TIM or an ST1 station or master station is selected in the list, the subscriber number and the WAN address can be edited in the lower part of the window. Following the modification, the changed subscriber number and/or changed WAN address can be adopted in the list by clicking the Apply button.



Figure 2-78 The SINAUT ST1 configuration overview

Examples in the ST1 configuration overview shown above include: ● Station 2:

Here, the WAN address must be set to 2. ● Master TIM with subscriber no. 1001:

Here, the WAN address must be set to 1 (the master station has the master station number 1).

If the content of the list is saved and the consistency check activated again, the changes become visible; in other words, the eliminated errors disappear from the error list. Any errors in the list can be work through one after the other and eliminated.

Configuration software for SINAUT ST7 2.11 Change matrix


2.11 Change matrix The change matrix describes the necessary follow-up activities of the user following typical actions in the SINAUT configuration tool.

Table 2-9 Change matrix

Object affected Operator activity in the SINAUT configuration tool

Necessary follow-up action

Station Adding a station - Station Renaming a station - Station Changing the parameter

assignment of a station -

Station Deleting a station All SINAUT connections running over a module in this station are then invalid and are removed the next time you open the SINAUT connection configuration. When necessary, these must be replaced by alternative connections. The SDBs or DBs of all modules that were involved in these deleted connections must be regenerated in the subscriber administration.

TIM module Adding a TIM module - TIM module Renaming a TIM module - TIM module Changing the parameter

assignment of a TIM module If the parameters of a TIM module are changed, the SDBs must be regenerated in subscriber administration only for this TIM. Exception: If parameters are changed in the "WAN access" tab, this affects all SINAUT connections running over the modified WAN driver.

TIM module Deleting a TIM module All SINAUT connections running over this module are then invalid and are removed the next time you open the SINAUT connection configuration. When necessary, these must be replaced by alternative connections. The SDBs or DBs of all modules that were involved in these deleted connections must be regenerated in the subscriber administration.

Network Adding a network - Network Renaming a network - Network Changing the parameter

assignment of a network The SDBs of all the modules connected to this network must be regenerated in the subscriber administration. In WAN networks, these are only TIM modules, in LANs all connected modules.

Network Deleting a network All SINAUT connections running over this network are then invalid and are removed the next time you open the SINAUT connection configuration. When necessary, these must be replaced by alternative connections. The SDBs or DBs of all modules that were involved in these deleted connections must be regenerated in the subscriber administration.

Network nodes Adding a network node - Network nodes Renaming a network node - Network nodes Changing the parameter

assignment of a network node The SDBs of the module containing this network node must be regenerated. Exception: When changing the telephone number, the SDBs of all TIMs in the dial-up network must be regenerated.

Network nodes Networking a network node -

Configuration software for SINAUT ST7 2.11 Change matrix


Object affected Operator activity in the SINAUT configuration tool

Necessary follow-up action

Network nodes Deleting a network node All SINAUT connections running over this network node are then invalid and are removed the next time you open the SINAUT connection configuration. When necessary, these must be replaced by alternative connections. The SDBs or DBs of all modules that were involved in these deleted connections must be regenerated in the subscriber administration.

Network nodes Canceling the networking of a network node

All SINAUT connections running over this network node are then invalid and are removed the next time you open the SINAUT connection configuration. When necessary, these must be replaced by alternative connections. The SDBs or DBs of all modules that were involved in these deleted connections must be regenerated in the subscriber administration.

SINAUT connection Adding a SINAUT connection The SDBs or DBs of all subscribers over which this connection runs must be regenerated in the subscriber administration.

SINAUT connection Deleting a SINAUT connection The SDBs or DBs of all subscribers over which the deleted connection runs must be regenerated in the subscriber administration.

SINAUT subscriber Changing the parameter assignment of a SINAUT subscriber

The SDBs or DBs of all connections that run over this subscriber must be regenerated in the subscriber administration.

Destination subscriber properties of TD7onTIM

Changing the parameter assignment of a destination subscriber of TD7onTIM

The SDBs of all TIMs with TD7onTIM that communicate with this destination subscriber must be regenerated in subscriber administration.

Configuration software for SINAUT ST7 2.12 Version information


2.12 Version information The version information wizard displays the currency installed version and compilation time of the most important components of the SINAUT configuration software. The installed versions of the SINAUT TD7 library and the SINAUT TIM firmware are also shown. This function is started from the Windows start menu SIMATIC / SINAUT ST7 / Information.

Figure 2-79 SINAUT ST7 version information

Configuration software for SINAUT ST7 2.13 Configuration practice


2.13 Configuration practice

2.13.1 Downloading data blocks to the CPU To download data blocks to the CPU module, you use the STEP 7 SIMATIC Manager standard tool. This allows you to copy blocks using drag-and-drop or a menu either in an online window (configured online access) or in the window with the accessible nodes (non-configured online access).

WARNING When you download blocks to the automation system by dragging and dropping, you yourself are responsible for ensuring that the blocks are copied to the correct online object (in other words, the object with the correct MPI address). The STEP 7 tool does not check this. For more detailed information on these activities, refer to the online help of the SIMATIC Manager.

2.13.2 Downloading system data blocks to the TIM You should only download system data blocks (SDBs) to the TIM in the SIMATIC Manager or in the SINAUT Diagnostics and Service tool.

Note When downloading system data blocks in hardware configuration, make sure that no connection SDBs (SDB7xx) are downloaded. If SDBs of this type need to be downloaded to the TIM module, you must use the SIMATIC Manager or the SINAUT Diagnostics and Service tool. SDBs can also be downloaded in network configuration. Creating SDBs during network configuration is a different procedure from that in the SIMATIC Manager and hardware configuration and is not suitable for the TIM module. Copying SDBs to TIM modules should therefore only be done in the SIMATIC Manager or SINAUT Diagnostics and Service tool.

In the SIMATIC Manager, all SDBs of a module are indicated by a symbol with the name System data. This means that you can only ever manipulate all SDBs of a module as a single unit. Otherwise, the same applies as for data blocks. In the hardware configuration, it is possible to download the SDBs of individual modules or entire stations. In both cases, the function is followed by a dialog in which you are asked whether you want to restart the TIM module. This dialog must be exited with Yes to restart the TIM and activate the new SDBs.



2.13.3 Uploading stations with the Upload Station to PG function The STEP 7 function Upload PLC/Station to PG allows the configuration of a connected station to be adopted. In conjunction with TIM modules, this function can only be used with certain restrictions. ● If the station to be uploaded is a TIM rack; in other words if the rack contains only stand-

alone TIM modules, it is not possible to upload the station. The Upload Station to PG function can only be used in racks with CPU modules.

● If there is a 300 series CPU in the rack, the configuration can be uploaded, the TIM module represented in the rack is, however, not fully initialized and is not suitable for further configuration. This must be replaced by a new module from the hardware catalog.

WARNING

If the TIM modules uploaded in this way are further configured, problems can arise particularly in SINAUT communication and when handling the relevant module.

2.13.4 Changing the MPI address of the CPU In hardware configuration, it is possible to change the MPI address of the CPU. If TIM modules are installed in the same rack, when downloading the SDBs ,it is necessary that the download is performed in two steps. 1. Download SDBs only to the CPU not to the TIM. Once the CPU module has received its

new MPI address, the TIM modules go through a reset. 2. Download the SDBs to the TIM modules when they have completed the restart.

2.13.5 Copying projects in the SIMATIC Manager In the SIMATIC Manager, you can, the entire projects by saving them under a different name (File / Save As... menu). After selecting the function, the Save project as dialog opens in which you enter the name and storage path.



Figure 2-80 Save project as dialog for copying objects

When you save, you can also select the With reorganization copy option.

WARNING When you copy projects with reorganization, the SINAUT subscribers and connection data are not copied. These must be reconfigured following the copy function. If you copy projects without reorganization, the SINAUT data is also copied. There are no disadvantages of using this variant. The without reorganization variant is preferable for SINAUT users.

2.13.6 Avoiding time stamp conflicts Each block has an interface time stamp that provides information about when the interface visible to other blocks was last changed. These time stamps are compared by the block editor when a block is opened. If inconsistencies are detected, the inconsistent calls are opened up; in other words, instead of a CALL command, the user finds the code generated by the system as a substitute for the



CALL. This status is reported as a time stamp conflict. The substitute code must then be deleted by the user and the CALL parameters set again. Inconsistencies of this type can occur between: ● OB and FBs / FCs ● FBs /FCs and FBs /FCs ● FBs and their instance DBs

Recommended procedure ● When using the configuration tool, this makes sure that the interface time stamp of all

blocks regenerated by the tool (including instance data blocks) are synchronized with the interface time stamps of the blocks in the TD7 library.

● The time stamp of the block interfaces (supplied version / updates) are frozen until there is an actual change to an interface; in other words changes or corrections in the program code do not affect the interface time stamp.

● This procedure means that an update is possible at any time without causing a time stamp conflict.

● Directly inserting blocks by dragging them from the SINAUT library is permitted as long as the standard ST7 block number range (compare symbol table of the library) is not changed. This procedure is recommended

Not recommended procedure ● If the TD7_UserSource provided by the tool is compiled manually into a CPU block

directory in which there are not yet any SINAUT TD7 blocks or in which some are missing, these blocks are given an interface time stamp that differs from that in the SINAUT ST7 library.

● Any SINAUT ST7 user programs already stored there then develop time stamp conflicts or they occur at the latest after the first update.

● Since SINAUT ST7 support is oriented mainly on the interface time stamp of the blocks due to version maintenance and management of upgrades, this procedure is generally not advisable.

Restrictions The time stamps of the blocks that call SINAUT blocks are not synchronized. Here, time stamp conflicts can continue to occur. The following sequence is therefore advisable for the user: 1. Before starting generation in the SINAUT ST7 configuration tool, a source file with all

blocks that call SINAUT blocks is created. 2. The generation is run. 3. The previously generated source file is compiled.


SINAUT TD7 software package for the CPU 33.1 Overview

Introduction For SINAUT ST7, there is the SINAUT TD7 software package for process data transmission between SINAUT subscribers over WAN, MPI bus and Ethernet. There are two variants of the software package: ● The SINAUT TD7 for the CPU software package, known as TD7onCPU, is a software

package that has parameters assigned on the CPU and that runs on the CPU. It is used in all SINAUT stations in which TIM modules of the type TIM 3 or TIM 4 are configured.

● The SINAUT TD7 for the TIM software package, known as TD7onTIM, is a software package that is configured on Ethernet TIMs and runs on these TIMs. It can be used as an alternative to the TD7onCPU software package if an Ethernet TIM is configured in a SINAUT station. TD7onTIM is described in the section Configuration software for SINAUT ST7.

This chapter only describes the TD7onCPU software package. The TD7 software package for the CPU contains blocks specifically for CPU modules. The package was designed so that it can run both on an S7-400 and on and S7-300 CPU. Exceptions to this will be pointed out explicitly. With the aid of the SINAUT TD7 software, the user creates a program for the CPUs. This program allows change-driven transmission of process data between the individual CPUs and the control center, for example ST7cc. Failure of connections, CPUs, or the control center are displayed. Once a problem has been corrected or the CPUs/control center has started up, data is updated automatically. Apart from process data transmission over WANs, the package is also suitable for local communication between CPUs if these are connected together over MPI. Even here, the local connections and CPUs are constantly monitored and data is updated automatically following startup or after a problem has been eliminated.

Note Data communication from CPU to CPU over a WAN connection can only be implemented with the SINAUT TD7 software. This is not possible with the S7 communication SFBs/SFCs for configured and unconfigured connections. These are suitable only for local communication without a gateway.



The content of the SINAUT TD7 software package The essential components are the package are as follows: ● Basic and auxiliary blocks

Most of these blocks are always required on the CPU. A few are purely optional. The basic blocks handle central tasks such as startup, monitoring of connections and availability of connection partners, general requests, time management, handling communication etc. The auxiliary blocks enter messages in the send buffer or fetch them from the receive buffer, handle send and receive jobs for specific connections, provide information as a result of searches, etc.

● Data point typicals These blocks are included in the CPU program depending on the type and amount of data to be transferred. They put messages together when data changes or when requested and output received process data.

Blocks required with the SINAUT ST7 configuration tool To operate correctly, the TD7 package requires several data blocks per CPU. These DBs are generated automatically by the SINAUT ST7 configuration tool when the SINAUT connections are configured and they are stored on the relevant CPU. These are as follows: ● Central records DB

This contains all the centrally required data including the records of all communication partners and the connections to be managed.

● Communication DBs A separate communication DB is created for each connection. This DB contains a send and receive buffer and all the data required for controlling and monitoring the connection.

Along with the data blocks mentioned above, the SINAUT ST7 configuration tool also stores the basic and auxiliary blocks necessary for a functioning program in the CPU program directory. Users only need to copy the required data point typicals from the SINAUT TD7 library to the CPU program directory and they can then create the SINAUT user program.

Note The blocks stored in the CPU program director by the SINAUT ST7 configuration tool exist once as individual blocks in the 'Blocks' directory and also in the 'Sources' directory as an STL source file with the name 'TD7_UserSource'.



Figure 3-1 Basic and auxiliary blocks in the blocks program directory

Figure 3-2 TD7_UserSource im Programmverzeichnis Quellen



Note If you want to change the STEP 7 user interface to English (in the SIMATIC Manager, Options/Settings menu), the following applies depending on the version of the SINAUT configuration tool: • SINAUT configuration tool version < 2.0

The Mnemonic option must not be changed to IEC or English! This must remain set to SIMATIC. Otherwise there will be compilation errors when generating the SINAUT program!

• SINAUT configuration tool as of version 2.0 The Mnemonic option can be changed to IEC or English! The configuration tool checks the setting for Mnemonic and compiles the SINAUT program correctly.

Basic structure of the user program The SINAUT user program consists of the following: ● Startup program OB100

Here, only the startup block for ST7 "FC Startup" needs to be called. It does not require any parameters.

● Cyclic program OB1 In the simplest case, this program consists of the basic block "FC BasicTask". Following this, the user calls all the data point typicals required for the CPU and sets the parameters to suit the particular application.

● Time-driven program OB35 (or another cyclic interrupt OB) This program is required only when counted pulses need to be acquired on the CPU. FC PulseCounter is called once or more than once in the cyclic interrupt OB.

3.1.1 SINAUT TD7 Library

Introduction When you install the SINAUT software, a library is also created with the SINAUT TD7 software package. This is access in the same way as all other libraries in STEP 7; in other words, from the SIMATIC Manager, you can display a list of available libraries with the Open menu in the Libraries tab. The SINAUT library is located there under the name SINAUT TD7 Library.



Figure 3-3 Opening the SINAUT library SINAUT TD7 Library

Structure of the library SINAUT TD7 Library contains the directory Basic01 that is made up of the following sections: ● Source

Contains the two STL source files Basic01_Source_de (blocks with German mnemonics) and Basic01_Source_en (blocks with English mnemonics). This contains all the blocks of the TD7 library in STL source format.

● Blocks contains all the blocks of the TD7 library in block format. This contains all the SINAUT blocks of the type FB, FC, DB, UDT and VAT and the SIMATIC system blocks SFC and SFB that are used by the SINAUT software.

● Symbols Contains the symbol table of the SINAUT TD7 library.

Note Never modify the content of Source, Blocks or Symbols in the SINAUT TD7 library! Event renaming or moving the library to a different directory is prohibited!



Figure 3-4 Components of the SINAUT TD7 library

Figure 3-5 Source STL files Basic01_Source_de/_en in the SINAUT TD7 library

Figure 3-6 Blocks of the SINAUT TD7 library in block format



Figure 3-7 The symbol table Symbols in the SINAUT TD7 library

Note If you want to change the numbers of individual SINAUT blocks to avoid conflicts with blocks already used in the user program, you must create a simple table for the relevant CPU block(s) in which all the required SINAUT blocks per CPU are listed. This involve is not only the blocks whose number has been changed in the simple table but also those whose number remains unchanged. For more detailed information, refer to the section Changing SINAUT block numbers.

3.1.2 Block overview

Introduction The following table lists all the blocks contained in the TD7 library. For each block, the table provides: ● The standard block number under which the lock is available in the TD7 library. This

number can be changed when necessary. ● The symbolic name of the block. You can call the relevant block in the user program

using this name. ● A note indicating whether this block is an auxiliary block that is called indirectly. This is

important in case the standard number of the auxiliary block needs to be changed. ● A list of the auxiliary blocks required by the relevant block. Only the SINAUT auxiliary

blocks are specified since only these blocks need to be transferred from the TD7 library into the user program directory (normally performed automatically by the ST7 configuration tool). The information on the auxiliary blocks is also important if one or more of the listed SINAUT auxiliary blocks are given a different block number. The block must then be recompiled.

● A brief explanation of the function of the block.



Table 3-1 SINAUT TD7 Library: Block overview

Block no. Symbolic name Aux. block

Required (SINAUT) auxiliary blocks

Explanation

Function blocks FB FB40 MTZ01 - DB127 BasicData,

FC123 Create, FC126 Search Send ST1 status message with 4 bytes of status/binary information.

FB41 MTZ02 - DB127 BasicData, FC123 Create, FC126 Search

Send ST1 status message with 2 bytes of status/binary information.

FB45 MTA01 - DB127 BasicData, FC123 Create, FC126 Search

Receive ST1 status message with 4 bytes of status/binary information.

FB46 MTA02 - DB127 BasicData, FC123 Create, FC126 Search

Receive ST1 status message with 2 bytes of status/binary information.

FB48 STKOP26W - DB127 BasicData, FC123 Create, FC126 Search

Send ST1 data message with max. 26 words of any information.

FB49 ETKOP26W - DB127 BasicData, FC123 Create, FC126 Search

Receive ST1 data message with max. 26 words of any information.

FB50 ATZ01 - DB127 BasicData, FC123 Create, FC126 Search

Send ST1 analog value message with 4 analog values (16-bit ST1 format).

FB52 ATZ03 - DB127 BasicData, FC123 Create, FC126 Search

Send ST1 analog value message with 8 analog values (16-bit ST1 format).

FB55 ATA01 - DB127 BasicData, FC123 Create, FC126 Search

Receive ST1 analog value message with 4 analog values (16-bit ST1 format).

FB56 ATA02 - DB127 BasicData, FC123 Create, FC126 Search

Receive ST1 analog value message with 8 analog values (16-bit ST1 format).

FB60 ZTZ01 - DB127 BasicData, FC123 Create, FC126 Search

Send ST1 counted value message with 1 counted value (32-bit ST1 format).

FB62 ZTZ03 - DB127 BasicData, FC123 Create, FC126 Search

Send ST1 counted value message with 4 counted values (32-bit ST1 format).

FB65 ZTA01 - DB127 BasicData, FC123 Create, FC126 Search

Receive ST1 counted value message with 1 counted value (32-bit ST1 format).


Receive ST1 counted value message with 2 counted values (32-bit ST1 format).


Receive ST1 counted value message with 4 counted values (32-bit ST1 format).

FB70 BTZ01 - DB127 BasicData, FC123 Create, FC126 Search

Send ST1 command message with 1 byte commands (1-out-of-8 ST1 format).

FB73 BTA01 - DB127 BasicData, FC126 Search

Receive ST1 command message with 1 byte commands (1-out-of-8 ST1 format).

FB76 STZ01 - DB127 BasicData, FC123 Create, FC126 Search

Send ST1 setpoint message with 1 setpoint (16-bit ST1 format).





Explanation

FB78 STA01 - DB127 BasicData, FC126 Search

Receive ST1 setpoint message with 1 setpoint (16-bit ST1 format).

FB82 Bin04B_S - DB127 BasicData, FC123 Create, FC126 Search

ST7 status message object, send 4 bytes of status/binary information.

FB83 Bin04B_R - DB127 BasicData, FC123 Create, FC126 Search

ST7 status message object, receive 4 bytes of status/binary information.

FB84 Dat12D_S - DB127 BasicData, FC123 Create, FC126 Search

ST7 data object, send max. 12 double words with any information.

FB85 Dat12D_R - DB127 BasicData, FC123 Create, FC126 Search

ST7 data object, receive max. 12 double words with any information.

FB92 Ana04W_S - DB127 BasicData, FC123 Create, FC126 Search

ST7 analog value object, send 4 analog values (16-bit value in the INT format).

FB93 Ana04W_R - DB127 BasicData, FC123 Create, FC126 Search

ST7 analog value object, receive 4 analog values (16-bit value in the INT format).

FB100 Cnt01D_S - DB127 BasicData, FC123 Create, FC126 Search

ST7 counted value object, send 1 counted value (32-bit ST1 format).

FB101 Cnt01D_R - DB127 BasicData, FC123 Create, FC126 Search

ST7 counted value object, receive 1 counted value (32-bit ST1 format).

FB102 Cnt04D_S - DB127 BasicData, FC123 Create, FC126 Search

ST7 counted value object, send 4 counted values (32-bit ST1 format).

FB103 Cnt04D_R - DB127 BasicData, FC123 Create, FC126 Search

ST7 counted value object, receive 4 counted values (32-bit ST1 format).

FB110 Cmd01B_S - DB127 BasicData, FC123 Create, FC126 Search

ST7 command object, send 1 byte commands (1-out-of-8 ST1 format).

FB111 Cmd01B_R - DB127 BasicData, FC126 Search

ST7 command object, receive 1 byte commands (1-out-of-8 ST1 format).

FB116 Set01W_S - DB127 BasicData, FC123 Create, FC126 Search

ST7 setpoint object, send 1 setpoint (16 bits) and receive current local setpoint.

FB118 Par12D_S - DB127 BasicData, FC123 Create, FC126 Search

ST7 parameter object, send max. 12 double words with parameters and receive current local parameters.

FB119 Par12D_R - DB127 BasicData, FC123 Create, FC126 Search

ST7 parameter object, receive max. 12 double words with parameters and send current local parameters.

FB124 SMS_Control - DB127 BasicData, FC123 Create, FC125 Diagnose, FC126 Search

Block for sending SMS messages.

FB125 PCom Yes DB127 BasicData, FC124 Distribute, FC125 Diagnose, FC126 Search

Block for communication over a peripheral bus connection (SFCs WR_REC and RD_REC are used).

FB126 XCom Yes DB127 BasicData, FC124 Distribute, FC125 Diagnose, FC126 Search

Communication block for an unconfigured X connection (SFCs X_SEND and X_RCV are used).





Explanation

FB127 BCom Yes DB127 BasicData, FC124 Distribute, FC125 Diagnose, FC126 Search

Communication block for a configured communication block connection (SFBs BSEND and BRCV are used).

Functions FC FC113 PartnerMonitor - DB127 BasicData,

FC125 Diagnose, FC126 Search Allows the display of important status information and control for a SINAUT subscriber.

FC114 Trigger - DB127 BasicData, FC125 Diagnose

Sets an output at a defined time or at a defined interval.

FC115 PartnerStatus - DB127 BasicData, FC125 Diagnose, FC126 Search

Displays the connection status for up to 8 SINAUT subscribers.

FC116 Safe - DB127 BasicData Block for saving command and setpoint input.

FC117 PulseCounter - DB127 BasicData Block for acquiring up to 8 counter inputs

FC118 TestCopy - DB127 BasicData Test block for logging received and/or sent messages.

FC119 ListGenerator300 - DB127 BasicData Block for generating an object list. Version for S7-300.

FC120 ListGenerator400 - DB127 BasicData Block for generating an object list. Version for S7-400.

FC121 TimeTask - DB127 BasicData, FC125 Diagnose

Block for keeping the date/time on a CPU.

FC122 Startup - DB127 BasicData Startup block. FC123 Create Yes DB127 BasicData,

FC125 Diagnose, FC126 Search Block for creating messages and entering them in the send buffer.

FC124 Distribute Yes DB127 BasicData, FC125 Diagnose, FC126 Search

Block for distributing received messages to the local destination objects.

FC125 Diagnose Yes DB127 BasicData Block for entering system messages in the diagnostic buffer of the CPU.

FC126 Search Yes - Block for handling searches. FC127 BasicTask - DB127 BasicData,

FC123 Create, FC125 Diagnose, FB125 PCom, FB126 XCom, FB127 BCom

Block for handling all SINAUT basic tasks on the CPU.

Data blocks DB DB99 TestCopyData - - Data block for the test block

FC TestCopy. DB125 SMS_Data - UDT125 ShortMessageObject Data block for FB SMS_Control for

entry, for example of SMS texts. DB127 BasicData Yes UDT126 ConnectionDescription,

UDT127 SubscriberObject Data block for entry of SINAUT basic information.

User-defined data types UDT UDT125 ShortMessage

object Yes - SMS object

(for DB SMS_Data).





Explanation

UDT126 Connection description

Yes - Connection description (for DB BasicData).

UDT127 SubscriberObject Yes - Subscriber object (for DB BasicData). Variable table VAT VAT99 VAT_TestCopy - - Variable table for the test block

FC TestCopy. System function blocks SFB SFB12 BSEND Yes - Block-oriented sending of data over a

configured connection. SFB13 BRCV Yes - Block-oriented reception of data over a

configured connection. System functions SFC SFC0 SET_CLK Yes - Set CPU clock. SFC1 READ_CLK Yes - Read CPU clock. SFC20 BLKMOV Yes - Copy variables. SFC22 CREAT_DB Yes - Create data block. SFC23 DEL_DB Yes - Delete data block. SFC24 TEST_DB Yes - Test data block. SFC25 COMPRESS Yes - Compress user memory. SFC46 STP Yes - Set CPU to STOP. SFC52 WR_USMSG Yes - Write user diagnostic message to the

diagnostic buffer. SFC64 TIME_TCK Yes - Read system time. SFC65 X_SEND Yes - Send data over an unconfigured

connection. SFC66 X_RCV Yes - Receive data over an unconfigured

connection.

3.1.3 Changing SINAUT block numbers

Introduction The blocks in the SINAUT library have fixed block numbers that you should, whenever possible, use with these numbers in your user program. This applies to all SFB an SFC system blocks whose numbers cannot be modified. The numbers of SINAUT FBs, FCs, DBs and UDTs can, however, be adapted when necessary. The effort required for the changes varies from case to case. The three following modification stages can be distinguished: 1. Only numbers of SINAUT blocks are changed that do not belong to the category of

auxiliary blocks (there is a dash in the 'Aux. block' column in the table), and The standard numbers of the SINAUT auxiliary blocks were not changed in the relevant project.

2. Only the numbers of the SINAUT UDTs are changed. 3. One or more SINAUT auxiliary blocks will be given a different number (in the table, there

is a 'yes' in the 'Aux. block' column),



or you want to copy for the SINAUT blocks into a project in which numbers of SINAUT auxiliary blocks have already been changed (it does not matter whether these are auxiliary blocks or not).

Depending on the change level, you should follow the steps outlined below:

Note With each change to a block number made by the user, make sure that the number change is also entered in the symbol table of the CPU. Otherwise, errors will occur when you save in the 'Subscriber Administration' SINAUT tool.

Changing the numbers of blocks other than auxiliary blocks The prerequisite for using the instructions here is as follows: ● You only want to change numbers of SINAUT blocks that do not belong to the auxiliary

block category, and

● The standard numbers of the SINAUT auxiliary blocks have not been changed in the relevant project.

Initial situation You have configured your SINAUT installation as already described in the section 'Configuration software for SINAUT ST7'; in other words, you have completed the connection configuration with the appropriate SINAUT configuration tool and have started to save in the 'Subscriber Administration' SINAUT tool. The result is that all the necessary SINAUT blocks already exist in all the program directories of the CPU in addition to the SDB directory and OB1 as shown in the following figure.

Figure 3-8 Example of a project (SINAUT basic blocks already present)



Making the change Copy the additional blocks that you require directly from the TD7 library to the program directory of the relevant CPU. If the number of one of the copied blocks is identical to an existing block, a dialog is displayed automatically indicating the number conflict. You will be asked whether or not you want to remain the block. After clicking on Rename..., a further dialog appears in which you can enter the new number, for example FB82 is renamed to FB8 as shown in the following figure.

Figure 3-9 Renaming blocks in the dialog

If the block number is changed using this dialog, the number change is automatically included in the symbol table. This can be recognized because the renamed block in the block directory is displayed immediately with the corresponding name from the TD7 library.

Figure 3-10 Renaming with automatic symbol assignment



If you copy several blocks at one time, the dialog is displayed for each block whose number is already being used. You can therefore copy all the required blocks per CPU at one time and then adapt the block numbers and entries in the symbol table as necessary. If the dialog does not appear when you copy blocks, there is no conflict with existing blocks. If you nevertheless want to give blocks a different number, you must change these numbers directly in the block directory and also adapt the relevant entries in the symbol table (although the symbolic name of a SINAUT block was entered automatically in the symbol table of the destination CPU when the blocks were copied from the TD7 library, the new numbers are not taken into account since they were not changed initially during copying). If you want to change one of the blocks already stored by the SINAUT tool (here, this can only involve the blocks FC122 Startup and FC127 BasicTask because all other blocks belong to the auxiliary block category), the numbers of these blocks can be changed directly in the block directory. Do not forget, however, to make the same number change in the symbol table of the CPU.

Note Never use this method to change the numbers of the SINAUT data blocks. These are the data blocks with the symbolic names BasicData, XComData01, XComData02 etc., PComData01, PComData02 etc. and BComData01, BComData02 etc.

If you want to make the same changes for more than one CPU, the most efficient method is to make the changes first in the block directory and the symbol table of one CPU. You can then copy the modified blocks from the block directory of the finished CPU to the other CPUs and then do the same for the symbol tables.

Changing the numbers of UDTs The prerequisite for using the instructions here is as follows: ● You only want to change the numbers of SINAUT UDTs.

Initial situation You have completed the configuration of your SINAUT installation including the connection configuration with the appropriate SINAUT configuration tool. You have not yet saved in the 'Subscriber Administration' SINAUT tool. The result is that there are not yet any SINAUT blocks in the program directories of the CPUs. The block directory CPU contents, for example, only the system data and OB1 as shown in the following figure.



Figure 3-11 Example of a project (still without user or SINAUT program)

Making the change The change to the UDT numbers is made indirectly using the symbol table of the CPU with the aid of the 'Subscriber Administration' SINAUT Configuration Tool. Step 1 ● Copy the UDTs that you want to change in your program from the symbol table of the

TD7 library to the symbol table of the first CPU. ● Change the numbers of the SINAUT UDTs to the numbers you require in the symbol

table. ● Save the symbol table. ● Then copy the rows with the changed UDT numbers to the symbol tables of all other

CPUs of your project. Do not forget to save all the modified symbol tables.

Step 2 ● Once all the symbol tables have the required values and have been saved, change to the

'Subscriber Administration' SINAUT ST7 Configuration Tool. ● Click the 'Save' button. An extra dialog 'Properties' opens (see following figure). ● Make sure that a check mark is entered in front of the following options in this dialog:

– 'System data blocks for TIMS and CPUs' and

– 'SINAUT TD7 blocks for CPUs' – and a dot in front of 'for all CPUs'. Then click on 'OK'.



Figure 3-12 Dialog for triggering compilation of the SINAUT TD7 blocks

After you have saved, all the SINAUT blocks basically required are entered in the block directories of all CPUs, and possibly also the UDTs with the new numbers you have selected. The SINAUT UDTs are required to generate the BasicData data block. This central administrative block also exists in the block directory and is generated taking into account the new UDT numbers.

Changing the numbers of auxiliary blocks The prerequisite for using the instructions here is as follows: ● You want to change the numbers of SINAUT auxiliary blocks in a new project (see below,

initial situation 1), or

● You want to copy further SINAUT blocks into a project in which numbers of SINAUT auxiliary blocks have already been changed; it does not matter whether these are auxiliary blocks or not (see below, initial situation 2).

Initial situation 1 You configure your SINAUT installation and as described in the section 'Configuration software for SINAUT ST7' and have configure the connections with the appropriate SINAUT configuration tool. You have not yet started the 'Subscriber Administration' SINAUT tool. Or the S7 CPUs and TIM modules exist in your project. The block directory of the CPU contains only the system data and OB1.



Making the change The change to the numbers is made indirectly using the symbol table of the CPU with the aid of the 'Subscriber Administration' SINAUT Configuration Tool. Step 1 Fill the block directories of all S7 CPUs with the user blocks (FBs, FCs, DBs and UDTs) whose numbers you want to retain. If you have assigned symbolic names to your blocks, enter these in the symbol tables of the CPUs. Step 2 Then check which SINAUT blocks you require for your program. The following table shows which blocks are always required by the SINAUT program (depending on the CPU type, there are slight variations). The SMSxxx blocks are required only when the SMS function is configured.

Table 3-2 SINAUT blocks that are always required

S7-300 S7-400 FB126 XCom FB127 BCom FB125 PCom

FB124 SMS_Control FC122 Startup FC123 Create

FC124 Distribute FC125 Diagnose FC126 Search

FC127 BasicTask DBxxx SMS_Data DB127 BasicData

UDT126 ConnectionDescription UDT127 SubscribeObject

Based on the table, you can see which other blocks may be required. At least one or more blocks for data acquisition and output are required. These are the blocks in the range from FB40 ... FB117. Further optional basic functions may also be required that are available in the library under FC114 ...FC121 (you will find information on these optional basic functions below in the section 'SINAUT startup program in OB100'). When putting together the required SINAUT blocks, does not matter whether or not these blocks have numbers that need to be changed. You should identify all the SINAUT blocks required per CPU. Copy the rows from the symbol table of the SINAUT TD7 library with the required SINAUT blocks to the symbol tables of the individual CPUs. In the symbol tables of the CPUs, change the SINAUT block numbers to the required numbers.



Note If a change is the same for several CPUs, the most efficient method is to adapt the symbol table first for one of the CPUs and then to copy these entries to the symbol tables of all other CPUs.

Step 3 Once all the symbol tables have the required values, change to the 'Subscriber Administration' SINAUT ST7 Configuration Tool. Click the 'Save' button. An additional dialog "Properties" opens. In this dialog, make sure that there is a check mark in front of 'System data blocks for TIMs and CPUs' and in front of 'SINAUT TD7 block for CPUS' and a dot in front of 'for all CPUs'. Then click on 'OK'. After the save is completed, the SINAUT blocks listed in the symbol table have been added to the content of the block directory and one or more communication DBs have been added (recognizable by their symbolic names, for example XComData01 or BComData01). The SINAUT blocks now have their new numbers. If numbers of SINAUT auxiliary blocks have been changed, all SINAUT blocks that call these auxiliary blocks have been recompiled; in other words, they now call these auxiliary blocks internally with the new numbers. Initial situation 2 You want to copy further SINAUT blocks to a CPU on which the numbers of SINAUT auxiliary blocks have already been changed. It does not matter whether or not these are auxiliary blocks or whether you also want to give these blocks new numbers. Copying later The blocks to be added to the existing, changed SINAUT auxiliary blocks are adapted and any number changes to these blocks made indirectly using the symbol table of the CPU and with the aid of the 'Subscriber Administration' SINAUT configuration tool. Step 1 Copy the rows from the symbol table of the SINAUT TD7 library with the SINAUT blocks you still require to the symbol table of the CPU. If necessary, change the numbers of these blocks in the symbol table of the CPU. If you want to add the same blocks to further CPUs, the most efficient method is to copy the new entries from the symbol table of the first CPU to the symbol tables of the other CPUs, particularly if you have assigned different numbers to the new blocks. Changes to the numbers of these blocks are then adopted directly on the other CPUs. Step 2 Change to the 'Subscriber Administration' SINAUT configuration tool and save again as explained in Step 3. When the save is complete, the blocks newly added to the symbol table are stored in the block directory of the CPU, if applicable with new block numbers. They have also been recompiled and therefore adapted to their local SINAUT environment; in other words internally, they call the SINAUT auxiliary blocks under their new numbers.



Note If a SINAUT block that you have added already exists on one of the other CPUs of the project, and if the same number changes have been made for the SINAUT auxiliary blocks, the block can also be copied from the program of the relevant CPU. In this case, however, no new entry is made in the symbol table of the target CPU as is the case when copying from the TD7 library *). You should therefore modify the symbol name manually to avoid errors during subsequent compilations.

*) This applies only to versions older than STEP 7 Version 5.1

3.1.4 Copying programs

Introduction If several stations of a SINAUT project require the same or almost the same programme, the most efficient method used to complete the program first for one of the stations. Following this, the program can be copied to all other stations and adapted to the local situation. A safe method for copying programs in SINAUT projects is described below.

Initial situation You have configured your SINAUT installation as already described in the section 'Configuration software for SINAUT ST7'; in other words, you have completed the connection configuration with the appropriate SINAUT configuration tool and have started to save in the 'Subscriber Administration' SINAUT tool. The result is that all the necessary SINAUT blocks already exist in all the program directories of the CPU in addition to the SDB directory and OB1. You have completed the program for one of the CPUs want to copy this to other CPUs.

Copying With the method described below, you copy the entire content of the S7 program from the source CPU to the target CPU(s). Following this, you correct the CPU SDBs and the SINAUT data blocks (BasicData, XComData, PComData, BComData) on the target CPUs. You do this by saving in the 'Subscriber Administration' SINAUT configuration tool. Step 1 ● Open the S7 Program(..) directory on the CPU whose program you are using as a

template. ● In the right-hand window, select all three subdirectories Sources, Symbols and Blocks

(see figure). ● Copy the selected elements to the clipboard: Either using the 'Copy' function in the 'Edit'

menu or using the Windows key combination Ctrl + C.



Figure 3-13 Selecting the program of the source CPU

Step 2 ● Now open the S7 Program(..) directory of the CPU in which you want to insert the

program from the clipboard. ● In the right-hand window, select the three subdirectories Sources, Symbols and Blocks

again. ● Then start the 'Paste' function: Either using the 'Paste' function in the 'Edit' menu or using

the Windows key combination Ctrl + V. Repeat step 2 for all other CPUs that require the same program. Step 3 ● Go to the 'Subscriber Administration" SINAUT configuration tool and save. ● In the 'Properties' dialog box, make sure that there is a checkmark before

– 'System data blocks for TIMS and CPUs' and

– 'SINAUT TD7 blocks for CPUs' . ● Then click on 'OK'. When the save is completed, the SINAUT-specific data has been adapted to the local situation in all CPUs and the SDBs of the CPUs once again have the correct content.



3.1.5 Using online help

Introduction This chapter 'SINAUT TD7 software package for the CPU' is available on the PG as a help file. You can therefore call up this chapter online. The following sections describe how to call up the online help.

Starting the online help from the SINAUT TD7 library To start the online help from the SINAUT TD7 library simply select a block in the ’Blocks’ directory, for example, FB82. Then press the F1 key. The description of the selected block is displayed immediately.

Figure 3-14 Starting the online help from the SINAUT TD7 library

Starting the online help from the block directory of the user program Just as in the SINAUT TD7 library, you can start the online help from the block directory of the user program as follows: Select the required block, and then press the F1 key.



Figure 3-15 Starting the online help from the block directory of the user program

Starting online help while creating programs You can also call up online help when you are programming. The cursor must be located in the row with the call of the block for which you need help. The figure below, for example, shows the cursor in the row with the FB82 'Bin04B_S' call. If you now press the F1 key, the help text for this block is displayed.

Figure 3-16 Starting online help while creating programs



Example of a help text The following figure shows part of the help text that appears if you press the F1 key in the examples above.

Figure 3-17 Example of a help text

Selecting help topics You can access any other part of the help file from the help text for an individual block. Double-clicking on the ’Contents’ button opens the help topics window: SINAUT TD7 block help' (see figure below). From here any section of this chapter ’SINAUT TD7 software package for the CPU’ can be opened using the ’Contents’, ’Index’ or ’Find’ tabs.

SINAUT TD7 software package for the CPU 3.2 Principle of communication between SINAUT objects


Figure 3-18 Selecting help topics

3.2 Principle of communication between SINAUT objects

Introduction The term "object" within SINAUT ST7 refers to the type of display and handling of process entities such as status information, analog values, commands, motors, valves, regulators, etc. An object always consists of a process component and an operator control and monitoring component that operate in separate PLCs (subscribers) of the SINAUT network To perform their assigned functions, the tow components must be able to communicate with one another. Setpoints, parameters, commands and organizational instructions are sent from the operator end to the process object and the process object returns process data, alarm/status messages, and organizational information. In the TD7 world, at both the process end as well as the operator end, an object consists of a processing instruction set - referred to below as a typical - in the form of an S7 function block (FB) and an assigned object data record in the form of an instance DB for the FB. The following figure shows the principle used for the exchange of data between the process and operator components of an object.



Daten-Index 0

Daten-Index n

• • •

Daten-Index 0

Daten-Index n

• • •

Figure 3-19 The principle of object communication

Essentially, the data that describes an object is exchanged. This is located in the object data record under data index 0...n. The extent and composition of this data area depends on the typical. It can consist of several identical data types or a combination of different data types. In the object data record at the process and operator ends, the data structure of two corresponding typicals is identical. The data exchange does not necessarily flow in both directions. There are simple objects in which data transmission is one-way, for example, only process data is sent to the operator component. Organizational information is also exchanged between the two ends in addition to process and operator data. This data flow and the data area reserved for this in the object data record (the org. indexes) are not shown in the figure above.

Principle of object addressing Every automation device with SINAUT TD7 software (generally simply referred to as a PLC or CPU) is assigned a unique network-wide SINAUT subscriber number ranging from 1 to 32000. Every typical that is called in one of these CPUs has an instance DB whose number is identical to the SINAUT object number. The use of the SINAUT subscriber number and the SINAUT object number allows unique addressing for the communication between corresponding typicals. Each typical has the following two parameters to define the communication relation: ● PartnerNo

Subscriber number of the partner with which data is exchanged. ● PartnerObjectNo

Object number (= instance DB no.) on this partner.



Figure 3-20 Object communication over WAN

The figure shows various examples of addressing objects that exchange data with partner objects over a WAN. Explanation based on the example of object communication between subscribers 1 and 4: Subscriber 1 contains the process-oriented object no. 5 and that communicates with the operator-oriented object no. 15. The partner addressing in the typical of object 5 must therefore be defined as follows PartnerNo = 4 (subscriber number of the operator partner) PartnerObjectNo = 15 (number of the corresponding object on this partner) In the other direction the partner address for object 15 is as follows: PartnerNo = 1 (subscriber number of the process partner) PartnerObjectNo = 5 (number of the corresponding object on this partner) When object 5 wants to transmit data to its partner object 15, a data message is put together in which the specified two-level partner address is entered as the destination address. Based on the destination subscriber 4 (= PartnerNo), the SINAUT TD7 software and the TIM



modules in the SINAUT network make sure that this message is delivered to the specified destination subscriber 4. When the message arrives at destination subscriber 4, the TD7 software reads the destination object number 15 (= PartnerObjectNo) contained in the message and recognizes that the information in the message should be stored in the local DB15. The index number contained in the message is also taken into account when selecting the storage location. If, for example, the index number is X, the information is stored in DB15 starting at data index X. Information is also entered in the object DB indicating that new data has arrived and identifying the data indexes that have been updated. In the following program cycle, the operator typical that processes this object detects the reception of new data, processes it according to the typical function and applies it to the data outputs configured for the typical. In the opposite direction, operator object 15 sends its data intended for process object 5 in a message containing subscriber no. 1 and object no. 5 as the destination address. This message finally arrives at subscriber no. 1 directed by the TD7 software and TIMs. The information contained in the message is entered in the appropriate location in object DB 5, once again based on the destination object no. 5 and the data index. In the following program cycle, the process typical processes the newly received data and makes it available to the configured outputs in an appropriate form.

Object communication over LAN In addition to data transmission between SINAUT objects over a WAN, the SINAUT TD7 software also allows local communication over LANs (the current software presently supports only the MPI bus as a LAN). The following figure assumes an installation structure in which several PLCs are planned in one station. Each PLC handles a particular automation task (in the example, subscribers 10, 11 and 12). This station also includes a further higher-level PLC (subscriber 13) in which a user controller is incorporated that controls the automation in the subordinate PLCs.



Figure 3-21 Object communication in the LAN (MPI)

In this configuration, the TD7 software could be used with its process and operator typicals as shown in the diagram. In the subordinate PLCs, the process typicals handle local automation and send data changes over the MPI bus to the operator objects in the central control device, subscriber 13. The user controller reads the process information output to the operator objects and processes it accordingly. If the current situation requires that commands or setpoints are transferred to the process objects, these are entered by the user controller over the appropriate inputs of the operator typicals. These handle the immediate transmission to the process objects that take into account this information in their automation task in keeping with the functions of the typical. The process objects can not only send their data to their corresponding operator object in subscriber 13 and receive control instructions from there. They can also send process information to another partner, for example, a control center connected over a WAN, and, if applicable, also receive commands and setpoints from there. The following section describes how communication with more than one partner can be implemented.

Object communication with several operator subscribers Apart from communication between one process typical and one operator typical, as in the figure above, data can also be exchanged between the process typical and more than one operator partner. The following figure illustrates the principle of such a configuration in which an operator typical for the process object in subscriber 1 is intended for local subscriber 2 and also for subscribers 3 and 4 that are connected over the WAN.



Figure 3-22 Object communication with several operator subscribers

The data acquired at the process end is sent simultaneously to all three operator partners. From the operator end, the operator data can be transferred to the process object at any time independently. Return messages from the process, resulting from an operator instruction from one subscriber, are automatically sent to all three operator objects. Each operator end therefore has the latest information. Even when it receives a general or single request, the process object sends the requested data not only to the partner who sent the request but also to the other two partner objects. In this case, subscribers 2, 3 and 4 must either be specified explicitly as partners in process typical (the typical must then have at least three parameters for partners, which is not the case at present) or there are no partner addresses specified in the typical. In the latter situation, the TD7 software automatically transmits to all subscribers for which a connection has been configured (using the SINAUT connection configuration). In the example above, subscriber 1 needed to have connections configured for subscriber 2 as well as for subscribers 3 and 4.



Based on this connection configuration, from the subscriber records it is known that subscriber 1 has a local connection with subscriber 2 as well as a WAN connection to subscribers 3 and 4 both over through the local TIM module. The TD7 software then puts together two messages: One message is sent to the locally available partner 2 over the MPI bus, the other message is sent to the TIM for transmission. For its part, the TIM checks which partners it knows in conjunction with subscriber 1. From its records it identifies subscriber 3 and subscriber 4. If the WAN is a dial-up network, the TIM duplicates the message: once for subscriber 3 and once for subscriber 4. The TIM adds the destination subscriber numbers 3 or 4 to the messages that are not yet in the messages. The TIM then establishes the connection to subscriber 3 and sends the message intended for it. Following this, the TIM calls subscriber 4 and transmits its copy of the message. If the WAN is a dedicated line network and the TIM of subscriber 3 is the polling master (master TIM), the subscriber 1 TIM cannot transmit directly to 3 and 4 as it can in a dial-up network. In this situation, the message for subscriber 4 must be transmitted indirectly over the master TIM in subscriber 3. The message to be sent is not duplicated; it is given two destination addresses, one for subscriber 3 and one for subscriber 4. This message is then to the master TIM sent with the next poll. Based on the destination addresses and its subscriber records, the TIM recognizes that one of these destinations can be reached locally and the other over the dedicated line network. The master TIM then makes a copy of the message. Destination address 4 from the original is removed and the message forwarded with the remaining destination address 3 to subscriber 3 that is available locally. The copy only includes destination address 4 and is sent to the TIM of subscriber 4 over the dedicated line from where it is then passed on to subscriber 4.

Interaction of the blocks

Figure 3-23 Interaction of the blocks (based on the example of the process end)

SINAUT TD7 software package for the CPU 3.3 Structure of the SINAUT user program


3.3 Structure of the SINAUT user program

Introduction The SINAUT user program is contained in the following organization blocks: ● SINAUT startup program in OB100 ● Cyclic SINAUT program in OB1 ● Time-driven SINAUT program in a cyclic interrupt OB, for example OB35 ● SINAUT test routine in the programming error OB121

Note In the following description of the SINAUT program structure, the tasks of the individual blocks are only outlined briefly. For more detailed information on the functions and parameters, refer to the descriptions of the blocks mentioned.

3.3.1 SINAUT startup program in OB100 The structure of the SINAUT program in the startup OB100 is as follows:

Startup OB100

• The only task required here for the SINAUT program is to integrate the FC Startup call in the startup OB100. The FC has no parameters.

Startup

• User-specific startup functions that are required independent of the SINAUT program can be included before or after FC Startup in the startup OB.

Note Startup OB101, which is intended for S7-400 restarts, may not be used!

3.3.2 Cyclic SINAUT program in OB1

Introduction The basic structure of the cyclic SINAUT program in OB1 is described below. In later sections, you will find a detailed description of OB1 for a station and a master station.



Note Unless indicated otherwise, the call sequence of the blocks must be adhered to exactly! The entire cyclic SINAUT program must be processed in every OB1 cycle.

Basic structure of the cyclic SINAUT program in OB1

Cyclic OB1 BasicTask • FC BasicTask must always be called at the start of the cyclic SINAUT

program. It handles basic SINAUT tasks that are always required. • Directly following FC BasicTask, additional blocks can be called to perform

optional basic functions, for example: • - FC TimeTask Provides the SINAUT time. • - FC Trigger Scheduled starts for user programs and data

messages. • - FC PartnerStatus Displays subscriber OK/disrupted. • - FC PartnerMonitor Extended subscriber-specific display and control

features.

Optional SINAUT basic functions

• - FC ListGenerator Creation of address lists for received messages with incomplete destination addresses.

Data point typicals • Following the FCs shown above for SINAUT basic tasks, data point typicals for sending and receiving data are called. The sequence of the individual typicals is unimportant. The number of typicals to call and the required types depend on the amount and type of data to be sent and received. You can see which data point typicals are currently available by referring to the SINAUT TD7 library installed on the programming device. All data point typicals are FBs. An instance DB must be specified when an FB is called. The number of this instance DB is identical to the object number of the datapoint object (this addressing rule does not apply to the ST1 versions of the data point typicals).

• The user-specific cyclic program that is required independent of the SINAUT program can be included before or after the SINAUT program in OB1 or, if suitable, within the SINAUT program itself.

Note Users, of course, is free to structure the SINAUT program in OB1 according to their preferences by ’packing’ the SINAUT program in one or more FCs.



The cyclic OB1 program for a station


program. The FC has only one parameter, namely UserFC. Normally 0 can be specified. However, if you require user-specific processing for received messages, you will need to specify the number of an FC containing the user program for this processing.

TimeTask • As an option, you can call FC TimeTask immediately after FC BasicTask. The FC has no parameters. FC TimeTask must be included if you need the SINAUT time. This enables SINAUT messages to be time-stamped. However, you can also use the SINAUT time to start program components at a specific point in time or to schedule the transmission of data messages. FC Trigger, described below, is then required. For this FC to be used, the PLC must be provided with the SINAUT time from a local TIM module. This can be specified during the parameter assignment of the TIM in HW Config in the ’Properties’ dialog, ’Time service’ tab. See chapter ’Configuration software for SINAUT ST7’.

Trigger • FC Trigger can be included as an option. The FC sets its output for the duration of one OB1 cycle when the point in time or the time interval set for the FC has been reached. The FC can be inserted several times if several times or various time intervals are required. Requirement for the use of the FC: FC TimeTask must be called first in the OB1 program (see above).

PartnerStatus • FC PartnerStatus can be included as an option. The FC shows the current ’disrupted’ or ’OK’ status for a maximum of 8 SINAUT subscribers (communication partners).



Cyclic OB1 ListGenerator • FC ListGenerator300 (for S7-300 CPU) or FC ListGenerator400 (for

S7-400 CPU) can be included as options. The FC is required if the station receives messages containing no destination address or an incomplete destination address. This can occur in the following situations: – When the station receives ST1 messages. – When the configuration of the destination address is omitted in

one or more data point typicals in an ST7 device with which the station communicates (the parameters PartnerNo and PartnerObjectNo were not specified; there is therefore a transmission to all known destination subscribers).

Following the FCs shown above for SINAUT basic tasks, data point typicals for sending and receiving data are called. The sequence of the individual typicals is unimportant. The number of typicals to call and the required types depend on the amount and type of data to be sent and received. The following typically applies to a station: • Send

– Binary information, such as status messages and alarms – Analog values – Counted values

• Receive – Commands – Setpoints (including limit values, parameters, etc.)

All data point typicals are FBs. An instance DB must be specified when an FB is called. The number of this instance DB is identical to the object number of the datapoint object (this addressing rule does not apply to the ST1 versions of the data point typicals). A data point object consists of one or more data points of the same type, e.g. 4 bytes of binary information, or 4 analog values, or 1 byte commands, etc.

ST7 format

ST1 format

Bin..._S MTZ.. • The following should be inserted for acquiring and transmitting of binary information, such as status information, alarms, etc.: For ST7: one or more FB-Bin…_S For ST1: one or more FB-MTZ..

Ana…_S ATZ.. • The following should be inserted for acquiring and transmitting analog values: For ST7: one or more FB Ana…_S For ST1: one or more FB ATZ..

Cnt…_S ZTZ.. • The following should be inserted for acquiring and transmitting counted values: For ST7: one or more FB Cnt…_S For ST1: one or more FB ZTZ.. A requirement for the use of the FBs mentioned is that FC PulseCounter is included in a cyclic interrupt OB, e.g. OB35. This FC is responsible for the actual (time-driven) acquisition of counted pulses in the background

CMD..._R BTA.. • The following should be included for receiving and outputting commands: For ST7: one or more FB Cmd…_R For ST1: one or more FB BTA..



Cyclic OB1 Set..._R

or Par…_R

STA.. • The following should be included for receiving and outputting setpoints, limits, parameters, etc.: For ST7: one or more FB Set…_R or FB-Par..._R For ST1: one or more FB STA..

• The user-specific cyclic program for the station that is required independent of the SINAUT program can be included before or after the SINAUT program in OB1 or, if suitable, within the SINAUT program itself.

In the above OB1 program structure for a station, only data point typicals which process data of the same type are listed. There are additional data point typicals that can send and receive any combination of data types: ● For ST7:

FB Dat12D_S for sending or FB Dat12D_R for receiving 12 data double words with any information content.

● For ST1: FB STKOP26W for sending or FB ETKOP26W for receiving 26 data double words with any information content.

These typicals can also be included in the cyclic SINAUT program in place of or in addition to the data point typicals in the program structure here.

Note There is no data-specific processing and change control for these typicals for any combination of information types. The user program is responsible for this. The only optional change control that can be activated is the triggering of a transmission at each bit change.

Note

The use of the typicals STKOP26W and ETKOP26W may be mandatory especially for communication with the SINAUT LSX control system when using the ST1 protocol. LSX objects that contain several data indices in the send or receive direction can be implemented without problem only with these typicals. For more information, refer to the detailed descriptions of these typicals.

The cyclic OB1 program for a master station


program. The FC has only one parameter, namely UserFC. Normally 0 can be specified. However, if you require user-specific processing for received messages, you will need to specify the number of an FC containing the user program for this processing.



Cyclic OB1 TimeTask • As an option, you can call FC TimeTask immediately after FC

BasicTask. The FC has no parameters. FC TimeTask must be included if you need the SINAUT time. This enables SINAUT messages to be time-stamped. You can also use the SINAUT time to start program sections according to a schedule. FC Trigger, described below, is then required. For this FC to be used, the PLC must be provided with the SINAUT time from a local TIM module. This can be specified during the parameter assignment of the TIM in HW Config in the ’Properties’ dialog, ’Time service’ tab. See chapter ’Configuration software for SINAUT ST7’.

Trigger • FC Trigger can be included as an option. The FC sets its output for the duration of one OB1 cycle when the point in time or the time interval set for the FC has been reached. The FC can be inserted more than once if several times or various time intervals are required.Requirement for the use of the FC: FC TimeTask must be called first in the OB1 program (see above).

PartnerStatus • FC PartnerStatus can be included as an option. The FC indicates the current ’disrupted’ or ’OK’ status for a maximum of 8 SINAUT subscribers (communication partners). If you want to display the status for more than 8 subscribers, a corresponding number of PartnerStatus FCs must be included. The block is practical for monitoring the connections with local TIMs.

PartnerMonitor • FC PartnerMonitor can be included as an option. This FC displays important status information about a SINAUT subscriber (communication partner). The FC can also be used to trigger a general request to the subscriber and to establish and disconnect a permanent connection with the subscriber. FC PartnerMonitor must be included once for each subscriber requiring the extended display and control features. FC PartnerStatus can be omitted for these subscribers. The block is practical for monitoring and controlling the connections with ST7 stations.



Cyclic OB1 ListGenerator FC ListGenerator300 (for S7-300 CPU) or FC ListGenerator400 (for S7-

400 CPU) can be included as options. The FC is required if the master station receives messages containing no destination address or an incomplete destination address. This can occur in the following situations:• When the configuration of the destination address is omitted in one or

more data point typicals in an ST7 station (the parameters PartnerNo and PartnerObjectNo were not specified; there is therefore a transmission to all known destination subscribers).

• When ST1 stations are connected to the master station. Following the FCs shown above for SINAUT basic tasks, data point typicals for sending and receiving data are called. The sequence of the individual typicals is unimportant. The number of typicals to call and the required types depend on the amount and type of data to be sent and received. The following typically applies to master station: • Send

– Commands – Setpoints (including limit values, parameters, etc.)

• Receive – Binary information, such as status messages and alarms – Analog values – Counted values

All data point typicals are FBs. An instance DB must be specified when an FB is called. The number of this instance DB is identical to the object number of the datapoint object (this addressing rule does not apply to the ST1 versions of the data point typicals). A data point object consists of one or more data points of the same type, e.g. 4 bytes of binary information, or 4 analog values, or 1 byte commands, etc.

ST7 format

ST1 format

Bin..._R MTA.. • The following should be inserted for receiving and outputting binary information, such as status information, alarms, etc.: For ST7: one or more FB Bin…_R For ST1: one or more FB MTA..

Ana…_R ATA.. • The following should be included for receiving and outputting analog values: For ST7: one or more FB Ana…_R For ST1: one or more FB ATA..

Cnt…_R ZTA.. • The following should be included for receiving and outputting counted values: For ST7: one or more FB Cnt…_R For ST1: one or more FB ZTA..

CMD..._S BTZ.. • The following should be inserted for acquiring and transmitting commands: For ST7: one or more FB Cmd…_S For ST1: one or more FB BTZ.. A requirement for the use of the FBs mentioned is that FC Safe is included at the end of all data point typicals. This FC is responsible for reliable input of commands and setpoints.



Cyclic OB1 Set..._S

or Par…_S

STZ.. • The following should be included for acquiring and transmitting setpoints, limits, parameters, etc.: For ST7: one or more FB Set…_S or FB Par..._S For ST1: one or more FB STZ.. A requirement for the use of the FBs mentioned is that FC Safe is included at the end of all data point typicals. This FC is responsible for reliable input of commands and setpoints.

Safe • FC Safe must be called once at the end of all data point typicals when send blocks for commands (Cmd..._S, BTZ..) or setpoints (Set..._S, Par..._S, STA..) are called.

• The user-specific cyclic program for the master station that is required independent of the SINAUT program can be included before or after the SINAUT program in OB1 or, if suitable, within the SINAUT program itself.

In the above OB1 program structure for a master station, only data point typicals which process data of the same type are listed. There are additional data point typicals that can send and receive any combination of data types: ● For ST7:

FB Dat12D_S for sending or FB Dat12D_R for receiving 12 data double words with any information content.

● For ST1: FB STKOP26W for sending or FB ETKOP26W for receiving 26 data double words with any information content.

These typicals can also be included in the cyclic SINAUT program in place of or in addition to the data point typicals in the program structure here.

Note There is no data-specific processing and change control for these typicals for any combination of information types. The user program is responsible for this. The only optional change control that can be activated is the triggering of a transmission at each bit change.

Note

In the master station it is practical to structure the OB1 program according to stations, in other words, all send and receive data typicals belonging to the same station are packaged in one FC. The best overview is provided when the number of the FC is identical to the subscriber number of the station.

3.3.3 Time-driven SINAUT program in a cyclic interrupt OB

Introduction A time-driven SINAUT program is only needed in a CPU if counted pulse acquisition is used in the CPU.



The counted pulses are acquired over a normal digital input module. To be able to acquire the pulses reliably, the digital inputs used must be polled for changes at fixed time intervals. This time interval is based on the duration of the shortest counted pulse. The minimum permitted counted pulse duration is 50 ms. The same applies to the length of the pause. The resulting maximum count frequency is 10 Hz. The time interval at which the counted pulse should be acquired must be approximately half of the counted pulse duration, in other words, an interval of approx. 25 ms is used for a 50 ms pulse. For this time-driven counted pulse acquisition, OB35 must be programmed for an S7-300 CPU and one of the available cyclic interrupt OBs, OB30 to OB38, for an S7-400 CPU. Although all of the cyclic interrupt OBs have a preset time interval (for example, 100 ms for OB35), this can be changed in 1 ms steps. For example, a cyclic interrupt OB can be set to 25 ms. The figure below shows how to change the time interval for a cyclic interrupt OB in the HW Config Properties dialog for the CPU.

Figure 3-24 Changing the time interval for cyclic interrupt OB35



The program structure in a cyclic interrupt OB The structure of the SINAUT program in the cyclic interrupt OB is as follows:

Cyclic interrupt OB

PulseCounter • One or more PulseCounter FCs can be inserted for acquisition of counted pulses. FC PulseCounter works with up to 8 pulse inputs from any type of digital input. The acquired counted pulses are accumulated in configurable SIMATIC counters that are available to the function blocks that put together the counted value messages (FB Cnt..._S, FB ZTZ..). For more detailed information, refer to the description of the SINAUT program structure in OB1.

• User-specific cyclic interrupt functions that are required independent of the SINAUT program, can be inserted at any location in the cyclic interrupt OB.

3.3.4 SINAUT test routine in the programming error OB121

Introduction When a non-existent block is called in a CPU, the CPU usually changes to STOP and the missing block (FBxx, FCyy or DBzz) is indicated in the diagnostics buffer. You can then load the missing block and restart the CPU. If you want to avoid the CPU stopping when there is a missing block, or only changing to STOP when certain block types or block numbers are missing, you can specify the type of response you require in OB121 with a user program. The CPU will continue to operate despite a missing block simply by loading OB121 even it contains nothing. If you want to specify when the CPU should continue and when it should stop, you will need to include an appropriate user program in OB121. In conjunction with SINAUT ST7, it is possible that a CPU will stop if it receives a message that it does not know (or does not yet know) from another CPU. For example, when you add a datapoint typical to a station and assign it a complete destination address (destination subscriber number plus destination object number). The set destination object number may result in a stop on the destination subscriber because the message is transmitted to the destination as soon as the new datapoint typical is installed in the station. If, however, the corresponding receive typical has not yet been installed in the destination CPU, the destination object number (instance DB of the receive typical to be installed) is also not yet available. The result is that the CPU stops as soon as this message is received, unless you have configured OB121 to avoid this. For SINAUT ST7 CPUs it is recommended that you call the FC ST7ObjectTest function in OB121. Then the CPU does not stop when a SINAUT object DB is not available as in the example described. FC ST7ObjectTest has a StopInOtherCases parameter. It allows you to specify what should occur in other situations: Stop or continue operation when OB121 is called because another data block, an FB or an FC is missing.

SINAUT TD7 software package for the CPU 3.4 Basic blocks


The program structure in the programming error OB121 The structure of the SINAUT program in the programming error OB121 is as follows:

OB121

ST7ObjectTest • Calling FC ST7ObjectTest in OB121 prevents a CPU stop when the CPU receives a message with an unknown destination object number. FC-ST7ObjectTest has a StopInOtherCases parameter. It allows you to specify what should occur in other situations: Stop or continue operation when OB121 is called because another data block, an FB or an FC is missing.

• A user-specific cyclic program that is required independent of the SINAUT program can be included at any location in OB121.

3.4 Basic blocks These blocks are needed for organizational tasks within a CPU and for controlling and monitoring all the transmission channels.

3.4.1 FC Startup This block is required in every CPU. It must be included in the startup program OB100. Its only task is to set the startup memory bit in the DB BasicData and reset the corresponding edge memory bit if it is still set. The block has no parameters. In a normally configured SINAUT installation, FC Startup is automatically available in the block directory of the CPU. This happens as soon as you save in the SINAUT configuration tool ’Subscriber Administration’ and the option for compiling the 'SINAUT TD7 Blocks for the CPUs' is marked as active. For more detailed information on the SINAUT startup program, refer to the section 'SINAUT startup program in OB100’.

3.4.2 FC BasicTask

Function This block is required in every CPU. It handles ● The central tasks to be performed during startup ● The processing of all communication channels ● The central organizational tasks such as starting and monitoring general requests,

responding to general requests, etc.



In a normally configured SINAUT installation, FC BasicTask is automatically available in the block directory of the CPU. This happens as soon as you save in the SINAUT configuration tool ’Subscriber Administration’ and the option for compiling the 'SINAUT TD7 Blocks for the CPUs' is marked as active.

Note The FC BasicTask must always be called as the first block in the cyclic SINAUT program (in OB1).

Explanation of the parameters

Name: UserFC Declaration: INPUT Data type: INT Explanation: Number of a user FC for user-specific processing of received SINAUT

messages. Range of

values: 0 or 1 ... 32000

0 = Dummy value in case no user FC is available for the specified purpose.

1 ... 32000 = Number of the user FC. The maximum number possible depends on the CPU where the SINAUT program will run.

If a user FC is specified, this FC will be called automatically by the SINAUT program each time a message is received. At the time of the call, the received message is still in the receive buffer of the communication DB. The user program in the user FC can read the received message from the receive buffer and process it as necessary, for example, transfer it to a temporary buffer. The number of the current communication DB can be read by the user program from DW60 of DB BasicData (symbolic address: CurrentComDB). As soon as the communications DB is opened, the beginning of the receive message in the receive buffer can be found with the pointer in DW10 (symbolic address: CurrentReceivedMessage). There is a separate description of the structure of a message available in the receive buffer.



Figure 3-25 DB-BasicData, DW60 CurrentComDB Number of the current communication DB

Figure 3-26 Current communication DB, DW10 CurrentReceivedMessage,

Pointer to the start of the current received message in the receive buffer

3.4.3 DB BasicData This data block handles the central data storage; in other words, information that needs to be kept at a central location for all blocks. Among other things, the data block includes the subscriber records and the connection descriptions. DB BasicData is automatically created with the necessary length, assigned the data specific to the subscribers and connections and then saved in the block directory of the CPU. This



happens as soon as you save in the SINAUT configuration tool ’Subscriber Administration’ and the option for compiling the 'SINAUT TD7 Blocks for the CPUs' is marked as active. DB BasicData replaces, among other things, the data blocks known from the TD1 package, ’stations record’, ’control center record’, ’interfaces record’ and the TD1 system bit memory address area from MB142 to MB199. DB BasicData is available once on every CPU.

Note In the SINAUT TD7 library, DB BasicData has the number DB127 and is also saved under this number in the CPUs when it is created for them. In principle, it would be possible to change the number but this requires a great deal of effort and may lead to errors when creating the rest of the SINAUT program. We therefore recommend: Leave DB127 free for DB BasicData if at all possible!

3.4.4 FB XCom Auxiliary block for FC BasicTask, for processing a communication buffer of type DB XComData, in which a unconfigured connection (X connection) is handled using the SFCs X_SEND and X_RCV. FB XCom also ensures that received messages are distributed immediately to the corresponding receive objects in the CPU. To do this, FB XCom calls FC Distribute as an auxiliary block. In a normally configured SINAUT installation, FC XCom is automatically available in the block directory of the CPU. This happens as soon as you save in the SINAUT configuration tool ’Subscriber Administration’ and the option for compiling the 'SINAUT TD7 Blocks for the CPUs' is marked as active. During compilation, there is a check to establish the CPU for which the program is being compiled. If an S7-300 CPU is involved, the FB-XCom is entered in the block directory of the CPU. With an S7-400 CPU, this is FB-BCom.

3.4.5 DB XComData Instance data block for the communication block FB XCom. This communication DB contains a receive and a send buffer as well as central data required for the control and management of the X connection handled by this DB. The data block is required in every CPU in which FB XCom is used. It can be inserted several times if the CPU maintains several X connections. DB XComData is automatically created with the necessary length, assigned the data specific to the subscribers and connections and then saved in the block directory of the CPU. This happens as soon as you save in the SINAUT configuration tool ’Subscriber Administration’ and the option for compiling the 'SINAUT TD7 Blocks for the CPUs' is marked as active.



3.4.6 FB-PCom Auxiliary block for FC BasicTask, for processing a communication buffer of type DB-PComData using SFCs WR_REC and RD_REC. Received messages are then distributed immediately to the relevant receive objects in the CPU. This is achieved by FB-PCom calling FC Distribute as an auxiliary block. The FB-PCom block is used only with normal communication over the P bus. This relates to communication between a TIM module and a CPU module of the type series CPU 317 and CPU 319 and the CPU 315-2PN/DP.

3.4.7 DB PComData Instance data block for the communication block FB PCom. This communication DB contains a receive and a send buffer as well as central data required for the control and management of the connection handled by this buffer. The data block is required in every CPU in which FB PCom is used. It can be inserted several times if the CPU maintains several such connections.

3.4.8 FB BCom Auxiliary block for FC BasicTask, for processing a communication buffer of type DB BComData, in which a configured connection (communication block connection) is handled using the SFBs BSEND and BRCV. FB BCom also ensures that received messages are distributed immediately to the corresponding receive objects in the CPU. To do this, FB BCom calls FC Distribute as an auxiliary block. In a normally configured SINAUT installation, FC BCom is automatically available in the block directory of the CPU. This happens as soon as you save in the SINAUT configuration tool ’Subscriber Administration’ and the option for compiling the 'SINAUT TD7 Blocks for the CPUs' is marked as active. During compilation, there is a check to establish the CPU for which the program is being compiled. If an S7-400 CPU is involved, the FB BCom is entered in the block directory of the CPU. With an S7-300 CPU, this is FB XCom.

3.4.9 DB BComData Instance data block for the communication block FB BCom. This communication DB contains a receive and a send buffer as well as central data required for the control and management of the communication block connection handled by this DB. The data block is required in every CPU in which FB BCom is used. It can be inserted several times if the CPU maintains several communication block connections. DB BComData is automatically created with the necessary length, assigned the data specific to the subscribers and connections and then saved in the block directory of the CPU. This happens as soon as you save in the SINAUT configuration tool ’Subscriber Administration’ and the option for compiling the 'SINAUT TD7 Blocks for the CPUs' is marked as active.



3.4.10 FC Create Auxiliary block for putting together messages and entering them in one or more relevant send buffers. This block is required by the data point typicals for data and organizational messages and by FC BasicTask only for organizational messages. This block is required in every CPU. In a normally configured SINAUT installation, FC Create is automatically available in the block directory of the CPU. This happens as soon as you save in the SINAUT configuration tool ’Subscriber Administration’ and the option for compiling the 'SINAUT TD7 Blocks for the CPUs' is marked as active.

3.4.11 FC Distribute Auxiliary block for distributing messages from the receive buffer to the appropriate data point typicals or to the subscriber objects in the subscriber records. This block is required in every CPU. In a normally configured SINAUT installation, FC Distribute is automatically available in the block directory of the CPU. This happens as soon as you save in the SINAUT configuration tool ’Subscriber Administration’ and the option for compiling the 'SINAUT TD7 Blocks for the CPUs' is marked as active.

3.4.12 FC Search Auxiliary block for searching: ● For the initial address of a subscriber object within the subscriber records ● For the local object no. (instance DB) from one of the two object reference lists for a

received message with an incomplete destination address or for a received message in ST1 format

This auxiliary block is required by almost all blocks. This block is required in every CPU. In a normally configured SINAUT installation, FC Search is automatically available in the block directory of the CPU. This happens as soon as you save in the SINAUT configuration tool ’Subscriber Administration’ and the option for compiling the 'SINAUT TD7 Blocks for the CPUs' is marked as active.

3.4.13 FC Diagnose Auxiliary block for entering SINAUT system messages in the diagnostic buffer of the CPU. This block is required in every CPU. In a normally configured SINAUT installation, FC Diagnose is automatically available in the block directory of the CPU. This happens as soon as you save in the SINAUT configuration tool ’Subscriber Administration’ and the option for compiling the 'SINAUT TD7 Blocks for the CPUs' is marked as active.

SINAUT TD7 software package for the CPU 3.5 Data point typicals


3.5 Data point typicals

Introduction Data point typicals consist of one or more data points of the same type, e.g. 4 bytes of binary information, or 4 analog values, or 1 byte commands, etc. Data point typicals for a specific type or amount of information always come in two versions: ● A typical for acquiring and sending

For example, FB Bin04B_S, for acquiring and sending 4 bytes of binary information (status signals);

● A typical for receiving and outputting For example, FB Bin04B_R, for receiving and outputting 4 bytes of binary information (status signals);

All data point typicals are FBs. An instance DB must be specified when an FB is called. The number of this instance DB is identical to the object number of the data point object. At the send and receive ends this object number does not have to be identical.

Structure of typical names Data point typicals have 8-character names based on the following scheme:

Table 3-3 Structure of 8-character typical names

1 2 3 4 5 6 7 8 Column 1 ... 3 Data point type: Bin Binary information

(status signal, alarm) Ana Analog value

Cnt Counted value

Cmd Command

Set Setpoint

(setpoint, parameter) Par Parameter Dat Data

(any mixture of information types)

Column 4 ... 5 Amount of data in the format of column 6.

Data format: X = bit B = byte W = word D = double word R = real

Not used (filled by underscore)

S = send function R = receive function

The table above relates to the name structure for ST7 typicals. For data point typicals used with ST1 installations, the standard names of corresponding ST1 function blocks have been adopted, e.g. MTZ01, MTA01, ATZ01, ATA01, ZTZ01 etc.



Overview of the available data point typicals The following table provides an overview of the currently available data point typicals. There are variants for SINAUT ST7 and for the previous SINAUT ST1 protocol: ● ST7 Data point typical for data exchange between two SINAUT ST7 subscribers ● ST1 Data point typical for data exchange between a SINAUT ST7 and a SINAUT ST1

subscriber (station or master station)

Table 3-4 Overview of the available data point typicals

SINAUT protocol Symbolic FB name

Explanation

Message typicals Bin04B_S ST7 status message object, send 4 bytes of

status/binary information ST7

Bin04B_R ST7 status message object, receive 4 bytes of status/binary information

MTZ01 Send ST1 status message with 4 bytes of status/binary information

MTA01 Receive ST1 status message with 4 bytes of status/binary information

MTZ02 Send ST1 status message with 2 bytes of status/binary information

ST1

MTA02 Receive ST1 status message with 2 bytes of status/binary information

Analog value typicals Ana04W_S ST7 analog value object, send 4 analog values (16-bit

value in the INT format) ST7

Ana04W_R ST7 analog value object, receive 4 analog values (16-bit value in the INT format)

ATZ01 Send ST1 analog value message with 4 analog values (16-bit ST1 format)

ATA01 Receive ST1 analog value message with 4 analog values (16-bit ST1 format)

ATZ03 Send ST1 analog value message with 8 analog values (16-bit ST1 format)

ST1

ATA02 Receive ST1 analog value message with 8 analog values (16-bit ST1 format)

Counted value typicals Cnt01D_S ST7 counted value object, send 1 counted value (32-bit

ST1 format) Cnt01D_R ST7 counted value object, receive 1 counted value (32-

bit ST1 format) Cnt04D_S ST7 counted value object, send 4 counted values (32-

bit ST1 format)

ST7

Cnt04D_R ST7 counted value object, receive 4 counted values (32-bit ST1 format)

ST1 ZTZ01 Send ST1 counted value message with 1 counted value (32-bit ST1 format)



SINAUT protocol Symbolic FB name

Explanation

ZTA01 Receive ST1 counted value message with 1 counted value (32-bit ST1 format)

ZTZ02 Send ST1 counted value message with 2 counted values (32-bit ST1 format)

ZTA02 Receive ST1 counted value message with 2 counted values (32-bit ST1 format)

ZTZ03 Send ST1 counted value message with 4 counted values (32-bit ST1 format)

ST1

ZTA03 Receive ST1 counted value message with 4 counted values (32-bit ST1 format)

Command typicals Cmd01B_S ST7 command object, send 1 byte commands (1-out-

of-8 ST1 format) ST7

Cmd01B_R ST7 command object, receive 1 byte commands (1-out-of-8 ST1 format)

BTZ01 Send ST1 command message with 1 byte commands (1-out-of-8 ST1 format)

ST1

BTA01 Receive ST1 command message with 1 byte commands (1-out-of-8 ST1 format)

Setpoint/parameter typicals Set01W_S ST7 setpoint object, receive 1 setpoint (16 bits) and

receive current local setpoint Set01W_R ST7 setpoint object, receive 1 setpoint (16 bits) and

send current local setpoint Par12D_S ST7 parameter object, send max. 12 double words with

parameters and receive current local parameters.

ST7

Par12D_R ST7 parameter object, receive max. 12 double words with parameters and send current local parameters.

STZ01 Send ST1 setpoint message with 1 setpoint (16-bit ST1 format)

ST1

STA01 Receive ST1 setpoint message with 1 setpoint (16-bit ST1 format)

Other data typicals Dat12D_S ST7 data object, send max. 12 double words with any

information. ST7

Dat12D_R ST7 data object, receive max. 12 double words with any information.

STKOP26W Send ST1 data message with max. 26 words of any information.

ST1

ETKOP26W Receive ST1 data message with max. 26 words of any information.

Notes on the SINAUT Time stamp For many data point typicals you can use the TimeStamp parameter to instruct that the data object should be transferred with a time stamp. However for the data point typicals used to receive this data there is no output parameter with which to output the received time stamp.



The time stamp is only saved in the instance DB which you have specified when calling the respective receive typical. This occurs in two data double words that always have the same name in all instance DBs (SINAUT object DB), namely:

Name of the double word Contents RecTimeStamp_1 Year, month, day and hour RecTimeStamp_2 Minute, second, millisecond and time status

The date and time of day is coded in BCD format (exception: the half byte with the time status). The exact byte-for-byte content appears as follows:

Contents Name of the double

word Byte no.

High nibble Low nibble 0 Year * 10 Year * 1 1 Month * 10 Month * 1 2 Day * 10 Day * 1

RecTimeStamp_1

3 Hour * 10 Hour * 1 0 Minute * 10 Minute * 1 1 Second * 10 Second * 1 2 Millisecond * 100 Millisecond * 10

RecTimeStamp_2

3 Millisecond * 1 Time status

The content of the half byte with the time status bit::

Bit place Value Meaning

0 Time is invalid 20 1 Time is valid 0 Standard time 21 1 Daylight saving time

22 Not used 23 Not used

The time double words occupy different addresses depending on the typical. Look in the instance DB or in the declaration header of the FB to find the absolute address of both double words. It is more convenient to give the instance DBs symbolic names. You can then use the symbolic addresses to read out the information. In this case, you do not need to worry about the actual absolute addresses. These are used automatically by STEP 7. The following example clarifies this procedure. Example Symbolic name of instance DB: ObjectDB27 The STEP 7 program for reading the date and time of day and for saving in DB20 beginning with data byte 100 may appear as follows programmed in STL: L"ObjectDB27".RecTimeStamp_1 TDB 20.DBD 100 L"ObjectDB27".RecTimeStamp_2 TDB 20.DBD 104



Notes on explanation of the parameters The detailed descriptions of the blocks in most of the following contain an "Explanation of the parameters" section. The following information is available there for each parameter:

Name: Name of the parameter Declaration: SIMATIC parameter type INPUT, OUTPUT or IN_OUT Data type: SIMATIC data type

The data types used: BOOL, BYTE, WORD, DWORD, INT, DINT, ANY, COUNTER and BLOCK_DB

Default (only applicable for FB parameters Default value for the parameter. This value is valid when the parameter is not specified when the FB is called.

Explanation: Detailed description of the parameter and specification of the allowable value range.

Note The data point typicals are described in detail in the following pages. Data point typicals that are identical except for the number of data points to be processed are included in a single description. If there is a difference in the function or in the parameters, the block for which the described function or parameter is valid is shown in square brackets, for example, [Cnt01D_S].

3.5.1 ST7 binary information typical FB Bin04B_S

Function Send 4 bytes of messages/binary information


Name: PartnerNo Declaration: INPUT Data type INT Default: 0



Explanation Subscriber no. of the partner. Range of values: 0 or 1 ... 32000 The subscriber number of the partner with which the FB communicates, i.e. to which the FB sends data, must be specified. For a process typical such as Bin04B_S, this is usually the subscriber no. of the master PLC or the ST7cc control center. Point to note with PartnerNo = 0 The data is transmitted to all subscribers for which a connection has been configured. The following PartnerObjectNo parameter is then irrelevant. If the set PartnerNo was not found in the administration (in DB-BasicData), an entry to this effect is made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.

Note When using the block in the PLC of a node station, you should consider the consequences of PartnerNo = 0! If the PLC of the node station maintains both connections to higher-level subscribers as well as to lower-level stations, a message with PartnerNo = 0 is transferred to all subscribers both "up" and "down".

Name: PartnerObjectNo Declaration: INPUT Data type INT Default: 0 Explanation Object number of the partner.

Range of values: 0 or 1 ... 32000 The number of the object (= DB number) on the partner with which the FB communicates, i.e. to which the FB sends data, must be specified. Point to note with PartnerObjectNo = 0 This parameter assignment is useful, if PartnerNo = 0 was set. If the PartnerObjectNo is missing, there must be a list on the partner PLC from which the missing object number can be recognized (see FC ListGenerator). If the subscriber specified by PartnerNo is an ST7cc control center, the PartnerObjectNo does not need to be specified in the FB because there are no DBs as destination objects in ST7cc as there are in a CPU. ST7cc decodes its messages solely based on the source address in the message.

Name: Enabled Declaration: INPUT Data type BOOL



Default: TRUE Explanation Enable block processing.

TRUE or FALSE No parameter specified: Default TRUE is valid

Range of values:

Input Bit memory Data bit

I 0.0 ... I n.7 M 0.0 ... M n.7 L 0.0 ... L n.7 DBm.DBX 0.0 ... n.7

Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is not enabled, the FB can only communicate at the organizational level; in other words, ORG messages can be sent and received. A query is, for example, answered, however the reply message contains the data valid at the time the function was disabled.

Name: ImageMemory Declaration: INPUT Data type BOOL Default: TRUE Explanation Image memory principle for spontaneous data transmission.

Range of values: TRUE or FALSE No parameter specified: Default value TRUE is valid. Here, you must specify whether the message is transferred according to the image memory principle or, if this is not the case, according to the send buffer principle. The image memory principle means that messages can be stored using less memory on the TIM and the traffic on the WAN is as low as possible. The default TRUE was chosen because the image memory principle is the best choice in practice for most data transmissions. In general, as the user you only need to change the default setting of the image memory parameter with a few objects, namely objects whose data changes must be stored on the TIM and sent to the partner singly, for example alarms with time stamp.

Name: Conditional Declaration: INPUT Data type BOOL Default: TRUE



Explanation Conditional spontaneous data transmission Range of values: TRUE or FALSE No parameter specified: Default value TRUE is valid. You will find information on the parameter assignment in the Unconditional parameter.

Name: Unconditional Declaration: INPUT Data type BOOL Default: FALSE Explanation Unconditional spontaneous data transmission.

Range of values: TRUE or FALSE No parameter specified: Default value FALSE is valid. Note on the use of the Conditional and Unconditional parameter settings: With the two parameters Conditional and Unconditional, you can decide whether a message is transmitted by the TIM immediately when data changes or at a later point in time. 1. If the transmission does not need to be made immediately, set the

parameters as follows: Conditional = TRUE Unconditional = FALSE

2. If you require immediate transmission, the parameter combination should be: Conditional = FALSE Unconditional = TRUE

The decision for immediate or later transmission only relates to dial-up networks. On a dedicated line, the transmission is always immediate even if the combination of Conditional and Unconditional is set to "not immediately".The default of the two parameters was chosen so that a message is not transmitted immediately (combination 1). On dedicated lines, you as the user do not need to make changes to the two parameter settings. Only in a dial-up network, do you need to decide which objects are so important that an immediate transmission is necessary if there is a change in the acquired data for the object. Only then do you need to change Conditional to FALSE and Unconditional to TRUE, for example for an object with alarms.

Name: Permanent Declaration: INPUT Data type BOOL Default: FALSE Explanation Permanent data transmission.

This parameter has no significance. The functionality of permanent data transmission is not supported by the TIM.



Note The "Permanent" parameter is no longer implemented, it has been retained to ensure compatibility.

Name: TimeStamp Declaration: INPUT Data type BOOL Default: FALSE Explanation Time stamp.

Range of values: TRUE or FALSE No parameter specified: Default value FALSE is valid. Here, you specify whether the message is transferred with the time stamp. The prerequisite is that the time provided by the local TIM is available on the PLC. For more detailed information, refer to the description of FC TimeTask. If no parameter is specified, the default is FALSE; in other words, data is transmitted without a time stamp.

Name: InputByte_1 … _4 Declaration: INPUT Data type BYTE Default: 0 (B#16#0) Explanation Input byte

Input byte IB0 ... IBn PIB0 ... PIBn

Memory bytes Data bytes

MB0 ... MBn LB0 ... LBn DBm.DBB0 ... n

Range of values:

No parameter specified: Default value 0 is valid. You can specify the bytes from where the binary information such as status

messages, alarms etc. is taken by the FB to be transferred in the data messages. Input bytes from the process input image, I/O bytes directly from digital input modules, data bytes from a data block and memory bytes can be mixed as required. If you do not require parameters, simply leave them open. The value 0 is transferred for these bytes in the message.

Name: DisableMask Declaration: INPUT Data type DWORD Default: 0 (2#0)



Explanation Disable mask Range of

values: As 32-bit binary number 2#0 ... 2#11111111_11111111_11111111_11111111 As 32-bit hex number DW#16#0 ... DW#16#FFFF_FFFF No parameter specified: Default value 0 (2#0) is valid

A 1 must be entered in the bit pattern that the position of each input to be disabled; 0 is entered for the other inputs. The assignment of the 32 inputs of the parameters InputByte_1 through InputByte_4 to the 32 bits in the bit pattern of the DisableMask parameter is shown in the following table. A disabled input always has the value 0 in the message.

InputByte_1 InputByte_2 InputByte_3 InputByte_4

Bit .7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0

2# _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ DW#16# _ _ _ _ _ _ _ _

Name: InversionMask Declaration: INPUT Data type DWORD Default: 0 (2#0) Explanation Inversion mask Range of

values: As 32-bit binary number 2#0 ... 2#11111111_11111111_11111111_11111111 As 32-bit binary number DW#16#0 ... DW#16#FFFF_FFFF No parameter specified: Default value 0 (2#0) is valid.

A 1 must be entered in the bit pattern that the position of each input to be inverted; 0 is entered for the other inputs. The assignment of the 32 inputs of the parameters InputByte_1 through InputByte_4 to the 32 bits in the bit pattern of the InversionMask parameter is shown in the following table. The inversion of input signals can, for example, be useful when using a mixture of sensors operating on the open and closed circuit principle.


Bit .7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0

2# _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ DW#16# _ _ _ _ _ _ _ _



3.5.2 ST7 binary information typical FB Bin04B_R

Function Receive 4 bytes of status/binary information


Name: PartmerNo Declaration: INPUT Data type: INT Default 0 Explanation: Subscriber no. of the partner.

Range of values: 1 ... 32000 The subscriber number of the partner with which the FB communicates, i.e. from which the FB receives data, must be specified. With an operator typical such as Bin04B_R, this is normally the subscriber number of a station PLC. The parameter setting PartnerNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 32000), an error message to this effect is entered in the diagnostic buffer (event ID B100). If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected. If the PLC receives a message for the object set here, the system checks whether the source subscriber number in the message is identical to the PartnerNo set here. If they are different, the received information is discarded. An error message to this effect is entered in the diagnostic buffer (event ID B130).

Name: PartmerObjectNo Declaration: INPUT Data type: INT Default 0



Explanation: Object number of the partner. Range of values: 1 ... 32000 The number of the object (= DB number) on the partner with which the FB communicates, i.e. from which the FB receives data, must be specified. The parameter setting PartnerObjectNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 32000), an error message to this effect is entered in the diagnostic buffer (event ID B102). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected. If the PLC receives a message for the object set here, the system checks whether the source object number in the message is identical to the PartnerObjectNo set here. If they are different, the received information is discarded. An error message to this effect is entered in the diagnostic buffer (event ID B131).

Name: Enabled Declaration: INPUT Data type BOOL Default: TRUE Explanation Enable block processing.


Range of values:



Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is not enabled, the FB can only communicate at the organizational level; in other words, ORG messages can be sent and received. A query can, for example, still be sent and the answer received, the received information is, however, not output to the output bytes OutputByte_1 through OutputByte_4.

Name: OutputByte_1 … _4 Declaration: OUTPUT Data type BYTE Default: 0 (B#16#0) Explanation Output byte Range of

values: Output byte Memory bytes Data bytes

QB0 ... Qbn PQB0 ... PQBn MB0 ... MBn LB0 ... LBn DBm.DBB0 ... n



Where the binary information such as status messages, alarms etc is to be output can be selected byte by byte. Output bytes in the process output image, I/O bytes directly on digital output modules, data bytes of a data block and memory bytes can be mixed as required. How to read out the time stamp received with the data is described in the section Notes on the SINAUT time stamp. If you do not require parameters, simply leave them open.

Name: NewData Declaration: OUTPUT Data type BOOL Default: FALSE Explanation Receive new data. Range of

values: Output Bit memory Data bit

Q 0.0 ... Q n.7 M 0.0 ... M n.7 L 0.0 ... L n.7 DBm.DBX 0.0 ... n.7

Whenever the FB has received new data and has output it to the output bytes OutputByte_1 through OutputByte_4, the NewData output is set to TRUE for one OB1 cycle. The output is intended for user-specific further processing, for example to react in a specific way to receipt of new data. If you do not require the parameter, simply leave it open.

3.5.3 ST1 binary information typicals FB MTZ01 and FB MTZ02

Function [MTZ01] send 4 bytes of status/binary information in a message with ST1 format. [MTZ02] send 2 bytes of status/binary information in a message with ST1 format.


Name: PartnerNo Declaration: INPUT Data type: INT Default 0



Explanation: Subscriber no. of the partner. Range of values: 0, 1 ... 8 or 1 ... 254 The subscriber number of the partner with which the FB communicates, i.e. to which the FB sends data, must be specified. With a process typical such as MTZ01 or MTZ02, this is normally the subscriber number of the ST1 master. If MTZ01 or MTZ02 is used in the reverse transmission direction (see ReverseDirection parameter), the subscriber number of an ST1 station must be specified. Partner is the ST1 master: Range of values limited to 1 ... 8 (= ST1 master number) Partner is the ST1 station: Range of values limited to 1 ... 254 (= ST1 station number) Partner is ST7/ST7cc: Range of values limited to 1 ... 254 (= SINAUT ST7 subscriber number) Point to note with PartnerNo = 0 If MTZ01 or MTZ02 is used in a station; in other words not in the reverse transmission direction (ReverseDirection = FALSE), the parameter setting PartnerNo = 0 is also permitted with MTZ01 and MTZ02. The data is then transferred to all subscribers to which a connection was configured; in other words, to all ST1 masters. If the parameter setting is incorrect (< 0 or > 8 or > 254), an error message to this effect is entered in the diagnostic buffer (event ID B100). If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.


Name: ST1_MessageNo Declaration: INPUT Data type: INT Default 0



Explanation: Message number for a message in ST1 format. Range of values: 2 ... 250 The message number of the ST1 message to be sent must be specified. The parameter must be set by the user in all situations. If the parameter is missing (default value 0 applies) or if the value is < 2 or > 250, a message to this effect is entered in the diagnostic buffer (event ID B103). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.

Note ST1_MessageNo = 1 is not permitted! This message number is reserved for the error message in ST1.

Name: ST1_ObjectNo Declaration: INPUT Data type: INT Default 0 Explanation: Object number for a message in ST1 format.

Range of values: 0 or 1 ... 255 If a value higher than 0 is set, this is an ST1 message with an address expansion. This expanded addressing is not normally required; only in conjunction with the SINAUT LSX control center system. If the parameter setting is incorrect (< 0 or > 255), an error message to this effect is entered in the diagnostic buffer (event ID B104). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.

Name: ST1_IndexNo Declaration: INPUT Data type: INT Default 0



Explanation: Index number for a message in ST1 format. Range of values: 0 ... 255 A value higher than 0 is permitted only when a value higher than 0 was also set for ST1_ObjectNo; in other words, an ST1 message with address expansion is to be transmitted. This expanded addressing is not normally required; only in conjunction with the SINAUT LSX control center system. If the parameter setting is incorrect (< 0 or > 255), an error message to this effect is entered in the diagnostic buffer (event ID B105). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.

Name: ST1_PACK_Value Declaration: INPUT Data type: INT Default 0 Explanation: PACK value for a message in ST1 format with address expansion.

An ST1 message transferred with the expanded addresses object and index number (ST1_ObjectNo, ST1_IndexNo) can contain data for several objects. Only the number of the first object is transferred with the message. The numbers of the other objects are assigned without gaps beginning at this start object. The packing scheme; in other words, how many bits belong to a single message object, is transferred in the message with the PACK value. Based on this PACK value, the ST1 message is then converted into several KOMSYS-X messages for SINAUT LSX in the master: One KOMSYS-X message per object with the amount of data specified with PACK. If the additional addresses ST1_ObjectNo and ST1_IndexNo are used, a setting must be made here with the ST1_PACK_Value parameter indicating the number of bits per message object (pack interval).

[MTZ01] Range of values: 4, 8, 16, 32 [bits] No parameter specified: Default value 0 is valid; corresponds to 32 bits

4 = 4 bits per object (the message contains 8 objects each 4 bits) 8 = 8 bits per object (the message contains 4 objects each 8 bits) 16 = 16 bits per object (the message contains 2 objects each 16 bits) 32 = 32 bits per object (the message contains 1 object of 32 bits) The assignment of the message inputs to the object numbers depending on the packing scheme:

InputByte_1 InputByte_2

.7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0 ST1_ObjectNo + 1 ST1_ObjectNo ST1_ObjectNo +3 ST1_ObjectNo +2


.7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0 ST1_ObjectNo +5 ST1_ObjectNo +4 ST1_ObjectNo +7 ST1_ObjectNo +6



ST1_PACK_Value = 4 The message contains 8 objects each with 4 bits. The figure shows the assignment of the 4 inputs to the object numbers. In the master station, 8 object messages each with a 16-bit message word are transferred to LSX. In this message word, only bits 0 to 3 have object information, bits 4 to 15 are set to 0.

InputByte_1 InputByte_2 .7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0

ST1_ObjectNo


ST1_ObjectNo + 1



ST1_ObjectNo


ST1_ObjectNo + 1

ST1_PACK_Value = 16

The message contains 2 objects each with 16 bits. The figure shows the assignment of the 16 inputs to the object numbers. In the master station, 2 object messages each with a 16-bit message word are transferred to LSX. This message word contains the object information of InputByte_1 + _2 or InputByte_3 + _4 as shown in the figure. If PACK = 32, 1 object message with two 16-bit message words is transferred to LSX in the master station. The first message word contains the information from InputByte_1 + InputByte_2 and the second message word the information from InputByte_3 + InputByte_4.



[MTZ02] Range of values: 4, 8, 16, [bits] No parameter specified: Default value 0 is valid; corresponds to 16 bits 4 = 4 bits per object (the message contains 8 objects each 4 bits) 8 = 8 bits per object (the message contains 4 objects each 8 bits) 16 = 16 bits per object (the message contains 2 objects each 16 bits) The assignment of the message inputs to the object numbers depending on the packing scheme:


ST1_ObjectNo + 1 ST1_ObjectNo ST1_ObjectNo +3 ST1_ObjectNo +2



ST1_ObjectNo ST1_ObjectNo + 1



.7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0 ST1_ObjectNo



ST1_PACK_Value = 16 The message contains 1 object with 16 bits. The figure shows the assignment of the 16 inputs to the object number. In the master station, 1 object message with a 16-bit message word is transferred to LSX. This message word contains the object information of InputByte_1 + _2 as shown in the figure.

Note Depending on ST1_PACK_Value, several object numbers are 'hidden' in the message. These are easy to overlook when assigning expanded addresses. The combination of ST1_MessageNo + ST1_ObjectNo + ST1_IndexNo may only exist once in a station!

For more detailed information on the ST1 object number and ST1 index

number and the packing scheme, refer to the SINAUT TD1/RX manual. If the parameter setting is incorrect (PACK values other than 0, 4, 8, 16 or 32), an error message to this effect is entered in the diagnostic buffer (event ID B106). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.



Range of values:






Name: ImageMemory Declaration: INPUT Data type BOOL Default: TRUE Explanation Image memory principle for spontaneous data transmission.

Range of values:


Here, you must specify whether the message is transferred according to the image memory principle or, if this is not the case, according to the send buffer principle. The image memory principle means that messages can be stored using less memory on the TIM and the traffic on the WAN is as low as possible. The default TRUE was chosen because the image memory principle is the best choice in practice for most data transmissions. In general, as the user you only need to change the default setting of the image memory parameter with a few objects, namely objects whose data changes must be stored on the TIM and sent to the partner singly, for example alarms with time stamp.

Name: Conditional Declaration: INPUT Data type BOOL Default: TRUE Explanation Conditional spontaneous data transmission

Range of values:


You will find information on the parameter assignment in the Unconditional parameter.

Name: Unconditional Declaration: INPUT Data type BOOL Default: FALSE Explanation Unconditional spontaneous data transmission. Range of

values: TRUE or FALSE No parameter specified: Default TRUE is valid



Note on the use of the Conditional and Unconditional parameter settings: With the two parameters Conditional and Unconditional, you can decide whether a message is transmitted by the TIM immediately when data changes or at a later point in time. 1. If the transmission does not need to be made immediately, set the




Name: Permanent Declaration: INPUT Data type BOOL Default: FALSE Explanation Permanent data transmission.

Range of values:

TRUE or FALSE No parameter specified: Default value FALSE is valid



Name: TimeStamp Declaration: INPUT Data type BOOL Default: FALSE Explanation Time stamp



Range of values:


Here, you specify whether the message is transferred with the time stamp. The prerequisite is that the time provided by the local TIM is available on the PLC. For more detailed information, refer to the description of FC TimeTask. If no parameter is specified, the default is FALSE; in other words, data is transmitted without a time stamp.

Name: ReverseDirection Declaration: INPUT Data type BOOL Default: FALSE Explanation Time stamp

Range of values:


Here, you specify whether the ST1 message is sent in the reverse direction (also known as the reverse measurement/monitoring direction); in other words, from the master station to the station. The FB requires this information to determine whether the message addresses set in the FB are to be interpreted as source or destination addresses since ST1 messages have only one source or one destination address depending on the transmission direction. If no parameter is specified, the default is FALSE; in other words, the data is transmitted in the 'normal' direction from station to master station.

Name: [MTZ01] InputByte_1 ... _4 [MTZ02] InputByte_1 ... _2

Declaration: INPUT Data type BYTE Default: 0 (B#16#0) Explanation Input byte

Input byte Memory bytes Data bytes

IB0 ... Ibn PIB0 ... PIBn MB0 ... MBn LB0 ... LBn DBm.DBB0 ... n

Range of values:

No parameter specified: Default value 0 is valid.



You can specify the bytes from where the binary information such as status messages, alarms etc. is taken by the FB to be transferred in the data messages. Input bytes from the process input image, I/O bytes directly from digital input modules, data bytes from a data block and memory bytes can be mixed as required. Parameters that are not required are simply left open. The value 0 is transferred for these bytes in the message.

Name: [MTZ01] DisableMask Declaration: INPUT Data type DWORD Default: 0 (2#0) Explanation Disable mask. Range of


A 1 must be entered in the bit pattern that the position of each input to be disabled; 0 is entered for the other inputs. The assignment of the 32 inputs of the parameters InputByte_1 through InputByte_4 to the 32 bits in the bit pattern of the DisableMask parameter is shown in the following table. A disabled input always has the value 0 in the message.


Bit .7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0

2# _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ DW#16# _ _ _ _ _ _ _ _

Name: [MTZ01] DisableMask Declaration: INPUT Data type WORD Default: 0 (2#0) Explanation Disable mask. Range of

values: As 16-bit binary number 2#0 ... 2#11111111_11111111 As 16-bit hexadecimal number W#16#0 ... W#16#FFFF No parameter specified: Default value 0 (2#0) is valid.



A 1 must be entered in the bit pattern that the position of each input to be disabled; 0 is entered for the other inputs. The assignment of the 16 inputs of the parameters InputByte_1 and InputByte_2 to the 16 bits in the bit pattern of the DisableMask parameter is shown in the following table. A disabled input always has the value 0 in the message.


Bit .7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0 2# _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

DW#16# _ _ _ _

Name: [MTZ01] InversionMask Declaration: INPUT Data type DWORD Default: 0 (2#0) Explanation Inversion mask. Range of


A 1 must be entered in the bit pattern that the position of each input to be inverted; 0 is entered for the other inputs. The assignment of the 32 inputs of the parameters InputByte_1 through InputByte_4 to the 32 bits in the bit pattern of the InversionMask parameter is shown in the following table. The inversion of input signals can, for example, be useful when using a mixture of sensors operating on the open and closed circuit principle.


Bit .7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0

2# _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ DW#16# _ _ _ _ _ _ _ _

Name: [MTZ02] InversionMask Declaration: INPUT Data type WORD Default: 0 (2#0) Explanation Inversion mask.



Range of values:

As 16-bit binary number 2#0 ... 2#11111111_11111111 As 16-bit hexadecimal number W#16#0 ... W#16#FFFF No parameter specified: Default value 0 (2#0) is valid.

A 1 must be entered in the bit pattern that the position of each input to be inverted; 0 is entered for the other inputs. The assignment of the 16 inputs of the parameters InputByte_1 and InputByte_2 to the 16 bits in the bit pattern of the InversionMask parameter is shown in the following table. The inversion of input signals can, for example, be useful when using a mixture of sensors operating on the open and closed circuit principle.


Bit .7 .6 .5 .4 .3 .2 .1 .0 .7 .6 .5 .4 .3 .2 .1 .0 2# _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

DW#16# _ _ _ _

3.5.4 ST1 binary information typicals FB MTA01 and FB MTA02

Function [MTA01] receive 4 bytes of status/binary information from a message with ST1 format. [MTA02] receive 2 bytes of status/binary information from a message with ST1 format.


Name: PartnerNo Declaration: INPUT Data type INT Default: 0 Explanation Subscriber no. of the partner. Range of

values: 1 ... 254 or 1 ... 8



The subscriber number of the partner with which the FB communicates, i.e. from which the FB receives data, must be specified. With an operator typical such as MTA01 or MTA02, this is normally the subscriber number of the ST1 station. If MTA01 or MTA02 is used in the reverse transmission direction (see ReverseDirection parameter), the subscriber number of the ST1 master station must be specified. Partner is the ST1 station: Range of values limited to 1 ... 254 (= ST1 station number) Partner is the ST1 master: Range of values limited to 1 ... 8 (= ST1 master number) Partner is ST7/ST7cc: Range of values limited to 1 ... 254 (= SINAUT ST7 subscriber number) The parameter setting PartnerNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 254 or > 8), an error message to this effect is entered in the diagnostic buffer (event ID B100). If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected. If the PLC receives a message for the object set here, the system checks whether the source subscriber number in the message is identical to the PartnerNo set here. If they are different, the received information is discarded. An error message to this effect is entered in the diagnostic buffer (event ID B130).

Name: ST1_MessageNo Declaration: INPUT Data type INT Default: 0 Explanation Message number for a message in ST1 format. Range of

values: 2 ... 250

The message number of the ST1 message to be received must be specified. The parameter must be set by the user in all situations. If the parameter is missing (default value 0 applies) or if the value is < 2 or > 250, a message to this effect is entered in the diagnostic buffer (event ID B103). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.




Name: ST1_ObjectNo Declaration: INPUT Data type INT Default: 0 Explanation Object number for a message in ST1 format. Range of

values: 0 or 1 ... 255

If a value higher than 0 is set, this is an ST1 message with an address expansion. This expanded addressing is not normally required; only in conjunction with the SINAUT LSX control center system. If the parameter setting is incorrect (< 0 or > 255), an error message to this effect is entered in the diagnostic buffer (event ID B104). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.

Name: ST1_IndexNo Declaration: INPUT Data type INT Default: 0 Explanation Index number for a message in ST1 format. Range of

values: 0 ... 255

A value higher than 0 is permitted only when a value higher than 0 was also set for ST1_ObjectNo; in other words, an ST1 message with address expansion is to be received. This expanded addressing is not normally required; only in conjunction with the SINAUT LSX control center system. If the parameter setting is incorrect (< 0 or > 255), an error message to this effect is entered in the diagnostic buffer (event ID B105). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.



Range of values:





Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is not enabled, the FB can only communicate at the organizational level; in other words, ORG messages can be sent and received. A query can, for example, still be sent and the answer received, the received information is, however, not output to the output bytes OutputByte_1 through OutputByte_4.

Name: ReverseDirection Declaration: INPUT Data type BOOL Default: FALSE Explanation Transmission in the reverse direction. Range of

values: TRUE or FALSE No parameter specified: Default value FALSE is valid.

Here, you specify whether the ST1 message is to be received in the reverse direction (also known as the reverse measurement/monitoring direction); in other words, is transmitted from the master station to the station. The FB requires this information to determine whether the message addresses set in the FB are to be interpreted as source or destination addresses since ST1 messages have only one source or one destination address depending on the transmission direction. If no parameter is specified, the default is FALSE; in other words, the data is transmitted in the 'normal' direction from station to master station.

Name: [MTA01] OutputByte_1 ... _4 [MTA02] OutputByte_1 ... _2

Declaration: OUTPUT Data type BYTE Default: 0 (B#16#0) Explanation Output byte. Range of

values: Output bytes Memory bytes Data bytes

QB0 ... Qbn PQB0 ... PQBn MB0 ... MBn LB0 ... LBn DBm.DBB0 ... n

Where the binary information such as status messages, alarms etc is to be output can be selected byte by byte. Output bytes in the process output image, I/O bytes directly on digital output modules, data bytes of a data block and memory bytes can be mixed as required. How to read out the time stamp received with the data is described in the section Notes on the SINAUT time stamp. If you do not require parameters, simply leave them open.






Whenever the FB has received new data and has output it to the output bytes OutputByte_1 through OutputByte_4, the NewData output is set to TRUE for one OB1 cycle. The output is intended for user-specific further processing, for example to react in a specific way to receipt of new data. If you do not require the parameter, simply leave it open.

3.5.5 ST7 analog value typical FB Ana04W_S

Function Send 4 analog values (16-bit value in the INT format). FB Ana04W_S transfers the 4 analog values: ● As instantaneous values

At the time of the transmission, the currently pending analog value is acquired and transferred to the partner. or

● As mean values The pending analog value is accumulated at selectable intervals. At the time of the transmission, a mean value is formed from the total value and transferred to the partner.

Note The processing parameters such as threshold, smoothing factor etc. exist only once in a typical. These parameters apply to all 4 analog values in common; in other words, it is not possible to set the parameters for the individual analog values. For this reason, each typical should only acquire analog values that can be processed in the same way.





Explanation Subscriber no. of the partner. Range of

values: 0 or 1 ... 32000

The subscriber number of the partner with which the FB communicates, i.e. to which the FB sends data, must be specified. For a process typical such as Ana04W_S, this is usually the subscriber no. of the master PLC or the ST7cc control center. Point to note with PartnerNo = 0 The data is transmitted to all subscribers for which a connection has been configured. The following PartnerObjectNo parameter is then irrelevant. If the set PartnerNo was not found in the administration (in DB-BasicData), an entry to this effect is made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.


Name: PartnerObjectNo Declaration: INPUT Data type INT Default: 0 Explanation Object no. of the partner. Range of

values: 0 or 1 ... 32000

The number of the object (= DB number) on the partner with which the FB communicates, i.e. to which the FB sends data, must be specified. Point to note on PartnerObjectNo = 0 This parameter assignment is useful, if PartnerNo = 0 was set. If the PartnerObjectNo is missing, there must be a list on the partner PLC from which the missing object number can be recognized (see FC ListGenerator). If the subscriber specified by PartnerNo is an ST7cc control center, the PartnerObjectNo does not need to be specified in the FB because there are no DBs as destination objects in ST7cc as there are in a CPU. ST7cc decodes its messages solely based on the source address in the message.





Range of values:




Name: ImageMemory Declaration: INPUT Data type BOOL Default: TRUE Explanation Image memory principle for spontaneous data transmission. Range of

values: TRUE or FALSE No parameter specified: Default value TRUE is valid.


Name: Conditional Declaration: INPUT Data type BOOL Default: TRUE Explanation Conditional spontaneous data transmission Range of











Name: Permanent Declaration: INPUT Data type BOOL Default: FALSE Explanation Permanent data transmission. Range of






Name: TimeStamp Declaration: INPUT Data type BOOL Default: FALSE Explanation Time stamp. Range of


Here, you specify whether the message is transferred with the time stamp. The prerequisite is that the time provided by the local TIM is available on the PLC. For more detailed information, refer to the description of FC TimeTask. The following applies to the time stamp in the message; • MeanValueGeneration = FALSE (instantaneous values are transmitted in

the message) The time stamp in the message is identical to the time of acquisition of the instantaneous values contained in the message.

• MeanValueGeneration = TRUE (the message contains mean values) The time stamp is identical to the time at which the mean value calculation period was completed. The start of the mean value calculation period is not included in the message. This is, however, identical to the time stamp of the previously transferred mean value message.

If no parameter is specified, the default is FALSE; in other words, data is transmitted without a time stamp.

Name: ThresholdIntegration Declaration: INPUT Data type BOOL Default: FALSE Explanation Threshold value processing according to the integration principle. Range of


With this parameter, you can specify whether the integration principle is used in threshold value processing. If no parameter is specified, the default is FALSE; in other words, threshold values are processed without integration. This corresponds to the previous ST1 procedure. In this case, you can also expect less traffic on the telecontrol line and locally between CPU and TIM (over the MPI bus or party line).

Note When MeanValueGeneration = TRUE, i.e. the analog values are sent as mean values, the ThresholdIntegration parameter has no meaning.



Name: ZeroLimitation Declaration: INPUT Data type BOOL Default: TRUE Explanation Zero limitation. Range of


This parameter allows you to specify whether negative values should be suppressed and replaced with the value 0. If no parameter is specified, the default is TRUE. This means that the lowest value is limited to 0.

Name: TriggerInput Declaration: INPUT Data type BOOL Default: FALSE Explanation Trigger input. Range of

values: Input Bit memory Data bit No parameter specified: Default value FALSE is valid.


If required, this parameter can be used to specify an input over which the user can trigger the transmission *) of the analog value message at any time (signal edge from 0 to 1).

Example: Time-driven analog value transmission with time stamp for supplying an analog value archive in the control center. Note: To prevent these messages with time stamps from being overwritten when saving on the station TIM, the ImageMemory parameter must be set to FALSE.



If the block calculates mean values, the duration of the calculation period is defined by the TriggerInput input. The current period is ended and a new period begun each time a transmission is triggered by this input. The interval between two message triggers therefore determines the duration of the mean value calculation period. FC Trigger can be used for time-driven triggering of a transmission over TriggerInput (for more detailed information, refer to the description of this block). If you do not require the parameter, simply leave it open. Message transmission should then be triggered based on the ThresholdValue and ThresholdIntegration threshold parameters. *) TriggerInput actually only triggers transmission indirectly. With a 0/1 edge at TriggerInput, the message is put together with its current values/mean values and transferred to the local TIM. The TIM is responsible for the actual transmission to the partner. Transmission is immediate over a dedicated line/wireless link; with a dial-up connection, it is possible that the message is saved first on the TIM and sent at a later point in time (for example, because the message is marked as a "conditional spontaneous" message; see the Conditional parameter).

Name: MeanValueGeneration Declaration: INPUT Data type BOOL Default: FALSE Explanation Mean value generation. Range of


With this parameter, you can specify whether the analog values to be acquired are transferred as mean values.



If you select mean value generation, the currently pending analog value is acquired cyclically and accumulated. The acquisition cycle depends on the SamplingPeriod parameter (for example 500 ms, see also the description of this parameter). The mean value is calculated from the accumulated values as soon as a transmission is triggered over the TriggerInput input. Following this, the accumulation starts again so that the next mean value can be calculated. The mean value can also be calculated if the transmission of the analog value message is triggered by a general or single request. The duration of the mean value calculation period is then the time from the last transmission (for example triggered over TriggerInput) to the time of the general or single request. Once again, the accumulation restarts so that the next mean value can be calculated. If the acquired analog value is above or below the permitted range (7FFFH bzw. 8000H), this value can either be taken into account immediately in the calculation of the mean value or it can be suppressed for a specific period for the calculation of the mean value. The required response can be decided with the FaultSuppressionTime parameter: FaultSuppressionTime = 0 Acquisition of a value above or below the allowed range results in an immediate cancelation of the mean calculation. The value 7FFFH or 8000H is saved as an invalid mean value for the current mean value calculation period and sent when the next analog value message is triggered. The calculation of a new mean value is then started. If the analog value remains above or below the permitted range, this new value is again saved immediately as an invalid value and sent when the next message is triggered. FaultSuppressionTime > 0 If the acquired analog value is above or below the permitted range, the bad values are excluded from the calculation of the mean value for a maximum duration as defined by the FaultSuppressionTime. If this period is exceeded, the value 7FFFH or 8000H is saved as an invalid mean value and sent when the next analog value message is triggered. This procedure is repeated in the new mean value calculation period; in other words, bad values are suppressed once again for the duration of the FaultSuppressionTime. The FaultSuppressionTime period allows you to indirectly determine the percentage of invalid values for each mean value calculation period. For example, if the mean is calculated every 15 minutes and FaultSuppressionTime is set to 5 minutes, the mean value is only sent as invalid when more than 1/3 or 33% of the analog values acquired are above or below the permitted range in the current mean value calculation period. If no parameter is specified, the default is FALSE; in other words, instantaneous values are acquired and transmitted.

Name: AnalogInput_1 ... _4 Declaration: INPUT Data type WORD Default: 0 (W#16#0)



Explanation Analog input word. Range of

values: I/O words Memory words Data words

PIW0 ... PIWn MW0 ... MWn LW0 ... LWn DBm.DBW0 ... n

For each analog value to be transmitted in the data message, you can specify from where the FB will take the analog information. I/O words from analog input modules, data words from a data block and memory words can be mixed as required. If you do not require parameters, simply leave them open. The value 0 is transferred for these analog inputs in the message.

Name: SamplingPeriod Declaration: INPUT Data type INT Default: 500 Explanation Acquisition interval for analog inputs in ms. Range of

values: 0 ... 32767 [ms] No parameter specified: Default value 500 ms is valid.

The acquisition interval is required for the following parameters: • For the processing of the threshold value according to the integration

principle (threshold integration) • For smoothing the analog input value (SmoothingFactor) • For calculating the mean values (MeanValueGeneration) The value must be selected high enough so that it is certain that a new value was acquired over the analog input. The interval has to be at least as long as the encoding time of the analog input module being used at the selected resolution (8 ... 15 bits). If no parameter is specified, the default of 500 ms applies. This time is high enough to be applied even at the highest resolution and for analog modules with the maximum number of inputs. If mean values are calculated, SamplingPeriod should not be less than 500 ms. If mean values are calculated over very long periods, the time must be increased as follows: • Mean value calculation period 12 h: SamplingPeriod = 1000 [ms] • Mean value calculation period 24 h: SamplingPeriod = 2000 [ms] Specifying a SamplingPeriod that is too short may lead to an overflow of internal accumulation counter (must not exceed max. value 2,147,483,647 of a double integer). When an overflow is detected, the invalid mean value of 8000H is transmitted for the current mean value calculation period.



Name: ThresholdValue Declaration: INPUT Data type INT Default: 270 Explanation Threshold value. Range of

values: 0 or 1 ... 32767 No parameter specified: Default 270 is valid (corresponds to 1%).

The encoding range of the analog value must be taken into consideration when setting the threshold value. Raw values from S7 analog inputs are always encoded in the range from 0 ... 27648 (= 0 ... 100 %) or + 27648 (= + 100%). Depending on the resolution of the analog input, the value jumps by 128 (at 8-bit resolution) or 1 (at 15-bit resolution). If the acquired analog values have a different encoding range, the threshold value should be entered according to this. If no parameter is entered, the default value of 270 applies. This corresponds to approximately 1% of the normal S7 analog raw value range. Point to note with ThresholdValue = 0 Changes are not checked based on the threshold value. The analog value message will only be sent in the following situations: 1. When there is a trigger over the TriggerInput input, typically a time-driven

or event-driven message trigger. 2. When there is a general request to the station or a single request for the

message. 3. When the analog value moves into the overflow or underflow range

(7FFFH or 8000H) (possibly after the suppression time set by FaultSuppressionTime has elapsed).

Note When MeanValueGeneration = TRUE, i.e. the analog values are sent as mean values, the ThresholdValue parameter has no meaning.

Name: SmoothingFactor Declaration: INPUT Data type INT Default: 1 Explanation Smoothing factor.



Range of values:

1 (no smoothing) 4 (weak smoothing) 32 (medium smoothing) 64 (strong smoothing) No parameter specified: Default 1 (no smoothing ) is valid.

Using the smoothing factor, quickly fluctuating analog values can be smoothed to a greater or lesser extent (depending on the factor). This may allow a narrower threshold band to be set (see ThresholdValue). The smoothing factors are identical to the smoothing factors that are configured for some S7 analog input modules. The smoothing is handled in typical using the same formula as for input modules, described by the following:

1y x k yk

nn n

=+ − −( )1

yn = smoothed value in the current cycle n yn = acquired value in the current cycle n k = smoothing factor

Note When MeanValueGeneration = TRUE, i.e. the analog values are sent as mean values, the SmoothingFactor parameter has no meaning.

Name: FaultSuppressionTime Declaration: INPUT Data type INT Default: 0 Explanation Fault suppression time in seconds. Range of

values: 0 ... 32767 [s] No parameter specified: Default value 0 s is valid.



Transmission of an analog value located in the overflow or underflow range (7FFFH or 8000H) is suppressed for the time period specified here. The value 7FFFH or 8000H is only sent after this time has elapsed, if it is still pending. If the value returns to below 7FFFH or above 8000H again before this time elapses, it is immediately sent again as normal The suppression time is started again for the full duration the next time 7FFFH or 8000H is acquired. This is typically used for temporary suppression of current values that may occur when powerful pumps and motors are started. The analog input may exceed several times the maximum range under some circumstances. Suppression prevents these values from being signaled as faults in the control center system. The suppression is adjusted to analog values that are acquired by the S7 analog input modules as raw values. These modules return the specified values for the overflow or underflow range for all input ranges (also for life-zero inputs). When the user provides specific values, fault suppression is only possible if these also adopt the values 7FFFH or 8000H when the permitted ranges are exceeded. If this is not the case, the parameter does not need to have a value entered. The parameter can also be used in combination with the mean value calculation temporary suppression of the values 7FFFH or 8000H (see description of the MeanValueGeneration) parameter. When no parameter is specified, the default value of 0 seconds applies. An acquired value of 7FFFH or 8000H is then sent immediately when it is first detected or, with mean value calculation, as an invalid mean value for the current mean value calculation period.

3.5.6 ST7 analog value typical FB Ana04W_R

Function Receive 4 analog values (16-bit value in the INT format).



values: 1 ... 32000



The subscriber number of the partner with which the FB communicates, i.e. from which the FB receives data, must be specified. With an operator typical such as Ana04W_R, this is normally the subscriber number of a station PLC. The parameter setting PartnerNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 32000), an error message to this effect is entered in the diagnostic buffer (event ID B100). If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected. If the PLC receives a message for the object set here, the system checks whether the source subscriber number in the message is identical to the PartnerNo set here. If they are different, the received information is discarded. An error message to this effect is entered in the diagnostic buffer (event ID B130).

Name: PartnerObjectNo Declaration: INPUT Data type INT Default: 0 Explanation Object number of the partner. Range of values: 1 ... 32000 The number of the object (= DB number) on the partner with which the FB

communicates, i.e. from which the FB receives data, must be specified. The parameter setting PartnerObjectNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 32000), an error message to this effect is entered in the diagnostic buffer (event ID B102). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected. If the PLC receives a message for the object set here, the system checks whether the source object number in the message is identical to the PartnerObjectNo set here. If they are different, the received information is discarded. An error message to this effect is entered in the diagnostic buffer (event ID B131).





Range of values:



Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is not enabled, the FB can only communicate at the organizational level; in other words, ORG messages can be sent and received. A request can, for example, still be sent and the answer received, the received information is, however, not output to the outputs AnalogOutput_1 through AnalogOutput_4.

Name: AnalogOutput_1 … _4 Declaration: OUTPUT Data type WORD Default: TRUE Explanation 0 (W#16#0) Range of


PQW0 ... PQWn MW0 ... MWn LW0 ... LWn DBm.DBW0 ... n

You can select where the individual analog values received by the FB are output. I/O words from analog output modules, data words from a data block and memory words can be mixed as required. How to read out the time stamp received with the data is described in the section Notes on the SINAUT time stamp. If you do not require parameters, simply leave them open.






Whenever the FB has received new data and has output it to the outputs AnalogOutput_1 through AnalogOutput_4, the NewData output is set to TRUE for one OB1 cycle. The output is intended for user-specific further processing, for example to react in a specific way to receipt of new data. If you do not require the parameter, simply leave it open.

3.5.7 ST1 analog value typicals FB ATZ01 and FB ATZ03

Function [ATZ01] send 4 analog values (16-bit ST1 format) in a message in ST1 format. [ATZ03] send 8 analog values (16-bit ST1 format) in a message in ST1 format.

Note The processing parameters such as threshold, smoothing factor etc. exist only once in a typical. These parameters apply to all 4 or 8 analog values in common; in other words, it is not possible to set the parameters for the individual analog values. For this reason, each typical should only acquire analog values that can be processed in the same way.


values: : 0, 1 ... 8 or 1 ... 254



The subscriber number of the partner with which the FB communicates, i.e. to which the FB sends data, must be specified. With a process typical such as ATZ01 or ATZ03, this is normally the subscriber number of the ST1 master. If ATZ01 or ATZ03 is used in the reverse transmission direction (see ReverseDirection parameter), the subscriber number of an ST1 station must be specified. Partner is the ST1 master: Range of values limited to 1 ... 8 (= ST1 master number) Partner is the ST1 station: Range of values limited to 1 ... 254 (= ST1 station number) Partner is ST7/ST7cc: Range of values limited to 1 ... 254 (= SINAUT ST7 subscriber number) Point to note with PartnerNo = 0 If ATZ01 or ATZ03 is used in a station; in other words not in the reverse transmission direction (ReverseDirection = FALSE), the parameter setting PartnerNo = 0 is also permitted with ATZ01 or ATZ03. The data is then transferred to all subscribers to which a connection was configured; in other words, to all ST1 masters. If the parameter setting is incorrect (< 0 or > 8 or > 254), an error message to this effect is entered in the diagnostic buffer (event ID B100). If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.



values: 2 ... 250



The message number of the ST1 message to be sent must be specified. The parameter must be set by the user in all situations. If the parameter is missing (default value 0 applies) or if the value is < 2 or > 250, a message to this effect is entered in the diagnostic buffer (event ID B103). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.



values: 1 ... 255



values: 0 ... 255

A value higher than 0 is permitted only when a value higher than 0 was also set for ST1_ObjectNo; in other words, an ST1 message with address expansion is to be transmitted. This expanded addressing is not normally required; only in conjunction with the SINAUT LSX control center system. If the parameter setting is incorrect (< 0 or > 255), an error message to this effect is entered in the diagnostic buffer (event ID B105). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.



Name: ST1_PACK_Value Declaration: INPUT Data type INT Default: 0 Explanation PACK value for a message in ST1 format with address expansion.

An ST1 message transferred with the expanded addresses object and index number (ST1_ObjectNo, ST1_IndexNo) can contain data for several objects. Only the number of the first object is transferred with the message. The numbers of the other objects are assigned without gaps beginning at this start object. The packing scheme; in other words, how many analog values belong to a single analog value object, is transferred in the message with the PACK value. Based on this PACK value, the ST1 message is then converted into several KOMSYS-X messages for SINAUT LSX in the master: One KOMSYS-X message per object with the amount of data specified with PACK. If the additional addresses ST1_ObjectNo and ST1_IndexNo are used, a setting must be made indicating the number of analog values per object (pack interval).

[ATZ01] Range of values: 1, 2 or 4 [analog values] No parameter specified: Default value 0 is valid; corresponds to 4 analog values 1 = 1 analog value per object (the message contains 4 objects each 1 analog value) 2 = 2 analog values per object (the message contains 2 objects each 2 analog values) 4 = 4 analog values per object (the message contains 1 object with 4 analog values)

[ATZ03] Range of values: 1, 2, 4 or 8 [analog values] No parameter specified: Default value 0 is valid; corresponds to 8 analog values 1 = 1 analog value per object (the message contains 8 objects each 1 analog value) 2 = 2 analog values per object (the message contains 4 objects each 2 analog values) 4 = 4 analog values per object (the message contains 2 objects each 4 analog values) 8 = 8 analog values per object (the message contains 1 object with 8 analog values)




For more detailed information on the ST1 object number and ST1 index number and the packing scheme, refer to the SINAUT TD1/RX manual. If the parameter setting is incorrect (PACK values other than 0, 1, 2, 4 or 8), an error message to this effect is entered in the diagnostic buffer (event ID B106). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.



Range of values:



























Range of values:

TRUE or FALSE No parameter specified: Default value FALSE is valid.


Name: ThresholdIntegration Declaration: INPUT Data type BOOL Default: FALSE Explanation Threshold value processing according to the integration principle. Range of


With this parameter, you can specify whether the integration principle is used in threshold value processing. If no parameter is specified, the default is FALSE; in other words, threshold values are processed without integration. This corresponds to the previous ST1 procedure. In this case, you can also expect less traffic on the telecontrol line and locally between CPU and TIM (over the MPI bus or party line).

Name: ZeroLimitation Declaration: INPUT Data type BOOL Default: TRUE Explanation Zero limitation. Range of


This parameter allows you to specify whether negative values should be suppressed and replaced with the value 0. If no parameter is specified, the default is TRUE. This means that the lowest value is limited to 0.

Name: TriggerInput Declaration: INPUT Data type BOOL Default: FALSE Explanation Trigger input.



Range of values:



If required, this parameter can be used to specify an input over which the user can trigger the transmission of the analog value message at any time (signal edge from 0 to 1).

Example: Time-driven analog value transmission with time stamp for supplying an analog value archive in the control center. To avoid these messages being overwritten when they are saved on the station TIM, the default TRUE of the ImageMemory parameter should be changed to FALSE. If you do not require the parameter, simply leave it open. The message is then transmitted according to normal criteria.




Name: LifeZero Declaration: INPUT Data type BOOL Default: FALSE Explanation Analog values have the life-zero measuring range. Range of




With this parameter, you can specify whether the analog values connected to inputs AnalogInput_1 ... _4 or AnalogInput_1 ... _8 have a life-zero measuring range (4 .. 20 mA, 1 .. 5V). The conversion to the ST1 format is then not in the range from 0 ... 2048 but from 512 ... 2560. If no parameter is specified, the default FALSE applies, in other words, it is converted into the normal ST1 format of 0 ... 2048.

Name: [ATZ01] AnalogInput_1 ... _4 [ATZ03] AnalogInput_1 ... _8

Declaration: INPUT Data type WORD Default: 0 (W#16#0) Explanation Analog input word. Range of


PIW0 ... PIWn MW0 ... MWn LW0 ... LWn DBm.DBW0 ... n

For each analog value to be transmitted in the data message, you can specify from where the FB will take the analog information. I/O words from analog input modules, data words from a data block and memory words can be mixed as required. If you do not require parameters, simply leave them open. The value 0 is transferred for these analog inputs in the message.

Note The ST1 typical ATZ01 assumes that the analog values are available at the inputs AnalogInput_1 through AnalogInput _4 or through AnalogInput _8 that have the encoding range of the S7 analog modules; in other words, 0 ... 27648 = 0 ... 100 % or + 27648 = + 100%, overflow is indicated by 7FFFH and underflow or wire break by 8000H. Only then can the typical convert the acquired analog values to the ST1 format and assign the error IDs 'overflow" and "wire break'. Refer to the two following tables.



Table 3-5 Conversion of ST7 to ST1 raw value format for unipolar and life-zero analog values

Transmitted ST1 raw value Acquired ST7 raw value LifeZero = FALSE LifeZero = TRUE

Measuring range in %

Unipolar e.g.

0 ... 20 mA

Life-zero e.g.

4 ... 20 mA Decimal Hexa

decimal Decimal 1) Hexa

decimal Decimal 1) Hexa

decimal

Range

> 117,5925

%

> 23.515 mA

> 22.810 mA 32767 7FFF 4095 + overflow

bit

7FF9 4095 + overflow

bit

7FF9 Overflow

117,5925 % :

100,0036 %

23.515 mA

: 20.0007

mA

22.810 mA :

20.0005 mA

32511 :

27649

7EFF :

6C01

2408 :

2048

4B40 :

4000

2920 :

2560

5B40 :

5000

Overflow range

100 % :

0 %

20 mA :

0 mA

20 mA :

4 mA

27648 : 0

6C00 :

0000

2048 : 0

4000 :

0000

2560 :

512

5000 :

1000

Nominal range

-0,0036 % :

-17,5925 %

-0.0007 mA

: -3.5185

mA

3.9995 mA :

1.1852 mA

-1 :

-4864

FFFF :

ED00

0 :

-360

0000 :

F4C0

512 :

152

1000 :

04C0

Under flow

range

< -17,5925

%

< -3.5185 mA

< 1.1852 mA -32768 8000 0 + Wire

break bit

0002 0 + Wire

break bit

0002 Underflow/wire break

1) The decimal value relates to the bits 3 through 15. Bits 0 through 2 contain code bits (overflow and wire break). Table 3-6 Conversion of ST7 to ST1 raw value format for bipolar analog values

Acquired ST7 raw value Transmitted ST1 raw value Measuring range in %

Bipolar e.g.

± 20 mA Decimal Hexa decimal

Decimal 1) Hexa decimal

Range

> 117,5925 % > 23.515 mA 32767 7FFF 4095 + overflow bit

7FF9 Overflow

117,5925 % :

100,0036 %

23.515 mA :

20.0007 mA

32511 :

27649

7EFF :

6C01

2408 :

2048

4B40 :

4000

Over flow

range

100 % :

0 % :

-100 %

20 mA : 0 :

-20 mA

27648 : 0 :

-27648

6C00 :

0000 :

9400

2048 : 0 :

-2048

4000 :

0000 :

C000

Nominal range

-100,0036 % :

-117,5925 %

-20.0007 mA :

-23.516 mA

-27649 :

-32512

93FF :

8100

-2048 :

-2408

C000 :

B4C0

Under flow

range

< -117,5925 % < -23.516 mA -32768 8000 0 + Wire

break bit

0002 Underflow

1) The decimal value relates to the bits 3 through 15. Bits 0 through 2 contain code bits (overflow and wire break).



Name: SamplingPeriod Declaration: INPUT Data type INT Default: 500 Explanation Acquisition interval for analog inputs in ms. Range of

values: 0 ... 32767 [ms] No parameter specified: Default value 500 ms is valid.

The acquisition interval is required both for processing the threshold value according to the integration principle and for smoothing the analog input value. The value must be selected high enough so that it is certain that a new value was acquired over the analog input. The interval has to be at least as long as the encoding time of the analog input module being used at the selected resolution (8 ... 15 bits). If no parameter is specified, the default of 500 ms applies. This time is high enough to be applied even at the highest resolution and for analog modules with the maximum number of inputs.

Name: ThresholdValue Declaration: INPUT Data type INT Default: 270 Explanation Acquisition interval for analog inputs in ms. Range of

values: 0 or 1 ... 32767 No parameter specified: Default 270 is valid (corresponds to 1%).

The encoding range of the analog value must be taken into consideration when setting the threshold value. Raw values from S7 analog inputs are always encoded in the range from 0 ... 27648 (= 0 ... 100 %) or + 27648 (= + 100%). Depending on the resolution of the analog input, the value jumps by 128 (at 8-bit resolution) or 1 (at 15-bit resolution). If the acquired analog values have a different encoding range, the threshold value should be entered according to this. If no parameter is entered, the default value of 270 applies. This corresponds to approximately 1% of the normal S7 analog raw value range. Point to note with ThresholdValue = 0 Changes are not checked based on the threshold value. The analog value message will only be sent in the following situations: 1. When there is a trigger over the TriggerInput input, typically a time-driven

or event-driven message trigger. 2. When there is a general request to the station or a single request for the

message. 3. When the analog value moves into the overflow or underflow range

(7FFFH or 8000H) (possibly after the suppression time set by FaultSuppressionTime has elapsed).



Name: SmoothingFactor Declaration: INPUT Data type INT Default: 2 Explanation Smoothing factor. Range of

values: 1 (no smoothing) 4 (weak smoothing) 32 (medium smoothing) 64 (strong smoothing) No parameter specified: Default 1 (no smoothing ) is valid.

Using the smoothing factor, quickly fluctuating analog values can be smoothed to a greater or lesser extent (depending on the factor). This may allow a narrower threshold band to be set (see ThresholdValue). The smoothing factors are identical to the smoothing factors that are configured for some S7 analog input modules. The smoothing is handled in typical using the same formula as for input modules, described by the following:

1y x k yk

nn n

=+ − −( )1

yn = smoothed value in the current cycle n yn = acquired value in the current cycle n k = smoothing factor

Name: FaultSuppressionTime Declaration: INPUT Data type INT Default: 0 Explanation Fault suppression time in seconds. Range of

values: 0 ... 32767 [s] No parameter specified: Default value 0 s is valid.



Transmission of an analog value located in the overflow or underflow range (7FFFH or 8000H) is suppressed for the time period specified here. The value is transmitted in the appropriate ST1 format only after this time has elapsed, if if is still pending. If the value returns to below 7FFFH or above 8000H again before this time elapses, it is immediately sent again as normal The suppression time is restarted with its full duration the next time 7FFFH or 8000H is acquired again. This is typically used for temporary suppression of current values that may occur when powerful pumps and motors are started. The analog input may exceed several times the maximum range under some circumstances. Suppression prevents these values from being signaled as faults in the control center system. The suppression is adjusted to analog values that are acquired by the S7 analog input modules as raw values. These modules return the specified values for the overflow or underflow range for all input ranges (also for life-zero inputs). Other analog value encodings are permitted with the ST1 typicals ATZ01 or ATZ03 (see also note in the explanation of the parameters AnalogInput_1 ... _4 or _8). If no parameter is set, the default of 0 s applies. An acquired value of 7FFFH or 8000H is then transmitted immediately in ST1 format when it is first detected.

3.5.8 ST1 analog value typicals FB ATA01 and FB ATA02

Function [ATA01] receive 4 analog values (16-bit ST1 format) from a message in ST1 format. [ATA02] receive 8 analog values (16-bit ST1 format) from a message in ST1 format.



values: 1 ... 254 or 1 ... 8



The subscriber number of the partner with which the FB communicates, i.e. from which the FB receives data, must be specified. With an operator typical such as ATA01 or ATA02, this is normally the subscriber number of the ST1 station. If ATA01 or ATA02 is used in the reverse transmission direction (see ReverseDirection parameter), the subscriber number of the ST1 master station must be specified. Partner is the ST1 station: Range of values limited to 1 ... 254 (= ST1 station number) Partner is the ST1 master: Range of values limited to 1 ... 8 (= ST1 master number) Partner is ST7/ST7cc: Range of values limited to 1 ... 254 (= SINAUT ST7 subscriber number) The parameter setting PartnerNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 254 or > 8), an error message to this effect is entered in the diagnostic buffer (event ID B100). If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected. If the PLC receives a message for the object set here, the system checks whether the source subscriber number in the message is identical to the PartnerNo set here. If they are different, the received information is discarded. An error message to this effect is entered in the diagnostic buffer (event ID B130).


values: 2 ... 250

The parameter must be set by the user in all situations. If the parameter is missing (default value 0 applies) or if the value is < 2 or > 250, a message to this effect is entered in the diagnostic buffer (event ID B103). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.





values: 0 or 1 ... 255



values: 0 ... 255




Range of values:





Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is not enabled, the FB can only communicate at the organizational level; in other words, ORG messages can be sent and received. A request can, for example, still be sent and the answer received, the received information is, however, not output to the outputs AnalogOutput_1 through AnalogOutput_4.

Name: ReverseDirection Declaration: INPUT Data type BOOL Default: FALSE Explanation Transmission in the reverse direction.

Range of values:


Here, you specify whether the ST1 message is to be received in the reverse direction (also known as the reverse measurement/monitoring direction); in other words, is transmitted from the master station to the station. The FB requires this information to determine whether the message addresses set in the FB are to be interpreted as source or destination addresses since ST1 messages have only one source or one destination address depending on the transmission direction. If no parameter is specified, the default is FALSE; in other words, the data is transmitted in the 'normal' direction from station to master station. Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is not enabled, the FB can only communicate at the organizational level; in other words, ORG messages can be sent and received. A query can, for example, still be sent and the answer received, the received information is, however, not output to the output bytes OutputByte_1 through OutputByte_4.

Name: LifeZero Declaration: INPUT Data type BOOL Default: FALSE Explanation Analog values have the life-zero encoding. Range of


With this parameter, you can specify whether or not the analog values included in the received message are encoded as life-zero values (512 ... 2560 instead of normal 0 ... 2048). This information is important to ensure correct conversion from ST1 to ST7 format. Refer to the two following tables. If no parameter is specified, the default FALSE applies, in other words, it is converted from the normal ST1 format of 0 ... 2048.



Name: [ATA01] AnalogOutput_1 ... _4 [ATA02] AnalogOutput_1 ... _8

Declaration: OUTPUT Data type WORD Default: 0 (W#16#0) Explanation Analog input word. Range of


PQW0 ... PQWn MW0 ... MWn LW0 ... LWn DBm.DBW0 ... n

You can select where the individual analog values received by the FB are output. I/O words from analog output modules, data words from a data block and memory words can be mixed as required. How to read out the time stamp received with the data is described in the section Notes on the SINAUT time stamp. If you do not require parameters, simply leave them open. The analog values received in ST1 raw value format are converted to ST7 raw value format. Refer to the two following tables.

Table 3-7 Conversion of ST1 to ST7 raw value format, unipolar and bipolar values

Received ST1 raw value Converted ST7 raw value Measuring range in % Decimal 1) Hexadecimal Decimal 1) Hexadecimal

Range

> 117,5781 % > 2408 or overflow bit

> 4B40 or 7FF9

32767 7FFF Overflow

117,5781 % :

100,0036 %

2408 :

2049

4B40 :

4008

32508 :

27661

7EFC :

6C0D

Over flow

range

100 % :

0 % :

-100 %

2048 : 0 :

-2048

4000 :

0000 :

C000

27648 : 0 :

-27648

6C00 :

0000 :

9400

Nominal range

-100,0036 % :

-117,5781 %

-2049 :

-2408

BFF8 :

64C0

-27661 :

-32508

93F3 :

8104

Under flow

range

< -117,5781 % < -2408 or wire break

< 64C0 or 0002

-32768 8000 Underflow




Table 3-8 Conversion of ST1 to ST7 raw value format, life-zero values

Received ST1 raw value Converted ST7 raw value Measuring range in % Decimal 1) Hexadecimal Decimal 1) Hexadecimal

Range

> 117,5781 % > 2920 or overflow bit

> 5B40 or 7FF9

32767 7FFF Overflow

117,5781 % :

100,0036 %

2920 :

2560

5B40 :

5000

32508 :

27661

7EFC :

6C0D

Over flow

range

100 % :

0 %

2560 :

512

5000 :

1000

27648 : 0

6C00 :

0000

Nominal range

-0,0036 % :

-17,5925 %

512 :

152

1000 :

04C0

-27661 :

-32508

93F3 :

8104

Under flow

range

< -17,5925 % < 152 or wire break

< 04C0 or 0002

-32768 8000 Underflow





Whenever the FB has received new data and has output it to the outputs AnalogOutput_1 through AnalogOutput_4, the NewData output is set to TRUE for one OB1 cycle. The output is intended for user-specific further processing, for example to react in a specific way to receipt of new data. If you do not require the parameter, simply leave it open.

3.5.9 ST7 counted value typicals FB Cnt01D_S and FB Cnt04D_S

Function [Cnt01D_S] send 1 counted value (32-bit ST1 format). [Cnt04D_S] send 4 counted values (32-bit ST1 format).





values: : 0 or 1 ... 32000

The subscriber number of the partner with which the FB communicates, i.e. to which the FB sends data, must be specified. For process typicals such as Cnt01D_S and Cnt04D_S, this is usually the subscriber no. of the master PLC or the ST7cc control center. Point to note with PartnerNo = 0 The data is transmitted to all subscribers for which a connection has been configured. The following PartnerObjectNo parameter is then irrelevant.

If the set PartnerNo was not found in the administration (in DB-BasicData), an entry to this effect is made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.



values: : 0 or 1 ... 32000

The number of the object (= DB number) on the partner with which the FB communicates, i.e. to which the FB sends data, must be specified. Point to note with PartnerObjectNo = 0 This parameter assignment is useful, if PartnerNo = 0 was set. If the PartnerObjectNo is missing, there must be a list on the partner PLC from which the missing object number can be recognized (see FC ListGenerator). If the subscriber specified by PartnerNo is an ST7cc control center, the PartnerObjectNo does not need to be specified in the FB because there are no DBs as destination objects in ST7cc as there are in a CPU. ST7cc decodes its messages solely based on the source address in the message.





Range of values:



























Name: GeneralTriggerCommand Declaration: INPUT Data type BOOL Default: FALSE Explanation General restore command: Range of


Here, you specify whether or not a counted value transmission should be triggered by a general restore command (the general restore command belongs to the organizational SINAUT system commands). If an explicit destination subscriber number (PartnerNo > 0) is assigned in the typical, the general restore command is evaluated in the corresponding subscriber object in the central administration. If the destination subscriber number is missing (PartnerNo = 0, send ’to all’), the central system memory bit ’General restore command’ is taken into account. When the general restore command is detected, the currently accumulated counted value is transmitted regardless of other criteria that affect message transmission. The restore identifier US is inverted in this counted value. Parameters GeneralTriggerCommand and TriggerInput can be used together. Transmission is then triggered by a signal edge change from 0 to 1 at the TriggerInput as well as when a general restore command is received. If no parameter is specified, the default is FALSE; in other words, there is no restore using the general restore command.

Name: TriggerInput Declaration: INPUT Data type BOOL Default: FALSE Explanation Enable block processing.




Range of values:



If required, this parameter can be used to specify an input over which the user can trigger (signal edge change from 0 to 1) a transmission at any time regardless of other criteria that affect message transmission. The currently accumulated counted value is transmitted. The restore identifier US is inverted in this counted value.

Note FC Trigger is an easy way to trigger time-driven transmission of a counted value message. For more detailed information, refer to the description of the FC.

Parameters TriggerInput and GeneralTriggerCommand can be used

together. Transmission is then triggered by a signal edge change from 0 to 1 at the TriggerInput as well as when an organizational restore command is received. If no parameter is specified, the default is FALSE; in other words, there is no restore and transmission triggered over the TriggerInput input.

Name: [Cnt01D_S] Counter_1 [Cnt04D_S] Counter_1 ... _4

Declaration: INPUT Data type COUNTER Default: - Explanation Number of the SIMATIC counter. Range of

values: C0 as dummy parameter or C1 ... Cn (n depending on CPU type)

Here, you specify the SIMATIC counter in which the pulses were counted time-driven. This takes place in the background using FC PulseCounter that is called in a cyclic interrupt OB, for example OB35. Refer to the description of FC PulseCounter and 'Time-driven SINAUT program in a cyclic interrupt OB'. The COUNTER data type cannot be assigned a default value. If you have used the C0 dummy parameter in the typical, the corresponding counted value is not processed.



Name: DifferenceValue Declaration: INPUT Data type INT Default: 0 Explanation Difference value. Range of

values: 0 or 1 ... 31768 No parameter specified: Default value 0 is valid.

When a value between 1 and 31768 is specified, the counted value is sent as soon as the difference between the current and most recently transmitted counted value reaches or exceeds the configured value.

If no parameter is specified, default value 0 applies; in other words, a counted value is only sent when a signal edge change from 0 to 1 is detected at the TriggerInput input , or when (if GeneralTriggerCommand = TRUE) an organizational restore command is received.

Note The difference value must be selected by the user depending on the maximum pulse rate per second. The value should not be too low otherwise there is a constant transfer of the message to the TIM. On one hand, this would cause heavy load on the MPI bus/party line but also stretch the send queue on the CPU.

Note

[Cnt04D_S] The DifferenceValue processing parameter exists only once in the typical. This parameter applies to all 4 counted values in common; in other words, it is not possible to set the parameter for the individual counted values. When using this parameter, each typical should therefore only acquire counted values that can be processed identically.

3.5.10 ST7 counted value typicals FB Cnt01D_R and FB Cnt04D_R

Function [Cnt01D_R] receive 1 counted value (32-bit ST1 format). [Cnt04D_R] receive 4 counted values (32-bit ST1 format).





Explanation Subscriber no. of the partner. Range of

values: 1 ... 32000

The subscriber number of the partner with which the FB communicates, i.e. from which the FB receives data, must be specified. With operator typicals such as Cnt01D_R and Cnt04D_R, this is normally the subscriber number of a station PLC. The parameter setting PartnerNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 32000), an error message to this effect is entered in the diagnostic buffer (event ID B100). If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected. If the PLC receives a message for the object set here, the system checks whether the source subscriber number in the message is identical to the PartnerNo set here. If they are different, the received information is discarded. An error message to this effect is entered in the diagnostic buffer (event ID B130).


values: : 0 or 1 ... 32000

The number of the object (= DB number) on the partner with which the FB communicates, i.e. from which the FB receives data, must be specified. The parameter setting PartnerObjectNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 32000), an error message to this effect is entered in the diagnostic buffer (event ID B102). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected. If the PLC receives a message for the object set here, the system checks whether the source object number in the message is identical to the PartnerObjectNo set here. If they are different, the received information is discarded. An error message to this effect is entered in the diagnostic buffer (event ID B131).

Name: Enabled Declaration: INPUT Data type BOOL



Default: TRUE Explanation Enable block processing.


Range of values:



Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is not enabled, the FB can only communicate at the organizational level; in other words, ORG messages can be sent and received. A request can, for example, still be sent and the answer received, the received information is, however, not output to the output / outputs CountedValueOutput_...

Name: BCD_Format Declaration: INPUT Data type BOOL Default: TRUE Explanation Counted value output in BCD format. Range of


Here, you specify the format in which counted value received at the output / outputs CountedValueOutput_... is output. If the parameter is left open or if you specify TRUE, the counted value is output with a maximum of seven places in BCD (= S7 format; the sign decade is always 0; in other words, +). The maximum counted value that can be represented is therefore restricted to 9,999,999. If you do not require BCD format (BCD_Format = FALSE), the counted value is output as a 32-bit integer and this is also always positive. The maximum counted value that can be represented is then 2,147,483.647. If the maximum counted value that can be represented is exceeded, the counted value starts again at 0 and counting continues in the positive numeric range.

Note [Cnt04D_R] The BCD_Format processing parameter exists only once in the typical. This parameter applies to all 4 counted values in common; in other words, it is not possible to set the parameter for the individual counted values. When using this parameter, each typical should therefore only output counted values that can have parameters set for an identical output format.



Name: CntValInvalid Declaration: OUTPUT Data type BOOL Default: FALSE Explanation Counted value invalid. Range of



At the CntValInvalid output, the FB indicates whether the last received counted value was invalid (with Cnt04D_R, this counts as a group display for all four counted values). In principle, the output shows the current status of the validity bit A from the most recently received counted value in inverted form.

On the one hand, the output serves as an error indicator. On the other, the output is intended for user-specific further processing. For example, the user may wish to react to invalidity by correcting the counted value at CountedValueOutput_... by adding counter pulses that may have been lost. If you do not require the parameter, simply leave it open.

Note [Cnt04D_R] Although all 4 counted values in the message have their own validity bit, only the validity bit A of the first counted value in the last received message is evaluated for the status at the CntValInvalid output. This status, however, applies to all 4 counted values, since all the counted values in the message always have the same validity status.

Note

When evaluating CntValInvalid, you should take into account the fact that it might only be possible for this bit to be set for one OB1 cycle.

Name: RestoreStatus Declaration: OUTPUT Data type BOOL Default: FALSE Explanation Current status of the restore bit US in the received counted value.

Output Bit memory Data bit


Range of values:

No parameter specified: Default value FALSE is valid.



At the RestoreStatus output, the FB indicates the current status of the restore bit US from the last received counted value message.

The output is intended for user-specific further processing. For example, the user may only wish to access the information at CountedValueOutput_... when a change has been detected at the RestoreStatus output; in other words, when the counted value has been received due to a restore, such as a local time-driven restore. If you do not require the parameter, simply leave it open.

Note [Cnt04D_R] Although all 4 counted values in the message have their own restore bit, only the restore bit US of the first counted value in the last received message is evaluated for the status at the RestoreStatus output. This status, however, applies to all 4 counted values since they are always restored together.

Name: NewData Declaration: OUTPUT Data type BOOL Default: FALSE Explanation Receive new data.



Range of values:

No parameter specified: Default value FALSE is valid. Whenever the FB has received new data and has output it to the output /

outputs CountedValueOutput_..., the NewData output is set to TRUE for one OB1 cycle. The output is intended for user-specific further processing, for example to react in a specific way to receipt of new data. If you do not require the parameter, simply leave it open.

Name: [Cnt01D_R] CountedValueOutput_1 [Cnt04D_R] CountedValueOutput_1 ... _4

Declaration: IN_OUT Data type DWORD Default: 0 Explanation Counted value output.



Range of values:

(process image) output double words Memory double words Data double words

QD0 ... Qnd MD0 ... MDn DBm.DBD0 ... n

The counted value output is a double word in which the counted value is stored in BCD format or as a 32-bit integer (depending on the BCD_Format parameter). In BCD format, the maximum counted value that can be represented is limited to 9,999,999, if the counted value is output as a 32-bit integer, the maximum counted value that can be represented is 2,147,483,647. The counted value is always output as a positive number; in other words, if the maximum counted value that can be represented is exceeded, the counted value starts again at 0 and counting continues in the positive numeric range. Since the parameter is an in-out parameter (declaration IN_OUT), the value can be reset to 0 or another value at the counted value output by the user at any time. The counted value typical always adds the newly formed difference value (difference between the new and last received counted value) to the value currently output that the counted value output.

Note Since the parameter is an in-out parameter (declaration IN_OUT), direct I/O output of the counted value to PQD0 ... PQDn is not permitted! It is also difficult to specify local bit memory with this parameter type and this should not be used.

How to read out the time stamp received with the data is described in the

section Notes on the SINAUT time stamp.

3.5.11 ST1 counted value typicals FB ZTZ01, FB ZTZ02 and FB ZTZ03

Function [ZTZ01] send 1 counted value (32-bit ST1 format) in a message in ST1 format. [ZTZ02] send 2 counted values (32-bit ST1 format) in a message in ST1 format. [ZTZ03] send 4 counted values (32-bit ST1 format) in a message in ST1 format.





values: 0, 1 ... 8 or 1 ... 254

The subscriber number of the partner with which the FB communicates, i.e. to which the FB sends data, must be specified. With process typicals such as ZTZ01, ZTZ02 and ZTZ03, this is normally the subscriber number of the ST1 master. If these typicals are used in the reverse transmission direction (see ReverseDirection parameter), the subscriber number of an ST1 station must be specified. Partner is the ST1 master: Range of values limited to 1 ... 8 (= ST1 master number) Partner is the ST1 station: Range of values limited to 1 ... 254 (= ST1 station number) Partner is ST7/ST7cc: Range of values limited to 1 ... 254 (= SINAUT ST7 subscriber number) Point to note with PartnerNo = 0 If ZTZ01, ZTZ02 or ZTZ03 is used in a station; in other words not in the reverse transmission direction (ReverseDirection = FALSE), the parameter setting PartnerNo = 0 is also permitted with these typicals. The data is then transferred to all subscribers to which a connection was configured; in other words, to all ST1 masters.

If the parameter setting is incorrect (< 0 or > 8 or > 254), an error message to this effect is entered in the diagnostic buffer (event ID B100). If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.





values: 2 ... 250




values: 0 or 1 ... 255


Name: ST1_IndexNo Declaration: INPUT Data type INT Default: 0 Explanation Index number for a message in ST1 format.



Range of values:

0 ... 255


Name: ST1_PACK_Value [ZTZ02, ZTZ03] Declaration: INPUT Data type INT Default: 0 Explanation PACK value for a message in ST1 format with address expansion.

An ST1 message transferred with the expanded addresses object and index number (ST1_ObjectNo, ST1_IndexNo) can contain data for several objects. Only the number of the first object is transferred with the message. The numbers of the other objects are assigned without gaps beginning at this start object. The packing scheme; in other words, how many counted values belong to a single counted value object, is transferred in the message with the PACK value. Based on this PACK value, the ST1 message is then converted into several KOMSYS-X messages for SINAUT LSX in the master: One KOMSYS-X message per object with the amount of data specified with PACK. If the additional addresses ST1_ObjectNo and ST1_IndexNo are used, a setting must be made indicating the number of counted values per object (pack interval).

[ZTZ02] Range of values:

1 or 2 [counted values] No parameter specified: Default 0 is valid; corresponds to 2 counted values

1 = 1 counted value per object (the message contains 2 objects each with 1 counted value) 2 = 2 counted values per object (the message contains 1 object with 2 counted values)

[ZTZ03] Range of values:

1, 2 or 4 [counted values] No parameter specified: Default 0 is valid; corresponds to 4 counted values

1 = 1 counted value per object (the message contains 4 objects each with 1 counted value) 2 = 2 counted values per object (the message contains 2 objects each with 2 counted values) 4 = 4 counted values per object (the message contains 1 object with 4 counted values)



For more detailed information on the ST1 object number and ST1 index number and the packing scheme, refer to the SINAUT TD1/RX manual. If the parameter setting is incorrect (PACK values other than 0, 1, 2, or 4), an error message to this effect is entered in the diagnostic buffer (event ID B106). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.




Range of values:



























Range of values:



Name: GeneralTriggerCommand Declaration: INPUT Data type BOOL Default: FALSE Explanation General restore command: Range of


Here, you specify whether or not a counted value transmission should be triggered by a general restore command (the general restore command belongs to the organizational SINAUT system commands). If an explicit destination subscriber number (PartnerNo > 0) is assigned in the typical, the general restore command is evaluated in the corresponding subscriber object in the central administration. If the destination subscriber number is missing (PartnerNo = 0, send ’to all’), the central system memory bit ’General restore command’ is taken into account. When the general restore command is detected, the currently accumulated counted value is transmitted regardless of other criteria that affect message transmission. The restore identifier US is inverted in this counted value. Parameters GeneralTriggerCommand and TriggerInput can be used together. Transmission is then triggered by a signal edge change from 0 to 1 at the TriggerInput as well as when a general restore command is received. If no parameter is specified, the default is FALSE; in other words, there is no restore using the general restore command.

Name: TriggerInput Declaration: INPUT Data type BOOL Default: FALSE Explanation Trigger input (restore input) Range of

values: TRUE or FALSE No parameter specified: Default value FALSE is valid





If required, this parameter can be used to specify an input over which the user can trigger (signal edge change from 0 to 1) a transmission at any time regardless of other criteria that affect message transmission. The currently accumulated counted value is transmitted. The restore identifier US is inverted in this counted value.

Note FC Trigger is an easy way to trigger time-driven transmission of a counted value message. For more detailed information, refer to the description of the FC.

Parameters TriggerInput and GeneralTriggerCommand can be used

together. Transmission is then triggered by a signal edge change from 0 to 1 at the TriggerInput as well as when an organizational restore command is received. If no parameter is specified, the default is FALSE; in other words, there is no restore and transmission triggered over the TriggerInput input.






Name: [ZTZ01] Counter_1 [ZTZ02] Counter_1 ... _2 [ZTZ03] Counter_1 ... _4

Declaration: INPUT Data type COUNTER Default: - Explanation Number of the SIMATIC counter. Range of

values: C0 as dummy parameter or C1 ... Cn (n depending on CPU type)

Here, you specify the SIMATIC counter in which the pulses were counted time-driven. This takes place in the background using FC PulseCounter that is called in a cyclic interrupt OB, for example OB35. Refer to the description of FC PulseCounter and 'Time-driven SINAUT program in a cyclic interrupt OB'. The COUNTER data type cannot be assigned a default value. If you have used the C0 dummy parameter in the typical, the corresponding counted value is not processed.

Name: DifferenceValue Declaration: INPUT Data type INT Default: 0 Explanation Difference value. Range of

values: 0 or 1 ... 31768

When a value between 1 and 31768 is specified, the counted value is sent as soon as the difference between the current and most recently transmitted counted value reaches or exceeds the configured value.

If no parameter is specified, default value 0 applies; in other words, a counted value is only sent when a signal edge change from 0 to 1 is detected at the TriggerInput input , or when (if GeneralTriggerCommand = TRUE) an organizational restore command is received.

Note The difference value must be selected by the user depending on the maximum pulse rate per second. The value should not be too low otherwise there is a constant transfer of the message to the TIM. On one hand, this would cause heavy load on the MPI bus/party line but also stretch the send queue on the CPU.



Note [ZTZ02, ZTZ03] The DifferenceValue processing parameter exists only once in the typical. This parameter applies to all 2 or 4 counted values in common; in other words, it is not possible to set the parameter for the individual counted values. When using this parameter, each typical should therefore only acquire counted values that can be processed identically.

3.5.12 ST1 counted value typicals FB ZTA01, FB ZTA02 and FB ZTA03

Function [ZTA01] receive 1 counted value (32-bit ST1 format) from a message in ST1 format. [ZTA02] receive 2 counted values (32-bit ST1 format) from a message in ST1 format. [ZTA03] receive 4 counted values (32-bit ST1 format) from a message in ST1 format.



values: 1 ... 254 or 1 ... 8



The subscriber number of the partner with which the FB communicates, i.e. from which the FB receives data, must be specified. With operator typicals such as ZTA01, ZTA02 and ZTA03, this is normally the subscriber number of the ST1 station. If these typicals are used in the reverse transmission direction (see ReverseDirection parameter), the subscriber number of the ST1 master station must be specified. Partner is the ST1 station: Range of values limited to 1 ... 254 (= ST1 station number) Partner is the ST1 master: Range of values limited to 1 ... 8 (= ST1 master number) Partner is ST7/ST7cc: Range of values limited to 1 ... 254 (= SINAUT ST7 subscriber number) The parameter setting PartnerNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 254 or > 8), an error message to this effect is entered in the diagnostic buffer (event ID B100). If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected. If the PLC receives a message for the object set here, the system checks whether the source subscriber number in the message is identical to the PartnerNo set here. If they are different, the received information is discarded. An error message to this effect is entered in the diagnostic buffer (event ID B130).


values: 2 ... 250






values: 1 ... 255



values: 0 ... 255


Name: Enabled Declaration: INPUT Data type BOOL Default: TRUE Explanation Enable block processing. Range of

values: TRUE or FALSE No parameter specified: Default TRUE is valid





Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is not enabled, the FB can only communicate at the organizational level; in other words, ORG messages can be sent and received. A request can, for example, still be sent and the answer received, the received information is, however, not output to the output / outputs CountedValueOutput_...

Name: BCD_Format Declaration: INPUT Data type BOOL Default: TRUE Explanation Counted value output in BCD format. Range of


Here, you specify the format in which counted value received at the output / outputs CountedValueOutput_... is output. If the parameter is left open or if you specify TRUE, the counted value is output with a maximum of seven places in BCD (= S7 format; the sign decade is always 0; in other words, +). The maximum counted value that can be represented is therefore restricted to 9,999,999. If you do not require BCD format (BCD_Format = FALSE), the counted value is output as a 32-bit integer and this is also always positive. The maximum counted value that can be represented is then 2,147,483.647. If the maximum counted value that can be represented is exceeded, the counted value starts again at 0 and counting continues in the positive numeric range.

Note The BCD_Format processing parameter exists only once in the typical. This parameter applies to all 2 or 4 counted values in common; in other words, it is not possible to set the parameter for the individual counted values. When using this parameter, each typical should therefore only output counted values that can have parameters set for an identical output format.

Name: ReverseDirection Declaration: INPUT Data type BOOL Default: FALSE



Explanation Transmission in the reverse direction. Range of



Name: CntValInvalid Declaration: OUTPUT Data type BOOL Default: FALSE Explanation Counted value invalid.



Range of values:

No parameter specified: Default value FALSE is valid. At the CntValInvalid output, the FB indicates whether the last received

counted value was invalid (with ZTA02 and ZTA03, this counts as a group display for all received counted values). In principle, the output shows the current status of the validity bit A from the most recently received counted value in inverted form.

On the one hand, the output serves as an error indicator. On the other, the output is intended for user-specific further processing. For example, the user may wish to react to invalidity by correcting the counted value at CountedValueOutput_... by adding counter pulses that may have been lost. If you do not require the parameter, simply leave it open.

Note [ZTA02, ZTA03] Although all 2 or 4 counted values in the message have their own validity bit, only the validity bit A of the first counted value in the last received message is evaluated for the status at the CntValInvalid output. This status, however, applies to all counted values, since all the counted values in the message always have the same validity status.



Note When evaluating CntValInvalid, you should take into account the fact that it might only be possible for this bit to be set for one OB1 cycle.

Name: RestoreStatus Declaration: OUTPUT Data type BOOL Default: FALSE Explanation Current status of the restore bit US in the received counted value.



Range of values:

No parameter specified: Default value FALSE is valid. At the RestoreStatus output, the FB indicates the current status of the

restore bit US from the last received counted value. The output is intended for user-specific further processing. For example, the user may only wish to access the information at CountedValueOutput_... when a change has been detected at the RestoreStatus output; in other words, when the counted value has been received due to a restore, such as a local time-driven restore. If you do not require the parameter, simply leave it open.

Note [ZTA02, ZTA03] Although all 2 or 4 counted values in the message have their own restore bit, only the restore bit US of the first counted value in the last received message is evaluated for the status at the RestoreStatus output. This status, however, applies to all counted values since they are always restored together.




Range of values:

No parameter specified: Default value FALSE is valid.



Whenever the FB has received new data and has output it to the output / outputs CountedValueOutput_..., the NewData output is set to TRUE for one OB1 cycle.

The output is intended for user-specific further processing, for example to react in a specific way to receipt of new data. If you do not require the parameter, simply leave it open.

Name: [ZTA01] CountedValueOutput_1 [ZTA02] CountedValueOutput_1 ... _2 [ZTA03] CountedValueOutput_1 ... _4

Declaration: IN_OUT Data type DWORD Default: 0 Explanation Counted value output. Range of

values: (process image) output double words Memory double words Data double words

QD0 ... Qnd MD0 ... MDn DBm.DBD0 ... n

The counted value output is a double word in which the counted value is stored in BCD format or as a 32-bit integer (depending on the BCD_Format parameter). In BCD format, the maximum counted value that can be represented is limited to 9,999,999, if the counted value is output as a 32-bit integer, the maximum counted value that can be represented is 2,147,483,647. The counted value is always output as a positive number; in other words, if the maximum counted value that can be represented is exceeded, the counted value starts again at 0 and counting continues in the positive numeric range. Since the parameter is an in-out parameter (declaration IN_OUT), the value can be reset to 0 or another value at the counted value output by the user at any time. The counted value typical always adds the newly formed difference value (difference between the new and last received counted value) to the value currently output that the counted value output.

How to read out the time stamp received with the data is described in the section Notes on the SINAUT time stamp.

Note Since the parameter is an in-out parameter (declaration IN_OUT), direct I/O output of the counted value to PQD0 ... PQDn is not permitted! It is also difficult to specify local bit memory with this parameter type and this should not be used.



3.5.13 ST7 command typical FB Cmd01B_S

Function Send 1 byte commands (1-out-of-8 ST1 format).

Note With FB Cmd01B_S, data can only be transmitted when FC Safe is included at the end of the cyclic SINAUT program. See also the section 'The cyclic OB1 program for a control center'.



values: 1 ... 32000

The subscriber number of the partner with which the FB communicates, i.e. to which the FB sends data, must be specified. With an operator typical such as Cmd01B_S, this is normally the subscriber number of a station PLC. The parameter setting PartnerNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 32000), an error message to this effect is entered in the diagnostic buffer (event ID B100). If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.


values: : 0 or 1 ... 32000



The number of the object (= DB number) on the partner with which the FB communicates, i.e. to which the FB sends data, must be specified. The parameter setting PartnerObjectNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 32000), an error message to this effect is entered in the diagnostic buffer (event ID B102). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.



Range of values:



Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is disabled the FB only checks to see if the disabled status has been canceled. The FB cannot communicate on the organizational level in this status because FB Cmd01B_S cannot send or receive organizational messages.

Name: CommandInputByte_HW Declaration: INPUT Data type BYTE Default: 0 (B#16#0) Explanation Command input byte for hardware input. Range of

values: Input byte Memory bytes Data bytes

IB0 ... Ibn PIB0 ... PIBn MB0 ... MBn LB0 ... LBn DBm.DBB0 ... n



This command input byte is specially designed for entering commands using hardware, i.e. over digital inputs. Input using memory or data bytes is also possible, but the user must then make sure that the command at the input byte is reset, which occurs at the hardware level when the command button is released. When input is detected, the command is transmitted if no error is detected during the 1-out-of-8 and 1-out-of-n check, and if the central enable memory bit is set. This is automatically set by FC Safe following a selected time delay set there (see FC Safe, InputDelayTime parameter). If a 1-out-of-8 or 1-out-of-n error is detected, the entered command is no longer processed. A new command is first read in when no hardware command has been acquired in the PLC for one OB1 cycle; in other words, not only for this block but also for all other command input blocks with hardware input. The FB enters the detected 1- out-of-8- or 1-out-of-n error in the diagnostic buffer (event ID B171 or B172). The error status is also indicated over the InputError output of FC Safe (see FC Safe, InputError parameter) and continues to be indicated as long as the error remains.

Name: CommandInputByte_SW Declaration: IN_OUT Data type BYTE Default: 0 (B#16#0) Explanation Command input byte for software input. Range of

values: Memory bytes Data bytes

MB0 ... MBn DBm.DBB0 ... n

This command input byte is specially designed for entering commands using software, i.e. by the user program or at an operator panel (OP). When input is detected, the command is reset at the input byte and transmitted if no error is detected during the 1-out-of-8 and 1-out-of-n check. The central enable memory bit is ignored here because it is only intended for command input over hardware (see CommandInputByte_HW). If a 1-out-of-8 or 1-out-of-n error is detected, the entered command is no longer processed. A new command is first read in when no software command has been acquired on the PLC for one OB1 cycle; in other words, not only for this block but also for all other command input blocks with software input. The FB enters the detected 1- out-of-8- or 1-out-of-n error in the diagnostic buffer (event ID B171 or B172). Appropriate error bits are also set in the central data block "BasicData" where they can be queried by the software. For more detailed information, refer to the description of FC Safe. In principle it is possible to enter a new command to CommandInputByte_SW in every OB1 cycle. However, only one command per OB1 cycle is allowed and this applies to all command input blocks with software input (1-out-of-n check). An ’empty cycle’ between two consecutive software commands is therefore not necessary.



Note The command inputs CommandInputByte_HW and CommandInputByte_SW can also be used at the same time; in other words, if you want to enter the same command over the hardware and software. If a command entry occurs at the same time over both input bytes, this is only accepted when coincidentally exactly the same command is entered over the hardware as well as the software input (the hardware entry is then processed). In all other cases the entry is rejected and an error message is entered in the diagnostics buffer (event ID B170). The error status is also indicated by the InputError output of FC Safe and appropriate error bits are set in the central data block "BasicData" where they can be queried by the software (see FC Safe).

Note

This is an in/out parameter (declaration IN_OUT). It is difficult to specify local bit memory with this parameter type and this should not be used.

3.5.14 ST7 command typical FB Cmd01B_R

Function Receive 1 byte commands (1-out-of-8 ST1 format).



values: 1 ... 32000 or 0 (if there is more than one partner)

The subscriber number of the partner with which the FB communicates, i.e. from which the FB receives data, must be specified. For a process typical such as Cmd01B_R, this is usually the subscriber no. of the master PLC or the ST7cc control center. Point to note on PartnerNo = 0 Enter 0 for the parameter when the typical can receive data from more than one partner, for example, when there are several control centers wanting to send data to the typical configured here. This is only possible when each partner sends the message with a complete destination address.



If the PLC receives a message for the object set here, and PartnerNo is greater than 0, the system checks whether the source subscriber number in the message is identical to the PartnerNo set here. If they are different, the received information is discarded. An error message to this effect is entered in the diagnostic buffer (event ID B130). This check is not made if PartnerNo = 0. Regardless of the sender, each message addressed to the object is also passed on to the object. If the set PartnerNo is greater than 0 and this number was not found in the administration (in DB-BasicData), an entry is made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.

Note PartnerNo = 0 is permitted only when it is certain that all partners that send data to the object selected here transfer their messages with a complete destination address; in other words, with destination subscriber number and destination object number.


values: 1 ... 32000 or 0 (for example if the partner is an ST7cc control center or if there is more than one partner)



The number of the object (= DB number) on the partner with which the FB communicates, i.e. from which the FB receives data, must be specified. The parameter setting PartnerObjectNo = 0 is necessary in the following situations: 1. The partner is not an S7-CPU; in other words, there is no object = DB

number. This is, for example, the case when the partner is an ST7cc control center.

2. There is more than one partner (PartnerNo = 0) that wants to send data to this typical. The corresponding objects of these partners will then generally have different numbers; in other words, no unique number can be specified here.

If the PLC receives a message for the object set here, and PartnerObjectNo is greater than 0, the system checks whether the source object number in the message is identical to the PartnerObjectNo set here. If they are different, the received information is discarded. An error message to this effect is entered in the diagnostic buffer (event ID B131). This check is not made if PartnerObjectNo = 0. Regardless of the sender object, each message addressed to the object is also passed on to the object.



Range of values:



Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is disabled the FB only checks to see if the disabled status has been canceled. Any commands that are still received are not output. The FB cannot communicate on the organizational level in this status because FB Cmd01B_R cannot send or receive organizational messages.

Note If the Enabled input can be controlled by a switch, this local disable means that no more commands are output if they are still received. Since the block is, however, not capable of sending ORG messages, it cannot report this local disable back to the partner itself. This must be implemented by the user with a separate message, for example Bin04B_S.



Name: MultipleOutput Declaration: INPUT Data type BOOL Default: FALSE Explanation Simultaneous output of multiple commands permitted. Range of


With this parameter, you can specify whether or not several (consecutively received) commands can be output simultaneously; in other words, you specify how the block reacts when a new command is received and the previously received command is still being output (command output time has not yet elapsed or the user program has not yet reset this command). FALSE (default): Multiple command output is not permitted. The newly received command overwrites the output byte. Any command is still pending is therefore reset to 0 unless the new command is identical to the old one. TRUE: Multiple command output is permitted. A newly received command is ORed into the current output byte. The command output time is retriggered. This applies to all pending commands.

Name: CommandOutputTime Declaration: INPUT Data type INT Default: 500 Explanation 500 Range of

values: Command up time for command outputs in ms. No parameter specified: Default value 500 [ms] is valid.

The specified time applies to all command outputs. If more than one output can be set at the same time (MultipleOutput = TRUE), the output time is restarted with each newly received command. This means that pending commands are retriggered. All the command outputs are reset of the same time when the output time elapses. Point to note with CommandOutputTime = 0 A set command output is not reset by the command typical. The user program is responsible for this. If no parameter is specified, an output time of 500 ms is used as the default.






Whenever the FB has received new data and has output it to the output byte CommandOuputByte, the NewData output is set to TRUE for one OB1 cycle. The output is intended for user-specific further processing, for example to react in a specific way to receipt of new data. If you do not require the parameter, simply leave it open.

Name: CommandOutputByte Declaration: IN_OUT Data type BYTE Default: 0 (B#16#0) Explanation Command output byte. Range of

values: (process image) output bytesMemory bytes Data bytes

QB0 ... Qbn MB0 ... MBn DBm.DBB0 ... n

To allow the command outputs to be reset both by the command typical itself as well as by the user program (went output time = 0), the parameter was declared as an IN_OUT parameter.

Note Since the parameter is an IN_OUT parameter, direct I/O output of the command byte to PQB0 ... PQBn is not permitted! It is also difficult to specify local bit memory with this parameter type and this should not be used.



3.5.15 ST1 command typical FB BTZ01

Function Send 1 byte commands (1-out-of-8 ST1 format) in a message in ST1 format.

Note With FB BTZ01, data can only be transmitted when FC Safe is included at the end of the cyclic SINAUT program.


Name: PartnerNo Declaration: INPUT Data type: INT Default: 0 Explanation Subscriber no. of the partner. Range of

values: 1 ... 254

The subscriber number of the partner with which the FB communicates, i.e. to which the FB sends data, must be specified. With an operator typical such as BTZ01, this is normally the subscriber number of an ST1 station. The parameter setting PartnerNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 254), an error message to this effect is entered in the diagnostic buffer (event ID B100). If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.

Name: ST1_MessageNo Declaration: INPUT Data type: INT Default: 0 Explanation Message number for a message in ST1 format. Range of

values: 2 ... 250





Name: ST1_ObjectNo Declaration: INPUT Data type: INT Default: 0 Explanation Object number for a message in ST1 format. Range of

values: 0 or 1 ... 255


Name: ST1_IndexNo Declaration: INPUT Data type: INT Default: 0 Explanation Index number for a message in ST1 format. Range of

values: 0 ... 255




Name: Enabled Declaration: INPUT Data type: BOOL Default: TRUE Explanation Enables block processing.

TRUE or FALSE No parameter specified: Default value TRUE is valid

Range of values:



Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is disabled the FB only checks to see if the disabled status has been canceled. The FB cannot communicate on the organizational level in this status because FB BTZ01 cannot send or receive organizational messages.

Name: CommandInputByte_HW Declaration: INPUT Data type: BYTE Default: 0 (B#16#0) Explanation Command input byte for hardware input. Range of

values: Input Bit memory Data bit

IB0 ... Ibn PIB0 ... PIBn MB0 ... MBn LB0 ... LBn DBm.DBB0 ... n)

This command input byte is specially designed for entering commands using hardware, i.e. over digital inputs. Input using memory or data bytes is also possible, but the user must then make sure that the command at the input byte is reset, which occurs at the hardware level when the command button is released. When input is detected, the command is transmitted if no error is detected during the 1-out-of-8 and 1-out-of-n check, and if the central enable memory bit is set. This is automatically set by FC Safe following a selected time delay set there (see FC Safe, InputDelayTime parameter). If a 1-out-of-8 or 1-out-of-n error is detected, the entered command is no longer processed. A new command is first read in when no hardware command has been acquired in the PLC for one OB1 cycle; in other words, not only for this block but also for all other command input blocks with hardware input. The FB enters the detected 1- out-of-8- or 1-out-of-n error in the diagnostic buffer (event ID B171 or B172). The error status is also indicated over the InputError output of FC Safe (see FC Safe, InputError parameter) and continues to be indicated as long as the error remains.



Name: CommandInputByte_SW Declaration: IN_OUT Data type: BYTE Default: 0 (B#16#0) Explanation Command input byte for software input. Range of

values: Memory bytes Data bytes

MB0 ... MBn DBm.DBB0 ... n

This command input byte is specially designed for entering commands using software, i.e. by the user program or at an operator panel (OP). When input is detected, the command is reset at the input byte and transmitted if no error is detected during the 1-out-of-8 and 1-out-of-n check. The central enable memory bit is ignored here because it is only intended for command input over hardware (see CommandInputByte_HW). If a 1-out-of-8 or 1-out-of-n error is detected, the entered command is no longer processed. A new command is first read in when no software command has been acquired on the PLC for one OB1 cycle; in other words, not only for this block but also for all other command input blocks with software input. The FB enters the detected 1- out-of-8- or 1-out-of-n error in the diagnostic buffer (event ID B171 or B172). Appropriate error bits are also set in the central data block "BasicData" where they can be queried by the software. For more detailed information, refer to the description of FC Safe. In principle it is possible to enter a new command to CommandInputByte_SW in every OB1 cycle. However, only one command per OB1 cycle is allowed and this applies to all command input blocks with software input (1-out-of-n check). An ’empty cycle’ between two consecutive software commands is therefore not necessary.

Note The command inputs CommandInputByte_HW and CommandInputByte_SW can also be used at the same time; in other words, if you want to enter the same command over the hardware and software. If a command entry occurs at the same time over both input bytes, this is only accepted when coincidentally exactly the same command is entered over the hardware as well as the software input (the hardware entry is then processed). In all other situations, the input is rejected and an error message entered in the diagnostic buffer ( event ID B170). The error status is also indicated over the InputError output of FC Safe and appropriate error bits are set in the central data block "BasicData" that can be queried by the software (see FC Safe).

Note




3.5.16 ST1 command typical FB BTA01

Function Receive 1 byte commands (1-out-of-8 ST1 format) from a message in ST1 format.



values: 0 or 1 ... 8

The subscriber number of the partner with which the FB communicates, i.e. from which the FB receives data, must be specified. With a process typical such as BTA01, this is normally the subscriber number of the ST1 master. The parameter is optional. It is not required for addressing or for any checks. It is therefore possible to enter 0 or leave the parameter open (default value 0 then applies).


values: 2 ... 250


Note Note ST1_MessageNo = 1 is not permitted! This message number is reserved in ST1 for the error message.




values: 0 or 1 ... 255



values: 0 ... 255




Range of values:





Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is disabled the FB only checks to see if the disabled status has been canceled. Any commands that are still received are not output. The FB cannot communicate on the organizational level in this status because FB BTA01 cannot send or receive organizational messages.

Note If the Enabled input can be controlled by a switch, this local disable means that no more commands are output if they are still received. Since the block is, however, not capable of sending ORG messages, it cannot report this local disable back to the partner itself. This must be implemented by the user with a separate message, for example MTZ01.

Name: MultipleOutput Declaration: INPUT Data type BOOL Default: FALSE Explanation Simultaneous output of multiple commands permitted. Range of


With this parameter, you can specify whether or not several (consecutively received) commands can be output simultaneously; in other words, you specify how the block reacts when a new command is received and the previously received command is still being output (command output time has not yet elapsed or the user program has not yet reset this command). FALSE (default): Multiple command output is not permitted. The newly received command overwrites the output byte. Any command is still pending is therefore reset to 0 unless the new command is identical to the old one. TRUE: Multiple command output is permitted. A newly received command is ORed into the current output byte. The command output time is retriggered. This applies to all pending commands.

Name: CommandOutputTime Declaration: INPUT Data type INT Default: 500 Explanation Command up time for command outputs in ms. Range of

values: 0 or 1 ... 32767 [ms] No parameter specified: Default value 500 [ms] is valid.



The specified time applies to all command outputs. If more than one output can be set at the same time (MultipleOutput = TRUE), the output time is restarted with each newly received command. This means that pending commands are retriggered. All the command outputs are reset of the same time when the output time elapses. Point to note with CommandOutputTime = 0 A set command output is not reset by the command typical. The user program is responsible for this. If no parameter is specified, an output time of 500 ms is used as the default.


values: Output Bit memory Data bit No parameter specified: Default value FALSE is valid.


Whenever the FB has received new data and has output it to the output byte CommandOuputByte, the NewData output is set to TRUE for one OB1 cycle. The output is intended for user-specific further processing, for example to react in a specific way to receipt of new data. If you do not require the parameter, simply leave it open.

Name: CommandOutputByte Declaration: IN_OUT Data type BYTE Default: 0 (B#16#0) Explanation Command output byte. Range of

values: (process image) output bytes Memory bytes Data bytes

QB0 ... Qbn MB0 ... MBn DBm.DBB0 ... n

To allow the command outputs to be reset both by the command typical itself as well as by the user program (went output time = 0), the parameter was declared as an IN_OUT parameter.

Note Since the parameter is an IN_OUT parameter, direct I/O output of the command byte to PQB0 ... PQBn is not permitted! It is also difficult to specify local bit memory with this parameter type and this should not be used.



3.5.17 ST7 setpoint typical FB Set01W_S

Function Send 1 setpoint (16 bits) and receive current local setpoint.

Note With FB Set01W_S, data can only be transmitted when FC Safe is included at the end of the cyclic SINAUT program.



values: 1 ... 32000

The subscriber number of the partner with which the FB communicates, i.e. to which the FB sends data and from which it also receives data, must be specified. With an operator typical such as Set01W_S, this is normally the subscriber number of a station PLC. The parameter setting PartnerNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 32000), an error message to this effect is entered in the diagnostic buffer (event ID B100). If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.

Name: PartnerObjectNo Declaration: INPUT Data type INT Default: 0 Explanation Object number of the partner. Range of

values: 1 ... 32000



The number of the object (= DB number) on the partner with which the FB communicates, i.e. to which the FB sends data and from which it receives data, must be specified. The parameter setting PartnerObjectNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 32000), an error message to this effect is entered in the diagnostic buffer (event ID B102). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.



Range of values:



Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is not enabled, the FB can only communicate at the organizational level; in other words, ORG messages can be sent and received. A request can, for example, still be sent and the answer received, the received information is, however, not output to the output ReturnedSetpoint.

Name: EnterInput Declaration: INPUT Data type BOOL Default: FALSE Explanation Enter input (for 'hardware' setpoint). Range of

values: Input Bit memory Data bit No parameter specified: Default value FALSE is valid




A setpoint at the SetpointInput can be applied over this input triggered by a signal edge change. A signal change at EnterInput is only taken into account when the parameter ContinuousEnterFunct = FALSE. If this condition is fulfilled, the setpoint entered at SetpointInput is applied and transmitted by a signal change from 0 to 1 even if the newly entered setpoint is identical to the previously sent setpoint. This method of applying setpoints is suitable for input at appropriate hardware, for example a console or control panel but can also be used for entering setpoints at an operator panel (OP). In the latter case, it must be possible to trigger the input by a separate function key on the OP. If you do not require the parameter, simply leave it open.

Name: ContinuousEnterFunct Declaration: INPUT Data type BOOL Default: FALSE Explanation Apply setpoint continuously (for ’software’ setpoint). Range of


With this parameter, you can decide whether the setpoint at SetpointInput should be continuously read in and changes checked. The change evaluation is made by comparing the current with the last setpoint that was sent. This method of applying a setpoint is suitable for input by appropriate software but can also be used for entering setpoints at an operator panel (OP) if it does not have a separate function key that can be used to trigger the input. If you do not require the parameter, simply leave it open.

Name: SetpointInput Declaration: INPUT Data type WORD Default: 0 (W#16#0) Explanation Setpoint input word. Range of

values: Input words Memory words Data words

IW0 ... Iwn PIW0 ... PIWn MW0 ... MWn LW0 ... LWn DBm.DBW0 ... n



How a setpoint available at SetpointInput is processed depends on whether it is a hardware or software input. The user specifies the type of input with the ContinuousEnterFunct parameter: • ContinuousEnterFunct = FALSE (= hardware input)

The setpoint at SetpointInput is only read in as long as a 1 signal is detected at EnterInput. The setpoint that is read in is then transmitted if no error is detected during the 1-out-of-n check, and if the central enable memory bit is set. This is automatically set by FC Safe following a selected time delay set there (see FC Safe, InputDelayTime parameter). The next setpoint is first read in by the FB when a 0 signal is detected for at least one OB1 cycle at EnterInput. If a 1-out-of-n error is detected the next time a value is applied to the hardware input, the entered setpoint is no longer processed. A new setpoint is first read in when no hardware input has been acquired in the PLC for one OB1 cycle; in other words, not only for this block but also for all other command and setpoint input blocks with hardware input. The FB enters the detected 1-out-of-n error in the diagnostic buffer (event ID B172). The error status is also indicated over the InputError output of FC Safe (see FC Safe, InputError parameter) and continues to be indicated as long as the error remains.

• ContinuousEnterFunct = TRUE (= software input) The setpoint at SetpointInput is read in continuously and checked for changes. The change evaluation is made by comparing the current with the last setpoint that was sent. The setpoint is sent immediately every time a change occurs unless the 1-out-of-n check detects an error. Without the setpoint having changed, a new transmission of the software setpoint can be triggered over the SendSoftSetpoint input (see below). While for hardware input an empty cycle must be detected before a new setpoint can be sent by the block, for software input a new setpoint can be transmitted in every OB1 cycle. This is possible only when there is no other software setpoint or software command in this cycle. Otherwise a 1-out-of- n error is detected. If a 1-out-of-n error is detected during the software input, the entered setpoint is no longer processed. A new setpoint is first read in when no software input has been acquired in the PLC for one OB1 cycle; in other words, not only for this block but also for all other command and setpoint blocks with software input. The FB enters the detected 1-out-of-n error in the diagnostic buffer (event ID B172). Appropriate error bits are also set in the central data block "BasicData" where they can be queried by the software. For more detailed information, refer to the description of FC Safe.

Name: ReturnedSetpoint Declaration: OUTPUT Data type WORD Default: 0 (W#16#0) Explanation Output word for a returned setpoint.



Range of values:

Output words Memory words Data words

QW0 ... QWn PQW0 ... PQWn MW0 ... MWn LW0 ... LWn DBm.DBW0 ... n

The partner object receiving the setpoint reports back the currently valid local setpoint. This value is displayed at the ReturnedSetpoint output. If the partner object is set to ’local’ and if an input is made there, then the setpoint changed locally is displayed here at ReturnedSetpoint. After startup of the local or partner PLC, or after restoring a connection, an automatic general request ensures that the current, local, valid setpoint is displayed at ReturnedSetpoint. How to read out the time stamp received with the data is described in the section Notes on the SINAUT time stamp. If you do not require the parameter, simply leave it open.

Name: LocalOperation Declaration: OUTPUT Data type BOOL Default: FALSE Explanation Return message from the partner object: Object is set to local operation. Range of



A setpoint can also be set locally at the partner object that receives the setpoint. The partner object then must be set to ’local’ at the Local input parameter (see FB Set01W_R below). The current status of the Local input parameter is reported by the partner object and displayed here at the LocalOperation output. After startup of the local or partner PLC, or after restoring a connection, an automatic general request ensures that the current, local, valid status is displayed at LocalOperation. How to read out the time stamp received with the data is described in the section Notes on the SINAUT time stamp. If you do not require the parameter, simply leave it open.




Range of values:

Output Bit memory Data bit No parameter specified: Default value FALSE is valid.


Whenever the FB has received new data and has output it to the outputs ReturnedSetpoint or LocalOperation, the NewData output is set to TRUE for one OB1 cycle. The output is intended for user-specific further processing, for example to react in a specific way to receipt of new data. If you do not require the parameter, simply leave it open.

Name: SendSoftSetpoint Declaration: IN_OUT Data type BOOL Default: FALSE Explanation Trigger input for resending the last (software) setpoint. Range of

values: Bit memory Data bit No parameter specified: Default value FALSE is valid.

M 0.0 ... M n.7 DBm.DBX 0.0 ... n.7

See also SetpointInput parameter. If you do not require the parameter, simply leave it open.

Note This is an in/out parameter (declaration IN_OUT). It is difficult to specify local bit memory with this parameter type and this should not be used.

3.5.18 ST7 setpoint typical FB Set01W_R

Function Receive or enter 1 setpoint locally (16 bits) and send the current, locally valid setpoint.






The subscriber number of the partner with which the FB communicates, i.e. from which the FB receives data and to which it also sends data, must be specified. For a process typical such as Set01W_R, this is usually the subscriber no. of the master PLC or the ST7cc control center. Point to note with PartnerNo = 0 Enter 0 for the parameter when the typical can exchange data with more than one partner, for example, when there are several control centers wanting to send data to this typical and have the local, valid setpoint returned. If the PLC receives a message for the object set here, and PartnerNo is greater than 0, the system checks whether the source subscriber number in the message is identical to the PartnerNo set here. If they are different, the received information is discarded. An error message to this effect is entered in the diagnostic buffer (event ID B130). This check is not made if PartnerNo = 0. Regardless of the sender, each message addressed to the object is also passed on to the object. If the set PartnerNo is greater than 0 and this number was not found in the administration (in DB-BasicData), an entry is made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.


Note

When using the block in the PLC of a node station, you should consider the consequences of PartnerNo = 0! If the PLC of the node station maintains both connections to higher-level subscribers as well as to lower-level stations, a message with PartnerNo = 0 is transferred to all subscribers both "up" and "down".





The number of the object (= DB number) on the partner with which the FB communicates, i.e.from which the FB receives data and to which which it sends data, must be specified. The parameter setting PartnerObjectNo = 0 is necessary in the following situations: 1. The partner is not an S7-CPU; in other words, there is no object = DB


2. There is more than one partner (PartnerNo = 0) that wants to exchange data data with this typical. The corresponding objects of these partners will then generally have different numbers; in other words, no unique number can be specified here.




Range of values:





Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is not enabled, the FB can only communicate at the organizational level; in other words, ORG messages can be sent and received. A query is, for example, answered, however the reply message contains the data valid at the time the function was disabled. Any setpoints that are still received are not output.

Name: ImageMemory Declaration: INPUT Data type BOOL Default: TRUE Explanation Transmission in the reverse direction. Range of









Range of values:










Name: TimeStamp Declaration: INPUT Data type BOOL Default: FALSE



Explanation Time stamp. Range of


Here, you specify whether the message with the returned setpoint and the ’Local’ status should be sent with a time stamp. The prerequisite is that the time provided by the local TIM is available on the PLC. For more detailed information, refer to the description of FC TimeTask. If no parameter is specified, the default is FALSE; in other words, data is transmitted without a time stamp.

Name: Local Declaration: INPUT Data type BOOL Default: FALSE Explanation Enable block processing.


Range of values:



This input is used to enable local input of a setpoint over LocalSetpointInput. A setpoint sent for example by the control center is not accepted by the object as long as Local = TRUE. The current status of the Local input is transmitted to the partner together with a copy of the setpoint which is currently being output at SetpointOutput (setpoint mirroring). Bumpless switchover: • When there is a switchover from Local = 0 to Local = 1, the last values at

ParameterOutput are held until new parameter values are entered over LocalParameterInput.

• When there is a switchback from Local = 1 to Local = 0, the last values at ParameterOutput are held until the block receives new parameter values from the remote partner.

Note Please read the note on the ContinuousEnterFunct parameter.



Name: EnterInput Declaration: INPUT Data type BOOL Default: FALSE Explanation Enter input for local setpoint input. Range of

values: TRUE or FALSE

Input Bit memory Data bit No parameter specified: Default value FALSE is valid


A setpoint at the LocalSetpointInput can be applied over this input triggered by a signal edge change. A signal change at EnterInput is only taken into account when the value TRUE is set at the Local input parameter and ContinuousEnterFunct = FALSE. If these conditions are fulfilled, a signal change from 0 to 1 causes the setpoint at LocalSetpointInput to be applied and output at SetpointOutput. This method of applying setpoints is suitable for input at appropriate hardware, for example a console or control panel but can also be used for entering setpoints at an operator panel (OP). In the latter case, it must be possible to trigger the input by a separate function key on the OP. If you do not require the parameter, simply leave it open.

Name: ContinuousEnterFunct Declaration: INPUT Data type BOOL Default: FALSE Explanation Continuous local setpoint acquisition: Range of


With this parameter, you can decide whether the setpoint at LocalSetpointInput should be continuously read in and changes checked. The change evaluation is made by comparing the current with the last mirrored setpoint. The value is only read when the Local input parameter is set to TRUE. If an array is detected, this is output immediately at SetpointOutput. This method of acquiring a setpoint is suitable for input by appropriate software but can also be used for entering setpoints at an operator panel (OP) if it does not have a separate function key that can be used to trigger the input. If you do not require the parameter, simply leave it open.



Note When ContinuousEnterFunct = TRUE, the value available at LocalSetpointInput is entered immediately and passed to SetpointOutput when the 1 signal at the Local input is detected if the local input value differs from the last returned setpoint at this point in time!

Name: LocalSetpointInput Declaration: INPUT Data type WORD Default: 0 (W#16#0) Explanation Local setpoint input word. Range of

values: Input words Memory words Data words No parameter specified: Default value 0 is valid.


A value at LocalSetpointInput is only adopted if the Local input parameter is set to TRUE. If this condition is met, how a pending setpoint is processed depends on whether it is a hardware or software input. The user specifies the type of input with the ContinuousEnterFunct parameter: • ContinuousEnterFunct = FALSE (= hardware input)

The setpoint at LocalSetpointInput is only read in when a signal change from 0 to 1 is detected at EnterInput. The setpoint entered locally is output over the output set with SetpointOutput and transferred to the partner for display. A further setpoint is then only read in by the FB when a 0 signal was detected at EnterInput for at least one OB1 cycle.

• ContinuousEnterFunct = TRUE (= software input) The setpoint at LocalSetpointInput is read in continuously and checked for changes. The change evaluation is implemented by comparing the current value with the last valid setpoint; in other words, the value stored as the returned setpoint. Every time there is a change, the setpoint is passed immediately to the output specified by SetpointOutput and sent to the partner for display. While for hardware input an empty cycle must be detected before a new setpoint can be read by the block, for software input a new setpoint can be entered in every OB1 cycle.

If you do not require the parameter, simply leave it open.



Name: SetpointOutput Declaration: OUTPUT Data type WORD Default: 0 (W#16#0) Explanation Setpoint output word. Range of

values: Output words Memory words Data words

QW0 ... Qwn PQW0 ... PQWn MW0 ... MWn LW0 ... LWn DBm.DBW0 ... n

The setpoint sent by the partner object or the setpoint entered locally at LocalSetpointInput is output to the output word specified here in SetpointOutput.


values: Output words Bit memory Data bit No parameter specified: Default value FALSE is valid.


Whenever the FB has received a new setpoint from the partner object and has output it to SetpointOutput, the NewData output is set to TRUE for one OB1 cycle. This also applies when there is new local input when Local = 1. The output is intended for user-specific further processing, for example to react in a specific way to receipt of new data. If you do not require the parameter, simply leave it open.



3.5.19 ST7 parameter typical FB Par12D_S

Function Send 1 to 12 parameter values (each 1 double word) and receive back the current, locally valid parameter values.

Note With FB Par12D_S, data can only be transmitted when FC Safe is included at the end of the cyclic SINAUT program.

The content of each double word may be a value in double word format (e.g. DINT, REAL etc.); it can also be a mixture of other formats which together form a double word, for example, ● 4 bytes, or ● 2 words, or ● 2 bytes plus 1 word. The data area to be sent is defined for the ParameterInput parameter in the form of an Any pointer. This data area must be within a data block and its length can vary between 1 and 12 data double words. The data area sent to the partner or the parameter values entered locally at the partner are returned from there and output here at ReturnedParameter. This output area (defined by an Any pointer) must also be within a data block and its length must match that defined for ParameterInput. Separate data areas are normally specified for ParameterInput and ReturnedParameter. This makes it easy to recognize the most recently entered values and the current, locally valid values. However, it is also possible to specify the same data area for both parameters. The two areas then overlap 100% and therefore always match. In this case, you can no longer distinguish the difference between what has been entered most recently and what is locally valid. When returned values are not needed, there is no need to specify a data area for ReturnedParameter. Even when separate areas are specified for ParameterInput and ReturnedParameter, it is still possible to ensure that the ParameterInput area and the ReturnedParameter value always match. This be done manually from case to case with the ApplyRemoteParamMan input or automatically by setting the ApplyRemoteParamAuto parameter to TRUE. A parameter can also be set locally at the partner object that receives the parameter. The partner object then must be set to ’local’ at the Local input parameter (see FB Par12D_R below). The current status of the Local input parameter is reported by the partner object and displayed here at the LocalOperation output. As long as the partner object is set to 'local', no parameters are accepted there from other locations. Transmission of the data area defined by ParameterInput can be triggered in four ways: ● With the input parameter EnterInput

You should use this input parameter when the data area defined at ParameterInput is entered over hardware (digital and analog input modules). EnterInput must then be connected to a button on a console or panel over a digital input. The transmission of the entered values is then triggered by pressing this button. The entire data area specified by ParameterInput is always transmitted.



● With the input parameter ContinuousEnterFunct = TRUE You can use this parameter setting when the parameter is entered by software, for example at an operator panel (OP). There is a constant check for changes. When a change is detected in the data area defined with ParameterInput, the data double words that have changed since the last transmission are transmitted (see note).

● With the input parameter Release You can use this input parameter when the parameter is entered by software, for example on an OP. The Release input should then be operated by a function key on the OP. Changes are checked when a 1 signal is detected at the Release input. The data double words from the data area defined with ParameterInput that have changed since the last transmission (see note) are transmitted.

● With the input parameter RetransmitAll You can use this input parameter when the parameter is entered by software, for example on an OP. The RetransmitAll input should then be operated by a function key on the OP. When a 1 signal is detected at the RetransmitAll input, the entire data area defined by ParameterInput is transmitted. Changes are not checked.

Note When the changed data area only is transmitted, this area consists of the first and the last double word in which a change was detected and all words located in between, even if these have not changed. Example: The area to be read is 10 double words long. In this case, changes were detected in the 2nd, 5th and 8th double words. The transmitted area is therefore from the 2nd to the 8th double word inclusive.

Note When only changed data is transmitted and the data area contains values in double word format, the user is responsible for ensuring that these double word values are actually located in one of the maximum 12 double words of the data area to be acquired. Distribution over two consecutive data double words could otherwise lead to the transmission of only one word of the double word value (high or low word) because a change has occurred in only that particular word. The missing word could lead to processing problems on the partner that receives this value.



values: 1 ... 32000



The subscriber number of the partner with which the FB communicates, i.e. to which the FB sends data and from which it also receives data, must be specified. With an operator typical such as Par12D_S, this is normally the subscriber number of a station PLC. The parameter setting PartnerNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 32000), an error message to this effect is entered in the diagnostic buffer (event ID B100). If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.


values: 1 ... 32000

The number of the object (= DB number) on the partner with which the FB communicates, i.e. to which the FB sends data and from which it receives data, must be specified. The parameter setting PartnerObjectNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 32000), an error message to this effect is entered in the diagnostic buffer (event ID B102). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.



Range of values:





Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is not enabled, the FB can only communicate at the organizational level; in other words, ORG messages can be sent and received. A request can, for example, still be sent and the answer received, the received information is, however, not output to the output ReturnedParameter. There is also neither a comparison made between the ParameterInput and ReturnedParameter data areas when the ApplyRemoteParamMan input is triggered nor automatically when the ApplyRemoteParamAuto parameter is set to TRUE.

Name: EnterInput Declaration: INPUT Data type BOOL Default: FALSE Explanation Enter input.


Range of values:



The transmission of the parameter value at ParameterInput can be triggered over this input by a signal edge change. A signal change at EnterInput is only taken into account when the parameter ContinuousEnterFunct = FALSE. If this condition is fulfilled, a transition from 0 to 1 causes the parameter values specified at ParameterInput to be entered and transmitted. Changes are not checked. The entire data area specified by ParameterInput is always transmitted. This method of transmission triggering is suitable for input with appropriate hardware, for example at a console or control panel. For more detailed information and related parameters, refer to the section Function. If you do not require the parameter, simply leave it open. Data checks: • The parameters that are read in are then transmitted if no error is

detected during the 1-out-of-n check, and if the central enable memory bit is set. This is automatically set by FC Safe following a selected time delay set there (see FC Safe, InputDelayTime parameter). The input area is then only read in by the FB when a 0 signal was detected at EnterInput for at least one OB1 cycle.

• When a 1-out-of-n error is detected at the "hardware" input, the entered parameters are no longer processed. New parameters are read in again only when no "hardware" input has been acquired in the PLC for one OB1 cycle; in other words, not only for this block but also for all other command, setpoint and parameter blocks with "hardware" input. The FB enters the detected 1-out-of-n error in the diagnostic buffer (event ID B172). The error status is also indicated over the InputError output of FC Safe (see FC Safe, InputError parameter) and continues to be indicated as long as the error remains.



Name: ContinuousEnterFunct Declaration: INPUT Data type BOOL Default: FALSE Explanation Continuous change checking. Range of


With this parameter, you can decide whether the parameter values at ParameterInput should be continuously read in and changes checked. The change evaluation is made by comparing the current with the last values that were sent. Only changed values are sent. If more than one change is detected, the block sends the data area in which all changed parameter values are located. A new transmission of the parameter values can be triggered over the RetransmitAll input (see below) even when the parameter entries have not changed. This method of transmission triggering is suitable when the parameter values are entered in the ParameterInput area by software, but can also be used for entering the parameters from an operator panel (OP) when the OP has no separate function key with which to trigger transmission. For more detailed information and related parameters, refer to the section Function. If you do not require the parameter, simply leave it open. The default value FALSE then applies; in other words, the parameter values at ParameterInput are not read continuously and evaluated for changes. Data checks: • The parameters read in are only transmitted if no error is detected during

the 1-out-of-n check. While for "hardware" input (see EnterInput) an empty cycle must be detected before new parameter values can be sent from the block, for "software" input new parameter values can be transmitted in every OB1 cycle. This assumes that there is no other "software" entry at another block in this cycle. Otherwise a 1-out-of-n error is detected.

• When a 1-out-of-n error is detected at the "software" input, the entered parameters are no longer processed. New parameters are read in again only when no "software" input has been acquired in the PLC for one OB1 cycle; in other words, not only for this block but also for all other command, setpoint and parameter blocks with "software" input. The FB enters the detected 1-out-of-n error in the diagnostic buffer (event ID B172).



Note The changed data area that is transmitted consists of the first and the last double word in which a change was detected and all words located in between, even if these have not changed. Example: The area to be read is 10 double words long. In this case, changes were detected in the 2nd, 5th and 8th double words. The transmitted area is therefore from the 2nd to the 8th double word inclusive.

Name: ApplyRemoteParamAuto Declaration: IN Data type BOOL Default: FALSE Explanation Automatic synchronization of the input area with the returned area. Range of


If ApplyRemoteParamAuto = TRUE, the input area ParameterInput is automatically synchronized with the ReturnedParameter area. All the parameter values from the ReturnedParameter area are then copied to the ParameterInput area. The send buffer is also synchronized with the returned parameter values. Automatic synchronization is then always performed when new data is received from the partner object (Par12D_R). If you do not require the parameter, simply leave it open. The default value FALSE then applies; in other words no automatic synchronization is performed.

Name: ParameterInput Declaration: INPUT Data type ANY Default: P#P 0.0 VOID 0 (null pointer) Explanation Parameter input area.



Range of values:

P#DBxx.DBX yy.0 DWORD zz xx : Data block number 1...32767 yy : Byte number zz : Number of double words 1...12 starting at byte number yy Example: P#DB20.DBX 100.0 DWORD 4 Remember the periods and spaces when entering the pointer! No parameter specified: Default (null pointer) is valid. This is, however, not permitted! A pointer >< null pointer must be specified.

The ANY pointer defines the data area in which the parameter values to be acquired are located. This data area must be within a data block and its length can vary between 1 and 12 data double words. The content of each double word may be a value in double word format (e.g. DINT, REAL etc.); it can also be a mixture of other formats which together form a double word, for example, • 4 bytes, or • 2 words, or • 2 bytes plus 1 word. If the parameter setting is incorrect (null pointer, length greater than 12, data area not a data block), an error message to this effect is entered in the diagnostics buffer (event ID B114, [Info2/3] = 11). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected. How the parameters at ParameterInput are processed depends on whether they are "hardware" or "software" entries and how the transmission of this data area is triggered. For more information refer to the detailed description of in Function.

Note When only changed data is transmitted and the data area contains values in double word format, the user is responsible for ensuring that these double word values are actually located in one of the maximum 12 double words of the data area to be acquired. Distribution over two consecutive data double words could otherwise lead to the transmission of only one word of the double word value (high or low word) because a change has occurred in only that particular word. The missing word could lead to processing problems on the partner that receives this value.

Name: ReturnedParameter Declaration: INPUT Data type ANY Default: P#P 0.0 VOID 0 (null pointer) Explanation Parameter output area.



Range of values:

P#DBxx.DBX yy.0 DWORD zz xx : Data block number 1...32767 yy : Byte number zz : Number of double words 1...12 starting at byte number yy Example: P#DB20.DBX 100.0 DWORD 4 Remember the periods and spaces when entering the pointer! No parameter specified: Default (null pointer) is valid.

The partner object receiving the parameter values reports back the currently valid local parameter values. These values are displayed at the ReturnedParameter output. If the partner object is set to ’local’ and if an input is made there, then parameters changed locally are displayed here at ReturnedParameter. The ANY pointer defines the data area in which the received parameter values are output. This data area must be within a data block and its length can vary between 1 and 12 data double words. The length must be identical with the length set for ParameterInput. After startup of the local or partner PLC, or after restoring a connection, an automatic general request ensures that the current, local, valid parameters are displayed at ReturnedParameter. How to read out the time stamp received with the data is described in the section Notes on the SINAUT time stamp. If you do not require the parameter, simply leave it open. If the parameter setting is incorrect (data area not a data block, length greater than 12 or length different from the length set for ParameterInput), an error message to this effect is entered in the diagnostics buffer (event ID B114, [Info2/3] = 11). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.

Name: LocalOperation Declaration: OUTPUT Data type BOOL Default: FALSE Explanation Return message from partner object: Object is set to local operation. Range of





A parameter can also be set locally at the partner object that receives the parameter. The partner object then must be set to ’local’ at the Local input parameter (see FB Par12D_R below). The current status of the Local input parameter is reported by the partner object and displayed here at the LocalOperation output. As long as the partner object is set to 'local', no parameters are accepted there from other locations. After startup of the local or partner PLC, or after restoring a connection, an automatic general request ensures that the current, local, valid status is displayed at LocalOperation. How to read out the time stamp received with the data is described in the section Notes on the SINAUT time stamp. If you do not require the parameter, simply leave it open.




Whenever the FB has received new data and has output it to the outputs ReturnedParameter or LocalOperation, the NewData output is set to TRUE for one OB1 cycle. The output is intended for user-specific further processing, for example to react in a specific way to receipt of new data. If you do not require the parameter, simply leave it open.

Name: Release Declaration: IN_OUT Data type BOOL Default: FALSE Explanation Trigger input for sending the currently pending parameter values Range of


M 0.0 ... M n.7 DBm.DBX 0.0 ... n.7



You can use this input parameter when the parameter is entered by software, for example at an operator panel (OP). The Release input should then be set using a function key on the OP. You can then enter several parameters initially on the OP. They are only transmitted when the Release function key is activated because the change check only begins with a 1 signal at the Release input and the data double words that have changed since the last transmission are transmitted from the data area defined by ParameterInput. If you always want to transmit the entire data area defined with ParameterInput and not only the changed parameter values, you should use the RetransmitAll input parameter instead of Release. The Release input is reset automatically. You should therefore only specify memory or data inputs as the input. The automatic reset would not work with a digital input. Data checks: The same safety checks are carried out as with ContinuousEnterFunct = TRUE. Refer to the description there. If you do not require the parameter, simply leave it open.


Note


Name: RetransmitAll Declaration: IN_OUT Data type BOOL Default: FALSE Explanation Trigger input for transmitting (or retransmitting) the entire data area defined

by ParameterInput. Range of


M 0.0 ... M n.7 DBm.DBX 0.0 ... n.7



You can use this input parameter when the parameter is entered by software, for example at an operator panel (OP). The RetransmitAll input should then be set using a function key on the OP. When a 1 signal is detected at the RetransmitAll input, the entire data area defined by ParameterInput is transmitted. Changes are not checked. The RetransmitAll input is reset automatically. You should therefore only specify memory or data inputs as the input. The automatic reset would not work with a digital input. Since there is no change check, this would lead to continuous transmission of all parameter values as long as the digital input has a 1 signal. The RetransmitAll input can also be used as an option in addition to Release or ContinuousEnterFunct = TRUE when new parameter values were entered but could not be transmitted to the partner (for example because of a disrupted connection or because the partner object was previously set to ’local’). You can then trigger transmission of the entire data area defined by ParameterInput using the RetransmitAll input. All changes that were previously entered but are not yet available at the partner are consistently included. The RetransmitAll input can also be used as an independent transmission trigger when you always want to send all entries and not just those that have changed. You should then use RetransmitAll instead of Release that only sends the changed parameter values. Data checks: The same safety checks are carried out as with ContinuousEnterFunct = TRUE. Refer to the description there. If you do not require the parameter, simply leave it open.


Name: ApplyRemoteParamMan Declaration: IN_OUT Data type BOOL Default: FALSE Explanation Trigger input for synchronization of the input area with the returned area. Range of




The input triggers a one-time synchronization of the ParameterInput input area with the ReturnedParameter area. All the parameter values from the ReturnedParameter area are then copied to the ParameterInput area. The send buffer is also synchronized with the returned parameter values. The ApplyRemoteParamMan input is reset automatically. You should therefore only specify memory or data inputs as the input. The automatic reset would not work with a digital input. The result would be a constant synchronization as long as the digital input has a 1 signal. If you do not require the parameter, simply leave it open.


3.5.20 ST7 parameter typical FB Par12D_R

Function Receive 1 to 12 parameter values (each 1 double word) or enter locally and send back the current, locally valid parameter values. The content of each double word may be a value in double word format (e.g. DINT, REAL etc.); it can also be a mixture of other formats which together form a double word, for example, ● 4 bytes, or ● 2 words, or ● 2 bytes plus 1 word. The data area in which the received parameter values are output is defined with the ParameterOutput parameter in the form of an Any pointer. This data area must be within a data block and its length can vary between 1 and 12 double words. You can also use the block to enter the parameter values locally. The input area for this is defined as an Any pointer with the LocalParameterInput parameter. It must be located within a data block and its length must be identical to the length configured at the ParameterOutput parameter. The block only sends the changed data area. However, the complete parameter set is returned in response to a general or single request. Bumpless switchover between the Local and Remote operating modes is guaranteed.






The subscriber number of the partner with which the FB communicates, i.e. from which the FB receives data and to which it also sends data, must be specified. For a process typical such as Par12D_R, this is usually the subscriber no. of the master PLC or the ST7cc control center. Point to note with PartnerNo = 0 Enter 0 for the parameter when the typical can exchange data with more than one partner, for example, when there are several control centers wanting to send data to this typical and have the local, valid parameter values returned. If the PLC receives a message for the object set here, and PartnerNo is greater than 0, the system checks whether the source subscriber number in the message is identical to the PartnerNo set here. If they are different, the received information is discarded. An error message to this effect is entered in the diagnostic buffer (event ID B130). This check is not made if PartnerNo = 0. Regardless of the sender, each message addressed to the object is also passed on to the object. If the set PartnerNo is greater than 0 and this number was not found in the administration (in DB-BasicData), an entry is made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.


Note

When using the block in the PLC of a node station, you should consider the consequences of PartnerNo = 0! If the PLC of the node station maintains both connections to higher-level subscribers as well as to lower-level stations, a message with PartnerNo = 0 is transferred to all subscribers both "up" and "down".





The number of the object (= DB number) on the partner with which the FB communicates, i.e.from which the FB receives data and to which which it sends data, must be specified. The parameter setting PartnerObjectNo = 0 is necessary in the following situations: 1. The partner is not an S7-CPU; in other words, there is no object = DB


2. There is more than one partner (PartnerNo = 0) that wants to exchange data data with this typical. The corresponding objects of these partners will then generally have different numbers; in other words, no unique number can be specified here.




Range of values:





Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is not enabled, the FB can only communicate at the organizational level; in other words, ORG messages can be sent and received. A query is, for example, answered, however the reply message contains the data valid at the time the function was disabled. Any parameter values that are still received are not output.

Name: ImageMemory Declaration: INPUT Data type BOOL Default: TRUE Explanation Image memory principle.

TRUE or FALSE Bit memory Data bit

M 0.0 ... M n.7 L 0.0 ... L n.7 DBm.DBX 0.0 ... n.7

Range of values:

No parameter specified: Default value TRUE is valid. Here, you must specify whether the message is transferred according to the

image memory principle or, if this is not the case, according to the send buffer principle. The image memory principle means that messages can be stored using less memory on the TIM and the traffic on the WAN is as low as possible. The default TRUE was chosen because the image memory principle is the best choice in practice for most data transmissions. In general, as the user you only need to change the default setting of the image memory parameter with a few objects, namely objects whose data changes must be stored on the TIM and sent to the partner singly, for example alarms with time stamp.



M 0.0 ... M n.7 L 0.0 ... L n.7 DBm.DBX 0.0 ... n.7

Range of values:

No parameter specified: Default value TRUE is valid. You will find information on the parameter assignment in the Unconditional

parameter.





M 0.0 ... M n.7 L 0.0 ... L n.7 DBm.DBX 0.0 ... n.7

Range of values:

No parameter specified: Default value TRUE is valid. Note on the use of the Conditional and Unconditional parameter settings:

With the two parameters Conditional and Unconditional, you can decide whether a message is transmitted by the TIM immediately when data changes or at a later point in time. 1. If the transmission does not need to be made immediately, set the






Here, you specify whether the message with the returned parameter and the ’Local’ status should be sent with a time stamp. The prerequisite is that the time provided by the local TIM is available on the PLC. For more detailed information, refer to the description of FC TimeTask. If no parameter is specified, the default is FALSE; in other words, data is transmitted without a time stamp.



Name: Local Declaration: INPUT Data type BOOL Default: FALSE Explanation Local parameter input released.

TRUE or FALSE Input Bit memory Data bit


Range of values:

No parameter specified: Default value FALSE is valid This input is used to enable local input of a parameter over the data area

addressed with LocalParameterInput. Parameters sent for example by the control center are not accepted by the object as long as Local = TRUE. The current status of the Local input is transferred to the partner. Bumpless switchover: • When there is a switchover from Local = 0 to Local = 1, the last values at

ParameterOutput are held until new parameter values are entered over LocalParameterInput.

• When there is a switchback from Local = 1 to Local = 0, the last values at ParameterOutput are held until the block receives new parameter values from the remote partner.

Special case: You can also enter the parameter values during local input directly in the output area defined by ParameterOutput. Either you do not specify an input area for LocalParameterInput or you specify the same data area both for LocalParameterInput and ParameterOutput. This type of the parameter entry cannot be prevented by the Local input. Regardless of the Local status, the values entered in the output area are sent immediately to the partner by the function block. Local parameter entries can therefore be made regardless of the status of the Local input. Local only influences the acceptance of parameters sent by the remote partner. • If Local = 0, the parameters sent by the remote partner are accepted and

output to the ParameterOutput data area. • If Local = 1, any parameters sent by the remote partner are rejected. In this special situation, the Release input and ContinuousEnterFunct have no function. A status change of the Local parameter is always sent by the TIM according to the send buffer principle (even when the parameter ImageMemory = TRUE). This ensures that the optional synchronization of the input and output area on the partner is always performed correctly (see FB Par12D_S, parameters ApplyRemoteParamMan and ApplyRemoteParamAuto).



Note Please read the note on the ContinuousEnterFunct parameter.

Name: ContinuousEnterFunct Declaration: INPUT Data type BOOL Default: FALSE Explanation Continuous local parameter acquisition: Range of


With this parameter, you can decide whether the parameter values in the LocalParameterInput input area should be continuously read in and changes checked. The change check is implemented by comparing the current parameter values at ParameterOutput. Changes in the input area are copied immediately to the output area and transmitted to the partner. Only changed values are sent. If there is more than one change, the block sends the data area in which all changed parameter values are located. The ContinuousEnterFunct = TRUE parameter setting only takes effect when the following conditions are met: • An input area is defined by the LocalParameterInput parameter and this

is not identical to the output area defined by ParameterOutput. and

• There is a 1 signal at the Local input (= TRUE). This method of local parameter acquisition is suitable when the parameter values are entered in the LocalParameterInput area by software, but can also be used for entering the parameters from an operator panel (OP) when the OP has no separate function key with which to trigger acceptance. For more detailed information and related parameters, refer to the section Function. If you do not require the parameter, simply leave it open.




Note When ContinuousEnterFunct = TRUE, the values available at LocalparameterInput are entered immediately and passed to ParameterOutput when the 1 signal at the Local input is detected assuming the local input values differ from the current parameter value output at this point in time.

Name: LocalParameterInput Declaration: INPUT Data type ANY Default: P#P 0.0 VOID 0 (null pointer) Explanation Local parameter input area. Range of

values: P#DBxx.DBX yy.0 DWORD zz xx : Data block number 1...32767 yy : Byte number zz : Number of double words 1...12 starting at byte number yy Example: P#DB20.DBX 100.0 DWORD 4 Remember the periods and spaces when entering the pointer! No parameter specified: Default (null pointer) is valid.

The ANY pointer defines the data area in which the parameter values to be acquired locally are located. This data area must be within a data block and its length can vary between 1 and 12 data double words. The length must be identical with the length set for ParameterOutput. The content of each double word may be a value in double word format (e.g. DINT, REAL etc.); it can also be a mixture of other formats which together form a double word, for example, • 4 bytes, or • 2 words, or • 2 bytes plus 1 word. If you do not require the parameter, simply leave it open. If the parameter setting is incorrect (data area not a data block, length greater than 12 or length different from the length set for ParameterOutput), an error message to this effect is entered in the diagnostics buffer (event ID B114, [Info2/3] = 11). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.



Note Only changed data is transmitted to the partner. If the data area contains values in double word format, the user is responsible for ensuring that these double word values are actually located in one of the maximum 12 double words of the data area to be acquired. Distribution over two consecutive data double words could otherwise lead to the transmission of only one word of the double word value (high or low word) because a change has occurred in only that particular word. The missing word could lead to problems in processing on the partner that receives this value (applies, for example to ST7cc, but not to an S7 CPU).

Name: ParameterOutput Declaration: INPUT Data type ANY Default: P#P 0.0 VOID 0 (null pointer) Explanation Parameter output area. Range of

values: P#DBxx.DBX yy.0 DWORD zz xx : Data block number 1...32767 yy : Byte number zz : Number of double words 1...12 starting at byte number yy Example: P#DB20.DBX 100.0 DWORD 4 Remember the periods and spaces when entering the pointer! No parameter specified: Default (null pointer) is valid. This is, however, not permitted! A pointer >< null pointer must be specified.



The ANY pointer defines the data area in which the locally entered parameter values or those received from the partner are output. This data area must be within a data block and its length can vary between 1 and 12 double words. The content of each double word may be a value in double word format (e.g. DINT, REAL etc.); it can also be a mixture of other formats which together form a double word, for example, • 4 bytes, or • 2 words, or • 2 bytes plus 1 word. FB Par12D_R stores the received data without further processing in the data area defined by ParameterOutput. The user program is responsible for evaluating and processing received data. When only changed data is sent by the partner object Par12D_S, it is possible that only part of the data output area is newly written, namely, the area in which the changes were detected at the acquisition end. If the parameter setting is incorrect (null pointer, length greater than 12, data area not a data block), an error message to this effect is entered in the diagnostics buffer (event ID B114, [Info2/3] = 11). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.

Note When only the changed data area is received, this area consists of the first and the last double word in which a change was detected and all words located in between, even if these have not changed. Example: The area to be read is 10 double words long. In this case, changes were detected in the 2nd, 5th and 8th double words. The transmitted area is therefore from the 2nd to the 8th double word inclusive.






Whenever the FB has received new parameter values from the partner object and has output them to the output field ParameterOutput, the NewData output is set to TRUE for one OB1 cycle. This also applies when there is new local input when Local = 1. The output is intended for user-specific further processing, for example to react in a specific way to receipt of new data. If you do not require the parameter, simply leave it open.

Name: Release Declaration: IN_OUT Data type BOOL Default: FALSE Explanation Input for the acceptance of local parameter entry. Range of


I 0.0 ... I n.7 M 0.0 ... M n.7 DBm.DBX 0.0 ... n.7

The acceptance of the parameter value at the LocalParameterInput parameter input can be triggered over this input by a signal edge change. A change from 0 to 1 at the Release input is taken into account only when the following conditions are met: • An input area is defined by the LocalParameterInput parameter and this

is not identical to the output area defined by ParameterOutput. and

• There is a 1 signal at the Local input (= TRUE). You can use this Release input parameter when the parameter is entered by software, for example at an operator panel (OP). The Release input should then be set using a function key on the OP. You can then enter several parameters initially on the OP. The parameter values are read in and checked for changes only when the Release function key is activated. The change check is implemented by comparing the current parameter values at ParameterOutput. Changes in the input area are then copied immediately to the output area and transmitted to the partner. Only changed values are sent. If there is more than one change, the block sends the data area in which all changed parameter values are located. The Release input is reset automatically. Instead of a memory bit or data bit, a digital input can also be specified as the input. The automatic reset would not work with a digital input. This does not, however, have negative effects. The triggering of the acquisition over Release is triggered by a signal edge change; in other words, it occurs only once. If you do not require the parameter, simply leave it open.




Note


3.5.21 ST1 setpoint typical FB STZ01

Function Send 1 setpoint (16-bit ST1 format) in a message in ST1 format.

Note With FB STZ01, data can only be transmitted when FC Safe is included at the end of the cyclic SINAUT program.



values: 1 ... 254

The subscriber number of the partner with which the FB communicates, i.e. to which the FB sends data, must be specified. With an operator typical such as STZ01, this is normally the subscriber number of an ST1 station. The parameter setting PartnerNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 254), an error message to this effect is entered in the diagnostic buffer (event ID B100). If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.




values: 2 ... 250




values: 0 or 1 ... 255



values: 0 ... 255






Range of values:



Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is disabled the FB only checks to see if the disabled status has been canceled. The FB cannot communicate on the organizational level in this status because FB STZ01 cannot send or receive organizational messages.

Name: EnterInput Declaration: INPUT Data type BOOL Default: FALSE Explanation Enter input (for 'hardware' setpoint). Range of





A setpoint at the SetpointInput can be applied over this input triggered by a signal edge change. A signal change at EnterInput is only taken into account when the parameter ContinuousEnterFunct = FALSE. If this condition is fulfilled, the setpoint entered at SetpointInput is applied and transmitted by a signal change from 0 to 1 even if the newly entered setpoint is identical to the previously sent setpoint. This method of applying setpoints is suitable for input at appropriate hardware, for example a console or control panel but can also be used for entering setpoints at an operator panel (OP). In the latter case, it must be possible to trigger the input by a separate function key on the OP. If you do not require the parameter, simply leave it open.

Name: ContinuousEnterFunct Declaration: INPUT Data type BOOL Default: FALSE Explanation Apply setpoint continuously (for ’software’ setpoint). Range of


With this parameter, you can decide whether the setpoint at SetpointInput should be continuously read in and changes checked. The change evaluation is made by comparing the current with the last setpoint that was sent. This method of applying a setpoint is suitable for input by appropriate software but can also be used for entering setpoints at an operator panel (OP) if it does not have a separate function key that can be used to trigger the input. If you do not require the parameter, simply leave it open.

Name: ST1_SetpointType Declaration: INPUT Data type INT Default: 0 Explanation ST1 setpoint type. Range of

values: 0 ... 2 No parameter specified: Default value 0 is valid.



For ST1 setpoints, an entry is necessary to allow the setpoint block to recalculate the entered setpoint into the correct ST1 format. The meaning of the values 0 ... 2 is as follows: 0 = S5 analog value format, i.e. the ST1 setpoint is in the range of + 2048 and is left justified in the setpoint word; any overflow or wire break is indicated in the three least significant bits. 1 = As 0 but the ST1 setpoint in the range of + 2048 is right justified in the setpoint word and contains no code bits for overflow or wire break. 2 = Send without recalculating, e.g. for bit patterns or 16-bit edited values.

Note When 0 or 1 are set for ST1_SetpointType, the ST1 typical STZ01 assumes that at the input SetpointInput there are values in the range of the S7 analog modules, i.e. 0 ... 27648 = 0 ... 100 % or + 27648 = + 100%, overflow is indicated by 7FFFH and underflow or wire break by 8000H. Only then can the typical calculate the setpoints into ST1 format. Refer to the two following tables.

Table 3-9 Conversion of ST7 to ST1 raw value format for unipolar and life-zero setpoints

Acquired ST7 raw value

Transmitted ST1 raw value

ST1_SetpointType = 0 ST1_SetpointType = 1

Setpoint range in %

Unipolar e.g.

0 ... 20 mA

Life-zero e.g.

4 ... 20 mA Decimal Hexa

decimal Decimal 1)

Hexa decimal

Decimal Hexa decimal

Range

> 117,5925

%

> 23.515 mA

> 22.810 mA

32767 7FFF 4095 + overflow

bit

7FF9 4095 0FFF Overflow

117,5925 % :

100,0036 %

23.515 mA

: 20.0007

mA

22.810 mA

: 20.0005

mA

32511 :

27649

7EFF :

6C01

2408 :

2048

4B40 :

4000

2408 :

2048

0968 :

0800

Over flow

range

100 % :

0 %

20 mA :

0 mA

20 mA :

4 mA

27648 : 0

6C00 :

0000

2048 : 0

4000 :

0000

2048 : 0

0800 :

0000

Nominal range

-0,0036 % :

-17,5925 %

-0.0007 mA

: -3.5185

mA

3.9995 mA

: 1.1852

mA

-1 :

-4864

FFFF :

ED00

0 :

-360

0000 :

F4C0

0 :

-360

0000 :

FE98

Under flow

range

< -17,5925

%

< -3.5185 mA

< 1.1852 mA

-32768 8000 0 + wirebreak

bit

0002 0 0000 Underflow/wire break




Table 3-10 Conversion of ST7 to ST1 raw value format for bipolar setpoints

Acquired ST7 raw value Transmitted ST1 raw value ST1_SetpointType = 0 ST1_SetpointType = 1

Setpoint range in %

Bipolar e.g.

+ 20 mA Decimal Hexa decimal Decimal 1) Hexa

decimal Decimal Hexa

decimal

Range

> 117,5925

%

> 23.515 mA

32767 7FFF 4095 + overflow

bit

7FF9 4095 0FFF Overflow

117,5925 % :

100,0036 %

23.515 mA

: 20.0007

mA

32511 :

27649

7EFF :

6C01

2408 :

2048

4B40 :

4000

2408 :

2048

0968 :

0800

Over flow

range

100 % :

0 % :

-100 %

20 mA : 0 :

-20 mA

27648 : 0 :

-27648

6C00 :

0000 :

9400

2048 : 0 :

-2048

4000 :

0000 :

C000

2048 : 0 :

-2048

0800 :

0000 :

F800

Nominal range

-100,0036 % :

-117,5925 %

-20.0007 mA

: -23.516

mA

-27649 :

-32512

93FF :

8100

-2048 :

-2408

C000 :

B4C0

-2048 :

-2408

F800 :

F698

Under flow

range

< -117,5925

%

< -23.516 mA

-32768 8000 0 + Wire

break bit

0002 0 0000 Underflow/wire break


Name: SetpointInput Declaration: INPUT Data type WORD Default: 0 (W#16#0) Explanation Setpoint input word. Range of

values: Input S words Memory words Data words




How a setpoint available at SetpointInput is processed depends on whether it is a hardware or software input. The user specifies the type of input with the ContinuousEnterFunct parameter: • ContinuousEnterFunct = FALSE (= hardware input)

The setpoint at SetpointInput is only read in as long as a 1 signal is detected at EnterInput. The setpoint that is read in is then transmitted if no error is detected during the 1-out-of-n check, and if the central enable memory bit is set. This is automatically set by FC Safe following a selected time delay set there (see FC Safe, InputDelayTime parameter). The next setpoint is first read in by the FB when a 0 signal is detected for at least one OB1 cycle at EnterInput. If a 1-out-of-n error is detected the next time a value is applied to the hardware input, the entered setpoint is no longer processed. A new setpoint is first read in when no hardware input has been acquired in the PLC for one OB1 cycle; in other words, not only for this block but also for all other command and setpoint input blocks with hardware input. The FB enters the detected 1-out-of-n error in the diagnostic buffer (event ID B172). The error status is also indicated over the InputError output of FC Safe (see FC Safe, InputError parameter) and continues to be indicated as long as the error remains.

• ContinuousEnterFunct = TRUE (= software input) The setpoint at SetpointInput is read in continuously and checked for changes. The change evaluation is made by comparing the current with the last setpoint that was sent. The setpoint is sent immediately every time a change occurs unless the 1-out-of-n check detects an error. Without the setpoint having changed, a new transmission of the software setpoint can be triggered over the SendSoftSetpoint input (see below). While for hardware input an empty cycle must be detected before a new setpoint can be sent by the block, for software input a new setpoint can be transmitted in every OB1 cycle. This is possible only when there is no other software setpoint or software command in this cycle. Otherwise a 1-out-of- n error is detected. If a 1-out-of-n error is detected during the software input, the entered setpoint is no longer processed. A new setpoint is first read in when no software input has been acquired in the PLC for one OB1 cycle; in other words, not only for this block but also for all other command and setpoint blocks with software input. The FB enters the detected 1-out-of-n error in the diagnostic buffer (event ID B172). Appropriate error bits are also set in the central data block "BasicData" where they can be queried by the software. For more detailed information, refer to the description of FC Safe.



3.5.22 ST1 setpoint typical FB STA01

Function Receive 1 setpoint (16-bit ST1 format) from a message in ST1 format.



values: 0 or 1 ... 8

The subscriber number of the partner with which the FB communicates, i.e. from which the FB receives data, must be specified. With a process typical such as STA01, this is normally the subscriber number of the ST1 master. The parameter is optional. It is not required for addressing or for any checks. It is therefore possible to enter 0 or leave the parameter open (default value 0 then applies).


values: 2 ... 250






values: 0 or 1 ... 255



values: 0 ... 255




Range of values:





Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is disabled the FB only checks to see if the disabled status has been canceled. Any setpoints that are still received are not output. The FB cannot communicate on the organizational level in this status because FB STA01 cannot send or receive organizational messages.

Note If the Enabled input can be controlled by a switch, this local disable means that no more setpoints are output if they are still received. Since the block is, however, not capable of sending ORG messages, it cannot report this local disable back to the partner itself. This must be implemented by the user with a separate message, for example MTZ01.

Name: ST1_SetpointType Declaration: INPUT Data type INT Default: 0 Explanation ST1 setpoint type. Range of

values: 0 ... 2 No parameter specified: Default value 0 is valid.

For ST1 setpoints, an entry is necessary to allow the setpoint block to recalculate the received ST1 setpoint into the correct ST7 format. The meaning of the values 0 ... 2 is as follows: 0 = S5 analog value format, i.e. the received ST1 setpoint is in the range of + 2048 and is left justified in the setpoint word; any overflow or wire break is indicated in the three least significant bits. 1 = as 0, but the received ST1 setpoint is located right justified in the range + 2048 in the setpoint word. The setpoint does not contain any code bits for overflow or wire break. 2 = the received ST1 setpoint is output without recalculation, for example because it is a bit pattern or a 16-bit edited value. If 0 or 1 is set for ST1_SetpointType, the setpoints received in ST1 raw value format are converted to ST7 raw value format. Refer to the following table.



Table 3-11 Conversion from ST1 to ST7 raw value format

RECEIVED ST1 raw value ST1_SetpointType = 0 ST1_SetpointType = 1

Converted ST1 raw value Setpoint range in %

Decimal 1)

Hexa decimal

Decimal Hexa decimal

Decimal Hexadecimal

Range

> 117,5781 %

> 2408 + overflow

bit

> 4B40 or 7FF9

> 2408 > 0968 32767 7FFF Overflow

117,5781 % :

100,0036 %

2408 :

2049

4B40 :

4008

2408 :

2049

0968 :

0808

32508 :

27661

7EFC :

6C0D

Overflow range

100 % :

0 % :

-100 %

2048 : 0 :

-2048

4000 :

0000 :

C000

2048 : 0 :

-2048

0800 :

0000 :

F800

27648 : 0 :

-27648

6C00 :

0000 :

9400

Nominal range

-100,0036 % :

-117,5781 %

-2049 :

-2408

BFF8 :

64C0

-2049 :

-2408

F7FF :

F698

-27661 :

-32508

93F3 :

8104

Underflow range

< -117,5781 %

< -2408 or wire

break bit

< 64C0 or 0002

< -2408 < F698 -32768 8000 Underflow/ wire break

1) The decimal value relates to the bits 3 through 15. Bits 0 through 2 contain code bits (overflow and wire break)

Name: SetpointOutput Declaration: OUTPUT Data type WORD Default: 0 (W#16#0) Explanation Setpoint output word. Range of



The setpoint received by the FB is output to the output word specified here at SetpointOutput.




Range of values:

Output Bit memory Data bit No parameter specified: Default value FALSE is valid


Whenever the FB has received a new setpoint and has output it to SetpointOutput, the NewData output is set to TRUE for one OB1 cycle. The output is intended for user-specific further processing, for example to react in a specific way to receipt of new data. If you do not require the parameter, simply leave it open.

3.5.23 ST7 data typical FB Dat12D_S

Function Send maximum of 12 double words with any data content. The content of each double word may be a value in double word format (e.g. DINT, REAL etc.); it can also be a mixture of other formats which together form a double word, for example, ● 4 bytes, or ● 2 words, or ● 2 bytes plus 1 word. Sending the data area can be triggered in two ways: ● By a change check. Transmission is triggered as soon as a bit changes. (Parameter

SendOnChange = TRUE) ● The user program decides when a transmission will take place (signal edge change from

0 to 1 at TriggerInput). This could also be a time-driven transmission. This case, you could use FC Trigger.

You can also specify whether the transmission includes all data or only the data double words that have changed.

Note When only changed data is transmitted and the data area contains values in double word format, the user is responsible for ensuring that these double word values are actually located in one of the maximum 12 double words of the data area to be acquired. Distribution over two consecutive data double words could otherwise lead to the transmission of only one word of the double word value (high or low word) because a change has occurred in only that particular word. The missing word could lead to problems in processing on the partner that receives this value (applies, for example to ST7cc, but not to an S7 CPU).





values: : 0 or 1 ... 32000

The subscriber number of the partner with which the FB communicates, i.e. to which the FB sends data, must be specified. For a process typical such as Dat12D_S, this is usually the subscriber no. of the master PLC or the ST7cc control center. Point to note with PartnerNo = 0 The data is transmitted to all subscribers for which a connection has been configured. The following PartnerObjectNo parameter is then irrelevant. If the set PartnerNo was not found in the administration (in DB-BasicData), an entry to this effect is made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.



values: 0 or 1 ... 32000

The number of the object (= DB number) on the partner with which the FB communicates, i.e. to which the FB sends data, must be specified. Point to note with PartnerObjectNo = 0 This parameter assignment is useful, if PartnerNo = 0 was set. If the PartnerObjectNo is missing, there must be a list on the partner PLC from which the missing object number can be recognized (see FC ListGenerator). If the subscriber specified by PartnerNo is an ST7cc control center, the PartnerObjectNo does not need to be specified in the FB because there are no DBs as destination objects in ST7cc as there are in a CPU. ST7cc decodes its messages solely based on the source address in the message.





Range of values:




Name: ImageMemory Declaration: INPUT Data type BOOL Default: TRUE Explanation Enable block processing.


Range of values:







TRUE or FALSE Range of values: Bit memory

Data bit No parameter specified: Default value TRUE is valid.

M 0.0 ... M n.7 L 0.0 ... L n.7 DBm.DBX 0.0 ... n.7




Range of values:

Bit memory Data bit

M 0.0 ... M n.7 L 0.0 ... L n.7 DBm.DBX 0.0 ... n.7










Name: SendOnChange Declaration: INPUT Data type BOOL Default: FALSE Explanation Send on change. Range of


Here, you specify whether the FB checks for changes within the acquired data area (to determine whether at least one bit has changed). If a change is detected, a transmission of the data area is triggered automatically. Whether the entire area is transmitted or only the changed part can be specified with the SendAll parameter (refer to the explanations on the relevant parameter). If no parameter is specified, the default is FALSE; in other words, there is no change-driven data transmission. Transmission must then be triggered by the user at the TriggerInput input parameter.

Name: TriggerInput Declaration: INPUT Data type BOOL Default: FALSE Explanation Trigger input. Range of





If required, this parameter can be used to specify an input over which the user can trigger the transmission *) of the data message at any time (signal edge from 0 to 1). Example: Time-driven analog value transmission with time stamp for supplying an analog value archive in the control center. Note: To prevent these messages with time stamps from being overwritten when saving on the station TIM, the ImageMemory parameter must be set to FALSE. FC Trigger can be used for time-driven triggering of a transmission over TriggerInput (for more detailed information, refer to the description of this block). If you do not require the parameter, simply leave it open. You should, however, then set the SendOnChange parameter to TRUE so that the data is transmitted automatically at every change. *) TriggerInput actually only triggers transmission indirectly. With a 0/1 edge at TriggerInput, the message is put together with its current values and transferred to the local TIM. The TIM is responsible for the actual transmission to the partner. Transmission is immediate over a dedicated line or wireless link; with a dial-up connection, it is possible that the message is saved first on the TIM and sent at a later point in time (for example, because the message is marked as a "conditional spontaneous" message; see the Conditional parameter).

Note You can also select a combination of SendOnChange plus TriggerInput. This means that a transmission is triggered both when a change is detected and at every signal edge change from 0 to 1 at the TriggerInput.

Note

If you use neither SendOnChange nor TriggerInput to trigger data transmission, the data will only be transmitted when there is a single request for this data object or within the framework of a general request.

Name: SendAll Declaration: INPUT Data type BOOL Default: TRUE Explanation Send all data with every transmission. Range of

values: TRUE or FALSE



Here, you specify whether the FB will transfer or data of the area defined with DataInput or only changed data. The transmission can be triggered by the activated change check (SendOnChange = TRUE) or by TriggerInput. • SendAll = TRUE always send all data • SendAll = FALSE send only changed data

– Exception: If a transmission is triggered over TriggerInput, and no data has changed at this point in time, the entire area is transmitted (in this exceptional situations, corresponds to SendAll = TRUE).

If no parameter is specified, the default TRUE applies; in other words, the entire area is always transmitted.

Note When only the changed data area is transmitted (SendAll = FALSE), this area consists of the first and the last double word in which a change was detected and all words located in between, even if these have not changed. Example: The area to be read is 10 double words long. In this case, changes were detected in the 2nd, 5th and 8th double words. The transmitted area is therefore from the 2nd to the 8th double word inclusive.

Note

If there is a single request for this data object or within the framework of a general request, all data words of the area defined by DataInput are always transmitted.

Name: DataInput Declaration: INPUT Data type ANY Default: P#P 0.0 VOID 0 (null pointer) Explanation Data input area. Range of




The ANY pointer describes the data area in which the data to be acquired is located. This data area must be within a data block and its length can vary between 1 and 12 data double words. The content of each double word may be a value in double word format (e.g. DINT, REAL etc.); it can also be a mixture of other formats which together form a double word, for example, • 4 bytes, or • 2 words, or • 2 bytes plus 1 word. If the parameter setting is incorrect (null pointer, length greater than 12, data area not a data block), an error message to this effect is entered in the diagnostics buffer (event ID B114, [Info2/3] = 11). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.

Note When only changed data is transmitted and the data area contains values in double word format, the user is responsible for ensuring that these double word values are actually located in one of the maximum 12 double words of the data area to be acquired. Distribution over two consecutive data double words could otherwise lead to the transmission of only one word of the double word value (high or low word) because a change has occurred in only that particular word. The missing word could lead to problems in processing on the partner that receives this value (applies, for example to ST7cc, but not to an S7 CPU).

3.5.24 ST7 data typical FB Dat12D_R

Function Receive maximum of 12 double words with any data content. The content of each double word may be a value in double word format (e.g. DINT, REAL etc.); it can also be a mixture of other formats which together form a double word, for example, ● 4 bytes, or ● 2 words, or ● 2 bytes plus 1 word. FB Dat12D_R stores the received data without further processing in the data area defined by DataOutput. The user program is responsible for evaluating and processing received data.





values: 1 ... 32000

The subscriber number of the partner with which the FB communicates, i.e. from which the FB receives data, must be specified. With an operator typical such as Dat12D_R, this is normally the subscriber number of a station PLC. The parameter setting PartnerNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 32000), an error message to this effect is entered in the diagnostic buffer (event ID B100). If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected. If the PLC receives a message for the object set here, the system checks whether the source subscriber number in the message is identical to the PartnerNo set here. If they are different, the received information is discarded. An error message to this effect is entered in the diagnostic buffer (event ID B130).


values: 1 ... 32000

The number of the object (= DB number) on the partner with which the FB communicates, i.e. from which the FB receives data, must be specified. The parameter setting PartnerObjectNo = 0 is not permitted! If the parameter setting is incorrect (< 1 or > 32000), an error message to this effect is entered in the diagnostic buffer (event ID B102). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected. If the PLC receives a message for the object set here, the system checks whether the source object number in the message is identical to the PartnerObjectNo set here. If they are different, the received information is discarded. An error message to this effect is entered in the diagnostic buffer (event ID B131).





Range of values:



Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is not enabled, the FB can only communicate at the organizational level; in other words, ORG messages can be sent and received. A request can, for example, still be sent and the answer received, the received information is, however, not output to the area defined by DataOutput.

Name: DataOutput Declaration: INPUT Data type ANY Default: P#P 0.0 VOID 0 (null pointer) Explanation Data output area. Range of




The ANY pointer describes the data area in which the received data will be stored. This data area must be within a data block and its length can vary between 1 and 12 data double words. The content of each double word may be a value in double word format (e.g. DINT, REAL etc.); it can also be a mixture of other formats which together form a double word, for example, • 4 bytes, or • 2 words, or • 2 bytes plus 1 word. FB Dat12D_R stores the received data without further processing in the data area defined by DataOutput. The user program is responsible for evaluating and processing received data. When only changed data is sent by the partner object Dat12D_S, it is possible that only part of the data output area is newly written, namely, the area in which the changes were detected at the acquisition end. How to read out the time stamp received with the data is described in the section Notes on the SINAUT time stamp. If the parameter setting is incorrect (null pointer, length greater than 12, data area not a data block), an error message to this effect is entered in the diagnostics buffer (event ID B114, [Info2/3] = 4). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.

Note When only the changed data area is received, this area consists of the first and the last double word in which a change was detected and all words located in between, even if these have not changed. Example: The area to be read is 10 double words long. In this case, changes were detected in the 2nd, 5th and 8th double words. The transmitted area is therefore from the 2nd to the 8th double word inclusive.






Whenever the FB has received new data and has stored it in the data area defined by DataOutput, the NewData output is set to TRUE for one OB1 cycle. The output is intended for user-specific further processing, for example to react in a specific way to receipt of new data. If you do not require the parameter, simply leave it open.

3.5.25 ST1 data typical FB STKOP26W

Function Send a maximum of 26 words with any data content in a message with ST1 format. Sending the data area can be triggered in two ways: ● By a change check. Transmission is triggered as soon as a bit changes. (Parameter

SendOnChange = TRUE) ● The user program decides when a transmission will take place (signal edge change from

0 to 1 at TriggerInput). This could also be a time-driven transmission. This case, you could use FC Trigger.

All the data is always sent during a transmission. With certain restrictions, the block can be used as a substitute for putting together SINAUT ST1 messages with any data combination (keyword: custom message composition possible in ST1 using the STKOP and STEND function blocks and the element blocks). This block can therefore be used when a custom composed message is sent to an ST1 master. The evaluation can be performed there with the usual blocks ETKOP and ETEND as well as element blocks. The element blocks available in ST1 for processing data that is to be entered in the message, and the finalization block STEND, do not exist in ST7. The function of STEND is contained in FB STKOP26W. The data area must nevertheless be filled by the user. The change check and the triggering of the data transmission is also the responsibility of the user (exception: the message is transmitted at every bit change. (Refer to the SendOnChange parameter).

Object-oriented data transmission with SINAUT LSX The STKOP26W function block is particularly useful when object-oriented data needs to be transmitted to the SINAUT LSX control center system. Although this is also possible with the MTZ, ATZ and ZTZ function blocks, when there are several different data types belonging to an object, this is only possible with FB STKOP26W. Example 1: An analog value object consists of two data words, namely ● one word for example with status and limit value messages ● one word with the actual analog value.



These two data words could not be transferred separately with an FB MTZ and an FB ATZ. It would be possible to specify a different ST1 index number for the two FBs but because of FBs must be given the same ST1 object number, the messages would override each other on the station TIM. With STKOP26W, this is no longer a problem. Both information words of the object are acquired by only one FB (STKOP26W) and the ST1 object number is assigned only once (defined with the ST1_ObjectNo parameter). With ST1_IndexNo, the index number of the first data word in the object must be specified. The index numbers of the remaining data words are then obtained automatically as continuous numbers (always incremented by 1). If, in the example shown, the ST1 index number is specified as 3, this applies to the 1st data word with the status and limit value messages. The 2nd data word with the analog value then has ST1 index number 4. With STKOP26W, not only one ST1 object but also several identical objects can be transferred.. Starting with the sample object shown above that includes total of 2 words, up to 13 objects could be transmitted with one STKOP26W. The object size is specified as 32 bits (= two words) in the ST1_PACK_Value parameter and the number of the 1st ST1 object is specified with the ST1_ObjectNo parameter. Numbers of the other objects are then assigned continuously starting from this number (always incremented by 1). The ST1 index number set with ST1_IndexNo then applies to each of the individual objects. Example 2: 4 analog value objects each of two words (as defined in example 1) are to be transferred with STKOP26W.

Relevant parameters for FB STKOP26W: DataInput P#DB20.DBX 100.0 WORD 8 (Input data area are located in DB20,

starting at data byte 100, length 8 words) ST1_MessageNo

3

ST1_ObjectNo 12

The combination of these two addresses forms the valid object number for LSX, here, for example 1,12

ST1_IndexNo 3 ST1_PACK_Value 32 (block size per object = 32 bits = 2 words)

From this, the object numbers for LSX are obtained as shown in the following table as well as the index numbers valid for the individual information words. LSX has the information how the word with index 3 or with index 4 is to be processed for the object x,y.

DB20,

data byte Information content Index no. LSX

object no. 100, 101 Status and limit value messages QW1 3 1. Object 102, 103 Analog value QW1 4

1,12

104, 105 Status and limit value messages QW2 3 2. Object 106, 107 Analog value QW2 4

1,13


1,14


1,15




Name: PartnerNo Declaration: INPUT Data type: INT Default: 0 Explanation Subscriber no. of the partner. Range of

values: 0, 1 ... 8 or 1 ... 254

The subscriber number of the partner with which the FB communicates, i.e. to which the FB sends data, must be specified. With a process typical such as STKOP26W, this is normally the subscriber number of the ST1 master. If STKOP26W is used in the reverse transmission direction (see ReverseDirection parameter), the subscriber number of an ST1 station must be specified. Partner is the ST1 master: Range of values limited to 1 ... 8 (= ST1 master number) Partner is the ST1 station: Range of values limited to 1 ... 254 (= ST1 station number) Partner is ST7/ST7cc: Range of values limited to 1 ... 254 (= SINAUT ST7 subscriber number) Point to note with PartnerNo = 0 If STKOP26W is used in a station; in other words not in the reverse transmission direction (ReverseDirection = FALSE), the parameter setting PartnerNo = 0 is also permitted with STKOP26W. The data is then transferred to all subscribers to which a connection was configured; in other words, to all ST1 masters. If the parameter setting is incorrect (< 0 or > 8 or > 254), an error message to this effect is entered in the diagnostic buffer (event ID B100). If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.


Name: ST1_MessageNo Declaration: INPUT Data type: INT Default: 0



Explanation Message number for a message in ST1 format. Range of

values: 2 ... 250



Name: ST1_ObjectNo Declaration: INPUT Data type: INT Default: 0 Explanation Object number for a message in ST1 format. Range of

values: 0 or 1 ... 255

If a value higher than 0 is set, this is an ST1 message with an address expansion. This expanded addressing is not normally required except in conjunction with a SINAUT LSX control center system (see also section Object-oriented data transmission with SINAUT LSX). If the parameter setting is incorrect (< 0 or > 255), an error message to this effect is entered in the diagnostic buffer (event ID B104). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.

Name: ST1_IndexNo Declaration: INPUT Data type: INT Default: 0 Explanation Index number for a message in ST1 format. Range of

values: 0 ... 255

A value higher than 0 is permitted only when a value higher than 0 was also set for ST1_ObjectNo; in other words, an ST1 message with address expansion is to be transmitted. This expanded addressing is not normally required except in conjunction with a SINAUT LSX control center system (see also section Object-oriented data transmission with SINAUT LSX).



If the parameter setting is incorrect (< 0 or > 255), an error message to this effect is entered in the diagnostic buffer (event ID B105). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.

Name: ST1_PACK_Value Declaration: INPUT Data type: INT Default: 0 Explanation PACK value for a message in ST1 format with address expansion.

An ST1 message transferred with the expanded addresses object and index number (ST1_ObjectNo, ST1_IndexNo) can contain data for several objects. Only the number of the first object is transferred with the message. The numbers of the other objects are assigned without gaps beginning at this start object. The packing scheme; in other words, how many bits belong to a single object, is transferred in the message with the PACK value. Based on this PACK value, the ST1 message is then converted into several KOMSYS-X messages for SINAUT LSX in the master: One KOMSYS-X message per object with the amount of data specified with PACK. If the additional addresses ST1_ObjectNo and ST1_IndexNo are used, a setting must be made here with the ST1_PACK_Value parameter indicating the number of bits per data object (pack interval).

Range of values:

4, 8, 16, 32, 64, 128 or 256 [bits] No parameter specified: Default value 0 is valid. In this case, all data words of the area defined with DataInput belong to the object set with ST1_ObjectNo.

4 = 4 bits per object (= ½ byte per object; DataInput max. 5 words) 8 = 8 bits per object (= 1 byte per object; DataInput max. 11 words) 16 = 16 bits per object (= 1 word per object; DataInput max. 23 words) 32 = 32 bits per object (= 2 words per object; DataInput max. 26 words) 64 = 64 bits per object (= 4 words per object; DataInput max. 24 words) 128 = 128 bits per object (= 8 words per object; DataInput max. 24 words) 256 = 256 bits per object (= 16 words per object; DataInput only 16 words) For more detailed information on the ST1 object and ST1 index number as well as the packing scheme, refer to the section Object-oriented data transmission with SINAUT LSX and the SINAUT TD1/RX manual. If the parameter setting is incorrect (length other than 4, 8, 16, 32, 64, 128 or 256 [bits]), an error message to this effect is entered in the diagnostic buffer (event ID B106). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.



Note Depending on the selected PACK parameter, the data area specified with DataInput must not exceed a certain maximum. You should therefore note the maximum permitted length shown in the list above. If an error is detected, an error message to this effect is entered in the diagnostic buffer. See also DataInput parameter.

Note

In addition to the specified maximum lengths, make sure that with an interval of 2, 4 or 8 words, a multiple of this interval matches the data area specified by DataInput. An interval of 2 words, for example does not match a data area to be transferred with the length of 15 words. This would have to be either 14 or 16 words. If an error is detected, an error message to this effect is entered in the diagnostic buffer. See also DataInput parameter.

Note

Depending on ST1_PACK_Value, several object numbers and even index numbers are 'hidden' in the message. They are easy to overlook when assigning the expanded addressing.

Name: Enabled Declaration: INPUT Data type: BOOL Default: TRUE Explanation Enables block processing.


Range of values:




Name: ImageMemory Declaration: INPUT Data type: BOOL Default: TRUE Explanation Image memory principle.




Range of values:

Bit memory Data bit

M 0.0 ... M n.7 L 0.0 ... L n.7 DBm.DBX 0.0 ... n.7


Name: Conditional Declaration: INPUT Data type: BOOL Default: TRUE Explanation Conditional spontaneous data transmission


Range of values:

Bit memory Data bit

M 0.0 ... M n.7 L 0.0 ... L n.7 DBm.DBX 0.0 ... n.7


Name: Unconditional Declaration: INPUT Data type: BOOL Default: FALSE Explanation Unconditional spontaneous data transmission.


Range of values:

Bit memory Data bit

M 0.0 ... M n.7 L 0.0 ... L n.7 DBm.DBX 0.0 ... n.7







Name: TimeStamp Declaration: INPUT Data type: BOOL Default: FALSE Explanation Time stamp. Range of



Name: ReverseDirection Declaration: INPUT Data type: BOOL Default: FALSE Explanation Transmission in the reverse direction. Range of





Name: SendOnChange Declaration: INPUT Data type: BOOL Default: FALSE Explanation Send on change. Range of


Here, you specify whether the FB checks for changes within the acquired data area (to determine whether at least one bit has changed). If a change is then detected, a transmission of the entire data area is triggered automatically. If no parameter is specified, the default is FALSE; in other words, there is no change-driven data transmission. Transmission must then be triggered by the user at the TriggerInput input parameter.

Name: TriggerInput Declaration: INPUT Data type: BOOL Default: FALSE Explanation Trigger input.

No parameter specified: Default value FALSE is valid Range of values: Input

Bit memory Data bit




If required, this parameter can be used to specify an input over which the user can trigger the transmission *) of the data message at any time (signal edge from 0 to 1). Example: Time-driven analog value transmission with time stamp for supplying an analog value archive in the control center. Note: To prevent these messages with time stamps from being overwritten when saving on the station TIM, the ImageMemory parameter must be set to FALSE. FC Trigger can be used for time-driven triggering of a transmission over TriggerInput (for more detailed information, refer to the description of this block). If you do not require the parameter, simply leave it open. You should, however, then set the SendOnChange parameter to TRUE so that the data is transmitted automatically at every change. *) TriggerInput actually only triggers transmission indirectly. With a 0/1 edge at TriggerInput, the message is put together with its current values and transferred to the local TIM. The TIM is responsible for the actual transmission to the partner. Transmission is immediate over a dedicated line or wireless link; with a dial-up connection, it is possible that the message is saved first on the TIM and sent at a later point in time (for example, because the message is marked as a "conditional spontaneous" message; see the Conditional parameter).

Note The following applies both to change-driven and transmission and transmission triggered over TriggerInput: All data words of the area defined with DataInput are always transmitted.

Note

You can also select a combination of SendOnChange plus TriggerInput. This means that a transmission is triggered both when a change is detected and at every signal edge change from 0 to 1 at the TriggerInput.

Note

If you use neither SendOnChange nor TriggerInput to trigger data transmission, the data will only be transmitted when there is a single request for this data object or within the framework of a general request.

Name: DataInput Declaration: INPUT Data type: ANY Default: P#P 0.0 VOID 0 (null pointer) Explanation Data input area.



Range of values:

P#DBxx.DBX yy.0 WORD zz xx : Data block number 1...32767 yy : Byte number zz : Number of words 1...26 starting at byte number yy Example: P#DB20.DBX 100.0 WORD 8 Remember the periods and spaces when entering the pointer! No parameter specified: Default (null pointer) is valid. This is, however, not permitted! A pointer >< null pointer must be specified.

The ANY pointer describes the data area in which the data to be acquired is located. This data area must be within a data block and its length can vary between 1 and 26 data words. If the parameter setting is incorrect (null pointer, length greater than 26, data area not a data block, length does not match ST1_PACK_Value), an error message to this effect is entered in the diagnostics buffer (event ID B114, [Info2/3] = 14). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.

Note Please remember the maximum DataInput lengths specified with the ST1_PACK_Value parameter permitted as a result of the PACK value. Make sure that a multiple of the PACK value matches the data area specified with DataInput. An interval of 2 words, for example does not match a data area to be transferred with the length of 15 words. This would have to be either 14 or 16 words.

3.5.26 ST1 data typical FB ETKOP26W

Function Receive a maximum of 26 words with any data content from a message with ST1 format. With certain restrictions, the block can be used as a substitute for evaluating SINAUT ST1 messages with any data combination (keyword: custom message composition. The evaluation of these messages is possible in ST1 with the aid of the function blocks ETKOP, ETEND and element blocks). The block is useful when a custom compiled message is sent from an ST1 station and must be received and evaluated by an S7 CPU. The element blocks available in ST1 for evaluating and processing data received with the message, and the finalization block ETEND, do not exist in ST7. The function of ETEND is contained in FB ETKOP26W. The user program is responsible for the evaluation and processing of the received data.



Object-oriented data transmission with SINAUT LSX The ETKOP26W function block is particularly useful when object-oriented data needs to be received from the SINAUT LSX control center system. Although this can also be done with the function blocks BTA and STA, when several different data types or even command bytes or setpoints belong to one object, they can only be received with FB ETKOP26W. Example: A combined command/setpoint object consists of two data words, namely ● one word with 8 commands ● one word with 1 setpoint These two data words could not be received separately with an FB BTA and an FB STA. Although the two FBs could be assigned different ST1 index numbers, because both FBs must have the same ST1 object number, only the first block with this ST1 object number would be addressed when a message is received for this object. With ETKOP26W, this is no longer a problem. Both information words of the object are received by only one FB (ETKOP26W) and the ST1 object number is assigned only once (defined with the ST1_ObjectNo parameter). With ST1_IndexNo, the index number of the first data word in the object must be specified. The index numbers of the remaining data words are then obtained automatically as continuous numbers (always incremented by 1). If, in the example shown, the ST1 index number is specified as 6, this applies to the 1st data word with the commands. The 2nd data word with the setpoint then has ST1 index number 7. Data for only 1 ST1 object can be received with ETKOP26W.



values: 1 ... 254 or 1 ... 8 or 0 (if ReverseDirection = TRUE and there is more than one partner)



The subscriber number of the partner with which the FB communicates, i.e. from which the FB receives data, must be specified. With an operator typical such as ETKOP26, this is normally the subscriber number of an ST1 station. If ETKOP26 is used in the reversethe transmission direction (see ReverseDirection parameter), the subscriber number of the ST1 master station must be specified. Partner is the ST1 station: Range of values limited to 1 ... 254 (= ST1 station number) Partner is the ST1 master: Range of values limited to 1 ... 8 (= ST1 master number) Partner is ST7/ST7cc: Range of values limited to 1 ... 254 (= SINAUT ST7 subscriber number) Point to note when PartnerNo = 0: The 0 is permitted only when ETKOP26 is used in the reverse transmission direction; in other words, in a station (ReverseDirection = TRUE). Enter 0 for the parameter when the typical can receive data from more than one partner, for example, when there are several control centers wanting to send data to the typical configured here. Checking the PartnerNo parameter: If the parameter setting is incorrect (< 1 or > 254 or > 8), an error message to this effect is entered in the diagnostic buffer (event ID B100, see diagnostic messages). This error message is also entered if PartnerNo = 0 and ReverseDirection = FALSE. If the value range is correct, but the PartnerNo was not found in the administration (in DB-BasicData), an entry is also made in the diagnostic buffer (event ID B101, see diagnostic messages). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected. If the PLC receives a message for the object set here and ReverseDirection = FALSE, the system checks whether the source subscriber number in the message is identical to the PartnerNo set here. If they are different, the received information is discarded. An error message to this effect is entered in the diagnostic buffer (event ID B130, see diagnostic messages).


values: 2 ... 250






values: 0 or 1 ... 255



values: 0 ... 255


Name: Enabled Declaration: INPUT Data type BOOL Default: TRUE



Explanation Enable block processing. TRUE or FALSE No parameter specified: Default TRUE is valid

Range of values:



Whether or not processing of the block is enabled must be specified. If processing is enabled, all the functions of the FB execute. If processing is not enabled, the FB can only communicate at the organizational level; in other words, ORG messages can be sent and received. A request can, for example, still be sent and the answer received, the received information is, however, not output to the area defined by DataOutput.




Name: DataInput Declaration: INPUT Data type ANY Default: P#P 0.0 VOID 0 (null pointer) Explanation Data output area.



Range of values:

P#DBxx.DBX yy.0 WORD zz xx : Data block number 1...32767 yy : Byte number zz : Number of words 1...26 starting at byte number yy Example: P#DB20.DBX 100.0 WORD 8 Remember the periods and spaces when entering the pointer! No parameter specified: Default (null pointer) is valid. This is, however, not permitted! A pointer >< null pointer must be specified.

The ANY pointer describes the data area in which the received data will be stored. This data area must be within a data block and its length can vary between 1 and 26 data words. FB ETKOP26W stores the received data without further processing in the data area defined by DataOutput. The user program is responsible for evaluating and processing received data. How to read out the time stamp received with the data is described in the section Notes on the SINAUT time stamp. If the parameter setting is incorrect (null pointer, length greater than 26, data area not a data block), an error message to this effect is entered in the diagnostics buffer (event ID B114, [Info2/3] = 7). The CPU does not change to STOP. The FB is then no longer processed, however, until the parameter assignment error has been corrected.




Whenever the FB has received new data and has stored it in the data area defined by DataOutput, the NewData output is set to TRUE for one OB1 cycle. The output is intended for user-specific further processing, for example to react in a specific way to receipt of new data. If you do not require the parameter, simply leave it open.

SINAUT TD7 software package for the CPU 3.6 Blocks for optional expansion


3.6 Blocks for optional expansion

3.6.1 FC ListGenerator300, FC ListGenerator400

Function The FC ListGenerator is required in a CPU that receives messages containing either an incomplete destination address or no destination address at all. The lack of the destination object number is the most important factor here because this points to the instance DB in which the received information should be stored. Missing or incomplete destination addresses can occur when no or incomplete parameters are set for them in the station (this is permitted for typicals that send binary information, analog values or counted values). If these typicals send data to more than one destination, no destination address is set for these typicals. Due to the missing destination information, the send message is automatically transmitted to all destinations for which a connection is configured. Such messages are therefore received without a destination address at the various destinations.

Note Messages without a destination address that are sent to the partner over a TIM have the destination subscriber number added by the sending TIM, and sometimes several addresses if there are several destinations along the way. The TIM enters 0 in the address field for the destination object number, since the TIM does not have the relevant information. The only destination subscribers it knows are those to which it has a configured connection. At the receiving end, the message therefore contains the destination subscriber number but the destination object number is 0.

If the destination object number is not contained in the received message, FC Distribute, which is responsible for distributing the received messages, references an object reference list. Using the source address (source subscriber no. + source object no.) contained in every message, FC Distribute searches through the list for an entry that specifies the missing destination object number for the given source address; in other words, it searches for the number of the local instance DB. This object reference list is created by FC ListGenerator. The FC has no parameters. It must be included in the cyclic SINAUT program (in OB1) following FC BasicTask.

Note There is an FC ListGenerator version for S7-300 (symbolic name, ListGenerator300) and for S7-400 (symbolic name ListGenerator400).

When creating the list, FC ListGenerator uses the addresses set in the parameters for the typicals that receive data. The parameters PartnerNo and PartnerObjectNo are mandatory for these typicals. These parameters are identical with the source address in the corresponding received message. Since the typical also knows the number of its instance DB, it therefore knows all the addresses required for an entry in the reference list. During startup, FC ListGenerator makes a request to all typicals that can receive data to enter their configured addresses with the number of the instance DB in the reference list. The object



reference list therefore does not require special parameter settings, it is simply created from the existing parameters of the receive typicals and is therefore always consistent.

Special feature with ST1 messages FC ListGenerator must always be used in a CPU that sends or receives ST1 messages. Because ST1 messages use a different addressing scheme, FC Distribute can only locate the corresponding instance DB in the CPU for received ST1 messages by using the object reference list. Two separate lists are created in a station when it is connected to ST1: A ’normal’ list for distributing received data messages (commands and setpoints) and a second list for forwarding received organizational messages to the appropriate instance DB. These organizational messages are message-specific functions for a single request for an ST1 message (binary information, analog value or counted value message) as well as the organizational command ’Enable/disable message’. The second reference list therefore contains the addresses in the ST1 send typical parameters and no those of the receive typicals. Along with PartnerNo, the ST1-specific addresses ST1_MessageNo and ST1_ObjectNo are stored in the object reference list for ST1 messages. References for ST7 and ST1 can be entered in the list in a control center that receives both ST7 and ST1 messages.

How it works FC ListGenerator creates the list(s) after startup in three consecutive OB1 cycles: 1. In the first cycle, it determines how many entries will be required in the first and, if

applicable, in the second object reference list. The typicals involved only increment a counter during this run.

2. In the second cycle, FC ListGenerator generates the data block for the first and, if applicable, the second object reference list with the required length and enters 0 in all the data words. During the same cycle, each typical involved enters its addresses and the number of the corresponding instance DB in the list.

3. In the third and final cycle, FC ListGenerator sorts all the entries in ascending order. Sorting speeds up the search in the list during actual operation.

When generating the data block, FC ListGenerator does the following: If a list has not yet been created, it first searches for a free DB number; the first free DB number below the number for DB BasicData (when two lists are created for ST1, it searches for two consecutive numbers in descending order). If a list already exists, FC ListGenerator checks to see if its present length is adequate for the currently required number of references. If the length is adequate, 0 is entered as the content and the addresses are written again and sorted. If the existing data block is too short, different procedures are used for S7-300 and S7-400: ● For S7-300, a new DB is generated. The old DB remains in memory because S7- 300

has no delete function for data blocks. This DB must be deleted by the user with the programming device. If there is not enough memory on the CPU to be able to generate a new DB, the existing DB must be deleted by the user before restarting.

● In an S7-400, the existing DB is deleted and a new DB is generated with the same number and the new length.



3.6.2 FC TimeTask

Function FC TimeTask is responsible for continuous date and time management on a CPU. The FC has no parameters. It must be included in the cyclic SINAUT program (in OB1) following FC BasicTask. FC TimeTask requires that the CPU is synchronized by a local TIM. This synchronization must be enabled in the ’Time Services’ tab in the Properties dialog for the corresponding TIM. See figure below.

Figure 3-27 TIM parameter assignment tabs - setting the synchronization on the MPI / party line

For more detailed information on setting the synchronization, refer to the chapter "Configuration software for SINAUT ST7" in this manual, section ’Parameter assignment for TIM modules'. After the CPU has started up, the TIM supplies the current date/time for the first time in an organizational message. Following this, the synchronization continues at the time interval specified by the configuration of the TIM (a one minute time scheme is recommended for synchronization on MPI/party line). FC TimeTask sets the CPU clock to the synchronized time received from the TIM and reads this clock in every OB1 cycle. As long as it continues to advance and remains plausible, the read time is entered in the first two double words of DB BasicData and is marked as valid or invalid and as daylight-saving or standard time. All blocks take the current time from there as they need it. For example, data point typicals do this to time stamp their messages, as does



FC Trigger to check whether a point in time configured for the FC has been reached or a specified time period has elapsed. This time is, of course, also available to the user program.

Figure 3-28 DB BasicData, CurrentDate and CurrentTime

Table 3-12 The exact assignment of the data words with data, time of day and time status:

Data byte 0 Year * 10 Year * 1 Data byte 1 Month * 10 Month * 1 Data byte 2 Day * 10 Day * 1

CurrentDate

Data byte 3 Hour * 10 Hour * 1 Data byte 4 Minute * 10 Minute * 1 Data byte 5 Second * 10 Second * 1 Data byte 6 Millisecond * 100 Millisecond * 10

CurrentTime

Data byte 7 Millisecond * 1 Time status

Table 3-13 Assignment of the 4 time status bits:

20 0 = Date/time invalid 1 = Date/time valid

21 0 = Standard time 1 = Daylight saving time

22 (not used) 23 (not used)

In addition to using the time status, data bit 16.1 CpuClockOk also indicates whether the date/time is valid. Once the time of day is valid on the CPU, this bit is set to 1 by FC TimeTask. In the user program this bit can be directly queried using its symbolic name "BasicData".CpuClockOk.



3.6.3 FC Trigger

Function This function block sets an output (memory bit, data bit or digital output) at a point in time or at time intervals specified by the user. The block resets this output after one OB1 cycle. The FC can be called from any point and also several times in the cyclic SINAUT program (in OB1). When an individual program section or software function is to be triggered using FC Trigger, it is advisable to call it directly before the block that, for example, will be executed conditionally due to the memory bit set by FC Trigger, or will execute a certain function triggered by the memory bit (e.g. triggering a counted value transmission every 2 hours). If you want to activate several (software) functions at the same time, this can be done with one FC Trigger: All query the same memory bit set by FC Trigger. However, this only works without problems when the triggered blocks do not reset this memory bit themselves. To avoid the problem of triggered blocks resetting the memory bit: ● Insert a suitable number of Trigger FCs, each with the same time but with a different

output memory bit, or ● Set a suitable number of additional memory bits after FC Trigger has set its output

memory bit. The FC accesses the SINAUT time in the first two data double words in DB BasicData. These are continuously updated if an FC TimeTask is included in the SINAUT program and this is synchronized with the date and time of day by a local TIM at regular intervals. FC Trigger only compares its time parameters with the current time of day if the SINAUT time is marked as O.K. (for a valid time of day bit 0 is set in DB BasicData in data byte 7, the time status byte). The precision with which FC Trigger operates depends, on the one hand, on the exactness of the SINAUT time and, on the other, on the OB1 cycle time. If the OB1 cycle time is less than 1 s (this is usually the case), the output is set exactly to the set second value (with the inaccuracy of the OB1 cycle time of less than 1 sec.). If the OB1 cycle time is greater than 1 s, the FC works with a tolerance window of 4 s; in other words, if the FC is processed late but still within 4 s of the configured time or time interval, the output is still set. The edge memory bit (Flag parameter) to be set for the FC is also set with the output and reset 5 s after the specified point in time or time interval. It is not allowed to use a dummy parameter for the edge memory bit or to reset it with the user program! Following the descriptions of the parameters below, you will find several examples that explain how to set parameters for points in time or time intervals using FC Trigger.


Name: IntervalMode Declaration: INPUT Data type BOOL



Explanation An interval is set for the FC. Range of values: TRUE or FALSE FALSE = no, in other words, a time is set. TRUE = Yes, in other words, an interval is set. You will find examples of setting a point in time or a time interval following the description of the parameters.

Name: Hour_Minute Declaration: INPUT Data type WORD Explanation Specifies the values for hours and minutes.

Further explanation: Refer to Month_Year parameter below.

Name: Second_Day Declaration: INPUT Data type WORD Explanation Specifies the values for seconds and day.

Further explanation: Refer to Month_Year parameter below.

Name: Month_Year Declaration: INPUT Data type WORD Explanation Specifies the values for month and year.

Range of values: 00 ... 99, or FF Each parameter has two parts, each of the two values per parameter is specified with two digits as a BCD coded value. The first two digits contain the values for hours, seconds or month; the two remaining digits specify the minutes, day or year. Enter FF for parameters you do not require. The parameters allowed depend on the particular parameter and the IntervalMode parameter. For more information, refer to examples following the descriptions of these parameters.

Name: TriggerOutput Declaration: OUTPUT Data type BOOL Explanation Trigger output.



Range of values:


Q 0.0 ... I n.7 M 0.0 ... M n.7 L 0.0 ... L n.7 DBm.DBX 0.0 ... n.7

The output is set for the duration of one OB1 cycle when the point in time or time interval specified by Hour ... Year is reached.

Name: Flag Declaration: IN_OUT Data type BOOL Explanation Edge memory bit for TriggerOutput. Range of

values: Bit memory Data bit

M 0.0 ... M n.7 DBm.DBX 0.0 ... n.7

No dummy memory bit is permitted. The edge memory bit must also not be reset by the user program.

Note This is an in/out parameter (declaration IN_OUT). It is difficult to specify local bit memory with this parameter and this should not be used.

Examples of setting a time or time interval IntervalMode = FALSE (or 0) The FC works with a point in time. When the set point in time is reached, TriggerOutput is set for one OB1 cycle. All time parameters can be used to specify the time. If you do not require a parameter, set FF. When checking whether a time has been reached, these are ignored. This can be used in some areas (although IntervalMode = 0) for setting a time scheme. Refer to the following examples. Permitted ranges for the time parameters:

Hours 00-23 Day 01-31 Minutes 00-59 Month 01-12 Seconds 00-59 Year 00-99

Examples: 1. IntervalMode: FALSE The TriggerOutput output is set once

Hour_Minute : W#16#0645 at 06:45:12 on 04.02.91. Second_Day : W#16#1204 Month_Year : W#16#0291

2. IntervalMode: FALSE The TriggerOutput output is set every Hour_Minute : W#16#0600 day at 06:00:00. Second_Day : W#16#00FF Month_Year : W#16#FFFF



3. IntervalMode: FALSE The TriggerOutput output is set on every Hour_Minute : W#16#0600 1st of a month at 06:00:00 Second_Day : W#16#0001. Month_Year : W#16#FFFF

4. IntervalMode: FALSE The TriggerOutput output is set every Hour_Minute : W#16#0600 year on October 1st Second_Day : W#16#0001 at 06:00:00. Month_Year : W#16#10FF IntervalMode = TRUE (or 1)

The FC works on the time interval principle. When the set point in time value is reached, TriggerOutput is set for one OB1 cycle. Only the entries for hours, minutes and seconds are relevant. The date parameters are ignored. A time interval can only be set in hours or minutes or seconds. If you do not require a time parameter, set FF. The following time intervals are permitted: Hours: 01, 02, 03, 04, 06, 08, 12, 24. Minutes : 01, 02, 03, 04, 05, 06, 10, 12, 15, 20, 30, 60. Seconds : 10, 12, 15, 20, 30, 60. Examples: 1. IntervalMode: TRUE Every 6 hours the output

Hour_Minute : W#16#06FF TriggerOutput is set at: Second_Day : W#16#FFFF 00:00:00, 06:00:00, 12:00:00 and Month_Year : W#16#FFFF 18:00:00.

2. IntervalMode: TRUE Every 30 minutes the output Hour_Minute : W#16#FF30 TriggerOutput is set at: Second_Day : W#16#FFFF 00:00:00, 00:30:00, 01:00:00, Month_Year : W#16#FFFF 01:30:00, 02:00:00, 02:30:00 etc.

Error message during startup The FC checks the parameters Hour_Minute, Second_Day and Month_Year every cycle to make sure that the permitted range of values is kept to. What is permitted depends to some extent on the IntervalMode parameter. If the parameter setting is incorrect, an error message to this effect is entered in the diagnostic buffer only during startup (event ID B113). The CPU does not change to STOP. The FC then checks only the parameters (without an error message) until the parameter assignment error is cleared. The diagnostic message provides an exact description of the bad parameter (consecutive number of the parameter, i.e. 2, 3 or 4). Depending on the parameter IntervalMode, the diagnostics message may be caused by the following situation: IntervalMode = FALSE (or 0) The range permitted for the parameters hours, minutes, seconds, day, month, year has been violated. Apart from FF, the following settings are valid:

Hours 00-23 Day 01-31 Minutes 00-59 Month 01-12 Seconds 00-59 Year 00-99



IntervalMode = TRUE (or 1) In this case, there are two possible causes for an error: 1. The range permitted for the parameters hours, minutes, and seconds was violated. Apart

from FF, the following settings are valid: Hours : 01, 02, 03, 04, 06, 08, 12, 24. Minutes : 01, 02, 03, 04, 05, 06, 10, 12, 15, 20, 30, 60. Seconds : 10, 12, 15, 20, 30, 60.

2. A time interval can only be set in hours or minutes or seconds. The two unused parameters must be specified as FF. An error also occurs when all three parameters are set to FF.

3.6.4 FC PulseCounter

Function The FC PulseCounter is responsible for counted pulse acquisition. A maximum of 8 pulse trains are acquired over digital inputs and using SIMATIC counters passed to the function blocks which create the counted value messages (Cnt01D_S, Cnt04D_S and ZTZ01, ZTZ02, ZTZ03). The acquisition of the counted pulses is time-driven. To this purpose, the FC PulseCounter is included in a cyclic interrupt OB, for example, OB35. The call interval for the cyclic interrupt OB must be matched to the pulse duration of the counted pulses. For more information on the cyclic interrupt OB, refer to the section ’Time-driven SINAUT program in a cyclic interrupt OB’.


Name: InByte Declaration: INPUT Data type BYTE Explanation Input byte for counted pulses. Range of

values: Input bytes Memory bytes Data bytes

PIB0 ... PIBn MB0 ... MBn LB0 ... LBn DBm.DBB0 ... n

The inputs for counted pulse acquisition can be set byte by byte.

Note If an input byte of a digital input is specified, it must be the address of the I/O byte (PIB) direct from the digital input modules. The current status of the counted value input can only be reliably acquired by direct access. Counted pulses may go undetected when read from the process image of the inputs (IB).



Name: EnableMask Declaration: INPUT Data type BYTE Explanation Enable mask for the counted value inputs. Range of

values: B#16#00 to B#16#FF

EnableInMask provides a bit mask for specifying the inputs in the input byte to which counted pulses are actually connected. The following applies to each bit in the bit mask: 0 = Input bit for acquisition disabled 1 = Input bit for acquisition enabled

Note The mask can only be edited in hexadecimal format B#16#00 to B#16#FF. Entry as 8-bit binary numbers from 2#0 to 2#1111 1111 is not possible for the data type BYTE.

The assignment of the bits in the mask to the inputs in the InByte input byte:

InByte .7 .6 .5 .4 .3 .2 .1 .0 EnableMask B#16# 0 … F 0 … F

Example:

EnableInMask : B#16#83 The following are enabled: Inputs .7, .1 and .0 The following are disabled: Inputs .6 to .2

Name: CntIn_0 ... CntIn_7 Declaration: INPUT Data type COUNTER Explanation Pulse counter Range of

values: C0 or C1 ... Cn (n is CPU-dependent)



For each enabled counted value input, a SIMATIC counter must be specified with the corresponding parameter CntIn_0 ... CntIn_7. The SIMATIC counter is incremented with each acquired pulse. The counters configured here must be specified for the actual counted value function blocks, Cnt01D_S, Cnt04D_S and ZTZ01, ZTZ02, ZTZ03 as input counters (parameter Counter_1 ... _4). These function blocks read out the assigned counter and then reset it. Counter C0 is recommended as a placeholder for parameters that are not required. Example of the setting for CntIn_0 ... CntIn_7 based on EnableInMask : = B#16#83 CntIn_0 : = C10 CntIn_1 : = C11 CntIn_2 : = C0 CntIn_3 : = C0 CntIn_4 : = C0 CntIn_5 : = C0 CntIn_6 : = C0 CntIn_7 : = C12

3.6.5 FC Safe

Function The block ensures reliable entry of commands and setpoints. When an entry is pending, the FC checks to determine whether only one entry is waiting in the current OB1 cycle and then enables the reading block. FC Safe should be called in the cyclic SINAUT program (in OB1) in every CPU in which commands and/or setpoints are acquired once at the end of all command and setpoint FBs. For more detailed information on the program structure, see the section ’The cyclic OB1 program for a control center’. The FC has separate monitoring functions for commands and setpoints entered by the hardware (input modules) or those entered by software (operator panel (OP) etc.). These two entry methods can be used at the same time. The FC then enables input from the hardware or software 'track' separately, and when necessary even simultaneously. As a basic rule, however, only one command or setpoint input may be detected per ’track’. For hardware input there is an additional condition: The input must remain constant for specific period of time. This delay time is set for FC Safe with the InputDelayTime parameter. The input is released after the delay time has elapsed only if the currently entered command or setpoint remains unchanged for the specified delay time and no other command or setpoint input is detected during this time. The actual creation of the command or setpoint message is handled by the block that read in the command or setpoint. FC Safe provides two other code bits for hardware input:



InputOK : Has signal 1 as soon as the current entry is enabled. The code bit goes off when the entry is reset, i.e. as soon as the command key is released or, for setpoint input, as soon as the key at the EnterInput input is released.

InputError : Has signal 1 as soon as an input error within the hardware ’track’ is detected. Either two or more simultaneous command or setpoint entries have been detected or at one of the inputs the 1 signal was detected over a long period if time, i.e. the input is ’stuck’. This long monitoring time can be configured for FC Safe with the MaxInputTime parameter.

FC Safe indicates a command output error recognized in a station using the GlobalCmdOutputError output. A command output error can only occur at the receiving end either when the content of both command bytes in the received message is not identical or when more than one bit is set in the command byte. When such an error is detected, the station reports this back with an organizational message to the subscriber that sent the command message. FC Safe on this subscriber then indicates the error at the GlobalCmdOutputError output. This is a group display. When an error is detected the output remains set to signal 1 until the user resets the group signal at the ResetError input.


Name: InputDelayTime Declaration: INPUT Data type INT Explanation Delay time in milliseconds for commands and setpoints entered by

hardware. Range of values: 0 or 1 ... 32000 [ms] A delay time of at least 1000 ms is recommended. 0 can be entered if the parameter is not required. For more detailed information on this parameter, refer to the section Function.

Name: MaxInputTime Declaration: INPUT Data type INT Explanation Monitoring time in seconds for commands and setpoints entered by

hardware. Range of values: 0 or 1 ... 32000 [s] A monitoring time of at least 30 s is recommended. 0 can be entered if the parameter is not required. For more detailed information on this parameter, refer to the section Function.



Name: ResetError Declaration: INPUT Data type BOOL Explanation Input for resetting the GlobalCmdOutputError output. Range of



If the parameter is not required, specify a memory bit or data bit that always has signal 0. For more detailed information on this parameter, refer to the section Function.

Name: InputOK Declaration: OUTPUT Data type BOOL Explanation Hardware command or setpoint entry has been executed correctly. Range of



If the parameter is not required, specify a memory bit or data bit that can be used as a scratchpad memory. For more detailed information on this parameter, refer to the section Function.

Name: InputError Declaration: OUTPUT Data type BOOL Explanation An error has occurred related to the hardware command or setpoint input. Range of






Name: GlobalCmdOutputError Declaration: OUTPUT Data type BOOL Explanation Group message: A command output error has been detected in a station. Range of




3.6.6 FC PartnerStatus

Function The FC PartnerStatus can show the current status ’disrupted’ or ’OK’ for a maximum of 8 SINAUT subscribers. The FC can be called at any point in the cyclic SINAUT program (in OB1). If you want to monitor the status of more than 8 subscribers, an appropriate number of PartnerStatus FCs must be included in the SINAUT program. A SINAUT subscriber (partner) can be an ST7 CPU, an ST7cc or an ST1 device to which a connection was configured, or a local TIM. One bit per subscriber is reserved in the PartnerStatus output byte to indicate the status of the respective subscriber: FALSE (or 0): Subscriber is disrupted (or the corresponding input parameter is not being used, i.e. configured as 0, or subscriber is unknown). TRUE (or 1): Subscriber OK


Name: Partner1 ... Partner8 Declaration: INPUT Data type INT Explanation SINAUT subscriber number of the subscriber to be monitored

Range of values:

0 or 1 ... 32000

0 = Dummy value for unrequired parameter 1 ... 32000 = Number of the subscriber to be monitored



If a set subscriber number not found in the administration (in DB-BasicData), an entry to this effect is made in the diagnostic buffer only during startup (event ID B101). The CPU does not change to STOP. The status of a correctly configured subscriber is indicated in the PartnerStatus output byte; unknown subscribers are not processed until the parameter error has been corrected. Their status bits are set to 0.

Name: PartnerStatus Declaration: OUTPUT Data type BYTE Explanation Output byte for indicating the status of a subscriber to be monitored. Range of

values: Output bytes Memory bytes Data bit bytes

QB0 ... QBn PQB0 ... PQBn MB0 ... MBn LB0 ... LBn DBm.DBB0 ... n

The assignment of the status bits in the PartnerStatus output byte in relation to the parameters Partner1 ... Partner8:

.7 .6 .5 .4 .3 .2 .1 .0 Partner X 8 7 6 5 4 3 2 1 Status:

0 = subscriber Partner X disrupted or parameters not set or unknown 1 = subscribe Partner X OK.

3.6.7 FC PartnerMonitor

Function FC PartnerMonitor displays important status information about a SINAUT subscriber (see PartnerStatus parameter). The FC can also be used to trigger a general request to the subscriber and to establish and disconnect a permanent connection to the subscriber. The FC can be called at any point in the cyclic SINAUT program (in OB1). If you want to monitor and control more than one subscriber, include an appropriate number of PartnerMonitor FCs in the SINAUT program. A SINAUT subscriber (partner) can only be an ST7 CPU, an ST7cc or an ST1 device to which a connection was configured. TIMs cannot be monitored or controlled by FC PartnerMonitor.

Note FC PartnerMonitor can also be used in a station. However, the control inputs for establishing and terminating a permanent connection can then no longer be used. This only works in the control center, i.e. when the local TIM is a master TIM.




Name: PartnerNo Declaration: INPUT Data type INT Explanation SINAUT subscriber number of the subscriber to be monitored and controlled.

Range of values:

1 ... 32000 [ms]

If the set PartnerNo is not found in the administration (in DB-BasicData), an entry to this effect is made in the diagnostic buffer only during startup (event ID B101). The CPU does not change to STOP. The status of a correctly configured subscriber is indicated in the PartnerStatus output word and the control inputs are processed. Unknown subscribers are not processed until the parameter assignment error has been corrected. The PartnerStatus output word remains set to 0 during this time.

Name: MaxConnectTime Declaration: INPUT Data type INT Explanation Maximum connection duration for a permanent connection.

Range of values:

0 (= no limit) or 1 ... 480 [minutes]

If the time specified here is greater than 0, it is activated at the start of a permanent connection (see PermanentCall_On parameter). If the time elapses before the permanent connection is reset, it is automatically disconnected. The time is retriggered as long as the signal 1 is present at the PermanentCall_On input. The time specified here applies to a permanent connection in a dial-up network as well as to a permanent connection (continuous polling) on a dedicated line.

Name: PartnerStatus Declaration: OUTPUT Data type WORD Explanation Output word to indicate the status of the subscriber to be monitored. Range of

values: Output words Memory words Data bit words


If you do not require the parameter, simply leave it open. The meaning of the status bits in the PartnerStatus output word:

Bit no. PartnerStatus .1

5 .14

.13

.12

.11

.10

.9 .8 .7 .6 .5 .4 .3 .2 .1 .0



Bit .0 Status of the subscriber:

0 0 = Subscriber disrupted 1 1 = Subscriber OK

Bit .1 Status of the redundant connection:

0 0 = Redundant connection is disrupted 1 1 = All connections OK.

Bit .3 .2 Status of the general request (GR):

0 0 0 = GR complete without error 0 1 1 = GR started 1 0 2 = GR start received

1 1 3 = GR finished with error (GR incomplete or cannot be executed, e.g. due to disrupted subscriber)

Bit .6 .5 .4 Status of the dial-up connection:

0 0 0 0 = No connection 0 0 1 1 = Outgoing call activated 0 1 0 2 = Incoming call established 0 1 1 3 = Outgoing call established 1 0 0 4 = Permanent connection registered 1 0 1 5 = Permanent connection established

1 1 0 6 = Permanent connection disconnected

Bit .7 Status of the dial-up connection: 0 0 = No dial-up connection check in background 1 1 = Dial-up connection check in background is activated

Bit .8 Status of continuous polling (on dedicated line):

0 0 = No continuous polling 1 1 = Continuous polling activated

Bit .9 Status of the WAN connection resources:

0 0 = Sufficient resources on partner *) 1 1 = Insufficient resources on partner

Bit .10 Time status:

0 0 = Date/time not available / not OK on partner *) 1 1 = Date/time OK on partner

*) Information not available for an ST1 partner or an ST7 partner communicating with ST1 protocol.



Bit .11 Time synchronization: 0 0 = The partner CPU received a plausible time during the last

synchronization or no synchronization time has been received since startup.

1 1 = The partner CPU has received an implausible synchronization time; the last valid time will continue to be used.

Note Bit 11 cannot be displayed in conjunction with TimeTask version ≤ 1.6 or when using the ST1 protocol.

Note

The following parameters, GeneralRequest, PermanentCall_On and PermanentCall_Off are in/out parameters (declaration IN_OUT). It is difficult to specify local bit memory with this parameter type and this should not be used.

Name: GeneralRequest Declaration: IN_OUT Data type BOOL Explanation Input for triggering a general request to the subscriber specified with

PartnerNo.

Range of


I 0.0 ... I n.7 M 0.0 ... M n.7 DBm.DBX 0.0 ... n.7

A general request to the subscriber is triggered with a 1 signal at this input if no request is active for this subscriber at this time. The input is then automatically reset by the FC. If a digital input is specified for the input (I 0.0 ... I n.7), the user is responsible for resetting the signal at the input. This must be done before ending the currently running general request otherwise another general request is triggered immediately.

Name: PermanentCall_On Declaration: IN_OUT Data type BOOL Explanation Input for triggering a permanent connection to the subscriber specified with

PartnerNo.



Range of values:


I 0.0 ... I n.7 M 0.0 ... M n.7 DBm.DBX 0.0 ... n.7

A permanent connection to the subscriber is triggered with a 1 signal at this input if there is currently no permanent connection to this subscriber. The input is then automatically reset by the FC. If a digital input is specified for the input (I 0.0 ... I n.7), the user is responsible for resetting the signal at the input. This should be done at the latest before terminating the existing permanent connection. A 1 signal at the input PermanentCall_On also activates the time specified with MaxConnectTime if it is greater than 0. Depending on whether the subscriber can be reached over a dial-up connection or a dedicated line, the command to establish the permanent connection is processed as follows and indicated at the PartnerStatus output: For a dial-up connection: A dial-up connection is established by the master TIM to the appropriate subscriber and, regardless of the data traffic, maintained until the terminate command is sent. The current status of the permanent connection is indicated in the PartnerStatus output word with the bits 4 ... 6 (see PartnerStatus parameter). For a dedicated line: In this case the master TIM operates in polling mode with the stations. A permanent connection is implemented in this case by ’continuous polling’ of the subscriber. This is actually an intermittent poll to the subscriber; in other words, the other subscribers on the dedicated line network are still polled but the preferred subscriber is polled again after every poll to a ’normal’ subscriber . The current status of the continuous polling is indicated by bit 8 in the PartnerStatus output word (see PartnerStatus parameter).

Note A permanent connection cannot be established from a station. This control input cannot therefore be used when FC PartnerMonitor is used in a station.

Name: PermanentCall_Off Declaration: IN_OUT Data type BOOL Explanation Input for triggering termination of an existing permanent connection to the

subscriber specified with PartnerNo.

Range of values:


I 0.0 ... I n.7 M 0.0 ... M n.7 DBm.DBX 0.0 ... n.7



A permanent connection to the subscriber is terminated with a 1 signal at

this input if there is currently a permanent connection to this subscriber. The input is then automatically reset by the FC. If a digital input is specified for the input (I 0.0 ... I n.7), the user is responsible for resetting the signal at the input. This should be done at the latest before establishing the permanent connection again. Depending on whether the subscriber can be reached over a dial-up connection or a dedicated line, the command to terminate the permanent connection is processed as follows and indicated at the PartnerStatus output: For a dial-up connection: The existing dial-up connection is terminated by the master TIM but only after any pending data has been sent. The current status of the permanent connection is indicated in the PartnerStatus output word with the bits 4 ... 6 (see PartnerStatus parameter). For a dedicated line: The master TIM deletes the registration for continuous polling of the corresponding subscriber. The polling cycle for all connected subscribers continues in normal mode. The current status of the continuous polling is indicated by bit 8 in the PartnerStatus output word (see PartnerStatus parameter).

Note Continuous polling can also be canceled on a dedicated line by instructing the master TIM to start continuous polling of another subscriber. The existing job is then replaced by the new one.

Note

A permanent connection cannot be terminated by a station. This control input cannot therefore be used when FC PartnerMonitor is used in a station.

3.6.8 FC ST7ObjectTest

Function Calling FC ST7ObjectTest in the programming error OB121 prevents a CPU stop when the CPU receives a message with an unknown destination object number. FC ST7ObjectTest checks why OB121 is called, i.e. what type of block is missing. If the missing block is a data block and this data block is an instance DB of a SINAUT object, then the CPU will not change to STOP.



The parameter StopInOtherCases allows the user to specify the reaction if a block other than a SINAUT instance DB is missing: Stop or continue operation. For more detailed information on the programming error OB121 and background information on the use of FC ST7ObjectTest: Refer to the section 'SINAUT test routing in the programming error OB121'.


Name: StopInOtherCases Declaration: INPUT Data type BOOL Explanation CPU will change to STOP if other errors occur

Range of values:

TRUE or FALSE

This parameter allows you to specify what should occur in other error situations: Stop or continue operation when OB121 is called because another data block, an FB or an FC is missing.

3.6.9 FB SMS_Control

Function The SMS typical FB SMS_Control is used to send event-triggered SMS messages (SMS: Short Message Service) to a mobile phone set in the parameter assignment. The configured SMS texts as well as the telephone number of the mobile phone are contained in a DB SMS_Data that must exist on the CPU. This DB is generated using the SINAUT ST7 configuration tool (see chapter Configuration software for SINAUT ST7, section Parameters for Single Subscribers). The texts are assigned 1:1 to a contiguous bit array consisting of digital inputs, memory bits or data of a data block. The SMS typical operates internally with a job list. This contains all of the SMS jobs that were acquired due to a change in the bit array. The SMS jobs remain in the job list until they are completed (with or without error). They are then deleted from the job list. An SMS task is successfully completed when: ● An SMS has been successfully sent to the SMS control center (SMS-C) over a fixed

network connection and this in turn has successfully forwarded the SMS to the mobile phone.

● An SMS not requiring acknowledgement has been sent to the SMS-C over a direct GSM connection.

● An SMS requiring acknowledgement has been sent to the SMS-C over a direct GSM connection and acknowledged by the mobile phone.

An SMS task is ended with an error when: ● An internal monitoring time has expired without the SMS being sent to the SMS-C.



● The validity period of the SMS job in the SMS-C and CPU has expired without the SMS having been sent to the mobile phone by the SMS-C within this period or, when acknowledgement is required, without the SMS being acknowledged within this period.

If an SMS is ended with an error, a diagnostic message is entered in the diagnostic buffer of the CPU. The jobs remain in the job list of the SMS typical until they are completed correctly or ended with an error, or until the SMS typical is disabled (Enable = FALSE). If the SMS typical is disabled while there are still SMS jobs in the job list, an entry is made in the diagnostics buffer of the CPU for every incomplete SMS job.. A delete job is transferred to the TIM for all SMS jobs that are still active.

Note If a signal that triggers an SMS occurs more than once, the SMS is only repeated when the preceding SMS job has been completed.

Operation with two mobile phone numbers The SMS typical offers the option of working with a main and a substitute mobile phone. If access to the SMS-C is over an M20 GSM module, the two mobile phones may also belong to different networks. Once a selectable monitoring time has expired, all SMS messages that have been sent up until this time but not yet successfully completed are sent once again in the same order to the substitute mobile phone and the monitoring time is restarted. If the SMS typical is still unable to complete the SMS jobs over the substitute mobile phone within the allotted period, it switches back to the main mobile phone and sends the incomplete SMS messages once again, etc. Each SMS that is repeated is entered in the diagnostic buffer of the CPU at the time it is resent . As a counterpart to this, a success message is entered in the diagnostic buffer each time a repeated SMS is completed successfully. The switchover between the main and backup mobile phone is not made for each individual SMS; this always involves all SMS messages of a DB SMSData being processed. When there are no more SMS messages for processing in the SMS typical, the system automatically switches back to the main mobile phone number so that when the next event occurs that triggers an SMS, this is sent to the main mobile phone.

Note There is no switchover to a disrupted SMS-C. In this case, the SMS typical acts as if it has been configured for only one mobile phone number. Only one of the two mobile phone numbers is active at any given time; the other one remains passive.



Effect of the validity period The validity period for SMS tasks can be set using the SINAUT ST7 configuration tools (see Subscriber Administration, SMS Configuration tab, SMS DB Data dialog, Valid period parameter). The time for the validity period is started as soon as the SMS can be delivered to the SMS-C. Within the validity period the SMS-C continues to attempt to deliver any SMS sent to it to the mobile phone. The retry intervals, however, may be very irregular. When the validity period expires, the SMS messages in the SMS job list of the SMS typical are deleted and a diagnostic message is entered in the diagnostic buffer of the CPU. The SMS messages in the SMS-C are normally also deleted at this time. How exactly the validity period in the SMS-C is adhered to varies considerably from provider to provider.

Note If the SMS-C can only be reached over a fixed network connection, the validity period in the SMS-C is always approximately 48 hours. The "validity period" parameter has no effect in this case. The configured validity period is then only applicable for the CPU and can be set to 11 hours and 55 minutes at the maximum.

Retry mechanisms If the SMS job is passed from the CPU to the TIM, the TIM is responsible for the send retry when the SMS-C cannot be reached. If the TIM is able to deliver the SMS message to the SMS-C, the SMS-C takes over responsibility for automatic retries when the mobile phone cannot be reached immediately. If the SMS message has been sent to the SMS-C but this is unable to deliver it to the mobile phone, the typical (on expiry of the validity period) switches over to the backup mobile phone (if this has been set). The same retry mechanism is used for an SMS message requiring acknowledgement when this SMS can be delivered to the mobile phone but no acknowledgement is returned within the current validity period. Once again, the SMS typical also switches to the backup mobile phone if it is available. When a SMS cannot be delivered to the backup mobile phone, or, in the case of messages requiring acknowledgement, no acknowledgement is received, the system switches back and forth between the main and backup mobile phones. This continues until delivery is completed or an acknowledgement has been received, or until the SMS typical is disabled (ENABLE = FALSE)

Other functions In addition to sending and managing SMS messages, the SMS typical also processes two globally valid functions. They are global because their execution is valid for all SMS jobs connected with DB SMS_Data that is processed by the SMS typical. The two global functions are: ● Status request for all SMS jobs of DB SMS_Data being processed by the typical.

The typical sends the status request to the TIM responsible for the SMS transmission. This reports the current status of each SMS job in its memory back to the typical (status messages 2, 3 or 8). The TIM closes the sequence of status messages with status



message 11 which indicates that no more status information is available. This status request function executes only during the startup of the CPU and then only when the SMS typical is enabled at this time (ENABLE = TRUE).

● Deletion of all SMS tasks of DB SMS_Data being processed by the typical. Deletion takes place at several places: – On the CPU: All jobs stored in DB SMS_Data. – On the TIM: All jobs stored in the TIM for DB SMS_Data. – In SMS-C: All jobs stored in SMS-C for DB SMS_Data (only when the SMS-C can be

reached over a fixed network). ● The delete function is executed automatically by the typical in the following situations:

– When the instance DB belonging to the typical is initialized. – When DB SMS_Data to be processed by the typical is initialized. – When a status change is detected at the ENABLE input of the typical.

The status request and the deletion function are time monitored. The duration of the monitoring time is determined by the SupervisionTime (900 sec. by default) of the corresponding subscriber object in DB BasicData. If the supervision time expires before the status request or the deletion function can be completed correctly, a message is entered in the diagnostic buffer of the CPU and a group message "Supervision time has expired" is set at the Status output parameter of the SMS typical. As long as the status request or the delete function is active, processing of the SMS messages is postponed and it is not possible to trigger a new SMS. The current status of the status request or delete function is indicated at the Status output word of the SMS typical.


Name: MessageObjectDB Declaration: INPUT Data type BLOCK_DB Default - Explanation Monitoring time in seconds for commands and setpoints entered by

hardware. Here, you specify the DB SMS_Data to be processed by the typical.

Range of values: DB1 ... DBn (n depending on CPU type) DB SMS_Data contains all data and SMS texts to be processed in a group of message or alarm bits. This data block can be conveniently configured by the user with the SINAUT ST7 configuration tool and filled out with the required data and texts



Name: Enabled Declaration: INPUT Data type BOOL Default TRUE Explanation Enable block processing.


Range of values:



The user can enable and disable SMS processing with this input. For example, this input can be used to schedule timed enabling and disabling by a user program if the SMS messages should only be sent to standby personnel evenings, nights and/or at weekends. When processing is enabled, the SMS send functions of the typical are activated. If processing is disabled after being enabled, all undelivered, unacknowledged SMS jobs are then deleted. The typical enters the actual disabled status only after this has taken place. If you do not require the parameter, simply leave it open.

Name: Status Declaration: OUTPUT Data type WORD Default 0 Explanation The SMS typical can be monitored using the status bits in this word. Range of


QW0 ... Qwn PQW0 ... PQWn MW0 ... MWn LW0 ... LWn DBm.DBW0 ... n

If you do not require the parameter, simply leave it open. The meaning of the status bits in the Status output word:

Bit no. Status .15 .14 .13 .12 .11 .10 .9 .8 .7 .6 .5 .4 .3 .2 .1 .0

Bit.0 There are two mobile phones Bit.1 At least one SMS being processed Bit.2 At least one SMS not yet acknowledged



Bit.3 At least one SMS being repeated Bit.4 DB-specific delete job active Bit.5 DB-specific status request job active Bit.6 Backup mobile telephone activated Bit.7 Monitoring time expired Delete or status request job ended with error (details in

the diagnostic buffer). Bit.8 SMS processing activated Bit.9 SMS processing temporarily paused (for details see operating mode, bits 12...15) Bit.10 Not used Bit.11 Not used

Bit .15 .14 .13 .12 Operating mode: Status of current processing 0 0 0 0 0 = disabled 0 0 0 1 1 = enabled, processing ready/in progress 0 0 1 0 2 = blocked: global status request in progress 0 0 1 1 3 = blocked: global deletion of an SMS-C in progress 0 1 0 0 4 = blocked, initialization of the instance DB + DB SMS_Data in

progress 0 1 0 1 5 = blocked: global deletion of all SMS-C in progress .. .. .. .. 6-11 = not used 1 1 0 0 12 = blocked, global SMS-C switchover in progress 1 1 0 1 13 = blocked, current SMS-C disrupted or cannot be reached 1 1 1 0 14 = blocked, keyword at end of DB-SMS_Data incorrect

1 1 1 1 15 = not used

No SMS messages can be accepted for processing when: • DB-specific delete job active

• A DB specific status request is in progress e.g. when the CPU is being restarted

• The instance DB or DB SMS_Data is being initialized • There must be a reaction to changes at the Enable input • A switchover between the main and backup mobile phone is in progress

or, in general, the change of a mobile telephone number including a new SMS transfer.

• Access to the SMS-C or the SMS-C itself is disrupted • The keyword in DB SMS_Data cannot be found

The typical is then temporarily blocked and sets bit .9.



Name: ReloadMobilPhoneNo Declaration: IN_OUT Data type BOOL Explanation If the telephone number or one or both mobile phones needs to be changed

online, activation of the new telephone numbers can be triggered over this input.


Range of values:


I 0.0 ... I n.7 M 0.0 ... M n.7 DBm.DBX 0.0 ... n.7

After the user has changed the mobile phone numbers in DB SMS_Data, the input can be set and the new telephone number data activated online. Otherwise the typical always uses the telephone numbers stored in DB SMS_Data when the typical detects a signal change from FALSE to TRUE at the ENABLE input. If you do not require the parameter, simply leave it open.


3.6.10 DB SMS_Data

Function DB SMS_Data contains all data and SMS texts needed by the SMS typical FB SMS_Control to send and manage SMS messages. This data block can be conveniently configured by the user with the SINAUT ST7 configuration tool and filled out with the required data and texts Using the information contained in DB SMS_Data, the user can read the current status separately for each SMS message and determine when the most recent message was last transmitted as an incoming or outgoing message (when a time stamp is being used) and, if the messages require acknowledgment, when the most recent acknowledgement occurred.

Structure of DB SMS_Data The DB consists of a body with globally required information and one or more sections called SMS objects that contain the data required for each SMS message. The data of an SMS object are defined in UDT125 ShortMessageObject that is contained in the TD7 library. The global information in the body of the DB includes: ● The SINAUT subscriber number of the main SMS control center (main SMS-C) and

possibly a backup SMS control center.



● The telephone number of the main mobile phone and, if available, the telephone number of the backup mobile phone.

● The start address of the contiguous bit array (digital inputs, memory bits or data bits). If a bit in this field changes, the corresponding SMS message is sent.

Structure of an SMS object The structure of an SMS object is defined in UDT125 ShortMessageObject. A ShortMessageObject is included in DB SMS_Data for each bit in the defined bit array. The information stored here includes the following: ● The text of the SMS message to be sent ● When the most recent SMS was sent with an incoming or outgoing message ● The current typical-internal processing status of the SMS message ● The current processing status of the SMS message on the TIM / SMS-C, including the

time stamp of the most recent status message and ID number assigned by the TIM (TIM ID) that allows the diagnostic buffer entries to be referenced (on the TIM and CPU)

● Various entries required by the typical for organizing processing Each SMS object consists of a maximum of 82 data word (with a maximum of 122 characters of text). The structure is as follows:

Table 3-14 Structure of an SMS object in DB SMS_Data

Number of data words Short name Meaning Max. 62 SMS text SMS text string, max. 122 characters long 1 Year Month 1 Day Hours 1 Minute Second

Acquisition time stamp for the most recently sent incoming SMS

1 Year Month 1 Day Hours 1 Minute Second

Acquisition time stamp for the most recently sent outgoing SMS

1 CurrentMessageStatus Typical-internal SMS processing status (see description of CurrentMessageStatus)

1 Status incoming SMS

Status outgoing SMS

Most recent SMS status received by the CPU from the TIM or SMS-C (see description of the Status incoming SMS)

1 TIM ID for incoming SMS ID number for incoming SMS assigned by the TIM 1 TIM ID for outgoing SMS ID number for outgoing SMS assigned by the TIM 1 Year Month 1 Day Hours 1 Minute Second

Time stamp of the status message most recently transferred by the TIM to the CPU

1 LastControlMessage Most recent control instruction from the CPU to the TIM (without time stamp)

1 RemainingValidPeriodP Time remaining in validity period of the incoming SMS



Number of data words Short name Meaning 1 RemainingValidPeriodN Time remaining in validity period of the outgoing

SMS 1 SupervisionTime Time remaining in the supervision time until

incoming or outgoing SMS must be transfer to the SMS-C at the latest

1 PreviousMessageAddress Previous address (for chained job list) 1 NextMessageAddress Next address (for chained job list) 1 MessageNumber Message number of the SMS for identification and

diagnostics

CurrentMessageStatus The meaning of the status bits in CurrentMessageStatus:

Bit no. Status .15 .14 .13 .12 .11 .10 .9 .8 .7 .6 .5 .4 .3 .2 .1 .0

Bit .1 .0 Status of the SMS after incoming signal edge: 0 0 0 = Job complete without error 0 1 1 = TIM confirms: (incoming) SMS received 1 0 2 = SMS-C confirms: (incoming) SMS received 1 1 3 = Job ended with error

Bit .3 .2 Status of the SMS after outgoing signal edge (only relevant when SMS is sent on both an incoming and outgoing message):

0 0 0 = Job complete without error 0 1 1 = TIM confirms: (outgoing) SMS received 1 0 2 = SMS-C confirms: (outgoing) SMS received 1 1 3 = Job ended with error

Bit.4 Edge memory bit. SMS entered in the job list on signal edge change Bit.5 Incoming SMS: Job is being repeated Bit.6 Outgoing SMS: Job is being repeated Bit.7 No signal edge change processing as long as the SMS job is in progress (an

incoming or outgoing SMS message is not sent again when the previous, identical message has not yet been completed).

Bit.8 SMS is disabled Bit.9 Mandatory acknowledgment of SMS Bit.10 SMS waiting of acknowledgment Bit.11 SMS is prefixed with + / - for incoming or outgoing



Bit.12 Not used Bit.13 Not used Bit.14 Reserved Bit.15 Reserved

Status incoming / outgoing SMS The valid SMS processing status on the TIM is reported by the TIM to the CPU. SMS typical enters the return messages belonging to an incoming SMS message in the "Status incoming SMS" byte and those belonging to an outgoing SMS message in the "Status outgoing SMS" byte. Status 1 is an exception here. It is not reported by the TIM to the CPU but is created by the SMS typical itself and entered in the status byte for incoming or outgoing SMS. The following classifications are described below: Status Status information: is sent by the TIM to the CPU when there is a change in the status or following a status request. Pulse "Pulse" information: is sent once to the CPU due to an event on the TIM; it cannot be requested. Fixed network Status information valid for the fixed network access to the SMS-C over the analog telephone network or ISDN network. Mobile network Status information valid for the mobile network access to the SMS-C via an M20 module. The following status entries are possible: 1. Job monitoring time has expired, SMS could not be sent in time to the SMS-C.

Status, fixed network, mobile network 2. SMS not yet sent to SMS-C.

Status, fixed network Comes as a response to a status request; cannot be requested for a mobile network access.

3. SMS saved in SMS-C but not yet delivered to the mobile phone. Status, fixed network This status cannot be requested for a mobile network access.

4. SMS successfully delivered to the mobile phone. Pulse, fixed network Counts as a ’completed without error’ message.

5. SMS cannot be delivered to the mobile phone. Pulse, fixed network Counts as a ’ended with error’ message.

6. SMS successfully delivered to the SMS-C. Pulse / status, mobile network Pulse for messages not requiring acknowledgement. Counts then as a ’completed without



error’ message. Status for messages requiring acknowledgment. The TIM waits for an acknowledgment or a delete job. Does not count as a ’completed’ message.

7. SMS acknowledged by mobile phone. Pulse, mobile network Counts as a ’completed without error’ message.

8. SMS could not be sent in time to the SMS-C. Status, mobile network The TIM repeats the transmission until the SMS can be delivered or the SMS is deleted. Possible causes are: – "ERROR" message from M20 module – Monitoring time on the TIM has expired (the M20 module did not answer). – Disruption in the GSM network

9. SMS successfully deleted. Pulse, fixed network, mobile network Response of the TIM to a global delete job transferred by the CPU to the TIM. The TIM sends a separate status message 9 to the CPU for every SMS task deleted on the TIM. With a fixed network connection the SMS message is deleted in the SMS-C and in the administration of the TIM. With mobile network access it is not possible to delete the message in the SMS-C. It is only deleted in the TIM administration.

10. No entries to be deleted or all entries deleted. Pulse, fixed network, mobile network Response of the TIM to a global delete job transferred by the CPU to the TIM. In this case all entries for a DB SMS_Data are deleted or there are no entries for this DB SMS_Data.

11. No other entry is available or no entry exists at all. Pulse, fixed network, mobile network Response of the TIM to a global status request transferred by the CPU to the TIM. The TIM had previously transferred the current status of all remaining active entries to the CPU.

12. SMS could not be deleted in the SMS-C. Only the entry in the TIM records is deleted. Pulse, fixed network Response of the TIM to a specific delete job for an individual SMS. Delete job has was transferred from the CPU to the TIM. In this case a message in the SMS-C could not be deleted. The SMS in question probably no longer exists in the SMS-C or the SMS has already been delivered. Therefore only the corresponding entry in the TIM administration is deleted.

SINAUT TD7 software package for the CPU 3.7 Test blocks


3.7 Test blocks

3.7.1 FC TestCopy

Function Using FC TestCopy message traffic between SINAUT ST7 subscribers can be copied in part or whole. Individual message types can be specifically filtered using configurable search masks in the control field of the DB TestCopyData. These can then be copied from the send or receive buffers for further analysis in DB TestCopyData. All send and receive messages are stored in the same DB TestCopyData. The chronological order of the copied send and receive messages is then easy to recognize. The functions SendCopy (= log send messages) or RecvCopy (= log receive messages) can be individually activated or activated simultaneously but only one common operating mode (OM) is possible for both communication directions. The operating modes are set in data byte DBB0 of the DB TestCopyData, whereby the following assignments apply: ● DBB0, bits 0...3: Operating mode for RecvCopy function (operating mode 0, 1, 2 or 3) ● DBB0, bits 4..0.7: Operating mode for SendCopy function (operating mode 0, 1, 2 or 3) If an operating mode > 0 is set in the less significant half-byte, this always applies to both communication directions. The value in DBX 4...7 (SendCopy function only) applies only if OM = 0 in bit 0...3 (no RecvCopy function required). Exception: DBB0 must be written with FF to delete DB TestCopyData, 0F is insufficient! Examples: DBB0 = 00h; no TestCopy-function activated DBB0 = 03h; RecvCopy function only, mode 3, no SendCopy function required DBB0 = 30h; SendCopy function only, mode 3, no RecvCopy function required DBB0 = 33h; RecvCopy function and SendCopy function, mode 3, required DBB0 = 23h; RecvCopy function and SendCopy function required, mode = 3 DBB0 = FFh; Delete content of DB TestCopyData

Prerequisites The user program must meet the following conditions to use the TestCopy function: ● The FC TestCopy function must be present in the CPU; ● The DB TestCopyData in the CPU must be long enough. To ensure this, copy DB99

TestCopyData from the TD7 library to your CPU. Change the length of the buffer area as required by correspondingly increasing or decreasing the TestCopyBuffer area in the declaration header of the DB. This buffer area is preset as an array with a length of [0..240] WORDs.



● In the communication DB (type DB XComData, DB PComData or DB BComData) whose send and/or receive messages you wish to log, the following entries must be made (the best way is to use the predefined variable table VAT_TestCopy from the TD7 library): – The number of the DB TestCopyData must be entered in DW32 (symbolic name

TestCopyDBNo). – The number of the FC TestCopy must be entered in DW34 (symbolic name

TestCopyFCNo).

Including FC TestCopy in the user program The test function is executed cyclically by FB XCom, FB PCom or FB BCom if the number of the FC TestCopy is entered in DBW34 of the data block DB XComData, DB PComData or DB BComData to be monitored.

Operating mode and filter settings for FC TestCopy The user controls FC TestCopy using a VAT (VAriable Table, that is comparable to Force Variables in the S5 environment). This VAT has a predefined form and is available in the TD7 library as VAT_TestCopy. The following settings in DB TestCopy are possible using VAT_TestCopy:

Name Permitted values Meaning

00 h Function disabled. 11 h Message entry always at the beginning of DB

TestCopyData. 22 h Write DB TestCopyData endlessly as a circulating

buffer. 33 h Fill DB TestCopydata once, then set mode 0.

OperationMode

FF h Delete complete DB TestCopyData and preset defaults.FF h Copy all message types (MT = 0, 1, 2, 3) into DB

TestCopyData. 00 h Copy only ORG messages (MT = 0). 11 h Copy only requested ORG messages (MT = 1). 22 h Copy only data messages (MT = 2). 33 h Copy only requested data messages (MT = 3). 01 h Copy messages with MT = 0 or MT = 1. 23 h Copy messages with MT = 2 or MT = 3.

????_TgrmType

Any combination Copy any combination of 0, 1, 2, 3. All perm. sbscr. Filter the destination subscriber no. in message. ????_DestSubscr -1 Copy all messages regardless of the destination

subscriber no. All perm. obj. Filter the destination object no. in message. ????_DestObject -1 Copy all messages regardless of the destination object

no. All perm. sbscr. Filter the source subscriber no. in message. ????_SourceSubscr -1 Copy all messages regardless of the source subscriber

no.



Name Permitted values Meaning All perm. obj. Filter the source object no. in message. ????_SourceObject -1 Copy all messages regardless of the source object no. All perm. ind. Filter the start index no. in message. ????_StartIndex -1 Copy all messages regardless of the start index no.

FC TestCopy supplies a counted value in DBW12 of the DB TestCopyData indicating the number of message that has been received since the operating mode was set to 1, 2, or 3 and that matched the filter criteria; the number of sent messages is entered in DBW26. In DBB28, the user receives a return value that provides information about the errors that occurred during processing of the FC. Up to now, the following have been defined: RetVal = 0: No error RetVal = 1: The specified DB TestCopyData is too short RetVal = 10d: The operating mode entered in DBB0 is not defined

Notes on operation The content of the DB TestCopyData is not deleted when the operating mode is changed; only internal pointers and message counters in the management area of DB TestCopyData are reset. It is therefore advisable to use the delete function "FF" when changing the operating mode to initialize the message buffer area with 0. This makes it easier to read the copied message blocks. If you want to copy sent and received messages, the same operating mode must be entered in the left half-byte and the right half-byte of the OperationMode parameter. The following scheme applies:

Bit .7 .6 .5 .4 .3 .2 .1 .0 Mode for SendCopy Mode for RecvCopy

For modes 0, 1, 2 and 3: If you want to delete the buffer, FFh should always be entered; separate deletion of the receive and send messages is not possible.

3.7.2 DB TestCopyData

Structure of DB TestCopyData The following table shows the structure of the DB TestCopyData:



Address Name Format Explanation DBB 0 OperationMode BYTE Mode DBB 1 Recv_TgrmType BYTE Receive filter: Message type (MT) DBW 2 Recv_DestSubscr INT Receive filter: Destination

subscriber no. DBW 4 Recv_DestObject INT Receive filter: Destination object

no. DBW 6 Recv_SourceSubscriber INT Receive filter: Source subscriber

no. DBW 8 Recv_SourceObject INT Receive filter: Source object no. DBW 10 Recv_StartIndex INT Receive filter: Start index no. DBW 12 Recv_TgramCounter INT Number of copied received

messages DBB 14 SpareDBB14 BYTE Reserve DBB 15 Send_TgrmType BYTE Send filter: Message type (MT) DBW 16 Send_DestSubscr INT Send filter: Destination subscriber

no. DBW 18 Send_DestObject INT Send filter: Destination object no. DBW 20 Send_SourceSubscriber INT Send filter: Source subscriber no. DBW 22 Send_SourceObject INT Send filter: Source object no. DBW 24 Send_StartIndex INT Send filter: Start index no. DBW 26 Send_TgramCounter INT Number of copied sent messages DBB 28 RetVal BYTE Error information:

0 = No error 1 = DB TestCopyData too short 10 = Unknown operating mode

DBB 29 SpareDBB29 BYTE Reserve DBB 30 SpareDBB30 BYTE Reserve DBB 31 TestCopyStatus BYTE Status byte for Testcopy

operation DBB 32 TestCopyCmdByte BYTE Command byte for Testcopy

operation DBB 33 TestCopyDelCount BYTE Loop counter for TestCopy delete

function DBW 34 NextFreeCopyByte INT Address of the next free

TestCopyBuffer byte DBD 36 StartTimeSFC64 DINT SFC64 time at the start of the

copy procedure DBB 40 TestCopyBuffer[0] BYTE Copy area, byte 0 DBB 41 TestCopyBuffer[1] BYTE Copy area, byte 1 DBB 42 TestCopyBuffer[2] BYTE Copy area, byte 2 DBB 43 TestCopyBuffer[3] BYTE Copy area, byte 3 : : : : DBB xxxx TestCopyBuffer[xxxx] BYTE Copy area, byte xxxx



The individual areas of DB TestCopyData The DB for the TestCopy function is divided into several different areas: ● Area 1: DBB 0 ... DBB28

User interface for setting the TestCopy operating mode and displaying any errors. This user interface in turn is divided into the following areas: – Area 1.1: DBB 1 ... DBB 13:

Filter settings for RecvCopy function and number of counted received messages. – Area 1.2: DBB 15 ... DBB 27:

Filter settings for SendCopy function and number of counted sent messages. ● Area 2: DBB 29 ... DBB 39:

Internal management pointers ● Area 3: DBB 40 ... DBB xxxx:

Buffer area for storing messages that match the filter criteria; the buffer area must be configured as an array [0...xxxx] of WORDs.

Structure of a copied message block A message block can contain several messages. The messages are stored in DB TestCopyData according to the following rules: 1. The first entry indicates the time difference in milliseconds (7 decade BCD plus sign)

since the last selection of an operating mode > 0. 2. This is followed by a separation sign AAAA for sent messages, EEEE for received

messages. 3. Storage of the first message from the message block. 4. Separation sign AAAA, or EEEE: 5. Storage of the last message from the message block. 6. Block end ID FFFF.

Example All received messages will be stored in DB TestCopyData. Communication is implemented using X blocks, i.e. a max. of 76 bytes per receive block. The receive buffer of the XComData DB is the source for FC TestCopy. The current receive block contains 3 messages.



Length calculation FC TestCopy uses the following parameters for determining the minimum length for the DB TestCopyData:

Length of communication buffer

= LenComBuffer = 76 or 202 bytes

Minimum message length = LenMinTgrm = 14 bytes Offset management area = Offset = 40 bytes Length of the time difference = LenDt = 4 bytes Length of the block separators

= LenSeparator = 2 bytes

The formula used for the actual calculation is the same for X communication and B communication. The results differ only due to different lengths for the communication buffer for X and B communication:

SINAUT TD7 software package for the CPU 3.8 SFC / SFB system blocks used


a) For X communication:

LenMin_Xcom =LenComBuffer + Offset + Lendt + (LenComBuffer / LenMinTgrm + 1) * LenSeparator = 76 + 40 + 4 + (76 / 14 + 1) * 2 = 120 + 12 = 132 bytes minimum

a) For B communication:

LenMin_Bcom =LenComBuffer + Offset + Lendt + (LenComBuffer / LenMinTgrm + 1) * LenSeparator = 202 + 40 + 4 + (202 / 14 + 1) * 2 = 236 +40 = 276 bytes minimum

If FC TestCopy determines that the DB TestCopyData is not long enough, an error message to this effect is entered in data byte DBB28.

3.8 SFC / SFB system blocks used

Introduction System functions, SFCs, and system function blocks, SFBs, are part of the operating system of the CPUs and are used by the TD7 blocks as auxiliary blocks. Since it should be possible to run the TD7 package on all CPU types, as a basic rule the only system blocks used are those that are available on all CPU types. Here, it is mainly the 300 CPUs that determine the system blocks that can be used. Presently there are only a few exceptions to this rule, namely, FC ListGenerator which has separate versions for S7-300 and S7-400 and FB BCom which is only used for S7-400 because communication function block connections are only possible there. Because the system blocks are part of the operating system, they use no user memory. Below, you will see an overview of the system blocks used that exist on all CPU types. SFC 0 SET_CLK Block for setting the date and time of day in the CPU. SFC 1 READ_CLK Block for reading the date and time of day on the CPU. SFC 20 BLKMOV Block for copying contiguous data areas. SFC 22 CREATE_DB Block for online generation of data blocks.

SINAUT TD7 software package for the CPU 3.8 SFC / SFB system blocks used


SFC 46 STP Block for setting the CPU to ’STOP’. SFC 52 WR_USRMSG Block for entering a user message in the diagnostic buffer. SFC 64 TIME_TCK Block for reading the system time of the CPU. SFC 65 X_SEND Block for sending data over an unconfigured connection. SFC 66 X_RCV Block for receiving data over an unconfigured connection. Other system blocks only available in 400 CPUs: SFC 23 DEL_DB Block for online deletion of data blocks. SFC 24 TEST_DB Block whose uses include determining whether a specific data block is available in the CPU. SFC 25 COMPRESS Block for online compression of the user memory, for example, after the deletion of a data block. SFB 12 BSEND Block for block-oriented sending of data over a configured connection. SFB 13 BRCV Block for block-oriented reception of data over a configured connection.


SINAUT Diagnostics and Service tool 44.1 Overview of the functions and operation of the SINAUT Diagnostics

and Service tool

Introduction The SINAUT Diagnostics and Service tool provides the user with functions for checking connections, interfaces and communication as well as the firmware and software components of the network subscribers of a SINAUT installation. The most important functions are as follows: ● Reading the diagnostic data from a TIM or CPU module ● Reading the diagnostic buffer ● Checking and setting the module time ● Reading the module parameter assignment ● Activating a message trace ● Firmware update of TIM modules ● Downloading a new parameter assignment to the TIM modules

Note Diagnostics functions that are also available in the SIMATIC Manager are described here with the emphasis on diagnostics of TIM modules.

4.1.1 Starting the program and types of access

Opening the Diagnostics and Service tool The SINAUT Diagnostics and Service tool is opened in the Windows start menu SIMATIC / SINAUT ST7 / Diagnostics and Service. You can access the module-specific diagnostic information alternatively over: ● Accessible nodes ● the SINAUT subscriber list of the STEP 7 project

SINAUT Diagnostics and Service tool 4.1 Overview of the functions and operation of the SINAUT Diagnostics and Service tool


NOTICE

Regardless of whether you access this information using Accessible nodes or the SINAUT subscriber list, unless you activate the PG routing function, you can only access subscribers of the subnet of the local MPI bus to which the PG is connected.

Access using Accessible Nodes To access the diagnostic data using Accessible Nodes, follow the steps outlined below: 1. Click on the Accessible Nodes button

or click on the Project / Accessible Nodes menu. The Accessible Nodes dialog opens.

2. In the Selectable Nodes dialog, select the required subscriber from the list of MPI addresses by clicking on it with the mouse.

Figure 4-1 The Accessible Nodes dialog of a sample installation

Access using the SINAUT subscriber list of a STEP 7 project To open the STEP 7 project in the Diagnostics and Service tool and to access the diagnostic data using the SINAUT subscriber list, follow the steps outlined below: 1. Click on the Open Project button in the toolbar or select the Project / Open menu. The

Open dialog is displayed. 2. Select the STEP 7 project in the User Projects tab of the Open dialog and click on the OK

button. The project window with the SINAUT subscriber list of the relevant project opens.



3. If the required project is not displayed in the Open dialog, click the Browse button. In the Browse dialog that opens, you can search for other projects and include them in the project list. As an alternative, you can open a current project with the Project / Recently Used menu.

4. Select the subscribers you require for the subsequent diagnostic functions in the SINAUT subscriber list by clicking on them with the mouse.

Figure 4-2 The SINAUT subscriber list of a sample project

Note Attempting to access a remote subscriber using the SINAUT subscriber list of a STEP 7 project can lead to "misunderstandings" if the subscriber is not connected to the local MPI bus and the PG routing function is not activated. With functions involving access to the module, the remote subscriber is displayed in the Path field of the diagnostics dialog, however the diagnostic data is that of the locally connected subscriber.

The SINAUT subscriber list displays the following entries for each subscriber: ● Subscriber no.: The subscriber number of the SINAUT subscriber that is unique

throughout the project ● Red. Subscriber no.: The redundant subscriber number parameter is used only when

there is a redundant partner for the subscriber in question. The number specifies the common subscriber number under which the redundant system can be addressed by other subscribers.

● Subscriber no. of red. Partner: The Subscriber number of the redundant partner parameter is used only when there is a redundant partner for this subscriber. The parameter specifies which of the subscribers belong to a redundant relationship.

● Subscriber type: The subscriber type specifies the class of subscriber involved. The subscriber type cannot be set by the user.



● Name: The module, application or PC/PG name. This can be changed in the configuration. As default, this is the name of the module type or the application as specified in the configuration.

● Station: Name of the station specified by the user in the configuration using NetPro. ● SINAUT connected: Specifies whether a SINAUT connection was configured for the

subscriber. ● TD7 library version: With CPU modules and modules of the type TIM 3V-IE, the name of

the SINAUT system library for the TD7 software blocks is displayed. ● TIM firmware version: With TIM modules, the version of the TIM firmware is displayed.

PG Routing If you connect a programming device (PG) or a PC to access the diagnostic data, you only have access to the local MPI network. The diagnostic data of remote subscribers in other subnets is not accessible. To access subscribers in other subnets, you can use PG Routing. If you access data in a subordinate subnet after activating PG Routing, remember that you can only access subordinate subnets and not subnets higher in the network hierarchy. The prerequisites, functions and activation of PG routing are described in a separate chapter. The PG Routing function is possible only when using the SINAUT subscriber list; PG Routing is not possible when using Accessible Nodes.

4.1.2 Access to SINAUT subscribers and working with the diagnostics dialogs

Activating diagnostic functions The diagnostic functions are activated as follows: 1. Select a SINAUT subscriber by clicking on it with the mouse in Accessible Nodes or in the

SINAUT subscriber list of a STEP 7 project. 2. Start the required diagnostic functions with one of the following alternatives:

– Clicking on the corresponding button in the toolbar – Selecting the function in the Project, STEP 7 Diagnostics or SINAUT menus – Pressing the relevant function key – Right-clicking on the subscriber in Access of Nodes or in the SINAUT subscriber list.

After clicking on the subscriber, select the required function with the right mouse button in the displayed context menu.

3. The dialog belonging to the selected diagnostic function is displayed.

Working with the dialogs The graphic user interface of the SINAUT Diagnostics and Service tool is designed based on Windows technology. To use diagnostic functions, you must generally first select a particular subscriber or a component from a list in the Windows and dialogs and the function will then be executed and the diagnostic data displayed for this subscriber or component. The



function is then activated from a menu or by selecting a button and a dialog for the specific diagnostic function then opens. When selecting a menu, a subscriber, or object is described, this involves clicking on the object once within the left mouse button. Buttons found in many of the diagnostics dialogs are explained here and not in each subsection. These include the buttons: ● Print:

Starts a printout of the currently open dialog. ● Update:

Updates the content of the dialog with the current diagnostic data of the selected subscriber.

● Save: Saves the content of the open dialog in a file. You can select any directory and file name in the Save dialog.

● Load: Loads the diagnostic data relevant to the current dialog content from a previously saved file into the open dialog. The loaded diagnostic data is displayed in the dialog.

Note When loading data from a file, the current project data in the dialog is overwritten by the data from the file. To display the data of the connected subscriber again, the dialog must be closed and reopened, in some cases, the display can be updated with the data of the connected subscriber again using the Update button.

● Close: Closes the current dialog. You return to the Accessible Nodes or SINAUT subscriber list.

● Help: Opens the online help function for the currently selected diagnostic function.

● OK: Confirms the entries made and closes the dialog.

● Cancel: Discards the entries made and closes the dialog.

4.1.3 Functions of the Diagnostics and Service tool

Overview of the diagnostic and service functions The diagnostic functions of the SINAUT Diagnostics and Service tool can be grouped together as follows: ● STEP 7 diagnostics ● SINAUT diagnostics (TIM status information and TD7 software diagnostics) ● Message protocol diagnostics ● Service functions



The following table shows the diagnostic and service functions and all the menus in which the functions of the SINAUT Diagnostics and Service tool can be called. The two right-hand columns in the table indicate that the scope of information when using the SINAUT subscriber list of a STEP 7 project is greater than when using accessible nodes.

Table 4-1 Overview of the diagnostic and service functions of the SINAUT Diagnostics and Service tool

Function group, diagnostic function (remarks)

Subscriber type relevant for diagnostics

Called in menu

Access over STEP 7 project

Access using

Accessible Nodes

STEP 7 diagnostics STEP 7 diagnostics

CPU messages CPU, TIM " X X Module information (including messages in diagnostic buffer)

CPU, TIM " X X

Operating mode CPU, TIM " X X Setting the time CPU, TIM " X X SINAUT SINAUT diagnostics SINAUT TIM Diagnostics TIM " X X TIM subscriber diagnostics TIM " X X TIM block diagnostics TIM " X X TIM diagnostic messages TIM " X TIM Message Monitor TIM " X TD7 software diagnostics SINAUT TD7 CPU diagnostics (TD7 messages in diagnostics buffer)

CPU " X X

TD7 block structure (configured data)

CPU " X

TD7 block structure for all CPUs (configured data)

CPU " X

TD7 CPU program comparison (configured data)

CPU " X

TD7 communication configuration check (configured data)

CPU " X

TD7onTIM diagnostics TIM " X SDB Viewer CPU, TIM " X X Service functions SINAUT Download SDB TIM " X Firmware update TIM " X Repair TIM " X Message protocol diagnostics Project Testcopy DB CPU " X X TIM message protocol TIM " X X ST7cc / ST7sc message protocol: TIM " X X

The diagnostic information is displayed only for SIMATIC CPU modules and SINAUT TIM modules.

SINAUT Diagnostics and Service tool 4.2 STEP 7 diagnostics


4.2 STEP 7 diagnostics

Introduction STEP 7 diagnostics involves the standard diagnostic functions of SIMATIC STEP 7. Over and above SIMATIC installations, the STEP 7 diagnostics in the SINAUT Diagnostics and Service tool provides information not only on the CPU modules but also information on the TIM modules of a project. The functions in the SINAUT Diagnostics and Service tool that are implemented on the TIM module: ● CPU messages ● Module information ● Operating mode ● Setting the time

4.2.1 CPU messages

Description of the functions The CPU messages function is used to archive diagnostic messages entered by a CPU or TIM module in its diagnostic buffer. Without archiving, messages in the ring buffer of the CPU or TIM would be successively overwritten once the buffer is full. The CPU messages function registers the PG used for diagnostics with one or more modules. The modules then transfer all newly generated diagnostic messages to the registered PG. The diagnostic messages of one or more modules are archive in a common list on the PG. The archive is designed as a ring buffer. The oldest messages are overwritten by newly arriving messages once the archive is full.



Figure 4-3 CPU Messages dialog

The messages for diagnostic events are entered at the bottom of the dialog in the Archive tab of the message list. From the menu of the dialog or using the buttons of the toolbar, various user-specific settings can be made for message output such as emptying the archive, processing messages, the view of the message window, the settings for the archive size and saving the PG connections to the registered modules for the next time the CP messages function is called.

Operator activities 1. Select a subscriber by clicking on it in the SINAUT subscriber list of the open project or in

Accessible Nodes. 2. Open the CPU Messages dialog by selecting the STEP 7 Diagnostics / CPU Messages

menu. 3. To register the PG/PC for the CPU Messages function, select the module in the W

column of the module list at the top of the dialog. After the registration, the connection option (check box) of the module is selected in the W column. All the generated diagnostic messages of the module are then displayed in chronological order in the Archive tab of the message list at the bottom of the dialog. If no connection can be established to the subscriber, a symbol is displayed in the first column of the module list indicating that the connection is interrupted.



4. Click on the relevant field for the module in the W column of the module list again to deactivate archiving of the diagnostic messages.

5. Select the menu or the button of the dialog to change the settings. 6. Close the CPU Messages dialog by clicking on the close dialog button (x) in the title bar

or double-clicking on the dialog name in the title bar of the dialog. Closing the dialog deactivates the CPU Messages function.

4.2.2 Module information

Description of the functions The module information function reads diagnostic data from the module of the connected station. The diagnostic data is displayed for the specific module in a series of tabs: ● General tab

List of hardware and firmware components with their versions and information on the status of the CPU module

● Diagnostic Buffer tab List of diagnostic messages

● Memory tab Information on the utilization of the load and work memory.

● Time System tab Information on the data, time, time system and time synchronization as well as on the operating hours counter of CPU modules

● Performance Data tab Lists of the organization blocks, system blocks and address ranges

● Communication tab Information on transmission speeds, connection resources and cycle load caused by a communication

Further tabs are displayed for CPU modules: ● Cycle Time tab

Set and measured cycle times of CPU modules ● Stacks tab

Information on the content of the blocks stack (B stack), interrupt stack (I stack) and local data stack (L stack) of CPU modules

Operator activities 1. Select a local subscriber in the SINAUT subscriber list of the open project or in

Accessible Nodes. 2. Open the dialog by selecting the STEP 7 Diagnostics / Module Information menu. 3. Select the individual tabs with the mouse.



General tab The General tab displays the operating mode of the local CPU module and the operating mode and status of the connected module if this is selected for outputs of diagnostic data. The Status text box displays information on the status of the connected module from the perspective of the local CPU module. The following possible statuses are distinguished: ● Status OK: Module exists, access possible ● Status Error: Problem, access to module not possible (parameter assignment or access

error) Information on the module name and system identification is also display and in the Version output box, you will see a list of hardware and firmware components of the module with their order numbers or the name and version. This is followed by information on the rack, address and slot of the CPU module.

Diagnostic Buffer tab The Diagnostic Buffer tab displays the content of the diagnostic buffer of the module with information on the message number, time of day, date and event. The entries are sorted in descending chronological order; in other words, the latest message is at the top. For the TIM, the last 50 entries of the diagnostic buffer are displayed, for a CPU normally the last ten diagnostic messages. For TIMs, or diagnostic messages are displayed in plain language. For CPUs, the system diagnostic messages are displayed as plain language and the TD7 diagnostic messages (in other words the messages created by the SINAUT user program) are displayed in hexadecimal format. The station number (STA no.) listed with some messages in the Details on Event text box is the WAN network address of the relevant SINAUT network.

Note If you have selected a CPU and want to see the plain text equivalent of TD7 diagnostic messages displayed in hexadecimal format in the Diagnostic Buffer tab, select the TD7 CPU Diagnostics function for the same CPU. You will then see the same TD7 diagnostic messages • in the Module Information / Diagnostic Buffer dialog in hexadecimal format and • in the TD7 CPU Diagnostics dialog as plain text.



Figure 4-4 Module Information dialog, Diagnostic Buffer tab

To change the settings and select the event types of the message display in the Diagnostic Buffer tab, follow the steps outlined below: 1. Select the Settings button to open the Setting for Display Diagnostic Buffer dialog. The

default number of entries can be changed either for CPUs or TIMs. 2. In the Display Events box, select or deselect the event types for message output. The

selection is displayed or hidden. 3. In the lower part of the dialog, select the following options if necessary:

- Output event information in hexadecimal format - Update display during operating mode transition - Save settings for this dialog box

4. Confirm your settings by clicking on the OK button or to discard the settings, click on Cancel. You then return to the Diagnostic Buffer tab.

Memory tab The Memory tab displays information on the utilization of the free and assigned load memory and work memory. The work memory utilization of a TIM of approximately 90% is normal and adequate for the TIM to function.



Time System tab The Time System tab provides information on the time system of the module in three boxes: ● The current state and time of the module, its resolution and the existence of a real-time

clock ● Time-of-day synchronization (CPU only) ● Run-time meter (CPU only)

Performance Data tab The Performance Data tab does not contain any diagnostic information relevant to TIM modules. For CPU modules, information is displayed on organization blocks (OB), system blocks (SFC, SFB) and address ranges.

Communication tab The Communication tab displays the following information: ● Maximum and unused connection resources for

– PG communication – OP communication – S7 basic communication

● Configured cycle load due to communication. For a TIM, this is 100%. Information on a communication relates only to the CPU.

IP Parameter tab The IP Parameters tab displays the most important IP parameters of an Ethernet TIM: ● IP address: Configured IP address of the module. ● Subnet mask: Configured subnet mask of the module. ● Default router: If a default router was specified during configuration, the IP address of the

default router is displayed here. ● IP settings: Indicates where the module obtained the IP parameters from.



Figure 4-5 Module Information dialog, IP Parameter tab

Note With a TIM 4R-IE, only information on the first Ethernet port P1 is displayed. For an overview of the status and parameters of both Ethernet ports of the module, refer to SINAUT Diagnostics, IP Parameters tab.

Network Connection tab The Network Connection tab for an Ethernet TIM displays the MAC address of the module and information on the status and settings of the Ethernet port: ● Link Status: Indicates whether or not a physical connection to Ethernet exists. ● Settings: Shows the setting for detecting network settings, here: "Automatic"

(Autosensing) ● Mode: Indicates the transmission speed and duplexity on Ethernet.



Figure 4-6 Module Information dialog, Network Connection tab

Note With a TIM 4R-IE, only information on the first Ethernet port P1 is displayed. For an overview of the status and parameters of both Ethernet ports of the module, refer to SINAUT Diagnostics, IP Parameters tab.

Statistics tab This tab is available only for Ethernet TIMs. The Statistics tab contains transmission statistics for the Ethernet ports. The number of transferred data packets with and without errors since the last reset or restart of the module is displayed for the send and receive directions. This time time is displayed as module time in the tab. The statistical values can be reset to zero with the Reset button.



Figure 4-7 Module Information dialog, Statistics tab

4.2.3 Operating mode

Description of the functions With the Operating mode function, you can change the operating mode of TIM and CPU modules. Apart from the operating mode, the current keyswitch setting and the last operating mode are displayed for CPU modules. With TIM and CPU modules, the operating mode can be changed from Run to Stop or from Stop to Run. Changing the operating mode from Stop to Run triggers a restart on the TIM module.

Operator activities 1. Select a subscriber in the SINAUT subscriber list of the open project or in Accessible

Nodes. 2. Open the dialog by selecting the STEP 7 Diagnostics / Operating Mode menu. 3. Click on the Stop button to stop the module. 4. Click on the Warm Restart button to restart the module.

A TIM goes through a warm restart after approximately 10 seconds.



4.2.4 Setting the time

Description of the functions The Set Time of Day function is used to display and set the date and time of a module. It is possible to set the module time to the PG/PC time or to set an edited time. CPU modules have a hardware clock. TIM modules have a software clock in the operating system of the module.

Figure 4-8 Set Time of Day dialog


Nodes. 2. Open the dialog by selecting the STEP 7 Diagnostics / Set Time of Day menu. 3. To set the module time manually, click in the date or time display with the mouse, change

the data and/or time using the keyboard and confirm by clicking the Apply button or or select the Apply from PG/PC option in the Module time field and confirm by clicking the Apply button.

SINAUT Diagnostics and Service tool 4.3 SINAUT diagnostics


4.3 SINAUT diagnostics

4.3.1 TIM Diagnostics

Description of the functions The TIM Diagnostics function provides various diagnostic data of a TIM module. This is displayed in the following tabs: ● Memory tab:

Information on memory and disk configuration ● Message buffer tab:

Information on the buffer areas of an Ethernet TIM for messages ● Communication tab:

Displays the installed communication drivers on the various interfaces of the TIM ● Time synchronization tab:

Status of the time-of-day synchronization on the interfaces of the TIM ● Time tab:

Information on the system clock of the TIM ● Filesystem:

Displays all the files in the flash file system or (if installed) on the RAM disk of the TIM ● IP Parameters tab (TIM 4R-IE only):

Displays the current IP parameters and settings of the Ethernet ports ● Statistics tab (TIM 4R-IE only):

Displays the transmission statistics for the Ethernet ports


Nodes. 2. Open the dialog by selecting the SINAUT / TIM Diagnostics menu. 3. Select the individual tabs with the mouse. 4. To display the interface-specific diagnostic data in the Communication and Time

Synchronization tabs, select the name of an interface. The information on the relevant interface is displayed in the fields in the lower part of the two tabs. – In the Communication tab: Select an interface in the Communication drivers list box. – In the Time Synchronization tab: Select an interface in the Communication interfaces for

time synchronization list box



Memory tab

Figure 4-9 SINAUT Diagnostics dialog, Memory tab

The Memory tab displays current diagnostic data on the memory configuration on the TIM: ● In the Memory configuration field:

– Static flash EPROM – Dynamic flash EPROM – RAM – Available RAM Size of the free storage space available to the drivers on the TIM for

dynamic data. – Memory overflow: If the free RAM is no longer adequate, a checkmark appears in the

Memory overflow check box. – Message memory: Size of the memory for data messages that can be stored – Size of a memory block that is reserved for a data message. – Number of possible message entries calculated based on the size of the message

memory and the size of a memory block ● In the Disc configuration field:

– Storage space, used and free storage capacity of the flash or RAM disk.



Message buffer tab The Message buffer tab is available only for TD7onTIM-compliant TIM modules (for example TIM 3V-IE). The tab displays the current diagnostic data on the size and utilization of the buffer areas for messages on the selected TIM module. With TD7onTIM-compliant TIM modules, the message buffer is divided into various buffer areas: ● Buffer areas for data messages sorted according to destination subscribers (destination

subscriber buffers) ● Buffer areas for messages in TIM - TIM communication (TIM buffers) ● Buffer area for local communication with the CPU or an ST7cc/sc The Message buffer diagnostic function analyzes the buffer areas of the destination subscribers in which the data messages are stored. These are of particular interest to the user.

Figure 4-10 TIM Diagnostics - Message buffer tab

The Total output box provides the following information:



● Size (blocks): Total size of the message buffer. The value indicates the total number of message memory blocks. This is calculated from the total size of the message memory set for the TIM and the byte size of a memory block. The parameter assignment is made in the network configuration in NetPro in the Properties dialog, Options tab, Global message memory field.

● Free (blocks): Free area of the message buffer. The value indicates the number of free memory blocks.

● Free (%): Free area of the message buffer as a percentage

● image blocks: Number of blocks occupied by the TIM in the message memory for data messages transmitted using the image memory principle.

The Buffers list box shows the message buffers for various communication partners with the following information: ● from:

Subscriber number of the source subscriber ● to:

Subscriber number of the destination subscriber ● no. of messages:

Total number of stored messages for the relevant source and destination subscriber If a message buffer is selected on the left with the mouse in the Buffers field, the following detailed information is displayed in the Buffer info list: ● from:

Subscriber number of the source subscriber ● to:

Subscriber number of the destination subscriber ● Type:

– = 2: Buffer for organizational messages, hand-shake messages or message transmitted from one TIM to another TIM.

– = 4: Buffer for messages to a remote subscriber (CPU or ST7cc). – = 8: Buffer for messages to a local subscriber (CPU or ST7cc).

● no. of messages: Total number of stored messages for the source and destination subscriber named at the top

● no. of uncond. messages: Number of stored messages to be sent unconditionally and spontaneously (only relevant in dial-up networks)

● no of prio. messages: Number of stored messages to be sent with high priority.

● flags: Flags is a hexadecimal value that codes the buffer information following it into binary.



● forced image mode: All data messages are currently processed in forced image mode; in other words, even send buffer messages are handled like image messages

● data brake: The sending of messages to the remote partner is currently disabled either because the remote partner is unavailable or there is a lack of memory on the remote partner.

● blocked: Reserved for future functions. Nothing is currently displayed.

● overflow warning: Reserved for future functions. Nothing is currently displayed.

● XGA: Reserved for future functions. Nothing is currently displayed.

● uncond. messages: Reserved for future functions. Nothing is currently displayed.

● est. dial-up conn. Reserved for future functions. Nothing is currently displayed.



Communication tab

Figure 4-11 SINAUT Diagnostics dialog, Communication tab

The Communication tab displays information on the status of communication of the TIM with information on interfaces, drivers (available/not available) and baud rate. The data is displayed in the lower part of the dialog when you select one of the communication interfaces.



Time Synchronization tab The Time Synchronization tab displays information on the time synchronization on the various interfaces of the TIM with information on the interface, synchronization and status of time synchronization. The information is displayed in the lower part of the dialog when you select one of the communication interfaces.

Figure 4-12 SINAUT Diagnostics dialog, Time Synchronization tab



Time tab The Time tab displays the data and current module time of the TIM on the left in the Current time area. On the right in the Clock status area, information on the validity of the time, daylight saving/standard time and the changeover from daylight saving to standard time is displayed.

Figure 4-13 SINAUT Diagnostics dialog, Time tab



Filesystem tab The Filesystem town displays all the system data blocks and files of the individual firmware components installed on the flash file system. If a RAM disk is configured on the TIM, this is also displayed with the files it contains.

Figure 4-14 SINAUT Diagnostics dialog, Filesystem tab



4.3.2 TIM diagnostics - IP Parameters tab

IP Parameter tab This tab is available only for the TIM 4R-IE.

Figure 4-15 SINAUT Diagnostics dialog, IP Parameters tab

The IP Parameters tab displays the current IP parameters and settings of the Ethernet ports: ● IP Address: Configured IP address of the module. ● Subnet Mask: Configured subnet mask of the module. ● Default router: If a default router was specified during configuration, the IP address of the

default router is displayed here. ● MAC address: MAC address of the module ● IP settings: Indicates where the module obtained the IP parameters from.



● Link Status: Indicates whether or not a physical connection to Ethernet exists. ● Link settings: Shows the setting for detecting network settings, here: "Automatic"

(Autosensing) ● Mode: Indicates the transmission speed and duplexity on Ethernet.

4.3.3 TIM Diagnostics - Statistics tab

Statistics tab This tab is available only for the TIM 4R-IE. The Statistics tab contains transmission statistics for the Ethernet ports. The number of transferred data packets with and without errors since the last reset or restart of the module is displayed for the send and receive directions.

4.3.4 TIM subscriber diagnostics

Description of the functions The TIM Subscriber Diagnostics function displays the diagnostic data of the known SINAUT subscribers of the connected TIM module. The following detailed information is available: ● Selection list of the known subscribers (on the left):

The selection list of the known subscribers is used to select individual subscribers known to the connected TIM module allowing the information to be displayed in the tabs on the right. The known subscribers are listed with their subscriber number and subscriber type, if accessed over a STEP 7 project the name and station is also displayed.

● Status tab: Information on the availability of the partners or connection disruptions and information on data communication and the operation of the send buffer

● Partner tab: Displays the known partners: – With CPU modules: Display in the known partners tab of the CPU selected in the list of

known subscribers on the left of the dialog – With TIM modules: Display in the known partners tab of the connected TIM module

● Dialing extern (optional): Dial-up service and command of the connected TIM module

● Polling intern (optional): Data of the station poll of the partners of the connected TIM module connected over a dedicated line with the option of disabling or enabling a connected partner

The colored symbols in the selection list of known subscribers indicate the availability of the individual subscriber and have the following meaning:



Table 4-2 Symbols indicating subscriber availability in subscriber diagnostics

Symbol Status

Subscriber is available, all connections OK

Subscriber is available, at least one connection is disrupted

Subscriber is not available

Operator activities 1. Select a TIM module in the SINAUT subscriber list of the open project or in Accessible

Nodes. 2. Open the dialog by selecting the SINAUT / TIM Subscriber Diagnostics menu. 3. Select a subscriber in the selection list of the known subscribers on the left in the dialog. 4. To display the information on Status, Partner, Dialing extern or Polling intern, click on the

relevant tab.

Status tab The Status displays the following information on the subscriber selected on the left in the list of known subscribers from the perspective of the connected TIM module: ● In the General field:

– Availability of the known subscriber. Entries indicating problems are highlighted. – Any connection disruptions – Information on gateways to the known subscriber (subscriber local / remote)

● In the Connection field: – Interface of the connection – Type of connection – Connection enable – Information on polling – Status of data communication

● In the Special field: – Information on the operation of the send buffer of the known subscriber



Figure 4-16 TIM Subscriber Diagnostics dialog, Status tab

Partner tab The Partner tab displays the following no partners with their subscriber number, name and station in the List of partners area: ● With CPU modules: Display of the communication partners of the CPU selected in the list

on the left of the dialog ● With TIM modules: Display of the communication partners of the connected TIM module

selected in the subscriber list prior to opening the dialog. If different subscribers are selected on the left in the dialog, the same subscribers are always displayed in the List of partners.

With TIM modules, partners are only displayed in the TIM is installed in the master station and is connected to partners over a dedicated line.



Figure 4-17 TIM Subscriber Diagnostics dialog, Partner tab



Dialing extern tab If a TIM with master functionality is selected before you open the dialog, the Dialing extern tab displays the special services and the telephone number list (dial command) of the dial-up network driver of the connected TIM modules.

Figure 4-18 TIM Subscriber Diagnostics dialog, Dialing extern tab

The parameters Subscriber number, Special service, Call enabled and Dial command are displayed for the listed TIM modules. An "X" in the Call enabled column means that the connection is enabled. The following functions are available only for the TIM 4R-IE: ● By double-clicking on a subscriber in the dialing list, the Disable / Enable Subscribers

dialog opens in which the configured and current enable states of the selected subscriber are displayed from the perspective of the master TIM. The current enable status can be changed.

● The settings for enabling subscribers are stored permanently. ● Using the button below the list, you store the current enable status in the STEP 7 project

of the connected PG/PC.



Polling intern tab If a TIM with master functionality is selected before opening the dialog, the Polling intern tab displays the data of the station for for the known subscriber connected to the connected TIM over a dedicated line.

Figure 4-19 TIM Subscriber Diagnostics dialog, Polling intern tab

By double-clicking on a subscriber in the polling list, the Disable / Enable Subscribers dialog opens in which the configured and current enable states of the selected subscriber are displayed from the perspective of the master TIM. The current enable status can be changed. If you change the status to Disable in this dialog, the configured status is adopted again next time the master TIM is reset. The following functions are available only for the TIM 4R-IE: ● The settings for enabling subscribers are stored permanently. ● Using the button below the list, you store the current enable status in the STEP 7 project

of the connected PG/PC.

4.3.5 TIM diagnostic messages

Functional description With the TIM Diagnostic Messages function, Extended diagnostic messages are activated or deactivated and selected levels for various components of the TIM firmware. The extended



diagnostic messages contain detailed information on subfunctions of individual firmware components and are entered in the diagnostic buffer of the TIM. The extended diagnostic messages are displayed in hexadecimal format. The display of extended diagnostic messages can be selected for various firmware components and some functions (diagnostic areas). The diagnostic areas of the TIM 3 / TIM 4 and the Ethernet TIMs are different:

Table 4-3 Diagnostic areas of the TIM 3 / TIM 4

Firmware section of the TIM

Diagnostic area

Meaning / subfunction

Diagnostic server 1 Reception of organizational messages 2 Management of organizational messages 3 System status list query 4 Data synchronization with driver and device redundancy 5 Not used Routing server 1 not assigned 2 not assigned 3 not assigned 4 not assigned 5 not assigned 6 not assigned Installation program 1 not assigned 2 not assigned Clock driver 1 WAN/LAN synchronization cycle 2 not assigned 3 not assigned 4 not assigned External WAN driver 1 Interrupt level (receive direction) error messages 2 Interrupt level (receive direction) level 1 3 Interrupt level (receive direction) level 2 4 Control level 5 Task management in WAN driver 6 not assigned 7 not assigned Internal WAN driver 1 Interrupt level (receive direction) error messages 2 Interrupt level (receive direction) level 1 3 Interrupt level (receive direction) level 2 4 Control level




Diagnostic area


5 Task management in WAN driver 6 not assigned 7 not assigned

Table 4-4 Diagnostic areas of the Ethernet TIMs


Diagnostic area


Start manager 1 - 8 Reserved P bus driver 1 - 8 Reserved Clock driver 1 - 8 Reserved LAN communication 1 - 32 Reserved LAN communication 1 - 32 Reserved Subscriber administration 1 - 32 Reserved Message buffer 1 - 32 Reserved TD7onTIM 1 - 32 Reserved WAN driver 1 1 - 32 Reserved

Figure 4-20 TIM Extended Diagnostics dialog



Operator activities 1. Select a subscriber in the SINAUT subscriber list of the open project. 2. First open the Module Information / Diagnostic Buffer tab by selecting the STEP 7

Diagnostics/ Module Information / Diagnostic Buffer tab and click on theSettings button. 3. Make sure that the Update display during operating mode transition option is deselected

(no check mark) at the bottom of the Settings for Display Diagnostic Buffer dialog and confirm with OK. You can leave the Module Information dialog open.

4. Change to the SINAUT Diagnostics and Service tool and open the TIM Extended Diagnostics dialog by selecting the SINAUT / TIM Diagnostics menu.

5. Select the required function in the field on the left of the dialog. 6. Then select the following in the Firmware module and diagnostics level area

– The required firmware component in the Module list box and – The required level (area) in the Level list box.

7. Confirm your entries by clicking on the Activate button. A dialog Loading opens briefly and indicates that the activation information for extended diagnostics is being sent to the module by displaying a progress bar. Once the information has been sent successful, the Loading and TIM Extended Diagnostics dialogs are closed. Any diagnostic messages are activated on the selected module and displayed in the active diagnostic buffer. If multiple extended diagnostic messages are activated, you must confirm the activation of the message output for each individual firmware component and level with Activate.

8. Change back to the Module Information / Diagnostic Buffer tab that is still open and click on Update, if necessary, several times. Extended diagnostic messages are displayed in hexadecimal code. If necessary, save the diagnostic messages as a text file as described for the Module Information function.

9. To disable the output of extended diagnostic messages for an individual level, select the deactivate selected level option in the TIM Extended Diagnostics dialog and close the dialog with the Activate button.

10. To disable the output of all extended diagnostic messages for all firmware components and all levels of the selected subscriber, select the deactivate all extended levels option in the TIM Extended Diagnostics dialog and close the dialog with the Activate button.

NOTICE

If even one level of the extended diagnostic messages is activated, the size of the TIM diagnostic buffer is increased from 50 to 200 entries. Due to the increased memory requirements, extended diagnostic messages should not be activated permanently. After recording and saving the extended diagnostic messages, deactivate the Extended Diagnostics function again. The simplest method is to a deactivate the function with the deactivate all extended levels option. When you deactivate extended diagnostics, the size of the TIM diagnostic buffer is set back from 200 to the basic setting of 50 entries.



4.3.6 TIM Message Monitor

Description of the functions The TIM Message Monitor function is used to specify the settings for message monitoring of a selected TIM and starts the monitoring. In TIM message monitoring, the messages received and sent by the TIM are recorded. As soon as the monitoring function is activated, copies of every message are stored in a buffer created specifically for this function. The messages are read out of the buffer of the TIM and saved in a monitoring file. To start to message monitoring, you must set the following: ● the output file in which the recorded messages are saved and ● the stop action for the monitoring, either

– manual for - continuous sampling (reading out the buffer at 5 second intervals) or - read data once after stop of monitor,

– fill buffer only once or – time-limited reading by specifying the elapsed time.

Reading the data once after stopping monitoring is set if the messages are to be monitored following any intervention, for example turning off the TIM. If the message buffer of the TIM is read once without any time limitation, the entire saved SINAUT data traffic of the relevant TIM is read out. With the fixed buffer size of the TIM, this involves 400 messages. Monitoring is always started manually in the TIM Message Monitor dialog. When monitoring is started, the TIM Message Monitor progress bar is displayed and the group error LED of the TIM flashes while monitoring is active. If the manual stop option is selected, monitoring is also stopped in the TIM Message Monitor progress bar.



Figure 4-21 TIM Message Monitor dialog

Operator activities 1. Select a subscriber in the SINAUT subscriber list of the open project. 2. Open the TIM Message Monitor dialog by selecting the SINAUT / TIM Message Monitor

menu. 3. In the Output file box, enter the name of a file of the type *.7dt, in which your recorded

TIM messages will be saved or browse for the directory of the 7dt file in the file tree using the square button.

4. In the TIM Message Monitor dialog, in the Monitor stop action area, select one of the three options for starting message monitoring. If you select manual, you must decide whether the recorded messages are read by continuous sampling or after stopping monitoring.

5. Start monitoring with the Start Monitor button. The TIM Message Monitor progress dialog opens and displays information on the acquisition mode and the progress of the message recording over time indicating the elapsed and remaining time. The amount of data read and data remaining is also displayed.

6. Click on the End Monitor button in the TIM Message Monitor dialog to stop monitoring manually.

7. In the next dialog, decide whether you want to read the monitored messages immediately (the TIM Message protocol window opens) or whether you want to read the monitored messages at a later point in time (you return to the SINAUT subscriber list).

Note You can open and evaluate the TIM message protocol later using the TIM message protocol function of the Diagnostics and Service tool.



4.3.7 TD7 CPU Diagnostics

Description of the functions The TD7 CPU Diagnostics function displays all the diagnostic messages in the diagnostic buffer of a previously selected CPU. As default, this is 10 messages for the CPU. The display in this dialog is for: ● Diagnostic messages generated by SINAUT TD7 as plain text ● All other STEP 7 diagnostic messages in hexadecimal code.

The message list at the top of the dialog contains the diagnostic messages with information on the message number, time, date and event. The entries are sorted in descending chronological order; in other words, the latest message is at the top. In the lower part of the dialog in Details of event, you can see the event ID and additional information on the message selected above in the message list.

Note If you also want to view the STEP 7 diagnostic messages in plain text as well as the messages generated by TD7, open the STEP 7 Diagnostics / Module Information - Diagnostic Buffer tab dialog and position this next to the TD7 CPU Diagnostics dialog that is already open. The STEP 7 diagnostic messages displayed in hexadecimal format in the TD7 CPU Diagnostics dialog are then displayed alongside as plain text in the STEP 7 Diagnostics / Module Information dialog.



Figure 4-22 SINAUT Diagnostics dialog of the TD7 CPU Diagnostics function

Operator activities 1. Select a CPU module in the SINAUT subscriber list of the open project. 2. Open the dialog by selecting the SINAUT / TD7 CPU Diagnostics menu. 3. Select a message in the list, the additional information on this message is displayed

below the message list in the Details of event text box. 4. Click on Update to update the display in the dialog with the most recent messages from

the diagnostic buffer.

4.3.8 TD7 Block Structure

Description of the functions The TD7 Block Structure function provides information on the software blocks of a CPU. The function starts the block structure analysis of a previously selected CPU. It does not access the module but rather the project data. The results are displayed in four tabs:



● Statistics tab: This indicates the number, name, type and station of the selected subscriber and displays the communication partner and number of objects of the communication links

● Block tree tab: This displays a tree structure with information on the paths and all SINAUT blocks and the data of all SINAUT block calls for the subscribers of the entire project

● Block list tab: Presents the data of all SINAUT block calls in the form of a list

● Plausibility tab: Shows the results of plausibility checks for the calls of the SINAUT blocks BasicTask, Startup, Safe and ListGenerator and for the unique assignment of DP numbers, partner numbers and partner object numbers

The tree structure of the subscriber can be saved in the form of an XML file in all tabs using the Save function. The tree structure of a different version, a different subscriber or project previously saved as an XML file can be opened and viewed with the Load function in all tabs of the open dialog. The previous view is then overwritten.

Operator activities 1. Select a subscriber in the SINAUT subscriber list of the open project. 2. Open the dialog by selecting the SINAUT / TD7 Block Structure menu. 3. Select the relevant tab to display the information.

Statistics tab The Statistics tab lists the number, name, type and station of the selected subscriber in the Subscriber Information area on the left. The Communication Links area on the right displays the communication partners of the selected CPU and the number of communication objects per communication partner (target subscriber).



Figure 4-23 SINAUT TD7 Block Structure dialog, Statistics tab

Block tree tab The Block tree tab shows the information obtained on the project path and the path to the previously selected subscriber in a tree structure. The following information is listed: ● Project Information (__Info)

with general information on the project path and the logical path ● Subscriber number / station name

with all system blocks and user objects of the selected subscriber: – All SINAUT data blocks (__Blocks) in the program directory of the CPU – Information (__Info) on the module name, station name, type name, and subnumber of

the subscriber – The system blocks. These can be: BASICTASK, PARTNERMONITOR, SAFE,

PARTNERSTATUS, PULSECOUNTER, STARTUP, TIMETASK, STARTUP – The user objects (analog value, binary value, command, counter, setpoint objects etc.)

with - information on their call data and a - listing of the most important parameters of the individual user objects



Figure 4-24 SINAUT TD7 Block Structure dialog, Block tree tab

Block list tab The Block list tab presents the data of all SINAUT block calls in the form of a list. As default, the blocks are displayed in the following five columns: ● Subscriber: This contains the block icon and the subscriber number of the CPU. The

system blocks have a blue icon, the user blocks a yellow icon. ● Object name: Name of the system block or the user object ● Objectno.: Object number of the SINAUT object, the number of the instance DB used on

the CPU ● Partnerno.: Subscriber number of the SINAUT destination or source subscriber as part of

the SINAUT addressing (subscriber number, object number) ● Partnerobjectno.: Destination or source object number as part of the SINAUT addressing You can change the ascending order of the blocks within the block list by clicking on the column headers to sort according to the parameters of the individual columns. Further parameters are added to the view of the block list as follows: 1. Right-click within the tab and click on the Add columns context menu.



2. In the Add columns dialog that opens, click on the required parameters and confirm with the OK button. The added block parameters are not included permanently in the list view and are no longer present the next time you open the dialog.

Figure 4-25 SINAUT TD7 Block Structure dialog, Block list tab

Note The data of the block list are required for the configuration of a SINAUT ST7cc/sc control center and can be saved for this purpose in an XML file.

Plausibility tab The Plausibility tab runs a series of CPU-specific plausibility checks for the selected subscriber and displays the Check result. The following is checked: ● Whether the Startup SINAUT block was called correctly, ● Whether the Safe SINAUT block needs to be called and was actually called, ● Whether the object numbers (DB numbers) of the SINAUT blocks were assigned

uniquely, ● Whether the partner numbers and partner object numbers were assigned uniquely,



● Whether the BasicTask SINAUT block was called correctly, ● Whether the ListGenerator SINAUT block needs to be called and was actually called. If errors occur in the plausibility checks listed above, a corresponding message is displayed in the Check result text box.

Figure 4-26 SINAUT TD7 Block Structure dialog, Plausibility tab

4.3.9 TD7 Block Structure for all CPUs

Description of the functions The Block Structure crore CPUs function starts the CPU block structure analysis for the entire project. This function does not access the modules but rather the project data. It is, for example, possible to compare a CPU of the current project with the CPU of another project by opening the Block Structure for all CPUs dialog a second time in the SINAUT Diagnostics and Service tool and copying the data of the other CPU whose block structure data was previously saved as an XML file into the dialog using the Load function. The two open dialogs can be placed next to each other (overlapping if necessary) and compared. The results of the block structure analysis are displayed in four tabs:



● Statistics tab: This indicates the number, name, type and station of the selected subscriber and displays the communication partner and number of objects of the communication links. The CPU is selected in the tab.

● Block tree tab: This displays a tree structure with information on the paths and all SINAUT blocks and the data of all SINAUT block calls for the subscribers of the entire project

● Block list tab: Presents the data of all SINAUT block calls in the form of a list

● Plausibility tab: Shows the results of plausibility checks for the calls of the SINAUT blocks BasicTask, Startup, Safe and ListGenerator and for the unique assignment of DP numbers, partner numbers and partner object numbers

In all tabs, the block structure of the project can be saved in the form of an XML file using the Save function. The block structure of a different version, a different subscriber or project that was previously saved as an XML file can be displayed in all tabs of the open dialog using the Load function. The previous view is then overwritten.

Note Since the blocks of all CPU modules must be decompiled into STL source files for the TD7 Block Structure for all CPUs function, this function can take a considerable time in extensive projects.

Operator activities 1. Open the dialog by clicking on the SINAUT / TD7 Block Structure for all CPUs menu. 2. Select the relevant tab to display the information.

Statistics tab The Statistics tab lists the number, name, type and station of the selected subscriber in the Subscriber Information area on the left. Select the subscriber in the Subscriber no. list box at the top left in the tab. The Communication Links area on the right displays the communication partners of the selected CPU and the number of communication objects per communication partner (target subscriber).

Block tree tab The Block tree tab shows the information obtained on the project path and the path to all subscribers in a tree structure. The following information is listed: ● Project Information (__Info)

with general information on the project path and the logical path



● All subscribers with Subscriber number / Station name, with a listing of the system blocks and user objects freed subscriber with the following information: – All SINAUT data blocks (__Blocks) in the program directory of the CPU – Information (__Info) on the module name, station name, type name, and subnumber of

the subscriber – The system blocks. These can be: BASICTASK, PARTNERMONITOR, SAFE,

PARTNERSTATUS, PULSECOUNTER, STARTUP, TIMETASK, STARTUP – The user objects (analog value, binary value, command, counter, setpoint objects etc.)

with - information on their call data and a - listing of the most important parameters of the individual user objects

Block list tab The Block list tab presents the data of the SINAUT block calls of all subscribers in the form of a list. As default, the blocks are displayed in the following five columns: ● Subscriber: This contains the block icon and the subscriber number of the relevant CPU.

The system blocks have a blue icon, the user blocks a yellow icon. ● Object name: Name of the system block or the user object ● Objectno.: Object number of the SINAUT object, the number of the instance DB used on

the CPU ● Partnerno.: Subscriber number of the SINAUT destination or source subscriber as part of

the SINAUT addressing (subscriber number, object number) ● Partnerobjectno.: Destination or source object number as part of the SINAUT addressing You can change the ascending order of the blocks within the block list by clicking on the column headers to sort according to the parameters of the individual columns. Further parameters are added to the view of the block list as follows: 1. Right-click within the tab and click on the Add columns context menu. 2. In the Add columns dialog that opens, click on the required parameters and confirm with

the OK button. The added block parameters are not included permanently in the list view and are no longer present the next time you open the dialog.

Note The data of the block list are required for the configuration of a SINAUT ST7cc/sc control center and can be saved for this purpose in an XML file.



Plausibility tab The Plausibility tab runs a series of CPU-specific plausibility checks for a subscriber to the selected and displays the Check result. Select the subscriber in the Subscriber no. list box at the top in the tab. The following is checked: ● Whether the Startup SINAUT block was called correctly, ● Whether the Safe SINAUT block needs to be called and was actually called, ● Whether the object numbers (DB numbers) of the SINAUT blocks were assigned

uniquely, ● Whether the partner numbers and partner object numbers were assigned uniquely, ● Whether the BasicTask SINAUT block was called correctly, ● Whether the ListGenerator SINAUT block needs to be called and was actually called. If errors occur in the plausibility checks listed above, a corresponding message is displayed in the Check result text box.

4.3.10 TD7 CPU Program Comparison

Description of the functions The TD7 CPU Program Comparison function displays the results of the comparison of the program of two CPU modules. This function does not, however, access the data of the modules but rather the project data. When you open the dialog, the CPU selected in the SINAUT subscriber list is selected as CPU 1. To make the comparison, select either a further CPU of the same project or any other CPU whose program overview (block structure) was previously saved as an XML file. The CPU Program Compare Result dialog that then opens displays the names and stations of the compared CPU modules in the Compared Stations / CPUs area. On the left-hand side of the Results area below this, the components and subcomponents (TD7 objects) of the two CPU modules are listed with a symbol indicating the status of the comparison.

Table 4-5 Significance of the comparison symbols for components in a CPU program comparison

Symbol Status

The objects found are different

The objects found are identical

The object only serves informal purposes

When you select a component in the list on the left, the parameter names of the components and a comparison symbol are displayed for CPU 1 and CPU 2 in the right-hand part of the Results area. If the name of a parameter is identical on both CPU modules, the names displayed only under CPU 1. The comparison symbols have the following meaning:



Table 4-6 Significance of the comparison symbols for parameters in a CPU program comparison

Symbol Meaning

Subcomponents exist only on CPU 1


Components on CPU 1 and 2 are different

Components are identical on both CPUs

The data of the program comparison can be saved in an XML file. In the same way, data of an earlier program comparison that was saved in an XML file can be displayed again in the dialog using the Load button. The previous display is then overwritten. If you selected the wrong file when loading, an error message is displayed and the dialog display is deleted.

Figure 4-27 CPU Program Compare Result dialog



Operator activities 1. Select a CPU in the SINAUT subscriber list of the open project. This is identified as CPU

1 in the following dialog. 2. Select the TD7 CPU Program Comparison function by selecting the SINAUT / TD7 CPU

Program Comparison menu. The Compare TD7 Block Structures dialog opens. 3. Select a CPU of the project has CPU 2 for comparison in the CPU 2 box, below the

default option Use CPU. 4. As an alternative, select Use file in the CPU 2 box and open a previously saved XML file

with the block data of any other CPU module by clicking on the ... button. 5. Click on the Compare button. The CPU Program Compare Result dialog opens

Note If you use the XML file with the block structure data of a CPU other than CPU 2 in the Compared TD7 Block Structures dialog, the XML file must only contain the data of one CPU. Otherwise, the dialog with the compare results will not open.

4.3.11 TD7 Check of the Communication Configuration

Description of the functions The TD7 Check of the communication configuration functions is used to compare communication structures of two CPU modules. When you open the dialog, the CPU selected in the SINAUT subscriber list is selected as CPU 1. To make the comparison, select either a further CPU of the same project or the program overview (block structure) of any other CPU that was previously saved as an XML file. In the Compared Stations / CPUs area of the CPU Program Compare Result, the name and station of the compared CPU modules are displayed. In the Results area below, you can see the objects of the two CPU modules and a symbol indicating their comparisons status into columns on the left-hand side.

Table 4-7 Comparison symbol for components of the TD7 check of the communication configuration

Symbol Status

The objects found are different

The objects found are identical

The object only serves informal purposes

When you select a pair of objects in the list on the left, the names of the relevant object parameters and a comparison symbol are displayed for CPU 1 and CPU 2 in the right-hand part of the Results area. The comparison symbols have the following meaning:



Table 4-8 Comparison symbol for parameters of the TD7 check of the communication configuration

Symbol Meaning



Components on CPU 1 and 2 are different

Components are identical on both CPUs

Since parameters of the two CPU modules with the same functions are listed side by side in the right-hand part of the Results area, the objects of the two CPU modules must be crossed over to compare their communication plausibility. For example, the object number X of CPU 1 is the partner object number X of CPU 2 and vice versa. The data resulting from comparing the communication configuration of two CPU modules can be saved in an XML file. In the same way, data of an earlier comparison of the communication configuration that was saved in an XML file can be displayed again in the dialog using the Load button. The previous display is then overwritten. If you selected the wrong file when loading, an error message is displayed and the dialog display is deleted.

Figure 4-28 CPU Program Compare Result dialog



Operator activities 1. Select a CPU in the SINAUT subscriber list of the open project. This is identified as CPU

1 in the following dialog. 2. Open the Compare TD7 Block Structures dialog by selecting the SINAUT / TD7 Check of

the Communication Configuration menu. 3. Select a CPU of the project has CPU 2 for comparison in the CPU 2 box, below the

default option Use CPU. 4. As an alternative, select Use file in the CPU 2 box and open a previously saved XML file

with the block data of any other CPU module by clicking on the ... button. 5. Click on the Compare button. The CPU Program Compare Result dialog opens

Note If you use the XML file with the block structure data of a CPU other than CPU 2 in the Compared TD7 Block Structures dialog, the XML file must only contain the data of one CPU. Otherwise, the dialog with the compare results will not open.

4.3.12 TD7onTIM diagnostics

Description of the functions

Note The TD7onTIM Diagnostics function is available only for TD7onTIM-compliant TIM modules on which parameters were set for the TD7onTIM software (for example TIM 3V-IE).

TD7onTIM Diagnostics provides information on the status of the data transmission of the TD7onTIM software package of the TIM module selected in the SINAUT subscriber list.



Figure 4-29 TD7onTIM Diagnostics dialog with system object numbers based on the example

WatchDog

In keeping with the parameter assignment of TD7onTIM, the diagnostic functions are displayed for the following objects: ● Status of system objects ● Status of data objects ● Status of the input and output channels The dialog displays the following information for the station of the selected TIM module: ● The path of the TIM in the project ● The subscriber no. of the TIM ● The subscriber no. of the CPU The lower part of the dialog displays the SINAUT objects and channels with their parameters: ● TD7onTIM Configuration:

This area lists the following directories of the selected TIM as they are successively expanded: – System objects (blue symbols) – Data objects (yellow symbols)



– The cycle time – Send and receive channels

● Properties: This area displays the following properties of an object selected in the directory tree: – Parameter name – Value – Comment

The Parameter name column lists the individual parameters with colored symbols indicating the following status: - Blue symbols: Configured data - Red symbols: Online data The cycle time is displayed in the TD7onTIM Configuration area below the last data object. This is the current time of a sampling cycle in which TD7onTIM samples the work memory of its local CPU. If you click on the cycle time, the corresponding value is displayed in the Properties area.

Figure 4-30 TD7onTIM Diagnostics dialog with channel parameters based on the example of the

Analog send channel



Operator activities 1. Select a TD7onTIM-compliant module in the SINAUT subscriber list of the open project. 2. Open the dialog by selecting the SINAUT / TD7onTIM Diagnostics menu. The dialog

opens. 3. Expand the directory tree in the TD7onTIM Configuration area. 4. Select a SINAUT object or a send or receive channel in the opened directory tree. The

relevant parameters are displayed in the Properties area.

4.3.13 SDB Viewer

Description of the functions The SDB Viewer function lists the content of the system data blocks (SDBs) of a previously selected CPU or TIM module. For TIM modules, the following SDB classes can be selected for display: ● SDB0 ● WAN data ● Subscriber data ● Connection data ● LAN connections ● TD7onTIM data (only TIM modules on which parameters have been set for TD7onTIM) ● Ethernet data (only TIM modules that are connected to Ethernet) ● Routing data ● Connection data (PBC) Apart from SDB0, the representation of the SDB data for the TIM modules is in plain text (as default), you can, however, change to hexadecimal display. The CPU DBs are always displayed in hexadecimal and the corresponding button cannot be deactivated here. When accessing the subscriber using the SINAUT subscriber list, you have the option of displaying the system data blocks from the module (online) or from the project (offline). There may be differences between online and offline access. The content of all system data blocks can be saved as a text file.



Figure 4-31 SDB Viewer dialog. In the example, SDB1000 - WAN data is selected.


Nodes. 2. Open the SDB Viewer dialog by selecting the SINAUT / SDB Viewer menu. 3. To access data online on the connected module (instead of the project data), deselect the

offline option on the right to the dialog. The data display is updated immediately with the current module data.

4. Select the required system block class (SDB0, WAN data etc.) in the System data blocks list box.

5. Click on the Save button to save the content of all system data blocks as a text file.

SDB Viewer - SDB0 SDB0 is displayed in hexadecimal format and contains information on the following points: ● Communication parameters for the MPI bus ● Parameters for the time response of the MPI bus ● MPI address of the module ● Rack configuration with rack and slot addresses for S7-300 stations



WAN data SDB The WAN data SDB contains information on the parameter assignment of the TIM module and the WAN drivers as illustrated below based on an example.

Table 4-9 Example of the information of a WAN data SDB (type 3202)

Parameter block Parameter

Parameter block

TIM

- TIM operation mode: telecontrol mode - Return to TD7: no - Count of WAN drivers: 2 - Subscriber no. of TIM: 1002 - Size of global message memory: 0 - Size of memory block: 64 - Size of diagnostics buffer: 50 - Diagnostics level: 0 - Time synchronization * external WAN driver: minute scheme, every 5 minutes * internal WAN driver: minute scheme, every 5 minutes * MPI: minute scheme, every minute * TIM bus: no synchronization - Language: german - DCF77 radio clock: not present - Size of ram disk: 0 - Minimum heap reserve: 85 - TIM bus present: 0 - No of master: 1

Parameter block

WAN driver 1

Base parameters: - Interface: external - TIM type: station - Net type: dial-up network - Operating mode: spontaneous - Message format: FT1.2 - Acknowledgment: short acknowl. - Retry factor: 7 - WAN protocol: ST7 - Master/node station/station no.: 2 - Max. message length: 240 - Number of local CPUs: 1 - General request priority: 0 - Number of spontaneous messages: 0 - Baud rate: 38,400 - Call answer delay: 0 - Country mode: Germany - Dialing mode: AT mode - Dialing format: 8 data bits, no parity, 1 stop bit - Extra transmission time: 0 - Customer identification: 0 - Paramet. for cond. spont. mess.: standard conditions - Limit for locked messages: 0 - Transfer mode: send single messages - Cancel delay time: 0 - Operating mode: Interrupt (Block) - # of subscribers: 2



Parameter block Parameter

Telephone number list: - Block 1 own telephone number * Telephone number 1 Telephone number: 2

- Block 2 remote telephone numbers Redialing attempts: 3 Cancel parameter: 0 * Telephone number 1 driver type master No special service Station address: 1 Telephone number: ATDP3

AT string: ATS45=3\N0F0&W Parameter block

WAN driver 2

Base parameters: - Interface: internal - TIM type: station - Net type: dedicated line - Operating mode: polling - Message format: FT1.2 - Acknowledgment: short acknowl. - Retry factor: 3 - WAN protocol: ST7 - Master/node station/station no.: 2 - Max. message length: 240 - Number of local CPUs: 1 - General request priority: 0 - Number of spontaneous messages: 20 - Number of permanent messages: 0 - Station address of cyclic partner: 1 - Baud rate: 19,200 - Polling time: 0 - RTS/CTS delay time: 0 - Send delay time: 0 - Extra transmission time: 0 - Limit for locked messages: 0 - Operating mode: Interrupt (Block) - # of subscribers: 2



Subscriber data SDB The subscriber data SDB contains information on the settings for data of all subscribers of a project. The content of a subscriber SDB is shown below based on an example.

Table 4-10 Example of the information of a subscriber data SDB (type 3203)

Subscriber Parameter

# of subscribers: 5 Subscriber 1 Subscriberno.: 1

Subscriber info: 0x0 ST7-CPU additional info: 0x0 send NO status object to subscriber count of connection blocks: 2 device | subnet ID | CFB/MPI | state | connection | STA int. WAN | 008a00000001 | 0 | remote | WAN connection.,ST7 | 0x01 ext. WAN | 008a00000001 | 0 | remote | WAN connection.,ST7 | 0x01 count of partner blocks: 1 subscriber no.: 2

Subscriber 2 Subscriberno.: 1003 Subscriber info: 0x1 ST7 TIM etc.

Connection data SDB The connection data SDB contains information on the parameter settings of the local X connections of a TIM module to their CPU. This is illustrated below based on an example.

Table 4-11 Example of the information of a connection data SDB (type 3205)

count of X com. blocks: 1

block

1

connection type static

loc. device ID 0

target MPI 2



LAN connection SDB The LAN connection SDB contains summarized information on the parameter assignment of all LAN connections on a TIM module. This is illustrated below based on an example.

Table 4-12 Example of the information of a LAN connection SDB (type 3201)

local subscriberno.:

local MPI address:

1002 3

count of LAN blocks: 2 block 1 2

connection time X com not conf. PBC

CFB/MPI 2 4

size of queue 64 64

count of TIM blocks: 1 Sno. 1001

MPI 8

additional info 0x0

DCF77 NOT built in

CPU slave

external WAN driver NOT active

internal WAN driver NOT active

count of local partners: 2 MPI 2 3

Rack 0 0

Slot 2 7

TD7onTIM data SDB The TD7onTIM data SDB contains information on the parameter assignment of the SINAUT objects, their send and receive channels and the source or destination subscribers. An excerpt of this information is shown below based on an example.

Table 4-13 Example of the information of a TD7onTIM data SDB (type 3206)

Parametertype T4T SDB Main Header = 61185

Length of block:

Count of target subscribers:

Count of source subscribers:

Count of objects:

Count of system objects:

12 3 1 7 3

----------------------------------------------------

----------------------

Parametertype T4T SDB Target Subscriber = 61186

Length of block:

Type of target subscriber:

Subscriberno.:

Supervision time:

Timestamp:

12 4 8 900 1

----------------------------------------------------

----------------------

Parametertype T4T SDB Target Subscriber = 61186



Length of block:

Type of target subscriber:

Subscriberno.:

Supervision time:

Timestamp:

12 0 2 900 1

----------------------------------------------------

----------------------

Parametertype T4T SDB Source Subscriber = 61187

Length of block:

Subscriberno. of TIM:

MPI address of TIM:

Subscriberno. of CPU:

MPI address of CPU:

Ext. Time Stamp:

Max Spon Out:

Max Main In:

Max Sub In:

Scan Delay:

Max Input Time:

Input Delay Time:

Max Connect Time:

Address Check:

30 1003 8 4 7 0 3 2 5000 100 0 0 0 1

----------------------------------------------------

----------------------

Parametertype T4T SDB System Object = 61188

Length of block: 12

Type of system object: 32,512

DBNo | memLoc | byteAdr | bitAdr|

7 | DB | 1 | 0 |

----------------------------------------------------

----------------------

Parametertype T4T SDB System Object = 61188

Length of block: 28

Type of system object: 32,513


7 | DB | 2 | 0 |

Partner | Subscriberno.

1 | 8

2 | 2

3 | 0

4 | 0

5 | 0

6 | 0

7 | 0

8 | 0

----------------------------------------------------

----------------------

Parametertype T4T SDB Partner = 61190

Length of block: 6

Partnerno.: 1

----------------------------------------------------

----------------------

Parametertype T4T SDB Partner = 61190



Length of block: 6

Partnerno.: 8

----------------------------------------------------

----------------------

Parametertype T4T SDB Channel = 61191

Length of block: 48

Channel active: 1

Channel type = Message Send = 60929

Send On Difference: 1

Send On Period Active: 0

Send On Period: 10

Send On Command Active: 0

Send On Command:


0 |UNKNOWN| 0 | 0 |

Alarm Mask: 0

Send Buffer Principle Mask: 0

Disable Mask: 0

Input Data:

dataType | repeatF | dbNo | memLoc | byteAdr |

bitAdr|

BYTE | 1 | 0 | M | 11 | 0 |

----------------------------------------------------

----------------------

Ethernet data SDB The Ethernet data SDB contains information on the IP address of the selected TIM module, the subnet mask and any configured router. If, as in the case here, the address of the router is the same as the IP address of the TIM, no router is set. The IP addresses are set in network configuration.

Table 4-14 Example of the information of an Ethernet data SDB (type 3100)

IP address : 140. 80. 0. 3 subnet mask : 255. 255. 0. 0 default router : 140. 80. 0. 3



Routing data SDB The routing data SDB contains information on the individual subnets of a project. This is illustrated below based on an example.

Table 4-15 Example of the information of a routing data SDB (type 3002)

Subnet type ID, address

local subnet - local subnet ID : 47 11 00 00 00 0c - local device ID : 03

local subnet - local subnet ID : 47 11 00 00 00 14 - local device ID : 02

remote subnet - remote subnet ID : 00 8a 00 00 00 01 - next station addr : 01 - local device ID : 03

etc.

Connection data (PBC) SDB The connection data (PBC) SDB contains information on the PBC connections of a TIM module. This is illustrated below based on an example.

Table 4-16 Example of the information of a connection data (PBC) SDB (type 700)

STEP 7 connection - Connection setup: fixed configured, static - Connection type: active connection setup - Operating Mode: send no operating mode messages - Connection ID: 1 - local device ID : 01 - local TSAP ID: 11 04 - remote Station addr.: 02 - remote TSAP ID: 11 04

Consistent data SDB The consistent data SDB is used to check consistency of the SDBs. Based on these SDBs, the TIM can check the consistency of the SDBs generated for it.

Table 4-17 Example of the information of a consistency SDB (type 3118)

SDB no. Type Time stamp

1000 2 07/14/05 17:11:11 1001 3 07/14/05 17:11:11 1002 5 07/14/05 17:11:11 1003 1 07/14/05 17:11:11 1004 6 07/14/05 17:11:11 1005 7 07/14/05 17:11:11 1006 8 07/14/05 17:11:11 1008 1024 07/14/05 17:11:11

SINAUT Diagnostics and Service tool 4.4 Service functions


4.4 Service functions

4.4.1 Download SDB

Description of the functions The Download SDB function downloads the system data blocks of a TIM module from the program directory of the SIMATIC Manager to the module. This is the same procedure as the Download Module function in the SIMATIC Manager. To activate newly downloaded SDBs on a TIM module, the TIM must be restarted.

Note When a TIM module is restarted after downloading new SDBs, the connection between the TIM and other SINAUT partners (SINAUT connections) is terminated. This leads to error messages on the partners of the TIM module. In the case of a node TIM, the connections to the downstream stations are also reported as being disrupted. With a node TIM, any data messages stored on the TIM are lost during the restart. This can be important, particularly in dial-up networks.

When downloading SDBs to TIM modules, you should therefore note the following points: ● Before you transfer the SDBs, you should give the TIM the opportunity of transferring any

messages stored on it. ● After restarting the TIM, the SINAUT connections are established again automatically, the

connection between the PG and the TIM must, however, be activated by the user on the PG if it is required.

More detailed information refer to the section Installing and putting a TIM into operation / Configuring and assigning parameters for a TIM.

Operator activities 1. Select a TIM module in the SINAUT subscriber list of the open project. 2. Start the function by selecting the SINAUT / Download SDB menu. The Open dialog is

displayed. Follow the instructions in the subsequent dialogs. When necessary, you can cancel the procedure in these dialogs.

3. After downloading SDBs, the Open message dialog asks you when you want to start the module again. To activate the downloaded SDBs, you must restart the module.

4. Click on Yes to restart module. A message is displayed indicating that the SDBs were successfully loaded.

5. Confirm this message by clicking on OK.



4.4.2 Firmware update

Description of the functions The Firmware Update function allows you to load a new firmware version on a TIM module. The function is supported on TIM modules that have the RMOS for TIM-ST7 operating system as of version 2.04.

Note You can read out the version of the operating system of a TIM using the Module Information function / General tab.

To use this function, the firmware must have been installed on the computer using the setup. If the firmware is not installed on the PG or is incomplete, a message is displayed. By clicking the Update details button in the Firmware Update dialog, you open the Update details dialog that displays the firmware version installed on the TIM module and located on your computer. After the download, the module is automatically reset to activate the new firmware. The parameter assignment of the module is not affected by the firmware update.

Figure 4-32 Firmware Update dialog

Note Downloading the firmware to the module can take several minutes.



Operator activities

Note Make sure that you select the correct TIM module in your project. The station and module name must match and the configured module must be of the same type as the module to which you are downloading. If this is not the case, a dialog will inform you of this at regular intervals during the update. The display of this message interrupts the update until the dialog is acknowledged by clicking on OK.

1. Select the relevant TIM in the SINAUT subscriber list of the open project. 2. Start the function by selecting the SINAUT / Firmware Update menu. The Firmware

Update dialog opens. 3. Click on the Update details button if you require a detailed information on the firmware

update. The Update details dialog opens. 4. Click on the Update button in the Firmware Update dialog to start the firmware update.

The following dialog Loading informs you of the current progress of the update. 5. On completion of the firmware update, a dialog appears with a message to this effect.

Confirm the message with OK.

Update details dialog The Update details dialog that can be opened from the Firmware Update dialog displays detailed information on the firmware update. The function and version of each firmware component on the TIM module and on the PG is shown and you can see whether the relevant component is copied, replaced, ignored, or deleted during the firmware update. The various actions have the following significance: ● copy: The file is copied from the PG to the TIM module. ● replace: The file on the TIM module is replaced by the file on the PG. ● ignore: The file is not affected by the firmware update. ● delete: There is no newer version for the file. The existing file is no longer required and is

deleted during the firmware update.



Figure 4-33 Update details dialog of the Firmware Update function

4.4.3 Repair

Description of the functions The Repair function allows you to restore TIM modules with a defective flash disk. The Firmware Update function is available for loading firmware on a functioning TIM module. The Repair function runs a completely new installation of the firmware on a TIM module.

Note The Repair function should not be used without consulting the offline.

The Repair function is supported on TIM modules that have the RMOS for TIM ST7 operating system as of version 2.04.

Note You can read out the version of the operating system of a TIM using the Module Information function / General tab.

To use this function, the firmware must have been installed on the computer using the setup. If the firmware is not installed on the PG or is incomplete, a message is displayed. By clicking the Installation details button, you open the Update details dialog that displays the firmware version installed on the TIM module and the version on your computer.



Following the download, the module is automatically reset to activate the new firmware. Steps in repairing Repairing involves the following steps: ● The flash disk of the TIM module is formatted. After formatting, the TIM module runs a

reset. ● This is followed by a default startup. ● Once the wait time for the default startup has elapsed, the firmware version installed on

the computer is downloaded to the TIM. ● Following this, the system data blocks are transferred to the TIM module. ● The module is then reset and resumes operation with its full functionality.

Note While the firmware is being reinstalled, the TIM module has MPI address 3. Make sure that this address is free on the MPI bus to which the TIM module is connected.

Operator activities

Note Make sure that you select the correct TIM module in your project. The station and module name must match and the configured module must be of the same type as the module to which you are downloading. If this is not the case, a dialog will inform you of this at regular intervals during the update. The display of this message interrupts the update until the dialog is acknowledged by clicking on OK.

1. Make sure that MPI address 3 is either free or is occupied by the module on which you

want to install. 2. Select the TIM you want to repair in the SINAUT subscriber list of the open project. 3. Start the function by selecting the SINAUT / Repair menu and then Complete

reinstallation in the context menu. The Firmware Install dialog opens. The version installed on the PG is displayed. If the firmware on the PG is incomplete, a message to this effect is also displayed.

4. Click on the Update details button if you require a detailed information on the firmware update. The Installation details dialog opens.

5. Click on the Start Installation button in the Firmware Install dialog to start the repair. The following dialog Download informs you of the current progress of the procedure.

6. On completion of the repair, a dialog opens with a message to this effect. Confirm the message with OK.

SINAUT Diagnostics and Service tool 4.5 Message protocol diagnostics


Installation details dialog The Installation details dialog that can be opened from the Firmware Install dialog displays detailed information on the repair. For each firmware component, the function and version on the TIM module and on the PG are shown and you can also see whether the component will be copied, replaced, ignored or deleted during the repair. The various actions have the following significance: ● copy: The file is copied from the PG to the TIM module. ● replace: The file on the TIM module is replaced by the file on the PG. ● ignore: The file is not affected by the repair. ● delete: There is no newer version for the file. The existing file is no longer required and is

deleted during the repair.

4.5 Message protocol diagnostics

Introduction To read out messages, SINAUT ST7 provides you with the option of recording messages transferred in the CPU, TIM and ST7cc/ST7sc PC components; in other words, to archive them in protocols. The following protocol types are distinguished: ● Testcopy DB:

This is used to record messages on a CPU module. ● ST7cc/ST7sc protocol:

This is used to record messages in SINAUT ST7cc or SINAUT ST7sc. ● TIM message protocol:

This is used to record messages received and sent by a TIM module.

The message protocols are displayed in a message list in the form of a table.

Note The functions of message protocol diagnostics are used only to analyze message protocols that have already been saved. Message recording is activated • for the Testcopy DB by setting up DB99 in the SIMATIC Manager • for the SINAUT ST7cc/sc protocols by setting up the Textcopy block • for the TIM message protocol in the TIM Message Monitor function of the SINAUT

Diagnostics and Service tool



4.5.1 Testcopy DB

Description of the functions The recording of the message traffic on the CPU is made possible by the TestCopyData data block. With the aid of the FC Testcopy function, you can filter out certain message types that can be copied from the send or receive buffer of the CPU for further evaluation in a TestCopyData data block. The default for the TestCopyData data block is DB99. When setting the the data block, in the control field of the TestCopyData DB, you set filters for certain message types, subscribers and objects and make further settings. All send and receive messages are stored in the TestCopyData DB in chronological order. For a detailed description of the functions and setting up the TestCopyData DB, refer to the chapter SINAUT TD7 software package of the SINAUT ST7 system manual. With the aid of the Testcopy DB function of the SINAUT Diagnostics and Service tool, a TestCopyData data block is opened and the recorded messages displayed as a message list for further analysis.

Figure 4-34 Open dialog of the Testcopy DB function

Operator activities 1. Open the Open dialog by selecting the Project / Testcopy DB menu. 2. In the Open dialog, select the Online option at the top right if you want to access the

TestCopyData DB directly on the CPU module. This assumes that there is a functioning connection between the PG and the relevant CPU module.

3. In the Entry point list box, specify Project or Accessible nodes as the project type. 4. Select the required project in the Name list box or click on the Browse button if the project

is not available in the Name list box. The Browse dialog opens with the file tree of the PG/PC. Enter the directory path in the



Search in directory input box and then click the Start search button. Select the project you require in the User Projects tab on the right and click on the OK button. You return to the Open dialog.

5. On the left, in the folder list open the list of project stations by double-clicking on the project name and then double-click to select the following: - the required station - its CPU module - the S7 program and - the block folder. The individual objects of the selected block folder are displayed in the object list on the right. As default, only data blocks are displayed, since the object type data block is the default in the Object type list box below.

6. On the right in the object list, select the DB TestCopyData (DB99), this is entered in the Object name input box below.

7. Confirm with OK and the message protocol Testcopy DB opens. if the Testcopy DB does not include any messages, a message to this effect is displayed.

Working in the open Testcopy-DB message protocol is the same as in the TIM message protocol.

4.5.2 ST7cc / ST7sc protocol

Description of the functions The recording of the message traffic between SINAUT subscribers and an ST7cc or ST7sc control center is possible in ST7cc or ST7sc using the trace. The function of the trace is explained in the SINAUT ST7cc Control Center Manual. This contains precise information on starting the trace functions, displaying messages in the output window, activating the trace output files and other functionalities.

Operator activities 1. Open the ST7cc or ST7sc protocol by selecting the Project / ST7cc/ST7sc Protocol

menu. The Open dialog is displayed. 2. In the file tree, select the directory and the 7DS file of the ST7cc or ST7sc message

protocol you require and confirm with the Open button. The message protocol opens in a separate window.

Working in the open ST7cc or ST7sc message protocol is the same as in the TIM message protocol.



4.5.3 TIM message protocol

Description of the functions The recording of the TIM messages is started with the TIM Message Monitor of the SINAUT Diagnostics and Service tool. The messages received and sent by the routing server of the TIM are recorded. The TIM message protocol function is used only to open a TIM message protocol for subsequent evaluation.

Operator activities 1. Open the TIM message protocol by selecting the Project / TIM Message Protocol menu.

The Open dialog is displayed. 2. In the file tree, select the directory and the 7DT file of the required TIM message protocol

and confirm with the Open button. The TIM message protocol is opened in a separate window.

Note You activate and deactivate recording of the TIM message protocol and specify the name and storage location of the message protocol file using the TIM Message Monitor function of the Diagnostics and Service tool.

4.5.4 Diagnostics of the TIM message protocol With a few exceptions relating to format and the diagnostic data, the functions and handling of the TIM message protocol are largely identical with those of the other message protocol typesTestcopy DB and ST7cc/ST7sc protocol. The description can therefore also be applied to the other message protocol types.

Structure of the TIM message protocol The upper part of the TIM message protocol dialog summarizes the following information: - Total number of messages, - Number of messages shown, - Source and path of the protocol file Below this, there is the list of TIM messages, that has nine columns as default and provides the following information on every message: - A symbol for incoming and outgoing messages - Message number - Source: number of the open message protocols in ascending order - msec: Recording time with DB TestCopyData and ST7cc/ST7sc protocols - Block: Number of the message block with TIM message protocols - Subscriber number of the message source and destination - ST1 message number (only for SINAUT ST1 messages) - Object number of message source and destination - Index no.: Address parameters for net data in data messages - Org. Information



Figure 4-35 The TIM Message Protocol dialog

Functions of the TIM message protocol Further functions are available with the right mouse button in a context menu. These can be grouped as follows: ● Presentation of the messages ● Details (of the message content) ● Statistics ● Filter functions ● Exporting protocol files

Working with the message list After opening the TIM message protocol with the Project / TIM Message Protocol menu, the following options are available in the open dialog: 1. If you click on the header of any column, the message list will be sorted according to this

criterion instead of the consecutive number.



2. Right-click (cursor within the protocol window) to activate further functions. A context menu opens with other functions.

3. Select the required function with the left mouse button in the context menu. Each function opens a dialog.

Presentation of the messages Add new columns With this function, you can add extra columns in the TIM message list with further message information. After starting the Add New Columns function, the Add Column dialog opens in which you can select the properties with the mouse. The selected message properties are displayed as additional columns in the message list. Delete additional columns This function deletes all previously added columns. No further dialog is displayed.

Details The Details function provides you with detailed information on the content of the individual messages. To open the Details dialog, you must first select a message. As an alternative to using the right mouse button, the Details dialog can also be opened by double-clicking on a message in the list. In the upper part of the Details dialog, you can see the path of the protocol file and five tabs containing further information. To page to other messages within the Details dialog, click on the << or >> button. In each tab, the dialog view switches to the previous or next message. ● The Message Header tab displays a table containing three columns with the following

data from the message header of the selected message: – Variable name or short name of the message – Value of the individual variables – Variable name



Figure 4-36 Details dialog, Message Header tab

● The Net Data tab shows the net data of the message.

With the message type 0 and 1 (organizational messages), the data is displayed as plain text. with message type 2 and 3 (data messages), the values are displayed. The mode of the display can be changed with the Display mode list box using the mouse. The options are: - ST7 analog value - ST1 analog value - ST7/ST1 counted value - ST7/ST1 message



Figure 4-37 Details dialog, Net Data tab

● The TIM Routing Infos tab shows the following:

– At the top in the Message area: - the internal task ID - the complete message length [bytes]

– Below in the Address infos area: - the device ID as a number and in plain text (for example MPI bus) - the CN ID - the station address



Figure 4-38 Details dialog, TIM Routing Infos tab

● The Hex tab shows the following in hexadecimal format:

– In the complete buffer area, the content of the entire message – In the net data field, only the net data of the message



Figure 4-39 Details dialog, Hex tab

● The Source/Destination/Time stamp tab provides information in its 3 in areas on the

source, and destination and time stamp of the message. The fields provide the following information: – Source: Information on the subscriber number, name, type name, station name, object

number and index number – Destination: Information on the subscriber number, name, type name, station name and

object number – Time stamp: Information on the date, time, status, status info.



Figure 4-40 Details dialog, Source/Destination/Time stamp tab

Statistics The Statistics function provides a statistical evaluation of the entire message protocol in terms of numbers, types, and throughput of messages of the subscribers involved assorted according to ● All messages, data messages and organizational messages and according to ● Requested and spontaneous messages.

With the aid of the statistics, you can, for example recognize particular concentrations of certain message types with individual subscribers allowing you to decide whether normal or acceptable message traffic is possible in the particular installation. The Statistics dialog displays the statistical data of the TIM message protocol in three tabs. In each tab, the sampling period of message recalling is displayed at the top. The three tabs of the dialog list the messages as tables sorted according to the following: ● The Counters tab provides information on the total number of messages and the number

of different sent and received message types. ● The Message flow tab provides information on the amount of message traffic per minute.

It shows the total number of messages and the number of different sent and received message types per minute.



● The Subscriber tab displays a table with the number of different message types per subscriber. With the list box at the top right, you can sort the messages according to subscriber number or message type.

Figure 4-41 Statistics dialog, Subscriber tab

The Statistics function is only available for individual message protocols (sources) and is not supported, for example, a Testcopy DB or ST7cc protocol was inserted in a TIM message protocol.

Filter functions Delete list If you select the Delete list function with the mouse, the TIM messages displayed in the list view are deleted. This deletion can be reversed. The messages can be inserted in the list view again using the to functions Selection and Show all messages. Selection The Selection function is used to select certain message types to be displayed again after they were deleted from the list view. Messages can be selected, for example, according to individual subscribers, direction, message header entries etc. This function allows you to reduce the number of messages to make the list view clearer. Show all messages The Show all messages function insert or messages of the TIM message protocol in the list view that were previously deleted completely with the Delete list function or selectively with the Selection function.

SINAUT Diagnostics and Service tool 4.6 Messages in the diagnostic buffer of the TIM


Exporting protocol files Save current list The Save current list function is used to save the currently open list with all data of the current list view in a CSV file. The CSV file can then be read in MS EXCEL. If you activate the function, an input box opens in which you have the option of entering a comment on the protocol you are saving. This comment is then included in the top rows of the CS the saved file. You then specify the directory and file name of the CSV file. Export complete list The Export complete list function is used to save the entire country open list with all available data in an MS EXCEL-compatible CSV file. If you activate the Export complete list function, an input box opens in which you have the option of entering a comment on the protocol you are saving. This comment is then included in the top rows of the CS the saved file. You then specify the directory and file name of the CSV file.

Note You can open the CSV file created with the Save current list or Export current list functions in MS EXCEL by selecting the File / Open... menu, so that the data from the individual columns of the list view of the TIM message protocol are shown in separate columns in EXCEL. If you open the CSV file by double-clicking in the Explorer, the data is shown with separators but nevertheless in one single column.

4.6 Messages in the diagnostic buffer of the TIM

Introduction In much the same way as on and S7 CPU, a diagnostic buffer is also maintained on the TIM. The TIM stores its specific diagnostic messages in this buffer. The diagnostic messages of the TIM module are read out in the same way as those of a CPU.

Note If there is no text file with the diagnostic texts of the TIM events on the PG with which the diagnostic buffer is read out, the events are displayed in hexadecimal format.

4.6.1 Diagnostic messages of the TIM

Classification of TIM messages The TIM uses a reserved area within the event class F, namely Fx60, known as the event ID. All TIM diagnostic messages start with Fx60 in the hexadecimal representation, where x is is the placeholder for an identifier that allows a global classification of the message:



Table 4-18 Global classification of the TIM diagnostic messages

ID x Resulting event ID Classification 2 F260 Event message, exiting state 3 F360 Event message, entering state 4 F460 Event message, internal error, exiting state 5 F560 Event message, internal error, entering state 8 F860 Event message, external error, exiting state 9 F960 Event message, external error, entering state

The event ID Fx60 is followed by the actual message, the detailed event. This occupies the numeric range from 0000h to 0FFFh. Depending on the message, there may be additional information under Additional info 1/2/3 or Additional info 4/5.

The diagnostic messages of the TIM in hexadecimal and plain text format The following table lists all the TIM diagnostic messages in ascending order of the detailed event in hexadecimal format. To complete the picture, the corresponding event ID is also listed. The event ID is used only to classify the message and has no relevance for the order.

Table 4-19 Diagnostic messages of the TIM

Event ID (hex)

Detailed event (hex)

Meaning

General messages F560 Entering state: Heap memory overflow. F460

0001 Exiting state: Heap memory overflow eliminated.

Init task messages F360 0060 ST7 installation started. F560 0061 Error creating the message queue of the INIT task. F360 0062 Archive was created. F560 0063 Error installing the DNA interrupt service routine. F560 0064 Error installing the interrupt service routine for the external interface. F560 0065 Error installing the interrupt service routine for the internal interface. F560 0066 Error installing the TIMER interrupt service routine. F560 0067 Structure of the interface administration could not be entered in the catalog. F560 0068 Dongle flag not found in catalog. F560 0069 EXE loader not found in catalog. F360 006A Internal / external WAN interface: Driver not released. F560 006B Internal / external WAN interface: Error sending the load job for a driver. F560 006C Internal / external WAN interface: Error loading the basic task of a driver. F560 006D Internal / external WAN interface: Error creating the basic task of a driver. F560 006E Internal / external WAN interface: Error receiving the task ID of a driver.



Event ID (hex)


Meaning

F560 006F Internal / external WAN interface: Error starting the basic task of a driver. F560 0070 WAN SDB could not be opened. F560 0071 WAN SDB could not be found. F560 0072 Error sending the load job for the clock driver. F560 0073 Error loading the basic task of the clock driver. F560 0074 Error creating the basic task of the clock driver. F560 0075 Error receiving the task ID of the clock driver. F560 0076 Error starting the basic task of the clock driver. F560 0077 WAN SDB does not start with the TIM parameter block. F560 0078 Not enough memory available. F560 0079 Error creating the global message memory. F560 007A Error sending the load job for the routing program. F560 007B Error loading the basic task of the routing program. F560 007C Error creating the basic task of the routing program. F560 007D Error receiving the task ID of the routing program. F560 007E Error creating the main task of the routing program. F560 007F Routing tables were not created within the specified time. F560 0080 WAN driver was not installed within the specified time. F560 0081 Unknown parameter block in WAN SDB. F360 0082 Startup of module completed. F560 0083 Flag group unknown. F360 0084 RAM drive was created. F560 0085 Error creating RAM drive. F560 0086 Error in memory analysis in HEAP. F560 0087 Error installing the clock driver. No message received at end of installation. F360 0088 Message of the message and HEAP memory initialized on the TIM. F360 0089 Routing SDB could not be found. F560 008A Routing SDB could not be opened. F560 008B Routing SDB starts with incorrect subnet block ID. F560 008C No memory available for routing function. F560 008D Incorrect block ID detected in routing SDB. F560 008E Error sending a job to the LAN task. F560 008F Installation of the routing function was aborted. F560 0090 ST7 installation started. F360 0091 Wrong TIM firmware loaded. F560 0100 Module startup: Installation error LAN messages F560 0101 Installation of the AMPLUS-L emulation aborted. F560 0103 LAN communication: Error sending a message. F560 0104 LAN communication: Error receiving a message or ID unknown. F360 0105 LAN communication: Unknown job.



Event ID (hex)


Meaning

F360 0106 LAN communication: Connection could not be entered in routing table. F360 0107 LAN communication: Connection could not be deleted in routing table. F560 0108 LAN communication: Error in a connection SDB. F360 0109 LAN communication: No resources available for connection. F560 010A LAN communication: PBC connection could not be established. Reference number unknown. F560 010B LAN communication: PBC connection could not be established. Reference number unknown. F360 Entering state: LAN communication: Connection down. F260

010C Exiting state: LAN communication: Connection OK.

F560 Entering state: LAN communication: Threat of send queue overflow for a connection. F460

010D Exiting state: LAN communication: Threatening send queue overflow for a connection eliminated.

F560 Entering state: LAN communication: Send queue overflow for a connection. F460

010E Exiting state: LAN communication: Send queue overflow for a connection eliminated.

F560 Entering state: Disruption of MPI/party line interface (SPC/2) detected. F460

010F Exiting state: Disruption of MPI/party line interface (SPC/2) eliminated.

F560 0110 LAN communication: Error reading the LAN SDB. F560 0111 LAN communication: Error occurred during PBC send. F560 0112 LAN communication: Error in SDB0 – bad MPI parameter. F560 0113 LAN communication: A negative acknowledgment was sent. F560 0114 No Ethernet SDB. F560 0115 Ethernet SDB could not be opened. F560 0116 Ethernet SDB with bad block ID received. F560 0117 Error creating a socket. F560 0118 Error linking a socket. F560 0119 Invalid socket. F560 011A Error listening on a socket. F560 011B Ethernet port: RFC1006 has received a packet whose length exceeds the maximum. F560 011C Bad RFC1006 PDU header. F560 011D Undefined PDU received. F560 011E Bad TCP/IP packet. F560 011F Error setting a socket. F560 0120 Error in ACCEPT socket. F560 0121 TCP/IP connection termination by partner. F560 0122 TCP/IP reception error. F560 0123 TCP/IP send error. F560 0124 TCP/IP connection number invalid. F560 0125 Error receiving a CR-PDU. F560 0126 Illegal access over TCP/IP. F560 0127 Invalid PDU length. F560 0128 KEEPALIVE expired. F560 0129 Entering state: Connection information: Ethernet port problem.



Event ID (hex)


Meaning

F460 Exiting state: Connection information: Ethernet port ok. F560 012A Error in socket CONNECT job. F560 012B Error receiving a CC-PDU. F560 012C Unknown error code. F560 012D Maximum number of S7 connections exceeded. WAN messages F560 0300 Internal / external WAN interface: Installation of the WAN driver was aborted. F360 0301 Internal / external WAN interface: WAN driver is installed. F360 0302 Internal / external WAN interface: Connection to a subscriber established (incoming call;

subscriber number identified). F560 0303 Bad organizational message from routing task. F360 Entering state: Internal / external WAN interface: Send buffer changed over to image. F260

0304 Exiting state: Internal / external WAN interface: Send buffer changed back from image.

F360 Entering state: Internal / external WAN interface: Send buffer overflow occurred. F260

0305 Exiting state: Internal / external WAN interface: Send buffer overflow eliminated.

F960 0306 Bad message: max. number of destination subscribers exceeded. F960 0307 Bad message: Unknown source subscriber number. F960 0308 Bad message: S7 PDU not with AE ID = 2. F960 Entering state: Internal / external WAN interface: CTS disturbance occurred on modem. F860

0309 Exiting state: Internal / external WAN interface: CTS disturbance eliminated on modem.

F560 Entering state: Internal / external WAN interface: USART error occurred. F460

030A Exiting state: Internal / external WAN interface: USART error eliminated.

F360 Entering state: Subscriber failed. F260

030B Exiting state: Subscriber OK.

F360 Entering state: Internal / external WAN interface: WAN driver disabled. F260

030C Exiting state: Internal / external WAN interface: WAN driver enabled.

F360 Entering state: Internal / external WAN interface: Subscriber call disabled. F260

030D Exiting state: Internal / external WAN interface: Subscriber call enabled.

F360 Entering state: Internal / external WAN interface: Subscriber call in subcycle. F260

030E Exiting state: Internal / external WAN interface: Subscriber call in main cycle.

F360 Entering state: Internal / external WAN interface: Permanent call to a subscriber enabled. F260

030F Exiting state: Internal / external WAN interface: Permanent call to a subscriber ended.

F360 Entering state: Internal / external WAN interface: Lack of resources on a subscriber. F260

0310 Exiting state: Internal / external WAN interface: Lack of resources on a subscriber eliminated.

F360 Entering state: Internal / external WAN interface: Alternative path changeover on. F260

0311 Exiting state: Internal / external WAN interface: Alternative path changeover off.

F560 0312 Internal / external WAN interface: No message memory available for new image element. F560 0313 Internal / external WAN interface: Image element too large for image memory. F560 0314 Internal / external WAN interface: Set number of subscribers exceeded in image. F560 0316 Internal / external WAN interface: 'List of Active Stations' (LAS) not available. F560 0317 Internal / external WAN interface: Error receiving a message.



Event ID (hex)


Meaning

F560 0318 Internal / external WAN interface: Error enabling message memory. F560 Entering state: Internal / external WAN interface: Communication with AMPLUS-L task

disrupted. F460

0319

Exiting state: Internal / external WAN interface: Communication with AMPLUS-L task OK. F560 Entering state: Internal / external WAN interface: Communication with clock driver disrupted. F460

031A Exiting state: Internal / external WAN interface: Communication with clock driver OK.

F560 Entering state: Internal / external WAN interface: Communication with routing task disrupted. F460

031B Exiting state: Internal / external WAN interface: Communication with routing task OK.

F560 031C Internal / external WAN interface: Modem command invalid. F560 031D Internal / external WAN interface: Invalid dialing string or bad call number transferred to

modem when calling a subscriber. F960 031E Internal / external WAN interface: Incorrect handshake PDU received from a subscriber. F360 031F Internal / external WAN interface: Own telephone connection occupied. F960 0320 Internal / external WAN interface: Modem not replying. F960 0321 Internal / external WAN interface: Access to called subscriber not permitted. F960 0322 Internal / external WAN interface: No answer tone received from modem of called subscriber. F960 0323 Internal / external WAN interface: Called subscriber is not operational. F960 0324 Internal / external WAN interface: Modem of called subscriber has no power. F960 0325 Internal / external WAN interface: Telephone line is disrupted. F360 0326 Internal / external WAN interface: Supervision time exceeded. Repetition starting. F360 0327 Internal / external WAN interface: All attempts to dial a subscriber were executed. No

connection was established. F360 Entering state: Internal / external WAN interface: Telephone number list with telephone

number(s) of a subscriber deactivated. F260

0328

Exiting state: Internal / external WAN interface: Telephone number list with telephone number(s) of a subscriber activated.

F560 0329 Internal / external WAN interface: Telephone number list with telephone number(s) of a subscriber is invalid or disrupted.

F360 032A Internal / external WAN interface: Telephone number of a subscriber temporarily disabled. F360 032B Internal / external WAN interface: Telephone number of a subscriber was changed. F560 032C Internal / external WAN interface: STA number not found in telephone number list. F360 Entering state: Internal / external WAN interface: Permanent connection established to a

subscriber. F260

032D

Exiting state: Internal / external WAN interface: Permanent connection to a subscriber was terminated.

F360 Entering state: Internal / external WAN interface: Permanent connection to a subscriber was registered.

F260

032E

Exiting state: Internal / external WAN interface: Permanent connection to a subscriber was deregistered.

F560 032F Internal / external WAN interface: Permanent connection to a subscriber was aborted. F360 Entering state: Internal / external WAN interface: Incoming call disabled. F260

0330 Exiting state: Internal / external WAN interface: Incoming call enabled.

F360 0331 Internal / external WAN interface: Establishing connection to a subscriber.



Event ID (hex)


Meaning

F360 0332 Internal / external WAN interface: Connection to a subscriber established (outgoing call). F360 0333 Internal / external WAN interface: Connection to a subscriber established (incoming call;

subscriber number not yet identified). F360 0334 Internal / external WAN interface: Connection to a subscriber was terminated. F560 0335 Internal / external WAN interface: Connection to a subscriber was aborted. F360 0336 Internal / external WAN interface: Connection to a subscriber is already terminated. F360 0337 Internal / external WAN interface: Supervision time exceeded. No repetition. F360 0338 Internal / external WAN interface: Send buffer was deleted. F360 0339 Internal / external WAN interface: Image memory and send buffer were deleted. F360 033A Internal / external WAN interface: No telephone number in modem memory. F960 033B Internal / external WAN interface: PDU received with unknown STA number. F360 Entering state: Internal / external WAN interface: Driver redundancy - memory management

switched over. F260

033C

Exiting state: Internal / external WAN interface: Driver redundancy - memory management switched back.

F560 033D Internal / external WAN interface: Incorrect service request to pager (SMS). F360 033E Internal / external WAN interface: No entries in the send queue. F560 033F Internal / external WAN interface: Unknown message type. F560 0340 Internal / external WAN interface: Communication with WAN driver disrupted. F360 0341 Internal / external WAN interface: Incoming call (RING). F960 0342 Internal / external WAN interface: No connection with incoming call. F960 0343 Internal / external WAN interface: Call or connection abort. F960 0344 Internal / external WAN interface: No carrier frequency detected on partner. F360 Entering state: Internal / external WAN interface: Further dialing attempts were made in the

background to a disturbed subscriber. F260

0345

Exiting state: Internal / external WAN interface: Subscriber is available again. Dialing attempts in the background will be stopped.

F960 0346 Internal / external WAN interface: Incorrect PIN number transferred to GSM module. F960 0348 Internal / external WAN interface: Error occurred in GSM module. F960 0349 Internal / external WAN interface: GSM module not responding or not available. F960 034A Internal / external WAN interface: SMS server of the TIM has received an unknown message.F960 034C Internal / external WAN interface: Short message (SMS) acknowledgment received from an

unknown mobile subscriber. F360 034E Internal / external WAN interface: Incoming call detected. Incoming calls are disabled. F360 034F Internal / external WAN interface: Incoming call detected. DTR signal was activated. F360 0350 Internal / external WAN interface: SMS server of the TIM was installed and started. F360 0351 Internal / external WAN interface: SMS status, global status request/deletion. F360 0352 Internal / external WAN interface: SMS status, single status request/deletion. F360 0353 Internal / external WAN interface: Spontaneous SMS status message. F960 0354 Internal / external WAN interface: Short message (SMS) acknowledgment incorrect. Format

or ID no. unknown. F560 0355 Internal / external WAN interface: No send buffer could be made available for sending a short

message (SMS).



Event ID (hex)


Meaning

F960 0356 Internal / external WAN interface: The GSM module expects the PUC number. F960 0357 Internal / external WAN interface: Telephone number of the SMS recipient could not be found.F360 0358 Internal / external WAN interface: The GSM signal strength is xx dBm. F360 0359 Subscribers cannot be blocked. F360 035A Internal / external WAN interface: GSM module detects wrong service ID. F360 035B Internal / external WAN interface: GSM module ready to receive. F360 035C Internal / external WAN interface: The switchover to the image method for blocked messages

was forced. F360 035D Internal / external WAN interface: Threat of forced switchover to image method. F360 035E Internal / external WAN interface: Threat of forced switchover to image method. F360 035F Internal / external WAN interface: Permanent connection already active. F360 0360 Internal / external WAN interface: Maximum number of messages exceeded. F360 Entering state: Internal / external WAN interface: The data brake for the connection to a

subscriber was enabled. F260

0361

Exiting state: Internal / external WAN interface: The data brake for the connection to a subscriber was disabled.

F960 0362 Internal / external WAN interface: After transferring the PIN to the GSM module, no network contact could be established.

Messages from the routine task F560 0500 Installation of the routing program aborted. F560 0501 Internal / external WAN interface: Receive task of the WAN driver unknown. F560 0502 Receive task of the clock driver unknown. F560 0503 Read time function unknown. F560 0504 Receive task of the LAN task unknown. F560 0505 Partner table unknown. F560 0506 Error occurred receiving a message. F560 0507 Unknown PDU received. F560 0508 PDU with bad address received. Destination subscriber number not found. F560 0509 No WAN driver available. F560 050B Error enabling heap memory. F560 050C Installation of the routing program ended. All routing tables available. F560 050D Error occurred sending a message. F560 050E No resources for creating the destination address table. F560 050F Destination address table not created. F560 0510 No resources for PDU copy. F560 0511 No resources for copy of partner table. F360 Entering state: Internal / external WAN interface: Redundancy function activated. F260

0512 Exiting state: Internal / external WAN interface: Redundancy function deactivated.

F960 0513 Message with incorrect block length received or block length is zero. F560 0514 Max. number of messages exceeded. F560 0515 Error in time-of-day synchronization over LAN. F560 0516 MesA - Error sending a message.



Event ID (hex)


Meaning

F560 0517 The partner table/substitute table of a subscriber does not exist. F560 0518 Error releasing memory. F560 0519 Error in the MesA memory management F560 Entering state: MesA - Start of indication of a message memory overflow. F460

051A Exiting state: MesA - End of indication of a message memory overflow.

F560 Entering state: MesA - Start of indication of a message memory overflow. F460

051B Exiting state: MesA - End of indication of a message memory overflow.

F560 051C Message memory overflow occurred. F560 Entering state: Start of indication of a message buffer overflow. F460

051D Exiting state: End of indication of a message buffer overflow.

F560 Entering state: Overflow of message buffer active. F460

051E Exiting state: Overflow of message buffer deactivated.

F560 051F Buffer with messages was deleted. F560 0520 MesA - Error in the dynamic assignment table. F560 0521 MesA - WAN/LAN router: Error sending messages. F560 0522 MesA could not send the acknowledgment for an org. 262 PDU to SubA. F560 0523 MesA - WAN/LAN router; error sending over WAN/LAN driver. F560 0524 Installation error occurred in the MesA. F560 0530 MesA - System error occurred. F560 0531 MesA - Error in the request for an Org4/14 message. F560 0532 MesA - Unknown control command received. F560 0533 MesA - Error in MesA system status list query. F560 0534 MesA: Bad PDU detected. Messages from clock driver F560 0620 Installation of clock driver aborted. F360 0621 for error code = 0: Installation of the clock driver completed

for error code = 1: Installation of clock driver aborted. F560 Entering state: Time synchronization (master) disturbed. F460

0622 Exiting state: Time synchronization (master) OK.

F960 Entering state: Time synchronization (slave) disturbed. F860

0623 Exiting state: Time synchronization (slave) OK.

F560 0624 Error occurred setting the RMOS clock. F560 0625 Error occurred reading the RMOS clock. F360 0626 Illegal setting of the RMOS clock by Set clock PG service. TIM has onboard DCF77 clock. F360 0627 Unknown message received. F360 0628 Time synchronization PDU with incorrect ORG number received. F360 0629 Bad synchronization PDU received from LAN. F560 Entering state: Time synchronization by DCF77 clock disturbed. F460

062A Exiting state: Time synchronization by DCF77 clock OK.

F960 Entering state: DCF77 clock radio signal disturbed. F860

062B Exiting state: DCF77 clock radio signal OK.



Event ID (hex)


Meaning

F360 062C TIM time OK. RMOS clock set for the first time. F360 Entering state: Changeover to daylight saving time. F260

062D Exiting state: Changeover to standard time.

F360 Entering state: Notification hour for daylight saving/standard time changeover active. F260

062E Exiting state: Notification hour for daylight saving/standard time changeover completed.

F360 0630 Change in synchronization mode. F360 0631 Daylight saving/standard time changeover performed manually. F360 0632 Error occurred in manual daylight saving/standard time changeover. F560 0633 Error occurred starting the synchronization task. F560 0634 Error occurred starting the control task for synchronization. F960 0635 Two time masters detected in one network. F960 0636 Incorrect synchronization mode on MPI. Master mode expected. F960 0637 No further module exists on MPI bus/party line. F560 0638 External / internal WAN interface: A subscriber could not be synchronized following restart. F360 0639 Error detected in time-of-day synchronization. F360 063A Bad time-of-day message received from DCF77 module. F360 063B Bad time-of-day message received from DCF77 module. F360 063C Time jump occurred. F360 063D Bad time-of-day message received from DCF77 module. F560 063E Error in synchronization request. Messages from diagnostic server F560 0660 Error occurred installing the diagnostic server. F360 0661 Installation of diagnostic server completed. F560 0662 Error occurred sending a message. F560 Entering state: Error occurred receiving a message. F460

0663 Exiting state: Error occurred receiving a message.

F560 Entering state: Heap memory overflow. F460

0664 Exiting state: Heap memory overflow eliminated.

F960 Entering state: Unknown PDU received. F860

0665 Exiting state: Unknown PDU received.

F560 0666 Incorrect firmware version installed on TIM. F360 Entering state: All [n] LAN connections are disrupted. F260

0667 Exiting state: [x] of [n] LAN connections are OK.

F360 0668 Message buffer of TIM records was deleted. F360 Entering state: ST7 Message Monitor on F260

0669 Exiting state: ST7 Message Monitor off

F360 Entering state: Extended diagnostics on F260

066A Exiting state: Extended diagnostics off

F360 066B Extended diagnostics - modification F360 066C Error occurred in system status list query. F560 066D Wrong firmware.



Event ID (hex)


Meaning

Messages from P bus server F560 06B0 Installation of P bus server aborted. F360 06B1 Unknown message received from task. F560 06B2 Error occurred receiving a message. F360 Entering state: Power outage on P bus. F260

06B3 Exiting state: Power supply on P bus OK.

F360 Entering state: I/O disabled by CPU. F260

06B4 Exiting state: I/O enabled by CPU.

F560 06B5 Module on P bus not capable of communication. F960 06B6 Parity error in P bus communication. F960 06B7 Bit shift error in P bus communication. F360 06B8 Diagnostic interrupt cannot be sent. Module is not enabled on P bus. F360 06B9 Diagnostic interrupt cannot be sent. Diagnostic interrupt is not enabled on P bus. F360 06BA SDB0.SDB cannot be opened. File overwritten without comparison. F360 06BB SDB0.SDB cannot be created. F360 06BC SDB0.SDB cannot be written. F560 06BD BUS3-ASIC could not be initialized. F360 06BE SDB5.SDB cannot be opened. File overwritten without comparison. F360 06BF SDB5.SDB cannot be created. F360 06C0 SDB5.SDB cannot be written. Messages from the SDB handler F560 06E0 Installation of the SDB handler aborted. F560 06E1 SDB could not be copied. F560 06E2 SDB could not be deleted. F560 06E3 SDB could not be loaded. F560 06E4 SDB information of hierarchy 1 not available. F560 06E5 SDB information of hierarchy 2 not available. F560 06E6 SDB information of hierarchy 3 not available. F560 06E7 Error chaining SDBs. F360 06E8 SDB handler: Unknown job. F360 06E9 Control instruction unknown. F560 06EB Error occurred during firmware update. TD7onTIM messages F560 Entering state: TD7 installation started. F460

0700 Exiting state: TD7 installation ready.

F560 0701 Semaphores not created. F560 0702 Semaphores not created. F560 0703 SecIntervall task was not started. F560 0704 TD7_ObjectAdmin task was not started. F560 0705 The path for SDB files could not be opened. F560 0706 The TD7 SDB could not be found.



Event ID (hex)


Meaning

F560 0707 The TD7 SDB could not be opened. F560 0708 Header with incorrect length of block ID. F560 0709 TD7-SDB: No TD7 parameters found. F560 070A TD7-SDB: Block not found. F560 070B TD7-SDB: T4T_MAINHDR has incorrect length. F560 070C TD7-SDB: T4T_SUBDATA has incorrect length. F560 070E TD7-SDB: Unknown format in a destination subscriber block. F560 0711 TD7-SDB: Number of partner blocks incorrect. F560 0712 TD7-SDB: Unknown format in a partner block. F560 0713 TD7-SDB: Unknown channel type. F560 0715 TD7-Run: Not enough memory for the channel list. F560 0716 TD7-SDB: Channel block not found. F560 0717 TD7-Run: Not enough memory for a channel object. F560 0718 TD7-SDB: The number of data entries is incorrect. F560 071B TD7-SDB: The number of object entries is incorrect. F560 071C TD7-Par: Subscriber object for a partner not found. F560 071D TD7-Par: Unknown partner. F560 0721 TD7-Par: Invalid scan cycle ID. F560 0722 TD7-Run: Object not in fast cycle. F560 0725 TD7-SDB: No objects found in header ID. F560 0726 TD7-SDB: Unknown format in an object. F560 0729 TD7-Par: Not enough memory for scan cycle job list. F560 072A Basic channel memory assignment error. F560 072D TD7-Par: Wrong channel data type. F560 072E Unknown channel type. F560 0730 TD7-Par: Invalid scan cycle ID. F560 0731 Memory assignment error creating the object list for the current subscriber. F560 0732 TD7-SDB: Number of objects does not match the number of objects in the header. F560 0733 A read job to the CPU was not responded to after 1 ms. F560 0736 TD7-Com: CPU communication error in object X, channel Y. F560 0737 TD7-Com: CPU access error for object X, channel Y. F560 073B Memory assignment error creating the message buffer for a scan cycle. F560 073D A write job to the CPU was not responded to after 1 ms. F560 073E TD7-Com: Negative acknowledgment from LAN communication for job from scan cycle. F560 0742 TD7-Run: Error reading an input trigger. F560 0744 TD7-Par: Object without channels. F560 074A TD7-Par: Invalid address with trigger signal. F560 074B TD7-Par: Invalid address for net data in object X, channel Y. F560 074C An invalid address was reported for object X in channel Y. F560 0752 TD7-SDB: Number of subscriber blocks does not match main header entry. F560 0755 Unknown channel type.



Event ID (hex)


Meaning

F560 0759 Not enough memory to create the TD7onTIM send job list. F560 0760 Initialization of TD7onTIM for source subscriber complete. F560 0761 The general request of a subscriber is incomplete. F560 0762 Timeout in the general request to a subscriber. F560 0763 The general request of object X of a destination subscriber is incomplete. F560 0766 Message with unknown source subscriber. F560 0767 Unknown start index in received organizational message. F560 0768 TD7-Run: Received organizational message not accepted due to invalid length. F560 076C Invalid start index in received data message. F560 076D TD7-Run: Received data too large for destination object. F560 076E TD7-Run: Start index of received data message does not match the receive channel of the

destination object. F560 0773 TD7-Run: Object without partner or channels. F560 0774 TD7-Run: No destination object found.



Diagnostic messages and activation of the group error LED If an error occurs during startup, the read group LED (SF) of the TIM lights up and a message to this effect is entered in the diagnostic buffer of the TIM. If the TIM is installed as a CP in an S7-300 rack, a diagnostic interrupt is sent to the CPU. The following table contains a summary of all error messages that caused the group error LED (SF) to light up.

Table 4-20 Classification of the group error messages of the TIM

Error class Detailed event in the diagnostic message Internal error 0061h

0063h - 0067h 0069h 0078h - 0080h 0083h 06B0h

External error 0320h No parameter assignment: 0070h

0071h 0620h

Bad parameter assignment 0077h 0081h 0110h 0112h 0300h 031C 0500h 0620h

RAM error 0085h 0086h

SINAUT Diagnostics and Service tool 4.7 Messages in the diagnostic buffer of the CPU


4.7 Messages in the diagnostic buffer of the CPU

Introduction The SINAUT TD7onCPU software package generates a series of operating and error messages that are entered in the diagnostic buffer of the CPU. These can be displayed in SINAUT / TD7 CPU Diagnostics. If a PG is connected and if this is registered for CP messages, these diagnostic messages are displayed on the PG immediately when they arise. The messages generated by TD7 are, however, only displayed in plain text when they are called up in SINAUT / TD7 CPU Diagnostics. If you call up the messages generated by TD7 in STEP 7 Diagnostics / Module Information, Diagnostic Buffer tab, they are displayed in hexadecimal format.

Note If there is no text file with the diagnostic texts of the TD7 events on the PG with which the diagnostic buffer is read out, the events are displayed in hexadecimal format. Based on the following list, you can identify the significance.

4.7.1 SINAUT diagnostic messages of TD7onCPU

Classification of TD7 messages The TD7onCPU software package uses the numeric range of event class B for its diagnostic messages. This event class is reserved for user-defined events in STEP 7. It is, however, used in SINAUT ST7 for SINAUT diagnostic messages.

Note In SINAUT ST7, the user can only use event class A for user-defined diagnostic messages. Just as in event class B, this is also reserved for user-defined messages in STEP 7.

The SINAUT diagnostic messages of TD7onCPU use the range from Bx00h to BxFFh. To distinguish the individual messages, only in the last two numbers are significant, in other words the range from 00h to FFh. x is a placeholder for an ID that allows the global classification of messages. For the TD7 diagnostic messages, the IDs 0 and 1 are used for events exiting state (0) and entering state (1).

Table 4-21 Global classification of the SINAUT diagnostic messages of TD7onCPU

ID x Resulting event IDs Classification 0 B000h ... B0FFh Exiting state messages 1 B100h ... B1FFh Entering state messages

Most messages are entering state, only a few are existing state.



The TD7 diagnostic messages in hexadecimal and plain text format The following table shows or SINAUT TD7 diagnostic messages according to their event IDs numbers in ascending order in hexadecimal format. Most diagnostic messages have additional information added to them. If the diagnostic messages are displayed as text, this additional information is included in the texts suitably formatted. In the explanations below, this additional information is specified within the texts as [Info1] or [Info2/3]. If the texts are not shown, the additional information is shown as 'Additional info 1 / 2 / 3' in the hexadecimal representation on the PG.

Table 4-22 SINAUT diagnostic messages of TD7onCPU

No. Event ID (hex)

Meaning

Parameter assignment errors, configuration errors 0 B100 Parameter assignment error for object no. [Info1]: PartnerNo [Info2/3] not permitted. 1 B101 Parameter assignment error for object no. [Info1]: PartnerNo [Info2/3] unknown. 2 B102 Parameter assignment error for object no. [Info1]: PartnerObjectNo [Info2/3] not permitted. 3 B103 Parameter assignment error for object no. [Info1]: ST1 message no. [Info2/3] not permitted. 4 B104 Parameter assignment error for object no. [Info1]: ST1 object no. [Info2/3] not permitted. 5 B105 Parameter assignment error for object no. [Info1]: ST1 index no. [Info2/3] not permitted. 6 B106 Parameter assignment error for object no. [Info1]: ST1 PACK value [Info2/3] not permitted. 7 B107 Errors generating the object reference list: DB[Info1] cannot be created. Cause: [Info2/3]. 8 B108 Parameter assignment errors in the object reference list: Reference to subscriber no. [Info1] and

object no. [Info2/3] exists more than once. 9 B109 Object reference list 1 missing. Searching for reference to subscriber no. [Info1] and object no.

[Info2/3]. 10 B10A Object reference list 2 missing. Searching for reference to subscriber no. [Info1] and object no.

[Info2/3]. 11 B10B Parameter assignment errors in object reference list 1: Reference to subscriber no. [Info1] and

object no. [Info2/3] missing. 12 B10C Parameter assignment errors in object reference list 2: Reference to subscriber no. [Info1] and

object no. [Info2/3] missing. 13 B10D Error in object DB no. [Info1]: SINAUT ST7 ID A5h missing. 14 B10E Configuration error: No subscriber contained in DB BasicData (DB[Info1]) . 15 B10F Unknown connection type for connection no. [Info1] to local subscriber no. [Info2/3]. 16 B110 Unknown subscriber type (= [Info1]) for subscriber no. [Info2/3]. 17 B111 Data received from an unknown local communication partner (MPI no. = [Info2/3]). 18 B112 In the send buffer of communication DB no. [Info1], an org. message with an unknown destination

subscriber (= [Info2/3]) was deleted. 19 B113 Parameter assignment error for FC [Info1] in parameter [Info2/3]. 20 B114 Parameter assignment error object no. [Info1] in parameter [Info2/3]. Reception errors 32 B120 Content of receive buffer in communication DB no. [Info1] not plausible: Length of a message

greater than the maximum receive length of [Info2/3] bytes. 33 B121 Content of receive buffer in communication DB no. [Info1] not plausible: Length of a message = 0.



No. Event ID (hex)

Meaning

34 B122 Content of receive buffer in communication DB no. [Info1] not plausible: Length of all messages greater than length of the receive data block.

35 B123 Received message in communication DB no. [Info1] incorrect: too many destination subscribers (= [Info2/3]).

36 B124 Received message in communication DB no. [Info1] incorrect: Subscriber no. too long (L = [Info2/3]).

37 B125 Org. Received message in communication DB no. [Info1] incorrect: Number of destination subscribers (= [Info2/3]) must be 1.

38 B126 Org. Received message in communication DB no. [Info1] incorrect: Address extension not permitted (AE = [Info2/3]).

39 B127 Received message in communication DB no. [Info1] incorrect: Address extension not permitted (AE = [Info2/3]).

40 B128 Org. Received message in communication DB no. [Info1] incorrect: Destination object no. (= [Info2/3]) not permitted (only 1 ... 32000 or 32767).

41 B129 Org. Received message (ST1) in communication DB no. [Info1] incorrect: Source object no. (= [Info2/3]) not permitted (only 0 or 32767).

42 B12A Org. Received message for object no. [Info2/3] incorrect: Start index is >< 0. Current communication DB = DB[Info1].

43 B12B Org. Received message for object no. [Info2/3] incorrect: Number of net received bytes is > 2. Current communication DB = DB[Info1].

44 B12C Received message for object no. [Info2/3] incorrect: Too many net received bytes. Current communication DB = DB[Info1].

45 B12D Org. Received message for subscriber object no. [Info2/3] incorrect: Subscriber unknown. Current communication DB = DB[Info1].

46 B12E Org. received message for subscriber object no. [Info2/3] incorrect: Too many net received bytes. Current communication DB = DB[Info1].

47 B12F Received message for object no. [Info1] incorrect: Source subscriber no. [Info2/3] unknown. 48 B130 Received message for object no. [Info1] rejected: Source subscriber no. [Info2/3] incorrect. 49 B131 Received message for object no. [Info1] rejected: Source object no. [Info2/3] incorrect. 50 B132 Short Message Service (SMS): Status return message for object no. [Info1] from SMS control

center subscriber no. [Info2/3] cannot be interpreted. 51 B133 Short Message Service (SMS): Status return message for object no. [Info1] contains unknown

status no. [Info2/3] 52 B134 Received message in communication DB no. [Info1] incorrect: Index no. is negative 53 B135 Org. Received message in communication DB no. [Info1] incorrect: The block length [Info2] of the

org. section is not plausible. 54 B136 The receive error was detected by the TIM with subsbcriber number [Info1] when reading the data

record. TIM error code = [Info2]. 55 B137 A receive error occurred when the TIM with subsbcriber number [Info1] was reading the data

record. An unexpected status = [Info2] was read in from the TIM I/O. 56 B138 A receive error occurred when the TIM with the subsbcriber number [Info1] was reading the data

record. The length [Info2] of the indicated receive block is not permitted. 57 B139 A receive error occurred when the TIM with the subsbcriber number [Info1] was reading the data

record. The actual data record length differs by [Info2] bytes from the indicated data record length. 58 B13A A receive error occurred when the TIM with the subsbcriber number [Info1] was reading the data

record. Error code (SFC RD_REC) = [Info2].



No. Event ID (hex)

Meaning

Send errors 64 B140 Content of send buffer in communication DB no. [Info1] not plausible: Length of a send message

too short: [Info2/3] bytes. 65 B141 Content of send buffer in communication DB no. [Info1] not plausible: Length of a send message

too long: [Info2/3] bytes. 66 B142 Content of send buffer in communication DB no. [Info1] not plausible: A sender message longer

than the send buffer length: [Info2/3] bytes. 67 B143 Content of send buffer in communication DB no. [Info1] not plausible: Length of a send message

odd: [Info2/3] bytes. 68 B144 Content of send buffer in communication DB no. [Info1] not plausible: Sum of all send message

lengths incorrect: [Info2/3] bytes. 69 B145 Data message from object no. [Info1] to destination subscriber no. [Info2/3] could not be entered in

the communication DB. 70 B146 Organisational message from object no. [Info1] to destination subscriber no. [Info2/3] could not be

entered in the communication DB. 71 B147 Short Message Service (SMS): Monitoring time elapsed for SMS message no. [Info1] sent over

SMS control center subscriber no. [Info2/3]. No repetition. B148 Entering state: Short Message Service (SMS): Monitoring time elapsed for SMS message no.

[Info1] sent over SMS control center subscriber no. [Info2/3]. Being repeated with backup mobile phone no.

72

B048 Exiting state: Short Message Service (SMS): SMS message no. [Info1] sent over SMS control center subscriber no. [Info2/3] could be delivered after repetition.

73 B149 Short Message Service (SMS): SMS message no. [Info1] was deleted because object no. [Info2/3] is disabled.

74 B14A Short Message Service (SMS): Monitoring time elapsed for send job from object no. [Info1] sent to SMS control center subscriber no. [Info2/3].

75 B14B The send error was detected when writing the data record to the TIM with subsbcriber number [Info1]. Error code (SFC WR_REC) = [Info2].

76 B14C The send error was detected when writing the data record by the TIM with subsbcriber number [Info1]. TIM error code = [Info2].

Connection displays B150 Entering state: Connection to local subscriber no. [Info1] disrupted. 80 B050 Exiting state: Connection to local subscriber no. [Info1] OK. B151 Entering state: Subscriber no. [Info1] disrupted. 81 B051 Exiting state: Subscriber no. [Info1] OK.

82 B152 Monitoring time for send job on local subscriber no. [Info1] elapsed. [Info2] = 0: The job could not be completed in time. [Info2] = 1: The job could not be started in time. [Info2] > 1: No. of the communication DB.

83 B153 Send job on local subscriber no. [Info1] failed. The job will be repeated. Communication DB no. = [Info2].

84 B154 Monitoring time for receive job from local subscriber no. [Info1] elapsed. [Info2] = 0: The job could not be completed in time. [Info2] = 1: The job could not be started in time.

85 B155 Receive job of local subscriber no. [Info1] failed. The job will be repeated. Communication DB no. = [Info2].



No. Event ID (hex)

Meaning

Request displays 96 B160 General request to subscriber no. [Info1] incomplete. 97 B161 Single request to subscriber no. [Info1] incomplete. 98 B162 Error in general request to object no. [Info1]. Source subscriber no. = [Info2/3]. 99 B163 Error in single request to object no. [Info1]. Source subscriber no. = [Info2/3]. Command/setpoint displays 112 B170 Command input error for object no. [Info1]: Simultaneous input over hardware and software input. 113 B171 Command input error for object no. [Info1]: 1-out-of-8 error. 114 B172 Command/setpoint input error for object no. [Info1]: 1-out-of-n error. Additional info: [Info2/3] (0 =

Comm. or Setp.; 1 = Comm.; 2 = Setp.) 115 B173 Command output error for object no. [Info1]: Command and control byte not identical. 116 B174 Command output error for object no. [Info1]: 1-out-of-8 error. 117 B175 Command output error for object no. [Info1]: 1-out-of-n error. Time displays 128 B180 Daylight saving/standard time changeover at change of day not permitted. 129 B181 Date/time error when setting the CPU clock. Incorrect date: [Info1]. 130 B182 Date/time error when setting the CPU clock. Incorrect time: [Info2/3]. 131 B183 Time synchronization disrupted on CPU. Processing errors 144 B190 Data loss in object no. [Info1]. Last received data was not processed by typical. 145 B191 Received data loss in subscriber object no. [Info1]. Last received data was not processed by

BasicTask. Operating displays 160 B1A0 Initialization of subscriber no. [Info1] completed.


SINAUT PG Routing 55.1 What is PG Routing?

5.1.1 Introduction In the SIMATIC world, the term routing is defined as follows: Routing is finding the path for information beyond network boundaries In the SIMATIC world at the present time, it is not possible to configure a connection over which data can be transmitted between the two endpoints involved if this connection goes beyond the boundaries of a network. What is possible, however, is PG routing. Using the PG routing, it is possible to access a programmable module or a module with diagnostic capability beyond network boundaries from a programming device (PG) or computer (PC).

SIMATIC PG routing and SINAUT PG routing PG routing allows any type of diagnostics with diagnostics-compliant modules. Test, commissioning, and service functions can be executed, such as opening blocks online, monitoring, editing and overwriting or changing the operating mode mode of modules. SIMATIC PG routing SIMATIC PG routing is possible only over network types such as MPI, PROFIBUS, and Ethernet. SIMATIC PG routing was released with STEP 7 V5.0. SINAUT PG routing Expanding SIMATIC PG routing, SINAUT PG routing also works over SINAUT networks; in other words, in WANs. In terms of functionality, SIMATIC PG routing and SINAUT PG routing are largely identical with the only difference being that SINAUT PG routing also functions beyond the boundaries of SINAUT networks. This gives the user a convenient option of remote programming and remote diagnostics over the company telecontrol network.



Note In the remainder of this chapter, the terms PG routing and remote are used with the following meaning: • PG routing

PG routing is PG routing over network types such as MPI, PROFIBUS, and Ethernet as well as SINAUT networks.

• Remote A remote CPU or remote TIM is a module that can be accessed from a PG over SINAUT telecontrol networks.

5.1.2 Examples of configuration for PG routing The following figures illustrate the basic principle of PG routing based on configurations.

Basic configuration of PG routing In the basic configuration, a PG in the master station is configured and connected to the MPI bus. PG routing extends from the master TIM over a SINAUT network (WAN) to a station TIM over which the CPU connected to it can be reached.

Figure 5-1 Basic configuration of PG routing



PG routing from a SINAUT ST7cc control center with SIMATIC STEP 7 In this case, PG routing does not extend from a PG in the master station but from a central SINAUT ST7cc control system connected to the MPI bus of the master TIM. The routing path shown here is basically the same as described in the basic configuration with a centrally configured PG. A SINAUT system configuration equipped with SINAUT ST7cc as the central control system already has the full range of functions of PG routing if SIMATIC STEP 7 is also installed alongside the SINAUT ST7cc software. PG routing is then activated in any case. This means that no further preparations are necessary for PG routing to be able to use the parameter assignment, diagnostics, and service functions for remote subscribers over SINAUT networks. For this configuration, PG routing extends from the PC with the STEP 7 software over the master TIM and a SINAUT network to a SINAUT station where both the station TIM and the CPU can be accessed.

Figure 5-2 PG routing from a SINAUT ST7cc control center with SIMATIC STEP 7

Indirect PG routing over remote PC / laptop with remote access The configuration below is initially the same as with the central SINAUT ST7cc control system. PG routing, in this case, is used with a remote PC connected over the telephone/ISDN network. With the aid of remote access software, a connection is established to the PC in the master station so that this can be controlled by the remote PC / laptop over the telephone/ISDN connection. From there, PG routing extends over the master TIM and a SINAUT network to a SINAUT station where both the station TIM and the CPU can be accessed. Various products, such as Symantec pcAnywhere are available on the market and can be used as remote access software.



Figure 5-3 Indirect PG routing over a remote PC / laptop with remote access

Indirect PG routing over remote PG/PC with SIMATIC STEP 7 The basic configuration with a configured PG in the master station can be expanded by a teleservice adapter. The PG is configured and connected to the MPI bus in the master station. The teleservice adapter allows the PG to be located remotely and connected over a telephone/ISDN network. As a result, the MPI bus in the master station is extended over a modem connection. In this case, PG routing extends from the PG with the SIMATIC STEP 7 software package over the modem connection, the master TIM and a SINAUT network to a SINAUT station where both the station TIM and the CPU can be accessed.

Figure 5-4 Indirect PG routing over a remote PG/PC with SIMATIC STEP 7



5.1.3 Range of functions of PG routing

Range of functions of PG routing SINAUT ST7 allows configuration of simple and complex networks. For PG routing, this means that the access to remote TIM and CPU modules always follows the hierarchical arrangement of a communication network "from top to bottom"; in other words from a master station to the node station or station. On the communication link, the following three levels are therefore significant:

Table 5-1 Communication path of PG routing

Starting point Intermediate point Target PG/PC on the MPI bus of the master TIM

TIM modules in a node station (possibly cascaded)

Station TIM or station CPU

The following table shows the starting point and the communication paths leading to the target with which PG routing functions.

Table 5-2 Overview of routing-compliant communication paths

Starting point over Intermediate point over Target Master station - - D Station Master station - - DT Station Master station - - DMT Station Master station - - DN Station Master station - - SPN Station Master station - - D Node station Master station - - DT Node station Master station - - DMT Node station Master station - - DN Node station Master station - - SPN Node station Node station - - D Station Node station - - DT Station Node station - - DMT Station Node station - - DN Station Node station - - SPN Station Master station D Node station D Station Master station D Node station DN Station Master station DN Node station D Station Master station DMT Node station D Station



Table 5-3 Abbreviations/acronyms:

Network type / mode D Dedicated line / polling DT Dedicated line / polling with time slots DMT Dedicated line / Multi-master polling with time slots DN Dial-up network / spontaneous mode SPN Spontaneous network / spontaneous mode

5.1.4 Properties and restrictions of PG routing When using PG routing with the SINAUT Diagnostics and Service tool or the SIMATIC Manager, certain special features and restrictions to the functions must be kept in mind.

Functions of the SINAUT Diagnostics and Service tool with PG routing ● TIM Message Monitor function

Activating the TIM message monitor on a remote TIM using PG routing is not possible. ● Firmware update function

When using the Firmware update function, remember that large amounts of data are transferred. With remote modules, long processing times of several minutes can occur.

● Repair function The repair function must not be used over PG routing. If you use the repair function, the flash disk of the TIM is formatted and the software completely deleted on the TIM. Following this, the module is no longer accessible over the SINAUT network. Reloading the TIM software is then only possible locally over the MPI bus.

Functions of the SIMATIC Manager with PG routing ● Display Accessible nodes function

The display Accessible nodes function is available only for subscribers connected to the local MPI bus. This restriction applies to SIMATIC PG routing and therefore also to SINAUT PG routing.

● Hardware diagnostics function The hardware diagnostics function is available only for subscribers connected to the local MPI bus. This restriction applies to SIMATIC PG routing and therefore also to SINAUT PG routing.

● Download function The download of an entire station (CPU 300 plus TIM) leads to a connection abort. Since the TIM system data are downloaded first followed by a restart on the TIM, the second step of the CPU data download is interrupted. It is possible to repeat the CPU download. We, nevertheless, recommend that you download the block folder of the CPU and the TIM module separately.

● Upload to PG function The upload to PG function is available only for subscribers connected to the local MPI bus. This restriction applies to SIMATIC PG routing and therefore also to SINAUT PG routing.

SINAUT PG Routing 5.2 System requirements for PG routing


Restrictions for PG routing with SINAUT ST1 components In the following situations, PG routing is not supported in ● SINAUT ST1 stations ● SINAUT networks with ST1 protocol ● SINAUT ST7 stations that operate with the SINAUT ST1 protocol.

5.2 System requirements for PG routing

Introduction To use the PG routing function in the SINAUT telecontrol network with SINAUT ST7, the following requirements must be met or preparations made. ● STEP 7 with at least Version 5.1 and service pack 3 is required on the PG/PC. ● The SINAUT software package version V3.0 or higher must be installed on your PG/PC. ● The RMOS operating system of the TIM modules of the type TIM 3 and TIM 4 in your

telecontrol network should be at least version 2.14. TIM modules of version 2.04 can be used with certain restrictions.

● The TIM firmware for the TIM 3 and TIM 4 must have a certain minimum version. With dedicated lines, firmware version V 3.14 is required. In dial-up networks, a minimum firmware version of V 3.46 is required.

● For SINAUT dedicated line or dial-up networks, a maximum message length of 240 must be set.

● On slow connections with only 1200 bauds transmission speed, the Retry factor must be set higher than 0.

● For PG routing, new SDBs must be transferred to the TIM modules. These are compiled with the SINAUT software package as of V3.0.

Note PG routing is released for the Ethernet TIMs regardless of the firmware version.

5.2.1 STEP 7 STEP 7 at least version 5.1,service pack 3 must be installed on your PG/PC. Only then is your PG/PC capable of routing and it is guaranteed that the routing SDBs are compiled with the correct content.



5.2.2 The SINAUT software package The routing SDB (SDB type 3002) can only be compiled for the TIM modules with the SINAUT software package as of the version V 3.0. The LAN SDB (SDB type 3201) also includes extra parameters required for PG routing. PG routing can only be used over TIM modules on which these routing and LAN SDBs are loaded.

Note The routing-SDB (SDB type 3002) is compiled only for TIM modules that actually require this information. No routing SDB is compiled for a TIM installed as a CP in an S7-300 station if there is no local network such as MPI bus or PROFIBUS DP in this station. The absence of the routing SDB in the SDB directory is not, in this case, a compilation error. Although the routing SDB is missing, this TIM and the connected S7-300 CPU can be accessed using PG routing.

Table 5-4 Overview of the SDBs

SDB type Contents 0 Standard SIMATIC SDB 700 Communication function block connection parameter 3002 Routing SDB 3201 LAN data 3202 WAN data 3203 SINAUT subscriber data 3205 Parameter for X connection

Apart from SDB type 0, the SDBs of the type 3201, 3202, 3203 and 3205 are always compiled for the TIM, the SDB types 700 and 3002, on the other hand, only when necessary.

5.2.3 RMOS operating system of the TIM 3 / TIM 4 Whether a TIM of the type TIM 3 or TIM 4 is suitable for PG routing, depends, among other things, on the version of the RMOS operating system of the TIM. In this respect, there are versions ideally suited for PG routing and versions that mean certain restrictions: ● TIM modules with an RMOS version older than 2.04 are not routing-compliant. ● TIM modules with an RMOS version as of 2.04 are routing-compliant but involve

restrictions regarding the number of remote subnets. No more than 10 remote subnets may be configured in the SINAUT project.

● TIM modules with an RMOS version as of 2.08 are routing-compliant but involve restrictions regarding the number of remote subnets. No more than 20 remote subnets may be configured in the SINAUT project.

● TIM modules with an RMOS version as of 2.04 are fully routing-compliant. The operating system of the TIM modules can be upgraded to the current version. A special cable is required for this. This can be borrowed from the hotline. Along with the cable, the current version of the operating system is supplied on diskette with instructions on upgrading using a PG/PC.



5.2.4 TIM firmware for TIM 3 / TIM 4 Not only the version of the operating system but also the version of the TIM firmware for TIM types TIM 3 and TIM 4 decides whether a TIM is suitable for PG routing. In this respect, there are versions ideally suited for PG routing and earlier versions that mean certain restrictions: For PG routing, a TIM firmware version of V 3.46 is generally recommended. It depends on the driver activated on the TIM (dedicated line or dial-up network driver) whether an older version will be adequate. PG routing over the dedicated line driver is possible as of firmware version V 3.14. If the dial-up network driver is activated on a TIM module, firmware version V 3.46 or higher must be installed.

5.2.5 Settings for SINAUT networks

Retry factor and maximum message length PG routing can only be used when the maximum message length network parameter for the SINAUT networks is set to a maximum of 240. Since this value is normally entered as default in the Properties dialog for SINAUT networks, this is normally already set. If a transmission speed of 1200 bauds is set in a SINAUT network, make sure that the retry factor is higher than 0. We recommend that you use the default values available for the retry factor in the configuration dialogs: ● For dedicated lines: 3 ● For dial-up networks: 7

5.2.6 Recompiling system blocks If you want to enable PG routing in an existing SINAUT ST7 system, the project must be recompiled in the subscriber management of the SINAUT configuration tool (as of V 3.0). It is adequate to simply recompile the new SDBs there. The programs for CPU modules do not change for PG routing. After compiling the SDBs, the entire SINAUT system configuration must be downloaded and activated on the TIM modules.

5.2.7 Downloading newly compiled SDBs to TIM modules If new SDBs have been compiled for an existing SINAUT ST7 system, they must then be downloaded to the relevant TIM modules of the system. Without PG routing, SDBs are downloaded locally to each TIM of the MPI bus. A further option for downloading SDBs from the master station to the remote TIM modules is described in the section Central SDB downloading with PG routing.



Note The new system data blocks are downloaded to a TIM module using the SINAUT Diagnostics and Service tool function Download SDBs. You will find more detailed information there.

To activate newly downloaded SDBs on a TIM module, the TIM must be restarted. The consequences of restarting a TIM module are, however, as follows: ● The connection from the PG to the TIM is terminated. ● The connections from the TIM to other SINAUT partners (SINAUT connections) are

terminated. This leads to error messages on the partners of the TIM module. ● In the case of a node TIM, the connections to the downstream stations are also reported

as being disrupted. ● With a node TIM, any data messages stored on the TIM are lost during the restart. This is

particularly relevant in station TIMs in the dial-up network. When downloading SDBs to TIM modules, you should therefore note the following points: ● Before you transfer the SDBs, you should give the TIM the opportunity of transferring any

messages stored on it. ● After restarting the TIM, the SINAUT connections are automatically re-established. If the

connection from the PG to the TIM is required, however, it must be activated from the PG of the user.

5.2.8 Central SDB download using PG routing SDBs can be downloaded as previously for each TIM locally over the MPI bus. It is, however, conceivable to perform this from the master station; in other words, to use the options of PG routing although the system was not activated for this function. This method can be considered if you already know that the TIM modules in the stations are suitable or prepared for PG routing in terms of the operating system and TIM firmware. In the following sample configuration, the central downloading and activation of the SDBs is performed in four consecutive steps: Step 1: First download the newly compiled SDBs to the TIM module in the master station (in the illustrated example, this is TIM 4 a) and then activate the SDBs by restarting the TIM module. TIM 4 is now routing-compliant. Repeat this procedure for all TIM modules in the master station if there is more than one TIM module.



Figure 5-5 Step 1 of central SDB download in the sample configuration

Over the now routing-compliant master TIM 4, the PG now has access to all station or node TIM modules connected directly to this master TIM over WAN a and WAN b. In the example, the PG can reach both TIM 4 b and TIM 3 a TIM modules over WAN but not the local CPU modules, the TIM 4 c of the node station. Since the two TIM modules TIM 4 b and TIM 3 a are now accessible, the PG can run the diagnostics and service functions for both these TIM modules. This means that SDBs can also be transferred to these two TIM modules by the PG. Step 2: Download the newly compiled SDBs to the TIM modules TIM 4 b and TIM 3 a and then activate the SDBs by running a restart on the two TIM modules. TIM 4 b and TIM 3 a are now routing-compliant.




Over the two routing-compliant modules TIM 4 b and TIM 3 a, the PG can now access all locally connected CPU and TIM modules. All CPU and TIM modules connected to a routing-compliant TIM over the backplane bus (with S7-300), over MPI, or over WAN are counted as local. In the example, the PG can now reach the following CPU and TIM modules: ● In the stations, the CPUs connected to TIM 3 a over the backplane bus. ● In the node station, the CPU and the TIM 4 c over MPI, the station TIM 3 b connected to

TIM 4 b over WAN c, but not the local CPU there. The reachable CPU modules can now be remotely programmed. The PG can once again perform all the diagnostics and service functions for the two newly reachable TIM modules TIM 4 c and TIM 3 b. The PG can therefore also transfer SDBs to these TIM modules. Step 3: Download the newly compiled SDBs to the TIM modules TIM 4 b and TIM 3 a and then activate the SDBs by running a restart on the two TIM modules. TIM 4 c and TIM 3 b are now routing-compliant.




Over the two routing-compliant modules TIM 4 c and TIM 3 b, the PG can now access all locally connected CPU and TIM modules. In the example, the PG can now reach the following CPU and TIM modules: ● In the stations, the CPUs connected to TIM 3 b over the backplane bus. ● The station TIM 3 c, connected over WAN d to the TIM 4 c in the node station, but the

CPU connected locally to TIM 3 c in the station not yet. The reachable CPU module can now be remotely programmed. The PG can once again perform all the diagnostics and service functions for the newly reachable TIM module. The PG can therefore also transfer SDBs to this TIM module. Step 4: Download the newly compiled SDBs to the TIM module TIM 3 c and then activate the SDBs by running a restart on the TIM module.

SINAUT PG Routing 5.3 Application of PG routing



TIM 3 c is now also routing-compliant. The CPU module attached to TIM 3 b can now be remotely programmed.

5.3 Application of PG routing Before you perform PG routing over the SINAUT telecontrol network with your PG of PC, you must first adapt the properties of the PG/PC interface and set the assignment of the PG/PC in the SINAUT network.

5.3.1 Properties of the PG/PC interface

Adapting the PG/PC interface 1. Open the Control Panel window by clicking on the Start / Settings / Control Panel menu. 2. Select the Set PG/PC interface icon. 3. In the Set PG/PC Interface dialog, set the MPI interface in the Interface parameter

assignment used field. 4. Then click on the Properties button. 5. Confirm the warning dialog with Yes. The Properties dialog opens. 6. In the MPI tab of the Properties dialog, select the option 100 s in the Timeout list. 7. Close the Properties and Set PG/PC Interface dialogs with the OK button and then close

the Control Panel window.



Figure 5-9 Properties dialog of the interface in the Control Panel

This completes the adaptation of the PG/PC interface.

5.3.2 PG/PC assignment in the SINAUT network Before you can use PG routing with a PG/PC over SINAUT networks, this must be configured and assigned within a SINAUT project.

Assigning the PG/PC The PG/PC is assigned in the network using the SIMATIC network configuration tool NetPro. 1. Open the project in which you want to use PG routing in the SIMATIC STEP 7 NetPro

network configuration tool. 2. Open the NetPro catalog if it is not already open. 3. Drag a PG/PC to the network window from the NetPro catalog directory Stations and

place it at a suitable position. 4. Right-click on the PG/PC you have just installed. A context menu opens. 5. In the context menu, click on the Assign PG/PC option. The Properties dialog opens. 6. Select the MPI network to which the configured PG/PC is connected in the Configured

interface field of the Properties dialog.



Figure 5-10 Properties - PG/PG dialog / Assignment tab in NetPro

7. Select the MPI interface you want to use in the Interface Parameter Assignments in the PG/PC.

8. Click on Assign. The assigned MPI interface is displayed in the Assigned box. The interface is now enabled for PG routing access.

9. Close the dialog with the OK button. The successful assignment of the PG/PC is indicated by an MPI connection on a yellow background and a yellow arrow pointing upwards in the PG/PC icon in NetPro and in the SIMATIC Manager.

10. Save your project in NetPro. 11. Connect your PG/PC to the MPI bus to which you assigned your PG/PC in NetPro over a

PG cable.



Figure 5-11 Project view in NetPro with assigned PG/PC

Note As long as you leave your PG/PC connected to the point in the network as you assigned it in NetPro, you do not need to cancel the assignment. Not even if you want to turn off the PG/PC. Each time you turn on the PG/PC and open the project, you can use PG routing again immediately. You do not need to make settings or assignments again. If, on the other hand, your PG/PC is not always at the same location or if you change to different projects on your PG/PC, we strongly recommend that you always cancel the assignment before your PG/PC is turned off or before you change to a different project. This ensures that the PG/PC can be assigned again when used at a different location or in a different project.

5.3.3 PG routing in dial-up networks There are PG functions that maintain constant message traffic with the CPU or the TIM after they have started because these functions want to update themselves constantly. Such a function in a dial-up network would lead to a permanent connection with the relevant station until you deselect the function.



Other PG functions execute only once. They do not need constant updating. In a dial-up network, in this case, the dial-up connection is established briefly and then terminated again. If a continuous connection to a dial-up station is required with PG routing, it is advisable to start a PG function at the beginning that requires constant updating regardless of the actual PG function that has just been activated. This function should then be maintained while PG routing is being used thus forcing a permanent connection. At the same time, other PG functions can be performed. The PG function most suitable for maintaining a permanent connection is the Operating mode function. This requires little time to execute and the load on the other data traffic caused by the constant updating is only minimal. Other suitable functions include Module Information and Set Time of Day. PG routing places load on the transfer of process data; in other words, this data is transferred to the control center while the PG connection is established. This will will be slower than when no PG routing is activated. On the other hand, the parallel transmission of data messages also slows down the reactions to PG functions that have started. This is particularly the case when the station TIM is currently being used for PG routing and this TIM has a lot of stored messages, PG routing will be very slow at the beginning. It is therefore advisable to give the station TIM the opportunity to transfer its messages before intensive PG functions are started.

5.3.4 Canceling the PG/PC attachment in the SINAUT network

Canceling the PG/PC assignment If a PG was assigned in a project and then needs to be used at a different location, for example locally connected directly to a CPU or TIM, the assignment must first be canceled. Follow the steps outlined below: 1. Right-click on the PG/PC that is still assigned in the project you have opened in NetPro. 2. In the context menu that opens, select Cancel PG/PC Assignment. 3. Acknowledge the warning dialog with OK.

The PG/PC assignment is now canceled, this is indicated as follows in the network image of NetPro: – The connecting line from the PG/PC to the MPI bus is no longer on a yellow

background. – The yellow arrow in the PG/PC icon disappears

4. Save your project in NetPro.


Glossary

Alarm logging (runtime) Alarm Logging controls the acquisition and archiving of events and provides display and operator input options. Using the message blocks, message class and message type structure elements, the configuration engineer can class the events according to their significance and allow the operator a fast evaluation of the status of the system.

Analog value An analog value is an analog process variable such as pressure, temperature etc. It is acquired over an analog input as a current or voltage value and converted by this module to a binary-coded value. In total, the converted value occupies 1 word; in other words, 16 bits including sign bit.

Automation program The automation program is the program section on the CPU that monitors and controls the technological process.

COM port RS-232 is a standard for serial (i.e. bit-by bit) data transmission with +12 V and -12 V signals. RS-232 is a Recommended Standard of the Electronic Industries Association. For the RS-232 interface, 9-pin and 25-pin connections with D-sub connectors are normal. These are sub-miniature connectors with a D-shaped face.

Command A command is binary information that is transferred once when there is a signal change from 0 to 1. The trailing edge from 1 to 0 does not trigger transmission again. At the receiving end, a command is either output as a pulse (selectable duration) or it is reset by the local user program after it is has been executed. 8 commands are put together to form a byte. When inputting and outputting commands, reliability and safety are important. At the input end, for example, there is a check to determine whether only one command is pending at the time of acquisition (1-out-of-n check). Only then is the transmission triggered. If several commands are pending at the same time, an error is detected. There is no transmission. To transmit 1 command byte, a total of 1 word is used: One "original" command byte and a copy. At the receiving end, a command is only output when the "original" command byte and the copy have the identical content and when only 1 command was received (once again a 1-out-of-n check).

Glossary


Configuration During configuration, communication- and connection-specific system settings are made for each device.

Counted value A counted value (for example amount of flow) is acquired over a digital input as a pulse train and totaled to produce a binary-coded value. A counted value is 2 words: 28 bits for the binary-coded value 4 display bits.

CP Communications processor

CPU (Central Processing Unit) The CPU handles the central sequential control and coordination of all activities of the module.

CSD (Circuit Switched Data) Service in GSM for wireless transmission of data at 9600 bps full duplex. Connections can be established to other GSM devices, to analog modems or to ISDN modems in the fixed network. The connection establishment can be started at both ends. Only dial-up connections are supported.

Data manager The accrued data is managed by the data manager in WinCC. The data manager works with data created in the WinCC project and data stored in the project database. It handles the entire management of WinCC tags while WinCC is in runtime mode. All WinCC applications request the data from the data manager in the form of WinCC tags. These applications include Graphics Runtime, Alarm Logging Runtime and Tag Logging Runtime. To allow WinCC to communicate with the widest variety of data sources (programmable controllers, ST7cc servers etc.), various communications drivers are used. A communications driver is a C++ DLL that communicates with the data manager over a specified interface known as the channel API. The WinCC tags are supplied with process values over the communications driver.

Data messages The actual transmission of data takes the form of data messages. These contain a fixed amount of a specific information type. There are status messages, analog value messages, counted value messages, command messages, setpoint messages, parameter messages and data messages for the various information types.

Glossary


DCF77 radio clock DCF77 is a time signal transmitted on the normal frequency 77.5 kHz as encoded time information. Reception of the time signal is restricted to Western Europe. Some TIM variants (TIM 4VD, TIM 42D, TIM 43D, TIM 44D, TIM 4RD) are equipped with a DCF77 receiver module that can receive the DCF77 time signal either over an indoor or outdoor antenna. The ST7 time management currently requires the existence of a DCF77 time signal to allow time synchronization of the stations and the control center throughout a network. For applications that cannot receive the DCF77 time signal, SINAUT provides a GPS receiver module with a GPS outdoor antenna that converts the GPS Time signal for the DCF77 receiver module.

Ethernet / Industrial Ethernet Industrial Ethernet is a powerful communication network complying with the international standard IEEE802.3 (Ethernet) that was optimized to meet the requirements of industrial application. Ethernet is designed with a linear or star topology. The transmission media are shielded coaxial cables, twisted pair, or fiber-optic cables. SIMATIC NET Industrial Ethernet uses both the Ethernet and Fast Ethernet standards.

Ethernet TIM A TIM module of the type TIM 3V-IE, TIM 3V-IE Advanced or TIM 4R-IE.

Firewall A firewall is a network component via which a secure network can be linked with an unsecure network. The task of a firewall is to control data exchange between the networks.

General request (GR) With a general request, the master station can update itself. All messages and the current content are requested from the stations. This allows the master station to obtain an up-to-date process image.

Global Script (Runtime) The term Global Script means all the C functions and actions that can be used throughout the project or over several projects. C actions are used in process control during runtime.

GPRS (General Packet Radio Service) GPRS is an expansion of GSM mobile wireless that adds packet-oriented data transmission. Network connections are established over GPRS either in the Internet or in private networks. The data is transmitted using the Internet protocols TCP/IP or UDP/IP.

Glossary


GPS (Global Positioning System) GPS is a worldwide US satellite navigation system for highly accurate location, navigation and time distribution. It operates with 24 orbiting satellites (21 operational and 3 spare satellites) on six satellite orbits at a height of approximately 20,000 kilometers. Each satellite contains an atomic clock whose time is transmitted continuously along with the orbit data. The GPS receiver receives data from a maximum of six satellites and calculates its position based on these values. Once the position has been calculated, the transmission time of the data from the individual satellites can be calculated. The GPS world time (UTC) is calculated in the system based on these values.

Graphics Designer The Graphics Designer is a vector-oriented drawing program for creating process pictures. Complex process pictures can be created using a wide variety of graphic objects from an object and style palette. ST7cc Config uses the ODK interface of the Graphics Designer to create picture typicals for the SINAUT subscribers and to make these available to the WinCC configuration engineer in a sample picture for use in further process pictures.

GSM (Global System for Mobile communications) Worldwide standard for wireless transmission of voice, data, fax and text messages (SMS). There are GSM-based wireless networks found in many countries in particular in Europe, China, Latin America as well as in many regions of the USA, Russia and Africa. A distinction is made according to frequencies: PCS 850 MHz, GSM 900 MHz, DCS 1800 MHz and PCS 1900 MHz.

Image memory principle A TIM has a send buffer and a message image memory for buffering send messages. If a send message is entered using the image memory principle, only a reference to the location of the message is entered in the message image memory. Whenever the TIM has the same message transferred to it again, before the message could actually be transmitted, only the image is updated. The message can only be entered in the send buffer again after it has been transmitted. As a result, it can only exist a maximum of once in the send buffer. If the TIM finds only the reference to the image when processing the send buffer, it takes the relevant message with its up-to-date information from the message image memory: This spontaneous message is then transmitted according to the image memory principle.

ISDN (Integrated Services Digital Network) ISDN integrates various services in one transmission network. ISDN networks integrate telephone, telefax, teletext, Datex-J, video phones and data transfer. This makes a wide variety of digital services available to the user: Language, texts, graphics and other data.

Glossary


LAN (Local Area Network) Local area network. Networked devices within a building or premises, < 2.4 km, no postal restrictions. A communication network for common use by the subscribers. In contrast to public networks, the user has legal control of the network and it is restricted spatially to a (office) building or company premises. LANs exist with different topologies and cabling systems. Example: Industrial Ethernet.

Local buffer If the ST7cc server cannot forward its data to WinCC, all messages (ST7 data messages and organizational messages) are stored in the local buffer. Once WinCC becomes available again, the buffered messages are processed. This mechanism achieves two aims: ● Form the perspective of the stations, the master station can be reached when WinCC is

not available. ● General requests resulting from temporary deactivation of WinCC are avoided.

Local TIM A TIM connected to an ST7cc PC or an S7 CPU over the MPI bus or Ethernet is known as a "local TIM".

LTOP (Line Transformer with Overvoltage Protection) Copper dedicated lines are highly susceptible to electromagnetic interference. The coupling of extraneous voltages can be inductive or capacitive, for example due to the effects of lightning. Direct conductive coupling is also possible due to bad insulation. The LTOP overvoltage protection modules limit extraneous voltage and overvoltage to a non-critical level. The floating transformer also provides electrical isolation preventing coupling of voltages into other cable sections. An LTOP protects persons and investment and is therefore an indispensable safety element in private dedicated line networks.

Main and subcycle The sequence of the polling cycle can be structured on the master TIM by assigning individual polling stations to a main cycle or a subcycle. The subcycle is always activated at the end of the main cycle; in other words, once all stations from the main cycle have been polled, a certain, selectable number of stations are polled in the subcycle. Following this, all the stations in the main cycle are polled again.

MPI The multipoint interface (MPI) is the programming device interface of SIMATIC S7. Devices with an MPI interface (for example a TIM), can also communicate with each other (MPI bus).

Glossary


Multimaster polling with time slots When stations need to communicate with more than one master station in dedicated line or wireless operation, the multimaster polling with time slots mode is used. Each of the connected master stations is assigned one or more defined time slots per minute for polling. The master stations then have their turn to poll in every minute.

Node station A node station is a station that receives messages are from lower-level stations and forwards them to other destination partners, substations (direct communication) or master stations.

OPC (OLE for Process Control) OPC includes a series of specifications for data exchange in automation engineering between controllers, alarm transmitters etc. and control systems.

Organizational message Organizational messages are used to execute organizational system functions. These include, for example: ● General requests ● Time synchronization ● Counted value storage ● Coordinated connection establishment and termination in a dial-up network ● Message indicating station startup and station failure ● Requests for and transmission of subscriber records

Parameter assignment A device is assigned the parameters it requires for starting up when it is supplied with data.

Permanent call A permanent call does not interrupt the normal polling cycle; it is always executed alternating with the standard poll from the normal polling cycle.

PG / programming device A PG is a personal computer designed specifically for use in industry. A PG is fully equipped for programming SIMATIC automation systems.

PG Routing Using PG routing, it is possible to access programmable modules or modules with diagnostic capability beyond network boundaries from a programming device (PG) or computer (PC).

Glossary


Polling In polling mode, data exchange is controlled by the master station. This polls the connected stations (including node stations) one after the other. Stations with data to transmit send it as soon as they are polled. Stations that do not currently have any data only acknowledge the poll. Data from the master station to the stations can be transferred at any time between individual polls.

Polling mode → Polling

Polling with time slots The polling with time slots mode is used in a wireless network in which the use of the radio frequency assigned by the registration authorities must be shared with other users. Each user typically has 6 seconds per minute to exchange data with its stations. The frequency must then be released for other operators. During the allocated time slot, this pooling variant functions like a normal polling system.

PROFIBUS PROFIBUS is the open, internationally standardized (EN50170) bus system for process and field communication with field devices and for data communication within an automation cell. The uses of PROFIBUS range from production and process automation to building automation.

Protocol A protocol is a set of rules for controlled transfer of data. Protocols, for example, specify the data structure, the structure of data packets and the coding. Protocols can also specify a control mechanisms and hardware and software requirements.

Remote buffer The remote buffer is set up only for redundant ST7cc. The ST7cc server recognizes whether or not the redundant mode is required based on the existence of the redundancy license. The remote buffer is organized as a ring buffer and records all incoming messages so that it can be used as a data source for the redundant partner during a restart. If the partner of a redundant ST7cc system starts up again, it can recognize the time for which messages are missing and can request these from the redundancy partner. The remote buffer is necessary to ensure data consistency when using a redundant ST7cc system.

Requested message Requested messages are practically identical to data messages. However, they contain a special ID that indicates that they are not normal spontaneous data messages and that they are transferred due to a request from the master. These data messages are then sent when a station or node TIM has received the organizational message for a general request from the master station.

Glossary


RJ-12 This describes a 6-pin connecting cable with a standardized modular (Western) connector.

RJ-45 This describes a 8-pin connecting cable with a standardized modular (Western) connector.

RS-485 RS-485 is a standard for data transmission with 5 V differential signals. The RS-485 interface uses only one pair of wires and is operated in half duplex. The connection is multipoint-compliant; in other words, up to 32 subscribers can be connected.

Send buffer / image memory A TIM has a send buffer and a message image memory for buffering send messages. A fixed position is reserved in this image memory for each data message transferred to the TIM for transmission. Each newly transferred message always overwrites the old message in the image memory. The image memory therefore contains all data messages with their latest content. The entry of send messages in the send buffer can therefore take place in two ways, according to the send buffer principle or the image memory principle.

Send buffer principle A TIM has a send buffer for buffering send messages. If a send message is entered using the send buffer principle, each time the message is transferred to the TIM, it is entered completely in the send buffer. As a result, it can exist more than once in the send buffer. When the message is transmitted, it is taken completely from the send buffer and transmitted: transmission is according to the send buffer principle.

Setpoint A setpoint is a selected digital or analog value that is transmitted once after the value has been set. The entered value is recalculated when necessary. A setpoint is always transmitted as 1 word. At the receiving end, the setpoint can either the output directly to the process as an analog signal (for example to an external controller) or the value is made available to the local program for further processing (setpoint for internal controller, limit value, threshold value etc.). Setpoint and command input are interlocked for safety reasons; in other words, a setpoint input cannot be made at the same time as a command input. In this case, the acquisition program recognizes an error. Neither the setpoint nor the command are transmitted.

SIM card (Subscriber Identity Module) The SIM card is an identification card for a subscriber of a GSM mobile wireless network.

Glossary


SIMATIC S7 Siemens automation system

SINAUT (SIemens Network AUTomation) Station control system or telecontrol system based on SIMATIC S7

SINAUT message An ST7 message contains the data of an ST7 object for transmission. Depending on the object type, a message can contain either all data of an ST7 object or only a contiguous subarea of the object data.

SINAUT object A SINAUT object contains the data of one or more process variables such as analog values, commands, calculated values, status information on motors, sliders etc. An ST7 object has type-specific processing functions and change checks assigned to it to minimize the communication traffic in the WAN. Type-specific processing functions include, for example, threshold checks or mean value calculation with the object type for analog values. The change check is designed so that a message is generated only when the object data has changed compared with the last time its value was transferred or when the type-specific processing enables generation of a message because the object data is "worth" transferring.

SINAUT TD7 Library The SINAUT TD7 library is a software package with blocks for the CPU. The package was designed so that it can run both on an S7-400 and on and S7-300 CPU. There are only a few blocks intended specifically for the S7-300 or S7-400 CPUs. The SINAUT software in the stations allows change-driven transmission of process data between the individual CPUs and the control center, for example ST7cc. Failure of connections, CPUs, or the control center are displayed. Once a problem has been corrected or the CPUs or control center has started up, data is updated automatically. When necessary, data messages can be given a time stamp. There are two variants of the SINAUT TD7 software package: ● The SINAUT TD7onCPU software package is a software package that has parameters

assigned on the CPU and that runs on the CPU. It is used in all SINAUT stations in which TIM modules of the type TIM 3 or TIM 4 are configured.

● The SINAUT TD7onTIM software package is a software package that is configured and runs on TD7onTIM-compliant TIM modules, for example the TIM 3V-IE. This can be used as an alternative to the TD7onCPU software package when a suitable TIM is configured in a SINAUT station.

SMS (Short Message Service)

Glossary


The short message service in the GSM standard is used to transfer short text messages to mobile radio users. When the short messages are transferred, they are first transferred to the SMS control center using a store-and-forward technique. They are buffered there and then forwarded to the recipient. The sender can query the status of the message in the SMS control center or can request acknowledgment of delivery.

Spontaneous message In SINAUT networks, messages are always transmitted spontaneously; in other words, messages are created and transmitted only when changes occur or event-driven. These messages are known as spontaneous messages. In the dial-up network, however, you can also specify per message whether or not a change causes a conditional or unconditional spontaneous transmission. Unconditional spontaneous messages cause the connection to be established immediately. Conditional spontaneous messages are initially only entered in the send buffer of the TIM. They are only transmitted when a connection is established to the partner for whatever reason, for example because an unconditional spontaneous message needs to be transmitted or because the partner calls.

Spontaneous mode The spontaneous mode is intended only for data exchange in dial-up networks. For transmission in dial-up networks, the data of the stations or a node station can be assigned different priorities (high or normal), data to be sent by the master station always has high priority. If data with high priority is waiting for transmission, a dial-up connection is established immediately. If the data has normal priority, it is first stored on the station. This data is then sent the next time a connection is established to the partner for whatever reason, for example, when information with higher priority is being sent or when the partner establishes a connection to exchange data.

ST7 message ST7 messages consist of a message frame, an area for addresses and control fields (message header) and an area for net data (object data) with the time stamp. The ST7 messages are divided into organizational messages and data messages. The structure of an ST7 message is based on the guidelines of the ST7 protocol.

ST7 protocol This protocol is used in the SINAUT ST7 system for transmitting process data over WANs.

ST7cc SINAUT ST7cc is the ideal control center system based on SIMATIC WinCC for both SINAUT ST7 and SINAUT ST1. It is specially designed for event-driven and time-stamped data transmission in the SINAUT system. It avoids the possible loss of data that can occur with cyclic polling in WinCC. It also ensures the use of the correct event time supplied by the SINAUT stations for all WinCC messages and archive entries. The process image integrated in ST7cc contains all process

Glossary


data as well as the status of all SINAUT subscribers in the network and makes this data available directly to WinCC for fast transfer to the process image.

ST7cc Config ST7cc Config allows the parameter values required for message processing to be specified. When the WinCC data framework is generated (in other words, message management), the individual WinCC messages are generated and imported into WinCC.

ST7cc tag An ST7cc tag is a data section from the data area of a SINAUT object that is managed and processed as a separate information unit in the ST7cc server. The tags are processed, however, in ST7cc and in WinCC. When the tags are defined, different processing can be assigned to them depending on their type. A tag can contain both a process value as well as status information from system components. System components are the SINAUT subscribers.

ST7cc tag management ST7cc tag management covers all ST7cc tags. The content of the ST7cc tags represents the current process image. WinCC writes and reads the ST7cc tags.

ST7sc The SINAUT system allows the networking of SIMATIC stations with a control center over a WAN (Wide Area Network). This control center can also be a SIMATIC station or a PC-based control center, for example, WinCC with the SINAUT ST7cc add-on. SINAUT ST7sc allows the manufacturers of control systems to connect to SINAUT without needing to integrate a SINAUT interface. Communication is over OPC: As an OPC server, SINAUT ST7sc forms the interface between the SINAUT system and a control system connected as an OPC client. The OPC interface is also suitable for data exchange with other applications, for example, the Microsoft Office application Excel.

Station In the SINAUT world, the term station includes the entire hardware components required for acquisition, processing and communication with other stations or a master station/control center. A station can, for example, consist of a modem, a TIM and a programmable controller (in turn consisting of a CPU and I/O modules). A SINAUT station can also include several programmable controllers, or, in the case of a node station, several TIMs.

Status message A status message is a process status (for example pump on, valve open) or alarm (for example limit value exceeded). This is binary information with the possible values 0 or 1. Eight status messages are put together to form one byte.

Glossary


STEP 7 The basic STEP 7 software is the standard tool for the SIMATIC S7, SIMATIC C7 and SIMATIC WinCC automation systems.

TCO (TIM Connect) The TCO component monitors the local TIMs connected over MPI or Ethernet, maps their most important status displays on ST7sc tags, forwards received messages for message decoding or transfers the messages to be sent to the relevant TIM for WAN communication.

TCP/IP (Transmission Control Protocol / Internet Protocol) Network protocols for connecting two computers in the Internet. IP is the basic protocol. UDP is based on IP and sends individual packets. These can arrive at the recipient in a different order from the order in which they were sent - they can even be lost. TCP is used to make the connection reliable and makes sure, for example, that data packets are passed on to the application in the correct order. In addition to the IP addresses, UDP and TCP also involve port numbers between 1 and 65535 with which the various services can be distinguished. On a Windows PC, the WINSOCK.DLL (or WSOCK32.DLL) is responsible for handling the two protocols.

TIM (Telecontrol Interface Module) The TIM transmission processor is a communications module that handles all data transmission functions provided by the SINAUT system independently. Depending on the type, the TIM has one or two WAN interfaces, an MPI interface or an Ethernet interface. Depending on the requirements, a variety of transmission equipment can be connected. The module is supplied in an S7-300 housing. The TIM is available in three basic variants: ● TIM 3

TIM 3x without MPI port, only for installation as a CP in the S7-300 with only one WAN port: either over the integrated modem or over the serial port for an external modem.

● TIM 4 TIM 4x with MPI port both for installation as a CP in an S7-300, can also be connected as a stand-alone device over MPI to one or more S7-400 and S7-300 PLCs. The TIM 4 has two WAN ports: one over the modem integrated in the TIM, the other over the serial port for an external modem. The two WANs can be identical or different, for example dedicated line plus telephone network.

● Ethernet TIMs – TIM 3V-IE variants with two WAN attachments: An RS-232 port and an RJ-45 Ethernet

port, only for installation as a CP in S7-300. With the TIM 3V-IE, SINAUT communication is either over the RS-232 or over the Ethernet port. The TIM 3V-IE Advanced can use the RS-232 port at the same time as the Ethernet port.

– TIM 4R-IE with four WAN connections: Two RS-232 interfaces and two RJ-45 Ethernet interfaces. Installation as a CP in an S7-300 or as standalone device in a separate

Glossary


TIM rack. With the TIM 4R-IE, SINAUT communication is handled over the RS-232 and over the Ethernet interfaces simultaneously.

Topology The topology describes the network structure. It specifies how a network (transmission medium and connectable devices or computers) is interconnected. Possible structures are linear (bus), star, ring, redundant ring and tree structure.

Unconditional / conditional spontaneous message → Spontaneous message

VPN (Virtual Private Network) The principle of a virtual private network is to use public networks such as the Internet to transfer private data. The communications partners of the private network can exchange data as if they were part of a LAN. Communication can be secured using various encryption and authorization techniques.

WAN (Wide Area Network) Wide area networks are intended for language or data transmission over greater distances. The concept of such networks is essentially decided by the services available. The basic structure of a wide area network can be based on circuit switching or packet switching. The circuit switching structure uses a hierarchical arrangement of switching points. WANs can have a span of several thousand kilometers. The following WANs can be used with SINAUT: ● Private or leased dedicated lines (copper or fiber-optic cable) ● Private radio networks (directional or omnidirectional radio and private mobile radio with

time slots) ● Analog telephone network ● Digital ISDN network ● GSM mobile wireless network with the services CSD, GPRS and SMS ● Private wideband networks such as OTN, PCM30 etc. ● DSL networks

WinCC WinCC is a cross-branch and technologically neutral system for the solution of visualization and process control tasks in production and process engineering. It provides function modules for graphics display (Graphics Designer), for signaling (Alarm Logging), for archiving (Tag Logging) and logging.

Glossary


WinCC API As a completely open and expandable system, WinCC makes a comprehensive API (Application Program Interface) available. This involves an interface over which the user programs such as ST7cc Server and ST7cc Config can access WinCC. A comprehensive description is available with the WinCC ODK (Open Developers Kit).

WinCC buffer Message and archive processing can be assigned to the ST7cc tags. If this is the case, individual messages or archive data are generated in ST7cc, that are transferred over the ODK interface to Alarm Logging or Tag Logging for further processing. The results of processing an ST7cc tag can, however, accrue faster than they can be accepted by WinCC. The WinCC buffer takes the WinCC jobs from the ST7cc processing and therefore separates the asynchronous procedures of job creation and job processing.

WinCC channel DLL To allow WinCC to communicate with the widest variety of data sources (programmable controllers, ST7cc servers etc.), various communications drivers are used. A communications driver is a C++ DLL that communicates with the data manager over an interface known as the channel API that is specified by the data manager. The WinCC tags are supplied with process values over the communications driver.

WinCC tag WinCC tags are central elements to allow process values to be accessed. Within a WinCC project, they have a unique name and a data type. A WinCC tag is assigned to a logical connection that specifies which channel supplies the process values of the tags and over which connection. For the WinCC tags whose data sources are the ST7 tags, the channel DLL is the connection over which the ST7cc server supplies the process values. The WinCC tags required for ST7cc can be generated with ST7cc Config.

WinCC tag logging (Runtime) Tag logging is used to receive data from running processes and to prepare it for display and archiving. The data formats and the acquisition times and archiving times can be set as required. WinCC tag logging is 'computer time'-oriented and [ ] not intended for the arrival of data with a delay offset as is the case with SINAUT ST7. This means that the ST7cc server must make certain archiving preparations for WinCC. The ST7cc server transfers the values to be archived to tag logging over the ODK interface. This ensures the chronological arrangement of the archive values even if process data is delivered by the ST7 stations, for example, with an offset of an hour.

WinCC tag management WinCC tag management covers all WinCC tags. Each element (in other words, every tag) used in WinCC is collected in tag management and managed there.


Index

C Configuration

Changing the, 19, 163 Connections, 82 Creating a new project, 20 Hardware configuration, 25 Network configuration, 21 Networks, network attachments, 47 Parameters for subscribers, 91 SMS Configuration, 101 ST7cc/sc control center, 90 Subscriber data, 88 TD7onTIM, 108 Telephone number, 98

Configuration software, 17 Connection configuration, 83 Consistency check, 79, 152, 161 Contacts, 16 Cyclic program OB1, 201

D Data objects, 109 Data point typicals, 217 Diagnostic messages

of TD7onCPU, 528 of the TIM, 514

Diagnostics and Service tool Overview of functions, 439 PG Routing, 438

E Error program OB121, 210

F Firmware update, 498

H Hotline, 15 HW Config, 25

I Internet, 16 Invalid Connections, 85

L Lost connections, 87

M Message protocol diagnostics

ST7cc/ST7sc, 504 Structure and function, 505 Testcopy DB, 503 TIM, 505

N NetPro, 21

O Object communication, 194 Optional blocks, 395

P PG Routing

Application, 546 Basic configurations, 534 Canceling the PG/PC assignment, 550 Introduction, 533 PG/PC assignment, 547 Range of functions, 537 System preparation, 539

Index


R Receive channel, 110 Repair, 500

S Send channel, 110 Service, 16 SIMATIC Customer Support hotline, 15 SIMATIC Manager, 20 SINAUT diagnostics

Block Structure for all CPUs, 478 SDB Viewer, 488 TD7 Block Structure, 473 TD7 Check of the Communication Configuration, 483 TD7 CPU Diagnostics, 472 TD7 CPU Program Comparison, 481 TD7onTIM diagnostics, 485 TIM diagnostic messages, 467 TIM Diagnostics, 451 TIM Message Monitor, 470 TIM subscriber diagnostics, 461

SINAUT objects, 108, 120, 194 SINAUT ST7 Configuration Tool, 80 SINAUT TD7, 171 Startup program OB100, 201 STEP 7 diagnostics

CPU messages, 441 General, 441 Module information, 443 Operating mode, 449 Setting the time, 450

Subscriber administration, 88 Support, 16 System data blocks

Generation of, 151 Transfer, 153

System function blocks SFBs, 432 System functions SFCs, 432 System objects, 109

T TD7 basic blocks, 211 TD7 library

Block overview, 177 General, 174 Online help, 191

TD7onCPU, 171 TD7onTIM, 108

Test blocks, 426 Time synchronization

in SINAUT networks, 57 of TIM modules, 32 with TD7onTIM, 150

Time-driven OB cyclic interrupt program, 208 Training center, 16

Documents

4 SINAUT ST7 Software 5 - Siemens AG · Preface 1 Configuration software for SINAUT ST7 2 SINAUT TD7 software package for the CPU 3 SINAUT Diagnostics and Service tool 4 SINAUT PG