Firmware for the RNode radio interface
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Go to file
Mark Qvist 09b0c2a488 Updated readme 7 days ago
Builds/Handheld RNode Added build guide 1 year ago
Console Added T3 TCXO build support 7 days ago
Documentation Updated readme 5 months ago
Fonts Added fonts 5 months ago
Python Module Cleanup 1 year ago
Release Added T3 TCXO build support 7 days ago
.gitignore Added basic console site generator and web server 1 year ago
Bluetooth.h Add BLE driver for NRF52 4 weeks ago
Boards.h Fixed nRF build include 1 week ago
Config.h Reworked board defines, fixed RSSI and waterfall bugs for SX1262. 2 weeks ago
Console.h Updated license headers 1 year ago
Device.h Added board configuration 2 weeks ago
Display.h Added board configuration 2 weeks ago
Framing.h Added battery state reporting over USB/Serial/Bluetooth. Implements #39. 5 months ago
Graphics.h Added channel load and airtime stats to display 5 months ago
LICENSE Updated license to GPLv3 1 year ago
MD5.cpp MD5 library 6 years ago
MD5.h MD5 library 6 years ago
Makefile Added T3 TCXO build support 7 days ago
Modem.h Add SX1280 driver and split driver in three parts 2 weeks ago
Power.h Switch from old AXP202X_Library to new XPowersLib 2 months ago
README.md Updated readme 7 days ago
RNode_Firmware.ino Added max power level differentiation for SX1262 1 week ago
ROM.h SX126x board defines 1 week ago
Utilities.h SX126x board defines 1 week ago
arduino-cli.yaml Add RAK4630 BSP 1 month ago
partition_hashes Use /usr/bin/env python in partition_hashes 1 month ago
release_hashes.py Cleanup 1 year ago
sx126x.cpp SX126x board defines 1 week ago
sx126x.h Added register values and op-codes. Cleanup. 1 week ago
sx127x.cpp Added register values and op-codes. Cleanup. 1 week ago
sx127x.h Added register values and op-codes. Cleanup. 1 week ago
sx128x.cpp Fix RAK4630 compilation error and SX1280 modemStatus logic 1 week ago
sx128x.h Add SX1280 driver and split driver in three parts 2 weeks ago

README.md

RNode Firmware

This is the open firmware that powers RNode devices.

An RNode is an open, free and unrestricted digital radio transceiver. It enables anyone to send and receive any kind of data over both short and very long distances. RNodes can be used with many different kinds of programs and systems, but they are especially well suited for use with Reticulum.

RNode is not a product, and not any one specific device in particular. It is a system that is easy to replicate across space and time, that produces highly functional communications tools, which respects user autonomy and empowers individuals and communities to protect their sovereignty, privacy and ability to communicate and exchange data and ideas freely.

An RNode made from readily available and cheap parts, in a durable 3D printed case

The RNode system is primarily software, which transforms different kinds of available hardware devices into functional, physical RNodes, which can then be used to solve a wide range of communications tasks. Such RNodes can be modified and built to suit the specific time, locale and environment they need to exist in.

Latest Release

The latest release, installable through rnodeconf, is version 1.68. This release brings the following changes:

  • Fixed a bug in high-bandwidth optimisation
  • Fixed a potential memory overflow during firmware update
  • Fixed a bug in LoRa modem status updates
  • Updated bootstrap console with latest packages

You must have at least version 2.1.3 of rnodeconf installed to update the RNode Firmware to version 1.67. Get it by updating the rns package to at least version 0.6.4.

A Self-Replicating System

If you notice the presence of a circularity in the naming of the system as a whole, and the physical devices, it is no coincidence. Every RNode contains the seeds necessary to reproduce the system, the RNode Bootstrap Console, which is hosted locally on every RNode, and can be activated and accesses at any time - no Internet required.

The designs, guides and software stored within allows users to create more RNodes, and even to bootstrap entire communications networks, completely independently of existing infrastructure, or in situations where infrastructure has become unreliable or is broken.

Where there is no Internet, RNodes will still communicate

The production of one particular RNode device is not an end, but the potential starting point of a new branch of devices on the tree of the RNode system as a whole.

This tree fits into the larger biome of Free & Open Communications Systems, which I hope that you - by using communications tools like RNode - will help grow and prosper.

One Tool, Many Uses

The RNode design is meant to flexible and hackable. At it's core, it is a low-power, but extremely long-range digital radio transceiver. Coupled with Reticulum, it provides encrypted and secure communications.

Depending on configuration, it can be used for local networking purposes, or to send data over very long distances. Once you have an RNode, there is a wide variety of possible uses:

Types & Performance

RNodes can be made in many different configurations, and can use many different radio bands, but they will generally operate in the 433 MHz, 868 MHz, 915 MHZ and 2.4 GHz bands. They will usually offer configurable on-air data speeds between just a few hundred bits per second, up to a couple of megabits per second. Maximum output power will depend on the transceiver and PA setup used, but will generally lie between 17 dbm and 27 dBm.

The RNode system has been designed to allow reliable systems for basic human communications, over very wide areas, while using very little power, being cheap to build, free to operate, and near impossible to censor.

While speeds are lower than WiFi, typical communication ranges are many times higher. Several kilometers can be acheived with usable bitrates, even in urban areas, and over 100 kilometers can be achieved in line-of-sight conditions.

Supported Boards & Devices

It's easy to create your own RNodes from one of the supported development boards and devices. If a device or board you want to use is not yet supported, you are welcome to join the effort and help creating a board definition and pin mapping for it!

The RNode Firmware supports the following boards:

  • Handheld v2.x RNodes from unsigned.io
  • Original v1.x RNodes from unsigned.io
  • LilyGO T-Beam v1.1 devices
  • LilyGO LoRa32 v1.0 devices
  • LilyGO LoRa32 v2.0 devices
  • LilyGO LoRa32 v2.1 devices
  • Heltec LoRa32 v2 devices
  • Homebrew RNodes based on ATmega1284p boards
  • Homebrew RNodes based on ATmega2560 boards
  • Homebrew RNodes based on Adafruit Feather ESP32 boards
  • Homebrew RNodes based on generic ESP32 boards

Supported Transceiver Modules

The RNode Firmware supports all transceiver modules based on Semtech SX1276 or Semtech SX1278 chips, that have an SPI interface and expose the DIO_0 interrupt pin from the chip.

Support for SX1262, SX1268 and SX1280 is being implemented. Please support the project with donations if you want this faster!

Getting Started Fast

You can download and flash the firmware to all the supported boards using the RNode Config Utility. All firmware releases are now handled and installed directly through the rnodeconf utility, which is included in the rns package. It can be installed via pip:

# Install rnodeconf via rns package
pip install rns --upgrade

# Install the firmware on a board with the install guide
rnodeconf --autoinstall

For more detailed instruction and in-depth guides, you can have a look at some of these resources:

If you would rather just buy a pre-made unit, you can visit my shop and purchase my particular version of the Handheld RNode, which I can assure you is made to the highest quality, and with a lot of care.

Support RNode Development

You can help support the continued development of open, free and private communications systems by donating via one of the following channels:

  • Monero:
    84FpY1QbxHcgdseePYNmhTHcrgMX4nFfBYtz2GKYToqHVVhJp8Eaw1Z1EedRnKD19b3B8NiLCGVxzKV17UMmmeEsCrPyA5w
    
  • Ethereum
    0xFDabC71AC4c0C78C95aDDDe3B4FA19d6273c5E73
    
  • Bitcoin
    35G9uWVzrpJJibzUwpNUQGQNFzLirhrYAH
    
  • Ko-Fi: https://ko-fi.com/markqvist

License & Use

The RNode Firmware is Copyright © 2024 Mark Qvist / unsigned.io, and is made available under the GNU General Public License v3.0. The source code includes an SX1276 driver that is released under MIT License, and Copyright © 2018 Sandeep Mistry / Mark Qvist.

You can obtain the source code from git.unsigned.io or GitHub.

Every RNode also includes an internal copy of it's own firmware source code, that can be downloaded through the RNode Bootstrap Console, by putting the RNode into Console Mode (which can be activated by pressing the reset button two times within two seconds).

The RNode Ecosystem is free and non-proprietary, and actively seeks to distribute it's ownership and control. If you want to build RNodes for commercial purposes, including selling them, you must do so adhering to the Open Source licenses that the various parts of the RNode project is released under, and under your own responsibility.

If you distribute or modify this work, you must adhere to the terms of the GPLv3, including, but not limited to, providing up-to-date source code upon distribution, displaying appropriate copyright and license notices in prominent positions of all conveyed works, and making users aware of their rights to the software under the GPLv3.

In practice, this means that you can use the firmware commercially, but you must understand your obligation to provide all future users of the system with the same rights, that you have been provided by the GPLv3. If you intend using the RNode Firmware commercially, it is worth reading this page.