nRF91 - thingy91_at_client_2020-04-29_bc7ade8b - is it possible to send and receive data with that client?

[Achim Kraus]

Is it possible to send and receive data with the thingy91_at_client_2020-04-29_bc7ade8b?

I found, that this is not supported by AT commands, instead socket libraries for zephyr are used. 

Is there a function in that client, which maps UDP traffic to the USB interface?

[Didrik Rokhaug]

Hi.

No, the at_client cannot be used to send data.

However, we also have the serial_lte_modem sample, which extends the functionality of the AT client to also include commands for socket operations.

You can find the documentation for that sample here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.2.0/nrf/samples/nrf9160/serial_lte_modem/README.html

I have also attached a compiled version of the sample. Note that it must be flashed with an external programmer.

Best regards,

Didrik

slm.hex

[Achim Kraus]

Thanks!

I'm using a Thingy:91 not a nRF9160 DK board (PCA10090).

Using the "slm.hex" seems not to work for a Thingy:91. It doesn't reply to the AT commands, which has worked so far.

UDP AT commands

The following proprietary UDP AT commands are used in this sample:

• AT#XSOCKET=<op>[,<type>]

• AT#XSOCKET?

• AT#XUDPSENDTO=<url>,<port>,<data>

• AT#XUDPRECVFROM=<url>,<port>,<length>,<timeout>

Where can I find the details about these AT commands? In the sources?

[Didrik Rokhaug]

How did you flash the hex file to the Thingy?

The hex file works as it should for me when I flash it using the Programmer application in nRF Connect for Desktop, and an nRF91DK as an external programmer for the Thingy.

 

Achim Kraus said:

Where can I find the details about these AT commands? In the sources?

 There are more documentation coming, but for now that is what we have.

But yes, the source code might help in the meantime.

[Achim Kraus]

Thanks! I was using the boot loader (MCU-boot). Using the JTAG works.

[Achim Kraus]

> This sample is an enhancement to the nRF9160: AT Client sample.

Now I get a "OK" for a "AT", and for "AT+CMEE=1", I get "\0x00OK" (binary 0x00 at the head).

After that, it stops to answer. I had to restart the thingy91.

If I don't send that "AT+CMEE=1" and send instead "AT+CFUN=0", I still get "\0x00OK" and it seems not to stop. But the other answers I checked are all starting with a binary 0x00.

Sometimes I read "at_host: Could not send AT command to modem: -8" from the serial.

Is that binary zero intended? For me that doesn't make too much sense.

[Didrik Rokhaug]

I also get the extra 0x00 byte, though it does not seem to cause any problems for me.

What program are you using to communicate with the Thingy?