You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think there is a problem with the dafault value of AckTimeoutRetriesCounter.
When I configure LoRaMacSendConfirmedFrame with nbRetries=1, the frame is sent one time( with ACK timeOut of course). and if configure nbRetries=2, the frame is sent two times.
Normally, the number of retrie is in more of the first frame. So if the value of nbRetries is 3, 4 frames are sent if there is no Acknowledge.
Thanks
GF.
The text was updated successfully, but these errors were encountered:
iirc if nbRetries = 0 the value reverts to some default. so nbRetries actually represents "number of retries - 1"? If so, maybe this just needs to be documented better... EDIT: this is the case for NbRep in LinkADRReq MAC command, NOT for LoRaMacSendConfirmedFrame.
Looks to me now that AckTimeoutRetries and AckTimeoutRetriesCounter could use zero as a base with a few additional changes, but at this point it could break compatibility for anyone using the new API and the value of McpsConfirm.NbRetries. Again, maybe this just needs to be documented better?
thanks for the report. Please intrepret the attribute "nbRetries" as the "number of trials". We will update the name of the attribute "nbRetries" and also the related documentation in the next release.
Hi,
I think there is a problem with the dafault value of AckTimeoutRetriesCounter.
When I configure LoRaMacSendConfirmedFrame with nbRetries=1, the frame is sent one time( with ACK timeOut of course). and if configure nbRetries=2, the frame is sent two times.
Normally, the number of retrie is in more of the first frame. So if the value of nbRetries is 3, 4 frames are sent if there is no Acknowledge.
Thanks
GF.
The text was updated successfully, but these errors were encountered: