Skip to main content

FAQ | Common Issues & Troubleshooting

This document summarizes common issues encountered when using the SDK, teleoperation system, and robot platform, along with recommended troubleshooting steps.

1. Control Interference When Operating Multiple Robots​

Symptom​

When multiple robots are connected to the same network and controlled through the SDK, commands may interfere with each other, causing unexpected robot behavior.

Cause​

Multiple robots are configured with the same domainid, resulting in DDS communication conflicts.

Solution​

  • Verify the domainid configuration of each robot and control device.
  • Ensure that every robot on the same network uses a unique domainid.
  • If Aurora fails to start, also check for duplicate domainid settings.

Note: Duplicate domainid values may cause communication conflicts and startup failures.

2. Control Session Is Unexpectedly Interrupted​

Symptom​

The robot suddenly stops responding to control commands during operation.

Cause​

The robot's safety protection mechanism has detected an abnormal posture or potentially unsafe condition and automatically disabled control.

Solution​

  1. Check the robot's current posture and stability.
  2. Ensure the robot is not tilted, unstable, or in a hazardous state.
  3. Once the abnormal condition is resolved, reconnect and resume operation.

Safety First: The system automatically disables control when unsafe conditions are detected.

3. Unexpected Behavior After Switching to PD Stand Mode​

Symptom​

A control example or application does not behave as expected after switching the robot to PD Stand mode.

Cause​

The robot has not fully stabilized in a standing position before the control program starts.

Solution​

  1. Ensure the robot is standing firmly on the ground.
  2. Verify that the robot has reached a stable posture.
  3. Start the control application only after the robot is fully stabilized.

4. Aurora Fails to Start After Replacing a Dexterous Hand or End Effector​

Symptom​

Aurora fails to launch after replacing a dexterous hand, gripper, or other end effector.

Cause​

During startup, Aurora performs hardware verification checks. Startup may fail if:

  • Required IP devices are missing.
  • The detected hardware configuration differs from the expected configuration.
  • A custom end effector has been installed without the corresponding configuration.

Solution​

Scenario 1: Initialization Failure​

Check the following:

  • All devices are powered on.
  • Network connections are functioning correctly.
  • The expected number of IP devices is detected.

Scenario 2: Custom End Effector Installed​

  • Ensure the new end effector is properly configured.
  • Use the corresponding software configuration and control profile for the installed hardware.

Aurora validates hardware consistency during startup to ensure safe operation.

5. Actuator Overheating or Robot Falls​

Symptom​

  • Actuator temperature becomes excessively high.
  • The robot falls or loses balance.

Solution​

  1. Immediately stop all operations.
  2. Power off the robot.
  3. Allow the system to cool down completely.
  4. Inspect the robot and operating environment before restarting.

Warning: Continuing operation while actuators are overheated may result in hardware damage.

6. Software UI or Control Abnormalities​

Symptom​

One or more of the following issues may occur:

  • Application error pop-ups
  • Status indicators not updating
  • Unexpected motion behavior
  • Unresponsive control interface
  • Robot moving without intended control input

Solution​

Option 1: Restart the Application​

  • Force-close the application.
  • Reopen the application and reconnect.

Option 2: Restart the System​

  • Restart the robot.
  • Restart the controller or host device if necessary.

Option 3: Emergency Stop for Uncontrolled Motion​

If the robot continues moving unexpectedly:

  • Immediately move the control joystick in the opposite direction.
  • Verify that the robot has stopped before troubleshooting further.

Option 4: Prevent Accidental Inputs​

Enable forced landscape mode on the controller device to reduce unintended screen touches and control errors.

Contact Support

If the issue persists after following the steps above, please collect the following information before contacting technical support:

  • Robot model
  • Software version
  • Aurora version
  • Time of occurrence
  • Reproduction steps
  • System logs (if available)
  • Photos or screen recordings (if available)

Providing these details will help our support team diagnose and resolve the issue more efficiently.