Phoenix Contact PROFI BUS AXL F BK PB User manual

User manual
Diagnostic and
firmware functions
of the AXL F BK PB bus coupler

2015-06-22
PHOENIX CONTACT 8453_en_03
Diagnostic and firmware functions of the AXL F BK PB bus coupler
UM EN AXL F BK PB
03
Designation Version Order No.
AXL F BK PB Hardware 04 or later
Firmware 2.00 or later
2688530
User manual
Designation:
Revision:
This user manual is valid for:

PHOENIX CONTACT
Please observe the following notes
User group of this manual
The use of products described in this manual is oriented exclusively to qualified application
programmers and software engineers, who are familiar with the safety concepts of automa-
tion technology and applicable standards.
Explanation of symbols used and signal words
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:
phoenixcontact.com
Make sure you always use the latest documentation.
It can be downloaded at:
phoenixcontact.net/products
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 phoenixcontact.com.
Published by PHOENIX CONTACT GmbH & Co. KG
Flachsmarktstraße 8
32825 Blomberg
GERMANY
Should you have any suggestions or recommendations for improvement of the contents and
layout of our manuals, please send your comments to:
[e-mail]
This is the safety alert symbol. It is used to alert you to potential personal injury
hazards. Obey all safety measures that follow this symbol to avoid possible in-
jury or death.
There are three different categories of personal injury that are indicated with a
signal word.
DANGER This indicates a hazardous situation which, if not avoided, will re-
sult 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.
This symbol together with the signal word NOTE and the accompanying text
alert the reader to a situation which may cause damage or malfunction to the
device, hardware/software, or surrounding property.
This symbol and the accompanying text provide the reader with additional in-
formation or refer to detailed sources of information.

Please observe the following notes
PHOENIX CONTACT
General terms and conditions of use for technical documentation
Phoenix Contact reserves the right to alter, correct, and/or improve the technical documen-
tation 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 user documentation) does not consti-
tute any further duty on the part of Phoenix Contact to furnish information on modifications
to products and/or technical documentation. You are responsible to verify the suitability and
intended use of the products in your specific application, in particular with regard to observ-
ing the applicable standards and regulations. All information made available in the technical
data is supplied without any accompanying guarantee, whether expressly mentioned, im-
plied or tacitly assumed.
In general, the provisions of the current standard Terms and Conditions of Phoenix Contact
apply exclusively, in particular as concerns any warranty liability.
This manual, including all illustrations contained herein, is copyright protected. Any
changes to the contents or the publication of extracts of this document is prohibited.
Phoenix Contact reserves the right to register its own intellectual property rights for the
product identifications of Phoenix Contact products that are used here. Registration of such
intellectual property rights by third parties is prohibited.
Other product identifications may be afforded legal protection, even where they may not be
indicated as such.

Table of contents
8453_en_03 PHOENIX CONTACT 5
Table of contents
1 PROFIBUS bus coupler .............................................................................................................7
2 Diagnostics ................................................................................................................................9
2.1 Activating/deactivating the diagnostic formats....................................................... 9
2.1.1 Diagnostics in common format ............................................................. 10
2.1.2 Diagnostics in status PDU format ......................................................... 15
2.1.3 Diagnostics in identifier-related format
(ID-specific diagnostics) ....................................................................... 16
2.2 Representing the error codes .............................................................................. 17
2.2.1 Local diagnostic indicators ................................................................... 17
2.2.2 Error type and error number ................................................................. 18
3 Acyclic communication (DP/V1 and PDI) .................................................................................21
3.1 Acyclic communication via the Class 1 master (C1master) ................................. 22
3.2 Acyclic communication via the Class 2 master (C2master) ................................. 22
3.3 Acyclic communication in DP/V1 mode ............................................................... 22
3.3.1 Communication mechanism ................................................................ 22
4 Dynamic configuration .............................................................................................................27
4.1 Empty spaces...................................................................................................... 27
4.2 Principle of dynamic configuration....................................................................... 30
4.3 Startup................................................................................................................ 31
4.3.1 Planning the configuration .................................................................... 31
4.3.2 Options for specifying the active configuration ..................................... 32
4.3.3 Specifying the active configuration via DP/V1 ...................................... 33
4.3.4 Summary ............................................................................................. 34
A Appendix ..................................................................................................................................35
A 1 Error codes for acyclic communication ................................................................ 35
A 2 Error codes for DP/V1 communication................................................................. 36
A 3 Format of the parameter telegram ....................................................................... 37
B Object dictionaries ....................................................................................................................41
B 1 Slot 0 ................................................................................................................... 41
B 2 Slots 1 to 63......................................................................................................... 46

