You are on page 1of 66

PROFIBUS-DP TSX PBY 100 module Contents

Section Page
1 General presentation of PROFIBUS-DP 1/1

1.1 General 1/1

1.2 Glossary 1/2

1.3 System architecture and components 1/3


1.3-1 General architecture and protocol 1/3
1.3-2 Multi-master architecture 1/4
1-3-3 PROFIBUS-FMS 1/4
1.3-4 PROFIBUS-DP characteristics and services 1/5
1.3-5 I/O modules 1/6
1.3-6 PROFIBUS-DP station addressing 1/6

1.4 Operating mode 1/7

1.5 Performance 1/8


1.5-1 Data transfer capacity 1/8
1.5-2 Network cycle 1/8
1.5-3 Application response time 1/10

2 Description of the TSX PBY100 module 2/1

2.1 Description 2/1


2.1-1 General description 2/1
2.1-2 Connection 2/2

2.2 Indicators on the front of the module 2/3

2.3 Compatibility 2/4

___________________________________________________________________________
1
PROFIBUS-DP TSX PBY 100 module Contents

Section Page
2.4 Mounting the module on a rack 2/5

2.5 Standard / Characteristics / Operating conditions 2/7


2.5-1 Standards 2/7
2.5-2 Characteristics 2/7
2.5-3 Operating conditions 2/8

3 Software setup 3/1

3.1 Description 3/1

3.2 Principle 3/2

3.3 Configuration 3/3


3.3-1 Declaration of the TSX PBY 100 module and access to
application-specific screens 3/3
3.3-2 Configuration screen 3/3
3.3-3 Data provided by the user 3/5
3.3-4 Data resulting from decoding the *.CNF text file 3/5
3.3-5 I/O logic addressing 3/8
3.3-6 Configuring a module 3/10

3.4 User interface 3/12


3.4-1 PROFIBUS-DP language objects 3/12
3.4-2 TSX PBY100 module language objects 3/14
3.4-3 TSX PBY100 module error codes 3/15

3.5 PROFIBUS-DP diagnostics 3/17


3.5-1 Diagnostic command 3/18
3.5-2 Diagnostic examples 3/19

___________________________________________________________________________
2
PROFIBUS-DP TSX PBY 100 module Contents

Section Page
3.6 Debugging 3/23
3.6-1 Debug screen 3/24
3.6-2 PROFIBUS-DP module Designation window 3/24
3.6-3 PROFIBUS-DP Diagnostics Window 3/25
3.6-4 Displaying PROFIBUS-DP slave devices 3/26
3.6-5 Icon for accessing SyCon-PB software 3/26
3.6-6 Displaying the master module configuration 3/26
3.6-7 PROFIBUS-DP slave x data 3/27

3.7 Module configuration documentation file 3/28

4 Diagnostics 4/1

4.1 Diagnostics using the module status LEDs 4/1

4.2 Downgraded application modes 4/2


4.2-1 Transmission medium faults 4/2
4.2-2 TSX PBY 100 master module faults 4/2
4.2-3 Slave faults 4/3
4.2-4 PLC CPU general faults 4/3
4.2-5 Resetting the outputs after loading an application 4/3

4.3 Lists of diagnostic variables 4/4


4.3-1 Master diagnostics 4/4
4.3-2 List of the diagnostics available 4/6
4.3-3 Compact diagnostics of all the slaves 4/6
4.3-4 Slave diagnostics 4/7
4.3-5 General information about a slave 4/8
4.3-6 Slave configuration data 4/9

4.4 Typical faults 4/10

5 Index 5/1

___________________________________________________________________________
3
PROFIBUS-DP TSX PBY 100 module Contents

Section Page

___________________________________________________________________________
4
Section 11
General presentation of PROFIBUS-DP
1 General presentation of PROFIBUS-DP
1.1 General
This manual is intended for users who wish to install the TSX PBY100
PROFIBUS-DP master communication module on TSX Premium.
PROFIBUS-DP is a serial link fieldbus for sensors and actuators which conforms to
industrial environment requirements.
It is particularly suitable for rapid data exchange between PLCs and remote devices.
Devices such as I/O modules are available :
• compact Classic TIO slaves :
- "classic" discrete inputs
- "classic" discrete outputs
• DEA203 modular slaves
• Momentum modular slaves :
- discrete inputs
- discrete outputs
- discrete I/O
- analog I/O
Installation of the PROFIBUS-DP bus is described in the PROFIBUS-DP installation
manual, reference 840 USE 468 00.

___________________________________________________________________________
1/1
1.2 Glossary
DP Decentralized Periphery (remote I/O) : PROFIBUS-DP
transmission medium for I/O data transfer
Master class1 Device which initializes, monitors I/O data transfer and
slave diagnostics on the bus. Several active master class1
devices can be installed on the bus and each one controls
its own slaves.
I/O Inputs/Outputs
OF Optional Function : PL7 message function block
PROFIBUS Process Fieldbus
SyCon-PB Hilscher PC software for configuring the PROFIBUS-DP
bus.

___________________________________________________________________________
1/2
General presentation of PROFIBUS-DP 1

1.3 System architecture and components


1.3-1 General architecture and protocol
General architecture of PROFIBUS-DP
The example below shows a PROFIBUS-DP fieldbus architecture using the TSX PBY 100
module and slave devices.
This configuration gives the shortest network cycle time.
TSX Premium
master

4 18 6 66

Slave Slaves Slave Slave

126 slaves max. and 3 repeaters max.

PROFIBUS-DP protocol
The protocol principle is based on a master/slave bus. This principle ensures excellent
response times for I/O exchanges (cyclic exchanges), with a maximum network cycle
time of less than 5 ms at 12 Mbds.
Only master stations, sometimes called active stations, have access rights to the bus.
Slave (or passive) stations can only respond to requests.
Several types of device are standardized :
• master class 1 : in general PLC, robot, numerical control, etc
• master class 2 : device for configuring, programming and diagnosing the master
• slaves

___________________________________________________________________________
1/3
1.3-2 Multi-master architecture
The example below shows a PROFIBUS-DP fieldbus multi-master architecture using
the TSX PBY 100 module and slave devices.

TSX Premium TSX Premium


master 1 master 2

I/O modules I/O modules


(slaves 1, 2 and 3) (slaves 4 and 5)

DP slaves

In a multi-master configuration, each master station is assigned to slaves and forms a


subsystem.

1-3-3 PROFIBUS-FMS
In comparison with PROFIBUS-DP, which is designed for high speed data transfer,
PROFIBUS-FMS is designed for data communication and message handling between
intelligent slaves (ALTIVAR or man-machine interface) and the associated master
devices.
This type of communication is not supported by the TSX PBY 100 module.

___________________________________________________________________________
1/4
General presentation of PROFIBUS-DP 1

1.3-4 PROFIBUS-DP characteristics and services


PROFIBUS-DP is a linear bus designed for high speed data transfer. The PLC
communicates with its peripheral devices via a high speed serial link.
Data exchange is mainly cyclic.
Characteristics of the PROFIBUS-DP bus supported by the TSX PBY100 module

Transmission characteristics
Topology linear bus with line terminators
Communication mode Half Duplex
Transmission rate 9.6 / 19.2 / 93.75 / 187.5 / 500 / 1500 Kbits/s up to 3 / 6 / 12 Mbit/s
Maximum length 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)
500 m at 500 Kbit/s (2000 m 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)
Possible transmission twisted pair line (standard version, RS 485)
media fiber optic link
wave guide
Connector 9-pin Sub-D
Capacity
Number of master stations 0 with TSX 57-10 processors
per PLC 1 with TSX 57-20/25 processors (version V3.0 or later)
2 with TSX/PMX/PCX 57-30/35/40/45 processors (version
V3.0 or later)
Number of slave stations 32 without repeaters
126 maximum with repeaters
Number of I/O 2048 inputs / 2048 outputs maximum
Number of repeaters 3

