PROFIBUS Guideline - Order No. 2.032: Test Specifications For Profibus - DP Slaves

®
PROCESS FIELD BUS
Draft
Technical Guideline
Test Specifications for

PROFIBUS – DP Slaves
Version 2.1
December 2002
PROFIBUS Guideline – Order No. 2.032

PROFIBUS Guideline, Order No. 2.032
Draft Technical Guideline

Test Specifications for PROFIBUS - DP Slaves
Version 2.1
December 2002
Prepared by the PROFIBUS WG 3: „PROFIBUS DP Slave

Certification“, in the TC 1: „Test and Certification“.
Publisher:
PROFIBUS Nutzerorganisation e.V.
Haid-und-Neu-Str. 7
D-76131 Karlsruhe
Phone:++49 721 / 96 58 590

Fax: ++49 721 / 96 58 589
pi@profibus.com
www.profibus.com
No part of this publication may be reproduced or uitilized in

any form or by any means, electronic or mechanical,
including photocopying and microfilm, without permission in
writing from the publisher.
Draft Technical Guideline: Test Specifications for PROFIBUS-DP Slaves, Version 2.1, December 2002
Contents
A - CERTIFICATION TO VERIFY PROFIBUS FUNCTIONALITY 3
1. Certification Application 3
2. Hints for a quicker test 3
3. Responsibility of the test laboratory 5
4. How to get a certificate 6
B - TEST OF DP STANDARD FUNCTIONS 7
1. Hardware Testing 7
a. Line terminators according to IEC 61158-2 8
b. Compatibility of the bus interface according to IEC 61158-2 8
c. RS 485 circuitry 9
d. Impedance and reflection 9
2. Bus Transmission (Slave Functionality) 10

a. Control interval monitoring according to IEC 61158-5 10
b. TSDR according to IEC 61158-3 10
c. Addressing 10
d. Manufacturer identifier according to IEC 61158-5 10
e. Transmission speeds 10
f. Operation in mixed networks 10
g. Combined (mixed) devices as FMS and DP slave 11
h. Consistency 11
i. Min_Slave_Intervall 11
j. GSD file check 11
k. Data format 11
3. Function Testing 12
a. Bus interruption at the test item (bus disconnected) 12
b. Power supply voltage at test item off/on 12
c. Network / power supply turned off at master 12
d. Network / power supply turned on at master 12
e. Master parameterization (with and without control interval monitoring) 12
f. Master (class 2) takes control during operation 12
g. State transitions 13
i. Optional features 16
j. Evaluation of the diagnostic function 16
k. Behavior of a slave to special failures 17
l. Test of modular devices 17
4. Interoperability 18
a. Load Test 18
b. Functional Test 18
c. Electromagnetic Compatibility 20
© PNO 2002, Copyright - all rights reserved Page 1

C - TEST OF DP-V1 FUNCTIONS (EXTENSIONS TO PART B) 21
1. Function Testing 21
a. MS1 services 21
b. MS2 services 23
2. Interoperability and Timing 24

a. Additional timing features 24
b. Additional interoperability test 24
APPENDIX: TEST REPORT 25
APPENDIX: EXAMPLE OF AN EMC TEST REPORT 31

A - Certification to verify PROFIBUS functionality
1. Certification Application
The certification application is submitted in writing by the applicant to one of the PROFIBUS
test laboratories. To get the latest information please contact your local PROFIBUS User
Organization or look at http://www.profibus.com/support.html to get the latest information.
The application must include the following:
1. Name and address of the applicant.

2. The technical documentation, including:
− a general description of the device’s structure.
− descriptions and explanations necessary for understanding how the device works.
− manufacturer’s declaration stating that the device conforms to the safety and EMC
requirements for its area of use (e.g.: VDE 0160, IEC 80x, EN50082-2).
− the device data base file (GSD) according to "GSD-Specification for PROFIBUS-DP"
(The device data base file has to be according to GSD Revision 2 or higher according
to the device capabilities),
− a copy of the confirmation of the "Registration of a PROFIBUS Device" issued by the
PROFIBUS User Organization, stating the model name, release and Ident Number,
− the hardware, software and firmware versions,
− circuit diagram of the RS485 bus interface.
The application will be stamped with the date of arrival and will be processed within two
weeks of this date. After the application is processed, the applicant will receive written
approval of a test date, as well as an indication of how long the test will last. From the
beginning of the application process to the test date, a maximum waiting time of 8 weeks is
possible. On the approved test date, the applicant, hereafter referred to as the customer, has
to make available the representative end product for planned production, hereafter referred to
as the test item, free of cost to the test laboratory. The test item must be representative of the
production series and the test shall be possible without modifying hardware or software.
After passing the tests, the test item will be integrated into the test system in the test
laboratory to show test reproducibility. The test item will be operated according to its regular
use. The test laboratory will make sure that the test item is inaccessible to all unauthorized
personnel.
2. Hints for a quicker test

To minimize the expense of clearing at the test of a slave, additional information is
necessary. The customer should supply the following information and necessary equipment
for testing the device.
If the slave uses ext_diag and/or stat_diag:
How can the ext_diag be set?
What is the meaning of the bytes and/or bits of the device specific diagnostic?
Addressing of the slave:
The address range of the slave has to be written in the manual. It is also necessary to
describe how the address is set.
If a special software tool is necessary for addressing the slave, that software has to be
delivered on a 3,5“ disc or on a CD-ROM. It has to work on MS-DOS or Windows 95/NT.

