Last modified by Karry Zhuang on 2024/07/11 11:58
<
From version < 58.1 >
edited by Xiaoling
on 2022/07/14 10:20
To version < 47.1 >
edited by Xiaoling
on 2022/06/01 14:29
>
Change comment: Uploaded new attachment "image-20220601142936-6.png", version {1}

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  
... ... @@ -9,13 +9,11 @@
9 9  
10 10  = **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 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  
21 21  [[image:image-20220527091852-1.png]]
... ... @@ -29,21 +29,18 @@
29 29  Connection
30 30  
31 31  
32 -(% style="color:blue" %)**Related documents:**
31 +Related documents:
33 33  
34 -* System Structure:  [[Solar Pump with Dragino>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Relay_VFD/||style="background-color: rgb(255, 255, 255);"]]
35 -* 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/||style="background-color: rgb(255, 255, 255);"]]
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.
36 36  * [[Video Demo>>url:https://www.youtube.com/watch?v=TAFZ5eaf-MY&t=6s&ab_channel=XavierFlorensaBerenguer]]
37 37  
38 38  
39 39  
40 -
41 41  == **1.2 Example 2: Connect to Pulse Counter** ==
42 42  
43 -
44 44  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:
45 45  
46 -
47 47  [[image:image-20220527092058-3.png]]
48 48  
49 49  Connection
... ... @@ -55,22 +55,17 @@
55 55  Connection
56 56  
57 57  
58 -(% style="color:blue" %)**Related documents:**
59 -
60 -* 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/]]
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
61 61  * [[Dragino Solution in Farm>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/&file=Dragino%20on%20Farms.pptx]]
62 62  
57 +== ==
63 63  
64 -
65 -
66 66  == **1.3 Example3: Use RS485-LN with energy meters** ==
67 67  
68 -
69 69  === **1.3.1 OverView** ===
70 70  
71 -
72 72  (((
73 -(% 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.
74 74  )))
75 75  
76 76  (((
... ... @@ -84,9 +84,7 @@
84 84  
85 85  
86 86  (((
87 -(% style="color:blue" %)**How to connect with Energy Meter：**
88 -
89 -
78 +How to connect with Energy Meter：
90 90  )))
91 91  
92 92  (((
... ... @@ -114,21 +114,23 @@
114 114  Connection2
115 115  
116 116  
106 +
117 117  [[image:image-20220527092555-7.png]]
118 118  
119 119  Connection3
120 120  
121 121  
122 -
123 123  === **1.3.2 How to use the parameters of the energy meter and MODBUS commands** ===
124 124  
125 -
126 126  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.
127 127  
128 -[[image:image-20220601143257-10.png]]
116 +[[image:image-20220527092629-8.png]]
129 129  
130 130  
131 -(% 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 +)))
132 132  
133 133  * The first byte : slave address code (=001～247)
134 134  * The second byte : read register value function code
... ... @@ -137,12 +137,12 @@
137 137  * 7th and 8th bytes: CRC16 checksum from bytes 1 to 6.
138 138  
139 139  (((
140 -
141 -
142 -
143 143  How to parse the reading of the return command of the parameter：
132 +)))
144 144  
145 -(% 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
146 146  )))
147 147  
148 148  * The first byte ARD: slave address code (=001～254)
... ... @@ -155,28 +155,22 @@
155 155  (% class="wikigeneratedid" %)
156 156  (((
157 157  
158 -
159 -
160 -
161 161  )))
162 162  
163 163  === **1.3.3 How to configure RS485-LN and parse output commands** ===
164 164  
165 -
166 166  RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK.
167 167  
168 168  
156 +==== **1.3.3.1 via AT COMMAND:** ====
169 169  
170 -==== **1.3.3.1 via AT COMMAND** ====
158 +First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct.
171 171  
172 -
173 -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.
174 -
175 175  (((
176 176  If the configured parameters and commands are incorrect, the return value is not obtained.
177 177  )))
178 178  
179 -[[image:image-20220601143201-9.png]]
164 +[[image:image-20220527092748-9.png]]
180 180  
181 181  AT COMMAND
182 182  
... ... @@ -183,7 +183,7 @@
183 183  
184 184  (% class="box infomessage" %)
185 185  (((
186 - **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
187 187  )))
188 188  
189 189  a:  length for the return of AT+COMMAND
... ... @@ -192,7 +192,7 @@
192 192  
193 193  c:  define the position for valid value.
194 194  
195 -[[image:image-20220601143115-8.png]]
180 +[[image:image-20220527092936-10.png]]
196 196  
197 197  AT COMMAND
198 198  
... ... @@ -201,7 +201,7 @@
201 201  PAYLOAD is available after the valid value is intercepted.
202 202  
203 203  
204 -[[image:image-20220601143046-7.png]]
189 +[[image:image-20220527093059-11.png]]
205 205  
206 206  AT COMMAND
207 207  
... ... @@ -209,7 +209,7 @@
209 209  
210 210  You can get configured PAYLOAD on TTN.
211 211  
212 -[[image:image-20220601143519-1.png]]
197 +[[image:image-20220527093133-12.png]]
213 213  
214 214  (((
215 215  AT COMMAND
... ... @@ -220,52 +220,52 @@
220 220  )))
221 221  
222 222  (((
223 -(% style="color:blue" %)**Example**:
208 +(% style="color:#4f81bd" %)**Example**:
224 224  
225 -(% 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
226 226  )))
227 227  
228 228  (((
229 -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)
230 230  )))
231 231  
232 232  (((
233 -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.
234 234  
235 235  
236 236  )))
237 237  
238 238  (((
239 -(% 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
240 240  )))
241 241  
242 242  (((
243 -RETURN2: 01 03 02 08 DC BE 1D(return data)
228 +RETURN2:01 03 02 08 DC BE 1D(return data)
244 244  )))
245 245  
246 246  (((
247 -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.
248 248  
249 249  
250 250  )))
251 251  
252 252  (((
253 -(% 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
254 254  )))
255 255  
256 256  (((
257 -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)
258 258  )))
259 259  
260 260  (((
261 -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.
262 262  )))
263 263  
264 264  (((
265 -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
266 266  )))
267 267  
268 -[[image:image-20220601142936-6.png]]
253 +[[image:image-20220527093204-13.png]]
269 269  
270 270  AT COMMAND
271 271  
... ... @@ -273,15 +273,14 @@
273 273  (% 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.**
274 274  
275 275  
276 -[[image:image-20220601143642-2.png]]
277 277  
262 +[[image:image-20220527093251-14.png]]
263 +
278 278  AT COMMAND
279 279  
280 280  
281 -
282 282  ==== **1.3.3.2 via LoRaWAN DOWNLINK** ====
283 283  
284 -
285 285  [[image:image-20220527093358-15.png]]
286 286  
287 287  (((
... ... @@ -304,7 +304,7 @@
304 304  )))
305 305  
306 306  (((
307 -(% style="color:red" %)**Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.**
291 +Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
308 308  )))
309 309  
310 310  (((
... ... @@ -342,7 +342,7 @@
342 342  (((
343 343  
344 344  
345 -(% style="color:blue" %)**Example:**
329 +(% style="color:#4f81bd" %)**Example:**
346 346  )))
347 347  
348 348  (((
... ... @@ -349,25 +349,25 @@
349 349  **AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
350 350  )))
351 351  
352 -[[image:image-20220601144149-6.png]]
336 +[[image:image-20220527093430-16.png]]
353 353  
354 354  DOWNLINK
355 355  
356 356  
357 357  
358 -[[image:image-20220601143803-3.png]]
342 +[[image:image-20220527093508-17.png]]
359 359  
360 360  DOWNLINK
361 361  
362 362  
363 363  
364 -[[image:image-20220601144053-5.png]]
348 +[[image:image-20220527093530-18.png]]
365 365  
366 366  DOWNLINK
367 367  
368 368  
369 369  
370 -[[image:image-20220601143921-4.png]]
354 +[[image:image-20220527093607-19.png]]
371 371  
372 372  DOWNLINK
373 373  
... ... @@ -378,7 +378,6 @@
378 378  DOWNLINK
379 379  
380 380  
381 -
382 382  === **1.3.4 How to configure and output commands for RS485 to USB** ===
383 383  
384 384  (((
... ... @@ -399,8 +399,6 @@
399 399  
400 400  (((
401 401  check digit: Even
402 -
403 -
404 404  )))
405 405  
406 406  [[image:image-20220527093708-21.png]]
... ... @@ -417,18 +417,14 @@
417 417  
418 418  (((
419 419  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.
420 -
421 -
422 422  )))
423 423  
424 424  (((
425 -(% style="color:blue" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
404 +(% style="color:#4f81bd" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
426 426  )))
427 427  
428 428  (((
429 429   output：01 03 04 00 00 00 42 7A 02
430 -
431 -
432 432  )))
433 433  
434 434  [[image:image-20220527093821-23.png]]
... ... @@ -436,10 +436,8 @@
436 436  USB
437 437  
438 438  
439 -
440 440  === **1.3.5 How to configure multiple devices and modify device addresses** ===
441 441  
442 -
443 443  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.
444 444  
445 445  (((
... ... @@ -451,14 +451,12 @@
451 451  [[image:image-20220601142044-1.png]]
452 452  
453 453  
454 -(% style="color:blue" %)**Example**(%%): These two meters are examples of setting parameters and device addresses.
429 +**Example**:These two meters are examples of setting parameters and device addresses.
455 455  
456 456  [[image:image-20220527093950-25.png]]
457 457  
458 -
459 459  [[image:image-20220527094028-26.png]]
460 460  
461 -
462 462  (((
463 463  (((
464 464  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.
... ... @@ -467,7 +467,7 @@
467 467  
468 468  (((
469 469  (((
470 -We can use (% style="color:blue" %)**AT+CFGDEV**(%%) to set the device address.
443 +We can use AT+CFGDEV to set the device address.
471 471  )))
472 472  )))
473 473  
... ... @@ -479,7 +479,6 @@
479 479  
480 480  [[image:image-20220601142354-2.png]]
481 481  
482 -
483 483  (% class="box infomessage" %)
484 484  (((
485 485  **AT+CFGDEV:01 10 00 61 00 01 02 00 02,1**
... ... @@ -510,59 +510,45 @@
510 510  
511 511  [[image:image-20220601142607-4.png]]
512 512  
485 +**PAYLOAD:01 08 DF 43 62**
513 513  
514 -(% style="color:blue" %)**PAYLOAD: 01 08 DF 43 62**
515 -
516 516  * 08 DF is the valid value of the meter with device address 02.
517 517  * 43 62 is the valid value of the meter with device address 01.
518 518  
519 519  
520 -
521 -
522 522  == 1.4 Example 4: Circuit Breaker Remote Open Close ==
523 523  
493 +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:
524 524  
525 -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.
526 -
527 -The structure is like below:
528 -
529 529  [[image:image-20220527094330-30.png]]
530 530  
531 531  Connection
532 532  
499 +* [[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
533 533  
534 -* 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/]]
535 535  
536 -
537 -
538 -
539 539  == 1.5 Example 5: SEM Three Energy Meter with RS485-BL or RS485-LN ==
540 540  
541 -
542 542  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:
543 543  
544 -* 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||style="background-color: rgb(255, 255, 255);"]]
545 -* 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]]
506 +* [[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
546 546  
508 +* [[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
547 547  
548 548  
549 549  
550 -== 1.6 Example 6: CEM C31 485-T1-MID Energy Meter with RS485-LN ==
512 +== 1.6 Example 6:CEM C31 485-T1-MID Energy Meter with RS485-LN ==
551 551  
552 -
553 553  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:
554 554  
555 -* 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||style="background-color: rgb(255, 255, 255);"]]
516 +* [[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
556 556  
557 557  
558 558  
520 +== 1.7 Example 7:Schneider Electric PLC M221 with RS485-BL ==
559 559  
560 -== 1.7 Example 7: Schneider Electric PLC M221 with RS485-BL ==
561 -
562 -
563 563  [[image:image-20220527094556-31.png]]
564 564  
565 565  Network Structure
566 566  
567 -
568 568  * [[Reference Instruction>>url:https://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Schneider%20Electric%20PLC/]]
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