Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 29.6
edited by Xiaoling
on 2022/06/01 18:01
Change comment: There is no comment for this version
To version 29.33
edited by Xiaoling
on 2022/06/02 08:58
Change comment: There is no comment for this version

Summary

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:**
... ... @@ -117,9 +117,12 @@
117 117  
118 118  [[RS485-BL Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Firmware/||style="background-color: rgb(255, 255, 255);"]]
119 119  
121 +
120 120  == 1.6 Hardware Change log ==
121 121  
122 122  (((
125 +
126 +
123 123  v1.4
124 124  )))
125 125  
... ... @@ -143,6 +143,8 @@
143 143  
144 144  (((
145 145  Release version ​​​​​
150 +
151 +
146 146  )))
147 147  
148 148  = 2. Pin mapping and Power ON Device =
... ... @@ -156,6 +156,7 @@
156 156  
157 157  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
158 158  
165 +
159 159  = 3. Operation Mode =
160 160  
161 161  == 3.1 How it works? ==
... ... @@ -162,6 +162,8 @@
162 162  
163 163  (((
164 164  The RS485-BL is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the RS485-BL. It will auto join the network via OTAA.
172 +
173 +
165 165  )))
166 166  
167 167  == 3.2 Example to join LoRaWAN network ==
... ... @@ -197,8 +197,6 @@
197 197  )))
198 198  
199 199  
200 -
201 -
202 202  [[image:image-20220519174512-1.png]]
203 203  
204 204  [[image:image-20220519174512-2.png||height="328" width="731"]]
... ... @@ -222,6 +222,7 @@
222 222  
223 223  [[image:1652953568895-172.png||height="232" width="724"]]
224 224  
232 +
225 225  == 3.3 Configure Commands to read data ==
226 226  
227 227  (((
... ... @@ -308,6 +308,7 @@
308 308  )))
309 309  )))
310 310  
319 +
311 311  === 3.3.2 Configure sensors ===
312 312  
313 313  (((
... ... @@ -328,8 +328,9 @@
328 328  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
329 329  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
330 330  
331 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
340 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
332 332  
342 +
333 333  === 3.3.3 Configure read commands for each sampling ===
334 334  
335 335  (((
... ... @@ -427,7 +427,7 @@
427 427  
428 428  **Examples:**
429 429  
430 -1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
440 +1）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
431 431  
432 432  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
433 433  
... ... @@ -435,7 +435,7 @@
435 435  
436 436  [[image:1653271044481-711.png]]
437 437  
438 -1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
448 +2）For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
439 439  
440 440  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
441 441  
... ... @@ -454,16 +454,18 @@
454 454  * **c: define the position for valid value.  **
455 455  )))
456 456  
457 -Examples:
467 +**Examples:**
458 458  
459 459  * Grab bytes:
460 460  
461 461  [[image:1653271581490-837.png||height="313" width="722"]]
462 462  
473 +
463 463  * Grab a section.
464 464  
465 465  [[image:1653271648378-342.png||height="326" width="720"]]
466 466  
478 +
467 467  * Grab different sections.
468 468  
469 469  [[image:1653271657255-576.png||height="305" width="730"]]
... ... @@ -506,6 +506,7 @@
506 506  
507 507  [[image:1653271763403-806.png]]
508 508  
521 +
509 509  === 3.3.4 Compose the uplink payload ===
510 510  
511 511  (((
... ... @@ -513,7 +513,7 @@
513 513  )))
514 514  
515 515  (((
516 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
529 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
517 517  )))
518 518  
519 519  (((
... ... @@ -525,7 +525,7 @@
525 525  )))
526 526  
527 527  (((
528 -(% 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**
529 529  )))
530 530  
531 531  (((
... ... @@ -534,8 +534,12 @@
534 534  
535 535  [[image:1653272787040-634.png||height="515" width="719"]]
536 536  
550 +
551 +
537 537  (((
538 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
553 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
554 +
555 +
539 539  )))
540 540  
541 541  (((
... ... @@ -547,7 +547,7 @@
547 547  )))
548 548  
549 549  (((
550 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
567 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
551 551  )))
552 552  
553 553  1. (((