Common questions
Answers about C++ package linking, discovery, logical names, optional capabilities, and handle lifetime.
Current version · 1.0.0
Common questions
Why did CMake link the wrong Core?
Exo 1.0.0 package metadata pairs with Core 1.4.0. Clear the old build tree and ensure CMAKE_PREFIX_PATH contains no earlier version.
Why must automatic discovery find one device?
A configuration without a port must resolve one physical device. For multiple devices, discover first and give every ExoConfig an explicit port and logical name.
Why is an IMU std::nullopt?
The hardware may not expose it. Inspect capabilities.imus and components.imus first.
Why did subscription callbacks stop?
Keep the Subscription value alive and ensure the Exo domain is started and a runtime driver is advancing.
Are assistance or calibration APIs available?
Version 1.0.0 does not expose raw QnTP, DFU, encoder-zero calibration, wireless provisioning, active assistance, algorithm targets, retargeting, or skeleton APIs.