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

phy-as923-sub-region not applied ? #15522

Open
rfuentess opened this issue Aug 1, 2024 · 1 comment
Open

phy-as923-sub-region not applied ? #15522

rfuentess opened this issue Aug 1, 2024 · 1 comment

Comments

@rfuentess
Copy link

rfuentess commented Aug 1, 2024

Description of defect

In our mbed_app.json apply the following configuration:

    "target_overrides": {
        "*": {
            ....
            "lora.phy": "AS923",
            "lora.phy-as923-sub-region": "AS2",
            ...
        },

By doing this, in theory we are setting AS923_LC1_FREQ, AS923_LC2__FREQ, AS923_LOWER_FREQ , AS923_UPPER_FREQ and AS923_RX_WND_2_FREQ to a proper range.

However, the first 4 defines are never used and AS923_RX_WND_2_FREQ is override later.

Still, I'm a rookie with Lora, so I'm not sure if mbed-os is using OK by trying to use the frequencies 923400000 and 923400000 for the RX1 and RX2 slots in both AS1 and AS2. However, based on what I understand from the lora regional specifications, I think no.

Target(s) affected by this defect ?

NUCLEO_WL55JC

Toolchain(s) (name and version) displaying this defect ?

GCC_ARM

What version of Mbed-os are you using (tag or sha) ?

mbed-os v6.17.0

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

mbed-tools

How is this defect reproduced ?

Try to make a STM32WL55 sensor to connect to a lora server settled for region AS923-2.

@mbedmain
Copy link

mbedmain commented Aug 1, 2024

@rfuentess thank you for raising this issue.Please take a look at the following comments:

It would help if you could also specify the versions of any tools you are using?

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'. This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Untriaged
Status: Needs Triage
Development

No branches or pull requests

2 participants