Custom mesh 3.0.1 messages.

RE: Custom mesh 3.0.1 messages.

Biliban Tierli — Mon, 05 Aug 2019 10:50:45 GMT

Hi,

I am not sure if the MAC address is transmitted, but if so you can find it in the access_message_rx_t -> access_message_rx_meta_t Struct that is received with every message. This documentation shows you what is sent: https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.3.0%2Findex.html

I hope this helps

Cheers

RE: Custom mesh 3.0.1 messages.

viper1983 — Wed, 31 Jul 2019 02:32:45 GMT

Hello, how does the receiver get the MAC address and element address of the sender?Thank you, you gave me a great help, address problem in there get

RE: Custom mesh 3.0.1 messages.

Biliban Tierli — Thu, 28 Mar 2019 12:18:30 GMT

No sorry, I uploaded the same code twice, probably because they are both called main.c.

This is the Code for the Server:

devzone.nordicsemi.com/.../7242.main.c

But yes technically it is possible to have a Node act as both a client and a server. For that you would just need to merge the two Models to one.

RE: Custom mesh 3.0.1 messages.

JohnRickman — Thu, 28 Mar 2019 10:40:02 GMT

are server and client using same code? is it because you are not using light switch model as a base?

RE: Custom mesh 3.0.1 messages.

Biliban Tierli — Wed, 27 Mar 2019 13:26:48 GMT

Hi John,

of Course! In my example i am using two nRF52840 Development Kits. I am using the light_switch example from the mesh sdk. I have a Server as well as a Client. The Client can remotely control the LEDs of the Server. I am currently using my Phone and the nRF-Mesh App to provision these Node. You have to set the Client Publication Address to the Unicast Address of the Server or you could also Publish to a Group Address (0xC0 or higher) and Subscribe with the Server to the same Address.

Server

devzone.nordicsemi.com/.../412810.main.c.

Client

devzone.nordicsemi.com/.../412810.main.c

If you have anymore questions feel free to ask.

Cheers

Kilian

RE: Custom mesh 3.0.1 messages.

JohnRickman — Wed, 27 Mar 2019 09:33:27 GMT

Hey Kilian,

I am also looking into using Bluetooth mesh to pass custom messages for my home sensor network. I am bit of hobbyist and coding is not my strong side yet as I am just getting into trying nordics devboards, could you share your source code for this project so I would have a reference point to test passing some custom messages back and forth.

Cheers,

John.

RE: Custom mesh 3.0.1 messages.

Biliban Tierli — Mon, 04 Mar 2019 13:23:27 GMT

Hi James,

I am pretty new to the NRF52 ecosystem and so I was wondering the same. After a lot of research and trial & error I found the following:

A model_init_cb function can be specified in the init_params of the mesh_stack_init function. In your model_init_cb function this should be done:

The function that actually adds the model is access_model_add. This function takes two arguments, access_model_add_params_t and access_model_handle_t which is just a uint16_t. Here is a code example of my usecase:

uint16_t model_handle;

access_model_add_params_t add_params =
{
.model_id = ACCESS_MODEL_VENDOR(0xFFAA, 0xF001), // Format of ACCESS_MODEL_VENDOR is (model_id, company_id)
.element_index = 0,
.p_opcode_handlers = &m_opcode_handlers[0],
.opcode_count = ARRAY_SIZE(m_opcode_handlers),
.p_args = NULL,
.publish_timeout_cb = publish_interval_cb
};

uint32_t status = access_model_add(&add_params, &model_handle);

Some of the Parameters inside the access_model_add_params_t need some explaining:

- model_id: The Model ID is used for identifying predefined Models, like the Simple_OnOff_Client you are probably using. If you want to make your own you you can choose your own ID and Company value. What I have found is, that the two MSB of these values should be 1 (0xC0 or higher).

- element_index: Defines in which element your model will be imported. Health and Config Server are at index 0.

- p_opcode_handlers: This contains your OpCodes and should look something like this:

static const access_opcode_handler_t m_opcode_handlers[] =
{
{ACCESS_OPCODE_VENDOR(0xC1, 0xF001), your_opcode_handler_function},
};

// Format of ACCESS_OPCODE_VENDOR is (opcode, company_id)
// Again what I have found is, that the two MSB of these values should be 1 (0xC0 or higher).

// Your OpCode Handler Function should look like this:
// static void your_opcode_handler_function(access_model_handle_t handle, const access_message_rx_t * p_rx_msg, void * p_args);

- p_args: Can be any additional arguments

- publish_timeout_cb: Haven't played around with it yet, currently is just an empty function for me.

After calling access_model_add you should call access_model_subscription_list_alloc, to allow it to subscribe to addresses. If both of these functions return the status 0 (NRF_SUCCESS) your model is added.

To send data you can now use the access_model_publish function. In my example I have it bound to a button in the button event handler. The parameter for the function look like this:

const uint8_t data[] = {0x00};

const access_message_tx_t msg = {
.opcode = ACCESS_OPCODE_VENDOR(0xC2, 0xF001), // Format of ACCESS_OPCODE_VENDOR is (opcode, company_id)
.p_buffer = &data,
.length = ARRAY_SIZE(data),
.force_segmented = false,
.transmic_size = NRF_MESH_TRANSMIC_SIZE_SMALL,
.access_token = nrf_mesh_unique_token_get()
};

access_model_publish(model_handle, &msg);

Here you can now specify your own data. You could make a Structure with all your Data and a Function which converts it to a uint8_t Array, aswel as a function which can then convert it back from a uint8_t Array to your Structure.

For most of the Information I used the Mesh SDK Documentation: www.nordicsemi.com/.../index

I hope this was helpful and if you have any more questions feel free to ask.

Cheers,

Kilian