___________________________________________________________________________
1/5
PROFIBUS-DP services
The TSX PBY 100 module is a master class 1 device and provides the following
services :

Services Request or To or Comments


response from
Data_Exchange request slave I/O data transfer
Slave_Diag request slave slave diagnostics service
Set_Prm request slave parameters sent to slaves on
power-up
Chk_Cfg request slave configuration check on power-up
Global_Control request slave global control of the bus
(automatically undertaken by the
PROFIBUS card)
Get_Master_Diag response master class2 master diagnostics service
(automatically undertaken by the
PROFIBUS card)

1.3-5 I/O modules


I/O modules are used to connect sensors and actuators which check or monitor
machines or processes to the PROFIBUS-DP system.

1.3-6 PROFIBUS-DP station addressing


PROFIBUS-DP stations can be identified by a number from 0 to 124 defining the number
of the station in the architecture (1 to 125).
This address corresponds to the connection point of the station on the bus declared
by the configuration editor.

___________________________________________________________________________
1/6
General presentation of PROFIBUS-DP 1

1.4 Operating mode


General diagram
The following diagram represents the various states of the module :

Module powered
Module stopped down Power
up

Module Communication Module in self-


configured function test phase
effective when the
module is configured

Reset

Configuration Module Self-tests OK


not configured

Configuration :
• PROFIBUS-DP in RUN mode : data exchange on the bus
• task in RUN mode : updating of I/O
• task in STOP mode :
- updating of inputs
- output fallback strategy (maintained or reset to zero)

___________________________________________________________________________
1/7
1.5 Performance
1.5-1 Data transfer capacity
The following table summarizes the size of data which can be sent :

Data Min Max


Image of the inputs in words (%IW) for the configuration - 242 (total)
Image of the outputs in words (%QW) for the configuration - 242 (total)
Maximum size of all the configuration data - 16 Kbytes
Configuration data per slave in bytes 31 250
Diagnostic data per slave in bytes 6 244

Limitations
This module requires slaves with less than 250 bytes of configuration data and less than
244 bytes of diagnostic data.
It can be used to store the configuration data of 125 devices with a maximum total size
of 16 Kbytes.

1.5-2 Network cycle


The network cycle depends on the transfer rate, the number of slaves connected to the
bus and the number of I/O words. The following table gives network cycle times for
several possible configurations :

Configuration Network cycle time (ms)


Transfer rate 12 Mbit/s 5 ms
124 slaves
242 input words and 242 output words
Transfer rate 12 Mbit/s 5 ms
124 slaves
126 input words and 126 output words
Transfer rate 12 Mbit/s 2.4 ms
32 slaves
32 input words and 32 output words

___________________________________________________________________________
1/8
General presentation of PROFIBUS-DP 1

Configuration Network cycle time (ms)


Transfer rate 12 Mbit/s 1 ms
1 slave
1 input word and 1 output word
Transfer rate 500 Kbit/s 100 ms
126 slaves
126 input words and 126 output words
Transfer rate 500 Kbit/s 25 ms
32 slaves
32 input words and 32 output words
Transfer rate 500 Kbit/s 1.8 ms
1 slave
1 input word and 1 output word

___________________________________________________________________________
1/9
1.5-3 Application response time
The application response time is a logical response time which does not take into
account the filtering and response times of the sensor and actuator interfaces.

Example of the time elapsed between the reading of an input and the setting of an output
at a transmission rate of 12 Mbit/s :

Response
I1 Q1 time

I1

MAST scan time : 10 ms

Q1

Maximum updated %IW / QW 32 128 242


MaximumnumberofprocessI/O 1024 4096 7744
Maximum number of 64 124 124
I/O modules
Min. Max. Min. Max. Min. Max.
= 2*Min. = 2*Min. = 2*Min.
Scan time (ms) 2.44 4.8 5 10 11 22
(read image I1)
MAST scan time (ms) 10.00 20.00 10.00 20.00 10.00 20.00
( I1 = Q1 )
PBY scan time (ms) 2.44 4.8 5 10 11 22
(update image Q1)

Application response 14.88 29.6 20 40 32 64


time (ms)

___________________________________________________________________________
1/10
Description of the TSX PBY100Section
module 22
2 Description of the TSX PBY100 module
2.1 Description
2.1-1 General description
The TSX PBY 100 module can be installed on a standard or extendable
TSX PREMIUM rack. The module can operate with the following PLCs :
• TSX 57-20/...
• PMX 57-20/...
• PCX 57-35/...
Communication with PROFIBUS-DP fieldbus devices is possible using :
• a host module (1) comprising :
- an indicator block with 4 LEDs (2)
- a slot for receiving a PCMCIA card (3)
• a PROFIBUS-DP PCMCIA card (4)
• a 0.6 m cable (5) for connection to a TAP
• a PROFIBUS-TAP (6), interface for connecting to the PROFIBUS-DP bus

___________________________________________________________________________
2/1
2.1-2 Connection
1 9-pin female Sub-D connector : RS485
PROFIBUS-DP bus connection.
1 shielding
2 M24 : ground for the 24V output voltage
3 RxD/TxD-P : data transmission positive
(RD+ / TD+)
4 CNTR-P : repeater control signal positive
(direction control) : not used
5 DGND : ground for the data transmission
6 VP : line terminator bias voltage
7 P24 : 24 V output voltage
8 RxD/TxD-N : data transmission negative
(RD- / TD-)
9 CNTR-N : repeater control signal negative
(direction control) : not used
Note :
The RxD/TxD-P, DGND, VP, RxD/TxD-N signals are compulsory. The other signals are optional.

___________________________________________________________________________
2/2
Description of the TSX PBY100 module 2

2.2 Indicators on the front of the module


LEDs indicate the status of the TSX PBY 100 module and the PROFIBUS-DP network.
The indicators conform to PREMIUM and PROFIBUS-DP standards. They are
arranged as follows :

RUN ERR

CH0 I/O

Status O n Flashing Off


LEDs
RUN TSX PBY 100 ready Module not initialized
- self-diagnostic tests (awaiting
green completed configuration)
- PROFIBUS-DP ready
ERR Bus fault Module awaiting No fault indicated
or configuration or loading
red configuration fault in progress (if RUN
or is off)
TSX PBY 100 or
module fault communication fault
with the PLC CPU (if
RUN is lit)
I/O Fault on one or No fault indicated
more slave (all slaves active)
red peripheral devices
CH0 I/O data exchange No I/O data
exchange
yellow

___________________________________________________________________________
2/3
2.3 Compatibility
Hardware
The TSX PBY 100 module requires the use of a PREMIUM PLC version V3.0 onwards :
• TSX 57-20/25 (only one module can be used)
• TSX/PMX/PCX 57-30/35/40/45 (two modules can be used with version V3.3 or later)
The TSX PBY 100 host module is a master class 1 device and can be integrated into
a multi-master configuration. It is compatible with the following communication
methods :
• master-slave
• logical token ring
Software
The TSX PBY 100 module is compatible with SyCon-PB configuration software
V2.5.0.0 and PL7 software from version V3.0 onwards.
Both these programs run under Windows 95 or NT V4.0.

___________________________________________________________________________
2/4
Description of the TSX PBY100 module 2

2.4 Mounting the module on a rack


A module can be inserted and removed while powered up.
To insert/remove a powered-up module, it must be manually screwed and unscrewed
to ensure that the signals on Bus X are connected/disconnected in the correct
sequence. This sequence is not necessarily respected if an electric screwdriver is used.

1 Locate the pins on the


rear of the module in
the centering holes at
the bottom of the rack
1. 2

2 Swivel the module


bringing it into contact
with the rack 2 . 1

