micropython-reticulum on ESP32-S3 feasible performance?
Started by Anonymous ·
https://github.com/varna9000/micropython-reticulum
It says: Announce validation ~6s
Do you think that can make a feasible standalone lora transport node?
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.
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.
Pity, that both projects are slopped