×

INDI Library v1.9.3 Released (11 Nov 2021)

Bimonthly Stable INDI Library release introduces new drivers and fixes for existing ones. Some highlights:

Re:New Polar Alignment Scheme and Features

  • Posts: 27
  • Thank you received: 0
Hi there,
Just to say thank you so much for doing this, the new "Triangle" really speeds up getting an accurate ( as reported ) alignment. I haven't yet checked it against the PHD2 drift align or guiding assistant but plan to. I'm fairly new to this hobby so anything that makes it easier is greatly appreciated.

I found one thing that has now changed that I haven't seen reported in what I've read so far on this thread. When you've finished your polar alignment and hit Done or Stop, it used to slew my mount back to the parked position automatically ( I'm aligning on NCP area ), but now it doesn't and you have to do that yourself. Don't know if this is a bug of a feature, but thought I'd mention it.

Thanks again, great work!
9 months 1 week ago #67706
The topic has been locked.
  • Posts: 55
  • Thank you received: 2
Finally I got a few logs:

[2021-02-21T19:07:36.162 CET INFO ][ org.kde.kstars.ekos.align] - "Number of Matches: 34"
[2021-02-21T19:07:36.163 CET INFO ][ org.kde.kstars.ekos.align] - "Solved with index: 4209"
[2021-02-21T19:07:36.165 CET INFO ][ org.kde.kstars.ekos.align] - "Field center: (RA,Dec) = (88.7944, 7.40904) deg."
[2021-02-21T19:07:36.166 CET INFO ][ org.kde.kstars.ekos.align] - "Field center: (RA H:M:S, Dec D:M:S) = (05:55:10.647, +07:24:32.542)."
[2021-02-21T19:07:36.167 CET INFO ][ org.kde.kstars.ekos.align] - "Field is: (1023.19, -1.60195) deg from search coords."
[2021-02-21T19:07:36.168 CET INFO ][ org.kde.kstars.ekos.align] - "Field size: 2.35378 x 1.77885 degrees"
[2021-02-21T19:07:36.169 CET INFO ][ org.kde.kstars.ekos.align] - "Pixel Scale: 1.82006\""
[2021-02-21T19:07:36.171 CET INFO ][ org.kde.kstars.ekos.align] - "Field rotation angle: up is 82.5178 degrees E of N"
[2021-02-21T19:07:36.172 CET INFO ][ org.kde.kstars.ekos.align] - "Field parity: neg\n"
[2021-02-21T19:07:36.173 CET INFO ][ org.kde.kstars.ekos.align] - "Solver completed after 0.55 seconds."
[2021-02-21T19:07:36.174 CET INFO ][ org.kde.kstars.ekos.align] - "Solver RA (88.79436) DEC (7.40904) Orientation (82.51781) Pixel Scale (1.82006)"
[2021-02-21T19:07:36.188 CET INFO ][ org.kde.kstars.ekos.align] - "Solution coordinates: RA (05h 56m 19s) DEC ( 07° 24' 38\") Telescope Coordinates: RA (05h 56m 19s) DEC ( 07° 24' 31\")"
[2021-02-21T19:07:36.219 CET INFO ][ org.kde.kstars.indi] - ZWO CCD ASI1600MM Pro : "[INFO] CCD FOV rotation updated to 82.5178 degrees. "

Up to here, I slewed to a star, a bit east of the meridian, I think it was Beteigeuze...


[2021-02-21T19:07:57.046 CET DEBG ][ org.kde.kstars.ekos.mount] - Mount status changed from "Tracking" to "Idle"

Here I had to stop tracking manually, because the "start" button was greyed out.

[2021-02-21T19:08:16.485 CET INFO ][ org.kde.kstars.ekos.align] - "Starting Polar Alignment Assistant process v2.3 ..."
[2021-02-21T19:08:16.485 CET DEBG ][ org.kde.kstars.indi] - ISD:Telescope: UnParking...

