×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Re:Re:EKOS parking close to NCP

  • Posts: 319
  • Thank you received: 25
Hello,

Today I found my mount pared close to the NCP, but bot as usual at AZ 0, and DEC +90

The plate-solving confirmed that position. Any idea what is wrong?

PS: When I cleared mount configuration and restarted KSTARS it started from the NCP (but again, the actual position is shifted confirmed by plate solving)

3 years 3 months ago #64222
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 1029
  • Thank you received: 301

Replied by Eric on topic Re:EKOS parking close to NCP

When this happens to me, I know something bumped into the tripod. The other solution is that your parking position is customised in the INDI configuration. You mentioned clearing this, so not likely.

There is another recent thread in the forum about eq6-r failing the meridian flip, with the same symptoms as you maybe, I think this may be helpful to you (sorry no usable link in my phone app).
Last edit: 3 years 3 months ago by Eric.
3 years 3 months ago #64270

Please Log in or Create an account to join the conversation.

  • Posts: 910
  • Thank you received: 86
This always happens to me too.
I was concerned a while ago and reported.
But now, I think, it's not a big deal. It's still parked in the right place. (Unless something major really happened).

You start at Park. Do your star alignments - things get corrected, sometimes by a lot.
When you go back to Park - the mount is parked but the coordinates are shown with the corrections/alignments applied.
But the mount is correctly parked.
-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 2.
Last edit: 3 years 3 months ago by maxthebuilder.
3 years 3 months ago #64273

Please Log in or Create an account to join the conversation.

  • Posts: 28
  • Thank you received: 1
I too have experienced this with my HEQ5 Pro. My solution was to park it using the handset first then set the park position in EKOS to the current mount position.
Last edit: 3 years 3 months ago by Martin Rumsam.
3 years 3 months ago #64274

Please Log in or Create an account to join the conversation.

  • Posts: 1067
  • Thank you received: 140
Yes, this is normal as the mount parks at Polaris, which is not the NCP hence why the position changes, as Polaris rotates around the NCP.
3 years 3 months ago #64281

Please Log in or Create an account to join the conversation.

  • Posts: 319
  • Thank you received: 25
Obviously it’s not me in my lonely island, it is something common to happen. What I did yesterday is that I left my gear outside for the day and before I start, I just manually fixed the Dec and RA to zero, and when I started ekos it picked from NCP, and the night went fine.


Thank you
Mohamed
3 years 3 months ago #64283

Please Log in or Create an account to join the conversation.

  • Posts: 319
  • Thank you received: 25

I may be new to this, but I’ve never seen the mount parks or even start from Polaris, it is always NCP. Maybe this is because I’m not using the HC anymore and the mount under ekos total control.


Thank you
Mohamed
3 years 3 months ago #64284

Please Log in or Create an account to join the conversation.

  • Posts: 1029
  • Thank you received: 301
Note that if you plate-solve at NCP, you may introduce a sync point which, depending on the mount, has a huuuge rounding error. So, never plate-solve near NCP for any other purpose than polar alignment.

-Eric
The following user(s) said Thank You: Mohamed
3 years 3 months ago #64288

Please Log in or Create an account to join the conversation.

  • Posts: 319
  • Thank you received: 25

Thanks Eric for the tip. I didn't know that... And maybe this is what happened!!! The 1st target I think was C1 which is very close to Polaris...
3 years 3 months ago #64293

Please Log in or Create an account to join the conversation.

Time to create page: 0.539 seconds