If the device uses special cables (e.g. RS232/RS485) or hardware, this has to be
delivered, too.
If the slave uses the service Set_Slave_Address, make sure that after setting the bit
“No_Add_Chg“ = True (which will be made when tested) the device can be reset to the
original state. It has to be described how that can be made. The necessary tools are to
be delivered.
Baudrate:
If the slave does not support automatic selection of the baudrate (Auto_Baud), the
selection of the baudrate has to be described. If a special software tool is necessary for
setting the baudrate of the slave, that software has to be delivered on a 3,5“ disc or on a
CD-ROM. It has to work on MS-DOS or Windows 95/NT.
If the device uses special cables (e.g. RS232/RS485) or hardware, this has to be
delivered, too.
Input and output data:
The input data of the device will be changed if possible. When not using physical inputs -
as used in I/O devices for example - a description of how to change the inputs is
necessary.
If the device uses special connectors, the used connectors with the wiring diagram or
pre-manufactured cables are to be delivered.
User applications:
If using a special profile for controlling the device, all data for controlling the device are to
be described. It is not sufficient to deliver only function blocks for a PLC.
Bus connector:
If the bus cable is not connected by the standard 9 pin D-Sub connector or by terminal
block, the used connectors with the wiring diagram or premanufactured cables are to be
delivered.
Modular devices:
If the slave is a hardwaremodular device, the customer has to provide all modules which
are requested by the testlab.

3. Responsibility of the test laboratory

The test laboratory
− Will execute the appropriate tests to determine whether the test item conforms with
PROFIBUS specifications, especially concerning its functional behaviour.
− Will write up a test report with the name and address of the applicant, test results, any
conditions for the test validity and necessary input for definite identification of the test item.
Important technical documentation will be attached to the report as an appendix.
− The test results and documents are to be available to the applicant and the test laboratory.
− The test laboratory is obligated to keep all test results and documents confidential.
− The documents received from the applicant and the test report will be kept in a separate
lockable cabinet for 4 years. Only test laboratory personnel have access to this cabinet.
− The test laboratory will make sure that the test procedure complies with the specifications
given by the PROFIBUS User Organization.
− The test laboratory will commit itself to adapting the test procedure to the demands, if
needed, after consulting the PROFIBUS User Organization.
− If a certified product demonstrates faulty behaviour in a system and this is proved in the
test laboratory, the certificate is cancelled immediately.

4. How to get a certificate
Procedure to obtain a
PROFIBUS certificate
Customer develops a field device

and creates a GSD file
Customer orders an identnumber from the PNO

and also applies for a certification
test at any test laboratory
Test of the field-

device in the test
laboratory
no
Test passed ?
yes
Customer
applies for a
certificate via PNO

B - Test of DP Standard Functions

The scope of the test includes a hardware test (Part 1), a bus transmission test
(Part 2), a function test (Part 3) and an interoperability test (Part 4).
1. Hardware Testing
Necessary Documentation
A circuit diagram of the bus interface is necessary, i.e. from ASIC or processor (for software
solutions) to the bus connector.
The customer has to supply the corresponding electrical diagrams in a legible form with a
clear identification of the product to be tested. The documents will be labelled with the date, a
test stamp and will then be archived. The documents will be kept confidential.
Sample circuit diagram:
Bus Interface
HCPL0601
300R 74HC132
RTS 300R
M &
EN
680R
300R
300R
M
CTS
680R
2P5
HCPL7101/7721/0721
2P5
P5 U+ OUT
680R 2P5
100K
IN EN 68n LSI ALS176D
TXD 68n
8
U- 2M 1K2 3
U+ 1
68n 2M 5
EN1
M U- U+ 2
B-line
20K
GND
EN2 3
2P5 RTS
P5 680R 4
2M
1K2
68n 1
68n 5
U+ U+ 1 2P5
IN 6
M U- 2
A-line
7
EN
680R 8
U- 2M
RXD
100K
OUT Driver select: Differential voltage > 2V 9

HCPL7101/7721/0721
Important: electrical isolation to bus 2M
2.2 .. 22nF 1M
500 V P5 and 2P5
Layout: lines must be kept as short as possible. Shield
Note: This is only a sample circuit diagram. For detailed specification of the interface see IEC
61158-2. Electrical isolation and shielding is recommended but not defined by the standard.

The following tests are performed using the circuit diagram and measurements:
a. Line terminators according to IEC 61158-2
390 Ω 220 Ω 390 Ω
VP DGND
B/B’ A/A’
The value of the termination resistor has to be 220 Ω for cable type A as specified in IEC
61158-2.
b. Compatibility of the bus interface according to IEC 61158-2
pin RS 485 signal