[2021-02-21T19:08:16.497 CET INFO ][ org.kde.kstars.ekos.align] - "Capturing image..."
[2021-02-21T19:08:16.535 CET INFO ][ org.kde.kstars.indi] - iOptron CEM25 : "[INFO] Telescope already unparked. "
[2021-02-21T19:08:18.046 CET DEBG ][ org.kde.kstars.ekos.mount] - Mount status changed from "Idle" to "Tracking"
[2021-02-21T19:08:20.569 CET DEBG ][ org.kde.kstars.indi] - processBLOB() mode 4
[2021-02-21T19:08:20.898 CET INFO ][ org.kde.kstars.ekos.align] - "Image received."
[2021-02-21T19:08:20.904 CET INFO ][ org.kde.kstars.ekos.align] - "Automatically downsampling the image by 3"
[2021-02-21T19:08:20.946 CET INFO ][ org.kde.kstars.ekos.align] - "Evaluating Installed RAM for inParallel Option. Total Size of Index files: 1.22301 GB, Installed RAM: 7.36862 GB, Free RAM: 4.33127 GB"
[2021-02-21T19:08:20.948 CET INFO ][ org.kde.kstars.ekos.align] - "There should be enough RAM to load the indexes in parallel."
[2021-02-21T19:08:20.950 CET INFO ][ org.kde.kstars.ekos.align] - "+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++"
[2021-02-21T19:08:20.951 CET INFO ][ org.kde.kstars.ekos.align] - "Starting Internal StellarSolver Sextractor with the 4-SmallScaleSolving profile . . ."
[2021-02-21T19:08:21.101 CET INFO ][ org.kde.kstars.ekos.align] - "Stars Found before Filtering: 355"
[2021-02-21T19:08:21.103 CET INFO ][ org.kde.kstars.ekos.align] - "Removing the stars with a/b ratios greater than 1.5"
[2021-02-21T19:08:21.104 CET INFO ][ org.kde.kstars.ekos.align] - "Keeping just the 50 brightest stars"
[2021-02-21T19:08:21.105 CET INFO ][ org.kde.kstars.ekos.align] - "Stars Found after Filtering: 50"
[2021-02-21T19:08:21.107 CET INFO ][ org.kde.kstars.ekos.align] - "+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++"
[2021-02-21T19:08:21.108 CET INFO ][ org.kde.kstars.ekos.align] - "Configuring StellarSolver"
[2021-02-21T19:08:21.404 CET INFO ][ org.kde.kstars.ekos.align] - "Scale range: 85.3931 to 169.428 arcmin wide"
[2021-02-21T19:08:21.406 CET INFO ][ org.kde.kstars.ekos.align] - "Image width: 4656 pixels, Downsampled Image width: 1552 pixels; arcsec per pixel range: 3.30128 to 6.55004"
[2021-02-21T19:08:21.408 CET INFO ][ org.kde.kstars.ekos.align] - "+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++"
[2021-02-21T19:08:21.409 CET INFO ][ org.kde.kstars.ekos.align] - "Starting Internal StellarSolver Astrometry.net based Engine with the 4-SmallScaleSolving profile. . ."
[2021-02-21T19:08:21.463 CET INFO ][ org.kde.kstars.ekos.align] - "+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++"
[2021-02-21T19:08:21.484 CET INFO ][ org.kde.kstars.ekos.align] - "Solve Log Odds: 104.543"
[2021-02-21T19:08:21.486 CET INFO ][ org.kde.kstars.ekos.align] - "Number of Matches: 17"
[2021-02-21T19:08:21.487 CET INFO ][ org.kde.kstars.ekos.align] - "Solved with index: 4211"
[2021-02-21T19:08:21.488 CET INFO ][ org.kde.kstars.ekos.align] - "Field center: (RA,Dec) = (88.8818, 7.40959) deg."
[2021-02-21T19:08:21.489 CET INFO ][ org.kde.kstars.ekos.align] - "Field center: (RA H:M:S, Dec D:M:S) = (05:55:31.642, +07:24:34.538)."
[2021-02-21T19:08:21.490 CET INFO ][ org.kde.kstars.ekos.align] - "Field is: (1013.82, -3.59769) deg from search coords."
[2021-02-21T19:08:21.492 CET INFO ][ org.kde.kstars.ekos.align] - "Field size: 2.35346 x 1.77875 degrees"
[2021-02-21T19:08:21.493 CET INFO ][ org.kde.kstars.ekos.align] - "Pixel Scale: 1.81989\""
[2021-02-21T19:08:21.494 CET INFO ][ org.kde.kstars.ekos.align] - "Field rotation angle: up is 82.5068 degrees E of N"
[2021-02-21T19:08:21.495 CET INFO ][ org.kde.kstars.ekos.align] - "Field parity: neg\n"
[2021-02-21T19:08:21.497 CET INFO ][ org.kde.kstars.ekos.align] - "Solver completed after 0.55 seconds."
[2021-02-21T19:08:21.498 CET INFO ][ org.kde.kstars.ekos.align] - "Solver RA (88.88184) DEC (7.40959) Orientation (82.50679) Pixel Scale (1.81989)"
[2021-02-21T19:08:21.499 CET INFO ][ org.kde.kstars.ekos.align] - "Solution coordinates: RA (05h 56m 40s) DEC ( 07° 24' 39\") Telescope Coordinates: RA (05h 56m 39s) DEC ( 07° 24' 31\")"
[2021-02-21T19:08:21.507 CET INFO ][ org.kde.kstars.ekos.align] - "Please wait while WCS data is processed..."
[2021-02-21T19:08:21.547 CET INFO ][ org.kde.kstars.indi] - ZWO CCD ASI1600MM Pro : "[INFO] CCD FOV rotation updated to 82.5068 degrees. "
[2021-02-21T19:08:25.831 CET INFO ][ org.kde.kstars.ekos.align] - "WCS data processing is complete."


