¿ªÔÆÌåÓý

Meridian Flip - Stopped Working


 

Thanks Frank?

yes inside testing is fine for now

Looking at the zip file you uploaded (thanks again that is perfect) does not appear you reset the limits as I described previously? Also i did not see a pic of your telescope immediately prior to attempting the flip


I'm setting up to do this exact test

On Wed, Feb 22, 2023 at 11:13 AM Frank Wielgus <frankwielgus55@...> wrote:
Regarding the tests to solve the issue, they are done indoors, otherwise it might be months.

From a cold start CWD:
- the mount is pointing at the NCP
- if I do a "go to bright star", it goes there with no issue ( I know from having used it outside, the star is within the field of view )
- this tells me the NCP is an alignment point
I just tested adding another star and did an alignment. No difference in outcome - when just over the meridian, the meridian flip function does nothing. The other functions do work. Even nudging the mount further to when it starts beeping, the meridian flip function does nothing.



--
Brian?



Brian Valente
astro portfolio?
portfolio
astrobin?

--
Brian


 

The NCP is *not* an alignment point in the sense that Gemini understands (and neither should the initial alignment be anywhere near the poles if it can be helped or it's asking for trouble!). On first movement after restart, it just moves the distance it calculates from the encoder ticks/gearing ratios/date/time and assumes *everything* else is perfect.

[In fact, it is highly likely that you cannot point directly at the pole as it requires nigh on zero orthogonality error between the Dec and RA axis (but this is somewhat beside the point).]

The test you did that had the extended logging had no alignment point recorded and there's nothing to indicate at any point that you have had a successful alignment since the 17th Feb, which was then followed by the flip command being issued at the right point. Even having CWD correctly set for a fake alignment when testing is taken out of the equation, so there should just be these two items required together.


Graeme?





On Wed, 22 Feb 2023, 19:13 Frank Wielgus, <frankwielgus55@...> wrote:
Regarding the tests to solve the issue, they are done indoors, otherwise it might be months.

From a cold start CWD:
- the mount is pointing at the NCP
- if I do a "go to bright star", it goes there with no issue ( I know from having used it outside, the star is within the field of view )
- this tells me the NCP is an alignment point
I just tested adding another star and did an alignment. No difference in outcome - when just over the meridian, the meridian flip function does nothing. The other functions do work. Even nudging the mount further to when it starts beeping, the meridian flip function does nothing.


 

Brian thanks - I'm starting to loose track here.
Do you want me to repeat the test ?? Please repeat where you want the limits set. I will then image the scope at the point of trying the meridian flip.


 

On Wed, Feb 22, 2023 at 02:13 PM, Frank Wielgus wrote:
Regarding the tests to solve the issue, they are done indoors, otherwise it might be months.

From a cold start CWD:
- the mount is pointing at the NCP
- if I do a "go to bright star", it goes there with no issue ( I know from having used it outside, the star is within the field of view )
- this tells me the NCP is an alignment point
I just tested adding another star and did an alignment. No difference in outcome - when just over the meridian, the meridian flip function does nothing. The other functions do work. Even nudging the mount further to when it starts beeping, the meridian flip function does nothing.
I tried to do exactly what you describe here, Frank.

I had Level 6 beta already flashed, so I tried a cold start, slew to past the meridian, and then do :Mf#... and it flipped with no problems, even without a single sync or align. Repeated a couple of times, works!

I then flashed firmware 5.21 and now, with cold start, align/sync, etc., I can't make it flip using the :Mf# command. The result is exactly like what you're getting, :Mf# returns 0, meaning success, but no flip. Anywhere before or past the meridian, all the way to the safety limit, still no flip. Unless I'm missing something, it appears the :Mf# command is broken in that version...

Regards,

? ?-Paul


Jim Waters
 

I haven¡¯t looked though each of the previous posts so I am likely missing necessary information.?

I am running 5.21 and I think ASCOM Gemini Driver 1.1.17.0 with NINA 2.1 HF1 RC0x and haven't had issues doing Meridian Flips with my G11G.? My setup process is as follows.? I was running ASCOM Gemini Driver 1.0.84 but upgraded recently.


  • Set CWD.? Use bubble levels on RA and DEC
  • Power on ¨C Quick start (Don't understand the difference between Quick and Cold Start now)
  • Polar align the mount with PoleMaster and SharpCap Pro
  • Park the mount CWD
  • Cycle power ¨C Quick Start
  • Model the mount - 3 or more in west then east
  • Setup NINA's target

I connect to the Gemini-2 through point-to-point Ethernet.? After modeling the mount I don¡¯t use the HC.? Everything is through NINA.? When I kick off an imaging session the mount is CWD and I tell NINA to sync from NINA to Gemini-2.? Never the other way around.? I have had issues syncing the other way.

I use Edward's setting for NINA and the mount Limits settings.

I am not sure if the above adds any value.


-----------------------
Jim W
Phoenix, AZ USA


 

In the auto meridian flip settings, is the "use telescope side of pier" on or off?


Jim Waters
 

On

-----------------------
Jim W
Phoenix, AZ USA


Jim Waters
 



-----------------------
Jim W
Phoenix, AZ USA


 

Frank I'm going to set you up with a support ticket so we can talk directly

There's a lot of cooks in the kitchen right now, and I realize it can be confusing for all



On Wed, Feb 22, 2023 at 11:51 AM Frank Wielgus <frankwielgus55@...> wrote:
Brian thanks - I'm starting to loose track here.
Do you want me to repeat the test ?? Please repeat where you want the limits set. I will then image the scope at the point of trying the meridian flip.



--
Brian?



Brian Valente
astro portfolio?
portfolio
astrobin?

--
Brian


 

On Wed, Feb 22, 2023 at 10:09 AM, Graeme Coates wrote:
so that's does appear to be a Gemini 2 bug (the reported value from <99: is incorrect when the mount has not had an Initial Alignment) :)
FYI this is confirmed as expected behavior. Gemini 2 has no "Initial Alignment" anymore, <99 always returns 1 + x. The coordinates are taken from startup.
?
--
Brian


 

ok


 

On Thu, Feb 23, 2023 at 12:13 PM, Brian Valente wrote:
FYI this is confirmed as expected behavior. Gemini 2 has no "Initial Alignment" anymore, <99 always returns 1 + x. The coordinates are taken from startup.
Correct. In G2, bit 2?Modelling in use is used to indicate whether an alignment was done. Bit 1 is always set to 1.


 

Hi Frank,

I posted a possible fix for the meridian flip issue in L5.21 using the :Mf# command. The new, test driver posted in the Gemini ASCOM Driver group has a setting that uses a different method to force a meridian flip. Please see if this works any better and let me know (don't forget to set the Flip using Goto option in telescope settings):

/g/Gemini_ASCOM_Driver/message/5047

This will not fix the flip not working from the HC, but hopefully will fix it when it's requested through the ASCOM driver (from the menu or your other software).

Regards,

? ? -Paul


On Mon, Feb 20, 2023 at 10:43 AM, Frank Wielgus wrote:
So, given the above:
- mount does not flip even though it should
- manipulating limits does not help?
- happens via usb or ethernet
- happens even when not running an imaging application
- happen after testing a variety of cables and laptops
Does this imply anything regarding my gemini unit ?


 

ok - will test


 

Paul,
The fix did work.? Thanks


 

On Mon, Mar 20, 2023 at 10:47 PM, Frank Wielgus wrote:
Paul,
The fix did work.? Thanks
Good to hear! Thanks for testing and reporting the issue, Frank!

Regards,

? ? -Paul