Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -55,7 +55,6 @@
55	55
56	56	== 2.2 Speed Up Network Attach time ==
57	57
58		-
59	59	**BG95-M2** supports multi bands (% style="color:blue" %)**in NB-IoT and LTE-M. **(%%) It will search one by one and try to attach, this will take a lot of time and even cause attach fail and show **Signal Strenght:99**.
60	60
61	61	**Note:**Before using the NB module command, users need to power on the NB module. Run the AT+QSW command to turn on and off the NB module.Remember to shut down after using the NB module command, otherwise it will consume power.
...	...	@@ -74,7 +74,7 @@
74	74
75	75	See bands used for different provider:** [[NB-IoT Deployment , Bands, Operator list>>http://wiki.dragino.com/xwiki/bin/view/Main/NB-IoT%20Deployment%20%2C%20Bands%2C%20Operator%20list/]]**
76	76
77		-=== **1. Configure Frequency Band** ===
	76	+=== **1.Configure Frequency Band** ===
78	78
79	79	AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
80	80
...	...	@@ -144,7 +144,7 @@
144	144	AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
145	145
146	146
147		-=== **2. Configure search network sequence** ===
	146	+=== **2.Configure search network sequence** ===
148	148
149	149	AT+QCFG="nwscanseq",<scanseq>,1
150	150
...	...	@@ -157,9 +157,8 @@
157	157
158	158	AT+QCFG="nwscanseq",02,1  ~/~/Priority search for eMTC
159	159
	159	+=== **3.Configure Network Category to be Searched for under LTE RAT** ===
160	160
161		-=== **3. Configure Network Category to be Searched for under LTE RAT** ===
162		-
163	163	AT+QCFG="iotopmode",mode,1
164	164
165	165	0 eMTC
...	...	@@ -166,9 +166,8 @@
166	166	1 NB-IoT
167	167	2 eMTC and NB-IoT
168	168
	167	+=== **4.AT command to set frequency band and network category** ===
169	169
170		-=== **4. AT command to set frequency band and network category** ===
171		-
172	172	AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f  ~/~/<eMTC_bandval>,<NB-IoT_bandval>
173	173
174	174	AT+IOTMOD=0  ~/~/ 0 eMTC  1 NB-IoT  2 eMTC and NB-IoT
...	...	@@ -190,7 +190,6 @@
190	190
191	191	== 3.1 General UDP Connection ==
192	192
193		-
194	194	The NB-IoT Sensor can send packet to server use UDP protocol.
195	195
196	196
...	...	@@ -235,7 +235,7 @@
235	235
236	236	* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%) ~/~/ Set COAP server address and port
237	237
238		-* (% style="color:#037691" %)**AT+URI1=11,"i"**  (%%) ~/~/  Configure CoAP Message Options
	234	+* (% style="color:#037691" %)**AT+URI1=11,"I"**  (%%) ~/~/  Configure CoAP Message Options
239	239	* (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%) ~/~/ Configure CoAP Message Options
240	240
241	241	[[image:image-20240819103212-2.png]]
...	...	@@ -309,6 +309,7 @@
309	309
310	310	* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
311	311
	308	+
312	312	==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
313	313
314	314
...	...	@@ -348,6 +348,7 @@
348	348
349	349	* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
350	350
	348	+
351	351	==== 3.3.3.2 Uplink Examples ====
352	352
353	353
...	...	@@ -419,6 +419,7 @@
419	419
420	420	* (% style="color:blue" %)**S31B-CB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction.
421	421
	420	+
422	422	=== 3.4.1 For device Already has template ===
423	423
424	424	==== 3.4.1.1 Create Device ====
...	...	@@ -578,6 +578,7 @@
578	578	* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
579	579	* (% style="color:#037691" %)**AT+PWD=“Your device token”**
580	580
	580	+
581	581	== 3.6 ThingsBoard.Cloud (via MQTT) ==
582	582
583	583	=== 3.6.1 Configure ThingsBoard ===
...	...	@@ -716,6 +716,7 @@
716	716
717	717	* (% style="color:#037691" %)**AT+PWD=“Your device token”**
718	718
	719	+
719	719	=== 3.7.2 Simulate with MQTT.fx ===
720	720
721	721
...	...	@@ -880,6 +880,7 @@
880	880	1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours.
881	881	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.
882	882
	884	+
883	883	== 6.2 Why the uplink JSON format is not standard? ==
884	884
885	885