Yaskawa MotionWorks IEC Hardware - Manual (Page 149)

MotionWorks IEC Hardware Configuration – 2013-03-26 146
Hex Code Description
ErrorClass AxisErrorID ErrorClass+AxisErrorID output from
MC_ReadAxisError
AlarmID AlarmID output from Y_ReadAlarm
app 340C 0143 Unknown I/O Driver.
app 340C 0200 Common causes of invalid configuration include
duplicate t2o/o2t assembly instances or invalid client
connection parameters.
app 340C 0202 Unable to connect to the EtherNet/IP remote server.
Common causes include: invalid remote server
address, invalid gateway, invalid subnet mask, or the
Ethernet network is not correctly configured.
app 340C 0203 There is no route to the EtherNet/IP server. Common
causes include: invalid remote server address, invalid
gateway, invalid subnet mask, or the Ethernet network
is not correctly configured.
app 340C 0204 Unable to reach the network for the EtherNet/IP server.
Common causes include: invalid remote server
address, invalid gateway, invalid subnet mask, or the
Ethernet network is not correctly configured.
app 340C 0205 Remote server rejected connection attempt. The
remote server may not be listening for connections or
there may be a firewall preventing the connection.
app 340C 0206 The Ethernet/IP client ran out of connection slot
resources. Reduce the number of concurrent client
connections.
app 340C 0302 Unable to connect to the Modbus TCP slave. Common
causes include: invalid Modbus TCP slave address,
invalid gateway, invalid subnet mask, or the Ethernet
network is not correctly configured.
app 340C 0303 There is no route to the Modbus TCP slave. Common
causes include: invalid Modbus TCP slave address,
invalid gateway, invalid subnet mask, or the Ethernet
network is not correctly configured.
app 340C 0304 Unable to reach the network for the Modbus TCP slave.
Common causes include: invalid Modbus TCP slave
address, invalid gateway, invalid subnet mask, or the
Ethernet network is not correctly configured.
app 340C 0305 Modbus TCP slave rejected connection attempt. The
Modbus TCP slave may not be listening for connections
or there may be a firewall preventing the connection.
app 340C 0306 The Modbus TCP master ran out of connection slot