Phoenix Contact FLM BK PB M12 DI 8 M12-EF User manual

AUTOMATION
UM EN
FLM BK PB M12 DI 8 M12-EF
User Manual
Diagnostic and firmware functions
of the FLM BK PB M12 DI 8 M12-EF bus coupler

Designation:
Revision:
This user manual is valid for
AUTOMATION
8097_en_00 PHOENIX CONTACT
2010-07-26
Diagnostic and firmware functions of the FLM BK PB M12 DI 8 M12-EF
bus coupler
UM EN FLM BK PB M12 DI 8 M12-EF
00
the FLM BK PB M12 DI 8 M12-EF bus coupler Order No.: 2773377
User Manual

UM EN FLM BK PB M12 DI 8 M12-EF
PHOENIX CONTACT 8097_en_00
Please observe the following notes
In order to ensure the safe use of the product described, you have to read and understand
this manual. The following notes provide information on how to use this manual.
User group of this manual
The use of products described in this manual is oriented exclusively to qualified electricians
or persons instructed by them, who are familiar with applicable standards and other
regulations regarding electrical engineering and, in particular, the relevant safety concepts.
Phoenix Contact accepts no liability for erroneous handling or damage to products from
Phoenix Contact or third-party products resulting from disregard of information contained in
this manual.
Explanation of symbols used and signal words
The following types of messages provide information about possible property damage and
general information concerning proper operation and ease-of-use.
This is the safety alert symbol. It is used to alert you to potential personal injury
hazards. Obey all safety messages that follow this symbol to avoid possible
injury or death.
DANGER
This indicates a hazardous situation which, if not avoided, will result in death or serious
injury.
WARNING
This indicates a hazardous situation which, if not avoided, could result in death or serious
injury.
CAUTION
This indicates a hazardous situation which, if not avoided, could result in minor or
moderate injury.
NOTE
This symbol and the accompanying text alerts the reader to a situation which may cause
damage or malfunction to the device, either hardware or software, or surrounding
property.
This symbol and the accompanying text provides additional information to the reader. It is
also used as a reference to other sources of information (manuals, data sheets, literature)
on the subject matter, product, etc.

UM EN FLM BK PB M12 DI 8 M12-EF
8097_en_00 PHOENIX CONTACT
General terms and conditions of use for technical documentation
Phoenix Contact reserves the right to alter, correct, and/or improve the technical
documentation and the products described in the technical documentation at its own
discretion and without giving prior notice, insofar as this is reasonable for the user. The
same applies to any technical changes that serve the purpose of technical progress.
The receipt of technical documentation (in particular data sheets, installation instructions,
manuals, etc.) does not constitute any further duty on the part of Phoenix Contact to furnish
information on alterations to products and/or technical documentation. Any other
agreement shall only apply if expressly confirmed in writing by Phoenix Contact. Please
note that the supplied documentation is product-specific documentation only and that you
are responsible for checking the suitability and intended use of the products in your specific
application, in particular with regard to observing the applicable standards and regulations.
Although Phoenix Contact makes every effort to ensure that the information content is
accurate, up-to-date, and state-of-the-art, technical inaccuracies and/or printing errors in
the information cannot be ruled out. Phoenix Contact does not offer any guarantees as to
the reliability, accuracy or completeness of the information. All information made available
in the technical data is supplied without any accompanying guarantee, whether expressly
mentioned, implied or tacitly assumed. This information does not include any guarantees
regarding quality, does not describe any fair marketable quality, and does not make any
claims as to quality guarantees or guarantees regarding the suitability for a special purpose.
Phoenix Contact accepts no liability or responsibility for errors or omissions in the content
of the technical documentation (in particular data sheets, installation instructions, manuals,
etc.).
The aforementioned limitations of liability and exemptions from liability do not apply, in so
far as liability must be assumed, e.g., according to product liability law, in cases of
premeditation, gross negligence, on account of loss of life, physical injury or damage to
health or on account of the violation of important contractual obligations. Claims for
damages for the violation of important contractual obligations are, however, limited to
contract-typical, predictable damages, provided there is no premeditation or gross
negligence, or that liability is assumed on account of loss of life, physical injury or damage
to health. This ruling does not imply a change in the burden of proof to the detriment of the
user.

UM EN FLM BK PB M12 DI 8 M12-EF
PHOENIX CONTACT 8097_en_00
Statement of legal authority
This manual, including all illustrations contained herein, is copyright protected. Use of this
manual by any third party is forbidden. Reproduction, translation, and public disclosure, as
well as electronic and photographic archiving or alteration requires the express written
consent of Phoenix Contact. Violators are liable for damages.
Phoenix Contact reserves all rights in the case of patent award or listing of a registered
design. Third-party products are always named without reference to patent rights. The
existence of such rights shall not be excluded.
How to contact us
Internet Up-to-date information on Phoenix Contact products and our Terms and Conditions can be
found on the Internet at:
www.phoenixcontact.com.
Make sure you always use the latest documentation.
It can be downloaded at:
www.phoenixcontact.net/catalog.
Subsidiaries If there are any problems that cannot be solved using the documentation, please contact
your Phoenix Contact subsidiary.
Subsidiary contact information is available at www.phoenixcontact.com.
Published by .
Should you have any suggestions or recommendations for improvement of the contents and
layout of our manuals, please send your comments to
[email protected].
PHOENIX CONTACT GmbH & Co. KG
Flachsmarktstraße 8
32825 Blomberg
Germany
Phone +49 - (0) 52 35 - 3-00
Fax +49 - (0) 52 35 - 3-4 12 00
PHOENIX CONTACT
P.O. Box 4100
Harrisburg, PA 17111-0100
USA
Phone [phone]

8097_en_00 PHOENIX CONTACT i
Table of Contents
1 The Fieldline Modular Bus Coupler for PROFIBUS .................................................................1-1
2 Diagnostics .............................................................................................................................2-1
2.1 Activating/deactivating the diagnostic formats....................................................2-1
2.1.1 Diagnostics in the FLM BK PB M12 DI 8 M12-EF format ....................2-2
2.1.2 Status PDU diagnostic format .............................................................2-8
2.1.3 ID-specific diagnostic format ...............................................................2-9
2.2 Local diagnostic indicators ...............................................................................2-10
3 Acyclic Communication (DP/V1 and PCP) ..............................................................................3-1
3.1 Acyclic Communication via C1 Master ...............................................................3-1
3.2 Acyclic Communication via C2 Master ...............................................................3-1
3.3 PCP Communication Basics...............................................................................3-2
3.4 Acyclic Communication in DP/V1 Mode .............................................................3-4
3.4.1 The Communication Mechanism ........................................................3-4
3.4.2 Examples ............................................................................................3-7
3.5 Acyclic Communication in DP/V0 Mode via Process Data................................3-13
3.5.1 Mechanism for Transmission in the Process Data ............................3-13
3.5.2 Examples of VC1 Services ................................................................3-18
4 Dynamic Configuration ............................................................................................................4-1
4.1 Empty Spaces ....................................................................................................4-1
4.2 Principle of the Dynamic Configuration...............................................................4-3
4.3 Startup................................................................................................................4-5
4.3.1 Planning Configuration ........................................................................4-5
4.3.2 Options for Specifying the Active Configuration ..................................4-6
4.3.3 Specification of the Active Configuration via DP/V0 ............................4-7
4.3.4 Specification of the Active Configuration via DP/V1 ..........................4-10
4.3.5 Summary ..........................................................................................4-11
5 IO-Link ....................................................................................................................................5-1
A Appendix ................................................................................................................................ A-1
A 1 Error Codes for PCP Communication ................................................................ A-1
A 2 Error Codes for DP/V1 and VC1 Communication .............................................. A-3
A 3 Format of the Parameter Telegram.................................................................... A-4
B Object dictionaries .................................................................................................................. B-1
B 1 Slot 0 ................................................................................................................. B-1
B 2 Slot 1 ................................................................................................................. B-8
B 3 Slots 2 to 16....................................................................................................... B-8

UM EN FLM BK PB M12 DI 8 M12-EF
ii PHOENIX CONTACT 8097_en_00

The Fieldline Modular Bus Coupler for PROFIBUS
8097_en_00 PHOENIX CONTACT 1-1
1 The Fieldline Modular Bus Coupler for PROFIBUS
The bus coupler connects a Fieldline modular station to PROFIBUS-DP and is also used to
acquire digital signals.
16 devices can be connected in any position to an existing PROFIBUS-DP system using the
bus coupler.
The PROFIBUS bus coupler can be ordered using Order No. 2773377.
Figure 1-1 Fieldline Modular bus coupler for PROFIBUS
Features – Connection to PROFIBUS-DP using M12 connectors (B-encoded)
– Opens the Fieldline modular local bus using M12 connectors (B-encoded)
– Length local bus max. 20 m
– Data transmission speed max. 12 Mbps (automatic detection)
– Device description using GSD file
– Dynamic configuration and empty spaces
– Supported PROFIBUS addresses 1 to 126
– Up to 16 PCP devices can be connected
–I& M functions
– Connection of digital sensors using M12 connectors
– Flexible voltage supply concept
– LED diagnostic and status indicators for bus operation and voltage supply
– Short-circuit and overload protection of the sensor supply
– Channel-specific diagnostics for different I/O devices
– IP65/IP67 protection
– IO-Link-Call (firmware 2.0 or later)
7008A001

