How to Maximize LoRaWAN Range with TX Power, DR, and ADR Settings
Updated: Nov 5
LoRa is famous for long-distance communication, but range does not come from the radio chip alone. In real deployments, the same end node can perform very differently depending on its transmit power, data rate, antenna, gateway location, and server settings.
If a node joins the network near the gateway but fails at the edge of a farm, factory site, hill, or city block, the first place to look is usually the software configuration. Three settings matter most: TX Power, Data Rate, and ADR.
This guide explains how those settings affect distance, how to set a node for maximum range, and what trade-offs come with that choice.

LoRaWAN range starts with link budget
A LoRaWAN link works when the gateway can detect the weak radio signal sent by the end node. The distance you get depends on the link budget, which is the gap between transmitted power and the weakest signal the receiver can still understand.
Several things affect that budget:
Output power from the end node
Spreading Factor and bandwidth
Antenna gain and antenna placement
Cable and connector losses
Gateway receiver quality and installation height
Terrain, buildings, trees, metal structures, and noise
Local radio rules for the selected frequency band
The software settings do not remove physical limits, but they can make the radio use its strongest long-range mode. For a node at the edge of coverage, that can be the difference between stable uplinks and missed packets.
The key idea is simple:
For maximum distance, use the highest allowed TX power and the lowest LoRaWAN data rate for the selected region.
In many AT-command based LoRaWAN modules, that means:
```text
AT+ADR=0
AT+DR=0
AT+TXP=0
```
Those commands look simple, but each one needs the right context.
TX Power controls how strongly the node transmits
`TXPower` is the output power setting of the end node. In many modules, the command is:
```text
AT+TXP
```
A common long-range setting is:
```text
AT+TXP=0
```
In LoRaWAN, `TXP=0` usually means the highest allowed transmit power index for the region and device configuration. It does not mean 0 dBm.
That detail matters. The same `AT+TXP=0` command can produce different real output levels in different regional frequency plans.
Frequency band | Typical module output when `TXP=0` | Notes |
EU868 | 14 dBm | Often shown with a 2 dBi antenna assumption |
US915 | 20 or 22 dBm | Depends on module capability and regional limits |
AS923 | 14 dBm | Often shown with a 2 dBi antenna assumption |
These values are common examples, not universal guarantees. Always check the module manual and the LoRaWAN Regional Parameters document used by the firmware.
Why higher TX power improves distance
Higher transmit power makes the uplink signal stronger when it leaves the antenna. A stronger signal can survive more path loss before it drops below the gateway receiver sensitivity.
This helps in hard locations such as:
Nodes behind trees or crops
Sensors inside plastic or fiberglass enclosures
Devices near the ground
Long rural links
Sites with partial obstruction between node and gateway
TX power alone does not solve every range problem. A poor antenna, bad connector, or metal enclosure can waste the extra power before the signal ever leaves the device.
Do not ignore legal limits
LoRaWAN devices use license-free spectrum, but license-free does not mean rule-free. Each region defines limits for transmit power, duty cycle, dwell time, channel plan, and other behavior.
For example, EU868 and US915 use different channel plans and limits. That is why the same command index can map to different actual power levels.
The safest approach is:
Select the correct regional frequency band in firmware.
Use the manufacturer’s AT command guide for that region.
Confirm the actual output power table.
Keep the antenna gain within the allowed limit.
Test in the real deployment location.
Data Rate decides the spreading factor and bandwidth
LoRaWAN `DR`, or Data Rate, is not only a speed setting. It represents a combination of modulation parameters, mainly Spreading Factor and Bandwidth.
In most common LoRaWAN regional plans, the lowest data rate is:
```text
AT+DR=0
```
For maximum range, `DR=0` is usually the setting you want.

