"No free slots for new incoming segmented messages" warning when sensor client receive messages from 2 servers

[Li Boyan_1]

Hello!

I'm using BLE Mesh sensor client receiving messages sent from multiple sensor servers. I used 2 nRF54l15DKs as 2 sensor servers, each sending 9 16-bit float data segmented messages from ICM20948 sensor, using my custom sensor type and mesh sensor property IDs; then I tried to receive data from both servers simultaneously, 1 time per second. Then I  met this warning:

What can I do to prevent this?

Thank you!

Li Boyan

[Hung Bui]

Hi Li, 

How large is the message from the server to the client ? 

Could you try to increase CONFIG_BT_MESH_RX_SEG_MSG_COUNT  ?  By default it's only one. 
You can try to test with 10. 

Also please try to increase CONFIG_BT_MESH_RX_SEG_MAX, try 10 as well. 

 

[Li Boyan]

Hello!

Thank you for your reply and sorry for the delay.

I increase CONFIG_BT_MESH_RX_SEG_MSG_COUNT and CONFIG_BT_MESH_RX_SEG_MAX, and now it is much better, but I still get warnings like this from time to time:

 

By the way the message are 9 16-byte float data from ICM20948 sensor. It's sent as segmented messages so the data payload is quite large.

[Hung Bui]

Hi, 
You can take a look here: Ignoring old SeqAuth Issue 

How large is the payload ? I would suggest considering breaking the message down if it's really large message. Large mesh message would strain the network resource especially when there is a lot of re-trasmission.