开云体育

Folks,

I've been tearing my hair out for the past month on this.? The initial symptoms were that it was impossible to polar align my mount using the PAA routine in Kstars.? After enabling logs, and Hy over on Indilib.org reviewing them, we found that either the driver or the mount are reporting my Longitude at 0.? Here is what I see in the log:

[2024-11-25T20:27:31.687 EST DEBG ][ ? ? ? ? ? org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] RES <Harold> "
[2024-11-25T20:27:31.687 EST DEBG ][ ? ? ? ? ? org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] Site Name <Harold> "
[2024-11-25T20:27:31.688 EST DEBG ][ ? ? ? ? ? org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] <getSiteLatitudeAlt> "
[2024-11-25T20:27:31.688 EST DEBG ][ ? ? ? ? ? org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] CMD <:Gt#> "
[2024-11-25T20:27:31.688 EST DEBG ][ ? ? ? ? ? org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] RES <+26 20> "
[2024-11-25T20:27:31.688 EST DEBG ][ ? ? ? ? ? org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] VAL [26,20,0.0] "
[2024-11-25T20:27:31.688 EST DEBG ][ ? ? ? ? ? org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] <getSiteLongitudeAlt> "
[2024-11-25T20:27:31.688 EST DEBG ][ ? ? ? ? ? org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] CMD <:Gg#> "
[2024-11-25T20:27:31.688 EST DEBG ][ ? ? ? ? ? org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] RES <+080 08> "
[2024-11-25T20:27:31.688 EST DEBG ][ ? ? ? ? ? org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] VAL in CartographicLongitude format [-80,6,0.0] "
[2024-11-25T20:27:31.689 EST INFO ][ ? ? ? ? ? org.kde.kstars.indi] - Losmandy Gemini : ?"[INFO] Mount has Latitude 26:25:0.0 (26.3382) Longitude (0 to +360 Eastwards) 360:00:00.0 (360) "
[2024-11-25T20:27:31.690 EST DEBG ][ ? ? ? ? ? org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] Configuration successfully saved for GEOGRAPHIC_COORD. "
[2024-11-25T20:27:31.690 EST DEBG ][ ? ? ? ? ? org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] CMD <:GG#> "

Things that might be useful:

I have also included the verbose log of last night's session.? Help!

?

Sounds like a configuration mistake.? After you connect the Gemini to kstars and the mount goes to an unknown location use the HC can you verify where Gemini thinks it is located and what time Gemini thinks it is wherever that place is?? If Gemini thinks it is someplace else other than where it is then kstars is updating Gemini and that data is incorrect. Turn off whatever is updating Gemini's location and time data, reinitialize and see if it works as expected.?

?

?

AFAIK the indi driver for Gemini is well established and works well.? So it is most likely an incorrect setting.?

?

--

If someone could point me to the settings that cause this behavior, I would really appreciate it.

I have been testing with it on my desk and as soon as I connect the mount to kstars, the Longitude on the hand controller resets to 0, regardless of whether I set the mount to be time/location source or kstars.??

?

Thanks in advance,

Anand

Chip has succinctly identified the probable cause.? Although I don't use this software, learning is part of the enjoyment. In the Setup area under INDI, you have the option to select whether Kstars pushes its Time and Site update information or pulls it.? You've described a planetarium program pushing Greenwich time.? If you don't want Kstars to push, then set Kstars to pull the updates by choosing "GPS & Mount Updates KStars" to synchronize from the mount's perspective.

?

It should function either way, but since you mentioned having a GPS for the mount that defines the current location and time, try setting it to pull.? As Kstars is a planetarium program, ensure you also synchronize it to the current view (the sky Now) under Time for general operation with the mount.? This is just a suggestion, but it seems like the correct approach to avoid confusion in the dark later on.

Putting this here to try to save someone else the aggravation I’ve just been through. This is indeed a bug in the lx200 driver in Kstars. Please see this . ?This only affects users who have Kstars set to update its time and location from the mount. ?If you use Kstars as the source it’ works as expected.?

?

?

On Thu, Nov 28, 2024 at 01:00 PM, Anand Narwani wrote:

Putting this here to try to save someone else the aggravation I’ve just been through. This is indeed a bug in the lx200 driver in Kstars. Please see this . ?This only affects users who have Kstars set to update its time and location from the mount. ?If you use Kstars as the source it’ works as expected.?

?

?

?

Supposedly this was fixed in the Dec. 1 release on GIT.? Have you tried it yet???

?

--

I pulled the recent changes from Git and built it on a test environment.? I am willing to say that it appears to set the longitude correctly (if a little different from how I'm used to seeing it):

?

?

I will withhold final judgement until I am able to do a complete imaging run starting with polar alignment and ending with an image that is of the target that asked it to take.? Once Indi 2.1.1 is released I will update and head to my dark site to test.

?

You might also want to update to the latest Gemini 2 and Hand Controller firmware, L6.1 and v1.63.? I don't know if it would directly impact this particular issue but they did a few nice things and it would also refresh all your Gemini 2 files with current versions which not surprisingly had some updated files.? ?

?

?

--

I did that in anger while trying everything, everywhere all at once.?