7 - 8 7 - 8
MELSEC-F
7 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE
CONTROL METHOD)
7.4 Data Format
When communicating between the Ethernet module and an external device, the data
format explained below is used.
The communication data consists of a "header" and "application data" as shown below.
Header
Application data
(1) Header
The header for TCP/IP or UDP/IP is used. In case of the Ethernet module, the
Ethernet module adds and deletes the header. Thus, the user does not need to
set it.
(Details of the size of the header section)
1) In case of TCP/IP
Ethernet
14 bytes
IP
20 bytes
TCP
20 bytes
2) In case of UDP/IP
Ethernet
14 bytes
IP
20 bytes
UDP
8 bytes
(2) Application Data
The data code in the application data is expressed in binary code.
Communication is performed using binary code, regardless of the set
communication data (see Section 4.6).
Text (command)
Maximum of 2064 bytes
NOTE
The subheader and data length that are added for communications using the fixed
buffers in the procedure exist control method are not present for communications in
the no procedure control method. All data is treated as valid text.
Содержание FX3U-ENET
Страница 1: ...USER S MANUAL FX3U ENET ...
Страница 2: ......
Страница 159: ...8 6 8 6 MELSEC F 8 COMMUNICATION USING MC PROTOCOL MEMO ...
Страница 295: ...App 25 App 25 MELSEC F APPENDIX MEMO ...
Страница 297: ......