Replies: 2 comments 1 reply
-
I am assuming you would setup the controller to do the built in exercise (without a load) and use the add on for the exercise with the load transfer. The problem is that the add on is not aware of which week of a bi-weekly exercise the controller will use. The add on writes a value to the config file named "last_exercise" to help keep track of the add on bi weekly cycle however this is independant from the built in exercise cycle. You may be better served to use the Post-Controller exercise frequency with transfer cycle for the add on. This will perform the exercise with load transfer immediately after the controllers built in cycle. The Post-Controller frequency is designed to make srue the two exercise cycles do not overlap. This is an easier way to keep the two exercise cycles in sync. |
Beta Was this translation helpful? Give feedback.
-
I see that it might create a dilemma if the two different exercise cycles are controlled by different entities, the controller and the Pi. |
Beta Was this translation helpful? Give feedback.
-
All,
I have the "enhanced exercise" enabled and have the following in my genexercise.conf:
and I've set the Generator Exercise Time to biweekly, Wednesday 1400 (although I can't find that in the configuration files).
The idea is to do a regular exercise every two weeks, and the weeks between that do a "real" exercise with load transfer.
However, the extended exercise has run two weeks in a row now, although the config file (and also the Add-Ons page) clearly say bi-weekly.
I did restart the Pi last week for a system update, is that maybe what got the enhanced exercise schedule out of whack?
And what's the best solution to do the bi-weekly exercise? Just set it to 1st Wednesday of the month and leave the regular exercise weekly?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions