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, 6 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -7,12 +7,15 @@ 7 7 **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual** 8 8 9 9 10 + 10 10 **Table of Contents:** 11 11 13 +{{toc/}} 12 12 13 13 14 14 15 15 18 + 16 16 = 1.Introduction = 17 17 18 18 == 1.1 What is RS485-BL RS485 to LoRaWAN Converter == ... ... @@ -22,19 +22,19 @@ 22 22 ))) 23 23 24 24 ((( 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. 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. 26 26 ))) 27 27 28 28 ((( 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. 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. 30 30 ))) 31 31 32 32 ((( 33 -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. 34 34 ))) 35 35 36 36 ((( 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. 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. 38 38 ))) 39 39 40 40 ((( ... ... @@ -51,6 +51,8 @@ 51 51 52 52 [[image:1652953304999-717.png||height="424" width="733"]] 53 53 57 + 58 + 54 54 == 1.2 Specifications == 55 55 56 56 **Hardware System:** ... ... @@ -60,7 +60,7 @@ 60 60 * Power Consumption (exclude RS485 device): 61 61 ** Idle: 6uA@3.3v 62 62 63 -* 68 +* 64 64 ** 20dB Transmit: 130mA@3.3v 65 65 66 66 **Interface for Model:** ... ... @@ -90,6 +90,7 @@ 90 90 * 127 dB Dynamic Range RSSI. 91 91 * Automatic RF Sense and CAD with ultra-fast AFC. 92 92 98 + 93 93 == 1.3 Features == 94 94 95 95 * LoRaWAN Class A & Class C protocol (default Class A) ... ... @@ -101,6 +101,7 @@ 101 101 * Support Modbus protocol 102 102 * Support Interrupt uplink 103 103 110 + 104 104 == 1.4 Applications == 105 105 106 106 * Smart Buildings & Home Automation ... ... @@ -110,10 +110,12 @@ 110 110 * Smart Cities 111 111 * Smart Factory 112 112 120 + 113 113 == 1.5 Firmware Change log == 114 114 115 115 [[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);"]] 116 116 125 + 117 117 == 1.6 Hardware Change log == 118 118 119 119 ((( ... ... @@ -140,6 +140,8 @@ 140 140 141 141 ((( 142 142 Release version 152 + 153 + 143 143 ))) 144 144 145 145 = 2. Pin mapping and Power ON Device = ... ... @@ -153,6 +153,7 @@ 153 153 154 154 The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper. 155 155 167 + 156 156 = 3. Operation Mode = 157 157 158 158 == 3.1 How it works? == ... ... @@ -159,6 +159,8 @@ 159 159 160 160 ((( 161 161 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. 174 + 175 + 162 162 ))) 163 163 164 164 == 3.2 Example to join LoRaWAN network == ... ... @@ -222,7 +222,9 @@ 222 222 == 3.3 Configure Commands to read data == 223 223 224 224 ((( 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 +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. 240 + 241 + 226 226 ))) 227 227 228 228 === 3.3.1 onfigure UART settings for RS485 or TTL communication === ... ... @@ -463,84 +463,120 @@ 463 463 464 464 [[image:1653271657255-576.png||height="305" width="730"]] 465 465 482 +((( 466 466 (% style="color:red" %)**Note:** 484 +))) 467 467 486 +((( 468 468 AT+SEARCHx and AT+DATACUTx can be used together, if both commands are set, RS485-BL will first process AT+SEARCHx on the return string and get a temporary string, and then process AT+DATACUTx on this temporary string to get the final payload. In this case, AT+DATACUTx need to set to format AT+DATACUTx=0,xx,xx where the return bytes set to 0. 488 +))) 469 469 490 +((( 470 470 **Example:** 492 +))) 471 471 494 +((( 472 472 (% style="color:red" %)AT+COMMAND1=11 01 1E D0,0 496 +))) 473 473 498 +((( 474 474 (% style="color:red" %)AT+SEARCH1=1,1E 56 34 500 +))) 475 475 502 +((( 476 476 (% style="color:red" %)AT+DATACUT1=0,2,1~~5 504 +))) 477 477 506 +((( 478 478 (% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 508 +))) 479 479 510 +((( 480 480 (% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 512 +))) 481 481 514 +((( 482 482 (% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36 516 +))) 483 483 484 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]518 +[[image:1653271763403-806.png]] 485 485 520 +=== 3.3.4 Compose the uplink payload === 486 486 487 - 488 - 489 -1. 490 -11. 491 -111. Compose the uplink payload 492 - 522 +((( 493 493 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.** 524 +))) 494 494 526 +((( 527 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0** 528 +))) 495 495 496 -**Examples: AT+DATAUP=0** 530 +((( 531 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**. 532 +))) 497 497 498 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**. 499 - 534 +((( 500 500 Final Payload is 536 +))) 501 501 502 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx 538 +((( 539 +(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx 540 +))) 503 503 542 +((( 504 504 Where PAYVER is defined by AT+PAYVER, below is an example screen shot. 544 +))) 505 505 506 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]546 +[[image:1653272787040-634.png||height="515" width="719"]] 507 507 548 +((( 549 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1** 550 +))) 508 508 552 +((( 553 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**. 554 +))) 509 509 510 -**Examples: AT+DATAUP=1** 511 - 512 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**. 513 - 556 +((( 514 514 Final Payload is 558 +))) 515 515 516 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 560 +((( 561 +(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 562 +))) 517 517 518 -1. Battery Info (2 bytes): Battery voltage 519 -1. PAYVER (1 byte): Defined by AT+PAYVER 520 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 521 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 522 -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 564 +1. ((( 565 +Battery Info (2 bytes): Battery voltage 566 +))) 567 +1. ((( 568 +PAYVER (1 byte): Defined by AT+PAYVER 569 +))) 570 +1. ((( 571 +PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 572 +))) 573 +1. ((( 574 +PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 575 +))) 576 +1. ((( 577 +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 578 +))) 523 523 524 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]580 +[[image:1653272817147-600.png||height="437" width="717"]] 525 525 526 - 527 527 So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA 528 528 529 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41 584 +DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41 530 530 531 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20 586 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20 532 532 533 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30 588 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30 534 534 535 - 536 - 537 537 Below are the uplink payloads: 538 538 539 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]592 +[[image:1653272901032-107.png]] 540 540 594 +(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below: 541 541 542 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below: 543 - 544 544 ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date) 545 545 546 546 * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date). ... ... @@ -549,90 +549,121 @@ 549 549 550 550 ~* For all other bands: max 51 bytes for each uplink ( so 51 -5 = 46 max valid date). 551 551 604 +=== 3.3.5 Uplink on demand === 552 552 553 - 554 -1. 555 -11. 556 -111. Uplink on demand 557 - 606 +((( 558 558 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. 608 +))) 559 559 610 +((( 560 560 Downlink control command: 612 +))) 561 561 562 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL. 614 +((( 615 +**0x08 command**: Poll an uplink with current command set in RS485-BL. 616 +))) 563 563 564 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors. 618 +((( 619 +**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors. 620 +))) 565 565 622 +=== 3.3.6 Uplink on Interrupt === 566 566 624 +Put the interrupt sensor between 3.3v_out and GPIO ext. 567 567 568 -1. 569 -11. 570 -111. Uplink on Interrupt 626 +[[image:1653273818896-432.png]] 571 571 572 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]] 573 - 628 +((( 574 574 AT+INTMOD=0 Disable Interrupt 630 +))) 575 575 632 +((( 576 576 AT+INTMOD=1 Interrupt trigger by rising or falling edge. 634 +))) 577 577 636 +((( 578 578 AT+INTMOD=2 Interrupt trigger by falling edge. ( Default Value) 638 +))) 579 579 640 +((( 580 580 AT+INTMOD=3 Interrupt trigger by rising edge. 642 +))) 581 581 644 +== 3.4 Uplink Payload == 582 582 583 -1. 584 -11. Uplink Payload 585 - 586 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands** 587 -|Value|((( 646 +(% border="1" style="background-color:#4f81bd; color:white; width:850px" %) 647 +|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands** 648 +|Value|(% style="width:130px" %)((( 649 +((( 588 588 Battery(mV) 651 +))) 589 589 653 +((( 590 590 & 655 +))) 591 591 657 +((( 592 592 Interrupt _Flag 593 -)))|((( 659 +))) 660 +)))|(% style="width:93px" %)((( 594 594 PAYLOAD_VER 595 595 596 596 597 -)))|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. 664 +)))|(% 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. 598 598 599 599 Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors. 600 600 601 - 668 +((( 602 602 function Decoder(bytes, port) { 670 +))) 603 603 672 +((( 604 604 ~/~/Payload Formats of RS485-BL Deceive 674 +))) 605 605 676 +((( 606 606 return { 678 +))) 607 607 680 +((( 608 608 ~/~/Battery,units:V 682 +))) 609 609 684 +((( 610 610 BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000, 686 +))) 611 611 688 +((( 612 612 ~/~/GPIO_EXTI 690 +))) 613 613 692 +((( 614 614 EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE", 694 +))) 615 615 696 +((( 616 616 ~/~/payload of version 698 +))) 617 617 700 +((( 618 618 Pay_ver:bytes[2], 702 +))) 619 619 704 +((( 620 620 }; 706 +))) 621 621 708 +((( 622 622 } 710 +))) 623 623 624 - 625 - 626 - 627 - 628 - 629 - 712 +((( 630 630 TTN V3 uplink screen shot. 714 +))) 631 631 632 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]716 +[[image:1653274001211-372.png||height="192" width="732"]] 633 633 634 -1. 635 -11. Configure RS485-BL via AT or Downlink 718 +== 3.5 Configure RS485-BL via AT or Downlink == 636 636 637 637 User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]or LoRaWAN Downlink Commands 638 638 ... ... @@ -642,15 +642,15 @@ 642 642 643 643 * **Sensor Related Commands**: These commands are special designed for RS485-BL. User can see these commands below: 644 644 645 -1. 646 -11. 728 +1. 729 +11. 647 647 111. Common Commands: 648 648 649 649 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]] 650 650 651 651 652 -1. 653 -11. 735 +1. 736 +11. 654 654 111. Sensor related commands: 655 655 656 656 ==== Choose Device Type (RS485 or TTL) ==== ... ... @@ -956,13 +956,13 @@ 956 956 957 957 958 958 959 -1. 1042 +1. 960 960 11. Buttons 961 961 962 962 |**Button**|**Feature** 963 963 |**RST**|Reboot RS485-BL 964 964 965 -1. 1048 +1. 966 966 11. +3V3 Output 967 967 968 968 RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor. ... ... @@ -980,7 +980,7 @@ 980 980 By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time 981 981 982 982 983 -1. 1066 +1. 984 984 11. +5V Output 985 985 986 986 RS485-BL has a Controllable +5V output, user can use this output to power external sensor. ... ... @@ -1000,13 +1000,13 @@ 1000 1000 1001 1001 1002 1002 1003 -1. 1086 +1. 1004 1004 11. LEDs 1005 1005 1006 1006 |**LEDs**|**Feature** 1007 1007 |**LED1**|Blink when device transmit a packet. 1008 1008 1009 -1. 1092 +1. 1010 1010 11. Switch Jumper 1011 1011 1012 1012 |**Switch Jumper**|**Feature** ... ... @@ -1052,7 +1052,7 @@ 1052 1052 1053 1053 1054 1054 1055 -1. 1138 +1. 1056 1056 11. Common AT Command Sequence 1057 1057 111. Multi-channel ABP mode (Use with SX1301/LG308) 1058 1058 ... ... @@ -1071,8 +1071,8 @@ 1071 1071 1072 1072 ATZ 1073 1073 1074 -1. 1075 -11. 1157 +1. 1158 +11. 1076 1076 111. Single-channel ABP mode (Use with LG01/LG02) 1077 1077 1078 1078 AT+FDR Reset Parameters to Factory Default, Keys Reserve ... ... @@ -1147,7 +1147,7 @@ 1147 1147 [[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]] 1148 1148 1149 1149 1150 -1. 1233 +1. 1151 1151 11. How to change the LoRa Frequency Bands/Region? 1152 1152 1153 1153 User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download. ... ... @@ -1154,7 +1154,7 @@ 1154 1154 1155 1155 1156 1156 1157 -1. 1240 +1. 1158 1158 11. How many RS485-Slave can RS485-BL connects? 1159 1159 1160 1160 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]]. ... ... @@ -1171,7 +1171,7 @@ 1171 1171 1172 1172 1173 1173 1174 -1. 1257 +1. 1175 1175 11. Why I can’t join TTN V3 in US915 /AU915 bands? 1176 1176 1177 1177 It might about the channels mapping. Please see for detail.
- 1653271763403-806.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +27.7 KB - Content
- 1653272787040-634.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +294.0 KB - Content
- 1653272817147-600.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +143.3 KB - Content
- 1653272901032-107.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +197.8 KB - Content
- 1653273818896-432.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +31.6 KB - Content
- 1653274001211-372.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +91.4 KB - Content