No worries, Hy.  Sometimes a step back is needed to proceed smile.pngI am sort of afraid that it would definitely be needed to be useful in the Scheduler.  At least, I find it hard to believe that for most people the obstruction curve would be monotonic in Az without either losing actually unobstructed area or leaving obstructions unhandled....

Read More...

Hello Hy,
I've attached a screenshot taken with an older version of kstars that shows how the horizon map actually should look. In the area of the overhang it is painting things twice it seems. But your further text explains why:
This of course is completely different from how it worked before. You cannot mark general obstructions anymore, as they often do not follow this linear approach and have overhangs. So I think this constraint brings a substantial reduction in usefulness of the horizon map sad.png

Read More...

This is independent of the kstars version, it is an INDI problem (of libasi, to be exact). So that are the packages to up/downgrade.

What does 'ls -l /usr/lib/libEAFFocuser*' tell? And if you run 'indi_asi_focuser'?

Read More...

With joy I noticed that the Artificial Horizon now properly updates also in the Ra-Dec mode silly.png
However, it now has a drawing error (both in Ra-Dec and Alt-Az modes) if features of the map "go backwards in azimuth" - see the attached image.  It's a tower with a larger platform on top, so there are points where Az decreases compared to the preceeding ones.  Here's an part of the Az,Alt values in that area:

     237.900      14.0500
      249.600      12.8500
      256.700      12.1000
      256.300      32.0500
      248.550      33.7000
      248.300      37.1000
      263.650      48.2000
      279.450      38.8500
      279.750      0.00000
      270.000      0.00000
It was rendered properly in the old version.
 

Read More...

Seems you are missing a link libASICamera2.so.1 -> libASICamera2.so.1.16
In doubt you can create that yourself (ln -s libASICamera2.so.1.16 /usr/lib/libASICamera2.so.1).

I just compiled the latest version here on my computer (Tumbleweed). No issues, indi_asi_ccd doesn't crash, and drives the camera.

Read More...

Peter Sütterlin replied to the topic 'Internal guider questions' in the forum. 2 weeks ago

As for guide log analysis:  phdlogview perfectly reads and analyzes the log files from EKOS as they are (in ~/.local/share/kstars/guidelogs/).
 

Read More...

Hi Jo,

yes, the link was what I was (trying to) point out. The executable is linked to libASICamera2.so, but this usually is a link to the actual (versioned) library. I was just not sure where they actually end up on your systems, as I don't have debian based installations around....
In my case it's like

/usr/lib64/libASICamera2.so -> libASICamera2.so.1
/usr/lib64/libASICamera2.so.1 -> libASICamera2.so.1.16
/usr/lib64/libASICamera2.so.1.16
and I had suspected that something wasn't updated properly in the package, and maybe leftovers from the 1.17 install had survived.

I would completely remove libasi, re-install it, and check where the links are pointing, and that they match the above pattern...

Read More...

mhammady post=70431 wrote: Hi Peter,

These readings were from the WO Z61 with a 2" Rack/Pinion focuser, and I'm connected directly to the course knob (not the fine). Any ideas what else can be wrong?
 


In that case it could be temperature variation.  If you put out the telescope from a warm room into the cold, it will change focus until it's temperature stabilized.  For a test like the above, I'd wait at least an hour after having brought the telescope out (My 140mm needs almost 2 hours...)
Or the coupler between motor and focus axis isn't solidly fixed.  Apart from that, I'm out of ideas....
 

Read More...

Maybe the code checks internally whether both name parts are non-zero?
My FITS files do contain my name properly, so in principle it seems to work.
Have you tried entering some spaces for the second name part?

Read More...

I just looked around a bit. For the 294 it's claimed that high speed mode switches the DAC between a 14bit and a 10bit version. Looks like the 2600 is similar? But it is really hard to find an explanation what this mode actually does.... ISTR (but cannot check ATM) that also the 1600 has a high-speed mode that ZWO recommended not to use... :(

Read More...

If you look at the values, both show a clear trend for decreasing values.
My suspicion would be that there is slip somewhere in your focuser train:  Either it is a Crayford-type that works just by friction between the axis and the tube, or you have connected the focus motor to the fine drive knob that usually also has some intrinsic slip.

But if your focuser has slip, backlash correction is quite futile anyhow. :(
 

Read More...

Peter Sütterlin created a new topic ' Question about versioning' in the forum. 2 weeks ago

To get unique and sequential names for my RPM packages of INDI, I use the VERSIN.MINOR.RELEASE from indiapi.h (because the git version number often was aout of sync, similar to kstars), followed by the git tag as given by 'git describe --tags'.
But for the second time now, the consecutive number in the git describe has been reset without the main version changing.
So after 1.9.0-106_g95a492dc from April 18, I now get 1.9.0-4_g8cb8dd5c, and of course the package manage doesn't want to update to that package, assuming it's much older than the installed one  :(

How do you handle this?
 

Read More...