RE: Consecutive messages latency problem

Joakim Jakobsen — Wed, 09 Jun 2021 10:14:35 GMT

Hi.

Sorry about the delay.

The "Mesh error 8" (NRF_ERROR_INVALID_STATE is occuring because there is only allowed to send one Segmented message at a time.

The message will be sent as a segmented message and reassembled on the peer side if one of the following conditions are true:

The length of the message is greater than NRF_MESH_UNSEG_PAYLOAD_SIZE_MAX.
The force_segmented field of p_message is true.
The transmic_size field of p_message is NRF_MESH_TRANSMIC_SIZE_LARGE.

NRF_ERROR_INVALID_STATE returns when;
There's already a segmented packet that is being to sent to this destination. Wait for the transmission to finish before sending new segmented packets.

___

You will either have to wait until you receive the NRF_MESH_EVT_TX_COMPLETE event before sending again.
Or you need to make sure that the requirements of the segmented message isn't met.

Br,
Joakim

RE: Consecutive messages latency problem

Atra — Tue, 01 Jun 2021 14:13:41 GMT

I found the error source in transport.c. Why I get this error while sending 12B message? First time it sends without problem when checking status with ERROR_CHECK() function but second time it gives this error with "Mesh error at 8" message. What is the relationship between this error and waiting 5-6 seconds? I have used RTTViewer to find exact location of error and got this code. What does this error mean? What I have to do to get rid of error?