Skip to main content

Error Messages Reference

tip

This manual summarizes the error messages that may occur during the operation of the teleoperation system, along with their meanings and handling suggestions, to help you quickly locate and resolve issues.

To look up an entry, use your browser's in-page find (press Ctrl + F on Windows / Linux, or ⌘ + F on macOS) and type the error code or an English keyword. All entries in this manual are on a single page, so you can jump straight to the match; you can also browse section by section using the headings below. Messages are shown in code style and can be selected and copied directly.

Placeholders such as {sensor name}, {topic}, and {service} are replaced with actual names on site — keep the complete information when contacting after-sales service.

If you cannot find the corresponding entry in this manual, please refer to the Log Collection section to complete related operations and contact technical support with the complete error information and on-site logs.

Messages containing heal, restored, received, or successfully usually mean the system has already recovered or the operation succeeded — they are not new faults, and are marked as "(Info)" below. If recovery messages keep alternating with error messages, the connection stability still needs to be checked.

Items that require operating internal device services, ROS configurations, or system privileges are placed in collapsible "Technician operation" blocks and should be handled by a technician with maintenance privileges or by after-sales service.

1. Safety Messages Requiring Immediate Stop​

When the following messages appear, the robot may lose normal control — press the emergency stop immediately.

MessageMeaningHandling
DANGER! VR App/TeleSuit/WIFI restarted during syncThe VR, motion capture suit, or Wi-Fi restarted during synchronization, and the robot may lose normal control.1) Immediately press the robot emergency stop and confirm personnel safety; 2) Identify which device restarted (VR App / motion capture suit / Wi-Fi); 3) Investigate the cause (power loss, overheating, program crash); 4) Verify the motion mapping in simulation or a safe environment, then manually restart synchronization.
You MUST manaully restart sync if you needAfter a safety interruption, the system will not recover synchronization automatically.1) Keep the robot stopped; 2) After completing the safety checks, have the operator manually restart synchronization.
DANGER! Multiple VR App connected to the same WIFI during syncMultiple VR devices are detected on the same network, which may cause control conflicts and let several people control the robot at once.1) Press the emergency stop immediately; 2) Confirm only one VR is connected to the motion capture suit Wi-Fi and disconnect the others; 3) After confirming, manually restart synchronization.
Only keep 1, then manaully restart sync if you needOnly one VR should be kept, then synchronization must be restored manually.1) Confirm only one operating VR is on the network; 2) Manually restart synchronization.
Initiating home reset...(Info) The robot is returning to its initial position (homing), and the arm will return to the preset safe starting posture.1) Make sure there are no obstacles or personnel around the robot; 2) Observe whether the arm returns to the initial position smoothly; 3) Do not touch the joysticks during homing; 4) Once homing completes, confirm the robot is in a safe posture before continuing.
Home reset completed successfully(Info) The homing operation completed successfully.1) Confirm the robot posture is correct before continuing operation.
Home reset completed but failed(Info) The homing flow finished, but part of the motion failed.1) Do not continue teleoperation directly; 2) Check whether each joint is in a safe position and re-home according to the project's operating rules if necessary (Standard: pull both joysticks outward and hold for 1 second, then release; Professional: externally rotate both feet and hold for 1 second, then return); 3) If it fails repeatedly, contact technical support.

Spellings such as manaully in the error messages come from the original system output and are kept here so that you can search for them.

2. Sensors, Motion Capture Suit, and Gloves​

Error CodeMessageMeaningRecommended Action
0101406Interval Seq error: {sensor name}The data transmission of sensor {sensor name} on the motion capture suit has experienced frame skipping / packet loss, and the captured motion data may be discontinuous or have gaps.1) Check whether the sensor is loose or detached; 2) Move closer to the router (to avoid signal interference); 3) If it occurs frequently, restart the motion capture suit and recalibrate.
0101302Seq warn {sensor name}The data transmission of sensor {sensor name} shows slight instability (occasional stuttering). Data quality has decreased, but basic use is not affected.1) Observe for 30 seconds — if it recovers automatically, no action is needed; 2) If it persists, check whether the strap at the sensor's location is loose; 3) If the motion capture display appears abnormal, disable Mocap in the VR App interface and re-enable it.
0101302Seq warn {sensor name} heal!(Info) The previously unstable sensor {sensor name} has automatically recovered to normal, and data collection is back to normal. The "heal!" at the end of the message indicates automatic recovery.1) No action needed — this is a recovery notification; 2) If the cycle of "warning → recovery → warning" repeats, check whether the sensor is securely fastened; 3) You can confirm the status on the sensor status panel in the VR App.
0101409Seq timeout {sensor name}Sensor {sensor name} is completely disconnected. Motion data for that body part is interrupted, and the corresponding part of the avatar in the VR App will freeze or disappear.1) Check whether the sensor is detached or out of battery; 2) Make sure there are no metal objects obstructing the signal between the sensor and the main controller; 3) Check the data on the communication frequency panel in the VR App interface; 4) Disable Mocap → wait 5 seconds → re-enable; 5) If the issue persists, please contact technical support.
0101407Imu data invaild error: {sensor name} g_x / g_y / g_zSensor {sensor name} has detected an abnormality in the body rotation direction data. The rotation data in this direction is unreliable, which will lead to inaccurate motion capture.1) Keep the corresponding body part still for 3 seconds and see if it recovers automatically; 2) Check whether the sensor has been impacted or is near a strong magnet; 3) Disable Mocap → recalibrate → re-enable Mocap; 4) If the error persists, the sensor may be damaged and needs to be replaced.
0101407Imu data invaild error: {sensor name} a_x / a_y / a_zSensor {sensor name} has detected an abnormality in body acceleration data, which will affect the smoothness and force feedback of motions.1) Confirm whether the corresponding body part is moving vigorously (excessive motion amplitude); 2) Keep that body part still and see if the data recovers; 3) Recalibrate; 4) If the error persists while the body part is still, the sensor may be damaged and needs to be replaced.
0101301Touch error {sensor name}The contact detection function of sensor {sensor name} is abnormal, and the tactile feedback data is unreliable.1) Check whether the sensor is damaged or has water ingress; 2) Confirm whether the sensor connection cable is securely plugged in; 3) Replug the sensor module and restart Mocap; 4) If the error persists, please contact technical support.
0101408Skeleton error: {sensor name} {i} data error!The data of the {i}-th finger joint on the data glove {sensor name} is abnormal, and finger motions in the VR App may be inaccurate.1) Check whether finger joint {i} is stuck or has foreign objects; 2) Re-wear the glove and ensure each joint fits snugly; 3) Disable Mocap and re-enable; 4) If the same joint keeps reporting errors, the glove may be damaged and needs after-sales inspection.
0101408Skeleton error: {sensor name} {i} heal!(Info) The data of the {i}-th joint on the data glove {sensor name} has returned to normal. The "heal!" indicates automatic recovery.1) Confirm whether finger motions have recovered in the VR App; 2) If the cycle of "error → recovery" repeats, check whether the glove joint is loose; 3) Record the joint number {i} and perform preventive checks if it occurs frequently.
0101410IMU magnetometer not calibrated: {sensor name}The orientation calibration of sensor {sensor name} is not complete. Long-term use may cause the orientation in the VR App to gradually drift (for example, you are facing forward but slowly tilting in the VR App).1) Perform the complete calibration process on the VR App interface; 2) Stay away from metal objects and electromagnetic interference sources during calibration; 3) Perform the calibration motions as prompted; 4) Confirm that the error no longer occurs after calibration is complete.
0104500{sensor name} not stableThe data fluctuation of sensor {sensor name} is too large.1) Keep the corresponding body part completely still (can be placed flat on a table or the ground); 2) Stay away from vibration sources (fans, air conditioner outlets, etc.); 3) Confirm that the sensor is tightly fastened and does not wobble; 4) Re-enter calibration and continue only after the data stabilizes; 5) If the data can never stabilize, the sensor may be damaged and needs to be replaced.
0101400no calib data foundThe motion capture suit is missing calibration data. Even when wearing the motion capture suit, body motions cannot be captured correctly, and the avatar posture in the VR App will be abnormal.1) Recalibrate; 2) There should be a voice prompt after calibration is complete.
0101401Cannot open fileThe device cannot read the calibration data file (file is corrupted or missing), which also shows up as an abnormal avatar posture.1) Re-run the calibration process (which will generate a new data file); 2) If the error persists, restart the device and recalibrate.
0101402YAML parsing errorThe calibration data file content is corrupted and cannot be loaded, which also shows up as an abnormal avatar posture.1) Perform calibration again. The new calibration will overwrite the corrupted data file.
0101403Type conversion erroThe calibration data format is incompatible (usually caused by inconsistent device software versions), and the calibration data cannot be used normally.1) Recalibrate; 2) Record the TeleSuit and TeleBox software versions and contact after-sales service to confirm compatibility.
0101400no skeleton data foundThe data glove is missing pairing or calibration data. Finger motions cannot be tracked, and fingers will not move in the VR App.1) Confirm whether the data glove has been successfully paired; 2) Confirm on the VR App interface that the correct glove type is selected; 3) Re-run the glove pairing and calibration process.
Detected removal of mocap devices: {devices}It is detected that mocap device(s) {devices} have been disconnected, and the data of the corresponding body part(s) will be lost.1) Check the connection status of the disconnected device(s) {devices}; 2) Check whether the connection cables and ports are loose; 3) For wireless devices (such as wireless exoskeleton gloves), confirm that they are within Wi-Fi range and have sufficient power; 4) Reconnect the devices.
Detected addition of mocap devices: {devices}(Info) New mocap device(s) {devices} are detected to be connected to the system, and new devices are added when Mocap is enabled.1) Confirm whether the newly connected device(s) {devices} are the ones you expected; 2) If not, disconnect that device.
{module_name} missing mocap sensors: {missing_imus}An expected sensor is actually missing. {missing_imus} is the missing sensor.1) Check whether the missing sensor(s) {missing_imus} are properly connected; 2) Confirm on the VR App sensor status panel whether the number of sensors is correct.
{module_name} mocap sensors restored: {restored_imus}(Info) The previously missing sensor(s) {restored_imus} have been restored, and data integrity is recovered.1) Confirm that the restored sensors match those that were previously missing; 2) Confirm on the VR App interface that the avatar posture has returned to normal; 3) If the sensor is lost again in a short time, check the connection stability of the sensor.

3. Internal Communication and Hardware of the Motion Capture Suit​

Error CodeMessageMeaningRecommended Action
0101500Available SPI Channel is not 1The internal hardware communication channel of the motion capture suit is abnormal, and sensor data cannot be read normally. This is an internal device fault that requires a device restart to resolve.1) Restart the motion capture suit main controller; 2) If the error persists after restart, it indicates a hardware fault. Contact after-sales service for handling.
0101502GPIO errorThe internal synchronization signal of the motion capture suit is abnormal, which may affect coordination between sensors.1) Restart the motion capture suit main controller; 2) If the error persists, the device hardware may be faulty. Contact after-sales service for inspection.
0101502GPIO error heal(Info) The internal synchronization signal of the motion capture suit has automatically recovered to normal.1) Confirm whether data collection is normal; 2) If "error → recovery" occurs frequently, the device power supply may be unstable. Contact after-sales service for inspection.
0101501SPI_ReadWrite failed!The internal data communication of the motion capture suit is interrupted (severe fault). All motion capture data may stop, and the avatar in the VR App will be completely frozen.1) Check whether all connection cables of the motion capture suit are loose; 2) Restart the motion capture suit main controller; 3) Confirm on the VR App interface whether the Mocap frequency is 0; 4) If a restart does not resolve the issue, contact technical support.
0101201SPI_ReadWrite failed heal!(Info) The internal communication of the motion capture suit has automatically recovered, and data collection is back to normal.1) Check on the VR App interface whether the Mocap frequency has returned to normal; 2) If it recurs within 10 minutes, the device hardware may have an intermittent fault. It is recommended to contact technical support.
0100504Frame end errorThe data transmission between internal devices of the motion capture suit is incomplete, communication quality is poor, and the collected data may be missing.1) Check whether the connection cables between devices are securely plugged in and undamaged; 2) Stay away from high-power electrical appliances (such as motors, frequency converters, and other sources of interference); 3) Restart the motion capture suit main controller.
0100503Frame head errorCommunication between internal devices of the motion capture suit cannot be established at all, and data cannot be transmitted.1) Check whether the connection cables are plugged in correctly (direction and port aligned); 2) Try a known-good connection cable; 3) Restart the motion capture suit main controller.
0100505Hub enter params mode failedThe main controller Hub of the motion capture suit is not working normally. The system cannot obtain information such as the number and type of sensors, and the Mocap function is abnormal.1) Check whether the Hub indicator light is on (if not, it is not powered); 2) Replug the connection cable between the Hub and the main controller; 3) Restart the motion capture suit main controller; 4) If it fails multiple times, the Hub may have a hardware fault and needs to be replaced.
0100506Hub read params failedAlthough the Hub is powered on, the system cannot read sensor information from it, and sensor data cannot be transmitted.1) Confirm that the Hub connection cable is not loose; 2) Unplug the Hub power, wait 3 seconds, then plug it back in; 3) Disable Mocap on the VR App interface and re-enable it; 4) If it keeps failing, the Hub may be damaged and needs to be replaced.
0100508Get device type errorThe system cannot identify the type of a connected device, and the data from that device cannot be used normally.1) Confirm whether the device is a model supported by the system; 2) Replug the device and restart Mocap.
0100509No device could be foundThe motion capture suit has not detected any sensor devices, and the Mocap function cannot be used at all.1) Check whether all sensor connection cables and power are properly connected (the aviation plug must be fully inserted, with the red dot aligned with the groove); 2) Confirm that the motion capture suit main controller is powered on (indicator light flashing slowly, Mocap light solid green); 3) Restart the motion capture suit main controller; 4) If the devices are still not found, check whether the connection order of the upper and lower body of the motion capture suit is correct.
Search device: {e.what()}An exception occurred while the system was searching for devices, and no device was found. {e.what()} is the specific reason.1) Check the specific error description in {e.what()} to confirm the cause; 2) Restart the motion capture suit main controller; 3) Keep the complete {e.what()} content and contact technical support if it persists after a restart.
Not open: {e.what()}The device connection port cannot be opened (usually due to insufficient permissions or the device not existing). {e.what()} contains the specific reason.1) Check the specific error in {e.what()}; 2) Restart the motion capture suit main controller; 3) Do not modify port permissions yourself.
Open failed: {e.what()}The device connection port is occupied by another program. {e.what()} contains the reason for the failure.1) Confirm that no multiple Mocap programs are running at the same time; 2) Restart the motion capture suit main controller to release port resources.
Technician operation: port occupancy and permission inspection

If Not open or Open failed keeps recurring after restarting the motion capture suit, a technician needs to check whether duplicate background Mocap processes are running and whether the port permission configuration is correct. Do not modify system permissions or terminate unknown processes yourself.

4. Network, TeleBox, and Teleoperation Connection​

Error CodeMessageMeaningRecommended Action
can't detect box, auto stop teleop nowThe motion capture suit cannot connect to the TeleBox, and the system automatically stops teleoperation for safety. This indicates that the network between the two devices is broken.1) Check whether the TeleBox is powered on (the indicator light should be normally on); 2) Confirm that the TeleBox network connection is normal (network port indicator light is on); 3) Access the TeleBox management page in the browser (http://10.42.0.3:7876) to test reachability; 4) Re-enable teleoperation after the connection is restored.
Cannot detect suit, scheduling stop teleop if its runningThe TeleBox cannot detect the motion capture suit, and teleoperation will be automatically stopped (safety protection mechanism). This indicates that the network from the TeleBox to the motion capture suit is not reachable.1) Check whether the motion capture suit is powered on (indicator light flashing slowly, Mocap light solid green / blue-green flashing); 2) Check the network connection between the motion capture suit and the TeleBox; 3) Access the motion capture suit management page in the browser (http://10.42.0.2:5000) to test reachability.
session '{session}' terminated unexpectedlyThe teleoperation session {session} was interrupted unexpectedly (may be caused by network disconnection or device overload).1) Record the session name {session}; 2) Check whether the device is overheating or running out of storage space; 3) Please restart the TeleBox software system first and try again; if the problem persists, contact technical support.
run easytier failed!The network connection tool failed to start.1) Check the network connection between the motion capture suit and the TeleBox; 2) Please restart the TeleBox software system first and try again; if the problem persists, contact technical support.
Failed to config data proxyThe data transmission tool configuration failed.1) Record the complete message; 2) Please restart the TeleBox software system first and try again; if the problem persists, contact technical support, and do not modify the service configuration yourself.
{service} {output}A background service is running abnormally. {service} is the service name, and {output} is the current status.1) Record the content of {service} and {output}; 2) Try restarting the motion capture suit main controller; 3) Please restart the TeleBox software system first and try again; if the problem persists, contact technical support.
Service {service} check error: {e}The health check for background service {service} failed. {e} is the specific reason.1) Record the content of {service} and {e}; 2) Try restarting the motion capture suit main controller; 3) Please restart the TeleBox software system first and try again; if the problem persists, contact technical support.
{service} failedBackground service {service} failed to run, and the corresponding function is unavailable.1) Record the service name {service}; 2) Please restart the TeleBox software system first and try again; if the problem persists, contact technical support.
call {start_serveice_name} service failedFailed to call the start service {start_serveice_name}. The function cannot be started.1) Record the service name; 2) Please restart the TeleBox software system first and try again; if the problem persists, contact technical support or the integrator.
call {stop_service_name} service failedFailed to call the stop service {stop_service_name}. The stop operation was not successfully executed.1) Record the service name; 2) Please restart the TeleBox software system first and try again; if the problem persists, contact technical support or the integrator.

