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
Hi,
I'm testing the library with ABP and unconfirmed frames.
After a frame is successfully sent (say frame A), if one tries to send another one (say frame B) before the duty-cycle allows it, modem.endPacket(false) returns no error, but the frame is not actually sent. Subsequent calls return error (rightly so) until the duty-cycle is available again.
It looks like frame B is queued and, when modem.endPacket(false) returns no error for another frame (say frame C), what is actually sent is the previously queued frame B.
It looks like modem.endPacket(false) return no error if there is no other frame waiting to be sent even though this frame won't be sent.
If this is the intended behaviour (I hope not), is there a way to know if a frame has actually been sent and not only queued? And a way to remove queued but unsent frames?
Otherwise there would be no way to know what frame is actually sent...
Thanks!
The text was updated successfully, but these errors were encountered:
I posted an issue #62 and another new issue #63 that I think is related to this problem. From what I have found with those two issues, I can see how this could happen. Moreover, I believe I have experienced what you describe which is what lead me down this path.
Hi,
I'm testing the library with ABP and unconfirmed frames.
After a frame is successfully sent (say frame A), if one tries to send another one (say frame B) before the duty-cycle allows it,
modem.endPacket(false)
returns no error, but the frame is not actually sent. Subsequent calls return error (rightly so) until the duty-cycle is available again.It looks like frame B is queued and, when
modem.endPacket(false)
returns no error for another frame (say frame C), what is actually sent is the previously queued frame B.It looks like
modem.endPacket(false)
return no error if there is no other frame waiting to be sent even though this frame won't be sent.If this is the intended behaviour (I hope not), is there a way to know if a frame has actually been sent and not only queued? And a way to remove queued but unsent frames?
Otherwise there would be no way to know what frame is actually sent...
Thanks!
The text was updated successfully, but these errors were encountered: