sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

RE: sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

Mttrinh — Thu, 20 May 2021 11:43:37 GMT

Hi,

1. Have you made any changes to the project? You are using the nRF Mesh to provision the devices, bind the models to appkey and set the publish address, correct? I don't see this on my side.

2. Any packet with size larger than 11 bytes (including header) will be split into segmented messages automatically. But the maximum possible segmented payload size is 380 so it will fail if you have a higher payload. Note that Mesh is not optimal for sending/streaming a lot of data.

3. Yes, you can send data to a specific node by publishing to their unicast address. You can do this in the nRF Mesh app.

RE: sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

Sama — Tue, 18 May 2021 05:20:26 GMT

Hi,

Thank you again for the modification of the codes which workes well.

1) I wonder that why the handle_send_status function is rune twice in the server-side as you see in the log:

<t: 0>, main.c, 370, ----- BLE Mesh Light Switch Server Demo -----
<t: 12177>, main.c, 326, Initializing and adding models
<t: 12180>, main.c, 180, App OnOff Model Handle: 2
<t: 12183>, main.c, 185, App DTT Model Handle: 3
<t: 12187>, main.c, 191, App Scene Model Handle: 5
<t: 12244>, main.c, 304, Node Address: 0x0002
<t: 12247>, mesh_app_utils.c, 66, Device UUID (raw): 137FF47B11294702B381A62F60654E45
<t: 12250>, mesh_app_utils.c, 67, Device UUID : 137FF47B-1129-4702-B381-A62F60654E45
<t: 12279>, main.c, 420,
-------------------------------------------------------------------------------
Button/RTT 1) LED state will toggle and inform clients about the state change.
Button/RTT 4) Clear all the states to reset the node.
-------------------------------------------------------------------------------
<t: 12745>, app_onoff.c, 154, msg: SET: 0
<t: 169757>, generic_onoff_server.c, 274, ASCII Message: Hello
<t: 169760>, generic_onoff_server.c, 280, length of buffer_RX: 5
<t: 169770>, generic_onoff_server.c, 325, Status : 0
<t: 172383>, generic_onoff_server.c, 274, ASCII Message: Hello
<t: 172385>, generic_onoff_server.c, 280, length of buffer_RX: 5
<t: 172395>, generic_onoff_server.c, 325, Status : 0

2) To send large data through the mesh, I used ".force_segmented = true" option in the definition of my message, allowing me to send 360-byte data. Is this way correct?
Is there any solution to send more bytes?

3) Is it possible to send the data to a specific node? Actually, how can I send my message to a specific device, and how can I set the address inside the codes?

Br,
Sama

RE: sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

Sama — Fri, 14 May 2021 13:42:12 GMT

Hi,

Thank you very much.

I will try that.

Br,

Sama

RE: sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

Mttrinh — Thu, 13 May 2021 10:44:54 GMT

Hi,

I have modified the light switch example in our latest Mesh SDK v5.0.0. You can search for "modified" to see what I have modified on the client and server.

I used the nRF Mesh app to provision the devices, bind the models to appkey and set the publish address.

Push button 1 on the client board and you will see that a "Hello" message will be received on the server.

devzone.nordicsemi.com/.../nrf5_5F00_SDK_5F00_for_5F00_Mesh_5F00_v5.0.0_5F00_src_5F00_.rar

RE: sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

Mttrinh — Wed, 05 May 2021 15:46:36 GMT

Hi,

Regarding the error 7, you probably haven't bound model to appkey or publish address haven't been set.

[quote user="Sama"]Are you sure there is no need to change other codes, as I see in this case that the Generic OnOff and a few lines have been modified?[/quote]

I don't think you have to make the changes that are being made on the client in that thread, but you need make changes on the server side though.

I will try setting up the example with the latest SDK version on my side. It might take some time, I will update you as soon as possible.

RE: sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

Sama — Wed, 05 May 2021 05:04:28 GMT

Hi,

Could you please help me to solve my problem?

I look forward to hearing from you.

Br,

Sama

RE: sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

Sama — Sat, 01 May 2021 06:19:30 GMT

Hi,

Thank you for your reply.

I tested that again, and it seems that the error is related to the invalid status in ERROR_CHECK(status);

Here is the log and line that returned the error.

<t: 0>, main.c, 431, ----- BLE Mesh Light Switch Client Demo -----
<t: 12585>, main.c, 390, Initializing and adding models
<t: 17486>, mesh_app_utils.c, 66, Device UUID (raw): 137FF47B11294702B381A62F60654E45
<t: 17489>, mesh_app_utils.c, 67, Device UUID : 137FF47B-1129-4702-B381-A62F60654E45
<t: 17506>, main.c, 478,
------------------------------------------------------------------------------------
Button/RTT 1) Send a message to the odd group (address: 0xC003) to turn on LED 1.
Button/RTT 2) Send a message to the odd group (address: 0xC003) to turn off LED 1.
Button/RTT 3) Send a message to the even group (address: 0xC002) to turn on LED 1.
Button/RTT 4) Send a message to the even group (address: 0xC002) to turn off LED 1.
------------------------------------------------------------------------------------
<t: 150901>, main.c, 297, Button 1 pressed
<t: 150903>, main.c, 139, ----- send_message -----
Sending to group address 0xCAFE
<t: 150914>, main.c, 151, Status : 7
<t: 150916>, app_error_weak.c, 115, Mesh error 7 at 0x000279E5 (D:\Behine Niroo\Nordic\NRF Mesh\nrf5_SDK_for_Mesh_v5.0.0_src\examples\light_switch - Copy (3)\client\src\main.c:161)

Because the status returned by the "access_model_publish" function, I printed out the parameters before that. As you can see

<t: 0>, main.c, 435, ----- BLE Mesh Light Switch Client Demo -----
<t: 12535>, main.c, 394, Initializing and adding models
<t: 17432>, mesh_app_utils.c, 66, Device UUID (raw): 137FF47B11294702B381A62F60654E45
<t: 17435>, mesh_app_utils.c, 67, Device UUID : 137FF47B-1129-4702-B381-A62F60654E45
<t: 17449>, main.c, 482,
------------------------------------------------------------------------------------
Button/RTT 1) Send a message to the odd group (address: 0xC003) to turn on LED 1.
Button/RTT 2) Send a message to the odd group (address: 0xC003) to turn off LED 1.
Button/RTT 3) Send a message to the even group (address: 0xC002) to turn on LED 1.
Button/RTT 4) Send a message to the even group (address: 0xC002) to turn off LED 1.
------------------------------------------------------------------------------------
<t: 111205>, main.c, 301, Button 1 pressed
<t: 111208>, main.c, 139, ----- send_message -----
Sending to group address 0xCAFE
<t: 111219>, main.c, 150, msg.opcode.opcode : 0x00C1
<t: 111221>, main.c, 151, msg.p_buffer : Hello
<t: 111223>, main.c, 152, msg.length : 5
<t: 111225>, main.c, 154, Status : 7
<t: 111227>, app_error_weak.c, 115, Mesh error 7 at 0x00027A1D (D:\Behine Niroo\Nordic\NRF Mesh\nrf5_SDK_for_Mesh_v5.0.0_src\examples\light_switch - Copy (3)\client\src\main.c:165)

I also followed the "access_model_publish" function until "packet_alloc_and_tx" function and tried to print out its parameters:

<t: 0>, main.c, 467, ----- BLE Mesh Light Switch Client Demo -----
<t: 12356>, main.c, 426, Initializing and adding models
<t: 12406>, main.c, 230, Node Address: 0x0002
<t: 12409>, mesh_app_utils.c, 66, Device UUID (raw): 137FF47B11294702B381A62F60654E45
<t: 12412>, mesh_app_utils.c, 67, Device UUID : 137FF47B-1129-4702-B381-A62F60654E45
<t: 12436>, main.c, 514,
------------------------------------------------------------------------------------
Button/RTT 1) Send a message to the odd group (address: 0xC003) to turn on LED 1.
Button/RTT 2) Send a message to the odd group (address: 0xC003) to turn off LED 1.
Button/RTT 3) Send a message to the even group (address: 0xC002) to turn on LED 1.
Button/RTT 4) Send a message to the even group (address: 0xC002) to turn off LED 1.
------------------------------------------------------------------------------------
<t: 178686>, main.c, 333, Button 1 pressed
<t: 178688>, main.c, 139, ----- send_message -----
Sending to group address 0xCAFE
<t: 178699>, main.c, 150, msg.opcode.opcode : 0x00C1
<t: 178702>, main.c, 151, msg.p_buffer : Hello
<t: 178704>, main.c, 152, msg.length : 5
<t: 178706>, access.c, 439, handle : 0
<t: 178708>, access.c, 440, pp_access_payload : 537128688
<t: 178711>, access.c, 441, p_access_payload_len : 537128694
<t: 178714>, access.c, 442, TX: Msg Hello
<t: 178716>, main.c, 154, Status : 7
<t: 178718>, app_error_weak.c, 115, Mesh error 7 at 0x00027A25 (D:\Behine Niroo\Nordic\NRF Mesh\nrf5_SDK_for_Mesh_v5.0.0_src\examples\light_switch - Copy (3)\client\src\main.c:165)

I am not sure about the correctness of my method to print out and I could not print the "p_rx_message" variable.

Any idea?

Are you sure there is no need to change other codes, as I see in this case that the Generic OnOff and a few lines have been modified?

Could you please run this example on your side? Because I have been struggling a long time to run that.

It seems that after 3 years, it is needed an update, isn't it?

Br,

Sama

RE: sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

Mttrinh — Wed, 28 Apr 2021 13:38:05 GMT

[quote user="Sama"]

or should I define another variable "m_client" as

static simple_on_off_client_t m_client[CLIENT_MODEL_INSTANCE_COUNT];

and use this in my functions?

[/quote]

Yes, you should define another variable for m_client and use this in your functions. As this is for simpleOnOff while the other one is for GenericOnOff.

The error that you get, Mesh error 7, corresponds to Invalid Parameter. In main on line 167, can you see which function is returning this error? Have you put in the correct parameter?

RE: sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

Sama — Wed, 28 Apr 2021 05:17:07 GMT

Hi,

Update:

When I provision and configure the devices, there are not simple messages or simple OnOff models.

any idea?

I look forward to hearing from you.

Br,

Sama

RE: sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

Sama — Tue, 27 Apr 2021 12:13:10 GMT

Hi,

Thank you for your reply.

Here it is two pictures of my debug:

In this case, I add my function in the case of 1.3 buttons,

and in this case, I add my function in the case of 2.4 buttons,

and this is the log:

<t: 0>, main.c, 439, ----- BLE Mesh Light Switch Client Demo -----
<t: 12144>, main.c, 398, Initializing and adding models
<t: 17040>, mesh_app_utils.c, 66, Device UUID (raw): 137FF47B11294702B381A62F60654E45
<t: 17043>, mesh_app_utils.c, 67, Device UUID : 137FF47B-1129-4702-B381-A62F60654E45
<t: 17056>, main.c, 486,
------------------------------------------------------------------------------------
Button/RTT 1) Send a message to the odd group (address: 0xC003) to turn on LED 1.
Button/RTT 2) Send a message to the odd group (address: 0xC003) to turn off LED 1.
Button/RTT 3) Send a message to the even group (address: 0xC002) to turn on LED 1.
Button/RTT 4) Send a message to the even group (address: 0xC002) to turn off LED 1.
------------------------------------------------------------------------------------
<t: 97625>, main.c, 304, Button 1 pressed
<t: 97627>, main.c, 329, Sending msg: ONOFF SET 1
<t: 97630>, main.c, 374, Publication not configured for client 1
<t: 350157>, main.c, 304, Button 1 pressed
<t: 350159>, main.c, 329, Sending msg: ONOFF SET 1
<t: 350162>, main.c, 374, Publication not configured for client 1
<t: 398193>, main.c, 304, Button 2 pressed
<t: 398195>, main.c, 145, ----- send_message -----
Sending to group address 0xCAFE
<t: 398206>, main.c, 157, Status : 7
<t: 398208>, app_error_weak.c, 115, Mesh error 7 at 0x000279EF (D:\Behine Niroo\Nordic\NRF Mesh\nrf5_SDK_for_Mesh_v5.0.0_src\examples\light_switch - Copy\client\src\main.c:167)

