Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual

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

...	...	@@ -9,6 +9,7 @@
9	9
10	10	**Table of Contents:**
11	11
	12	+{{toc/}}
12	12
13	13
14	14
...	...	@@ -18,27 +18,31 @@
18	18
19	19	== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
20	20
21		-(((
22		-
23	23
	23	+(((
24	24	The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*.
	25	+)))
25	25
	27	+(((
26	26	The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use.
	29	+)))
27	27
	31	+(((
28	28	N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
	33	+)))
29	29
	35	+(((
30	30	N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report).
	37	+)))
31	31
32		-
	39	+(((
33	33	~* make sure you have NB-IoT coverage locally.
34		-
35		-
36	36	)))
37	37
	43	+
38	38	[[image:1657348284168-431.png]]
39	39
40	40
41		-
42	42	== 1.2 ​ Features ==
43	43
44	44
...	...	@@ -64,16 +64,15 @@
64	64
65	65	(% style="color:#037691" %)**NB-IoT Spec:**
66	66
67		-* - B1 @H-FDD: 2100MHz
68		-* - B3 @H-FDD: 1800MHz
69		-* - B8 @H-FDD: 900MHz
70		-* - B5 @H-FDD: 850MHz
71		-* - B20 @H-FDD: 800MHz
72		-* - B28 @H-FDD: 700MHz
	72	+* B1 @H-FDD: 2100MHz
	73	+* B3 @H-FDD: 1800MHz
	74	+* B8 @H-FDD: 900MHz
	75	+* B5 @H-FDD: 850MHz
	76	+* B20 @H-FDD: 800MHz
	77	+* B28 @H-FDD: 700MHz
73	73
74	74	(% style="color:#037691" %)**Battery:**
75	75
76		-
77	77	* Li/SOCI2 un-chargeable battery
78	78	* Capacity: 8500mAh
79	79	* Self Discharge: <1% / Year @ 25°C
...	...	@@ -83,6 +83,7 @@
83	83
84	84	== ​1.4  Applications ==
85	85
	90	+
86	86	* Smart Buildings & Home Automation
87	87	* Logistics and Supply Chain Management
88	88	* Smart Metering
...	...	@@ -94,40 +94,47 @@
94	94	​
95	95
96	96
97		-== 1.5  Pin Definitions ==
	102	+== 1.5  Pin Definitions & Switch ==
98	98
	104	+
99	99	N95S31B use the mother board from NBSN95 which as below.
100	100
	107	+
101	101	[[image:image-20220709144723-1.png]]
102	102
103	103
104	104	=== 1.5.1 Jumper JP2 ===
105	105
	113	+
106	106	Power on Device when put this jumper.
107	107
108	108
109		-
110	110	=== 1.5.2 BOOT MODE / SW1 ===
111	111
112		-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.
113	113
114		-2) Flash: work mode, device starts to work and send out console output for further debug
	120	+(((
	121	+**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.
	122	+)))
115	115
	124	+(((
	125	+**2) Flash:**  work mode, device starts to work and send out console output for further debug
	126	+)))
116	116
117	117
118	118	=== 1.5.3 Reset Button ===
119	119
	131	+
120	120	Press to reboot the device.
121	121
122	122
123		-
124	124	=== 1.5.4 LED ===
125	125
	137	+
126	126	It will flash:
127	127
128		-1. When boot the device in flash mode
129		-1. Send an uplink packet
	140	+1.  When boot the device in flash mode
130	130
	142	+2.  Send an uplink packet
131	131
132	132
133	133	= 2.  Use N95S31B to communicate with IoT Server =
...	...	@@ -148,16 +148,14 @@
148	148
149	149	)))
150	150
151		-[[image:1657350248151-650.png]]
	163	+[[image:1657520100595-569.png]]
152	152
153	153	(((
154	154
155	155	)))
156	156
157		-
158	158	== 2.2 ​ Configure the N95S31B ==
159	159
160		-
161	161	=== 2.2.1  Power On N95S31B ===
162	162
163	163
...	...	@@ -164,26 +164,48 @@
164	164	[[image:image-20220709150546-2.png]]
165	165
166	166
167		-=== 2.2.1 Test Requirement ===
	177	+=== 2.2.2 Test Requirement ===
168	168
169	169
	180	+(((
170	170	To use N95S31B in your city, make sure meet below requirements:
	182	+)))
171	171
172		-* Your local operator has already distributed a NB-IoT Network there.
173		-* The local NB-IoT network used the band that N95S31B supports.
174		-* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	184	+* (((
	185	+Your local operator has already distributed a NB-IoT Network there.
	186	+)))
	187	+* (((
	188	+The local NB-IoT network used the band that N95S31B supports.
	189	+)))
	190	+* (((
	191	+Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	192	+)))
175	175
	194	+(((
176	176	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
	196	+)))
177	177
	198	+(((
178	178	N95S31B supports different communication protocol such as :
	200	+)))
179	179
180	180	(((
181		-* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
182		-* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
183		-* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
184		-* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	203	+* (((
	204	+CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
	205	+)))
	206	+* (((
	207	+raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
	208	+)))
	209	+* (((
	210	+MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
	211	+)))
	212	+* (((
	213	+TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	214	+)))
185	185
	216	+(((
186	186	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.
	218	+)))
187	187
188	188
189	189	)))
...	...	@@ -191,9 +191,9 @@
191	191	[[image:1657350625843-586.png]]
192	192
193	193
194		-
195	195	=== 2.2.3  Insert SIM card ===
196	196
	228	+
197	197	(((
198	198	Insert the NB-IoT Card get from your provider.
199	199	)))
...	...	@@ -206,26 +206,29 @@
206	206	[[image:1657351240556-536.png]]
207	207
208	208
209		-
210	210	=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
211	211
	243	+
212	212	(((
213	213	(((
214	214	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.
	247	+
	248	+
215	215	)))
216	216	)))
217	217
218	218	[[image:1657351312545-300.png]]
219	219
220		-**Connection:**
221	221
222		- (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
	255	+(% style="color:blue" %)**Connection:**
223	223
224		- (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
	257	+ (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
225	225
226		- (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
	259	+**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
227	227
	261	+**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
228	228
	263	+
229	229	In the PC, use below serial tool settings:
230	230
231	231	* Baud:  (% style="color:green" %)**9600**
...	...	@@ -240,17 +240,18 @@
240	240
241	241	[[image:1657329814315-101.png]]
242	242
	278	+
243	243	(((
244		-(% 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/]]
	280	+(% 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]]**
245	245	)))
246	246
247	247
248		-
249	249	=== 2.2.5  Use CoAP protocol to uplink data ===
250	250
251		-(% 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/]]
252	252
	287	+(% 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/]]**
253	253
	289	+
