<
From version < 117.2 >
edited by Xiaoling
on 2022/07/11 11:35
To version < 124.1 >
edited by David Huang
on 2022/09/08 16:38
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.David
Content
... ... @@ -17,6 +17,7 @@
17 17  
18 18  = 1.  Introduction =
19 19  
20 +
20 20  == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
21 21  
22 22  (((
... ... @@ -55,6 +55,7 @@
55 55  
56 56  == 1.2 ​ Features ==
57 57  
59 +
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
... ... @@ -66,7 +66,6 @@
66 66  * Micro SIM card slot for NB-IoT SIM
67 67  * 8500mAh Battery for long term use
68 68  
69 -
70 70  == 1.3  Specification ==
71 71  
72 72  
... ... @@ -92,9 +92,9 @@
92 92  * Max continuously current: 130mA
93 93  * Max boost current: 2A, 1 second
94 94  
95 -
96 96  == ​1.4  Applications ==
97 97  
98 +
98 98  * Smart Buildings & Home Automation
99 99  * Logistics and Supply Chain Management
100 100  * Smart Metering
... ... @@ -106,15 +106,20 @@
106 106  ​
107 107  
108 108  
110 +
109 109  == 1.5  Pin Definitions & Switch ==
110 110  
113 +
111 111  N95S31B use the mother board from NBSN95 which as below.
112 112  
116 +
113 113  [[image:image-20220709144723-1.png]]
114 114  
115 115  
120 +
116 116  === 1.5.1 Jumper JP2 ===
117 117  
123 +
118 118  Power on Device when put this jumper.
119 119  
120 120  
... ... @@ -121,6 +121,7 @@
121 121  
122 122  === 1.5.2 BOOT MODE / SW1 ===
123 123  
130 +
124 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 126  )))
... ... @@ -133,6 +133,7 @@
133 133  
134 134  === 1.5.3 Reset Button ===
135 135  
143 +
136 136  Press to reboot the device.
137 137  
138 138  
... ... @@ -139,14 +139,15 @@
139 139  
140 140  === 1.5.4 LED ===
141 141  
150 +
142 142  It will flash:
143 143  
144 144  1. When boot the device in flash mode
145 145  1. Send an uplink packet
146 146  
147 -
148 148  = 2.  Use N95S31B to communicate with IoT Server =
149 149  
158 +
150 150  == 2.1  How it works ==
151 151  
152 152  
... ... @@ -163,7 +163,7 @@
163 163  
164 164  )))
165 165  
166 -[[image:1657350248151-650.png]]
175 +[[image:1657520100595-569.png]]
167 167  
168 168  (((
169 169  
... ... @@ -179,6 +179,7 @@
179 179  [[image:image-20220709150546-2.png]]
180 180  
181 181  
191 +
182 182  === 2.2.1 Test Requirement ===
183 183  
184 184  
... ... @@ -231,6 +231,7 @@
231 231  
232 232  === 2.2.3  Insert SIM card ===
233 233  
244 +
234 234  (((
235 235  Insert the NB-IoT Card get from your provider.
236 236  )))
... ... @@ -246,14 +246,18 @@
246 246  
247 247  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
248 248  
260 +
249 249  (((
250 250  (((
251 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.
264 +
265 +
252 252  )))
253 253  )))
254 254  
255 255  [[image:1657351312545-300.png]]
256 256  
271 +
257 257  **Connection:**
258 258  
259 259   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -277,8 +277,9 @@
277 277  
278 278  [[image:1657329814315-101.png]]
279 279  
295 +
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/]]
297 +(% 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]]**
282 282  )))
283 283  
284 284  
... ... @@ -285,9 +285,10 @@
285 285  
286 286  === 2.2.5  Use CoAP protocol to uplink data ===
287 287  
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  
305 +(% 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/]]**
290 290  
307 +
291 291  (((
292 292  **Use below commands:**
293 293  )))
... ... @@ -335,6 +335,7 @@
335 335  
336 336  === 2.2.7  Use MQTT protocol to uplink data ===
337 337  
355 +
338 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
... ... @@ -350,6 +350,7 @@
350 350  
351 351  [[image:1657352645687-385.png]]
352 352  
371 +
353 353  (((
354 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 355  )))
... ... @@ -363,6 +363,7 @@
363 363  
364 364  === 2.2.8  Use TCP protocol to uplink data ===
365 365  
385 +
366 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
... ... @@ -377,6 +377,7 @@
377 377  
378 378  === 2.2.9  Change Update Interval ===
379 379  
400 +
380 380  User can use below command to change the (% style="color:green" %)**uplink interval**.
381 381  
382 382  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -385,13 +385,16 @@
385 385  
386 386  )))
387 387  
409 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
388 388  
411 +**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).**
389 389  
413 +
390 390  == 2.3  Uplink Payload ==
391 391  
392 392  
393 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.
418 +N95S31B 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 395  )))
396 396  
397 397  
... ... @@ -400,7 +400,7 @@
400 400  )))
401 401  
402 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.
427 + (% 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.
404 404  )))
405 405  
406 406  
... ... @@ -423,15 +423,19 @@
423 423  
424 424  (% style="color:red" %)
425 425  1. (((
426 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
450 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
427 427  )))
428 428  1. (((
429 -By default, the device will send an uplink message every 1 hour.
430 -)))
453 +**By default, the device will send an uplink message every 1 hour.**
431 431  
432 432  
456 +
457 +
458 +)))
459 +
433 433  === 2.3.1  Payload Analyze ===
434 434  
462 +
435 435  N95S31B uplink payload includes in total 21 bytes
436 436  
437 437  
... ... @@ -466,6 +466,8 @@
466 466  )))
467 467  
468 468  (((
497 +
498 +
469 469  (((
470 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.
471 471  )))
... ... @@ -492,12 +492,41 @@
492 492  )))
493 493  
494 494  (((
495 -
525 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
496 496  )))
497 497  
528 +In this mode, uplink payload includes 91 bytes in total by default.
498 498  
530 +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.
531 +
532 +|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4
533 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp .....
534 +
535 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
536 +
537 +[[image:image-20220908154949-1.png]]
538 +
539 +The payload is ASCII string, representative same HEX:
540 +
541 +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:
542 +
543 +* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782
544 +* (% style="color:blue" %) Version: 0x000c=120=1.2
545 +* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V
546 +* (% style="color:red" %) Singal: 0x0c = 12
547 +* (% style="color:blue" %) Mod: 0x01 = 1
548 +* TemDS18B20: 0x0000= 0 = 0
549 +* (% style="color:green" %)Interrupt: 0x00= 0
550 +* (% style="color:green" %)adc: 0x0030= 48
551 +* SHTTEM: 0x0114= 276 = 27.6
552 +* SHTHUM:0x0231 =561=56.1%
553 +* (% style="color:red" %) Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
554 +* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
555 +* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,.......
556 +
499 499  === 2.3.2  Device ID ===
500 500  
559 +
501 501  (((
502 502  By default, the Device ID equal to the last 6 bytes of IMEI.
503 503  )))
... ... @@ -516,12 +516,25 @@
516 516  
517 517  (((
518 518  The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
578 +
579 +
519 519  )))
520 520  
582 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
521 521  
522 522  
585 +By default, the Device ID equal to the last 15 bits of IMEI.
586 +
587 +User can use **AT+DEUI** to set Device ID
588 +
589 +**Example:**
590 +
591 +AT+DEUI=868411056754138
592 +
593 +
523 523  === 2.3.3  Version Info ===
524 524  
596 +
525 525  (((
526 526  These bytes include the hardware and software version.
527 527  )))
... ... @@ -549,6 +549,7 @@
549 549  
550 550  === 2.3.4  Battery Info ===
551 551  
624 +
552 552  (((
553 553  Ex1: 0x0B45 = 2885mV
554 554  )))
... ... @@ -561,6 +561,7 @@
561 561  
562 562  === 2.3.5  Signal Strength ===
563 563  
637 +
564 564  (((
565 565  NB-IoT Network signal Strength.
566 566  )))
... ... @@ -593,6 +593,7 @@
593 593  
594 594  === 2.3.6  Temperature & Humidity ===
595 595  
670 +
596 596  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
597 597  
598 598  [[image:image-20220709161741-3.png]]
... ... @@ -611,8 +611,9 @@
611 611  
612 612  == 2.4  Downlink Payload ==
613 613  
614 -By default, NDDS75 prints the downlink payload to console port.
615 615  
690 +By default, N95S31B prints the downlink payload to console port.
691 +
616 616  [[image:image-20220709100028-1.png]]
617 617  
618 618  
... ... @@ -649,7 +649,7 @@
649 649  )))
650 650  
651 651  (((
652 -If payload = 0x04FF, it will reset the NDDS75
728 +If payload = 0x04FF, it will reset the N95S31B
653 653  )))
654 654  
655 655  
... ... @@ -660,12 +660,59 @@
660 660  )))
661 661  
662 662  
739 +== 2.5 Humidity and Temperature alarm function ==
663 663  
664 -== 2.5  ​Battery Analysis ==
741 + AT Command:
665 665  
666 -=== 2.5.1  ​Battery Type ===
743 +AT+ SHHUM=min,max
667 667  
745 +² When min=0, and max≠0, Alarm higher than max
668 668  
747 +² When min≠0, and max=0, Alarm lower than min
748 +
749 +² When min≠0 and max≠0, Alarm higher than max or lower than min
750 +
751 +Example:
752 +
753 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
754 +
755 +
756 +AT+ SHTEMP=min,max
757 +
758 +² When min=0, and max≠0, Alarm higher than max
759 +
760 +² When min≠0, and max=0, Alarm lower than min
761 +
762 +² When min≠0 and max≠0, Alarm higher than max or lower than min
763 +
764 +Example:
765 +
766 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
767 +
768 +== 2.6 Set the number of data to be uploaded and the recording time ==
769 +
770 +➢ AT Command:
771 +
772 +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)
773 +
774 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
775 +
776 +== 2.7 Read or Clear cached data ==
777 +
778 +➢ AT Command:
779 +
780 +AT+CDP ~/~/ Read cached data
781 +
782 +[[image:image-20220908163102-2.png]]
783 +
784 +AT+CDP=0 ~/~/ Clear cached data
785 +
786 +== 2.8  ​Battery Analysis ==
787 +
788 +
789 +=== 2.8.1  ​Battery Type ===
790 +
791 +
669 669  (((
670 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.
671 671  )))
... ... @@ -688,10 +688,11 @@
688 688  
689 689  
690 690  
691 -=== 2.5.2  Power consumption Analyze ===
814 +=== 2.8.2  Power consumption Analyze ===
692 692  
816 +
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.
818 +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.
695 695  )))
696 696  
697 697  (((
... ... @@ -699,8 +699,9 @@
699 699  )))
700 700  
701 701  
702 -=== 2.5.3  ​Battery Note ===
826 +=== 2.8.3  ​Battery Note ===
703 703  
828 +
704 704  (((
705 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.
706 706  )))
... ... @@ -707,7 +707,7 @@
707 707  
708 708  
709 709  
710 -=== 2.5.4  Replace the battery ===
835 +=== 2.8.4  Replace the battery ===
711 711  
712 712  
713 713  (((
... ... @@ -723,6 +723,7 @@
723 723  
724 724  = 3. ​ Access NB-IoT Module =
725 725  
851 +
726 726  (((
727 727  Users can directly access the AT command set of the NB-IoT module.
728 728  )))
... ... @@ -729,6 +729,8 @@
729 729  
730 730  (((
731 731  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/]] 
858 +
859 +
732 732  )))
733 733  
734 734  [[image:1657333200519-600.png]]
... ... @@ -737,11 +737,13 @@
737 737  
738 738  = 4.  Using the AT Commands =
739 739  
868 +
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/]]
743 743  
872 +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]]
744 744  
874 +
745 745  AT+<CMD>?  : Help on <CMD>
746 746  
747 747  AT+<CMD>         : Run <CMD>
... ... @@ -781,7 +781,24 @@
781 781  
782 782  AT+SERVADDR  : Server Address
783 783  
914 +AT+TR      : Get or Set record time
784 784  
916 +AT+APN     : Get or set the APN
917 +
918 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
919 +
920 +AT+DNSCFG  : Get or Set DNS Server
921 +
922 +AT+GETSENSORVALUE   : Returns the current sensor measurement
923 +
924 +AT+NOUD      : Get or Set the number of data to be uploaded
925 +
926 +AT+CDP     : Read or Clear cached data
927 +
928 +AT+SHTEMP: Get or Set alarm of temp
929 +
930 +AT+SHHUM: Get or Set alarm of moisture
931 +
785 785  (% style="color:#037691" %)**COAP Management**      
786 786  
787 787  AT+URI            : Resource parameters
... ... @@ -815,6 +815,7 @@
815 815  
816 816  = ​5.  FAQ =
817 817  
965 +
818 818  == 5.1 ​ How to Upgrade Firmware ==
819 819  
820 820  
... ... @@ -830,7 +830,7 @@
830 830  
831 831  
832 832  (((
833 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
981 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
834 834  )))
835 835  )))
836 836  
... ... @@ -838,6 +838,7 @@
838 838  
839 839  = 6.  Trouble Shooting =
840 840  
989 +
841 841  == 6.1  ​Connection problem when uploading firmware ==
842 842  
843 843  
... ... @@ -853,6 +853,7 @@
853 853  
854 854  == 6.2  AT Command input doesn't work ==
855 855  
1005 +
856 856  (((
857 857  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.
858 858  
... ... @@ -902,5 +902,7 @@
902 902  
903 903  = 9.  Support =
904 904  
1055 +
905 905  * 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.
906 906  * 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]]
1058 +
1657520100595-569.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
image-20220908154949-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +58.5 KB
Content
image-20220908163102-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +29.7 KB
Content
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0