ait pr interface-plc-transmit si en

8/14/2019 AiT Pr Interface-PLC-Transmit SI En

1/48

VVersion V8.00 (Edition March 2009)

Acqu i s iT Transmi t Siemens S7


2/48

Acquis iT Transmit Siemens S72

Plant iT V8.00 (Edition March2009)R26

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 issubject to the license conditions.

ProLeiT AGEinsteinstrae 8, D-91074 HerzogenaurachTel.: +49 9132 / 777-0Fax: +49 9132 / 777-150eMail: [email protected]://www.proleit.de

Hotline:

eMail: [email protected]

Plant iT V8.00 (Edition March 2009) Acquis iT Transmit Siemens S7R26, Edition: 12/06/2007

AiT_pr_Interface-PLC-Transmit_SI_en.doc

Designations for hardware and software mentioned in this manual are in mostcases also registered trademarks of the owner and should be considered as

such.
http://www.proleit.com/http://www.proleit.com/


3/48


4/48

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


5/48

Introduction



1 Introduction Acquis iT Transmit is a standard software package for controllers. Its task is toprovide parameterized facilities to send process data for the acquisition andarchiving from the controller to an acquisition system. Transmit also can also beused to receive process data in the PLC.

The following section describes the operation and parameterization. You willalso 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 ifyou have any questions, you can recommend improvements, you would like tohave your wishes catered for, or have just found errors. We would be pleasedto call you back if you give your name and fax/telephone number.


6/48

Method of Operation



2 Method of Operation Acquis iT is a system for plant data acquisition. It allows the Plant iT ExecutiveServer on the PC to acquire any data, irrespective of whether this involvesmessages, counter values or maintenance information, or whether the datarelates 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 usingtelegrams.

Acquis iT Transmit, together with the Plant iT basic driver, performs this task inthe PLC: The Acquis iT Transmit fetches the data to be acquired from thesource areas of the PLC and transfers this to the Plant iT basic driver, which isresponsible for the buffering and the actual sending of the telegrams to the PC.

The TCP/IP (RFC1006) protocols are supported as transmission protocols.

Process data bus

Server MS SQL Server Configuration Server Executive Server

WorkstationMS ExcelConfiguration ClientSelectWork

Machine controler Transmit

Figure 1: Control lers send using TCP/IP (RFC1006) to the Executive Server

When used in the SoftPLC WinAC, both the Acquis iT Executive Server and thePLC components (Acquis iT Transmit and basic driver) are stored on the samePC.


7/48

Technical Description



3 Technical Descr ipt ion

3.1 Components of Acquis iT Transmit

Acquis iT Transmit is a parametrizable standard software component of thePlant iT basic driver. It consists of two datablocks and two function module.

Symbolic Name S7-400/WinAC module Description DRV_TMT_Main FC1002 Fetches the data to be sent from the data sources of

the PLCDRV_Service10 FC1001 Writes the received data in the target areas of the PLCDB_DRV_TMT_Parameter DB1006 DB for parametrizationDB_DRV_TMT_Send DB1007 Work areaTMT_Parameter UDT1001 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 driverwhen 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 inthe "DB_TMT_Parameter". When you receive data, you must parameterizehere that target area in the PLC. The "TMT_Parameter" structure defines theparameter records in the "DB_TMT_Parameter".

The FC "DRV_TMT_Main" transfers the data to be sent to the basic driver inthe "DB_TMT_Send" datablocks.

The data connection to the PC with the Plant iT Executive Server must beparameterized in the basic driver. The supplied basic driver already has anoperational 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 thebasic driver. No further WinAC-specific settings need to be made in the AcquisiT Transmit parameters.

3.3 Default Settings

To simplify the first test with the Transmit software, it is supplied with twoparameter records already preparameterized in the"DB_DRV_TMT_Parameter" so that you can immediately send user data to anExecutive Server with the station number 100.Here, 50 data words are sent from the DB5 in a time cycle of 5 seconds and 50data words from the DB6 in a time cycle of 1 second. When this parametrizationexample is no longer required, you can use the parameter records 1 and 2 inthe "DB_DRV_TMT_Parameter" for your own applications and delete the DB5and DB6.


8/48


9/48

Configuring



4 ConfiguringThe 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" forsending/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 areaand an area that contains a data record for each data block to be sent/received.

This section describes the global variables.

Extract f rom the "DB_DRV_TMT_Parameter" :DBW 2: Par t nerSt ati on I NT 100 P: St ati on number of t he server

wi t h Acqui s i T Execut i veServer

DBX 4.0: Uhr zei t _er gaenzen BOOL TRUE P: FALSE: wi t hout t i me, TRUE: wi t h t i me

DBX 4.1: Fr ei gabeTi meSync BOOL FALSE P: TRUE: anal yze t el egr am wi t ht i me f or sync syst emcl ock

DBX 4.2 Local Ti me BOOL FALSE P TRUE: Ti mesync usi ng l ocalt i me,

FALSE: usi ng GMT

Only those global variables from the "DB_DRV_TMT_Parameter" on whichsettings can be made are listed here.

The parametrization of the actual data connection is made in the basic driveritself. The "Installation of the Basic Drivers" manual provides support here. Theprovided manual also describes in short form the data connection to the AcquisiT 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 iTExecutive Server. This is the station to which you wish to send the data or fromwhich 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 to65535 are permitted.


10/48

Configuring



DBX 4.0: TimeSet this bit to specify that the telegrams from your controller are always sentwith the time of your controller. However, this makes sense only when the clockin your controller is maintained from a central clock! If you set this bit at 0, thedata is sent without timestamp. The Executive Server recognizes this when it

receives the telegram and then automatically assigns the time when thetelegram arrived at the Windows NT Server. The latter is the recommendedmethod.

FALSE = 0 Send data without the time from the PLC (the Executive Serveradds the time when the telegram is received)

TRUE = 1 Send data with the time from the PLC

DBX 4.1: Enable time synchronization via telegramThis functionality was originally needed for the CPUs of the S7-300 whosesystem clock cannot be synchronized directly using the inserted CP module.Consequently, it is possible the synchronize the system clock time of the PLCvia telegrams from the PC.

FALSE = 0 time synchronization in the PLC via telegram is deactivatedTRUE = 1 time synchronization in the PLC via telegram is active

DBX 4.1: Clock synchroni zation with local time or GMTIf you have enabled the synchronization of the PLC system clock by telegramusing DBX4.1, you can select here whether the system clock is to be set withthe local time or GMT.

FALSE = GMTTRUE = local time

4.2 Parameterize the PDA Data Blocks to beSent/Received

A data record exists in the "DB_DRV_TMT_Parameter" for each data block tobe sent or received. This data record describes which data blocks are to besent and which send criterion is to be used, or in which data block the receiveddata is to be stored.

You must parameterize the lines shown bold. They are also marked in the DBwith a "P:". (S) or (R) in the comment indicates parameters that need to be setfor the sending or receiving of data blocks, respectively. Parameters with an(S+R) are needed for both transmission directions.


11/48

Configuring



Selection from the "DB_DRV_TMT_Parameter" in the sample file:(P= to be parameterized by the user)

Absolutebyte no.

Relativebyte no.

Format Content Description

100 - 101 / INT +14 Length of the parameter record inwords102 - 103 / INT +2 P Number of valid parameter

records (S+R) 104 - 105 0 - 1 INT +0 P Pointer to release flag (bit

number) (S) 106 - 107 2 - 3 INT +0 P Pointer to release flag (byte

number) (S) 108 - 109 4 - 5 INT +5000 P Set time in ms (S) 110 - 111 6 - 7 INT +0 Actual time in ms (S)112 - 113 8 - 9 INT +0 Good-telegrams counter (display)

(S+R)114 - 115 10 - 11 INT +5 P DB number as data source or

data target for the data block(S+R)

116 - 117 12 - 13 INT +0 P Byte number in the source/targetmodule where the data blockbegins (S+R)

118 - 119 14 - 15 INT +101 P Length of the source/target areain words (S+R)

120 16.0 BOOL FALSE P Send or receive (S+R) 121 17.0 BOOL FALSE Send condition satisfied (S)122 - 123 18 - 19 INT +0 Last error (display) (S+R)124 20 BYTE B#16#00 Time: year (BCD) (S+R)125 21 BYTE B#16#00 Time: month (BCD) (S+R)126 22 BYTE B#16#00 Time: day (BCD) (S+R)127 23 BYTE B#16#00 Time: hour (BCD) (S+R)128 24 BYTE B#16#00 Time: minute (BCD) (S+R)129 25 BYTE B#16#00 Time: second (BCD) (S+R)130 - 131 26 - 27 INT +10 P: Block number (S+R)

A data record is always 14 data words (= 28 bytes) long. The first data recordstarts at DBB 104 in the "DB_DRV_TMT_Parameter". The data records mustbe contiguous. Thus, the second data record starts at DBB 132, the third startsat 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 beentered, ensure that the data record length (14) is entered in DBW 100 and theDB 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 followingsection describes the data words that you must parameterize. The numbering ofthe individual data items does not refer to the byte number in the data block butthe byte number within a record. The first byte within a record is designated asDBB 0, similarly, the first byte within a data block is designated as DBB 0. Set tothe 0 value all data in the records that you do not need to configure.


12/48

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 ofthe corresponding data block depends on an explicit release of the applicationprogram. The value range for the byte number of the flag depends on theassociated CPU type:

CPU 414: flag byte [1 ... 1023]CPU 416: flag byte [1 ... 2047]CPU 417: flag byte [1 ... 16383]WinAC: flag byte [1 ... 2047]

If this parameter is initialized with 0, the program recognizes that no release flagwas parameterized and only operates with the set time from DBW 4.

DBW 4: Set time in mil liseconds (S)Enter here the time to be used for the send interval. If, for example, you wish tosend a data block every 2 seconds, enter here the value 2000 for 2000milliseconds. 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, theprogram itself sets the parameter to 500 ms. This is the smallest permittedvalue; smaller values could very quickly overload the complete system. Werecommend 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 whichthe received data is to be stored. The value range for the DB number dependson the associated CPU type:

CPU 414: DB-no. [1 ... 1023]CPU 416: DB-no. [1 ... 4095]

CPU 417: DB-no. [1 ... 8191]WinAC: DB-no. [1 ... 65534]

DBW 12: Begin byte number (S+R)Enter here the byte number of your DB where the data to be sent starts or thestarting location for the received data is to be stored. The DB length and thusthe byte number depends on the associated CPU type. The following listassumes 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 30words, then enter the value 30 here.

Note the maximal permitted value here! This depends on the maximumtelegram block length "Blocklen" in the DBW164 of the DB1023 "DB_System".The following table shows the maximum send length for the user datadepending on the set block length.

Telegram block leng th in the DB1023 Max. send length f or user d ata 120 words 101 words200 words 181 words

For receiving (R):Enter here the maximum length of the target area in words. Transmit will reject


13/48

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. Themaximum length of the target area is subject to the same dependencies as thetelegram 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 thesending or the receiving of a data block. Accordingly, the parameterized datablock represents the source for the data to be sent or the target for the receiveddata.

FALSE = send a data blockTRUE = 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 toassign the configured data to your data blocks. The Executive Server does notknow your data blocks. Consequently, it needs another characteristic for theassignment. This characteristic is the block number. Thus, you must assign adifferent, namely unique, block number for each data block that you send. Youcan use any number in the range 1-255 for this purpose. The block numbermust be unique within your controller.

For receiving (R):Transmit uses the block number contained in the telegram to search for theassociated parameter record in the "DB_DRV_TMT_Parameter". Theparameter record provides it with the information about the position and lengthof 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 Variant 1 Variant 2 Variant 3 Variant 4 DBW 0 bit number +0 +x +x +0DBW 2 byte number +0 +y +y +0DBW 4 set time +z +z +0 +0

Variant 1 Send a telegram in the fixed time interval without requiring a specific releasefrom the application program.

Variant 2 Send a telegram in the fixed time interval with release from the applicationprogram using M y,x. In this case sending continues until the applicationprogram resets M y.x.

Variant 3 Send a telegram once with release from the application program using the My,x flag. Here, the data block is sent just once and then the Transmit softwareresets the release flag back to 0. In this case, the user himself must organizethe time-related behavior for sending the data.

Variant 4 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 theparameter record. However, all other data blocks are sent provided such aparametrization does not apply to them.


14/48

Configuring



Example: Send a data block with the time cycle of 5000 ms in continuous operation

Absolutebyte no.

Relativebyte no.


104 - 105 0 - 1 INT +0 P Pointer to release flag (bit number)(S)

106 - 107 2 - 3 INT +0 P Pointer to release flag (bytenumber) (S)

108 - 109 4 - 5 INT +5000 P Set time in ms (S)110 - 111 6 - 7 INT +0 Actual time in ms (S)112 - 113 8 - 9 INT +0 Good-telegrams counter (display)



116 - 117 12 - 13 INT +4 P Byte number in the source/targetblock w here the data blockbegins (S+R)


120 16.0 BOOL FALSE P Send or receive (S+R) 121 17.0 BOOL FALSE Send condition satisfied (S)122 - 123 18 - 19 INT +0 Last error (display) (S+R)124 20 BYTE B#16#00 Time: year (BCD) (S+R)125 21 BYTE B#16#00 Time: month (BCD) (S+R)126 22 BYTE B#16#00 Time: day (BCD) (S+R)127 23 BYTE B#16#00 Time: hour (BCD) (S+R)128 24 BYTE B#16#00 Time: minute (BCD) (S+R)129 25 BYTE B#16#00 Time: second (BCD) (S+R)130 - 131 26 - 27 INT +10 P Block number (S+R)

DBW 0 + DBW 2 = 0 No release flag parameterizedDBW 4 = 5000 The data is sent every 5 secondsDBW 10 = 10 The data is contained in the module with number 10DBW 12 = 4 The data to be sent starts at byte 4 in the DB10DBW 14 = 30 30 words are to be sentDBX 16.0 = FALSE The parametrization is used to send a data blockDBW 26 = 10 The data receives block number 10

Example: Send a data block wi th the time cycl e of 5000 ms on release by theapplication program in the M99.1.

Absolutebyte no.

Relativebyte no.


104 - 105 0 - 1 INT +1 P Pointer to release flag (bitnumber) (S)


