Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual
Last modified by Bei Jinggeng on 2024/05/31 09:53
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Edwin - Content
-
... ... @@ -71,8 +71,6 @@ 71 71 * Micro SIM card slot for NB-IoT SIM 72 72 * 8500mAh Battery for long term use 73 73 74 - 75 - 76 76 == 1.3 Specification == 77 77 78 78 ... ... @@ -83,12 +83,12 @@ 83 83 84 84 (% style="color:#037691" %)**NB-IoT Spec:** 85 85 86 -* B1 @H-FDD: 2100MHz 87 -* B3 @H-FDD: 1800MHz 88 -* B8 @H-FDD: 900MHz 89 -* B5 @H-FDD: 850MHz 90 -* B20 @H-FDD: 800MHz 91 -* B28 @H-FDD: 700MHz 84 +* - B1 @H-FDD: 2100MHz 85 +* - B3 @H-FDD: 1800MHz 86 +* - B8 @H-FDD: 900MHz 87 +* - B5 @H-FDD: 850MHz 88 +* - B20 @H-FDD: 800MHz 89 +* - B28 @H-FDD: 700MHz 92 92 93 93 (% style="color:#037691" %)**Battery:** 94 94 ... ... @@ -103,8 +103,6 @@ 103 103 * STOP Mode: 10uA @ 3.3v 104 104 * Max transmit power: 350mA@3.3v 105 105 106 - 107 - 108 108 == 1.4 Applications == 109 109 110 110 ... ... @@ -120,6 +120,7 @@ 120 120 121 121 122 122 119 + 123 123 == 1.5 Pin Definitions == 124 124 125 125 ... ... @@ -204,13 +204,13 @@ 204 204 [[image:image-20220709092052-2.png]] 205 205 206 206 207 - (% style="color:blue" %)**Connection:**204 +**Connection:** 208 208 209 - (% style="background-color:yellow" %) **USB TTL GND <~-~-~-~-> GND**206 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 210 210 211 - **~(% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**208 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 212 212 213 - **~(% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**210 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 214 214 215 215 216 216 In the PC, use below serial tool settings: ... ... @@ -248,10 +248,10 @@ 248 248 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 249 249 ))) 250 250 * ((( 251 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ 248 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 252 252 ))) 253 253 * ((( 254 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ 251 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 255 255 256 256 257 257 ... ... @@ -259,8 +259,6 @@ 259 259 260 260 ((( 261 261 For parameter description, please refer to AT command set 262 - 263 - 264 264 ))) 265 265 266 266 [[image:1657330452568-615.png]] ... ... @@ -269,8 +269,6 @@ 269 269 270 270 ((( 271 271 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. 272 - 273 - 274 274 ))) 275 275 276 276 [[image:1657330472797-498.png]] ... ... @@ -280,9 +280,9 @@ 280 280 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 281 281 282 282 283 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ 284 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ 285 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 276 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 277 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 278 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 286 286 287 287 [[image:1657330501006-241.png]] 288 288 ... ... @@ -294,13 +294,13 @@ 294 294 === 2.2.6 Use MQTT protocol to uplink data === 295 295 296 296 297 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ 298 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ 299 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ 300 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ 301 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ 302 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ 303 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ 290 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 291 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 292 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 293 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 294 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 295 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 296 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 304 304 305 305 [[image:1657249978444-674.png]] 306 306 ... ... @@ -317,8 +317,8 @@ 317 317 === 2.2.7 Use TCP protocol to uplink data === 318 318 319 319 320 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ 321 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ 313 +* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 314 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 322 322 323 323 [[image:image-20220709093918-1.png]] 324 324 ... ... @@ -332,29 +332,24 @@ 332 332 333 333 User can use below command to change the (% style="color:green" %)**uplink interval**. 334 334 335 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ 328 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 336 336 337 337 ((( 338 - 331 +(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.** 339 339 340 - 341 -(% style="color:red" %)**NOTE:** 342 - 343 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** 344 - 345 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:** 333 + 346 346 ))) 347 347 348 - (% style="color:red" %)**By default,thedevicewill sendan uplink messageevery 2 hours. Each Uplink Include 8 setof records inthis 2hour (15 minute interval /record).**336 +**NOTE:When the firmware version is v1.3.2 and later firmware:** 349 349 338 +**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).** 350 350 351 351 352 352 == 2.3 Uplink Payload == 353 353 354 354 355 -=== 2.3.1 v1.3.2 ===344 +=== 2.3.1 Before Firmware 1.3.2 === 356 356 357 - 358 358 In this mode, uplink payload includes in total 14 bytes 359 359 360 360 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) ... ... @@ -364,7 +364,7 @@ 364 364 |(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]] 365 365 366 366 ((( 367 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 355 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 368 368 ))) 369 369 370 370 ... ... @@ -371,70 +371,64 @@ 371 371 [[image:1657331036973-987.png]] 372 372 373 373 362 +((( 363 +The payload is ASCII string, representative same HEX: 364 +))) 374 374 375 -The payload is **ASCII** string, representative same HEX: 366 +((( 367 +0x72403155615900640c6c19029200 where: 368 +))) 376 376 377 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** 370 +* ((( 371 +Device ID: 0x724031556159 = 724031556159 372 +))) 373 +* ((( 374 +Version: 0x0064=100=1.0.0 375 +))) 378 378 379 -**where :** 377 +* ((( 378 +BAT: 0x0c6c = 3180 mV = 3.180V 379 +))) 380 +* ((( 381 +Signal: 0x19 = 25 382 +))) 383 +* ((( 384 +Distance: 0x0292= 658 mm 385 +))) 386 +* ((( 387 +Interrupt: 0x00 = 0 380 380 381 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159 389 + 390 +))) 382 382 383 - * (% style="color:#037691"%)**Version:**(%%)0x0064=100=1.0.0392 +=== **2.3.2 Since firmware v1.3.2** === 384 384 385 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V 386 - 387 -* (% style="color:#037691" %)**Signal:**(%%) 0x19 = 25 388 - 389 -* (% style="color:#037691" %)**Distance:** (%%)0x0292= 658 mm 390 - 391 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 392 - 393 - 394 - 395 -=== 2.3.2 Since firmware v1.3.2 === 396 - 397 - 398 398 In this mode, uplink payload includes 69 bytes in total by default. 399 399 400 400 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. 401 401 402 -(% border="1" style="background-color:#ffffcc; color:green; width:490px" %) 403 -|=(% 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** 404 -|=(% 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....... 398 +|**Size(bytes)**|**8**|2|2|1|1|1|2|4|2|4 399 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Distance|Timestamp|Distance|Timestamp....... 405 405 406 406 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 407 407 408 408 [[image:image-20220908175246-1.png]] 409 409 410 - 411 411 The payload is ASCII string, representative same HEX: 412 412 413 - **0x#00b0f0" %)1e#7030a0" %)01#d60093" %)00(% style="color:#a14d07" %)(% style="color:#0020b0" %)6315537b(% style="color:#663300" %)00396319baf0**407 +0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where: 414 414 415 -**where:** 409 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317 410 +* (% style="color:red" %)Version: 0x0084=132=1.3.2 411 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V 412 +* (% style="color:blue" %)Singal: 0x1e = 30 413 +* (% style="color:red" %)Mod: 0x01 = 1 414 +* Interrupt: 0x00= 0 415 +* Distance: 0x0039= 57 = 57 416 +* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 417 +* Distance,Time stamp : 00396319baf0 418 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,....... 416 416 417 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317 418 - 419 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2 420 - 421 -* (% style="color:#037691" %)**BAT:**(%%) 0x0cf4 = 3316 mV = 3.316V 422 - 423 -* (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 424 - 425 -* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 426 - 427 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 428 - 429 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57 430 - 431 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 432 - 433 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0 434 - 435 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 436 - 437 - 438 438 == 2.4 Payload Explanation and Sensor Interface == 439 439 440 440 ... ... @@ -452,7 +452,7 @@ 452 452 ))) 453 453 454 454 ((( 455 - (% style="color:blue" %)**Example437 +**Example:** 456 456 ))) 457 457 458 458 ((( ... ... @@ -460,23 +460,20 @@ 460 460 ))) 461 461 462 462 ((( 463 -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.445 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 464 464 ))) 465 465 466 466 467 - (% style="color:red" %)**NOTE:449 +**NOTE:When the firmware version is v1.3.2 and later firmware:** 468 468 469 - (% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**451 +By default, the Device ID equal to the last 15 bits of IMEI. 470 470 471 -User can use (% style="color:blue" %)**AT+DEUI**(%%)to set Device ID453 +User can use **AT+DEUI** to set Device ID 472 472 455 +**Example:** 473 473 474 -(% style="color:blue" %)**Example :** 475 - 476 476 AT+DEUI=868411056754138 477 477 478 - 479 - 480 480 === 2.4.2 Version Info === 481 481 482 482 ... ... @@ -571,7 +571,7 @@ 571 571 ))) 572 572 573 573 ((( 574 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/ 553 +(% 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]])**.** 575 575 ))) 576 576 577 577 ... ... @@ -672,14 +672,12 @@ 672 672 ))) 673 673 674 674 654 +== 2.6 Distance alarm function(Since firmware v1.3.2) == 675 675 676 - ==2.6Distance alarm function(Since firmware v1.3.2) ==656 +➢ AT Command: 677 677 658 +AT+ LDDSALARM=min,max 678 678 679 -(% style="color:blue" %)** ➢ AT Command:** 680 - 681 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max** 682 - 683 683 ² When min=0, and max≠0, Alarm higher than max 684 684 685 685 ² When min≠0, and max=0, Alarm lower than min ... ... @@ -686,39 +686,29 @@ 686 686 687 687 ² When min≠0 and max≠0, Alarm higher than max or lower than min 688 688 666 +Example: 689 689 690 - (%style="color:blue"%)** Example:**668 +AT+ LDDSALARM=260,2000 ~/~/ Alarm when distance lower than 260. 691 691 692 -**AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 693 693 671 +== 2.7 Set the number of data to be uploaded and the recording time == 694 694 673 +➢ AT Command: 695 695 696 -= = 2.7Setthe numberofdatatobeuploadedandhe recording time==675 +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) 697 697 677 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 698 698 699 - (%style="color:blue"%)** ➢ AT Command:**679 +== 2.8 Read or Clear cached data == 700 700 701 -* (% 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) 702 -* (% 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. 681 +➢ AT Command: 703 703 704 - hediagrambelowexplainstherelationship between TR, NOUD, andTDC moreclearly**:**683 +AT+CDP ~/~/ Read cached data 705 705 706 -[[image:image-20221009001114-1.png||height="687" width="955"]] 707 - 708 - 709 - 710 -== 2.8 Read or Clear cached data == 711 - 712 - 713 -(% style="color:blue" %)** ➢ AT Command:** 714 - 715 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 716 -* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 717 - 718 718 [[image:image-20220908175333-2.png]] 719 719 687 +AT+CDP=0 ~/~/ Clear cached data 720 720 721 - 722 722 == 2.9 LED Indicator == 723 723 724 724 ... ... @@ -864,90 +864,90 @@ 864 864 See this link for detail: [[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]] 865 865 866 866 867 -AT+<CMD>? : 834 +AT+<CMD>? : Help on <CMD> 868 868 869 -AT+<CMD> : 836 +AT+<CMD> : Run <CMD> 870 870 871 -AT+<CMD>=<value> : 838 +AT+<CMD>=<value> : Set the value 872 872 873 -AT+<CMD>=? : 840 +AT+<CMD>=? : Get the value 874 874 875 875 876 876 (% style="color:#037691" %)**General Commands**(%%) 877 877 878 -AT : 845 +AT : Attention 879 879 880 -AT? : 847 +AT? : Short Help 881 881 882 -ATZ : 849 +ATZ : MCU Reset 883 883 884 -AT+TDC : 851 +AT+TDC : Application Data Transmission Interval 885 885 886 -AT+CFG : 853 +AT+CFG : Print all configurations 887 887 888 -AT+CFGMOD : 855 +AT+CFGMOD : Working mode selection 889 889 890 -AT+INTMOD : 857 +AT+INTMOD : Set the trigger interrupt mode 891 891 892 -AT+5VT : 859 +AT+5VT : Set extend the time of 5V power 893 893 894 -AT+PRO : 861 +AT+PRO : Choose agreement 895 895 896 -AT+WEIGRE : 863 +AT+WEIGRE : Get weight or set weight to 0 897 897 898 -AT+WEIGAP : 865 +AT+WEIGAP : Get or Set the GapValue of weight 899 899 900 -AT+RXDL : 867 +AT+RXDL : Extend the sending and receiving time 901 901 902 -AT+CNTFAC : 869 +AT+CNTFAC : Get or set counting parameters 903 903 904 -AT+SERVADDR : 871 +AT+SERVADDR : Server Address 905 905 906 -AT+TR 873 +AT+TR : Get or Set record time" 907 907 908 -AT+APN : 875 +AT+APN : Get or set the APN 909 909 910 -AT+FBAND : 877 +AT+FBAND : Get or Set whether to automatically modify the frequency band 911 911 912 -AT+DNSCFG : Get or Set DNS Server 879 +AT+DNSCFG : Get or Set DNS Server 913 913 914 -AT+GETSENSORVALUE : 881 +AT+GETSENSORVALUE : Returns the current sensor measurement 915 915 916 -AT+NOUD : 883 +AT+NOUD : Get or Set the number of data to be uploaded 917 917 918 -AT+CDP : 885 +AT+CDP : Read or Clear cached data 919 919 920 -AT+LDDSALARM : 887 +AT+LDDSALARM : Get or Set alarm of distance 921 921 922 922 923 923 (% style="color:#037691" %)**COAP Management** 924 924 925 -AT+URI : 892 +AT+URI : Resource parameters 926 926 927 927 928 928 (% style="color:#037691" %)**UDP Management** 929 929 930 -AT+CFM : 897 +AT+CFM : Upload confirmation mode (only valid for UDP) 931 931 932 932 933 933 (% style="color:#037691" %)**MQTT Management** 934 934 935 -AT+CLIENT 902 +AT+CLIENT : Get or Set MQTT client 936 936 937 -AT+UNAME :Get or Set MQTT Username904 +AT+UNAME : Get or Set MQTT Username 938 938 939 -AT+PWD 906 +AT+PWD : Get or Set MQTT password 940 940 941 -AT+PUBTOPIC :Get or Set MQTT publish topic908 +AT+PUBTOPIC : Get or Set MQTT publish topic 942 942 943 -AT+SUBTOPIC :Get or Set MQTT subscription topic910 +AT+SUBTOPIC : Get or Set MQTT subscription topic 944 944 945 945 946 946 (% style="color:#037691" %)**Information** 947 947 948 -AT+FDR : 915 +AT+FDR : Factory Data Reset 949 949 950 -AT+PWORD : 917 +AT+PWORD : Serial Access Password 951 951 952 952 953 953
- image-20221009001114-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content