AiT PR Interface-PLC-Transmit SI en

Acquis iT Transmit Siemens S7
VVersion V8.00 (Edition March 2009)
No responsibility can be assumed for the details contained in this manual; changes can be made at any time. The software described in this manual is subject to the license conditions.
ProLeiT AG Einsteinstrae 8, D-91074 Herzogenaurach Tel.: +49 9132 / 777-0 Fax: +49 9132 / 777-150 eMail: Info@proleit.de http://www.proleit.de Hotline: eMail:
hotline@proleit.de
Plant iT V8.00 (Edition March 2009) Acquis iT Transmit Siemens S7 R26, Edition: 12/06/2007 AiT_pr_Interface-PLC-Transmit_SI_en.doc
Designations for hardware and software mentioned in this manual are in most cases also registered trademarks of the owner and should be considered as such.
Plant iT V8.00 (Edition March 2009) R26
Acquis iT Transmit Siemens S7 2
Table of Contents
Table of Contents 1 2 3 3.1 3.2 3.3 4 4.1 4.2 4.3 5 5.1 5.2 5.3 5.4 6 6.1 6.2 6.3 6.4 6.4.1 6.4.2 6.4.3 6.4.4 6.4.5 6.4.6 6.4.7 6.4.8 6.4.9 6.5 6.6 6.6.1 6.6.2 6.7 6.7.1 6.7.2 6.7.3 6.7.4 7 7.1 7.2 7.3 7.4
Introduction ..............................................................................................5 Method of Operation ................................................................................6 Technical Description ..............................................................................7 Components of Acquis iT Transmit.......................................................7 Using Acquis iT Transmit in the WinAC ................................................7 Default Settings.....................................................................................7 Configuring ...............................................................................................9 Parameterize the Global Variables .......................................................9 Parameterize the PDA Data Blocks to be Sent/Received ..................10 Supply/Clear the User Data Blocks.....................................................17 Commissioning ......................................................................................18 Test the Connection Parameters ........................................................18 Diagnosis of the Connection on the CP ..............................................21 Diagnostic Display in the DB_System.................................................21 Diagnostic Displays in the DB_DRV_TMT_Parameter.......................21 Recommendation: Categorization of the Process Information to be Recorded.................................................................................................24 Category: Resource State...................................................................24 Category: Fault Messages ..................................................................25 Category: Process Messages .............................................................25 Category: Overall Machine State / Overall Plant State.......................26 Bit 0 : Machine ON .........................................................................26 Bit 1 : Manual / Semiautomatic Operation .....................................26 Bit 2 : Automatic Operation ............................................................26 Bit 3 : Machine Producing ..............................................................27 Bit 4 : Deficiency ............................................................................27 Bit 5 : Congestion...........................................................................27 Bit 6 : External Fault.......................................................................28 Bit 7 : Self-Fault..............................................................................28 Bit 8 to Bit 15 : For Special Tasks..................................................28 Category: Plant States ........................................................................28 Counters Versus Measured Values ....................................................29 Category: Counters........................................................................29 Category: Measured Values ..........................................................30 Maintenance Information.....................................................................30 Category: Switching Cycles ...........................................................30 Category: External Operating Times .............................................31 Category: Internal Operating Times...............................................31 Category: Maintenance Signal.......................................................31 Recommendation: Module Structures .................................................32 Resource States, Fault Messages, Process Messages, Plant States, Machine/Plant Overall States..............................................................33 Counters..............................................................................................34 Measured Values ................................................................................35 Switching Cycles .................................................................................36
Table of Contents
7.5
Operating Times..................................................................................36
8 Appendix .................................................................................................38 8.1 Telegram Structure .............................................................................38 8.1.1 PDA Telegram Service 10, Type 1 (Timestamp in Second-Coding)38 8.1.2 PDA Telegram Service 10, Type 2 to/from the Executive Server..38 8.1.3 PDA Telegram, Service 10, Type 2 to the Acquis iT Collect .........41 8.1.4 Clock Telegram, Service 10, Type 3 from Executive Server .........43 8.2 Example: Create a Counter in the DINT Format with Overflow Processing ..........................................................................................44 8.3 Error Recognized from Acquis iT Transmit.........................................45
Introduction
Introduction
Acquis iT Transmit is a standard software package for controllers. Its task is to provide parameterized facilities to send process data for the acquisition and archiving from the controller to an acquisition system. Transmit also can also be used to receive process data in the PLC. The following section describes the operation and parameterization. You will also find recommendations for the structuring of the process data to be sent. The contents of this manual are grouped into individual blocks of topics: Method of Operation Technical description Configuring Commissioning Recommendations Appendixes. A "Hotline Sheet" is attached at the end of this document. Please inform us if you have any questions, you can recommend improvements, you would like to have your wishes catered for, or have just found errors. We would be pleased to call you back if you give your name and fax/telephone number.
Method of Operation
Method of Operation
Acquis iT is a system for plant data acquisition. It allows the Plant iT Executive Server on the PC to acquire any data, irrespective of whether this involves messages, counter values or maintenance information, or whether the data relates to an order, a batch or a shift. The Plant iT Executive Server runs on a computer under a Windows Server OS. The controllers must send the data to be acquired to the Executive Server using telegrams. Acquis iT Transmit, together with the Plant iT basic driver, performs this task in the PLC: The Acquis iT Transmit fetches the data to be acquired from the source areas of the PLC and transfers this to the Plant iT basic driver, which is responsible for the buffering and the actual sending of the telegrams to the PC. The TCP/IP (RFC1006) protocols are supported as transmission protocols.
Server MS SQL Server Configuration Server Executive Server Workstation MS Excel Configuration Client Select Work
Process data bus
Machine controler Transmit
Figure 1:
Controllers send using TCP/IP (RFC1006) to the Executive Server When used in the SoftPLC WinAC, both the Acquis iT Executive Server and the PLC components (Acquis iT Transmit and basic driver) are stored on the same PC.
Technical Description
3
3.1
Components of Acquis iT Transmit
Acquis iT Transmit is a parametrizable standard software component of the Plant iT basic driver. It consists of two datablocks and two function module.
Symbolic Name DRV_TMT_Main DRV_Service10 DB_DRV_TMT_Parameter DB_DRV_TMT_Send TMT_Parameter S7-400/WinAC module FC1002 FC1001 DB1006 DB1007 UDT1001 Description Fetches the data to be sent from the data sources of the PLC Writes the received data in the target areas of the PLC DB for parametrization Work area Structure of the parameter record
The "DRV_TMT_Main" FC is invoked from the programs of the basic driver. The FC fetches the data from the parameterized source areas and transfers it to send it to the programs of the basic driver. The "DRV_Service10" FC is invoked from the programs of the basic driver when data from the Executive Server has arrived in the PLC. The FC "DRV_Service10" writes this data into the parameterized target areas. You must parameterize the data to be sent and the associated send criterion in the "DB_TMT_Parameter". When you receive data, you must parameterize here that target area in the PLC. The "TMT_Parameter" structure defines the parameter records in the "DB_TMT_Parameter". The FC "DRV_TMT_Main" transfers the data to be sent to the basic driver in the "DB_TMT_Send" datablocks. The data connection to the PC with the Plant iT Executive Server must be parameterized in the basic driver. The supplied basic driver already has an operational data connection to the Plant iT Executive Server using the TCP/IP (RFC1006) protocol.
3.2
Using Acquis iT Transmit in the WinAC
When a WinAC is applied, no connection parameters need to be set in the basic driver. No further WinAC-specific settings need to be made in the Acquis iT Transmit parameters.
3.3
Default Settings
To simplify the first test with the Transmit software, it is supplied with two parameter records already preparameterized in the "DB_DRV_TMT_Parameter" so that you can immediately send user data to an Executive Server with the station number 100. Here, 50 data words are sent from the DB5 in a time cycle of 5 seconds and 50 data words from the DB6 in a time cycle of 1 second. When this parametrization example is no longer required, you can use the parameter records 1 and 2 in the "DB_DRV_TMT_Parameter" for your own applications and delete the DB5 and DB6.
If you use the Plant iT software with integrated Transmit, the TCP/IP (RFC1006)-connection to the Executive Server has already been parameterized. The connection parameters in the DB1020, DB1023 of the basic driver, and in the hardware configuration and connection table of the S7 and in the INI files (IDSEXEC.INI and DRVRFC.INI for the Executive Server) have been preconfigured appropriately on the PC.
S7-400 module Description DB5 Sample DB with user data to send in a 5 second cycle (can be deleted when it is no longer needed) DB6 Sample DB with user data to send in a 1 second cycle (can be deleted when it is no longer needed)
Configuring
Configuring
The Transmit is configured in the following steps: Parameterization of the global variables in the "DB_TMT_Parameter" Parameterization of the parameter records in the "DB_TMT_Parameter" for sending/receiving data. The next section leads you step-by-step through the configuration.
4.1
Parameterize the Global Variables
The "DB_DRV_TMT_Parameter" (DB1006) consists of two areas, a global area and an area that contains a data record for each data block to be sent/received. This section describes the global variables. Extract from the "DB_DRV_TMT_Parameter":
DBW DBX DBX DBX 2: 4.0: 4.1: 4.2 PartnerStation INT P: Station number of the server with Acquis iT Executive Server TRUE P: FALSE: without time, TRUE: with time FALSE P: TRUE: analyze telegram with time for sync system clock FALSE P TRUE: Timesync using local time, FALSE: using GMT 100
Uhrzeit_ergaenzen BOOL FreigabeTimeSync LocalTime BOOL BOOL
Only those global variables from the "DB_DRV_TMT_Parameter" on which settings can be made are listed here. The parametrization of the actual data connection is made in the basic driver itself. The "Installation of the Basic Drivers" manual provides support here. The provided manual also describes in short form the data connection to the Acquis iT Executive Server as supplied. You can find it at the end of this section. DBW 2: Station number of the partner: Parameterize in the DBW 2 the station number of the PC with the Acquis iT Executive Server. This is the station to which you wish to send the data or from which you wish to receive data. You can only specify a single partner station. This number must be unique throughout the plant. Numbers in the range 1 to 65535 are permitted.
Configuring
DBX 4.0:
Time Set this bit to specify that the telegrams from your controller are always sent with the time of your controller. However, this makes sense only when the clock in your controller is maintained from a central clock! If you set this bit at 0, the data is sent without timestamp. The Executive Server recognizes this when it receives the telegram and then automatically assigns the time when the telegram arrived at the Windows NT Server. The latter is the recommended method. FALSE = 0 Send data without the time from the PLC (the Executive Server adds the time when the telegram is received) TRUE = 1 Send data with the time from the PLC
DBX 4.1:
Enable time synchronization via telegram This functionality was originally needed for the CPUs of the S7-300 whose system clock cannot be synchronized directly using the inserted CP module. Consequently, it is possible the synchronize the system clock time of the PLC via telegrams from the PC. FALSE = 0 time synchronization in the PLC via telegram is deactivated TRUE = 1 time synchronization in the PLC via telegram is active
DBX 4.1:
Clock synchronization with local time or GMT If you have enabled the synchronization of the PLC system clock by telegram using DBX4.1, you can select here whether the system clock is to be set with the local time or GMT. FALSE = GMT TRUE = local time
4.2
Parameterize the PDA Data Blocks to be Sent/Received
A data record exists in the "DB_DRV_TMT_Parameter" for each data block to be sent or received. This data record describes which data blocks are to be sent and which send criterion is to be used, or in which data block the received data is to be stored. You must parameterize the lines shown bold. They are also marked in the DB with a "P:". (S) or (R) in the comment indicates parameters that need to be set for the sending or receiving of data blocks, respectively. Parameters with an (S+R) are needed for both transmission directions.
Configuring
Selection from the "DB_DRV_TMT_Parameter" in the sample file: (P= to be parameterized by the user)
Absolute byte no. 100 - 101 102 - 103 104 - 105 106 - 107 108 - 109 110 - 111 112 - 113 114 - 115 Relative byte no. / / 0-1 2-3 4-5 6-7 8-9 10 - 11 Format INT INT INT INT INT INT INT INT Content +14 +2 +0 +0 +5000 +0 +0 +5 P P P P Description Length of the parameter record in words Number of valid parameter records (S+R) Pointer to release flag (bit number) (S) Pointer to release flag (byte number) (S) Set time in ms (S) Actual time in ms (S) Good-telegrams counter (display) (S+R) DB number as data source or data target for the data block (S+R) Byte number in the source/target module where the data block begins (S+R) Length of the source/target area in words (S+R) Send or receive (S+R) Send condition satisfied (S) Last error (display) (S+R) Time: year (BCD) (S+R) Time: month (BCD) (S+R) Time: day (BCD) (S+R) Time: hour (BCD) (S+R) Time: minute (BCD) (S+R) Time: second (BCD) (S+R) P: Block number (S+R)
116 - 117
12 - 13
INT
+0
118 - 119 120 121 122 - 123 124 125 126 127 128 129 130 - 131
14 - 15 16.0 17.0 18 - 19 20 21 22 23 24 25 26 - 27
INT BOOL BOOL INT BYTE BYTE BYTE BYTE BYTE BYTE INT
+101
FALSE P FALSE +0 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 +10
A data record is always 14 data words (= 28 bytes) long. The first data record starts at DBB 104 in the "DB_DRV_TMT_Parameter". The data records must be contiguous. Thus, the second data record starts at DBB 132, the third starts at DBB 160, etc. You must enter the number of valid data records in DBW 102. Although there is no restriction to the number of data records that can be entered, ensure that the data record length (14) is entered in DBW 100 and the DB is lengthened accordingly should you need additional parameter records. These data records contain both values you must parameterize (shown bold) and also values that must be supplied dynamically at runtime. The following section describes the data words that you must parameterize. The numbering of the individual data items does not refer to the byte number in the data block but the byte number within a record. The first byte within a record is designated as DBB 0, similarly, the first byte within a data block is designated as DBB 0. Set to the 0 value all data in the records that you do not need to configure.
Configuring
DBB 0 - 3:
Pointer to the release flag (S) Enter here the bit number and the byte number of a flag when the sending of the corresponding data block depends on an explicit release of the application program. The value range for the byte number of the flag depends on the associated CPU type: CPU 414: CPU 416: CPU 417: WinAC: flag byte [1 ... 1023] flag byte [1 ... 2047] flag byte [1 ... 16383] flag byte [1 ... 2047]
If this parameter is initialized with 0, the program recognizes that no release flag was parameterized and only operates with the set time from DBW 4. DBW 4: Set time in milliseconds (S) Enter here the time to be used for the send interval. If, for example, you wish to send a data block every 2 seconds, enter here the value 2000 for 2000 milliseconds. If the value 0 is entered, the program interprets this parameter as "not parameterized". If you enter the parameter with value range KF [-32767..-1,1..499] ms, the program itself sets the parameter to 500 ms. This is the smallest permitted value; smaller values could very quickly overload the complete system. We recommend that you set the value to 1000ms or larger. DBW 10: Module number (S+R) Enter here the number of the DB that contains the data to be sent or in which the received data is to be stored. The value range for the DB number depends on the associated CPU type: CPU 414: CPU 416: CPU 417: WinAC: DBW 12: DB-no. [1 ... 1023] DB-no. [1 ... 4095] DB-no. [1 ... 8191] DB-no. [1 ... 65534]
Begin byte number (S+R) Enter here the byte number of your DB where the data to be sent starts or the starting location for the received data is to be stored. The DB length and thus the byte number depends on the associated CPU type. The following list assumes that you wish to exchange at least 2 bytes. Value range: [0 ... 64KB -2]
DBW 14:
Length in words (S+R) For sending (S): Enter here the number of words to be sent. If, for example, you wish to send 30 words, then enter the value 30 here. Note the maximal permitted value here! This depends on the maximum telegram block length "Blocklen" in the DBW164 of the DB1023 "DB_System". The following table shows the maximum send length for the user data depending on the set block length.
Telegram block length in the DB1023 120 words 200 words Max. send length for user data 101 words 181 words
For receiving (R): Enter here the maximum length of the target area in words. Transmit will reject
Configuring
any data block that arrives that is longer than the specified maximum length. This avoids overwriting the data following the target area in your target DB. The maximum length of the target area is subject to the same dependencies as the telegram block length for sending. DBX 16.0: Send or receive flag (S+R) Set here whether the current parameter record is to be responsible for the sending or the receiving of a data block. Accordingly, the parameterized data block represents the source for the data to be sent or the target for the received data. FALSE = send a data block TRUE = receive a data block DBW 26: Block number (S+R) For sending (S): Similarly to your station number, the Executive Server uses the block number to assign the configured data to your data blocks. The Executive Server does not know your data blocks. Consequently, it needs another characteristic for the assignment. This characteristic is the block number. Thus, you must assign a different, namely unique, block number for each data block that you send. You can use any number in the range 1-255 for this purpose. The block number must be unique within your controller. For receiving (R): Transmit uses the block number contained in the telegram to search for the associated parameter record in the "DB_DRV_TMT_Parameter". The parameter record provides it with the information about the position and length of the actual target area in which the received data is to be stored. Notes For the DBW 0+2 and DBW 4 parameters (S) These two parameters can be used to control the behavior of the software. There are four possibilities of using these two parameters:
Data word number DBW 0 bit number DBW 2 byte number DBW 4 set time Variant 1 +0 +0 +z Variant 2 +x +y +z Variant 3 +x +y +0 Variant 4 +0 +0 +0
Variant 1 Variant 2
Send a telegram in the fixed time interval without requiring a specific release from the application program. Send a telegram in the fixed time interval with release from the application program using M y,x. In this case sending continues until the application program resets M y.x. Send a telegram once with release from the application program using the M y,x flag. Here, the data block is sent just once and then the Transmit software resets the release flag back to 0. In this case, the user himself must organize the time-related behavior for sending the data. This version causes the program not to send such a parameterized data block, but rather enter an error message in the associated error data word of the parameter record. However, all other data blocks are sent provided such a parametrization does not apply to them.
Variant 3
Variant 4
Configuring
Example:
Send a data block with the time cycle of 5000 ms in continuous operation
Absolute byte no. 104 - 105 106 - 107 108 - 109 110 - 111 112 - 113 114 - 115 Relative Format byte no. 0-1 INT 2-3 4-5 6-7 8-9 10 - 11 INT INT INT INT INT Content +0 +0 +5000 +0 +0 +10 P P P Description Pointer to release flag (bit number) (S) Pointer to release flag (byte number) (S) Set time in ms (S) Actual time in ms (S) Good-telegrams counter (display) (S+R) DB number as data source or data target for the data block (S+R) Byte number in the source/target block where the data block begins (S+R) Length of the source/target area in words (S+R) Send or receive (S+R) Send condition satisfied (S) Last error (display) (S+R) Time: year (BCD) (S+R) Time: month (BCD) (S+R) Time: day (BCD) (S+R) Time: hour (BCD) (S+R) Time: minute (BCD) (S+R) Time: second (BCD) (S+R) Block number (S+R)
116 - 117
12 - 13
INT
+4
118 - 119 120 121 122 - 123 124 125 126 127 128 129 130 - 131
14 - 15 16.0 17.0 18 - 19 20 21 22 23 24 25 26 - 27
+30
FALSE P FALSE +0 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 P +10
DBW 0 + DBW 2 DBW 4 DBW 10 DBW 12 DBW 14 DBX 16.0 DBW 26
=0 = 5000 = 10 =4 = 30 = FALSE = 10
No release flag parameterized The data is sent every 5 seconds The data is contained in the module with number 10 The data to be sent starts at byte 4 in the DB10 30 words are to be sent The parametrization is used to send a data block The data receives block number 10
Example:
Send a data block with the time cycle of 5000 ms on release by the application program in the M99.1.
Absolute byte no. 104 - 105 106 - 107 108 - 109 110 - 111 112 - 113 114 - 115 Relative Format byte no. 0-1 INT 2-3 4-5 6-7 8-9 10 - 11 INT INT INT INT INT Content +1 +99 +5000 +0 +0 +10 P P P Description Pointer to release flag (bit number) (S) Pointer to release flag (byte number) (S) Set time in ms (S) Actual time in ms (S) Good-telegrams counter (display) (S+R) DB number as data source or data target for the data block (S+R) Byte number in the source/target block where the data block begins (S+R)
116 - 117
12 - 13
INT
+4
Configuring
Absolute byte no. 118 - 119 120 121 122 - 123 124 125 126 127 128 129 130 - 131 DBW 0 DBW 2 DBW 10 DBW 12 DBW 14 DBX 16.0 DBW 26 =1 = 99 = 10 =4 = 30 = FALSE = 10
Relative Format byte no. 14 - 15 INT 16.0 17.0 18 - 19 20 21 22 23 24 25 26 - 27 BOOL BOOL INT BYTE BYTE BYTE BYTE BYTE BYTE INT
Content +30 P
Description Length of the source/target area in words (S+R) Send or receive (S+R) Send condition satisfied (S) Last error (display) (S+R) Time: year (BCD) (S+R) Time: month (BCD) (S+R) Time: day (BCD) (S+R) Time: hour (BCD) (S+R) Time: minute (BCD) (S+R) Time: second (BCD) (S+R) Block number (S+R)
FALSE P FALSE +0 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 +10 P
Bit number of the release flag Byte number of the release flag The data is contained in the module with number 10 The data to be sent starts at byte 4 in the DB10 30 words are to be sent The parametrization is used to send a data block The data receives block number 10
Example:
Send a single data block on release by the application program

Absolute byte no. 104 - 105 106 - 107 108 - 109 110 - 111 112 - 113 114 - 115 Relative Format byte no. 0-1 INT 2-3 4-5 6-7 8-9 10 - 11 INT INT INT INT INT Content +1 +99 +0 +0 +0 +10 P P P Description Pointer to release flag (bit number) (S) Pointer to release flag (byte number) (S) Set time in ms (S) Actual time in ms (S) Good-telegrams counter (display) (S+R) DB number as data source or data target for the data block (S+R) Byte number in the source/target block where the data block begins (S+R) Length of the source/target area in words (S+R) Send or receive (S+R) Send condition satisfied (S) Last error (display) (S+R) Time: year (BCD) (S+R) Time: month (BCD) (S+R) Time: day (BCD) (S+R) Time: hour (BCD) (S+R) Time: minute (BCD) (S+R) Time: second (BCD) (S+R) Block number (S+R)
116 - 117
12 - 13
INT
+4
118 - 119 120 121 122 - 123 124 125 126 127 128 129 130 - 131
14 - 15 16.0 17.0 18 - 19 20 21 22 23 24 25 26 - 27
+30
FALSE FALSE +0 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 +10 P
Configuring
DBW 0 DBW 2 DBW 4 DBW 10 DBW 12 DBW 14 DBX 16.0 DBW 26
=1 = 99 =0 = 10 =4 = 30 = FALSE = 10
Release flag is M 99.1 The data is sent just once and the release is then reset. The data is contained in the module with number 10 The data to be sent starts at byte 4 in the DB10 30 words are to be sent The parametrization is used to send a data block The data receives block number 10
Example:
Receive a data block

Absolute byte no. 104 - 105 106 - 107 108 - 109 110 - 111 112 - 113 114 - 115 Relative Format byte no. 01 INT 23 4-5 6-7 8-9 10 - 11 INT INT INT INT INT Content +0 +0 +0 +0 +0 +20 P P P Description Pointer to release flag (bit number) (S) Pointer to release flag (byte number) (S) Set time in ms (S) Actual time in ms (S) Good-telegrams counter (display) (S+R) DB number as data source or data target for the data block (S+R) Byte number in the source/target block where the data block begins (S+R) Length of the source/target area in words (S+R) Send or receive (S+R) Send condition satisfied (S) Last error (display) (S+R) Time: year (BCD) (S+R) Time: month (BCD) (S+R) Time: day (BCD) (S+R) Time: hour (BCD) (S+R) Time: minute (BCD) (S+R) Time: second (BCD) (S+R) Block number (S+R)
116 - 117
12 - 13
INT
+6
118 - 119 120 121 122 - 123 124 125 126 127 128 129 130 - 131
14 - 15 16.0 17.0 18 - 19 20 21 22 23 24 25 26 - 27
+10
TRUE P FALSE +0 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 +11 P
DBW 10 DBW 12 DBW 14 DBX 16.0 DBW 26
= 20 =6 = 30 = TRUE = 11
The received data should be stored in the module with number 20 The data should be stored starting at byte 6 in the DB 20 A maximum of 10 words are provided for the arriving data in DB20 starting at byte 6. Any longer data blocks will be rejected when they are received. The parametrization is used to receive a data block Only data that arrives with block number 11 in the PLC is stored in the target area
Configuring
4.3
Supply/Clear the User Data Blocks
Generally, you are responsible for how and when you supply process data to the sending data blocks. However, the data must be assigned to the data blocks at least as fast as these are sampled by the Executive Server. It is desirable to store data for fast sampling in one data block and data for slower sampling in a different data block. Thus, for example, one data block can send with a cycle time of 1000 milliseconds while the other data block sends with a cycle time of 5000 milliseconds. Similar conditions also exist for receiving: you most process the data at least as fast as the Executive Server sends to data to the PLC. It is not specified which process information must be placed in which data word. Acquis iT, with its flexible parametrization, permits an arbitrary mixture of process data within a data block. A standard for filling plants has crystallized over the course of time. Many items from this standard can also be used for other production areas, such as brewhouses, packing plants, etc. You should contact the person responsible for the parametrization of the Executive Server. He can answer the question whether and which standard is being employed.
Commissioning
Commissioning
Once you have performed all parameterization work and transferred the software to your controller, the system can be tested for its functional capability. However, this can be performed only when your peer is also connected to the network using TCP/IP. The following tools are available to test the function or to search for errors: Siemens programming device software Siemens NCM software for the associated communications module Diagnostic displays in the basic driver Diagnostic displays for the Acquis iT Transmit standard software.
5.1
Test the Connection Parameters
The connection parameters are parameterized in the basic driver in the DB1023 and DB1020. The Siemens NCM software must be used to enter the connection into the connection table for the communications module. note: The manual for the installation of the basic driver provides a guide for this parametrization. To simplify troubleshooting, the following section describes the interaction between the set parameters of an TCP/IP connection. A general schematic overview is provided first. The same overview is then shown in more detail using the current parameters as supplied.
Commissioning
Steuerung mit Acquis iT Transmit
DB1006 Partner station x
DB1023
DB1020 parameters of connection to station x: LADDR ID a parameters of connection to station y: parameters of connection to station z: ...
CP443 List of connection ID a IP-adresses TSAPs ID b IP-adresses TSAPs ID c IP-adresses TSAPs

4
List of stations station x station y station z ...
TCP/IP
IDSEXEC.INI DRVRFC.INI
PC with Plant iT Executive Server
PLC station k PLC station l PLC station m

5
PLC station k IP adresses TSAPs PLC station l IP adresses TSAPs PLC station m IP adresses TSAPs
Figure 1:
Overview: Connection parameters for control and PC 1. 2. The partner station from the DB1006 must be contained in the station list in the system DB 1023 for the basic driver. The position of the partner station in the station list of the basic driver determines the parameter record in the DB1020 with the connection parameters for the communications module. Where position 1 in the station list in the DB1023 points to the 1st record in the DB1020, position 2 in the station list in the DB1023 points to the 2nd record in the DB1020, etc. The parameterized connection-ID in the record of the DB1020 points to the associated entry in the connection table. The IP address and the TSAPs to the connection partner are stored on the communications module (CP). The partner to the entry in the connection table of the CP is stored on the PC in the DRVRFC.INI file. The assignment of the connection data from the DRVRFC.INI to the PLC is established on the PC using the station number in the IDSEXEC.INI file.
3.
4. 5.
Commissioning
Warning:
When you set up the connection of the partner PC with the Plant iT Executive Server in the S7 hardware configuration, ensure that you do not use the same IP address for the partner PC as for the communication to the Plant iT Automation Unit Server. Although the two communications programs, Executive Server and Automation Unit Server, are served on the PC using the same network card, they always require two different IP addresses in their DRVRFC.INI files, and two different station numbers in the IDSEXEC.INI and AUSERVER.INI files.
Commissioning
5.2
Diagnosis of the Connection on the CP
If you have the impression that everything has been parameterized correctly, there is still the possibility that the connection between your communications module and the communications module of your peer is not established. This can be caused by hardware problems (cabling, bus terminals, hubs, equipotential bonding). However, there can also be incorrect parameterization in the communications modules. Check the parametrization of the module and the module of your peer. The NCM software for your communications module contains a function to test a connection. Use this to analyze the status of the connection. The manual for your communications module provides information about the troubleshooting capabilities.
5.3
Diagnostic Display in the DB_System
The status for every data connection is available in the System-DB of the basic driver. DBX 176.0 DBX 176.1 DBX 176.2 Status of the 1st connection (=parameter record 1 in the DB1020) Status of the 2nd connection (=parameter record 2 in the DB1020) Status of the 3rd connection (=parameter record 3 in the DB1020), etc.
TRUE = connection is OK FALSE = connection is faulty
5.4
Diagnostic Displays in the DB_DRV_TMT_Parameter
To simplify the test, diagnostic information has been stored in the parameter records of the DB_DRV_TMT_Parameter. This diagnostic information is supplied in every cycle. Extract from the DB_DRV_TMT_Parameter (DB1006):
Absolute byte no. 104 - 105 106 - 107 108 - 109 110 - 111 112 - 113 114 - 115 116 - 117 Relative Format byte no. 0-1 INT 2-3 4-5 6-7 8-9 10 - 11 12 - 13 INT INT INT INT INT INT Content +0 +0 +5000 +0 +0 +5 +0 P P P
Description
P P
Pointer to release flag (bit number) (S) Pointer to release flag (byte number) (S) Set time in ms (S) Actual time in ms (S) Good-telegrams counter (display) (S+R) DB number as data source or data target for the data block (S+R) Byte number in the source/target module where the data block begins (S+R)
Commissioning
Absolute byte no. 118 - 119
Relative Format byte no. 14 - 15 INT
Content +30 P
Description
121 122 123 124 125 126 127 128 129 130 - 131
17.0 18 - 19 20 21 22 23 24 25 26 - 27
BOOL INT BYTE BYTE BYTE BYTE BYTE BYTE INT
P FALSE +0 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 +10 P
Length of the source/target area in words (S+R) Send or receive (S+R) Send condition satisfied (S) Last error (display) (S+R) Time: year (BCD) (S+R) Time: month (BCD) (S+R) Time: day (BCD) (S+R)
Block number (S+R)
DBW 8:
Good-telegrams counter The DBW8 of every data record contains a counter that is always incremented by one when the contents of the parameterized DB can be successfully sent or when a received data block could be placed successfully in the target area. If the system was parameterized correctly, the contents of the data word must always be incremented after the set time you configured when you send data. Eventually an overflow will occur. The counter then restarts at 0. Last recognized error The most recently recognized error during sending or receiving of the data is always entered into DBW18. Errors recognized during the sending of data blocks
3 4 11 DB_DRV_TMT_Send is not present in the programmable controller DB_DRV_TMT_Send is too short (minimum 400 bytes) The receiver of the data cannot be reached. Causes: 1. The receiver station with its path has not been entered in the path list in the DB1023 starting at DBB364. 2. The number of released paths in the DB1023 DBW107 is too small. Timeout to the PC detected. Check whether a second transmit, not integrated in the driver, is called in the S7. The transmit job has been cancelled because of a cold restart or a warm restart. The telegram queue to the receiver station is not present in the S7. The DB parameterized in the data record does not exist (byte 10+11) The parameterized telegram length is too long for the CP (byte 14+15) The parameterized block number is < 1 (bytes 26+27) The DB parameterized in the data record DB is too short (bytes 12-15) The parameterized telegram length is less than 1 word (bytes 14-15) The set time and the edge flag were parameterized with 0 in the data The bit number for the release flag is > 7 Byte number for the release flag is too large for this CPU. Valid ranges are CPU414: range [1...1023] CPU416: range [1...2047] CPU417: range [1...16383] WinAC: range [1...2047]
DBW 18:
12 13 23
61 63 64 66 67 68 69 70
Commissioning
72
The DB parameterized in the data record has number 0 or a number too large for this CPU. Valid DB numbers are CPU414: range [1...1023] CPU416: range [1...4095] CPU417: range [1...8191] WinAC: r ange [1...65534]
Each last recorded error during the sending of data is also stored centrally in the "DB_DRV_TMT_Parameter" in the DBW 28. Errors recognized during the receiving of data blocks
8 10 33 34 35 36 37 DB_DRV_TMT_Recv is not present in the programmable controller DB_DRV_TMT_Recv is too short (minimum 400 bytes) The received PDA block contains no user data. The amount of user data for the received PDA block exceeds the parameterized maximum length in the target area. The target DB is too short for the received PDA block. The received telegram is not from service 10. The received telegram does not have telegram type 2.
Each last recorded error during the receiving of data is also stored centrally in the "DB_DRV_TMT_Parameter" in the DBW 40. An error can also occur during the receiving that cannot be assigned explicitly to a parameter data record and thus can only be stored centrally in the DBW40:
31 No parameter record for the received PDA block could be found in the Parameter DB. Either no parameter record was parameterized with this block number or the receiving bit is not set in the record (rel. DBX16.0)
The number of the received PDA blocks can also be read from DBW32 for error 31.
Recommendation: Categorization of the Process Information to be Recorded
The motivation of the plant operator to record the machine data varies widely. Depending on the plant operator, one or more of the following is applicable: Recording of consumption and produced quantities Cost accounting Reporting Recording of measured values and messages for the quality determination Recording of measured values and messages to meet legal requirements Weakness analysis Preventative maintenance Capacity determination for machines / plants.
To meet the requirements of the plant operator, data for the following categories must be recorded: Resource states, machine states, process line states, plant states Process messages and fault messages Counter values Measured values Switching cycles / operating times / maintenance signals.
The following sections aim to provide precise definitions for the terms used here.
6.1
Category: Resource State
Resource states are a mixture of fault messages and process messages. A resource state always provides the current status of a resource. A resource, such as a pump or a damper driver, could be in one of the following states: Off On in a manual operating mode, such as manual operation or set-up operation, etc. On in automatic operation Faulty
These information items must be present as consecutive bit information and so produce a 4-bit tetrade. An example using a pump: Bit 0: Bit 1: Bit 2: Bit 3: 0=pump is off, 0=manual mode, 0=pump has no fault, reserved 1=pump running 1=automatic mode 1= pump has a fault
This produces a 4-bit wide structure that is easy to count. Note that bit 2 can represent a collective fault bit for the resource. If, for example, you have a pump that can become faulty because of a failed motorcircuit breaker or a triggered thermal cut-out, you must OR the possible fault bits and apply to the bit 2. Expressed another way, if your resource is faulty, you must set bit 2, irrespective of the reason (failed motor-circuit breaker or triggered thermal cut-out) why your resource is faulty.
6.2
Category: Fault Messages
Fault messages (e.g. "Fallen bottle in the run-in") are designed to provide the plant operating personnel with exact information about a fault. It can always be assumed in the case of a fault message that something 'no longer operates as it should' and consequently intervention by the plant operating personnel is required. Fault messages are also required to create statistics that the personnel can use for preventative maintenance. A fault message is reported as a bit. The bit state '1' means fault, the bit state '0' means no fault. No statement can be made here as to whether the machine continues to operate or not. For example, a filling valve may be defective at a filling unit. This requires that the 'filling valve defective' fault bit be set although the filling unit can continue to produce. There is also no statement made as to whether this is a self-fault or an external fault. Thus, it is only the task of the fault bit to generate a message for the plant operating personnel, to color a symbol red for the visualization and to make statistical information available for the maintenance. It does not suffice just to apply a fault signal to bit 2 for a resource status. Rather, it is necessary that every possible fault sets an alarm bit. Only this permits a differentiation and makes it possible to provide the plant operating personnel with correct information. Please ensure that the fault bit you set does not 'flicker' because of an unfavorable logic. This would cause an incorrect creation of message and incorrect computations with regard to the availability of your machine / plant section.
6.3
Category: Process Messages
Similarly to fault messages, process messages are also designed to inform the plant operating personnel about specific conditions and to supply statistical information. However, a process message does not normally produce an information text for the plant operating personnel. Process messages are typically required for the visualization. The plant operating personnel, for example, is then graphically shown that the hoisting gear of a palleting unit is at the upper end position or that it is currently feeding containers into the upper gate, etc.
A process message is reported as a bit. The bit state '0' signals one state, the bit state '1' signals another state. For example, the bit state '1' of a process message could mean 'hoisting gear up' whereas the bit state '0' would mean 'hoisting gear not up'. Never apply the manual or automatic state of a resource to a bit from the process messages area. The Resource State category is provided for a manual or automatic signal of a resource. The Process Messages category is reserved for the operating states of your machine / plant section that do not represent a resource state. Typical process messages are hoisting gear in the upper or lower end position, etc.
6.4
Category: Overall Machine State / Overall Plant State
The overall machine state or also overall plant state specifies a general statement on the state of a machine/plant. If, for example, a "no product" external fault occurs at the filling machine of a filling line, the associated "no product" fault message of the "fault messages" category is set and also bit 6 for "external fault" set in the overall machine state, in addition the bit 3 "machine producing" is cleared. It is possible that several bits are set concurrently. For example, the bit 3 for "machine producing" can be set even when, for example, the bit 7 for a filling machine is set, if, for example, a filling valve is defective, thus the machine has a self-fault even though it can continue to fill.
6.4.1
Bit 0 : Machine ON
This bit must be set to 1 when the machine / process line is active.
6.4.2
Bit 1 : Manual / Semiautomatic Operation
If bit 0 is set to 1 and the machine is in manual or semiautomatic mode, then bit 1 must be set, otherwise it must be cleared. This bit indicates that the machine / process line is in a manual mode (manual, set-up operation, semiautomatic operation, etc.).
6.4.3
Bit 2 : Automatic Operation
If the bit 0 is set to 1 and the machine is in automatic operation, then bit 2 must be set, otherwise it must be cleared. This bit indicates that the machine is in automatic operation.
6.4.4
Bit 3 : Machine Producing
If a machine/plant is producing, then set bit 3. The machine/plant is producing when it satisfies the purpose for which it was sold. For example, this bit is set to 1 for a filling machine when bottles are being filled with the product. If, for example, the bottle gate of a machine is closed, this bit is set to 0, because the machine no longer produces. If, for example, a palleting unit could place crates on a pallet but does not receive any full crates, then it must set this bit to 0. It does not pallet. Consequently, this bit can only be set to 1 when the machine actually does what it should be doing.
6.4.5
Bit 4 : Deficiency
If a deficiency occurs at a machine in the run-in of the main product flow (for example, bottles, crates, etc.), this bit must be set to 1. Otherwise it must be set to 0. Typically the bit 3 ("machine producing") must be cleared when deficiencies occur in the main product flow (e.g. lack of bottles for a filling unit, lack of empty pallets for a palleting unit), because the machine can no longer perform the task for which it was sold. Because cyclical machines (e.g. a packing unit) through their means of operation can briefly assume a deficiency, this signal should be carried out for such machines only after a time delay. The deficiency signal may only be applied after a delay has expired and, in particular, when the machine has stopped working. The delay time to be used depends on the particular machine.
6.4.6
Bit 5 : Congestion
If congestion occurs in the run-out of the main product flow of a machine (for example, bottles, crates, etc.), this bit must be set to 1. Otherwise it must be set to 0. Typically, the occurrence of congestion at the main product flow (e.g. bottles congestion for a filling unit, full pallet congestion for a palleting unit) requires that bit 3 ("machine producing") be cleared, because the machine can no longer perform the task for which it was sold. Because cyclical machines (e.g. a packing unit) through their means of operation can briefly assume a congested state, this signal should be carried out for such machines only after a time delay. The congestion signal may only be applied after a delay has expired and, in particular, when the machine has stopped working. The delay time to be used depends on the particular machine.
6.4.7
Bit 6 : External Fault
If one or more faults occur at a machine/plant that were not caused by the machine/plant, then this bit 6 must be set to 1, otherwise to 0. For example, "product deficiency" or "run-in deficiency" at a filling machine. Typically the bit 3 ("machine producing") must be cleared when an external fault occurs (e.g. a bottle congestion at a filling unit, full pallet congestion at a palleting unit), because the machine can no longer perform the task for which it was sold.
6.4.8
Bit 7 : Self-Fault
If one or more faults occur at a machine/plant the causes of which are found in the machine/plant itself, then this bit 7 must be set to 1, otherwise to 0. Typically the bit 3 ("machine producing") must be cleared when a self-fault occurs (e.g. motor contactor fallen), because the machine can no longer perform the task for which it was sold. However, this is not mandatory. There are machines that can still perform their task even when a self-fault occurs, although often only with reduced capacity. For example, a filling unit for which a filling valve has failed. It must indicate this by setting the "filling valve defective" fault bit and it must also set this bit 7 "selffault" for the display of its machine overall status. If it can continue to fill despite the defective filling valve and also does this, the bit 3 ("machine producing") must still remain set to 1 as before.
6.4.9
Bit 8 to Bit 15 : For Special Tasks
The bits 8 to 15 are provided for special tasks and can be used only after consultation with the instance that realizes the PDA system.
6.5
Category: Plant States
The Plant States category describes the properties of the machine/plant. These properties include, for example, the selected product or the selected bottle container for a filling machine, the pallet type or the layer pattern for a palleting unit, or the bottle or crate type for a packing unit. To obtain a standardization of the "value for meaning" assignment, definitions specific for the plant but consistent within the plant should be agreed with the project instance responsible for the realization of the PDA. This applies, for example, to the filling container, the filling product, etc. For example, the description of the current filling container for the filling plant could have the following form:
Value 0 1 2 3 4 5 Meaning No container 0.2 l bottle 0.3 l bottle 0.5 l bottle 1.0 l bottle 1.5 l bottle
6.6
Counters Versus Measured Values
In practice, the meaning of a counter or a measured value is often not understood correctly. For this reason, the different meanings of these two categories will be further discussed here. A counter always counts a quantity. The value can only become larger (and never smaller) during the course of the production (of an order, of a batch). Examples of counters: Bottles, pallets, crates, but also quantities such as water consumption, compressed air consumption, processed product quantity. A measured value never records a quantity. Measured values record values that can become larger but also smaller again. Examples of measured values: Temperatures, capacities (such as bottles/h or crates/h), pressures, such as the production pressure of the compressed air supply.
6.6.1
Category: Counters
Counters are recorded exclusively in double data format, i.e. 32-bit wide. If a device exists at the machine that can be used to reset the counters to "0, the affected data for the counter must to be present twice. The value is counted once with reset and once without reset. The data item counted with the reset has the "(w.R)" code suffixed to its designation. The data item counted without this reset has the "(n.R)" code suffixed to its designation. Thus, if you have a machine that supplies a counter but which cannot be reset at the machine, it suffices when you provide this counter as a "circulating counter". If you have a machine that supplies a counter, which, for example, is cleared before or at the end of a product run (reset to 0), you must provide this counter as both a "circulating counter" and as an "absolute counter". The "absolute counter" is the value that, for example, you would display as text. It will always increase during the production; it is reset to 0 at the end (or also before the start) of production. Although you supply both the "circulating counter" and the "absolute counter", you must never reset the circulating counter to 0. Thus, the circulating counter will become increasingly large and will at some stage no longer fit in a double word. This produces an "overflow" in the double word. You can handle this overflow very simply. Simply clear bit 31 of the double word after assigning the value. This limits the number to the maximum value 7FFF FFFF hexadecimal. If you supply a counter both with and without reset, you must ensure that both counters are coherent. This means that you must feed both counters in the same cycle. It must not arise that a cycle lies between changing the value of the counter without reset and changing the value of the counter with reset. This would lead to an incorrect acquisition, display and statistics.
6.6.2
Category: Measured Values
In contrast to counter values that change by an amount n, measured values are data subject to a smooth change (e.g. C, mbar etc.). A width of 16 bits normally suffices to record measured values. This means that you have to feed one measured value per data word. A special situation can occur during the recording of measured values. If, for example, you record a measured value using a PT100 or use an external measuring unit with a serial coupling, it is possible that the connection to the PT100 or the external measuring unit is interrupted. In this case you cannot supply a correct measured value because you do not know it. A special flag is provided for this situation. If you are not supplied with a measured value, then set the data word in which you would normally enter the measured value to the hexadecimal value KH 8000 (decimal -32768). It is your decision whether you provide the measured value evaluated or unevaluated. The control system can always perform a linear analysis using gradient/ordinate. Note: Ensure that the measured value always fits in the data word. Because the data word of a measured value is considered to be signed, you are provided with a value range of +32767 to -32767. As described above, the value -32768 is used as the "measured value not available" flag. If your measured value does not fit in a data word, you can also use a double word. Ensure here, however, that the value KH8000 0000 is entered for a wire breakage in the double data item instead of the value KH8000.
6.7
Maintenance Information
Maintenance information typically has the single purpose to permit the acquisition for the preventative maintenance. Whether machine switching cycles, operating times, or both, need to be supplied depends on the type of your machine and the requirements you give to the plant operator demands for the preventative maintenance. If, for example, your maintenance schedule contains the requirement that an inspection must be performed after 20000 cycles and bearings must be replaced after 60000 cycles, then you must also supply cycles. If, for example, you have a maintenance requirement that lubrication work must be performed after 1000 hours of operation, then you must supply operating hours.
6.7.1
Category: Switching Cycles
A switching cycle is typically characterized as being the movement from an initial position into the action state and back to the initial position. Example: A switching cycle is counted when a valve changes from the "closed" state to the "open" state and then back again to the "closed" state.
Example: An eccentric drive performs exactly one revolution to raise and lower a drive. Whether you return this wear in the form of cycles or operating hours depends on the requirements you give to the plant operator. Switching cycles are treated as "circulating counters". Thus, you must supply a double word for each switching cycle and then clear bit 31 of this double word afterwards to avoid a wrap.
6.7.2
Category: External Operating Times
For those machine parts subject to a continuous load (e.g. drives for conveyors, etc.), the running time of the resource is typically recorded as being the operating time. The operating time is understood to be the time which the component is under load and thus subject to wear. Operating times are treated like "circulating counters". Thus, you must supply a double word for each operating time and then clear bit 31 of this double word afterwards to avoid a wrap. Operating times have seconds as the unit.
6.7.3
Category: Internal Operating Times
For the External Operating Times category, you build an operating hours counter in your controller program and supply its value to the control system. For the Internal Operating Times category, it suffices when you supply a signal indicating that a drive is running. The control system can build the operating hours counter for you in this mode. However, it is only appropriate to use this mode when the shortest regular running time of your drive exceeds 100 seconds. This achieves an average error rate of less than 1 %. The reason for this is that the control systems typically perform time measurements with a resolution of 1 second. The data transfer on the network also distorts the times. If you already feed your drive in the Resource State category that control system can sample there the signal for the operating hours counter. If you wish to supply an internal signal for the operating times but are not concerned with the resource state, then supply this signal in the Process messages category.
6.7.4
Category: Maintenance Signal
Some machines require maintenance work to be performed that is independent of a cycle count and the operating time, but that depends on an event. An example would be an oil container with a level switch. Oil must be refilled when the level in the container falls below a certain level. If your machine provides such a maintenance signal, then assign this bit in the Process Messages category.
Recommendation: Module Structures
Depending on the category, the controller must transfer the process data fast or less fast to the control system. The communications modules represent the bottleneck for the couplings. To make optimum use of these capabilities, it is appropriate to combine the data in various data modules depending on your speed of updating. If only very little data are to be recorded and the complete system (consisting of servers, network, communications modules and controllers) is capable of processing all the values in a second cycle, then no further investigation is necessary. In practice, this situation occurs very seldom. In general, the following rule can be recommended: If possible, the Resource States, Fault Messages, Process Messages, Machine Overall State categories should be transferred in the 1 second cycle to the control system. The updating speed for the Measured Values category depends on the measured value's possible speed of change and on the sampling rate. For example, it is not sensible to transfer a temperature at 1 second rate to the control system if a temperature change of 1 degree takes an hour. It would suffice to transfer the temperature measured value in a minute cycle. For the Counters category, the update speed depends on whether the value is used for the visualization, how fast it is to be updated and how fast the value changes in the controller. Experience has shown that it suffices to transfer counters in the 5 second cycle from the controller to the control system. For the Switching Cycles and Operating Hours categories, it would suffice to transfer them once per day. These categories usually have a 5 minute cycle. As a consequence of these conditions and the typical quantities involved, the following distribution has proved useful: 1 data module for resource states, fault messages, process messages 1 data module for counters 1 data module for measured values (also two or three modules when there is a large difference in the times) 1 data module for switching cycles 1 data module for operating hours. To permit a module to also be transferred over a Profibus it is always assumed that a module to be transferred is never longer than 64 data words incl. the telegram header. If, for example, a data module for counters is not adequate, an additional data module can obviously be created for counters. This makes it necessary to uniformly identify the data modules for the control system. This identification must be unique throughout the plant. An identification using the controller number and the block number has proved useful. The instance that the control system installed, assigns the controller number uniquely throughout the plant. The block number identifies a data block (a data module) within a controller. You can yourself assign this block number.
You must forward the description of a data block, namely the block number and the assignment of the individual bits, words and double words, to the instance that the control system installed. An Excel work folder that has been developed for the documentation of this information simplifies the documentation .
7.1
Resource States, Fault Messages, Process Messages, Plant States, Machine/Plant Overall States
The following diagram shows the assignment of the user data for these categories. The allocation of the user data area is a recommendation. If, for example, you can manage with significantly less than 128 process messages but require correspondingly more fault messages, then simply move the boundary. However, ensure that you move the boundary right from the beginning. If the control system has already been configured and you want to (or must) move the boundary, this requires an enormous effort. It is better to create an additional data module in such a case.
DBB 0 : 42 44 : 58 60 : 74 76 : 107 108 : 113 Fault messages 352 bits, fault messages
Process messages
128 bits, process messages
Plant states
16 bytes, states
Resource states
64 tetrades, resource states
Machine/plant state
3 words, machine/plant state
The following table shows the detailed assignment at the bit level:
DBB 0 : : : : 43 44 : : : : 59 60 : : : : 75 76 : : : : 107 7 FM FM FM FM FM FM PM PM PM PM PM PM 6 FM FM FM FM FM FM PM PM PM PM PM PM 5 FM FM FM FM FM FM PM PM PM PM PM PM 4 3 FM FM FM FM FM FM FM FM FM FM FM FM PM PM PM PM PM PM PM PM PM PM PM PM Plant state Plant state Plant state Plant state Plant state Plant state 2 FM FM FM FM FM FM PM PM PM PM PM PM 1 FM FM FM FM FM FM PM PM PM PM PM PM 0 FM FM FM FM FM FM PM PM PM PM PM PM
Resource state Resource state Resource state Resource state Resource state Resource state
Resource state Resource state Resource state Resource state Resource state Resource state
108 109 110 111 112 113
Machine/plant overall state Machine/plant overall state Machine/plant overall state
Legend: FM Bit-coded fault message, 1-bit wide, 0=no fault, 1=fault present Bit-coded process message, 1-bit wide, 0=operating state a, 1= operating state b
PM
Binary-coded plant state, value range 0-255 Binary-coded resource state, 4-bit wide: Bit 0: 0=resource is off, 1= resource is running Bit 1: 0= resource in manual mode/subautomatic, 1=resource in automatic Bit 2: 0=no fault, 1=fault present Bit 3: eserved Binary-coded machine/plant overall state, 16-bit wide: Bit 0: 1=machine on Bit 1: 1=machine in manual mode/subautomatic Bit 2: 1=machine in automatic operation Bit 3: 1=machine is producing Bit 4: 1=deficiency in the main product flow Bit 5: 1=congestion in the main product flow Bit 6: 1=external fault Bit 7: 1=self-fault Bit 8-15 reserved, must remain as 0.
7.2
Counters
The following diagram shows the assignment of the user data area for the Counters category. The allocation in the user data area is a recommendation.
DBW 0 : : : : : : :
DBW 110
Counters
28 double words, counters
The following table shows the detailed assignment at bit level.

