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 see high packet loss when sending rapid UDP packets without yield() or delay(). A yield() after each packet does only help slightly, but delay(1) after each Udp.write() works around that bug.
Problem description:
The MAC layer seems to drop packets if the send queue is full, but this condition is not reported back to the application (endPacket() should return 0 in this case).
The text was updated successfully, but these errors were encountered:
igrr
changed the title
errors from netif->output will bubble up to udp_send, but we aren't forwarding them to WiFiUdp class
Check return value of udp_send and forward it WiFiUdp::endPacket
Feb 29, 2016
so i guess it's up to espressif to fix this then. :-/ no idea where to
report this though.
On Wed, Mar 2, 2016 at 6:00 PM, Ivan Grokhotkov [email protected]
wrote:
I have addressed this in commit aa67d1c aa67d1c,
however it appears that udp_sendto doesn't actually return errors when
underlying packet buffer is full.
—
Reply to this email directly or view it on GitHub #1696 (comment).
I see high packet loss when sending rapid UDP packets without yield() or delay(). A yield() after each packet does only help slightly, but delay(1) after each Udp.write() works around that bug.
Problem description:
The MAC layer seems to drop packets if the send queue is full, but this condition is not reported back to the application (endPacket() should return 0 in this case).
The text was updated successfully, but these errors were encountered: