05.01 Commercial Deployment Troubleshooting

Open manual menu
  1. Business Customer / Developer Integration Manual
  2. 5.1 Commercial Deployment Troubleshooting

5.1 Troubleshooting Commercial Deployments

First determine whether the issue involves power, the channel configuration, fit and calibration, an optional capability, or customer integration. Do not substitute consumer pairing or firmware flashing for troubleshooting.

Checks by Symptom

Symptom Check First Stop Condition
No data from the receiver USB connection, project device permissions, and whether the receiver belongs to the current channel group Still not detected after changing ports
Gloves do not connect automatically Glove power, receiver configuration, and asset and channel records Do not enter the consumer pairing process
Left and right gloves or multiple device sets are swapped Disconnect one set at a time and reconnect each set according to its asset ID Channel records cannot be matched
Finger data jumps or movements are abnormal Fit, TMR/N52 position, and Menu button calibration The issue persists after recalibrating once
No response from haptic feedback or buttons Whether the order includes the capability, the project test entry point, and the current version No approved test method is available
No data in the SDK or customer application Hardware baseline, SDK version, runtime environment, and minimum data path The version source cannot be confirmed

Troubleshooting Sequence

  1. Reproduce the issue with one device set first; do not make simultaneous changes in a multiple-device environment.
  2. Verify the gloves, receiver, and channel group.
  3. Check fit and the TMR/N52 position, then calibrate once according to the project instructions.
  4. After confirming hardware data, check the SDK and customer application.
  5. Retain the complete symptom and version information; do not submit only partial screenshots.

Prohibited Actions

Do not pair devices, change channels, disassemble devices, flash firmware, substitute an SDK from an unknown source, or use a receiver from another project.

Next Step

If the issue remains unresolved, prepare the required information according to 5.2 Information to Submit When Contacting Technical Support.