7 DBB 0 DBB 1 2 3 : : : : : : : 108 109 110 111 6 5 4 3 2 1 0 32-bit counter, most-significant word 32-bit counter, least-significant word
32-bit counter, most-significant word 32-bit counter, least-significant word
7.3
Measured Values
The following diagram shows the assignment of the user data area for the Measured Values category. The allocation in the user data area is a recommendation.
DBB 0 : : : : : : : DBW 112
Measured values
57 words, measured values

7 DBB 0 1 2 3 : : : : : 110 111 112 113 6 5 4 3 2 16-bit measured value 16-bit measured value 1 0
16-bit measured value 16-bit measured value
Note:
If you create measured values for which it makes no sense to sample in a 1 second cycle, you should create two or more data modules. You use one of these for fast measured values and the other for slower measured values. You assign different block numbers to the two data modules. This means that unnecessary amounts of data are not sent over the bus, which could possibly place an excessive load on it.
7.4
Switching Cycles
The following diagram shows the assignment of the user data area for the Switching Cycles category. The allocation in the user data area is a recommendation.
DBB 0 : : : : : : : DBB 110
Switching cycles
28 double words, switching cycles

7 DBB 0 1 2 3 : : : : : 108 109 110 111 6 5 4 3 2 1 0 32-bit switching cycle counter, mostsignificant word 32-bit switching cycle counter, leastsignificant word
32-bit switching cycle counter, mostsignificant word 32-bit switching cycle counter, leastsignificant word
7.5
Operating Times
The following diagram shows the assignment of the user data area for the Operating Times category. The allocation in the user data area is a recommendation.
DBB 0 : : : : : : : DBW 110
Operating times
28 double words, operating times

