Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 16 added, 0 removed)
  • 1657350625843-586.png
  • 1657351240556-536.png
  • 1657351312545-300.png
  • 1657352146020-183.png
  • 1657352185396-303.png
  • 1657352391268-297.png
  • 1657352403317-397.png
  • 1657352634421-276.png
  • 1657352645687-385.png
  • 1657352898400-901.png
  • 1657352914475-252.png
  • 1657354294009-643.png
  • 1657520100595-569.png
  • image-20220709161741-3.png
  • image-20220908154949-1.png
  • image-20220908163102-2.png

Details

Page properties

Author

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

Content

...	...	@@ -9,6 +9,7 @@
9	9
10	10	**Table of Contents:**
11	11
	12	+{{toc/}}
12	12
13	13
14	14
...	...	@@ -16,21 +16,35 @@
16	16
17	17	= 1.  Introduction =
18	18
	20	+
19	19	== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
20	20
21	21	(((
22	22
23	23
	26	+(((
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*.
	28	+)))
25	25
	30	+(((
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.
	32	+)))
27	27
	34	+(((
28	28	N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
	36	+)))
29	29
	38	+(((
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).
	40	+)))
31	31
	42	+(((
	43	+
	44	+)))
32	32
	46	+(((
33	33	~* make sure you have NB-IoT coverage locally.
	48	+)))
34	34
35	35
36	36	)))
...	...	@@ -53,8 +53,6 @@
53	53	* Micro SIM card slot for NB-IoT SIM
54	54	* 8500mAh Battery for long term use
55	55
56		-
57		-
58	58	== 1.3  Specification ==
59	59
60	60
...	...	@@ -74,7 +74,6 @@
74	74
75	75	(% style="color:#037691" %)**Battery:**
76	76
77		-
78	78	* Li/SOCI2 un-chargeable battery
79	79	* Capacity: 8500mAh
80	80	* Self Discharge: <1% / Year @ 25°C
...	...	@@ -81,10 +81,9 @@
81	81	* Max continuously current: 130mA
82	82	* Max boost current: 2A, 1 second
83	83
84		-
85		-
86	86	== ​1.4  Applications ==
87	87
	98	+
88	88	* Smart Buildings & Home Automation
89	89	* Logistics and Supply Chain Management
90	90	* Smart Metering
...	...	@@ -96,15 +96,20 @@
96	96	​
97	97
98	98
99		-== 1.5  Pin Definitions ==
100	100
	111	+== 1.5  Pin Definitions & Switch ==
	112	+
	113	+
101	101	N95S31B use the mother board from NBSN95 which as below.
102	102
	116	+
103	103	[[image:image-20220709144723-1.png]]
104	104
105	105
	120	+
106	106	=== 1.5.1 Jumper JP2 ===
107	107
	123	+
108	108	Power on Device when put this jumper.
109	109
110	110
...	...	@@ -111,14 +111,20 @@
111	111
112	112	=== 1.5.2 BOOT MODE / SW1 ===
113	113
	130	+
	131	+(((
114	114	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.
	133	+)))
115	115
	135	+(((
116	116	2) Flash: work mode, device starts to work and send out console output for further debug
	137	+)))
117	117
118	118
119	119
120	120	=== 1.5.3 Reset Button ===
121	121
	143	+
122	122	Press to reboot the device.
123	123
124	124
...	...	@@ -125,16 +125,15 @@
125	125
126	126	=== 1.5.4 LED ===
127	127
	150	+
128	128	It will flash:
129	129
130	130	1. When boot the device in flash mode
131	131	1. Send an uplink packet
132	132
133		-
134		-
135		-
136	136	= 2.  Use N95S31B to communicate with IoT Server =
137	137
	158	+
138	138	== 2.1  How it works ==
139	139
140	140
...	...	@@ -151,7 +151,7 @@
151	151
152	152	)))
153	153
154		-[[image:1657350248151-650.png]]
	175	+[[image:1657520100595-569.png]]
155	155
156	156	(((
157	157
...	...	@@ -166,27 +166,61 @@
166	166
167	167	[[image:image-20220709150546-2.png]]
168	168
	190	+
	191	+
169	169	=== 2.2.1 Test Requirement ===
170	170
	194	+
171	171	(((
172		-To use NDDS75 in your city, make sure meet below requirements:
	196	+To use N95S31B in your city, make sure meet below requirements:
173	173	)))
174	174
175		-* Your local operator has already distributed a NB-IoT Network there.
176		-* The local NB-IoT network used the band that NSE01 supports.
177		-* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	199	+* (((
	200	+Your local operator has already distributed a NB-IoT Network there.
	201	+)))
	202	+* (((
	203	+The local NB-IoT network used the band that N95S31B supports.
	204	+)))
	205	+* (((
	206	+Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	207	+)))
178	178
179	179	(((
180		-Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
	210	+Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
181	181	)))
182	182
	213	+(((
	214	+N95S31B supports different communication protocol such as :
	215	+)))
183	183
184		-[[image:1657328756309-230.png]]
	217	+(((
	218	+* (((
	219	+CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
	220	+)))
	221	+* (((
	222	+raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
	223	+)))
	224	+* (((
	225	+MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
	226	+)))
	227	+* (((
	228	+TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	229	+)))
185	185
	231	+(((
	232	+We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server.
	233	+)))
186	186
	235	+
	236	+)))
187	187
188		-=== 2.2.2 Insert SIM card ===
	238	+[[image:1657350625843-586.png]]
189	189
	240	+
	241	+
	242	+=== 2.2.3  Insert SIM card ===
	243	+
	244	+
190	190	(((
191	191	Insert the NB-IoT Card get from your provider.
192	192	)))
...	...	@@ -196,20 +196,24 @@
196	196	)))
197	197
198	198
199		-[[image:1657328884227-504.png]]
	254	+[[image:1657351240556-536.png]]
200	200
201	201
202	202
203		-=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
	258	+=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
204	204
	260	+
205	205	(((
206	206	(((
207		-User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
	263	+User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below.
	264	+
	265	+
208	208	)))
209	209	)))
210	210
211		-[[image:image-20220709092052-2.png]]
	269	+[[image:1657351312545-300.png]]
212	212
	271	+
213	213	**Connection:**
214	214
215	215	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
...	...	@@ -228,22 +228,24 @@
228	228	* Flow Control: (% style="color:green" %)**None**
229	229
230	230	(((
231		-Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
	290	+Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
232	232	)))
233	233
234	234	[[image:1657329814315-101.png]]
235	235
	295	+
236	236	(((
237		-(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
	297	+(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**
238	238	)))
239	239
240	240
241	241
242		-=== 2.2.4 Use CoAP protocol to uplink data ===
	302	+=== 2.2.5  Use CoAP protocol to uplink data ===
243	243
244		-(% 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/]]
245	245
	305	+(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**
246	246
	307	+
247	247	(((
248	248	**Use below commands:**
249	249	)))
...	...	@@ -259,10 +259,12 @@
259	259	)))
260	260
261	261	(((
	323	+
	324	+
262	262	For parameter description, please refer to AT command set
263	263	)))
264	264
265		-[[image:1657330452568-615.png]]
	328	+[[image:1657352146020-183.png]]
266	266
267	267
268	268	(((
...	...	@@ -269,11 +269,11 @@
269	269	After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
270	270	)))
271	271
272		-[[image:1657330472797-498.png]]
	335	+[[image:1657352185396-303.png]]
273	273
274	274
275	275
276		-=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
	339	+=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
277	277
278	278
279	279	* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
...	...	@@ -280,109 +280,114 @@
280	280	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
281	281	* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
282	282
283		-[[image:1657330501006-241.png]]
	346	+[[image:1657352391268-297.png]]
284	284
285	285
286		-[[image:1657330533775-472.png]]
	349	+[[image:1657352403317-397.png]]
287	287
288	288
289	289
290		-=== 2.2.6 Use MQTT protocol to uplink data ===
	353	+=== 2.2.7  Use MQTT protocol to uplink data ===
