I will be having the following questions answered by Bosch shortly and will post the answers. If anyone already has the answers, it would be great if you could share! Thanks in advance.
Mode of Operation:
That's a lot of questions, let me try my best to answer.
The chip has an operating temperature of -40 to +85C. The gyroscope calibration require the device to be still, if the vibration from your engine exceeds a certain threshold, then it may never calibrate.
This is a known issue in current firmware. See this thread.
Both would provide the same performance for this application
The opposite would be true, your best estimate of the calibration is before powering off the device
Initially yes. Once it has become non-zero, data can be trusted from that point on.
In the built-in firmware yes, see above.
The behavior is the same in all working modes
The calibration status is aligned to the Android definition of sensor status accuracy Unreliable to High.
If you manually load the calibration, you are responsible for its validity. The BNO055 will assume that it is good. If that is not the case, the performance will actually be worse until the sensor finds the correct values.
The strength of the magnetic and gravitational fields. use to compensate for sensitivity error.
FMC means "Fast Magnetometer Calibration". With this calibrator, the calibrated gyroscope data is compared with the magnetometer data to extrapolate the Earth's magnetic field 3D sphere.
That depends on your accuracy requirements. Accelerometer calibration at the factory may be desired, but gyroscope calibration is better when done at every power-on (and very fast)
Mode of Operation:
COMPASS = Android's Geomagnetic Rotation Vector.
NDOF = Andoid's Rotation Vector
The magnetometer is used in lieu of the gyroscope in M4G and Compass mode.
We are planning the release of a new firmware (hopefully soon) for customers to flash via the bootloader. Pre-programmed firmware will not change.
Thank you for your timely reply! Does FW ver: 0.3.0.11 address the calibration status issue? Is it possible to evaluate it now? Could we check out the changelog?