Skip to main content

Troubleshooting

tip

This chapter covers troubleshooting for common power, connection, network, and software issues during teleoperation. Do not attempt any operation that is not explicitly described here; do not disassemble the device, modify system configurations, or run commands from unknown sources.

If the content in this chapter cannot solve your problem, please refer to the Log Collection section to complete related operations and contact technical support. If an English error message appears on screen, search for it in the Error Messages Reference first.

Quick Navigation​

ContentJump to
Quick checkThree steps before you start
Pre-use checksPre-use Checks
Common issuesPower & Device Connection · Network & Communication · Calibration & Motion Capture · VR Application · Teleoperation & Data
Daily useDaily Use Notes · Device Shutdown
After-salesInformation to Provide When Contacting Support

Three Steps Before You Start​

Check in order. As soon as you find an abnormality at one step, handle that item first — there is no need to keep checking the remaining steps.

Step 1: Check whether the devices are OK​

  • Are the TeleSuit, TeleBox, and VR headset all powered on?
  • Are the power adapter and device indicator lights normal?
  • Are the network cable, aviation plug, and glove harnesses firmly connected, without looseness or damage?
  • Is any device abnormally hot, making unusual noises, or emitting a burning smell?

If you notice a burning smell, smoke, or abnormal heat, cut the power immediately and contact after-sales service. Do not continue troubleshooting.

Step 2: Check whether the devices are connected to each other​

  • Do the TeleSuit and TeleBox belong to the same set, with matching serial numbers (SN)?
  • Is each device connected to the correct network?
  • When using a wired connection, is the network port connected correctly?
  • When the computer is connected to both Wi-Fi and a network cable, can it not reach the devices due to a network path issue?

You can disconnect unrelated networks first, then test the connection again. When multiple sets are in use, also confirm there is no cross-connection.

Step 3: Check whether the pages and data are normal​

  • Can the front-end page http://device-IP:7876 be opened?
  • Can Mocap receive data from both hands?
  • Can VR receive data and cast normally?
  • Do the TeleSuit and TeleBox software versions match?
  • Do stuttering, latency, or explicit errors occur during operation?

If the first two steps are normal but a page will not open, data is missing, or errors persist, record the error content, device serial numbers, and software versions, then continue with the matching item below.

Pre-use Checks​

These checks rule out most problems before you start. For the full site, personnel, and device requirements, see Safety Instructions and Standard Usage.

Check devices and cables​

  • The power adapter works normally, with no abnormal indicator light status
  • Network cable, aviation plug, and glove harnesses are firmly connected, without damage or looseness
  • The TeleSuit and TeleBox belong to the same set, with matching serial numbers (SN)
  • When multiple sets are in use, no set is cross-connected with another
  • The devices are well ventilated, and ports and vents are not blocked

Confirm the connector orientation before plugging or unplugging cables, and never force them in. If the aviation plug is loose, makes unusual noises, or cannot be locked, stop using it and contact after-sales service.

Check the network​

  1. Confirm the Wi-Fi you need to connect to based on the TeleSuit label, and do not connect to another device's hotspot.
  2. When using a wired connection, confirm the device port connects to the TeleSuit and the interactive port connects to the computer or industrial PC. For port definitions and connection topology, see Site Network Reference.
  3. The TeleSuit, TeleBox, and the terminals involved in the operation should be on the correct network and able to communicate with each other.
  4. If the computer cannot reach the devices when connected to both Wi-Fi and a network cable, temporarily disable the unrelated network and test again.

In complex network environments, enabling multiple network interfaces at the same time can cause access traffic to take the wrong path, though this is not necessarily an IP conflict. If the problem persists after adjustment, keep the current network configuration and contact after-sales service.

If wireless relay is enabled on the router but not connected to an upstream router, VR may report a Wi-Fi disconnection. When wireless relay is not needed, log in to the router management page to disable it; if you are not familiar with router settings, contact the on-site network administrator or after-sales service.

Check the software version​

Record the TeleSuit and TeleBox software versions and confirm they match. When an upgrade is needed, refer to Software Upgrade and contact after-sales service first to confirm the version and timing.

Power & Device Connection​

1. TeleSuit cannot connect and the power box shows a red light​

Symptom: The middle indicator on the power box keeps flashing or turns red, and VR reports no data.

Solution:

  1. Check the power box power supply and cable connections.
  2. Power off the TeleSuit, wait 10 seconds, then power it on again.
  3. Confirm the TeleSuit and TeleBox use the correct network and are not cross-connected with another set.
  4. Record the TeleSuit and TeleBox software versions.

