Lte Link monitor timed out

upswing

I get timed out errors when using the LTE link monitor on one of my boards

pressing the button AT+CFUN = 1 gives me a timed out response.

The board is recognized on COM4. I have ensured that Flow Control is turned off, and Auto device/port filter is also unchecked. Also Automatic requests is turned on.

Here is a copy of the log

2021-04-12T15:36:28.533Z INFO Application data folder: C:\Users\PC\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2021-04-12T15:36:28.640Z DEBUG App pc-nrfconnect-linkmonitor v1.1.10 official
2021-04-12T15:36:28.640Z DEBUG App path: C:\Users\PC\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2021-04-12T15:36:28.640Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.6.0)
2021-04-12T15:36:28.641Z DEBUG nRFConnect path: C:\Users\PC\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-04-12T15:36:28.641Z DEBUG HomeDir: C:\Users\PC
2021-04-12T15:36:28.641Z DEBUG TmpDir: C:\Users\PC\AppData\Local\Temp
2021-04-12T15:39:10.091Z INFO Modem port is opened
2021-04-12T15:39:10.102Z DEBUG modem >> AT+CFUN?
2021-04-12T15:39:57.886Z DEBUG modem >> AT+CFUN=1
2021-04-12T15:39:58.900Z ERROR Error: 'AT+CFUN=1
' timed out
2021-04-12T15:40:05.590Z DEBUG modem >> AT+CFUN?
2021-04-12T15:40:06.604Z ERROR Error: 'AT+CFUN?
' timed out
2021-04-12T16:11:41.820Z INFO Modem port is opened
2021-04-12T16:11:41.823Z DEBUG modem >> AT+CFUN?
2021-04-12T16:11:47.263Z DEBUG modem >> AT+CFUN=1
2021-04-12T16:11:48.269Z ERROR Error: 'AT+CFUN=1
' timed out

My other board version 2 operates as expected with the LTE link monitor. What can be the problem with my other board?

jaredwolff

upswing can you connect using LTE link monitor and hit the reset button? It should display some text during the boot process. As long as the factory test firmware is installed it should be spitting out accelerometer readings every second or so.

