Others - Delta Electronics AH500 Operation Manual

12.2.7 Others

Error
Description
Code
The original program in the PLC is
16#000F
damaged.
There is no I/O module on a
16#0024
backplane.
The CPU module does not detect a
16#005D
memory card. (SM453)
The memory card is initialized
16#005E
incorrectly. (SM453)
A nonexistent file is read from the
memory card, or a nonexistent file
16#005F
is written to the memory card.
(SM453)
The CPU module can not create a
16#0060 default folder in the memory card.
(SM453)
The capacity of the memory card is
16#0061
not sufficient. (SM453)
The memory card is
16#0062
write-protected. (SM453)
An error occurs when data is
16#0063 written to the memory card.
(SM453)
A file in the memory card can not
16#0064
be read. (SM453)
A file in the memory card is a
16#0065
read-only file. (SM453)
16#1420 The module Ethernet port is off.
There is no interrupt service
16#1801
routine in the CPU module.
16#600A TCP connection failure (SM1090)
16#600B UDP connection failure (SM1091)
C h a p t e r 1 2 Tr o u b l e s h o o t i n g
Solution
After users compile the program again, they can
download the program again.
Please check whether a module exists.
Check whether a memory card is inserted into the CPU
module correctly.
Check whether the memory card breaks down.
Check whether the file path is correct.
Check whether the capacity of the memory card is large
enough, or whether the memory card breaks down.
Check whether the capacity of the memory card is large
enough.
Check whether the memory card is write protected.
Check whether the file path is correct, or whether the
memory card breaks down.
Check whether the file path is correct, or whether the file
is damaged.
Users need to set the file so that the file is not a
read-only file.
Check if the module network cable is connected
correctly.
Check whether there is a corresponding interrupt task
(24V low voltage interrupt service routine) in the
program.
1. Check the actual network configuration, and check
whether the number of TCP connections exceeds the
upper limit supported by the CPU module.
2. Retry the TCP connection later. (This error does not
cause the PLC to stop running. Users can perform the
corresponding remedy by means of the related flag in
the program.)
1. Check the actual network configuration, and check
whether the number of UDP connections exceeds the
upper limit supported by the CPU module.
2. Retry the TCP connection later. (This error does not
cause the PLC to stop running. Users can perform the
corresponding remedy by means of the related flag in
the program.)
1 2 - 2 5