Lte Link monitor timed out

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

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

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

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.

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

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 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?

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

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.

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 that would do it! Glad you figured it out.