number
1 shield* shield or protective ground
2 M24* ground 24V output voltage
3 B/B’ RxD/TxD-P received/transmitted data - P
4 CNTR-P** repeater control signal - P
5 C/C’ DGND data reference potential output
6 VP power supply voltage output
7 P24V* +24V output voltage
8 A/A’ RxD/TxD-N received/transmitted data - N
9 CNTR-N** repeater control signal - N
* signals are optional
** signals are optional; preferably RS 485 signal level
If a 9 pin D-Sub connector or a M12 circular connector, as described in IEC 61158-2, is used
on the test item, the pin assignment has to correspond to this standard.
If a connector described in the PROFIBUS Guideline "PROFIBUS Interconnection
Technology" is used on the test item, the pin assignment has to correspond to the
specifications of this guideline.
Every connector must include the signals RxD/TxD-P, RxD/TxD-N. If the device has not an
internal bus terminator that can be switched off/on also the signals VP and DGND must be
provided by the connector. If the connector is different from D-Sub connector and it is not
described in the PROFIBUS Guideline "PROFIBUS Interconnection Technology" it is allowed
to include two pins 24V and DGND that also serve for power supply of an active bus
termination. The use of the active bus termination working with 24V instead of a 5V bus
termination has to be described sufficiently in the device documentation.
When optional signals are used, they also must comply with IEC 61158-2 or with the
PROFIBUS Guideline "PROFIBUS Interconnection Technology" and have to agree with the
description in the GSD file.

c. RS 485 circuitry
The test item is driven at its maximum transmission speed with the maximum length of cable
(e.g. 1500 kBit/s at 200 m or 12000 kBit/s at 100m).
The differential voltage and the line level (operation level and idle level with terminating
resistors at both ends) are tested at a PROFIBUS cable with a length of 200m.
The differential voltage between A- and B-line shall be a minimum of 4V and a maximum of
7V.
The signals of the A- and B-line are measured against DGND. The sum of the measured
amplitudes shall be more than 4V. The difference of the amplitudes shall be less than 0,5 V.
d. Impedance and reflection
The reflections on the PROFIBUS cable, caused by the impedance of the device under test
must be checked, if it supports baudrates higher than 1500 kBit/s.
A pulse generator sends a 5V pulse on the bus cable to the device under test. The rise time
(10% to 90%) of the pulse must not exceed 15 ns. The maximum allowed reflection of the
test item is 0,5Vpp.
Example:
max. 0,5V reflection of the
device under test
5V pulse of the
pulse generator
Form and amplitude of the reflection can be controlled by length inductors in the cabling (to
decrease stub capacity in the device).
The pulse generator can be a PROFIBUS master, operating at low baudrate.
It is possible to use inductors to reduce reflections. The overall ohmic resistance for one
signal line shall not exceed 350mΩ.

2. Bus Transmission (Slave Functionality)

a. Control interval monitoring according to IEC 61158-5
It is checked whether the watchdog value set by the master is adhered to.
Measurements are taken with various set times (3 arbitrary values in the allowable range of
10 ms to 650 s). Allowable tolerance: +/- 100 ms at time values higher 1s, otherwise +/- 10 %
of the set time.
b. TSDR according to IEC 61158-3

An oscilloscope is used to check whether the test item adheres to the demanded min. and
max. TSDR according to IEC 61158-3at the available baudrates.
Adhering to the max. TSDR must agree with the entry in the GSD file. The GSD entries for
TSDR should be optimised, e.g. according to the datasheets of the used protocol chips.
c. Addressing
Addressability is tested in the range 0 to 126. Required are minimum 32 different addresses
for a slave.
Modules that use the service Set_Slave_Address must allow to reset the address to a
defined address, normally 126, for addressing with a master (class 2). Within the device must
be the possibility to reset bit NO_ADD_CHG. The device must start after power on with the
same address as it had before switching the power off, if not changed by the tester.
Test parameters: The test item is operated under various addresses.
d. Manufacturer identifier according to IEC 61158-5

The manufacturer identifier must be securely stored in the test item and must not be
changeable when the test item is operated in its intended fashion. The manufacturer identifier
must be the same as the entry in the GSD file and as granted from the PROFIBUS User
Organization.
e. Transmission speeds
It is tested whether data is correctly transmitted at the supported baudrates, depending on
the entry in the GSD file. The master does the parameterization, the slave must recognize
the set baudrates and accept bus communication.
f. Operation in mixed networks

The test item must be able to operate on a bus with PROFIBUS DP stations in conjunction
with PROFIBUS FMS or PA stations. The construction and the bus parameter settings must
be explained in the product description. The slave shall start with the default times according
to IEC 61158-5.

g. Combined (mixed) devices as FMS and DP slave

If the test item can be used as a combined slave, it is tested in mixed operation. The slave
has to start with the default times according to IEC 61158-5.
A combined (mixed) device must be able to start with DP parameters as well as with FMS
parameters.
h. Consistency
If the test item can transmit consistent data, this will also be checked. The test has to be run
device specific. This device specific test is run for a sufficient period of time and it shall show
no consistency error during this time.
i. Min_Slave_Intervall
The entry of the Min_Slave_Intervall in the GSD file has to be according to IEC 61158-6. The
Min_Slave_Intervall of the test item is tested at the highest supported baudrate and shall
agree with the following table:
Baudrate [kbit/s] ≤ 187,5 500 1500 3000 6000 12000

