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

Summary

Details

Page properties
Content
... ... @@ -70,7 +70,6 @@
70 70  
71 71  
72 72  
73 -
74 74  == 1.3  Specification ==
75 75  
76 76  
... ... @@ -79,8 +79,6 @@
79 79  * Supply Voltage: 2.1v ~~ 3.6v
80 80  * Operating Temperature: -40 ~~ 85°C
81 81  
82 -
83 -
84 84  (% style="color:#037691" %)**NB-IoT Spec:**
85 85  
86 86  * - B1 @H-FDD: 2100MHz
... ... @@ -90,8 +90,6 @@
90 90  * - B20 @H-FDD: 800MHz
91 91  * - B28 @H-FDD: 700MHz
92 92  
93 -
94 -
95 95  (% style="color:#037691" %)**Battery:**
96 96  
97 97  * Li/SOCI2 un-chargeable battery
... ... @@ -102,7 +102,6 @@
102 102  
103 103  
104 104  
105 -
106 106  == ​1.4  Applications ==
107 107  
108 108  
... ... @@ -139,11 +139,11 @@
139 139  
140 140  
141 141  (((
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.
136 +**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.
143 143  )))
144 144  
145 145  (((
146 -2) Flash: work mode, device starts to work and send out console output for further debug
140 +**2) Flash:**  work mode, device starts to work and send out console output for further debug
147 147  )))
148 148  
149 149  
... ... @@ -160,9 +160,9 @@
160 160  
161 161  It will flash:
162 162  
163 -1. When boot the device in flash mode
164 -1. Send an uplink packet
157 +1.  When boot the device in flash mode
165 165  
159 +2.  Send an uplink packet
166 166  
167 167  
168 168  
... ... @@ -326,10 +326,10 @@
326 326  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
327 327  )))
328 328  * (((
329 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
323 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
330 330  )))
331 331  * (((
332 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
326 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
333 333  )))
334 334  
335 335  (((
... ... @@ -365,15 +365,16 @@
365 365  
366 366  === 2.2.7  Use MQTT protocol to uplink data ===
367 367  
362 +
368 368  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
369 369  
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
365 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
366 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
367 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
368 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
369 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
370 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
371 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
377 377  
378 378  [[image:1657352634421-276.png]]
379 379  
... ... @@ -380,6 +380,7 @@
380 380  
381 381  [[image:1657352645687-385.png]]
382 382  
378 +
383 383  (((
384 384  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.
385 385  )))
... ... @@ -393,6 +393,7 @@
393 393  
394 394  === 2.2.8  Use TCP protocol to uplink data ===
395 395  
392 +
396 396  This feature is supported since firmware version v110
397 397  
398 398  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -407,6 +407,7 @@
407 407  
408 408  === 2.2.9  Change Update Interval ===
409 409  
407 +
410 410  User can use below command to change the (% style="color:green" %)**uplink interval**.
411 411  
412 412  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -415,13 +415,21 @@
415 415  
416 416  )))
417 417  
416 +(((
417 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
418 +)))
418 418  
420 +(((
421 +(% 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).**
422 +)))
419 419  
424 +
425 +
420 420  == 2.3  Uplink Payload ==
421 421  
422 422  
423 423  (((
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.
430 +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.
425 425  )))
426 426  
427 427  
... ... @@ -453,10 +453,10 @@
453 453  
454 454  (% style="color:red" %)
455 455  1. (((
456 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
462 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
457 457  )))
458 458  1. (((
459 -By default, the device will send an uplink message every 1 hour.
465 +**By default, the device will send an uplink message every 1 hour.**
460 460  
461 461  
462 462  
... ... @@ -465,14 +465,18 @@
465 465  
466 466  === 2.3.1  Payload Analyze ===
467 467  
474 +
475 +==== 2.3.1.1  Before Firmware v1.2 ====
476 +
477 +
468 468  N95S31B uplink payload includes in total 21 bytes
469 469  
470 470  
471 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
481 +(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:745px" %)
472 472  |=(% style="width: 60px;" %)(((
473 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" %)(((
484 +)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 162px;" %)5|=(% style="width: 102px;" %)**2**|=(% style="width: 81px;" %)**2**
485 +|(% 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" %)(((
476 476  (((
477 477  Reserve/ Same as NBSN95 CFGMOD=1
478 478  )))
... ... @@ -480,7 +480,7 @@
480 480  (((
481 481  No function here.
482 482  )))
483 -)))|(% style="width:77px" %)(((
493 +)))|(% style="width:102px" %)(((
484 484  (((
485 485  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
486 486  )))
... ... @@ -488,7 +488,7 @@
488 488  (((
489 489  By SHT31
490 490  )))
491 -)))|(% style="width:80px" %)(((
501 +)))|(% style="width:81px" %)(((
492 492  (((
493 493  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
494 494  )))
... ... @@ -499,6 +499,8 @@
499 499  )))
500 500  
501 501  (((
512 +
513 +
502 502  (((
503 503  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
504 504  )))
... ... @@ -508,29 +508,90 @@
508 508  [[image:1657354294009-643.png]]
509 509  
510 510  
511 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
523 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
512 512  
513 -* Device ID: 0x724031607457 = 724031607457
514 -* Version: 0x006e=110=1.1.0
525 +**where:**
515 515  
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
527 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
522 522  
529 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
530 +
531 +* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
532 +
533 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
534 +
535 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
536 +
537 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
538 +
539 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
540 +
541 +* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
542 +
523 523  (((
524 524  
525 -)))
526 526  
527 -(((
546 +
528 528  
529 529  )))
530 530  
550 +==== 2.3.1.2 Since Firmware v1.2 ====
531 531  
552 +
553 +In this mode, uplink payload includes 91 bytes in total by default.
554 +
555 +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.
556 +
557 +
558 +(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %)
559 +|(% style="width:95px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:43px" %)**2**|(% style="width:47px" %)**2**|(% style="width:124px" %)**1**|(% style="width:56px" %)**1**|(% style="width:109px" %)**2**|(% style="width:80px" %)**1**|(% style="width:51px" %)**2**|(% style="width:79px" %)**2**|(% style="width:84px" %)**2**|(% style="width:100px" %)**4**|(% style="width:76px" %)**2**|(% style="width:81px" %)**2**|(% style="width:121px" %)**4**
560 +|(% 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 .....
561 +
562 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
563 +
564 +
565 +[[image:image-20220908154949-1.png]]
566 +
567 +
568 +The payload is ASCII string, representative same HEX:
569 +
570 +**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__ **
571 +
572 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
573 +
574 +**where:**
575 +
576 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
577 +
578 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
579 +
580 +* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
581 +
582 +* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
583 +
584 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
585 +
586 +* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
587 +
588 +* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
589 +
590 +* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
591 +
592 +* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
593 +
594 +* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
595 +
596 +* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
597 +
598 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
599 +
600 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
601 +
602 +
603 +
532 532  === 2.3.2  Device ID ===
533 533  
606 +
534 534  (((
535 535  By default, the Device ID equal to the last 6 bytes of IMEI.
536 536  )))
... ... @@ -537,10 +537,12 @@
537 537  
538 538  (((
539 539  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
613 +
614 +
540 540  )))
541 541  
542 542  (((
543 -**Example:**
618 +(% style="color:blue" %)**Example:**
544 544  )))
545 545  
546 546  (((
... ... @@ -548,13 +548,28 @@
548 548  )))
549 549  
550 550  (((
551 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
626 +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.
627 +
628 +
552 552  )))
553 553  
631 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
554 554  
555 555  
634 +By default, the Device ID equal to the last 15 bits of IMEI.
635 +
636 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
637 +
638 +
639 +(% style="color:blue" %)**Example:**
640 +
641 +AT+DEUI=868411056754138
642 +
643 +
644 +
556 556  === 2.3.3  Version Info ===
557 557  
647 +
558 558  (((
559 559  These bytes include the hardware and software version.
560 560  )))
... ... @@ -582,6 +582,7 @@
582 582  
583 583  === 2.3.4  Battery Info ===
584 584  
675 +
585 585  (((
586 586  Ex1: 0x0B45 = 2885mV
587 587  )))
... ... @@ -594,6 +594,7 @@
594 594  
595 595  === 2.3.5  Signal Strength ===
596 596  
688 +
597 597  (((
598 598  NB-IoT Network signal Strength.
599 599  )))
... ... @@ -626,6 +626,7 @@
626 626  
627 627  === 2.3.6  Temperature & Humidity ===
628 628  
721 +
629 629  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
630 630  
631 631  [[image:image-20220709161741-3.png]]
... ... @@ -644,6 +644,7 @@
644 644  
645 645  == 2.4  Downlink Payload ==
646 646  
740 +
647 647  By default, N95S31B prints the downlink payload to console port.
648 648  
649 649  [[image:image-20220709100028-1.png]]
... ... @@ -694,11 +694,74 @@
694 694  
695 695  
696 696  
697 -== 2.5  ​Battery Analysis ==
791 +== 2.5  Humidity and Temperature alarm function ==
698 698  
699 -=== 2.5.1  ​Battery Type ===
700 700  
794 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
701 701  
796 +
797 +(% style="color:#037691" %)**AT+ SHHUM=min,max**
798 +
799 +
800 +² When min=0, and max≠0, Alarm higher than max
801 +
802 +² When min≠0, and max=0, Alarm lower than min
803 +
804 +² When min≠0 and max≠0, Alarm higher than max or lower than min
805 +
806 +
807 + (% style="color:blue" %)**Example:**
808 +
809 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
810 +
811 +
812 +(% style="color:#037691" %)**AT+ SHTEMP=min,max**
813 +
814 +² When min=0, and max≠0, Alarm higher than max
815 +
816 +² When min≠0, and max=0, Alarm lower than min
817 +
818 +² When min≠0 and max≠0, Alarm higher than max or lower than min
819 +
820 +
821 +**~ (% style="color:blue" %)Example:(%%)**
822 +
823 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
824 +
825 +
826 +
827 +== 2.6 Set the number of data to be uploaded and the recording time ==
828 +
829 +
830 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
831 +
832 +* (% 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)
833 +* (% 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.
834 +
835 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
836 +
837 +[[image:image-20221009001045-1.png||height="726" width="1009"]]
838 +
839 +
840 +
841 +== 2.7 Read or Clear cached data ==
842 +
843 +
844 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
845 +
846 +* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
847 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
848 +
849 +[[image:image-20220908163102-2.png]]
850 +
851 +
852 +
853 +== 2.8  ​Battery Analysis ==
854 +
855 +
856 +=== 2.8.1  ​Battery Type ===
857 +
858 +
702 702  (((
703 703  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.
704 704  )))
... ... @@ -721,10 +721,11 @@
721 721  
722 722  
723 723  
724 -=== 2.5.2  Power consumption Analyze ===
881 +=== 2.8.2  Power consumption Analyze ===
725 725  
883 +
726 726  (((
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.
885 +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.
728 728  )))
729 729  
730 730  (((
... ... @@ -732,8 +732,9 @@
732 732  )))
733 733  
734 734  
735 -=== 2.5.3  ​Battery Note ===
893 +=== 2.8.3  ​Battery Note ===
736 736  
895 +
737 737  (((
738 738  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.
739 739  )))
... ... @@ -740,7 +740,7 @@
740 740  
741 741  
742 742  
743 -=== 2.5.4  Replace the battery ===
902 +=== 2.8.4  Replace the battery ===
744 744  
745 745  
746 746  (((
... ... @@ -756,6 +756,7 @@
756 756  
757 757  = 3. ​ Access NB-IoT Module =
758 758  
918 +
759 759  (((
760 760  Users can directly access the AT command set of the NB-IoT module.
761 761  )))
... ... @@ -762,6 +762,8 @@
762 762  
763 763  (((
764 764  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/]] 
925 +
926 +
765 765  )))
766 766  
767 767  [[image:1657333200519-600.png]]
... ... @@ -770,11 +770,13 @@
770 770  
771 771  = 4.  Using the AT Commands =
772 772  
935 +
773 773  == 4.1  Access AT Commands ==
774 774  
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/]]
776 776  
939 +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]]
777 777  
941 +
778 778  AT+<CMD>?  : Help on <CMD>
779 779  
780 780  AT+<CMD>         : Run <CMD>
... ... @@ -814,7 +814,24 @@
814 814  
815 815  AT+SERVADDR  : Server Address
816 816  
981 +AT+TR      : Get or Set record time
817 817  
983 +AT+APN     : Get or set the APN
984 +
985 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
986 +
987 +AT+DNSCFG  : Get or Set DNS Server
988 +
989 +AT+GETSENSORVALUE   : Returns the current sensor measurement
990 +
991 +AT+NOUD      : Get or Set the number of data to be uploaded
992 +
993 +AT+CDP     : Read or Clear cached data
994 +
995 +AT+SHTEMP: Get or Set alarm of temp
996 +
997 +AT+SHHUM: Get or Set alarm of moisture
998 +
818 818  (% style="color:#037691" %)**COAP Management**      
819 819  
820 820  AT+URI            : Resource parameters
... ... @@ -848,6 +848,7 @@
848 848  
849 849  = ​5.  FAQ =
850 850  
1032 +
851 851  == 5.1 ​ How to Upgrade Firmware ==
852 852  
853 853  
... ... @@ -863,7 +863,7 @@
863 863  
864 864  
865 865  (((
866 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
1048 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
867 867  )))
868 868  )))
869 869  
... ... @@ -871,6 +871,7 @@
871 871  
872 872  = 6.  Trouble Shooting =
873 873  
1056 +
874 874  == 6.1  ​Connection problem when uploading firmware ==
875 875  
876 876  
... ... @@ -886,6 +886,7 @@
886 886  
887 887  == 6.2  AT Command input doesn't work ==
888 888  
1072 +
889 889  (((
890 890  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.
891 891  
... ... @@ -935,5 +935,6 @@
935 935  
936 936  = 9.  Support =
937 937  
1122 +
938 938  * 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.
939 939  * 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,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
image-20221009001045-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +282.9 KB
Content

Applications

Navigation

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