Dealing with Errors

There are multiple errors that can occur on an axis, either while at standstill or during a move. It is important when operating a show you pay attention to an axis status so you can take quick and appropriate action if an error occurs.

Depending on your moves, you may want to take advantage of the Group Stop feature (see “Groups and Triggers”) which will automatically stop an axis if any other axis in the Global Stop Group has an error.

Any errors are displayed in the Status section of the Axis Block.

Further diagnostic information and the Drive Reset button can be found under the Cont (Configuration) tab.

Safety Related Errors

Safety Related Errors are indicated by a "SafeOff"status.

Safety related errors can only be reset using the physical blue reset button on the desk.

To reset a Safety Related Error:

Ensure that the condition that led to the error no longer exists.
Press and release the blue [RESET] button on the desk.

✏️

You can also use other reset buttons to reset safety related errors on the automation system. Locations include the front of a Safety[Controller] or on top of a Stop[Box].

Communication Errors

Communication Errors are indicated by a "Offline" status on an axis or by a red background behind a node in the nodes section of the sidebar.

If only an individual axis has a status of "Offline" the cause of the error is likely only affecting that one axis.

If multiple axes have a status of "Offline" check to see if any nodes are showing as offline in the sidebar.

To reset a Communication Error, you can attempt to restart communications by:

Right-click on the node showing as offline.
The software will attempt to reconnect to the node and start communications.
If reconnecting is successful the node’s background will change to green and the "Offline" error will stop displaying on the affected axes.

Alternatively, you can attempt restart communications for all nodes in the system by:

Tap Exit to exit to the main menu.
Tap Run to reopen the run page and restart communication.

If the communication error persists:

Make sure the desk is set to Main and not Backup.

In Backup mode, the desk does not communicate with the automation system to avoid conflicting with the Main desk. Commands in Backup mode are queued up and send when switching into Main mode.

⚠️

Only one desk should be in Main mode at any one time

If you are unable to restart communications, see “Diagnosing Errors” on how to access further information about an error, or contact Absolute Motion Control.

Axis Warnings

Warnings will not usually affect an axis or cause it to stop. They communicate to the operator that a value in the system is close to reaching the limit of its permissible threshold.

UVLT_WRN	Under Voltage Warning. The input voltage is nearing the low threshold. Note: This warning is specific to low voltage drives.
OVLT_WRN	Over Voltage Warning. The input voltage is nearing the high threshold. Note: This warning is specific to low voltage drives
OTMP_WRN	Motor Over Temperature Warning. The motor temperature is higher than the maximum permissible value. Note: This warning is specific to low voltage drives
I2TAMP_WRN	2T Amplifier Warning. The drive internal simulated temperature calculation is nearing the maximum permissible value. Note: This warning is specific to low voltage drives
ENC_WRN	Encoder Warning. The encoder for this axis has issued a warning. Note: This warning is specific to low voltage motors and drives

Axis Errors

Errors will cause an axis to stop, because it is attempting to do something that is not permitted or a value has fallen outside an acceptable range.

Errors are reset for each axis individually using the Drive Reset button in the Conf (Configuration) section of an Axis Block.

To reset an Axis Error:

Locate the Axis Block for the affected axis.
If is isn’t already, expand the Conf section of the Axis Block.
Ensure that the condition that led to the error no longer exists.
Tap the Drive Reset button to reset the error.

Errors marked with * do not need to be reset and will reset automatically next time a move is run on that axis.

SLV_VELO	Slave Velocity Error. This error indicates that the slave axis velocity is different to the master axis, outside an acceptable range.
SLV_FAULT	Slave Fault. There is a fault on the slave axis, preventing movement.
PFOL_ERR	Position Following Error. This error indicates that an axis hasn’t been able to reach the position it expects at this point in time. This is often caused by a mechanical obstruction or issue, as a result of the axis exceeding the amount of current it has been permitted to draw.
VFOL_ERR	Velocity Following Error. This error indicates that an axis hasn’t been able to reach the velocity it expects at this point in time. This is often caused by a mechanical obstruction or issue.
MCFB_ERR	Motion Control Error. This error indicates that an axis is unable to start or continue motion control on this axis. This could be that a limit has been struck, preventing motion, or that the programmed move is outside the accepted parameters for that axis (trying to program a move beyond the axis’ soft limits, for example).
INTK_ERR	Interlock Error. This error indicates that an interlock condition has not been met, and movement has been stopped/prevented.
TIMO_ERR	Timeout Error. This error indicates that a condition hasn’t been met in a certain time.
STND_STL	Standstill Error. This error indicates that the axis was unable to execute its move, and was at standstill for longer than the permitted time.
DM_ERR	Deadman Error. The Deadmans Handle was released during a move. The axis stopped as a result of this.
DIR_ERR	Direction Error. The axis moved in the opposite direction to the direction intended.
GRP_ERR	Group Error. The axis stopped as a result of a group fault condition. An axis that has group stop enabled has entered the error state, and stopped the remaining axis with group stop enabled.
BRK_ERR	Brake Error. On axis enable, the brake did not release within the given time window, before initiating the move.
TRG_ERR	Trigger Error. The axis failed to locate its trigger source. Either the axis requested does not exist, or triggers have not been enabled within the control system.
I2TMTR_ERR	I2T Motor Warning. The drive internal simulated motor temperature calculation is nearing the maximum permissible value. Note: This error is specific to low voltage motors and drives
GRSGRV_ERR	Cross Groove Error. The axis has stopped as a result of a Cross Groove Detection. It is possible the axis could still be allowed to move in one direction, if this is permitted within the control system.
DRV_ERR	Drive Error. The drive has reported an error. For further information on the specific error see “Diagnosing Errors”
OVR_CUR	Over Current. The axis has requested more current than has been allowed for. Specific to Low Voltage Drives.
OVR_TMP	Over Temperature. The drive temperature is greater than the maximum allowed temperature. Note: This error is specific to low voltage drives
OVR_VLT	Over Voltage. The drive input voltage is greater than the maximum permissible value. Note: This error is specific to low voltage drives
UND_CUR	Under Current. The drive current is less than the minimum required current. Note: This error is specific to low voltage drives.
INIT	Initialisation. The axis is performing an initialisation procedure at boot up. Move commands during this time will not be permitted.
POS_INIT	Position Initialisation. The axis is performing a position initialisation procedure at the boot up. Move commands during this time will not be permitted. Note: the position of the axis during this time may not be correct.

There is more information that can be reported back about an error, which can help diagnose the issue. This can be accessed in the Conf (Configuration) section of an Axis Block, see “Diagnosing Errors”.

Up Next:

🚨Diagnosing Errors