Last modified by Karry Zhuang on 2024/07/11 11:58
<
From version < 57.20 >
edited by Xiaoling
on 2022/07/14 10:10
To version < 45.1 >
edited by Xiaoling
on 2022/06/01 14:26
>
Change comment: Uploaded new attachment "image-20220601142607-4.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,21 +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 65  == **1.3 Example3: Use RS485-LN with energy meters** ==
66 66  
67 -
68 68  === **1.3.1 OverView** ===
69 69  
70 -
71 71  (((
72 -(% 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.
73 73  )))
74 74  
75 75  (((
... ... @@ -83,9 +83,7 @@
83 83  
84 84  
85 85  (((
86 -(% style="color:blue" %)**How to connect with Energy Meter：**
87 -
88 -
78 +How to connect with Energy Meter：
89 89  )))
90 90  
91 91  (((
... ... @@ -113,6 +113,7 @@
113 113  Connection2
114 114  
115 115  
106 +
116 116  [[image:image-20220527092555-7.png]]
117 117  
118 118  Connection3
... ... @@ -120,13 +120,15 @@
120 120  
121 121  === **1.3.2 How to use the parameters of the energy meter and MODBUS commands** ===
122 122  
123 -
124 124  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.
125 125  
126 -[[image:image-20220601143257-10.png]]
116 +[[image:image-20220527092629-8.png]]
127 127  
128 128  
129 -(% 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 +)))
130 130  
131 131  * The first byte : slave address code (=001～247)
132 132  * The second byte : read register value function code
... ... @@ -135,12 +135,12 @@
135 135  * 7th and 8th bytes: CRC16 checksum from bytes 1 to 6.
136 136  
137 137  (((
138 -
139 -
140 -
141 141  How to parse the reading of the return command of the parameter：
132 +)))
142 142  
143 -(% 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
144 144  )))
145 145  
146 146  * The first byte ARD: slave address code (=001～254)
... ... @@ -153,27 +153,22 @@
153 153  (% class="wikigeneratedid" %)
154 154  (((
155 155  
156 -
157 -
158 -
159 159  )))
160 160  
161 161  === **1.3.3 How to configure RS485-LN and parse output commands** ===
162 162  
163 -
164 164  RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK.
165 165  
166 166  
167 -==== **1.3.3.1 via AT COMMAND** ====
156 +==== **1.3.3.1 via AT COMMAND:** ====
168 168  
158 +First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct.
169 169  
170 -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.
171 -
172 172  (((
173 173  If the configured parameters and commands are incorrect, the return value is not obtained.
174 174  )))
175 175  
176 -[[image:image-20220601143201-9.png]]
164 +[[image:image-20220527092748-9.png]]
177 177  
178 178  AT COMMAND
179 179  
... ... @@ -180,7 +180,7 @@
180 180  
181 181  (% class="box infomessage" %)
182 182  (((
183 - **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
184 184  )))
185 185  
186 186  a:  length for the return of AT+COMMAND
... ... @@ -189,7 +189,7 @@
189 189  
190 190  c:  define the position for valid value.
191 191  
192 -[[image:image-20220601143115-8.png]]
180 +[[image:image-20220527092936-10.png]]
193 193  
194 194  AT COMMAND
195 195  
... ... @@ -198,7 +198,7 @@
198 198  PAYLOAD is available after the valid value is intercepted.
199 199  
200 200  
201 -[[image:image-20220601143046-7.png]]
189 +[[image:image-20220527093059-11.png]]
202 202  
203 203  AT COMMAND
204 204  
... ... @@ -206,7 +206,7 @@
206 206  
207 207  You can get configured PAYLOAD on TTN.
208 208  
209 -[[image:image-20220601143519-1.png]]
197 +[[image:image-20220527093133-12.png]]
210 210  
211 211  (((
212 212  AT COMMAND
... ... @@ -217,52 +217,52 @@
217 217  )))
218 218  
219 219  (((
220 -(% style="color:blue" %)**Example**:
208 +(% style="color:#4f81bd" %)**Example**:
221 221  
222 -(% 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
223 223  )))
224 224  
225 225  (((
226 -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)
227 227  )))
228 228  
229 229  (((
230 -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.
231 231  
232 232  
233 233  )))
234 234  
235 235  (((
236 -(% 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
237 237  )))
238 238  
239 239  (((
240 -RETURN2: 01 03 02 08 DC BE 1D(return data)
228 +RETURN2:01 03 02 08 DC BE 1D(return data)
241 241  )))
242 242  
243 243  (((
244 -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.
245 245  
246 246  
247 247  )))
248 248  
249 249  (((
250 -(% 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
251 251  )))
252 252  
253 253  (((
254 -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)
255 255  )))
256 256  
257 257  (((
258 -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.
259 259  )))
260 260  
261 261  (((
262 -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
263 263  )))
264 264  
265 -[[image:image-20220601142936-6.png]]
253 +[[image:image-20220527093204-13.png]]
266 266  
267 267  AT COMMAND
268 268  
... ... @@ -270,14 +270,14 @@
270 270  (% 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.**
271 271  
272 272  
273 -[[image:image-20220601143642-2.png]]
274 274  
262 +[[image:image-20220527093251-14.png]]
263 +
275 275  AT COMMAND
276 276  
277 277  
278 278  ==== **1.3.3.2 via LoRaWAN DOWNLINK** ====
279 279  
280 -
281 281  [[image:image-20220527093358-15.png]]
282 282  
283 283  (((
... ... @@ -300,7 +300,7 @@
300 300  )))
301 301  
302 302  (((
303 -(% 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.
304 304  )))
305 305  
306 306  (((
... ... @@ -338,7 +338,7 @@
338 338  (((
339 339  
340 340  
341 -(% style="color:blue" %)**Example:**
329 +(% style="color:#4f81bd" %)**Example:**
342 342  )))
343 343  
344 344  (((
... ... @@ -345,31 +345,31 @@
345 345  **AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
346 346  )))
347 347  
348 -[[image:image-20220601144149-6.png]]
336 +[[image:image-20220527093430-16.png]]
349 349  
350 350  DOWNLINK
351 351  
352 352  
353 353  
354 -[[image:image-20220601143803-3.png]]
342 +[[image:image-20220527093508-17.png]]
355 355  
356 356  DOWNLINK
357 357  
358 358  
359 359  
360 -[[image:image-20220601144053-5.png]]
348 +[[image:image-20220527093530-18.png]]
361 361  
362 362  DOWNLINK
363 363  
364 364  
365 365  
366 -[[image:image-20220601143921-4.png]]
354 +[[image:image-20220527093607-19.png]]
367 367  
368 368  DOWNLINK
369 369  
370 370  
371 371  
372 -[[image:image-20220601142805-5.png]]
360 +[[image:image-20220527093628-20.png]]
373 373  
374 374  DOWNLINK
375 375  
... ... @@ -394,8 +394,6 @@
394 394  
395 395  (((
396 396  check digit: Even
397 -
398 -
399 399  )))
400 400  
401 401  [[image:image-20220527093708-21.png]]
... ... @@ -412,18 +412,14 @@
412 412  
413 413  (((
414 414  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.
415 -
416 -
417 417  )))
418 418  
419 419  (((
420 -(% 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
421 421  )))
422 422  
423 423  (((
424 424   output：01 03 04 00 00 00 42 7A 02
425 -
426 -
427 427  )))
428 428  
429 429  [[image:image-20220527093821-23.png]]
... ... @@ -433,7 +433,6 @@
433 433  
434 434  === **1.3.5 How to configure multiple devices and modify device addresses** ===
435 435  
436 -
437 437  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.
438 438  
439 439  (((
... ... @@ -445,14 +445,12 @@
445 445  [[image:image-20220601142044-1.png]]
446 446  
447 447  
448 -(% 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.
449 449  
450 450  [[image:image-20220527093950-25.png]]
451 451  
452 -
453 453  [[image:image-20220527094028-26.png]]
454 454  
455 -
456 456  (((
457 457  (((
458 458  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.
... ... @@ -461,7 +461,7 @@
461 461  
462 462  (((
463 463  (((
464 -We can use **AT+CFGDEV** to set the device address.
443 +We can use AT+CFGDEV to set the device address.
465 465  )))
466 466  )))
467 467  
... ... @@ -473,7 +473,6 @@
473 473  
474 474  [[image:image-20220601142354-2.png]]
475 475  
476 -
477 477  (% class="box infomessage" %)
478 478  (((
479 479  **AT+CFGDEV:01 10 00 61 00 01 02 00 02,1**
... ... @@ -502,49 +502,43 @@
502 502  [[image:image-20220601142452-3.png]]
503 503  
504 504  
505 -[[image:image-20220601142607-4.png]]
483 +[[image:image-20220527094224-29.png]]
506 506  
507 -
508 508  **PAYLOAD:01 08 DF 43 62**
509 509  
510 510  * 08 DF is the valid value of the meter with device address 02.
511 511  * 43 62 is the valid value of the meter with device address 01.
512 512  
490 +
513 513  == 1.4 Example 4: Circuit Breaker Remote Open Close ==
514 514  
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:
515 515  
516 -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.
517 -
518 -The structure is like below:
519 -
520 520  [[image:image-20220527094330-30.png]]
521 521  
522 522  Connection
523 523  
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
524 524  
525 -* 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/]]
526 526  
527 527  == 1.5 Example 5: SEM Three Energy Meter with RS485-BL or RS485-LN ==
528 528  
529 -
530 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-BL to connect to SEM Three Energy Meter and send the data to mobile phone for remote minitor. The structure is like below:
531 531  
532 -* 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);"]]
533 -* 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
534 534  
535 -== 1.6 Example 6: CEM C31 485-T1-MID Energy Meter with RS485-LN ==
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
536 536  
510 +== 1.6 Example 6:CEM C31 485-T1-MID Energy Meter with RS485-LN ==
537 537  
538 538  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:
539 539  
540 -* 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);"]]
514 +* [[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
541 541  
542 -== 1.7 Example 7: Schneider Electric PLC M221 with RS485-BL ==
516 +== 1.7 Example 7:Schneider Electric PLC M221 with RS485-BL ==
543 543  
544 -
545 545  [[image:image-20220527094556-31.png]]
546 546  
547 547  Network Structure
548 548  
549 -
550 550  * [[Reference Instruction>>url:https://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Schneider%20Electric%20PLC/]]
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