<
From version < 57.19 >
edited by Xiaoling
on 2022/07/14 10:09
To version < 44.1 >
edited by Xiaoling
on 2022/06/01 14:24
>
Change comment: Uploaded new attachment "image-20220601142452-3.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,18 +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 -== **1.2 Example 2: Connect to Pulse Counter** ==
39 39  
40 40  
39 +== **1.2 Example 2: Connect to Pulse Counter** ==
40 +
41 41  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:
42 42  
43 -
44 44  [[image:image-20220527092058-3.png]]
45 45  
46 46  Connection
... ... @@ -52,21 +52,17 @@
52 52  Connection
53 53  
54 54  
55 -(% style="color:blue" %)**Related documents:**
56 -
57 -* 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
58 58  * [[Dragino Solution in Farm>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/&file=Dragino%20on%20Farms.pptx]]
59 59  
57 +== ==
60 60  
61 -
62 62  == **1.3 Example3: Use RS485-LN with energy meters** ==
63 63  
64 -
65 65  === **1.3.1 OverView** ===
66 66  
67 -
68 68  (((
69 -(% 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.
70 70  )))
71 71  
72 72  (((
... ... @@ -80,9 +80,7 @@
80 80  
81 81  
82 82  (((
83 -(% style="color:blue" %)**How to connect with Energy Meter:**
84 -
85 -
78 +How to connect with Energy Meter:
86 86  )))
87 87  
88 88  (((
... ... @@ -110,6 +110,7 @@
110 110  Connection2
111 111  
112 112  
106 +
113 113  [[image:image-20220527092555-7.png]]
114 114  
115 115  Connection3
... ... @@ -117,13 +117,15 @@
117 117  
118 118  === **1.3.2 How to use the parameters of the energy meter and MODBUS commands** ===
119 119  
120 -
121 121  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.
122 122  
123 -[[image:image-20220601143257-10.png]]
116 +[[image:image-20220527092629-8.png]]
124 124  
125 125  
126 -(% 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 +)))
127 127  
128 128  * The first byte : slave address code (=001~247)
129 129  * The second byte : read register value function code
... ... @@ -132,12 +132,12 @@
132 132  * 7th and 8th bytes: CRC16 checksum from bytes 1 to 6.
133 133  
134 134  (((
135 -
136 -
137 -
138 138  How to parse the reading of the return command of the parameter:
132 +)))
139 139  
140 -(% 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
141 141  )))
142 142  
143 143  * The first byte ARD: slave address code (=001~254)
... ... @@ -150,27 +150,22 @@
150 150  (% class="wikigeneratedid" %)
151 151  (((
152 152  
153 -
154 -
155 -
156 156  )))
157 157  
158 158  === **1.3.3 How to configure RS485-LN and parse output commands** ===
159 159  
160 -
161 161  RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK.
162 162  
163 163  
164 -==== **1.3.3.1 via AT COMMAND** ====
156 +==== **1.3.3.1 via AT COMMAND:** ====
165 165  
158 +First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct.
166 166  
167 -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.
168 -
169 169  (((
170 170  If the configured parameters and commands are incorrect, the return value is not obtained.
171 171  )))
172 172  
173 -[[image:image-20220601143201-9.png]]
164 +[[image:image-20220527092748-9.png]]
174 174  
175 175  AT COMMAND
176 176  
... ... @@ -177,7 +177,7 @@
177 177  
178 178  (% class="box infomessage" %)
179 179  (((
180 - **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
181 181  )))
182 182  
183 183  a:  length for the return of AT+COMMAND
... ... @@ -186,7 +186,7 @@
186 186  
187 187  c:  define the position for valid value.
188 188  
189 -[[image:image-20220601143115-8.png]]
180 +[[image:image-20220527092936-10.png]]
190 190  
191 191  AT COMMAND
192 192  
... ... @@ -195,7 +195,7 @@
195 195  PAYLOAD is available after the valid value is intercepted.
196 196  
197 197  
198 -[[image:image-20220601143046-7.png]]
189 +[[image:image-20220527093059-11.png]]
199 199  
200 200  AT COMMAND
201 201  
... ... @@ -203,7 +203,7 @@
203 203  
204 204  You can get configured PAYLOAD on TTN.
205 205  
206 -[[image:image-20220601143519-1.png]]
197 +[[image:image-20220527093133-12.png]]
207 207  
208 208  (((
209 209  AT COMMAND
... ... @@ -214,52 +214,52 @@
214 214  )))
215 215  
216 216  (((
217 -(% style="color:blue" %)**Example**:
208 +(% style="color:#4f81bd" %)**Example**:
218 218  
219 -(% 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
220 220  )))
221 221  
222 222  (((
223 -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)
224 224  )))
225 225  
226 226  (((
227 -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.
228 228  
229 229  
230 230  )))
231 231  
232 232  (((
233 -(% 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
234 234  )))
235 235  
236 236  (((
237 -RETURN2: 01 03 02 08 DC BE 1D(return data)
228 +RETURN2:01 03 02 08 DC BE 1D(return data)
238 238  )))
239 239  
240 240  (((
241 -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.
242 242  
243 243  
244 244  )))
245 245  
246 246  (((
247 -(% 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
248 248  )))
249 249  
250 250  (((
251 -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)
252 252  )))
253 253  
254 254  (((
255 -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.
256 256  )))
257 257  
258 258  (((
259 -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
260 260  )))
261 261  
262 -[[image:image-20220601142936-6.png]]
253 +[[image:image-20220527093204-13.png]]
263 263  
264 264  AT COMMAND
265 265  
... ... @@ -267,14 +267,14 @@
267 267  (% 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.**
268 268  
269 269  
270 -[[image:image-20220601143642-2.png]]
271 271  
262 +[[image:image-20220527093251-14.png]]
263 +
272 272  AT COMMAND
273 273  
274 274  
275 275  ==== **1.3.3.2 via LoRaWAN DOWNLINK** ====
276 276  
277 -
278 278  [[image:image-20220527093358-15.png]]
279 279  
280 280  (((
... ... @@ -297,7 +297,7 @@
297 297  )))
298 298  
299 299  (((
300 -(% 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.
301 301  )))
302 302  
303 303  (((
... ... @@ -335,7 +335,7 @@
335 335  (((
336 336  
337 337  
338 -(% style="color:blue" %)**Example:**
329 +(% style="color:#4f81bd" %)**Example:**
339 339  )))
340 340  
341 341  (((
... ... @@ -342,31 +342,31 @@
342 342  **AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
343 343  )))
344 344  
345 -[[image:image-20220601144149-6.png]]
336 +[[image:image-20220527093430-16.png]]
346 346  
347 347  DOWNLINK
348 348  
349 349  
350 350  
351 -[[image:image-20220601143803-3.png]]
342 +[[image:image-20220527093508-17.png]]
352 352  
353 353  DOWNLINK
354 354  
355 355  
356 356  
357 -[[image:image-20220601144053-5.png]]
348 +[[image:image-20220527093530-18.png]]
358 358  
359 359  DOWNLINK
360 360  
361 361  
362 362  
363 -[[image:image-20220601143921-4.png]]
354 +[[image:image-20220527093607-19.png]]
364 364  
365 365  DOWNLINK
366 366  
367 367  
368 368  
369 -[[image:image-20220601142805-5.png]]
360 +[[image:image-20220527093628-20.png]]
370 370  
371 371  DOWNLINK
372 372  
... ... @@ -391,8 +391,6 @@
391 391  
392 392  (((
393 393  check digit: Even
394 -
395 -
396 396  )))
397 397  
398 398  [[image:image-20220527093708-21.png]]
... ... @@ -409,18 +409,14 @@
409 409  
410 410  (((
411 411  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.
412 -
413 -
414 414  )))
415 415  
416 416  (((
417 -(% 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
418 418  )))
419 419  
420 420  (((
421 421   output:01 03 04 00 00 00 42 7A 02
422 -
423 -
424 424  )))
425 425  
426 426  [[image:image-20220527093821-23.png]]
... ... @@ -430,7 +430,6 @@
430 430  
431 431  === **1.3.5 How to configure multiple devices and modify device addresses** ===
432 432  
433 -
434 434  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.
435 435  
436 436  (((
... ... @@ -442,14 +442,12 @@
442 442  [[image:image-20220601142044-1.png]]
443 443  
444 444  
445 -(% 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.
446 446  
447 447  [[image:image-20220527093950-25.png]]
448 448  
449 -
450 450  [[image:image-20220527094028-26.png]]
451 451  
452 -
453 453  (((
454 454  (((
455 455  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.
... ... @@ -458,7 +458,7 @@
458 458  
459 459  (((
460 460  (((
461 -We can use **AT+CFGDEV** to set the device address.
443 +We can use AT+CFGDEV to set the device address.
462 462  )))
463 463  )))
464 464  
... ... @@ -470,7 +470,6 @@
470 470  
471 471  [[image:image-20220601142354-2.png]]
472 472  
473 -
474 474  (% class="box infomessage" %)
475 475  (((
476 476  **AT+CFGDEV:01 10 00 61 00 01 02 00 02,1**
... ... @@ -496,52 +496,46 @@
496 496  
497 497  Its default device address is 01, and the following are the parameters for configuring two energy meters.
498 498  
499 -[[image:image-20220601142452-3.png]]
480 +[[image:image-20220527094150-28.png]]
500 500  
501 501  
502 -[[image:image-20220601142607-4.png]]
483 +[[image:image-20220527094224-29.png]]
503 503  
504 -
505 505  **PAYLOAD:01 08 DF 43 62**
506 506  
507 507  * 08 DF is the valid value of the meter with device address 02.
508 508  * 43 62 is the valid value of the meter with device address 01.
509 509  
490 +
510 510  == 1.4 Example 4: Circuit Breaker Remote Open Close ==
511 511  
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:
512 512  
513 -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.
514 -
515 -The structure is like below:
516 -
517 517  [[image:image-20220527094330-30.png]]
518 518  
519 519  Connection
520 520  
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
521 521  
522 -* 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/]]
523 523  
524 524  == 1.5 Example 5: SEM Three Energy Meter with RS485-BL or RS485-LN ==
525 525  
526 -
527 527  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:
528 528  
529 -* 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);"]]
530 -* 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
531 531  
532 -== 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
533 533  
510 +== 1.6 Example 6:CEM C31 485-T1-MID Energy Meter with RS485-LN ==
534 534  
535 535  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:
536 536  
537 -* 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
538 538  
539 -== 1.7 Example 7: Schneider Electric PLC M221 with RS485-BL ==
516 +== 1.7 Example 7:Schneider Electric PLC M221 with RS485-BL ==
540 540  
541 -
542 542  [[image:image-20220527094556-31.png]]
543 543  
544 544  Network Structure
545 545  
546 -
547 547  * [[Reference Instruction>>url:https://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Schneider%20Electric%20PLC/]]
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
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0