Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.33 >
edited by Xiaoling
on 2022/07/11 09:06
To version < 106.1 >
edited by Xiaoling
on 2022/07/09 15:35
>
Change comment: Uploaded new attachment "1657352146020-183.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
... ... @@ -68,7 +68,6 @@
68 68  
69 69  
70 70  
71 -
72 72  == 1.3  Specification ==
73 73  
74 74  
... ... @@ -77,7 +77,6 @@
77 77  * Supply Voltage: 2.1v ~~ 3.6v
78 78  * Operating Temperature: -40 ~~ 85°C
79 79  
80 -
81 81  (% style="color:#037691" %)**NB-IoT Spec:**
82 82  
83 83  * - B1 @H-FDD: 2100MHz
... ... @@ -87,9 +87,9 @@
87 87  * - B20 @H-FDD: 800MHz
88 88  * - B28 @H-FDD: 700MHz
89 89  
90 -
91 91  (% style="color:#037691" %)**Battery:**
92 92  
77 +
93 93  * Li/SOCI2 un-chargeable battery
94 94  * Capacity: 8500mAh
95 95  * Self Discharge: <1% / Year @ 25°C
... ... @@ -98,7 +98,6 @@
98 98  
99 99  
100 100  
101 -
102 102  == ​1.4  Applications ==
103 103  
104 104  * Smart Buildings & Home Automation
... ... @@ -127,13 +127,9 @@
127 127  
128 128  === 1.5.2 BOOT MODE / SW1 ===
129 129  
130 -(((
131 131  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.
132 -)))
133 133  
134 -(((
135 135  2) Flash: work mode, device starts to work and send out console output for further debug
136 -)))
137 137  
138 138  
139 139  
... ... @@ -190,45 +190,24 @@
190 190  === 2.2.1 Test Requirement ===
191 191  
192 192  
193 -(((
194 194  To use N95S31B in your city, make sure meet below requirements:
195 -)))
196 196  
197 -* (((
198 -Your local operator has already distributed a NB-IoT Network there.
199 -)))
200 -* (((
201 -The local NB-IoT network used the band that N95S31B supports.
202 -)))
203 -* (((
204 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
205 -)))
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.
206 206  
207 -(((
179 +
208 208  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
209 -)))
210 210  
211 -(((
212 212  N95S31B supports different communication protocol such as :
213 -)))
214 214  
215 215  (((
216 -* (((
217 -CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
218 -)))
219 -* (((
220 -raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
221 -)))
222 -* (((
223 -MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
224 -)))
225 -* (((
226 -TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
227 -)))
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(%%))
228 228  
229 -(((
230 230  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.
231 -)))
232 232  
233 233  
234 234  )))
... ... @@ -252,7 +252,7 @@
252 252  
253 253  
254 254  
255 -=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
214 +=== 2.2.3 Connect USB – TTL to N95S31B to configure it ===
256 256  
257 257  (((
258 258  (((
... ... @@ -291,7 +291,7 @@
291 291  
292 292  
293 293  
294 -=== 2.2.5  Use CoAP protocol to uplink data ===
253 +=== 2.2.4 Use CoAP protocol to uplink data ===
295 295  
296 296  (% 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/]]
297 297  
... ... @@ -311,12 +311,10 @@
311 311  )))
312 312  
313 313  (((
314 -
315 -
316 316  For parameter description, please refer to AT command set
317 317  )))
318 318  
319 -[[image:1657352146020-183.png]]
276 +[[image:1657330452568-615.png]]
320 320  
321 321  
322 322  (((
... ... @@ -323,11 +323,11 @@
323 323  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.
324 324  )))
325 325  
326 -[[image:1657352185396-303.png]]
283 +[[image:1657330472797-498.png]]
327 327  
328 328  
329 329  
330 -=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
287 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
331 331  
332 332  
333 333  * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
... ... @@ -334,16 +334,15 @@
334 334  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
335 335  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
336 336  
337 -[[image:1657352391268-297.png]]
294 +[[image:1657330501006-241.png]]
338 338  
339 339  
340 -[[image:1657352403317-397.png]]
297 +[[image:1657330533775-472.png]]
341 341  
342 342  
343 343  
344 -=== 2.2.7  Use MQTT protocol to uplink data ===
301 +=== 2.2.6 Use MQTT protocol to uplink data ===
345 345  
346 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
347 347  
348 348  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
349 349  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -350,40 +350,35 @@
350 350  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
351 351  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
352 352  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
353 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
354 -* (% 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
355 355  
356 -[[image:1657352634421-276.png]]
312 +[[image:1657249978444-674.png]]
357 357  
358 358  
359 -[[image:1657352645687-385.png]]
315 +[[image:1657330723006-866.png]]
360 360  
361 -(((
362 -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.
363 -)))
364 364  
365 -
366 366  (((
367 -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.
368 368  )))
369 369  
370 370  
371 371  
372 -=== 2.2.8  Use TCP protocol to uplink data ===
324 +=== 2.2.7 Use TCP protocol to uplink data ===
373 373  
374 -This feature is supported since firmware version v110
375 375  
376 376  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
377 377  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
378 378  
379 -[[image:1657352898400-901.png]]
330 +[[image:image-20220709093918-1.png]]
380 380  
381 381  
382 -[[image:1657352914475-252.png]]
333 +[[image:image-20220709093918-2.png]]
383 383  
384 384  
385 385  
386 -=== 2.2.9  Change Update Interval ===
337 +=== 2.2.8 Change Update Interval ===
387 387  
388 388  User can use below command to change the (% style="color:green" %)**uplink interval**.
389 389  
... ... @@ -390,227 +390,227 @@
390 390  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
391 391  
392 392  (((
393 -
344 +(% style="color:red" %)**NOTE:**
394 394  )))
395 395  
347 +(((
348 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
349 +)))
396 396  
397 397  
352 +
398 398  == 2.3  Uplink Payload ==
399 399  
355 +In this mode, uplink payload includes in total 14 bytes
400 400  
401 -(((
402 -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.
403 -)))
404 404  
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"]]
405 405  
406 406  (((
407 -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.
408 408  )))
409 409  
410 -(((
411 - (% 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.
412 -)))
413 413  
369 +[[image:1657331036973-987.png]]
414 414  
415 415  (((
416 -The uplink payloads are composed in  ASCII String. For example:
372 +The payload is ASCII string, representative same HEX:
417 417  )))
418 418  
419 419  (((
420 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
376 +0x72403155615900640c6c19029200 where:
421 421  )))
422 422  
423 -(((
424 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
379 +* (((
380 +Device ID: 0x724031556159 = 724031556159
425 425  )))
426 -
427 -
428 -(((
429 -(% style="color:red" %)**NOTE:**
382 +* (((
383 +Version: 0x0064=100=1.0.0
430 430  )))
431 431  
432 -(% style="color:red" %)
433 -1. (((
434 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
386 +* (((
387 +BAT: 0x0c6c = 3180 mV = 3.180V
435 435  )))
436 -1. (((
437 -By default, the device will send an uplink message every 1 hour.
389 +* (((
390 +Signal: 0x19 = 25
438 438  )))
392 +* (((
393 +Distance: 0x0292= 658 mm
394 +)))
395 +* (((
396 +Interrupt: 0x00 = 0
439 439  
440 440  
441 441  
400 +
401 +)))
442 442  
443 -=== 2.3.1  Payload Analyze ===
403 +== 2.4  Payload Explanation and Sensor Interface ==
444 444  
445 -N95S31B uplink payload includes in total 21 bytes
446 446  
406 +=== 2.4.1  Device ID ===
447 447  
448 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
449 -|=(% style="width: 60px;" %)(((
450 -**Size(bytes)**
451 -)))|=(% 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**
452 -|(% 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" %)(((
453 453  (((
454 -Reserve/ Same as NBSN95 CFGMOD=1
409 +By default, the Device ID equal to the last 6 bytes of IMEI.
455 455  )))
456 456  
457 457  (((
458 -No function here.
413 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
459 459  )))
460 -)))|(% style="width:77px" %)(((
415 +
461 461  (((
462 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
417 +**Example:**
463 463  )))
464 464  
465 465  (((
466 -By SHT31
421 +AT+DEUI=A84041F15612
467 467  )))
468 -)))|(% style="width:80px" %)(((
423 +
469 469  (((
470 -[[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.
471 471  )))
472 472  
428 +
429 +
430 +=== 2.4.2  Version Info ===
431 +
473 473  (((
474 -By SHT31
433 +Specify the software version: 0x64=100, means firmware version 1.00.
475 475  )))
476 -)))
477 477  
478 478  (((
479 -(((
480 -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.
481 481  )))
482 -)))
483 483  
484 484  
485 -[[image:1657354294009-643.png]]
486 486  
442 +=== 2.4.3  Battery Info ===
487 487  
488 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
489 -
490 -* Device ID: 0x724031607457 = 724031607457
491 -* Version: 0x006e=110=1.1.0
492 -
493 -* BAT: 0x0ccd = 3277 mV = 3.277V
494 -* Signal: 0x1b = 27
495 -* Model: 0x01 = 1
496 -* 0x00dc000ccc= reserve, ignore in N95S31B
497 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
498 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
499 -
500 500  (((
501 -
445 +Ex1: 0x0B45 = 2885mV
502 502  )))
503 503  
504 504  (((
505 -
449 +Ex2: 0x0B49 = 2889mV
506 506  )))
507 507  
508 508  
509 -=== 2.3.2  Device ID ===
510 510  
454 +=== 2.4.4  Signal Strength ===
455 +
511 511  (((
512 -By default, the Device ID equal to the last 6 bytes of IMEI.
457 +NB-IoT Network signal Strength.
513 513  )))
514 514  
515 515  (((
516 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
461 +**Ex1: 0x1d = 29**
517 517  )))
518 518  
519 519  (((
520 -**Example:**
465 +(% style="color:blue" %)**0**(%%)  -113dBm or less
521 521  )))
522 522  
523 523  (((
524 -AT+DEUI=A84041F15612
469 +(% style="color:blue" %)**1**(%%)  -111dBm
525 525  )))
526 526  
527 527  (((
528 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
473 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
529 529  )))
530 530  
476 +(((
477 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
478 +)))
531 531  
480 +(((
481 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
482 +)))
532 532  
533 -=== 2.3.3  Version Info ===
534 534  
535 535  
536 -These bytes include the hardware and software version.
486 +=== 2.4.5  Distance ===
537 537  
538 -Higher byte: Specify hardware version: always 0x00 for N95S31B
488 +Get the distance. Flat object range 280mm - 7500mm.
539 539  
540 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
490 +(((
491 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
492 +)))
541 541  
542 -
543 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
544 -
545 545  (((
546 -
495 +(((
496 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
547 547  )))
498 +)))
548 548  
549 -
550 -=== 2.3.4  Battery Info ===
551 -
552 552  (((
553 -Ex1: 0x0B45 = 2885mV
501 +
554 554  )))
555 555  
556 556  (((
557 -Ex2: 0x0B49 = 2889mV
505 +
558 558  )))
559 559  
508 +=== 2.4.6  Digital Interrupt ===
560 560  
561 -
562 -=== 2.3.5  Signal Strength ===
563 -
564 564  (((
565 -NB-IoT Network signal Strength.
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.
566 566  )))
567 567  
568 568  (((
569 -**Ex1: 0x1d = 29**
515 +The command is:
570 570  )))
571 571  
572 572  (((
573 -(% style="color:blue" %)**0**(%%)  -113dBm or less
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]])**.**
574 574  )))
575 575  
522 +
576 576  (((
577 -(% style="color:blue" %)**1**(%%)  -111dBm
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.
578 578  )))
579 579  
527 +
580 580  (((
581 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
529 +Example:
582 582  )))
583 583  
584 584  (((
585 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
533 +0x(00): Normal uplink packet.
586 586  )))
587 587  
588 588  (((
589 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
537 +0x(01): Interrupt Uplink Packet.
590 590  )))
591 591  
592 592  
593 593  
594 -=== 2.3.6  Temperature & Humidity ===
542 +=== 2.4.7  ​+5V Output ===
595 595  
596 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
544 +(((
545 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
546 +)))
597 597  
598 -[[image:image-20220709161741-3.png]]
599 599  
549 +(((
550 +The 5V output time can be controlled by AT Command.
551 +)))
600 600  
601 -Convert the read byte to decimal and divide it by ten.
553 +(((
554 +(% style="color:blue" %)**AT+5VT=1000**
555 +)))
602 602  
557 +(((
558 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
559 +)))
603 603  
604 -**Example:**
605 605  
606 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
607 607  
608 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
563 +== 2.5  Downlink Payload ==
609 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,9 +827,7 @@
827 827  )))
828 828  
829 829  (((
830 -
831 -
832 -(% 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.
833 833  )))
834 834  
835 835  
... ... @@ -861,7 +861,7 @@
861 861  = 7. ​ Order Info =
862 862  
863 863  
864 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
869 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
865 865  
866 866  
867 867  (% class="wikigeneratedid" %)
... ... @@ -876,7 +876,7 @@
876 876  
877 877  (% style="color:#037691" %)**Package Includes**:
878 878  
879 -* N95S31B NB-IoT Temperature and Humidity Sensor
884 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
880 880  * External antenna x 1
881 881  )))
882 882  
... ... @@ -885,10 +885,11 @@
885 885  
886 886  (% style="color:#037691" %)**Dimension and weight**:
887 887  
893 +
888 888  * Device Size: 13.0 x 5 x 4.5 cm
889 889  * Device Weight: 150g
890 -* Package Size / pcs : 14.0 x 8x 5 cm
891 -* Weight / pcs : 180g
896 +* Package Size / pcs : 15 x 12x 5.5 cm
897 +* Weight / pcs : 220g
892 892  )))
893 893  
894 894  (((
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
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