Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 125.5 >
edited by Xiaoling
on 2022/09/09 16:02
To version < 114.1 >
edited by Xiaoling
on 2022/07/09 16:11
>
Change comment: Uploaded new attachment "1657354294009-643.png", version {1}

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  )))
... ... @@ -68,6 +68,8 @@
68 68  * Micro SIM card slot for NB-IoT SIM
69 69  * 8500mAh Battery for long term use
70 70  
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,10 @@
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 +== ​1.4  Applications ==
87 +
99 99  * Smart Buildings & Home Automation
100 100  * Logistics and Supply Chain Management
101 101  * Smart Metering
... ... @@ -107,21 +107,15 @@
107 107  ​
108 108  
109 109  
99 +== 1.5  Pin Definitions ==
110 110  
111 -
112 -== 1.5  Pin Definitions & Switch ==
113 -
114 -
115 115  N95S31B use the mother board from NBSN95 which as below.
116 116  
117 -
118 118  [[image:image-20220709144723-1.png]]
119 119  
120 120  
121 -
122 122  === 1.5.1 Jumper JP2 ===
123 123  
124 -
125 125  Power on Device when put this jumper.
126 126  
127 127  
... ... @@ -128,20 +128,14 @@
128 128  
129 129  === 1.5.2 BOOT MODE / SW1 ===
130 130  
131 -
132 -(((
133 133  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.
134 -)))
135 135  
136 -(((
137 137  2) Flash: work mode, device starts to work and send out console output for further debug
138 -)))
139 139  
140 140  
141 141  
142 142  === 1.5.3 Reset Button ===
143 143  
144 -
145 145  Press to reboot the device.
146 146  
147 147  
... ... @@ -148,15 +148,16 @@
148 148  
149 149  === 1.5.4 LED ===
150 150  
151 -
152 152  It will flash:
153 153  
154 154  1. When boot the device in flash mode
155 155  1. Send an uplink packet
156 156  
157 -= 2.  Use N95S31B to communicate with IoT Server =
158 158  
159 159  
135 +
136 += 2.  Use N95S31B to communicate with IoT Server =
137 +
160 160  == 2.1  How it works ==
161 161  
162 162  
... ... @@ -173,7 +173,7 @@
173 173  
174 174  )))
175 175  
176 -[[image:1657520100595-569.png]]
154 +[[image:1657350248151-650.png]]
177 177  
178 178  (((
179 179  
... ... @@ -189,49 +189,27 @@
189 189  [[image:image-20220709150546-2.png]]
190 190  
191 191  
192 -
193 193  === 2.2.1 Test Requirement ===
194 194  
195 195  
196 -(((
197 197  To use N95S31B in your city, make sure meet below requirements:
198 -)))
199 199  
200 -* (((
201 -Your local operator has already distributed a NB-IoT Network there.
202 -)))
203 -* (((
204 -The local NB-IoT network used the band that N95S31B supports.
205 -)))
206 -* (((
207 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
208 -)))
175 +* Your local operator has already distributed a NB-IoT Network there.
176 +* The local NB-IoT network used the band that N95S31B supports.
177 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
209 209  
210 -(((
179 +
211 211  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
212 -)))
213 213  
214 -(((
215 215  N95S31B supports different communication protocol such as :
216 -)))
217 217  
218 218  (((
219 -* (((
220 -CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
221 -)))
222 -* (((
223 -raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
224 -)))
225 -* (((
226 -MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
227 -)))
228 -* (((
229 -TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
230 -)))
185 +* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
186 +* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
187 +* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
188 +* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
231 231  
232 -(((
233 233  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.
234 -)))
235 235  
236 236  
237 237  )))
... ... @@ -242,7 +242,6 @@
242 242  
243 243  === 2.2.3  Insert SIM card ===
244 244  
245 -
246 246  (((
247 247  Insert the NB-IoT Card get from your provider.
248 248  )))
... ... @@ -258,18 +258,14 @@
258 258  
259 259  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
260 260  
261 -
262 262  (((
263 263  (((
264 264  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.
265 -
266 -
267 267  )))
268 268  )))
269 269  
270 270  [[image:1657351312545-300.png]]
271 271  
272 -
273 273  **Connection:**
274 274  
275 275   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -293,9 +293,8 @@
293 293  
294 294  [[image:1657329814315-101.png]]
295 295  
296 -
297 297  (((
298 -(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**
248 +(% style="color:red" %)Note: the valid AT Commands can be found at:  (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]
299 299  )))
300 300  
301 301  
... ... @@ -302,10 +302,9 @@
302 302  
303 303  === 2.2.5  Use CoAP protocol to uplink data ===
304 304  
255 +(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
305 305  
306 -(% 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/]]**
307 307  
308 -
309 309  (((
310 310  **Use below commands:**
311 311  )))
... ... @@ -353,7 +353,6 @@
353 353  
354 354  === 2.2.7  Use MQTT protocol to uplink data ===
355 355  
356 -
357 357  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
358 358  
359 359  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
... ... @@ -361,8 +361,8 @@
361 361  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
362 362  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
363 363  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
364 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
365 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
312 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527  **(%%)~/~/Set the sending topic of MQTT
313 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527  **(%%) ~/~/Set the subscription topic of MQTT
366 366  
367 367  [[image:1657352634421-276.png]]
368 368  
... ... @@ -369,7 +369,6 @@
369 369  
370 370  [[image:1657352645687-385.png]]
371 371  
372 -
373 373  (((
374 374  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.
375 375  )))
... ... @@ -383,7 +383,6 @@
383 383  
384 384  === 2.2.8  Use TCP protocol to uplink data ===
385 385  
386 -
387 387  This feature is supported since firmware version v110
388 388  
389 389  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -398,7 +398,6 @@
398 398  
399 399  === 2.2.9  Change Update Interval ===
400 400  
401 -
402 402  User can use below command to change the (% style="color:green" %)**uplink interval**.
403 403  
404 404  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -407,56 +407,52 @@
407 407  
408 408  )))
409 409  
410 -(((
411 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
412 -)))
413 413  
414 -(((
415 -(% 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).**
416 -)))
417 417  
418 -
419 -
420 420  == 2.3  Uplink Payload ==
421 421  
359 +In this mode, uplink payload includes in total 14 bytes
422 422  
423 -(((
424 -N95S31B has different working 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.
425 -)))
426 426  
362 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
363 +|=(% style="width: 60px;" %)(((
364 +**Size(bytes)**
365 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
366 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
427 427  
428 428  (((
429 -For example:
369 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
430 430  )))
431 431  
432 -(((
433 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
434 -)))
435 435  
373 +[[image:1657331036973-987.png]]
436 436  
437 437  (((
438 -The uplink payloads are composed in  ASCII String. For example:
376 +The payload is ASCII string, representative same HEX:
439 439  )))
440 440  
441 441  (((
442 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
380 +0x72403155615900640c6c19029200 where:
443 443  )))
444 444  
445 -(((
446 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
383 +* (((
384 +Device ID: 0x724031556159 = 724031556159
447 447  )))
448 -
449 -
450 -(((
451 -(% style="color:red" %)**NOTE:**
386 +* (((
387 +Version: 0x0064=100=1.0.0
452 452  )))
453 453  
454 -(% style="color:red" %)
455 -1. (((
456 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
390 +* (((
391 +BAT: 0x0c6c = 3180 mV = 3.180V
457 457  )))
458 -1. (((
459 -**By default, the device will send an uplink message every 1 hour.**
393 +* (((
394 +Signal: 0x19 = 25
395 +)))
396 +* (((
397 +Distance: 0x0292= 658 mm
398 +)))
399 +* (((
400 +Interrupt: 0x00 = 0
460 460  
461 461  
462 462  
... ... @@ -463,188 +463,105 @@
463 463  
464 464  )))
465 465  
466 -=== 2.3.1  Payload Analyze ===
407 +== 2.4  Payload Explanation and Sensor Interface ==
467 467  
468 468  
469 -==== 2.3.1.1  Before Firmware v1.2 ====
410 +=== 2.4.1  Device ID ===
470 470  
471 -
472 -N95S31B uplink payload includes in total 21 bytes
473 -
474 -
475 -(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %)
476 -|=(% style="width: 60px;" %)(((
477 -**Size(bytes)**
478 -)))|=(% 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**
479 -|(% 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" %)(((
480 480  (((
481 -Reserve/ Same as NBSN95 CFGMOD=1
413 +By default, the Device ID equal to the last 6 bytes of IMEI.
482 482  )))
483 483  
484 484  (((
485 -No function here.
417 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
486 486  )))
487 -)))|(% style="width:106px" %)(((
488 -(((
489 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
490 -)))
491 491  
492 492  (((
493 -By SHT31
421 +**Example:**
494 494  )))
495 -)))|(% style="width:85px" %)(((
496 -(((
497 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
498 -)))
499 499  
500 500  (((
501 -By SHT31
425 +AT+DEUI=A84041F15612
502 502  )))
503 -)))
504 504  
505 505  (((
506 -
507 -
508 -(((
509 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
429 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
510 510  )))
511 -)))
512 512  
513 513  
514 -[[image:1657354294009-643.png]]
515 515  
434 +=== 2.4.2  Version Info ===
516 516  
517 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
436 +(((
437 +Specify the software version: 0x64=100, means firmware version 1.00.
438 +)))
518 518  
519 -* Device ID:  0x724031607457 = 724031607457
440 +(((
441 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
442 +)))
520 520  
521 -* Version:  0x006e=110=1.1.0
522 522  
523 -* BAT:  0x0ccd = 3277 mV = 3.277V
524 524  
525 -* Signal:  0x1b = 27
446 +=== 2.4.3  Battery Info ===
526 526  
527 -* Model:  0x01 = 1
528 -
529 -* 0x00dc000ccc= reserve, ignore in N95S31B
530 -
531 -* Temperature by SHT31:  0x00e1 = 225 = 22.5 °C
532 -
533 -* Humidity by SHT31:  0x0186 = 390 = 39.0 %rh
534 -
535 535  (((
536 -
449 +Ex1: 0x0B45 = 2885mV
450 +)))
537 537  
538 -
539 -
452 +(((
453 +Ex2: 0x0B49 = 2889mV
540 540  )))
541 541  
542 -==== 2.3.1.2 Since Firmware v1.2 ====
543 543  
544 544  
545 -In this mode, uplink payload includes 91 bytes in total by default.
458 +=== 2.4.4  Signal Strength ===
546 546  
547 -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.
548 -
549 -
550 -(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %)
551 -|(% 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**
552 -|(% 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 .....
553 -
554 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
555 -
556 -
557 -[[image:image-20220908154949-1.png]]
558 -
559 -
560 -The payload is ASCII string, representative same HEX:
561 -
562 -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:
563 -
564 -* (% style="color:red" %)Device ID: f868411056758782 = f868411056758782
565 -
566 -* (% style="color:blue" %)Version: 0x000c=120=1.2
567 -
568 -* (% style="color:green" %)BAT: 0x0d0f = 3343 mV = 3.343V
569 -
570 -* (% style="color:red" %)Singal: 0x0c = 12
571 -
572 -* (% style="color:blue" %)Mod: 0x01 = 1
573 -
574 -* TemDS18B20: 0x0000= 0 = 0
575 -
576 -* (% style="color:green" %)Interrupt: 0x00= 0
577 -
578 -* (% style="color:green" %)adc: 0x0030= 48
579 -
580 -* SHTTEM: 0x0114= 276 = 27.6
581 -
582 -* SHTHUM:0x0231 =561=56.1%
583 -
584 -* (% style="color:red" %)Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
585 -
586 -* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
587 -
588 -* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,.......
589 -
590 -
591 -
592 -=== 2.3.2  Device ID ===
593 -
594 -
595 595  (((
596 -By default, the Device ID equal to the last 6 bytes of IMEI.
461 +NB-IoT Network signal Strength.
597 597  )))
598 598  
599 599  (((
600 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
465 +**Ex1: 0x1d = 29**
466 +)))
601 601  
602 -
468 +(((
469 +(% style="color:blue" %)**0**(%%)  -113dBm or less
603 603  )))
604 604  
605 605  (((
606 -*
607 -** (% style="color:blue" %)Example:
473 +(% style="color:blue" %)**1**(%%)  -111dBm
608 608  )))
609 609  
610 610  (((
611 -AT+DEUI=A84041F15612
477 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
612 612  )))
613 613  
614 614  (((
615 -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.
481 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
482 +)))
616 616  
617 -
484 +(((
485 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
618 618  )))
619 619  
620 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
621 621  
622 622  
623 -By default, the Device ID equal to the last 15 bits of IMEI.
490 +=== 2.4.5  Distance ===
624 624  
625 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
492 +Get the distance. Flat object range 280mm - 7500mm.
626 626  
627 -
628 -*
629 -** (% style="color:blue" %)Example:
630 -
631 -AT+DEUI=868411056754138
632 -
633 -
634 -
635 -=== 2.3.3  Version Info ===
636 -
637 -
638 638  (((
639 -These bytes include the hardware and software version.
495 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
640 640  )))
641 641  
642 642  (((
643 -Higher byte: Specify hardware version: always 0x00 for N95S31B
499 +(((
500 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
644 644  )))
502 +)))
645 645  
646 646  (((
647 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
505 +
648 648  )))
649 649  
650 650  (((
... ... @@ -651,85 +651,65 @@
651 651  
652 652  )))
653 653  
512 +=== 2.4.6  Digital Interrupt ===
513 +
654 654  (((
655 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
515 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
656 656  )))
657 657  
658 658  (((
659 -
519 +The command is:
660 660  )))
661 661  
662 -
663 -=== 2.3.4  Battery Info ===
664 -
665 -
666 666  (((
667 -Ex1: 0x0B45 = 2885mV
523 +(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
668 668  )))
669 669  
526 +
670 670  (((
671 -Ex2: 0x0B49 = 2889mV
528 +The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
672 672  )))
673 673  
674 674  
675 -
676 -=== 2.3.5  Signal Strength ===
677 -
678 -
679 679  (((
680 -NB-IoT Network signal Strength.
533 +Example:
681 681  )))
682 682  
683 683  (((
684 -**Ex1: 0x1d = 29**
537 +0x(00): Normal uplink packet.
685 685  )))
686 686  
687 687  (((
688 -(% style="color:blue" %)**0**(%%)  -113dBm or less
541 +0x(01): Interrupt Uplink Packet.
689 689  )))
690 690  
544 +
545 +
546 +=== 2.4.7  ​+5V Output ===
547 +
691 691  (((
692 -(% style="color:blue" %)**1**(%%)  -111dBm
549 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
693 693  )))
694 694  
552 +
695 695  (((
696 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
554 +The 5V output time can be controlled by AT Command.
697 697  )))
698 698  
699 699  (((
700 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
558 +(% style="color:blue" %)**AT+5VT=1000**
701 701  )))
702 702  
703 703  (((
704 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
562 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
705 705  )))
706 706  
707 707  
708 708  
709 -=== 2.3.6  Temperature & Humidity ===
567 +== 2.5  Downlink Payload ==
710 710  
569 +By default, NDDS75 prints the downlink payload to console port.
711 711  
712 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
713 -
714 -[[image:image-20220709161741-3.png]]
715 -
716 -
717 -Convert the read byte to decimal and divide it by ten.
718 -
719 -
720 -**Example:**
721 -
722 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
723 -
724 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
725 -
726 -
727 -
728 -== 2.4  Downlink Payload ==
729 -
730 -
731 -By default, N95S31B prints the downlink payload to console port.
732 -
733 733  [[image:image-20220709100028-1.png]]
734 734  
735 735  
... ... @@ -766,7 +766,7 @@
766 766  )))
767 767  
768 768  (((
769 -If payload = 0x04FF, it will reset the N95S31B
607 +If payload = 0x04FF, it will reset the NDDS75
770 770  )))
771 771  
772 772  
... ... @@ -778,75 +778,48 @@
778 778  
779 779  
780 780  
781 -== 2.5  Humidity and Temperature alarm function ==
619 +== 2.6  ​LED Indicator ==
782 782  
783 783  
784 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
622 +The NDDS75 has an internal LED which is to show the status of different state.
785 785  
786 786  
787 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
625 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
626 +* Then the LED will be on for 1 second means device is boot normally.
627 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
628 +* For each uplink probe, LED will be on for 500ms.
788 788  
630 +(((
631 +
632 +)))
789 789  
790 -² When min=0, and max≠0, Alarm higher than max
791 791  
792 -² When min≠0, and max=0, Alarm lower than min
793 793  
794 -² When min≠0 and max≠0, Alarm higher than max or lower than min
636 +== 2.7  ​Firmware Change Log ==
795 795  
796 796  
797 - (% style="color:blue" %)**Example:**
639 +(((
640 +Download URL & Firmware Change log
641 +)))
798 798  
799 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
643 +(((
644 +[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
645 +)))
800 800  
801 801  
802 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
648 +(((
649 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
650 +)))
803 803  
804 -² When min=0, and max≠0, Alarm higher than max
805 805  
806 -² When min≠0, and max=0, Alarm lower than min
807 807  
808 -² When min≠0 and max≠0, Alarm higher than max or lower than min
809 -
810 -
811 -**~ (% style="color:blue" %)Example:(%%)**
812 -
813 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
814 -
815 -
816 -
817 -== 2.6 Set the number of data to be uploaded and the recording time ==
818 -
819 -
820 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
821 -
822 -* (% 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)
823 -* (% 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.
824 -
825 -
826 -
827 -
828 -== 2.7 Read or Clear cached data ==
829 -
830 -
831 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
832 -
833 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
834 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
835 -
836 -
837 -
838 -[[image:image-20220908163102-2.png]]
839 -
840 -
841 -
842 842  == 2.8  ​Battery Analysis ==
843 843  
844 -
845 845  === 2.8.1  ​Battery Type ===
846 846  
847 847  
848 848  (((
849 -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.
660 +The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
850 850  )))
851 851  
852 852  (((
... ... @@ -869,35 +869,54 @@
869 869  
870 870  === 2.8.2  Power consumption Analyze ===
871 871  
683 +(((
684 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
685 +)))
872 872  
687 +
873 873  (((
874 -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.
689 +Instruction to use as below:
875 875  )))
876 876  
877 877  (((
878 -
693 +(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
879 879  )))
880 880  
881 881  
882 -=== 2.8.3  ​Battery Note ===
697 +(((
698 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
699 +)))
883 883  
701 +* (((
702 +Product Model
703 +)))
704 +* (((
705 +Uplink Interval
706 +)))
707 +* (((
708 +Working Mode
709 +)))
884 884  
885 885  (((
886 -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.
712 +And the Life expectation in difference case will be shown on the right.
887 887  )))
888 888  
715 +[[image:image-20220709110451-3.png]]
889 889  
890 890  
891 -=== 2.8.4  Replace the battery ===
892 892  
719 +=== 2.8.3  ​Battery Note ===
893 893  
894 894  (((
895 -You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
722 +The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
896 896  )))
897 897  
898 898  
726 +
727 +=== 2.8.4  Replace the battery ===
728 +
899 899  (((
900 -The default battery pack of N95S31B includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
730 +The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
901 901  )))
902 902  
903 903  
... ... @@ -904,7 +904,6 @@
904 904  
905 905  = 3. ​ Access NB-IoT Module =
906 906  
907 -
908 908  (((
909 909  Users can directly access the AT command set of the NB-IoT module.
910 910  )))
... ... @@ -911,8 +911,6 @@
911 911  
912 912  (((
913 913  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/]] 
914 -
915 -
916 916  )))
917 917  
918 918  [[image:1657333200519-600.png]]
... ... @@ -921,13 +921,11 @@
921 921  
922 922  = 4.  Using the AT Commands =
923 923  
924 -
925 925  == 4.1  Access AT Commands ==
926 926  
753 +See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
927 927  
928 -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]]
929 929  
930 -
931 931  AT+<CMD>?  : Help on <CMD>
932 932  
933 933  AT+<CMD>         : Run <CMD>
... ... @@ -967,24 +967,7 @@
967 967  
968 968  AT+SERVADDR  : Server Address
969 969  
970 -AT+TR      : Get or Set record time
971 971  
972 -AT+APN     : Get or set the APN
973 -
974 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
975 -
976 -AT+DNSCFG  : Get or Set DNS Server
977 -
978 -AT+GETSENSORVALUE   : Returns the current sensor measurement
979 -
980 -AT+NOUD      : Get or Set the number of data to be uploaded
981 -
982 -AT+CDP     : Read or Clear cached data
983 -
984 -AT+SHTEMP: Get or Set alarm of temp
985 -
986 -AT+SHHUM: Get or Set alarm of moisture
987 -
988 988  (% style="color:#037691" %)**COAP Management**      
989 989  
990 990  AT+URI            : Resource parameters
... ... @@ -1018,7 +1018,6 @@
1018 1018  
1019 1019  = ​5.  FAQ =
1020 1020  
1021 -
1022 1022  == 5.1 ​ How to Upgrade Firmware ==
1023 1023  
1024 1024  
... ... @@ -1031,18 +1031,13 @@
1031 1031  )))
1032 1032  
1033 1033  (((
1034 -
1035 -
1036 -(((
1037 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
841 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
1038 1038  )))
1039 -)))
1040 1040  
1041 1041  
1042 1042  
1043 1043  = 6.  Trouble Shooting =
1044 1044  
1045 -
1046 1046  == 6.1  ​Connection problem when uploading firmware ==
1047 1047  
1048 1048  
... ... @@ -1058,7 +1058,6 @@
1058 1058  
1059 1059  == 6.2  AT Command input doesn't work ==
1060 1060  
1061 -
1062 1062  (((
1063 1063  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.
1064 1064  
... ... @@ -1069,7 +1069,7 @@
1069 1069  = 7. ​ Order Info =
1070 1070  
1071 1071  
1072 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
873 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1073 1073  
1074 1074  
1075 1075  (% class="wikigeneratedid" %)
... ... @@ -1084,7 +1084,7 @@
1084 1084  
1085 1085  (% style="color:#037691" %)**Package Includes**:
1086 1086  
1087 -* N95S31B NB-IoT Temperature and Humidity Sensor
888 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
1088 1088  * External antenna x 1
1089 1089  )))
1090 1090  
... ... @@ -1093,10 +1093,11 @@
1093 1093  
1094 1094  (% style="color:#037691" %)**Dimension and weight**:
1095 1095  
897 +
1096 1096  * Device Size: 13.0 x 5 x 4.5 cm
1097 1097  * Device Weight: 150g
1098 -* Package Size / pcs : 14.0 x 8x 5 cm
1099 -* Weight / pcs : 180g
900 +* Package Size / pcs : 15 x 12x 5.5 cm
901 +* Weight / pcs : 220g
1100 1100  )))
1101 1101  
1102 1102  (((
... ... @@ -1108,10 +1108,5 @@
1108 1108  
1109 1109  = 9.  Support =
1110 1110  
1111 -
1112 1112  * 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.
1113 1113  * 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]]
1114 -
1115 -
1116 -
1117 -
1657520100595-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -111.2 KB
Content
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