Troubleshooting

1. OpenLoongVuer Demo Not Working Properly

a. Abnormal Image Feedback

Check Vuer Web Page Status (10.42.0.3:8012)

Web page not opened

Use a laptop with graphics support (integrated or discrete GPU) that can connect to WIFI. Connect to Y2_5G_xxxx WIFI and access the Vuer page at http://10.42.0.3:8012

Normal image display in the upper left corner of the web page showing objects on the desktop

Click the RESTART TELEBOX button in the VR app and refresh the Vuer web page

Image displays normally after restart

Issue resolved

Image still abnormal after restart

Please restart the teleopbox service:

ssh orangepi@10.42.0.3
teleopbox stop
teleopbox restart

Black image in the upper left corner of the web page

1. Click the RESTART TELEBOX button in the VR app
2. Refresh the Vuer web page
3. Check if the image now displays normally, showing objects on the desktop

b. Abnormal Robot Movement

Robot doesn't move after clicking START TELEOP and pressing A

Image displays normally

Click RESTART TELEBOX button in the VR app and refresh the Vuer web page

Movement normal after restart

Issue resolved

Movement still abnormal after restart

Please restart the teleopbox service:

ssh orangepi@10.42.0.3
teleopbox stop
teleopbox restart

Image not displaying normally

Follow the procedures in the "Abnormal Image Feedback" section

2. Unable to Start Motion Capture

START MOCAP failure

Continuous alarm

Check motion capture connection

Occasional alarm

Can be ignored

3. Inaccurate Motion of Motion Capture Avatar

Blue motion capture avatar movements don't match human movements

Calibration not performed

Follow the motion capture suit calibration tutorial

Calibration already performed

Avatar roughly matches human movement after calibration but lacks precision

Follow the calibration tutorial strictly, paying attention to motion capture suit fit and calibration movement direction. If the suit is loose, secure it with straps

Avatar movements significantly different from human movements

Contact your sales representative to check if the motion capture suit's internal parameters are accurate

Avatar movements normal after calibration but abnormal again after device restart

Use soft shutdown to save calibration results; do not directly power off the TeleSuit

4. VR Error Messages

The button panel on the left side of the VR display may show error notifications. Please refer to the following table for troubleshooting.

info

The following content applies only to the out-of-the-box Demo or already adapted robots, not for reference during the adaptation process.
If you encounter alarm messages not listed in the table below, please contact AIO technical support.

Error Message	Explanation	Solution
Unknown robot	Using a robot not supported in the VR resource library. Cannot display the robot model in the VR app	If you're doing your own adaptation, ignore this alarm. Self-adaptation does not currently support robot model visualization and motion synchronization in VR If you're using an AIO-adapted robot, contact AIO technical support
Error fetching time from API	VR cannot get configuration update time from TeleBox	Usually occurs when restarting TeleBox (applying configuration). If the alarm stops after restart, it can be ignored. If the alarm persists, check if the TeleBox connection is normal
Loading Video Port Failed	VR cannot get the WebSocket communication port for the image from TeleBox	Check if the TeleBox connection is normal
No Video Ports Configured	VR cannot get image message configuration from TeleBox	If you don't need to visualize the robot's perception images in VR and haven't configured image transmission on the 10.42.0.3:7876 web page, this can be ignored. Otherwise, check the image-related configuration on the configuration page
teleopbox_launch_robot.service failed	Failed to start VR mapping service	If you're doing your own adaptation, check vr_configs.yml If you're using an AIO-adapted robot, contact AIO technical support
teleopbox_mocap2robot_cmd_v2.service failed	Failed to start motion capture mapping service	If you're doing your own adaptation, check mocap_to_robot_command_v2.yml If you're using an AIO-adapted robot, contact AIO technical support
teleopbox_control_pid.service failed	Failed to start controller service	If you're doing your own adaptation, check controller_v2.yml If you're using an AIO-adapted robot, contact AIO technical support
teleopbox_control_sol_q.service failed
call start_sync failed	Cannot normally start or end synchronization	Ensure teleoperation feature is fully started with the TELEOP button in the STOP TELEOP state before starting or ending synchronization
can't receive xxx exceed xxx	Corresponding messages not received during data recording	Check if data is being published normally Disable unnecessary message recording on the 10.42.0.3:7876 web page