Last modified by Karry Zhuang on 2024/07/11 11:58
Change comment:
Uploaded new attachment "image-20220601143201-9.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 20 removed)
- 1720669739434-926.png
- 1720669744315-613.png
- 1720669933691-331.png
- 1720669944339-942.png
- 1720669981767-254.png
- 1720670003601-544.png
- 1720670016539-422.png
- 1720670019136-658.png
- 1720670035661-234.png
- 1720670038725-366.png
- 1720670041974-372.png
- 1720670079781-764.png
- 1720670090204-634.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
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. karry1 +XWiki.Xiaoling - Content
-
... ... @@ -1,4 +1,5 @@ 1 -**Table of Contents:** 1 +(% class="wikigeneratedid" %) 2 + **Contents:** 2 2 3 3 {{toc/}} 4 4 ... ... @@ -7,67 +7,60 @@ 7 7 8 8 9 9 10 -= 1. Introduction = 11 += **1. Introduction** = 11 11 12 - 13 13 This article provide the examples for RS485-LN to connect to different type of RS485 sensors. 14 14 15 15 16 -== 1.1 Example 1: Connect to Leak relay and VFD == 16 +== **1.1 Example 1: Connect to Leak relay and VFD** == 17 17 18 - 19 19 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: 20 20 20 +[[image:image-20220527091852-1.png]] 21 21 22 - [[image:image-20220527091852-1.png||height="547" width="994"]]22 +Connection 23 23 24 -**Connection** 25 25 26 26 27 27 [[image:image-20220527091942-2.png]](% style="display:none" %) 28 28 29 - **Connection**28 +Connection 30 30 31 31 32 - (% style="color:blue" %)**Related documents:**31 +Related documents: 33 33 34 -* System Structure: [[Solar Pump with Dragino>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Relay_VFD/||_mstmutation="1" style="background-color: rgb(255, 255, 255);"]] 35 - 36 -* Explanation on how to integrate to Node-red and to the Mobile Phone, and with link to the Github code: [[Configure Manual>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Relay_VFD/||_mstmutation="1" style="background-color: rgb(255, 255, 255);"]] 37 - 33 +* [[Solar Pump with Dragino>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Relay_VFD/]] : System Structure 34 +* [[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 40 41 -== 1.2 Example 2: Connect to Pulse Counter == 42 42 39 +== **1.2 Example 2: Connect to Pulse Counter** == 43 43 44 44 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: 45 45 43 +[[image:image-20220527092058-3.png]] 46 46 47 - [[image:image-20220527092058-3.png||height="552" width="905"]]45 +Connection 48 48 49 -**Connection** 50 50 51 51 52 -[[image:image-20220527092146-4.png ||height="507" width="906"]]49 +[[image:image-20220527092146-4.png]] 53 53 54 - **Connection**51 +Connection 55 55 56 56 57 -(% style="color:blue" %)**Related documents:** 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/||_mstmutation="1"]] 60 - 54 +* [[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 61 61 * [[Dragino Solution in Farm>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/&file=Dragino%20on%20Farms.pptx]] 62 62 57 +== == 63 63 64 -== 1.3 Example 59 +== **1.3 Example3: Use RS485-LN with energy meters** == 65 65 66 -=== 1.3.1 OverView === 61 +=== **1.3.1 OverView** === 67 67 68 - 69 69 ((( 70 - (% style="color:red" %)**Note**:**The specifications of each energy meter are different, please refer to your own energy meter specifications.**64 +**Note**:The specifications of each energy meter are different, please refer to your own energy meter specifications. 71 71 ))) 72 72 73 73 ((( ... ... @@ -76,13 +76,12 @@ 76 76 77 77 [[image:image-20220527092419-5.png]] 78 78 79 - **Connection1**73 +Connection1 80 80 81 81 82 -((( 83 -(% style="color:blue" %)**How to connect with Energy Meter:** 84 84 85 - 77 +((( 78 +How to connect with Energy Meter: 86 86 ))) 87 87 88 88 ((( ... ... @@ -94,11 +94,11 @@ 94 94 ))) 95 95 96 96 ((( 97 -Power Source **VIN**to RS485-LN**VIN+**90 +Power Source VIN to RS485-LN VIN+ 98 98 ))) 99 99 100 100 ((( 101 -Power Source **GND**to RS485-LN**VIN-**94 +Power Source GND to RS485-LN VIN- 102 102 ))) 103 103 104 104 ((( ... ... @@ -107,81 +107,75 @@ 107 107 108 108 [[image:image-20220527092514-6.png]] 109 109 110 - **Connection2**103 +Connection2 111 111 112 112 106 + 113 113 [[image:image-20220527092555-7.png]] 114 114 115 - **Connection3**109 +Connection3 116 116 117 117 118 -=== 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** === 119 119 120 - 121 121 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. 122 122 123 -[[image:image-20220 601143257-10.png]]116 +[[image:image-20220527092629-8.png]] 124 124 125 125 126 -(% style="color:blue" %)**Example:**(%%) AT+COMMAND1=01 03 00 00 00 01 84 0A 119 +(% class="box infomessage" %) 120 +((( 121 +**Example:** AT+COMMAND1=01 03 00 00 00 01 84 0A 122 +))) 127 127 128 128 * The first byte : slave address code (=001~247) 129 - 130 130 * The second byte : read register value function code 131 - 132 132 * 3rd and 4th bytes: start address of register to be read 133 - 134 134 * 5th and 6th bytes: Number of registers to read 135 - 136 136 * 7th and 8th bytes: CRC16 checksum from bytes 1 to 6. 137 137 138 138 ((( 139 - 140 - 141 - 142 142 How to parse the reading of the return command of the parameter: 132 +))) 143 143 144 -(% style="color:blue" %)**Example:**(%%) RETURN1:01 03 02 08 FD 7E 05 134 +(% class="box infomessage" %) 135 +((( 136 +**Example:** RETURN1:01 03 02 08 FD 7E 05 145 145 ))) 146 146 147 147 * The first byte ARD: slave address code (=001~254) 148 - 149 149 * The second byte: Return to read function code 150 - 151 151 * 3rd byte: total number of bytes 152 - 153 153 * 4th~5th bytes: register data 154 - 155 155 * The 6th and 7th bytes: CRC16 checksum 156 - 157 157 * 08 FD is register data. Use short integer 16 bits to convert to decimal, get 2301, then 230.1V is the voltage. 158 158 146 +(% class="wikigeneratedid" %) 147 +((( 148 + 149 +))) 159 159 160 -=== 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** === 161 161 162 - 163 163 RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK. 164 164 165 165 166 -==== **1.3.3.1 via AT COMMAND** ==== 156 +==== **1.3.3.1 via AT COMMAND:** ==== 167 167 158 +First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct. 168 168 169 -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. 170 - 171 171 ((( 172 172 If the configured parameters and commands are incorrect, the return value is not obtained. 173 - 174 - 175 175 ))) 176 176 177 -[[image:image-20220 601143201-9.png]]164 +[[image:image-20220527092748-9.png]] 178 178 179 - **AT COMMAND**166 +AT COMMAND 180 180 181 181 182 182 (% class="box infomessage" %) 183 183 ((( 184 - (% _mstmutation="1" %)**AT+DATACUTx**(%%):This command defines how to handle the return from AT+COMMANDx, max reture length is 40 bytes. AT+DATACUTx=a,b,c171 + AT+DATACUTx : This command defines how to handle the return from AT+COMMANDx, max reture length is 40 bytes. AT+DATACUTx=a,b,c 185 185 ))) 186 186 187 187 a: length for the return of AT+COMMAND ... ... @@ -190,24 +190,27 @@ 190 190 191 191 c: define the position for valid value. 192 192 193 -[[image:image-20220 601143115-8.png]]180 +[[image:image-20220527092936-10.png]] 194 194 195 - **AT COMMAND**182 +AT COMMAND 196 196 197 197 185 + 198 198 PAYLOAD is available after the valid value is intercepted. 199 199 188 + 200 200 [[image:image-20220601143046-7.png]] 201 201 202 - **AT COMMAND**191 +AT COMMAND 203 203 204 204 194 + 205 205 You can get configured PAYLOAD on TTN. 206 206 207 -[[image:image-20220 601143519-1.png]]197 +[[image:image-20220527093133-12.png]] 208 208 209 209 ((( 210 - **AT COMMAND**200 +AT COMMAND 211 211 ))) 212 212 213 213 ((( ... ... @@ -215,49 +215,49 @@ 215 215 ))) 216 216 217 217 ((( 218 -(% style="color:b lue" %)**Example**:208 +(% style="color:#4f81bd" %)**Example**: 219 219 220 - (% style="color:red" %)**CMD1:**(%%)Read current data with MODBUS command. address:210 +CMD1:Read current data with MODBUS command. address:0x03 AT+COMMAND1= 01 03 00 03 00 01,1 221 221 ))) 222 222 223 223 ((( 224 -RETURN1: 214 +RETURN1:01 03 02 00 02 39 85 00 00(return data) 225 225 ))) 226 226 227 227 ((( 228 -AT+DATACUT1: 218 +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. 229 229 230 230 231 231 ))) 232 232 233 233 ((( 234 - (% style="color:red" %)**CMD2:**(%%)Read voltage data with MODBUS command. address:224 +CMD2:Read voltage data with MODBUS command. address:0x00 AT+COMMAND2= 01 03 00 00 00 01,1 235 235 ))) 236 236 237 237 ((( 238 -RETURN2: 228 +RETURN2:01 03 02 08 DC BE 1D(return data) 239 239 ))) 240 240 241 241 ((( 242 -AT+DATACUT2: 232 +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. 243 243 244 244 245 245 ))) 246 246 247 247 ((( 248 - (% style="color:red" %)**CMD3:**(%%)Read total active energy data with MODBUS command. address:238 +CMD3:Read total active energy data with MODBUS command. address:0x0031 AT+COMMAND3= 01 03 00 31 00 02,1 249 249 ))) 250 250 251 251 ((( 252 -RETURN3: 242 +RETURN3:01 03 04 00 00 00 44 FA 00(return data) 253 253 ))) 254 254 255 255 ((( 256 -AT+DATACUT3: 246 +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. 257 257 ))) 258 258 259 259 ((( 260 -Payload: 250 +Payload:01 00 02 39 85 08 DC 00 00 00 44 261 261 ))) 262 262 263 263 [[image:image-20220601142936-6.png]] ... ... @@ -265,26 +265,29 @@ 265 265 AT COMMAND 266 266 267 267 268 -(% style="color:b lue" %)**01 is device address,00 02 is the current, 08 DC is the voltage,00 00 00 44 is the total active energy.**258 +(% 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.** 269 269 270 270 271 -[[image:image-20220601143642-2.png]] 272 272 262 +[[image:image-20220527093251-14.png]] 263 + 273 273 AT COMMAND 274 274 275 275 276 276 ==== **1.3.3.2 via LoRaWAN DOWNLINK** ==== 277 277 278 - 279 279 [[image:image-20220527093358-15.png]] 280 280 281 281 ((( 282 - **DOWNLINK**272 +DOWNLINK 283 283 ))) 284 284 275 +((( 276 + 277 +))) 285 285 286 286 ((( 287 -(% style="color:b lue" %)**Type Code 0xAF**280 +(% style="color:#4f81bd" %)**Type Code 0xAF** 288 288 ))) 289 289 290 290 ((( ... ... @@ -295,7 +295,7 @@ 295 295 ))) 296 296 297 297 ((( 298 - (% style="color:red" %)**Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.**291 +Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink. 299 299 ))) 300 300 301 301 ((( ... ... @@ -330,9 +330,10 @@ 330 330 will execute an uplink after got this command. 331 331 ))) 332 332 333 - 334 334 ((( 335 -(% style="color:blue" %)**Example:** 327 + 328 + 329 +(% style="color:#4f81bd" %)**Example:** 336 336 ))) 337 337 338 338 ((( ... ... @@ -339,34 +339,37 @@ 339 339 **AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1 340 340 ))) 341 341 342 -[[image:image-20220 601144149-6.png]]336 +[[image:image-20220527093430-16.png]] 343 343 344 - **DOWNLINK**338 +DOWNLINK 345 345 346 346 347 -[[image:image-20220601143803-3.png]] 348 348 349 - **DOWNLINK**342 +[[image:image-20220527093508-17.png]] 350 350 344 +DOWNLINK 351 351 352 -[[image:image-20220601144053-5.png]] 353 353 354 -**DOWNLINK** 355 355 348 +[[image:image-20220527093530-18.png]] 356 356 357 - [[image:image-20220601143921-4.png]]350 +DOWNLINK 358 358 359 -**DOWNLINK** 360 360 361 361 362 -[[image:image-20220 601142805-5.png]]354 +[[image:image-20220527093607-19.png]] 363 363 364 - **DOWNLINK**356 +DOWNLINK 365 365 366 366 367 -=== 1.3.4 How to configure and output commands for RS485 to USB === 368 368 360 +[[image:image-20220601142805-5.png]] 369 369 362 +DOWNLINK 363 + 364 + 365 +=== **1.3.4 How to configure and output commands for RS485 to USB** === 366 + 370 370 ((( 371 371 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. 372 372 ))) ... ... @@ -389,12 +389,13 @@ 389 389 390 390 [[image:image-20220527093708-21.png]] 391 391 392 - **USB**389 +USB 393 393 394 394 392 + 395 395 [[image:image-20220527093747-22.png]] 396 396 397 - **USB**395 +USB 398 398 399 399 400 400 ... ... @@ -403,23 +403,20 @@ 403 403 ))) 404 404 405 405 ((( 406 -(% style="color:b lue" %)**Example:** (%%)input:01 03 00 31 00 02 95 c4404 +(% style="color:#4f81bd" %)**Example:** (%%)input:01 03 00 31 00 02 95 c4 407 407 ))) 408 408 409 409 ((( 410 410 output:01 03 04 00 00 00 42 7A 02 411 - 412 - 413 413 ))) 414 414 415 415 [[image:image-20220527093821-23.png]] 416 416 417 - **USB**413 +USB 418 418 419 419 420 -=== 1.3.5 How to configure multiple devices and modify device addresses === 416 +=== **1.3.5 How to configure multiple devices and modify device addresses** === 421 421 422 - 423 423 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. 424 424 425 425 ((( ... ... @@ -431,15 +431,12 @@ 431 431 [[image:image-20220601142044-1.png]] 432 432 433 433 434 - (% style="color:blue" %)**Example**(%%):429 +**Example**:These two meters are examples of setting parameters and device addresses. 435 435 436 - 437 437 [[image:image-20220527093950-25.png]] 438 438 439 - 440 440 [[image:image-20220527094028-26.png]] 441 441 442 - 443 443 ((( 444 444 ((( 445 445 First of all, since the default device address of the energy meter is 01, the configuration of two energy meters will conflict, so we first connect an energy meter and configure the device address. ... ... @@ -448,7 +448,7 @@ 448 448 449 449 ((( 450 450 ((( 451 -We can use (% style="color:blue" %)**AT+CFGDEV**(%%)to set the device address.443 +We can use AT+CFGDEV to set the device address. 452 452 ))) 453 453 ))) 454 454 ... ... @@ -460,15 +460,14 @@ 460 460 461 461 [[image:image-20220601142354-2.png]] 462 462 463 - 464 464 (% class="box infomessage" %) 465 465 ((( 466 466 **AT+CFGDEV:01 10 00 61 00 01 02 00 02,1** 467 467 ))) 468 468 469 -* 01: 460 +* 01:device adaress 470 470 471 -* 10: 462 +* 10:function code 472 472 473 473 * 00 61:Register address 474 474 ... ... @@ -491,77 +491,45 @@ 491 491 492 492 [[image:image-20220601142607-4.png]] 493 493 485 +**PAYLOAD:01 08 DF 43 62** 494 494 495 -(% style="color:blue" %)**PAYLOAD: 01 08 DF 43 62** 496 - 497 497 * 08 DF is the valid value of the meter with device address 02. 498 498 * 43 62 is the valid value of the meter with device address 01. 499 499 500 -(% style="display:none" %) (%%) 501 501 502 - 503 503 == 1.4 Example 4: Circuit Breaker Remote Open Close == 504 504 493 +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: 505 505 506 -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. 507 - 508 -The structure is like below: 509 - 510 510 [[image:image-20220527094330-30.png]] 511 511 512 - **Connection**497 +Connection 513 513 499 +* [[Circuit Breaker Remote Open Close>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Circuit_Breaker_Remote_Open_Close/]] : Configure Documen 514 514 515 -* Configure Documen: [[Circuit Breaker Remote Open Close>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Circuit_Breaker_Remote_Open_Close/||_mstmutation="1"]] 516 516 517 - 518 518 == 1.5 Example 5: SEM Three Energy Meter with RS485-BL or RS485-LN == 519 519 520 - 521 521 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-BL to connect to SEM Three Energy Meter and send the data to mobile phone for remote minitor. The structure is like below: 522 522 523 -* Configure Document For RS485-BL:[[Connect to SEM Three>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Application_Note/&file=Dragino%20RS485BL%20and%20pickdata%20SEM%20Three%20v1.pdf||_mstmutation="1" style="background-color:rgb(255, 255, 255);"]]506 +* [[Connect to SEM Three>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Application_Note/&file=Dragino%20RS485BL%20and%20pickdata%20SEM%20Three%20v1.pdf]] : Configure Document For RS485-BL 524 524 525 -* Configure Document for RS485-LN:[[Connect to SEM Three>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/SEM_Three_Energy_Meter/&file=SEM%20three%20and%20Dragino%20RS485-LN%20v1.pdf||_mstmutation="1"]]508 +* [[Connect to SEM Three>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/SEM_Three_Energy_Meter/&file=SEM%20three%20and%20Dragino%20RS485-LN%20v1.pdf]] : Configure Document for RS485-LN 526 526 527 527 528 -== 1.6 Example 6: CEM C31 485-T1-MID Energy Meter with RS485-LN == 529 529 512 +== 1.6 Example 6:CEM C31 485-T1-MID Energy Meter with RS485-LN == 530 530 531 531 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 CEM C31 485-T1-MID and send the data for remote minitor. The structure is like below: 532 532 533 -* Configure Document For RS485-LN:[[CEM C31 485-T1-MID>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/ELECTRICAL%20CABINET/&file=ELECTRICAL%20CABINET%20READINGS.pdf||_mstmutation="1" style="background-color:rgb(255, 255, 255);"]]516 +* [[CEM C31 485-T1-MID>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/ELECTRICAL%20CABINET/&file=ELECTRICAL%20CABINET%20READINGS.pdf]] : Configure Document For RS485-LN 534 534 535 535 536 -== 1.7 Example 7: Schneider Electric PLC M221 with RS485-BL == 537 537 520 +== 1.7 Example 7:Schneider Electric PLC M221 with RS485-BL == 538 538 539 539 [[image:image-20220527094556-31.png]] 540 540 541 - 542 542 Network Structure 543 543 544 544 * [[Reference Instruction>>url:https://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Schneider%20Electric%20PLC/]] 545 - 546 - 547 -== 1.8 Example 8: This sketch is supposed to test Dragino RS485-BL (Modbus master), using an Arduino UNO as a Modbus slave. == 548 - 549 - 550 -This sketch uses 4 registers: some of them can be set by Dragino with a command, another is used to store value from a DS18B20 temperature sensor, or a random generated number. All data is 16bit uint, but the sketch shows also how to represent booleans and negative numbers. 551 - 552 -In the next days I will be adding more documentation, but I think it already explains users how to build their own modbus sensor to pair with Dragino RS485-BL. 553 - 554 -This is released the code under GNU LGPL licence on Github: 555 - 556 -[[https:~~/~~/github.com/zorbaproject/ArduinoModbusForDraginoRS485>>url:https://github.com/zorbaproject/ArduinoModbusForDraginoRS485]] 557 - 558 - 559 -== 1.9 Example 9: RS485-LN and ultrasonic flow meter transmission data == 560 - 561 - 562 -It shows how to use RS485-LN to connect to an ultrasonic flow meter and read the data from the ultrasonic flow meter. 563 - 564 - 565 - 566 -* **Specific steps**: RS485-LN with ultrasonic flow meter 567 -*
- 1720669739434-926.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.karry - Size
-
... ... @@ -1,1 +1,0 @@ 1 -489.9 KB - Content
- 1720669744315-613.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.karry - Size
-
... ... @@ -1,1 +1,0 @@ 1 -476.9 KB - Content
- 1720669933691-331.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.karry - Size
-
... ... @@ -1,1 +1,0 @@ 1 -395.1 KB - Content
- 1720669944339-942.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.karry - Size
-
... ... @@ -1,1 +1,0 @@ 1 -341.8 KB - Content
- 1720669981767-254.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.karry - Size
-
... ... @@ -1,1 +1,0 @@ 1 -341.8 KB - Content
- 1720670003601-544.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.karry - Size
-
... ... @@ -1,1 +1,0 @@ 1 -385.3 KB - Content
- 1720670016539-422.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.karry - Size
-
... ... @@ -1,1 +1,0 @@ 1 -503.5 KB - Content
- 1720670019136-658.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.karry - Size
-
... ... @@ -1,1 +1,0 @@ 1 -592.6 KB - Content
- 1720670035661-234.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.karry - Size
-
... ... @@ -1,1 +1,0 @@ 1 -316.5 KB - Content
- 1720670038725-366.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.karry - Size
-
... ... @@ -1,1 +1,0 @@ 1 -571.9 KB - Content
- 1720670041974-372.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.karry - Size
-
... ... @@ -1,1 +1,0 @@ 1 -571.9 KB - Content
- 1720670079781-764.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.karry - Size
-
... ... @@ -1,1 +1,0 @@ 1 -614.7 KB - Content
- 1720670090204-634.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.karry - Size
-
... ... @@ -1,1 +1,0 @@ 1 -30.6 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