Delta AH500 Manual page 425

Code
E8 AH10DNET-5A is initializing.
An error in the modules on the
rack connected to
E9
AHRTU-DNET or the extension
rack error
10.10.3 Software Diagnosis
When ISPSoft is used to read PLC system record, the following error codes may appear.
Error code Description
No slave is configured in
16#A0F1
the scan list
The node address of
AH10DNET-5A is
16#A0F0 repeated in that of other
node or exceeds the valid
range.
Excessively low voltage
16#A0F2
for AH10DNET-5A.
AH10DNET-5A enters the
16#A0F3
test mode.
AH10DNET-5A enters the
16#A0F4
bus-off state.
No power for the
16#A0F5
DeviceNet network is
detected.
Internal storage unit
16#A0F6
errors in AH10DNET-5A
Data exchange unit errors
16#A0F7
in AH10DNET-5A
Sequence number
16#A0F8 detection errors in
AH10DNET-5A
Errors in reading/writing
16#A0F9
the configuration data
The node address of
AH10DNET-5A is
16#A0FA repeated in that of the
slave configured in the
scan list.
The data exchange
16#A0FB between AH10DNET-5A
and AHCPU fails.
Some error occurs in the
slave or in the modules
16#A0FC
on the rack connected to
AHRTU-DNET or the
Ch a pt er 1 0 De v ic eN e t Com m unic at i on Mo d ul e A H 10 DN ET
Indication
Configure the slave in the scan list and then download
the scan list to AH10DNET-5A.
Ensure that the node address of AH10DNET-5A is
unique and repower it after changing its node address.
Check if the work power for AH10DNET-5A and the
AH500 series CPU module is normal.
Switch IN1 from ON to OFF and repower
AH10DNET-5A.
1. Check if the network cable is normal and the
shielded wire has been grounded.
2. Check if the baud rates of all node equipment on the
network are the same.
3. Check if both ends of the network have been
connected with a 121 Ω resistor respectively.
4. Repower AH10DNET-5A.
Make sure that the cable is correctly connected and
check if the network power supply is normal.
If the error still exists after power on again, send your
AH10DNET-5A back to the factory for repair.
If the error still exists after power on again, send your
AH10DNET-5A back to the factory for repair.
If the error still exists after power on again, send your
AH10DNET-5A back to the factory for repair.
If the error still exists after power on again, send your
AH10DNET-5A back to the factory for repair.
Method 1: Reset the node address of AH10DNET-5A,
which must be different from that of the slave
configured in the scan list and then repower it.
Method 2: Do not configure any slave in the scan list.
Download the empty configuration to AH10DNET-5A
by using the "Simulate online" function. Finally, repower
it.
If the error still exists after AH CPU and AH10DNET-5A
are repowered, send your AH10DNET-5A back to the
factory for repair.
1. Check if the node address of the slave has been
changed.
2. Check if the network cable is connected normally in
case it is loose or cut.
How to deal with
If initializing lasts too long, please repower
AH10DNET-5A.
1. Check if the modules on the rack connected
to AHRTU-DNET are normal.
2. Check if the extension rack connected to
AHRTU-DNET is connected normally.
How to deal with
1 0 - 6 3