I haven't had my AVX mount for a couple of years but I do remember that I needed to do an align before I could use Ekos. There was a discussion 3 years back about an AVX doing weird things which I replied to... www.indilib.org/forum/mounts/7156-mount-...-me/55522.html#55522

In any case the comment in my reply helped me remember the steps I used with my AVX, I set it up roughly polar aligned then when powering up I did a Quick Align. That skipped having to do star alignments with an eyepiece and allowed the mount to think it was aligned. Then I did a polar alignment with the polar alignment tool. Once that is done using Kstars/Ekos I could pick a couple of stars to goto then use the alignment tool with sync to mount.

About picking your camera. The latest version uses Optical Trains. There a drop down at the top of the Alignment tool to pick your optical train. You can also edit your optical trains by clicking on the pencil icon next to the drop down.


Quick fix, just had to build and install libasi.

Thank you.


I built and installed the latest 2.0.1 indi-core on Raspberry Pi OS 64 bit no problem.
Then I grabbed the indi-3rdparty 2.0.1 to build the asi drivers. The build for asi_focuser failed with the following:

[  7%] Building CXX object CMakeFiles/indi_asi_focuser.dir/asi_focuser.cpp.o
[ 21%] Built target indi_asi_st4
[ 35%] Built target indi_asi_wheel
[ 57%] Built target indi_asi_single_ccd
[ 71%] Built target asi_camera_test
[ 92%] Built target indi_asi_ccd
/mnt/usbDrive1/Projects/indi-3rdparty/indi-asi/asi_focuser.cpp: In member function ‘virtual bool ASIEAF::updateProperties()’:
/mnt/usbDrive1/Projects/indi-3rdparty/indi-asi/asi_focuser.cpp:202:34: error: ‘EAFGetSDKVersion’ was not declared in this scope
  202 |         VersionInfoSP[1].setText(EAFGetSDKVersion());
      |                                  ^~~~~~~~~~~~~~~~
/mnt/usbDrive1/Projects/indi-3rdparty/indi-asi/asi_focuser.cpp: In member function ‘bool ASIEAF::readMaxPosition()’:
/mnt/usbDrive1/Projects/indi-3rdparty/indi-asi/asi_focuser.cpp:296:10: error: ‘EAFStepRange’ was not declared in this scope; did you mean ‘stepRange’?
  296 |     rc = EAFStepRange(m_ID, &stepRange);
      |          ^~~~~~~~~~~~
      |          stepRange
make[2]: *** [CMakeFiles/indi_asi_focuser.dir/build.make:82: CMakeFiles/indi_asi_focuser.dir/asi_focuser.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:105: CMakeFiles/indi_asi_focuser.dir/all] Error 2
make: *** [Makefile:149: all] Error 2

I'm fairly certain I could build the indi-3rdparty 2.0.0 version without issues. Can anyone assist?



I use a post capture script to rsync my pictures to my NAS. I run the rsync in the background and return immediately so the capture queue does not wait for the rsync to complete. You could try to nest your scripts and have the post capture script run a second script in the background and return immediately.


Just a quick note than an alternative to getting a dummy HDMI dongle is to use the dummy monitor driver xserver-xorg-video-dummy. I've used it with X11vnc on Ubuntu 20.04 and 22.04. I use a script to switch between dummy mode and HDMI mode depending on whether or not I want to run my Mele PCs headless or not.

If interested just google xserver-xorg-video-dummy. There are articles out there on setting it up.


I've been searching through the forum looking for the polar alignment issue that I had last night (not easy with a limit of 20 results). In any case, I had an issue with the polar alignment refresh last night that seems similar to the one reported here. Although I did not get any crashes, I did have problems with the FITS Viewer refresh during polar alignment.

The main issue seemed to be that the FITS viewer would not refresh. I went through the PA tool multiple times, I'd get to the PA result, toggle to the full screen FITS Viewer, select a star, Alt-Tab back to the PA tool, click Next then click refresh and although the "Image #" was incrementing every second the FITS viewer was not refreshing the image. Hard to do the alignment without the refresh.

I had used the PA tool the night before without issue so I was trying figure out what I changed to break it. Ultimately it seemed to be related to using dark images. The previous evening I did not used Dark images and earlier in the day I had created a set of new dark images using the Dark Library tool. So, I had enabled the dark check box on the Align tool. As soon as I unchecked the Dark box the FITS Viewer refresh started working again.

Another note, it seems that the KStars 3.5.8 version now has a minimum refresh of 1.0 second. I'm pretty sure I used to use 0.5 seconds with Update PA Error on.

I'm using KStars 3.5.8 on Ubuntu 20.04.4 LTS. Guide camera is QHYCCD QHY5 III 178C.


Tunafish replied to the topic 'How I lost whole night if imaging' in the forum. 2 years ago

This also happened to me a couple months back but I have not seen it happen again. At the time I thought it might be related to using the new dark library tool in the Ekos CCD tab. I believe the darks are written to /tmp before they are processed and added to the dark library. Somehow this over wrote the directory setting in the main CCD tab. Now, I have not been able to repeat this so it was more of a guess as to what happened.