UM EN FLM BK PB M12 DI 8 M12-EF
1-2 PHOENIX CONTACT 8097_en_00
For additional information about the bus coupler, please refer to the following documents:
Data sheet: DB EN FLM BK PB M12 DI 8 M12-EF
Handbücher: FLS FLM SYS INST UM E und FLS FLM PB SYS PRO UM E
They can be downloaded at www.phoenixcontact.net/catalog.
Configuration and start-up with the Step7 SIMATIC Manager are described in detail in the
FLS FLM PB SYS PRO UM E.

Diagnostics
8097_en_00 PHOENIX CONTACT 2-1
2Diagnostics
The diagnostic concept for the bus coupler consists of two components.
– Firstly, diagnostic data is supplied to the control system via PROFIBUS in the form of
diagnostic bytes.
– Secondly, local diagnostics are available, whereby the error type is indicated by the
LEDs on the bus coupler.
2.1 Activating/deactivating the diagnostic formats
The diagnostic format can be set as a parameter on the terminal.
You can select either:
– FLM BK PB M12 DI 8 M12-EF Format
– Status-PDU Diagnostics
– ID-Specific Diagnostics
By default, "FLM BK PB M12 DI 8 M12-EF Format" is activated.
Figure 2-1 Diagnostic formats dialog box

UM EN FLM BK PB M12 DI 8 M12-EF
2-2 PHOENIX CONTACT 8097_en_00
2.1.1 Diagnostics in the FLM BK PB M12 DI 8 M12-EF format
This diagnostic format consists of the following blocks:
1PROFIBUS standard diagnostics
2ID-specific diagnostics
3Status diagnostics (terminal status)
4Channel-specific diagnostics
5Revision diagnostics (manufacturer-specific)
6Status-PDU (manufacturer-specific)
The header bytes are used to distinguish between all blocks.
From block 2 onwards the diagnostic telegram is dynamic. The individual number of bytes
in a block depends on the station structure.
Table 2-1 FLM BK PB M12 DI 8 M12-EF format diagnostics
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Meaning
Block 1
1 X X X X X X X X Station status 1
2 X X X X X X X X Station status 2
3 X X X X X X X X Station status 3
4 X X X X X X X X PROFIBUS master address
5 0 0 0 0 1 0 1 1 Manufacturer ID high byte (0Chex)
6 0 1 0 1 0 0 0 0 Manufacturer ID low byte (39hex)
Block 2
7 0 1 Number of local bus devices ID-specific diagnostics (header)
8LD 8 LD 7 LD 6 LD 5 LD 4 LD 3 LD 2 LD 1 Local bus devices 1 to 8
9LD 16 LD 15 LD 14 LD 13 LD 12 LD 11 LD 10 LD 9 Local bus devices 9 to 16

Diagnostics
8097_en_00 PHOENIX CONTACT 2-3
Block 3
16 0 0 Number of local bus devices Status PDU (header)
17 1 0 0 0 0 0 1 0 Status type = terminal status
18 0 0 0 0 0 0 0 0 Slot (= 0 = general status of the bus
coupler)
19 0 0 0 0 0 0 SP SP Specifier
20 ST LD 4 ST LD 3 ST LD 2 ST LD 1 Status, local bus devices 1 to 4
21 ST LD 8 ST LD 7 ST LD 6 ST LD 5 Status, local bus devices 5 to 8
... ST LD 12 ST LD 11 ST LD 10 ST LD 9 Status, local bus devices 9 to 12
35 ST LD 16 ST LD 15 ST LD 14 ST LD 13 Status, local bus devices 13 to 16
Block 4
36 1 0 Slot Channel-specific diagnostics (header)
slot 1
37 IO Channel IN/OUT and channel number slot 1
38 CT ET Channel and error type slot 1
... 1 0 Slot number Channel-specific diagnostics (header)
slot 2
... IO Channel IN/OUT and channel number slot 2
... CT ET Channel and error type slot 1
... ... ... ... ... ... ... ... ... ...
... 1 0 Slot number Channel-specific diagnostics (header)
slot 10
... IO Channel IN/OUT and channel number slot 10
65 CT ET Channel and error type slot 10
Table 2-1 FLM BK PB M12 DI 8 M12-EF format diagnostics
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Meaning