108 - 109 4 - 5 INT +5000 P Set time in ms (S) 110 - 111 6 - 7 INT +0 Actual time in ms (S)112 - 113 8 - 9 INT +0 Good-telegrams counter (display)





15/48

Configuring



Absolutebyte no.

Relativebyte no.



120 16.0 BOOL FALSE P Send or receive (S+R) 121 17.0 BOOL FALSE Send condition satisfied (S)122 - 123 18 - 19 INT +0 Last error (display) (S+R)124 20 BYTE B#16#00 Time: year (BCD) (S+R)125 21 BYTE B#16#00 Time: month (BCD) (S+R)126 22 BYTE B#16#00 Time: day (BCD) (S+R)127 23 BYTE B#16#00 Time: hour (BCD) (S+R)128 24 BYTE B#16#00 Time: minute (BCD) (S+R)129 25 BYTE B#16#00 Time: second (BCD) (S+R)130 - 131 26 - 27 INT +10 P Block number (S+R)

DBW 0 = 1 Bit number of the release flagDBW 2 = 99 Byte number of the release flagDBW 10 = 10 The data is contained in the module with number 10DBW 12 = 4 The data to be sent starts at byte 4 in the DB10DBW 14 = 30 30 words are to be sentDBX 16.0 = FALSE The parametrization is used to send a data blockDBW 26 = 10 The data receives block number 10

Example: Send a sing le data block on release by the application program

Absolutebyte no.

Relativebyte no.


104 - 105 0 - 1 INT +1 P Pointer to release flag (bitnumber) (S)


108 - 109 4 - 5 INT +0 P Set time in ms (S) 110 - 111 6 - 7 INT +0 Actual time in ms (S)112 - 113 8 - 9 INT +0 Good-telegrams counter (display)





120 16.0 BOOL FALSE Send or receive (S+R)

121 17.0 BOOL FALSE Send condition satisfied (S)122 - 123 18 - 19 INT +0 Last error (display) (S+R)124 20 BYTE B#16#00 Time: year (BCD) (S+R)125 21 BYTE B#16#00 Time: month (BCD) (S+R)126 22 BYTE B#16#00 Time: day (BCD) (S+R)127 23 BYTE B#16#00 Time: hour (BCD) (S+R)128 24 BYTE B#16#00 Time: minute (BCD) (S+R)129 25 BYTE B#16#00 Time: second (BCD) (S+R)130 - 131 26 - 27 INT +10 P Block number (S+R)


16/48

Configuring



DBW 0 = 1 Release flag is M 99.1DBW 2 = 99 The data is sent just once and the release is then reset.DBW 4 = 0DBW 10 = 10 The data is contained in the module with number 10DBW 12 = 4 The data to be sent starts at byte 4 in the DB10

DBW 14 = 30 30 words are to be sentDBX 16.0 = FALSE The parametrization is used to send a data blockDBW 26 = 10 The data receives block number 10

Example: Receive a data bloc k Absolutebyte no.

Relativebyte no.


104 - 105 0 1 INT +0 P Pointer to release flag (bitnumber) (S)

106 - 107 2 3 INT +0 P Pointer to release flag (bytenumber) (S)

108 - 109 4 - 5 INT +0 P Set time in ms (S) 110 - 111 6 - 7 INT +0 Actual time in ms (S)

112 - 113 8 - 9 INT +0 Good-telegrams counter (display)(S+R)114 - 115 10 - 11 INT +20 P DB number as data source or




120 16.0 BOOL TRUE P Send or receive (S+R) 121 17.0 BOOL FALSE Send condition satisfied (S)122 - 123 18 - 19 INT +0 Last error (display) (S+R)

124 20 BYTE B#16#00 Time: year (BCD) (S+R)125 21 BYTE B#16#00 Time: month (BCD) (S+R)126 22 BYTE B#16#00 Time: day (BCD) (S+R)127 23 BYTE B#16#00 Time: hour (BCD) (S+R)128 24 BYTE B#16#00 Time: minute (BCD) (S+R)129 25 BYTE B#16#00 Time: second (BCD) (S+R)130 - 131 26 - 27 INT +11 P Block number (S+R)

DBW 10 = 20 The received data should be stored in the module with number 20DBW 12 = 6 The data should be stored starting at byte 6 in the DB 20DBW 14 = 30 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.

DBX 16.0 = TRUE The parametrization is used to receive a data blockDBW 26 = 11 Only data that arrives with block number 11 in the PLC is stored in the

target area


17/48

Configuring



4.3 Supply/Clear the User Data Blocks

Generally, you are responsible for how and when you supply process data tothe sending data blocks. However, the data must be assigned to the datablocks 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 forslower sampling in a different data block. Thus, for example, one data block cansend with a cycle time of 1000 milliseconds while the other data block sendswith a cycle time of 5000 milliseconds.

Similar conditions also exist for receiving: you most process the data at least asfast 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 ofprocess data within a data block.

A standard for filling plants has crystallized over the course of time. Many itemsfrom this standard can also be used for other production areas, such asbrewhouses, packing plants, etc.

You should contact the person responsible for the parametrization of theExecutive Server. He can answer the question whether and which standard isbeing employed.


18/48

Commissioning



5 CommissioningOnce you have performed all parameterization work and transferred thesoftware 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 thenetwork 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 DB1023and DB1020. The Siemens NCM software must be used to enter the connectioninto the connection table for the communications module.

note : The manual for the installation of the basic driver provides a guide for thisparametrization.

To simplify troubleshooting, the following section describes the interactionbetween the set parameters of an TCP/IP connection. A general schematicoverview is provided first. The same overview is then shown in more detailusing the current parameters as supplied.


19/48

Commissioning



DB1006 DB1023

Partner station x

List of stationsstation xstation ystation z...

parameters of

connectionto station x:LADDRID a

parameters ofconnection tostation y:

parameters ofconnection tostation z:

DB1020

...

CP443

List of connectionID a

IP-adressesTSAPs

ID bIP-adressesTSAPs

ID cIP-adressesTSAPs

Steuerung mit cquis iT Transmit

TCP/IP

PLC station kIP adressesTSAPs

PLC station lIP adressesTSAPs

PLC station mIP adressesTSAPs

DRVRFC.INIIDSEXEC.INI

PLC station k

PLC station l

PLC station m

1 2 3

4

5

PC withPlant iT Executive Server

Figure 1: Overview: Connection parameters for control and PC

1. The partner station from the DB1006 must be contained in the stationlist in the system DB 1023 for the basic driver.

2. The position of the partner station in the station list of the basic driverdetermines the parameter record in the DB1020 with the connectionparameters for the communications module. Whereposition 1 in the station list in the DB1023 points to the 1st record in theDB1020,position 2 in the station list in the DB1023 points to the 2nd record in theDB1020,etc.

3. The parameterized connection-ID in the record of the DB1020 points tothe associated entry in the connection table. The IP address and the TSAPsto the connection partner are stored on the communications module (CP).

4. The partner to the entry in the connection table of the CP is stored onthe PC in the DRVRFC.INI file.

5. The assignment of the connection data from the DRVRFC.INI to thePLC is established on the PC using the station number in the IDSEXEC.INIfile.


20/48

Commissioning



