Controls

Rodread · May 29, 2020, 8:46am

Awww, so tempting, I’m drooling a bit…
Look at all those joysticks…
https://auctions.ramco.uk/auctions/7461/ramco-10217/lot-details/e75c79e1-f514-4ce7-a8a8-abb40099d2dc
It’s mostly just a camera control desk for decommissioning.
Probably a bit over the top for a Windswept and Interesting mobile control station needs.
But if your AWES team is looking for a new desk… £220 bargain

Rodread · May 29, 2020, 9:14am

The more modern way to spend £220 on controlling a kite network is
a small node controller distributed network spread over a few miles

github.com

Wei1234c/Broccoli/blob/master/notebooks/demo/Broccoli_readme_en.md


# Broccoli - distributed task queues for ESP32 cluster
[GitHub repo.](https://github.com/Wei1234c/Broccoli)

Wei Lin  
2018-04-06

![Broccoli](https://raw.githubusercontent.com/Wei1234c/Broccoli/master/jpgs/Broccoli_cluster_cover.gif)

## [Motivations and Goal]
- Building cluster with Raspberry Pi  
  - For those who like DIY, it is very interesting to create a cluster. With the appearance of [Raspberry Pi](https://www.raspberrypi.org/), the cost of building a cluster is drastically reduced and many [examples](https://www.google.com.tw/search?q=raspberry+pi+cluster&tbm=isch&tbo=u&source=univ&sa=X&ved=0ahUKEwiTuYuw4qDaAhWMgLwKHXaMCNkQsAQIUA&biw=1543&bih=732) of using the Raspberry Pi to create clusters can be found on the Internet.  
- Cost and quantity  
  - However, at present, a Raspberry Pi 3 still costs USD 35 or more, if you can build a cluster with a smaller machine, such as [ESP32](https://en.wikipedia.org/wiki/ESP32), so the cost of each node will only costs USD 7 or so. Under the same budget, the lower the cost of a single node is, the more nodes can be, and it will be more ideal for some purposes.  
- Frameworks and common design patterns  
  - There are many existing communication and software platforms, such as Kafka, Dask, Ipython Parallel, Celery, MQTT, etc., which can be used as a mechanism of communication and integration for cluster and distributed systems. There are many common design patterns, for example: controller/master/broker corresponds to nodes/workers/clients, the message queue and message-passing interfaces, and the paradigms of producer/queue/consumer or publisher/topic/subscriber. With these all combined, it is possible to build an elastic and robust computing platform for distributed/parallel operations. [Celery](http://www.celeryproject.org/) is one of the famous examples.  
- Mechanism of Celery  
  - Celery operates in a producer/queue/consumer paradigm. It is used with some suites (eg RabbitMQ, Redis...) which follow the [AMQP](https://www.amqp.org/) protocol. The mechanism is described in details in the [Celery documents](http://docs.celeryproject.org/en/latest/getting-started/index.html). Please also refer to [this]( Https://www.vinta.com.br/blog/2017/celery-overview-archtecture-and-how-it-works/) easy-to-understand articles.  
- Canvas is one of Celery's cores  
  - Celery provides a sub-module called [Canvas](http://docs.celeryproject.org/en/latest/userguide/canvas.html). With Canvas it's easy to organize tasks into workflow and dispatch it all at once to workers for processing. The client only needs to wait for the final result. I was very curious and interested in its souce code.

This file has been truncated. show original

Then get it to control itself over cloud computing with AI & extra controls over your phone.