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.

CC2538: ZED could not get replied in MTO

Part Number: CC2538
Other Parts Discussed in Thread: CC2530, TEST2

Hi  Team,

A customer found some strange problems when testing MTO.  He used CC2538 as coordinator and CC2530 as ZED, the stack version was 3.0.2. These devices were switches and sockets distributed in several rooms, the total number was 37. After a while, some ZED devices would get no response from his father or coordinator. Details:

1.The router would not retransmit abnormal ZED's message, he tried multiple router, all the same phenomenon.

2.The broadcasted message "route request", the abnormal ZED could not send out data whether received or not received this MTO message.

3.If the abnormal ZED sent "route request", not device would retransmit to get to the coordinator.

Please check the attached capture file, in this case,the not-working-ZED's address is 0859(long address:00:12:4B:00:13:5D:6B:74)

0083.test2.rar

  • Hi Viki,

    The device with short address 0x0859 identifies as a Zigbee Router in the sniffer log as compared to a Zigbee End Device.  This is important terminology to differentiate between since ZEDs do not route packets or respond to broadcast messages,

    Is the ZC the MTO concentrator (CONCENTRATOR_ENABLED) and what other compile options (CONCENTRATOR_*,  MAX_NEIGHBOR_ ENTRIES, etc.) have been changed for both ZC and ZR roles to allow for this large network?  You can reference SWRA427 and Section 5.4 of the Zigbee Developer's Guide to further understand Many-To-One Routing Protocol.

    Regards,
    Ryan

  • Hi Ryan,

    The 0x0859 is indeed a router device, sorry for the mistake.

    He already referred the SWRA427, here's some settings of  compile options :

    CONCENTRATOR_ENABLE was set to 1 in concentrator;

    CONCENTRATOR_ROUTE_CACHE  was set to 1;

    MAX_NEIGHBOR_ ENTRIES was set to 3 in coordinator, and 40 in router.

  • Hi Viki,

    If these are the only changes then they need to increase MAX_RTG_SRC_ENTRIES and ZDSECMGR_TC_DEVICE_MAX on the ZC as well.  I would recommend re-testing after applying most routing changes from SWRA427 and SWRA650.

    Regards,
    Ryan