Cumulus Support

Hi Mark
Just loaded the new release and all seems to function as expected from a local view (no web site for me!).

I note that the default view for the solar and rain charts are now for only 24hrs and whilst I can live with it it does seem a bit short. Maybe I just need to rework my brain.

Amended title

I've updated successfully after one issue I had to overcome.
And just posting this as information.

On my CumulusMX with WLL the IP address for the WLL had been 192.168.0.102
After I updated to b3101 my start-up froze at "Ping 192.168.0.102" and I waited for nearly 10 minutes, and then exit the startup (I assumed it was in the StartupDelay period but I only had it at 120 seconds). After some checking, I found my router IP address for WLL had been changed to 192.168.0.100 (possibly after some resets by my IP provider after having some connection issues).
I changed the IP in Cumulus.ini StartupPingHost=192.168.0.100 and started again and it still froze at Startup ping: 192.168.0.102 (I verified the Cumulus.ini was at the changed IP 192.168.0.100 and had been saved).
Then looked in MXdiags ServiceConsoleLog and saw the IP was still at the previous 192.168.0.102 from the last run and shutdown. I removed(renamed) ServiceConsoleLog and then started again and all is good.
I had not changed the IP number in Cumulus.ini Station VP2IPAddr= but it was correct (I assume from the WLL Auto Discovery setting).

This change in IP address is not very often (first time since I've had the WLL) and now know what to do if a start up freezes at the IP address Ping.

Enjoy,
Paul

@paul: you might also give the WLL a fixed IP address.

Hi Hans,
Yes, but I didn't initially

Thanks,
Paul

Hi Paul, the start-up ping wasn't really intended to ping the WLL, Cumulus should retry it until it becomes available anyway. Though you may get a gap between the history download and the WLL becoming available - I haven't checked though.

The startup delay starts once the ping is successful. The ping does not timeout.

The intention really was to check for an internet connection to some destination like WeatherLink.com and then delay whilst some synchronisation takes place before starting processing.

I had a power out last evening and both my systems (b3101) 'stalled' at the ping. They are both pinging the same device, my MariaSQL system, which was up and running correctly at the time I noticed - about 30mins after power restore. A restart of CMX (not a reboot) on both systems (both PiZeroWs) worked OK. The target of the ping is the slowest of the systems to become active and is obviously needed to log data which is why I chose this system. They are all on the same sub-net. A ping from my Windows system to the SQL system, prior to reboot, was fine.

Phil, are you pinging by name or IP address?

Sorry for delay - by IP Address

That's odd isn't it. You'd expect as soon as the network was up, an ARP request would get a response, and then the ping would work. I don't know why it would loop forever with no response, but I'll try and reproduce this...