<div dir="ltr">Agreed that the "guider" label on the optical train can be confusing. The mouse over does explain it, but that's easy to overloop. <div>The whole optical trains thing is a change in behaviour, but the optical trains didn't change behaviour, as far as I can tell.</div><div><br></div><div><b>Your optical train still sounds wrong to me. You need to set your mount as the guider, assuming you're not using ST4 guiding.</b></div><div><b>Please read the mouse-over on the "guiding" label when editing optical trains. Jasem probably has a video on it.</b></div><div><b><br></b></div><div>I haven't watched it, but I just found this: <a href="https://www.youtube.com/watch?v=ltOFxH_fKnQ" target="_blank">https://www.youtube.com/watch?v=ltOFxH_fKnQ</a> video Jasem made on optical trains.</div><div><b><br></b></div><div>Hy </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Apr 28, 2023 at 5:57 PM <a href="mailto:joseph.mcgee@sbcglobal.net">joseph.mcgee@sbcglobal.net</a> <<a href="mailto:joseph.mcgee@sbcglobal.net">joseph.mcgee@sbcglobal.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>Thank You Hy! <br>
</p>
<p>I think that solved my problem.<br>
</p>
<p>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"). <br>
</p>
<p>I just tested it on my Desktop PC and looks like it is working.
So I'll do the same for my Raspberry Pi.<br>
</p>
<p>I guess this is a behavior change from the older version I had on
the Pi.</p>
<p>I'm very relieved!<br>
</p>
<p><br>
</p>
<p><br>
</p>
<div>On 4/28/23 17:13, Hy Murveit wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I'll take a wild guess and guess that the issue is
with the optical train.
<div>First you should make sure that </div>
<div>- the guide tab is using the guiding train </div>
<div>- the other tabs are using the primary train</div>
<div>- the guide train shows your guide tab on it </div>
<div>- the other tabs show your primary camera on it</div>
<div>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)</div>
<div>Restart your system and make sure it all looks good again.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Good luck,</div>
<div>Hy</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Apr 27, 2023 at
9:14 PM <a href="mailto:joseph.mcgee@sbcglobal.net" target="_blank">joseph.mcgee@sbcglobal.net</a>
<<a href="mailto:joseph.mcgee@sbcglobal.net" target="_blank">joseph.mcgee@sbcglobal.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi
All,<br>
<br>
I recently refreshed my Raspberry Pi4 to Ubuntu 22.04 and also
upgraded <br>
KStars to 3.6.4 Stable. I'm hesitant to report the following
issue as <br>
a bug because it's likely that I have a miss configuration,
caused by my <br>
upgrade process.<br>
<br>
Last night was the first test with the upgraded Pi. But I ran
into a <br>
problem with guiding; When I started an imaging capture the
guiding <br>
failed. I soon realized that guiding was using my imaging
camera instead <br>
of my guide camera; so the imaging capture was conflicting
with guiding.<br>
<br>
Today I was able to reproduce this issue on my desktop pc
using the same <br>
cameras, (but running the telescope simulator instead of my
mount).<br>
<br>
I traced the problem of the guider selecting my imaging camera
to this <br>
line of code:<br>
<br>
guide.cpp:739 ISD::CameraChip *targetChip = <br>
m_Camera->getChip(useGuideHead ? ISD::CameraChip::GUIDE_CCD
: <br>
ISD::CameraChip::PRIMARY_CCD);<br>
<br>
this is combined with the fact that the guide camera I use (an
ASI-290mm <br>
-Mini), is returning a false on the call to hasGuideHead().
(Just to be <br>
clear, my imaging camera does not even have a guide port.)<br>
<br>
I looked a bit further into the code, and discovered that a
property <br>
named GUIDER_EXPOSURE would need to be included in guide
camera <br>
definition order for the HasGuideHead value to be true. This
property is <br>
not being found by indicamera for my ASI-290mm - Mini. This
property <br>
appears to be part of CustomProperties, but it's also in a
list <br>
(skipProperties), so I think that even if it were being set,
it would be <br>
ignored.<br>
<br>
So, I'm quite lost at this point; and would appreciate any
help from you <br>
all.<br>
<br>
Thanks<br>
<br>
<br>
<br>
<br>
<br>
<br>
</blockquote>
</div>
</blockquote>
</div>
</blockquote></div>