DBB 0 1 2 3 : : : : : 108 109 110 111 7 6 5 4 3 2 1 0 32-bit operating times, most-significant word 32-bit operating times, least-significant word
32-bit operating times, most-significant word 32-bit operating times, least-significant word
Appendix
8
8.1
Appendix
Telegram Structure
This chapter describes the structure of the PDA (process data acquisition) telegram. The telegram header is explained using a data module. If you do not want to use the Transmit standard software, you can yourself send the PDA telegrams, provided you adhere to the following structure.
8.1.1
PDA Telegram Service 10, Type 1 (Timestamp in Second-Coding)
This telegram format is no longer supported in the S7.
8.1.2
PDA Telegram Service 10, Type 2 to/from the Executive Server
The following table shows the structure of the telegram header when a send is made to the Executive Server or when a telegram is received from the Executive Server in the PLC. The " TMT_Main" generates this telegram header for every telegram in the "DB_TMT_Send" send mailbox (DB1001 or DB30 in the delivered system) when it sends data from the PLC to the Executive Server. The telegram with the structure described below is present starting at DBW0 in the "DB_TMT_Receive" receive mailbox (DB1002 or DB29 in the delivered system) when it is received. The "TMT_Main" assigns the user data (starting at DBW 38) from the receive mailbox in the parameterized target area.
DBW 0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 : : 00 0A 00 01 Source station Target station Length in words 00 00 00 00 01 Length in words Source station Block number 00 Year Month Day Hour Minute Second 00 All user data start here User data 02 00 00 00 7 words, header information for PDA block 06 00 00 01 6 words, Plant iT Core protocol
6 words, Plant iT Service protocol
Appendix

