adding second element to a light control server node mesh example

RE: adding second element to a light control server node mesh example

ms3412amo — Wed, 06 Sep 2017 14:34:35 GMT

Thank you for this information. It will help for sure.

RE: adding second element to a light control server node mesh example

Thomas Stenersen — Wed, 06 Sep 2017 07:11:14 GMT

Hi ms3412amo,

The light control client example is unfortunately not made as a general purpose provisioner as you've discovered. It's assuming that the node it's provisioning is a light control server with only one element and one simple on off server model. In other words, multiple elements and models is supported, it's just not integrated into the provisioner example.

To make it work for multiple elements and multiple models, there are as Hung pointed out a couple of changes to be made:

When the provisioner receives the NRF_MESH_EVT_PROV_CAPS_RECEIVED event, it needs to inspect the num_element variable and store it for the device currently being provisioned. As you may know, when being provisioned a device is assigned a range of unicast addresses: [unicast_start, ..., unicast_start + num_elements - 1]. The provisioner needs to store the a publication address for each of the elements in the newly provisioned node to talk to them.
When configuring the device, in the config_client_event_cb(), the CONFIG_OPCODE_COMPOSITION_DATA_STATUS event gives the composition data of the node. It details the structure of the elements and models of the node. This can be used to know what models are present and configure the correct keys and publication state for them.

I understand that this is a lot to take in, the mesh provisioner can get quite complex. I would advise you to read the How to build a network guide on the infocenter for an introduction to the provisioning and configuration process in Bluetooth Mesh. Otherwise the official Bluetooth Mesh profile specification is not a terrible read.

Hope this helps,
Thomas

RE: adding second element to a light control server node mesh example

ms3412amo — Tue, 05 Sep 2017 15:55:39 GMT

Hi, thank you for your answer. I finally added more opcode and callback to simple_on_off_model to control more than just an output. It's working fine, but I would like to have to ability to add elements in a node in a near future. I understand the Mesh specification is new and some features still need to be implemented in Nordic Mesh SDK.

RE: adding second element to a light control server node mesh example

Hung Bui — Tue, 05 Sep 2017 15:18:40 GMT

Hi ms, Sorry for late response.

It doesn't seem the current provisioner in the lighting example check for the number of elements (num_components or num_elements) in the capability sent by the provisionee. The number of element is reported back to the provisioner in NRF_MESH_EVT_PROV_CAPS_RECEIVED event (event.params.prov_oob_caps_received.oob_caps.num_elements = p_pdu->num_components;) but doesn't seem this value is used by the provisioner. Also the provisioner doesn't seems to assign the application key to the second server. I will report this issue internally.

RE: adding second element to a light control server node mesh example

ms3412amo — Tue, 29 Aug 2017 18:37:10 GMT

Hi Petter, I'm on client's project, assuming my server is OK. Do I need to change provisioner.c code to access 2 elements in a same node. In main.c access_setup seems ok to me without any change. I try this with 2 devkits, 1 clients(devkitA) controlling 2 servers in the same node(devkitB). I got the first LED working with button0 from devkitA, but I got APP_ERROR code 7 on ERROR_CHECK(status) at the end of button_event_handler when I try button1 to control the second LED (second element in the node). I suspect provisioning not binding the 2 elements to the clients model. I'm almost at a point to try adding a second led in the simpleOnOffModel, with more opcode and callback of opcode to control the other led, but I would prefer to understand adding a element with the same model before customising simpleOnOff model. Thank you

RE: adding second element to a light control server node mesh example

Petter Myhre — Mon, 28 Aug 2017 10:57:18 GMT

Seems to me like you have two elements with a Simple OnOff model in each, and your approach is correct. With regards to simple_on_off_server_init(), it should be okay to call it twice, as long as it is on different elements. If you have any more specific questions, let me know, I'll try to answer.

RE: adding second element to a light control server node mesh example

ms3412amo — Thu, 24 Aug 2017 14:34:51 GMT

It was in ERROR_CHECK(access_model_subscription_list_alloc(m_server1.model_handle)); on the second call of this function because I declare two m_serverX, one per element. That was because my ACCESS_MODEL_COUNT was set to 2 (one config model and one simple_on_off) instead of 3 (1 config and 2 simple_on_off), I don't have this error anymore, I got provisioning message on RTT, so.. Now I still have to check on client's code side to map button function to control the second LED on this the server. But as I wrote above, I still not sure about my server code, I'm not sure I really have 2 elements with a simple_on_off_model in each. I'm working on this today. If you have any suggestion or advice to help me solve this I would really appreciate this. I'm trying with 1 client(switchs) and 1 server(2 leds).Thanks to follow my case, I really appreciate it, my first experience with Nordic devices and Bluetooth Mesh.

RE: adding second element to a light control server node mesh example

Petter Myhre — Thu, 24 Aug 2017 12:44:27 GMT

No_RAM? Do you mean NRF_ERROR_NO_MEM? Which function returned it? And where inside the function was it returned from?

RE: adding second element to a light control server node mesh example

ms3412amo — Wed, 23 Aug 2017 15:20:07 GMT

Error was No_RAM, some numbers to scale missing in nrf_mesh_config_app.h like ACCESS_MODEL_COUNT. Now on server node it seems to run but still not sure about some points: DSM_VIRTUAL_ADDR_MAX is it the number of Model to be addressed in the device, I put 2. I got provisionning completed, I'm now on client side to adapt code to control 2 Led on the same server. I'm in access_setup() to see whats going there...

RE: adding second element to a light control server node mesh example

Petter Myhre — Wed, 23 Aug 2017 14:44:01 GMT

Which error do you get? From which function?