254	254	(((
255	255	**Use below commands:**
256	256	)))
...	...	@@ -259,10 +259,10 @@
259	259	(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
260	260	)))
261	261	* (((
262		-(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
	298	+(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
263	263	)))
264	264	* (((
265		-(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
	301	+(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
266	266	)))
267	267
268	268	(((
...	...	@@ -281,7 +281,6 @@
281	281	[[image:1657352185396-303.png]]
282	282
283	283
284		-
285	285	=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
286	286
287	287
...	...	@@ -295,18 +295,18 @@
295	295	[[image:1657352403317-397.png]]
296	296
297	297
298		-
299	299	=== 2.2.7  Use MQTT protocol to uplink data ===
300	300
	335	+
301	301	N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
302	302
303		-* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
304		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
305		-* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
306		-* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
307		-* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
308		-* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
309		-* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
	338	+* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
	339	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
	340	+* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
	341	+* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
	342	+* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
	343	+* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
	344	+* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
310	310
311	311	[[image:1657352634421-276.png]]
312	312
...	...	@@ -313,19 +313,19 @@
313	313
314	314	[[image:1657352645687-385.png]]
315	315
	351	+
316	316	(((
317	317	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.
318	318	)))
319	319
320		-
321	321	(((
322	322	MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
323	323	)))
324	324
325	325
326		-
327	327	=== 2.2.8  Use TCP protocol to uplink data ===
328	328
	363	+
329	329	This feature is supported since firmware version v110
330	330
331	331	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
...	...	@@ -337,9 +337,9 @@
337	337	[[image:1657352914475-252.png]]
338	338
339	339
340		-
341	341	=== 2.2.9  Change Update Interval ===
342	342
	377	+
343	343	User can use below command to change the (% style="color:green" %)**uplink interval**.
344	344
345	345	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
...	...	@@ -348,59 +348,99 @@
348	348
349	349	)))
350	350
	386	+(((
	387	+(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
	388	+)))
351	351
	390	+(((
	391	+(% 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).**
	392	+)))
352	352
	394	+
353	353	== 2.3  Uplink Payload ==
354	354
355	355
356		-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.
	398	+(((
	399	+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.
	400	+)))
357	357
358	358
	403	+(((
359	359	For example:
	405	+)))
360	360
361		- (% 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.
	407	+(((
	408	+ (% 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.
	409	+)))
362	362
363	363
	412	+(((
364	364	The uplink payloads are composed in  ASCII String. For example:
	414	+)))
365	365
	416	+(((
366	366	0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
	418	+)))
367	367
	420	+(((
368	368	0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
	422	+)))
369	369
370	370
	425	+(((
371	371	(% style="color:red" %)**NOTE:**
	427	+)))
372	372
373	373	(% style="color:red" %)
374		-1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
375		-1. By default, the device will send an uplink message every 1 hour.
	430	+1. (((
	431	+**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
	432	+)))
	433	+1. (((
	434	+**By default, the device will send an uplink message every 1 hour.**
376	376
377	377
	437	+
	438	+)))
378	378
379		-
380	380	=== 2.3.1  Payload Analyze ===
381	381
	442	+==== 2.3.1.1  Before Firmware v1.2 ====
	443	+
	444	+
382	382	N95S31B uplink payload includes in total 21 bytes
383	383
384	384
385		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
386		-|=(% style="width: 60px;" %)(((
387		-**Size(bytes)**
388		-)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1**
389		-|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
	448	+(% border="1" style="background-color:#f2f2f2; width:520px" %)
	449	+|=(% style="width: 50px;background-color:#D9E2F3" %)**Size(bytes)**|=(% style="width: 45px;background-color:#D9E2F3" %)**6**|=(% style="width: 25px;background-color:#D9E2F3" %)2|=(% style="width: 25px;background-color:#D9E2F3" %)**2**|=(% style="width: 65px;background-color:#D9E2F3" %)**1**|=(% style="width: 50px;background-color:#D9E2F3" %)1|=(% style="width: 120px;background-color:#D9E2F3" %)5|=(% style="width: 70px;background-color:#D9E2F3" %)**2**|=(% style="width: 70px;background-color:#D9E2F3" %)**2**
	450	+|(% 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" %)(((
	451	+(((
390	390	Reserve/ Same as NBSN95 CFGMOD=1
	453	+)))
391	391
	455	+(((
392	392	No function here.
393		-)))|(% style="width:77px" %)(((
394		-[[Temperature >>||anchor="H2.4.5A0Distance"]]
	457	+)))
	458	+)))|(% style="width:102px" %)(((
	459	+(((
	460	+[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
	461	+)))
395	395
	463	+(((
396	396	By SHT31
397		-)))|(% style="width:80px" %)(((
398		-[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
	465	+)))
	466	+)))|(% style="width:81px" %)(((
	467	+(((
	468	+[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
	469	+)))
399	399
	471	+(((
400	400	By SHT31
401	401	)))
	474	+)))
402	402
403	403	(((
	477	+
	478	+
404	404	(((
405	405	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
406	406	)))
...	...	@@ -410,29 +410,88 @@
410	410	[[image:1657354294009-643.png]]
411	411
412	412
413		-The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
	488	+The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
414	414
415		-* Device ID: 0x724031607457 = 724031607457
416		-* Version: 0x006e=110=1.1.0
	490	+**where:**
417	417
418		-* BAT: 0x0ccd = 3277 mV = 3.277V
419		-* Signal: 0x1b = 27
420		-* Model: 0x01 = 1
421		-* 0x00dc000ccc= reserve, ignore in N95S31B
422		-* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
423		-* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
	492	+* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
424	424
	494	+* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
	495	+
	496	+* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
	497	+
	498	+* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
	499	+
	500	+* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
	501	+
	502	+* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
	503	+
	504	+* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
	505	+
	506	+* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
	507	+
425	425	(((
426	426
427		-)))
428	428
429		-(((
430	430
431	431	)))
432	432
	514	+==== 2.3.1.2 Since Firmware v1.2 ====
433	433
	516	+
	517	+In this mode, uplink payload includes 91 bytes in total by default.
	518	+
	519	+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.
	520	+
	521	+
	522	+(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
	523	+|=(% 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**
	524	+|=(% 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 .....
	525	+
	526	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
	527	+
	528	+
	529	+[[image:image-20220908154949-1.png]]
	530	+
	531	+
	532	+The payload is ASCII string, representative same HEX:
	533	+
	534	+**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__ **
	535	+
	536	+**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
	537	+
	538	+**where:**
	539	+
	540	+* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
	541	+
	542	+* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
	543	+
	544	+* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
	545	+
	546	+* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
	547	+
	548	+* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
	549	+
	550	+* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
	551	+
	552	+* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
	553	+
	554	+* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
	555	+
	556	+* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
	557	+
	558	+* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
	559	+
	560	+* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	561	+
	562	+* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
	563	+
	564	+* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
	565	+
	566	+
434	434	=== 2.3.2  Device ID ===
435	435
	569	+
436	436	(((
437	437	By default, the Device ID equal to the last 6 bytes of IMEI.
438	438	)))
...	...	@@ -439,10 +439,12 @@
439	439
440	440	(((
441	441	User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	576	+
	577	+
442	442	)))
443	443
444	444	(((
445		-**Example:**
	581	+(% style="color:blue" %)**Example:**
446	446	)))
447	447
448	448	(((
...	...	@@ -450,30 +450,54 @@
450	450	)))
451	451
452	452	(((
453		-The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	589	+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.
	590	+
	591	+
454	454	)))
455	455
	594	+(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
456	456
457	457
	597	+By default, the Device ID equal to the last 15 bits of IMEI.
	598	+
	599	+User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
	600	+
	601	+
	602	+(% style="color:blue" %)**Example:**
	603	+
	604	+AT+DEUI=868411056754138
	605	+
	606	+
458	458	=== 2.3.3  Version Info ===
459	459
460	460
	610	+(((
461	461	These bytes include the hardware and software version.
	612	+)))
462	462
463		-Higher byte: Specify hardware version: always 0x00 for N95S31B
	614	+(((
	615	+**Higher byte:** Specify hardware version: always 0x00 for N95S31B
	616	+)))
464	464
465		-Lower byte: Specify the software version: 0x6E=110, means firmware version 110
	618	+(((
	619	+**Lower byte:** Specify the software version: 0x6E=110, means firmware version 110
	620	+)))
466	466
	622	+(((
	623	+
	624	+)))
467	467
	626	+(((
468	468	For example: 0x00 6E: this device is N95S31B with firmware version 110.
	628	+)))
469	469
470	470	(((
471	471
472	472	)))
473	473
474		-
475	475	=== 2.3.4  Battery Info ===
476	476
	636	+
477	477	(((
478	478	Ex1: 0x0B45 = 2885mV
479	479	)))
...	...	@@ -483,9 +483,9 @@
483	483	)))
484	484
485	485
486		-
487	487	=== 2.3.5  Signal Strength ===
488	488
	648	+
489	489	(((
490	490	NB-IoT Network signal Strength.
491	491	)))
...	...	@@ -515,9 +515,9 @@
515	515	)))
516	516
517	517
518		-
519	519	=== 2.3.6  Temperature & Humidity ===
520	520
	680	+
521	521	The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
522	522
523	523	[[image:image-20220709161741-3.png]]
...	...	@@ -533,10 +533,10 @@
533	533	Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
534	534
535	535
	696	+== 2.4  Downlink Payload ==
536	536
537		-== 2.5  Downlink Payload ==
538	538
539		-By default, NDDS75 prints the downlink payload to console port.
	699	+By default, N95S31B prints the downlink payload to console port.
540	540
541	541	[[image:image-20220709100028-1.png]]
542	542
...	...	@@ -574,7 +574,7 @@
574	574	)))
575	575
576	576	(((
577		-If payload = 0x04FF, it will reset the NDDS75
	737	+If payload = 0x04FF, it will reset the N95S31B
578	578	)))
579	579
580	580
...	...	@@ -585,144 +585,97 @@
585	585	)))
586	586
587	587
	748	+== 2.5  Humidity and Temperature alarm function ==
588	588
589		-== 2.6  ​LED Indicator ==
590	590
	751	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
591	591
592		-The NDDS75 has an internal LED which is to show the status of different state.
593	593
	754	+(% style="color:#037691" %)**AT+ SHHUM=min,max**
594	594
595		-* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
596		-* Then the LED will be on for 1 second means device is boot normally.
597		-* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
598		-* For each uplink probe, LED will be on for 500ms.
599	599
600		-(((
601		-
602		-)))
	757	+² When min=0, and max≠0, Alarm higher than max
603	603
	759	+² When min≠0, and max=0, Alarm lower than min
604	604
	761	+² When min≠0 and max≠0, Alarm higher than max or lower than min
605	605
606		-== 2.7  ​Firmware Change Log ==
607	607
	764	+ (% style="color:blue" %)**Example:**
608	608
609		-(((
610		-Download URL & Firmware Change log
611		-)))
	766	+AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
612	612
613		-(((
614		-[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
615		-)))
616	616
	769	+(% style="color:#037691" %)**AT+ SHTEMP=min,max**
617	617
618		-(((
619		-Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
620		-)))
	771	+² When min=0, and max≠0, Alarm higher than max
621	621
	773	+² When min≠0, and max=0, Alarm lower than min
622	622
	775	+² When min≠0 and max≠0, Alarm higher than max or lower than min
623	623
624		-== 2.8  ​Battery Analysis ==
625	625
626		-=== 2.8.1  ​Battery Type ===
	778	+**~ (% style="color:blue" %)Example:(%%)**
627	627
	780	+AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
628	628
629		-(((
630		-The NDDS75 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.
631		-)))
632	632
633		-(((
634		-The battery is designed to last for several years depends on the actually use environment and update interval.
635		-)))
	783	+== 2.6 Set the number of data to be uploaded and the recording time ==
636	636
637		-(((
638		-The battery related documents as below:
639		-)))
640	640
641		-* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
642		-* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
643		-* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	786	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
644	644
645		-(((
646		-[[image:image-20220709101450-2.png]]
647		-)))
	788	+* (% 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)
	789	+* (% 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.
648	648
	791	+ The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
649	649
	793	+[[image:image-20221009001045-1.png||height="726" width="1009"]]
650	650
651		-=== 2.8.2  Power consumption Analyze ===
652	652
653		-(((
654		-Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
655		-)))
	796	+== 2.7 Read or Clear cached data ==
656	656
657	657
658		-(((
659		-Instruction to use as below:
660		-)))
	799	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
661	661
662		-(((
663		-(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
664		-)))
	801	+* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
	802	+* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
665	665
	804	+[[image:image-20220908163102-2.png]]
666	666
667		-(((
668		-(% style="color:blue" %)**Step 2: **(%%) Open it and choose
669		-)))
670	670
671		-* (((
672		-Product Model
673		-)))
674		-* (((
675		-Uplink Interval
676		-)))
677		-* (((
678		-Working Mode
679		-)))
	807	+== 2.8 Battery & Power Consumption ==
680	680
681		-(((
682		-And the Life expectation in difference case will be shown on the right.
683		-)))
684	684
685		-[[image:image-20220709110451-3.png]]
	810	+N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
686	686
	812	+[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
687	687
688	688
689		-=== 2.8.3  ​Battery Note ===
	815	+= 3. ​ Access NB-IoT Module =
690	690
691		-(((
692		-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 transmit LoRa, then the battery life may be decreased.
693		-)))
694	694
695		-
696		-
697		-=== 2.8.4  Replace the battery ===
698		-
699	699	(((
700		-The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
701		-)))
702		-
703		-
704		-
705		-= 3. ​ Access NB-IoT Module =
706		-
707		-(((
708	708	Users can directly access the AT command set of the NB-IoT module.
709	709	)))
710	710
711	711	(((
712	712	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/]]
	824	+
	825	+
713	713	)))
714	714
715	715	[[image:1657333200519-600.png]]
716	716
717	717
718		-
719	719	= 4.  Using the AT Commands =
720	720
721	721	== 4.1  Access AT Commands ==
722	722
723		-See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
724	724
	836	+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]]
725	725
	838	+
726	726	AT+<CMD>?  : Help on <CMD>
727	727
728	728	AT+<CMD>         : Run <CMD>
...	...	@@ -762,7 +762,24 @@
762	762
763	763	AT+SERVADDR  : Server Address
764	764
	878	+AT+TR      : Get or Set record time
765	765
	880	+AT+APN     : Get or set the APN
	881	+
	882	+AT+FBAND   : Get or Set whether to automatically modify the frequency band
	883	+
	884	+AT+DNSCFG  : Get or Set DNS Server
	885	+
	886	+AT+GETSENSORVALUE   : Returns the current sensor measurement
	887	+
	888	+AT+NOUD      : Get or Set the number of data to be uploaded
	889	+
	890	+AT+CDP     : Read or Clear cached data
	891	+
	892	+AT+SHTEMP: Get or Set alarm of temp
	893	+
	894	+AT+SHHUM: Get or Set alarm of moisture
	895	+
766	766	(% style="color:#037691" %)**COAP Management**
767	767
768	768	AT+URI            : Resource parameters
...	...	@@ -793,7 +793,6 @@
793	793	AT+PWORD  : Serial Access Password
794	794
795	795
796		-
797	797	= ​5.  FAQ =
798	798
799	799	== 5.1 ​ How to Upgrade Firmware ==
...	...	@@ -808,11 +808,12 @@
808	808	)))
809	809
810	810	(((
811		-(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
	940	+Firmware Download：[[https:~~/~~/www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0>>https://www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0]]
	941	+
	942	+(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
812	812	)))
813	813
814	814
815		-
816	816	= 6.  Trouble Shooting =
817	817
818	818	== 6.1  ​Connection problem when uploading firmware ==
...	...	@@ -822,14 +822,10 @@
822	822	**Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
823	823	)))
824	824
825		-(% class="wikigeneratedid" %)
826		-(((
827		-
828		-)))
829	829
830		-
831	831	== 6.2  AT Command input doesn't work ==
832	832
	958	+
833	833	(((
834	834	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.
835	835
...	...	@@ -836,18 +836,18 @@
836	836
837	837	)))
838	838
	965	+== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
839	839
840		-= 7. ​ Order Info =
841	841
	968	+This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
842	842
843		-Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
844	844
	971	+= 7. ​ Order Info =
845	845
846		-(% class="wikigeneratedid" %)
847		-(((
848		-
849		-)))
850	850
	974	+Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
	975	+
	976	+
851	851	= 8.  Packing Info =
852	852
853	853	(((
...	...	@@ -855,7 +855,7 @@
855	855
856	856	(% style="color:#037691" %)**Package Includes**:
857	857
858		-* NSE01 NB-IoT Distance Detect Sensor Node x 1
	984	+* N95S31B NB-IoT Temperature and Humidity Sensor
859	859	* External antenna x 1
860	860	)))
861	861
...	...	@@ -864,21 +864,19 @@
864	864
865	865	(% style="color:#037691" %)**Dimension and weight**:
866	866
867		-
868	868	* Device Size: 13.0 x 5 x 4.5 cm
869	869	* Device Weight: 150g
870		-* Package Size / pcs : 15 x 12x 5.5 cm
871		-* Weight / pcs : 220g
	995	+* Package Size / pcs : 14.0 x 8x 5 cm
	996	+* Weight / pcs : 180g
872	872	)))
873	873
874		-(((
875		-
876	876
877	877
878		-
879		-)))
880		-
881	881	= 9.  Support =
882	882
	1003	+
883	883	* 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.
	1005	+
884	884	* 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]]
	1007	+
	1008	+

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