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

FreeRTOS RX retrieval windows to long #203

Open
mcserved opened this issue Jul 5, 2021 · 3 comments
Open

FreeRTOS RX retrieval windows to long #203

mcserved opened this issue Jul 5, 2021 · 3 comments
Assignees
Labels
bug Something isn't working Firmware Anything related to code and SW on the HW

Comments

@mcserved
Copy link
Contributor

mcserved commented Jul 5, 2021

Summary:

FreeRTOS has some drift, causing downlinks to fail. This relates to PR #202 and issue #187.

Steps to Reproduce:

  1. Default value should show this in current consumption:
    image
  2. Change this:
    #define lorawanConfigRX_MAX_TIMING_ERROR ( 50 )

    And this will produce this image:
    image
    With this timing:
basic_lorawan freertos_lorawan (new) freertos
5s14ms 5s129ms 4s980ms
218ms 271ms 531ms
781ms 754ms 492ms
218ms 271ms 531ms

What do you see now?

Delayed RX windows.

What do you want to see instead?

RX windows closer to their appropriate values.

How do you propose to implement this?

Find the cause of the drift delaying the downlink.

Environment:

FreeRTOS

What can you do yourself and what do you need help with?

All

@mcserved mcserved added bug Something isn't working Firmware Anything related to code and SW on the HW labels Jul 5, 2021
@mcserved mcserved added this to the Next Up milestone Jul 5, 2021
@mcserved mcserved self-assigned this Jul 5, 2021
This was referenced Jul 5, 2021
@elsalahy elsalahy modified the milestones: Next Up, 2021 Q3 Jul 5, 2021
@elsalahy
Copy link
Contributor

@marnixcro Can you please share some informations on your attempts to solve this?

@mcserved
Copy link
Contributor Author

@marnixcro Can you please share some informations on your attempts to solve this?

I tried finding the cause with the clocks drifting, but the datasheet mentioned max drifts of only 1-2% on these clocks. I have not been able to find where in the firmware the downlink event gets triggered.

@NicolasMrad NicolasMrad modified the milestones: 2021 Q3, 2021 Q4 Oct 4, 2021
@elsalahy elsalahy assigned elsalahy and unassigned mcserved Oct 5, 2021
@NicolasMrad NicolasMrad assigned azerimaker and unassigned elsalahy Dec 13, 2021
@NicolasMrad NicolasMrad modified the milestones: 2021 Q4, 2022 Q1 Jan 3, 2022
@NicolasMrad NicolasMrad modified the milestones: 2022 Q1, 2022 Q2 Mar 29, 2022
@NicolasMrad
Copy link

is this still relevant?

@NicolasMrad NicolasMrad modified the milestones: 2022 Q2, 2022 Q3 Jun 29, 2022
@NicolasMrad NicolasMrad modified the milestones: 2022 Q3, 2022 Q4 Oct 10, 2022
@NicolasMrad NicolasMrad modified the milestones: 2022 Q4, 2023 Q1 Dec 12, 2022
@NicolasMrad NicolasMrad modified the milestones: 2023 Q1, 2023 Q2 Apr 13, 2023
@KrishnaIyer KrishnaIyer removed this from the 2023 Q2 milestone Sep 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Firmware Anything related to code and SW on the HW
Projects
None yet
Development

No branches or pull requests

5 participants