LTE/NB-IOT connection with MIKROE LTE IOT 4 CLICK

Question

Hii, 
 
 I´m working with LTE IoT 4 Click, by Mikroe, that use a nrf9160. 
 I need to connect to network with my modem, but i have some erros. My goal is to communicate with LTE or NB-IoT (preference for LTE). 
 
 When a trying to connect, my modem restart or not connect. I tested with basic examples: at_client, at_monitor and some samples provided for DevAcademy course, Cellular IOT Fundamentals. 
 
 My setup is:

Im using a nRF52840 to program my device. I want only use LTE, so i used a antenna by Digi: 76000926 ( https://es.digi.com/products/models/antennas/76000926) . 
 On the NRF CONNECT SDK, i`m using a nRF9160 DK NRF9160 Non Secure board: 
 When i tried with standart samples by NRF Connect SDK: 
 AT_MONITOR SAMPLE 
 ``` 
 *** Booting nRF Connect SDK 3758bcbfa5cd *** AT Monitor sample started Subscribing to notifications Connecting to network Resuming link quality monitor for AT notifications Waiting for network Network connection timed out Continuing without network Pausing link quality monitor for AT notifications Reading PSM info... PSM: disabled Enabling PSM Reading PSM info... PSM: disabled Periodic TAU string: Active time string: 00100001 Modem response: +CEREG: 1,4 OK Shutting down modem Network registration status: no network Bye ---- Closed the serial port /dev/ttyUSB0 ---- 
 
 AT_CLIENT WITH NB-IOT 
 *** Booting nRF Connect SDK v2.7.0-5cb85570ca43 *** *** Using Zephyr OS v3.6.99-100befc70c74 *** The AT host sample started Ready ---- Sent utf8 encoded message: "AT+CFUN=4
" ---- OK ---- Sent utf8 encoded message: "AT%XSYSTEMMODE?
" ---- %XSYSTEMMODE: 0,1,0,2 OK ---- Sent utf8 encoded message: "AT+CIND=1,0,1
" ---- OK ---- Sent utf8 encoded message: "AT+CFUN=1
" ---- OK ---- Sent utf8 encoded message: "AT+CGDCONT?
" ---- +CGDCONT: 0,"","","",0,0 OK ---- Sent utf8 encoded message: "AT+CGDCONT=0,\"IP\",\"smart.m2m.vivo.com.br\"
" ---- OK ---- Sent utf8 encoded message: "AT+CGDCONT?
" ---- +CGDCONT: 0,"IP","smart.m2m.vivo.com.br","",0,0 OK ---- Sent utf8 encoded message: "AT+COPS?
" ---- +COPS: 0 OK ---- Sent utf8 encoded message: "AT+CEREG=2
" ---- OK ---- Sent utf8 encoded message: "AT+CEREG?
" ---- +CEREG: 2,2 OK ---- Sent utf8 encoded message: "AT+CIMI
" ---- 724238041443476 OK ---- Sent utf8 encoded message: "AT+CGATT?
" ---- +CGATT: 0 OK ---- Sent utf8 encoded message: "AT+CGATT=1
" ---- OK ---- Sent utf8 encoded message: "AT+CGATT?
" ---- +CGATT: 0 OK ---- Sent utf8 encoded message: "AT+CEREG?
" ---- +CEREG: 2,2 OK ---- Sent utf8 encoded message: "AT+CGATT?
" ---- +CGATT: 0 OK ---- Sent utf8 encoded message: "AT+CEREG?
" ---- +CEREG: 2,2 OK 
 
 AT_CLIENT WITH LTE 
 *** Booting nRF Connect SDK v2.7.0-5cb85570ca43 *** *** Using Zephyr OS v3.6.99-100befc70c74 *** The AT host sample started Ready ---- Sent utf8 encoded message: "AT+CFUN=4
" ---- OK ---- Sent utf8 encoded message: "AT%XSYSTEMMODE=1,0,0,0
" ---- OK ---- Sent utf8 encoded message: "AT%XSYSTEMMODE?
" ---- %XSYSTEMMODE: 1,0,0,0 OK ---- Sent utf8 encoded message: "AT+CIND=1,0,1
" ---- OK ---- Sent utf8 encoded message: "AT+CFUN=1
" ---- OK *** Booting nRF Connect SDK v2.7.0-5cb85570ca43 *** *** Using Zephyr OS v3.6.99-100befc70c74 *** The AT host sample started Ready 
 Im send and receive AT Commands from UART0 (TX=29, RX=28). 
 
 When i trying with NB-IoT, the connection was not made. When trying with LTE, the modem restart. 
 
 I believe that my SIMCARDs are ok because i tried in other modules (SIM7080G) and all is ok. 
 
 I need help.

Achim Kraus · Accepted Answer

I use such a MIKROE LTE IOT 4 CLICK with success. Here in south Germany both works LTE-M and NB-IoT. 
 I use also the nrf9160dk_nrf9160_ns board definition and add the mikroe specific stuff using an additional mikroe.overlay and also some mikroe-prj.conf . (The CONFIG_UART_RX_PULLDOWN=y is specific to my project, just skip it.) 
 I'm not sure, what you use as power supply, it need to be a 3.3V one. 
 And you may need to update the modems firmware to 1.3.6 as well.

Achim Kraus · Answer

modem firmware update: 
 Your logs shows "mfw_nrf9160_1.3.5", that's pretty well. I don't consider 1.3.6 will solve the issue. 
 Anyway: 
 I usually use a jlink and the "nRF connect for Desktop" and there the "Programmer" App. 
 First connect the MIKROE with the JLink (your nRF???-DK) and power up both. 
 Then start the "nRF connect for Desktop" and the "Programmer" app there. 
 Select your JLink as "Device" in the "Programmer" app. 
 Load the "mfw_nrf9160_1.3.6.zip" into the "Programmer" app ... wait 
 If all goes well, the "Write" button gets enabled and you start the update pressing that. 
 A special "Modem Dialog" shows up. Press OK and wait a couple of seconds (30s and more). 
 On finish you get noticed by the "Programmer" app. 
 Restart the MIKROE device.

Achim Kraus · Answer

> My power supply is 3.3V, come from TTL. 
 Not sure, what that means? Do you use a USB-Serial-TTL converter? And the 3.3V are from that? I don't think, that this provides enough current, the most will only provide 75mA and more than 500mA will be required as peak. (The most USB-Serial-TTL even don't supply 3.3V, they supply 5V and only use 3.3V on the I/O). 
 > Can you tell me if my sequence of AT commands is correct? 
 What I see, but it may be caused by something different and unknown, 
 ################################ 
 ---- Sent utf8 encoded message: "AT+CFUN=1
" ---- OK *** Booting nRF Connect SDK v2.7.0-5cb85570ca43 *** *** Using Zephyr OS v3.6.99-100befc70c74 *** The AT host sample started 
 ################################ 
 that indicates an "reboot", my guess, because of your power supply.

Achim Kraus · Answer

Just in the case, you're still interested or someone else reads this thread. 
 A normal USB serial adapter as power supply will not work. 
 But there are special ones as CANADUINO&reg; Breadboard Power Supply 3.3V, 5V, 12V with USB-UART which works pretty well for power and serial-to-USB.

LTE/NB-IOT connection with MIKROE LTE IOT 4 CLICK

Top Replies