Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 129.2 >
edited by Xiaoling
on 2022/10/14 17:59
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
... ... @@ -70,6 +70,7 @@
70 70  
71 71  
72 72  
73 +
73 73  == 1.3  Specification ==
74 74  
75 75  
... ... @@ -78,6 +78,8 @@
78 78  * Supply Voltage: 2.1v ~~ 3.6v
79 79  * Operating Temperature: -40 ~~ 85°C
80 80  
82 +
83 +
81 81  (% style="color:#037691" %)**NB-IoT Spec:**
82 82  
83 83  * - B1 @H-FDD: 2100MHz
... ... @@ -87,6 +87,8 @@
87 87  * - B20 @H-FDD: 800MHz
88 88  * - B28 @H-FDD: 700MHz
89 89  
93 +
94 +
90 90  (% style="color:#037691" %)**Battery:**
91 91  
92 92  * Li/SOCI2 un-chargeable battery
... ... @@ -97,6 +97,7 @@
97 97  
98 98  
99 99  
105 +
100 100  == ​1.4  Applications ==
101 101  
102 102  
... ... @@ -159,6 +159,7 @@
159 159  
160 160  
161 161  
168 +
162 162  = 2.  Use N95S31B to communicate with IoT Server =
163 163  
164 164  
... ... @@ -319,10 +319,10 @@
319 319  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
320 320  )))
321 321  * (((
322 -(% 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
323 323  )))
324 324  * (((
325 -(% 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
326 326  )))
327 327  
328 328  (((
... ... @@ -358,7 +358,6 @@
358 358  
359 359  === 2.2.7  Use MQTT protocol to uplink data ===
360 360  
361 -
362 362  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
363 363  
364 364  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
... ... @@ -374,7 +374,6 @@
374 374  
375 375  [[image:1657352645687-385.png]]
376 376  
377 -
378 378  (((
379 379  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.
380 380  )))
... ... @@ -388,7 +388,6 @@
388 388  
389 389  === 2.2.8  Use TCP protocol to uplink data ===
390 390  
391 -
392 392  This feature is supported since firmware version v110
393 393  
394 394  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -403,7 +403,6 @@
403 403  
404 404  === 2.2.9  Change Update Interval ===
405 405  
406 -
407 407  User can use below command to change the (% style="color:green" %)**uplink interval**.
408 408  
409 409  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -412,21 +412,13 @@
412 412  
413 413  )))
414 414  
415 -(((
416 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
417 -)))
418 418  
419 -(((
420 -(% 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).**
421 -)))
422 422  
423 -
424 -
425 425  == 2.3  Uplink Payload ==
426 426  
427 427  
428 428  (((
429 -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.
430 430  )))
431 431  
432 432  
... ... @@ -458,10 +458,10 @@
458 458  
459 459  (% style="color:red" %)
460 460  1. (((
461 -**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"]].
462 462  )))
463 463  1. (((
464 -**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.
465 465  
466 466  
467 467  
... ... @@ -470,18 +470,14 @@
470 470  
471 471  === 2.3.1  Payload Analyze ===
472 472  
473 -
474 -==== 2.3.1.1  Before Firmware v1.2 ====
475 -
476 -
477 477  N95S31B uplink payload includes in total 21 bytes
478 478  
479 479  
480 -(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:745px" %)
471 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
481 481  |=(% style="width: 60px;" %)(((
482 482  **Size(bytes)**
483 -)))|=(% 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**
484 -|(% 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" %)(((
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" %)(((
485 485  (((
486 486  Reserve/ Same as NBSN95 CFGMOD=1
487 487  )))
... ... @@ -489,7 +489,7 @@
489 489  (((
490 490  No function here.
491 491  )))
492 -)))|(% style="width:102px" %)(((
483 +)))|(% style="width:77px" %)(((
493 493  (((
494 494  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
495 495  )))
... ... @@ -497,7 +497,7 @@
497 497  (((
498 498  By SHT31
499 499  )))
500 -)))|(% style="width:81px" %)(((
491 +)))|(% style="width:80px" %)(((
501 501  (((
502 502  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
503 503  )))
... ... @@ -508,8 +508,6 @@
508 508  )))
509 509  
510 510  (((
511 -
512 -
513 513  (((
514 514  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
515 515  )))
... ... @@ -519,89 +519,29 @@
519 519  [[image:1657354294009-643.png]]
520 520  
521 521  
522 -The payload is ASCII string, representative same HEX: **0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
511 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
523 523  
524 -**where:**
513 +* Device ID: 0x724031607457 = 724031607457
514 +* Version: 0x006e=110=1.1.0
525 525  
526 -* (% 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
527 527  
528 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
529 -
530 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
531 -
532 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
533 -
534 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
535 -
536 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
537 -
538 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
539 -
540 -* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
541 -
542 542  (((
543 543  
525 +)))
544 544  
545 -
527 +(((
546 546  
547 547  )))
548 548  
549 -==== 2.3.1.2 Since Firmware v1.2 ====
550 550  
551 -
552 -In this mode, uplink payload includes 91 bytes in total by default.
553 -
554 -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.
555 -
556 -
557 -(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %)
558 -|(% 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**
559 -|(% 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 .....
560 -
561 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
562 -
563 -
564 -[[image:image-20220908154949-1.png]]
565 -
566 -
567 -The payload is ASCII string, representative same HEX:
568 -
569 -**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__ __0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
570 -
571 -**where:**
572 -
573 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
574 -
575 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
576 -
577 -* (% style="color:#037691" %)**BAT:**  (%%)0x0d0f = 3343 mV = 3.343V
578 -
579 -* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
580 -
581 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
582 -
583 -* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
584 -
585 -* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
586 -
587 -* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
588 -
589 -* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
590 -
591 -* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
592 -
593 -* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
594 -
595 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
596 -
597 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
598 -
599 -
600 -
601 -
602 602  === 2.3.2  Device ID ===
603 603  
604 -
605 605  (((
606 606  By default, the Device ID equal to the last 6 bytes of IMEI.
607 607  )))
... ... @@ -608,12 +608,10 @@
608 608  
609 609  (((
610 610  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
611 -
612 -
613 613  )))
614 614  
615 615  (((
616 -(% style="color:blue" %)**Example:**
543 +**Example:**
617 617  )))
618 618  
619 619  (((
... ... @@ -621,28 +621,13 @@
621 621  )))
622 622  
623 623  (((
624 -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.
625 -
626 -
551 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
627 627  )))
628 628  
629 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
630 630  
631 631  
632 -By default, the Device ID equal to the last 15 bits of IMEI.
633 -
634 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
635 -
636 -
637 -(% style="color:blue" %)**Example:**
638 -
639 -AT+DEUI=868411056754138
640 -
641 -
642 -
643 643  === 2.3.3  Version Info ===
644 644  
645 -
646 646  (((
647 647  These bytes include the hardware and software version.
648 648  )))
... ... @@ -670,7 +670,6 @@
670 670  
671 671  === 2.3.4  Battery Info ===
672 672  
673 -
674 674  (((
675 675  Ex1: 0x0B45 = 2885mV
676 676  )))
... ... @@ -683,7 +683,6 @@
683 683  
684 684  === 2.3.5  Signal Strength ===
685 685  
686 -
687 687  (((
688 688  NB-IoT Network signal Strength.
689 689  )))
... ... @@ -716,7 +716,6 @@
716 716  
717 717  === 2.3.6  Temperature & Humidity ===
718 718  
719 -
720 720  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
721 721  
722 722  [[image:image-20220709161741-3.png]]
... ... @@ -735,7 +735,6 @@
735 735  
736 736  == 2.4  Downlink Payload ==
737 737  
738 -
739 739  By default, N95S31B prints the downlink payload to console port.
740 740  
741 741  [[image:image-20220709100028-1.png]]
... ... @@ -786,74 +786,11 @@
786 786  
787 787  
788 788  
789 -== 2.5  Humidity and Temperature alarm function ==
697 +== 2.5  ​Battery Analysis ==
790 790  
699 +=== 2.5.1  ​Battery Type ===
791 791  
792 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
793 793  
794 -
795 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
796 -
797 -
798 -² When min=0, and max≠0, Alarm higher than max
799 -
800 -² When min≠0, and max=0, Alarm lower than min
801 -
802 -² When min≠0 and max≠0, Alarm higher than max or lower than min
803 -
804 -
805 - (% style="color:blue" %)**Example:**
806 -
807 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
808 -
809 -
810 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
811 -
812 -² When min=0, and max≠0, Alarm higher than max
813 -
814 -² When min≠0, and max=0, Alarm lower than min
815 -
816 -² When min≠0 and max≠0, Alarm higher than max or lower than min
817 -
818 -
819 -**~ (% style="color:blue" %)Example:(%%)**
820 -
821 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
822 -
823 -
824 -
825 -== 2.6 Set the number of data to be uploaded and the recording time ==
826 -
827 -
828 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
829 -
830 -* (% 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)
831 -* (% 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.
832 -
833 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
834 -
835 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
836 -
837 -
838 -
839 -== 2.7 Read or Clear cached data ==
840 -
841 -
842 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
843 -
844 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
845 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
846 -
847 -[[image:image-20220908163102-2.png]]
848 -
849 -
850 -
851 -== 2.8  ​Battery Analysis ==
852 -
853 -
854 -=== 2.8.1  ​Battery Type ===
855 -
856 -
857 857  (((
858 858  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.
859 859  )))
... ... @@ -876,11 +876,10 @@
876 876  
877 877  
878 878  
879 -=== 2.8.2  Power consumption Analyze ===
724 +=== 2.5.2  Power consumption Analyze ===
880 880  
881 -
882 882  (((
883 -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.
884 884  )))
885 885  
886 886  (((
... ... @@ -888,9 +888,8 @@
888 888  )))
889 889  
890 890  
891 -=== 2.8.3  ​Battery Note ===
735 +=== 2.5.3  ​Battery Note ===
892 892  
893 -
894 894  (((
895 895  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.
896 896  )))
... ... @@ -897,7 +897,7 @@
897 897  
898 898  
899 899  
900 -=== 2.8.4  Replace the battery ===
743 +=== 2.5.4  Replace the battery ===
901 901  
902 902  
903 903  (((
... ... @@ -913,7 +913,6 @@
913 913  
914 914  = 3. ​ Access NB-IoT Module =
915 915  
916 -
917 917  (((
918 918  Users can directly access the AT command set of the NB-IoT module.
919 919  )))
... ... @@ -920,8 +920,6 @@
920 920  
921 921  (((
922 922  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/]] 
923 -
924 -
925 925  )))
926 926  
927 927  [[image:1657333200519-600.png]]
... ... @@ -930,13 +930,11 @@
930 930  
931 931  = 4.  Using the AT Commands =
932 932  
933 -
934 934  == 4.1  Access AT Commands ==
935 935  
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/]]
936 936  
937 -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]]
938 938  
939 -
940 940  AT+<CMD>?  : Help on <CMD>
941 941  
942 942  AT+<CMD>         : Run <CMD>
... ... @@ -976,24 +976,7 @@
976 976  
977 977  AT+SERVADDR  : Server Address
978 978  
979 -AT+TR      : Get or Set record time
980 980  
981 -AT+APN     : Get or set the APN
982 -
983 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
984 -
985 -AT+DNSCFG  : Get or Set DNS Server
986 -
987 -AT+GETSENSORVALUE   : Returns the current sensor measurement
988 -
989 -AT+NOUD      : Get or Set the number of data to be uploaded
990 -
991 -AT+CDP     : Read or Clear cached data
992 -
993 -AT+SHTEMP: Get or Set alarm of temp
994 -
995 -AT+SHHUM: Get or Set alarm of moisture
996 -
997 997  (% style="color:#037691" %)**COAP Management**      
998 998  
999 999  AT+URI            : Resource parameters
... ... @@ -1027,7 +1027,6 @@
1027 1027  
1028 1028  = ​5.  FAQ =
1029 1029  
1030 -
1031 1031  == 5.1 ​ How to Upgrade Firmware ==
1032 1032  
1033 1033  
... ... @@ -1043,7 +1043,7 @@
1043 1043  
1044 1044  
1045 1045  (((
1046 -(% 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.
1047 1047  )))
1048 1048  )))
1049 1049  
... ... @@ -1051,7 +1051,6 @@
1051 1051  
1052 1052  = 6.  Trouble Shooting =
1053 1053  
1054 -
1055 1055  == 6.1  ​Connection problem when uploading firmware ==
1056 1056  
1057 1057  
... ... @@ -1067,7 +1067,6 @@
1067 1067  
1068 1068  == 6.2  AT Command input doesn't work ==
1069 1069  
1070 -
1071 1071  (((
1072 1072  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.
1073 1073  
... ... @@ -1117,6 +1117,5 @@
1117 1117  
1118 1118  = 9.  Support =
1119 1119  
1120 -
1121 1121  * 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.
1122 1122  * 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