Min_Slave_Intervall ≤ 20 ≤6 ≤2 ≤ 1,5 ≤1 ≤ 0,6
[ms]
These times are valid for all DP slaves. A correct operation of the device under test at the
Min_Slave_Intervall of the GSD file is to be checked.
j. GSD file check
According to IEC 61784.for every PROFIBUS DP slave and master (class 1) must exist one
GSD. The GSD specification is contained in ISO 15745-3 and in the PROFIBUS guideline
"Specification for PROFIBUS Device Description and Device Integration", volume 1.
The correctness of that file is to be tested by the current GSD File Checker of the PROFIBUS
User Organization. The registered features have to match with the features of the device. A
standard tool for generating the parameter sets for the master must be able to interprete the
GSD file correctly, so that the used standard DP master of the test system can start up the
device under test and go to Data_Exchange without any errors.
k. Data format
The data format for transferring 16 Bit words on the PROFIBUS is Motorola format. It is
checked, whether the high byte and the low byte are in the right sequence and whether the
consistency is correct. The used data types have to be according to IEC 61158-5.

3. Function Testing
The function test distinguishes between PROFIBUS single chip and processor interface
solutions (with and without ASIC). Parts of the test can be skipped for single chip solutions if
the chip in question has already been approved (more information concerning this can be
obtained from the PROFIBUS User Organization or test laboratory). This refers to the test
sequences of the state transitions.
a. Bus interruption at the test item (bus disconnected)

All other slaves must still be addressable (bus looped through).
A bus interruption must be detected on the slave (with control interval monitoring) and the
slave must switch to a defined state.
The test item has to take on cyclical bus communication automatically once the error has
been removed.
b. Power supply voltage at test item off/on

After turning on the supply voltage the test item automatically must take on cyclical bus
communication.
c. Network / power supply turned off at master

When the master is switched off it sends a Global_Control_Command CLEAR_DATA. The
test item outputs must switch to a defined state (evaluation of clear data) at once.
d. Network / power supply turned on at master

The test item must take on cyclical bus communication automatically once the master has
been turned on.
e. Master parameterization (with and without control interval monitoring)

The behavior of the test item is checked when the bus is interrupted.
f. Master (class 2) takes control during operation

The test item is in Data_Exchange with a master (class 1). It is checked whether a master
(class 2) can take control of the test item and give back the control to the master (class 1).

g. State transitions
(see state transitions according to IEC 61158-6)

Here is tested the MS0 communication relationship between DP master and DP slave and
the behavior of the FSPMS, MSCY1S and DMPMS protocol machines.
The state transitions of the protocol machines are checked using a test program. The
purpose of the test program is to provide all possible stimulations which realize the state
transitions, defined in the state machine tables of the FSPMS, MSCY1S and DMPMS in the
IEC 61158-6. In the test cases are used all mandatory and all supported optional master-
slave services of MS0:
− master class 1 services for communication with slave, mandatory at slave:
Slave Diag
Set Prm
Chk Cfg
Data Exchange
Global Control
− master class 2 services for communication with slave, mandatory at slave:
Read Input
Read Output
Get Cfg
− master class 1 service for communication with slave, optional at slave:

Set Ext Prm
− master class 2 service for communication with slave, optional at slave:
Set Slave Add
DDLM_Set_Slave_Add
Additionally, frames with invalid lengths are checked (configuration with incorrect length,
parameterization with incorrect user data length, Global_Control with length #2 and
Set_Slave_Address with length < 4).
In the state WAIT-PRM and WAIT-CFG of MSCY1S, the services Global Control, RD Input,
RD Output and Data Exchange must be denied.
Structure of a DP-slave:

