Fusion sensor implementation details
This section provides implementation details about the Windows fusion sensor driver stack.
Note
Microsoft provides fusion driver binaries on some platforms and these cannot be replaced by partners.
The following diagram shows the sensor fusion software stack.
The fusion software stack consists of the following components:
- The sensor native APIs are called by applications to access fusion and compass features and functionality. The APIs are wrappers for ReadFile and DeviceIoControl. These APIs are sent to the sensor class extension, which then processes and completes the request.
- The sensor class extension provides support for any required sensor-specific extensibility.
- The fusion driver is the function-specific software part of the driver. It reads the physical sensors and processes the data. The algorithm for the compass and fusion sensor is implemented in this component.
The coordinate system shown in the following diagram is used for all physical sensors and fusion data.
The coordinate system shown in the following diagram is the convention used by the fusion algorithm and APIs for all vectors in the Earth/ground frame of reference.
The following structures and enumerations are used by the fusion data part of the logical sensor driver:
Fusion sensor enumerations and Fusion sensor structures provide information about the entire sensor fusion data structure, which include the attitude (in multiple formats) and the linear acceleration, and the compass data.