Coordinator problems during commission of 40 devices

RE: Coordinator problems during commission of 40 devices

Elfving — Fri, 08 Dec 2023 09:04:01 GMT

[quote user="Marco_A"]Ok, thank you, now I'm a little busy, I'll try the workaround as soon as possible![/quote]

Great! :) Let me know if it helps. Otherwise I guess it would work to simply reset it when the nRF doesn't respond, though hopefully we'll avoid doing it that way.

Regards,

Elfving

RE: Coordinator problems during commission of 40 devices

Marco_A — Thu, 07 Dec 2023 16:05:06 GMT

[quote userid="103347" url="~/f/nordic-q-a/105786/coordinator-problems-during-commission-of-40-devices/458537"]Have you also tried the other configuration alternatives listed by sebr here to see if any helped? [/quote]

Hi Elfving, yes I've tried to use the configuration alternatives, and with:

CONFIG_NRF_802154_RX_BUFFERS set to 64
ZB_CONFIG_IOBUF_POOL_SIZE defined to 127U
ZB_CONFIG_SCHEDULER_Q_SIZE defined to 127U

some devices were able to join in the network, but only about 10 of 50..
After the Nordic seems blocked and only with a reset is possible to recover it.

Now I resolved with a "ping" from my main microcontroller to the Nordic. When he doesn't answer, I reboot it, and I open the Zigbee network again. Some devices at the time, I am able to join all devices.

[quote userid="103347" url="~/f/nordic-q-a/105786/coordinator-problems-during-commission-of-40-devices/459373"]If you do get asserts, it might be that you've gotten the known ZigBee issue KRKNWK-12115. The link describes issues in nRF Connect SDK, but the corresponding ZBOSS stack is also being used in Zigbee SDK 4.2, so it should still be relevant to you.[/quote]

Ok, thank you, now I'm a little busy, I'll try the workaround as soon as possible!

RE: Coordinator problems during commission of 40 devices

Elfving — Thu, 07 Dec 2023 13:42:22 GMT

Hello Marco,

If you do get asserts, it might be that you've gotten the known ZigBee issue KRKNWK-12115. The link describes issues in nRF Connect SDK, but the corresponding ZBOSS stack is also being used in Zigbee SDK 4.2, so it should still be relevant to you.

Could you try implementing the workaround described there and see if it helps?

Regards,

Elfving

RE: Coordinator problems during commission of 40 devices

Elfving — Fri, 01 Dec 2023 13:42:49 GMT

Sorry about the delay Marco

Any development in the issue from your side?

[quote user="Marco_A"]How can I do to see the assert messages?[/quote]

It should pop up along with the log if there are any asserts, I guess that is what you get on UART. If you are not seeing any when trying to add these devices then my guess is that this is similar but not exactly the issue described in the other case.

Have you also tried the other configuration alternatives listed by sebr here to see if any helped?

Regards,

Elfving

RE: Coordinator problems during commission of 40 devices

Marco_A — Fri, 24 Nov 2023 13:04:52 GMT

How can I do to see the assert messages? Now I see only my debug print on uart.

RE: Coordinator problems during commission of 40 devices

Elfving — Fri, 24 Nov 2023 12:59:24 GMT

I see. So I take it that you do not have the same asserts as where described in the other case?

Regards,

Elfving

RE: Coordinator problems during commission of 40 devices

Marco_A — Fri, 24 Nov 2023 06:47:23 GMT

Hello Elfving,
I have the problem only when I switch on all the devices together and the auto join starts.
If I add the devices without auto join, I don't have problems.

I have already used that custom configuration with:

#define ZB_CONFIG_SCHEDULER_Q_SIZE 127U
#define ZB_CONFIG_IOBUF_POOL_SIZE 127U

Whit this type of configuration, some devices were able to join in the network (about 10 on 50 devices), but then the coordinator doesn't send or receive messages anymore.

RE: Coordinator problems during commission of 40 devices

Elfving — Thu, 23 Nov 2023 14:44:26 GMT

Hello again, and sorry about the wait. Things have been a bit busy lately.

[quote user="Marco_A"]Unfortunately, this project is very large and too close to market launch, so at this moment, it's impossible for us think a migration from Sdk 4.2 to SDK connect[/quote]

Understandable. And we will still try to help you of course.

[quote user=""]

My problem is very similar at this topic:

[/quote]

So the case you linked to is also similar in the fact that if you add the devices slowly, you get less issues adding them? Do you run into the same assert that they do in the other case, or only the situation where you do not get any events?

Could you try it with this memory config?

devzone.nordicsemi.com/.../5314.zb_5F00_mem_5F00_config_5F00_custom_5F00_max.h

Regards,

Elfving

RE: Coordinator problems during commission of 40 devices

Marco_A — Fri, 17 Nov 2023 10:24:35 GMT

Good morning Elfving, thank you for your reply.
I know it, and we use the NRF Connect SDK on the other our Zigbee devices.
Unfortunately, this project is very large and too close to market launch, so at this moment, it's impossible for us think a migration from Sdk 4.2 to SDK connect.

RE: Coordinator problems during commission of 40 devices

Elfving — Fri, 17 Nov 2023 10:08:22 GMT

Good morning Marco,

[quote user=""]I'm developing a Zigbee Coordinator with the nrf52840 and SDK 4.2. [/quote]

First of all, if this is a new development for new devices, I would recommend you to switch to the nRF Connect SDK for this development.

Here is one reason, though another is that the Zigbee SDK is not just old, but deprecated.

Regards,

Elfving