Proposal: using Mespnow in ESP-NOW strategy
michael-sayapin opened this issue · 1 comments
Currently ESP-NOW strategy is limited to sending 250 - overhead bytes packets. Using Mespnow high-level APIs could lift this limitation and allow sending much larger payloads.
https://docs.espressif.com/projects/esp-mdf/en/latest/api-reference/mespnow/index.html
Features
Retransmission filter: Mespnow adds a 16-bit ID to each fragment, and the redundant fragments with the same ID will be discarded.
Fragmented transmission: When the data packet exceeds the limit of the maximum packet size, Mespnow splits it into fragments before they are transmitted to the target device for reassembly.
Cyclic Redundancy Check: Mespnow implements CRC when it receives the data packet to ensure the packet is transmitted correctly.
The API is very similar, and changing it should be pretty straightforward. If interested, I will work on submitting a PR in the near future.
Ciao @michael-sayapin thank you very much for your support to the project.
For sure the additional features of mespnow are interesting, could simplify life to PJON over ESPNOW users.
I would be happy to test your contribution and include it in master if feasible.
Thank you again.