UM EN FLM BK PB M12 DI 8 M12-EF
2-4 PHOENIX CONTACT 8097_en_00
Block 5
66 1 1 X X X X X X Version (start with C1)
Block 6
67 0 0 0 0 1 1 0 0 Status (header)
68 1 0 1 0 0 0 0 0 Reserved (header)
69 0 0 0 0 0 0 0 0 Reserved (header)
70 0 0 0 0 0 0 0 0 Reserved (header)
71 0 0 0 0 0 0 B B Local bus baud rate
1 = 500 kbaud
2 = 2 Mbaud
72 X X X X X X X X Diagnostic location (FF = OK)
73 X X X X X X X X User ID code,
1st local bus device with error
74 X X X X X X X X User length code,
1st local bus device with error
75 X X X X X X X X LB state (high byte)
76 X X X X X X X X LB state (low byte)
77 0 0 0 0 0 0 0 X System limit violated?
78 X X X X X X X X Number of accessible local bus devices
Table 2-1 FLM BK PB M12 DI 8 M12-EF format diagnostics
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Meaning

Diagnostics
8097_en_00 PHOENIX CONTACT 2-5
Block 1: PROFIBUS standard diagnostics
X: Value 1 is activated. Value 0 is deactivated.
M: Slave transmits 0, master adds if necessary.
Table 2-2 Byte 1: Status 1
76543210
MStation does not exist.
XSlave is not ready for data exchange.
XError in configuration telegram
XExtended diagnostics follows in the telegram.
XThe requested function is not supported by the slave.
MInvalid response from slave
XError in parameter telegram
MSlave assigned to another master
Table 2-3 Byte 2: Status 2
76543210
XSlave must be reparameterized.
XStatic diagnostics
1Fixed to 1 for DP operation
XWatchdog activated
XFreeze command received
XSync command received
0Reserved
MSlave is deactivated.
Table 2-4 Byte 3: Status 3
7 6 5 4 3 2 1 0
0000000Reserved
XSlave has more diagnostic information than displayed in the telegram.
Table 2-5 Byte: Master address
76543210
0-125 (00hex-7Ehex)Master address following parameterization, default address is 255 (FFhex)
Table 2-6 Byte 5 and 6: ID number
76543210
0-225 (00hex-FFhex)ID number high byte
0-225 (00hex-FFhex)ID number low byte

UM EN FLM BK PB M12 DI 8 M12-EF
2-6 PHOENIX CONTACT 8097_en_00
Block 2: ID-specific diagnostics
The table 2-1 shows the faulty local bus devices. For every faulty terminal, a "1" is entered.
In the first byte of the block, bits 0 to 5 specify the number of local bus devices and therefore
the length L of the block (8 devices for each byte, maximum). The minimum length of this
block is 2 bytes (1-byte header + 1 byte (8 devices, maximum)), the maximum length is
3 bytes (1-byte header + 2 bytes (16 devices, maximum)). The size of the ID-specific
diagnostic block depends on the number of configured terminals.
Block 3: Status PDU (terminal status)
For every local bus device there are 2 bits for status encoding:
The specifier (SP) equals 1 in the event of a faulty state. The specifier equals 2 if the terminal
changes from a faulty state to an error-free state. If the specifier equals 0, the state has not
changed.
In the first byte of the block, bits 0 to 5 specify the number of local bus devices and therefore
the length of the Status-PDU block. The minimum length of this block is 5
(4-byte header + 1 byte (4 devices, maximum)), the maximum length is 8 (4-byte header +
4 bytes (16 devices, maximum)). The size of the status PDU block therefore depends on the
number of configured terminals.
ST LD x: 00 = Terminal data valid
ST LD x: 01 = Terminal data invalid due to an error
ST LD x: 10 = Terminal data invalid due to incorrect terminal being connected
ST LD x: 11 = Terminal data invalid or no terminal connected
(despite configuration)
SP: 0 = No evaluation
SP: 1 = Error occurs (number > 0)
SP: 2 = Error disappears (number = 0)
SP: 3 = Reserved

