开云体育

Correct. In G2, bit 2 Modelling in use is used to indicate whether an alignment was done. Bit 1 is always set to 1.

ok

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

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 wrote: -- Brian Brian Valente

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

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

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

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

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

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

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

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

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

Set up and HC version images.? By following Losmandy setting limits video my limits are 94 otherwise contact with tripod legs.

Ok - 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) :) That's not the issue behind no flipping though: @Frank

Hi Graeme, You might be right. I just tried it from command terminal in the ASCOM driver, and this is what I get after a cold start:

I think this is a Gemini bug. I just cold started (power cycle and choice at restart) our G2 which running a slightly later Gemini version (with runaway slew, and RA=0 sync bug fixes) and it also

The log seems to show that Gemini thinks it's aligned. Status 1 was returned by <99: command. But certainly at least one sync/align is needed before doing any sort of testing from a Cold start.

The file date is weird, but the file itself appears to match the reported firmware version, 5.21

From Pointing.DAT: *! *** Losmandy Gemini2 Version 5.21 Build Mar 12 2017 08:22:00 started up **** I think the file date is a red herring here. Graeme