https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #4 from James Lancaster <deathstal...@gmail.com> ---
The settle timer operates from when it thinks the end of a slew is and is up to
15 seconds long, whereas slews (especially meridian flips) might be minutes. 

I went back to the version in git, rebuilt kstars. Also commented out the one
reference to EqNP.s being set to anything other than IPS_ALERT in lx200_OnStep
(in the Sync, which is a modified copy from lx200telescope file, which sets
that) 

So I reproduced it running wireshark to make sure there's no odd settings being
made in INDI and sent to Kstars, and there don't appear to be. I have saved the
wireshark log and attached what seem to be relevant packets below.
(EQUATORIAL_EOD_COORD or EQUATORIAL_COORD are being looked for by Kstars,
EQUATORIAL_COORD does not appear (not unexpectedly) at all) 

Timeline/Description

Start with slew in progress: EQUATORIAL_EOD_COORD" state="Busy" at 19:03
(Packet 1) (Note: As OnStep sometimes has an issue with not finishing, the
behavior here is running into it's internal: Is it done timer? which is why no
more RA/DEC changes)

Slew from prior sync is finished at :19:07, EQUATORIAL_EOD_COORD" state="Ok"
(Packet 2)

Ekos Starts captue and solving is done at :19:26 and sends sync and CCD
rotation values (At this point m_wasSlewStarted should be false with the Mount
was synced message) (Packet 3)

INDI sends back changes, and log inforation and still shows
EQUATORIAL_EOD_COORD" state="Ok" (Packet 4)

Ekos sends new coordinates (Packet 5) to slew to