Diagnostics
8097_en_00 PHOENIX CONTACT 2-7
Block 4: Channel-specific diagnostics
Up to 10 channel errors are indicated here. There are 3 bytes per channel error, this block
can be a maximum of 30 bytes in size. Each channel error is an individual and independent
error. In order to display the channel errors, the I/O terminal must support PCP (Peripherals
Communication Protocol) and channel-specific diagnostics must be activated on the bus
coupler.
Block 5: Revision diagnostics
Indicates the firmware version, e.g., C3hex = Version 3
IO: 00bin = Reserved
IO: 01bin = Input
IO: 10bin = Output
IO: 11bin = Input and output
Channel: Channel number of the relevant channel (0 to 16)
CT: 000bin = Reserved
CT: 001bin = 1 bits
CT: 010bin = 2 bits
CT: 011bin = 4 bits
CT: 100bin = 1 byte
CT: 101bin = 1 word
CT: 110bin = 2 words
CT: 111bin = Reserved
ET: 0 = Reserved
ET: 1 = Short circuit
ET: 2 = Undervoltage
ET: 3 = Surge voltage
ET: 4 = Overload
ET: 5 = Overtemperature
ET: 6 = Cable break
ET: 7 = Upper limit value exceeded
ET: 8 = Lower limit value exceeded
ET: 9 = General error

UM EN FLM BK PB M12 DI 8 M12-EF
2-8 PHOENIX CONTACT 8097_en_00
Block 6: Status PDU
The sixth block is also encoded as a status PDU block, but in manufacturer-specific format.
The information stored here does not usually need to be evaluated.
Byte 5 indicates the baud rate at which the local bus is operated.
Byte 7 and byte 8 indicate the ID and length code of the first faulty terminal. This can be used
as additional information for blocks 2 and 3, if required.
The value of byte 11 is 1 if a system limit was violated.
Byte 12 indicates the number of available terminals.
2.1.2 Status PDU diagnostic format
This diagnostic format consists of the following blocks:
1PROFIBUS standard diagnostics (see also 2.1.1 on page 2-2)
2Status-PDU (manufacturer-specific)
The bus coupler is always counted as a local bus device (LD). In the event of an error on
the bus coupler, the corresponding bits for local bus device 1 are set in the diagnostics.
Table 2-7 Status PDU diagnostics incl. error codes
Byte X Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Meaning
Block 1
1 X X X X X X X X Station status 1
2 X X X X X X X X Station status 2
3 X X X X X X X X Station status 3
4 X X X X X X X X PROFIBUS master address
5 0 0 0 0 1 0 1 1 Manufacturer ID high byte (0Chex)
6 0 1 0 1 0 0 0 0 Manufacturer ID low byte (39hex)
Block 2
7 0 0 0 0 1 0 0 1 Status (header) + length
8 1 0 1 0 0 0 0 1 Status type = e.g., A1hex (header)
9 X X X X X X X X Slot number (header)
10 0 0 0 0 0 0 X X Status specifier (header)
11 X X X X X X X X Error code, high byte
12 X X X X X X X X Error code, low byte
13 X X X X X X X X User ID code,
local bus device with error
14 X X X X X X X X User length code,
local bus device with error
15 X X X X X X X X FW version (e.g., 33hex)

Diagnostics
8097_en_00 PHOENIX CONTACT 2-9
Block 2: Status PDU
In Byte 8 you find the Standard Status message.
2.1.3 ID-specific diagnostic format
This diagnostic format consists of the following blocks:
1PROFIBUS standard diagnostics (see also 2.1.1 on page 2-2)
2ID-specific diagnostics (see also page 2-6)
81hex Standard status message
Byte 11 and byte 12 provide more detailed information on the standard status message:
High byte Error type
Low byte Error number
Table 2-8 ID-specific (terminal) diagnostics
Byte X Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Meaning
Block 1
1 X X X X X X X X Station status 1
2 X X X X X X X X Station status 2
3 X X X X X X X X Station status 3
4 X X X X X X X X PROFIBUS master address
5 0 0 0 0 1 0 1 1 Manufacturer ID high byte (0Chex)
6 0 1 0 1 0 0 0 0 Manufacturer ID low byte (39hex)
Block 2
7 0 1 X X X X X X Number of devices (values 0 to 16)
8 X X X X X X X X Terminals 1 to 8 (values 0 to 255)
9 X X X X X X X X Terminals 9 to 16 (values 0 to 255)

UM EN FLM BK PB M12 DI 8 M12-EF
2-10 PHOENIX CONTACT 8097_en_00
2.2 Local diagnostic indicators
The LEDs on the bus coupler show the Error type.
Figure 2-2 Local diagnostic indicators on the bus coupler
BK PB
UL S
I N
U S
O U T
I N
B U S U L
B F
M D L B
O U T
UL S
I 1 I 2
I 3 I 4
I 5 I 6
I 7 I 8
R U N
2 M B D
B F
U L
U S
M D
X X
7 0 0 8 A 0 0 3
X X
X X
X X
RUN
02
4
6
9
8
02
4
6
8
1 2
1 0
1 0
x
1
x
2 M B D