Why lower DR reaches farther
A lower data rate usually uses a higher Spreading Factor. A higher Spreading Factor makes the signal easier for the gateway to decode when the received power is very low.
The trade-off is airtime. The radio stays on longer to send the same payload.
That affects:
Battery life
Channel use
Network capacity
Downlink timing
Packet collision risk in dense deployments
So, `DR=0` is excellent for maximum distance, but it is not always the best everyday setting for every device. It is best for nodes that truly need long reach, send small payloads, and transmit infrequently.
Example long-range DR settings by region
When `AT+DR=0` is used, the actual LoRa parameters can vary by region.
Frequency band | Data rate index | Spreading Factor | Bandwidth |
EU868 | DR0 | SF12 | 125 kHz |
US915 | DR0 | SF10 | 125 kHz |
AS923 | DR0 | SF12 | 125 kHz |
This table shows why regional context matters. In EU868 and AS923, `DR0` commonly means SF12 at 125 kHz. In US915, `DR0` commonly means SF10 at 125 kHz.
SF12 can often reach farther than SF10 under the same conditions, but US915 also allows different transmit power behavior. You cannot compare one number in isolation. TX power, channel plan, gateway, antenna, and local rules all work together.
ADR can change TX power and DR after deployment
ADR means Adaptive Data Rate. When ADR is enabled, the network server can ask the end node to change its data rate and transmit power based on link quality.
On many devices, ADR is controlled with:
```text
AT+ADR
```
ADR enabled:
```text
AT+ADR=1
```
ADR disabled:
```text
AT+ADR=0
```
Many modules ship with ADR enabled by default.
ADR is useful because it can reduce airtime and battery use for nodes with strong links. If a sensor is close to a gateway, it does not need SF12 and maximum power. The server can move it to a faster data rate or lower TX power.
That helps the whole network. Shorter airtime means less chance of packet collisions.
Why ADR can reduce long-distance performance
ADR can be a problem when your goal is maximum range at all times. If the server decides the link is strong enough, it may tell the node to use a higher data rate or lower transmit power. That can reduce margin.
This is not a bug. It is what ADR is designed to do.
For a fixed node with a stable radio path, ADR often works well. For a node at the edge of coverage, in a changing environment, or moving between locations, ADR can make behavior harder to predict.
Common examples include:
Tracking devices
Portable sensors
Agricultural sensors hidden by crop growth
Nodes affected by seasonal foliage
Devices installed close to the ground
Sensors installed indoors near thick walls
For maximum distance testing, turn ADR off so the node keeps the settings you choose.
Use these AT commands for maximum distance
For many AT-command based LoRaWAN end nodes, the basic long-range configuration is:
```text
AT+ADR=0
AT+DR=0
AT+TXP=0
```
Here is what each command does.
Command | Purpose | Range effect |
`AT+ADR=0` | Disables network-controlled data rate and power changes | Keeps the node in the chosen long-range mode |
`AT+DR=0` | Selects the lowest regional data rate | Uses the longest-reach modulation available in that plan |
`AT+TXP=0` | Selects the highest regional TX power index | Sends with the strongest allowed module output |
This is the usual software starting point for maximum LoRaWAN range.