7 DBB 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 6 5 3 2 00 06 0A 00 00 00 01 01 Source station Target station Length in words 00 02 00 00 00 00 00 00 00 01 Length in words Source station 00 Block number 00 00 Year, tens Month, tens Day, tens Hour, tens Minute, tens Seconds, tens 4 1 0
Note:
The first byte of a word (the byte with the smaller number) is the most significant byte of the word; the second byte is the least significant byte of the word. The Executive Server expects first the most significant byte and then the least significant byte as the sequence for the arrival of the telegram. The telegram fields of the telegram for sending from the PLC to the Executive Server are described below. This permits you to send your own telegrams without requiring the use of the Transmit. When such a telegram is received, only the information from the source and target station is interchanged (affects DBW8, DBW10 and DBW26). The telegram fields of the telegram to the Collect handled at the end are a subset of this description.
Appendix
DBB 0-7: These data words must have a fixed format as described in the table. All details are hexadecimal. DBW 8: The station number of the controller is specified in DBW 8. DBW 10: The station number of the partner (Executive Server) is specified in DBW 10. DBW 12: The number of words starting with DBW 12 and including the last word of the telegram (i.e., the last word of the user area) is specified in DBW 12. DBB 14-23: These cells must have a fixed format as described in the table. All details are hexadecimal. DBW 24: The number of words starting with DBW 24 and including the last word of the telegram (i.e., the last word of the user area) is specified in DBW 24. DBW 26: The station number of the controller is specified in DBW 26. DBB 28: DBB 28 must always have the fixed value 0. DBB 29: The block number for the data block is specified in DBB 29. DBW 30: DBW 30 must always have the fixed value 0. DBW 32-37: Bytes 32-37 contain a timestamp. The six bytes must be set completely to the value 0 or contain valid date/time details when sending. If all six bytes contain 0, the Executive Server provides its own time when the telegram arrives. The timestamp values are always supplied in Greenwich Mean Time (GMT) without daylight saving. The values must always be entered BCD-packed (Siemens standard format). Each byte contains 2 digits to the base 10. Consequently, the following assignments are available to the timestamp: DBB 32: Year, value range 00 to 99 BCD Bit 0-3 units value of the year, value range 0-9 Bit 4-7 tens value of the year, value range 0-9 DBB 33: Month, value range 01-12 BCD Bit 0-3 units value of the month, value range 0-9 Bit 4-7 tens value of the month, value range 0-1 DBB 34: Day, value range 01-31 BCD Bit 0-3 units value of the day, value range 0-9 Bit 4-7 tens value of the day, value range 0-3 DBB 35: Hour, value range 00-23 BCD Bit 0-3 units value of the hour, value range 0-9 Bit 4-7 tens value of the hour, value range 0-2
Appendix
DBB 36: Minute, value range 00-59 BCD Bit 0-3 units value of the minute, value range 0-9 Bit 4-7 tens value of the minute, value range 0-5 DBB 37: Seconds, value range 00-59 BCD Bit 0-3 units value of the seconds, value range 0-9 Bit 4-7 tens value of the seconds, value range 0-5
8.1.3
PDA Telegram, Service 10, Type 2 to the Acquis iT Collect
The following table shows the structure of the telegram header when sent to the Collect. The "TMT_Main" in the standard software of the Transmit generates this telegram header for every telegram in the send mailbox "DB_TMT_Send" (DB1001 or DB30 for the delivered system). Only the missing Plant iT protocol (Core+Service protocol) distinguishes this telegram from the telegram to the Executive Server.
DBW 0 2 4 6 8 10 12 14 : : Length in words Source station 00 Block number 00 Year Month Day Hour Minute Seconds User data 7 words, header information for PDA block
All user data start here
The following table shows the assignment of the telegram header at bit level.
7 DBB 0 1 2 3 4 5 6 7 8 9 10 11 12 13 6 5 4 3 2 Length in words Source station 00 Block number 00 00 Year, tens Month, tens Day, tens Hour, tens Minute, tens Seconds, tens 1 0
Note:
The first byte of a word (the byte with the smaller number) is the most significant byte of the word; the second byte is the least significant byte of the word. The Executive Server expects first the most significant byte and then the least significant byte as the sequence for the arrival of the telegram. The descriptions of the telegram fields for the telegram to the Executive Server follow. The telegram fields of the telegram to the Collect handled at the end are a subset of this description.
Appendix
DBW 0: The number of words starting with DBW 0 and including the last word of the telegram (i.e., the last word of the user area) is specified in DBW 0. DBW 2: The station number of the controller is specified in DBW 2. DBB 4: DBB 4 must always have the fixed value 0. DBB 5: The block number for the data block is specified in DBB 5. DBW 6: DBW 6 must always have the fixed value 0. DBW 8-13: Bytes 8-13 contain a timestamp. The six bytes must be set completely to the value 0 or contain valid date/time details. If all six bytes contain 0, the Executive Server provides its own time when the telegram arrives. The timestamp values are always supplied in Greenwich Mean Time (GMT) without daylight saving. The values must always be entered BCD-packed (Siemens standard format). Each byte contains 2 digits to the base 10. Consequently, the following assignments are available to the timestamp: DBB 8: Year, value range 00 to 99 BCD Bit 0-3 units value of the year, value range 0-9 Bit 4-7 tens value of the year, value range 0-9 DBB 9: Month, value range 01-12 BCD Bit 0-3 units value of the month, value range 0-9 Bit 4-7 tens value of the month, value range 0-1 DBB 10: Day, value range 01-31 BCD Bit 0-3 units value of the day, value range 0-9 Bit 4-7 tens value of the day, value range 0-3 DBB 11: Hour, value range 00-23 BCD Bit 0-3 units value of the hour, value range 0-9 Bit 4-7 tens value of the hour, value range 0-2 DBB 12: Minute, value range 00-59 BCD Bit 0-3 units value of the minute, value range 0-9 Bit 4-7 tens value of the minute, value range 0-5 DBB 13: Seconds, value range 00-59 BCD Bit 0-3 units value of the seconds, value range 0-9 Bit 4-7 tens value of the seconds, value range 0-5
Appendix
8.1.4
Clock Telegram, Service 10, Type 3 from Executive Server
The following table shows the structure of the clock telegram when the system clock of the PLC per telegram is synchronized from the PC (only for S7-300) For receiving, the telegram is stored with the structure described below in the receive mailbox of S7-300 "DB_TMT_Receive" starting at DBW0 (DB29 for the supplied system). The "TMT_Main" represents with the transferred clock (local time or GMT) the system clock of the PLC.
DBW 0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 00 0A 00 01 Source station Destination station 000E 00 00 00 00 00 Year Day Minute Month Hour Seconds 1/100 second Year Month Day Month Minute Seconds 1/100 second BCD clock (local time) 02 00 00 00 06 00 00 01 6 words Plant iT Core protocol
6 words Plant iT Service protocol
BCD clock (GMT)
DBW 24-38: Bytes 24-31 contain the timestamp for local time, bytes 32-39 contain the timestamp for GMT. The values are packed-BCD (Siemens standard format). 2 digits to base 10 are transferred per byte. The following assignments apply to the timestamp in the two ranges: Year, value range 00 to 99 BCD Bit 0-3 units digit for the year, value range 0-9 Bit 4-7 tens digit for the year, value range 0-9 Month, value range 01-12 BCD Bit 0-3 units digit of the month, value range 0-9 Bit 4-7 tens digit of the month, value range 0-1 Day, value range 01-31 BCD Bit 0-3 units digit of the day, value range 0-9 Bit 4-7 tens digit of the day, value range 0-3 Hour, value range 00-23 BCD Bit 0-3 units digit of the hour, value range 0-9 Bit 4-7 tens digit of the hour, value range 0-2 Minute, value range 00-59 BCD Bit 0-3 units digit of the minute, value range 0-9 Bit 4-7 tens digit of the minute, value range 0-5 Seconds, value range 00-59 BCD Bit 0-3 units digit of the seconds, value range 0-9 Bit 4-7 tens digit of the seconds, value range 0-5
Appendix
8.2
Example: Create a Counter in the DINT Format with Overflow Processing
The listing of a small sample program that follows shows how a double data item can be realized as a 32-bit counter with overflow processing. The program can run on all CPUs of the S7-300 or S7-400. It is printed as ASCII source code. The symbolic operands have the following meanings: CMD Command flag; a change from 0 to 1 causes an increment to the counter EDGE Edge flag CTR Double word 32-bit counter If the counter is contained in a data module, then the data module must be opened before this sample program is invoked.
FUNCTION FC99: VOID TITLE = AUTHOR: FAMILY: NAME: VERSION: Double word counter with overflow processing MA IDS_TOOL ZAEHL32 01.00 //Change from 0 to 1 -> increment //counter command
VAR_INPUT CMD : BOOL; END_VAR VAR_IN_OUT EDGE : BOOL; CTR : DINT; END_VAR BEGIN NETWORK TITLE =
//Edge for counted y/n //32-bit counter
Counter in double-word format with overflow processing //Counter command not present? //Then clear "counted" edge //and end //Command present and already "counted"? //then end //We count, set edge
UN CMD; R EDGE; BEB; U EDGE; BEB; S EDGE;
L DW#16#7FFF_FFFF; L CTR; //Double word counter ==I; //just before overflow SPB REST; //then wrap L 1; +D; //Otherwise increase by 1 T CTR; BEA; REST: L 0; T CTR; // Set double word = 0 BE; END_FUNCTION
Appendix
8.3
Error Recognized from Acquis iT Transmit
The software for the Transmit in the S7 was created with the Simatic Manager and there with the source text editor. For the subsequent compiler run, the documentation preheaders in datablocks are not currently displayed. However, because all important error acknowledgements of the Transmit in the S7 are still stored in the DB preheaders, the following section shows an extract of these modules from the source code listing. This listing is useful for the commissioning when you want to work exclusively with the compiled S7 data modules. Values that the configuring engineer must set are identified with the "P:" code in the comment. Values that you must configure in order to send a datablock from the PLC to the Collect or Executive Server are identified with an "(S)" in the comment. Values that you must configure in order to receive a data block from the Executive Server in your own PLC are identified with an "(R)" in the comment.
// Note: Global errors, such as "DB_DRV_TMT_Parameter" does not // exist, etc. are returned using the symbolic operand PAFE of //the FC "TMT_Main". // // ===================================================== // ERROR NUMBERS IN THE GENERAL PART OF THE PARAMETER DB: // ===================================================== // // Errors that are detected while receiving PDA blocks are stored // in DBW 40. The receiving of PDA blocks must be explicitly // enabled in DBX 12.4. // // 30 The station number for the receiver in the telegram does not agree with the own station number in the DBW8 // Parameter DB. // 31 No parameter set in the Parameter DB exists for the // received PDA block (identified using the PDA block // number from the telegram) // 32 The target DB for the received PDA block does not exist // in the PLC // 33 The received PDA block contains no application data // 34 The size of the application data of the received PDA // block exceeds the parameterizedmaximum length in the // target area // 35 The target DB is too short for the received PDA block // 36 The received telegram is not from service 10 // 37 The received telegram does not have telegram type 2 // // In addition to the errors that are detected during the // evaluation of the telegrams,the errors supplied directly from // the communikation module are also stored here. These error // numbers lie in the range 8000h-8FFF (hexadecimal) and are // listed at the end of the error numbers for the parameter set. // // // ================================== // ERROR NUMBERS IN THE PARAMETER SET: // ================================== // // The rel. byte 18+19 always contains an error number when an // error is detected. This helps you to recognize and rectify // incorrect parameterizations. The error number always applies // to the record or the DB that contains the telegram to be sent. // // // 0 No error occurred
Appendix
// // The range 61 to 79 contains parameterization errors from the // user's parameter sets: // ================================================================= // 61 The DB parameterized in the data record does not exist // (byte 10+11) // 63 The parameterized telegram length is too large for the // CP (byte 14+15) // 64 The parameterized block number is < 1 (byte 26+27) // 66 The DB parameterized in the data record is too short // (byte 12-15) // 67 The parameterized telegram length is smaller than 1 word // (byte 14-15) // 68 The set time and the edge flag have been parameterized // with 0 in the data record (e.g. bytes 0-5 have been // preassigned with 0). The program does not further // process this record, but the subsequent data record will // be processed as previous. // 69 Bit number for the release flag is > 7 // 70 Byte number for the release flag is too large for this // CPU. Valid ranges are // CPU312: range [1..127] // CPU313 - 316: range [1..255] // CPU412/413: range [1..511] // CPU414: range [1..1023] // CPU416: range [1..2047] // 71 The DB parameterized in the data record is write // protected // 72 The DB parameterized in the data record has the number 0 // or a number that is too large // for this CPU. Valid DB numbers are // CPU312: range [1..63] // CPU313 - 316: range [1..127] // CPU412/413: range [1..511] // CPU414: range [1..1023] // CPU416: range [1..4095] // 128 Illegal response in the status of the HTB Send // In addition, the following error numbers of the communication // module are also stored here: // // The range 8000h-8FFFh contains the error numbers of the CP // (in hexadecimal): // ================================================================= // 8183h The configuring is missing or the ISO transport service // in the Ethernet-CP has not yet been started // 8184h System error // 8185h LEN parameter larger than the source area // 8186h ID parameter invalid. Valid range for Ethernet [1..64], // for Profibus [1..32] // 8301h SAP not activated at the target station // 8302h No receive resources for the target station, receive // station cannot process the received data // sufficiently fast or no receive resources provided // 8303h The SDA service (Send Data with Acknowledge) is not // supported by the target station on this SAP // 8304h The ISO transport connection has not been established // 8311h Target station cannot be reached using the specified // Ethernet address // 8312h Ethernet error in the CP // 8F22h Source area invalid, e.g. area not present in the DB, // parameter LEN < 0 // 8F24h Range area while reading a parameter // 8F28h Alignment error while reading a parameter // 8F32h Parameter contains a DB-number that is too large // 8F33h DB-number error // 8F3Ah Area not loaded (DB) // 8F42h Acknowledgment delay while reading a parameter from the // peripheral area
Appendix
// 8F44h Address of the parameter to be read disabled in the // access track // 8F7Fh Internal error, e.g. invalid ANY reference, e.g. LEN=0 // 8090h Module with this address not present // 8091h Module start address not on a double word boundary // 80B0h Module does not recognize the data record // 80B1h Target area is invalid, e.g. target area > 240 bytes // 80B2h The K-bus-connection between CPU and CP has not been // established // 80C0h Data record cannot be read // 80C1h The specified data record is currently being processed // 80C2h An order congestion has occurred // 80C3h The resource (memory) of the CPU is temporarily o // ccupied // 80C4h Communications error // 80D2h Module start address is incorrect // Selection from the preheader of the "TMT_Main" FC with the error numbers and error texts for the PAFE return value. FUNCTION TMT_Main: VOID TITLE = Transmit cyclical part //=============================================================== // TRANSMIT SEND FOR SIEMENS S7 -300/400 //=============================================================== // // Transmit for Siemns S7 - 300/400 // Copyright by PROLEIT, Herzogenaurach // All rights reserved ! // // // INVOCATION: In OB1 and after cold restart OB100/101 // // INVOCATION PARAMETER: None // // RESPONSE: // PAFE: // 0= No parameterization error // ><0 Parameterization error: // 1 The DB-no. of the "DB_DRV_TMT_Parameter" is zero or larger than // allowed in the CPU // 2 The parameter sets start before DBW100 in the "DB_DRV_TMT_Parameter" // 3 The "DB_DRV_TMT_Parameter" is too short (because of DBW2) // 4 The "DB_DRV_TMT_Parameter" is too short (because of structure) // 7 The "DB_DRV_TMT_Parameter" does not exist // 10 The "DB_DRV_TMT_Send" has zero DB-no. or is larger than allowed // in the CPU // 11 The "DB_DRV_TMT_Send" does not exist // 13 The "DB_DRV_TMT_Send" is too short (minimum length 240 bytes) // 15 The flag count could not be read from the CPU after a cold // restart // 16 The DB count could not be read from the CPU after a cold // restart // 17 The "DB_DRV_TMT_Receive" has zero DB-no. or is larger than // allowed in the CPU // 18 The "DB_DRV_TMT_Receive" does not exist // 19 The "DB_DRV_TMT_Receive" is too short (minimum length 240 // bytes)
Notes

