×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Read More...

Wrong mount position (?) - Solver failed

  • Posts: 403
  • Thank you received: 41

Wrong mount position (?) - Solver failed was created by Euripides

Hello guys,

3 nights ago I tried to capture a low on horizon target and I saw that the Solver couldn't solve the image. After switching to online astrometry I was able to solve it. I didn't pay much attention back then.

Yesterday, I opened my observatory and I was quite happy to start a new session. As I was observing through my surveillance camera I saw that my scope was going upside down!
Tried to plate solve multiple times, but all failed. I was able to see the ERR on the align module on extreme numbers.

Tried purge settings, location change, etc. but I wasn't able to resolve it. Even tried to plate-solve Polaris and the counterweight went upside down!

Cause now I do have an observatory, I hadn't made any changes (moving mount, etc).

Could you please take a look at the log? I am pretty sure that I am missing something.


File Attachment:

File Name: log_22-13-39.txt
File Size:2,264 KB
10 months 4 days ago #93686
Attachments:

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

Replied by Jasem Mutlaq on topic Wrong mount position (?) - Solver failed 

[2023-06-26T22:34:46.656 EEST DEBG ][     org.kde.kstars.ekos.mount] - Setting target RA= "03h 00m 04s" DEC= " 89° 21' 30\""
[2023-06-26T22:34:46.656 EEST DEBG ][     org.kde.kstars.ekos.mount] - flipDelayHrs set to zero in slew, m_MFStatus= "MOUNT_FLIP_NONE"
[2023-06-26T22:34:46.656 EEST DEBG ][     org.kde.kstars.ekos.mount] - Slewing to RA= "03h 00m 04s" DEC= " 89° 21' 30\""
[2023-06-26T22:34:46.656 EEST DEBG ][     org.kde.kstars.ekos.mount] - Initial HA  -11.5795 , flipDelayHrs  0 MFStatus  "MOUNT_FLIP_NONE"
[2023-06-26T22:34:46.658 EEST INFO ][     org.kde.kstars.ekos.align] - Target coordinates updated to JNow RA: "03h 00m 04s" DE: " 89° 21' 30\""
[2023-06-26T22:34:46.660 EEST DEBG ][           org.kde.kstars.indi] - ISD:Telescope sending coords RA: "03h 00m 04s" ( 3.00111 ) DE: " 89° 21' 30\"" ( 89.3583 )

This sets target coordinates to RA 3 and DE 89
[2023-06-26T22:39:15.147 EEST INFO ][     org.kde.kstars.ekos.align] - "Solution coordinates: RA (10h 33m 01s) DEC ( 83° 51' 24\") Telescope Coordinates: RA (21h 29m 44s) DEC ( 90° 00' 00\") Target Coordinates: RA (03h 00m 04s) DEC ( 89° 21' 30\")"
[2023-06-26T22:39:15.148 EEST INFO ][     org.kde.kstars.ekos.align] - "Target is within  113° 22' 12\" degrees of solution coordinates."
[2023-06-26T22:39:15.149 EEST DEBG ][     org.kde.kstars.ekos.align] - Align state changed to "Successful"
[2023-06-26T22:39:15.149 EEST DEBG ][   org.kde.kstars.ekos.capture] - Align State changed from "In Progress" to "Successful"
[2023-06-26T22:39:15.153 EEST DEBG ][     org.kde.kstars.ekos.align] - Align state changed to "Syncing"
[2023-06-26T22:39:15.153 EEST DEBG ][           org.kde.kstars.indi] - ISD:Telescope: Syncing...
[2023-06-26T22:39:15.154 EEST DEBG ][           org.kde.kstars.indi] - ISD:Telescope sending coords RA: "10h 33m 01s" ( 10.5502 ) DE: " 83° 51' 24\"" ( 83.8568 )

It's not a good idea to platesolve near poles unless you're running PAA. The target above is very different from solution, by 113 degrees! was the mount aligned at all? The normal workflow is this:
1. Unpark
2. Go to near by star (20-30 degrees away from poles)
3. Plate-solve
Last edit: 10 months 4 days ago by Jasem Mutlaq.
10 months 4 days ago #93687

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

  • Posts: 403
  • Thank you received: 41

Replied by Euripides on topic Wrong mount position (?) - Solver failed

Yes, it is supposed to be aligned. At least till 4 days ago when I had my last session it was perfectly PAA.

I've tried to plate solve to Polaris just to check the behavior.

My home - park position is Polaris.

For example, tried to Go To NGC7000, mount slews there (I can see that goes correctly), and starts to plate solve. The error is humongous and when finds the solution, it starts to slew upside down.


So I can't understand what broke down and the Stellarsolver return those numbers.
Last edit: 10 months 4 days ago by Euripides.
10 months 4 days ago #93688

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

  • Posts: 403
  • Thank you received: 41

Replied by Euripides on topic Wrong mount position (?) - Solver failed

