◈ 9ce92808be498e9e05590ff27cbfdfe4
RNS 1.3.8 released https://pypi.org/project/rns/
Forum / Build Guides / micropython-reticulum on ESP32-S3 feasible performance?

micropython-reticulum on ESP32-S3 feasible performance?

Question Discussion

Started by Anonymous ·

Anonymous

https://github.com/varna9000/micropython-reticulum

It says: Announce validation ~6s

Do you think that can make a feasible standalone lora transport node?

edited

I'd recommend going with microReticulum instead, specifically https://github.com/attermann/microReticulum_Firmware/releases, as it's finally reached a state where it should work well as a standalone transport node.

Of course the Raspberry Pi Zero + RNode setup also works well if you really want to run RNS.

edited

I just want to quickly jump in here. I'm the developer of micropython reticulum. Since the above was posted, I've ported the problematic modules in C with micropython bindings - the critical parts were crypto modules and bz2 module. I've kept a native micropython fallback versions just in case. This dramatically increased the performance of the port. I've been testing it now with sending images, voice etc in small networks and it behaves good both on LoRa and TCP interfaces.

circfruit wrote:

I just want to quickly jump in here. I'm the developer of micropython reticulum. Since the above was posted, I've ported the problematic modules in C with micropython bindings - the critical parts were crypto modules and bz2 module. I've kept a native micropython fallback versions just in case. This dramatically increased the performance of the port. I've been testing it now with sending images, voice etc in small networks and it behaves good both on LoRa and TCP interfaces.

Hi!

This is your repository, right? https://github.com/varna9000/microReticulum_Firmware

I'm following the steps for building firmware for the Seeed XIAO nRF52840 + Wio-SX1262.
During the process, I discovered that the files "xiao_rnode_setup.py" and "provision_xiao.py" are missing in your repository.

I'm afraid that without provisioning EEPROM, nothing will work.

Anonymous

Pity, that both projects are slopped

Otto wrote:

circfruit wrote:
> I just want to quickly jump in here. I'm the developer of micropython reticulum. Since the above was posted, I've ported the problematic modules in C with micropython bindings - the critical parts were crypto modules and bz2 module. I've kept a native micropython fallback versions just in case. This dramatically increased the performance of the port. I've been testing it now with sending images, voice etc in small networks and it behaves good both on LoRa and TCP interfaces.

Hi!

This is your repository, right? https://github.com/varna9000/microReticulum_Firmware

I'm following the steps for building firmware for the Seeed XIAO nRF52840 + Wio-SX1262.
During the process, I discovered that the files "xiao_rnode_setup.py" and "provision_xiao.py" are missing in your repository.

I'm afraid that without provisioning EEPROM, nothing will work.

To be fair, I didn't put much effort in tidying up this particular repo. I kind of used Claude to blindly sort out the pinout and cut off some bits so that microReticulum doesn't die on the xiao nrf52840.

I give more attention to the Micropython port. I understand that some might not be keen on the AI tooling, but this allows more people to get engaged in projects like Reticulum and speed up the adoption. I've been coding with Micropython on microcontrollers before AI was a thing, so wouldn't call the port a "slop" as Anonymous does above. In any case, it allows flexibility on adding features (like standalone camera reticulum node), works for me and hopefully for others too.

Post a Reply

Markdown

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

Log in to upload images

Proof of work verification for anonymous posting

Copied to clipboard