AT_PARAM_ERROR using AT+SEND

We are using RAK3172 and we are getting an AT_PARAM_ERROR error when trying to send data using AT+SEND. We already check that data is in hex pairs.
Here is the log:

RAKwireless RAK3172-E Example

Current Work Mode: LoRaWAN.
AT+VER=?
AT+VER=RUI_4.0.1_RAK3172-E
OK
AT+NJM=1
OK
AT+CLASS=A
OK
AT+BAND=6
OK
AT+APPEUI=0011223344556677
OK
AT+APPKEY=00112233445566778899aabbccddeeff
OK
AT+CFM=1
OK
AT+ADR=0
OK
AT+MASK=0001
OK
AT+JOIN=1
OK
+EVT:JOINED
AT+SEND=2:735342014300146A1727745F614210A845001A5800107800007200004D0000
AT_PARAM_ERROR
AT+SEND=2:735342014300146A1727745F614210A845001A5800107800007200004D0000
AT_PARAM_ERROR
AT+SEND=2:735342014300146A1727745F614210A845001A5800107800007200004D0000
AT_PARAM_ERROR

If I try a smaller package like
AT+SEND=2:735342014300146A172774
it works.

What I’m missing? Do I have to configure anything else?

Welcome to RAK forum @flanzaiof ,

It is likely that your DR is low. Can you check it via AT+DR=?

If your DR is 0, it is likely that the payload exceeds the limit.

1 Like

Hi,

using V4.0.5 I’m now experiencing the same problem with longer payloads (above 20 bytes)

Every second AT+SEND command results in AT_PARAM_ERROR. The payload is in correct format.

[INFO][RAK ]: AT TX ( 8): AT+SEND=
[INFO][RAK ]: AT TX (58): 1:01010000000000000000410DCA5E41D2700000000020000000000000
[INFO][RAK ]: AT TX ( 2): <cr><ln>
[INFO][RAK ]: AT RX ( 3): AT_
[INFO][RAK ]: AT RX (13): PARAM_ERROR<cr><ln>

What I tried to mitigate

  • Changed data rate (problem still there but less often)
  • different gateways

Any ideas what may cause the problem? I wouldn’t consider 20-30 bytes a very long message which would fail so often.

Thanks,
Andy