Last modified by Karry Zhuang on 2024/07/11 11:58
<
From version < 39.3 >
edited by Xiaoling
on 2022/05/27 09:49
To version < 57.8 >
edited by Xiaoling
on 2022/07/14 09:33
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,15 +1,23 @@
1 1  (% class="wikigeneratedid" %)
2 - **Contents:**
2 +*
3 +** Table of** **Contents:
3 3  
4 4  {{toc/}}
5 5  
6 -= 1. Introduction =
7 7  
8 +
9 +
10 +
11 +
12 += **1. Introduction** =
13 +
14 +
8 8  This article provide the examples for RS485-LN to connect to different type of RS485 sensors.
9 9  
10 10  
11 -== 1.1 Example 1: Connect to Leak relay and VFD ==
18 +== **1.1 Example 1: Connect to Leak relay and VFD** ==
12 12  
20 +
13 13  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:
14 14  
15 15  [[image:image-20220527091852-1.png]]
... ... @@ -29,31 +29,33 @@
29 29  * [[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.
30 30  * [[Video Demo>>url:https://www.youtube.com/watch?v=TAFZ5eaf-MY&t=6s&ab_channel=XavierFlorensaBerenguer]]
31 31  
40 +== **1.2 Example 2: Connect to Pulse Counter** ==
32 32  
33 -== 1.2 Example 2: Connect to Pulse Counter ==
34 34  
35 35  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:
36 36  
45 +
37 37  [[image:image-20220527092058-3.png]]
38 38  
39 39  Connection
40 40  
41 41  
51 +
42 42  [[image:image-20220527092146-4.png]]
43 43  
44 44  Connection
45 45  
46 -* [[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 +
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/]]
47 47  * [[Dragino Solution in Farm>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/&file=Dragino%20on%20Farms.pptx]]
48 48  
49 -== ==
60 +== **1.3 Example3: Use RS485-LN with energy meters** ==
50 50  
51 -== 1.3 Example3: Use RS485-LN with energy meters ==
62 +=== **1.3.1 OverView** ===
52 52  
53 -=== 1.3.1 OverView ===
54 54  
55 55  (((
56 -**Note**：The specifications of each energy meter are different, please refer to your own energy meter specifications.
66 +(% style="color:red" %)**Note**：The specifications of each energy meter are different, please refer to your own energy meter specifications.
57 57  )))
58 58  
59 59  (((
... ... @@ -65,8 +65,11 @@
65 65  Connection1
66 66  
67 67  
78 +
68 68  (((
69 -How to connect with Energy Meter：
80 +**How to connect with Energy Meter：**
81 +
82 +
70 70  )))
71 71  
72 72  (((
... ... @@ -94,22 +94,21 @@
94 94  Connection2
95 95  
96 96  
110 +
97 97  [[image:image-20220527092555-7.png]]
98 98  
99 99  Connection3
100 100  
101 101  
102 -=== 1.3.2 How to use the parameters of the energy meter and MODBUS commands ===
116 +=== **1.3.2 How to use the parameters of the energy meter and MODBUS commands** ===
103 103  
118 +
104 104  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.
105 105  
106 -[[image:image-20220527092629-8.png]]
121 +[[image:image-20220601143257-10.png]]
107 107  
108 108  
109 -(% class="box infomessage" %)
110 -(((
111 -**Example:** AT+COMMAND1=01 03 00 00 00 01 84 0A
112 -)))
124 +(% style="color:blue" %)**Example:**(%%)  AT+COMMAND1=01 03 00 00 00 01 84 0A
113 113  
114 114  * The first byte : slave address code (=001～247)
115 115  * The second byte : read register value function code
... ... @@ -118,12 +118,12 @@
118 118  * 7th and 8th bytes: CRC16 checksum from bytes 1 to 6.
119 119  
120 120  (((
133 +
134 +
135 +
121 121  How to parse the reading of the return command of the parameter：
122 -)))
123 123  
124 -(% class="box infomessage" %)
125 -(((
126 -**Example:** RETURN1：01 03 02 08 FD 7E 05
138 +(% style="color:blue" %)**Example:**(%%) RETURN1：01 03 02 08 FD 7E 05
127 127  )))
128 128  
129 129  * The first byte ARD: slave address code (=001～254)
... ... @@ -136,22 +136,27 @@
136 136  (% class="wikigeneratedid" %)
137 137  (((
138 138  
151 +
152 +
153 +
139 139  )))
140 140  
141 -=== 1.3.3 How to configure RS485-LN and parse output commands ===
156 +=== **1.3.3 How to configure RS485-LN and parse output commands** ===
142 142  
158 +
143 143  RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK.
144 144  
145 145  
146 -==== 1.3.3.1 via AT COMMAND: ====
162 +==== **1.3.3.1 via AT COMMAND** ====
147 147  
148 -First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct.
149 149  
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 +
150 150  (((
151 151  If the configured parameters and commands are incorrect, the return value is not obtained.
152 152  )))
153 153  
154 -[[image:image-20220527092748-9.png]]
171 +[[image:image-20220601143201-9.png]]
155 155  
156 156  AT COMMAND
157 157  
... ... @@ -158,31 +158,33 @@
158 158  
159 159  (% class="box infomessage" %)
160 160  (((
161 - AT+DATACUTx : This command defines how to handle the return from AT+COMMANDx, max reture length is 40 bytes. AT+DATACUTx=a,b,c
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
162 162  )))
163 163  
164 -a: length for the return of AT+COMMAND
181 +a:  length for the return of AT+COMMAND
165 165  
166 -b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.
183 +b: 1: grab valid value by byte, max 6 bytes;  2: grab valid value by bytes section, max 3 sections.
167 167  
168 -c: define the position for valid value.
185 +c:  define the position for valid value.
169 169  
170 -[[image:image-20220527092936-10.png]]
187 +[[image:image-20220601143115-8.png]]
171 171  
172 172  AT COMMAND
173 173  
174 174  
192 +
175 175  PAYLOAD is available after the valid value is intercepted.
176 176  
177 177  
178 -[[image:image-20220527093059-11.png]]
196 +[[image:image-20220601143046-7.png]]
179 179  
180 180  AT COMMAND
181 181  
182 182  
201 +
183 183  You can get configured PAYLOAD on TTN.
184 184  
185 -[[image:image-20220527093133-12.png]]
204 +[[image:image-20220601143519-1.png]]
186 186  
187 187  (((
188 188  AT COMMAND
... ... @@ -193,37 +193,37 @@
193 193  )))
194 194  
195 195  (((
196 -**Example**:
215 +(% style="color:blue" %)**Example**:
197 197  
198 -CMD1:Read current data with MODBUS command. address:0x03 AT+COMMAND1= 01 03 00 03 00 01,1
217 +CMD1:Read current data with MODBUS command. address: 0x03 AT+COMMAND1= 01 03 00 03 00 01,1
199 199  )))
200 200  
201 201  (((
202 -RETURN1:01 03 02 00 02 39 85 00 00(return data)
221 +RETURN1: 01 03 02 00 02 39 85 00 00(return data)
203 203  )))
204 204  
205 205  (((
206 -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.
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.
207 207  
208 208  
209 209  )))
210 210  
211 211  (((
212 -CMD2:Read voltage data with MODBUS command. address:0x00 AT+COMMAND2= 01 03 00 00 00 01,1
231 +CMD2: Read voltage data with MODBUS command. address: 0x00 AT+COMMAND2= 01 03 00 00 00 01,1
213 213  )))
214 214  
215 215  (((
216 -RETURN2:01 03 02 08 DC BE 1D(return data)
235 +RETURN2: 01 03 02 08 DC BE 1D(return data)
217 217  )))
218 218  
219 219  (((
220 -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.
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.
221 221  
222 222  
223 223  )))
224 224  
225 225  (((
226 -CMD3:Read total active energy data with MODBUS command. address:0x0031 AT+COMMAND3= 01 03 00 31 00 02,1
245 +CMD3: Read total active energy data with MODBUS command. address: 0x0031 AT+COMMAND3= 01 03 00 31 00 02,1
227 227  )))
228 228  
229 229  (((
... ... @@ -231,14 +231,14 @@
231 231  )))
232 232  
233 233  (((
234 -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.
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.
235 235  )))
236 236  
237 237  (((
238 -Payload:01 00 02 39 85 08 DC 00 00 00 44
257 +Payload: 01 00 02 39 85 08 DC 00 00 00 44
239 239  )))
240 240  
241 -[[image:image-20220527093204-13.png]]
260 +[[image:image-20220601142936-6.png]]
242 242  
243 243  AT COMMAND
244 244  
... ... @@ -245,13 +245,16 @@
245 245  
246 246  (% 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.**
247 247  
248 -[[image:image-20220527093251-14.png]]
249 249  
268 +
269 +[[image:image-20220601143642-2.png]]
270 +
250 250  AT COMMAND
251 251  
252 252  
253 -==== 1.3.3.2 via LoRaWAN DOWNLINK ====
274 +==== **1.3.3.2 via LoRaWAN DOWNLINK** ====
254 254  
276 +
255 255  [[image:image-20220527093358-15.png]]
256 256  
257 257  (((
... ... @@ -263,7 +263,7 @@
263 263  )))
264 264  
265 265  (((
266 -**Type Code 0xAF**
288 +(% style="color:#4f81bd" %)**Type Code 0xAF**
267 267  )))
268 268  
269 269  (((
... ... @@ -310,39 +310,45 @@
310 310  )))
311 311  
312 312  (((
313 -Example:
335 +
336 +
337 +(% style="color:#4f81bd" %)**Example:**
314 314  )))
315 315  
316 316  (((
317 -AF 03 01 06 0A 05 00 04 00 01 00: Same as AT+COMMAND3=0A 05 00 04 00 01,1
341 +**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
318 318  )))
319 319  
320 -[[image:image-20220527093430-16.png]]
344 +[[image:image-20220601144149-6.png]]
321 321  
322 322  DOWNLINK
323 323  
324 324  
325 -[[image:image-20220527093508-17.png]]
326 326  
350 +[[image:image-20220601143803-3.png]]
351 +
327 327  DOWNLINK
328 328  
329 329  
330 -[[image:image-20220527093530-18.png]]
331 331  
356 +[[image:image-20220601144053-5.png]]
357 +
332 332  DOWNLINK
333 333  
334 334  
335 -[[image:image-20220527093607-19.png]]
336 336  
362 +[[image:image-20220601143921-4.png]]
363 +
337 337  DOWNLINK
338 338  
339 339  
340 -[[image:image-20220527093628-20.png]]
341 341  
368 +[[image:image-20220601142805-5.png]]
369 +
342 342  DOWNLINK
343 343  
344 344  
345 -=== 1.3.4 How to configure and output commands for RS485 to USB ===
373 +=== **1.3.4 How to configure and output commands for RS485 to USB** ===
346 346  
347 347  (((
348 348  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.
... ... @@ -369,17 +369,19 @@
369 369  USB
370 370  
371 371  
400 +
372 372  [[image:image-20220527093747-22.png]]
373 373  
374 374  USB
375 375  
376 376  
406 +
377 377  (((
378 378  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.
379 379  )))
380 380  
381 381  (((
382 -**Example:**  input：01 03 00 31 00 02 95 c4
412 +(% style="color:#4f81bd" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
383 383  )))
384 384  
385 385  (((
... ... @@ -391,7 +391,7 @@
391 391  USB
392 392  
393 393  
394 -=== 1.3.5 How to configure multiple devices and modify device addresses ===
424 +=== **1.3.5 How to configure multiple devices and modify device addresses** ===
395 395  
396 396  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.
397 397  
... ... @@ -401,7 +401,7 @@
401 401  )))
402 402  )))
403 403  
404 -[[image:image-20220527093849-24.png]]
434 +[[image:image-20220601142044-1.png]]
405 405  
406 406  
407 407  **Example**:These two meters are examples of setting parameters and device addresses.
... ... @@ -408,6 +408,7 @@
408 408  
409 409  [[image:image-20220527093950-25.png]]
410 410  
441 +
411 411  [[image:image-20220527094028-26.png]]
412 412  
413 413  (((
... ... @@ -428,7 +428,7 @@
428 428  )))
429 429  )))
430 430  
431 -[[image:image-20220527094100-27.png]]
462 +[[image:image-20220601142354-2.png]]
432 432  
433 433  (% class="box infomessage" %)
434 434  (((
... ... @@ -455,12 +455,12 @@
455 455  
456 456  Its default device address is 01, and the following are the parameters for configuring two energy meters.
457 457  
458 -[[image:image-20220527094150-28.png]]
489 +[[image:image-20220601142452-3.png]]
459 459  
460 460  
461 -[[image:image-20220527094224-29.png]]
492 +[[image:image-20220601142607-4.png]]
462 462  
463 -PAYLOAD:01 08 DF 43 62
494 +**PAYLOAD:01 08 DF 43 62**
464 464  
465 465  * 08 DF is the valid value of the meter with device address 02.
466 466  * 43 62 is the valid value of the meter with device address 01.
image-20220601142044-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +3.7 KB
Content
image-20220601142354-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +2.8 KB
Content
image-20220601142452-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +28.1 KB
Content
image-20220601142607-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.9 KB
Content
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