One install is C:\CumulusMX and this starts fine, including archive downloading, and runs most of the time.
A second totally separate install C:\CumulusMXutils usually started once a day to run for a short while. At a restart after the day before stop there is no archive download. After a daily start and see that there was no archive download I stop this CumulusMXutils, copy in the log files from the good CumulusMX and then restart CumulusMXutils and then all works fine, until the next day new start.
The Cumulus.ini files are very similar for both installs.
Attached are both MXdiags files for CumulusMXutils.
The first is for the restart after yesterday's stop and therefore includes day end tasks like dayfile, etc, BUT NO archive download.
The second is a restart after the log files were added so no day end tasks and no archive download expected as the log files and last run times are current.
The Loop2 message often shows at a start in both installs but not always. The connection for both these installs is WiFi - Davis Vue with firmware v4.30 and WiFiLogger V2.
MXDiags in the first start instance without archive download has:
and the MXDiags for the second has:2020-06-28 08:51:38.975 Connected OK
2020-06-28 08:51:38.978 Reading firmware version
2020-06-28 08:51:42.481 Reading firmware version
2020-06-28 08:51:45.982 FW version = ???
2020-06-28 08:51:45.982 LOOP2 is enabled in Cumulus.ini but this firmare version does not support it. Consider disabling it in Cumulus.ini
There are also other issues such as Console clock: Failed to read console time in the first instance MXdiags.2020-06-28 09:03:44.531 Connected OK
2020-06-28 09:03:44.534 Reading firmware version
2020-06-28 09:03:46.538 FW version = 4.30
Any thoughts what could cause the failure of archive download?