×

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

Bi-monthly release with minor bug fixes and improvements

Mount doesn't complete the meridian flip

  • Posts: 1185
  • Thank you received: 370
Is a capture sequence running? Planned means that the mount waits until the next capture is completed.
4 years 9 months ago #40105

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

  • Posts: 209
  • Thank you received: 33
No there is no capture sequence running.
I am using the Ekos Mount panel to test the meridian flip.
4 years 9 months ago #40109

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

  • Posts: 1185
  • Thank you received: 370
Hm, strange. Please post the logs.
4 years 9 months ago #40110

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

  • Posts: 554
  • Thank you received: 138
I would certainly wonder if any command was actually sent to the mount. A full debug log from the mount driver will show the commands to the mount. It should also show the pier side response from the mount.
4 years 9 months ago #40111

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

  • Posts: 209
  • Thank you received: 33
Here are the logs for the mount only.
Settings :
- Hand control / Meridian : Favor East
- Ekos : Flip if HA > 0.00 h
When the object crossed the meridian, the scope started a flip without completing it (it had some sort of a hiccup !) and Ekos said :
"Meridian flip running ..." and then "Meridian flip completed" and then "Status : inactive"
I don't know how to attach the log file . I pasted it :

[2019-06-11T21:37:40.098 CEST INFO ][ org.kde.kstars] - Welcome to KStars 3.2.3
[2019-06-11T21:37:40.098 CEST INFO ][ org.kde.kstars] - Build: 2019-05-30T02:21:19Z
[2019-06-11T21:37:40.099 CEST INFO ][ org.kde.kstars] - OS: "osx"
[2019-06-11T21:37:40.099 CEST INFO ][ org.kde.kstars] - API: "x86_64-little_endian-lp64"
[2019-06-11T21:37:40.099 CEST INFO ][ org.kde.kstars] - Arch: "x86_64"
[2019-06-11T21:37:40.099 CEST INFO ][ org.kde.kstars] - Kernel Type: "darwin"
[2019-06-11T21:37:40.099 CEST INFO ][ org.kde.kstars] - Kernel Version: "18.6.0"
[2019-06-11T21:37:40.099 CEST INFO ][ org.kde.kstars] - Qt Version: 5.12.0
[2019-06-11T21:37:40.106 CEST DEBG ][ default] - Starting DBus
[2019-06-11T21:37:40.301 CEST DEBG ][ org.kde.kstars] - Opened the User DB. Ready.
[2019-06-11T21:37:40.554 CEST INFO ][ org.kde.kstars] - Processing "unnamedstars.dat" , HTMesh Level 3
[2019-06-11T21:37:40.554 CEST INFO ][ org.kde.kstars] - Sky Mesh Size: 512
[2019-06-11T21:37:40.572 CEST INFO ][ org.kde.kstars] - Loaded DSO catalog file: "unnamedstars.dat"
[2019-06-11T21:37:40.572 CEST INFO ][ org.kde.kstars] - Processing "deepstars.dat" , HTMesh Level 3
[2019-06-11T21:37:40.572 CEST INFO ][ org.kde.kstars] - Sky Mesh Size: 512
[2019-06-11T21:37:40.573 CEST INFO ][ org.kde.kstars] - Loaded DSO catalog file: "deepstars.dat"
[2019-06-11T21:37:40.579 CEST INFO ][ org.kde.kstars] - Processing "USNO-NOMAD-1e8.dat" , HTMesh Level 6
[2019-06-11T21:37:40.586 CEST INFO ][ org.kde.kstars] - Sky Mesh Size: 32768
[2019-06-11T21:37:40.591 CEST INFO ][ org.kde.kstars] - Loaded DSO catalog file: "USNO-NOMAD-1e8.dat"
[2019-06-11T21:37:40.859 CEST WARN ][ org.kde.kstars] - "Star HD20794 not found."
[2019-06-11T21:37:40.868 CEST WARN ][ org.kde.kstars] - "Star HD98230 not found."
[2019-06-11T21:37:40.877 CEST DEBG ][ default] - File opened: "/Users/JCJ/Library/Application Support/kstars/ngcic.dat"
[2019-06-11T21:37:40.877 CEST INFO ][ org.kde.kstars] - Loading NGC/IC objects
[2019-06-11T21:37:41.264 CEST DEBG ][ default] - File opened: "/Users/JCJ/Library/Application Support/kstars/comets.dat"
[2019-06-11T21:37:41.395 CEST WARN ][ org.kde.kstars] - "Object named NGC 3314A not found"
[2019-06-11T21:37:41.397 CEST WARN ][ org.kde.kstars] - "Object named NGC 6050A not found"
[2019-06-11T21:37:41.400 CEST WARN ][ org.kde.kstars] - "Object named NGC 72 not found"
[2019-06-11T21:37:41.400 CEST WARN ][ org.kde.kstars] - "Object named NGC 78 not found"
[2019-06-11T21:37:41.402 CEST WARN ][ org.kde.kstars] - "Object named NGC 4666 not found"
[2019-06-11T21:37:41.403 CEST WARN ][ org.kde.kstars] - "Object named NGC 7318 not found"
[2019-06-11T21:37:41.403 CEST WARN ][ org.kde.kstars] - "Object named NGC 7839 not found"
[2019-06-11T21:37:41.403 CEST WARN ][ org.kde.kstars] - "Object named NGC 7840 not found"
[2019-06-11T21:37:41.403 CEST WARN ][ org.kde.kstars] - "Object named IC 1127 not found"
[2019-06-11T21:37:41.404 CEST WARN ][ org.kde.kstars] - "Object named IC 2497 not found"
[2019-06-11T21:37:41.404 CEST WARN ][ org.kde.kstars] - "Object named IC 4703 not found"
[2019-06-11T21:37:41.404 CEST WARN ][ org.kde.kstars] - "Object named 2 Encke not found"
[2019-06-11T21:37:41.404 CEST WARN ][ org.kde.kstars] - "Object named 81 Wild 2 not found"
[2019-06-11T21:37:41.408 CEST WARN ][ org.kde.kstars] - "Object named NGC 72 not found"
[2019-06-11T21:37:41.409 CEST WARN ][ org.kde.kstars] - "Object named NGC 78 not found"
[2019-06-11T21:37:41.410 CEST WARN ][ org.kde.kstars] - "Object named NGC 4666 not found"
[2019-06-11T21:37:41.411 CEST WARN ][ org.kde.kstars] - "Object named NGC 7318 not found"
[2019-06-11T21:37:41.412 CEST WARN ][ org.kde.kstars] - "Object named NGC 7839 not found"
[2019-06-11T21:37:41.412 CEST WARN ][ org.kde.kstars] - "Object named NGC 7840 not found"
[2019-06-11T21:37:41.412 CEST WARN ][ org.kde.kstars] - "Object named IC 1127 not found"
[2019-06-11T21:37:41.412 CEST WARN ][ org.kde.kstars] - "Object named IC 2497 not found"
[2019-06-11T21:37:41.412 CEST WARN ][ org.kde.kstars] - "Object named IC 4703 not found"
[2019-06-11T21:37:41.413 CEST WARN ][ org.kde.kstars] - "Object named 2 Encke not found"
[2019-06-11T21:37:41.413 CEST WARN ][ org.kde.kstars] - "Object named 81 Wild 2 not found"
[2019-06-11T21:37:41.446 CEST DEBG ][ org.kde.kstars] - Paths to color scheme : ("/Users/JCJ/Library/Application Support/kstars/themes")
[2019-06-11T21:37:41.592 CEST DEBG ][ org.kde.kstars] - Daylight Saving Time active
[2019-06-11T21:37:41.593 CEST DEBG ][ org.kde.kstars] - Next Daylight Savings Time change (Local Time): "Sun Oct 27 03:00:00 2019 GMT"
[2019-06-11T21:37:41.593 CEST DEBG ][ org.kde.kstars] - Next Daylight Savings Time change (UTC): "Sun Oct 27 01:00:00 2019 GMT"
[2019-06-11T21:37:41.604 CEST DEBG ][ org.kde.kstars] - Daylight Saving Time active
[2019-06-11T21:37:41.605 CEST DEBG ][ org.kde.kstars] - Next Daylight Savings Time change (Local Time): "Sun Oct 27 03:00:00 2019 GMT"
[2019-06-11T21:37:41.605 CEST DEBG ][ org.kde.kstars] - Next Daylight Savings Time change (UTC): "Sun Oct 27 01:00:00 2019 GMT"
[2019-06-11T21:37:41.605 CEST DEBG ][ org.kde.kstars] - Starting the timer
[2019-06-11T21:37:41.651 CEST DEBG ][ org.kde.kstars] - Date/Time is: "Tue Jun 11 19:37:41 2019 GMT"
[2019-06-11T21:37:41.651 CEST DEBG ][ org.kde.kstars] - Location: "LAVAL, France"
[2019-06-11T21:37:41.652 CEST DEBG ][ org.kde.kstars] - TZ0: 1 TZ: 2
[2019-06-11T21:37:41.673 CEST DEBG ][ org.kde.kstars] - "Black Body" :: "/Users/JCJ/Library/Application Support/kstars/themes/blackbody.colors"
[2019-06-11T21:37:42.094 CEST DEBG ][ default] - Did not find glibc >= 2.1. Will use ANSI-compliant sin()/cos() functions.
[2019-06-11T21:37:52.259 CEST DEBG ][ default] - File opened: "/Users/JCJ/Library/Application Support/kstars/comets.dat"
[2019-06-11T21:37:58.187 CEST DEBG ][ default] - File opened: "/Users/JCJ/Library/Application Support/kstars/asteroids.dat"
4 years 9 months ago #40113

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

  • Posts: 1185
  • Thank you received: 370
