×

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

Bi-monthly release with minor bug fixes and improvements

Internal Guider not calibrating

  • Posts: 1957
  • Thank you received: 420

I can almost confirm that. First of all, I haven't had any issues with the EQMod/ASI120MC-S on a 280 mm guide scope combi. Secondly I have been getting 0.7" RMS and less on both my EQ5 and EQ6.
The following user(s) said Thank You: Helge
5 years 10 months ago #25883

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

  • Posts: 226
  • Thank you received: 88
Hi,
I looked at the log and considered a guide pulse (line 38858) 1000ms@0,5x):
- it starts at 22:20:50:556, and the actual track speed modification occurs at 22:20:50:656. There is a 47ms delay between the two first log messages, 0ms between all the others, but the last, with a 53ms delay which may be due to the real serial comm occuring here.
- the end of the pulse occurs at 22:20:51:715 (line 38897) after the end of a mount probe started at 22:20:51:372, The actual speed modification occurs at 22:20:51:832.
I have thought serial comm could be the problem but in the first part, a ':f1' serial command gets its response in the same millisecond, but the same command in the second part took 50ms. I believe the timestamps in log messages are added by the indi framework and thus we see when they have been processed, not when they have been queued. Furthermore the indi-eqmod driver uses the timer callback mechanism of the indi framework too, that explains why they may be delayed by the normal mount probe processing. I think we have to look at the eventloop of the indi framework as the timer callbacks are managed with select timeouts. Anyway a first idea would be to delay the ReadscopeStatus callback while pulse guiding.
Now none of this happens when you use ST4 guiding, you could do that with your ASI120MM and your AZ-EQ5.
Jean-Luc.
The following user(s) said Thank You: Jasem Mutlaq, Helge
5 years 10 months ago #25884

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

  • Posts: 281
  • Thank you received: 29
Many thanks for dealing with the problem - now I am wondering, and apologize my ignorance, what do you mean by ST4 guiding? The ASI120 ism connected to the AZ-EQ5 via a ST4 cable, or is there a specific setting required in EKOS or the guide module?
5 years 10 months ago #25886

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

  • Posts: 281
  • Thank you received: 29
Thanks also for advise on binning and exposure (up to 2 seconds). Do you also set gain to 50% and offset to zero? Any views on possibly different settings for the OAG or difference in focal length, like 500mm in my case? Just wanted to prepare as good as possible for the next occasion... ;)
5 years 10 months ago #25888

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

  • Posts: 226
  • Thank you received: 88
I think you did not select your ASI120MM as guiding interface, but EQMod Mount. If you use a ST4 cable between your ASI and the mount, guiding commands should be sent to the ASI camera, so select your camera as guiding interface in Ekos. I don't have it under the hand so can't precisely say how, but this is set in your Ekos profile before starting.
5 years 10 months ago #25890

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


Actually now that I think about it, the logs are from KStars. So IDMessage(...) is being sent to KStars and then it is logged, this is not done inside INDI directly, so the timestamps could be off, but the delays appear consistent nevertheless.
5 years 10 months ago #25897

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

  • Posts: 281
  • Thank you received: 29
Did some "extensive" testings yesterday, but did not succeed calibrating. Tried different settings for the minimum pulse lengths and backlash (backlash settings in the eqmod driver, but have to admit that I have no clou which values would makes sense). I tried also both available choices in the pop down menu for "via" (either picked ASI120 or EqMod), but results were the same. There was no selection of "ST4" or anything else available. I think I chose stars around the stars Pollux or Castor as calibration target.

Attached my log file. Would be great if problem can be resolved. If issue is on my side (e.g. mount), would be curious to know as well - if for instance "backlash" was an issue, I would not know what to do.

Thanks a lot as always for the terrific support! Helge
5 years 10 months ago #25914
Attachments:

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

  • Posts: 226
  • Thank you received: 88
Don't use backlash, I made that for a home made mount hardware, I will disable it. The calibration process takes care of that.
Select the ASI120 in the menu to use its ST4 port.
And try again using the default settings. That should work, I use the same setup ;-)
Anyway your last log file was almost empty.
5 years 10 months ago #25917

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

  • Posts: 281
  • Thank you received: 29
Oh no, it is empty, indeed - and no other file stored from last night. What a shame.

Anyway, thanks for the feedback, and good to know better not to touch the backlash - do you think that could have been disturbing the calibration?

Quick question: is the calibration process affected the brightness of the stars, should the autostretch function be enabled?
5 years 10 months ago #25918

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

  • Posts: 1309
  • Thank you received: 226
Knro wroteWhy should subframing be avoided?
5 years 10 months ago #26113

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

  • Posts: 238
  • Thank you received: 15

Replied by Tom on topic Internal Guider not calibrating

Now you can try my way of guiding. I am also having the same mount and ASI120MC for guiding.
1. under profile editor, guiding set to internal
2. Under Guide tab, choose via EQmod moun and bin to 2x2
3. under guide option page, follow my setting in attached photo if you wish to perform dithering.
4. Please remove ST4 cable!!!!!!!

Are you using USB to connect to the mount? I am doing that as well.

Good luck!





Last edit: 5 years 10 months ago by Tom.
5 years 10 months ago #26142
Attachments:

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

  • Posts: 281
  • Thank you received: 29
Great, thanks a lot! I never thought about not using the ST4 cable. I have connected the mount via Bluetooth to the Raspberry, as well as the ASI via USB to the Pi.

Best, Helge
5 years 10 months ago #26148

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

Time to create page: 0.576 seconds