Hi,
we are making heavy use of datagrams and have an issue coming up in two types of situations - slave reconnection after a drop or network reconfiguration - in my application there is functionality to reconfigure the network, i.e. disconnect a slave form the current master and connect to another master in the network based on the information in a datagram.
The slave has no problem in joining the new master in terms of base radio connection but the new connection hangs up in terms of the datagram connection. It seems that after a slave is dropped and tries to reconnect the master is not able to clear the datagram queue quickly and after the slave connects it expects confirmations to the old datagrams left in the TX queue and hangs up/blocks the datagram connection since the slave does not have these datagrams any more in its RX queue. It seems that an extra delay of approx. 1s helps although it seems that not always works.
Could you please provide some more details on the timing and event dependencies in the slave reconnection process after a drop when using datagrams ? Does it work this way that the slave can join the master only after the master has cleared the TX datagram queue ? And if so how to check it ? - it seems we join the master when it is not ready yet with the TX queue. If the two mechanisms (radio join and datagram channel) are not synchronized in terms of post-drop clearing then can it be handled with a time delay and if so how long should this delay be to guarantee propoer working ?
Regards, Pawel
