×

INDI Library v1.9.1 Released (26 Jun 2021)

Bi-monthly INDI Library v1.9.1 is released bringing a few new drivers and improvements to existing drivers.

Meridian flip not working consistently

  • Posts: 13
  • Thank you received: 0
I have been unable to fix this issue. I have reset the mount to factory defaults. It has auto-meridian flip set as a default.
I rebuilt my Linux machine and installed the latest version of KStars 3.5.2 2021-03-01 and tested. Meridian flip worked, once, then would not work again. When it reaches the meridian + 0.1 it states "Meridian Flip Planned". No further captures take place and it just sits there and does nothing.
However I have found that if I uncheck the Meridian Flip if HA>0.1 before a run and then check it again then it will meridian flip during the run - hence the title of my topic.

I see from the changelog that there were a number of changes made around the meridian flip part. Is it possible that something has gone awry?

 
Scopes: William Optics ZenithStar 73, William Optics ZenithStar 103, Skywatcher 200P reflector. Mount: Skywatcher HEQ5 Pro Rowan. Guiders SW9x50 and WO 50 Uniguide both with ZWOASI120MM, Cameras: Canon EOS400D astro-modded, ZWO ASI 183MC-Pro OSC, ZWO ASI 183MM Pro mono Filters: IDAS D2, Altair Ast
Last edit: 3 months 1 week ago by Terry McKnight.
3 months 1 week ago #70260

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

  • Posts: 30
  • Thank you received: 5
My iOptron mount, failed to do a MF last night, because my mount stops dead at the meriddean. (Not sure if this is Firmware?)
My ask is that we have the capability to say Flip Early (-ve) or Flip Late (+ve).

Thus I can say 10 minutes before the meridean schedule the flip, then it will wait for the last image to come in and do the flip.
Currently what happens is that if the image is still being taken on the meridean, then the mount aborts and stops on the meridean and just hangs there till the morning and my last image has star trails.

This should be pretty easy change as all we need is to unlock the setting to allow a negitive number?
Or have i missed something here, as i am pretty new to scheduler.
Christopher | Sussex England | n2042.blogspot.com
iOptron GEM45 | Altair Mobile Pier | TSPhoton 154 @ F3.7
ASI 294MM Pro | ASI EFW | ASI EAF | ASI 120MM
Mini PC | Quad 4GB 64GB 5G | Juice USB Harness
Last edit: 3 months 1 week ago by christopher.
3 months 1 week ago #70364

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

  • Posts: 745
  • Thank you received: 96
No. The problem is most mounts do not even have a 'flip' command, so EKOS only sends a 'slew to target' after it has crossed the meridian. The mount firmware then sees that it's in the other hemisphere, and performs the flip.

In your case, you have to set the mount (via the hand controller) what to do. You can usually set the acition (stop or flip), and the limit when to perform this.
Standard is to set the mount to a 'safety setting', i.e., set it to flip (or stop) quite late (like 5 degrees past meridian), and then set EKOS to flip, say, 2 degrees after meridian.

What happened in your case most likely was that the mount stopped by itself before EKOS could initiate an action. The above settings will prevent that situation.
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
The following user(s) said Thank You: christopher
3 months 1 week ago #70365

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

  • Posts: 30
  • Thank you received: 5
Thanks, new mission is to update driver to set the flip location as i sold my handcontroller.
Christopher | Sussex England | n2042.blogspot.com
iOptron GEM45 | Altair Mobile Pier | TSPhoton 154 @ F3.7
ASI 294MM Pro | ASI EFW | ASI EAF | ASI 120MM
Mini PC | Quad 4GB 64GB 5G | Juice USB Harness
3 months 1 week ago #70407

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

  • Posts: 745
  • Thank you received: 96
Depending on what mount it is, you can also set that via serial commands. From the command language description:
It should be saved to eprom, and survive power cycling.
Some mounts also allow to query the current setting via “:GMT#”.
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
3 months 1 week ago #70414

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

  • Posts: 26
  • Thank you received: 2
In the past I only managed an auto flip about 40-60% precent of the time. So I always set an alarm to wake me up so I can watch it. Every time it fails there is a different sequence. (no flip or says it flipped but did not or flips then solves the wrong way.....)

Anyway my last "FIX" was to clear ALL alignment and sync settings and turn off ALL sync and align functions in EKOS, there are 3 tabs under EQMOD-EKOS. This is not remembered by EKOS so needs doing after every restart.

It now works about 90% of the time.

I have never had a flip work near the zenith.

I will look into mount settings mentioned above to see if I can get nearer to 100%.

(This is all on SW EQ5, 6 and 8 )
Last edit: 3 months 4 hours ago by John. Reason: 8 became and emoticon.
3 months 5 hours ago #70854

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

  • Posts: 576
  • Thank you received: 55
Sorry for stepping in again...
For me MF works most of the time (HEQ5, no hand controller, Stellarmate latest stable).
I just had a flip 2 minutes ago imaging the Whale Galaxy (close to Zenith).
It went just fine.

What doesn't work consistently since a few months ago is the Guider calibration step after the flip.
The calibration goes in a wrong direction and fails.
If I stop the calibration and restart (or wait for it to fail and restart) then it calibrates correctly.
Is this just me or anyone else has the same issue?
Max S.

RPI 4 B (4Gb) with SMate
Nikon D5500 H-a modified. Nikon D5500 stock
AT72EDII, TPO RC6
ASI2600MC Pro
ZWO ASI120MM Mini on ZWO 30F4
ZWO ASI224MC-S on Orion 50 mm f/3.2
ZWO EAF x 2
SW AZ-GTi
SW HEQ5
RST-135
2 months 3 weeks ago #70943

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

Time to create page: 0.798 seconds