Schneider Electric TSXPBY100 Master Profibus DP communication module User Guide

Modicon Premium PLCs

TSX PBY 100

Profibus-DP

07/2008 eng www.schneider-electric.com

2

Document Set

Document Set

At a Glance This manual deals with both the hardware and software implementation of the

Profibus-DP module.

35015381.01 07/2008

3

Document Set

4

35015381.01 07/2008

Table of Contents

About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 1

Introduction to Profibus DP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

General introduction to Profibus-DP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

General architecture and protocol for Profibus-DP . . . . . . . . . . . . . . . . . . . . . . . 11

Multi-master architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Features of Profibus-DP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 2

Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Data transfer capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Network cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Application response time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 3

Description of the TSX PBY 100 module . . . . . . . . . . . . . . . . . 21

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.1

Description of module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

General description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Operating mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Connecting the Profibus-DP bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2

Installing the module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Mounting the module in a rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.3

Technical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Standards and characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 4

Software implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.1

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Principle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

35015381.01 07/2008

5

6

Physical or logical addressing of inputs/outputs . . . . . . . . . . . . . . . . . . . . . . . . . 41

Mapping IW and QW addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4.2

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Declaring the TSX PBY 100 module and accessing application screens . . . . . . 46

Configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Data to be provided . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Data resulting from decoding the *.CNF text file . . . . . . . . . . . . . . . . . . . . . . . . . 51

Viewing Profibus-DP master configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

General module configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Module configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4.3

Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Description of the debugging screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Debugging parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

4.4

Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Profibus-DP diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Diagnostic command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Examples of diagnostics command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Communication/operation report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

4.5

Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Diagnostics of the module’s status from the LEDs . . . . . . . . . . . . . . . . . . . . . . . 73

Downgraded application modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Lists of diagnostics variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

List of available diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Compressed diagnostics on all slaves. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Slave diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

General information on a slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Slave configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Typical errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

4.6

Language objects associated with the TSX PBY 100 module . . . . . . . . . . . . . . . 87

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Language objects in implicit exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Language objects for explicit exchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Explicit exchange management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Language objects associated with the configuration . . . . . . . . . . . . . . . . . . . . . . 94

Error code for module TSX PBY 100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Index

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

35015381.01 07/2008

About the Book

At a Glance

Document Scope This manual is aimed at users who wish to install the TSX PBY 100 master

Profibus DP communication module onto the Premium.

Validity Note The update of this publication takes PL7 V4.5 functionality into account.

Related

Documents

Title of Documentation

Profibus – Reference manual

Reference Number

See SIEMENS documentation

Product Related

Warnings

Installation of the Profibus-DP bus is described in the Profibus-DP installation manual, reference 840 USE 468 00 (English version).

User Comments We welcome your comments about this document. You can reach us by e-mail at [email protected]

35015381.01 07/2008

7

About the Book

8

35015381.01 07/2008

Introduction to Profibus DP

1

At a Glance

Subject of this

Chapter

What's in this

Chapter?

This chapter introduces the main features of communication on the Profibus DP.

This chapter contains the following topics:

Topic

General introduction to Profibus-DP

General architecture and protocol for Profibus-DP

Multi-master architecture

Features of Profibus-DP

Page

10

11

13

14

35015381.01 07/2008

9

Introduction to Profibus DP

General introduction to Profibus-DP

At a Glance

Input/output modules

Profibus-DP is a serial link field bus for sensors and actuators, which responds to the demands of the industrial environment.

This bus uses the master/slave procedure. The master subscriber manages and coordinates access to the bus, it transmits data to and receives data from all the subscribers.

z z

Devices such as input/output modules are also available : z compact Classic TIO slaves: z classic discrete inputs, z classic discrete outputs.

DEA203 modular slaves

Momentum modular slaves: z discrete inputs, z z z discrete outputs, discrete inputs/outputs, analog inputs/outputs.

Input/output modules are used to link up sensors and actuators for checking or monitoring machines or processes to the Profibus-DP system.

10

35015381.01 07/2008

Introduction to Profibus DP

General architecture and protocol for Profibus-DP

General architecture

The architecture of the Profibus-DP field bus is used to implement the TSX PBY 100 module and slave devices.

This illustration shows the shortest network cycle time.

Master Premium

Slave 4 Slave 18 Slave 6

124 slaves maximum with number of repeaters

Slave 66

35015381.01 07/2008

11

Introduction to Profibus DP

Connection rules A Profibus-DP bus can be made up of several electric and optic segments interconnected by repeaters.

Protocol

Each of the electric segments must be adapted (impedance) and you must use: z z

Two connectors: ref. 490NAD91103 (yellow) mounted on the devices situated at the ends of each electric segment.

For the other connections, you must use these connectors: ref. 499NAD91104 or

490NAD91105 (gray).

You must ensure that there is cable screening continuity at connector level, otherwise the devices may be weakened.

It is advisable to use an optic segment between two constructions or to add surge absorbers on the electric segments.

The protocol principle is based on a master/slave type bus. This principle guarantees excellent response times on I/O type exchanges (cyclic exchanges), with a maximum network cycle time less than 5 ms at 12 Mbds.

Only the master stations, sometimes called active stations, have access rights to the bus. The slave (or passive) stations can only respond to prompts and requests.

Profibus-DP station addressing z z

Several types of device are standardized:

Master class 1 generally PLC, robot, digital command, etc.

Master class 2 configuration devices, programming and master diagnostics.

z Slaves.

The Profibus-DP stations allocated to the PBY module can be identified using a number between 1 and 125.

This address corresponds to the station connection point on the bus registered in the configuration.

12

35015381.01 07/2008

Introduction to Profibus DP

Multi-master architecture

At a Glance

Illustration

The Profibus DP field bus allows there to be several master stations.

In a multi-master configuration, each master station is associated to slaves and so forms a sub-system.

This illustration describes a Profibus DP field bus multi-master architecture implementing a TSX PBY 100 module and slave devices.

Premium master 1 Premium master 2

I/O modules

(slaves 1, 2 and 3)

DP slaves

I/O modules

(slaves 4 and 5)

35015381.01 07/2008

13

Introduction to Profibus DP

Features of Profibus-DP

Introduction

Transmission features

Profibus-DP is a linear bus, designed for transfers of high speed data. The PLC communicates with its peripheral devices via a high-speed serial link.

Data exchange is mainly cyclic.

This table describes the transmission features of the Profibus-DP bus supported by the TSX PBY 100 module.

Topology

Transmission mode

Transmission rate

Maximum segment length

Possible transmission media

Serial link

Linear bus with line terminations

Half Duplex

9.6 / 19.2 / 93.75 / 187.5 / 500 / 1500 Kbits/s up to 3 / 6 / 12 Mbit/s

100 m at 3 / 6 / 12 Mbit/s (400 m with 3 repeaters)

200 m at 1.5 Mbit/s (800 m with 3 repeaters)

546.81 yd at 500 Kbit/s (2,187.23 yd with 3 repeaters)

1000 m at 187.5 Kbit/s (4000 m with 3 repeaters)

1200 m at 9.6 / 19.2 / 93.75 Kbit/s (4800 m with 3 repeaters)

Twisted pair line (standard version, type RS 485)

Fiber optic link

Waveguide

9 point DSUB, M12 or Domino Block

Capacity This table describes the Profibus-DP bus transmission capacity for Premium PLCs.

Number of master stations per PLC

Number of slave stations

Number of inputs/ outputs

0 with TSX 57-10 processors

1 with TSX 57-20/25 processors (from version V3.0 onwards)

2 with TSX/PMX/PCX 57-30/35/40/45 processors (from version

V3.0 onwards)

32 without repeaters

124 with repeaters (the number of authorized repeaters depends on the repeaters, please refer to the documentation of the repeaters used)

4096 inputs / 4096 outputs (corresponds to 242 input words and

242 output words)

14

35015381.01 07/2008

Performance

2

At a Glance

Subject of this

Chapter

What's in this

Chapter?

This chapter introduces Profibus DP bus performance.

This chapter contains the following topics:

Topic

Data transfer capacity

Network cycle

Application response time

Page

16

17

18

35015381.01 07/2008

15

Performance

Data transfer capacity

At a Glance The PBY 100 module requires configuration data slaves containing than 250 bytes and diagnostics data slaves containing less than 244 bytes.

It is used to store configuration data for 125 devices whose total maximum size is

16 Kbytes.

Transmitted data The following table shows the size of input/output image data in words:

Data

Image of inputs in words (%IW) for configuration

Image of outputs in words (%QW) for configuration minimum

-

maximum

242

242

Data per slave The following table shows the size of data per slave in bytes:

Data

Configuration data per slave (in bytes)

Configuration data per slave

Maximum size of all configuration data

6

minimum

31 maximum

250

244

16 Kb

16

35015381.01 07/2008

Performance

Network cycle

At a Glance

Configuration

The network cycle depends on the rate of transfer, the number of slaves connected to the bus and the number of input/output words.

The following table shows the network cycle times for several possible configurations.

Configuration

Transfer rate 12 Mbit/s

124 slaves

242 input words and 242 output words

Transfer rate 12 Mbit/s

124 slaves

126 input words and 126 output words

Transfer rate 12 Mbit/s

32 slaves

32 input words and 32 output words

Transfer rate 12 Mbit/s

1 slave

1 input word and 1 output word

Transfer rate 500 Mbit/s

124 slaves

126 input words and 126 output words

Transfer rate 500 Mbit/s

32 slaves

32 input words and 32 output words

Transfer rate 500 Mbit/s

1 slave

1 input word and 1 output word

Network cycle time (ms)

5 ms

5 ms

2.4 ms

1 ms

100 ms

25 ms

1.8 ms

35015381.01 07/2008

17

Performance

Application response time

At a Glance The application response time is a logical response time, which does not take into account the filtering time or the response time of the sensor and actuator interfaces.

Illustration The following example shows the time elapsed between acquiring an input and setting an output at a transmission rate of 12 Mbit/s.

I

1

O

1

MAST cycle time: 10 ms

I

1

Response time

O

1

18

35015381.01 07/2008

Calculation example

Performance

The following table groups together the different elements for calculating the application response time.

max. updated %IW / QW

Maximum number of I/O modules

32

Maximum number of I/O for the process

1024

64

Min.

128

4096

124

Min.

242

7744

124

Min.

Max. =

2 x min.

4,8 5

Max. =

2 x min.

10 11

Max. =

2 x min.

22 Scanning time (ms)

(acquiring image I

1

)

2,44

MAST cycle time (in ms) (I

1

= O

1

)

10,00

IBS scanning time (in ms)

(updating O image

1

)

2,44

Application response time (in ms)

14,88

20,00

4,8

29,6

10,00

5

20

20,00

10

40

10,00

11

32

20,00

22

32

35015381.01 07/2008

19

Performance

20

35015381.01 07/2008

Description of the TSX PBY 100 module

3

At a Glance

Subject of this

Chapter

What's in this

Chapter?

This chapter introduces the main features of the TSX PBY 100 module.

This chapter contains the following sections:

Section

3.1

3.2

3.3

Topic

Description of module

Installing the module

Technical specifications

Page

22

27

31

35015381.01 07/2008

21

Description of the TSX PBY 100 module

3.1

Description of module

At a Glance

Subject of this

Section

What's in this

Section?

This section describes the physical appearance of the module and its operation.

This section contains the following topics:

Topic

General description

Operating mode

Connecting the Profibus-DP bus

Page

23

25

26

22

35015381.01 07/2008

Description of the TSX PBY 100 module

General description

At a Glance

Illustration

The TSX PBY 100 module can be installed on a standard or extendable Premium

PLC rack.

The TSX PBY 100 module is made up of several elements:

35015381.01 07/2008

23

Description of the TSX PBY 100 module

Description of elements

5

6

3

4

The following table describes the different elements:

Number

1

2

Function

A reception module to be placed in any I/O slot.

An indicator block made up of 4 LEDs.

Diagnostics of the module’s status from

the LEDs, p. 73

A slot for receiving a PCMCIA card.

A Profibus-DP PCMCIA card.

A cable of 0.6m for linking up to a connection box.

A Profibus connection box, Profibus-DP bus connection interface.

Utilities The TSX PBY 100 module is a master class 1 type device and provides the following utilities:

Utilities

DATA_EXCHANG

E

SLAVE_DIAG

SET_PRM

Request or response request

To or from slave request request

CHK_CFG

GLOBAL_CONTR

OL

GET_MASTER_D

IAG request request request

Comments input/output data transfer slave slave slave diagnostics utility transmission of parameters to slaves on power-up configuration check on power-up slave slave global bus control (automatically taken on by the Profibus card) master class 2 master diagnostics utility (automatically taken on by the Profibus card)

24

35015381.01 07/2008

Description of the TSX PBY 100 module

Operating mode

Operation The following illustration shows how the module operates:

Module stopped Module off

Power up

Module configured

Reset

Configuration

Communication function effective when module is configured

Module in self-testing phase

Module not configured Self-tests OK

Behavior Description of the different operating modes of the module: z Profibus DP in RUN mode : data exchange on the bus.

z Task in RUN mode : input/output update.

z Task in STOP mode : z z input update, output fallback strategy (maintained or reset to zero).

35015381.01 07/2008

25

Description of the TSX PBY 100 module

Connecting the Profibus-DP bus

Illustration Female 9 point Sub-D 9 connector RS 485

Description

6

7

4

5

8

9

2

3

Number

1

Description

Shield

M24: 24 V output voltage ground

RxD/TxD-P : positive data transmission (RD+ / TD+)

CNTR-P: positive repeater monitoring signal (direction monitoring): not used

DGND : data transmission ground

VP : line termination bias voltage

P24: output voltage 24 V

RxD/TxD-N : negative data transmission (RD- / TD-)

CNTR-N: negative repeater monitoring signal (direction monitoring): not used

Note: RxD/TxD-P, DGND, VP, RxD/TxD-N signals are mandatory. The other signals are optional

26

35015381.01 07/2008

Description of the TSX PBY 100 module

3.2

Installing the module

Mounting the module in a rack

General The mounting and removal of a module can be done with the power on.

Inserting/extracting module with the power on must be done by doing/undoing the screws manually in order to maintain an adequate sequencing of the connection/ disconnection of the signals on the X bus. Using an electric screwdriver cannot assure this sequencing.

Procedure

Step Action

1 Place the pins situated on the back of the module in the centering holes situated on the lower part of the rack.

Illustration

35015381.01 07/2008

27

Description of the TSX PBY 100 module

Step Action

2 Pivot the module in order to bring it into connect with the rack.

Illustration

3 Fix the module to the rack by tightening the screw situated on the upper part of the module

28

35015381.01 07/2008

35015381.01 07/2008

Description of the TSX PBY 100 module

Step Action

4

Illustration

You must not insert or take out the communication card while the reception module is powered up.

Insert the card into its slot

5 Screw the card in so that it cannot move, thus ensuring it will operate properly.

29

Description of the TSX PBY 100 module

Step Action

6

Illustration

You must not connect or disconnect the connection unit while the module is powered up.

Connect the cable to the connection unit

7 Screw the connector in so that it cannot move, thus ensuring a good connection.

30

35015381.01 07/2008

Description of the TSX PBY 100 module

3.3

Technical specifications

At a Glance

Subject of this

Section

What's in this

Section?

This section describes the technical specifications for using Profibus DP communication with the TSX PBY 100 module.

This section contains the following topics:

Topic

Compatibility

Standards and characteristics

Operating conditions

Page

32

33

34

35015381.01 07/2008

31

Description of the TSX PBY 100 module

Compatibility

Hardware

Software

The following table shows the number of TSX PBY 100 modules available for each processor:

Version Module number

V3.0

≥

V3.3

≥

V5.0

Processor type

TSX

P57 102

P57 202/252

P57 302/352

P57 402/352

PMX

P57 102

PCX

57 1012

P57 202/352/452 57 3512

P57 102

P57 202/252

P57 302/352

P57 402/452

P57 103/153

P57 203/2623/253/

2823

-

P57 303/353/3623/

453/4823

-

P57 102

P57 202

P57 352

P57 452

-

57 1012

-

57 3512

-

57 203

57 353

0

1

2

0

1

0

1

2

The TSX PBY 100 reception module is a master class 1 type device and can be integrated into a multi-master configuration. It is compatible with the communication methods of: z z master / slave, logical token ring.

The TSX PBY 100 module is compatible with the software SYC SPU LF (SyCon) from version V2.8 and PL7 software version from V3.0.

These two software applications operate under Windows XP Professional.

Note: Windows VISTA Professionnel Edition 32 does not supporte the SyCon software.

32

35015381.01 07/2008

Description of the TSX PBY 100 module

Standards and characteristics

Standards The TSX PBY 100 communication module complies with the following international standards:

EC Standards

US Standards

Canadian Standards

IEC 1131-2, CENELEC (50081-2)

UL508

CSA C22.2 No. 142-M1987

The TSX IBY 100 module also complies with the following standards:

Marine classification

US Standards z z z z

Germanischer Lloyd

Det Norsk Veritas

Bureau Veritas

Lloyds Register

FM, Class I.Div.2 (CSA C22.2 No 213-M1987)

Certification

Characteristics

PBO

The electric characteristics are as follows: z z

Logical DC V supply: 5 V DC provided by the rack power supply.

Current consumed on 5 V: 400 mA.

35015381.01 07/2008

33

Description of the TSX PBY 100 module

Operating conditions

z Ambient operating temperature: 0 °C to + 60 °C (IEC 1131-2 = + 5 °C to + 55 °C).

Operating temperature

Hygrometry

Altitude

Mechanical standards

Electrostatic discharge standard z 30 % to 95 % (without condensation) z 0 to 2000 meters z z

Vibration immunity: complies with the IEC 68-2-6 standard, Fc test.

Shock immunity: complies with the IEC 68-2-27 standard, Ea test.

z Electrostatic discharge immunity: complies with the IEC 1000-4-2 standard, level 3.

Note: minimum level in conditions defined by the standards

HF parasite standard

BF parasite standard z z z

Immunity to radiated electromagnetic fields: complies with the IEC 1000-4-3 standard, level 3.

Immunity to rapid burst transients: complies with the standard

IEC 1000-4-4, level 3.

Immunity to radiated electromagnetic fields: complies with the IEC 1000-4-12 standard, level 3.

Note: minimum level in conditions defined by the standards z Complies with prescriptions of the IEC 1131-2 standard.

34

35015381.01 07/2008

