Chapter 8 – Troubleshooting
User Manual
79
Vortex
®
Precedence
Rev 3.6
Error
Class
Error
ID
Description
340C
0135
Error in I/O configuration.
340C
0136
Initializing I/O driver failed.
340C
0137
Board not instantiated.
340C
0138
Board number not allowed.
340C
0139
Input Group doesn't fit.
340C
013A
Output Group doesn't fit.
340C
013B
Board not found.
340C
013C
Error reading inputs.
340C
013D
Error writing outputs.
340C
013E
Error creating I/O semaphore.
340C
013F
Invalid memory size.
340C
0140
Invalid I/O memory address.
340C
0141
Internal PLC Error: PG defined more than once.
340C
0142
POU exceeds 64K module size during insertion. POU size must be reduced.
340C
0143
Internal PLC Error: Error in task configuration.
340C
0143
Unknown I/O Driver.
340C
0200
Common causes of invalid configuration include duplicate t2o/o2t assembly instances or invalid client
connection parameters.
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.
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.
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.
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.
340C
0206
The Ethernet/IP client ran out of connection slot resources. Reduce the number of concurrent client
connections.
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.
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.
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.
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.
340C
0306
The Modbus TCP master ran out of connection slot resources. Reduce the number of concurrent slave
connections.
340C
1020
The controller battery voltage has dropped, indicating it has failed or is about to fail. While the
controller is powered on, the battery should be replaced as soon as possible or a prolonged power-
down state will cause various static data to be lost.
340C
1028
The driver parameter specified in the axis configuration caused an exception
340C
1029
The driver parameter did not match the axis configuration
340C
1111
The move could not be buffered because the motion queue for that axis is full.
340C
1112
The move could not be started because motion is prohibited.
340C
1113
The servo drive failed to enable or disable.
340C
1114
Drive parameter read/write did not complete.
340C
1115
Drive parameter read/write failed
340C
1116
Torque move prohibited while non-torque moves queued or in progress.
340C
111A
The function block cannot command an external axis.
340C
111B
The homing sequence is already in progress.
340C
111C
MC_SetPosition cannot be called while the axis is moving.
340C
111D
Motion aborted due to axis alarm.
340C
111E
MC_SetPosition cannot set the position to be outside the configured wrap range.
340C
111F
Cannot transition to homing state; must be in StandStill state first.
340C
1120
Clear alarms is already in progress.
340C
1121
Axis reset is already in progress.
Summary of Contents for VORTEX PRECEDENCE G1
Page 66: ...Chapter 6 Operation User Manual 60 Vortex Precedence Rev 3 6 Sequence of Operations Flowchart ...
Page 69: ...Chapter 6 Operation User Manual 63 Vortex Precedence Rev 3 6 ...
Page 88: ...Chapter 8 Troubleshooting User Manual 82 Vortex Precedence Rev 3 6 Servo Drive Alarms ...
Page 89: ...Chapter 8 Troubleshooting User Manual 83 Vortex Precedence Rev 3 6 ...
Page 90: ...Chapter 8 Troubleshooting User Manual 84 Vortex Precedence Rev 3 6 ...
Page 91: ...Chapter 8 Troubleshooting User Manual 85 Vortex Precedence Rev 3 6 Servo Drive Warnings ...
Page 104: ...651 Case Karsten Drive Zeeland MI 49464 1 800 324 6205 www extolinc com ...