Last modified by Karry Zhuang on 2024/07/11 11:58
<
From version < 57.10 >
edited by Xiaoling
on 2022/07/14 09:35
To version < 39.4 >
edited by Xiaoling
on 2022/05/27 09:52
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,23 +1,15 @@
1 1  (% class="wikigeneratedid" %)
2 -*
3 -** Table of** **Contents:
2 + **Contents:**
4 4  
5 5  {{toc/}}
6 6  
6 += 1. Introduction =
7 7  
8 -
9 -
10 -
11 -
12 -= **1. Introduction** =
13 -
14 -
15 15  This article provide the examples for RS485-LN to connect to different type of RS485 sensors.
16 16  
17 17  
18 -== **1.1 Example 1: Connect to Leak relay and VFD** ==
11 +== 1.1 Example 1: Connect to Leak relay and VFD ==
19 19  
20 -
21 21  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:
22 22  
23 23  [[image:image-20220527091852-1.png]]
... ... @@ -37,33 +37,30 @@
37 37  * [[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.
38 38  * [[Video Demo>>url:https://www.youtube.com/watch?v=TAFZ5eaf-MY&t=6s&ab_channel=XavierFlorensaBerenguer]]
39 39  
40 -== **1.2 Example 2: Connect to Pulse Counter** ==
32 +== 1.2 Example 2: Connect to Pulse Counter ==
41 41  
42 -
43 43  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:
44 44  
45 -
46 46  [[image:image-20220527092058-3.png]]
47 47  
48 48  Connection
49 49  
50 50  
51 -
52 52  [[image:image-20220527092146-4.png]]
53 53  
54 54  Connection
55 55  
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/]]
45 +* [[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  
60 -== **1.3 Example3: Use RS485-LN with energy meters** ==
48 +== ==
61 61  
62 -=== **1.3.1 OverView** ===
50 +== 1.3 Example3: Use RS485-LN with energy meters ==
63 63  
52 +=== 1.3.1 OverView ===
64 64  
65 65  (((
66 -(% style="color:red" %)**Note**：The specifications of each energy meter are different, please refer to your own energy meter specifications.
55 +**Note**：The specifications of each energy meter are different, please refer to your own energy meter specifications.
67 67  )))
68 68  
69 69  (((
... ... @@ -75,11 +75,8 @@
75 75  Connection1
76 76  
77 77  
78 -
79 79  (((
80 -**How to connect with Energy Meter：**
81 -
82 -
68 +How to connect with Energy Meter：
83 83  )))
84 84  
85 85  (((
... ... @@ -107,21 +107,22 @@
107 107  Connection2
108 108  
109 109  
110 -
111 111  [[image:image-20220527092555-7.png]]
112 112  
113 113  Connection3
114 114  
115 115  
116 -=== **1.3.2 How to use the parameters of the energy meter and MODBUS commands** ===
101 +=== 1.3.2 How to use the parameters of the energy meter and MODBUS commands ===
117 117  
118 -
119 119  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.
120 120  
121 -[[image:image-20220601143257-10.png]]
105 +[[image:image-20220527092629-8.png]]
122 122  
123 123  
124 -(% style="color:blue" %)**Example:**(%%)  AT+COMMAND1=01 03 00 00 00 01 84 0A
108 +(% class="box infomessage" %)
109 +(((
110 +**Example:** AT+COMMAND1=01 03 00 00 00 01 84 0A
111 +)))
125 125  
126 126  * The first byte : slave address code (=001～247)
127 127  * The second byte : read register value function code
... ... @@ -130,12 +130,12 @@
130 130  * 7th and 8th bytes: CRC16 checksum from bytes 1 to 6.
131 131  
132 132  (((
133 -
134 -
135 -
136 136  How to parse the reading of the return command of the parameter：
121 +)))
137 137  
138 -(% style="color:blue" %)**Example:**(%%) RETURN1：01 03 02 08 FD 7E 05
123 +(% class="box infomessage" %)
124 +(((
125 +**Example:** RETURN1：01 03 02 08 FD 7E 05
139 139  )))
140 140  
141 141  * The first byte ARD: slave address code (=001～254)
... ... @@ -148,27 +148,22 @@
148 148  (% class="wikigeneratedid" %)
149 149  (((
150 150  
151 -
152 -
153 -
154 154  )))
155 155  
156 -=== **1.3.3 How to configure RS485-LN and parse output commands** ===
140 +=== 1.3.3 How to configure RS485-LN and parse output commands ===
157 157  
158 -
159 159  RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK.
160 160  
161 161  
162 -==== **1.3.3.1 via AT COMMAND** ====
145 +==== 1.3.3.1 via AT COMMAND: ====
163 163  
147 +First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct.
164 164  
165 -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.
166 -
167 167  (((
168 168  If the configured parameters and commands are incorrect, the return value is not obtained.
169 169  )))
170 170  
171 -[[image:image-20220601143201-9.png]]
153 +[[image:image-20220527092748-9.png]]
172 172  
173 173  AT COMMAND
174 174  
... ... @@ -175,33 +175,31 @@
175 175  
176 176  (% class="box infomessage" %)
177 177  (((
178 - **AT+DATACUTx **:  This command defines how to handle the return from AT+COMMANDx, max reture length is 40 bytes. AT+DATACUTx=a,b,c
160 + AT+DATACUTx : This command defines how to handle the return from AT+COMMANDx, max reture length is 40 bytes. AT+DATACUTx=a,b,c
179 179  )))
180 180  
181 -a:  length for the return of AT+COMMAND
163 +a: length for the return of AT+COMMAND
182 182  
183 -b: 1: grab valid value by byte, max 6 bytes;  2: grab valid value by bytes section, max 3 sections.
165 +b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.
184 184  
185 -c:  define the position for valid value.
167 +c: define the position for valid value.
186 186  
187 -[[image:image-20220601143115-8.png]]
169 +[[image:image-20220527092936-10.png]]
188 188  
189 189  AT COMMAND
190 190  
191 191  
192 -
193 193  PAYLOAD is available after the valid value is intercepted.
194 194  
195 195  
196 -[[image:image-20220601143046-7.png]]
177 +[[image:image-20220527093059-11.png]]
197 197  
198 198  AT COMMAND
199 199  
200 200  
201 -
202 202  You can get configured PAYLOAD on TTN.
203 203  
204 -[[image:image-20220601143519-1.png]]
184 +[[image:image-20220527093133-12.png]]
205 205  
206 206  (((
207 207  AT COMMAND
... ... @@ -212,52 +212,52 @@
212 212  )))
213 213  
214 214  (((
215 -(% style="color:blue" %)**Example**:
195 +(% style="color:#4f81bd" %)**Example**:
216 216  
217 -CMD1: Read current data with MODBUS command. address: 0x03 AT+COMMAND1= 01 03 00 03 00 01,1
197 +CMD1:Read current data with MODBUS command. address:0x03 AT+COMMAND1= 01 03 00 03 00 01,1
218 218  )))
219 219  
220 220  (((
221 -RETURN1: 01 03 02 00 02 39 85 00 00(return data)
201 +RETURN1:01 03 02 00 02 39 85 00 00(return data)
222 222  )))
223 223  
224 224  (((
225 -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.
205 +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.
226 226  
227 227  
228 228  )))
229 229  
230 230  (((
231 -CMD2: Read voltage data with MODBUS command. address: 0x00 AT+COMMAND2= 01 03 00 00 00 01,1
211 +CMD2:Read voltage data with MODBUS command. address:0x00 AT+COMMAND2= 01 03 00 00 00 01,1
232 232  )))
233 233  
234 234  (((
235 -RETURN2: 01 03 02 08 DC BE 1D(return data)
215 +RETURN2:01 03 02 08 DC BE 1D(return data)
236 236  )))
237 237  
238 238  (((
239 -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.
219 +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.
240 240  
241 241  
242 242  )))
243 243  
244 244  (((
245 -CMD3: Read total active energy data with MODBUS command. address: 0x0031 AT+COMMAND3= 01 03 00 31 00 02,1
225 +CMD3:Read total active energy data with MODBUS command. address:0x0031 AT+COMMAND3= 01 03 00 31 00 02,1
246 246  )))
247 247  
248 248  (((
249 -RETURN3: 01 03 04 00 00 00 44 FA 00(return data)
229 +RETURN3:01 03 04 00 00 00 44 FA 00(return data)
250 250  )))
251 251  
252 252  (((
253 -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.
233 +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.
254 254  )))
255 255  
256 256  (((
257 -Payload: 01 00 02 39 85 08 DC 00 00 00 44
237 +Payload:01 00 02 39 85 08 DC 00 00 00 44
258 258  )))
259 259  
260 -[[image:image-20220601142936-6.png]]
240 +[[image:image-20220527093204-13.png]]
261 261  
262 262  AT COMMAND
263 263  
... ... @@ -264,15 +264,13 @@
264 264  
265 265  (% 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.**
266 266  
247 +[[image:image-20220527093251-14.png]]
267 267  
268 -[[image:image-20220601143642-2.png]]
269 -
270 270  AT COMMAND
271 271  
272 272  
273 -==== **1.3.3.2 via LoRaWAN DOWNLINK** ====
252 +==== 1.3.3.2 via LoRaWAN DOWNLINK ====
274 274  
275 -
276 276  [[image:image-20220527093358-15.png]]
277 277  
278 278  (((
... ... @@ -331,8 +331,6 @@
331 331  )))
332 332  
333 333  (((
334 -
335 -
336 336  (% style="color:#4f81bd" %)**Example:**
337 337  )))
338 338  
... ... @@ -340,36 +340,32 @@
340 340  **AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
341 341  )))
342 342  
343 -[[image:image-20220601144149-6.png]]
319 +[[image:image-20220527093430-16.png]]
344 344  
345 345  DOWNLINK
346 346  
347 347  
324 +[[image:image-20220527093508-17.png]]
348 348  
349 -[[image:image-20220601143803-3.png]]
350 -
351 351  DOWNLINK
352 352  
353 353  
329 +[[image:image-20220527093530-18.png]]
354 354  
355 -[[image:image-20220601144053-5.png]]
356 -
357 357  DOWNLINK
358 358  
359 359  
334 +[[image:image-20220527093607-19.png]]
360 360  
361 -[[image:image-20220601143921-4.png]]
362 -
363 363  DOWNLINK
364 364  
365 365  
339 +[[image:image-20220527093628-20.png]]
366 366  
367 -[[image:image-20220601142805-5.png]]
368 -
369 369  DOWNLINK
370 370  
371 371  
372 -=== **1.3.4 How to configure and output commands for RS485 to USB** ===
344 +=== 1.3.4 How to configure and output commands for RS485 to USB ===
373 373  
374 374  (((
375 375  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.
... ... @@ -396,13 +396,11 @@
396 396  USB
397 397  
398 398  
399 -
400 400  [[image:image-20220527093747-22.png]]
401 401  
402 402  USB
403 403  
404 404  
405 -
406 406  (((
407 407  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.
408 408  )))
... ... @@ -420,7 +420,7 @@
420 420  USB
421 421  
422 422  
423 -=== **1.3.5 How to configure multiple devices and modify device addresses** ===
393 +=== 1.3.5 How to configure multiple devices and modify device addresses ===
424 424  
425 425  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.
426 426  
... ... @@ -430,7 +430,7 @@
430 430  )))
431 431  )))
432 432  
433 -[[image:image-20220601142044-1.png]]
403 +[[image:image-20220527093849-24.png]]
434 434  
435 435  
436 436  **Example**:These two meters are examples of setting parameters and device addresses.
... ... @@ -437,7 +437,6 @@
437 437  
438 438  [[image:image-20220527093950-25.png]]
439 439  
440 -
441 441  [[image:image-20220527094028-26.png]]
442 442  
443 443  (((
... ... @@ -458,7 +458,7 @@
458 458  )))
459 459  )))
460 460  
461 -[[image:image-20220601142354-2.png]]
430 +[[image:image-20220527094100-27.png]]
462 462  
463 463  (% class="box infomessage" %)
464 464  (((
... ... @@ -485,12 +485,12 @@
485 485  
486 486  Its default device address is 01, and the following are the parameters for configuring two energy meters.
487 487  
488 -[[image:image-20220601142452-3.png]]
457 +[[image:image-20220527094150-28.png]]
489 489  
490 490  
491 -[[image:image-20220601142607-4.png]]
460 +[[image:image-20220527094224-29.png]]
492 492  
493 -**PAYLOAD:01 08 DF 43 62**
462 +PAYLOAD:01 08 DF 43 62
494 494  
495 495  * 08 DF is the valid value of the meter with device address 02.
496 496  * 43 62 is the valid value of the meter with device address 01.
image-20220601142044-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -3.7 KB
Content
image-20220601142354-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -2.8 KB
Content
image-20220601142452-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -28.1 KB
Content
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

Applications

Navigation

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