Asynchronous replies are not sent automatically

LPWAN Modules / EVBs RAK3172
1

Hi,

Out of the blue (no firmware update, no change in settings I’m aware of) I’ve got the following problem:

All async replies (+EVT:) such as +EVT:JOINED are not automatically placed on the UART line by the RAK3172 module. I first have to send an AT command by the connected host to get the latest URC.

for example:

[INFO][RAK]: AT TX ( 8): AT+JOIN=
[INFO][RAK]: AT TX ( 1): 1
[INFO][RAK]: AT TX ( 1): :
[INFO][RAK]: AT TX ( 1): 0
[INFO][RAK]: AT TX ( 1): :
[INFO][RAK]: AT TX ( 2): 15
[INFO][RAK]: AT TX ( 1): :
[INFO][RAK]: AT TX ( 1): 5
[INFO][RAK]: AT TX ( 2):
[INFO][RAK]: AT RX ( 3): OK
[INFO][RAK]: AT RX ( 1):

… no async event incoming, but I’m connected when I call +NJS a few seconds later:

[INFO][RAK]: AT TX ( 8): AT+NJS=?
[INFO][RAK]: AT TX ( 2):
[INFO][RAK]: AT RX (26): +EVT:JOINEDAT+NJS=1OK

… here we go: +EVT:JOINED is placed on the UART line.

So what do I do wrong? Is there any setting that prevents +EVT async events to be placed on the UART?

My firmware version is: RUI_4.0.5_RAK3172-E

Thank you,
Andy

2

Welcome to RAK forum @Andir ,

+EVT:JOINED will only return once the device received the join downlink. This can take more than few seconds so what you see is normal.

3

Could be your terminal app if you do not see the response without sending another command.
What are the settings in your terminal app to detect the end of line of received data?
The RAK3172 will end it’s +EVT messages with a CR/LF.

4

Thank you very much for your prompt replies.

Unfortunately, it’s a compilation error on my host mcu, so the RAK3172 device actually works fine.

Its fixed now and everything works as expected. I appreciate your help!