Send and receive a string via access layer

RE: Send and receive a string via access layer

Bjørn Kvaale — Thu, 11 Apr 2019 14:07:14 GMT

Please create a new devzone case. We will take a look at it there.

RE: Send and receive a string via access layer

Guille — Thu, 11 Apr 2019 12:20:11 GMT

Hello Bjorn:

I have the nrf5SDKforMeshv310src folder and I can't make it works, propertly.

Could you give me some advice of the steps that I need to cover?

Thanks a lot

RE: Send and receive a string via access layer

run_ar — Wed, 25 Apr 2018 11:09:44 GMT

Please create a new thread for this.

RE: Send and receive a string via access layer

husain.smb — Tue, 24 Apr 2018 18:00:23 GMT

Hi Bjorn,

So I have implemented the above code. Now I am able to take inputs from the UART port of the client and send it to the UART port of the Server. But I am unable to do vice versa.But when I change the address from 0xCAFE to 0x0001 which is the provisioner address(in this case the client) the string I send from the server is printed on the debug terminal.But I am not able to find the place where it is received.I checked and it does not come into the handle_incoming() function as is the case with the => Client to Server communication.

Can you please help me figure this out?

RE: Send and receive a string via access layer

vijayrakesh — Thu, 19 Apr 2018 10:59:50 GMT

I tried for this but its not working for me.. I there any working code to share

RE: Send and receive a string via access layer

Bjørn Kvaale — Wed, 11 Apr 2018 12:59:21 GMT

As explained in my answer, this example only shows how to broadcast a message to all nodes. Could you please create a new devzone case & we will take a look at it there?

RE: Send and receive a string via access layer

Arij — Wed, 11 Apr 2018 09:28:31 GMT

How to set the address to unicast address instead of 0xCAFE ?

RE: Send and receive a string via access layer

Bjørn Kvaale — Mon, 09 Apr 2018 10:37:49 GMT

Not that I know of but my guess is that this would be quite similar to the example above.

RE: Send and receive a string via access layer

Igor — Wed, 28 Mar 2018 07:44:36 GMT

Is there any working example of server<->client mesh reliable send/receive available?

RE: Send and receive a string via access layer

Pooja — Thu, 15 Mar 2018 12:09:42 GMT

How we send string through advertising packet with unicast address and ttl value?

RE: Send and receive a string via access layer

Bjørn Kvaale — Mon, 12 Mar 2018 14:12:00 GMT

See the comment I posted here.

RE: Send and receive a string via access layer

Pooja — Mon, 12 Mar 2018 09:14:36 GMT

how other node receive the published message?

RE: Send and receive a string via access layer

Bjørn Kvaale — Fri, 09 Mar 2018 09:14:29 GMT

Sorry for the delayed response. What is currently not working for you in the above example?

RE: Send and receive a string via access layer

Kvadratukas — Fri, 23 Feb 2018 10:58:04 GMT

has anyone made this work and or willing to share a working example?

RE: Send and receive a string via access layer

swap007 — Tue, 30 Jan 2018 06:27:22 GMT

Thank you Bjorn

RE: Send and receive a string via access layer

Gerry — Thu, 25 Jan 2018 12:50:20 GMT

Thanks Bjørn

RE: Send and receive a string via access layer

koustubhavachat — Tue, 23 Jan 2018 11:42:29 GMT

I am also facing the similar issue as mentioned above. A device is not getting provisioned.

RE: Send and receive a string via access layer

Aman Chandan — Tue, 23 Jan 2018 10:25:35 GMT

Hi Bjørn, when I run these projects, the provisioning is not getting established.This is client code rtt log. <t: 59167>, provisioner.c, 227, Local provisioning link established <t: 60998>, provisioner.c, 212, Using static authentication <t: 72481>, provisioner.c, 221, Static authentication data provided <t: 108612>, provisioner.c, 235, Unexpected event: 13. <t: 112053>, provisioner.c, 182, Local provisioning link closed <t: 112056>, provisioner.c, 185, Provisioning failed. Retrying... <t: 175442>, provisioner.c, 227, Local provisioning link established Can you help me to resolve this?

RE: Send and receive a string via access layer

swap007 — Tue, 23 Jan 2018 04:13:36 GMT

Hi Bjørn, Thank you for your reply. could u please upload "simple_message" folder which u mentioned to copy in models?

RE: Send and receive a string via access layer

Bjørn Kvaale — Mon, 22 Jan 2018 15:30:57 GMT

Update: Sorry for the confusion. I have tried to find out what the reason is that the client is not provisioning correctly, but it seems the issue is more complicated than I thought. Instead of posting a solution which currently does not work & only works for an outdated Mesh SDK, I think it would be best for now to explain how messaging can work on a theoretical level with mesh in the access layer. Sorry for any confusion caused.

You can most likely base mesh messaging off of the light switch example in the Mesh SDK v1.0.0. In the light switch client example main.c file:

To make this simple, I will assume you only want to send a message from one node to all of the other nodes on the mesh network. In order to do this, we can use the simple_message model created by an application engineer at Nordic. You'll want to download the file & extract it to the models folder in the Mesh SDK v1.0.0. I would get rid of one of the folders, so that the path to the folders img, include, simple_message & src become MeshSDK/models/simple_message instead of MeshSDK/models/simple_message/simple_message You'll want to include the simple_message_client.c file in the Simple OnOff Model folder in SES. In addition, you'll want to include the header files located in the models/simple_message/include folder. See this tutorial for help.

uint32_t status=0;
uint8_t buffer[30];
uint8_t length;
uint16_t address;
access_message_tx_t msg;
length= SEGGER_RTT_Read(0,buffer, 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[0].model_handle, &msg);

              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);
               }
            }

To send a message, you could have two instances of Segger RTT viewer open. The status variable is used later in the code to see if the device is busy & to check for any errors that might have occurred. Going through the code, you will then need a buffer to store the message you want to send from one node to another node. The next variable is the length of the input message & is updated once the SEGGER_RTT_Read() function reads the input from the RTT terminal. Next, you can declare an address, which in our case will be the broadcast address to all of the other mesh nodes.

You will also need to declare a variable access_message_tx_t msg; of struct access_message_txt_t. This struct is defined in the access.h file. The next statement after the if block sets the 14-bit or 7-bit Bluetooth SIG defined opcode or 6-bit vendor specific opcode (see access.h). The simple_message_OPCODE_SEND is defined in the simple message model. Then, you want to set the company ID, which in this case is Nordic's company ID. The next line sets the pointer to the address where the message starts. I am assuming you start the message at the buffer index 0. You also need to define the length of the message. As mentioned previously, the address is set to the broadcast address for all of the mesh nodes.

The address_set function is defined as:

    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));
 }

& checks for errors. Then, you can add a print command to make understand what is happening in the real time terminal & call the access_model_publish function (see access.c & access.h). This function publishes an access layer message to the publish address of the model, which in our case is the broadcast address to all of the nodes.

Lastly, some checks are done to ensure that the device is not busy or one last error_check is done.

Inside the message_server main.c file:

Use the same code as above but make a few changes:

In the access_model_publish() function, use this statement instead:

status= access_model_publish(m_server.model_handle, &msg);

That should hopefully be the main things to be able to broadcast a message from one node to every other node (regardless of whether the node is a client or a server). I have not tested this to make sure it works in the latest Mesh SDK, so there could be some errors. Hope that helps!