Summary

• Page properties (1 modified, 0 added, 0 removed)

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=11,8,20,28,2,4,12,13,66,85,5,4**
	56	+(% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=10,8,20,28,2,4,12,13,66,85,5**
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,9 +656,10 @@
656	656
657	657	== 4.2 Why the uplink JSON format is not standard? ==
658	658
659		-
660	660	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.
661	661
	661	+The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
	662	+
662	662	[[image:image-20240229233154-1.png]]
663	663
664	664
...	...	@@ -741,4 +741,3 @@
741	741	[[image:image-20240226111928-1.png]]
742	742
743	743
744		-