rns.recipes

Welcome to the microReticulum Updates and Technical Discussion thread.

This thread serves as the central place for announcements related to new microReticulum releases, including bug fixes, new features, performance improvements, compatibility changes, and development milestones.

In addition to release updates, the thread is open for technical discussion covering topics such as architecture and design decisions, implementation details, integrations, troubleshooting, optimization, deployment experiences, and general development feedback.

Whether you are following project progress, testing new releases, integrating microReticulum into your own applications, or contributing ideas and improvements, you are encouraged to participate in the discussion.

Note that discussions are expected to remain respectful, constructive, and productive. Offensive, disruptive, or non-constructive posts may be removed in order to maintain a healthy and collaborative community environment.

Let's build together!

microReticulum GitHub Repo

A quick announcement...

I know there has been a lot of interest in Resource support in microReticulum over the past months (even years), and I'm happy to announce that it has finally arrived!

I've also added an example project nomadnet in the repo that demonstrates a very basic NomadNet client and server. Note however that microReticulum presently does not have support for compressed content, so most pages delivered by standard NomadNet will fail to be received unless compression is disabled. The reason for this omission lies in the compression algorithm bz2 used by RNS which is extremely resource-intensive and not embedded-friendly at all, but this is a discussion for another day.

Note that Resource support is currently only available in the master branch of the microReticulum repo and not in any release (yet). Please treat it as "experimental" for the time being while we work to get more interop testing behind us. In the meantime, feel free to play.

Cheers!

Is there a way that the microReticulum transport nodes can show up in my network visualization panel on MeshchatX which is connected to a standard RNode? It would be great to confirm that the transport node is indeed up and running.

gdane wrote:

A quick announcement...

I know there has been a lot of interest in Resource support in microReticulum over the past months (even years), and I'm happy to announce that it has finally arrived!

I've also added an example project nomadnet in the repo that demonstrates a very basic NomadNet client and server. Note however that microReticulum presently does not have support for compressed content, so most pages delivered by standard NomadNet will fail to be received unless compression is disabled. The reason for this omission lies in the compression algorithm bz2 used by RNS which is extremely resource-intensive and not embedded-friendly at all, but this is a discussion for another day.

Note that Resource support is currently only available in the master branch of the microReticulum repo and not in any release (yet). Please treat it as "experimental" for the time being while we work to get more interop testing behind us. In the meantime, feel free to play.

Cheers!

This is so awesome. Great work Attermann!!!

As a side note, for any LXMF implementations in the future that target microControllers where bzip isn't possible - there is compression support signalling with the SF_COMPRESSION flag :)

https://github.com/markqvist/LXMF/commit/72932eea28074420defd02b6eb3e5e09a126e4ee

daylight-hub wrote:

Is there a way that the microReticulum transport nodes can show up in my network visualization panel on MeshchatX which is connected to a standard RNode? It would be great to confirm that the transport node is indeed up and running.

Not yet, but that has actually been the motivation behind finally getting Resource implemented, so that transport nodes can have a mechanism to share instrumentation with other nodes on the network.

I haven't decide if I will implement a NomadNet-type interface, or extend the existing management endpoints already in RNS and recently (partially, wip) implemented in microReticulum.

Of course you don't have to wait for me either. You could roll your own firmware based on microReticulum_Firmware, and add in whatever endpoint you like using microReticulum code and the nomednet example as a guide.

Zenith wrote:

gdane wrote:

A quick announcement...

I know there has been a lot of interest in Resource support in microReticulum over the past months (even years), and I'm happy to announce that it has finally arrived!

I've also added an example project nomadnet in the repo that demonstrates a very basic NomadNet client and server. Note however that microReticulum presently does not have support for compressed content, so most pages delivered by standard NomadNet will fail to be received unless compression is disabled. The reason for this omission lies in the compression algorithm bz2 used by RNS which is extremely resource-intensive and not embedded-friendly at all, but this is a discussion for another day.

Note that Resource support is currently only available in the master branch of the microReticulum repo and not in any release (yet). Please treat it as "experimental" for the time being while we work to get more interop testing behind us. In the meantime, feel free to play.

Cheers!

This is so awesome. Great work Attermann!!!

As a side note, for any LXMF implementations in the future that target microControllers where bzip isn't possible - there is compression support signalling with the SF_COMPRESSION flag :)

https://github.com/markqvist/LXMF/commit/72932eea28074420defd02b6eb3e5e09a126e4ee

Awesome thanks for the heads-up. That would be a really nice addition to NomadNet too.

That could probably be done too.

In the long run, I think it would be very nice to see some type of feature flag happen on the link level, and maybe even options for different compression like zstd. Much like how MTU is negotiated.

gdane wrote:

A quick announcement...

I know there has been a lot of interest in Resource support in microReticulum over the past months (even years), and I'm happy to announce that it has finally arrived!

I've also added an example project nomadnet in the repo that demonstrates a very basic NomadNet client and server. Note however that microReticulum presently does not have support for compressed content, so most pages delivered by standard NomadNet will fail to be received unless compression is disabled. The reason for this omission lies in the compression algorithm bz2 used by RNS which is extremely resource-intensive and not embedded-friendly at all, but this is a discussion for another day.

Note that Resource support is currently only available in the master branch of the microReticulum repo and not in any release (yet). Please treat it as "experimental" for the time being while we work to get more interop testing behind us. In the meantime, feel free to play.

Cheers!

Awesome! I spent a few cycles in the last few weeks grafting pyxis onto microReticulum 0.3.0, since I had formed it back in December or something, and you had much nicer solutions for several of the problems I had to solve along the way to get it working.

Will happily spend a few more using your Resource implementation!

New microReticulum version 0.4.1 released with several fixes and enhancements.

Also new microReticulum_Firmware version 1.86.2 released with the latest microReticulum and added features.

Notably, this latest firmware release includes support for the new Provisioning system, as well as a single-page HTML RNode management console for managing microReticulum settings and most RNode settings.
NOTE: This new provisioning and web console is experimental so use at your own risk.

Also announcing a new and very experimental feature of microReticulum_Firmware.

The latest release version 1.86.2 includes RNode Linux daemons for Raspberry Pi (debian-bookworm) and Luckfox (ubuntu-jammy) that interface directly with SPI-attached LoRa radios (think meshtasticd).
I have only tested with an Adafruit RFM95x module wired to a Luckfox Pico so far but will add more example configs as I am able to test new SPI radios.
This daemon can run in either traditional RNode Host interface mode (default), or in self-contained transport mode (TNC mode).
To use it as a Host interface from Python RNS just define your RNodeInterface as usual but use "port = tcp://localhost" to connect to the rnoded daemon.

(duplicate post deleted)

Is there a way to edit the Nomadnet page? Would be great to customise the name of the Node and page content.

Anonymous wrote:

Is there a way to edit the Nomadnet page? Would be great to customise the name of the Node and page content.

Not through runtime configuration unfortunately. You can easily change in the source though if you're comfortable building it yourself. The site name is currently line 875 in RNode_Firmware.ino, and the page content in all in Pages.h.

How do I configure the latest microReticulum_Firmware to enable Transport? I used the rnodeconf --tnc but the serial console says Transport is disabled. It's not clear how the new provisioning system works.

I would also be very interested in a bit more documentation about how the new features work. <3

Dio wrote:

How do I configure the latest microReticulum_Firmware to enable Transport? I used the rnodeconf --tnc but the serial console says Transport is disabled. It's not clear how the new provisioning system works.

That should still work the same way it always has using rnodeconf. Be sure you're passing all lora parameters when you're enabling TNC mode since those are required to init the radio. Also check the display and be sure it's not complaining about the device being un-provisioned, firmware corrupt, etc. All of those things can happen during installation. If all else fails, provide the device logs from init if you'd like me to take a look.

Anonymous wrote:

I would also be very interested in a bit more documentation about how the new features work. <3

Baptism by fire unfortunately is all that's available at the moment ;-)

gdane wrote:

Anonymous wrote:

I would also be very interested in a bit more documentation about how the new features work. <3

Baptism by fire unfortunately is all that's available at the moment ;-)

And it was worth it! Its the first time I finally tried microreticulum, and the new management console is amazing! You really should include some screenshots of all the things you can configure and check out to get people a bit excited :)

One thing I noticed is that as soon as I set the LoRa interface to AP it would not announce its own nomadnet site. Thats probably not intended, AP mode should only block announce propagation, not your own announces?

So, the last microReticulum firmware for the Heltec V4 that I was able to flash using Liam Cottle's RNode flasher was 1.86.1. When I try to flash 1.86.2 or 1.86.3 using the flasher it shows up as missing config.