×
INDI Library v1.8.6 Released (21 Aug 2020)

August 2020 release of INDI Library v1.8.6 introduces new drivers while providing fixes and improvements to existing devices and core framework.

Some help with understanding the basics

3 months 3 weeks ago
msacco
Fresh Boarder
Fresh Boarder
Posts: 14
More
Topic Author
Some help with understanding the basics #55033
Hey guys, got a raspberry pi recently and I'm trying to understand some of the basics of indi. Yes, I'm totally aware of the fact that there is astroberry which is a ready image, still, I like to learn how things work.
So I have installed a fresh raspbian image, I have installed indi which includes the server and the actual indi drivers, I did manage to start a server and obviously I'll need some software to "talk" to it, but on the raspberry pi level, is there any way of knowing that some device is "ready" or connected?

E.g:
indiserver -v indi_simulator_focus

This starts an indi server, so I guess that now the raspberry pi can talk to a client trying to access this driver? Can the raspberry pi communicate with itself? (I know it doesn't really make much sense...) For example, instead of connecting from a client(android, web, etc), control the driver directly from the raspberry pi itself? I assume that this is what happens under the hood maybe, the client simply sends commands to the raspberry pi which then forwards that to the drivers?

Sorry for the dumb questions, just trying to understand some of the basics and how some things work.
Thanks! :)

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

3 months 3 weeks ago
jerry
Gold Boarder
Gold Boarder
Posts: 198
Karma: 1
More
Some help with understanding the basics #55056
Hi,
Indi Web Manager can control and provide an indication of what indi services are running. www.indilib.org/support/tutorials/162-indi-web-manager.html
I have it running on an Odroid-N2 under ubuntu, so I can't comment on its suitability/compatibility under raspbian.
Cheers
Jerry

120 MM Skywatcher Esprit on Celestron CGX
ZWO ASI 224MC or QHY-5L-II-M for guiding
Nikon Z7 8256 x 5504, 35.9 x 23.9mm 4.34 um pixel size
Triad Ultra Quad Band Narrow Filter
Kstars installations:
1) Odroid-N2 Ubuntu-mate 20.04
2) StellarMate on RPI4 8G
3) KStars on Astroberry RPI3.

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

3 months 3 weeks ago
wotalota
Gold Boarder
Gold Boarder
Posts: 184
More
Some help with understanding the basics #55057
Reading through the entries under indilib.org/about.html provides a good overview. You generally monitor and control the indi
drivers from a client running locally or remotely. KStars/Ekos can also be run on the Rpi although it will be under powered. More common I think is for a client to communicate remotely to a Rpi running the drivers.

Mach1, TS86SDQ, ASI071, ASI174, OAG, focusPro

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

3 months 2 weeks ago
msacco
Fresh Boarder
Fresh Boarder
Posts: 14
More
Topic Author
Some help with understanding the basics #55114

jerry wrote: Hi,
Indi Web Manager can control and provide an indication of what indi services are running. www.indilib.org/support/tutorials/162-indi-web-manager.html
I have it running on an Odroid-N2 under ubuntu, so I can't comment on its suitability/compatibility under raspbian.
Cheers
Jerry

wotalota wrote: Reading through the entries under indilib.org/about.html provides a good overview. You generally monitor and control the indi
drivers from a client running locally or remotely. KStars/Ekos can also be run on the Rpi although it will be under powered. More common I think is for a client to communicate remotely to a Rpi running the drivers.


Thanks for the commends, I'm wondering though, if I'm running a raspberry pi headlessly, without actually having another machine running a client, can I validate that some driver is connected?
If so, how would I go about testing that?

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

3 months 2 weeks ago
wotalota
Gold Boarder
Gold Boarder
Posts: 184
More
Some help with understanding the basics #55118
Well I suppose you could ssh in and look at the drivers log file, would that serve the purpose?

[tg@tcup ~]$ indiserver -help
2020-06-05T13:02:49: startup: indiserver -help
Usage: indiserver [options] driver [driver ...]
Purpose: server for local and remote INDI drivers
INDI Library: 1.8.1
Code 1.8.1-tgz. Protocol 1.7.
Options:
-l d : log driver messages to <d>/YYYY-MM-DD.islog
-m m : kill client if gets more than this many MB behind, default 128
-d m : drop streaming blobs if client gets more than this many MB behind, default 5. 0 to disable
-p p : alternate IP port, default 7624
-r r : maximum driver restarts on error, default 10
-f path : Path to fifo for dynamic startup and shutdown of drivers.
-v : show key events, no traffic
-vv : -v + key message content
-vvv : -vv + complete xml
driver : executable or device@host[:port

Mach1, TS86SDQ, ASI071, ASI174, OAG, focusPro

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

3 months 2 weeks ago
dallmon
Senior Boarder
Senior Boarder
Posts: 58
More
Some help with understanding the basics #55129
ssh into the pi and type
ps ax |grep indi

That shows me all indi apps running.
BigMac:~ dallmon$ ps ax | grep indi
44995   ??  S      0:05.89 /Applications/KStars.app/Contents/MacOS/indi/indiserver -v -p 7624 -m 300 -r 0 -f /tmp/indififocd12bf59
44996   ??  S      0:03.43 indi_simulator_telescope
44997   ??  S      0:02.40 indi_simulator_ccd
44998   ??  S      0:05.49 indi_moonlite_focus
46829 s000  S+     0:00.01 grep indi

Dave Allmon

12" LX600
SBIG STF-8300EN
Raspberry Pi 4 Indi server
Mac Pro client

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

3 months 2 weeks ago
wotalota
Gold Boarder
Gold Boarder
Posts: 184
More
Some help with understanding the basics #55131
I tried the log using: $ indiserver -l /home/tg/ indi_moonlite_focus indi_asi_ccd &

Examined it:
tg@:~$ cat 2020-06-05.islog
2020-06-05T21:06:35: MoonLite: [INFO] Auto search is disabled.
tg@:~$

Started ekos with the profile set to remote/localhost connecting to the drivers
Examined the log again:
tg@:~$ cat 2020-06-05.islog
2020-06-05T21:06:35: MoonLite: [INFO] Auto search is disabled.
2020-06-05T21:07:21: MoonLite: [INFO] Detected firmware version 2.0
2020-06-05T21:07:21: MoonLite: [INFO] MoonLite is online. Getting focus parameters...
2020-06-05T21:07:21: MoonLite: [INFO] MoonLite is online.
2020-06-05T21:07:21: MoonLite: [INFO] MoonLite parameters updated, focuser ready for use.
2020-06-05T21:07:21: MoonLite: [INFO] Loading device configuration...
2020-06-05T21:07:21: MoonLite: [INFO] Device configuration applied.
2020-06-05T21:07:22: ZWO CCD ASI1600MM Pro: [INFO] Setting intital bandwidth to AUTO on connection.
2020-06-05T21:07:22: ZWO CCD ASI1600MM Pro: [INFO] CCD is online. Retrieving basic data.
2020-06-05T21:07:22: ZWO CCD ASI1600MM Pro: [INFO] The CCD Temperature is 0.000
2020-06-05T21:07:22: ZWO CCD ASI174MM Mini: [INFO] Setting intital bandwidth to AUTO on connection.
2020-06-05T21:07:22: ZWO CCD ASI174MM Mini: [INFO] CCD is online. Retrieving basic data.
2020-06-05T21:07:22: ZWO CCD ASI174MM Mini: [INFO] The CCD Temperature is 28.600
2020-06-05T21:07:22: ZWO CCD ASI1600MM Pro: [INFO] Loading device configuration...
2020-06-05T21:07:22: ZWO CCD ASI1600MM Pro: [INFO] Upload settings set to client only.
2020-06-05T21:07:23: ZWO CCD ASI1600MM Pro: [INFO] Device configuration applied.
2020-06-05T21:07:23: ZWO CCD ASI1600MM Pro: [INFO] World Coordinate System is enabled.
2020-06-05T21:07:23: ZWO CCD ASI174MM Mini: [INFO] Loading device configuration...
2020-06-05T21:07:23: ZWO CCD ASI174MM Mini: [INFO] Upload settings set to client only.
2020-06-05T21:07:23: ZWO CCD ASI174MM Mini: [INFO] Device configuration applied.
tg@:~$

Mach1, TS86SDQ, ASI071, ASI174, OAG, focusPro

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

3 months 2 weeks ago
El Corazon
Platinum Boarder
Platinum Boarder
Posts: 853
Karma: 3
More
Some help with understanding the basics #55135

wotalota wrote: Reading through the entries under indilib.org/about.html provides a good overview. You generally monitor and control the indi
drivers from a client running locally or remotely. KStars/Ekos can also be run on the Rpi although it will be under powered. More common I think is for a client to communicate remotely to a Rpi running the drivers.


The Pi3 was definitely underpowered, but the Pi4 handles Kstars with plenty of power to spare. I am running the system entirely on the Pi4 under Ubuntu 20.04 and just VNC in from inside the house or from my Phone.
The Pi4 is plenty up to the task, including plate solving (completes with in 8 seconds on average).
Jo

Atlas Pro AZ-EQ, ASI1600MM-Pro, ASI120MM-S, ES102ED, WO-Z61, Nikon D3300, ASI-EFW, ZWO LRGB,Ha,O3,S2 filter set

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

3 months 2 weeks ago
msacco
Fresh Boarder
Fresh Boarder
Posts: 14
More
Topic Author
Some help with understanding the basics #55271
That helped me so much guys, thanks a lot for the help! Much appreciated :)

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

Time to create page: 0.778 seconds