Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 15 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

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	)))
...	...	@@ -55,6 +55,7 @@
55	55
56	56
57	57
	73	+
58	58	== 1.3  Specification ==
59	59
60	60
...	...	@@ -63,6 +63,8 @@
63	63	* Supply Voltage: 2.1v ~~ 3.6v
64	64	* Operating Temperature: -40 ~~ 85°C
65	65
	82	+
	83	+
66	66	(% style="color:#037691" %)**NB-IoT Spec:**
67	67
68	68	* - B1 @H-FDD: 2100MHz
...	...	@@ -72,9 +72,10 @@
72	72	* - B20 @H-FDD: 800MHz
73	73	* - B28 @H-FDD: 700MHz
74	74
75		-(% style="color:#037691" %)**Battery:**
76	76
77	77
	95	+(% style="color:#037691" %)**Battery:**
	96	+
78	78	* Li/SOCI2 un-chargeable battery
79	79	* Capacity: 8500mAh
80	80	* Self Discharge: <1% / Year @ 25°C
...	...	@@ -83,8 +83,10 @@
83	83
84	84
85	85
	105	+
86	86	== ​1.4  Applications ==
87	87
	108	+
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
	121	+== 1.5  Pin Definitions & Switch ==
	122	+
	123	+
101	101	N95S31B use the mother board from NBSN95 which as below.
102	102
	126	+
103	103	[[image:image-20220709144723-1.png]]
104	104
105	105
	130	+
106	106	=== 1.5.1 Jumper JP2 ===
107	107
	133	+
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
	140	+
	141	+(((
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.
	143	+)))
115	115
	145	+(((
116	116	2) Flash: work mode, device starts to work and send out console output for further debug
	147	+)))
117	117
118	118
119	119
120	120	=== 1.5.3 Reset Button ===
121	121
	153	+
122	122	Press to reboot the device.
123	123
124	124
...	...	@@ -125,6 +125,7 @@
125	125
126	126	=== 1.5.4 LED ===
127	127
	160	+
128	128	It will flash:
129	129
130	130	1. When boot the device in flash mode
...	...	@@ -135,6 +135,7 @@
135	135
136	136	= 2.  Use N95S31B to communicate with IoT Server =
137	137
	171	+
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]]
	188	+[[image:1657520100595-569.png]]
155	155
156	156	(((
157	157
...	...	@@ -167,42 +167,60 @@
167	167	[[image:image-20220709150546-2.png]]
168	168
169	169
	204	+
170	170	=== 2.2.1 Test Requirement ===
171	171
172	172
	208	+(((
173	173	To use N95S31B in your city, make sure meet below requirements:
	210	+)))
174	174
175		-* Your local operator has already distributed a NB-IoT Network there.
176		-* The local NB-IoT network used the band that N95S31B supports.
177		-* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	212	+* (((
	213	+Your local operator has already distributed a NB-IoT Network there.
	214	+)))
	215	+* (((
	216	+The local NB-IoT network used the band that N95S31B supports.
	217	+)))
	218	+* (((
	219	+Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	220	+)))
178	178
179		-
	222	+(((
180	180	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
	224	+)))
181	181
	226	+(((
182	182	N95S31B supports different communication protocol such as :
	228	+)))
183	183
184	184	(((
185		-* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
186		-* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
187		-* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
188		-* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	231	+* (((
	232	+CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
	233	+)))
	234	+* (((
	235	+raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
	236	+)))
	237	+* (((
	238	+MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
	239	+)))
	240	+* (((
	241	+TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	242	+)))
189	189
	244	+(((
190	190	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.
	246	+)))
191	191
192	192
193	193	)))
194	194
195		-(((
196		-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
197		-)))
	251	+[[image:1657350625843-586.png]]
198	198
199	199
200		-[[image:1657328756309-230.png]]
201	201
	255	+=== 2.2.3  Insert SIM card ===
202	202
203	203
204		-=== 2.2.2 Insert SIM card ===
205		-
206	206	(((
207	207	Insert the NB-IoT Card get from your provider.
208	208	)))
...	...	@@ -212,20 +212,24 @@
212	212	)))
213	213
214	214
215		-[[image:1657328884227-504.png]]
	267	+[[image:1657351240556-536.png]]
216	216
217	217
218	218
219		-=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
	271	+=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
220	220
	273	+
221	221	(((
222	222	(((
223		-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.
	276	+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.
	277	+
	278	+
224	224	)))
225	225	)))
226	226
227		-[[image:image-20220709092052-2.png]]
	282	+[[image:1657351312545-300.png]]
