• State Verified Answer
  • Replies 22 replies
  • Subscribers 89 subscribers
  • Views 6589 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 265809
Options
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

Pranav3

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.

Parents
  • 0

    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.

  • 0 in reply to Pranav3

    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?

Reply
  • 0 in reply to Pranav3

    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?

Children
  • 0 in reply to Edvin
    Edvin said:
    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

  • 0 in reply to Pranav3
    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

  • 0 in reply to Edvin

    Hello,

    Thank you for your reply. I think I may not have explained you properly. Sorry for that.

    I have attached some screenshots for proper understanding.

    In the first step, I have imported/selected the light_switch example(under zigbee - light_switch)from SDK v1.4.2. 

    In this the path of the example is - C:/Users/Pranav/ncs/v1.4.2/nrf/samples/zigbee/light_switch/build_nrf52833dk_nrf52833

    In the second step, I have followed the same for SDK v1.5.0.

    In this the path of the example is 

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

    I have also tried to enter the path manually in v1.5.0. But it also redirects to Bluetooth/mesh. 

    I also confirmed this issue with my colleague and the same issue occurred on his pc.

    1. About the NCP example 

    I am running the light_control application and NCP connected to my Linux pc. Also tried the same step with my colleague but encountered the same issue.

    Can you please suggest to me some solution by trying it out on your side? 

    Thank you,

    Pranav.

  • 0 in reply to Pranav3

    Oh, I see. When you select zigbee: Light_switch, then the project generator in SES uses the Mesh light switch example:

    Yes. That looks like a bug. Thank you for reporting. I will forward this bug to our developers. 

    As a workaround, you can select the project folder manually, using the 3 dots to the right of the projects selecter:

    and select the folder "v1.5.0\nrf\samples\zigbee\light_switch"

    Best regards,

    Edvin

  • 0 in reply to Edvin

    Hello Edvin,

    Edvin said:

    Yes. That looks like a bug. Thank you for reporting. I will forward this bug to our developers. 

    As a workaround, you can select the project folder manually, using the 3 dots to the right of the projects selecter:

    Thank you for your quick reply. I tried what you suggested here.

    But facing another problem after imported(imported same as you mentioned) the light_switch project.

    nus_cmd.c file is missing in the project.

     

    Also, After building and running the same project. There is no advertisement on the nRF Toolbox application and also it is not joining the network

    In the previous SDK i.e 1.4.2 the nus_cmd file is present and it also visible on the nRF Toolbox i.e working properly to both protocol (BLE + Zigbee)

    Thanks,

    Pranav

Related