beautypg.com

Yaskawa MotionWorks IEC Hardware User Manual

Page 141

background image

MotionWorks IEC Hardware Configuration – 2013-03-26

138

Hex Code

Description

ErrorClass

AxisErrorID

ErrorClass+AxisErrorID output from

MC_ReadAxisError

AlarmID

AlarmID output from Y_ReadAlarm

finished but the event did not occur. Please submit an
SCR.

communication

3403

0200

Invalid EtherNet/IP I/O configuration. Common causes
of invalid configuration include duplicate t2o/o2t
assembly instances or invalid client connection
parameters.

communication

3403

0202

EtherNet/IP remote server unreachable. 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.

communication

3403

0203

EtherNet/IP remote server unreachable. 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.

communication

3403

0204

EtherNet/IP network unreachable. 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.

communication

3403

0205

EtherNet/IP connection refused. Remote server
rejected connection attempt. The remote server may
not be listening for connections or there may be a
firewall preventing the connection.

communication

3403

0206

Too many EtherNet/IP connections. The Ethernet/IP
client ran out of connection slot resources. Reduce the
number of concurrent client connections.

communication

3403

0302

Error connecting to the Modbus TCP slave. 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.

communication

3403

0303

Modbus TCP slave unreachable. 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.