RAK3172 Send fail

LPWAN Modules / EVBs
#1

testing RAK3172 communication.

As shown in the log below, it was being sent normally,
but when it was sent again 3 hours later, a failure event message was displayed.

The network status was checked with “AT+NJS=?” and was judged to be normal.
As a result of resending again, the event message “+EVT:SEND_CONFIRMED_FAILED(4)” was displayed.

After sending the “AT+JOIN=1:0:8:8” command, we confirmed that data was being sent normally.

But I can’t figure out what the problem is.
Is it possible that the join will not continue and a timeout will occur?

### LOG ###
Version: RUI_4.0.6_RAK3172-E
Current Work Mode: LoRaWAN.
[02:05:29.625]AT+JOIN=1:0:8:8
[02:05:29.665]OK
[02:05:34.803]+EVT:JOINED
[02:05:43.690]AT+SEND=2:12345678
[02:05:43.721]OK
[02:05:44.845]+EVT:SEND_CONFIRMED_OK
[05:14:03.254]AT+SEND=2:12345678
[05:14:03.286]OK
[05:14:07.307]+EVT:SEND_CONFIRMED_FAILED(4)
[05:14:10.542]AT+NJS=?
[05:14:10.566]AT+NJS=1
OK
[05:14:15.423]AT+SEND=2:12345678
[05:14:15.455]OK
[05:14:18.474]+EVT:SEND_CONFIRMED_FAILED(4)
[05:17:41.786]AT+JOIN=1:0:8:8
[05:17:41.838]OK
[05:17:46.969]+EVT:JOINED
[05:17:49.035]AT+SEND=2:12345678
[05:17:49.069]OK
[05:17:50.180]+EVT:SEND_CONFIRMED_OK
[05:17:51.983]AT+CFS=?
[05:17:52.022]AT+CFS=1

#2

There is usually no timeout for a join.
Ideally a LoRaWAN device needs to join only once after it’s powered up and it stays connected.

What LoRaWAN server are you using.

#3

I’m using chirpstack V4.

It was sent 16 hours later, but this time it was sent normally.
I’m not sure what this error is about.

#4

Did you restart or power off Chirpstack during this time?

#5

No, I didn’t reboot.

And another problem occurred while testing several boards.

I sent “AT+SEND”
Output event logs are different.

All modules under test have the same configuration.

I’ve seen “+EVT:SEND_Confirmed_OK” printed so far,
I connected a new RAK3172 module to see if the log “+EVT:TX_DONE” is output.
How do I get log “+EVT: SEND_confirmed_OK”?

## LOG1 ##

[05:17:42.876]ATZ
[05:17:42.928]
[05:17:43.114]RAKwireless RAK3172

Version: RUI_4.0.6_RAK3172-E
Current Work Mode: LoRaWAN.
[05:18:05.608]AT+JOIN=1:0:8:8
[05:18:05.643]OK
[05:18:10.780]+EVT:JOINED
[05:18:15.029]AT+SEND=2:12345678
[05:18:15.066]OK
[05:18:16.166]+EVT:SEND_CONFIRMED_OK

## LOG2 ##

[05:17:58.044]ATZ
[05:17:58.119]
[05:17:58.321]RAKwireless RAK3172

Version: RUI_4.0.6_RAK3172-E
Current Work Mode: LoRaWAN.
[05:18:07.753]AT+JOIN=1:0:8:8
[05:18:07.839]OK
[05:18:12.983]+EVT:JOINED
[05:18:16.554]AT+SEND=2:12345678
[05:18:16.598]OK
[05:18:17.709]+EVT:TX_DONE

#6

+EVT:SEND_CONFIRMED_OK is the response for a confirmed packet transmission.
+EVT:TX_DONE is the response for an unconfirmed packet transmission.

The module does not switch between confirmed and unconfirmed packet mode without an AT command.

Default is unconfirmed. If you need confirmed packet mode, you can enable it with AT+CFM=1

Regarding your problem that after a long time of no transmission, the module has to re-join, can you check with the Chirpstack communitity about this problem. It should not happen. I am using Chirpstack V4 a lot, but my devices are sending data at least every 10 minutes and I never saw this problem.

1 Like
#7

All right.
Thank you for your answer.

#8

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.