Nordic Thingy91: nRF9160 AT Command %XBANDLOCK not working

Hello,

I am using Nordic Thingy91 5G board. My modem firmware version is 1.3.6. My nRF Connect for Desktop version is 5.2.0, which has a Serial Terminal version of 1.5.0. I am using VS Code for the source code and conf file. My nRF Connect SDK Toolchain version is 2.6.0, and my nRF Connect SDK version is also 2.6.0. I used and modified the sample 'azure_iot_hub' and used Git Bash to build the application hex file which was then flashed onto the Nordic Thingy91 5G board by using the Programmer (v4.6.0) in nRF Connect for Desktop.

Then, I connected the 5G board to power. It was working perfectly since I received an email with the deviceID. I connected the 5G board to my laptop and typed the following command in Serial Terminal in nRF Connect for Desktop, and I got the following results. I also attached the screenshots in sequential order. 

AT: 'OK', indicating command understood

AT%XCBAND: '%XCBAND: 12   OK', indicating that it is currently using band 12

AT%XCBAND=?: '%XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)   OK', indicating the available bands

AT+CGMR: 'mfw_nrf9160_1.3.6   OK', indicating the firmware version

AT%XBANDLOCK?: '%XBANDLOCK: "",""   OK', indicating no bands currently locked to

               

It looked like everything was working fine. Now I tried to lock the 5G board's LTE band of operation by using the %XBANDLOCK command provided here: Band lock %XBANDLOCK. However, if I tried their example commands in the Serial Terminal, the results were 'error' as shown below. Did anyone have this issue before? I really appreciate it if anyone could help me solve this. 

    

    

Thank you very much for your help!

: )

 

Related