Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 5 added, 0 removed)
  • 1657352898400-901.png
  • 1657352914475-252.png
  • 1657354294009-643.png
  • 1657520100595-569.png
  • image-20220709161741-3.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
...	...	@@ -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,27 +167,49 @@
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	)))
...	...	@@ -198,6 +198,7 @@
198	198
199	199	=== 2.2.3  Insert SIM card ===
200	200
	257	+
201	201	(((
202	202	Insert the NB-IoT Card get from your provider.
203	203	)))
...	...	@@ -213,14 +213,18 @@
213	213
214	214	=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
215	215
	273	+
216	216	(((
217	217	(((
218	218	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	+
219	219	)))
220	220	)))
221	221
222	222	[[image:1657351312545-300.png]]
223	223
	284	+
224	224	**Connection:**
225	225
226	226	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
...	...	@@ -244,8 +244,9 @@
244	244
245	245	[[image:1657329814315-101.png]]
246	246
	308	+
247	247	(((
248		-(% 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/]]
	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]]**
249	249	)))
250	250
251	251
...	...	@@ -252,9 +252,10 @@
252	252
253	253	=== 2.2.5  Use CoAP protocol to uplink data ===
254	254
255		-(% 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/]]
256	256
	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/]]**
257	257
	320	+
258	258	(((
259	259	**Use below commands:**
260	260	)))
...	...	@@ -293,15 +293,16 @@
293	293	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
294	294	* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
295	295
296		-[[image:1657330501006-241.png]]
	359	+[[image:1657352391268-297.png]]
297	297
298	298
299		-[[image:1657330533775-472.png]]
	362	+[[image:1657352403317-397.png]]
300	300
301	301
302	302
303		-=== 2.2.6 Use MQTT protocol to uplink data ===
	366	+=== 2.2.7  Use MQTT protocol to uplink data ===
304	304
	368	+N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
305	305
306	306	* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
307	307	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
...	...	@@ -308,35 +308,40 @@
308	308	* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
309	309	* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
310	310	* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
311		-* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
312		-* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
	375	+* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
	376	+* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
313	313
314		-[[image:1657249978444-674.png]]
	378	+[[image:1657352634421-276.png]]
315	315
316	316
317		-[[image:1657330723006-866.png]]
	381	+[[image:1657352645687-385.png]]
318	318
	383	+(((
	384	+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.
	385	+)))
319	319
	387	+
320	320	(((
321		-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.
	389	+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.
322	322	)))
323	323
324	324
325	325
326		-=== 2.2.7 Use TCP protocol to uplink data ===
	394	+=== 2.2.8  Use TCP protocol to uplink data ===
327	327
	396	+This feature is supported since firmware version v110
328	328
329	329	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
330	330	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
331	331
332		-[[image:image-20220709093918-1.png]]
	401	+[[image:1657352898400-901.png]]
333	333
334	334
335		-[[image:image-20220709093918-2.png]]
	404	+[[image:1657352914475-252.png]]
336	336
337	337
338	338
339		-=== 2.2.8 Change Update Interval ===
	408	+=== 2.2.9  Change Update Interval ===
