Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 129.15 >
edited by Xiaoling
on 2022/10/25 17:45
To version < 119.2 >
edited by Xiaoling
on 2022/08/22 14:47
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -68,6 +68,9 @@
68 68  * Micro SIM card slot for NB-IoT SIM
69 69  * 8500mAh Battery for long term use
70 70  
71 +
72 +
73 +
71 71  == 1.3  Specification ==
72 72  
73 73  
... ... @@ -76,6 +76,8 @@
76 76  * Supply Voltage: 2.1v ~~ 3.6v
77 77  * Operating Temperature: -40 ~~ 85°C
78 78  
82 +
83 +
79 79  (% style="color:#037691" %)**NB-IoT Spec:**
80 80  
81 81  * - B1 @H-FDD: 2100MHz
... ... @@ -85,6 +85,8 @@
85 85  * - B20 @H-FDD: 800MHz
86 86  * - B28 @H-FDD: 700MHz
87 87  
93 +
94 +
88 88  (% style="color:#037691" %)**Battery:**
89 89  
90 90  * Li/SOCI2 un-chargeable battery
... ... @@ -93,6 +93,9 @@
93 93  * Max continuously current: 130mA
94 94  * Max boost current: 2A, 1 second
95 95  
103 +
104 +
105 +
96 96  == ​1.4  Applications ==
97 97  
98 98  
... ... @@ -129,11 +129,11 @@
129 129  
130 130  
131 131  (((
132 -**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.
142 +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.
133 133  )))
134 134  
135 135  (((
136 -**2) Flash:**  work mode, device starts to work and send out console output for further debug
146 +2) Flash: work mode, device starts to work and send out console output for further debug
137 137  )))
138 138  
139 139  
... ... @@ -150,9 +150,9 @@
150 150  
151 151  It will flash:
152 152  
153 -1.  When boot the device in flash mode
163 +1. When boot the device in flash mode
164 +1. Send an uplink packet
154 154  
155 -2.  Send an uplink packet
156 156  
157 157  
158 158  
... ... @@ -272,13 +272,13 @@
272 272  [[image:1657351312545-300.png]]
273 273  
274 274  
275 -(% style="color:blue" %)**Connection:**
285 +**Connection:**
276 276  
277 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
287 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
278 278  
279 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
289 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
280 280  
281 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
291 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
282 282  
283 283  
284 284  In the PC, use below serial tool settings:
... ... @@ -316,10 +316,10 @@
316 316  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
317 317  )))
318 318  * (((
319 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
329 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
320 320  )))
321 321  * (((
322 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
332 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
323 323  )))
324 324  
325 325  (((
... ... @@ -355,16 +355,15 @@
355 355  
356 356  === 2.2.7  Use MQTT protocol to uplink data ===
357 357  
358 -
359 359  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
360 360  
361 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
362 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
363 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
364 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
365 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
366 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
367 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
370 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
371 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
372 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
373 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
374 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
375 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
376 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
368 368  
369 369  [[image:1657352634421-276.png]]
370 370  
... ... @@ -371,7 +371,6 @@
371 371  
372 372  [[image:1657352645687-385.png]]
373 373  
374 -
375 375  (((
376 376  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.
377 377  )))
... ... @@ -385,7 +385,6 @@
385 385  
386 386  === 2.2.8  Use TCP protocol to uplink data ===
387 387  
388 -
389 389  This feature is supported since firmware version v110
390 390  
391 391  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -400,7 +400,6 @@
400 400  
401 401  === 2.2.9  Change Update Interval ===
402 402  
403 -
404 404  User can use below command to change the (% style="color:green" %)**uplink interval**.
405 405  
406 406  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -409,21 +409,13 @@
409 409  
410 410  )))
411 411  
412 -(((
413 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
414 -)))
415 415  
416 -(((
417 -(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
418 -)))
419 419  
420 -
421 -
422 422  == 2.3  Uplink Payload ==
423 423  
424 424  
425 425  (((
426 -N95S31B has different working modes for the connections of different types of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
424 +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.
427 427  )))
428 428  
429 429  
... ... @@ -455,10 +455,10 @@
455 455  
456 456  (% style="color:red" %)
457 457  1. (((
458 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
456 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
459 459  )))
460 460  1. (((
461 -**By default, the device will send an uplink message every 1 hour.**
459 +By default, the device will send an uplink message every 1 hour.
462 462  
463 463  
464 464  
... ... @@ -467,16 +467,14 @@
467 467  
468 468  === 2.3.1  Payload Analyze ===
469 469  
470 -
471 -==== 2.3.1.1  Before Firmware v1.2 ====
472 -
473 -
474 474  N95S31B uplink payload includes in total 21 bytes
475 475  
476 476  
477 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
478 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|=(% style="width: 40px;" %)**6**|=(% style="width: 20px;" %)2|=(% style="width: 20px;" %)**2**|=(% style="width: 60px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 100px;" %)5|=(% style="width: 100px;" %)**2**|=(% style="width: 100px;" %)**2**
479 -|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:162px" %)(((
471 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
472 +|=(% style="width: 60px;" %)(((
473 +**Size(bytes)**
474 +)))|=(% 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**
475 +|(% 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" %)(((
480 480  (((
481 481  Reserve/ Same as NBSN95 CFGMOD=1
482 482  )))
... ... @@ -484,7 +484,7 @@
484 484  (((
485 485  No function here.
486 486  )))
487 -)))|(% style="width:102px" %)(((
483 +)))|(% style="width:77px" %)(((
488 488  (((
489 489  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
490 490  )))
... ... @@ -492,7 +492,7 @@
492 492  (((
493 493  By SHT31
494 494  )))
495 -)))|(% style="width:81px" %)(((
491 +)))|(% style="width:80px" %)(((
496 496  (((
497 497  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
498 498  )))
... ... @@ -503,8 +503,6 @@
503 503  )))
504 504  
505 505  (((
506 -
507 -
508 508  (((
509 509  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
510 510  )))
... ... @@ -514,88 +514,29 @@
514 514  [[image:1657354294009-643.png]]
515 515  
516 516  
517 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
511 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
518 518  
519 -**where:**
513 +* Device ID: 0x724031607457 = 724031607457
514 +* Version: 0x006e=110=1.1.0
520 520  
521 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
516 +* BAT: 0x0ccd = 3277 mV = 3.277V
517 +* Signal: 0x1b = 27
518 +* Model: 0x01 = 1
519 +* 0x00dc000ccc= reserve, ignore in N95S31B
520 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
521 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
522 522  
523 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
524 -
525 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
526 -
527 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
528 -
529 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
530 -
531 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
532 -
533 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
534 -
535 -* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
536 -
537 537  (((
538 538  
525 +)))
539 539  
540 -
527 +(((
541 541  
542 542  )))
543 543  
544 -==== 2.3.1.2 Since Firmware v1.2 ====
545 545  
546 -
547 -In this mode, uplink payload includes 91 bytes in total by default.
548 -
549 -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.
550 -
551 -
552 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
553 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:30px" %)**1**|(% style="width:25px" %)**1**|(% style="width:40px" %)**2**|(% style="width:30px" %)**1**|(% style="width:25px" %)**2**|(% style="width:30px" %)**2**|(% style="width:30px" %)**2**|(% style="width:30px" %)**4**|(% style="width:30px" %)**2**|(% style="width:30px" %)**2**|(% style="width:30px" %)**4**
554 -|=(% style="width: 95px;" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp .....
555 -
556 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
557 -
558 -
559 -[[image:image-20220908154949-1.png]]
560 -
561 -
562 -The payload is ASCII string, representative same HEX:
563 -
564 -**0x (% style="color:red" %)__f868411056758782__ (% style="color:blue" %)__000c__ (% style="color:green" %)__0d0f__ (% style="color:#00b0f0" %)__0c__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__0000__ (% style="color:#a14d07" %)__00__ __0030__ (% style="color:#0020b0" %)__0114__ (% style="color:#420042" %)__0231__ (% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__// //__0112023763199baa__ __0112023263199af6__// //__0111023b631999a7__ **
565 -
566 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
567 -
568 -**where:**
569 -
570 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
571 -
572 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
573 -
574 -* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
575 -
576 -* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
577 -
578 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
579 -
580 -* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
581 -
582 -* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
583 -
584 -* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
585 -
586 -* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
587 -
588 -* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
589 -
590 -* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
591 -
592 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
593 -
594 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
595 -
596 596  === 2.3.2  Device ID ===
597 597  
598 -
599 599  (((
600 600  By default, the Device ID equal to the last 6 bytes of IMEI.
601 601  )))
... ... @@ -602,12 +602,10 @@
602 602  
603 603  (((
604 604  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
605 -
606 -
607 607  )))
608 608  
609 609  (((
610 -(% style="color:blue" %)**Example:**
543 +**Example:**
611 611  )))
612 612  
613 613  (((
... ... @@ -615,28 +615,13 @@
615 615  )))
616 616  
617 617  (((
618 -The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
619 -
620 -
551 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
621 621  )))
622 622  
623 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
624 624  
625 625  
626 -By default, the Device ID equal to the last 15 bits of IMEI.
627 -
628 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
629 -
630 -
631 -(% style="color:blue" %)**Example:**
632 -
633 -AT+DEUI=868411056754138
634 -
635 -
636 -
637 637  === 2.3.3  Version Info ===
638 638  
639 -
640 640  (((
641 641  These bytes include the hardware and software version.
642 642  )))
... ... @@ -664,7 +664,6 @@
664 664  
665 665  === 2.3.4  Battery Info ===
666 666  
667 -
668 668  (((
669 669  Ex1: 0x0B45 = 2885mV
670 670  )))
... ... @@ -677,7 +677,6 @@
677 677  
678 678  === 2.3.5  Signal Strength ===
679 679  
680 -
681 681  (((
682 682  NB-IoT Network signal Strength.
683 683  )))
... ... @@ -710,7 +710,6 @@
710 710  
711 711  === 2.3.6  Temperature & Humidity ===
712 712  
713 -
714 714  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
715 715  
716 716  [[image:image-20220709161741-3.png]]
... ... @@ -729,7 +729,6 @@
729 729  
730 730  == 2.4  Downlink Payload ==
731 731  
732 -
733 733  By default, N95S31B prints the downlink payload to console port.
734 734  
735 735  [[image:image-20220709100028-1.png]]
... ... @@ -780,74 +780,11 @@
780 780  
781 781  
782 782  
783 -== 2.5  Humidity and Temperature alarm function ==
697 +== 2.5  ​Battery Analysis ==
784 784  
699 +=== 2.5.1  ​Battery Type ===
785 785  
786 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
787 787  
788 -
789 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
790 -
791 -
792 -² When min=0, and max≠0, Alarm higher than max
793 -
794 -² When min≠0, and max=0, Alarm lower than min
795 -
796 -² When min≠0 and max≠0, Alarm higher than max or lower than min
797 -
798 -
799 - (% style="color:blue" %)**Example:**
800 -
801 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
802 -
803 -
804 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
805 -
806 -² When min=0, and max≠0, Alarm higher than max
807 -
808 -² When min≠0, and max=0, Alarm lower than min
809 -
810 -² When min≠0 and max≠0, Alarm higher than max or lower than min
811 -
812 -
813 -**~ (% style="color:blue" %)Example:(%%)**
814 -
815 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
816 -
817 -
818 -
819 -== 2.6 Set the number of data to be uploaded and the recording time ==
820 -
821 -
822 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
823 -
824 -* (% style="color:#037691" %)**AT+TR=900**     (%%)~/~/  The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
825 -* (% style="color:#037691" %)**AT+NOUD=8**  (%%)~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
826 -
827 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
828 -
829 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
830 -
831 -
832 -
833 -== 2.7 Read or Clear cached data ==
834 -
835 -
836 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
837 -
838 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
839 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
840 -
841 -[[image:image-20220908163102-2.png]]
842 -
843 -
844 -
845 -== 2.8  ​Battery Analysis ==
846 -
847 -
848 -=== 2.8.1  ​Battery Type ===
849 -
850 -
851 851  (((
852 852  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.
853 853  )))
... ... @@ -870,11 +870,10 @@
870 870  
871 871  
872 872  
873 -=== 2.8.2  Power consumption Analyze ===
724 +=== 2.5.2  Power consumption Analyze ===
874 874  
875 -
876 876  (((
877 -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.
727 +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.
878 878  )))
879 879  
880 880  (((
... ... @@ -882,9 +882,8 @@
882 882  )))
883 883  
884 884  
885 -=== 2.8.3  ​Battery Note ===
735 +=== 2.5.3  ​Battery Note ===
886 886  
887 -
888 888  (((
889 889  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.
890 890  )))
... ... @@ -891,7 +891,7 @@
891 891  
892 892  
893 893  
894 -=== 2.8.4  Replace the battery ===
743 +=== 2.5.4  Replace the battery ===
895 895  
896 896  
897 897  (((
... ... @@ -907,7 +907,6 @@
907 907  
908 908  = 3. ​ Access NB-IoT Module =
909 909  
910 -
911 911  (((
912 912  Users can directly access the AT command set of the NB-IoT module.
913 913  )))
... ... @@ -914,8 +914,6 @@
914 914  
915 915  (((
916 916  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/]] 
917 -
918 -
919 919  )))
920 920  
921 921  [[image:1657333200519-600.png]]
... ... @@ -924,13 +924,11 @@
924 924  
925 925  = 4.  Using the AT Commands =
926 926  
927 -
928 928  == 4.1  Access AT Commands ==
929 929  
775 +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/]]
930 930  
931 -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]]
932 932  
933 -
934 934  AT+<CMD>?  : Help on <CMD>
935 935  
936 936  AT+<CMD>         : Run <CMD>
... ... @@ -970,24 +970,7 @@
970 970  
971 971  AT+SERVADDR  : Server Address
972 972  
973 -AT+TR      : Get or Set record time
974 974  
975 -AT+APN     : Get or set the APN
976 -
977 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
978 -
979 -AT+DNSCFG  : Get or Set DNS Server
980 -
981 -AT+GETSENSORVALUE   : Returns the current sensor measurement
982 -
983 -AT+NOUD      : Get or Set the number of data to be uploaded
984 -
985 -AT+CDP     : Read or Clear cached data
986 -
987 -AT+SHTEMP: Get or Set alarm of temp
988 -
989 -AT+SHHUM: Get or Set alarm of moisture
990 -
991 991  (% style="color:#037691" %)**COAP Management**      
992 992  
993 993  AT+URI            : Resource parameters
... ... @@ -1021,7 +1021,6 @@
1021 1021  
1022 1022  = ​5.  FAQ =
1023 1023  
1024 -
1025 1025  == 5.1 ​ How to Upgrade Firmware ==
1026 1026  
1027 1027  
... ... @@ -1037,7 +1037,7 @@
1037 1037  
1038 1038  
1039 1039  (((
1040 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
866 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
1041 1041  )))
1042 1042  )))
1043 1043  
... ... @@ -1045,7 +1045,6 @@
1045 1045  
1046 1046  = 6.  Trouble Shooting =
1047 1047  
1048 -
1049 1049  == 6.1  ​Connection problem when uploading firmware ==
1050 1050  
1051 1051  
... ... @@ -1061,7 +1061,6 @@
1061 1061  
1062 1062  == 6.2  AT Command input doesn't work ==
1063 1063  
1064 -
1065 1065  (((
1066 1066  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.
1067 1067  
... ... @@ -1111,6 +1111,5 @@
1111 1111  
1112 1112  = 9.  Support =
1113 1113  
1114 -
1115 1115  * 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.
1116 1116  * 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]]
image-20220908154949-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -58.5 KB
Content
image-20220908163102-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -29.7 KB
Content
image-20221009001045-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content

Applications

Navigation

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