Yesterday, we had a long running logfile, that showed a gap of about 10,000 seconds halfway. Reasoning back, it seems likely that the computer went into standby mode, causing a chunk of log output to go missing. Looking at the computer power settings, it was indeed set to go into standby mode after 2 hours, so that is probably the cause. When this happened, the frontend seemed to have disconnected from the connector as well.
It would be interesting if the connector could somehow prevent the computer from going to sleep. I suspect there are OS-depenent APIs for doing so. If we do this, it should probably be configurable (but default to on).
Another interesting observation is that with manual logging with the Arduino application, this problem never showed up. So perhaps Arduino is already doing something similar, or perhaps the fact that it is showing and updating a window is sufficient to prevent standby?
Yesterday, we had a long running logfile, that showed a gap of about 10,000 seconds halfway. Reasoning back, it seems likely that the computer went into standby mode, causing a chunk of log output to go missing. Looking at the computer power settings, it was indeed set to go into standby mode after 2 hours, so that is probably the cause. When this happened, the frontend seemed to have disconnected from the connector as well.
It would be interesting if the connector could somehow prevent the computer from going to sleep. I suspect there are OS-depenent APIs for doing so. If we do this, it should probably be configurable (but default to on).
Another interesting observation is that with manual logging with the Arduino application, this problem never showed up. So perhaps Arduino is already doing something similar, or perhaps the fact that it is showing and updating a window is sufficient to prevent standby?