Changes for page RS485-BL – Waterproof RS485 to LoRaWAN Converter
Last modified by Xiaoling on 2025/04/23 15:57
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -25,19 +25,19 @@ 25 25 ))) 26 26 27 27 ((( 28 -The Dragino RS485-BL is a **RS485 / UART to LoRaWAN Converter** for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server. 28 +The Dragino RS485-BL is a (% style="color:blue" %)**RS485 / UART to LoRaWAN Converter**(%%) for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server. 29 29 ))) 30 30 31 31 ((( 32 -RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides **a 3.3v output** and** a 5v output** to power external sensors. Both output voltages are controllable to minimize the total system power consumption. 32 +RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides (% style="color:blue" %)**a 3.3v output**(%%) and** (% style="color:blue" %)a 5v output(%%)** to power external sensors. Both output voltages are controllable to minimize the total system power consumption. 33 33 ))) 34 34 35 35 ((( 36 -RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years. 36 +RS485-BL is IP67 (% style="color:blue" %)**waterproof**(%%) and powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use for several years. 37 37 ))) 38 38 39 39 ((( 40 -RS485-BL runs standard **LoRaWAN 1.0.3 in Class A**. It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server. 40 +RS485-BL runs standard (% style="color:blue" %)**LoRaWAN 1.0.3 in Class A**(%%). It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server. 41 41 ))) 42 42 43 43 ((( ... ... @@ -54,8 +54,11 @@ 54 54 55 55 [[image:1652953304999-717.png||height="424" width="733"]] 56 56 57 + 58 + 57 57 == 1.2 Specifications == 58 58 61 + 59 59 **Hardware System:** 60 60 61 61 * STM32L072CZT6 MCU ... ... @@ -62,8 +62,6 @@ 62 62 * SX1276/78 Wireless Chip 63 63 * Power Consumption (exclude RS485 device): 64 64 ** Idle: 6uA@3.3v 65 - 66 -* 67 67 ** 20dB Transmit: 130mA@3.3v 68 68 69 69 **Interface for Model:** ... ... @@ -121,6 +121,8 @@ 121 121 == 1.6 Hardware Change log == 122 122 123 123 ((( 125 + 126 + 124 124 v1.4 125 125 ))) 126 126 ... ... @@ -203,8 +203,6 @@ 203 203 ))) 204 204 205 205 206 - 207 - 208 208 [[image:image-20220519174512-1.png]] 209 209 210 210 [[image:image-20220519174512-2.png||height="328" width="731"]] ... ... @@ -228,6 +228,7 @@ 228 228 229 229 [[image:1652953568895-172.png||height="232" width="724"]] 230 230 232 + 231 231 == 3.3 Configure Commands to read data == 232 232 233 233 ((( ... ... @@ -314,6 +314,7 @@ 314 314 ))) 315 315 ))) 316 316 319 + 317 317 === 3.3.2 Configure sensors === 318 318 319 319 ((( ... ... @@ -334,8 +334,9 @@ 334 334 mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 335 335 )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 336 336 337 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>> path:#AT_CFGDEV]].340 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]]. 338 338 342 + 339 339 === 3.3.3 Configure read commands for each sampling === 340 340 341 341 ((( ... ... @@ -433,7 +433,7 @@ 433 433 434 434 **Examples:** 435 435 436 -1 .For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49440 +1）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 437 437 438 438 If we set AT+SEARCH1=1,1E 56 34. (max 5 bytes for prefix) 439 439 ... ... @@ -441,7 +441,7 @@ 441 441 442 442 [[image:1653271044481-711.png]] 443 443 444 - 1.For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49448 +2）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 445 445 446 446 If we set AT+SEARCH1=2, 1E 56 34+31 00 49 447 447 ... ... @@ -460,16 +460,18 @@ 460 460 * **c: define the position for valid value. ** 461 461 ))) 462 462 463 -Examples: 467 +**Examples:** 464 464 465 465 * Grab bytes: 466 466 467 467 [[image:1653271581490-837.png||height="313" width="722"]] 468 468 473 + 469 469 * Grab a section. 470 470 471 471 [[image:1653271648378-342.png||height="326" width="720"]] 472 472 478 + 473 473 * Grab different sections. 474 474 475 475 [[image:1653271657255-576.png||height="305" width="730"]] ... ... @@ -512,6 +512,7 @@ 512 512 513 513 [[image:1653271763403-806.png]] 514 514 521 + 515 515 === 3.3.4 Compose the uplink payload === 516 516 517 517 ((( ... ... @@ -519,7 +519,7 @@ 519 519 ))) 520 520 521 521 ((( 522 -(% style="color:# 4f81bd" %)**Examples: AT+DATAUP=0**529 +(% style="color:#037691" %)**Examples: AT+DATAUP=0** 523 523 ))) 524 524 525 525 ((( ... ... @@ -531,7 +531,7 @@ 531 531 ))) 532 532 533 533 ((( 534 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx 541 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx** 535 535 ))) 536 536 537 537 ((( ... ... @@ -540,8 +540,12 @@ 540 540 541 541 [[image:1653272787040-634.png||height="515" width="719"]] 542 542 550 + 551 + 543 543 ((( 544 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1** 553 +(% style="color:#037691" %)**Examples: AT+DATAUP=1** 554 + 555 + 545 545 ))) 546 546 547 547 ((( ... ... @@ -553,7 +553,7 @@ 553 553 ))) 554 554 555 555 ((( 556 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 567 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA** 557 557 ))) 558 558 559 559 1. ((( ... ... @@ -586,6 +586,7 @@ 586 586 587 587 [[image:1653272901032-107.png]] 588 588 600 + 589 589 (% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below: 590 590 591 591 ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)