Some older versions may show similar problems. Whether an upgrade is needed should be judged by after-sales service based on your current version. If the red light persists after a restart, do not disassemble the device — contact after-sales service directly.

2. VR cannot obtain an IP when connected to the TeleSuit via a wired connection​

Symptom: Occasionally cannot obtain an IP when directly connected to the TeleSuit via a network cable.

Solution:

  1. Check whether the network cable and port are firmly connected. For port definitions, see Site Network Reference.
  2. Power off the VR headset, restart the related devices normally, then reconnect.

If the problem recurs, record the connection method, the port indicator status, and whether VR can connect normally over Wi-Fi, then contact after-sales service.

3. TeleBox network port does not obtain an IP​

Symptom: The network port on the TeleBox interactive port does not obtain an IP.

Solution:

  1. Check whether the TeleBox network port indicator light is normally on.
  2. If the light is off, check whether both ends of the network cable are firmly plugged in, and try a known-good network cable or switch port.
  3. If the light is normal but there is still no IP, access http://10.42.0.3:7876 and re-Apply Configuration.

The front-end address depends on the actual device IP. If you cannot open the front end, or there is still no IP after applying the configuration, record the network port indicator status and contact after-sales service.

4. TeleBox cannot connect to the TeleSuit after switching from remote mode to collection mode​

Symptom: After the TeleBox switches from remote mode to collection mode, it cannot connect to the TeleSuit over a network cable.

Solution: Log out of the remote account in VR, then the connection works normally.

5. First-time wireless module pairing with the PC on 5G WiFi prevents the module from connecting to the TeleSuit​

Symptom: When pairing the wireless module for the first time, if the PC is connected to 5G WiFi, the wireless module cannot connect to the TeleSuit.

Solution: When pairing the wireless module, the PC must be connected to the router's 2.4G WiFi.

Check Wi-Fi signal strength

If the wireless module network connection is unstable, run the following command in a terminal on the PC running the motion capture software (Ubuntu) to list the available Wi-Fi networks and their signal strength:

nmcli device wifi list

Use the SIGNAL value in the output to determine whether there is interference or excessive distance, then move closer to the router or re-run network configuration.

Network & Communication​

6. TeleSuit IPs obtained over WiFi and wired connection are in different subnets​

Symptom: When connecting to the TeleSuit over WiFi and over a wired connection, the assigned IPs are not in the same subnet.

Solution:

  1. Check whether other DHCP services are running.
  2. Check whether any device connected to the TeleSuit over a wired connection has started another DHCP service.

If the checks above do not locate the cause, you can change the WiFi password and reconnect to narrow down the device running the DHCP service.

Technician operation: locating the DHCP conflict step by step
  • Disconnect the devices connected to the TeleSuit over a wired connection one by one. After each disconnection, reconnect WiFi and observe whether the assigned IP returns to the same subnet.
  • Once the specific device is identified, disable the DHCP service on it or adjust its subnet configuration.
  • Keep the original network configuration during troubleshooting. Do not change the fixed IP of the TeleSuit or TeleBox.

7. TeleBox cannot access the network after switching to upload mode​

Symptom: After the TeleBox switches to upload mode and the network cable is connected again, the network is unavailable.

Solution: Access http://10.42.0.3:7876 and re-Apply Configuration to make the network take effect.

8. The 8686 web front end cannot refresh normally​

Symptom: When accessing the http://10.42.0.2:8686 page, the front end cannot refresh normally.

Solution:

  1. Clear the browser cache, then reopen the page.
  2. Reopen it in a Chrome incognito window, or try another browser.

If it still cannot refresh, record the access address, the browser error, and the device indicator status, then contact after-sales service. Restarting the front-end service is a technical maintenance operation — do not perform it yourself.

9. WiFi disconnection alert caused by wireless relay​

Symptom: When wireless relay is enabled but not connected to an upstream router, VR detects a WiFi disconnection and triggers an alert.

Solution: Connect to the device's WiFi, enter the router management page, and disable wireless relay when not in use. If you are not familiar with router settings, contact the on-site network administrator or after-sales service.

10. TeleSuit and TeleBox cannot communicate, and no TeleBox topics are received​

Symptom: The TeleSuit and TeleBox cannot communicate, no TeleBox topics are received, and teleoperation cannot start.

