Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 118.1 >
edited by Xiaoling
on 2022/07/11 14:15
To version < 105.1 >
edited by Xiaoling
on 2022/07/09 15:21
>
Change comment: Uploaded new attachment "1657351312545-300.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  
... ... @@ -22,29 +22,16 @@
22 22  (((
23 23  
24 24  
25 -(((
26 26  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*.
27 -)))
28 28  
29 -(((
30 30  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.
31 -)))
32 32  
33 -(((
34 34  N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
35 -)))
36 36  
37 -(((
38 38  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).
39 -)))
40 40  
41 -(((
42 -
43 -)))
44 44  
45 -(((
46 46  ~* make sure you have NB-IoT coverage locally.
47 -)))
48 48  
49 49  
50 50  )))
... ... @@ -55,6 +55,7 @@
55 55  
56 56  == 1.2 ​ Features ==
57 57  
44 +
58 58  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
59 59  * Monitor Temperature & Humidity via SHT31
60 60  * AT Commands to change parameters
... ... @@ -67,6 +67,7 @@
67 67  * 8500mAh Battery for long term use
68 68  
69 69  
57 +
70 70  == 1.3  Specification ==
71 71  
72 72  
... ... @@ -86,6 +86,7 @@
86 86  
87 87  (% style="color:#037691" %)**Battery:**
88 88  
77 +
89 89  * Li/SOCI2 un-chargeable battery
90 90  * Capacity: 8500mAh
91 91  * Self Discharge: <1% / Year @ 25°C
... ... @@ -93,6 +93,7 @@
93 93  * Max boost current: 2A, 1 second
94 94  
95 95  
85 +
96 96  == ​1.4  Applications ==
97 97  
98 98  * Smart Buildings & Home Automation
... ... @@ -106,7 +106,7 @@
106 106  ​
107 107  
108 108  
109 -== 1.5  Pin Definitions & Switch ==
99 +== 1.5  Pin Definitions ==
110 110  
111 111  N95S31B use the mother board from NBSN95 which as below.
112 112  
... ... @@ -121,13 +121,9 @@
121 121  
122 122  === 1.5.2 BOOT MODE / SW1 ===
123 123  
124 -(((
125 125  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.
126 -)))
127 127  
128 -(((
129 129  2) Flash: work mode, device starts to work and send out console output for further debug
130 -)))
131 131  
132 132  
133 133  
... ... @@ -145,6 +145,8 @@
145 145  1. Send an uplink packet
146 146  
147 147  
134 +
135 +
148 148  = 2.  Use N95S31B to communicate with IoT Server =
149 149  
150 150  == 2.1  How it works ==
... ... @@ -182,45 +182,24 @@
182 182  === 2.2.1 Test Requirement ===
183 183  
184 184  
185 -(((
186 186  To use N95S31B in your city, make sure meet below requirements:
187 -)))
188 188  
189 -* (((
190 -Your local operator has already distributed a NB-IoT Network there.
191 -)))
192 -* (((
193 -The local NB-IoT network used the band that N95S31B supports.
194 -)))
195 -* (((
196 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
197 -)))
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.
198 198  
199 -(((
179 +
200 200  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
201 -)))
202 202  
203 -(((
204 204  N95S31B supports different communication protocol such as :
205 -)))
206 206  
207 207  (((
208 -* (((
209 -CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
210 -)))
211 -* (((
212 -raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
213 -)))
214 -* (((
215 -MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
216 -)))
217 -* (((
218 -TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
219 -)))
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(%%))
220 220  
221 -(((
222 222  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.
223 -)))
224 224  
225 225  
226 226  )))
... ... @@ -244,15 +244,15 @@
244 244  
245 245  
246 246  
247 -=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
214 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
248 248  
249 249  (((
250 250  (((
251 -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.
218 +User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
252 252  )))
253 253  )))
254 254  
255 -[[image:1657351312545-300.png]]
222 +[[image:image-20220709092052-2.png]]
256 256  
257 257  **Connection:**
258 258  
... ... @@ -272,18 +272,18 @@
272 272  * Flow Control: (% style="color:green" %)**None**
273 273  
274 274  (((
275 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
242 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
276 276  )))
277 277  
278 278  [[image:1657329814315-101.png]]
279 279  
280 280  (((
281 -(% 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/]]
248 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
282 282  )))
283 283  
284 284  
285 285  
286 -=== 2.2.5  Use CoAP protocol to uplink data ===
253 +=== 2.2.4 Use CoAP protocol to uplink data ===
287 287  
288 288  (% 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/]]
289 289  
... ... @@ -303,12 +303,10 @@
303 303  )))
304 304  
305 305  (((
306 -
307 -
308 308  For parameter description, please refer to AT command set
309 309  )))
310 310  
311 -[[image:1657352146020-183.png]]
276 +[[image:1657330452568-615.png]]
312 312  
313 313  
314 314  (((
... ... @@ -315,11 +315,11 @@
315 315  After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
316 316  )))
317 317  
318 -[[image:1657352185396-303.png]]
283 +[[image:1657330472797-498.png]]
319 319  
320 320  
321 321  
322 -=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
287 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
323 323  
324 324  
325 325  * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
... ... @@ -326,16 +326,15 @@
326 326  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
327 327  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
328 328  
329 -[[image:1657352391268-297.png]]
294 +[[image:1657330501006-241.png]]
330 330  
331 331  
332 -[[image:1657352403317-397.png]]
297 +[[image:1657330533775-472.png]]
333 333  
334 334  
335 335  
336 -=== 2.2.7  Use MQTT protocol to uplink data ===
301 +=== 2.2.6 Use MQTT protocol to uplink data ===
337 337  
338 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
339 339  
340 340  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
341 341  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -342,40 +342,35 @@
342 342  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
343 343  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
344 344  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
345 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
346 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
309 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
310 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
347 347  
348 -[[image:1657352634421-276.png]]
312 +[[image:1657249978444-674.png]]
349 349  
350 350  
351 -[[image:1657352645687-385.png]]
315 +[[image:1657330723006-866.png]]
352 352  
353 -(((
354 -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.
355 -)))
356 356  
357 -
358 358  (((
359 -MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
319 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
360 360  )))
361 361  
362 362  
363 363  
364 -=== 2.2.8  Use TCP protocol to uplink data ===
324 +=== 2.2.7 Use TCP protocol to uplink data ===
365 365  
366 -This feature is supported since firmware version v110
367 367  
368 368  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
369 369  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
370 370  
371 -[[image:1657352898400-901.png]]
330 +[[image:image-20220709093918-1.png]]
372 372  
373 373  
374 -[[image:1657352914475-252.png]]
333 +[[image:image-20220709093918-2.png]]
375 375  
376 376  
377 377  
378 -=== 2.2.9  Change Update Interval ===
337 +=== 2.2.8 Change Update Interval ===
379 379  
380 380  User can use below command to change the (% style="color:green" %)**uplink interval**.
381 381  
... ... @@ -382,156 +382,164 @@
382 382  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
383 383  
384 384  (((
385 -
344 +(% style="color:red" %)**NOTE:**
386 386  )))
387 387  
347 +(((
348 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
349 +)))
388 388  
389 389  
352 +
390 390  == 2.3  Uplink Payload ==
391 391  
355 +In this mode, uplink payload includes in total 14 bytes
392 392  
393 -(((
394 -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.
395 -)))
396 396  
358 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
359 +|=(% style="width: 60px;" %)(((
360 +**Size(bytes)**
361 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
362 +|(% 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"]]
397 397  
398 398  (((
399 -For example:
365 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
400 400  )))
401 401  
402 -(((
403 - (% 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.
404 -)))
405 405  
369 +[[image:1657331036973-987.png]]
406 406  
407 407  (((
408 -The uplink payloads are composed in  ASCII String. For example:
372 +The payload is ASCII string, representative same HEX:
409 409  )))
410 410  
411 411  (((
412 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
376 +0x72403155615900640c6c19029200 where:
413 413  )))
414 414  
415 -(((
416 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
379 +* (((
380 +Device ID: 0x724031556159 = 724031556159
417 417  )))
418 -
419 -
420 -(((
421 -(% style="color:red" %)**NOTE:**
382 +* (((
383 +Version: 0x0064=100=1.0.0
422 422  )))
423 423  
424 -(% style="color:red" %)
425 -1. (((
426 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
386 +* (((
387 +BAT: 0x0c6c = 3180 mV = 3.180V
427 427  )))
428 -1. (((
429 -By default, the device will send an uplink message every 1 hour.
389 +* (((
390 +Signal: 0x19 = 25
430 430  )))
392 +* (((
393 +Distance: 0x0292= 658 mm
394 +)))
395 +* (((
396 +Interrupt: 0x00 = 0
431 431  
432 432  
433 -=== 2.3.1  Payload Analyze ===
434 434  
435 -N95S31B uplink payload includes in total 21 bytes
400 +
401 +)))
436 436  
403 +== 2.4  Payload Explanation and Sensor Interface ==
437 437  
438 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
439 -|=(% style="width: 60px;" %)(((
440 -**Size(bytes)**
441 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**
442 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
405 +
406 +=== 2.4.1  Device ID ===
407 +
443 443  (((
444 -Reserve/ Same as NBSN95 CFGMOD=1
409 +By default, the Device ID equal to the last 6 bytes of IMEI.
445 445  )))
446 446  
447 447  (((
448 -No function here.
413 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
449 449  )))
450 -)))|(% style="width:77px" %)(((
415 +
451 451  (((
452 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
417 +**Example:**
453 453  )))
454 454  
455 455  (((
456 -By SHT31
421 +AT+DEUI=A84041F15612
457 457  )))
458 -)))|(% style="width:80px" %)(((
423 +
459 459  (((
460 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
425 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
461 461  )))
462 462  
428 +
429 +
430 +=== 2.4.2  Version Info ===
431 +
463 463  (((
464 -By SHT31
433 +Specify the software version: 0x64=100, means firmware version 1.00.
465 465  )))
466 -)))
467 467  
468 468  (((
469 -(((
470 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
437 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
471 471  )))
472 -)))
473 473  
474 474  
475 -[[image:1657354294009-643.png]]
476 476  
442 +=== 2.4.3  Battery Info ===
477 477  
478 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
444 +(((
445 +Ex1: 0x0B45 = 2885mV
446 +)))
479 479  
480 -* Device ID: 0x724031607457 = 724031607457
481 -* Version: 0x006e=110=1.1.0
448 +(((
449 +Ex2: 0x0B49 = 2889mV
450 +)))
482 482  
483 -* BAT: 0x0ccd = 3277 mV = 3.277V
484 -* Signal: 0x1b = 27
485 -* Model: 0x01 = 1
486 -* 0x00dc000ccc= reserve, ignore in N95S31B
487 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
488 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
489 489  
453 +
454 +=== 2.4.4  Signal Strength ===
455 +
490 490  (((
491 -
457 +NB-IoT Network signal Strength.
492 492  )))
493 493  
494 494  (((
495 -
461 +**Ex1: 0x1d = 29**
496 496  )))
497 497  
498 -
499 -=== 2.3.2  Device ID ===
500 -
501 501  (((
502 -By default, the Device ID equal to the last 6 bytes of IMEI.
465 +(% style="color:blue" %)**0**(%%)  -113dBm or less
503 503  )))
504 504  
505 505  (((
506 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
469 +(% style="color:blue" %)**1**(%%)  -111dBm
507 507  )))
508 508  
509 509  (((
510 -**Example:**
473 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
511 511  )))
512 512  
513 513  (((
514 -AT+DEUI=A84041F15612
477 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
515 515  )))
516 516  
517 517  (((
518 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
481 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
519 519  )))
520 520  
521 521  
522 522  
523 -=== 2.3.3  Version Info ===
486 +=== 2.4.5  Distance ===
524 524  
488 +Get the distance. Flat object range 280mm - 7500mm.
489 +
525 525  (((
526 -These bytes include the hardware and software version.
491 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
527 527  )))
528 528  
529 529  (((
530 -Higher byte: Specify hardware version: always 0x00 for N95S31B
495 +(((
496 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
531 531  )))
498 +)))
532 532  
533 533  (((
534 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
501 +
535 535  )))
536 536  
537 537  (((
... ... @@ -538,79 +538,63 @@
538 538  
539 539  )))
540 540  
508 +=== 2.4.6  Digital Interrupt ===
509 +
541 541  (((
542 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
511 +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.
543 543  )))
544 544  
545 545  (((
546 -
515 +The command is:
547 547  )))
548 548  
549 -
550 -=== 2.3.4  Battery Info ===
551 -
552 552  (((
553 -Ex1: 0x0B45 = 2885mV
519 +(% 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]])**.**
554 554  )))
555 555  
522 +
556 556  (((
557 -Ex2: 0x0B49 = 2889mV
524 +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.
558 558  )))
559 559  
560 560  
561 -
562 -=== 2.3.5  Signal Strength ===
563 -
564 564  (((
565 -NB-IoT Network signal Strength.
529 +Example:
566 566  )))
567 567  
568 568  (((
569 -**Ex1: 0x1d = 29**
533 +0x(00): Normal uplink packet.
570 570  )))
571 571  
572 572  (((
573 -(% style="color:blue" %)**0**(%%)  -113dBm or less
537 +0x(01): Interrupt Uplink Packet.
574 574  )))
575 575  
540 +
541 +
542 +=== 2.4.7  ​+5V Output ===
543 +
576 576  (((
577 -(% style="color:blue" %)**1**(%%)  -111dBm
545 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
578 578  )))
579 579  
548 +
580 580  (((
581 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
550 +The 5V output time can be controlled by AT Command.
582 582  )))
583 583  
584 584  (((
585 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
554 +(% style="color:blue" %)**AT+5VT=1000**
586 586  )))
587 587  
588 588  (((
589 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
558 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
590 590  )))
591 591  
592 592  
593 593  
594 -=== 2.3.6  Temperature & Humidity ===
563 +== 2.5  Downlink Payload ==
595 595  
596 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
597 -
598 -[[image:image-20220709161741-3.png]]
599 -
600 -
601 -Convert the read byte to decimal and divide it by ten.
602 -
603 -
604 -**Example:**
605 -
606 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
607 -
608 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
609 -
610 -
611 -
612 -== 2.4  Downlink Payload ==
613 -
614 614  By default, NDDS75 prints the downlink payload to console port.
615 615  
616 616  [[image:image-20220709100028-1.png]]
... ... @@ -661,16 +661,51 @@
661 661  
662 662  
663 663  
664 -== 2.5  ​Battery Analysis ==
615 +== 2.6  ​LED Indicator ==
665 665  
666 -=== 2.5.1  ​Battery Type ===
667 667  
618 +The NDDS75 has an internal LED which is to show the status of different state.
668 668  
620 +
621 +* 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)
622 +* Then the LED will be on for 1 second means device is boot normally.
623 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
624 +* For each uplink probe, LED will be on for 500ms.
625 +
669 669  (((
670 -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.
627 +
671 671  )))
672 672  
630 +
631 +
632 +== 2.7  ​Firmware Change Log ==
633 +
634 +
673 673  (((
636 +Download URL & Firmware Change log
637 +)))
638 +
639 +(((
640 +[[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/]]
641 +)))
642 +
643 +
644 +(((
645 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
646 +)))
647 +
648 +
649 +
650 +== 2.8  ​Battery Analysis ==
651 +
652 +=== 2.8.1  ​Battery Type ===
653 +
654 +
655 +(((
656 +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.
657 +)))
658 +
659 +(((
674 674  The battery is designed to last for several years depends on the actually use environment and update interval. 
675 675  )))
676 676  
... ... @@ -688,35 +688,56 @@
688 688  
689 689  
690 690  
691 -=== 2.5.2  Power consumption Analyze ===
677 +=== 2.8.2  Power consumption Analyze ===
692 692  
693 693  (((
694 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
680 +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.
695 695  )))
696 696  
683 +
697 697  (((
698 -
685 +Instruction to use as below:
699 699  )))
700 700  
688 +(((
689 +(% 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/]]
690 +)))
701 701  
702 -=== 2.5.3  ​Battery Note ===
703 703  
704 704  (((
705 -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.
694 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
706 706  )))
707 707  
697 +* (((
698 +Product Model
699 +)))
700 +* (((
701 +Uplink Interval
702 +)))
703 +* (((
704 +Working Mode
705 +)))
708 708  
707 +(((
708 +And the Life expectation in difference case will be shown on the right.
709 +)))
709 709  
710 -=== 2.5.4  Replace the battery ===
711 +[[image:image-20220709110451-3.png]]
711 711  
712 712  
714 +
715 +=== 2.8.3  ​Battery Note ===
716 +
713 713  (((
714 -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.
718 +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.
715 715  )))
716 716  
717 717  
722 +
723 +=== 2.8.4  Replace the battery ===
724 +
718 718  (((
719 -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).
726 +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).
720 720  )))
721 721  
722 722  
... ... @@ -739,7 +739,7 @@
739 739  
740 740  == 4.1  Access AT Commands ==
741 741  
742 -See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]
749 +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/]]
743 743  
744 744  
745 745  AT+<CMD>?  : Help on <CMD>
... ... @@ -827,12 +827,8 @@
827 827  )))
828 828  
829 829  (((
830 -
831 -
832 -(((
833 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
837 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
834 834  )))
835 -)))
836 836  
837 837  
838 838  
... ... @@ -863,7 +863,7 @@
863 863  = 7. ​ Order Info =
864 864  
865 865  
866 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
869 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
867 867  
868 868  
869 869  (% class="wikigeneratedid" %)
... ... @@ -878,7 +878,7 @@
878 878  
879 879  (% style="color:#037691" %)**Package Includes**:
880 880  
881 -* N95S31B NB-IoT Temperature and Humidity Sensor
884 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
882 882  * External antenna x 1
883 883  )))
884 884  
... ... @@ -887,10 +887,11 @@
887 887  
888 888  (% style="color:#037691" %)**Dimension and weight**:
889 889  
893 +
890 890  * Device Size: 13.0 x 5 x 4.5 cm
891 891  * Device Weight: 150g
892 -* Package Size / pcs : 14.0 x 8x 5 cm
893 -* Weight / pcs : 180g
896 +* Package Size / pcs : 15 x 12x 5.5 cm
897 +* Weight / pcs : 220g
894 894  )))
895 895  
896 896  (((
1657352146020-183.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -264.0 KB
Content
1657352185396-303.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.3 KB
Content
1657352391268-297.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -238.0 KB
Content
1657352403317-397.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -547.7 KB
Content
1657352634421-276.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -163.6 KB
Content
1657352645687-385.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -214.7 KB
Content
1657352898400-901.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -144.8 KB
Content
1657352914475-252.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -157.0 KB
Content
1657354294009-643.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -214.7 KB
Content
1657520100595-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -111.2 KB
Content

Applications

Navigation

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