Developing a driver is no rocket science and it is easy to maintain. For Ascom I have release Cycle that are aligned with the firmware update and I have to do the same with INDI.
What do I need to compile all that stuff? is it possible to crosscompile INDI with visual Studio?
Dragonlost asked me if I can develop an INDI driver for TeenAstro.
If think it is much easier for both community to have 2 drivers one for onstep and one for TeenAstro. Indeed all the beauty of OnStep is the flexibility and the beauty of TeenAstro is to keep the thing as simple as possible.
The good news is that TeenAstro overlap to 95% with ONStep and has significantly less feature. For example no PEC and No multiStar alignment...
My only problem is that I have no experience with LINUX...
Hello this is my first post here,
I have some experience in ASCOM driver development, and I wish to extend my knowledge to INDI. The goal of this topic is to find some people willing to developp/test a TeenAstro INDI driver.
The TeenAstro protocol overlap to 90% with the ONStep driver, and has TeenAstro has less function than OnStep it is significantly less effort.
I think it is easier to maintain 2 drivers: one for OnStep and one for TeenAstro then every body has the freedom to developp.
Most of the TeenAstro user are in Germany and are former user of the Little Foot or the excellent FS2.
If there are some users in germany that has INDI background I will be happy to support them.
TeenAstro user Grouphttps://groups.io/g/TeenAstro