This is machine translation

Translated by Microsoft
Mouseover text to see original. Click the button below to return to the English verison of the page.

Note: This page has been translated by MathWorks. Please click here
To view all translated materals including this page, select Japan from the country navigator on the bottom of this page.

UDP Receive

Receive uint8 vector as UDP message





The UDP Receive block receives UDP packets from an IP network port and saves them to its buffer. With each sample, the block outputs the contents of a single UDP packet as a data vector. The local IP port number on which the block receives the UDP packets is tunable in the C/C++ generated code.

The generated code for this block relies on prebuilt .dll files. You can run this code outside the MATLAB® environment, or redeploy it, but you must account for these extra .dll files when doing so. The packNGo function creates a single zip file containing all of the pieces required to run or rebuild this code. For more details, see How To Run a Generated Executable Outside MATLAB.


Local IP port

Specify the IP port number on which to receive UDP packets. This parameter is tunable in the C/C++ generated code but not tunable during simulation. The default is 25000. The value can be in the range [1 65535].

    Note:   On Linux®, to set the IP port number below 1024, run MATLAB with root privileges. For example, at the Linux command line, enter:

    sudo matlab

Remote IP address ('' to accept all)

Specify the IP address from which to accept packets. Entering a specific IP address blocks UDP packets from other addresses. To accept packets from any IP address, enter ''. This value defaults to ''.

Receive buffer size (bytes)

Make the receive buffer large enough to avoid data loss caused by buffer overflows. This value defaults to 8192.

Maximum length for Message

Specify the maximum length, in vector elements, of the data output vector. Set this parameter to a value equal or greater than the data size of a UDP packet. The system truncates data that exceeds this length. This value defaults to 255.

If you disable Output variable-size signal, the block outputs a fixed-length output the same length as the Maximum length for Message.

Data type for Message

Set the data type of the vector elements in the Message output. Match the data type with the data input used to create the UDP packets. This option defaults to uint8.

Output variable-size signal

If your model supports signals of varying length, enable the Output variable-size signal parameter. This checkbox defaults to selected (enabled). In that case:

  • The output vector varies in length, depending on the amount of data in the UDP packet.

  • The block emits the data vector from a single unlabeled output.

If your model does not support signals of varying length, disable the Output variable-size signal parameter. In that case:

  • The block emits a fixed-length output the same length as the Maximum length for Message.

  • If the UDP packet contains less data than the fixed-length output, the difference contains invalid data.

  • The block emits the data vector from the Message output.

  • The block emits the length of the valid data from the Length output.

  • The block dialog box displays the Data type for Length parameter.

In both cases, the block truncates data that exceeds the Maximum length for Message.

Data type for Length

Set the data type of the Length output. This option defaults to double.

Blocking time (seconds)

For each sample, wait this length of time for a UDP packet before returning control to the scheduler. This value defaults to inf, which indicates to wait indefinitely.

    Note:   This parameter appears only in the Embedded Coder® UDP Receive block.

Sample time (seconds)

Specify how often the scheduler runs this block. Enter a value greater than zero. In real-time operation, setting this option to a large value reduces the likelihood of dropped UDP messages. This value defaults to a sample time of 0.01 s.

Extended Capabilities

See Also

System Objects


Introduced in R2010a

Was this topic helpful?