The other day I finally had a chance to snap M33 for a couple of hours. After my image session I wanted to shot some flats, dark flats and bias frames and then I suddenly became uncertain about the auto focuser, so I disconnected that from Ekos before taking the calibration frames.
So my simple question is:
Is the auto focus module suspended during flats, bias and darks?
I contacted Pavle and it turns out the AF3 needs to have the Baud rate set to 115200 instead of 9600. Changing it to 115200 did the trick
Now, get me some nice weather!
Did another test without my mount plugged in. I got "serial" errors and a failure to connect the AF3.
What's going on?
Update complete, but it didn't help. KStars, however, now shuts down after the splash screen and I have to restart it 1-2 times before I works. But AF3 still can't connect.
I just got a new DeepSkyDad AF3 (auto focuser). I updated Kstars/Ekos on my Raspberry Pi 4 to get the latest drivers. I plug the USB cable from the AF3 into my ZWO 294MC Pro's USB hub and start KStars/Ekos.
When hitting connect the AF3 fails and the mount (SkyWatcher HEQ5) fails for a while but then finally connects. If I remove the AF3 from my list of equipment (and unplugs the usb cable) the mount connects right away. I also tried connecting the AF3 directly to my RP4, but the end result is the exact same as before.
I've attached the log-file. Any ideas on what to do?
P.S I'm currently updating (using the AstroPi3 script) KStars/Ekos again to check if that should solve the problem.
Can’t wait until the weather cleares (should be sometime soon in the next decade or so) and start on my list of nebulas.
Last night I tried my first session with my RP4 2gb running KStars on Raspbian.
Polar alignment ran perfectly and smooth (also in full screen).
Guiding ran so I started a small imaging session of 1x60s, 1x120, 1x180, 1x240 and 1x300s subs. During the 180 sub, I wanted to check the Stars on the 120 s and my messing about with the fits viewer, while guiding and taking a 180s sub, caused KStars to crash.
After restarting and reconnecting etc I tried the same imaging session again, this time leasing the poor fits viewer alone. This time no crash.
I then slewed to a New target, solved and synced and started a one hour session of 30s subs - no problems. Darks, Bias and flats afterwards without problems.
So I’ll just try not to push my 2GB RP4 too hard I did notice that my cooler fan was running pretty much all the way through my session.
Just tried again last night, this time with my Raspberry Pi 4 instead of my Mac. Did a rough polar alignment, forgot to level my tripod etc and then ran the Ekos Polar alignment tool. This time no problems, the crosshair was very close to my selected star and only very small adjustments needed to center the star. I haven’t changed anything in my setup besides changing from Mac to RP4. I’m happy.
I've been looking at the Stellarmate App as a way to check and control my setup during the night instead of VNC on my phone. But I'm not really sure how this works.
Do you need the Stellarmate OS or just KStars/Ekos (eg. from rlancaste's AstroPi3 script)?
Do you need an Ekos Live (free or paid) account?
The free version includes 500 MB/month - how is this calculated? 500 MB will run out very fast if just checking some images during the night, focusing and guide calibration. Or am I missing something?
Sorry for the really stupid questions
I can't wait to give this a try again in the (hopefully) near future.
Vox45 wrote: That is interesting. Would that mean when I was only clicking once it was showing the crosshair on the other end of the purple line but I could not see it as it was off screen ? If so, what is the purpose of bringing the crosshair to the other side of the purple line when clicking twice ? As you can see in the screen shot I was centered in that crosshair but the alignment is out by 1° ... This is odd
All the times I've tried to PA I could only see the Purple line across the entire FOV. When moving as far as possible along the line and then redoing the PA to get even closer, I was told be Ekos that the NCP was outside my FOV, eventhough I should've been closer than my initial PA. When the weather clears (should be within the next decade or so ) I'll give it a try again and double clicking this time (I've moved from running KStars/Ekos on my Mac to running it on a Raspberry Pi 4, but haven't had a chance to test it yet).
I think we need some of the developers to look at the thread. Maybe they can tells us about the double click etc.
Ok, I just tried the PA tool in the simulator. That shows the crosshairs right away. Clicking a star moves the purple line and crosshairs to the new location. When double clicking a star, the crosshairs moves to the star in the other end of the purple line. So I don't think you are supposed to double click a star?!
Vox45 wrote: -> when I get to the final screen, I double click on a star in the field to get the correction vector's crosshair
(It took me a while to understand what was happening as I was only "clicking" on a star as it is instructed but only clicking once only moves the purple line to the star but does not show the crosshair...)
Wow! It's also news to me that you need to double click a star. I always just end up with a purple line, but no crosshairs (except the first time I tried - maybe I double clicked by accident then?) so I haven't been able to PA correctly yet. I'll give the double click a try next time.
If your PA error is too large afterwards, then just try and redo the process. This should help improve the PA - I guess.