Table of Contents
Advertisement
Advertisement
Table of Contents
Related Manuals for Phoenix Contact AXL F BK S3
Summary of Contents for Phoenix Contact AXL F BK S3
- Page 1 Axioline F: Diagnostic registers, and error messges User manual...
- Page 2 User manual Axioline F: Diagnostic registers, and error messges 2016-11-11 Designation: UM EN AXL F SYS DIAG Revision: Order No.: — This manual is valid for: Modules of the Axioline F product group PHOENIX CONTACT 8663_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 constitute 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 observing the applicable standards and regulations.
-
Page 5: Table Of Contents
Diagnostics register of the AXL F BK ... bus coupler ........... 16 Error codes ..........................17 Error codes for user errors................... 17 Error codes for bus diagnostics ................22 Error codes when calling the PDI services............23 Error codes of the I/O modules ................28 8663_en_03 PHOENIX CONTACT... - Page 6 UM EN AXL F SYS DIAG PHOENIX CONTACT 8663_en_03...
-
Page 7: Diagnostics In The Axioline F System
An overview of all main diagnostics and status indicators in the Axioline F system and their meaning can be found in the UM EN AXL F SYS INST user manual: Refer to the module-specific documentation for information on the diagnostics and status indicators on each special module and their meaning. 8663_en_03 PHOENIX CONTACT... -
Page 8: Indicators D And E On Controllers And Bus Couplers
Serious device error at a local bus device (local bus device can no longer be accessed) Green on The bus coupler is ready for operation, communication within the station is OK. All data is valid. There are no faults. PHOENIX CONTACT 8663_en_03... -
Page 9: Indicators D And E On I/O Modules
The device is ready for operation but has lost the connection to the bus head. Not connected Flashing The device is ready for operation but there is no connection to the previously existing device. Power down Device is in (power) reset. E1/E2 Error Error, see module-specific documentation. No error. 8663_en_03 PHOENIX CONTACT... -
Page 10: (Diagstate)
Subindex 3 refers to a channel number. Subindex 3 refers to a group num- ber. Subindex 3 refers to a module number. Other Currently not used. Visible string max. 51 Text Plain text message of the error PHOENIX CONTACT 8663_en_03... - Page 11 Lower priority messages are not indicated if a higher priority message is already pres- ent. The message with the priority 8x is a one-time internal message to the bus coupler or controller that is converted to the error mechanisms of the higher-level system by the bus coupler. 8663_en_03 PHOENIX CONTACT...
-
Page 12: Diagnostic Registers Of The Local Bus Master
Output data is blocked (substitute value behavior is ac- tive) F_FORCE_BIT Force mode Force mode (startup tool/I/O check) is active. F_SYNC_BIT Synchronization Synchronization between higher-level system and local bus master has failed. F_PARA_REQ Module parameter At least one device is requesting parameters. 13 …15 Reserved PHOENIX CONTACT 8663_en_03... - Page 13 If there are I/O warnings from several devices, the warnings are shown in the same way as the I/O errors. After an error has been removed or disappears (e.g., elimination of an interrupt) the bus is started automatically and output data is enabled. The Run indicator bit is set again (F_RUN_BIT = 1). 8663_en_03 PHOENIX CONTACT...
-
Page 14: Diagnostic Parameter Register
The error location is stored as a slot number. This starts at 1 and corresponds to the sequential number of the Axioline F mod- ules that are installed one after another. PHOENIX CONTACT 8663_en_03... -
Page 15: Diagnostics Register Of The Axc
System variables of the diagnostic parameter register System variable Type Meaning AXIO_DIAG_PARAM_REG_HI BYTE Diagnostic parameter register 1 (high byte) AXIO_DIAG_PARAM_REG_LOW BYTE Diagnostic parameter register 1 (low byte) AXIO_DIAG_PARAM_2_REG_HI BYTE Diagnostic parameter register 2 (high byte) AXIO_DIAG_PARAM_2_REG_LOW BYTE Diagnostic parameterregister 2 (low byte) 8663_en_03 PHOENIX CONTACT... -
Page 16: Diagnostics Register Of The Axl F Bk
You can call the diagnostics for the bus coupler and local bus here. When using the Startup+ software: • Right-click on the bus coupler to open the context menu and select the “Diagnostics” menu item. You can call the diagnostics for the station and the individual devices here. PHOENIX CONTACT 8663_en_03... -
Page 17: Error Codes
Use a service that is sup- ported. 0917 Code of failed service Service decoding failed. Restart the device. If the problem still occurs, please contact Phoenix Contact. 0918 Code of the unknown Call of an unknown service code. Check the call. service 0928... - Page 18 0A01 A hardware or firmware error occurred. Restart the device. If the problem still occurs, please contact Phoenix Contact. 0A02 Current status of the A service was called that is not permitted in the current Set the local bus master to local bus master status of the local bus master.
- Page 19 Meaning Remedy (hex) 0A0D A firmware error occurred. Restart the device. If the problem still occurs, please contact Phoenix Contact. 0A18 Invalid Used_Attri- A reserved bit is set in Used_Attributes. Check the parameters. butes parameter 0A19 Number of bus devices The end of the frame was exceeded when accessing the Check the access.
- Page 20 Service (e.g, Create_Configuration) could not be exe- Restart the device. If the cuted due to PDI communication malfunctions (num- problem still occurs, please ber). contact Phoenix Contact. 0A83 Object index Service (e.g, Create_Configuration) could not be exe- Restart the device. If the cuted due to PDI communication malfunctions (error).
- Page 21 A hardware or firmware error occurred. Restart the device. If the problem still occurs, please 0B02 A hardware or firmware error occurred. contact Phoenix Contact. 0B03 A hardware or firmware error occurred. 0B04 A hardware or firmware error occurred. 0B05 Invalid parameters Check the parameters.
-
Page 22: Error Codes For Bus Diagnostics
The process data width of an active device was changed after the configuration frame was connected. 0C14 The module type does not correspond to the configured value. 0C15 The module ID does not correspond to the configured value. PHOENIX CONTACT 8663_en_03... -
Page 23: Error Codes When Calling The Pdi Services
The current object state prevents the service from being executed. Problem with the PDU size Permissible length exceeded. Object cannot be read completely. The service cannot be executed at present. The service contains inconsistent parameters. A parameter has an invalid value. Other error 8663_en_03 PHOENIX CONTACT... - Page 24 Hardware fault Eliminate the hardware error (e.g., I/O voltage not present). Restart the device. If the problem still occurs, please contact Phoenix Contact. Access to object denied Check the call. Access to an invalid address Check the call. Inconsistent object attributes The service used cannot be applied to this ob- ject.
- Page 25 Additional Meaning Remedy (hex) (hex) code Hardware or firmware error Restart the device. If the problem still occurs, please contact Phoenix Contact. Inconsistent parameters Check the parameters. PDI object Invalid parameters Check the parameters. index PDI object Access not supported.
- Page 26 Resource not available; No more resources (memory) available for download. 00A2 Incorrect CRC (checksum) 00A3 Error opening the file (if file system is available) 00A4 Error writing the file (if file system is available) 00A5 Error closing the file (if file system is available) PHOENIX CONTACT 8663_en_03...
- Page 27 Error reading the file (if file system is available). 00A9 Segment number invalid or duplicated (segment ignored). 00B1 The password cannot be replaced (deleted). 00B2 The password cannot be added (too many passwords). 00B3 The password cannot be assigned for the desired type of access. 8663_en_03 PHOENIX CONTACT...
-
Page 28: Error Codes Of The I/O Modules
24 V encoder supply for channel x faulty 5113 Short circuit or overload of the 5 V supply 5120 Cold junction invalid Check the cold junction. 5160 Supply voltage faulty Check the I/O supply. I/O supply overload PHOENIX CONTACT 8663_en_03... - Page 29 Remove the open circuit. Open circuit 8000 Monitoring 8600 Input error of incremental encoder – Check the input signal. – Remove the short circuit. – Connect the sensor. 8910 Overrange – Adapt the range. – Check the wiring. 8920 Underrange 8663_en_03 PHOENIX CONTACT...
- Page 30 Lower-level bus: hardware fault Restart the device. Replace the device if the error still occurs. A042 Lower-level bus: firmware error Check the parameterization of the specified device. A043 Lower-level bus is asynchronous to the higher- level system PHOENIX CONTACT 8663_en_03...
Need help?
Do you have a question about the AXL F BK S3 and is the answer not in the manual?
Questions and answers