UDP_Receive block
Short summary
Name |
|
→POU type |
|
Category |
more system blocks, network blocks, block with internal error diagnostic |
Graphical interface |
|
Available since |
|
Functionality
The block receives a →UDP packet.
Inputs, outputs
|
Identifier |
Description |
|
---|---|---|---|
Inputs: |
|
|
UDP handle |
|
|
additional flags for receiving |
|
In-outs |
|
Further restriction: In the case of function blocks, no function blocks with a →generic data type are allowed. As a result of this restriction, you cannot use the following blocks as input of the current block: LIMITER_O, LIMITER_U, FORCEMRK, MAX_HOLD, MIN_HOLD, and →vendor-function blocks that have been declared with a generic data type. |
content of received UDP packet |
Outputs: |
|
|
source address of the received UDP packet (in network byte order)
Use the |
|
|
source port of the received UDP packet (in host byte order) |
|
|
|
length of the received UDP packet |
|
|
|
status of the UDP operation:
|
Input EN
and output ENO
are available when →calling the block. See "Execution control: EN, ENO" for information on input EN
and output ENO
.
See:
-
"Blocks for safe logic" whether this block is supported for developing safety-relevant applications.
-
"Highlighting safe logic in the FBD-editor" for the effects when using the block as a block for safe logic.
Internal error diagnostic for block
The block checks the following error cases:
-
The flag is invalid.
-
The handle is invalid.
-
Data cannot be received.
In such an error case, the output ENO
of the block is set to value FALSE
(or an equivalent). Moreover, the output rc
returns the appropriate code (see the above table).
Example for usage within ST-editor
See "UDP_Open block".