About the mesh configuration failure

RE: About the mesh configuration failure

Jui-Chou (Rick) Chung — Wed, 18 Apr 2018 10:55:33 GMT

Hello caca1989,

Great to hear that it works :)

No, we don't have to enlarge this parameter because of we are going to add more servers.

Since this parameter is for allocating the scanner buffer for receiving ADV packets. If the size of the scanner buffer is not large enough and also there are lots of ADV in the environments, scanner buffer will be filled to full easily.

RE: About the mesh configuration failure

caca1989 — Wed, 18 Apr 2018 10:36:52 GMT

Rick Chung,

thank you very much！

the SCANNER_BUFFER_SIZE modified to 1024, 2server can be configured successfully, but I need

more servers, such as 50 servers, then the SCANNER_BUFFER_SIZE takes up too much space, there

are other more effective way? I'm afraid of 50 servers this value is too big

RE: About the mesh configuration failure

Jui-Chou (Rick) Chung — Tue, 17 Apr 2018 11:45:23 GMT

Hello caca1989,

Are there lots of device advertising on your site? I would assume there may be too many devices advertising at the same time which interference the configuration procedure.

I would like to suggest you modify the SCANNER_BUFFER_SIZE in nrf_mesh_config_bearer.h from 512 to 2048, recompile and program to see if this can do help : )

RE: About the mesh configuration failure

caca1989 — Tue, 17 Apr 2018 09:53:11 GMT

Hello RIck Chung，

but. After I successfully configured the first server, I shut it down and then powered on the second server. In this case, the second server can be configured successfully! Feel the configuration is disturbed by the first server!

RE: About the mesh configuration failure

Jui-Chou (Rick) Chung — Tue, 17 Apr 2018 09:13:30 GMT

Hello caca1989,

Does it mean after you erase both of the servers and client, and run the demo again, you still can only finish configuration for one server, and always failed on configuring the second one?

RE: About the mesh configuration failure

caca1989 — Tue, 17 Apr 2018 09:06:24 GMT

Hi Rick Chung,

Thank you for your reply, I've tried the method you mentioned, but this is not the reason!

RE: About the mesh configuration failure

Jui-Chou (Rick) Chung — Tue, 17 Apr 2018 08:18:30 GMT

Hello caca1989,

Since you are running NUS and mesh concurrently, I would like to suggest you extend the advertising interval and also the connection interval to be more than 100 ms to avoid the collision of mesh packets.

And in the current light switch example, once if the configuration procedure failed, it would be a little hard to recover.

Would you please erase and re-program both of light swtich client and server, and check if the error still happen?