(Mesh)device restart,how to communicate with the previous configuration;

RE: (Mesh)device restart,how to communicate with the previous configuration;

Hung Bui — Tue, 06 Feb 2018 11:45:35 GMT

Hi Beike,

Adding subscription_count increase there might not be best idea. Usually what we do is when we restore model (start by calling nrf_mesh_node_config() from main) , restore_addresses_for_model() in access.c will be called and the subscription_count will be updated by dsm_address_subscription_add_handle() function.

The serial example currently demonstrates a simple serialization application, meaning all the configuration data and provisioning should be stored on the peer MCU (or PC). And be restored every time the chip reset.

If you are creating a standalone node, I would suggest to have a look at the light switch example. In that example the flash is handled properly.

RE: (Mesh)device restart,how to communicate with the previous configuration;

Beike — Tue, 06 Feb 2018 06:34:47 GMT

today, this problem solved by me .

Adding this command in flash_load fountion.

    if(type == DSM_ENTRY_TYPE_ADDR_NONVIRTUAL)
    {
        m_addresses[index].subscription_count++;
    }

static void flash_load(dsm_entry_type_t type, uint32_t index, const dsm_flash_entry_t * p_entry, uint16_t entry_len)
{
    NRF_MESH_ASSERT(type < DSM_ENTRY_TYPES);
    const flash_group_t * p_group = &m_flash_groups[type];

    p_group->to_dsm_entry(index, p_entry, entry_len);
    bitfield_set(p_group->p_allocated_bitfield, index);

    //add by zhou ,to update the subscription address number , avoid adding subscription address after reboot.
    if(type == DSM_ENTRY_TYPE_ADDR_NONVIRTUAL)
    {
        m_addresses[index].subscription_count++;
    }
}

to update the subscription number after reboot.

is this a bug?

RE: (Mesh)device restart,how to communicate with the previous configuration;

Beike — Tue, 06 Feb 2018 01:18:53 GMT

Sorry, My description is not clear enough. I am using Serial example.

yes, i think the subscription/publication address is missing on the client/server after reboot.

after reboot device, we must send this command "send(cmd.AddrSubscriptionAdd(49218))" to reconnfigrate the subscription address to receive the messages.

RE: (Mesh)device restart,how to communicate with the previous configuration;

Hung Bui — Mon, 05 Feb 2018 12:59:12 GMT

I was asking which application firmware/example did you use ? In our lightswitch example we did call dsm_flash_config_load() in main.

What do you mean by " if let the client and server node that has been rebooted print log by serial port" ?

Are you saying the subscription/publication address is missing on the client/server after reboot ?

RE: (Mesh)device restart,how to communicate with the previous configuration;

Beike — Mon, 05 Feb 2018 11:05:26 GMT

firmware :S132_5.0.0

RE: (Mesh)device restart,how to communicate with the previous configuration;

Beike — Mon, 05 Feb 2018 11:02:31 GMT

mesh V1.0.0;

This problem has been solved by me. I found the configration has been stored on flash, but has not been reload after reboot , so add this line "dsm_flash_config_load();" in main fountion , that is ok! I think this is a bug.

Add, there still has a little problem is that the relay node can relay messages in a same subnet after reboot and don't need to reconfigrate the app key and subnet address, but if let the client and server node that has been rebooted print log by serial port we must reconfigrate the publlication and subscription address by this command

send(cmd.AddrSubscriptionAdd(49218));send(cmd.AddrPublicationAdd(49218))

so can you tell me why?

RE: (Mesh)device restart,how to communicate with the previous configuration;

Hung Bui — Fri, 02 Feb 2018 14:50:28 GMT

Which firmware did you use ? Have you set PERSISTENT_STORAGE = 1 ? If you did, the configuration should be stored on flash.

What did you observe ?