Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 0 removed)
  • image-20240229233154-1.png

Details

Page properties

Author

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

Content

...	...	@@ -94,8 +94,6 @@
94	94
95	95	* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
96	96
97		-* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
98		-
99	99	[[image:image-20230802112413-2.png]]
100	100
101	101
...	...	@@ -645,6 +645,15 @@
645	645	1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
646	646	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.
647	647
	646	+
	647	+== 4.2 Why the uplink JSON format is not standard? ==
	648	+
	649	+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.
	650	+
	651	+[[image:image-20240229233154-1.png]]
	652	+
	653	+
	654	+
648	648	= 5. Trouble Shooting: =
649	649
650	650	== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==

image-20240229233154-1.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+39.5 KB

Content