×

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

Bi-monthly release with minor bug fixes and improvements

Sudden problems with plate solving Kstars 3.6.8

  • Posts: 107
  • Thank you received: 12
Im not exactly sure when it started as I updated to the latest TheSkyX for my paramount also. (10.5.0 1368 On ubuntu 23.04).

Im trying to enable logs for astrometry and pointed the path to my home folder and the file never shows up. I also changed it from log none to log verbose. Leaving the log in /tmp also yields no log in /tmp no idea here.

Here is the dump from the alignment window at least:

2023-12-28T23:22:34 Capture aborted.
2023-12-28T23:22:34 Capturing image...
2023-12-28T23:22:32 Slew complete. Solving Alignment Point. . .
2023-12-28T23:22:31 Solver aborted after 0.80 seconds.
2023-12-28T23:22:31 Slew detected, suspend solving...
2023-12-28T23:22:31 Slew complete. Target accuracy is not met, running solver again...
2023-12-28T23:22:31 Slewing to target coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56").
2023-12-28T23:22:31 Syncing to RA (05h 26m 31s) DEC ( 29° 20' 24")
2023-12-28T23:22:31 Camera position angle is 88.9731 degrees.
2023-12-28T23:22:31 Target is within 00° 09' 48" degrees of solution coordinates.
2023-12-28T23:22:31 Solution coordinates: RA (05h 26m 31s) DEC ( 29° 20' 24") Telescope Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 58") Target Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56")
2023-12-28T23:22:31 Solver completed after 0.44 seconds.
2023-12-28T23:22:30 Image received.
2023-12-28T23:22:23 Capturing image...
2023-12-28T23:22:21 Slew complete. Target accuracy is not met, running solver again...
2023-12-28T23:22:20 Slewing to target coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56").
2023-12-28T23:22:19 Syncing to RA (05h 26m 31s) DEC ( 29° 20' 22")
2023-12-28T23:22:19 Camera position angle is 88.9921 degrees.
2023-12-28T23:22:19 Target is within 00° 09' 44" degrees of solution coordinates.
2023-12-28T23:22:19 Solution coordinates: RA (05h 26m 31s) DEC ( 29° 20' 22") Telescope Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 58") Target Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56")
2023-12-28T23:22:19 Solver completed after 0.47 seconds.
2023-12-28T23:22:19 Image received.
2023-12-28T23:22:11 Capturing image...
2023-12-28T23:22:10 Slew complete. Target accuracy is not met, running solver again...
2023-12-28T23:22:08 Slewing to target coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56").
2023-12-28T23:22:07 Syncing to RA (05h 26m 31s) DEC ( 29° 20' 21")
2023-12-28T23:22:07 Camera position angle is 88.9676 degrees.
2023-12-28T23:22:07 Target is within 00° 09' 40" degrees of solution coordinates.
2023-12-28T23:22:07 Solution coordinates: RA (05h 26m 31s) DEC ( 29° 20' 21") Telescope Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 58") Target Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56")
2023-12-28T23:22:07 Solver completed after 0.46 seconds.
2023-12-28T23:22:07 Image received.
2023-12-28T23:21:59 Capturing image...
2023-12-28T23:21:58 Slew complete. Target accuracy is not met, running solver again...
2023-12-28T23:21:56 Slewing to target coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56").
2023-12-28T23:21:56 Syncing to RA (05h 26m 31s) DEC ( 29° 20' 20")
2023-12-28T23:21:56 Camera position angle is 88.9671 degrees.
2023-12-28T23:21:56 Target is within 00° 09' 38" degrees of solution coordinates.
2023-12-28T23:21:56 Solution coordinates: RA (05h 26m 31s) DEC ( 29° 20' 20") Telescope Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 58") Target Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56")
2023-12-28T23:21:56 Solver completed after 0.43 seconds.
2023-12-28T23:21:55 Image received.
2023-12-28T23:21:48 Capturing image...
2023-12-28T23:21:38 Camera position angle is 88.9586 degrees.
2023-12-28T23:21:38 Solution coordinates: RA (05h 26m 31s) DEC ( 29° 20' 20") Telescope Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 58") Target Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56")
2023-12-28T23:21:38 Effective telescope focal length is updated to 2,454.68 mm.
2023-12-28T23:21:38 Solver completed after 0.41 seconds.
2023-12-28T23:21:37 Image received.
2023-12-28T23:21:30 Capturing image...
2023-12-28T23:21:05 Capture aborted.
2023-12-28T23:21:03 Capturing image...
2023-12-28T23:21:02 Slew complete. Target accuracy is not met, running solver again...
2023-12-28T23:20:59 Slewing to target coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56").
2023-12-28T23:20:59 Syncing to RA (05h 26m 32s) DEC ( 29° 20' 18")
2023-12-28T23:20:59 Camera position angle is 88.9691 degrees.
2023-12-28T23:20:59 Target is within 00° 09' 33" degrees of solution coordinates.
2023-12-28T23:20:59 Solution coordinates: RA (05h 26m 32s) DEC ( 29° 20' 18") Telescope Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 58") Target Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56")
2023-12-28T23:20:59 Solver completed after 0.49 seconds.
2023-12-28T23:20:58 Image received.
2023-12-28T23:20:50 Capturing image...
2023-12-28T23:20:44 Camera position angle is 88.962 degrees.
2023-12-28T23:20:44 Solution coordinates: RA (05h 26m 32s) DEC ( 29° 20' 18") Telescope Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 58") Target Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56")
2023-12-28T23:20:44 Effective telescope focal length is updated to 2,454.43 mm.
2023-12-28T23:20:44 Solver completed after 0.45 seconds.
2023-12-28T23:20:43 Image received.
2023-12-28T23:20:36 Capturing image...
2023-12-28T23:19:30 Capture aborted.
2023-12-28T23:19:30 Capturing image...
2023-12-28T23:19:28 Slew complete. Target accuracy is not met, running solver again...
2023-12-28T23:19:27 Slewing to target coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56").
2023-12-28T23:19:27 Syncing to RA (05h 26m 32s) DEC ( 29° 20' 16")
2023-12-28T23:19:27 Camera position angle is 88.9706 degrees.
2023-12-28T23:19:27 Target is within 00° 09' 30" degrees of solution coordinates.
2023-12-28T23:19:27 Solution coordinates: RA (05h 26m 32s) DEC ( 29° 20' 16") Telescope Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 58") Target Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56")
2023-12-28T23:19:27 Solver completed after 0.39 seconds.
2023-12-28T23:19:26 Image received.
2023-12-28T23:19:19 Capturing image...
2023-12-28T23:19:17 Slew complete. Solving Alignment Point. . .
2023-12-28T23:19:14 Solver aborted after 0.78 seconds.
2023-12-28T23:19:14 Slew detected, suspend solving...
2023-12-28T23:19:14 Slew complete. Target accuracy is not met, running solver again...
2023-12-28T23:19:14 Slewing to target coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56").
2023-12-28T23:19:14 Syncing to RA (05h 26m 32s) DEC ( 29° 20' 14")
2023-12-28T23:19:14 Camera position angle is 88.9664 degrees.
2023-12-28T23:19:14 Target is within 00° 09' 27" degrees of solution coordinates.
2023-12-28T23:19:14 Solution coordinates: RA (05h 26m 32s) DEC ( 29° 20' 14") Telescope Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56") Target Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56")
2023-12-28T23:19:14 Solver completed after 0.43 seconds.
2023-12-28T23:19:13 Image received.
2023-12-28T23:19:05 Capturing image...
2023-12-28T23:18:55 Mount is synced to solution coordinates.
2023-12-28T23:18:55 Syncing to RA (05h 26m 32s) DEC ( 29° 20' 15")
2023-12-28T23:18:55 Camera position angle is 88.9688 degrees.
2023-12-28T23:18:55 Solution coordinates: RA (05h 26m 32s) DEC ( 29° 20' 15") Telescope Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 58") Target Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56")
2023-12-28T23:18:55 Solver completed after 0.43 seconds.
2023-12-28T23:18:54 Image received.
2023-12-28T23:18:46 Capturing image...
2023-12-28T23:17:08 Camera position angle is 88.9915 degrees.
2023-12-28T23:17:08 Solution coordinates: RA (05h 26m 32s) DEC ( 29° 20' 14") Telescope Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 58") Target Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56")
2023-12-28T23:17:08 Solver completed after 0.47 seconds.
2023-12-28T23:17:07 Image received.
2023-12-28T23:17:00 Capturing image...
2023-12-28T23:11:22 Solver aborted after 11.58 seconds.
2023-12-28T23:11:15 Capturing image...
2023-12-28T23:11:14 Slew complete. Solving Alignment Point. . .
2023-12-28T23:11:12 Solver aborted after 0.72 seconds.
2023-12-28T23:11:12 Slew detected, suspend solving...
2023-12-28T23:11:12 Slew complete. Target accuracy is not met, running solver again...
2023-12-28T23:11:11 Slewing to target coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56").
2023-12-28T23:11:11 Syncing to RA (05h 26m 32s) DEC ( 29° 20' 11")
2023-12-28T23:11:11 Camera position angle is 88.9836 degrees.
2023-12-28T23:11:11 Target is within 00° 09' 25" degrees of solution coordinates.
2023-12-28T23:11:11 Solution coordinates: RA (05h 26m 32s) DEC ( 29° 20' 11") Telescope Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 58") Target Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56")
2023-12-28T23:11:11 Solver completed after 0.38 seconds.
2023-12-28T23:11:11 Image received.
2023-12-28T23:11:03 Capturing image...
2023-12-28T23:10:32 Camera position angle is 88.9923 degrees.
2023-12-28T23:10:32 Solution coordinates: RA (05h 26m 32s) DEC ( 29° 20' 11") Telescope Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 58") Target Coordinates: RA (05h 27m 07s) DEC ( 29° 16' 56")
2023-12-28T23:10:32 WCS information updated. Images captured from this point forward shall have valid WCS.
2023-12-28T23:10:32 Effective telescope focal length is updated to 2,453.87 mm.
2023-12-28T23:10:32 Solver completed after 1.46 seconds.
2023-12-28T23:10:31 Image received.
2023-12-28T23:10:23 Capturing image...
2023-12-28T23:08:30 World Coordinate System (WCS) is enabled.

The weird thing is Ive never had an issue with plate solving in EKOS. I can solve fine in TSX.

When you watch it try to "capture and solve" with "slew to target" selected you can see it initially center the star but as it fails it will move diagonally down and to the right with each fail an even increment. If I choose "nothing" for the action, it solves fine and finishes very fast. I can then center the object using the "center object" tool in the preview provided I don't try to do another astrometric solution and have it try to center again.

Almost feels like a Jnow vs J2000 issue due to the slow progression diagonally off the screen as it tries to center the star. Nothing in the release notes about a change in that or anything else relevant in the latest TSX. It was only a minor bump up.

I even went as far as removing my kstars settings completely and starting from scratch, same issue, so I reverted them back.

Im assuming you need the logs, but I can't make that work.

thanks

Bryan
3 months 4 weeks ago #97808

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

  • Posts: 602
  • Thank you received: 281
Hi Bryan,

Looks from the log info that plate solving is working, but for some reason the scope is not being moved nearer to the target between each iteration.

The solve gives you:
2023-12-28T23:10:32 Effective telescope focal length is updated to 2,453.87 mm.
Is that about right for your equipment?

I guess the next thing to check is slewing. When you slew to targets in the sky map does the scope slew "correctly"? For example, if you slew to a target higher in the sky and say West of the current position, does the scope move West and point higher?

As to whether its related to Jnow vs J2000 as you suspect, its possible. I don't know anything about the TheSkyX. Kstars uses Jnow so if TheSkyX is working in J2000 that could be a potential issue. Maybe something got flipped in the upgrades? On the Sky Map if you right click on the target and select details you can see the Jnow and J2000 coordinates.

How are you syncing time and location? - in Kstars its usually best to have Kstars update all devices (including the mount).
3 months 4 weeks ago #97812

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

  • Posts: 107
  • Thank you received: 12
The Focal length is correct. There is a jnow vs j2000 opton in the "mount control" window in EKOS, but I think that only changes what that particular window shows. Either way changing it and then setting a target and trying to solve/reslew makes no difference. Same problem.

I still can't make the log work either.

I found this old thread:

indilib.org/forum/ekos/2922-slew-to-target-failed/21867.html

exactly what is happening. Jasem, did something change in the latest build that would affect paramounts negatively again? You fixed something as noted in this thread.

Losing my mind. :/
The following user(s) said Thank You: Chris Madson
3 months 4 weeks ago #97824

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

Nothing was changed in the driver side. As far as I can see, everything is in Epoch of Date (JNow).
3 months 4 weeks ago #97826

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

  • Posts: 107
  • Thank you received: 12
Any thoughts as to what to do? Ill provide logs but I cant make that work either..
3 months 4 weeks ago #97827

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

I'm not sure, what's the focal length for your scope?
3 months 4 weeks ago #97828

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

  • Posts: 107
  • Thank you received: 12
2432. 304mm @F8 Is solving a bit higher but that has never been an issue
3 months 4 weeks ago #97829

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

  • Posts: 107
  • Thank you received: 12
3 months 4 weeks ago #97832

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

  • Posts: 270
  • Thank you received: 74
First let me underline, that John is right: The solving process works flawless, the problem lies in the slewing process,

This seems like the same issue:
www.indilib.org/forum/ekos/14087-alignme...sn-t-work.html#97387


Yes, I think you're right! Especially considering your brand of mount, which is a Paramount, right? I don't know this mount in depth, but it seems, it has the same kind of an internal stars model, which is compromised when executing a "sync", as it is the case with the standard [Load & Slew]. That's the reason why there is a switch called "Differential Slewing" (actually it is a *difference* slewing!). This switch prevents a "sync" in [Load & Slew] and induces a the slewing process relying entirely on the information of the mount's model.
As you saw in the mentioned thread above, I found, that the programming flow with difference slewing had some flaws. I tried to correct this flow and managed to get correct results with the telescope simulator. However I don't know it there are additional problems with a real mount like a 10Micron or Paramount.
Chris sent some logging information of his 10Micron which I will analyze.

Now the crucial question is: Are you using "Differential Slewing" and are you sure that your model is intact?
Nevertheless, it would be of great help, if you could get working the log system!
The following user(s) said Thank You: Chris Madson
3 months 4 weeks ago #97834

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

  • Posts: 147
  • Thank you received: 12
I completely forgot paramount has the same setup as 10 micron. From what I can see, he has the same issue I have.

Strangely enough, I turned off differential skewing and was x able to center my target. It didn’t seem to corrupt my model… but I don’t know what sync does in the INDI driver. In ASCOM, you can tell it to ignore syncs but there isn’t similar settings in INDI.

Thanks again for looking into this.
3 months 4 weeks ago #97837

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

  • Posts: 270
  • Thank you received: 74
I completely forgot paramount has the same setup as 10 micron.
With Paramount it is a matter of using the TPoint model of TheSkyX. (The INDI driver for Paramount is using it exclusively.) As far as I found out one can use this software for other mounts also such as Celestron, iOptron and so on. 10Micron doesn't use TPoint but has a similar solution -> www.indilib.org/forum/mounts/2484-10micr....html?start=36#83277

Strangely enough, I turned off differential skewing and was x able to center my target. It didn’t seem to corrupt my model…
In the mentioned thread Michael Fields writes: "Sync align mode is for shifting/correcting an existing model. So if you have 40 points from the night before but maybe you rebalanced and moved your OTA in the saddle, you choose sync align and do one single plate solve/sync and it shifts/corrects/updates your existing model." I'm not able to determine what the consequences really are, performing additional syncs on such a system. All contributions in the web, I have found so far, disadvise doing so, if you want to stay with the current model. But I must confess, I don't think the model is so good, if the telescope is landing so far away, that EKOS is complaining. Thus a sync would perhaps correct the model? I'm looking forward to get any clarification from experts reading this,

Good news are, that I found another problematic code fragment, which is responsible for the issues we have with "differential slewing". I hope to find a solution following that trace.
Last edit: 3 months 4 weeks ago by Toni Schriber.
3 months 4 weeks ago #97840

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

  • Posts: 147
  • Thank you received: 12
Good information. I know Mike; he's on our facebook group for the mount. Sync in my case definitely didn't add a point to the model... so it must've adjusted all the other points. Tracking wasn't 'as good' as measured by eccentricity... I was averaging .39-.43 last night and I usually get between .24-.29; but I have my old model saved.

Toni, if there are things I can try to enable testing for you LMK. Skies arent great here; but I'm supposed to have clear skies on Sunday. I'm on the Stellarmate discord too (mads0100).

Thanks,
Chris
3 months 4 weeks ago #97841

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

Time to create page: 0.659 seconds