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)
-
Attachments (0 modified, 0 added, 3 removed)
Details
- Page properties
-
- Content
-
... ... @@ -7,15 +7,12 @@ 7 7 **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual** 8 8 9 9 10 - 11 11 **Table of Contents:** 12 12 13 -{{toc/}} 14 14 15 15 16 16 17 17 18 - 19 19 = 1.Introduction = 20 20 21 21 == 1.1 What is RS485-BL RS485 to LoRaWAN Converter == ... ... @@ -25,19 +25,19 @@ 25 25 ))) 26 26 27 27 ((( 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.25 +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. 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 (% 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.29 +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. 33 33 ))) 34 34 35 35 ((( 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.33 +RS485-BL is IP67 **waterproof** and powered by **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 (% 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.37 +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. 41 41 ))) 42 42 43 43 ((( ... ... @@ -54,11 +54,8 @@ 54 54 55 55 [[image:1652953304999-717.png||height="424" width="733"]] 56 56 57 - 58 - 59 59 == 1.2 Specifications == 60 60 61 - 62 62 **Hardware System:** 63 63 64 64 * STM32L072CZT6 MCU ... ... @@ -65,6 +65,8 @@ 65 65 * SX1276/78 Wireless Chip 66 66 * Power Consumption (exclude RS485 device): 67 67 ** Idle: 6uA@3.3v 62 + 63 +* 68 68 ** 20dB Transmit: 130mA@3.3v 69 69 70 70 **Interface for Model:** ... ... @@ -118,12 +118,9 @@ 118 118 119 119 [[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);"]] 120 120 121 - 122 122 == 1.6 Hardware Change log == 123 123 124 124 ((( 125 - 126 - 127 127 v1.4 128 128 ))) 129 129 ... ... @@ -147,8 +147,6 @@ 147 147 148 148 ((( 149 149 Release version 150 - 151 - 152 152 ))) 153 153 154 154 = 2. Pin mapping and Power ON Device = ... ... @@ -162,7 +162,6 @@ 162 162 163 163 The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper. 164 164 165 - 166 166 = 3. Operation Mode = 167 167 168 168 == 3.1 How it works? == ... ... @@ -169,8 +169,6 @@ 169 169 170 170 ((( 171 171 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 - 174 174 ))) 175 175 176 176 == 3.2 Example to join LoRaWAN network == ... ... @@ -206,6 +206,8 @@ 206 206 ))) 207 207 208 208 197 + 198 + 209 209 [[image:image-20220519174512-1.png]] 210 210 211 211 [[image:image-20220519174512-2.png||height="328" width="731"]] ... ... @@ -229,13 +229,10 @@ 229 229 230 230 [[image:1652953568895-172.png||height="232" width="724"]] 231 231 232 - 233 233 == 3.3 Configure Commands to read data == 234 234 235 235 ((( 236 -There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors. 237 - 238 - 225 +There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>path:#AT_COMMAND]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors. 239 239 ))) 240 240 241 241 === 3.3.1 onfigure UART settings for RS485 or TTL communication === ... ... @@ -316,8 +316,6 @@ 316 316 ))) 317 317 ))) 318 318 319 - 320 - 321 321 === 3.3.2 Configure sensors === 322 322 323 323 ((( ... ... @@ -338,9 +338,8 @@ 338 338 mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 339 339 )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 340 340 341 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>> ||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].326 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]]. 342 342 343 - 344 344 === 3.3.3 Configure read commands for each sampling === 345 345 346 346 ((( ... ... @@ -438,7 +438,7 @@ 438 438 439 439 **Examples:** 440 440 441 -1 )For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49425 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 442 442 443 443 If we set AT+SEARCH1=1,1E 56 34. (max 5 bytes for prefix) 444 444 ... ... @@ -446,7 +446,7 @@ 446 446 447 447 [[image:1653271044481-711.png]] 448 448 449 - 2)For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49433 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 450 450 451 451 If we set AT+SEARCH1=2, 1E 56 34+31 00 49 452 452 ... ... @@ -465,19 +465,16 @@ 465 465 * **c: define the position for valid value. ** 466 466 ))) 467 467 452 +Examples: 468 468 469 -**Examples:** 470 - 471 471 * Grab bytes: 472 472 473 473 [[image:1653271581490-837.png||height="313" width="722"]] 474 474 475 - 476 476 * Grab a section. 477 477 478 478 [[image:1653271648378-342.png||height="326" width="720"]] 479 479 480 - 481 481 * Grab different sections. 482 482 483 483 [[image:1653271657255-576.png||height="305" width="730"]] ... ... @@ -520,82 +520,64 @@ 520 520 521 521 [[image:1653271763403-806.png]] 522 522 523 -=== 3.3.4 Compose the uplink payload === 524 524 525 -((( 505 + 506 + 507 +1. 508 +11. 509 +111. Compose the uplink payload 510 + 526 526 Through AT+COMMANDx and AT+DATACUTx we got valid value from each RS485 commands, Assume these valid value are RETURN1, RETURN2, .., to RETURNx. The next step is how to compose the LoRa Uplink Payload by these RETURNs. The command is **AT+DATAUP.** 527 -))) 528 528 529 -((( 530 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0** 531 -))) 532 532 533 -((( 534 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**. 535 -))) 514 +**Examples: AT+DATAUP=0** 536 536 537 -((( 516 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**. 517 + 538 538 Final Payload is 539 -))) 540 540 541 -((( 542 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx 543 -))) 520 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx 544 544 545 -((( 546 546 Where PAYVER is defined by AT+PAYVER, below is an example screen shot. 547 -))) 548 548 549 -[[image: 1653272787040-634.png||height="515" width="719"]]524 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]] 550 550 551 -((( 552 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1** 553 -))) 554 554 555 -((( 556 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**. 557 -))) 558 558 559 -((( 528 +**Examples: AT+DATAUP=1** 529 + 530 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**. 531 + 560 560 Final Payload is 561 -))) 562 562 563 -((( 564 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 565 -))) 534 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 566 566 567 -1. ((( 568 -Battery Info (2 bytes): Battery voltage 569 -))) 570 -1. ((( 571 -PAYVER (1 byte): Defined by AT+PAYVER 572 -))) 573 -1. ((( 574 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 575 -))) 576 -1. ((( 577 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 578 -))) 579 -1. ((( 580 -DATA: Valid value: max 6 bytes(US915 version here, Notice*!) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes 581 -))) 536 +1. Battery Info (2 bytes): Battery voltage 537 +1. PAYVER (1 byte): Defined by AT+PAYVER 538 +1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 539 +1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 540 +1. DATA: Valid value: max 6 bytes(US915 version here, [[Notice*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes 582 582 583 -[[image: 1653272817147-600.png||height="437" width="717"]]542 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]] 584 584 544 + 585 585 So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA 586 586 587 -DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %)20 20 0a 33 90 41547 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41 588 588 589 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20549 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20 590 590 591 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (%style="background-color:#4f81bd; color:white" %)20 20 20 2d 30551 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30 592 592 553 + 554 + 593 593 Below are the uplink payloads: 594 594 595 -[[image: 1653272901032-107.png]]557 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]] 596 596 597 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below: 598 598 560 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below: 561 + 599 599 ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date) 600 600 601 601 * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date). ... ... @@ -604,121 +604,90 @@ 604 604 605 605 ~* For all other bands: max 51 bytes for each uplink ( so 51 -5 = 46 max valid date). 606 606 607 -=== 3.3.5 Uplink on demand === 608 608 609 -((( 571 + 572 +1. 573 +11. 574 +111. Uplink on demand 575 + 610 610 Except uplink periodically, RS485-BL is able to uplink on demand. The server sends downlink command to RS485-BL and RS485 will uplink data base on the command. 611 -))) 612 612 613 -((( 614 614 Downlink control command: 615 -))) 616 616 617 -((( 618 -**0x08 command**: Poll an uplink with current command set in RS485-BL. 619 -))) 580 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL. 620 620 621 -((( 622 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors. 623 -))) 582 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors. 624 624 625 -=== 3.3.6 Uplink on Interrupt === 626 626 627 -Put the interrupt sensor between 3.3v_out and GPIO ext. 628 628 629 -[[image:1653273818896-432.png]] 586 +1. 587 +11. 588 +111. Uplink on Interrupt 630 630 631 -((( 590 +Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]] 591 + 632 632 AT+INTMOD=0 Disable Interrupt 633 -))) 634 634 635 -((( 636 636 AT+INTMOD=1 Interrupt trigger by rising or falling edge. 637 -))) 638 638 639 -((( 640 640 AT+INTMOD=2 Interrupt trigger by falling edge. ( Default Value) 641 -))) 642 642 643 -((( 644 644 AT+INTMOD=3 Interrupt trigger by rising edge. 645 -))) 646 646 647 -== 3.4 Uplink Payload == 648 648 649 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %) 650 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands** 651 -|Value|(% style="width:130px" %)((( 652 -((( 601 +1. 602 +11. Uplink Payload 603 + 604 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands** 605 +|Value|((( 653 653 Battery(mV) 654 -))) 655 655 656 -((( 657 657 & 658 -))) 659 659 660 -((( 661 661 Interrupt _Flag 662 -))) 663 -)))|(% style="width:93px" %)((( 611 +)))|((( 664 664 PAYLOAD_VER 665 665 666 666 667 -)))| (% style="width:509px" %)If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.615 +)))|If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server. 668 668 669 669 Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors. 670 670 671 - (((619 + 672 672 function Decoder(bytes, port) { 673 -))) 674 674 675 -((( 676 676 ~/~/Payload Formats of RS485-BL Deceive 677 -))) 678 678 679 -((( 680 680 return { 681 -))) 682 682 683 -((( 684 684 ~/~/Battery,units:V 685 -))) 686 686 687 -((( 688 688 BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000, 689 -))) 690 690 691 -((( 692 692 ~/~/GPIO_EXTI 693 -))) 694 694 695 -((( 696 696 EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE", 697 -))) 698 698 699 -((( 700 700 ~/~/payload of version 701 -))) 702 702 703 -((( 704 704 Pay_ver:bytes[2], 705 -))) 706 706 707 -((( 708 708 }; 709 -))) 710 710 711 -((( 712 712 } 713 -))) 714 714 715 -((( 642 + 643 + 644 + 645 + 646 + 647 + 716 716 TTN V3 uplink screen shot. 717 -))) 718 718 719 -[[image: 1653274001211-372.png||height="192" width="732"]]650 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]] 720 720 721 -== 3.5 Configure RS485-BL via AT or Downlink == 652 +1. 653 +11. Configure RS485-BL via AT or Downlink 722 722 723 723 User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]or LoRaWAN Downlink Commands 724 724 ... ... @@ -728,15 +728,15 @@ 728 728 729 729 * **Sensor Related Commands**: These commands are special designed for RS485-BL. User can see these commands below: 730 730 731 -1. 732 -11. 663 +1. 664 +11. 733 733 111. Common Commands: 734 734 735 735 They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands>>url:http://wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands]] 736 736 737 737 738 -1. 739 -11. 670 +1. 671 +11. 740 740 111. Sensor related commands: 741 741 742 742 ==== Choose Device Type (RS485 or TTL) ==== ... ... @@ -1042,13 +1042,13 @@ 1042 1042 1043 1043 1044 1044 1045 -1. 977 +1. 1046 1046 11. Buttons 1047 1047 1048 1048 |**Button**|**Feature** 1049 1049 |**RST**|Reboot RS485-BL 1050 1050 1051 -1. 983 +1. 1052 1052 11. +3V3 Output 1053 1053 1054 1054 RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor. ... ... @@ -1066,7 +1066,7 @@ 1066 1066 By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time 1067 1067 1068 1068 1069 -1. 1001 +1. 1070 1070 11. +5V Output 1071 1071 1072 1072 RS485-BL has a Controllable +5V output, user can use this output to power external sensor. ... ... @@ -1086,13 +1086,13 @@ 1086 1086 1087 1087 1088 1088 1089 -1. 1021 +1. 1090 1090 11. LEDs 1091 1091 1092 1092 |**LEDs**|**Feature** 1093 1093 |**LED1**|Blink when device transmit a packet. 1094 1094 1095 -1. 1027 +1. 1096 1096 11. Switch Jumper 1097 1097 1098 1098 |**Switch Jumper**|**Feature** ... ... @@ -1138,7 +1138,7 @@ 1138 1138 1139 1139 1140 1140 1141 -1. 1073 +1. 1142 1142 11. Common AT Command Sequence 1143 1143 111. Multi-channel ABP mode (Use with SX1301/LG308) 1144 1144 ... ... @@ -1157,8 +1157,8 @@ 1157 1157 1158 1158 ATZ 1159 1159 1160 -1. 1161 -11. 1092 +1. 1093 +11. 1162 1162 111. Single-channel ABP mode (Use with LG01/LG02) 1163 1163 1164 1164 AT+FDR Reset Parameters to Factory Default, Keys Reserve ... ... @@ -1233,7 +1233,7 @@ 1233 1233 [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image035.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image036.png]] 1234 1234 1235 1235 1236 -1. 1168 +1. 1237 1237 11. How to change the LoRa Frequency Bands/Region? 1238 1238 1239 1239 User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download. ... ... @@ -1240,7 +1240,7 @@ 1240 1240 1241 1241 1242 1242 1243 -1. 1175 +1. 1244 1244 11. How many RS485-Slave can RS485-BL connects? 1245 1245 1246 1246 The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>path:#downlink_A8]]. ... ... @@ -1257,7 +1257,7 @@ 1257 1257 1258 1258 1259 1259 1260 -1. 1192 +1. 1261 1261 11. Why I can’t join TTN V3 in US915 /AU915 bands? 1262 1262 1263 1263 It might about the channels mapping. Please see for detail.
- 1653272901032-107.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -197.8 KB - Content
- 1653273818896-432.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.6 KB - Content
- 1653274001211-372.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -91.4 KB - Content