Update:
The SIM Card was not activated. Now I was able to connect to the Network.
But now, as others mentioned, I cant get the ‘last payload’ in the GUI. I will wait for an update in other posts.

Fixed: The AT commands for this module are slightly different for this chip.

@mybeepad-0

Hey I will try,
The AT commands for the BC660K are documented in a file named Quectel_BC660K-GL_TCP(IP)_Application_Note_V1.0.pdf.
The ping command is the same with BC66 but I used the wrong contextID. This worked for me:
AT+QPING=0,“x.x.x.x”
If you want DNS resolution, you have to configure it first, read the docs at chapter 2.3.8. I didnt try that myself.
The QIOPEN command is different to BC66, best to read the docs but this worked for me:
AT+QIOPEN=0,0,“UDP”,“x.x.x.x”,15683,1001,1

Hope this helps
Daniel

@mybeepad-0

Hey I will try,
The AT commands for the BC660K are documented in a file named Quectel_BC660K-GL_TCP(IP)_Application_Note_V1.0.pdf.
The ping command is the same with BC66 but I used the wrong contextID. This worked for me:
AT+QPING=0,“x.x.x.x”
If you want DNS resolution, you have to configure it first, read the docs at chapter 2.3.8. I didnt try that myself.
The QIOPEN command is different to BC66, best to read the docs but this worked for me:
AT+QIOPEN=0,0,“UDP”,“x.x.x.x”,15683,1001,1

Hope this helps
Daniel

Fixed: The AT commands for this module are slightly different for this chip.

Hello,

I have problems sending/pinging to your server, can you assist?
I am using a BC660K-GL Dev Kit for the first time and was using the BC66 Dev Kit before which worked fine.
It is registered and is assigned an IP.
Debug Output:

+IP: 10.0.5.169

at+cereg?
+CEREG: 0,1
OK

AT+QPING=1,“172.27.131.100”
ERROR

at+qiopen=1,1,“UDP”,“172.27.131.100”,15683,1001,0,0
ERROR

at+cops?
+COPS: 1,2,“26201”,9
OK

at+qcgdefcont?
+QCGDEFCONT: “IP”,“CDP.IOT-MOBILENL”,
OK

at+qband?
+QBAND: 8
OK

Regards
Daniel

Update:
The SIM Card was not activated. Now I was able to connect to the Network.
But now, as others mentioned, I cant get the ‘last payload’ in the GUI. I will wait for an update in other posts.

Hi,

As I am trying to attach the BC66-T-BE DVK to the NB-IoT network, the device doesn’t get an IP assigned. Here is some debug output, that shows, that the setup is ok so far, but AT+CEREG? goes from “trying to attach or searching” to " Not registered" after about 10 seconds. Setup was successful and no errors while reading the IMEI. Any suggestions? Location is east Germany.

at+qrst=1
F1: 0000 0000
V0: 0000 0000 [0001]
00: 0006 000C
01: 0000 0000
U0: 0000 0001 [0000]
T0: 0000 00B4
Leaving the BROM

at+qsclk=0
OK

ate1
OK

at+cereg?
+CEREG: 0,2

at+cereg?
+CEREG: 0,0

at+cops=1,2,“26201”,9
ERROR

at+cops=?
+COPS: (1,“26201”,“26201”,“26201”,9),(0-4),(0-2)

at+qband?
+QBAND: 8

at+qcgdefcont?
+QCGDEFCONT: “IP”,“iot.telekom.net”

at+qigeterror
+QIGETERROR: 0,operate successfully

ati
Quectel_Ltd
Quectel_BC66
Revision: BC66NBR01A10