Phoenix Contact Axioline F AXC Series User manual

User manual
Axioline F: 
Diagnostic registers, and 
error messges

2016-11-11
PHOENIX CONTACT 8663_en_03
Axioline F: Diagnostic registers, and error messges
UM EN AXL F SYS DIAG
03
—
Modules of the Axioline F product group
User manual
Designation:
Revision:
Order No.:
This 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
automation 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
injury 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
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.
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
information 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
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 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. All information made
available in the technical data is supplied without any accompanying guarantee, whether
expressly mentioned, implied 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.

8663_en_03 PHOENIX CONTACT 5
Table of contents
1 Diagnostics in the Axioline F system ..........................................................................................7
1.1 Local diagnostics and status indicators .................................................................7
1.1.1 Indicators D and E on controllers and bus couplers ...............................8
1.1.2 Indicators D and E on I/O modules .........................................................9
1.2 Diagnostics via object 0018hex (DiagState) ......................................................... 10
1.3 Diagnostic registers of the local bus master ........................................................ 12
1.3.1 Diagnostic status register ..................................................................... 12
1.3.2 Diagnostic parameter register .............................................................. 14
1.4 Diagnostics register of the AXC ... controller .......................................................15
1.5 Diagnostics register of the AXL F BK ... bus coupler ...........................................16
2 Error codes ..............................................................................................................................17
2.1 Error codes for user errors................................................................................... 17
2.2 Error codes for bus diagnostics ........................................................................... 22
2.3 Error codes when calling the PDI services........................................................... 23
2.4 Error codes of the I/O modules ............................................................................ 28

UM EN AXL F SYS DIAG
6PHOENIX CONTACT 8663_en_03

Diagnostics in the Axioline F system
8663_en_03 PHOENIX CONTACT 7
1 Diagnostics in the Axioline F system
Terms used in the document:
The Axioline F modules indicate the errors that occur in different ways:
– About the local diagnostics indicators
– About the diagnostics object 0018hex (DiagState)
– About the diagnostics register of the AXC ... controller
– About the diagnostics registers of the AXL F BK ... bus coupler
1.1 Local diagnostics and status indicators
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.
Diagnostics The diagnostics indicators (red, yellow or green) provide information about the state of the
module and, in the event of an error, provide information about the type and location of the
error. The module is functioning correctly if all of the green LEDs are on.
Status The status indicators (yellow) display the status of the relevant input/output and the con-
nected I/O device.
Extended diagnostics Some modules have extended diagnostics. For example, a short circuit or an overload of
the sensor supply can be detected and reported. If a short circuit occurs at an output, some
output modules can diagnose each channel individually. Information about the supply volt-
age is also reported. Information about I/O errors is sent to the controller with precise details
of the error type and is displayed using status indicators.
Local bus Axioline F local bus
Head of an Axioline F station e.g., Axioline F bus coupler, Axioline F controller
Local bus master Part of the head of the Axioline station that is responsible
for the controller of the Axioline F local bus
Axioline F module Any module of an Axioline F station, 
i. e., head of the Axioline F station or I/O module
The following only considers the LEDs D (diagnostics for local bus communica-
tion) and E (Error).
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.

