On nRF9160DK, I have installed the "Serial LTE Modem" application. DK is connected via USB to a Windows PC. It works just fine with nRF Connect for Desktop apps (LTE Link Monitor and Serial Terminal), and I can send AT commands and receive responses, both Modem-specific AT commands and Proprietary AT commands.
However, when I try to send AT via Putty terminal, I don't get any response. The same is true when I try to send AT commands with Python script (serial module) on Windows or Raspberry Pi 4B (nrfDK is also connected via USB).
The problem occurs on the Serial LTE Modem application. I can send AT with the terminal using the "Asset Tracker v2" or "AT Client" applications. For every application, I use the same Putty settings.
I am counting on the "Serial LTE Modem" application because it is the only available app that enables sending proprietary commands for HTTP, SMS (unfortunately, IBasis card turns it off), ICMP, and MQTT(unfortunately, these don't work either; I get permanently "Error").
I tried to solve it on my own, but I've read that it requires modifying source files like "Kconfig", "prj.conf", "mcuboot.conf". I did modify "prj.conf" like this:
# Segger RTT
CONFIG_USE_SEGGER_RTT=n
# Where console messages (printk) are output.
# By itself, SLM does not output any.
CONFIG_RTT_CONSOLE=n
CONFIG_UART_CONSOLE=y
# Where SLM logs are output.
CONFIG_LOG_BACKEND_RTT=n
CONFIG_LOG_BACKEND_UART=y
But it didn't help after building and flashing the app in the DK.
I am using the latest firmware (v1.3.5), apps(v4.3.0) and nRF Connect SDK (v2.5.0).
So, what should I do to be able to send and receive AT with the "Serial LTE Modem" application via the terminal?
Really appreciate any help!
Peter
nrf connect for desktop putty
