You need to load the VG_AHRS Application which runs Kalman Filter and estimates the Roll and Pitch.

The OpenIMU300RI ships by default with IMU only.

The compiled code is on this page and can be directly installed from the website if the devices is connected via the Python driver.
https://developers.aceinna.com/code/apps

The FW code is also in Visual Studio Code Aceinna Extensions and can be compiled and loaded from source

Home -> Custom IMU Examples -> OpenIMU300RI/VG_AHRS

Since you are not using Overcurrent protection functionality nor the fault flag, you can leave the FaultB and VOC pin OPEN.

The output step response of the device on Vout is 300nS

There is example code in the open source python driver

Check here
https://github.com/Aceinna/python-openimu/blob/master/openimu/openimu.py

There also example code in the open source C++ driver

Check here
https://github.com/Aceinna/cpp-openimu/blob/master/OpenIMUProtoTest/cksum.cpp

There is finally embedded C-code in the open imu library source itself

Check here
https://github.com/Aceinna/OpenIMU330-lib/blob/master/Platform/Core/src/crc16.c

The accelerations are in m/s^2 and rates in deg/s

Parking lot test of OpenIMU300 with Ublox M8 in INS mode.

Quick data share test

My raw data is Files

Nice. Why does it share the data as an image instead of a JS graph?

I think our default algorithm will work fine for this application. The errors in roll and pitch will should be pretty modest. This is a very easy case to simulate with our online simulator found on our developers website. I look forward to see the simulation results which can be shared directly on the forum.

UWB is probably best option indeed.

The call back rate of RunUserNavAlgorithm() is defaulted to 200Hz.

The is controlled by the following line of code found in taskDataAcquisition.c

inertialAndPositionDataProcessing(dacRate)

dacRate is by default 200Hz