Warning: When you set up the connection of the partner PC with the Plant iT ExecutiveServer in the S7 hardware configuration, ensure that you do not use the sameIP address for the partner PC as for the communication to the Plant iT

Automation Unit Server.

Although the two communications programs, Executive Server and AutomationUnit Server, are served on the PC using the same network card, they alwaysrequire two different IP addresses in their DRVRFC.INI files, and two differentstation numbers in the IDSEXEC.INI and AUSERVER.INI files.


21/48

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 parameterizationin the communications modules.

Check the parametrization of the module and the module of your peer. TheNCM software for your communications module contains a function to test aconnection. Use this to analyze the status of the connection. The manual foryour communications module provides information about the troubleshootingcapabilities.

5.3 Diagnostic Display in the DB_System

The status for every data connection is available in the System-DB of the basicdriver.

DBX 176.0 Status of the 1st connection(=parameter record 1 in the DB1020)

DBX 176.1 Status of the 2nd connection(=parameter record 2 in the DB1020)

DBX 176.2 Status of the 3rd connection(=parameter record 3 in the DB1020), etc.

TRUE = connection is OKFALSE = connection is faulty

5.4 Diagnostic Displays in the DB_DRV_TMT_Parameter

To simplify the test, diagnostic information has been stored in the parameterrecords of the DB_DRV_TMT_Parameter. This diagnostic information issupplied in every cycle.

Extract from the DB_DRV_TMT_Parameter (DB1006):

Absolutebyte no.

Relativebyte no.


104 - 105 0 - 1 INT +0 P Pointer to release flag (bit number)(S)


108 - 109 4 - 5 INT +5000 P Set time in ms (S)110 - 111 6 - 7 INT +0 Actual time in ms (S)112 - 113 8 - 9 INT +0 Good-telegrams counter (display)

(S+R)114 - 115 10 - 11 INT +5 P DB number as data source or data

target for the data block (S+R)116 - 117 12 - 13 INT +0 P Byte number in the source/target

module where the data blockbegins (S+R)


22/48

Commissioning



Absolutebyte no.

Relativebyte no.


118 - 119 14 - 15 INT +30 P Length of the source/target area inwords (S+R)

P Send or receive (S+R)

121 17.0 BOOL FALSE Send condition satisfied (S)122 123 18 - 19 INT +0 Last erro r (disp lay) (S+R) 124 20 BYTE B#16#00 Time: year (BCD) (S+R)125 21 BYTE B#16#00 Time: month (BCD) (S+R)126 22 BYTE B#16#00 Time: day (BCD) (S+R)127 23 BYTE B#16#00128 24 BYTE B#16#00129 25 BYTE B#16#00130 - 131 26 - 27 INT +10 P Block number (S+R)

DBW 8: Good-telegrams coun ter

The DBW8 of every data record contains a counter that is always incrementedby one when the contents of the parameterized DB can be successfully sent orwhen a received data block could be placed successfully in the target area. Ifthe system was parameterized correctly, the contents of the data word mustalways be incremented after the set time you configured when you send data.Eventually an overflow will occur. The counter then restarts at 0.

DBW 18: Last recognized errorThe most recently recognized error during sending or receiving of the data isalways entered into DBW18.

Errors recognized during the sending of data blocks

3 DB_DRV_TMT_Send is not present in the programmable controller

4 DB_DRV_TMT_Send is too short (minimum 400 bytes)11 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 theDB1023 starting at DBB364.2. The number of released paths in the DB1023 DBW107 is too small.

12 Timeout to the PC detected. Check whether a second transmit, not integrated inthe driver, is called in the S7.

13 The transmit job has been cancelled because of a cold restart or a warm restart.23 The telegram queue to the receiver station is not present in the S7.61 The DB parameterized in the data record does not exist (byte 10+11)63 The parameterized telegram length is too long for the CP (byte 14+15)64 The parameterized block number is < 1 (bytes 26+27)66 The DB parameterized in the data record DB is too short (bytes 12-15)67 The parameterized telegram length is less than 1 word (bytes 14-15)68 The set time and the edge flag were parameterized with 0 in the data69 The bit number for the release flag is > 770 Byte number for the release flag is too large for this

CPU. Valid ranges areCPU414: range [1...1023]CPU416: range [1...2047]CPU417: range [1...16383]WinAC: range [1...2047]


23/48

Commissioning



72 The DB parameterized in the data record has number 0 or a number too large forthis CPU. Valid DB numbers areCPU414: 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 inthe "DB_DRV_TMT_Parameter" in the DBW 28.

Errors recognized during the receiving of data blocks

8 DB_DRV_TMT_Recv is not present in the programmable controller10 DB_DRV_TMT_Recv is too short (minimum 400 bytes)33 The received PDA block contains no user data.34 The amount of user data for the received PDA block exceeds the parameterized

maximum 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.

Each last recorded error during the receiving of data is also stored centrally inthe "DB_DRV_TMT_Parameter" in the DBW 40. An error can also occur duringthe receiving that cannot be assigned explicitly to a parameter data record andthus can only be stored centrally in the DBW40:

31 No parameter record for the received PDA block could be found in the ParameterDB. Either no parameter record was parameterized with this block number or thereceiving bit is not set in the record (rel. DBX16.0)

The number of the received PDA blocks can also be read from DBW32for error 31.


24/48

Recommendation: Categorization of the Process Information to be Recorded



6 Recommendation: Categorization of theProcess 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 categoriesmust 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 usedhere.

6.1 Category: Resource State

Resource states are a mixture of fault messages and process messages. Aresource 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-upoperation, etc.

On in automatic operation

Faulty


25/48




These information items must be present as consecutive bit information and soproduce a 4-bit tetrade. An example using a pump:

Bit 0: 0=pump is off, 1=pump runningBit 1: 0=manual mode, 1=automatic mode

Bit 2: 0=pump has no fault, 1= pump has a faultBit 3: reserved

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, forexample, you have a pump that can become faulty because of a failed motor-circuit breaker or a triggered thermal cut-out, you must OR the possible faultbits 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 ortriggered 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 theplant operating personnel with exact information about a fault. It can always beassumed in the case of a fault message that something 'no longer operates asit should' and consequently intervention by the plant operating personnel isrequired. Fault messages are also required to create statistics that thepersonnel 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 machinecontinues to operate or not. For example, a filling valve may be defective at afilling unit. This requires that the 'filling valve defective' fault bit be set althoughthe filling unit can continue to produce. There is also no statement made as towhether this is a self-fault or an external fault. Thus, it is only the task of thefault bit to generate a message for the plant operating personnel, to color asymbol red for the visualization and to make statistical information available forthe 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 thispermits a differentiation and makes it possible to provide the plant operatingpersonnel with correct information.

Please ensure that the fault bit you set does not 'flicker' because of anunfavorable logic. This would cause an incorrect creation of message and

incorrect computations with regard to the availability of your machine / plantsection.

6.3 Category: Process Messages

Similarly to fault messages, process messages are also designed to inform theplant operating personnel about specific conditions and to supply statisticalinformation. However, a process message does not normally produce aninformation text for the plant operating personnel. Process messages aretypically required for the visualization. The plant operating personnel, forexample, 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 uppergate, etc.


26/48




