开云体育

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

Frank what is the firmware version you are currently running? You can check via hand controller Menu->HC->Info Thanks Brian Brian Valente Losmandy Astronomical Losmandy.com Tutorials and vids at

From the log zip file provided, Pointing.DAT appears to show no Initial Alignment since startup - If there is no initial alignment, Gemini will not flip. (I have a sample python script which I wrote

First is selected via the HC then synced.

Thanks, Frank.? The logs show all the settings and configuration, and I'm still unable to see anything that would cause the no flip behavior. *Maybe René?can take a look.* The comm errors you saw

Frank, How do you slew to the first star after a cold start? Do you manually slew to it or do you select an object from the hand controller and issue a goto command? If you manually slew and then

Interesting results. Once the troubleshooter started recording, I went to a bright star via the HC and synched.? During this time, error messages were flashing rather quickly with time out, com

In the first instance I suspect that you may have had an unusually cold period causing over-tight worm to ring mesh which caused stalls. However a faulty encoder could certainly cause similar

I'm currently using 1.0.84. I will download and install 1.1.17 beta.