UM EN AXL F SYS DIAG
8PHOENIX CONTACT 8663_en_03
1.1.1 Indicators D and E on controllers and bus couplers
Figure 1-1 Indicators on controllers and bus couplers
Example: AXC 1050 Example: AXL F BK EIP
LNK ACT
LNK ACT
UL
BF
SF
RUN
D
E
FAIL
DBG
LNK ACT
LNK ACT
UL
NET
MOD
CO
RDY
D
E
PP
Tabelle 2 Indicators on controllers and bus couplers
Des. Color Meaning State Description
DRed/
yellow/
green
Diagnostics for local bus communication
Power off Off The station coupler is in (power) reset.
Ready Yellow on The station is ready for operation, no data exchange taking place.
Ready + Bus
error
Flashing red Local bus error on startup
Possible causes:
– Configuration cannot be generated, information is missing from
a device
– Chip version of a device is <V1.1
– The desired and actual configuration are different
– No local bus device connected
– The maximum number of local bus devices is exceeded.
Active Flashing green The station is ready for operation, communication within the station
is OK.
The data is not valid. Valid data from the controller/higher-level net-
work is not available.
There is no fault in the module.
Active +
Force
Flashing yellow Access from Startup+ in I/O check mode
Flashing yellow/red Local bus error during active I/O check
Active + 
Bus error
Red on The station is ready for operation but has lost connection to at least
one device.
Possible causes:
– Communication error
– Local bus device has been removed or configured device is
missing.
– Reset at a local bus device
– Serious device error at a local bus device (local bus device can
no longer be accessed)
Run Green on The bus coupler is ready for operation, communication within the
station is OK. All data is valid. There are no faults.

Diagnostics in the Axioline F system
8663_en_03 PHOENIX CONTACT 9
1.1.2 Indicators D and E on I/O modules
Figure 1-3 LEDs D and E on the power connectors of the I/O modules
(examples)
E Yellow/
red
Error Yellow on I/O warning at a local bus device.
Red on I/O error at a local bus device.
Off No I/O messages present.
Tabelle 2 Indicators on controllers and bus couplers
Des. Color Meaning State Description
D
UI
E1
E2
D
UO
E1
D
UA
E1
E2
D
UO
E1
Tabelle 4 LEDs D and E on the power connectors of the I/O modules
Designa-
tion
Color Meaning State Description
D Red/yel-
low/green
Diagnostics for local bus communication
Run Green on The device is ready for operation, communication within the station
is OK.
All data is valid. There are no faults.
Active Flashing
green
The device is ready for operation, communication within the station
is OK.
The data is not valid. Valid data from the controller/higher-level net-
work is not available.
There is no fault in the module.
Device applica-
tion not active
Flashing
green/yel-
low
The device is ready for operation, communication within the station
is OK.
Output data cannot be output and/or input data cannot be read.
There is a fault on the I/O side of the module.
Ready Yellow on The device is ready for operation but has still not detected a valid
cycle after power-on.
Connected Flashing
yellow
The device is not (yet) part of the active configuration.
Reset Red on The device is ready for operation but has lost the connection to the
bus head.
Not connected Flashing
red
The device is ready for operation but there is no connection to the
previously existing device.
Power down Off Device is in (power) reset.
E1/E2 Red Error On Error, see module-specific documentation.
Off No error.

UM EN AXL F SYS DIAG
10 PHOENIX CONTACT 8663_en_03
1.2 Diagnostics via object 0018hex (DiagState)
In addition, each I/O module is equipped with object 0018hex (DiagState) that serves the
structured reporting of an error. The I/O module also makes its diagnostics state available.
The object is illustrated in the module-specific documentation of each I/O module.
Table 1-1 Diagnostics state (0018hex: DiagState) (general representation)
0018hex: DiagState (Read)
Subindex Data type Length in
bytes
Meaning Content
0 Record 6 entries Diagnostic state Complete diagnostic information
1 Unsigned 16 2 Error number Unique, consecutive number since the last
power-up reset or the last reset of the diagnos-
tics counter
0 ... 65535dec
2 Unsigned 8 1 Priority 00hex No error
01hex Error
02hex Warning
03hex Information
81hex Error eliminated
82hex Warning eliminated
83hex Information eliminated
3 Unsigned 8 1 Channel/group/mod-
ule
Channel, group or module where the error oc-
curred.
Additional information under “Additional infor-
mation”.
00hex No error
xxhex Channel xx, groupxx or module xx
FFhex Entire device
4 Unsigned 16 2 Error code Error code
5 Unsigned 8 1 Additional Information 00hex Subindex 3 refers to a channel
number.
04hex Subindex 3 refers to a group num-
ber.
08hex Subindex 3 refers to a module
number.
Other Currently not used.
6 Visible string max. 51 Text Plain text message of the error

