Wouter van Reeven replied to the topic 'Camera rotation in kstars' in the forum. yesterday

Is the sky map set for equatorial coordinates instead of azimuthal? To try, go west or east (press w or e) and verify the orientation of the horizon. If it is horizontal and close to the bottom of the sky map then you are in azimuthal coordinates. If not then you're in equatorial coordinates. You can switch between the two by pressing the space bar.

HTH, Wouter


Thanks, that clears this up!


Yes I found the dome issue as well though I assumed that it was me because this was the first time that I used KStars on this MacBook. I agree that it should be set to no dome.


To answer my second question myself: yes that works.

So the question remains: what is the difference between the driver in the package and the driver at GitHub?



I am trying to debug issues I have with our ASI2600MC camera and I ran into a curious situation concerning the ASI driver provided by the libasi package. I am on a Raspberry Pi 4 running Ubuntu Mate 20.04 64 bit:

$> uname -a
Linux mulder 5.4.0-1028-raspi #31-Ubuntu SMP PREEMPT Wed Jan 20 11:30:45 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

As you can see I am looking at the package built last night:
$> dpkg -l libasi
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version                         Architecture Description
ii  libasi         1.12~202102230338~ubuntu20.04.1 arm64        Library for ASI Cameras, Filter Wheel, Focuser and ST4

When I look at the contents of the libasi package I get this:
$> dpkg -L libasi

So far all is good. Now, when I check the size of the binary drivers, I see this:
$> ll /usr/lib/aarch64-linux-gnu/libASICamera2.so.1.16.3 /usr/lib/aarch64-linux-gnu/libASICamera2.so /usr/lib/aarch64-linux-gnu/libASICamera2.so.1
lrwxrwxrwx 1 root root      18 Feb 23 00:38 /usr/lib/aarch64-linux-gnu/libASICamera2.so -> libASICamera2.so.1
lrwxrwxrwx 1 root root      23 Feb 23 00:38 /usr/lib/aarch64-linux-gnu/libASICamera2.so.1 -> libASICamera2.so.1.16.3
-rw-r--r-- 1 root root 1887712 Feb 23 00:38 /usr/lib/aarch64-linux-gnu/libASICamera2.so.1.16.3

and this is where it starts to get weird. When I download the driver directly from GitHub, I see this size for the file:
$> wget https://github.com/indilib/indi-3rdparty/raw/master/libasi/armv8/libASICamera2.bin
--2021-02-23 12:34:05--  https://github.com/indilib/indi-3rdparty/raw/master/libasi/armv8/libASICamera2.bin
Resolving github.com (github.com)...
Connecting to github.com (github.com)||:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://raw.githubusercontent.com/indilib/indi-3rdparty/master/libasi/armv8/libASICamera2.bin [following]
--2021-02-23 12:34:06--  https://raw.githubusercontent.com/indilib/indi-3rdparty/master/libasi/armv8/libASICamera2.bin
Resolving raw.githubusercontent.com (raw.githubusercontent.com)...,,, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)||:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2243289 (2.1M) [application/octet-stream]
Saving to: ‘libASICamera2.bin’

libASICamera2.bin                                           100%[=========================================================================================================================================>]   2.14M  3.09MB/s    in 0.7s

2021-02-23 12:34:07 (3.09 MB/s) - ‘libASICamera2.bin’ saved [2243289/2243289]

$> ll libASICamera2.bin
-rw-rw-r-- 1 ashdered ashdered 2243289 Feb 23 12:34 libASICamera2.bin

Looking into CMakeLists.txt for libasi, the only thing I see is that the .bin file corresponding to the system architecture gets copied to a file with the name ending in .so but that doesn't explain the difference in file size. So my questions are:
  1. Why is there a difference in file size?
  2. Can I simply take the .bin file for my architecture and copy that over the .so file in the /usr/lib/aarch64-linux-gnu directory and will the driver work?

I guess I can try out copying the .bin file after making a backup of the existing .so file but that still doesn't explain the difference in file size.

Thanks, Wouter


For me this beta installs as 3.5.2 beta. I see that by clicking on KStars in the Apple menu and then About KStars:


Wouter van Reeven replied to the topic 'Strange guiding behaviour' in the forum. 2 days ago

For future reference: if you click on Individuals -> Error Reporting at the top of this forum then you end up at this page:
which explains how to enable and submit debug logs.


pdmogg wrote: Just to say I really like what's been done with the Polar Alignment in this version ( 3.5.2 ) . The new green and yellow lines showing the ALT/AZ axes really help speed up getting a good alignment. Thanks!

You may want to add that to this thread as well:



Wouter van Reeven replied to the topic 'ASI2600 Settings' in the forum. 2 days ago

I shoot with an ASI2600MC with Ekos myself and I never had that problem. The images process just fine in APP. Once again, please join that forum and Vincent and I can try to help you with your images.


dx_ron wrote: So there is no mechanism to solve an image and make the solved position become the "target"? I was not suggesting using "Do nothing" after the flip, only once you've settled on your framing, then setting it back to "Slew to". Seems like there ought to be a way to solve an image and make that the current Goto target without having to type in RA/Dec coordinates.

No, there is no such option though it would be a great addition!


dx_ron wrote: I wonder what happens if you tell Align to solve with the "Do Nothing" button checked. Will that become the new default re-centering after a flip? You could probably test that with the simulator.

"Do Nothing" literally does that with the mount: nothing. It solves the image and that's it. So if after the meridian flip the mount is not positioned correctly, it will stay positioned incorrectly.


Just to add to this: I edited the INDI config file for the filter wheel and added two more FILTER_SLOT entries and now the filter wheel is working perfectly OK.


Wouter van Reeven replied to the topic 'ASI2600 Settings' in the forum. 3 days ago

This is perfectly normal. The image you see is linear which means that it needs to be stretched before you see all the data in it. Before that you need to debayer the image too though it looks like you stacked your image in APP (judging by the file name). If you come over to the APP forum then I can help you there.