Skip to main content
This page covers recovery from a lost connection, device reboot, what survives a reboot for parameters and calibration output, plus the user-serviceable boundary, daily checks, storage requirements, and firmware updates. To diagnose by symptom, see Troubleshooting.

Connection Loss and Recovery

The glove has no joint motors, so recovery involves no stop behavior. Recovery escalates in three steps: free the client connection, reboot the device, then power-cycle it. The indicator light on the data acquisition board shows the current state.

Connection States and the Indicator Light

The color and blink pattern of the indicator light map to the glove’s current state, and a higher-priority state overrides the display of a lower-priority one: For all 11 states and their priorities, see Product Introduction.

Free Up an Occupied Device Connection

Only one client holds the glove connection at a time. When wuji viz and an SDK script connect to the same glove one after another, the second one can’t establish a connection. Exit the running client before switching, then connect again. For the full path when ping replies but the connection still fails, see Software layer.

Reboot the Device

Reboot the glove from the SDK when a parameter needs a reboot to take effect, or when a stream stops updating for a long time:
After the reboot, the device returns to standby and accepts a new connection. If the SDK doesn’t respond, power the device down and back up.

What Survives a Reboot

A reboot or a power cycle leaves the following data intact: Hand model writes go through an atomic replace, so a failed calibration keeps the last successful output and the run can be retried. For the storage rules, see Where Calibration Is Stored in SDK Reference. After an IP address change that leaves the host NIC and the glove on different subnets, the device drops off the scan list. Reconfigure the host NIC as described in Unable to connect to the glove to bring it back.

Checks After Recovery

wuji devices lists the devices on the subnet, wuji doctor checks EMF disconnections and tactile dead points, rows, and columns, and wuji sub tactile --count 1 exits once it receives one frame. All three passing means the link is back.

Maintenance and Routine Checks

The glove body and cabling follow the wearing and routing requirements, daily checks cover appearance, cables, and the indicator light, and both firmware upgrades and log export run through the Wuji CLI.

What You Can Service

The tactile array sits inside the palm-side fabric and the EMF receiver coils sit inside the fingertip housings, and neither comes apart on its own. Contact support if a sensor area shows physical damage.

Daily Checks

Confirm before each use:
  • The sensor areas lie flat, with no folds
  • Fingers stay slightly bent and relaxed, without crossing the fingertip EMF modules or making a fist
  • Both ends of the USB-C to USB-C cable face the same way, the Ethernet cable is seated, and the adapter indicator is lit
  • The board indicator reaches cyan breathing, which means standby waiting for a host connection
Run wuji doctor regularly to check EMF disconnections and tactile dead points, rows, and columns. For usage, see Wuji CLI health diagnostics.
The tactile check needs the glove placed statically. Wearing or pressing it produces false positives.

Storage and Environment

  • Storage: keep the glove in a dry, cool place and avoid folding the sensor areas
  • Operating environment: temperature -5 to 40 °C, humidity below 55% RH
  • Storage environment: temperature -10 to 70 °C, humidity below 80% RH
  • EMF interference: the sensing is sensitive to metal and ferromagnetic materials, so keep a clearance of 3 cm or more. Stay away from metal objects and electronics in use, and keep the hand within 30 cm of the transmitter coil

Firmware and Software Updates

The Wuji CLI pulls the matching firmware version from the official firmware source, verifies it, flashes it, and prints a per-device report:
--check is read-only and lists which devices have a firmware update. --type wuji_glove upgrades every glove in scope to its own latest version, and each device reboots into the new firmware once flashing finishes. For the full scope and action options, see Wuji CLI firmware upgrade. The calibration interfaces have minimum firmware and SDK versions. For the pairing, see the component version table in Release Notes.

Support

Export a log support bundle before contacting support:
The command writes a timestamped ZIP bundle to the current directory, containing text logs, host and device diagnostics, hand model calibration recordings, and a file manifest. Send the bundle to [email protected] together with the glove serial number, firmware version, SDK and CLI versions, operating system version, and reproduction steps. For the options, see Wuji CLI log export.