Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 29.31
edited by Xiaoling
on 2022/06/02 08:55
Change comment: There is no comment for this version
To version 24.1
edited by Xiaoling
on 2022/05/23 10:09
Change comment: Uploaded new attachment "1653271763403-806.png", version {1}

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 ===
... ... @@ -316,8 +316,6 @@
316 316  )))
317 317  )))
318 318  
319 -
320 -
321 321  === 3.3.2 Configure sensors ===
322 322  
323 323  (((
... ... @@ -338,9 +338,8 @@
338 338  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
339 339  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
340 340  
341 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
326 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
342 342  
343 -
344 344  === 3.3.3 Configure read commands for each sampling ===
345 345  
346 346  (((
... ... @@ -438,7 +438,7 @@
438 438  
439 439  **Examples:**
440 440  
441 -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
442 442  
443 443  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
444 444  
... ... @@ -446,7 +446,7 @@
446 446  
447 447  [[image:1653271044481-711.png]]
448 448  
449 -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
450 450  
451 451  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
452 452  
... ... @@ -465,139 +465,98 @@
465 465  * **c: define the position for valid value.  **
466 466  )))
467 467  
452 +Examples:
468 468  
469 -**Examples:**
470 -
471 471  * Grab bytes:
472 472  
473 473  [[image:1653271581490-837.png||height="313" width="722"]]
474 474  
475 -
476 476  * Grab a section.
477 477  
478 478  [[image:1653271648378-342.png||height="326" width="720"]]
479 479  
480 -
481 481  * Grab different sections.
482 482  
483 483  [[image:1653271657255-576.png||height="305" width="730"]]
484 484  
485 -(((
486 486  (% style="color:red" %)**Note:**
487 -)))
488 488  
489 -(((
490 490  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.
491 -)))
492 492  
493 -(((
494 494  **Example:**
495 -)))
496 496  
497 -(((
498 498  (% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
499 -)))
500 500  
501 -(((
502 502  (% style="color:red" %)AT+SEARCH1=1,1E 56 34
503 -)))
504 504  
505 -(((
506 506  (% style="color:red" %)AT+DATACUT1=0,2,1~~5
507 -)))
508 508  
509 -(((
510 510  (% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
511 -)))
512 512  
513 -(((
514 514  (% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
515 -)))
516 516  
517 -(((
518 518  (% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
519 -)))
520 520  
521 -[[image:1653271763403-806.png]]
484 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
522 522  
523 523  
524 -=== 3.3.4 Compose the uplink payload ===
525 525  
526 -(((
488 +
489 +1.
490 +11.
491 +111. Compose the uplink payload
492 +
527 527  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.**
528 -)))
529 529  
530 -(((
531 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
532 -)))
533 533  
534 -(((
535 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
536 -)))
496 +**Examples: AT+DATAUP=0**
537 537  
538 -(((
498 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
499 +
539 539  Final Payload is
540 -)))
541 541  
542 -(((
543 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
544 -)))
502 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
545 545  
546 -(((
547 547  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
548 -)))
549 549  
550 -[[image:1653272787040-634.png||height="515" width="719"]]
506 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
551 551  
552 552  
553 -(((
554 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
555 -)))
556 556  
557 -(((
558 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
559 -)))
510 +**Examples: AT+DATAUP=1**
560 560  
561 -(((
512 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
513 +
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  
589 -DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
529 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
590 590  
591 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
531 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
592 592  
593 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
533 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
594 594  
535 +
536 +
595 595  Below are the uplink payloads:
596 596  
597 -[[image:1653272901032-107.png]]
539 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
598 598  
599 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
600 600  
542 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
543 +
601 601   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
602 602  
603 603   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -606,121 +606,90 @@
606 606  
607 607   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
608 608  
609 -=== 3.3.5 Uplink on demand ===
610 610  
611 -(((
553 +
554 +1.
555 +11.
556 +111. Uplink on demand
557 +
612 612  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.
613 -)))
614 614  
615 -(((
616 616  Downlink control command:
617 -)))
618 618  
619 -(((
620 -**0x08 command**: Poll an uplink with current command set in RS485-BL.
621 -)))
562 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
622 622  
623 -(((
624 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
625 -)))
564 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
626 626  
627 -=== 3.3.6 Uplink on Interrupt ===
628 628  
629 -Put the interrupt sensor between 3.3v_out and GPIO ext.
630 630  
631 -[[image:1653273818896-432.png]]
568 +1.
569 +11.
570 +111. Uplink on Interrupt
632 632  
633 -(((
572 +Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
573 +
634 634  AT+INTMOD=0  Disable Interrupt
635 -)))
636 636  
637 -(((
638 638  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
639 -)))
640 640  
641 -(((
642 642  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
643 -)))
644 644  
645 -(((
646 646  AT+INTMOD=3  Interrupt trigger by rising edge.
647 -)))
648 648  
649 -== 3.4 Uplink Payload ==
650 650  
651 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
652 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
653 -|Value|(% style="width:130px" %)(((
654 -(((
583 +1.
584 +11. Uplink Payload
585 +
586 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
587 +|Value|(((
655 655  Battery(mV)
656 -)))
657 657  
658 -(((
659 659  &
660 -)))
661 661  
662 -(((
663 663  Interrupt _Flag
664 -)))
665 -)))|(% style="width:93px" %)(((
593 +)))|(((
666 666  PAYLOAD_VER
667 667  
668 668  
669 -)))|(% 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.
670 670  
671 671  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
672 672  
673 -(((
601 +
674 674  function Decoder(bytes, port) {
675 -)))
676 676  
677 -(((
678 678  ~/~/Payload Formats of RS485-BL Deceive
679 -)))
680 680  
681 -(((
682 682  return {
683 -)))
684 684  
685 -(((
686 686   ~/~/Battery,units:V
687 -)))
688 688  
689 -(((
690 690   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
691 -)))
692 692  
693 -(((
694 694   ~/~/GPIO_EXTI 
695 -)))
696 696  
697 -(((
698 698   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
699 -)))
700 700  
701 -(((
702 702   ~/~/payload of version
703 -)))
704 704  
705 -(((
706 706   Pay_ver:bytes[2],
707 -)))
708 708  
709 -(((
710 710   };
711 -)))
712 712  
713 -(((
714 714   }
715 -)))
716 716  
717 -(((
624 +
625 +
626 +
627 +
628 +
629 +
718 718  TTN V3 uplink screen shot.
719 -)))
720 720  
721 -[[image:1653274001211-372.png||height="192" width="732"]]
632 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
722 722  
723 -== 3.5 Configure RS485-BL via AT or Downlink ==
634 +1.
635 +11. Configure RS485-BL via AT or Downlink
724 724  
725 725  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
726 726  
... ... @@ -730,15 +730,15 @@
730 730  
731 731  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
732 732  
733 -1.
734 -11.
645 +1.
646 +11.
735 735  111. Common Commands:
736 736  
737 737  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]]
738 738  
739 739  
740 -1.
741 -11.
652 +1.
653 +11.
742 742  111. Sensor related commands:
743 743  
744 744  ==== Choose Device Type (RS485 or TTL) ====
... ... @@ -1044,13 +1044,13 @@
1044 1044  
1045 1045  
1046 1046  
1047 -1.
959 +1.
1048 1048  11. Buttons
1049 1049  
1050 1050  |**Button**|**Feature**
1051 1051  |**RST**|Reboot RS485-BL
1052 1052  
1053 -1.
965 +1.
1054 1054  11. +3V3 Output
1055 1055  
1056 1056  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
... ... @@ -1068,7 +1068,7 @@
1068 1068  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
1069 1069  
1070 1070  
1071 -1.
983 +1.
1072 1072  11. +5V Output
1073 1073  
1074 1074  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
... ... @@ -1088,13 +1088,13 @@
1088 1088  
1089 1089  
1090 1090  
1091 -1.
1003 +1.
1092 1092  11. LEDs
1093 1093  
1094 1094  |**LEDs**|**Feature**
1095 1095  |**LED1**|Blink when device transmit a packet.
1096 1096  
1097 -1.
1009 +1.
1098 1098  11. Switch Jumper
1099 1099  
1100 1100  |**Switch Jumper**|**Feature**
... ... @@ -1140,7 +1140,7 @@
1140 1140  
1141 1141  
1142 1142  
1143 -1.
1055 +1.
1144 1144  11. Common AT Command Sequence
1145 1145  111. Multi-channel ABP mode (Use with SX1301/LG308)
1146 1146  
... ... @@ -1159,8 +1159,8 @@
1159 1159  
1160 1160  ATZ
1161 1161  
1162 -1.
1163 -11.
1074 +1.
1075 +11.
1164 1164  111. Single-channel ABP mode (Use with LG01/LG02)
1165 1165  
1166 1166  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1235,7 +1235,7 @@
1235 1235  [[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]]
1236 1236  
1237 1237  
1238 -1.
1150 +1.
1239 1239  11. How to change the LoRa Frequency Bands/Region?
1240 1240  
1241 1241  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1242,7 +1242,7 @@
1242 1242  
1243 1243  
1244 1244  
1245 -1.
1157 +1.
1246 1246  11. How many RS485-Slave can RS485-BL connects?
1247 1247  
1248 1248  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]].
... ... @@ -1259,7 +1259,7 @@
1259 1259  
1260 1260  
1261 1261  
1262 -1.
1174 +1.
1263 1263  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1264 1264  
1265 1265  It might about the channels mapping. Please see for detail.
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