Solution:

  1. Confirm the TeleSuit and TeleBox are connected to the correct network. For port definitions and connection topology, see Site Network Reference.
  2. Check whether the two ends can communicate with each other.
  3. Confirm the TeleSuit and TeleBox are not cross-connected with another set.
  4. Record the software versions on both ends and confirm they match.
  5. Restart the TeleSuit and TeleBox normally, then test again.
Technician operation: data_proxy service and ROS domain configuration

If communication still fails after the checks above, the data_proxy service status and the ROS domain (domain id) configuration need to be inspected. These items should be handled by a technician with maintenance privileges or by after-sales service; do not modify them yourself.

11. ROS2 cannot communicate for teleoperation​

Symptom: When the robot uses ROS2, it cannot communicate with the TeleBox, causing teleoperation abnormalities.

Solution: Configure the discovery server address pointing to box_ip:11811 for the device connected to the TeleBox, so that ROS2 data can be obtained.

box_ip should be replaced with the actual IP of the current TeleBox. This is robot integration configuration and should be performed by an integrator. Do not modify the ROS2 configuration yourself; contact after-sales service if needed.

12. Teleoperation stutters or is delayed​

Symptom: Robot motions are out of sync, joint states drop frames, or delays of several seconds occur.

Solution:

  1. Confirm whether you are using a wired or wireless network, and prefer a stable wired connection when conditions allow.
  2. Check whether the network carries heavy traffic such as downloads, casting, or video transmission, and test again after stopping them.
  3. Confirm the TeleSuit, TeleBox, and industrial PC software versions match.
  4. Confirm the industrial PC is not running unnecessary high-load programs.
  5. If stuttering appears only after a long run, save your work and restart the devices normally.

If the problem can be reproduced reliably, record the time, the delay behavior, and the network connection in use, then contact after-sales service. Checking resource usage and service status should be done by a technician.

Calibration & Motion Capture​

13. No voice announcement during calibration​

Symptom: No voice announcement during the calibration process.

Solution:

  1. Check the wiring of the motion capture suit and gloves.
  2. Disable Mocap.
  3. Handle and clear the existing alerts as prompted on screen. Errors when Mocap is enabled will interrupt the voice announcement.
  4. Wait about 5 seconds, re-enable Mocap, then start calibration.

If the alerts cannot be cleared, capture a screenshot of the alert page and contact after-sales service.

14. Inaccurate motion capture calibration or stuttering calibration animation​

Symptom: Unstable calibration results, abnormal postures such as inward-collapsing knees, or a stuttering calibration animation.

Solution:

  1. Perform the calibration motions as prompted on screen, with sufficient range and correct posture; keep the environment spacious, avoid occlusion, and stay away from devices that may cause magnetic interference.
  2. Check whether the motion capture suit and sensors are worn correctly.
  3. Check whether the network is stable.
  4. Exit the current calibration flow, confirm the devices are in a normal state, then calibrate once more.

Do not calibrate repeatedly in quick succession. If the same problem occurs multiple times, keep the abnormal screen or recording and contact after-sales service.

15. Guide character is not in frame during full automatic calibration​

Symptom: When clicking full automatic calibration, the motion capture guide character is not in the frame.

Solution: Enable the global positioning function, then re-enter full automatic calibration and confirm whether the guide view returns to normal.

If the global positioning option cannot be found, or the problem persists after enabling it, record the software version and contact after-sales service.

16. Motion capture character does not move after Mocap is enabled​

Symptom: After Mocap is enabled, the motion capture character does not move.

Solution:

  1. Disable Mocap, wait a few seconds, then re-enable it.
  2. If it still does not recover, exit the VR APP and re-enter.
  3. Check whether other error alerts are displayed on screen at the same time.

If there is still no motion data after repeated restarts, do not continue calibrating. Check the connection following the "VR reports No data available" item.

17. Only one hand has data after Mocap is enabled​

Symptom: After Mocap is enabled, only one side of the hand has data.

Solution:

  1. Check whether the glove cable on the side with no data is loose or damaged.
  2. Power off the related devices, then firmly reconnect that side's cable.
  3. Restart Mocap and check whether the data recovers.

If only one side still has data after reconnecting, the cable or glove hardware usually needs further inspection — contact after-sales service.

18. Abnormal Mocap or Teleop issues​

Symptom: Restarting the TeleSuit while Mocap or Teleop is open may, with some probability, prevent them from being enabled normally again.

Solution: Access http://10.42.0.3:7876, re-Apply Configuration, then exit VR and re-enter the APP to recover.

VR Application​

19. VR reports No data available​

Symptom: VR displays No data available.

