Skip to content

TP_A_EU868_ED_MAC_104_RETRANSMISSION_BACKOFF fails due to violation of duty cycle restrictions #129

Open

Description

@sca-l

Hi all,

I'm using the latest LBM v4.8.0 tag source code and I'm trying to execute the LCTT TP_A_EU868_ED_MAC_104_RETRANSMISSION_BACKOFF test for EU868. Test has a FAIL result. Was this test been executed on your side? do you have some hints on that?
I attached the LCTT log of FAIL result.

More over, I noticed that the Duty cycle service seems implemented for EU868 and RU864 regions, but it is totally missed for AS923. Is there a reason for that? Did I miss something?

Thank you, best regards,
Laura Scalzo

Activity

  1. sca-l commented on Jul 18, 2025

    @sca-l
    Author
  2. lbm-team commented on Sep 8, 2025

    @lbm-team
    Contributor

    Hello,

    Have you disabled the certification mode to run this test ? else the Join duty-cycle constraint is not honored.

    The regional duty-cycle is not required for AS923.

    This test, only check the join-request backoff duty-cycle, it's to be sure the device does not try to join infinitely if not registered on a network for example.

    Best

  3. sca-l commented on Oct 9, 2025

    @sca-l
    Author

    Hello,

    I didn't disable the certification mode, but this should not impact the backoff test.
    The test steps are only related to join and to count the join requests. No commands to disable Duty Cycle is sent by TCL.
    Why do you refer to Certification mode?

    Could I see the LCTT logs related to the Backoff test for LBM, please? Just to see what I should expect. Thanks.

    Instead, looking the RP02-1.0.4 Specification Table 2: Dynamic channel plan summary, the AS923 has the same indication of RU864 and EU868 for Duty Cycle <1%, so in my understanding the Duty Cycle limitation should be implemented also for AS923.
    Why do you think it should not be done?

    Image

    Thank you, regards,
    Laura

  4. sca-l commented on Nov 4, 2025

    @sca-l
    Author

    Hello,

    Seems also that there is logic to consider the Duty Cycle periods of 1h, 10h and 24h. Seems it is implemented only to cover the 1h period. Any comments on that please?

    Thank you, regards,
    Laura

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions