×

INDI Library v1.9.2 Released (14 Sep 2021)

Bimonthly Stable INDI Library release introduces new drivers and fixes for existing ones.

Meridian Flip - EKOS/Onstep Slews to last star

  • Posts: 249
  • Thank you received: 22
Just tried now with the latest PPA package on Ubuntu 18.04, and I can confirm that the mount status is not right.

kstars-bleeding 6:3.5.4+202107081130~ubuntu18.04.1
indi-bin 1.9.1~202107052238~ubuntu18.04.1

When I slew from KStars, after a second or two, I get the notification of "Mount arrived at target location", and in Ekos main screen the mount says it is "Tracking".

But in reality, the mount is slewing, and I can see the cross hairs moving over the sky.

In the meantime, my Python API reports the correct status.

I also see that the target name on the Ekos screen is wrong: although I reached Arcturus west of the meridian, Ekos says it is on Capella, east of the meridian. Another user says he saw this last problem in a thread on the OnStep group.
1 month 3 weeks ago #74894

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

  • Posts: 140
  • Thank you received: 18
I'll build this and see - be back in a bit
1 month 3 weeks ago #74895

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

  • Posts: 140
  • Thank you received: 18
Tried if (!strstr(OSStat, "n") && !strstr(OSStat, "N"))
No love....and I can confirm the mismatch in star as I was ON Rastaban...Ekos showing something else (Gremin?)
I think I may be going back to 3.5.3 or 3.5.2 here until it gets looked at by actual experts :-)
1 month 3 weeks ago #74896

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

  • Posts: 249
  • Thank you received: 22
Since this bug reared its head, Ekos is always one star behind.
If you slew to Capella, wait a bit, then slew Arcturus.
After the second slew, Ekos will still say it is on Capella.
1 month 3 weeks ago #74901

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

  • Posts: 857
  • Thank you received: 257
Could you please check in the INDI window of EKOS which coordinates are shown? Do they match the position Ekos shows? If yes, the problem is probably inside the OnStep INDI service and not inside Ekos.
TSA-120 + FSQ-85 + GSO 150/750 | Avalon Linear + M-zero | ASI 1600mm pro + 6200mm pro | KStars/INDI on Raspberry Pi 4/Intel NUC
1 month 3 weeks ago #74902

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

  • Posts: 249
  • Thank you received: 22
I slewed to Regulus (in Leo, near the Western horizon), then to Altair, which is just above the Eastern horizon.

Here is what Ekos thinks: still says Regulus, though the coordinates are correct.


These are the coordinates of Altair in my location now


And here is how Kstars look. Pointing is correct.
Last edit: 1 month 3 weeks ago by Khalid.
1 month 3 weeks ago #74904
Attachments:

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

  • Posts: 857
  • Thank you received: 257
Could you please check the INDI window?

I guess it matches the position that KStars is showing.
TSA-120 + FSQ-85 + GSO 150/750 | Avalon Linear + M-zero | ASI 1600mm pro + 6200mm pro | KStars/INDI on Raspberry Pi 4/Intel NUC
1 month 3 weeks ago #74905
Attachments:

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

  • Posts: 249
  • Thank you received: 22
The coordinates in INDI are correct (they show the second star, which is Altair in this case, not the first star, which Ekos thinks it is at 

1 month 3 weeks ago #74907
Attachments:

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

  • Posts: 857
  • Thank you received: 257
OK, good. Next step: slew to a new target and check the color of the light left to the label "Eq. Coordinates" during the slew. It should be yellow until the scope reaches the new position.
TSA-120 + FSQ-85 + GSO 150/750 | Avalon Linear + M-zero | ASI 1600mm pro + 6200mm pro | KStars/INDI on Raspberry Pi 4/Intel NUC
1 month 3 weeks ago #74908

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

  • Posts: 249
  • Thank you received: 22
What happens is consistent with the notification of "mount arrived at target location".

The "Eq. Coordinates" turn yellow for a second, then go green, although the slew has not actually finished yet.
1 month 3 weeks ago #74909

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

  • Posts: 857
  • Thank you received: 257
OK, we getting closer to where the problem sits: it looks like the OnStep driver does not report correctly when it slews. During a slew, the state needs to be IPS_BUSY (shown as yellow light). If the state is IPS_OK (shown as green), Ekos assumes that the mount is tracking.

If this is fixed in the OnStep driver, Ekos should recognize the target correctly.
TSA-120 + FSQ-85 + GSO 150/750 | Avalon Linear + M-zero | ASI 1600mm pro + 6200mm pro | KStars/INDI on Raspberry Pi 4/Intel NUC
1 month 3 weeks ago #74912

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

  • Posts: 140
  • Thank you received: 18
Think I found it

lower case p mean UNPARKED and the structures are all IF() clause with no IF else so after checking and setting slew status I am fairly sure this block WILL get executed - the mount IS unparked and since slewing has neither n or N you fall to the else which set TRACKING and UNPARKED - line 1904 anyone ant to confirm

if (strstr(OSStat, "p"))
{
SetParked(false); //defaults to TrackState=SCOPE_IDLE but we want
if (strstr(OSStat, "nN")) // azwing need to detect if unparked idle or tracking
{
IUSaveText(&OnstepStat[1], "Idle");
TrackState = SCOPE_IDLE;
}
else TrackState = SCOPE_TRACKING;
IUSaveText(&OnstepStat[3], "UnParked");
}
1 month 3 weeks ago #74914

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

Time to create page: 1.119 seconds