Last modified by Karry Zhuang on 2024/07/11 11:58
<
From version < 41.16 >
edited by Xiaoling
on 2022/06/01 14:15
To version < 37.1 >
edited by Xiaoling
on 2022/05/27 09:45
>
Change comment: Uploaded new attachment "image-20220527094556-31.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -3,18 +3,12 @@
3 3  
4 4  {{toc/}}
5 5  
6 += 1. Introduction =
6 6  
7 -
8 -
9 -
10 -
11 -= **1. Introduction** =
12 -
13 13  This article provide the examples for RS485-LN to connect to different type of RS485 sensors.
14 14  
10 +== 1.1 Example 1: Connect to Leak relay and VFD ==
15 15  
16 -== **1.1 Example 1: Connect to Leak relay and VFD** ==
17 -
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]]
... ... @@ -34,10 +34,8 @@
34 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.
35 35  * [[Video Demo>>url:https://www.youtube.com/watch?v=TAFZ5eaf-MY&t=6s&ab_channel=XavierFlorensaBerenguer]]
36 36  
31 +== 1.2 Example 2: Connect to Pulse Counter ==
37 37  
38 -
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 43  [[image:image-20220527092058-3.png]]
... ... @@ -45,20 +45,18 @@
45 45  Connection
46 46  
47 47  
48 -
49 49  [[image:image-20220527092146-4.png]]
50 50  
51 51  Connection
52 52  
53 -
54 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
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 57  == ==
58 58  
59 -== **1.3 Example3: Use RS485-LN with energy meters** ==
49 +== 1.3 Example3: Use RS485-LN with energy meters ==
60 60  
61 -=== **1.3.1 OverView** ===
51 +=== 1.3.1 OverView ===
62 62  
63 63  (((
64 64  **Note**：The specifications of each energy meter are different, please refer to your own energy meter specifications.
... ... @@ -73,7 +73,6 @@
73 73  Connection1
74 74  
75 75  
76 -
77 77  (((
78 78  How to connect with Energy Meter：
79 79  )))
... ... @@ -103,13 +103,12 @@
103 103  Connection2
104 104  
105 105  
106 -
107 107  [[image:image-20220527092555-7.png]]
108 108  
109 109  Connection3
110 110  
111 111  
112 -=== **1.3.2 How to use the parameters of the energy meter and MODBUS commands** ===
100 +=== 1.3.2 How to use the parameters of the energy meter and MODBUS commands ===
113 113  
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  
... ... @@ -148,12 +148,12 @@
148 148  
149 149  )))
150 150  
151 -=== **1.3.3 How to configure RS485-LN and parse output commands** ===
139 +=== 1.3.3 How to configure RS485-LN and parse output commands ===
152 152  
153 153  RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK.
154 154  
155 155  
156 -==== **1.3.3.1 via AT COMMAND:** ====
144 +==== 1.3.3.1 via AT COMMAND: ====
157 157  
158 158  First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct.
159 159  
... ... @@ -171,11 +171,11 @@
171 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
172 172  )))
173 173  
174 -a:  length for the return of AT+COMMAND
162 +a: length for the return of AT+COMMAND
175 175  
176 -b: 1: grab valid value by byte, max 6 bytes;  2: grab valid value by bytes section, max 3 sections.
164 +b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.
177 177  
178 -c:  define the position for valid value.
166 +c: define the position for valid value.
179 179  
180 180  [[image:image-20220527092936-10.png]]
181 181  
... ... @@ -182,7 +182,6 @@
182 182  AT COMMAND
183 183  
184 184  
185 -
186 186  PAYLOAD is available after the valid value is intercepted.
187 187  
188 188  
... ... @@ -191,7 +191,6 @@
191 191  AT COMMAND
192 192  
193 193  
194 -
195 195  You can get configured PAYLOAD on TTN.
196 196  
197 197  [[image:image-20220527093133-12.png]]
... ... @@ -205,9 +205,7 @@
205 205  )))
206 206  
207 207  (((
208 -(% style="color:#4f81bd" %)**Example**:
209 -
210 -CMD1:Read current data with MODBUS command. address:0x03 AT+COMMAND1= 01 03 00 03 00 01,1
194 +**Example**: CMD1:Read current data with MODBUS command. address:0x03 AT+COMMAND1= 01 03 00 03 00 01,1
211 211  )))
212 212  
213 213  (((
... ... @@ -216,8 +216,6 @@
216 216  
217 217  (((
218 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.
219 -
220 -
221 221  )))
222 222  
223 223  (((
... ... @@ -230,8 +230,6 @@
230 230  
231 231  (((
232 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.
233 -
234 -
235 235  )))
236 236  
237 237  (((
... ... @@ -262,7 +262,7 @@
262 262  AT COMMAND
263 263  
264 264  
265 -==== **1.3.3.2 via LoRaWAN DOWNLINK** ====
245 +==== 1.3.3.2 via LoRaWAN DOWNLINK ====
266 266  
267 267  [[image:image-20220527093358-15.png]]
268 268  
... ... @@ -275,7 +275,7 @@
275 275  )))
276 276  
277 277  (((
278 -(% style="color:#4f81bd" %)**Type Code 0xAF**
258 +**Type Code 0xAF**
279 279  )))
280 280  
281 281  (((
... ... @@ -322,11 +322,11 @@
322 322  )))
323 323  
324 324  (((
325 -(% style="color:#4f81bd" %)**Example:**
305 +Example:
326 326  )))
327 327  
328 328  (((
329 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
309 +AF 03 01 06 0A 05 00 04 00 01 00: Same as AT+COMMAND3=0A 05 00 04 00 01,1
330 330  )))
331 331  
332 332  [[image:image-20220527093430-16.png]]
... ... @@ -354,7 +354,7 @@
354 354  DOWNLINK
355 355  
356 356  
357 -=== **1.3.4 How to configure and output commands for RS485 to USB** ===
337 +=== 1.3.4 How to configure and output commands for RS485 to USB ===
358 358  
359 359  (((
360 360  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.
... ... @@ -391,7 +391,7 @@
391 391  )))
392 392  
393 393  (((
394 -(% style="color:#4f81bd" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
374 +**Example:**  input：01 03 00 31 00 02 95 c4
395 395  )))
396 396  
397 397  (((
... ... @@ -403,7 +403,7 @@
403 403  USB
404 404  
405 405  
406 -=== **1.3.5 How to configure multiple devices and modify device addresses** ===
386 +=== 1.3.5 How to configure multiple devices and modify device addresses ===
407 407  
408 408  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.
409 409  
... ... @@ -472,7 +472,7 @@
472 472  
473 473  [[image:image-20220527094224-29.png]]
474 474  
475 -**PAYLOAD:01 08 DF 43 62**
455 +PAYLOAD:01 08 DF 43 62
476 476  
477 477  * 08 DF is the valid value of the meter with device address 02.
478 478  * 43 62 is the valid value of the meter with device address 01.
... ... @@ -505,7 +505,7 @@
505 505  
506 506  == 1.7 Example 7:Schneider Electric PLC M221 with RS485-BL ==
507 507  
508 -[[image:image-20220527094556-31.png]]
488 +[[image:https://wiki.dragino.com/images/thumb/9/97/PLC_M221.png/600px-PLC_M221.png||height="353" width="600"]]
509 509  
510 510  Network Structure
511 511  

Applications

Navigation

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