3. Fix the module firmly


onto the rack by tight-
ening the screw at the
top of the module 3 .
3

___________________________________________________________________________
2/5
The communication card cannot be inserted or removed while the
reception module is powered up.

4 Insert the card in the


slot provided 4 .

5 Screw in the card to


prevent it from being
handled and to ensure
correct operation 5 . 5

The TAP cannot be connected or disconnected while the reception


module is powered up.

6 Connect the cable to


the TAP 6 .

7 Screw in the connector


to prevent it from being
handled and to ensure
correct connection 7 .

___________________________________________________________________________
2/6
Description of the TSX PBY100 module 2

2.5 Standard / Characteristics / Operating conditions

2.5-1 Standards
The TSX PBY 100 communication module conforms to the following international
standards :
• EC standards : IEC 1131-2 / CENELEC (50081-2).
• US standards : UL508.
• CANADA standards : CSA C22. -142.
The TSX PBY 100 module conforms to the following standards :
• Marine classification :
- Germanischer Lloyd
- Det Norsk Veritas
- Bureau Veritas
- Lloyds register
• US standards : FM, Class 1.Div.II.

2.5-2 Characteristics
• Vdc logic power supply : 5 V DC supplied by the rack power supply
• Current drawn at 5 V : 400 mA

___________________________________________________________________________
2/7
2.5-3 Operating conditions
• Operating temperature/Humidity/Altitude

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


Relative humidity 30% to 95% (without condensation)
Altitude 0 to 2000 meters

• Mechanical withstand
- Immunity to vibrations :
Conforming to standard IEC 68-2-6, Fc test.
- Immunity to shocks :
Conforming to standard IEC 68-2-27, Fc test.
• Electrostatic discharge withstand
- Immunity to electrostatic discharges :
Conforming to standard IEC 1000-4-2, level 3 (1).
• HF interference withstand
- Immunity to radiated electromagnetic fields :
Conforming to standard IEC 1000-4-3, level 3 (1).
- Immunity to bursts of rapid transients :
Conforming to standard IEC 1000-4-4, level 3 (1).
- Immunity to damped oscillatory waves :
Conforming to standard IEC 1000-4-12, level 3 (1).
• LF interference withstand
Conforming to the requirements of standard IEC 1131-2
• TSX PREMIUM PLC protective treatment
TSX Premium PLCs meet the requirements for "TC" treatment (2).
For installations in an industrial production workshop or in an atmosphere
corresponding to "TH" treatment (3), TSX Premium PLCs must be installed in
enclosures with a minimum of IP54 protection as defined by the IEC 664 and NF C
20 040 standards.
Reminder :
TSX Premium PLCs on their own have protection index IP20 (4). They can therefore
be installed without enclosures in restricted access areas which do not exceed
pollution level 2 (control room with neither machines nor dust-producing activity).
(1) Minimum level in the test conditions defined by the standards.
(2) "TC" treatment : all-climates treatment.
(3) "TH" treatment : treatment for warm or humid atmospheres.
(4) When a position is not occupied by a module, a TSX RKA 02 protective cover must be placed
over it.

___________________________________________________________________________
2/8
Description of the TSX PBY100 module 2

• Transport and storage requirements


Conforming to the requirements of IEC 1131-2.

Storage temperature -25°C to +70°C


Relative humidity 5% to 95% (without condensation)

___________________________________________________________________________
2/9
___________________________________________________________________________
2/10
Section
Software 3
setup 3
3 Software setup
3.1 Description
This section describes the various configuration, control and diagnostic possibilities
for a PROFIBUS-DP application.
The PROFIBUS-DP fieldbus and the master and slave devices can only be configured
using the Hilscher SyCon-PB configuration tool supplied by Schneider and its
documentation, reference TLX FBC M.
Any intervention on a module connected to PROFIBUS-DP requires the use of this
software. The user is advised to consult the software documentation.

___________________________________________________________________________
3/1
3.2 Principle
Setting up the TSX PBY 100 module involves :
Configuring the module :
Offline
• selection of the rack number Configuration
(compulsory)
• selection of the position in the rack
• entry of the configuration parameters
• declaration of the configuration using
SyCon-PB and generation of a *.CNF
text file
• importing this file in PL7
Symbolization of variables assigned to
the PROFIBUS-DP module using the Symbolization
variables editor. Offline
or
Programming :
online
• bit objects and words assigned to the
Programming
module or the PROFIBUS-DP link
• module-specific instructions (OFs).
When the program is written in offline
mode, it must be transferred to the PLC so
that it can be debugged. Transfer
and startup
• transfer of the application to the PLC or
a cold restart of the application config-
Online
ures and starts the PROFIBUS-DP mod-
ule.
Various means can be accessed for de-
bugging the application, controlling the Debug
I/O and fault diagnostics : and diagnostics
• language objects on PL7
• debug screen on PL7
• SyCon-PB software
• the front of the TSX PBY 100 module

The documentation editor can be used to


print the parts of the documentation file
relating to the configuration of the Offline
PROFIBUS-DP module. Documentation or
online

___________________________________________________________________________
3/2
Software setup 3

3.3 Configuration
3.3-1 Declaration of the TSX PBY 100 module and access to application-
specific screens
Declaration of the TSX PBY 100 module
To declare a TSX PBY 100 module, consult the PL7 TSX PREMIUM application-
specific documentation.
Access to application-specific screens
Using the mouse, double-click on the TSX PBY 100 graphic module to access the
application-specific screens. The first screen is Configuration.

3.3-2 Configuration screen


This screen, which is shown below, displays various information about the
PROFIBUS-DP configuration :

___________________________________________________________________________
3/3
The configuration screen can be used to display :
• a PROFIBUS-DP Slaves Configuration drop-down list of pre-configured
PROFIBUS-DP slave devices
• a PROFIBUS-DP General Configuration window
• an icon used to run the SyCon-PB software : this can be accessed provided that the
software is installed with the machine offline
• a View button for displaying the configuration of the bus and the master device
• a PROFIBUS-DP Configuration File window, providing access to the configuration
*.CNF text file
• a PROFIBUS-DP Slave Data window
There are two types of data :
• data provided by the user :
- the type of task
- the number of IW/QW
- the output status when the task is in STOP mode
- the number of diagnostic bytes
• data resulting from decoding the *.CNF text file from the configuration software
described in :
- the PROFIBUS-DP slave configuration drop-down list
- the slave x device information block
If the TSX PBY 100 module has never been configured, all fields are empty and the
module operates using the following default values :
• type of task : Mast
• number of IW/QW : 128
• outputs reset when the task is in STOP mode
• number of diagnostic bytes : 32

___________________________________________________________________________
3/4
Software setup 3

3.3-3 Data provided by the user


General Parameter Blocks
In the Task field, select the type of system task which will control the PROFIBUS-DP
fieldbus : MAST or FAST.
In the Outputs field, select the output behavior when the task is in STOP mode :
Maintain or Reset.
In the Nb IW\QW field, select the number of words used for the inputs and outputs : 32,
64, 128, 242.
In the Diagnostic Length field, select the length in bytes of the diagnostics from 6 to
244 bytes (32 by default). The size configured must be sufficient to contain the largest
diagnostics of the bus. If it is too small, the slave concerned will not be active on the
bus because its diagnostics will be invalid.
To optimize performance, select a minimum number of I/O words and diagnostic bytes
which should nevertheless be compatible with the actual bus configuration.

3.3-4 Data resulting from decoding the *.CNF text file


Displaying the PROFIBUS-DP slave configuration
The PROFIBUS-DP Slaves Configuration drop-down list shows the topology of the
PROFIBUS-DP fieldbus configuration. It displays the contents of the selected *.CNF text
file. The user can then access configuration of 125 possible devices. Each line of the
drop-down list displays the state of one device.
A line is shown below :

