UDP and SEW MOVI-C
Overview
Section titled “Overview”Exchanges one fixed binary telegram per direction with a PLC, SCADA system or your own tool. The SEW MOVI-C (UDP) catalog row is a preset of this interface.
The telegram flows like this.
Set up and parameters
Section titled “Set up and parameters”| Parameter | Example |
|---|---|
| Local port | 11001 (listens on all network adapters by default) |
| Remote host / port | 127.0.0.1 / 11000 |
| Byte order | little-endian (default) or big-endian |
| Symbol table | C:\Projects\Line1\udp-symbols.csv (optional) |
UDP exchanges one fixed binary telegram per direction. Each signal names its byte offset and type: 0:BOOL (1 byte), 4:INT (32-bit integer) or 8:REAL (32-bit float). The direction comes from the signal type — PLCInput signals form the telegram CONNECT sends every update cycle, PLCOutput signals are read from the telegram it receives. The telegram length is the end of the last field.
A received datagram that is shorter than the configured fields keeps the uncovered values and reports a signal issue instead of being dropped. UDP has no connection: the interface shows Connected once its port is bound, whether or not the partner is sending. With a symbol table (Name;Type;Direction, separator configurable) Browse lists its signals with the offsets already computed.
SEW MOVI-C (UDP)
Section titled “SEW MOVI-C (UDP)”Choose SEW MOVI-C (UDP) in Add Interface for the binary telegram layout used by the Unity SEW simulation. This catalog preset uses the UDP interface (Type: Udp, preset SEW-UDP). New interfaces receive an id such as sew-udp-1, appear as SEW UDP in the CONNECT panel and start disabled. Switch them on with the power icon on their row.
| Parameter | Default |
|---|---|
| Local bind address / port | 0.0.0.0 / 11001 |
| Remote host / port | 127.0.0.1 / 11000 |
| Byte order | little-endian (LittleEndian: true) |
| Update cycle | 20 ms |
While the interface has no signals, Import SEW symbol table… is the main action in its empty state. At any time, open ⋮ → Import SEW symbol table… on the interface card and select a CSV with the header Name;Type;Direction. This action is available on every UDP card, including interfaces created without the preset. The browser reads the file; it does not need to be on the CONNECT computer. Review the signal preview and skipped rows, then import and enable the interface.
Name;Type;DirectionSpeedSetpoint;REAL;PLC_INStartButton;BOOL;PLC_INCurrentSpeed;REAL;PLC_OUTErrorCode;INT;PLC_OUTOffsets follow file order, separately from byte 0 for each direction: PLC_IN is sent to the partner and PLC_OUT is received. The example produces 0:REAL, 4:BOOL in the send telegram and 0:REAL, 4:INT in the receive telegram.
BOOLoccupies 1 byte;INTandREALoccupy 4 bytes, without alignment or padding. Types and directions are case-insensitive.TEXT,STRINGandWSTRING, unknown types or directions, and rows with fewer than three columns are skipped without consuming bytes.- Empty or duplicate names are skipped, but their bytes remain reserved when the type and direction are valid. Following fields keep their offsets.
- Fields ending beyond 65 507 bytes are skipped and reported; their bytes still advance the offset for that direction.
Re-import replaces the interface’s signals after you confirm the number of existing signals being replaced. It keeps ports, host, byte order and update cycle. Skipped rows show their line and reason; a file with no importable signals cannot be imported. A table with only one direction shows that nothing is sent or received in the other direction. Name collisions and signal-limit errors from CONNECT appear in the dialog.
Version compatibility: Release CONNECT before realvirtual. An older CONNECT that supplies a catalog without this preset does not show SEW MOVI-C (UDP) in the list; with the new realvirtual release, you can still add a regular UDP interface and use Import SEW symbol table… on its card.
Create or import signals
Section titled “Create or import signals”- Manually. Name the byte offset and type:
0:BOOL(1 byte),4:INT(32-bit integer),8:REAL(32-bit float). The direction comes from the signal type. - Browse. Only from a file. With a symbol table (a file on the CONNECT machine, set in the interface settings) (
Name;Type;Direction, separator configurable), Browse lists its signals with the offsets already computed. - File import. Import SEW symbol table… in the ⋮ menu of any UDP card (and the main action of an empty SEW card) reads a CSV with the header
Name;Type;Directionin the browser, previews signals and skipped rows, and replaces the interface’s signals after confirmation. - From the model. When the model already has its PLC signals, Addresses → Fill from controller… in the signal-mapping section of the CONNECT panel previews matches by exact name against what Browse finds in the symbol table and then writes the addresses. Addresses → Import address table… takes a CSV or TSV with
name;address[;dataType[;topic]]rows. New signals take direction and type from the same-named model signal; signals that already exist keep their configured type. See Configuring interfaces.
How direction, data types and write access are decided is explained in Common concepts and Configuring interfaces.
See also
Section titled “See also”- CODESYS NVL for Network Variable Lists
- Common concepts — text signals, direction, write access, tracking signals
- Configuring interfaces — adding signals, direction and write access
- All supported interfaces
- Troubleshooting — connection and signal problems