Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 3 added, 0 removed)
  • 1657520100595-569.png
  • image-20220908154949-1.png
  • image-20220908163102-2.png

Details

Page properties

Author

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

Content

...	...	@@ -17,6 +17,7 @@
17	17
18	18	= 1.  Introduction =
19	19
	20	+
20	20	== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
21	21
22	22	(((
...	...	@@ -55,6 +55,7 @@
55	55
56	56	== 1.2 ​ Features ==
57	57
	59	+
58	58	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
59	59	* Monitor Temperature & Humidity via SHT31
60	60	* AT Commands to change parameters
...	...	@@ -66,9 +66,6 @@
66	66	* Micro SIM card slot for NB-IoT SIM
67	67	* 8500mAh Battery for long term use
68	68
69		-
70		-
71		-
72	72	== 1.3  Specification ==
73	73
74	74
...	...	@@ -77,7 +77,6 @@
77	77	* Supply Voltage: 2.1v ~~ 3.6v
78	78	* Operating Temperature: -40 ~~ 85°C
79	79
80		-
81	81	(% style="color:#037691" %)**NB-IoT Spec:**
82	82
83	83	* - B1 @H-FDD: 2100MHz
...	...	@@ -87,7 +87,6 @@
87	87	* - B20 @H-FDD: 800MHz
88	88	* - B28 @H-FDD: 700MHz
89	89
90		-
91	91	(% style="color:#037691" %)**Battery:**
92	92
93	93	* Li/SOCI2 un-chargeable battery
...	...	@@ -96,11 +96,9 @@
96	96	* Max continuously current: 130mA
97	97	* Max boost current: 2A, 1 second
98	98
99		-
100		-
101		-
102	102	== ​1.4  Applications ==
103	103
	98	+
104	104	* Smart Buildings & Home Automation
105	105	* Logistics and Supply Chain Management
106	106	* Smart Metering
...	...	@@ -112,15 +112,20 @@
112	112	​
113	113
114	114
115		-== 1.5  Pin Definitions ==
116	116
	111	+== 1.5  Pin Definitions & Switch ==
	112	+
	113	+
117	117	N95S31B use the mother board from NBSN95 which as below.
118	118
	116	+
119	119	[[image:image-20220709144723-1.png]]
120	120
121	121
	120	+
122	122	=== 1.5.1 Jumper JP2 ===
123	123
	123	+
124	124	Power on Device when put this jumper.
125	125
126	126
...	...	@@ -127,6 +127,7 @@
127	127
128	128	=== 1.5.2 BOOT MODE / SW1 ===
129	129
	130	+
130	130	(((
131	131	1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
132	132	)))
...	...	@@ -139,6 +139,7 @@
139	139
140	140	=== 1.5.3 Reset Button ===
141	141
	143	+
142	142	Press to reboot the device.
143	143
144	144
...	...	@@ -145,6 +145,7 @@
145	145
146	146	=== 1.5.4 LED ===
147	147
	150	+
148	148	It will flash:
149	149
150	150	1. When boot the device in flash mode
...	...	@@ -152,6 +152,7 @@
152	152
153	153	= 2.  Use N95S31B to communicate with IoT Server =
154	154
	158	+
155	155	== 2.1  How it works ==
156	156
157	157
...	...	@@ -168,7 +168,7 @@
168	168
169	169	)))
170	170
171		-[[image:1657350248151-650.png]]
	175	+[[image:1657520100595-569.png]]