340	340
341	341	User can use below command to change the (% style="color:green" %)**uplink interval**.
342	342
...	...	@@ -343,59 +343,51 @@
343	343	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
344	344
345	345	(((
346		-(% style="color:red" %)**NOTE:**
	415	+
347	347	)))
348	348
349		-(((
350		-(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
351		-)))
352	352
353	353
354		-
355	355	== 2.3  Uplink Payload ==
356	356
357		-In this mode, uplink payload includes in total 14 bytes
358	358
	423	+(((
	424	+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.
	425	+)))
359	359
360		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
361		-|=(% style="width: 60px;" %)(((
362		-**Size(bytes)**
363		-)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
364		-|(% 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"]]
365	365
366	366	(((
367		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
	429	+For example:
368	368	)))
369	369
	432	+(((
	433	+ (% 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.
	434	+)))
370	370
371		-[[image:1657331036973-987.png]]
372	372
373	373	(((
374		-The payload is ASCII string, representative same HEX:
	438	+The uplink payloads are composed in  ASCII String. For example:
375	375	)))
376	376
377	377	(((
378		-0x72403155615900640c6c19029200 where:
	442	+0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
379	379	)))
380	380
381		-* (((
382		-Device ID: 0x724031556159 = 724031556159
	445	+(((
	446	+0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
383	383	)))
384		-* (((
385		-Version: 0x0064=100=1.0.0
	448	+
	449	+
	450	+(((
	451	+(% style="color:red" %)**NOTE:**
386	386	)))
387	387
388		-* (((
389		-BAT: 0x0c6c = 3180 mV = 3.180V
	454	+(% style="color:red" %)
	455	+1. (((
	456	+All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
390	390	)))
391		-* (((
392		-Signal: 0x19 = 25
393		-)))
394		-* (((
395		-Distance: 0x0292= 658 mm
396		-)))
397		-* (((
398		-Interrupt: 0x00 = 0
	458	+1. (((
	459	+By default, the device will send an uplink message every 1 hour.
399	399
400	400
401	401
...	...	@@ -402,105 +402,108 @@
402	402
403	403	)))
404	404
405		-== 2.4  Payload Explanation and Sensor Interface ==
	466	+=== 2.3.1  Payload Analyze ===
406	406
	468	+N95S31B uplink payload includes in total 21 bytes
407	407
408		-=== 2.4.1  Device ID ===
409	409
	471	+(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
	472	+|=(% style="width: 60px;" %)(((
	473	+**Size(bytes)**
	474	+)))|=(% 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**
	475	+|(% 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" %)(((
410	410	(((
411		-By default, the Device ID equal to the last 6 bytes of IMEI.
	477	+Reserve/ Same as NBSN95 CFGMOD=1
412	412	)))
413	413
414	414	(((
415		-User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	481	+No function here.
416	416	)))
417		-
	483	+)))|(% style="width:77px" %)(((
418	418	(((
419		-**Example:**
	485	+[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
420	420	)))
421	421
422	422	(((
423		-AT+DEUI=A84041F15612
	489	+By SHT31
424	424	)))
425		-
	491	+)))|(% style="width:80px" %)(((
426	426	(((
427		-The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	493	+[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
428	428	)))
429	429
430		-
431		-
432		-=== 2.4.2  Version Info ===
433		-
434	434	(((
435		-Specify the software version: 0x64=100, means firmware version 1.00.
	497	+By SHT31
436	436	)))
	499	+)))
437	437
438	438	(((
439		-For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
	502	+(((
	503	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
440	440	)))
	505	+)))
441	441
442	442
	508	+[[image:1657354294009-643.png]]
443	443
444		-=== 2.4.3  Battery Info ===
445	445
446		-(((
447		-Ex1: 0x0B45 = 2885mV
448		-)))
	511	+The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
449	449
450		-(((
451		-Ex2: 0x0B49 = 2889mV
452		-)))
	513	+* Device ID: 0x724031607457 = 724031607457
	514	+* Version: 0x006e=110=1.1.0
453	453
	516	+* BAT: 0x0ccd = 3277 mV = 3.277V
	517	+* Signal: 0x1b = 27
	518	+* Model: 0x01 = 1
	519	+* 0x00dc000ccc= reserve, ignore in N95S31B
	520	+* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
	521	+* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
454	454
455		-
456		-=== 2.4.4  Signal Strength ===
457		-
458	458	(((
459		-NB-IoT Network signal Strength.
	524	+
460	460	)))
461	461
462	462	(((
463		-**Ex1: 0x1d = 29**
	528	+
464	464	)))
465	465
	531	+
	532	+=== 2.3.2  Device ID ===
	533	+
466	466	(((
467		-(% style="color:blue" %)**0**(%%)  -113dBm or less
	535	+By default, the Device ID equal to the last 6 bytes of IMEI.
468	468	)))
469	469
470	470	(((
471		-(% style="color:blue" %)**1**(%%)  -111dBm
	539	+User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
472	472	)))
473	473
474	474	(((
475		-(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
	543	+**Example:**
476	476	)))
477	477
478	478	(((
479		-(% style="color:blue" %)**31**  (%%) -51dBm or greater
	547	+AT+DEUI=A84041F15612
480	480	)))
481	481
482	482	(((
483		-(% style="color:blue" %)**99**   (%%) Not known or not detectable
	551	+The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
484	484	)))
485	485
486	486
487	487
488		-=== 2.4.5  Distance ===
	556	+=== 2.3.3  Version Info ===
489	489
490		-Get the distance. Flat object range 280mm - 7500mm.
491		-
492	492	(((
493		-For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
	559	+These bytes include the hardware and software version.
494	494	)))
495	495
496	496	(((
497		-(((
498		-(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
	563	+Higher byte: Specify hardware version: always 0x00 for N95S31B
499	499	)))
500		-)))
501	501
502	502	(((
503		-
	567	+Lower byte: Specify the software version: 0x6E=110, means firmware version 110
504	504	)))
505	505
506	506	(((
...	...	@@ -507,65 +507,81 @@
507	507
508	508	)))
509	509
510		-=== 2.4.6  Digital Interrupt ===
511		-
512	512	(((
513		-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.
	575	+For example: 0x00 6E: this device is N95S31B with firmware version 110.
514	514	)))
515	515
516	516	(((
517		-The command is:
	579	+
518	518	)))
519	519
	582	+
	583	+=== 2.3.4  Battery Info ===
	584	+
520	520	(((
521		-(% 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]])**.**
	586	+Ex1: 0x0B45 = 2885mV
522	522	)))
523	523
524		-
525	525	(((
526		-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.
	590	+Ex2: 0x0B49 = 2889mV
527	527	)))
528	528
529	529
	594	+
	595	+=== 2.3.5  Signal Strength ===
	596	+
530	530	(((
531		-Example:
	598	+NB-IoT Network signal Strength.
532	532	)))
533	533
534	534	(((
535		-0x(00): Normal uplink packet.
	602	+**Ex1: 0x1d = 29**
536	536	)))
537	537
538	538	(((
539		-0x(01): Interrupt Uplink Packet.
	606	+(% style="color:blue" %)**0**(%%)  -113dBm or less
540	540	)))
541	541
542		-
543		-
544		-=== 2.4.7  ​+5V Output ===
545		-
546	546	(((
547		-NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
	610	+(% style="color:blue" %)**1**(%%)  -111dBm
548	548	)))
549	549
550		-
551	551	(((
552		-The 5V output time can be controlled by AT Command.
	614	+(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
553	553	)))
554	554
555	555	(((
556		-(% style="color:blue" %)**AT+5VT=1000**
	618	+(% style="color:blue" %)**31**  (%%) -51dBm or greater
557	557	)))
558	558
559	559	(((
560		-Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
	622	+(% style="color:blue" %)**99**   (%%) Not known or not detectable
561	561	)))
562	562
563	563
564	564
565		-== 2.5  Downlink Payload ==
	627	+=== 2.3.6  Temperature & Humidity ===
566	566
567		-By default, NDDS75 prints the downlink payload to console port.
	629	+The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
568	568
	631	+[[image:image-20220709161741-3.png]]
	632	+
	633	+
	634	+Convert the read byte to decimal and divide it by ten.
	635	+
	636	+
	637	+**Example:**
	638	+
	639	+Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
	640	+
	641	+Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
	642	+
	643	+
	644	+
	645	+== 2.4  Downlink Payload ==
	646	+
	647	+By default, N95S31B prints the downlink payload to console port.
	648	+
569	569	[[image:image-20220709100028-1.png]]
570	570
571	571
...	...	@@ -602,7 +602,7 @@
602	602	)))
603	603
604	604	(((
605		-If payload = 0x04FF, it will reset the NDDS75
	685	+If payload = 0x04FF, it will reset the N95S31B
606	606	)))
607	607
608	608
...	...	@@ -614,51 +614,16 @@
614	614
615	615
616	616
617		-== 2.6  ​LED Indicator ==
	697	+== 2.5  ​Battery Analysis ==
618	618
	699	+=== 2.5.1  ​Battery Type ===
619	619
620		-The NDDS75 has an internal LED which is to show the status of different state.
621	621
622		-
623		-* 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)
624		-* Then the LED will be on for 1 second means device is boot normally.
625		-* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
626		-* For each uplink probe, LED will be on for 500ms.
627		-
628	628	(((
629		-
	703	+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.
630	630	)))
631	631
632		-
633		-
634		-== 2.7  ​Firmware Change Log ==
635		-
636		-
637	637	(((
638		-Download URL & Firmware Change log
639		-)))
640		-
641		-(((
642		-[[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/]]
643		-)))
644		-
645		-
646		-(((
647		-Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
648		-)))
649		-
650		-
651		-
652		-== 2.8  ​Battery Analysis ==
653		-
654		-=== 2.8.1  ​Battery Type ===
655		-
656		-
657		-(((
658		-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.
659		-)))
660		-
661		-(((
662	662	The battery is designed to last for several years depends on the actually use environment and update interval.
663	663	)))
664	664
...	...	@@ -676,56 +676,35 @@
676	676
677	677
678	678
679		-=== 2.8.2  Power consumption Analyze ===
	724	+=== 2.5.2  Power consumption Analyze ===
680	680
681	681	(((
682		-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.
	727	+The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
683	683	)))
684	684
685		-
686	686	(((
687		-Instruction to use as below:
	731	+
688	688	)))
689	689
690		-(((
691		-(% 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/]]
692		-)))
693	693
	735	+=== 2.5.3  ​Battery Note ===
694	694
695	695	(((
696		-(% style="color:blue" %)**Step 2: **(%%) Open it and choose
	738	+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.
697	697	)))
698	698
699		-* (((
700		-Product Model
701		-)))
702		-* (((
703		-Uplink Interval
704		-)))
705		-* (((
706		-Working Mode
707		-)))
708	708
709		-(((
710		-And the Life expectation in difference case will be shown on the right.
711		-)))
712	712
713		-[[image:image-20220709110451-3.png]]
	743	+=== 2.5.4  Replace the battery ===
714	714
715	715
716		-
717		-=== 2.8.3  ​Battery Note ===
718		-
719	719	(((
720		-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.
	747	+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.
721	721	)))
722	722
723	723
724		-
725		-=== 2.8.4  Replace the battery ===
726		-
727	727	(((
728		-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).
	752	+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).
729	729	)))
730	730
731	731
...	...	@@ -748,7 +748,7 @@
748	748
749	749	== 4.1  Access AT Commands ==
750	750
751		-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/]]
	775	+See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]
752	752
753	753
754	754	AT+<CMD>?  : Help on <CMD>
...	...	@@ -836,8 +836,12 @@
836	836	)))
837	837
838	838	(((
839		-(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
	863	+
	864	+
	865	+(((
	866	+(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
840	840	)))
	868	+)))
841	841
842	842
843	843
...	...	@@ -868,7 +868,7 @@
868	868	= 7. ​ Order Info =
869	869
870	870
871		-Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
	899	+Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
872	872
873	873
874	874	(% class="wikigeneratedid" %)
...	...	@@ -883,7 +883,7 @@
883	883
884	884	(% style="color:#037691" %)**Package Includes**:
885	885
886		-* NSE01 NB-IoT Distance Detect Sensor Node x 1
	914	+* N95S31B NB-IoT Temperature and Humidity Sensor
887	887	* External antenna x 1
888	888	)))
889	889
...	...	@@ -892,11 +892,10 @@
892	892
893	893	(% style="color:#037691" %)**Dimension and weight**:
894	894
895		-
896	896	* Device Size: 13.0 x 5 x 4.5 cm
897	897	* Device Weight: 150g
898		-* Package Size / pcs : 15 x 12x 5.5 cm
899		-* Weight / pcs : 220g
	925	+* Package Size / pcs : 14.0 x 8x 5 cm
	926	+* Weight / pcs : 180g
900	900	)))
901	901
902	902	(((

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