61–70 of 99 posts
Here is what I'm confused about: There is no published protocol/spec. It's nominally for radios like LoRa (Semtech) which are programmed with microcontrollers. To run it, you need Python software, or more recently, std Rust, both of which can't be used on the devices that would make sense for the hardware.
Here is what I'm confused about: There is no published protocol/spec. It's nominally for radios like LoRa (Semtech) which are programmed with microcontrollers. To run it, you need Python software, or more recently, std Rust, both of which can't be used on the devices that would make sense for the hardware.
Sounds like you’re looking for the RNode firmware
Earlier quoted context omitted.
Sounds like you’re looking for the RNode firmware
I hadn't heard of this. It sounds like then you'd need a dedicated radio co-processor that is just running their firmware. Then, connect to it via [SPI?] to your main MCU or similar.
Surprised to see nobody mentioned Yggdrasil [0]. It's a routing protocol with cryptographic, non-topologic addresses, which could be used on top of TCP/IP or any alternative stack, like LoRA. I've been using it as a Tailscale replacement for a few weeks, including hosting game servers, with about equivalent latency, and it seemed pretty stable. How does Reticulum differ? [0] https://yggdrasil-network.github.io/
Surprised to see nobody mentioned Yggdrasil [0]. It's a routing protocol with cryptographic, non-topologic addresses, which could be used on top of TCP/IP or any alternative stack, like LoRA. I've been using it as a Tailscale replacement for a few weeks, including hosting game servers, with about equivalent latency, and it seemed pretty stable. How does Reticulum differ? [0] https://yggdrasil-network.github.io/
Earlier quoted context omitted.
Yes, in the EU one subband allows 10%, the rest is 1%. I believe that Meshtastic uses the whole 250kHz of that subband by default. This is by far the most relaxed constraints of what is available in the EU and US. That's about 180 max. size messages per hour (at longfast) per device but you need to take into account retransmissions, acks, mesh management and routing of third party messages. So it may work, barely, fo…
>I believe that Meshtastic uses the whole 250kHz of that subband by default. This is by far the most relaxed constraints of what is available in the EU and US. Again wrong, just look at EU vs US: https://meshtastic.org/docs/configuration/radio/lora/#region > beyond extremely small meshes, if at all. 180 online nodes (300 at max) is not extremely small (and that's our small mesh EU with medium_fast)
(Careful that the US have a 400ms dwell time depending on settings that can put a significant limit on things/range)
Such a nasty name for a good project ;-;
The name comes from Neal Stephenson's book Anathem
It's quite a tough read for me with such an alien vocabulary.
Anyway, good to know it's not meant to resemble anything nasty.
Here is what I'm confused about: There is no published protocol/spec. It's nominally for radios like LoRa (Semtech) which are programmed with microcontrollers. To run it, you need Python software, or more recently, std Rust, both of which can't be used on the devices that would make sense for the hardware.
Earlier quoted context omitted.
The name comes from Neal Stephenson's book Anathem
Thanks. That's quite a dictionary there and I'm not familiar with that particular universe so the reference was lost on me. It's quite a tough read for me with such an alien vocabulary. Anyway, good to know it's not meant to resemble anything nasty.