Summary

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

Details

Page properties

Content

...	...	@@ -55,6 +55,7 @@
55	55
56	56	== 1.2 ​ Features ==
57	57
	58	+
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
...	...	@@ -67,6 +67,7 @@
67	67	* 8500mAh Battery for long term use
68	68
69	69
	71	+
70	70	== 1.3  Specification ==
71	71
72	72
...	...	@@ -93,8 +93,10 @@
93	93	* Max boost current: 2A, 1 second
94	94
95	95
	98	+
96	96	== ​1.4  Applications ==
97	97
	101	+
98	98	* Smart Buildings & Home Automation
99	99	* Logistics and Supply Chain Management
100	100	* Smart Metering
...	...	@@ -108,43 +108,47 @@
108	108
109	109	== 1.5  Pin Definitions & Switch ==
110	110
	115	+
111	111	N95S31B use the mother board from NBSN95 which as below.
112	112
	118	+
113	113	[[image:image-20220709144723-1.png]]
114	114
115	115
116	116	=== 1.5.1 Jumper JP2 ===
117	117
	124	+
118	118	Power on Device when put this jumper.
119	119
120	120
121		-
122	122	=== 1.5.2 BOOT MODE / SW1 ===
123	123
	130	+
124	124	(((
125		-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	+**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.
126	126	)))
127	127
128	128	(((
129		-2) Flash: work mode, device starts to work and send out console output for further debug
	136	+**2) Flash:**  work mode, device starts to work and send out console output for further debug
130	130	)))
131	131
132	132
133		-
134	134	=== 1.5.3 Reset Button ===
135	135
	142	+
136	136	Press to reboot the device.
137	137
138	138
139		-
140	140	=== 1.5.4 LED ===
141	141
	148	+
142	142	It will flash:
143	143
144		-1. When boot the device in flash mode
145		-1. Send an uplink packet
	151	+1.  When boot the device in flash mode
146	146
	153	+2.  Send an uplink packet
147	147
	155	+
148	148	= 2.  Use N95S31B to communicate with IoT Server =
149	149
150	150	== 2.1  How it works ==
...	...	@@ -163,7 +163,7 @@
163	163
164	164	)))
165	165
166		-[[image:1657350248151-650.png]]
	174	+[[image:1657520100595-569.png]]
