UDP
Last updated
Last updated
This interface is currently in Beta
The UDP Interface provides high-performance signal communication with minimal cycle times, offering swift connectivity between applications and realvirtual.io. Unlike the WebSocket Realtime Interface, the UDP Interface does not transmit structural information within the telegram, nor does it support signal list imports.
The UDP interface operates using separate sending and listening ports. It's crucial to assign distinct ports for sending and listening purposes. All PLCInput signals are transmitted to the remote partner, while all PLCOutput signals are received from the remote partner.
When using the UDP Interface, all signals are transmitted and received in the form of a byte array, ensuring the most efficient packet size. Each signal must define a value in its Name property to indicate its position in the byte array. Since there is a single sending and receiving message, the positions of inputs and outputs may overlap. Signal data sizes must adhere to the following guidelines:
Boolean: Always occupies the first bit in one full byte.
Integer: Occupies 4 bytes.
Float: Occupies 4 bytes.
