• State Not Answered
  • Replies 1 reply
  • Subscribers 67 subscribers
  • Views 48 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 335878
Options

Issue of Thread reader device remove child device

Tom.Fu

Hi Support team

Application:

1) We have a Thread network of one leader and 12 child and all of notes run BLE and Thread at the same time.

2) BLE center on the leader is used to connect the BLE peripheral on the child for child commissioning  one by one.

3) All commissioned child devices send 12bytes by UDP per 250ms to leader. 

Issue:

1) Many child devices are removed and reconnected repeatedly during leader BLE connect next child device for commissioning.

2) Many child devices are removed and reconnected repeatedly after all child devices has been commissioned.

Could you help us to analyze what's the reason and how to resolve it?

Parents
  • 0

    Hi,

    Since both BLE and Thread operate on the 2.4GHz band, they can cause interference when devices attempt to "run BLE and Thread simultaneously," both among themselves and with several other similar devices work intensively.

    If you are using the Multi-Protocol Service Layer (MPSL) to manage both, a notable challenge arises from BLE scanning. This operation requires significant time to process Bluetooth LE traffic, potentially blocking 802.15.4 traffic or be blocked.

    To address this, it is recommended to use the Sleepy End Device role for Thread or Zigbee applications when BLE scanning is active.

    Given that your Thread leader is communicating with 12 devices, the remaining time for BLE communication could become a critical limitation, you may incread UDP tranfering interval and decrease child amount to verify.

    Best regards,

    Charlie

Reply
  • 0

    Hi,

    Since both BLE and Thread operate on the 2.4GHz band, they can cause interference when devices attempt to "run BLE and Thread simultaneously," both among themselves and with several other similar devices work intensively.

    If you are using the Multi-Protocol Service Layer (MPSL) to manage both, a notable challenge arises from BLE scanning. This operation requires significant time to process Bluetooth LE traffic, potentially blocking 802.15.4 traffic or be blocked.

    To address this, it is recommended to use the Sleepy End Device role for Thread or Zigbee applications when BLE scanning is active.

    Given that your Thread leader is communicating with 12 devices, the remaining time for BLE communication could become a critical limitation, you may incread UDP tranfering interval and decrease child amount to verify.

    Best regards,

    Charlie

Children
No Data
Related