×

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

Bi-monthly release with minor bug fixes and improvements

Can't select guide cam as guider

These numbers are correct. Not sure why they wouldn't show up in the "Guider" list.
10 months 2 weeks ago #93402

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

  • Posts: 989
  • Thank you received: 161
Same here. The guide cam was recognized and I was able to shoot images using it. But it was not listed under "guider" in train setup. Weird. I almost hope the issue reoccurs so we can find out what was going wrong. For the time being, I'm glad to have my ST-4 port back.
10 months 2 weeks ago #93409

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

  • Posts: 989
  • Thank you received: 161
It happened again. Twice tonight. Have to quit now. Both cameras did show "Interface 2" in "General Info" field.
And there are more problems with the ASIs. The 294MC-Pro's gain setting was reset to 0 several times during the session without any reason as far as I can tell. I had to reset it to 120 by hand multiple times, save settings, but shortly thereafter it was reset to 0 again.
10 months 2 weeks ago #93486

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

  • Posts: 989
  • Thank you received: 161
Regarding gain being reset to zero I suspect what happens is this:

1. In my case the gain field in the CCD tab is being left blank ("-"), so the Indi-saved value of 120 is being used and displayed.
2. During a focus run gain is set to 0 as (it appears to me) the focus tab behaves differently (compared to the CCD tab) and doesn't care about Indi-saved settings. It overwrites the gain value and sets it to 0.
3. After the focus run when the CCD tab retakes control, the gain value remains what it is, which now is 0.

That could be the reason why I started out taking subs at gain=120 and later figured subs were taken at gain=0 (although I never actively configured it to be 0).

The fact that (as I believe) the focus TAB behaves differently compared to the CCD tab needs to be changed. As long as no specific gain value has been set by the user, it should be left untouched. The default value in focus TAB should be "-" rather than 0. Same as in the CCD tab.
Last edit: 10 months 1 week ago by Alfred.
10 months 1 week ago #93504

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

  • Posts: 989
  • Thank you received: 161
Is there anything that I can do to prevent both cameras from claiming the same Interface?
10 months 1 week ago #93549

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

I can't reproduce this behavior with simulators... so does this happen all the time or it's random?
10 months 1 week ago #93564

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

  • Posts: 989
  • Thank you received: 161
It's random. Sometimes both cams are allocated Interface no. 2. On other occasions the 294MC gets interface 6.

Where is the logic situated that decides which interface number goes to what camera?
10 months 1 week ago #93569

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

  • Posts: 603
  • Thank you received: 281
Hi Alfred,

Re- your comments on Gain and Focus... this is what should happen:

If you leave Gain on Focus unset ("--") then Focus will not change Gain during Autofocus and the camera will use whatever Gain was set when Autofocus was started.

If you have Gain set to any number in Focus, then Autofocus will set camera gain to that number at the start of Autofocus. So if you set 0, then this would set Gain to 0 at the start of Autofocus.

Whether Capture sets Gain after Focus depends on whether Gain is set in Capture or left unset ('--').

So if you have Gain set to 0 in Focus and unset in Capture, then what you describe is what I would expect to see.

Let me know if this isn't the behaviour you're seeing.
10 months 1 week ago #93573

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

  • Posts: 989
  • Thank you received: 161
John, thanks a lot for your reply! That's exactly how I would expect it to work.

I've no idea why it would be set to 0 here as I never use gain=0, especially when focusing. I tried to set gain to "-" by typing - but it was reverted to 0 when I hit enter. I now found out I should have typed "--" instead OR I should have used the arrow down which would have set it from 0 to "--" then. Thanks a lot for the explanation!
10 months 1 week ago #93575

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


This is definitely related to a recent change in INDI. By default, it was setting all cameras to have Guide interface support. But since is not the case, it was removed and a camera has to explicitly set Guide interface by inspecting the camera capabilities. I just added more logging to INDI ASI driver to indicate whether ST4 support was reported as true by the camera or not. You need to compile INDI ASI from GIT to get these logs though. In case you get Interface 2, then check the camera logs. If the camera reports ST4Port: True then it's an issue with INDI/Ekos. But if the camera reports it as False, then it's an issue with the camera or ASI SDK itself.
10 months 1 week ago #93583

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

  • Posts: 989
  • Thank you received: 161
Many thanks for your help, Jasem! I compiled indi from git, and kstars as well. I can see where you made changes like

LOGF_DEBUG("ST4Port: %s", mCameraInfo.ST4Port ? "True" : "False");

in asi_base.cpp. I started KStars with logging (Indi, Caputure, Guide, CCD) and then searched for "ST4" in the logfile but without result. Shouldn't it be mentioned there?
10 months 1 week ago #93585

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

Time to create page: 0.245 seconds