After that, polar alignment performs great....

I think, that when you change the step size from 30 degree to e.g. 20, then Tracking stops automatically and the start button becomes active, but after the initial slew and without changing the default parameters, the start button keeps being disabled, which is understandable, because how should the software know, that a polar alignment is "wanted"... .

Regards

Dirk
iOptron CEM25P
Skywatcher Evostar 72 ED DSPro
Explore Scientific ED 102
ASI 1600Mm Pro ASI EFW Mini
QHY 8L
DeepSky Dad AF1 motor focus
ASI 120MM Mini and Bresser (Touptek) 290 Guidecams
Sykwatch EvoGuide 50/242 and NoName 50/175 Guidescopes
Raspberry Pi 3 and 4
9 months 1 week ago #67709
The topic has been locked.
  • Posts: 727
  • Thank you received: 336
Paul (@pdmogg),

There is a (well hidden) checkbox in the alignment options menu, top tab now called "StellarSolver Options", that's called "auto park".
It should control whether the system parks after polar alignment or not. See the screenshot below.

Hy

Orion Atlas Pro, William Optics ZS105, Moonlight V2 focuser, GSO RC10 w/RSF focuser
ZWO ASI1600, Astronomik Filters, ST80, QHY 5L-IIm guidecam.
KStars/Ekos/Indi on NUC10 & RPi4 w/SSD -- Ubuntu
Projects: Terrain, Polar Align, Analyze, Linear Focuser, SEP MultiStar & GPG Guide, FITS autostretch.
9 months 1 week ago #67715
Attachments:
The topic has been locked.
  • Posts: 727
  • Thank you received: 336
Dirk,

I took at quick look at the code (and, BTW, this part of the code was not changed with my recent polar-alignment changes).
From what I can see, there is no issue with tracking during polar alignment. In fact, the code explicitly turns on tracking
if it isn't already tracking (though after Start is clicked).
See invent.kde.org/education/kstars/-/blob/m...lign/align.cpp#L5398

However, the Start button is explicitly disabled during slewing and re-enabled when slewing is completed:
invent.kde.org/education/kstars/-/blob/m...lign/align.cpp#L5868

I'll bet that, as I mentioned earlier, for some reason the end-of-slew status-change message was missed,
so the Start button was never re-enabled. Then, I think that when you turn off tracking, that causes a change the mount's status,
and that causes the setMountStatus method to be called again
invent.kde.org/education/kstars/-/blob/m...lign/align.cpp#L5868
and this causes the Start button to be re-enabled!

