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, 6 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 === ... ... @@ -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 49425 +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 49433 +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,143 +463,97 @@ 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"]] 481 481 482 -((( 483 483 (% style="color:red" %)**Note:** 484 -))) 485 485 486 -((( 487 487 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 -))) 489 489 490 -((( 491 491 **Example:** 492 -))) 493 493 494 -((( 495 495 (% style="color:red" %)AT+COMMAND1=11 01 1E D0,0 496 -))) 497 497 498 -((( 499 499 (% style="color:red" %)AT+SEARCH1=1,1E 56 34 500 -))) 501 501 502 -((( 503 503 (% style="color:red" %)AT+DATACUT1=0,2,1~~5 504 -))) 505 505 506 -((( 507 507 (% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 508 -))) 509 509 510 -((( 511 511 (% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 512 -))) 513 513 514 -((( 515 515 (% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36 516 -))) 517 517 518 -[[image: 1653271763403-806.png]]484 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]] 519 519 520 520 521 -=== 3.3.4 Compose the uplink payload === 522 522 523 -((( 488 + 489 +1. 490 +11. 491 +111. Compose the uplink payload 492 + 524 524 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 -))) 526 526 527 -((( 528 -(% style="color:#037691" %)**Examples: AT+DATAUP=0** 529 -))) 530 530 531 -((( 532 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**. 533 -))) 496 +**Examples: AT+DATAUP=0** 534 534 535 -((( 498 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**. 499 + 536 536 Final Payload is 537 -))) 538 538 539 -((( 540 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx** 541 -))) 502 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx 542 542 543 -((( 544 544 Where PAYVER is defined by AT+PAYVER, below is an example screen shot. 545 -))) 546 546 547 -[[image: 1653272787040-634.png||height="515" width="719"]]506 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]] 548 548 549 549 550 550 551 -((( 552 -(% style="color:#037691" %)**Examples: AT+DATAUP=1** 510 +**Examples: AT+DATAUP=1** 553 553 554 - 555 -))) 512 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**. 556 556 557 -((( 558 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**. 559 -))) 560 - 561 -((( 562 562 Final Payload is 563 -))) 564 564 565 -((( 566 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA** 567 -))) 516 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 568 568 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 -))) 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 584 584 585 -[[image: 1653272817147-600.png||height="437" width="717"]]524 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]] 586 586 526 + 587 587 So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA 588 588 529 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41 589 589 590 -DATA 1=RETURN1 ValidValue= (% style="background-color:#4f81bd;color:white"%)20200a33 9041531 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20 591 591 592 -DATA 2=1^^st^^ ~~6^^th^^ byte of Valid value of RETURN10=(% style="background-color:#4f81bd;color:white" %)02aa05810a20533 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30 593 593 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 596 597 597 Below are the uplink payloads: 598 598 599 -[[image: 1653272901032-107.png]]539 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]] 600 600 601 601 602 - (% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:542 +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) 605 605 ... ... @@ -611,147 +611,108 @@ 611 611 612 612 613 613 614 -=== 3.3.5 Uplink on demand === 554 +1. 555 +11. 556 +111. Uplink on demand 615 615 616 -((( 617 617 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 -))) 619 619 620 -((( 621 621 Downlink control command: 622 -))) 623 623 624 -((( 625 -**0x08 command**: Poll an uplink with current command set in RS485-BL. 626 -))) 562 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL. 627 627 628 -((( 629 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors. 564 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors. 630 630 631 - 632 -))) 633 633 634 -=== 3.3.6 Uplink on Interrupt === 635 635 636 -Put the interrupt sensor between 3.3v_out and GPIO ext. 568 +1. 569 +11. 570 +111. Uplink on Interrupt 637 637 638 -[[image: 1653273818896-432.png]]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]] 639 639 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 655 656 - 657 -))) 658 658 659 -== 3.4 Uplink Payload == 583 +1. 584 +11. Uplink Payload 660 660 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 -((( 586 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands** 587 +|Value|((( 665 665 Battery(mV) 666 -))) 667 667 668 -((( 669 669 & 670 -))) 671 671 672 -((( 673 673 Interrupt _Flag 674 -))) 675 -)))|(% style="width:93px" %)((( 593 +)))|((( 676 676 PAYLOAD_VER 677 677 678 678 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.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. 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 -))) 602 +function Decoder(bytes, port) { 690 690 691 -((( 692 -{{{return {}}} 693 -))) 604 +~/~/Payload Formats of RS485-BL Deceive 694 694 695 -((( 696 -{{{ //Battery,units:V}}} 697 -))) 606 +return { 698 698 699 -((( 700 -{{{ BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,}}} 701 -))) 608 + ~/~/Battery,units:V 702 702 703 -((( 704 -{{{ //GPIO_EXTI }}} 705 -))) 610 + BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000, 706 706 707 -((( 708 -{{{ EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}} 709 -))) 612 + ~/~/GPIO_EXTI 710 710 711 -((( 712 -{{{ //payload of version}}} 713 -))) 614 + EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE", 714 714 715 -((( 716 -{{{ Pay_ver:bytes[2],}}} 717 -))) 616 + ~/~/payload of version 718 718 719 -((( 720 -{{{ }; }}} 721 -))) 618 + Pay_ver:bytes[2], 722 722 723 -((( 724 -} 620 + }; 725 725 726 - 727 -))) 622 + } 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**(%%):Theyshouldbe available for each sensor, such as: change uplinkinterval, reset device. Forfirmwarev1.3, user canfind what common commands itsupports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]630 +TTN V3 uplink screen shot. 743 743 744 - * (% style="color:#4f81bd" %)**Sensor RelatedCommands**(%%):Thesecommands arespecialdesigned for RS485-BL. User can see thesecommands below:632 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]] 745 745 634 +1. 635 +11. Configure RS485-BL via AT or Downlink 746 746 637 +User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]or LoRaWAN Downlink Commands 747 747 748 - ===3.5.1Common Commands:===639 +There are two kinds of Commands: 749 749 750 -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 Commandsand Downlink Command>>doc:Main.End.WebHome]]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 751 751 643 +* **Sensor Related Commands**: These commands are special designed for RS485-BL. User can see these commands below: 752 752 753 -=== 3.5.2 Sensor related commands: === 645 +1. 646 +11. 647 +111. Common Commands: 754 754 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 + 651 + 652 +1. 653 +11. 654 +111. Sensor related commands: 655 + 755 755 ==== Choose Device Type (RS485 or TTL) ==== 756 756 757 757 RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect. ... ... @@ -1055,13 +1055,13 @@ 1055 1055 1056 1056 1057 1057 1058 -1. 959 +1. 1059 1059 11. Buttons 1060 1060 1061 1061 |**Button**|**Feature** 1062 1062 |**RST**|Reboot RS485-BL 1063 1063 1064 -1. 965 +1. 1065 1065 11. +3V3 Output 1066 1066 1067 1067 RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor. ... ... @@ -1079,7 +1079,7 @@ 1079 1079 By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time 1080 1080 1081 1081 1082 -1. 983 +1. 1083 1083 11. +5V Output 1084 1084 1085 1085 RS485-BL has a Controllable +5V output, user can use this output to power external sensor. ... ... @@ -1099,13 +1099,13 @@ 1099 1099 1100 1100 1101 1101 1102 -1. 1003 +1. 1103 1103 11. LEDs 1104 1104 1105 1105 |**LEDs**|**Feature** 1106 1106 |**LED1**|Blink when device transmit a packet. 1107 1107 1108 -1. 1009 +1. 1109 1109 11. Switch Jumper 1110 1110 1111 1111 |**Switch Jumper**|**Feature** ... ... @@ -1151,7 +1151,7 @@ 1151 1151 1152 1152 1153 1153 1154 -1. 1055 +1. 1155 1155 11. Common AT Command Sequence 1156 1156 111. Multi-channel ABP mode (Use with SX1301/LG308) 1157 1157 ... ... @@ -1170,8 +1170,8 @@ 1170 1170 1171 1171 ATZ 1172 1172 1173 -1. 1174 -11. 1074 +1. 1075 +11. 1175 1175 111. Single-channel ABP mode (Use with LG01/LG02) 1176 1176 1177 1177 AT+FDR Reset Parameters to Factory Default, Keys Reserve ... ... @@ -1246,7 +1246,7 @@ 1246 1246 [[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]] 1247 1247 1248 1248 1249 -1. 1150 +1. 1250 1250 11. How to change the LoRa Frequency Bands/Region? 1251 1251 1252 1252 User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download. ... ... @@ -1253,7 +1253,7 @@ 1253 1253 1254 1254 1255 1255 1256 -1. 1157 +1. 1257 1257 11. How many RS485-Slave can RS485-BL connects? 1258 1258 1259 1259 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]]. ... ... @@ -1270,7 +1270,7 @@ 1270 1270 1271 1271 1272 1272 1273 -1. 1174 +1. 1274 1274 11. Why I can’t join TTN V3 in US915 /AU915 bands? 1275 1275 1276 1276 It might about the channels mapping. Please see for detail.
- 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