Premium PLC protection handling

Description of the TSX PBY 100 module

Premium PLCs meet the "ACP" processing demands (All Climate Processing)

For installations in industrial production workshops, or in an environment corresponding to "PWH" (Processing for Warm and Humid environments),

Premium PLCs must be inserted into IP54 minimum protection envelopes as prescribed by IEC 664 and NFC 20 040 standards.

Reminder

Premium PLCs have an IP20 protection index. They can therefore be installed without an envelope in premises with restricted access which do not exceed pollution level 2 (control room with no machines or dust-producing activity).

Note: when a position is not occupied by a module, a TSX RKA 02 protection cover must be installed in it.

Instructions relating to transport and storage

These instructions comply with the IEC 1131-2 standard.

z z

Storage temperature: -25 degrees C to +70 degrees C.

Relative humidity: 5 % to 95 % (without condensation).

35015381.01 07/2008

35

Description of the TSX PBY 100 module

36

35015381.01 07/2008

Software implementation

4

At a Glance

Subject of this

Chapter

What's in this

Chapter?

This chapter describes the different possibilities for the configuration and diagnostics of a Profibus-DP application.

This chapter contains the following sections:

Section

4.1

4.2

4.3

4.4

4.5

4.6

Topic

General

Configuration

Debugging

Programming

Diagnostics

Language objects associated with the TSX PBY 100 module

Page

38

45

58

63

72

87

35015381.01 07/2008

37

Software implementation

4.1

General

At a Glance

Subject of this

Section

What's in this

Section?

This section describes the principles of installing the TSX PBY 100 module.

This section contains the following topics:

Topic

Principle

Physical or logical addressing of inputs/outputs

Mapping IW and QW addresses

Page

39

41

43

38

35015381.01 07/2008

Software implementation

Principle

Introduction When installing Profibus-DP, the physical context of the application into which it will be integrated (rack, supply, processor, modules or devices, etc.) must be defined, and its software must be installed.

This second aspect is done from the various PL7 editors: z z either offline, or in online mode (modification is limited to certain parameters).

35015381.01 07/2008

39

Software implementation

Installation principle

The table below shows the different phases of installation.

Mode

Offline

On or offline

Online

Phase

Module declaration

Configuration (1)

Symbolization

Programming

Transfer

Description z z

Selection: z of geographical position (number and slot when a module is on a rack), z of module type.

Entering the configuration parameters,

Declaring bus configuration using the software

SyCon and creating a *.CNF text file.

Symbolizing variables associated with the Profibus-DP bus using the variables editor.

z z

Bit and word objects associated with the module or the

Profibus-DP link.

Module-specific instructions (OFs).

Transferring the application to the PLC.

An application transfer to a PLC or a cold start of the application configures and starts up the Profibus-DP.

On or offline

Debug

Diagnostics

Documentation z z z z

Different methods are accessible for debugging the application, controlling inputs/outputs and fault diagnostics:

PL7 language objects, the PL7 debugging screen, the SyCon software, module signalization.

Printing the various pieces of information relating to Profibus-DP bus configuration.

(1) When configuring a Profibus-DP installation, SyCon software (available on CD-ROM) needs to be used. This software comprises a library of profiles which describe each device which can be connected to Profibus-DP. For an update, consult our regional office.

40

35015381.01 07/2008

Software implementation

Physical or logical addressing of inputs/outputs

At a Glance

Topology

Inputs/outputs respect the topology used by the PL7 software and can be identified: z z either by physical addressing, or by logical addressing.

Addressing is defined in the following way:

% I or Q

Symbol Type of objects

I = input

Q = output

X, W or D

Format

X = Boolean

W = word

D = double word xy

Rack address x = 0 to 7

Module position y = 0 to 10

.

i .

Channe l no.

i = 0 r :

Position r = 0 to

253

Xj

Bit j = 0 to 15

Block assignment

DP data is exchanged in the form of input/output blocks. All a slave’s input data is indexed by adjacent %IW blocks, and a slave’s output data is indexed by adjacent

%QW blocks. The continuity of %IW and %QW blocks is valid even for a modular slave.

Each data block for a slave or modular slave slot starts with a new %IW or %QW.

As a result, the first I/O word of a slave is always associated to a new %IW or %QW.

In the event where a slave image (%IW or %QW) has a special size (for example 1 byte or 3 bytes), it is completed by unused bytes in order to manipulate the I/O words.

35015381.01 07/2008

41

Software implementation

Example The table below describes an example of assignment:

Input image

Slave 2

2 words

Slave 1

1 byte

%IWm.0.i

%IWm.0.i+1

Unused byte

%IWm.0.j

Only bits 0 to 7 are significant

Output image

Slave 17

2 words

%QWm.0.i %QWm.0.i+1

Slave 17

1 word

%IWm.0.k

Slave 2

1 byte

Unused byte

%QWm.0.j

Only bits 0 to 7 are significant

42

35015381.01 07/2008

Software implementation

Mapping IW and QW addresses

General Mapping input/output data addresses is used to achieve the clearest possible addressing.

A slave can be made up of several modules of different data sizes. In this case, misalignment of addresses can happen.

To avoid this, modules can be physically positioned in the slave rack by: z z z z grouping together input modules of a particular size (e.g.: 1 byte) for each pair, grouping together output modules of a particular size (e.g.: 1 byte) for each pair, positioning a single input module of a particular size (e.g.: 1 byte) at the last input module position, positioning a single output module of a particular size (e.g.: 1 byte) at the last output module position.

Example: nonmapped modules

Slave x in non-mapped modules

Module A

1 input word

Module B

1 input byte

Module C

1 output byte

Module D

1 input word

Module E

1 output word

Module F

1 output byte

Input image

%IWm.0.x

Module A

1 input word

%IWm.0.x+1

Module B

1 input byte

Output image

%IWm.0.x

Module C

1 output byte

%IWm.0.x+2

Module D

1 input word

Unused byte

Module E

1 output word

%IWm.0.x+1

Module F

1 output byte

35015381.01 07/2008

43

Software implementation

Example: mapped modules

Slave x in mapped modules

Module A

1 input word

Module D

1 input word

Module B

1 input byte

Module E

1 output word

Module C

1 output word

Module F

1 output byte

Input image

%IWm.0.x

Module A

1 input word

Output image

%IWm.0.x

Module E

1 output word

%IWm.0.x+1

Module D

1 input word

%IWm.0.x+2

Module B

1 input byte

%IWm.0.x+1

Module C

1 output byte

Unused byte

Module F

1 output byte

44

35015381.01 07/2008

Software implementation

4.2

Configuration

At a Glance

Subject of this

Section

What's in this

Section?

This section describes the Profibus-DP configuration screen.

This section contains the following topics:

Topic

Declaring the TSX PBY 100 module and accessing application screens

Configuration screen

Data to be provided

Data resulting from decoding the *.CNF text file

Viewing Profibus-DP master configuration

General module configuration

Module configuration file

Page

46

48

50

51

53

54

56

35015381.01 07/2008

45

Software implementation

Declaring the TSX PBY 100 module and accessing application screens

Declaring the

TSX PBY 100 module

To declare a TSX PBY 100 module, refer to the PL7 Premium Applications documentation.

46

35015381.01 07/2008

Procedure

35015381.01 07/2008

3

4

5

Software implementation

This operation allows you to use the software to declare a TSX PBY 100 module in a PLC rack.

The example below concerns a TSX PBY 100 module, the procedure being identical regardless of the module type in the rack.

Step

1

2

Action

Access the application's hardware configuration screen.

Double click on the slot in which the module is to be configured.

Result: the Add module screen appears.

Add module

Family:

Analog 1.5

Communication1.5

Counting 1.5

Remote BusX 1.0

Movement

Weighing

1.5

1.7

Simulation 1.0

All or Nothing 1.5

Module:

TSX IBX 100

TSX IBY 100

InterBus-S ISA MODULE

InterBus-S MODULE

TSX PBY 100 PROFIBUS-DP MODULE

TSX SCY 21601 PCMCIA DOCKING MODULE

TSX ETY 110

TSX ETY 120

TSX ETY 210

TSX ETY 410

TCP/IP ETHWAY MODULE

ETY120 ETHERNET MODULE

TCP/IP ETHWAY MODULE

TCP/IP INTRANET MODULE

TSX SAY 100 AS-Interface MODULE

TSX SCY 21600 PCMCIA DOCKING MODULE

OK

Cancel

Select from the field Family

→

Communication .

Select the module reference from the Module field (in the example TSX PBY 100 ).

Click on OK to confirm the selection.

Result: the module is declared in its slot; the slot is grayed out and contains the module reference.

Configuration

TSX 57203 V3.3 ...

XMWI

XTI..

0

0

0

2

6

P

S

Y

0

2

0

5

7

3

T

S

X

1 2

1

0

0

P

B

Y

3 4

6 Double click on the module (in the example TSX PBY 100 ) to access the configuration screen (See: PL7 Micro, Junior, Pro; Communication module for

Modicon Premium PLCs).

47

Software implementation

Configuration screen

At a Glance

Illustration

The configuration screen is made up of two zones and is used to set the features required for a Profibus-DP link

This screen allows the following parameters to be displayed and modified:

1

2

TSX PBY 100 [RACK 0 POSITION 6]

Configuration

Designation: PROFIBUS-DP MODULE

3

InterBus-S Configuration

Adr.

1

2

3

ID

0x1354

0x2354

Act.

1

1

ID Gr.

0

0

WatchDog

1

1

PROFIBUS-DP general configuration

Task

MAST

Outputs

Maintain

IW/QW number

In words 128

Reset

Diagnostics length

In bytes 32

PROFIBUS-DP tool Master configuration

Display hil scher

PROFIBUS-DP configuration file

Load CNF E:\CNF\L21CIE67.CNF

PROFIBUS-DP slave data

%IW

Adr.

Symbol

5

6

7

8

9

2

No. %IW No. %QW

2 2

%QW

Adr.

Symbol

48

35015381.01 07/2008

Description

Software implementation

The table below shows the different zones of the configuration screen:

6

7

Numbe r

1

Element

2

Function

Title bar Indicates the reference of the selected module and its physical position in the rack

Module zone Allows the parameter type to be selected: z from a drop-down menu enabling configuration or de-bugging mode to be selected (online mode only), z from a window displaying the designation of the selected module.

3

4

5

8

9

Specific zones

Drop-down list showing the configuration of the Profibus-DP bus.

See

Data resulting from decoding the *.CNF text file, p. 51

The three fields show: z z z

No. of slaves: total number of slaves.

No. %IW: total number of input words.

No. %QW: total number of output words.

General parameters allow definition of the strategy to be applied upon the application stopping. See

General parameters, p. 50

Icon for starting the software.

" View button for starting the file converter. See Viewing Profibus-

DP master configuration, p. 53

This window is used to select the *.CNF configuration file. See

General module configuration , p. 54

This window is used to display addresses and symbols associated with input and output data for a device on the list. See Profibus-DP

slave data, p. 52

35015381.01 07/2008

49

Software implementation

Data to be provided

At a Glance To configure the communication channel, you must complete the parameters in the

General parameters window dedicated to the application:

General parameters

The window looks like this:

PROFIBUS-DP general configuration

Task

MAST

Outputs

Maintain Reset

Number of IW/QW Diagnostics length

In words 128 In bytes 32 z The Task field is used to select the task which drives the Profibus-DP bus: z MAST : default value, selects the master task as the bus driver.

z FAST : selects the fast task as the bus driver.

z z z

The IW/QW Number field is used to select the number of words used for the inputs/outputs: 32, 64, 128 or 242.

The Output field is used to select the fallback mode of the outputs when the PLC is switched off : z Maintain : the value of the outputs is maintained.

z Reset : reset to zero.

The Diagnostics length field is used to select the diagnostics length in bytes from

6 to 244 bytes (32 by default). The size configured should be sufficient to contain the most important bus diagnostics. If the size is insufficient, the slave concerned will not be active on the bus because its diagnostics will be invalid.

Note: in order to optimize performance, select a minimum number of input/output words and diagnostics bytes compatible with the actual bus configuration.

50

35015381.01 07/2008

Software implementation

Data resulting from decoding the *.CNF text file

At a Glance

Profibus-DP configuration

One part of the configuration screen is used to display the Profibus-DP field bus topology as well as information on the slaves, which are associated to the module.

It is split into two windows: z z the Profibus-DP configuration window, the Profibus-DP slave data window.

The Profibus-DP configuration drop-down list shows the configuration of the

Profibus-DP field bus. It shows the contents of the *.CNF text file selected. The configuration of the 125 possible devices can be accessed in this manner.

Each line of this drop-down list shows the status of a single device. A line is presented in the format:

Addr.

1

2

3

ID

0x1354

0x2354

Act.

Gr. ID WatchDog

1

1

0

0

1

1 z z z z z

The first field indicates the address of the slave device (between 1 and 125).

The second field indicates the Profibus identification code from the GSD file of the slave device.

The third field shows whether the slave is activated in the Profibus configuration file.

The fourth field is always 0.

The last field shows whether the slave guard dog is activated in the Profibus configuration file.

35015381.01 07/2008

51

Software implementation

Profibus-DP slave data

The window looks like this:

PROFIBUS-DP slave data

%IW

Addr.

%IW6.0

%IW6.0.1

Symbol

%QW

Addr.

Symbol

Two lists displaying the input/output addresses and symbols: z z the top list shows the input data relating to the selected device, with their associated symbol, the bottom list shows the output data relating to the selected device, with their associated symbol.

52

35015381.01 07/2008

Software implementation

Viewing Profibus-DP master configuration

At a Glance

Illustration

By pressing the View button, you are able to view the master and bus configuration parameters. This screen is enabled when you have selected a *.CNF text file.

If no *.CNF text file has been selected, a default file appears. It shows a master module with no slave.

The screen is presented in the following format:

Master configuration

Station address 1

Bus configuration

Baud rate 12M baud

Number of slaves 2

Gap Update Factor

Highest St Addr

Retry Limit

10

1

4

Slot Time

Min St Delay Resp

Max St Delay Resp

Quiet Time

Setup Time

1000

11

800

9

16

Token Rot. Time 6459

Min Slave

Interval

Polling Timeout

Data Control

Time

1

10

120

100µs

1 ms

10 ms

OK

Note: the bus parameters are calculated automatically by the SyCon configuration tool. A manual adaptation may be necessary for the pathways deliverd without using the GSD file and which are not entered in the Profibus configuration file. The documentation handling the pathways provides information on the potential adaptations.

Note: for further information, please refer to the SyCon software documentation and theModule configuration file (see

Illustration, p. 56 ).

35015381.01 07/2008

53

Software implementation

General module configuration

At a Glance Module configuration is split into two parts: z z

Configuring the general parameters.

Configuring the TSX PBY 100 module.

How to configure general parameters

The following procedure is used to configure the general parameters.

Step

1

2

3

4

Action

Select the type of task that will drive the bus.

Select the number of words used for the inputs/outputs.

Select the action of PMS services upon the application stopping.

Select the action of output upon the application stopping.

54

35015381.01 07/2008

Software implementation

How to configure the PBY module

The following procedure is used to configure the TSX PBY 100 module with SyCon.

Step

1

Action

Click on the Hilscher button.

2

3

4

Result: SyCon software is activated.

z z

Under SyCon, configure: z z the bus topology, memory allocation: addressing for each image module in the %IW and %QW registers, group settings, special functions.

Export this configuration into the *.CNF text file.

Click on the Load CNF button.

Result: the following window appears.

Open

Search:

0.cnf

120.cnf

250.cnf

255.cnf

256.cnf

257.cnf

Cnf

264.cnf

4.cnf

40.cnf

atelier.cnf

Bad.cnf

ibus.cnf

m2siby4k.cnf

?

5

6

7

Name:

Type: atelier.Cnf

CNF FILE (*.cnf)

Open

Cancel

Find and select the *.CNF text file which describes the configuration being used.

Confirm your selection using the Open button.

The file is rejected if: z z the file format is incorrect, there are over 125 devices.

Confirm the configuration.

35015381.01 07/2008

55

Software implementation

Module configuration file

At a Glance A file describing the application configuration for the TSXPBY100 module is available in the PL7 documentation editor.

It is presented in the following format: Illustration

TSX PBY 100 [RACK 0 POSITION 4]

Module identification

Ref. Commercial :

Address:

Channel parameters: 0

TSX PBY 100

004

Profibus-DP general configuration :

Task: MAST

No. of IW/QW: 128 words

Profibus-DP configuration file:

Profibus-DP master configuration :

Station address: 1

Designation:

Symbol:

Outputs:

Diagnostics length:

No. of slaves:

Baud rate:

Slot Time:

Min St Delay Resp

Setup Time

Gap Update Factor

Highest St Addr:

1.5M baud

2000 tBit

11 tBit

1 tBit

1

126

Polling Timeout 500 ms

Profibus-DP slave configuration

Profibus-DP slave language objects

Quiet Time:

Max St Delay Resp:

Token Rot. Time

Retry Limit:

Min Slave Interval:

Data Control Time:

Profibus-DP module

Reset

32 bytes

0

6 tBit

55 tBit

50000 tBit

3

1 * 100 microseconds

100 * 10ms

56

35015381.01 07/2008

35015381.01 07/2008

Software implementation

Key:

Slot Time

Min St Delay Resp.

Setup Time

Gap Update Factor

Highest St addr.

Quiet Time

Max St Delay Resp.

Token Rot. Time

Retry Limit

Min Slave Interval

Data Control Time

Maximum waiting time before the master starts responding to a request

Minimum waiting time before a slave is authorised to reply

(transmission delay included)

Waiting time between the sending of the last bit by the slave and the master’s acceptance of the response

Specify the number of bus cycle the master uses to search for other masters on the network.

The master looks for the other masters on the network only as far as this address.

Time needed for a signal to return to zero after sending a frame.

During this time devices are only active on the bus.

Maximum time during which the master waits for the slave to respond

Maximum token rotation time

When a slave does not respond, the master again asks the slave to transmit. It scans the next slave when the Retry Limit delay has been reached.

Minimum time before a slave is rescanned.

Maximum time for data exchange between the master and each slave.

Note: a manual configuration of the bus parameters may be necessary,see

Viewing the Profibus-DP master configuration (see

Illustration, p. 53 ).

57

Software implementation

4.3

Debugging

At a Glance

Subject of this

Section

What's in this

Section?

This section describes the debugging mode screen.

This section contains the following topics:

Topic

Description of the debugging screen

Debugging parameters

Page

59

61

58

35015381.01 07/2008

Software implementation

Description of the debugging screen

At a Glance

Illustration

The Debugging function or the ability to double click on the TSX PBY 100 graphical module in the PL7 configuration is only available in online mode.

This selection allows us to display the following screen:

1

2

5

TSX PBY 100 [RACK 0 POSITION 6]

Debugging

Designation: PROFIBUS-DP MODULE

CH0 RUN ERR IO

PROFIBUS-DP slave configuration

Addr

1

2

3

ID

0x1354

0x2354

Act.

1

1

Gr. ID

0

0

WatchDog

1

1

DIAG...

PROFIBUS-DP diagnostic data

MASTER ID: 0x1654 V5.02I FW: 1.0 (7)

Operate mode c0 00 16 54 10 14 10 10 07 56 35 2e 30 32 49 00

PROFIBUS-DP tool Master configuration

View hil scher

Addr.

Symbol Value

3

4

6

7

8

Edit %QW

%QW

Addr.

Confirm

Symbol

Format

Bin Hex

Value

Dec

9

10

Total

No. of slaves No. of

2 2

No. of

2

35015381.01 07/2008

59

Software implementation

Description The table below shows the different zones of the debugging screen:

1

2

Numbe r

Element

Title bar

Function selection

3

4

5

6

7

Function

Indicates the product reference and the position of the module

Debugging (available in online mode only) or Configuration

Lights Indicate the state of the module: z RUN lit: the module is in operation z ERR lit: there is a fault in the module

DIAG button When a module fault is detected, this button allows access to status information for this module (this button is disabled or enabled according to the value of the %Ixy.MOD.ERR bit)

Profibus-DP

Configuration

Profibus-DP diagnostic data

Hilscher button z z

This drop-down list shows the configuration of the Profibus-DP field bus. When a device has a fault: the cursor places itself over that device, the corresponding line appears in red

This window is used to carry out diagnostics on the Profibus-DP bus. See

Profibus-DP diagnostics, p. 64

Icon for starting the software.

8

9

10

View button

Profibus-DP slave data

Button for starting the file converter. Viewing Profibus-DP master

configuration, p. 53

Used to display addresses and symbols associated to input and output data for a device on the list. See

Slave data, p. 61

The three fields show: z z z

No. of slaves total number of slaves.

No. %IW: total number of input words.

No. %QW: total number of output words.

60

35015381.01 07/2008

Software implementation

Debugging parameters

Slave data To display I/O data values for a device, select Profibus-DP slave configuration from the drop-down list.

Adr.

Symbol Value

Edit %QW

%QW

Adr.

%QW6.0

%QW6.0.1

Validate

Symbol

Format

Bin Hex

Value

-17964

-17964

Dec

Two pull down lists show the input/output data values: z z

The %IW zone field displays the input data list for the device selected, with the symbol and the associated value for each data item.

The %QW zone field displays the output data list for the device selected, with the symbol and the associated value for each data item.

z The Edit %QW zone field is used to enter the value of a %QW data item, and indicate for each data item the type of display: z z z hexadecimal, decimal,

ASCII.

Note: forcing is not authorized for %IW and %QW language objects.

The PLC switching to STOP mode makes the module’s fallback values appear in red.

35015381.01 07/2008

61

Software implementation

Diagnostics window

This window shows all the diagnostics information for a device. By selecting a device from the Profibus-DP slave configuration list, its diagnostics appear in the

Profibus-DP diagnostics data window.

PROFIBUS-DP diagnostic data

SLAVE ID: 0x1354

Diagnostics created by slave

Slave watchdog active

Master address: 1

00 0c 00 01 13 54 07 00 00 00 00 00 00

The data displayed corresponds to a new diagnostics. When a device is selected from the list, the addressed module automatically undergoes diagnostics.

In all cases of diagnostics, the first six bytes are standardized and displayed. If a slave requires more than six bytes of diagnostics, the data is displayed in the window and can be accessed using the scroll bars.

62

35015381.01 07/2008

4.4

Programming

At a Glance

Subject of this

Section

What's in this

Section?

This section describes the programming principles.

This section contains the following topics:

Topic

Profibus-DP diagnostics

Diagnostic command

Examples of diagnostics command

Communication/operation report

Software implementation

Page

64

65

68

70

35015381.01 07/2008

63

Software implementation

Profibus-DP diagnostics

General Profibus-DP diagnostic functions are used to quickly find and identify faults on devices connected to the bus. Diagnostics messages are exchanged on

Profibus DP via the TSX PBY 100 master module.

z z z z

There are four types of diagnostics:

Master diag : complete diagnostics on the TSX PBY 100 master module.

Slave diag : complete diagnostics on a single slave.

Compressed diag : compressed diagnostics on all slaves.

List of diagnostics available for each slave.

Each of these diagnostics can be read by the PL7 software or by any other debugging PC.

64

35015381.01 07/2008

Software implementation

Diagnostic command

At a Glance A diagnostics command is sent by the SEND_REQ function block.

The SEND_REQ function must be used for reading or resetting the various diagnostics counters.

In order to handle current problems, the TSX PBY 100 module provides four diagnostics counters per slave. These counters can be accessed via the

SEND_REQ function and are presented in the form of a byte table. See General

information on a slave, p. 82

35015381.01 07/2008

65

Software implementation

Syntax The communication function syntax is presented in the following format:

