×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Astro Photography Tool (APT) now supports Indi

  • Posts: 79
  • Thank you received: 23
I do not know how mature INDI is. But it is definitly older. By the way what do you think anout the news that pixinsight is migrating from INDI to INDIGO. i think that tells a lot about the maturity...
4 years 9 months ago #39776
The topic has been locked.

If you are interested, you can contact the author and ask for proper INDI support. Now there are StellarMate/AstroBerry/QHY StarMaster/AtikBase plus there are a couple more commercial devices under development based on INDI technology to be released soon, so it makes sense to support them.
4 years 9 months ago #39779
The topic has been locked.
  • Posts: 407
  • Thank you received: 74
Why the contest/friction between Indigo/Indi or so it seems to me IMO - most Astro users couldn't care a fig what software they use as long as it works in the way they want to work.

IMHO and simple experience :-

for DSLR

1. Indi works well and is fairly mature ,as it uses Gphoto2 (as I guess Indigo does for Linux) ,but it cannot be used by any Windows Client (unless you know different).

2. Indigo has a RPI based Web image (Indigosky) that will connect a DSLR but does not have the functionality/robustness of Indi Ekos- Plus Indigo ,IMO, seems to be more concentrated on Apple kit. APT was released when I last tried Indigosky - Stage0 ?

3. APT,in Windows only, has the big advantage as it uses Canon's own SDK (Canon are a pain IMO) which is not available on Linux/Unix as far as I am aware and does not allow DSLR or native ZWO access on Indi or Indigo at this stage. Although this was released in Jan2019 which suggests Linux support www.canon-europe.com/press-centre/press-...sdk-and-api-package/


IMHO (which doesn't count for much) APT have made a mistake in not including DSLR users in the initial release - but its their software and therefore their decision - good luck APT it is good software(I have used it for 4yrs) . Guess I am too focused on DSLR use but then there are many such users and they are not Apple based.

If I am wrong about what does work or doesn't etc - please correct me.
RPI3 Ubuntu 16.04 / AMD desktop Kstars under Ubuntu 16.04 Mounts :azeq6 ,SWAZGoTo

RPI3 Fedora testing out on AMD desktop Fedpra 28 - running kstars 2.9.4 , Indilib 1.7.4 ?????
4 years 9 months ago #39783
The topic has been locked.
Well, technically it works with KStars/SkyCharts/PixInsight/etc on Windows, but I take it you already know that :D
4 years 9 months ago #39785
The topic has been locked.
  • Posts: 407
  • Thank you received: 74
:blush: Yes I did - I wrote that badly. What I was trying to point out was that there is no Windows Application (Astro) that can call Gphoto2 directly unless it was Indi/Indigo aware - i.e. no Indi or Indigo server involved in the chain.

Nearest was Virtualhere (RPI Virtualhere server and Windows Virtualhere client - no Gphoto2 involved) but that was too slow but it did work!

Hope that makes more sense know
RPI3 Ubuntu 16.04 / AMD desktop Kstars under Ubuntu 16.04 Mounts :azeq6 ,SWAZGoTo

RPI3 Fedora testing out on AMD desktop Fedpra 28 - running kstars 2.9.4 , Indilib 1.7.4 ?????
Last edit: 4 years 9 months ago by Clive Stachon.
4 years 9 months ago #39789
The topic has been locked.
  • Posts: 79
  • Thank you received: 23
Stash, indigo is not concentrated to Mac. Indigo is native to linux and Mac. And the client library is also windows native. It just happend that the there is more client software on mac. But with Pixinsight and APT, windows it will be also well supported. And yes you are correct indigo does not have native linux clients but this is changing. However all indi clients work against indigo server but in legacy mode. By the way have you tried ekos against indigo? It works :)
4 years 9 months ago #39793
The topic has been locked.
  • Posts: 554
  • Thank you received: 138
I wonder what the oldest standard is that's in current use on the internet. TCP/IP must be pretty old, so are the email protocols. Then there's ASCII... As for the QUERTY keyboard...
4 years 9 months ago #39795
The topic has been locked.
  • Posts: 1067
  • Thank you received: 140

I have tried indigo with Ekos, and it does work, but poorly, you even have to start the indigo server manually, which is a pain... :(
4 years 9 months ago #39808
The topic has been locked.
  • Posts: 407
  • Thank you received: 74
Not strictly "on the internet" but the Internet wouldn't work without it - the "Half Adder" :-) :evil:
RPI3 Ubuntu 16.04 / AMD desktop Kstars under Ubuntu 16.04 Mounts :azeq6 ,SWAZGoTo

RPI3 Fedora testing out on AMD desktop Fedpra 28 - running kstars 2.9.4 , Indilib 1.7.4 ?????
4 years 9 months ago #39810
The topic has been locked.
  • Posts: 407
  • Thank you received: 74
Yes tried all variations and as someone else has already said its too slow (slower than Virtualhere) But I did like he Web control Interface in Indigosky , as I reported to you before(email), which was clean ,simple to use and uncluttered :-).

