#63 Consider lack of frequency adoption

Closed
opened 3 years ago by Michael Schloh von Bennewitz · 1 comments

Consider lack of frequency adoption

Problem environment

Transceivers must center on a base frequency around 868 MHz or 915 MHz, whereas the 433 MHz LoRa ISM band requires a second transceiver. Some regions have failed to adopt all frequencies above 433 MHz, which invalidates the broad service plan.

Steps to reproduce

  1. Review the worldwide regions
  2. Search for ISM bands near 900 MHz
  3. Compare with LoRa adoption

Expected result

Each world region adopts a LoRaWAN frequency around 900 MHz.

Actual result

Some regions (such as China) have regulated a 780 MHz ISM frequency but exclusively use 433 MHz for their LoRa transmissions.

Workaround

Reconfigure the transceiver to work at 433 MHz, although this will stress the 868 MHz optimised RF path and deliver poor performance.

Severity level

This is low priority because project requirements do not state regional preference or portability.

# Consider lack of frequency adoption ## Problem environment Transceivers must center on a base frequency around 868 MHz or 915 MHz, whereas the 433 MHz LoRa ISM band requires a second transceiver. Some regions have failed to adopt all frequencies above 433 MHz, which invalidates the broad service plan. ## Steps to reproduce 1. Review the worldwide regions 1. Search for ISM bands near 900 MHz 1. Compare with LoRa adoption ## Expected result Each world region adopts a LoRaWAN frequency around 900 MHz. ## Actual result Some regions (such as China) have regulated a 780 MHz ISM frequency but exclusively use 433 MHz for their LoRa transmissions. ## Workaround Reconfigure the transceiver to work at 433 MHz, although this will stress the 868 MHz optimised RF path and deliver poor performance. ## Severity level This is **low priority** because project requirements do not state regional preference or portability.
Michael Schloh von Bennewitz added the
wontfix
label 3 years ago
Michael Schloh von Bennewitz added the
bug
label 3 years ago
Michael Schloh von Bennewitz added this to the Online vendor sourcing milestone 3 years ago
Michael Schloh von Bennewitz removed the
bug
label 3 years ago
Michael Schloh von Bennewitz added the
derivative
label 3 years ago

This problem can be revisited on request, but assuming that users accept the approximately 900 MHz transceiving performance as satisfactory the ticket is closed.

This problem can be revisited on request, but assuming that users accept the approximately 900 MHz transceiving performance as satisfactory the ticket is closed.
Sign in to join this conversation.
No Assignees
1 Participants
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Cancel
Save
There is no content yet.