What does Unimplemented signal 54 , 50 etc. message mean.

[JorgenM]

Hello,

Using nrf Connect SDK v1.9.1 
Zigbee nrf52840 -DK and Nordic Zigbee coordinator sample.

When in terminal sending command BDB START I get " I: Unimplemented signal (signal: 54, status: 0)" when network steering is finished..
I also get similar messages with sending some ZCL commands but with other "signal numbers" (signal: 50, status: 0)

In what file can I find these "signals" 54 , 50 described ?
Any suggestion what causes this and how to fix?

Thank you,

Jorgen

[AHaug]

Hi Jorgen, 

Did you do any modifications to the coordinator sample? I will see if I can recreate this behaviour tomorrow

Kind regards,
Andreas

[JorgenM]

A few mods: In Kconfig zigbee channel = 11 We also tuned on SoC chip usb port for Shell terminal access.
I believe the original coordinator example give same message. 
I don't think you need to recreate it.
Question is more general about how I find out what/where those messages are related to?
Where is "signal 50" defined? Where in the code / what file etc?
Thx!
Jorgen

[AHaug]

Hi again!

Yeah, there is no need for recreating this. These infomessages are generated by the ZigBee Signal Handler, and as you stated comes when running the original coordinator as well.

Information about these types of messages should be written in the API  about https://developer.nordicsemi.com/nRF_Connect_SDK/doc/zboss/3.11.2.0/group__zb__comm__signals.html#gacc1a886ff943f210eff635655bb2ab84 and https://developer.nordicsemi.com/nRF_Connect_SDK/doc/zboss/3.11.2.0/group__zb__comm__signals.html#gaf2b7d7aafb092dcd775411ff0c56afe7

Let me know if this answers your question,

Kind regards,
Andreas

[JorgenM]

Thank again for attention to this.

Hmm... I don't know how I would even find related signal handler info for this unless I scan through all the docs...?
A search on "54U" or any "signal numbers" in api docs won't work.

Anyway, any idea how to fix this in Coordinator?

Signal 50U and 54U seem to pop up a lot.

Thx, Jorgen

[AHaug]

Hi, 

Those messages shows up as Information message (Log_INF). They are triggered by a case in the signal handler function "void zboss_signal_handler(zb_bufid_t bufid)". I were not able to pinpoint the exact trigger for that message today, but the following files should give some more insight about specifically what cases triggers this information logging. I have also asked some of my colleagues if they know that specific trigger and will come back with a reply if I hear from them

1. zigbee_app_utils.h located at <ncs_location>\v1.9.1\nrf\include\zigbee
2. zigbee_app_utils.rts located at <ncs_location>\v1.9.1\nrf\doc\nrf\libraries\zigbee
3. zigbee_app_utils.c located at <ncs_location>\v1.9.1\nrf\subsys\zigbee\lib\zigbee_app_utils

Kind regards,
Andreas

[JorgenM]

Thanks!

I will take a look at these files and hopefully I can figure out why I get this message.