AP -Context
Initiate.ind/rsp Started.ind
DLL Init.req/cnf GetPublisherData.req/cnf Read.ind/rsp Stopped.ind
SInit MS0.req/cnf Start Subscriber.req/cnf Write.ind/rsp Abort.ind
SInit MS1.req/cnf Stop Subscriber.req/cnf Data Transport.ind/rsp Fault.ind
SInit MS2.req/cnf Load CRL DXB-Linktable Entries.req/cnf Alarm Ack.ind/rsp Check Ex t User Prm.ind
Reset.req/cnf Set ARL Isochron Mode.req/cnf LR Initiate Load.ind/rsp Set Slav e Add.ind
Abort.req CheckEx tUserPrmResult LR Push Segment.ind/rsp Check User Prm.ind
CheckUserPrmResult.req/cnf .req/cnf LR Pull Segment.ind/rsp Check Cfg.ind
Check Cfg Result.req/cnf Alarm Notification.req/cnf LR Terminate Load.ind/rsp New Output.ind
Set Cfg.req/cnf Application Ready .req FI Start.ind/rsp Global Control.ind
Set Slav e Diag.req/cnf FI Stop.ind/rsp SYNCH_Ev ent.ind
FI Resume.ind/rsp Set Time.ind
Set Input.req/cnf FI Reset.ind/rsp Sy ncInterv alViolation.ind
Get Output.req/cnf FI Call.ind/rsp New Publisher Data.ind
Get FI State.ind/rsp Publisher Activ e.ind
FSPMS
Start.ind Fault.ind New Publisher Data Abort.ind
SInit MS0.req/cnf Stopp.ind Read.ind/rsp .ind Fault.ind
Reset.req/cnf Fault.ind Write.ind/rsp Publisher Activ e.ind Initiate.ind/rsp
Abort.req Set Slav e Add.ind Alarm Ack Read.ind/rsp
Application Ready .req Check User Prm.ind .ind/rsp Write.ind/rsp
CheckUserPrm Check Ex t User Data Transport
Result.req/cnf Prm.ind .ind/rsp
CheckEx tUserPrm Check Cfg.ind
Result.req/cnf New Output.ind Get Publisher
CheckCfgResult.req/cnf Global Control.ind Data.req/cnf Set Time.ind
Set Cfg.req/cnf SYNCH Ev ent.ind StartSubscriber Sy ncInterv alViolation.ind
Set Slav e Diag.req/cnf .req/cnf SInit MS2.req/cnf
Set Input.req/cnf SInit MS1.req/cnf StopSubscriber Reset.req/cnf
Get Output.req/cnf Reset.req/cnf .req/cnf Abort.req
MS Start.req/cnf MS SS MS MS MS
SInit DLL.req/cnf CY Stop.req/cnf AC CY RM AC CS
Reset.req/cnf 1S MS0 Abort.ind 1S MS1 1S MS0 2S 2SMS2 1S MS3
Fault.ind Set Slav e Add.ind DATA DX Broadcast.ind DATA REPLY.ind
Slav e Diag.ind REPLY.ind DX Entered.ind
Set Prm.ind
Slav e Init.req/cnf Set Ex t Prm.ind
Enter.req Chk Cfg.ind
Leav e.req Data Ex change.ind
Slav e Deact.req/cnf Global Control.ind RSAP ACTIVATE CS CLOCK VALUE.ind
Set minTsdr.req .req/cnf
Slav e Diag Upd.req RSAP ACTIVATE.req/cnf SAP DEACTIVATE
Data Ex change Upd.req SAP DEACTIVATE .req/cnf
RD Outp Upd.req .req/cnf REPLY UPDATE
RD Inp Upd.req REPLY UPDATE.req/cnf .req/cnf
DMPMS
DATA.ind RESET.req/cnf
DATA REPLY.ind SET VALUE.req/cnf
MCT DATA REPLY.ind DLSAP ACTIVATE.req/cnf
DXM REPLY.ind DLSAP DEACTIVATE.req/cnf
CS CLOCK VALUE.ind DLSAP ACTIVATE RESPONDER.req/cnf
REPLY UPDATE.req/cnf DLSAP ACTIVATE SUBSCRIBER.req/cnf
DLL

i. Optional features
If optional features are supported, they must be executed according to the standard. The
supported optional features have to be according to the description in the GSD file.
− Freeze
− Sync
These features must be executed immediately after receipt. The group selection must be
recognized.
When these features are activated, the corresponding function bit must be set in the slave
diagnostic.
The test is carried out by reading the slave diagnostic information.
− Fail_safe
This feature must be executed, e.g. if a frame CLEAR or DXCH with the length “0” has been
received.
If the test item uses this optional feature, the safe state of the outputs shall be defined in the
documentation of this device.
j. Evaluation of the diagnostic function

Each slave must provide the octets 1 to 6 according to the standard. Different error states are
created to test the functionality.
Bits marked as reserved in the standard have to be “0”.
If the slave uses ext_diag_data, they must agree with the corresponding entry in the GSD file
and the predefined format described in the standard.
The diagnosability of the test item must be defined in the product description. Ext_diag is
tested using the product description and the bus monitor. If it is not possible to test the
ext_diag (e.g. memory failure) this must be remarked in the test report.
If the device uses the diagnostic function for informing about status (ext_diag_data, but
without having set the bit EXT_DIAG), this also has to be according to IEC 61158-6. The
meaning of the status information has to be defined in the documentation of this device.
Note: If the bit EXT_DIAG is set, the six standard octets are followed by a header with length
information and ext_diag bytes. Then a bit is set in the diagnostic overview for that slave in
the DP master (class 1).
If the bit EXT_DIAG is not set, an ext_diag can follow the six standard octets - according to
IEC 61158-6- with the meaning of a status information. In this case the bit of the diagnostic
overview for that slave in the DP master (class 1) will not be set.
A device can have several blocks of device related diagnostic. For identifier related
diagnostic only one block is allowed.

k. Behavior of a slave to special failures

If the device gets a telegram to a not activated SAP or a non DP SAP, the slave has to
answer with “RS” and remain in the state he was before.
If a slave device is in the state Data_Exchange and receives more data in a Data_Exchange
frame than specified, the slave can either:
answer with “RR” and remains in the state he was before.
or:
answer with “RR” and goes back via POWER_ON with the bit
“CFG_FAULT” set in diagnostic.
or:
answer correctly and goes back to WAIT_PRM with the bit
“CFG_FAULT” set in diagnostic.
That behavior can also be transferred to other states of the slave and corresponding frame
length.
If the test item does not support the function “SET_SLAVE_ADD“ it has to answer with “RS”
when receiving a frame at SAP 55 (0x37). If the test item supports this function it has to
answer with “E5”.
l. Test of modular devices