291	291
292	292
	356	+N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
	357	+
293	293	* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
294	294	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
295	295	* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
296	296	* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
297	297	* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
298		-* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
299		-* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
	363	+* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
	364	+* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
300	300
301		-[[image:1657249978444-674.png]]
	366	+[[image:1657352634421-276.png]]
302	302
303	303
304		-[[image:1657330723006-866.png]]
	369	+[[image:1657352645687-385.png]]
305	305
306	306
307	307	(((
308		-MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
	373	+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.
309	309	)))
310	310
311	311
	377	+(((
	378	+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.
	379	+)))
312	312
313		-=== 2.2.7 Use TCP protocol to uplink data ===
314	314
315	315
	383	+=== 2.2.8  Use TCP protocol to uplink data ===
	384	+
	385	+
	386	+This feature is supported since firmware version v110
	387	+
316	316	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
317	317	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
318	318
319		-[[image:image-20220709093918-1.png]]
	391	+[[image:1657352898400-901.png]]
320	320
321	321
322		-[[image:image-20220709093918-2.png]]
	394	+[[image:1657352914475-252.png]]
323	323
324	324
325	325
326		-=== 2.2.8 Change Update Interval ===
	398	+=== 2.2.9  Change Update Interval ===
327	327
	400	+
328	328	User can use below command to change the (% style="color:green" %)**uplink interval**.
329	329
330	330	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
331	331
332	332	(((
333		-(% style="color:red" %)**NOTE:**
	406	+
334	334	)))
335	335
336		-(((
337		-(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
338		-)))
	409	+(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
339	339
	411	+**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
340	340
341	341
342	342	== 2.3  Uplink Payload ==
343	343
344		-In this mode, uplink payload includes in total 14 bytes
345	345
	417	+(((
	418	+N95S31B 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.
	419	+)))
346	346
347		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
348		-|=(% style="width: 60px;" %)(((
349		-**Size(bytes)**
350		-)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
351		-|(% 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:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
352	352
353	353	(((
354		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
	423	+For example:
355	355	)))
356	356
	426	+(((
	427	+ (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
	428	+)))
357	357
358		-[[image:1657331036973-987.png]]
359	359
360	360	(((
361		-The payload is ASCII string, representative same HEX:
	432	+The uplink payloads are composed in  ASCII String. For example:
362	362	)))
363	363
364	364	(((
365		-0x72403155615900640c6c19029200 where:
	436	+0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
366	366	)))
367	367
368		-* (((
369		-Device ID: 0x724031556159 = 724031556159
	439	+(((
	440	+0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
370	370	)))
371		-* (((
372		-Version: 0x0064=100=1.0.0
	442	+
	443	+
	444	+(((
	445	+(% style="color:red" %)**NOTE:**
373	373	)))
374	374
375		-* (((
376		-BAT: 0x0c6c = 3180 mV = 3.180V
	448	+(% style="color:red" %)
	449	+1. (((
	450	+**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
377	377	)))
378		-* (((
379		-Signal: 0x19 = 25
380		-)))
381		-* (((
382		-Distance: 0x0292= 658 mm
383		-)))
384		-* (((
385		-Interrupt: 0x00 = 0
	452	+1. (((
	453	+**By default, the device will send an uplink message every 1 hour.**
386	386
387	387
388	388
...	...	@@ -389,105 +389,153 @@
389	389
390	390	)))
391	391
392		-== 2.4  Payload Explanation and Sensor Interface ==
	460	+=== 2.3.1  Payload Analyze ===
393	393
394	394
395		-=== 2.4.1  Device ID ===
	463	+N95S31B uplink payload includes in total 21 bytes
396	396
	465	+
	466	+(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
	467	+|=(% style="width: 60px;" %)(((
	468	+**Size(bytes)**
	469	+)))|=(% 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**
	470	+|(% 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" %)(((
397	397	(((
398		-By default, the Device ID equal to the last 6 bytes of IMEI.
	472	+Reserve/ Same as NBSN95 CFGMOD=1
399	399	)))
400	400
401	401	(((
402		-User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	476	+No function here.
403	403	)))
	478	+)))|(% style="width:77px" %)(((
	479	+(((
	480	+[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
	481	+)))
404	404
405	405	(((
406		-**Example:**
	484	+By SHT31
407	407	)))
	486	+)))|(% style="width:80px" %)(((
	487	+(((
	488	+[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
	489	+)))
408	408
409	409	(((
410		-AT+DEUI=A84041F15612
	492	+By SHT31
411	411	)))
	494	+)))
412	412
413	413	(((
414		-The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	497	+
	498	+
	499	+(((
	500	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
415	415	)))
	502	+)))
416	416
417	417
	505	+[[image:1657354294009-643.png]]
418	418
419		-=== 2.4.2  Version Info ===
420	420
	508	+The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
	509	+
	510	+* Device ID: 0x724031607457 = 724031607457
	511	+* Version: 0x006e=110=1.1.0
	512	+
	513	+* BAT: 0x0ccd = 3277 mV = 3.277V
	514	+* Signal: 0x1b = 27
	515	+* Model: 0x01 = 1
	516	+* 0x00dc000ccc= reserve, ignore in N95S31B
	517	+* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
	518	+* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
	519	+
421	421	(((
422		-Specify the software version: 0x64=100, means firmware version 1.00.
	521	+
423	423	)))
424	424
425	425	(((
426		-For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
	525	+(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
427	427	)))
428	428
	528	+In this mode, uplink payload includes 91 bytes in total by default.
429	429
	530	+Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
430	430
431		-=== 2.4.3  Battery Info ===
	532	+|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4
	533	+|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp .....
432	432
433		-(((
434		-Ex1: 0x0B45 = 2885mV
435		-)))
	535	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
436	436
437		-(((
438		-Ex2: 0x0B49 = 2889mV
439		-)))
	537	+[[image:image-20220908154949-1.png]]
440	440
	539	+The payload is ASCII string, representative same HEX:
441	441
	541	+0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where:
442	442
443		-=== 2.4.4  Signal Strength ===
	543	+* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782
	544	+* (% style="color:blue" %) Version: 0x000c=120=1.2
	545	+* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V
	546	+* (% style="color:red" %) Singal: 0x0c = 12
	547	+* (% style="color:blue" %) Mod: 0x01 = 1
	548	+* TemDS18B20: 0x0000= 0 = 0
	549	+* (% style="color:green" %)Interrupt: 0x00= 0
	550	+* (% style="color:green" %)adc: 0x0030= 48
	551	+* SHTTEM: 0x0114= 276 = 27.6
	552	+* SHTHUM:0x0231 =561=56.1%
	553	+* (% style="color:red" %) Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	554	+* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
	555	+* 8 sets of recorded data: SHTTEM(% style="color:red" %),SHTHUM,Time stamp : //**0113023163199c5e**//,.......
444	444
445		-(((
446		-NB-IoT Network signal Strength.
447		-)))
	557	+=== 2.3.2  Device ID ===
448	448
449		-(((
450		-**Ex1: 0x1d = 29**
451		-)))
452	452
453	453	(((
454		-(% style="color:blue" %)**0**(%%)  -113dBm or less
	561	+By default, the Device ID equal to the last 6 bytes of IMEI.
455	455	)))
456	456
457	457	(((
458		-(% style="color:blue" %)**1**(%%)  -111dBm
	565	+User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
459	459	)))
460	460
461	461	(((
462		-(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
	569	+**Example:**
463	463	)))
464	464
465	465	(((
466		-(% style="color:blue" %)**31**  (%%) -51dBm or greater
	573	+AT+DEUI=A84041F15612
467	467	)))
468	468
469	469	(((
470		-(% style="color:blue" %)**99**   (%%) Not known or not detectable
	577	+The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	578	+
	579	+
471	471	)))
472	472
	582	+(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
473	473
474	474
475		-=== 2.4.5  Distance ===
	585	+By default, the Device ID equal to the last 15 bits of IMEI.
476	476
477		-Get the distance. Flat object range 280mm - 7500mm.
	587	+User can use **AT+DEUI** to set Device ID
478	478
	589	+**Example:**
	590	+
	591	+AT+DEUI=868411056754138
	592	+
	593	+
	594	+=== 2.3.3  Version Info ===
	595	+
	596	+
479	479	(((
480		-For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
	598	+These bytes include the hardware and software version.
481	481	)))
482	482
483	483	(((
484		-(((
485		-(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
	602	+Higher byte: Specify hardware version: always 0x00 for N95S31B
486	486	)))
487		-)))
488	488
489	489	(((
490		-
	606	+Lower byte: Specify the software version: 0x6E=110, means firmware version 110
491	491	)))
492	492
493	493	(((
...	...	@@ -494,65 +494,85 @@
494	494
495	495	)))
496	496
497		-=== 2.4.6  Digital Interrupt ===
498		-
499	499	(((
500		-Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
	614	+For example: 0x00 6E: this device is N95S31B with firmware version 110.
501	501	)))
502	502
503	503	(((
504		-The command is:
	618	+
505	505	)))
506	506
	621	+
	622	+=== 2.3.4  Battery Info ===
	623	+
	624	+
507	507	(((
508		-(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
	626	+Ex1: 0x0B45 = 2885mV
509	509	)))
510	510
511		-
512	512	(((
513		-The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
	630	+Ex2: 0x0B49 = 2889mV
514	514	)))
515	515
516	516
	634	+
	635	+=== 2.3.5  Signal Strength ===
	636	+
	637	+
517	517	(((
518		-Example:
	639	+NB-IoT Network signal Strength.
519	519	)))
520	520
521	521	(((
522		-0x(00): Normal uplink packet.
	643	+**Ex1: 0x1d = 29**
523	523	)))
524	524
525	525	(((
526		-0x(01): Interrupt Uplink Packet.
	647	+(% style="color:blue" %)**0**(%%)  -113dBm or less
527	527	)))
528	528
529		-
530		-
531		-=== 2.4.7  ​+5V Output ===
532		-
533	533	(((
534		-NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
	651	+(% style="color:blue" %)**1**(%%)  -111dBm
535	535	)))
536	536
537		-
538	538	(((
539		-The 5V output time can be controlled by AT Command.
	655	+(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
540	540	)))
541	541
542	542	(((
543		-(% style="color:blue" %)**AT+5VT=1000**
	659	+(% style="color:blue" %)**31**  (%%) -51dBm or greater
544	544	)))
545	545
546	546	(((
547		-Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
	663	+(% style="color:blue" %)**99**   (%%) Not known or not detectable
548	548	)))
549	549
550	550
551	551
552		-== 2.5  Downlink Payload ==
	668	+=== 2.3.6  Temperature & Humidity ===
553	553
554		-By default, NDDS75 prints the downlink payload to console port.
555	555
	671	+The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
	672	+
	673	+[[image:image-20220709161741-3.png]]
	674	+
	675	+
	676	+Convert the read byte to decimal and divide it by ten.
	677	+
	678	+
	679	+**Example:**
	680	+
	681	+Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
	682	+
	683	+Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
	684	+
	685	+
	686	+
	687	+== 2.4  Downlink Payload ==
	688	+
	689	+
	690	+By default, N95S31B prints the downlink payload to console port.
	691	+
556	556	[[image:image-20220709100028-1.png]]
557	557
558	558
...	...	@@ -589,7 +589,7 @@
589	589	)))
590	590
591	591	(((
592		-If payload = 0x04FF, it will reset the NDDS75
	728	+If payload = 0x04FF, it will reset the N95S31B
593	593	)))
594	594
595	595
...	...	@@ -600,49 +600,61 @@
600	600	)))
601	601
602	602
	739	+== 2.5 Humidity and Temperature alarm function ==
603	603
604		-== 2.6  ​LED Indicator ==
	741	+➢ AT Command:
605	605
	743	+AT+ SHHUM=min,max
606	606
607		-The NDDS75 has an internal LED which is to show the status of different state.
	745	+² When min=0, and max≠0, Alarm higher than max
608	608
	747	+² When min≠0, and max=0, Alarm lower than min
609	609
610		-* 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)
611		-* Then the LED will be on for 1 second means device is boot normally.
612		-* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
613		-* For each uplink probe, LED will be on for 500ms.
	749	+² When min≠0 and max≠0, Alarm higher than max or lower than min
614	614
615		-(((
616		-
617		-)))
	751	+Example:
618	618
	753	+AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
619	619
620	620
621		-== 2.7  ​Firmware Change Log ==
	756	+AT+ SHTEMP=min,max
622	622
	758	+² When min=0, and max≠0, Alarm higher than max
623	623
624		-(((
625		-Download URL & Firmware Change log
626		-)))
	760	+² When min≠0, and max=0, Alarm lower than min
627	627
628		-(((
629		-[[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/]]
630		-)))
	762	+² When min≠0 and max≠0, Alarm higher than max or lower than min
631	631
	764	+Example:
632	632
633		-(((
634		-Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
635		-)))
	766	+AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
636	636
	768	+== 2.6 Set the number of data to be uploaded and the recording time ==
637	637
	770	+➢ AT Command:
638	638
	772	+AT+TR=900  ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
	773	+
	774	+AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
	775	+
	776	+== 2.7 Read or Clear cached data ==
	777	+
	778	+➢ AT Command:
	779	+
	780	+AT+CDP ~/~/ Read cached data
	781	+
	782	+[[image:image-20220908163102-2.png]]
	783	+
	784	+AT+CDP=0 ~/~/ Clear cached data
	785	+
639	639	== 2.8  ​Battery Analysis ==
640	640
	788	+
641	641	=== 2.8.1  ​Battery Type ===
642	642
643	643
644	644	(((
645		-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.
	793	+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.
646	646	)))
647	647
648	648	(((
...	...	@@ -665,54 +665,35 @@
665	665
666	666	=== 2.8.2  Power consumption Analyze ===
667	667
668		-(((
669		-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.
670		-)))
671	671
672		-
673	673	(((
674		-Instruction to use as below:
	818	+The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
675	675	)))
676	676
677	677	(((
678		-(% 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/]]
	822	+
679	679	)))
680	680
681	681
682		-(((
683		-(% style="color:blue" %)**Step 2: **(%%) Open it and choose
684		-)))
	826	+=== 2.8.3  ​Battery Note ===
685	685
686		-* (((
687		-Product Model
688		-)))
689		-* (((
690		-Uplink Interval
691		-)))
692		-* (((
693		-Working Mode
694		-)))
695	695
696	696	(((
697		-And the Life expectation in difference case will be shown on the right.
	830	+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.
698	698	)))
699	699
700		-[[image:image-20220709110451-3.png]]
701	701
702	702
	835	+=== 2.8.4  Replace the battery ===
703	703
704		-=== 2.8.3  ​Battery Note ===
705	705
706	706	(((
707		-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.
	839	+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.
708	708	)))
709	709
710	710
711		-
712		-=== 2.8.4  Replace the battery ===
713		-
714	714	(((
715		-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).
	844	+The default battery pack of N95S31B 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).
716	716	)))
717	717
718	718
...	...	@@ -719,6 +719,7 @@
719	719
720	720	= 3. ​ Access NB-IoT Module =
721	721
	851	+
722	722	(((
723	723	Users can directly access the AT command set of the NB-IoT module.
724	724	)))
...	...	@@ -725,6 +725,8 @@
725	725
726	726	(((
727	727	The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]]
	858	+
	859	+
728	728	)))
729	729
730	730	[[image:1657333200519-600.png]]
...	...	@@ -733,11 +733,13 @@
733	733
734	734	= 4.  Using the AT Commands =
735	735
	868	+
736	736	== 4.1  Access AT Commands ==
737	737
738		-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/]]
739	739
	872	+See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]]
740	740
	874	+
741	741	AT+<CMD>?  : Help on <CMD>
742	742
743	743	AT+<CMD>         : Run <CMD>
...	...	@@ -777,7 +777,24 @@
777	777
778	778	AT+SERVADDR  : Server Address
779	779
	914	+AT+TR      : Get or Set record time
780	780
	916	+AT+APN     : Get or set the APN
	917	+
	918	+AT+FBAND   : Get or Set whether to automatically modify the frequency band
	919	+
	920	+AT+DNSCFG  : Get or Set DNS Server
	921	+
	922	+AT+GETSENSORVALUE   : Returns the current sensor measurement
	923	+
	924	+AT+NOUD      : Get or Set the number of data to be uploaded
	925	+
	926	+AT+CDP     : Read or Clear cached data
	927	+
	928	+AT+SHTEMP: Get or Set alarm of temp
	929	+
	930	+AT+SHHUM: Get or Set alarm of moisture
	931	+
781	781	(% style="color:#037691" %)**COAP Management**
782	782
783	783	AT+URI            : Resource parameters
...	...	@@ -811,6 +811,7 @@
811	811
812	812	= ​5.  FAQ =
813	813
	965	+
814	814	== 5.1 ​ How to Upgrade Firmware ==
815	815
816	816
...	...	@@ -823,13 +823,18 @@
823	823	)))
824	824
825	825	(((
826		-(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
	978	+
	979	+
	980	+(((
	981	+(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
827	827	)))
	983	+)))
828	828
829	829
830	830
831	831	= 6.  Trouble Shooting =
832	832
	989	+
833	833	== 6.1  ​Connection problem when uploading firmware ==
834	834
835	835
...	...	@@ -845,6 +845,7 @@
845	845
846	846	== 6.2  AT Command input doesn't work ==
847	847
	1005	+
848	848	(((
849	849	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.
850	850
...	...	@@ -855,7 +855,7 @@
855	855	= 7. ​ Order Info =
856	856
857	857
858		-Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
	1016	+Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
859	859
860	860
861	861	(% class="wikigeneratedid" %)
...	...	@@ -870,7 +870,7 @@
870	870
871	871	(% style="color:#037691" %)**Package Includes**:
872	872
873		-* NSE01 NB-IoT Distance Detect Sensor Node x 1
	1031	+* N95S31B NB-IoT Temperature and Humidity Sensor
874	874	* External antenna x 1
875	875	)))
876	876
...	...	@@ -879,11 +879,10 @@
879	879
880	880	(% style="color:#037691" %)**Dimension and weight**:
881	881
882		-
883	883	* Device Size: 13.0 x 5 x 4.5 cm
884	884	* Device Weight: 150g
885		-* Package Size / pcs : 15 x 12x 5.5 cm
886		-* Weight / pcs : 220g
	1042	+* Package Size / pcs : 14.0 x 8x 5 cm
	1043	+* Weight / pcs : 180g
887	887	)))
888	888
889	889	(((
...	...	@@ -895,5 +895,8 @@
895	895
896	896	= 9.  Support =
897	897
	1055	+
898	898	* 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.
899	899	* 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]]
	1058	+
	1059	+

1657350625843-586.png

Author

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

Size

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

Content

1657351240556-536.png

Author

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

Size

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

Content

1657351312545-300.png

Author

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

Size

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

Content

1657352146020-183.png

Author

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

Size

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

Content

1657352185396-303.png

Author

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

Size

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

Content

1657352391268-297.png

Author

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

Size

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

Content

1657352403317-397.png

Author

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

Size

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

Content

1657352634421-276.png

Author

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

Size

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

Content

1657352645687-385.png

Author

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

Size

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

Content

1657352898400-901.png

Author

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

Size

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

Content

1657352914475-252.png

Author

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

Size

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

Content

1657354294009-643.png

Author

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

Size

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

Content

1657520100595-569.png

Author

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

Size

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

Content

image-20220709161741-3.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+111.2 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