Error NRF_ERROR_INVALID_STATE when send data via mesh 3.0

RE: Error NRF_ERROR_INVALID_STATE when send data via mesh 3.0

Igor — Tue, 04 Jun 2019 16:44:14 GMT

Do you send message to a group address? Is message segmented?

RE: Error NRF_ERROR_INVALID_STATE when send data via mesh 3.0

Andrea Pieretti — Mon, 11 Feb 2019 11:07:03 GMT

Hi, I've followed your indications and now I can send multiple segmented messages from the same client.

However, I receive the NRF_MESH_EVT_TX_COMPLETE event after more then 2s from the moment of sending.

Is it normal?

RE: Error NRF_ERROR_INVALID_STATE when send data via mesh 3.0

Igor — Tue, 22 Jan 2019 16:06:59 GMT

1. Check this answer for similar problem in Mesh 2.2

2. IRQ priorities have been changed in Mesh 3.0
- NRF_MESH_IRQ_PRIORITY_LOWEST should be 6.
- APP_IRQ_PRIORITY_LOW should also evaluate to 6.
- Search sdk.config for string "_IRQ_PRIORITY 7". Replace all occurrences with "_IRQ_PRIORITY 6".

3. In Mesh 3.0 only one segmented message from an element to a destination address at a time is allowed.
- Set force_segmented to false and message length to <= NRF_MESH_UNSEG_PAYLOAD_SIZE_MAX in every message you intend to send or
- Subcribe to NRF_MESH_EVT_TX_COMPLETE in order to achieve max one concurrent message transfer or
- Use timers and add all required logic to achieve max one concurrent message transfer

RE: Error NRF_ERROR_INVALID_STATE when send data via mesh 3.0

Igor — Thu, 03 Jan 2019 11:55:37 GMT

I have the same problem after upgrade to Mesh 3.0.

access_model_reliable_publish() causes assert in NRF_MESH_ASSERT_DEBUG(bearer_event_in_correct_irq_priority())

RE: Error NRF_ERROR_INVALID_STATE when send data via mesh 3.0

Giang — Sat, 22 Dec 2018 05:10:08 GMT

any help !!