Last modified by Karry Zhuang on 2024/07/11 11:58
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -3,12 +3,18 @@ 3 3 4 4 {{toc/}} 5 5 6 -= 1. Introduction = 7 7 7 + 8 + 9 + 10 + 11 += **1. Introduction** = 12 + 8 8 This article provide the examples for RS485-LN to connect to different type of RS485 sensors. 9 9 10 -== 1.1 Example 1: Connect to Leak relay and VFD == 11 11 16 +== **1.1 Example 1: Connect to Leak relay and VFD** == 17 + 12 12 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: 13 13 14 14 [[image:image-20220527091852-1.png]] ... ... @@ -28,8 +28,10 @@ 28 28 * [[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. 29 29 * [[Video Demo>>url:https://www.youtube.com/watch?v=TAFZ5eaf-MY&t=6s&ab_channel=XavierFlorensaBerenguer]] 30 30 31 -== 1.2 Example 2: Connect to Pulse Counter == 32 32 38 + 39 +== **1.2 Example 2: Connect to Pulse Counter** == 40 + 33 33 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: 34 34 35 35 [[image:image-20220527092058-3.png]] ... ... @@ -37,18 +37,20 @@ 37 37 Connection 38 38 39 39 48 + 40 40 [[image:image-20220527092146-4.png]] 41 41 42 42 Connection 43 43 53 + 44 44 * [[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 45 45 * [[Dragino Solution in Farm>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/&file=Dragino%20on%20Farms.pptx]] 46 46 47 47 == == 48 48 49 -== 1.3 Example3: Use RS485-LN with energy meters == 59 +== **1.3 Example3: Use RS485-LN with energy meters** == 50 50 51 -=== 1.3.1 OverView === 61 +=== **1.3.1 OverView** === 52 52 53 53 ((( 54 54 **Note**:The specifications of each energy meter are different, please refer to your own energy meter specifications. ... ... @@ -63,6 +63,7 @@ 63 63 Connection1 64 64 65 65 76 + 66 66 ((( 67 67 How to connect with Energy Meter: 68 68 ))) ... ... @@ -92,12 +92,13 @@ 92 92 Connection2 93 93 94 94 106 + 95 95 [[image:image-20220527092555-7.png]] 96 96 97 97 Connection3 98 98 99 99 100 -=== 1.3.2 How to use the parameters of the energy meter and MODBUS commands === 112 +=== **1.3.2 How to use the parameters of the energy meter and MODBUS commands** === 101 101 102 102 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. 103 103 ... ... @@ -136,12 +136,12 @@ 136 136 137 137 ))) 138 138 139 -=== 1.3.3 How to configure RS485-LN and parse output commands === 151 +=== **1.3.3 How to configure RS485-LN and parse output commands** === 140 140 141 141 RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK. 142 142 143 143 144 -==== 1.3.3.1 via AT COMMAND: ==== 156 +==== **1.3.3.1 via AT COMMAND:** ==== 145 145 146 146 First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct. 147 147 ... ... @@ -159,11 +159,11 @@ 159 159 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 160 ))) 161 161 162 -a: length for the return of AT+COMMAND 174 +a: length for the return of AT+COMMAND 163 163 164 -b:1: grab valid value by byte, max 6 bytes .2: grab valid value by bytes section, max 3 sections.176 +b: 1: grab valid value by byte, max 6 bytes; 2: grab valid value by bytes section, max 3 sections. 165 165 166 -c: define the position for valid value. 178 +c: define the position for valid value. 167 167 168 168 [[image:image-20220527092936-10.png]] 169 169 ... ... @@ -170,6 +170,7 @@ 170 170 AT COMMAND 171 171 172 172 185 + 173 173 PAYLOAD is available after the valid value is intercepted. 174 174 175 175 ... ... @@ -191,7 +191,9 @@ 191 191 ))) 192 192 193 193 ((( 194 -**Example**: CMD1:Read current data with MODBUS command. address:0x03 AT+COMMAND1= 01 03 00 03 00 01,1 207 +(% style="color:#4f81bd" %)**Example**: 208 + 209 +CMD1:Read current data with MODBUS command. address:0x03 AT+COMMAND1= 01 03 00 03 00 01,1 195 195 ))) 196 196 197 197 ((( ... ... @@ -200,6 +200,8 @@ 200 200 201 201 ((( 202 202 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. 218 + 219 + 203 203 ))) 204 204 205 205 ((( ... ... @@ -212,6 +212,8 @@ 212 212 213 213 ((( 214 214 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. 232 + 233 + 215 215 ))) 216 216 217 217 ((( ... ... @@ -242,7 +242,7 @@ 242 242 AT COMMAND 243 243 244 244 245 -==== 1.3.3.2 via LoRaWAN DOWNLINK ==== 264 +==== **1.3.3.2 via LoRaWAN DOWNLINK** ==== 246 246 247 247 [[image:image-20220527093358-15.png]] 248 248 ... ... @@ -255,7 +255,7 @@ 255 255 ))) 256 256 257 257 ((( 258 -**Type Code 0xAF** 277 +(% style="color:#4f81bd" %)**Type Code 0xAF** 259 259 ))) 260 260 261 261 ((( ... ... @@ -302,11 +302,11 @@ 302 302 ))) 303 303 304 304 ((( 305 -Example: 324 +(% style="color:#4f81bd" %)**Example:** 306 306 ))) 307 307 308 308 ((( 309 -AF 03 01 06 0A 05 00 04 00 01 00: Same as AT+COMMAND3=0A 05 00 04 00 01,1 328 +**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1 310 310 ))) 311 311 312 312 [[image:image-20220527093430-16.png]] ... ... @@ -334,7 +334,7 @@ 334 334 DOWNLINK 335 335 336 336 337 -=== 1.3.4 How to configure and output commands for RS485 to USB === 356 +=== **1.3.4 How to configure and output commands for RS485 to USB** === 338 338 339 339 ((( 340 340 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. ... ... @@ -371,7 +371,7 @@ 371 371 ))) 372 372 373 373 ((( 374 -**Example:** input:01 03 00 31 00 02 95 c4 393 +(% style="color:#4f81bd" %)**Example:** (%%)input:01 03 00 31 00 02 95 c4 375 375 ))) 376 376 377 377 ((( ... ... @@ -383,7 +383,7 @@ 383 383 USB 384 384 385 385 386 -=== 1.3.5 How to configure multiple devices and modify device addresses === 405 +=== **1.3.5 How to configure multiple devices and modify device addresses** === 387 387 388 388 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. 389 389 ... ... @@ -452,7 +452,7 @@ 452 452 453 453 [[image:image-20220527094224-29.png]] 454 454 455 -PAYLOAD:01 08 DF 43 62 474 +**PAYLOAD:01 08 DF 43 62** 456 456 457 457 * 08 DF is the valid value of the meter with device address 02. 458 458 * 43 62 is the valid value of the meter with device address 01. ... ... @@ -485,7 +485,7 @@ 485 485 486 486 == 1.7 Example 7:Schneider Electric PLC M221 with RS485-BL == 487 487 488 -[[image: https://wiki.dragino.com/images/thumb/9/97/PLC_M221.png/600px-PLC_M221.png||height="353" width="600"]]507 +[[image:image-20220527094556-31.png]] 489 489 490 490 Network Structure 491 491
- image-20220527094556-31.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +162.5 KB - Content