First it would not work if you had say 6 hrs of frequencies to run only 2/3s of it for 4 hours.
So while we could use the Run For x Hours setting to limit the program to 4 hours, this is actually a better method.
When you build your program, it will give you a Estimated Total Runtime.
Limit the program to 4 hours or less.
You will note to the right that there is a setting:
Repeat Sequence = 0
This means that it will run the program non-stop until you stop it.
Change this to = 1 to limit the program to one complete loop.
This will terminate the program before the 4 hour mark.
However, there in lies a new problem.
Remote programs need repeats to build efficacy. One application loop will not do much.
However, if you are testing the waters, I can understand your approach. Just try to get past the one application loop as soon as you are comfortable.
However, if you have say 30 minutes of frequencies you want to run for say sleep.
This would be a good time to use the Run For x Hours setting.
In this case, leave the Repeat Sequence = 0 in place, and on the Settings tab, edit the Run For x Hours to set a 4 hour limit.
Keep in mind again this only works for programs who's one loop runtime is shorter than say 2 hours.
For more details, please check the link:
https://www.facebook.com/groups/spooky2/permalink/734511963377376/
Comments
Maybe because I'm just new to all this- but this article did not provide clarity for me. I am still very confused about this 4 hour suggested limit for programs that are longer than 4 hours...
Please sign in to leave a comment.