That's how I expected it. This means that the Ekos Mount controller executed a meridian flip, i.e. it issued a slew command to the position where it is currently pointing at.

Now it's up to the mount how it reacts - see the discussion above and the hint from Chris to turn off the meridian flip control in the hand controller. It looks like the mount itself does not see a necessity in changing the pier side, although the position it is pointing at is beyond the meridian.

- Wolfgang
4 years 9 months ago #40117

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

  • Posts: 554
  • Thank you received: 138
There's nothing in that log fragment that relates to the mount.

You said:I would expect there to be problems with that setup. The attempt to move by the scope seems to indicate that the mount has recieved a slew command and the meridian mode, which is diferent to what I suggested, caused the mount not to do a flip.
As I said in my previous message:
Set the meridian mode to None.
Set the Flip Ha position to 0.2h
4 years 9 months ago #40118

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

  • Posts: 209
  • Thank you received: 33
Well Chris, I tried what you suggested :
Set the meridian mode to None.
Set the Flip Ha position to 0.2h
but this didn't initiate a flip.
I got the msg : "Meridian flip planned..."
I reset my hand control to Factory Settings : no flip.
I changed my location from France to Algeria which is in the same time zone WITHOUT daylight saving : no flip.
But I noticed something which might be the culprit : there is a variable difference between the hour angle indicated in the target details and its position to the meridian. In some occasion it might be as big as 1m30s when the target crosses the meridian.
I will try later this week on a friend's scope to see if things are working allright.
4 years 9 months ago #40126

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

  • Posts: 1957
  • Thank you received: 420
Does this angle difference increase with increasing declination? If yes, try an object close to the celestial equator and see if the flip happens then.

HTH, Wouter
4 years 9 months ago #40127

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

  • Posts: 554
  • Thank you received: 138
I have set up my AVX mout indoors and done a quick align.
Ekos is running and connected, I've set the Celestron GPS scope and the CCD Simulator.
Slew to an object that's about cross the meridian - Procyon as it happens.
The mount display in Ekos shows the Ra, Dec, Ha and LST as expected. The meridian flip is expected, the Ha limit is set to 0.1 hrs and when the mount data indicted an Ha of -20 minutes the time to flip was 26 minutes. All exactly as expected.
Looking on the HC display the Ra and Dec are the same, the LST is slightly different, by 2 mins 40 secs but that may be accounted for by slight differences in time or location in the mount or KStars The 6 minute delay before the flip is attempted should account for it.
I've set up an acquisition using the simulated CCD, 5 minute exposures.
And now I'm waiting...
The HC and EKos times are different by a couple of minutes or so, this probably accounts for the difference in LST.
These minor differences would be compensated for by doing a real alignment but the HC may have a slightly different position where a slew will change from one pointing state to the other.
Things I've not done:
I've not changed my location.
I've not set the meridian mode, it remains disabled.
I've not done a factory reset. That would set the mount location to Torrance.
The mount thinks it's past the meridian, ha axis shows 190 and increasing, Kstar doesn't think so.
Now Kstars thinks the mount is past the meridian, flip in 5 mins or so.
The image acquistion may cause it to hold off for a bit longer, up to the exposure time.
BTW I have set the mount time without DST enabled because Indi doesn't seem to handle it in it's local time structure.
Meridian time finished - Meridian flip running mount slewing
And it's a long slew, to the other side of the meridian.
I'm a little surprised there wasn't a delay but perhaps the CCD waits if there isn't time to complete the exposure before the slew is required.
Anyway the meridian flip was done as expected.

Hope this helps with working out what is happening
The following user(s) said Thank You: Jean-Claude JESIOR
4 years 9 months ago #40130

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

  • Posts: 209
  • Thank you received: 33
Thank you Chris for the suggestions and sorry for the late reply.
I think I solved the problem.
Suppose you are pointing a target to the South. A meridian flip will only be executed by the mount if the scope is on the West side of the pier pointing East. If the scope is already on this side of the pier, the meridian flip will not be executed because unnecessary.
I have a Celestron CGE Pro mount.
If I select a target with an hour angle HA < -1h (i.e. quite East), the scope will slew on the West side of the pier pointing East : in this case a meridian flip will be relevant.
If I select a target with an hour angle -1h < HA < 0 or HA > 0, the scope will slew on the East side of the pier pointing West : in this case a meridian flip will be irrelevant.
This is what caused my problem : at the correct HA, KStars sent a flip command to the scope which wasn't execute because it was not necessary. The mount had a hiccup but didn't flip.
To do the experiment without having to wait too long, you can fool the scope by doing the following.
On your hand control, select Meridian > Favor East. On KStars select a target with an HA around a few minutes and slew to it.
The scope will be on the West side pointing East. That's what you want.
Now immediately set Meridian > Disabled on your hand control.
When the target reaches the meridian (with some imprecision) the scope will flip.
4 years 9 months ago #40354

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

  • Posts: 554
  • Thank you received: 138
What I'm saying is to set the Meridian mode to none (the default) and leave it alone.
4 years 9 months ago #40357

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

Time to create page: 0.800 seconds