Open b8b8 opened 2 months ago
Parts of this could be implemented with a LR1121 based wideband radio. I don't think it can listen to 900 and 2.4 at the same time though. I have a Lilygo T3 S3 LR1121 incoming and after initial support we can revisit this.
Excellent. This also provides a little bit more worldwide compatibility by default as I believe 2.4 LoRa is legal in all countries like wifi is.
Platform
NRF52, ESP32, Cross-Platform
Description
This is just an idea I wanted to get in writing; i dont expect it to be worked on anytime soon.
My idea is to slave a 2.4GHz LoRa radio to our standard NRF or ESP32 boards. The main purpose will be to drastically increase the bandwidth available for city and high congestion events while falling back to standard 900MHz when appropriate.
The two radios show up as a single combined radio (thus the master/slave relationship) to the app with two default public channels. The standard LongFast 900 LoRa channel and the new 2.4GHz LoRa channel would show up on the message list.
The major change is now all direct messages (and maybe private-primary channel telemetry) would first be tried at the much higher bandwidth 2.4 channel and if no acknowledgement is received, then it will resend the DM on the 900 LoRa channel. The two frequencies would not actually be bridged directly so you dont have to worry about dumping a massive amount of 2.4 traffic onto the more fragile 900 band. Since both public channels would still exist people can still chat on both to the public independently.
Without breaking backward compatibility and still allowing users to interact with nodes that dont have 2.4 radios, this could dramatically increase available bandwidth in congested areas (and offload private telemetry with public fallback). No changes would need to be made say when hiking and the 2.4 band cant make contact, as it would fall back to the longer range 900 band.