A process message is reported as a bit. The bit state '0' signals one state, thebit state '1' signals another state. For example, the bit state '1' of a processmessage 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 theprocess messages area. The Resource State category is provided for a manualor automatic signal of a resource.

The Process Messages category is reserved for the operating states of yourmachine / plant section that do not represent a resource state. Typical processmessages 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 generalstatement 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 "noproduct" 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 "machineproducing" is cleared.

It is possible that several bits are set concurrently.

For example, the bit 3 for "machine producing" can be set even when, forexample, the bit 7 for a filling machine is set, if, for example, a filling valve isdefective, 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 bit1 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, semiautomaticoperation, 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 mustbe set, otherwise it must be cleared. This bit indicates that the machine is inautomatic operation.


27/48




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 filledwith the product. If, for example, the bottle gate of a machine is closed, this bitis set to 0, because the machine no longer produces.

If, for example, a palleting unit could place crates on a pallet but does notreceive 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 doeswhat it should be doing.

6.4.5 Bit 4 : DeficiencyIf a deficiency occurs at a machine in the run-in of the main product flow (forexample, bottles, crates, etc.), this bit must be set to 1. Otherwise it must be setto 0.

Typically the bit 3 ("machine producing") must be cleared when deficienciesoccur in the main product flow (e.g. lack of bottles for a filling unit, lack of emptypallets for a palleting unit), because the machine can no longer perform the taskfor which it was sold.

Because cyclical machines (e.g. a packing unit) through their means ofoperation can briefly assume a deficiency, this signal should be carried out forsuch machines only after a time delay. The deficiency signal may only beapplied after a delay has expired and, in particular, when the machine hasstopped working. The delay time to be used depends on the particular machine.

6.4.6 Bit 5 : Congesti on

If congestion occurs in the run-out of the main product flow of a machine (forexample, bottles, crates, etc.), this bit must be set to 1. Otherwise it must be setto 0.

Typically, the occurrence of congestion at the main product flow (e.g. bottlescongestion for a filling unit, full pallet congestion for a palleting unit) requires

that bit 3 ("machine producing") be cleared, because the machine can no longerperform the task for which it was sold.

Because cyclical machines (e.g. a packing unit) through their means ofoperation can briefly assume a congested state, this signal should be carriedout for such machines only after a time delay. The congestion signal may onlybe applied after a delay has expired and, in particular, when the machine hasstopped working. The delay time to be used depends on the particular machine.


28/48




6.4.7 Bit 6 : External Fault

If one or more faults occur at a machine/plant that were not caused by themachine/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 faultoccurs (e.g. a bottle congestion at a filling unit, full pallet congestion at apalleting unit), because the machine can no longer perform the task for which itwas sold.

6.4.8 Bit 7 : Self-Fault

If one or more faults occur at a machine/plant the causes of which are found inthe 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-faultoccurs (e.g. motor contactor fallen), because the machine can no longerperform the task for which it was sold.

However, this is not mandatory. There are machines that can still perform theirtask 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 thisby setting the "filling valve defective" fault bit and it must also set this bit 7 "self-fault" for the display of its machine overall status. If it can continue to fill despitethe 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 TasksThe bits 8 to 15 are provided for special tasks and can be used only afterconsultation with the instance that realizes the PDA system.

6.5 Category: Plant States

The Plant States category describes the properties of the machine/plant. Theseproperties include, for example, the selected product or the selected bottlecontainer for a filling machine, the pallet type or the layer pattern for a palletingunit, or the bottle or crate type for a packing unit.

To obtain a standardization of the "value for meaning" assignment, definitionsspecific for the plant but consistent within the plant should be agreed with theproject instance responsible for the realization of the PDA. This applies, forexample, to the filling container, the filling product, etc. For example, thedescription of the current filling container for the filling plant could have thefollowing form:

Value Meaning 0 No container1 0.2 l bottle2 0.3 l bottle3 0.5 l bottle4 1.0 l bottle

5 1.5 l bottle


29/48




6.6 Count ers Versus Measured Values

In practice, the meaning of a counter or a measured value is often notunderstood correctly. For this reason, the different meanings of these twocategories will be further discussed here.

A counter always counts a quantit y.The value can only become larger (and never smaller) during the course of theproduction (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 quantit y.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 theproduction 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 countedonce with reset and once without reset. The data item counted with the resethas 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 resetat the machine, it suffices when you provide this counter as a "circulatingcounter".

If you have a machine that supplies a counter, which, for example, is clearedbefore or at the end of a product run (reset to 0), you must provide this counteras 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 alsobefore 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 counterwill become increasingly large and will at some stage no longer fit in a doubleword. This produces an "overflow" in the double word. You can handle thisoverflow very simply. Simply clear bit 31 of the double word after assigning thevalue. 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 bothcounters are coherent. This means that you must feed both counters in thesame cycle. It must not arise that a cycle lies between changing the value of thecounter without reset and changing the value of the counter with reset. Thiswould lead to an incorrect acquisition, display and statistics.


30/48




6.6.2 Category : Measured Values

In contrast to counter values that change by an amount n , measured values aredata subject to a smooth change (e.g. C, mbar etc.).

A width of 16 bits normally suffices to record measured values. This means thatyou have to feed one measured value per data word.

A special situation can occur during the recording of measured values. If, forexample, you record a measured value using a PT100 or use an externalmeasuring unit with a serial coupling, it is possible that the connection to thePT100 or the external measuring unit is interrupted. In this case you cannotsupply a correct measured value because you do not know it. A special flag isprovided for this situation. If you are not supplied with a measured value, thenset the data word in which you would normally enter the measured value to thehexadecimal value KH 8000 (decimal -32768).

It is your decision whether you provide the measured value evaluated orunevaluated. The control system can always perform a linear analysis usinggradient/ordinate.

Note: Ensure that the measured value always fits in the data word. Because the dataword of a measured value is considered to be signed, you are provided with avalue range of +32767 to -32767. As described above, the value -32768 is usedas the "measured value not available" flag.

If your measured value does not fit in a data word, you can also use a doubleword. Ensure here, however, that the value KH8000 0000 is entered for a wirebreakage in the double data item instead of the value KH8000.

6.7 Maintenance InformationMaintenance information typically has the single purpose to permit theacquisition for the preventative maintenance.

Whether machine switching cycles, operating times, or both, need to besupplied depends on the type of your machine and the requirements you give tothe plant operator demands for the preventative maintenance.

If, for example, your maintenance schedule contains the requirement that aninspection must be performed after 20000 cycles and bearings must bereplaced after 60000 cycles, then you must also supply cycles.

If, for example, you have a maintenance requirement that lubrication work mustbe performed after 1000 hours of operation, then you must supply operatinghours.

6.7.1 Category: Switching Cycles

A switching cycle is typically characterized as being the movement from aninitial 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 tothe "open" state and then back again to the "closed" state.


31/48




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 dependson the requirements you give to the plant operator.

Switching cycles are treated as "circulating counters". Thus, you must supply adouble word for each switching cycle and then clear bit 31 of this double wordafterwards 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 theoperating time. The operating time is understood to be the time which thecomponent is under load and thus subject to wear.

Operating times are treated like "circulating counters". Thus, you must supply adouble word for each operating time and then clear bit 31 of this double wordafterwards 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 hourscounter in your controller program and supply its value to the control system.

For the Internal Operating Times category, it suffices when you supply a signalindicating that a drive is running. The control system can build the operatinghours counter for you in this mode.

However, it is only appropriate to use this mode when the shortest regularrunning time of your drive exceeds 100 seconds. This achieves an averageerror rate of less than 1 %. The reason for this is that the control systemstypically perform time measurements with a resolution of 1 second. The datatransfer on the network also distorts the times.

If you already feed your drive in the Resource State category that controlsystem can sample there the signal for the operating hours counter.

If you wish to supply an internal signal for the operating times but are notconcerned 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 independentof 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 refilledwhen the level in the container falls below a certain level.

If your machine provides such a maintenance signal, then assign this bit in theProcess Messages category.


32/48

Recommendation: Module Structures



7 Recommendation: Module StructuresDepending on the category, the controller must transfer the process data fast orless fast to the control system.

The communications modules represent the bottleneck for the couplings. Tomake optimum use of these capabilities, it is appropriate to combine the data invarious data modules depending on your speed of updating.

If only very little data are to be recorded and the complete system (consisting ofservers, network, communications modules and controllers) is capable ofprocessing all the values in a second cycle, then no further investigation isnecessary. In practice, this situation occurs very seldom.

In general, the follow ing rul e can be recommended:

If possible, the Resource States, Fault Messages, Process Messages, MachineOverall State categories should be transferred in the 1 second cycle to thecontrol system.

The updating speed for the Measured Values category depends on themeasured value's possible speed of change and on the sampling rate. Forexample, it is not sensible to transfer a temperature at 1 second rate to thecontrol system if a temperature change of 1 degree takes an hour. It wouldsuffice to transfer the temperature measured value in a minute cycle.

For the Counters category, the update speed depends on whether the value isused for the visualization, how fast it is to be updated and how fast the valuechanges in the controller. Experience has shown that it suffices to transfercounters 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, thefollowing 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 isa 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 assumedthat a module to be transferred is never longer than 64 data words incl. thetelegram header.

If, for example, a data module for counters is not adequate, an additional datamodule can obviously be created for counters. This makes it necessary touniformly identify the data modules for the control system. This identificationmust be unique throughout the plant. An identification using the controllernumber and the block number has proved useful. The instance that the controlsystem 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.


33/48




You must forward the description of a data block, namely the block number andthe assignment of the individual bits, words and double words, to the instancethat the control system installed. An Excel work folder that has been developedfor 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 thesecategories. The allocation of the user data area is a recommendation. If, forexample, you can manage with significantly less than 128 process messagesbut require correspondingly more fault messages, then simply move theboundary. However, ensure that you move the boundary right from thebeginning. 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 tocreate an additional data module in such a case.

DBB 0: Fault messages 352 bits, fault messages4244: Process messages 128 bits, process messages5860: Plant states 16 bytes, states7476: Resource states 64 tetrades, resource states107108

: Machine/plant state 3 words, machine/plant state113

The following table shows the detailed assignment at the bit level:

7 6 5 4 3 2 1 0DBB 0 FM FM FM FM FM FM FM FM

: FM FM FM FM FM FM FM FM: FM FM FM FM FM FM FM FM: FM FM FM FM FM FM FM FM: FM FM FM FM FM FM FM FM43 FM FM FM FM FM FM FM FM44 PM PM PM PM PM PM PM PM: PM PM PM PM PM PM PM PM: PM PM PM PM PM PM PM PM: PM PM PM PM PM PM PM PM: PM PM PM PM PM PM PM PM59 PM PM PM PM PM PM PM PM60 Plant state: Plant state: Plant state: Plant state: Plant state75 Plant state76 Resource state Resource state: Resource state Resource state: Resource state Resource state: Resource state Resource state: Resource state Resource state107 Resource state Resource state


34/48




108 Machine/plant overall state109110 Machine/plant overall state111112 Machine/plant overall state113

Legend:

FM Bit-coded fault message, 1-bit wide,0=no fault,1=fault present

PM Bit-coded process message, 1-bit wide,0=operating state a,1= operating state b

Binary-coded plant state, value range 0-255

Binary-coded resource state, 4-bit wide:

Bit 0: 0=resource is off, 1= resource is runningBit 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 onBit 1: 1=machine in manual mode/subautomaticBit 2: 1=machine in automatic operationBit 3: 1=machine is producingBit 4: 1=deficiency in the main product flowBit 5: 1=congestion in the main product flowBit 6: 1=external faultBit 7: 1=self-faultBit 8-15 reserved, must remain as 0.

7.2 Counters

The following diagram shows the assignment of the user data area for theCounters category. The allocation in the user data area is a recommendation.

DBW 0:::: Counters 28 double words, counters:::

DBW 110


35/48




The following table shows the detailed assignment at bit level.

7 6 5 4 3 2 1 0DBB 0 32-bit counter, most-significant wordDBB 1

2 32-bit counter, least-significant word3:::::::108 32-bit counter, most-significant word109110 32-bit counter, least-significant word111

7.3 Measured Values

The following diagram shows the assignment of the user data area for theMeasured Values category. The allocation in the user data area is arecommendation.

DBB 0:::: Measured values 57 words, measured values:

::

DBW 112


7 6 5 4 3 2 1 0DBB 0 16-bit measured value

12 16-bit measured value3::

:::110 16-bit measured value111112 16-bit measured value113


36/48




Note: If you create measured values for which it makes no sense to sample in a 1second cycle, you should create two or more data modules. You use one ofthese for fast measured values and the other for slower measured values. Youassign different block numbers to the two data modules. This means thatunnecessary 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 theSwitching Cycles category. The allocation in the user data area is arecommendation.

DBB 0:::: Switching cycles 28 double words, switching: cycles::

DBB 110


7 6 5 4 3 2 1 0DBB 0 32-bit switching cycle counter, most-

significant word 12 32-bit switching cycle counter, least-

significant word 3

:::::108 32-bit switching cycle counter, most-

significant word109110 32-bit switching cycle counter, least-

significant word111

7.5 Operating Times

The following diagram shows the assignment of the user data area for theOperating Times category. The allocation in the user data area is arecommendation.

DBB 0:::: Operating times 28 double words, operating: times::

DBW 110


37/48





7 6 5 4 3 2 1 0DBB 0 32-bit operating times, most-significant word

12 32-bit operating times, least-significant word3:::::108 32-bit operating times, most-significant word109110 32-bit operating times, least-significant word111


38/48

Appendix



8 Appendix

8.1 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 sendthe 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 ismade to the Executive Server or when a telegram is received from theExecutive 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 inthe "DB_TMT_Receive" receive mailbox (DB1002 or DB29 in the delivered

system) when it is received. The "TMT_Main" assigns the user data (starting atDBW 38) from the receive mailbox in the parameterized target area.

DBW 0 00 06 6 words, Plant iT Core protocol 2 0A 00

4 00 006 01 018 Source station10 Target station12 Length in words 6 words, Plant iT Service

protocol14 00 0216 00 0018 00 0020 00 0022 0124 Length in words 7 words, header information for

PDA block26 Source station28 00 Block number30 0032 Year Month34 Day Hour36 Minute Second38 All user data start here: User data:


39/48

Appendix




7 6 5 4 3 2 1 0DBB 0 00

1 062 0A3 004 005 006 017 0189

Source station

1011

Target station

1213

Length in words

14 0015 02

16 0017 0018 0019 0020 0021 0022 0023 012425

Length in words

2627

Source station

28 0029 Block number30 0031 0032 Year, tens33 Month, tens34 Day, tens35 Hour, tens36 Minute, tens37 Seconds, tens

Note: The first byte of a word (the byte with the smaller number) is the mostsignificant byte of the word; the second byte is the least significant byte of theword. The Executive Server expects first the most significant byte and then theleast significant byte as the sequence for the arrival of the telegram.

The telegram fields of the telegram for sending from the PLC to the ExecutiveServer are described below. This permits you to send your own telegramswithout requiring the use of the Transmit. When such a telegram is received,only the information from the source and target station is interchanged (affectsDBW8, DBW10 and DBW26).

The telegram fields of the telegram to the Collect handled at the end are a subsetof this description.


40/48

Appendix



DBB 0-7:These data words must have a fixed format as described in the table. All detailsare 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 thetelegram (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 arehexadecimal.


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 thevalue 0 or contain valid date/time details when sending. If all six bytes contain0, 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-9Bit 4-7 tens value of the year, value range 0-9

DBB 33: Month, value range 01-12 BCDBit 0-3 units value of the month, value range 0-9Bit 4-7 tens value of the month, value range 0-1

DBB 34: Day, value range 01-31 BCDBit 0-3 units value of the day, value range 0-9Bit 4-7 tens value of the day, value range 0-3

DBB 35: Hour, value range 00-23 BCDBit 0-3 units value of the hour, value range 0-9Bit 4-7 tens value of the hour, value range 0-2


41/48

Appendix



DBB 36: Minute, value range 00-59 BCDBit 0-3 units value of the minute, value range 0-9Bit 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-9Bit 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 theCollect. The "TMT_Main" in the standard software of the Transmit generatesthis 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 thistelegram from the telegram to the Executive Server.

DBW 0 Length in words 7 words, header information2 Source station for PDA block4 00 Block number6 008 Year Month10 Day Hour12 Minute Seconds14 All user data start here: User data:

The following table shows the assignment of the telegram header at bit level.

7 6 5 4 3 2 1 0DBB 0

1Length in words

23

Source station

4 005 Block number6 007 008 Year, tens9 Month, tens10 Day, tens11 Hour, tens12 Minute, tens13 Seconds, tens

Note: The first byte of a word (the byte with the smaller number) is the mostsignificant byte of the word; the second byte is the least significant byte of theword. The Executive Server expects first the most significant byte and then theleast significant byte as the sequence for the arrival of the telegram.

The descriptions of the telegram fields for the telegram to the Executive Serverfollow. The telegram fields of the telegram to the Collect handled at the end area subset of this description.


42/48

Appendix




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 thevalue 0 or contain valid date/time details. If all six bytes contain 0, the ExecutiveServer 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 BCDBit 0-3 units value of the year, value range 0-9Bit 4-7 tens value of the year, value range 0-9

DBB 9: Month, value range 01-12 BCDBit 0-3 units value of the month, value range 0-9Bit 4-7 tens value of the month, value range 0-1

DBB 10: Day, value range 01-31 BCDBit 0-3 units value of the day, value range 0-9Bit 4-7 tens value of the day, value range 0-3

DBB 11: Hour, value range 00-23 BCDBit 0-3 units value of the hour, value range 0-9Bit 4-7 tens value of the hour, value range 0-2

DBB 12: Minute, value range 00-59 BCDBit 0-3 units value of the minute, value range 0-9Bit 4-7 tens value of the minute, value range 0-5

DBB 13: Seconds, value range 00-59 BCDBit 0-3 units value of the seconds, value range 0-9Bit 4-7 tens value of the seconds, value range 0-5


43/48

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 systemclock 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 thesupplied system). The "TMT_Main" represents with the transferred clock (localtime or GMT) the system clock of the PLC.

DBW 0 00 06 6 words Plant iT2 0A 00 Core protocol4 00 006 01 018 Source station10 Destination station12 000E 6 words Plant iT14 00 02 Service protocol16 00 0018 00 0020 00 0022 0024 Year Month BCD clock (local time)26 Day Hour28 Minute Seconds30 1/100 second32 Year Month BCD clock (GMT)34 Day Month36 Minute Seconds38 1/100 second

DBW 24-38:Bytes 24-31 contain the timestamp for local time, bytes 32-39 contain thetimestamp for GMT. The values are packed-BCD (Siemens standard format). 2digits to base 10 are transferred per byte.

The following assignments apply to the timestamp in the two ranges:

Year, value range 00 to 99 BCDBit 0-3 units digit for the year, value range 0-9Bit 4-7 tens digit for the year, value range 0-9

Month, value range 01-12 BCDBit 0-3 units digit of the month, value range 0-9Bit 4-7 tens digit of the month, value range 0-1

Day, value range 01-31 BCDBit 0-3 units digit of the day, value range 0-9Bit 4-7 tens digit of the day, value range 0-3

Hour, value range 00-23 BCDBit 0-3 units digit of the hour, value range 0-9Bit 4-7 tens digit of the hour, value range 0-2

Minute, value range 00-59 BCDBit 0-3 units digit of the minute, value range 0-9Bit 4-7 tens digit of the minute, value range 0-5

Seconds, value range 00-59 BCDBit 0-3 units digit of the seconds, value range 0-9Bit 4-7 tens digit of the seconds, value range 0-5


44/48

Appendix



8.2 Example: Create a Counter in the DINT Format withOverflow Processing

The listing of a small sample program that follows shows how a double dataitem can be realized as a 32-bit counter with overflow processing. The programcan run on all CPUs of the S7-300 or S7-400. It is printed as ASCII sourcecode. The symbolic operands have the following meanings:

CMD Command flag; a change from 0 to 1 causes an increment to thecounter

EDGE Edge flagCTR Double word 32-bit counter

If the counter is contained in a data module, then the data module must beopened before this sample program is invoked.

FUNCTI ON FC99: VOI D

TI TLE = Doubl e wor d count er wi t h over f l ow pr ocessi ng

AUTHOR: MAFAMI LY: I DS_TOOLNAME: ZAEHL32VERSI ON: 01. 00

VAR_I NPUTCMD : BOOL; / / Change f r om 0 t o 1 - > i ncr ement

/ / count er commandEND_VAR

VAR_I N_OUTEDGE : BOOL; / / Edge f or count ed y/ nCTR : DI NT; / / 32- bi t count er

END_VARBEGI NNETWORK

TI TLE = Count er i n doubl e- wor d f or mat wi t h over f l ow pr ocess i ng

UN CMD; / / Counter command not pr esent ?R EDGE; / / Then cl ear " count ed" edgeBEB; / / and endU EDGE; / / Command pr esent and al r eady " count ed"?BEB; / / t hen endS EDGE; / / We count , set edge

L DW#16#7FFF_ FFFF;L CTR; / / Doubl e wor d count er==I ; / / j ust bef or e over f l owSPB REST; / / t hen wr apL 1;+D; / / Ot her wi se i ncrease by 1

T CTR;BEA;

REST: L 0; T CTR; / / Set doubl e wor d = 0BE;

END_FUNCTI ON


45/48

Appendix



8.3 Error Recogn ized from Acquis iT Transmit

The software for the Transmit in the S7 was created with the Simatic Managerand there with the source text editor. For the subsequent compiler run, thedocumentation preheaders in datablocks are not currently displayed.

However, because all important error acknowledgements of the Transmit in theS7 are still stored in the DB preheaders, the following section shows an extractof these modules from the source code listing. This listing is useful for thecommissioning when you want to work exclusively with the compiled S7 datamodules.

Values that the configuring engineer must set are identified with the "P:" code in thecomment.

Values that you must configure in order to send a datablock from the PLC to theCollect 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 ExecutiveServer in your own PLC are identified with an "(R)" in the comment.

/ / Not e: Gl obal err or s, such as " DB_DRV_TMT_Par amet er " does not/ / exi st , et c. ar e ret ur ned usi ng the symbol i c oper and PAFE of/ / t he FC " TMT_Mai n" ./ // / =====================================================/ / ERROR NUMBERS I N THE GENERAL PART OF THE PARAMETER DB:/ / =====================================================/ // / Er r or s t hat ar e det ect ed whi l e recei vi ng PDA bl ocks are st or ed/ / i n DBW 40. The recei vi ng of PDA bl ocks must be expl i ci t l y/ / enabl ed i n DBX 12. 4./ // / 30 The st at i on number f or t he r ecei ver i n t he t el egr am does

not agree wi t h t he own st at i on number i n t he DBW8/ / Par amet er DB./ / 31 No par amet er set i n t he Par amet er DB exi st s f or t he/ / r ecei ved PDA bl ock ( i dent i f i ed usi ng t he PDA bl ock/ / number f r om t he t el egr am)/ / 32 The t arget DB f or t he r ecei ved PDA bl ock does not exi st/ / i n t he PLC/ / 33 The r ecei ved PDA bl ock cont ai ns no appl i cat i on dat a/ / 34 The si ze of the appl i cat i on data of t he r ecei ved PDA/ / bl ock exceeds t he par amet er i zedmaxi mum l engt h i n t he/ / t ar get area/ / 35 The t arget DB i s t oo short f or t he r ecei ved PDA bl ock/ / 36 The r ecei ved t el egr am i s not f r om ser vi ce 10/ / 37 The r ecei ved t el egr am does not have t el egr am t ype 2/ // / I n addi t i on t o t he er r or s t hat ar e det ected dur i ng t he/ / eval uat i on of t he t el egr ams, t he er r or s suppl i ed di r ectl y f r om/ / t he communi kat i on modul e ar e al so st or ed her e. These err or/ / number s l i e i n t he r ange 8000h- 8FFF ( hexadeci mal ) and ar e/ / l i st ed at t he end of t he er r or number s f or t he par amet er set ./ // // / ==================================/ / ERROR NUMBERS IN THE PARAMETER SET: / / ==================================/ // / The r el . byt e 18+19 al ways cont ai ns an er r or number when an/ / er r or i s det ected. Thi s hel ps you t o recogni ze and r ecti f y/ / i ncor r ect par amet er i zat i ons. The er r or number al ways appl i es/ / t o t he r ecor d or t he DB t hat cont ai ns t he t el egr am t o be sent ./ /

/ // / 0 No er r or occur r ed


46/48

Appendix



/ // / The range 61 to 79 cont ai ns par amet er i zat i on er r or s f r om t he/ / user ' s par amet er set s:/ /=================================================================/ / 61 The DB par amet er i zed i n t he dat a r ecor d does not exi st

/ / ( byt e 10+11)/ / 63 The par amet er i zed t el egr am l engt h i s t oo l ar ge f or t he/ / CP ( byt e 14+15)/ / 64 The par amet er i zed bl ock number i s < 1 ( byt e 26+27)/ / 66 The DB par ameter i zed i n t he data r ecor d i s t oo short/ / ( byte 12- 15)/ / 67 The parameter i zed t el egr am l engt h i s smal l er t han 1 word/ / ( byte 14- 15)/ / 68 The set t i me and t he edge f l ag have been par amet er i zed/ / wi t h 0 i n t he data r ecord ( e. g. byt es 0- 5 have been/ / pr eassi gned wi t h 0) . The pr ogr am does not f ur t her/ / pr ocess t hi s r ecor d, but t he subsequent dat a r ecor d wi l l/ / be pr ocessed as pr evi ous./ / 69 Bi t number f or t he r el ease f l ag i s > 7/ / 70 Byte number f or t he r el ease f l ag i s t oo l ar ge f or t hi s/ / CPU. Val i d r anges ar e/ / CPU312: r ange [ 1. . 127]/ / CPU313 - 316: r ange [ 1. . 255]/ / CPU412/ 413: r ange [ 1. . 511]/ / CPU414: r ange [ 1. . 1023]/ / CPU416: r ange [ 1. . 2047]/ / 71 The DB par ameter i zed i n t he data r ecor d i s wr i t e/ / pr ot ected/ / 72 The DB par amet er i zed i n t he dat a r ecor d has t he number 0/ / or a number t hat i s t oo l ar ge/ / f or t hi s CPU. Val i d DB numbers are/ / CPU312: r ange [ 1. . 63]/ / CPU313 - 316: r ange [ 1. . 127]/ / CPU412/ 413: r ange [ 1. . 511]/ / CPU414: r ange [ 1. . 1023]/ / CPU416: r ange [ 1. . 4095]

/ / 128 I l l egal r esponse i n t he st at us of t he HTB Send/ / I n addi t i on, t he f ol l owi ng er r or number s of t he communi cat i on/ / modul e are al so st ored here:/ // / The r ange 8000h- 8FFFh cont ai ns t he er r or number s of t he CP/ / ( i n hexadeci mal ) :/ /=================================================================/ / 8183h The conf i gur i ng i s mi ssi ng or t he I SO t r anspor t ser vi ce/ / i n t he Et hernet - CP has not yet been st art ed/ / 8184h System er r or/ / 8185h LEN par amet er l ar ger t han t he sour ce ar ea/ / 8186h I D par amet er i nval i d. Val i d r ange f or Et her net [ 1. . 64] ,/ / f or Pr of i bus [ 1. . 32]/ / 8301h SAP not act i vat ed at t he t ar get st at i on/ / 8302h No r ecei ve r esour ces f or t he t ar get st at i on, r ecei ve/ / st at i on cannot pr ocess t he r ecei ved dat a/ / suf f i ci ent l y f ast or no r ecei ve r esour ces pr ovi ded/ / 8303h The SDA ser vi ce ( Send Dat a wi t h Acknowl edge) i s not/ / suppor t ed by t he t ar get st at i on on t hi s SAP/ / 8304h The I SO t r anspor t connect i on has not been est abl i shed/ / 8311h Tar get st ati on cannot be r eached usi ng t he speci f i ed/ / Et her net addr ess/ / 8312h Et hernet err or i n t he CP/ / 8F22h Sour ce ar ea i nval i d, e. g. ar ea not pr esent i n t he DB,/ / paramet er LEN < 0/ / 8F24h Range ar ea whi l e r eadi ng a par amet er/ / 8F28h Al i gnment er r or whi

ait pr interface-plc-transmit si en

Documents