LoRa E5 MSG Done response when message not successfully sent

Products & Technology
#1

I have a few E5 sensors running at the moment and I’m finding on the odd occasion a device will join the LNS (in this case TTN) but fail to get the message through. I’d like to overcome this in python by checking the response out of the E5 to reinitiate if needed but I’m only getting the following back -

+MSG LoRaWAN modem is busy
+MSG LoRaWAN modem is busy
+MSG LoRaWAN modem is busy
+MSG LoRaWAN modem is busy
+MSG LoRaWAN modem is busy
+MSG LoRaWAN modem is busy
+MSG LoRaWAN modem is busy
+MSG Done

It appears the modem is either trying and eventually giving up or it’s trying and assuming it’s ok - I can’t tell if TTN provides the E5 with an acknowledgement of message received.

Does anyone have a solution for ironing out these missed messages?

Cheers

#2

Hi,

Not an answer but an up on likely the same issue.

I resume my work with Seeeduino LoRaWan card. I used to get my data on TTN without problem.
But now, when the setup fonction makes:

while(!lora.setOTAAJoin(JOIN));
result = lora.transferPacket("coucou",10);

I get on the serial port:

16:50:03.102 -> +JOIN: Start
16:50:03.102 -> +JOIN: NORMAL
16:50:19.106 -> +MSG: LoRaWAN modem is busy
16:50:19.106 -> +JOIN: Join failed
16:50:19.106 -> +JOIN: Done

What should I look for?