LoRa Common Settings #688
Replies: 2 comments 1 reply
-
There's been some discussion and these are the points as I remember them.
Basically, my takeaway is this is best served by local users forming groups and setting standards for their local nets. This allows for better optimization for local conditions and keeps the decisions where they should be: in the hands of the end-users. There is some value in regional standards, but again, this is best served by the local users, not the network stack itself. I highly encourage local groups to set and publish local standards, then post about them here or in another central repository. Another major advantage is network congestion. If Chicago has a high speed LoRa system called ChiNet, just to not waste a good name on a meta-variable, and a much slower, more compact SleepyNet, then users passing small bits of telemetry can avoid the congestion of the main talk-group. So, because I ramble and I'm not actually awake yet, I'll sum up:
|
Beta Was this translation helpful? Give feedback.
-
https://github.com/markqvist/Reticulum/wiki/Popular-RNode-Settings |
Beta Was this translation helpful? Give feedback.
-
Has there been any discussion on having a common listing of LoRa settings for RNode?
For example in ANZ :
Freq 919.875 Mhz
Bandwidth 250 kHz
Spread 9
Code 5
If 2 people (who didn't know each other in advance) had the same settings, ended up in the same general area and both had RNodes they would at least one pre-determined common interface for LoRa
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions