Last modified by Karry Zhuang on 2024/07/11 11:58
<
From version < 39.2 >
edited by Xiaoling
on 2022/05/27 09:47
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,31 +193,37 @@
193 193  )))
194 194  
195 195  (((
196 -**Example**: CMD1:Read current data with MODBUS command. address:0x03 AT+COMMAND1= 01 03 00 03 00 01,1
215 +(% style="color:blue" %)**Example**:
216 +
217 +CMD1:Read current data with MODBUS command. address: 0x03 AT+COMMAND1= 01 03 00 03 00 01,1
197 197  )))
198 198  
199 199  (((
200 -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)
201 201  )))
202 202  
203 203  (((
204 -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.
226 +
227 +
205 205  )))
206 206  
207 207  (((
208 -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
209 209  )))
210 210  
211 211  (((
212 -RETURN2:01 03 02 08 DC BE 1D(return data)
235 +RETURN2: 01 03 02 08 DC BE 1D(return data)
213 213  )))
214 214  
215 215  (((
216 -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.
240 +
241 +
217 217  )))
218 218  
219 219  (((
220 -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
221 221  )))
222 222  
223 223  (((
... ... @@ -225,14 +225,14 @@
225 225  )))
226 226  
227 227  (((
228 -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.
229 229  )))
230 230  
231 231  (((
232 -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
233 233  )))
234 234  
235 -[[image:image-20220527093204-13.png]]
260 +[[image:image-20220601142936-6.png]]
236 236  
237 237  AT COMMAND
238 238  
... ... @@ -239,13 +239,16 @@
239 239  
240 240  (% 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.**
241 241  
242 -[[image:image-20220527093251-14.png]]
243 243  
268 +
269 +[[image:image-20220601143642-2.png]]
270 +
244 244  AT COMMAND
245 245  
246 246  
247 -==== 1.3.3.2 via LoRaWAN DOWNLINK ====
274 +==== **1.3.3.2 via LoRaWAN DOWNLINK** ====
248 248  
276 +
249 249  [[image:image-20220527093358-15.png]]
250 250  
251 251  (((
... ... @@ -257,7 +257,7 @@
257 257  )))
258 258  
259 259  (((
260 -**Type Code 0xAF**
288 +(% style="color:#4f81bd" %)**Type Code 0xAF**
261 261  )))
262 262  
263 263  (((
... ... @@ -304,39 +304,45 @@
304 304  )))
305 305  
306 306  (((
307 -Example:
335 +
336 +
337 +(% style="color:#4f81bd" %)**Example:**
308 308  )))
309 309  
310 310  (((
311 -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
312 312  )))
313 313  
314 -[[image:image-20220527093430-16.png]]
344 +[[image:image-20220601144149-6.png]]
315 315  
316 316  DOWNLINK
317 317  
318 318  
319 -[[image:image-20220527093508-17.png]]
320 320  
350 +[[image:image-20220601143803-3.png]]
351 +
321 321  DOWNLINK
322 322  
323 323  
324 -[[image:image-20220527093530-18.png]]
325 325  
356 +[[image:image-20220601144053-5.png]]
357 +
326 326  DOWNLINK
327 327  
328 328  
329 -[[image:image-20220527093607-19.png]]
330 330  
362 +[[image:image-20220601143921-4.png]]
363 +
331 331  DOWNLINK
332 332  
333 333  
334 -[[image:image-20220527093628-20.png]]
335 335  
368 +[[image:image-20220601142805-5.png]]
369 +
336 336  DOWNLINK
337 337  
338 338  
339 -=== 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** ===
340 340  
341 341  (((
342 342  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.
... ... @@ -363,17 +363,19 @@
363 363  USB
364 364  
365 365  
400 +
366 366  [[image:image-20220527093747-22.png]]
367 367  
368 368  USB
369 369  
370 370  
406 +
371 371  (((
372 372  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.
373 373  )))
374 374  
375 375  (((
376 -**Example:**  input：01 03 00 31 00 02 95 c4
412 +(% style="color:#4f81bd" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
377 377  )))
378 378  
379 379  (((
... ... @@ -385,7 +385,7 @@
385 385  USB
386 386  
387 387  
388 -=== 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** ===
389 389  
390 390  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.
391 391  
... ... @@ -395,7 +395,7 @@
395 395  )))
396 396  )))
397 397  
398 -[[image:image-20220527093849-24.png]]
434 +[[image:image-20220601142044-1.png]]
399 399  
400 400  
401 401  **Example**:These two meters are examples of setting parameters and device addresses.
... ... @@ -402,6 +402,7 @@
402 402  
403 403  [[image:image-20220527093950-25.png]]
404 404  
441 +
405 405  [[image:image-20220527094028-26.png]]
406 406  
407 407  (((
... ... @@ -422,7 +422,7 @@
422 422  )))
423 423  )))
424 424  
425 -[[image:image-20220527094100-27.png]]
462 +[[image:image-20220601142354-2.png]]
426 426  
427 427  (% class="box infomessage" %)
428 428  (((
... ... @@ -449,12 +449,12 @@
449 449  
450 450  Its default device address is 01, and the following are the parameters for configuring two energy meters.
451 451  
452 -[[image:image-20220527094150-28.png]]
489 +[[image:image-20220601142452-3.png]]
453 453  
454 454  
455 -[[image:image-20220527094224-29.png]]
492 +[[image:image-20220601142607-4.png]]
456 456  
457 -PAYLOAD:01 08 DF 43 62
494 +**PAYLOAD:01 08 DF 43 62**
458 458  
459 459  * 08 DF is the valid value of the meter with device address 02.
460 460  * 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