Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: User configurable center frequency #2144

Closed
code8buster opened this issue Jan 15, 2023 · 7 comments
Closed

[Feature Request]: User configurable center frequency #2144

code8buster opened this issue Jan 15, 2023 · 7 comments
Assignees
Labels
enhancement New feature or request

Comments

@code8buster
Copy link
Contributor

Platform

NRF52, ESP32

Description

Tracking issue for user configured frequency

As is, there is no direct way to start the LoRa modem at a given frequency. All of it is arbitrated by the RadioInterface in terms of frequency ranges and regions.
We do not have a region or band plan for licensed amateur radio, and to make any would be onerous due to the variability of bands, national/regional usage differences, etc. The number of RDEFs would expand greatly.

For users who set is_licensed=1, it may be better to expose a method of setting frequency. (RadioInterface::saveFreq a good candidate?)

@code8buster code8buster added the enhancement New feature or request label Jan 15, 2023
@caveman99
Copy link
Sponsor Member

Another possibility would be a custom RDEF slot that can be set via lora config. But just speccing the frequency is a lot easier. power Region limitation is off for is_licensed anyway and i think we could also override the other settings (voice, duty cycle) if is_licensed is true.

@faydr
Copy link
Contributor

faydr commented Jan 15, 2023

Just to advocate further for this feature -- if hams (such as myself) want to set up "infrastructure" Meshtastic nodes (e.g., fixed nodes on top of mountains), we need to coordinate with other users in the band (like other repeaters). Readily knowing the exact frequency in this case is essential to coordinating with other repeater owners.

@caveman99 caveman99 self-assigned this Jan 17, 2023
@caveman99
Copy link
Sponsor Member

We're shuffling protobufs right now, ths is on hold till the transition is done.

@mc-hamster
Copy link
Member

May also need to consider other overrides, eg bandwidth & coding since those won't have any specific region.

@caveman99 I'd advocate for a prescribed frequency / modem configuration. This won't be the last time this comes up.

@mc-hamster
Copy link
Member

... now that (I think) we have plumbing for the 2.4ghz lora radios, this may be used for a possible future Meshtastic EME bounce. Imagine the headline "Meshtastic goes to the moon"

@caveman99
Copy link
Sponsor Member

May also need to consider other overrides, eg bandwidth & coding since those won't have any specific region.

@caveman99 I'd advocate for a prescribed frequency / modem configuration. This won't be the last time this comes up.

The modem configuration ranges (both our presets and freely configurable parameters) are the same across all sub ghz Lora chips. so this really needs a custom frequency settable. Radiolib will do a bounds check anyway, i don't see the need to make Coding Rate, Bandwidth and Spreading Factor 'freeform'.

2.4 GHz is ready, but the 'bandwidth' settings is different for the higher bands. Our presets were adjusted accordingly, but the same as for the sub-GHz bands applies.

@code8buster
Copy link
Contributor Author

CR/BW/SF already free-form in the way that we already have config.lora protobufs for modem settings if a user doesn't want to use a preset like LongFast.

caveman99 added a commit to meshtastic/protobufs that referenced this issue Jan 30, 2023
caveman99 added a commit to meshtastic/protobufs that referenced this issue Jan 30, 2023
caveman99 added a commit to meshtastic/protobufs that referenced this issue Jan 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants