RNS Logo

rns.recipes

◈ 9ce92808be498e9e05590ff27cbfdfe4
Service restored

RTNode-HeltecV4 vs microreticulum_firmware for transport nodes

Question RNode

Started by NONGKHAEM_BKK_TH e23e9a470d42f05d... ·

NONGKHAEM_BKK_TH e23e9a470d42f05d...
#1

Hello!

 

Anyone knows the difference between running microReticulum_Firmware and
RTNode-HeltecV4 , both with transport mode on?

 

In theory, there should be none, however, I can see in the HeltecV4 repo references to issues between the s3r2 vs s3r8, as well as very tight limitations on the Hash list and path request tags etc . These limitations are not present on the microReticulum_Firmware, which leads me to think: these two pieces of software might be the same thing at all, because hardware limitations are evidently there for everyone.

 

I tried contacting jrl290 (if you are here, let me know :) - but couldn't find a gh discussion page, or LXMF address.

 

Thank you!

Cleeyv 0b91c6bd3f4e6eda...
#2

Both are based on Attermann's microReticulum library, but RTNode runs a vendored, customized version.

 

I've found the biggest practical difference between the two is that RTNode only runs on Heltec v4 and v3 ESP32 hardware, whereas microReticulum_Firmware runs on these two plus many other boards. Most significantly, it can run on the nRF52-based RAK4631 board which is much more power efficient. This makes it well-suited for smaller solar/battery-powered LoRa repeaters. Another useful feature it offers for remote repeaters is a nomadnet status page, and there is even early work on remote node admin over LoRa. It also has support for the RAK15001 flash module which makes the minimal nRF52 hardware more functional for storing RNS transport node routing tables on larger networks.

 

RTNodes are designed specifically to act a bridge between 1) LoRa mesh nodes, 2) local WiFi/TCP client nodes, and 3) remote internet/TCP backbone nodes (it also recently added Bluetooth bridging but I haven't tested this yet). Combined with battery-powered WiFi router/APs, this can create an access hub that allows anyone with a WiFi-capable device running a Reticulum app to communicate over a very resilient (and hopefully less likely to be bandwidth congested) hybrid of both LoRa and whatever TCP is still online/accessible. RTNodes can also still run on solar/battery, they just need to have a bigger power setup or they won't last as long in winter or otherwise less favourable conditions.

 

I will also highlight an important difference because it has caused problems for me during earlier rounds of testing: RTNode supports IFACs, but microReticulum_Firmware still does not! Therefore, for testing of LoRa repeater nodes, there can't be any LoRa interfaces with IFACs enabled if you're trying to use a microReticulum_Firmware node.

NONGKHAEM_BKK_TH e23e9a470d42f05d...
#3

oh wow, thank you for this very detailed reply! much appreciated!

burger ace748e1c4e3fd4e...
#4

ones vibecoded ones not

burger ace748e1c4e3fd4e...
#5

Screenshot_20261012_214259.pngevil prns

burger ace748e1c4e3fd4e...
#6

prns is slopiculum

Post a Reply

Supports Markdown: **bold**, *italic*, `code`, ```code blocks```, [links](url)

Log in to upload images

Quote
Copied to clipboard