Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual
Last modified by Bei Jinggeng on 2024/05/31 09:53
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 3 removed)
Details
- Page properties
-
- Content
-
... ... @@ -16,7 +16,6 @@ 16 16 17 17 = 1. Introduction = 18 18 19 - 20 20 == 1.1 What is NDDS75 Distance Detection Sensor == 21 21 22 22 ((( ... ... @@ -72,6 +72,7 @@ 72 72 * 8500mAh Battery for long term use 73 73 74 74 74 + 75 75 == 1.3 Specification == 76 76 77 77 ... ... @@ -103,6 +103,7 @@ 103 103 * Max transmit power: 350mA@3.3v 104 104 105 105 106 + 106 106 == 1.4 Applications == 107 107 108 108 ... ... @@ -117,7 +117,6 @@ 117 117 118 118 119 119 120 - 121 121 == 1.5 Pin Definitions == 122 122 123 123 ... ... @@ -127,7 +127,6 @@ 127 127 128 128 = 2. Use NDDS75 to communicate with IoT Server = 129 129 130 - 131 131 == 2.1 How it works == 132 132 133 133 ... ... @@ -201,16 +201,15 @@ 201 201 202 202 [[image:image-20220709092052-2.png]] 203 203 203 +**Connection:** 204 204 205 -(% style="color: blue" %)**Connection:**205 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 206 206 207 - (% style="background-color:yellow" %) **USB TTLGND <~-~-~-~->GND**207 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 208 208 209 - **~(% style="background-color:yellow" %)USB TTLTXD <~-~-~-~-> UART_RXD(%%)**209 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 210 210 211 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 212 212 213 - 214 214 In the PC, use below serial tool settings: 215 215 216 216 * Baud: (% style="color:green" %)**9600** ... ... @@ -225,9 +225,8 @@ 225 225 226 226 [[image:1657329814315-101.png]] 227 227 228 - 229 229 ((( 230 -(% style="color:red" %) **Note: the valid AT Commands can be found at:**(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]**227 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]] 231 231 ))) 232 232 233 233 ... ... @@ -246,29 +246,21 @@ 246 246 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 247 247 ))) 248 248 * ((( 249 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ 246 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 250 250 ))) 251 251 * ((( 252 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 253 - 254 - 255 - 249 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 256 256 ))) 257 257 258 258 ((( 259 259 For parameter description, please refer to AT command set 260 - 261 - 262 262 ))) 263 263 264 264 [[image:1657330452568-615.png]] 265 265 266 266 267 - 268 268 ((( 269 269 After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server. 270 - 271 - 272 272 ))) 273 273 274 274 [[image:1657330472797-498.png]] ... ... @@ -278,9 +278,9 @@ 278 278 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 279 279 280 280 281 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ 282 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ 283 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 270 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 271 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 272 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 284 284 285 285 [[image:1657330501006-241.png]] 286 286 ... ... @@ -292,13 +292,13 @@ 292 292 === 2.2.6 Use MQTT protocol to uplink data === 293 293 294 294 295 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ 296 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ 297 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ 298 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ 299 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ 300 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ 301 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ 284 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 285 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 286 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 287 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 288 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 289 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 290 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 302 302 303 303 [[image:1657249978444-674.png]] 304 304 ... ... @@ -315,8 +315,8 @@ 315 315 === 2.2.7 Use TCP protocol to uplink data === 316 316 317 317 318 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ 319 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ 307 +* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 308 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 320 320 321 321 [[image:image-20220709093918-1.png]] 322 322 ... ... @@ -330,31 +330,24 @@ 330 330 331 331 User can use below command to change the (% style="color:green" %)**uplink interval**. 332 332 333 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ 322 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 334 334 335 335 ((( 336 - 337 - 338 - 339 339 (% style="color:red" %)**NOTE:** 326 +))) 340 340 328 +((( 341 341 (% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** 342 - 343 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:** 344 344 ))) 345 345 346 -(% 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).** 347 347 348 348 349 - 350 350 == 2.3 Uplink Payload == 351 351 352 352 353 -=== 2.3.1 Before Firmware v1.3.2 === 354 - 355 - 356 356 In this mode, uplink payload includes in total 14 bytes 357 357 339 + 358 358 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 359 359 |=(% style="width: 60px;" %)((( 360 360 **Size(bytes)** ... ... @@ -368,70 +368,38 @@ 368 368 369 369 [[image:1657331036973-987.png]] 370 370 371 - 372 - 373 -The payload is **ASCII** string, representative same HEX: 374 - 375 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** 376 - 377 -**where :** 378 - 379 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159 380 - 381 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 382 - 383 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V 384 - 385 -* (% style="color:#037691" %)**Signal:**(%%) 0x19 = 25 386 - 387 -* (% style="color:#037691" %)**Distance:** (%%)0x0292= 658 mm 388 - 389 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 390 - 391 - 392 -=== **2.3.2 Since firmware v1.3.2** === 393 - 394 - 395 -In this mode, uplink payload includes 69 bytes in total by default. 396 - 397 -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. 398 - 399 -(% border="1" style="background-color:#ffffcc; color:green; width:490px" %) 400 -|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:70px" %)**4**|(% style="width:40px" %)**2**|(% style="width:60px" %)**4** 401 -|=(% style="width: 95px;" %)**Value**|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp....... 402 - 403 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 404 - 405 -[[image:image-20220908175246-1.png]] 406 - 407 - 353 +((( 408 408 The payload is ASCII string, representative same HEX: 355 +))) 409 409 410 -**0x (% style="color:red" %)f867787050213317 (% style="color:blue" %)0084 (% style="color:green" %)0cf4 (% style="color:#00b0f0" %)1e (% style="color:#7030a0" %)01 (% style="color:#d60093" %)00(% style="color:#a14d07" %) 0039 (% style="color:#0020b0" %)6315537b (% style="color:#663300" %)00396319baf0 00396319ba3c 00396319b988 00396319b8d4 00396319b820 00396319b76c 00396319b6b8 00396319b604 (%%)** 357 +((( 358 +0x72403155615900640c6c19029200 where: 359 +))) 411 411 412 -**where:** 361 +* ((( 362 +Device ID: 0x724031556159 = 724031556159 363 +))) 364 +* ((( 365 +Version: 0x0064=100=1.0.0 366 +))) 413 413 414 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317 368 +* ((( 369 +BAT: 0x0c6c = 3180 mV = 3.180V 370 +))) 371 +* ((( 372 +Signal: 0x19 = 25 373 +))) 374 +* ((( 375 +Distance: 0x0292= 658 mm 376 +))) 377 +* ((( 378 +Interrupt: 0x00 = 0 415 415 416 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2 417 417 418 -* (% style="color:#037691" %)**BAT:**(%%) 0x0cf4 = 3316 mV = 3.316V 419 419 420 -* (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 382 + 383 +))) 421 421 422 -* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 423 - 424 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 425 - 426 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57 427 - 428 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 429 - 430 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0 431 - 432 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 433 - 434 - 435 435 == 2.4 Payload Explanation and Sensor Interface == 436 436 437 437 ... ... @@ -444,12 +444,10 @@ 444 444 445 445 ((( 446 446 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 447 - 448 - 449 449 ))) 450 450 451 451 ((( 452 - (% style="color:blue" %)**Example400 +**Example:** 453 453 ))) 454 454 455 455 ((( ... ... @@ -457,23 +457,11 @@ 457 457 ))) 458 458 459 459 ((( 460 -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.408 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 461 461 ))) 462 462 463 463 464 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:** 465 465 466 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.** 467 - 468 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 469 - 470 - 471 -(% style="color:blue" %)**Example :** 472 - 473 -AT+DEUI=868411056754138 474 - 475 - 476 - 477 477 === 2.4.2 Version Info === 478 478 479 479 ... ... @@ -568,7 +568,7 @@ 568 568 ))) 569 569 570 570 ((( 571 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/ 507 +(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.** 572 572 ))) 573 573 574 574 ... ... @@ -601,14 +601,10 @@ 601 601 602 602 ((( 603 603 The 5V output time can be controlled by AT Command. 604 - 605 - 606 606 ))) 607 607 608 608 ((( 609 609 (% style="color:blue" %)**AT+5VT=1000** 610 - 611 - 612 612 ))) 613 613 614 614 ((( ... ... @@ -670,55 +670,9 @@ 670 670 671 671 672 672 673 -== 2.6 D istancealarm function(Since firmwarev1.3.2)==605 +== 2.6 LED Indicator == 674 674 675 675 676 -(% style="color:blue" %)** ➢ AT Command:** 677 - 678 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max** 679 - 680 -² When min=0, and max≠0, Alarm higher than max 681 - 682 -² When min≠0, and max=0, Alarm lower than min 683 - 684 -² When min≠0 and max≠0, Alarm higher than max or lower than min 685 - 686 - 687 -(% style="color:blue" %)** Example:** 688 - 689 -**AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 690 - 691 - 692 - 693 -== 2.7 Set the number of data to be uploaded and the recording time == 694 - 695 - 696 -(% style="color:blue" %)** ➢ AT Command:** 697 - 698 -* (% 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) 699 -* (% 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. 700 - 701 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 702 - 703 -[[image:image-20221009001114-1.png||height="687" width="955"]] 704 - 705 - 706 - 707 -== 2.8 Read or Clear cached data == 708 - 709 - 710 -(% style="color:blue" %)** ➢ AT Command:** 711 - 712 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 713 -* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 714 - 715 -[[image:image-20220908175333-2.png]] 716 - 717 - 718 - 719 -== 2.9 LED Indicator == 720 - 721 - 722 722 The NDDS75 has an internal LED which is to show the status of different state. 723 723 724 724 ... ... @@ -733,29 +733,29 @@ 733 733 734 734 735 735 736 -== 2. 10Firmware Change Log ==622 +== 2.7 Firmware Change Log == 737 737 738 738 739 739 ((( 740 -Download URL & Firmware Change log : [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]]626 +Download URL & Firmware Change log 741 741 ))) 742 742 743 743 ((( 744 - 630 +[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]] 745 745 ))) 746 746 633 + 747 747 ((( 748 -Upgrade Instruction: [[Upgrade 635 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 749 749 ))) 750 750 751 751 752 752 753 -== 2. 11Battery Analysis ==640 +== 2.8 Battery Analysis == 754 754 642 +=== 2.8.1 Battery Type === 755 755 756 -=== 2.11.1 Battery Type === 757 757 758 - 759 759 ((( 760 760 The NDDS75 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. 761 761 ))) ... ... @@ -778,7 +778,7 @@ 778 778 779 779 780 780 781 -=== 2. 11.2 Power consumption Analyze ===667 +=== 2.8.2 Power consumption Analyze === 782 782 783 783 784 784 ((( ... ... @@ -817,7 +817,7 @@ 817 817 818 818 819 819 820 -=== 2. 11.3 Battery Note ===706 +=== 2.8.3 Battery Note === 821 821 822 822 823 823 ((( ... ... @@ -826,7 +826,7 @@ 826 826 827 827 828 828 829 -=== 2. 11.4 Replace the battery ===715 +=== 2.8.4 Replace the battery === 830 830 831 831 832 832 ((( ... ... @@ -844,8 +844,6 @@ 844 844 845 845 ((( 846 846 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/]] 847 - 848 - 849 849 ))) 850 850 851 851 [[image:1657333200519-600.png]] ... ... @@ -854,103 +854,85 @@ 854 854 855 855 = 4. Using the AT Commands = 856 856 857 - 858 858 == 4.1 Access AT Commands == 859 859 860 860 861 -See this link for detail: pbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]744 +See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 862 862 863 863 864 -AT+<CMD>? : 747 +AT+<CMD>? : Help on <CMD> 865 865 866 -AT+<CMD> : 749 +AT+<CMD> : Run <CMD> 867 867 868 -AT+<CMD>=<value> : 751 +AT+<CMD>=<value> : Set the value 869 869 870 -AT+<CMD>=? : 753 +AT+<CMD>=? : Get the value 871 871 872 872 873 873 (% style="color:#037691" %)**General Commands**(%%) 874 874 875 -AT : 758 +AT : Attention 876 876 877 -AT? : 760 +AT? : Short Help 878 878 879 -ATZ : 762 +ATZ : MCU Reset 880 880 881 -AT+TDC : 764 +AT+TDC : Application Data Transmission Interval 882 882 883 -AT+CFG : 766 +AT+CFG : Print all configurations 884 884 885 -AT+CFGMOD : 768 +AT+CFGMOD : Working mode selection 886 886 887 -AT+INTMOD : 770 +AT+INTMOD : Set the trigger interrupt mode 888 888 889 -AT+5VT : 772 +AT+5VT : Set extend the time of 5V power 890 890 891 -AT+PRO : 774 +AT+PRO : Choose agreement 892 892 893 -AT+WEIGRE : 776 +AT+WEIGRE : Get weight or set weight to 0 894 894 895 -AT+WEIGAP : 778 +AT+WEIGAP : Get or Set the GapValue of weight 896 896 897 -AT+RXDL : 780 +AT+RXDL : Extend the sending and receiving time 898 898 899 -AT+CNTFAC : 782 +AT+CNTFAC : Get or set counting parameters 900 900 901 -AT+SERVADDR : 784 +AT+SERVADDR : Server Address 902 902 903 -AT+TR : Get or Set record time" 904 904 905 -AT+APN : Get or set the APN 906 - 907 -AT+FBAND : Get or Set whether to automatically modify the frequency band 908 - 909 -AT+DNSCFG : Get or Set DNS Server 910 - 911 -AT+GETSENSORVALUE : Returns the current sensor measurement 912 - 913 -AT+NOUD : Get or Set the number of data to be uploaded 914 - 915 -AT+CDP : Read or Clear cached data 916 - 917 -AT+LDDSALARM : Get or Set alarm of distance 918 - 919 - 920 920 (% style="color:#037691" %)**COAP Management** 921 921 922 -AT+URI : 789 +AT+URI : Resource parameters 923 923 924 924 925 925 (% style="color:#037691" %)**UDP Management** 926 926 927 -AT+CFM : 794 +AT+CFM : Upload confirmation mode (only valid for UDP) 928 928 929 929 930 930 (% style="color:#037691" %)**MQTT Management** 931 931 932 -AT+CLIENT 799 +AT+CLIENT : Get or Set MQTT client 933 933 934 -AT+UNAME :Get or Set MQTT Username801 +AT+UNAME : Get or Set MQTT Username 935 935 936 -AT+PWD 803 +AT+PWD : Get or Set MQTT password 937 937 938 -AT+PUBTOPIC :Get or Set MQTT publish topic805 +AT+PUBTOPIC : Get or Set MQTT publish topic 939 939 940 -AT+SUBTOPIC :Get or Set MQTT subscription topic807 +AT+SUBTOPIC : Get or Set MQTT subscription topic 941 941 942 942 943 943 (% style="color:#037691" %)**Information** 944 944 945 -AT+FDR : 812 +AT+FDR : Factory Data Reset 946 946 947 -AT+PWORD : 814 +AT+PWORD : Serial Access Password 948 948 949 949 950 950 951 951 = 5. FAQ = 952 952 953 - 954 954 == 5.1 How to Upgrade Firmware == 955 955 956 956 ... ... @@ -970,7 +970,6 @@ 970 970 971 971 = 6. Trouble Shooting = 972 972 973 - 974 974 == 6.1 Connection problem when uploading firmware == 975 975 976 976 ... ... @@ -1019,7 +1019,6 @@ 1019 1019 ((( 1020 1020 1021 1021 1022 - 1023 1023 (% style="color:#037691" %)**Dimension and weight**: 1024 1024 1025 1025 * Device Size: 13.0 x 5 x 4.5 cm
- image-20220908175246-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -55.7 KB - Content
- image-20220908175333-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.1 KB - Content
- image-20221009001114-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content