It seems that changing the profile from SmallScaleSolving to Default resolved the issue - at least it plate solves again.


2023-06-28T23:12:20 Current PA is 2.1621; Target PA is 2.13966; diff: 0.0224364
2023-06-28T23:12:20 Target is within acceptable range.
2023-06-28T23:12:20 Target is within  00° 00' 04" degrees of solution coordinates.
2023-06-28T23:12:20 Solution coordinates: RA (20h 08m 47s) DEC ( 35° 51' 21") Telescope Coordinates: RA (20h 08m 46s) DEC ( 35° 51' 21") Target Coordinates: RA (20h 08m 46s) DEC ( 35° 51' 21")
2023-06-28T23:12:20 Effective telescope focal length is updated to 401.332 mm.
2023-06-28T23:12:20 Solver RA (301.96922) DEC (35.78992) Orientation (-177.83790) Pixel Scale (1.93246) Parity (neg)
2023-06-28T23:12:20 Solver completed after 0.46 seconds.
2023-06-28T23:12:20 Image received.
2023-06-28T23:12:16 Capturing image...
2023-06-28T23:12:14 Slew complete. Target accuracy is not met, running solver again...
2023-06-28T23:12:13 Slewing to target coordinates: RA (20h 08m 46s) DEC ( 35° 51' 21").
2023-06-28T23:12:12 Syncing to RA (20h 08m 44s) DEC ( 35° 51' 24")
2023-06-28T23:12:12 Target is within  00° 00' 36" degrees of solution coordinates.
2023-06-28T23:12:12 Solution coordinates: RA (20h 08m 44s) DEC ( 35° 51' 24") Telescope Coordinates: RA (20h 08m 46s) DEC ( 35° 51' 21") Target Coordinates: RA (20h 08m 46s) DEC ( 35° 51' 21")
2023-06-28T23:12:12 Effective telescope focal length is updated to 401.376 mm.
2023-06-28T23:12:12 Solver RA (301.95816) DEC (35.79074) Orientation (-177.83787) Pixel Scale (1.93224) Parity (neg)
2023-06-28T23:12:12 Solver completed after 0.47 seconds.
2023-06-28T23:12:11 Image received.
2023-06-28T23:12:07 Capturing image...
2023-06-28T23:12:06 Slew complete. Target accuracy is not met, running solver again...
2023-06-28T23:12:03 Slewing to target coordinates: RA (20h 08m 46s) DEC ( 35° 51' 21").
2023-06-28T23:12:03 Syncing to RA (20h 02m 59s) DEC ( 35° 57' 39")
2023-06-28T23:12:03 Target is within  01° 26' 57" degrees of solution coordinates.
2023-06-28T23:12:03 Solution coordinates: RA (20h 02m 59s) DEC ( 35° 57' 39") Telescope Coordinates: RA (20h 08m 45s) DEC ( 35° 51' 21") Target Coordinates: RA (20h 08m 46s) DEC ( 35° 51' 21")
2023-06-28T23:12:03 Effective telescope focal length is updated to 401.319 mm.
2023-06-28T23:12:03 Solver RA (300.52422) DEC (35.89760) Orientation (-177.83562) Pixel Scale (1.93251) Parity (neg)
2023-06-28T23:12:03 Solver completed after 5.02 seconds.
2023-06-28T23:11:58 Image received.
2023-06-28T23:11:54 Capturing image...
2023-06-28T23:11:33 Solver Failed.
2023-06-28T23:11:31 Image received.
2023-06-28T23:11:27 Capturing image...
2023-06-28T23:11:19 Solver aborted after 94.49 seconds.
2023-06-28T23:09:44 Image received.
2023-06-28T23:09:40 Capturing image...
2023-06-28T23:08:47 Solver Failed.
2023-06-28T23:08:35 Solving with blind image position...
2023-06-28T23:08:35 Image received.
2023-06-28T23:08:31 Capturing image...
2023-06-28T23:08:26 Solving with blind image scale...
2023-06-28T23:08:26 Image received.
2023-06-28T23:08:22 Capturing image...
2023-06-28T23:08:21 Image received.
2023-06-28T23:08:17 Capturing image...
2023-06-28T23:08:14 Slewing to target coordinates: RA (20h 08m 46s) DEC ( 35° 51' 21").
2023-06-28T23:08:14 Solution coordinates: RA (20h 08m 46s) DEC ( 35° 51' 21") Telescope Coordinates: RA (20h 08m 47s) DEC ( 35° 51' 23") Target Coordinates: RA (20h 08m 47s) DEC ( 35° 51' 22")
2023-06-28T23:08:14 Solver RA (301.96800) DEC (35.78974) Orientation (-177.86034) Pixel Scale (1.93251) Parity (neg)
2023-06-28T23:08:14 Solver completed after 0.36 seconds.
2023-06-28T23:08:13 Loaded image was taken on pierside WEST
10 months 2 days ago #93700
Attachments:

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

Time to create page: 0.300 seconds