An issue with the value of m_Camera->hasGuideHead()

[joseph.mcgee at sbcglobal.net]

Thank You Hy!

I think that solved my problem.

I actually had not established a separate train for the guider. My guide 
cam is on an OAG, and so I had only been using a single train; which had 
the imaging camera as "Camera", and the guide camera as "Guider".  So 
now I've created a separate train for the guiding, each train now only 
has the appropriate "Camera" selected (and nothing selected for "Guider").

I just tested it on my Desktop PC and looks like it is working. So I'll 
do the same for my Raspberry Pi.

I guess this is a behavior change from the older version I had on the Pi.

I'm very relieved!



On 4/28/23 17:13, Hy Murveit wrote:
> I'll take a wild guess and guess that the issue is with the optical 
> train.
> First you should make sure that
> - the guide tab is using the guiding train
> - the other tabs are using the primary train
> - the guide train shows your guide tab on it
> - the other tabs show your primary camera on it
> If all that looks good, I would toggle all the trains on all the tabs 
> (there was an old bug that was fixed that required that)
> Restart your system and make sure it all looks good again.
>
> Re your question about GUIDER_EXPOSURE: I'm not familiar with your 
> guide camera, but perhaps you can ask on the forum to see if others 
> are successfully using that camera.
>
> Good luck,
> Hy
>
>
> On Thu, Apr 27, 2023 at 9:14 PM joseph.mcgee at sbcglobal.net 
> <joseph.mcgee at sbcglobal.net> wrote:
>
>     Hi All,
>
>     I recently refreshed my Raspberry Pi4 to Ubuntu 22.04 and also
>     upgraded
>     KStars  to 3.6.4 Stable.  I'm hesitant to report the following
>     issue as
>     a bug because it's likely that I have a miss configuration, caused
>     by my
>     upgrade process.
>
>     Last night was the first test with the upgraded Pi.  But I ran into a
>     problem with guiding;  When I started an imaging capture the guiding
>     failed. I soon realized that guiding was using my imaging camera
>     instead
>     of my guide camera; so the imaging capture was conflicting with
>     guiding.
>
>     Today I was able to reproduce this issue on my desktop pc using
>     the same
>     cameras, (but running the telescope simulator instead of my mount).
>
>     I traced the problem of the guider selecting my imaging camera to
>     this
>     line of code:
>
>          guide.cpp:739    ISD::CameraChip *targetChip =
>     m_Camera->getChip(useGuideHead ? ISD::CameraChip::GUIDE_CCD :
>     ISD::CameraChip::PRIMARY_CCD);
>
>     this is combined with the fact that the guide camera I use (an
>     ASI-290mm
>     -Mini), is returning a false on the call to hasGuideHead(). (Just
>     to be
>     clear, my imaging camera does not even have a guide port.)
>
>     I looked a bit further into the code, and discovered that a property
>     named GUIDER_EXPOSURE would need to be included in guide camera
>     definition order for the HasGuideHead value to be true. This
>     property is
>     not being found by indicamera for my ASI-290mm - Mini.  This property
>     appears to be part of CustomProperties, but it's also in a list
>     (skipProperties), so I think that even if it were being set, it
>     would be
>     ignored.
>
>     So, I'm quite lost at this point; and would appreciate any help
>     from you
>     all.
>
>     Thanks
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kstars-devel/attachments/20230428/9ae788de/attachment.htm>