ASCOM Gemini Driver - updated

[jase (Jason)]

Perhaps old hat news...(apologies if its already been posted).

Gemini Telescope .NET (1.0.0.0) has been released;
http://ascom-standards.org/Downloads/ScopeDrivers.htm

This is a successor to the Gemini 4.2.27 driver.

I've been running in over the past few nights during slew tests and plate solves. Appears to be more reliable when running remotely. Telescope park commands and homing are adhered to. Compared to a few times where I'd need to remotely power cycle the mount to return it to the home position with the old driver.

With a try if you're up to it. The 'Version 1.0.0.0' label may not give many a boost of confidence.

[allan gould]

Have you tried the voice option as well as the gamepad control function?

[jase (Jason)]

No Allan, I've not tested these.

I'm not physically around to listen the mount advising what its doing as I operate the gear 160km's away. My focus is more on reliability and robotic functions. So far so good on the latter two.

I'm pleased you can now force meridian flips as needed remotely, though I usually let the goto limit determine this automatically based on the target.

Also, this new driver has a cool feature to nudge the mount out of the slew safety limit if it is reached for what ever reason. This is a major bonus as once you hit the safety limit, you can't issue any PC ascom commands to correct it (so you don't damage equipment no doubt). Normally you need to use the hand paddle/controller to move the scope out of the safety limit zone, then PC ascom commands can be issued again. Accessing the hand paddle while remote isn't going to happen so you're stuck in a nasty situation.

You can of course get around the safety limit zone, even if you don't want to use this new feature but you need to disconnect from ASCOM and connect via a serial console port to issue a series of commands that will re-park the mount.

I ended up scripting it in ACP to simplify getting out of this nasty situation (below), but now I don't think I'll need to use this with new driver.

Sub Main()
Console.PrintLine "Sending Me command"
Telescope.CommandBlind("Me")
Console.PrintLine "Finished CommandBlind(Me), waiting for 5 seconds"
Util.WaitForMilliseconds 5000
Console.PrintLine "Sending Qe command"
Telescope.CommandBlind("Qe")
Console.PrintLine "Finished CommandBlind(Qe), sending hP command"
Telescope.CommandBlind("hP")
Console.PrintLine "Finished CommandBlind(hP), End of script"
End Sub

The Me, Qe and hP statements are raw Gemini commands (not ascom). Move east (to get out of the safety limit zone), wait 5 secs, stop, then park the mount. In essence, that's all this new driver is doing, talking to the mount in its native command set.

[allan gould]

Thanks for that Jase, most informative. I'm also really interested in the ability for pulse-guiding that I want to test out soon.
Allan

[JohnG (John)]

The latest release is 1.0.7.0, released about a week or so ago.

http://tech.groups.yahoo.com/group/Gemini_ASCOM_Driver/

Cheers

[allan gould]

Gemin driver is now updated to V1.0.8.
Tried it with my Gemini and Losmandy mount and its superb.
Have now installed it in my observatory and using voice annunciations as well as controlling it using the wireless controller - extremely simple to use and works perfectly.
Highly recommended

[Octane (Humayun)]

Allan,

Can you explain what the vocal thing is all about?

Do I upgrade the ASCOM driver running on my laptop tonight seeing as I'm going to Border Stargaze tomorrow morning? ; )

H

[allan gould]

Humayun
One of the new features of EQMOD and the new ASCOM gemini driver is that you get a voice feedback of what your mount is doing. You just select the voice option in preferences and when slewing you get Microsoft Sam's crappy voice saying "mount Slewing" or if you increase the speed "Rate increase" goto object etc etc. Really helps in the dark so that you know that command has been accepted etc.
At present Im in the process of modifying my laptop screen to a touch screen device. I found that when I went to upgrade my laptop that a trialled a Toshiba touchscreen lappy. O beautiful and no more messing about in the dark trying to see the keyboard. Worked great with my planetarium program and CCDSoft.
But thats OT. Try the voice option - very good.

[Octane (Humayun)]

Allan,

Appreciate that -- will give it a go. : )

H

[Bassnut (Fred)]

Originally Posted by jase

Also, this new driver has a cool feature to nudge the mount out of the slew safety limit if it is reached for what ever reason..

Gaud, believe it or not, I have to hand nudge the PME out of the limit too, and then home, before anything else .

[allan gould]

One thing I forgot to mention is that the latest Gemini ASCOM driver will allow pulseguiding which is great as I found with the EQ6 that this form of guiding was far superior to straight ST4 style guiding ie was able easily to guide at 2500mm with round stars.

[allan gould]

Finally got hold of my GPUSB-AH from Shoestring Astronomy (to guide older Losmandy Gemini with RJ45 ports) and it works beautifully with pulse-guiding and PHDguiding and the new ASCOM 1.0.8 driver. Very happy now as I can keep the Losmandy mount in the observatory and use the EQ6 for mobile work.
Ive also attached a touch screen to my laptop which makes working in the dark so much easier than trying to use a keyboard. One of the better improvements to portable computing.

[JohnH]

Originally Posted by allan gould

One thing I forgot to mention is that the latest Gemini ASCOM driver will allow pulseguiding which is great as I found with the EQ6 that this form of guiding was far superior to straight ST4 style guiding ie was able easily to guide at 2500mm with round stars.

Can you explain why this method is better?

I was of the understanding that ST4 commands would be better than anything going via the software/firmware/serial loop (less lag?) - when using a camera with on-board guide port (eg QHY5).

Or perhaps I should just try it?

[allan gould]

Originally Posted by JohnH

Can you explain why this method is better?

I was of the understanding that ST4 commands would be better than anything going via the software/firmware/serial loop (less lag?) - when using a camera with on-board guide port (eg QHY5).

Or perhaps I should just try it?

Its all explained here :-
http://f1.grp.yahoofs.com/v1/kDGITGR...%20Guiding.pdf
but to quote from the article:-
ST4 Guiding
• Advantages:
– Available in All EQMod Connection options
• Disadvantages:
– Rate changes will require re-calibration
– Can not be combined with PEC

Pulse Guiding
• Guide commands sent via EQMOD
• Advantages:
– Variable rate pulse guiding
– Modify/modify pulse control on the fly
– Combine with PEC
• Disadvantage:
– Can only work with EQDIRECT configuration
– Too many variables (things to remember)

EQMOD and Gemini pulse guiding apparently operate the same AFAIK
Allan

[JohnH]

Ah - but that is about the advantages of the EQMod on an EQ6 so I am not sure this really applies to Gemini driven mounts - for example PEC on a Gemini can be combined with ST4 guide inputs - in fact this is SOP as far as I know.

So Pulse gives speed and duration but has to go via the firmware whereas ST4 signal is on/off only (ie duration) at whatever guide rate is set (typically 0.5x) and acts directly on the motor controller.

[allan gould]

Originally Posted by JohnH

Ah - but that is about the advantages of the EQMod on an EQ6 so I am not sure this really applies to Gemini driven mounts - for example PEC on a Gemini can be combined with ST4 guide inputs - in fact this is SOP as far as I know.

So Pulse gives speed and duration but has to go via the firmware whereas ST4 signal is on/off only (ie duration) at whatever guide rate is set (typically 0.5x) and acts directly on the motor controller.

John
You are probably correct but as there is NO information re the gemini ascom driver and so since they give it the same name I assumed it had the same functionality as the EQMOD version. Anyway using the Gemini ascom driver and PHD i had very excellent guiding - no matter what its doing under the hood I really don't care as the guiding at 2500mm was excellent.