I wonder that the address_set function in server and client are different or not. Because in this case, it seems that they are alike.

Furthermore, I am confused about the "m_clients" variable. This variable is defined in the Nordic's codes as:

static generic_onoff_client_t m_clients[CLIENT_MODEL_INSTANCE_COUNT];

Should I use this in my functions, e.g

ERROR_CHECK(access_model_publish_address_set(m_clients[0].model_handle, m_central_handle));
status= access_model_publish(m_clients[0].model_handle, &msg);

or should I define another variable "m_client" as

static simple_on_off_client_t m_client[CLIENT_MODEL_INSTANCE_COUNT];

and use this in my functions?

Please let me know as soon as possible.

I look forward to hearing from you.

Br,

Sama

RE: sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

Mttrinh — Mon, 26 Apr 2021 15:14:08 GMT

Hi,

You don't need to make a new ticket for this, we can continue this here. I'm not sure what the issue is though

[quote user="Sama"]

I added the send_my_message function in the button handler but it got stuck.

[/quote]

What do you mean by stuck? Do you get any errors? Any log you can share?

[quote user="Sama"] Due to existing the generic_onoff model in this example, may it cause a conflict with the simple_onoff model?[/quote]

I don't think this will casue any problems. You can add multiple models in the same example.

[quote user="Sama"]In the access_model_publish_address_set function we assign an address for our model, right? how can I found if another model signed to this address or not? and is there any limitation to add models? [/quote]

Yes, that function is for adding a publish address to a model. You can have multiple models sending to the same address.

RE: sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

Sama — Sun, 25 Apr 2021 15:11:31 GMT

Hi,

Is there any solution?

Should I creat a new ticket?

RE: sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

Sama — Mon, 19 Apr 2021 11:30:54 GMT

Hi,

Sorry for my late reply. I have been working on another part of the project.

Now, I added these lines on the client-side:

#include "simple_message_common.h"
#include "simple_on_off_client.h"

static simple_on_off_client_t m_client;
static dsm_handle_t m_central_handle;

void address_set(uint16_t addr)
{
ERROR_CHECK(dsm_address_publish_add(addr, &m_central_handle));
ERROR_CHECK(access_model_publish_address_set(m_client[0].model_handle, m_central_handle));
}

void send_my_message (void)
{
uint32_t status=0;
uint8_t buffer[5]="Hello";
uint8_t length;
uint16_t address;
access_message_tx_t msg;
length= sizeof(buffer);
__LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "----- send_message -----\n");
if (length)
{
msg.opcode.opcode = simple_message_OPCODE_SEND;
msg.opcode.company_id = 0x0059; // Nordic's company ID

msg.p_buffer = (const uint8_t *) &buffer[0];
msg.length =length;
address = 0xCAFE;
address_set(address);
SEGGER_RTT_printf(0,"Sending to group address 0x%04x\n", address);
status= access_model_publish(m_client[0].model_handle, &msg);
__LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Status : %u \n", status);

if (status == NRF_ERROR_INVALID_STATE ||
status == NRF_ERROR_BUSY||status == NRF_ERROR_NO_MEM)
{
__LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Cannot send. Device is busy.\n");
hal_led_blink_ms(LEDS_MASK, 50, 4);
}
else
{
ERROR_CHECK(status);
}
}
}

and also added the c files of simple_message_client and simple_onoff_client and their paths to the user include directories.

and for server-side:

#include "simple_message_common.h"
#include "simple_on_off_server.h"

static simple_on_off_server_t m_server;
static dsm_handle_t m_central_handle;

void address_set(uint16_t addr)
{
ERROR_CHECK(dsm_address_publish_add(addr, &m_central_handle));
ERROR_CHECK(access_model_publish_address_set(m_server.model_handle, m_central_handle));
}

