Last modified by Karry Zhuang on 2024/07/11 11:58
<
From version < 60.13 >
edited by Xiaoling
on 2023/04/20 10:19
To version < 41.16 >
edited by Xiaoling
on 2022/06/01 14:15
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,5 @@
1 -**Table of Contents:**
1 +(% class="wikigeneratedid" %)
2 + **Contents:**
2 2  
3 3  {{toc/}}
4 4  
... ... @@ -7,89 +7,74 @@
7 7  
8 8  
9 9  
10 -= 1. Introduction =
11 += **1. Introduction** =
11 11  
12 -
13 13  This article provide the examples for RS485-LN to connect to different type of RS485 sensors.
14 14  
15 15  
16 -== 1.1 Example 1: Connect to Leak relay and VFD ==
16 +== **1.1 Example 1: Connect to Leak relay and VFD** ==
17 17  
18 -
19 19  This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-LN to connect to Relay and VFD and communicate with Mobile. The structure is like below:
20 20  
20 +[[image:image-20220527091852-1.png]]
21 21  
22 -[[image:image-20220527091852-1.png||height="547" width="994"]]
22 +Connection
23 23  
24 -**Connection**
25 25  
26 26  
27 -
28 28  [[image:image-20220527091942-2.png]](% style="display:none" %)
29 29  
30 -**Connection**
28 +Connection
31 31  
32 32  
33 -(% style="color:blue" %)**Related documents:**
31 +Related documents:
34 34  
35 -* System Structure:  [[Solar Pump with Dragino>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Relay_VFD/||_mstmutation="1" style="background-color: rgb(255, 255, 255);"]]
36 -
37 -* Explanation on how to integrate to Node-red and to the Mobile Phone, and with link to the Github code:  [[Configure Manual>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Relay_VFD/||_mstmutation="1" style="background-color: rgb(255, 255, 255);"]]
38 -
33 +* [[Solar Pump with Dragino>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Relay_VFD/]] : System Structure
34 +* [[Configure Manual>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Relay_VFD/]] : Explanation on how to integrate to Node-red and to the Mobile Phone, and with link to the Github code.
39 39  * [[Video Demo>>url:https://www.youtube.com/watch?v=TAFZ5eaf-MY&t=6s&ab_channel=XavierFlorensaBerenguer]]
40 40  
41 41  
42 42  
43 -== 1.2 Example 2: Connect to Pulse Counter ==
39 +== **1.2 Example 2: Connect to Pulse Counter** ==
44 44  
45 -
46 46  This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-LN to connect to Pulse Counter and communicate with Mobile. This example and example 2 compose the structure for a farm IoT solution. The structure is like below:
47 47  
43 +[[image:image-20220527092058-3.png]]
48 48  
49 -[[image:image-20220527092058-3.png||height="552" width="905"]]
45 +Connection
50 50  
51 -**Connection**
52 52  
53 53  
49 +[[image:image-20220527092146-4.png]]
54 54  
55 -[[image:image-20220527092146-4.png||height="507" width="906"]]
51 +Connection
56 56  
57 -**Connection**
58 58  
59 -
60 -(% style="color:blue" %)**Related documents:**
61 -
62 -* Configure Document:  [[Pickdata MIO40 water pulse counter to LoRa with Dragino RS485-LN>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Pulse-Counter/||_mstmutation="1"]]
63 -
54 +* [[Pickdata MIO40 water pulse counter to LoRa with Dragino RS485-LN>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Pulse-Counter/]] : Configure Document
64 64  * [[Dragino Solution in Farm>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/&file=Dragino%20on%20Farms.pptx]]
65 65  
57 +== ==
66 66  
59 +== **1.3 Example3: Use RS485-LN with energy meters** ==
67 67  
68 -== 1.3 Example 3: Use RS485-LN with energy meters ==
61 +=== **1.3.1 OverView** ===
69 69  
70 -=== 1.3.1 OverView ===
71 -
72 -
73 73  (((
74 -(% style="color:red" %)**Note**：**The specifications of each energy meter are different, please refer to your own energy meter specifications.**
64 +**Note**：The specifications of each energy meter are different, please refer to your own energy meter specifications.
75 75  )))
76 76  
77 77  (((
78 78  This example describes a single-phase meter.This is the connection between the RS485-LN and the energy meter.
79 -
80 -
81 81  )))
82 82  
83 83  [[image:image-20220527092419-5.png]]
84 84  
85 -**Connection1**
73 +Connection1
86 86  
87 87  
88 88  
89 89  (((
90 -(% style="color:blue" %)**How to connect with Energy Meter：**
91 -
92 -
78 +How to connect with Energy Meter：
93 93  )))
94 94  
95 95  (((
... ... @@ -101,98 +101,88 @@
101 101  )))
102 102  
103 103  (((
104 -Power Source **VIN** to RS485-LN **VIN+**
90 +Power Source VIN to RS485-LN VIN+
105 105  )))
106 106  
107 107  (((
108 -Power Source **GND** to RS485-LN **VIN-**
94 +Power Source GND to RS485-LN VIN-
109 109  )))
110 110  
111 111  (((
112 112  Once there is power, the RS485-LN will be on.
113 -
114 -
115 115  )))
116 116  
117 117  [[image:image-20220527092514-6.png]]
118 118  
119 -**Connection2**
103 +Connection2
120 120  
121 121  
122 122  
123 123  [[image:image-20220527092555-7.png]]
124 124  
125 -**Connection3**
109 +Connection3
126 126  
127 127  
128 -=== 1.3.2 How to use the parameters of the energy meter and MODBUS commands ===
112 +=== **1.3.2 How to use the parameters of the energy meter and MODBUS commands** ===
129 129  
130 -
131 131  If the user needs to read the parameters of the electric energy meter and use the modbus command,please refer to the appendix of the MODBUS communication protocol in the user manual of the energy meter.
132 132  
133 -[[image:image-20220601143257-10.png]]
116 +[[image:image-20220527092629-8.png]]
134 134  
135 135  
136 -(% style="color:blue" %)**Example:**(%%)  AT+COMMAND1=01 03 00 00 00 01 84 0A
119 +(% class="box infomessage" %)
120 +(((
121 +**Example:** AT+COMMAND1=01 03 00 00 00 01 84 0A
122 +)))
137 137  
138 138  * The first byte : slave address code (=001～247)
139 -
140 140  * The second byte : read register value function code
141 -
142 142  * 3rd and 4th bytes: start address of register to be read
143 -
144 144  * 5th and 6th bytes: Number of registers to read
145 -
146 146  * 7th and 8th bytes: CRC16 checksum from bytes 1 to 6.
147 147  
148 148  (((
149 -
150 -
151 -
152 152  How to parse the reading of the return command of the parameter：
132 +)))
153 153  
154 -(% style="color:blue" %)**Example:**(%%) RETURN1：01 03 02 08 FD 7E 05
134 +(% class="box infomessage" %)
135 +(((
136 +**Example:** RETURN1：01 03 02 08 FD 7E 05
155 155  )))
156 156  
157 157  * The first byte ARD: slave address code (=001～254)
158 -
159 159  * The second byte: Return to read function code
160 -
161 161  * 3rd byte: total number of bytes
162 -
163 163  * 4th～5th bytes: register data
164 -
165 165  * The 6th and 7th bytes: CRC16 checksum
166 -
167 167  * 08 FD is register data. Use short integer 16 bits to convert to decimal, get 2301, then 230.1V is the voltage.
168 168  
146 +(% class="wikigeneratedid" %)
147 +(((
148 +
149 +)))
169 169  
151 +=== **1.3.3 How to configure RS485-LN and parse output commands** ===
170 170  
171 -=== 1.3.3 How to configure RS485-LN and parse output commands ===
172 -
173 -
174 174  RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK.
175 175  
176 176  
177 -==== **1.3.3.1 via AT COMMAND** ====
156 +==== **1.3.3.1 via AT COMMAND:** ====
178 178  
158 +First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct.
179 179  
180 -First, we can use (% style="color:blue" %)**AT+CFGDEV**(%%) to get the return value, and we can also judge whether the input parameters are correct.
181 -
182 182  (((
183 183  If the configured parameters and commands are incorrect, the return value is not obtained.
184 -
185 -
186 186  )))
187 187  
188 -[[image:image-20220601143201-9.png]]
164 +[[image:image-20220527092748-9.png]]
189 189  
190 -**AT COMMAND**
166 +AT COMMAND
191 191  
192 192  
193 193  (% class="box infomessage" %)
194 194  (((
195 - (% _mstmutation="1" %)**AT+DATACUTx **(%%):  This command defines how to handle the return from AT+COMMANDx, max reture length is 40 bytes. AT+DATACUTx=a,b,c
171 + AT+DATACUTx : This command defines how to handle the return from AT+COMMANDx, max reture length is 40 bytes. AT+DATACUTx=a,b,c
196 196  )))
197 197  
198 198  a:  length for the return of AT+COMMAND
... ... @@ -201,26 +201,27 @@
201 201  
202 202  c:  define the position for valid value.
203 203  
204 -[[image:image-20220601143115-8.png]]
180 +[[image:image-20220527092936-10.png]]
205 205  
206 -**AT COMMAND**
182 +AT COMMAND
207 207  
208 208  
209 209  
210 210  PAYLOAD is available after the valid value is intercepted.
211 211  
212 -[[image:image-20220601143046-7.png]]
213 213  
214 -**AT COMMAND**
189 +[[image:image-20220527093059-11.png]]
215 215  
191 +AT COMMAND
216 216  
217 217  
194 +
218 218  You can get configured PAYLOAD on TTN.
219 219  
220 -[[image:image-20220601143519-1.png]]
197 +[[image:image-20220527093133-12.png]]
221 221  
222 222  (((
223 -**AT COMMAND**
200 +AT COMMAND
224 224  )))
225 225  
226 226  (((
... ... @@ -228,79 +228,77 @@
228 228  )))
229 229  
230 230  (((
231 -(% style="color:blue" %)**Example**:
208 +(% style="color:#4f81bd" %)**Example**:
232 232  
233 -(% style="color:red" %)**CMD1:**(%%) Read current data with MODBUS command. address: 0x03 AT+COMMAND1= 01 03 00 03 00 01,1
210 +CMD1:Read current data with MODBUS command. address:0x03 AT+COMMAND1= 01 03 00 03 00 01,1
234 234  )))
235 235  
236 236  (((
237 -RETURN1: 01 03 02 00 02 39 85 00 00(return data)
214 +RETURN1:01 03 02 00 02 39 85 00 00(return data)
238 238  )))
239 239  
240 240  (((
241 -AT+DATACUT1: 9,1,4+5+6+7 Take the return value 00 02 39 85 as the valid value of reading current data and used to splice payload.
218 +AT+DATACUT1:9,1,4+5+6+7 Take the return value 00 02 39 85 as the valid value of reading current data and used to splice payload.
242 242  
243 243  
244 244  )))
245 245  
246 246  (((
247 -(% style="color:red" %)**CMD2: **(%%)Read voltage data with MODBUS command. address: 0x00 AT+COMMAND2= 01 03 00 00 00 01,1
224 +CMD2:Read voltage data with MODBUS command. address:0x00 AT+COMMAND2= 01 03 00 00 00 01,1
248 248  )))
249 249  
250 250  (((
251 -RETURN2: 01 03 02 08 DC BE 1D(return data)
228 +RETURN2:01 03 02 08 DC BE 1D(return data)
252 252  )))
253 253  
254 254  (((
255 -AT+DATACUT2: 7,1,4+5 Take the return value 08 DC as the valid value of reading voltage data and used to splice payload.
232 +AT+DATACUT2:7,1,4+5 Take the return value 08 DC as the valid value of reading voltage data and used to splice payload.
256 256  
257 257  
258 258  )))
259 259  
260 260  (((
261 -(% style="color:red" %)**CMD3:**(%%) Read total active energy data with MODBUS command. address: 0x0031 AT+COMMAND3= 01 03 00 31 00 02,1
238 +CMD3:Read total active energy data with MODBUS command. address:0x0031 AT+COMMAND3= 01 03 00 31 00 02,1
262 262  )))
263 263  
264 264  (((
265 -RETURN3: 01 03 04 00 00 00 44 FA 00(return data)
242 +RETURN3:01 03 04 00 00 00 44 FA 00(return data)
266 266  )))
267 267  
268 268  (((
269 -AT+DATACUT3: 9,1,4+5+6+7 Take the return value 00 00 00 44 as the valid value of reading total active energy data and used to splice payload.
246 +AT+DATACUT3:9,1,4+5+6+7 Take the return value 00 00 00 44 as the valid value of reading total active energy data and used to splice payload.
270 270  )))
271 271  
272 272  (((
273 -Payload: 01 00 02 39 85 08 DC 00 00 00 44
250 +Payload:01 00 02 39 85 08 DC 00 00 00 44
274 274  )))
275 275  
276 -[[image:image-20220601142936-6.png]]
253 +[[image:image-20220527093204-13.png]]
277 277  
278 278  AT COMMAND
279 279  
280 280  
258 +(% style="color:#4f81bd" %)**01 is device address,00 02 is the current, 08 DC is the voltage,00 00 00 44 is the total active energy.**
281 281  
282 -(% style="color:blue" %)**01 is device address,00 02 is the current, 08 DC is the voltage,00 00 00 44 is the total active energy.**
260 +[[image:image-20220527093251-14.png]]
283 283  
284 -
285 -[[image:image-20220601143642-2.png]]
286 -
287 287  AT COMMAND
288 288  
289 289  
290 -
291 291  ==== **1.3.3.2 via LoRaWAN DOWNLINK** ====
292 292  
293 -
294 294  [[image:image-20220527093358-15.png]]
295 295  
296 296  (((
297 -**DOWNLINK**
270 +DOWNLINK
298 298  )))
299 299  
273 +(((
274 +
275 +)))
300 300  
301 -
302 302  (((
303 -(% style="color:blue" %)**Type Code 0xAF**
278 +(% style="color:#4f81bd" %)**Type Code 0xAF**
304 304  )))
305 305  
306 306  (((
... ... @@ -311,7 +311,7 @@
311 311  )))
312 312  
313 313  (((
314 -(% style="color:red" %)**Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.**
289 +Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
315 315  )))
316 316  
317 317  (((
... ... @@ -346,9 +346,8 @@
346 346  will execute an uplink after got this command.
347 347  )))
348 348  
349 -
350 350  (((
351 -(% style="color:blue" %)**Example:**
325 +(% style="color:#4f81bd" %)**Example:**
352 352  )))
353 353  
354 354  (((
... ... @@ -355,38 +355,33 @@
355 355  **AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
356 356  )))
357 357  
358 -[[image:image-20220601144149-6.png]]
332 +[[image:image-20220527093430-16.png]]
359 359  
360 -**DOWNLINK**
334 +DOWNLINK
361 361  
362 362  
337 +[[image:image-20220527093508-17.png]]
363 363  
364 -[[image:image-20220601143803-3.png]]
339 +DOWNLINK
365 365  
366 -**DOWNLINK**
367 367  
342 +[[image:image-20220527093530-18.png]]
368 368  
344 +DOWNLINK
369 369  
370 -[[image:image-20220601144053-5.png]]
371 371  
372 -**DOWNLINK**
347 +[[image:image-20220527093607-19.png]]
373 373  
349 +DOWNLINK
374 374  
375 375  
376 -[[image:image-20220601143921-4.png]]
352 +[[image:image-20220527093628-20.png]]
377 377  
378 -**DOWNLINK**
354 +DOWNLINK
355 +
379 379  
357 +=== **1.3.4 How to configure and output commands for RS485 to USB** ===
380 380  
381 -
382 -[[image:image-20220601142805-5.png]]
383 -
384 -**DOWNLINK**
385 -
386 -
387 -=== 1.3.4 How to configure and output commands for RS485 to USB ===
388 -
389 -
390 390  (((
391 391  This step is not necessary, it is just to show how to use a normal RS485 to USB adapter to connect to the meter to check the input and output. This can be used to test the connection and RS485 command of the meter without RS485-LN.
392 392  )))
... ... @@ -405,45 +405,37 @@
405 405  
406 406  (((
407 407  check digit: Even
408 -
409 -
410 410  )))
411 411  
412 412  [[image:image-20220527093708-21.png]]
413 413  
414 -**USB**
381 +USB
415 415  
416 416  
417 -
418 418  [[image:image-20220527093747-22.png]]
419 419  
420 -**USB**
386 +USB
421 421  
422 422  
423 -
424 424  (((
425 425  The configuration command is consistent with the AT command, input the hexadecimal command directly into the serial port, and the serial port will output the command.
426 426  )))
427 427  
428 428  (((
429 -(% style="color:blue" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
394 +(% style="color:#4f81bd" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
430 430  )))
431 431  
432 432  (((
433 433   output：01 03 04 00 00 00 42 7A 02
434 -
435 -
436 436  )))
437 437  
438 438  [[image:image-20220527093821-23.png]]
439 439  
440 -**USB**
403 +USB
441 441  
442 442  
406 +=== **1.3.5 How to configure multiple devices and modify device addresses** ===
443 443  
444 -=== 1.3.5 How to configure multiple devices and modify device addresses ===
445 -
446 -
447 447  If users need to read the parameters of multiple energy meters, they need to modify the device address, because the default device address of each energy meter is 01.
448 448  
449 449  (((
... ... @@ -452,18 +452,15 @@
452 452  )))
453 453  )))
454 454  
455 -[[image:image-20220601142044-1.png]]
416 +[[image:image-20220527093849-24.png]]
456 456  
457 457  
458 -(% style="color:blue" %)**Example**(%%): These two meters are examples of setting parameters and device addresses.
419 +**Example**:These two meters are examples of setting parameters and device addresses.
459 459  
460 -
461 461  [[image:image-20220527093950-25.png]]
462 462  
463 -
464 464  [[image:image-20220527094028-26.png]]
465 465  
466 -
467 467  (((
468 468  (((
469 469  First of all, since the default device address of the energy meter is 01, the configuration of two energy meters will conflict, so we first connect an energy meter and configure the device address.
... ... @@ -472,7 +472,7 @@
472 472  
473 473  (((
474 474  (((
475 -We can use (% style="color:blue" %)**AT+CFGDEV**(%%) to set the device address.
433 +We can use AT+CFGDEV to set the device address.
476 476  )))
477 477  )))
478 478  
... ... @@ -482,17 +482,16 @@
482 482  )))
483 483  )))
484 484  
485 -[[image:image-20220601142354-2.png]]
443 +[[image:image-20220527094100-27.png]]
486 486  
487 -
488 488  (% class="box infomessage" %)
489 489  (((
490 490  **AT+CFGDEV:01 10 00 61 00 01 02 00 02,1**
491 491  )))
492 492  
493 -* 01: device adaress
450 +* 01:device adaress
494 494  
495 -* 10: function code
452 +* 10:function code
496 496  
497 497  * 00 61：Register address
498 498  
... ... @@ -510,62 +510,46 @@
510 510  
511 511  Its default device address is 01, and the following are the parameters for configuring two energy meters.
512 512  
513 -[[image:image-20220601142452-3.png]]
470 +[[image:image-20220527094150-28.png]]
514 514  
515 515  
516 -[[image:image-20220601142607-4.png]]
473 +[[image:image-20220527094224-29.png]]
517 517  
475 +**PAYLOAD:01 08 DF 43 62**
518 518  
519 -(% style="color:blue" %)**PAYLOAD: 01 08 DF 43 62**
520 -
521 521  * 08 DF is the valid value of the meter with device address 02.
522 522  * 43 62 is the valid value of the meter with device address 01.
523 523  
524 -(% style="display:none" %) (%%)
525 525  
526 -
527 527  == 1.4 Example 4: Circuit Breaker Remote Open Close ==
528 528  
483 +This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-LN to connect to SCHNEIDER SMART and Monitor and control your cabinet remotely with no wires and with Dragino RS485-LN LoRaWAN technology. The structure is like below:
529 529  
530 -This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-LN to connect to SCHNEIDER SMART and Monitor and control your cabinet remotely with no wires and with Dragino RS485-LN LoRaWAN technology.
531 -
532 -The structure is like below:
533 -
534 534  [[image:image-20220527094330-30.png]]
535 535  
536 -**Connection**
487 +Connection
537 537  
489 +* [[Circuit Breaker Remote Open Close>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Circuit_Breaker_Remote_Open_Close/]] : Configure Documen
538 538  
539 -* Configure Documen:  [[Circuit Breaker Remote Open Close>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Circuit_Breaker_Remote_Open_Close/||_mstmutation="1"]]
540 540  
541 -
542 -
543 543  == 1.5 Example 5: SEM Three Energy Meter with RS485-BL or RS485-LN ==
544 544  
545 -
546 546  This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-BL to connect to SEM Three Energy Meter and send the data to mobile phone for remote minitor. The structure is like below:
547 547  
548 -* Configure Document For RS485-BL:  [[Connect to SEM Three>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Application_Note/&file=Dragino%20RS485BL%20and%20pickdata%20SEM%20Three%20v1.pdf||_mstmutation="1" style="background-color: rgb(255, 255, 255);"]]
496 +* [[Connect to SEM Three>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Application_Note/&file=Dragino%20RS485BL%20and%20pickdata%20SEM%20Three%20v1.pdf]] : Configure Document For RS485-BL
549 549  
550 -* Configure Document for RS485-LN:  [[Connect to SEM Three>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/SEM_Three_Energy_Meter/&file=SEM%20three%20and%20Dragino%20RS485-LN%20v1.pdf||_mstmutation="1"]]
498 +* [[Connect to SEM Three>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/SEM_Three_Energy_Meter/&file=SEM%20three%20and%20Dragino%20RS485-LN%20v1.pdf]] : Configure Document for RS485-LN
551 551  
500 +== 1.6 Example 6:CEM C31 485-T1-MID Energy Meter with RS485-LN ==
552 552  
553 -
554 -== 1.6 Example 6: CEM C31 485-T1-MID Energy Meter with RS485-LN ==
555 -
556 -
557 557  This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-LN to connect to CEM C31 485-T1-MID and send the data for remote minitor. The structure is like below:
558 558  
559 -* Configure Document For RS485-LN:  [[CEM C31 485-T1-MID>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/ELECTRICAL%20CABINET/&file=ELECTRICAL%20CABINET%20READINGS.pdf||_mstmutation="1" style="background-color: rgb(255, 255, 255);"]]
504 +* [[CEM C31 485-T1-MID>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/ELECTRICAL%20CABINET/&file=ELECTRICAL%20CABINET%20READINGS.pdf]] : Configure Document For RS485-LN
560 560  
506 +== 1.7 Example 7:Schneider Electric PLC M221 with RS485-BL ==
561 561  
562 -
563 -== 1.7 Example 7: Schneider Electric PLC M221 with RS485-BL ==
564 -
565 -
566 566  [[image:image-20220527094556-31.png]]
567 567  
568 568  Network Structure
569 569  
570 -
571 571  * [[Reference Instruction>>url:https://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Schneider%20Electric%20PLC/]]
image-20220601142044-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -3.7 KB
Content
image-20220601142354-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -2.8 KB
Content
image-20220601142452-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -28.1 KB
Content
image-20220601142607-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.9 KB
Content
image-20220601142805-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -35.8 KB
Content
image-20220601142936-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.7 KB
Content
image-20220601143046-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.2 KB
Content
image-20220601143115-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.9 KB
Content
image-20220601143201-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -16.5 KB
Content
image-20220601143257-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.1 KB
Content
image-20220601143519-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -13.2 KB
Content
image-20220601143642-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -41.4 KB
Content
image-20220601143803-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.8 KB
Content
image-20220601143921-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.2 KB
Content
image-20220601144053-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -17.1 KB
Content
image-20220601144149-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -17.4 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0