Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 148.1
edited by Edwin Chen
on 2024/03/17 00:13
Change comment: There is no comment for this version
To version 146.1
edited by Edwin Chen
on 2024/03/03 16:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -53,7 +53,7 @@
53 53  (% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
54 54  (% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
55 55  (% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
56 -(% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=10,8,20,28,2,4,12,13,66,85,5**
56 +(% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=11,8,20,28,2,4,12,13,66,85,5,4**
57 57  
58 58  (% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
59 59  (% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
... ... @@ -656,10 +656,9 @@
656 656  
657 657  == 4.2 Why the uplink JSON format is not standard? ==
658 658  
659 +
659 659  The json format in uplink packet is not standard Json format. Below is the example. This is to make the payload as short as possible, due to NB-IoT transmit limition, a standard Json is not able to include 32 sets of sensors data with timestamp.
660 660  
661 -The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
662 -
663 663  [[image:image-20240229233154-1.png]]
664 664  
665 665  
... ... @@ -742,3 +742,4 @@
742 742  [[image:image-20240226111928-1.png]]
743 743  
744 744  
744 +