Client 2/3 Cannot Send Error yet message is sent

[jonappleseed]

Hi,

I have modified the light switch demo so that all messages from the client are sent to all servers. I have done this by subscribing all servers to GROUP_ADDRESS_ODD in node_setup.c. Now when I send using button 2/3 (unacked) I get the message Client 2(/3) cannot send, I have found that this is because status == NRF_ERROR_INVALID_STATE. However, it still sends, the servers receive the message and even tell the client. Is it safe to ignore this message?

[Hung Bui]

Hi Jon, 

Are you sure you haven't modified the client ? I don't think the client would act any different if you have all server to subscribe to GROUP_ADDRESS_ODD. When you are sending with unAcked message, the client wouldn't care who are subscribing. 

Please try to step into the code (or printing log) to see what exactly throwing NRF_ERROR_INVALID_STATE.

[jonappleseed]

I have modified the client by making it send bytes of data rather than a single byte and I've also added some timing code. However, this should not explain why Client 2 and 3 give this error but 0 and 1 do not. I have also enable Instaburst, but I have the same code without Instaburst enabled with the same problem. I will try to find where NRF_ERROR_INVALID_STATE is being set.

[jonappleseed]

Ok, so it is being set in segmented_packet_tx() in transport.c (line 1205)

[Hung Bui]

Yes, segmented messages can only be sent one by one.You can't have 2 segmented messages sending at the same time. 

[jonappleseed]

I found that it's being set for any clients/buttons at that line.

[jonappleseed]

The problem is actually caused in packet_alloc_and_tx() in access.c (~line 462). In the case of buttons 2/3 the if statement is true, causing the status to be returned as NRF_ERROR_INVALID_STATE rather than NRF_SUCCESS as in the case of buttons 0 and 1.