In my LoggerNet (LN) 4.1, build 4.1.0.16, the scheduled collection from a station occasionally stops (no more data collected), and does not resume until I manually click the Collect Now or the Reset Device button in the Status Monitor.
This happens every time one or more of the data files for the station are write protected at the moment when a scheduled collection is performed (for ex. if the file is open in Excel, or if any other operation has write protected the file).
When write protection is cancelled, you would expect the schedule to resume, but it does not. Restarting LN does not help. The Collect Now or the Rest Device button must be clicked to get things going again. Anyone else who had this experience?
* Last updated by: helgeaa on 11/8/2012 @ 6:57 AM *
I doubt that the schedule is stopping. It is more likely going into primary or secondary retry intervals. You can verify this in the status monitor. You can adjust the intervals for both the primary and secondary retry schedules.
Thank you for answering. You are right. I had chosen 0 primary retries, and a long secondary interval (10 days).
I thought that, after a failed collection, LoggerNet would continue with the original collection interval if the secondary interval is longer, and 0 is chosen for primary retries.
Now I understand that this is not the case.