Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 129.2 >
edited by Xiaoling
on 2022/10/14 17:59
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
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,20 +111,15 @@
111 111  ​
112 112  
113 113  
100 +== 1.5  Pin Definitions ==
114 114  
115 -== 1.5  Pin Definitions & Switch ==
116 -
117 -
118 118  N95S31B use the mother board from NBSN95 which as below.
119 119  
120 -
121 121  [[image:image-20220709144723-1.png]]
122 122  
123 123  
124 -
125 125  === 1.5.1 Jumper JP2 ===
126 126  
127 -
128 128  Power on Device when put this jumper.
129 129  
130 130  
... ... @@ -131,20 +131,14 @@
131 131  
132 132  === 1.5.2 BOOT MODE / SW1 ===
133 133  
134 -
135 -(((
136 136  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.
137 -)))
138 138  
139 -(((
140 140  2) Flash: work mode, device starts to work and send out console output for further debug
141 -)))
142 142  
143 143  
144 144  
145 145  === 1.5.3 Reset Button ===
146 146  
147 -
148 148  Press to reboot the device.
149 149  
150 150  
... ... @@ -151,7 +151,6 @@
151 151  
152 152  === 1.5.4 LED ===
153 153  
154 -
155 155  It will flash:
156 156  
157 157  1. When boot the device in flash mode
... ... @@ -158,10 +158,8 @@
158 158  1. Send an uplink packet
159 159  
160 160  
161 -
162 162  = 2.  Use N95S31B to communicate with IoT Server =
163 163  
164 -
165 165  == 2.1  How it works ==
166 166  
167 167  
... ... @@ -178,7 +178,7 @@
178 178  
179 179  )))
180 180  
181 -[[image:1657520100595-569.png]]
153 +[[image:1657350248151-650.png]]
182 182  
183 183  (((
184 184  
... ... @@ -194,49 +194,26 @@
194 194  [[image:image-20220709150546-2.png]]
195 195  
196 196  
197 -
198 198  === 2.2.1 Test Requirement ===
199 199  
200 200  
201 -(((
202 202  To use N95S31B in your city, make sure meet below requirements:
203 -)))
204 204  
205 -* (((
206 -Your local operator has already distributed a NB-IoT Network there.
207 -)))
208 -* (((
209 -The local NB-IoT network used the band that N95S31B supports.
210 -)))
211 -* (((
212 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
213 -)))
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.
214 214  
215 -(((
216 216  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
217 -)))
218 218  
219 -(((
220 220  N95S31B supports different communication protocol such as :
221 -)))
222 222  
223 223  (((
224 -* (((
225 -CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
226 -)))
227 -* (((
228 -raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
229 -)))
230 -* (((
231 -MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
232 -)))
233 -* (((
234 -TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
235 -)))
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(%%))
236 236  
237 -(((
238 238  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.
239 -)))
240 240  
241 241  
242 242  )))
... ... @@ -247,7 +247,6 @@
247 247  
248 248  === 2.2.3  Insert SIM card ===
249 249  
250 -
251 251  (((
252 252  Insert the NB-IoT Card get from your provider.
253 253  )))
... ... @@ -263,18 +263,14 @@
263 263  
264 264  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
265 265  
266 -
267 267  (((
268 268  (((
269 269  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.
270 -
271 -
272 272  )))
273 273  )))
274 274  
275 275  [[image:1657351312545-300.png]]
276 276  
277 -
278 278  **Connection:**
279 279  
280 280   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -298,9 +298,8 @@
298 298  
299 299  [[image:1657329814315-101.png]]
300 300  
301 -
302 302  (((
303 -(% 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/]]
304 304  )))
305 305  
306 306  
... ... @@ -307,10 +307,9 @@
307 307  
308 308  === 2.2.5  Use CoAP protocol to uplink data ===
309 309  
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/]]
310 310  
311 -(% 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/]]**
312 312  
313 -
314 314  (((
315 315  **Use below commands:**
316 316  )))
... ... @@ -319,10 +319,10 @@
319 319  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
320 320  )))
321 321  * (((
322 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
264 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
323 323  )))
324 324  * (((
325 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
267 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
326 326  )))
327 327  
328 328  (((
... ... @@ -358,7 +358,6 @@
358 358  
359 359  === 2.2.7  Use MQTT protocol to uplink data ===
360 360  
361 -
362 362  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
363 363  
364 364  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
... ... @@ -374,7 +374,6 @@
374 374  
375 375  [[image:1657352645687-385.png]]
376 376  
377 -
378 378  (((
379 379  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.
380 380  )))
... ... @@ -388,7 +388,6 @@
388 388  
389 389  === 2.2.8  Use TCP protocol to uplink data ===
390 390  
391 -
392 392  This feature is supported since firmware version v110
393 393  
394 394  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -403,7 +403,6 @@
403 403  
404 404  === 2.2.9  Change Update Interval ===
405 405  
406 -
407 407  User can use below command to change the (% style="color:green" %)**uplink interval**.
408 408  
409 409  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -412,104 +412,58 @@
412 412  
413 413  )))
414 414  
415 -(((
416 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
417 -)))
418 418  
419 -(((
420 -(% 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).**
421 -)))
422 422  
423 -
424 -
425 425  == 2.3  Uplink Payload ==
426 426  
427 427  
428 -(((
429 -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.
430 -)))
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.
431 431  
432 432  
433 -(((
434 434  For example:
435 -)))
436 436  
437 -(((
438 - (% 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.
439 -)))
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.
440 440  
441 441  
442 -(((
443 443  The uplink payloads are composed in  ASCII String. For example:
444 -)))
445 445  
446 -(((
447 447  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
448 -)))
449 449  
450 -(((
451 451  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
452 -)))
453 453  
454 454  
455 -(((
456 456  (% style="color:red" %)**NOTE:**
457 -)))
458 458  
459 459  (% style="color:red" %)
460 -1. (((
461 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
462 -)))
463 -1. (((
464 -**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.
465 465  
466 466  
467 467  
468 -
469 -)))
470 -
471 471  === 2.3.1  Payload Analyze ===
472 472  
473 -
474 -==== 2.3.1.1  Before Firmware v1.2 ====
475 -
476 -
477 477  N95S31B uplink payload includes in total 21 bytes
478 478  
479 479  
480 -(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:745px" %)
386 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
481 481  |=(% style="width: 60px;" %)(((
482 482  **Size(bytes)**
483 -)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 162px;" %)5|=(% style="width: 102px;" %)**2**|=(% style="width: 81px;" %)**2**
484 -|(% 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:162px" %)(((
485 -(((
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" %)(((
486 486  Reserve/ Same as NBSN95 CFGMOD=1
487 -)))
488 488  
489 -(((
490 490  No function here.
491 -)))
492 -)))|(% style="width:102px" %)(((
493 -(((
494 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
495 -)))
394 +)))|(% style="width:77px" %)(((
395 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
496 496  
497 -(((
498 498  By SHT31
499 -)))
500 -)))|(% style="width:81px" %)(((
501 -(((
502 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
503 -)))
398 +)))|(% style="width:80px" %)(((
399 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
504 504  
505 -(((
506 506  By SHT31
507 507  )))
508 -)))
509 509  
510 510  (((
511 -
512 -
513 513  (((
514 514  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
515 515  )))
... ... @@ -519,89 +519,29 @@
519 519  [[image:1657354294009-643.png]]
520 520  
521 521  
522 -The payload is ASCII string, representative same HEX: **0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
414 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
523 523  
524 -**where:**
416 +* Device ID: 0x724031607457 = 724031607457
417 +* Version: 0x006e=110=1.1.0
525 525  
526 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
419 +* BAT: 0x0ccd = 3277 mV = 3.277V
420 +* Signal: 0x1b = 27
421 +* Model: 0x01 = 1
422 +* 0x00dc000ccc= reserve, ignore in N95S31B
423 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
424 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
527 527  
528 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
529 -
530 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
531 -
532 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
533 -
534 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
535 -
536 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
537 -
538 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
539 -
540 -* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
541 -
542 542  (((
543 543  
428 +)))
544 544  
545 -
430 +(((
546 546  
547 547  )))
548 548  
549 -==== 2.3.1.2 Since Firmware v1.2 ====
550 550  
551 -
552 -In this mode, uplink payload includes 91 bytes in total by default.
553 -
554 -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.
555 -
556 -
557 -(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %)
558 -|(% style="width:95px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:43px" %)**2**|(% style="width:47px" %)**2**|(% style="width:124px" %)**1**|(% style="width:56px" %)**1**|(% style="width:109px" %)**2**|(% style="width:80px" %)**1**|(% style="width:51px" %)**2**|(% style="width:79px" %)**2**|(% style="width:84px" %)**2**|(% style="width:100px" %)**4**|(% style="width:76px" %)**2**|(% style="width:81px" %)**2**|(% style="width:121px" %)**4**
559 -|(% style="width:95px" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp .....
560 -
561 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
562 -
563 -
564 -[[image:image-20220908154949-1.png]]
565 -
566 -
567 -The payload is ASCII string, representative same HEX:
568 -
569 -**0x (% style="color:red" %)__f868411056758782__ (% style="color:blue" %)__000c__ (% style="color:green" %)__0d0f__ (% style="color:#00b0f0" %)__0c__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__0000__ (% style="color:#a14d07" %)__00__ __0030__ (% style="color:#0020b0" %)__0114__ (% style="color:#420042" %)__0231__ (% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__// //__0112023763199baa__ __0112023263199af6__// //__0111023b631999a7__ __0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
570 -
571 -**where:**
572 -
573 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
574 -
575 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
576 -
577 -* (% style="color:#037691" %)**BAT:**  (%%)0x0d0f = 3343 mV = 3.343V
578 -
579 -* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
580 -
581 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
582 -
583 -* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
584 -
585 -* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
586 -
587 -* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
588 -
589 -* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
590 -
591 -* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
592 -
593 -* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
594 -
595 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
596 -
597 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
598 -
599 -
600 -
601 -
602 602  === 2.3.2  Device ID ===
603 603  
604 -
605 605  (((
606 606  By default, the Device ID equal to the last 6 bytes of IMEI.
607 607  )))
... ... @@ -608,12 +608,10 @@
608 608  
609 609  (((
610 610  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
611 -
612 -
613 613  )))
614 614  
615 615  (((
616 -(% style="color:blue" %)**Example:**
446 +**Example:**
617 617  )))
618 618  
619 619  (((
... ... @@ -621,47 +621,22 @@
621 621  )))
622 622  
623 623  (((
624 -The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
625 -
626 -
454 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
627 627  )))
628 628  
629 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
630 630  
631 631  
632 -By default, the Device ID equal to the last 15 bits of IMEI.
633 -
634 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
635 -
636 -
637 -(% style="color:blue" %)**Example:**
638 -
639 -AT+DEUI=868411056754138
640 -
641 -
642 -
643 643  === 2.3.3  Version Info ===
644 644  
645 645  
646 -(((
647 647  These bytes include the hardware and software version.
648 -)))
649 649  
650 -(((
651 651  Higher byte: Specify hardware version: always 0x00 for N95S31B
652 -)))
653 653  
654 -(((
655 655  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
656 -)))
657 657  
658 -(((
659 -
660 -)))
661 661  
662 -(((
663 663  For example: 0x00 6E: this device is N95S31B with firmware version 110.
664 -)))
665 665  
666 666  (((
667 667  
... ... @@ -670,7 +670,6 @@
670 670  
671 671  === 2.3.4  Battery Info ===
672 672  
673 -
674 674  (((
675 675  Ex1: 0x0B45 = 2885mV
676 676  )))
... ... @@ -683,7 +683,6 @@
683 683  
684 684  === 2.3.5  Signal Strength ===
685 685  
686 -
687 687  (((
688 688  NB-IoT Network signal Strength.
689 689  )))
... ... @@ -716,7 +716,6 @@
716 716  
717 717  === 2.3.6  Temperature & Humidity ===
718 718  
719 -
720 720  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
721 721  
722 722  [[image:image-20220709161741-3.png]]
... ... @@ -733,11 +733,10 @@
733 733  
734 734  
735 735  
736 -== 2.4  Downlink Payload ==
538 +== 2.5  Downlink Payload ==
737 737  
540 +By default, NDDS75 prints the downlink payload to console port.
738 738  
739 -By default, N95S31B prints the downlink payload to console port.
740 -
741 741  [[image:image-20220709100028-1.png]]
742 742  
743 743  
... ... @@ -774,7 +774,7 @@
774 774  )))
775 775  
776 776  (((
777 -If payload = 0x04FF, it will reset the N95S31B
578 +If payload = 0x04FF, it will reset the NDDS75
778 778  )))
779 779  
780 780  
... ... @@ -786,76 +786,13 @@
786 786  
787 787  
788 788  
789 -== 2.5  Humidity and Temperature alarm function ==
590 +== 2.5  ​Battery Analysis ==
790 790  
592 +=== 2.5.1  ​Battery Type ===
791 791  
792 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
793 793  
794 -
795 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
796 -
797 -
798 -² When min=0, and max≠0, Alarm higher than max
799 -
800 -² When min≠0, and max=0, Alarm lower than min
801 -
802 -² When min≠0 and max≠0, Alarm higher than max or lower than min
803 -
804 -
805 - (% style="color:blue" %)**Example:**
806 -
807 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
808 -
809 -
810 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
811 -
812 -² When min=0, and max≠0, Alarm higher than max
813 -
814 -² When min≠0, and max=0, Alarm lower than min
815 -
816 -² When min≠0 and max≠0, Alarm higher than max or lower than min
817 -
818 -
819 -**~ (% style="color:blue" %)Example:(%%)**
820 -
821 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
822 -
823 -
824 -
825 -== 2.6 Set the number of data to be uploaded and the recording time ==
826 -
827 -
828 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
829 -
830 -* (% style="color:#037691" %)**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)
831 -* (% style="color:#037691" %)**AT+NOUD=8**  (%%)~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
832 -
833 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
834 -
835 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
836 -
837 -
838 -
839 -== 2.7 Read or Clear cached data ==
840 -
841 -
842 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
843 -
844 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
845 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
846 -
847 -[[image:image-20220908163102-2.png]]
848 -
849 -
850 -
851 -== 2.8  ​Battery Analysis ==
852 -
853 -
854 -=== 2.8.1  ​Battery Type ===
855 -
856 -
857 857  (((
858 -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.
859 859  )))
860 860  
861 861  (((
... ... @@ -878,35 +878,54 @@
878 878  
879 879  === 2.8.2  Power consumption Analyze ===
880 880  
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 +)))
881 881  
623 +
882 882  (((
883 -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:
884 884  )))
885 885  
886 886  (((
887 -
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/]]
888 888  )))
889 889  
890 890  
891 -=== 2.8.3  ​Battery Note ===
633 +(((
634 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
635 +)))
892 892  
637 +* (((
638 +Product Model
639 +)))
640 +* (((
641 +Uplink Interval
642 +)))
643 +* (((
644 +Working Mode
645 +)))
893 893  
894 894  (((
895 -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.
896 896  )))
897 897  
651 +[[image:image-20220709110451-3.png]]
898 898  
899 899  
900 -=== 2.8.4  Replace the battery ===
901 901  
655 +=== 2.8.3  ​Battery Note ===
902 902  
903 903  (((
904 -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.
905 905  )))
906 906  
907 907  
662 +
663 +=== 2.8.4  Replace the battery ===
664 +
908 908  (((
909 -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).
910 910  )))
911 911  
912 912  
... ... @@ -913,7 +913,6 @@
913 913  
914 914  = 3. ​ Access NB-IoT Module =
915 915  
916 -
917 917  (((
918 918  Users can directly access the AT command set of the NB-IoT module.
919 919  )))
... ... @@ -920,8 +920,6 @@
920 920  
921 921  (((
922 922  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/]] 
923 -
924 -
925 925  )))
926 926  
927 927  [[image:1657333200519-600.png]]
... ... @@ -930,13 +930,11 @@
930 930  
931 931  = 4.  Using the AT Commands =
932 932  
933 -
934 934  == 4.1  Access AT Commands ==
935 935  
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/]]
936 936  
937 -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]]
938 938  
939 -
940 940  AT+<CMD>?  : Help on <CMD>
941 941  
942 942  AT+<CMD>         : Run <CMD>
... ... @@ -976,24 +976,7 @@
976 976  
977 977  AT+SERVADDR  : Server Address
978 978  
979 -AT+TR      : Get or Set record time
980 980  
981 -AT+APN     : Get or set the APN
982 -
983 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
984 -
985 -AT+DNSCFG  : Get or Set DNS Server
986 -
987 -AT+GETSENSORVALUE   : Returns the current sensor measurement
988 -
989 -AT+NOUD      : Get or Set the number of data to be uploaded
990 -
991 -AT+CDP     : Read or Clear cached data
992 -
993 -AT+SHTEMP: Get or Set alarm of temp
994 -
995 -AT+SHHUM: Get or Set alarm of moisture
996 -
997 997  (% style="color:#037691" %)**COAP Management**      
998 998  
999 999  AT+URI            : Resource parameters
... ... @@ -1027,7 +1027,6 @@
1027 1027  
1028 1028  = ​5.  FAQ =
1029 1029  
1030 -
1031 1031  == 5.1 ​ How to Upgrade Firmware ==
1032 1032  
1033 1033  
... ... @@ -1040,18 +1040,13 @@
1040 1040  )))
1041 1041  
1042 1042  (((
1043 -
1044 -
1045 -(((
1046 -(% 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.
1047 1047  )))
1048 -)))
1049 1049  
1050 1050  
1051 1051  
1052 1052  = 6.  Trouble Shooting =
1053 1053  
1054 -
1055 1055  == 6.1  ​Connection problem when uploading firmware ==
1056 1056  
1057 1057  
... ... @@ -1067,7 +1067,6 @@
1067 1067  
1068 1068  == 6.2  AT Command input doesn't work ==
1069 1069  
1070 -
1071 1071  (((
1072 1072  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.
1073 1073  
... ... @@ -1078,7 +1078,7 @@
1078 1078  = 7. ​ Order Info =
1079 1079  
1080 1080  
1081 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
809 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1082 1082  
1083 1083  
1084 1084  (% class="wikigeneratedid" %)
... ... @@ -1093,7 +1093,7 @@
1093 1093  
1094 1094  (% style="color:#037691" %)**Package Includes**:
1095 1095  
1096 -* N95S31B NB-IoT Temperature and Humidity Sensor
824 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
1097 1097  * External antenna x 1
1098 1098  )))
1099 1099  
... ... @@ -1102,10 +1102,11 @@
1102 1102  
1103 1103  (% style="color:#037691" %)**Dimension and weight**:
1104 1104  
833 +
1105 1105  * Device Size: 13.0 x 5 x 4.5 cm
1106 1106  * Device Weight: 150g
1107 -* Package Size / pcs : 14.0 x 8x 5 cm
1108 -* Weight / pcs : 180g
836 +* Package Size / pcs : 15 x 12x 5.5 cm
837 +* Weight / pcs : 220g
1109 1109  )))
1110 1110  
1111 1111  (((
... ... @@ -1117,6 +1117,5 @@
1117 1117  
1118 1118  = 9.  Support =
1119 1119  
1120 -
1121 1121  * 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.
1122 1122  * 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
image-20221009001045-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content

Applications

Navigation

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