AXL F BK PB
6PHOENIX CONTACT 8453_en_03

PROFIBUS bus coupler
8453_en_03 PHOENIX CONTACT 7
1 PROFIBUS bus coupler
PROFIBUS bus coupler The bus coupler is the link between a PROFIBUS network and the Axioline F system.
Up to 63 Axioline F devices can be connected to an existing PROFIBUS system using the
bus coupler.
Features – PROFIBUS connection via D-SUB 9 socket
– Interface physics RS-485 for PROFIBUS
– Electrical isolation between PROFIBUS interface and logic
– Up to 63 additional Axioline F devices can be connected
– DP/V1 for class 1 and class 2 masters
– Data transmission speed of 9.6 kbps up to 12 Mbps (automatic detection)
– Rotary coding switches for setting the PROFIBUS address
– Supported PROFIBUS addresses 0 to 126
– Device description using GSD file
–I&Mfunctions
– Typical cycle time of the Axioline F local bus is around 10 μs
– Diagnostics and status indicators
In addition to this document, please also observe the information in the following
documents:
– Module-specific data sheet
– “Axioline: System and installation” user manual, UM EN AXL SYS INST
They can be downloaded at:
phoenixcontact.net/catalog

AXL F BK PB
8PHOENIX CONTACT 8453_en_03

Diagnostics
8453_en_03 PHOENIX CONTACT 9
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 specific
flashing codes of the LEDs on the bus coupler.
2.1 Activating/deactivating the diagnostic formats
The diagnostic format can be set as a parameter on the module. You can either select
display in common format, status PDU format or identifier-related format (ID-specific
diagnostics). By default, common format is activated.
Figure 2-1 Selection dialog - Diagnostic formats

AXL F BK PB
10 PHOENIX CONTACT 8453_en_03
2.1.1 Diagnostics in common format
This diagnostic format consists of the following blocks:
1PROFIBUS standard diagnostics
2ID-specific diagnostics
3Status diagnostics (device status)
4Channel-specific diagnostics
5Revision diagnostics (manufacturer-specific)
6Status-PDU (manufacturer-specific)
The header bytes are used to distinguish between all blocks.
The diagnostic telegram is dynamic from block 2 onwards. Therefore, the number of bytes
in a block depends on the station structure used.
Table 2-1 Diagnostics in common format
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 1 0 1 Manufacturer ID, high byte (0Dhex)
6 1 0 1 1 0 1 0 0 Manufacturer ID, low byte (B4hex)
Block 2
7 0 1 Length of block ID-specific diagnostics (header)
8 LD 8 LD 7 LD 6 LD 5 LD 4 LD 3 LD 2 LD 1 Local bus devices 1 ... 8
9 LD 16 LD 15 LD 14 LD 13 LD 12 LD 11 LD 10 LD 9 Local bus devices 9 ... 16
... ... ... ... ... ... ... ... ... ...
15 0 LD 63 LD 62 LD 61 LD 60 LD 59 LD 58 LD 57 Local bus devices 57 ... 63
Block 3
16 0 0 Length of block Status (header)
17 1 0 0 0 0 0 1 0 Status type = device status
1800000 0 0 0
Slot (= 0 = general status of the bus
coupler)
1900000 0SPSPSpecifier
20 ST LD 4 ST LD 3 ST LD 2 ST LD 1 Status of local bus devices 1 ... 4
21 ST LD 8 ST LD 7 ST LD 6 ST LD 5 Status of local bus devices 5 ... 8
... … … … … … … … … …
35 0 ST LD 63 ST LD 62 ST LD 61 Status of local bus devices 61 ... 63

