开云体育

Hi All I've just deforked a 12" Meade Classic which comes in now at 35Ibs. I also have the heavy-duty tripod. Been looking round for another mount to do some beginner astrophotography and visual.

Thanks for the wrap up Sean. ?Many threads get left “hanging” and it hard to know if you are actually helping. ? So a good wrap up feedback is very important import for other to learn from.

Good to hear you got it working, Sean. The "Gemini expects J2000" setting is off by default in the Gemini.NET driver. You must have turned it on at some point for it to be active. The setting is there

Must be all that extra resolution. The ASIAIR Plus I have been using for a few years saw the tracking error drop about 15-20% after going to L6.x I have not got the most steady or consistent skies

Thanks for the useful tips Paul. This will be helpful to those of us buying and running PEMPro and L6. -- Chip Louie Chief Daydreamer Imagination Hardware Astrospheric Weather Forecast - South

Hi George, It could have been that the selected star was temporarily dimmed by a cloud or wind spreading the star out over a wider area. -Ray

To close out this topic and give a summary; My solution was to insure "Gemini expects J2000" to be deselected when using NINA. As this was in a screen I rarely if ever looked at I can not remember if

Sure, try to lower camera gain. The PEMPro screen shots you posted show that the star it was using was at or very close to 32767 adu value. The fact that it didn't vary much between exposures is a

Interesting. I had set the maximum star brightness at 20,000 at one point and then worked my way lower from there. Most of my attempts had been with a maximum star brightness of 15,000. Would this be

An easier way is to tell PEMPro not to pick such over-exposed stars. Set maximum level to 20000 for your sensor to avoid picking saturated or nearly-saturated stars (32767 adu in your case):

Your guide star is overexposed and saturates the sensor pixels. Try shorter exposures, no binning, or find a dimmer star.

I recently upgraded to Level 6 (6.02) and decided to run new PE measurements and generate a PEC curve. I've run into a toothy/jagged PE measurement. I had this issue before with L5 and the solution

As Brendan has posted start with getting the basic connection using Gemini.NET - ASCOM driver - working first. Once you have the physical connection and the basic communication link and software

Hi Mark, first place to start is the Gemini 1 manual, downloads as pdf from this link here (

Good evening, I've heard you can control a Losmandy mount (I have just acquired a GM8/11) from a computer using astronomy software. Any recommendations, and can you point me to any instructions or

Sorry I didn't note you had a GPS for a gemini 1.?? This makes it more complicated but do able as it has an Rj11 plug for data (to serial port G1) and an Rj45 for power (to feature port G1) It'll

From what I know (or think I know) it’s a GPS ” week rollover bug (

Bringing this back to life, as I have the same issue with my Gemini 1 unit.? Did you ever find a way to update your Garmin unit?

I already have the Gemini2 updated to level 6, in a few days it will arrive home from Berlin, updated by Rene ??

Now the Gemini is being repaired by an integrated electronic circuit company. Thanks to all for your advice. Luis [email protected]>) escribió: