Overview
This section contains Dragino Mesh product documentation.
Dragino Mesh is a private LoRa mesh network for battery-powered sensor nodes. It runs on the STM32WL / LoRa-E5 platform and is based on Meshtastic firmware with Dragino-specific changes. Unlike a LoRaWAN star network, where every node talks directly to a gateway, mesh nodes relay each other's packets so data can travel several hops to reach a gateway node without every node being in direct radio range.
Applies to: Dragino Mesh Node products: SN50v3-MS, S31B-MS, SE01-MS, SPH01-MS, LMS01-MS, SDI-12-MS, CPL03-MS, SVC01-MS
Firmware: Dragino MeshNode firmware based on Meshtastic LoRa technology
Network: Dragino private LoRa Mesh network
| Category | Description |
|---|---|
| Quick Start of Mesh IoT Network | Step-by-step guide to deploy your first mesh network |
| Frequency Plan | Dragino Mesh Node use below default Frequency Plan |
| Mesh End Node | Mesh sensor nodes, including SN50V3-MS and S31B-MS |
| Mesh Edge Gateway | Mesh edge gateway documentation |
| FAQ | Frequently Asked Questions |
| Developer Instruction | Firmware customization, compiling, and flashing guides |
1. Introduction
1.1 What is Dragino Mesh?
Dragino Mesh turns a Dragino sensor node into a member of a self-forming LoRa mesh. A node can send data directly to a Mesh gateway or relay it through other nodes that are awake, so not every node must have a direct connection to the gateway. The Mesh gateway collects the data and provides it to users or upper-layer applications. No cellular network, SIM card, or internet connection is required for node-to-node communication.
To deploy your first network, follow the Quick Start of Mesh IoT Network; for troubleshooting, see the FAQ; for building or modifying firmware, see the Developer Instruction.
1.2 Key features
- Off-grid: node-to-node communication needs no cellular network, SIM card, or internet connection.
- No LoRaWAN infrastructure: no LoRaWAN gateway and no network server (TTN / ChirpStack) are required.
- Multi-hop range: data reaches the Mesh gateway even when a node is out of its direct radio range, by relaying through other nodes that are awake.
- Low power: enrolled nodes follow a scheduled, time-aligned wake-up-and-send cycle (≈ 30 min by default) and sleep in between.
- Private, enrolled network: nodes are added to the Mesh gateway and enrolled into a private Dragino network; only enrolled nodes exchange business data.
- No radio configuration needed: Dragino supplies fixed-frequency versions for different countries or regions, so users do not need to configure radio parameters themselves.
1.3 Typical applications
- Off-grid or private sensor networks in areas without LoRaWAN coverage.
- Agriculture and environmental monitoring, including soil moisture, EC and temperature, soil pH, or leaf wetness, using the RS485 / SDI-12 Mesh models.
- Remote or industrial sites where running a LoRaWAN gateway and network server is impractical.
- Extending sensor reach beyond a single radio hop by relaying through intermediate nodes.
2. How Dragino Mesh works
2.1 How a LoRa mesh works
Every node shares the same radio parameters (region, frequency, bandwidth, spreading factor). A node only hears traffic from nodes that use the same values. When a node transmits, nearby nodes rebroadcast the packet so it reaches farther.
Before rebroadcasting, a node listens for a short moment to check whether another node has already relayed the same packet; if it has, the node does not rebroadcast it. This "managed flooding" lets a packet travel outward hop by hop without every node re-sending every copy.
A hop limit caps how many times a packet is rebroadcast. Each relay decrements it; at zero the packet is no longer forwarded. Dragino business data is sent with a hop limit of 3.
A single Mesh gateway (Dragino node running the gateway firmware) is the collection point. It provides the received data to users or upper-layer applications:
While a node is asleep, it cannot receive or relay data in real time. Mesh coverage therefore depends not only on the number of nodes, but also on node wake-up times, installation positions, antenna heights, obstructions, and Mesh gateway coverage.
2.2 Network roles and components
| Component | Role |
|---|---|
| Mesh Node | A battery-powered Dragino sensor node installed at the deployment site. Before enrollment, it does not take part in normal business-data communication or relaying; it only sends enrollment requests (internally, the Client-Mute role). After enrollment, it collects site data, sends it to the Mesh gateway through the network, and can relay other nodes' packets while awake (the Client role). |
| Mesh gateway node | The management and data reception device for the entire Mesh network. It adds devices, handles enrollment, receives node data, sends configurations, and provides data to users or upper-layer applications. |
| Gateway management interface | The device management pages of the Mesh gateway, accessed from a computer or management terminal. Used to add nodes (with their Dev EUI and App Key), check enrollment status, and access the received data. |
[Mesh photo family]
2.3 Frequency and regions
Every node must use the LoRa frequency and power allowed in your country, and the nodes and the Mesh gateway must use the same Region. Dragino supplies fixed-frequency versions for different countries or regions, so users do not need to configure radio parameters themselves. The factory default is EU868. All regions use the same LONG_FAST modem preset (SF11 / BW 250 kHz), so only the frequency and power change from one region to another. For the full list of regions, frequencies, and per-country shipping profiles, see the Frequency Plan page.
2.4 Dragino Mesh vs. Dragino LoRaWAN
| Dragino Mesh | Dragino LoRaWAN | |
|---|---|---|
| Topology | Mesh (multi-hop, nodes relay) | Star (node → gateway direct) |
| LoRaWAN gateway required | No | Yes |
| Network server required (TTN/ChirpStack) | No | Yes |
| Node roles | Unenrolled node (Client-Mute) / enrolled node (Client) / Mesh gateway | End node only |
| Reach beyond radio range | Yes, via other nodes | No |
| Typical use | Off-grid / private sensor networks | Standard LoRaWAN deployments |
3. Models
3.1 Compatible models
All Mesh models share the same base platform (STM32WLE5JC MCU with an integrated SX126x-class radio). Each sensor variant is a separate firmware build.
| Model | Measured parameter(s) | Firmware status |
|---|---|---|
| SN50v3-MS | Base / generic node (no dedicated onboard sensor) | Available |
| S31B-MS | Temperature & humidity (external SHT31 probe) | In development |
| SE01-MS | Soil moisture, EC & soil temperature (RS485 probe) | In development |
| SPH01-MS | Soil pH & temperature (RS485 probe) | In development |
| LMS01-MS | Leaf wetness & leaf temperature (RS485 probe) | In development |
| SDI-12-MS | SDI-12 sensor interface | In development |
| CPL03-MS | (to be confirmed) | In development |
| SVC01-MS | (to be confirmed) | In development |
Each model has its own product page under Mesh End Node, where datasheet, configuration, wiring, and profiles live.
3.2 Related pages
| Category | Description |
|---|---|
| Mesh End Node | Mesh sensor nodes (SN50v3-MS, S31B-MS, and other MS series products). |
| Mesh Edge Gateway | Mesh gateway products, gateway setup, and bridge-related documentation. |