Hello!
I was wondering if it would be possible to add an UNIX timestamp, in milliseconds, to the accelerometer, gyroscope and magnetometer data.
I would like to add the timestamp to the sensor report, every time new data is generated.
I was looking at the documentation (https://support.dialog-semiconductor.com/system/files/restricted/UM-B-06...) and I found that there is a bmi160_get_sensor_time, is there a way to go from this sensor time to some sort of UNIX timestamp in milliseconds that can be added to the sensor report?
I would need to add 4 extra bytes to the sensor report for this three sensors, would it be possible?
Thanks in advance,
Alejandra
Device:
Hi gomezago,
The bmi160_get_sensor_time() function return an uint32, which is not the real time clock, because it returns a relative value which is related with the previous calculated value. Be aware that the DA14553 does not have a real time clock. Also, be aware that the DA14585 IoT reference application , is an old design. Currently, we have moved on DA14585/6 products and our new SDK6!Please check DA14585/6 in our support website:
//www.xmece.com/products/connectivity/bluetooth-low-energy/smartbond-da14585-and-da14586
The DA14585 IoT Multi Sensor Development Kit is recommended for new designs.
//www.xmece.com/products/da14585-iot-multi-sensor-development-kit
Thanks, PM_Dialog
Hi PM_Dialog!
Thanks for your reply,
有什么方法可以使用bmi160_get_sensor_time t ()o get some kind of time difference (in milliseconds) between the different instants in which data is generated?
I could get the UNIX Timestamp from the android App, and use that difference as a complement.
Best,
Alejandra
Hi gomezago,
Let me check it and if it is possible, I will let you know.
Thanks, PM_Dialog
Thank you very much PM_Dialog! Please keep me posted :)
Best,
Alejandra
Hi gomezago,
It is not possible, because as it is mentioned before, the bmi160_get_sensor_time() function returns an uint32, which is not the real time clock.
Thanks, PM_Dialog