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.David - Content
-
... ... @@ -71,6 +71,7 @@ 71 71 * Micro SIM card slot for NB-IoT SIM 72 72 * 8500mAh Battery for long term use 73 73 74 + 74 74 == 1.3 Specification == 75 75 76 76 ... ... @@ -81,12 +81,12 @@ 81 81 82 82 (% style="color:#037691" %)**NB-IoT Spec:** 83 83 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 85 +* - B1 @H-FDD: 2100MHz 86 +* - B3 @H-FDD: 1800MHz 87 +* - B8 @H-FDD: 900MHz 88 +* - B5 @H-FDD: 850MHz 89 +* - B20 @H-FDD: 800MHz 90 +* - B28 @H-FDD: 700MHz 90 90 91 91 (% style="color:#037691" %)**Battery:** 92 92 ... ... @@ -101,6 +101,7 @@ 101 101 * STOP Mode: 10uA @ 3.3v 102 102 * Max transmit power: 350mA@3.3v 103 103 105 + 104 104 == 1.4 Applications == 105 105 106 106 ... ... @@ -116,6 +116,7 @@ 116 116 117 117 118 118 121 + 119 119 == 1.5 Pin Definitions == 120 120 121 121 ... ... @@ -200,13 +200,13 @@ 200 200 [[image:image-20220709092052-2.png]] 201 201 202 202 203 - (% style="color:blue" %)**Connection:**206 +**Connection:** 204 204 205 - (% style="background-color:yellow" %) **USB TTL GND <~-~-~-~-> GND**208 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 206 206 207 - **~(% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**210 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 208 208 209 - **~(% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**212 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 210 210 211 211 212 212 In the PC, use below serial tool settings: ... ... @@ -244,10 +244,10 @@ 244 244 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 245 245 ))) 246 246 * ((( 247 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ 250 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 248 248 ))) 249 249 * ((( 250 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ 253 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 251 251 252 252 253 253 ... ... @@ -255,8 +255,6 @@ 255 255 256 256 ((( 257 257 For parameter description, please refer to AT command set 258 - 259 - 260 260 ))) 261 261 262 262 [[image:1657330452568-615.png]] ... ... @@ -265,8 +265,6 @@ 265 265 266 266 ((( 267 267 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. 268 - 269 - 270 270 ))) 271 271 272 272 [[image:1657330472797-498.png]] ... ... @@ -276,9 +276,9 @@ 276 276 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 277 277 278 278 279 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ 280 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ 281 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 278 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 279 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 280 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 282 282 283 283 [[image:1657330501006-241.png]] 284 284 ... ... @@ -290,13 +290,13 @@ 290 290 === 2.2.6 Use MQTT protocol to uplink data === 291 291 292 292 293 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ 294 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ 295 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ 296 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ 297 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ 298 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ 299 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ 292 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 293 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 294 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 295 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 296 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 297 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 298 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 300 300 301 301 [[image:1657249978444-674.png]] 302 302 ... ... @@ -313,8 +313,8 @@ 313 313 === 2.2.7 Use TCP protocol to uplink data === 314 314 315 315 316 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ 317 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ 315 +* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 316 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 318 318 319 319 [[image:image-20220709093918-1.png]] 320 320 ... ... @@ -328,31 +328,25 @@ 328 328 329 329 User can use below command to change the (% style="color:green" %)**uplink interval**. 330 330 331 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ 330 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 332 332 333 333 ((( 334 - 333 +(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.** 335 335 336 - 337 -(% style="color:red" %)**NOTE:** 338 - 339 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** 340 - 341 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:** 335 + 342 342 ))) 343 343 344 - (% style="color:red" %)**By default,thedevicewill sendan uplink messageevery 2 hours. Each Uplink Include 8 setof records inthis 2hour (15 minute interval /record).**338 +**NOTE:When the firmware version is v1.3.2 and later firmware:** 345 345 340 +**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).** 346 346 347 347 348 348 == 2.3 Uplink Payload == 349 349 350 350 351 -=== 2.3.1 Before Firmware v1.3.2 === 352 - 353 - 354 354 In this mode, uplink payload includes in total 14 bytes 355 355 348 + 356 356 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 357 357 |=(% style="width: 60px;" %)((( 358 358 **Size(bytes)** ... ... @@ -360,7 +360,7 @@ 360 360 |(% 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"]] 361 361 362 362 ((( 363 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 356 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 364 364 ))) 365 365 366 366 ... ... @@ -367,67 +367,64 @@ 367 367 [[image:1657331036973-987.png]] 368 368 369 369 363 +((( 364 +The payload is ASCII string, representative same HEX: 365 +))) 370 370 371 -The payload is **ASCII** string, representative same HEX: 367 +((( 368 +0x72403155615900640c6c19029200 where: 369 +))) 372 372 373 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** 371 +* ((( 372 +Device ID: 0x724031556159 = 724031556159 373 +))) 374 +* ((( 375 +Version: 0x0064=100=1.0.0 376 +))) 374 374 375 -**where :** 378 +* ((( 379 +BAT: 0x0c6c = 3180 mV = 3.180V 380 +))) 381 +* ((( 382 +Signal: 0x19 = 25 383 +))) 384 +* ((( 385 +Distance: 0x0292= 658 mm 386 +))) 387 +* ((( 388 +Interrupt: 0x00 = 0 376 376 377 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159 390 + 391 +))) 378 378 379 -* (% style="color:#037691"%)**Version:**(%%)0x0064=100=1.0.0393 +**NOTE:When the firmware version is v1.3.2 and later firmware:** 380 380 381 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V 382 - 383 -* (% style="color:#037691" %)**Signal:**(%%) 0x19 = 25 384 - 385 -* (% style="color:#037691" %)**Distance:** (%%)0x0292= 658 mm 386 - 387 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 388 - 389 -=== 2.3.2 Since firmware v1.3.2 === 390 - 391 - 392 392 In this mode, uplink payload includes 69 bytes in total by default. 393 393 394 394 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. 395 395 396 -(% border="1" style="background-color:#ffffcc; color:green; width:490px" %) 397 -|=(% 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** 398 -|=(% 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....... 399 +|**Size(bytes)**|**8**|2|2|1|1|1|2|4|2|4 400 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Distance|Timestamp|Distance|Timestamp....... 399 399 400 400 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 401 401 402 402 [[image:image-20220908175246-1.png]] 403 403 404 - 405 405 The payload is ASCII string, representative same HEX: 406 406 407 - **0x#00b0f0" %)1e#7030a0" %)01#d60093" %)00(% style="color:#a14d07" %)(% style="color:#0020b0" %)6315537b(% style="color:#663300" %)00396319baf0**408 +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: 408 408 409 -**where:** 410 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317 411 +* (% style="color:red" %)Version: 0x0084=132=1.3.2 412 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V 413 +* (% style="color:blue" %)Singal: 0x1e = 30 414 +* (% style="color:red" %)Mod: 0x01 = 1 415 +* Interrupt: 0x00= 0 416 +* Distance: 0x0039= 57 = 57 417 +* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 418 +* Distance,Time stamp : 00396319baf0 419 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,....... 410 410 411 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317 412 - 413 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2 414 - 415 -* (% style="color:#037691" %)**BAT:**(%%) 0x0cf4 = 3316 mV = 3.316V 416 - 417 -* (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 418 - 419 -* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 420 - 421 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 422 - 423 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57 424 - 425 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 426 - 427 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0 428 - 429 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 430 - 431 431 == 2.4 Payload Explanation and Sensor Interface == 432 432 433 433 ... ... @@ -445,7 +445,7 @@ 445 445 ))) 446 446 447 447 ((( 448 - (% style="color:blue" %)**Example438 +**Example:** 449 449 ))) 450 450 451 451 ((( ... ... @@ -453,23 +453,20 @@ 453 453 ))) 454 454 455 455 ((( 456 -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.446 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 457 457 ))) 458 458 459 459 460 - (% style="color:red" %)**NOTE:450 +**NOTE:When the firmware version is v1.3.2 and later firmware:** 461 461 462 - (% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**452 +By default, the Device ID equal to the last 15 bits of IMEI. 463 463 464 -User can use (% style="color:blue" %)**AT+DEUI**(%%)to set Device ID454 +User can use **AT+DEUI** to set Device ID 465 465 456 +**Example:** 466 466 467 -(% style="color:blue" %)**Example :** 468 - 469 469 AT+DEUI=868411056754138 470 470 471 - 472 - 473 473 === 2.4.2 Version Info === 474 474 475 475 ... ... @@ -564,7 +564,7 @@ 564 564 ))) 565 565 566 566 ((( 567 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/ 554 +(% 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]])**.** 568 568 ))) 569 569 570 570 ... ... @@ -665,14 +665,12 @@ 665 665 ))) 666 666 667 667 655 +== 2.6 Distance alarm function == 668 668 669 - ==2.6Distance alarm function(Since firmware v1.3.2) ==657 +➢ AT Command: 670 670 659 +AT+ LDDSALARM=min,max 671 671 672 -(% style="color:blue" %)** ➢ AT Command:** 673 - 674 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max** 675 - 676 676 ² When min=0, and max≠0, Alarm higher than max 677 677 678 678 ² When min≠0, and max=0, Alarm lower than min ... ... @@ -679,39 +679,29 @@ 679 679 680 680 ² When min≠0 and max≠0, Alarm higher than max or lower than min 681 681 667 +Example: 682 682 683 - (%style="color:blue"%)** Example:**669 +AT+ LDDSALARM=260,2000 ~/~/ Alarm when distance lower than 260. 684 684 685 -**AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 686 686 672 +== 2.7 Set the number of data to be uploaded and the recording time == 687 687 674 +➢ AT Command: 688 688 689 -= = 2.7Setthe numberofdatatobeuploadedandhe recording time==676 +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) 690 690 678 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 691 691 692 - (%style="color:blue"%)** ➢ AT Command:**680 +== 2.8 Read or Clear cached data == 693 693 694 -* (% 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) 695 -* (% 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. 682 +➢ AT Command: 696 696 697 - hediagrambelowexplainstherelationship between TR, NOUD, andTDC moreclearly**:**684 +AT+CDP ~/~/ Read cached data 698 698 699 -[[image:image-20221009001114-1.png||height="687" width="955"]] 700 - 701 - 702 - 703 -== 2.8 Read or Clear cached data == 704 - 705 - 706 -(% style="color:blue" %)** ➢ AT Command:** 707 - 708 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 709 -* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 710 - 711 711 [[image:image-20220908175333-2.png]] 712 712 688 +AT+CDP=0 ~/~/ Clear cached data 713 713 714 - 715 715 == 2.9 LED Indicator == 716 716 717 717 ... ... @@ -746,13 +746,91 @@ 746 746 747 747 748 748 749 -== 2.11 & Power Consumption==724 +== 2.11 Battery Analysis == 750 750 751 751 752 - PS-LB-NAuses ER26500 + SPC1520 battery pack.See below link for detail information aboutthebatteryinfo and how to replace.727 +=== 2.11.1 Battery Type === 753 753 754 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 755 755 730 +((( 731 +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. 732 +))) 733 + 734 +((( 735 +The battery is designed to last for several years depends on the actually use environment and update interval. 736 +))) 737 + 738 +((( 739 +The battery related documents as below: 740 +))) 741 + 742 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 743 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 744 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 745 + 746 +((( 747 +[[image:image-20220709101450-2.png]] 748 +))) 749 + 750 + 751 + 752 +=== 2.11.2 Power consumption Analyze === 753 + 754 + 755 +((( 756 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval. 757 +))) 758 + 759 + 760 +((( 761 +Instruction to use as below: 762 +))) 763 + 764 +((( 765 +(% style="color:blue" %)**Step 1: **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]] 766 +))) 767 + 768 + 769 +((( 770 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 771 +))) 772 + 773 +* ((( 774 +Product Model 775 +))) 776 +* ((( 777 +Uplink Interval 778 +))) 779 +* ((( 780 +Working Mode 781 +))) 782 + 783 +((( 784 +And the Life expectation in difference case will be shown on the right. 785 +))) 786 + 787 +[[image:image-20220709110451-3.png]] 788 + 789 + 790 + 791 +=== 2.11.3 Battery Note === 792 + 793 + 794 +((( 795 +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 transmit LoRa, then the battery life may be decreased. 796 +))) 797 + 798 + 799 + 800 +=== 2.11.4 Replace the battery === 801 + 802 + 803 +((( 804 +The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes). 805 +))) 806 + 807 + 808 + 756 756 = 3. Access NB-IoT Module = 757 757 758 758 ... ... @@ -779,90 +779,90 @@ 779 779 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]] 780 780 781 781 782 -AT+<CMD>? : 835 +AT+<CMD>? : Help on <CMD> 783 783 784 -AT+<CMD> : 837 +AT+<CMD> : Run <CMD> 785 785 786 -AT+<CMD>=<value> : 839 +AT+<CMD>=<value> : Set the value 787 787 788 -AT+<CMD>=? : 841 +AT+<CMD>=? : Get the value 789 789 790 790 791 791 (% style="color:#037691" %)**General Commands**(%%) 792 792 793 -AT : 846 +AT : Attention 794 794 795 -AT? : 848 +AT? : Short Help 796 796 797 -ATZ : 850 +ATZ : MCU Reset 798 798 799 -AT+TDC : 852 +AT+TDC : Application Data Transmission Interval 800 800 801 -AT+CFG : 854 +AT+CFG : Print all configurations 802 802 803 -AT+CFGMOD : 856 +AT+CFGMOD : Working mode selection 804 804 805 -AT+INTMOD : 858 +AT+INTMOD : Set the trigger interrupt mode 806 806 807 -AT+5VT : 860 +AT+5VT : Set extend the time of 5V power 808 808 809 -AT+PRO : 862 +AT+PRO : Choose agreement 810 810 811 -AT+WEIGRE : 864 +AT+WEIGRE : Get weight or set weight to 0 812 812 813 -AT+WEIGAP : 866 +AT+WEIGAP : Get or Set the GapValue of weight 814 814 815 -AT+RXDL : 868 +AT+RXDL : Extend the sending and receiving time 816 816 817 -AT+CNTFAC : 870 +AT+CNTFAC : Get or set counting parameters 818 818 819 -AT+SERVADDR : 872 +AT+SERVADDR : Server Address 820 820 821 -AT+TR 874 +AT+TR : Get or Set record time" 822 822 823 -AT+APN : 876 +AT+APN : Get or set the APN 824 824 825 -AT+FBAND : 878 +AT+FBAND : Get or Set whether to automatically modify the frequency band 826 826 827 -AT+DNSCFG : Get or Set DNS Server 880 +AT+DNSCFG : Get or Set DNS Server 828 828 829 -AT+GETSENSORVALUE : 882 +AT+GETSENSORVALUE : Returns the current sensor measurement 830 830 831 -AT+NOUD : 884 +AT+NOUD : Get or Set the number of data to be uploaded 832 832 833 -AT+CDP : 886 +AT+CDP : Read or Clear cached data 834 834 835 -AT+LDDSALARM : 888 +AT+LDDSALARM : Get or Set alarm of distance 836 836 837 837 838 838 (% style="color:#037691" %)**COAP Management** 839 839 840 -AT+URI : 893 +AT+URI : Resource parameters 841 841 842 842 843 843 (% style="color:#037691" %)**UDP Management** 844 844 845 -AT+CFM : 898 +AT+CFM : Upload confirmation mode (only valid for UDP) 846 846 847 847 848 848 (% style="color:#037691" %)**MQTT Management** 849 849 850 -AT+CLIENT 903 +AT+CLIENT : Get or Set MQTT client 851 851 852 -AT+UNAME :Get or Set MQTT Username905 +AT+UNAME : Get or Set MQTT Username 853 853 854 -AT+PWD 907 +AT+PWD : Get or Set MQTT password 855 855 856 -AT+PUBTOPIC :Get or Set MQTT publish topic909 +AT+PUBTOPIC : Get or Set MQTT publish topic 857 857 858 -AT+SUBTOPIC :Get or Set MQTT subscription topic911 +AT+SUBTOPIC : Get or Set MQTT subscription topic 859 859 860 860 861 861 (% style="color:#037691" %)**Information** 862 862 863 -AT+FDR : 916 +AT+FDR : Factory Data Reset 864 864 865 -AT+PWORD : 918 +AT+PWORD : Serial Access Password 866 866 867 867 868 868
- image-20221009001114-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content