-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Network watchdog #287
Comments
Some additional points:
|
Thanks. I do miss an on/off setting. Perhaps better, move the time-out to dbus and when 0 => disabled. |
On off setting has been implemented. Waiting for inclusion in Venus. |
The functionality has been added to Venus v2.30~8, with this commit. Now needs adding to the gui; and testing. |
Its in the ccgx manual |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To do
Once released
Summary of the functionality as implemented in the watchdog recipes:
com.victronenergy.settings /Settings/Watchdog/VrmTimeout
.a. vrmlogger has been disabled, or
b.
VrmLastContact + log-interval + timeout >= now
c. there has been no contact yet; and
boot-time + log-interval + time-out >= now()
Code is here.
Proposal for the gui
Summary of the full requirement.
If internet connectivity is lost, a local malfunction may be the cause. It is thus desirable to detect such a condition and take appropriate action which may include rebooting the system. When connectivity is provided by the GX GSM or similar, this shall also be restarted.
vrmlogger TimeOfLastContact will be used to detect network loss
Using VRM TimeLastContact value avoids creating additional network traffic for the connectivity check. The logging interval setting must be taken into account. The check will be performed periodically by the watchdog daemon.
Making sure (usb connected-) modems also reboot
The Victron USB modem can be rebooted by stopping updates of its watchdog and waiting for it to reset. An onboard modem can be simply power cycled. A subsequent full system reboot ensures that a hung pppd or similar does not block communication.
Timeout
To allow for an unreliable external network, a relatively long timeout shall be used. 60 minutes is likely a suitable choice. This timeout is in addition to the VRM logging interval, so the final amount can be significantly longer depending on VRM settings.
The text was updated successfully, but these errors were encountered: