Built to order

Long-Range LoRa Text Messenger for Off-Grid Communication

This project builds two handheld text-messenger units that talk directly to each other over LoRa radio — no mobile network, no Wi-Fi, no infrastructure. Each unit carries an ATmega328P, a Ra-02 433 MHz LoRa module, an OLED chat display showing messages with live RSSI, and push buttons for composing text, all running from AA batteries. The build demonstrates spread-spectrum long-range communication, addressing and link-quality measurement in a form anyone can hold. Suitable for B.E./B.Tech final-year projects in Electronics, Communication and IoT.

Long-Range LoRa Text Messenger for Off-Grid Communication — project thumbnail preview
More project photos (2)

The problem

When the network goes down — in a disaster zone, on a trek, across a large farm — ordinary messaging dies with it. LoRa exists precisely for that gap: chirp spread-spectrum modulation that trades data rate for kilometres of range at milliwatts of power. This project turns that principle into something you can hold: two identical handheld messenger units, each built around an ATmega328P with a Ra-02 433 MHz LoRa module, an OLED display, three message buttons and an AA battery pack. Compose a short text on Unit A, and it appears on Unit B's screen with the received signal strength beside it. The build covers the full peer-to-peer loop — addressing so each unit knows who a message is for, acknowledgements, RSSI-based link quality, and the low-power behavior that lets such units run for days on batteries.

How it works

  1. The user composes a message on Unit A using the buttons — scrolling presets or entering characters — and presses send.
  2. The ATmega328P frames the text with the destination address and a sequence number, and hands it to the Ra-02 LoRa module.
  3. The module transmits using chirp spread-spectrum modulation at 433 MHz, which resists interference and reaches far at low power.
  4. Unit B's Ra-02 receives the chirps, decodes them, checks the address, and passes the payload to its microcontroller.
  5. Unit B displays the message with its measured RSSI and transmits a short acknowledgement back to Unit A.
  6. Unit A marks the message delivered on its OLED; if no acknowledgement arrives, it reports the failure honestly instead of pretending.
  7. Between activity both units sleep to conserve the AA batteries, waking on button press or incoming preamble.

Tech stack:

  • ATmega328P microcontroller (Arduino-compatible)
  • Ra-02 LoRa module (SX1278, 433 MHz)
  • OLED character/graphic display
  • Push-button input interface
  • AA battery power with sleep modes
  • C/C++ firmware (Arduino IDE)
Parameter Value
Radio Ra-02 LoRa, 433 MHz ISM band
Modulation Chirp spread spectrum (LoRa)
Receiver sensitivity Down to approximately −148 dBm (SX1278 datasheet)
Range Kilometre-scale line-of-sight (design target; buyer-measured on site)
Display OLED with message thread and RSSI readout
Input 3 push buttons (presets + character entry)
Power AA battery pack per unit, sleep between activity (expected)
Units supplied 2 (Unit A and Unit B, addressed pair)

Project features

  • [Peer-to-peer LoRa texting] Two identical units exchange addressed text messages directly over the 433 MHz LoRa link, with no gateway or network.
  • [OLED chat display] Each unit shows the conversation with unit identity, message direction and status on a crisp OLED.
  • [Live RSSI readout] Every received message displays its signal strength (e.g. −71 dBm), turning link quality into a visible, measurable quantity.
  • [Button text entry] Three push buttons drive a message composer with preset phrases and character entry, designed for gloved or field use.
  • [Addressing and acknowledgements] Unit A / Unit B addressing with delivery acknowledgement, demonstrating reliable transfer over an unreliable medium.
  • [Battery operation] AA battery packs with low-power sleep between activity, showing the energy profile that makes LoRa field devices practical.
  • [Range-test procedure] A buyer-run procedure for measuring usable range and RSSI fall-off across the student's own test sites.

What is included

  • Two complete handheld messenger units (PCB, ATmega328P, Ra-02, OLED, buttons, battery pack)
  • Peer-to-peer messaging firmware with full source
  • Range and RSSI measurement procedure (buyer-run)
  • Battery-life estimation worksheet
  • Project report PDF (LoRa theory, spread spectrum, link budget, measurements)
  • PPT presentation for final review
  • Viva Q&A preparation document (chirp modulation, spreading factor, RSSI, addressing)

