×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Help understanding the log - what happened here?

  • Posts: 643
  • Thank you received: 62
Hi!

I'd need some help in understanding my logs. The situation is this: I have a rather complex schedule set up, with around 20 different jobs - mostly variable stars and in the end imaging a nebula. However, something happens just after midnight, and in the morninng when I wake up, the mount is positioned oddly. It looks as if it for some odd reason has "run into" the western safety limit, and when doing that, it's stuck. What I do not get is why it landed there - there is really no reason. If there was a GOTO sent close to the safety limit, is should have executed a meridian flip. But: the targets where it fails (variable IX Lyr) should not send the scope there at all. It is easily accessible in the eastern sky. But I've seen this happen before - the scope sent to the safety limit. So therefore, I turned on mount logging and debugging. But I cannot makse sense of the logs.

As I see it, something odd happens around line 18077 and on. There are "slew failed" and so on. As far as I can see, up to that point, most things work nicely (there was a glitch somewhat earlier that I corrected manually, before I turned the mount logging on - not sure if that is visible in the log). I have cut out the very long log after around 1 am, since it is jus repetition of errors - can post if needed.

One of my hunches is that the alignment for some reason sends the scope in odd directions. Either because some strange plate solviing issue, or because the mount (a G11) interprets the commands in some odd way. But... just a wild hunch.

Any help with this would be much appreciated. I feel totally lost in reading these detailed logs.

Also: is there a way to "replay" the detailed mount log? To send it to the mount and see what it does, so to speak?

Magnus
The following user(s) said Thank You: Jasem Mutlaq
3 years 10 months ago #53938
Attachments:

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

So the primary culprit here is why the mount failed to slew? At 2020-05-15T00:17:01.071, it gets synced but afterwards all subsequent slews fail.
3 years 10 months ago #53950

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

  • Posts: 643
  • Thank you received: 62
Exactly! My guess is that the failed slew is caused by the scope hitting the safety limit - then it is stuck there.

So my thinking is: why on earth was it sent there? IX Lyr should have been to the east, almost directly to the east, by midnight. To hit the safety limit (western side) the scope must have been sent from almost straight east to SSW or something like that. And why should that happen when aligning on an object to the east?

So: is there anything indicating that the mount is getting orders to move away from the east, close to IX Lyr?

Magnus
3 years 10 months ago #53952

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

  • Posts: 643
  • Thank you received: 62
Hi!

But wait. At this point in time, the scope IS really in a position where it probably hits the safety limit. Those coordinates ("Syncing to RA (13h 41m 45s) DEC ( 32° 15' 25\")") really are a bit west of the meridian. And very far from IX Lyr. The coordinates in the scheduler file for IX Lyr are:
<J2000RA>18.4823</J2000RA>
<J2000DE>32.2473</J2000DE>

So why is the alignment process now trying to send the scope to
"Slewing to target coordinates: RA (13h 38m 24s) DEC ( 32° 15' 29\")."
Just after that sync......? Have I set the job up wrongly, or what is going on here?

Attached is the scheduler file.

I guess this is another stupid user error.....

Magnus
3 years 10 months ago #53954
Attachments:

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

  • Posts: 643
  • Thank you received: 62
Hi again!

Here is a more detailed reading of the log file from me, giving some more details to my question.

It has worked with EQ Lyr, aligned nicely, line 14587:

[2020-05-15T00:03:38.031 CEST INFO ][ org.kde.kstars.ekos.align] - "Solution coordinates: RA (19h 19m 35s) DEC ( 41° 07' 21\") Telescope Coordinates: RA (19h 19m 41s) DEC ( 41° 08' 43\")"
[2020-05-15T00:03:38.034 CEST INFO ][ org.kde.kstars.ekos.align] - "Target is within 00° 01' 52\" degrees of solution coordinates."
[2020-05-15T00:03:38.043 CEST INFO ][ org.kde.kstars.ekos.align] - "Target is within acceptable range. Astrometric solver is successful."

Then finished, line 15730:

