Skip to Content

Wiki source code of 14 Ethernet communication

Last modified by Jim on 2023/09/22 15:36
Show last authors
1 = **Ethernet overview** =
2
3 == **{{id name="_Toc3979"/}}{{id name="_Toc14022"/}}{{id name="_Toc10482"/}}{{id name="_Toc7863"/}}IP address** ==
4
5 IP address consists of network address and host address, and distinguished by subnet mask. If programming device (such as PC) use network card to connect to LAN, the programming device and PLC must be in the same subnet. You can specify the subnet of a device by combining an IP address with a subnet mask.
6
7 The network address could be calculated by performing logic and operation between IP address and subnet mask. If the addresses are in the same network, it means that communication is possible.
8
9 (% class="table-bordered" %)
10 |(% rowspan="2" %)**Number**|(% colspan="3" %)**Network device 1**|(% colspan="3" %)**Network device 2**|(% rowspan="2" %)**Network connection**
11 |**IP**|**Subnet mask**|**Network address**|**IP**|**Subnet mask**|**Network address**
12 |1|192.168.0.1|255.255.255.0|192.168.0.0|192.168.0.10|255.255.255.0|192.168.0.0|Yes
13 |2|192.168.0.1|255.255.255.0|192.168.0.0|192.168.1.10|255.255.255.0|192.168.1.0|No
14 |3|192.168.0.1|255.255.255.1|192.168.0.1|192.168.0.10|255.255.255.1|192.168.0.0|No
15
16 == **{{id name="_Toc16835"/}}{{id name="_Toc518"/}}{{id name="_Toc4567"/}}{{id name="_Toc24276"/}}Set PC network address** ==
17
18 (1) Click “Control panel”→”Network and Internet”→”Network and sharing center”.
19
20 (% style="text-align:center" %)
21 [[image:14_html_c2a8809528586e62.png||class="img-thumbnail"]]
22
23 (2) Click “Ethernet”→”Properties”→”Internet protocol version 4”.
24
25 (3) Set the IP address and subnet mask on the same network address as the PLC. The IP address that has been used in LAN could not be set. If the IP of PLC is 192.168.8.8, and the subnet mask is 255.255.255.0. The IP address as shown below could be set to connect PC to PLC.
26
27 (% style="text-align:center" %)
28 [[image:14_html_a9fe3141424b96c7.png||class="img-thumbnail"]]
29
30 == **{{id name="_Toc27521"/}}{{id name="_Toc29278"/}}{{id name="_Toc9496"/}}{{id name="_Toc10920"/}}Test the network connection status** ==
31
32 Test the connection status between PC and PLC by ping command.
33
34 (1) Press “WIN” and “R” keys, and input “cmd”.
35
36 (% style="text-align:center" %)
37 [[image:14_html_dabf04cdadd8a3d8.png||class="img-thumbnail"]]
38
39 (2) If the IP address of PLC is 192.168.8.8.
40
41 1) Input “ping 192.168.8.8 ”, and enter. If it display ”100% loss”, it means that PLC could be connected.
42
43 (% style="text-align:center" %)
44 [[image:14_html_7aa7f1c9b25ffe38.png||class="img-thumbnail"]]
45
46 2) Input “ping 192.168.8.8 ”, and enter. If it display ”0% loss”, it means that it could be connected to PLC.
47
48 (% style="text-align:center" %)
49 [[image:14_html_62b05ca96148a3f1.png||class="img-thumbnail"]]
50
51 3) The command “ping network device IP” could only be use four times. To ping network devices continuously, run “ping network device ip-t” command, it is shown as below.
52
53 (% style="text-align:center" %)
54 [[image:14_html_d69739e24edf0b2d.png||class="img-thumbnail"]]
55
56 == **PLC Editor2 connect to PLC with Ethernet** ==
57
58 (1) Transfer settings →Ethernet configuration → Input IP address.(**✎Note:** The address of NIC must be on the same network segment as that of the PLC.)
59
60 (% style="text-align:center" %)
61 [[image:14_html_144b2bfcd0791114.png||class="img-thumbnail"]]
62
63 (2) Click “Communication test” to comfirm the communication.
64
65 (% style="text-align:center" %)
66 [[image:14_html_d0e31208a663b835.png||class="img-thumbnail"]]
67
68 (3) After successful connection, PLC is able to operate.
69
70 == **PLC Editor2 Ethernet search funtion** ==
71
72 (1) Transfer settings → NIC comfiguration → Device search. (**✎Note:** The address of NIC must be on the same network segment as that of the PLC.)
73
74 (% style="text-align:center" %)
75 [[image:14_html_4d043668ca526831.png||class="img-thumbnail"]]
76
77 (2) The search interface is as below. Click search to display the PLC devices in the LAN, and select the corresponding device and click OK to communicate.
78
79 (% style="text-align:center" %)
80 [[image:14_html_15c7655b852e111.png||class="img-thumbnail"]]
81
82 (3) The IP address of one is filled in automatically.
83
84 (% style="text-align:center" %)
85 [[image:14_html_2d7b6e1b3d27381a.png||class="img-thumbnail"]]
86
87 = {{id name="_Toc15427"/}}{{id name="_Toc12664"/}}{{id name="_Toc24930"/}}{{id name="_Toc1600"/}}**Ethernet configuration** =
88
89 == **Hardware interface** ==
90
91 The LX5V is equipped with standard Ethernet ports (1 channel RJ45 port) and supports Modbus TCP communication protocol.
92
93 //RJ45 specification//
94
95 (% class="table-bordered" %)
96 |=(% scope="row" style="width: 277px;" %)**Contents**|=(% style="width: 797px;" %)**Ethernet interfece**
97 |=(% style="width: 277px;" %)Transmission speed|(% style="width:797px" %)(((
98 10Mbps: 10BASE-T
99
100 100Mbps: 100BASE-TX
101
102 10Mbps/100Mbps self-adaptive
103 )))
104 |=(% style="width: 277px;" %)Modulation|(% style="width:797px" %)Basband
105 |=(% style="width: 277px;" %)Topology|(% style="width:797px" %)Starlike
106 |=(% style="width: 277px;" %)Transmission medium|(% style="width:797px" %)Class 5 or above twisted pairs or shielded twisted pairs with aluminum foil and woven mesh
107 |=(% style="width: 277px;" %)Transmission distance|(% style="width:797px" %)The distance between nodes: 100m or less
108 |=(% style="width: 277px;" %)Linking number|(% style="width:797px" %)8
109
110 == **{{id name="_Toc31870"/}}{{id name="_Toc15967"/}}{{id name="_Toc3350"/}}{{id name="_Toc2558"/}}Total numbers of links supported** ==
111
112 When LX5V-N series PLC is powered on, ModbusTCP server monitor is automatically enabled by default. 2 to 8 ModbusTCP clients are supported, and the port number is 502. (PLC host computer upload and download, monitor and HMI communication protocol are supported by the ModbusTCP server.)
113
114 The number of configurable links is 6. The free configurations of TCP server free protocol, TCP client free protocol, ModbusTCP server and ModbusTCP client are supported.
115
116 (% class="table-bordered" %)
117 |**Communicaition protocol**|**Maximum links supported**
118 |ModbusTCP server|8
119 |ModbusTCP client|6
120 |Free TCP server|6
121 |Free TCP client|6
122
123 == **IP address settings** ==
124
125 **Set by programming software**
126
127 Project manager →Parameter→PLC parameters→Ethernet configuration. Download selected parameters through PLC after modification. The download takes effect after STOP->RUN is complete.
128
129 (% class="box infomessage" %)
130 (((
131 **✎Note: **The maximum link supported of ModbusTCP servers is used to set the maximum number of external ModbusTCP clients that could connect to PLC simultaneously. The range is from 2 to 8.
132 )))
133
134 (% style="text-align:center" %)
135 [[image:14_html_5d3039a657266507.png||class="img-thumbnail"]]
136
137 **Set by special device**
138
139 Write IP address, subnet mask, and default gateway in SD2680 to SD2691.
140
141 SM2680 is set to ON, static IP function is enable. (**✎Note:** DHCP function is not supported by LX5V currently.)
142
143 SM2683 is set to ON, IP identification could be modified.
144
145 New IP address takes effect when STOP->RUN or after power-on again.
146
147 (% class="table-bordered" %)
148 |=(% scope="row" style="width: 108px;" %)**SM number**|=(% style="width: 277px;" %)**Name**|=(% style="width: 394px;" %)**Contents**|=(% style="width: 53px;" %)**R/W**|=(% style="width: 82px;" %)**SD number**|=(% style="width: 161px;" %)**Name**
149 |=(% style="width: 108px;" %)SM2680|(% style="width:277px" %)Static set IP switch|(% style="width:394px" %)(((
150 ON: Static set
151
152 OFF: Automatically configurate IP address by router DHCP, and could not be modify IP. When STOP->RUN takes effect.
153 )))|(% style="width:53px" %)R/W|(% style="width:82px" %)SD2680|(% style="width:161px" %)The 1st byte of IP address
154 |=(% style="width: 108px;" %)SM2681|(% style="width:277px" %)Display current network information|(% style="width:394px" %)(((
155 Refresh current IP gateway subnet mask after ON.
156
157 Turn OFF after the fresh is complete.
158 )))|(% style="width:53px" %)R/W|(% style="width:82px" %)SD2681|(% style="width:161px" %)The 2nd byte of IP address
159 |=(% style="width: 108px;" %)SM2682|(% style="width:277px" %)Display current MAC information|(% style="width:394px" %)(((
160 Refresh current MAC after ON.
161
162 Turn OFF after the fresh is complete.
163 )))|(% style="width:53px" %)R/W|(% style="width:82px" %)SD2682|(% style="width:161px" %)The 3rd byte of IP address
164 |=(% style="width: 108px;" %)SM2683|(% style="width:277px" %)The modification flag of IP, subnet mask and gateway|(% style="width:394px" %)(((
165 ON: Modifiable
166
167 OFF: Unmodifiable
168
169 (After setting to ON, modify when stop->run, and automatically turn OFF after the modification)
170 )))|(% style="width:53px" %)R/W|(% style="width:82px" %)SD2683|(% style="width:161px" %)The 4th byte of IP address
171 |=(% style="width: 108px;" %)SM2684|(% style="width:277px" %) |(% style="width:394px" %) |(% style="width:53px" %) |(% style="width:82px" %)SD2684|(% style="width:161px" %)The 1st byte of subnet mask
172 |=(% style="width: 108px;" %)SM2685|(% style="width:277px" %) |(% style="width:394px" %) |(% style="width:53px" %) |(% style="width:82px" %)SD2685|(% style="width:161px" %)The 2nd byte of subnet mask
173 |=(% style="width: 108px;" %)SM2686|(% style="width:277px" %) |(% style="width:394px" %) |(% style="width:53px" %) |(% style="width:82px" %)SD2686|(% style="width:161px" %)The 3rd byte of subnet mask
174 |=(% style="width: 108px;" %)SM2687|(% style="width:277px" %) |(% style="width:394px" %) |(% style="width:53px" %) |(% style="width:82px" %)SD2687|(% style="width:161px" %)The 4th byte of subnet mask
175 |=(% style="width: 108px;" %)SM2688|(% style="width:277px" %) |(% style="width:394px" %) |(% style="width:53px" %) |(% style="width:82px" %)SD2688|(% style="width:161px" %)The 1st byte of default gateway
176 |=(% style="width: 108px;" %)SM2689|(% style="width:277px" %) |(% style="width:394px" %) |(% style="width:53px" %) |(% style="width:82px" %)SD2689|(% style="width:161px" %)The 2nd byte of default gateway
177 |=(% style="width: 108px;" %)SM2690|(% style="width:277px" %) |(% style="width:394px" %) |(% style="width:53px" %) |(% style="width:82px" %)SD2690|(% style="width:161px" %)The 3rd byte of default gateway
178 |=(% style="width: 108px;" %)SM2691|(% style="width:277px" %) |(% style="width:394px" %) |(% style="width:53px" %) |(% style="width:82px" %)SD2691|(% style="width:161px" %)The 4th byte of default gateway
179
180 == **{{id name="_Toc4089"/}}{{id name="_Toc24639"/}}{{id name="_Toc2733"/}}{{id name="_Toc9277"/}}TCP protocol** ==
181
182 TCP protocol, short for Transport Control Protocol, is Is a connection-oriented and reliable transport layer protocol. Connection-oriented means that a normal TCP transmission need to be completed by establishing a specific virtual circuit connection between TCP client and TCP server. To transfer data over TCP, a connection must be established between hosts at both ends.
183
184 == **{{id name="_Toc8484"/}}{{id name="_Toc24972"/}}{{id name="_Toc28751"/}}{{id name="_Toc29133"/}}UDP protocol** ==
185
186 UDP protocol, short for User Datagram Protocol, is a connectionless transport layer protocol. There is no guarantee of data order, a risk of data loss. It provides a simple and unreliable information transfer service for transactions and is Mainly used in data broadcasting.
187
188 == **{{id name="_Toc21446"/}}{{id name="_Toc4791"/}}{{id name="_Toc10286"/}}Socket** ==
189
190 When the application layer communicates data over the transport layer, TCP encounters the problem of providing concurrent services to multiple application processes at the same time. Multiple TCP connections or multiple application processes may require data to be transmitted over the same TCP protocol port. To distinguish between different application processes and connections, many computer operating systems provide interfaces called sockets for applications to interact with the TCP/IP protocol.
191
192 To generate a socket, there are three main parameters: the IP address of the destination of the communication, the transport layer protocol used (TCP or UDP) used, and the port number used. By combining these three parameters and binding to a socket, the application layer and the transport layer can distinguish communication from different application processes or network connections through the socket interface, realizing concurrent services for data transmission.
193
194 == **{{id name="_Toc1095"/}}{{id name="_Toc17322"/}}{{id name="_Toc3808"/}}{{id name="_Toc23814"/}}Establish an Ethernet link by socket** ==
195
196 At least one pair of sockets is required to establish a socket link.
197
198 For TCP, the two sockets, one running on the TCP client and the other running on the TCP server. The connection process between sockets is divided into three steps: server monitor, client request, connection confirmation, also known as the three-way handshake.
199
200 **Server monitor: **After the server socket is enabled, it does not locate the specific client socket, but is in a state of waiting for the connection, monitoring the network status in real time, and waiting for the client's connection request.
201
202 **Client request: **Refers to a connection request made by a client-side socket, and the target of the connection is the server-side socket. To do this, the client-side socket must first describe the socket of the server to which it is connecting, indicate the address and port number of the server-side socket, and then make a connection request to the server-side socket
203
204 **Connection confirmation: **Refers to when the server-side socket listens to or receives a connection request from the client socket, it responds to the client socket request, establishes a new thread, sends the description of the server-side socket to the client. Once the client confirms this description, the connection is established. The server-side socket continues to listen and continues to receive connection requests from other client-side sockets.
205
206 (% style="text-align:center" %)
207 [[image:14_html_c4fd785c7111eade.gif||class="img-thumbnail"]]
208
209 In order to simplify the complexity of ladder programming, sockets have been partially simplified:
210
211 For TCP clients, merge socket() and connect() into SOCOOPEN instructions. After this function is enabled, automatically connect to the TCP server.
212
213 For TCP server, merge socket(), bind(), listen(), and accept() into SOCOOPEN instructions. After this function is enabled, automatically listen to server connection. If the server is successfully connected, the corresponding position is marked and the IP address and port information of the server are displayed.
214
215 For UDP, there is no concept of client and server. Creating a UDP socket only requires local address information and remote address information, without connection operations. Communication could be made when the address information of the local socket and the remote socket could be matched, that is, the remote address of the local socket is the same as the local address of the remote socket, and the local address of the local socket is the same as the remote address of the remote socket. For UDP connections, the connection could be established immediately by calling the SOCOPEN instruction.
216
217 == **{{id name="_Toc3008"/}}{{id name="_Toc10015"/}}{{id name="_Toc32444"/}}{{id name="_Toc444"/}}LX5V-N socket configuration instructions** ==
218
219 LX5V socket could be configured in Project manager→Extended function→Ethernet, right click to create socket configuration, as shown below.
220
221 (% style="text-align:center" %)
222 [[image:14_html_e73123ae26a00972.png||class="img-thumbnail"]]
223
224 **Socket ID:** The number of the socket ranges from K0 to K5, and a total of six are supported. The socket is used to specify links, and each ID could be used for one link and could not be defined repeatedly.
225
226 **Communication protocol: **TCP protocol and UDP protocol are supported.
227
228 **Operating mode: **For TCP, client and server could be selected. For UDP, this is meaningless.
229
230 **Local port:**
231
232 For TCP client mode, the local port would be automatically allocated by PLC without setting.
233
234 For TCP server mode, the local port ranges from 1 to 65535. Port 502 is used for internal ModbusTCP and can not be set to port 502.
235
236 For UDP mode, the local port ranges from 1 to 65535. Port 1092 is used for scanning protocol of Wecon and can not be set to port 1092.
237
238 **Destination IP: **It is valid in TCP client mode or UDP mode, and specify the IP of opposite end device to be linked.
239
240 **Destination port: **It is valid in TCP client mode or UDP mode, and specify the port number of opposite end device to be linked.
241
242 **Receive timeout period(10ms): **After the PLC sends the data, If the response of the opposite end device exceeds the timeout period, it is considered that the network has an abnormality and sets the wrong flag.
243
244 **TCP keep-alive mechanism: **When using the TCP protocol for communication, if the communication line is idle in most cases, there is only a small amount of data to be sent and received, but it is necessary to keep the link open continuously, or disconnect in time in the case of a drop, crash or forced end of the process at the other end of the communication, the keep-alive mechanism can be used to communicate.
245
246 When the keep-alive function is turned on, after the two parties stop communicating for 5 seconds, the TCP connection that opens the keep-alive function will send a survival confirmation message to the other party. If the other party responds, it means that the other party is alive and online. The connection is normal, and the survival confirmation message is sent again after 5 seconds to continue to confirm. If the other party does not confirm the survival, it means that the other party has a problem, the end that opens the keep-alive will continue to send it a survival confirmation message after 5 seconds. When the opposite end does not respond for 9 consecutive times, it means that the opposite end communication is abnormal, and the end that opens the keep-alive will actively disconnect.
247
248 = **{{id name="_Toc15732"/}}{{id name="_Toc1158"/}}{{id name="_Toc32054"/}}{{id name="_Toc21761"/}}Ethernet instruction** =
249
250 == **{{id name="_Toc23288"/}}{{id name="_Toc6733"/}}{{id name="_Toc31937"/}}{{id name="_Toc3966"/}}SOCOPEN/Create a socket link** ==
251
252 Create socket link specified by (s), and update the data information of this socket link to (d1) and the status information to (d2).
253
254 -[SOCOPEN (s) (d1) (d2)]
255
256 **Content, range and data type**
257
258 (% class="table-bordered" %)
259 |**Parameter**|**Content**|**Range**|**Data type**|**Data type (label)**
260 |(s)|Socket ID|0 to 5|Signed BIN 16 bit|ANY16
261 |(d1)|The start device that stores the data information of socket links|-|Signed BIN 16 bit|ANY_ELEMENTARY
262 |(d2)|The start device that stores the status information of socket links|-|Bit|ANY_BOOL
263
264 **Device used**
265
266 (% class="table-bordered" %)
267 |(% rowspan="2" %)**Instruction**|(% rowspan="2" %)**Parameter**|(% colspan="12" %)**Devices**|**Offset modification**|(((
268 **Pulse**
269
270 **extension**
271 )))
272 |**Y**|**M**|**S**|**SM**|**D.b**|**T**|**C**|**D**|**R**|**SD**|**K**|**H**|**[D]**|**XXP**
273 |(% rowspan="3" %)SOCOPEN|Parameter 1| | | | | | | | | | |●|●| |
274 |Parameter 2| | | | | |●|●|●|●|●| | | |
275 |Parameter 3|●|●|●|●|●| | | | | | | | |
276
277 **Features**
278
279 ✎Create the socket link specified in (s) and update the link information in (d1) and (d2).
280
281 ✎When the instruction is turned on, the devices specified in (d1) and (d2) will be used in other Ethernet instructions using the same socket ID. (SOCSEND, SOCRECV, SOCCLOSE, SOCMTCP)
282
283 ✎(d1) Specifies the following information (a total of 14 word devices):
284
285 (% class="table-bordered" %)
286 |**Device**|**Function**
287 |（d1）|Local port number
288 |（d1+1）|The 1st segment of the destination IP
289 |（d1+2）|The 2nd segment of the destination IP
290 |（d1+3）|The 3rd segment of the destination IP
291 |（d1+4）|The 4th segment of the destination IP
292 |（d1+5）|Destination port number
293 |（d1+6）|Receive timeout period(10ms)
294 |（d1+7）|Actual receiving length (byte)
295 |（d1+8）|Current link error code
296 |（d1+9）|Numbers of communication errors high bit
297 |（d1+10）|Numbers of communication errors low bit
298 |（d1+11）|Reserved
299 |（d1+12）|Reserved
300 |（d1+13）|Reserved
301
302 ✎(d2) Specifies the following information (a total of 14 bit devices):
303
304 (% class="table-bordered" %)
305 |**Device**|**ON status**|**OFF status**
306 |（d2）|Connecting|The connection is not turned on
307 |（d2+1）|Connection completed|Connecting or not connected
308 |（d2+2）|Sending data(used by SOCSEND instruction)|Data is not sent or data sending is complete
309 |（d2+3）|Data sending completed(used by SOCSEND instruction)|The instruction is not started or being sent.
310 |（d2+4）|Receiving data(used by SOCRECV instruction)|No data or receiving is completed
311 |（d2+5）|Data receiving completed(used by SOCRECV instruction)|The instruction is not started or received
312 |（d2+6）|Connection is closing|The instruction is not started or is receiving
313 |（d2+7）|Connection close completed|The instruction is not started or close is complete
314 |（d2+8）|Communication completed(used by SOCMTCP instruction)|In communication
315 |（d2+9）|Connection error|No error in connection
316 |（d2+10）|Reserved|Reserved
317 |（d2+11）|Reserved|Reserved
318 |（d2+12）|Reserved|Reserved
319 |（d2+13）|Reserved|Reserved
320
321 **Features**
322
323 **Local port number:**
324
325 Establish a TCP client: PLC automatically allocates the local communication port, ranging from 49152 to 65535. The port number is automatically incremented by 1 each time it is turned on.
326
327 Establish a TCP server: specified by Ethernet socket configuration of the host computer.
328
329 Establish a UDP connection: specified by Ethernet socket configuration of the host computer.
330
331 **Destination IP:**
332
333 Establish a TCP client: The destination address is specified by Ethernet socket configuration of the host computer.
334
335 Establish a TCP server: After the remote client connection is successful, display the IP address of the remote connection.
336
337 Establish a UDP connection: The destination address is specified by Ethernet socket configuration of the host computer.
338
339 **Destination port number:**
340
341 Establish a TCP client: The destination port number is specified by Ethernet socket configuration of the host computer.
342
343 Establish a TCP server: After the remote client connection is successful, display the port number of the remote connection.
344
345 Establish a UDP connection: The destination port number is specified by Ethernet socket configuration of the host computer.
346
347 **Receive timeout period(10ms): **specified by Ethernet socket configuration of the host computer.
348
349 **Actual receiving length: **This parameter is valid only when the SOCRECV instruction is used. It indicates the number of bytes received after the instruction is enabled.
350
351 **Current link error code:** Display the current error information. For details, Refer to Ethernet error code List.
352
353 **Numbers of communication errors:** total number of communication errors after successful connection (double word).
354
355 **Error codes**
356
357 (% class="table-bordered" %)
358 |**Error code**|**Content**
359 |4085H|The device specified in application instruction (d1) and (d2) exceeds the corresponding device range.
360 |5080H|The specified socket is already connected and cannot be opened again.
361 |5082H|The socket used by parameter 1 exceeds the range of 0 to 5.
362 |5083H|Failed to establish TCP server.
363 |5084H|Failed to create links.
364 |5086H|The specified (d) is not configured socket or the socket is not enabled.
365 |5089H|502 port could not be used on the TCP server because the 502 port is enabled by default.
366
367 == **{{id name="_Toc17901"/}}{{id name="_Toc26204"/}}{{id name="_Toc1326"/}}{{id name="_Toc2455"/}}SOCCLOSE/Close socket link** ==
368
369 Close socket link specified by (s).
370
371 -[SOCCLOSE (s)]
372
373 **Content, range and data type**
374
375 (% class="table-bordered" %)
376 |**Parameter**|**Content**|**Range**|**Data type**|**Data type (label)**
377 |(s)|Socket ID|0 to 5|Signed BIN 16 bit|ANY16
378
379 **Device used**
380
381 (% class="table-bordered" %)
382 |(% rowspan="2" %)**Instruction**|(% rowspan="2" %)**Parameter**|(% colspan="2" %)**Devices**|**Offset modification**|(((
383 **Pulse extension**
384 )))
385 |**K**|**H**|**[D]**|**XXP**
386 |SOCCLOSE|Parameter 1|●|●| |
387
388 **Features**
389
390 ✎Close the socket link specified in (s).
391
392 ✎When the TCP server is closed, the reset request will be sent to the remote client. At the moment, in bit device specified by SOCOPEN, the status of connection closure will be set. The socket is not actually released until the connection closure state is set and the next connection is opened
393
394 ✎If the socket specified by (s) is not connected to the remote end, it cannot be closed and the instruction error occurs.
395
396 **Error codes**
397
398 (% class="table-bordered" %)
399 |**Error code**|**Content**
400 |5081H|The socket specified by is not connected, and could not be closed
401 |5082H|The data specified in (s) exceeds the range of 0 to 5
402
403 == **SOCSEND/Ethernet free-form communication sending** ==
404
405 Send the data in (s2) to the socket link specified by (s1) at the length specified by (S3).
406
407 -[SOCSEND (s1) (s2) (s3)]
408
409 **Content, range and data type**
410
411 (% class="table-bordered" %)
412 |**Parameter**|**Content**|**Range**|**Data type**|**Data type (label)**
413 |(s1)|Socket ID|0 to 5|Signed BIN 16 bit|ANY16
414 |(s2)|The start device that send the data|-|Signed BIN 16 bit|ANY_ELEMENTARY
415 |(s3)|Sent length|1 to 256|Bit|ANY16
416
417 **Device used**
418
419 (% class="table-bordered" %)
420 |(% rowspan="2" %)**Instruction**|(% rowspan="2" %)**Parameter**|(% colspan="7" %)**Devices**|**Offset modification**|(((
421 **Pulse extension**
422 )))
423 |**T**|**C**|**D**|**R**|**SD**|**K**|**H**|**[D]**|**XXP**
424 |(% rowspan="3" %)SOCSEND|Parameter 1| | | | | |●|●| |
425 |Parameter 2|●|●|●|●|●| | | |
426 |Parameter 3|●|●|●|●|●|●|●| |
427
428 **Features**
429
430 ✎Send the data specified in (s2) from the socket connected to (s1), and the length is (s3).
431
432 ✎According to the devices specified by SOCOPEN, the information such as the sending status and the total sending length could be queried. For details, refer to the SOCOPEN instruction.
433
434 ✎It must be used with the SOCOPEN instruction, and data can only be sent after a full link has been established.
435
436 **Error codes**
437
438 (% class="table-bordered" %)
439 |**Error code**|**Content**
440 |4084H|The data in (s3) exceeds the specified range.
441 |5081H|The socket specified by is not connected, and could not be sent.
442 |5082H|The data specified in (s) exceeds the range of 0 to 5.
443
444 == **SOCRECV/Ethernet free-form communication reveiving** ==
445
446 Receive the data from the socket link in (s1) and store in the start device of (s2) at the length of (S3).
447
448 -[SOCRECV (s1) (S2) (S3)]
449
450 **Content, range and data type**
451
452 (% class="table-bordered" %)
453 |**Parameter**|**Content**|**Range**|**Data type**|**Data type (label)**
454 |(s1)|Socket ID|0 to 5|Signed BIN 16 bit|ANY16
455 |(s2)|The start device that receive the data|-|Signed BIN 16 bit|ANY_ELEMENTARY
456 |(s3)|Receive length|1 to 256|Bit|ANY16
457
458 **Device used**
459
460 (% class="table-bordered" %)
461 |(% rowspan="2" %)**Instruction**|(% rowspan="2" %)**Parameter**|(% colspan="7" %)**Devices**|(((
462 **Offset modification**
463 )))|(((
464 **Pulse extension**
465 )))
466 |**T**|**C**|**D**|**R**|**SD**|**K**|**H**|**[D]**|**XXP**
467 |(% rowspan="3" %)SOCRECV|Parameter 1| | | | | |●|●| |
468 |Parameter 2|●|●|●|●|●| | | |
469 |Parameter 3|●|●|●|●|●|●|●| |
470
471 **Features**
472
473 ✎Receive the data from the socket link in (s1) and store in the start device of (s2) at the length of (S3).
474
475 ✎According to the devices specified by SOCOPEN, the information such as the sending status and the total sending length could be queried. For details, refer to the SOCOPEN instruction.
476
477 ✎It must be used with the SOCOPEN instrcution, and data can only be sent after a full link has been established.
478
479 ✎**When used with SOCSEND, it could not be opened at the same time.**
480
481 **Error codes**
482
483 (% class="table-bordered" %)
484 |**Error code**|**Content**
485 |4084H|The data in (s3) exceeds the specified range.
486 |5081H|The socket specified by is not connected, and could not be sent.
487 |5082H|The data specified in (s) exceeds the range of 0 to 5.
488 |5087H|Receiving data timeout
489
490 == **{{id name="_Toc7826"/}}{{id name="_Toc20952"/}}{{id name="_Toc14034"/}}{{id name="_Toc18874"/}}SOCMTCP/Ethernet ModbusTCP communication** ==
491
492 Ethernet ModbusTCP client communication instruction
493
494 -[SOCMTCP (s1) (s2) (s3) (s4) (s5)]
495
496 **Content, range and data type**
497
498 (% class="table-bordered" %)
499 |**Parameter**|**Content**|**Range**|**Data type**|**Data type (label)**
500 |(s1)|Socket ID|0 to 5|Signed BIN 16 bit|ANY16
501 |(s2)|High byte is station number, low byte is function code|-|Signed BIN 16 bit|ANY_ELEMENTARY
502 |(s3)|The Modbus address that need communication|1 to 65536|Unsigned BIN 16 bit|ANY16
503 |(s4)|Sent length or received length| |Signed BIN 16 bit|ANY16
504 |(s5)|Sent or received start device| |Signed BIN 16 bit|ANY_ELEMENTARY
505
506 **Device used**
507
508 (% class="table-bordered" %)
509 |(% rowspan="2" %)**Instruction**|(% rowspan="2" %)**Parameter**|(% colspan="7" %)**Devices**|**Offset modification**|(((
510 **Pulse extension**
511 )))
512 |**T**|**C**|**D**|**R**|**SD**|**K**|**H**|**[D]**|**XXP**
513 |(% rowspan="5" %)SOCMTCP|Parameter 1| | | | | |●|●| |
514 |Parameter 2|●|●|●|●|●|●|●| |
515 |Parameter 3|●|●|●|●|●|●|●| |
516 |Parameter 4|●|●|●|●|●|●|●| |
517 |Parameter 5|●|●|●|●|●| | | |
518
519 **Features**
520
521 ✎(s1) specify the socket link. The other parameters are compatible with RS instruction Modbus master protocol.
522
523 ✎(s2) high byte is station number. For ModbusTCP, the station number can be set freely.
524
525 ✎(s2) low byte is function code.For details, refer to [[Modbus protocol description.>>http://54.254.131.57:8080/xwiki/bin/view/PLC%20Editor2/1%20User%20manual/2.1%20LX5V%20user%20manual/10/#HModbusprotocoldescription]]
526
527 ✎(s3) Modbus communication address, ModbusTCP server address that needs to be read or written.
528
529 ✎(s4): the length read or written by Modbus.
530
531 ✎(s5): the start device that Modbus receive read data or or store written data.
532
533 ✎It must be used with the SOCOPEN instruction, and data can only be sent after a full link has been established.
534
535 ✎This instruction can only be used when a TCP client socket link is established.
536
537 ✎The communication completion information and the number of received and transmitted could be viewed in the soft devices specified in the SOCOPEN instruction.
538
539 **Error codes**
540
541 (% class="table-bordered" %)
542 |**Error code**|**Content**
543 |5081H|The socket specified by is not connected, and could not communicate.
544 |5082H|The data specified in (s1) exceeds the range of 0 to 5.
545 |5086H|The socket specified by (s1) is not configured in the host computer or enabled.
546 |5088H|The SOCMTCP instruction only supports TCP client mode.
547
548 = **{{id name="_Toc8546"/}}{{id name="_Toc3486"/}}{{id name="_Toc14446"/}}{{id name="_Toc26257"/}}Ethernet applications** =
549
550 == **{{id name="_Toc2539"/}}{{id name="_Toc1989"/}}{{id name="_Toc30706"/}}Data exchange between two PLCs through ModbusTCP** ==
551
552 (% class="table-bordered" %)
553 |**Parameters**|PLC No.1|PLC No.2
554 |**Port number**|Free internal distribution|502
555 |**IP address**|192.168.8.10|192.168.8.8
556 |**Protocol type**|ModbusTCP client|ModbusTCP server
557
558 The socket configuration of PLC No.1
559
560 (% style="text-align:center" %)
561 [[image:14_html_202f1d4e5f1733c8.png||class="img-thumbnail"]]
562
563 Ladder diagram logic: Automatically connect socket 0 after power on 1s. Read the 0 address length 20 of PLC No.2 to D100 to D119 after the link is successful, and set the value of D100 to D119 to address 100 of PLC No.2 after the communication is successful. Close the link when communicate successfully again, and wait 1s to re-connect after closing successfully. Repeat the actions above.
564
565 The ladder diagram of PLC No.1
566
567 (% style="text-align:center" %)
568 [[image:14_html_4206400d31f134fa.png||class="img-thumbnail"]]
569
570 As a ModbusTCP server, PLC No. 2 does not need to write instructions. (Open two links by default, and could be modified in [PLC parameters]→[Ethernet settings]. A maximum of eight links are supported.)
571
572 == **{{id name="_Toc462"/}}{{id name="_Toc22212"/}}{{id name="_Toc11578"/}}{{id name="_Toc30403"/}}Data exchange between two PLCs through Free TCP** ==
573
574 (% class="table-bordered" %)
575 |**Parameters**|PLC No.1|PLC No.2
576 |**Port number**|Free internal distribution|520
577 |**IP address**|192.168.8.10|192.168.8.8
578 |**Protocol type**|Free TCP client|Free TCP server
579
580 The IP setting of PLC No.1
581
582 [Project manager]→[Parameter]→[PLC parameter]→[Ethernet settings]
583
584 (% style="text-align:center" %)
585 [[image:14_html_c4654ab7a5c4ee36.png||class="img-thumbnail"]]
586
587 The socket comfiguration of PLC No.1
588
589 [Project manager]→[Extended function]→[Ethernet],and right click to create.
590
591 (% style="text-align:center" %)
592 [[image:14_html_ec9300bfd59ac79f.png||class="img-thumbnail"]]
593
594 The ladder diagram of PLC No.1
595
596 Ladder diagram logic: Automatically connect socket one after power on. Send character string ”hello word” initiatively to PLC No.2 after connecting successfully.
597
598 After receiving "hello word" and verifying it correctly, PLC No.2 would reply “abcdefghijklmnopqrstuvwxyz”. If PLC No.1 receives the reply of PLC No.2, the link closed.
599
600 (% style="text-align:center" %)
601 [[image:14_html_3e51e79948c709b.png||class="img-thumbnail"]]
602
603 The socket configuration of PLC No.2
604
605 [Project manager]→[Parameter]→[PLC parameter]→[Ethernet settings]
606
607 (% style="text-align:center" %)
608 [[image:14_html_4d60262e7d7e6978.png||class="img-thumbnail"]]
609
610 The socket comfiguration of PLC No.2
611
612 [Project manager]→[Extended function]→[Ethernet],and right click to create.
613
614 (% style="text-align:center" %)
615 [[image:14_html_1e0fa43741d0ea96.png||class="img-thumbnail"]]
616
617 The ladder diagram of PLC No.2
618
619 (% style="text-align:center" %)
620 [[image:14_html_309dfbea85ed7f7c.png||class="img-thumbnail"]]
621
622 Ladder diagram logic: Automatically open the monitor server link of socket one after power on. The data sent by the client is continuously read after connecting successfully. After receiving "hello word", PLC No.2 would reply “abcdefghijklmnopqrstuvwxyz”.
623
624 == **{{id name="_Toc7658"/}}{{id name="_Toc3572"/}}{{id name="_Toc27678"/}}{{id name="_Toc13195"/}}Data exchange between two PLCs through Free UDP** ==
625
626 (% class="table-bordered" %)
627 |**Parameters**|PLC No.1|PLC No.2
628 |**Port number**|666|666
629 |**IP address**|192.168.8.10|192.168.8.8
630 |**Protocol type**|Free UDP|Free UDP
631
632 The IP setting of PLC No.1
633
634 (% style="text-align:center" %)
635 [[image:14_html_4d60262e7d7e6978.png||class="img-thumbnail"]]
636
637 The socket configuration of PLC No.1
638
639 (% style="text-align:center" %)
640 [[image:14_html_d26f36ecd7d82039.png||class="img-thumbnail"]]
641
642 The ladder diagram of PLC No.1
643
644 Ladder diagram logic: After setting the NIC state bit, establish UDP socket. After the link is established successful, send a data of 20 bytes that start from D100 to 192.168.8.10: 666. After the data is sent successfully, wait for the reply data of the other party. After the reply succeeds, continues the process, and so on
645
646 (% style="text-align:center" %)
647 [[image:14_html_dbd3907c288c9523.png||class="img-thumbnail"]]
648
649 The IP address configuration of PLC No.2
650
651 (% style="text-align:center" %)
652 [[image:14_html_4d60262e7d7e6978.png||class="img-thumbnail"]]
653
654 The socket configuration of PLC No.2
655
656 (% style="text-align:center" %)
657 [[image:14_html_5db18357d06716af.png||class="img-thumbnail"]]
658
659 The ladder diagram of PLC No.2
660
661 Ladder diagram logic: After setting the NIC state bit, establish UDP socket. After the link is established successful, send a data of 20 bytes that start from D300 to 192.168.8.10: 666. After the data is sent successfully, wait for the reply data of the other party, and so on.
662
663 (% style="text-align:center" %)
664 [[image:14_html_4a93f07f5fdbe522.png||class="img-thumbnail"]]
665
666 = **Server address table** =
667
668
669 |(% colspan="5" %)**Word address**
670 |**Address type**|**Occupy**|**Address range**|**Decimal address**|**Total reserved address size**
671 |T0 to T511|512 WORD|0x0000-0x01ff|0|1536
672 |C0 to C255|256 WORD|0x0600-0x06ff|1536|1024
673 |LC0 to LC255|512 WORD|0x0A00-0x0BFF|2560|1024
674 |HSC0 to HSC15|32 WORD|0x0E00-0x0E1F|3584|512
675 |D0 to D7999|8000 WORD|0x1000-0x2F3F|4096|16384
676 |SD0 to SD4095|4096 WORD|0x5000-0x5FFF|20480|12288
677 |R0 to R29999|30000 WORD|0x8000-0xF52F|32768|30000
678
679 |(% colspan="5" %)**Bit address**
680 |**Address type**|**Occupy**|**Address range**|**Decimal address**|**Total reserved address size**
681 |T0 to T511|512 bit|0x0000-0x01ff| |1536
682 |C0 to C255|256 bit|0x0600-0x06ff|1536|1024
683 |LC0 to LC255|256 bit|0x0A00-0x0AFF|2560|1024
684 |HSC0 to HSC15|16 bit|0x0E00-0x0E0F|3584|512
685 |M0 to M7999|8000 bit|0x1000-0x2F3F|4096|16384
686 |SM0 to SM4095|4096 bit|0x5000-0x5FFF|20480|12288
687 |Reserved| |0x8000-0xBFFF| |16383
688 |S0 to S4095|4096 bit|0xC000-0xCFFF|49152|8192
689 |X0 to X1777|1024 bit|0xE000-0xE3FF|57344|4096
690 |Y0 to Y1777|1024 bit|0xF000-0xF3FF|61440|4096
691
692 = =
693
694 = =
695
696 = =
697
698 = =
699
700 = **{{id name="_Toc4903"/}}{{id name="_Toc31730"/}}{{id name="_Toc608"/}}{{id name="_Toc9880"/}}List of special device related to Ethernet** =
701
702
703 (% class="table-bordered" %)
704 |(% style="width:124px" %)**SM number**|(% style="width:396px" %)**Name**|**Content**|**R/W**|**Power down retentive**
705 |(% style="width:124px" %)SM2681|(% style="width:396px" %)Display current network information|(((
706 Refresh current IP gateway subnet mask after ON.
707
708 Turn OFF after the fresh is complete.
709 )))|R/W|×
710 |(% style="width:124px" %)SM2682|(% style="width:396px" %)Display current MAC information|(((
711 Refresh current MAC after ON.
712
713 Turn OFF after the fresh is complete.
714 )))|R/W|×
715 |(% style="width:124px" %)SM2683|(% style="width:396px" %)The modification flag of IP, subnet mask and gateway|(((
716 ON: Modifiable
717
718 OFF: Unmodifiable
719
720 (After setting to ON, modify when stop->run, and turn OFF automatically after the modification)
721 )))|R/W|√
722 |(% style="width:124px" %)SM2684|(% style="width:396px" %)The connecting status of NIC|(((
723 ON: The network is connected
724
725 OFF: The network is not connected. Please check whether the network cable is connected.
726 )))|R|√
727 |(% style="width:124px" %)SM2692|(% style="width:396px" %)MAC address modification flag|(((
728 ON: Modifiable
729
730 OFF: Unmodifiable
731
732 (After setting to ON, modify when stop->run, and automatically turn OFF after the modification)
733 )))|R/W|√
734 |(% style="width:124px" %)SM2700|(% style="width:396px" %)ModbusTCP keep-alive mechanism|(((
735 ON: open
736
737 OFF: close (default)
738 )))|R/W|√
739 |(% style="width:124px" %)SM2701|(% style="width:396px" %)ModbusTCP server force close|(((
740 ON: open
741
742 OFF: close (default)
743
744 (After enabling, automatically changes to OFF After it is successfully turned OFF)
745 )))|R/W|×
746 |(% style="width:124px" %)SM2710|(% style="width:396px" %)Ethernet error flag|(((
747 ON: Ethernet error. Please check SD2710 and SD2711
748
749 OFF: No Ethernet error.
750 )))|R|×
751 |(% style="width:124px" %)SM2740|(% style="width:396px" %)ModbusTCP server connection status 1|(((
752 ON: The client is connected
753
754 OFF: The client is not connected
755 )))|R|×
756 |(% style="width:124px" %)SM2760|(% style="width:396px" %)ModbusTCP server connection status 2|(((
757 ON: The client is connected
758
759 OFF: The client is not connected
760 )))|R|×
761 |(% style="width:124px" %)SM2780|(% style="width:396px" %)ModbusTCP server connection status 3|(((
762 ON: The client is connected
763
764 OFF: The client is not connected
765 )))|R|×
766 |(% style="width:124px" %)SM2800|(% style="width:396px" %)ModbusTCP server connection status 4|(((
767 ON: The client is connected
768
769 OFF: The client is not connected
770 )))|R|×
771 |(% style="width:124px" %)SM2820|(% style="width:396px" %)ModbusTCP server connection status 5|(((
772 ON: The client is connected
773
774 OFF: The client is not connected
775 )))|R|×
776 |(% style="width:124px" %)SM2840|(% style="width:396px" %)ModbusTCP server connection status 6|(((
777 ON: The client is connected
778
779 OFF: The client is not connected
780 )))|R|×
781 |(% style="width:124px" %)SM2860|(% style="width:396px" %)ModbusTCP server connection status 7|(((
782 ON: The client is connected
783
784 OFF: The client is not connected
785 )))|R|×
786 |(% style="width:124px" %)SM2880|(% style="width:396px" %)ModbusTCP server connection status 8|(((
787 ON: The client is connected
788
789 OFF: The client is not connected
790 )))|R|×
791
792 (% class="table-bordered" %)
793 |(% style="width:122px" %)**SD number**|(% style="width:388px" %)**Name**|**Content**|**R/W**|**Power down retentive**
794 |(% style="width:122px" %)SD2680|(% style="width:388px" %)The 1st byte of IP address|(% rowspan="4" %)Local IP address|R/W|√
795 |(% style="width:122px" %)SD2681|(% style="width:388px" %)The 2nd byte of IP address|R/W|√
796 |(% style="width:122px" %)SD2682|(% style="width:388px" %)The 3rd byte of IP address|R/W|√
797 |(% style="width:122px" %)SD2683|(% style="width:388px" %)The 4th byte of IP address|R/W|√
798 |(% style="width:122px" %)SD2684|(% style="width:388px" %)The 1st byte of subnet mask|(% rowspan="4" %)Local subnet mask|R/W|√
799 |(% style="width:122px" %)SD2685|(% style="width:388px" %)The 2nd byte of subnet mask|R/W|√
800 |(% style="width:122px" %)SD2686|(% style="width:388px" %)The 3rd byte of subnet mask|R/W|√
801 |(% style="width:122px" %)SD2687|(% style="width:388px" %)The 4th byte of subnet mask|R/W|√
802 |(% style="width:122px" %)SD2688|(% style="width:388px" %)The 1st byte of default gateway|(% rowspan="4" %)Local default gateway|R/W|√
803 |(% style="width:122px" %)SD2689|(% style="width:388px" %)The 2nd byte of default gateway|R/W|√
804 |(% style="width:122px" %)SD2690|(% style="width:388px" %)The 3rd byte of default gateway|R/W|√
805 |(% style="width:122px" %)SD2691|(% style="width:388px" %)The 4th byte of default gateway|R/W|√
806 |(% style="width:122px" %)SD2692|(% style="width:388px" %)The 1st byte of MAC|(% rowspan="6" %)Local MAC address|R/W|√
807 |(% style="width:122px" %)SD2693|(% style="width:388px" %)The 2nd byte of MAC|R/W|√
808 |(% style="width:122px" %)SD2694|(% style="width:388px" %)The 3rd byte of MAC|R/W|√
809 |(% style="width:122px" %)SD2695|(% style="width:388px" %)The 4th byte of MAC|R/W|√
810 |(% style="width:122px" %)SD2696|(% style="width:388px" %)The 5th byte of MAC|R/W|√
811 |(% style="width:122px" %)SD2697|(% style="width:388px" %)The 6th byte of MAC|R/W|√
812 |(% style="width:122px" %)SD2700|(% style="width:388px" %)Communication speed display|(((
813 0: 100Mbps/Half-duplex
814
815 1: 100Mbps/Full-duplex
816
817 2: 10Mbps/Half-duplex
818
819 3: 10Mbps/Full-duplex
820 )))|R|×
821 |(% style="width:122px" %)SD2702|(% style="width:388px" %)Maximum link number supported by ModbusTCP server|Maximum link number of simultaneous client links supported by local ModbusTCP server|R/W|×
822 |(% style="width:122px" %)SD2703|(% style="width:388px" %)The number of links of ModbusTCP|The number of links of local ModbusTCP|R|×
823 |(% style="width:122px" %)SD2710|(% style="width:388px" %)Error code|Ehternet error code|R|×
824 |(% style="width:122px" %)SD2711|(% style="width:388px" %)The socket ID of current error|(((
825 -1: default ModbusTCP server
826
827 0 to 5: Custom socket error
828 )))|R|×
829 |(% style="width:122px" %)SD2720|(% style="width:388px" %)Input low bit of number of ping request|(% rowspan="2" %)The number of external input ping command|R|×
830 |(% style="width:122px" %)SD2721|(% style="width:388px" %)Input high bit of number of ping request|R|×
831 |(% style="width:122px" %)SD2722|(% style="width:388px" %)Input low bit of number of ping response|(% rowspan="2" %)The number of replies after receiving external ping command|R|×
832 |(% style="width:122px" %)SD2723|(% style="width:388px" %)Input high bit of number of ping response|R|×
833 |(% style="width:122px" %)SD2724|(% style="width:388px" %)Input low bit of number of ping request|(% rowspan="2" %)The number of sending ping command|R|×
834 |(% style="width:122px" %)SD2725|(% style="width:388px" %)Input high bit of number of ping request|R|×
835 |(% style="width:122px" %)SD2726|(% style="width:388px" %)Input low bit of number of ping response|(% rowspan="2" %)The number of replies after receiving external ping command sent|R|×
836 |(% style="width:122px" %)SD2727|(% style="width:388px" %)Input high bit of number of ping response|R|×
837 |(% style="width:122px" %)SD2728|(% style="width:388px" %)The number of arp pack sent|Count of the number of arp packets sent|R|×
838 |(% style="width:122px" %)SD2729|(% style="width:388px" %)The number of arp pack received|The number of arp pack received|R|×
839 |(% style="width:122px" %)SD2730|(% style="width:388px" %)The number of IP pack sent|The number of IP pack sent|R|×
840 |(% style="width:122px" %)SD2731|(% style="width:388px" %)The number of IP pack received|The number of IP pack received|R|×
841 |(% style="width:122px" %)SD2732|(% style="width:388px" %)The number of TCP pack sent|The number of TCP pack sent|R|×
842 |(% style="width:122px" %)SD2733|(% style="width:388px" %)The number of TCP pack received|The number of TCP pack received|R|×
843 |(% style="width:122px" %)SD2734|(% style="width:388px" %)The number of UDP pack sent|The number of UDP pack sent|R|×
844 |(% style="width:122px" %)SD2735|(% style="width:388px" %)The number of UDP pack received|The number of UDP pack received|R|×
845 |(% style="width:122px" %)SD2740|(% style="width:388px" %)Connection one Local port number|(% rowspan="11" %)The first ModbusTCP client to connect the connection information and error information of this PLC.|R|×
846 |(% style="width:122px" %)SD2741|(% style="width:388px" %)Connection one The 1st byte of IP address|R|×
847 |(% style="width:122px" %)SD2742|(% style="width:388px" %)Connection one The 2nd byte of IP address|R|×
848 |(% style="width:122px" %)SD2743|(% style="width:388px" %)Connection one The 3rd byte of IP address|R|×
849 |(% style="width:122px" %)SD2744|(% style="width:388px" %)Connection one The 4th byte of IP address|R|×
850 |(% style="width:122px" %)SD2745|(% style="width:388px" %)Connection one Opposite end port number|R|×
851 |(% style="width:122px" %)SD2746|(% style="width:388px" %)Reserved|R|×
852 |(% style="width:122px" %)SD2747|(% style="width:388px" %)Reserved| |
853 |(% style="width:122px" %)SD2748|(% style="width:388px" %)Connection one Error code|R|×
854 |(% style="width:122px" %)SD2749|(% style="width:388px" %)Connection one Error communication times low word|R|×
855 |(% style="width:122px" %)SD2750|(% style="width:388px" %)Connection one Error communication times high word|R|×
856 |(% style="width:122px" %)SD2760|(% style="width:388px" %)Connection two Local port number|(% rowspan="11" %)The second ModbusTCP client to connect the connection information and error information of this PLC.|R|×
857 |(% style="width:122px" %)SD2761|(% style="width:388px" %)Connection two The 1st byte of IP address|R|×
858 |(% style="width:122px" %)SD2762|(% style="width:388px" %)Connection two The 2nd byte of IP address|R|×
859 |(% style="width:122px" %)SD2763|(% style="width:388px" %)Connection two The 3rd byte of IP address|R|×
860 |(% style="width:122px" %)SD2764|(% style="width:388px" %)Connection two The 4th byte of IP address|R|×
861 |(% style="width:122px" %)SD2765|(% style="width:388px" %)Connection two Opposite end port number|R|×
862 |(% style="width:122px" %)SD2766|(% style="width:388px" %)Reserved|R|×
863 |(% style="width:122px" %)SD2767|(% style="width:388px" %)Reserved| |
864 |(% style="width:122px" %)SD2768|(% style="width:388px" %)Connection two Error code|R|×
865 |(% style="width:122px" %)SD2769|(% style="width:388px" %)Connection two Error communication times low word|R|×
866 |(% style="width:122px" %)SD2770|(% style="width:388px" %)Connection two Error communication times high word|R|×
867 |(% style="width:122px" %)SD2780|(% style="width:388px" %)Connection three Local port number|(% rowspan="11" %)The third ModbusTCP client to connect the connection information and error information of this PLC.|R|×
868 |(% style="width:122px" %)SD2781|(% style="width:388px" %)Connection three The 1st byte of IP address|R|×
869 |(% style="width:122px" %)SD2782|(% style="width:388px" %)Connection three The 2nd byte of IP address|R|×
870 |(% style="width:122px" %)SD2783|(% style="width:388px" %)Connection three The 3rd byte of IP address|R|×
871 |(% style="width:122px" %)SD2784|(% style="width:388px" %)Connection three The 4th byte of IP address|R|×
872 |(% style="width:122px" %)SD2785|(% style="width:388px" %)Connection three Opposite end port number|R|×
873 |(% style="width:122px" %)SD2786|(% style="width:388px" %)Reserved|R|×
874 |(% style="width:122px" %)SD2787|(% style="width:388px" %)Reserved| |
875 |(% style="width:122px" %)SD2788|(% style="width:388px" %)Connection three Error code|R|×
876 |(% style="width:122px" %)SD2789|(% style="width:388px" %)Connection three Error communication times low word|R|×
877 |(% style="width:122px" %)SD2780|(% style="width:388px" %)Connection three Error communication times high word|R|×
878 |(% style="width:122px" %)SD2800|(% style="width:388px" %)Connection four Local port number|(% rowspan="11" %)The forth ModbusTCP client to connect the connection information and error information of this PLC.|R|×
879 |(% style="width:122px" %)SD2801|(% style="width:388px" %)Connection four The 1st byte of IP address|R|×
880 |(% style="width:122px" %)SD2802|(% style="width:388px" %)Connection four The 2nd byte of IP address|R|×
881 |(% style="width:122px" %)SD2803|(% style="width:388px" %)Connection four The 3rd byte of IP address|R|×
882 |(% style="width:122px" %)SD2804|(% style="width:388px" %)Connection four The 4th byte of IP address|R|×
883 |(% style="width:122px" %)SD2805|(% style="width:388px" %)Connection four Opposite end port number|R|×
884 |(% style="width:122px" %)SD2806|(% style="width:388px" %)Reserved|R|×
885 |(% style="width:122px" %)SD2807|(% style="width:388px" %)Reserved| |
886 |(% style="width:122px" %)SD2808|(% style="width:388px" %)Connection four Error code|R|×
887 |(% style="width:122px" %)SD2809|(% style="width:388px" %)Connection four Error communication times low word|R|×
888 |(% style="width:122px" %)SD2810|(% style="width:388px" %)Connection four Error communication times high word|R|×
889 |(% style="width:122px" %)SD2820|(% style="width:388px" %)Connection five Local port number|(% rowspan="11" %)The fifth ModbusTCP client to connect the connection information and error information of this PLC.|R|×
890 |(% style="width:122px" %)SD2821|(% style="width:388px" %)Connection five The 1st byte of IP address|R|×
891 |(% style="width:122px" %)SD2822|(% style="width:388px" %)Connection five The 2nd byte of IP address|R|×
892 |(% style="width:122px" %)SD2823|(% style="width:388px" %)Connection five The 3rd byte of IP address|R|×
893 |(% style="width:122px" %)SD2824|(% style="width:388px" %)Connection five The 4th byte of IP address|R|×
894 |(% style="width:122px" %)SD2825|(% style="width:388px" %)Connection five Opposite end port number|R|×
895 |(% style="width:122px" %)SD2826|(% style="width:388px" %)Reserved|R|×
896 |(% style="width:122px" %)SD2827|(% style="width:388px" %)Reserved| |
897 |(% style="width:122px" %)SD2828|(% style="width:388px" %)Connection five Error code|R|×
898 |(% style="width:122px" %)SD2829|(% style="width:388px" %)Connection five Error communication times low word|R|×
899 |(% style="width:122px" %)SD2830|(% style="width:388px" %)Connection five Error communication times high word|R|×
900 |(% style="width:122px" %)SD2840|(% style="width:388px" %)Connection six Local port number|(% rowspan="11" %)The sixth ModbusTCP client to connect the connection information and error information of this PLC.|R|×
901 |(% style="width:122px" %)SD2841|(% style="width:388px" %)Connection six The 1st byte of IP address|R|×
902 |(% style="width:122px" %)SD2842|(% style="width:388px" %)Connection six The 2nd byte of IP address|R|×
903 |(% style="width:122px" %)SD2843|(% style="width:388px" %)Connection six The 3rd byte of IP address|R|×
904 |(% style="width:122px" %)SD2844|(% style="width:388px" %)Connection six The 4th byte of IP address|R|×
905 |(% style="width:122px" %)SD2845|(% style="width:388px" %)Connection six Opposite end port number|R|×
906 |(% style="width:122px" %)SD2846|(% style="width:388px" %)Reserved|R|×
907 |(% style="width:122px" %)SD2847|(% style="width:388px" %)Reserved| |
908 |(% style="width:122px" %)SD2848|(% style="width:388px" %)Connection six Error code|R|×
909 |(% style="width:122px" %)SD2849|(% style="width:388px" %)Connection six Error communication times low word|R|×
910 |(% style="width:122px" %)SD2850|(% style="width:388px" %)Connection six Error communication times high word|R|×
911 |(% style="width:122px" %)SD2860|(% style="width:388px" %)Connection seven Local port number|(% rowspan="11" %)The seventh ModbusTCP client to connect the connection information and error information of this PLC.|R|×
912 |(% style="width:122px" %)SD2861|(% style="width:388px" %)Connection seven The 1st byte of IP address|R|×
913 |(% style="width:122px" %)SD2862|(% style="width:388px" %)Connection seven The 2nd byte of IP address|R|×
914 |(% style="width:122px" %)SD2863|(% style="width:388px" %)Connection seven The 3rd byte of IP address|R|×
915 |(% style="width:122px" %)SD2864|(% style="width:388px" %)Connection seven The 4th byte of IP address|R|×
916 |(% style="width:122px" %)SD2865|(% style="width:388px" %)Connection seven Opposite end port number|R|×
917 |(% style="width:122px" %)SD2866|(% style="width:388px" %)Reserved|R|×
918 |(% style="width:122px" %)SD2867|(% style="width:388px" %)Reserved| |
919 |(% style="width:122px" %)SD2868|(% style="width:388px" %)Connection seven Error code|R|×
920 |(% style="width:122px" %)SD2869|(% style="width:388px" %)Connection seven Error communication times low word|R|×
921 |(% style="width:122px" %)SD2870|(% style="width:388px" %)Connection seven Error communication times high word|R|×
922 |(% style="width:122px" %)SD2880|(% style="width:388px" %)Connection eight Local port number|(% rowspan="11" %)The eighth ModbusTCP client to connect the connection information and error information of this PLC.|R|×
923 |(% style="width:122px" %)SD2881|(% style="width:388px" %)Connection eight The 1st byte of IP address|R|×
924 |(% style="width:122px" %)SD2882|(% style="width:388px" %)Connection eight The 2nd byte of IP address|R|×
925 |(% style="width:122px" %)SD2883|(% style="width:388px" %)Connection eight The 3rd byte of IP address|R|×
926 |(% style="width:122px" %)SD2884|(% style="width:388px" %)Connection eight The 4th byte of IP address|R|×
927 |(% style="width:122px" %)SD2885|(% style="width:388px" %)Connection eight Opposite end port number|R|×
928 |(% style="width:122px" %)SD2866|(% style="width:388px" %)Reserved| |
929 |(% style="width:122px" %)SD2867|(% style="width:388px" %)Reserved|R|×
930 |(% style="width:122px" %)SD2888|(% style="width:388px" %)Connection eight Error code|R|×
931 |(% style="width:122px" %)SD2889|(% style="width:388px" %)Connection eight Error communication times low word|R|×
932 |(% style="width:122px" %)SD2890|(% style="width:388px" %)Connection eight Error communication times high word|R|×
933
934 = **{{id name="_Toc25788"/}}{{id name="_Toc14289"/}}{{id name="_Toc2936"/}}{{id name="_Toc31902"/}}Ethernet error codes table** =
935
936 == **{{id name="_Toc15175"/}}{{id name="_Toc13420"/}}{{id name="_Toc19210"/}}{{id name="_Toc13265"/}}Operational error** ==
937
938 (% class="table-bordered" %)
939 |(% style="width:101px" %)**Error code**|(% style="width:462px" %)**Description**|(% style="width:186px" %)**Action**|(% style="width:516px" %)**Processing scheme**|(% style="width:183px" %)**Test time**
940 |(% style="width:101px" %)3680|(% style="width:462px" %)Ethernet data reception error|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Check the environment for interference.|(% style="width:183px" %)When the instruction is executed
941 |(% style="width:101px" %)3681|(% style="width:462px" %)Ethernet data reception timeout|(% style="width:186px" %)Continue to run|(% style="width:516px" %)(((
942 Check whether the network cable is loose.
943
944 Check whether the network opposite end is faulty and cannot send data.
945
946 Check whether the network opposite end is not responding in time and the data is too late.
947
948 For this reason, try increasing the receive timeout in the socket configuration.
949 )))|(% style="width:183px" %)When the instruction is executed
950 |(% style="width:101px" %)3684|(% style="width:462px" %)ModbusTCP station number configuration error|(% style="width:186px" %)Continue to run|(% style="width:516px" %)(((
951 Check the setting of slave station number.
952
953 Check whether there is a problem with the receiving and sending mechanism of the slave station.
954 )))|(% style="width:183px" %)When the instruction is executed
955 |(% style="width:101px" %)3685|(% style="width:462px" %)ModbusTCP send buffer overflow|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Contact the technician for the error|(% style="width:183px" %)When the instruction is executed
956 |(% style="width:101px" %)3686|(% style="width:462px" %)ModbusTCP function code error|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Check whether the function code set is supported by the PLC.|(% style="width:183px" %)When the instruction is executed
957 |(% style="width:101px" %)3687|(% style="width:462px" %)ModbusTCP address error|(% style="width:186px" %)Continue to run|(% style="width:516px" %)(((
958 Check whether the slave station has the address.
959
960 (Please refer to Modbus abnormality 02)
961 )))|(% style="width:183px" %)When the instruction is executed
962 |(% style="width:101px" %)3688|(% style="width:462px" %)ModbusTCP length error|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Check whether the communication length exceeds the range of Modbus.|(% style="width:183px" %)When the instruction is executed
963 |(% style="width:101px" %)3689|(% style="width:462px" %)ModbusTCP data error|(% style="width:186px" %)Continue to run|(% style="width:516px" %)(((
964 Check whether the parameter of instruction is incorrect.
965
966 Check whether the value set is supported by slave. (Please refer to Modbus abnormality 03)
967 )))|(% style="width:183px" %)When the instruction is executed
968 |(% style="width:101px" %)368A|(% style="width:462px" %)ModbusTCP slave station is busy|(% style="width:186px" %)Continue to run|(% style="width:516px" %)(((
969 Slave returns message: Slave is busy.
970
971 (Please refer to Modbus abnormality 06)
972 )))|(% style="width:183px" %)When the instruction is executed
973 |(% style="width:101px" %)368B|(% style="width:462px" %)ModbusTCP slave station does not support function code|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Check whether the function code is supported by slave. (Please refer to Modbus abnormality 01)|(% style="width:183px" %)When the instruction is executed
974 |(% style="width:101px" %)368C|(% style="width:462px" %)ModbusTCP slave station fault|(% style="width:186px" %)Continue to run|(% style="width:516px" %)(((
975 Slave returns message: Slave is faulty.
976
977 (Please refer to Modbus abnormality 04)
978 )))|(% style="width:183px" %)When the instruction is executed
979 |(% style="width:101px" %)368D|(% style="width:462px" %)ModbusTCP slave station confirmation|(% style="width:186px" %)Continue to run|(% style="width:516px" %)(((
980 Slave returns message: Slave confirmation.
981
982 (Please refer to Modbus abnormality 05)
983 )))|(% style="width:183px" %)When the instruction is executed
984 |(% style="width:101px" %)368E|(% style="width:462px" %)ModbusTCP protocol currently does not support this instruction|(% style="width:186px" %)Continue to run|(% style="width:516px" %)RS instruction could not be used when set to slave protocol. Please change protocol or close the contact before the RS instruction.|(% style="width:183px" %)When the instruction is executed
985 |(% style="width:101px" %)368F|(% style="width:462px" %)Network port sending timeout|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Contact the technician for the error.|(% style="width:183px" %)When the instruction is executed
986 |(% style="width:101px" %)3690|(% style="width:462px" %)Receiving cache overflow|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Check whether the other device has been sending data.|(% style="width:183px" %)When the instruction is executed
987 |(% style="width:101px" %)36A0|(% style="width:462px" %)ModbusTCP unavailable gateway|(% style="width:186px" %)Continue to run|(% style="width:516px" %)(((
988 Slave returns message: Unavailable gateway.
989
990 (Please refer to Modbus abnormality 0A)
991 )))|(% style="width:183px" %)When the instruction is executed
992 |(% style="width:101px" %)36A1|(% style="width:462px" %)ModbusTCP No response was received from the target device. Generally it means that the device is not on the network.|(% style="width:186px" %)Continue to run|(% style="width:516px" %)(((
993 Slave returns message: The device is not on the network.
994
995 (Please refer to Modbus abnormality 0B)
996 )))|(% style="width:183px" %)When the instruction is executed
997 |(% style="width:101px" %)36C0|(% style="width:462px" %)ModbusTCP transaction identifier error|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Check whether the network is congested and data cannot be received.|(% style="width:183px" %)When the instruction is executed
998 |(% style="width:101px" %)36C1|(% style="width:462px" %)ModbusTCP The server is full of available links|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Check whether SD2702 and SD2703 have too many clients to link.|(% style="width:183px" %)When the instruction is executed
999 |(% style="width:101px" %)36C8|(% style="width:462px" %)The Ethernet protocol stack is running out of space|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Contact the technician for the error.|(% style="width:183px" %)When the instruction is executed
1000 |(% style="width:101px" %)36C9|(% style="width:462px" %)The number of links exceeded the limit|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Check whether the total number of links exceeds the limit.|(% style="width:183px" %)When the instruction is executed
1001 |(% style="width:101px" %)36CA|(% style="width:462px" %)The last sending is not complete|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Use the send completion flag to judge the current send is complete before sending the next one.|(% style="width:183px" %)When the instruction is executed
1002 |(% style="width:101px" %)36CB|(% style="width:462px" %)TCP abnormal write|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Use flag bit device to judge whether the connection is normal. If not, not data is sent. For example, after the closing flag is set,no data is sent.|(% style="width:183px" %)When the instruction is executed
1003 |(% style="width:101px" %)36CC|(% style="width:462px" %)TCP abnormal output|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Contact the technician for the error.|(% style="width:183px" %)When the instruction is executed
1004 |(% style="width:101px" %)36CD|(% style="width:462px" %)The IP address has been used|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Check whether a connection using the same address information exists.|(% style="width:183px" %)When the instruction is executed
1005 |(% style="width:101px" %)36CE|(% style="width:462px" %)The server receiving link error|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Contact the technician for the error.|(% style="width:183px" %)When the instruction is executed
1006 |(% style="width:101px" %)36CF|(% style="width:462px" %)TCP receiving buffer overflow|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Contact the technician for the error.|(% style="width:183px" %)When the instruction is executed
1007 |(% style="width:101px" %)36D0|(% style="width:462px" %)TCP connection failed|(% style="width:186px" %)Continue to run|(% style="width:516px" %)The TCP client may be enabled when the network cable is not connected.|(% style="width:183px" %)When the instruction is executed
1008 |(% style="width:101px" %)36D1|(% style="width:462px" %)Abnormal when closing the link initiative|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Contact the technician for the error.|(% style="width:183px" %)When the instruction is executed
1009 |(% style="width:101px" %)36D2|(% style="width:462px" %)An abnormal shutdown occurred inside the protocol stack|(% style="width:186px" %)Continue to run|(% style="width:516px" %)It may be closed because of no response for a long time. Check whether the opposite end is online, and whether it could be pinged.|(% style="width:183px" %)When the instruction is executed
1010 |(% style="width:101px" %)36D3|(% style="width:462px" %)Initiate an RST link on the opposite end|(% style="width:186px" %)Continue to run|(% style="width:516px" %)(((
1011 1. Check whether the opposite end initiates an abnormal shutdown.
1012 1. As a client, the number of links on the opposite end is full or the port on the opposite end is notopened.
1013 )))|(% style="width:183px" %)When the instruction is executed
1014 |(% style="width:101px" %)36D4|(% style="width:462px" %)A single-ended shutdown of the protocol stack occurs|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Contact the technician for the error.|(% style="width:183px" %)When the instruction is executed
1015 |(% style="width:101px" %)36D5|(% style="width:462px" %)There is an IP address conflict|(% style="width:186px" %)Continue to run|(% style="width:516px" %)There are the same IP devices in the LAN, please change the IP address.|(% style="width:183px" %)When the instruction is executed
1016 |(% style="width:101px" %)36D6|(% style="width:462px" %)There is an MAC address conflict|(% style="width:186px" %)Continue to run|(% style="width:516px" %)There are the same MAC devices in the LAN, please change the MAC address.|(% style="width:183px" %)When the instruction is executed
1017 |(% style="width:101px" %)36D7|(% style="width:462px" %)TCP sending buffer overflow|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Contact the technician for the error.|(% style="width:183px" %)When the instruction is executed
1018 |(% style="width:101px" %)36D8|(% style="width:462px" %)UDP abnormal connection|(% style="width:186px" %)Continue to run|(% style="width:516px" %)IP address and port number may have been used.|(% style="width:183px" %)When the instruction is executed
1019 |(% style="width:101px" %)36D9|(% style="width:462px" %)UDP sending buffer overflow|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Contact the technician for the error.|(% style="width:183px" %)When the instruction is executed
1020 |(% style="width:101px" %)36DA|(% style="width:462px" %)UDP insufficient memory space when sending|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Contact the technician for the error.|(% style="width:183px" %)When the instruction is executed
1021 |(% style="width:101px" %)36DB|(% style="width:462px" %)UDP failed to send|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Contact the technician for the error.|(% style="width:183px" %)When the instruction is executed
1022 |(% style="width:101px" %)36DC|(% style="width:462px" %)UDP memory release failure|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Contact the technician for the error.|(% style="width:183px" %)When the instruction is executed
1023 |(% style="width:101px" %)36DD|(% style="width:462px" %)UDP receiving buffer overflow|(% style="width:186px" %)Continue to run|(% style="width:516px" %)The data length that UDP received exceeds the limit value 512.|(% style="width:183px" %)When the instruction is executed
1024 |(% style="width:101px" %)4084|(% style="width:462px" %)The data input in the application instruction exceeds the specified range.|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Modify application instruction parameter.|(% style="width:183px" %)When the application instruction is executed
1025 |(% style="width:101px" %)4085|(% style="width:462px" %)The output result in the read application instruction exceeds the device range.|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Modify application instruction parameter.|(% style="width:183px" %)When the application instruction is executed
1026 |(% style="width:101px" %)4086|(% style="width:462px" %)The output result in the read application instruction exceeds the device range.|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Modify application instruction parameter.|(% style="width:183px" %)When the application instruction is executed
1027 |(% style="width:101px" %)5080|(% style="width:462px" %)The Ethernet socket is already linked and could not be opened again|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Check whether the SOCOPEN instruction is executed repeatedly.|(% style="width:183px" %)When the application instruction is executed
1028 |(% style="width:101px" %)5081|(% style="width:462px" %)The Ethernet socket is not opened and could not be operated|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Check whether the connected bit of SOCOPEN instruction (d2) parameter is set.|(% style="width:183px" %)When the application instruction is executed
1029 |(% style="width:101px" %)5082|(% style="width:462px" %)The socket ID that Ethernet instruction inputs exceeds the range|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Modify application instruction parameter.|(% style="width:183px" %)When the application instruction is executed
1030 |(% style="width:101px" %)5083|(% style="width:462px" %)Failed to create TCP server|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Check whether the link is full.|(% style="width:183px" %)When the application instruction is executed
1031 |(% style="width:101px" %)5084|(% style="width:462px" %)Failed to create links|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Check whether the link is full.|(% style="width:183px" %)When the application instruction is executed
1032 |(% style="width:101px" %)5086|(% style="width:462px" %)The socket ID used by Ethernet instruction is not configured in the host computer or is not enabled after configuration|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Check the Ethernet configuration of the host computer.|(% style="width:183px" %)When the application instruction is executed
1033 |(% style="width:101px" %)5087|(% style="width:462px" %)SOCRECV instruction reception timeout|(% style="width:186px" %)Continue to run|(% style="width:516px" %)(((
1034 1. Check whether the network connection is normal.
1035 1. Check whether the network opposite end has data sent.
1036 )))|(% style="width:183px" %)When the application instruction is executed
1037 |(% style="width:101px" %)5088|(% style="width:462px" %)The socket specified by SOCMTCP instruction uses the configuration mode of non-TCP client|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Check the Ethernet configuration of the host computer.|(% style="width:183px" %)When the application instruction is executed
1038 |(% style="width:101px" %)5089|(% style="width:462px" %)When Ethernet socket configures a TCP server, specify the local port as 502|(% style="width:186px" %)Continue to run|(% style="width:516px" %)The port 502 is occupied by the system. Please modify the local port number.|(% style="width:183px" %)When the application instruction is executed
1039 |(% style="width:101px" %)508A|(% style="width:462px" %)The UDP port is set to 1092|(% style="width:186px" %)Continue to run|(% style="width:516px" %)The UDP port 1092 is occupied by the system and could not be used. Please modify the local port number.|(% style="width:183px" %)When the application instruction is executed
1040 |(% style="width:101px" %)5090|(% style="width:462px" %)Abnormal network cable connection|(% style="width:186px" %)Continue to run|(% style="width:516px" %)Check whether the network cable is connected|(% style="width:183px" %)When the application instruction is executed