Skip to content
Engineering
CompletedRF & Wireless Communication · Practical build

433 MHz RF Wireless Data Transmission System

A wireless link that sends binary data over 433 MHz from an ESP-based transmitter to an Arduino receiver, which decodes it to text via ASCII and displays it on an OLED.

  • ESP microcontroller
  • Arduino
  • 433 MHz RF
  • Binary encoding
  • ASCII
  • OLED
  • Embedded C/C++

Overview

This project is a point-to-point wireless link built from separate parts rather than a ready-made radio module. An ESP-based microcontroller encodes a message as binary and transmits it over a 433 MHz RF link. An Arduino board receives the signal, decodes the binary back into characters using ASCII, and prints the result to an OLED display.

The goal was understanding rather than product: I wanted to follow a message the whole way from text, to bits, to a radio signal, to bits again, and back to text on a screen.

Signal path

Message to binary encoding, to the ESP-based transmitter, across the 433 MHz RF link, to the Arduino receiver, through ASCII decoding, to the OLED display.MessagetextBinaryencodingTransmitterESP-based433 MHzReceiverArduinoASCIIdecodingOLEDwireless link — no error checking yet

How it works

Transmitter

The ESP-based board holds the message to send and converts each character into its binary representation. Those bits drive the 433 MHz transmitter module, which turns them into an RF signal on the carrier frequency.

Receiver

The Arduino board reads the output of the 433 MHz receiver module and recovers the stream of bits. It groups those bits back into bytes and maps each byte to a character using ASCII, which is the same table the transmitter encoded against. The decoded text is then written to the OLED display.

Why ASCII

ASCII is what makes the two ends agree. The radio link carries no meaning on its own — it only moves ones and zeros. ASCII is the shared convention that says a particular byte represents a particular character, so both sides interpret the same bits the same way.

Status of the technical details

The link works end to end: a message typed on the transmitter side appears as readable text on the OLED. Beyond that, I have not yet documented the exact hardware revisions or measured the link's performance, so the specifications table above has gaps rather than guesses. Filling those in is the next piece of work, and it is what the proposed experiments are for.

What I took away

The part that proved most instructive was how little the radio knows. The RF layer moves bits and nothing else — every piece of structure (where a character starts, whether anything was lost, whether the message is complete) has to be imposed by the code on either side. A link that works on a bench in one room is not the same thing as a link that works reliably, and the difference is almost entirely protocol rather than hardware.

That gap is what makes the future experiments interesting: range, packet loss, antenna orientation and acknowledgement are exactly the problems that have to be solved before a link like this could carry telemetry for something that moves, such as a drone.

Objectives

  • Build a working point-to-point wireless link from discrete parts rather than a packaged module.
  • Understand how a message becomes binary, travels as an RF signal, and is reassembled as readable text.
  • Get hands-on with the boundary between firmware, radio hardware and a display peripheral.

Known limitations

  • One-way link — the receiver has no way to acknowledge what it received.
  • No error detection, so a corrupted bit is displayed as a corrupted character.
  • Range, reliability and data rate have not been measured.

Proposed future work

  • Measure usable range in open air and compare it with obstructed paths.
  • Log packet loss over a fixed number of transmissions to get a reliability figure.
  • Test how antenna orientation and placement change reception.
  • Add a checksum so the receiver can reject corrupted packets.
  • Add acknowledgement and retransmission to make the link two-way.
  • Explore what this implies for drone telemetry, where a dropped packet matters.