This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Problem of connection between Nordic's zigbee device and other Zigbee device

Hi,

I have a problem with a specific Zigbee certified device that I can't connect to my Nordic device.

When trying to connect to the device, I go to see the status:


void zboss_signal_handler(zb_uint8_t param)
{
    zb_zdo_app_signal_hdr_t  * p_sg_p = NULL;
    zb_zdo_app_signal_type_t   sig    = zb_get_app_signal(param, &p_sg_p);
    zb_ret_t                   status = ZB_GET_APP_SIGNAL_STATUS(param);
    zb_bool_t                  comm_status;

    switch (sig)
    {
        case ZB_BDB_SIGNAL_DEVICE_FIRST_START:
        case ZB_BDB_SIGNAL_DEVICE_REBOOT:
            
            if (status == RET_OK)
                        {
                NRF_LOG_INFO("Joined network successfully");
                bsp_board_led_on(ZIGBEE_NETWORK_STATE_LED);
            }

and it is equal to -1, so it is not RET_OK.

It's the first time that I have this problem of interoperability. Is it necessary to do something specific so that the Nordic device is visible from any other Zigbee device?

Best regards,

Raffaela

  • Now I see a very strange behaviour: by the sniffer log, you can see that the connection is happened but, in the zboss_signal_handler, I see the status = -1 so the connection is not happened. How is this possible?

    I tried to use also this function "zb_bdb_set_legacy_device_support(0);" but it doen't help. The ERASE_PERSISTENT_CONFIG is set to ZB_FALSE.

    Thank you, 

    Raffaela

  • Hi Raffaella,

    The signal change once the TCLK exchange is completed, but this is not despicted in the screenshot. Could you please send me the whole traffic dump and not just a screenshot? Please use .pcapng file format if possible.

    Best regards,

    Marjeris

  • Hi Marjeris,

    Sorry for the late response. I have the whole traffic dump, but not in .pcapng but in .psd format: I use the CC2531 TI Dongle and the software "Texas Instrument Packet Sniffer". I hope that it is useful.

    I continued to do other tests and noticed that if I set the Zigbee channel of the device I'm building (I usually use the define ZB_TRANSCEIVER_ALL_CHANNELS_MASK to make the device visible in all channels), it happens that the device tries to connect for good 8 times with different short addresses, although the endpoint is always the same.

    Thank you,

    Raffaela

    Data_Sniffer_20191104.psd

  • Hi Marjeris,

    By carefully monitoring the Zigbee traffic, I noticed that this message is missing and is not sent from my device when trying to make a connection (This superframe is sent by an other device that works fine with all the Zigbee devices):

     How can I enable superframe sending?

    Thank you,

    Raffaela

  • Hi Raffaela,

    Unfortunately I am not familiar with Texas Instrument Packet Sniffer. Could you be so kind of setting up nRF Sniffer for 802.15.4 and sending the sniffer trace using Wireshark?

    The last packet you send looks like a frame with an association permit, sent from another node in the network (not the coordinator), but this doesn't say too much to me.

    Can you please explain more about the context of the situation? What does the topology of the network look like? What kind of coordinator are you using? Does the coordinator support network steering commissioning? Is the coordinator sending an association response to the router? Do they interchange keys?

    Best regards,

    Marjeris

Related