6GK1543-0AA01 - Siemens - Datasheet.Live

Volume 1 of 2

CP 5430 TF with COM 5430 TF, CP 5431 FMS with COM 5431 FMS

1Introduction

C79000-B8976-C060/02 11 Data Transmission with Dist ri buted

I/Os

2System Overview 12 Service- und Diagnost ic Functions

on SINEC L2 Bus using

FMA Services

3Fundamentals of the Modul 13 Clock Services

4Technical Descri ption/Installat ion 14 Documentation and Testing

5Selecti ng the Type of

Communication 15 Utilities

6Basics of Conf iguration wi th NCM 16 Working with the Application

Examples

7Data T ransmission Using S5-S5

Links 17 Appendix

8Data T ransmission by Direc t

Access to Layer 2-Services AAbbreviations

9Data T ransmission wi th Global

I/Os BIndex

10 Data Transmission with Cyclic

I/Os CFurther Reading

SINEC is a trademark of Siemens

Siemens Aktiengesellschaft

SINEC

6GK1970-5AB01-0AA1 C79000-G8976-C048 Release 02

Siemens Aktiengesellschaft Elektronikwerk Karlsruhe

Printed in the Federal Republic of Ger m any

Wir haben den Inhalt der Druckschrift auf Überein-

stimmung mit der beschriebenen Hard- und Soft-

wa re geprüft. De nnoch kön nen Abw eichungen nicht

ausgeschlossen werden, so daß wir für die vollstän-

dige Übereinstimmung keine Gewähr übernehmen.

Die Angaben in der Druckschrift werden jedoch re-

gel mäßig ü berprü ft. Notwend ige Korrektu ren sind in

den nachf olg en de n A u flagen ent h al ten. F ü r V e r be s-

serungsvorschläge sind wir dankbar.

Technische Änderungen vorbehalten.

Weitergabe sowie Vervielfältigung dieser Unterlage,

Ve rw er tu ng un d M itt ei lun g ihr e s I nh alts nicht ge sta t -

tet, soweit nicht ausdrücklich zugestanden. Zuwider-

handlungen verpflichten zu Schadenersatz. Alle

Rechte vorbehalten, insbesondere für den Fall der

Patenterteilung oder GM-Eintragung.

Copyri ght © Siem ens A G 199 5

We have checked the contents of this manual for

agreement with the hardware described. Since de-

v iations cannot be precluded entirely, we cannot gua-

rantee full agreeme nt. Howe ver, the data in thi s ma-

nual are reviewed regularly and any necessary cor-

rections included in subsequent editions. Suggesti-

ons for improvement are welcome.

Technical data subject to change.

The reproduction, transmission or use of this docu-

ment or its contents is not permitted without express

written authority. Offenders will be liable for dama-

ges. All rights, including rights created by patent

grant or registration of a utility or design, are reser-

ved.

Cop yright © Si em en s A G 1995

Nous avons vérifié la conformité du contenu du

présent manuel avec le matériel et le logiciel qui y

sont décrits. Or, des divergences n’étant pas exclu-

es, nou s n e po uvons pas no u s po rt er ga r an t s po ur la

conformité intégrale. Si l’usage du manuel devait

révéler des erreurs, nous en tiendrons compte et ap-

po rter o ns le s cor rect io ns né ce ssair es dè s la pr o ch ai-

ne édition. Veuillez nous faire part de vos suggesti-

ons.

Nous nous réservons le droit de modifier les ca-

ractéristiques techniqu es.

Toute communication ou reproduction de ce support

d’informations, toute exploitation ou communication

de son contenu sont interdites, sauf autorisation ex-

presse. T out manquement à cette règle est illicite et

expose son auteur au versement de dommages et

intérêts. Tous nos droits sont réservés, notamment

pour le cas de la délivrance d’un brevet ou celui de

l’enregistrement d’un modèle d’utilité.

Cop yright © Si em en s A G 1995

SINEC

CP 5430 TF/CP 5431 FMS with COM 5430 TF/COM 5431 FMS

Description C79000-B8976-C060/02

Note

We wo uld p oin t out tha t the c onten ts o f th is prod uc t docu menta tio n shal l not bec ome a pa rt o f or m odify a ny

prior or exist ing agreement , c ommit ment or le gal relationship. The Purchase Agree m ent c ontains the compl e-

te and exclusive obligations of Siemens. Any statements contained in this documentation do not create new

warranties or restrict the existing warranty.We would further point out that, for reasons of clarity, these

operating instructions cannot deal with every possible problem ari s in g from the use of this device. Should you

require further infor mat ion or if any special problem s arise which are no t suffici ent ly dealt with in t he op erating

instructions, please contact your local Siemens repre sentative.

General This device is electrically operated. In operation, certain parts of this device carry a

dangerously high voltage.

Failure to heed war nings may re sult in seriou s ph ysical injury and/or materi al d amage.

Only appropriately qualified personnel may operate this equipment or work in its vicinity.

Personnel must be thoroughly familiar with all warnings and maintenance measures in

ac cordan ce with these operating instructions.

Correct and safe operation of this equipment requires proper transport, storage and

assembly as well as careful operator control and maintenance.

Personnel qualification requirements

Qual if ie d p er s on ne l as r efe rr ed to in t h e o pe r atin g i ns t ruc tions o r in th e w arning not es are def i ne d as pe r so ns

who are familiar with the installation, assembly, startup and operation of this product and who posses the

relevant qualifications f or their work, e.g. :

– Training in or authorization for connecting up, grounding or labelling circuits and devices or systems in

accordance with current standards in saftey technology;

– Trai ning in or au thor izatio n for th e mai ntena nce an d u se of su itable safte y equ ipme nt in acco rda nce w ith

current standards in safety technology;

– First Aid qualification.

WARNING !

1 Introduction 1 - 1

2 System Overview 2 - 1

2.1 SINEC Overview 2 - 3

2.2 The PROFIBUS-Compatible Network

SINEC L2/L2FO 2 - 5

2.2.1 Standards 2 - 7

2.2.2 Network Access Technique 2 - 10

2.2.3 Transmission Techniques 2 - 14

2.2.3.1 Transmission According to RS-485 2 - 14

2.2.3.2 Transmission with Fiber Optic Cables (FO) 2 - 15

2.3 Network Topology 2 - 18

2.3.1 Topology of an Electrical SINEC L2 Network for

the RS-485 Technique 2 - 18

2.3.2 Topology of an Optical SINEC L2FO Network 2 - 20

2.3.3 Topology of a Combined Electrical / Optical

SINEC L2/L2 FO Network 2 - 21

2.4 Configuring the Network 2 - 23

2.4.1 Configuring a SINEC L2 Network for RS-485 2 - 23

2.4.2 Configuring a SINEC L2FO Network 2 - 25

3 Fundamentals of the Model 3 - 1

3.1 ISO/OSI Reference Model for Communication 3 - 2

3.2 Architecture <-> OSI Env ironment 3 - 3

3.2.1 Communications Model 3 - 6

3.2.1.1 Relationship between Applic ation Processes 3 - 6

3.2.1.2 Logical Data Exchange 3 - 7

3.2.2 Communication Relati ons 3 - 7

3.2.2.1 Addressing Model for Expli cit Communication

(for S5-S5, free layer 2 and FMA) 3 - 8

3.2.2.2 Addressing Model for Implicit Communication

(GP, DP ZP) 3 - 9

B8976060/02 Contents

I Volume 1

3.3 Applicat ion Interfaces of Layer 2 Communi cation 3 - 11

3.3.1 Explicit Communi cation 3 - 11

3.3.1.1 S5-S5 Communication 3 - 11

3.3.1.2 Free Layer 2 Communication with FDL Services 3 - 12

3.3.1.3 Fieldbus Management with FMA Services 3 - 14

3.3.2 Implicit Communication 3 - 15

3.3.2.1 Global I/Os (GP) 3 - 16

3.3.2.2 Cyclic I/ Os (ZP), only with CP 5430 TF 3 - 17

3.3.2.3 Distri buted I/Os (DP) 3 - 18

4 Technical Description and Installation of the

CP 5430 TF/CP 5431 FMS 4 - 1

4.1 Technical Descri ption 4 - 1

4.1.1 Communications Processor CP 5430 TF/CP 5431 FMS 4 - 1

4.1.1.1 Mode Indicators (RUN and STOP LEDs) 4 - 3

4.1.1.2 Fault LED 4 - 6

4.1.2 Data Ex change between the CPU and

CP 5430 TF/CP 5431 FMS 4 - 7

4.1.2.1 Hardware Monit oring ( Watchdog) 4 - 11

4.1.3 Technical Data of the CP 5430 TF/CP 5431 FMS 4 - 12

4.1.3.1 Interfaces 4 - 12

4.1.3.2 Operating and Environmental Condit ions 4 - 12

4.1.3.3 Mechanical and Electrical Data 4 - 13

4.1.3.4 Logical Characteris ti cs 4 - 13

4.1.3.5 Performance Data CP 5430 TF 4 - 14

4.1.3.6 Performance data of the CP 5431 FMS 4 - 16

4.1.3.7 Interface Assignments 4 - 18

4.2 Memory Subm odules 4 - 20

4.2.1 Memory Submodule Types for the

CP 5430 TF/CP 5431 FMS 4 - 20

4.3 Installat ion Guidel ines 4 - 21

4.3.1 Basic Conf igurati on 4 - 21

4.3.1.1 CP 5430 TF/CP 5431 FMS Slots in the various PLCs 4 - 21

4.4 Ways of Connecting PGs on the SINEC L2 Bus 4 - 26

4.4.1 Structure and Functions of the Bus Terminal 4 - 29

Contents B8976060/02

Vol ume 1 I I

4.4.2 Example of Transm ission wi th RS 485 Bus Terminals 4 - 29

5 Selecting the Type of Communication 5 - 1

5.1 Data Transmission with HDBs (S5-S5) 5 - 3

5.2 Data Transmission with HDBs (Free Layer 2 Access) 5 - 4

5.3 Data T ransmission wi th Global I/O s (GP) 5 - 5

5.4 Data T ransmission wi th Cy clic I /Os (ZP)

(CP 5430 TF) 5 - 7

5.5 Data T ransmission wi th Dis tributed I/Os (DP ) 5 - 8

5.6 Communication with TF (CP 5430 TF) 5 - 9

5.7 Communication with FMS (CP 5431 FMS) 5 - 11

6 Basics of Configuration with NCM 6 - 1

6.1 SINEC NCM 6 - 2

6.1.1 The Keyboard 6 - 3

6.1.2 Menu Structure and Operation 6 - 4

6.1.3 COM Screen Layout and Operation 6 - 6

6.1.4 Special Windows 6 - 9

6.2 Installat ion and Start 6 - 10

6.3 General Guidelines for Working with your Software 6 - 12

6.4 Overview of Basic Configur ation 6 - 14

6.5 Screens for Basic Configuration 6 - 17

6.5.1 Editing 6 - 17

6.5.2 CP Init 6 - 20

6.5.3 Network Parameters 6 - 24

6.5.3.1 Global Network Parameters 6 - 25

B8976060/02 Contents

III Volume 1

6.5.3.2 Local Network Parameters 6 - 28

6.5.4 Network Functions 6 - 33

6.5.4.1 Network Overview 6 - 34

6.5.4.2 Network Matching 6 - 36

6.5.4.3 GP Consistency 6 - 38

6.5.4.4 Default S5-S5 Links 6 - 40

6.5.4.5 Network Documentation 6 - 42

6.5.4.6 Archivi ng 6 - 44

6.6 Transfer Functions 6 - 46

6.6.1 Start CP / Stop CP / CP Status 6 - 47

6.6.1.1 Start CP 6 - 47

6.6.1.2 Stop CP 6 - 48

6.6.1.3 CP Status 6 - 48

6.6.2 Delete CP 6 - 49

6.6.3 Delete FD 6 - 50

6.6.4 CP Database Transfer 6 - 51

6.6.4.1 FD -> CP 6 - 51

6.6.4.2 CP -> FD 6 - 53

6.6.4.3 FD -> EPROM 6 - 55

6.6.4.4 EPROM -> FD 6 - 56

6.6.4.5 FD -> FD 6 - 57

6.7 Link Configuration 6 - 59

6.8 Basic Conf igurati on 6 - 60

6.8.1 Block Overview CP 5430 TF 6 - 62

6.8.2 Block Overview CP 5431 FMS 6 - 63

7 Data Transmission Usi ng Configured S 5-S5 L inks 7 - 1

7.1 Basics of Data Transmission with HDBs

on Configured S5-S5 Links 7 - 2

7.1.1 Sequence of the Data Transmission 7 - 4

7.1.2 Checking with ANZW and PAFE 7 - 6

7.2 Configuring 7 - 10

7.2.1 Configuring S5-S5 Link s 7 - 11

Contents B8976060/02

Vol ume 1 I V

7.3 Example of a Program for an S5-S5 Link 7 - 15

7.3.1 Outline of the Task 7 - 17

7.3.1.1 Program for PLC 1 (S5-155 U) 7 - 19

7.3.1.2 Program for PLC 2 (S5-115 U) 7 - 20

7.3.2 Transferring the Configur ation Data for the

CP 5430 TF/CP 5431 FMS and the STEP 5

User Pr ogram 7 - 20

7.3.3 Monitoring the Data Transmission 7 - 22

8 Data Transmission b y Direct Access t o

Layer 2 Services 8 - 1

8.1 Basics of Data Transmission using Layer 2 Services 8 - 2

8.1.1 FDL Services implemented in a

CP 5430 TF/CP 5431 FMS for Data Transmission 8 - 3

8.1.2 How Data Transmission by Direct Access to

Layer 2 Services Functions 8 - 9

8.1.3 Handling the Individual Data Transmission Services

from the Point of View of the Control Program 8 - 13

8.1.4 Checking the Data Transmission in the

Control Program using ANZW and PAFE 8 - 13

8.1.5 Sequence of the Data Transmission 8 - 18

8.2 Transmitting Multicast Messages by Direct

Access to Layer 2 Services 8 - 28

8.3 Configuring 8 - 31

8.3.1 Configuring Free Layer 2 Links 8 - 32

8.4 Example of a Layer 2 Link 8 - 35

8.4.1 Program Description 8 - 36

8.4.1.1 Program for PLC 1 8 - 37

8.4.1.2 Program for PLC 2 8 - 37

8.4.2 Transferring the Configur ation Data for the

CP 5430 TF/CP 5431 FMS and the

STEP 5 User P rogram 8 - 38

B8976060/02 Contents

V Volume 1

9 Data Transmission with Global I/Os 9 - 1

9.1 Basics of Data Transmission with Global I/Os 9 - 3

9.1.1 Checking the Data Transmission with

ANZW and the GP Station List 9 - 18

9.2 Configuring 9 - 23

9.2.1 I/O Areas CP 5430 TF 9 - 24

9.2.2 I/O Areas CP 5431 FMS 9 - 28

9.2.3 Editor for Global I/Os 9 - 32

9.3 Example of Data Transfer with Communication

using Global I/Os 9 - 35

9.3.1 Program Description 9 - 36

9.3.1.1 Start-up Response 9 - 42

9.3.1.2 Cyclic Mode 9 - 46

9.3.2 Transferring the Configur ation Data for the

CP 5430 TF/CP 5431 FMS and the

STEP 5 User P rogram 9 - 47

10 Data Transmission with Cyclic I/Os (CP 5430 TF) 10 - 1

10.1 Basics of Data Transmission with Cyclic I/Os (ZP) 10 - 3

10.1.1 Checking the Data Transmission with

ANZW and the ZP Station List 10 - 16

10.2 Configuring 10 - 20

10.2.1 I/O Areas 10 - 21

10.2.2 ZP Editor 10 - 24

10.3 Example of using t he Cyclic I/Os 10 - 27

10.3.1 Program Description 10 - 28

10.3.1.1 Program for PLC 1 10 - 29

10.3.1.2 Program for PLC 2 (S5-95U) 10 - 29

10.3.2 Transferring the Configur ation Data for the

CP 5430 TF and the STEP 5 User Program 10 - 30

Contents B8976060/02

Vol ume 1 VI

11 Data Transmission with Distributed I/Os 11 - 1

11.1 Basics of SINEC L2-DP 11 - 4

11.1.1 The SINEC L2-DP Interface for the

CP 5430 TF/CP 5431FMS 11 - 6

11.2 CP 5430 TF/CP 5431 FMS L2-DP Functions 11 - 7

11.3 Communicat ion Between the DP Master and t he

DP Slave Station 11 - 9

11.4 Basics of Data Transmission Using the

DP Service of the CP 11 - 10

11.5 Updating the Input and O utput Areas

with the DP Service 11 - 11

11.5.1 Consistency of the Input and Output Bytes

with the DP Service of the CP 11 - 11

11.5.2 How the FREE Mode Functions 11 - 12

11.5.3 How the CYCLE-SYNCHRONIZED Mode Functions 11 - 15

11.6 Configuring 11 - 22

11.6.1 I/O Areas 11 - 23

11.6.2 Assigning Parameters to DP Slaves 11 - 26

11.6.3 DP Editor 11 - 31

11.6.4 Example of using the DP service 11 - 37

11.7 L2-DP Diagnostic s wi th the User Pr ogram 11 - 40

11.7.1 Overview 11 - 40

11.7.2 Examples of Practical Applicati ons 11 - 45

11.7.2.1 Reading out the DP station list 11 - 45

11.7.3 Reading Out the DP Diagnostic List 11 - 48

11.7.4 Request Single DP Stati on Diagnostic Data 11 - 51

11.7.5 Example of a Program for Requesting

Single DP Stati on Diagnostics 11 - 52

11.8 Sending Control Commands to the DP Sl ave 11 - 66

11.8.1 Function of the Control Commands -

Sync and Unsync 11 - 67

11.8.2 Function of the Control Commands -

Freeze and Unfreeze 11 - 68

B8976060/02 Contents

VII Volume 1

11.8.3 Cyclic and Acyclic Transmission of

Global_Control Commands 11 - 69

11.8.4 Special Job "STOP DP polling list processing" 11 - 74

12 Service and Diagno sti c Functions on the

SINEC L2 Bus using FMA Services 12 - 1

12.1 Use and Types of FMA Service 12 - 2

12.2 Fundamental s of using the FMA Serv ices 12 - 5

12.3 FDL_READ_VALUE 12 - 13

12.3.1 FDL_READ_VALUE_Request 12 - 13

12.3.2 FDL_READ_VALUE_Confir mation 12 - 14

12.4 LSAP_STATUS 12 - 17

12.4.1 LSAP_STATUS_Request 12 - 18

12.4.2 LSAP_STATUS Confirmati on 12 - 19

12.5 FDL_LIFE_LIST_CREATE_LOCAL 12 - 22

12.5.1 FDL_LIFE_LIST_CREATE_LOCAL Request 12 - 22

12.5.2 FDL_LIFE_LIST_CREATE_LOCAL Confirmation 12 - 23

12.6 FDL_IDENT 12 - 25

12.6.1 FDL_IDENT Request 12 - 25

12.6.2 FDL_IDENT Confirmation 12 - 26

12.7 FDL_READ_STATISTIC_CTR 12 - 28

12.7.1 FDL_READ_STATISTIC_CTR Request 12 - 28

12.7.2 FDL_READ_STATISTIC_CTR Confirmati on 12 - 29

12.8 FDL_READ_LAS_STATISTIC_CTR 12 - 32

12.8.1 FDL_READ_LAS_STATISTIC_CTR Reques t 12 - 32

12.8.2 FDL_READ_LAS_STSTISTIC_CTR Conf irmation 12 - 33

12.9 Examples 12 - 35

12.9.1 Program Example for the FDL_READ_VALUE Service 12 - 35

12.9.2 Program Example for the LSAP_STATUS Service 12 - 40

Contents B8976060/02

Vol ume 1 V II I

12.9.3 Program Examples for the

FDL_LIFE_LIST_CREATE_REMOTE Service 12 - 42

12.9.4 Program Example for the

FDL_LIFE_LIST_CREATE_LOCAL Service 12 - 43

12.9.5 Program Example for the FDL_IDENT Service 12 - 45

12.9.6 Program Example for

FDL_READ_STATISTIC_CTR Service 12 - 48

12.9.7 Program Example for

FDL_READ_LAS_STATISTIC_CTR S ervice 12 - 51

13 Clock Services 13 - 1

13.1 Network Topology, Clock Master/Slave Functions 13 - 3

13.2 How the Clock Functions 13 - 6

13.3 Several CP 5430 TF/ CP 5431 FMS Modules

on a SINEC L2 Bus 13 - 8

13.3.1 Setting and Reading the Time in the

Programmable Cont roller 13 - 9

13.4 Setting and Reading the Time with

COM 5430 TF/CP 5431 FMS 13 - 14

13.5 Restrictions / Tips 13 - 17

13.6 Accuracy 13 - 18

14 Documentation and Testing 14 - 1

14.1 Document ation F unctions 14 - 1

14.2 Test 14 - 3

14.2.1 S5-S5/ Free L2 - Test Functions 14 - 4

14.2.1.1 Total Status 14 - 5

14.2.1.2 Single Status 14 - 10

14.2.2 GP Test Functions 14 - 13

14.2.2.1 Total Status of the GP Jobs 14 - 13

B8976060/02 Contents

IX Volume 1

14.2.2.2 Display of the GP Output Values 14 - 15

14.2.2.3 Display of the GP Input Values 14 - 18

14.2.3 ZP Test Functions (CP 5430 TF) 14 - 21

14.2.3.1 Total Status of the ZP Jobs 14 - 21

14.2.3.2 Display of the ZP Output Values 14 - 24

14.2.3.3 Display of the ZP Input Values 14 - 27

14.2.4 DP Test Functions 14 - 29

14.2.4.1 DP Total Status 14 - 29

14.2.4.2 DP Single Status 14 - 32

14.2.5 FMA Test Functions 14 - 35

14.2.5.1 Local Life List 14 - 35

14.2.5.2 Station-or iented Statistics 14 - 36

14.2.5.3 Bus-oriented Statistics 14 - 37

15 Utiliti es 15 - 1

15.1 PG Functi ons on the SINEC L2 Bus 15 - 2

15.1.1 Bus Selection - Creating Paths in Path Files 15 - 5

15.1.2 Editing a Path 15 - 6

15.1.3 Activat ing the Edited Path 15 - 8

15.2 Change Submodule Siz e 15 - 10

15.3 Convert CP 5430 Dat abase old - new (CP 5430 TF) 15 - 12

16 Working with the Application Examples 16 - 1

17 Appendix 17 - 1

17.1 Job Numbers for the CP 5430 TF 17 - 1

17.2 Job Numbers for the CP 5431 FMS 17 - 3

17.3 SAP - Job Number Assi gnment 17 - 5

17.4 Overview of the Error Messages 17 - 6

Contents B8976060/02

Vol ume 1 X

17.4.1 Messages in the status word for predefined

S5S5 links, free layer 2 and FMA 17 - 6

17.4.2 Global I/Os - Error Bits 17 - 10

17.4.3 Cyclic I/Os Error Messages 17 - 14

17.4.4 DP Error Displays 17 - 17

17.5 Overview of the FMA Services 17 - 21

17.6 Calculation of the Target Rotation Time (TTR) 17 - 24

17.6.1 Overview 17 - 24

17.7 Calculating the Switch-off and Reaction Times

of the Global I/Os 17 - 30

A Abbreviations A - 1

C Index B - 1

C Further Reading C - 1

B8976060/02 Contents

XI Volume 1

Contents B8976060/02

Vol ume 1 XI I

1 Introduction

The manual for the CP 5430 TF and CP 5431 FMS is divided into two

volumes. This volume, Volume 1 of the manual describes the PROFIBUS

(PROcess FIeld BUS) communication available with the two CPs.

Differences in communication and performance are pointed out in the

appropriate chapters. The communications processors are configured with

COM 5430 TF/COM 5431 FMS under SINEC-NCM.

PROFIBUS is a bus system for applications in automation engineering in

areas closely associated with the process and allows easy implementation

of bus interfaces. With the PROFIBUS, SIMATIC S5 programmable

controllers, programmers, AT-compatible PCs and other control systems

and, of course, PROFIBUS-compatible devices from various manufacturers

can be networked.

The CP 5430 TF is used to connect SIMATIC S5 programmable controllers

to the SINEC L2/L2FO local area network and complies with the

PROFIBUS standard (DIN 19245) Part 1 /1/. The range of performance

described in Volume 2 extends the functions of the CP by the services

described in the TF standard for SINEC TF. The CP 5430 TF also provides

the L2-DP (distributed I/Os) service.

The CP 5431 FMS communications processor is used to connect

programmable controllers of the SIMATIC S5 range to the local area

network SINEC L2/L2FO and complies with the PROFIBUS standard (DIN

19245) both in Part 1 and Part 2 /10/ as an active station on the bus

(PROFIBUS multivendor network). The CP 5431 FMS also provides the

L2-DP (distributed I/Os) service.

SINEC L2-DP is the Siemens implementation of DIN E19245 Part 3

PROFIBUS-DP /11/. The L2-DP protocol uses a subset of the functions

specified in DIN 19245 Part 1 for layers 1 and 2 and supplements these for

the special applicati ons in distributed I/Os.

The performance of the CP 5431 FMS described in Volume 2 extends the

functions of the CP by the services described in the FMS standard.

B8976060/02 Introduction

1 - 1 Volume 1

The network is configured with COM 5430 TF/COM 5431 FMS under

SINEC NCM (Network and Communicat ion Management ). The configuration

tool can be run on the PG 710, 730, 750 and 770 under the S5-DOS/ST

operating system.

The handling of the communications protocols for layers 1 and 2 described

in this volume is microprocessor-controlled. The host system is therefore

relieved of specific communications tasks.

To allow a wide range of applications, the PROFIBUS communications

system provides the user system with a variety of services for open

communication.

The information in this manual is intended for the followi ng users:

➣The planner and designer of a communications network

➣Programmers of c ommunications relations

➣Customers wishing to use SINEC L2/L2FO in the SIMATIC S5 system

S5 S5

CP 5430 TF

Field

device Field

device

Bus terminal with line terminator connected

Bus terminal

Active SINEC L2 / PROFIBUS stations

Passive SINEC L2 / PROFIBUS stations

SINEC L2/

L2FO

PROFIBUS

o. vendor

device

CP 5410 PC

CP 5412

CP 5431 FMS

CP 5430

Fig. 1. 1 Ex ampl e of P ROFIB US L 2 Co nfigu rati on

Introduction B8976060/02

Volume 1 1 - 2

General symbols:

✔ This character indicates an activity or operation for you to perform.

☞This symbol highlights special features and dangers.

mm The dimensions in diagrams and scale drawings are specified in

millimeters.

DTE

Active star coupler

Twisted pair

Bus terminal (terminating resistor connected)

Bus terminal (terminating resistor disconnected)

Data Terminal Equipment

Fiber optic cable

Optical bus terminal

SF repeater adapter

RS 485 repeater

Table 1.1 Symbol s fo r SINEC L2/L2F O

B8976060/02 Introduction

1 - 3 Volume 1

Requirements of the user

To understand the examples, you should have the following:

➣Knowledge of programming with STEP 5

➣Basic knowledge of the use of handling blocks (HDBs). The description

of the HDBs can be found in the manual for your programmable

control ler or in separate descript ions of the programmable controllers.

Train ing off er

Siemens provides SINEC users with a comprehensive range of training

opportunities.

For more det ailed inf ormation contact

Informations - and Traini ngs-Center

für Automatisierungstechnik

AUT 6 Kursbüro

Postfach 21 12 62

76181 Karlsruhe

Germany

or your l ocal S iemens of fice.

Order numbers for the products mentioned in this manual can be found in

the current catalogs.

Introduction B8976060/02

Volume 1 1 - 4

To help you find your way through this manual (Volume 1) the remainder of

this section outlines the chapters briefly.

Chapter 2

System Overview

This chapter supports you when structuring your network and provides an

overview of the standards, techniques, devices and structure of the

PROFIBUS-compatible network SINEC L2/L2FO. You will also find general

information about different topologies, functions and network planning and

design of the SINEC L2/L2FO bus system.

Chapter 3

Fundament als of the Model

This chapter provides an introduction to the communications model by

explaining terminology and inter-relationships and illustrates the interface to

the SIMATIC S5 user.

Chapter 4

Technical Description and Installation Guidelines for the CP 5430

TF/CP 5431 FMS

This chapter describes in detail the hardware of the CP 5430 TF/CP 5431

FMS (technical data, interfaces, operating statuses, memory modules) and

also deals with PG connections and the module slots in various PLCs.

Chapter 5

Selecting the Type of Communication

This chapter helps you to select the type of communication for your specific

task by briefly outlining the essential characteristics of different types of

communication. The detailed descriptions of the possible types of

communication can then be found in Chapters 7 to 11 in Volume 1 and for

the FMS or TF services in Volume 2. Each chapter contains a specific

description of the basics and of configuration.

B8976060/02 Introduction

1 - 5 Volume 1

Chapter 6

Basics of Configuration with NCM

This chapter contains an introduction to working with SINEC NCM and

COM 5430 TF/COM 5431 FMS. It is intended to familiarize you with the

basics of configuring, i.e. how to use general guidelines and the basic

configuration screens and their application.

Chapter 7

S5-S5 Communication

This chapter describes the communication with handling blocks on

pre-configured S5-S5 links between active SIMATIC S5 programmable

controllers.

Chapter 8

Free Layer 2 (FL2) Communication

This chapter describes the data exchange with handling blocks using the

layer 2 access of the CP.

The free layer 2 access allows communication with passive and/or

non-Siemens PROFIBUS stations which also have free layer 2 access.

Chapter 9

Globa l I/Os (GP) Communi cation

This chapter describes event-driven data transmission using the global I/Os

(GP) via the I/O area of the SIMATIC S5 programmable logic controller.

Chapter 10

Cyclic I/O s (only CP 5430 TF)

This chapter describes the cyclic data exchange to normally passive field

devices using the cyclic I/Os service (ZP) via the I/O area of the SIMATIC

S5 programmable controller.

Chapter 11

Distributed I/Os (DP) Communication

This chapter describes the cyclic communication with standard DP slave

stations via the I/O area of the SIMATIC S5 programmable controller.

Introduction B8976060/02

Volume 1 1 - 6

Chapter 12

FMA Services

This chapter describes the different types of communication including a

detailed description of the basics and the configuring procedure. At the end

of each section there is an example to illustrate the type of communication.

Chapter 13

Clock Services

This chapter describes the data formats for the time of day and explains

how the clock master and clock slave roles function.

Chapter 14

Documentation and Test

This chapter contains a description of the test and documentation functions

referred t o i n earli er chapters

Chapter 15

Utilities

The "bus selection" utility is described in this chapter. This tool is used to

create paths that can be activated using the menu command Bus Selection.

You can also use this tool to modify the memory module size and with the

CP 5430 TF, you can convert databases of the CP 5430 to new databases.

Chapter 16

Using the Application Examples

This chapter describes the general procedure f or the application examples.

Chapter 17

Appendix

Here, you will find important information you require regularly, for example

the significance of error messages, basic calculations for important bus

parameters, notes on the simultaneous use of different types of data

transmission etc.

B8976060/02 Introduction

1 - 7 Volume 1

Chapter A and B

Abbreviations and Index

The list of abbreviations will help you considerably when working with this

manual since you can check the meaning of unknown abbreviations qui ckly.

You can use the i ndex to find a term quickly.

Chapter C

Archive

Documentation All

Topology

Application Associations

FMS Links

Output all

Fig . 6.16 Network Documentation Screen

Basics of Configuration B8976060/02

Vol ume 1 6 - 42

The following documentation filters are availabl e:

All: complete documentation of the network

(starting with the network overview list).

Topology: output of the network overview list.

ZP: output of the ZP configuration (CP 5430 TF) incl. I/O

area.

CI: output of the CI configuration (CP 5431 FMS) incl. I/O

area.

GP: output of the GP configuration (CP 5430 TF/CP 5431

FMS) incl. I/O area.

DP: output of the DP configuration (CP 5430 TF/CP 5431

FMS) incl. I/O area.

Application

Associations: output of the SINEC application association

configuration of all CP 5430 TF stations.

FMS Links.: output of the FMS links of all CP 5431 FMS stations.

B8976060/02 Basics of Configuration

6 - 43 Volume 1

6.5.4.6 Archiving

With this function, you can archive a whole network on di sk. .

Input fi eld:

Network file: Format: Dr ive : Network f ile name

- Drive: Here, you specify the drive you want to work with. You

can display possible drives with F8.

- Network file

name: Name under which the network file will be archiv ed.

Dest drive: All S5 drives except for the currently selected drive of

the network file can be specified.

Netw. - Network Archiving SINEC NCM (EXIT)

Network file :

Dest. drive: A

Status:

SELECT

@@@@@NCM.NET:C

HELP

Fig . 6.17 Arc hiving Screen

Basics of Configuration B8976060/02

Vol ume 1 6 - 44

Output field:

Status: Displays the status of the currently active archiving

function.

Functi on keys:

OK Starts the archiving

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select entries from the list with the cursor keys and

enter them in the field with the return key.

B8976060/02 Basics of Configuration

6 - 45 Volume 1

6.6 Transfer Functions

Using the transfer functions, a parameter set, e.g. a submodule file of a CP

created locally c an be transferred. The commands start, stop and delete are

used. In addition to this, it is possible to transfer data from one file to

another and to transfer files to the PLC. When transferring from a memory

submodule to hard disk, the parameter Submodule type is automatically set

to "EPROM" in the SYSID block, regardless of the actual type of

submodule. When transferring from a diskette or hard disk to a memory

submodule, the Submodule type parameter is automatically matched to the

current type of memory submodule.

After selecti ng the Transfer f unction in t he menu bar, the menu items shown

in Fig. 6.18 appear in the pull-down menu.

screen

CP Database Transfer

->FD->CP

Transfer

Menu item

= Init Edit ...

SINEC NCM

Further

menu items

screen

CP Database Transfer

->FD->FD

screen

Transfer->Delete CP screen

Transfer->Delete FD

dialog box

Transfer->Start CP

dialog box

Transfer->Stop CP

dialog box

Transfer->CP status

Transfer->

screen

PLC Database Transfer

sub menu

Transfer->

CP Database Transfer

->CP->FD

screen

CP Database Transfer

->EPROM->FD

screen

CP Database Transfer

->FD->EPROM

screen

Fig . 6.18 NCM Menu Transfer Function

Basics of Configuration B8976060/02

Vol ume 1 6 - 46

In the ONLINE mode, the transfer is between the hard disk (= FD) and the

memory submodule of the CP. If the memory submodule is an EPROM,

only transfer from EPROM to diskette is possible ONLINE.

6.6.1 Start CP / Stop CP / CP Status

The CP recognizes the modes RUN and STOP. The RUN mode is the

normal operating status of the CP. In this mode, it is not possible to modify

the database. It is only possible to read from the CP. In contrast, in the

STOP mode, the CP can be written to. For this reason, before using the

functions "Transfer -> FD -> CP" or "Transfer -> Delete CP", the CP must

be switched to the STOP mode. The CP can be stopped directly with the

START/STOP switch or by a COM function.

The following functions are available:

➣Start CP

➣Stop CP

➣CP status.

The functions can be activated directly from the NCM menu and logically

belong to the "Transfer" menu item.

6.6.1.1 Start CP

Sel e ct Transfer -> Start CP to call the function. This function switches the

CP to the RUN mode. A dial og box which you can exit by pr essi ng a key or

clicking with the mouse informs you whether the function was successful or

not.

B8976060/02 Basics of Configuration

6 - 47 Volume 1

6.6.1.2 Stop CP

Sel e ct Transfer -> Stop CP, to call the function. This function changes the

CP to the STOP mode. A dialog box which you can exit by pressing a key

or clicking with the mouse informs you whether the function was successful

or not.

6.6.1.3 CP Status

Select Transfer -> CP Status, to call the function. This function allows you

to inquire about the CP status. The status or an error message is displayed

in a dialog box which you can exit by pressing a key or clicking with the

mouse.

Basics of Configuration B8976060/02

Vol ume 1 6 - 48

6.6.2 Delete CP

With the delete CP command, you can delete the content of a RAM

submodule. To prevent you deleting data accidentally, this command must

be confir med.

Select Transfer -> Delete CP to call the COM screen. The screen has the

following layout:

In the message line, the prompt: Delete CP? appears to which you respond

using the functi on keys.

Functi on keys:

YES CP will be deleted.

NO CP contents are retained.

Delete CP ?

YES NO

=Init Edit Network Transfer Test Utilities SINEC CP 54xx

Fig . 6.19 Transfer -> Delete CP Screen

B8976060/02 Basics of Configuration

6 - 49 Volume 1

6.6.3 Delete FD

With the Delete FD command you can delete the contents of a database

file. To prevent data being accidentally deleted, this command must be

confirmed.

Select Transfer -> Delete FD to call the COM screen. The screen has the

following layout:

The following prompt appears in the message line: drive: source file name:

Delete file?, to which you can respond with the function keys.

Functi on keys:

YES Source file will be deleted.

NO Source file is retained.

Delete file ?

YES NO

=Init Edit Network Transfer Test Utilities SINEC CP 54xx

Fig . 6.20 Transfer -> Delete FD Screen

Basics of Configuration B8976060/02

Vol ume 1 6 - 50

6.6.4 CP Dat abase Transfer

Select Transfer -> CP Database Transfer, to change to the submenu.

6.6.4.1 FD -> CP

Submodule files created OFFLINE are transferred to the CP. The PG must,

however, be connected ONLINE (via the PG interface or the bus) with the

CP at the time of the transfer. There must be a RAM submodule inserted in

the CP. As the submodule file, the database file specified in the Init -> Edit

screen is used. Select CP Database Transfer -> FD -> CP, to call the

COM screen. The screen has the following layout:

The COM asks whether single blocks or all blocks are to be transferred. If

the network belonging to the database is inconsistent, a warning is

displayed. If you acknowledge the message, the function is continued. You

can abort the function with ESC

Transfer - Database - FD ->CP

SINGLE

CP Type :

Source :

Dest. : CP

TOTAL

(EXIT)

HELP

SELECT

Fig . 6.21 Da tabase Tran sfer -> FD -> CP Screen

B8976060/02 Basics of Configuration

6 - 51 Volume 1

Functi on keys:

SINGLE The blocks are transferred singly to the CP. For the

meaning of the individual blocks refer to Fig. 6.27/6.28

in this chapter.

TOTAL The blocks are all transferred to the CP.

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select entries from the list with the cursor keys and

enter them in the field with the return key.

☞Make sure that the size of the RAM submodule matches the

submo dule size set wi th "E dit CP Ini t" (Fi g. 6.8).

Basics of Configuration B8976060/02

Vol ume 1 6 - 52

6.6.4.2 CP -> FD

The submodule files are transferred from the CP to FD. The PG must,

however, be ONLINE with the CP at the time of the transfer. The default

destination file is the dat abase file specified in the Init -> Edit screen. Select

CP Database Transfer -> CP -> FD, to call the COM screen. The screen

has the f ollowi ng layout:

If the fil e already exists, a message appears in the message line asking you

whether you want to delete the file on the destination station by overwriting

it.

Transfer - Database - Eprom->FD

SINGLE

Dest. file : :

TOTAL

CP type :

Source : (EXIT)

HELP

SELECT

Fig . 6.22 CP Da tabase Transfer -> CP -> FD Screen

B8976060/02 Basics of Configuration

6 - 53 Volume 1

Output fields:

Dest. file This is the file in which the database from the CP is

stored.

Functi on keys:

SINGLE The blocks are transferred singly to the CP. For the

meaning of the individual blocks refer to Fig. 6.28 in

this chapter.

TOTAL The blocks are all transferred to the destination file.

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select entries from the list with the cursor keys and

enter them in the field with the return key.

Basics of Configuration B8976060/02

Vol ume 1 6 - 54

6.6.4.3 FD -> EPROM

The data records on FD (diskette or hard disk) are written directly to the

EPROM (blown). Select CP Database Transfer -> FD -> EPROM to call

the COM screen. The screen has the following layout:

Input fields :

Programming

number: Here, you enter the programming number of the

EPROM type you are using. You can select this from

the NCM selection menu.

☞Make sure that the EPROM type matches the programming

number. If the assignment is wrong, the EPROM submodule

is destroyed.

You should also make sure that the size of the EPROM

matches the submodule size preset in "Edit CP I nit" (Fig. 6.8).

Transfer - Database -> Eprom

Programming number :

OK SELECT

CP type :

Source : (EXIT)

HELP

Fig . 6.23 CP Da tabase Transfer -> FD -> EPROM Sc reen

B8976060/02 Basics of Configuration

6 - 55 Volume 1

Functi on keys:

OK The data are transferred to the EPROM.

SELECT If you press this key, a selection list is displayed with

possible entries for fields. Select entries from the list

with t he cursor keys and enter them in the field with the

return key.

6.6.4.4 EPROM -> FD

The data recor ds on the EPROM are copied directly to the default database

file. Select CP Database Transfer -> EPROM -> FD to call the COM

screen. The screen has the following layout:

If the fil e already exists, a message appears in the message line asking you

whether you want to delete the file on the destination station by overwriting

it.

Transfer - Database - Eprom-> FD

Dest. file:

CP type :

Source :

SINGLE TOTAL

(EXIT)

HELP

Fig . 6.24 CP Da tabase Transfer -> EPROM -> FD Sc reen

Basics of Configuration B8976060/02

Vol ume 1 6 - 56

Output fields

Dest. file This is the file in which the database from the EPROM

is st ored.

Functi on keys:

OK All the data are read from the EPROM and stored in

the destination file.

6.6.4.5 FD -> FD

This function is used to duplicate the source in the destination file. Select

CP Database Transfer -> FD -> FD to call the COM screen. The screen

has the f ollowi ng layout:

If the fil e already exists, a message appears in the message line asking you

whether you want to delete the file on the destination station by overwriting

it.

Transfer - Database

SINGLE TOTAL

Dest. file : :

CP type :

Source : (EXIT)

HELP

SELECT

Fig . 6.25 Da tabase Tran sfer -> FD -> FD Screen

B8976060/02 Basics of Configuration

6 - 57 Volume 1

Input fi elds :

Dest. file Here, you specify the drive (e.g. A: for floppy disk or B:

for a hard disk) and the name of the destination file

(possible values drive: "A" to "Z", file name:

alphanumeric characters and the period).

Functi on keys:

SINGLE The data are read from the EPROM into the destination

file in blocks. Refer to Figs. 6.27 and 6.28 in this

chapter for the meaning of the individual blocks.

TOTAL All the data are read from the EPROM and stored in

the destination file.

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select entries from the list with the cursor keys and

enter them in the field with the return key.

Basics of Configuration B8976060/02

Vol ume 1 6 - 58

6.7 Lin k Config uration

This menu item is available in all SINEC NCM COMs but the screen layout

differs depending on the protocol or type of data transmission and is

therefore described in the relevant chapters.

B8976060/02 Basics of Configuration

6 - 59 Volume 1

6.8 Basic Configu ration

For basic configuring, the software package COM 5430 TF/COM 5431 FMS

is used under SI NEC NCM.

The screens required for basic configuration are provided by SINEC NCM

as illustrated in Fig. 6.26.

Init

Menu item Edit

Menu item

= Init Edit ...

SINEC NCM

Initial screen

Init->Edit

Screen (SYSID)

Edit->CP Init

Edit->Global network

screen

parameters Edit->Local network

screen

parameters

Network

Menu item

Network->

Network matching

screen

Fig . 6.26 Basic Configuration

Basics of Configuration B8976060/02

Vol ume 1 6 - 60

General Procedure:

During configuration, the following must be done for each station:

➣A database file must be assigned in the Init -> Edit screen per station

and the status OFFLINE entered.

➣The Edit -> CP Init screen must be com pleted, i.e.:

– as signment of an L2 addres s

– s etting of the base interface

– ent eri ng of a valid network file for each station on the bus

– ent ry of the plant designation and the date created (optional)

➣In the Edit -> Global network parameters screen:

– ent ry of the highest station address (HSA)

– ent ry of the "bus parameters"

– ent ry of the "bus parameter data"

The global network parameters only need to be entered once, since they

are automatically available to the other stations when the network file is

entered.

Once these data have been entered for every station in the network, the

network matching function is then required to match the global network

parameters. This is performed with the menu item (Network -> Network

Matching).

Other global network functions are described in Section 6.5.4.

B8976060/02 Basics of Configuration

6 - 61 Volume 1

6.8.1 Block Overview CP 5430 TF

Block Meaning

PB1 Link list for S5-S5 links

PB2 GP i nputs

PB3 GP outputs

PB4 ZP li st

PB7 DP l ist

OB2 SAP lis t for FL2 access

OB3 Sta rt I/O area I /Os lis t

OB5 Variable descri pt ion VMD

OB6 Configuration parameters

OB8 Network data return reference

VB 0...X TF dat a link block

UB1 (UL1) Initialization block (bus paramet er field)

Fig . 6.27 Block Overview CP 5430 TF

Basics of Configuration B8976060/02

Vol ume 1 6 - 62

6.8.2 Block Overview CP 5431 FMS

❑

Block Meaning

PB1 Link list for S5-S5 links

PB2 GP i nputs

PB3 GP outputs

PB5 ZI l ist

PB7 DP l ist

OB2 SAP lis t for FL2 access

OB3 Sta rt I/O area I /Os lis t

OB5 Variable descri pt ion VMD

OB8 Network data return reference

VB 0...X FMS data link block

UB1 (UL1) Initialization block (bus paramet er field)

Fig . 6.28 Block Overview CP 5431 FMS

B8976060/02 Basics of Configuration

6 - 63 Volume 1

NOTES

7 Data Transmission Using Configured S5-S5

Links

This chapter describes how to transmit data using handling blocks via

configured S5-S5 links. The following as pects are explained:

➣The applications for which this type of data transmission is suitable.

➣The principles of this type of data transmission.

➣What is meant by "links" between the stations on the bus.

➣How to assign parameters for these "links" and configure the CP 5430

TF/CP 5431 FMS modules using COM 5430 TF/COM 5431 FMS

(example Section 7.3).

➣The structure of STEP 5 programs for this type of data transmission

(example Section 7.3).

➣How to recognize and clear errors.

Areas of application for data transmission with HDBs via configured

S5-S 5 links

This type of data transmission is suitable for transmitting blocks of data of

up to 128 byt es between ac tive S IMATIC S5 programmable c ontrol lers.

B8976060/02 S5-S5 Communication

7 - 1 Volume 1

7.1 Basics of Data Transmission with HDBs on

Configured S5-S5 Links

The following applies for the CP 5430 TF/CP 5431 FMS:

The firmware of the module generates frames from the data records of the

SIMATIC S5 PLC whi ch meet t he requirements of the PROF IBUS standard.

The services of the first and second layers of the ISO/OSI reference model

are used.

You shoul d understand the followin g points:

➣What is meant by S5-S5 links and what are the characteristics of such

links?

➣How is data t ransmission via suc h link s cont rolled?

Characteristics of the S5S5 link

➣S5-S5 links allow reliable data exchange between two SIMATIC PLCs

using the SEND and RECEIVE handling blocks.

➣The start and end points of an S5-S5 link are service access points

(SAPs).

➣An SAP manages the link and provides the application process with

servic es for data transmission.

➣64 SAPs are defined, of which the SAPs 2 to 54 are available for this

type of transmission.

➣The links between the PLCs created with COM 5430 TF/COM 5431

FMS use SAPs 2 to 54. Each SAP can be assigned a particular send or

receive job number (refer to Table 7.1). The number of possible SAPs

may be restricted if other types of data transmission are used.

➣An S5-S5 link must be assigned the priority "Low", "High" or "Interrupt"

(refer to Section 7. 2.1).

S5-S5 Comm un ica tion B897 6060/02

Volume 1 7 - 2

☞Make sure there can be no overlapping of job numbers and

LSAPs for FMS links. COM 5431 FMS does not check this

automatically.

Checking data transmission in the control program

If frames are transmitted by a PLC, the PLC expects an acknowledgment.

This acknowledgment can either be positive or negative and simply

indicates whether or not the frame arrived at the communications partner.

The acknowledgment provides information about the processing status of

the frame and can be evaluated by the updated status word (ANZW) of the

HDBs CONTROL/SEND/RECEIVE.

The status word (refer to Section 7.1.2) informs you about the

following:

➣The status of a job

➣The data management

➣Any errors which may have occurred

Link to station

with L 2 address via LSAP no. with SEND-ANR and RECEIVE-ANR

12 1 101

23 2 102

34 3 103

31 32 31 131

Table 7.1 SAP-ANR (Job Num be rs) - Assign me nt Proposed by COM

B8976060/02 S5-S5 Communication

7 - 3 Volume 1

7.1.1 Sequence of the Data Tran smission

Figs. 7.1 to 7.3 are schematics showing how the relevant bits of the ANZW

change during correct or incorrect data transmission. The transmitting L2

station is defined as "local", the receiving L2 station as "remote".

ANZW local ANZW remote Meaning

0004H Previous job complete without error

0002HJob active (data being sent)

0008HJob complete with error

0001HReceive possible (data can be fetched from

the CP)

0005HPrevious job complete without error and

RECEIVE possi ble

Table 7.2 Ch anges in the Statu s Wo rd During Job Processing

S5-Adr.

ANZW

ANR

SSNR

PAFE

Anzw = Job_complete_without_error

Anzw = Job_active

(data)

BUS

SEND

S5 add.

ANZW

ANR

SSNR

PAFE

RECEIVE

Anzw = RECEIVE possible

Anzw = Job_complete_without_error

e.g. :DB

Control program sender Control program receiver

Fig. 7. 1 Job Processing - No Error Oc cu rred

S5-S5 Comm un ica tion B897 6060/02

Volume 1 7 - 4

If errors occur during the data transmission, the acknowledgment may be

from either the remote or local CP depending on the error.

S5 add.

ANZW

ANR

SSNR

PAFE

Anzw = Job_complete_with_error

Anzw = Job_active

(data)

CP PLC (remote)

BUS

SEND

e.g..:DB

Control program sender

Fig. 7. 2 Job Proces sing wi th Error Message from L ocal CP

S5 add.

ANZW

ANR

SSNR

PAFE

Anzw = Job_complete_with_error

Anzw = Job_active

(data)

CP PLC (remote)

BUS

SEND

e.g..:DB

Control program sender

Fig. 7. 3 Job Proces sing wi th Error Message from Re mote CP

B8976060/02 S5-S5 Communication

7 - 5 Volume 1

7.1.2 Checking with ANZW and PAFE

The status word is part of a double word specified in the calling HDB. The

second part of the double word is formed by the length word which

indicates how much data has already been transferred for the current job.

Following sy nchronizat ion, the status words of all the HDBs (ANR) assigned

parameters with COM 5430 TF/COM 5431 FMS contain the value 0008H. If

the ANR used is incorrectly or not configured in the COM, the ANZW has

the value 0F0AH.

Not

used Error

bits Data

mgment. Status

bits

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Job complete with error

Job complete without error

Receive possible

bit

set Job active

Fig. 7. 4 Struct ure of the Status Word, h ere: Status Bits

Not

used Error

bits Data

mgment. Status

bits

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

For meaning of

the error bits:

refer to table 7.3

Data acceptance complete

Data acceptance/transfer

enable/disable Data acceptance/

transfer active

Data transfer

complete on CP

(The data management is the responsibility of the appropriate HDB)

Fig. 7. 5 Struct ure of the Stat us Word, here : Data Manag ement

S5-S5 Comm un ica tion B897 6060/02

Volume 1 7 - 6

Bits

8 -11 Meaning of the error bits

0HNo error.

If bit 3 "job complete with error" is nevertheless set, this means that

the CP has set up the job ag ai n followin g a cold rest ar t or RESET.

1HWrong type specified in block call (QTYP/ZTYP).

2HMemory area does not exist (e.g. not initial ized).

3HMemory area too small.

The memory area specified in the HDB call (parameters Q(Z)TYP,

Q(Z)ANF, Q(Z)LAE) is for t oo small for the data transmission.

4HTimeout (QVZ).

Acknowledgment from the memory cell is absent during dat a transfer.

Remedy: check and if necessary replace the memory submodule or

check and correct the source/destination parameters.

5HIncorrect parameters assigned to status word.

The parameter "ANZW" was specified incorrectly. Remedy: correct the

parameter or set up the data block corr ectly in which the ANZW is to

be l ocated.

6HInvalid source/destination parameter.

Parameter ID "NN" or "RW" was used or the data length is too small

(=0) or longer than 128 bytes. Remedy: use the correct Q(Z)TYP

parameter; "NN" and "RW" are not allowed for this type of data

transmission. Check the data l ength.

7HLocal resources bottleneck.

There are no data buffer s available for processing the j ob. Remedy:

retrigger the job, reduce the CP load.

8HRemote resources bottleneck.

No fre e rec eive b uffer on t he remote CP. Remedy: i n the re mote PLC,

accept "old" data with the receive HDB, in the transmitting PLC repeat

the transmi t job.

Table 7.3 Erro r Bits (bits 8...1 1) in Status Wo rd

B8976060/02 S5-S5 Communication

7 - 7 Volume 1

Bits

8 -11 Meaning of the error bits

9HRemote error.

The remote CP has acknowledged the job negatively because e.g. the

SAP assignment is in correct. Remedy: rea ssign parameters for the li nk.

AHConnection error.

The sending PLC or receiving PLC is not connected to the bus.

Remedy: switch systems on/off or check bus connections.

BHHands hake e rror.

The HDB processing was incorrect or the HDB monitori ng time was

exceeded. Remedy: st art the job agai n.

CHSystem error.

Error in the system program. Remedy: inform Siemens service.

DHDisabled data block.

The data transmission i s or was disabled during the HDB processing.

EHFree

FHLink or ANR not specified.

The job is not defined on the CP. Remedy: program the j ob (link) or

correct the SSNR/ANR in t he HDB call .

Table 7.4 Erro r Bits (bits 8..1 1) in Status Wo rd (continued)

S5-S5 Comm un ica tion B897 6060/02

Volume 1 7 - 8

The parameter assignment error byte (PAFE) informs you about various

parameter assignment errors. When assigning parameters for the individual

blocks, you specify the address at which this information can be called. The

meaning of the individual bits is explained in Fig. 7.6

Error

number

7654 3210

0 - no error

1 - error

0 - no error

1 - wrong ORG format /ZTYP illegal (PLC or CP)

2 - area does not exist (DB does not exist/illegal)

3 - area too short

4 - QVZ (timeout) error no access possible

5 - wrong status word

6 - no source or destination parameters for SEND/RECEIVE

7 - interface does not exist

8 - interface not ready

9 - interface overload

A - interface busy with other modules

B - illegal ANR

C - interface (CP) not acknowledging or negatively

D - parameter/BLGR illegal (1st byte)

E - error in HDB

F - HDB call illegal (e.g. double call or

illegal change)

Fig. 7. 6 Struct ure of the Paramete r Assignment Error Byte "PAFE"

B8976060/02 S5-S5 Communication

7 - 9 Volume 1

7.2 Configuring

To assign parameters for S5-S5 functi ons, t he software package COM 5430

TF/COM 5431 FMS is used under SINEC NCM.

The screen forms required in addition to the basic initialization screen f orms

for assigning parameters are provided by SINEC NCM as shown in Fig. 7.7:

➣Link edi tor

➣Documentation and test functions.

Dealt with in separate chapters

Edit

Menu item

Documentation and

= Init Edit ...

SINEC NCM

S5-S5 Link

Links ->S5-S5 Links

Editor

Test in Chapter 12

Fig. 7. 7 S5-S5 Param et er Assignment

S5-S5 Comm un ica tion B897 6060/02

Vol ume 1 7 - 10

General procedure:

To implement a simple task (transferring data from PLC 1 to PLC 2 via

pre-confi gured li nks with HDBs) the following procedure is required:

➣The links between the PLCs must be configured (as mentioned in the

general guidelines). For planning the link, refer to Characteristics of the

S5-S5 Link (Section 7.2.1).

➣Assigning parameters to the individual CP modules. This involves

creati ng the SYSID and INIT blocks (refer to Chapter 6).

➣Configuring the links between the PLCs. This involves creating the link

blocks (ref er to Secti on 7.1) according to the planned task.

➣Programming the CPUs of the PLCs according to the task. This

invol ves HDBs, OBs, FBs and DBs.

7.2. 1 C onfiguring S 5-S5 Li nks

With the link editor of the COM 5430 TF/COM 5431 FMS software package

you assign parameters for the links between two stations on the bus. You

can also generate default S5-S5 links valid throughout the network (refer to

Section 6.5.4.4).

SEND / ANR 2 RECEIVE / ANR 101

STATION 1 STATION 1

SAP 2 SAP3

L2 link

Fig. 7. 8 Schematic Representation of a Link Between 2 Stations

B8976060/02 S5-S5 Communication

7 - 11 Volume 1

These links are either saved in a submodule file (offline mode) or written

directly to the CP submodule or modified there (online mode). This means

that submodule files created offline can also be loaded on the CP or that

the contents of the CP submodule can be saved in a fil e.

Select Edit -> Links -> S5-S5 Links to call the following screen. The screen

is structured as follows:

Input fi elds

Remote L2

station addres s Here, you enter the address of the remote station

(range of values: 1 .. 31)

PRIO (H/L/I): Specifies the priority of the jobs. The default is "LOW".

(Possible entries: "LOW", "HIGH" "Interr upt").

"LOW": frames with this priority are normal frames. After receiving the

token, and if there is sufficient token holding time, frames with low priority

are sent.

Link Editor S5-S5 Links

Block does not exist

Local L2 station address:

PRIO (H/L/I):

SSAP :

DSAP :

Remote L2 station address:

Parameters sending:

SSNR:

ANR:

Parameters receiving:

SSNR:

ANR:

SELECT

+1 -1 INPUT DELETE OK

CP type:

Source: (EXIT)

HELP

Fig. 7. 9 S5-S5 Links Conf igurat ion Scre en

S5-S5 Comm un ica tion B897 6060/02

Vol ume 1 7 - 12

"High": frames with this priority are given preference during data exchange.

This means that if an L2 station has no more token time available when it

receives the token, it can still t ransmit a high prior ity frame.

"Interrupt": these frames are handled just like high priority frames during

data exchange. They also trigger an interrupt in the receiving PLC

(IR-A/B/C/D).

SSAP: Local (Source) Service Access Point. (range of values:

2 .. 33).

Make sure you exclude the possibility of

overlapping with LSAPs for FMS links.

DSAP: Remote (Destination) Service Access Point. (range of

values: 2 .. 33, 56).

Make sure you exclude the possibility of

overlapping with LSAPs for FMS links.

Parameters

sending/receiving: Parameters for the local station for transmitting and

receiving are entered here.

SSNR: Interface number, corresponds to the number of the

CPU and therefore forms the CPU-CP interface. (range

of values 0..3).

ANR: Job number via which the job is triggered. (range of

values transmitting :1..32, range of values receiving

:101..132).

Make sure you exclude the possibility of

overlapping with job numbers (ANR) for FMS links.

Output fields

Local L2 station

address: L2 address currently being processed.

B8976060/02 S5-S5 Communication

7 - 13 Volume 1

Functi on keys:

+1 Page forwards through the links for several S5-S5 links.

-1 Page backwards through the links for several S5-S5

links.

INPUT Prepare next input.

DELETE Delete the input link.

OK Enter the data in the link block.

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select entries from the list with the cursor keys and

enter them in the field with the return key.

S5-S5 Comm un ica tion B897 6060/02

Vol ume 1 7 - 14

7.3 Example of a Program for an S5-S5 Link

The aim of the example is to set up a communication system that allows

simple control of the activity on a SINEC L2 bus system. It should be

possible to formulate the basic information required to set up and operate a

SINEC L2 bus system and to control the activity on the bus system. The

example illustrates how to program the CPU and assign parameters for the

CP as well as triggering and checking the data transmission.

You should have worked through Chapters 3 to 6 of this manual and be

familiar with the handling blocks and STEP 5.

Hardware and software requirements

The following hardware is necessary:

➣Two SIMATIC S5 programmable controllers (PLC 1: S5-155U and

PLC 2: S5-115U)

➣One CP 5430 TF or CP 5431 FMS per PLC

➣One EPROM or RAM submodule per CP 5430 TF or CP 5431 FMS

➣One RS 485 bus terminal per CP

➣SINEC L2 bus cable

➣At least one PG 710, PG 730, PG 750 or PG 770,

or PC

B8976060/02 S5-S5 Communication

7 - 15 Volume 1

The following software packages are also required:

➣COM 5430 TF/COM 5431 FMS under SINEC NCM

➣PG software for STEP 5 programming

➣Appropriate handling blocks for the PLCs

➣Diskette with the example program.

. .

interface

Bus cable

Bus terminal 1

with terminal cable Bus terminal 2

with terminal cable

PLC1 (S5-155U) PLC2 (S5-115U)

interface

(AS511)

interface

(AS511)

Terminator

activated

PG-

inter-

face

(AS511)

Fig . 7.10 S che mati c Rep res enta tio n of t he Ha rdw are C omp onen ts

S5-S5 Comm un ica tion B897 6060/02

Vol ume 1 7 - 16

7.3. 1 Out line of the Task

Data from PLC 1 will be transmitted via confi gured links using HDBs to PLC

2 and data will be transmitted via configured links using HDBs from PLC 2

to PLC 1. The following tasks must be performed in the individual PLCs:

PL C 1

➣DW 1 i s incremented in DB 10.

➣After incrementing DW 1, this is transmitted to PLC 2 using the handling

block SEND.

➣HDB SEND is assigned the values ANR = 2 and SSNR = 0.

➣PLC 1 has the L2 address 1.

➣The data word received from PLC 2 is stored in DB 12 DW 1.

➣HDB RECEIVE is assigned values ANR=102 and SSNR=0.

B8976060/02 S5-S5 Communication

7 - 17 Volume 1

PL C 2

➣DW 1 i s incremented in DB 20.

➣After DW 1 has been incremented in DB 20, t his is transmitted to PLC 1

using HDB SEND.

➣HDB SEND is assigned the values ANR=1 and SSNR=4.

➣PLC 2 has the L2 address 2.

➣The data sent from PLC 1 are received in PLC 2 and st ored in DB 22.

➣HDB RECEIVE is used for this. The HDB is assigned the values

A-NR=101 and SSNR=4.

RS485 RS485

PLC 1 PLC 2

SAP

2SAP

Send-ANR 1 RECEIVE-ANR 101

DB 10 DB 22

SSNR 0 SSNR 4

DW 1

L2 add 1 L2 add 2

DW 1

DB 12 DB 20

DW 1 DW 1

Fig . 7.11 S yste m C onfig ura tion fo r th e Exam pl e of Dat a Tra nsm issio n wit h HD Bs

S5-S5 Comm un ica tion B897 6060/02

Vol ume 1 7 - 18

7.3.1.1 Program for PLC 1 (S5-155 U)

When the PLC starts up, the CP interface is synchronized with the

SYNCHRON handling block.

PLC 1 increments data word DW 1 in DB10 and then transmits it to PLC 2.

Once the job is completed, i.e. the status of the ANZW is "complete without

error", the data word is incremented again and transmitted to PLC 2.

Transmission is triggered in PLC 1 with a SEND HDB. This is called in FB

2. Before each SEND call, the data bytes of DW 1 are incremented in DB

10. This takes plac e in FB 1. The function bloc ks and FB 2 are called in OB

Before triggering a new send job, the following statuses must be checked:

➣Has the corresponding DW been incremented (F2.0 =1)?

➣Is the previous SEND job complete (F11.1 = 0) and free of error

(F 11.2 =1)?

➣Has no parameter assignment error occurred (F15.0 = 0)?

In addition to this, PLC 1 receives a DW from PLC 2 which must be written

to DW 1 in DB 12.

If the status of ANZW FW 110 in FB 102 is "receive possible", the

RECEIVE HDB is called and the receive word stored in the DB.

➣Is "RECEIVE possible" (F111.0=1)?

➣Has no parameter assignment occurred (F115.0=0).

B8976060/02 S5-S5 Communication

7 - 19 Volume 1

7.3.1.2 Program for PLC 2 (S5-115 U)

The CP interface of PLC 2 must also be synchronized during start-up using

the SYNCHRON handling block. The SYNCHRON calls must therefore be

programmed for the PLC used in blocks OB 21 (for manual warm restart)

and OB 22 (warm restart following power down).

The synchronization is triggered and checked in FB 111 STARTUP (not a

standard FB). If an error occurs, a flag bit is set which can be evaluated by

the user program.

The transmit trigger in PLC 2 uses a SEND HDB. This is called in FB 10.

Before each SE ND call, the data bytes must be incremented. This occurs in

FB 20. Function blocks FB 1 and FB 2 are called in OB 1.

The data transmitted by PLC 1 are received in PLC 2 using the RECEIVE

handling block. This HDB is called in FB 101.

7.3.2 Transferring the Configuration Data for the CP 5430 TF/CP

5431 FMS and the STEP 5 User Program

To be able to implement the practical example for S5-S5 communication,

follow the procedure outlined below (and refer to Chapter 16):

➣Transfer the following COM 5430 TF/COM 5431 FMS database files to

the CPs you are using:

When using the CP 5430 TF under the network file AGAGONCM.NET

– f or station 1 OAGAG.155

– f or station 2 OAGAG.115.

S5-S5 Comm un ica tion B897 6060/02

Vol ume 1 7 - 20

When using the CP 5431 FMS under the network file AGAGQNCM.NET

– f or station 1 QAGAG.155

– f or station 2 QAGAG.115.

➣Transfer the following STEP 5 files to the programmable controllers you

are using:

– For P LC 1 (S5-155U) the file AGAGT1ST.S5D

– For P LC 2 (S5-115U) the file AGAGT2ST.S5D.

B8976060/02 S5-S5 Communication

7 - 21 Volume 1

7.3.3 Monitoring the Data Transmission

The data transmission can be monitored best by using two PGs. Connect

one PG to one CPU and display the data blocks, the status word (ANZW)

and the parameter assignment error byte (PAFE) with which the data

transmission can be monitored. The following table lists the blocks, flag

words and flag bytes relevant for checking this example.

The data words in the DBs must change in rapid succession. If this is not

the case, there is a transmission or parameter assignment error and the

type of error can be found by evaluating the ANZW and PAFE bits.

Section 7.1.2 explains the significance of the bits in ANZW and PAFE.

These bytes must be continuously evaluated t o check the dat a transmission

and to be abl e to localize and remedy any errors which may occur. ❑

PLC 1 PLC 2

DB transmitted/received

data DB 10 (DW 1)

DB 12 (DW 1) DB 20 ( DW 1)

DB 22 ( DW 1)

ANZW

FB 120 SEND

FB 121 RECEIVE

FB 244 SEND

FB 245 RECEIVE

PAFE

FB 120 SEND

FB 121 RECEIVE

FB 244 SEND

FB 245 RECEIVE

FW 10

FW 11 0

FY 15

FY 11 5

FW 20

FW 210

FY 25

FY 215

Table 7.5 DB Transmitted and Received Data, Status Words and PAFE Codes

S5-S5 Comm un ica tion B897 6060/02

Vol ume 1 7 - 22

8 Data Transmission by Direct Acce ss to

Layer 2 Services

This chapter explai ns the f ollowi ng aspects:

➣The devices and applications for which "data transmission by direct

access to layer 2 services" is suitable.

➣How this type of data transmission functions.

➣How this "link" is configured with COM 5430 TF/COM 5431 FMS and

how to assign parameters for the CP 5430 TF/CP 5431 FMS module

(example program in Section 8.4).

➣The STEP 5 programs for this type of data transmission (example

program in Section 8.4).

➣How to detect and remedy errors.

Areas of application for data transmission by direct access to layer 2

services

This type of data transmission is suitable for communication between two

SIMATIC S5 programmable controllers and remote PROFIBUS compatible

programmable controllers or field devices. SIMATIC S5 programmable

controllers can also communicate with each other with this type of data

transmission; however, for this situation, data transmission via S5-S5 links

is easier to implement (refer to Chapter 7).

With data transmission by di rect access to layer 2 services you can transmit

or receive blocks of data with a maximum length of 242 bytes.

B8976060/02 Free Layer 2 Communication

8 - 1 Volume 1

8.1 Basics of Data Transmission using Layer 2

Services

The following applies to the CP 5430 TF/CP 5431 FMS:

The firmware of the modules generates S5 frames from the data records of

the SIMATIC S5 PLC which comply with the requirements of the

PROFIBUS standard. The services of the first and second layer of the

ISO/OSI reference model are used. The services of layer 2 are also known

as FDL (Fieldbus Data Link) services. The terms used are explained in the

model or in the appendix.

What you need to know

➣Which layer 2 services are available for data transmission?

➣How do you use these services for data transfer?

➣How does this type of data transmission function and how is it used

correctly?

➣How to handle and check data transmission using these services from

the point of view of the control program.

Free Layer 2 Communication B8976060/02

Volume 1 8 - 2

8.1.1 FDL Services implemented in a CP 5430 TF/CP 5431 FMS for

Data Transmission

The layer 2 firmware of the CP 5430 TF/CP 5431 FMS provides various

services for reliable data transmission which can be used in the control

program. In concrete terms this means that the control program can request

layer 2 data transmission services and can evaluate confirmations (and

error messages) made available by this layer. You must also evaluate

indications from layer 2 when a frame is received by the CP.

SDA (Send

Data with

Acknowledge):

Data is sent to the remote station and this

acknowledges reception.

SDN (Send

Data with No

Acknowledge):

Data is sent to the remote station but this does not

acknowledge reception.

SRD (Send and

Request Data): Data is sent to the remote station and at the same time

data is requested from it. The requested data must

already be prepared by the remote station in a transfer

buffer.

RPL_UPD_S

(RePLy-

UPDate-Single):

With this service the transfer buffer is filled with data to

be fetched by the communications partner using the

SRD service. Once the data have been fetched, the

buffer is empty.

RPL_UPD_M

(RePLy-UPDate

-Multiple):

With this service the transfer buffer is filled with data to

be fetched by the communications partner using the

SRD service. The data are not deleted after they have

been fetched (they remain available until they are

overwritten).

You use these services provided by the layer 2 firmware of the CP 5430

TF/CP 5431 FMS in the STEP 5 control program by programming handling

block calls.

B8976060/02 Free Layer 2 Communication

8 - 3 Volume 1

Using the services for the actual data transfer

The data to be transmitted (max. 242 bytes "net data") and the received

data (also max. 242 bytes) should be stored in a data block; it can,

however, also be stored in the flag area.

The data to be transmitted and received is always preceded by an 8 byte

header containing control and status information for the layer 2 firmware.

When calculating the memory required for transmitted and received data

(parameters QLAE or ZLAE when calling a handling block) these 8 bytes

must be taken into account. The data including the header form the general

interface for calling the services, known as the "job buffer". The action is

triggered by an application program via the job buffer. The job buffers are

transferred to the interface module via the dual-port RAM using the

standard handling blocks. The job buffer itself is used to transfer the

parameters for correct execution of the service on the i nterface module. Job

buffers must always be in the data block area or in the extended data block

area and are restricted to a maximum length of 250 bytes. Each job buffer

consists of a header and a data .

Fig. 8.1 illustrates the basic structure of a job buffer. The description of the

header is in the key to the figure. The user must create the job buffer for

specific services .

Free Layer 2 Communication B8976060/02

Volume 1 8 - 4

Description of the parameters in the h eader

com_class: 1 byte, format: KH

FDL request =00H in transmit buffer:

Service request to layer 2

FDL confirmation=01H in receive buffer:

Acknowledgment from layer 2 after FDL request

FDL indication =02H in receive buffer:

Indicates that the data was received.

user_id: 1 by te, format: KH

Freely assignable ID which is returned unchanged with

a confirmation. In an indication the value is "0". With the

user_id it is possible to establish a unique assignment

between request and confirmation.

com_class

user_id

service_code

link_status

Byte

Header service_class

DSAP/RSAP

rem_add_station

rem_add_segment

Data

249

Fig. 8. 1 Structure of the Header with a Job Buffer to be Sent/Received

B8976060/02 Free Layer 2 Communication

8 - 5 Volume 1

service_code: 1 byt e, form at: KH

This identifies the type of service requested for the

transmitti ng job buf fer:

SDA=00H

SDN=01H

SRD=03H

RPL_UPD_S=06H

RPL_UPD_M=07H

This identifies the type of service provided by layer 2

for the received job buffer.

SDA=00H

SDN=01H

SRD=03H

only with FDL confirmation:

RPL_UPD_S=06H

RPL_UPD_M=07H

only with FDL indication:

SDN_MULTICAST=7FH

link_status: 1 byte, format: K H

Table 8.1 describes the link_status for a confirmation

Table 8.2 describes the link_status for an SRD

indication

service-cl ass: 1 byte, format: KH

Service class specifies the prior ity of the service

Low = 00H

High = 10H

DSAP/RSAP: 1 byte, format: KH

When transmitting, number of the destination SAP

coded in hexadecimal (default SAP = FFH)

When receiving, number of the remote SAP, coded in

hexadecimal (default SAP = FFH)

Free Layer 2 Communication B8976060/02

Volume 1 8 - 6

rem_add_station: 1 byte, format: K H

When transmitting, this indicates the station address of

the receiver station, coded in hexadecimal.

When receiving, this indicates t he stati on address of t he

transmitting station, coded in hexadecimal.

rem_add_segment: by te, format: KH

Logical segment address, FFH always entered (at

present, no other segments can be addressed)

Data: 241 bytes, format: KH

When transmitting, the data to be transmitted are

entered here

When receiving, this contains the received data (only

with indication and SRD confirmati on)

B8976060/02 Free Layer 2 Communication

8 - 7 Volume 1

Value of

link_status Abbreviation

PROFIBUS Meaning

SDA

00H

01H

02H

03H

11H

12H

positive acknowledgment, service executed.

positive acknowledgment, remote user/FDL interface error

positive acknowledgment, resources of the remote FDL

controller not available.

service or re m_add on rem ot e SAP not activate d.

no reaction (Ack./Res.) from the remote station.

local FDL/PHY not in the logical token ring or not connected

to bu s.

SDN

00H

12H

positive acknowledgment, transfer of data by local FDL/PHY

controller completed.

local FDL/PHY not in the logical token ring or not connected

to bu s.

SRD

08H

0AH

01H

02H

03H

09H

0CH

0DH

11H

12H

RDL

RDH

positive acknowledgment, reply data low exist.

positive acknowledgment, remote user/FDL interface error.

positive acknowledgment, resources of the remote FDL

controller not available.

service or re m_add on rem ot e SAP not activate d.

positive acknowledgment, resources of the remote FDL

controller not available.

re ply da ta ( low) e xist, but nega tive a ckno wle dgme nt f or

trans mitted d ata, 09H (NR).

re ply da ta ( high) e xist, bu t nega tiv e ackno wle dgme nt for

trans mitted d ata , 09H (NR).

no reaction (Ack./Res.) from the remote station.

local FDL/PHY not in the logical token ring or not connected

to bu s.

REPLY_UPDATE_SINGLE/REPLAY_UPDATE_MULTIPLE

00H

12HOK

LR pos itiv e ack nowle dg ment , dat a are a load ed .

re spon se r esou rce curr ently being used by MAC .

SDA/SDN/SRD/REPLY_UPDATE_SINGLE/REPLAY_UPDATE_MULTIPLE

10H

15HLS

IV service on local SAP not a ctivated .

inva lid param et ers in the r eque st he ader .

Table 8.1 Meaning of the Values in Byte 3 (link_status) in the Confirmation Header

Free Layer 2 Communication B8976060/02

Volume 1 8 - 8

8.1.2 How Data Transmission by Direct Access to Layer 2 Services

Functions

The first 8 bytes of the block of data to be transmitted (in the header)

contain control information for the layer 2 firmware. The receiver can also

evaluate the first 8 bytes of the received block of data as status information

(e.g. error messages (link_status)).

With the data transmission services SDA, SDN and SRD, the CP 5430

TF/CP 5431 FMS uses the control information from the header of the data

to "package" the transmitted data in a frame which is then transmitted by

the SINEC L2 bus.

The basic sequence of communication via the free layer 2 access is

illustrated in Fig. 8.2.

Value of

link_status Abbreviation

PROFIBUS Meaning

SRD (Indication)

20HLO in this SRD exchange, the reply was with low priority

data.

21HHI in this SRD exchange, the reply was with high priority

data.

22HNO_DATA in this SRD exchange, no reply data were sent

Table 8.2 Meaning of the Values in Byte 3 (Link Status) in the Indication Header

B8976060/02 Free Layer 2 Communication

8 - 9 Volume 1

The link to communication end points is via so-called channels. To

communicate via the free layer 2 access, a link must be configured using

"channels" with the link editor (Section 8.3.1).

Characteristics of the free channels

The communication start and end point of a channel between two stations

on the bus is known as a service access point (SAP). An SAP is a further

address criterion in addition to the station address. As already mentioned in

the model, a channel (SAP) is addressed by a job number (ANR). An SAP

number must be specified for each channel to be able to use layer 2

services (refer to Fig. 8.3). The assignment of ANR and local SAP is made

when configuring with the COM.

☞Make sure that any possibility of overlapping with SAPs used

for DP is excluded.

CPU memory CP 5430

frame

Header

Data

field

Firm-

ware

layer2

layer1

HDB (SEND)

HDB (RECEIVE)

Fig. 8. 2 Basic Sequence of Communication using Free Layer 2 Access

Free Layer 2 Communication B8976060/02

Vol ume 1 8 - 10

With t he link edito r yo u specif y the followi ng:

➣The interface number

➣The assignment between:

– SEND/RECEIVE job numbers ANR (range: 134 to 186). The same

ANR is used both for transmitting and receiving.

– Num ber of the local service access point (SAP; range 2...54, 56)

➣Priority of the link.

With the link editor, the link parameters of the local station can be selected.

The missing information must be stored in the header of the

corresponding data package; this includes the following:

➣DSAP (destination SAP) of the remote station

➣Address of the remote station

➣Required layer 2 service (SDA, SDN or SRD).

CPU

Control

program

ANR layer 2

services

SIMATIC S5 PLC

Channel layer 2

services

SAP

no.

LOCAL SAP

SAP

no.

REMOTE SAP

Control

program

PROFIBUS-compatible L2 station

(REMOTE)

(LOCAL)

Fig. 8. 3 Access to L ayer 2 Services via Service Ac ce ss Points (SAPs)

B8976060/02 Free Layer 2 Communication

8 - 11 Volume 1

☞The firmware of the CP 5430 TF/CP 5431 FMS activates all the

specified SAPs for the services SDA, SDN and SRD (both for

the initiator and responder functions). The L2 address range

of the remote station is not restricted.

Once the "channels" have been assigned parameters with the link editor for

every L2 station with a CP 5430 TF/CP 5431 FMS that is intended to

communicate via the free layer 2 access, the required data transfer must be

coordinated in the control program.

Free Layer 2 Communication B8976060/02

Vol ume 1 8 - 12

8.1.3 Handling the Individual Data Transmission Services from the

Poin t of View of the Control Prog ram

The SEND block can be used to transfer an FDL request. FDL

confirmations or FDL indications are accepted in the PLC with a RECEIVE

HDB. Via the bits in the status word which can be updated with the

CONTROL block, the SEND or RECEIVE HDBs can be controlled.

The status word contains information about the status of a job, information

about data management and error bits. In the figures illustrating the

sequence of the control program (refer to Figs. 8.7 to 8.11) the change in

the status word (ANZW) is always visible.

8.1.4 Checking the Data Transmission in the Control Program

usi ng ANZW and PAFE

If messages are sent by a PLC, the PLC expects an acknowledgment. This

acknowledgment can be either positive or negative and simply indicates

whether the frame arrived at the communications partner or not. The

acknowledgment provides information about the processing status of the

frame and can be evaluated from the updated status word (ANZW) of the

CONTROL/SEND/RECEIVE HDBs.

The status word informs you about the fo llowing:

➣the status of the job

➣the data management

➣any errors

Following synchronization, the status words of all the links (ANR) assigned

parameters with COM 5430 TF/COM 5431 FMS contain the value 0008H. If

the link was not defined, the ANZW has the value 0F0AH

B8976060/02 Free Layer 2 Communication

8 - 13 Volume 1

The status word is part of a double wor d defi ned by the parameter ANZW in

the HDB call. The second part of the double word is the length word which

indicates how many data have already been transferred for the current job.

The structure of the status word is basically identical to that for S5-S5

communication, howev er, it is handled di fferently .

Structure of a status word

☞Apart from the status word, you must also evaluate the

"link_status" byte from the confirmation header (or indication

header of an SRD indication) in the control program. The

significance of the information in the "link_status" byte (or in

the indication header of an SRD indication) can be seen in

Table 8.1/8.2.

Not

used Error

bits Data

mgment Status

bits

15 1413 12 11 10 9 8 7 6 5 4 3 2 1 0

Job complete with error

Error transferring a request or when accepting

an indication or confirmation

Job complete without error

(with SEND HDB: correct transfer of an FDL request

with the RECEIVE HDB: correct transfer of

a confirmation or indication)

Job active

(Request being processed or confirmation of request

not yet received) only set when the SAP is disabled or

Receive possible

Confirmation or indication exists and can be accepted with the

RECEIVE HDB

not yet released

Fig. 8. 4 Struct ure of the Status Word, h ere: Status Bits

Free Layer 2 Communication B8976060/02

Vol ume 1 8 - 14

If the bit "job complete with error" is set in the status bits, the "error bits"

provide the coding of the cause. With the "channels" only the PLC error is

indicated (error numbers 1 to 6). Errors processing an FDL request are

transferred with the corresponding confirmation. The error number 15 (0FH)

is set by the CP when the corresponding SAP was not enabled. With this

number, the bits "job complete with error" and "job active" are also set

(ANZW 0F0AH). The way in which this data transmission is handled

between two SIMATIC PLCs can be seen in Figs. 8.7 to 8.11. Before these

figures, there is an explanation of the sequence of the transmission. Figs.

8.7 to 8.11 also take into account the status bits in the status word (e.g.

ANZW....1H" m eans "RECE IVE possible" ).

Data acceptance/transfer

(enable/disable bit)

Reserved

Data transfer complete on CP

(FDL request was transferred),

This bit is reset by the HDB

Data acceptance complete

(FDL indication or FDL confirmation

transferred to PLC)

This bit is reset by the HDB

Error

bits Data

mgment. Status

bits

For meaning of

the error bits:

refer to Table 8.3

11 10 9 8 7 6 5 4 3 2 1 0

This bit is not required here, no

fragmentation

Fig. 8. 5 Struct ure of the Stat us Word, here : Data Manag ement

B8976060/02 Free Layer 2 Communication

8 - 15 Volume 1

Bits

8-11 Meaning of the error bits

0 No erro r.

If bit 3 " job c ompl ete with erro r" is n ev erthe less s et , this m e ans th at t he C P has

set up t he job again fo llo wing a cold restart o r RESET.

1 Wrong type specifie d in block call (QTYP/ZT YP).

2 M emo ry ar ea do es no t exis t (e. g. n ot ini tializ ed)

3 Memory area too small.

The memory area specified in the HDB call (parameters Q(Z)TYP, Q(Z)ANF,

Q(Z)L AE) is t oo small fo r the data transmission .

4 Timeout (QVZ).

Acknowledgement from the memory cell is absent during data transfer. Remedy:

che ck an d if nece ssar y rep lace t he mem ory su bm odul e or chec k and cor rect t he

source/destination parameters.

5 Incorrect parameters assigned to status word.

The p ara meter "ANZW" was specified incorrect ly. Remedy: correct th e

parameter or set up the data block correctly in which the ANZW is to be located.

6 Invalid source/destination parameter.

Parameter ID "NN" or "RW" was used or the data length is too small (=0) or

longer than 128 bytes. Remedy: use the correct Q(Z)TYP parameter; "NN" and

"RW" are not allowed for this type of data transmission. Check the data length.

7 L ocal r eso urce b ot tlene ck.

Th ere ar e no data buf fers a vaila ble for pr oce ssing the jo b. Remed y: r etri gger th e

job, reduce the CP load.

B Handshake error.

Th e HDB p roc essi ng w as inc orre ct or the H DB m onit orin g ti me wa s e xcee ded.

Re medy : s tart the jo b aga in.

C Syste m error !

Il legal ser vice c ode s ervic e_co de or er ror in syst em pr ogra m.

Re medy : c heck servic e_co de or info rm Siem ens servic e.

D D ata f iel d bloc ked!

Th e dat a tra nsm issio n is or w as d isab led du rin g HDB exe cutio n (con trol bit

disable/enable in status word set to disable).

E free

F Job or channel not programmed !

Programming e rror or incorrect HDB call (parameter SSNR/ANR).

Remedy: p rogram job numbe r (ANR) as "free channel" (ty pe:FREE) or correct

SSNR/ANR for HDB call.

Table 8.3 Erro r Bits (bits 8..1 1) in the Statu s Word

Free Layer 2 Communication B8976060/02

Vol ume 1 8 - 16

Structure of the parameter assignment error byte

The parameter assignment error byte (PAFE) informs you about various

parameter assignment errors. When you assign parameters to the individual

blocks, you specify the address at which this information is available. The

meaning of the individual bits is explained in Fig. 8.6.

Error

number

7654 3210

0 - no error

1 - error

0 - no error

1 - wrong ORG format /ZTYP illegal (PLC or CP)

2 - area does not exist (DB does not exist/illegal)

3 - area too short

4 - QVZ (timeout) error no access possible

5 - wrong status word

6 - no source or destination parameters for SEND/RECEIVE

7 - interface does not exist

8 - interface not ready

9 - interface overload

A - interface busy with other modules

B - illegal ANR

C - interface (CP) not acknowledging or negatively

D - parameter/BLGR illegal (1st byte)

E - error in HDB

F - HDB call illegal (e.g. double call or

illegal change)

Fig. 8. 6 Struct ure of the Paramete r Assignment Error Byte "PAFE"

B8976060/02 Free Layer 2 Communication

8 - 17 Volume 1

8.1.5 Sequence of the Data Tran smission

To understand how the services are handled, the following section shows

how a data exchange must be coordinated in the control program

depending on the data transmission service used. It is assumed that the

transmitter and receiver are SIMATIC PLCs which exchange data via the

CP 5430 TF/CP 5431 FMS.

Data are transmitted with the SEND HDB, data and acknowledgments

(confirmation, indication) are received with the RECEIVE HDB. To be able

to monitor the data exchange, you must constantly evaluate the status word

for this job.

☞As long as an indication is waiting to be accepted by the

PLC, the corresponding SAP does not have a receive b uffer.

Free Layer 2 Communication B8976060/02

Vol ume 1 8 - 18

Start-up OBs for SIMATIC S5 PLCs

You must call the SYNCHRON handling block for the interface number of

the CP 5430 TF/CP 5431 FMS in the start-up OB.

Transmitti ng and receiving data with acknowledgment (service: SDA)

Sequence of the transmission

☞SEND and RECEIVE job numbers must match the

programmed job numbers (link editor of the COM 5430

TF/COM 5431 FMS ).

If the link was not programmed with the link editor of COM

5430 TF/COM 5431 FMS, the job (triggering the SEND HDB) is

blocked by the firmware of the CP ( ANZW 0F0AH)!

Request to layer 2

(Evaluation of the status word))

The data preceded by an

8-byte header are sent

with the SEND HDB

The receiver is informed

that data have been

received

The sender is informed that

an acknowledgment has

arrived from the receiving CP

The receiver fetches the

received data with the RECEIVE

HDB from the CP.

The first 8 bytes contain

management information (header)

Indication

Confirmation

The sender fetches the

confirmation consisting of an

8-byte header from the CP.

To do this it uses the

RECEIVE HDB

(Evaluation of the status word)

SENDER RECEIVER

(Evaluation of the status word))

B8976060/02 Free Layer 2 Communication

8 - 19 Volume 1

Control program sender

S5 add.

ANZW

ANR

SSNR

PAFE

Anzw = Job_active receive possible

Anzw = Job_active

(data)

BUS

SEND

Anzw = RECEIVE possible

SDA-

Request

e.g..:DB

Header

DATA

(...2

(...1 or (...5

if previously

(...4

(...3 S5 add.

ANZW

ANR

SSNR

PAFE

RECEIVE

e.g..:DB

Header

DATA

S5-Adr.

ANZW

ANR

SSNR

PAFE

RECEIVE

e.g.:DB

Header

Anzw = Job_complete_without_error

(...4

Control program receiver

Anzw = Job_complete_without_error

Fig. 8. 7 Transm itting and Receiving Data with Acknowledgme nt (Service SDA)

Free Layer 2 Communication B8976060/02

Vol ume 1 8 - 20

Transmitting and receiving data without acknowledgment (service:

SDN)

Sequence of the transmission

☞In contrast to the SDA service, the sender does not receive

an acknowledgment from the receiver CP with the SDN

service, but simply an acknowledgment from its own local

CP.

Request to layer 2

The data preceded by an

8-byte header are sent

with the SEND HDB

The receiver is informed

that data have been

received

The receiver fetches the

received data with the RECEIVE

HDB from the CP.

The first 8 bytes contain

management information (header)

Indication

SENDER RECEIVER

(Evaluation of the status word))

B8976060/02 Free Layer 2 Communication

8 - 21 Volume 1

Transmitting data with request to receiver to return data (service: SRD)

Sequence of the transmission:

Before the sender requests data from the receiver, the receiver must

prepare the requested data in a CP buffer (responder function). The

receiver either uses the "reply update single (RPL_UPD_S)" or the "reply

update multipl e (RPL_UP D_M)" serv ice.

The RPL_UPD_S service prepares the requested data once. After the

requesting station has read the data from the buffer the buffer is empty and

must be filled again with an RPL_UPD_S service. The user is informed that

the data have been fetched in the SRD indication (link_status). If the

requesting station finds an empty buffer, it is informed by an error message

in the confirmation header (link_status).

Control program sender

S5 add.

ANZW

ANR

SSNR

PAFE

Anzw = Job_active receive possible

Anzw = Job_active

(data)

BUS

SEND

Anzw = RECEIVE possible

SDN-

Request

e.g..:DB

Header

DATA

(...2

(...1 or (...5

if previously

(...4

(...3 S5 add.

ANZW

ANR

SSNR

PAFE

RECEIVE

e.g..:DB

Header

DATA

S5-Adr.

ANZW

ANR

SSNR

PAFE

RECEIVE

e.g.:DB

Header

Anzw = Job_complete_without_error

(...4

Control program receiver

Anzw = Job_complete_without_error

Fig. 8. 8 Tra nsm itti ng an d Re ceivi ng Data with out A ckn owle dgm ent ( Servic e: SD N)

Free Layer 2 Communication B8976060/02

Vol ume 1 8 - 22

With the RPL_UPD_M service, the data remain in the buffer until the buffer

is overwritten. This means that the data can be read out more than once.

How the data are writ ten t o the buffer:

(Evaluation of status word))

RECEIVER

Confirmation

When the data are entered in

buffer, the condition code word

of the receiver changes.

The acknowledgment consists

of an 8-byte header and can

be received with the

RECEIVE HDB

The receiver supplies the

buffer with data (responder

function), which the sender

fetches with the SRD service.

To allow this, the receiver sends

this data with an 8-byte header

to its own CP with the SEND HDB

(Evaluation of status word))

Fig. 8. 9 RPL_UPD_S service

B8976060/02 Free Layer 2 Communication

8 - 23 Volume 1

CP CP (remote)

BUS

Anzw = Job active (...2

Anzw = Job_complete_without_error

S5 add.

ANZW

ANR

SSNR

e.g..:DB

Header

DATA2

Request data

as soon as data are read out of

the buffer by the sender, it must

be filled again (otherwise error

message on the sender).

This only applies to the service

RPL_UPD_S

Anzw = Receive possible (...3

RPL_UPD_S

SEND

PAFE

S5 add.

ANZW

ANR

SSNR

PAFE

RECEIVE

e.g..:DB

Header

(...4H)

Fig . 8.10 RPL _UPD_S service (continued)

Free Layer 2 Communication B8976060/02

Vol ume 1 8 - 24

Once the requirements for the SRD service are met, the sender can

transmit data to the receiver and fetch the data from the receiver’s buffer.

Fig. 8.11 is the logical continuation of the procedure outlined in Fig. 8.10.

Request to layer 2

(Evaluation of the status word))

The data preceded by an

8-byte header are sent

with the SEND HDB

The receiver is informed

that data have been

received

The sender is informed that

an acknowledgment has

arrived from the receiving CP

Indication

Confirmation

The sender fetches the

confirmation with a RECEIVE

HDB. It consists of an 8-byte

header and the data from the

buffer of the (receiver) CP

(Evaluation of the status word)

SENDER RECEIVER

(Evaluation of the status word))

The receiver fetches the

received data with the RECEIVE

HDB from the CP. The first 8 bytes

contain management info (header)

The data previously provided by the

receiver were automatically returned

with the confirmation. The now

empty buffer can be filled with data

again.

B8976060/02 Free Layer 2 Communication

8 - 25 Volume 1

Control program sender

S5 add.

ANZW

ANR

SSNR

PAFE

Anzw = Job_active receive possible

Anzw = Job_active

(data)

BUS

SEND

Anzw = RECEIVE possible

SRD

request

e.g..:DB

Header

DATA1

(...2

(...3 S5 add.

ANZW

ANR

SSNR

PAFE

RECEIVE

e.g..:DB

Header

DATA1

S5 add.

ANZW

ANR

SSNR

PAFE

RECEIVE

e.g.:DB

Header

Anzw = Job_complete_without_error

(...4

)

Control program receiver

Anzw = Job_complete_without_error

SRD ind

Data2

(data)

(...1 or

(...5 H)

Fig . 8.11 Tra nsmitti ng Data with Req uest for Re ceiver to Return Data ( SRD)

Free Layer 2 Communication B8976060/02

Vol ume 1 8 - 26

Special case: requesting data (service: SRD with 0 bytes of data to be

transmitted)

Sequence of the transmission

If the sender does not have data to transmit to the receiver, but only wants

to request data from the receiver, use the SRD service with 0 bytes of data

to send. T he terms "sender" and "receiver" are retained even if the "sender"

has no data to transmit, but only requests data.

The "receiver" transfers the requested data to the buffer using the "reply

update single (RPL_UPD_S)" service or the "reply update multiple

(RPL_UPD_M)" service. How the data are transferred to the buffer and

handled in the buffer has already been described above. The sequence is

illustrated schematically in Figs. 8.10 and 8.11 with the special feature that

in Fig. 8.11 there are no data to be transmitted with the SRD request (data

1 = 0) .

B8976060/02 Free Layer 2 Communication

8 - 27 Volume 1

8.2 Transmitting Multicast Messages by Direct Access

to L ayer 2 Se rvic es

If the transmitted data are intended for several stations simultaneously

(using layer 2 services) you must use the following procedure:

➣Program the same (local) SAP number (range 2..54) for each receiver

of the multicast message.

➣Create the (request) header for the block of data to be transmitted, as

follows:

The stati on address 7FH i s a global address for this application. Multi cast to

all stations is only possible when the same (local) SAP is set up for every

L2 station and this SAP is entered as the DSAP/RSAP in the request

header of the sender. Fig. 8.12 illustrates which stations receive an SDN

frame with DSAP/RSAP 10 and address 7FH.

Byte

DSAP/RSAP=no. of the SAP programmed

for each receiver

...........

rem_add_station = 7F (global address)

service_code =01 (SDN)

Free Layer 2 Communication B8976060/02

Vol ume 1 8 - 28

Another way of sending multicast messages to all stations is to use the

default SAP. This SAP which can be programmed with the Init editor of the

COM 5430 TF software package has the f ollowing function:

All receive messages with DSAP/RSAP information are automatically

assigned to the default SAP by the layer 2 firmware. To reach all stations

on the bus you must simply follow the procedure below:

➣Assign a default SAP (range: 2..54) to each station

➣Assign byte 2 (service_code) the value 01H (service: SDN)

➣Make sure that the sender generates a frame without DSAP/RSAP

information. To do this, enter the value FFH in byte 5 of the request

header (DSAP/RSAP)

and

➣Enter the value 7FH (global address) in byte 6 (rem_add_station) of the

request header

Station 2 Station 5 Station 3 Station 4 Station 1

SAP 12

SAP 10 SAP 10 SAP 10

SDN frame with DSAP/RSAP 10 and address 7F H

Fig . 8.12 S end ing M ult icast Mess ages with th e SDN Ser vice

B8976060/02 Free Layer 2 Communication

8 - 29 Volume 1

Fig. 8.13 illust rates how all the stations assigned a default SAP in the range

2..54 can receive a multicast frame.

☞COM 5430 TF/COM 5431 FMS automatically assigns the same

default SAP number to all CP 5430 TF/CP 5431 FMS stations.

Station 2 Station 3 Station 4 Station 1

SAP SAP

SAP

Default Default Default

SDN frame with DSAP/RSAP FF and address 7FH

Fig . 8.13 Receiving Multicast Messages using the Default SAP

Free Layer 2 Communication B8976060/02

Vol ume 1 8 - 30

8.3 Configuring

The software package COM 5430 TF/COM 5431 FMS is used under SINEC

NCM to configure free layer 2 communication.

The screens required for configuration are provided by SINEC NCM as

shown in Fig. 8.14:

➣Link edi tor

➣Documentation and test functions

Edit

Menu item

= Init Edit ...

SINEC NCM

Links->Free

Layer 2 Links

dealt with in separate chapters

Documentation and

Test in Chapter 14

Fig . 8.14 Free Layer 2 Configuration

B8976060/02 Free Layer 2 Communication

8 - 31 Volume 1

General procedure:

To implement a simple task (transferring data from PLC 1 to the remote

device via pre-programmed links with HDBs) the following procedure is

required:

➣The links between the PLC and remote device must be programmed

(as mentioned in the general guidelines). For planning the link, refer to

Characterist ics of the S5-S5 Link.

➣Assigning parameters to the CP module. This involves creating the

SYSID block (refer to Chapter 6)

➣Configuring the links between the PLC and the remote device.

➣Programming the CPUs of the PLCs i.e. HDBs, OBs, FBs and DBs and

creating the frames with service-specific headers (refer to Section 8.1)

according to the planned task. .

8.3.1 Configuring Free Layer 2 Lin ks

With the link editor of the COM 5430 TF/COM 5431 FMS software package

you assign parameters for the links between two stations on the bus.

These links are either stored in a submodule file (offline mode) or written

directly to the CP submodule or modified there (online mode).

This means that submodule files created offline can also be loaded on the

CP or that the contents of the CP submodule can be saved in a file.

Free Layer 2 Communication B8976060/02

Vol ume 1 8 - 32

Select Edit -> Links -> Free layer 2 Links to call the following screen. The

screen is structured as follows:

Output fields

L2 station

address: L2 address you are currently working with

Input fi elds

PRIO (H/L): Specifies the priority of the jobs. The default is "LOW".

(Possible entries: : "LOW" , " HIGH").

Parameters

sending/receiving: Send or receive parameters are entered here.

SSAP: Local Service Access Point (range of values: 2 - 54,

56).

Link Editor Free Layer 2 Links

Local L2 station address:

PRIO (H/L) :

SSAP :

Parameters sending/receiving:

SSNR :

ANR :

+1 -1 INPUT DELETE OK SELECT

CP type:

Source: (EXIT)

HELP

Fig . 8.15 Layer 2 Link Configuration Screen

B8976060/02 Free Layer 2 Communication

8 - 33 Volume 1

SSNR: Interface number corresponding to the PLC DPR page

number and therefore forming the CPU-CP interface.

The interface number must be uniform for all jobs via a

link. It can therefore only be entered in the first field and

is automatically repeated for further parallel services

(range of values: 0..3).

ANR: Job number via which the job is triggered. (Range of

values: 134 .. 186)

Functi on keys

+1 Page forwards through the links for several free layer 2

links

-1 Page backwards through the links for several free layer

2 link s

INPUT Prepare next input.

DELETE Delete the input link.

OK Enter the data in the link block.

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select entries from the list with the cursor keys and

enter them in the field with the return key.

Free Layer 2 Communication B8976060/02

Vol ume 1 8 - 34

8.4 Example of a Layer 2 Link

This section describes how two stations can be configured with COM 5430

TF/COM 5431 FMS to be able to exchange data via direct acc ess to layer 2

services.

You should have worked through Chapters 3 to 6 of this manual and be

familiar with the handling blocks and STEP 5.

Hardware and software requirements

The following hardware is necessary:

➣Two SIMATIC S5 programmable controllers (PLC 1: S5-155U and

PLC 2: S5-115U)

➣One CP 5430 TF or CP 5431 FMS per PLC

➣One RAM submodule per CP 5430 TF or CP 5431 FMS

➣One RS 485 bus terminal per CP

➣SINEC L2 bus cable

➣At least one PG 710, PG 730, PG 750 or PG 770,

or PC

The following software packages are also required:

➣COM 5430 TF or COM 5431 FMS under SINE C NCM

➣PG software for STEP 5 programming

➣Appropriate handling blocks for the PLCs

➣Diskette with the example programs.

B8976060/02 Free Layer 2 Communication

8 - 35 Volume 1

8.4.1 Program Description

Two SIMATIC programmable controllers with the L2 addresses 1 and 2 are

to exchange data via the SINEC L2 bus. The transmitted and received data

will be written to data blocks (DB).

Station 1, an S5 155U PLC, uses SAP 2 as the service access point. For

station 2, an S5 115U PLC, SAP 3 has been selected.

The data exchange uses an SRD service on station 1 and an RPL_UPD_S

service on station 2.

. .

interface

Bus cable

Bus terminal 1

with terminal cable Bus terminal 2

with terminal cable

PLC1 (S5-155U) PLC2 (S5-115U)

interface

(AS511)

interface

(AS511)

Terminator

activated

PG-

inter-

face

(AS511)

Fig . 8.16 Sy ste m Structure with all Hardware Co mp onents

Free Layer 2 Communication B8976060/02

Vol ume 1 8 - 36

8.4.1.1 Program for PLC 1

During the PLC start up, the CP interface is synchronized with the

SYNCHRON handling block.

Four data words will be sent from PLC 1 to PLC 2. At the same time, four

data words will be requested from PLC 2 (SRD). PLC 2 transfers the

requested data to a buffer using an RPL_UPD_S job.

The data (request) are transmitted with the SEND HDB, the receive data

and "acknowledgments" (confirmations/indication) are received with the

RECEIVE HDB.

To be able to monitor the data exchange, you must evaluate the status

word for this job continuously. The status word contains information about

the status of the job, information about data management and error codes.

8.4.1.2 Program for PLC 2

PLC 2 receives 4 data words. At the same time, 4 data words are

requested by PLC 1 and are transmitted or transferred to the buffer

(RPL_UPD_S).

B8976060/02 Free Layer 2 Communication

8 - 37 Volume 1

8.4.2 Transferring the Configuration Data for the CP 5430 TF/CP

5431 FMS and the STEP 5 User Program

To be able to implement the practical example for free layer 2

communication, follow the procedure outlined below (and refer to Chapter

16):

➣Transfer the following COM 5430 TF/COM 5431 FMS database files to

the CPs you are using:

When using the CP 5430 TF under the network file LAY2ONCM.NET

– f or station 1 OLAY2T1.155

– f or station 2 OLAY2T2.115

When using the CP 5431 FMS under the network file LAY2QNCM.NET

– f or station 1 QLAY2T1.155

– f or station 2 QLAY2T2.115

➣Transfer the following STEP 5 files to the programmable controllers you

are using:

– For P LC 1 (S5-155U) the file LAY2T1ST.S5D

– For P LC 2 (S5-115U) the file LAY2T2ST.S5D.❑

Free Layer 2 Communication B8976060/02

Vol ume 1 8 - 38

9 Data Transmission with Global I/Os

This chapter explains the followi ng:

➣The applications for which data transmission with global I/Os is suitable.

➣How this type of data transmission functions.

➣How to assign parameters for the CP 5430 TF/CP 5431 FMS for this

type of transmission when programmable controllers exchange data via

the global I/Os (GP).

➣How to use this type of data transmission based on an example

incl uding a STEP 5 program (example in Section 9.3).

Areas of app lication:

Communication with global I/Os is only allowed via the base interface

number base SSNR!

Data transmission with global I/Os (I/O interface) is suitable for

communication between SIMATIC PLCs.

Data transmission with global I/Os is suitable for the transmission of single

bytes using high priority broadcast frames between active SIMATIC S5

programmable controllers. Data with the following characteristics may be

considered for this type of communication.

➣Small volumes of data

➣Time-critical data

➣Data which does not change constantly

This, for example, might include control commands, messages, measured

values and analog values.

B8976060/02 Communication with Global I/Os

9 - 1 Volume 1

An important characteristic of the global I/Os is that changes in the data

bytes are recognized and only these changes transmitted. The changed

data bytes are then transmitted more quickly compared with data

transmission using HDBs (refer to Chapter 7).

The term "global I/Os" means that part of the I/O area is not used by I/O

modules but for global data exchange between SIMATIC PLCs. Global data

exchange involves the CP sending the entire changed output area assigned

to the GP and updating the entire input area assigned to the GP with the

received data once again cyclically. You can use these I/Os as normal

inputs and outputs. The address areas are processed with STEP 5

operations.

The mode can either be synchronized with the cycle or free. With the

cycle-synchronized mode, an HDB must be called at the checkpoints

required by the user to ensure the consistency of inputs and outputs.

Ideally with the global I/Os, you should transmit data which change rarely

relative to the target rotation time (the rate of change should be a multiple

of the target rotation time). If, however, the data bytes to be transmitted

change constantly (compared with the target rotation time), the advantage

of minimum bus load, the mai n characteristic of GP, is lost.

☞Simul taneous use of GP and DP is not possi ble.

Communication with Global I/Os B8976060/01

Volume 1 9 - 2

9.1 Basics of Data Transmission with Global I/Os

This section describes the funct ions of the global I/Os from the point of view

of the CPU control program.

➣Data exchange via I/Os

➣How the data transmission functions

➣Updating the I/Os with GP

In data transmission with global I/Os the data exchange takes place using

the I/Os of the SIMATIC PLC, as follows:

➣The data for transmission are assigned to the output area of the I/Os in

the control program.

➣The received data are stored in the input area of the I/Os.

➣Transmitted and received data can be processed with STEP 5

operations.

The term "global I/Os" conveys the fact that part of the I/O area of a

programmable controller is not assigned "locally" to the corresponding input

and output modules but is "globally" available to all programmable

controllers on t he L2 bus .

➣Data for transmission via the output area

➣Received data via the input area

All I/O bytes via which you want to transmit and all I/O bytes via which you

want to receive must be designated as I/Os. To do this, you reserve I/O

areas of each station taking part in the GP communication for GP using the

COM.

B8976060/02 Communication with Global I/Os

9 - 3 Volume 1

➣Each output I/O byte via which you want to transmit must be assigned

to a "global object" (GO). A GO is a global I/O byte (GPB).

➣The GOs are numbered.

➣Each input I/O byte via which you want to receive, must also be

assigned to a GO.

A GO always consists of the following:

➣One I/O output byt e for one sender and

➣One or more I/O input bytes for the receivers

The way in which areas are reserved for the GP and how I/O bytes are

assigned to gl obal objects is described in Section 9.2.

➣Configuring I/O areas for GP

The GP frames automatically have the priority "high" for the CP 5430 TF/CP

5431 FMS; i.e. the CP 5430 TF/CP 5431 FMS gives priority to a GP frame.

Functions:

By configuring with the GP station editor, the CP becomes the "distributor".

Transmission on the CP:

➣The output data of the PLC are read out.

➣All values changed since the last time the output data were read out are

detected.

➣All changed values including object information is packed into change

frames.

➣The frame is transmitted as a broadcast to all GP stations.

Communication with Global I/Os B8976060/01

Volume 1 9 - 4

Receiving: on the CP

➣A frame containing changes is received.

➣Locally conf igured obj ects are fi ltered out of t he frame.

➣All the filtered values are entered in the input area of the PLC.

Fig. 9.1 is a schematic representation of transmission and reception using

the "global I/Os area". A byte to be transmitted from station 1 is written to

output byte 7 (PY 7). The global I /Os byte 10 (GPB 10) i s assigned to PY 7.

The transmitted byte is received at station 2 as input byte 1 (PY 1) because

PY 1 is assigned to GPB 10 i n this station.

PY 7 of station 1 is therefore in a sense directly "wired" to PY 1 of station 2

via GPB 10.

Each station which assigns GPB 10 to an input byte as shown in the

previous example is also the receiver of this byte.

CPU1 PY7 CPU2

PY1

CP 5430 TFCP 5430 TF

PY7=>GPB10 GPB10=>PY1

Station 1 Station 2

GPB10

L2 bus cable

011010110 011010110

CP 5431 FMS CP 5431 FMS

Fig . 9.1: Tra nsm itti ng an d Re ceivi ng U sing t he Gl obal I /O A rea

B8976060/02 Communication with Global I/Os

9 - 5 Volume 1

Updat ing the input and output bytes of the gl obal I/O s

The times at which the CP 5430 TF/CP 5431 FMS updates the GP bytes

to be t ransmitted are either

➣FREE mode: decided by the CP (the STEP 5 control program has no

influence) or

➣CYCLE-SYNCHRONIZED mode: decided by the control program using

a send handling block call with job number 210.

The times at which the CP 5430 TF/CP 5431 FMS transfers the received

GP b ytes t o the CPU input area are also either

➣FREE mode: decided by the CP (or influenced by the STEP 5 control

program) or

➣CYCLE-SYNCHRONIZED mode: decided by the control program using

a RECEIVE handling block call with job number 211.

Consi stency of the input and outpu t bytes of th e G P

➣FREE mode: guaranteed consi stency of one byte.

➣CYCLE-SYNCHRONIZED mode: guaranteed consistency over the

whole ar ea.

Special features

➣CYCLE-SYNCHRONIZED mode: when a GP station fails, the input

bytes assigned to this station are reset on the other stations (to the

value 0). Notes on the calculation of this "switch off time" can be found

in the appendix of this manual.

If the PLC changes from the RUN to the STOP mode, its GP output bytes

are reset (to the value 0). Since the CP 5430 TF/CP 5431 FMS registers

this change, each of these bytes which previously had a value other than

"0" is transmitted with the value "0".

Communication with Global I/Os B8976060/01

Volume 1 9 - 6

The FREE and CYCLE-SYNCHRONIZED modes are now explained in

more detail.

Send GP (free)

Expla nation of Fig . 9.2:

In the free mode, there is no synchronization with the PLC cycle. The

consistency of the I/Os can therefore only be guaranteed for one byte. The

time at which the output byte is evaluated (i.e. the new/old comparison) is

determined solely by the CP (e.g. after sending the previous GP frame). In

the free mode, a cycle overflow of the PLC cannot be detected. A cycle

overflow means that the data of a PY were updated at least twice by the

control program before the GP was able to perform a "new/old" comparison.

PLC

program

execution

GPB I/O

area in

CP-DPR

PY7 GPB10 to the BUS

GPB

that transmits

100

5 5

100

Comparison

Internal

cycle

Internal

cycle

Internal

cycle

* not transferred, skipped

by internal cycle

???

??? undefined status

Fig . 9.2: How the Mod e Transmit FREE F unction s

B8976060/02 Communication with Global I/Os

9 - 7 Volume 1

In the PLC program, the control program changes the output byte to be

transmitted (PY 7).

In the CP cycle, the CP checks all (GP) output bytes for changes (new/old

comparison) and transmits only the GP bytes whose values have changed

since the last comparison.

Result: the CP 5430 TF/CP 5431 FMS only sends a GP byte when its

value has changed bet ween two consecutiv e "new/old" compari sons.

The value of the GP byte at the time of the new/old comparison is decisive.

If, in the meantime, a bit has changed its value more than once, but has

returned to its original value when the next comparison is made, these

changes are not recognized. Information about calculating the "reaction

times" of the global I/Os in t he FREE mode can be found in the appendix of

this manual.

Communication with Global I/Os B8976060/01

Volume 1 9 - 8

Receive GP in the free mode

Expla nation of Fig . 9.3:

When a frame containing changes is received, the data are entered in the

DPR independently of the PLC cycle. This means that the consistency of

the received data, just as with sending, can only be guaranteed for one

byte. In the free mode, a cycle overflow cannot be detected by the bus. A

cycle overflow means that the data of a PY from the bus were updated at

least twice before the control program was able to evaluate the PY data.

PLC

program

execution

GPB I/O

area in

CP-DPR

PY1 GPB10

from BUS

GPB

that receives

30 30

???

Bus

cycle

Bus

cycle

Bus

cycle

40 40

??? undefinined status

Fig . 9.3: Ho w the Mod e Rece ive FREE Fu nctions

B8976060/02 Communication with Global I/Os

9 - 9 Volume 1

➣In the bus cycle, GP bytes are only received when the data have

changed on the sender.

➣In the PLC, the control program evaluates the received input byte

(PY 1).

The value of the GP byte at the time the control program accesses it in the

PLC is decisive. If data is received several times between two accesses by

the PLC, only the current value is passed on to the control program. All

intermediate values are lost.

Essential features of the FREE mode:

➣Minimum cycle load (corresponds to the cycle load that would occur

simply by pluggi ng in the corresponding input/output modules.

➣Minimum load on the CP 5430 TF/CP 5431 FMS.

➣Simple programming (single handling block call; HDB SYNCHRON

during start -up).

☞If GP bytes need to be transferred together because they form

a logical unit (e.g. a control parameter requiring a word), the

FREE update mode must under no circumstances be

selected. With this mode, there is no guarantee that the GP

bytes which belong together are actually transferred together.

The receiver would then process in consistent values.

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 10

Transmit GP cycle-synchronized

Expla nation of Fig . 9.4:

In the cycle-synchronized mode, the consistency of the I/O bytes of a PLC

cycle is guaranteed. The output byte is only transferred to the CP at the

cycle checkpoint (HDB execution) of the PLC. The cycle checkpoint must

be made known to the CP by a handl ing block.

PLC

program

execution

GPB I/O

area in

CP-DPR

PY7 GPB10 to the BUS

GPB

that transmits

???

100

HDB execution

100

PLC

cycle

PLC

cycle Comparison

Comparison

??? undefined status

Fig . 9.4: How the Mode Transmit CYCLE-SYNCHRONIZED Functions

B8976060/02 Communication with Global I/Os

9 - 11 Volume 1

➣The PLC control program changes the output byte to be transmitted

(PY 7).

➣At the point when the HDB is executed, the CP 5430 TF/CP 5431 FMS

rechecks all the (GP) output bytes for changes (new/old comparison)

and only transmits the GP bytes which have changed since the last

"new/ old" compari son.

Result: the CP 5430 TF/CP 5431 FMS only transmits a GP byte in the

cycle-synchronized mode, when its value has changed between two

consecutive new/old comparisons.

The value of the GP byte at the time of the new/old comparison which you

decide in the control program (by means of an HDB send call with job

number 210) is decisive. If a byte changes its value several times but has

returned to its original value at the time of the "new/old" comparison, these

changes are not detected.

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 12

Receive GP (cycle-synchronized)

Expla nation of Fig . 9.5:

The consistent acceptance of the input byte by the CP takes place at the

cycle checkpoint. The cycle c heckpoi nt must be made known t o the CP wit h

a handling block.

➣At the point when the HDB is executed, all changed PYs are entered in

the DPR by the CP. Once the HDB has been executed, the PLC can

access this current data of the PY.

PLC

program

execution

GPB I/O

area in

CP-DPR

PY1 GPB10 from BUS

GPB

that receives

???

HDb execution

HDB execution

PLC

cycle

PLC

cycle

40 *

60 *

Bus

cycle

Bus

cycle

Bus

cycle

* cycle overrun is entered in the station list

??? undefined status

Fig . 9.5: How the Mode Receive CYCLE-SYNCHRONIZED Function s

B8976060/02 Communication with Global I/Os

9 - 13 Volume 1

➣The PLC control program accepts the received input byte (PY 1).

The value of the GP byte at the time of the HDB execution (HDB receive

call with job number 211) is decisive. If a GP byte has changed its value

several times between two HDB executions, the current value is accepted.

This cycle overflow is indicated in the GP station list by the bus.

☞With short PLC cycle times (< 50 ms) the HDB

SEND/RECEIVE calls with job numbers 210/211 may extend

the PLC cycle time. The load on the CP 5430 TF/CP 5431 FMS

may also increase so that the transmission times of the

global I/Os deteriorate. If you have short PLC cycle times,

make sure that the time between two HDB calls is greater

than 50 ms (e.g. by programming HDB SEND/RECEIVE calls

with job numbers 210/211 in every nth PLC cycle).

Sequence of the data transmission

The start-up OBs have the following task with the global I/Os data

transmission mode;

➣They must synchronize the CP 5430 TF/CP 5431 FMS interface.

➣They can make sure that the PLC only starts up when certain or all

stations are ready to transmit and receive (i.e. when there are no GP

error messages).

➣If you have selected the CYCLE-SYNCHRONIZED update mode, the

complete GP should be received at the end of a start-up OB.

The SEND synchronization point is indicated by the SEND-HDB (ANR 210).

The parameter QTYP must be assigned the value "NN". DBNR, QANF,

QLAE are irrelevant. The ANZW should be assigned to a data or flag word.

The RECEIVE synchronization point is indicated by the RECEIVE HDB

(ANR 211). The remaining assignment of parameters to the HDBs is the

same as for the SEND synchronization point.

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 14

The following figure (Fig. 9.6) illustrates one way of integrating the HDBs in

the cold or warm restart branch of the PLC.

Both in the cold restart branch (OB 20) and in the warm restart branch

(OB 21/22) each CP interface to be used later must be synchronized

(SYNCHRON HDB). From the cold restart branch, the PLC operating

system branches directly to the first cycle checkpoint. The process image of

the inputs (PII) is read in for the first time at this point. The first RECEIVE

synchronization point for t he CP 5430 TF/CP 5431 FMS is therefore already

in the cold rest art branch. At this point (i.e. at the end of OB 20) the CP can

also be monitored to check that the GP image is complete. For this

purpose, the CONTROL HDB can be integrated and called in a loop

repeatedly until the CP no longer signals an error in the GP image using

the control status word.

(OB 20, OB21, OB 22)

With this HDB call (job number

201), the station list is read in

by the CP 5430 TF/CP 5431 FMS.

The station list contains the

statuses of the CPs of all active

stations on the bus from which

input GP is expected.

HDB SYNCHRON call for the SSNR

of the CP 5430 TF/CP 5431 FMS

yes

GP of

stations

1and 2 ok?

end

Synchronization of the interface

PLC-CP 5430 TF/CP 5431 FMS

Evaluation of the station list

i.e. interrogation of the statuses

which should have started up

(here, stations 1 and 2).

HDB RECEIVE call with

ANR 211

HDB RECEIVE call with

ANR 201

Fig . 9.6: HDBs in the Cold or Warm Restart Branch of the PLC

B8976060/02 Communication with Global I/Os

9 - 15 Volume 1

Cyclic operation

The cyclic program has the following structure for all stations in the CYCLE

SYNCHRONIZED update mode:

In cyclic operation, the SEND synchronization point is immediately at the

start of OB 1; the RECEIVE synchronization point at the end of the PLC

cycle. The division into a SEND and a RECEIVE synchronization point is

necessary, since the CP must make the received GP bytes available to the

PLC before the PLC cycle control point and on the other hand the CP can

only process the GP output byte after output of the PIQ.

If one of the SIMATIC S5 PLCs fails, the switch off safety strategy for I/O

signals is used for the "global I/Os". If a PLC stops, all outputs and

therefore all GP output bytes sent by this PLC are set to zero. This means

that these GP bytes are automatically sent to all other receiving stations.

The failure of a complete station (e.g. caused by a power failure) can be

detected by the CP 5430 TF/CP 5431 FMS usi ng ANR 201.

Control program

Cycle

checkpoint HDB RECEIVE call with

ANR 211

(last statement in cyclic

program before the end

of the block)

Call HDB SEND with

ANR 210

(at the start of the cyclic

program)

Fig . 9.7: Struct ure of the Cyclic Program fo r all Stations

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 16

Possibilities of error detection

➣Group error message in ANZW (RECEIVE ANR 210)

➣Reading the station list (ANR 201).

Error statuses within the bus system including GP processing are written to

the station list. Using a cyclic CONTROL call and a RECEIVE handling

block call, the user program can read out the station list. In the status byte

for GP processing (ANR = 210) an error which occurs in the GP processing

is indicated as a "group error message" so that the station list must only be

read out in case of an error. If the cycle-synchronized processing mode is

set, "cycle overflow" is also entered in the station list. A cycle overflow can

occur when changes in the GP output bytes cannot be transmitted owing to

a lack of bus capacity (PLC cycle is faster than the bus token cycle). The

failure of a GP transmitter i s also indicated in the station list. The st ation list

can be read out with ANR 201 using the RECEIVE block.

B8976060/02 Communication with Global I/Os

9 - 17 Volume 1

9.1.1 Checking the Data Transmission with ANZW and the

GP Sta tion List

Structure of the status word with HDB SEND (ANR 210) and RECEIVE

(ANR 211):

Bits 8... 11 (error bits) are group error messages; more detailed information

about the errors that have occurred in GP processing can be obtained from

the GP station list.

Not

used Error

bits Data

mgment. Status

bits

15 1413 12 11 10 9 8 7 6 5 4 3 2 1 0

Job complete with error*

(e.g. invalid job number)

Job complete without error

SEND synchronization disabled

RECEIVE synchronization possible

Synchronization done without error

(Input GP was received)

* Bit 3 of the status bits is not connected with the error bits (8..11).

When bit 3 is set, the error is not specified by the error bits. All the errors

listed in table 7.3 are possible.

Fig . 9.8: Struct ure of the Status Word, h ere: Status Bits

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 18

☞If there is a group error message, bit 3 of the error status

word is not set!

If a station has failed, the corresponding GP input I/O bytes

on the other stations are automatically reset by the CP 5430

TF/CP 5431 FMS (to value 0). This also appl ies to the start-up!

Bit 11 10 9 8 of the status word

Transmission delay in the other station, i.e. the

PLC cycle was faster than the transfer capacity

of the L2 bus (transmitted data of the remote

station could not be fetched quickly enough

by the L2 bus).

Reception delay in the local PLC, i.e. the transfer

capacity of the L2 bus was faster than the PLC

cycle (while the received data was being evaluated

in the local PLC, the L2 bus had supplied new data

data which could no longer be evaluated).

At least one remote station is in the STOP status

GP image is incomplete

(either not all stations have started up

at least one station has dropped out)

Reserved for ZP error message

Fig . 9.9: Meani ng of the Error Bit s in the Statu s Word

B8976060/02 Communication with Global I/Os

9 - 19 Volume 1

Evaluation of the GP station list (HDB RECEIVE with ANR 201)

Each CP 5430 TF/CP 5431 FMS which receives global I/Os manages an

internal GP station list. This has a length of 32 bytes.

Each of these 32 bytes provide information about the operating statuses of

all active L2 stations (maximum 32 stations) connected via global objects to

the stations which evaluate the station list.

Table 9.1 illustrates the structure of the GP station list, Fig. 9.10 the

structure of a status byte. You can read the GP station list with the HDB

RECEIVE (ANR 201).

You can only evaluate the station list when HDB RECEIVE (with ANR 201)

was executed without an error.

If no GP input byte was defined, the value "AH" is entered in the status bit

of the status word for this job.

Byte no Status byte f rom stations

0 stat us byte station 1 (L2 station address 1)

1 stat us byte station 2 (L2 station address 2)

...

31 status byte station 32 (L2 station address 32)

Table 9.1: Structure of the GP Station List

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 20

Fig. 9.10 takes this difference into account in the explanation of the

individual bits of the status byte:

A further distinction must be made as to the mode (FREE or

CYCLE-SYNCHRONIZED) in which the station list is eval uated, as follows:

➣FREE:

the stati on list is updated continuously by the CP.

Bit 01234567

0=no

1=yes

Status byte of the local station:

The complete expected GP is OK

Status byte of the remote station:

Input GP expected from this station

is ok

Station expects input GP from

other stations

Input GP expected from this station

All remote stations are in RUN status

The PLC of the remote station is in RUN status

send/receive delay* in at least

one remote station

send/receive delay* in at least

one GO of the remote station

*With send/receive delay, GOs have changed more often than they could be

sent or received (intermediate values can be lost)

Status byte of the local station:

Status byte of the remote station:

Status byte of the local station:

Status byte of the remote station:

Status byte of the local station:

Status byte of the remote station:

Fig . 9.10 : Stru cture of a Sta tus Byte in th e Station List

B8976060/02 Communication with Global I/Os

9 - 21 Volume 1

➣CYCLE-SYNCHRONIZED:

the station list is updated by the CP at the point when the HDB

RECEIVE with job number 211 is called in the control program (GP

receive).

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 22

9.2 Configuring

The PG package SINEC NCM with COM 5430 TF/COM 5431 FMS is used

to configure the functions.

The screens you require for programming are provided by SINEC NCM as

shown in Fig. 9.11.

➣I/O areas

➣GP ed i tor

➣Documentation and test

➣GP consistency

= Init Edit ...

SINEC NCM

Basic initialization screen

I/O areas

I/Os -> I/O Areas

Edit -> I/Os

Pull-down menu item

Basic initialization screen

GP station

I/Os -> GP Station Editor

dealt with in separate chapters.

Documentation and

Test in Chapter 14

Menu item Network

GP consistency

in Section 6

Fig . 9.11 : GP Configuration

B8976060/02 Communication with Global I/Os

9 - 23 Volume 1

9.2.1 I/O Areas CP 5430 TF

The assignment of input and output areas in the SIMATIC PLC is made for

the global I/Os in a screen.

If you specify areas for ZP at the same time, you require only three limits

for the input and output areas since one limit is always implicit ly specif ied.

☞Simul taneous use of GP and DP is not possi ble.

Select Edit -> I /Os -> I/O Areas to call the f ollowing screen. T he screen has

the following structure:

Input/Output (I/O) Areas:

L2 station address:

OUTPUT AREAS:

INPUT AREAS:

GP update:

Stations from which global I/Os are expected:

OK SELECT

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

1 2 3 4 5 6 7 9 10 11 12 13 14 15 168

ZP/DP STA: GP STA: GP END: ZP/DP END:

CP type:

Source: (EXIT)

HELP

ZP/DP update:

Fig . 9.12 : Sc reen for Assigning I nput/Outp ut Areas CP 5430 TF

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 24

Input fi elds :

GP senders: All the stations from which GP bytes are expected must

be marked with "X".

Recommendation: only enter an X for the stations

from which GP data are expected, otherwise the bus

load is increased.

Update: Cycle-synchronized: update at the cycle checkpoint by

the HDB.

Free: implicit update of the I/O areas by the CP.

Input areas

GP STA: Begi nning of the (continuous) input area for the GP.

(Range of values PY 0 .. 254, OY 0 .. 254)

GP END: End of the (continuous) input area for the GP.

(Range of values PY 1 .. 255, OY 1 .. 255)

Output areas

GP STA: Begi nning of the (continuous) output area for the GP.

(Range of values PY 0 .. 254, OY 0 .. 254)

GP END: End of the (continuous) output area for the GP.

(Range of values PY 1 .. 255, OY 1 .. 255)

Output fields:

L2 station

address: The address of the currently addressed station is

displayed.

B8976060/02 Communication with Global I/Os

9 - 25 Volume 1

Functi on keys:

OK The "OK" key enters the data. If the module file does

not yet exist, it is set up when you confirm the entries.

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select values from the list with the cursor keys and

enter them in the field with the return key.

☞The input or output area must al ways begin with an even byte

number and must always end wit h an odd byte number.

The fields remain empty if no input or output areas are required for the GP.

If you make errors in the entries, these are rejected by the COM. After you

press the OK key, an error message appears in the message line.

If you want to reserve areas for the cyclic I/Os (ZP), remember the followi ng

when you are reser ving areas:

➣The area for the "global I/Os" (i.e. the area shared by all stations

invol ved) can be a maximum of 2048 bytes long (GPB0 to GPB2047).

➣Per station, a maximum of 64 bytes can be used as output GPs. These

64 output bytes must be a continuous block in the P or O extended

input and output area.

➣Per station, a maximum of 256 bytes can be used as input GPs. These

bytes can also only be located as a continuous block in the P or O

extended input and output area.

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 26

➣GP and ZP/ DP input areas must not overlap.

➣GP and ZP/ DP output areas must not overlap.

➣The reserved input area for GP and ZP/DP must not include gaps.

➣The reserved output area for GP and ZP/DP must not include gaps.

➣The input area per station for GP and ZP/DP together must not exceed

a maximum of 256 bytes.

➣The output area per station for GP and ZP/DP together must not

exceed a maximum of 256 bytes, of which a maximum of 64 bytes are

reserved for GP.

Input and output I/O areas can be selected independent of each ot her (refer

to Fig. 9.12). They can be shifted "up" or "down".

☞The I/O area reserved for the GP and ZP/DP must not be used

by othe r I/O modu les.

An online modification of the GP or ZP/DP area only becomes

effective after the CP 5430 TF has gone through power

off /power on.

B8976060/02 Communication with Global I/Os

9 - 27 Volume 1

9.2.2 I/O Areas CP 5431 FMS

The assignment of input and output areas in the SIMATIC PLC is made for

the global I/Os in a screen.

If you specify areas for ZI at the same time, you require only require three

limits for the input and output areas since one limit is always implicitly

specified.

☞Simul taneous use of GP and DP is not possi ble.

Select Edit -> I/Os -> I/O areas to call the following screen. The screen has

the following structure:

Input/Output (I/O) Areas:

L2 station address:

OUTPUT AREAS:

INPUT AREAS:

GP update:

Stations from which global I/Os are expected:

OK SELECT

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

1 2 3 4 5 67 9101112 131415168

CI/DP STA: GP STA: GP END: CI/DP END:

CP type:

Source: (EXIT)

HELP

DP update:

Fig . 9.13 Screen for Assignning Input/Output Areas CP 5431 FMS

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 28

Input fi elds :

GP senders: All the stations from which GP bytes are expected must

be marked with "X".

Recommendation: only enter an X for the stations

from which GP data are expected, otherwise the bus

load is increased.

Update: Cycle-synchronized: update at the cycle checkpoint by

the HDB.

Free: implicit update of the I/O areas by the CP.

Input areas

GP STA: Begi nning of the (continuous) input area for the GP.

(Range of values PY 0 .. 254, OY 0 .. 254)

GP END: End of the (continuous) input area for the GP.

(Range of values PY 1 .. 255, OY 1 .. 255)

Output areas

GP STA: Begi nning of the (continuous) output area for the GP.

(Range of values PY 0 .. 254, OY 0 .. 254)

GP END: End of the (continuous) output area for the GP.

(Range of values PY 1 .. 255, OY 1 .. 255)

Output fields:

L2 station

address: The address of the currently addressed station is

displayed.

B8976060/02 Communication with Global I/Os

9 - 29 Volume 1

Functi on keys:

OK The "OK" key enters the data. If the module file does

not yet exist, it is set up when you confirm the entries.

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select values from the list with the cursor keys and

enter them in the field with the return key.

☞The input or output area must al ways begin with an even byte

number and must always end wit h an odd byte number.

The fields remain empty if no input or output areas are required for the GP.

If you make errors in the entries, these are rejected by the COM. After you

press the OK key, an error message appears in the message line.

If you want to reserve areas for the cyclic interface (ZI), remember the

following when you are res erving areas :

➣The area for the "global I/Os" (i.e. the area shared by all stations

invol ved) can be a maximum of 2048 bytes long (GPB0 to GPB2047).

➣Per station, a maximum of 64 bytes can be used as output GPs. These

64 output bytes must be a continuous block in the P or O extended

input and output area.

➣Per station, a maximum of 256 bytes can be used as input GPs. These

bytes can also only be located as a continuous block in the P or O

extended input and output area.

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 30

➣GP and ZI/DP input areas must not overlap.

➣GP and ZI/DP output areas must not overlap.

➣The reserved input area for GP and ZI /DP must not include gaps.

➣The reserved output area for GP and ZI/DP must not include gaps.

➣The input area per station for GP and ZI/DP together must not exceed a

maximum of 256 bytes.

➣The output area per station for GP and ZI/DP together must not exceed

a maximum of 256 bytes, of which a m aximum of 64 bytes are reserved

for GP.

Input and output I/O areas can be selected independent of each ot her (refer

to Fig. 9.13). They can be shifted "up" or "down".

☞The I/O area reserved for the GP and ZI/DP must not be used

by othe r I/O modu les.

An online modification of the GP or ZI/DP area only becomes

effective after the CP 5431 FMS has gone through power

off /power on.

B8976060/02 Communication with Global I/Os

9 - 31 Volume 1

9.2. 3 E ditor for Gl obal I/O s

Once you have reserved the input/output areas for the global I/Os, you must

assign the individual inputs and outputs of the stations to objects of the

global I/Os (abbreviation GO) using the GP editor. These GOs are global

I/O bytes (GPB).

Select Edit -> I/Os -> GP station editor to call the following screen. The

screen has the following structure:

GP Editor (station-oriented)

L2 station address:

Output area: Input area:

from to from to

8 SELECT

Output GO Symbol GO Input

DELETE

INSERT

Q <-> I

CP type:

Source:

Fig . 9.14 : Sc reen for GP Editor

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 32

Output fields:

L2 station address: The address of the currently addressed station is

displayed.

Input/output

area: Here, the I/O area is displayed in which the variables to

be programmed will be simulated.

From: the first byte of the block in the I/O area

To: the last byte of the block in the I/O area

(Range of values: area programmed in the I /O area.)

Input fi elds :

Output: Output byte to be transmitted. (Range of values PY 0 ..

254, OY 0 .. 254).

GO: Global object or "global I/O byte" (GPB). (Range of

values 0 .. 2047).

Symbol: Symbolic ID of the GO (Range of values 8 ASCII

characters ).

Input: Input byte to be read in. (Range of values PY 0 .. 254,

OY 0 .. 254).

Functi on keys:

Q<->I Change between inputs and outputs.

INSERT An empty line is inserted at the current cursor position.

DELETE Deletes the line marked by the cursor in the input or

output area.

OK The "OK" key enters the data. If the module file does

not yet exist, it is set up when you confirm the entries.

B8976060/02 Communication with Global I/Os

9 - 33 Volume 1

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select values from the list with the cursor keys and

enter them in the field with the return key.

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 34

9.3 Example of Data Transfer with Communication

using Global I/Os

The following example describes an application with cycle-synchronized

global I/Os.

Hardware and software requirements

The following hardware is necessary:

➣Three SIMATI C S5 pr ogrammable cont rollers ( PLC 1: S5-155U and

PLC 2: S5-115U and PLC 3: S5-135U)

➣One CP 5430 TF/CP 5431 FMS per PLC

➣One RAM submodule per CP 5430 TF/CP 5431 FMS

➣One RS 485 bus terminal per CP

➣SINEC L2 bus cable

➣At least one PG 710, PG 730, PG 750 or PG 770,

or PC

B8976060/02 Communication with Global I/Os

9 - 35 Volume 1

The following software packages are also required:

➣COM 5430 TF/COM 5431 FMS under SINEC NCM

➣PG software for STEP 5 programming

➣Appropriate handling blocks for the PLCs

➣Diskette with the example program.

9.3.1 Program Description

Three programmable controllers (S5-155U, S5-115U and S5-135U) of a

manufacturing unit are to be connected via the SINEC L2 bus (-> Fig. 9.14).

Station 1

S5-155U

with CPU 946/947 S5-115U

with CPU 944 S5-135U

with CPU 928

L2 bus cable

Station 2 Station 3

Fig . 9.15 : Ex ampl e o f Glob al I/ Os (Sy st em Con fig ura tion)

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 36

The distribution of the tasks is as follows:

PLC Bus station

number Task

S5-155U 1 "head control"

- Sends program selecti on number and control

commands for both manufacturing subunits 1

and 2 ( bus stations 1 and 2)

- Receives acknowledgement and position

messages from the manufacturing subunits

S5-115U 2 "manufacturing subunit 1"

- Acknowledges the control commands received

from the head control

- Signals positions and faults to the head

control

- Signals faults to manufacturing subunit 2

S5-135U 3 "manufacturing subunit 2"

- Acknowledges the control command received

from the head control

- Signals positions and faults to the head

control

- Signals faults to manufacturing subunit 1

Table 9.2: Distribution of Tasks in the "Manufacturing Unit" Example

B8976060/02 Communication with Global I/Os

9 - 37 Volume 1

The following specification of the transmitted and received data includes the

assignment of the I/O bytes (PY) to the global I/O bytes (GB).

Bus

stn.

no.

Input/output bytes used for data

transmission Assignment: input and

output words to

global I/Os

PY 2 -Sen d t he control comm ands to

stations 2 and 3

PY 3 -Send the program selection

(number) to stations 2 and 3

PY 2 -> GPB 10

PY 3 -> GPB 11

output

PY 2 -Rec ei ve the ack. from

station 2

PY 3 -Receive the position and fault

message from station 2

PY 2 <- GPB 100

PY 3 <- GPB 101

input GP

PY 4 -Rec ei ve the ack. from

station 3

PY 5 -Receive the position and fault

messages from station 3

PY 4 <- GPB 102

PY 5 <- GPB 103

input GP

PY 10 -Receive the control commands

from station 1

PY 11 -Receive the program selection

from station 1

PY 12 -Receive the fault messages from

station 3

PY 10 <- GPB 10

PY 11 <- GPB 11

PY 12 <- GPB 122

input GP

PY 20 -Send the ack. to stn. 1

PY 21 -Send the position and fault

messages to station 1

PY 22 -Se nd the fa ult messa ges to

station 3

PY 20 -> GPB 100

PY 21 -> GPB 101

PY 22 -> GPB 22

output

PY 110 -Receive the control commands

fromstation 1

PY 111 -Receive the program selectionl

from station 1

PY 1 12 -Rec eive the f ault mess ages fro m

Station 2

PY 110 <- GPB 10

PY 111 <- GPB 11

PY 112 <- GPB 22

input GP

PY 120 -Send the ack. to

station 1

PY 121 -Send the position and fault

messages to station 1

PY 122 -Send the fault messages to

station 2

PY 120 -> GPB 102

PY 121 -> GPB 103

PY 122 -> GPB 122

output

Table 9.3: Specification of the Transmitted and Received Data and the Assignment to GP

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 38

In Figs. 9.16 to 9.20 you can see that the I/O input and output bytes of the

three stations in the manufacturing unit are practically directly connected or

"wired" to each other by the GP.

Station 1

Station 2

Station 3

PY 130 PY 3

PY 10

PY 110

Auto Man Start Stop PROGRAM SELECTION

PY 11

PY 111

Fig . 9.16 : Station 1 Sends Control Commands and Program Selection to Stations 2 and 3

Station 1

Station 2 Auto Man Start Stop PO51 PO52 Fault

1Fault

PY 2 PY 3

PY 148 PY 149

Position and fault messages

Fig . 9.17 : St atio n 2 S ends Ackno wle dgme nt, Positi on an d Fa ult M essa ges to Sta tion 1

B8976060/02 Communication with Global I/Os

9 - 39 Volume 1

Station 2

Station 3 Fault

1Fault

PY 12

PY 122

Fig . 9.18 : St atio n 3 S ends Fa ult Me ssag es to Stat ion 2

Station 2

Station 3

PY 22

PY 112

Fault

1Fault

Fig . 9.19 : St atio n 2 S ends Fa ult Me ssag es to Stat ion 3

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 40

Station 2

Station 3 Auto Man Start Stop PO51 PO52 Fault

1Fault

PY 4 PY 5

PY 120 PY 121

Position and fault messages

QB QB

Fig . 9.20 : St atio n 3 S ends Ackno wle dgme nt, Positi on an d Fa ult M essa ges to Sta tion 1

B8976060/02 Communication with Global I/Os

9 - 41 Volume 1

9.3.1.1 Start-up Response

During a PLC "cold restart" the various PLCs process the following start-up

OBs:

The start-up OBs have the following task with the global I/Os data

transmission mode;

➣They must synchronize the CP 5430 TF/CP 5431 FMS interface.

➣They can make sure that the PLC only starts up when certain or all

stations are ready to transmit and receive (i.e. when there are no GP

error messages).

➣If you have selected the CYCLE-SYNCHRONIZED update mode, the

complete GP should be received at the end of a start-up OB.

St art-up OB OB 20 OB 21 OB 22

Device

S5-115U Cold restart after

STOP-RUN

transition (manual)

Cold res tart after

power down

(automatic)

S5-135U

S5-155U Cold restart

(manual) Warm restart

(manual) Warm r estart

(automatic)

Table 9.4: Sta rt-Up OBs for the Vari ous Programmable Con trollers

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 42

For the "manufacturing unit" example, the three stations should have

different start-up responses:

As a result of the conditions listed above, the following start-up variations

are required:

Station No. Start-up response

S5-155U

(head control )

The controller should always start up even if there is a

GP erro r mess age s uch as PLC S TOP, volt age OFF, n o

bus connection to the manufacturing subuni ts 1 and 2.

S5-115U

(manufacturing

subunit 1)

The controller should always start up when the head

control is active, i.e. when there are no GP error

messages for station 1. GP error messages for

ma nufa ctu rin g su bunit 2 are ignore d.

S5-135U

(manufacturing

subunit 2)

This controller must only start up when both the head

controller and the manufacturing subunit 1 are running,

i.e. there ar e no GP error messages.

Table 9.5: Description of the Start-up Response for the Stations of the Manufacturing Unit

(OB 20, OB21, OB22)

Station 1:

HDB SYNCHRON call

for the SSNR of the CP 5430 TF/CP 5431 FMS

Fig . 9.21 : St art -up R esp onse of St ati on 1 ( Man ufac turi ng U nit)

B8976060/02 Communication with Global I/Os

9 - 43 Volume 1

Station 2:

(OB 20, OB21)

With this HDB call (job number

201) the station list is read in

by the CP 5430 TF/

list contains the statuses of

the CPs of all active stations

from which input GP is expected.

The structure of the station list

is explained following this

figure.

Evaluation of the station list

i.e. interrogation of the statuses

of all stations which should have

started up.

Job number 211 causes the

first reception of the GP, i.e.

inputs and station list are

updated (only necessary in

the CYCLE-SYNCHRONIZED

mode)

HDB SYNCHRON call for the SSNR

of the CP 5430 TF/CP 5431 FMS

HDB RECEIVE call with

ANR 211

HDB RECEIVE call with

ANR 201

yes

Is GP of

station 1

ok?

end

Synchronization of the interface

PLC-CP 5430 TF/CP 5431 FMS

CP 5431 FMS. The station

Fig . 9.22 : St art -up R esp onse of St ati on 2 ( Man ufac turi ng U nit)

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 44

Station 3:

(OB 20, OB21, OB 22)

With this HDB call (job number

201), the station list is read in

by the CP 5430 TF/CP 5431 FMS.

The station list contains the

statuses of the CPs of all active

stations on the bus from which

input GP is expected.

HDB SYNCHRON call for the SSNR

of the CP 5430 TF/CP 5431 FMS

yes

GP of

stations

1and 2 ok?

end

Synchronization of the interface

PLC-CP 5430 TF/CP 5431 FMS

Evaluation of the station list

i.e. interrogation of the statuses

which should have started up

(here, stations 1 and 2).

HDB RECEIVE call with

ANR 211

HDB RECEIVE call with

ANR 201

Fig . 9.23 : St art -up R esp onse of St ati on 3 ( Man ufac turi ng U nit)

B8976060/02 Communication with Global I/Os

9 - 45 Volume 1

9.3.1.2 Cyclic Mode

The cyclic program has the following structure in all stations for the

CYCLE-SYNCHRONIZED update mode.

HDB SEND call with ANR 210

(at start of cyclic program)

Control program

HDB RECEIVE call with ANR 211

(last statement in cyclic program

before block end)

Fig . 9.24 : Stru ct ure of the Cyclic Program (O B 1) for all Stations. (M an ufacturing Unit)

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 46

9.3.2 Transferring the Configuration Data for the CP 5430 TF/CP

5431 FMS and the STEP 5 User Program

To be able to implement the practical example for communication using

global I/Os, follow the procedure outlined below (and refer to Chapter 16):

➣Transfer the following COM 5430 TF/COM 5431 FMS database files to

the CPs you are using:

When using the CP 5430 TF under the network file GPO@@NCM.NET

– f or station 1 OGPTLN1.155

– f or station 2 OGPTLN2.115

– f or station 3 OGPTLN3.135.

When using the CP 5431 FMS under the network file GPQ@@NCM.NET

– f or station 1 QGPTLN1.155

– f or station 2 QGPTLN2.115

– f or station 3 QGPTLN3.135.

➣Transfer the following STEP 5 files to the programmable controllers you

are using:

– For P LC 1 (S5-155U) the file GP155UST.S5D

– For P LC 2 (S5-115U) the file GP115UST.S5D

– For P LC 3 (S5-135U) the file GP135UST.S5D.❑

B8976060/02 Communication with Global I/Os

9 - 47 Volume 1

Notes

Communication with Global I/Os B8976060/01

Vol ume 1 9 - 48

10 Data Transmission with Cyclic I/Os

(CP 5430 TF)

This chapter contains the following information:

➣The devices and applications for which data transmission with cyclic

I/Os (ZP) is suitable.

➣How this type of data transmission functions.

➣How to assign parameters to the CP 5430 TF for this type of data

transmission when an S5 programmable controller is to exchange data

with a fiel d device (example in Section 10.3).

➣The STEP 5 program for this example.

Applications for data transmission w ith cyclic I/Os (ZP)

The high, cyclic communications demands for the automation function of a

field device cannot be met with direct HDB calls. Instead of cyclic HDB

calls, the CP 5430 TF therefore provides the cyclic I/Os service.

Data transmission with cyclic I/Os is suitable for communication between

SIMATIC S5 PLCs and field devices. Field devices are passive stations on

the bus which cannot access the bus themselves and must be constantly

(normally cyclicall y) polled by active L2 stations.

The main feature of data transmission with cyclic I/Os (ZP) is that it is easy

to use, i.e. it involves far less programming compared with other types of

data transmission, for example "free layer 2 access" (refer to Chapter 8).

The term "cyclic I/Os" means that part of the I/O area is not used by I/O

modules but rather for the cyclic data exchange between SIMATIC

programmable controllers and passive stations on the bus. "Cyclic data

exchange" means that the CP 5430 TF sends the whole of the output area

assigned for ZP cyclicall y and updates the whole input area assigned for ZP

with the received data. You can use these virtual I/Os as proper inputs or

outputs. These addressed areas are processed normally with STEP 5

commands. The mode is cycle-synchronized or free. With the

CYCLE-SYNCHRONIZED mode, an HDB must be called at the checkpoints

B8976060/02 Communication with Cyclic I/Os

10 - 1 Volume 1

required by the user to ensure the consistency of inputs and outputs. This

HDB also serves to trigger a group job for data transmission.

The volume of data to be transmitted with ZP should be small.

This would, for example, include control commands, messages, measured

values and analog values.

☞Simul taneous use of ZP and DP is not possi ble

Communica tion with Cyclic I/Os B8 97 60 60/02

Vol ume 1 10 - 2

10.1 Basics of Data Transmission with Cyclic I/Os (ZP)

When you have specified a SIMATIC S5 PLC with a CP 5430 TF as being

an active station, you can program data transmission with "cyclic I/Os" for

this PLC and exchange (poll ) data with PROFI BUS-compatible field devices.

The communication between the SIMATIC S5 PLC and field device

functions according to the mast er slave method.

This section describes the functions of the cyclic I/Os from the point of view

of the CPU control program

In data transmission with cyclic I/Os the data exchange takes place via the

I/Os of the SIMATIC PLC, as follows

Communication using cyclic I/Os is only permitted using the base interface

number (base SSNR).

➣The data for transmission are assigned to the output area of the I/Os in

the control program.

➣The received data are stored in the input area of the I/Os.

➣Transmitted and received data can be processed with STEP 5

operations.

–Data for transmission via the output area

–Received data via the input area

All I/O bytes via which you want to transmit and all I/O bytes via which you

want to receive must be designated as cyclic I/Os. To do this, you program

I/O areas using COM 5430 TF (refer to section 10.2).

B8976060/02 Communication with Cyclic I/Os

10 - 3 Volume 1

Configuring I/O areas for ZP

Fig. 10.1 illustrates the basic function of the cyclic I/Os. The field device

(slave) can only be addressed by the CP 5430 TF when it knows both the

L2 address and the corresponding service access point (SAP) of this field

device. Both the L2 address of the slave and the SAP number must be

specified using the ZP editor of the COM 5430 TF software package.

The CP 5430 TF becomes the "distributor" after it is configured with the ZP

editor. I t perform s the f ollowi ng functions:

➣receives the trigger for data transmission via an HDB or CP internal

cycle

➣reads the ZP output area of the CPU

➣allocates the L2 address and destination SAP to the corresponding field

device

➣"packs" all the output bytes belonging together in frames

➣sends these frames to the addressed field devices and at the same

time requests reply frames from these field devices

CPU CP 5430 TF Field device

Peripherals

Output

area

Input

area

Input

buffer

Output

buffer

L2 bus

Dual-port RAM of the CP 5430 TF SAP (with the CP 5430 TF, SAP 61 is used for ZP)

The SAP of the field device must be assigned with

COM 5430 TF

SAP 61 SAP ?

Fig. 10 .1: O utlin e of th e Functio ns of Cyclic I/Os

Communica tion with Cyclic I/Os B8 97 60 60/02

Vol ume 1 10 - 4

➣receives the reply frames and assigns them to the configured ZP input

bytes of t he CPU

The following information is important:

➣With field devices, different data (e.g. programming data in contrast to

signal data) can be assigned to different SAPs.

➣ZP transmits and receives exclusively using SAP number 61.

➣ZP uses the PROFIBUS layer 2 service SRD (send and request data)

for dat a transmission.

➣The frames of the cyclic I/Os always have low priority. This means that

when there is a large volume of traffic on the bus from other stations

with higher priority, it cannot be guaranteed that ZP frames are

transmit ted during a token rotation.

➣if ZP is to transmit via the default SAP, SAP61 must be set as the

default SAP

Updating the input and o utput areas of the cyclic I/Os

The times at which the CP 5430 TF updates the ZP bytes to be

transmitted are either

➣FREE mode: decided by the CP (the STEP 5 control program has no

influence) or

➣CYCLE-SYNCHRONIZED mode: decided by the control program using

a send handling block call with job number 210.

The times at which the CP 5430 TF transfers the received ZP bytes to the

CPU input area are also either

➣FREE mode: decided by the CP (not influenced by the STEP 5 control

program) or

➣CYCLE-SYNCHRONIZED mode: decided by the control program by

means of a RECEIVE handling block call with job number 211.

B8976060/02 Communication with Cyclic I/Os

10 - 5 Volume 1

Consi stency of the input and outpu t bytes of th e Z P

➣FREE mode: guaranteed consi stency of one byte.

➣CYCLE-SYNCHRONIZED mode: guaranteed consistency over the

whole ar ea.

☞The ZP update points depend on the communication via the

L2 bus. Communication between the CP 5430 TF and passive

stations is constant (cyclic) and not dependent on handling

block calls (SEND/RECEIVE with ANR 210/211).

Special features

If a passive station fails, the input bytes assigned to this station are reset

(to the value 0). If the PLC changes from the RUN to the STOP mode, its

ZP output bytes are also reset so that the value "0" is transmitted. This is

also the reaction during start-up.

The following pages describe the FREE and CYCLE-SYNCHRONIZED

modes; how to set these modes with COM 5430 TF is described in the

example.

Communica tion with Cyclic I/Os B8 97 60 60/02

Vol ume 1 10 - 6

Procedure with the FREE mode: master transmits to slave

Expla nation of Fig . 10.2:

➣The control program modifies the output byte to be transmitted (PY 1).

➣In the CP cycle, the CP 5430 TF transmits the whole of the output area

assigned to ZP. In the FREE mode, the CP cycle determines the point

at which the data is transmitted.

In the FREE mode, the time when the CP 5430 TF transmits the ZP output

bytes i s not f ixed.

PLC

program

execution

I/O

area in

CP- DPR

PY1 to the BUS

The byte

transmitted

by ZP

1 1

Internal

CP cycle=

"after processing

the polling list"

Fig. 10 .2: How the FREE Mode Functions: Master Transmits to Slave

B8976060/02 Communication with Cyclic I/Os

10 - 7 Volume 1

Procedure with the FREE mode: master receives from slave

Expla nation of Fig . 10.3:

➣The byte received by ZP is tr ansferred to the I/O area of the DPR withi n

the internal CP cycle.

➣The control program can then work wi th these values under PY1.

PLC

program

execution

I/O

area in

CP-DPR

PY1 from BUS

The byte

received

by ZP

Internal CP-

cycle =

"after processing

the polling list"

? undefined status

Fig. 10 .3: F REE M ode : M aster R ece ives from Sla ve

Communica tion with Cyclic I/Os B8 97 60 60/02

Vol ume 1 10 - 8

☞If ZP bytes need to be transferred together because they form

a logical unit (e.g. a control parameter requiring a word), the

FREE update mode must under no circumstances be

selected. With this mode, there is no guarantee that the ZP

bytes which belong together are actually transferred together.

The receiver (PLC or slave) would then process inconsistent

values.

Essential features of the FREE mode:

➣Minimum cycle load (corresponds to the cycle load that would occur

simply by pluggi ng in the corresponding input/output modules.

➣Minimum l oad on t he CP.

➣Simple programming (single handling block call; HDB SYNCHRON

during start -up).

B8976060/02 Communication with Cyclic I/Os

10 - 9 Volume 1

Procedure with the CYCLE-SYNCHRONIZED mode: master transmits to

slave

Expla nation of Fig . 10.4:

➣The control program changes the output byte to be transmitted (PY1).

PLC

program

execution

I/O

area in

CP-DPR

PY1 to the BUS

The byte

transmitted

by ZP

1 1

HDB

execution

HDB

execution

ttt

Bus

cycle

PLC

cycle

Fig. 10 .4: CYCL E-SYNCHRONI ZED Mode: Master Transmits t o Slave

Communica tion with Cyclic I/Os B8 97 60 60/02

Volume 1 10 - 10

➣At the point when the HDB is executed, the CP 5430 TF transmits all

the output bytes assigned to the ZP. In contrast to the FREE mode, you

determine this point in time in the control program by means of an HDB

SEND call with job number 210.

Procedure with the CYCLE-SYNCHRONIZED mode: master receives

from slave

Expla nation of Fig . 10.5:

➣The byte received by ZP is tr ansferred to the I/O area of the DPR at the

point determined by the executi on of the HDB.

PLC

program

execution area in

CP-DPR

PY0 from BUS

The byte

received

by ZP

HDB

execution

HDB

execution

ttt

Bus

cycle

PLC

cycle

? undefined status

I/O

Fig. 10 .5: CYCL E-SYNCHRONI ZED Mode: Master Receives from Slave

B8976060/02 Communication with Cyclic I/Os

10 - 11 Volume 1

➣The control program can then work with these values under PY0.

The advantage of the CYCLE-SYNCHRONIZED mode is that the time at

which the ZP is sent or received is fixed in the control program.

To ensure that the ZP input area of the CPU is also updated at a defined

point in time, an HDB RECEIVE with job number 211 must be called in the

control program, normally at the end of the cyclic control program.

To ensure that the ZP output area of the CPU is also updated at a defined

point in time, an HDB SEND with job number 210 must be called in the

control program, normally at the start of the cyclic control program.

☞With short PLC cycle times (< 50 ms) the HDB

SEND/RECEIVE calls with job numbers 210/211 may extend

the PLC cycle time. The load on the CP 5430 TF may also

increase so that the transmission times of the global I/Os

deteriorate.

If you have short PLC cycle times, make sure that the time between two

HDB calls is greater than 50 ms (e.g. by programming HDB

SEND/RECEIVE calls with job numbers 210/211 in every nth PLC cycle).

The normal safety philosophy of SIMATIC control systems, resetting all the

output bytes if the PLC stops and clearing the input bytes belonging to an

I/O device if this fai ls, is also used here. The total number of GP and ZP I/O

bytes processed by the CP must not exceed 256 input or output bytes, but

can be assigned to the P or O areas (O area only with S5 135U, S5 150U

and S5 155U).

Sequence of the data transmission

The start-up OBs have the following task with the cyclic I/Os data

transmission mode;

➣They must synchronize the CP 5430 TF interface

➣They can make sure that the PLC only starts up when certain or all

stations are ready to transmit and receive (i.e. when there are no ZP

error m essages)

Communica tion with Cyclic I/Os B8 97 60 60/02

Volume 1 10 - 12

➣If you have selected the CYCLE-SYNCHRONIZED update mode, the

complete ZP should be received at the end of a start-up OB

The SEND synchronization point is indicated by the SEND-HDB (ANR 210).

The parameter QTYP must be assigned the value "NN". DBNR, QANF,

QLAE are irrelevant. The ANZW should be assigned to a data or flag word.

The RECEIVE synchronization point is indicated by the RECEIVE HDB in

the "direct mode" and ANR 211. The remaining assignment of parameters

to the HDBs is the same as for the SEND synchronization point.

The following figure (Fig. 10.6) illustrates one way of integrating the HDBs

in the cold or warm restart branch of the PLC.

(OB 20, OB21, OB 22)

With this HDB call (job number

202), the station list is read in

by the CP 5430 TF.

The station list contains the

statuses of the CPs of all slaves

addressed by the ZP.

HDB SYNCHRON call

for the SSNR of the CP 5430 TF

yes

ZP of

stations

1and 2 ok?

end

Evaluation of the station list

i.e. interrogation of the statuses

of all slaves which must have

started up.

HDB RECEIVE call with

ANR 211

HDB RECEIVE call with

ANR 202

This HDB call (job number 211)

causes the ZP to be received

the first time, i.e. the inputs and

station list are updated. (only

required in CYCLE-SYNCHR.

mode).

Fig. 10 .6: HDBs in Cold or Warm Res tart of the PLC

B8976060/02 Communication with Cyclic I/Os

10 - 13 Volume 1

Both in the cold restart branch (OB 20) and in the warm restart branch (OB

21/22) each CP interface to be used later must be synchronized

(SYNCHRON HDB). From the cold restart branch, the PLC operating

system branches directly to the first cycle checkpoint. The process image of

the inputs (PII) is read in for the first time at this point. The first RECEIVE

synchronization point for the CP 5430 TF is therefore already in the cold

restart branch.

After the warm restart (OB21/22) the PLC cycle is resumed at the point at

which it was interrupted. The old PII is still valid for the remainder of the

PLC cycle and is only updated at the next PLC cycle checkpoint. If a check

of the ZP image is required with a warm restart, the control HDB should be

called in a loop at the end of OB21/22 until the status word contains no

further relevant error bits.

Cyclic operation

The cyclic program has the following structure for all stations in the CYCLE

SYNCHRONIZED update mode:

Control program

Cycle

checkpoint

HDB RECEIVE call with

ANR 211

(last statement in cyclic

program before the end

of the block)

Call HDB SEND with

ANR 210

(at the start of the cyclic

program)

Fig. 10 .7: Stru cture of the Cyclic Program

Communica tion with Cyclic I/Os B8 97 60 60/02

Volume 1 10 - 14

In cyclic operation, the SEND synchronization point is immediately at the

start of OB 1; the RECEIVE synchronization point at the end of the PLC

cycle. The division into a SEND and a RECEIVE synchronization point is

necessary, since the CP must make the received ZP bytes available to the

PLC before the PLC cycle control point and on the other hand the CP can

only process the ZP output byte after the PIQ has been output.

B8976060/02 Communication with Cyclic I/Os

10 - 15 Volume 1

10.1.1 Checking the Data Transmission with ANZW and the ZP

Stat ion List

☞If there is a group error message, bit 3 of the status word

(status bit) is not set.

Not

used Error

bits Data

mgment. Status

bits

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Job complete with error*

(e.g. invalid job number)

Job complete without error

SEND synchronization disabled

RECEIVE synchronization possible

Synchronization done without error

(Input GP was received)

* Bit 3 of the status bits is not connected with the error bits (8..11).

When bit 3 is set, the error is not specified by the error bits. All the errors

listed in table 7.3 are possible.

Fig. 10 .8: Stru cture of ANZW for HDB SEND (ANR 21 0) a nd RECEIVE (ANR 211), here:

Status Bits

Communica tion with Cyclic I/Os B8 97 60 60/02

Volume 1 10 - 16

Error bits for the RECEIVE-HDB (ANR 211)

Error bits of the ZP station list (ANR 202)

Bit 11 10 9 8 of the status word

Reserved for GP error message

ZP image is incomplete

(either all stations have not yet

started up

at least one station has

dropped out)

Reserved for GP error message

Fig. 10 .9: Erro r Bits in RECEIVE HDB (ANR 211)

Bit 11 10 9 8 of the status word

ZP image is incomplete

(either all stations have not yet

at least one station has

dropped out)

Only relevant with the IM 318B

(there is a request from the

IM 318B to fetch diagnostic

data)

started up

Fig. 10 .10: Error Bits of the ZP Station List

B8976060/02 Communication with Cyclic I/Os

10 - 17 Volume 1

Structure of the ZP station list

The station list has a length of 16 bytes, with each bit assigned to a station

address.

All stations configured for ZP and which respond correctly are marked with

"0". Stations not responding correctly or from which a diagnosis request

exists (only with IM318B) are marked wit h a "1" in the stati on lis t.

The last bit in the station list is irrelevant, since the permitted station

addresses on the L2 bus are in t he range from 0 to 126.

Error bits and updating the station list during data transmission:

During start-up, the station list is initialized with "0". After the RECEIVE

HDB has been executed the first time, all stations which do not respond

correctly are marked with bit value "1". Note: the RECEIVE HDB is only

released when the complete polling list has been run through once.

As long as one station does not respond correctly, the corresponding group

error message is set both in the status word of the RECEIVE HDB (ANR

211) and in the status word of the ZP station list (ANR 202).

As soon as a station responds correctly, it is cleared from the station list

and the bit in the station list is set to "0".

76543210

120 127

7654321076543210

012345678 9 10 11 12 13 14 15

2 - 14

16 - 119

Byte

Bit

Station

address

Fig. 10 .11: Structure of the ZP Station List

Communica tion with Cyclic I/Os B8 97 60 60/02

Volume 1 10 - 18

If an error occurs, (one or more links not in the data transfer phase), the ZP

station list can be read out at any point. If all the links are functioning

correctly in the data transfer phase, the RECEIVE HDB for the ZP station

list is disabled.

A further distinction must be made as to the mode (FREE or

CYCLE-SYNCHRONIZED) in which the station list is eval uated, as follows:

FREE:

the station list is updated conti nuously by the CP.

CYCLE-SYNCHRONIZED:

the station list is updated by the CP at the point when the HDB RECEIVE

with job number 211 is called in the control program (ZP receive)

B8976060/02 Communication with Cyclic I/Os

10 - 19 Volume 1

10.2 Configuring

The PG package SINEC NCM with COM 5430 TF is used to configure the

functions.

The screens you require for configuring are provided by SINEC NCM as

shown in Fig. 10.12.

➣I/O areas

➣ZP ed i tor

➣Documentation and test = Init Edit ...

SINEC NCM

Edit -> I/Os

I/O area Edit -> I/Os

ZP editor

Edit

Menu item

-> I/O areas -> ZP Editor

Documentation and

Test in Chapter 14

dealt with in separate chapters

Fig. 10 .12: Configuring Cyclic I/Os

Communica tion with Cyclic I/Os B8 97 60 60/02

Volume 1 10 - 20

10.2.1 I/O Areas

Input and output areas of the SIMATIC PLC for cyclic I/Os are assigned in

a screen.

If you also specify areas for GP, you only require three area limits for the

input and output areas since one limit is always specified implicitly.

☞Simul taneous use of ZP and DP is not possi ble

Select Edit -> I/Os -> I/O areas to call the following screen. The screen has

the following structure:

Input/Output (I/O) Areas:

L2 station address:

OUTPUT AREAS:

INPUT AREAS:

GP update:

Stations from which global I/Os are expected:

OK SELECT

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

1 2 3 4 5 6 7 9 10 11 12 13 14 15 168

ZP/DP STA: GP STA: GP END: ZP/DP END:

CP type:

Source:

ZP/DP update

HELP

(EXIT)

Fig. 10 .13: Screen for Assig nin g I/O Areas (CP 543 0 TF )

B8976060/02 Communication with Cyclic I/Os

10 - 21 Volume 1

Input fields :

Update: Cycle-synchronized: update at the cycle checkpoint by

the HDB.

Free: implicit update of the I/O areas by the CP.

Input areas

ZP/DP STA: Beginning of the (continuous) input area for the cyclic

I/Os. (Range of values PY 0 .. 254, OY 0 .. 254)

ZP/DP END: End of the (continuous) input area for the cyclic I/Os.

(Range of values PY 1 .. 255, OY 1 .. 255)

Output areas

ZP/DP STA: Beginning of the (continuous) output area for the cyclic

I/Os. (Range of values PY 0 .. 254, OY 0 .. 254)

ZP/DP END: End of the (continuous) output area for the cyclic I/Os.

(Range of values PY 1 .. 255, OY 1 .. 255)

Output fields:

L2 station

address: The address of the currently addressed station is

displayed.

Functi on keys:

OK The "OK" key enters the data. If the module file does

not yet exist, it is set up when you confirm the entries.

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select values from the list with the cursor keys and

enter them in the field with the return key.

Communica tion with Cyclic I/Os B8 97 60 60/02

Volume 1 10 - 22

☞The input or output area must always begin with an even byte

number and must always end wit h an odd byte number.

The fields remain empty if no input or output areas are required for the

cycl ic I/Os.

The input area/output area for ZP must not exceed a maximum of 256

bytes.

If you want to reserve areas for the global I/Os (GP), remember the

following when you are res erving areas :

➣GP and ZP input areas must not overlap.

➣GP and ZP output areas must not overlap.

➣The reserved input area for GP and ZP must not include gaps.

➣The reserved output area for GP and ZP must not include gaps.

➣The input area per station for GP and ZP together must not exceed a

maximum of 256 bytes.

➣The output area per station for GP and ZP together must not exceed a

maximum of 256 bytes, of which a maximum of 64 bytes are reserved

for GP.

☞The I/O area reserved for the GP and ZP must not be used by

other I/O modu les.

An online modification of the GP/ZP area only becomes

effective after the CP 5430 TF has gone through power

off /power on.

B8976060/02 Communication with Cyclic I/Os

10 - 23 Volume 1

10.2.2 ZP Editor

Once you have reserved the input/output areas for cyclic I/Os, you must

now assign part of the reserved area to each field device (slave) using the

ZP ed i tor.

Select Edit -> I/Os -> ZP editor to call the following screen. The screen has

the following structure:

Input fi elds

rem. add: In this column, you specify the L2 address of the slave

station.

DSAP: The SAP of the slave station must also be specified.

(Range of values: 2 .. 64, empty = default SAP)

ZP Editor

L2 station address:

Output area: Input area:

OK SELECT

from to from to

Rem. add. DSAP from to from to M

DELETE

INSERT

Default SAP:

CP type:

Source: (EXIT)

HELP

Fig. 10 .14: "ZP Editor" Screen

Communica tion with Cyclic I/Os B8 97 60 60/02

Volume 1 10 - 24

Output area

If you intend to define an output block for the corresponding slave on the

DSAP, this block of continuous bytes is specified here.

from: The first byte of the output block.

to: The last byte of the output block.

It is possibl e to assign t he output areas more than once using a different L2

address.

Input area

If an input block is intended, it is defined here. Multiple assignment is,

however, not possibl e.

from: The first byte of the input block.

to: The last byte of the input block.

M: Here, the number of entries in the internal polling list is

specified. This also specifies the priority of the link

(range of values: default 1, otherwise 1...4).

Output fields:

L2 station

address: The L2 station address of the station for which inputs

and outputs are to be assigned to a slave station.

Input/output area

Here, the I/O area in which the variables to be configured will be simulated,

is di splayed.

Default SAP: Here, the specified default SAP is displayed (refer to

Section 6.5.3 network parameters). If the CP 5430 TF

is to transmit via the default SAP with ZP, the default

SAP must be set to SAP number 61.

from: The first byte of the block.

to: The last byte of the block.

(range of values in I/O area, configured area).

B8976060/02 Communication with Cyclic I/Os

10 - 25 Volume 1

Functi on keys:

INSERT An empty line is inserted at the current cursor position.

DELETE Deletes the line marked by the cursor in the input or

output area.

OK The "OK" key enters the data. If the module file does

not yet exist, it is set up when you confirm the entries.

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select values from the list with the cursor keys and

enter them in the field with the return key.

☞After saving and reading out the input/output areas, the

entries are displayed in descending order of priorit y (M).

Communica tion with Cyclic I/Os B8 97 60 60/02

Volume 1 10 - 26

10.3 Example of using the Cyclic I/Os

The following example describes an application using cycle-synchronized

cycl ic I/Os.

Hardware and software requirements

The following hardware is necessary:

➣Two SIMATIC S5 programmable controllers (PLC 1: S5-115U and

PLC 2: S5-95U)

➣One CP 5430 TF

➣One RAM submodule per CP

➣Two RS 485 bus terminals

➣SINEC L2 bus cable

➣At least one PG 710, PG 730, PG 750 or PG 770,

or PC

The following software packages are also required:

➣COM 5430 TF under SINEC NCM

➣PG software for STEP 5 programming

➣Appropriate handling blocks for the PLCs

➣Diskette with the example programs.

B8976060/02 Communication with Cyclic I/Os

10 - 27 Volume 1

10.3.1 Program Description

Two programmable controllers (S5-115U and S5-95U) must be linked via

the SINEC L2-BUS.

For the example, a simple data exchange of two bytes in both

communications directions has been selected. PLC 1 sends changing data

to PLC 2. In PLC 2, these data are returned to PLC 1.

Station 1 Station 2

S5-115U

with CPU 944 S5-95U

L2 bus cable

Fig. 10 .15: Programmable Contro lle rs

Station number Inputs and outputs used for

data transmission

1 PY 1 0 - tr ansmit I/Os

PY 11 - trans mit I/Os

PY 12 - rece ive I/Os

PY 13 - rece ive I/Os

output ZP

input ZP

2 PY 100

DW 1 trans mitted word

DW 10 received word

output ZP

input ZP

Table 10.1: Specification of the Transmitted and Received Data and Assignment to ZP

Communica tion with Cyclic I/Os B8 97 60 60/02

Volume 1 10 - 28

10.3.1.1 Program for PLC 1

When a PLC starts up, the CP interface must be synchronized using a

SYNCHRON HDB.

PLC 1 sends DW 10 of DB 100 to PLC 2 and fetches the DW 1 of DB 100.

10.3.1.2 Program for PLC 2 (S 5-95U)

PLC 2 receives the ZP from PLC 1 via DW 10 in DB 100. FB 150 transfers

the received DW 10 to DW 1 of DB 100 and therefore sends it back to PLC

Assignment of DB 1 parameters of the S5 95U for L2

SL2 -> L2 parameters

STA 2 -> own L2 address

STA PAS -> station is passive

BDR 187.5 -> transmission rate 187.5 Kbps

SDT 1 12 - > smallest station delay 12 bit times

ST 380 -> slot time 380

ZPDB 100 - > transmit and receive DB of the ZP, DB 100

ZPSS FY 100 -> status byte of the ZP (FY 100)

ZPSA DW 1-1 -> output area of the ZP (DW 1)

ZPSE DW 10-10 -> input area of the ZP (DW 10)

DB 1 C:DZP95UST.S5D

0 : KS = "DB 1 ";

12: KS = "SL2: STA 2 STA PAS ";

24: KS = "BDR 187.5 SDT 1 12 ";

36: KS = "ST 380 ";

48: KS = " ZPDB DB100 ZPSS FY 100 ";

60: KS = " ZPSA DW 1 DW 1 ";

72: KS = " ZPSE DW 10 DW 10; ";

84: KS = "ERT: ERR DB 255 DW ;1 ";

96: KS = "END ";

108:

Table 10.2: DB 1

B8976060/02 Communication with Cyclic I/Os

10 - 29 Volume 1

10.3.2 Transferring the Configuration Data for the CP 5430 TF and

the STEP 5 User Program

To be able to implement the practical example for communication using

cyclic I/Os, follow the proc edure outlined below (and refer to Chapter 16):

➣Transfer the following COM 5430 TF database file to the CP 5430 you

are using:

– under the network fil e ZP@@@NCM.NET, the file OZPTLN1.115

➣Transfer the following STEP 5 files to the programmable controllers you

are using:

– For P LC 1 (S5-115U) the file ZP115UST.S5D

– For P LC 2 (S5-95U) the file ZP95U@ST.S5D❑

Communica tion with Cyclic I/Os B8 97 60 60/02

Volume 1 10 - 30

11 Data Transmission with Distributed I/Os

With the distributed I/ Os system SINEC L2-DP, you can use a large number

of distributed I/O modules and field devices in close proximity to the

process.

Distributed means that there can be large distances between your

programmable controller and the I /O and field devices which can be bridged

by a field bus or (twisted pair or fiber optic).

This chapter describes the functions of the DP from the point of view of the

CPU control program.

Data exchange with distributed I/Os (DP) is handled via the I/O area of the

SIMATIC PLC:

– In the control program, the data for transmission are assigned to

the output area of the I/Os.

– The rec eived data are stored in the input area of the I/Os.

All I/O bytes via which you want to send data and all I/O bytes via which

you want to rec eive data must be marked as DP. You do this by confi guring

the I/O areas in COM 5430 TF/COM 5431 FMS (see Section 11.6.1).

This chapter describes the foll owing:

➣How data transmission with DP functions.

➣Configuring the data exchange with the connected DP slaves.

➣Diagnostics using the control program.

B8976060/02 Distributed I/Os (DP)

11 - 1 Volume 1

The distributed I/Os system SINEC L2-DP consists of active and passive

stations on the bus.

Active stations (masters) are:

– t he programmable controllers

S5-115U/H, S5-135U, S5-150U, S5-155U/H with the master

modules IM308-B and CP 5430 T F/CP 5431 FMS

– P Cs or PGs with the appropriate interface card

– pr ogrammable controllers of other manufacturers

Passive stations (slav es) are, for example:

– ET200U-DP

– S 5-95U L2-DP

– OP 15/20

– DP slaves of other manufacturers

Data transmission using L2-DP (distributed I/Os) provides a standardized

interface for communication between SIMATIC S5 PLCs and field devices

(DP slaves).

Data transmission using DP is particularly easy to handle.

Programming and handling is reduced to a minimum for the user. When

using the DP service, distributed I/Os can be used as if they were modules

plugged into a central controller. With DP, part of the I/O area of the PLC is

occupied by the connected DP slaves with the CP modeling the I/O bytes

used in the direction of the CPU.

This means that access by the user program to the I/O bytes used for

L2-DP, is acknowledged by the CP in place of the distributed I/Os.

Using the L2- DP protocol, the inputs and outputs assigned to t he DP slaves

are exchanged cyclically be the CP (see Fig. 11.1).

Distributed I/ Os (DP) B890 60 /02

Vol ume 1 11 - 2

ONLINE test and diagnostics with the COM 5430 TF/COM 5431 FMS

package are described in Section 14.2.4 .

☞Simul taneous use of GP/ZP and DP is no t po ssible.

Simul taneous use of GP/CI and DP is not possible.

CPU

S5 backplane bus CP 5431 FMS

I/O area

DP polling list

Slave x

L2 bus

Q bytes

I bytes

QX1

QX2

QX3

QX4

IX1

IX2

Slave y

Q bytes

I bytes

QY1

QY2

IY1

IY2

IY3

IY4

Q bytes

I bytes

QX1

QX2

QX3

QX4

IX1

IX2

Q bytes

I bytes

QY1

QY2

IY1

IY2

IY3

IY4

DP slave x

DP slave y

CP5430 TF/

Fig. 11 .1 How the Data Transmission between CPs and DP Slaves Functions

B8976060/02 Distributed I/Os (DP)

11 - 3 Volume 1

11.1 Basics of SINEC L2-DP

SINEC L2-DP is the Siemens implementation of the DIN E19245 Part 3

PROFIBUS-DP.

The L2-DP protocol uses the functions specified in DIN 19245 Part 1 for

layers 1 and 2, and supplements these for the special requirements of

distributed I /Os.

The data exchange in a pure SINEC L2-DP bus system is characterized by

the master- (active station on the bus) slave (passive station on the bus)

relationship. The main purpose of such a SINEC L2-DP bus system is fast

data exchange between the master (PLC) and the distributed slave stations

(for example, I/Os of the ET200U station).

Because the L2-DP protocol is based on Part 1 of the PROFIBUS standard

and the hybrid bus access method it specifies, it also possible to operate

MASTER - MASTER communication in addition to the L2-DP MASTER

-SLAVE communication.

With SINEC L2-DP/PROFIBUS-DP the following configurations are possible:

➣Communication function of the DP MASTER class 1

The class 1 MASTER polls the slaves assigned to it cyclically and

handles the configured data exchange using its requester and

responder f unctions.

➣Communication function of the DP MASTERS, class 2

In SINEC L2-DP/PROFIBUS, a programming, diagnostic or

management device used for diagnostic and service functions is known

as a class 2 MASTER.

Distributed I/ Os (DP) B890 60 /02

Vol ume 1 11 - 4

➣Communication with other active PROFIBUS devices functioning

according to the standard DIN 19245 Part 1 and 2 on the bus. These

configurations are suitable for applications with low to middle

requirements in terms of system reaction times .

Passive

station on bus

DP master (class1)

- IM 308 B

- CP 5430 TF/CP 5431 FMS

DP master (class 2)

PG7xx with CP 5410 B

SINEC L2 bus

DPslave

Active

station on bus

OP20

DP slave

ET200U-DP

DP slave

S5 95U L2-DP

Fig. 11 .2 Bus Configuration with a SINEC L2-DP Application to PROFIBUS Stan dard

B8976060/02 Distributed I/Os (DP)

11 - 5 Volume 1

11.1.1 The SINEC L2-DP Interface for the CP 5430 TF/CP 5431FMS

Characteristics of the SINEC L2-DP interface of the CP 5430 TF/

5431 FMS:

➣The CP can only be operated as DP master, class 1 on the SINEC L2

bus.

➣The L2-DP interface of the CP functions in accordance with the

PROFIBUS s tandard DI N E19254, Part 3.

The L2-DP interface can be operated parallel to the FMS interface (CP

5431 FMS) or to the TF interface (CP 5430 TF ) (combined appli cations).

Passive

station on bus

Active

station on bus

SINEC L2 bus

DP slave DP slave

CP 5430 TF/CP 5431 FMS

als DP-Master (classe 1) CP 5431 FMS

DP slave

FMS

slave

CP 5431 FMS

Fig. 11 .3 Bus Configuration with SINEC L2-DP in a Multi-Master Application

Distributed I/ Os (DP) B890 60 /02

Vol ume 1 11 - 6

11.2 CP 5430 TF/CP 5431 FMS L2-DP Functions

The following SINEC L2-DP functions are implemented on the CP 5430

TF/CP 5431 FMS:

➣Assignment of parameters to the DP slave (Set_Prm_Request)

Using this function, the connected DP slave is assigned parameters

during the start up or restart phase of the DP system.

➣Reading out configuration data of a DP slave (Get_Cfg_Request)

This function allows configuration data to be read from a DP slave.

➣Configuration of a DP slave (Chk_Cfg_Request)

Using this function, the configuration data are transferred to the DP

slave .

➣Productive data exchange (Data_Exchange_Request)

This function handles the cyclic I/O data exchange between the DP

master (class 1) and the DP sl aves assi gned to it.

➣Send control command to the DP slave (Global_Control_Request)

This allows specific control commands to be sent to the DP slaves.

➣Read DP slave i nformation (Slave_Diag_Request)

This function allows the diagnostic data of a DP slave to be read out.

➣Read master diagnostic data information (Get_master_Diag_Response)

Using this function the diagnostic data stored on the CP (DP master,

class 1) belonging to the DP slaves assigned to it can be read by a DP

master (class 2).

B8976060/02 Distributed I/Os (DP)

11 - 7 Volume 1

With the exception of the functions that the user can execute using HDB

calls

– r ead DP slave diagnostic information and

– s end control command to DP s lave,

all the functions listed above run automatically on the CP when the L2-DP

service is activated.

Type of service

DP slave

service DP master

service

Data_Exchange

Slave_Diag

Set_Prm

Chk_Cfg

Global_Control

Get_Cfg

Get_Master_Diag

CP 5430 TF/CP 5431 FMS as

Requester Responder

Layer 2 service

used SSAP used DSAP used

SRD

SDN

Default SAP *

* As default SAP, SAP 61 must be configured in the COM

Network Parameters screen (see Section 6.5.3).

Table 11.1 DP Functio ns Supporte d by the CP and Their SAP Assignme nt

Distributed I/ Os (DP) B890 60 /02

Vol ume 1 11 - 8

11.3 Communication Between the DP Master and the DP

Slave Station

During the start-up phase, the CP checks whether the DP slave station is

operational by fetching diagnostic data.

This job is repeated (controlled cyclically using the DP polling list ) until the

slave responds with the requested diagnostic data. If the received

diagnostic data do not indicate any further errors, the DP slave is then

assigned parameters and configured.

If no error is signaled after the second request for diagnostic data, the CP

changes to t he mode "cyclic data exchange" with the DP slave.

DP master DP slave

Request slave diagnostic data 1st time

Send parameter assignment data

Fetch configuration data

Send configuration data

Request slave diagnostic data 2nd time

If no error was signalled

continue with cyclic

data exchange

Send output data to DP slave

Receive input data from DP slave

Cyclic data

exchange

phase

Start-up

phase

Repeat job until

the slave replies

Request

Response

Fig. 11 .4 Co mmu nicat ion be tw een DP Ma ster CP 5 430 T F/C P 5431 FM S and D P Sl ave

B8976060/02 Distributed I/Os (DP)

11 - 9 Volume 1

11.4 Basics of Data Transmission Using the DP Service

of t he CP

This section descri bes the funct ions of the DP service from the point of view

of the CPU control program.

With data transmission using L2-DP, the data exchange is handled via the

I/O area of the SIMATIC PLC.

This means the following:

➣The transmitted data are transferred to the CP by the control program

with STEP-5 commands directly or using the operating system function

PIQ (Output process image of the outputs).

➣The received data are fetched from the CP by the control program with

STEP-5 commands directly or using the operating system function PII

(Update process image of the inputs).

All the I/O bytes you want to use for sending and for receiving must be

identified as DP I/Os when the I/O areas are configured in the COM.

Communication with distributed I/Os is only permitted using the base

interface number (base SSNR) .

☞Simul taneous use of DP and GP is not possi ble

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 10

11.5 Updating the Input and Output Areas with the DP

Service

Depending on the selected mode, the CP distinguishes between two times

when the DP output bytes for transmission can be accepted:

➣FREE mode: decided by the CP (the STEP 5 control program has no

influence)

➣ CYCLE-SYNCHRONIZED mode: decided by the control program using

a send handling block call with job number 210.

Depending on the selected mode, the CP distinguishes between two times

when the DP input bytes received can be transferred:

➣FREE mode: decided by the CP (not influenced by the STEP 5 control

program)

➣CYCLE-SYNCHRONIZED mode: decided by the control program using

a RECEIVE handling block call with job number 211.

11.5.1 Consistency of the Input and Output Bytes with the DP

Service of the CP

The consistency of the DP I/O bytes depends on the selected mode.

➣FREE mode: guaranteed consistency of only one byte for the I/O DP

area.

➣CYCLE-SYNCHRONIZED mode: The data of the whole I/O DP area is

consistent. Whenever you want to work with consistent I/O areas, for

example, when using the analog I/Os in the ET200U, you must select

the CYCLE-SYNCHRONIZED mode.

B8976060/02 Distributed I/Os (DP)

11 - 11 Volume 1

11.5. 2 H ow the FREE Mode Functions

The following diagram illustrates how the FREE mode functions for output

bytes.

Expla nation of Fig . 11.5:

The output byte information to be transmitted is transferred to the output

area of the CP by the user program.

This takes place, either at the end of the PLC cycle using the "PIQ output

or by direct I/O access.

In the FREE mode, the DP polling list processing cycle alone decides when

the data in the output area of the CP are accepted for transmission on the

L2 bus.

PLC

Program

Output

area

PY1 : 7

Data information

transmitted on

the L2 bus

nth processing of

the DP polling

list

(n+1) processing

of the DP polling

list

PY1 : 3

PY1 : 5

PY1 : 00

PY1 : 5

L KH 0007

TPY 1

L KH 0005

TPY 1

L KH 0000

TPY 1

PY1 : 7

L KH 0003

TPY 1

mth PLC cycle

(m+1) PLC cycle

PY1 : 7

PY1 : 5

in CP

Fig. 11 .5 CP 5 430 TF/CP 5431 FM S Sends to L2 -DP Slav e

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 12

The following diagram illustrates how the FREE mode functions for input

bytes.

Expla nation of Fig .11.6:

The input byte information received from the L2 bus when processing the

DP polling list, is transferred to the input area of the CP after each DP data

exchange is completed.

Following the "update PII" function at the beginning of each CPU program

cycle or using direct access (for example, LPY) to the input bytes, the

received data can be processed further in the user program.

In the FREE mode, the DP polling list processing cycle of the CP alone

decides when t he data received f rom the L2 bus are transferred t o the input

area of t he CP.

PLC

Program

Input

area

PY1 : 4

Data information

transmitted on

the L2 bus

nth processing

of the DP polling

list

(n+1) processing

of the DP polling

list

PY1 : 9

L PY 1 PY1 : 1

mth PLC cycle

(m+1). PLC cycle

PY1 : 4

PY1 : 9

L IB 1

in CP

Fig. 11 .6 CP 5430 TF /CP 54 31 FMS Receives fro m L2-DP Slave

B8976060/02 Distributed I/Os (DP)

11 - 13 Volume 1

☞If DP bytes need to be transferred together (e.g. analog

values/counted values with word or double word length), the

FREE update mode must under no circumstances be

selected. With this mode, there is no guarantee that the DP

bytes which belong together are actually transferred in one

frame.

Essential features of the FREE mode:

➣Minimum cycle load (corresponds to the cycle load that would occur

simply by pluggi ng in the corresponding input/output modules..

➣Minimum load on the CP, since no HDB calls are required for

communication.

➣Simple programming of data exchange (single handling block call; HDB

SYNCHRON for the CP during start-up of the PLC).

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 14

11.5.3 How the CYCLE-SYNCHRONIZED Mode Functions

The following diagram illustrates how the CYCLE-SYNCHRONIZED mode

functions for output bytes.

Expla nation of Fig . 11.7:

The output byte information to be transmitted is transferred to the output

area of the CP by the user program.

This transfer is made at the end of the PLC cycle using the "output PIQ"

function, or as shown in the diagram, by direct I/O access.

PLC

Program

Output

area

PY1 : 7

Data information

transferred on

the L2 bus

HTB-SEND

210 CALL

nth processing

of the DP polling

list

PY 1:

(n+1) processing

of the DP polling

list

(n+2) processing

of the DP polling

list

PY1 : 7

PY1 : 9

PY1 : 1

PY1 : 8

L KH 0007

TPY 1

L KH 0008

TPY 1

L KH 0009

TPY 1

HTB-SEND

210 CALL

L KH 0001

TPY 1

in CP

Fig. 11 .7 CYCL E-SYNCHRONIZED Mod e: Ma ste r Sends to Slave

B8976060/02 Distributed I/Os (DP)

11 - 15 Volume 1

In the CYCLE-SYNCHRONIZED mode, all the data located in the output

area of the CP are accepted and buffered when the HDB send 210 is

called. At the beginning of the next DP polling list cycle, this data is

transmitted to the connected DP slaves.

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 16

The following diagram illustrates how the CYCLE-SYNCHRONIZED mode

functions for input bytes.

Expla nation of Fig . 11.8:

The input byte information received from the L2 bus when processing the

DP polling list is buffered by the CP after it completes the DP polling list

cycle and transferred completely to the input area of the CP with the next

HDB RECEIVE 211 call. After the "update PII" function at the beginning of

every program cycle of the CPU or by means of direct access (for example,

LPY) to the input bytes, the received data can be further processed in the

user program.

PLC

Program

PY1 : 0

Data information

received on the

L2 bus

HDB-RECEIVE

211 CALL

PY1: 0

PY1: 10

HDB-RECEIVE

211 CALL

PY1: 9

PY1 : 10

PY1 : 9

Input

area

PY1 : 0

PY1 : 10

PY1 : 7

PY1 : 9

nth processing

of the DP

(n+1) processing

of the DP

in CP

polling list

Fig. 11 .8 CYCLE-SYNCHRONIZED Mode: Master Receives from Slave

B8976060/02 Distributed I/Os (DP)

11 - 17 Volume 1

In the CYCLE-SYNCHRONIZED mode, you as user decide when the DP

input and output data is accepted or transferred by the CP by calling the

HDB checkpoints SEND 210/RECEIVE 211.

As can be seen in Figs. 11.9 and 11.10, in the CYCLE-SYNCHRONIZED

mode for DP, the processing of the DP polling l ist and the calls for t he HDB

checkpoints (PLC cycle) are independent of each other.

☞The processing of the DP polling list in the

CYCLE-SYNCHRONIZED mode is only started after the first

call of one of the HDB checkpoints (SEND 210/RECEIVE 211).

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 18

Relationship between the HDB SEND 210 call and DP polling list cycle

The information transferred to the output area of the CP with the HDB

SEND 210 call, is only transferred to the bus as allowed by the processing

of the DP polling list.

DP polling list processing

PLC program processing

CPU CP 5430 TF/CP 5431 FMS L2 bus

Call HDB SEND 210

(with data information "X")

Call HDB SEND 210

(with data information "A")

Call HDB SEND 210

(with data information "B")

Call HDB SEND 210

(with data information "C")

Call HDB SEND 210

(with data information "D")

Transmitted

data information "X"

Transmitted

data information "C"

DP polling list cycle n+2

DP polling list cycle n+1

DP polling list cycle n

Fig. 11 .9 Relationship Between HDB SEND 210 Call and DP Polling List Cyc le

B8976060/02 Distributed I/Os (DP)

11 - 19 Volume 1

Relationship between the HDB RECEIVE 211 call and the DP polling

list cycle

The data information received during the processing of the DP polling list is

only transferred to the input area of the CP at the end of the pol ling cycle.

DP polling list processing

PLC program processing

CPU

CP 5430 TF/CP 5431 FMS L2 bus

Call HDB RECEIVE 211

(with data information "A") Received

data information "B"

DP polling list cycle n+1

Call HDB RECEIVE 211

(with data information "A")

Call HDB RECEIVE 211

(with data information "A")

Call HDB RECEIVE 211

(with data information "B")

Received

data information "A"

Received

data information "C"

DP polling list cycle n

DP polling list cycle n+2

Fig. 11 .10 Re lation sh ip Betw een HDB R ECEIVE 211 Call an d DP P ollin g Lis t Cycle

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 20

The DP update times are in no way connected to the communications

taking place on the L2 bus.

The data exchange with the L2-DP service between the CP and the L2-DP

slaves is constant (cyclic according to the DP polling list entry) regardless of

the call cycle of the handling blocks SEND 210 and RECEIVE 211. To start

the DP polling list processing in the CYCLE-SYNCHRONIZED mode, at

least one HDB checkpoint (SEND 210/RECEIVE 211) must be called.

Using the status word bits 8 - 11 of the HDB checkpoint, diagnostic

information can be analyzed.

SEND-HDB

A-NR 210

RECEIVE-HDB

A-NR 211

Read inputs

Write outputs

I/O area

of the CP 5430 TF/CP 5431 FMS

Processing the

DP polling list

PLC cycle L2 bus

User

Fig. 11 .11 Function of the CYCLE-SYNCHRONIZED Mode

B8976060/02 Distributed I/Os (DP)

11 - 21 Volume 1

11.6 Configuring

The PG package SINEC NCM with COM 5430 TF/COM 5431 FMS is used

to configure the DP functions.

The screens you require for configuring are provided by SINEC NCM as

shown in Fig. 10.12.

➣Assignment/reservation of the I/O areas required for the DP service

➣Assignment of parameters to the DP slaves to be addressed

➣Entry of the DP polling list in the DP editor

➣Documentation and Test

☞When you transfer a database CP->FD, the DP slaves

configured in the database are not entered in the network

table. The DP slaves can be entered by entering the lines

individually in the DP editor (Section 11.6.3).

= Init Edit ...

SINEC NCM

I/O Areas DP Editor

Edit

Menu item

Dokumentation and

Test in Chapter 14

dealt with in separate chapters

I/Os

Menu item

Assign parameters

to DP slave

Fig. 11 .12 DP Configuration

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 22

11.6.1 I/O Areas

The I/O areas used with the DP service are selected in the I/O area editor

screen.

☞Simul taneous use of GP/ZP and DP is no t po ssible

Simul taneous use of GP/CI and DP is not possible.

The I/O area editor is different for the CP 5430 TF and CP 5431 FMS.

In the DP Update (CP 5431 FMS) or ZP/DP Update (CP 5430 TF), you

select when the I/O between the CPU and CP are updated.

Cycle-

synchronized: Updating at the call points of the HDBs SEND 210 and

RECEIVE 211 (cycle checkpoint). The DP polling list

processing is only started after the first HDB checkpoint

has been called (SEND 210/RECEIVE 211).

Input/Output (I/O) Areas:

L2 station address:

OUTPUT AREAS:

INPUT AREAS:

GP update:

GP Sender :

OK SELECT

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

1 2 3 4 5 67 9101112 131415168

/DP STA: GP STA: GP END: /DP END:

GP STA: GP END:

PY 100

PY 119

HELP

CYCLE-SYNCHRON

/DP STA: /DP END:

CP type:

Source: (EXIT)

ZP/DP update:

Fig. 11 .13 In put/ Ou tput A reas Scre en

B8976060/02 Distributed I/Os (DP)

11 - 23 Volume 1

Free: The point at which t he I/O areas are updated is decided

by the CP.

Input areas:

(CP 5431 FM S)

CI/DP STA:

(CP 5430 TF)

ZP/DP STA:

Beginning of the (continuous) input area for the

distributed I /Os.

Range of values: PY0-254, OY0-254. Only even

addresses al lowed.

(CP 5431 FM S)

CI/DP END:

(CP 5430 TF)

ZP/DP END:

End of the (continuous) input area for the distributed

I/Os.

Range of values: PY1-255, OY1-255. Only odd

addresses al lowed..

Output areas:

(CP 5431 FM S)

CI/DP STA:

(CP 5430 TF)

ZP/DP STA:

Beginning of the (continuous) output area for the

distributed I /Os.

Range of values: PY0-254, OY0-254. Only even

addresses al lowed.

(CP 5431 FM S)

CI/DP END:

(CP 5430 TF)

ZP/DP END:

End of the (continuous) output area for the distributed

I/Os.

Range of values: PY1-255, OY1-255. Only odd

addresses al lowed.

Output fields:

L2 station

address: The bus address of the station of the currently selected

database is displayed here.

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 24

Functi on keys:

OK The "OK" key enters the data. If the module file does

not yet exist, it is set up when you confirm the entries.

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select values from the list with the cursor keys and

enter them in the field with the return key.

☞The input or output area must al ways begin with an even byte

number and must always end wit h an odd byte number.

Note:

The fields remain empty if no input or output areas are required for the

distributed I /Os.

The input area/output area for DP must not exceed a maximum of 256

bytes.

☞The I/O area reserved for the DP must not be used for I/O

modules! Online modification of the DP area is only

recogn ized by the C P af ter POWER OFF/POW ER ON!

B8976060/02 Distributed I/Os (DP)

11 - 25 Volume 1

11.6.2 Assigning Parameters to DP Slaves

For each DP slave to be addressed with the DP service, parameters must

be assigned using the screen "Edit->I/Os->DP Slave Parameters". This

information such as "Slave L2 address" and "Slave Vendor Identification", is

required later separately for each DP slave during data exchange. 32 DP

slaves can be assigned.

DP slave parameter assignment can only be called when no CI (CP 5431

FMS) or ZP (CP 5430 TF) has been configured and an I/O area has been

reserved for DP.

Once you have entered more than 25 bytes of user assigned data, the

symbol ">" appears at the end of the field. To enter more than 25 bytes,

you must change to the next screen User-Specific Parameters by selecting

F6 USER PAR.

DP Slave Parameter Assignment

Slave L2 address

Slave name

OK SELECT

HELP

USER PAR

Check slave sync mode

Check slave freeze mode

Slave watchdog time

:OFF

OFF

Slave vendor ID

Slave group ID

0000

User-selectable data : Length : 0

00000000

CP type:

Source: (EXIT)

+1 - 1 NEW DUPLICATE DELETE

Fig. 11 .14 DP Slave Param eter Assignment Scree n

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 26

The second slave parameter screen (Fig. 11.14) selected with F6 USER

PAR.

Input fi elds :

Slave L2 address: Here, you enter the L2 bus address of the DP slave

(Range of v alues: 1- 124).

Slave vendor ID: Here, the four-digit vendor identification listed in the

device documentation of the slave must be entered for

the DP s lave.

Slave group ID: The group identifier specified here is only relevant when

jobs will be processed using the global control function

with Sync/Unsync or Freeze/Unfreeze.

User-Specific Parameters

HELP

User-selectable data : Length : 0

CP type:

Source: (EXIT)

Fig. 11 .15 DP Slave Para meter Assignmen t Screen II

B8976060/02 Distributed I/Os (DP)

11 - 27 Volume 1

The group identifier makes it possible to distinguish the followi ng 8 groups.

If no group identifier was specified at the HDB call for the global control job

(all bits set to "0"), the global control job is sent and executed by all DP

slaves capable of the Sync and/or freeze mode.

If the group identifier is not zero, the conditions for execution are as follows:

– S ync and/or freeze mode must be supported by the DP slave.

– At least one group of the global control job and of the group

identifi er must match.

Slave name: Here, it is possible to assign up to 10 ASCII characters

long to the slave for documentation purposes.

Check slave

sync mode/

Check slave

freeze mode:

If you select the ON mode here, the CP checks

whether or not the slave supports the Sync. or Freeze

jobs using the parameter assignment frame during start

up.

1st group

2nd group

3rd group

8th group

0 0 0 0 0 0

Fig. 11 .16 Group Identifier Structure

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 28

Slave watchdog

time: With this parameter, you decide whether or not the

slave operates on the L2-DP bus with watchdog

monitoring ON or watchdog monitoring OFF.

The monitoring time itself is set only once in the DP

editor screen and applies to all connected DP slaves.

The watchdog monitoring on the DP slave is used to

monitor the DP master.

Each time a frame is received from the DP master, the

watchdog monitoring is restarted in the DP slave. If the

master fails, this is recogni zed by the DP slave after the

monitoring time elapses and the slave changes to a

safe state (for example, all outputs are reset).

User-selectable

data: In this field (which can also be selected in the next

screen with F6 USER PAR) you can specify the

user-specific data contained in the device

documentation provided this is permitted for the DP

slave. From 0 to 235 bytes (0: none) of user assignable

data can be specified.

Output fields:

Length: Here, the length of the user-specific data entered is

displayed i n byt es.

Functi on keys:

USER PAR Change to the next screen to enter the user-specific

parameters.

OK The OK function key enters the data.

B8976060/02 Distributed I/Os (DP)

11 - 29 Volume 1

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select values from the list with the cursor keys and

enter them in the field with the return key.

Once a slave has had parameters assigned with F7 OK, the following

function keys are available in the screen:

+1 Page forwards in the DP slave parameters (only if more

than one DP slave has had parameters assigned).

-1 Page backwards in the DP slave parameters (only if

more than one DP slave has had parameters

assigned).

NEW Assign parameters to new DP slave .

All the input fields in the screen are deleted or display

default values.

DUPLICATE Duplicate DP slave parameter assignment for new DP

slave.

With the exception of the slave L2 address, slave name

and input/output areas (in t he DP editor Section 11.6.3),

all the values entered for the open DP slave are

adopted .

DELETE All the parameters of the selected DP slave are

deleted.

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 30

11.6.3 DP Edit or

Once you have reserved the input/output areas for distributed I/Os and have

entered the parameter data for the slaves to be addressed, you must now

assign part of the required I/O area of the CP to each DP slave using the

DP editor.

The DP editor can only be called when at least one DP slave has been

configured.

The fields, Watchdog time, Min. polling cycle time and Clear DP can only

be modified after selecting function key F3 GLOB.DAT. With F3 LIST, you

exit this modification mode.

Edit - DP Editor

Watchdog time:

Output areas:Input areas:

OK SELECT

HELP

Min. poll. cyc. time: 100 x 10 ms

Name from: PB 0 to: PB 255 from: PB 0 to: PB 255

PAGE +

LINE +

PAGE -

LINE - GLOB.DAT. DELETE

Clear DP: NO

CP TYP:

Quelle: (ENDE)

200 x 10 ms

Slave

L2 address

Fig. 11 .17 DP Editor Screen

B8976060/02 Distributed I/Os (DP)

11 - 31 Volume 1

Input fi elds :

Input areas: Here, you assign the input bytes of the configured DP

slaves to the reserved input area of the CP.

The permitted range of values is from one byte (from

PYxxx to PYxxx, xxx = same address) to the I/O byte

limit specified in the I/O area editor for the I area (up to

a maximum of 242 bytes). If the DP slave does not

have an I area, these fields remain empty. Multiple

assignment for different DP slave stations is not

possible.

Output areas: Here, the output areas of the configured DP slaves are

assigned to the Q area of the CP.

The permitted range of values is from one byte (from

PYxxx to PYxxx, xxx = same address) to the I/O byte

limit specified in the I/O area editor for the Q area (up

to a maximum of 242 bytes). If the DP slave does not

have a Q area, these fields remain empty. Multiple

assignment for different DP slave stations is not

possible.

Watchdog

time: The time specified here is the timeout value for all DP

slaves with activated watchdog monitoring ("DP slave

parameter assignment" screen).

The watchdog monitoring time, transferred to the DP

slave during the start-up phase in the parameter

assignment frame is used to monitor the DP master.

Each time a frame is received from the DP master, the

watchdog monitoring is restarted in the DP slave.

If the master fails, this is recognized by the DP slave

after the monitoring time elapses and the slave

changes to a safe state (for example, all outputs are

reset).

The time set here, is directly related to the token

rotation and the pr ocessing t ime of the DP pol ling list.

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 32

Min. polling

cycle time: Here you select the time intervals at which the DP

polling list is processed.

Once all the jobs in the DP polling list have been

executed, the processing of the DP polling list is only

restarted after this cycle time has elapsed.

Setting the times:

For the configured times:

- Minimum polli ng cycle time

- Highest min. s lave interval

- Watc hdog time

of the slaves, the following four condit ions must be met:

(1) Min polling cycle time >= 2 x highest min.. slave

interval

(2) 10 ms <= min. Polling cycl e time <= (watchdog-

time - 30 ms)

(3) Watchdog time <= 9900 ms

(4) Watchdog time must be di vi si ble by 100.

The configured min. polling cycle time is also checked

by the CP to make sure that the CP can operate

correctly with the time.

The minimum value depends directly on the number of

active slaves and corresponds to the lowest min. polling

cycle time. If you select a value below this when

configuring, the error LED flashes to indicate a DP

slave parameter assignment error (see Section 4.1.1.2).

Note:

- All three times apply to all slaves!

- The I/O list for the configured slaves can be re-called

with (F3) LIST.

B8976060/02 Distributed I/Os (DP)

11 - 33 Volume 1

Highest min.

slave interval The time specified here is the highest value of the

minimum slave interval of all DP slaves to be

processed using the DP polli ng l ist.

The min. slave interval of a DP slave is the time the

slave requires to process the last polling frame

received. Following this, the slave is ready to receive

the next polling frame.

The value of the min. slave interval can be found in the

documentation for the particular slave.

Clear DP: Yes: The output data of the CPU are only transferred

when all the DP slaves are in the cyclic data transfer

phase. Otherwise, all the output data are sent as "0".

No: The output data of the CPU are transferred as

soon as the slave is in the cyclic data transfer phase.

Output fields:

L2 address and

name: Here, all the configured L2-DP slaves are listed with

their bus address and name.

Functi on keys:

LINE + Move display one line forwards.

SHI FT F1

PAGE + Move display one page forwards.

LINE - Move display one line backwards.

SHI FT F2

PAGE - Move display one page backwards.

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 34

GLOB.DAT. Change to the fields watchdog monitoring time, min.

Polling cycle time and clear DP.

DELETE Delete the input and output areas of a L2-DP slave.

OK With the OK function key, you enter the data. If the

module file does not yet exist it is created after you

press this key.

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select values from the list with the cursor keys and

enter them in the field with the return key

This function key appears only after you press the function key F3

GLOB.DAT.:

LIST Change to the I/ O area ent ries f or t he DP

slaves.

Assignment of the DP I/O areas to the I/O modul es in the slave

The following rules apply:

➣The selected I (input) area is assigned to the input modules beginning

at the left wit hout gaps.

➣The selected Q (output) area is assigned to the output modules

beginning at the left wit hout gaps.

B8976060/02 Distributed I/Os (DP)

11 - 35 Volume 1

ET200U-DP example of a configuration

The following I/O assignments were made with the help of the COM for the

ET200U-DP stat ion 10 described below:

I/O area editor:

DP-mode: cycle-synchronized

Input area DP STA: PY100 Input area DP-END: PY 107

Output area DP STA: PY80 Output area DP-END: PY85

DP-Editor:

Station 10, Input area: PY100 to 107/Output area PY80 to PY85

ET200U-DP

Station 10

Occupied address area (bytes)

I peripheral byte

address assignment

Q peripheral byte

address assignment

1124114

PY80

PY100

PY101

PY81

PY102 PY103

PY82

PY83

PY84

PY85

PY104

PY105

PY106

PY107

2) The bytes be handled in the user program

as being word size (e.g. PY82 and PY83 = PW82).

This is only guaranteed in the "cycle-synchronized" mode

1) Number of channels used can be selected

In this case 2.

PS IM

318B DQ

440 DQ

441 DI

422 AQ

470 DI

430 DI

421 AI

464 empty

Table 11.2 ET200U-DP Example of a Configuration

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 36

11.6.4 Example of using the DP service

The following example describes the use of the cycle-synchronized DP.

Task:

Three ET200U-DP station are to be connected to a programmable controller

(S5 115U) as distributed I/Os using the DP service.

The ET200U-DP stations have the following data:

Vendor identification: 8008H

Sync mode: OFF

Freeze mode: OFF

Watchdog: ON

1. L2 station

L2 bus address: 20

I inputs: 3xDI each with 8 bits

Q outputs: 2xDQ each with 8 bits

2. L2 station

L2 bus address: 21

I inputs : 2xDI each with 8 bits

Q outputs: 1xDQ each with 8 bits

3. L2 station

L2 bus address: 22

I inputs: 1xDI each with 8 bits

Q outputs: 1xDQ each with 8 bits

B8976060/02 Distributed I/Os (DP)

11 - 37 Volume 1

The distributed I/O bytes will be assigned to the input addresses from

PY100 and the output byte addresses from PY108 .

This means a DP input area from PY100 - PY105 and a DP output area

from PY108 - PY111 must be reserved in the I/O area editor!

L2 bus address I/O bytes of the

ET200U-DP station CP 5431

3 x DI

2 x DQ

2 x DI

1 x DQ

1 x DI

1 x DQ

PY100-102

PY108-109

PY103-104

PY110

PY105

PY111

Table 11.3 L 2 I/O A ssi gnme nt

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 38

Configuring with COM 5430 TF/COM 5431 FMS

To assign parameters to the CP 5430 TF/CP 5431 FMS for the DP service,

several steps are required:

➣First, the basic configuration of the CP must be specified. This is

described in detail i n Chapt er 6.

➣After the basic configuration, the input/output area for the I/Os used

must be specified.

➣Using "DP slave parameter assignment", you specify the parameters for

each DP slave to be addressed.

➣Finally, in the "DP editor" screen, the I/Os intended for data exchange

must be assigned to the individual DP slaves.

To be able to use the practical example of the DP service, proceed as

follows (see also Chapter 16).

➣Transfer the following COM 5430 TF/COM 5431 FMS database file to

the CP you are using.

– When using the CP 5430 TF under the network file

DPO@@NCM.NET the file ODPTLN1.115.

– When using the CP 5431 FMS under the network file

DPQ@@NCM.NET, the file QDPTLN1.115.

➣Transfer the STEP 5 file DP115UST.S5D to the PLC you are using

(S5-115U). The example files are on the COM application file diskette.

B8976060/02 Distributed I/Os (DP)

11 - 39 Volume 1

11.7 L2-DP Diagnostics with the User Program

11.7.1 Overview

To allow you to monitor the data exchange with the configured DP slaves

from the user program, the CPs prov ide the following functions:

➣Read out DP station list

The DP station list provides information about the status of all slaves

and has a length of 16 bytes (128 bits). Each bit of the station list

corresponds to one of the possible bus addresses of a DP slave station.

Meani ng of the bit s

76543210

120 127 *)

7654321076543210

012345678 9 10 11 12 13 14 15

2 - 14

16 - 119

Byte

Bit

Station

address

*) The first and last two bits in the station list are not relevant, since the permitted

station address on the L2 bus must be in the range 1-125

124

Fig. 11 .18 Str uct ure of the DP Stat ion Li st

Bit code Meaning

0 Station is in the cyclic dat a transfer phase or the station

address is not assigned.

1 Station is not in the cyclic data transfer phase

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 40

All the bits of the DP slave stations, for which there was no configura-

tion in t he DP editor, (-> no input/output areas configured), are identifi ed

with "0". These DP slave stations are known as passive DP stations

and are ignored in the station list.

This also applies to DP stations with which cyclic data exchange is

running free of error.

For all DP slave stations not in the cyclic data transfer phase, the DP

station bit is set to "1"

This is the case when the DP slave station does not acknowledge on

the bus or i s not yet completel y ini tialized.

When a DP station is first initialized, the DP station bit is kept at "0"

during the initial ization.

➣Read out DP diagnostic list

The DP diagnostic list indicates whether there are any new diagnostic

data from the DP slaves and has a length of 16 bytes (128 bits).

Each bit of the DP diagnostic list corresponds to one of the possible

bus addresses of the DP slave stations.

76543210

120 127 *)

7654321076543210

012345678 9 10 11 12 13 14 15

2 - 14

16 - 119

Byte

Bit

Station

address 124

*) The first and last two bits in the station list are not relevant, since the permitted

station address on the L2 bus must be in the range 1-125

Fig. 11 .19 Str uct ure of the DP Diagno st ic Lis t

B8976060/02 Distributed I/Os (DP)

11 - 41 Volume 1

Meani ng of the bit s

Bit coding Meaning

0 Station does not exist or there are no new di agnostic dat a .

1 There are new diagnostic data .

All the bi ts of the DP slave stations for whic h there are no new diagnos-

tic data or which are not configured and all the passive stations are

identif ied by "0" in the diagnostic list.

If there are new diagnostic data from a DP station, the DP station diag-

nostic bit is set to "1".

When the DP station is first initialized, the DP diagnostic bit is set to

zero.

The new diagnostic data reported by the slave can be requested from

the slave using the function "single diagnostics".

➣Read out DP slave single diagnostics

With this function, further diagnostic data about the specific slave can

be requested.

The information provided consists of the followi ng:

The general DP slave diagnostic data:

– S tation status 1 - 3

– Master address (address of the DP-master (class 1), which

assigned param eters to the DP slave) .

– V endor ID of the DP slave.

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 42

The extended DP slave diagnostic data:

– Dev ice-related diagnostics

(Vendor and device-specifi c diagnostic data)

– I D-relat ed diagnostics

(Configuration- dependent list ing of the I/O channels) .

All I/O channels for which diagnosti cs are available are marked.

– Channel- related di agnostics

(reason for diagnosed channels).

B8976060/02 Distributed I/Os (DP)

11 - 43 Volume 1

Structure of the diagnostic data according to the DP standard

Byte 1

Station status 1

Station status 2

Station status 3

Master address

Vendor ID

*) can be extended to max. 242 bytes

General DP slave

diagnostic data

Other DP slave-specific

diagnostic data, such as:

- device-related

- ID-related

- channel-related

diagnostics

Fig. 11 .20 Str uct ure of the Sing le D P Slav e Di agno stic D ata

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 44

11.7.2 Examples of Practical Applications

11.7.2.1 Reading out the DP stat ion list

Whenever t he cyclic data exchange is disturbed with at least one DP slave

station, the DP station list can be read out with the HDB call RECEIVE

A-NR: 202.

If there is no fault/error, i.e. all DP slave stations are in the cyclic data

transfer phase, the HDB RECEIVE 202 call is blocked with the ANZW bit

"Receive possible".

B8976060/02 Distributed I/Os (DP)

11 - 45 Volume 1

DP Group messages with HDB Receive 202 ANZW

The DP ANZW bits 8-11 of the HDB Receive job 202 create the following

DP group message:

To update the group messages bits 8 - 11 in the ANZW of the HDB job

202, it is sufficient to call HDB-CONTROL A-NR: 202.

Bit 11 10 9 8 of ANZW/A-NR: 202

0 = no error, all the configured DP slaves are in

the data transfer phase

1= at least one DP slave is not in the data

transfer phase

Cause of error, what to do:

To find out which slave(s) is affected, you must

read out the DP station list using

HDB-RECEIVE A-NR: 202.

Cause of error, what to do:

use the special service "DP station diagnostic list"

HTB-A-NR: 209, to read out the diagnostic list

Using the special service "Read single DP slave diagnostic

data", HTB-A-NR: 209, it is possible to obtain an accurate

error analysis for every slave.

Possible causes of a group message are;

- DP slave, does not reply on the bus (not connected,

switched off)

0 = cyclic global control job not sent

1= cyclic global control job sent

0 = there are no new diagnostic data for DP slave

1= there are diagnostic data for a DP slave

0 = no timeout occurred during processing of the DP polling list

1= a timeout occurred during processing of the DP polling list

The selected monitoring time for processing the polling

list was exceeded.

Possible causes of this error message:

- problems on the bus

- delayed DP polling list processing due to parallel

processing of other acyclic services on the CP.

To find out which slave(s) is affected, you must

Fig. 11 .21 DP G rou p Me ssag es Usin g t he HD B Rec eive 2 02 A NZW

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 46

Programming example of reading out the DP station list and updating

DP group messages

FB202 "STAT-LIS" makes all DP group messages available by means of bit

formal operands .

If a slave leaves the cyclic data transfer phase, the DP station list is read

and saved in data block DB202 from DW0 onwards.

Description of the FB202 "STAT-LIS" formal operands:

STAF : DP station failed

DIAG : New DP diagnostic data exist

ZYGC : Cyclic global control job active

TOUT : Timeout processing the DP polling list

Function block FB202 with the corresponding data block DB202 for use in a

CPU of the S5-115U series is in the STEP 5 file STATIOST.S5D on the

COM/application example diskette.

B8976060/02 Distributed I/Os (DP)

11 - 47 Volume 1

11.7.3 Readi ng Out the DP Diagnosti c List

The message that a slave has new diagnostic data causes the

corresponding bit in the DP diagnostic list to be set to "1". As soon new

diagnostic data exist for at least one connected slave, this is indicated in

the group status ANZW HDB/A-NR202 (DP station list) bit 9.

Using the HDB special service, A-NR209, the diagnostic list can be read

out. When the diagnostic list is read out by the user program, the currently

set diagnostic message bits and the group diagnostic status bits are reset

on the CP.

The DP diagnostic list can always be read out regardless of group bit 9

(HDB job 202).

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 48

Example of a program for reading out the DP diagnostic list

The following figure shows the sequence of the HDB special service A-NR

209 for r eading out the DP diagnos tic l ist.

Expla nation of Fig . 11.22:

The "DP diagnostic list" special service is triggered with SEND A-NR: 209

and acknowledged with RECEIVE A-NR: 209. The acknowledgment is

made with the local CP data.

S5-Adr.

ANZW

ANR

SSNR

PAFE

Job

L2-DP bus

SEND

A-NR:

209

S5-Adr.

ANZW

ANR

SSNR

PAFE

RECEIVE

Anzw = job_complete_without_error

(...4H)

Control program

Job

field

Anzw = job_active receive possible (...3 ) H

A-NR: 209

Ack.

Data

Anzw = job_active (...2H)

Fig. 11 .22 Se quen ce of HDB S pec ial Ser vice, A-NR : 20 9 for Rea d Out DP Dia gnos tic List

B8976060/02 Distributed I/Os (DP)

11 - 49 Volume 1

Structure of the job field "DP diagnostic list"

Struct ure of t he Acknowl edgment fiel d for "DP diagnost ic list "

1st byte

2nd byte

3rd byte

4th byte

Length of the job field in bytes

Diagnostics request

DP station diagnostics list

not occupied with this function

Job type

Diagnostics type

Fig. 11 .23 Str uct ure of the Jo b Field "D P Diag nost ic L ist"

1st byte

2nd byte

3rd byte

18th byte

Length in bytes

Acknowledgment

Diagnostics list

- with negative ack. -> 2

- with positive ack. -> 18

DP station diagnostics list for

stations 1 - 125

00 hex ok

01 hex syntax error in job field

02 hex error in HDB handling

0B hex CP job cannot be executed, since the DP polling

list processing is in the STOP mode

Fig. 11 .24 Structure of the Acknowledgment for "DP Diagnostic List"

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 50

Example of programming for reading out the DP diagnostic list

FB209 "DIAG-LIS" requests the diagnostic list from the CP with the special

service HDB A-NR. 209 and enters it in DB209 from DW4 onwards (incl.

acknowledgment).

Function block FB 209 signals that the job has been done by resetting the

assigned trigger bit "ANST".

Function block FB 209 with the corresponding data block 209, for use in a

CPU of the S5-115U series is in the STEP 5 file DIAG@@ST.S5D on the

COM/Application exampl es diskett e.

11.7.4 Request Single DP Station Diagnostic Data

With the special service "single DP station diagnostics", you can request DP

slave-specifi c diagnostic data from a slave connected to the bus.

The diagnostic data of a single DP slave, can be requested from a DP

slave at any time regardless of the "New diagnostic data" message in the

DP diagnostic list .

En entry in the DP diagnostic list indicating that new diagnostic data exist is

deleted when the diagnostic data are read.

B8976060/02 Distributed I/Os (DP)

11 - 51 Volume 1

11.7.5 Example of a Program for Requesting Single DP Station

Diagnostics

The following figure shows the sequence of the HDB special service, A-Nr:

209 singl e DP station diagnostics.

Expla nation of Fig . 11.25:

The special service "single DP station diagnostics" is triggered with SEND

A-NR: 209 and acknowledged with RECEIVE A-NR: 209.

It is acknowledged with the diagnostic data requested from the DP slave.

S5-Adr.

ANZW

ANR

SSNR

PAFE

Job

L2-DP bus

SEND

A-NR:

209

S5-Adr.

ANZW

ANR

SSNR

PAFE

RECEIVE

Anzw = job_complete_without_error

(...4H)

Control program

Job

field

Anzw = job_active (...2H)

A-NR: 209

Ack.

Data

DP slave

Request diagnostic

data

Acknowl. with

diagnostic data

Anzw = job_active receive possible (...3 ) H

Fig. 11 .25 Sequen ce of HDB Sp ecial Service, A-Nr: 209 for Single DP Statio n Diagn ostic s

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 52

Struct ure of t he job field "sin gle DP stat ion diagnost ics"

1st byte

2nd byte

3rd byte

4th byte

Length of job field in bytes

Diagnostics request

Single DP diagnostics

Station address (e.g. 3)

Job type

Type of diagnostics

Fig. 11 .26 Structure of the Job Field "Single DP Station Diagnostics"

B8976060/02 Distributed I/Os (DP)

11 - 53 Volume 1

Structure of the acknowledgment field for "single DP station

diagnostics"

Causes of errors in the acknowledgment 0AH "DP slave configuration

error detected by DP master when configuring the DP slave" are as follows:

– Configured I/O area for the DP slave does not match the DP slave

I/O configuration or

– DP slave works with consistent I/O areas, but the free mode is

configured on the CP.

1st byte

2nd byte

3rd byte

4th byte

8th byte

9th byte

34th byte *

5th byte

7th byte

6th byte

* can be extended up to 244 bytes

Length in bytes

Acknowledgment

Station status

byte 1

Station status

byte 2

Master address

Station status

byte 3

Ident_number

Extended

diagnostics

- with negative acknowl. -> 2

- with positive acknowl. 8 - 244

Structure of thestation status bytes

Vendor ID, dependent of DP slave type

Bus address of the DP master, which assigned

parameters to the slave

DP slave-specific diagnostic information

00 hex ok

01 hex syntax error in job field

02 hex error in HDB handling

03 hex CP not in logical ring

04 hex slave station not configured

05 hex slave nor replying (failed)

0A hex DP slave configuration error detected by master

when configuring the DP slave

0B hex DP polling list processing is in the

STOP mode

Fig. 11 .27 Structure of the Acknowledgment Field for "Single DP Station Diagnostics"

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 54

Structure of the stati on status bytes

Stat ion status byt e 1

Bit no. Meaning Explanation

7Master_Lock The DP slave was assigned parameters

by a different DP master.

This bit is set by the CP (DP master)

when the master address in the byte

is not FFH and not the CP bus

address.

6 Parameter_Fault The last parameter frame received

contained an error.

5 Invalid_Slave_ This bit is set by the CP (DP master)

when no plausible response was

received from the slave.

4 Not_Supported The requested functions are not

supported by the DP slave

3 Ext_Diag Bit = 1 means: slave-specific diagn.

2Slv_Cfg_Chk_Fault Configuration data received from

master do not match the configuration

expected in the DP slave.

1 Station_Not_Ready The DP slave is not ready for the

data exchange.

0 Station_Non_Existent This bit is set by the CP (DP master).

Response

Ext_Status-Message data exist.

Bit = 0 means: slave signals own

status, with or without extended

diagnostic information.

The DP slave does not reply on the bus.

Table 11.4 Statio n Status Byte 1

B8976060/02 Distributed I/Os (DP)

11 - 55 Volume 1

Stat ion status byt e 2

If bit 1 and bit 0 are set at t he same time, bit 0 has the higher priority.

Bit no. Meaning Explanation

7Deactivated

6 Reserved

5 Sync_Mode

4 Freeze_Mode

3 WD_On

1 Stat_Diag

This bit is set by the CP (DP master)

when the DP slave no longer exists

Set by the DP slave after receiving

sync command.

Watchdog on (response monitoring)

DP slave is active (bit = "1").

The slave sets this permanently to

Static diagnostics

If this bit is set, the DP master must

fetch diagnostic data from the

DP until the DP slave can make

valid network data available so that

this bit can be reset.

Prm_Req This bit is set by the DP slave when it

has new parameters assigned and

must be configured.

"1".

in the DP pollin list.

Status_From_Slv

Set by the DP slave after receiving

freeze command.

Table 11.5 Statio n Status Byte 2

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 56

Stat ion status byt e 3

Structure of the byte "master address"

Bit no. Meaning Explanation

6 - 0 reserved

If this bit is set, there is more

diagnostic information than specified

in the extended diagnostic data.

Ext_Diag_Data

_Overflow

Table 11.6 Station St atus Byte 3

Bit 01234567

- Station address of the DP master which

assigned parameters to the slave

- If the DP slave has not yet had parameters

assigned, FFH is entered here.

Fig. 11 .28 Struct ure of the "Ma ster Address" By te

B8976060/02 Distributed I/Os (DP)

11 - 57 Volume 1

"Ident_Number" bytes

These two bytes contain the vendor ID for exact identification of a DP slave

type.

Structure of the extended DP sl ave diagnostics

The extended DP slave diagnostics is divided into 3 groups depending on

the DP s lave device t ype and type of error signal ed.

➣Device-related di agnostics

➣ID-related diagnostic s and

➣Channel-related diagnosti cs.

In contrast to device-related diagnostics in which general diagnostic data

are stipulated depending on vendor and device type, the structure of the

ID-related diagnostic data and channel-related data is stipulated in the

DP-standard DIN E19245 Part 3 .

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 58

The three diagnostic groups are dis tinguished by the header or identification

bytes. The order of the groups is unimportant. Each group can also occur

more than once.

Device-related diagnostics

The evaluation of the device-related diagnostics can be found in the

documentation for the device. This information varies from vendor to

vendor.

ID-related diagnostics

In ID-related diagnostics, the list following the header byte contains a bit

reserved f or every configur ed module ( ID).

This list indicates the ID number for which diagnostic data exist (bit "1") .

The list of ID-related diagnostics is rounded up to a byte boundary.

Non-configured modules are indicated by "0".

Bit 01234567

Header byte for the data field

(group) device-related diagnostics

Field length in bytes (incl. header

byte) 2 to 63

Identification for

device-related diagnostics

2nd byte

xth byte

(Field length can also be "0")

Fig. 11 .29 Str uct ure of the Hea de r Byte for Device -Rel ate d Di agno sti cs

B8976060/02 Distributed I/Os (DP)

11 - 59 Volume 1

1st byte of the data field of ID-related di agnostics

2nd byt e of the data fiel d of I D-related diagnost ics

Bit 01234567

Header byte for the data field

(group) ID-related diagnostics

Field length in bytes (incl. header

byte) 2 to 63

Identification for

device-related diagnostics

(Field length can also be "0")

Fig. 11 .30 Str uct ure of the Hea de r Byte for ID-Rel ate d Di agno sti cs

Bit 01234567

ID number 0 has diagnostic data

ID number 7 has diagnostic data

Fig. 11 .31 Structure of the Field of ID-Related Diagnostics Byte 2

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 60

3rd byte of the data fi eld of ID-related diagnostics

Channel -relate d diagnost ics

Part of a module is known as channel .

The order of the diagnosed channels and the reason for diagnostics are

each entered in three bytes in the data field for channel-related diagnost ics.

Bit 01234567

ID number 8 has diagnostic data

ID number 15 has diagnostic data

usw.

Fig. 11 .32 Structure of the Field of ID-Related Diagnostics Byte 3

B8976060/02 Distributed I/Os (DP)

11 - 61 Volume 1

1st byte of the channel-related diagnostics

2nd byte of the channel-related diagnostics

Bit 01234567

ID number 0 to 63

Identification byte for

channel-related diagnostics

Identification for

channel-related

diagnostics

Fig. 11 .33 Ch an nel-R elate d Di agno stics Byte 1

Bit 01234567

Channel number 0 to 63

Byte channel number

Input/output ID *

* ID bytes which contain both

inputs and outputs, the direction is indicated.

by bits 7 and 6 of the ID number byte

0 0 reserved

0 1 input

1 0 output

1 1 input/output

Fig. 11 .34 Ch an nel-R elate d Di agno stics Byte 2

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 62

3rd byte of the chann el-related diagnostics

Bit 01234567

Byte for error and channel type

Error type

00000 reserved

00001 short circuit

00010 undervoltage

00011 overvoltage

00100 overload

00101 overtemperature

00110 line break

00111 upper limit exceeded

01000 lower limit exceeded

01001 error

01010 reserved

01111 reserved

10000 vendor-specific

11111 vendor-specific

channel type

000 reserved

001 bit

010 2 bits

011 4 bits

100 byte

101 word

110 2 words

111 reserved

Fig. 11 .35 Ch an nel-R elate d Di agno stics Byte 3

B8976060/02 Distributed I/Os (DP)

11 - 63 Volume 1

Example: Structure of a complete data field "extended diag nostics"

Bit 01234567

110000

2 bytes vendor-specific

diagnostic data

001000

010000

00100000

10000100

110100

10100010

01100100

111010

00110001

11100101

Device-related diagnostics

Meaning explained in in DP slave

documentation.

ID-related diagnostics

-> ID number 1 with diagn.

-> ID number 11 with diagn.

-> ID number 23 with diagn.

Channel-related diagnostics

with ID number 1

Channel 4

Short circuit, channel organized in bits

Channel-related diagnostics

with ID number 11

Channel 5, input

Line break, channel organized in

bits

Channel-related diagnostics

with ID number 23

Channel 12, output

Upper limit exceeded,

organized in words

Fig. 11 .36 Str uct ure of a C omp lete D ata F iel d "Ext en ded Di agn ostic s"

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 64

Example of a program for read single DP slave diagnostics

Functions block FB 208 "EINZ-DIA" requests the diagnostic data of a single

DP slave using the CP 5430 TF/CP 5431 FMS special service HDB A-NR

209. The corresponding DP slave station number is transferred to the

function bl ock wit h the formal oper and " STAT".

FB 208 signals that the job has been done by resetting the FB trigger bit

"ANST".

Function block FB208 with the corresponding data block 208, for use in a

CPU of the S5 115U s eries can be found in t he STEP 5 file EINZELST.S5D

on the COM/application example diskette.

B8976060/02 Distributed I/Os (DP)

11 - 65 Volume 1

11.8 Sending Control Commands to the DP Slave

Using the special HDB A-NR: 209, the "Global_Control" DP service can be

used to send various control commands to the DP slav es.

These Global_Control jobs c an be used, for example, to synchronize the I/O

data from some or all of the connected DP slaves .

In general, the following rules apply for sending Global_Control jobs:

➣A DP slave only accepts control commands from the master that

assigned parameters to it and configured it.

➣By using the "group identifier" (see COM function DP slave parameter

assignment, Section 11.6.2) it is possible to control commands:

– t o a particular DP slave (single)

– t o certai n groups of DP slaves (multicast), or

– t o all connected DP slaves (broadcast)

Global_control jobs are not acknowledged on the L2 bus, i.e. the reception

of a global_control frame is not confirmed by the DP slaves .

At the handling block-user program level for the special HDB A-NR: 209

there is only a confirmation in the job acknowledgment field indicating that

the global_control frame was sent .

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 66

11.8.1 Function of the Control Commands - Sync and Unsync

Sync

The output data last received with the "Sync" control command are output

by the DP slave and frozen.

All the output data received after this are ignored until the next Sync control

command or the control command "Unsy nc" is received.

Unsync

The control command "Unsync" cancels the function of the control

command "Sync".

L2-DP master L2-DP bus DP slave Outputs

Q data info

Control command "Sync"

Control command "Unsync"

Q data info

Control command "Sync"

Q data info

Fig. 11 .37 Fu nctio n of t he Co nt rol Co mma nds - S ync and Un sync

B8976060/02 Distributed I/Os (DP)

11 - 67 Volume 1

11.8.2 Function of the Control Commands - Freeze and Unfreeze

Freeze

When the cont rol command "Freeze" is received, the current statuses of the

inputs are read in by the DP slave and frozen.

The frozen input data are transferred to the L2-DP master during cyclic

transfer until the next "Freeze" control command or the control command

"Unfreeze" is received.

Unfreeze

Cancels the function of the control command "Freeze".

L2-DP master L2-DP bus DP slave Inputs

I data info

Control command "Freeze"

Control command "Unfreeze"

I data info

Control command "Freeze"

I data info

Fig. 11 .38 Fu nctio n o f the C ont rol Co m mand s - F reeze and U nfr eeze

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 68

11.8.3 Cyclic and Acyclic Transmission of

Globa l_ Contr ol C om mands

When a control command is sent with the special HDB A-NR: 209, the CPs

distinguish between the two job types in the transferred job field:

➣Acyclic transmission of control commands

➣Cyclic transmission of control commands

Acyclic transmissio n of co ntrol commands

With the job type, "acyclic transmission", the CPs send the required control

command once at the end of a DP polling list cycle.

If any of the DP slaves relevant for the control command job are not in the

cyclic data transfer phase with the CPs, the job is not executed and is

acknowledged negatively.

Cyclic transmissio n of co ntrol commands

In contrast to the "acyclic transmission" of control commands, in the job

type "cyclic transmission", once the control command has been activated, it

is sent by the CPs at the end of every DP polling list cycle (Unsync,

Unfreeze).

The cyclic transmission of a control command is terminated by sending a

new control command.

Sending control commands with the job type "cyclic transmission" is only

possible when the mode "cycle-synchronized" was selected during

configuration of the I/O areas with the COM package.

B8976060/02 Distributed I/Os (DP)

11 - 69 Volume 1

If any of the DP slaves relevant to the control command job are not in the

cyclic data trans fer phase with the CPs when the job fi eld is transferred, t he

job is acknowledged negatively when it is transferred to the CP or may be

deactivated later.

A cyclic global control job that only deactivates the mode Sync and /or

Freeze is converted to a cyclic control job. The requirement for this is a

Group ID other than "0".

Checking the cyclic control command j ob

The cyclic transmission of global control commands can be monitored using

the group status bit of the ANZW HDB A-NR: 202 (DP s tation list).

The bit has the following signific ance:

bit 10 = "1" Global_Control command is sent cyclically.

"0" The cyclic transmission of Global_Control commands

is not active (has been deactivated).

Here, there are two different sit uations:

a) no Global_Control command was sent with the

job type cyclic transmission.

b) at least one of the DP slav e stat ions relevant for the

job is no longer in the cyclic data transfer phase

with the CP.

☞The cyclic transmission of Global_Control and control

commands must be activated again by the PLC.

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 70

Program example of sending a control command to a DP slave

Expla nation of Fig . 11.39:

The special service to send "Global_Control commands" to the DP slave is

triggered with SEND A-NR: 209 (job field transferred) and acknowledged

locally by the CP with RECEIVE A-NR: 209.

S5-Adr.

ANZW

ANR

SSNR

PAFE

Job

L2-DP bus

SEND

A-NR:

209

S5-Adr.

ANZW

ANR

SSNR

PAFE

RECEIVE

Anzw = job_complete_without_error

(...4H)

Control program

Job

field

Anzw = job_active (...2H)

A-NR: 209

DP slave

Control command

Ackn.

field

Anzw = job_active receive possible (...3 ) H

Fig. 11 .39 Se quen ce of HDB S pec ial Ser vic e A-NR : 209 fo r Glob al_C ontro l

B8976060/02 Distributed I/Os (DP)

11 - 71 Volume 1

Structure of the job field "send con trol command"

1st byte

2nd byte

3rd byte

4th byte

04 hex

Job type

Length of job field in bytes

Bit 7 = reserved = 0

Control

command

Group

identifier

02 hex acyclic synchronization job

03 hex cyclic synchronization job

Bit 6 = reserved = 0

Bit 5 = Sync

Bit 4 = Unsync

Bit 3 = Freeze

Bit 2 = Unfreeze

Bit 1 = not used = 0

Bit 0 = reserved = 0

Function table for the

bits Sync/Unsync

and Freeze/Unfreeze

As assigned with COM in the DP slave

parameter assignment or 00 Hex

as general broadcast frame

Fig. 11 .40 Structure of the Job Field of "Send Control Command"

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 72

Control Command Byt e

Structure of t he acknowl edgment field for "send cont rol command"

Bit 01234567

reserved = 0

Unfreeze

Freeze

Unsync

Sync

reserved = 0

Fig. 11 .41 Function Table for Control Command Byte

1st byte

2nd byte

02 hex

Acknowledgment

Length in bytes

00 hex OK

01 hex syntax error in job field

02 hex error in HDB handling

06 hex slave stations not all in the

data transfer phase

08 hex illegal command code

07 hex cyclic control command not possible

because "Free" mode is set.

09 hex no DP slave with the relevant group identifier

is active.

0B hex job cannot be executed because DP polling list

processing is in the STOP mode

Fig. 11 .42 Str uct ure of t he Ack now ledgm ent Fiel d fo r "Sen d Co ntro l Co mma nd"

B8976060/02 Distributed I/Os (DP)

11 - 73 Volume 1

Meaning of the bits for Un-/Sync and Un-/Freeze

bit 2 or 4 bit 3 or 5 Meaning

0 0 No function

0 1 Function is activated

1 0 Function i s deacti vated

1 1 Function i s deacti vated.

11.8.4 Special Job "STOP DP polling list processing"

Using the special job "STOP DP polling list processing" with special HDB

A-NR: 209, you can stop the cyclic processing of the DP polling list.

Polling list processing is continued again as soon as a new cycle

checkpoint is sent with HDB SEND 210 or RECEIVE 211.

The following rules apply to sending the special job "STOP DP polling list

processing":

➣The special job "STOP DP polling list processing" is only effective in the

"cycle-synchronized" DP mode.

➣The stop job only takes effect at the end of a DP polli ng l ist cycle.

➣Polling list processing is continued by calling the cycle check HDBs

(SEND 210 or RECEIVE 211).

➣As long as DP polling list processing is in the STOP mode, it is not

possible to send Global_Control commands or to read the diagnostic

list.

➣When DP polling list processing is resumed with the cycle check HDBs,

the connected DP slaves are assigned new parameters and

reconfigured.

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 74

Sequence of the special service "STOP DP pol ling list processing"

Expla nation of Fig . 11.43:

The special service "STOP DP polling list processing" is triggered with the

SEND A-NR: 209 and acknowledged locally by the CP with RECEIVE

A-NR: 209.

S5-Adr.

ANZW

ANR

SSNR

PAFE

Job

L2-DP bus

SEND

A-NR:

209

S5-Adr.

ANZW

ANR

SSNR

PAFE

RECEIVE

Anzw = job_complete_without_error

(...4H)

Control program

Job

field

Anzw = job_active receive possible (...3 ) H

A-NR: 209

Ackn.

Data

Anzw = job_active (...2H)

Fig. 11 .43 Se quen ce of t he Specia l Ser vice "STO P DP P ollin g Lis t Proc essi ng"

B8976060/02 Distributed I/Os (DP)

11 - 75 Volume 1

Structure of the job field "STOP DP po lling list processing"

Structure of the acknowledgment field for "STOP DP polling list

processing"

❑

1st byte

2nd byte

3rd byte

4th byte

Length of the job field in bytes

Job type: STOP-DP polling list processing

Not used with this function

Fig. 11 .44 Str uct ure of the Jo b Field "ST OP D P Poll ing Li st Pro cess in g"

1st byte

2nd byte

Length in

bytes

Acknowl.

always 2 bytes

00 hex ok

01 hex syntax error in job field

07 hex stop DP polling list processing not possible,

because the DP "Free" mode is set.

0B Hex stop DP polling list processing unnecessary

DP polling list processing already in the

STOP mode.

Fig. 11 .45 Stru ct ure of the Ackno wledgment Field fo r "STOP DP Polling List Proce ss ing"

Distributed I/ Os (DP) B890 60 /02

Volume 1 11 - 76

12 Service and Diagnostic Fu nctions o n the

SINEC L2 Bus using FMA Services

This chapter describes the administrative fieldbus management (FMA)

services available to you as the user and the corresponding parameters.

The chapter informs you of the following:

➣What is understood by FMA services

➣Why FMA services are used

➣Which FMA services are relevant for the SINEC L2 bus system

➣How FMA services are called

➣How the corresponding request and confirmation frames are structured.

Requirements for understanding this chapter are as follows:

➣Knowledge of the PROFIBUS standard (DIN 19245, Part 1)

➣Knowledge of data transmission by direct access to layer 2 services.

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 1 Volume 1

12.1 Use and Types of FMA Service

The fieldbus management (FMA) organizes the initialization, monitoring and

error handling between the FMA user and the logical functions in layers 1

and 2.

The management therefore serves as mediator between the local user and

layers 1 and 2. Service requests which may be specified by the

management are passed on to layers 1 or 2 and the user of the FMA

services receives an acknowledgement with a confirmation.

The FMA services permitted for the SINEC L2 bus system allow diagnosis

of all the systems belonging to the bus and t heir links.

When using the FMA services and the clock function at the same time, the

following feature of the CP must be noted:

☞If the CP is the clock master on the L2 bus and if an FMA

service is triggered at the same time, this can lead to delays

in the transmission of the cyclic time of day frame.

Service and Diagnostics using FMA Functions B8976060/02

Vol ume 1 12 - 2

To avoid dangerous plant states in the bus system, only the following

reading (passive) FMA services are permitted with the CP 5430 TF/CP

5431 FMS:

Services Function

FDL_READ_VALUE Reading the current bus parameters.

LSAP_STATUS Reading the status values of an SAP.

FDL_LIFE_LIST_CREATE_LOCAL Creating the current overview of all the

systems connected to the bus system

by means of station-internal

information.

FDL_IDENT Reading the identification of the local

or a remote station on the SINEC L2

bus system.

FDL_READ_STATISTIC_CTR Reading the station-oriented statistical

information.

FDL_READ_LAS_STATISTIC_CTR Reading the bus-oriented statistical

information.

Table 12.1 FMA Se rvices

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 3 Volume 1

The following table lists some of the characteristics of the individual

services.

Before using t he FMA services, you must perform the following tasks for t he

CP 5430 TF/CP 5431 FMS:

➣create the SYSID block

➣assign parameters for the required HDBs SYNCHRON, CONTROL,

SEND or RECEIVE

➣set up a data block with the request header and space for the

confirmation.

The creation of the SYSID block is described in detail in Chapter 6.

FDL_READ_VALUE

LSAP_STATUS

FDL_LIFE_LIST_CREATE_LOCAL

FMA services

Characteristics of the

FMA services FMA service

can be used

when

CP 5430 TF:

active passive

FMA service

requests

info from

CP 5430 TF:

local remote

For the FMA service the

following bytes in the FMA

header are relevant:

0213

4567

XXXXXXXXX

XXXXXXX

FDL_IDENT

FDL_READ_STATISTIC_CTR

FDL_READ_LAS_STATISTIC_CTR

CP 5431 FMS:CP 5431 FMS:

Table 12.2 Chara cte ristics of the FMA Se rvic es

Service and Diagnostics using FMA Functions B8976060/02

Vol ume 1 12 - 4

12. 2 Fu ndam ental s o f usi ng t he FM A Serv ic es

The request for an FMA service by the CP 5430 TF/CP 5431 FMS and the

transfer of the confirmation to the CPU of the PLC is the responsibility of

the handling blocks SEND and RECEIVE.

For FMA services, use job number ANR 200 when calling the HDBs SEND

and RECEIVE.

If an FMA service is requested, the following procedure is executed:

(Evaluation of status word)

SENDER

Indication that an "acknowledgment"

(confirmation) has arrived from

receiver CP

The confirmation is fetched with

an HDB RECEIVE; it consists of

an 8-byte header and the

requested data or parameters.

An 8-byte header (request block)

is sent with HDB SEND

(Evaluation of status word)

(Evaluation of condition code word)

(Evaluation of status word)

Fig. 12 .1 Schematic Seq uence of th e F MA Services

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 5 Volume 1

A distinction is made b etween local and remote FMA servi ces

Local control program

S5-add.

ANZW

ANR

SSNR

PAFE

Anzw = Job_active receive possible

Anzw = Job_active

(data)

BUS

SEND

Request

e.g.:DB

Header

(...2 )

(...3 )

e.g.:DB

Header

S5-add.

ANZW

ANR

SSNR

PAFE

RECEIVE

Anzw = Job_complete_without_error

FMA-

Fig. 12 .2 Schematic Seq uence of a n FM A Service (local)

Local control program

S5-add..

ANZW

ANR

SSNR

PAFE

Anzw = Job_active receive possible

Anzw = Job_active

(data)

BUS

SEND

FMA-

Request

e.g.:DB

Header

(...2 )

(...3 )

e.g.:DB

Header

S5-add..

ANZW

ANR

SSNR

PAFE

RECEIVE

Anzw = Job_complete_without_error

(...4 )

CP Remote station

Fig. 12 .3 Schematic Sequence of a n FMA Service (re mote)

Service and Diagnostics using FMA Functions B8976060/02

Vol ume 1 12 - 6

An FMA request consists of an 8-byte header. Depending on the service,

the confirmation consists of a maximum of 250 bytes, of which the first 8

bytes are occupied by the confirmation header (FMA header).

Fig. 12.4 shows the structure of a block of data to be transmitted or

received. The designations of the header bytes are taken from the

PROFIBUS standard.

The FMA header contains the following parameters which are not

completely evaluated by all functions.

com_class

user_id

service_code

link_status

Byte

Header

service_class

DSAP/RSAP

rem_add_station

rem_add_segment

data

249

Fig. 12 .4 Structure of the FMA Header for Request and Confirmation

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 7 Volume 1

Storing the request header and confirmation data

The data to be transferred (8 bytes) and t he received data (max. 250 bytes)

should be stored in a data block. Correct storage of the header information

in a DB (see Fig. 12.4) is necessary for error-free use of an FMA service. It

is advisable to provide enough space for the confirmation data in the same

DB.

Note

The following rules apply to FMA services:

➣If parameters occupy two bytes (one word) the order in which these

bytes are stored in the data word of a data block is important:

– lef t data (DL): low byte of the parameter

– r ight dat a (DR): high by te of the parameter.

The header bytes are explained as necessary in the service descriptions

starting in Section 12.3.

The program example is described in detail for the FMA service

FDL_READ_VALUE. Setting up the DB is also illustrated as

comprehensively as the user program.

The user program for the other FMA services has an analogous structure.

The only difference is that a different DB must be called with parameters

assigned f or the par ticular servic e (e.g. service_code) .

Service and Diagnostics using FMA Functions B8976060/02

Vol ume 1 12 - 8

Controlling the data exchange

To be able to control the data exchange between the CPU and CP 5430

TF/CP 5431 FMS, you must evaluate the status word (ANZW) for this job.

The condition contains information about the status of the job, information

about data management and error bits (refer to Figs. 12.5/12.6).

The figures illustrating the sequence of the control program (refer to Figs.

12.2/12.3) illust rate the changes in the status word.

Not

used Error

bits Data

mgment. Status

bits

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Job complete with error

Error transferring a request or when accepting

an indication or confirmation

Job complete without error

(with SEND HDB: correct transfer of an FMA request

with the RECEIVE HDB: correct transfer of

a confirmation)

Job active

(Request being processed or confirmation of request

not yet received)

Receive possible

Confirmation exists and can be accepted with the

RECEIVE HDB

Fig. 12 .5 Structure of the Stat us Word, h ere: Status Bits

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 9 Volume 1

Data acceptance/transfer

(enable/disable bit)

Reserved

Data transfer complete on CP

(FMA request was transferred),

This bit is reset by the HDB

Data acceptance complete

(FMA indication or FDL confirmation

transferred to PLC)

This bit is reset by the HDB

Error

bits Data

mgment. Status

bits

For meaning of

the error bits:

refer to Table 12.3

111098 7654 3210

This bit is not required here, no

fragmentation

Fig. 12 .6 Stru ct ure of the Stat us w ord, here: Data M anag emen t

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 10

Bits

8-11 Meaning

0HNo error

I f bit 3 " job c omp let e wit h er ror" is neve rthe le ss se t, th is me ans t ha t the C P has

set up the job aga in f oll owing a cold restart or RESET.

1HWron g type specifi ed in block call (QTYP/Z TYP).

2HMe mor y area do es no t exis t (e. g. no t init ializ ed). .

3HM emo ry ar ea to o sma ll.

The memory area specified in the HDB call (parameters Q(Z)TYP, Q(Z)ANF,

Q(Z)L AE) ist for too sm all for th e data tra nsmission.

4HTim eout (QVZ).

Ac know led geme nt from th e m emo ry cel l is abse nt dur ing data tran sfe r. Re me dy:

check and if necessary replace the memory submodule or check and correct the

sou rce /d estin ation pa ramet ers .(ty pes A S, PB a nd OY sp ecifie d).

5HIncorrect parameters assigned to status word.

The parameter "ANZW" wa s specified incorrec tly . Remedy: correct th e

par am eter or set up t he da ta blo ck co rrec tly in whic h the ANZ W is to be loc ated .

(DB-No. and DB length).

6HInvalid source/destination parameter.

Parameter ID "NN" or "RW" was used or the data length is too small (=0) or

longer than 128 bytes. Remedy: use the correct Q(Z)TYP parameter; "NN" and

"RW" are n ot allow ed fo r this type of data t ransm ission.

7HLocal resource bottleneck.

There are no data buffers available for processing the job. Remedy: retrigger

the job, reduce the CP load.

BHH and shak e er ror.

The HDB processing was incorrect or the HDB monitoring time was exceeded.

Remedy: start the job again.

CHSy st em error.

Error in the system program . Remedy: in form Siemens service

DHDisabled data block.

The data transmission is or was disabled during the HDB processing. (control bit

di sab le/ en able i n stat us word disab le).

EHFree

FHJ ob or "cha nn el not pro gra mme d.

programm in g error or wrong (SSNR/ANR). Remedy: program ANR as "cha nn el"

(FREE) or correct SSNR/ANR in HDB call

Table 12.3 Error Bits (bit s 8...11) i n th e Status W ord

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 11 Volume 1

The parameter assignment error byte (PAFE) must also be evaluated in

the control program. It informs you about various parameter assignment

errors. When you assign parameters to the individual blocks, you specify

the address at which this information is available. The meaning of the

individual bits is explained in Fig. 12.7.

Error

number

7654 3210

0 - no error

1 - error

0 - no error

1 - wrong ORG format /ZTYP illegal (PLC or CP)

2 - area does not exist (DB does not exist/illegal)

3 - area too short

4 - QVZ (timeout) error no access possible

5 - wrong status word

6 - no source or destination parameters for SEND/RECEIVE

7 - interface does not exist

8 - interface not ready

9 - interface overload

A - interface busy with other modules

B - illegal ANR

C - interface (CP) not acknowledging or negatively

D - parameter/BLGR illegal (1st byte)

E - error in HDB

F - HDB call illegal (e.g. double call or

illegal change)(only with S5 135U/155U)

Fig. 12 .7 Structure of t he Paramete r Assignment Error Byte "PAF E"

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 12

12.3 FDL_READ_VALUE

This service allows the FMA user to read out the current bus parameters of

the local station.

12.3.1 FDL_READ_VALUE_Request

For the structure of the FDL_READ_VALUE request you must enter the

following parameters in the header:

com_class 0. byte: f ormat KH, serv ice request to l ayer 2

here:

FDL request =00H

user_id 1st byte: f reely assignable ID, which is returned

unchanged with a confirmation

(optional)

service_code 2nd byte: format KH, type of service requested:

FDL_READ_VALUE=0BH

link_status /

service_class/

SAP number/

rem_add_station/

rem_add_segment

3rd-7th byte: irrelevant

The arrangement of the data in a DB from which they can then be read by

the HDB S END is explai ned i n more det ail in Sec tion 12. 9.1.

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 13 Volume 1

12.3.2 FDL_READ_VALUE_Confirmation

In the FDL_READ_VALUE confirmation, the values for the header and bus

parameters are stored as follows:

com_class 0. byte: f ormat KH, serv ice request to l ayer 2 here:

FDL confirmation =01H

user_id 1st byte: I D assigned with FDL reques t

(optional)

service_code 2nd byte: format KH, type of service requested:

FDL_READ_VALUE=0BH

link_status 3rd byte: format KH, OK or error message

(refer to Table 12.4)

service_class/

SAP number/

rem_add_station/

rem_add_segment

4th-7th byte: irrelevant

Bus parameter

block from 8th byte: (refer to Table 12.5)

The storage of the block data in a DB by HDB RECEIVE is described in

detail i n Secti on 12.9.1.

The parameter link_status of the confirmation indicates the success or

failure of the previous FMA request.

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 14

The following messages can occur with the FMA service

FDL_READ_VALUE:

The reaction in the user program when this message is received is not

fixed.

Value of

link_status Abbrev.

PROFIBUS Meaning

FDL_READ_VALUE

00HOK P osit ive acknowl edgme nt: se rvic e exe cut ed, bus

parame ters re ad

15HIV Negative acknowledgment: "...RESET" curre nt ly

acti ve or no receive buffer

Table 12.4 li nk_st atus Mess age f or F DL_R EAD_ VAL UE Co nf irmati on

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 15 Volume 1

Structure of the bus parameter block (see also network parameters):

Parameter Meaning Range of values/Code

hsa (byte) Highest station address 2 to 126 (display of the value set

in t he I nit blo ck)

loc_add._station

(byte) Address of the local station 1 to 126

station_typ (word) Active / passive 0 0H = pa ssive 01 H = acti ve

baud_rate (word) Baud rate 00H = 9.6 Kbps

01H = 19.2 K bps

02H = 93.75 Kbps

03H = 187.5 Kbp s

04H = 500 Kb ps

07H = 1.5 Mbps

medium_red (word) Redundancy 00H = not redundant

retry _ctr Number o f retries 01H = once 02H = tw ice

def ault_sap (byte) Def ault SAP if no SAP

specified 2 to 54, 57 , 61

network_connection_s

ap (byte) Num ber o f ne two rk

co nnec tion S AP 0 (not used)

tsl (word) Slot time 20 to 216 -1 bit tim e un it

tqu i (word ) M odulator qu iet time rese rved

tset (word) Setup time 0 to 216 bit time unit

min_tsdr (word) Min. station delay time 20 to 2 16 -1 bit time unit

max_tsdr (word) Max. station delay time 20 to 216 -1bit tim e un it

ttr (Dop pelwort) Targe t rot ation time 2 0 to 224 -1 bi t time unit

g ( byte ) GA P upda te f actor 1 to 100

in_ring_desired

(word) Request to enter ring true = 1(im low byte)

false = 0

physical_layer (word) Physical bus characteristics 00H = R S 485 / F O

Table 12.5 Values of th e Bus Parameter Bloc k fo r FDL_READ_VALUE Confirmatio n

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 16

12.4 LSAP_STATUS

This service allows the FMA user to read out the services and functions

assigned to a particular SAP of a remote or local station.

Services

➣SDA

➣SDN

➣SRD

➣CSRD (not possible for CP 5430 TF/CP 5431 FMS)

Functions

➣Initiator

➣Responder

➣Initiator and Responder

➣Service not activated

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 17 Volume 1

12.4.1 LSAP_STATUS_Request

The LSAP_STATUS request block must be structured as follows:

com_class 0. byte: f ormat KH, serv ice request to l ayer 2

here:

FDL request =00H

user_id 1st byte: f reely assignable ID, which is returned

unchanged with a confirmation.

(optional)

service_code 2nd byte: format KH, type of service requested:

LSAP_STATUS=19H

link_status /

service_class/ 3rd-4th by te: ir relevant

RSAP 5th byte: format: KH,

Range of values of the remote SAP no.: (0 . . 63)

rem_add_station 6th by te: for mat KH

Range of values of the station address: (0 .. 126)

rem_add_segment 7th byte: f ormat KH, irrelevant

The arrangement of the data in a DB from which they can then be read by

the HDB S END is explai ned i n more det ail in Sec tion 12. 9.2.

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 18

12.4.2 LSAP_STATUS Confirmatio n

The values for the header and LSAP status are stored as follows in the

LSAP_STATUS conf irmation:

com_class 0. byte: f ormat KH, serv ice request to l ayer 2

here:

FDL confirmation =01H

user_id 1st byte: I D assigned with FDL reques t

(optional)

service_code 2nd byte: format KH, type of service requested:

LSAP_STATUS=19H

link_status 3rd byte: format KH, OK or error message

(refer to Table 12.6)

service_class 4th byte: irrelevant

RSAP 5th byte: format K H, rem ote SAP number

rem_add_station 6th by te: for mat KH, station number of sender

rem_add_segment 7th byte: irrelevant

access_station 8th byte: station access restrictions

access_segment 9th byte: segment access restrictions

LSAP status

(The arrangement

may be di ff erent

with other devices)

10th byte: Status_SDA

11th byte: Status_SDN

12th byte: Status_SRD

13th byte: Status_CSRD

The storage of the data in a DB by HDB RECEIVE is illustrated in detail in

the example in Section 12.9.2.

The parameter link_status of the confirmation indicates the success or

failure of the previous FMA request.

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 19 Volume 1

The following messages can occur with the FMA service LSAP_STATUS

The reaction in the user program to receiving this message is not fixed.

The status bytes of the service descriptions are structured as follows:

Value o f

link_status Abbrev.

PROFIBUS Meaning

00H OK Positi ve ac know ledg men t, st atus was r ead

RS LSAP n ot activated o n t he remote FDL controller

NA No p laus ibl e reac tio n (ack /res ) fro m re mote st ation

DS Local FDL/PHY not in logical token ring or is disconnected

from the bus line

NR Negative acknowledgment, reply data (L_sdu) not available

on th e remote FDL con troller

15H IV Negative acknowledgment:

- "FDL_RESET" cu rren tly active

- in valid param et er in th e app licati on blo ck

- pa ssiv e stat ion ( with remo te re ques t)

- other FM A se rvic e c urrently active (MAC)

Table 12.6 link_stat us Me ssage for LSAP_STATUS Con firmation

Role_in_service Service_type

Bit 76543210

Fig. 12 .8 Structure of t he LSAP_STATUS Byte

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 20

The entries in the right or left nibble have the following significance:

Service_type Bit

Role_in_service

32 10 Enabled service

Bit SAP function for the enabled

services

00 00

00 01

00 11

01 01

SDA enabled

SDN enabled

SRD enabled

CSRD enabled

76 54

Initiator

Responder

Initiator and Responder

00 00

00 01

00 10

00 11 Service not activated

Table 12.7 Meaning of the Status Byte Entries

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 21 Volume 1

12.5 FDL_LIFE_LIST_CREATE_LOCAL

This service supplies status information about all active stations and all

passive stations located in the GAP area of the service requesting station.

To provide the status information, no information is requested from remote

station, i.e. the bus is not subjected to extra load by this service.

12.5.1 FDL_LIFE_LIST_CREATE_LOCAL Request

The FDL_LIFE_LIST_CREATE_LOCAL request bl ock must be structured as

follows:

com_class 0. byte: f ormat KH, serv ice request to l ayer 2

here:

FDL request =00H

user_id 1st byte: f reely assignable ID, which is returned

unchanged with the confirmation

(optional)

service_code 2nd byte: format KH, type of service requested:

FDL_LIFE_LIST_CREATE_LOCAL=1BH

link_status /

service_class/

SAP number/

rem_add_station/

rem_add_segment

3rd-7th byte: irrelevant

The arrangement of the data in a DB from which they can then be read by

the HDB S END is explai ned i n more det ail in Sec tion 12. 9.4.

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 22

12.5.2 FDL_LIFE_LIST_CREATE_LOCAL Confirmation

The values for the header and station status are stored as follows in the

FDL_LIFE_LIST_CREATE_LOCAL confirmation:

com_class 0. byte: f ormat KH, serv ice request to l ayer 2

here:

FDL confirmation =01H

user_id 1st byte: I D assigned with FDL reques t

(optional)

service_code 2nd byte: format KH, type of service provided:

FDL_LIFE_LIST_CREATE_LOCAL=1BH

link_status 3rd byte: format KH, OK or error message

(refer to Table 12.9)

service_class/

SAP number/

rem_add_station

rem_add_segment

4th-7th byte: irrelevant

Status bytes 8th byte: status byte stati on (STA) 00

9th byte: status byte station (STA) 01

(hsa+8th byte): status byte station (STA) hsa

The storage of the status data in a DB by the HDB RECEIVE is illustrated

in detail in the example (Section 12.9.4).

The parameter link_status of the confirmation indicates the success or

failure of the previous FMA request.

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 23 Volume 1

The following messages can occur with this FMA service:

The reaction of the user program to rec eiving this message is not fixed.

The confirmation block contains status bytes of the active stations and

passive stations located in the GAP area of the service requesting station.

The status bytes are structured as follows:

Byte val. Meaning

10 St at ion does not exist

20 St at ion active and ready

30 St atio n acti ve

00 St at ion pa ss ive

Fig. 12 .9 FDL_L IFE_LIST_ST ATUS Byte

Value of

link_status Abbrev.

PROFIBUS Meaning

FDL_LIFE_LIST_CREATE_LOCAL

00HOK Positive acknowledgment, lif e list was

created

IR Resources of the local FDL controller not

available or not adequate (no life list buffer)

15HIV Negative acknowledgement:

- "FDL_RESET" currently active

- passive station

- another FMA service currently active

Table 12.8 link_status Message for FDL_LIFE_LIST_CREATE_LOCAL Confirmation

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 24

12.6 FDL_IDENT

With this service, identification information can be requested from a station

connected to the bus. This can involve both the local or a remote station.

The identification contains the manufacturers name, the PROFIBUS

interface module type, the hardware and software versions.

12.6.1 FDL_IDENT Request

The FDL_IDENT request block must be structured as follows:

com_class 0. byte: f ormat KH, serv ice request to l ayer 2

here:

FDL request =00H

user_id 1st byte: f reely assignable ID, which is returned

unchanged with the confirmation

(optional)

service_code 2nd byte: format KH, type of service requested:

FDL_IDENT=1CH

link_status /

service_class/

SAP number

3rd-5th byt e: irr elevant

rem_add_station 6th byte: format: KH:,

Range of values of the station address: (0 .. 126)

rem_add_segment 7th byte: irrelevant

The arrangement of the data in a DB from which they can then be read by

the HDB S END is explai ned i n more det ail in Sec tion 12. 9.5.

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 25 Volume 1

12.6.2 FDL_IDENT Confirmation

The values for the header and station Ident parameters are stored in the

FDL_IDENT confirmation as follows:

com_class 0. byte: f ormat KH, serv ice request to l ayer 2 here:

FDL confirmation =01H

user_id 1st byte: I D assigned with FDL reques t

(optional)

service_code 2nd byte: format KH, type of service provided:

FDL_IDENT=1CH

link_status 3rd byte: format KH, OK or error message

(refer to Table 12.10)

service_class/

SAP number 4th-5th byte: irrelevant

rem_add_station 6th byte: format: KH:

Number of the station: (0 .. 126)

rem_add_segment 7th byte: irrelevant

Ident bytes 8th byte: LE1 (length byte 1)

9th byte: LE2 (length byte 2)

10th byte: LE3 (length byte 3)

11th byte: LE4 (length byte 4)

12th byte: hardware version

(12+LE1) by te: cont roller PROF IBUS i nterface modul e

(12+LE1+LE2) byte: vendor name

(12+LE1+LE2+LE3) byte: software release

max. 200th byte

The storage of the status data in a DB by the HDB RECEIVE is illustrated

in detail in the example (Section 12.9.5).

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 26

The parameter link_status of the confirmation indicates the success or

failure of the previous FMA request.

The following messages can occur with this FMA service:

The reaction in the user program to receiving this message is not fixed.

Value of

link_status Abbrev.

PROFIBUS Meaning

FDL_IDENT

00HOK Po sit ive ac know led gmen t, I de nt wa s re ad

11HNA No plausible reaction (ack/res) from remote

station)

12HDS Local FDL/PHY not in logical token ring or

d iscon nect ed f rom th e b us lin e

09HNR Negative acknowledgment for IDENT data since

not available on remote controller

LR Resources of the local FDL controller not

available or inadequate

15HIV Negative acknowledgment:

- "FDL_RESET" c urrently active

- passive station

- other FM A service currently ac tive.

Table 12.9 li nk_st atus Mess age f or F DL_I DE NT Con firm at ion

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 27 Volume 1

12.7 FDL_READ_STATISTIC_CTR

This service is used to read station-oriented statistical information. In the

appropriate bytes, counters indicate how often certain statuses occurred in

the bus system. The counters are set to 0 at each cold restart and

whenever they are read. This means that the values always relate to a

defined period. If the counters overflow, this is not indicated. When the

upper limit is reached, the counters stop.

12.7.1 FDL_READ_STATISTIC_CTR Request

The FDL_READ_STATISTIC_CTR request block must be structured as

follows:

com_class 0. byte: f ormat KH, serv ice request to l ayer 2

here:

FDL request =00H

user_id 1st byte: f reely assignable ID, which is returned

unchanged with the confirmation

(optional)

service_code 2nd byte: format KH, type of service requested:

FDL_READ_STATISTIC_CTR=1DH

link_status /

service_class/

SAP number/

rem_add_station/

rem_add_segment

3rd-7th byt e: irr elevant

The arrangement of the block data in a DB from which they can then be

read by the HDB is explained in detail in the example (refer to Section

12.9.6).

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 28

12.7.2 FDL_READ_STATISTIC_CTR Confirmatio n

The values for the header and st ati on statistics parameters are s tored in t he

FDL_READ_STATISTIC_CTR as follows :

com_class 0. byte: f ormat KH, serv ice request to l ayer 2

here:

FDL confirmation =01H

user_id 1st byte: I D assigned with FDL reques t

(optional)

service_code 2nd byte: format KH, type of service provided:

FDL_READ_STATISTIC_CTR=1DH

link_status 3rd byte: format KH, OK or error message

(refer to Table 12.10)

service_class/

SAP number/

rem_add_station/

rem_add_segment

4th-7th byte: irrelevant

Statistics

parameters field from 8th byte: (refer to Table 12.11)

The storage of the status data in a DB by the HDB RECEIVE is illustrated

in detail in the example (Section 12.9.6).

The parameter link_status of the confirmation indicates the success or

failure of the previous FMA request.

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 29 Volume 1

The following messages can occur with this FMA service:

The reaction of the user program to rec eiving this message is not fixed.

Value of

link_status Abbrev.

PROFIBUS Meaning

FDL_READ_STATISTIC_CTR

00HOK Positive acknowledgment: service executed,

statistics read

15HIV Negative acknowledgment: "..._RESET"

currently active or no recei ve buffer or no

statis ti cs buffer exists

Table 12.10 link _status Me ssage f or FDL_READ_ STATISTIC_ CTR Con firmatio n

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 30

The values in the statistics block provide information about how often the

following processing statuses occurred:

Parameter Meaning

invalid_start_delimiter_ctr Received frame with invalid start delimiter

inv ali d_fcb _fcv _ctr Rec eive d fra me w ith in valid FCB /FC V.

invalid_token_ctr Token frame:

- do es no t mat ch LA S

- DA and SA > bus_ pa rameter.hsa.

col lis ion_c tr Une xpec te d resp on se fram e

wro ng _fcs _or _ed_ ctr R ecei ved f ram e wit h wro ng FCS or E D.

f rame_ erro r_ct r - Gap in re ceiv ed fram e

- Receive buffer too short

char_e rror_ctr - Seri al e rror (framing, pari ty, overrun error)

- In va lid sta rt d elimi ter

- Frame with invalid SD2 header

- Wrong FCS or ED.

retry _ctr Frame repet ition

st art_d el imite r_ctr Rec eive d fra me w ith v alid s tart delim iter (=re fere nce)

stop_receive_ctr Reception aborted, because:

- receive bu ffer too sh ort

- in valid start d eli miter

- co llisio n

- du plica te ad dre ss

- invalid DA, SA, DAE, SAE o r LE

- wr ong f cs or e d

- SD1, SD2, SD3 received in LI STEN_T OKEN

sen d_ conf irmed _ct r Num ber o f tra nsmi tte d "co nfirm ed" re qu ests

send_sdn_ctr Number of transmitted SDN requests.

Table 12.11 Info in the Statist ics Para meter Blo ck for FDL_REA D_STATISTIC_CTR Confirmation

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 31 Volume 1

12.8 FDL_READ_LAS_STATISTIC_CTR

This service is used to read bus-oriented statistical information. In the

appropriate bytes, counters indicate how often certain statuses occurred in

the bus system. The counters are set to 0 at each cold restart and

whenever they are read. This means that the values always relate to a

defined period. If the counters overflow, this is not indicated. When the

upper limit is reached, the counters stop.

12.8.1 FDL_READ_LAS_STATISTIC_CTR Request

The FDL_READ_LAS_STATISTIC_CTR request block must be structured

as follows:

com_class 0. byte: f ormat KH, serv ice request to l ayer 2

here:

FDL request =00H

user_id 1st byte: f reely assignable ID, which is returned

unchanged with the confirmation

(optional)

service_code 2nd byte: format KH, type of service requested:

FDL_READ_LAS_STATISTIC_CTR=1EH

link_status /

service_class/

SAP number/

rem_add_station/

rem_add_segment

3rd-7th byt e: irr elevant

The arrangement of the block data in a DB from which they can then be

read by the HDB is explained in detail in the example (refer to Section

12.9.7).

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 32

12.8.2 FDL_READ_LAS_STSTISTIC_CTR Confirmation

The values for the header and statistical data are stored in the

FDL_READ_LAS_STATISTIC_CTR confirmation as foll ows:

com_class 0. byte: f ormat KH, serv ice request to l ayer 2

here:

FDL confirmation =01H

user_id 1st byte: I D assigned with FDL reques t

(optional)

service_code 2nd byte: format KH, type of service provided:

FDL_READ_LAS_STATISTIC_CTR=1EH

link_status 3rd byte: format KH, OK or error message

(refer to Table 12.13)

service_class/

SAP number/

rem_add_station/

rem_add_segment

4th-7th byte: irrelevant

Statistics

parameter block from 8th byte: (refer to Table 12.13)

The storage of the status data in a DB by the HDB RECEIVE is illustrated

in detail in the example (Section 12.9.7).

The parameter link_status of the confirmation indicates the success or

failure of the previous FMA request.

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 33 Volume 1

The following messages can occur with this FMA service:

The reaction of the user program to rec eiving this message is not fixed.

The statistics provide information about the number of token rotations and

the number of received tokens in the individual active stations.

Value of

link_status Abbrev.

PROFIBUS Meaning

FDL_READ_LAS_STATISTIC_CTR

00HOK Pos it ive ack nowl edg ment : s erv ice ex ecut ed,

statistics read.

15HIV Negative acknowle dgmen t: "..._RESET"

currently acti ve or no receive buf fer or

pas si ve st ation.

Table 12.12 link_stat us Message for FDL _READ_LAS_STATI STIC_CTR Confirma tion

Parameter Meaning

las_cycle_ctr Number of token rotations (reference)

station x Number of received tokens station x

station y Number of received tokens station y

station z Number of received tokens station z

Table 12.13 Info in the Statistics Block for F DL_READ_LAS_STAT ISTIC_CTR Confi rma tion

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 34

12.9 Examples

The program example is described in detail for the FMA service

FDL_READ_VALUE. Setting up the DB is also illustrated as

comprehensively as the user program.

The user program for the other FMA services has an analogous structure.

The only difference is that a different DB must be called with parameters

assigned f or the par ticular servic e (e.g. service_code) .

12.9.1 Program Example for the FDL_READ_VALUE Service

For this example, DB 140 is set up to store the request and confirmation

data.

The following parameters must be specified for the FMA service

FDL_READ_VALUE:

com_class : 00H = request

service_code : OBH = FDL_READ_VALUE

After accepting the confirmation block with the HDB RECEIVE, the values

are entered in the DB and can then be processed further by the user

program.

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 35 Volume 1

The user program is st ruct ured as foll ows:

After evaluating the ANZW, to determine whether a previous job is still

active, the request is sent. If no PAFE occurs and the SEND job is

completed, the ANZW is checked to determine whether a confirmation has

been received. If this is the case, this is transferred with HDB RECEIVE to

the CPU and the parameters can be processed in the user program or

evaluated as a check. An error check has already been performed with

ANZW, PAFE and link_status.

Word DB 140 Explanation

KH = 0000;

KY = 000,000

KY = 011,000

KY = 000,000

KH = 0000;

KY = 000,000

***Request-Header****

com_class / user_id

service_code / no significance

no significance

****Confirmation-Header****

com_class / user_id

service_code / link_status

no significance/no significance

10:

11:

12:

13:

14:

15:

16:

17:

18:

19:

20:

21:

22:

23:

24:

25:

26:

27:

KY = 000,000

KH = 0000;

KY = 000,000

KH = 0000;

KY = 000,000

KY = ..

KY = .. ..

hsa / loc_add.station

station_type

baud_rate

medium_red

retry

default_sap / net work_con._sap

tsl (slot-time)

tqui (modulator quiet time)

tset (set -up time)

min_tsdr (min. station delay)

max_tsdr (max. station delay)

ttr (target rotation time)

g (gap_up) / in_ring_desired

in_ring_desired / physical_Layer

physical_Layer / no significance

.....

Table 12.14 DB 140

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 36

FB140 Explanation

Segment 1

Name : READ-Va l

DECL:ANST I/Q/D/B/T/C: I BI/BY/W/D:

0008 :

0009 :

000A :

000B :

000C :

000D : JU FB 123

000E Name: CONTROL

000F SSNR: KY 0,0

0010 A-NR : KY 0,200

0011 ANZW: FW 140

0012 PAFE: FY 145

0013 :

0014 :

0015 : AN =ANST

0016 : O F 141. 1

0017 : JC =CONF

0018 :

0019 :

001A :

001B : JC FB 120

001C Name: SEND

001D SSNR: KY 0,0

001E A-NR : KY 0,200

001F ANZW: FW 140

0020 QTYP : KS DB

0021 DBNR : KY 0,140

0022 QANF : KF +1

0023 QLAE : KF +4

0024 PAFE : FY 144

0025 :

0026 : O F 141.3

0027 : O F 144.0

0028 : BEC

FMA service read_value "OBH"

FMA read_value REQUEST and

CONFIRMATION

**************************************

read status for FMA job

job number for FMA servic e

**************************************

transmi t tr igger fo r FMA s ervic e

ANZW job active

jump to rec eive c onfirma ti on

**************************************

FMA-REQUEST_SEND

jo b numb er fo r FMA f uncti on

FMA-REQ header is in

DB 140

from DW 1 on ward s

REQUEST length is 4 words

ANZW e rror

PAFE with las t SEND?

Ta ble 1 2.15 F B 140 ( part 1 of 3)

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 37 Volume 1

FB 140 (continued) Explanation

0029 :

002A : RB =ANST

002B :

002C :

002D CONF:

002E :

002F : A F 141.0

0030 : BEC

0031 :

0032 : JC FB 121

0033 Name : RECEIVE

0034SSNR : KY 0,0

0035 A-NR : KY 0,200

0036 ANZW: FW 140

0037 ZTYP : KS DB

0038 DBNR: KY 0,140

0039 ZANF : KF +6

003A ZLAE : KF -1

003B PAFE: FY 146

003C :

003D :

003E : O F 141.3

003F : O F 146.0

0040 : BEC

0041 :

reset tran smi t trigger

***************************************

ANZW-CONFIRMATION re ceiv ed?

FMA-CONFIRMATION-RECEIVE

job number for FMA servic e

FMA confirmation to be stored in

DB 140

from DW 6

"joker length"

evaluation whether RECEIVE activated

ANZW e rror

PAFE-error

Table 12.16 FB 140 (part 2 of 3)

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 38

FB 140 (continued) Explanation

0042 :

0043 :

0044 :

0045 : C DB 140

0046 :

0047 : L KB 0

0048 : L DR 1.1

0049 : ! = F

004A : BEC

004B :

004C :

004D :

004E :

004F :

0050 :

0051 :

0052 :

0053 :

0054 :

0055 : BE

***************************************

evaluation of link_status

status "ok"

load FMA link_status

program end here if

confirmation link_status positive

***************************************

user program for evaluation

of FMA-CONFIRMA TION err or

message

**************************************

Table 12.17 FB 140 (part 3 of 3)

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 39 Volume 1

12.9.2 Program Example for the LSAP_STATUS Service

For the example, DB 141 is set up to store the request and confirmation

data.

The following parameters must be specified for the FMA service

LSAP_STATUS.

com_class 00H= request

service_code 19H= LSAP_STATUS

Remote SAP no. 30H= dest SAP

rem_add_station 0AH= address of the receiver

rem_add-segment FFH= irrelevant, always enter FFH

After accepting the confirmation block with the HDB RECEIVE, the values

are entered in the DB and can then be processed further by the user

program.

DB 141 Explanation

0: KH = 0000;

1: KY = 000,000

2: KY = 025,000

3: KY = 000,061

4: KY = 002,255

5: KH = 0000;

6: KY = 000,000

7: KY = 000,000

8: KY = 000,000

9: KY = 000,000

**** RE QUE ST_ HEA DER** ** **

com_class / user_id

ser vi ce_code / no significance

no signif icance / remote SAP-Nr.

no significance / rem_add_segment

******CONFIRMATION*******

com_class / user_id

ser vi ce_code / link_status

no signif icance / remote SAP-Nr.

rem_add_st ation/ rem_add_segment

10:KM = 00000000 00000000

11:KM = 00000000 00000000

12:KM = 00000000 00000000

13:KH = 0000;

14:KH = 0000;

15:KH = 0000;

statusbyte 1 / statusbyte 2

Status SDA / Status SDN

Status SRD / Status CSRD

Table 12.18 DB 141

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 40

The structure of the user program for sending the request and receiving the

confirmation is exactly as described for the FMA service

FDL_READ_VALUE (refer to Section 12.9.1). The differences simply result

from using a different DB for storing the request or confirmation block .

☞Remember that when reading a remote station of a different

manufacturer, the position of the status bytes in the data field

may be different.

For the CP 5430 TF/CP 5431 FMS, the positions of the status bytes are as

described in the manual.

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 41 Volume 1

12.9.3 Program Examples for the FDL_LIFE_LIST_CREATE_REMOTE

Service

This service is not implemented

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 42

12.9.4 Program Example for the FDL_LIFE_LIST_CREATE_LOCAL

Service

For the example, DB 143 is set up to store the request and confirmation

data.

The following parameters must be specified for the FMA service

FDL_LIFE_LIST_CREATE_LOCAL:

com_class : 00 = request

service_code : 1BH= FDL_LIFE_LIST_CREATE

_LOCAL

After accepting the confirmation block with the HDB RECEIVE, the values

are entered in the DB and can then be processed further by the user

program.

DB 143 Explanation

0: KH = 0000;

1: KY = 000,000

2: KY = 027,000

3: KY = 000,000

4: KY = 000,000

5: KH = 0000;

6: KY = 000,000

7: KY = 000,000

8: KY = 000,000

9: KY = 000,000

**** RE QUE ST_ HEA DER** ** **

com_class / user_id

ser vi ce_code / no significance

no significance / no significance

******CONFIRMATION*******

com_class / user_id

ser vi ce_code / link_status

no significance / no significance

10:KM = 00000000 00000000

11:KM = 00000000 00000000

12:KM = 00000000 00000000

13:KM = . ...

14:KM = . ...

15:KM = . ...

16:KM = . ...

17:KM = . ...

Status TN 00 / Status TN 01

Status TN 02 / Status TN 03

Status TN 04 / Status TN 05

.....

Table 12.19 DB 143

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 43 Volume 1

The structure of the user program for sending the request and receiving the

confirmation is exactly as described for the FMA service

FDL_READ_VALUE (refer to Section 12.9.1). The differences simply result

from using a different DB for storing the request or confirmation block .

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 44

12.9.5 Program Example for the FDL_IDENT Service

For the example, DB 144 is set up to store the request and confirmation

data.

The following parameters must be specified for the FMA service

FDL_IDENT:

com_class : 00H= request

service_code : 1CH= FDL_IDENT

rem._add._station : 0AH= address of the receiver

After accepting the confirmation block with HDB RECEIVE, the values are

entered in the DB and can be read out.

DB 144 Explanation

0: KH = 0000;

1: KY = 000,000

2: KY = 028,000

3: KY = 000,000

4: KY = 002,000

5: KH = 0000;

6: KY = 001,000

7: KY = 028,000

8: KY = 000,000

9: KY = 002,000

10:KH = 0000;

11:KH = 0000;

12:KS = ’ ’;

13:KS = ’ ’;

14:KS = ’ ’;

**** RE QUE ST_ HEA DER** ** **

com_class / user_id

ser vi ce_code / no significance

no significance / no significance

rem_add_station / no significance

******CONFIRMATION*******

com_class / user_id

ser vi ce_code / link_status

no significance / no significance

rem_add_station / no significance

ident buffer (LE1/LE2)

(LE3/LE4)

....

Table 12.20 DB 144

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 45 Volume 1

Example of DB 144 with identification data of the station:

DB144 Explanation

0: KH = 0000;

1: KY = 000,000

2: KY = 028,000

3: KY = 000,000

4: KY = 002,000

5: KH = 0000;

6: KY = 001,000

7: KY = 028,000

8: KY = 000,000

9: KY = 002,000

**** RE QUE ST_ HEA DER** ** **

com_class / user_id

ser vi ce_code / no significance

no significance / no significance

rem_add_station / no significance

******CONFIRMATION*******

com_class / user_id

ser vi ce_code / link_status

no significance / no significance

rem_add_station / no significance

10:KH = 020A;

11:KS = ????;

15:KH = 3232;

16:KS = ????;

23:KH = ????;

24:KS = ????;

27:KH = ????;

28:KS = ????;

32:KS = ????;

33:KH = 0101;

34:KH = 0101;

35:KH = 0101;

36:KH = 0101;

37:KH = 0101;

38:KH = 0101;

39:KH = 0101;

40:KH = 0101;

41:KH = 0101;

42:KH = 0101;

43:KH = 0101;

44:KH = 0101;

Length byte 1; Length byte 2

Length byte 3, Length byte 4

CP 5430 TF

Siemens AG

V x.y

Table 12.21 DB 144

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 46

The structure of the user program for sending the request and receiving the

confirmation is exactly as described for the FMA service

FDL_READ_VALUE (refer to Section 12.9.1). The differences simply result

from using a different DB for storing the request or confirmation block .

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 47 Volume 1

12.9.6 Program Example for FDL_READ_STATISTIC_CTR Service

For the example, DB 145 is set up to store the request and confirmation

data.

The following parameters must be specified for the FMA service

FDL_READ_STATISTIC_CTR:

com_class : 00H= request

service_code : 1DH= FDL_READ_STATISTIC_CTR

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 48

After accepting the confirmation block with HDB RECEIVE, the values are

entered in the DB and can be read out.

DB 145 Explanation

0: KH = 0000;

1: KY = 000,000

2: KY = 029,000

3: KY = 000,000

4: KY = 010,000

5: KH = 0000;

6: KY = 000,000

7: KY = 000,000

8: KY = 000,000

9: KY = 000,000

**** RE QUE ST_ HEA DER** ** **

com_class / user_id

ser vi ce_code / no significance

no significance /no significance

no significance / no significance

******CONFIRMATION*******

com_class / user_id

ser vi ce_code / link_status

no significance / no significance

no significance/ no significance

10:KH = 0000;

11:KH = 0000;

12:KH = 0000;

13:KH = 0000;

14:KH = 0000;

15:KH = 0000;

16:KH = 0000;

17:KH = 0000;

18:KH = 0000;

19:KH = 0000;

20:KH = 0000;

21:KH = 0000;

22:KH = 0000;

23:KH = 0000;

24:KH = 0000;

25:KH = 0000;

26:KH = 0000;

invalid_start_delimiter_ctr

invalid_fcb_fcv_ctr

invalid_token_ctr

collision_ctr

wrong_fcs_or_ed_ctr

frame_error_ctr

char_error_ctr

retry_ctr

start_delimiter_ctr

stop_receive_ctr

send_confirmed_ctr

send_sdn_ctr

Table 12.22 DB 145

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 49 Volume 1

The structure of the user program for sending the request and receiving the

confirmation is exactly as described for the FMA service

FDL_READ_VALUE (refer to Section 12.9.1). The differences simply result

from using a different DB for storing the request or confirmation block .

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 50

12.9.7 Program Example for FDL_READ_LAS_STATISTIC_CTR

Service

For the example, DB 146 is set up to store the request and confirmation

data.

The following parameters must be specified for the FMA service:

FDL_READ_LAS_STATISTIC_CTR:

com_class : 00H= request

service_code : 1EH= FDL_READ_LAS_STATISTIC_CTR

After accepting the confirmation block with HDB RECEIVE, the values are

entered in the DB and can be read out.

DB 146 Explanation

0: KH = 0000;

1: KY = 000,000

2: KY = 030,000

3: KY = 000,000

4: KY = 000,000

5: KH = 0000;

6: KY = 000,000

7: KY = 000,000

8: KY = 000,000

9: KY = 000,000

**** RE QUE ST_ HEA DER** ** **

com_class / user_id

ser vi ce_code / no significance

no significance / no significance

******CONFIRMATION*******

com_class / user_id

ser vi ce_code / link_status

no significance / no significance

10:KH = 0000;

11:KY = 000,000;

12:KH = 000,000;

13:KH = 000,000;

14:KH = 000,000;

15:KH = 000,000;

las_cycle_ctr (reference)

1st act. station / 2nd act. stati on

3rd act. station / 4t h act. station

1x:KH = 000,000; nth act. station

Table 12.23

B89 7606 0/0 2 Serv ice a nd Diag nost ics us ing FM A Fu ncti ons

12 - 51 Volume 1

The structure of the user program for sending the request and receiving the

confirmation is exactly as described for the FMA service

FDL_READ_VALUE (refer to Section 12.9.1). The differences simply result

from using a different DB for storing the request or confirmation block . ❑

Service and Diagnostics using FMA Functions B8976060/02

Volume 1 12 - 52

13 Clock Services

The CP 5430 TF/CP 5431 FMS clock function is implemented by a clock

chip and clock software that uses the clock chip (cl ock task).

There are two basic clock functions:

1. The clock keeps the time on the CP 5430 TF/CP 5431 FMS within the

absolute limits of accuracy described in the technical data. This clock

continues to run during a power down as long as the battery voltage is

present.

2. The clock can also be used to synchronize synchronization frames so

that all the CP 5430 TF/CP 5431 FMS modules connected to the

SINEC L2 network and involved in synchronization have a relative de-

viation of 20 ms from each other. The transmitter of the clock message

must be the CP 5430 TF/CP 5431 FMS.

The clock message has a fixed format for SINEC which corresponds to the

TF standard (refer to Fig. 13.1). The transmitter has SAP 55 reserved for

transmitting the time of day message. The user does not need to assign

parameters to this, since the clock software does this automatically.

When using the FMA services and clock function at the same time,

remember the following special feature of the CP:

☞ If the CP is the active time transmitter (clock master) on the

L2 bus and an FMA service is triggered at the same time, this

may lead to the cyclic transmission of the time of day being

delayed.

C8976060/02 Clock Services

13 - 1 Volume 1

Bit position for serial

transmission via L2

More significant part

Less significant part

reserved

Correction value (in 1/2 h)

for representing local time

Sign for correction

(0=forwards, 1= backwards)

1 = synchronization failed

Alternative synchronization

on LAN (not implemented)

1 = time jump

(not implemented)

Resolution: 01 = 10 ms

Time value not correct

(not implemented)

reserved

8--------------------1

0 0 0 0 t t t t

t t t t t t t t

d d d d d d d d

S c c c c 0 0

0 0 t a a j e n

Time of day:

Milliseconds relative

to 0:00 o’clock

Date:

Days relative to

01.01.84

Status

Fig. 13 .1 Representation of Time and Status on the Bus

Cloc k Se rvice s C8 97 6060 /02

Vol ume 1 13 - 2

13.1 Network Topology, Clock Master/Slave Functions

Within a SINEC L2 network, all the CP 5430 TF/CP 5431 FMSs can

execute clock functions. The aim is to achieve network-wide clock

synchronization.

The synchronization can be performed by one selected CP 5430 TF/CP

5431 FMS.

The station that transmits the clock synchronization frames is known as the

"clock master".

In this case, all other stations are "clock slaves".

The CP 5430 TF/CP 5431 FMS can take over the functions of the clock

master if programmed accordingly.

The transmission of clock frames can be selected within a range between 1

and 60 seconds. The value used by COM 5430 TF/CP 5431 FMS as the

default value is 10 s. This means that all slaves expect a synchronization

frame from the clock master after a maximum of 10 s. Otherwise, the clock

slaves attempt to take over the clock master function (only the highest

priority clock slave station is successful, provided this is programmed as

DYNAMIC CLOCK MASTER i n COM 5430 TF/CP 5431 FMS).

The order of priority in which the stations take over the clock master

function is selected when the station address is assigned.

CP 5430 TF

Station I

CP 5430 TF

Station II

CP 5430 TF

Station n

CP 5431 FMS

CP 5431 FMS CP 5431 FMS

Fig. 13 .2 Netw ork To pology

C8976060/02 Clock Services

13 - 3 Volume 1

The station address is defined as the L2 address:

Based on the L2 address, a time is stipulated after which the station

attempts t o become cloc k master.

The following terms are important:

➣Delay Time,

corresponds to the L2 address in seconds.

➣Update Time,

select ed time interval for transmitting clock synchronization frames.

➣Undefined Time

sum of the delay time and update time.

By taking the L2 address as the delay time, a priority is established for

stations attempting to take over the clock master functions.

Cloc k Se rvice s C8 97 6060 /02

Vol ume 1 13 - 4

Example:

the following table shows which station takes over the clock master function

and if this fails, which station will replace it.

☞Since in L2 the individual station addresses must be different

from each other, the delay times cannot overlap .

This concept ensures that there is always clock synchronization within the

network.

Status

Master

Slave

Dyn. Master

Delay Time

Slave Y12

Slave Y13

Slave N18

Slave N21

Slave N01

!=!etc.

Master possible

Master not

possible

Priority assigned based

on the delay time

C8976060/02 Clock Services

13 - 5 Volume 1

13.2 How the Clock Functions

The clock can have the following statuses:

Description of the status transitions

1. When the CP starts up, the hardware clock of the CP 5430 TF/CP

5431 FMS is checked.

2. The status of the hardware clock was recognized as invalid. The clock

must be reset.

3. The status of the hardware clock was recognized as valid, i.e. the

hardware clock has already been set.

4. If during the CP start-up the clock is recognized as valid, the CP auto-

maticall y assumes the "clock_slav e" status.

Start-up

Clock

valid

= "invisible" CP operating statuses

= "visible" CP operating statuses

Power

OFF

Clock

invalid

Clock

slave Clock

master

Fig. 13 .3 Clock Statuses

Cloc k Se rvice s C8 97 6060 /02

Vol ume 1 13 - 6

5. During the undef ined time, no synchronization frame was received. The

CP therefore attempts to take over the clock master function.

6. The current clock master has received a synchronization frame from a

higher priority CP 5430 TF/CP 5431 FMS. The station once again as-

sumes the status of clock slave.

7. The CP with the clock slave status recognizes an invalid time (e.g.

defective hardware clock).

8. This status change is possible after receiving a valid clock frame from

the cloc k master from t he PG or from the PLC.

9. The CP with the clock master status recognizes an invalid time (e.g.

defective hardware clock).

C8976060/02 Clock Services

13 - 7 Volume 1

13.3 Several CP 5430 TF/CP 5431 FMS Modules on a

SINEC L2 Bu s

Dynamic clock masters can be configured on an L2 bus. The L2 address

determines which CP 5430 TF/CP 5431 FMS assumes the clock master

function. A double definition is not possible.

The cl ock is programmed in the Edit->Clock_Init screen.

The values entered in the screen correspond to the defaults.

Clock master (Y/N):

Y The CP 5430 TF/CP 5431 FMS can become the clock master if it has

the highest priority and can transmit clock synchronizat ion frames.

Clock Master Editor

Clock master

Sync cycle

10 sec.

CP Type:

Source:

OK SELECT

Fig. 13 .4 Edit -> Clock Init Screen

Cloc k Se rvice s C8 97 6060 /02

Vol ume 1 13 - 8

N The CP 5430 TF/CP 5431 FMS receives synchronization frames if they

exist in the L2 network.

Sync cycle: 10 (sec) default

If the CP 5430 TF/CP 5431 FMS is the clock master, it sends clock

synchronization frames to the SINEC L2 network at the time intervals

specified above.

Possible values: 1 - 60 sec.

OK The data edited in the screen are entered as the

current data.

SELECT Activating this key displays a selection list for each

input field that cannot be freely edited. Values can be

selected in the list using the cursor keys and entered

directly in the input field wit h the return key.

13.3.1 Setting and Reading the Time in the

Programmable Controller

The CP 5430 TF/CP 5431 FMS has the job number 218 available for

processing the time.

A SEND with this job number writes the CP’s time, a RECEIVE, reads the

CP’s time.

These services are possible on the synchronized CP interfaces using the

standard HDBs for the PLC.

☞When the CP starts up, internal test functions can lead to a

waiting time of 1 second before the clock can be read out

reliably from the PLC.

To provide the time for the programmable controller, the following

representation is used:

C8976060/02 Clock Services

13 - 9 Volume 1

Data format of the time in a DB of the PLC (S5 155 U format)

Possible values (hexadecimal):

1/100 seconds:

1/10 seconds

units seconds

tens seconds

units minutes

tens minutes

units hours

0...9

0...5

0...9

0...5

0...9

tens hours 0...1 / 0...2

bit 15 = 1: 24-hour format

bit 14 = 0: AM

bit 15 = 1: PM

Weekday

units days

tens days

units months

tens months

units years

tens years

Mo.. .Su = 0...6

0...9

0...3

0...9

0...1

0...9

Correction v alue:

The correction value corresponds formally to the correction value for

representing the local time (refer to Fig. 13.1) from the SINEC clock frames

Bit 0...5 deviation in 1/2 hour 0..24

Bit 7 sign 0 = plus (+) / 1 = minus (-)

15 12 11 8 7 4 3 0

DW n: tens sec units sec 1/ 10 sec 1/100 sec

DW n+1: tens hr units hr tens min units min

DW n+2: tens day units day weekday 0

DW n+3: tens year units year tens month units month

DW n+4: correction value

Cloc k Se rvice s C8 97 6060 /02

Volume 1 13 - 10

The following identifiers are possible replies to a "set time" job from the

PLC.

(d ecod ed ID s) Identifier Meaning

OK, n o error 0 0HCommand could be executed

without error.

Proto col error 0 1HT ime is in valid (was not se t etc. ).

System erro r 0EHSy st em error (e.g. i nvalid command).

Hardware clock 0FHHardware clock has failed.

C8976060/02 Clock Services

13 - 11 Volume 1

The followi ng identifiers are possible as the reply t o a "read time" job of t he

PLC.

Reply Identifier Meaning

System error 0EHSystem err or (e.g. wi th inval id

command).

Hardware c lock 0 FHHardware clock has failed.

Clock_Master 06HCP is clock master and

ex ec ut es t hi s fu nc ti on .

Clock_Slave 07HCP is clock slave.

Clock_Slave, + invalid 08HStation has an invalid clock

chip, clock must be reset.

Clock_Slave, + asynchronous 09HStation not recei vi ng clock

frame.

Slave, >master

Master,>slave

0BH

0AH

CP is clock slave; prepare for

master function.

CP is clock master; prepare for

slave function.

Subst synchron 0CHCP is synchronized by a CP

5430 TF/ CP 5431 FMS.

Cloc k Se rvice s C8 97 6060 /02

Volume 1 13 - 12

When the CP is starting up, the lower two bits of the status word are set to

"set clock" and "read clock" not possible. During normal operation, these

bits are set according to the CP clock status.

After the HDB has been run through successfully (Receive or Send), the

number of accepted or transferred data is entered in the length word.

Receive possible

Job active

0 0

0 1

1 0

1 1

Set clock

yes

Read clock

yes

06H..0FH free

ANZW

Length word

Identifier X X

Fig. 13 .5 ID i n th e Stat us W ord of the Han dling Bloc ks ( HDBs)

C8976060/02 Clock Services

13 - 13 Volume 1

13.4 Setting and Reading the Time with COM 5430

TF/CP 5431 FMS

Using COM 5430 TF/CP 5431 FMS, it is possible to both set the hardware

clock of the CP 5430 TF/CP 5431 FMS as well as to read the current time

cyclically.

The clock can only be read when it is in one of the following statuses:

➣Clock master

➣Clock slave substitute sync

➣Clock slave asynchronous

➣Slave > master

➣Master > slave.

The time can be set in the following statuses:

➣Clock master

➣Clock slave substitute sync

➣Clock slave invalid

Cloc k Se rvice s C8 97 6060 /02

Volume 1 13 - 14

In the NCM menu, the following screen can be called under the menu item

Utiliti es -> Clock Functions.

A clock read frame is then sent to the selected CP 5430 TF /CP 5431 FMS.

The screen is completed with the received data and functions are available

depending on the CP clock status.

When reading the time, an ID byte is supplied to the CP protocol which

provides information about the current status of the clock chip. The decoded

IDs are entered in the field "CP clock status".

UPDATE The PG requests the time cyclically. The CP clock

status is also updated.

WEEKDAY:

DATE TODAY:

CURRENT TIME:

TIME DIFFERENCE (1/2 H):

CLOCK MASTER :

CP CLOCK STATUS:

CP type:

Source:

Read Date/Time

UPDATE SET

(EXIT)

Fig. 13 .6 Clock Fu nctions Scre en

C8976060/02 Clock Services

13 - 15 Volume 1

SET The time can only be set when the CP status is "master

clock" or "clock_slave_asynchronous" or when the clock

chip of the CP 5430 TF/CP 5431 FMS is marked as

invalid.

Displays in the COM 5430 TF/CP 5431 FMS screen

WEEKDAY: MONDAY - SUNDAY

DATE TODAY: e.g. 29. 10. 1993

The data can be set within the limits 01.03.1984 to

31.12 2083.

CURRENT TIME: e.g. 15: 23:43

TIME DI FF-

ERENCE (1/2 H): "+" or "-" and range between 0 and 24

CLOCK MASTER: Indicates whether the current CP 5430 TF/CP 5431

FMS is the clock master or is a clock slave.

CP CLOCK

STATUS: CLOCK MASTER

the clock sends synchronization frames

CLOCK SLAVE

the clock receives synchronizat ion frames

CLOCK SLAVE,+ INVALID

the clock must be set

CLOCK SLAVE,+ ASYNCHR

clock does not receive synchronizati on frames

SLAVE <--> MASTER

clock status change

TRANSMITTER ASYNCHR

time transmitter is itself asynchronous

SUBST SYNCHRON

the clock is synchronized from a CP 5430 TF/CP 5431

FMS

SYSTEM ERROR

an internal error has occurred

HW CLOCK FAILURE

hardware clock has failed

Cloc k Se rvice s C8 97 6060 /02

Volume 1 13 - 16

13.5 Restrictions / T ips

The time should be read or set by the programmable controller (with

RECEIVE) at a time interval > 10 ms.

a) The hardware clock of the CP 5430 TF/CP 5431 FMS itself only has a

resoluti on of 10 ms.

b) By reading or setting the clock too quickly (cyclically) PLCs, the CP

5430 TF/CP 5431 FMS can be influenced to such an extent that the

module is di sabled for other ac tiviti es.

To avoid loading the SINEC L2 bus with unnecessary time frames, a

synchronization time greater than 10 seconds should be selected.

To ensure that the CP functions correctly, the following points must be

taken into account:

➣The cycle time for synchronization frames on every CP 5430 TF/CP

5431 FMS must be the same. The default cycle time is 10 seconds (can

be modified in the Clock Init screen).

➣At least one dynamic clock master must be configured.

C8976060/02 Clock Services

13 - 17 Volume 1

13.6 Accuracy

The hardware clock of the CP 5430 TF/CP 5431 FMS has a maximum

deviation of 11.94 s/day or 8.3 ms/min. This deviation is based on a

calculation involving t he quartz inaccuracy and temperature fluctuation.

➣Absolute accuracy

The absolute accuracy of the clock chip on the CP 5430 TF/CP 5431

FMS is in the worst case +/- 11.94 sec per day.

For this reason, it is necessary to compensate for this deviation in the

CP 5430 TF/CP 5431 FMS hardware clock by receiving synchronization

frames.

The time is kept on the hardware clock of the CP 5430 TF/CP 5431

FMS with a resolution of 10 ms.

To achieve a system-wide clock accuracy in the programmable

controllers, a time difference of 20 ms must not be exceeded. This is

achieved by time of day synchronization.

➣Relative accuracy

If the times on the SINEC H1 relative to each other should not deviate

by more than 20 ms, the rel ationship between t he Ethernet address (ID)

and cycle time of the synchronization frame must be borne in mind.

Once it is running, if the CP sends a synchronization frame, the

following deviations are possible providing the CP is only functioning as

clock master.

Cycle time 1 sec 10 sec 60 sec

Deviation 0.28 ms/s 2.77 ms/10s 16.6 ms/min

Table 13.1 Accuracy

Cloc k Se rvice s C8 97 6060 /02

Volume 1 13 - 18

If the CP is in a transitional status, i.e. it has not received a synchronization

frame, and is attempting to become master, then depending on the L2

address, larger deviations are possible (refer to Table 13.2). The bus

parameters are not included in these calculations. Depending on the real

CP load and parameter settings, greater deviations in the accuracy may be

possible.

❑

L2 address Cycle time and resulting deviations in the time of day

1 s 10 s 60 s

2 0.55 ms/s

0.83 ms/s 3.04 ms/10s

3.32 ms/10s 16.58 ms/min

16.86 ms/min

::::

11 19.38 ms/min

19.66 ms/min

::::

21 8.36 ms/10s

8.64 ms/10s

::::

31 8.67 ms/s

8.95 ms/s

Table 13.2 Status Transitions

C8976060/02 Clock Services

13 - 19 Volume 1

NOTES

14 Documentation and Testing

The screens required for documentation or testing are provided by SINEC

NCM as l isted in Fig. 14.1 and Fig. 14.2.

14.1 Documentation Functions

To give you the opportunity of producing lists with your programming, the

following documentation and print functions are integrated.

= Init Edit ...

SINEC NCM

Basic functions I/Os TF Objects FMS Objects

CP Init

I/O

Areas

Edit -> Documentation

Global Netw.

Parameters All

Local Netw.

Parameters

VMD

Table All

All

Global

I/Os

Cyclic

I/Os

Application

Associations

Menu item Edit

S5-S5

Links Free L2

Links

Table VFD

Table

DP Slave

Parameters

CP 5430 TF

CP 5431 FMS

DP Editor Cyclic

Interface

Fig. 14 .1 Menu Structure Documentation

B8976060/02 Documentation, Test

14 - 1 Volume 1

With footer on/off in the "Init -> Edit" screen (Chapter 6, Fig. 6.7) you can

specify a footer file in which you saved a footer for the printout using the

S5-DOS footer editor.

With "Printer output on/off" in the screen (Chapter 6, Fig. 6.7) you can

decide whether t o output solely on the screen or on both printer and screen.

☞Make sure that your printer is switched on.

To activate the documentation functions, select the

appropriate menu item in the documentation menu in SINEC

NCM.

= Init Edit ...

SINEC NCM

Topology

All

Network -> Documentation

Menu item Network Request Editor -> Documentation

Menu item Utilities

All Job

Buffer

Overview

ZP CI GP DP

Applic. Associations Applic. Associations

CP 5431 FMS

CP 5430 TF

Fig. 14 .2 Menu Structure Network Documentation

Doc umen tat ion, T est B8 9760 60/02

Vol ume 1 14 - 2

14.2 Test

Suitable test and diagnostic tools are particularly important when installing

SINEC L2 networks. For this reason, the software package COM 5430

TF/COM 5431 FMS under SINEC NCM provides a number of test functions.

To allow you to test your configuration, the test and diagnostic functions

shown in Fig. 14.3 were integrated in

➣S5-S5/free layer 2

➣GP (global I/Os)

➣ZP (cycl ic I/Os) (only wi th CP 5430 TF)

➣DP (distributed I/Os)

➣FMA

The TF/FMS test functions are described in Volume 2.

Total Status

= Init Edit ...

SINEC NCM

Test

Global I/Os

Test S5S5/Free L2

Links Cyclic Interface FMA Test Functions

Total Status Output Values Input Values

Output Values Input Values Local Life List Station Statistics Bus Statistics

Total Status

Single Status

Distributed I/Os

Test App. Ass.

(Volume 2)

Total Status

Single Status

ALI Total Status

(Volume 2)

CP 5430 TF

CP 5431 FMS

Cyclic I/Os

Fig. 14 .3 Menu St ructure Test

B8976060/02 Documentation, Test

14 - 3 Volume 1

☞With the test functions, only the data exchange between the

PLC and CP via the S5 backplane bus is monitored. The data

transmission from the CP on the L2 bus cannot be checked

with the test functions (to check this traffic, use the SINEC L2

bus monitor "SCOPE L2"). If PLC or bus errors occur, COM

5430 TF/COM 5431 FMS uses the various messages contained

in the status word (ANZW) of the handling blocks and the

link_status of the confirmation header.

14.2.1 S 5-S5/ F ree L2 - Test Functi ons

With the S5-S5 / free L2 link test functions, you can determine the status of

individual parts of the system during communication and localize any errors

that are detected.

Doc umen tat ion, T est B8 9760 60/02

Vol ume 1 14 - 4

14.2.1.1 Total St atus

The screen has the following structure (examples of parameters):

Output fields:

L2 station

address Station, with which the test functions are performed.

Sel: Indicates a selection.

POS: Number of the li nk.

SSNR: Page number via which the communication between the

CP and PLC i s handled.

ANR: Job number, identi fies the confi gured li nks.

L status: Link status displayed coded in hex (s ee Table 14.1).

Total Status S5S5 / Free Layer 2 Links

L2 station address: 8

Sel. POS SSNR ANR L status J type J status J error Cha

101

200

0120

Send- S5S5

0001

Recv- S5S5

Send- FMA 0000

0000

UPD ON SING STAT SELECT DESELECT

Message line

CP Type:

Source: (EXIT)

HELP

Fig. 14 .4 Tota l Status Screen

B8976060/02 Documentation, Test

14 - 5 Volume 1

J type: Job type: the fol lowing job types can be distinguished:

SEND - S5-S5

RECV - S5-S5

SEND - F L 2

RECV - F L 2

SEND - FMA

RECV - FMA

J status: Job status (see Table 14.2).

J error: Job error with S5-S5/free layer 2 communication.

Cha: Indicates a status change with " * " .

Functi on keys:

UPD ON Using this key, you can update the content of the

screen. Pressing this key activates the automatic, cyclic

updating of the screen data, pressing it again

deactivates the automatic updating.

SI NG ST AT Changes to the single status of the link shown on a

gray background.

SELECT Select the lines marked by the cursor.

DESELECT Undo the selections.

Doc umen tat ion, T est B8 9760 60/02

Vol ume 1 14 - 6

Link statuses

Based on the link statuses, you can see the current status of a configured

link.

Hex value ID Meaning

0120HLINK_LAYER_2 Layer 2 link is established.

0180HCANNOT_EST Layer 2 link cannot be est ablished.

Table 14.1 Li nk Sta tuses

B8976060/02 Documentation, Test

14 - 7 Volume 1

Job status

Hex Meaning

0000HInitial status, no cur rent job exist s

0001HNo job processing at preset

0021HAwait-Indication Request field sent to layer 2.

0022HData being transferred to PLC

0023HCP waiting for transfer of an indication.

0024HError in indication transfer (FL2).

0025HError in the indication ( S5-S5) -> Await-Request field to layer 2.

0026HIncorrect request field transfer with send direct

0031HRequest f ield transfer to layer 2.

0032HCP waiting for request trigger from PLC

0033HCP wa iting for transfer o f a confir mation.

0034HError in confirmation transfer (FL2).

0035HError in the confirmation ( S5- S5) -> CP expects new trigger.

0036HIncorrect data acceptance with receive direct (S5-S5).

Table 14.2 Job Stat uses

Doc umen tat ion, T est B8 9760 60/02

Vol ume 1 14 - 8

Errors in S5-S5/free layer 2 commu nication

Er ror ID Meanin g

0000HNo error

0001HWrong block type for SEND-DI RECT.

0002HMemory area does not exist on PLC

0003HMemory area too small

0004HTimeout

0005HE rro r in s tatus word

0006HData too long or short for S5-S5 and FL2.

0007HNo local resources

0008HNo remote resources.

0009HRe mote e rror

000AHLink error

000CHSystem error

Table 14.3 Errors in S5-S5/Fre e Layer 2 Comm unication

B8976060/02 Documentation, Test

14 - 9 Volume 1

14.2.1.2 Single Status

The screen with the example parameters has the following structure:

Output fields:

L type: Link type:

"S5-S5" : S5-S5 link

"FDL" : free layer 2 link

"FMA" : FMA link

"DEFAULT" : link via default SAP

J type: Represent ation of the job in text form.

SEND - S5-S5

RECV - S5-S5

SEND - F L 2

RECV - F L 2

SEND - FMA

RECV - FMA

Single Status S5-S5 / Free Layer 2 Links

UPD ON

J ID

J status

J error

L status

L error

SEND- S5S5

0001

0000

0120

0000

L type

No job processing at present

S5S5

Local test data Remote test data

SSNR

ANR

Source SAP

L2 address

Remote SAP

L2 address

CP Type:

Source: (EXIT)

HELP

No error

Layer 2 link established

ACK positive

Fig. 14 .5 Single Status Screen

Doc umen tat ion, T est B8 9760 60/02

Volume 1 14 - 10

J status: Job status. Presentation of the action coded (see Table

14.2) and i n t ext form .

J error: Job error in S5-S5/free layer 2 communication (see

Table 14.3) and in text form.

L status: Displays the link status coded (hexadecimal) (refer to

Table 14.1) and in text form.

L error: Link error FDL err or message (see T able 14.4).

SSNR: Page via which the PLC and CP communi cate.

ANR: Job number. Identifies the configured link

Source SAP/

Remote SAP: Configured SAP; local or remote.

L2 address: L2 addresses of the local and remote station.

Functi on keys:

UPD ON Using this key, you can update the content of the

screen. Pressing this key activates the automatic, cyclic

updating of the screen data, pressing it again

deactivates the automatic updating.

B8976060/02 Documentation, Test

14 - 11 Volume 1

FDL error messages

These error messages are returned as the link status in the

acknowledgment (Confirmation).

ID link_status Meaning

L2_LST_OK 0x0000 ack. positive

L2_LST_UE 0x0001 rem. user interface error

L2_LST_RR 0x0002 no remote resour ces

L2_LST_RS 0x0003 rem service or SAP error

L2_LST_DL 0x0008 r esp. data low available

L2_LST_NR 0x0009 no resp. data rem.

L2_LST_DH 0x000a resp. data high available

L2_LST_RDL 0x000c neg. ack., resp. data low available

L2_LST_RDH 0x000d neg. ack., resp. data high available

L2_LST_LS 0x0010 service not allowed locally

L2_LST_NA 0x0011 no reaction from rem. station

L2_LST_DS 0x0012 l ocal station not i n ring

L2_LST_NO 0x0013 neg. ack., function-dependent

L2_LST_LR 0x 0014 no local resources

L2_LST_IV 0x0015 invalid parameter in r equest

L2_LST_LO 0x0020 low resp. data send

L2_LST_HI 0x0021 high resp. data send

L2_LST_NO_DA

TA 0x0022 no data resp. data send

Table 14.4 FDL Error Me ssages

Doc umen tat ion, T est B8 9760 60/02

Volume 1 14 - 12

14.2.2 GP Test F unctions

With the GP test funct ions, the user can determine the statuses of individual

parts of the system and localize any errors from the PG.

14.2.2.1 Total St atus of t he GP Jobs

The total status of the GP jobs provides you with an overview of all or some

of the data transmission statuses. The status job requests the statuses of

the station from the point of view of the local station.

Up to 32 stations and their statuses can be displayed in two columns. The

local station is highlighted. Other functions are explained with the softkeys.

The screen has the following layout:

Test Functions / GP Total Status

UPD ON

GP inp PLC stat

add Cycle

error GP inp PLC stat

add Cycle

error

CP type:

Source: (EXIT)

HELP

Fig. 14 .6 GP- Total Stat us

B8976060/02 Documentation, Test

14 - 13 Volume 1

Output fields:

L2 add: Here, the L2 addresses of the master stations in the

logical ring are displayed.

GP inp: "X" indicates all the stations from which GP input bytes

are expected.

PLC stat: Indicates the PLC status. The status can only be RUN

or STOP .

Cycle errors: A data delay is indicat ed by "X".

Functi on keys:

UPD ON Using this key, you can update the content of the

screen. Pressing this key activates the automatic, cyclic

updating of the screen data, pressing it again

deactivates the automatic updating.

Doc umen tat ion, T est B8 9760 60/02

Volume 1 14 - 14

14.2.2.2 Display of the GP Ou tput Values

The GP output values are displayed as bytes in ascending order.

The screen with the example parameters has the following structure:

Output fields:

L2 station-

address: The L2 address of the master station is display ed here.

Status of GP: Indicates the current status of the GP. The status can

only be RUN (GP act ive) or STOP (GP was st opped).

Sel: Indicates with an asterisk that a line is selected.

Test Functions / GP Outputs

UPD ON

L2 station address: 2 RUN

Sel. Pos. Output Value

PY20 KH= 0 KM= 0000 0000

PY21 KH= 0 KM= 0000 0000

STOP START STEP SELECT DESELECT

Status of GP:

GPY 100

GPY 101

Symbol

CP type:

Source: (EXIT)

HELP

Fig. 14 .7 GP Output Values

B8976060/02 Documentation, Test

14 - 15 Volume 1

Pos:Line index.

Output: Physical as signment of the output bytes of this station.

GO: Global Object or object name of the output.

Symbol: Symbolic name of the output.

Value Value of the output in KH (hexadecimal) and KM (bits).

Functi on keys:

UPD ON Using this key, you can update the content of the

screen. Pressing this key activates the automatic, cyclic

updating of the screen data, pressing it again

deactivates the automatic updating.

STOP With this key, you can send a stop message to the GP.

The output values are then no longer updated. The

status field then changes to STOP.

START With this key, you can send a start message to the GP.

The output values are then no longer updated. The

status field then changes to RUN.

STEP With this key, you can update the GP output bytes

once. The status field then changes to STOP.

SELECT Using this key, or the enter key, you can select lines

from the complete list of the outputs screen by marking

them with the inverse bar controlled by the cursor keys.

These selected lines are then the only lines displayed

after pressing the update key F1. You exit this mode

with the ESC key.

Doc umen tat ion, T est B8 9760 60/02

Volume 1 14 - 16

DESELECT With this key, you can cancel the selection made with

F7.

With the page up and page down keys you can page through the lines of

the screen if t hey cannot al l be di splayed.

B8976060/02 Documentation, Test

14 - 17 Volume 1

14.2. 2.3 Display of th e G P I nput Values

The GP input values are displayed as byes in ascending order. The screen

has the f ollowi ng layout:

Output fields:

L2 station

address: The L2 address of the master station is display ed here.

Incorrectly

programmed

station:

Here, the first station is displayed that sent an incorrect

GP by t e.

Test Functions / GP Inputs

UPD ON

L2 station address: 2

Sel. Pos. GO Value

GPB 10 KH= 0 KM= 0000 0000

GPB 11 KH= 0 KM= 0000 0000

SELECT DESELECT

Incorrectly programmed station:

Input

PB 10

PB 11

Sender

n.e.

Error

CP type:

Source: (ENDE)

HELP

Fig. 14 .8 GP Inpu t Values

Doc umen tat ion, T est B8 9760 60/02

Volume 1 14 - 18

Sel: Indicates with an asterisk that a line is selected.

Pos: Line index.

GO: Global object or object name of the input.

Input: Physical assignment of the input bytes of this station.

Sender: L2 address of the GP sender. A GP byte, that has not

yet been received cannot be assigned to a sender and

is marked as n.e. (non-existent).

Value: Value of the input in K H ( hexadecimal) and KM (bit s).

Error: "X" indicates that a GP byte was received from two

different stations .

Functi on keys:

UPD ON Using this key, you can update the content of the

screen. Pressing this key activates the automatic, cyclic

updating of the screen data, pressing it again

deactivates the automatic updating.

SELECT Using this key, or the enter key, you can select lines

from the complete list of the input values screen by

marking them with the inverse bar controlled by the

cursor keys. These selected lines are then the only

lines displayed after pressing the update key F1. You

exit this mode with the ESC key.

DESELECT With this key, you can cancel the selection made with

F7.

B8976060/02 Documentation, Test

14 - 19 Volume 1

With the page up and page down keys you can page through the lines of

the screen if t hey cannot al l be di splayed.

Doc umen tat ion, T est B8 9760 60/02

Volume 1 14 - 20

14.2.3 ZP Test Functions (CP 5430 TF)

With the ZP test functions you can determine the status of individual parts

of the system during communication and localize any errors that are

detected on the PG.

14.2.3.1 Total St atus of t he ZP Jobs

The total status of the ZP Jobs is displayed in the form of lists. The screen

has the f ollowi ng struct ure:

Output fields:

L2 station

address: The L2 address of the master station is display ed here.

Sel: Indicates with an asterisk that the line is selected.

Test Functions / ZP Total Status

UPD ON

L2 station address: 1

Sel.

SELECT DESELECT

INPUTS OUTPUTS

Pos.

Rem. add.

DSAP

Output area

from to Input area

from to

PB 8 PB 8

Status

CP Type:

Source: (EXIT)

HILFE

Fig. 14 .9 ZP Tota l Statu s

B8976060/02 Documentation, Test

14 - 21 Volume 1

Pos: Display position. links are displayed in ascending order

(0-255).

rem. add.: Address of the remote station.

DSAP: Remote SAP of the configured link.

Output area: Physical output area of a ZP link.

Input area: Physical output area of a ZP link.

M: Specifies how often a station is entered in the polling

list.

Status: Provides the status of the selected station

(hexadecimal) (see Table 14.4 and Table 14.5).

Functi on keys:

UPD ON Using this key, you can update the content of the

screen. Pressing this key activates the automatic, cyclic

updating of the screen data, pressing it again

deactivates the automatic updating.

INPUTS This calls the screen for the inputs of the currently

selected link. Using the cursor keys, you can select a

line with the inverse bar and examine it more closely.

OUTPUTS This calls the screen for the outputs of the currently

selected link. Using the cursor keys, you can select a

line with the inverse bar and examine it more closely.

SELECT Using this key, or the enter key, you can select lines

from the complete list of the input values screen by

marking them with the inverse bar controlled by the

cursor keys. These selected lines are then the only

lines displayed after pressing the update key F1. You

exit this mode with the ESC key.

DESELECT With this key, you can cancel the selection made with

F7.

Doc umen tat ion, T est B8 9760 60/02

Volume 1 14 - 22

ID Status Meaning

ZP_ERR_START 0x00F0 Start- up ID

ZP_ERR_DIAG_REQ 0x00F1 Diagnostics request from ET200U

ZP_ERR_INP_TOO

_LONG 0x00F3 Input area> receive_len of frame

ZP_ERR_I_FRA_TOO

_LONG 0x00F4 Input area < receive_len of frame

Table 14.5 ZP Inte rnal Errors

B8976060/02 Documentation, Test

14 - 23 Volume 1

14.2.3.2 Display of the ZP Ou tput Values

The ZP output values are displayed as byes in ascending order. The screen

has the f ollowi ng layout:

Output fields:

L2 station

address Here, the L2 address of the local station is displayed.

ZP status: Displays the current status of the ZP. The status can

only be RUN (ZP act ive) or STOP (ZP was st opped).

Sel: Indicates with an asterisk that the line is selected.

Pos: Line index

Test Functions / ZP Outputs

UPD ON

L2 station address: 2

Sel. Pos. Output Value

0 PB32 KH= 0 KM= 0000 0000

SELECT DESELECT

Rem. add.

DSAP

ZP status: RUN

STOP START STEP

CP Type:

Source: (EXIT)

HELP

Fig. 14 .10 ZP Ou tputs

Doc umen tat ion, T est B8 9760 60/02

Volume 1 14 - 24

Output: Physical as signment of the output bytes of this station.

Rem. add: Remote L2 address or address of the remote station.

DSAP: Remote SAP of the configured link.

Value value of the output in KH (hexadecimal) and KM (bits).

Functi on keys:

UPD ON Using this key, you can update the content of the

screen. Pressing this key activates the automatic, cyclic

updating of the screen data, pressing it again

deactivates the automatic updating.

STOP With this key, you can send a stop message to the ZP.

The output values are then no longer updated. The

status field then changes to STOP.

START With this key, you can send a start message to the ZP.

The output values are then no longer updated. The

status field then changes to RUN.

STEP With this key, you can update the ZP output bytes

once. The status field then changes to STOP.

SELECT Using this key, or the enter key, you can select lines

from the complete list of the outputs screen by marking

them with the inverse bar controlled by the cursor keys.

These selected lines are then the only lines displayed

after pressing the update key F1. You exit this mode

with the ESC key.

B8976060/02 Documentation, Test

14 - 25 Volume 1

DESELECT With this key, you can cancel the selection made with

F7.

With the page up and page down keys you can page through the lines of

the screen if t hey cannot al l be di splayed.

Doc umen tat ion, T est B8 9760 60/02

Volume 1 14 - 26

14.2. 3.3 Display of th e Z P I nput Values

The GP input values are displayed as byes in ascending order. The screen

has the f ollowi ng layout:

Output fields:

L2 station-

address: The L2 address of the master station is display ed here.

Sel: Indicates with an asterisk that a line is selected.

Pos: Line index.

Input Physical assignment of the input bytes of this station.

Rem. add Address of the remote st ation.

Test Functions / ZP Inputs

UPD ON

L2 station address: 2

Sel. Pos. Input Value

PB36 KH= 0 KM= 0000 0000

PB37 KH= 0 KM= 0000 0000

SELECT DESELECT

Rem. add.

DSAP

2 PB38 KH= 0 KM= 0000 000060

CP type:

Source: (EXIT)

HELP

Fig. 14 .11 ZP I nputs

B8976060/02 Documentation, Test

14 - 27 Volume 1

DSAP: Remote SAP of the configured link.

Value: Value of the input in K H ( hexadecimal) and KM (bit s).

Functi on keys:

UPD ON Using this key, you can update the content of the

screen. Pressing this key activates the automatic, cyclic

updating of the screen data, pressing it again

deactivates the automatic updating.

SELECT Using this key, or the enter key, you can select lines

from the complete list of the input values screen by

marking them with the inverse bar controlled by the

cursor keys. These selected lines are then the only

lines displayed after pressing the update key F1. You

exit this mode with the ESC key.

DESELECT With this key, you can cancel the selection made with

F7.

With the page up and page down keys you can page through the lines of

the screen if t hey cannot al l be di splayed.

Doc umen tat ion, T est B8 9760 60/02

Volume 1 14 - 28

14.2.4 DP Test Functions

With the DP Test Functions you can find out the statuses on individual DP

slaves and the DP master ONLINE and to localize any errors.

14.2.4.1 DP T otal Status

The test function total status of the DP jobs displays a list of the

communications statuses of all configured DP slaves. The screen has the

following layout:

Output fields:

PLC status: Indicates the PLC status. The status can only be RUN

or STOP .

Test Functions / DP Total Status

UPD ON SING STAT SELECT DESELECT

CP Type:

Source: (EXIT)

HELP

PLC status

DP station status

DP station L2 add.

DP station poll. cyc. timeout

Cycl. global control from PLC

Sel. Slv.add. Name Vendor ID Group ID Passive Transfer Diagn.

3 ET200DP 8008 00000000

Fig. 14 .12 DP To tal Sta tus

B8976060/02 Documentation, Test

14 - 29 Volume 1

DP station

status: Local DP master mode wi th the following meaning:

RUN: DP polling list is processed.

STOP: DP polling list is not processed.

Clear: DP polling list is processed, all output data bytes

are sent with the value "0".

DP station

L2 add: Bus address of the DP master (CP).

DP station

poll. cyc. timeout: An asterisk indicates that the DP polling list could not

be processed in t he set time.

Cycl. global

control from PLC: An asterisk indicates that a cyclic

global_control control command is currently being

processed.

Sel: Indicates with an asterisk that a line is selected.

Slave address: Bus address of the DP slave.

Name: The names of the DP slaves specified in parameter

assignment are displayed here.

Vendor ID: The configured vendor identifier of the DP slave is

shown here.

Group ID: The group ID of the DP slave specified in parameter

assignment is displayed here.

Pass.: An asterisk here indicates that there is no parameter

assignment for this slave (neither an input nor output

area was specified in the DP editor).

Transfer: An asterisk here indicates that this slave is in the cyclic

data transfer phase with the master.

Diagn.: An asterisk here indicates that there are new diagnostic

data from t he slave.

Doc umen tat ion, T est B8 9760 60/02

Volume 1 14 - 30

Functi on keys:

UPD ON This key switches on automatic cyclic updating of the

screen data.

UPD OFF This key switches off automatic cyclic updating of the

screen data.

SING-STAT This key branches to the screen for the DP single

status. The selection criterion is the cursor position

(inverse bar).

SELECT Using this key, or the enter key, you can select lines

from the complete list of the outputs screen by marking

them with the inverse bar controlled by the cursor keys.

These selected lines are then the only lines displayed

after pressing the update key F1. You exit this mode

with the ESC key.

DESELECT With this key, you can cancel the selection made with

F7.

B8976060/02 Documentation, Test

14 - 31 Volume 1

14.2.4.2 DP Single Status

The screen for the test function "DP single status", which can be called in

the total status screen, has the followi ng layout:

Output fields:

Slave L2

address: Station addr ess of the DP slaves .

Slave name: The name of the DP slave specified in parameter

assignment is displayed here.

Master L2

address: Station address of the DP master, which assigned

parameters to and configured the DP slave.

Test Functions / DP Single Status

UPD ON

CP type:

Source: (EXIT)

HELP

Data being updated - CP in RUN

Slave

Master

Vendor

Group

PLC status

DP station status

DP station L2 address

DP station in ring

DP station - slave

ET200DP

8008

00000000

pass.

Station diagnos.:

StationNonExistent

StationNotReady

InvalidSlaveResponse

ServiceNotSupported

MasterLock

WatchdogOn

Device diagn.:

StaticDiag

ExtStatusMessage

ExtDiagMessage

ExtDataOverflow

SyncMode

FreezeMode

ParameterRequest

ParameterFault

SlaveConfigCheckFault

MasterConfigCheckFault

StatusFromSlave

No diagnostic data received

SlaveDeactivated :

L2 address

name

ID.

L2 address

ID&C DIAG

Fig. 14 .13 DP Single Status

Doc umen tat ion, T est B8 9760 60/02

Volume 1 14 - 32

Vendor ID: The configured vendor ID or (if possible) the vendor ID

sent by the slave is displayed here.

Group ID: The group ID of the DP slave specified in parameter

assignment is displayed here.

PLC status: The mode of the PLC is displayed here (RUN/STOP).

DP station status: Local DP master mode with the following meaning:

RUN: DP polling list is processed.

STOP: DP polling list is not processed.

Clear: DP polling list is processed, all output data bytes

are sent with the value "0".

DP station L2

address: Bus address of the DP master station (CP), on which

you have just selected the single status function.

DP station in

ring: yes/no: indicates whether or not the DP master station

(CP), on which you have just selected the single status

function is in the logical ring.

DP station

slave: active/passive, indicates whether the DP slave was

configured with (-> active) or without I/Os (-> passive)

in the DP editor.

Station

diagn.: For the meaning of the bits, refer to Section 11.7

"Single DP S lave Di agnostics").

Master Config

Check Fault: An asterisk here i ndicates that the DP master of the DP

slave detected a configuration error during the

initializat ion phase. Possible causes are:

- configured I/O area for the slave does not match the

DP Status Pol l active

slaves Q data:

PLC -> Slave s I data:

Slaves-> PLC

STOP

CLEAR

RUN

yes

yes, Q data= zero

yes

B8976060/02 Documentation, Test

14 - 33 Volume 1

DP slave I/O configuration

- DP slave works with consistent I/O areas,

but the free mode is configured on the CP.

Device

diagn.: Here, the general DP slave device-specific diagnostic

messages are displayed, see documentation of the DP

slave).

As soon as ID and/or channel-related diagnostic information exists, this is

indicated by COM.

After stopping the DP single status updating with F1, you can branch to the

ID and channel-related diagnostics with F3 "ID&C DIAG".

Functi on keys:

UPD ON This key switches on automatic cyclic updating of the

screen data.

UPD OFF This key switches off automatic cyclic updating of the

screen data.

ID&C DIAG This key branches to the ID and channel-related

diagnostics.

Doc umen tat ion, T est B8 9760 60/02

Volume 1 14 - 34

14.2.5 FMA Test Fu nctions

These test functions are used to read out the Layer 2 st ati stic s.

14.2.5.1 Local Life List

This screen contains a list of all the active and passive stations on SINEC

L2.

The screen has the following structure:

Output fields:

L2 address: The L2 addresses of all the stations in the logical ring

are displayed.

Station

status: Possible entries : "active station in the logical token r ing"

or "passive station in the logical token ring".

Local Life List

PAGE +

L2 address Station status

2 Active station in logical token ring

PAGE -

CP type:

Source: (EXIT)

1 Active station in logical token ring

Fig. 14 .14 Local Life List

B8976060/02 Documentation, Test

14 - 35 Volume 1

Functi on keys:

PAGE + Page one page forwards.

PAGE - Page one page backwards.

14.2.5.2 Station-oriented Statistics

This screen contains station-relat ed stati stic al information.

The screen has the following structure:

Station-oriented Statistics

Received frame with invalid start delimiter

Received frame with invalid FCB / FCV

Invalid token frames

Unexpected response frames

Received frame with wrong FCS or ED

Gaps in received frames

Transmission error (framing, parity, overrun)

Received frame with valid start delimiter

Reception aborted

00000000

00017003

CP type:

Source: (EXIT)

Fig.: 1 4.15 Station-oriented Statistics

Doc umen tat ion, T est B8 9760 60/02

Volume 1 14 - 36

Output fields:

Counted values about station statuses.

14.2.5.3 Bus-oriented Statistics

This screen contains bus-oriented statistical information to allow

assessment of the bus response.

The screen has the following layout:

Output:

Counted values about statuses that occurred on the bus. ❑

Bus-Oriented Statistics

Number of token rotations : 36149 (= reference)

Active

station Received token Active

station Received token

1 36149 2 36149

CP type:

Source: (EXIT)

Fig.: 1 4.16 Bus-oriented Statistics

B8976060/02 Documentation, Test

14 - 37 Volume 1

NOTES

15 Utilities

The following figure is an overview of all the utilities available under the

Utilities menu item. The individual utilities are described in this chapter.

= Init Edit ...

SINEC NCM

Bus

Request Editor

Volume 2 Sec. 15.1

Clock Functions

Chap. 13

Convert

(CP 5430 TF)

Sec. 15.3

Change Subm.

Size

Sec. 15.2

Utilities

Menu item

Selection

Fig. 15 .1 Overview of the Utilities

B8976060/02 Utilities

15 - 1 Volume 1

15.1 PG Functions on the SINEC L2 Bus

The PG functions on the SINEC-L2 Bus allow you to obtain, monitor and

configure stations (CPs, CPUs) in the network topology from a central PG.

A link f rom a PG to t he required station i s known as a path. Using this path,

all the normal programming functions can be executed as if a direct

point-to-point link existed. The selected devices or CPs on the path are

known as nodes.

There are basically two ways of configuring a path.

The PG has only one AS 511 interface:

☞If the end point is an S5-95U with a SINEC L2 interface and

there is no other station on the bus, it may not be possible to

establish the path on the PG interface.

PG AS 511 "Aux. CP"

"Dest CP" ENDP

(e.g. CPU connected to

dest. CP with a

"swing cable")

Fig. 15 .2 PG via AS 511 (Path _1)

Utilities B8976060/02

Vol ume 1 15 - 2

The PG has an internal L2 interface:

This path (see Fig. 15.2,15.3), symbolized by t he path name can be used to

monitor the selected station and if necessary to reconfigure it using the

appropriate software packages (COM, LAD/CSF/STL).

The two paths shown here are examples that can be ext ended and modified

to fit other topologies. It is, for example, possible to implement gateways

between H1 and L2 networks (see Fig. 15.4).

Before you can use a path, you must first edit it using a suitable tool (Bus

selection). This utility can be obtained both under SINEC NCM as well as

under the normal S5 interface (KOMI).

"Dest CP" ENDP

(e.g. CPU connected to

dest. CP with a

"swing cable")

e.g.CP L2

Fig. 15 .3 PG via Inte rnal L2 In terface (Pa th_2)

B8976060/02 Utilities

15 - 3 Volume 1

PG 511

CP-H1

CP-L2

CP-H1

CP-H1 CP-L2

PG 511

CP-L2

ENDP ENDP

CP-L1 ENDP

SINEC L2

SINEC L1

SINEC L2

SINEC H1

MUX*

MUX*MUX*

MUX*

MUX*In the diagram, this is an alternative to a direct connection,

however, the maximum number of MUX levels is two.

Fig. 15 .4 Overview of the Paths Possible on SINEC L2

Utilities B8976060/02

Vol ume 1 15 - 4

15.1.1 Bus Selection - Creating Paths in Path Files

To be able to obtain remote active stations on the SINEC L2 bus with the

PG, the "BUS SELECTION" utility is available under the SINEC NCM menu

item. This provides tools with which you can edit paths and store them in a

path file. Selecting a remote station via the L2 bus is only possible with

S5-DOS from S tage VI onwards.

In the BUS SELECTION utility, you edit a dedicated link from a PG to the

required station.

You can then activate this path to the required station under the menu item

Init in the Path selection screen.

You can edit the paths with the corresponding station addresses both in the

OFFLINE and ONLINE mode of the programmer. In the OFFLINE mode,

the PATH is stored in the PATH FILE on diskette or hard disk, i.e. you edit

the PATH on the screen and store it on diskette or hard disk. You can only

activate a PATH in the ONLINE mode by calling up a PATH from diskette

or hard disk or by activating the PATH you have just edited.

BUS SELECTION is described in the manual for your PG

= Init Edit ...

SINEC NCM

Init-> Path Definition

Path Definition

Utilities ->Bus Selection

Bus Selection

Utilities

Menu item

Init

Menu item

Fig. 15 .5 Menu Structure of the PG Functions on the Bus

B8976060/02 Utilities

15 - 5 Volume 1

With the TERMINATE command of this utility, or by calling a different

PATH, you can terminate a dedicated link again.

Example of a Path::

PG-->COR/MUX-->CP 5430 TF-->CP 5430 TF-->COR/MUX-->ENDP

15.1.2 Editing a Path

The method of editing a path is described in the manual for your PG under

the utility "BUS SELECTION". Here, the procedure for the paths

represented in Figs. 15.2 and 15.3 will be illustrated.

Path_1: (PG via AS511)

✔Set the AS 511 interface in the PG

✔Call the bus selection package

✔Specify the path name and path file (this combination later selects the

node in the application programs e.g. LAD/CSF/STL, NCM)

✔Edit and store the path

✔Check the path by attempting to activate it

Path_2: (PG via internal L2 interface)

✔Set the L2 interface in the PG

✔Call the bus selection package

✔Specify the path name and path file

✔Edit and store the path

✔Check the path

Utilities B8976060/02

Vol ume 1 15 - 6

– A ctivate the path only as far as the internal L2 interface module.

– Check and if necessary match the internal SYSID.

The set bus parameters of the internal L2 interface module must

not collide with the bus parameters of the external L2 CPs (e.g.

data rate).

– A ctivate the remaining nodes of the path.

B8976060/02 Utilities

15 - 7 Volume 1

15.1.3 Activating the Edited Path

Before activating a path starting from a CP L2, the local (SYSID)

parameters of the CP L2 must be matched to t he L2 bus parameters.

How is the PATH activated?

An edited path can be activated as follows:

➣In the NCM menu under menu item Init->Path selection (>screen: INIT

PATH DEFINITIONS).

➣In an S5 program package intended for path selection.

By activating a path, the link is established to a remote station.

Path Definitions SINEC NCM

DR Path file Path name

CP link: .INI:

OK SELECT

HELP

(EXIT)

Fig. 15 .6 Screen for Act ivt ing a Path

Utilities B8976060/02

Vol ume 1 15 - 8

The screen for Init->Path selection has the following structure

Input fi elds :

CP link

/Path file: Format: drive: file

Drive

Here, you must specify the drive you wish to work with.

If you press F8, possible drives are displayed for

selection.

Pat h fi le

Paths with different path names can be stored in this

PATH FILE. A path file can contain up to 100 different

paths. The path files are all of the type AP.INI (range of

values: max. 6 ASCII characters).

Path name: Each edited PATH in the path file is assigned a path

name which you supply here in order to select the

required PATH. (Range of values: max. 19 ASCII

characters, first character must be a letter.)

☞If a path name is entered in the corresponding field, online

operation is not possible via the AS 511 interface.

☞Once a path name has been entered, it is stored by SINEC

NCM even if the PG is switched off.

Functi on keys:

OK The "OK" key enters the data.

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select entries from the list with the cursor keys and

enter them in the field with the return key

B8976060/02 Utilities

15 - 9 Volume 1

15. 2 Cha nge Sub modul e S iz e

You can change the submodule size (16/32/64 bytes) using the menu item

with this name in the Utilities menu.

Input fi elds :

Database file: Format: drive: database

- Drive: Here, you specify the drive with which you want to

work. Press F8 to display a list of drives for selection.

- Database: All existing CP 5430/5431/5412 databases

New submodule

size: Possible entri es 16/32/64 Kbytes

Change Submodule Size SINEC NCM (EXIT)

Database file :

Current submodule size

HELP

SELECT

Currently requiered submudule size

New submodule size

31200

BACK

QDPDP1

64 KByte

KByte

Byte

Fig. 15 .7 Ch ange the S ubm odule Size

Utilities B8976060/02

Volume 1 15 - 10

Output fields:

Current sub-

module size: Memory capacity of the submodule in Kbytes (values:

16/32/64)

Currently r equired

submodule size Memory requirements of the currently selected

database file in bytes; (minimum submodule size)

Functi on keys:

BACK With the BACK function, you can reverse the change.

The old submodule size is selected again.

OK Starts the conversion to the new submodule size.

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select entries from the list with the cursor keys and

enter them in the field with the return key.

B8976060/02 Utilities

15 - 11 Volume 1

15.3 Convert CP 5430 Database old - new

(CP 5430 TF)

The CP 5430 TF has its own menu item under "Utilities" with which you

can convert old CP 5430 databases to new ones.

Input fi elds :

Source file: Format: drive: source file name

- Drive: Here, you specify the drive with which you want to

work. Press F8 to display a list of drives for selection.

- Source file name: Database file name of a database created with COM

5430 (A0).

Convert CP 5430 Database old - new SINEC NCM (EXIT)

Source file :

Network file

SELECT

Dest:

:NETZ1NCM.NET

Fig. 15 .8 Co nvert C P 5 430 D ata base old - new Scre en

Utilities B8976060/02

Volume 1 15 - 12

Network file: Format: drive: network file name

- Drive: Here, you specify the drive with which you want to

work. Press F8 to display a list of drives for selection.

- Network file

nam e: Destination network file where the new database will be

saved. The new database name is displayed in the

"Dest:" output field and matches that specified with "Init

-> Edit". The database fi le speci fied for conversion must

be new.

OK This function key starts the conversion.

SELECT If you press this key, a selection list is displayed with

possible entries for fields which cannot be edited freely.

Select entries from the list with the cursor keys and

enter them in the field with the return key.❑

B8976060/02 Utilities

15 - 13 Volume 1

NOTES

16 Workin g with the Application Examples

On the COM 5430 TF/COM 5431 FMS diskette, you will find all the COM

and STEP 5 user files required to work through the application examples.

The application examples were written for RAMs on both the CPs and the

CPUs.

The following general procedure is recommended for working with the

example programs:

➣Delete the CPUs and switch to the STOP mode.

➣In the SIMATIC S5 package, select the preset ON and select the

program file you want to work with.

➣Transfer all the blocks from FD to the CPUs.

➣Switch the CPs you are using to STOP with the mode selector switch.

➣Call the COM and select the required database file on diskette in the

menu item "INIT -> EDIT".

➣Transfer the database files to the CP with menu item "TRANSFER ->

CP Database Transfer -> FD -> CP" and the key F2 TOTAL.

➣Switch the CPs to RUN.

➣Once the configuration data have been transferred to the CPs, you

must switch the power off and on again so that the CPs accept the new

configur ation (SSNR, I/O area being used).

➣Switch the CPUs of the programmable controllers to RUN.

B8976060/02 Working with the Application Examples

16 - 1 Volume 1

The following list include all the COM and STEP 5 files required for the

application ex amples:

List of example programs for the CP 5430 T F:

S5-S5

AGAGT1ST.S5D

AGAGT2ST.S5D

OAGAG.115

OAGAG.155

AGAGONCM.NET

AGAGONCM.BPB

LAYER2

LAY2T1ST.S5D

LAY2T2ST.S5D

LAY2ONCM.NET

LAY2ONCM.BPB

OLAY2T1.155

OLAY2T2.115

OGPTLN1.155

OGPTLN2.115

OGPTLN3.135

GP115UST.S5D

GP155UST.S5D

GP135UST.S5D

GPO@@NCM.NET

GPO@@NCM.BPB

DIAGNOST.S5D

STATIOST.S5D

EINZELST.S5D

ODPTLN1.115

DP115UST.S5D

DPO@@NCM.NET

DPO@@NCM.BPB

Work ing w ith th e Ap plica tion E xam ples B8 9760 60 /02

Vol ume 1 16 - 2

OZPTLN1.115

ZP115UST.S5D

ZP95U@ST.S5D

ZP@@@NCM.NET

ZP@@@NCM.BPB

TF115UST.S5D

OTFTLN1

OTFTLN2

TF@@@NCM.NET

TF@@@NCM.BPB

List of example programs for the CP 5431 F MS:

S5-S5

AGAGT1ST.S5D

AGAGT2ST.S5D

QAGAG.115

QAGAG.155

AGAGQNCM.NET

AGAGQNCM.BPB

LAYER2

LAY2T1ST.S5D

LAY2T2ST.S5D

LAY2ONCM.NET

LAY2ONCM.BPB

QLAY2T1.155

QLAY2T2.115

B8976060/02 Working with the Application Examples

16 - 3 Volume 1

QGPTLN1.155

QGPTLN2.115

QGPTLN3.135

GP115UST.S5D

GP155UST.S5D

GP135UST.S5D

GPQ@@NCM.NET

GPQ@@NCM.BPB

DIAGNOST.S5D

STATIOST.S5D

EINZELST.S5D

QDPTLN1.115

DP115UST.S5D

DPQ@@NCM.NET

DPQ@@NCM.BPB

FMS

FERTIGST.S5D

LAGER@.ST.S5D

QFERTIG.TN1

QLAGER.TN2

QZIBEIS.TN1

FMS2@NCM.NET

FMS2@NCM.BPB

ZIBEISST.S5D

FMS1@NCM.NET

FMS1@NCM.BPB❑

Work ing w ith th e Ap plica tion E xam ples B8 9760 60 /02

Vol ume 1 16 - 4

17 Appendix

17.1 Job Numbers for the CP 5430 TF

ANR HDB

0 Send or Receive All

1 - 32 Send via Laye r 2

33 - 96 Se nd or R ece ive vi a L 2 Tran spo rt (TF )

97 - 100 Disabled

101-132 Receive via Layer 2 (S5S5 link)

133 Disabled

134- 186 Fr ee a cces s to L ayer 2

187-199 Disabled

200 FMA services

201 Read out the GP station list

202 Read out the ZP station list

203 Fileserver associations

205 Local jobs (PI, domain)

206-209 Disabled

210 Sync hronization G P/ZP/DP out put byte

211 Synchronization GP/ZP/DP input byte

212-217 Disabled

2 18 T rans fe r or re ceive th e time of day

219-223 Disabled

224- 255 D oes not ex ist

Table 17.1 Overview of the Job Numbers for the CP 5430 TF

B8976060/02 Appendix

17 - 1 Volume 1

SAP Use ANR

0 Disabled ------------

1 Disabled ------------

These SAPs are normall y u sed for

S5S5. T heir use for free lay er 2

access or FMS application

associations is possible as long as

the memory limits are kept to (total

num be r of lin ks) ; doub le us e of a

SAP must, h owever, be a voided.

1 - 32 Send S5S5 lin k

101-132 Receive S5S5 link

These SAPs are normall y u sed for

free layer 2 access. If they are not

used for this purpose, they can be

used for FMS application

associations. (Caution: make sure

the SAPs are only used by one

service!)

134-185 Free layer 2 access

134- 199 FMS appl icatio n a ssocia tio ns

54 DP master class 2 response

55 Clo ck fu nctio n 218 R ead /set clo ck

56 S5-95 standard link 206-209 free 212-217 free 219-223 free

200 F MA s ervic es

201 R ead out GP st ation lis t

57 Free

58 Pollin g SAP for cyclic FMS

application association

ANR not assigned to a service

59 Re served for PG links

60 Reserved for GP broadcast

61 De fault SAP for DP

62 Re served for GP

Re ques t fra me an d f or DP s lave

services

63 Disabled

Table 17.2 Assignme nt of the SAPs to the ANR fo r the CP 5431 FM S

Appendix B8976060/02

Vol ume 1 17 - 2

17.2 Job Numbers for the CP 5431 FMS

* These job numbers can also be used for FMS application associations. Make sure, however

that there are no double assignments. The ANR is assigned either to an S5S5 link or a free

layer 2 link or and FMS application association.

ANR HDB

0 Send or Receive All

1 - 32 Send via laye r 2 (S5S5 ) *

33 - 100 FMS application associations

101-132 Receive über Layer 2 (S5S5 link) *

133 FMS application associations

13 4-186 Fr ee a cces s to la ye r 2 *

187-199 FMS application associations

200 FMA services

201 Read out the GP station list

202 Read out the ZI station list/DP station list

203-208 Disabled

209 D P- s pecia l serv ices

210 S ync hroniz at ion GP /DP ou tp ut byt e

211 S ync hroniz at ion GP /DP in put byte

212-217 Disabled

218 Transfer/receive the time of day

219-223 Disabled

224- 255 D oes not ex ist

Table 17.3 Overview of the Job Numbers for the CP 5431 FMS

B8976060/02 Appendix

17 - 3 Volume 1

SAP Use ANR

0 Disabled ------------

1 Disabled ------------

These SAPs are normall y u sed for

S5S5. Use as "free channels" is

only po ssib le when le ss tha n the

maximum number of links have

been defined.

1 - 32 Send S5-S5 lin k

101-132 Receive S5-S5 link

Thes e SAPs are not u sed by the

sys tem p rog ram of the CP 54 30

TF and a re a vaila ble as "free

channels" .

- free layer 2, PG access

(cau tion, ma ke sure th ere is no t

d ouble assi gnme nt !)

33 - 96 A pplic ation asso ci ation s

97 - 100 f ree

134-186 Free Layer 2 access

54 DP master class 2 response

55 Clo ck fu nctio n 218 c lo ck fun ction

56 S5-95 standard link 187-199 free 206-209 free

212-217 free 219-223 free

200 F MA s ervic es

201 r ead out G P st ation list

202 r ead out Z P sta tio n list

57 Free

58 Free

59 Re served for PG- links -----------

60 Reserved for GP broadcast 210 synch. GP/ZP output bytes

61 Reserve d for ZP/DP 210 syn ch. GP/ZP/ DP output b ytes

211 synch. GP/ZP/DP input bytes

62 Re served for GP

re ques t fra me 211 synch. GP/ZP input bytes

63 Disabled 224-255 not defined

Table 17.4 Assignme nt of the SAPs to the ANR fo r the CP 5430 TF

Appendix B8976060/02

Vol ume 1 17 - 4

17.3 SAP - Job Number Assignment

Before you can work with free channels, the SAPs involved must be

configured with the free layer 2 links.

While the dual-port RAM sizes are limited to 128 bytes for the predefined

S5S5 links, data units of up to 256 bytes can be exchanged using "free

channels". This allows transmission of blocks of data with a maximum

length of 242/256 bytes. The first 8 bytes of these 256 bytes are used for

the header.

B8976060/02 Appendix

17 - 5 Volume 1

17.4 Overview of the Error Messages

The error messages are listed here to provide you with an overview.

17.4.1 Messages in the status word for predefined S5S5 links, free

layer 2 and FMA

Not

used Error

bits Data

mgment. Status

bits

15141312111098 7654 3210

Job complete with error

Job complete without error

Receive possible

bit

set Job active

Fig. 17 .1 Stru ct ure of the Stat us Wor d he re: Stat us Bit s

Appendix B8976060/02

Vol ume 1 17 - 6

Bits

8 -11 Meaning of the error bits

0HNo error.

If bit 3 "job complete with error" is nevertheless set, this means that

the CP has set up the job ag ai n followin g a cold rest ar t or RESET.

1HWrong type specified in block call (QTYP/ZTYP).

2HMemory area does not exist (e.g. not initial ized).

3HMemory area too small.

The memory area specified in the HDB call (parameters Q(Z)TYP,

Q(Z)ANF, Q(Z)LAE) is for t oo small for the data transmission.

4HTimeout (QVZ).

Acknowledgment from the memory cell is absent during dat a transfer.

Remedy: check and if necessary replace the memory submodule or

check and correct the source/destination parameters.

5HIncorrect parameters assigned to status word.

The parameter "ANZW" was specified incorrectly. Remedy: correct the

parameter or set up the data block corr ectly in which the ANZW is to

be l ocated.

6HInvalid source/destination parameter.

Parameter ID "NN" or "RW" was used or the data length is too small

(=0) or longer than 128 bytes. Remedy: use the correct Q(Z)TYP

parameter; "NN" and "RW" are not allowed for this type of data

transmission. Check the data l ength.

7HLocal resources bottleneck.

There are no data buffer s available for processing the j ob. Remedy:

retrigger the job, reduce the CP load.

8H* Remote r esources bottleneck.

No fre e rec eive b uffer on t he remote CP. Remedy: i n the re mote PLC,

accept "old" data with the receive HDB, in the transmitting PLC repeat

the transmi t job.

Table 17.5 Error Bits (Bits 8..11) in the Status Word (cont inued in Tab le 17.6)

B8976060/02 Appendix

17 - 7 Volume 1

Bits

8 -11 Meaning of the error bits

9H* Remote err or.

The remote CP has acknowledged the job negatively because e.g. the

SAP assignment is in correct. Remedy: rea ssign parameters for the li nk.

AH* Connection error.

The sending PLC or receiving PLC is not connected to the bus.

Remedy: switch systems on/off or check bus connections.

BHHands hake e rror.

The HDB processing was incorrect or the HDB monitori ng time was

exceeded. Remedy: st art the job agai n.

CHSystem error.

Error in the system program. Remedy: inform Siemens service.

DHDisabled data block.

The data transmission i s or was disabled during the HDB processing.

EHFree

FHLink or ANR not specified.

The job is not defined on the CP. Remedy: program the j ob (link) or

correct the SSNR/ANR in t he HDB call .

* only applies to S5-S5 links. With free layer 2 and FMA j obs, the errors are

identif ied in great er detail by the link_status in the confirmation header

Table 17.6 Error Bits (Bits 8..11) in the Status Word (cont inued fro m T able 17.5)

Appendix B8976060/02

Vol ume 1 17 - 8

The following table lists the Profibus error IDs (link_status) modeled on the

S5-S5 error messages.

PROFIBUS Meaning ANZW error ID

00 OK No error 0 No error

0 1 VE Neg ati ve ac know ledg men t 9 R em ote erro r

02 RR Remote resources not available 8 Resources remote

03 RS Remote SAP not d ef ine d 9 Rem ote error

10H LS Stat ion no t d efine d C S yste m err or

11H NA No reaction from station A Link error

12H DS Station not in ring A Li nk error

15H IV Invalid para meter C System e rror

Table 17.7 Profib us Error ID (link_status)

B8976060/02 Appendix

17 - 9 Volume 1

17.4.2 Global I/O s - Error Bits

Structure of the st atus wor d for HDB SEND (ANR 210) and RECEIVE (ANR

211)

Not

used Error

bits Data

mgment. Status

bits

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Job complete with error*

(e.g. invalid job number)

Job complete without error

SEND synchronization disabled

RECEIVE synchronization possible

Synchronization done without error

(Input GP was received)

* Bit 3 of the status bits is not connected with the error bits (8..11).

When bit 3 is set, the error is not specified by the error bits. All the errors

listed in table 7.3 are possible.

Fig. 17 .2 Structure of the status word, here: Status Bits

Appendix B8976060/02

Volume 1 17 - 10

Bit 11 10 98of the status word

Transmission delay in the other station, i.e. the

PLC cycle was faster than the transfer capacity

of the L2 bus (transmitted data of the remote

station could not be fetched quickly enough

by the L2 bus).

Reception delay in the local PLC, i.e. the transfer

capacity of the L2 bus was faster than the PLC

cycle (while the received data was being evaluated

in the local PLC, the L2 bus had supplied new data

data which could no longer be evaluated).

At least one remote station is in the STOP status

GP image is incomplete

(either not all stations have started up

at least one station has dropped out)

Reserved for ZP error message

Fig. 17 .3 Meaning of the Error bits in t he Status Word in RECEIVE

B8976060/02 Appendix

17 - 11 Volume 1

Evaluation of the GP station list (HDB RECEIVE with ANR 201)

Every CP that receives global I/Os manages a GP station list internally.

This list is 32 bytes long.

Each of the 32 bytes provides information about the status of an active L2

station (max. 32 stations) using global objects with which the stations

evaluating the station li st are "connected" .

Byte no. Status byte of the stations

0 Status byte station 1 (L2 station address 1)

1 Status byte station 2 (L2 station address 2)

...

31 Status byte station 32 (L2 station address 32)

Table 17.8 Structure of the GP Station List

Appendix B8976060/02

Volume 1 17 - 12

Explanation of the individual bits of the status byte:

Bit 01234567

0=no

1=yes

Status byte of the local station:

The complete expected GP is OK

Status byte of the remote station:

Input GP expected from this station

is ok

Station expects input GP from

other stations

Input GP expected from this station

All remote stations are in RUN status

The PLC of the remote station is in RUN status

send/receive delay* in at least

one remote station

send/receive delay* in at least

one GO of the remote station

*With send/receive delay, GOs have changed more often than they could be

sent or received (intermediate values can be lost)

Status byte of the local station:

Status byte of the remote station:

Status byte of the local station:

Status byte of the remote station:

Status byte of the local station:

Status byte of the remote station:

Fig. 17 .4 Structure of a Status Byte of the Station List

B8976060/02 Appendix

17 - 13 Volume 1

17.4.3 Cyclic I/Os Error Messages

Not

used Error

bits Data

mgment. Status

bits

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Job complete with error*

(e.g. invalid job number)

Job complete without error

SEND synchronization disabled

RECEIVE synchronization possible

Synchronization done without error

(Input GP was received)

* Bit 3 of the status bits is not connected with the error bits (8..11).

When bit 3 is set, the error is not specified by the error bits. All the errors

listed in table 7.3 are possible.

Fig. 17 .5 Structure of St atus Word HDB SEND (ANR210) and RECEIVE (ANR 211), St atus Bits

Appendix B8976060/02

Volume 1 17 - 14

Error bits for RECEIVE -HDB (ANR 211)

Error bits for the ZP station list (ANR 202)

Bit 11 10 9 8 of the status word

Reserved for GP error message

ZP image is incomplete

(either all stations have not yet

started up

at least one station has

dropped out)

Reserved for GP error message

Fig. 17 .6 Error Bits in RECEIVE-HDB (ANR 211)

Bit 11 10 9 8 of the status word

ZP image is incomplete

(either all stations have not yet

at least one station has

dropped out)

Only relevant with the IM 318B

(there is a request from the

IM 318B to fetch diagnostic

data)

started up

Fig. 17 .7 Error Bits of the ZP Station List

B8976060/02 Appendix

17 - 15 Volume 1

Structure of the ZP station list (ANR 202)

The station list has a length of 16 bytes, with each bit assigned to a station

address.

76543210

120 127

7654321076543210

012345678 9 10 11 12 13 14 15

2 - 14

16 - 119

Byte

Bit

Station

address

Fig. 17 .8 Structure of the ZP Station List

Appendix B8976060/02

Volume 1 17 - 16

17.4.4 DP Error Displays

Structure of the status word for HDB SEND (ANR 210) and RECEIVE

ANR 211).

Not

used Error

bits Data

mgment. Status

bits

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Job complete with error*

(e.g. invalid job number)

Job complete without error

SEND synchronization disabled

RECEIVE synchronization possible

Synchronization done without error

(Input DP was received)

* Bit 3 of the status bits is not connected with the error bits (8..11).

When bit 3 is set, the error is not specified by the error bits. All the errors

listed in table 7.3 are possible.

Fig. 17 .9 Structure of the Stat us Word, h ere: Status Bits

B8976060/02 Appendix

17 - 17 Volume 1

DP group messages of the DP station list

The DP ANZW bits 8-11 of job 202 provide the following DP group

message:

Bit 11 10 9 8 of ANZW/A-NR: 202

0 = no error, all the configured DP slaves are in

the data transfer phase

1= at least one DP slave is not in the data

transfer phase

Cause of error, what to do:

To find out which slave(s) is affected, you must

read out the DP station list using

HDB-RECEIVE A-NR: 202.

Cause of error, what to do:

use the special service "DP station diagnostic list"

HTB-A-NR: 209, to read out the diagnostic list

Using the special service "Read single DP slave diagnostic

data", HTB-A-NR: 209, it is possible to obtain an accurate

error analysis for every slave.

Possible causes of a group message are;

- DP slave, does not reply on the bus (not connected,

switched off)

0 = cyclic global control job not sent

1= cyclic global control job sent

0 = there are no new diagnostic data for DP slave

1= there are diagnostic data for a DP slave

0 = no timeout occurred during processing of the DP polling list

1= a timeout occurred during processing of the DP polling list

The selected monitoring time for processing the polling

list was exceeded.

Possible causes of this error message:

- problems on the bus

- delayed DP polling list processing due to parallel

processing of other acyclic services on the CP.

To find out which slave(s) is affected, you must

Fig. 17 .10 The ANZW Bits 8-11 of Job 202

Appendix B8976060/02

Volume 1 17 - 18

Structure of the DP station list (ANR 202)

The DP station list has a length of 16 bytes (128 bits). Each bit of the DP

station list corresponds to one of the possible station addresses on the bus

of the DP slave stations.

Structure of the DP diagnostic list (ANR 209)

The DP diagnostic list has a length of 16 bytes (128 bits). Each bit of the

DP diagnostic list corresponds to one of the possible station addresses on

the bus of the DP slave stations.

76543210

120 127 *)

7654321076543210

012345678 9 10 11 12 13 14 15

2 - 14

16 - 119

Byte

Bit

Station

address

*) The first and last two bits in the station list are not relevant, since the permitted

station address on the L2 bus must be in the range 1-125

124

Fig. 17 .11 Str uct ure of the DP Stat ion Li st

76543210

120 127 *)

7654321076543210

012345678 9 10 11 12 13 14 15

2 - 14

16 - 119

Byte

Bit

Station

address 124

*) The first and last two bits in the station list are not relevant, since the permitted

station address on the L2 bus must be in the range 1-125

Fig. 17 .12 Str uct ure of t he D P Diag nost ics List

B8976060/02 Appendix

17 - 19 Volume 1

Meaning of the acknowledgmen t messages for speci al job ANR 209

Acknowledgment:

00 Hex No error

01 Hex Syntax error in job field.

02 Hex Error in HDB handling.

03 Hex CP not in logical t oken ring.

04 Hex Slave stati on not configured.

05 Hex Slave not responding (failed).

06 Hex Slave station not in data transfer phase

07 Hex CP not in cycle-synchronized mode

08 Hex Global_Control: mode not allowed

09 Hex Gl obal_Control: no act ive slav e s elected

0A Hex CP check of slave configuration detected error

0B Hex DP STOP status

0C Hex Global_Control: acyclic Global_Control

Appendix B8976060/02

Volume 1 17 - 20

17.5 Overview of the FMA Services

Relevant bytes in the request field

You want to.... . . then

use the

service

FDL

request

(byte 0)

Service

code (byte

SAP no.

(byte 5)

rem

add

station

(byte 6)

Read current bus

parameters FDL_READ

_VALUE 00HOBH

(= 11) _____ ______

Read status values

of an SAP LSAP_STA-

TUS 00H19H

(= 25) 2...63 0...126

Obtain an overview

of all stations con-

nected to the bus

(query the local sta-

tions)

FDL_LIFE

_LIST_

CREATE_

LOCAL

00H1BH

(= 27) _____ ______

Re ad id entifi cation

of a station FDL_IDENT 00H1CH

(= 28) ______ 0...126

Re ad st ati on-

oriented statistics FDL_

READ_

STATIST

IC_CTR

00H1DH

(= 29) ______ ______

Re ad st ati on-

oriented statistics FDL_

READ_LAS_

STATIST

IC_CTR

00H1EH

(= 30) ______ ______

Table 17.9 Overvi ew o f the FMA Se rvices

B8976060/02 Appendix

17 - 21 Volume 1

Byte Field to be sent (request) Byte Field recei ved

(Confirmation/Indication)

0 com_class

FDL request=00

(service request to layer 2)

0com_class

FDL confirmation = 01H

(ac knowl ed gmen t fro m layer 2

firmwa re afte r FDL request) o r

FDL Indicati on = 02H (da ta

received)

1user_id

Freely assigned ID that is

re turn ed un chan ge d in th e

confirmation

1user_id

Id entifi er a ssign ed in an F DL

request (on ly rele vant for

conf irm ation ; wit h in dicat ion t he

va lue is "0")

2 service_code

Ty pe of reque ste d serv ice:

SDA = 00 H

SDN = 01H

SRD = 02 H

RPL_UPD_S = 06

RPL_UPD_M = 07

2 service_code

Ty pe of s ervic e pr ovide d by t he

layer 2 firmware

SDA = 00 H / SDN = 01H

SRD = 32 H

Only with FDL confi rmatio n:

RPL_UPD_S = 06 H

RPL_UPD_M = 07 H

Only with FDL indic ation :

SDN_MULTICAST = 7FH

3 link_status

only relevant for confirmation

relevant

3 link_status

(see table 17.11)

4 ser vice _cla ss ( prior ity)

Low = 0H, Hig h = 1H4 se rvice _c lass (p rio rity)

Low = 0H, H igh = 1 H

5 DSAP/RSAP

Nu mber of th e des tin ation SAP

(defaul t SAP = FFH)

5 DSAP/RSAP

Number o f the remote SAP

(=Source-SAP) (defaul t SAP =

FFH)

6 rem_add_station

st ation addre ss of the recei vin g

station

6 rem_add_station

st ation addr ess of the rec eivin g

station

7 rem_add_segment

lo gica l segm ent a dd ress; alwa ys

ente r FFH

7 rem_add_segment

lo gical segm ent a dd ress; a lwa ys

ente r FFH

Ta ble 1 7.10 Structure of the Confirmation/Indication/Request Header

Appendix B8976060/02

Volume 1 17 - 22

Value of

link_status Abbreviation

PROFIBUS Meaning

SDA

00H

01H

02H

03H

11H

12H

Po sitive -ac know led gmen t, s ervic e exe cut ed.

Negative-acknowledgment, remote user/FDL interface error.

Ne gat ive-a ck nowl edgm ent, res ou rces o f rem ot e FD L

controller not available.

Service or rem_add o n remote SAP no t activated.

No rea ction (Ack./Re s.) from rem ote sta tion.

Local FDL/PHY not in logical ring or disconnected from the

bus.

SDN

00H

12H

Positive acknowledgment, transmission of data from local

FDL/PHY controller completed.

L ocal F DL/PH Y not in l ogica l to ken ri ng or disc on nect ed

from the bus.

SRD

08H

0AH

01H

02H

03H

09H

0CH

0DH

11H

12H

RDL

RDH

Po sitive ac knowl ed gmen t, re ply d ata low exist .

Po sitive ac knowl ed gmen t, re ply d ata high exist .

Negative acknowledgment, remote user/FDL interface error.

Negative acknowledgment, resources of the remote FDL

controller not available.

Service or rem_add o n remote SAP no t activated.

Negative acknowledgment, resources of the remote FDL

controller not available.

Reply data (low) exist but negative acknowledgment of

transmitted data 09H (NR).

Reply data (high) exist but negative acknowledgment of

trans mitted d ata, 09H (NR).

No rea ction (Ack./Re s.) from rem ote sta tion.

Loc al F DL/PH Y not in t he log ical ri ng or disc onne ct ed from

the b us.

REPLY_UPDATE_SINGLE/REPLY_UPDATE_MULTIPLE

00H

12HOK

LR Positive acknowledgment, data area loaded.

Re spon se resou rce being used by M AC.

SDA/SDN/SRD/REPLY_UPDATE_SINGLE/REPLY_UPDATE_MULTIPLE

10H

15HLS

IV Service not activated o n local SAP.

In valid param e ter in r equ est he ader .

Table 17.11 Meaning of the Values in byte 3 (link_status) in the Confirmation Header

B8976060/02 Appendix

17 - 23 Volume 1

17.6 Calculation of the Target Rotation Time (TTR)

The TTR is dependent to a great extent on the data rate and the number of

active stations (NAS).

17.6.1 Overview

Parameter Explanation

Retry-Counter Number of attempts to re-transmit when

transmission unsuccessful.

Slot-Time* Wait to recieve time (or wait for reaction time).

This is the time the sender(initiator) of a request

has to wait until the addressed station reacts.

It does not matter whether the frame is a message

or the token frame.

Range: 1....65535 bit times

Setup-Time "Dead time": this is the maximum time between an

event (e.g. reception of characters or end of an

internal monitoring time) and the reaction to the

event.

Range: 1....255 bit times

Minimum Station

Delay*

Maximum Station

Delay*

Minimum time between receiving the last bit of

a frame and sending the first bit of the next

frame.

Range: 1....255 bit times

Maximum time between receiving the last bit of

a frame and sending the first bit of the next

frame.

Range: 1....255 bit times

Target Rotation

Time * Preset token rotation time. This time is compared

with the actual token rotation time that has elapsed

when the token is received. The result of the

comparison decides whether and which frames

can be sent by the station.

Range: 1....16777215 bit time units*.

You must select this time to match the

requirements of the bus system.

* Times are entered as bit times. This is the time required

to send one bit (reciprocal of the data rate in bps)

Table 17.12 Overvi ew: INIT Pa ram eters

Appendix B8976060/02

Volume 1 17 - 24

Parameter Explanation

The address area between the local station

address of an active station and the address

of the next active station is known as the GAP.

The GAP addresses are checked cyclically

to obtain the status of stations in the GAP

address area ("not ready", "ready" or "passive").

If the status is "ready", the station is a new

active station and the token is passed to it.

The GAP update factor "G" is a factor for

calculating the time = (G*TTR) after which the

You must select this factor to match the

requirements of your bus system.

GAP Update

Factor

HSA

(highest L2 station

address) Range: 2....126.

Default SAP

Bus characteristics

If an L2 frame is received without a destination

SAP number, the layer 2 firmware automatically

selects the default SAP.

If you want to use FDL services, you must

select the number of the default SAP in the

range 2 to 54, since the FDL service only

only accesses these DAPs.

RS 485

station with the lower address checks whether

a further station is requesting to enter the

ring.

Range 1 to 100

* Times are entered as bit times. This is the time required

to send one bit (reciprocal of the data rate in bps)

Table 17.13 Overvi ew: INIT Pa ram eters (conti nu ed)

B8976060/02 Appendix

17 - 25 Volume 1

Orientation values for the INIT parameters

Recommended default parameters:

The next sections explain how to do the following,

➣calculate the target rotati on time

➣select the GAP update factor

➣the effects of the HSA set ting "HSA" (highest station address).

Assuming that you have used the recommended default INIT parameters,

the target rotation time can be calculated relatively accurately for

➣S5-S5 links

➣Data transmission with direct access to layer 2 services.

Data rate

(in Kbps)) 9.6 19.2 93.75 187.5 500 1500

Slot Time

Setup Time

Minimum

Station Delay

Maximum

Station Delay

100

170

240

200

400

360

1000

360

3000

150

980

Appendix B8976060/02

Volume 1 17 - 26

Proceed as follows to calculate the required target rotation time:

➣Work out the maximum possible number of frames from all stations that

can occur in one token rotation distinguishing between the different

types of frame (e.g. SDN, SDA frames). Frames on predeifined S5-S5

link s count as SDA frames.

➣Calculate the "worst case" target rotation time using Table 17.13. You

must then add 11 bit time units for every data byte to the basic

overhead from the table (BTU).

➣Then multiply the "worst case" target rotation time by the correction

factor 0.6.

Type of

frame 9.6 19.2 93.75 187.5 500 1500

Token (LAS<3) 88

165

195

160

195

410

270

320

690

450

750

215

1650

850

2700

450

4950

1950

Token (LAS>3)

GAP

SDN

SDA

SRD

215

345

225

295

430

465

610

1100

1300

3150

Data rate in Kbps

Table 17.14 Basic O verhead s of th e Frames Relative t o the Da ta Rate (in BTU)

B8976060/02 Appendix

17 - 27 Volume 1

Selecting the GAP update factor:

The GAP update fact or decides how many token rotations take place before

all the active stations check their GAP area.

If you requir e a low bus load, s elect a high GAP update factor. Stations that

have dropped out of the ring and wish to re-enter it are registered later in

this case.

If, on the other hand, you want such stations to be included in the ring as

soon as possible, then select the GAP update factor as small as possible.

This increases the bus load (more frames due to addi tional GAP frames).

The more stations connected to the bus, the lower the relative load caused

by GAP frames. If the station addresses and HSA are selected optimally, a

GAP update factor on 1 can be select ed.

Example of cal culating the target rotation time (TTR) with the following

bus conf igurat ion:

Three stations are c onnected t o the SINEC L2 bus:

Addresses: 1, 2 and 3

HSA: 3

GAP update factor: 1

Data rate (in Kbps): 187.5

Volume of frames:

station 1: 1 SDN frame with 10 bytes of transmitted data

station 2: 1 SDN frame with 10 bytes of transmitted data

station 3: 1 SDN frame with 10 bytes of transmitted data

1 SRD frame with 20 bytes of transmitted data and 10

bytes of received data.

Appendix B8976060/02

Volume 1 17 - 28

Calculation of the volume of frames and time required:

Type of frame Number Overheads from column 187,5

Kbp s Ta bl e 17 .1 3 Result

(in B TU)

Token 3 (stati ons) x 320 960

GAP 1 (GAP upd.) x 690 690

SDN 3 (SDN with 1 0

bytes transmitte d

data)

x (450 + 10 (bytes) x 11 BTU) 1680

SRD 1 (SRD with 3 0

bytes transmitte d

and received data)

x (610 + 30 (bytes) x 11 BTU) 940

The total is the "worst-case" target rotation time 4270

From this you can select the target rotation time:

4270 ("worst-case" target rotation time) x 0.6 (correction factor) = 2562 BTU

(target rotation time)

Optimizing the target rotation time:

➣Assign the station addresses in ascending order

(1, 2, ..)

➣The selected HSA should be the same as the highest station address

on the L2 bus.

B8976060/02 Appendix

17 - 29 Volume 1

17.7 Calculating the Switch-off and Reaction Times of

the Glob al I/Os

Calculation of the switch-off times Tso for the free and

cycle-synchronized modes

The CP 5430 TF/CP 5431 FMS "registers" the failure of a station only after

the switch-off time Tso has expired. After this time, the CP resets the GP

inputs, i.e. the input bytes assigned to this station are set to the value "0".

The time Tso depends on the following

- the select ed target rotation time and

- the s elected dat a rate.

The diagram shows the switch-off time Tso (in seconds) as a function of the

target rotation time (TTR; in bit time units).

Tso/s

Tsomin

TTR limit TTR/bit time units

Explanation of areas and :

1 If TTR is less than TTR limit , the CP switches off

the failed station at the latest after time T somin has elapsed

2If TTR is greater than TTR ,there is a linear relationship

according to the equaiton (TTR in bit time units, data rate in

bps, T in seconds):

T =----------------*TTR

data rate

limit

Fig. 17 .13 Switch-off Time Tso (in second s) as Functio n of th e Target R otatio n Time

Appendix B8976060/02

Volume 1 17 - 30

The shape of the curve is similar for all data rates; it always consists of

areas 1 and 2.

The curves for different data rates differ in

- The position of the "dog-leg" separating areas 1 and 2.

and

- The angle of the curve in area 2.

The switch-off times (in seconds) for the different data rates can be

calculated based on the f ollowing t able (BTU=bit t ime uni ts):

Data rate Switch-off time in area 1 Switch-off time in area 2

9.6 Kbps TTRlimit = 317 BTU

TTR< 317 BTU:

>T so = T somin = 0.8 s TTR > 317 BTU:

>T so = 0.0025xTTR(s)

19.2 Kbps TTRlimit = 590 BTU

TTR< 590 BTU:

>T so =T somin = 0.8 s TTR> 590 BTU:

>T so= 0.00125xTTR(s)

93.75 Kbps TTR< 2883 BTU: TTR> 2883 BTU:

>T =T somin= 0.8 s

so >T so= 0.000256xTTR(s)

187.5Kbps

TTRlimit = 4125 BTU

500 Kbps

1.5 Kbps

TTR< 5766 BTU:

>T so=T somin = 0.8 s TTR> 5766 BTU:

>T so= 0.000128xTTR(s)

TTRlimit = 8250 BTU

TTR< 15375 BTU:

>T so=T somin = 0.8 s TTR> 15375 BTU:

>T so= 0,.0005xTTR(s)

TTRlimit = 15375 BTU

TTR< 46125 BTU:

>T so=T somin = 0.8 s TTR> 46125 BTU:

>T so= 0,.0002xTTR(s)

TTRlimit = 46125 BTU

Table 17.15 Swit ch-off tim es (in se co nds) for th e Differe nt Data R ates

B8976060/02 Appendix

17 - 31 Volume 1

Calculation of the react ion time T R of the global I/Os

In the CYCLE-SYNCHRONIZED mode, the time interval between HDB

SEND (RECEIVE) calls in the control program determines the reaction

times of the global I/Os.

In the FREE mode, you can calculate the minimum time interval between

two consecutive "changed value frames" (the CP sends only data whose

values have changed!).

This minimum interval, called the "reaction time" (TR) is a function of the

data rate and the selected target rotation time (TTR).

TTRlimit TTR/bit time units

Explanation of areas and :

1 If TTR is less than TTR limit , the CP sends changed

GP output bytes at the latest after a reaction time T RMin .

2If TTR is greater than TTR , there is a linear relationship

according to the following equation (TTR in bit time units,

limit

T =---------------- *TTR

data rate

data rate in bps, T in seconds):

Min

Fig. 17 .14 Re action Ti mes T R

Appendix B8976060/02

Volume 1 17 - 32

The shape of the curve is similar for all data rates; it always consists of

areas 1 and 2.

The curves for different data rates differ in

- The position of the "dog-leg" separating areas 1 and 2.

and

- The angle of the curve in area 2.

The reaction times (in milliseconds) for the different data rates can be

calculated based on the f ollowing t able.

Data rate Switch-off time in area 1 Switch-off time in area 2

9.6 Kbps TTRlimit = 3177 BTU

TTR< 317 BTU:

>T R= T RMin = 132 ms TTR > 317 BTU:

>T R= 0.417xTTR(ms)

19.2 Kbps TTRlimit = 590 BTU

TTR< 590 BTU: TTR> 590 BTU:

>T R= 0.208xTTR(ms)

93.75 Kbps TTR< 2883 BTU: TTR> 2883 BTU:

>T R= 0,043xTTR(ms)

187.5 Kbps

TTRlimit = 2883 BTU

>T R= T RMin = 132 ms

500 Kbps

1.5 Mbps

TTR< 5766 BTU: TTR> 5766 BTU:

>T R= 0.021xTTR(ms)

TTRlimit = 5766 BTU

>T R= T RMin = 132 ms

TTR< 15375 BTU: TTR> 15375 BTU:

>T R= 0.008xTTR(ms)

TTRlimit = 15375 BZE

>T R= T RMin = 132 ms

TTR< 46125 BTU: TTR> 46125 BTU:

>T R= 0.003xTTR(ms)

TTRlimit = 46125 BTU

>T R= T RMin = 132 ms

Table 17.16 Re action Ti mes (in mill isecond s) for the D ifferen t Data R ates

B8976060/02 Appendix

17 - 33 Volume 1

Example:

You have set a TTR of 4000 BTU at a data rate of 187.5 Kbps. Based on

the table this means:

Swi tch-off time Tso = Tsomin = 1.06 s

Reaction time TR = TRMin = 132 ms

Now increase the TTR to 10,000 BTU at the same data rate.

Result:

Swi tch-off time Tso = 0. 000128xTTR(s) = 1. 28 s

Reaction time TR = 0.016xTTR(ms) = 160 ms. ❑

Appendix B8976060/02

Volume 1 17 - 34

A Abbreviations

Abbreviations

ALI Application Layer Interf ace

ANR Job number (for handling blocks)

ANZW Status word

AP Automation protocol layers 5 to 7 of the ISO/OSI

reference model

AS Ac tive s tar c oupler

AS 511 511 interface, protocol for the communication between

PLC and PG

ASCII American Standard Code of Information Interchange

BBlock

BCD Binary coded decimal

BE Bl ock end

CC Central controller

CI Cyclic interface

CIM Computer Integrated Manufacturing

COM Abbreviation for programming software for SIMATIC S5

CPs

B8976060/02 Abbreviations

A - 1 Volume 1

COR Coordination module

CP Communications Processor

CPU Central Processing Unit

CSF Control System Flowchart, graphical representation of

automation tasks with symbols

CSMA/CD Carrier sense multiple access with collision detect

DA Destination Address

DB Data block

DCE Data Communication Equipment

DIN Deutsches Institut für Normung (German Standards

Institute)

DIR Directory of data medium and files

DMA Direct Memory Access

DOS Operating system

DP Distribut ed I/O s

DPR Dual Port RAM

DTE Data Termi nal Equi pment

DW Data word (16 bit s)

DX Extended dat a bloc k

Abbreviations B8976060/02

Volume 1 A - 2

EG/EU Expansion unit

EIA Electronic I ndustries Associati on

EPROM Erasable Programmable Read Only Memory

ET 200 El ectronic T erminal 200

F Flag bit

FB Function block

FD Floppy Disk (data medium)

FD Flag double word

FDDI Fiber Distribut ed Data Interface

FDL

FDL2 Fieldbus Data Link (subfunction of layer 2)

Free layer 2 communi cations

FlexOs Multitasking operati ng system

FMA Fieldbus Management Layer

FMS Fieldbus Message Specification (complying with

PROFIBUS)

FO Fibr e Optic

FW Flag word

FY Flag byte

B8976060/02 Abbreviations

A - 3 Volume 1

GO Global Object

GP Global I/Os

GPW Global Peripheral Word

GPY Global Peripheral Byte

GRAPH 5 Software package for planning and programming

sequence controllers

HDB Handling blocks

HSA Highest Station Address

IB Input by te

IEC International Electronics Commission

IEEE Institution of Electrical and Electronic Engineers

IP Intelligent peripheral module

ISO International Standardization Organization

IW Input word

KOMI Command interpr eter

LAD Ladder Diagram, graphical representation of the

automation task with symbols of a circuit diagram

Abbreviations B8976060/02

Volume 1 A - 4

LAN Local A rea Network

LB Link bl ock

LED Light Emitting Diode

LEN Length of a block

LLC Logical Link Control

LLI Lower Layer Interface

LSB Least Signifi cant Bit

MAC Medium Access Control

MAP Manufacturing Automation Protocol

MMS Manufacturing Message Specific ation

NCM Network and Communication Management

OB Organization block

OSI Open System Interconnection

OW Word from the extended I/Os

OY Byte from the extended I/Os

PAFE Parameter assignment error

PB Program block

B8976060/02 Abbreviations

A - 5 Volume 1

PC Personal Computer

PCI Protocol Control Information (for coordinating a

protocol)

PCP/M-86 Operating system Personal CP/M-86

PDU Protocol Data Unit (frames consisting of PCI and SDU)

PG Programmer

PI Program invocati on

PI Process image

PII Process image of the inputs

PIQ Process image of the outputs

PLC Programmable controller

PNO PROFIBUS user organization

PRIO Priority

PROFIBUS PROcess Field BUS

PW Peripheral word

PY Peripheral byte

QB Output byte

QW Output word

RAM Random Access Memory

Abbreviations B8976060/02

Volume 1 A - 6

RLO Result of logi c operation (code bits)

RS Recommended Standard

RS 485 EIA standard (multipoint capability) standard for

electrical data transmission

S5-S5 Special ty pe of communication PLC wi th PLC

SA Source Address

SAP Service Access Point. Logical interface points on the

interface between the layers via which the PDUs are

exchanged between service users.

SB Sequence block

SDA Send Data with Acknowledge

SDN Send Data wi th No Acknowledge

SDU Service Data Unit. Information about the service used

and the user data contained within it.

SINEC Siemens network architecture for coordination and

engineering

SINEC AP SINEC aut omation pr otocol

SINEC H1 SINEC bus system for industrial applications based on

CSMA/CD

SINEC H1FO SINEC bus system for industrial applications based on

CSMA/CD with fiber optics

SINEC H3 SINEC bus system for industrial applications based on

FDDI

B8976060/02 Abbreviations

A - 7 Volume 1

SINEC L2 SINEC bus system for industrial applications based on

PROFIBUS

SINEC L2-FO SINEC bus system for industrial applications based on

PROFIBUS with fiber optics

SINEC L2-FMS SINEC bus system for industrial applications based on

PROFIBUS with the FMS protocol

SINEC L2-DP SINEC bus system for industrial applications based on

PROFIBUS with the DP protocol

SINEC L2TF SINEC bus system for industrial applications based on

PROFIBUS with the TF protocol

SINEC TF SINEC t echnological funct ions

SRD Send and Request Data

SSNR Interface number

STEP 5 Programming language for programming programmable

controllers of the SIMATIC S5 range

STL Statement List, STEP 5 method of representation as a

series of mnemonics of PLC commands (complying

with DIN 19239)

Sub-D Subminiature D (c onnector)

SYM Symbolic addressing

SYSID Block for syst em identifi cation

S5-KOMI S5 command interpreter

S5-DOS/ MT S5 operating system based on FlexOS

Abbreviations B8976060/02

Volume 1 A - 8

TF Technological functions

TSAP Transport Service Access Point

TSAP-ID Transport Service Access Point I dentifier

TS ET Set - up t im e

TSDR Station del ay

TSL Slot-time

TTR Target rotation time

TPDU Transport Protocol Data Unit (size of the block of data

transferred by the transport system)

TSDU Transport Service Data Unit (size of the block of data

transferred to the transport system with a job for

transportation via a transport relation)

TSEL Transport selector, term used as an alternative for

TSAP-ID

VB Code for application association-specific and

abbreviation (code) for data link block.

VFD Virtual Field Device

VMD Virtual Manufac turing Device

ZP Cyc lic I /Os

B8976060/02 Abbreviations

A - 9 Volume 1

Notes

Index

Ack. field for DP station single diagnosis 11-54

Active and passive stations on the bus 11-2

Active star coupler (AS 501) 2-20

Active st ations 2-10

Acyclic communication 5-11

ANZW 7-6

Assignment of parameters to the DP slave 11-7

Backplane connector 4-18

Base interface number 4-9

Basic configuration 6-17

Bit time 6-27, 6-30

Bus cable 2-18

Bus characteristics 6-26

Bus selection 15-5

Bus terminal 2-15

Channel-related diagnosti cs 11-61

Clear DP 11-34

Communications model 3-6

Configuration of a DP slave 11-7

Connecting c ables (t o stations) 2-23

Connecting PGs via bus 4-26

Consistency of the I/Os with DP service 11-11

Control command 11-7

Control commands 11-66

CP 5430 TF/CP 5431 FMS t echnical description 4-1

CP database transfer 6-51

CP INIT 6-20

CP starting/stopping/st atus 6-47

CP status 6-48

B8976060/02 Index

B - 1 Volume 1

Cycle-synchronized 10-6

Cyclic and acyclic transmission 11-69

Cyclic communication 5-11

Data rate 6-26

Delete CP 6-49

Medium connector 4-2

Device-related di agnosis 11-59

DIN E19245 Part 3 PROFIBUS-DP 11-4

DP diagnostic list 11-41

DP editor 11-22

DP group message 11-46

DP MASTER, class 1 11-4

DP MASTER, class 2 11-4

DP polling list cycl e 11-19

DP polling list, processing time 11- 32

DP slave 11-22

DP slave diagnostic informati on 11-7

DP slave single diagnosis 11-42

DP slave, parameter assignment 11-26

DP station list 11-40

DPR page 4-9

DSAP 7-13

Dual-port RAM 4-8

Fault LED 4-6

Fieldbus-Data-Link services (FDL) 8-2

Freeze 11-68

GAP address area 2-11

GAP update factor 2-11

GAP update factor (G) 6-27

Glass fiber optic cable 2- 16, 2-20

Global I/Os 9-1

Global network parameters 6-24, 6-25

Index B8976060/02

Volume 1 B - 2

Global_Control 11-66

GP station list 9-18, 9-20

Group identif ier 11-27

Handling block (HDB) 4-8

HDB Receive 202 ANZW 11-46

HDB RECEIVE 211 11-20

HDB SEND 210 11-19

Highest station address 6-26, 6-29

I/O area 11-22

I/O areas 9-24, 9-28

ID-related diagnostic s 11-59

Ident_Number 11-58

Installati on and s tart 6-10

Installati on guidelines 4- 21

Interface as signments 4-18

Interface num ber 4-9

Interrupt 7-13

Job number 4-8

L2 interface socket 4-18

Layer 2 service 8-1

link_status 8-6

Local network parameters 6-24, 6-28

Master diagnostic data information 11-7

Maximum retry limi t 6-26

Maximum station delay (max. TSDR) 6-27

Medium 2-14

B8976060/02 Index

B - 3 Volume 1

Memory submodules 4-20

Menu structure SINEC NCM 6-4

Minimum pol ling c ycle 11-33

Minimum station delay (min. TSDR) 6-27

Mode changes 4-3

Mode LEDs 4-3

Mode: CYCLE- SYNCHRONIZED 11-11

Mode: FREE 11-11

Multi-master 11-6

Multicast messages 8-28

Multiprocessor PLC 4-9

NCM 1-2, 6-1, 6-10

Network file 6-22, 6-36

Network matching 6-36

Network parameters 6-24

Network topology 2-18

Number of stations 2-15, 2-23

Optical repeater adapter SF 2-21

OSI reference model 3-2

Parameter assignment error byte (PAFE) 7-9

Passive stations 2-10

Path, editing 15-6

Peripherals editor 9-32

PG 4-26

PG functions 15-2

PG interface 4-12

PG interface socket 4-18

PIQ output 11-12

Plastic fiber opti c cable 2-16, 2-20

Polling cycle time 11-33

Productive data exchange 11-7

Programmable controller 4-7

Index B8976060/02

Volume 1 B - 4

Response monitoring 11-29

RPL_UPD_M 8-3

RPL_UPD_S 8-3

S5-S5 links 7-1

characteristics 7-2

Screen layout 6-6

SDA 5-3, 8-3

SDN 8-3

Service access point (SAP) 3-8

Setup time (TSET) 6-27

SINEC 2-3

SINEC L2 2-5

SINEC L2 repeater 2-18

SINEC L2-DP 11-1

SINEC L2-TF 2-7

SINEC L2FO 2-5

SINEC tec hnological functions ( TF) 5-9

Slot time (TSL) 6-26

Slots 4-21

SRD 8-3

SSAP 7-13

Start CP 6-47

START/STOP response 4-5

Status word 7-3, 7-6

Stop CP 6-48

STOP DP polling l ist processing 11-74

Sync 11-67

Sync mode/Freeze mode 11-28

SYSID block 6-20

Target rotation time (TTR) 6-27

Technical data CP 5430 TF/CP 5431 FMS 4-12

Token 2-10

Token ring 2-10

B8976060/02 Index

B - 5 Volume 1

Token rotation 2-10

Token rotation time 2-12

Transfer func tions 6-46

Transmission according to RS 485 2-14

Transmission medium 2-16

Transmission with fiber optic cables 2- 15

Unfreeze 11-68

Unsync 11-67

Update PII 11-13

Vendor identification 11-27

Watchdog 4-11

ZP editor 10-24

ZP station li st 10-18

Index B8976060/02

Volume 1 B - 6

CFurther Reading

/1/ N.N.:

PROFIBUS Standard DIN 19245, Part 1

Beuth-Verlag Berli n 1988

/2/ Siemens:

SINEC TF, Manual for

Order No. 6GK1971-1AB00-0AA0 German

Order No. 6GK1971-1AB00-0AA1 English

SIEMENS AG 12/90

/4/ N.N.:

EIA RS 485 Standard

/5/ G. Mahlke, P . G össig.:

Lichtwellenlei terkabel: Grundlagen, Kabeltechnik

SIEMENS AG, Berlin und München

ISBN 3-8009-1501-4, 2Auflage 1988

/6/ N.N.:

VDI VDE 3692 Sheet 2

/7/ N.N.:

Arbeitsric htl inie AR 463-2-220

Montage des Bussystems SINEC L2

/8/ N.N.:

Arbeitsric htl inie AR 320-3-220

Verlegen von LWL-Kabeln in industriel len Anl agen

/9/ Siemens:

SINEC L2/L2FO Network Manual

Order no. 6GK1970-5CA00-0AA0 German

Order no. 6GK1970-5CA00-0AA1 English

SIEMENS AG

/10/ N.N.:

PROFIBUS Standard DIN 19245, Part 2

Beuth-Verlag Berli n 1994

B8976060/02 Further Reading

C - 1 Volume 1

/11/ N.N.:

PROFIBUS Standard DIN E19245, Part 3

Beuth-Verlag Berli n 1994

/12/ Siemens:

CP 5431 FMS with COM 5431 FMS, Volume 2

Order no. refer to latest SINEC Catalog

Siemens AG 07/94

/13/ Siemens:

CP 5430 TF with COM 5430 TF, Volume 2

Order no. refer to latest SINEC Catalog

Siemens AG 07/94❑