AT+P2P Bandwidth Parameter

[JBurg (Jan)]

Hi,
according to the Quick Start Guide and the AT Command Manual the AT+P2P command should have the bandwidth in kHz as a number in it, like: AT+P2P=868000000:7:125:0:10:14 for 125 kHz.
However, this command produces an AT_PARAM_ERROR.
When I send AT+P2P=868000000:7:0:0:10:14 instead, the result is OK.
Is the bandwidth to be entered as index (0, 1, 2…) or what could be the mistake?

Regards
Jan

[carlrowan]

Welcome to RAK forum @JBurg ,

There was change on the latest firmware of the version on the parameters of bandwidth. However, we will make the bandwidth parameter backward compatible on the next release of RUI3.

I already answered this question in this forum thread. You can use it as reference.

AT+P2P=868000000:7:125:0:10:14 Commend not working

Hi @pragnesh , I already discussed this to the team and it will be backward compatible on the next release of the RUI3 firmware v3.5.4. Right now, the stable version is 3.5.3. To be compatible on the new convention, you just need to update the 3rd parameter which is the bandwidth. On your test, you use 125. Therefore from AT+P2P=868000000:7:125:0:10:14 it will become AT+P2P=868000000:7:0:0:10:14 You can see that 125 was changed to 0. This follows the other possible bandwidth values: 0 = 12…