Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. David1 +XWiki.Xiaoling - 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 ... ... @@ -108,7 +108,6 @@ 108 108 109 109 110 110 111 - 112 112 == 1.5 Pin Definitions & Switch == 113 113 114 114 ... ... @@ -154,6 +154,9 @@ 154 154 1. When boot the device in flash mode 155 155 1. Send an uplink packet 156 156 166 + 167 + 168 + 157 157 = 2. Use N95S31B to communicate with IoT Server = 158 158 159 159 ... ... @@ -353,7 +353,6 @@ 353 353 354 354 === 2.2.7 Use MQTT protocol to uplink data === 355 355 356 - 357 357 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 358 358 359 359 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink ... ... @@ -369,7 +369,6 @@ 369 369 370 370 [[image:1657352645687-385.png]] 371 371 372 - 373 373 ((( 374 374 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. 375 375 ))) ... ... @@ -383,7 +383,6 @@ 383 383 384 384 === 2.2.8 Use TCP protocol to uplink data === 385 385 386 - 387 387 This feature is supported since firmware version v110 388 388 389 389 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -398,7 +398,6 @@ 398 398 399 399 === 2.2.9 Change Update Interval === 400 400 401 - 402 402 User can use below command to change the (% style="color:green" %)**uplink interval**. 403 403 404 404 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -407,21 +407,13 @@ 407 407 408 408 ))) 409 409 410 -((( 411 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 412 -))) 413 413 414 -((( 415 -(% 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).** 416 -))) 417 417 418 - 419 - 420 420 == 2.3 Uplink Payload == 421 421 422 422 423 423 ((( 424 -N95S31B has different working mode sfor the connections of different typesof 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. 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"]].**456 +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.**459 +By default, the device will send an uplink message every 1 hour. 460 460 461 461 462 462 ... ... @@ -465,18 +465,14 @@ 465 465 466 466 === 2.3.1 Payload Analyze === 467 467 468 - 469 -==== 2.3.1.1 Before Firmware v1.2 ==== 470 - 471 - 472 472 N95S31B uplink payload includes in total 21 bytes 473 473 474 474 475 -(% border=" 2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %)471 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 476 476 |=(% style="width: 60px;" %)((( 477 477 **Size(bytes)** 478 -)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 174px;" %)5|=(% style="width:106px;" %)**2**|=(% style="width:85px;" %)**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:174px" %)(((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: 106px" %)(((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:8 5px" %)(((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 ))) ... ... @@ -516,81 +516,27 @@ 516 516 517 517 The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 518 518 519 -* Device ID: 0x724031607457 = 724031607457 513 +* Device ID: 0x724031607457 = 724031607457 514 +* Version: 0x006e=110=1.1.0 520 520 521 -* Version: 0x006e=110=1.1.0 522 - 523 -* BAT: 0x0ccd = 3277 mV = 3.277V 524 - 525 -* Signal: 0x1b = 27 526 - 527 -* Model: 0x01 = 1 528 - 516 +* BAT: 0x0ccd = 3277 mV = 3.277V 517 +* Signal: 0x1b = 27 518 +* Model: 0x01 = 1 529 529 * 0x00dc000ccc= reserve, ignore in N95S31B 520 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 521 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 530 530 531 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 532 - 533 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 534 - 535 535 ((( 536 536 525 +))) 537 537 538 - 527 +((( 539 539 540 540 ))) 541 541 542 -==== 2.3.1.2 Since Firmware v1.2 ==== 543 543 544 - 545 -In this mode, uplink payload includes 91 bytes in total by default. 546 - 547 -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. 548 - 549 - 550 -(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %) 551 -|(% 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** 552 -|(% 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 ..... 553 - 554 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 555 - 556 - 557 -[[image:image-20220908154949-1.png]] 558 - 559 - 560 -The payload is ASCII string, representative same HEX: 561 - 562 -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: 563 - 564 -* (% style="color:red" %)Device ID: f868411056758782 = f868411056758782 565 - 566 -* (% style="color:blue" %)Version: 0x000c=120=1.2 567 - 568 -* (% style="color:green" %)BAT: 0x0d0f = 3343 mV = 3.343V 569 - 570 -* (% style="color:red" %)Singal: 0x0c = 12 571 - 572 -* (% style="color:blue" %)Mod: 0x01 = 1 573 - 574 -* TemDS18B20: 0x0000= 0 = 0 575 - 576 -* (% style="color:green" %)Interrupt: 0x00= 0 577 - 578 -* (% style="color:green" %)adc: 0x0030= 48 579 - 580 -* SHTTEM: 0x0114= 276 = 27.6 581 - 582 -* SHTHUM:0x0231 =561=56.1% 583 - 584 -* (% style="color:red" %)Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 585 - 586 -* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12 587 - 588 -* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,....... 589 - 590 - 591 591 === 2.3.2 Device ID === 592 592 593 - 594 594 ((( 595 595 By default, the Device ID equal to the last 6 bytes of IMEI. 596 596 ))) ... ... @@ -597,12 +597,10 @@ 597 597 598 598 ((( 599 599 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 600 - 601 - 602 602 ))) 603 603 604 604 ((( 605 - (% style="color:blue" %)**Example:**543 +**Example:** 606 606 ))) 607 607 608 608 ((( ... ... @@ -610,28 +610,13 @@ 610 610 ))) 611 611 612 612 ((( 613 -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. 614 - 615 - 551 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 616 616 ))) 617 617 618 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 619 619 620 620 621 -By default, the Device ID equal to the last 15 bits of IMEI. 622 - 623 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 624 - 625 - 626 -**(% style="color:blue" %)Example:(%%)** 627 - 628 -AT+DEUI=868411056754138 629 - 630 - 631 - 632 632 === 2.3.3 Version Info === 633 633 634 - 635 635 ((( 636 636 These bytes include the hardware and software version. 637 637 ))) ... ... @@ -659,7 +659,6 @@ 659 659 660 660 === 2.3.4 Battery Info === 661 661 662 - 663 663 ((( 664 664 Ex1: 0x0B45 = 2885mV 665 665 ))) ... ... @@ -672,7 +672,6 @@ 672 672 673 673 === 2.3.5 Signal Strength === 674 674 675 - 676 676 ((( 677 677 NB-IoT Network signal Strength. 678 678 ))) ... ... @@ -705,7 +705,6 @@ 705 705 706 706 === 2.3.6 Temperature & Humidity === 707 707 708 - 709 709 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 710 710 711 711 [[image:image-20220709161741-3.png]] ... ... @@ -724,7 +724,6 @@ 724 724 725 725 == 2.4 Downlink Payload == 726 726 727 - 728 728 By default, N95S31B prints the downlink payload to console port. 729 729 730 730 [[image:image-20220709100028-1.png]] ... ... @@ -775,71 +775,11 @@ 775 775 776 776 777 777 778 -== 2.5 Humidityand Temperaturealarmfunction==697 +== 2.5 Battery Analysis == 779 779 699 +=== 2.5.1 Battery Type === 780 780 781 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 782 782 783 - 784 -(% style="color:#037691" %)**AT+ SHHUM=min,max** 785 - 786 - 787 -² When min=0, and max≠0, Alarm higher than max 788 - 789 -² When min≠0, and max=0, Alarm lower than min 790 - 791 -² When min≠0 and max≠0, Alarm higher than max or lower than min 792 - 793 - 794 - (% style="color:blue" %)**Example:** 795 - 796 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 797 - 798 - 799 -(% style="color:#037691" %)**AT+ SHTEMP=min,max** 800 - 801 -² When min=0, and max≠0, Alarm higher than max 802 - 803 -² When min≠0, and max=0, Alarm lower than min 804 - 805 -² When min≠0 and max≠0, Alarm higher than max or lower than min 806 - 807 - 808 -**~ (% style="color:blue" %)Example:(%%)** 809 - 810 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 811 - 812 - 813 - 814 -== 2.6 Set the number of data to be uploaded and the recording time == 815 - 816 - 817 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 818 - 819 -* (% 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) 820 -* (% 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. 821 - 822 -This link explains the relationship between TR, NOUD and TDC more clearly **: **[[https:~~/~~/www.processon.com/view/link/6340e606e401fd390891af87>>url:https://www.processon.com/view/link/6340e606e401fd390891af87]] 823 - 824 -== 2.7 Read or Clear cached data == 825 - 826 - 827 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 828 - 829 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 830 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 831 - 832 - 833 -[[image:image-20220908163102-2.png]] 834 - 835 - 836 - 837 -== 2.8 Battery Analysis == 838 - 839 - 840 -=== 2.8.1 Battery Type === 841 - 842 - 843 843 ((( 844 844 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. 845 845 ))) ... ... @@ -862,11 +862,10 @@ 862 862 863 863 864 864 865 -=== 2. 8.2 Power consumption Analyze ===724 +=== 2.5.2 Power consumption Analyze === 866 866 867 - 868 868 ((( 869 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dro pbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]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. 870 870 ))) 871 871 872 872 ((( ... ... @@ -874,9 +874,8 @@ 874 874 ))) 875 875 876 876 877 -=== 2. 8.3 Battery Note ===735 +=== 2.5.3 Battery Note === 878 878 879 - 880 880 ((( 881 881 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. 882 882 ))) ... ... @@ -883,7 +883,7 @@ 883 883 884 884 885 885 886 -=== 2. 8.4 Replace the battery ===743 +=== 2.5.4 Replace the battery === 887 887 888 888 889 889 ((( ... ... @@ -899,7 +899,6 @@ 899 899 900 900 = 3. Access NB-IoT Module = 901 901 902 - 903 903 ((( 904 904 Users can directly access the AT command set of the NB-IoT module. 905 905 ))) ... ... @@ -906,8 +906,6 @@ 906 906 907 907 ((( 908 908 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/]] 909 - 910 - 911 911 ))) 912 912 913 913 [[image:1657333200519-600.png]] ... ... @@ -916,13 +916,11 @@ 916 916 917 917 = 4. Using the AT Commands = 918 918 919 - 920 920 == 4.1 Access AT Commands == 921 921 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/]] 922 922 923 -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]] 924 924 925 - 926 926 AT+<CMD>? : Help on <CMD> 927 927 928 928 AT+<CMD> : Run <CMD> ... ... @@ -962,24 +962,7 @@ 962 962 963 963 AT+SERVADDR : Server Address 964 964 965 -AT+TR : Get or Set record time 966 966 967 -AT+APN : Get or set the APN 968 - 969 -AT+FBAND : Get or Set whether to automatically modify the frequency band 970 - 971 -AT+DNSCFG : Get or Set DNS Server 972 - 973 -AT+GETSENSORVALUE : Returns the current sensor measurement 974 - 975 -AT+NOUD : Get or Set the number of data to be uploaded 976 - 977 -AT+CDP : Read or Clear cached data 978 - 979 -AT+SHTEMP: Get or Set alarm of temp 980 - 981 -AT+SHHUM: Get or Set alarm of moisture 982 - 983 983 (% style="color:#037691" %)**COAP Management** 984 984 985 985 AT+URI : Resource parameters ... ... @@ -1013,7 +1013,6 @@ 1013 1013 1014 1014 = 5. FAQ = 1015 1015 1016 - 1017 1017 == 5.1 How to Upgrade Firmware == 1018 1018 1019 1019 ... ... @@ -1029,7 +1029,7 @@ 1029 1029 1030 1030 1031 1031 ((( 1032 -(% 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. 1033 1033 ))) 1034 1034 ))) 1035 1035 ... ... @@ -1037,7 +1037,6 @@ 1037 1037 1038 1038 = 6. Trouble Shooting = 1039 1039 1040 - 1041 1041 == 6.1 Connection problem when uploading firmware == 1042 1042 1043 1043 ... ... @@ -1053,7 +1053,6 @@ 1053 1053 1054 1054 == 6.2 AT Command input doesn't work == 1055 1055 1056 - 1057 1057 ((( 1058 1058 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. 1059 1059 ... ... @@ -1103,9 +1103,5 @@ 1103 1103 1104 1104 = 9. Support = 1105 1105 1106 - 1107 1107 * 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. 1108 1108 * 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]] 1109 - 1110 - 1111 -
- 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