lightcontrol demo in Bluetooth Mesh SDK v0.9.1-alpha, why is there "Not in RUNNING state" on RTT?

RE: lightcontrol demo in Bluetooth Mesh SDK v0.9.1-alpha, why is there "Not in RUNNING state" on RTT?

Thomas Stenersen — Mon, 31 Jul 2017 06:23:15 GMT

Hi Ameer,

Setting the SERVER_COUNT to 1 works if you have less than three servers available. Note that other parameters in the nrf_mesh_config_app.h in the examples/light_control/client/include directory aren't scaled with the SERVER_COUNT. E.g., with only one server, you really only need 1 element, 2 models (configuration client and 1 light control client) and 1 device key.

Best,
Thomas

RE: lightcontrol demo in Bluetooth Mesh SDK v0.9.1-alpha, why is there "Not in RUNNING state" on RTT?

kren — Mon, 31 Jul 2017 05:18:04 GMT

After re-flashing servers firmware, they can work well, one client and three server. Thanks for the help.

RE: lightcontrol demo in Bluetooth Mesh SDK v0.9.1-alpha, why is there "Not in RUNNING state" on RTT?

kren — Sun, 30 Jul 2017 23:50:15 GMT

I think it's a good idea, I may try to set SERVER_COUNT as 2. Thanks.

RE: lightcontrol demo in Bluetooth Mesh SDK v0.9.1-alpha, why is there "Not in RUNNING state" on RTT?

Ameer.Sheik — Sun, 30 Jul 2017 13:51:20 GMT

Hi kren,

while testing following Demo "lightcontrol demo in Bluetooth Mesh". i am also facing same issue then i did some small changes in source code then it working properly

in the Client side program i did the change in "#define SERVER_COUNT (3)" instead of 3 i put 1 because i am using two nRF51-DK board..then it working fine

Note

@Nordic Developer Zone Community member please correct me if i did anything is wrong in above code changes

Thanks

Ameer

RE: lightcontrol demo in Bluetooth Mesh SDK v0.9.1-alpha, why is there "Not in RUNNING state" on RTT?

Thomas Stenersen — Sat, 29 Jul 2017 09:38:51 GMT

Hi kren,

From the client log, it seems like only two servers are being provisioned and configured. The client will not transition to the running state until all three servers are provisioned and configured.

Could one of the servers have a pre-stored configuration? If the applications are compiled with #define PERSISTENT_STORAGE 1, provisioning data will be stored in flash and not erased across power cycles. Use

nrfjprog -e

on each device to erase all the flash memory, then re-flash the firmware again.

Best,
Thomas