This was partly discussed as an issue on the library's github
Here's how I understand it:
The library doesn't configure the registers you want. I don't see a reference to writing to the
ACC_CONFIG register (address 8). Not even defined in the header.
The sensor has two register-pages (0 and 1) [refer page 50]. I.e. if you select page 0 then the register at address X means something, at page 1 it means something else.
We want to write to
ACC_Config at address
0x08 on Page 1.
Page 77 tells us that, regarding writing to the register: "Write: can only be changed in sensor mode, see section 3.5.2"
In code, you could hack something in there:
After changing to the sensore mode, you could then write to the register as
//values taken from section 3.5.2 page 27
#define BNO055_ACC_CONFIG_2G (0) //0B00
#define BNO055_ACC_CONFIG_4G (1) //0B01
#define BNO055_ACC_CONFIG_8G (2) //0B10
#define BNO055_ACC_CONFIG_16G (3) //0B11
#define BNO055_ACC_BW_7_81_Hz (0)
#define BNO055_ACC_BW_15_63_Hz (1)
#define BNO055_ACC_BW_31_25_Hz (2)
#define BNO055_ACC_BW_62_5_Hz (3)
#define BNO055_ACC_BW_125_Hz (4)
#define BNO055_ACC_BW_250_Hz (5)
#define BNO055_ACC_BW_500_Hz (6)
#define BNO055_ACC_BW_1000_Hz (7)
#define BNO055_ACC_PWRMODE_NORMAL (0)
#define BNO055_ACC_PWRMODE_SUSPEND (1)
#define BNO055_ACC_PWRMODE_LP1 (2)
#define BNO055_ACC_PWRMODE_STANDBY (3)
#define BNO055_ACC_PWRMODE_LP2 (4)
#define BNO055_ACC_PWRMODE_DEEP_SUSPEND (5)
#define BNO055_ACC_CONFIG_ADDR 0x08
//Select page ID 1 to write to the right register
//build the config value with bitshifts
//see page 77
//use all standard values except 16G parameter
uint8_t acc_config = (uint8_t)((BNO055_ACC_PWRMODE_NORMAL << 5)
| (BNO055_ACC_BW_62_5_Hz << 2)
//write new accelerometer config
//change back to page ID 0 (or whatever was before there)
//Otherwise we read sensor data from the wrong page with entirely different meaning
Since I don't have that sensor here I have no way to test it. So this is just the basic idea. You can also read registers with
read8, with which you can verify that before you write anything to the register, it has some standard (or expected) value. E.g.,
ACC_CONFIG should read as
0x0d. And after you write a value there you should be able to read the same value back, otherwise the chip didn't let you execute the write and you have to investigate why.
Yes, you mostly have to do the hard work by yourself. Changing from 4G to 16G might also have the implication that some other calculations on the raw data has to be done different, however I am not sure of that.