Hi all,

I'm currently setting up a schedule for the a few nights imaging and I would like to use a start-up/shutdown script. from what I understand, they have to be written in python, which I don't know all that well. So I was wondering if someone had a script I could use. I realise it will be specific to their system but if I could use it as a starting point I could modify it to suit my set-up.

I'm running KStars from Windows with INDI on a RPI4 attached to my rig.

Here's what I'd like the script to do:

Start-up -
1. UnPark Mount
2. Warm camera to a specified temp

At this point the schedule should kick in and run my imaging

Shut-down -
1. Warm camera
2. Park mount

Thanks in advance

Rene

I presume on startup "Cool" camera to specific temperature? Except for this, the rest is already supported by the scheduler itself, no need for a script.

Hah, ha yes! Cool the camera of course. Thanks for the info.

So what function do the startup/shutdown scripts serve?

Rene

From www.indilib.org/individuals/ekos-kstars/...-ekos-scheduler.html it says the script can be any language that can be executed on the local machine.

"Startup and shutdown scripts can be written any language that can be executed on the local machine. It must return 0 to report success, any other exist value is considered an error indicator."

I'm working on startup/cooldown and shutdown/warmup scripts that are executable bash and work at the console, but I'm having issues running them in the context of Ekos. The startup script gives an error "cannot run startup procedure while indi devices are not online", but all my devices are online. Running the shutdown script starts and outputs to the indi console, so I know it is starting, but then it hangs. I suspect there's a detail I need to work out with permissions perhaps, but the odd thing is when I terminate the script, it keeps restarting again. I had to close kstars completely to get out of the loop.

Happy to share what I have working, but I'm hoping someone chimes in with some tips. I haven't found anything of relevance to the error I'm getting, and very little in the way of resources for these scripts other than that one online man page.

Any update information

The start script that you are looking for could be realised in the scheduler. Maybe there is a better way, but this is how I do it: create a sequence (exposure time and number, gain etc ) and save it to a file, ending is *.esq. This is a text file, just open it with the text editor and look for the parameter 'force temperature '. Change status from false to true and enter the desired value, e.g. -10.0 and save the file. In the scheduler enter an object or load a reference frame to set the target coordinates and load the edited esq file. Keep slew, guide and track ticked and if applicable for your setup also focus. Add this sequence to the schedule and press play. When the job can be run, it slews to the target, focuses, starts guiding, cools the camera and starts the exposures.
Hope this is of help.
Alex

Gesendet von meinem SM-T510 mit Tapatalk

Sorry, tablet reported the post could not be sent, but it was, which I realised after pressing send 4 times.

Sorry, tablet reported the post could not be sent, but it was, which I realised after pressing send 4 times.

The start script that you are looking for could be realised in the scheduler. Maybe there is a better way, but this is how I do it: create a sequence (exposure time and number, gain etc ) and save it to a file, ending is *.esq. This is a text file, just open it with the text editor and look for the parameter 'force temperature '. Change status from false to true and enter the desired value, e.g. -10.0 and save the file. In the scheduler enter an object or load a reference frame to set the target coordinates and load the edited esq file. Keep slew, guide and track ticked and if applicable for your setup also focus. Add this sequence to the schedule and press play. When the job can be run, it slews to the target, focuses, starts guiding, cools the camera and starts the exposures.
Hope this is of help.
Alex

Gesendet von meinem SM-T510 mit Tapatalk

I was just looking for this too.

I believe that it could be a feature on the Observatory Start-Up procedure, just like the Warm CCD on the Observatory Shutdown Procedure.

As far as I can understand the T value here - I believe the same that Alexander above changes through the text file - while you use the scheduler comes after all the steps (track, focus, align, guide).

What would be really helpful is the option to pre-cool the camera:
1. Unpark Dome
2. Unpark Mount
3. Unpark Cap
4. Cool the camera at the specified value, when reached proceed on the 1st sequence.


PS. The 4 could be 1 too, but it would be easier for the cooler to drop the temp after the dome is open, not while is closed.

A script with the ability to delay dome parking a period of time after parking mount would come in handy. I am running a remote observatory where there are multiple setup wwith different telescope parking time, on an emergency, having the ability for a setup to wait a minutes for every other mount to park before closing the ROR is important.

A script with the ability to delay dome parking a period of time after parking mount would come in handy. I am running a remote observatory where there are multiple setup wwith different telescope parking time, on an emergency, having the ability for a setup to wait a minutes for every other mount to park before closing the ROR is important.