Troubleshooting

1. OpenLoongVuer Demo Not Working

a. Image Feedback Issues

Check Vuer Webpage Status (10.42.0.3:8012)

Cannot Open Webpage

Use a laptop with Wi-Fi and a GPU (integrated or dedicated), connect to the Y2_5G_xxxx Wi-Fi, and visit the Vuer page at http://10.42.0.3:8012

Image Displays Normally in Top Left Corner, Objects Visible

In the VR app, click the RESTART TELEBOX button and refresh the Vuer webpage.

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

Image in Top Left Corner is Completely Black

1. In the VR app, click RESTART TELEBOX.
2. Refresh the Vuer webpage.
3. If the image displays normally and objects are visible, the issue is resolved.

b. Robot Not Moving

Robot Doesn't Move After Clicking START TELEOP and Pressing A

Image Displays Normally

Click RESTART TELEBOX in VR App and Refresh Vuer Webpage

Robot Moves Normally After Restart

Issue resolved.

Robot Still Not Moving After Restart

Please restart the teleopbox service:

ssh orangepi@10.42.0.3
teleopbox stop
teleopbox restart

Image Not Displaying Normally

Refer to the "Image Feedback Issues" section above.

2. Motion Capture Cannot Start

START MOCAP Failed

Continuous Alarms

Check the motion capture connection.

Occasional Alarms

Can be ignored.

3. Motion Capture Avatar Moves Incorrectly

Blue Mocap Avatar Doesn't Match Human Movements

Not Calibrated

Follow the motion capture suit calibration guide.

Already Calibrated

Avatar Movement Roughly Matches but Not Accurate

Follow the calibration guide carefully. Ensure the suit is worn correctly and calibration poses are accurate. If the suit is loose, use straps to secure it.

Avatar Movement Differs Greatly from Human

Contact your sales representative to check the suit's internal parameters.

Avatar Moves Correctly After Calibration, But Not After Reboot

Use a proper shutdown to save calibration results. Do not power off the TeleSuit directly.

4. VR Error Messages

On the left panel in VR, you may see error messages. Please refer to the table below for troubleshooting.

info

The following is for the out-of-the-box demo or robots already adapted for this system. For robots in the adaptation process, please do not use this as a reference.
If you encounter an error not listed below, please contact technical support.

Message	Explanation	Solution
Unknown robot	The robot is not supported by the VR resource library, so its model cannot be displayed in the VR app.	If you are adapting your own robot, ignore this warning. Custom robots are not yet supported for visualization and motion sync in VR. If you are using a robot adapted by us, please contact technical support.
Error fetching time from API	VR cannot get the configuration update time from TeleBox.	Usually occurs when restarting TeleBox (applying configuration). If the warning disappears after restart, it can be ignored. If it persists, check the TeleBox connection.
Loading Video Port Failed	VR cannot get the image WebSocket port from TeleBox.	Check the TeleBox connection.
No Video Ports Configured	VR cannot get image message configuration from TeleBox.	If you do not need to visualize robot perception images in VR and have not configured image transmission at 10.42.0.3:7876, ignore this. Otherwise, check the image configuration on the setup page.
teleopbox_launch_robot.service failed	Failed to start VR mapping service.	If you are adapting your own robot, check vr_configs.yml. If you are using a robot adapted by us, please contact technical support.
teleopbox_mocap2robot_cmd_v2.service failed	Failed to start mocap mapping service.	If you are adapting your own robot, check mocap_to_robot_command_v2.yml. If you are using a robot adapted by us, please contact technical support.
teleopbox_control_pid.service failed	Failed to start controller service.	If you are adapting your own robot, check controller_v2.yml. If you are using a robot adapted by us, please contact technical support.
teleopbox_control_sol_q.service failed
call start_sync failed	Failed to start or stop synchronization.	Ensure teleoperation is fully started and the TELEOP button is in STOP TELEOP state before starting or stopping sync.
can't receive xxx exceed xxx	No corresponding message received during data recording.	Check if the data is being published normally. On the 10.42.0.3:7876 page, disable unnecessary message recording.