×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Preferred order for chaining indiservers

  • Posts: 8
  • Thank you received: 0
Hi,

I'm just starting my deploy of indi on a raspberry pi for my set up, but I'm starting to think that putting two of them in place would be better, as to reduce cabling and potential tangles of wires as the scope moves. My current idea is:

Pi 1 on scope, with gphoto, V4L2 (Pi cam), and focuser (DIY, when I get the chance)
Pi 2 on mount with an astroeq/eqmod device

My question is, which is best to act as primary? If Pi 2 is the primary, does all network traffic (ie, all those photos) go through from Pi1->Pi2->Ekos? But if I make Pi 1 primary, is there an issue with latency for commands to the astroeq?

I'd be running both of them from their own power source, and possibly wifi connections to remove even more cabling. If I do it this way, only the Dec motor cable runs the risk of any tangles. And everything should be nice and neat.

Or am I over thinking this? Would there ever be a risk of getting cables tangled and its easier to run them all from one Pi?
8 years 2 weeks ago #7634

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

I would select Pi 1 as primary.

I have a lot of equipment, but I'm using 5 meter active USB extension cable to connect all the equipment to a USB hub which is then connected to Odroid. I have no problems at all with cable getting tangled since there is quite a bit of leeway.
8 years 2 weeks ago #7639

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

  • Posts: 8
  • Thank you received: 0
Cool, thanks.

Yeah, figured I could just use long cables, but I like things to be neat and tied out of the way. :)

Hopefully getting the mechanical parts for my mount and astroeq, and just about to dust off the old 3d printer to make some parts to modify my finder scope into a picam/guider.

All just in time for bad viewing over summer! :P
8 years 2 weeks ago #7641

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

Time to create page: 0.596 seconds