Installing a LoRaWAN gateway does not automatically establish reliable coverage or predictable network capacity. Water meters and pressure sensors may be located inside reinforced-concrete chambers or below metal covers, where antenna location, regional frequencies, message intervals and retries all matter. This guide presents a project-engineering method for the ATLAS LoRaGateway LR-1 rather than promising a fixed radius or number of endpoints.
1. Verify the regional band and actual hardware version
EU863–870 commonly uses 868.10, 868.30 and 868.50 MHz as default channels under the applicable LoRaWAN regional parameters. Nevertheless, permitted sub-bands, radio power and duty cycle must be checked against the current regulations in the installation country. Do not assume a European profile can be transferred unchanged to another region.
The LR-1 product information lists several regional band options, not universal simultaneous support in one hardware unit. Match the exact gateway revision, antenna, end-device frequency plan and network-server channel configuration before procurement.
2. Survey link margin, not only map distance
The brochure’s 15 km open-field figure is not a guaranteed city-network radius. Concrete chambers, manhole covers, urban obstructions, antenna orientation, elevation and local interference all affect packet reception. Use real representative locations, including difficult underground meter sites, rather than concentric coverage rings on a map.
Record device location, antenna height, frequency, spreading factor (SF), RSSI, SNR and packet reception for each trial. Account for feeder losses, weatherproofing and surge protection in the physical site design.
3. Worked capacity example: 300 nodes at 15-minute intervals
Suppose 300 meters send once every fifteen minutes: this produces 96 uplinks per meter and 28,800 uplinks per day across the network. Assuming 0.5 seconds of on-air time per packet solely for illustration yields 48 seconds per device per day and an aggregate 14,400 seconds of raw uplink airtime. The aggregate is not elapsed time on a single sequential channel.
Real channel occupancy and collisions depend on payload size, SF mix, bandwidth, channel availability, retransmissions and the concentrator’s simultaneous reception capabilities. A generic “one gateway supports X meters” claim is not a substitute for a traffic and coverage study.
4. ADR, Class A timing and downlink constraints
Adaptive Data Rate (ADR) can adjust data rate and transmit power to improve airtime efficiency and energy usage when conditions are appropriate. Static end devices and changing or subterranean radio environments require different tuning and validation. Lower data rates may increase airtime materially.
Class A nodes normally open limited receive windows after an uplink; a command is not necessarily delivered immediately on demand. Frequent confirmed uplinks, valve operations and large payload updates consume scarce downlink opportunities and may meet regulatory duty-cycle constraints. Define a fail-safe field behaviour for control functions.
5. Power, backhaul and gateway availability
The LR-1 page specifies a 12–24 V, 2 A supply and lists GSM, Ethernet, RS485 and Wi-Fi interface options. Confirm the ports fitted to the quoted hardware version. Distinguish mains failure, cellular outage, backhaul routing failure and network-server availability in monitoring and service procedures.
Choose an appropriate field enclosure, cable glands, grounding/surge protection and backup supply from the site risk assessment. A gateway, LoRaWAN network server and application platform are separate elements; AtlasServer.io integration and commercial entitlement require project confirmation.
6. Pilot acceptance and expansion decisions
A practical illustrative pilot is 20 representative meters over 48 hours, with transmitted and received messages matched per device. If 1,872 of 1,920 expected packets are ingested, observed packet reception is 97.5% in that specific test, not a guaranteed service level for the entire network.
Investigate low-performing locations before ordering additional units: change antenna location, add gateway diversity, change report intervals or consider another bearer. Record endpoint coordinates, traffic rate, protocol versions and acceptance KPIs in the purchase specification.
Frequently asked questions
Will LR-1 always cover 15 km?
No. The figure is an open-field catalogue value; real coverage must be validated on site.
Can one gateway be promised for 300 meters?
Not without field and airtime measurements, traffic assumptions and downlink requirements.
Send ATLAS your proposed LR-1 site map, meter count, reporting interval and backhaul requirements for an engineering review.
Related ATLAS product 1 · Related ATLAS product 2
Traffic, airtime and pilot figures are illustrative; radio compliance and product features must be confirmed for the actual configuration.