×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

30 sec delay on align module

  • Posts: 1187
  • Thank you received: 370
Could you please upload the entire log file? I'll take a look...
The following user(s) said Thank You: Rafa Barberá
4 years 3 months ago #47297

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

  • Posts: 219
  • Thank you received: 41
I was editing the message because I've seen that I've forgotten it :)
4 years 3 months ago #47298

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

  • Posts: 1187
  • Thank you received: 370
Did you intentionally align with the ASI-120mm-s? Capturing the image during the alignment worked fine but it might be that it interferes with guiding.

- Wolfgang
4 years 3 months ago #47300

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

  • Posts: 219
  • Thank you received: 41
Yes i was trying to use the ASI120MM-S to align/guide and the main telescope with DSLR to imaging. But please, ignore all the guiding calibration. Latter, around time stamp 2019-12-27T19:29:36.148, you can see that all the alignments have a 30sec pause. Ar this time, no camera was trying to capture any image, other that the ASI120MM-S in the align module
4 years 3 months ago #47302

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

  • Posts: 1187
  • Thank you received: 370
OK, now I can see it. One thing that looks unusual: it looks like the EQMOD driver logs excessively. Could you please check which value is set as the polling period of your mount? I would recommend to set it to a value of 500ms or more.

If this does not help, I would at least try to set logging level to INFO. Maybe the explanation is simply excessive logging that leads to some blocking.

- Wolfgang
The following user(s) said Thank You: Rafa Barberá
4 years 3 months ago #47304

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

  • Posts: 219
  • Thank you received: 41
I’ll review the pooling interval, but I’m pretty sure that the login has no relation with the problem, because it was disabled when the problem started. I’ve started the logs just to be able to show the behavior. For me is very suspicious the message

WARN ][                       default] - QProcess: Destroyed while process ("/usr/local/bin/pip3") is still running.
.
4 years 3 months ago #47305

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

  • Posts: 1187
  • Thank you received: 370
Hm, maybe that blocks the INDI client of EKOS. No clue where this comes from.
4 years 3 months ago #47306

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

  • Posts: 219
  • Thank you received: 41


Looking for info about this error, I’ve found this entry on stackoverflow

stackoverflow.com/questions/14504201/ddg#14505682

So my “30 sec freeze” seems related with a sync problem between Ekos and astrometry.net
4 years 3 months ago #47307

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

  • Posts: 333
  • Thank you received: 92

Replied by han on topic Re:30 sec delay on align module

The 1000 pixels is not an hard boundary. The reliability for poor image reduces below 1000 pixels but it should still work. Setting the tolerance form 0.005 will 0.007 will help.

Han
The following user(s) said Thank You: Rafa Barberá
4 years 3 months ago #47323

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

  • Posts: 219
  • Thank you received: 41

Good to know! I’ll give it another try
4 years 3 months ago #47324

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

  • Posts: 219
  • Thank you received: 41
Hi Han,

This night I was able to use ASTAP to solve my images. I need to tweak continuously the exposure, because your algorithm is very sensitive (too much?) to image quality.

Anyway thanks to ASTAP I was able to polar align my AZ GTi mount to 31” from pole!! And refine el each goto landing place. Thanks!

But the problem with Astrometry.net remains, I can’t use it right now

4 years 3 months ago #47341

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

  • Posts: 333
  • Thank you received: 92
Hello rbarberac,

Exposure time should not be critical. Either 1 or 300 seconds should work. Could you share a few images made with the guider, so I can have a look?

Han
The following user(s) said Thank You: Rafa Barberá
4 years 3 months ago #47342

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

Time to create page: 0.677 seconds