Sending UDP using the Serial LTE Modem application - AT sequence

RE: Sending UDP using the Serial LTE Modem application - AT sequence

Bard — Fri, 02 Oct 2020 08:43:15 GMT

The following sequence now works fine:

at#xudpcli=1,"xx.xxx.xx.xxx",xxxx
at#xudpsend=1,"testdata"
at#xudpcli=0

Thank you

RE: Sending UDP using the Serial LTE Modem application - AT sequence

Martin Lesund — Wed, 30 Sep 2020 12:09:04 GMT

Please enable UDP proxy:

CONFIG_SLM_UDP_PROXY=y

and connect using:

AT#XUDPCLI=<op>[,<url>,<port>[,<sec_tag>]
AT#XUDPSEND=<datatype>,<data>

recv is handled automatically when using proxy.

"Proxy" not related to a proxy server as commonly known.
It is named a proxy as it stands between the TCP interface of the modem and the application itself.
The modem TCP/UDP layer supports full-duplex but the AT commands are blocking, 
so we need this added interface to remove the blocking behavior.

RE: Sending UDP using the Serial LTE Modem application - AT sequence

Bard — Tue, 29 Sep 2020 13:05:03 GMT

Using the draft documentation, I ended up with this sequence:

at#xsocket=1,2,0    // must have the last zero
at#xsendto="xx.xxx.xx.xxx",xxxx,"Test UDP"

// both below works ok
at#xrecvfrom="xx.xxx.xx.xxx",xxxx
at#xrecvfrom="xx.xxx.xx.xxx",xxxx,100,1

at#xsocket=0

But at#xrecvfrom hangs if there is no data from the network. Is there a way to test before fetch, or a timeout parameter?

RE: Sending UDP using the Serial LTE Modem application - AT sequence

Martin Lesund — Tue, 29 Sep 2020 09:32:51 GMT

Hi Bard,

There is now a draft pull request for the SLM documentation up.

This version will be reviewed and most likely some changes will be added before its merged with NCS master.

RE: Sending UDP using the Serial LTE Modem application - AT sequence

Martin Lesund — Fri, 25 Sep 2020 11:44:59 GMT

Hi Bard,
We are working on improving the documentation to explain this better.

#XSENDTO	UDP send data	Send data via UDP channel
		#XSENDTO=<url>,<port>,<datatype>,<data> Response: #XSENDTO: <size>

	<url> values	String type, hostname or IP address Max 128 bytes. In case of IP address, IPv4 only, not support IPv6
	<port> values	Integer, UDP service port
	<datatype> values	0 - hexidecimal string format, e.g. "DEADBEEF" for 0xDEADBEEF 1 - plain text (default value) 2 - Json 3 - HTML 4 - OMA TLV
	<data> values	String type, arbitary data NOTE1 max NET_IPV4_MTU (576) bytes NOTE2 no NULL char in the middle
	<size> values	Integer type, actual number of bytes sent

	example	AT#XSENDTO="test.server.com",1234,"Test UDP" #XSENDTO: 8 OK

#XRECVFROM	UDP receive data	Receive data via UDP channel
		#XRECVFROM=<url>,<port>[,<size>] NOTE receive max NET_IPV4_MTU(576) bytes Response: <data> #XRECVFROM: <datatype>, <size>

	<url> values	String type, hostname or IP address Max 128 bytes. In case of IP address, IPv4 only, not support IPv6
	<port> values	Integer, UDP service port
	<size> values	Requested number of bytes in command, , NET_IPV4_MTU if not specified Actual number of bytes received in response
	<datatype> values	See #XSEND command

	example	AT#UDPRECVFROM="test.server.com",1234 Test OK #XRECVFROM: 1, 7 OK

RE: Sending UDP using the Serial LTE Modem application - AT sequence

Bard — Fri, 25 Sep 2020 06:37:41 GMT

Thank you, Martin. But is there some documentation on the usage of these commands? What is <datatype> and <op>? And how is addressing implemented? - the old AT#XUDPSENDTO had both IP address and Port in the call...

RE: Sending UDP using the Serial LTE Modem application - AT sequence

Martin Lesund — Thu, 24 Sep 2020 13:25:22 GMT

Hi Bard,

You can use the following commands:

at#xsocket=1,2

AT#XSENDTO=<url>,<port>,<datatype>,<data>

AT#XRECVFROM[=<length>]

AT#XSOCKET=0