TAMAGAWA TS2651N111E78 TS2651N111E78 TS2651N111E78 TS2651N111E78 TS2651N111E78

TS2651N111E78

Guang Zhou Lai Jie Electric Co.,LTD

Please contact with “Tommy” for the price

TS5205N454

TS2651N11E78

TS2651N141E78

TS2651N1E78

TS2651N131E78

TS3103N40

TS3653N2E5

TS3653N3E8

TS3684N1E3

TS3684N2E6

TS3684N3E8

TS3667N3E8

TS3624N2E3

TS3624N2E4

TS3624N3E6

TS3630N1E1

TS3630N2E3

TS3630N1306

TS3630N1303E9

TS3630N1214E3

TS5013N60

TS5013N61

TS5016N60

TS5013N63

TS5013N64

TS5016N61

TS5013N66

TS5016N63

TS5016N64

TS5017N60

TS5019N60

User Datagram Protocol TUSEND and TURCV Assigns port numbers to
the Local (active) and

PROFINET RT CPU-to-PROFINET
IO device
communication
Data transmission and
reception with specified
length
Built-in Built-in Typically, TCP and ISO-on-TCP receive data packets of a specified length, ranging from 1 to
8192 bytes. However, the TRCV_C and TRCV communication instructions also provide an
"ad hoc" communications mode that can receive data packets of a variable length from 1 to
1472 bytes.
Note
If you store the data in an "optimized" DB (symbolic only), you can receive data only in
arrays of Byte, Char, USInt, and SInt data types.
To configure the TRCV_C or TRCV instruction for ad hoc mode, set the LEN parameter to
65535 (0xFFFF).
If you do not call the TRCV_C or TRCV instruction in ad hoc mode frequently, you could
receive more than one packet in one call. For example: If you were to receive five 100-byte
packets with one call, TCP would deliver these five packets as one 500-byte packet, while
ISO-on-TCP would restructure the packets into five 100-byte packets.
10.2.2.4 TCP and ISO on TCP
Transport Control Protocol (TCP) is a standard protocol described by RFC 793:
Transmission Control Protocol. The primary purpose of TCP is to provide reliable, secure
connection service between pairs of processes. This protocol has the following features:
● An efficient communications protocol since it is closely tied to the hardware
● Suitable for medium-sized to large data amounts (up to 8192 bytes)
● Provides considerably more facilities for applications, notably error recovery, flow control,
and reliability A connection-oriented protocol
● Can be used very flexibly with third-party systems which exclusively support TCP
● Routing-capable
● Only static data lengths are applicable.
● Messages are acknowledged.

Applications are addressed using port numbers.
● Most of the user application protocols, such as TELNET and FTP, use TCP.
● Programming effort is required for data management due to the SEND / RECEIVE
programming interface.
International Standards Organization (ISO) on Transport Control Protocol (TCP) (RFC 1006)
(ISO on TCP) is a mechanism that enables ISO applications to be ported to the TCP/IP
network. This protocol has the following features:
● An efficient communications protocol closely tied to the hardware
● Suitable for medium-sized to large data amounts (up to 8192 bytes)
● In contrast to TCP, the messages feature an end-of-data identification and are messageoriented.

● Routing-capable; can be used in WAN
● Dynamic data lengths are possible.
● Programming effort is required for data management due to the SEND / RECEIVE
programming interface.
Using Transport Service Access Points (TSAPs), TCP protocol allows multiple connections
to a single IP address (up to 64K connections). With RFC 1006, TSAPs uniquely identify
these communication end point connections to an IP address.
TSEND_C and TRCV_C
The TSEND_C instruction combines the functions of the TCON, TDISCON and TSEND
instructions. The TRCV_C instruction combines the functions of the TCON, TDISCON, and
TRCV instructions. (Refer to "TCON, TDISCON, TSEND, AND TRCV (Page 439)" for more
information on these instructions.) The minimum size of data that you can transmit (TSEND_C) or receive (TRCV_C) is one
byte; the maximum size is 8192 bytes. TSEND_C does not support the transmission of data
from boolean locations, and TRCV_C will not receive data into boolean locations. For
information transferring data with these instructions, see the section on data consistency
(Page 153).
Note
Initializing the communication parameters
After you insert the TSEND_C or TRCV_C instruction, use the "Properties" of the instruction
(Page 127) to configure the communication parameters. As you enter the parameters for the
communication partners in the inspector window, STEP 7 enters the corresponding data in
the DB for the instruction.
If you want to use a multi-instance DB, you must manually configure the DB on both CPUs. TSEND_C establishes a TCP or ISO on TCP
communication connection to a partner station,
sends data, and can terminate the connection.
After the connection is set up and established, it
is automatically maintained and monitored by
the CPU. TRCV_C establishes a TCP or ISO on TCP
communication connection to a partner CPU,
receives data, and can terminate the connection.
After the connection is set up and established, it
is automatically maintained and monitored by
the CPUControl parameter REQ starts the send job with the connection
described in CONNECT on a rising edge.