Last modified by Karry Zhuang on 2024/07/11 11:58
<
From version < 45.2 >
edited by Xiaoling
on 2022/06/01 14:26
To version < 57.27 >
edited by Xiaoling
on 2022/07/14 10:18
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,4 @@
1 -(% class="wikigeneratedid" %)
2 - **Contents:**
1 +**Table of Contents:**
3 3  
4 4  {{toc/}}
5 5  
... ... @@ -10,11 +10,13 @@
10 10  
11 11  = **1. Introduction** =
12 12  
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 +
18 18  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:
19 19  
20 20  [[image:image-20220527091852-1.png]]
... ... @@ -28,18 +28,19 @@
28 28  Connection
29 29  
30 30  
31 -Related documents:
32 +(% style="color:blue" %)**Related documents:**
32 32  
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.
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);"]]
35 35  * [[Video Demo>>url:https://www.youtube.com/watch?v=TAFZ5eaf-MY&t=6s&ab_channel=XavierFlorensaBerenguer]]
36 36  
37 37  
38 -
39 39  == **1.2 Example 2: Connect to Pulse Counter** ==
40 40  
41 +
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  
44 +
43 43  [[image:image-20220527092058-3.png]]
44 44  
45 45  Connection
... ... @@ -51,17 +51,20 @@
51 51  Connection
52 52  
53 53  
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
56 +(% style="color:blue" %)**Related documents:**
57 +
58 +* 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/]]
55 55  * [[Dragino Solution in Farm>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/&file=Dragino%20on%20Farms.pptx]]
56 56  
57 -== ==
58 58  
59 59  == **1.3 Example3: Use RS485-LN with energy meters** ==
60 60  
64 +
61 61  === **1.3.1 OverView** ===
62 62  
67 +
63 63  (((
64 -**Note**：The specifications of each energy meter are different, please refer to your own energy meter specifications.
69 +(% style="color:red" %)**Note**：The specifications of each energy meter are different, please refer to your own energy meter specifications.
65 65  )))
66 66  
67 67  (((
... ... @@ -75,7 +75,9 @@
75 75  
76 76  
77 77  (((
78 -How to connect with Energy Meter：
83 +(% style="color:blue" %)**How to connect with Energy Meter：**
84 +
85 +
79 79  )))
80 80  
81 81  (((
... ... @@ -103,23 +103,21 @@
103 103  Connection2
104 104  
105 105  
106 -
107 107  [[image:image-20220527092555-7.png]]
108 108  
109 109  Connection3
110 110  
111 111  
118 +
112 112  === **1.3.2 How to use the parameters of the energy meter and MODBUS commands** ===
113 113  
121 +
114 114  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.
115 115  
116 -[[image:image-20220527092629-8.png]]
124 +[[image:image-20220601143257-10.png]]
117 117  
118 118  
119 -(% class="box infomessage" %)
120 -(((
121 -**Example:** AT+COMMAND1=01 03 00 00 00 01 84 0A
122 -)))
127 +(% style="color:blue" %)**Example:**(%%)  AT+COMMAND1=01 03 00 00 00 01 84 0A
123 123  
124 124  * The first byte : slave address code (=001～247)
125 125  * The second byte : read register value function code
... ... @@ -128,12 +128,12 @@
128 128  * 7th and 8th bytes: CRC16 checksum from bytes 1 to 6.
129 129  
130 130  (((
136 +
137 +
138 +
131 131  How to parse the reading of the return command of the parameter：
132 -)))
133 133  
134 -(% class="box infomessage" %)
135 -(((
136 -**Example:** RETURN1：01 03 02 08 FD 7E 05
141 +(% style="color:blue" %)**Example:**(%%) RETURN1：01 03 02 08 FD 7E 05
137 137  )))
138 138  
139 139  * The first byte ARD: slave address code (=001～254)
... ... @@ -146,22 +146,28 @@
146 146  (% class="wikigeneratedid" %)
147 147  (((
148 148  
154 +
155 +
156 +
149 149  )))
150 150  
151 151  === **1.3.3 How to configure RS485-LN and parse output commands** ===
152 152  
161 +
153 153  RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK.
154 154  
155 155  
156 -==== **1.3.3.1 via AT COMMAND:** ====
157 157  
158 -First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct.
166 +==== **1.3.3.1 via AT COMMAND** ====
159 159  
168 +
169 +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.
170 +
160 160  (((
161 161  If the configured parameters and commands are incorrect, the return value is not obtained.
162 162  )))
163 163  
164 -[[image:image-20220527092748-9.png]]
175 +[[image:image-20220601143201-9.png]]
165 165  
166 166  AT COMMAND
167 167  
... ... @@ -168,7 +168,7 @@
168 168  
169 169  (% class="box infomessage" %)
170 170  (((
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
182 + **AT+DATACUTx **:  This command defines how to handle the return from AT+COMMANDx, max reture length is 40 bytes. AT+DATACUTx=a,b,c
172 172  )))
173 173  
174 174  a:  length for the return of AT+COMMAND
... ... @@ -177,7 +177,7 @@
177 177  
178 178  c:  define the position for valid value.
179 179  
180 -[[image:image-20220527092936-10.png]]
191 +[[image:image-20220601143115-8.png]]
181 181  
182 182  AT COMMAND
183 183  
... ... @@ -186,7 +186,7 @@
186 186  PAYLOAD is available after the valid value is intercepted.
187 187  
188 188  
189 -[[image:image-20220527093059-11.png]]
200 +[[image:image-20220601143046-7.png]]
190 190  
191 191  AT COMMAND
192 192  
... ... @@ -194,7 +194,7 @@
194 194  
195 195  You can get configured PAYLOAD on TTN.
196 196  
197 -[[image:image-20220527093133-12.png]]
208 +[[image:image-20220601143519-1.png]]
198 198  
199 199  (((
200 200  AT COMMAND
... ... @@ -205,52 +205,52 @@
205 205  )))
206 206  
207 207  (((
208 -(% style="color:#4f81bd" %)**Example**:
219 +(% style="color:blue" %)**Example**:
209 209  
210 -CMD1:Read current data with MODBUS command. address:0x03 AT+COMMAND1= 01 03 00 03 00 01,1
221 +(% style="color:red" %)**CMD1:**(%%) Read current data with MODBUS command. address: 0x03 AT+COMMAND1= 01 03 00 03 00 01,1
211 211  )))
212 212  
213 213  (((
214 -RETURN1:01 03 02 00 02 39 85 00 00(return data)
225 +RETURN1: 01 03 02 00 02 39 85 00 00(return data)
215 215  )))
216 216  
217 217  (((
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.
229 +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.
219 219  
220 220  
221 221  )))
222 222  
223 223  (((
224 -CMD2:Read voltage data with MODBUS command. address:0x00 AT+COMMAND2= 01 03 00 00 00 01,1
235 +(% style="color:red" %)**CMD2: **(%%)Read voltage data with MODBUS command. address: 0x00 AT+COMMAND2= 01 03 00 00 00 01,1
225 225  )))
226 226  
227 227  (((
228 -RETURN2:01 03 02 08 DC BE 1D(return data)
239 +RETURN2: 01 03 02 08 DC BE 1D(return data)
229 229  )))
230 230  
231 231  (((
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.
243 +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.
233 233  
234 234  
235 235  )))
236 236  
237 237  (((
238 -CMD3:Read total active energy data with MODBUS command. address:0x0031 AT+COMMAND3= 01 03 00 31 00 02,1
249 +(% style="color:red" %)**CMD3:**(%%) Read total active energy data with MODBUS command. address: 0x0031 AT+COMMAND3= 01 03 00 31 00 02,1
239 239  )))
240 240  
241 241  (((
242 -RETURN3:01 03 04 00 00 00 44 FA 00(return data)
253 +RETURN3: 01 03 04 00 00 00 44 FA 00(return data)
243 243  )))
244 244  
245 245  (((
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.
257 +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.
247 247  )))
248 248  
249 249  (((
250 -Payload:01 00 02 39 85 08 DC 00 00 00 44
261 +Payload: 01 00 02 39 85 08 DC 00 00 00 44
251 251  )))
252 252  
253 -[[image:image-20220527093204-13.png]]
264 +[[image:image-20220601142936-6.png]]
254 254  
255 255  AT COMMAND
256 256  
... ... @@ -258,14 +258,15 @@
258 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.**
259 259  
260 260  
272 +[[image:image-20220601143642-2.png]]
261 261  
262 -[[image:image-20220527093251-14.png]]
263 -
264 264  AT COMMAND
265 265  
266 266  
277 +
267 267  ==== **1.3.3.2 via LoRaWAN DOWNLINK** ====
268 268  
280 +
269 269  [[image:image-20220527093358-15.png]]
270 270  
271 271  (((
... ... @@ -288,7 +288,7 @@
288 288  )))
289 289  
290 290  (((
291 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
303 +(% style="color:red" %)**Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.**
292 292  )))
293 293  
294 294  (((
... ... @@ -326,7 +326,7 @@
326 326  (((
327 327  
328 328  
329 -(% style="color:#4f81bd" %)**Example:**
341 +(% style="color:blue" %)**Example:**
330 330  )))
331 331  
332 332  (((
... ... @@ -333,35 +333,36 @@
333 333  **AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
334 334  )))
335 335  
336 -[[image:image-20220527093430-16.png]]
348 +[[image:image-20220601144149-6.png]]
337 337  
338 338  DOWNLINK
339 339  
340 340  
341 341  
342 -[[image:image-20220527093508-17.png]]
354 +[[image:image-20220601143803-3.png]]
343 343  
344 344  DOWNLINK
345 345  
346 346  
347 347  
348 -[[image:image-20220527093530-18.png]]
360 +[[image:image-20220601144053-5.png]]
349 349  
350 350  DOWNLINK
351 351  
352 352  
353 353  
354 -[[image:image-20220527093607-19.png]]
366 +[[image:image-20220601143921-4.png]]
355 355  
356 356  DOWNLINK
357 357  
358 358  
359 359  
360 -[[image:image-20220527093628-20.png]]
372 +[[image:image-20220601142805-5.png]]
361 361  
362 362  DOWNLINK
363 363  
364 364  
377 +
365 365  === **1.3.4 How to configure and output commands for RS485 to USB** ===
366 366  
367 367  (((
... ... @@ -382,6 +382,8 @@
382 382  
383 383  (((
384 384  check digit: Even
398 +
399 +
385 385  )))
386 386  
387 387  [[image:image-20220527093708-21.png]]
... ... @@ -398,14 +398,18 @@
398 398  
399 399  (((
400 400  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.
416 +
417 +
401 401  )))
402 402  
403 403  (((
404 -(% style="color:#4f81bd" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
421 +(% style="color:blue" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
405 405  )))
406 406  
407 407  (((
408 408   output：01 03 04 00 00 00 42 7A 02
426 +
427 +
409 409  )))
410 410  
411 411  [[image:image-20220527093821-23.png]]
... ... @@ -413,8 +413,10 @@
413 413  USB
414 414  
415 415  
435 +
416 416  === **1.3.5 How to configure multiple devices and modify device addresses** ===
417 417  
438 +
418 418  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.
419 419  
420 420  (((
... ... @@ -426,12 +426,14 @@
426 426  [[image:image-20220601142044-1.png]]
427 427  
428 428  
429 -**Example**:These two meters are examples of setting parameters and device addresses.
450 +(% style="color:blue" %)**Example**(%%): These two meters are examples of setting parameters and device addresses.
430 430  
431 431  [[image:image-20220527093950-25.png]]
432 432  
454 +
433 433  [[image:image-20220527094028-26.png]]
434 434  
457 +
435 435  (((
436 436  (((
437 437  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.
... ... @@ -440,7 +440,7 @@
440 440  
441 441  (((
442 442  (((
443 -We can use AT+CFGDEV to set the device address.
466 +We can use (% style="color:blue" %)**AT+CFGDEV**(%%) to set the device address.
444 444  )))
445 445  )))
446 446  
... ... @@ -452,6 +452,7 @@
452 452  
453 453  [[image:image-20220601142354-2.png]]
454 454  
478 +
455 455  (% class="box infomessage" %)
456 456  (((
457 457  **AT+CFGDEV:01 10 00 61 00 01 02 00 02,1**
... ... @@ -482,43 +482,55 @@
482 482  
483 483  [[image:image-20220601142607-4.png]]
484 484  
485 -**PAYLOAD:01 08 DF 43 62**
486 486  
510 +(% style="color:blue" %)**PAYLOAD: 01 08 DF 43 62**
511 +
487 487  * 08 DF is the valid value of the meter with device address 02.
488 488  * 43 62 is the valid value of the meter with device address 01.
489 489  
490 490  
516 +
491 491  == 1.4 Example 4: Circuit Breaker Remote Open Close ==
492 492  
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:
494 494  
520 +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.
521 +
522 +The structure is like below:
523 +
495 495  [[image:image-20220527094330-30.png]]
496 496  
497 497  Connection
498 498  
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
500 500  
529 +* 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/]]
501 501  
531 +
532 +
502 502  == 1.5 Example 5: SEM Three Energy Meter with RS485-BL or RS485-LN ==
503 503  
535 +
504 504  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:
505 505  
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
538 +* 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);"]]
539 +* 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]]
507 507  
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
509 509  
510 510  
543 +== 1.6 Example 6: CEM C31 485-T1-MID Energy Meter with RS485-LN ==
511 511  
512 -== 1.6 Example 6:CEM C31 485-T1-MID Energy Meter with RS485-LN ==
513 513  
514 514  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:
515 515  
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
548 +* 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);"]]
517 517  
518 -== 1.7 Example 7:Schneider Electric PLC M221 with RS485-BL ==
519 519  
551 +
552 +== 1.7 Example 7: Schneider Electric PLC M221 with RS485-BL ==
553 +
554 +
520 520  [[image:image-20220527094556-31.png]]
521 521  
522 522  Network Structure
523 523  
559 +
524 524  * [[Reference Instruction>>url:https://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Schneider%20Electric%20PLC/]]
image-20220601142805-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +35.8 KB
Content
image-20220601142936-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.7 KB
Content
image-20220601143046-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +11.2 KB
Content
image-20220601143115-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +11.9 KB
Content
image-20220601143201-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +16.5 KB
Content
image-20220601143257-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +9.1 KB
Content
image-20220601143519-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +13.2 KB
Content
image-20220601143642-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +41.4 KB
Content
image-20220601143803-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.8 KB
Content
image-20220601143921-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +29.2 KB
Content
image-20220601144053-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +17.1 KB
Content
image-20220601144149-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +17.4 KB
Content

Applications

Navigation

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