RAK3172 AT_PARAM_ERROR when sending

LPWAN Modules / EVBs
1

I receive an error when I send a base64 encoded packet, however after I send a single byte payload the original packet is sent error free. What do I need to do the fix this? Thanks in advance for any help!!

Here is an example:

AT+SEND=12:A5000000010000013C53333300350001000A001001A000110441BA49AA00120441B625DB00130442ED4FCC00010106FFD00106FFD20106FFD40106FFD6010600010105
<< AT_PARAM_ERROR
AT+SEND=12:00
<<OK
<< +EVT:TX_DONE
AT+SEND=12:A5000000010000013C53333300350001000A001001A000110441BA49AA00120441B625DB00130442ED4FCC00010106FFD00106FFD20106FFD40106FFD6010600010105
<< OK
<< +EVT:TX_DONE

2

What LoRaWAN region?
What DR?
What RUI3 version?

3

Hello @Bernd - thanks for your response! Since posting my question, I determined that DR=0 or DR=1 will return the AT_PARAM_ERROR; so after setting DR=2 the packets sent fine. On your questions:

What LoRaWAN region? US915
What DR? 0 when I wrote the initial message, 2 now
What RUI3 version? RUI_4.0.6_RAK3172-E

Thanks again!

4

Your payload (67 bytes) is too large for DR0 and DR1

==> Maximum Transmission Load by Region
It will always and the error message is most likely a bug in RUI3 V4.0.6

Adjust your DR to match your payload size.
Update RUI3 to the latest released firmware V4.2.3. We fixed many problems since V4.0.6

Update guide ==> RAK3172 WisDuo LoRaWAN Module Datasheet | Specs & Features
Change log ==> Release Versions | RAKwireless Documentation Center

5

Thank you @beegee ! Definitely want to update RUI2 to v4.2.3. Can you confirm that I only need to update the BIN file as the boot loader is working satisfactorily?

Really appreciate your help!!

6

Yes, you only update the bin file. Bootloader is the same.