{single}{actor}{/single}{multiple}{actors}{/multiple} replied to the...

Wolfgang,

Thanks for looking at the log. I thought that I had the flip set to occur after the meridian had occurred, but I was playing with settings in that run. Is the value you're talking about 'meridian diff' ? Is that value in hours?

I'm attaching another log that has a MF failure, this one has:

[2023-05-03T11:12:11.530 CDT DEBG ][     org.kde.kstars.ekos.mount] - Meridian flip planned with LST= "00h 29m 54s"  scope RA= "12h 17m 54s"  ha= 0.199836 , meridian diff= 0.1 , hrstoFlip= -0.0998358 , flipDelayHrs= 0 ,  "Pier Side: East (pointing West)"
...
[2023-05-03T11:12:16.461 CDT WARN ][     org.kde.kstars.ekos.mount] - Meridian flip failed, pier side not changed

I have a GPS dongle connected to the RPi, it appears that Ekos sends the time & location to the mount since I've configured KStars to use GPS for location and time. I see this in the log:

[2023-05-03T10:52:02.173 CDT INFO ][     org.kde.kstars.ekos.mount] - "GPS driver detected. KStars and mount time and location settings are now synced to the GPS driver."

But I'll double check that when I start KStars.

Thanks again for your help. We have clouds for the next few days, so I"ll be doing indoor testing to see if I can reproduce this again.

Pete

File Attachment:

File Name: log_10-51-48.zip
File Size: 60 KB