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)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. David1 +XWiki.Edwin - Content
-
... ... @@ -71,7 +71,6 @@ 71 71 * Micro SIM card slot for NB-IoT SIM 72 72 * 8500mAh Battery for long term use 73 73 74 - 75 75 == 1.3 Specification == 76 76 77 77 ... ... @@ -102,7 +102,6 @@ 102 102 * STOP Mode: 10uA @ 3.3v 103 103 * Max transmit power: 350mA@3.3v 104 104 105 - 106 106 == 1.4 Applications == 107 107 108 108 ... ... @@ -203,13 +203,13 @@ 203 203 [[image:image-20220709092052-2.png]] 204 204 205 205 206 - (% style="color:blue" %)**Connection:**204 +**Connection:** 207 207 208 - (% style="background-color:yellow" %) **USB TTL GND <~-~-~-~-> GND**206 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 209 209 210 - **~(% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**208 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 211 211 212 - **~(% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**210 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 213 213 214 214 215 215 In the PC, use below serial tool settings: ... ... @@ -247,10 +247,10 @@ 247 247 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 248 248 ))) 249 249 * ((( 250 -(% 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 251 251 ))) 252 252 * ((( 253 -(% 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 254 254 255 255 256 256 ... ... @@ -258,8 +258,6 @@ 258 258 259 259 ((( 260 260 For parameter description, please refer to AT command set 261 - 262 - 263 263 ))) 264 264 265 265 [[image:1657330452568-615.png]] ... ... @@ -268,8 +268,6 @@ 268 268 269 269 ((( 270 270 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. 271 - 272 - 273 273 ))) 274 274 275 275 [[image:1657330472797-498.png]] ... ... @@ -279,11 +279,10 @@ 279 279 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 280 280 281 281 282 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ 283 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ 284 -* (% 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 285 285 286 - 287 287 [[image:1657330501006-241.png]] 288 288 289 289 ... ... @@ -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" %) ... ... @@ -372,7 +372,7 @@ 372 372 373 373 374 374 ((( 375 -The payload is **ASCII**string, representative same HEX:363 +The payload is ASCII string, representative same HEX: 376 376 ))) 377 377 378 378 ((( ... ... @@ -383,11 +383,11 @@ 383 383 Device ID: 0x724031556159 = 724031556159 384 384 ))) 385 385 * ((( 386 -Version: 374 +Version: 0x0064=100=1.0.0 387 387 ))) 388 388 389 389 * ((( 390 -BAT: 378 +BAT: 0x0c6c = 3180 mV = 3.180V 391 391 ))) 392 392 * ((( 393 393 Signal: 0x19 = 25 ... ... @@ -398,28 +398,22 @@ 398 398 * ((( 399 399 Interrupt: 0x00 = 0 400 400 401 - 402 - 403 - 404 404 405 405 ))) 406 406 407 -=== **2.3.2 392 +=== **2.3.2 Since firmware v1.3.2** === 408 408 409 - 410 410 In this mode, uplink payload includes 69 bytes in total by default. 411 411 412 412 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. 413 413 414 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %) 415 -|(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4 416 -|(% 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....... 417 417 418 418 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 419 419 420 420 [[image:image-20220908175246-1.png]] 421 421 422 - 423 423 The payload is ASCII string, representative same HEX: 424 424 425 425 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: ... ... @@ -435,7 +435,6 @@ 435 435 * Distance,Time stamp : 00396319baf0 436 436 * (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,....... 437 437 438 - 439 439 == 2.4 Payload Explanation and Sensor Interface == 440 440 441 441 ... ... @@ -453,7 +453,7 @@ 453 453 ))) 454 454 455 455 ((( 456 - (% style="color:blue" %)**Example437 +**Example:** 457 457 ))) 458 458 459 459 ((( ... ... @@ -461,23 +461,20 @@ 461 461 ))) 462 462 463 463 ((( 464 -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. 465 465 ))) 466 466 467 467 468 - (% style="color:red" %)**NOTE:449 +**NOTE:When the firmware version is v1.3.2 and later firmware:** 469 469 470 - (% 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. 471 471 472 -User can use (% style="color:blue" %)**AT+DEUI**(%%)to set Device ID453 +User can use **AT+DEUI** to set Device ID 473 473 455 +**Example:** 474 474 475 -(% style="color:blue" %)**Example :** 476 - 477 477 AT+DEUI=868411056754138 478 478 479 - 480 - 481 481 === 2.4.2 Version Info === 482 482 483 483 ... ... @@ -572,7 +572,7 @@ 572 572 ))) 573 573 574 574 ((( 575 -(% 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]])**.** 576 576 ))) 577 577 578 578 ... ... @@ -673,14 +673,12 @@ 673 673 ))) 674 674 675 675 654 +== 2.6 Distance alarm function(Since firmware v1.3.2) == 676 676 677 - ==2.6Distance alarm function(Since firmware v1.3.2) ==656 +➢ AT Command: 678 678 658 +AT+ LDDSALARM=min,max 679 679 680 -(% style="color:blue" %)** ➢ AT Command:** 681 - 682 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max** 683 - 684 684 ² When min=0, and max≠0, Alarm higher than max 685 685 686 686 ² When min≠0, and max=0, Alarm lower than min ... ... @@ -687,35 +687,29 @@ 687 687 688 688 ² When min≠0 and max≠0, Alarm higher than max or lower than min 689 689 666 +Example: 690 690 691 - (%style="color:blue"%)** Example:**668 +AT+ LDDSALARM=260,2000 ~/~/ Alarm when distance lower than 260. 692 692 693 -**AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 694 694 671 +== 2.7 Set the number of data to be uploaded and the recording time == 695 695 673 +➢ AT Command: 696 696 697 -= = 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) 698 698 677 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 699 699 700 - (%style="color:blue"%)** ➢ AT Command:**679 +== 2.8 Read or Clear cached data == 701 701 702 -* (% 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) 703 -* (% 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: 704 704 705 -T hislinkexplainstherelationshipbetween TR, NOUDandTDC moreclearly **: **[[https:~~/~~/www.processon.com/view/link/6340e606e401fd390891af87>>url:https://www.processon.com/view/link/6340e606e401fd390891af87]]683 +AT+CDP ~/~/ Read cached data 706 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 715 [[image:image-20220908175333-2.png]] 716 716 687 +AT+CDP=0 ~/~/ Clear cached data 717 717 718 - 719 719 == 2.9 LED Indicator == 720 720 721 721 ... ... @@ -861,90 +861,90 @@ 861 861 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]] 862 862 863 863 864 -AT+<CMD>? : 834 +AT+<CMD>? : Help on <CMD> 865 865 866 -AT+<CMD> : 836 +AT+<CMD> : Run <CMD> 867 867 868 -AT+<CMD>=<value> : 838 +AT+<CMD>=<value> : Set the value 869 869 870 -AT+<CMD>=? : 840 +AT+<CMD>=? : Get the value 871 871 872 872 873 873 (% style="color:#037691" %)**General Commands**(%%) 874 874 875 -AT : 845 +AT : Attention 876 876 877 -AT? : 847 +AT? : Short Help 878 878 879 -ATZ : 849 +ATZ : MCU Reset 880 880 881 -AT+TDC : 851 +AT+TDC : Application Data Transmission Interval 882 882 883 -AT+CFG : 853 +AT+CFG : Print all configurations 884 884 885 -AT+CFGMOD : 855 +AT+CFGMOD : Working mode selection 886 886 887 -AT+INTMOD : 857 +AT+INTMOD : Set the trigger interrupt mode 888 888 889 -AT+5VT : 859 +AT+5VT : Set extend the time of 5V power 890 890 891 -AT+PRO : 861 +AT+PRO : Choose agreement 892 892 893 -AT+WEIGRE : 863 +AT+WEIGRE : Get weight or set weight to 0 894 894 895 -AT+WEIGAP : 865 +AT+WEIGAP : Get or Set the GapValue of weight 896 896 897 -AT+RXDL : 867 +AT+RXDL : Extend the sending and receiving time 898 898 899 -AT+CNTFAC : 869 +AT+CNTFAC : Get or set counting parameters 900 900 901 -AT+SERVADDR : 871 +AT+SERVADDR : Server Address 902 902 903 -AT+TR 873 +AT+TR : Get or Set record time" 904 904 905 -AT+APN : 875 +AT+APN : Get or set the APN 906 906 907 -AT+FBAND : 877 +AT+FBAND : Get or Set whether to automatically modify the frequency band 908 908 909 -AT+DNSCFG : Get or Set DNS Server 879 +AT+DNSCFG : Get or Set DNS Server 910 910 911 -AT+GETSENSORVALUE : 881 +AT+GETSENSORVALUE : Returns the current sensor measurement 912 912 913 -AT+NOUD : 883 +AT+NOUD : Get or Set the number of data to be uploaded 914 914 915 -AT+CDP : 885 +AT+CDP : Read or Clear cached data 916 916 917 -AT+LDDSALARM : 887 +AT+LDDSALARM : Get or Set alarm of distance 918 918 919 919 920 920 (% style="color:#037691" %)**COAP Management** 921 921 922 -AT+URI : 892 +AT+URI : Resource parameters 923 923 924 924 925 925 (% style="color:#037691" %)**UDP Management** 926 926 927 -AT+CFM : 897 +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 902 +AT+CLIENT : Get or Set MQTT client 933 933 934 -AT+UNAME :Get or Set MQTT Username904 +AT+UNAME : Get or Set MQTT Username 935 935 936 -AT+PWD 906 +AT+PWD : Get or Set MQTT password 937 937 938 -AT+PUBTOPIC :Get or Set MQTT publish topic908 +AT+PUBTOPIC : Get or Set MQTT publish topic 939 939 940 -AT+SUBTOPIC :Get or Set MQTT subscription topic910 +AT+SUBTOPIC : Get or Set MQTT subscription topic 941 941 942 942 943 943 (% style="color:#037691" %)**Information** 944 944 945 -AT+FDR : 915 +AT+FDR : Factory Data Reset 946 946 947 -AT+PWORD : 917 +AT+PWORD : Serial Access Password 948 948 949 949 950 950