AT Commands

RE: AT Commands

John — Mon, 23 Mar 2020 19:57:11 GMT

Thank you so much for your assistance Simon. That works.

RE: AT Commands

Simon — Mon, 23 Mar 2020 12:54:04 GMT

I am able to use Termite with the AT Client example without any problems. Regarding Putty, check out this ticket, which proposes a solution that might solve your problem.

Best regards,

Simon

RE: AT Commands

John — Fri, 20 Mar 2020 18:48:15 GMT

Simon that would be fantastic if you were able to find out what's wrong with Putty or something else I could use. I've found exactly the same thing as you. I can use Link monitor...but not with our own board which means that we are forced to use Putty or anything else that you may recommend

RE: AT Commands

Simon — Fri, 20 Mar 2020 13:00:08 GMT

I tested the AT Client sample with NCS v1.2.0 and Putty, but like you, I was not able to input commands. However, I followed the steps under AT Client → Building and running, which used the LTE Link Monitor, and was able to send commands and run the sample successfully.

Could you check if you are able to send commands through the LTE Link Monitor?

Do you want me to look into the issues regarding Putty?

Best regards,

Simon

RE: AT Commands

John — Tue, 17 Mar 2020 18:54:06 GMT

Simon, I must add that it's seems to be many sample applications including our own, it's not just the AT sample.I'm using putty to connect to our device.

I would be grateful if you would confirm that you are seeing the same thing please.

RE: AT Commands

Simon — Mon, 16 Mar 2020 14:02:30 GMT

Could you try to debug the AT Command sample and figure out where the error happens, inspect the library ncs\nrf\lib\at_host\at_host.c when sending AT commands to the nRF9160. The received messages are handled by isr()-->uart_rx_handler(), before getting sent to the modem through cmd_send(). Check if these function runs and locate exactly what the issue is.

Best regards,

Simon