User manual UM EN AXL F SYS DIAG
Contents
1. Axioline F Diagnostic registers and error messages User manual MN Ww i a m p a e dm p p 4 d 4 b 4 r PHCENIX M di D U teo an D SES EN Ww u 4 I WW CONTACT h 4 INSPIRING INNOVATIONS User manual Axioline F Diagnostic registers and error messages 2013 04 30 Designation UM EN AXL F SYS DIAG Revision 00 Order No This user manual is valid for Modules of the Axioline F product group PHOENIX CONTACT 8663 en 00 Internet Subsidiaries Published by 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 hazards Obey all safety measures that follow this symbol to avoid possible in h This is the safety alert symbol It is used to alert you to potential personal injury 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 which2. if not avoided could result in minor or moderate injury alert the reader to a situation which may cause damage or malfunction to the D This symbol together with the signal word NOTE and the accompanying text device hardware software or surrounding property This symbol and the accompanying text provide the reader with additional in E formation or refer to detailed sources of information How to contact us 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 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 PHOENIX CONTACT GmbH amp Co KG FlachsmarktstraBe 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 tecdoc phoenixcontact com PHOENIX CONTACT Please observe the following notes 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
3. the call length 0F24 Invalid num Invalid number of parameters Check the number of parameters ber of param eters 0F31 Internal error Restart the device If the problem still oc 0F32 curs please contact Phoenix Contact 0F33 8663 en 00 PHOENIX CONTACT 17 Axioline F Diagnostics 2 4 Error codes of the I O modules If there is an error on an I O module the module reports this error to the local bus master li Please refer to the module specific data sheets for the error types that a module reports Table 2 4 Error codes of the I O modules Code Meaning Text Solution hex 2130 Short circuit Short circuit Check the wiring Overload of the analog output or short circuit 2211 Current inside the device no 1 Overload at an input 2344 Overload at an output Short circuit overload of an output 3300 Output voltage Overload or short circuit at the output Output 3400 I O supply voltage failure Check the I O supply 3412 Initiator supply not present VO supply voltage failure 3422 Actuator supply not present 5112 24 V supply Faulty 24 V supply 24 V supply fail Short circuit or overload of the 24 Vsupply 24V supply no 1 24 V supply no 2 5113 5 V supply Short circuit or overload of the 5 V supply 5 V supply no 1 5 V supply no 2 5120 Air supply Cold junction invalid C
4. OBO4 A hardware or firmware error occurred 0B05 Invalid parameters Check the parameters 0B06 Access not supported E g write protection Restart the device If the 0B07 Object does not exist problem still occurs please contact Phoenix Contact OBOC A hardware or firmware error occurred 14 PHOENIX CONTACT 8663_en_00 Error codes 2 2 Error codes for bus diagnostics Table 2 2 Error codes for bus diagnostics Code Additional code Meaning Solution hex OBD1 The bus could not be activated due to bus malfunctions Check the bus configuration OBF1 OBF2 OBF3 0C01 Device number The configured module is not accessible Check the configuration A device present in the configuration frame has been re Adapt the configuration moved from the physical bus structure after the configu frame if the modification was ration frame has been connected done on purpose 0C02 A module has been detected that was not configured An additional device was added at the end of the physi cal bus structure after the configuration frame was con nected 0C11 The module is not located in the configured slot An active device was inserted at the different location of the physical bus structure after the configuration frame was connected 0C12 The module is accessible but was not put into operation due to missing parameters An active device was replaced by an unknown device in the physical bus str
5. al bus master 2 Error codes 2 1 Error codes for user errors 2 2 Error codes for bus diagnostics 2 3 Error codes when calling the PDI services 2 4 Error codes of the I O modules 8663_en_00 PHOENIX CONTACT 5 Axioline F Diagnostics 6 PHOENIX CONTACT 8663_en_00 Diagnostic registers of the Axioline F local bus master 1 Diagnostic registers of the Axioline F local bus master Diagnostic status register Diagnostic parameter register 1 Diagnostic parameter register 2 Terms used in the document Local bus Axioline F local bus Local bus master Head of an Axioline station e g Axioline F bus coupler Axioline F controller All Axioline F modules are provided with diagnostic and status indicators for quick local error diagnostics They enable the clear localization of system errors bus errors or I O errors In addition the module can report various errors to the local bus master which maps them to the diagnostic registers A local bus master has three diagnostic registers The diagnostic status register indicates operating and error states of the local bus master see Table 1 1 Diagnostic status register The first diagnostic parameter register returns the associated error code in the event of an error For possible error codes please refer to Section 2 Error codes The second diagnostic parameter register contains additional information For localized bus or I O errors this is the err
6. he service called ceeded Processing conflict previously to be completed and then try again 090A Value transmitted in The number of parameters is inconsistent with the ser Match the number of parame Parameter_Count vice ters The Parameter_Count parameter does not agree with the number of subsequent words 0913 Code of failed services The service called is not supported Use a service that is sup ported 0918 Code of the unknown Call of an unknown service code Check the call service 0928 An exclusive service was to be executed without the ap Wait for the exclusive rights propriate rights to be enabled 0932 Attempt to pass on the exclusive rights without having these rights 0933 Another node has currently the exclusive rights Wait for the exclusive rights to be enabled 0934 The node already has the exclusive rights 0937 Faulty Variable ID Unknown Variable_ID component Check the call 0938 Reserved Variable ID An internal Variable ID was used Check the call 0939 Variable ID not en The Variable ID is not enabled Password protection Check the call abled O93A Incorrect Variable ID Length specification in the Variable ID is O or incorrect Check the call 093B Incorrect The number of variables has been calculated incor Check the call Variable_Count rectly 8663_en_00 PHOENIX CONTACT 11 Axioline F Diagnostics Table 2 1 Error codes for user e
7. ocessing conflict previously to be completed and then try again OAOC Unknown Variable ID Call of Set Value or Read Value with a Variable ID that Check the call contains an unknown code 12 PHOENIX CONTACT 8663 en 00 Error codes Table 2 1 Error codes for user errors Code Additional code Meaning Solution hex OAOD A firmware error occurred Restart the device If the problem still occurs please contact Phoenix Contact 0A18 Invalid Used Attributes A reserved bit is set in Used Attributes Check the parameters parameter 0A19 Number of bus devices The end of the frame was exceeded when accessing the Check the access configuration or line 0 was accessed 0A1A Invalid The frame reference specified for the service does not Check the parameters Frame Reference exist if specified OA1C Number of connected Maximum number of devices exceeded Reduce the bus configura devices tion OA2F Number of devices is zero Connect the device and check the connection 0A51 A frame reference from 1 to 254 is permitted only Currently the value 1 is per mitted only 0A54 The maximum number of l O points was exceeded Reduce the number of I O points to the maximum num ber To obtain the exact number please refer to the documen tation for your controller 0A60 No configuration frames could be assigned Create the configuration frame 0A70 A reser
8. old Junction Check the cold junction 5160 Supply of I O devices supplied by the de Check the I O supply vice Supply voltage faulty Supply fail 6300 Data record not OK Parameter set faulty Parameter set not ok Check the parameterization of the specified device 6301 Data record no 1 Restart the device Replace the Device error CS FLASH device if the error still occurs 6302 Data record no 2 Device error FO FLASH 18 PHOENIX CONTACT 8663 en 00 Error codes Table 2 4 Error codes of the I O modules Code Meaning Text Solution hex 6320 Parameter error Parameter table invalid Invalid para Check the parameterization of the specified device 7300 Sensor at the device Sensor error Sensor encoder fail Check the sensor 7305 Incremental encoder 1 faulty Encoder error Malfunction of encoder Check the encoder 7610 RAM Receive buffer full Rx Buf full Read the receive buffer 7611 Transmit buffer full Tx Buf full Check the handshake 7620 EPROM device error CS ROM Restart the device Replace the device if the error still occurs 7710 Opencircuit at sensor cable Remove the open circuit Open circuit Open circuit 8600 Positioning controller Input error of the incremental encoder Encoder input signal error Check the input signal Remove the short circuit Connect the sensor 8910 Overrange Overrange 8920 Under
9. or location device number 8663 en 00 PHOENIX CONTACT 7 Axioline F Diagnostics Diagnostic status register A local bus master state is assigned to each bit in the diagnostic status register The states in the error bits F_PF_BIT F_BUS_BIT F_CTRL_BIT are described in greater detail using the two diagnostic parameter registers The diagnostic parameter registers are always writ ten to whenever one of the above error bits is set Otherwise they have the value 0000hex Table 1 1 Diagnostic status register Bit Designation Meaning 00 F PW BIT VO warning pe The device detected a warning at the I Os ripheral warning 01 F PF BIT VO error periph The device detected an I O error peripheral fault eral fault 02 F BUS BIT Bus error A bus error occurred 03 F CTRL BIT Controller error The driver detected an internal error 04 Reserved 05 F RUN BIT Run Data cycles are being exchanged output data is enabled 06 F ACTIVE BIT Active The configuration is active PDI to the devices is possible output data is disabled substitute value behavior 07 F READY BIT Ready The local bus master is ready for operation no data exchange over the bus 08 F BD BIT Bus different A device which does not belong to the current configuration has been detected at the last interface 09 F BASP BIT SYS FAIL The controller is in the STOP state or no application program has been loaded Out
10. put data is blocked substitute value behavior 10 F FORCE BIT Force mode Force mode start up tool is active 11 15 Reserved 8 PHOENIX CONTACT 8663 en 00 Diagnostic registers of the Axioline F local bus master Operating indicators The Ready Active and Run operating indicators show the current state of the system The diagnostic parameter registers are not used After initialization the driver is ready for operation The Ready indicator bus is set F_READY_BIT 1 If the driver has been configured and a configuration frame has been activated without er rors the system indicates it is active The Ready and Active indicator bits are set F READY BIT 2 1 F ACTIVE BIT 1 In addition the Run indicator bit is set F READY 1 F ACTIVE BIT 1 and F RUN BIT 1 when data exchange is started Error indicators The PF BUS and CTRL error indicators report an error PW a warning Errors which are indicated with BUS or CTRL will cause the bus to be disconnected The Run indication bit is reset F RUN 0 Further information on the error cause is provided by the two diagnostic parameter regis ters If several error bits are 1 atthe same time the values in the parameter registers represent the error with the highest priority Table 1 2 Priorities of the error messages Message Priority CTRL 1 Highest priority BUS 2 PF 3 PW 4 Lowest priority If there are I O errors PF a
11. range Underrange Adapt the range Check the wiring Add_Error_Info module errors In diagnostic parameter register 2 the error location is given as Add Error Info for all I O 8663_en_00 PHOENIX CONTACT 19 Axioline F Diagnostics 20 PHOENIX CONTACT 8663_en_00
12. 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 PHOENIX CONTACT Table of contents 1 Diagnostic registers of the Axioline F loc
13. rrors Code Additional code Meaning Solution hex 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 Se the local bus master to the local bus master status of the local bus master reguired state Possible states 0001 Ready After restart or reset 0002 Load Config Configuration cannot be loaded 0004 Config Ready Configuration loaded successfully 0008 Active Configuration frame connected 0010 Param Ready Parameterization of modules completed 0020 Run Process data traffic running 0080 Force Mode Startup tool specifies outputs 0100 Ready Fail Communication abort in Ready 0800 Active Fail Communication abort in Active 1000 Param Ready Fail Communication abort in Ready parameter 2000 Run Fail Process data traffic with subsystem 4000 Force Fail Application timeout for all devices 8000 Force Mode Fail Communication abort in Force Mode 0A03 Memory problem e g buffer too small Restart the device If the problem still occurs please contact Phoenix Contact 0A04 Inconsistent parameters Check the call 0A05 Invalid parameters Check the call 0A06 Access not supported Check the call 0A07 Object does not exist Check the call 0A08 Code of failed services Maximum number of permitted parallel SM services ex Wait for the service called ceeded Pr
14. t or reserved code was used during pa Check the parameterization rameterization XX Number of the affected elements 30 Value is out of range 0801 0000 Error writing the object Check the call 00A2 Error reading the object 16 PHOENIX CONTACT 8663 en 00 Error codes Table 2 3 Error codes when calling the PDI services Code Additional Meaning Solution hex Code hex 0F01 Hardware or firmware error Restart the device If the problem still oc 0F02 curs please contact Phoenix Contact 0F03 0F04 Inconsistent parameters Check the parameters 0F05 PDI object Invalid parameters Check the parameters index 0F06 PDI object Access not supported Check the call index 0F08 PDI object Maximum number of permitted parallel PDI services Wait until the services have been pro index exceeded cessed OFOC Unknown Incorrect variable ID for Set_Value or Read_Value Check the call Variable_ID OFOD Internal error Restart the device If the problem still oc curs please contact Phoenix Contact OF 11 Device not accessible bus error Check the bus configuration 0F12 Device not accessible timeout Check the device 0F21 Invalid device Invalid slot number Check the call number Value is 0 or larger than the maximum number of de vices 0F22 Invalid device Slot is not active Check the call number 0F23 Invalid data Invalid data length Check
15. t several devices the parameter registers show the message that occurred first If this message has been removed the next pending message with the lowest device number is shown If there are peripheral warnings PW from several devices the warnings are shown in the 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 in the default setting The Run indicator bus is set again F RUN 1 8663_en_00 PHOENIX CONTACT 9 Axioline F Diagnostics 10 PHOENIX CONTACT 8663_en_00 Error codes 2 Error codes Problems when calling the firmware services or problems during operation are reported with error codes to determine the exact cause of the error The following sections explain the meanings of the individual codes The code listed in the tables consists of Error Class and Error Code The Additional Code parameter contains a detailed description of the error reason 2 1 Error codes for user errors Table 2 1 Error codes for user errors Code Additional code Meaning Solution hex 0903 Memory problem e g buffer too small Reduce the amount of data 0904 Inconsistent parameters Check the parameters 0905 Invalid parameters Check the parameters 0908 Code of failed services Maximum number of permitted parallel services ex Wait for t
16. ucture after the configuration frame was connected wrong instance ID 0C13 The process data length does not correspond to the configured value 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 8663 en 00 PHOENIX CONTACT 15 Axioline F Diagnostics 2 3 Error codes when calling the PDI services Table 2 3 Error codes when calling the PDI services Code Additional Meaning Solution hex Code hex 0502 Problem with the PDU size Check the call 0031 Permissible length exceeded Object cannot be read completely 0602 00A2 Hardware fault Restart the device If the problem still oc curs please contact Phoenix Contact 0603 0000 Access to object denied Check the call 0605 0000 Inconsistent object attributes 0011 Subindex is not supported 0012 Code is not a reguest 0013 A reserved bit has been used 0014 Subslot is not supported 0015 Read write service type is not supported 0016 Index of Reguest Fetch service does not equal 0000hex 0017 Length for Read or Fetch services does not equal zero 0018 Length does not correspond to the object length which has been read from the EEPROM 0019 Read only object cannot be overwritten 0607 0000 Object does not exist 8000 xx30 A reserved bi
17. ved bit has been set in the Diag Info attribute Check the parameters 0A73 Device number Device present with a chip version in the local bus thatis Replace the device not supported 0A74 Device number Device of a manufacturer thatis not supported presentin Replace the device the local bus 0A7A Invalid Dev Type specified during loading Check the parameters 0A7B Invalid Dev ID specified during loading Check the parameters 0A7C Invalid Dev Length specified during loading Check the parameters 0A81 Object index Service e g Create Configuration could not be exe Restart the device If the cuted due to PDI communication malfunctions timeout problem still occurs please 0A82 Object index Service e g Create Configuration could not be exe Contact Phoenix Contact cuted due to PDI communication malfunctions num ber 0A83 Object index Service e g Create_Configuration could not be exe cuted due to PDI communication malfunctions error OAFF Call of Reset_Driver during PDI communication 8663_en_00 PHOENIX CONTACT 13 Axioline F Diagnostics Table 2 1 Error codes for user errors Code Additional code Meaning Solution hex 0B01 A hardware or firmware error occurred Restart the device If the 0B02 A hardware or firmware error occurred problem still occurs please contact Phoenix Contact OB03 A hardware or firmware error occurred
Download Pdf Manuals
Related Search