开云体育

I've got an older Gemini 1 with flat RJ45 RA and Dec cables that I'd like to update to curly RJ45 cables. I don't want to invest in a crimping tool, bulk cable and connectors for this one time job but I'm having a hard time locating cables that I can be confident are correct for my application. I would appreciate a link to some ready made curly cables or would be happy to purchase some from a member of this board that makes this sort of thing. Thanks! Warren

Greetings, GM8; I am able to connect via Bluetooth to my laptop using ASCOM. Both Stellarium and Sky Safari, but alas, not on my tablet. Suggestion on a platform which works on an Android would be most appreciated. 1,000 Thanks in Advance!!

Does anyone have a hand controller for the 492 Losmandy Digital system? Losmandy has a used one one but they want way too much for it in my opinion.

Has anyone found a block diagram to simulate your way around the Gemini I Level 4 controller? I do have the manual printed out, but it's a bit clunky. Could just be me. 1,000 Thanks!

Folks, A new version of the ASCOM driver that fixes some timeout issues related to PEC and PEMPro programming for L4 Gemini-1, and increases timeouts for most serial communications is now available: https://gemini-2.com/ASCOM.html * Enable solar system objects selection from Objects + Coordinates screen (L6 and later) * Add a window to select one of multiple observations from Small and Solar System Objects * Fix for PEMPro + PEC programming for Gemini-1 L4 timeout errors * Increased timeouts for serial comms for L4 and later * Fix worm cycle display in PEC window for Gemini-1 L4 * Additional statistics and frequency display in PEC Chart window

I have a Gemini 1 L4 controlling a G11. I have just replaced the CR2354 battery with a new one measuring at 3.3v. I cold started the system and successfully set all the parameters such as mount type, time and location but when I put it in sidereal mode it refuses to activate the motors using the buttons on the handset. Any suggestions? David

I recently purchased the upgrade from Gemini I to Gemini 2. I have watched most of the videos on the Losmandy site. I saw a couple of references to software such as Stellarium. Does anyone have any other recommendations? Thank you

Hi gang, Is the ASI Air compatible with Gemini II please.

I'm new to the forum and new to the Losmandy G11 and Gemini 1. The Gemini unit appears to power up properly with all 4 "arrow" buttons seeming to operate properly when used for menu selection, sub-menus selection and previous menu selection as described in the user manual. After alignment, or if I skip the alignment process, the arrow buttons will not power/slew the RA or Dec motors manually? Any ideas? What am I missing? Occasionally, during the alignment process, The Dec motor will turn (I can hear it), but the Dec axis does not move. How tight should the RA and DEC clutches be when slewing the mount? Lastly, the mount is just back from Losmandy with new tucked in motors and worm drives. Thanks for the insight as I begin this journey of knowledge.

One question, Each time that you perform a pointing model is it necessary to save it, and download after the new warm restart, or Gemini 1 does it automatically? Luis

Hi all, figured I should join and post to this group rather than the Gemini-2 now: My club has recently obtained a G11 with Gemini-1 board shown here: https://gemini-2.com/pcb/GeminiPCB1A.jpg We noticed it is completely missing the battery holder (and obviously battery), and the on/off switch is bad. After checking the board for other obvious issues, we jumped the switch and applied power, where the Hand Controller came to life, causing a big sigh of relief. I do not have a photo of the board at hand, so do not know if the battery mods mentioned here https://gemini-2.com/Gemini1-early-mods.html have been performed, or are even still relevant? 1. Can anyone point me to a proper battery holder to repair the board with, and which battery is currently suggested for use? 2. Are the battery mods above still appropriate? 3. Any other mods/issues we should be aware of to bring this board back into service? 4. The firmware is Level 4.something (don't recall without the HC at hand). What is the latest/bestest revision that ca/should be applied here? 5. Can anyone think of a reason the battery holder would have been removed? Thanks in advance for any info you can provide! I am posting separately on the Losmandy users forum r.e. G11 tuneups. Dale Nelson

Duplicate message to one posted on Losmandy Group. I am trying to understand when Meridian Flips are allowed as my attempt to do a manual flip are not working as expected. ---- How I do the Flip Manually I have been testing some dome behavior and am trying to manually initiate MF operations. On Gemini L4, I recall there being a quick menu to do a MF. On Gemini II I am resorting to Goto > Coordinate Input, Enable Flip, and leave current coordinates in place. There is also a menu option in the ASCOM HC, Funcs > Perform Meridian Flip. ---- My Configuration I have my limits set as follows: Eastern Safety Limit 99:10 (deg:min) This corresponds to an Hour Angle of -00:36:34 hr:min:sec So a MF request from WEST to EAST will not be allowed if target HA < -00:36:34, right? Western Safety Limit 101:30 This should correspond to an Hour Angle of +00:45:43 hr:min:sec So, 45 minutes after crossing the Meridian the mount should stop tracking Also, a MF from EAST to WEST will not be allowed if target HA > +00:45:43 Western Goto Limit 11:00 This corresponds to an absolute goto limit of 101:30 - 11:00 = 90:30 deg:min or an Hour Angle of +00:01:59.67 hr:min:sec I set this conservative value to allow NINA to make a MF 2 min after the Meridian per some comments made by Jim Waters. ---- My Experiment If my mount is on the WEST and pointing at HA = -01:15:00, it is too early to make a MF to the EAST. This makes sense because it would violate the Eastern Limit which only allows HA to slew 36min prior to the Meridian. If my mount is on the WEST at HA = 00:01:07, which happens to be within the Western Goto Limit, I am able to make a MF. No issues here. However if the mount is on the WEST and tracks further to HA = +00:35:00, I am unable to make a MF. This does not make sense to me as a flip would not violate the ESL and, since I am getting near the western limit, a MF would be a really good thing to do now! Why does the Western Goto Limit have anything to do with *preventing* a flip back to the EAST? I thought it was the furthest west you could go before a GOTO would *force* you back to the EAST. Can anyone point me at a specification for Gemini II of the conditions under which the HC or ASCOM UI will accept a flip that I explicitly requested? Once the Western Safety Limit is violated ... beeping ensues ... how do I get back on target if it won't do a goto?

Hello Group Looking for advice on setting up Automated Meridian Fiip on my Gemini 1/G11/APT setup. After watching Brian's various videos on automating the Meridian Flip I applied the the priciples to my own Gemini 1 and G11 setup. Here are my derived measurements which I input to the Gemini 1 controller:- Eastern Safety Limit = 88 deg, Western Safety Limit = 114 deg, Western GOTO Limit = 23 deg. Last night we had our first brief spell of clear weather so thought I would try an Automated MF. Chose the star Regulus which was about 1.25 hrs from transiting the Meridian. I also configured my aquisition software, APT, to automate the MF. Not sure I interpretted APT's instructions correctly but set this up as "Flip Moment (mins)" to = 5 mins, "Delay Flip Move (mins)" = 8 mins and checked "Delay is counted after Meridian passing". I Cold Started Gemin1 and selected Regulus from the Bright Star List in the Hand Controller but the mount did not move and the Hand Controller displayed "Interrupted'. Lots of double checking everything and reading the Gemini 1 Manual (should have done that earlier) and it would seem that I have a problem with my Safety Limits. Following a statement in the G1 Manual I changed my 1Western GOTO Limit' from my calculated value of 23 deg to 95 deg and the mount went straight to Regulus. APT seemed to behave as I concluded it should of by stopping 5 mins before the Meridian, taking a 10 sec image then attempting to Plate Solve it and use these coordinates after the flip to recentre but by this time the conditions had deteriated and the plate solve failed so APT left the mount with tracking off . I thouhgt I would try and get something from the evening so I tried a Manual Flip using the Gemini net ascom driver which was successful. I then called it a night and read some more of the Gemini 1 Manual on the topics of Safety Limits and Meridien Flips. I am confused by what I read in the Gemini Manual which mentions possible problems with setting your Western GOT Limit between 1 - 89 deg. It also talks about Western GOTO Limits with values of 2.5 and 95 deg which I find hard to equate with Brian's videos. I am starting to believe that Gemin 1 and Gemini 2, for which the videos were produced I believe, might handle the Meridian Flip differently, for example having to set the Weastern GOTO limit referenced from the CWD position hence angle such as 95 deg etc. Any assistance or guidance on how to apply Brians AMF videos to a Gemini 1 setup would be very welcome and appreciated as would any APT users who have successfully configured APT's Automated Meridian Flip instructions. Regards Terry (uk)

Hi - I have a Gemini 1 L4 v1.05 unit that seems to be having eprom issues. Luckiiy I have a spare control panel that works fine. Where can I buy a replacement eprom for my faulty unit? Regards Mark

Hi, newbie to my CG-11 and this forum, I searched but didn't find an answer to my problem. I use NINA 2.0 HF1 and ASCOM Gemini Drive 1.0.84.0 to control the mount via my laptop, no HC. During a Meridian Flip in NINA Sequencer I get a handful of timeout errors from the Driver, then when the Flip process is complete, during the platesolve and recenter process the mount disconnects from NINA. In NINA's Advanced Sequencer I've add a "reconnect telescope" trigger after the Meridian Flip and that works to solve the issue. However, in the normal Sequencer routine NINA doesn't offer that option. While combing the ASCOM Log looking for timeout errors, it appears to be a Bad Checksum error that leads to a timeout? What ASCOM/Gemini command disconnects the Driver from NINA? The log is a very large file, so I only attached a smaller section that has suspicious words like timeout, error and disconnect. Thanks in advance to whomever can help me out.