Hi AstroBinners,
Apologies if this question has been asked elsewhere and if so please feel free to point me to the discussion
I am running NINA in a remote observatory which reports the roof condition as open or close in the Safety Monitor of NINA.
I am using Loop while Safe as a loop condition. But when it becomes unsafe the sequence just ends and skip to the end of sequence instructions thus shutting down the rig.
Is there a way to pause imaging/guiding when conditions are unsafe while still tracking. So when conditions become safe a plate solve occurs, guiding resumes as does imaging.
Thanks for any insights, tips tricks and suggestions
Best
Vikas Chander
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Hello Vikas,
Lucas here from the observatory.
Safety monitor is less and less used as it is a bit sensitive. we recommend to get it out of the configuration. From what I know some user's are using the roof status on the user interface with a script, or pushover's notification as a trigger which is more reliable.
otherwise, you can shoot the roof as except during april roof are unlikely not closing very often 
Best regards !
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Hi Vikas,
I have my setup doing exactly what you want to do. You can use the sequencer powerups plugin with its When Becomes Unsafe and Once Safe instructions to stop guiding, park your mount, etc once the roofs close, and then unpark and slew, run autofocus and resume imaging. Here is an image showing how I have set it up. Create something like below and add it as a trigger to your sequences. Works like a charm.
Ani
 |
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Ani Shastry:
Hi Vikas,
I have my setup doing exactly what you want to do. You can use the sequencer powerups plugin with its When Becomes Unsafe and Once Safe instructions to stop guiding, park your mount, etc once the roofs close, and then unpark and slew, run autofocus and resume imaging. Here is an image showing how I have set it up. Create something like below and add it as a trigger to your sequences. Works like a charm.
Ani
@Ani Shastry thanks i was just thinking more about this recently and your example is helpful. How do you handle the startups, making sure it doesn't open if unsafe? -Brian
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
THIBAUD Lucas:
Safety monitor is less and less used as it is a bit sensitive. we recommend to get it out of the configuration. From what I know some user's are using the roof status on the user interface with a script, or pushover's notification as a trigger which is more reliable.
otherwise, you can shoot the roof as except during april roof are unlikely not closing very often
There is an ASCOM generic file safety monitor available that will allow you to read various status files and apply them to the safety monitor function.
Generic File Safety Monitor
I use it to monitor roof status at a remote site in combination with Marc Blank's Sequencer Powerups and it works great.
 |
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Brian Valente:
I essentially have a couple of wait until safe instructions in the startup section. I first wait until the roofs open, then I cool the camera, reset the focuser/rotator, etc... and wait until 15 mins before astro-dark, and I have another wait until safe there just in case the roofs close right before astro dark.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Ani Shastry:
Brian Valente:
I essentially have a couple of wait until safe instructions in the startup section. I first wait until the roofs open, then I cool the camera, reset the focuser/rotator, etc... and wait until 15 mins before astro-dark, and I have another wait until safe there just in case the roofs close right before astro dark.
Got. I take it you are not managing the roof open/close?
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Bill McLaughlin:
THIBAUD Lucas:
Safety monitor is less and less used as it is a bit sensitive. we recommend to get it out of the configuration. From what I know some user's are using the roof status on the user interface with a script, or pushover's notification as a trigger which is more reliable.
otherwise, you can shoot the roof as except during april roof are unlikely not closing very often
There is an ASCOM generic file safety monitor available that will allow you to read various status files and apply them to the safety monitor function.
Generic File Safety Monitor
I use it to monitor roof status at a remote site in combination with Marc Blank's Sequencer Powerups and it works great.
Thanks Bill - I use the ascom safety hub to monitor a few different things. It looks similar to this but it's ascom driven vs file driven. I manage the open-close of the roof myself, so there are a few more steps for me.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
1.51
0.00
1.20
1.51
5.61