172	172
173	173	(((
174	174
...	...	@@ -184,26 +184,49 @@
184	184	[[image:image-20220709150546-2.png]]
185	185
186	186
	191	+
187	187	=== 2.2.1 Test Requirement ===
188	188
189	189
	195	+(((
190	190	To use N95S31B in your city, make sure meet below requirements:
	197	+)))
191	191
192		-* Your local operator has already distributed a NB-IoT Network there.
193		-* The local NB-IoT network used the band that N95S31B supports.
194		-* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	199	+* (((
	200	+Your local operator has already distributed a NB-IoT Network there.
	201	+)))
	202	+* (((
	203	+The local NB-IoT network used the band that N95S31B supports.
	204	+)))
	205	+* (((
	206	+Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	207	+)))
195	195
	209	+(((
196	196	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
	211	+)))
197	197
	213	+(((
198	198	N95S31B supports different communication protocol such as :
	215	+)))
199	199
200	200	(((
201		-* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
202		-* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
203		-* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
204		-* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	218	+* (((
	219	+CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
	220	+)))
	221	+* (((
	222	+raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
	223	+)))
	224	+* (((
	225	+MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
	226	+)))
	227	+* (((
	228	+TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	229	+)))
205	205
	231	+(((
206	206	We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server.
	233	+)))
207	207
208	208
209	209	)))
...	...	@@ -214,6 +214,7 @@
214	214
215	215	=== 2.2.3  Insert SIM card ===
216	216
	244	+
217	217	(((
218	218	Insert the NB-IoT Card get from your provider.
219	219	)))
...	...	@@ -229,14 +229,18 @@
229	229
230	230	=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
231	231
	260	+
232	232	(((
233	233	(((
234	234	User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below.
	264	+
	265	+
235	235	)))
236	236	)))
237	237
238	238	[[image:1657351312545-300.png]]
239	239
	271	+
240	240	**Connection:**
241	241
242	242	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
...	...	@@ -260,8 +260,9 @@
260	260
261	261	[[image:1657329814315-101.png]]
262	262
	295	+
263	263	(((
264		-(% style="color:red" %)Note: the valid AT Commands can be found at:  (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]
	297	+(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**
265	265	)))
266	266
267	267
...	...	@@ -268,9 +268,10 @@
268	268
269	269	=== 2.2.5  Use CoAP protocol to uplink data ===
270	270
271		-(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
272	272
	305	+(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**
273	273
	307	+
274	274	(((
275	275	**Use below commands:**
276	276	)))
...	...	@@ -318,6 +318,7 @@
318	318
319	319	=== 2.2.7  Use MQTT protocol to uplink data ===
320	320
	355	+
321	321	N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
322	322
323	323	* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
...	...	@@ -333,6 +333,7 @@
333	333
334	334	[[image:1657352645687-385.png]]
335	335
	371	+
336	336	(((
337	337	To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period.
338	338	)))
...	...	@@ -346,6 +346,7 @@
346	346
347	347	=== 2.2.8  Use TCP protocol to uplink data ===
348	348
	385	+
349	349	This feature is supported since firmware version v110
350	350
351	351	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
...	...	@@ -360,6 +360,7 @@
360	360
361	361	=== 2.2.9  Change Update Interval ===
362	362
	400	+
363	363	User can use below command to change the (% style="color:green" %)**uplink interval**.
364	364
365	365	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
...	...	@@ -368,35 +368,62 @@
368	368
369	369	)))
370	370
	409	+(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
371	371
	411	+**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
372	372
	413	+
373	373	== 2.3  Uplink Payload ==
374	374
375	375
376		-NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
	417	+(((
	418	+N95S31B has different working modes for the connections of different types of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
	419	+)))
377	377
378	378
	422	+(((
379	379	For example:
	424	+)))
380	380
381		- (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
	426	+(((
	427	+ (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
	428	+)))
382	382
383	383
	431	+(((
384	384	The uplink payloads are composed in  ASCII String. For example:
	433	+)))
385	385
	435	+(((
386	386	0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
	437	+)))
387	387
	439	+(((
388	388	0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
	441	+)))
389	389
390	390
	444	+(((
391	391	(% style="color:red" %)**NOTE:**
	446	+)))
392	392
393	393	(% style="color:red" %)
394		-1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
395		-1. By default, the device will send an uplink message every 1 hour.
	449	+1. (((
	450	+**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
	451	+)))
	452	+1. (((
	453	+**By default, the device will send an uplink message every 1 hour.**
396	396
397	397
	456	+
	457	+
	458	+)))
	459	+
398	398	=== 2.3.1  Payload Analyze ===
399	399
	462	+
	463	+==== 2.3.1.1 Before Firmware v1.2 ====
	464	+
400	400	N95S31B uplink payload includes in total 21 bytes
401	401
402	402
...	...	@@ -431,6 +431,8 @@
431	431	)))
432	432
433	433	(((
	499	+
	500	+
434	434	(((
435	435	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
436	436	)))
...	...	@@ -456,13 +456,40 @@
456	456
457	457	)))
458	458
459		-(((
460		-
461		-)))
	526	+==== 2.3.1.2 Since Firmware v1.2 ====
462	462
	528	+In this mode, uplink payload includes 91 bytes in total by default.
463	463
	530	+Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
	531	+
	532	+|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4
	533	+|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp .....
	534	+
	535	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
	536	+
	537	+[[image:image-20220908154949-1.png]]
	538	+
	539	+The payload is ASCII string, representative same HEX:
	540	+
	541	+0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where:
	542	+
	543	+* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782
	544	+* (% style="color:blue" %) Version: 0x000c=120=1.2
	545	+* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V
	546	+* (% style="color:red" %) Singal: 0x0c = 12
	547	+* (% style="color:blue" %) Mod: 0x01 = 1
	548	+* TemDS18B20: 0x0000= 0 = 0
	549	+* (% style="color:green" %)Interrupt: 0x00= 0
	550	+* (% style="color:green" %)adc: 0x0030= 48
	551	+* SHTTEM: 0x0114= 276 = 27.6
	552	+* SHTHUM:0x0231 =561=56.1%
	553	+* (% style="color:red" %) Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	554	+* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
	555	+* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,.......
	556	+
464	464	=== 2.3.2  Device ID ===
465	465
	559	+
466	466	(((
467	467	By default, the Device ID equal to the last 6 bytes of IMEI.
468	468	)))
...	...	@@ -481,21 +481,44 @@
481	481
482	482	(((
483	483	The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	578	+
	579	+
484	484	)))
485	485
	582	+(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
486	486
487	487
	585	+By default, the Device ID equal to the last 15 bits of IMEI.
	586	+
	587	+User can use **AT+DEUI** to set Device ID
	588	+
	589	+**Example:**
	590	+
	591	+AT+DEUI=868411056754138
	592	+
	593	+
488	488	=== 2.3.3  Version Info ===
489	489
490	490
	597	+(((
491	491	These bytes include the hardware and software version.
	599	+)))
492	492
	601	+(((
493	493	Higher byte: Specify hardware version: always 0x00 for N95S31B
	603	+)))
494	494
	605	+(((
495	495	Lower byte: Specify the software version: 0x6E=110, means firmware version 110
	607	+)))
496	496
	609	+(((
	610	+
	611	+)))
497	497
	613	+(((
498	498	For example: 0x00 6E: this device is N95S31B with firmware version 110.
	615	+)))
499	499
500	500	(((
501	501
...	...	@@ -504,6 +504,7 @@
504	504
505	505	=== 2.3.4  Battery Info ===
506	506
	624	+
507	507	(((
508	508	Ex1: 0x0B45 = 2885mV
509	509	)))
...	...	@@ -516,6 +516,7 @@
516	516
517	517	=== 2.3.5  Signal Strength ===
518	518
	637	+
519	519	(((
520	520	NB-IoT Network signal Strength.
521	521	)))
...	...	@@ -548,6 +548,7 @@
548	548
549	549	=== 2.3.6  Temperature & Humidity ===
550	550
	670	+
551	551	The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
552	552
553	553	[[image:image-20220709161741-3.png]]
...	...	@@ -566,8 +566,9 @@
566	566
567	567	== 2.4  Downlink Payload ==
568	568
569		-By default, NDDS75 prints the downlink payload to console port.
570	570
	690	+By default, N95S31B prints the downlink payload to console port.
	691	+
571	571	[[image:image-20220709100028-1.png]]
572	572
573	573
...	...	@@ -604,7 +604,7 @@
604	604	)))
605	605
606	606	(((
607		-If payload = 0x04FF, it will reset the NDDS75
	728	+If payload = 0x04FF, it will reset the N95S31B
608	608	)))
609	609
610	610
...	...	@@ -615,12 +615,59 @@
615	615	)))
616	616
617	617
	739	+== 2.5 Humidity and Temperature alarm function ==
618	618
619		-== 2.5  ​Battery Analysis ==
	741	+➢ AT Command:
620	620
621		-=== 2.5.1  ​Battery Type ===
	743	+AT+ SHHUM=min,max
622	622
	745	+² When min=0, and max≠0, Alarm higher than max
623	623
	747	+² When min≠0, and max=0, Alarm lower than min
	748	+
	749	+² When min≠0 and max≠0, Alarm higher than max or lower than min
	750	+
	751	+Example:
	752	+
	753	+AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
	754	+
	755	+
	756	+AT+ SHTEMP=min,max
	757	+
	758	+² When min=0, and max≠0, Alarm higher than max
	759	+
	760	+² When min≠0, and max=0, Alarm lower than min
	761	+
	762	+² When min≠0 and max≠0, Alarm higher than max or lower than min
	763	+
	764	+Example:
	765	+
	766	+AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
	767	+
	768	+== 2.6 Set the number of data to be uploaded and the recording time ==
	769	+
	770	+➢ AT Command:
	771	+
	772	+AT+TR=900  ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
	773	+
	774	+AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
	775	+
	776	+== 2.7 Read or Clear cached data ==
	777	+
	778	+➢ AT Command:
	779	+
	780	+AT+CDP ~/~/ Read cached data
	781	+
	782	+[[image:image-20220908163102-2.png]]
	783	+
	784	+AT+CDP=0 ~/~/ Clear cached data
	785	+
	786	+== 2.8  ​Battery Analysis ==
	787	+
	788	+
	789	+=== 2.8.1  ​Battery Type ===
	790	+
	791	+
624	624	(((
625	625	The N95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
626	626	)))
...	...	@@ -643,10 +643,11 @@
643	643
644	644
645	645
646		-=== 2.5.2  Power consumption Analyze ===
	814	+=== 2.8.2  Power consumption Analyze ===
647	647
	816	+
648	648	(((
649		-The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
	818	+The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
650	650	)))
651	651
652	652	(((
...	...	@@ -654,8 +654,9 @@
654	654	)))
655	655
656	656
657		-=== 2.5.3  ​Battery Note ===
	826	+=== 2.8.3  ​Battery Note ===
658	658
	828	+
659	659	(((
660	660	The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to uplink data, then the battery life may be decreased.
661	661	)))
...	...	@@ -662,7 +662,7 @@
662	662
663	663
664	664
665		-=== 2.5.4  Replace the battery ===
	835	+=== 2.8.4  Replace the battery ===
666	666
667	667
668	668	(((
...	...	@@ -678,6 +678,7 @@
678	678
679	679	= 3. ​ Access NB-IoT Module =
680	680
	851	+
681	681	(((
682	682	Users can directly access the AT command set of the NB-IoT module.
683	683	)))
...	...	@@ -684,6 +684,8 @@
684	684
685	685	(((
686	686	The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]]
	858	+
	859	+
687	687	)))
688	688
689	689	[[image:1657333200519-600.png]]
...	...	@@ -692,11 +692,13 @@
692	692
693	693	= 4.  Using the AT Commands =
694	694
	868	+
695	695	== 4.1  Access AT Commands ==
696	696
697		-See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]
698	698
	872	+See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]]
699	699
	874	+
700	700	AT+<CMD>?  : Help on <CMD>
701	701
702	702	AT+<CMD>         : Run <CMD>
...	...	@@ -736,7 +736,24 @@
736	736
737	737	AT+SERVADDR  : Server Address
738	738
	914	+AT+TR      : Get or Set record time
739	739
	916	+AT+APN     : Get or set the APN
	917	+
	918	+AT+FBAND   : Get or Set whether to automatically modify the frequency band
	919	+
	920	+AT+DNSCFG  : Get or Set DNS Server
	921	+
	922	+AT+GETSENSORVALUE   : Returns the current sensor measurement
	923	+
	924	+AT+NOUD      : Get or Set the number of data to be uploaded
	925	+
	926	+AT+CDP     : Read or Clear cached data
	927	+
	928	+AT+SHTEMP: Get or Set alarm of temp
	929	+
	930	+AT+SHHUM: Get or Set alarm of moisture
	931	+
740	740	(% style="color:#037691" %)**COAP Management**
741	741
742	742	AT+URI            : Resource parameters
...	...	@@ -770,6 +770,7 @@
770	770
771	771	= ​5.  FAQ =
772	772
	965	+
773	773	== 5.1 ​ How to Upgrade Firmware ==
774	774
775	775
...	...	@@ -784,13 +784,16 @@
784	784	(((
785	785
786	786
787		-(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
	980	+(((
	981	+(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
788	788	)))
	983	+)))
789	789
790	790
791	791
792	792	= 6.  Trouble Shooting =
793	793
	989	+
794	794	== 6.1  ​Connection problem when uploading firmware ==
795	795
796	796
...	...	@@ -806,6 +806,7 @@
806	806
807	807	== 6.2  AT Command input doesn't work ==
808	808
	1005	+
809	809	(((
810	810	In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
811	811
...	...	@@ -855,5 +855,6 @@
855	855
856	856	= 9.  Support =
857	857
	1055	+
858	858	* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
859	859	* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]

1657520100595-569.png

Author

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

Size

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

Content

image-20220908154949-1.png

Author

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

Size

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

Content

image-20220908163102-2.png

Author

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

Size

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

Content