Open metro69 opened 1 year ago
Are you being rate limited by your regional LoRaWAN parameters?
I don't think so. It seems more a matter of the lorawan code generating interrupts that interfere with the serial.print and dropping the send request without any failure indication.
If I leave ~10s between button presses, transmits seem to work.
I would expect the API to be robust to signal the send call to not succeed if the system is not ready to accept another send.
Yep, the codebase isn't that good. And it is not well maintained at the moment. Guys from Heltec are not really responsive on this repository.
I am running the LoRaWan_interrupt example on a HTCC-AB01 v2 board.
Without any changes, I am losing ~50% of all USER_KEY presses: the interrupt happens, but the LoRaWAN transmit never happens.
In the serial output below, every � coincides with a missed transmit.
It looks like some other interrupt is interfering with the
LoRaWAN.send
command.