Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.15 >
edited by Xiaoling
on 2022/07/09 18:02
To version < 112.1 >
edited by Xiaoling
on 2022/07/09 15:48
>
Change comment: Uploaded new attachment "1657352898400-901.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  
... ... @@ -42,6 +42,7 @@
42 42  
43 43  == 1.2 ​ Features ==
44 44  
44 +
45 45  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
46 46  * Monitor Temperature & Humidity via SHT31
47 47  * AT Commands to change parameters
... ... @@ -130,6 +130,9 @@
130 130  1. When boot the device in flash mode
131 131  1. Send an uplink packet
132 132  
133 +
134 +
135 +
133 133  = 2.  Use N95S31B to communicate with IoT Server =
134 134  
135 135  == 2.1  How it works ==
... ... @@ -173,6 +173,7 @@
173 173  * The local NB-IoT network used the band that N95S31B supports.
174 174  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
175 175  
179 +
176 176  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
177 177  
178 178  N95S31B supports different communication protocol such as :
... ... @@ -298,7 +298,7 @@
298 298  
299 299  === 2.2.7  Use MQTT protocol to uplink data ===
300 300  
301 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
305 +N95S31B supports only plain MQTT now it doesn’t support TLS and other related encryption.
302 302  
303 303  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
304 304  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -305,8 +305,8 @@
305 305  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
306 306  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
307 307  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
308 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
309 -* (% 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
310 310  
311 311  [[image:1657352634421-276.png]]
312 312  
... ... @@ -324,21 +324,20 @@
324 324  
325 325  
326 326  
327 -=== 2.2.8  Use TCP protocol to uplink data ===
331 +=== 2.2.7 Use TCP protocol to uplink data ===
328 328  
329 -This feature is supported since firmware version v110
330 330  
331 331  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
332 332  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
333 333  
334 -[[image:1657352898400-901.png]]
337 +[[image:image-20220709093918-1.png]]
335 335  
336 336  
337 -[[image:1657352914475-252.png]]
340 +[[image:image-20220709093918-2.png]]
338 338  
339 339  
340 340  
341 -=== 2.2.9  Change Update Interval ===
344 +=== 2.2.8 Change Update Interval ===
342 342  
343 343  User can use below command to change the (% style="color:green" %)**uplink interval**.
344 344  
... ... @@ -345,91 +345,69 @@
345 345  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
346 346  
347 347  (((
348 -
351 +(% style="color:red" %)**NOTE:**
349 349  )))
350 350  
354 +(((
355 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
356 +)))
351 351  
352 352  
359 +
353 353  == 2.3  Uplink Payload ==
354 354  
362 +In this mode, uplink payload includes in total 14 bytes
355 355  
356 -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.
357 357  
358 -
359 -For example:
360 -
361 - (% 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.
362 -
363 -
364 -The uplink payloads are composed in  ASCII String. For example:
365 -
366 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
367 -
368 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
369 -
370 -
371 -(% style="color:red" %)**NOTE:**
372 -
373 -(% style="color:red" %)
374 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
375 -1. By default, the device will send an uplink message every 1 hour.
376 -
377 -
378 -=== 2.3.1  Payload Analyze ===
379 -
380 -N95S31B uplink payload includes in total 21 bytes
381 -
382 -
383 383  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
384 384  |=(% style="width: 60px;" %)(((
385 385  **Size(bytes)**
386 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %)1|=(% style="width: 99px;" %)5|=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**2**
387 -|(% 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" %)(((
388 -Reserve/ Same as NBSN95 CFGMOD=1
368 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
369 +|(% 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"]]
389 389  
390 -No function here.
391 -)))|(% style="width:77px" %)(((
392 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
371 +(((
372 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
373 +)))
393 393  
394 -By SHT31
395 -)))|(% style="width:80px" %)(((
396 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
397 397  
398 -By SHT31
376 +[[image:1657331036973-987.png]]
377 +
378 +(((
379 +The payload is ASCII string, representative same HEX:
399 399  )))
400 400  
401 401  (((
402 -(((
403 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
383 +0x72403155615900640c6c19029200 where:
404 404  )))
385 +
386 +* (((
387 +Device ID: 0x724031556159 = 724031556159
405 405  )))
389 +* (((
390 +Version: 0x0064=100=1.0.0
391 +)))
406 406  
393 +* (((
394 +BAT: 0x0c6c = 3180 mV = 3.180V
395 +)))
396 +* (((
397 +Signal: 0x19 = 25
398 +)))
399 +* (((
400 +Distance: 0x0292= 658 mm
401 +)))
402 +* (((
403 +Interrupt: 0x00 = 0
407 407  
408 -[[image:1657354294009-643.png]]
409 409  
410 410  
411 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
412 -
413 -* Device ID: 0x724031607457 = 724031607457
414 -* Version: 0x006e=110=1.1.0
415 -
416 -* BAT: 0x0ccd = 3277 mV = 3.277V
417 -* Signal: 0x1b = 27
418 -* Model: 0x01 = 1
419 -* 0x00dc000ccc= reserve, ignore in N95S31B
420 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
421 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
422 -
423 -(((
424 424  
425 425  )))
426 426  
427 -(((
428 -
429 -)))
410 +== 2.4  Payload Explanation and Sensor Interface ==
430 430  
431 431  
432 -=== 2.3.2  Device ID ===
413 +=== 2.4.1  Device ID ===
433 433  
434 434  (((
435 435  By default, the Device ID equal to the last 6 bytes of IMEI.
... ... @@ -453,25 +453,20 @@
453 453  
454 454  
455 455  
456 -=== 2.3.3  Version Info ===
437 +=== 2.4.2  Version Info ===
457 457  
439 +(((
440 +Specify the software version: 0x64=100, means firmware version 1.00.
441 +)))
458 458  
459 -These bytes include the hardware and software version.
460 -
461 -Higher byte: Specify hardware version: always 0x00 for N95S31B
462 -
463 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
464 -
465 -
466 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
467 -
468 468  (((
469 -
444 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
470 470  )))
471 471  
472 472  
473 -=== 2.3.4  Battery Info ===
474 474  
449 +=== 2.4.3  Battery Info ===
450 +
475 475  (((
476 476  Ex1: 0x0B45 = 2885mV
477 477  )))
... ... @@ -482,7 +482,7 @@
482 482  
483 483  
484 484  
485 -=== 2.3.5  Signal Strength ===
461 +=== 2.4.4  Signal Strength ===
486 486  
487 487  (((
488 488  NB-IoT Network signal Strength.
... ... @@ -514,26 +514,85 @@
514 514  
515 515  
516 516  
517 -=== 2.3.6  Temperature & Humidity ===
493 +=== 2.4.5  Distance ===
518 518  
519 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
495 +Get the distance. Flat object range 280mm - 7500mm.
520 520  
521 -[[image:image-20220709161741-3.png]]
497 +(((
498 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
499 +)))
522 522  
501 +(((
502 +(((
503 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
504 +)))
505 +)))
523 523  
524 -Convert the read byte to decimal and divide it by ten.
507 +(((
508 +
509 +)))
525 525  
511 +(((
512 +
513 +)))
526 526  
527 -**Example:**
515 +=== 2.4.6  Digital Interrupt ===
528 528  
529 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
517 +(((
518 +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.
519 +)))
530 530  
531 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
521 +(((
522 +The command is:
523 +)))
532 532  
525 +(((
526 +(% 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]])**.**
527 +)))
533 533  
534 534  
535 -== 2.4  Downlink Payload ==
530 +(((
531 +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.
532 +)))
536 536  
534 +
535 +(((
536 +Example:
537 +)))
538 +
539 +(((
540 +0x(00): Normal uplink packet.
541 +)))
542 +
543 +(((
544 +0x(01): Interrupt Uplink Packet.
545 +)))
546 +
547 +
548 +
549 +=== 2.4.7  ​+5V Output ===
550 +
551 +(((
552 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
553 +)))
554 +
555 +
556 +(((
557 +The 5V output time can be controlled by AT Command.
558 +)))
559 +
560 +(((
561 +(% style="color:blue" %)**AT+5VT=1000**
562 +)))
563 +
564 +(((
565 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
566 +)))
567 +
568 +
569 +
570 +== 2.5  Downlink Payload ==
571 +
537 537  By default, NDDS75 prints the downlink payload to console port.
538 538  
539 539  [[image:image-20220709100028-1.png]]
... ... @@ -584,16 +584,51 @@
584 584  
585 585  
586 586  
587 -== 2.5  ​Battery Analysis ==
622 +== 2.6  ​LED Indicator ==
588 588  
589 -=== 2.5.1  ​Battery Type ===
590 590  
625 +The NDDS75 has an internal LED which is to show the status of different state.
591 591  
627 +
628 +* 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)
629 +* Then the LED will be on for 1 second means device is boot normally.
630 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
631 +* For each uplink probe, LED will be on for 500ms.
632 +
592 592  (((
593 -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.
634 +
594 594  )))
595 595  
637 +
638 +
639 +== 2.7  ​Firmware Change Log ==
640 +
641 +
596 596  (((
643 +Download URL & Firmware Change log
644 +)))
645 +
646 +(((
647 +[[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/]]
648 +)))
649 +
650 +
651 +(((
652 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
653 +)))
654 +
655 +
656 +
657 +== 2.8  ​Battery Analysis ==
658 +
659 +=== 2.8.1  ​Battery Type ===
660 +
661 +
662 +(((
663 +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.
664 +)))
665 +
666 +(((
597 597  The battery is designed to last for several years depends on the actually use environment and update interval. 
598 598  )))
599 599  
... ... @@ -611,35 +611,56 @@
611 611  
612 612  
613 613  
614 -=== 2.5.2  Power consumption Analyze ===
684 +=== 2.8.2  Power consumption Analyze ===
615 615  
616 616  (((
617 -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.
687 +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.
618 618  )))
619 619  
690 +
620 620  (((
621 -
692 +Instruction to use as below:
622 622  )))
623 623  
695 +(((
696 +(% 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/]]
697 +)))
624 624  
625 -=== 2.5.3  ​Battery Note ===
626 626  
627 627  (((
628 -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.
701 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
629 629  )))
630 630  
704 +* (((
705 +Product Model
706 +)))
707 +* (((
708 +Uplink Interval
709 +)))
710 +* (((
711 +Working Mode
712 +)))
631 631  
714 +(((
715 +And the Life expectation in difference case will be shown on the right.
716 +)))
632 632  
633 -=== 2.5.4  Replace the battery ===
718 +[[image:image-20220709110451-3.png]]
634 634  
635 635  
721 +
722 +=== 2.8.3  ​Battery Note ===
723 +
636 636  (((
637 -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.
725 +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.
638 638  )))
639 639  
640 640  
729 +
730 +=== 2.8.4  Replace the battery ===
731 +
641 641  (((
642 -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).
733 +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).
643 643  )))
644 644  
645 645  
... ... @@ -662,7 +662,7 @@
662 662  
663 663  == 4.1  Access AT Commands ==
664 664  
665 -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/]]
756 +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/]]
666 666  
667 667  
668 668  AT+<CMD>?  : Help on <CMD>
... ... @@ -750,9 +750,7 @@
750 750  )))
751 751  
752 752  (((
753 -
754 -
755 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
844 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
756 756  )))
757 757  
758 758  
... ... @@ -784,7 +784,7 @@
784 784  = 7. ​ Order Info =
785 785  
786 786  
787 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
876 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
788 788  
789 789  
790 790  (% class="wikigeneratedid" %)
... ... @@ -799,7 +799,7 @@
799 799  
800 800  (% style="color:#037691" %)**Package Includes**:
801 801  
802 -* N95S31B NB-IoT Temperature and Humidity Sensor
891 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
803 803  * External antenna x 1
804 804  )))
805 805  
... ... @@ -808,10 +808,11 @@
808 808  
809 809  (% style="color:#037691" %)**Dimension and weight**:
810 810  
900 +
811 811  * Device Size: 13.0 x 5 x 4.5 cm
812 812  * Device Weight: 150g
813 -* Package Size / pcs : 14.0 x 8x 5 cm
814 -* Weight / pcs : 180g
903 +* Package Size / pcs : 15 x 12x 5.5 cm
904 +* Weight / pcs : 220g
815 815  )))
816 816  
817 817  (((
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