<
From version < 122.1 >
edited by David Huang
on 2022/09/08 16:31
To version < 115.5 >
edited by Xiaoling
on 2022/07/09 17:18
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.David
1 +XWiki.Xiaoling
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  )))
... ... @@ -56,7 +56,6 @@
56 56  
57 57  == 1.2 ​ Features ==
58 58  
59 -
60 60  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
61 61  * Monitor Temperature & Humidity via SHT31
62 62  * AT Commands to change parameters
... ... @@ -68,6 +68,9 @@
68 68  * Micro SIM card slot for NB-IoT SIM
69 69  * 8500mAh Battery for long term use
70 70  
55 +
56 +
57 +
71 71  == 1.3  Specification ==
72 72  
73 73  
... ... @@ -87,6 +87,7 @@
87 87  
88 88  (% style="color:#037691" %)**Battery:**
89 89  
77 +
90 90  * Li/SOCI2 un-chargeable battery
91 91  * Capacity: 8500mAh
92 92  * Self Discharge: <1% / Year @ 25°C
... ... @@ -93,9 +93,11 @@
93 93  * Max continuously current: 130mA
94 94  * Max boost current: 2A, 1 second
95 95  
96 -== ​1.4  Applications ==
97 97  
98 98  
86 +
87 +== ​1.4  Applications ==
88 +
99 99  * Smart Buildings & Home Automation
100 100  * Logistics and Supply Chain Management
101 101  * Smart Metering
... ... @@ -107,20 +107,15 @@
107 107  ​
108 108  
109 109  
100 +== 1.5  Pin Definitions ==
110 110  
111 -== 1.5  Pin Definitions & Switch ==
112 -
113 -
114 114  N95S31B use the mother board from NBSN95 which as below.
115 115  
116 -
117 117  [[image:image-20220709144723-1.png]]
118 118  
119 119  
120 -
121 121  === 1.5.1 Jumper JP2 ===
122 122  
123 -
124 124  Power on Device when put this jumper.
125 125  
126 126  
... ... @@ -127,20 +127,14 @@
127 127  
128 128  === 1.5.2 BOOT MODE / SW1 ===
129 129  
130 -
131 -(((
132 132  1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
133 -)))
134 134  
135 -(((
136 136  2) Flash: work mode, device starts to work and send out console output for further debug
137 -)))
138 138  
139 139  
140 140  
141 141  === 1.5.3 Reset Button ===
142 142  
143 -
144 144  Press to reboot the device.
145 145  
146 146  
... ... @@ -147,15 +147,14 @@
147 147  
148 148  === 1.5.4 LED ===
149 149  
150 -
151 151  It will flash:
152 152  
153 153  1. When boot the device in flash mode
154 154  1. Send an uplink packet
155 155  
134 +
156 156  = 2.  Use N95S31B to communicate with IoT Server =
157 157  
158 -
159 159  == 2.1  How it works ==
160 160  
161 161  
... ... @@ -172,7 +172,7 @@
172 172  
173 173  )))
174 174  
175 -[[image:1657520100595-569.png]]
153 +[[image:1657350248151-650.png]]
176 176  
177 177  (((
178 178  
... ... @@ -188,49 +188,26 @@
188 188  [[image:image-20220709150546-2.png]]
189 189  
190 190  
191 -
192 192  === 2.2.1 Test Requirement ===
193 193  
194 194  
195 -(((
196 196  To use N95S31B in your city, make sure meet below requirements:
197 -)))
198 198  
199 -* (((
200 -Your local operator has already distributed a NB-IoT Network there.
201 -)))
202 -* (((
203 -The local NB-IoT network used the band that N95S31B supports.
204 -)))
205 -* (((
206 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
207 -)))
174 +* Your local operator has already distributed a NB-IoT Network there.
175 +* The local NB-IoT network used the band that N95S31B supports.
176 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
208 208  
209 -(((
210 210  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
211 -)))
212 212  
213 -(((
214 214  N95S31B supports different communication protocol such as :
215 -)))
216 216  
217 217  (((
218 -* (((
219 -CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
220 -)))
221 -* (((
222 -raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
223 -)))
224 -* (((
225 -MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
226 -)))
227 -* (((
228 -TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
229 -)))
183 +* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
184 +* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
185 +* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
186 +* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
230 230  
231 -(((
232 232  We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server.
233 -)))
234 234  
235 235  
236 236  )))
... ... @@ -241,7 +241,6 @@
241 241  
242 242  === 2.2.3  Insert SIM card ===
243 243  
244 -
245 245  (((
246 246  Insert the NB-IoT Card get from your provider.
247 247  )))
... ... @@ -257,18 +257,14 @@
257 257  
258 258  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
259 259  
260 -
261 261  (((
262 262  (((
263 263  User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below.
264 -
265 -
266 266  )))
267 267  )))
268 268  
269 269  [[image:1657351312545-300.png]]
270 270  
271 -
272 272  **Connection:**
273 273  
274 274   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -292,9 +292,8 @@
292 292  
293 293  [[image:1657329814315-101.png]]
294 294  
295 -
296 296  (((
297 -(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**
246 +(% 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/]]
298 298  )))
299 299  
300 300  
... ... @@ -301,10 +301,9 @@
301 301  
302 302  === 2.2.5  Use CoAP protocol to uplink data ===
303 303  
253 +(% 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/]]
304 304  
305 -(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**
306 306  
307 -
308 308  (((
309 309  **Use below commands:**
310 310  )))
... ... @@ -352,7 +352,6 @@
352 352  
353 353  === 2.2.7  Use MQTT protocol to uplink data ===
354 354  
355 -
356 356  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
357 357  
358 358  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
... ... @@ -368,7 +368,6 @@
368 368  
369 369  [[image:1657352645687-385.png]]
370 370  
371 -
372 372  (((
373 373  To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period.
374 374  )))
... ... @@ -382,7 +382,6 @@
382 382  
383 383  === 2.2.8  Use TCP protocol to uplink data ===
384 384  
385 -
386 386  This feature is supported since firmware version v110
387 387  
388 388  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -397,7 +397,6 @@
397 397  
398 398  === 2.2.9  Change Update Interval ===
399 399  
400 -
401 401  User can use below command to change the (% style="color:green" %)**uplink interval**.
402 402  
403 403  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -406,96 +406,58 @@
406 406  
407 407  )))
408 408  
409 -(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
410 410  
411 -**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
412 412  
413 -
414 414  == 2.3  Uplink Payload ==
415 415  
416 416  
417 -(((
418 -N95S31B has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
419 -)))
358 +NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
420 420  
421 421  
422 -(((
423 423  For example:
424 -)))
425 425  
426 -(((
427 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
428 -)))
363 + (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
429 429  
430 430  
431 -(((
432 432  The uplink payloads are composed in  ASCII String. For example:
433 -)))
434 434  
435 -(((
436 436  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
437 -)))
438 438  
439 -(((
440 440  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
441 -)))
442 442  
443 443  
444 -(((
445 445  (% style="color:red" %)**NOTE:**
446 -)))
447 447  
448 448  (% style="color:red" %)
449 -1. (((
450 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
451 -)))
452 -1. (((
453 -**By default, the device will send an uplink message every 1 hour.**
376 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
377 +1. By default, the device will send an uplink message every 1 hour.
454 454  
455 455  
456 456  
457 -
458 -)))
459 -
460 460  === 2.3.1  Payload Analyze ===
461 461  
462 -
463 463  N95S31B uplink payload includes in total 21 bytes
464 464  
465 465  
466 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
386 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
467 467  |=(% style="width: 60px;" %)(((
468 468  **Size(bytes)**
469 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**
470 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
471 -(((
389 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1**
390 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
472 472  Reserve/ Same as NBSN95 CFGMOD=1
473 -)))
474 474  
475 -(((
476 476  No function here.
477 -)))
478 478  )))|(% style="width:77px" %)(((
479 -(((
480 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
481 -)))
395 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
482 482  
483 -(((
484 484  By SHT31
485 -)))
486 486  )))|(% style="width:80px" %)(((
487 -(((
488 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
489 -)))
399 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
490 490  
491 -(((
492 492  By SHT31
493 493  )))
494 -)))
495 495  
496 496  (((
497 -
498 -
499 499  (((
500 500  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
501 501  )))
... ... @@ -522,41 +522,12 @@
522 522  )))
523 523  
524 524  (((
525 -(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
431 +
526 526  )))
527 527  
528 -In this mode, uplink payload includes 91 bytes in total by default.
529 529  
530 -Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
531 -
532 -|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4
533 -|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp .....
534 -
535 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
536 -
537 -[[image:image-20220908154949-1.png]]
538 -
539 -The payload is ASCII string, representative same HEX:
540 -
541 -0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where:
542 -
543 -* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782
544 -* (% style="color:blue" %) Version: 0x000c=120=1.2
545 -* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V
546 -* (% style="color:red" %) Singal: 0x0c = 12
547 -* (% style="color:blue" %) Mod: 0x01 = 1
548 -* TemDS18B20: 0x0000= 0 = 0
549 -* (% style="color:green" %)Interrupt: 0x00= 0
550 -* (% style="color:green" %)adc: 0x0030= 48
551 -* SHTTEM: 0x0114= 276 = 27.6
552 -* SHTHUM:0x0231 =561=56.1%
553 -* (% style="color:red" %) Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
554 -* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
555 -* 8 sets of recorded data: SHTTEM(% style="color:red" %),SHTHUM,Time stamp : //**0113023163199c5e**//,.......
556 -
557 557  === 2.3.2  Device ID ===
558 558  
559 -
560 560  (((
561 561  By default, the Device ID equal to the last 6 bytes of IMEI.
562 562  )))
... ... @@ -575,44 +575,21 @@
575 575  
576 576  (((
577 577  The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
578 -
579 -
580 580  )))
581 581  
582 -(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
583 583  
584 584  
585 -By default, the Device ID equal to the last 15 bits of IMEI.
586 -
587 -User can use **AT+DEUI** to set Device ID
588 -
589 -**Example:**
590 -
591 -AT+DEUI=868411056754138
592 -
593 -
594 594  === 2.3.3  Version Info ===
595 595  
596 596  
597 -(((
598 598  These bytes include the hardware and software version.
599 -)))
600 600  
601 -(((
602 602  Higher byte: Specify hardware version: always 0x00 for N95S31B
603 -)))
604 604  
605 -(((
606 606  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
607 -)))
608 608  
609 -(((
610 -
611 -)))
612 612  
613 -(((
614 614  For example: 0x00 6E: this device is N95S31B with firmware version 110.
615 -)))
616 616  
617 617  (((
618 618  
... ... @@ -621,7 +621,6 @@
621 621  
622 622  === 2.3.4  Battery Info ===
623 623  
624 -
625 625  (((
626 626  Ex1: 0x0B45 = 2885mV
627 627  )))
... ... @@ -634,7 +634,6 @@
634 634  
635 635  === 2.3.5  Signal Strength ===
636 636  
637 -
638 638  (((
639 639  NB-IoT Network signal Strength.
640 640  )))
... ... @@ -667,7 +667,6 @@
667 667  
668 668  === 2.3.6  Temperature & Humidity ===
669 669  
670 -
671 671  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
672 672  
673 673  [[image:image-20220709161741-3.png]]
... ... @@ -684,11 +684,10 @@
684 684  
685 685  
686 686  
687 -== 2.4  Downlink Payload ==
538 +== 2.5  Downlink Payload ==
688 688  
540 +By default, NDDS75 prints the downlink payload to console port.
689 689  
690 -By default, N95S31B prints the downlink payload to console port.
691 -
692 692  [[image:image-20220709100028-1.png]]
693 693  
694 694  
... ... @@ -725,7 +725,7 @@
725 725  )))
726 726  
727 727  (((
728 -If payload = 0x04FF, it will reset the N95S31B
578 +If payload = 0x04FF, it will reset the NDDS75
729 729  )))
730 730  
731 731  
... ... @@ -736,61 +736,14 @@
736 736  )))
737 737  
738 738  
739 -== 2.5 Humidity and Temperature alarm function ==
740 740  
741 - AT Command:
590 +== 2.5  ​Battery Analysis ==
742 742  
743 -AT+ SHHUM=min,max
592 +=== 2.5.1  ​Battery Type ===
744 744  
745 -² When min=0, and max≠0, Alarm higher than max
746 746  
747 -² When min≠0, and max=0, Alarm lower than min
748 -
749 -² When min≠0 and max≠0, Alarm higher than max or lower than min
750 -
751 -Example:
752 -
753 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
754 -
755 -
756 -AT+ SHTEMP=min,max
757 -
758 -² When min=0, and max≠0, Alarm higher than max
759 -
760 -² When min≠0, and max=0, Alarm lower than min
761 -
762 -² When min≠0 and max≠0, Alarm higher than max or lower than min
763 -
764 -Example:
765 -
766 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
767 -
768 -== 2.6 Set the number of data to be uploaded and the recording time ==
769 -
770 -➢ AT Command:
771 -
772 -AT+TR=900  ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
773 -
774 -AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
775 -
776 -== 2.7 Read or Clear cached data ==
777 -
778 -➢ AT Command:
779 -
780 -AT+CDP ~/~/ Read cached data
781 -
782 -[[image:image-20220908163102-2.png]]
783 -
784 -AT+CDP=0 ~/~/ Clear cached data
785 -
786 -== 2.8  ​Battery Analysis ==
787 -
788 -
789 -=== 2.8.1  ​Battery Type ===
790 -
791 -
792 792  (((
793 -The N95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
596 +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.
794 794  )))
795 795  
796 796  (((
... ... @@ -813,35 +813,54 @@
813 813  
814 814  === 2.8.2  Power consumption Analyze ===
815 815  
619 +(((
620 +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.
621 +)))
816 816  
623 +
817 817  (((
818 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
625 +Instruction to use as below:
819 819  )))
820 820  
821 821  (((
822 -
629 +(% 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/]]
823 823  )))
824 824  
825 825  
826 -=== 2.8.3  ​Battery Note ===
633 +(((
634 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
635 +)))
827 827  
637 +* (((
638 +Product Model
639 +)))
640 +* (((
641 +Uplink Interval
642 +)))
643 +* (((
644 +Working Mode
645 +)))
828 828  
829 829  (((
830 -The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to uplink data, then the battery life may be decreased.
648 +And the Life expectation in difference case will be shown on the right.
831 831  )))
832 832  
651 +[[image:image-20220709110451-3.png]]
833 833  
834 834  
835 -=== 2.8.4  Replace the battery ===
836 836  
655 +=== 2.8.3  ​Battery Note ===
837 837  
838 838  (((
839 -You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
658 +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.
840 840  )))
841 841  
842 842  
662 +
663 +=== 2.8.4  Replace the battery ===
664 +
843 843  (((
844 -The default battery pack of N95S31B includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
666 +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).
845 845  )))
846 846  
847 847  
... ... @@ -848,7 +848,6 @@
848 848  
849 849  = 3. ​ Access NB-IoT Module =
850 850  
851 -
852 852  (((
853 853  Users can directly access the AT command set of the NB-IoT module.
854 854  )))
... ... @@ -855,8 +855,6 @@
855 855  
856 856  (((
857 857  The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
858 -
859 -
860 860  )))
861 861  
862 862  [[image:1657333200519-600.png]]
... ... @@ -865,13 +865,11 @@
865 865  
866 866  = 4.  Using the AT Commands =
867 867  
868 -
869 869  == 4.1  Access AT Commands ==
870 870  
689 +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/]]
871 871  
872 -See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]]
873 873  
874 -
875 875  AT+<CMD>?  : Help on <CMD>
876 876  
877 877  AT+<CMD>         : Run <CMD>
... ... @@ -911,24 +911,7 @@
911 911  
912 912  AT+SERVADDR  : Server Address
913 913  
914 -AT+TR      : Get or Set record time
915 915  
916 -AT+APN     : Get or set the APN
917 -
918 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
919 -
920 -AT+DNSCFG  : Get or Set DNS Server
921 -
922 -AT+GETSENSORVALUE   : Returns the current sensor measurement
923 -
924 -AT+NOUD      : Get or Set the number of data to be uploaded
925 -
926 -AT+CDP     : Read or Clear cached data
927 -
928 -AT+SHTEMP: Get or Set alarm of temp
929 -
930 -AT+SHHUM: Get or Set alarm of moisture
931 -
932 932  (% style="color:#037691" %)**COAP Management**      
933 933  
934 934  AT+URI            : Resource parameters
... ... @@ -962,7 +962,6 @@
962 962  
963 963  = ​5.  FAQ =
964 964  
965 -
966 966  == 5.1 ​ How to Upgrade Firmware ==
967 967  
968 968  
... ... @@ -975,18 +975,13 @@
975 975  )))
976 976  
977 977  (((
978 -
979 -
980 -(((
981 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
777 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
982 982  )))
983 -)))
984 984  
985 985  
986 986  
987 987  = 6.  Trouble Shooting =
988 988  
989 -
990 990  == 6.1  ​Connection problem when uploading firmware ==
991 991  
992 992  
... ... @@ -1002,7 +1002,6 @@
1002 1002  
1003 1003  == 6.2  AT Command input doesn't work ==
1004 1004  
1005 -
1006 1006  (((
1007 1007  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.
1008 1008  
... ... @@ -1013,7 +1013,7 @@
1013 1013  = 7. ​ Order Info =
1014 1014  
1015 1015  
1016 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
809 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1017 1017  
1018 1018  
1019 1019  (% class="wikigeneratedid" %)
... ... @@ -1028,7 +1028,7 @@
1028 1028  
1029 1029  (% style="color:#037691" %)**Package Includes**:
1030 1030  
1031 -* N95S31B NB-IoT Temperature and Humidity Sensor
824 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
1032 1032  * External antenna x 1
1033 1033  )))
1034 1034  
... ... @@ -1037,10 +1037,11 @@
1037 1037  
1038 1038  (% style="color:#037691" %)**Dimension and weight**:
1039 1039  
833 +
1040 1040  * Device Size: 13.0 x 5 x 4.5 cm
1041 1041  * Device Weight: 150g
1042 -* Package Size / pcs : 14.0 x 8x 5 cm
1043 -* Weight / pcs : 180g
836 +* Package Size / pcs : 15 x 12x 5.5 cm
837 +* Weight / pcs : 220g
1044 1044  )))
1045 1045  
1046 1046  (((
... ... @@ -1052,8 +1052,5 @@
1052 1052  
1053 1053  = 9.  Support =
1054 1054  
1055 -
1056 1056  * 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.
1057 1057  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
1058 -
1059 -
1657520100595-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
image-20220908154949-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -58.5 KB
Content
image-20220908163102-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -29.7 KB
Content
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0