2: Attach to NB-IoT network

After you have setup your devkit successfully you learn in this chapter how you can attach your device with the NB-IoT network.

The basic NB-IoT configuration parameter which you need during your journey through the network attach you can find on the page IoT Configuration Parameter

👍

Good Luck !!

This chapter explains how you can attach the BC66-T-BE DVK to the NB-IoT network. I recommend to read the chapter "Setup Quectel BC66-T-BE DVK" first.

🚧

If you are only interested in the conclusion of the AT commands to configure the network setup scroll to the end of this document under the header "AT Commands to setup Network Configuration".

📘

In case you are looking for any documentation documents go to the setup chapter of the device.

After you switched on the device and deactivated the auto-sleep (AT+QSCLK=0) and activated the echo of inputs (ATE1) you can configure the network setup for the module with the following steps:

Set mobile operation band: AT+QBAND=1,8

AT+QBAND=1,8
OK

Switch off radio functionality: AT+CFUN=0

AT+CFUN=0
OK

Setup APN for iotcreators protocol server "scs.telekom.tma.iot"

See this page https://docs.iotcreators.com/docs/general-settings for the other available APNs

AT+QCGDEFCONT="IP","scs.telekom.tma.iot"

Restart device after network setup
Some configurations of the network setup will only take effect after the device has been restarted.

Restart device: AT+QRST=1

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

Don't forget to disable auto-sleep and enable echo of inputs:

AT+QSCLK=0
OK

ATE1
OK

If everything works you should get an IP address displayed after 10-45 seconds which the device has been assigned by the network.

+IP: 10.0.0.239

👍

Yeah!! If you can see the IP address on the console after starting up the device you did everything perfect and your are now ready to send and receive data.

If that is not the case and the device doesn't get an IP address the problem can be fixed sometimes by defining local operator explicity.

Configure operator manually: AT+COPS=1,2,"26201"

AT+COPS=1,2,"26201"

AT+COPS=1,2,"20416"

AT+COPS=1,2,"23203"

AT Commands to setup Network Configuration

# Deactivate auto-sleep
AT+QSCLK=0
OK

# Switch on echo mode
ATE1
OK

# Set the band to band 8 (900 MHz) for Telekom NB-IoT network
AT+QBAND=1,8
OK

# Turn off the radio
AT+CFUN=0
OK

# Setup APN for T-Mobile Netherland
AT+QCGDEFCONT="IP","cdp.iot.t-mobile.nl"

# Configure local operator manually: Germany, Telekom
AT+COPS=1,2,"26201" 
# Configure local operator manually: Netherland, T-Mobile
AT+COPS=1,2,"20416" 
# Configure local operator manually: Austria, T-Mobile
AT+COPS=1,2,"23203" 

# Restart the module as some configurations only take place after a reboot
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

# Deactivate auto-sleep
AT+QSCLK=0
OK

# Switch on echo mode
ATE1
OK

+IP: 10.0.0.239