Summary

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

Details

Page properties

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
...	...	@@ -67,8 +67,6 @@
67	67	* 8500mAh Battery for long term use
68	68
69	69
70		-
71		-
72	72	== 1.3  Specification ==
73	73
74	74
...	...	@@ -88,7 +88,6 @@
88	88
89	89	(% style="color:#037691" %)**Battery:**
90	90
91		-
92	92	* Li/SOCI2 un-chargeable battery
93	93	* Capacity: 8500mAh
94	94	* Self Discharge: <1% / Year @ 25°C
...	...	@@ -95,8 +95,10 @@
95	95	* Max continuously current: 130mA
96	96	* Max boost current: 2A, 1 second
97	97
	97	+
98	98	== ​1.4  Applications ==
99	99
	100	+
100	100	* Smart Buildings & Home Automation
101	101	* Logistics and Supply Chain Management
102	102	* Smart Metering
...	...	@@ -108,15 +108,20 @@
108	108	​
109	109
110	110
111		-== 1.5  Pin Definitions ==
112	112
	113	+== 1.5  Pin Definitions & Switch ==
	114	+
	115	+
113	113	N95S31B use the mother board from NBSN95 which as below.
114	114
	118	+
115	115	[[image:image-20220709144723-1.png]]
116	116
117	117
	122	+
118	118	=== 1.5.1 Jumper JP2 ===
119	119
	125	+
120	120	Power on Device when put this jumper.
121	121
122	122
...	...	@@ -123,14 +123,20 @@
123	123
124	124	=== 1.5.2 BOOT MODE / SW1 ===
125	125
126		-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.
127	127
128		-2) Flash: work mode, device starts to work and send out console output for further debug
	133	+(((
	134	+**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.
	135	+)))
129	129
	137	+(((
	138	+**2) Flash:**  work mode, device starts to work and send out console output for further debug
	139	+)))
130	130
131	131
	142	+
132	132	=== 1.5.3 Reset Button ===
133	133
	145	+
134	134	Press to reboot the device.
135	135
136	136
...	...	@@ -137,13 +137,18 @@
137	137
138	138	=== 1.5.4 LED ===
139	139
	152	+
140	140	It will flash:
141	141
142		-1. When boot the device in flash mode
143		-1. Send an uplink packet
	155	+1.  When boot the device in flash mode
144	144
	157	+2.  Send an uplink packet
	158	+
	159	+
	160	+
145	145	= 2.  Use N95S31B to communicate with IoT Server =
146	146
	163	+
147	147	== 2.1  How it works ==
148	148
149	149
...	...	@@ -160,7 +160,7 @@
160	160
161	161	)))
162	162
163		-[[image:1657350248151-650.png]]
	180	+[[image:1657520100595-569.png]]
