Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -55,6 +55,7 @@
55	55
56	56	== 2.2 Speed Up Network Attach time ==
57	57
	58	+
58	58	**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**.
59	59
60	60	**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.
...	...	@@ -73,7 +73,7 @@
73	73
74	74	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/]]**
75	75
76		-=== **1.Configure Frequency Band** ===
	77	+=== **1. Configure Frequency Band** ===
77	77
78	78	AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
79	79
...	...	@@ -143,7 +143,7 @@
143	143	AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
144	144
145	145
146		-=== **2.Configure search network sequence** ===
	147	+=== **2. Configure search network sequence** ===
147	147
148	148	AT+QCFG="nwscanseq",<scanseq>,1
149	149
...	...	@@ -156,8 +156,9 @@
156	156
157	157	AT+QCFG="nwscanseq",02,1  ~/~/Priority search for eMTC
158	158
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	+
161	161	AT+QCFG="iotopmode",mode,1
162	162
163	163	0 eMTC
...	...	@@ -164,8 +164,9 @@
164	164	1 NB-IoT
165	165	2 eMTC and NB-IoT
166	166
167		-=== **4.AT command to set frequency band and network category** ===
168	168
	170	+=== **4. AT command to set frequency band and network category** ===
	171	+
169	169	AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f  ~/~/<eMTC_bandval>,<NB-IoT_bandval>
170	170
171	171	AT+IOTMOD=0  ~/~/ 0 eMTC  1 NB-IoT  2 eMTC and NB-IoT
...	...	@@ -187,6 +187,7 @@
187	187
188	188	== 3.1 General UDP Connection ==
189	189
	193	+
190	190	The NB-IoT Sensor can send packet to server use UDP protocol.
191	191
192	192
...	...	@@ -231,7 +231,7 @@
231	231
232	232	* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%) ~/~/ Set COAP server address and port
233	233
234		-* (% style="color:#037691" %)**AT+URI1=11,"I"**  (%%) ~/~/  Configure CoAP Message Options
	238	+* (% style="color:#037691" %)**AT+URI1=11,"i"**  (%%) ~/~/  Configure CoAP Message Options
235	235	* (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%) ~/~/ Configure CoAP Message Options
236	236
237	237	[[image:image-20240819103212-2.png]]
...	...	@@ -305,7 +305,6 @@
305	305
306	306	* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
307	307
308		-
309	309	==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
310	310
311	311
...	...	@@ -345,7 +345,6 @@
345	345
346	346	* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
347	347
348		-
349	349	==== 3.3.3.2 Uplink Examples ====
350	350
351	351
...	...	@@ -417,7 +417,6 @@
417	417
418	418	* (% 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.
419	419
420		-
421	421	=== 3.4.1 For device Already has template ===
422	422
423	423	==== 3.4.1.1 Create Device ====
...	...	@@ -577,7 +577,6 @@
577	577	* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
578	578	* (% style="color:#037691" %)**AT+PWD=“Your device token”**
579	579
580		-
581	581	== 3.6 ThingsBoard.Cloud (via MQTT) ==
582	582
583	583	=== 3.6.1 Configure ThingsBoard ===
...	...	@@ -716,7 +716,6 @@
716	716
717	717	* (% style="color:#037691" %)**AT+PWD=“Your device token”**
718	718
719		-
720	720	=== 3.7.2 Simulate with MQTT.fx ===
721	721
722	722
...	...	@@ -881,7 +881,6 @@
881	881	1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours.
882	882	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.
883	883
884		-
885	885	== 6.2 Why the uplink JSON format is not standard? ==
886	886
887	887