Examples of C++ API usage for LPMS-B2 using OpenZen

[mxochicale]

Let's quickly add a README, built workflow and modified version of the following scripts as examples of C++ API usage for LPMS-B2 using OpenZen.

• https://bitbucket.org/lpresearch/openzen/src/master/examples/ExampleCpp.cpp
• https://bitbucket.org/lpresearch/openzen/src/master/examples/ExampleCpp17.cpp
• https://bitbucket.org/lpresearch/openzen/src/master/examples/CMakeLists.txt

Notes

• Check or test other CMakeList.txt options from https://bitbucket.org/lpresearch/openzen/src/master/examples/CMakeLists.txt

target_link_libraries(OpenZenExample
    PRIVATE
        OpenZen
        GSL
        Threads::Threads
        spdlog
)

• "C++17 more convenient return types"
  """
  By default, the C++14 API will be used. If your project uses C++17 for compilation, the C++17 API will be automatically used. You can also force the usage of the C++17 API by defining the preprocessor variable OPENZEN_CXX17. The C++14 and C++17 APIs have the same method names but the C++17 uses more convenient return types via the std::optional class.
  A complete example of the C++ API usage can be found at this example source file.
  """
  https://lpresearch.bitbucket.io/openzen/latest/cpp_api.html

• "Synchronizing multiple Sensors"
  """
  If multiple sensor are connected to the same OpenZen instance, they can be synchronized by putting them into synchronization mode and then sending the command to leave synchronization mode at the same time. The result of this operation will be that the timestamp and frameCount values returned by each sensor will be in the same time frame. However, this method is a software synchronization and does not account for the delay of the transport layer (USB, Bluetooth etc.) so the accuracy of this synchronization is limited by this fact. In our experience, the software synchronization can achieve a synchronization better than 5 milliseconds.
  """
  https://lpresearch.bitbucket.io/openzen/latest/examples.html