void send_my_message (void)
{
uint32_t status=0;
uint8_t buffer[5]="Hello";
uint8_t length;
uint16_t address;
access_message_tx_t msg;
length= sizeof(buffer);
if (length)
{
msg.opcode.opcode = simple_message_OPCODE_SEND;
msg.opcode.company_id = 0x0059; // Nordic's company ID

msg.p_buffer = (const uint8_t *) &buffer[0];
msg.length =length;
address = 0xCAFE;
address_set(address);
SEGGER_RTT_printf(0,"Sending to group address 0x%04x\n", address);
status= access_model_publish(m_server.model_handle, &msg);
__LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Status : %u \n", status);

and also added the c files of simple_message_server and simple_onoff_server and their paths to the user include directories.

I want to send my message by pressing a button and stop that with another button.

I added the send_my_message function in the button handler but it got stuck.

So I have some questions:

1. Where should I add my function? Is needed any pre-requirement function?

2. Due to existing the generic_onoff model in this example, may it cause a conflict with the simple_onoff model?

3. In the access_model_publish_address_set function we assign an address for our model, right? how can I found if another model signed to this address or not? and is there any limitation to add models?

Could you please help me?

Thank you in advance.

Br,

Sama

RE: sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

Mttrinh — Wed, 17 Feb 2021 16:09:54 GMT

Hi,

Have you had any progress with this?

You should put the send_my_message() function outside the button_event_handler(). And the void address_set(uint16_t addr) can be added to main.c.

Additional you should add these static variables and include as well in your main.c:

#include "simple_message_common.h"
#include "simple_on_off_server.h"

static simple_on_off_server_t m_server;

static dsm_handle_t m_central_handle;

Thanks for your patience.

RE: sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

Sama — Wed, 03 Feb 2021 13:12:45 GMT

Hi,

What I did is:

copy the simple message model inside the vendor folder where there is the simple on-off model.

add a new folder in the project file in the switch light client SES and add simple on-off and simple message models.

add ../../../../../../models\vendor\simple_message\include and ../../../../../../models\vendor\simple_on_off\include to the User Include Directories field.

add this code in the main.c in line 248 (switch(button_number)
{
case 1:
case 3:
set_params.on_off = APP_STATE_ON;)

void send_my_message (void)
{
uint32_t status=0;
uint8_t buffer[5]="Hello";
uint8_t length;
uint16_t address;
access_message_tx_t msg;
length= sizeof(buffer);
if (length)
{
msg.opcode.opcode = simple_message_OPCODE_SEND;
msg.opcode.company_id = 0x0059; // Nordic's company ID

msg.p_buffer = (const uint8_t *) &buffer[0];
msg.length =length;
address = 0xCAFE;
address_set(address);
SEGGER_RTT_printf(0,"Sending to group address 0x%04x\n", address);
status= access_model_publish(m_clients[3].model_handle, &msg);
__LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Status : %u \n", status);

After running I get this

Rebuilding ‘light_switch_client_nrf52840_xxAA_s140_7.2.0’ from solution ‘light_switch_client_nrf52840_xxAA_s140_7.2.0’ in configuration ‘Debug’
Compiling ‘main.c’
'simple_message_OPCODE_SEND' undeclared (first use in this function)
each undeclared identifier is reported only once for each function it appears in
implicit declaration of function 'address_set'; did you mean 'dsm_address_get'? [-Wimplicit-function-declaration]
implicit declaration of function 'SEGGER_RTT_printf' [-Wimplicit-function-declaration]
Compiling ‘mesh_provisionee.c’
Compiling ‘rtt_input.c’
Compiling ‘simple_hal.c’
Build failed

In addition to this, I do not know where I should add the void address_set(uint16_t addr) which is stated in the mentioned links.

I am a beginner and I confuse when I deal with the names of different functions I do not know where they are and what they did.

Thank you,

Sama

RE: sending ASCII bytes through Mesh between a nrf52840 development kit and two dongle

Mttrinh — Tue, 02 Feb 2021 13:22:33 GMT

Hi,

There have been made a lot of changes and improvements from Mesh SDK v1.0.0 to v5.0.0. Unfortunately, we don't have any official examples for sending strings over mesh. The links you are referring to is a great starting point and gives you an idea of how you can do this.

When it comes to the error you get, can you get more details? What function gives which errors? What kinda error do you get? Can you provide some debug logs?