About Thingy52 custom firmware: I can't choose accelerometer 16G range

RE: About Thingy52 custom firmware: I can't choose accelerometer 16G range

Bjørn Kvaale — Fri, 07 Sep 2018 10:57:05 GMT

Did you get the logging working now? It seems that Martin answered your other question. It is a good idea to check out the logging on the device itself before trying to log via nrf connect for desktop.

RE: About Thingy52 custom firmware: I can't choose accelerometer 16G range

manumonti — Tue, 04 Sep 2018 09:03:34 GMT

Hi, Bjørn.

I didn't know that there are two accelerometers in the device, but it makes sense.

I'm trying to see the values captured by the hardware directly (without the android app). For this, I'm trying to see debug messages, but how you can see in this post, I can't do it.

Thank you for your answers,

Manuel Montenegro.

RE: About Thingy52 custom firmware: I can't choose accelerometer 16G range

Bjørn Kvaale — Fri, 31 Aug 2018 12:00:41 GMT

Hi Manuel,

You are currently modifying the low power accelerometer, which is only used for waking up the Thingy device. You will need to use the other accelerometer on the Thingy device.

I am not sure that you will need to make any changes to the code itself. I do not believe there is a n accelerometer limit in the Thingy SDK either. There could be some kind of limit in the nRF Connect apps maybe. I have tested with both iOS & Android using the Thingy apps & nRF Connect for Mobile. I was also unable to get a reading higher than +9.81 or -9.81 m/s^2. Whether this is due to a limit in the app itself or whether it is difficult for me to see a value higher than the acceleration of gravity, I am not so sure.

I have tried to increase the .motion_freq_hz in the MOTION_DEFAULT_CONFIG define in m_motion.h from 10 to 100. If you combine that with using nRF Connect for Desktop, you can connect to your Thingy device, read the gravity values & download the log. The log values are unfortunately given in hexadecimal values, so you will need to figure out a way of converting the values with a script or going through the log itself to see if you can find a value greater than g. Hope that helps a bit!

Kind Regards,

Bjørn