×

INDI Library v1.8.0 is Released (27 Jul 2019)

INDI Library v1.8.0 is mostly a maintenance release to fix a few bugs in several drivers.

TeenAstro driver for INDI

  • Posts: 3
  • Thank you received: 0

TeenAstro driver for INDI was created by Charles

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

Charles
3 months 1 week ago #38856

Please Log in or Create an account to join the conversation.

Replied by knro on topic TeenAstro driver for INDI

Hello Charles,

Welcome to INDI! Let me know if you need any help with the driver. Some of the developers of the OnStep driver might be interested in this as well.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
3 months 1 week ago #38862

Please Log in or Create an account to join the conversation.

  • Posts: 60
  • Thank you received: 2

Replied by dragonlost on topic TeenAstro driver for INDI

Hello ! nice start !

here is my fork of indi :

github.com/dragonlost/indi

i have copy OnStep driver and remove PEC and Focuser part. I write new line in other file : CMaleLists.txt, drivers.xml, lx200driver.h, lx200generic.cpp

Following Kbahey's suggestion, it would be nice to put a symbolic link to the onstep functions that are identical and common to teenastro so as not to duplicate code.

It should remove all the part alignment to N star that is not supported by teenastro.
At first, no need to coded the part that allows you to change the mount settings on the fly.

Charles, will you be able to list the differences between teenastro and onstep so that everyone can clearly identify what he will need to do ?
Last edit: 3 months 1 week ago by dragonlost.
3 months 1 week ago #38942

Please Log in or Create an account to join the conversation.

  • Posts: 396
  • Karma: 2
  • Thank you received: 54

Replied by Herrhausen on topic TeenAstro driver for INDI

Will the Teenastro driver support the onboard focuser?
3 months 1 week ago #38952

Please Log in or Create an account to join the conversation.

  • Posts: 60
  • Thank you received: 2

Replied by dragonlost on topic TeenAstro driver for INDI

The focuser will not be supported by this driver because in teenastro the focuser is on another card (another teensy and usb). But nothing prevents to develop another driver for the focuser.
3 months 1 week ago #38954

Please Log in or Create an account to join the conversation.

  • Posts: 396
  • Karma: 2
  • Thank you received: 54

Replied by Herrhausen on topic TeenAstro driver for INDI

Many thanks for the clarification. Am I correct in assuming it currently doesn't make sense to build my own Teenastro if I want to continue on an "INDI only" basis?
3 months 1 week ago #38957

Please Log in or Create an account to join the conversation.

  • Posts: 186
  • Thank you received: 13

Replied by kbahey on topic TeenAstro driver for INDI

I think it is better if the INDI driver for TeenAstro and OnStep share the same code base (i.e. they are one .cpp/.h file).

The reasoning behind this is that TeenAstro is merely a subset of OnStep. So it will only be missing some features. The code can check the executable name and set a flag, and if it is TeenAstro then just skip the features that TeenAstro lacks. Everything else remains the same.

That way, bug fixes are quicker, and maintenance is generally easier.
3 months 1 week ago #38965

Please Log in or Create an account to join the conversation.

  • Posts: 60
  • Thank you received: 2

Replied by dragonlost on topic TeenAstro driver for INDI

actually this seems like a good solution. On the other hand, the coding in C and C ++ exceeds me. I only code in python. I am coding an interface to program the teensy with pyqt.
3 months 1 week ago #38966

Please Log in or Create an account to join the conversation.

  • Posts: 3
  • Thank you received: 0

Replied by Charles on topic TeenAstro driver for INDI

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?
Thanks.
Charles
3 months 1 week ago #38967

Please Log in or Create an account to join the conversation.

  • Posts: 221
  • Thank you received: 17

Replied by Blueshawk on topic TeenAstro driver for INDI

@Charles: Following this. :) I like the simple scope of this teensy only version of onstep. Try to keep that KISS attitude as you guys go forward.
I was reminded recently that keeping units separate has the benefit of making troubleshooting easier and processor redundancy, as in the case of using a standalone focuser or filter wheel, allows you to continue to operate the others if any one unit goes down. This just seemed like a good place to share that bit of wisdom.

@Kbhaley: Good idea! Maybe you can give them a short example of how the linking works?
I mean, if they still need it?

@Herrhausen I'd continue to use the version that's working for you. I think the idea here is to make the project more approachable for people just starting out.

just my 2c. :-*
3 months 1 week ago #38969

Please Log in or Create an account to join the conversation.

  • Posts: 186
  • Thank you received: 13

Replied by kbahey on topic TeenAstro driver for INDI

Blueshawk wrote: Good idea! Maybe you can give them a short example of how the linking works?
I mean, if they still need it?


There is an example of how INDI checks the name of the executable (which is actually a symbolic link), in this code .

In the above case, the code instantiates a new driver depending on the name. But I am suggesting that the codebase for OnStep and TeenAstro be a single code base, with the parts that the latter does not support being conditional in the code. This is much better in the long run.

There is always the temptation to write new code, but what people often forget is the technical debt carried forward with maintenance (bug fixes, new features, ...etc.).
The following user(s) said Thank You: Blueshawk
3 months 1 week ago #38970

Please Log in or Create an account to join the conversation.

Time to create page: 0.490 seconds