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

Use of NCP in Zigbee

Hello,

I am using nRF52833, nRF Connect SDK  v1.5.0.

In v1.5.0 there is one new example i.e Zigbee NCP. ( Zigbee: NCP — nRF Connect SDK 1.5.0 documentation (nordicsemi.com)..)

In the above link, NCP and coordinator are both used for testing.

I'm not understanding what is the use of NCP.  I am confused between the use of coordinator and NCP.

Can you please explain to me why and in which case NCP required?

What is the difference between NCP and coordinator?

Thank you,

Pranav.

  • Hello,

    NCP stands for Network Co-Processor. Basically, it is used if you want to run the stack on another chip, and just use the nRF as the radio. So the Zigbee stack is split in two pieces. NCP and the rest. "The rest" is running on another chip, and sends commands to the NCP to tell it what to send over the air, and the NCP reports back with events from the radio to the application chip.

    The NCP can either be a coordinator or a normal node (router or end device). 

    Best regards,

    Edvin

  • Hello,

    Understood. Thank you for your quick reply. I have encountered two problems while testing,

    1. With the help of this link Zigbee: NCP — nRF Connect SDK 1.5.0 documentation (nordicsemi.com) and Readme file under ncp_sdk_v0.9.3. I        tried to test the NCP example. But after completing all the steps under testing, my light control device doesn't join the Zigbee network. It doesn't show any led indication on board. 

    2. Also tried to test the (SDK v1.5.0) Zigbee network_coordinator, light_switch,light_bulb example but after building while testing it  light_switch doesn't respond. Doesn't show any led indication and not joined the network. Previously, I tested the same scenario with SDK v1.4.2 its works fine there.  

    Can you please help me to resolve this issue?

    Thanks,

    Pranav.

  • Pranav3 said:
    2. Also tried to test the (SDK v1.5.0) Zigbee network_coordinator, light_switch,light_bulb example but after building while testing it  light_switch doesn't respond. Doesn't show any led indication and not joined the network. Previously, I tested the same scenario with SDK v1.4.2 its works fine there.  

     Does the logs from the nRFs say anything?

    Try erasing all boards completely using "nrfjprog --eraseall" (nRF command line tools is needed for this) and re-program them.

     

    Pranav3 said:
    1. With the help of this link Zigbee: NCP — nRF Connect SDK 1.5.0 documentation (nordicsemi.com) and Readme file under ncp_sdk_v0.9.3. I        tried to test the NCP example. But after completing all the steps under testing, my light control device doesn't join the Zigbee network. It doesn't show any led indication on board. 

     

    Is your NCP connected to anything physically? What is running the application?

  • Pranav3 said:
    2. Also tried to test the (SDK v1.5.0) Zigbee network_coordinator, light_switch,light_bulb example but after building while testing it  light_switch doesn't respond. Doesn't show any led indication and not joined the network. Previously, I tested the same scenario with SDK v1.4.2 its works fine there.  

     Does the logs from the nRFs say anything?

    Try erasing all boards completely using "nrfjprog --eraseall" (nRF command line tools is needed for this) and re-program them.

    Thank you for your quick reply. I tried what you suggested. But facing the same problem.

    While comparing both SDK i.e v1.4.2 and v1.5.0 I came to know that path for the light_switch example in v1.5.0 is different than v1.4.2

    v1.4.2 - C:/Users/Pranav/ncs/v1.4.2/nrf/samples/zigbee/light_switch/build_nrf52833dk_nrf52833

    v1.5.0 - C:/Users/Pranav/ncs/v1.5.0/nrf/samples/bluetooth/mesh/light_switch/build_nrf52833dk_nrf52833 

    Also after building the v1.5.0 light_switch example, When I am trying to connect "nRF Toolbox" it shows a message -  "The device does not have the required services" 

    Also in v1.5.0 light_switch example, there is  modle_handler.c instead of  nus_cmd.c . In v1.4.2 light_switch example there is nus_cmd.c file is present.

    So can you please look into it?

    Thank you,

    Pranav

  • Pranav3 said:

    While comparing both SDK i.e v1.4.2 and v1.5.0 I came to know that path for the light_switch example in v1.5.0 is different than v1.4.2

    v1.4.2 - C:/Users/Pranav/ncs/v1.4.2/nrf/samples/zigbee/light_switch/build_nrf52833dk_nrf52833

    v1.5.0 - C:/Users/Pranav/ncs/v1.5.0/nrf/samples/bluetooth/mesh/light_switch/build_nrf52833dk_nrf52833 

     These are not at all the same examples. The one from 1.4.2 is zigbee, and the other is bluetooth mesh. That is like comparing carrots and cars.

    Try looking into ncs\v1.5.0\nrf\samples\zigbee\light_switch

Related