Hi All,
I am new in the Dev Zone and apologize in advance if the question was posted in the incorrect section.
I would like to run the Thingy91 as tracker hardware for some gimmicks and use the latest version of the Asser tracker firmware ncs 1.6.0.
Especially the latest features sound very convincing to me:
"Offline first" - Highly mobile cellular IoT products need to deal gracefully with unreliable connections by implementing mechanisms to retry sending failed data.
Timestamp on the device - Sensor data is timestamped on the device using multiple time sources. When the device is offline (scheduled or unscheduled), timestamping is not dependent on the cloud side.
Batching of data - data can be batched to reduce the number of messages transmitted and to be able to keep collected data while the device is offline."
For my application the main focus is offline logging with the following functions:
- Climate logging : every 300 seconds
- GPS logging: every 30 minutes (if ACC movements are indicated)
- Store Data in FCB or orther NV-Memory
- Publishing Data every 1/12/24 hour -> If failed: retry 12h later or ~10 Minutes after detecting a motion.
Asset-Tracker V2 has been successfully installed and built in SEGGER Embedded Studio. Unfortunately, I couldn't find a config about exactly how big the buffer is. In addition, offline logging is not working as described. If I disconnect the Thingy from the network ( metallic housing) and reconnect it, the data of the buffer is not displayed in the nRF cloud.
Can anyone help me with how exactly I can activate the offline features and adapt them to my requirements?
I look positively for helpful tips or sample implementations.
Thanks!
