I never got astap to blind solve. So before polar alignment, I'll double click Polaris in the kstars star map, then do an ASTAP solve with "do nothing" checked to set the camera wcs. Then run polar alignment.
Never works unless I track Polaris in kstars first.
El Corazon wrote:
astromyr wrote: Great! I’ve been wanting capture controls in the fits viewer. l.e. exposure time, gain, start, stop. And perhaps focus. Integrated in the viewer (the same way as the histogram split view) is better for my usage pattern than a floating widget that can hide other stuff or become hidden.
I am not sure how that would work. Once the FITS file is acquired, it is too late to change the .esq Sequence file that controls the raw data acquisition in the scheduler.
Can you explain how you see that integration in the FITS viewer to feed back on the saved .esq file?
Great! I’ve been wanting capture controls in the fits viewer. l.e. exposure time, gain, start, stop. And perhaps focus. Integrated in the viewer (the same way as the histogram split view) is better for my usage pattern than a floating widget that can hide other stuff or become hidden.
The PI4 is picky on the power. The official PI4 power adapter is 5.1 V. I have an adjustable power brick set to 5.2V, and the PI is connected to both asi294mc, asi120mm, and eqdir directly without hub. I just keep the WiFi active. WiFi performance is poor due to USB3 interference, so I have cabled Ethernet to my windows laptop running kstars. Pi 4 is running astroberry. Very stable setup.
Is there a particular reason you run kstars on the RPi?
I'm very happy with Astroberry 2 perfomance on RPi 4 with 4 GB RAM. The builtin wifi is too slow for anything but simple management.
I would not run kstars on the RPI for performance reasons, and definately not if using the builtin wifi.
Running kstars on a Windows laptop with cabled Ethernet to the indi server on the RPi4. This way I have very snappy response when imaging, and better color reproduction in the kstars fits viewer than if using VNC.
When guiding with the builtin guider from windows, the lag with wifi is unacceptable and guiding becomes very erratic. Running phd2 locally on the RPi 4 solves this. The Ekos guider via Ethernet cable is also fine.
The FITS download times I get on Wifi (10m from wifi router, one wall) is 6-7 sec / FITS. With Ethernet it's 1 sec / FITS.
I didn't want to connect a USB WiFI to the RPi4 as I'm afraid it wil interfere with camera USB traffic.
RPI 4 / 4 GB / 125 GB fast SD card / astroberry 2.0.1. All latest updates (sudo apt update; sudo apt full-upgrade)
Skywatcher Az GTi, with EQMOD USB cable (Not using built-in wifi)
ZWO ASI294MC with DIY cooling
ZWO ASI120MM Mini
Astrocat 250 mm
30mm F4 miniscope
I just keep everything setup and ready to go. After poweron I connect kstars from my laptop and start the polar alignment in ekos. For simplicity, I tend to use the builtin guider rather than phd2.
I run Astroberry on a RPi4 with AZ-GTi, ASI294mc for imaging, and asi120mm mini for guiding. I leave everything outside and connect to the RPI4 from Kstars on Windows indoors. Works very well!
The RPI4 wifi doesn't have the longest reach (as the AZ-GTi). Also, I have issues with the AZ-GTi outside due to the massive amount of wifi routers nearby.
So I ended up using a EQDIR cable (made one from a FTDI 3.3V uart cable) from the RPi to the AZ-GTi. Rosck solid. I also run Ethernet cable from the RPi to the windows computer or the house Wifi accesspoint.
I'm not using the synscan app anymore, except for configuring the Wifi.
I polar align with the ekos polar alignment tool, and then pick about 3 points around in the sky, that ekos plate solves and syncs. To gotos get pretty good from that.
If you connect by wifi, you can do this a number of ways:
1) Connect the RPi, AZ-GTi, and synscan app device/computer to your house access point.
2) Connect the AZ-GTi and synscan app device/computer to your RPi
3) Connect the synscan app device/computer and RPi to the AZ-GTi accespoint.
You can create a prioritized list of wifi configurations in the astroberry so it will connect to the house wifi first, connect to the AZ-GTi second, or create an accespoint third, if the two other fails.
I love this rig! I'm up and imaging in 25 minutes including polar alignment. I guess part of the success is that I'm using a 250 mm f4 spacecat for imaging, thus it's fairly forgiving about accuracy
Yes, home position is north when the mount is powered up, but the scope may be pointing elwehere as the motor encoders are relative.
With the synscan app, I always enable the internal encoders after poweron, and tell the scope to goto (-90,90). Then the scope is aligned with the home position, and the internal decoders can be switched off. Some claim that there is less precision with the internal decoders - I don't know.
Using EQ wedge.
I use a twin scope bracket, so I need the black dowetail screw on the mount to point towards polaris - that's why I goto (-90,90)
Got it working! Compiled from git. You need to also compile and install 3rdparty.
Did not have time for an extensive test - only slewing around in my living room.
Wather forcast is cloudy for the next 10 days...
Excellent! Looking forward to try it out