Python Forum
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Comms for multiple nodes.
#1
I need a socket server/client app which is a little unusual and I'm struggling to get my head around how it would work.

I have 128 nodes, all mini board pi Raspians, 8 stacks of 16 pis. Within each 2x stacks are 16 fan controllers. If a pi gets hot it needs to send a message to a controller to turn on the fan. The fan controller pis also need to be clients and need the ability to turn the fan on. I hope this is making sense.

I've had this working almost perfectly with a serial token ring, but now and then I get a rogue serial corruption that breaks the loop.

So, I'm looking for a socket server/client app to do the same. However, each pi needs to be a server and a client with the ability to accept messages from any other pi, and the ability to send to any other pi.

So an app with a server and client on separate threads seems feasible, but it boggles my head a little. Or can anyone think of a much simpler idea?

Many thanks.
Reply
#2
why not use some solid state relays that allow high current through for running the fan?
Then you can do it all with one pi that will never get hot!
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  How can I rearrange df as the nodes index in pytorch geometric manner? uqlsmey 0 521 Jul-31-2023, 11:28 AM
Last Post: uqlsmey
  Python3 binary tree not replacing parent nodes with child nodes Aspect11 0 1,794 Sep-23-2020, 02:22 PM
Last Post: Aspect11
  read individual nodes from an xml url using pandas mattkaplan27 5 2,968 Jul-05-2020, 10:06 PM
Last Post: snippsat
  Modifying anytree Nodes gw1500se 1 2,680 Jun-05-2020, 03:44 PM
Last Post: Gribouillis
  Animate graph nodes inside a function adamG 0 2,963 Sep-23-2019, 11:18 AM
Last Post: adamG
  Randomise network while maintaining topology of nodes using edge-swap approach Tom1988 3 4,154 May-25-2017, 10:59 PM
Last Post: ichabod801

Forum Jump:

User Panel Messages

Announcements
Announcement #1 8/1/2020
Announcement #2 8/2/2020
Announcement #3 8/6/2020