This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2652P: ZED still sends data requests when no network is open

Part Number: CC2652P
Other Parts Discussed in Thread: Z-STACK

SDK: simplelink_cc13x2_26x2_sdk_4_40_04_04

ZED sends data requests even when there's no open network for joining. Why?

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/158/_985BB965_20210603_5F00_1.cubx

BR,

Shuyang

  • Hi Shuyang,

    How does the customer replicate this issue using an out-of-box example?  I only see a single Beacon Request each time I try to start commissioning with a v5.10 ZED.  Please have them factory reset or re-flash devices to see if the behavior changes.

    Concerning the sniffer log, the MAC sequence numbers of Beacon Requests are widely different which indicate that multiple ZEDs are attempting to join a network.  The Data Requests also seem to come from a different source, albeit a TI device as determined through the IEEE address, and may not be the device they are attempting to monitor.

    Regards,
    Ryan

  • Hi Ryan,

    The MAC addr of data req can confirm that the ZED is the device we are testing.

    The example we use is an out-of-box example of V4.40.

    In the example, we turned on MANAGED_SCAN and activated all channels (this causes the MAC sequence numbers of beacon req to be discontinuous in the sniffer).
    Then we power on and start a 2-second timer to periodically execute commissioning.


    We added debugging information in ZDO_beaconNotifyIndCB(), ZDApp_NwkDescListProcessing(), ZDO_NetworkDiscoveryConfirmCB(uint8_t status) respectively.
    When the problem recurs, ZDO_beaconNotifyIndCB() and ZDApp_NwkDescListProcessing() show no available network and the status codes in ZDOCBApp_NwkListProcessing() is 0xEA (ZMacNoBeacon).

    Regards,

    Howjie

  • Hi Howjie,

    I tried performing a similar setup with v5.10 but was not able to recreate the behavior you are describing.  Can you please perform a test with the latest SDK to see whether it persists on this version?

    I spoke with the Software Development Team and found that additional Data Request behavior on channel 11 has persisted in Z-Stack for a few quarters now from default PIB parameters (which is why 0xFFFE is the destination address).  It should not have anything to do with MANAGED_SCAN, but this function has not been tested for several years.

    I hope this insight is able to assist you further into your mitigation of the issue.

    Regards,
    Ryan

  • Hi Ryan,

    Our application scenarios are more sensitive to power consumption.
    This problem will generate a higher current consumption(lasts about 2 seconds) and it causes our device to work abnormally.

    Is there a way to workaround this problem?
    For example, interfere with the MAC's RF Tx queue or adjust the mac layer retransmission when the problem occurs?

    Regards,

    Howjie

  • Howjie,

    I am not aware of a workaround at the moment.  The greater hinderance to power consumption is performing a managed scan on all active channels.  Unless you've changed the pre-defined settings, I expect the managed scan length (150 ms * 16 channels = 2400 ms) to exceed your commissioning interval (2000 ms).

    Regards,
    Ryan

  • Hi Ryan,

    ZDOManagedScan_Next();
    ret = NLME_NetworkDiscoveryRequest( managedScanChannelMask, BEACON_ORDER_15_MSEC );

    Commissioning is executed every 2 seconds, and managedScanChannelMask only represents one channel when NLME_NetworkDiscoveryRequest() is called, which means that 16 channels are not scanned within 2 seconds.

    According to your information inform in the previous reply, 0xFFFE is an invalid destination address. Based on this, it is easy to detect an abnormality and terminate the frame transmission.

     

    Regards,

    Howjie

  • Hi Howjie,

    Thanks for further explaining.  I've provided your feedback to the Software Development Team.

    Regards,
    Ryan