• the first field shows the slave device address (between 1 and 125)
• the second field shows an ID code (identification number supplied by the manufac-
turer)
• the third field shows if the slave is configured and present on the bus (1 if configured
and present)
• the fourth field shows if the slave is made up of several modules
• the last field shows the state of the watchdog
The number of slaves and the total number of I/O words are shown at the bottom of the
PROFIBUS-DP Configuration list. This data is in decimal format.
___________________________________________________________________________
3/5
PROFIBUS-DP Slave data
Select a device in the PROFIBUS-DP Slaves Configuration drop-down list by clicking
on the corresponding line, to display the I/O addresses and symbols.
It appears in reverse video and a description is provided in the PROFIBUS-DP Slave
data block in the bottom right-hand corner of the configuration screen.

Two drop-down lists can be used to display the I/O addresses and symbols :
• the top list shows the input data relating to the selected device, with its associated
symbol
• the bottom list shows the output data relating to the selected device, with its
associated symbol

___________________________________________________________________________
3/6
Software setup 3

Displaying the PROFIBUS-DP master configuration


The user can display the master and bus configuration parameters by pressing theView
button. This screen is valid when the user has selected a *.CNF text file.
The screen is shown below :

Consult the SyCon-PB software documentation for the definition of various fields.
If no *.CNF text file is selected by the user, a default file appears showing a master
module with no slave.

___________________________________________________________________________
3/7
3.3-5 I/O logic addressing
IW and QW topology

% I or Q X, W or D m • v • i : x

Symbol Type Format m=xy Chan. no. Row Bit


of object X = boolean Rack address v=0 i= x
I = input W = word x = 0 to 7 0 to 253 0 to 15
Q = output D = double word Module position
y = 00 to 10

IW and QW block assignment


DP data is exchanged in the form of I/O blocks. All slave input data is listed by the
adjacent %IW blocks and all slave input data are listed by the adjacent %QW blocks.
Continuity of the %IW and %QW blocks is valid even with a modular slave.
Each slave data block starts with a new %IW or %QW. Consequently, the first slave I/O
word is always associated with a new %IW or %QW.
When the image (%IW or %QW) of the slave has a particular size (example 1 byte or
3 bytes), it is completed by unused bytes in order to handle I/O words.
Example of assignment

Image of inputs
Slave 2 Slave 1 Byte not Slave 17
2 words 1 byte used 1 word

%IWm.0.i %IWm.0.i+1 %IWm.0.j %IWm.0.k


Only bits 0 to 7 are significant

Image of outputs
Slave 17 Slave 2 Byte not
2 words 1 byte used

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


Only bits 0 to 7 are significant

!
SyCon-PB configuration software is required to assign the %IW and
%QW to each slave.

___________________________________________________________________________
3/8
Software setup 3

IW and QW addressing arrangement


One of the main aims of the I/O data arrangement is to make the addressing as clear
as possible.
A slave can be made up of several modules of different data sizes. In this case,
addresses may not be aligned correctly. To avoid this, the user can physically arrange
the modules in the slave rack by :
• grouping input modules of a particular size (example : 1 byte) in pairs
• grouping output modules of a particular size (example : 1 byte) in pairs
• positioning a single input module of a particular size (example : 1 byte) in the last input
module position
• positioning a single output module of a particular size (example : byte) in the last
output module position
Example : slave x with modules not arranged

Module Module Module Module Module Module


A B C D E F
1 input 1 input 1 output 1 input 1 output 1 output
word byte byte word word byte

Image of inputs Image of outputs


%IWm.0.x %IWm.0.x+1 %IWm.0.x+2 %QWm.0.x %QWm.0.x+1
Module Module Module Byte Module Module Module
A B D not C E F
1 input 1 input 1 input used 1 output 1 output 1 output
word byte word byte word byte

The same slave x with modules arranged

Module Module Module Module Module Module


A D B E C F
1 input 1 input 1 input 1 output 1 output 1 output
word word byte word word byte

Image of inputs Image of outputs


%IWm.0.x %IWm.0.x+1 %IWm.0.x+2 %QWm.0.x %QWm.0.x+1
Module Module Module Byte Module Module Module
A D B not E C F
1 input 1 input 1 input used 1 output 1 output 1 output
word word byte word byte byte

___________________________________________________________________________
3/9
3.3-6 Configuring a module
General configuration of PROFIBUS-DP
Before selecting a *.CNF text file, it is necessary to perform the following operations
(default values are shown in bold) :
• the field for the type of task : MAST or FAST
• the state of the outputs when the task is in STOP mode : Maintain or Reset
• the size of words %IW and %QW updated on each PLC scan : 32, 64, 128 or 242
words (128 : default value, 128 for the % IW and 128 for the % QW)
• the byte size for slave diagnostics (the value can vary from 6 to 244, 32 by default)
*.CNF text configuration file
SyCon-PB software is required for configuring :
• the fieldbus topology
• the memory allocation : addressing of each image module in the %IW and %QW
registers
• group definitions
• special functions
• exporting a *.CNF text file
SyCon-PB software can be directly accessed via the icon on the configuration screen.
After configuration, SyCon-PB software generates a *.CNF text file. This file describes
the behavior of the application and all the configuration information to be sent to the
module before starting the PROFIBUS-DP fieldbus.

___________________________________________________________________________
3/10
Software setup 3

This file (or any other existing file) can be retrieved via the configuration screen on PL7
by performing the following operations :
• press the Select file button to select a *.CNF text file : the Open dialog box is
displayed

• select the access path and directory, then the *.CNF text file
• press the Open button to confirm your selection.

The file will be rejected if :


• the file format is incorrect
• there are more than 125 devices

___________________________________________________________________________
3/11
3.4 User interface
This section describes all the language objects which can be displayed or modified by
the application program as well as all the tools used for data exchange.
For all language objects common to communication modules, consult the PL7 Micro /
Junior, TSX Micro / Premium, communication documentation.

3.4-1 PROFIBUS-DP language objects

Objects Function Meaning


%Im.0.ERR I Channel fault Bit set to 1 when there is a channel fault
%IWm.0.0..241 I DP inputs 242 DP input words
%IWm.0.242 I PBY status x0 = 1 If x8=1 or x9=1 or x10=1, channel fault
x8 = 1 Master module operating
fault (DP_error)
x9 = 1 PCMCIA card operating
fault (IOM_error)
x10 = 1 Master module configuration fault
(CM_error)
x13 = 1 Configuration fault
x14 = 1 Communication fault : no
communication with the PLC
%IWm.0.243 I x0..x6 Address of the last diagnosed slave
x7 Hardware fault on the bus (line
terminator, wiring, connections, TAP,
etc)
x8 = 1 Master module operating
x9 = 1 I/O fault (one or more faulty slaves)
x10 = 1 New master module diagnostics
available
x11 = 1 New diagnostics available for one
slave (address given by x0..x6)
x12 = 1 New diagnostics for several slaves
received
x13..x15 Last management event code (bus
offline, communication fault between
master devices, etc)

___________________________________________________________________________
3/12
Software setup 3

Objects Function Meaning


%IWm.0.244 I Bitmap x0..x15 Status bits for slaves 0 to 15
diagnostics
%IWm.0.245 I Bitmap x0..x15 Status bits for slaves 16 to 31
diagnostics
%IWm.0.246 I Bitmap x0..x15 Status bits for slaves 32 to 47
diagnostics
%IWm.0.247 I Bitmap x0..x15 Status bits for slaves 48 to 63
diagnostics
%IWm.0.248 I Bitmap x0..x15 Status bits for slaves 64 to 79
diagnostics
%IWm.0.249 I Bitmap x0..x15 Status bits for slaves 80 to 95
diagnostics
%IWm.0.250 I Bitmap x0..x15 Status bits for slaves 96 to 111
diagnostics
%IWm.0.251 I Bitmap x0..x12 Status bits for slaves 112 to 124
diagnostics x14 Transfer of module inputs to the
PLC CPU
x15 Transfer of PLC CPU outputs to
the module
%IWm.0.252 I CM_error Master module error code
code (consult the error code list)
%IWm.0.253 I IOM_error I/O error code
code (consult the error code list)
I : Implicit exchange (automatic updating at the start of the task for inputs and automatic updating
at the end of the task for outputs)
E : Explicit exchange (updating after execution of a user request).

