Mesh Chat Model - Error Message = No free slots for new incoming segmented messages

[BlueMeshUK]

We are getting this message on our RELAY - via PuTTY.

"No free slots for new incoming segmented messages"

uart:~$ [01:00:53.683,380] <wrn> bt_mesh_transport: trans_seg: No free slots for new incoming segmented messages

then >>>

ASSERTION FAIL @ WEST_TOPDIR/zephyr/lib/os/ring_buffer.c:73

We are getting this error - using CHAT MODEL in MESH.  The RELAY gives us this same error message - we have increased the CONFIG_BT_MESH_ADV_BUF_COUNT value from 13 to 50.

We read here >>>  "No free slots" error while sending message  that adding a timing delay may help. 

We have not added a timing delay yet but lets say we use 0.1s between receiving and transmitting on to the proxy or the next Relay. Is this because of timing issues between the next available Tx slot being ready and the device being ready - or mistiming i should say.

How do we add a small delay?

We put this into our VS Code build - yes?

Please help if you can give us some information - many thanks.

We have nRF52840 BLE > nRF21540 DK as RELAY > nRF21540 DK as proxy.  

Thanks - Richard 

[AHaug]

Hi,

Based on my understanding of the case it looks like you might be changing the wrong parameter. https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/kconfig/index.html#CONFIG_BT_MESH_ADV_BUF_COUNT states "Number of advertising buffers available for sending local messages. This should be chosen based on the number of local messages that the node can send simultaneously.", while afaik you have issues with relaying messages, so I believe that increasing  https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/kconfig/index.html#CONFIG_BT_MESH_RELAY_BUF_COUNT should resolve your issue

Could you attempt to increase this configuration and to post the complete device log if this does not resolve the issue?

Kind regards,
Andreas

[BlueMeshUK]

Hi Andreas, I'm working with Richard.

I've added 

CONFIG_BT_MESH_RELAY_BUF_COUNT=256 into the prj.conf file and the messages No free slots" error while sending message have disappeared.

i also added to the KConfig file the lines below (please let me know if it is completely redundant)

config BT_MESH_RELAY_BUF_COUNT

int "Number of advertising buffers for relayed messages"

default 32

range 1 256

help

Number of advertising buffers available for messages to be relayed.

High number of advertising buffers increases the reliability of the

mesh network. Low number of advertising buffers reduces the message

latency on the Relay Node, but at the same time increases the amount

of packet drops. When considering the message latency, also consider

the values of BT_MESH_RELAY_RETRANSMIT_COUNT and

BT_MESH_RELAY_RETRANSMIT_INTERVAL. A higher number of

BT_MESH_RELAY_ADV_SETS allows the increase in the number of buffers

while maintaining the latency.

[TimD]

This is my prj.conf

2451.prj.conf

[TimD]

Hi Andreas, I few more questions:

Firstly I read somewhere that if the message is a max of 11bytes then the message doesn't need to be segmented. If thats the case why is the message "No free slots for new incoming segmented messages" appearing?

Also is there a way of getting rid of this warning "Ignoring old SeqAuth"?

Thanks

Tim

[TimD]

Hi Andreas,

The crash problem ASSERTION FAIL @ WEST_TOPDIR/zephyr/lib/os/ring_buffer.c:73 seems to be fixed by setting the messages to 11bytes max. I realised I didn't set the message buffer size on the relay to 11 (it was 60). After setting this the relay has been running for ~36 with 7 beacons advertising every 5 seconds. Our proxy crashed after 2 hours so I set the byte size to 11 
but didn't add
CONFIG_BT_MESH_RELAY_BUF_COUNT=256

I think the message "No free slots for new incoming segmented messages" has been misleading us to thinking this is the cause of the crash.

It would be good to understand why we are still seeing this message in the log and also the "Ignoring old SeqAuth" message as these messages are taking up most of the log file.

[AHaug]

Hi,

Apologies for the lack of response for the past two days, I've been out of office

Glad to hear that you were able to resolve the issue and thank you for sharing the fix! I must admit I also was mislead by the "no free slots for new incoming segmented messages" 

TimD said:

It would be good to understand why we are still seeing this message in the log and also the "Ignoring old SeqAuth" message as these messages are taking up most of the log file.

The log message is triggered in trans_seg() in zephyr/subsys/bluetooth/mesh/transport_legacy.c whenever the incoming messages sequence number is older than the current sequence number. Does the amount of these message change if you change the number of retransmissions you perform, or is it always the roughly the same amount?

Kind regards,
Andreas

[TimD]

Hi Andreas,

Ok so we've set the message size to 9bytes. This is a section of the log from the relay

<0x004C>: 030134
<0x004E>: 030336
<0x004A>: 030035
<0x004F>: 030735
message echo: Re:0000
<0x0050>: 030935
<0x004B>: 030535
<0x004D>: 030235
<0x004C>: 030134
<0x004E>: 030336
<0x004A>: 030035
<0x004F>: 030735
<0x0050>: 030935
<0x004B>: 030535
<0x004C>: 030134
<0x004E>: 030336
<0x004F>: 030735
<0x0050>: 030935
<0x004A>: 030035
<0x004C>: 030134
<0x004E>: 030336
<0x004F>: 030735
<0x0050>: 030935

i.e all warning message have disappeared. 

Somewhere in your documentation its says: For a vendor specific model, such as the chat model, messages with 9 or less bytes of payload should get sent in one packet (i.e. not segmented), which would go significantly faster due to two properties of segmented messages:

 

[BlueMeshUK]

Andreas - this would make life a LOT easier if 9 bytes was the default setting - i think it is set to Max 60 bytes by default - anyone reading this - start at 9 bytes and work up from there - dont start at the Nordic default or you may repeat our problems. 

[TimD]

Hi Andreas, unfortunately just been running another test with 9 byte messages and the relay and proxy crashed with the error ASSERTION FAIL @ WEST_TOPDIR/zephyr/lib/os/ring_buffer.c:73.

There is nothing in the log files that help.

[BlueMeshUK]

Hi Andreas - we have a commercial requirement to get this Sprint fixed - so it would be very helpful to help solve this issue with us ... FYI ... we moved from Wirepas to Bluetooth Mesh after some discussions with Nordic and we really need to get this sorted out now - if you need us to pay you a fee to solve the issue can you please send me a meeting link to richard:bluemeshsolutions.com so we can discuss together.  Thanks Richard 

[AHaug]

Hi, 

TimD said:

WEST_TOPDIR/zephyr/lib/os/ring_buffer.c:73.

There is nothing in the log files that help.

Could you post the contents of the log nonetheless? Could you also post a full device log?

TimD said:

Sorry I've just checked and the messages No free slots" error while sending message  are still appearing.

In the previous case you had a ring buffer error it stated that the ring buffer was full and that you needed to drain the buffer. Did you also ensure that the buffer was emptied or did you only increase the buffer size?

BlueMeshUK said:

discussions with Nordic and we really need to get this sorted out now - if you need us to pay you a fee to solve the issue can you please send me a meeting link to richard:bluemeshsolutions.com so we can discuss together.  Thanks Richard 

I would recommend that you stay in contact with your regional sales director regarding mapping your needs so they can look into them. Let me know if you need their contact information and I'll send it to you in a PM. 

Kind regards,
Andreas

[BlueMeshUK]

I have reached out to Claire Steed in the UK - is that the correct person?

Andreas in your answer above you mention ensuring empty the buffer - but you dont explain how to do this - can you be clear in your reply - what is the parameter or commend to drain the buffer please - it would make your reply much more useful to us if you recommend and then explain or demonstrate - thanks - Richard