[2020-05-15T00:09:02.782 CEST INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'EQ Lyr' is stopping guiding..."
[2020-05-15T00:09:02.782 CEST INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'EQ Lyr' is complete."

Then going to IX Lyr
Line 15773
[2020-05-15T00:09:05.982 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - "Job 'IX Lyr' is selected for next observation with priority #10 and score 37."

Line 15788
[2020-05-15T00:09:07.131 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Get next action...
[2020-05-15T00:09:07.132 CEST DEBG ][ org.kde.kstars.ekos.mount] - Slewing to RA= "18h 29m 40s" DEC= " 32° 15' 38\""

This is the correct coordinates. And almost straight to the east at this point in time.

Line 15890
2020-05-15T00:09:21.261 CEST INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'IX Lyr' slew is complete."

Focusing complete
Line 16730
[2020-05-15T00:12:07.087 CEST INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'IX Lyr' focusing is complete."
[2020-05-15T00:12:07.095 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Get next action...
[2020-05-15T00:12:07.106 CEST INFO ][ org.kde.kstars.ekos.align] - "Capturing image..."
[2020-05-15T00:12:07.112 CEST INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'IX Lyr' is capturing and plate solving."


Alignment succeeded
Line 16811
[2020-05-15T00:12:24.148 CEST INFO ][ org.kde.kstars.ekos.align] - "Solver completed in 4 seconds."
[2020-05-15T00:12:24.152 CEST INFO ][ org.kde.kstars.ekos.align] - "Solver RA (277.27280) DEC (32.23952) Orientation (-91.25037) Pixel Scale (4.26018)"
[2020-05-15T00:12:24.174 CEST INFO ][ org.kde.kstars.ekos.align] - "Solution coordinates: RA (18h 29m 50s) DEC ( 32° 15' 10\") Telescope Coordinates: RA (18h 29m 40s) DEC ( 32° 15' 38\")"
[2020-05-15T00:12:24.177 CEST INFO ][ org.kde.kstars.ekos.align] - "Target is within 00° 02' 34\" degrees of solution coordinates."
[2020-05-15T00:12:24.188 CEST DEBG ][ org.kde.kstars.indi] - ISD:Telescope: Syncing...
[2020-05-15T00:12:24.191 CEST DEBG ][ org.kde.kstars.indi] - ISD:Telescope sending coords RA: "18h 29m 50s" ( 18.4973 ) DE: " 32° 15' 10\"" ( 32.253 )
[2020-05-15T00:12:24.192 CEST INFO ][ org.kde.kstars.ekos.align] - "Syncing to RA (18h 29m 50s) DEC ( 32° 15' 10\")"
[2020-05-15T00:12:24.195 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Align State "Syncing"
[2020-05-15T00:12:24.213 CEST DEBG ][ org.kde.kstars.ekos.mount] - Mount status changed from "Tracking" to "Slewing"
[2020-05-15T00:12:24.251 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 2
[2020-05-15T00:12:24.252 CEST INFO ][ org.kde.kstars.indi] - Atik 383L : "[INFO] CCD FOV rotation updated to -91.2504 degrees. "
[2020-05-15T00:12:24.254 CEST INFO ][ org.kde.kstars.indi] - Losmandy Gemini : "[INFO] Synchronization successful. "
[2020-05-15T00:12:24.255 CEST DEBG ][ org.kde.kstars.indi] - ISD:Telescope: TRACK
[2020-05-15T00:12:24.258 CEST DEBG ][ org.kde.kstars.indi] - ISD:Telescope sending coords RA: "18h 29m 40s" ( 18.4944 ) DE: " 32° 15' 38\"" ( 32.2606 )
[2020-05-15T00:12:24.258 CEST INFO ][ org.kde.kstars.ekos.align] - "Slewing to target coordinates: RA (18h 29m 40s) DEC ( 32° 15' 38\")."
[2020-05-15T00:12:24.280 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Align State "Slewing"

Then it slews. And then finished:
Line 17039
[2020-05-15T00:13:09.167 CEST INFO ][ org.kde.kstars.ekos.align] - "Slew complete. Target accuracy is not met, running solver again..."
[2020-05-15T00:13:09.184 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gm#> "
[2020-05-15T00:13:09.184 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <W>, lst 14.650595, ha 1.021429, pierSide 0 "
[2020-05-15T00:13:09.185 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Align State "In Progress"
[2020-05-15T00:13:09.215 CEST DEBG ][ org.kde.kstars.ekos.mount] - Mount status changed from "Slewing" to "Tracking"
[2020-05-15T00:13:09.269 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 3
[2020-05-15T00:13:10.166 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gm#> "
[2020-05-15T00:13:10.179 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <W>, lst 14.650876, ha 1.021431, pierSide 0 "
[2020-05-15T00:13:10.703 CEST INFO ][ org.kde.kstars.ekos.align] - "Capturing image..."
[2020-05-15T00:13:10.709 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Align State "In Progress"

If I read it right, it has now slewed to slightly west of the meridian (from negative HA to slightly positive). Now it is very far from the target it should slew to, and very close to the safety limit.

Do I read this correctly? If so, how can I understand this last disastrous slew?

Magnus
3 years 10 months ago #53955

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

  • Posts: 643
  • Thank you received: 62
Hi!

Anyone got any idea on this?

Magnus
3 years 10 months ago #54128

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

  • Posts: 1029
  • Thank you received: 301
This is weird yes. I wonder if that could be an issue with sync points. In order to rule this out, enable the Ekos solver option "use differential slewing instead of sync points". This will make alignment slower as the mount model will not evolve, but we'll perhaps determine whether the issue is with the use of sync points or with the mount commands themselves.

-Eric
3 years 10 months ago #54156

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

  • Posts: 643
  • Thank you received: 62
Hi!

Thanks, Eric, both for your suggestion and for acknowledging that it is weird :)

Just to be sure: I have a Losmandy G11. Ekos does not build a model on that, just syncs (if I got it right). Does that affect your advice?

Magnus
3 years 10 months ago #54158

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

  • Posts: 1029
  • Thank you received: 301
Ekos will give the sync points to the indi driver. Then the driver may or may not send them to the mount. In terms of mount model, Ekos only builds a list of points to send when booting the mount, but I'm not talking about this here. I was only referring to the fact that for each sync point sent, the mount becomes more efficient at pointing. My suggestion is to disable that feature to eliminate a parameter in the problem.

-Eric
3 years 10 months ago #54159

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

  • Posts: 643
  • Thank you received: 62
OK, got it. Testing now.

But: what it does now, is plate solve and then slews to what it thinks is the correct position. But it does not take a new image there to check. It did that before, so I could see visually that the object was centred. Is this the correct behavior now, or is there another setting I might have shifted or should change?

Magnus
3 years 10 months ago #54195

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

  • Posts: 643
  • Thank you received: 62
Hi!

I have another case here. Unfortunately, this one is with the "differential slew" disabled. I toggled that on and off, and was a bit worried by the fact that when checked, the solver did not take a final shot, validating the position. So I turned it off. And this happened.

This time, the mount did not fail to slew, it was not "caught" in the safety limit. But it went far away from the target (while I slept). We are trying to image the Cave Nebula here, Sh2-155. So here are some extracts from the log. My main question now, concerns that fact that it seems that the aligment process shifts the target position along the way. It starts out with the correct coordinates, but in the end, after a disastrous slew, suddenly has new coordinates. So my question: how can that happen?

I will continue to test with the "differential slew" checked, but post this anyway, as just another piece of the puzzle, perhaps. And I'm thinking, could this in any way be connected to the recent changes in the driver that Chris made, to solve the problem of pierside not following ASCOM standards? (which was extremely helpful for me)?

Here are some extracts from the log file, attached in its entirety:


We are starting the job:

Line 39462:
[2020-05-21T00:16:34.366 CEST INFO ][ org.kde.kstars.ekos.scheduler] - Executing Job "Sh2-155"
[2020-05-21T00:16:34.837 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:h?#> "
[2020-05-21T00:16:37.535 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Get next action...
[2020-05-21T00:16:37.536 CEST DEBG ][ org.kde.kstars.ekos.mount] - Slewing to RA= "22h 57m 52s" DEC= " 62° 44' 19\""
[2020-05-21T00:16:37.543 CEST DEBG ][ org.kde.kstars.indi] - ISD:Telescope sending coords RA: "22h 57m 52s" ( 22.9645 ) DE: " 62° 44' 19\"" ( 62.7386 )
[2020-05-21T00:16:37.549 CEST INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'Sh2-155' is slewing to target."
[2020-05-21T00:16:37.555 CEST DEBG ][ org.kde.kstars.ekos.mount] - Mount status changed from "Tracking" to "Slewing"
[2020-05-21T00:16:37.556 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <0> "
[2020-05-21T00:16:37.557 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gv#> "
[2020-05-21T00:16:37.557 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <T> "
[2020-05-21T00:16:37.558 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gm#> "
[2020-05-21T00:16:37.558 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <W>, lst 15.102883, ha -0.778506, pierSide 0 "
[2020-05-21T00:16:37.632 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 2


Now we have slewed to the target, and begin focusing and alignint. This is a bit messy – and I interrupted here, paused the scheduler to manage filter, but never interferred with the aligment (I think)

Line 39965
[2020-05-21T00:17:52.295 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gv#> "
[2020-05-21T00:17:52.296 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <T> "
[2020-05-21T00:17:52.299 CEST INFO ][ org.kde.kstars.indi] - Losmandy Gemini : "[INFO] Slew is complete. Tracking... "
[2020-05-21T00:17:52.307 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gm#> "
[2020-05-21T00:17:52.320 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <E>, lst 15.123713, ha -7.840454, pierSide 0 "
[2020-05-21T00:17:52.398 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 2
[2020-05-21T00:17:52.398 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Slewing stage...
[2020-05-21T00:17:52.401 CEST DEBG ][ org.kde.kstars.ekos.mount] - Mount status changed from "Slewing" to "Tracking"
[2020-05-21T00:17:52.402 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 3
[2020-05-21T00:17:52.402 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Slewing stage...
[2020-05-21T00:17:52.403 CEST INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'Sh2-155' slew is complete."


Focusing complete, aligning:
Line 41053
[2020-05-21T00:21:45.806 CEST INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'Sh2-155' focusing is complete."
[2020-05-21T00:21:45.813 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Get next action...
[2020-05-21T00:21:45.822 CEST INFO ][ org.kde.kstars.ekos.align] - "Capturing image..."
[2020-05-21T00:21:45.830 CEST INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'Sh2-155' is capturing and plate solving."
[2020-05-21T00:21:45.891 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Align State "In Progress"
[2020-05-21T00:21:45.896 CEST INFO ][ org.kde.kstars.indi] - Atik 383L : "[INFO] Taking a 20 seconds frame... "
[2020-05-21T00:21:46.266 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:h?#> "
[2020-05-21T00:21:46.267 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <0> "
[2020-05-21T00:21:46.267 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gv#> "
[2020-05-21T00:21:46.268 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <T> "
[2020-05-21T00:21:46.274 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gm#> "
[2020-05-21T00:21:46.274 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <E>, lst 15.188883, ha -7.775283, pierSide 0 "

Fails, and I manually interrups, shifting filter.

Aligning again. Note that here the target coordinates are correct.
Line 43260
[2020-05-21T00:31:10.597 CEST INFO ][ org.kde.kstars.ekos.align] - "Solution coordinates: RA (22h 58m 00s) DEC ( 62° 47' 09\") Telescope Coordinates: RA (22h 57m 50s) DEC ( 62° 44' 19\")"
[2020-05-21T00:31:10.601 CEST INFO ][ org.kde.kstars.ekos.align] - "Target is within 00° 03' 46\" degrees of solution coordinates."
[2020-05-21T00:31:10.649 CEST DEBG ][ org.kde.kstars.indi] - ISD:Telescope: Syncing...
[2020-05-21T00:31:10.653 CEST DEBG ][ org.kde.kstars.indi] - ISD:Telescope sending coords RA: "22h 58m 00s" ( 22.9669 ) DE: " 62° 47' 09\"" ( 62.7858 )
[2020-05-21T00:31:10.654 CEST INFO ][ org.kde.kstars.ekos.align] - "Syncing to RA (22h 58m 00s) DEC ( 62° 47' 09\")"
[2020-05-21T00:31:10.661 CEST INFO ][ org.kde.kstars.indi] - Atik 383L : "[INFO] CCD FOV rotation updated to -98.8856 degrees. "
[2020-05-21T00:31:10.662 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Align State "Syncing"
[2020-05-21T00:31:10.746 CEST INFO ][ org.kde.kstars.indi] - Losmandy Gemini : "[INFO] Synchronization successful. "
[2020-05-21T00:31:10.748 CEST DEBG ][ org.kde.kstars.indi] - ISD:Telescope: TRACK
[2020-05-21T00:31:10.753 CEST DEBG ][ org.kde.kstars.indi] - ISD:Telescope sending coords RA: "22h 57m 51s" ( 22.9642 ) DE: " 62° 44' 19\"" ( 62.7386 )
[2020-05-21T00:31:10.754 CEST INFO ][ org.kde.kstars.ekos.align] - "Slewing to target coordinates: RA (22h 57m 51s) DEC ( 62° 44' 19\")."
[2020-05-21T00:31:10.756 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Align State "Slewing"
[2020-05-21T00:31:10.843 CEST INFO ][ org.kde.kstars.indi] - Losmandy Gemini : "[INFO] Slewing to RA: 22:57:51 - DEC: 62:44:19 "
[2020-05-21T00:31:11.418 CEST DEBG ][ org.kde.kstars.ekos.mount] - Mount status changed from "Tracking" to "Slewing"
[2020-05-21T00:31:11.420 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 2
[2020-05-21T00:31:11.515 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:h?#> "
[2020-05-21T00:31:11.516 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <0> "
[2020-05-21T00:31:11.516 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gv#> "
[2020-05-21T00:31:11.518 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <S> "
[2020-05-21T00:31:11.518 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gv#> "
[2020-05-21T00:31:11.520 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <S> "
[2020-05-21T00:31:11.525 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gm#> "
[2020-05-21T00:31:11.556 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <E>, lst 15.346328, ha -7.620339, pierSide 0 "
[2020-05-21T00:31:12.527 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gv#> "
[2020-05-21T00:31:12.527 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <S> "
[2020-05-21T00:31:12.534 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gm#> "
[2020-05-21T00:31:12.534 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <E>, lst 15.346608, ha -7.591170, pierSide 0 "

Goes on to slew. And it slews far off. And I am not interrupting here.

Line 43680 – finished slewing. Now we are very far from the object, as seen by the hour angle. How does the solver handle this?

[2020-05-21T00:32:31.423 CEST DEBG ][ org.kde.kstars.ekos.mount] - Mount status changed from "Slewing" to "Tracking"
[2020-05-21T00:32:31.425 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 3
[2020-05-21T00:32:32.361 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gm#> "
[2020-05-21T00:32:32.371 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <W>, lst 15.368843, ha 1.131343, pierSide 0 "
[2020-05-21T00:32:32.888 CEST INFO ][ org.kde.kstars.ekos.align] - "Capturing image..."
[2020-05-21T00:32:32.896 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Align State "In Progress"
[2020-05-21T00:32:32.940 CEST INFO ][ org.kde.kstars.indi] - Atik 383L : "[INFO] Taking a 20 seconds frame... "
[2020-05-21T00:32:33.013 CEST DEBG ][ org.kde.kstars.indi] - processBLOB() mode 2
[2020-05-21T00:32:33.016 CEST INFO ][ org.kde.kstars.fits] - Reading FITS file buffer
[2020-05-21T00:32:33.368 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gm#> "
[2020-05-21T00:32:33.374 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <W>, lst 15.369124, ha 1.131346, pierSide 0 "
[2020-05-21T00:32:34.376 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gm#> "
[2020-05-21T00:32:34.387 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <W>, lst 15.369405, ha 1.131349, pierSide 0 "
[2020-05-21T00:32:35.420 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gm#> "
[2020-05-21T00:32:35.420 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <W>, lst 15.369685, ha 1.130519, pierSide 0 "
[2020-05-21T00:32:36.420 CEST DEBG ][ org.kde.kstars.ekos.mount] - Mount status changed from "Tracking" t


Now solver suddenly has changed target position!

Line 43903
[2020-05-21T00:33:28.766 CEST INFO ][ org.kde.kstars.ekos.align] - "Solver iteration #1"
[2020-05-21T00:33:28.784 CEST INFO ][ org.kde.kstars.ekos.align] - "Starting solver..."
[2020-05-21T00:33:28.789 CEST INFO ][ org.kde.kstars.ekos.align] - "/opt/astap/astap -r 30 -speed auto -f /tmp/fitsttNJlr.fits -o /tmp/solution"
[2020-05-21T00:33:28.912 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gm#> "
[2020-05-21T00:33:28.914 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <W>, lst 15.384595, ha 0.639873, pierSide 0 "
[2020-05-21T00:33:29.919 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] CMD: <:Gm#> "
[2020-05-21T00:33:29.921 CEST DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] RES: <W>, lst 15.384876, ha 0.640154, pierSide 0 "
[2020-05-21T00:33:30.150 CEST INFO ][ org.kde.kstars.ekos.align] - "Solver completed in 1 second."
[2020-05-21T00:33:30.153 CEST INFO ][ org.kde.kstars.ekos.align] - "Solver RA (221.24291) DEC (62.85979) Orientation (-98.34907) Pixel Scale (2.84378)"
[2020-05-21T00:33:30.187 CEST INFO ][ org.kde.kstars.ekos.align] - "Solution coordinates: RA (14h 45m 26s) DEC ( 62° 46' 41\") Telescope Coordinates: RA (14h 44m 41s) DEC ( 62° 44' 19\")"
[2020-05-21T00:33:30.191 CEST INFO ][ org.kde.kstars.ekos.align] - "Target is within 00° 11' 36\" degrees of solution coordinates."



Magnus
3 years 10 months ago #54283
Attachments:

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

Same here, I was wondering if they could be related to Chris recent changes... you can revert to the previous driver from GIT (need to recompile against an older commit). Will ask Chris also to check if this could be related.

EDIT: so it looks like Chris changes were related to Side of Pier. Do you have in the logging level of the driver SCOPE debug? this would make it more verbose and get the RA/DE reading which are missing from the log now.
Last edit: 3 years 10 months ago by Jasem Mutlaq.
3 years 10 months ago #54338

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

Time to create page: 0.639 seconds