167	167
168	168	(((
169	169
...	...	@@ -172,7 +172,6 @@
172	172
173	173	== 2.2 ​ Configure the N95S31B ==
174	174
175		-
176	176	=== 2.2.1  Power On N95S31B ===
177	177
178	178
...	...	@@ -179,7 +179,7 @@
179	179	[[image:image-20220709150546-2.png]]
180	180
181	181
182		-=== 2.2.1 Test Requirement ===
	189	+=== 2.2.2 Test Requirement ===
183	183
184	184
185	185	(((
...	...	@@ -228,9 +228,9 @@
228	228	[[image:1657350625843-586.png]]
229	229
230	230
231		-
232	232	=== 2.2.3  Insert SIM card ===
233	233
	240	+
234	234	(((
235	235	Insert the NB-IoT Card get from your provider.
236	236	)))
...	...	@@ -243,26 +243,29 @@
243	243	[[image:1657351240556-536.png]]
244	244
245	245
246		-
247	247	=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
248	248
	255	+
249	249	(((
250	250	(((
251	251	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.
	259	+
	260	+
252	252	)))
253	253	)))
254	254
255	255	[[image:1657351312545-300.png]]
256	256
257		-**Connection:**
258	258
259		- (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
	267	+(% style="color:blue" %)**Connection:**
260	260
261		- (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
	269	+ (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
262	262
263		- (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
	271	+**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
264	264
	273	+**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
265	265
	275	+
266	266	In the PC, use below serial tool settings:
267	267
268	268	* Baud:  (% style="color:green" %)**9600**
...	...	@@ -277,17 +277,18 @@
277	277
278	278	[[image:1657329814315-101.png]]
279	279
	290	+
280	280	(((
281		-(% 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/]]
	292	+(% 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]]**
282	282	)))
283	283
284	284
285		-
286	286	=== 2.2.5  Use CoAP protocol to uplink data ===
287	287
288		-(% 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/]]
289	289
	299	+(% 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/]]**
290	290
	301	+
291	291	(((
292	292	**Use below commands:**
293	293	)))
...	...	@@ -296,10 +296,10 @@
296	296	(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
297	297	)))
298	298	* (((
299		-(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
	310	+(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
300	300	)))
301	301	* (((
302		-(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
	313	+(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
303	303	)))
304	304
305	305	(((
...	...	@@ -318,7 +318,6 @@
318	318	[[image:1657352185396-303.png]]
319	319
320	320
321		-
322	322	=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
323	323
324	324
...	...	@@ -332,18 +332,18 @@
332	332	[[image:1657352403317-397.png]]
333	333
334	334
335		-
336	336	=== 2.2.7  Use MQTT protocol to uplink data ===
337	337
	347	+
338	338	N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
339	339
340		-* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
341		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
342		-* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
343		-* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
344		-* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
345		-* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
346		-* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
	350	+* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
	351	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
	352	+* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
	353	+* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
	354	+* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
	355	+* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
	356	+* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
347	347
348	348	[[image:1657352634421-276.png]]
349	349
...	...	@@ -350,6 +350,7 @@
350	350
351	351	[[image:1657352645687-385.png]]
352	352
	363	+
353	353	(((
354	354	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.
355	355	)))
...	...	@@ -360,9 +360,9 @@
360	360	)))
361	361
362	362
363		-
364	364	=== 2.2.8  Use TCP protocol to uplink data ===
365	365
	376	+
366	366	This feature is supported since firmware version v110
367	367
368	368	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
...	...	@@ -374,9 +374,9 @@
374	374	[[image:1657352914475-252.png]]
375	375
376	376
377		-
378	378	=== 2.2.9  Change Update Interval ===
379	379
	390	+
380	380	User can use below command to change the (% style="color:green" %)**uplink interval**.
381	381
382	382	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
...	...	@@ -385,13 +385,20 @@
385	385
386	386	)))
387	387
	399	+(((
	400	+(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
	401	+)))
388	388
	403	+(((
	404	+(% style="color:red" %)**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).**
	405	+)))
389	389
	407	+
390	390	== 2.3  Uplink Payload ==
391	391
392	392
393	393	(((
394		-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.
	412	+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.
395	395	)))
396	396
397	397
...	...	@@ -400,7 +400,7 @@
400	400	)))
401	401
402	402	(((
403		- (% 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.
	421	+ (% 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.
404	404	)))
405	405
406	406
...	...	@@ -423,23 +423,26 @@
423	423
424	424	(% style="color:red" %)
425	425	1. (((
426		-All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
	444	+**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
427	427	)))
428	428	1. (((
429		-By default, the device will send an uplink message every 1 hour.
430		-)))
	447	+**By default, the device will send an uplink message every 1 hour.**
431	431
432	432
	450	+
	451	+)))
	452	+
433	433	=== 2.3.1  Payload Analyze ===
434	434
	455	+==== 2.3.1.1  Before Firmware v1.2 ====
	456	+
	457	+
435	435	N95S31B uplink payload includes in total 21 bytes
436	436
437	437
438		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
439		-|=(% style="width: 60px;" %)(((
440		-**Size(bytes)**
441		-)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**
442		-|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
	461	+(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
	462	+|=(% style="width: 50px;" %)**Size(bytes)**|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 65px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**2**
	463	+|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:162px" %)(((
443	443	(((
444	444	Reserve/ Same as NBSN95 CFGMOD=1
445	445	)))
...	...	@@ -447,7 +447,7 @@
447	447	(((
448	448	No function here.
449	449	)))
450		-)))|(% style="width:77px" %)(((
	471	+)))|(% style="width:102px" %)(((
451	451	(((
452	452	[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
453	453	)))
...	...	@@ -455,7 +455,7 @@
455	455	(((
456	456	By SHT31
457	457	)))
458		-)))|(% style="width:80px" %)(((
	479	+)))|(% style="width:81px" %)(((
459	459	(((
460	460	[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
461	461	)))
...	...	@@ -466,6 +466,8 @@
466	466	)))
467	467
468	468	(((
	490	+
	491	+
469	469	(((
470	470	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
471	471	)))
...	...	@@ -475,29 +475,90 @@
475	475	[[image:1657354294009-643.png]]
476	476
477	477
478		-The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
	501	+The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
479	479
480		-* Device ID: 0x724031607457 = 724031607457
481		-* Version: 0x006e=110=1.1.0
	503	+**where:**
482	482
483		-* BAT: 0x0ccd = 3277 mV = 3.277V
484		-* Signal: 0x1b = 27
485		-* Model: 0x01 = 1
486		-* 0x00dc000ccc= reserve, ignore in N95S31B
487		-* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
488		-* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
	505	+* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
489	489
	507	+* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
	508	+
	509	+* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
	510	+
	511	+* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
	512	+
	513	+* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
	514	+
	515	+* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
	516	+
	517	+* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
	518	+
	519	+* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
	520	+
490	490	(((
491	491
492		-)))
493	493
494		-(((
	524	+
495	495
496	496	)))
497	497
	528	+==== 2.3.1.2 Since Firmware v1.2 ====
498	498
	530	+
	531	+In this mode, uplink payload includes 91 bytes in total by default.
	532	+
	533	+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.
	534	+
	535	+
	536	+(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
	537	+|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:30px" %)**1**|(% style="width:20px" %)**1**|(% style="width:55px" %)**2**|(% style="width:35px" %)**1**|(% style="width:20px" %)**2**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:30px" %)**4**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:35px" %)**4**
	538	+|=(% style="width: 95px;" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp .....
	539	+
	540	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
	541	+
	542	+
	543	+[[image:image-20220908154949-1.png]]
	544	+
	545	+
	546	+The payload is ASCII string, representative same HEX:
	547	+
	548	+**0x (% style="color:red" %)__f868411056758782__ (% style="color:blue" %)__000c__ (% style="color:green" %)__0d0f__ (% style="color:#00b0f0" %)__0c__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__0000__ (% style="color:#a14d07" %)__00__ __0030__ (% style="color:#0020b0" %)__0114__ (% style="color:#420042" %)__0231__ (% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__// //__0112023763199baa__ __0112023263199af6__// //__0111023b631999a7__ **
	549	+
	550	+**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
	551	+
	552	+**where:**
	553	+
	554	+* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
	555	+
	556	+* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
	557	+
	558	+* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
	559	+
	560	+* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
	561	+
	562	+* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
	563	+
	564	+* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
	565	+
	566	+* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
	567	+
	568	+* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
	569	+
	570	+* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
	571	+
	572	+* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
	573	+
	574	+* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	575	+
	576	+* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
	577	+
	578	+* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
	579	+
	580	+
	581	+
499	499	=== 2.3.2  Device ID ===
500	500
	584	+
501	501	(((
502	502	By default, the Device ID equal to the last 6 bytes of IMEI.
503	503	)))
...	...	@@ -504,10 +504,12 @@
504	504
505	505	(((
506	506	User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	591	+
	592	+
507	507	)))
508	508
509	509	(((
510		-**Example:**
	596	+(% style="color:blue" %)**Example:**
511	511	)))
512	512
513	513	(((
...	...	@@ -515,13 +515,27 @@
515	515	)))
516	516
517	517	(((
518		-The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	604	+The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
	605	+
	606	+
519	519	)))
520	520
	609	+(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
521	521
522	522
	612	+By default, the Device ID equal to the last 15 bits of IMEI.
	613	+
	614	+User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
	615	+
	616	+
	617	+(% style="color:blue" %)**Example:**
	618	+
	619	+AT+DEUI=868411056754138
	620	+
	621	+
523	523	=== 2.3.3  Version Info ===
524	524
	624	+
525	525	(((
526	526	These bytes include the hardware and software version.
527	527	)))
...	...	@@ -546,9 +546,9 @@
546	546
547	547	)))
548	548
549		-
550	550	=== 2.3.4  Battery Info ===
551	551
	651	+
552	552	(((
553	553	Ex1: 0x0B45 = 2885mV
554	554	)))
...	...	@@ -558,9 +558,9 @@
558	558	)))
559	559
560	560
561		-
562	562	=== 2.3.5  Signal Strength ===
563	563
	663	+
564	564	(((
565	565	NB-IoT Network signal Strength.
566	566	)))
...	...	@@ -590,9 +590,9 @@
590	590	)))
591	591
592	592
593		-
594	594	=== 2.3.6  Temperature & Humidity ===
595	595
	695	+
596	596	The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
597	597
598	598	[[image:image-20220709161741-3.png]]
...	...	@@ -608,11 +608,11 @@
608	608	Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
609	609
610	610
611		-
612	612	== 2.4  Downlink Payload ==
613	613
614		-By default, NDDS75 prints the downlink payload to console port.
615	615
	714	+By default, N95S31B prints the downlink payload to console port.
	715	+
616	616	[[image:image-20220709100028-1.png]]
617	617
618	618
...	...	@@ -649,7 +649,7 @@
649	649	)))
650	650
651	651	(((
652		-If payload = 0x04FF, it will reset the NDDS75
	752	+If payload = 0x04FF, it will reset the N95S31B
653	653	)))
654	654
655	655
...	...	@@ -660,12 +660,70 @@
660	660	)))
661	661
662	662
	763	+== 2.5  Humidity and Temperature alarm function ==
663	663
664		-== 2.5  ​Battery Analysis ==
665	665
666		-=== 2.5.1  ​Battery Type ===
	766	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
667	667
668	668
	769	+(% style="color:#037691" %)**AT+ SHHUM=min,max**
	770	+
	771	+
	772	+² When min=0, and max≠0, Alarm higher than max
	773	+
	774	+² When min≠0, and max=0, Alarm lower than min
	775	+
	776	+² When min≠0 and max≠0, Alarm higher than max or lower than min
	777	+
	778	+
	779	+ (% style="color:blue" %)**Example:**
	780	+
	781	+AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
	782	+
	783	+
	784	+(% style="color:#037691" %)**AT+ SHTEMP=min,max**
	785	+
	786	+² When min=0, and max≠0, Alarm higher than max
	787	+
	788	+² When min≠0, and max=0, Alarm lower than min
	789	+
	790	+² When min≠0 and max≠0, Alarm higher than max or lower than min
	791	+
	792	+
	793	+**~ (% style="color:blue" %)Example:(%%)**
	794	+
	795	+AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
	796	+
	797	+
	798	+== 2.6 Set the number of data to be uploaded and the recording time ==
	799	+
	800	+
	801	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
	802	+
	803	+* (% style="color:#037691" %)**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)
	804	+* (% style="color:#037691" %)**AT+NOUD=8**  (%%)~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
	805	+
	806	+ The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
	807	+
	808	+[[image:image-20221009001045-1.png||height="726" width="1009"]]
	809	+
	810	+
	811	+== 2.7 Read or Clear cached data ==
	812	+
	813	+
	814	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
	815	+
	816	+* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
	817	+* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
	818	+
	819	+[[image:image-20220908163102-2.png]]
	820	+
	821	+
	822	+== 2.8  ​Battery Analysis ==
	823	+
	824	+=== 2.8.1  ​Battery Type ===
	825	+
	826	+
669	669	(((
670	670	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.
671	671	)))
...	...	@@ -687,11 +687,11 @@
687	687	)))
688	688
689	689
	848	+=== 2.8.2  Power consumption Analyze ===
690	690
691		-=== 2.5.2  Power consumption Analyze ===
692	692
693	693	(((
694		-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.
	852	+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.
695	695	)))
696	696
697	697	(((
...	...	@@ -698,8 +698,8 @@
698	698
699	699	)))
700	700
	859	+=== 2.8.3  ​Battery Note ===
701	701
702		-=== 2.5.3  ​Battery Note ===
703	703
704	704	(((
705	705	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.
...	...	@@ -706,10 +706,9 @@
706	706	)))
707	707
708	708
	867	+=== 2.8.4  Replace the battery ===
709	709
710		-=== 2.5.4  Replace the battery ===
711	711
712		-
713	713	(((
714	714	You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
715	715	)))
...	...	@@ -720,9 +720,9 @@
720	720	)))
721	721
722	722
723		-
724	724	= 3. ​ Access NB-IoT Module =
725	725
	882	+
726	726	(((
727	727	Users can directly access the AT command set of the NB-IoT module.
728	728	)))
...	...	@@ -729,19 +729,21 @@
729	729
730	730	(((
731	731	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/]]
	889	+
	890	+
732	732	)))
733	733
734	734	[[image:1657333200519-600.png]]
735	735
736	736
737		-
738	738	= 4.  Using the AT Commands =
739	739
740	740	== 4.1  Access AT Commands ==
741	741
742		-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/]]
743	743
	901	+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]]
