Last modified by Karry Zhuang on 2024/07/11 11:58
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 16 added, 0 removed)
- image-20220601142044-1.png
- image-20220601142354-2.png
- image-20220601142452-3.png
- image-20220601142607-4.png
- image-20220601142805-5.png
- image-20220601142936-6.png
- image-20220601143046-7.png
- image-20220601143115-8.png
- image-20220601143201-9.png
- image-20220601143257-10.png
- image-20220601143519-1.png
- image-20220601143642-2.png
- image-20220601143803-3.png
- image-20220601143921-4.png
- image-20220601144053-5.png
- image-20220601144149-6.png
Details
- Page properties
-
- Content
-
... ... @@ -1,15 +1,22 @@ 1 1 (% class="wikigeneratedid" %) 2 - **Contents:** 2 + ** Table of** **Contents:** 3 3 4 4 {{toc/}} 5 5 6 -= 1. Introduction = 7 7 7 + 8 + 9 + 10 + 11 += **1. Introduction** = 12 + 13 + 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 == 17 +== **1.1 Example 1: Connect to Leak relay and VFD** == 12 12 19 + 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,28 +29,36 @@ 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 32 -== 1.2 Example 2: Connect to Pulse Counter == 33 33 40 + 41 + 42 +== **1.2 Example 2: Connect to Pulse Counter** == 43 + 44 + 34 34 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: 35 35 47 + 36 36 [[image:image-20220527092058-3.png]] 37 37 38 38 Connection 39 39 40 40 53 + 41 41 [[image:image-20220527092146-4.png]] 42 42 43 43 Connection 44 44 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 + 59 +* 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/]] 46 46 * [[Dragino Solution in Farm>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/&file=Dragino%20on%20Farms.pptx]] 47 47 48 -== == 49 49 50 -== 1.3 Example3: Use RS485-LN with energy meters == 51 51 52 -=== 1.3.1 OverView === 53 53 65 +== **1.3 Example3: Use RS485-LN with energy meters** == 66 + 67 +=== **1.3.1 OverView** === 68 + 54 54 ((( 55 55 **Note**:The specifications of each energy meter are different, please refer to your own energy meter specifications. 56 56 ))) ... ... @@ -64,6 +64,7 @@ 64 64 Connection1 65 65 66 66 82 + 67 67 ((( 68 68 How to connect with Energy Meter: 69 69 ))) ... ... @@ -93,16 +93,17 @@ 93 93 Connection2 94 94 95 95 112 + 96 96 [[image:image-20220527092555-7.png]] 97 97 98 98 Connection3 99 99 100 100 101 -=== 1.3.2 How to use the parameters of the energy meter and MODBUS commands === 118 +=== **1.3.2 How to use the parameters of the energy meter and MODBUS commands** === 102 102 103 103 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. 104 104 105 -[[image:image-20220 527092629-8.png]]122 +[[image:image-20220601143257-10.png]] 106 106 107 107 108 108 (% class="box infomessage" %) ... ... @@ -137,12 +137,12 @@ 137 137 138 138 ))) 139 139 140 -=== 1.3.3 How to configure RS485-LN and parse output commands === 157 +=== **1.3.3 How to configure RS485-LN and parse output commands** === 141 141 142 142 RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK. 143 143 144 144 145 -==== 1.3.3.1 via AT COMMAND: ==== 162 +==== **1.3.3.1 via AT COMMAND:** ==== 146 146 147 147 First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct. 148 148 ... ... @@ -150,7 +150,7 @@ 150 150 If the configured parameters and commands are incorrect, the return value is not obtained. 151 151 ))) 152 152 153 -[[image:image-20220 527092748-9.png]]170 +[[image:image-20220601143201-9.png]] 154 154 155 155 AT COMMAND 156 156 ... ... @@ -160,28 +160,30 @@ 160 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 161 161 ))) 162 162 163 -a: length for the return of AT+COMMAND 180 +a: length for the return of AT+COMMAND 164 164 165 -b:1: grab valid value by byte, max 6 bytes .2: grab valid value by bytes section, max 3 sections.182 +b: 1: grab valid value by byte, max 6 bytes; 2: grab valid value by bytes section, max 3 sections. 166 166 167 -c: define the position for valid value. 184 +c: define the position for valid value. 168 168 169 -[[image:image-20220 527092936-10.png]]186 +[[image:image-20220601143115-8.png]] 170 170 171 171 AT COMMAND 172 172 173 173 191 + 174 174 PAYLOAD is available after the valid value is intercepted. 175 175 176 176 177 -[[image:image-20220 527093059-11.png]]195 +[[image:image-20220601143046-7.png]] 178 178 179 179 AT COMMAND 180 180 181 181 200 + 182 182 You can get configured PAYLOAD on TTN. 183 183 184 -[[image:image-20220 527093133-12.png]]203 +[[image:image-20220601143519-1.png]] 185 185 186 186 ((( 187 187 AT COMMAND ... ... @@ -192,7 +192,9 @@ 192 192 ))) 193 193 194 194 ((( 195 -**Example**: CMD1:Read current data with MODBUS command. address:0x03 AT+COMMAND1= 01 03 00 03 00 01,1 214 +(% style="color:#4f81bd" %)**Example**: 215 + 216 +CMD1:Read current data with MODBUS command. address:0x03 AT+COMMAND1= 01 03 00 03 00 01,1 196 196 ))) 197 197 198 198 ((( ... ... @@ -201,6 +201,8 @@ 201 201 202 202 ((( 203 203 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 + 226 + 204 204 ))) 205 205 206 206 ((( ... ... @@ -213,6 +213,8 @@ 213 213 214 214 ((( 215 215 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 + 240 + 216 216 ))) 217 217 218 218 ((( ... ... @@ -231,7 +231,7 @@ 231 231 Payload:01 00 02 39 85 08 DC 00 00 00 44 232 232 ))) 233 233 234 -[[image:image-20220 527093204-13.png]]259 +[[image:image-20220601142936-6.png]] 235 235 236 236 AT COMMAND 237 237 ... ... @@ -238,12 +238,14 @@ 238 238 239 239 (% 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.** 240 240 241 -[[image:image-20220527093251-14.png]] 242 242 267 + 268 +[[image:image-20220601143642-2.png]] 269 + 243 243 AT COMMAND 244 244 245 245 246 -==== 1.3.3.2 via LoRaWAN DOWNLINK ==== 273 +==== **1.3.3.2 via LoRaWAN DOWNLINK** ==== 247 247 248 248 [[image:image-20220527093358-15.png]] 249 249 ... ... @@ -256,7 +256,7 @@ 256 256 ))) 257 257 258 258 ((( 259 -**Type Code 0xAF** 286 +(% style="color:#4f81bd" %)**Type Code 0xAF** 260 260 ))) 261 261 262 262 ((( ... ... @@ -303,39 +303,45 @@ 303 303 ))) 304 304 305 305 ((( 306 -Example: 333 + 334 + 335 +(% style="color:#4f81bd" %)**Example:** 307 307 ))) 308 308 309 309 ((( 310 -AF 03 01 06 0A 05 00 04 00 01 00: Same as AT+COMMAND3=0A 05 00 04 00 01,1 339 +**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1 311 311 ))) 312 312 313 -[[image:image-20220 527093430-16.png]]342 +[[image:image-20220601144149-6.png]] 314 314 315 315 DOWNLINK 316 316 317 317 318 -[[image:image-20220527093508-17.png]] 319 319 348 +[[image:image-20220601143803-3.png]] 349 + 320 320 DOWNLINK 321 321 322 322 323 -[[image:image-20220527093530-18.png]] 324 324 354 +[[image:image-20220601144053-5.png]] 355 + 325 325 DOWNLINK 326 326 327 327 328 -[[image:image-20220527093607-19.png]] 329 329 360 +[[image:image-20220601143921-4.png]] 361 + 330 330 DOWNLINK 331 331 332 332 333 -[[image:image-20220527093628-20.png]] 334 334 366 +[[image:image-20220601142805-5.png]] 367 + 335 335 DOWNLINK 336 336 337 337 338 -=== 1.3.4 How to configure and output commands for RS485 to USB === 371 +=== **1.3.4 How to configure and output commands for RS485 to USB** === 339 339 340 340 ((( 341 341 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. ... ... @@ -362,17 +362,19 @@ 362 362 USB 363 363 364 364 398 + 365 365 [[image:image-20220527093747-22.png]] 366 366 367 367 USB 368 368 369 369 404 + 370 370 ((( 371 371 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. 372 372 ))) 373 373 374 374 ((( 375 -**Example:** input:01 03 00 31 00 02 95 c4 410 +(% style="color:#4f81bd" %)**Example:** (%%)input:01 03 00 31 00 02 95 c4 376 376 ))) 377 377 378 378 ((( ... ... @@ -384,7 +384,7 @@ 384 384 USB 385 385 386 386 387 -=== 1.3.5 How to configure multiple devices and modify device addresses === 422 +=== **1.3.5 How to configure multiple devices and modify device addresses** === 388 388 389 389 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. 390 390 ... ... @@ -394,7 +394,7 @@ 394 394 ))) 395 395 ))) 396 396 397 -[[image:image-20220 527093849-24.png]]432 +[[image:image-20220601142044-1.png]] 398 398 399 399 400 400 **Example**:These two meters are examples of setting parameters and device addresses. ... ... @@ -401,6 +401,7 @@ 401 401 402 402 [[image:image-20220527093950-25.png]] 403 403 439 + 404 404 [[image:image-20220527094028-26.png]] 405 405 406 406 ((( ... ... @@ -421,7 +421,7 @@ 421 421 ))) 422 422 ))) 423 423 424 -[[image:image-20220 527094100-27.png]]460 +[[image:image-20220601142354-2.png]] 425 425 426 426 (% class="box infomessage" %) 427 427 ((( ... ... @@ -448,16 +448,17 @@ 448 448 449 449 Its default device address is 01, and the following are the parameters for configuring two energy meters. 450 450 451 -[[image:image-20220 527094150-28.png]]487 +[[image:image-20220601142452-3.png]] 452 452 453 453 454 -[[image:image-20220 527094224-29.png]]490 +[[image:image-20220601142607-4.png]] 455 455 456 -PAYLOAD:01 08 DF 43 62 492 +**PAYLOAD:01 08 DF 43 62** 457 457 458 458 * 08 DF is the valid value of the meter with device address 02. 459 459 * 43 62 is the valid value of the meter with device address 01. 460 460 497 + 461 461 == 1.4 Example 4: Circuit Breaker Remote Open Close == 462 462 463 463 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:
- 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