reading AT responses from the modem

RE: reading AT responses from the modem

miked531 — Sat, 21 Sep 2019 03:46:26 GMT

I found the answer I was looking for. the socket is a datagram. See https://devzone.nordicsemi.com/f/nordic-q-a/44057/bsdlib-at-socket-api

RE: reading AT responses from the modem

Didrik Rokhaug — Fri, 20 Sep 2019 09:14:41 GMT

Hi.

Two things I thought I should make you aware of:

1. There is a new modem firmware version (v1.0.1), which you should upgrade to.

2. There is an interesting conversation happening here: https://github.com/NordicPlayground/fw-nrfconnect-nrf/pull/1143 that is somewhat related to your case.

Best regards,

Didrik

RE: reading AT responses from the modem

miked531 — Wed, 11 Sep 2019 03:40:08 GMT

Thanks for the command suggestions. For the time being I will keep the max size small as I have no need for the commands listed above.

I am not using the AT driver, but similar code to what the driver does and the same resolution applies, to set a max response size. I added a call to recv(..., MSG_PEEK) which works nicely to let me know if the response would exceed the buffer size.

RE: reading AT responses from the modem

Didrik Rokhaug — Tue, 10 Sep 2019 14:32:03 GMT

Hi.

Regarding other AT commands with long responses, I only know of %CMNG. Looking at the documentation, I also expect it might be necessary with %XPMNG, %XBANDLOCK, %XMIPIRFFEDEV, %XMONITOR, and +CMT notifications. However, I have not confirmed the max length of those responses.

As to how you can receive long responses, you can do this by setting CONFIG_AT_CMD_RESPONSE_MAX_LEN to a sufficiently large number in your prj.conf.

Best regards,

Didrik