5. Robot Data and Synchronization​

Error CodeMessageMeaningRecommended Action
Can't receive {topic} exceed {threshold}sNo data was received for topic {topic} within the specified time, and the recording may be incomplete.1) Check whether the robot industrial PC is powered on and running normally; 2) Confirm that the TeleBox network connection is normal; 3) Have the integrator restart the teleoperation data recording function.
Failed to create subscription for {topic} as {subscription_type}: {e.what()}The TeleBox cannot receive data for topic {topic}. {e.what()} is the specific reason.1) Keep the topic name, type, and full error text; 2) Confirm whether the topic type is supported; 3) Have the integrator check the ROS configuration.
No robot joint state receivedThe TeleBox has not received robot joint state data, so the motion mapping between the operator and the robot cannot be established, and synchronization cannot start.1) Confirm that the robot industrial PC is powered on and the program is running normally; 2) Check the network connection between the motion capture suit and the TeleBox; 3) Have the integrator restart the robot-side control program.
Robot joint state received, ready to sync :)(Info) Robot data has been successfully received, and the system is ready to sync.1) This is part of the normal flow — no troubleshooting needed.
Arm sync recovered(Info) Arm synchronization has recovered. The operator's hand motions can now normally control the robot arms.1) This is a recovery notification; 2) If recovery occurs frequently, check the stability of the VR controller and motion capture data.
Arm sync stopped: VR App controller count doesn't match robot arm countArm synchronization has stopped: the number of VR App controllers does not match the number of robot arms, so the system does not know how to map them.1) Confirm whether the robot has a single arm or dual arms; 2) Check whether the arm count configuration is correct.
RESTART SYNC! (lost vr data at last sync)VR App data was lost during the last sync, and the system forces a restart of synchronization. This is usually caused by Wi-Fi signal fluctuations on the VR App headset.1) Confirm that the Wi-Fi connection of the VR App headset is stable; 2) Move the VR App headset closer to the motion capture suit router (5 GHz signal is better); 3) Restart synchronization; 4) If it occurs frequently, consider using a wired connection.
unknown endtools controller version:{endtools_controller_version}The controller version {endtools_controller_version} of the dexterous hand / end tool is not supported by the system.1) Confirm the currently connected dexterous hand model and version; 2) Contact technical support to confirm version compatibility and check whether an upgrade is needed.
unknown controller version:{controller_version}{controller_version} is not supported by the system, which may cause teleoperation abnormalities.1) Record the controller version {controller_version}; 2) Contact technical support to confirm compatibility.

6. Teleoperation, Collection, and Playback Status​

