I got the show up and running tonight. I setup the schedule with 2 sequences totaling 16:45 seconds. It ran great at first, well not great, I will cover that in another thread. It started on time, and ran for a few hours. I have it set to start at 5:30 and run looped untill 11:00 pm. It was running great untill about 10:15 and it completed the program and ended. No errors or anything, just as if the timer had reached it's end time. I hit restart timers and the show started back up, but it executed it 2 times simultaniosly a second or two appart, running overlapping. I stoped the timer and restarted it a few times but same problem. Then I restarted vixen and the problem was gone. The timer started back up and was running great.
Now the next issue, and I all ready know the answer. My show is 16:45 seconds long, set to end at 11:00 pm. At 10:50 the program came to it's end and instead of starting again and running till 11:00, it ended completely. I know if there is not enough time for the show to run before it's end time, Vixen will not run it. Is there any way around this? The only thing I can come up with is to set it to run untill 11:20, this would make sure that there is enough time for it to run one last time to make sure there is a show going untill 11:00. I have been telling everyone that the show runs untill 11:00. I would hate for someone to show up at 10:46 and the show not be running because it just ended and can not start again.
Thanks a million KC, this is the best year for my lights yet, and it is mostly thanks to all of your hard work.
I have experienced the dual exucution of a program. I'm not real sure what triggers it.
My show does the same thing, scheduled for 6 - 10 and ends at 9:45 (16 minutes long) so I just set the schedule for 10:30.
Since you want it to run up until the end time, what behavior would you expect it to have at the end time? Should it just run past the end time if it's in the middle of an execution and not prevent an execution as long as it's starting before the end time?
Should it just run past the end time if it's in the middle of an execution and not prevent an execution as long as it's starting before the end time?
yes 😀
otherwise you see it off before it's supposed tom and have to go play with the schedule. Rather a little long instead of ending short.
Tom
Unless there are any objections, I will change the behavior right now.
I experienced the dual execution tonight after I redid my schedule. Yesterday I had an LEDTriks and a program running from 5:30 to 10 (Although I may have removed the LEDTriks sequence from the schedule before it was done, I can't remember). Today I removed both timers and put a new LEDTriks and the same program in the schedule. Both were from 5-11 originally, then I changed both to 5:30 to 11. The LEDTriks ran fine but the program was running two at the same time like described above.
I removed the program from the scheduler, but when I clicked restart timers, the program ran. At the time I thought something weird happened to the LED sequence and it was causing the program to run. When it got to a little after ten I noticed the lights were not running and when I went to the computer only the LED sequence was running. I rescheduled the program to go until 11 and both the sign and program ran fine.
I think somehow yesterdays schedule just got erased from the calendar, but it was still scheduled to run with in the timer file? So when it got to 5:30 it ran both the program I scheduled yesterday and the program I scheduled today.
I put the timer file in a .zip file.
Michael
I get something similar where the is something scheduled to run every day 6--10 and every day I have to go in and remove the event and add it back cause it won't start. When I hit restart timers it says there's nothing scheduled.
I get the same thing... vixen just stops in the middle of the time it's supposed to be on, as if the timer is over. Is there any reason this happens? Also, where do we go to get the update for version 1.1?
I don't know if I posted it in this thread or not, but I could really use examples of schedules that cause this. If you could PM the file named "timers" and a short blurb on the issue, it would really help.
