Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 3 removed)
  • 1657354294009-643.png
  • 1657520100595-569.png
  • image-20220709161741-3.png

Details

Page properties

Content

...	...	@@ -9,7 +9,6 @@
9	9
10	10	**Table of Contents:**
11	11
12		-{{toc/}}
13	13
14	14
15	15
...	...	@@ -17,35 +17,21 @@
17	17
18	18	= 1.  Introduction =
19	19
20		-
21	21	== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
22	22
23	23	(((
24	24
25	25
26		-(((
27	27	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		-)))
29	29
30		-(((
31	31	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		-)))
33	33
34		-(((
35	35	N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
36		-)))
37	37
38		-(((
39	39	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		-)))
41	41
42		-(((
43		-
44		-)))
45	45
46		-(((
47	47	~* make sure you have NB-IoT coverage locally.
48		-)))
49	49
50	50
51	51	)))
...	...	@@ -70,7 +70,6 @@
70	70
71	71
72	72
73		-
74	74	== 1.3  Specification ==
75	75
76	76
...	...	@@ -79,8 +79,6 @@
79	79	* Supply Voltage: 2.1v ~~ 3.6v
80	80	* Operating Temperature: -40 ~~ 85°C
81	81
82		-
83		-
84	84	(% style="color:#037691" %)**NB-IoT Spec:**
85	85
86	86	* - B1 @H-FDD: 2100MHz
...	...	@@ -90,10 +90,9 @@
90	90	* - B20 @H-FDD: 800MHz
91	91	* - B28 @H-FDD: 700MHz
92	92
93		-
94		-
95	95	(% style="color:#037691" %)**Battery:**
96	96
	77	+
97	97	* Li/SOCI2 un-chargeable battery
98	98	* Capacity: 8500mAh
99	99	* Self Discharge: <1% / Year @ 25°C
...	...	@@ -102,10 +102,8 @@
102	102
103	103
104	104
105		-
106	106	== ​1.4  Applications ==
107	107
108		-
109	109	* Smart Buildings & Home Automation
110	110	* Logistics and Supply Chain Management
111	111	* Smart Metering
...	...	@@ -117,20 +117,15 @@
117	117	​
118	118
119	119
	99	+== 1.5  Pin Definitions ==
120	120
121		-== 1.5  Pin Definitions & Switch ==
122		-
123		-
124	124	N95S31B use the mother board from NBSN95 which as below.
125	125
126		-
127	127	[[image:image-20220709144723-1.png]]
128	128
129	129
130		-
131	131	=== 1.5.1 Jumper JP2 ===
132	132
133		-
134	134	Power on Device when put this jumper.
135	135
136	136
...	...	@@ -137,20 +137,14 @@
137	137
138	138	=== 1.5.2 BOOT MODE / SW1 ===
139	139
140		-
141		-(((
142	142	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		-)))
144	144
145		-(((
146	146	2) Flash: work mode, device starts to work and send out console output for further debug
147		-)))
148	148
149	149
150	150
151	151	=== 1.5.3 Reset Button ===
152	152
153		-
154	154	Press to reboot the device.
155	155
156	156
...	...	@@ -157,7 +157,6 @@
157	157
158	158	=== 1.5.4 LED ===
159	159
160		-
161	161	It will flash:
162	162
163	163	1. When boot the device in flash mode
...	...	@@ -168,7 +168,6 @@
168	168
169	169	= 2.  Use N95S31B to communicate with IoT Server =
170	170
171		-
172	172	== 2.1  How it works ==
173	173
174	174
...	...	@@ -185,7 +185,7 @@
185	185
186	186	)))
187	187
188		-[[image:1657520100595-569.png]]
	154	+[[image:1657350248151-650.png]]
189	189
190	190	(((
191	191
...	...	@@ -201,49 +201,27 @@
201	201	[[image:image-20220709150546-2.png]]
202	202
203	203
204		-
205	205	=== 2.2.1 Test Requirement ===
206	206
207	207
208		-(((
209	209	To use N95S31B in your city, make sure meet below requirements:
210		-)))
211	211
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		-)))
	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.
221	221
222		-(((
	179	+
223	223	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
224		-)))
225	225
226		-(((
227	227	N95S31B supports different communication protocol such as :
228		-)))
229	229
230	230	(((
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		-)))
	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(%%))
243	243
244		-(((
245	245	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		-)))
247	247
248	248
249	249	)))
...	...	@@ -254,7 +254,6 @@
254	254
255	255	=== 2.2.3  Insert SIM card ===
256	256
257		-
258	258	(((
259	259	Insert the NB-IoT Card get from your provider.
260	260	)))
...	...	@@ -270,18 +270,14 @@
270	270
271	271	=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
272	272
273		-
274	274	(((
275	275	(((
276	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		-
279	279	)))
280	280	)))
281	281
282	282	[[image:1657351312545-300.png]]
283	283
284		-
285	285	**Connection:**
286	286
287	287	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
...	...	@@ -305,9 +305,8 @@
305	305
306	306	[[image:1657329814315-101.png]]
307	307
308		-
309	309	(((
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]]**
	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/]]
311	311	)))
312	312
313	313
...	...	@@ -314,10 +314,9 @@
314	314
315	315	=== 2.2.5  Use CoAP protocol to uplink data ===
316	316
	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/]]
317	317
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/]]**
319	319
320		-
321	321	(((
322	322	**Use below commands:**
323	323	)))
...	...	@@ -372,8 +372,8 @@
372	372	* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
373	373	* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
374	374	* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password 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
	312	+* (% style="color:blue" %)**AT+PUBTOPIC=f9527  **(%%)~/~/Set the sending topic of MQTT
	313	+* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527  **(%%) ~/~/Set the subscription topic of MQTT
377	377
378	378	[[image:1657352634421-276.png]]
379	379
...	...	@@ -419,44 +419,48 @@
419	419
420	420	== 2.3  Uplink Payload ==
421	421
	359	+In this mode, uplink payload includes in total 14 bytes
422	422
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		-)))
426	426
	362	+(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
	363	+|=(% style="width: 60px;" %)(((
	364	+**Size(bytes)**
	365	+)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
	366	+|(% 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"]]
427	427
428	428	(((
429		-For example:
	369	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
430	430	)))
431	431
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		-)))
435	435
	373	+[[image:1657331036973-987.png]]
436	436
437	437	(((
438		-The uplink payloads are composed in  ASCII String. For example:
	376	+The payload is ASCII string, representative same HEX:
439	439	)))
440	440
441	441	(((
442		-0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
	380	+0x72403155615900640c6c19029200 where:
443	443	)))
444	444
445		-(((
446		-0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
	383	+* (((
	384	+Device ID: 0x724031556159 = 724031556159
447	447	)))
448		-
449		-
450		-(((
451		-(% style="color:red" %)**NOTE:**
	386	+* (((
	387	+Version: 0x0064=100=1.0.0
452	452	)))
453	453
454		-(% style="color:red" %)
455		-1. (((
456		-All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
	390	+* (((
	391	+BAT: 0x0c6c = 3180 mV = 3.180V
457	457	)))
458		-1. (((
459		-By default, the device will send an uplink message every 1 hour.
	393	+* (((
	394	+Signal: 0x19 = 25
	395	+)))
	396	+* (((
	397	+Distance: 0x0292= 658 mm
	398	+)))
	399	+* (((
	400	+Interrupt: 0x00 = 0
460	460
461	461
462	462
...	...	@@ -463,108 +463,105 @@
463	463
464	464	)))
465	465
466		-=== 2.3.1  Payload Analyze ===
	407	+== 2.4  Payload Explanation and Sensor Interface ==
467	467
468		-N95S31B uplink payload includes in total 21 bytes
469	469
	410	+=== 2.4.1  Device ID ===
470	470
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" %)(((
476	476	(((
477		-Reserve/ Same as NBSN95 CFGMOD=1
	413	+By default, the Device ID equal to the last 6 bytes of IMEI.
478	478	)))
479	479
480	480	(((
481		-No function here.
	417	+User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
482	482	)))
483		-)))|(% style="width:77px" %)(((
	419	+
484	484	(((
485		-[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
	421	+**Example:**
486	486	)))
487	487
488	488	(((
489		-By SHT31
	425	+AT+DEUI=A84041F15612
490	490	)))
491		-)))|(% style="width:80px" %)(((
	427	+
492	492	(((
493		-[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
	429	+The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
494	494	)))
495	495
	432	+
	433	+
	434	+=== 2.4.2  Version Info ===
	435	+
496	496	(((
497		-By SHT31
	437	+Specify the software version: 0x64=100, means firmware version 1.00.
498	498	)))
499		-)))
500	500
501	501	(((
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.
	441	+For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
504	504	)))
505		-)))
506	506
507	507
508		-[[image:1657354294009-643.png]]
509	509
	446	+=== 2.4.3  Battery Info ===
510	510
511		-The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
	448	+(((
	449	+Ex1: 0x0B45 = 2885mV
	450	+)))
512	512
513		-* Device ID: 0x724031607457 = 724031607457
514		-* Version: 0x006e=110=1.1.0
	452	+(((
	453	+Ex2: 0x0B49 = 2889mV
	454	+)))
515	515
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
522	522
	457	+
	458	+=== 2.4.4  Signal Strength ===
	459	+
523	523	(((
524		-
	461	+NB-IoT Network signal Strength.
525	525	)))
526	526
527	527	(((
528		-
	465	+**Ex1: 0x1d = 29**
529	529	)))
530	530
531		-
532		-=== 2.3.2  Device ID ===
533		-
534	534	(((
535		-By default, the Device ID equal to the last 6 bytes of IMEI.
	469	+(% style="color:blue" %)**0**(%%)  -113dBm or less
536	536	)))
537	537
538	538	(((
539		-User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	473	+(% style="color:blue" %)**1**(%%)  -111dBm
540	540	)))
541	541
542	542	(((
543		-**Example:**
	477	+(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
544	544	)))
545	545
546	546	(((
547		-AT+DEUI=A84041F15612
	481	+(% style="color:blue" %)**31**  (%%) -51dBm or greater
548	548	)))
549	549
550	550	(((
551		-The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	485	+(% style="color:blue" %)**99**   (%%) Not known or not detectable
552	552	)))
553	553
554	554
555	555
556		-=== 2.3.3  Version Info ===
	490	+=== 2.4.5  Distance ===
557	557
	492	+Get the distance. Flat object range 280mm - 7500mm.
	493	+
558	558	(((
559		-These bytes include the hardware and software version.
	495	+For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
560	560	)))
561	561
562	562	(((
563		-Higher byte: Specify hardware version: always 0x00 for N95S31B
	499	+(((
	500	+(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
564	564	)))
	502	+)))
565	565
566	566	(((
567		-Lower byte: Specify the software version: 0x6E=110, means firmware version 110
	505	+
568	568	)))
569	569
570	570	(((
...	...	@@ -571,81 +571,65 @@
571	571
572	572	)))
573	573
	512	+=== 2.4.6  Digital Interrupt ===
	513	+
574	574	(((
575		-For example: 0x00 6E: this device is N95S31B with firmware version 110.
	515	+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.
576	576	)))
577	577
578	578	(((
579		-
	519	+The command is:
580	580	)))
581	581
582		-
583		-=== 2.3.4  Battery Info ===
584		-
585	585	(((
586		-Ex1: 0x0B45 = 2885mV
	523	+(% 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]])**.**
587	587	)))
588	588
	526	+
589	589	(((
590		-Ex2: 0x0B49 = 2889mV
	528	+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.
591	591	)))
592	592
593	593
594		-
595		-=== 2.3.5  Signal Strength ===
596		-
597	597	(((
598		-NB-IoT Network signal Strength.
	533	+Example:
599	599	)))
600	600
601	601	(((
602		-**Ex1: 0x1d = 29**
	537	+0x(00): Normal uplink packet.
603	603	)))
604	604
605	605	(((
606		-(% style="color:blue" %)**0**(%%)  -113dBm or less
	541	+0x(01): Interrupt Uplink Packet.
607	607	)))
608	608
	544	+
	545	+
	546	+=== 2.4.7  ​+5V Output ===
	547	+
609	609	(((
610		-(% style="color:blue" %)**1**(%%)  -111dBm
	549	+NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
611	611	)))
612	612
	552	+
613	613	(((
614		-(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
	554	+The 5V output time can be controlled by AT Command.
615	615	)))
616	616
617	617	(((
618		-(% style="color:blue" %)**31**  (%%) -51dBm or greater
	558	+(% style="color:blue" %)**AT+5VT=1000**
619	619	)))
620	620
621	621	(((
622		-(% style="color:blue" %)**99**   (%%) Not known or not detectable
	562	+Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
623	623	)))
624	624
625	625
626	626
627		-=== 2.3.6  Temperature & Humidity ===
	567	+== 2.5  Downlink Payload ==
628	628
629		-The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
	569	+By default, NDDS75 prints the downlink payload to console port.
630	630
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		-
649	649	[[image:image-20220709100028-1.png]]
650	650
651	651
...	...	@@ -682,7 +682,7 @@
682	682	)))
683	683
684	684	(((
685		-If payload = 0x04FF, it will reset the N95S31B
	607	+If payload = 0x04FF, it will reset the NDDS75
686	686	)))
687	687
688	688
...	...	@@ -694,16 +694,51 @@
694	694
695	695
696	696
697		-== 2.5  ​Battery Analysis ==
	619	+== 2.6  ​LED Indicator ==
698	698
699		-=== 2.5.1  ​Battery Type ===
700	700
	622	+The NDDS75 has an internal LED which is to show the status of different state.
701	701
	624	+
	625	+* 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)
	626	+* Then the LED will be on for 1 second means device is boot normally.
	627	+* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
	628	+* For each uplink probe, LED will be on for 500ms.
	629	+
702	702	(((
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.
	631	+
704	704	)))
705	705
	634	+
	635	+
	636	+== 2.7  ​Firmware Change Log ==
	637	+
	638	+
706	706	(((
	640	+Download URL & Firmware Change log
	641	+)))
	642	+
	643	+(((
	644	+[[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/]]
	645	+)))
	646	+
	647	+
	648	+(((
	649	+Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
	650	+)))
	651	+
	652	+
	653	+
	654	+== 2.8  ​Battery Analysis ==
	655	+
	656	+=== 2.8.1  ​Battery Type ===
	657	+
	658	+
	659	+(((
	660	+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.
	661	+)))
	662	+
	663	+(((
707	707	The battery is designed to last for several years depends on the actually use environment and update interval.
708	708	)))
709	709
...	...	@@ -721,35 +721,56 @@
721	721
722	722
723	723
724		-=== 2.5.2  Power consumption Analyze ===
	681	+=== 2.8.2  Power consumption Analyze ===
725	725
726	726	(((
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.
	684	+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.
728	728	)))
729	729
	687	+
730	730	(((
731		-
	689	+Instruction to use as below:
732	732	)))
733	733
	692	+(((
	693	+(% 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/]]
	694	+)))
734	734
735		-=== 2.5.3  ​Battery Note ===
736	736
737	737	(((
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.
	698	+(% style="color:blue" %)**Step 2: **(%%) Open it and choose
739	739	)))
740	740
	701	+* (((
	702	+Product Model
	703	+)))
	704	+* (((
	705	+Uplink Interval
	706	+)))
	707	+* (((
	708	+Working Mode
	709	+)))
741	741
	711	+(((
	712	+And the Life expectation in difference case will be shown on the right.
	713	+)))
742	742
743		-=== 2.5.4  Replace the battery ===
	715	+[[image:image-20220709110451-3.png]]
744	744
745	745
	718	+
	719	+=== 2.8.3  ​Battery Note ===
	720	+
746	746	(((
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.
	722	+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.
748	748	)))
749	749
750	750
	726	+
	727	+=== 2.8.4  Replace the battery ===
	728	+
751	751	(((
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).
	730	+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).
753	753	)))
754	754
755	755
...	...	@@ -772,7 +772,7 @@
772	772
773	773	== 4.1  Access AT Commands ==
774	774
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/]]
	753	+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/]]
776	776
777	777
778	778	AT+<CMD>?  : Help on <CMD>
...	...	@@ -860,12 +860,8 @@
860	860	)))
861	861
862	862	(((
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.
	841	+(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
867	867	)))
868		-)))
869	869
870	870
871	871
...	...	@@ -896,7 +896,7 @@
896	896	= 7. ​ Order Info =
897	897
898	898
899		-Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
	873	+Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
900	900
901	901
902	902	(% class="wikigeneratedid" %)
...	...	@@ -911,7 +911,7 @@
911	911
912	912	(% style="color:#037691" %)**Package Includes**:
913	913
914		-* N95S31B NB-IoT Temperature and Humidity Sensor
	888	+* NSE01 NB-IoT Distance Detect Sensor Node x 1
915	915	* External antenna x 1
916	916	)))
917	917
...	...	@@ -920,10 +920,11 @@
920	920
921	921	(% style="color:#037691" %)**Dimension and weight**:
922	922
	897	+
923	923	* Device Size: 13.0 x 5 x 4.5 cm
924	924	* Device Weight: 150g
925		-* Package Size / pcs : 14.0 x 8x 5 cm
926		-* Weight / pcs : 180g
	900	+* Package Size / pcs : 15 x 12x 5.5 cm
	901	+* Weight / pcs : 220g
927	927	)))
928	928
929	929	(((

1657354294009-643.png

Author

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

Size

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

Content

1657520100595-569.png

Author

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

Size

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

Content

image-20220709161741-3.png

Author

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

Size

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

Content