I think that getting the stats every minute for a day or a maybe a week or more is a bit excessive! At that rate, you'd have 1440 readings a day (approx 50kb) and 10080 readings a week (approx 345kb). At each reading, there are many things going on (several router queries, waiting for the router to respond, calculations etc) so it's possible that after a minute the router hasn't had time to settle or router's CPU / file system may get over loaded. Maybe the RSL is still waiting for something or calculating when the timer 'goes off' again. I'd be interested to see memory usage stats from your router while the RSL is monitoring.KevinR wrote:Using 1.0.29 I got the frozen stats file effect after 10 minutes, 10 recorded values. Both countdown clocks were running. The values in the "show log" display matched with the same timestamp. On closing the end of snr_stats.txt file appeared to match the stats.txt entries.
Second Edit:
OK it ran over night fine from 01:16 to 09:57. Then this morning the RSL locked up again.
If the RSL encounters a problem obtaining the stats, it would probably require the RSL to be completely closed and then restarted (that would currently be the only way to reset some of the variables).KevinR wrote:Using the user interface I used Stop Monitoring & Start Monitoring to try and reestablish logging. It waited, then greyed the router access functions (ie. Get Router Info, Reboot) but appears not to get much further. This implies the internal logic, router or file access is confused, so it cannot restart.
I've been running the RSL on my PC, with monitoring set to 1 minute intervals, but I haven't been able to reproduce the problem (yet). The only thing I've noticed is that during monitoring, web browsing appears very sluggish.