Mesh reliable message

[Damien Berger]

Hi, i am working on a message model based on the simple_on_off model. I am able to send and receive a buffer via unicast or multicast. Now i am trying to develop a reliable "send" as implemented in the simple_on_off model.

I don't know how to stop my model to send the reliable message. I think it comes from my function "reliable_message_cb" similar to "reliable_status_cb" ( from simple_on_off_client) which is the one that disable the transfer ("p_client->state.reliable_transfer_active = false;"). My function is never called...

Can you explain me how this function is called for the simple_on_off model ? 

Maybe the problem comes from somewhere else : after sending my reliable message from my client, the server respond with a very simple message (similar to the status message), maybe i am missing something in the reception of this message to stop the transfer ?

Thanks for your help

[Mttrinh]

Hi,

I'm not sure I understand what you mean by "I don't know how to stop my model to send the reliable message". You need to make sure the server are sending you an ACK and after that ACK is received on the client, the client will call the callback. Can you give me more details about your issue and clarify what exactly that you are observing?

[Damien Berger]

As i said in my second post:

"The calling function is access_reliable_rx_cb, now it works better, my problem was in the find_index function : the model handles were not the same. Now it stops sending after receiving the "ACK" message."
"Now i have an other doubt : the first reliable message sent is correct but if the server does not respond with an ACK, the others messages sent does not contain the right packet, they have the right size, but the content is different."

You have more details in my others replies.
Thank you