SEND_REQ (ADR#rm.v, 16#0031, %MWi:3, %MWj:L, % MWk:4)

The following table describes the various parameters of the function:

Parameter

ADR#rm.v

16#0031

%MWi:3

%MWj:L

Description r m v

Rack number

Module number

Channel number (0 for Profibus-DP)

Request code

Request parameters

%MWi Type of diagnostics

%MWi:x0...x8 0...125

126

127

128

129

130

131

132

%MWi:x9 Reserved

Diagnostics on slave x

List of diagnostics available

Compressed diagnostics on all slaves

Diagnostics on master module

Total diagnostics counters

Faulty exchange counters

Downtime counters

Invalid response counters

%MWi:x10 Reserved

%MWi:x11

%MWi:x12

%MWi:x13

%MWi:x14

%MWi:x15

Reserved

If activated, reading of configuration data for slave selected by %MWi.x0..x8 (= 0 to 124)

If activated, reading of information for slave selected by

%MWi.x0..x8 = 0 to 124

If activated, resetting the list of available diagnostics or the counters specified by %MWi.x0...x8 = 126, 129 to 132

If activated, reading of the list of available diagnostics or the counters specified by %MWi.x0...x8 = 126, 129 to 132

%MWi+1 Start address in the diagnostics table (default value is 0). To access part of the diagnostics table, it is possible to specify a start word in the table (Offset start) j

%MWi+2 Length of diagnostics to be read

PL7 control words where responses are stored

Number of first word

L Number of words

66

35015381.01 07/2008

Software implementation

Parameter

%MWk:4

Description

Four words identifying the address of PL7 data used to control the function k Exchange status

35015381.01 07/2008

67

Software implementation

Examples of diagnostics command

Reading diagnostics words from a slave

Diagnostics carried out on slave 2.

%M0 p

OPERATE

%MW203:=6

OPERATE

(1)

%M0

R

(1) SEND_REQ(ADR#6.0,16#0031,%MW100:3,%MW104:32,%MW200:4)

The table below describes the parameters:

Parameters

Address

Request code

Data to be sent

Reception Zone

Report

Variables

-

-

%MW100:3

%MW104:32 -

%MW200:4 -

Values

ADR#6.0

16#0031

2 (slave address in decimal)

0 (diagnostics table address in decimal)

32 (length of diagnostics table in decimal)

68

35015381.01 07/2008

Software implementation

Diagnostics on a master

SEND_REQ(ADR#6.0,16#0031,%MW100:3,%MW104:32,%MW200:4 )

Parameters

Address

Request code

Data to be sent

Reception Zone

Report

Variables

-

Values

ADR#6.0

-

%MW100:3

16#0031

126 (master code in decimal)

0 (diagnostics table address in decimal)

32 (length of diagnostics table in decimal)

%MW104:32 -

%MW200:4 -

Resetting the diagnostics counter

SEND_REQ(ADR#6.0,16#0031,%MW100:3,%MW104:32,%MW200:4 )

Parameters

Address

Request code

Data to be sent

Reception Zone

Report

Variables

-

Values

ADR#6.0

-

%MW100:3

%MW104:32 -

%MW200:4 -

16#0031

16#4081 (initialization of the total diagnostics counter in hexadecimal)

0 (diagnostics table address in decimal)

32 (length of diagnostics table in decimal)

35015381.01 07/2008

69

Software implementation

Communication/operation report

Description These messages are common to all types of requests.

16#01

16#02

16#03

16#04

16#05

16#06

Communication report (least significant byte)

Value

16#00

Meaning

Correct exchange

Operation report (most significant byte)

Value / error code

Send request code in increments of 16#30

16#01

16#02

16#03

Meaning

Positive result

Request not processed

Incorrect response

Reserved

Exchange stopped on timeout

Exchange stopped on user request (CANCEL)

Incorrect address format

16#07

16#08

16#09

16#0A

16#0B

Incorrect target address

Incorrect management parameter format

Incorrect specific parameters

Problem with sending to destination device

Reserved

Size of receive buffer is insufficient

Size of send buffer is insufficient

No processor system resources

16#0C

16#0D

16#0E

16#0F

16#10

Incorrect exchange number

No telegram received

Incorrect length

Telegram service not configured

Network module missing

70

35015381.01 07/2008

35015381.01 07/2008

16#FF

Software implementation

Message refused

Operation report (most significant byte)

Value / error code Meaning

16#01

16#02

16#03

16#04

16#05

16#06

16#07

16#08

16#0B

16#0D

16#0F

16#11

16#12

16#FD

Lack of resources communicating with the processor

Lack of line resources

Device missing

Line error

Length error

Communication channel fault

Addressing error

Application fault

No system resources

Destination missing

Intra-station routing problem or channel not configured

Address format not handled

Lack of destination resources

Invalid parameter

71

Software implementation

4.5

Diagnostics

At a Glance

Subject of this

Section

What's in this

Section?

This section describes the different diagnostics functions.

This section contains the following topics:

Topic

Diagnostics of the module’s status from the LEDs

Downgraded application modes

Lists of diagnostics variables

List of available diagnostics

Compressed diagnostics on all slaves

Slave diagnostics

General information on a slave

Slave configuration data

Typical errors

Page

73

74

76

79

80

81

82

83

84

72

35015381.01 07/2008

Software implementation

Diagnostics of the module’s status from the LEDs

At a Glance

Illustration

LEDs on the card are used to display the state of the module and the Profibus DP network. The signaling complies with Premium and Profibus DP standards.

The diagnostic LEDs are as follows:

RUN

CH0

ERR

I/O

Diagnostics Depending on the state of the LEDs, the diagnostics are as follows:

LEDs

RUN

(green)

On

TSX PBY 100 module ready

- self-diagnostic tests successful

- Profibus DP ready

Flashing

-

Off

Module has not been initialized (awaiting configuration)

ERR

(red)

Bus fault or

Configuration fault or

TSX PBY 100 module fault

Module awaiting configuration or

Currently loading (if RUN is off) or

Communication fault with the PLC (if RUN is on)

-

No fault indicated

I/O (red) Fault on one or several of the slave peripherals

CHO

(yellow)

Input/output data exchange

-

No fault indicated (all slaves are active)

No input/output data exchange

35015381.01 07/2008

73

Software implementation

Downgraded application modes

Transmission media fault z Communication fault on starting Profibus-DP

This fault can be caused by poor configuration or damage to the cable. In this case, the bus remains in a non-operational state and the slaves remain in failed start state.

z

An error code is generated by the TSX PBY 100 master module in the form of diagnostics. All the diagnostics bits of the slaves remain in their fault state. The

ERR LED is on and the other LEDs are off.

Communication fault during operation

If a fault occurs while exchanges are in progress, an error code is generated by the TSX PBY 100 master module in the form of diagnostics. In this case, the slaves switch to their pre-configured default state after the watchdog period is exceeded.

The diagnostic bits of the slaves are enabled to indicate that the slaves are not available and that inputs are reset to zero. The TSX PBY 100 module saves the diagnostics and informs the CPU of their availability using the language object

%IWm.0.129:x10..x12.

TSX PBY 100 master module faults

When a fault appears, data exchanges, commands and diagnostics are interrupted.

After the watchdog period is exceeded, an error code is generated in the form of diagnostics.

If exchanges are interrupted, the diagnostics bits of the slaves are enabled to indicate that the slaves are not available and that inputs are reset to zero. The ERR

LED is on and the other LEDs are off.

74

35015381.01 07/2008

Slave faults

Software implementation

When exchanges are in progress, a slave fault is indicated by a new diagnostic. If communication is still established, the slave generates the diagnostics, if not, the diagnostics are generated by the TSX PBY 100 master module.

The diagnostics bits of the slave are enabled to indicate that the slave is not available and that its inputs are reset to zero. The TSX PBY 100 module saves the diagnostics and informs the CPU of their availability using the language object

%IWm.0.129:x10..x12.

General PLC

CPU faults

Resetting outputs after loading an application

Note: if one or several slaves are faulty, the bus cycle slows down. Several PLC cycles may be necessary for diagnostics to be recognized and inputs to be reset to zero.

In the event of a communication fault between the CPU and the TSX PBY 100 module, all outputs are set to their default state (maintained or Reset) and inputs are reset to zero. The ERR LED flashes to indicate the communication fault between the

PLC CPU and the TSX PBY 100 module.

The transfer of diagnostics data between the master and the slave are not affected.

For a low baud rate (less than 500 Kbit/s) and a large watchdog value, the slaves maintain their output states for the whole of the watchdog period.

For a low baud rate (less than 500 Kbit/s) and a disabled watchdog, the slave output states are maintained until the application loading has finished.

35015381.01 07/2008

75

Software implementation

Lists of diagnostics variables

Master diagnostics

The following table indicates the diagnostics data for the TSX PBY 100 module.

Bytes Structure

0/1

2/3

4

5

6

7

OPERATING_MO

DE

Description

PNO_IDENTIFIER Master identification code depending on the Profibus DPcode

(byte 2 : least significant byte; byte 3: most significant byte)

Hexadecimal values:

16#1654 : for the TSX PBY 100 module

PC card hardware version

PC card firmware version

PBY hardware version

PBY firmware version

Master operating mode (byte 0: least significant byte; byte 1: most significant byte)

Hexadecimal values:

16#00 : inoperative (initialization)

16#40 : stop (ready to receive configuration)

16#80 : output fallback (depending on the configuration)

16#C0: operating

Hardware version of the PCMCIA card depending on the

Profibus DPcode

Hexadecimal values:

16#10 : version V1.0

16#XY: version VX.Y

16#FF: no card or card invalid

Software version of the PCMCIA card depending on the

Profibus DPcode

Hexadecimal values:

16#14 : version V5.02I

16#16 : version V5.02K

16#XY: version V5.XY

16#FF: no card or card invalid

Hardware version of the TSX PBY 100 module

Hexadecimal values:

16#10 : version V1.0

16#XY: version VX.Y

Software version of the TSX PBY 100 module

Hexadecimal values:

16#10 : version V1.0

16#XY: version VX.Y

76

35015381.01 07/2008

Software implementation

Bytes

8

Structure

PBY IE version

9...15

PC card firmware version (ASCII)

Description

Index of software version for the TSX PBY 100 module

Hexadecimal values:

16#04 : version IE04

16#XY: version IEXY

Software version of the PCMCIA card in ASCII mode

Master Class 2 diagnostics

For Profibus DP, a Master Class 2 device has the following standard TSX PBY 100 module diagnostics data:

Bytes

0

1/2

3

Structure

OPERATING_MO

DE

Description

Master operating mode

Hexadecimal values:

16#00 : inoperative (initialization)

16#40 : stop (ready to receive configuration)

16#80 : output fallback (depending on the configuration)

16#C0: operating

PNO_IDENTIFIER Master ID code depending on the Profibus DPcode (byte 1 : least significant byte; byte 2: least significant byte)

Hexadecimal values:

16#1654 : for the TSX PBY 100 module

PC card hardware version

Hardware version of the PCMCIA card depending on the

Profibus DPcode

Hexadecimal values:

16#10 : version V1.0

16#XY: version VX.Y

16#FF: no card or card invalid

4

5

PC card firmware version

PBY hardware version

Software version of the PCMCIA card depending on the

Profibus DPcode

Hexadecimal values:

16#14 : version V5.02I

16#16 : version V5.02K

16#XY: version V5.XY

16#FF: no card or card invalid

Hardware version of the TSX PBY 100 module

Hexadecimal values:

16#10 : version V1.0

16#XY: version VX.Y

35015381.01 07/2008

77

Software implementation

Bytes Structure

6 PBY firmware version

Description

Hardware version of the TSX PBY 100 module

Hexadecimal values:

16#10 : version V1.0

16#XY: version VX.Y

Note: the most and least significant diagnostics bytes of the PNO_IDENTIFIER are transposed in relation to the standard diagnostics on Profibus DP.

78

35015381.01 07/2008

Software implementation

List of available diagnostics

At a Glance This table provides the activity bits. With one bit per slave, they provide information on the availability of new diagnostics coming from slaves.

5

6

3

4

7

1

2

Words

0

Structure x0...x15

x0...x15

x0...x15

x0...x15

x0...x15

x0...x15

x0...x15

x0...x13

x14,x15

Description

New diagnostics for slaves 0 to 15

New diagnostics for slaves 16 to 31

New diagnostics for slaves 32 to 47

New diagnostics for slaves 48 to 63

New diagnostics for slaves 64 to 79

New diagnostics for slaves 80 to 95

New diagnostics for slaves 96 to 111

New diagnostics for slaves 112 to 124

Not used

The bit is reset when the slave has been diagnosed by the SEND_REQ communication function.

All the bits can only be reset once by the SEND_REQ command, the parameter identifying this table and the parameter identifying the reset.

35015381.01 07/2008

79

Software implementation

Compressed diagnostics on all slaves

At a Glance The diagnostics table groups together the main diagnostics for each slave. It always has a size of 125 bytes.

Each byte corresponds to a slave address, byte 0 corresponding to slave 1 and byte 124 corresponding to slave 125.

Each byte shows the same diagnostics information.

Words

0...124

The following table describes the diagnostics information contained in each byte.

Structure

0: NOT_REACHABLE x1: NOT_READY x2: CONFIG_FAULT x3: PRM_REQUIRED x4: INACTIVE x5: INVALID_RSP x6: PARAM_FAULT

Description x0=1 if slave x is not connected or switched off x1=1 if slave x is not ready for data exchanges x2=1 if there is a configuration error on slave x when test requested x3=1 if slave x has to be reconfigured and re-parameterized x4=1 if slave x is inactive (excluded from processing) x5=1 if there is an error in the last response from slave x x6=1 if there is an error in the last parametering message from slave x x7=1 if slave x has already been parameterized by another master module x7: MASTER_LOCK

80

35015381.01 07/2008

Software implementation

Slave diagnostics

At a Glance Only the first six diagnostics bytes are standardized and mandatory.

One slave can provide up to 244 diagnostics bytes. If there is an extended diagnostics (byte 7 is worth ff in hexadecimal), bit x3 of byte 0 indicates this by being at value 1 (x3=1).

Bytes

0

Structure x0: NOT_REACHABLE x1: NOT_READY x2: CONFIG_FAULT

1 x3: EXT_DIAG x4: NOT_SUPPORTED x5: INVALID_RSP x6: PARAM_FAULT x7: MASTER_LOCK x0: PRM_REQUIRED x1: DIAG_DATA_RDY x2: IS_SLAVE_DIAG

2

3

4/5 x3: WDT_ACTIVE x4: FREEZE_MODE x5: SYNC_MODE x6 x7: INACTIVE x0...x6

x7: DIAG_OVERFLOW

MASTER_ADDRESS

PNO_IDENTIFIER

6...244

SPECIFIC_DIAG

Description x0=1 if slave is not connected or switched off x1=1 if slave is not ready for data exchanges x2=1 if there is a slave configuration error when test requested x3=1 if there are extended diagnostics (byte 7 at FFh in hexadecimal) x4=1 if the function is not supported by the slave x5=1 if there is an error in the last response from the slave x6=1 if there is an error in the last parametering message from the slave x7=1 if slave has already been parameterized by another master module x0=1 if slave has to be reconfigured and re-parameterized x1=1 if the slave has generated a diagnostics to be processed by the master x2=0 if the diagnostics has been created by the master x2=1 if the diagnostics has been created by the slave x3=1 if the slave watchdog is active x4=1 if the slave inputs selected are frozen x5=1 if the slave outputs selected are frozen not used x7=1 if slave is inactive (excluded from processing)

Not used x7=1 if the number of diagnostics exceeds the size of the receive words

Address of the master module that sets the parameters for the slave

Identification code for the slave

Optional specific diagnostics data

35015381.01 07/2008

81

Software implementation

General information on a slave

At a Glance For each slave, the following general information can be read by the TSX PBY 100 module using the SEND_REQ function.

Designation

Configured

Operating

Number of %IW

Number of %QW

Size of input data

Size of output data word word byte byte

Size of diagnostics data byte

Compressed diagnostics byte

Diagnostics counter Byte table

Exchange counter

Downtime counter

Size byte byte

Byte table

Byte table

Invalid response counter Byte table

Description the slave has been configured according to Profibus

DPconfiguration the slave has been initialized and is running correctly total size of input data in the %IW zone total size of output data in the %QW zone total size of input data on Profibus total size of output data on Profibus total size of the last received diagnostics compressed diagnostics data for this slave total number of diagnostics messages received from the slaves, one byte per slave (the size is always 126 bytes, byte n corresponds to slave address n) total number of communication faults between the master and his slaves, one byte per slave (the size is always 126 bytes. Byte n corresponds to slave address n) number of times when this slave is present but unavailable (the size is always 125 bytes, byte 0 corresponds to device 1 and byte 124 to device 125) number of invalid responses for this slave (the size is always 125 bytes, byte 0 corresponds to device 1 and byte 124 to device 125)

82

35015381.01 07/2008

Software implementation

Slave configuration data

At a Glance The TSX PBY 100 module can read the configuration data from each slave with the aid of the SEND_REQ function.

Designation

Total length

%IW number

%QW number

Offset %IW

Offset %QW

Station Status

Watchdog Factor 1

Watchdog Factor 2

Min TSDR

PNO_IDENTIFIER

Group Flags

ID Address

Modular slave

Slave active

Size of parameters

Configuration data size

Size of data used

Parameters

Configuration data

Data used byte byte word byte byte byte

Size word byte byte word word byte byte

Description total length of configuration information total input data size in the %IW zone total output data size in the %QW zone input data blocks offset in the %IW zone input data blocks offset in the %QW zone refer to the Profibus DP standard slave address on the bus value = 1 if the slave is a modular device value = 0 if the slave is a compact device byte word word value = 1 if slave is active on the bus value = 0 if slave is inactive on the bus parameter data block size for this slave configuration data block size for this slave word data used block size for this slave x bytes parameter data block for this slave x bytes configuration data block for this slave x bytes block of data used for this slave

35015381.01 07/2008

83

Software implementation

Typical errors

Case 1 ERR flashing

Results

After loading the application, the TSX PBY 100 module’s ERR LED flashes

Causes Actions

The PBY 100 module is not recognized by the processor and has no configuration data z z

Test whether the PL7 configuration corresponds to the actual configuration

Test whether the processor, PL7 and

TSX PBY 100 software versions are compatible

Case 2 ERR lit

Results

After loading the application, the PBY 100 module’s ERR LED is permanently lit

Causes

Profibus cabling problem

Physical problem resulting from the TAP or

PCMCIA card

PCMCIA card software problem

Problem with the loaded configuration

Actions z z

Disconnect the TSX PBY 100 module from the TAP and reinitialize the processor

If the module starts correctly following this action, there is a short circuit or a wire inversion in the cabling z If the module does not start correctly, cut the power supply to the PLC and change the TAP and if necessary the PCMCIA card

(the TAP and the card must be changed when the module is switched off) z Test the software version of the card, it must be V5.02I or above z z

Test the master module error codes and the input/output error codes

Test the error codes via the diagnostics function

84

35015381.01 07/2008

Case 3

Case 4

Case 5

Case 6

35015381.01 07/2008

Software implementation

Line fault

Results

After loading an application, some bus slaves start and become faulty

Causes

A line termination is detected but it is not at the end of the bus

Actions z Test all the Profibus connectors and place the bus termination at the end of the line

Faulty slave

Results

A bus slave is faulty but has not caused a bus error

Causes Actions

The slave has some input/output errors or configuration error or the watchdog is inactive z Test the slave diagnostics data via the debugging screen

Delay in starting up the slave

Results

Bus slaves do not react immediately to start-up without causing a bus error. After a while, the slave starts

Causes

Some slaves require a control command before being activated. These slaves have been too slow to react to the first command sent

Actions z z

Modify the bus parameters to delay the sending of the first command

Add 5 time units to the Timeout

Slaves faulty intermittently

Results

Some slaves are intermittently faulty

Causes

Slaves are subject to cabling faults or errors in electromagnetic compatibility but the

PBY 100 module tries to reactivate them

Actions z z

Reset all the diagnostics counters using the

SEND_REQ function

Test if the TSX PBY 100 module has received the new diagnostics

85

Software implementation

Case 7 Bus hardware fault

Results

The %IWxy.0.243:x7 bit is activated, indicating one or more bus hardware faults and all the devices transmit their diagnostics data

Causes Actions

The bus is subject to cabling faults, connection faults, line termination faults or

TAP faults. Because of this the slaves transmit their diagnostics and fill the receive zone with diagnostics z z z z z z

Check the cabling and line terminations, in particular the connectors whose terminations are activated but not located at the end of the bus

Reset %IWxy.0.243:x7 by: z switching off and then switching on the

PLC, reinitializing the PLC, disconnecting and reconnecting the

TSX PBY 10 module while switched on, downloading a new application, resetting all the diagnostics counters using the SEND_REQ function.

86

35015381.01 07/2008

4.6

Software implementation

Language objects associated with the

TSX PBY 100 module

At a Glance

Subject of this

Section

What's in this

Section?

This section presents the different language objects specific to the TSX PBY 100 module.

This section contains the following topics:

Topic

Language objects in implicit exchange

Language objects for explicit exchange

Explicit exchange management

Language objects associated with the configuration

Error code for module TSX PBY 100

Page

88

92

93

94

95

35015381.01 07/2008

87

Software implementation

Language objects in implicit exchange

At a Glance

Bit objects

All the language objects for implicit exchange (See: PL7 Micro, Junior, Pro;

Communication applications Volume 1) for Profibus-DP communication with the

TSX PBY 100 module can be displayed or modified by the application program.

The table below shows the different bit objects for implicit exchange.

Object (1) Function

%Ixy.MOD.ERR Module error

%Ixy.0.ERR

Channel error

Meaning

Bit set to 1 indicates a module error (at least one of the channels has an error, ...)

Bit set at 1 indicates a channel error

Key

(1) xy address z z x: corresponds to the rack number y: corresponds to the module number

88

35015381.01 07/2008

Input word objects

35015381.01 07/2008

Software implementation

The table below shows the different input word objects for implicit exchange.

Object (1)

%IWxy.0.0

to

%IWxy.0.241

Function

DP inputs

%IWxy.0.242

PBY status

Meaning

242 DP input words

%IWxy.0.243

PBY status z z z z z z x0 = 1: if x8 = 1 or x9 = 1 or x10 = 1, channel error x8 = 1 Master module operating error (DP_ERROR) x9 = 1 PCMCIA card operating error The 9 bit is at state

1 when an error is detected at the 253 word (IOM_error), see at the end of this table x10 = 1 Master module configuration error The 10 bit is at state 1 when an error is detected at the 252 word

(CM_error), see at the end of this table x13 = 1 Configuration error x14 = 1 Communication error: no communication with the programmable controller z z z z z z z z x0..x6: Address of the last diagnosed slave x7 = 1: Hardware fault on the bus (line termination, cabling, connectors, TAP, etc) x8 = 1: Master module operating x9 = 1: Inputs/outputs error (one or more slaves faulty) x10 = 1: New diagnostics available for the master module x11 = 1: New diagnostics available for a slave (address given via x0..x6) x12 = 1: New diagnostics received for several slaves x13..x15: Code of last management event (bus inoperative, communication error between master devices, etc.) z x0..x15: Status bits for slaves 0 to 15 %IWxy.0.244

Diagnostics bitmap

%IWxy.0.245

Diagnostics bitmap

%IWxy.0.246

Diagnostics bitmap

%IWxy.0.247

Diagnostics bitmap

%IWxy.0.248

Diagnostics bitmap

%IWxy.0.249

Diagnostics bitmap

%IWxy.0.250

Diagnostics bitmap z x0..x15: Status bits for slaves 16 to 31 z x0..x15: Status bits for slaves 32 to 47 z x0..x15: Status bits for slaves 48 to 63 z x0..x15: Status bits for slaves 64 to 79 z x0..x15: Status bits for slaves 80 to 95 z x0..x15: Status bits for slaves 96 to 111

89

Software implementation

Object (1)

%IWxy.0.251

Function

Diagnostics bitmap

Meaning z z z x0..x12: Status bits for slaves 112 to 124 x14: Transfer of inputs from the module to the PLC processor x15: Transfer of outputs from the PLC processor to the module

%IWxy.0.252

CM_ERROR code

Master module error code (see Error code for module

TSX PBY 100

, p. 95

)

%IWxy.0.253

IOM_ERROR code

Inputs/outputs error code (see Error code for module

TSX PBY 100

, p. 95

)

Key

(1) xy address z z x: corresponds to the rack number y: corresponds to the module number

90

35015381.01 07/2008

Output word objects

Software implementation

The table below shows the different output word objects for implicit exchange.

Object (1)

%QWxy.0.0

to

%QWxy.0.241

Function

DP outputs

Meaning

242 DP output words

%QWxy.0.242

I/O exchange mode %QWxy.0.242:X0=0: 'Byte consistency' mode

%QWxy.0.242:X0=1: 'Byte consistency' mode

Reserved %QWxy.0.243

to

%QWxy.0.253

Key

(1) z z xy address x: corresponds to the rack number y: corresponds to the module number

The I/O exchange mode is used with version V1.3IE14 (or higher) of the PBY software and requires version 5.8 (or higher) of PL7 CPU.

The application program can select either of these operating modes: z 'Byte consistency' mode (Recommended for discrete I/Os):

%QWxy.0.242:X0=0 == Data is coherent byte by byte with the Profibus frame, but z it does not guarantee that the entire frame is transmitted in the PLC cycle. This mode ensures the best performance.

'Frame consistency' mode (Recommended for analog I/Os):

%QWxy.0.242:X0=1 ==> This guarantees that the entire frame is transmitted in the same PLC cycle. In this case, the overall performance of the system may be reduced.

35015381.01 07/2008

91

Software implementation

Language objects for explicit exchange

At a Glance

Internal words

All the language objects for explicit exchange (See: PL7 Micro, Junior, Pro;

Communication applications Volume 1) for Profibus-DP communication with the

TSX PBY100 module can be displayed or modified by the application program.

The following table describes the internal words:

Object (1) Function

%MWxy.MOD.2 Module status

%MWxy.0.2

Reserved

Meaning z z z z x0 = 1: defective module x1 = 1: functional fault (Communication fault between the CPU and the module, command, adjustment or configuration value not accepted, etc.) x5 = 1: error in hardware or software configuration (the module present is not that declared in the configuration, the sub-modules are not compatible) x6 = 1: missing module

-

Label

(1) z z xy Address x: corresponds to the rack number y: corresponds to the module number

92

35015381.01 07/2008

Software implementation

Explicit exchange management

At a Glance

Word objects

This page describes all the language objects that manage explicit exchanges (See:

PL7 Micro, Junior, Pro; Communication applications Volume 1).

The table below shows the different word objects for managing explicit exchanges.

Object (1) Function

%MWxy.MOD.0 Exchange in progress

%MWxy.MOD.1 Reserved

%MWxy.0.0

%MWxy.0.1

Exchange in progress

Reserved

Meaning z x0 = 1: reading of status in progress

z x15 = 0: reconfiguration in progress

-

Key

(1) z z xy address x: corresponds to the rack number y: corresponds to the module number

35015381.01 07/2008

93

Software implementation

Language objects associated with the configuration

At a Glance

Internal constants

All the configuration language objects for Profibus-DP communication with the

TSX PBY 100 module can be displayed or modified by the application program.

The following table describes the internal constants:

Object (1) Function

%KWxy.0.0

PBY function block

Meaning z x0...x15: PBY 100 function code

%KWxy.0.1

Size of %IW and %QW Number of %IW and %QW updated (32, 64, 128,

242)

%KWxy.0.2

Configuration bits z z x0 = 1: outputs set to zero x0 = 1: maintained outputs

Key

(1) z z xy address x: corresponds to the rack number y: corresponds to the module number

94

35015381.01 07/2008

Software implementation

Error code for module TSX PBY 100

Master module

(%IWxy.0.252)

Managing the internal configuration of module TSX PBY 100

Symbol

E_CFG_DATA_SIZE

E_CFG_IO_IMAGE_SIZE

E_CFG_N_SLAVES

E_CFG_MASTER_ADDRESS

E_CFG_BAUD_RATE

E_CFG_BUS_PARAM

E_CFG_NODE_ID

E_CFG_SLAVE_IN_SIZE

E_CFG_SLAVE_OUT_SIZE

E_CFG_AAT_DATA

E_CFG_AAT_OVERLAP

E_CFG_CNF_TIMEOUT

E_CFG_INIT_FMB

E_CFG_INIT_MASTER

E_CFG_LOAD_BUSPAR

E_CFG_SET_OPMODE

E_CFG_LOAD_SLAVE

E_CFG_MASTER_DIAG

E_CFG_DUP_ADDR

E_CFG_TAP_FAULT

116

117

118

119

120

110

111

112

113

114

115

104

105

106

107

108

109

Value

101

102

103

Description

Size of configuration data block invalid

Size of I/O images invalid

Number of slaves invalid

Address of master module invalid

Transmission speed invalid

Bus parameters invalid

Address invalid or already exists

Slave input data size invalid

Slave output data size invalid

Size/offset combination of I/O data invalid

I/O data overlap

Timeout on confirmation waiting time

Cannot initialize PCMCIA card

Cannot initialize master module

Cannot load module bus parameters

Cannot switch into operating mode

Cannot load slave configuration

Cannot read master module diagnostics

Bus address already exists

Fault between the PCMCIA card and the TAP

35015381.01 07/2008

95

Software implementation

Inputs/outputs

(%IWxy.0.253)

Managing the TSX PBY 100 module inputs/outputs

Symbol

E_OK

E_INIT

E_NO_CONFIG

E_INVALID_CONFIG

E_INVALID_PARAM

E_INVALID_STATE

E_ACCESS

E_NO_RESSOURCES

E_SEND

E_RECEIVE

E_STATE

E_SERVICE

8

9

6

7

10

11

1

2

3

4

5

Value

0

Description

No error

Initialization error

No configuration data

Invalid configuration data

Invalid parameters

Slave state does not allow the request to be carried out

No exchange on BusX

No resources available

Cannot send message to PCMCIA card

Cannot receive message from PCMCIA card

Invalid state

Invalid service code (Uni-telway request and facility)

96

35015381.01 07/2008

Index

A

Address mapping, 43

Addressing, 41

Architecture

General, 11

Multi-master, 13

C

Capacity, 14

Characteristics

Electric, 33

Profibus-DP, 14

CNF, 51

Compatibility, 32

Configuration, 83

Configuration parameters, 50, 51

Configuration screen, 48

Connection, 26

D

Debugging, 59

Description

TSX PBY 100, 22

Diagnostics, 61, 79

Command, 65

Profibus-DP, 64

35015381.01 07/2008

E

ERR, 84

Error code, 95

Errors, 84

Examples

Diagnostics command, 68

Exchange management, 93

F

File, 51

Module configuration, 56

G

General, 9

L

Language objects

Explicit exchange, 92

Implicit exchange, 88

LEDs, 73

M

Modes, 50

N

Network cycle, 17

A C

97

Index

O

Operating conditions, 34

Operating mode, 25

P

Principle, 39

Protocol, 11

R

Report, 70, 93

Response time, 18

S

Set-up, 27

Slave, 61, 84

Diagnostics, 81

Standards, 33

T

Technical specifications

TSX PBY 100, 31

Topology, 11

Transfer capacity, 16

98

35015381.01 07/2008