I use an Avalon mount which is EQmod compatible. Under Windows for the mount to rotate at the correct sidereal speed I had to change the parameters of the ASCOM driver and introduce a drift of 0.4 (see image below).
How can I do the same under indi? Should I modify the values of RA which for now are 15.041067? If so, what would be the correct value?
Thanks.
Read More...
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.
Read More...
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.
Joe.
Read More...
Thanks Hans
My only security problem is ti stop motors in the morning.
To be sure everything is stopped at 6am I use this !
Joe
Read More...
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
After 2 sequences and Flip non more guiding and capture.
Read More...
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
Read More...
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!
Thanks
Joe
Read More...
I change some settings and know it works
Mount Model is always purged and guiding calibration is restarted after each slew.
Read More...
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.
Read More...
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
Read More...
Hi guys,
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
This night a put verbose logs to see what is going on.
The meridian flip goes well, and after flip motion, an align action starts. After a large number of solve and slew it ends whit a failure. The scheduler stars guiding and capture begins.
In my understanding of logs, my next photo should be a portion of the sky not aligned with my object but with round stars....
If needed I can attach a portion of the logs (35 mo).
Thanks for you suggestions.
Joseph
Read More...
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).
Joe
Read More...