To show that this theory might be correct, I'll bet that if you did the following, it would also work.
After your slew is complete, if the Start button is not enabled, then disable tracking, and then a few seconds later re-enable tracking
(so that you've really done nothing but "shake things up").
My guess is that after all that the Start button will be enabled, with tracking on, and you'd be able to polar align.

If this is the case, I can forward this issue to someone else who knows more about mount/Ekos communications than I do.
Hy
Orion Atlas Pro, William Optics ZS105, Moonlight V2 focuser, GSO RC10 w/RSF focuser
ZWO ASI1600, Astronomik Filters, ST80, QHY 5L-IIm guidecam.
KStars/Ekos/Indi on NUC10 & RPi4 w/SSD -- Ubuntu
Projects: Terrain, Polar Align, Analyze, Linear Focuser, SEP MultiStar & GPG Guide, FITS autostretch.
9 months 1 week ago #67727
The topic has been locked.
  • Posts: 55
  • Thank you received: 2
Hello Hy,
the explanation sounds reasonable for me, I will check the turn off / turn on procedure when the next opportunity arises. and keep you updated.


Generally speaking, I am very happy with the easy and precision of the new polar alignment and especially that you do not need a view to north anymore.

Thank you again

Dirk
iOptron CEM25P
Skywatcher Evostar 72 ED DSPro
Explore Scientific ED 102
ASI 1600Mm Pro ASI EFW Mini
QHY 8L
DeepSky Dad AF1 motor focus
ASI 120MM Mini and Bresser (Touptek) 290 Guidecams
Sykwatch EvoGuide 50/242 and NoName 50/175 Guidescopes
Raspberry Pi 3 and 4
9 months 1 week ago #67732
The topic has been locked.
  • Posts: 55
  • Thank you received: 2
Hello Hy,
I can confirm, that disabling tracking and enabling immediately after this, keeps the "Start" button enabled.
I slewed to the target with platesolve and slew to target enabled, maybe this is where the information of the movement gets lost. I will check, what happens, if I:
1. simply slew to the target
2. slew to the target with plate solve and sync.....



Regards

Dirk
iOptron CEM25P
Skywatcher Evostar 72 ED DSPro
Explore Scientific ED 102
ASI 1600Mm Pro ASI EFW Mini
QHY 8L
DeepSky Dad AF1 motor focus
ASI 120MM Mini and Bresser (Touptek) 290 Guidecams
Sykwatch EvoGuide 50/242 and NoName 50/175 Guidescopes
Raspberry Pi 3 and 4
9 months 1 week ago #67820
The topic has been locked.
  • Posts: 221
  • Thank you received: 20
Hello Hy,
Radek has just updated Astroberry to include KStars 3.5.2. so I have now been able to test out your new upgraded polar alignment with the right angle triangle of adjustment. Works very well - thank you for your intensive work on it! I have yet to try out your suggestion of using manual adjustment to turn the RA axis through 60° East in advance of the PA routine. This should compensate for the PA routine turning the RA axis through two 30° shifts to end up in the Park position where the right angle triangle will have horizontal and vertical sides and the hypotenuse should directly describe the adjustment vector. I am also yet to try PA elsewhere than at the NCP, not normally needed where I set up my equipment, but could have major benefits for a friend who lives in a bowl with no view of Polaris.
Thanks again, Ed
Currently running KStars/Ekos/Indi on two Raspberry Pi 4Bs 4GByte under Raspberry Pi OS thanks to Astroberry
Two mounts, two Fracs, a Newt and a Mak and a couple of OSC cameras.
9 months 2 days ago #68024
The topic has been locked.
  • Posts: 19
  • Thank you received: 1
I could finally try the new polar alignment of 1.5.2 and it looks great. The circle which marks the star selected for the movement is of great help in case of correcting to fast.

However for me the alignment of the green and yellow line with Az/Alt knobs does not seem to correlate and I still follow the direct vector purple line. I would be keen to understand why that is.

The only idea I have so far is that it might be caused by the use of a dual mount where the main telescope and the guider and the main telescope are mounted side by side. So both are outside of the actual rotation axis (see attachement showing my 'home' position.)

  

Is it possible that my setup prevents that I can follow the vectors straight indicating the Alt/AZ corrections?

Thanks for any hints on what I should do differently or adjust to take full advantage of the new feature.

Alex
Standard setup: EQ6R, Williams Megrez 72- ASI 533MC -ZWO EAF, 50 mm viewfinder - ASI 120MM
Last edit: 8 months 1 week ago by Alexander Weis.
8 months 1 week ago #69008
Attachments:
The topic has been locked.
  • Posts: 221
  • Thank you received: 20
If your mount begins the PA routine from the Park (or Home) positions, then, when you come to see the correction vectors, the scopes have rotated by 60° to the West (or East). Therefore Alt and Az mechanical adjustments will move the chosen star along lines which are 60° rotated from vertical and horizontal on your display. If you want to avoid this you should start the PA process from a pre-rotated start position 60° to the East (or West). I have tried this, but in the end I've just accepted that the green and yellow vectors are the directions of the Alt and Az adjustments. ,
Currently running KStars/Ekos/Indi on two Raspberry Pi 4Bs 4GByte under Raspberry Pi OS thanks to Astroberry
Two mounts, two Fracs, a Newt and a Mak and a couple of OSC cameras.
8 months 1 week ago #69009
The topic has been locked.
  • Posts: 727
  • Thank you received: 336
Alex,

Could you explain a little more? You say your star follows the purple line when you're correcting polar alignment. Is that with the Alt knob, or the Az knob, or both? If you're pointed somewhere near the pole, those two knobs should move your telescope is orthogonal directions, so it would be surprising that they both move the star along the purple line.  If almost all of your alignment error is in one of the axes, then moving the offending knob, would, of course be pretty similar to the purple line.

As an experiment, you might intentionally misalign both axes by, say, 20 or 30 arc-minutes and see if you still get the same behavior.

FWIW, at least for my setup, I don't believe the numbers much for anything under 1 arc-minute, or perhaps half that. I wouldn't recommend thinking about arc-seconds. 

Thanks for trying it out,
Hy
 
Orion Atlas Pro, William Optics ZS105, Moonlight V2 focuser, GSO RC10 w/RSF focuser
ZWO ASI1600, Astronomik Filters, ST80, QHY 5L-IIm guidecam.
KStars/Ekos/Indi on NUC10 & RPi4 w/SSD -- Ubuntu
Projects: Terrain, Polar Align, Analyze, Linear Focuser, SEP MultiStar & GPG Guide, FITS autostretch.
8 months 1 week ago #69024
The topic has been locked.
  • Posts: 19
  • Thank you received: 1
Hello Hy,

Sorry, I was not clear in my description of what I think is the problem. I (myself) try to follow the purple line to the crosshair and use both knobs for this. So the workflow for me is basically like in the previous version. The movement of the Alt and Az knobs itself is at least close to orthogonal. So with a bit of trial and error I make my way along the purple line using the knobs for Alt and AZ.

With the split into Alt and AZ components in the display that you implemented  my expectation was that I could use this decomposition of the Alt and Az component for the correction. So when I select a star I expected to move only Alt along the yellow line to the edge of the triangle, then only Az along the green line to the crosshair. So only care about one direction at a time. But when moving my Altidude screw on the mount the stars do not move parallel to the yellow line. Same applies to AZ not parallel to the green line.

Wrong expectation that I could move the selected star along the indicated lines, separating the Alt and AZ correction? Do I need to slew back to home before using the hardware knobs as the calculation of the vectors is based on the first position?

Thanks!
Alex

In case this is relevant: I start in the home position and slew 30 degrees east with each step so when I start turning the hardware knobs the mount is rotated by 60 degrees. I could see Polaris from where I set up my mount and start close to the pole. At the moment I use my main scope for the polar alignment(432 mm focal length, camera ASI 533MC). I'm not  striving for extreme precision below an arcminute.
Standard setup: EQ6R, Williams Megrez 72- ASI 533MC -ZWO EAF, 50 mm viewfinder - ASI 120MM
8 months 1 week ago #69030
The topic has been locked.
  • Posts: 208
  • Thank you received: 25
Hi,

could it be your mount is not level? You can perfectly polar align in case it is not level, but an adlustment in AZ will have impact on Alt. Looks like that is what you are describing?

Rgrds,

Paul
8 months 1 week ago #69031
The topic has been locked.
Time to create page: 0.901 seconds