Hello,
I'm dealing with two different timing issues for a hardware application: execution of critical code in loop() versus monitoring of device output.
In this application, it's acceptable to read device output every 15 / 60 / 300 seconds. But it's very necessary to keep loop() running at maximum speed without any hang-ups to data uploads.
Our current (and much older) application uses a Raspberry Pi to interface with two Arduino Nanos in the era before Arduino's IOT Cloud. The Pi is able to build data queues to our own data server in the 15 / 60 / 300 second intervals, while the Nano's run several iterations in loop() per second.
The goal is eliminate the Pi board and move to something like the Giga R1 or so forth and moving off our own data server to the IOT Cloud (for many reasons which we like).
The problem we could see is making calls to ArduinoCloud.update() within loop() as these default scripts have, and something happens with our network that causes hang-ups in data transfer, thus causing a back-up in critical code.
Is there any timeout feature in ArduinoCloud.update() which aborts the data transfer, flushes the data buffers and continues with the code in loop()?
Thank you,
Chris
1 post - 1 participant