Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 31.1
edited by Xiaoling
on 2022/06/02 09:38
Change comment: Uploaded new attachment "1654133913295-597.png", version {1}
To version 28.4
edited by Xiaoling
on 2022/05/23 10:46
Change comment: There is no comment for this version

Summary

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 ===
... ... @@ -336,9 +336,8 @@
336 336  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
337 337  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
338 338  
339 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
326 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
340 340  
341 -
342 342  === 3.3.3 Configure read commands for each sampling ===
343 343  
344 344  (((
... ... @@ -436,7 +436,7 @@
436 436  
437 437  **Examples:**
438 438  
439 -1）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
425 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
440 440  
441 441  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
442 442  
... ... @@ -444,7 +444,7 @@
444 444  
445 445  [[image:1653271044481-711.png]]
446 446  
447 -2）For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
433 +1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
448 448  
449 449  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
450 450  
... ... @@ -463,18 +463,16 @@
463 463  * **c: define the position for valid value.  **
464 464  )))
465 465  
466 -**Examples:**
452 +Examples:
467 467  
468 468  * Grab bytes:
469 469  
470 470  [[image:1653271581490-837.png||height="313" width="722"]]
471 471  
472 -
473 473  * Grab a section.
474 474  
475 475  [[image:1653271648378-342.png||height="326" width="720"]]
476 476  
477 -
478 478  * Grab different sections.
479 479  
480 480  [[image:1653271657255-576.png||height="305" width="730"]]
... ... @@ -517,7 +517,6 @@
517 517  
518 518  [[image:1653271763403-806.png]]
519 519  
520 -
521 521  === 3.3.4 Compose the uplink payload ===
522 522  
523 523  (((
... ... @@ -525,7 +525,7 @@
525 525  )))
526 526  
527 527  (((
528 -(% style="color:#037691" %)**Examples: AT+DATAUP=0**
511 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
529 529  )))
530 530  
531 531  (((
... ... @@ -537,7 +537,7 @@
537 537  )))
538 538  
539 539  (((
540 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
523 +(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
541 541  )))
542 542  
543 543  (((
... ... @@ -546,12 +546,8 @@
546 546  
547 547  [[image:1653272787040-634.png||height="515" width="719"]]
548 548  
549 -
550 -
551 551  (((
552 -(% style="color:#037691" %)**Examples: AT+DATAUP=1**
553 -
554 -
533 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
555 555  )))
556 556  
557 557  (((
... ... @@ -563,7 +563,7 @@
563 563  )))
564 564  
565 565  (((
566 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
545 +(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
567 567  )))
568 568  
569 569  1. (((
... ... @@ -586,7 +586,6 @@
586 586  
587 587  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
588 588  
589 -
590 590  DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
591 591  
592 592  DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
... ... @@ -593,12 +593,10 @@
593 593  
594 594  DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
595 595  
596 -
597 597  Below are the uplink payloads:
598 598  
599 599  [[image:1653272901032-107.png]]
600 600  
601 -
602 602  (% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
603 603  
604 604   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
... ... @@ -609,8 +609,6 @@
609 609  
610 610   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
611 611  
612 -
613 -
614 614  === 3.3.5 Uplink on demand ===
615 615  
616 616  (((
... ... @@ -627,8 +627,6 @@
627 627  
628 628  (((
629 629  **0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
630 -
631 -
632 632  )))
633 633  
634 634  === 3.3.6 Uplink on Interrupt ===
... ... @@ -637,7 +637,6 @@
637 637  
638 638  [[image:1653273818896-432.png]]
639 639  
640 -
641 641  (((
642 642  AT+INTMOD=0  Disable Interrupt
643 643  )))
... ... @@ -652,8 +652,6 @@
652 652  
653 653  (((
654 654  AT+INTMOD=3  Interrupt trigger by rising edge.
655 -
656 -
657 657  )))
658 658  
659 659  == 3.4 Uplink Payload ==
... ... @@ -680,117 +680,92 @@
680 680  
681 681  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
682 682  
683 -(((
684 -{{{function Decoder(bytes, port) {}}}
685 -)))
686 686  
687 -(((
688 -{{{//Payload Formats of RS485-BL Deceive}}}
689 -)))
653 +function Decoder(bytes, port) {
690 690  
691 -(((
692 -{{{return {}}}
693 -)))
655 +~/~/Payload Formats of RS485-BL Deceive
694 694  
695 -(((
696 -{{{ //Battery,units:V}}}
697 -)))
657 +return {
698 698  
699 -(((
700 -{{{ BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,}}}
701 -)))
659 + ~/~/Battery,units:V
702 702  
703 -(((
704 -{{{ //GPIO_EXTI }}}
705 -)))
661 + BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
706 706  
707 -(((
708 -{{{ EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}}
709 -)))
663 + ~/~/GPIO_EXTI 
710 710  
711 -(((
712 -{{{ //payload of version}}}
713 -)))
665 + EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
714 714  
715 -(((
716 -{{{ Pay_ver:bytes[2],}}}
717 -)))
667 + ~/~/payload of version
718 718  
719 -(((
720 -{{{ }; }}}
721 -)))
669 + Pay_ver:bytes[2],
722 722  
723 -(((
724 -}
671 + };
725 725  
726 -
727 -)))
673 + }
728 728  
729 -(((
730 -TTN V3 uplink screen shot.
731 -)))
732 732  
733 -[[image:1653274001211-372.png||height="192" width="732"]]
734 734  
735 735  
736 -== 3.5 Configure RS485-BL via AT or Downlink ==
737 737  
738 -User can configure RS485-BL via AT Commands or LoRaWAN Downlink Commands
739 739  
740 -There are two kinds of Commands:
741 741  
742 -* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
681 +TTN V3 uplink screen shot.
743 743  
744 -* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-BL.  User can see these commands below:
683 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
745 745  
746 -=== 3.5.1 Common Commands: ===
685 +1.
686 +11. Configure RS485-BL via AT or Downlink
747 747  
748 -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: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
688 +User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
749 749  
690 +There are two kinds of Commands:
750 750  
751 -=== 3.5.2 Sensor related commands: ===
692 +* **Common Commands**: They should be available for each sensor, 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
752 752  
753 -==== ====
694 +* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
754 754  
755 -==== **Choose Device Type (RS485 or TTL)** ====
696 +1.
697 +11.
698 +111. Common Commands:
756 756  
700 +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]]
701 +
702 +
703 +1.
704 +11.
705 +111. Sensor related commands:
706 +
707 +==== Choose Device Type (RS485 or TTL) ====
708 +
757 757  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
758 758  
759 -* **AT Command**
711 +* AT Command
760 760  
761 -(% class="box infomessage" %)
762 -(((
763 763  **AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
764 -)))
765 765  
766 -(% class="box infomessage" %)
767 -(((
768 768  **AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
769 -)))
770 770  
771 771  
772 -* **Downlink Payload**
718 +* Downlink Payload
773 773  
774 -**0A aa**  ~-~->  same as AT+MOD=aa
720 +**0A aa**     à same as AT+MOD=aa
775 775  
776 776  
777 777  
778 -==== **RS485 Debug Command (AT+CFGDEV)** ====
724 +==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
779 779  
780 780  This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
781 781  
782 -* **AT Command**
728 +* AT Command
783 783  
784 -(% class="box infomessage" %)
785 -(((
786 -**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
787 -)))
730 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
788 788  
789 789  m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
790 790  
791 791  
792 -* **Downlink Payload**
793 793  
736 +* Downlink Payload
737 +
794 794  Format: A8 MM NN XX XX XX XX YY
795 795  
796 796  Where:
... ... @@ -804,15 +804,15 @@
804 804  
805 805  To connect a Modbus Alarm with below commands.
806 806  
807 -* The command to active alarm is: 0A 05 00 04 00 01 **4C B0**. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
751 +* The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
808 808  
809 -* The command to deactivate alarm is: 0A 05 00 04 00 00 **8D 70**. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
753 +* The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
810 810  
811 811  So if user want to use downlink command to control to RS485 Alarm, he can use:
812 812  
813 -(% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
757 +**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
814 814  
815 -(% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
759 +**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
816 816  
817 817  A8 is type code and 01 means add CRC-16/MODBUS at the end, the 3^^rd^^ byte is 06, means the next 6 bytes are the command to be sent to the RS485 network, the final byte 00 means this command don’t need to acquire output.
818 818  
... ... @@ -821,60 +821,48 @@
821 821  
822 822  Check TTL Sensor return:
823 823  
824 -[[image:1654132684752-193.png]]
768 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
825 825  
826 826  
827 827  
828 -==== **Set Payload version** ====
829 829  
773 +==== Set Payload version ====
774 +
830 830  This is the first byte of the uplink payload. RS485-BL can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload.
831 831  
832 -* **AT Command:**
777 +* AT Command:
833 833  
834 -(% class="box infomessage" %)
835 -(((
836 -**AT+PAYVER: Set PAYVER field = 1**
837 -)))
779 +AT+PAYVER: Set PAYVER field = 1
838 838  
839 839  
840 -* **Downlink Payload:**
782 +* Downlink Payload:
841 841  
842 -**0xAE 01**  ~-~-> Set PAYVER field =  0x01
784 +0xAE 01   à Set PAYVER field =  0x01
843 843  
844 -**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
786 +0xAE 0F   à Set PAYVER field =  0x0F
845 845  
846 846  
789 +==== Set RS485 Sampling Commands ====
847 847  
848 -==== **Set RS485 Sampling Commands** ====
849 -
850 850  AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
851 851  
852 -These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
793 +These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>path:#polling_485]].
853 853  
854 854  
855 -* **AT Command:**
796 +* AT Command:
856 856  
857 -(% class="box infomessage" %)
858 -(((
859 -**AT+COMMANDx: Configure RS485 read command to sensor.**
860 -)))
798 +AT+COMMANDx: Configure RS485 read command to sensor.
861 861  
862 -(% class="box infomessage" %)
863 -(((
864 -**AT+DATACUTx: Configure how to handle return from RS485 devices.**
865 -)))
800 +AT+DATACUTx: Configure how to handle return from RS485 devices.
866 866  
867 -(% class="box infomessage" %)
868 -(((
869 -**AT+SEARCHx: Configure search command**
870 -)))
802 +AT+SEARCHx: Configure search command
871 871  
872 872  
873 -* **Downlink Payload:**
805 +* Downlink Payload:
874 874  
875 -**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
807 +0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
876 876  
877 -(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
809 +Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
878 878  
879 879  Format: AF MM NN LL XX XX XX XX YY
880 880  
... ... @@ -881,23 +881,23 @@
881 881  Where:
882 882  
883 883  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
884 -* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
885 -* LL:  The length of AT+COMMAND or AT+DATACUT command
816 +* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
817 +* LL: The length of AT+COMMAND or AT+DATACUT command
886 886  * XX XX XX XX: AT+COMMAND or AT+DATACUT command
887 -* YY:  If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-BL will execute an uplink after got this command.
819 +* YY: If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-BL will execute an uplink after got this command.
888 888  
889 -**Example:**
821 +Example:
890 890  
891 -(% style="color:#037691" %)**AF 03 01 06 0A 05 00 04 00 01 00**(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1
823 +**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
892 892  
893 -(% style="color:#037691" %)**AF 03 02 06**(% style="color:orange" %)** 10 **(% style="color:red" %)**01 **(% style="color:green" %)**05 06 09 0A**(% style="color:#037691" %)** 00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**16**(%%),(% style="color:red" %)**1**(%%),(% style="color:green" %)**5+6+9+10**
825 +**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
894 894  
895 -(% style="color:#037691" %)**AF 03 02 06 **(% style="color:orange" %)**0B**(% style="color:red" %)** 02 **(% style="color:green" %)**05 07 08 0A **(% style="color:#037691" %)**00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**11**(%%),(% style="color:red" %)**2**(%%),(% style="color:green" %)**5~~7+8~~10**
827 +**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
896 896  
897 897  
898 -**0xAB** downlink command can be used for set AT+SEARCHx
830 +0xAB downlink command can be used for set AT+SEARCHx
899 899  
900 -**Example:** **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
832 +Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
901 901  
902 902  * AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
903 903  * AB aa 02 03 xx xx xx 02 yy yy(03 means there are 3 bytes after 03, they are xx xx xx;02 means there are 2 bytes after 02, they are yy yy) so the commands
... ... @@ -905,7 +905,6 @@
905 905  **AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
906 906  
907 907  
908 -
909 909  ==== Fast command to handle MODBUS device ====
910 910  
911 911  AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]].
... ... @@ -1076,13 +1076,13 @@
1076 1076  
1077 1077  
1078 1078  
1079 -1.
1010 +1.
1080 1080  11. Buttons
1081 1081  
1082 1082  |**Button**|**Feature**
1083 1083  |**RST**|Reboot RS485-BL
1084 1084  
1085 -1.
1016 +1.
1086 1086  11. +3V3 Output
1087 1087  
1088 1088  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
... ... @@ -1100,7 +1100,7 @@
1100 1100  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
1101 1101  
1102 1102  
1103 -1.
1034 +1.
1104 1104  11. +5V Output
1105 1105  
1106 1106  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
... ... @@ -1120,13 +1120,13 @@
1120 1120  
1121 1121  
1122 1122  
1123 -1.
1054 +1.
1124 1124  11. LEDs
1125 1125  
1126 1126  |**LEDs**|**Feature**
1127 1127  |**LED1**|Blink when device transmit a packet.
1128 1128  
1129 -1.
1060 +1.
1130 1130  11. Switch Jumper
1131 1131  
1132 1132  |**Switch Jumper**|**Feature**
... ... @@ -1172,7 +1172,7 @@
1172 1172  
1173 1173  
1174 1174  
1175 -1.
1106 +1.
1176 1176  11. Common AT Command Sequence
1177 1177  111. Multi-channel ABP mode (Use with SX1301/LG308)
1178 1178  
... ... @@ -1191,8 +1191,8 @@
1191 1191  
1192 1192  ATZ
1193 1193  
1194 -1.
1195 -11.
1125 +1.
1126 +11.
1196 1196  111. Single-channel ABP mode (Use with LG01/LG02)
1197 1197  
1198 1198  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1267,7 +1267,7 @@
1267 1267  [[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]]
1268 1268  
1269 1269  
1270 -1.
1201 +1.
1271 1271  11. How to change the LoRa Frequency Bands/Region?
1272 1272  
1273 1273  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1274,7 +1274,7 @@
1274 1274  
1275 1275  
1276 1276  
1277 -1.
1208 +1.
1278 1278  11. How many RS485-Slave can RS485-BL connects?
1279 1279  
1280 1280  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]].
... ... @@ -1291,7 +1291,7 @@
1291 1291  
1292 1292  
1293 1293  
1294 -1.
1225 +1.
1295 1295  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1296 1296  
1297 1297  It might about the channels mapping. Please see for detail.
1653274001211-372.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.4 KB
Content
1654132684752-193.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.8 KB
Content
1654133913295-597.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -116.2 KB
Content