744	744
	903	+
745	745	AT+<CMD>?  : Help on <CMD>
746	746
747	747	AT+<CMD>         : Run <CMD>
...	...	@@ -781,7 +781,24 @@
781	781
782	782	AT+SERVADDR  : Server Address
783	783
	943	+AT+TR      : Get or Set record time
784	784
	945	+AT+APN     : Get or set the APN
	946	+
	947	+AT+FBAND   : Get or Set whether to automatically modify the frequency band
	948	+
	949	+AT+DNSCFG  : Get or Set DNS Server
	950	+
	951	+AT+GETSENSORVALUE   : Returns the current sensor measurement
	952	+
	953	+AT+NOUD      : Get or Set the number of data to be uploaded
	954	+
	955	+AT+CDP     : Read or Clear cached data
	956	+
	957	+AT+SHTEMP: Get or Set alarm of temp
	958	+
	959	+AT+SHHUM: Get or Set alarm of moisture
	960	+
785	785	(% style="color:#037691" %)**COAP Management**
786	786
787	787	AT+URI            : Resource parameters
...	...	@@ -812,7 +812,6 @@
812	812	AT+PWORD  : Serial Access Password
813	813
814	814
815		-
816	816	= ​5.  FAQ =
817	817
818	818	== 5.1 ​ How to Upgrade Firmware ==
...	...	@@ -830,12 +830,11 @@
830	830
831	831
832	832	(((
833		-(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
	1008	+(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
834	834	)))
835	835	)))
836	836
837	837
838		-
839	839	= 6.  Trouble Shooting =
840	840
841	841	== 6.1  ​Connection problem when uploading firmware ==
...	...	@@ -850,9 +850,9 @@
850	850
851	851	)))
852	852
853		-
854	854	== 6.2  AT Command input doesn't work ==
855	855
	1029	+
856	856	(((
857	857	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.
858	858
...	...	@@ -859,7 +859,6 @@
859	859
860	860	)))
861	861
862		-
863	863	= 7. ​ Order Info =
864	864
865	865
...	...	@@ -866,11 +866,6 @@
866	866	Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
867	867
868	868
869		-(% class="wikigeneratedid" %)
870		-(((
871		-
872		-)))
873		-
874	874	= 8.  Packing Info =
875	875
876	876	(((
...	...	@@ -896,11 +896,16 @@
896	896	(((
897	897
898	898
899		-
900	900
901	901	)))
902	902
903	903	= 9.  Support =
904	904
	1072	+
905	905	* 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.
906	906	* 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]]
	1075	+
	1076	+
	1077	+
	1078	+
	1079	+

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

image-20221009001045-1.png

Author

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

Size

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

Content