Both softwaremodular and hardwaremodular devices can appear with a huge number of
instantaneous configuration data, due to the combinatorics of modules and slots. For the test
of modular devices the following preconditions can be applied:
- Different modules with the same I/O data structure will be represented by the most
comprehensively described module (e.g. the module with data type definition and most
parameter data).
- Test of maximum configurations for Output Length, Input Length and Data Length stated
in the GSD with minimum and maximum number of modules.
- Test of additional randomly selected configurations.
- Negative tests for exceeding Data Length, Output Length, Input Length and number of
modules stated in the GSD.
- Negative tests for invalid module assignment and nonspecified configuration identifiers.
Only Config data defined in the GSD are valid. Others have to be rejected.
The testlab may test all or a reasonable subset of tests based on the number of possible test
combinations. Based on these preconditions all modules of a hardwaremodular device
requested by the testlab must be present for test.

4. Interoperability
a. Load Test
The test item’s operation at the maximum sampling frequency on the bus is tested. The
maximum sampling frequency is reached when the test item is operated as a single station at
its highest allowable baudrate and a short evaluation program in the master is run on
PROFIBUS DP.
Can the test item follow this sampling frequency? How does it react? The master must make
the Min_Slave_Intervall time comply with the entry in the GSD file (IDLE 1).
b. Functional Test
The test item is integrated into a test system and is tested on its interoperability with
multifunctional devices in this system. The evaluation program in the master documents the
slave’s functionality.
− The test item is allocated by a DP master (class 1). An evaluation program for cyclic
services and slave diagnostic is created in the master. The evaluation program also takes
possible error states into account caused by the additional slaves.
− During the cyclic operation, the test item will be controlled by a master (class 2).
− Mixed operation (FMS communication or acyclic communication to PA slaves) is also
involved in the test system.
The interoperability test can be carried out in four steps:

1. DP mono master system just with the test item (specimen)
2. DP mono master system with at least 10 slaves
3. DP multi master system with at least 10 slaves
4. Mixed operation consisting of step 3 and FMS or PA components
The individual steps are realized by reconstructing and reparameterizing the overall system.

General System Structure
Test system structure (number of slaves is variable; minimum of 9 slaves + device under
test)
Device
Analyser
Test Test Under
Test DP
System Master
Test
Terminator Terminator
DP
Coupler DP min DP
/Link
Slave . . . . 9. .x Slave
PA Terminator
PA- min PA-

Slave . . . . 1. .x Slave

c. Electromagnetic Compatibility
The customer has to supply either a manufacturer declaration stating the conformity of the
product to the relevant CE standard or a test report concerning EMC measurements -
according to the CE Standard - from an authorized EMC Test Laboratory. An example of a
test report for EMC can be seen in the Appendix.

C - Test of DP-V1 Functions (Extensions to Part B)

For Slaves which support features according to DP-V1, additional tests, covering the
extended communication model shall be carried out.
1. Function Testing
Here are tested the MS1 and MS2 communication relationship between DP master and DP
slave and the behavior of the FSPMS, MSAC1S, MSRM2S, MSAC2S and DMPMS protocol
machines.
The state transitions of the protocol machines are checked using a test program. The
purpose of the test program is to provide all possible stimulations which realize the state
transitions, defined in the state machine tables of the FSPMS, MSAC1S, MSRM2S, MSAC2S
and DMPMS in the IEC 61158-6. Also the dependencies on MS0 communication relationship
are checked.
The conformance of the device to the diagnosis model of DP-V1, dividing alarms and status
messages is checked.
a. MS1 services
− master class 1 services for communication with slave:
Read
Write
Alarm Notification
Alarm Ack

The following features are tested:

− the MSAC1S SAPs shall not be activated in the cyclic states WAIT-PRM and WAIT-
CFG.
− the MSAC1S SAPs shall not be activated when the DPV1_Enable bit in the Parameter
Data is not set.
− in DATA-EXCH only the parameterizing master is allowed to use the MSAC1S SAPs.
− the MS1 services
− the compliance of MS1 features with entries of the GSD file.
− DP-V1 devices which are stated to not support MS1 shall refuse parameter data with
DPV1_Enable bit or Alarm bits set and shall refuse DLPDUs addressed to the
MSAC1S SAPs.

b. MS2 services
− master class 2 services for communication with slave:
Initiate
Abort
Read
Write
Data Transport
The following features are tested:

− the MSAC2S timers (U - user response timer; F - fetch response timer; I - indication
timer) by their reactions.
− the MS2 services
− the compliance of MS2 features with entries of the GSD file.
− DP-V1 devices which are stated to not support MS2 shall refuse DLPDUs addressed
to the MSRM2S SAP.

2. Interoperability and Timing

a. Additional timing features
The cyclic functions with a DP master (class1) according to IEC 61158-5 (see part B) and
also with a DP-V1 master are to be checked. The additional timing of the Slave (e.g.
Send_Timeout) is checked. The used data types have to be according to IEC61158-5.
Baudrate [kbit/s] ≤ 187,5 500 ≥ 1500

Max_Send_Timeout [s] 4 2 1
b. Additional interoperability test

The device under test has to run an additional interoperability test as described in chapter
B.4.b. step 3, together with DP-V1 devices and acyclic bus transmissions by the masters
(class 1 and class 2).
DP-V1 master
DP-V1 master
class 1
class 2
e.g. PLC
MS1 e.g. PC
MS0 READ, WRITE
ALARM, STATUS
PRM, CFG ALARM_ACK MS2
DIAG, DATA_EXCH
INITIATE, ABORT
GLOBAL_CTRL
READ, WRITE
DATA_TRANSPORT
DP-V1 slave
test item

Appendix: Test Report
Test Report Nr.X-Y
Slave on PROFIBUS DP
Page / Attachment File Identifier Department
/
Responsible Party Signature Date

12.03.03
Customer:
Company Name
Address
Technical Contact Person: Mr. Person

Tel.: 123 456 email: name@company.com
Fax.:123 789
Name of Model: Model_Name
Manufacturer: Vendor_Name
Revision: a.b
Software/Firmware Release: c.d / g.h

Hardware Release e.f
Application: Valve block with digital I/Os
Ident Number: Ident_Number HEX
GSD-File: COMP0000.GSD
Minimum Slave Interval: 1,0 ms
Solution applied:
Processor ASIC with processor Single Chip
Designation: SPC3
Summary:
suggested to be certified restrictions suggested not to be certified
Scope of test performed:
DP-V0 MS0, Sync, Freeze, Fail Safe, Set Slave Address
DP-V1 MS1, MS2, Alarms, Structured Parameterization
DP-V2 DxB Publisher, DxB Subscriber, Isochronous Mode
Profile PA-Profile 3.0
Note: The test of the device is made according to following relevant documents:
- Test specification for PROFIBUS-DP Slaves, Version 2.1 from December 2002

Test report
According to the specified test areas:
1. Hardware
Bus Termination
electrical data comply with the demands
bus termination external
electrical data do not comply with the demands
further remarks: Remarks recorded in Italics
PROFIBUS Connection
standard 9 pin D-SUB
nonstandard, but includes all mandatory signals and sufficient description
of the implementation: .....
nonstandard and .....
RS 485
requirements fulfilled
requirements not fulfilled sufficiently
Component Use
electrical data comply with the demands
electrical data do not comply with the demands
2. Bus Transmission
Control Interval Monitoring

adjustable in entire available range
limited in the range of: .....
TSDR
requirements fulfilled
recorded timing behaviour does not conform with PROFIBUS DP: .....
Addressing the Test Item under PROFIBUS

test item can be addressed by Master Class 2
test item can be addressed in the entire available range
limited addressability: The device under test can only be addressed in the range 1-99.
Manufacturer Identifier
as issued
limitations: .....

Transmission Rate
test item can be operated with the following PROFIBUS DP transmission rates:
9,6 kBit/s
19,2 kBit/s
45,45 kBit/s
93,75 kBit/s
187,5 kBit/s
500 kBit/s
1500 kBit/s
3000 kBit/s
6000 kBit/s
12000 kBit/s
restricted operability: at 12000 kBit/s because of the Min_Slave_Int of 1ms.
Mixed Network
no errors in operation detected
errors in operation when: .....
Mixed Operation (specimen can be operated as DP/FMS slave)

test item is not designed for the mixed operation
test item is designed for the mixed operation and no errors in operation detected
the test item could not be further operated on DP when FMS operation was disturbed or
interrupted
the test item could not be further operated on FMS when DP operation was disturbed or
interrupted
other errors in operation when: .....
Consistency
consistency not adjustable on test item
consistency is supported correctly

3. Function Testing
Bus Interruption
correct behaviour
special behaviour when: .....
acceptable
not acceptable in this form
Supply Voltage
correct behaviour
acceptable
Power off/on at Master

correct behaviour
acceptable
With and without Control Interval Monitoring

correct behaviour
acceptable
Master Class 2
correct behaviour
acceptable
State Transitions
nothing unusual in operation could be detected
acceptable
Optional Services
optional services sync and freeze are not supported
sync is supported and is correctly carried out
freeze is supported and is correctly carried out

Diagnostic
mandatory diagnostic is carried out correctly
ext_diag is not used
ext_diag complies with the standard
Acyclic DP-V1 Services

DP-V1 services are not supported
all following Class1 functions are supported and are carried out correctly:
READ, WRITE, ALARM, ALARM_ACK, STATUS
all following Class2 functions are supported and are carried out correctly:
INITIATE, ABORT, READ, WRITE, DATA_TRANSPORT
errors in operation: .....
4. Interoperability
Load Test
load test complies with specifications
Functional Test
no restrictions could be determined
restrictions when: .....
EMC
correct EMC test report according CE standard available
manufacturer’s declaration according CE standard available
no EMC test report or manufacturer’s declaration according CE standard available
EMC restrictions when: .....
5. Supplementary Hints and other Restrictions
Here, verbal descriptions of the following functions are reported:

- any errors or special behaviour with reference to the respective test area
- other test product peculiarities
- remarks concerning manufacturer explanations
- remarks concerning documentation comprehension
Hints:
Restrictions:

6. Test Apparatus and Equipment Used
Here, the test apparatus is documented, all versions of test software and any abnormalities.
This documentation guarantees the test’s reproducibility for 3 years.
Version Testsystem PC :
Hardware version :
Software version :
Version master class 1 :

Hardware state :
Firmware state :
Version master class 2 :

Hardware state :
Firmware state :
Version FMS master :