228	228
	284	+
229	229	**Connection:**
230	230
231	231	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
...	...	@@ -244,22 +244,24 @@
244	244	* Flow Control: (% style="color:green" %)**None**
245	245
246	246	(((
247		-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.
	303	+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.
248	248	)))
249	249
250	250	[[image:1657329814315-101.png]]
251	251
	308	+
252	252	(((
253		-(% 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/]]
	310	+(% 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]]**
254	254	)))
255	255
256	256
257	257
258		-=== 2.2.4 Use CoAP protocol to uplink data ===
	315	+=== 2.2.5  Use CoAP protocol to uplink data ===
259	259
260		-(% 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/]]
261	261
	318	+(% 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/]]**
262	262
	320	+
263	263	(((
264	264	**Use below commands:**
265	265	)))
...	...	@@ -275,10 +275,12 @@
275	275	)))
276	276
277	277	(((
	336	+
	337	+
278	278	For parameter description, please refer to AT command set
279	279	)))
280	280
281		-[[image:1657330452568-615.png]]
	341	+[[image:1657352146020-183.png]]
282	282
283	283
284	284	(((
...	...	@@ -285,11 +285,11 @@
285	285	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.
286	286	)))
287	287
288		-[[image:1657330472797-498.png]]
	348	+[[image:1657352185396-303.png]]
289	289
290	290
291	291
292		-=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
	352	+=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
293	293
294	294
295	295	* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
...	...	@@ -296,109 +296,117 @@
296	296	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
297	297	* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
298	298
299		-[[image:1657330501006-241.png]]
300	300
301	301
302		-[[image:1657330533775-472.png]]
	361	+[[image:1657352391268-297.png]]
303	303
304	304
	364	+[[image:1657352403317-397.png]]
305	305
306		-=== 2.2.6 Use MQTT protocol to uplink data ===
307	307
308	308
	368	+=== 2.2.7  Use MQTT protocol to uplink data ===
	369	+
	370	+
	371	+N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
	372	+
309	309	* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
310	310	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
311	311	* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
312	312	* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
313	313	* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
314		-* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
315		-* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
	378	+* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
	379	+* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
316	316
317		-[[image:1657249978444-674.png]]
318	318
319	319
320		-[[image:1657330723006-866.png]]
	383	+[[image:1657352634421-276.png]]
321	321
322	322
	386	+[[image:1657352645687-385.png]]
	387	+
	388	+
323	323	(((
324		-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.
	390	+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.
325	325	)))
326	326
327	327
	394	+(((
	395	+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.
	396	+)))
328	328
329		-=== 2.2.7 Use TCP protocol to uplink data ===
330	330
331	331
	400	+=== 2.2.8  Use TCP protocol to uplink data ===
	401	+
	402	+
	403	+This feature is supported since firmware version v110
	404	+
332	332	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
333	333	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
334	334
335		-[[image:image-20220709093918-1.png]]
336	336
337	337
338		-[[image:image-20220709093918-2.png]]
	410	+[[image:1657352898400-901.png]]
339	339
340	340
	413	+[[image:1657352914475-252.png]]
341	341
342		-=== 2.2.8 Change Update Interval ===
343	343
	416	+
	417	+=== 2.2.9  Change Update Interval ===
	418	+
	419	+
