Nrf router and end device with Digi Xbee Coordinator

[Yash_2]

Hello,

I am using nrf sdk 1.5.1 and trying to connect the Nrf ZigBee router(light bulb example) with Digi Xbee Coordinator but it doesn't seem to connect. I observed the same when I tried to connect nrf end device(light switch example). 

Note - the digi xbee coordinator is tested and working with the digi end device and router

I have attached the sniffer log for more information.

IG_nrfRouter.pcapng

Any help on this is appreciated.

Thanks and Regards,

Yash.

[Jørgen Holmefjord]

Hi,

Have you made sure to fully erase the nRF device before programming the application, to make sure there is no commissioning data stored in flash?

Can you post the application log from the light bulb/switch example, to see if this provides any information about what is failing? You can enable more logs and increase the log level of the application as described in the SDK documentation.

Best regards,
Jørgen

[Jørgen Holmefjord]

Hi,

Can you try the suggestion in this post?

Yash_2 said:

Is there a separate log file that is generated? If yes, can you please help me locate that file?

No, I was referring to the console log output that you see on Putty.

Best regards,
Jørgen

[Yash_2]

Hello Jorgen,

I went through the link you suggested but I am guessing its for NRF5 as I can't locate the functions(zb_start and zb_zdo_set_tc_standard_distributed_key) mentioned in the link and I am working with nrf NCS 52833. Are there any equivalent steps in NCS that I can try?

Thanks and Regards,

Yash.

[Yash_2]

Hello Jorgen,

Any update on this?

Thanks and Regards,

Yash.

[Jørgen Holmefjord]

It seems that the function API is included in NCS as well. Did you include this header file in the sample (#include <zboss_api_zdo.h>)?

I will need to check with our developers regarding the result code from zb_trans_transmit function, but it looks like that should be the correct define you have found.

[Yash_2]

Hello Jorgen,

Can you please elaborate on the API "zb_start",and where can I find that function in the code? and the link keys that are needed for the "zb_zdo_set_tc_standard_distributed_key" where I could find that?

Thanks and Regards,

Yash

[Jørgen Holmefjord]

Hi Yash,

I had our Zigbee developers have a look at the sniffer trace you provided. It shows that the coordinator is not behaving as expected. After the Association Response (and corresponding MAC ACK), coordinator should have sent Transport Key frame with NWK key inside. With that frame missing, association is broken and procedure is restarted later by the joining device.

You need to look into why your coordinator side is not sending the Transport Key frame.

Best regards,
Jørgen

[Yash_2]

Hello Jorgen,

Understood, thank you.

But considering that the coordinator will not send the Transport key, are there any changes(config or code changes) that I can make in the nrf_router/nrf_endDevice that will skip past those transport key steps?

Thanks and Regards,

Yash.

[Yash_2]

Hello Jorgen,

While searching for API's to disable the n/w link key transfers I stumbled upon these API's -

ZBOSS - Compile-time configuration parameters
Link -developer.nordicsemi.com/.../group___z_b___c_o_n_f_i_g.html

#define ZB_ROUTER_SECURITY //Defines router security

And found these as well ->

Would either of those be used to disable the Transport key exchange step?

If not, can you please suggest what changes I can do to make it work?

Thanks and Regards,

Yash.

[run_ar]

Hi,
I am sorry, we are currently a little low on zigbee competence due to vacations (and will be for a couple of weeks). But I will try to forward your question to the developers to see if they can help answer your quesiton. I am sorry for the inconvenience.

[run_ar]

Hi,

Yash_2 said:

But considering that the coordinator will not send the Transport key, are there any changes(config or code changes) that I can make in the nrf_router/nrf_endDevice that will skip past those transport key steps?

Here is the answer I got from the zigbee team when forwarding your question:

I don't think so. First, make sure that Digi Xbee Coordinator is configured correctly so it can work with our Zigbee router.

For example, have the customer enabled securtiy at Xbee device? (Encryption Enable (EE) parameter must be set to 1)

[Smart.Enrg]

Thanks run_ar,

run_ar said:

Here is the answer I got from the zigbee team when forwarding your question:

I don't think so. First, make sure that Digi Xbee Coordinator is configured correctly so it can work with our Zigbee router.

For example, have the customer enabled securtiy at Xbee device? (Encryption Enable (EE) parameter must be set to 1)

I am working with Yash on this. Couple of follow-up questions for the team, if you will please: 
1) Digi Xbee based ZC is a 3rd party device already installed in the field, we are trying to connect 
     nRF52833 based ZED, ZR devices to it. As such, we've limited control over ZC's configuration.
     I mean - we can't change settings (like enable security), that will break things for other devices
     on this otherwise working, deployed network, right?

2) Like your recommendation to enable encryption on ZC side; which I agree with but not allowed
    to do:( - is there a way to disable encryption on our side? - i.e. in nRF52833 nRF Connect SDK
    (preferable), or nRF5 (if we must)?

Please advise. Thanks again.