×

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

Bi-monthly release with minor bug fixes and improvements

Internal Guider - Correction pulses sent every other frame?

  • Posts: 985
  • Thank you received: 161
Hi, during the last couple of sessions I noticed guiding corrections were sent every other guide frame only. What I mean is this:

A frame is received from the guide cam. Drift Graphics as well as "Guiding Delta" and "Pulse Length" show the correspoinding values.

When the next frame is received though, nothing happens. Neither Drift Graphics nor Guiding Delta or Pulse Length are updated.

The third frame triggers correct action, the fourth doesn't, and so on...

I don't know whether this really means that no correction pulses are being sent to the mount, in particular when ST4 guiding is active. But it is my impression that indeed no correction pulses are sent because after dithering it takes way too long to get the guide star centered again. Normally I would have a 7 second wait between re-start of guiding and the next picture being taken. Recently though it took much longer for guiding to return to stable operation again.

Today I checked with Build: 2018-10-12T15:09:27Z and a fresh GIT pull (Build: 2018-10-16T12:47:25Z) but the issue remains (even when operating simulators).

A video is attached.
The following user(s) said Thank You: Jim
5 years 5 months ago #30462
Attachments:

    screenreco...0-16.mkv

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

  • Posts: 535
  • Thank you received: 109
This happened for me last night as well, on the latest bleeding build.
The following user(s) said Thank You: Alfred
5 years 5 months ago #30463

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

  • Posts: 985
  • Thank you received: 161
I'm afraid I can't see in the log files what's going wrong. Apparently everything is OK. I don't know whether any correction pulses are being received by the mount and why Drift Graph, Pulse Length etc. are not being updated on every guide frame received. Are there any log options that I should activate in order to get this kind of information into the log file?
5 years 5 months ago #30636
Attachments:

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

  • Posts: 985
  • Thank you received: 161
Has this been taken care of or is it going to be fixed, maybe before 3.0.0 is released? Due to bad weather I don't have a chance to check it out on my own.
5 years 4 months ago #31339

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

  • Posts: 985
  • Thank you received: 161
The issue remains with today's GIT. I am wondering why there is no feedback (other than xsnrg's confirmation, thanks!). Has it been put on the back burner?
Last edit: 5 years 4 months ago by Alfred.
5 years 4 months ago #31549

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

  • Posts: 1067
  • Thank you received: 140
There seems to be a lot of issue ATM so things are slow, Jasem has a todo list... :)
5 years 4 months ago #31555

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

  • Posts: 985
  • Thank you received: 161
Is this issue on the to-do list?
5 years 3 months ago #32785

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

By default, any correction pulses less than 100ms are not sent to the Mount/ST4. Have to check with Robert about the graph itself.
5 years 3 months ago #32909

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

  • Posts: 985
  • Thank you received: 161
It goes deeper than that. Correction pulses aren't even calculated and remain the same as in the guide frame before. It can be seen with simulators, so it is independent from my hardware.
5 years 3 months ago #32974

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

  • Posts: 985
  • Thank you received: 161
Today's git still discards every second guide frame. The guide module doesn't work correctly.
5 years 2 months ago #33186

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

Ok it's fixed, please check GIT now.
The following user(s) said Thank You: Alfred, Greg
5 years 2 months ago #33194

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

  • Posts: 985
  • Thank you received: 161
It now works as expected, thanks! What a pity this bug is in V3.0.
The following user(s) said Thank You: Greg
5 years 2 months ago #33196

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

Time to create page: 0.353 seconds