164	164
165	165	(((
166	166
...	...	@@ -176,26 +176,49 @@
176	176	[[image:image-20220709150546-2.png]]
177	177
178	178
	196	+
179	179	=== 2.2.1 Test Requirement ===
180	180
181	181
	200	+(((
182	182	To use N95S31B in your city, make sure meet below requirements:
	202	+)))
183	183
184		-* Your local operator has already distributed a NB-IoT Network there.
185		-* The local NB-IoT network used the band that N95S31B supports.
186		-* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	204	+* (((
	205	+Your local operator has already distributed a NB-IoT Network there.
	206	+)))
	207	+* (((
	208	+The local NB-IoT network used the band that N95S31B supports.
	209	+)))
	210	+* (((
	211	+Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	212	+)))
187	187
	214	+(((
188	188	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
	216	+)))
189	189
	218	+(((
190	190	N95S31B supports different communication protocol such as :
	220	+)))
191	191
192	192	(((
193		-* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
194		-* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
195		-* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
196		-* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	223	+* (((
	224	+CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
	225	+)))
	226	+* (((
	227	+raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
	228	+)))
	229	+* (((
	230	+MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
	231	+)))
	232	+* (((
	233	+TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	234	+)))
197	197
	236	+(((
198	198	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.
	238	+)))
199	199
200	200
201	201	)))
...	...	@@ -206,6 +206,7 @@
206	206
207	207	=== 2.2.3  Insert SIM card ===
208	208
	249	+
209	209	(((
210	210	Insert the NB-IoT Card get from your provider.
211	211	)))
...	...	@@ -221,23 +221,27 @@
221	221
222	222	=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
223	223
	265	+
224	224	(((
225	225	(((
226	226	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.
	269	+
	270	+
227	227	)))
228	228	)))
229	229
230	230	[[image:1657351312545-300.png]]
231	231
232		-**Connection:**
233	233
234		- (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
	277	+**(% style="color:blue" %)Connection:**
235	235
236		- (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
	279	+ (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
237	237
238		- (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
	281	+**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
239	239
	283	+**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
240	240
	285	+
241	241	In the PC, use below serial tool settings:
242	242
243	243	* Baud:  (% style="color:green" %)**9600**
...	...	@@ -252,8 +252,9 @@
252	252
253	253	[[image:1657329814315-101.png]]
254	254
	300	+
255	255	(((
256		-(% 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/]]
	302	+(% 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]]**
257	257	)))
258	258
259	259
...	...	@@ -260,9 +260,10 @@
260	260
261	261	=== 2.2.5  Use CoAP protocol to uplink data ===
262	262
263		-(% 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/]]
264	264
	310	+(% 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/]]**
265	265
	312	+
266	266	(((
267	267	**Use below commands:**
268	268	)))
...	...	@@ -271,10 +271,10 @@
271	271	(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
272	272	)))
273	273	* (((
274		-(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
	321	+(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
275	275	)))
276	276	* (((
277		-(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
	324	+(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
278	278	)))
279	279
280	280	(((
...	...	@@ -310,15 +310,16 @@
310	310
311	311	=== 2.2.7  Use MQTT protocol to uplink data ===
312	312
	360	+
313	313	N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
314	314
315		-* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
316		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
317		-* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
318		-* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
319		-* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
320		-* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
321		-* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
	363	+* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
	364	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
	365	+* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
	366	+* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
	367	+* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
	368	+* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
	369	+* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
322	322
323	323	[[image:1657352634421-276.png]]
324	324
...	...	@@ -325,6 +325,7 @@
325	325
326	326	[[image:1657352645687-385.png]]
327	327
	376	+
328	328	(((
329	329	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.
330	330	)))
...	...	@@ -338,6 +338,7 @@
338	338
339	339	=== 2.2.8  Use TCP protocol to uplink data ===
340	340
	390	+
341	341	This feature is supported since firmware version v110
342	342
343	343	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
...	...	@@ -352,6 +352,7 @@
352	352
353	353	=== 2.2.9  Change Update Interval ===
354	354
	405	+
355	355	User can use below command to change the (% style="color:green" %)**uplink interval**.
356	356
357	357	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
...	...	@@ -360,43 +360,76 @@
360	360
361	361	)))
362	362
	414	+(((
	415	+(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
	416	+)))
363	363
	418	+(((
	419	+(% 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).**
	420	+)))
364	364
	422	+
	423	+
365	365	== 2.3  Uplink Payload ==
366	366
367	367
368		-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.
	427	+(((
	428	+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.
	429	+)))
369	369
370	370
	432	+(((
371	371	For example:
	434	+)))
372	372
373		- (% 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.
	436	+(((
	437	+ (% 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.
	438	+)))
374	374
375	375
	441	+(((
376	376	The uplink payloads are composed in  ASCII String. For example:
	443	+)))
377	377
	445	+(((
378	378	0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
	447	+)))
379	379
	449	+(((
380	380	0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
	451	+)))
381	381
382	382
	454	+(((
383	383	(% style="color:red" %)**NOTE:**
	456	+)))
384	384
385	385	(% style="color:red" %)
386		-1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
387		-1. By default, the device will send an uplink message every 1 hour.
	459	+1. (((
	460	+**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
	461	+)))
	462	+1. (((
	463	+**By default, the device will send an uplink message every 1 hour.**
388	388
389	389
	466	+
	467	+
	468	+)))
	469	+
390	390	=== 2.3.1  Payload Analyze ===
391	391
	472	+
	473	+==== 2.3.1.1  Before Firmware v1.2 ====
	474	+
	475	+
392	392	N95S31B uplink payload includes in total 21 bytes
393	393
394	394
395		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
396		-|=(% style="width: 60px;" %)(((
	479	+(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
	480	+|=(% style="width: 50px;" %)(((
397	397	**Size(bytes)**
398		-)))|=(% 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**
399		-|(% 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" %)(((
	482	+)))|=(% style="width: 40px;" %)**6**|=(% style="width: 20px;" %)2|=(% style="width: 20px;" %)**2**|=(% style="width: 60px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 100px;" %)5|=(% style="width: 102px;" %)**2**|=(% style="width: 81px;" %)**2**
	483	+|(% 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" %)(((
400	400	(((
401	401	Reserve/ Same as NBSN95 CFGMOD=1
402	402	)))
...	...	@@ -404,7 +404,7 @@
404	404	(((
405	405	No function here.
406	406	)))
407		-)))|(% style="width:77px" %)(((
	491	+)))|(% style="width:102px" %)(((
408	408	(((
409	409	[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
410	410	)))
...	...	@@ -412,7 +412,7 @@
412	412	(((
413	413	By SHT31
414	414	)))
415		-)))|(% style="width:80px" %)(((
	499	+)))|(% style="width:81px" %)(((
416	416	(((
417	417	[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
418	418	)))
...	...	@@ -423,6 +423,8 @@
423	423	)))
424	424
425	425	(((
	510	+
	511	+
426	426	(((
427	427	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
428	428	)))
...	...	@@ -432,29 +432,89 @@
432	432	[[image:1657354294009-643.png]]
433	433
434	434
435		-The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
	521	+The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
436	436
437		-* Device ID: 0x724031607457 = 724031607457
438		-* Version: 0x006e=110=1.1.0
	523	+**where:**
439	439
440		-* BAT: 0x0ccd = 3277 mV = 3.277V
441		-* Signal: 0x1b = 27
442		-* Model: 0x01 = 1
443		-* 0x00dc000ccc= reserve, ignore in N95S31B
444		-* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
445		-* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
	525	+* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
446	446
	527	+* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
	528	+
	529	+* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
	530	+
	531	+* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
	532	+
	533	+* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
	534	+
	535	+* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
	536	+
	537	+* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
	538	+
	539	+* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
	540	+
447	447	(((
448	448
449		-)))
450	450
451		-(((
	544	+
452	452
453	453	)))
454	454
	548	+==== 2.3.1.2 Since Firmware v1.2 ====
455	455
	550	+
	551	+In this mode, uplink payload includes 91 bytes in total by default.
	552	+
	553	+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.
	554	+
	555	+
	556	+(% border="2" style="background-color:#ffffcc; color:green; width:520px" %)
	557	+|(% style="width:50px" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**2**|(% style="width:50px" %)**1**|(% style="width:30px" %)**2**|(% style="width:50px" %)**2**|(% style="width:50px" %)**2**|(% style="width:50px" %)**4**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:50px" %)**4**
	558	+|(% 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 .....
	559	+
	560	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
	561	+
	562	+
	563	+[[image:image-20220908154949-1.png]]
	564	+
	565	+
	566	+The payload is ASCII string, representative same HEX:
	567	+
	568	+**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__ **
	569	+
	570	+**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
	571	+
	572	+**where:**
	573	+
	574	+* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
	575	+
	576	+* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
	577	+
	578	+* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
	579	+
	580	+* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
	581	+
	582	+* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
	583	+
	584	+* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
	585	+
	586	+* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
	587	+
	588	+* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
	589	+
	590	+* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
	591	+
	592	+* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
	593	+
	594	+* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	595	+
	596	+* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
	597	+
	598	+* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
	599	+
	600	+
456	456	=== 2.3.2  Device ID ===
457	457
	603	+
458	458	(((
459	459	By default, the Device ID equal to the last 6 bytes of IMEI.
460	460	)))
...	...	@@ -461,10 +461,12 @@
461	461
462	462	(((
463	463	User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	610	+
	611	+
464	464	)))
465	465
466	466	(((
467		-**Example:**
	615	+(% style="color:blue" %)**Example:**
468	468	)))
469	469
470	470	(((
...	...	@@ -472,22 +472,47 @@
472	472	)))
473	473
474	474	(((
475		-The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	623	+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.
	624	+
	625	+
476	476	)))
477	477
	628	+(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
478	478
479	479
	631	+By default, the Device ID equal to the last 15 bits of IMEI.
	632	+
	633	+User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
	634	+
	635	+
	636	+(% style="color:blue" %)**Example:**
	637	+
	638	+AT+DEUI=868411056754138
	639	+
	640	+
	641	+
480	480	=== 2.3.3  Version Info ===
481	481
482	482
	645	+(((
483	483	These bytes include the hardware and software version.
	647	+)))
484	484
	649	+(((
485	485	Higher byte: Specify hardware version: always 0x00 for N95S31B
	651	+)))
486	486
	653	+(((
487	487	Lower byte: Specify the software version: 0x6E=110, means firmware version 110
	655	+)))
488	488
	657	+(((
	658	+
	659	+)))
489	489
	661	+(((
490	490	For example: 0x00 6E: this device is N95S31B with firmware version 110.
	663	+)))
491	491
492	492	(((
493	493
...	...	@@ -496,6 +496,7 @@
496	496
497	497	=== 2.3.4  Battery Info ===
498	498
	672	+
499	499	(((
500	500	Ex1: 0x0B45 = 2885mV
501	501	)))
...	...	@@ -508,6 +508,7 @@
508	508
509	509	=== 2.3.5  Signal Strength ===
510	510
	685	+
511	511	(((
512	512	NB-IoT Network signal Strength.
513	513	)))
...	...	@@ -540,6 +540,7 @@
540	540
541	541	=== 2.3.6  Temperature & Humidity ===
542	542
	718	+
543	543	The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
544	544
545	545	[[image:image-20220709161741-3.png]]
...	...	@@ -558,8 +558,9 @@
558	558
559	559	== 2.4  Downlink Payload ==
560	560
561		-By default, NDDS75 prints the downlink payload to console port.
562	562
	738	+By default, N95S31B prints the downlink payload to console port.
	739	+
563	563	[[image:image-20220709100028-1.png]]
564	564
565	565
...	...	@@ -596,7 +596,7 @@
596	596	)))
597	597
598	598	(((
599		-If payload = 0x04FF, it will reset the NDDS75
	776	+If payload = 0x04FF, it will reset the N95S31B
600	600	)))
601	601
602	602
...	...	@@ -608,11 +608,74 @@
608	608
609	609
610	610
611		-== 2.5  ​Battery Analysis ==
	788	+== 2.5  Humidity and Temperature alarm function ==
612	612
613		-=== 2.5.1  ​Battery Type ===
614	614
	791	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
615	615
	793	+
	794	+(% style="color:#037691" %)**AT+ SHHUM=min,max**
	795	+
	796	+
	797	+² When min=0, and max≠0, Alarm higher than max
	798	+
	799	+² When min≠0, and max=0, Alarm lower than min
	800	+
	801	+² When min≠0 and max≠0, Alarm higher than max or lower than min
	802	+
	803	+
	804	+ (% style="color:blue" %)**Example:**
	805	+
	806	+AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
	807	+
	808	+
	809	+(% style="color:#037691" %)**AT+ SHTEMP=min,max**
	810	+
	811	+² When min=0, and max≠0, Alarm higher than max
	812	+
	813	+² When min≠0, and max=0, Alarm lower than min
	814	+
	815	+² When min≠0 and max≠0, Alarm higher than max or lower than min
	816	+
	817	+
	818	+**~ (% style="color:blue" %)Example:(%%)**
	819	+
	820	+AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
	821	+
	822	+
	823	+
	824	+== 2.6 Set the number of data to be uploaded and the recording time ==
	825	+
	826	+
	827	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
	828	+
	829	+* (% 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)
	830	+* (% 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.
	831	+
	832	+ The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
	833	+
	834	+[[image:image-20221009001045-1.png||height="726" width="1009"]]
	835	+
	836	+
	837	+
	838	+== 2.7 Read or Clear cached data ==
	839	+
	840	+
	841	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
	842	+
	843	+* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
	844	+* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
	845	+
	846	+[[image:image-20220908163102-2.png]]
	847	+
	848	+
	849	+
	850	+== 2.8  ​Battery Analysis ==
	851	+
	852	+
	853	+=== 2.8.1  ​Battery Type ===
	854	+
	855	+
616	616	(((
617	617	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.
618	618	)))
...	...	@@ -635,10 +635,11 @@
635	635
636	636
637	637
638		-=== 2.5.2  Power consumption Analyze ===
	878	+=== 2.8.2  Power consumption Analyze ===
639	639
	880	+
640	640	(((
641		-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.
	882	+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.
642	642	)))
643	643
644	644	(((
...	...	@@ -646,8 +646,9 @@
646	646	)))
647	647
648	648
649		-=== 2.5.3  ​Battery Note ===
	890	+=== 2.8.3  ​Battery Note ===
650	650
	892	+
651	651	(((
652	652	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.
653	653	)))
...	...	@@ -654,7 +654,7 @@
654	654
655	655
656	656
657		-=== 2.5.4  Replace the battery ===
	899	+=== 2.8.4  Replace the battery ===
658	658
659	659
660	660	(((
...	...	@@ -670,6 +670,7 @@
670	670
671	671	= 3. ​ Access NB-IoT Module =
672	672
	915	+
673	673	(((
674	674	Users can directly access the AT command set of the NB-IoT module.
675	675	)))
...	...	@@ -676,6 +676,8 @@
676	676
677	677	(((
678	678	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/]]
	922	+
	923	+
679	679	)))
680	680
681	681	[[image:1657333200519-600.png]]
...	...	@@ -684,11 +684,13 @@
684	684
685	685	= 4.  Using the AT Commands =
686	686
	932	+
687	687	== 4.1  Access AT Commands ==
688	688
689		-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/]]
690	690
	936	+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]]
691	691
	938	+
692	692	AT+<CMD>?  : Help on <CMD>
693	693
694	694	AT+<CMD>         : Run <CMD>
...	...	@@ -728,7 +728,24 @@
728	728
729	729	AT+SERVADDR  : Server Address
730	730
	978	+AT+TR      : Get or Set record time
731	731
	980	+AT+APN     : Get or set the APN
	981	+
	982	+AT+FBAND   : Get or Set whether to automatically modify the frequency band
	983	+
	984	+AT+DNSCFG  : Get or Set DNS Server
	985	+
	986	+AT+GETSENSORVALUE   : Returns the current sensor measurement
	987	+
	988	+AT+NOUD      : Get or Set the number of data to be uploaded
	989	+
	990	+AT+CDP     : Read or Clear cached data
	991	+
	992	+AT+SHTEMP: Get or Set alarm of temp
	993	+
	994	+AT+SHHUM: Get or Set alarm of moisture
	995	+
732	732	(% style="color:#037691" %)**COAP Management**
733	733
734	734	AT+URI            : Resource parameters
...	...	@@ -762,6 +762,7 @@
762	762
763	763	= ​5.  FAQ =
764	764
	1029	+
765	765	== 5.1 ​ How to Upgrade Firmware ==
766	766
767	767
...	...	@@ -776,13 +776,16 @@
776	776	(((
777	777
778	778
779		-(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
	1044	+(((
	1045	+(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
780	780	)))
	1047	+)))
781	781
782	782
783	783
784	784	= 6.  Trouble Shooting =
785	785
	1053	+
786	786	== 6.1  ​Connection problem when uploading firmware ==
787	787
788	788
...	...	@@ -798,6 +798,7 @@
798	798
799	799	== 6.2  AT Command input doesn't work ==
800	800
	1069	+
801	801	(((
802	802	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.
803	803
...	...	@@ -847,5 +847,6 @@
847	847
848	848	= 9.  Support =
849	849
	1119	+
850	850	* 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.
851	851	* 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

image-20221009001045-1.png

Author

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

Size

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

Content