×

INDI Library v1.9.7 Released (29 Jul 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

Re:New Polar Alignment Scheme and Features

  • 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
1 year 7 months 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
1 year 7 months ago #67820
The topic has been locked.
  • Posts: 233
  • Thank you received: 24
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.
1 year 6 months ago #68024
The topic has been locked.
  • Posts: 39
  • Thank you received: 3
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: 1 year 6 months ago by Alexander Weis.
1 year 6 months ago #69008
Attachments:
The topic has been locked.
  • Posts: 233
  • Thank you received: 24
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.
1 year 6 months ago #69009
The topic has been locked.
  • Posts: 878
  • Thank you received: 419
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
 
AP1100 & Orion Atlas Pro, WO/ZS105 w/Moonlight V2 focus, GSO RC10 w/RSF focus
ZWO ASI1600, Astronomik Filters, ST80, QHY 5L-IIm.
KStars/Ekos/Indi on NUC10 & RPi4 w/SSD -- Ubuntu
Projects: Greedy Scheduler, Terrain, Polar Align, Analyze, Linear Focuser, SEP MultiStar & GPG Guide, FITS autostretch.
1 year 6 months ago #69024
The topic has been locked.
  • Posts: 39
  • Thank you received: 3
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
1 year 6 months ago #69030
The topic has been locked.
  • Posts: 212
  • Thank you received: 26
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
1 year 6 months ago #69031
The topic has been locked.
  • Posts: 39
  • Thank you received: 3

Paul,
I use the bubble level of the mount and align the bar with the double clamp with an electronic level. Might not be perfect but I assume it is not too far off.

Potentially anything to do with the fact that the clamp of the scope itself is turned by 90 degrees for fixing the bar? Do I need to enter this in some configuration setting?

Alex

Gesendet von meinem BKL-L09 mit Tapatalk
Standard setup: EQ6R, Williams Megrez 72- ASI 533MC -ZWO EAF, 50 mm viewfinder - ASI 120MM
1 year 6 months ago #69033
The topic has been locked.
  • Posts: 19
  • Thank you received: 0
I was using this feature last night in the northern hemisphere and doing a polar alignment away from the pole. I found the correction vectors recommended wherein the wrong direction. Also adjusting say Altitude the star never travelled along the yellow line or anywhere near it. So what I ended up doing was looking at the length of each vector and then moving the star that length for the corresponding direction.
I am using a Celestron AVX mount connected via HC and a 6 " RC scope with an AA26C camera. KSTARS is 3.5.2 stable build.
Is there something I need to check or configure to correct this performance?

Thanks
Lenny
1 year 5 months ago #69572
The topic has been locked.
Do you have any logs? Hy is working on this issue and he suspects its due to image parity as reported by the solver. The log would confirm this.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
1 year 5 months ago #69576
The topic has been locked.
  • Posts: 39
  • Thank you received: 3
As the problem that I experience is somewhat similar to what LKIERSEY  describes (when turning the knobs on my EQ6R the movement of the stars is not alligned to the vectors displayed): what log should be activated to be able to record helpful input here? The weather might allow me to have a session in the next days so I might be able to get some data that might be valuabe to help to narrow it down.

Alex
Standard setup: EQ6R, Williams Megrez 72- ASI 533MC -ZWO EAF, 50 mm viewfinder - ASI 120MM
1 year 5 months ago #69578
The topic has been locked.
Time to create page: 1.184 seconds