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.

CC1352P: CC1352P: MT Commands

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

Hello

I’m developing a zigbee coordinator/router communication with CC1352P.

based on the document "z-stack monitor and test api" I have a number of questions

 

  1. What is the MT command to change short address?
  2. What is the MT command to change frequency?
  3. What is the value of TRUE for the MT commands? I tried different values like 00, FF, 01, 0F, but none of them worked to fill the TRUE field.

 

Best regards!

  • Part Number: CC1352P

    Hello

    I’m developing a zigbee coordinator/router communication with CC1352P.

    based on the document "z-stack monitor and test api" I have a number of questions

    1.When I send the MAC_INIT command according to the frame format it would be:

    SREQ: FE 00 22 02 20

    I get a wrong answer

    SRSP: FE 03 60 00 01 22 02 42

    According to the document it would be:

    SRSP: FE 01 62 02 status XOR

    Why this happens if it is an initialization command?

     2.When I send the UTIL_SRC_MATCH_ENABLE command according to the frame format it would be:

    SREQ: FE 00 27 20 07

    I get a wrong answer

    SRSP: FE 01 67 20 F5 B3

    the F5 field corresponds to the status, which in this case would be failure because if it were success it would be 00.

     

    Why this happens if it is an enable command?

     3.When I send the ZDO_EXT_NWK_INFO command according to the frame format it would be:

    SREQ: FE 00 25 50 75

    I get a wrong answer

    SRSP: FE 03 60 00 02 25 50 14

     

    why this happens if it is an information command?

     

    Best regards!

  • Hello Jose,

    1. Short/network addresses are stochastically assigned in accordance with Z-Stack protocol, and are randomly generated by the parent of the joining device.  These cannot be changed by MT commands.  Please see the Network Address Assignment section of the Z-Stack User's Guide
    2. APP_CNF_BDB_SET_CHANNEL, see the Z-Stack Monitor and Test API.
    3. TRUE is one and FALSE is zero, please provide further details on what command is not working and the interface being used.

    1. MT_MAC_FUNC and MT_MAC_CB_FUNC are not defined by default ZNP projects, and are not recommended for customer usage.  You should be using APP_CNF_BDB_START_COMMISSIONING to start the device.
    2. AUTO_PEND is not enabled by default (deprecated functionality) and thus ZMacUnsupported/0xF5 is returned.
    3. This is an error message for MT_RPC_ERR_COMMAND_ID/0x02, so the MT_ZDO_EXT_NWK_INFO case of MT_ZdoCommandProcessing was likely never entered.  You would have to check your ZNP version to discover the cause of this.

    Regards,
    Ryan

  • Hello  Ryan,

    thank you for answering my questions.

    About TRUE, i tested the following commands:

    MAC_RESET_REQ, UTIL_DATA_REQ, SYS_ZDIAGS_CLEAR_STATS, MAC_SET_RX_GAIN_REQ, UTIL_SRC_MATCH_ACK_ALL_PENDING

    so far they have not worked for me

    Where can I check my znp version?

  • Most of these APIs are not supported by the default ZNP configuration (MAC_*, SYS_*, UTIL_SRC_MATCH_ACK_ALL_PENDING) or ignore the boolean parameter (UTIL_DATA_REQ) and thus it does not matter what the value is.  If you are building the ZNP yourself then it would be the SimpleLink SDK version and any changes you've made, otherwise you would need to ask the developer from which you obtained the ZNP firmware.

    Regards,
    Ryan

  • Hello Ryan,

    Thanks for answering the questions, I have one last question

    We want to develop a zigbee application in which we need a coordinator to create a network with 200 routers, with bidirectional communication between coordinator and router through a web application, for this we need fixed short addresses that do not change. That it is configured at runtime and that it is not random, as in the previous questions you already answered me Short/network addresses are stochastically assigned in accordance with Z-Stack protocol, and are randomly generated by the parent of the joining device.  These cannot be changed by MT commands.

    we are currently using CC1352P

    What alternative do you suggest to have a fixed short address, no matter if it is not through MT commands or even if we change the chip?

    Regards,

    Jose

  • Since stochastic addressing is a requirement of the Zigbee 3.0 Specification, the address assignment functionality remains inside Z-Stack source code which developers are not given access to.  You can keep track of devices which have joined the network through incoming ZDO_END_DEVICE_ANNCE_IND messages (routers also send this message upon joining) and/or perform device discovery by sending ZDO_IEEE_ADDR_REQ/ZDO_NWK_ADDR_REQ messages and evaluating the responses.  Please note that if you can alter the router firmware then you may be able to determine an IEEE address, such as zmain_ext_addr performs for SimpleLink devices.  Z-Stack remains suitable for the end use case you've described, but if you are still unsatisfied with this answer then you can also refer to TI 15.4-Stack for which NWK addresses can be determined.  This network however will be limited to sensor nodes and not include mesh networking.  200 nodes is a stretch to support for either networking solution based on the communication intervals, physical barriers, channel frequency interferers (such as Bluetooth/WiFi), etc.

    Regards,
    Ryan

  • Hello Ryan,

    Thanks for your help.

    Regards,

    Jose