6 F 3 B 0 3 6 2
5.4 PC Link Protocol Transmission (Data read)
The T series PC link protocol allows a T2N on the network to read register data from another T2N or T3H port's registers into its own registers.
As is the case with the computer link protocol, the PC link protocol uses UDP/IP as its transmission protocol.
The PC link main port uses a UDP socket for message transmission and transmits to the slave Ethernet Port message transmission UDP socket. The user program that runs on the main port is discussed later.
When this function is used on the PC link slave port, the T2N simply performs the:
∙Parameter setup and
∙Operating mode control (message transmission permission)
that were described in an earlier chapter. There is no need to create any special user programs on the T2N.
Usage Recommendations
1.Since UDP/IP does not provide control functions to guarantee communication reliability, higher level protocols (such as retry) are required.
2.No processing is performed if a PC link protocol transmission message is received at any point other than a message transmission UDP socket.
Register read request (using the RECV instruction)
a.Function
The register data specified by the remote port (T2N/T3H) is read to the specified register on the local port (T2N).
b.Transfer parameters
A | 3100H |
A+1 | CMD = 0021H |
A+2 | WordSize |
A+3 | SRID |
A+4 | SRegNO |
A+5 | DRID |
A+6 | DRegNO |
A+7 | Timecnt |
A+8 | |
A+9 |
|
A+10 |
Module designation
Command number
(1)Transfer register data length: 1 to 485 words
(2)Local port register type code
(3)Local port register number
(4)Remote port register type code
(5)Remote port register number
(6)Timer count
Remote port IP address (The input format is the same as that for parameter setup requests.)
Remote port message transmission UDP port number
⎯ 61 ⎯
