Motion control function block error IDs

When a motion control function block ends with an error and the axis state is Error Stop, use the MC_Reset function block or MC_Power Off/On and MC_Reset to recover the axis. The axis can be reset to normal motion operation without stopping the controller operation.
Motion control function block error IDs
Value
MACRO ID
Description
00
MC_FB_ERR_ NO
The function block execution is successful.
01
MC_FB_ERR_ WRONG_STATE
The function block cannot execute because the axis is not in the correct state. Check the axis state.
02
MC_FB_ERR_ RANGE
The function block cannot execute because invalid axis dynamic parameters (velocity, acceleration, deceleration, or jerk) exist in the function block.
Correct the setting for the dynamic parameters in the function block against the
Axis - Dynamics
 configuration page.
03
MC_FB_ERR_ PARAM
The function block cannot execute because there is an invalid parameter other than velocity, acceleration, deceleration, or jerk, set in the function block.
Correct the setting for the parameters (for example, mode or position) for the function block.
04
MC_FB_ERR_ AXISNUM
The function block cannot execute because the axis does not exist, the axis configuration data is corrupted, or the axis is not correctly configured.
05
MC_FB_ERR_ MECHAN
The function block cannot execute because this axis gets a fault due to drive or mechanical issues. Check the connection between the drive and the controller (Drive Ready and In-Position signals), and ensure that the drive is operating normally.
06
MC_FB_ERR_ NOPOWER
The function block cannot execute because the axis is not powered on.
Power on the axis using the MC_Power function block.
07
MC_FB_ERR_ RESOURCE
The function block cannot execute because the resource required by the function block is controlled by some other function block or it is not available.
Ensure the resource required by the function block is available for use.
Examples:
  • MC_Power try to control the same axis.
  • MC_Stop are executed against the same axis at the same time.
  • MC_TouchProbe are executed against the same axis at the same time.)
  • MC_TouchProbe is executed, while touch probe input is not enabled in motion configuration.
08
MC_FB_ERR_ PROFILE
The function block cannot execute because the motion profile defined in the function block cannot be achieved.
Correct the profile in the function block.
09
MC_FB_ERR_ VELOCITY
The function block cannot execute because the motion profile requested in the function block cannot be achieved due to current axis velocity.
Examples:
  • The function block requests the axis to reverse the direction while the axis is moving.
  • The required motion profile cannot be achieved because the current velocity is too low or too high.
Check the motion profile setting in the function block, and correct the profile, or re-execute the function block when the axis velocity is compatible with the requested motion profile.
0A
MC_FB_ERR_ SOFT_LIMIT
This function block cannot execute because it will end up moving beyond the soft limit, or the function block is canceled because the soft limit has been reached.
Check the velocity or target position settings in the function block, or adjust the soft limit setting.
0B
MC_FB_ERR_ HARD_LIMIT
This function block is canceled because the hard limit switch active state has been detected during axis movement, or canceled because the hard limit switch active state has been detected before axis movement starts.
Move the axis away from the hard limit switch in the opposite direction.
0C
MC_FB_ERR_ LOG_LIMIT
This function block cannot execute because it will end up moving beyond the PTO Accumulator logic limit, or the function block is canceled because the PTO Accumulator logic limit has been reached.
Check the velocity or target position settings for the function block or use the MC_SetPosition function block to adjust the axis coordinate system.
0D
MC_FB_ERR_ ERR_ENGINE
A motion engine execution error is detected when executing the function block.
Power cycle the whole motion setup, including controller, drives and actuators, and re-download the User Application. If the fault persists, contact the technical support.
10
MC_FB_ERR_ NOT_HOMED
The function block cannot execute because the axis must be homed first.
Execute homing against the axis using the MC_Home function block.
80
MC_FB_ERR_ PARAM_MODIFIED
Warning: The requested velocity for the axis has been adjusted to a lower value.
The function block executes successfully at a lower velocity.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal