7 FAQ

Q: Running the example reports: “Package ‘examples’ not found”

Q: Example build failed

  • If colcon is not found, ensure ROS is installed correctly and sourced properly.

  • Check build error logs; if libraries are missing, verify dependency installation.

  • Clear build caches and retry.

Q: After connecting via Ethernet, the examples show no response?

  • Try running ros2 topic list and ros2 topic echo topic_name (replace topic_name with the actual topic) to check system status.

  • Preset motions require the robot to be in the Stable Standing Mode.

  • For TTS/audio playback issues, check the following:

      1. Whether the volume is muted, and whether the TTS text or audio format meets interface requirements.

      1. Verify that the X2 built-in voice interaction system is not disabled.

Q: There is no response when I directly control the motor

If you are controlling the HAL layer directly, the MC module must be stopped.

  • Use aima em stop-app mc to stop the MC module.

  • Restart your program afterward.

Q: When switching to Stand-Ready (Position-Control Standing) mode, the legs don’t respond and the arms move slowly

  • Low battery may prevent power delivery to the legs; replace with a sufficiently charged battery.

Q: Robot service calls have no response

  • Verify that all service request fields are correctly set.

Q: Error when using cv_bridge on the robot (Assertion failed: s >= 0 in function 'setSize')

  • Check the OpenCV version used during compilation:
    The robot environment includes both Nvidia-supplied OpenCV and Ubuntu repository OpenCV.
    When using cv_bridge, you must link against the Ubuntu-sourced OpenCV.

Q: A node launched by systemd service cannot receive ROS topic messages

  • Check whether you can subscribe to the target topic in an SSH terminal.

  • Ensure the AgiBot DDS config and environment variables are loaded at startup by running source /agibot/data/home/agi/.aima/env/bashrc.

Q: Why can I only use limited system-level commands?

  • X2 introduces a filesystem isolation sandbox. User programs run in an isolated agi rootfs environment, separated from the system rootfs.

  • Advantage: users can freely install packages and dependencies (e.g. pip install, apt install) inside the sandbox without affecting robot system stability.

  • Limitations:

    • Only limited system-level commands are available, such as sudo apt, sudo nmcli, sudo nmtui, sudo ifconfig, etc.

    • docker is not yet supported; please contact after-sales technical support if needed.

Q: How to configure auto-start services on boot?

  • systemd only supports systemctl --user user-level services, system-level systemctl is not available.

  • Programs in a service must be launched via /usr/bin/agirun, e.g. ExecStart=/usr/bin/agirun /bin/bash /path/to/your_script.sh.