Help in using Suspend and Resume in Dragscript

I have used dragscript successfully to capture data for a whole night when the forecast said no rain and I was fairly confident there would be no issues. The system successfully coped with cloud, retrying to acquire the target and continue imaging.

Now I have added a weather station, so that I can close the observatory roof when conditions are Unsafe. This means I have to use Suspend and Resume.

The dragscript I came up with did some of the things I expected, but also some things I don’t know how to correct.I followed some of the samples here and used this:


Start: Events At Start are ENABLE
2 - Script
3 - Viking Client Connect: ClientID 1
4 - Block: Imaging
5 - Sequence: Start Immediately - End 04:00:00 [hh:mm:ss] - C:\Users…\Voyager\ConfigSequence\Leo Triplet Blue.s2q
6 - IF ERROR
7 - External Script: C:\Users…\telegram_me.vbs “Leo Triplet Imaging Run Failure”
8 - IF OK
9 - External Script: C:\Users…\telegram_me.vbs “Leo Triplet Sequence Successful”
10 - Sequence: Start Immediately - End 04:00:00 [hh:mm:ss] - C:\Users…\Voyager\ConfigSequence\Leo Triplet Blue.s2q
11 - IF ERROR
12 - External Script: C:\Users…\telegram_me.vbs “Leo Triplet Imaging Run Failure”
13 - IF OK
14 - External Script: C:\Users…\telegram_me.vbs “Leo Triplet Sequence Successful”
15 - Sequence: Start Immediately - End 04:00:00 [hh:mm:ss] - C:\Users…\Voyager\ConfigSequence\Leo Triplet Green.s2q
16 - IF ERROR
17 - External Script: C:\Users…\telegram_me.vbs “Leo Triplet Imaging Run Failure”
18 - IF OK
19 - External Script: C:\Users…\telegram_me.vbs “Leo Triplet Sequence Successful”
20 - Sequence: Start Immediately - End 04:00:00 [hh:mm:ss] - C:\Users…\Voyager\ConfigSequence\Leo Triplet Red.s2q
21 - IF ERROR
22 - External Script: C:\Users…\telegram_me.vbs “Leo Triplet Imaging Run Failure”
23 - IF OK
24 - External Script: C:\Users…\telegram_me.vbs “Leo Triplet Sequence Successful”
25 - Sequence: Start Immediately - End 04:00:00 [hh:mm:ss] - C:\Users…\Voyager\ConfigSequence\Leo Triplet Lum.s2q
26 - IF ERROR
27 - External Script: C:\Users…\telegram_me.vbs “Leo Triplet Imaging Run Failure”
28 - IF OK
29 - External Script: C:\Users…\telegram_me.vbs “Leo Triplet Sequence Successful”
30 - Wait Time: 00:10:00 [hh:mm:ss] Interval
31 - Repeat Current Block Until Time: 04:00:00
32 - Block: Terminate
33 - Stop Tracking
34 - Parking
35 - Relay On: 2 - ClientID 1
36 - Relay Off: 7 - ClientID 1
37 - Wait Time: 00:00:02 [hh:mm:ss] Interval
38 - Relay Off: 2 - ClientID 1
39 - Warmup: Async
40 - External Script: C:\Users…\telegram_me.vbs “Good NIght”
41 - Goto End
42 - End
43 - Events
44 - Emergency Suspend: Wait Resume until absolute time : 04:00:00 [hh:mm:ss] - On Resume Timeout Exec Emergency Exit Event
45 - Block: Suspend
46 - Stop Tracking
47 - Parking
48 - Relay On: 2 - ClientID 1
49 - Relay Off: 7 - ClientID 1
50 - Wait Time: 00:00:02 [hh:mm:ss] Interval
51 - Relay Off: 2 - ClientID 1
52 - External Script: C:\Users…\telegram_me.vbs “Suspend Operations”
53 - Emergency Resume
54 - Block: Resume
55 - Unparking
56 - Start Tracking
57 - Relay On: 1 - ClientID 1
58 - Relay On: 7 - ClientID 1
59 - Wait Time: 00:00:02 [hh:mm:ss] Interval
60 - Relay Off: 1 - ClientID 1
61 - External Script: C:\Users…\telegram_me.vbs “Resume Operations”
62 - Emergency Exit
63 - Viking Client Connect: ClientID 1
64 - Block: Close up
65 - Stop Tracking
66 - Parking
67 - Relay On: 2 - ClientID 1
68 - Relay Off: 7 - ClientID 1
69 - Wait Time: 00:00:02 [hh:mm:ss] Interval
70 - Relay Off: 2 - ClientID 1
71 - Warmup: Async
72 - Disconnect Setup
73 - External Script: C:\Users…\telegram_me.vbs “Emergency Shut Down - Raining”

I am using VIking with a Velleman VM110n interface card, to control roof and flap. Hence the relay on-off instructions.

I divided the filters into separate sequences to try and avoid VOyager going back to the beginning of a complex sequence if interrupted.

In last night’s run the first three sequences ran OK. After starting the fourth sequence clouds came in and the weather station switched to Unsafe triggering a Suspend.

My first problem is that the cloud was fluctuating rapidly around the Safe/Undafe boundary. This caused a sequence of Suspend followed immediately by REsume, then Suspend again and so on. The system was bouncing between roof and flap open and roodf and flap closed as fast as it could.

Question - what do I need to add to prevent a Resume until the weather condition has been safe for at least 5 minutes? None of the options in the Emergency Suspend configuration seem to be useful. WAIT SAFE seems to be the answer, but I don’t know where to put it.

Later on things stabilised and conditions were Safe for the rest of the night. However, some cloud obscured the target later on and Voyager attempted to reacquire the target using Precise Pointing. Because of the cloud platesolving failed, and after three tries an error was detected and that sequence stopped and control moved to the next sequence. Which also failed platesolving. Because of the Repeat Block instruction at line 31, Voyager started with the first sequence again, so I captured a few more subs with the Lue filter (Line 5). The Dragscript ended at 04:00, executing Blocl: Terminate (line 32).

If I want to go back to the filter I was using when the interrupt, came should I put each filter sequence in a separate Block? I could then use a Repeat Block until Time to spread my efforts on each filter across the night. Perhaps allowing 1 hour for each filter, for example. Or use the number of completed subs in the sequence file to repeat each filter block until the sequence is complete or the imaging night is over.

Is that a way to do it, or have I missed something very simple.

Thanks in advance for any suggestions.

REgards

old_eyes

You do not wrote about which kind of emergency system use.

For weather integration time is here "Before Resuming Sensor Must Read “OK/Resume/Don’t Care” Conditions for:
https://wiki.starkeeper.it/index.php/Weather_Setup#Weather_Setup_Workspace

For SafetyMonitor usually is provided by driver itself, you can add integration in Voyager Add Integration time management to conditions Safety Monitor Setup - Voyager Wiki

For Viking you can decide integration time for each events:
immagine
https://wiki.starkeeper.it/index.php/Viking_Setup#Viking_Setup_Workspace

No other ways to acquire emergency events in Voyager.
Please take your time in testing your emergency system and check that all work fine before run unattended.

Resume is not predictive and return back to the suspended block or to a defined block, depends on you. The block will be restart from begin you cannot choose which filter to use. if you have so many supend in one night better to evaluate if finish the night also because probably performance of the night is not so good.

I remember to you that for sending telegram message Voyager have a dedicated block.

All the best
Leonardo

Thanks Leonardo.

I saw that you had created a dedicated block for Telegram messages, but I had already implemented the external .vbs call and the focus of this trial was integrating the weather station. I will change to the integrated block for the next runs. Thanks for this useful addition.

My weather station is the Hitec Weather, which is neither the Boltwood or AAG system. So I am using the safety monitor. So this is the solution - " For SafetyMonitor usually is provided by driver itself, you can add integration in Voyager Add Integration time management to conditions".

VIking is OK, I am using it for a second rain monitor and a mains power fail action. That part I am comfortable with.

I take your point about many suspends means a poor night, but we do get nights where there are a few episodes of cloud, but still several hours of good imaging possible. I live in North Wales and the weather changes rapidly. I think this solution is to break the plan for the night into segments that are each a useful amount of data collection.

Thanks for your help.

old_eyes

1 Like