That might not be a bad idea, as in almost all case it'd be able to share code.
We'd need to copy it and change the base class to probably INDI::Device and we could keep the Interfaces for the others which load as is, if we wanted something in parallel and quick and dirty, or we could see about moving from INDI::Telescope to INDI::TelescopeInterface and we could load it as needed, similar to the rotators and other things which are detected on connection.
After looking a bit, Actually scratch that, there's no telescopeinterface. Probably the only project that might consider it is OnStepX (heh). More fun with flexible open source software!
yes I agree and even we could make it a bit differently.
Splitting the driver code in files specific to rotator, focuser and telescope and just include things as needed.
So we would end up with three main files located something like
indi/drivers/focuser OnStep_Focuser.cpp and .h
indi/drivers/rotator OnStep_rotator.cpp and .h
indi/drivers/telescope OnStep_Telescope and .h
but needs to be tought out carefully since it would also be a complete rewrite of the code to make things more modular
I am quite new to this topic and am very interested in contributing to the onstep driver and to onstepx. As my setup is using two focuser I would like to improve the second focuser feature in the driver. Right now the driver can be selected with a custom switch that is not used by any indi client application. To me this looks like a workaround to avoid adding multiple focusers to the driver.
Do you know if it is possible to add multiple focuser tabs to the driver, so it can be selected by client applications like Ekos etc.?
I am not quite sure if this is possible or if adding two devices of the same kind to one driver is not provided by the indi library.
honestly I am not really interested in adding support for multiple focusers into the driver and this for two reasons:
- When I first tried to implement the second focuser it was a nightmare with Ekos
- I prefer the idea to have a dedicated driver for additional focusers (less complexity)
But of course if you would like to work on this topic free to you, that(s the purpose of open source
If you intend to start this job, it would be good advice to read Indi doc and see is multiple instances of "FI" (Focuser Interface) are possible and recognized by Ekos. I made so many times the error to believe it works but discovered afterwards it is not working with Ekos ...
As far as I know, there is only one project that has forked from OnStep and reached a high level of usability, it is "TeenAstro".
Maybe some other people did something in this way but I never heard about.
I don't undersatnd your concern.
There is nothing to build.
Just go to [tools][Devices][Device Manager][Focusers][TeenAstroFocuser] and start the Service
you now should be able to connect to OnStep and use the Focuser.