Command List for ZE51-2.4 and Sequence of intialization for both Coordinator and End Device

11 thoughts on “Command List for ZE51-2.4 and Sequence of intialization for both Coordinator and End Device

  1. Hello Sir/madam,

    1. I have ‘Telit_ZigBee_PRO_Democase_User Guide_r5.pdf’ available with me but it seems that it doesn’t have the list of all the commands, if so please share the document that has the list of all the commands.

    2. Please share the below mentioned information for creating a small network consists of a Coordinator and 3 end devices. Like:

        i. Configuring and initalizing the coordinator (what is cluster Id and network Id? do I need to set these Ids for the above said simple network?)

        ii. Configuring the initalizing all the 3 end devices

        iii. Establishing a network having a coordinator and 3 end devices

        iv. Data exchange between coordinator and 3 end devices

        v. Where is the device Id mentioned? If I want some data from device number 2 ? 

        vi. How can a end device leave network?

    3. Is there some extra space in the ZE51 module available to handle firmware upgrade, to store the firmware locally in the module then start upgrading the host microcontroller’s firmware later on? 

    4. What is Application Frame Direct Request?  

     

    Thanks 

  2. Hi

    ZE
    module can not be managed via AT command as other protocol, but or via
    SRManager tool or via function described into ZE protocol user guide

    I have ready a sample of AF direct communication (AF it is the fast and easier system to put modules in communication)

     

    1. Hello Cosmin,

      Thanks for the reply!

       

      I have to interface our host controller with the telit ZE51-2.4 using UART.

       

      I understand that I need to send stream of bytes containing Function Code, Arguments and other ZigBee parameters over UART and need to wait for confirmation.

       

      OR

       

      Do I need to include some libraries in my project and call the functions (APIs) described into ZE protocol user guide directly in my application?

       

      Please clearify. 

    2. Hello Cosmin,

      I need to interface my host controller with Telit ZE51-2.4 using UART.

       

      I understand that I need to send stream of bytes containing Function Code, Arguments and other ZigBee parameters over UART and wait for the confirmation.

       

      OR

       

      Do I need to include some libraries in my project and call the functions described in ZE protocol user guide directly?

       

      Please clearify. 

  3. Hi 

    yes, you could manage the module with your micro connected to the serial


    In order to do it we released a doc (attached) with a lot of primitives, useful to configure and manage the network.


    Before all you have to program the module with the appropriate SW, Coord, Router and End Device.


    Otherwise we provide a Demokit with modules already programmed. 


    By this DEmo you can have an idea about the use of Telit module and a guide to start development of your own application.

    1. Hello Cosmin,

      I have got the demo boards with me and am able to create a small network.But the attached document (Telit_ZigBee_PRO_Democase_User_Guide_r5.pdf) doesn’t seems to have all the required information for developing my own application. Do you have some other document (you mentioned in your previous reply :: guide to start development of your own application) which explains the sequence of configuration, intialization of the modules and then start data exchange, please provide.

       

      I have following queries

       

      1. In Application Frame Direct Request what are Destination End Point, Source End Point and txOption fields meant for?

      2. What are bind(0xD8)/unbind(0xDA) requests used for? Aren’t they required for joining or leaving the network?

       

       

       

       

       

       

       


       

       

  4. I had following queries too: 

    1. In Application Frame Direct Request what are Destination End Point, Source End Point and txOption fields meant for?

    2. What are bind(0xD8)/unbind(0xDA) requests used for? Aren’t they required for joining or leaving the network? 

    3. Are the steps described in ‘Telit_ZigBee_PRO_Democase_User Guide_r5.pdf’ enough for initalizing and configuring Coordinator and End-Devices in a star topology?

    4. Is there some extra space (memory) in the ZE51 module available to handle firmware upgrade, to store the firmware locally in the module then start upgrading the host microcontroller’s firmware later on?  

    Please answer all the 4 questions with heading.

    1. I had following queries too:

       

      1. In Application Frame Direct Request what are Destination End Point, Source End Point and txOption fields meant for?

       

      Tx option: are optional byte to add in tx mode:

      example: 

      Bit 0: encrypt request

      Bit 2: APS ack

      Bit 3: Frag

       

      2. What are bind(0xD8)/unbind(0xDA) requests used for? Aren’t they required for joining or leaving the network? 

      Yes 0xD8 it is for bind a remote device with another remote device

      0xDA it is need for unbind request.
       
       

  5. 1. How can I fix the Network Address (command number to invoke mgt_zdoChangeNwkAddress() on UART) of the ZE51-2.4 module?

    2. There are two low power modes defined in the data sheet

         i. Std-by: 2 MicroAmp

         ii. Sleep: 1 MicroAmp

     It seems only Sleep mode is discussed in Democase Useer Guide. Please provide information about Std-by Mode and ways of exiting the Std-by mode. 

     

    1. Hi
      in order to manage the MGT interface I suggest refer to chapt. 3.9 of Z-One PRO Protocol user guide (page131 and >).
      Other info about command code and behaviour are available on Zig Bee PRO Democase User Guide (page 34 and >).
      Doc are in attachment
      About Stand by mode it is HW low power, in order to manage it you have to set logical on Stand by pin:
      logical 1: module in operating mode
      logical 0: module in stand by period.