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

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

Achim Kraus — Mon, 23 Sep 2024 13:47:07 GMT

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® Breadboard Power Supply 3.3V, 5V, 12V with USB-UART which works pretty well for power and serial-to-USB.

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

Achim Kraus — Tue, 20 Aug 2024 08:18:40 GMT

> 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\r\n" ----
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.

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

Achim Kraus — Tue, 20 Aug 2024 08:07:19 GMT

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.

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

Luis Santos — Mon, 19 Aug 2024 20:15:16 GMT

Thank you very much for your reply!

Im from Brazil. My power supply is 3.3V, come from TTL.

I tried your suggestions, but the errors are still the same. Below is the sequence of AT commands and the returns for two scenarios: without the .overlay and prj.conf suggestions, and with them. Here ir my application: https://github.com/sluissantos/lte_4_click.

at_client with nrf9160dk_nrf9160ns (testing with NB-IOT SYSTEMMODE=0,1,0,0)

---- Opened the serial port /dev/ttyUSB0 ----
*** 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\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CGMR\r\n" ----
mfw_nrf9160_1.3.5
OK
---- Sent utf8 encoded message: "AT+CFUN=4\r\n" ----
OK
---- Sent utf8 encoded message: "AT%XSYSTEMMODE=0,1,0,0\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CIND=1,0,1\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CFUN=1\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CGDCONT=1,\"IP\",\"smart.m2m.vivo.com.br\"\r\n" ----
OK
---- Sent utf8 encoded message: "AT+COPS=0\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CEREG=2\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CIMI\r\n" ----
724238041443476
OK
+CEREG: 2,"5867","034C4997",9
+CEREG: 2
---- Sent utf8 encoded message: "AT+CGATT?\r\n" ----
+CGATT: 0
OK
---- Sent utf8 encoded message: "AT+CEREG?\r\n" ----
+CEREG: 2,2
OK
---- Sent utf8 encoded message: "AT+CESQ\r\n" ----
+CESQ: 99,99,255,255,29,64
OK
---- Sent utf8 encoded message: "AT+CSQ\r\n" ----
+CSQ: 99,99
OK
+CEREG: 2,"A8AD","0318182D",9
+CEREG: 2

at_client with nrf9160dk_nrf9160ns (testing with LTE-M SYSTEMMODE=1,0,0,0)
*** 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\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CGMR\r\n" ----
mfw_nrf9160_1.3.5
OK
---- Sent utf8 encoded message: "AT+CFUN=4\r\n" ----
OK
---- Sent utf8 encoded message: "AT%XSYSTEMMODE=1,0,0,0\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CIND=1,0,1\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CFUN=1\r\n" ----
OK
*** Booting nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
The AT host sample started
Ready

at_client with nrf9160dk_nrf9160ns with overlay (testing with NB-IOT SYSTEMMODE=0,1,0,0)

*** 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\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CGMR\r\n" ----
mfw_nrf9160_1.3.5
OK
---- Sent utf8 encoded message: "AT+CFUN=4\r\n" ----
OK
---- Sent utf8 encoded message: "AT%XSYSTEMMODE=0,1,0,0\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CIND=1,0,1\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CFUN=1\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CGDCONT=1,\"IP\",\"smart.m2m.vivo.com.br\"\r\n" ----
OK
---- Sent utf8 encoded message: "AT+COPS=0\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CEREG=2\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CIMI\r\n" ----
724238041443476
OK
---- Sent utf8 encoded message: "AT+CGATT?\r\n" ----
+CGATT: 0
OK
---- Sent utf8 encoded message: "AT+CEREG?\r\n" ----
+CEREG: 2,2
OK
+CEREG: 2,"A8AD","031A1C28",9
+CEREG: 2
---- Sent utf8 encoded message: "AT+CESQ\r\n" ----
+CESQ: 99,99,255,255,31,43
OK
---- Sent utf8 encoded message: "AT+CSQ\r\n" ----
+CSQ: 99,99
OK

at_client with nrf9160dk_nrf9160ns with overlay (testing with LTE-M SYSTEMMODE=1,0,0,0)

Can you tell me if my sequence of AT commands is correct?

I observed that my antenna signal quality is not as expected, but I don't know if this is happening because my connection failed. Is it possible that my signal would be available even though my connection failed?

This firmware version appears after I build the standard at_client sample. Can you tell me how I can update a custom firmware to version 1.3.6?

I tried running your Zephyr application, but since I have limited experience with this, I wasn't able to do it.

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

Luis Santos — Mon, 19 Aug 2024 20:03:12 GMT

Thank you very much for your reply!

I am already working on a custom board. Could you take a look at my custom board to verify if I made it correctly?

https://github.com/sluissantos/lte_4_click

My board schematic:
https://download.mikroe.com/documents/add-on-boards/click/lte_lot_4_click/LTE_IoT_4_click_v101_Schematic.pdf

When I used that custom board, the output and errors were the same as when I tried with the nrf9160dk_nrf9160ns.

at_client with custom board nrf9160_ns (testing with NB-IOT SYSTEMMODE=0,1,0,0)

All pins have been configured as non-secure
[Sec Thread] Secure image initializing!
Booting TF-M v2.0.0
*** 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\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CGMR\r\n" ----
mfw_nrf9160_1.3.5
OK
---- Sent utf8 encoded message: "AT+CFUN=4\r\n" ----
OK
---- Sent utf8 encoded message: "AT%XSYSTEMMODE=0,1,0,0\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CIND=1,0,1\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CFUN=1\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CGDCONT=1,\"IP\",\"smart.m2m.vivo.com.br\"\r\n" ----
OK
---- Sent utf8 encoded message: "AT+COPS=4\r\n" ----
ERROR
---- Sent utf8 encoded message: "AT+COPS=0\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CEREG=2\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CIMI\r\n" ----
724238041443476
OK
---- Sent utf8 encoded message: "AT+CGATT?\r\n" ----
+CGATT: 0
OK
---- Sent utf8 encoded message: "AT+CEREG=2\r\n" ----
OK
---- Sent utf8 encoded message: "AT+CESQ\r\n" ----
+CESQ: 99,99,255,255,31,64
OK
---- Sent utf8 encoded message: "AT+CSQ\r\n" ----
+CSQ: 99,99
OK
+CEREG: 2,"A8AD","0318182D",9
+CEREG: 2

at_client with custom board nrf9160_ns (testing with LTE-M SYSTEMMODE=1,0,0,0)

Can you tell me if my sequence of AT commands is correct?

This firmware version appears after I build the standard at_client sample. Can you tell me how I can update a custom firmware to version 1.3.6?

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

Achim Kraus — Fri, 16 Aug 2024 11:43:08 GMT

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.

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

Elfving — Fri, 16 Aug 2024 09:27:36 GMT

Hello,

To start off, even though it doesn't immediately seem to be the issue here, it would be the best to build what you are running for the appropriate board. Right now you are flashing something built for the DK. Do you have a board file, or any other instructions that you have gotten along with the Mikroe board?

I also found this previous case here that might be interesting to you.

Regards,

Elfving