could not set acceleration range on DA14583 IoT Sensor Development Kit

9 posts / 0 new
Last post
Jean-Paul
Offline
Last seen: 5 years 7 months ago
Joined: 2016-04-21 14:14
could not set acceleration range on DA14583 IoT Sensor Development Kit

Hi
I cant change the accel rate from 2G to 16G
according on the User Manual DA 14583 IoT sensor to set basic configuration where is able to set the accelerometer range
at byte 2 an 0x0C has to send to change range to 16G. (page 26).
i am sending that via my app . but no change is hapen . the acceleration value that i get at runing is 16000 aprox.
so means 1G at 2G setting. but i like to measure at 16G so far the the value i should get is a round 2000.

i am using SFL Projekt.

i could set all other basic configuration sucessfull , only acceleration range is not working.
pleas confirm if there is an error on firmware SFL . and send me the solution.

thanks for your help,.
best regards.

Device: 
MT_dialog
Offline
Last seen: 1 year 5 months ago
Staff
Joined: 2015-06-08 11:34
Hi Jean-Paul,

Hi Jean-Paul,

I ve tested your case and i can see that something is wrong when changing the range of the accelerometer, so i can confirm your issue, i ve checked and the value that is passed to the IoT and stored in the NV memory seems to be the one provided by the app, but for some reason the accelerometer range doesn't change. I will check with the sw team and let you know as soon as possible.

Thanks MT_dialog

Jean-Paul
Offline
Last seen: 5 years 7 months ago
Joined: 2016-04-21 14:14
Hello There,

Hello There,

Thx a lot..
if you have an firmware version where only the connection to the bmi160 and Bluetooth is implemented would be also creat..
we will us your chip and bosh bmi160 sensor on our future sport product.
so I need an firmware where I can get the acceleration and gyroscope at the max . sampling rate via Bluetooth..
16G and at higher then 100Hz. if you have an FW version where that are already implemented and with issue corrected please send it to me .

Best regards.

MT_dialog
Offline
Last seen: 1 year 5 months ago
Staff
Joined: 2015-06-08 11:34
Hi Jean-Paul,

Hi Jean-Paul,

The only available reference design for interfacing with bmi160 is the IoT reference design, you can use the template project from the SDK5 and the existing drivers from the IoT to implement what you need. Also regarding this problem you are the first user reporting this so it will take some time to fix the issue.

Thanks MT_dialog

kiwi
Offline
Last seen: 4 years 5 months ago
Joined: 2015-06-09 16:42
We see this problem as well.

We see this problem as well. What would be the approximate timeline for this fix on the IOT firmware kit?

MT_dialog
Offline
Last seen: 1 year 5 months ago
Staff
Joined: 2015-06-08 11:34
Hi kiwi,

Hi kiwi,

I trust that we will have a solution within this week and provide a fix.

Thanks MT_dialog

MT_dialog
Offline
Last seen: 1 year 5 months ago
Staff
Joined: 2015-06-08 11:34
Hi all,

Hi all,

Regarding the IoT project and the fact that the user couldn't change the range of the accelerometer the same should happen with the gyro range, you should add the below snippet in the bmi160.c file at line 477:

   s_bmi160.delay_msec(C_BMI160_ONE_U8X); 

    bmi160_set_accel_range(BMI_160_ACCEL_RANGE);

    s_bmi160.delay_msec(C_BMI160_ONE_U8X);

    bmi160_set_gyro_range(BMI_160_GYRO_RANGE);

Thanks MT_dialog

Jean-Paul
Offline
Last seen: 5 years 7 months ago
Joined: 2016-04-21 14:14
Thanks a lot it works now.

Thanks a lot it works now.
in the moment I got some timing problems with my app .
so I like to ask for your Android app source code to compare with my source code ..
of course I accept the SLA terms .
pleas send me the Adroid app. source code .
thx.

MT_dialog
Offline
Last seen: 1 year 5 months ago
Staff
Joined: 2015-06-08 11:34
Hi Jean Paul,

Hi Jean Paul,

The mail has been sent to the registered email account.

Thanks MT_dialog

Topic locked