"It just happend that the there is more client software on mac" - hence my use of the word concentrated :-)

Plus still does helps with DSLR via APT. Yes I do like my APT software :-)

As I stated its not Indi/Indigo/Linux fault - I lay the problem squarely on Canon(and other DSLR makers) - for not releasing the SDK for Linux.

Thats not a criticism of Gphoto dev team who deserve massive praise for the massive project of reverse engineering the protocols used. :-)

Hopefully later releases of APT (3.90) will provide me with what I want. :-)
RPI3 Ubuntu 16.04 / AMD desktop Kstars under Ubuntu 16.04 Mounts :azeq6 ,SWAZGoTo

RPI3 Fedora testing out on AMD desktop Fedpra 28 - running kstars 2.9.4 , Indilib 1.7.4 ?????
4 years 9 months ago #39811
The topic has been locked.
  • Posts: 79
  • Thank you received: 23
I have to disagree. Ekos works well with i digo server. The problem is that ekos is hardcoded to work with indiserver. We can not make it to support start and stop of indigo. On the other hand indigo server is not always required if you run properindigo client.
4 years 9 months ago #39828
The topic has been locked.
  • Posts: 111
  • Thank you received: 41
I don't know how you would define: "mature implementation", but let's make a simple experiment
and run cppcheck over the core library source files (no driver, no external libraries,....)
of INDI and INDIGO
Cppcheck report - cppcheck report: Statistics
 
Back to summary
 
Top 10 files for error severity, total findings: 18
   6  indibase/connectionplugins/ttybase.cpp
   4  indibase/indidetector.cpp
   3  lx/Lx.cpp
   1  stream/encoder/rawencoder.cpp
   1  lilxml.c
   1  indicom.c
   1  indibase/indilightboxinterface.cpp
   1  indibase/indicontroller.cpp
 
Top 10 files for warning severity, total findings: 149
   35  indibase/alignment/ConvexHull.h
   28  indibase/inditelescope.cpp
   22  webcam/v4l2_base.cpp
   11  stream/jpegutils.c
   8   indibase/indidome.cpp
   4   stream/streammanager.cpp
   4   indibase/indiusbdevice.cpp
   4   indibase/baseclient.cpp
   3   webcam/v4l2_decode/v4l2_builtin_decoder.cpp
   2   webcam/v4l2_decode/v4l2_decode.cpp
 
Top 10 files for portability severity, total findings: 18
   5  indibase/indidetector.cpp
   2  stream/recorder/serrecorder.cpp
   2  indibase/inditelescope.cpp
   2  indibase/indiccd.cpp
   1  stream/streammanager.cpp
   1  indicom.c
   1  indibase/indilogger.cpp
   1  indibase/indidome.cpp
   1  indibase/indiccdchip.cpp
   1  indibase/baseclient.cpp
 
Top 10 files for performance severity, total findings: 76
   55  indibase/alignment/TelescopeDirectionVectorSupportFunctions.h
   7   indibase/alignment/BasicMathPlugin.cpp
   2   indibase/defaultdevice.cpp
   2   indibase/baseclientqt.cpp
   2   indibase/baseclient.cpp
   2   indibase/alignment/InMemoryDatabase.cpp
   1   webcam/v4l2_decode/v4l2_decode.cpp
   1   stream/streammanager.cpp
   1   stream/recorder/recordermanager.cpp
   1   stream/encoder/encodermanager.cpp
 
Top 10 files for style severity, total findings: 761
   80  indibase/connectionplugins/connectionserial.h
   70  indibase/connectionplugins/connectiontcp.h
   52  webcam/v4l2_base.cpp
   32  webcam/v4l2_decode/v4l2_builtin_decoder.h
   31  indicom.c
   27  stream/ccvt_misc.c
   21  indibase/indidome.cpp
   17  indibase/indidetector.cpp
   17  indibase/defaultdevice.h
   16  dsp/buffer.c

where,
libindi/libs>find . -type f | wc -l
173

And now let us repeat the experiment for INDIGO
Cppcheck report - cppcheck report: Statistics
 
Back to summary
 
Top 10 files for error severity, total findings: 1
   1  indigo_ccd_driver.c
 
Top 10 files for warning severity, total findings: 9
   8  indigo_client.c
   1  indigo_server_tcp.c
 
Top 10 files for portability severity, total findings: 29
   24  indigo_ccd_driver.c
   3   indigo_bus.c
   2   indigo_driver.c

where,
indigo/indigo_libs>find . -type f | wc -l 
88

Now one can also divide by the number of code files to get the relative comparable result.
Using other metrics, such as e.g. what is the memory footprint, number of cycles starting from exposure to finally getting the FIT file delivered,
and you will see immediately which code is much "more mature" ;)
4 years 9 months ago #39945
The topic has been locked.
Time to create page: 1.391 seconds