Diagnostics
8453_en_03 PHOENIX CONTACT 11
Block 4 (ten errors possible, maximum)
36 1 0 Slot Channel-specific diagnostics (header),
error 1
37 IO Channel IN/OUT and channel number, error 1
38 CT ET Channel and error type, error 1
39 1 0 Slot Channel-specific diagnostics (header),
error 2
40 IO Channel IN/OUT and channel number, error 2
... CT ET Channel and error type, error 2
... ... ... ... ... ... ... ... ... ...
63 1 0 Slot Channel-specific diagnostics (header),
error 10
64 IO Channel IN/OUT and channel number, error 10
65 CT ET Channel and error type, error 10
Block 5
66 1 1 X X X X X X Revision (start with C1hex)
Block 6
67 0 0 0 0 1 1 0 1 Status (header) with block length 13
68 X X X X X X X X Status type (81hex)
69 Slot Slot number of the module with the last
reported error
7000000 0SPSPSpecifier
71 X X X X X X X X Error code of byte 3
72 X X X X X X X X Error code of byte 2
73 X X X X X X X X Error code of byte 1/error type
74 X X X X X X X X Error code of byte 0/error number
75 X X X X X X X X Local bus diagnostic status register 1
76 X X X X X X X X Local bus diagnostic status register 0
77 X X X X X X X X Local bus diagnostic parameter register 1
77 X X X X X X X X Local bus diagnostic parameter register 0
78 X X X X X X X X Number of accessible local bus devices
Table 2-1 Diagnostics in common format
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Meaning

AXL F BK PB
12 PHOENIX CONTACT 8453_en_03
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
7 6 5 4 3 2 1 0
M Station does not exist
X Slave is not ready for data exchange
X Error in configuration telegram
X Extended diagnostics follows in the telegram
X Requested function is not supported by the slave
M Invalid response from slave
X Error in parameter telegram
M Slave assigned to another master
Table 2-3 Byte 2: status 2
76543210
X Slave must be reparameterized
XStaticdiagnostics
1 Fixed to 1 for DP operation
X Watchdog activated
X Freeze command received
X Sync command received
0 Reserved
M Slave is deactivated
Table 2-4 Byte 3: status 3
76543210
0000000Reserved
X Slave has more diagnostic information than displayed in the telegram
Table 2-5 Byte 4: master address
76543210
0-125 (00hex-7Ehex) Master address following parameterization, default address is 255 (FFhex)
Table 2-6 Bytes 5 and 6: ID number
76543210
0-225 (00hex-FFhex)IDnumber,highbyte
0-225 (00hex-FFhex)IDnumber,lowbyte

Diagnostics
8453_en_03 PHOENIX CONTACT 13
Block 2: ID-specific diagnostics
The table shows the faulty local bus devices. “1” is entered for every faulty module.
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 (up to 8 devices per byte). The minimum length of this block is
2 bytes (1 byte header + 1 byte (8 devices, maximum)), the maximum length is 9 bytes
(1 byte header + 8 bytes (63 devices, maximum)). The size of the ID-specific diagnostic
block therefore depends on the number of configured modules.
Block 3: status PDU (device status)
For every local bus device there are 2 bits for status coding:
The specifier (SP) equals 1 in the event of a faulty state. The specifier equals 2 if the module
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 bytes header + 1 byte (4 devices, maximum)), the maximum length is 20 (4 bytes header
+ 16 bytes (63 devices, maximum)). The size of the status PDU block therefore depends on
the number of configured modules.
ST LD x: 00 = module data is valid
ST LD x: 01 = module data is invalid because of an error
ST LD x: 10 = module data is invalid because the wrong module is inserted
ST LD x: 11 = module data is invalid or no module is inserted (despite configuration)
SP: 0 = no evaluation
SP: 1 = error occurs (number > 0)
SP: 2 = error disappears (number = 0)
SP: 3 = reserved

