Error Codes and Exception Description
1 Real-time Motion Errors
The robot will detect its status during motion and report errors to the SDK when anomalies are detected. Users can determine the error type through the following 20 error bits.
| Error Bit | Error Name | Cause | Solution |
|---|---|---|---|
| 0 | kActualJointPositionLimitsViolation | Actual joint angle exceeded limit | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 1 | kActualCartesianPositionLimitsViolation | Actual end posture exceeded limit | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 2 | kActualCartesianMotionGeneratorElbowLimitViolation | Actual elbow angle exceeded limit | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 3 | kActualJointVelocityLimitsViolation | Actual joint velocity exceeded limit | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 4 | kActualCartesianVelocityLimitsViolation | Actual end velocity exceeded limit | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 5 | kActualJointAccelerationLimitsViolation | Actual joint acceleration exceeded limit | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 6 | kActualCartesianAccelerationLimitsViolation | Actual end acceleration exceeded limit | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 7 | kCommandJointPositionLimitsViolation | Command joint angle exceeded limit | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 8 | kCommandCartesianPositionLimitsViolation | Command end posture exceeded limit | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 9 | kCommandCartesianMotionGeneratorElbowLimitViolation | Command elbow angle exceeded limit | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 10 | kCommandJointVelocityLimitsViolation | Command joint velocity exceeded limit | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 11 | kCommandCartesianVelocityLimitsViolation | Command end velocity exceeded limit | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 12 | kCommandJointAccelerationLimitsViolation | Command joint acceleration exceeded limit | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 13 | kCommandCartesianAccelerationLimitsViolation | Command end acceleration exceeded limit | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 14 | kCommandJointAccelerationDiscontinuity | Command joint acceleration discontinuous | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 17 | kCommandTorqueDiscontinuity | Command torque discontinuous | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 18 | kCommandTorqueRange Violation | Command torque exceeded limit | Check if planned trajectory is continuous and differentiable. Generally, planned trajectories need to have continuous velocity and angular velocity. If robot motion is unstable or abnormal noise occurs, first consider whether the trajectory is smooth, and perform additional filtering if necessary. |
| 15 | kCollision | Collision detected | If collision detection is triggered frequently, appropriately increase the collision detection threshold. E-stop triggering may also cause this error. |
| 16 | kCartesianPositionMotionGeneratorInvalidFrame | Robot singularity | Robot should not pass through singular poses during Cartesian space motion |
| 19 | kInstabilityDetection | Instability detected | 1. Check if packet loss threshold is too low, generally set to 10~20; 2. Servo error, usually requires robot restart; 3. Pressing E-stop switch will also trigger this error; |
2 Error Codes
Non-real-time interface call results are fed back through error codes. Each interface passes a std::error_code type parameter, and the error message can be obtained through error_code::message().
| Value | Error Message | Cause and Solution |
|---|---|---|
| 0 | Operation completed successfully | None |
| -1 | An error occurred | May be due to unrecognized error code, please contact technical support |
| -3 | Robot E-stop button pressed, please recover first | Recover E-stop state |
| -16 | This operation is not allowed in current mode (manual/auto), please switch to another mode | Switch manual/auto mode |
| -17 | This operation is not allowed in current power state | Switch power on/off state |
| -18 | This operation is not allowed in current robot running state | Robot not idle, may be in drag/RT mode/identification etc. |
| -19 | This operation is not allowed in current control mode (position/force) | Switch position control/force control |
| -20 | Robot in motion | Stop robot motion |
| -32 | Inverse kinematics calculation error | Pass correct posture |
| -33 | IK solution is singular point | Avoid singular points |
| -34 | IK solution exceeds robot soft limit | Check soft limit settings, pass pose within limits |
| -35 | Target point exceeds motion range | Pass reachable points |
| -36 | Target point exceeds motion range | Pass reachable points |
| -37 | Step distance too large, cannot calculate IK | Pass reachable points |
| -38 | Configuration data cfx error, IK has no solution | Check conf data |
| -39 | Input data error, cannot calculate IK | Pass reachable points |
| -40 | IK reference point is singular point | Pass reachable points |
| -41 | Algorithm failed, cannot calculate IK | May be controller calculation issue, contact technical support |
| -257 | Communication protocol parsing failed | Contact technical support |
| -258 | No matching data name found | May be controller and SDK version mismatch |
| -259 | No matching command name found | May be controller and SDK version mismatch |
| -260 | Data value error, possibly protocol mismatch | May be controller and SDK version mismatch |
| -272 | Data name to query not found | May be controller and SDK version mismatch |
| -273 | Data not readable | May be controller and SDK version mismatch |
| -288 | Data not writable | May be controller and SDK version mismatch |
| -289 | Failed to set data | Data value unreasonable |
| -290 | Failed to set data | Data value unreasonable |
| -291 | Monitor data failed | Will not occur |
| -292 | Data already monitored, duplicate monitoring not supported | Will not occur |
| -320 | Command execution not completed | Will not occur |
| -337 | Recorded path too short, insufficient data points, please re-record | Increase record time and re-record |
| -338 | Recorded path contains points exceeding joint soft limits. Please re-record | Drag within soft limits |
| -339 | Recorded path contains points with excessive joint velocity. Please re-record | Slow down drag motion |
| -340 | Path recording did not start from robot stationary state | Start recording when robot is stationary |
| -341 | Robot not stopped when stopping path recording | Stop recording when robot is stationary |
| -342 | Robot in power-off state, failed to save path | Power on robot |
| -352 | No valid path in buffer, please record | Record path before saving |
| -353 | Failed to save path to disk | Re-record drag trajectory, or restart robot |
| -513 | Failed to switch manual/auto mode | -Stop robot motion -Recover E-stop -Disable drag |
| -514 | Power on/off failed | -Recover E-stop -Clear servo alarm |
| -515 | Failed to enable/disable drag, check if robot is powered off | Enable drag when robot is in manual mode and powered off |
| -10005 | Calibrating, or failed to reset load during calibration | -Wait for calibration to complete -Set correct load |
| -10030 | Simulation mode not enabled or signal does not exist | Enable simulation mode before setting DI/AI |
| -10040 | Failed to start drag, set correct load and calibrate torque sensor | Correctly set tool load mass and COG; calibrate torque sensor after setting |
| -10051 | Soft limit exceeds mechanical limit | Set soft limits within mechanical limits |
| -10065 | NTP time sync failed | -Install NTP function -Confirm server NTP available, confirm IP correct |
| -10101 | Illegal IP address | Check if it conforms to IPv4 format |
| -10079 | Force control module in error state | Force control protection triggered, check robot status in force control mode and set reasonable protection parameters |
| -10141 | Load mass exceeds robot rated load | Use and set load within rated range |
| -14010 | Already bound as system IO | - Unbind this signal as system IO - Use other signals |
| -14501 | DO signal does not exist or is system output | Check if DO signal is created |
| -17001 | Read register error | - Check if register is created - Check array index - Read with matching data type |
| -17002 | Write register error | - Check if register is created - Check array index - Write with matching data type |
| -17320 | RL program executed, need to reset motion cache before starting motion | Call moveReset to reset |
| -17407 | Enable rail needs to disable safety zone | Disable safety zone function |
| -28672 | Real-time mode network error | - Local IP cannot be localhost or robot address - Port occupied, check RCI settings-port |
| -28688 | Failed to switch motion control mode | - Stop robot motion - Restart controller |
| -28689 | This frequency not supported | State data send frequency supports 1kHZ, 500Hz, 250Hz, 125Hz |
| -28705 | Already in motion | Stop motion before starting |
| -28706 | Cannot execute this operation, possibly robot not in idle state | Stop robot motion |
| -28707 | Start position is singular point | Move robot to non-singular point |
| -28708 | Parameter error | Reset data |
| -28709 | Robot in collision stop | Power on to recover collision state |
| -28710 | Robot in E-stop state | Recover E-stop |
| -28711 | Request rejected | In impedance control, usually due to FC model deviation, recalibrate torque sensor and set correct load |
| -41400 | Force control command not yet completed | Wait for previous FC command to complete |
| -41419 | TCP length exceeded, FC init failed | End tool length limit is 0.3m |
| -41420 | FC not initialized; or load not set correctly; or large FC model deviation | - Calibrate zero point, torque sensor; - Set correct load mass and COG; - Check if base frame is set correctly; - No external force received when enabling drag |
| -41421 | Failed to stop FC, not in FC running state | Robot not in FC state |
| -41422 | Failed to restart FC | Pause or stop FC first, then restart |
| -41425 | Not in impedance control mode, or search motion running | - Ensure in impedance mode and search motion stopped - Check parameter settings |
| -41426 | Not in impedance control mode, or search motion running | -Ensure in impedance mode and search motion stopped - Check parameter settings |
| -41427 | Not in Cartesian impedance mode or search motion not set | Check control mode command, set search motion parameters before trying |
| -41428 | Not in Cartesian impedance mode or search motion not started | Ensure search motion enabled and in Cartesian impedance state |
| -41429 | Not in Cartesian impedance mode or search motion not paused | Pause current FC task and check control mode, switch to Cartesian impedance before trying |
| -41430 | Unsupported impedance control type or FC frame | Stop current FC task and reinitialize parameters |
| -41431 | Not in joint impedance mode or not initialized | Set joint space impedance control mode before running FC |
| -41432 | Not in Cartesian impedance mode or not initialized | Set Cartesian impedance control mode before running FC |
| -41433 | Not in Cartesian impedance mode or not initialized | Check current impedance control mode before trying. Ensure force value input correct and Cartesian impedance mode set |
| -41434 | Joint desired force exceeded limit | Check current impedance control mode before trying. Ensure desired force value input correct and joint space impedance mode set |
| -41435 | Cartesian desired force exceeded limit | Check current impedance control mode before trying. Ensure desired force value input correct and Cartesian impedance mode set |
| -41442 | Robot does not meet soft limit requirements, failed to enable FC | Ensure robot is within soft limits when enabling impedance |
| -41444 | Impedance stiffness setting failed, value unreasonable or cannot set in current state | Reset impedance stiffness value within reasonable range |
| -41448 | Powered off during FC, init failed | Power on and execute FC init |
| -41449 | FC command not yet completed, init failed | FC commands sent too frequently, increase time between exit FC and restart |
| -41457 | FC stop executed, need to restart | Execute FC init |
| -41459 | In FC mode, operation not allowed | Stop FC before replaying path |
| -50000 | Trajectory angle too small or length too short, zone cannot be generated | -Increase angle between trajectories; -Increase trajectory length; -Increase zone value |
| -50001 | Controller state error, cannot generate trajectory | Call moveReset() to reset |
| -50002 | Target point exceeds motion range or is singular point | - Check target point position; - Move robot using joint mode - Check confdata configuration |
| -50003 | Two adjacent target points too close | Check if adjacent motion commands have same target point |
| -50004 | Cannot generate arc, start and target point too close | Adjust distance between arc start and target points |
| -50005 | Cannot generate arc, start and auxiliary point too close | Adjust distance between arc start and auxiliary points |
| -50006 | Cannot generate arc, auxiliary and target point too close | Adjust distance between arc auxiliary and target points |
| -50007 | Cannot generate arc, start/auxiliary/target points too close | Adjust distances between arc points |
| -50008 | Cannot generate arc, points on same line | Adjust distances between arc points |
| -50009 | Cannot generate arc, radius too small | Adjust distances between arc points |
| -50010 | Cannot generate arc | Adjust distances or orientations between arc points |
| -50019 | Failed to generate trajectory | Readjust target point position, orientation and elbow angle (7-axis only) |
| -50021 | No solution for target point with specified conf, check value or don't set confData | -Call setDefaultConfOpt(false) to disable confdata - Re-teach point, pass correct confdata |
| -50027 | Trajectory shorter than minimum zone radius, auto path blending | - This trajectory needs zones on both sides but length is less than twice min zone radius; - This trajectory has one zone but length less than min zone radius. This makes motion smoother, to disable set min zone radius to 0 |
| -50033 | Robot in axis lock state, target point lock angle deviated, adjust target or disable lock | In lock state, 4th axis angle must be 0° or 180° or -180° |
| -50034 | Cannot reach target point in lock state or 5-axis model | 6-axis in lock state or 5-axis model cannot reach target, change point or disable lock |
| -50101 | Joint angle exceeded range, try disabling soft limits and moving axes to allowed range | - Disable soft limits - Manually move robot axes to normal working range |
| -50102 | Trajectory passing through singular point | - Avoid singular points - Re-teach points, change target; - Change Cartesian motion to joint motion |
| -50103 | Cartesian path endpoint doesn't match given ConfData | - Call setDefaultConfOpt(false) to not use confdata - Change to MoveJ or MoveAbsJ - Change target point confdata |
| -50104 | Joint torque exceeded limit | - Check if load matches actual - Check friction coefficient, motor overload coefficient, transmission overload coefficient - Try changing command type, e.g., Cartesian to joint |
| -50112 | Posture error, IK calculation failed | - Re-teach posture - If current model is 3 or 4-axis, check if input posture matches model - If using setAvoidSingularity(lock4axis), check if target meets lock requirements |
| -50113 | Orientation change exceeded set threshold | - Avoid singular points - Reset singularity avoidance orientation change threshold |
| - Re-teach points, change target - Use other singularity avoidance methods | ||
| -50114 | Axis motion exceeded range during lookahead, stopped early | - Disable soft limits - Manually move robot axes to normal working range |
| -50115 | Singular point encountered during trajectory lookahead | - Avoid singular points - Re-teach points, change target - Change jog mode, try joint space jog - Change Cartesian motion to joint motion |
| -50118 | Orientation changed endpoint doesn't match required endpoint | - Avoid singular points - Re-teach points, change target - Change singularity avoidance method |
| -50120 | Failed to search path endpoint angle under singularity avoidance | - Avoid singular points - Re-teach points, change target - Change singularity avoidance method - If Conf enabled, can disable Conf |
| -50121 | Failed to search path endpoint angle under singularity avoidance | - Avoid singular points - Re-teach points, change target - Change singularity avoidance method |
| -50204 | Insufficient sampling points during planning, please re-run | IPC unstable, re-run or try restart |
| -50205 | Adjacent position commands differ too much | - Re-teach trajectory target points - Try changing command type, e.g., MoveL to MoveJ |
| -50208 | Internal trajectory error | - Call moveReset() to reset motion cache - Increase or decrease zone |
| -50401 | Collision detected | - Check robot environment, ensure personnel and equipment safety, power on and resume - Check if current tool settings match actual, if tool mass and COG are reasonable |
| -50501 | Tool/workpiece frame setting failed, possibly doesn't exist | Set created tool/workpiece, handheld and external respectively |
| -50512 | Axis count mismatch | Joint space jog index cannot exceed axis count + external axis count |
| -50513 | Invalid speed setting, robot cannot move | Pass speed parameter in 0.01 ~ 1 range |
| -50514 | Invalid step setting, robot cannot move | Pass step parameter greater than 0 |
| -50515 | Invalid reference frame, robot cannot move | Pass supported frame type |
| -50516 | Invalid motion axis, robot cannot move | Pass index parameter as described |
| -50518 | Motion failed, target may be current point | Target point may be current point |
| -50519 | Failed to generate trajectory, target may exceed robot work range | Re-teach points within normal work range |
| -50525 | This model doesn't support singularity avoidance, or axis lock failed, 4th axis angle not 0 | Adjust 4th axis angle to 0° or ±180° |
| -60005 | RL project or specified task doesn't exist | Run created project and task |
| -60014 | Controller current state doesn't allow starting motion | Ensure robot powered on and idle |
| -60200 | Load info error, setting failed | - Load info error, check if load weight exceeds rated, COG not exceeding 0.3m - FC doesn't support external tool or handheld workpiece |
| -60511 | Path doesn't exist | Use saved replay path |
| -60611 | Generating diagnostic data, cannot move, please wait | Wait 10 seconds and try again |
| -60702 | Current 4th axis angle not 0, cannot switch to 4-axis fixed mode, or model not supported | Check if current 4th axis angle is 0° or 180° |
| -60704 | Sacrifice orientation singularity avoidance enable conditions not met | Check if current state meets sacrifice orientation singularity avoidance conditions |
| -60706 | Joint space interpolation singularity avoidance enable conditions not met | Check if current state meets joint space interpolation singularity avoidance conditions |
| 256 | Network connection error | - IPC not powered on - Robot address wrong, or not on same LAN - Instance type error or SDK not authorized, connection refused |
| 255 | Robot connection not initialized | Generally won't happen, normally construct Robot class instance |
| 257 | Cannot parse robot message, possibly SDK version mismatch with controller | May be controller and SDK version mismatch |
| 258 | Parameter error, value out of range | Check parameter value range according to function description |
| 259 | Parameter error, wrong type or count | Check parameter type or array length according to function description |
| 260 | Not a valid transformation matrix | Check if input meets homogeneous transformation matrix requirements |
| 261 | Array element count doesn't match robot axis count | Pass array length matching robot axis count |
| 262 | Motion control mode error, please switch to correct mode | Call setMotionControlMode to switch mode according to actual situation |
| 263 | No response from robot before timeout, possibly network issue | Check network connection, or contact technical support |
| 264 | Duplicate operation | Collision detection already enabled, need to disable first |
| 265 | Failed to receive data via UDP port, check network and firewall | - Check if local address is set correctly - Check firewall settings, allow UDP connection |
| 266 | Client verification failed, check controller version, authorization and model | - Upgrade controller to matching version per manual - Create robot instance with matching type - Contact technical support for SDK authorization |
| 272 | Event not monitored | Call setEventWatcher first to start monitoring |
| 273 | Points too close, frame calibration failed | Refer to "xCore Control System Manual" for tool/workpiece calibration method, recalibrate |
| 512 | IP address or port setting error, or port occupied | - Local IP cannot be localhost or robot address - Port occupied, check RCI settings-port |
| 513 | Unsupported field set, or total length exceeded | Supported fields see RtSupportedFields, total length limit 1024 bytes |
| 768 | No executable motion commands | Call moveAppend to send motion commands before starting motion |
| 769 | Robot stopping or current state cannot pause | May be due to manual power off or E-stop just pressed before calling stop(), controller responding to stop, please wait |
3 Exceptions
Real-time mode interfaces for sending motion commands, periodic scheduling, reading state data, etc. may throw exceptions during calls. Exception types are in rokae/exception.h.
| Exception Message | Cause and Solution |
|---|---|
| Motion control mode error, not real-time mode | - Call setMotionControlMode(RtCommand) to switch mode - Previous impedance control error, controller switched back to non-RT mode, need to re-enable |
| Failed to create real-time control client | Network connection error, check IPC running state |
| Already receiving data | Stop receiving state data first, then restart receiving |
| Controller cannot set sent state data | May be version mismatch, contact technical support |
| Failed to set control command | May be version mismatch, contact technical support |
| UDP socket open failed. Invalid argument provided | Robot connection didn't fill in local address. e.g., xMateRobot(remoteIp, localIp); |
| UDP socket open failed. Address invalid in this context | Failed to bind local address, check if local address is correct and on same LAN as robot |
| Controller cannot send robot state info | Controller UDP port setting error, contact technical support to check controller logs |
| Not receiving data | Call startReceiveRobotState to start receiving data |
| No robot state feedback before timeout, check network config | - Check if local address is set correctly - Check firewall settings, allow UDP connection |
| Robot state data receive error | State data parsing failed, may be version mismatch, contact technical support |
| Cannot receive motion error feedback | Data parsing failed, may be version mismatch, contact technical support |
| xCore minimum version required | Upgrade controller version according to prompt |
| SDK function not authorized | Contact technical support for SDK authorization |
| Robot instance type doesn't match connected model | Create corresponding robot instance according to manual |
| Local IPv4 address setting failed, cannot be 127.0.0.1 or robot address | Set correct local address |
| Posture init receives 6 or 16 parameters | Init trans&rpy should pass array of length 6; init pos (RT mode Cartesian command) should pass array of length 16 |
| Failed to load model | Unless network connection issue, generally won't occur |
| xMate model library doesn't support this model | Refer to xMateModel class comments for supported models |
| Already in motion, don't call repeatedly | Only one motion callback allowed at a time, call stopMove before starting next motion |
| startMove not called | Call startMove first, then call startLoop |
| Mode setting error, failed to start motion | Unless network connection issue, generally won't occur |
| Failed to start motion | - Ensure robot idle, not in E-stop or other abnormal state |
| - Common in impedance control, calibrate zero point, torque sensor, set correct load and retry - Or provide complete exception info to technical support. | |
| Failed to stop motion | Generally network connection issue |
| Industrial model only supports position control | Industrial model uses position control |
| Start and end elbow angle format different | Cartesian command hasElbow values inconsistent |
| Command doesn't match control mode | Callback return data type (JointPosition/CartesianPosition/Torque) should match control type |
| Failed to send command | Command data serialization failed, contact technical support |
| Arc start/end/auxiliary points coincide | Adjust distances between arc points |
| Arc path solving, three points collinear | Adjust arc start, auxiliary, end points |
| Arc path solving, three points angle too small | Adjust arc start, auxiliary, end points |
| Arc path solving, arc radius too small failed | Adjust distances between arc points |
| Not initialized | FollowPosition default constructor needs to call init() before use |
| Filter error, input data not positive | Check command data, if callback returned unassigned command |
| Filter error, data to filter is infinite | Check command data, if callback returned unassigned command |