A node is a device that sends and receives data from a nearby gateway. This is where the user can communicate with a network of FDRS gateways using their own sketch. A node can be a sensor (sending data), controller (receiving data), or both.
Sensors load a packet with data, then send the packet to the gateway that they are addressed to.
#include "fdrs_node_config.h"
#include <fdrs_node.h>
void setup() {
beginFDRS(); // Start the system
pingFDRS(2000); // Send ping and wait 2000ms for response
}
void loop() {
loadFDRS(21.0, TEMP_T); // Load a temperature of 21.0 into the queued packet
sendFDRS(); // Send the queued packet
sleepFDRS(60); // Sleep for 60 seconds
}
Controllers register with the gateway they are addressed to, then receive data from it.
#include "fdrs_node_config.h"
#include <fdrs_node.h>
void fdrs_recv_cb(DataReading theData) {
DBG("ID: " + String(theData.id));
DBG("Type: " + String(theData.t));
DBG("Data: " + String(theData.d));
}
void setup() {
beginFDRS(); // Start the system
addFDRS(fdrs_recv_cb); // Call fdrs_recv_cb() when data arrives.
subscribeFDRS(42); // Subscribe to DataReadings with ID 42
}
void loop() {
loopFDRS(); // Listen for data
}
The unique ID that the node will use when sending sensor values. Can be any integer 0 - 65535. Nodes are not necessarily tied to this parameter. They can be subscribed to up to 256 different IDs or send using several different IDs.
The UNIT_MAC
of the gateway that this device will be paired with.
Initializes FDRS, powers up the sensor array, and begins ESP-NOW and/or LoRa.
Sends a ping request to the device's paired gateway with a timeout in ms. Returns the ping time in ms and displays it on the debugging console.
Loads some data into the current packet. 'data' is a float, 'type' is the data type (see below), and 'id' is the DataReading id.
Same as above, but the 'id' is preset to the node's READING_ID
.
Sends the current packet using ESP-NOW and/or LoRa. Returns true if packet is confirmed to have been received successfully by the gateway.
Queues the current packet to be sent asynchronously (in the background). Be sure to use loopFDRS()
to ensure the system can process the packet. Returns true if packet is successfully added to queue.
Time to sleep in seconds. If DEEP_SLEEP
is enabled, the device will enter sleep. Otherwise it will use a simple delay()
.
Initializes controller functionality by selecting the function to be called when incoming commands are received. If using LoRa, the controller will automatically receive any packets sent with broadcastLoRa(), provided they were sent by the paired gateway. ESP-NOW requires the device to register with its gateway before it will receive incoming commands. This is done automatically, and the ESP-NOW node will continue recieving data until the paired gateway is reset. A maximum of 16 ESP-NOW controllers can receive data from a single gateway. There is no limit to how many LoRa controllers can listen to the same gateway.
Sets the device to listen for a specific DataReading id. When a DataReading with id sub_id
is received, the callback function will be called and given the full DataReading as a parameter.
Removes sub_id
from subscription list.
Always add this to loop()
to handle the controller's listening capabilities.
Enables/disables ESP-NOW.
Enables/disables LoRa.
This definition enables debug messages to be sent over the serial port. If disabled, no serial debug interface will be initialized.
Sets the level of verbosity in debug messages. '0' (default) shows only the most important system messages, '1' will show additional debug messages for troubleshooting, and '2' will show all messages, including those used in development. Much gratitude to Jeff Lehman for this feature!
If enabled, device will enter deep-sleep when the sleepFDRS() command is used. If using ESP8266, be sure that you connect the WAKE pin (GPIO 16) to RST or your device will not wake up.
If defined, power control will bring a GPIO pin high when FDRS is initialized. This is useful for powering sensors while running on battery.
Enables LoRa packet acknowledgement. The device will use CRC to ensure that the data arrived at its destination correctly. If disabled, sendFDRS()
will always return true when sending LoRa packets.
Thanks Jeff Lehman for this feature!
The name of the RadioLib module being used. Tested modules: SX1276, SX1278, SX1262.
LoRa chip select pin.
LoRa reset pin.
LoRa DIO pin. This refers to DIO1 on SX127x chips and DIO1 on SX126x chips.
For SX126x chips: LoRa BUSY pin. For SX127x: DIO1 pin, or "RADIOLIB_NC" to leave it blank.
LoRa TX power in dBm.
Enable this if using the SX126x series of LoRa chips.
Built on the ThingPulse OLED SSD1306 Library
The message to be displayed at the top of the screen.
OLED I²C pins.
OLED reset pin. Use '-1' if not present or known.
The callback function is executed when data arrives with an ID that the controller is subscribed to. Inside of this function, the user has access to the incoming DataReading. If multiple readings are received, the function will be called for each of them. While you should always be brief in interrupt callbacks (ISRs), it's okay to do more in this one.
For the moment, my thought is to reserve the first two bits of the type. I might use them in the future to indicate the data size or type (bool, char, int, float, etc?). This leaves us with 64 possible type definitions. If you have more types to add, please get in touch!
#define STATUS_T 0 // Status
#define TEMP_T 1 // Temperature
#define TEMP2_T 2 // Temperature #2
#define HUMIDITY_T 3 // Relative Humidity
#define PRESSURE_T 4 // Atmospheric Pressure
#define LIGHT_T 5 // Light (lux)
#define SOIL_T 6 // Soil Moisture
#define SOIL2_T 7 // Soil Moisture #2
#define SOILR_T 8 // Soil Resistance
#define SOILR2_T 9 // Soil Resistance #2
#define OXYGEN_T 10 // Oxygen
#define CO2_T 11 // Carbon Dioxide
#define WINDSPD_T 12 // Wind Speed
#define WINDHDG_T 13 // Wind Direction
#define RAINFALL_T 14 // Rainfall
#define MOTION_T 15 // Motion
#define VOLTAGE_T 16 // Voltage
#define VOLTAGE2_T 17 // Voltage #2
#define CURRENT_T 18 // Current
#define CURRENT2_T 19 // Current #2
#define IT_T 20 // Iterations
#define LATITUDE_T 21 // GPS Latitude
#define LONGITUDE_T 22 // GPS Longitude
#define ALTITUDE_T 23 // GPS Altitude
#define HDOP_T 24 // GPS HDOP
#define LEVEL_T 25 // Fluid Level
#define UV_T 26 // UV
#define PM1_T 27 // 1 Particles
#define PM2_5_T 28 // 2.5 Particles
#define PM10_T 29 // 10 Particles
#define POWER_T 30 // Power
#define POWER2_T 31 // Power #2
#define ENERGY_T 32 // Energy
#define ENERGY2_T 33 // Energy #2
typedef struct __attribute__((packed)) DataReading {
float d;
uint16_t id;
uint8_t t;
} DataReading;
Each node in the system sends its data inside of a structure called a DataReading. Its global sensor address is represented by an integer 'id', and each type of reading is represented by a single byte 't'. If a sensor or gateway needs to send multiple DataReadings, then they are sent in an array. A single DataReading.id may have readings of multiple types ('t') associated with it.