Error CodeMessageMeaningRecommended Action
Cannot start teleop: {hint}Cannot start teleoperation. {hint} is the specific reason — usually because the system is in playback status.1) Confirm the specific reason based on {hint}; 2) Close playback and try again.
Cannot start: teleop is {status} after waiting stopping.Teleoperation is stuck in an intermediate status, and the new operation cannot be started.1) Stop and start teleoperation again from the interface; 2) If that does not work, restart the device and try again.
Start failed or skipped: {e}Start failed or was skipped. {e} is the specific exception reason.1) Confirm the failure reason based on {e}; 2) Keep the complete error content and contact technical support.
Start process finished but resulted in IDLE. Stop not needed.The start process has completed, but teleoperation did not actually run — some conditions may not have been met during the start process.1) Restart the device and restart teleoperation; 2) Contact technical support if it occurs repeatedly.
Failed to stop {teleop_state}: {type}: {e}Failed to stop teleoperation. {teleop_state} is the teleoperation status, and {e} is the specific reason.1) Confirm the robot is in a safe state, then restart the device; 2) If it occurs repeatedly, contact technical support.
can't start recordCannot start recording data. Possible reasons: insufficient storage space, or the current status does not allow recording.1) Check whether the TeleBox storage space is sufficient; 2) Confirm on the browser management page that the "Store recording files" option is enabled; 3) Save your work and restart the TeleBox to retry.
{SUCCESS_MSG_PREFIX} {msg}(Info) Upload successful. {msg} is the success content.1) Read {msg} to confirm the specific content of the operation completed; 2) No additional action is needed — this is a normal status feedback.
{FAILURE_MSG_PREFIX} {msg}Upload failed. {msg} is the specific reason for the failure.1) Record the failure reason in {msg}; 2) Contact technical support.
Collect config not foundThe configuration file for the data collection mode is not found, and the collection function cannot be started.1) On the browser management page (http://10.42.0.3:7876), select the collection mode and click "Apply Configuration"; 2) Save any work in progress first.
Failed to get system mode, fallback to '{DEFAULT_MODE}' modeFailed to obtain the system running mode. The default mode has been used as a substitute, which may cause the function to be inconsistent with expectations.1) Check the current running mode on the browser management page; 2) If it does not match the requirement, manually switch to the correct mode and apply the configuration.
Unknown ros type: {ros_type}The system cannot identify the robot communication protocol type {ros_type}. The configuration is incorrect.1) Confirm on the browser management page that the communication protocol type is configured correctly; 2) If confirmed correct, contact technical support.
Failed to stop collect: {err}Failed to stop the data collection service. The collection program may be stuck. {err} is the specific error.1) Check the error information in {err}; 2) Check whether the storage space is full, causing the program to be abnormal; 3) Confirm the task is safe, then restart the TeleBox normally.
Failed to start collect services: {err}Failed to start the data collection service. {err} is the specific reason.1) Check {err} to confirm the reason; 2) Check whether the storage space is sufficient; 3) Re-apply the collection mode configuration on the browser management page and try again.
[{state.name} start]{msg}(Info) Data playback status change: a certain state starts (such as playback start). {msg} is the accompanying information.1) Confirm whether the status change matches your operation expectation; 2) If the status is inconsistent with the operation, keep the complete message and contact technical support.
[{state.name} stop]{msg}(Info) Data playback status change: a certain state stops (such as playback end). {msg} is the accompanying information.1) Confirm whether the stop matches expectations; 2) If the status is inconsistent with the operation, keep the complete message and contact technical support.
Cannot start playback: {hint}Cannot play back the recorded data. {hint} is the specific reason — usually because the teleoperation status is incorrect.1) Confirm the reason based on {hint}; 2) Confirm that teleoperation is closed (playback and teleoperation cannot run at the same time).

The management page is at http://10.42.0.3:7876 under some default configurations. If you cannot access it, confirm the current device IP first, and do not change the fixed IP of the computer or the device directly.

No Matching Entry?​

If the error is not in this manual, or it still occurs after following the recommendations, contact technical support and provide the complete message, time of occurrence, software version, device serial numbers, and related screenshots. Logs are collected by personnel with maintenance privileges according to the project process — see Log Collection for details.

For troubleshooting steps for common power, connection, and network symptoms, see Troubleshooting.