AXL F BK PB
14 PHOENIX CONTACT 8453_en_03
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 error should be considered individually. In order
to display the channel errors, channel-specific diagnostics must be activated on the bus
coupler.
Block 5: revision diagnostics
Indicates the firmware version, e.g., C3hex = version 3
During channel-specific diagnostics only the errors reported by the channel are indicated.
Errors concerning the entire device are not indicated.
IO: 00bin = reserved
IO: 01bin = input
IO: 10bin = output
IO: 11bin = input and output
Channel: channel number of the relevant channel (0 ... 63)
CT: 000bin = reserved
CT: 001bin = 1 bit
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

Diagnostics
8453_en_03 PHOENIX CONTACT 15
Block 6: status PDU
The sixth block is also coded as status PDU.
Assignment of byte 2 to byte 8 corresponds to the assignment for diagnostics in status PDU
format. This is described in Section 2.1.2, “Diagnostics in status PDU format” and can be
used as additional information for blocks 2 and 3, if required.
Bytes 9 to 12 map the diagnostic status register and the diagnostic parameter register of the
local bus.
Byte 13 indicates the number of available modules.
2.1.2 Diagnostics in status PDU format
This diagnostic format consists of the following blocks:
1PROFIBUS standard diagnostics (see also 2.1.1 on page 10)
2Status-PDU (manufacturer-specific)
The bus coupler is always counted as a local bus device (LD). If an error occurs on this
device, the corresponding bits in the diagnostics are set for local bus device 1.
Table 2-7 Status PDU diagnostics including error codes
Byte X Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Meaning
Block 1
1 XXXXX X X XStationstatus1
2 XXXXX X X XStationstatus2
3 XXXXX X X XStationstatus3
4 X X X X X X X X PROFIBUS master address
5000011 0 1ManufacturerID,highbyte(0D
hex)
6110001 0 0ManufacturerID,lowbyte(C4
hex)
Block 2
7000011 0 1Status(header)withblocklength13
8 XXXXX X X XStatustype(81
hex)
9Slot
Slot number of the module with the last
reported error code
10000000SPSPSpecifier
11 X X X X X X X X Error code of byte 1/error type
12 X X X X X X X X Error code of byte 0/error number
13 X X X X X X X X Module ID code, byte 3
14 X X X X X X X X Module ID code, byte 2
15 X X X X X X X X Module ID code, byte 1
16 X X X X X X X X Module ID code, byte 0

AXL F BK PB
16 PHOENIX CONTACT 8453_en_03
Block 2: status PDU
Byte 8: All diagnostics are transmitted as standard status messages.
2.1.3 Diagnostics in identifier-related format
(ID-specific diagnostics)
This diagnostic format consists of the following blocks:
1PROFIBUS standard diagnostics (see also 2.1.1 on page 10)
2ID-specific diagnostics (see also 2.1.1 on page 13)
81hex Standard status message
Byte 11 and byte 12 provide more detailed information on the standard status message:
High byte Error code byte 1 / Error type
Low byte Error code byte 0 / Error number
Unless there is detailed diagnostic information, byte 11 and 12 indicate the error type and
the error number. These correspond to the blinking behavior of the FS and FN LEDs on
the bus coupler.
If further diagnostic information is available, these bytes indicate a specific Axioline F di-
agnostic code.
For detailed information on the Axioline F error codes, please refer to Section 2.2, “Rep-
resenting the error codes”, the documentation of the individual modules, or the
UM DE AXL F SYS DIAG user manual.
Table 2-8 ID-specific (device) diagnostics
Byte X Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Meaning
Block 1
1 XXXXX X X XStationstatus1
2 XXXXX X X XStationstatus2
3 XXXXX X X XStationstatus3
4 X X X X X X X X PROFIBUS master address
5 0 0 0 0 1 1 0 1 Module ID, high byte (0Dhex)
6 1 0 1 1 0 1 0 0 Module ID, low byte (B4hex)
Block 2
7 0 1 X X X X X X Number of devices (values 0 ... 63)
8 X X X X X X X X Modules 1 ... 8 (values 0 ... 255)
9 X X X X X X X X Modules 9 ... 16 (values 0 ... 255)
10 X X X X X X X X Modules 17 ... 24 (values 0 ... 255)
11 X X X X X X X X Modules 25 ... 32 (values 0 ... 255)
12 X X X X X X X X Modules 33 ... 40 (values 0 ... 255)

