MA01-LN Multi-Gateway Mesh Network
Configuration guide for deploying multiple gateways in the same Mesh network, including MA01-LN and other Dragino Mesh gateway models.
1. Introduction
MA01-LN supports deploying multiple gateways working together in the same Mesh network. Mesh Node sensor data received by any gateway can be forwarded to the LoRaWAN server.
Multiple-gateway deployment is recommended when Mesh Nodes are spread over a wide area or installed behind obstacles. A node only needs to be received by one available gateway for its data to be reported.
A single Mesh network supports up to 4 gateways at the same time. Each gateway is assigned a group number via AT+MNGROUP=0/1/2/3 (valid values: 0–3, default: 0). Gateways cooperate according to their group assignment:
- Gateways in the same group: discover each other, verify trust, and synchronize the node table, forwarding data jointly. Sensor data received by any gateway in the group will be reported, while the remaining gateways in the group serve as backups, improving reception coverage and preventing data loss caused by a single gateway failure or poor signal.
- Gateways in different groups: do not synchronize node tables; each group only registers and reports the batch of nodes it manages. Each group transmits data of its own nodes independently, thereby increasing the overall uplink throughput of the entire network within a given time period.
In regions with duty-cycle restrictions (e.g., EU868, RU864), the transmission capacity of a single gateway is limited by airtime. Assigning nodes to gateways in different groups can multiply the total throughput of the entire area.
Typical deployment example: Gateways A and B are set to group 0 and jointly manage the first batch of nodes; Gateways C and D are set to group 1 and jointly manage the second batch. A and B provide coverage redundancy for each other, and so do C and D, while the two groups report different nodes without duplication.
The Mesh Network ID used by MA01-LN is a 32-byte network private key. It is displayed and configured as 64 HEX characters. Keep this value private.
2. Configure the First MA01-LN Gateway
The first gateway is used as the reference gateway for the Mesh Network ID and the initial node table.
Step 1. Register the first MA01-LN in the LoRaWAN server and configure its OTAA keys.
Step 2. Power on MA01-LN and wait until its green LED turns on for about 5 seconds.
Step 3. Use the mobile BLE APP to connect to MA01-LN.
Step 4. Send AT+MNID=? to query the Mesh Network ID from the first gateway.
Step 5. Click “Add Device” and scan the QR code on the Mesh Node package to add Mesh Nodes.
3. Configure Additional MA01-LN Gateways
Each additional gateway must use its own LoRaWAN OTAA keys, but it must use the same Mesh Network ID as the first gateway.
Step 1. Register the additional MA01-LN in the LoRaWAN server.
Step 2. Use the mobile BLE APP to connect to the second MA01-LN.
Step 3. Use AT+MNID= to configure the same Mesh Network ID copied from the first gateway.
Step 4. Reboot or wait for a while.
The BLE APP can save the Mesh Network ID generated by the first connected MA01-LN.
When the APP connects to another MA01-LN, the same Mesh Network ID can be configured to that gateway so that it joins the same Mesh network.
4. Add Mesh Nodes and Synchronize the Node Table
A Mesh Node can be added from any trusted gateway. After gateways verify each other, the node table can be synchronized between gateways.
When two gateways are verified and their node table are different, MA01-LN can exchange node table information. Complete node records include NodeID, DevEUI, AppKey, record flags, and last seen time.
5. Change Mesh Network ID in a Multi-Gateway Network
Step 1. Make sure the gateways are powered and have already saved the same old Mesh Network ID.
Step 2. On one gateway, use AT+MNID= to set the new 64 HEX Mesh Network ID.
Step 3. Wait 1-2 minutes for MA01-LN to finish the network migration process.
If a Mesh Node is sleeping, it will complete migration only after it restarts.
6. Work with Other Mesh Gateway
MA01-LN can work with other Dragino Mesh gateway models, such as LPS8v2. All gateways must use the same Mesh Network ID, which is also called network private key.
Step 1. Configure the first gateway.
Step 2. Read the Mesh Network ID from the first gateway.
Step 3. Configure the same Mesh Network ID into each later gateway.
Step 4. After the gateways are powered on, they can work in the same Mesh network according to the gateway features supported by each model.
Step 5. Add Mesh Nodes to the LPS8 series gateway and MA01-LN.
7. FAQ
7.1 Node table does not synchronize
Node table synchronization works only between MA01-LN gateways. LPS8v2 and other gateway models do not exchange node table records with MA01-LN. For MA01-LN-to-MA01-LN use, confirm that all gateways use the same Mesh Network ID and have been powered on.
7.2 Mesh Network ID changed but gateways are not synchronized
This program only works between MA01-LN gateways. Other gateway models will not receive a new Mesh Network ID / network private key automatically from MA01-LN. After changing the Mesh Network ID, manually configure the same new ID on other gateway models. For MA01-LN-to-MA01-LN use, confirm that all gateways use the same Mesh Network ID before it changes and have been powered on.
7.3 Do not configure different Mesh Network IDs on several gateways at the same time
A Mesh Network can only keep one Mesh Network ID. If users configure different Mesh Network IDs on several gateways, MA01-LN will not adopt the configuration, but reuse the previous Mesh Network ID.
7.4 Logs show “mesh rx encrypted/undecoded……”
It means MA01-LN recognized another MA01-LN while they use different Mesh Network IDs. If users plan to make them work in the same network, use BLE APP to set the same Mesh Network ID for them.