RAK3172 Baud rate much too slow

Hi Carl,
The document indicates that the module must restarted for the new baud rate to take effect.
This means hardware reset?

Thank you

Thanks Carl,
Thus a hardware reset will do also.

Why is the SF limited to 6?
The chipset can do 5.
This limits the maximum bit rate.
The higher bit rates is extremely useful for OTA firmware upgrades.

What is the maximum payload in P2P?
The AT command document doesn’t say.
Looks like 250 bytes (500 hex characters)


In AT+PRECV=65535 how does it know when packet is fully received?

I see there is no sleep command.
How to put the device into sleep mode?
If it goes into sleep mode automatically, how long does it take to wake-up?
Do you just send a command to wake it and wait for OK?

Thank You

Hi @frank_r ,

SF5 will be supported on the next FW update. No exact schedule yet. We just released the latest version.

Maximum payload in p2p mode is 255.

P2P packets have no confirmation built-in. You have to include it in your application code if needed.

RAK3172 sleeps automatically so there is no sleep command. Any input to LPUART will wake it up.

Thanks Carl,

The maximum packet length and sleep / wake-up should be noted in the AT command document.

If I understand correctly, when the RAK3172 goes to sleep , when a command is sent to it (UART2/LPUART1 Interface) it will wake it up.
Will that command be executed with an OK?
This would make sense.

I have some parts on order, I’ve asked they they be programmed with the latest firmware.
I will observe the timings.
There is one very critical timing when a packet is sent.
The OK should after the packet is. We need this.
This was confirmed to me a few months back.

You see the RAK811 gave a lot problems in terms of timing, hanging and other unexpected behaviour.
The RAK811 takes 1.2s to change frequency!!!
And the from LoraWAN to P2P.
The frequency change is a much bigger issue.
Since mode change is only done once.

These should be store in FLASH

  • Mode (P2P / LoRaWAN)

Thank you