Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 125.2 >
edited by Xiaoling
on 2022/09/09 15:51
To version < 115.3 >
edited by Xiaoling
on 2022/07/09 16:59
>
Change comment: There is no comment for this version

Summary

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  )))
... ... @@ -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
... ... @@ -70,6 +70,7 @@
70 70  
71 71  
72 72  
57 +
73 73  == 1.3  Specification ==
74 74  
75 75  
... ... @@ -89,6 +89,7 @@
89 89  
90 90  (% style="color:#037691" %)**Battery:**
91 91  
77 +
92 92  * Li/SOCI2 un-chargeable battery
93 93  * Capacity: 8500mAh
94 94  * Self Discharge: <1% / Year @ 25°C
... ... @@ -97,9 +97,9 @@
97 97  
98 98  
99 99  
86 +
100 100  == ​1.4  Applications ==
101 101  
102 -
103 103  * Smart Buildings & Home Automation
104 104  * Logistics and Supply Chain Management
105 105  * Smart Metering
... ... @@ -111,21 +111,15 @@
111 111  ​
112 112  
113 113  
100 +== 1.5  Pin Definitions ==
114 114  
115 -
116 -== 1.5  Pin Definitions & Switch ==
117 -
118 -
119 119  N95S31B use the mother board from NBSN95 which as below.
120 120  
121 -
122 122  [[image:image-20220709144723-1.png]]
123 123  
124 124  
125 -
126 126  === 1.5.1 Jumper JP2 ===
127 127  
128 -
129 129  Power on Device when put this jumper.
130 130  
131 131  
... ... @@ -132,20 +132,14 @@
132 132  
133 133  === 1.5.2 BOOT MODE / SW1 ===
134 134  
135 -
136 -(((
137 137  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.
138 -)))
139 139  
140 -(((
141 141  2) Flash: work mode, device starts to work and send out console output for further debug
142 -)))
143 143  
144 144  
145 145  
146 146  === 1.5.3 Reset Button ===
147 147  
148 -
149 149  Press to reboot the device.
150 150  
151 151  
... ... @@ -152,7 +152,6 @@
152 152  
153 153  === 1.5.4 LED ===
154 154  
155 -
156 156  It will flash:
157 157  
158 158  1. When boot the device in flash mode
... ... @@ -159,10 +159,8 @@
159 159  1. Send an uplink packet
160 160  
161 161  
162 -
163 163  = 2.  Use N95S31B to communicate with IoT Server =
164 164  
165 -
166 166  == 2.1  How it works ==
167 167  
168 168  
... ... @@ -179,7 +179,7 @@
179 179  
180 180  )))
181 181  
182 -[[image:1657520100595-569.png]]
153 +[[image:1657350248151-650.png]]
183 183  
184 184  (((
185 185  
... ... @@ -195,49 +195,26 @@
195 195  [[image:image-20220709150546-2.png]]
196 196  
197 197  
198 -
199 199  === 2.2.1 Test Requirement ===
200 200  
201 201  
202 -(((
203 203  To use N95S31B in your city, make sure meet below requirements:
204 -)))
205 205  
206 -* (((
207 -Your local operator has already distributed a NB-IoT Network there.
208 -)))
209 -* (((
210 -The local NB-IoT network used the band that N95S31B supports.
211 -)))
212 -* (((
213 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
214 -)))
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.
215 215  
216 -(((
217 217  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
218 -)))
219 219  
220 -(((
221 221  N95S31B supports different communication protocol such as :
222 -)))
223 223  
224 224  (((
225 -* (((
226 -CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
227 -)))
228 -* (((
229 -raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
230 -)))
231 -* (((
232 -MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
233 -)))
234 -* (((
235 -TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
236 -)))
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(%%))
237 237  
238 -(((
239 239  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.
240 -)))
241 241  
242 242  
243 243  )))
... ... @@ -248,7 +248,6 @@
248 248  
249 249  === 2.2.3  Insert SIM card ===
250 250  
251 -
252 252  (((
253 253  Insert the NB-IoT Card get from your provider.
254 254  )))
... ... @@ -264,18 +264,14 @@
264 264  
265 265  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
266 266  
267 -
268 268  (((
269 269  (((
270 270  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.
271 -
272 -
273 273  )))
274 274  )))
275 275  
276 276  [[image:1657351312545-300.png]]
277 277  
278 -
279 279  **Connection:**
280 280  
281 281   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -299,9 +299,8 @@
299 299  
300 300  [[image:1657329814315-101.png]]
301 301  
302 -
303 303  (((
304 -(% 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/]]
305 305  )))
306 306  
307 307  
... ... @@ -308,10 +308,9 @@
308 308  
309 309  === 2.2.5  Use CoAP protocol to uplink data ===
310 310  
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/]]
311 311  
312 -(% 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/]]**
313 313  
314 -
315 315  (((
316 316  **Use below commands:**
317 317  )))
... ... @@ -359,7 +359,6 @@
359 359  
360 360  === 2.2.7  Use MQTT protocol to uplink data ===
361 361  
362 -
363 363  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
364 364  
365 365  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
... ... @@ -375,7 +375,6 @@
375 375  
376 376  [[image:1657352645687-385.png]]
377 377  
378 -
379 379  (((
380 380  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.
381 381  )))
... ... @@ -389,7 +389,6 @@
389 389  
390 390  === 2.2.8  Use TCP protocol to uplink data ===
391 391  
392 -
393 393  This feature is supported since firmware version v110
394 394  
395 395  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -404,7 +404,6 @@
404 404  
405 405  === 2.2.9  Change Update Interval ===
406 406  
407 -
408 408  User can use below command to change the (% style="color:green" %)**uplink interval**.
409 409  
410 410  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -413,104 +413,58 @@
413 413  
414 414  )))
415 415  
416 -(((
417 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
418 -)))
419 419  
420 -(((
421 -(% style="color:red" %)**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).**
422 -)))
423 423  
424 -
425 -
426 426  == 2.3  Uplink Payload ==
427 427  
428 428  
429 -(((
430 -N95S31B has different working modes for the connections of different types 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.
431 -)))
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.
432 432  
433 433  
434 -(((
435 435  For example:
436 -)))
437 437  
438 -(((
439 - (% 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.
440 -)))
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.
441 441  
442 442  
443 -(((
444 444  The uplink payloads are composed in  ASCII String. For example:
445 -)))
446 446  
447 -(((
448 448  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
449 -)))
450 450  
451 -(((
452 452  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
453 -)))
454 454  
455 455  
456 -(((
457 457  (% style="color:red" %)**NOTE:**
458 -)))
459 459  
460 460  (% style="color:red" %)
461 -1. (((
462 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
463 -)))
464 -1. (((
465 -**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.
466 466  
467 467  
468 468  
469 -
470 -)))
471 -
472 472  === 2.3.1  Payload Analyze ===
473 473  
474 -
475 -==== 2.3.1.1  Before Firmware v1.2 ====
476 -
477 -
478 478  N95S31B uplink payload includes in total 21 bytes
479 479  
480 480  
481 -(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %)
386 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
482 482  |=(% style="width: 60px;" %)(((
483 483  **Size(bytes)**
484 -)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 174px;" %)5|=(% style="width: 106px;" %)**2**|=(% style="width: 85px;" %)**2**
485 -|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:174px" %)(((
486 -(((
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" %)(((
487 487  Reserve/ Same as NBSN95 CFGMOD=1
488 -)))
489 489  
490 -(((
491 491  No function here.
492 -)))
493 -)))|(% style="width:106px" %)(((
494 -(((
495 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
496 -)))
394 +)))|(% style="width:77px" %)(((
395 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
497 497  
498 -(((
499 499  By SHT31
500 -)))
501 -)))|(% style="width:85px" %)(((
502 -(((
503 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
504 -)))
398 +)))|(% style="width:80px" %)(((
399 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
505 505  
506 -(((
507 507  By SHT31
508 508  )))
509 -)))
510 510  
511 511  (((
512 -
513 -
514 514  (((
515 515  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
516 516  )))
... ... @@ -522,63 +522,27 @@
522 522  
523 523  The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
524 524  
525 -* Device ID:  0x724031607457 = 724031607457
416 +* Device ID: 0x724031607457 = 724031607457
417 +* Version: 0x006e=110=1.1.0
526 526  
527 -* Version:  0x006e=110=1.1.0
528 -
529 -* BAT:  0x0ccd = 3277 mV = 3.277V
530 -
531 -* Signal:  0x1b = 27
532 -
533 -* Model:  0x01 = 1
534 -
419 +* BAT: 0x0ccd = 3277 mV = 3.277V
420 +* Signal: 0x1b = 27
421 +* Model: 0x01 = 1
535 535  * 0x00dc000ccc= reserve, ignore in N95S31B
423 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
424 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
536 536  
537 -* Temperature by SHT31:  0x00e1 = 225 = 22.5 °C
538 -
539 -* Humidity by SHT31:  0x0186 = 390 = 39.0 %rh
540 -
541 541  (((
542 542  
428 +)))
543 543  
544 -
430 +(((
545 545  
546 546  )))
547 547  
548 -==== 2.3.1.2 Since Firmware v1.2 ====
549 549  
550 -In this mode, uplink payload includes 91 bytes in total by default.
551 -
552 -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.
553 -
554 -|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4
555 -|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp .....
556 -
557 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
558 -
559 -[[image:image-20220908154949-1.png]]
560 -
561 -The payload is ASCII string, representative same HEX:
562 -
563 -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:
564 -
565 -* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782
566 -* (% style="color:blue" %) Version: 0x000c=120=1.2
567 -* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V
568 -* (% style="color:red" %) Singal: 0x0c = 12
569 -* (% style="color:blue" %) Mod: 0x01 = 1
570 -* TemDS18B20: 0x0000= 0 = 0
571 -* (% style="color:green" %)Interrupt: 0x00= 0
572 -* (% style="color:green" %)adc: 0x0030= 48
573 -* SHTTEM: 0x0114= 276 = 27.6
574 -* SHTHUM:0x0231 =561=56.1%
575 -* (% style="color:red" %) Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
576 -* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
577 -* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,.......
578 -
579 579  === 2.3.2  Device ID ===
580 580  
581 -
582 582  (((
583 583  By default, the Device ID equal to the last 6 bytes of IMEI.
584 584  )))
... ... @@ -597,44 +597,21 @@
597 597  
598 598  (((
599 599  The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
600 -
601 -
602 602  )))
603 603  
604 -(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
605 605  
606 606  
607 -By default, the Device ID equal to the last 15 bits of IMEI.
608 -
609 -User can use **AT+DEUI** to set Device ID
610 -
611 -**Example:**
612 -
613 -AT+DEUI=868411056754138
614 -
615 -
616 616  === 2.3.3  Version Info ===
617 617  
618 618  
619 -(((
620 620  These bytes include the hardware and software version.
621 -)))
622 622  
623 -(((
624 624  Higher byte: Specify hardware version: always 0x00 for N95S31B
625 -)))
626 626  
627 -(((
628 628  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
629 -)))
630 630  
631 -(((
632 -
633 -)))
634 634  
635 -(((
636 636  For example: 0x00 6E: this device is N95S31B with firmware version 110.
637 -)))
638 638  
639 639  (((
640 640  
... ... @@ -643,7 +643,6 @@
643 643  
644 644  === 2.3.4  Battery Info ===
645 645  
646 -
647 647  (((
648 648  Ex1: 0x0B45 = 2885mV
649 649  )))
... ... @@ -656,7 +656,6 @@
656 656  
657 657  === 2.3.5  Signal Strength ===
658 658  
659 -
660 660  (((
661 661  NB-IoT Network signal Strength.
662 662  )))
... ... @@ -689,7 +689,6 @@
689 689  
690 690  === 2.3.6  Temperature & Humidity ===
691 691  
692 -
693 693  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
694 694  
695 695  [[image:image-20220709161741-3.png]]
... ... @@ -706,11 +706,10 @@
706 706  
707 707  
708 708  
709 -== 2.4  Downlink Payload ==
538 +== 2.5  Downlink Payload ==
710 710  
540 +By default, NDDS75 prints the downlink payload to console port.
711 711  
712 -By default, N95S31B prints the downlink payload to console port.
713 -
714 714  [[image:image-20220709100028-1.png]]
715 715  
716 716  
... ... @@ -747,7 +747,7 @@
747 747  )))
748 748  
749 749  (((
750 -If payload = 0x04FF, it will reset the N95S31B
578 +If payload = 0x04FF, it will reset the NDDS75
751 751  )))
752 752  
753 753  
... ... @@ -758,61 +758,49 @@
758 758  )))
759 759  
760 760  
761 -== 2.5 Humidity and Temperature alarm function ==
762 762  
763 -➢ AT Command:
590 +== 2.6  ​LED Indicator ==
764 764  
765 -AT+ SHHUM=min,max
766 766  
767 -² When min=0, and max≠0, Alarm higher than max
593 +The NDDS75 has an internal LED which is to show the status of different state.
768 768  
769 -² When min≠0, and max=0, Alarm lower than min
770 770  
771 -² When min≠0 and max≠0, Alarm higher than max or lower than min
596 +* 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)
597 +* Then the LED will be on for 1 second means device is boot normally.
598 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
599 +* For each uplink probe, LED will be on for 500ms.
772 772  
773 -Example:
601 +(((
602 +
603 +)))
774 774  
775 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
776 776  
777 777  
778 -AT+ SHTEMP=min,max
607 +== 2.7  ​Firmware Change Log ==
779 779  
780 -² When min=0, and max≠0, Alarm higher than max
781 781  
782 -² When min≠0, and max=0, Alarm lower than min
610 +(((
611 +Download URL & Firmware Change log
612 +)))
783 783  
784 -² When min≠0 and max≠0, Alarm higher than max or lower than min
614 +(((
615 +[[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/]]
616 +)))
785 785  
786 -Example:
787 787  
788 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
619 +(((
620 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
621 +)))
789 789  
790 -== 2.6 Set the number of data to be uploaded and the recording time ==
791 791  
792 -➢ AT Command:
793 793  
794 -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)
795 -
796 -AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
797 -
798 -== 2.7 Read or Clear cached data ==
799 -
800 -➢ AT Command:
801 -
802 -AT+CDP ~/~/ Read cached data
803 -
804 -[[image:image-20220908163102-2.png]]
805 -
806 -AT+CDP=0 ~/~/ Clear cached data
807 -
808 808  == 2.8  ​Battery Analysis ==
809 809  
810 -
811 811  === 2.8.1  ​Battery Type ===
812 812  
813 813  
814 814  (((
815 -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 +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.
816 816  )))
817 817  
818 818  (((
... ... @@ -835,35 +835,54 @@
835 835  
836 836  === 2.8.2  Power consumption Analyze ===
837 837  
654 +(((
655 +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.
656 +)))
838 838  
658 +
839 839  (((
840 -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.
660 +Instruction to use as below:
841 841  )))
842 842  
843 843  (((
844 -
664 +(% 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/]]
845 845  )))
846 846  
847 847  
848 -=== 2.8.3  ​Battery Note ===
668 +(((
669 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
670 +)))
849 849  
672 +* (((
673 +Product Model
674 +)))
675 +* (((
676 +Uplink Interval
677 +)))
678 +* (((
679 +Working Mode
680 +)))
850 850  
851 851  (((
852 -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.
683 +And the Life expectation in difference case will be shown on the right.
853 853  )))
854 854  
686 +[[image:image-20220709110451-3.png]]
855 855  
856 856  
857 -=== 2.8.4  Replace the battery ===
858 858  
690 +=== 2.8.3  ​Battery Note ===
859 859  
860 860  (((
861 -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.
693 +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.
862 862  )))
863 863  
864 864  
697 +
698 +=== 2.8.4  Replace the battery ===
699 +
865 865  (((
866 -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).
701 +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).
867 867  )))
868 868  
869 869  
... ... @@ -870,7 +870,6 @@
870 870  
871 871  = 3. ​ Access NB-IoT Module =
872 872  
873 -
874 874  (((
875 875  Users can directly access the AT command set of the NB-IoT module.
876 876  )))
... ... @@ -877,8 +877,6 @@
877 877  
878 878  (((
879 879  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/]] 
880 -
881 -
882 882  )))
883 883  
884 884  [[image:1657333200519-600.png]]
... ... @@ -887,13 +887,11 @@
887 887  
888 888  = 4.  Using the AT Commands =
889 889  
890 -
891 891  == 4.1  Access AT Commands ==
892 892  
724 +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/]]
893 893  
894 -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]]
895 895  
896 -
897 897  AT+<CMD>?  : Help on <CMD>
898 898  
899 899  AT+<CMD>         : Run <CMD>
... ... @@ -933,24 +933,7 @@
933 933  
934 934  AT+SERVADDR  : Server Address
935 935  
936 -AT+TR      : Get or Set record time
937 937  
938 -AT+APN     : Get or set the APN
939 -
940 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
941 -
942 -AT+DNSCFG  : Get or Set DNS Server
943 -
944 -AT+GETSENSORVALUE   : Returns the current sensor measurement
945 -
946 -AT+NOUD      : Get or Set the number of data to be uploaded
947 -
948 -AT+CDP     : Read or Clear cached data
949 -
950 -AT+SHTEMP: Get or Set alarm of temp
951 -
952 -AT+SHHUM: Get or Set alarm of moisture
953 -
954 954  (% style="color:#037691" %)**COAP Management**      
955 955  
956 956  AT+URI            : Resource parameters
... ... @@ -984,7 +984,6 @@
984 984  
985 985  = ​5.  FAQ =
986 986  
987 -
988 988  == 5.1 ​ How to Upgrade Firmware ==
989 989  
990 990  
... ... @@ -997,18 +997,13 @@
997 997  )))
998 998  
999 999  (((
1000 -
1001 -
1002 -(((
1003 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
812 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
1004 1004  )))
1005 -)))
1006 1006  
1007 1007  
1008 1008  
1009 1009  = 6.  Trouble Shooting =
1010 1010  
1011 -
1012 1012  == 6.1  ​Connection problem when uploading firmware ==
1013 1013  
1014 1014  
... ... @@ -1024,7 +1024,6 @@
1024 1024  
1025 1025  == 6.2  AT Command input doesn't work ==
1026 1026  
1027 -
1028 1028  (((
1029 1029  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.
1030 1030  
... ... @@ -1035,7 +1035,7 @@
1035 1035  = 7. ​ Order Info =
1036 1036  
1037 1037  
1038 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
844 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1039 1039  
1040 1040  
1041 1041  (% class="wikigeneratedid" %)
... ... @@ -1050,7 +1050,7 @@
1050 1050  
1051 1051  (% style="color:#037691" %)**Package Includes**:
1052 1052  
1053 -* N95S31B NB-IoT Temperature and Humidity Sensor
859 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
1054 1054  * External antenna x 1
1055 1055  )))
1056 1056  
... ... @@ -1059,10 +1059,11 @@
1059 1059  
1060 1060  (% style="color:#037691" %)**Dimension and weight**:
1061 1061  
868 +
1062 1062  * Device Size: 13.0 x 5 x 4.5 cm
1063 1063  * Device Weight: 150g
1064 -* Package Size / pcs : 14.0 x 8x 5 cm
1065 -* Weight / pcs : 180g
871 +* Package Size / pcs : 15 x 12x 5.5 cm
872 +* Weight / pcs : 220g
1066 1066  )))
1067 1067  
1068 1068  (((
... ... @@ -1074,6 +1074,5 @@
1074 1074  
1075 1075  = 9.  Support =
1076 1076  
1077 -
1078 1078  * 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.
1079 1079  * 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]]
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

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0