开云体育

My Gemini and other things are set to UTC, which I ignore. I have my other timekeeping set to 24-hour time and can readily compute that in my head. But UTC eliminates DST bother. Whether we like it or

Paul, I don't think in UTC either. So I'll use my regular time/-4 offset. In the Fall I'll have to go into the handset and change it back to -5 via the cold start routine. No problem.? I have another

Paul, David is privileged somehow, in Merry Old England near the prime meridian ;) René Am 02.04.25 um 15:32 schrieb Paul Kanevsky:

Personally, I never liked that recommendation. I like to see my local date and time displayed on Gemini. Living many hours away from UTC, I don't think in UTC time, and rarely know what it is without

On Wed, Apr 2, 2025 at 09:03 AM, <fishonkevin@...> wrote: > > Hi Folks, > My name is Kevin, and this is my first time posting to the Group. I took > delivery of the Retro-fit kit for my G-ll on

Stick with UTC and set the clock accordingly (using an offset of 0). Never need to change it again. Sent: 02 April 2025 14:03 To: [email protected] Subject: [Gemini-II_io] First Time Set-up and Use

Hi Folks, My name is Kevin, and this is my first time posting to the Group. I took delivery of the Retro-fit kit for my G-ll on Monday and am planning on doing the basic set-up before installation

After I rebooted, it seems the mount thought it was a CWD as an attempt to park it simply kept it where it was. So, I shut it down and asked the staff to manually move it back to CWD. I've operated

Typically, I do a warm start if and only if the mount is still at CWD when I power it up. Further, the mount "knew" where it was for the first part of the session before comms was lost. Will do, but

Hi John, Yep, that would scare the heck out of me, too. Something I've done in the past, and as recently last week (first time in a long time) is to do a "Factory Reset". *Tanya of Losmandy hosts a

Hey John, Quick question: Were you able to regain mount communication before power-cycling the mount when you found it in the inverted position? If so, where did the mount "think" it was pointed at

John, it sounds like Gemini was in a bad state if everything was initialized properly, but then it lost communications with the PC and continued to track past the safety limit. A few things to check,

Thanks Doug, to be clear the mount was NOT parked as the software/driver lost communication.

Hi folks, An updated version of Gemini firmware L6.12 is now available. This fixes the reported issue where PEC, once programmed, can't be turned off and must be cleared to disable. Update your Gemini

Concur with Dale. PEC selects and deselects normally again. Works on the desktop hand controller as well as through PEMPro. Thank you Rene and Paul!

This seems to have fixed the issue. PEC on/off is fully controllable via PEMPro now. Thanks Paul and Rene ! Dale

Viewing this, could not this come about tracking past the west horizon.? Started west of the limits tracking does not cross them.? Check that the mount ended the session Parked.? If a secondary

Thank you Paul and Rene! Will try it out this afternoon if I can

Hi Ryan, Dale, and others using PEC with L6.11, René investigated the PEC not turning off issue in L6.11, and has produced an updated firmware L6.12 to resolve this. Please test with your Gemini and

By the way, my limit config -