344	344	User can use below command to change the (% style="color:green" %)**uplink interval**.
345	345
346	346	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
347	347
348	348	(((
349		-(% style="color:red" %)**NOTE:**
	425	+
350	350	)))
351	351
352		-(((
353		-(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
354		-)))
355	355
356	356
357		-
358	358	== 2.3  Uplink Payload ==
359	359
360		-In this mode, uplink payload includes in total 14 bytes
361	361
	433	+(((
	434	+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.
	435	+)))
362	362
363		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
364		-|=(% style="width: 60px;" %)(((
365		-**Size(bytes)**
366		-)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
367		-|(% 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"]]
368	368
369	369	(((
370		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
	439	+For example:
371	371	)))
372	372
	442	+(((
	443	+ (% 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.
	444	+)))
373	373
374		-[[image:1657331036973-987.png]]
375	375
376	376	(((
377		-The payload is ASCII string, representative same HEX:
	448	+The uplink payloads are composed in  ASCII String. For example:
378	378	)))
379	379
380	380	(((
381		-0x72403155615900640c6c19029200 where:
	452	+0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
382	382	)))
383	383
384		-* (((
385		-Device ID: 0x724031556159 = 724031556159
	455	+(((
	456	+0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
386	386	)))
387		-* (((
388		-Version: 0x0064=100=1.0.0
	458	+
	459	+
	460	+(((
	461	+(% style="color:red" %)**NOTE:**
389	389	)))
390	390
391		-* (((
392		-BAT: 0x0c6c = 3180 mV = 3.180V
	464	+(% style="color:red" %)
	465	+1. (((
	466	+**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
393	393	)))
394		-* (((
395		-Signal: 0x19 = 25
396		-)))
397		-* (((
398		-Distance: 0x0292= 658 mm
399		-)))
400		-* (((
401		-Interrupt: 0x00 = 0
	468	+1. (((
	469	+**By default, the device will send an uplink message every 1 hour.**
402	402
403	403
404	404
...	...	@@ -405,105 +405,113 @@
405	405
406	406	)))
407	407
408		-== 2.4  Payload Explanation and Sensor Interface ==
	476	+=== 2.3.1  Payload Analyze ===
409	409
410	410
411		-=== 2.4.1  Device ID ===
	479	+N95S31B uplink payload includes in total 21 bytes
412	412
	481	+
	482	+(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
	483	+|=(% style="width: 60px;" %)(((
	484	+**Size(bytes)**
	485	+)))|=(% 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**
	486	+|(% 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" %)(((
413	413	(((
414		-By default, the Device ID equal to the last 6 bytes of IMEI.
	488	+Reserve/ Same as NBSN95 CFGMOD=1
415	415	)))
416	416
417	417	(((
418		-User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	492	+No function here.
419	419	)))
420		-
	494	+)))|(% style="width:77px" %)(((
421	421	(((
422		-**Example:**
	496	+[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
423	423	)))
424	424
425	425	(((
426		-AT+DEUI=A84041F15612
	500	+By SHT31
427	427	)))
428		-
	502	+)))|(% style="width:80px" %)(((
429	429	(((
430		-The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	504	+[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
431	431	)))
432	432
433		-
434		-
435		-=== 2.4.2  Version Info ===
436		-
437	437	(((
438		-Specify the software version: 0x64=100, means firmware version 1.00.
	508	+By SHT31
439	439	)))
	510	+)))
440	440
441	441	(((
442		-For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
	513	+
	514	+
	515	+(((
	516	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
443	443	)))
	518	+)))
444	444
445	445
	521	+[[image:1657354294009-643.png]]
446	446
447		-=== 2.4.3  Battery Info ===
448	448
	524	+The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
	525	+
	526	+* Device ID: 0x724031607457 = 724031607457
	527	+* Version: 0x006e=110=1.1.0
	528	+
	529	+* BAT: 0x0ccd = 3277 mV = 3.277V
	530	+* Signal: 0x1b = 27
	531	+* Model: 0x01 = 1
	532	+* 0x00dc000ccc= reserve, ignore in N95S31B
	533	+* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
	534	+* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
	535	+
449	449	(((
450		-Ex1: 0x0B45 = 2885mV
	537	+
451	451	)))
452	452
453	453	(((
454		-Ex2: 0x0B49 = 2889mV
	541	+
455	455	)))
456	456
457	457
	545	+=== 2.3.2  Device ID ===
458	458
459		-=== 2.4.4  Signal Strength ===
460	460
461	461	(((
462		-NB-IoT Network signal Strength.
	549	+By default, the Device ID equal to the last 6 bytes of IMEI.
463	463	)))
464	464
465	465	(((
466		-**Ex1: 0x1d = 29**
	553	+User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
467	467	)))
468	468
469	469	(((
470		-(% style="color:blue" %)**0**(%%)  -113dBm or less
	557	+**Example:**
471	471	)))
472	472
473	473	(((
474		-(% style="color:blue" %)**1**(%%)  -111dBm
	561	+AT+DEUI=A84041F15612
475	475	)))
476	476
477	477	(((
478		-(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
	565	+The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
479	479	)))
480	480
481		-(((
482		-(% style="color:blue" %)**31**  (%%) -51dBm or greater
483		-)))
484	484
485		-(((
486		-(% style="color:blue" %)**99**   (%%) Not known or not detectable
487		-)))
488	488
	570	+=== 2.3.3  Version Info ===
489	489
490	490
491		-=== 2.4.5  Distance ===
492		-
493		-Get the distance. Flat object range 280mm - 7500mm.
494		-
495	495	(((
496		-For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
	574	+These bytes include the hardware and software version.
497	497	)))
498	498
499	499	(((
500		-(((
501		-(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
	578	+Higher byte: Specify hardware version: always 0x00 for N95S31B
502	502	)))
503		-)))
504	504
505	505	(((
506		-
	582	+Lower byte: Specify the software version: 0x6E=110, means firmware version 110
507	507	)))
508	508
509	509	(((
...	...	@@ -510,65 +510,85 @@
510	510
511	511	)))
512	512
513		-=== 2.4.6  Digital Interrupt ===
514		-
515	515	(((
516		-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.
	590	+For example: 0x00 6E: this device is N95S31B with firmware version 110.
517	517	)))
518	518
519	519	(((
520		-The command is:
	594	+
521	521	)))
522	522
	597	+
	598	+=== 2.3.4  Battery Info ===
	599	+
	600	+
523	523	(((
524		-(% 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]])**.**
	602	+Ex1: 0x0B45 = 2885mV
525	525	)))
526	526
527		-
528	528	(((
529		-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.
	606	+Ex2: 0x0B49 = 2889mV
530	530	)))
531	531
532	532
	610	+
	611	+=== 2.3.5  Signal Strength ===
	612	+
	613	+
533	533	(((
534		-Example:
	615	+NB-IoT Network signal Strength.
535	535	)))
536	536
537	537	(((
538		-0x(00): Normal uplink packet.
	619	+**Ex1: 0x1d = 29**
539	539	)))
540	540
541	541	(((
542		-0x(01): Interrupt Uplink Packet.
	623	+(% style="color:blue" %)**0**(%%)  -113dBm or less
543	543	)))
544	544
545		-
546		-
547		-=== 2.4.7  ​+5V Output ===
548		-
549	549	(((
550		-NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
	627	+(% style="color:blue" %)**1**(%%)  -111dBm
551	551	)))
552	552
553		-
554	554	(((
555		-The 5V output time can be controlled by AT Command.
	631	+(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
556	556	)))
557	557
558	558	(((
559		-(% style="color:blue" %)**AT+5VT=1000**
	635	+(% style="color:blue" %)**31**  (%%) -51dBm or greater
560	560	)))
561	561
562	562	(((
563		-Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
	639	+(% style="color:blue" %)**99**   (%%) Not known or not detectable
564	564	)))
565	565
566	566
567	567
568		-== 2.5  Downlink Payload ==
	644	+=== 2.3.6  Temperature & Humidity ===
569	569
570		-By default, NDDS75 prints the downlink payload to console port.
571	571
	647	+The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
	648	+
	649	+[[image:image-20220709161741-3.png]]
	650	+
	651	+
	652	+Convert the read byte to decimal and divide it by ten.
	653	+
	654	+
	655	+**Example:**
	656	+
	657	+Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
	658	+
	659	+Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
	660	+
	661	+
	662	+
	663	+== 2.4  Downlink Payload ==
	664	+
	665	+
	666	+By default, N95S31B prints the downlink payload to console port.
	667	+
572	572	[[image:image-20220709100028-1.png]]
573	573
574	574
...	...	@@ -605,7 +605,7 @@
605	605	)))
606	606
607	607	(((
608		-If payload = 0x04FF, it will reset the NDDS75
	704	+If payload = 0x04FF, it will reset the N95S31B
609	609	)))
610	610
611	611
...	...	@@ -617,51 +617,17 @@
617	617
618	618
619	619
620		-== 2.6  ​LED Indicator ==
	716	+== 2.5  ​Battery Analysis ==
621	621
622	622
623		-The NDDS75 has an internal LED which is to show the status of different state.
	719	+=== 2.5.1  ​Battery Type ===
624	624
625	625
626		-* 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)
627		-* Then the LED will be on for 1 second means device is boot normally.
628		-* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
629		-* For each uplink probe, LED will be on for 500ms.
630		-
631	631	(((
632		-
	723	+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.
633	633	)))
634	634
635		-
636		-
637		-== 2.7  ​Firmware Change Log ==
638		-
639		-
640	640	(((
641		-Download URL & Firmware Change log
642		-)))
643		-
644		-(((
645		-[[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/]]
646		-)))
647		-
648		-
649		-(((
650		-Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
651		-)))
652		-
653		-
654		-
655		-== 2.8  ​Battery Analysis ==
656		-
657		-=== 2.8.1  ​Battery Type ===
658		-
659		-
660		-(((
661		-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.
662		-)))
663		-
664		-(((
665	665	The battery is designed to last for several years depends on the actually use environment and update interval.
666	666	)))
667	667
...	...	@@ -679,56 +679,37 @@
679	679
680	680
681	681
682		-=== 2.8.2  Power consumption Analyze ===
	744	+=== 2.5.2  Power consumption Analyze ===
683	683
684		-(((
685		-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.
686		-)))
687	687
688		-
689	689	(((
690		-Instruction to use as below:
	748	+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.
691	691	)))
692	692
693	693	(((
694		-(% 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/]]
	752	+
695	695	)))
696	696
697	697
698		-(((
699		-(% style="color:blue" %)**Step 2: **(%%) Open it and choose
700		-)))
	756	+=== 2.5.3  ​Battery Note ===
701	701
702		-* (((
703		-Product Model
704		-)))
705		-* (((
706		-Uplink Interval
707		-)))
708		-* (((
709		-Working Mode
710		-)))
711	711
712	712	(((
713		-And the Life expectation in difference case will be shown on the right.
	760	+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.
714	714	)))
715	715
716		-[[image:image-20220709110451-3.png]]
717	717
718	718
	765	+=== 2.5.4  Replace the battery ===
719	719
720		-=== 2.8.3  ​Battery Note ===
721	721
722	722	(((
723		-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.
	769	+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.
724	724	)))
725	725
726	726
727		-
728		-=== 2.8.4  Replace the battery ===
729		-
730	730	(((
731		-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).
	774	+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).
732	732	)))
733	733
734	734
...	...	@@ -735,6 +735,7 @@
735	735
736	736	= 3. ​ Access NB-IoT Module =
737	737
	781	+
738	738	(((
739	739	Users can directly access the AT command set of the NB-IoT module.
740	740	)))
...	...	@@ -741,6 +741,8 @@
741	741
742	742	(((
743	743	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/]]
	788	+
	789	+
744	744	)))
745	745
746	746	[[image:1657333200519-600.png]]
...	...	@@ -749,11 +749,13 @@
749	749
750	750	= 4.  Using the AT Commands =
751	751
	798	+
752	752	== 4.1  Access AT Commands ==
753	753
754		-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/]]
755	755
	802	+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]]
756	756
	804	+
757	757	AT+<CMD>?  : Help on <CMD>
758	758
759	759	AT+<CMD>         : Run <CMD>
...	...	@@ -827,6 +827,7 @@
827	827
828	828	= ​5.  FAQ =
829	829
	878	+
830	830	== 5.1 ​ How to Upgrade Firmware ==
831	831
832	832
...	...	@@ -839,13 +839,18 @@
839	839	)))
840	840
841	841	(((
842		-(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
	891	+
	892	+
	893	+(((
	894	+(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
843	843	)))
	896	+)))
844	844
845	845
846	846
847	847	= 6.  Trouble Shooting =
848	848
	902	+
849	849	== 6.1  ​Connection problem when uploading firmware ==
850	850
851	851
...	...	@@ -861,6 +861,7 @@
861	861
862	862	== 6.2  AT Command input doesn't work ==
863	863
	918	+
864	864	(((
865	865	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.
866	866
...	...	@@ -871,7 +871,7 @@
871	871	= 7. ​ Order Info =
872	872
873	873
874		-Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
	929	+Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
875	875
876	876
877	877	(% class="wikigeneratedid" %)
...	...	@@ -886,7 +886,7 @@
886	886
887	887	(% style="color:#037691" %)**Package Includes**:
888	888
889		-* NSE01 NB-IoT Distance Detect Sensor Node x 1
	944	+* N95S31B NB-IoT Temperature and Humidity Sensor
890	890	* External antenna x 1
891	891	)))
892	892
...	...	@@ -895,11 +895,10 @@
895	895
896	896	(% style="color:#037691" %)**Dimension and weight**:
897	897
898		-
899	899	* Device Size: 13.0 x 5 x 4.5 cm
900	900	* Device Weight: 150g
901		-* Package Size / pcs : 15 x 12x 5.5 cm
902		-* Weight / pcs : 220g
	955	+* Package Size / pcs : 14.0 x 8x 5 cm
	956	+* Weight / pcs : 180g
903	903	)))
904	904
905	905	(((
...	...	@@ -911,5 +911,9 @@
911	911
912	912	= 9.  Support =
913	913
	968	+
914	914	* 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.
915	915	* 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]]
	971	+
	972	+
	973	+

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