2021-04-12T23:25:01.879Z DEBUG modem << {ù«ûy£oo¹«ëYééa«kékõszóo«»k³óó³=óã{9kiûõËa£ë{jëoó¡ak©o©+)©o©okëû©oaáûoi©s¡¹ié{©¹iéc!©{)é¡s)©o©?k©o¡¹ié{¡?cãó©»)éùc)©o«éié¡k)éoié{©kiëû¡ái©ooiés©oiéû©oaëû©k)©o£¡ié{©?c©o©;ké{ë}}ko-ëiùáããa/ok«yû«
2021-04-12T23:25:01.882Z DEBUG modem << [00:00:00.202,636] [0m<inf> rtc: PCF85063A is initialized![0m
2021-04-12T23:25:01.921Z DEBUG modem << [00:00:00.211,883] [0m<inf> lis2dh: int1 on pin=29[0m
2021-04-12T23:25:01.923Z DEBUG modem << [00:00:00.217,010] [0m<inf> lis2dh: bus=I2C_1 fs=2, odr=0x1 lp_en=0x0 scale=9576[0m
2021-04-12T23:25:01.925Z DEBUG modem << *** Booting Zephyr OS build v2.4.0-ncs2  ***
2021-04-12T23:25:01.926Z DEBUG modem << [00:00:00.238,098] [0m<inf> app: Start of Pyrinas Hub example![0m
2021-04-12T23:25:01.928Z DEBUG modem << [00:00:00.244,262] [0m<inf> app: device is 0x20020350, name is PCF85063A[0m
2021-04-12T23:25:01.936Z DEBUG modem << [00:00:00.252,746] [0m<inf> rtc: mode 0x16[0m
2021-04-12T23:25:01.939Z DEBUG modem << [00:00:00.257,751] [0m<inf> app: Area 0 at 0x0 on W25Q32JV for 33554432 bytes[0m
2021-04-12T23:25:01.946Z DEBUG modem << [00:00:00.265,289] [0m<inf> littlefs: LittleFS version 2.2, disk version 2.0[0m
2021-04-12T23:25:01.958Z DEBUG modem << [00:00:00.273,773] [0m<inf> littlefs: FS at W25Q32JV:0x0 is 8192 0x1000-byte blocks with 512 cycle[0m
2021-04-12T23:25:01.963Z DEBUG modem << [00:00:00.283,172] [0m<inf> littlefs: sizes: rd 16 ; pr 16 ; ca 64 ; la 32[0m
2021-04-12T23:25:01.974Z DEBUG modem << [00:00:00.298,065] [0m<inf> littlefs: /lfs mounted[0m
2021-04-12T23:25:01.980Z DEBUG modem << [00:00:00.303,192] [0m<inf> app: /lfs mount: 0[0m
2021-04-12T23:25:01.995Z DEBUG modem << [00:00:00.312,561] [0m<inf> app: /lfs: bsize = 16 ; frsize = 4096 ; blocks = 8192 ; bfree = 8187[0m
2021-04-12T23:25:02.002Z DEBUG modem << [00:00:00.321,868] [0m<inf> app: Set up button at GPIO_0 pin 12[0m
2021-04-12T23:25:02.010Z DEBUG modem << [00:00:00.332,946] [0m<inf> app: Battery: 2524 mV[0m
2021-04-12T23:25:02.022Z DEBUG modem << [00:00:00.339,080] [0m<inf> app: Set up gpio walker at GPIO_0 pin 24[0m
2021-04-12T23:25:02.025Z DEBUG modem << [00:00:00.344,116] [0m<inf> app: Accel reading: #1 @ 344 ms[0m
2021-04-12T23:25:03.020Z DEBUG modem << [00:00:01.341,033] [0m<inf> app: Accel reading: #2 @ 1341 ms[0m
2021-04-12T23:25:04.016Z DEBUG modem << [00:00:02.337,951] [0m<inf> app: Accel reading: #3 @ 2337 ms[0m
2021-04-12T23:25:05.014Z DEBUG modem << [00:00:03.334,899] [0m<inf> app: Accel reading: #4 @ 3334 ms[0m
2021-04-12T23:25:06.010Z DEBUG modem << [00:00:04.331,848] [0m<inf> app: Accel reading: #5 @ 4331 ms[0m
2021-04-12T23:25:07.007Z DEBUG modem << [00:00:05.328,979] [0m<inf> app: Accel reading: #6 @ 5328 ms[0m
2021-04-12T23:25:08.004Z DEBUG modem << [00:00:06.325,744] [0m<inf> app: Accel reading: #7 @ 6325 ms[0m
2021-04-12T23:25:09.001Z DEBUG modem << [00:00:07.322,753] [0m<inf> app: Accel reading: #8 @ 7322 ms[0m
2021-04-12T23:25:09.998Z DEBUG modem << [00:00:08.319,671] [0m<inf> app: Accel reading: #9 @ 8319 ms[0m
2021-04-12T23:25:10.995Z DEBUG modem << [00:00:09.316,680] [0m<inf> app: Accel reading: #10 @ 9316 ms[0m
2021-04-12T23:25:11.992Z DEBUG modem << [00:00:10.313,598] [0m<inf> app: Accel reading: #11 @ 10313 ms[0m
2021-04-12T23:25:12.989Z DEBUG modem << [00:00:11.310,516] [0m<inf> app: Accel reading: #12 @ 11310 ms[0m
2021-04-12T23:25:13.986Z DEBUG modem << [00:00:12.307,434] [0m<inf> app: Accel reading: #13 @ 12307 ms[0m
2021-04-12T23:25:14.986Z DEBUG modem << [00:00:13.304,443] [0m<inf> app: Accel reading: #14 @ 13304 ms[0m
2021-04-12T23:25:15.980Z DEBUG modem << [00:00:14.301,544] [0m<inf> app: Accel reading: #15 @ 14301 ms[0m
2021-04-12T23:25:16.977Z DEBUG modem << [00:00:15.298,522] [0m<inf> app: Accel reading: #16 @ 15298 ms[0m
2021-04-12T23:25:17.974Z DEBUG modem << [00:00:16.295,562] [0m<inf> app: Accel reading: #17 @ 16295 ms[0m
2021-04-12T23:25:18.971Z DEBUG modem << [00:00:17.292,572] [0m<inf> app: Accel reading: #18 @ 17292 ms[0m

The blue LED should be blinking as well.

GerryB

jaredwolff I am also getting the same problem with LTE Link Monitor. AT+CFUN? just times out. I reset the modem and see all the text right up to “*** Booting Zephyr OS build v2.4.99-ncs1 ***The AT host sample started” then nothing seems to do anything - this is with the at_client firmware

jaredwolff

GerryB Did you make any modifications to the example? What version of NCS did you install? What OS are you on?

GerryB

jaredwolff Im using Windows 10 OS. NCS is NRF Connect 3.7.0 and SDK 1.5.0. I didnt make any mods at all to the AT_CLIENT. I read a few things in other forums and it doesnt look good - a guy named Olvynd was stumped in the other forums and the users berated the IDE after there were no fixes

jaredwolff

GerryB hmm you were able to load the example using newtmgr right? Make sure that you don’t have any other open serial connections to the device.

GerryB

I dont think Im using newtmgr - Im in the IDE and it’s uploading firmware that way. Isnt newtmgr a command line tool?

jaredwolff

GerryB I dont think Im using newtmgr - Im in the IDE and it’s uploading firmware that way. Isnt newtmgr a command line tool?

Ahh right, you’re using a Tag connect to program it that way?

When you’re building you’re building from the nrf/samples/nrf9160/at_client/ folder with west build -b circuitdojo_feather_nrf9160ns?

GerryB

I’m essentially following this tutorial verbatim and I get all the way to the 11:30 mark and then no response from an AT command input: https://www.youtube.com/watch?v=KSivO9Cf1TE

GerryB

Yes Im using a Jlink segger. I tried it last week by uploading through the USB-C port using command lines including newtmgr but I really want to follow this tutorial. And yes to your second question

jaredwolff

GerryB got it. Looks like potentially the RX pin on the USB-to-UART chips is not connected thus why you can receive from the PC side but not send out. I would reach out to Sparkfun and get a replacement. Or if you got it through DK I would go directly to them.

GerryB

I thought it might be a hardware thing too. I soldered on some wires to see if the separate RX and TX holes would work with an FTDI at 115200 baud 1 stop no parity but I got nothing at all even in the receive on reset

GerryB

I guess I should have read the original poster’s message on this thread - I turned off “flow control” on the right side panel of the screen and now I am getting responses to the AT commands. So it finally works

jaredwolff

GerryB that would do it! Glad you figured it out.