send data from client to specific server via unicast address

RE: send data from client to specific server via unicast address

urvilsuthar — Wed, 29 Sep 2021 10:17:58 GMT

Hi Karinca,

Using nRF5_SDK_17.0.2_d674dde + nrf5_SDK_for_Mesh_v5.0.0_src

I have tried the above function code to change the publish address but getting Mesh Assert " Mesh assert at 0x000316E0 (:0)".

I am trying to send data to server side from client node using UART communication. UART data gives the server node publish address and data(1 byte) to be sent.

Tried to debug the cause of assertion and found function "dirty_entries_process" is causing this assertion.

After success in single byte, going for Insta-Burst implementation.

Need support in this.. Thanks

One more Input to this, After Resetting client device only once dirty_entries_process works perfect. later when the unicast address changed his error comes again.

RE: send data from client to specific server via unicast address

Hit — Thu, 27 Dec 2018 11:03:14 GMT

Hi Michel

[quote userid="74354" url="~/f/nordic-q-a/40666/send-data-from-client-to-specific-server-via-unicast-address"]The sensor send data on regular bases to the client via the mesh and the client then send it via UART to a computer[/quote]

Can you share the data how you made this network. Basically I'm trying to build the sensor network using Bluetooth Mesh to transfer data to end node to computer.

Can you help me with your data to build the network.

RE: send data from client to specific server via unicast address

michel_93 — Sun, 02 Dec 2018 10:24:22 GMT

Thank you very much the solution works

RE: send data from client to specific server via unicast address

michel_93 — Thu, 22 Nov 2018 09:14:27 GMT

Thanks for you answer. I will check it out this week.

RE: send data from client to specific server via unicast address

karinca — Wed, 21 Nov 2018 21:45:43 GMT

Another method would be blinking led in provision completed callback on server.

RE: send data from client to specific server via unicast address

karinca — Wed, 21 Nov 2018 21:41:51 GMT

You change the publication address like this:

uint32_t status = NRF_SUCCESS;

  dsm_handle_t publish_address_handle = DSM_HANDLE_INVALID;
  nrf_mesh_address_t publish_address_stored;

  if (access_model_publish_address_get(m_clients[0].model_handle, &publish_address_handle) != NRF_SUCCESS) {

    status = dsm_address_publish_add(destination_address, &publish_address_handle);

  } else {

    if (dsm_address_get(publish_address_handle, &publish_address_stored) == NRF_SUCCESS) {

      if ((publish_address_stored.type == NRF_MESH_ADDRESS_TYPE_VIRTUAL) ||
          (publish_address_stored.type != NRF_MESH_ADDRESS_TYPE_VIRTUAL &&
              publish_address_stored.value != destination_address)) {
        /* This should never assert */
        NRF_MESH_ASSERT(dsm_address_publish_remove(publish_address_handle) == NRF_SUCCESS);
        status = dsm_address_publish_add(destination_address, &publish_address_handle);
      } else {
        /* Use the retrieved publish_address_handle */
      }
    } else {

      status = dsm_address_publish_add(destination_address, &publish_address_handle);
    }
  }

  switch (status) {
  case NRF_ERROR_NO_MEM:
    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "NRF_ERROR_NO_MEM\n");
    //            status_error_pub_send(handle, p_message, sig_model, ACCESS_STATUS_INSUFFICIENT_RESOURCES);
    return;

  case NRF_SUCCESS:
    break;

  default:
    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "ACCESS_STATUS_UNSPECIFIED_ERROR\n");
    //            status_error_pub_send(handle, p_message, sig_model, ACCESS_STATUS_UNSPECIFIED_ERROR);
    return;
  }

  NRF_MESH_ASSERT(access_model_publish_address_set(m_clients[0].model_handle, publish_address_handle) == NRF_SUCCESS);

destination_address is unicast address you want to send on/off command. You can figure out which header file you must include by searching the function on all solution.