XRoboToolkit PC Service

Project notes

Verify a real connection before integrating motion

The reviewed release is v1.0.0, commit 6386009475369615fa984bca0a6e9902cd81eb2a. Upstream lists Windows and Linux builds, including Linux ARM64. Source builds require Qt 6.6.3 and platform-specific compiler/dependency setup. Adjust the hardcoded Qt paths before using the build scripts. For Linux x86_64, start with RoboticsService/qt-gcc.sh; the console example has its own build.sh under its source directory. [1] [2] [4] [6]

After building, run the service and the ConsoleDemo executable produced in the Linux redistributable directory. The example registers a callback with PXREAInit and prints server connection, device discovery, connection and state-data events. Its separate once-per-second liveness message only proves that the example loop is running: it does not check the initialization return value. Look for actual connection and device-data callbacks before treating the transport as working. [3] [4]

Only one service instance is documented. A successful SDK connection is also distinct from receiving valid tracking from a connected device. The README describes head, controller, hand and body data; consumers must handle those formats and coordinate conventions explicitly. No pose conversion or downstream robot compatibility was tested here. [1]

Source and binary scope

The repository root carries Apache-2.0 terms, while its tree also contains platform SDK libraries, redistributable dependencies and Unity demonstration binaries. Those bundled materials should not be assumed to inherit one blanket license. This review inspected a pinned subset of service build, SDK and example sources; it did not compile the service, validate binary provenance or connect a headset. [1] [7]