4. FUNCTIONS
MELSEC-A
4-17
(c)
When the trouble code = 0200h
For a slave trouble information occurrence (error code = 0200h), the slave trouble
information is stored in the detailed data. The communication trouble area configuration for
this case is shown below. In addition, the expansion communication trouble information is
stored in buffer memory 2096 to 2110 for only the latest trouble information of the error code
= 0200h trouble information. For information regarding the expansion communication trouble
information refer to Section 4.3.2 (6).
Error code = slave trouble information occurrence
Detailed data length = 3
Detailed data 1
Master address (*1)
Slave address (*2)
Detailed data 2
Trouble information
Detailed data 3
Slave ID (*3)
*1
The station address of the master station that controls the slave station in which this trouble
information occurred is stored. However, FFh is stored when the trouble information shows
the exchange with the slave is failed.
*2
The station address of the slave station in which this trouble information occurred is stored.
*3
Individual slave inherent ID No. from the PNO is stored. However, FFh is stored for trouble
information that shows that the exchange with the slave failed.
The trouble information is shown in a 16-bit bit string, and the bits that correspond to the
respective trouble occurrences are set. A description of the error information is given below.
bit
Description
Communi-
cation state
Processing
Setting
station
15
Controlled by another master.
Multiple masters are trying to communicate with the same
slave, so recheck the parameter.
Master
14
The parameter transmitted by the master is
incorrect.
Check the parameter.
Slave
13
The response from the slave is incorrect.
Check the slave or network status.
Master
12
The function requested by the master is not
supported.
Check the slave specifications. Especially if global control is
supported.
Slave
11
Expansion trouble information exists.
Check the slave status. (refer to User's Manual.)
Master
10
The I/O byte size parameter received from the
master does not match that of the slave.
Check the slave parameter.
Slave
9
The slave is not ready to exchange.
This trouble information will always occur at exchange start,
so it can be ignored. If this trouble occurs during exchange,
check the slave status and communication circuit.
Slave
8
Exchange with the slave cannot be conducted.
Check the slave status and communication circuit. And check
the parameter.
Master
7
Separated from the cyclic exchange by the
parameter setting.
This trouble information will always occur at exchange start,
so it can be ignored. Check if the parameter on the network
was changed by a class 2 master.
Master
6
0 (reserved)
Slave
5
The slave has entered the SYNC mode.
(Normal operation)
Slave
4
The slave has entered the FREEZE mode.
(Normal operation)
Slave
3
Watchdog monitoring is being conducted in the
slave.
(Normal operation)
Slave
2
0 (fixed)
Slave
1
Diagnostic data read request.
Check the slave statue.
Slave
0
Parameter allocation request from a slave.
This error information will always occur at exchange start, so it
can be ignored. If this error occurs during exchange, check
the slave status and communication circuit.
Slave
: Exchange continues even if trouble occurs.