Diagnostics
8453_en_03 PHOENIX CONTACT 17
2.2 Representing the error codes
2.2.1 Local diagnostic indicators
Figure 2-2 Local diagnostic indicators on the bus coupler
Error type and error number are indicated by flashing codes of the local diagnostic LEDs
(FS and FN LEDs).
13 X X X X X X X X Modules 41 ... 48 (values 0 ... 255)
14 X X X X X X X X Modules 49 ... 56 (values 0 ... 255)
15 X X X X X X X X Modules 57 ... 63 (values 0 ... 127)
Table 2-8 ID-specific (device) diagnostics [...]
For the meaning of the diagnostic indicators, please refer to the module-specific data
sheet.
UL
BF
FS
FN
RDY
D
E

AXL F BK PB
18 PHOENIX CONTACT 8453_en_03
2.2.2 Error type and error number
Error type and error number can be accessed via the status PDU diagnostics.
Table 2-9 Error type and error number (also FS/FN flashing codes)
Error type
(FS ON,
FN flashing)
Error
number
(FS OFF,
FN flashing)
Error cause Error remedy
1Parameter errors on PROFIBUS
1 A parameter block is faulty. The number of modules does not correspond to the
number of parameter blocks or the header byte of the
module parameter is incorrect or the parameter block
is incomplete.
2 Too many data blocks for the
station.
The number of modules does not correspond to the
number of parameter blocks.
3 The data length of the parameter
block is too short.
Check the number of parameters.
4 Reserved
5 The data block length was
exceeded.
Check the number of modules.
6 A parameter block is not
complete.
Check the structure of the parameters for the
modules.
7 The number of parameter blocks
is larger than the maximum
number of modules in the station.
Check the configuration.
8 Reserved
9 Reserved

Diagnostics
8453_en_03 PHOENIX CONTACT 19
2Configuration errors on PROFIBUS
1 Less modules have been
configured than are available in
the station.
Add these modules to the configuration.
2 More modules have been
configured than are available in
the station.
Delete the extra modules from your configuration.
3 Configuration block is faulty. Determine the exact error location using the device-
specific diagnostics in your controller.
4 The device type in the
configuration does not
correspond to that of the module.
Determine the exact error location using the device-
specific diagnostics in your controller. Check the
configuration in the hardware configurator.
5 The configured length does not
correspond to the actual length of
the module.
Determine the exact error location using the device-
specific diagnostics in your controller. Check the
configuration in the hardware configurator.
6 The data length of the
configuration block is faulty.
Check the number of parameters. The parameter
length must not be longer than the output data length
of the relevant module.
7 The PROFIBUS address set is
larger than 126.
Check the PROFIBUS address of the AXL F BK PB.
After the address is set, the bus coupler must be
restarted.
8 More than 244 bytes are required
for the configuration.
Reduce the modules from the station.
Table 2-9 Error type and error number (also FS/FN flashing codes) [...]
Error type
(FS ON,
FN flashing)
Error
number
(FS OFF,
FN flashing)
Error cause Error remedy

AXL F BK PB
20 PHOENIX CONTACT 8453_en_03
3Configuration and parameter errors on the local bus
1 General PDI parameterization
failed.
Check the configuration of the station.
2 Reserved
3 Module error occurred during
initialization.
Try to restart the station.
4 An error occurred in the I/O circuit
(e.g., short circuit or overload at
the actuator).
Remove the error from your I/O devices.
5 Error in the module. Activate channel-specific diagnostics when
parameterizing the bus coupler in your controller and
determine the exact error location and error cause.
6 Reserved
7 More than 63 Axioline F devices
are connected.
Configure the station again and observe the maximum
number of Axioline F devices.
8 Reserved
9 The sum of the process data in the
local bus is greater than 244
bytes.
Check the amount of process data and reduce the
number of devices in the station.
4Local bus error within the station
1 Local bus was stopped. Check the configuration of the station.
Table 2-9 Error type and error number (also FS/FN flashing codes) [...]
Error type
(FS ON,
FN flashing)
Error
number
(FS OFF,
FN flashing)
Error cause Error remedy