Solution: This message means VR is not receiving data at the moment — it is not necessarily a VR fault. Check in order:

  1. Whether the TeleSuit is powered on normally, with no abnormal indicator status.
  2. Whether the TeleSuit and TeleBox are connected to the correct network.
  3. Whether the TeleSuit and TeleBox belong to the same set.
  4. Whether communication between the TeleBox and VR is normal.

If all of the above are normal, search for the specific error on screen in the Error Messages Reference.

20. VR APP installation failure​

Symptom: Installing the APP in VR fails (occasional).

Solution:

  1. Uninstall the APP first, then reinstall.
  2. Confirm the VR headset has sufficient storage space, restart the headset, then try again.
Technician operation: uninstall via ADB and reinstall

If installation still fails, a technician can uninstall it via ADB and reinstall:

adb uninstall com.ioai.TeleXperiencebeta

21. VR login failure or network error​

Symptom: VR login fails, or a network error is reported.

Solution: Domestic devices and overseas accounts may have different network and account region requirements. First confirm the VR headset can access the network normally, then verify the account region and login environment. If a network error appears during login, connect to another available network to complete account login, then switch back to the TeleSuit Wi-Fi for operation.

Do not conclude that the device is faulty simply because login failed.

22. VR casting failure​

Symptom: The VR view cannot be cast to the computer.

Solution: Before casting, confirm the VR headset and the computer receiving the cast are on the same network. Some casting methods do not support the current wired connection scheme and require a mutually reachable wireless network instead.

If casting still fails, check separately:

  1. Whether the VR headset is connected to the network.
  2. Whether the computer can access other devices on the same network.
  3. Whether the VR headset and the computer are connected to different hotspots.
  4. Whether the current casting method supports the network in use.

23. Abnormal scene when entering the APP while screen recording​

Symptom: When entering the APP during screen recording and pressing the A key to enter the safety notice, the entire scene follows head movement.

Solution: Do not start screen recording immediately when entering the APP. Exit the app, stop screen recording, then re-enter; start screen recording only after entering the APP and completing the initial page operations.

24. VR view changes after modifying camera resolution​

Symptom: After modifying the camera resolution, the camera view in VR changes.

Solution:

  1. After changing the camera settings, restart the teleoperation devices.
  2. If a restart is inconvenient, access http://10.42.0.3:7876 and re-Apply Configuration.

Save any work in progress before applying the configuration.

Teleoperation & Data​

25. Teleop service error after TeleBox power restart​

Symptom: After a TeleBox power restart, pressing the A key when starting Teleop sync for the first time causes a service error.

Solution: Disable and re-enable Teleop.

Prevention: Never cut the power directly; doing so over a long period may cause storage card or file system problems. Shut down the device by following TeleBox Shutdown before disconnecting power.

26. VR video artifacts​

Symptom: VR video artifacts (occasional). Applies to OpenLongVuer on ROS1.

Operations tried without effect: restarting the VR APP, connecting VR directly with a network cable, re-applying the configuration.

Other observations:

  1. When the H264 display tool is opened, the video displays normally.
  2. After switching to ROS2 (domain id not 0), the artifacts disappear; after switching back to ROS1, the artifacts did not reappear. After setting the ROS1 domain id to 0, the artifacts also did not reappear.

Temporary workaround: Switch to ROS2, then switch back to ROS1.

The root cause is still under analysis. Contact technical support if you need a permanent fix.

Daily Use Notes​

  • When the devices are not in use, shut them down by following Device Shutdown before disconnecting the power; do not leave them powered on and idle for long periods.
  • If abnormalities appear after a long run, save your work first, then restart the devices normally.

For ventilation, cable handling, storage, and other usage and maintenance requirements, as well as the shutdown steps, see Standard Usage.

Information to Provide When Contacting Support​

To help us locate the problem faster, please provide the following when contacting technical support:

  • TeleSuit and TeleBox software versions
  • Serial numbers (SN) of the TeleSuit, TeleBox, and related accessories
  • Fault symptoms, time of occurrence, and operation steps
  • Indicator light colors and flashing states
  • Current network connection method and device connection relationships
  • Troubleshooting steps already attempted
  • Routine shutdown method (whether the devices are shut down by following Device Shutdown, whether power is often cut directly), which helps determine whether the problem is related to long-term direct power cuts
  • Error screenshots, abnormal recordings, or logs (if available)

If an English error message appears on screen, keep the full message content and search for it in the Error Messages Reference first. Logs are collected by personnel with maintenance privileges according to the project process.