Data loss and latency issues from Node Red to ThingSpeak channel.
4 ビュー (過去 30 日間)
古いコメントを表示
I'm currently busy with a project in which I use a wearble device that uses an accelerometer to track a worker's motions. I'm using Node Red to develop the system and from there I send the data to a ThingSpeak channel. There is however latency issues between these two platforms. It takes a few seconds for measurements to pop up on the ThingSpeak channel after the captured data has been displayed on Node Red. Additionally, only a quater of the data displayed on Node Red can be accounted for on ThingSpeak.
Any adivce would be greatly appreciated.
0 件のコメント
回答 (1 件)
Christopher Stapels
2023 年 7 月 11 日
The most likely cause of lost data is sending too fast. If you are using a free account or using the bulk write endpoint, the minimum time between updates is 15 seconds. For the paid account you can post updates at most once per second. Data sent faster than those rates can be lost.
Although ThingSpeak will keep an accurate record of ingested data, the infrastructure does not guarantee 'real time' updates. I would definitely expect a delay of several seconds, and occasionally slightly more depending on the system load at the time.
0 件のコメント
コミュニティ
その他の回答 ThingSpeak コミュニティ
参考
カテゴリ
Help Center および File Exchange で Read Data from Channel についてさらに検索
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!