INDI sends back current coordnates with no change in status
(EQUATORIAL_EOD_COORD" state="Ok") (Packet 6) 

INDI sends back new target coordinates and state change EQUATORIAL_EOD_COORD"
state="Busy" in (Packet 7) Acknowledging Packet 5, and beginning move. At this
point m_wasSlewStarted should be changed to true. But as per getting the: "Slew
complete. Solving Alignment Point. . ." message at :19:26 it seems to be true.
Otherwise it should break. This also starts the Settling timer. 

Slew is continuning (Packet 8, 9) in :19:26 (Not included next packet is in
:19:27) 


My guess is that something about getting packet 6 with an OK, means there's a
breakdown, in some logic that I'm not seeing, and somehow m_wasSlewStarted is
true when it shouldn't be, or the break isn't breaking to the right point? 
--------------------

Second test I modified it as such: 
 case ALIGN_SLEWING:
                            appendLogText(i18n("ALIGN_SLEWING (%1)",
m_wasSlewStarted));
                        // If mount has not started slewing yet, then skip
                        if (m_wasSlewStarted == false) {
                                appendLogText(i18n("m_wasSlewStarted false!"));
                            break;
                        }
                        appendLogText(i18n("m_wasSlewStarted true!"));
                        m_wasSlewStarted = false;



2019-08-04T10:35:00 Settling...
2019-08-04T10:35:00 Slew complete. Solving Alignment Point. . .
2019-08-04T10:35:00 m_wasSlewStarted true!
2019-08-04T10:35:00 ALIGN_SLEWING (1)
2019-08-04T10:35:00 Slewing to target coordinates: RA (03h 11m 55s) DEC ( 23°
51' 01").
2019-08-04T10:35:00 Mount is synced to solution coordinates. Astrometric solver
is successful.
2019-08-04T10:35:00 Syncing to RA (02h 58m 48s) DEC ( 28° 53' 51")
2019-08-04T10:35:00 Solution coordinates: RA (02h 58m 48s) DEC ( 28° 53' 51")
Telescope Coordinates: RA (02h 58m 49s) DEC ( 28° 54' 04")
2019-08-04T10:35:00 WCS information updated. Images captured from this point
forward shall have valid WCS.


Hope that's helpful. Because Argh. 


===================================================

1st test
===================================================
Ekos window messages (Oldest on bottom)

2019-08-04T09:19:26 Settling...
2019-08-04T09:19:26 Slew complete. Solving Alignment Point. . .
2019-08-04T09:19:26 Slewing to target coordinates: RA (23h 54m 33s) DEC ( 52°
02' 30").
2019-08-04T09:19:26 Mount is synced to solution coordinates. Astrometric solver
is successful.
2019-08-04T09:19:26 Syncing to RA (00h 15m 39s) DEC ( 38° 40' 48")
2019-08-04T09:19:26 Solution coordinates: RA (00h 15m 39s) DEC ( 38° 40' 48")
Telescope Coordinates: RA (00h 15m 39s) DEC ( 38° 41' 05")
2019-08-04T09:19:26 Solver completed in 5 seconds.
2019-08-04T09:19:20 Starting solver...
2019-08-04T09:19:20 Image received.
2019-08-04T09:19:12 Capturing image...
2019-08-04T09:19:07 Settling...
2019-08-04T09:19:07 Slew complete. Solving Alignment Point. . .
2019-08-04T09:18:33 Slewing to target coordinates: RA (00h 15m 38s) DEC ( 38°
41' 04").




Any Wireshark packets on loopback with EQUATORIAL_EOD_COORD mentioned (Oldest
first, --- indicates INDI > KStars/Ekos, ==TO indicates Kstars/Ekos > INDI,
plus a number)
-----1
<setNumberVector device="LX200 OnStep" name="EQUATORIAL_EOD_COORD" state="Busy"
timeout="60" timestamp="2019-08-04T14:19:03">
    <oneNumber name="RA">
0.26083333333333336146
    </oneNumber>
    <oneNumber name="DEC">
38.684722222222220012
    </oneNumber>
</setNumberVector>


-----2
<setSwitchVector device="LX200 OnStep" name="TELESCOPE_TRACK_STATE"
state="Busy" timeout="0" timestamp="2019-08-04T14:19:07">
    <oneSwitch name="TRACK_ON">
On
    </oneSwitch>
    <oneSwitch name="TRACK_OFF">
Off
    </oneSwitch>
</setSwitchVector>
<setNumberVector device="LX200 OnStep" name="EQUATORIAL_EOD_COORD" state="Ok"
timeout="60" timestamp="2019-08-04T14:19:07">
    <oneNumber name="RA">
0.26083333333333336146
    </oneNumber>
    <oneNumber name="DEC">
38.684722222222220012
    </oneNumber>
</setNumberVector>

====TO3
device='CCD Simulator'
  name='CCD_ROTATION'
>  <oneNumber
    name='CCD_ROTATION_VALUE'>
      89.9867
  </oneNumber>
</newNumberVector>
<newSwitchVector
  device='LX200 OnStep'
  name='ON_COORD_SET'>
  <oneSwitch
    name='SYNC'>
      On
  </oneSwitch>
</newSwitchVector>
<newNumberVector
  device='LX200 OnStep'
  name='EQUATORIAL_EOD_COORD'
>  <oneNumber
    name='RA'>
      0.260904
  </oneNumber>
  <oneNumber
    name='DEC'>
      38.6803
  </oneNumber>
</newNumberVector>

-----4
<setNumberVector device="CCD Simulator" name="CCD_ROTATION" state="Ok"
timeout="60" timestamp="2019-08-04T14:19:26">
    <oneNumber name="CCD_ROTATION_VALUE">
89.986699999999999022
    </oneNumber>
</setNumberVector>
<message device="CCD Simulator" timestamp="2019-08-04T14:19:26" message="[INFO]
CCD FOV rotation updated to 89.9867 degrees."/>
<message device="LX200 OnStep" timestamp="2019-08-04T14:19:26" message="[SCOPE]
&lt;setObjectRA&gt;"/>
<message device="LX200 OnStep" timestamp="2019-08-04T14:19:26" message="[SCOPE]
CMD &lt;:Sr 00:15:39#&gt;"/>
<message device="LX200 OnStep" timestamp="2019-08-04T14:19:26" message="[SCOPE]
CMD &lt;:Sr 00:15:39#&gt; successful."/>
<message device="LX200 OnStep" timestamp="2019-08-04T14:19:26" message="[SCOPE]
&lt;setObjectDEC&gt;"/>
<message device="LX200 OnStep" timestamp="2019-08-04T14:19:26" message="[SCOPE]
CMD &lt;:Sd +38:40:49#&gt;"/>
<message device="LX200 OnStep" timestamp="2019-08-04T14:19:26" message="[SCOPE]
CMD &lt;:Sd +38:40:49#&gt; successful."/>
<message device="LX200 OnStep" timestamp="2019-08-04T14:19:26" message="[DEBUG]
CMD &lt;:CM#&gt;"/>
<message device="LX200 OnStep" timestamp="2019-08-04T14:19:26" message="[SCOPE]
CMD &lt;:CM#&gt;"/>
<message device="LX200 OnStep" timestamp="2019-08-04T14:19:26" message="[SCOPE]
RES &lt;N/A&gt;"/>
<message device="LX200 OnStep" timestamp="2019-08-04T14:19:26" message="[DEBUG]
RES &lt;N/A&gt;"/>
<message device="LX200 OnStep" timestamp="2019-08-04T14:19:26" message="[INFO]
OnStep: Synchronization successful."/>
<setNumberVector device="LX200 OnStep" name="EQUATORIAL_EOD_COORD" state="Ok"
timeout="60" timestamp="2019-08-04T14:19:26">
    <oneNumber name="RA">
0.26090400000000002478
    </oneNumber>
    <oneNumber name="DEC">
38.680300000000002569
    </oneNumber>
</setNumberVector>
<setNumberVector device="LX200 OnStep" name="EQUATORIAL_EOD_COORD" state="Ok"
timeout="60" timestamp="2019-08-04T14:19:26">
    <oneNumber name="RA">
0.26090400000000002478
    </oneNumber>
    <oneNumber name="DEC">
38.680300000000002569
    </oneNumber>
</setNumberVector>
<message device="LX200 OnStep" timestamp="2019-08-04T14:19:26" message="[SCOPE]
CMD &lt;:GR#&gt;"/>


======TO5

device='LX200 OnStep'
  name='ON_COORD_SET'>
  <oneSwitch
    name='TRACK'>
      On
  </oneSwitch>
</newSwitchVector>
<newNumberVector
  device='LX200 OnStep'
  name='EQUATORIAL_EOD_COORD'
>  <oneNumber
    name='RA'>
      23.9092
  </oneNumber>
  <oneNumber
    name='DEC'>
      52.0419
  </oneNumber>
</newNumberVector>
-----6
<setNumberVector device="LX200 OnStep" name="EQUATORIAL_EOD_COORD" state="Ok"
timeout="60" timestamp="2019-08-04T14:19:26">
    <oneNumber name="RA">
0.26083333333333336146
    </oneNumber>
    <oneNumber name="DEC">
38.680277777777774872
    </oneNumber>
</setNumberVector>
-----7
<setNumberVector device="LX200 OnStep" name="TARGET_EOD_COORD" state="Idle"
timeout="60" timestamp="2019-08-04T14:19:26">
    <oneNumber name="RA">
23.909199999999998454
    </oneNumber>
    <oneNumber name="DEC">
52.041899999999998272
    </oneNumber>
</setNumberVector>
<setNumberVector device="LX200 OnStep" name="EQUATORIAL_EOD_COORD" state="Busy"
timeout="60" timestamp="2019-08-04T14:19:26">
    <oneNumber name="RA">
0.26083333333333336146
    </oneNumber>
    <oneNumber name="DEC">
38.680277777777774872
    </oneNumber>
</setNumberVector>

-----8
<setNumberVector device="LX200 OnStep" name="EQUATORIAL_EOD_COORD" state="Busy"
timeout="60" timestamp="2019-08-04T14:19:26">
    <oneNumber name="RA">
0.26055555555555554026
    </oneNumber>
    <oneNumber name="DEC">
38.686388888888885162
    </oneNumber>
</setNumberVector>
-----9
<setNumberVector device="LX200 OnStep" name="EQUATORIAL_EOD_COORD" state="Busy"
timeout="60" timestamp="2019-08-04T14:19:26">
    <oneNumber name="RA">
0.25861111111111112493
    </oneNumber>
    <oneNumber name="DEC">
38.714166666666670835
    </oneNumber>
</setNumberVector>

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to