Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Edwin
	1	+XWiki.Xiaoling

Content

...	...	@@ -651,11 +651,14 @@
651	651	1*. **AT+TR=1800** ~/~/ The unit is seconds, and the default is to record data once every 1800 seconds (30 minutes, the minimum can be set to 180 seconds)
652	652	1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
653	653	1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
654		-1*. this will mean each uplink will actually include the 6 uplink data (24 set data which cover 12 hours). So if device doesn;t lost 6 continue data. There will not data lost.
	654	+1*. this will mean each uplink will actually include the 6 uplink data (24 set data which cover 12 hours). So if device doesn't lost 6 continue data. There will not data lost.
655	655
656	656
	657	+
	658	+
657	657	== 4.2 Why the uplink JSON format is not standard? ==
658	658
	661	+
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	661	The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
...	...	@@ -740,5 +740,3 @@
740	740	When the MCU is communicating with the NB-IoT module, the MCU response of AT Command will become slower, it might takes several seconds to response.
741	741
742	742	[[image:image-20240226111928-1.png]]
743		-
744		-