开云体育

Thanks, Trevor. That's the right file this time, but it's even more confusing :) What I see is that Gemini is reporting L6.12, which is one of the conditions for enabling the 4x encoder option. But,

try this one

Still not a Gemini.NET log. Look for the file name that I mentioned. Starts with *ASCOM.Gemini Telescope .NET.*

Great! Thanks Ryan. I will re-balance and adjust the knobs. Art Trailattrail1@...

Found it: /g/Losmandy_users/message/83608 Chip Louie explains here better than I can.

Sorry all new to this never had to do this before in over 15 years owning my mount :)

Sorry, but that's not the log I was looking for. The log I'd like to see is from the Gemini.NET ASCOM driver. That will be on your PC, the name should be something like *ASCOM.Gemini Telescope

Roboscope (what is your name?) Connect Gemini to the mount and start using it. Gemini doesn't let you go to objects that are below the horizon. If you believe some of these should be visible, then

Attached log don't know if will help

So I tried the screen calibration again,, following every step carefully, and it appears that calibration worked and the hand controller is functional. Then I went through all the buttons with a

This is correct. NINA internally works on the basis of J2000. Basically, anything that comes from a static database of coordinates - plate solve results, planetarium apps, NINA's own internal object

Thank you for taking time to answer my question.? Here are answers to specific questions in previous posts: * I do not have another G2, I was able to test the motors using one of my Gemini I units.?

Oh right, duh!? I used to know that when I used PC apps under ASCOM.? With ASIAIR's planned community ecosystem I have basically forgotten all of the issues that need to be looked at every time you

Wow! Why have I not read this or seen it it any videos. I have been through all Losmandy?docs and videos that I know of. Maybe I ignored it but I don’t think so.Thanks Ryan! I will definitely

Hmm. Sounds peculiar….

That is actually how it's supposed to work with NINA. The ASCOM driver tells NINA what precession coordinates are expected by Gemini, and NINA tries to ensure that the correct coordinates are sent.

Since it shows the selector for the encoder resolution, it's "new enough" :)? I'd recommend to run the ASCOM driver while connected to Gemini, and then bring up the advanced settings window. This

Yeah his HC is 1st ver but you can see this is his HC FW info I took pic of prior to sending. ?This showed updates were done to latest versions. It’s possible the HC might not have been Tx’ing

Hi Bren, that's a mystery! The screen shot that Trevor posted indicates that the encoders are still at 1x resolution, which the L6 firmware automatically sets to 4x when it first detects v3 PIC

Hi Trevor, the screen I wanted to see was with the Firmware version on it (Firmware/SRAM screen). But what I'm seeing from your screenshot, either the main unit firmware is not updated to 6.x or the