I would like to Retry on a platesolve error and Ignore the error if the Retry fails. I am not sure if nested or sequential Ignore and Retry steps are required. If nested, should the affected steps be specified once or twice. The sequence builder allows nesting so I am guessing that the sequence shown below shouid work.
SEQUENCE
SAVE MOUNT COORDINATES
PROMPT FOR TARGET
IGNORE ERRORS FROM
MOUNT SOLVESYNCONLY
RETRY ERRORS UP TO 1 TIMES
MOUNT SOLVESYNCONLY
END RETRY ERRORS
END IGNORE ERRORS
LOOP 18 TIMES
CAPTURE START
DELAY 600
CAPTURE STOP
MOUNT SOLVESYNCONLY
GOTO SAVED COORDINATES
DELAY 60
END LOOP
END SEQUENCE
IGNORE ERRORS FROM
RETRY ERRORS UP TO 1 TIMES
MOUNT SOLVESYNCONLY
END RETRY ERRORS
END IGNORE ERRORS
That will do the solve/sync initially, try a second time if it fails and then move on regardless. Your initial version would not retry if the first attempt failed (because the first attempt was outside the retry block). Not only that, but it would actually have a second go if the first go succeeded
Thanks Robin, your suggestion makes sense. I wasn't quite sure whether or not to include the step/s to be Retried & Ignored in both or just the Retry, as you suggest.
yes, they are available and can be found in the 'advanced' section. You can also search for commands using the search box above the available steps area - this will filter the commands that are shown (and the sections to only those with matching commands in).
Cheers and thanks for live stacking, polar alignment, sequencer and scripting. Thanks for SharpCap. Also your amazing video basically on Smart Histogram. You are a real gift to Amateur Astronomy. I wrote scripts in MAXIM DL to take images while I sleep. But I can do the same with the sequencer much easier. I don't even know if I'll need your scripting interface as the sequencer might have everything I need. Cheers mate.
If you are a big user of the sequencing tool and you find things that are awkward or plain impossible that you really want to do, please let me know... Real world feedback is invaluable!
I'm a little confused on how to use the sequencer guiding commands while livestacking a list of images. I've figured out how to use a text file with a list of coordinates, and loop through them to position the scope using a platesolve, restart the guider, and then livestack. But the PHD control seems to be unreliable. What commands should I be using to restart autoguiding after the scope is moved and adjusted and before I start livestacking again. It seems often the guiding is not always restarting but the images don't seem to suffer too much as the exposures recommended by the smart histogram are usually in the 5 to 15 second range. Because of learning about the error commands, I'm able to continue the sequence even after the guiding attempt fails after fixed number of tries. Do I even need to restart PHD after each scope move? Can you please explain what sequencer guiding commands I should use please?
well, if you are using SharpCap 4.1 beta then the best bet is to not worry about it, as it should all be automatic...
In SharpCap 4.1, it should pause guiding automatically when the mount is asked to slew to new co-ordinates and then resume guiding when the slew is complete. This ought to work as long as SharpCap is currently connected to the guiding application, so in the case of running a sequence it should happen if you had a 'guiding connect' step earlier in the sequence.
Now, bringing live stacking into the mix complicates things a bit... Live stacking will handle guiding itself if you have previously set the appropriate options when live stacking manually. If you have live stacking in your sequence and no 'guiding connect' step then each live stack will separately connect to PHD2 when it starts and disconnect when the stack ends. This disconnection means that when you come to perform the GOTO adjustment for the next target, the guiding will not be connected, so no guiding pause will happen.
In SharpCap 4.1, if you have previously connected using a guiding connect step then the live stacking should leave guiding connected. This may not be the same in SharpCap 4.0 (a lot of this code re-written for SC 4.1).