Hardware state :
Software state :
List of used slaves :

Type specifications sorted according to increasing station number:
.......
7. Attachments
The only enclosures are the measurement reports or recordings which are to inform the
customer or PROFIBUS User Organization about abnormal behaviour.
All recordings are stored in the test laboratory in two separate places accessible only by test
laboratory personnel. The customer and PROFIBUS User Organization can receive all
recordings on demand.

Appendix: Example of an EMC Test Report
Test No ...
Noise Immunity against Highly Transcient Burst Disturbances
according to
IEC 801, Part 4 (1988)
Project:
Test Item:
Responsible Party:
Tester:
Test Location:
Time Range:
Test Requirements/Results
Requirement Requirement fulfilled? Achieved Immunity
Coupling to Level Test yes no Test Voltage
Voltage kV
kV
Current supply lines
Data and signal lines
Result :
Test requirements are fulfilled

not fulfilled
Every single requirement must be met.
Remarks:
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________
Enclosures:
_________________________________________________________________________
_________________________________________________________________________
Date Tester’s Signature

Test No ...
Immunity against Electrostatic Discharge (ESD)
according to
IEC 801, Part 2 (1991)
Project:
Test Item:
Responsible Party:
Tester:
Test Location:
Time Range:
Test Requirements/Results:
Type of discharge Requirement Requirement fulfilled? Achieved Immunity
Level Test yes no Test Voltage
Voltage kV
kV
Contact discharge
Air discharge
HCP
VCP
Result:
Test requirements are fulfilled

not fulfilled
Every single requirement must be met.
Remarks:
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
Enclosures:
__________________________________________________________________________
__________________________________________________________________________
Date Tester’s Signature

 Copyright by:
PROFIBUS Nutzerorganisation e.V.

Haid-und-Neu-Str. 7
D-76131 Karlsruhe
Phone: ++ 721 / 96 58 590
Fax: ++ 721 / 96 58 589
e-mail: pi@profibus.com
http://www.profibus.com

PROFIBUS Guideline - Order No. 2.032: Test Specifications For Profibus - DP Slaves

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PROFIBUS Guideline - Order No. 2.032: Test Specifications For Profibus - DP Slaves

Uploaded by

Copyright:

Available Formats

®

PROCESS FIELD BUS

Test Specifications for

PROFIBUS Guideline – Order No. 2.032

Draft Technical Guideline

Prepared by the PROFIBUS WG 3: „PROFIBUS DP Slave

Phone:++49 721 / 96 58 590

No part of this publication may be reproduced or uitilized in

A - CERTIFICATION TO VERIFY PROFIBUS FUNCTIONALITY 3

2. Hints for a quicker test 3

3. Responsibility of the test laboratory 5

4. How to get a certificate 6

B - TEST OF DP STANDARD FUNCTIONS 7

2. Bus Transmission (Slave Functionality) 10

© PNO 2002, Copyright - all rights reserved Page 1

C - TEST OF DP-V1 FUNCTIONS (EXTENSIONS TO PART B) 21

2. Interoperability and Timing 24

APPENDIX: TEST REPORT 25

APPENDIX: EXAMPLE OF AN EMC TEST REPORT 31

© PNO 2002, Copyright - all rights reserved Page 2

A - Certification to verify PROFIBUS functionality

1. Name and address of the applicant.

2. Hints for a quicker test

© PNO 2002, Copyright - all rights reserved Page 3

© PNO 2002, Copyright - all rights reserved Page 4

3. Responsibility of the test laboratory

© PNO 2002, Copyright - all rights reserved Page 5

4. How to get a certificate

Customer develops a field device

Customer orders an identnumber from the PNO

Test of the field-

© PNO 2002, Copyright - all rights reserved Page 6

B - Test of DP Standard Functions

Sample circuit diagram:

OUT Driver select: Differential voltage > 2V 9

Layout: lines must be kept as short as possible. Shield

© PNO 2002, Copyright - all rights reserved Page 7

a. Line terminators according to IEC 61158-2

390 Ω 220 Ω 390 Ω

b. Compatibility of the bus interface according to IEC 61158-2

pin RS 485 signal

© PNO 2002, Copyright - all rights reserved Page 8

© PNO 2002, Copyright - all rights reserved Page 9

2. Bus Transmission (Slave Functionality)

b. TSDR according to IEC 61158-3

d. Manufacturer identifier according to IEC 61158-5

f. Operation in mixed networks

© PNO 2002, Copyright - all rights reserved Page 10

g. Combined (mixed) devices as FMS and DP slave

Baudrate [kbit/s] ≤ 187,5 500 1500 3000 6000 12000

j. GSD file check

© PNO 2002, Copyright - all rights reserved Page 11

a. Bus interruption at the test item (bus disconnected)

b. Power supply voltage at test item off/on

c. Network / power supply turned off at master

d. Network / power supply turned on at master

e. Master parameterization (with and without control interval monitoring)

f. Master (class 2) takes control during operation

© PNO 2002, Copyright - all rights reserved Page 12

© PNO 2002, Copyright - all rights reserved Page 13

− master class 1 service for communication with slave, optional at slave:

© PNO 2002, Copyright - all rights reserved Page 14

© PNO 2002, Copyright - all rights reserved Page 15