Adding timestamps to ble tms service's raw characteristic.

RE: Adding timestamps to ble tms service's raw characteristic.

Bjørn Kvaale — Mon, 22 Jul 2019 08:41:12 GMT

soyoungCould you please comment?

RE: Adding timestamps to ble tms service's raw characteristic.

Matej — Sat, 20 Jul 2019 16:54:19 GMT

How did you manage to send timestamps in the end? I am having the same problem and would really appreciate to know.

RE: Adding timestamps to ble tms service's raw characteristic.

Bjørn Kvaale — Fri, 24 Aug 2018 07:17:58 GMT

Very sorry for the delayed response. It seems correct to use motion_freq_hz & changing the value to 100 Hz to get a reading every 10 ms. You should not have to change the DEFAULT_MPU_HZ value. How are you testing this? Could you try connecting to the motion service on nrf connect for mobile & see if you notice a difference when motion_freq_hz is 5 Hz vs 200 Hz? I am not sure you will notice this, but it could be worth a shot.

You will probably need to disconnect & connect to the Thingy device again to see the update.

It is a good idea to keep the frequency above 50 Hz, as the integration of the motion data will not be as accurate if the frequency is lower.

RE: Adding timestamps to ble tms service's raw characteristic.

soyoung — Thu, 16 Aug 2018 16:47:24 GMT

Um.. I found another way to send timestamps.

But now I have another problem, I want to receive raw characteristic notification every 20ms, but it's sending notification every 100ms.

How can I change data sending rate?. I changed motion_freq_hz to 100 in m_motion.h file, DEFAULT_MPU_HZ to 10 in drv_motion.c file, but rate doesn't changed.

RE: Adding timestamps to ble tms service's raw characteristic.

Bjørn Kvaale — Wed, 15 Aug 2018 11:40:26 GMT

Hi, sorry for the delayed response. It seems there could be an error in the line:

APP_ERROR_CHECK_BOOL(size == sizeof(int32_t) * RAW_PARAM_NUM);

There could be an issue there with the value of RAW_PARAM_NUM (i.e. you may need to increase this number to 11 since you have added two variables) & also one of your variables has the type uint16_t. This could potentially lead to errors.

Could you try setting one of the variables as a constant to make sure that this data is being transferred correctly, e.g.:

data.gyro.y = 1234;

in drv_motion_evt_handler & see if you receive this value in the GATT client.