Diagnostics in the Axioline F system
8663_en_03 PHOENIX CONTACT 11
Table 1-2 Classification of the error messages
Priority Message type Example Note
01hex High Error (fault, alarm) Supply voltage faulty
Parameter table invalid
An error is present, which must be re-
sponded to.
A fault leads e.g., to an activity in the drive,
but does not necessarily require the sys-
tem to be stopped with immediate effect.
02hex Me-
dium
Warning Limit value not reached or ex-
ceeded
Risk of error.
A warning does not require action to be
taken in the device.
03hex Low Information (message,
notification)
General operating message:
10000 operating hours have
elapsed.
General operating message: 10000 oper-
ating hours have elapsed.
Diagnostic object 0018hex is implemented with a storage depth of 1.
This means that:
– A higher priority message overwrites a lower priority message.
– Lower priority messages are not indicated if a higher priority message is already pres-
ent.
The message with the priority 8xhex 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.

UM EN AXL F SYS DIAG
12 PHOENIX CONTACT 8663_en_03
1.3 Diagnostic registers of the local bus master
The errors reported to the local master by the I/O modules are mapped in the diagnostic reg-
isters of the local master.
A local bus master has three diagnostic registers:
– Diagnostic status register:
Operating and error states of the Axioline F local bus
– Diagnostic parameter register 1:
Returns the associated error code in the event of an error
– Diagnostic parameter register 2:
Returns the error location for local bus or I/O errors (device number)
1.3.1 Diagnostic status register
Information on the operating state of the Axioline F local bus is stored in the diagnostic sta-
tus register. Each bit in the diagnostic status register is assigned to a state of the Axioline F
local bus.
The states in the error bits (F_PW_BIT, F_PF_BIT, F_BUS_BIT, F_CTRL_BIT) are de-
scribed in greater detail using the two diagnostic parameter registers.
Table 1-3 Diagnostic status register
Bit Designation Meaning
00 F_PW_BIT I/O warning At least one device indicates an I/O warning.
01 F_PF_BIT I/O error At least one device indicates an I/O error.
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 Configuration is active, PDI to the devices is possible, data exchange
with invalid/non-enabled process data.
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. Output data is blocked (substitute value behavior is ac-
tive)
10 F_FORCE_BIT Force mode Force mode (startup tool/I/O check) is active.
11 F_SYNC_BIT Synchronization Synchronization between higher-level system and local bus master
has failed.
12 F_PARA_REQ Module parameter At least one device is requesting parameters.
13 …15 - Reserved

Diagnostics in the Axioline F system
8663_en_03 PHOENIX CONTACT 13
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 bit 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 = 1, F_ACTIVE_BIT = 1).
In addition the Run indicator bit is set (F_READY_BIT = 1, F_ACTIVE_BIT = 1 and
F_RUN_BIT = 1) when data exchange is started.
Error indicators
The PF, BUS, CTRL, and SYNC 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 indicator bit is reset (F_RUN_BIT = 0).
Further information on the error cause is provided by the two diagnostic parameter regis-
ters.
If several error bits are 1 at the same time, the values in the parameter registers represent
the error with the highest priority.
If there are I/O errors (PF) at 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 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).
Table 1-4 Priorities of the error messages
Message Priority
CTRL 1 (Highest priority)
BUS 2
SYNC 3
PF 4
PW 5 (Lowest priority)

