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.

Sign up for GitHub

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

Jump to bottom

[Bug]: EU 433 channels centers incorrect #3371

Open
audriusb opened this issue Mar 11, 2024 · 3 comments · May be fixed by #2696
Open

[Bug]: EU 433 channels centers incorrect #3371

audriusb opened this issue Mar 11, 2024 · 3 comments · May be fixed by #2696
Labels
3.0 Planned for next major release expected behavior This behavior is expected. low-priority Possibly something we'll consider in the future but doesn't serve the core use-cases or problematic pinned Exclude from stale processing tech debt Code or lib references that are not up to date or propper standards

Comments

@audriusb
Copy link

audriusb commented Mar 11, 2024 •
edited
Loading

Category

Other

Hardware

Not Applicable

Firmware Version

2.2.24

Description

Accorting to lora alliance the band plan starts at 433.05Mhz.
Not 433.00. It ends at 434.79. The very first channel used by meshtastic is centered at 433.125, but it should be 433.175.
ETSI has defined 433 to 434 MHz frequency band for LoRa application. It uses 433.175 MHz, 433.375 MHz and 433.575 MHz frequency channels.
Having a bandwidth of 250 kHz makes it out of band and illegal to be used without a licence.
Please consider shifting all the channels.
IMG_20240311_131545_169

Relevant log output

No response
@audriusb audriusb added the bug Something isn't working label Mar 11, 2024
@caveman99
Copy link
Member

While your observation is technically correct, we can not change the channel raster with a minor firmware version. If we change it at all this needs to go into the next major revision.

Also please take into consideration the ISM band 433.05-434.79 MHz is only a secondarly allocation, primary user being the HAM radio service from 430-439,1 MHz. (and RX only from 439.1-440 MHz) - The borders of the ISM band are crafted with a safeguard gap to prevent carrier overlap outside of 433-435 MHz with broadband signals not to interfere with the allocation of the adjacent frequencies, especially in the sensitive 435-438 MHz Satcom band. So a center frequency of 433.125 and BW 250 kHz will stay clear of 433.000 and this is fine with the primary user of those frequencies.

@audriusb
Copy link
Author

I can see there was a discussion about it few years ago
https://meshtastic.discourse.group/t/etsi-violations/2719/18

@caveman99 caveman99 added tech debt Code or lib references that are not up to date or propper standards expected behavior This behavior is expected. low-priority Possibly something we'll consider in the future but doesn't serve the core use-cases or problematic and removed bug Something isn't working labels Mar 11, 2024
@andrekir
Copy link
Member

this is planned for the next breaking cycle in #2696

@caveman99 caveman99 added the 3.0 Planned for next major release label Mar 11, 2024
@andrekir andrekir linked a pull request Mar 11, 2024 that will close this issue
[breaking] fix EU433 LoRa definitions #2696
Draft
@caveman99 caveman99 added the pinned Exclude from stale processing label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3.0 Planned for next major release expected behavior This behavior is expected. low-priority Possibly something we'll consider in the future but doesn't serve the core use-cases or problematic pinned Exclude from stale processing tech debt Code or lib references that are not up to date or propper standards
Projects
Meshtastic 3.0 Goals and Ideas
Status: No status
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[breaking] fix EU433 LoRa definitions andrekir/Meshtastic-device
3 participants
@caveman99 @audriusb @andrekir