Troubleshooting

Unable to connect to the glove

1. Check physical connections

   • Is the USB-C cable firmly plugged in with consistent orientation markings?
   • Is the Ethernet cable connected and adapter indicator light on?
   • Is power supply normal (the glove LED should light up and transition to a breathing pattern. Use a USB-A to USB-C cable, since USB-C to USB-C cables cannot power the glove)?

2. Confirm the glove IP

   • Factory default IP: 192.168.1.100 (left hand), 192.168.1.101 (right hand)
   • If the glove IP has been changed via Studio or SDK, replace 192.168.1.100/101 below with the actual configured IP

3. Check network configuration

   • Is the computer IP on the same subnet as the glove (default 192.168.1.x, or the subnet of the configured IP if it's been changed)?
   • Is the subnet mask set to 255.255.255.0?
   • Does the computer IP conflict with the glove (avoid the IP the glove actually uses)?
   • Try ping <glove IP> to verify reachability (with factory defaults, that's ping 192.168.1.100 or ping 192.168.1.101)

Ping replies but can't connect to the glove

A ping reply doesn't guarantee a client (Studio or SDK script) can reach the glove. Rule out network-layer interference first, then look at software-layer causes.

Network layer: ping isn't actually reaching the glove

In multi-NIC environments, ping traffic may be routed to the wrong device:

• Imposter device: another NIC sits on the glove's subnet with an unrelated device occupying the glove IP and answering the ping.
• IP conflict: two NICs on the same machine are both assigned to the glove's subnet (for example, .1 and .3). The OS usually reports a conflict. Even when it doesn't, ping traffic is routed at random between the NICs, producing intermittent replies.

If the NIC actually connected to the glove isn't on the glove's subnet, the client still can't reach the glove.

To resolve (examples below use the factory default 192.168.1.100, replace with the actual glove IP if you've changed it):

1. Unplug the glove and ping the glove IP again:
   • Ping still gets a reply → another device holds that IP. Remove it from this machine's network (unplug its cable, power it off, or drop it from the routing table) so the NIC can no longer reach it.
   • Ping replies are intermittent, or the OS reports an IP conflict → multi-NIC IP conflict. Keep only the NIC connected to the glove on the glove's subnet, and move the other NICs off that subnet or disable them.
2. Plug the glove back in and ping again. If ping still gets no reply, check the IP of the NIC the glove is attached to—it should be on the same subnet as the glove. If not, set it to that subnet (for the default glove IP 192.168.1.100, use something like 192.168.1.50/24).

Helper commands (the 192.168.1.100 below uses the factory default, replace with the actual glove IP if you've changed it):

ip addr show                # List each NIC's IP
ip route get 192.168.1.100  # Check which NIC ping uses
ip neigh show 192.168.1.100 # Compare the responder's MAC with the glove's

Software layer: ping reaches the glove but the client still can't connect

• Make sure no other client (Studio or SDK script) is already connected to the device

• If ufw is enabled on Ubuntu, allow the UDP ports the device uses (50000 for discovery, 50001 for data, with the data port configurable in device settings):

  sudo ufw status
  sudo ufw allow 50000/udp
  sudo ufw allow 50001/udp

• Try restarting the glove (power cycle)

Get technical support

Contact support@wuji.tech with the following information:

• Glove serial number (SN)
• Firmware version
• SDK/Studio version
• Operating system and version
• Steps to reproduce the issue