AT Command Permission

LPWAN Modules / EVBs RAK3172
1

Hi all,

I’ve been playing with the WisDuo RAK3272LP board testing some of the RUI3 examples that are available on Arduino.
Checking the “AT Command Permission” example I’ve seen that it’s not working as expected. The example says that it is possible to assign different permission levels to a specific the AT command and limit the functionality.

This is the example on where I added API and firmware version.

CHANGE_ATCMD_PERM("AT+APPKEY", RAK_ATCMD_PERM_READ);
CHANGE_ATCMD_PERM("AT+DEVEUI", RAK_ATCMD_PERM_WRITE);
CHANGE_ATCMD_PERM("AT+PWORD", RAK_ATCMD_PERM_WRITEONCEREAD);
CHANGE_ATCMD_PERM("AT+APPEUI", RAK_ATCMD_PERM_DISABLE);
CHANGE_ATCMD_PERM("AT+ALIAS", RAK_ATCMD_PERM_READ | RAK_ATCMD_PERM_WRITE);

void setup()
{
    Serial.begin(115200);
    delay(1000);
    Serial.println("RAKwireless AT Command Permission Example");
    Serial.print("API version ");
    Serial.println(api.system.apiVersion.get().c_str());
    Serial.print("Firmware version ");
    Serial.println(api.system.firmwareVersion.get().c_str());      
    Serial.println("------------------------------------------------------");
  
}

And the output is:


RAKwireless AT Command Permission Example
API version 3.2.9
Firmware version RUI_4.1.1_RAK3272LP-SiP
------------------------------------------------------
Current Work Mode: LoRaWAN.
AT+DEVEUI=?
AT+DEVEUI=1122334455667788
OK
AT+APPEUI=?
AT+APPEUI=0000000000000000
OK
AT+APPEUI=0102030405060708
OK
AT+APPEUI=?
AT+APPEUI=0102030405060708
OK

The DEVEUI command is set to write only, so it won’t be possible to read the value, only write. The same happens with the APPEUI which it is disabled and in theory not available for the user.
Is there something I’m doing wrong or missing?

Thank you.

Regards,
David

2

I don’t have a RAK3172-SiP module at hand but on RUI3 V4.2.0 with a RAK3172 it works as expected.

CHANGE_ATCMD_PERM("AT+DEVEUI", RAK_ATCMD_PERM_WRITE);

Log output:

> AT+DEVEUI=?
AT_PARAM_ERROR
> AT+DEVEUI=?
AT_PARAM_ERROR
3

Hi Beegee,

Thanks for your quick reply.

As far as I know, RAK3172-SiP and RAK3172 are based on the same STM32WL chipset, so what I don’t understand is why using the same RUI version (v4.2.0) and chipset core, we have different results executing the same code.

Do you have any clue?
Is anything I can test or check?
Thank you.

Regards,
David

4

Seems you found a bug. I found a RAK3172-SiP somewhere in my drawers.

With same permissions you set in your code tested on RAK3172-SiP, using RUI3 V4.2.0

RAK3172-SiP:
Permissions are not changed.

image
image379×525 15.8 KB

I will issue a bug report to the R&D team.

5

Hi Beegee,

Many thanks for your time testing the code and finding that there’s a bug on it.
I’ll wait for the new release to check it again.
I suppose that you won’t have this information, but do you have an idea of when the new release will be available?
Thank you so much.

Regards,
David

6

Hi David,

No, I have no release date.

If the R&D team can provide me with a patch to fix the problem, I will let you know.

7

Hi Beegee,

Thanks a lot.
If you need me to test anything else, just let me know.
Keep in touch.

Regards,
David

8

Hi David,
I will let you know if we need anything else. I submitted the problem to our R&D team. They are back tomorrow from the Chinese New Year holidays, but I cannot commit to any date for the bug to be fixed.