BMI270 config file options or variations?

[_nd345]

Github samples include these two useful config files:

https://github.com/boschsensortec/BMI270-Sensor-API/blob/d270cdee303b2ed9ea4c43fb7064da8ded8a48b4/bm...
bmi270_maximum_fifo_config_file 328 bytes

https://github.com/boschsensortec/BMI270-Sensor-API/blob/d270cdee303b2ed9ea4c43fb7064da8ded8a48b4/bm...
bmi270_config_file 8192 bytes

How can end-users generate custom config files? What are the options and how to generate? FIFO is very small, but the raw gyro data is not as clean as the NORMAL config.  Yet at 8192 bytes, it's rather large and not preferable or maybe even usable for some embeded systems.

[_nd345]

off-subject, the github has issue-trackers and pull-requests that have been completely ignored by Bosch.

[BSTRobin · Accepted solution]

Hi _nd345,

The config file contains different algorithms, such as any motion, step counter, etc. The more algorithms supported, the larger the config file.

As you can see, for the config file with the largest FIFO, the size of the config file is small, and it should not occupy the memory space of the host as much as possible to store the config file. It provide a large FIFO as much as possible to cache more data. Due to small size of config files, many algorithms were removed.

Similarly, the 8KB config file provides as many algorithms as possible, so the size of the config file is relatively large.

The config file does not support being modified by the user. You can select and use from published config files based on user applications.

Applications

 

BMI270 (base)

• Any motion, No motion, Significant motion detectors
• Wrist worn Step counter and Step detector (Pedometer)
• Activity change recognition
  • Still
  • Walking
  • Running
• Wrist gestures
  • Push arm down
  • Pivot up
  • Wrist shake jiggle
  • Flick in
  • Flick out
• Wrist wear wake up

 

BMI270 Context

• Step counter and Step detector (Pedometer)
• Activity change recognition
  • Still
  • Walking
  • Running

 

BMI270 Legacy

• Any motion, No motion, Significant motion detector
• Orientation detector (Advanced Potrait-Landscape)
• High-G, Low-G (Freefall) detector
• Flat detector
• Tap detection (Single, Double, Triple taps)
• Smartphone Step counter and Step detector (Pedometer)
• Activity change recognition
  • Still
  • Walking
  • Running

 

BMI270 Maximum FIFO

• Supports a 6kB FIFO

[_nd345]

Fair enough.
Does FIFO contain essentially the same "Any motion, No motion, Significant motion detectors"?
I'm trying to understand why NORMAL with OSR4 would have cleaner data and less filter delay for software-post-filtering as compared to FIFO with OSR4, which was sliglhty noisier data and slightly more software-post-filtering delay.  This application is in regards to A:B testing of Quadcopter Flight-Controller software comparing the two BMI270 config files.Flight-control obvisouly does not need all the features, but FIFO seems to be missing something special.
Thank you.

[BSTRobin]

Hi _nd345,

FIFO and "Any motion, No motion, Significant motion detectors" are parallel relationships, not inclusive relationships.

You can provide a detailed description of your A and B tests separately, so that we can understand your problem.
Sensor configuration:
How to read data:
Test environment: