Simple_on_off model on nRF52832

[JK0201]

Hello to everyonel.

I am working with the Light_switch example of Mesh 3.1 on nRF52832 (PCA10040).
At this moment, I am trying to understand how I can send a message from the server to the client in the network. I found this publication on Github that explains how to create new models for mesh technology. On that page, indicate which functions: access_model_publish () and send_reply () (of the models simple_on_off), is used to send a message from the server to the client as a callback of the client's message.
There is a problem with that. The Simple_on_off models (".c" and ".h" files) are not included in the server and client projects. What I want to know is, if I add (in the main.c code of the server) the function "send_reply ()" (with the correct path, the function and the declaration of the library, etc.), It could works.

In addition, the user of this question modified the simple_on_off_server.c code to create a function called "publish_state2 ()" (I believe that before Mesh 3.1, there is a function called "publish_state ()" but now it is called "simple_on_off_server_status_publish ()", I suppose). I tried to do the same, but when I compile the program, it throws these errors:

Does anyone knows why the code throws those error?

I hope you can help me.

Best regards,
John

[BubDev]

There is no such thing as a "server node" and a "client node". A node contains elements which contain models. A model can be a server or a client. So a node can have server models in it and client models in it. A server model does not send messages to a client model but instead a client model publishes to an address and a server model subscribes to that address. If you want two way communication between your nodes I suggest you add both a client model and a server model to both your nodes. The best way to achieve adding a new model is to open the example light switch server and clients main.c file side by side and copy over the definitions/functions needed for each type of model. You will need to include the .c and .h files of each generic model. 

Servers send a reply to a client if using an acknowledged messages and the response will contain the on/off message that it received. This allows the client to resend the message if the server model received the incorrect value or didn't receive the value at all. It seems like you are on the right path. 

Hopes this help a little until the Nordic Devs can get to it. 

[JK0201]

BubDev, thank you very mucho for your fast answer.
Yeah, I did a mistake calling "nodes" to the models. Is already corrected.
I've tried to add the client model to the server project before, but It did't work well.
So, what I thought is, if the server only answers when the clients send a message, I have to understand how I can modify this answer to put-in the status that I want, not the default.

[BubDev]

So I don't think modifying the status message will work as it is define in the mesh specification to act in a certain way.

 

What I've been doing is using generic_level client to publish a value between -32k and 32k then on the server side I convert that value to the message that I want. This way you won't have to make a custom model to handle the custom message you want. 

[JK0201]

Can you show me how it works?

[BubDev]

So for the generic client model use the function

generic_level_client_set(&m_clients, &set_params, &transition_params);

to publish the level/message you want to send.


Then on the server side use the function

static void app_level_server_set_cb(const app_level_server_t * p_server, int16_t present_level){}

to handle the message you received.


Also this may help you as this is something I needed to do to successfully be able to publish messages inside the main

uint8_t is_nested;

ERROR_CHECK(sd_nvic_critical_region_enter(&is_nested));

generic_level_client_set(&m_clients, &set_params, &transition_params);

ERROR_CHECK(sd_nvic_critical_region_exit(is_nested));


This makes sure you are not in a critical region when publishing the message and avoids a mesh assert error.

Check here for more info on critical region
devzone.nordicsemi.com/.../mesh-sdk-2-2-0-bug-in-mesh_opt_core_adv_set