Sending messages from client to different LPNs

RE: Sending messages from client to different LPNs

BroccLee — Thu, 23 Apr 2020 08:19:19 GMT

After putting some __LOG lines in the change_publication_address() function i see that ist the line status = dsm_address_publish_add(destination_address, &publish_address_handle); that causes the error.

if(access_model_publish_address_get(handle, &publish_address_handle) == NRF_SUCCESS)      
    {
        __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "1\n");
        status = dsm_address_publish_add(destination_address, &publish_address_handle);  
        __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "adding new publication address1\n");
    }

On the console, I see the "1" as output and then comes the error: app_error_weak.c, 105, Mesh assert at 0x00031B0C (:0). I don't see the message "adding new publication address1".

Can i not pass the handle and address as change_publication_address(m_clients[0].model_handle, 0002); ?

Thanks

RE: Sending messages from client to different LPNs

BroccLee — Tue, 21 Apr 2020 12:58:03 GMT

Hi Joakim

Thanks for the reply. I am now trying to send a message from my gateway to a specific (server)Node. I have two server nodes with addresses 0x0002 and 0x0003. i want to send the onoff switch command to 0x0002 and leave 0x0003 as it is. However, I have problems changing the publication address.

This is my code for changing the publication address:

static void change_publication_address(access_model_handle_t handle, uint16_t address)
{
    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Change Publication address\n");
    uint32_t status = NRF_SUCCESS;  
    nrf_mesh_address_t publish_address_stored;
    destination_address = address;
    
    if(publish_address_handle != DSM_HANDLE_INVALID)
    {
        NRF_MESH_ASSERT(dsm_address_publish_remove(publish_address_handle) == NRF_SUCCESS);
    }

    if(access_model_publish_address_get(handle, &publish_address_handle) == NRF_SUCCESS)      
    {
        status = dsm_address_publish_add(destination_address, &publish_address_handle);       // add destination address        
    }   
    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))
            {
                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_remove(publish_address_handle);
            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");
            return;
        case NRF_SUCCESS:
            __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "NRF_SUCCESS\n");
            break;
        default:
            __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Not defined ERROR\n");
            return;
    }
    NRF_MESH_ASSERT(access_model_publish_address_set(handle, publish_address_handle) == NRF_SUCCESS);  // change the address
}

When I call change_publication_address(m_clients[0].model_handle, 0002); on the gateway, all the LEDs on the server DK go on and i get the error app_error_weak.c, 105, Mesh assert at 0x000275CC (:0) in the RTT Viewer.

The error occurs because of the line

NRF_MESH_ASSERT(access_model_publish_address_set(handle, publish_address_handle) == NRF_SUCCESS); which is at the bottom of my change_publication_address() function.

The funny thing is, when I reset the gateway (reset button on DK), I see that the address was changed correctly and I am sending data to 0x0002 only. Can you help me with this?

I link my main file in case it might help. devzone.nordicsemi.com/.../38807.main.c

Thank you

RE: Sending messages from client to different LPNs

Joakim Jakobsen — Sun, 19 Apr 2020 23:35:42 GMT

Hi.

If you want this to happen after each poll complete event, I guess this should be fine.

I also want to comment on a few questions from your original question;
If you publish a message to a group address, this will be received and processes by each node subscribing to that group address. If you want to send a message to a specific node, you should use the unicast address for the node instead.

We have a section in our online documentation about Creating new models.

Best regards

RE: Sending messages from client to different LPNs

BroccLee — Fri, 17 Apr 2020 08:20:04 GMT

This is how I implemented it right now and it seems to work. I used the the lpn and lightswitch examples and added a functionality to the lightswitch client and lpn example. Now i can send and receive from gateway(lightswitch client) and lpn.

However, I'm not sure if the lowpower functionality of the LPN is still working as intended now. I added the line

case NRF_MESH_EVT_LPN_FRIEND_POLL_COMPLETE:
            __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Friend poll procedure complete\n");
            app_onoff_status_publish(&m_onoff_server_0); // I added this
            break;

in the main.c of the lpn example inside the app_mesh_core_event_cb, so it updates the LEDs when it polls.

Does this make sense? Is this how it's supposed to wirk?

Thanks