Phoenix Contact PROFI BUS AXL F BK PB User Manual
  1. Manuals
  2. Brands
  3. Phoenix Contact Manuals
  4. Industrial Equipment
  5. PROFI BUS AXL F BK PB
  6. User manual

Phoenix Contact PROFI BUS AXL F BK PB User Manual

Bus coupler
Hide thumbs
Table of Contents

Advertisement

Quick Links

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

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the PROFI BUS AXL F BK PB and is the answer not in the manual?

Questions and answers

Related Manuals for Phoenix Contact PROFI BUS AXL F BK PB

Summary of Contents for Phoenix Contact PROFI BUS AXL F BK PB

  • Page 1 Diagnostic and firmware functions of the AXL F BK PB bus coupler User manual...
  • Page 2 Diagnostic and firmware functions of the AXL F BK PB bus coupler 2015-06-22 Designation: UM EN AXL F BK PB Revision: This user manual is valid for: Designation Version Order No. AXL F BK PB Hardware 04 or later 2688530 Firmware 2.00 or later PHOENIX CONTACT 8453_en_03...
  • Page 3 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.
  • Page 4 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.

  • Page 5: Table Of Contents

    Summary ..................... 34 Appendix ..........................35 Error codes for acyclic communication ..............35 Error codes for DP/V1 communication..............36 Format of the parameter telegram ............... 37 Object dictionaries ........................41 Slot 0 ........................41 Slots 1 to 63......................46 8453_en_03 PHOENIX CONTACT...
  • Page 6 AXL F BK PB PHOENIX CONTACT 8453_en_03...

  • Page 7: Profibus Bus Coupler

    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 8453_en_03 PHOENIX CONTACT...
  • Page 8 AXL F BK PB PHOENIX CONTACT 8453_en_03...

  • Page 9: Diagnostics

    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 8453_en_03 PHOENIX CONTACT...

  • Page 10: Diagnostics In Common Format

    ST LD 5 Status of local bus devices 5 ... 8 … … … … … … … … … ST LD 63 ST LD 62 ST LD 61 Status of local bus devices 61 ... 63 PHOENIX CONTACT 8453_en_03...
  • Page 11 Error code of byte 1/error type Error code of byte 0/error number Local bus diagnostic status register 1 Local bus diagnostic status register 0 Local bus diagnostic parameter register 1 Local bus diagnostic parameter register 0 Number of accessible local bus devices 8453_en_03 PHOENIX CONTACT...
  • Page 12 Table 2-5 Byte 4: master address 0-125 (00 Master address following parameterization, default address is 255 (FF Table 2-6 Bytes 5 and 6: ID number 0-225 (00 ID number, high byte 0-225 (00 ID number, low byte PHOENIX CONTACT 8453_en_03...
  • Page 13 (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. 8453_en_03 PHOENIX CONTACT...
  • Page 14 ET: 6 = cable break ET: 7 = upper limit value exceeded ET: 8 = lower limit value exceeded ET: 9 = general error Block 5: revision diagnostics Indicates the firmware version, e.g., C3 = version 3 PHOENIX CONTACT 8453_en_03...

  • Page 15: Diagnostics In Status Pdu Format

    Slot reported error code Specifier Error code of byte 1/error type Error code of byte 0/error number Module ID code, byte 3 Module ID code, byte 2 Module ID code, byte 1 Module ID code, byte 0 8453_en_03 PHOENIX CONTACT...

  • Page 16: (Id-Specific Diagnostics)

    Modules 1 ... 8 (values 0 ... 255) Modules 9 ... 16 (values 0 ... 255) Modules 17 ... 24 (values 0 ... 255) Modules 25 ... 32 (values 0 ... 255) Modules 33 ... 40 (values 0 ... 255) PHOENIX CONTACT 8453_en_03...

  • Page 17: Representing The Error Codes

    Local diagnostic indicators on the bus coupler For the meaning of the diagnostic indicators, please refer to the module-specific data sheet. Error type and error number are indicated by flashing codes of the local diagnostic LEDs (FS and FN LEDs). 8453_en_03 PHOENIX CONTACT...

  • Page 18: Error Type And Error Number

    A parameter block is not Check the structure of the parameters for the complete. modules. The number of parameter blocks Check the configuration. is larger than the maximum number of modules in the station. Reserved Reserved PHOENIX CONTACT 8453_en_03...
  • Page 19 Check the PROFIBUS address of the AXL F BK PB. larger than 126. After the address is set, the bus coupler must be restarted. More than 244 bytes are required Reduce the modules from the station. for the configuration. 8453_en_03 PHOENIX CONTACT...
  • Page 20 Check the amount of process data and reduce the local bus is greater than 244 number of devices in the station. bytes. Local bus error within the station Local bus was stopped. Check the configuration of the station. PHOENIX CONTACT 8453_en_03...

  • Page 21: Acyclic Communication (Dp/V1 And Pdi)

    PDI mechanism in the local bus. PDI data from the local bus is then converted into DP/V1 telegrams by the bus coupler. Before programming the application, check whether your controller or configuration tool supports DP/V1. The different communication types will be described in the following. 8453_en_03 PHOENIX CONTACT...

  • Page 22: Acyclic Communication Via The Class 1 Master (C1Master)

    – Device activation – Device diagnostics – Cycle count – Cycle error count – I & M functions – PD OUT – 1 ... 63 PD IN – 1 ... 63 PDI access – 1 ... 63 PHOENIX CONTACT 8453_en_03...
  • Page 23 Structure of the data depending on the service Access Service Data Write objects DP/V1 write request Object data (AXL F BK PB) DP/V1 write response None Read objects DP/V1 read request None (AXL F BK PB) DP/V1 read response Object data 8453_en_03 PHOENIX CONTACT...
  • Page 24 00 should be entered for index low. – <Subindex>: When working with a PDI object, the subindex can be used to select a specific element from an array or record. PHOENIX CONTACT 8453_en_03...
  • Page 25 PDI error code (see “Error codes for DP/V1 communication” on page 36). When accessing PDI, please note the first byte in the DP/V1 data block. PDI read is executed using 06 and PDI write is executed using 07 Set reserved bits to 00 8453_en_03 PHOENIX CONTACT...
  • Page 26 AXL F BK PB PHOENIX CONTACT 8453_en_03...

  • Page 27: Dynamic Configuration

    ® Configuration, e.g., in STEP 7 , is carried out in the same way as for other modular slaves. The configuration can be created from the hardware catalog using drag & drop, see Figure 4-1. 8453_en_03 PHOENIX CONTACT...
  • Page 28 Please note that adjustments to the configuration and actual structure are also carried out for inactive modules. A message is displayed if deactivated modules are connected. Figure 4-3 Module activation/deactivation Following activation/deactivation, the configuration can be saved, translated, and downloaded as usual. PHOENIX CONTACT 8453_en_03...
  • Page 29 Depending on the module type, substitute values (DO and AO) to be output in the event of an error can also be set at this point, for example. Furthermore, inputs (AI) can be parameterized. This is also carried out via the dialog box shown in Figure 4-3. 8453_en_03 PHOENIX CONTACT...

  • Page 30: Principle Of Dynamic Configuration

    (reservation of empty spaces) is also indicated here. Structure: Length of 8 bytes Byte 1 Byte 2 Bytes 3 ... 7 Byte 8 57 58 59 60 61 Bit = 0: module and slot inactive Bit = 1: module and slot active PHOENIX CONTACT 8453_en_03...

  • Page 31: Startup

    Figure 4-4 shows an example of the maximum configuration, as provided. All modules are activated by default. ® Figure 4-4 Configuration in the STEP 7 hardware configurator ® Configure the modules in STEP 7 via the module object properties as usual. In addition, indices 4 and 6 can be accessed. 8453_en_03 PHOENIX CONTACT...

  • Page 32: Options For Specifying The Active Configuration

    Section “Acyclic communication in DP/V1 mode” on page 22. Here, you will find further examples for communication via DP/V1. The individual indices are explained in Section “Slot 0” on page 41. PHOENIX CONTACT 8453_en_03...

  • Page 33: Specifying The Active Configuration Via Dp/V1

    5F 00 06 08 F2 00 00 00 00 00 00 00 Write/Slot/Index/Total length of data/ Length/8 bytes of object data Write response (slave -> master) Data (8 words VC1) Data structure 5F 00 06 08 Write/Slot/Index/Length 8453_en_03 PHOENIX CONTACT...

  • Page 34: Summary

    In this example, the modules have been deactivated with the illustrated services and therefore must not be connected. For additional information and examples regarding communication via DP/V1, please refer to Section “Acyclic communication (DP/V1 and PDI)” on page 21. PHOENIX CONTACT 8453_en_03...

  • Page 35: A Appendix

    I/O voltage not present). hardware fault. Restart the device. If the problem still occurs, please contact Phoenix Contact. 0603 Object access The object has limited It may be a read-only object Check the access rights in the denied access rights.

  • Page 36: A 2 Error Codes For Dp/V1 Communication

    Access to device or index not permitted Invalid parameter (Internal) resource not available Access to the service is not supported Incorrect service code (Internal) timeout when reading (Internal) error when sending a request (Internal) error when receiving a service PHOENIX CONTACT 8453_en_03...

  • Page 37: A 3 Format Of The Parameter Telegram

    0 0: stop local bus in the event of a module failure 1: operate local bus with available modules The data for the configuration and the failsafe value can be found in the module-specific data sheets. 8453_en_03 PHOENIX CONTACT...
  • Page 38 An additional byte is automatically used if the total length of the function block is exceeded. This byte specifies the actual length of the function block. The first byte (header byte for the function blocks) is set to FF After that the function blocks are decoded: PHOENIX CONTACT 8453_en_03...
  • Page 39 Byte x + 2 Reserved (set to 00 Byte x + 3 Index high byte Byte x + 4 Index low byte Byte x + 5 Subindex Byte x + 6 ... x n data bytes + 6 + n 8453_en_03 PHOENIX CONTACT...
  • Page 40 AXL F BK PB PHOENIX CONTACT 8453_en_03...

  • Page 41: B Object Dictionaries

    However, if the activation status is reset during a restart, set bit 3 once following dynamic configuration via index 6. In this way, both options are available: – Restart with original configuration – Restart with last dynamic configuration 8453_en_03 PHOENIX CONTACT...
  • Page 42 Bytes 0, 1: invalid frame counter Bytes 2, 3: coding error counter Bytes 4, 5: frame start error counter Bytes 6, 7: length error counter Bytes 8, 9: CRC error counter Bytes 10, 11: CRC stat error counter PHOENIX CONTACT 8453_en_03...
  • Page 43 Each PROFIBUS device is equipped with an electronic name plate for unique identification. This name plate can be accessed, for example, during startup or for maintenance purposes. Depending on the selected I & M function, either read-only or read/write access is possible. 8453_en_03 PHOENIX CONTACT...
  • Page 44 Access Description Header Manufacturer specification Read AXL F BK PB I & M block MANUFACTURER_ID Read Manufacturer identification Phoenix Contact = 00B0 ORDER_ID Read Order number of the module SERIAL_NUMBER Read Production serial number for clear identification HARDWARE_REVISION Read Hardware revision XXXX...
  • Page 45 Please note that the internal non-volatile memory of the device is accessed when writing to I & M functions I & M1 to I & M4. The memory is designed for a maximum of 100,000 write access operations. 8453_en_03 PHOENIX CONTACT...

  • Page 46: B 2 Slots 1 To 63

    0 ... 128 bytes Index 47: PDI access Function: Read and write PDI data on connected modules via DP/V1 Access: Read and write Length: Depends on the command and PDI object Structure: See Section 3.3, Page 22 and onwards. PHOENIX CONTACT 8453_en_03...

This manual is also suitable for:

2688530

Table of Contents