×

INDI Library v1.7.6 Released. (27 Feb 2019)

First release of 2019 comes with quite a few new drivers across the board along with significant performance improvements to INDI camera and live streaming performance. Many drivers received significant updates to improve performance & stability, while a few were re-written from scratch to be in line with INDI standards. Here are some of the highlights:

Would an IndiServer Startup Script Work?

  • Posts: 37
  • Thank you received: 10

Would an IndiServer Startup Script Work? was created by werper

I am using two RPIs in distributed networking to split the computing load for my imaging and guiding. I have it working well. However, after my PIs have booted, I need to log into each PI, launch a terminal, and key-in the commands into each PI to start Indi Server and also network from the primary to the secondary PI. Would a start-up script work so I don't have to waste valuable time each time I set-up my rig? OR, is there a way I can write a script and have it sitting on the desktop (as an icon) so I can simply double click on it to run it? ...FYI: I'm pretty much a Linux noob, but have an IT background, so if I'm pointed in the right direction, I can usually make it happen.

Here's the set-up:

Two RPIs, the Primary is called guide, the secondary is called camera, each has a dedicated IP address on an isolated/dedicated network just for my AP rig. The PIs names have been added to the hosts file on each PI and my laptop that runs Kstarts/Ekos.

Step one is to start the camera server on the secondary PI, here is the command I use:
indiserver -v indi_gphoto_ccd

Step two is to start the guide server and connect to the camera server on the Primary PI, here is the command I use:
indiserver "GPhoto CCD"@camera:7624 indi_ieq_telescope indi_qhy_ccd

It is those two commands that would comprise the scripts: one on each PI. Would this work and if so, what's the best way to do it? The ideal solution would be for a seamless boot-up, where I never even have to log into either of the PIs, but again, I'm not sure that's possible...???

Thanks!

Tom
Celestron C8-N
iOptron iEQ45 Pro
Two Stellarmate Rasberry Pis - Distributed
Dedicated WiFi Network
Canon T3i DSLR - Primary Cam
QHY5L-II-M - Guide Cam
Astromania 60 Guide Scope
1 week 6 days ago #37423

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

  • Posts: 141
  • Karma: 2
  • Thank you received: 35

Replied by kengs on topic Would an IndiServer Startup Script Work?

Just install INDI Web Manager on each Pi. It will start automatically and you can configure profiles with different sets of drivers, autostart one of the profiles and manage it via a web browser from your client
www.indilib.org/support/tutorials/162-indi-web-manager.html
Ubuntu 16.04 AMD64 VM, RPi3 Ubuntu Mate 16.04, Windows 10 AMD64, Ubuntu 16.04 AAEON UP Core
Avalon M-Uno, EQ6 Pro, Atik420, ASI1600MM-C, ASI120MM-S, DBK21AU04, ZWO EFW, Optec TCFSi
Vixen R150S, GSO RC8, ST80
The following user(s) said Thank You: knro
1 week 6 days ago #37429

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

  • Posts: 37
  • Thank you received: 10

Replied by werper on topic Would an IndiServer Startup Script Work?

That's fine for one PI, but not two, running distributed. You have to start the servers manually from the terminal, which is what I'm trying to speed up / automate.
Celestron C8-N
iOptron iEQ45 Pro
Two Stellarmate Rasberry Pis - Distributed
Dedicated WiFi Network
Canon T3i DSLR - Primary Cam
QHY5L-II-M - Guide Cam
Astromania 60 Guide Scope
1 week 6 days ago #37430

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

Replied by knro on topic Would an IndiServer Startup Script Work?

Why not? You can specify in Pi#2 remote driver field "GPhoto CCD"@camera:7624

The only thing you need to guarantee is that Pi#1 boots and is running before Pi#2
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
1 week 5 days ago #37436

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

Time to create page: 0.741 seconds