Quote:
Originally Posted by rally
Possible suggestion ?
You probably already know that there are existing standard protocols for many of the functions that you are proposing within ASCOM.
It could make good sense that your system attempt to use these because that makes your box compliant with a large amount of existing Astronomy software out there.
It also means that you are not reinventing the wheel entirely and can make use of existing programs by writing an appropriate driver and can then mix and match amateur and commercial products as the need arises and people progress from one level to another or want the functionality that an existing commercial product offers because they dont have the skills to precision machine their own device for example.
I am sure I have read about existing Observatory controllers that make use of the Velleman board that are ASCOM compliant
Once you go down the automation path you might want to make use of the existing scheduling and planning software - "Glue", that holds all the different telescope/obs sub systems together.
So you may as well make use of them and just write the stuff to control the devices that are not already covered by them.
Just a thought ?
Cheers
Rally
|
Good comments, Rally, this is where the asset of having IIS reaps the benefits, so many people can make constructive inputs to the design.
I confess I'm unfamiliar with the scope of ASCOM, I just like to use it
If the wheel has been invented, that would seem to be a very sensible approach. I'll do some more research on it.
If you have access to any additional information on ASCOM-related Obs functions, links would be most appreciated.
If we can keep this as far as possible as a "glue" approach, so much the better. I'm still a little bemused that no one in the home Astro community seems to have done this. It's all been about telescopes
Cheers,