Common questions
Answers about automatic discovery, logical names, missing capabilities, subscriptions, and Exo boundaries.
Common questions
Why does automatic discovery fail?
It requires exactly one usable candidate. With multiple devices, run discover_exos() and set an explicit port.
Is name the hardware name?
No. ExoConfig.name is an application-level logical name. ExoDeviceInfo.hardware_name and serial_number are read-only device information.
Why is an IMU or handset missing?
Products and firmware expose different capabilities. Inspect get_device_info().capabilities and components; optional IMU fields may be None.
Why did subscription callbacks stop?
Keep the Subscription alive, start the Exo domain, and make sure a runtime driver is advancing.
Does Exo SDK expose assistance or calibration?
Version 1.0.0 does not expose raw QnTP, firmware/DFU, encoder-zero calibration, wireless provisioning, active assistance, algorithm targets, retargeting, or skeleton APIs.