Fault Diagnostics
tip
If the content in this chapter cannot solve your problem, please refer to the Log Collection section to complete related operations and contact your sales representative for feedback.
Common Issues and Solutions
WiFi Disconnection Alert Caused by Wireless Relay
- Symptom: When wireless relay is enabled but not connected to an upstream router, VR will detect WiFi disconnection and trigger an alert.
- Solution: Connect to the device's WiFi, enter the router management page, and disable wireless relay when not in use.
Mocap or Teleop Abnormal Issues
- Symptom: When Mocap or Teleop is restarted while enabled, there is a certain probability that they cannot be enabled again normally.
- Solution: Access the http://10.42.0.3:7876 webpage, re-Apply Configuration, then exit VR and re-enter the APP to recover.
No Voice Announcement During Motion Capture Calibration
- Symptom: No voice announcement during calibration process.
- Solution: Errors when Mocap is enabled will cause voice announcement interruption. Check wiring, close Mocap, clear error alerts, wait about 5 seconds, then re-enable Mocap for calibration.
Teleop Service Error After Box Power Restart
- Symptom: After Box power restart, pressing A key when starting Teleop sync for the first time causes service error.
- Solution: Close and re-enable Teleop.
Motion Capture Character Cannot Move After Mocap Enabled
- Symptom: After Mocap is enabled, the motion capture character does not move.
- Solution: Close and re-enable Mocap, or exit VR APP and re-enter.
View Changes After Modifying Camera Resolution
- Symptom: After modifying camera resolution, camera view in VR changes.
- Solution: After modifying camera settings, restart the teleoperation device, or access http://10.42.0.3:7876 webpage to re-Apply Configuration.
VR Cannot Obtain IP When Connected to Suit via Wired Connection
- Symptom: Occasionally cannot obtain IP when directly connected to Suit via wired connection.
- Solution: Close VR and restart the device. After restart, IP can be obtained normally.
ROS2 Cannot Communicate for Teleoperation
- Symptom: When robot uses ROS2, cannot communicate with Box, causing teleoperation abnormalities.
- Solution: Configure the discovery server address pointing to box_ip:11811 for the device connected to Box to ensure ROS2 data can be obtained.
Box Network Port Not Obtaining IP
- Symptom: Box interactive port network port is not obtaining IP.
- Solution:
- Check if Box network port indicator light is normal.
- If light is off, unplug and replug network cable; if light is on, re-access http://10.42.0.3:7876 and Apply Configuration.
Box Cannot Connect to Internet After Switching to Upload Mode
- Symptom: After Box switches to upload mode and network cable is connected again, network is unavailable.
- Solution: Access http://10.42.0.3:7876 webpage and re-Apply Configuration to make network effective.
Suit IPs in Different Subnets via WiFi and Wired Connection
- Symptom: When connecting to Suit via WiFi and wired connection, assigned IPs are not in the same subnet.
- Solution:
- Check if other DHCP services are running.
- Check if devices connected to Suit via wired connection have started other DHCP services.
- Modify WiFi password and reconnect, gradually identify devices starting DHCP services.
VR APP Installation Failure
- Symptom: Installation failure when installing APP in VR (occasional).
- Solution:
- Uninstall APP first, then reinstall.
- If still fails, use ADB command to uninstall:
adb uninstall com.ioai.TeleXperiencebeta
Abnormal Scene When Entering APP During Screen Recording
- Symptom: When entering APP during screen recording and pressing A key to enter safety notice, the entire scene follows head movement.
- Solution: Do not start screen recording immediately when entering APP. Start screen recording after entering.
Calibration Guide Character Not in Frame
- Symptom: When clicking full automatic calibration, motion capture guide character is not in the frame.
- Solution: Enable global positioning function.
8686 Webpage Frontend Cannot Refresh Normally
- Symptom: When accessing http://10.42.0.2:8686 webpage, frontend cannot refresh normally.
- Solution: Clear browser cache, then reopen the webpage.