Agricultural IoT in Rural Australia: LoRaWAN and Satellite Sensor Gateways

Separate the local radio from backhaul

LoRaWAN can connect low-rate field sensors to a local gateway; a satellite terminal can then carry gateway traffic to an application or network server. This is different from a sensor communicating directly with a satellite. A drawing that connects every LoRa sensor straight to a broadband constellation misrepresents the architecture.

Water levels, soil measurements and equipment states often need only short periodic messages. The challenge is reliable delivery, battery life and coverage across terrain rather than raw bandwidth. Survey antenna placement and seasonal vegetation, and keep sensor sampling aligned with the actual decision being supported.

Estimate airtime and payload

Suppose 100 sensors each send a 24-byte application payload every 15 minutes. That is 230,400 payload bytes per day before LoRaWAN, IP, encryption and retransmission overhead. The satellite data volume may be modest, yet the gateway and terminal can still consume significant energy continuously. An always-on broadband terminal is not automatically the best fit for a tiny telemetry workload.

Airtime depends on radio parameters and message size, not just byte count. Confirm regional channel plans and access constraints. Avoid excessive confirmed messages or downlink dependence in a dense sensor deployment.

Buffer and secure

Where supported by the chosen architecture, keep bounded local queues and preserve measurement timestamps through backhaul outages. Protect device keys and use unique device identities. A gateway that forwards traffic does not eliminate the need for correct network-server security and application authorisation.

Field acceptance

Walk the actual paddocks and structures, then test after weather and vegetation changes. Measure missed reports, battery demand and delivery delay instead of merely noting signal strength. Make alerts tolerant of a single missed sample but explicit when a sensor stays silent. Plan physical access for battery replacement and identify which operational alarms need a separate safety-rated channel.

From concept to acceptance

Worked design exercise

The 100-sensor example produces about 230 kB of daily application payload. If an always-on gateway and backhaul draw a combined 40 W, they consume 960 Wh per day despite the tiny data volume. A lower-power backhaul or scheduled connectivity may therefore materially improve autonomy if the application can tolerate delayed delivery.

Test whether the chosen gateway/server design supports outages and reconnects without losing join state or queued measurements. Confirm the maximum acceptable alarm delay with the farm operator; do not apply a daily upload schedule to a problem that requires a prompt response.