Problem with mesh assert in access_model_publish function

[thingyplayer]

Hi, I am using https://github.com/NordicPlayground/Nordic-Thingy52-mesh-demo with segger embedded studio and nordic thingy52 modules. I have problem with the mesh assert which appears after the button_evt_handler (turning the diode on and off) function performing 2710 times. The problem occurs during access_model_publish function.

After use addr2line -e <src.elf> 0x000354E4  it points to

…\mesh_sdk\mesh\core\src/net_state.c:299 (discriminator 1)

It’s here:

Someone had a similar problem ?
Do you know if there is still a problem with the newer sdk for mesh 2.0.1 ?
How to quickly and easily move to new sdk ?

[Jui-Chou (Rick) Chung]

Hello Thingyplayer,

Unfortunately the "Nordic Thingy52 mesh demo" is based on the very old mesh SDK v1.0.1.
I am planning to upgrade the project with using the latest mesh SDK, but may need times. 

Regarding to the issue you faced, may I know:

1. The frequency you press the button for sending the message

2. Could reset the bridge do help to recover from the assert?

[thingyplayer]

Hello Rick Chung, thank you for your answer.

1. Time interval is 100ms, but I tested 500ms too, and effect was the same.
I wrote the same function as buton_evt_handler and use ticker variable to execute.

2. Yes, after bridge reset, it works, but few moments later node freezes too. Reset all devices in the mesh network solves problem. The problem described in this thread occurs every time as described earlier. Always after using the function access_model_publish 2710 times (in this example) -> retry = 3. So when I try sending one unack messages, mesh assert runs after 8130 times.

[wangshuai]

hi   thingyplayer

You are familiar with the Mesh network. Can you teach me the following questions?

  How the Mesh Network Shows the Power of Each Node's Battery to the Phone?

[Jui-Chou (Rick) Chung]

Hello wangshuai,

I would like to suggest you open another thread for discussing this issue.
Since there's no relationship between your question and this thread :)

[thingyplayer]

I tested 2.0.1 version and the problem does not occur.
Outdated topic :) 

[Jui-Chou (Rick) Chung]

Hello Thingyplayer,

I just finish the test on mesh SDK 2.0.1, and cannot replicate the issue (I have sent the message through access_model_publish with retry = 3 for 4300 times with 500 ms interval). I would assume the related issue has been fixed in the current mesh SDK. I won't look into this issue in the current stage, and will work on upgrade the Thingy mesh demo into latest mesh SDK, will let you know when I done it 

[thingyplayer]

Thanks for support, I think other people will also benefit from this update.
Regards :)