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, 12 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,7 +316,6 @@ 316 316 ))) 317 317 ))) 318 318 319 - 320 320 === 3.3.2 Configure sensors === 321 321 322 322 ((( ... ... @@ -337,9 +337,8 @@ 337 337 mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 338 338 )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 339 339 340 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>> ||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].326 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]]. 341 341 342 - 343 343 === 3.3.3 Configure read commands for each sampling === 344 344 345 345 ((( ... ... @@ -412,8 +412,8 @@ 412 412 413 413 **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is: 414 414 415 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px"%)416 -|( % style="width:498px" %)(((400 +(% border="1" class="table-bordered" %) 401 +|((( 417 417 **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m** 418 418 419 419 **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent** ... ... @@ -427,36 +427,39 @@ 427 427 428 428 **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx. 429 429 430 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px"%)431 -|( % style="width:577px" %)(((415 +(% border="1" class="table-bordered" %) 416 +|((( 432 432 **AT+SEARCHx=aa,xx xx xx xx xx** 433 433 434 434 * **aa: 1: prefix match mode; 2: prefix and suffix match mode** 435 435 * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix** 421 + 422 + 436 436 ))) 437 437 438 - **Examples:**425 +Examples: 439 439 440 -1 )For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49427 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 441 441 442 442 If we set AT+SEARCH1=1,1E 56 34. (max 5 bytes for prefix) 443 443 444 -The valid data will be all bytes after 1E 56 34 , so it is (% style="background-color:yellow" %)**2e 30 58 5f 36 41 30 31 00 49**431 +The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49 445 445 446 -[[image: 1653271044481-711.png]]433 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]] 447 447 448 -2)For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 449 449 436 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 437 + 450 450 If we set AT+SEARCH1=2, 1E 56 34+31 00 49 451 451 452 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is (%style="background-color:yellow" %) **2e 30 58 5f 36 41 30**440 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30 453 453 454 -[[image: 1653271276735-972.png]]442 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]] 455 455 444 + 456 456 **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes. 457 457 458 -(% style="background-color:#4f81bd; color:white; width:729px" %) 459 -|(% style="width:726px" %)((( 447 +|((( 460 460 **AT+DATACUTx=a,b,c** 461 461 462 462 * **a: length for the return of AT+COMMAND** ... ... @@ -464,143 +464,98 @@ 464 464 * **c: define the position for valid value. ** 465 465 ))) 466 466 467 - **Examples:**455 +Examples: 468 468 469 469 * Grab bytes: 470 470 471 -[[image: 1653271581490-837.png||height="313" width="722"]]459 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]] 472 472 473 - 474 474 * Grab a section. 475 475 476 -[[image: 1653271648378-342.png||height="326" width="720"]]463 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]] 477 477 478 - 479 479 * Grab different sections. 480 480 481 -[[image: 1653271657255-576.png||height="305" width="730"]]467 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]] 482 482 483 -((( 484 -(% style="color:red" %)**Note:** 485 -))) 486 486 487 -((( 470 +Note: 471 + 488 488 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. 489 -))) 490 490 491 -((( 492 -**Example:** 493 -))) 474 +Example: 494 494 495 -((( 496 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0 497 -))) 476 +AT+COMMAND1=11 01 1E D0,0 498 498 499 -((( 500 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34 501 -))) 478 +AT+SEARCH1=1,1E 56 34 502 502 503 -((( 504 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5 505 -))) 480 +AT+DATACUT1=0,2,1~~5 506 506 507 -((( 508 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 509 -))) 482 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 510 510 511 -((( 512 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 513 -))) 484 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 514 514 515 -((( 516 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36 517 -))) 486 +Valid payload after DataCUT command: 2e 30 58 5f 36 518 518 519 -[[image: 1653271763403-806.png]]488 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]] 520 520 521 521 522 -=== 3.3.4 Compose the uplink payload === 523 523 524 -((( 492 + 493 +1. 494 +11. 495 +111. Compose the uplink payload 496 + 525 525 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.** 526 -))) 527 527 528 -((( 529 -(% style="color:#037691" %)**Examples: AT+DATAUP=0** 530 -))) 531 531 532 -((( 533 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**. 534 -))) 500 +**Examples: AT+DATAUP=0** 535 535 536 -((( 502 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**. 503 + 537 537 Final Payload is 538 -))) 539 539 540 -((( 541 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx** 542 -))) 506 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx 543 543 544 -((( 545 545 Where PAYVER is defined by AT+PAYVER, below is an example screen shot. 546 -))) 547 547 548 -[[image: 1653272787040-634.png||height="515" width="719"]]510 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]] 549 549 550 550 551 551 552 -((( 553 -(% style="color:#037691" %)**Examples: AT+DATAUP=1** 514 +**Examples: AT+DATAUP=1** 554 554 555 - 556 -))) 516 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**. 557 557 558 -((( 559 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**. 560 -))) 561 - 562 -((( 563 563 Final Payload is 564 -))) 565 565 566 -((( 567 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA** 568 -))) 520 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 569 569 570 -1. ((( 571 -Battery Info (2 bytes): Battery voltage 572 -))) 573 -1. ((( 574 -PAYVER (1 byte): Defined by AT+PAYVER 575 -))) 576 -1. ((( 577 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 578 -))) 579 -1. ((( 580 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 581 -))) 582 -1. ((( 583 -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 584 -))) 522 +1. Battery Info (2 bytes): Battery voltage 523 +1. PAYVER (1 byte): Defined by AT+PAYVER 524 +1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 525 +1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 526 +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 585 585 586 -[[image: 1653272817147-600.png||height="437" width="717"]]528 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]] 587 587 530 + 588 588 So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA 589 589 533 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41 590 590 591 -DATA 1=RETURN1 ValidValue= (% style="background-color:#4f81bd;color:white"%)20200a33 9041535 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20 592 592 593 -DATA 2=1^^st^^ ~~6^^th^^ byte of Valid value of RETURN10=(% style="background-color:#4f81bd;color:white" %)02aa05810a20537 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30 594 594 595 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30 596 596 597 597 598 598 Below are the uplink payloads: 599 599 600 -[[image: 1653272901032-107.png]]543 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]] 601 601 602 602 603 - (% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:546 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below: 604 604 605 605 ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date) 606 606 ... ... @@ -612,123 +612,88 @@ 612 612 613 613 614 614 615 -=== 3.3.5 Uplink on demand === 558 +1. 559 +11. 560 +111. Uplink on demand 616 616 617 -((( 618 618 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. 619 -))) 620 620 621 -((( 622 622 Downlink control command: 623 -))) 624 624 625 -((( 626 -**0x08 command**: Poll an uplink with current command set in RS485-BL. 627 -))) 566 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL. 628 628 629 -((( 630 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors. 568 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors. 631 631 632 - 633 -))) 634 634 635 -=== 3.3.6 Uplink on Interrupt === 636 636 637 -Put the interrupt sensor between 3.3v_out and GPIO ext. 572 +1. 573 +11. 574 +111. Uplink on Interrupt 638 638 639 -[[image: 1653273818896-432.png]]576 +Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]] 640 640 641 -((( 642 642 AT+INTMOD=0 Disable Interrupt 643 -))) 644 644 645 -((( 646 646 AT+INTMOD=1 Interrupt trigger by rising or falling edge. 647 -))) 648 648 649 -((( 650 650 AT+INTMOD=2 Interrupt trigger by falling edge. ( Default Value) 651 -))) 652 652 653 -((( 654 654 AT+INTMOD=3 Interrupt trigger by rising edge. 655 -))) 656 656 657 -== 3.4 Uplink Payload == 658 658 659 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %) 660 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands** 661 -|Value|(% style="width:130px" %)((( 662 -((( 587 +1. 588 +11. Uplink Payload 589 + 590 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands** 591 +|Value|((( 663 663 Battery(mV) 664 -))) 665 665 666 -((( 667 667 & 668 -))) 669 669 670 -((( 671 671 Interrupt _Flag 672 -))) 673 -)))|(% style="width:93px" %)((( 597 +)))|((( 674 674 PAYLOAD_VER 675 675 676 676 677 -)))| (% 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.601 +)))|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. 678 678 679 679 Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors. 680 680 681 - (((605 + 682 682 function Decoder(bytes, port) { 683 -))) 684 684 685 -((( 686 686 ~/~/Payload Formats of RS485-BL Deceive 687 -))) 688 688 689 -((( 690 690 return { 691 -))) 692 692 693 -((( 694 694 ~/~/Battery,units:V 695 -))) 696 696 697 -((( 698 698 BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000, 699 -))) 700 700 701 -((( 702 702 ~/~/GPIO_EXTI 703 -))) 704 704 705 -((( 706 706 EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE", 707 -))) 708 708 709 -((( 710 710 ~/~/payload of version 711 -))) 712 712 713 -((( 714 714 Pay_ver:bytes[2], 715 -))) 716 716 717 -((( 718 718 }; 719 -))) 720 720 721 -((( 722 722 } 723 -))) 724 724 725 -((( 628 + 629 + 630 + 631 + 632 + 633 + 726 726 TTN V3 uplink screen shot. 727 -))) 728 728 729 -[[image: 1653274001211-372.png||height="192" width="732"]]636 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]] 730 730 731 -== 3.5 Configure RS485-BL via AT or Downlink == 638 +1. 639 +11. Configure RS485-BL via AT or Downlink 732 732 733 733 User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]or LoRaWAN Downlink Commands 734 734 ... ... @@ -738,15 +738,15 @@ 738 738 739 739 * **Sensor Related Commands**: These commands are special designed for RS485-BL. User can see these commands below: 740 740 741 -1. 742 -11. 649 +1. 650 +11. 743 743 111. Common Commands: 744 744 745 745 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]] 746 746 747 747 748 -1. 749 -11. 656 +1. 657 +11. 750 750 111. Sensor related commands: 751 751 752 752 ==== Choose Device Type (RS485 or TTL) ==== ... ... @@ -1052,13 +1052,13 @@ 1052 1052 1053 1053 1054 1054 1055 -1. 963 +1. 1056 1056 11. Buttons 1057 1057 1058 1058 |**Button**|**Feature** 1059 1059 |**RST**|Reboot RS485-BL 1060 1060 1061 -1. 969 +1. 1062 1062 11. +3V3 Output 1063 1063 1064 1064 RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor. ... ... @@ -1076,7 +1076,7 @@ 1076 1076 By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time 1077 1077 1078 1078 1079 -1. 987 +1. 1080 1080 11. +5V Output 1081 1081 1082 1082 RS485-BL has a Controllable +5V output, user can use this output to power external sensor. ... ... @@ -1096,13 +1096,13 @@ 1096 1096 1097 1097 1098 1098 1099 -1. 1007 +1. 1100 1100 11. LEDs 1101 1101 1102 1102 |**LEDs**|**Feature** 1103 1103 |**LED1**|Blink when device transmit a packet. 1104 1104 1105 -1. 1013 +1. 1106 1106 11. Switch Jumper 1107 1107 1108 1108 |**Switch Jumper**|**Feature** ... ... @@ -1148,7 +1148,7 @@ 1148 1148 1149 1149 1150 1150 1151 -1. 1059 +1. 1152 1152 11. Common AT Command Sequence 1153 1153 111. Multi-channel ABP mode (Use with SX1301/LG308) 1154 1154 ... ... @@ -1167,8 +1167,8 @@ 1167 1167 1168 1168 ATZ 1169 1169 1170 -1. 1171 -11. 1078 +1. 1079 +11. 1172 1172 111. Single-channel ABP mode (Use with LG01/LG02) 1173 1173 1174 1174 AT+FDR Reset Parameters to Factory Default, Keys Reserve ... ... @@ -1243,7 +1243,7 @@ 1243 1243 [[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]] 1244 1244 1245 1245 1246 -1. 1154 +1. 1247 1247 11. How to change the LoRa Frequency Bands/Region? 1248 1248 1249 1249 User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download. ... ... @@ -1250,7 +1250,7 @@ 1250 1250 1251 1251 1252 1252 1253 -1. 1161 +1. 1254 1254 11. How many RS485-Slave can RS485-BL connects? 1255 1255 1256 1256 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]]. ... ... @@ -1267,7 +1267,7 @@ 1267 1267 1268 1268 1269 1269 1270 -1. 1178 +1. 1271 1271 11. Why I can’t join TTN V3 in US915 /AU915 bands? 1272 1272 1273 1273 It might about the channels mapping. Please see for detail.
- 1652954654347-831.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.7 KB - Content
- 1653271044481-711.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -27.8 KB - Content
- 1653271276735-972.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -26.6 KB - Content
- 1653271581490-837.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.7 KB - Content
- 1653271648378-342.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -131.4 KB - Content
- 1653271657255-576.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -142.6 KB - Content
- 1653271763403-806.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -27.7 KB - Content
- 1653272787040-634.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -294.0 KB - Content
- 1653272817147-600.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -143.3 KB - Content
- 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