___________________________________________________________________________
3/13
Objects Function Meaning
%QWm.0.0 to 241 I DP outputs 242 DP output words
%QWm.0.242 to 253 I Reserved
%MWm.0.0 E Exchange x15 = 1 Reconfiguration in progress
in progress
%MWm.0.1 E Reserved
%MWm.0.2 E Reserved
%KWm.0.0 PBY function x0..x15 PBY 100 function code
block
%KWm.0.1 %IW and Number of updated %IW and %QW (32, 64, 128,
%QW size 242)

%KWm.0.2 Configuration x0 = 0 Output set to zero


bits x0 = 1 Output maintained
I : Implicit exchange (automatic updating at the start of the task for inputs and automatic updating
at the end of the task for outputs)
E : Explicit exchange (updating after execution of a user request)

3.4-2 TSX PBY100 module language objects

Objects Function Meaning


%Im.MOD.ERR I Module fault Bit set to 1 when there is a module fault
(at least one faulty channel, etc)
%MW m.MOD.0 E Exchange x0 = 1 Read current status
in progress
%MWm.MOD.1 E Reserved
%MWm.MOD.2 E Module status x0 = 1 Module faulty
x1 = 1 Operating fault (Communication
fault between the CPU and the
module, command, adjustment or
configuration value not accepted, etc)
x5 = 1 Hardware or software configuration
fault (the module present is not the
one declared in the configuration,
the sub-modules are not compatible)
x6 = 1 Module missing
I : Implicit exchange (automatic updating at the start of the task for inputs and automatic updating
at the end of the task for outputs)
E : Explicit exchange (updating after execution of a user request)

___________________________________________________________________________
3/14
Software setup 3

3.4-3 TSX PBY100 module error codes


Master module error codes (%IWm.0.252)
Managing the internal TSX PBY 100 module configuration :
Symbol Value Description
E_CFG_DATA_SIZE 101 Invalid configuration data block size
E_CFG_IO_IMAGE_SIZE 102 Invalid I/O image size
E_CFG_N_SLAVES 103 Invalid number of slaves
E_CFG_MASTER_ADDRESS 104 Invalid master module address
E_CFG_BAUD_RATE 105 Invalid transmission speed
E_CFG_BUS_PARAM 106 Invalid bus parameters
E_CFG_NODE_ID 107 Address invalid or exists already
E_CFG_SLAVE_IN_SIZE 108 Invalid slave input data size
E_CFG_SLAVE_OUT_SIZE 109 Invalid slave output data size
E_CFG_AAT_DATA 110 Invalid I/O data size / offset combination
E_CFG_AAT_OVERLAP 111 I/O data overlap
E_CFG_CNF_TIMEOUT 112 Confirmation waiting time exceeded
E_CFG_INIT_FMB 113 PCMCIA card cannot be initialized
E_CFG_INIT_MASTER 114 Master module cannot be initialized
E_CFG_LOAD_BUSPAR 115 Module bus parameters cannot be loaded
E_CFG_SET_OPMODE 116 Cannot change to operating mode
E_CFG_LOAD_SLAVE 117 Cannot load slave configuration
E_CFG_MASTER_DIAG 118 Cannot read master module diagnostics
E_CFG_DUP_ADDR 119 Bus address already exists
E_CFG_TAP_FAULT 120 Fault between the PCMCIA card and the TAP

___________________________________________________________________________
3/15
I/O error codes (%IWm.0.253)
Managing the internal TSX PBY 100 module I/O :
Symbol Value Description
E_OK 0 No Fault
E_INIT 1 Initialization fault
E_NO_CONFIG 2 No configuration data
E_INVALID_CONFIG 3 Invalid configuration data
E_INVALID_PARAM 4 Invalid parameters
E_INVALID_STATE 5 The slave status does not allow the request to be performed
E_ACCESS 6 No exchange on Bus X
E_NO_RESOURCES 7 No resources available
E_SEND 8 Cannot send a message to the PCMCIA card
E_RECEIVE 9 Cannot receive a message from the PCMCIA card
E_STATE 10 Invalid state
E_SERVICE 11 Invalid service code (Invalid UNI-TELWAY request and
service)

___________________________________________________________________________
3/16
Software setup 3

3.5 PROFIBUS-DP diagnostics


PROFIBUS-DP diagnostic functions are used to quickly locate and identify faults on
devices connected to the bus. Diagnostic messages are exchanged on PROFIBUS-DP
by the TSX PBY 100 master module.
There are four types of diagnostics :
• Master diag : complete diagnostics of the TSX PBY 100 master module
• Slave diag : complete diagnostics of a single slave
• Compressed diag : complete diagnostics of all slaves
• list of diagnostics available for each slave
Each of these diagnostics can be read by PL7 software or by any other PC used for
debugging.

___________________________________________________________________________
3/17
3.5-1 Diagnostic command
A diagnostic command is sent using the SEND_REQ function block.
SEND_REQ( ADR#rm.v, 16#0031, %MWi:3, %MWj:L, %Mwk:4)

r Rack number
m Module number
v Channel number (0 for PROFIBUS-DP)
16#0031 Request code
%MWi:3 Request parameters
%MWi:x0..x8 Type of diagnostics
0..125 Slave x diagnostics
126 List of available diagnostics
127 Compressed diagnostics of all slaves
128 Master module diagnostics
129 Total diagnostics counters
130 Faulty exchange counters
131 Unavailability counters
132 Invalid response counters
%MWi:x9 reserved
%MWi:x10 reserved
%MWi:x11 reserved
%MWi:x12 if activated, reads the configuration data of the slave
selected by %MWi:x0..x8 (=0 to 124)
%MWi:x13 if activated, reads the selected slave data
by %MWi:x0..x8 (=0 to 124)
%MWi:x14 if activated, resetting of the list of available diagnostics
or of the counters specified by %MWi:x0..x8 (=126, 129 to
132)
%MWi:x15 if activated, reading of the list of available diagnostics
or counters specified by %MWi:x0..x8 (=126, 129 to
132) without resetting to zero
%MWi+1 Start address in the diagnostics table (1)
%MWi+2 Length of the diagnostics to be read
%MWj:L PL7 control words where the responses are stored
j Number of the first word
L Number of words
%MWk:4 Four words identifying the PL7 data address used to control the
function
k Exchange status
(1) Default value 0. To gain partial access to the diagnostics table, it is possible to specify a start
word in the table (Start offset).

___________________________________________________________________________
3/18
Software setup 3

The SEND_REQ function must be used to read or reset to zero the various diagnostics
counters.
The TSX PBY 100 module currently provides four diagnostics counters per slave for
troubleshooting. These counters can be accessed via the SEND_REQ function and are
displayed in the form of a table. The size of each counter is 126 bytes of 8 bits each (see
the Diagnostics section).

3.5-2 Diagnostic examples


• Reading the diagnostic words of a slave 2
%M0 OPERATE
p %MW203:=6

OPERATE
(1)

%M0

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

Parameters Variables Values


Address ADR#6.0
Request code 16#0031
Data to send %MW100:3 2 (slave address 2 in decimal format)
0 (address of the diagnostic table in decimal
format)
32 (length of the diagnostic table in decimal
format)
Reception zone %MW104:32
Report %MW200:4

___________________________________________________________________________
3/19
• Master diagnostics
SEND_REQ(ADR#6.0,16#0031,%MW100:3,%MW104:32,%MW200:4)

Parameters Variables Values


Address ADR#6.0
Request code 16#0031
Data to send %MW100:3 126 (master code in decimal format)
0 (address of the diagnostic table in decimal
format
32 (length of the diagnostic table in decimal
format)
Reception zone %MW104:32
Report %MW200:4

• Resetting the diagnostics counter


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

Parameters Variables Values


Address ADR#6.0
Request code 16#0031
Data to send %MW100:3 16#4081(initialization of the total diagnostics
counter in hexadecimal format)
0 (address of the diagnostic table in decimal
format)
32 (length of the diagnostic table in decimal
format)
Reception zone %MW104:32
Report %MW200:4

___________________________________________________________________________
3/20
Software setup 3

Communication / operation report


These messages are common for all types of request.

Communication report (low order byte)


Value Meaning
16#00 Exchange correct
Transaction report (high order byte)
value / error code Meaning
Transmission request code incremented by16#30 Positive result
16#01 Request not processed
16#02 Invalid response
16#03 Reserved
16#01 Exchange stopped on time-out
16#02 Exchange stopped on user request (CANCEL)
16#03 Invalid address format
16#04 Invalid destination address
16#05 Invalid management parameter format
16#06 Invalid specific parameters
16#07 Problem sending to destination
16#08 Reserved
16#09 Reception buffer too small
16#0A Transmission buffer too small
16#0B No processor system resource
16#0C Invalid exchange number
16#0D No telegram received
16#0E Invalid length
16#10 Network module missing
16#0F Telegram service not configured

___________________________________________________________________________
3/21
Communication report (low order byte)
Value Meaning
16#FF Message failed

Operation report (high order byte)


value / error code Meaning

16#01 No resource to the processor

16#02 No line resource

16#03 Device missing

16#04 Line failure

16#05 Length fault

16#06 Faulty communication channel

16#07 Addressing fault

16#08 Application program fault

16#0B No system resource

16#0D Destination missing

16#0F Intra-station routing problem or channel


not configured

16#11 Address format not supported

16#12 No destination resource

16#FD Invalid parameter

___________________________________________________________________________
3/22
Software setup 3

3.6 Debugging
The following screen can be displayed by selecting Debug mode or by double-clicking
on the TSX PBY 100 graphic module in the PL7 configuration in online mode.

___________________________________________________________________________
3/23
3.6-1 Debug screen
The debug screen displays the following information :
• a Designation : PROFIBUS-DP module window
• a PROFIBUS-DP Diagnostic Data window
• a PROFIBUS-DP Slaves Configuration drop-down list
• an icon for accessing SyCon-PB software
• a View button
• a PROFIBUS-DP Slave Data window.

3.6-2 PROFIBUS-DP module Designation window

1 2 3 4

1 Title bar. This shows the product reference and position of the module

2 Function selection : Debug (available in online mode only) or Configuration

3 This field displays the state of the LEDs on the front of the communication
module

4 When a module fault is detected, this DIAGNOSTICS button is used to access


information on the status of the module.

___________________________________________________________________________
3/24
Software setup 3

3.6-3 PROFIBUS-DP Diagnostics Window


This window displays all the diagnostic data for a device. By selecting a device in the
PROFIBUS-DP Slaves Configuration list, its diagnostic data appears in the PROFIBUS-
DP Diagnostic Data window.

The data displayed corresponds to a new diagnostic item. When a device is selected
from the list, the module in question is automatically diagnosed.
In all diagnostics, the first six bytes are standardized and displayed. If a slave requires
more than six diagnostic bytes, the data is displayed in the window and can be accessed
using the scroll bars.

___________________________________________________________________________
3/25
3.6-4 Displaying PROFIBUS-DP slave devices
When a device is faulty, its corresponding line in the PROFIBUS-DP Configuration
drop-down list is shown in red.

3.6-5 Icon for accessing SyCon-PB software


If the SyCon-PB tool is installed on the station, the user can run the software by clicking
on the following icon :

Note :
The TSX PBY 100 V1.0 module can only be configured using the SyCon-PB tool.

3.6-6 Displaying the master module configuration


As in configuration mode, information on the master module can be displayed by
pressing the View button.

___________________________________________________________________________
3/26
Software setup 3

3.6-7 PROFIBUS-DP slave x data


x represents the number of the device ranging from 1 to 125.
To display the I/O data values of a device, select PROFIBUS-DP Slaves Configuration
in the drop-down list by clicking on the corresponding line.

Two drop-down lists show the I/O data values :


• The top field displays the list of input data relating to the selected device,
with the associated symbol and value for each data item.
• The bottom field displays the list of output data relating to the selected device,
with the associated symbol and value for each data item.
• The intermediate field is used to enter the value of a %QW data and to specify the
type of display for each data item :
- hexadecimal
- decimal
- ASCII

Forcing is not allowed on IW and QW language objects.

When the PLC changes to STOP mode, the module fallback values are displayed in
red.

___________________________________________________________________________
3/27
3.7 Module configuration documentation file
A documentation file describing the application configuration for the TSX IBY100
module is available in the PL7 documentation editor. It is presented in the following
format :

TSX PBY 100[RACK 0 POSITION 4]


Module Identification :

Commercial Ref. : TSX PBY 100 Designation : PROFIBUS-DP MODULE


Address : 006 Symbol :

Channel parameters : 0

Task : MAST Outputs : Reset


No. of IW/QW : Words Diagnostic Length : 32 Bytes

PROFIBUS-DP configuration file : E:\CNF\L21CIE67.CNF

PROFIBUS-DP master configuration :


Station address : 1 No. of slaves : 2
Baudrate : 12Mbits/s
Slot time : 1000 tBit Quiet time : 9 tBit
Min St Delay Resp : 11 tBit Max St Delay Resp : 800 tBit
Setup time : 16 tBit Token Rot. time : 6459 tBit
Gap update factor : 10 Retry limit : 4
Highest st. addr : 1 Min slave interval : 1*1000µs
Poll timeout : 10 ms Data control time : 120*10 ms

PROFIBUS-DP slave configuration :


Address Slave_ID Active / Group_ID / Wch dog
2 0x1354 1/0/1
3 0x2354 1/0/1

PROFIBUS-DP slave language objects :


Address IW/QW Symbol
2 %IW6.0
%IW6.0.1

3 %QW6.0
%QW6.0.1

___________________________________________________________________________
3/28
Section 44
Diagnostics
4 Diagnostics
4.1 Diagnostics using the module status LEDs
The diagnostic LEDs are as follows :

RUN ERR

CH0 I/O

Status O n Flashing Off


LEDs
RUN TSX PBY 100 ready Module not initialized
- self-diagnostic tests (awaiting
green completed configuration)
- PROFIBUS-DP ready
ERR Bus fault Module awaiting No fault indicated
or configuration or
configuration fault loading in progress
red or (if RUN is off)
TSX PBY 100 module or
fault communication fault
with the PLC CPU (if
RUN is lit)
I/O Fault on one or No fault indicated
more slave (all slaves active)
red peripheral devices
CH0 I/O data exchange No I/O data
exchange
yellow

___________________________________________________________________________
4/1
4.2 Downgraded application modes
4.2-1 Transmission medium faults
Communication fault when launching PROFIBUS-DP
This fault may be due to incorrect configuration or a faulty cable. In this case, the bus
remains in a non operational state and the slaves remain in a startup error state.
An error code is generated by the TSX PBY 100 master module as a diagnostic item.
All the slave diagnostic bits remain in their error state. The ERR LED is lit, and the other
LEDs are not.
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 as a diagnostic item. In this case, the slaves change to their
preconfigured error state after the watchdog time has elapsed.
The slave diagnostic bits are enabled to indicate the unavailability of slaves and
resetting of the inputs. The TSX PBY 100 module records the diagnostics and informs
the CPU of their availability via %IWMm.0.129:x10..x12.

4.2-2 TSX PBY 100 master module faults


When a fault is detected, exchanges of data, commands and diagnostics are inter-
rupted. After the watchdog time has elapsed, an error code is generated as a diagnostic
item.
If the exchanges are interrupted, the slave diagnostic bits are enabled to indicate the
unavailability of slaves and resetting of the inputs. The ERR LED is lit, and the other
LEDs are not.

___________________________________________________________________________
4/2
Diagnostics 4

4.2-3 Slave faults


When the exchanges are in progress, a slave fault is indicated by a new diagnostic item.
If communication is still established, the slave generates the diagnostic item, otherwise
it is generated by the TSX PBY 100 master module.
The slave diagnostic bits are enabled to indicate its unavailability and resetting of its
inputs. The TSX PBY 100 module records the diagnostics and informs the CPU of their
availability via %IWMm.0.129:x10..x12.
If one or more slaves are faulty, the bus cycle slows down. Acknowledg-
ment of a diagnostic item and resetting the inputs may require several
PLC scans.

4.2-4 PLC CPU general faults


In the event of a communication fault between the CPU and the TSX PBY 100 module,
all the outputs are set to their error state (maintain or fallback) and the inputs are reset.
The ERR LED flashes to indicate the communication fault between the PLC CPU and
the TSX PBY 100 module.
Diagnostic data transfers between master and slave are not affected.

4.2-5 Resetting the outputs after loading an application


For slow speeds (less than 500 Kbit/s) and a long watchdog time, the slaves will
maintain the states of the outputs throughout the duration of the watchdog.
For slow speeds (less than 500Kbit/s) and a deactivated watchdog, the states of the
slave outputs will be maintained until the application has finished loading.

___________________________________________________________________________
4/3
4.3 Lists of diagnostic variables
4.3-1 Master diagnostics
The following table gives the diagnostic data of the TSX PBY 100 master module :

Bytes Structure Description


0/1 Operating_mode Operating mode of the master (byte 0 : low order byte;
byte 1 : high order byte)
Values :
00h offline (initialization)
40h stop (ready to receive the configuration)
80h output fallback (outputs reset to zero, clear)
C0h operating
2/3 PNO_identifier Master identification code according to the PROFIBUS code
(byte 2 : low order byte; byte 3 : high order byte)
Value :
1654h for the TSX PBY 100 module
4 PC card PCMCIA card hardware version according to the PROFIBUS code
hardware version Values :
10h version V1.0
XYh version VX.Y
FFh no card or card invalid
5 PC card PCMCIA card software version according to the PROFIBUS code
firmware version Values :
10h version V5.02E
11h version V5.02F
XYh version V5.XY
FFh no card or card invalid
6 PBY Hardware version of the TSX PBY 100 module
hardware version Values :
10h version V1.0
XYh version VX.Y
7 PBY Software version of the TSX PBY 100 module
firmware version Values :
10h version V1.0
XYh version VX.Y
8 PBY IE Software upgrade index of the TSX PBY 100 module
version Values :
04h version UI 04
XYh version UI XY
9..15 PC card firmware Software version of the PCMCIA card in ASCII mode
version (ASCII)

___________________________________________________________________________
4/4
Diagnostics 4

For PROFIBUS-DP, a Master Class 2 device will have the following standard diagnostic
data for the TSX PBY 100 module :

Bytes Structure Description


0 Operating_mode Operating mode of the master
Values :
00h offline (initialization)
40h stop (ready to receive the configuration)
80h output fallback (outputs reset to zero, clear)
C0h operating
1/2 PNO_identifier Master identification code according to the PROFIBUS code
(byte 1 : high order byte; byte 2 : low order byte)
Value :
1654h for the TSX PBY 100 module
3 PC card PCMCIA card software version according to the PROFIBUS
hardware version code
Values :
10h version V1.0
XYh version VX.Y
FFh no card or card invalid
4 PC card PCMCIA card software version according to the PROFIBUS
firmware version code
Values :
10h version V5.02E
11h version V5.02F
XYh version V5.XY
FFh no card or card invalid
5 PBY Hardware version of the TSX PBY 100 module
hardware version Values :
10h version V1.0
XYh version VX.Y

6 PBY Software version of the TSX PBY 100 module


firmware version Values :
10h version V1.0
XYh version VX.Y

Note :

The high and low order diagnostic bytes of the PNO_Identifier are inverted in
relation to the standard diagnostics on PROFIBUS-DP.

___________________________________________________________________________
4/5
4.3-2 List of the diagnostics available
This table provides the activity bits. There is one bit per slave. These bits provide
information about the availability of new diagnostics from the slaves.

Bytes Structure Description


0 x0...x15 new diagnostics concerning slaves 0 to 15
1 x0...x15 new diagnostics concerning slaves 16 to 31
2 x0...x15 new diagnostics concerning slaves 32 to 47
3 x0...x15 new diagnostics concerning slaves 48 to 63
4 x0...x15 new diagnostics concerning slaves 64 to 79
5 x0...x15 new diagnostics concerning slaves 80 to 95
6 x0...x15 new diagnostics concerning slaves 96 to 111
7 x0...x13 new diagnostics concerning slaves 112 to 124
x14,x15 not used

Bit x is reset to zero when slave x has been diagnosed by the SEND_REQ
communication function.
All the bits can be reset to zero simultaneously by the SEND_REQ command, the
parameter which identifies this table and the parameter which identifies the reset.

4.3-3 Compact diagnostics of all the slaves


This table shows the main diagnostics for each slave. The size of this table is always
125 bytes, with byte 0 corresponding to slave 1 and byte 124 corresponding to slave
125.
Each byte corresponds to a slave address and shows the same diagnostic information.

Bytes Structure Description


0..125 x0 : not_reachable x0=1 if slave x is not connected or off
x1 : not_ready x1=1 if slave x is not ready for data exchange
x2 : config_fault x2=1 if configuration fault on slave x when the test is
requested
x3 : prm_required x3=1 if slave x needs to be reconfigured and the
parameters reset
x4 : inactive x4=1 if slave x is inactive (excluded from processing)
x5 : invalid_rsp x5=1 if there is a fault in the last slave x response
x6 : param_fault x6=1 if there is a fault in the last slave x parameter message
x7 : master_lock x7=1 if the slave x parameters have already been set by
another master module

___________________________________________________________________________
4/6
Diagnostics 4

4.3-4 Slave diagnostics


Only the first six diagnostic bytes are standardized and compulsory.
A slave can supply up to 244 diagnostic bytes. For extended diagnostics (byte 7 equals
ff in hexadecimal format), bit x3 of byte 0 is at value 1 (x3=1) to indicate the extended
diagnostics.

Bytes Structure Description


0 x0 : not_reachable x0=1 if the slave is not connected or off
x1 : not_ready x1=1 if the slave is not ready for data exchange
x2 : config_fault x2=1 if slave configuration fault when the test is requested
x3 : ext_diag x3=1 if extended diagnostics (byte 7 at ff in hexadecimal format)
x4 : not_suppported x4=1 if the function is not supported by the slave
x5 : invalid_rsp x5=1 if there is a fault in the last slave response
x6 : param_fault x6=1 if there is a fault in the last slave parameter message
x7 : master_lock x7=1 if the slave parameters have already been set by another
master module
1 x0 : prm_required x0=1 if the slave needs to be reconfigured and the
parameters reset
x1 : diag_data_rdy x1=1 if slave has generated a diagnostic item to be
processed by the master
x2 : is_slave_diag x2=0 if the diagnostics have been created by the master
x2=1 if the diagnostics have been created by the slave
x3 : wdt-active x3=1 if the slave watchdog is active
x4 : freeze_mode x4=1 if the inputs of the selected slave are frozen
x5 : sync_mode x5=1 if the outputs of the selected slave are frozen
x6 not used
x7 : inactive x7=1 if the slave is inactive (excluded from processing)
2 x0.. x6 not used
x7 : diag_overflow x7=1 if the number of diagnostics is greater than the size
of the reception words
3 master_address Address of the master module which sets the slave parameters
4/5 PNO_identifier Slave identification code
6..244 specific_diag Optional specific diagnostic data

___________________________________________________________________________
4/7
4.3-5 General information about a slave
The following general information about each slave can be read by the TSX PBY 100
module using the SEND_REQ function :

Designation Size Description


Configured byte the slave has been configured in the PROFIBUS
configuration
Operating byte the slave has been initialized and is operating
correctly
Number of %IW word total size of the input data in the %IW zone
Number of %QW word total size of the output data in the %QW zone
Size of input data byte total size of the input data on PROFIBUS
Size of output data byte total size of the output data on PROFIBUS
Size of diagnostic data byte total size of the last diagnostics data item received
Compact diagnostics byte compact diagnostic data for that slave
Total diagnostics counter byte total number of diagnostic messages received from
table that slave (the size is always 125 bytes, byte 0
corresponds to device 1 and byte 124 to device 125)
Faulty exchange counter byte number of faulty exchanges between the master and
table that slave (the size is always 125 bytes, byte 0
corresponds to device 1 and byte 124 to device 125)
Unavailability counter byte number of times that slave has been present but not
table available (the size is always 125 bytes, byte 0
corresponds to device 1 and byte 124 to device 125)
Invalid response counter byte number of invalid responses for that slave
table (the size is always 125 bytes, byte 0 corresponds to
device 1 and byte 124 to device 125)

___________________________________________________________________________
4/8
Diagnostics 4

4.3-6 Slave configuration data


The TSX PBY 100 module can read the configuration data of each slave using the
SEND_REQ function :

Designation Size Description


Total length word total length of the configuration data
Number of %IW byte total size of the input data in the %IW zone
Number of %QW byte total size of the output data in the %QW zone
%IW offset word offset of the input data blocks in the %IW zone
%QW offset word offset of the output data blocks in the %QW zone
Station Status byte refer to the PROFIBUS-DP standard
Watchdog Factor 1 byte refer to the PROFIBUS-DP standard
Watchdog Factor 2 byte refer to the PROFIBUS-DP standard
Min TSDR byte refer to the PROFIBUS-DP standard
PNO_Identifier word refer to the PROFIBUS-DP standard
Group Flags byte refer to the PROFIBUS-DP standard
ID address byte address of the slave on the bus
Modular slave byte value = 1 if the slave is a modular device
value = 0 if the slave is a compact device
Active slave byte value = 1 if the slave is active on the bus
value = 0 if the slave is inactive on the bus
Parameter size word size of the parameters data block for that slave
Size of configuration data word size of the configuration data block for that slave
Size of data used word size of the data block used for that slave
Parameters x bytes parameters data block for that slave
Configuration data x bytes configuration data block for that slave
Data used x bytes data block used for that slave

___________________________________________________________________________
4/9
4.4 Typical faults
Situation 1 : ERR flashing

Effects
After loading the application, the ERR LED on the PBY 100 module flashes.
Causes Actions
The PBY 100 module is not recognized by • Test that the configuration in PL7 is
the processors and has no configuration consistent with the actual configuration.
data • Test that the software versions of the
processor, PL7 and PBY 100 are compatible.

Situation 2 : ERR on

Effects
After loading the application, the ERR LED on the PBY 100 module is on continuously.
Causes Actions
PROFIBUS wiring problem • Disconnect the PBY 100 module from the
TAP and reinitialize the processor
• If the module starts correctly following this
operation, there is a short-circuit or a
reversal of the wires in the wiring.
Physical problem originating in the TAP or the • If the module does not start correctly,
PCMCIA card switch off the PLC power supply and
change the TAP and, if necessary, the
PCMCIA card (the module
must be powered off when the TAP and
the card are changed)
PCMCIA card software problem • Test the software version of the card. The
` version must be V5.021 or later
Problem with the configuration which has • Test the error codes of the master module
been loaded and the I/O error codes
•Test the error codes using the
diagnostics function

Situation 3 : Line fault

Effects
After loading the application, some of the slaves on the bus start and change to fault mode
Causes Actions
A line terminator is detected but • Test all the PROFIBUS connectors and
not located at the end of the bus place the bus terminator at the end of the line

___________________________________________________________________________
4/10
Diagnostics 4

Situation 4 : Slave faulty

Effects
A slave on the bus is faulty without causing a bus fault.
Causes Actions
The slave has a number of I/O faults or • Test the slave diagnostic data via
a configuration fault, or the watchdog is the debug screen
inactive

Situation 5 : Delayed start-up of a slave

Effects
A number of slaves on the bus do not react immediately on start-up without causing a bus
fault. After some time the slaves start.
Causes Actions
Some slaves require a control command • Modify the bus parameters to delay
before being activated. These slaves have transmission of the first command
been too slow to react to the first command • Add 5 time units to the Time-out
which was sent.

Situation 6 : Slaves intermittently faulty

Effects
Some slaves are intermittently faulty.
Causes Actions
The slaves are subject to wiring or • Reset all the diagnostics counters to zero
using the SEND_REQ function electromagnetic compatibility faults
but the PBY 100 module tries to • Test whether the new diagnostics have
reactivate them been received by the PBY 100 module.

___________________________________________________________________________
4/11
Situation 7 : Hardware fault on the bus

Effects
Bit %IWm.0.243:x7 is activated indicating one or more hardware faults on the bus and all
the devices are sending their diagnostic data.
Causes Actions
The bus wiring, connections, line terminators • Check the wiring and line terminators,
or TAPs are faulty. especially the connections whose
As a result, the slaves send their diagnostics terminators are activated but are not
and saturate the diagnostics reception zone. located at the end of the bus.
• Reset %IWm.0.243:x7 by
- switching the PLC off and then on again
- resetting the PLC
- disconnecting and reconnecting the
TSX PBY 100 module while it is powered
up
- downloading a new application
- resetting the diagnostics counters to
zero using the SEND_REQ function.

___________________________________________________________________________
4/12
Section
Index 5
5 Index

A
Addressing 1/6, 3/8 M
Architecture 1/3, 1/4
Master class1 1/2
C Mounting 2/5

CH0 2/3, 4/1 N


Characteristics 1/5, 2/7
CNF 3/10 Network cycle 1/8
Command 3/18
Compatibility 2/4
O
Configuration 3/3, 3/5, 3/7, 3/10, 4/9 Operating conditions 2/8
Connection 2/2
P
D
Performance 1/8
Debugging 3/23 Principle 3/2
Diagnostics 3/17, 3/25, 4/4, 4/6 PROFIBUS 1/2
Documentation file 3/28 PROFIBUS-DP 1/3
DP 1/2 PROFIBUS-FM 1/4
Protocol 1/3
E
ERR 2/3, 4/1, 4/10
R
Error codes 3/15 Report 3/21
Examples 3/19 Response time 1/10
RUN 2/3, 4/1
F
Faults 4/10
S
File 3/10 SEND_REQ 3/18
Services 1/6
G Slave 1/1, 3/6, 3/27, 4/3, 4/7, 4/8, 4/11
General 1/1 Standards 2/7
SyCon-PB 1/2, 3/26
I
T
I/O 2/3
Indicator lamps 2/3 Transfer capacity 1/8

L
Language objects 3/12, 3/14
LEDs 4/1

___________________________________________________________________________
5/1
___________________________________________________________________________
5/2