UM EN AXL F SYS DIAG
14 PHOENIX CONTACT 8663_en_03
1.3.2 Diagnostic parameter register
The diagnostic parameter registers are always written to when a fault occurs and whenever
one of the error bits is set (F_PW_BIT, F_PF_BIT, F_BUS_BIT, F_CTRL_BIT). Otherwise,
the diagnostic parameter register has the value 0000hex.
The diagnostic parameter registers provide additional information on the status indicated in
the diagnostic status register when the error bits specified above are set.
The diagnostic parameter register 1 contains the error code. 
An overview of the error codes can be found in Section 2, “Error codes”.
The diagnostic parameter register 2 contains additional information. For localized bus or I/O
errors, this is the error location or the device number. 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.

Diagnostics in the Axioline F system
8663_en_03 PHOENIX CONTACT 15
1.4 Diagnostics register of the AXC ... controller
With the help of the system variables, information on the diagnostic status register of an
AXC ... controller can be read out.
Table 1-5 System variables of the diagnostic status register
System variable Ty p e Meaning
AXIO_DIAG_STATUS_REG_HI BYTE Diagnostic status register (high byte)
AXIO_DIAG_STATUS_REG_LOW BYTE Diagnostic status register (low byte)
AXIO_DIAG_STATUS_REG_PF BOOL I/O error
AXIO_DIAG_STATUS_REG_PW BOOL I/O warning
AXIO_DIAG_STATUS_REG_BUS BOOL Bus error
AXIO_DIAG_STATUS_REG_RUN BOOL Data transmission is active
AXIO_DIAG_STATUS_REG_ACT BOOL Selected configuration is ready to operate
AXIO_DIAG_STATUS_REG_RDY BOOL Axioline F local bus is ready for operation
AXIO_DIAG_STATUS_REG_SYSFAIL BOOL The Axioline F local bus switches to the SYSFAIL state
when the controller is in the STOP state or there is no pro-
gram present on it.
Table 1-6 System variables of the diagnostic parameter register
System variable Ty p e 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)

UM EN AXL F SYS DIAG
16 PHOENIX CONTACT 8663_en_03
1.5 Diagnostics register of the AXL F BK ... bus
coupler
The diagnostic registers of the local bus master can be read via the diagnostic mechanisms
of the higher-level system (see Table 1-7).
Table 1-7 Diagnostics mechanisms of the higher-level systems
Bus coupler Higher-level
system
Diagnostics mechanism See Web-based
Management
AXL F BK PB PROFIBUS Diagnostics in common format, 
block 6, byte 9 ... 12
UM EN AXL F BK PB No
AXL F BK EC EtherCAT®CoE object F100hex: 
Axioline Bus Coupler Diag Info
DB EN AXL F BK EC No
AXL F BK PN ... PROFINET Diagnostic alarms DB EN AXL F BK PN ...
UM EN PROFINET SYS
Yes
AXL F BK ETH ... Ethernet Modbus registers:
Local bus diagnostics:
7997 diagnostic status register
7998 diagnostic status register 1
7999 diagnostic status register 2
I/O diagnostics:
1801 ... 1989 I/O diagnostics of
local bus devices
DB EN AXL F BK ETH ... Yes
AXL F BK EIP ... EtherNet/IP™ Axioline F diagnostics object 
(class code 67hex)
UM EN AXL F BK EIP -
OBJECTS
Yes
AXL F BK S3 Sercos Diagnostics IDNs DB EN AXL F BK S3 No
AXL F BK SAS IEC 61850 Yes
Further options for diagnostics:
For devices with web-based management:
•Open the “Diagnostics” menu item.
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.

Error codes
8663_en_03 PHOENIX CONTACT 17
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
(hex)
Additional code Meaning Remedy
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 service Maximum number of permitted parallel services ex-
ceeded (Processing conflict)
Wait for the service called
previously to be completed,
and then try again.
090A Value transmitted in
Parameter_Count
The number of parameters is inconsistent with the ser-
vice.
The Parameter_Count parameter does not agree with
the number of subsequent words.
Match the number of parame-
ters.
0913 Code of failed service The service called is not supported. 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
service
Call of an unknown service code. Check the call.
0928 An exclusive service was to be executed without the ap-
propriate rights.
Wait for the exclusive 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-
abled
The Variable_ID is not enabled. (Password protection) Check the call.
093A Incorrect Variable_ID Length specification in the Variable_ID is 0 or incorrect. Check the call.

