×
INDI Library v1.8.1 Released (09 Sep 2019)

Monthly maintenance release INDI v1.8.1

TeenAstro driver for INDI

6 months 1 week ago
Charles
Fresh Boarder
Fresh Boarder
Posts: 3
More
Topic Author
TeenAstro driver for INDI #38856
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

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

6 months 1 week ago
knro
Administrator
Administrator
Posts: 7355
Karma: 51
TeenAstro driver for INDI #38862
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

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

6 months 1 week ago 6 months 1 week ago by dragonlost.
dragonlost
Senior Boarder
Senior Boarder
Posts: 60
More
TeenAstro driver for INDI #38942
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 ?

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

6 months 1 week ago
Herrhausen
Platinum Boarder
Platinum Boarder
Posts: 508
Karma: 3
More
TeenAstro driver for INDI #38952
Will the Teenastro driver support the onboard focuser?

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

6 months 1 week ago
dragonlost
Senior Boarder
Senior Boarder
Posts: 60
More
TeenAstro driver for INDI #38954
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.

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

6 months 1 week ago
Herrhausen
Platinum Boarder
Platinum Boarder
Posts: 508
Karma: 3
More
TeenAstro driver for INDI #38957
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?

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

6 months 1 week ago
kbahey
Gold Boarder
Gold Boarder
Posts: 201
Karma: 2
More
TeenAstro driver for INDI #38965
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.

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

6 months 1 week ago
dragonlost
Senior Boarder
Senior Boarder
Posts: 60
More
TeenAstro driver for INDI #38966
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.

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

6 months 1 week ago
Charles
Fresh Boarder
Fresh Boarder
Posts: 3
More
Topic Author
TeenAstro driver for INDI #38967
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

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

6 months 1 week ago
Blueshawk
Gold Boarder
Gold Boarder
Posts: 230
More
TeenAstro driver for INDI #38969
@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. :-*

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

6 months 1 week ago
kbahey
Gold Boarder
Gold Boarder
Posts: 201
Karma: 2
More
TeenAstro driver for INDI #38970

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

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

1 month 1 week ago 1 month 1 week ago by fdesvallees. Reason: Updated - problem was in the board
fdesvallees
Fresh Boarder
Fresh Boarder
Posts: 3
More
TeenAstro driver for INDI #44269
I am testing communications through EKOS and a TeenAstro mount controller. TeenAstro does not have a serial port, it communicates through TCP instead.
I used the LX200 Basic driver, because I was not able to configure OnStep for TCP (it seems to connect through serial only).

The communication starts fine, I can read the initial coordinates of the mount,

[2019-10-04T22:37:17.134 CEST INFO ][ org.kde.kstars.indi] - LX200 Basic : "[INFO] Connecting to 192.168.0.12@9999 ... "
[2019-10-04T22:37:17.434 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "[DEBUG] Connection successful, attempting handshake... "
[2019-10-04T22:37:17.442 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "[SCOPE] CMD <:GR#> "
[2019-10-04T22:37:17.446 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "[SCOPE] RES <09:53:28> "
[2019-10-04T22:37:17.446 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "[SCOPE] VAL [9.89111] "
[2019-10-04T22:37:17.447 CEST INFO ][ org.kde.kstars.indi] - LX200 Basic : "[INFO] LX200 Basic is online. "

but immediately after, the log shows communication errors

[2019-10-04T22:37:19.474 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "[SCOPE] CMD <:GR#> "
[2019-10-04T22:37:19.498 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "Error reading RA/DEC. "
[2019-10-04T22:37:21.484 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "[SCOPE] CMD <:GR#> "
[2019-10-04T22:37:21.491 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "Error reading RA/DEC. "
[2019-10-04T22:37:23.486 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "[SCOPE] CMD <:GR#> "
[2019-10-04T22:37:23.488 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "Error reading RA/DEC. "
[2019-10-04T22:37:25.488 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "[SCOPE] CMD <:GR#> "

I started investigating, and found out this is due to tty_write() returning an error: first TTY_WRITE_ERROR then TTY_OVERFLOW.

Before continuing, I would like to ask if anyone recognizes this, and ask for suggestions on how to fix it. Thank you!

** updated **
I found out the problem was in the board which would close the connection after 2 seconds.

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

Time to create page: 0.507 seconds