I have the same problem since trees reduce my sky to a small portion. The only solution that works for me is to schedule 2 or 3 jobs for the night and use "repeat until" for each job. But you will have to estimate end on each job.
To eliminate any issues due to starting focus point, you should start you first autofocus sequence with your best focus point (if you have a bahtinov mask use it to focus your system). Check your mechanics settings : initial step size and out step multiple to be sure that the first capture always show a few stars identified by the search star algorithm. To do that, after a good manual focus, move your focuser using (initial step * out step multiple) and take an image to verify star size and star detectivity.
My only security problem is ti stop motors in the morning.
To be sure everything is stopped at 6am I use this !
I do not have Logs. I will try this night. But in guiding console (still opened this moring) I can't see any error message.
This is a copy of the Analyse Tab
I'm quite new using PI4 and astroberry and I appreciate the the general philosophy of this solution (PI gadget + open software).
By the way I wanted to use the scheduler to have an automated solution (all the rig is in the garden) and capture images during the week without waiting all the night long.
My first attempts are frustrating me since every night something is going wrong.
For instance, this night I schedule a first sequence on NGC3628 (hamburger galaxy) from 10pm to 2am (I have trees in my neighbour's garden) and then a second sequence from 2am to 5am on M64.
For each sequence I wanted to use a LUM filter and an IRpass Filter (it's a test to avoid light pollution). So my sequence was 12 images with Lum + 12 images with IRpass repeated for 2 runs.
This morning I have 12 Lum images, and 11 IRpass images. Just before the 12th IRpass image, the mount do the meridian flip (all is correct) and the guiding hangs and never resumes... The mount waits until 5am and then parks! The second sequence never starts.
So, what should be the best strategy to be sure that after an error or perhaps x minutes without any image captured (This night I have no error, just the capture module waiting for guiding!) to skip current sequence and go to the next one?
Thanks for your help
How do you upgrade an astroberry to 3.5.3 beta ?
Do You really solved this problem.
I'm trying to use this driver in non bulb mode (essential with A7S Star Eater) and I never achieve this operation.
1) No data is saved on A7S memory card (that non a big issue)
2) The photo saved on PI card is always wrong
Just have a look on my first post here indilib.org/forum/ccds-dslrs/8282-a7s-non-bulb-mode.html
To add some new information, when connecting to the A7S, I supposed that a first photo is engaged and when you try to take a photo, in fact Kstars/Ekos deals with the previous one. In this situation you cannot use astrometry and focusing, since all the intelligence is applied to a wrong image!
I change some settings and know it works
I think I will do the same thing. It's slower but it can save me 3 hours of capture.
PDB post=69502 wrote: Think I will switch the "resuse calibration" feature to off again. It's slower but I always used to have good results.
My Reverse DEC setting is set to OFF.
My mount is an Avalon Fast Linear using EQ6 motherboard and Eqmod driver. Comming from windows I have never seen such guiding corrections...
This evening a will plan a first object just near meridian to see what is happening
I'm running last version of Kstars/ekos on a raspberry PI4. Since a few sessions, I have a big issue after meridian flip, all images after flip are showing elongated stars
just like this one
When doing polar align, have you tried using your main image system or your guiding system?
As the polar align uses the solver, the first thing to do is to solve the polar region, to be sure that all the configuration files are downloaded. This is one of the first thing to do in relation to you telescope and camera (do both prime telescope and guider). The best way is to declare you telescope and guider focal length in the mount page (you can save several configurations).
In the align window you have a configuration button witch brings you on the specific page to download configuration files. As the FOV is know, the good files to download are easy to identify (green signal toward each file).
Hi Kurt, are you using a A7S mark1? In this case can you confirm that non bulb mode is working?
I open several posts with no real answer since ekos in non bulb mode seems have a bug when downloading file to the fits viewer.
I describe it here www.indilib.org/forum/ccds-dslrs/8282-a7s-non-bulb-mode.html
Thanks Jurgen to join my request to debug A7S driver.
To add some details, I would say that M mode is possible but when switching to non Bulb mode, capturing an image will result on a faulty situation. The first image will be ok but the second one is still the first, the third one is the second and so on. This situation avoid using autofocus and astrometry since Kstar is not analyzing the good image.
In the last version of indi and gphoto driver, I notice that in fact when using "RAW" mode the capture download "RAW + JPG". This situation leads to use RAW for the first shoot and JPG for the second, introducing a gap between gphoto driver and Kstar.
I open 2 bugs in github here github.com/indilib/indi-3rdparty/issues/339 and here github.com/gphoto/libgphoto2/issues/630
Like Jurgen I not skilled to debug myself the driver code, but I can contribute doing test sessions.