UM EN AXL F SYS DIAG
18 PHOENIX CONTACT 8663_en_03
093B Incorrect Vari-
able_Count
The number of variables has been calculated incor-
rectly.
Check the call.
0A01 A hardware or firmware error occurred. Restart the device. If the
problem still occurs, please
contact Phoenix Contact.
0A02 Current status of the
local bus master
A service was called that is not permitted in the current
status of the local bus master.
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)
Set the local bus master to
the required state.
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 service Maximum number of permitted parallel SM services ex-
ceeded. (Processing conflict)
Wait for the service called
previously to be completed,
and then try again.
0A0C Unknown Variable_ID Call of Set_Value or Read_Value with a Variable_ID that
contains an unknown code.
Check the call.
Table 2-1 Error codes for user errors [...]
Code
(hex)
Additional code Meaning Remedy

Error codes
8663_en_03 PHOENIX CONTACT 19
0A0D A firmware error occurred. Restart the device. If the
problem still occurs, please
contact Phoenix Contact.
0A18 Invalid Used_Attri-
butes parameter
A reserved bit is set in Used_Attributes. Check the parameters.
0A19 Number of bus devices The end of the frame was exceeded when accessing the
configuration or line 0 was accessed.
Check the access.
0 A1 A Invalid Frame_Refer-
ence (if specified)
The frame reference specified for the service does not
exist.
Check the parameters.
0A1C Number of connected
devices
Maximum number of devices exceeded. Reduce the bus configura-
tion.
0A2F 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 I/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 reserved 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 that is
not supported.
Replace the device.
0A74 Device number Device of a manufacturer that is not supported present in
the local bus.
Replace the device.
0A75 Device number Device is indicating a serious error (e. g., faulty EE-
PROM).
Restart the device. If the
problem still occurs, please
contact Phoenix Contact.
0A76 Device number The topology used by the device is not supported by the
master.
Replace the device.
0A77 Device number Error at the interface. Check the connection be-
tween the electronics module
and bus base module.
0A7 A 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-
cuted due to PDI communication malfunctions (timeout).
Restart the device. If the
problem still occurs, please
contact Phoenix Contact.
Table 2-1 Error codes for user errors [...]
Code
(hex)
Additional code Meaning Remedy

UM EN AXL F SYS DIAG
20 PHOENIX CONTACT 8663_en_03
0A82 Object index Service (e.g, Create_Configuration) could not be exe-
cuted due to PDI communication malfunctions (num-
ber).
Restart the device. If the
problem still occurs, please
contact Phoenix Contact.
0A83 Object index Service (e.g, Create_Configuration) could not be exe-
cuted due to PDI communication malfunctions (error).
Restart the device. If the
problem still occurs, please
contact Phoenix Contact.
0A90 Device number Device was selected for synchronization, however it
does not support this.
Select a device that supports
synchronization or change
the selection.
0A91 Device number Device was selected for synchronization, however it
does not support the specified cycle time.
Select a different cycle time
or a different device.
0A92 Device number Device was selected for synchronization, but does not
support the specified value for Input_Delay.
Select a different value for In-
put_Delay or a different de-
vice.
0A93 Device number Device was selected for synchronization, but does not
support the specified value for Output_Delay.
Select a different value for
Output_Delay or a different
device.
0A94 Device number Device was selected for synchronization, but does not
support the specified values for Input_Delay and Out-
put_Delay.
Selected different values for
Input_Delay and Output_De-
lay or a different device.
0AFF Call of Reset_Driver during PDI communication. Restart the device. If the
problem still occurs, please
contact Phoenix Contact.
Table 2-1 Error codes for user errors [...]
Code
(hex)
Additional code Meaning Remedy