Skip to Content

Wiki source code of 13 Ethernet Communication

Last modified by Wecon on 2025/09/03 21:03
Show last authors
1 == **Overview of Ethernet** ==
2
3 ----
4
5 === **IP Address Concept** ===
6
7 ----
8
9 IP addresses consist of network addresses and host addresses, which are distinguished by subnet masks. If a programming device (such as a PC) needs to be connected to a factory LAN via a network card, the programming device and the PLC must be in the same subnet. The IP address is combined with a subnet mask to specify the subnet of the device.
10
11 |=**No.**|=(% colspan="3" %)**Network equipment 1**|=(% colspan="3" %)**Network equipment 2**|=**Network connection**
12 | |**IP**|**Subnet mask**|**Network address**|**IP**|**Subnet mask**|**Network address**|
13 |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
14 |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
15 |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
16
17 When logical operation of IP address and subnet mask is performed, the network address can be calculated. If the addresses are in the same network, it means that communication can be carried out. For instance:
18
19 === **Setting PC Network Address** ===
20
21 ----
22
23 1.Open the control panel->Network and Internet->Network and sharing center;
24
25 (% style="text-align:center" %)
26 [[image:1709800172136-122.png]]
27
28 2.Click on the local link->Attributes->Internet Protocol Version 4;
29
30 3.Set the IP address and subnet mask that are within the same network address as PLC. Note that IP addresses that have been used in LAN cannot 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 in the following figure can be set to connect the PC to PLC.
31
32 (% style="text-align:center" %)
33 [[image:1709800197035-940.png]]
34
35 === **Testing Network Connection Status** ===
36
37 ----
38
39 Test the connection status of PC and PLC via ping command.
40
41 1.win+R key, input cmd;
42
43 (% style="text-align:center" %)
44 [[image:1709800277099-298.png]]
45
46 2.If PLC’s IP address is 192.168.8.8;
47
48 (1)Enter ping 192.168. 8.8 command and press Enter. If 100% missing is displayed, it means that it cannot be connected with PLC.
49
50 (% style="text-align:center" %)
51 [[image:1709800385874-944.png]]
52
53 (2)Enter ping 192.168. 8.8 command and press Enter. If 0% missing is displayed, it means that it can be connected with PLC.
54
55 (% style="text-align:center" %)
56 [[image:1709800404587-687.png]]
57
58 (3)“ping network equipment ip”command can only be used for four times . If it needs to further perform ping , please use the command “ping network equipmentip -t”, as shown in following figure: 
59
60
61 (% style="text-align:center" %)
62 [[image:1709800414375-820.png]]
63
64
65 === **Ethernet connection between PLC Editor2 and PLC** ===
66
67 ----
68
69 ~1. Transmission settings->Ethernet configuration->Input the IP address of PLC; (note: the address of the network card should be in the same network segment with PLC)
70
71 (% style="text-align:center" %)
72 [[image:1709800528216-231.png]]
73
74 2.Click the communication test to confirm the communication;
75
76 (% style="text-align:center" %)
77 [[image:1709800557135-786.png]]
78
79 3.After successful connection, click “select” to operate PLC.
80
81 === **Ethernet Search Function of PLC Editor 2** ===
82
83 ----
84
85 ~1. Transmission settings->Network card selection->Equipment search (note: the address of the network card should be in the same network segment with PLC), select “connect PLC” at 1 or the network card that is within the same network segment with PLC, and click 2 to search PLC equipment in LAN.
86
87 (% style="text-align:center" %)
88 [[image:1709800659995-499.png]]
89
90 2.Search interface is shown as follows. Click search to display the PLC equipment in the LAN, select the corresponding equipment and click OK to communicate.
91
92 (% style="text-align:center" %)
93 [[image:1709800676198-944.png]]
94
95 3.IP address at 1 is automatically filled in. Click the communication test to test whether the communication is normal. if it is normal, click “select” button to complete the connection configuration.
96
97 (% style="text-align:center" %)
98 [[image:1709800686490-665.png]]
99
100
101 == **Ethernet Configuration** ==
102
103 ----
104
105 === **IP Address Setting** ===
106
107 ----
108
109 (1) Setting via programming software
110
111 Project management->parameters->PLC parameter->Ethernet configuration.
112
113 After modification, check the parameter items through PLC download; after download, click STOP->RUN to complete.
114
115 (% class="box infomessage" %)
116 (((
117 **Note: **Modbus TCP Server supports maximum connections, which is used to set the maximum number of external Modbus TCP clients that can be connected to PLC simultaneously, with the range being 2~~8.
118 )))
119
120 (% style="text-align:center" %)
121 [[image:1709800796514-672.png]]
122
123
124 (2) Setting via special device
125
126 Write IP address, subnet mask and default gateway in SD2680~~SD2691;
127
128 When SM2680 is set as ON, open static IP function;
129
130 When SM2683 is set as ON, the sign IP can be modified;
131
132 STOP->RUN or the new IP address takes effect after power-on again.
133
134 |=(% style="width: 122px;" %)**SM sign**|=(% style="width: 169px;" %)**Name**|=(% style="width: 396px;" %)**Content**|=(% style="width: 60px;" %)**R/W**|=(% style="width: 93px;" %)**SD label**|=**Name**
135 |(% style="width:122px" %)SM2680|(% style="width:169px" %)Statically set IP switch|(% style="width:396px" %)(((
136 ON: static setting
137
138 OFF: The IP address is automatically configured by router DHCP, and the IP cannot be modified
139
140 STOP->RUN
141 )))|(% style="width:60px" %)R/W|(% style="width:93px" %)SD2680|The first byte of the IP address
142 |(% style="width:122px" %)SM2681|(% style="width:169px" %)Display current network information|(% style="width:396px" %)Refresh the current IP gateway subnet mask after being set as ON. OFF after refresh is completed.|(% style="width:60px" %)R/W|(% style="width:93px" %)SD2681|The second byte of the ip address
143 |(% style="width:122px" %)SM2682|(% style="width:169px" %)Display current MAC information (reserved)|(% style="width:396px" %)Refresh the current MAC after being set as ON. OFF after refresh is completed.|(% style="width:60px" %)R/W|(% style="width:93px" %)SM2682|The third byte of the ip address
144 |(% style="width:122px" %)SM2683|(% style="width:169px" %)IP, subnet mask, gateway modification sign|(% style="width:396px" %)(((
145 ON: can be modified
146
147 OFF: cannot be modified
148
149 (When being set as ON, STOP->RUN; it can be automatically changed to OFF after modification)
150 )))|(% style="width:60px" %)R/W|(% style="width:93px" %)SD2683|The fourth byte of the ip address
151 |(% style="width:122px" %)SM2684|(% style="width:169px" %) |(% style="width:396px" %) |(% style="width:60px" %) |(% style="width:93px" %)SD2684|The first byte of subnet mask
152 |(% style="width:122px" %)SM2685|(% style="width:169px" %) |(% style="width:396px" %) |(% style="width:60px" %) |(% style="width:93px" %)SD2685|The second byte of subnet mask
153 |(% style="width:122px" %)SM2686|(% style="width:169px" %) |(% style="width:396px" %) |(% style="width:60px" %) |(% style="width:93px" %)SD2686|The third byte of subnet mask
154 |(% style="width:122px" %)SM2687|(% style="width:169px" %) |(% style="width:396px" %) |(% style="width:60px" %) |(% style="width:93px" %)SD2687|The fourth byte of subnet mask
155 |(% style="width:122px" %)SM2688|(% style="width:169px" %) |(% style="width:396px" %) |(% style="width:60px" %) |(% style="width:93px" %)SD2688|Default gateway first byte
156 |(% style="width:122px" %)SM2689|(% style="width:169px" %) |(% style="width:396px" %) |(% style="width:60px" %) |(% style="width:93px" %)SD2689|Default gateway second byte
157 |(% style="width:122px" %)SM2690|(% style="width:169px" %) |(% style="width:396px" %) |(% style="width:60px" %) |(% style="width:93px" %)SD2690|Default gateway third byte
158 |(% style="width:122px" %)SM2691|(% style="width:169px" %) |(% style="width:396px" %) |(% style="width:60px" %) |(% style="width:93px" %)SD2691|Default gateway fourth byte
159
160 === **TCP Protocol Concept** ===
161
162 ----
163
164 TCP protocol is a Transport Control Protocol, which is a connection-oriented and reliable transport layer protocol. Connection-oriented means that a normal TCP transmission needs to be completed by establishing a specific virtual circuit connection between TCP client and TCP server. To transmit data over TCP, a connection must be established between hosts at both ends.
165
166
167 == **List of Ethernet-related Special Devices** ==
168
169 ----
170
171 |=(% style="width: 81px;" %)**SM sign**|=(% style="width: 208px;" %)**Name**|=**Content**|=**R/W**|=**Power-down save**
172 |(% style="width:81px" %)SM2681|(% style="width:208px" %)Display current network information|Refresh the current IP, subnet mask and default gateway after being set as ON; and then being set as OFF upon completion of refresh|R/W|×
173 |(% style="width:81px" %)SM2682|(% style="width:208px" %)Display current MAC information|Refresh the current MAC after being set as ON. OFF after refresh is completed.|R/W|×
174 |(% style="width:81px" %)SM2683|(% style="width:208px" %)IP, subnet mask, gateway modification sign|(((
175 ON: can be modified
176
177 OFF: cannot be modified
178
179 (When being set as ON, STOP->RUN; it can be automatically changed to OFF after modification)
180 )))|R/W|√
181 |(% style="width:81px" %)SM2684|(% style="width:208px" %)Network card connection status|(((
182 ON: network connected
183
184 OFF: network not connected; check if the network cable is connected
185 )))|R|√
186 |(% style="width:81px" %)SM2692|(% style="width:208px" %)MAC address modification sign|(((
187 ON: can be modified
188
189 OFF: cannot be modified
190
191 (When being set as ON, STOP->RUN; it can be automatically changed to OFF after modification)
192 )))|R/W|√
193 |(% style="width:81px" %)SM2700|(% style="width:208px" %)Modbus TCP keep-alive mechanism|(((
194 ON: Open
195
196 OFF: Close (default)
197 )))|R/W|√
198 |(% style="width:81px" %)SM2701|(% style="width:208px" %)Forced shutdown of Modbus TCP server|(((
199 ON: Open
200
201 OFF: Close (default) (after being enabled, it will be automatically changed into OFF after shutdown)
202 )))|R/W|×
203 |(% style="width:81px" %)SM2710|(% style="width:208px" %)Ethernet error sign|(((
204 ON: there is an Ethernet error, please check SD2710 and SD2711
205
206 OFF: there is no Ethernet error
207 )))|R|×
208 |(% style="width:81px" %)SM2740|(% style="width:208px" %)ModbusTCP server connection status 1|(((
209 ON: Client side has been connected
210
211 OFF: Client side hasn’t been connected
212 )))|R|×
213 |(% style="width:81px" %)SM2760|(% style="width:208px" %)ModbusTCP server connection status 2|(((
214 ON: Client side has been connected
215
216 OFF: Client side hasn’t been connected
217 )))|R|×
218 |(% style="width:81px" %)SM2780|(% style="width:208px" %)ModbusTCP server connection status 3|(((
219 ON: Client side has been connected
220
221 OFF: Client side hasn’t been connected
222 )))|R|×
223 |(% style="width:81px" %)SM2800|(% style="width:208px" %)ModbusTCP server connection status 4|(((
224 ON: Client side has been connected
225
226 OFF: Client side hasn’t been connected
227 )))|R|×
228 |(% style="width:81px" %)SM2820|(% style="width:208px" %)ModbusTCP server connection status 5|(((
229 ON: Client side has been connected
230
231 OFF: Client side hasn’t been connected
232 )))|R|×
233 |(% style="width:81px" %)SM2840|(% style="width:208px" %)ModbusTCP server connection status 6|(((
234 ON: Client side has been connected
235
236 OFF: Client side hasn’t been connected
237 )))|R|×
238 |(% style="width:81px" %)SM2860|(% style="width:208px" %)ModbusTCP server connection status 7|(((
239 ON: Client side has been connected
240
241 OFF: Client side hasn’t been connected
242 )))|R|×
243 |(% style="width:81px" %)SM2880|(% style="width:208px" %)ModbusTCP server connection status 8|(((
244 ON: Client side has been connected
245
246 OFF: Client side hasn’t been connected
247 )))|R|×
248
249 |=(% style="width: 91px;" %)**SD label**|=(% style="width: 304px;" %)**Name**|=**Content**|=**R/W**|=**Power-down save**
250 |(% style="width:91px" %)SD2680|(% style="width:304px" %)The first byte of the IP address|Local IP address|R/W|√
251 |(% style="width:91px" %)SD2681|(% style="width:304px" %)The second byte of the ip address| |R/W|√
252 |(% style="width:91px" %)SM2682|(% style="width:304px" %)The third byte of the ip address| |R/W|√
253 |(% style="width:91px" %)SD2683|(% style="width:304px" %)The fourth byte of the ip address| |R/W|√
254 |(% style="width:91px" %)SD2684|(% style="width:304px" %)The first byte of subnet mask|Local subnet mask|R/W|√
255 |(% style="width:91px" %)SD2685|(% style="width:304px" %)The second byte of subnet mask| |R/W|√
256 |(% style="width:91px" %)SD2686|(% style="width:304px" %)The third byte of subnet mask| |R/W|√
257 |(% style="width:91px" %)SD2687|(% style="width:304px" %)The fourth byte of subnet mask| |R/W|√
258 |(% style="width:91px" %)SD2688|(% style="width:304px" %)Default gateway first byte|Local default gateway|R/W|√
259 |(% style="width:91px" %)SD2689|(% style="width:304px" %)Default gateway second byte| |R/W|√
260 |(% style="width:91px" %)SD2690|(% style="width:304px" %)Default gateway third byte| |R/W|√
261 |(% style="width:91px" %)SD2691|(% style="width:304px" %)Default gateway fourth byte| |R/W|√
262 |(% style="width:91px" %)SD2692|(% style="width:304px" %)The first byte of MAC address|Local MAC address|R/W|√
263 |(% style="width:91px" %)SD2693|(% style="width:304px" %)The second byte of MAC address| |R/W|√
264 |(% style="width:91px" %)SD2694|(% style="width:304px" %)The third byte of MAC address| |R/W|√
265 |(% style="width:91px" %)SD2695|(% style="width:304px" %)The fourth byte of MAC address| |R/W|√
266 |(% style="width:91px" %)SD2696|(% style="width:304px" %)The fifth byte of MAC address| |R/W|√
267 |(% style="width:91px" %)SD2697|(% style="width:304px" %)The sixth byte of MAC address| |R/W|√
268 |(% style="width:91px" %)SD2700|(% style="width:304px" %)Communication speed display|(((
269 0: 100Mbps/half duplex
270
271 1: 100Mbps/full duplex
272
273 2: 10Mbps/half duplex
274
275 3: 10Mbps/full duplex
276 )))|R|×
277 |(% style="width:91px" %)SD2702|(% style="width:304px" %)The modbusTCP server supports the maximum number of connections|Local modbusTCP server supports the maximum number of clients to make connections at the same time|R/W|×
278 |(% style="width:91px" %)SD2703|(% style="width:304px" %)Modbus TCP connections|Local Modbus TCP connections|R|×
279 |(% style="width:91px" %)SD2710|(% style="width:304px" %)Error code|Ethernet error code|R|×
280 |(% style="width:91px" %)SD2711|(% style="width:304px" %)Socket ID of the error|(((
281 -1: system default Modbus TCP server
282
283 0~~5: Customer custom socket error
284 )))|R|×
285 |(% style="width:91px" %)SD2720|(% style="width:304px" %)Input the low bit of the number of ping request|External input ping command count|R|×
286 |(% style="width:91px" %)SD2721|(% style="width:304px" %)Input the high bit of the number of ping request| |R|×
287 |(% style="width:91px" %)SD2722|(% style="width:304px" %)Input the low bit of the number of ping response|Number of replies after receiving external ping command|R|×
288 |(% style="width:91px" %)SD2723|(% style="width:304px" %)Input the high bit of the number of ping response| |R|×
289 |(% style="width:91px" %)SD2724|(% style="width:304px" %)Output the low bit of the number of ping request|Send ping command count|R|×
290 |(% style="width:91px" %)SD2725|(% style="width:304px" %)Output the high bit of the number of ping request| |R|×
291 |(% style="width:91px" %)SD2726|(% style="width:304px" %)Output the low order of the number of ping response|Number of replies after receiving sent ping command|R|×
292 |(% style="width:91px" %)SD2727|(% style="width:304px" %)Output the high bit of the number of ping response| |R|×
293 |(% style="width:91px" %)SD2728|(% style="width:304px" %)Number of arp packets sent|Count of number of arp packets sent|R|×
294 |(% style="width:91px" %)SD2729|(% style="width:304px" %)Number of arp packets received|Count of number of arp packets received|R|×
295 |(% style="width:91px" %)SD2730|(% style="width:304px" %)Number of ip packets sent|Count of number of ip packets sent|R|×
296 |(% style="width:91px" %)SD2731|(% style="width:304px" %)Number of ip packets received|Count of number of arp packets received|R|×
297 |(% style="width:91px" %)SD2732|(% style="width:304px" %)Number of tcp packets sent|Count of number of tcp packets sent|R|×
298 |(% style="width:91px" %)SD2733|(% style="width:304px" %)The number of tcp packets received|Count of number of tcp packets received|R|×
299 |(% style="width:91px" %)SD2734|(% style="width:304px" %)Number of udp packets sent|Count of number of udp packets sent|R|×
300 |(% style="width:91px" %)SD2735|(% style="width:304px" %)Number of udp packets received|Count of number of udp packets received|R|×
301 |(% style="width:91px" %)
302 SD2740|(% style="width:304px" %)Connection 1 local port number|Connection information and error information about the first Modbus TCP client’s connection to the PLC.|R|×
303 |(% style="width:91px" %)SD2741|(% style="width:304px" %)Connection 1 IP address first byte| |R|×
304 |(% style="width:91px" %)SD2742|(% style="width:304px" %)Connection 1 IP address second byte| |R|×
305 |(% style="width:91px" %)SD2743|(% style="width:304px" %)Connection 1 IP address third byte| |R|×
306 |(% style="width:91px" %)SD2744|(% style="width:304px" %)Connection 1 IP address fourth byte| |R|×
307 |(% style="width:91px" %)SD2745|(% style="width:304px" %)Connection 1 peer port number| |R|×
308 |(% style="width:91px" %)SD2746|(% style="width:304px" %)Reserved| |R|×
309 |(% style="width:91px" %)SD2747|(% style="width:304px" %)Reserved| | |
310 |(% style="width:91px" %)SD2748|(% style="width:304px" %)Connection 1 error code| |R|×
311 |(% style="width:91px" %)SD2749|(% style="width:304px" %)Connection 1 error communication times low word| |R|×
312 |(% style="width:91px" %)SD2750|(% style="width:304px" %)Connection 1 error communication times high word| |R|×
313 |(% style="width:91px" %)SD2760|(% style="width:304px" %)Connection 2 local port number|Connection information and error information about the second Modbus TCP client’s connection to the PLC.|R|×
314 |(% style="width:91px" %)SD2761|(% style="width:304px" %)Connection 2 IP address first byte| |R|×
315 |(% style="width:91px" %)SD2762|(% style="width:304px" %)Connection 2 IP address second byte| |R|×
316 |(% style="width:91px" %)SD2763|(% style="width:304px" %)Connection 2 IP address third byte| |R|×
317 |(% style="width:91px" %)SD2764|(% style="width:304px" %)Connection 2 IP address fourth byte| |R|×
318 |(% style="width:91px" %)SD2765|(% style="width:304px" %)Connection 2 peer port number| |R|×
319 |(% style="width:91px" %)SD2766|(% style="width:304px" %)Reserved| |R|×
320 |(% style="width:91px" %)SD2767|(% style="width:304px" %)Reserved| | |
321 |(% style="width:91px" %)SD2768|(% style="width:304px" %)Connection 2 error code| |R|×
322 |(% style="width:91px" %)SD2769|(% style="width:304px" %)Connection 2 error communication times low word| |R|×
323 |(% style="width:91px" %)SD2770|(% style="width:304px" %)Connection 2 error communication times high word| |R|×
324 |(% style="width:91px" %)SD2780|(% style="width:304px" %)Connection 3 local port number|Connection information and error information about the third Modbus TCP client’s connection to the PLC.|R|×
325 |(% style="width:91px" %)SD2781|(% style="width:304px" %)Connection 3 IP address first byte| |R|×
326 |(% style="width:91px" %)SD2782|(% style="width:304px" %)Connection 3 IP address second byte| |R|×
327 |(% style="width:91px" %)SD2783|(% style="width:304px" %)Connection 3 IP address third byte| |R|×
328 |(% style="width:91px" %)SD2784|(% style="width:304px" %)Connection 3 IP address fourth byte| |R|×
329 |(% style="width:91px" %)SD2785|(% style="width:304px" %)Connection 3 peer port number| |R|×
330 |(% style="width:91px" %)SD2786|(% style="width:304px" %)Reserved| |R|×
331 |(% style="width:91px" %)SD2787|(% style="width:304px" %)Reserved| | |
332 |(% style="width:91px" %)SD2788|(% style="width:304px" %)Connection 3 error code| |R|×
333 |(% style="width:91px" %)SD2789|(% style="width:304px" %)Connection 3 error communication times low word| |R|×
334 |(% style="width:91px" %)SD2780|(% style="width:304px" %)Connection 3 error communication times high word| |R|×
335 |(% style="width:91px" %)SD2800|(% style="width:304px" %)Connection 4 local port number|Connection information and error information about the fourth Modbus TCP client’s connection to the PLC.|R|×
336 |(% style="width:91px" %)SD2801|(% style="width:304px" %)Connection 4 IP address first byte| |R|×
337 |(% style="width:91px" %)SD2802|(% style="width:304px" %)Connection 4 IP address second byte| |R|×
338 |(% style="width:91px" %)SD2803|(% style="width:304px" %)Connection 4 IP address third byte| |R|×
339 |(% style="width:91px" %)SD2804|(% style="width:304px" %)Connection 4 IP address fourth byte| |R|×
340 |(% style="width:91px" %)SD2805|(% style="width:304px" %)Connection 4 peer port number| |R|×
341 |(% style="width:91px" %)SD2806|(% style="width:304px" %)Reserved| |R|×
342 |(% style="width:91px" %)SD2807|(% style="width:304px" %)Reserved| | |
343 |(% style="width:91px" %)
344 SD2808|(% style="width:304px" %)Connection 4 error code|Error information about the fourth Modbus TCP client’s connection to the PLC.|R|×
345 |(% style="width:91px" %)SD2809|(% style="width:304px" %)Connection 4 error communication times low word| |R|×
346 |(% style="width:91px" %)SD2810|(% style="width:304px" %)Connection 4 error communication times high word| |R|×
347 |(% style="width:91px" %)SD2820|(% style="width:304px" %)Connection 5 local port number|Connection information and error information about the fifth Modbus TCP client’s connection to the PLC.|R|×
348 |(% style="width:91px" %)SD2821|(% style="width:304px" %)Connection 5 IP address first byte| |R|×
349 |(% style="width:91px" %)SD2822|(% style="width:304px" %)Connection 5 IP address second byte| |R|×
350 |(% style="width:91px" %)SD2823|(% style="width:304px" %)Connection 5 IP address third byte| |R|×
351 |(% style="width:91px" %)SD2824|(% style="width:304px" %)Connection 5 IP address fourth byte| |R|×
352 |(% style="width:91px" %)SD2825|(% style="width:304px" %)Connection 5 peer port number| |R|×
353 |(% style="width:91px" %)SD2826|(% style="width:304px" %)Reserved| |R|×
354 |(% style="width:91px" %)SD2827|(% style="width:304px" %)Reserved| | |
355 |(% style="width:91px" %)SD2828|(% style="width:304px" %)Connection 5 error code| |R|×
356 |(% style="width:91px" %)SD2829|(% style="width:304px" %)Connection 5 error communication times low word| |R|×
357 |(% style="width:91px" %)SD2830|(% style="width:304px" %)Connection 5 error communication times high word| |R|×
358 |(% style="width:91px" %)SD2840|(% style="width:304px" %)Connection 6 local port number|Connection information and error information about the sixth Modbus TCP client’s connection to the PLC.|R|×
359 |(% style="width:91px" %)SD2841|(% style="width:304px" %)Connection 6 IP address first byte| |R|×
360 |(% style="width:91px" %)SD2842|(% style="width:304px" %)Connection 6 IP address second byte| |R|×
361 |(% style="width:91px" %)SD2843|(% style="width:304px" %)Connection 6 IP address third byte| |R|×
362 |(% style="width:91px" %)SD2844|(% style="width:304px" %)Connection 6 IP address fourth byte| |R|×
363 |(% style="width:91px" %)SD2845|(% style="width:304px" %)Connection 6 peer port number| |R|×
364 |(% style="width:91px" %)SD2846|(% style="width:304px" %)Reserved| |R|×
365 |(% style="width:91px" %)SD2847|(% style="width:304px" %)Reserved| | |
366 |(% style="width:91px" %)SD2848|(% style="width:304px" %)Connection 6 error code| |R|×
367 |(% style="width:91px" %)SD2849|(% style="width:304px" %)Connection 6 error communication times low word| |R|×
368 |(% style="width:91px" %)SD2850|(% style="width:304px" %)Connection 6 error communication times high word| |R|×
369 |(% style="width:91px" %)SD2860|(% style="width:304px" %)Connection 7 local port number|Connection information and error information about the seventh Modbus TCP client’s connection to the PLC.|R|×
370 |(% style="width:91px" %)SD2861|(% style="width:304px" %)Connection 7 IP address first byte| |R|×
371 |(% style="width:91px" %)SD2862|(% style="width:304px" %)Connection 7 IP address second byte| |R|×
372 |(% style="width:91px" %)SD2863|(% style="width:304px" %)Connection 7 IP address third byte| |R|×
373 |(% style="width:91px" %)SD2864|(% style="width:304px" %)Connection 7 IP address fourth byte| |R|×
374 |(% style="width:91px" %)SD2865|(% style="width:304px" %)Connection 7 peer port number| |R|×
375 |(% style="width:91px" %)SD2866|(% style="width:304px" %)Reserved| |R|×
376 |(% style="width:91px" %)SD2867|(% style="width:304px" %)Reserved| | |
377 |(% style="width:91px" %)SD2868|(% style="width:304px" %)Connection 7 error code| |R|×
378 |(% style="width:91px" %)SD2869|(% style="width:304px" %)Connection 7 error communication times low word| |R|×
379 |(% style="width:91px" %)SD2870|(% style="width:304px" %)Connection 7 error communication times high word| |R|×
380 |(% style="width:91px" %)SD2880|(% style="width:304px" %)Connection 8 local port number|Connection information and error information about the eighth Modbus TCP client’s connection to the PLC.|R|×
381 |(% style="width:91px" %)SD2881|(% style="width:304px" %)Connection 8 IP address first byte| |R|×
382 |(% style="width:91px" %)SD2882|(% style="width:304px" %)Connection 8 IP address second byte| |R|×
383 |(% style="width:91px" %)SD2883|(% style="width:304px" %)Connection 8 IP address third byte| |R|×
384 |(% style="width:91px" %)SD2884|(% style="width:304px" %)Connection 8 IP address fourth byte| |R|×
385 |(% style="width:91px" %)SD2885|(% style="width:304px" %)Connection 8 peer port number| |R|×
386 |(% style="width:91px" %)
387 SD2866|(% style="width:304px" %)Reserved|Connection information and error information about the eighth Modbus TCP client’s connection to the PLC.| |
388 |(% style="width:91px" %)SD2867|(% style="width:304px" %)Reserved| |R|×
389 |(% style="width:91px" %)SD2888|(% style="width:304px" %)Connection 8 error code| |R|×
390 |(% style="width:91px" %)SD2889|(% style="width:304px" %)Connection 8 error communication times low word| |R|×
391 |(% style="width:91px" %)SD2890|(% style="width:304px" %)Connection 8 error communication times high word| |R|×
392
393
394 == **List of Ethernet Operation Error Codes** ==
395
396 ----
397
398 |=**Error code**|=**Description**|=**Action**|=**Processing approach**|=**Test time**
399 |3680|Ethernet data reception error|Continue to run|Check whether there is any interference in the environment|When the command is executed
400 |3681|Ethernet data reception timeout|Continue to run|(((
401 Check if the network cable is loosened
402
403 ~1. Check whether the network peer is faulty, which results in failure in sending data.
404
405 Check whether the network peer does not respond in time, which results in any delay in data. Under such circumstance, the reception timeout in the socket configuration can be increased.
406 )))|When the command is executed
407 |3684|Modbus TCP station number configuration error|Continue to run|(((
408 Check slave station number setting.
409
410 Check whether there is any problem with the receiving and sending mechanism of slave station.
411 )))|When the command is executed
412 |3685|Modbus TCP send buffer overflow|Continue to run|If this error message appears, please contact technical personnel|When the command is executed
413 |3686|Modbus TCP function code error|Continue to run|Check whether the set function code is a function code supported by PLC|When the command is executed
414 |3687|Modbus TCP address error|Continue to run|Check whether the slave station has this address. (Please refer to Modbus exception 02).|When the command is executed
415 |3688|Modbus TCP length error|Continue to run|Check whether the communication length exceeds the Modbus range|When the command is executed
416 |3689|Modbus TCP data error|Continue to run|(((
417 Check whether parameters of the command are wrong.
418
419 Check whether the set value is supported by the slave station. (Please refer to Modbus exception 03).
420 )))|When the command is executed
421 |368A|Modbus TCP slave is busy|Continue to run|Message returned from slave station: Slave station is busy. (Please refer to Modbus exception 06).|When the command is executed
422 |368B|Modbus TCP slave station does not support function code|Continue to run|Check whether this function code is supported by the slave station. (Please refer to Modbus exception 01).|When the command is executed
423 |368C|Modbus TCP slave failure|Continue to run|Message returned from slave station: Slave station failed, please check whether slave station failed. (Please refer to Modbus exception 04).|When the command is executed
424 |368D|Modbus TCP slave confirmation|Continue to run|Message returned from slave station: slave station confirmation. (Please refer to Modbus exception 05).|When the command is executed
425 |368E|(((
426 The current protocol of Modbus TCP does not support this command
427
428 Instruction
429 )))|Continue to run|The RS command cannot be used when the slave protocol is set, please change the protocol or close the contact before the RS command|When the command is executed
430 |368F|Network port send timeout|Continue to run|If this error message appears, please contact technical personnel|When the command is executed
431 |3690|Receive buffer overflow|Continue to run|Check if the other device is sending data all the time|When the command is executed
432 |36A0|Unavailable gateway for Modbus TCP|Continue to run|Message returned from the slave station: no available gateway. (Please refer to Modbus exception 0A).|When the command is executed
433 |36A1|Modbus TCP indicates that no response was obtained from the target device. It usually means the device is not on the network.|Continue to run|(((
434 Message returned from the slave station: The device is not in the network.
435
436 (Please refer to Modbus exception 0B)
437 )))|When the command is executed
438 |36C0|ModbusTCP transaction identifier error|Continue to run|Check if there is network congestion and data can not be received in time.|When the command is executed
439 |36C1|Modbus TCP server available links are full|Continue to run|Check if SD2702 and SD2703 have too many clients to link|When the command is executed
440 |36C8|Insufficient space in the Ethernet stack|Continue to run|If this error message appears, please contact technical personnel|When the command is executed
441 |36C9|Number of connections exceeds the limit|Continue to run|Confirm whether the total number of connections exceeds the limit|When the command is executed
442 |36CA|The last send is not completed|Continue to run|Use the sending completion sign to determine that the current sending is completed, and then send the next one|When the command is executed
443 |36CB|TCP write exception|Continue to run|Use the sign bit device to judge whether the current connection status is normal. If it is not normal, no data transmission will be performed. For example, after the closing sign is set, data transmission will not be performed.|When the command is executed
444 |36CC|TCP output exception|Continue to run|If this error message appears, please contact technical personnel|When the command is executed
445 |36CD|IP address is used|Continue to run|Please check if a connection exists with the same address information|When the command is executed
446 |36CE|Error in server’s acceptance of connection|Continue to run|If this error message appears, please contact technical personnel|When the command is executed
447 |36CF|TCP receive buffer overflow|Continue to run|If this error message appears, please contact technical personnel|When the command is executed
448 |36D0|TCP link failed|Continue to run|It may be caused by opening the TCP client when the network cable is not connected.|When the command is executed
449 |36D1|Exception when actively closing the connection|Continue to run|If this error message appears, please contact technical personnel|When the command is executed
450 |36D2|Abnormal shutdown occurred inside the protocol stack|Continue to run|May be shut down due to no answering for a long time. Check whether the peer is online and can ping.|When the command is executed
451 |36D3|The peer initiates an RST link|Continue to run|1. Check whether the peer initiates abnormal shutdown. 2. As a client, the number of peer connections is full, or the peer port is not open.|When the command is executed
452 |36D4|The protocol stack has a single-ended shutdown|Continue to run|If this error message appears, please contact technical personnel|When the command is executed
453 |36D5|There is an IP address conflict|Continue to run|The same IP device exists in the LAN, please change the IP address|When the command is executed
454 |36D6|There is a MAC address conflict|Continue to run|The same MAC device exists in the LAN, please change the MAC address|When the command is executed
455 |36D7|TCP send buffer overflow|Continue to run|If this error message appears, please contact technical personnel|When the command is executed
456 |36D8|UDP connection exception|Continue to run|IP address or port number may has been used.|When the command is executed
457 |36D9|UDP send buffer overflow|Continue to run|If this error message appears, please contact technical personnel|When the command is executed
458 |36DA|Insufficient memory space when sending UDP|Continue to run|If this error message appears, please contact technical personnel|When the command is executed
459 |36DB|UDP send failed|Continue to run|If this error message appears, please contact technical personnel|When the command is executed
460 |36DC|UDP memory release failed|Continue to run|If this error message appears, please contact technical personnel|When the command is executed
461 |36DD|UDP receive buffer overflow|Continue to run|The length of the data received by UDP exceeds the limit value of 512.|When the command is executed
462 |4084|(((
463 Data beyond the specified range is entered in the application command (for example, parameter 1 is specified as 0~~1,
464
465 setting 2)
466 )))|Continue to run|Modify application command parameters|When the application command is executed
467 |4085|(((
468 The output result of the read application command exceeds the device range.
469
470 (For example, the maximum output of the D device is D7999, but D8000 is used)
471 )))|Continue to run|Modify application command parameters|When the application command is executed
472 |4086|(((
473 The output result of the write application command exceeds the device range.
474
475 (For example, the maximum output of the D device is D7999, but D8000 is used)
476 )))|Continue to run|Modify application command parameters|When the application command is executed
477 |5080|The Ethernet socket has been linked and cannot be opened repeatedly.|Continue to run|Check if SOCOPEN command is executed repeatedly|When the application command is executed
478 |5081|Ethernet socket is not open, which results in the failure in operation|Continue to run|Check whether set ON the connected sign bit of the SOCOPEN command (d2) parameter|When the application command is executed
479 |5082|Socket ID input by Ethernet command is out of range.|Continue to run|Modify application command parameters|When the application command is executed
480 |5083|Failed to create TCP server|Continue to run|Check if the connection is full|When the application command is executed
481 |5084|Failed to create link|Continue to run|Check if the connection is full|When the application command is executed
482 |5086|The socket ID used by the Ethernet command is not configured by the upper computer or is not enabled after configuration.|Continue to run|Check the Ethernet configuration of upper computer|When the application command is executed
483 |5087|SOCRECV command reception timeout|Continue to run|(((
484 ~1. Check if the network connection is normal.
485
486 2. Check whether there is data sent by the network peer.
487 )))|When the application command is executed
488 |5088|The SOCMTCP command specifies that the socket uses the configuration mode of a non-TCP client|Continue to run|Check the Ethernet configuration of upper computer|When the application command is executed
489 |5089|When configuring the TCP server for the Ethernet socket, specify the local port as 502|Continue to run|Port 502 has been occupied internally, please modify the local port.|When the application command is executed
490 |508A|The UDP port is specified as 1092|Continue to run|(((
491 UDP port: 1092 is occupied by the system and cannot be used,
492
493 please modify the local port number.
494 )))|When the application command is executed
495 |5090|Network cable connection exception|Continue to run|Check if the network cable is connected|When the application command is executed