mirror of
https://github.com/timmbogner/Farm-Data-Relay-System
synced 2024-11-08 13:10:29 +00:00
Update README.md
This commit is contained in:
parent
822e7571db
commit
cbcadb1105
@ -1,7 +1,7 @@
|
||||
# <p align="center">Farm Data Relay System
|
||||
##### <p align="center">[***In loving memory of Gay Holman, an extraordinary woman.***](https://www.facebook.com/CFECI/posts/2967989419953119) #####
|
||||
|
||||
The Farm Data Relay System is an easy way to communicate with remote devices without relying on WiFi or LoRaWAN. It is designed to use the ESP-NOW and LoRa protocols to establish lines of low-power, low-cost gateways and repeaters that provide coverage to remote devices. The system can be used to exchange sensor readings or control messages in situations where it would be too difficult or energy-consuming to provide full WiFi/LoRaWAN coverage.
|
||||
The Farm Data Relay System is an easy way to communicate with remote devices without relying on WiFi or LoRaWAN. The system establishes a series of low-power, low-cost access points and repeaters that provide light-weight ESP-NOW and LoRa coverage to remote IOT devices. The system can be used to exchange sensor readings or control messages in situations where it would be too difficult or energy-consuming to provide full WiFi/LoRaWAN coverage.
|
||||
|
||||
FDRS devices are classified into two types: gateways and user nodes. Gateways comprise the infrastructure of the network, moving data in pre-determined directions to provide coverage to all devices. User nodes allow the user to exchange data with the gateways. Each gateway is identified with an 8-bit physical hex address (MAC), while nodes use 16-bit integers to identify datapoints as they move through the system.
|
||||
|
||||
@ -29,10 +29,10 @@ Gateways are modular and configurable ESP32/8266 devices that can perform a vari
|
||||
|
||||
A gateway can be an access point for remote ESP-NOW and LoRa senosrs and controller devices (nodes). If it receives a packet from an unknown ESP-NOW or LoRa address, the gateway infers that these are sensor readings and passes them downstream towards the front-end. Packets originating from the front end can be sent to registered peers and then passed upstream.
|
||||
|
||||
Gateways can also be configured as simple repeaters; passing data from one neighbor directly to another neighbor or vice versa. This can create a data wormhole that will carry packets upstream or downsteam ad infinitum. You can configure your gateways to share data headed upstream with connected peers, which provide them any data being send from the front-end.
|
||||
Gateways can also be configured as simple repeaters; passing data from one neighbor directly to another neighbor or vice versa. This can create a data wormhole that will carry packets upstream or downsteam ad infinitum. You can configure your gateways to share data headed upstream with connected peers, thus providing them with any data being sent from the front-end.
|
||||
|
||||
## Front-end
|
||||
The front-end is the point where the user interacts with FDRS. This could be anything from an microcontroller communicating through UART and displaying data on a screen to your favorite server/database platform logging the data via MQTT.
|
||||
The front-end is the point where the user interacts with FDRS. This could be anything from a microcontroller communicating through UART and displaying data on a screen, to your favorite server/database platform logging the data via MQTT.
|
||||
|
||||
My recommended method of accessing your data is using a Raspberry Pi linked to an FDRS Gateway device via either MQTT or UART (serial-to-USB). Node-RED is my favorite platform for accessing/manipulating data on the front-end, and InfluxDB+Grafana is the dream team for storage and visualization.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user