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,8 +51,11 @@ 51 51 52 52 [[image:1652953304999-717.png||height="424" width="733"]] 53 53 57 + 58 + 54 54 == 1.2 Specifications == 55 55 61 + 56 56 **Hardware System:** 57 57 58 58 * STM32L072CZT6 MCU ... ... @@ -59,8 +59,6 @@ 59 59 * SX1276/78 Wireless Chip 60 60 * Power Consumption (exclude RS485 device): 61 61 ** Idle: 6uA@3.3v 62 - 63 -* 64 64 ** 20dB Transmit: 130mA@3.3v 65 65 66 66 **Interface for Model:** ... ... @@ -114,9 +114,12 @@ 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 121 + 117 117 == 1.6 Hardware Change log == 118 118 119 119 ((( 125 + 126 + 120 120 v1.4 121 121 ))) 122 122 ... ... @@ -140,6 +140,8 @@ 140 140 141 141 ((( 142 142 Release version 150 + 151 + 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 165 + 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. 172 + 173 + 162 162 ))) 163 163 164 164 == 3.2 Example to join LoRaWAN network == ... ... @@ -194,8 +194,6 @@ 194 194 ))) 195 195 196 196 197 - 198 - 199 199 [[image:image-20220519174512-1.png]] 200 200 201 201 [[image:image-20220519174512-2.png||height="328" width="731"]] ... ... @@ -219,10 +219,13 @@ 219 219 220 220 [[image:1652953568895-172.png||height="232" width="724"]] 221 221 232 + 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. 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 + 226 226 ))) 227 227 228 228 === 3.3.1 onfigure UART settings for RS485 or TTL communication === ... ... @@ -323,8 +323,9 @@ 323 323 mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 324 324 )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 325 325 326 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>> path:#AT_CFGDEV]].339 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]]. 327 327 341 + 328 328 === 3.3.3 Configure read commands for each sampling === 329 329 330 330 ((( ... ... @@ -422,7 +422,7 @@ 422 422 423 423 **Examples:** 424 424 425 -1 .For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49439 +1)For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 426 426 427 427 If we set AT+SEARCH1=1,1E 56 34. (max 5 bytes for prefix) 428 428 ... ... @@ -430,7 +430,7 @@ 430 430 431 431 [[image:1653271044481-711.png]] 432 432 433 - 1.For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49447 +2)For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 434 434 435 435 If we set AT+SEARCH1=2, 1E 56 34+31 00 49 436 436 ... ... @@ -449,97 +449,143 @@ 449 449 * **c: define the position for valid value. ** 450 450 ))) 451 451 452 -Examples: 466 +**Examples:** 453 453 454 454 * Grab bytes: 455 455 456 456 [[image:1653271581490-837.png||height="313" width="722"]] 457 457 472 + 458 458 * Grab a section. 459 459 460 460 [[image:1653271648378-342.png||height="326" width="720"]] 461 461 477 + 462 462 * Grab different sections. 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 486 486 521 +=== 3.3.4 Compose the uplink payload === 487 487 488 - 489 -1. 490 -11. 491 -111. Compose the uplink payload 492 - 523 +((( 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.** 525 +))) 494 494 527 +((( 528 +(% style="color:#037691" %)**Examples: AT+DATAUP=0** 529 +))) 495 495 496 -**Examples: AT+DATAUP=0** 531 +((( 532 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**. 533 +))) 497 497 498 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**. 499 - 535 +((( 500 500 Final Payload is 537 +))) 501 501 502 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx 539 +((( 540 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx** 541 +))) 503 503 543 +((( 504 504 Where PAYVER is defined by AT+PAYVER, below is an example screen shot. 545 +))) 505 505 506 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]547 +[[image:1653272787040-634.png||height="515" width="719"]] 507 507 508 508 509 509 510 -**Examples: AT+DATAUP=1** 551 +((( 552 +(% style="color:#037691" %)**Examples: AT+DATAUP=1** 511 511 512 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**. 554 + 555 +))) 513 513 557 +((( 558 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**. 559 +))) 560 + 561 +((( 514 514 Final Payload is 563 +))) 515 515 516 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 565 +((( 566 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA** 567 +))) 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 569 +1. ((( 570 +Battery Info (2 bytes): Battery voltage 571 +))) 572 +1. ((( 573 +PAYVER (1 byte): Defined by AT+PAYVER 574 +))) 575 +1. ((( 576 +PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 577 +))) 578 +1. ((( 579 +PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 580 +))) 581 +1. ((( 582 +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 583 +))) 523 523 524 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]585 +[[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 530 530 531 -DATA 2=1^^st^^~~ 6^^th^^ byte ofValidvalue ofRETURN10=02aa05810a20590 +DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41 532 532 533 -DATA 3=7^^th^^ ~~11^^th^^ bytesof Valid value of RETURN10 =202020 2d 30592 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20 534 534 594 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30 535 535 536 536 537 537 Below are the uplink payloads: 538 538 539 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]599 +[[image:1653272901032-107.png]] 540 540 541 541 542 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below: 602 +(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below: 543 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 ... ... @@ -551,113 +551,154 @@ 551 551 552 552 553 553 554 -1. 555 -11. 556 -111. Uplink on demand 614 +=== 3.3.5 Uplink on demand === 557 557 616 +((( 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. 618 +))) 559 559 620 +((( 560 560 Downlink control command: 622 +))) 561 561 562 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL. 624 +((( 625 +**0x08 command**: Poll an uplink with current command set in RS485-BL. 626 +))) 563 563 564 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors. 628 +((( 629 +**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors. 565 565 631 + 632 +))) 566 566 634 +=== 3.3.6 Uplink on Interrupt === 567 567 568 -1. 569 -11. 570 -111. Uplink on Interrupt 636 +Put the interrupt sensor between 3.3v_out and GPIO ext. 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]]638 +[[image:1653273818896-432.png]] 573 573 640 + 641 +((( 574 574 AT+INTMOD=0 Disable Interrupt 643 +))) 575 575 645 +((( 576 576 AT+INTMOD=1 Interrupt trigger by rising or falling edge. 647 +))) 577 577 649 +((( 578 578 AT+INTMOD=2 Interrupt trigger by falling edge. ( Default Value) 651 +))) 579 579 653 +((( 580 580 AT+INTMOD=3 Interrupt trigger by rising edge. 581 581 656 + 657 +))) 582 582 583 -1. 584 -11. Uplink Payload 659 +== 3.4 Uplink Payload == 585 585 586 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands** 587 -|Value|((( 661 +(% border="1" style="background-color:#4f81bd; color:white; width:850px" %) 662 +|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands** 663 +|Value|(% style="width:130px" %)((( 664 +((( 588 588 Battery(mV) 666 +))) 589 589 668 +((( 590 590 & 670 +))) 591 591 672 +((( 592 592 Interrupt _Flag 593 -)))|((( 674 +))) 675 +)))|(% 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. 679 +)))|(% 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 683 +((( 684 +{{{function Decoder(bytes, port) {}}} 685 +))) 601 601 602 -function Decoder(bytes, port) { 687 +((( 688 +{{{//Payload Formats of RS485-BL Deceive}}} 689 +))) 603 603 604 -~/~/Payload Formats of RS485-BL Deceive 691 +((( 692 +{{{return {}}} 693 +))) 605 605 606 -return { 695 +((( 696 +{{{ //Battery,units:V}}} 697 +))) 607 607 608 - ~/~/Battery,units:V 699 +((( 700 +{{{ BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,}}} 701 +))) 609 609 610 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000, 703 +((( 704 +{{{ //GPIO_EXTI }}} 705 +))) 611 611 612 - ~/~/GPIO_EXTI 707 +((( 708 +{{{ EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}} 709 +))) 613 613 614 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE", 711 +((( 712 +{{{ //payload of version}}} 713 +))) 615 615 616 - ~/~/payload of version 715 +((( 716 +{{{ Pay_ver:bytes[2],}}} 717 +))) 617 617 618 - Pay_ver:bytes[2], 719 +((( 720 +{{{ }; }}} 721 +))) 619 619 620 - }; 723 +((( 724 +} 621 621 622 - } 726 + 727 +))) 623 623 729 +((( 730 +TTN V3 uplink screen shot. 731 +))) 624 624 733 +[[image:1653274001211-372.png||height="192" width="732"]] 625 625 626 626 736 +== 3.5 Configure RS485-BL via AT or Downlink == 627 627 738 +User can configure RS485-BL via AT Commands or LoRaWAN Downlink Commands 628 628 740 +There are two kinds of Commands: 629 629 630 -T TNV3uplink screenshot.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]] 631 631 632 - [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]744 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-BL. User can see these commands below: 633 633 634 -1. 635 -11. Configure RS485-BL via AT or Downlink 636 636 637 - Usercan configure RS485-BLvia [[ATCommands >>path:#_Using_the_AT]]or LoRaWAN DownlinkCommands747 +=== 3.5.1 Common Commands: === 638 638 639 -There are t wokinds ofCommands:749 +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]] 640 640 641 -* **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 642 642 643 - ***SensorRelatedCommands**: Thesecommandsare special designed for RS485-BL. User can see these commands below:752 +=== 3.5.2 Sensor related commands: === 644 644 645 -1. 646 -11. 647 -111. Common Commands: 754 +(% class="wikigeneratedid" %) 755 +==== ==== 648 648 649 - Theyshould be available foreachofDragino Sensors, such as: change uplink interval, reset device.For firmwarev1.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]]757 +==== **Choose Device Type (RS485 or TTL)** ==== 650 650 651 - 652 -1. 653 -11. 654 -111. Sensor related commands: 655 - 656 -==== Choose Device Type (RS485 or TTL) ==== 657 - 658 658 RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect. 659 659 660 -* AT Command 761 +* **AT Command** 661 661 662 662 **AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins. 663 663 ... ... @@ -664,17 +664,17 @@ 664 664 **AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins. 665 665 666 666 667 -* Downlink Payload 768 +* **Downlink Payload** 668 668 669 -**0A aa** àsame as AT+MOD=aa770 +**0A aa** ~-~-> same as AT+MOD=aa 670 670 671 671 672 672 673 -==== [[RS485 Debug Command>>path:#downlink_A8]](AT+CFGDEV) ====774 +==== **RS485 Debug Command (AT+CFGDEV)** ==== 674 674 675 675 This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling. 676 676 677 -* AT Command 778 +* **AT Command** 678 678 679 679 AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 680 680 ... ... @@ -681,9 +681,8 @@ 681 681 m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command. 682 682 683 683 785 +* **Downlink Payload** 684 684 685 -* Downlink Payload 686 - 687 687 Format: A8 MM NN XX XX XX XX YY 688 688 689 689 Where: ... ... @@ -693,6 +693,7 @@ 693 693 * XX XX XX XX: RS485 command total NN bytes 694 694 * YY: How many bytes will be uplink from the return of this RS485 command, if YY=0, RS485-BL will execute the downlink command without uplink; if YY>0, RS485-BL will uplink total YY bytes from the output of this RS485 command 695 695 796 + 696 696 **Example 1:** 697 697 698 698 To connect a Modbus Alarm with below commands. ... ... @@ -956,13 +956,13 @@ 956 956 957 957 958 958 959 -1. 1060 +1. 960 960 11. Buttons 961 961 962 962 |**Button**|**Feature** 963 963 |**RST**|Reboot RS485-BL 964 964 965 -1. 1066 +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. 1084 +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. 1104 +1. 1004 1004 11. LEDs 1005 1005 1006 1006 |**LEDs**|**Feature** 1007 1007 |**LED1**|Blink when device transmit a packet. 1008 1008 1009 -1. 1110 +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. 1156 +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. 1175 +1. 1176 +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. 1251 +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. 1258 +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. 1275 +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.
- 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
- 1654132684752-193.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +22.8 KB - Content