Controller Alarm ID List
Controller alarm ID list
The following is a list of alarm codes that are reported in the Hardware Configuration's Controller Alarms tab, Y_ReadAlarm, Y_GP_GroupControl, Y_GP_GroupStatus and MC_GroupReadError function blocks, and the webUI. These are non axis specific system alarms.
<insert schematic>
| Hex Code | Description | ||
|---|---|---|---|
| ErrorClass (UINT) | AxisErrorID (UINT) GroupErrorID (UINT) | ErrorClass+AxisErrorID output from MC_ReadAxisError | |
| AlarmID (UDINT) | AlarmID output from Y_ReadAlarm | ||
| system | 1103 | 0102 | The motion kernel scan failed to complete before the next update period. The system update rate must be lowered. |
| system | 1103 | 0103 | An exception occured in the motion kernel scan. Check the debugging log for details. |
| system | 1103 | 0106 | The motion kernel scan experienced an unspecified error. |
| motionKernel | 1201 | 0103 | An alarm task queue was full when a new alarm was posted. This indicates that the task is being starved of execution time or that the system is generating many alarms simultaneously. |
| app | 1407 | 0001 | The file system on which the configuration file directory resides could not be read and may be unmounted or corrupted. The system has booted in a minimal configuration mode, and most functionality is limited. If possible, the file system should be recovered or reformatted and new config files uploaded if applicable. |
| app | 140A | 0009 | Network reset detected multiple Axes connected to the same servo network node. |
| app | 140A | 000A | Network reset detected multiple I/O connected to the same network node. |
| app | 140A | 0015 | Controller memory was corrupted during network reset resulting in a lost logical Axis data structure. |
| app | 140A | 0016 | Controller memory was corrupted during network reset resulting in a lost logical I/O data structure. |
| app | 140A | 0018 | An Abort input specified in the configuration could not be found. The abort condition is considered permanently asserted. No motion is possible until the I/O configuration can be matched to the abort inputs (restart required). |
| app | 140A | 0021 | Too many events were posted from the system ISR. The motion scan and servo net loop have been shut down. |
| app | 140A | 0028 | Too many events occurred in the system without being serviced, and some events were lost. The system is in an undefined state and should be rebooted. |
| app | 140A | 0029 | Too many events occurred in the system without being serviced, and some events were lost. The system is in an undefined state and should be rebooted. |
| app | 140A | 002B | An attempt to store an axis offset to the flash file system failed. The axis offset was not saved and will not persist across the next reboot. |
| system | 2103 | 0104 | The motion kernel scan synchronization timed out. Verify status of the real-time field bus(es) for further diagnostics. |
| system | 2103 | 0105 | The motion kernel scan skipped at least one cycle. Real-time constraints of the system may be exceeded. |
| servoNet | 2301 | 0001 | The drive returned an invalid watch dog code indicating a possible dropped communication packet. |
| servoNet | 2301 | 0005 | Two or more nodes have the same ID. As a result, all servo network communication has been suspended. |
| servoNet | 2301 | 0007 | The servo network communication device failed to initialize. Servo network communication is not possible. |
| servoNet | 2301 | 0008 | An error occurred sending a command to a node during initialization. The node may not be online or may not support the configuration communications rate. |
| servoNet | 2301 | 0015 | Node is not found on network. |
| servoNet | 2301 | 0016 | Invalid node. |
| system | 3103 | 0100 | 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. |
| system | 3103 | 0101 | The file system failed the integral consistency check. Remedy: Power up the controller in supervisor mode using the SUP switch. Clear the alarm. Turn off the SUP switch. Power cycle the controller. |
| motionKernel | 3201 | 0001 | The motion kernel didn't request to enable axis. But, the axis is enabled. |
| motionKernel | 3201 | 0002 | The motion kernel didn't request to disable axis. But, the axis is disabled. |
| motionKernel | 3201 | 0004 | The encoder position stored in SRAM could not be validated. The value has been reset. |
| motionKernel | 3201 | 0005 | Main bus power was disconnected while the axis was enabled. Main power must be restored and this alarm cleared before motion can continue. |
| motionKernel | 3201 | 0006 | A subordinate linked group is in an alarm condition. The subordinate group alarm must be cleared to proceed. |
| motionKernel | 3201 | 0007 | Setting the tool offset failed. Tool offsets are not supported by the installed kinematics package for the axis group, or no package is installed. |
| motionKernel | 3201 | 0101 | Configuration error: multiple alarm tasks with duplicate priority. |
| motionKernel | 3201 | 0102 | Configuration error: Alarm task not configured. Using default priority and name. |
| motionKernel | 3202 | 0001 | The command position was outside the allowable range for the axis in the positive direction (positive overtravel). The axis may not be moved again until the alarm condition is cleared. After the alarm is cleared, it is permissible to execute a move which brings the axis back toward the allowed region, even though the axis is probably still outside the allowed region. Any move which pulls the axis further away from the allowed region will re-trigger the alarm. |
| motionKernel | 3202 | 0002 | The command position was outside the allowable range for the axis in the negative direction (negative overtravel). The axis may not be moved again until the alarm condition is cleared. After the alarm is cleared, it is permissible to execute a move which brings the axis back toward the allowed region, even though the axis is probably still outside the allowed region. Any move which pulls the axis further away from the allowed region will re-trigger the alarm. |
| motionKernel | 3202 | 0003 | The command speed was greater than the allowable range for the axis in the positive direction (overspeed). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0004 | The command speed was greater than the allowable range for the axis in the negative direction (overspeed). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0005 | The command acceleration was greater than the allowable range for the axis in the positive direction. The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0006 | The command acceleration was greater than the allowable range for the axis in the negative direction. The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0007 | The command torque was greater than the allowable range for the axis in the positive direction (overtorque). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0008 | The command torque was greater than the allowable range for the axis in the negative direction (overtorque). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0011 | The command position was outside the allowable range for the axis in the positive direction (positive overtravel). The axis may not be moved again until the alarm condition is cleared. After the alarm is cleared, it is permissible to execute a move which brings the axis back toward the allowed region, even though the axis is probably still outside the allowed region. Any move which pulls the axis further away from the allowed region will re-trigger the alarm. |
| motionKernel | 3202 | 0012 | The command position was outside the allowable range for the axis in the negative direction (negative overtravel). The axis may not be moved again until the alarm condition is cleared. After the alarm is cleared, it is permissible to execute a move which brings the axis back toward the allowed region, even though the axis is probably still outside the allowed region. Any move which pulls the axis further away from the allowed region will re-trigger the alarm. |
| motionKernel | 3202 | 0013 | The command speed was greater than the allowable range for the axis in the positive direction (overspeed). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0014 | The command speed was greater than the allowable range for the axis in the negative direction (overspeed). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0015 | The command acceleration was greater than the allowable range for the axis in the positive direction. The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0016 | The command acceleration was greater than the allowable range for the axis in the negative direction. The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0017 | The command torque was greater than the allowable range for the axis in the positive direction (overtorque). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0018 | The command torque was greater than the allowable range for the axis in the negative direction (overtorque). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0021 | The command position was outside the allowable range for the axis in the positive direction (positive overtravel). The axis may not be moved again until the alarm condition is cleared. After the alarm is cleared, it is permissible to execute a move which brings the axis back toward the allowed region, even though the axis is probably still outside the allowed region. Any move which pulls the axis further away from the allowed region will re-trigger the alarm. |
| motionKernel | 3202 | 0022 | The command position was outside the allowable range for the axis in the negative direction (negative overtravel). The axis may not be moved again until the alarm condition is cleared. After the alarm is cleared, it is permissible to execute a move which brings the axis back toward the allowed region, even though the axis is probably still outside the allowed region. Any move which pulls the axis further away from the allowed region will re-trigger the alarm. |
| motionKernel | 3202 | 0023 | The command speed was greater than the allowable range for the axis in the positive direction (overspeed). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0024 | The command speed was greater than the allowable range for the axis in the negative direction (overspeed). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0025 | The command acceleration was greater than the allowable range for the axis in the positive direction. The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0026 | The command acceleration was greater than the allowable range for the axis in the negative direction. The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0027 | The command torque was greater than the allowable range for the axis in the positive direction (overtorque). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0028 | The command torque was greater than the allowable range for the axis in the negative direction (overtorque). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 3202 | 0031 | The move specified would exceed the software position limits in the positive direction and was rejected before being started. The group may be moved again immediately if desired. |
| motionKernel | 3202 | 0032 | The move specified would exceed the software position limits in the negative direction and was rejected before being started. The group may be moved again immediately if desired. |
| motionKernel | 3202 | 0033 | The move specified would exceed the software speed limits in the positive direction and was rejected before being started. The group may be moved again immediately if desired. |
| motionKernel | 3202 | 0034 | The move specified would exceed the software speed limits in the negative direction and was rejected before being started. The group may be moved again immediately if desired. |
| motionKernel | 3202 | 0035 | The move specified would exceed the software acceleration limits in the positive direction and was rejected before being started. The group may be moved again immediately if desired. |
| motionKernel | 3202 | 0036 | The move specified would exceed the software acceleration limits in the negative direction and was rejected before being started. The group may be moved again immediately if desired. |
| motionKernel | 3202 | 0037 | The move specified would exceed the software torque limits in the positive direction and was rejected before being started. The group may be moved again immediately if desired. |
| motionKernel | 3202 | 0038 | The move specified would exceed the software torque limits in the negative direction and was rejected before being started. The group may be moved again immediately if desired. |
| motionKernel | 3202 | 0039 | The predictive soft limit encountered a segment that doesn't support the predicted stopping point. |
| motionKernel | 3202 | 0041 | Cam and Contour tables must have a header indicating the number of rows and colums and a feed forward velocity flag. Comma seperated data values following the header. |
| motionKernel | 3202 | 0042 | In CamTables, the first (master) column must be either increasing or decreasing. |
| motionKernel | 3202 | 0043 | In ContourTables, the first (time) column must start at zero and be increasing. |
| motionKernel | 3202 | 0044 | The master postion was outside the range of the CamTable, which automatically stopped the cam motion. |
| motionKernel | 3202 | 0045 | One one or more slave axes could not attain the target postion and velocity within the user specified time limit for the Cam or Gear motion. |
| motionKernel | 3202 | 0046 | One one or more slave axes could not attain the target postion and velocity within the user specified distance limit for the Cam or Gear motion. |
| motionKernel | 3202 | 0051 | Axis enable failed. This problem is usually a result of communication problems with the servo drive. |
| motionKernel | 3202 | 0052 | Runtime computation detected an invalid motion parameter. |
| motionKernel | 3202 | 0053 | Runtime computation detected jerk limit too low to allow correction for off-axis motion. |
| motionKernel | 3202 | 0054 | Runtime computation detected acceleration limit too low to allow correction for off-axis motion. |
| motionKernel | 3202 | 0056 | Off-axis initial conditions correction was not able to complete before the main motion profile ended, leading to a discontinuity in velocity. This can happen if the motion planning computations are not adequate for short moves in cross-frame transitions. |
| motionKernel | 3202 | 0100 | The inverse kinematics computation detected a world position that can not be reached. |
| motionKernel | 3202 | 0101 | The inverse kinematics computation detected that the elbow 'handedness' (orientation) does not match the configuration. The 'handedness' must be fixed by commanding the individual axes or manually moving the robot. |
| motionKernel | 3202 | 0102 | The robot XY position intruded into the configured dead zone area near the origin. |
| motionKernel | 3202 | 0103 | A valid command velocity is required for inverse kinematics computation of Scara robots when near the singularity. Choose a different motion type which includes valid command velocity generation. |
| motionKernel | 3202 | 0104 | The solution for Scara inverse kinematics requires that any motion very near the singularity be continuous. Coming to a stop very near the singularity can cause a sudden position jump in subsequent motions. This region is controlled with the configuration parameter 'correctionRadius'. |
| motionKernel | 3202 | 0105 | The axis group has been misconfigured with too few axes or too small a world coordinate space to satisfy the dimensionality of the kinematics. |
| motionKernel | 3202 | 0106 | The commanded motion generated elbow values that lie within the configured 'outerSingularInterpRange', and the orthogonality check between the direciton of motion and the singular direction was not within the configured 'singularityOrthogonalityTolerance' |
| motionKernel | 3202 | 0107 | The kinematics algorithm encountered an unexpected error |
| motionKernel | 3202 | 0108 | The kinematics solution produced angles outside the allowable range |
| motionKernel | 3202 | 0109 | Inverse kinematics is not supported when at the singularity configuration. |
| motionKernel | 3202 | 010A | Inverse kinematics encountered an error resolving the mechanism joint configuration. Some joints may be outside the ranges allowed for the device. |
| motionKernel | 3202 | 010B | A configured kinematics parameter has a value which is not supported or is outside the supported range. |
| motionKernel | 3202 | 010C | The kinematics configuration data in group.xml is not supported by the model. |
| motionKernel | 3202 | 010D | The specified tool offset or tool plate offset contained values which are not supported by the kinematics package. |
| motionKernel | 3202 | 010E | The specified tool offset or tool plate offset vector size did not match the size of the kinematics model. |
| motionKernel | 3202 | 0200 | The axis group split-axis command data did not agree. The component axes must be moved to identical locations separately before issuing multi-axis commands. |
| servoNet | 3301 | 0009 | Some motor properties, such as encoder resolution, maximum speed, and maximum torque, could not be determined for the attached motor. The serial encoder may be malfunctioning, incorrectly programmed, or unplugged. |
| servoNet | 3301 | 000D | The servo network does not support this motion control mode. |
| servoNet | 3301 | 0018 | The command position specified an instantaneous jump too large relative to the current position. |
| servoNet | 3301 | 001A | An error occurred while initializing a node. |
| servoNet | 3301 | 0022 | The drive has lost synchronous communication with the controller. Reset the communication to continue. |
| servoNet | 3301 | 002D | The servo identification process failed. |
| servoNet | 3303 | 0000 | The base code for Sigma drive alarms. The drive's alarm value is bitwise OR'd in with this base value. |
| servoNet | 3303 | 0020 | EEPROM data of SERVOPACK is incorrect |
| servoNet | 3303 | 0021 | The data of the parameter in the SERVOPACK is incorrect. |
| servoNet | 3303 | 0022 | The data of the parameter in the SERVOPACK is incorrect. |
| servoNet | 3303 | 0023 | The data of the parameter in the SERVOPACK is incorrect. |
| servoNet | 3303 | 0024 | An internal program error occurred in the SERVOPACK |
| servoNet | 3303 | 0025 | An internal program error occurred in the SERVOPACK |
| servoNet | 3303 | 002A | FlashROM data of SERVOPACK is incorrect |
| servoNet | 3303 | 002B | The data of the parameter in the SERVOPACK is incorrect. |
| servoNet | 3303 | 0030 | Detection data for power circuit is incorrect. |
| servoNet | 3303 | 0040 | The parameter setting is outside the allowable setting range. |
| servoNet | 3303 | 0041 | The PG dividing pulse setting (Pn212) is outside the allowable setting range or does not satisfy the setting conditions |
| servoNet | 3303 | 0042 | The combination of some parameters exceeds the setting range |
| servoNet | 3303 | 0044 | The settings of the Option Module and Pn002.4 (External Encoder Usage) do not match. Pn00E.4 ≠ 0 and Pn002.4 ≠ 0, or Pn00E.4 ≠ 0 and feedback option module not attached. |
| servoNet | 3303 | 0046 | An error was detected in the SigmaLINK II response data or SigmaLINK II command data settings. |
| servoNet | 3303 | 0047 | The SERVOPACK was connected to an encoder with functional safety. |
| servoNet | 3303 | 004A | The parameter setting is outside the allowable setting range. |
| servoNet | 3303 | 0050 | SERVOPACK and servomotor capacities do not match each other. |
| servoNet | 3303 | 0051 | The device unsupported was connected. |
| servoNet | 3303 | 0070 | The connected motor is a different type of motor from the previously connected motor. |
| servoNet | 3303 | 0080 | The initial value (0um) is set for the linear scale pitch (Pn282) |
| servoNet | 3303 | 00B0 | The servo ON command (SV_ON) was sent from the host controller after executing a utility function that turns ON servomotor. |
| servoNet | 3303 | 0100 | An overcurrent flowed through the IGBT. Heat sink of SERVOPACK was overheated. |
| servoNet | 3303 | 0101 | The current to the motor exceeded the allowable current |
| servoNet | 3303 | 0102 | The current to the motor exceeded the allowable current. |
| servoNet | 3303 | 0231 | The built-in brake relay malfunctioned. |
| servoNet | 3303 | 0232 | The number of built-in brake relay operations exceeded the service life of the relay. |
| servoNet | 3303 | 0300 | Regenerative circuit and/or resistor is faulty. |
| servoNet | 3303 | 0320 | Regenerative energy exceeds regenerative resistor capacity. |
| servoNet | 3303 | 0330 | The power supply to the main circuit does not match the parameter Pn001 setting. |
| servoNet | 3303 | 0400 | Main circuit DC voltage is excessively high. |
| servoNet | 3303 | 0410 | Main circuit DC voltage is excessively low. |
| servoNet | 3303 | 042A | One of the following was detected by the converter. 1. An operation error occurred when using the limit relay for inrush current 2. PN voltage error 3. Regeneration operation error 4. The converter's heat sink overheated 5. An operation error occurred when using the converter and fan 6. SR200 converter control slot error (an axis has been detected other than the converter control axis) |
| servoNet | 3303 | 044A | A CPS Power error has been detected. This is issued when an overcurrent, overvoltage, and undervoltage for each of the CPS power outputs, as well as CPS power board temperature error has been detected. |
| servoNet | 3303 | 0450 | The capacitor of the main circuit has deteriorated or is faulty. |
| servoNet | 3303 | 0510 | Rotational speed of the motor is excessively high. |
| servoNet | 3303 | 0511 | The motor speed upper limit of the set PG dividing pulse (Pn212) was exceeded. |
| servoNet | 3303 | 0520 | Abnormal vibration at the motor speed was detected. |
| servoNet | 3303 | 0521 | Vibration was detected while performing tuning-less function. |
| servoNet | 3303 | 0550 | The setting value of Pn385 exceeds the motor maximum speed |
| servoNet | 3303 | 0710 | The motor was operating for several seconds to several tens of seconds under a torque largely exceeding ratings. |
| servoNet | 3303 | 0720 | The motor was operating continuously under a torque largely exceeding ratings. |
| servoNet | 3303 | 0729 | A continuous load that exceeds the SERVOPACK rating was applied. |
| servoNet | 3303 | 0730 | When the dynamic brake was applied, rotational energy exceeded the capacity of dynamic brake resistor. |
| servoNet | 3303 | 0731 | When the dynamic brake was applied, rotational energy exceeded the capacity of dynamic brake resistor. |
| servoNet | 3303 | 0740 | The main circuit power was frequently turned ON and OFF. |
| servoNet | 3303 | 07A0 | The heat sink of SERVOPACK overheated. |
| servoNet | 3303 | 07A1 | The surrounding temperature of the control PCB is abnormal |
| servoNet | 3303 | 07A2 | The surrounding temperature of the power PCB is abnormal |
| servoNet | 3303 | 07A3 | An error occurred in the temperature sensor circuit |
| servoNet | 3303 | 07A4 | The surrounding temperature of the converter PCB is abnormal. |
| servoNet | 3303 | 07AB | The fan inside the SERVOPACK stopped. |
| servoNet | 3303 | 0810 | All the power supplies for the absolute encoder have failed and position data was cleared. |
| servoNet | 3303 | 0820 | The checksum results of encoder memory is incorrect. |
| servoNet | 3303 | 0830 | Backup battery voltage for the absolute encoder has dropped. |
| servoNet | 3303 | 0840 | Data in the encoder is incorrect. |
| servoNet | 3303 | 0850 | The encoder was operating at high speed when the power was turned ON |
| servoNet | 3303 | 0860 | The internal temperature of encoder is too high |
| servoNet | 3303 | 0861 | The internal temperature of motor is too high |
| servoNet | 3303 | 0862 | The input voltage (temperature) for the overheat protection input (TH) signal exceeded the setting of Pn61B (261Bh) (Overheat Alarm Level). |
| servoNet | 3303 | 0870 | Checksum result error of encoder memory. |
| servoNet | 3303 | 0880 | Encoder internal data was incorrect. |
| servoNet | 3303 | 0890 | A failure occurred in the linear encoder |
| servoNet | 3303 | 0891 | An error occurred in the linear encoder |
| servoNet | 3303 | 08A0 | Linear encoder is faulty. |
| servoNet | 3303 | 08A1 | Linear encoder or serial converter unit is faulty. |
| servoNet | 3303 | 08A2 | Linear encoder is faulty. |
| servoNet | 3303 | 08A3 | Encoder feedback position is faulty. |
| servoNet | 3303 | 08A5 | An overspeed error occurred in the external encoder |
| servoNet | 3303 | 08A6 | An overheating error occurred in the external encoder |
| servoNet | 3303 | 0A10 | The SERVOPACK and Sync0 events cannot be synchronized |
| servoNet | 3303 | 0A11 | The EtherCAT AL does not move to the Operational state when the DS402 drive is in Operation Enabled state |
| servoNet | 3303 | 0A12 | The process data reception events and Sync0 events cannot be synchronized. (Process data communications failed.) |
| servoNet | 3303 | 0A20 | A parameter setting exceeds the setting range |
| servoNet | 3303 | 0A40 | Initialization failed when the power supply was turned ON |
| servoNet | 3303 | 0A41 | An error occurred during ESC initialization |
| servoNet | 3303 | 0A47 | Loading SERVOPACK information failed |
| servoNet | 3303 | 0A48 | A checksum error occurred in the EEPROM |
| servoNet | 3303 | 0B10 | The A/D converter for reference speed input is faulty. |
| servoNet | 3303 | 0B11 | A/D converstion data of speed reference is incorrect. |
| servoNet | 3303 | 0B20 | The A/D converter for reference torque input is faulty. |
| servoNet | 3303 | 0B31 | Phase-U current sensor is faulty. |
| servoNet | 3303 | 0B32 | Phase-V current sensor is faulty. |
| servoNet | 3303 | 0B33 | Phase-W current sensor is faulty. |
| servoNet | 3303 | 0B6A | ASIC error occurred in the MECHATROLINK communications. |
| servoNet | 3303 | 0B6B | ASIC error occurred in the MECHATROLINK communications. |
| servoNet | 3303 | 0BE0 | An internal program error occurred in the SERVOPACK. |
| servoNet | 3303 | 0BE2 | A firmware error occurred in the SERVOPACK. |
| servoNet | 3303 | 0BF0 | "Internal program error 0" of SERVOPACK occurred. |
| servoNet | 3303 | 0BF1 | "Internal program error 1" of SERVOPACK occurred. |
| servoNet | 3303 | 0BF2 | "Internal program error 2" of SERVOPACK occurred. |
| servoNet | 3303 | 0BF3 | "Internal program error 3" of SERVOPACK occurred. |
| servoNet | 3303 | 0BF4 | "Internal program error 4" of SERVOPACK occurred. |
| servoNet | 3303 | 0BF5 | Internal program error 5 occurred in the SERVOPACK. |
| servoNet | 3303 | 0BF6 | Internal program error 6 occurred in the SERVOPACK. |
| servoNet | 3303 | 0BF7 | Internal program error 7 occurred in the SERVOPACK. |
| servoNet | 3303 | 0BF8 | Internal program error 8 occurred in the SERVOPACK. |
| servoNet | 3303 | 0BFB | An internal program error B occurred in the SERVOPACK. |
| servoNet | 3303 | 0BFD | An internal program error D occurred in the SERVOPACK. |
| servoNet | 3303 | 0C10 | The servomotor ran out of control. |
| servoNet | 3303 | 0C20 | The electric angle error of U-phase hall signal rising edge exceeds +/- 30 degrees. |
| servoNet | 3303 | 0C21 | All of U, V, and W-phase of hall sensor signal are H level or L level. |
| servoNet | 3303 | 0C22 | The phase information does not match. |
| servoNet | 3303 | 0C50 | Failed to detect the polarity position of linear servomotor. |
| servoNet | 3303 | 0C51 | An overtravel signal was detected during polarity detection. |
| servoNet | 3303 | 0C52 | The servomotor was turned ON under the condition of polarity detection uncompleted. |
| servoNet | 3303 | 0C53 | The moving distance exceeded the set value of Pn48E during polarity detection. |
| servoNet | 3303 | 0C54 | The polarity detection failed. |
| servoNet | 3303 | 0C80 | The multi-turn for the absolute encoder was not properly cleared or set. |
| servoNet | 3303 | 0C90 | Communication between SERVOPACK and encoder is not possible. |
| servoNet | 3303 | 0C91 | An encoder position data calculation error occurred. |
| servoNet | 3303 | 0C92 | An error occurred in the communications timer between the encoder and the SERVOPACK. |
| servoNet | 3303 | 0CA0 | Encoder parameters are faulty. |
| servoNet | 3303 | 0CB0 | Contents of communications with encoder is incorrect. |
| servoNet | 3303 | 0CC0 | Different multi-turn limits have been set in the encoder and SERVOPACK. |
| servoNet | 3303 | 0CD1 | A configuration that cannot be connected with SigmaLINK II was detected. |
| servoNet | 3303 | 0CD2 | An error occurred in the power system of the SigmaLINK II connection. |
| servoNet | 3303 | 0CD3 | Saving the configuration data failed. |
| servoNet | 3303 | 0CD4 | The content saved in the configuration and the content detected in node detection are different. |
| servoNet | 3303 | 0CD7 | An error occurred in communications with the SigmaLINK II I/O device. |
| servoNet | 3303 | 0CD8 | The SigmaLINK II I/O device detected an error. |
| servoNet | 3303 | 0CF1 | Communication of fully-closed serial converter unit is faulty. |
| servoNet | 3303 | 0CF2 | Communication of fully-closed serial converter unit is faulty |
| servoNet | 3303 | 0D00 | The setting of Pn520 (Excessive Position Deviation Alarm Level) was exceeded by the position deviation while the servo was ON. |
| servoNet | 3303 | 0D01 | The servo was turned ON after the position deviation exceeded the setting of Pn526 (Excessive Position Deviation Alarm Level at Servo ON) while the servo was OFF. |
| servoNet | 3303 | 0D02 | If position deviation remains in the deviation counter, the setting of Pn529 or Pn584 (Speed Limit Level at Servo ON) limits the speed when the servo is turned ON. This alarm occurs if a position reference is input and the setting of Pn520 (Excessive Position Deviation Alarm Level) is exceeded before the limit is cleared. |
| servoNet | 3303 | 0D04 | Overtravel was detected while the servo was ON. |
| servoNet | 3303 | 0D10 | There was too much position deviation between the motor and load during fully-closed loop control. |
| servoNet | 3303 | 0D30 | The position feedback data exceeded ±1,879,048,192 [Linear encoder pulse units] |
| servoNet | 3303 | 0E00 | Communications I/F Error 0 of SERVOPACK occurred. |
| servoNet | 3303 | 0E01 | Communications I/F Error 1 of SERVOPACK occurred. |
| servoNet | 3303 | 0E02 | Communications I/F Error 2 of SERVOPACK occurred. |
| servoNet | 3303 | 0E03 | There is an error in the communications data between the SERVOPACK and the EtherCAT Module |
| servoNet | 3303 | 0E07 | Communications I/F Error 7 of SERVOPACK occurred. |
| servoNet | 3303 | 0E11 | The statuses of channel A1 and A2 did not match within the specified time. [ASM-7 only] - Pulse error due to open line or short circuit on Input A. |
| servoNet | 3303 | 0E12 | The statuses of channel A1 and A2 did not match within the specified time. [ASM-7 only] - Pulse error due to open line or short circuit on Input B. |
| servoNet | 3303 | 0E13 | The statuses of channel A1 and A2 did not match within the specified time. [ASM-7 only] - Pulse error due to open line or short circuit on Input C. |
| servoNet | 3303 | 0E14 | The statuses of channel A1 and A2 did not match within the specified time. [ASM-7 only] - Pulse error due to open line or short circuit on Input D. |
| servoNet | 3303 | 0E15 | The statuses of channel A1 and A2 did not match within the specified time. [ASM-7 only] - Pulse error due to open line or short circuit on Input E. |
| servoNet | 3303 | 0E16 | The statuses of channel A1 and A2 did not match within the specified time. [ASM-7 only] - Pulse error due to open line or short circuit on Input F. |
| servoNet | 3303 | 0E1F | An alarm occurred for a safety module that was not registered in the SERVOPACK. |
| servoNet | 3303 | 0E28 | An error occurred in FSoE communications. The FSoE communications state has become a state other than Data. |
| servoNet | 3303 | 0E29 | Receiving encoder data failed. |
| servoNet | 3303 | 0E2A | Absolute position tolerance between motor encoder and external encoder exceeded. |
| servoNet | 3303 | 0E2B | The deviation between redundant encoders exceeded the specified value. |
| servoNet | 3303 | 0E2C | Analog values (0-10 V) on port F exceed allowed channel tolerance. |
| servoNet | 3303 | 0E2D | There is no homing position stored in the safety module. The requested safety function needs a homing position. |
| servoNet | 3303 | 0E2F | FSoE initialization error. |
| servoNet | 3303 | 0E33 | The internal supply voltage monitoring detected an error. |
| servoNet | 3303 | 0E34 | The test of the external I/O connection failed. |
| servoNet | 3303 | 0E35 | The alarm status between CPUs did not match. |
| servoNet | 3303 | 0E36 | An anomaly occurred in the internal temperature of the safety module. |
| servoNet | 3303 | 0E3A | An error occurred in the safety module EEPROM. |
| servoNet | 3303 | 0E3B | An error occurred in contents of the encoder communications data. |
| servoNet | 3303 | 0E3C | The statuses between CPUs in the safety module do not match. |
| servoNet | 3303 | 0E3E | The statuses of SBC ssafe output and the feedback signal did not match within the specified time. |
| servoNet | 3303 | 0E40 | Transmission cycle setting of MECHATROLINK is incorrect. |
| servoNet | 3303 | 0E41 | The Setting of the MECHATROLINK communications data size is incorrect. |
| servoNet | 3303 | 0E42 | The Setting of the MECHATROLINK station address is incorrect. |
| servoNet | 3303 | 0E50 | Synchronization error during MECHATROLINK communications. |
| servoNet | 3303 | 0E51 | Synchronization error during MECHATROLINK communications. |
| servoNet | 3303 | 0E60 | Continuous communications error during MECHATROLINK communications. |
| servoNet | 3303 | 0E61 | Transmission cycle error during MECHATROLINK communications. |
| servoNet | 3303 | 0E62 | Communications error occurs continuously during MECHATROLINK communications. |
| servoNet | 3303 | 0E63 | Synchronization frames are not received continuously during MECHATROLINK communications. |
| servoNet | 3303 | 0E71 | Detection of the safety module failed. |
| servoNet | 3303 | 0E72 | Detection of the Feedback Option Module failed. |
| servoNet | 3303 | 0E74 | An unsupported safety module was connected to the SERVOPACK. |
| servoNet | 3303 | 0E75 | An unsupported feedback option module was connected. |
| servoNet | 3303 | 0E78 | DOA is not opperating correctly. |
| servoNet | 3303 | 0E79 | DOB is not opperating correctly. |
| servoNet | 3303 | 0E7A | DOC is not opperating correctly. |
| servoNet | 3303 | 0E7B | DOD is not opperating correctly. |
| servoNet | 3303 | 0E7C | DOE is not opperating correctly. |
| servoNet | 3303 | 0E80 | An error occurred in the system of the safety module. |
| servoNet | 3303 | 0E81 | A safety module of a different model than the previous safety module was connected to the SERVOPACK. |
| servoNet | 3303 | 0E82 | The settings of the safety functions do not conform to the settings of the connected motor or parameter setting is out of logical area. |
| servoNet | 3303 | 0E83 | An error occurred in the HWBB circuit of the SERVOPACK. |
| servoNet | 3303 | 0E89 | A safety module parameter for which the power must be turned OFF and ON again to enable the settings was changed. |
| servoNet | 3303 | 0EA0 | DRV Alarm 0 of the SERVOPACK occurred. |
| servoNet | 3303 | 0EA1 | DRV Alarm 1 of the SERVOPACK occurred. |
| servoNet | 3303 | 0EA2 | A SERVOPACK DRV alarm 0 occurs. |
| servoNet | 3303 | 0EA3 | An error occurred in communications data between the SERVOPACK and EtherCAT (CoE) Network Module |
| servoNet | 3303 | 0EB0 | An error occurred in the CPU of the Safety Module, or in a peripheral circuit. |
| servoNet | 3303 | 0EB1 | The safety function signal input timing is faulty. |
| servoNet | 3303 | 0EB2 | A safety module parameter setting is outside the setting range. An error occurred for a combination of safety module parameters. |
| servoNet | 3303 | 0EB3 | An error occurred in the SERVOPACK HWBB circuit. |
| servoNet | 3303 | 0EB4 | The feedback data is incorrect. (The output data of encoder pulse is incorrect.) |
| servoNet | 3303 | 0EB5 | The ON/OFF timing of Safety Request Input Signals A1 and A2 does not match the specified time period. |
| servoNet | 3303 | 0EB6 | The ON/OFF timing of Safety Request Input Signals B1 and B2 does not match the specified time period. |
| servoNet | 3303 | 0EB7 | The motor speed has exceeded the monitoring speed specified for Safety Function A. Alternatively, the distance that the motor moved has exceeded the allowable distance for monitoring that was specified for Safety Function A. |
| servoNet | 3303 | 0EB8 | The motor speed has exceeded the monitoring speed specified for Safety Function B. Alternatively, the distance that the motor moved has exceeded the allowable distance for monitoring that was specified for Safety Function B. |
| servoNet | 3303 | 0EB9 | A safety module parameter was modified. |
| servoNet | 3303 | 0EC0 | A different SERVOPACK than the previous SERVOPACK was connected. |
| servoNet | 3303 | 0EC1 | There is a mismatch between the safety-related servo parameters in the safety module and the parameters in the SERVOPACK or in the combination of the currently connected motor and encoder. |
| servoNet | 3303 | 0EC2 | A safety function that cannot be used together with the Active Mode Function has been selected. |
| servoNet | 3303 | 0EC3 | An unsupported SERVOPACK was connected to the safety module. |
| servoNet | 3303 | 0EC4 | An unsupported encoder was connected and/or the encoder configuration is incorrect. |
| servoNet | 3303 | 0EC5 | The safety module password has not been registered. |
| servoNet | 3303 | 0EC6 | An error occurred in a peripheral circuit of the safety module. |
| servoNet | 3303 | 0EC8 | An error occurred in the gate drive circuit. |
| servoNet | 3303 | 0EC9 | An error occurred in the gate drive circuit. |
| servoNet | 3303 | 0ED0 | Command error in the SERVOPACK |
| servoNet | 3303 | 0ED1 | A timeout occurred when using a MECHATROLINK command. |
| servoNet | 3303 | 0F10 | One phase is not connected in the main power supply. |
| servoNet | 3303 | 0F50 | The Servomotor did not operate or power was not supplied to the Servomotor even though the Servo ON command (Enable Operation command) was input when the Servomotor was ready to receive it |
| servoNet | 3317 | 0002 | SERVOPACK parameters are set incorrectly for external axis. Set Pn002.3 = 0 and Pn00E.3 = 1 or 3. |
| servoNet | 3317 | 0003 | The CoE module had certain required pdo mappings which were not present. |
| servoNet | 3317 | 0004 | EC_TOPOLOGY_OK is false, indicating a fault with the EtherCAT network configuration. The motion system cannot initialize EtherCAT-connected axes. |
| servoNet | 3317 | 0005 | Counter no longer enabled on CoE SLIO bus coupler module. |
| servoNet | 3317 | 0006 | The configured cycle time for the EtherCAT network is invalid. All fieldbus networks using motion axes must be configured with a synchronized cycle time. |
| servoNet | 3317 | 0007 | Unable to read CoE Slave Configuration info from Master OD. |
| servoNet | 3317 | 0008 | The module map is empty or missing form servonet.xml. |
| servoNet | 3317 | 0009 | The servo product code is not found in the list of supported servopacks. |
| servoNet | 3319 | 0001 | Local-SLIO counter no longer enabled. |
| servoNet | 3319 | 0002 | SB_TOPOLOGY_OK is false, indicating a fault with the SLIO network configuration. The motion system cannot initialize Local SLIO connected axes. |
| servoNet | 3319 | 0006 | The configured cycle time for the SliceBus network is invalid. All fieldbus networks using motion axes must be configured with a synchronized cycle time. |
| app | 3407 | 0002 | The base directory for configuration files was missing and has been created automatically. The system has booted in a minimal configuration mode, and most functionality is limited. Please upload a new complete configuration file set. |
| app | 3407 | 0003 | A required default configuration file was missing. A minimal configuration for the corresponding component has been loaded, and some functionality may be limited. |
| app | 3407 | 0004 | A required default configuration file was incorrectly formatted. A minimal configuration for the corresponding component has been loaded, and some functionality may be disabled. |
| app | 3407 | 0005 | A configuration file specified by the user configuration file set was incorrectly formatted. The corresponding default configuration file is being used instead. |
| app | 3407 | 0006 | The file describing which configuration set to use was corrupted. The default configuration set is being used. |
| app | 3407 | 0007 | An error occurred while writing a config file. The file system may be full or damaged. |
| app | 3407 | 0008 | Querying controller information during startup failed, likely due to a problem with the hardware configuration. Information about the controller and attached hardware may be missing. |
| app | 3409 | 0001 | The servo network axis node for the axis specified in the configuration file was not found. |
| app | 3409 | 0002 | Axis enable failed. This problem is usually a result of communication problems with the servo drive. |
| app | 3409 | 0003 | Axis group motion activation failed. Some axes in the group are currently under control of another group, or motion has been blocked by the user. |
| app | 3409 | 0004 | The motion segment could not be added to the motion queue because it is already queued. |
| app | 3409 | 0005 | Moves are prohibited when any of the group's axes are disabled, have an alarm, or are in violation of their soft limits. |
| app | 340A | 0001 | The source for the logical input was not found, so the configured input will not be available. |
| app | 340A | 0002 | The source for the logical output was not found, the the configured output will not be available. |
| app | 340A | 0003 | Two or more axis in the configuration file had the same axis ID. |
| app | 340A | 0004 | The servo network axis node for the axis specified in the configuration file was not found. |
| app | 340A | 0005 | The axis group specified in the configuration file could not be created. Check that the name is not already in use, that all the axes are valid, and that the other configuration data (such as kinematics module) are valid and supported by this product. |
| app | 340A | 0006 | The type of AtTargetAgent specified in the configuration file is unknown. This is because AtTargetAgent could not be created. |
| app | 340A | 0007 | The number of constraints for axis group soft limit must be the same as the number of axes in the axis group. |
| app | 340A | 0008 | The axis group doesn't have the configured frame. |
| app | 340A | 000B | A continuous-wrap range for an axis causes its position to automatically wrap around between two user-specified numbers. Generally these numbers evaluate to full revolutions of the encoder but other ranges are permitted. However, all ranges specified in user units must map exactly to an integral number of encoder pulses. This alarm indicates that the mapping from user units to encoder ticks was inexact. Use more precise numbers to describe the range or choose a different range that evaluates to an integral number of encoder pulses. When this alarm occurs at startup or servo-net reset, it indicates that the axis has not been connected to an axis node and cannot be servoed on. Otherwise, this alarm indicates that the specified continuous-wrap range was not put into effect. |
| app | 340A | 000D | Two or more logical outputs specified in the I/O configuration file use the same physical bit. This can cause writes to not correctly generate value-change events on logical outputs for the shared bits. The configuration file should be fixed. |
| app | 340A | 000E | One or more of the data parameters in the axis configuration file were out-of-range or otherwise incorrectly specified for the axis. The axis was not created and is not available. |
| app | 340A | 0010 | After servo network reset, the Axis failed to reconnect to the servo network. The drive might have been removed from the network, the node ID of the drive might have changed or there might be a communication problem. |
| app | 340A | 0012 | After servo network reset, the network I/O failed to reconnect to the servo network. The network I/O module might have been removed from the network, the node ID of the network I/O module might have changed or there might be a network communication problem. |
| app | 340A | 0013 | After servo network reset, a new axis node was discovered. This axis node is not associated with any existing axes and will not be available. To make this node available, update the configuration and power cycle the controller. |
| app | 340A | 0014 | After servo network reset, a new I/O node was discovered. This I/O node is not associated with any existing I/O and will not be available. To make this node available, update the configuration and power cycle the controller. |
| app | 340A | 0017 | One or more of the axis data or configuration parameters were inconsistent or incompatible with the axis node specified. The axis was created but was not connected to the servo node. |
| app | 340A | 001B | Two or more LogicalInput have the same ID. The configuration file should be fixed. |
| app | 340A | 001C | Two or more LogicalOutput have the same ID. The configuration file should be fixed. |
| app | 340A | 001D | Two or more AnalogInput have the same ID. The configuration file should be fixed. |
| app | 340A | 001E | Two or more AnalogOutput have the same ID. The configuration file should be fixed. |
| app | 340A | 001F | Analog I/O configuration is missing the 'hardwareConfig' element, and configuration could not be resolved by the physical hardware. The configuration file should be fixed by adding this element to the analog I/O element. |
| app | 340A | 0020 | One or more axes failed to respond to a servo-off command during a system I/O initiated abort. This is normally the result of communication problems with the drive, which also causes an automatic servo-off. |
| app | 340A | 0022 | Reset of a servo node failed. |
| app | 340A | 0023 | The axis position may not be valid because the persistent axis data was corrupted. SRAM should be reinitialized and the axis should be homed. |
| app | 340A | 0024 | The configuration property in Axis.xml could not be set on startup. This error might occur if the servo drive has been removed or changed since Axis.xml was created. |
| app | 340A | 0025 | The configuration property in Axis.xml could not be fetched on startup. This error might occur if the servo drive has been removed or changed since Axis.xml was created. |
| app | 340A | 0026 | The configuration property in Axis.xml does not match the one checked on startup. This error might occur if the servo drive has been removed or changed since Axis.xml was created. |
| app | 340A | 0027 | The configured feature in Axis.xml could not be found on startup. This error might occur if the servo drive has been removed or changed since Axis.xml was created. |
| app | 340A | 002A | An axis group was configured with a kinematics feature that was unrecognized or unsupported on this product. |
| app | 340A | 002C | The axis offset persistent storage was corrupted on startup. Axis offsets may be reset to 0. |
| app | 340A | 002D | Backing storage for the axis offset was unavailable. The axis offset will not be saved. |
| app | 340A | 002E | Backing storage for the axis offset encountered an error. The axis ID may exceed the allowable value. |
| app | 340C | 0000 | All PLCopen error codes are in the range from 0x0000 to 0x0fff. |
| app | 340C | 0001 | Time limit exceeded. |
| app | 340C | 0002 | Distance limit exceeded. |
| app | 340C | 0003 | Torque limit exceeded. |
| app | 340C | 1101 | When stopping the PLC, an axis experienced a state error. The axis may not work correctly if the PLC warm start is performed without a controller restart. |
| app | 340C | 1102 | When starting the PLC, an axis experienced an internal state error. The axis may not work correctly until the controller is restarted, or the PLC is warm started after the source of the error is corrected. |
| app | 340C | 1103 | When stopping the PLC, an axes group experienced a state error. The group may not work correctly if the PLC warm start is performed without a controller restart. |
| app | 340C | 1110 | All motion error codes are in the range from 0x1111 to 0x111f. |
| app | 340C | 1111 | The move could not be buffered because the motion queue for that axis is full. |
| app | 340C | 1112 | The move could not be started because motion is prohibited. |
| app | 340C | 1113 | The servo drive failed to enable or disable. |
| app | 340C | 1114 | Drive parameter read/write did not complete. |
| app | 340C | 1115 | Drive parameter read/write failed |
| app | 340C | 1116 | Torque move prohibited while non-torque moves queued or in progress. |
| app | 340C | 1117 | CamOut called while not camming. |
| app | 340C | 1118 | The master slave relationship can not be modified because the master axis has not been set yet. |
| app | 340C | 1119 | CamFileSelect can not open a second cam table while the first cam table is still being opened. |
| app | 340C | 111A | The function block can not be used with an external axis. |
| app | 340C | 111B | The homing sequence is already in progress. |
| app | 340C | 111C | MC_SetPosition can not be called while the axis is moving. |
| app | 340C | 111D | Motion aborted due to axis alarm. |
| app | 340C | 111E | MC_SetPosition can not set the position to be outside the configured wrap range. |
| app | 340C | 111F | Can not transition to homing state |
| app | 340C | 1120 | Clear alarms is already in progress. |
| app | 340C | 1121 | Axis reset is already in progress. |
| app | 340C | 1122 | Mechatrolink reset is already in progress. |
| app | 340C | 1123 | CamStructSelect can tansfer a second cam structure while the first cam structure is being transferred. |
| app | 340C | 1124 | CamTableRead can not be read a second cam structure while the first cam structure is being read. |
| app | 340C | 1125 | CamTableWrite can not write a second cam structure while the first cam structure is being written. |
| app | 340C | 1126 | MC_SetPosition can not be called while either the master or slave axis is caming. |
| app | 340C | 1127 | The function block can not be used with a virtual axis. |
| app | 340C | 1128 | The function block can not be used with an inverter axis. |
| app | 340C | 1129 | Y_VerifyParameters and Y_WriteParameters can not be called a second time while the first one is in progress. |
| app | 340C | 112A | Unable to add position monitor. Increase the 'maxPositionWindows' element in motion.xml. |
| app | 340C | 112B | Window parameters are outside the wrap range. |
| app | 340C | 112C | The function block could not be executed because the axis latch function was already in use. |
| app | 340C | 112D | Over travel limit still ON after attempting to move away from it. |
| app | 340C | 112E | The cam shift is not possible with EndPostion and current master position. |
| app | 340C | 112F | Axis could not be enabled because drive control power is off. |
| app | 340C | 1130 | Axis could not be enabled because hardware base block is on. |
| app | 340C | 1131 | Unable to communicate with the axis |
| app | 340C | 1132 | The function block requires an external axis. |
| app | 340C | 1133 | The coincidence output function is not supported on this device. |
| app | 340C | 1134 | Can not execute MC_GearOut because axis is not gearing. |
| app | 340C | 1135 | Y_CamOut was aborted. |
| app | 340C | 1136 | The axis does not support position latch, or it does not support position latch in the mode requested. |
| app | 340C | 1137 | The internal buffer for storing continuous latch data for Y_ProbeContinuous overflowed between scans of the function block. |
| app | 340C | 1138 | The drive did not accept the specified Pattern.PatternSize or Pattern.PatternCount for Y_ProbeContinuous. |
| app | 340C | 1139 | The parameter write operation could not be completed because a previous parameter write was in progress. |
| app | 340C | 113A | Parameter is read-only. |
| app | 340C | 113B | The parameter read operation could not be completed because a previous parameter read was in progress. |
| app | 340C | 113C | The axis does not support this parameter. |
| app | 340C | 113D | The function block can not be used with a stepper axis. |
| app | 340C | 113E | The controller cannot communicate with a drive. |
| app | 340C | 113F | Reboot already in progress. |
| app | 340C | 1140 | Add IP Address already in progress. |
| app | 340C | 1141 | Remove IP Address already in progress. |
| app | 340C | 1142 | Debug Print already in progress. |
| app | 340C | 1143 | Motion queue resize failed. Motion queue is not empty. |
| app | 340C | 1144 | Brake release function failed to execute. Brake release is prohibited while servo on, or the axis may not support brake release. |
| app | 340C | 1145 | Servo ON is prohibited while the brake is manually released with Y_BrakeRelease. |
| app | 340C | 1146 | Position offset update failed. Do not call MC_SetPosition at high frequency when using ABS encoder on products which store the offset in flash, such as Sigma-7Siec. |
| app | 340C | 1147 | The function block can not be used with an active slave axis. |
| app | 340C | 1148 | Velocity override value outside allowable range |
| app | 340C | 1149 | Tangent master axis is invalid. TangentSlave must be connected to an axis with valid continuous wrap. |
| app | 340C | 114A | The function block requires an external axis. |
| app | 340C | 1210 | All error codes for structures are in the range from 0x1211 to 0x121f. |
| app | 340C | 1211 | Axis ID does not correspond to an axis. |
| app | 340C | 1212 | The master slave relationship is not defined. |
| app | 340C | 1213 | The input reference does not correspond to a real input |
| app | 340C | 1214 | The output reference does not correspond to a real output. |
| app | 340C | 1215 | The input/output number does not correspond to a real input or output bit. |
| app | 340C | 1216 | Trigger reference is not valid. |
| app | 340C | 1217 | The cam switch structure is not valid. |
| app | 340C | 1218 | The track structure is not valid. |
| app | 340C | 1219 | Table size results in misaligned data. |
| app | 340C | 121A | Buffer size results in misaligned data. |
| app | 340C | 121B | Table type is not supported. |
| app | 340C | 121C | Invalid start index. |
| app | 340C | 121D | Invalid end index. |
| app | 340C | 121E | The specified buffer is full. |
| app | 340C | 1220 | All error codes for invalid enumeration values are in the range from 0x1221 to 0x122f. |
| app | 340C | 1221 | 'BufferMode' does not correspond to a valid enumeration value. |
| app | 340C | 1222 | 'Direction' does not correspond to a valid enumeration value. |
| app | 340C | 1223 | 'StartMode' does not correspond to a valid enumeration value. |
| app | 340C | 1224 | 'ShiftMode' does not correspond to a valid enumeration value. |
| app | 340C | 1225 | 'OffsetMode' does not correspond to a valid enumeration value. |
| app | 340C | 1226 | 'Mode' does not correspond to a valid enumeration value. |
| app | 340C | 1227 | 'SynchMode' does not correspond to a valid enumeration value. |
| app | 340C | 1228 | 'Parameter' does not correspond to a valid enumeration value. |
| app | 340C | 1229 | 'AdjustMode' does not correspond to a valid enumeration value. |
| app | 340C | 122A | 'RampIn' does not correspond to a valid enumeration value. |
| app | 340C | 122B | 'ControlMode' does not correspond to a valid enumeration value. |
| app | 340C | 122C | 'EndMode' does not correspond to a valid enumeration value. |
| app | 340C | 1230 | All error codes for range errors are from 0x1231 to 0x124f. |
| app | 340C | 1231 | Distance parameter is less than zero. |
| app | 340C | 1232 | Velocity parameter is less than or equal to zero. |
| app | 340C | 1233 | Acceleration is less than or equal to zero. |
| app | 340C | 1234 | Deceleration is less than or equal to zero. |
| app | 340C | 1235 | Torque is less than or equal to zero. |
| app | 340C | 1236 | Time is less than or equal to zero |
| app | 340C | 1237 | Specified time was less than zero. |
| app | 340C | 1238 | Specified scale was less than or equal to zero. |
| app | 340C | 1239 | Velocity is negative. |
| app | 340C | 123A | Denominator is zero. |
| app | 340C | 123B | Jerk is less than or equal to zero. |
| app | 340C | 123C | TorqueRamp is less than or equal to zero. |
| app | 340C | 123D | Engage position is outside the table domain. |
| app | 340C | 123E | Negative engage width. |
| app | 340C | 123F | Disengage position is outside the table domain. |
| app | 340C | 1240 | Negative disengage width. |
| app | 340C | 1241 | StartPosition is outside of master's range. |
| app | 340C | 1242 | EndPosition is outside of master's range. |
| app | 340C | 1243 | Axis filter time constant out of specified range. |
| app | 340C | 1244 | Feedback delay is out of range. |
| app | 340C | 1245 | The specified size of the array was larger than the maximum permitted size. |
| app | 340C | 1246 | The array index was greater than the specified buffer's size. |
| app | 340C | 1247 | An invalid date or time value was entered. |
| app | 340C | 1248 | An invalid acceleration filter type was entered. |
| app | 340C | 1249 | The specified position value exceeded the limits set for the axis or group configuration. |
| app | 340C | 124A | The specified velocity value exceeded the limits set for the axis or group configuration. |
| app | 340C | 124B | The specified acceleration value exceeded the limits set for the axis or group configuration. |
| app | 340C | 1310 | All error codes for invalid input data range from 0x1211 to 0x121f. |
| app | 340C | 1311 | The specified Pn does not exist. |
| app | 340C | 1312 | The mask does not correspond to valid tracks. |
| app | 340C | 1313 | The profile must start with relative time equal to zero, and the time must be increasing. |
| app | 340C | 1314 | The specified cam file does not exist. |
| app | 340C | 1315 | Invalid header for the cam file. Cam tables must have a header indicating the number of rows, number of columns and a feed forward velocity flag |
| app | 340C | 1316 | The first (master) column must be either increasing or decreasing. |
| app | 340C | 1317 | Cam table reference does not refer to a valid cam table. |
| app | 340C | 1318 | The engage phase exceeded the time limit. Slave axis could not attain the target position and velocity within the user specified time limit. |
| app | 340C | 1319 | The engage phase exceeded the distance limit. Slave axis could not attain the target position and velocity within the user specified master distance. |
| app | 340C | 131A | Invalid width input. Width is an enumeration type with the following allowable values 'WIDTH_8'=0, 'WIDTH_16'=1, and 'WIDTH_32'=2. |
| app | 340C | 131B | The slave axis can not be the same as the master axis. |
| app | 340C | 131C | Default drive parameter info is not available for this parameter. |
| app | 340C | 131D | Invalid external axis. |
| app | 340C | 131E | Invalid virtual axis. |
| app | 340C | 131F | File extension is not recognized or missing. |
| app | 340C | 1320 | Cound not find the axis parameter file. |
| app | 340C | 1321 | The drive's model number or type does not match the parameter file. |
| app | 340C | 1322 | No S-curve filter is configured for the axis. |
| app | 340C | 1323 | Axis position compensation file was not found at the location specified, or the default location if no location was specified. |
| app | 340C | 1324 | The axis position compensation file was formatted incorrectly. |
| app | 340C | 1325 | The axis must be servo off before changing the enable state of position compensation. |
| app | 340C | 1326 | When the axis is configured in rotary wrap mode, the axis position compensation file data range must match the rotary wrap range. The start and end offset for the file must also match to prevent discontinuity. |
| app | 340C | 1327 | The Data Type input value does not match the data type of the Value input. |
| app | 340C | 1328 | The Data Type input value is out of the range of allowed values. |
| app | 340C | 1329 | IO Identifier value did not correspond to a configured IO object in io.xml. |
| app | 340C | 1330 | The specified servonet node was not found. |
| app | 340C | 1331 | The Mechatrolink node did not support the specified IO aux cmd. |
| app | 340C | 1332 | The Mode argument to Y_MLinkIOMode was invalid. |
| app | 340C | 1333 | Bulk parameter eeprom write operation required but not supported |
| app | 340C | 1334 | Some written parameters require a drive reboot or power cycle to take effect. |
| app | 340C | 1335 | The cam engage window cannot be automatically calculated from the current parameters. |
| app | 340C | 2110 | All log error codes are in the range from 0x2111 to 0x211f. |
| app | 340C | 2111 | Adding log items or setting up log is not possible because the data log is already set up. |
| app | 340C | 2112 | Starting or stopping logging is not possible because the data log is not set up. |
| app | 340C | 2113 | Invalid handle for user log item. |
| app | 340C | 2114 | Data log can not be created because too many data logs are in use. |
| app | 340C | 2115 | Invalid handle for data log. |
| app | 340C | 2116 | A user log item can only support eight inputs for each type. |
| app | 340C | 2117 | Saving the log failed. |
| app | 340C | 2200 | All socket and serial error codes are in the range from 0x2200 to 0x22ff. |
| app | 340C | 2201 | The maximum number of concurrently open user IO devices (sockets/files) has been reached. |
| app | 340C | 2202 | The user IO device handle was invalid. |
| app | 340C | 2203 | The IP address string was not in a valid format. |
| app | 340C | 2204 | The socket could not be created. |
| app | 340C | 2205 | The specified address or port is already in use. |
| app | 340C | 2206 | The specified address or port is not available for use. |
| app | 340C | 2207 | Unable to accept new socket connection. |
| app | 340C | 2208 | Unable to bind to the specified address. |
| app | 340C | 2209 | The socket type argument was invalid. |
| app | 340C | 220A | The local address or port was not valid. |
| app | 340C | 220B | The socket could not be connected. |
| app | 340C | 220C | There is no network routing path to the specified address. |
| app | 340C | 220D | The socket is already connected to another endpoint. |
| app | 340C | 220E | The socket connection attempt was actively refused by the remote peer. |
| app | 340C | 220F | The socket was not connected to a remote endpoint. Call Y_ConnectSocket prior to Y_ReadDevice or Y_WriteDevice. |
| app | 340C | 2210 | An error occurred trying to get or set the device option. |
| app | 340C | 2211 | The communication device could not be read. |
| app | 340C | 2212 | The communication device could not be written. |
| app | 340C | 2213 | The Buffer argument to WriteDevice and ReadDevice is required. |
| app | 340C | 2214 | The device option ID was invalid. |
| app | 340C | 2215 | The device option value was not the right size or the data was out of range. |
| app | 340C | 2216 | The serial port ID was not a valid serial port. |
| app | 340C | 2217 | The serial port could not be opened. |
| app | 340C | 2218 | The subnet mask string was not in a valid format. |
| app | 340C | 2219 | The desired interface is invalid. |
| app | 340C | 221A | Adding the IP Address failed for an unknown reason. |
| app | 340C | 221B | Removing the IP Address failed for an unknown reason. |
| app | 340C | 221C | The desired address and subnet combination conflict with the settings on the existing units. |
| app | 340C | 221D | RemoveIPAddress cannot remove the primary address. |
| app | 340C | 221E | Debug Print failed. |
| app | 340C | 2300 | Invalid Group Handle |
| app | 340C | 2301 | Group enable is not possible because on or more axes is already owned by another group |
| app | 340C | 2302 | Group activation is blocked. |
| app | 340C | 2303 | Invalid coordinate system |
| app | 340C | 2304 | Move prohibited because group has an alarm |
| app | 340C | 2305 | Group activation was prohibited because the axis/joint configuration was invalid. |
| app | 340C | 2306 | Group activation was prohibited because the split joint axis command positions were mismatched. Align the axes to the same command position before continuing. |
| app | 340C | 2307 | The group reports one or more of its axes has an error. Clear the individual axis errors to clear this alarm. |
| app | 340C | 2308 | Axis group reset is already in progress. |
| app | 340C | 2309 | The method specifier for the circular path computation was invalid. Use a supported circular path method enumeration. |
| app | 340C | 230A | The method specifier for the circular path direction was invalid. Use a supported circular path direction enumeration. |
| app | 340C | 230B | The points specified to describe the circle are invalid: they may be collinear, collocated, or result in inconsistent circle radius. |
| app | 340C | 230C | The group is in an error state because one of its axes is disabled. |
| app | 340C | 230D | The transition mode is out of range or unsupported. |
| app | 340C | 230E | The transition parameter is out of range. |
| app | 340C | 230F | The values for the acceleration, deceleration, and/or velocity of the transition yield an invalid geometry. |
| app | 340C | 2310 | Axes groups cannot transition directly between certain states, such as direct transition to disabled state from moving or error states. Use the appropriate function block to transition to the correct intermediate state. |
| app | 340C | 2311 | The optional limit coordinate type specifier (a.k.a. VelocityUnit) parameter for the motion was outside the allowed range. |
| app | 340C | 2312 | The resolved velocity limit for the move was infinite. |
| app | 340C | 2313 | The resolved acceleration limit for the move was infinite. |
| app | 340C | 2314 | The resolved deceleration limit for the move was infinite. |
| app | 340C | 2315 | The specified coordinate frame has insufficient dimensions for the operation. |
| app | 340C | 2316 | The specified Plane argument to Y_SyncTangentAxisToGroup was out of range. |
| app | 340C | 2317 | The specified value for motion join colinearity angle was out of range. |
| app | 340C | 2318 | The points specified to describe the circle are invalid due to a mismatch in dimensions, or the rotations do not match. |
| app | 340C | 2319 | The move cannot be completed as computed because the motion requirements violate acceleration constraints. Please make the move less aggressive. |
| app | 340C | 2320 | The move cannot be completed as computed because the motion requirements violate velocity constraints. Please make the move less aggressive. |
| app | 340C | 2321 | This action requires the group to be inactive. |
| app | 340C | 2322 | This axis group does not support motion command filtering. |
| app | 340C | 2323 | The specified time constant for the axis group motion command filter was less than zero or exceeded the maximum value. |
| app | 340C | 2324 | Parameter 2110 (axis group filter time constant) must be set to a non-zero value before the filter can be enabled. |
| app | 340C | 2325 | The specified action was not supported for the specified coordinate frame combination. |
| app | 340C | 2326 | A zero-length vector was supplied for the direction |
| app | 340C | 2327 | The specified coordinate frame was actively involved in commanded motion and could not be modified. |
| app | 340C | 2328 | Specified blending transition for the function block was not supported. |
| app | 340C | 2329 | The specified blending transition called for exact corner distance or deviation, but insufficient distance remained in the segment to satisfy the transition geometry. |
| app | 340C | 232A | The specified position was unreachable due to inverse kinematics limitations. |
| app | 340C | 232B | Specified blending transition for the function block could not be realized due to blending parameter restrictions. Typically due to accel limit too low or segment length too short, relative to transition velocity. |
| app | 340C | 232C | An invalid or unsupported value of ExecutionMode was input to the function block. |
| app | 340C | 232D | An invalid or unsupported value of TrackProfileMode was input to the function block. |
| app | 340C | 232E | An invalid value of TrackProfile parameter was input to the function block. |
| app | 340C | 232F | The execution of the function with ExecutionMode = Queued or Delayed failed. The conditions for applying the function were validated when it was called, but when the deferred execution occurred the conditions were no longer valid. Check the sequencing of the program. |
| app | 340C | 2330 | The specified memory address is out of range. |
| app | 340C | 2331 | Memory operations are not supported on this servopack. |
| app | 340C | 2332 | Attempted NONVOLATILE write to VOLATILE only address. |
| app | 340C | 2333 | The conveyor position was past the allowable sync-in position when the conditions for sync-in were met. |
| app | 340C | 2334 | If a group is in motion, it cannot reinitiate conveyor tracking. |
| app | 340C | 2335 | The target coordinate frame is invalid or missing. |
| app | 340C | 2336 | The conveyor master must enter into each TrackState region from the lower boundary and exit to the upper boundary. Backtracking into previous TrackState regions (e.g. transitioning from SyncOut back to InSync) is not supported. |
| app | 340C | 2337 | The conveyor master exceeded the options.SyncIn.DelayLimit parameter when the ExecutionMode was satisfied |
| app | 340C | 2338 | Axis group is not paused/interrupted |
| app | 340C | 2339 | The group is unable to begin velocity override because it is in an active master/slave relationship. |
| app | 340C | 233A | NONVOLATILE memory write cannot be attempted when axis servo is enabled. |
| app | 340C | 233B | An invalid value of DwellTime parameter was input to the function block. |
| app | 340C | 233C | An invalid value of BlankTime parameter was input to the function block. |
| app | 340C | 233D | An invalid value of FinalDwellTime parameter was input to the function block. |
| app | 340C | 233E | The alarm code used to query an alarm description was not recognized by the controller. |
| app | 340C | 233F | The Alarm Describer is fetching the description of the alarm code entered from an xml file. |
| app | 340C | 2340 | The Alarm History read operation is already in progress. |
| app | 340C | 2341 | Specified points are collinear when not allowed. |
| app | 340C | 2342 | Specified points are coincident when not allowed. |
| app | 340C | 2343 | Radius from center of start/end/via points is not consistent within tolerance |
| app | 340C | 2344 | Via point is missing when required, incorrect size, or otherwise invalid |
| app | 340C | 2345 | Normal vector is missing when required, incorrect size, or otherwise invalid |
| app | 340C | 2346 | Circle center could not be calculated due to numeric imprecision error |
| app | 340C | 2347 | The read multiple alarms operation is already in progress. |
| app | 340C | 2348 | To ensure the correct velocity scaling, moves with only rotational components should specify the VelocityUnits option as "UseRotationalScalars" or assign non-zero values to the AlternateVelocity and AlternateAcceleration options. Similar logic exists for translational only moves and the "UseTranslationalScalars" option. |
| app | 340C | 2349 | Tool offset is not supported for this axes group. |
| app | 340C | 2350 | One or more tool offset values are invalid for this axis group |
| app | 340C | B114 | Failed to send clear alarms command. |
| app | 340C | B115 | Failed to reset Mechatrolink. |
| app | 340C | B116 | Mechatrolink reset is prohibited while axes are moving. |
| app | 340C | B117 | Failed to initialize abs encoder. |
| app | 340C | B118 | Function block can not be executed because download is in progress. |
| app | 340C | B119 | Y_RebootController prohibitied while an axis is enabled. |
| app | 340C | B11A | The specified file contains a formatting error. |
| app | 340C | B11B | Servo node read/write failed due to an error returned from the protocol stack. Check the output log for details. |
| app | 340C | B11C | Servo node read/write failed due to an error returned from the node. Check the output log for details. |
| app | 340C | EDED | This function block was implemented in a later firmware version. If you would like to use this function block, then the controller must be updated. |
| app | 340C | F110 | All error codes for kernel errors range from 0xF111 to 0xF11f. |
| app | 340C | F111 | An internal assertion in the motion kernel failed indicating the controller is not in a stable state. This error should be reported to Yaskawa Electric America. |
| app | 340D | 0000 | Custom PLC alarm codes posted by the user application |
| app | 340E | 1030 | The configured axis count exceeded the allowable limit. |
| app | 340E | 1031 | The default drive parameter file could not be processed. The file may be incorrect or misformatted. |
| motionKernel | 4202 | 0001 | The command position will soon reach the allowable range for the axis in the positive direction (positive overtravel). The axis may not be moved again until the alarm condition is cleared. After the alarm is cleared, it is permissible to execute a move which brings the axis back toward the allowed region, even though the axis is probably still outside the allowed region. Any move which pulls the axis further away from the allowed region will re-trigger the alarm. |
| motionKernel | 4202 | 0002 | The command position will soon reach the allowable range for the axis in the negative direction (negative overtravel). The axis may not be moved again until the alarm condition is cleared. After the alarm is cleared, it is permissible to execute a move which brings the axis back toward the allowed region, even though the axis is probably still outside the allowed region. Any move which pulls the axis further away from the allowed region will re-trigger the alarm. |
| motionKernel | 4202 | 0003 | The command speed will soon reach the allowable range for the axis in the positive direction (overspeed). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0004 | The command speed will soon reach the allowable range for the axis in the negative direction (overspeed). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0005 | The command acceleration will soon reach the allowable range for the axis in the positive direction. The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0006 | The command acceleration will soon reach the allowable range for the axis in the negative direction. The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0007 | The command torque will soon reach the allowable range for the axis in the positive direction (overtorque). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0008 | The command torque will soon reach the allowable range for the axis in the negative direction (overtorque). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0011 | The command position will soon reach the allowable range for the axis in the positive direction (positive overtravel). The axis may not be moved again until the alarm condition is cleared. After the alarm is cleared, it is permissible to execute a move which brings the axis back toward the allowed region, even though the axis is probably still outside the allowed region. Any move which pulls the axis further away from the allowed region will re-trigger the alarm. |
| motionKernel | 4202 | 0012 | The command position will soon reach the allowable range for the axis in the negative direction (negative overtravel). The axis may not be moved again until the alarm condition is cleared. After the alarm is cleared, it is permissible to execute a move which brings the axis back toward the allowed region, even though the axis is probably still outside the allowed region. Any move which pulls the axis further away from the allowed region will re-trigger the alarm. |
| motionKernel | 4202 | 0013 | The command speed will soon reach the allowable range for the axis in the positive direction (overspeed). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0014 | The command speed will soon reach the allowable range for the axis in the negative direction (overspeed). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0015 | The command acceleration will soon reach the allowable range for the axis in the positive direction. The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0016 | The command acceleration will soon reach the allowable range for the axis in the negative direction. The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0017 | The command torque will soon reach the allowable range for the axis in the positive direction (overtorque). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0018 | The command torque will soon reach the allowable range for the axis in the negative direction (overtorque). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0021 | The command position will soon reach the allowable range for the axis in the positive direction (positive overtravel). The axis may not be moved again until the alarm condition is cleared. After the alarm is cleared, it is permissible to execute a move which brings the axis back toward the allowed region, even though the axis is probably still outside the allowed region. Any move which pulls the axis further away from the allowed region will re-trigger the alarm. |
| motionKernel | 4202 | 0022 | The command position will soon reach the allowable range for the axis in the negative direction (negative overtravel). The axis may not be moved again until the alarm condition is cleared. After the alarm is cleared, it is permissible to execute a move which brings the axis back toward the allowed region, even though the axis is probably still outside the allowed region. Any move which pulls the axis further away from the allowed region will re-trigger the alarm. |
| motionKernel | 4202 | 0023 | The command speed will soon reach the allowable range for the axis in the positive direction (overspeed). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0024 | The command speed will soon reach the allowable range for the axis in the negative direction (overspeed). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0025 | The command acceleration will soon reach the allowable range for the axis in the positive direction. The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0026 | The command acceleration will soon reach the allowable range for the axis in the negative direction. The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0027 | The command torque will soon reach the allowable range for the axis in the positive direction (overtorque). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0028 | The command torque will soon reach the allowable range for the axis in the negative direction (overtorque). The axis may not be moved again until the alarm condition is cleared. |
| motionKernel | 4202 | 0055 | Runtime motion acceleration and/or jerk limits were temporarily exceeded to correct for off-axis motion. |
| servoNet | 4301 | 000A | The SERVOPACK model type was unable to be determined. This can indicate that some parameters may be incorrect. |
| servoNet | 4303 | 0000 | The base code for Sigma drive warnings. The drive's warning value is bitwise OR'd in with this base value. |
| servoNet | 4303 | 0900 | Position error pulse exceeded the parameter settings (Pn520 x Pn51E/100). |
| servoNet | 4303 | 0901 | When the servo turned ON, the position error pulses exceeded the parameter setting (Pn526 x Pn528/100). |
| servoNet | 4303 | 0910 | This warning occurs before the overload alarms (A.710 or A.720) occur. If the warning is ignored and operation continues, an overload alarm may occur. |
| servoNet | 4303 | 0911 | Abnormal vibration at the motor speed was detected. The detection level is the same as A.520. Set whether to output an alarm or warning by "Vibration Detection Switch" of Pn310. |
| servoNet | 4303 | 0912 | The surrounding temperature of the control PCB is abnormal |
| servoNet | 4303 | 0913 | The surrounding temperature of the power PCB is abnormal |
| servoNet | 4303 | 0914 | The surrounding temperature of the converter PCB is abnormal |
| servoNet | 4303 | 0920 | This warning occurs before the regenerative overload alarm (A.320) occurs. If the warning is ignored and operation continues, a regenerative overload alarm may occur. |
| servoNet | 4303 | 0921 | This warning occurs before Dynamic Brake Overload (A.731) alarm occurs. If the warning is ignored and operation continues, a dynamic brake overload alarm may occur. |
| servoNet | 4303 | 0923 | The fan inside the SERVOPACK stopped |
| servoNet | 4303 | 0930 | This warning occurs when the absolute encoder battery voltage is lowered. Continuing the operation in this status may cause an alarm. |
| servoNet | 4303 | 0941 | The change of the parameters can be validated only after turning the power ON from OFF. |
| servoNet | 4303 | 0942 | The speed ripple compensation information stored in the encoder does not agree with the speed ripple compensation information stored in the SERVOPACK |
| servoNet | 4303 | 094A | Incorrect command parameter number was set. |
| servoNet | 4303 | 094B | Command input data is out of range. |
| servoNet | 4303 | 094C | Calculation error was detected. |
| servoNet | 4303 | 094D | Data size does not match. |
| servoNet | 4303 | 094E | Latch mode error is detected. |
| servoNet | 4303 | 095A | Command was sent though command sending condition was not satisfied. |
| servoNet | 4303 | 095B | Unsupported command was sent. |
| servoNet | 4303 | 095C | Command condition is not satisfied for parameter settings. |
| servoNet | 4303 | 095D | Command, especially latch command, interferes. |
| servoNet | 4303 | 095E | Subcommand and main command interfere. |
| servoNet | 4303 | 095F | Undefined command was sent. |
| servoNet | 4303 | 0960 | Communications error occurred during MECHATROLINK communications. |
| servoNet | 4303 | 0962 | Communications error occurred during MECHATROLINK communications. |
| servoNet | 4303 | 0963 | The Synchronization frame was not received during MECHATROLINK communications. |
| servoNet | 4303 | 0971 | This warning occurs before Undervoltage (A.410) alarm occurs. If the warning is ignored and operation continues, an undervoltage alarm may occur. |
| servoNet | 4303 | 097A | A command that cannot be executed in the current phase was sent. |
| servoNet | 4303 | 097B | The set command data was clamped to a minimum or maximum value out of the allowable setting range. |
| servoNet | 4303 | 09A0 | Overtravel is detected while the servomotor power is ON. |
| servoNet | 4303 | 09B0 | One of the consumable parts has reached the end of its service life |
| servoNet | 4317 | 0001 | DC either not configured or not in sync |
| app | 4407 | 0001 | The configuration file directory is read-only or resides on a read-only file system. Attempts to update the configuration or create directories will fail. |
| app | 4407 | 0002 | An attempt was made to write to a read-only configuration file. The write failed. |
| app | 4408 | 0001 | The alarm history was configured to use NVRAM storage, but either the available NVRAM was not sufficient to contain the configured buffer size, or the configured buffer size was not large enough to contain the configured number of records. The alarm history will contain fewer records than configured. |
| app | 4408 | 0002 | The alarm history was configured to use NVRAM storage and the data was found to be corrupted. The alarm history has been lost. NOTE: this alarm also occurs if the configured size of the alarm history has been changed. |
| app | 440A | 000C | The position and torque scales specified in the configuration file have different signs. As a result, a positive acceleration results in a negative torque, and position limits are opposite in sign as the torque limits. |
| app | 440A | 000F | The axis was temporarily disconnected from the servo network during reset. During this time, the feedback data is not valid and the axis cannot be moved. |
| app | 440A | 0011 | The network I/O was temporarily disconnected from the servo network during reset. During this time, any network I/O state change will be unobservable to the controller. |
| app | 440A | 0019 | The system was rebooted by the user. |
| app | 440A | 001A | The system failed to shut down gracefully during a reboot, although the reboot did occur. This does not necessarily indicate that the software is damaged. |
| app | 440E | 1032 | The default drive parameter file was not found. |