Ublox SARA-R4 Series User Manual (English)

To Next Page

To Previous Page

SARA-R4/N4 series-AT Commands Manual

UBX-17003787 - R09



18Internet protocol transport layer

Page 193 of 307

reading, either when new data arrives or after a partial read by the user for the socket. This command can also

return the total amount of unread data.

This command can be applied to UDP sockets only, and it can be used to read data after both +UUSORD and

+UUSORF unsolicited indication.

If the HEX mode is enabled (see +UDCONF=1) the received data will be displayed using an hexadecimal

string.

18.13.2Syntax

Type Syntax Response Example

Set AT+USORF=<socket>,<length> +USORF: <socket>,<remote_ip_

addr>,<remote_port>,<length>,

<data in the ASCII [0x00,0xFF]

range>

AT+USORF=3,16

+USORF: 3,"151.9.34.66",2222,16,"16

bytes of data"

Test AT+USORF=? +USORF: (list of supported

<socket>s),(list of supported

<length>s)

+USORF: (0-6),(0-1024)

URC +UUSORF: <socket>,<length> +UUSORF: 3,16

18.13.3Defined values

Parameter Type Description

<socket> Number Socket identifier. The range goes from 0 to 6

<remote_ip_addr> String Remote host IP address. For IP address format reference see the IP addressing.

<remote_port> Number Remote host port, in range 1-65535

<length> Number Number of data bytes to read, in range 0-1024

<data> String Data bytes to be read

18.13.4Notes

• Each packet received from the network is stored in a separate buffer and the command is capable to read

only a packet (or e portion of it) at time. This means that if <length> is greater than the packet size, the

command will return a maximum amount of data equal to the packet size, also if there are other packets

in the buffer. The remaining data (i.e. the remaining UDP packets) can be read with further reads.

• The returned data may have any kind of ASCII character in the range [0x00,0xFF] i.e. control characters

too. The starting quotation marks shall not be taken into account like data; the first byte of data starts

after the first quotation marks. Then the other characters are provided for a <length> amount. At the

end of the length byte stream, another quotation marks followed by <CR><LF> are provided for user

convenience and visualization purposes. An application should rely on the <length> info to count the

received number of characters (after the starting quotation marks) especially if any protocol control

characters are expected.

• If an application deals with letter and number characters only i.e. all of the expected characters are

outside the [0x00, 0x1F] range and are not quotation marks, the AT+USORD response quotation marks

can be assumed to identify the start and the end of the received data packet, anyway the <length> field

usage to identify the valid data stream is recommended.

• When <length>= 0, the command returns the total amount of data present in the network buffer.

Example: 23 unread bytes in the socket

AT+USORF=3,0

+USORF: 3,23

• If the HEX mode is enabled, the length of <data> will be 2 times <length>.

Other manuals for Ublox SARA-R4 Series

System Integration Manual157 pages

Need help?

Do you have a question about the Ublox SARA-R4 Series and is the answer not in the manual?

Ublox SARA-R4 Series Specifications

General

Operating Temperature	-40°C to +85°C
Category	Cellular Module
Technology	LTE Cat M1, LTE Cat NB1
Frequency Bands	B1, B2, B3, B4, B5, B8, B12, B13, B18, B19, B20, B25, B26, B28, B39
Interfaces	UART, USB, I2C, GPIO
Protocols	TCP/IP, UDP, HTTP, HTTPS, MQTT, LWM2M
Security	TLS/SSL, DTLS, Secure Boot
Certifications	GCF, PTCRB, CE, FCC, IC