AiT PR Interface-PLC-Transmit SI en

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

AiT PR Interface-PLC-Transmit SI en

Încărcat de

Drepturi de autor:

Formate disponibile

Acquis iT Transmit Siemens S7

VVersion V8.00 (Edition March 2009)

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 2

Acquis iT Transmit Siemens S7 3

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 4

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 5

Process data bus

Machine controler Transmit

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 6

Using Acquis iT Transmit in the WinAC

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 7

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 8

Parameterize the Global Variables

Uhrzeit_ergaenzen BOOL FreigabeTimeSync LocalTime BOOL BOOL

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 9

Parameterize the PDA Data Blocks to be Sent/Received

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 10

FALSE P FALSE +0 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 +10

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 11

Acquis iT Transmit Siemens S7 12

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 13

FALSE P FALSE +0 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 P +10

DBW 0 + DBW 2 DBW 4 DBW 10 DBW 12 DBW 14 DBX 16.0 DBW 26

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 14

FALSE P FALSE +0 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 +10 P

Send a single data block on release by the application program

FALSE FALSE +0 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 +10 P

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 15

DBW 0 DBW 2 DBW 4 DBW 10 DBW 12 DBW 14 DBX 16.0 DBW 26

Receive a data block

TRUE P FALSE +0 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 B#16#00 +11 P

DBW 10 DBW 12 DBW 14 DBX 16.0 DBW 26

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 16

Supply/Clear the User Data Blocks

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 17

Test the Connection Parameters

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 18

Steuerung mit Acquis iT Transmit

DB1006 Partner station x

CP443 List of connection ID a IP-adresses TSAPs ID b IP-adresses TSAPs ID c IP-adresses TSAPs

List of stations station x station y station z ...

PC with Plant iT Executive Server

PLC station k PLC station l PLC station m

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 19

Plant iT V8.00 (Edition March 2009) R26

Acquis iT Transmit Siemens S7 20