2023-02-06, 08:40 PM
Hi Greg,
I created a datafile to use iTelescope T80 for Feb 6. It included a #waitfor command. I had an opportunity to grab T80 for free on Feb 5, but the #waitfor command caused the scope to stop the run. I was so excited that I got control of T80 that I forgot about that #waitfor command that the ST4i Scheduler created.
My question: how to prevent the Scheduler from adding a #waitfor command? Should I just eliminate it with a text editor?
I don't speak 'ACP'.
TIA,
Phil S.
I created a datafile to use iTelescope T80 for Feb 6. It included a #waitfor command. I had an opportunity to grab T80 for free on Feb 5, but the #waitfor command caused the scope to stop the run. I was so excited that I got control of T80 that I forgot about that #waitfor command that the ST4i Scheduler created.
My question: how to prevent the Scheduler from adding a #waitfor command? Should I just eliminate it with a text editor?
I don't speak 'ACP'.
TIA,
Phil S.