I got a BG96 MiniPCIe interface, and use it in NBIoT mode.
Initially, this BG96 can’t get DNS config from operator.
So, I modify AT+QCFG=“nccconf”, 1 to AT+QCFG=“nccconf”, 101.
Then it can get DNS config from operator, at this point the version is BG96MAR02A07M1G_01.016.01.016.
And recently I upgrade this BG96 to BG96MAR02A07M1G_01.017.01.017.
I found it can get DNS config from operator. And AT+QCFG=“nccconf”, 1.
It 's strange for me, because I use the same modem and sim card, but behavior looks different.
Do I still need to care this “nccconf” config ?
Does BG96 new FW can handle this issue ?
Or something wrong ?
Could you explain this to me ?
Hi Wich_Lio
According to your description, we conducted related tests. When the firmware version is BG96MAR02A07M1G_01.016.01.016, use AT + QCFG = “nccconf”, 1 BG96 can obtain the DNS configuration from the operator, but it cannot when using AT + QCFG = “nccconf”,101. When the version is BG96MAR02A07M1G_01.017.01.017, the test result is the same as BG96MAR02A07M1G_01.016.01.016.
Based on your description，this situation may be related to the device not restarting after the <cap_val> parameter setting is completed, and the local network operator parameters. If this problem occurs again, you can provide the log to us. We provide you with the AT test command record when the firmware version is BG96MAR02A07M1G_01.016.01.016, you can check it.
Thanks for your kindly reply, I will arrange a test to verify again.