Confirm the settings after reboot
Some modules save AT settings immediately. Others require a save command. Some reset settings after a firmware update or power cycle.
After setting the node, check the configuration again:
```text
AT+ADR?
AT+DR?
AT+TXP?
```
If the module supports a full configuration print command, use it and record the result before field testing.
Join behavior can still matter
Range problems are not only uplink problems. OTAA join requests need a working uplink and a downlink response from the network.
If a node can send uplinks after it has joined but struggles to join at long distance, check:
Join channel configuration
Gateway downlink capability
RX1 and RX2 settings
Regional downlink data rate rules
Server-side device profile
Antenna and gateway placement
Maximum uplink settings help, but the network still needs to answer at the right time and frequency.
Know the trade-offs before forcing maximum range
Using maximum TX power and minimum DR is effective, but it has costs. A long-range profile should be used with intention.
Battery life can drop
Higher TX power uses more current. Lower DR increases airtime. Together, they make each message more expensive for the battery.
For a sensor that sends one short payload every few hours, this may be acceptable. For a device that sends often, the battery impact can be significant.
Network capacity can suffer
Low data rates occupy the channel longer. On a shared LoRaWAN network, too many SF12 devices can create congestion.
This matters most when many nodes use the same gateway area. If every device uses maximum range settings even when it is close to a gateway, the network becomes less efficient.
Duty cycle and dwell time limits still apply
Some regions limit how long a device may transmit. Low data rates increase airtime, so a device can reach those limits sooner.
If messages stop or become delayed during testing, do not assume the radio failed. Check the regional rules, firmware limits, and server logs.
Use a simple field test process
Software settings are only useful if they hold up outdoors. A structured test can save hours of guessing.
Start with a baseline near the gateway
Place the node close to the gateway and confirm:
The device joins successfully
Uplinks arrive on the server
RSSI and SNR values appear in logs
The expected frequency band is active
ADR, DR, and TXP settings match the test plan
Do not start range testing until the basic connection is stable.
Move outward in stages
Increase distance gradually. At each test point, send several uplinks and record:
Distance from gateway
Gateway ID
RSSI
SNR
Data rate
TX power index
Packet success rate
Antenna orientation
Installation height
A single successful packet does not prove a stable link. Look for repeated success over time.
Test at real installation height
A node tested at chest height may work better than the same node installed 12 inches above the ground. Height changes Fresnel clearance, ground absorption, and obstruction.
If the final device will be mounted low, test it low. If it will be inside a box, test it inside the box.
Do not forget antenna and gateway placement
The requested settings are software-side controls, but physical installation can make or break the result.
Before blaming the module, check these items:
Use an antenna tuned for the correct frequency band.
Keep the antenna outside metal enclosures.
Avoid coiling antenna cables tightly.
Use low-loss cable for long antenna runs.
Mount gateways high and clear of nearby metal.
Keep the node antenna vertical when using common vertical gateway antennas.
Avoid placing the node directly against batteries, solar panels, or large metal parts.
A well-placed 14 dBm node can outperform a poorly installed higher-power node.

Recommended starting profiles
Use these profiles as practical starting points. Adjust them after checking local rules, module documentation, gateway logs, and field results.
Scenario | ADR | DR | TXP | Reason |
Maximum range test | Off | `DR=0` | `TXP=0` | Locks the node into long-range behavior |
Fixed node far from gateway | Usually off or carefully managed | Low DR | High TX power | Keeps stronger link margin |
Fixed node near gateway | On | Server-managed | Server-managed | Saves airtime and battery |
Mobile node | Off | Conservative low DR | High enough for coverage | Avoids ADR choices based on changing paths |
Dense network with many nodes | Mixed | Use only as low as needed | Use only as high as needed | Reduces channel congestion |
For a first long-distance test, the most direct command set remains:
```text
AT+ADR=0
AT+DR=0
AT+TXP=0
```
Then verify the real values behind those indexes for your frequency band.
The practical takeaway
To maximize LoRaWAN distance, start with the radio settings that give the node the strongest link budget: disable ADR, select the lowest data rate, and use the highest allowed TX power index.
In AT command form, that usually means:
```text
AT+ADR=0
AT+DR=0
AT+TXP=0
```
Those settings are not magic. They increase airtime, use more energy, and can reduce network capacity if used everywhere. The best approach is to use them for range testing and edge-of-coverage nodes, then relax the settings where the link has enough margin.
Set the correct regional band, confirm what each command maps to in real dBm and LoRa parameters, and test from the actual installation position. That combination gives you the clearest path to longer, more reliable LoRaWAN links.
Need help with your application?
ProSense Instruments - explore instruments, sensors, data loggers and test equipment.
ProSense Solutions - discuss complete monitoring and automation systems.
ProSight Software - explore cloud dashboards, alarms and reporting. Device integration must be confirmed for your application.
Instrument enquiries: sales@prosenseinstruments.com.au | 1800 560 854
Project enquiries: sales@prosense.com.au. Software enquiries: info@prosightsoftware.com.




Comments