Limitations & prerequisites

  • Text only, at low data rates — LoRa trades throughput for range; no images, voice or fast chat.
  • Real-world range is environment-dependent (buildings, terrain, antenna orientation) and is measured by the student, never pre-claimed.
  • Button text entry is deliberately simple and slower than a phone keyboard — a field-device trade-off, stated honestly.
  • The 433 MHz band has regional duty-cycle and power rules; the firmware keeps transmissions short and the report notes the regulatory position.
  • Acknowledgements confirm delivery between the two units only; there is no store-and-forward for out-of-range units.

Frequently Asked Questions

How far can the two units really talk?

That depends on terrain, antenna orientation and spreading-factor settings — kilometres are achievable line-of-sight, far less through buildings. The included procedure has the student measure their own range and RSSI fall-off at several sites and report those real numbers.

Why LoRa instead of Wi-Fi or Bluetooth?

Wi-Fi and Bluetooth reach tens of metres; LoRa's chirp spread spectrum reaches kilometres at similar or lower power. The trade-off is data rate — perfect for short text, wrong for video — and the project makes that trade-off tangible.

What does the RSSI number on the screen mean?

Received Signal Strength Indicator, in dBm — how loud the other unit sounds. Values nearer zero are stronger; the units typically show around −60 to −90 dBm at classroom distances, and the number visibly drops as the units separate.

How do you type with only three buttons?

The composer offers scrollable preset phrases for fast field use plus a character-entry mode. It is slower than a touchscreen by design — the project is about the radio link, and the UI honesty is part of the report.

Does it need any network or SIM card?

No. The two units talk directly to each other, peer to peer. That is the entire point: messaging that works where there is no infrastructure at all.

Is this project suitable for a final-year project?

Yes — for Electronics, Communication and IoT programs. It demonstrates long-range wireless communication end to end: modulation, addressing, acknowledgements, link-quality measurement and low-power design. Suitable for B.E./B.Tech final-year projects in Electronics, Communication and IoT.

Components & software requirements
  • ATmega328P microcontroller (Arduino-compatible)
  • Ra-02 LoRa module (SX1278, 433 MHz)
  • OLED character/graphic display
  • Push-button input interface
  • AA battery power with sleep modes
  • C/C++ firmware (Arduino IDE)
Delivery information

Built-to-order project. Delivery timeline is shared after order confirmation based on current queue.

Support terms

Complete documentation, setup guide, and viva preparation included. Support for setup and explanation provided.

Download abstract (PDF)

Related guides

All guides
Blueprint-style technical illustration of an ESP32 development board at the centre, with sensor nodes, data-flow arrows and a circuit-brain motif representing an AI agent reasoning and sending decisions back.Engineering students building IoT or embedded final-year projects who want to add local AI agent behaviour with ESP32, MQTT and a small language model.

AI Agents on ESP32: Agentic IoT Final-Year Projects

An agentic IoT system observes, reasons, acts, remembers and explains. On ESP32 that means a split architecture: the chip senses and acts while a small local model (Ollama on your laptop) reasons over MQTT — a full LLM needs gigabytes of RAM the chip doesn't have. This guide covers three working patterns (host-reasoned agent, on-device tinyML on ESP32-S3, and a hybrid of both), plus Wi-Fi CSI presence sensing, parts and budget for India, code shapes, and honest limits to state in your report.

Read guide
Technical illustration of three electronic control units linked by a twisted-pair CAN bus cable carrying signal pulses between them.Electronics, E&TC, IoT and robotics students who keep hearing “CAN bus” in EV, automotive and industrial project ideas and want to understand it properly before wiring anything

CAN Bus Basics for Students: How ECUs Communicate

CAN bus is the shared network that lets dozens of controllers in a car, EV or robot communicate over two wires. This guide explains message IDs, arbitration, the physical layer, frame structure, error handling and CAN FD, then walks through building a working two-node bench network with an ESP32 and a transceiver.

Read guide
Illustration of a quadcopter drone build showing labeled parts including frame, motors, propellers, ESCs, flight controller, and battery.B.E./B.Tech Electronics, Mechanical, and Computer Science students planning to build a quadcopter drone who need to select compatible parts without wasting money on mismatched

Drone Build: Parts Selection Guide

Picking drone parts that actually work together is a sizing problem, not a shopping problem. This guide walks the compatibility chain — frame to props to motors to ESCs to battery — with the thrust math, firmware choices, LiPo safety, and the bench-test order that prevents disasters.

Read guide
Get a quotation