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, 2 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -71,9 +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 - 77 77 == 1.3 Specification == 78 78 79 79 ... ... @@ -82,8 +82,6 @@ 82 82 * Supply Voltage: 2.1v ~~ 3.6v 83 83 * Operating Temperature: -40 ~~ 85°C 84 84 85 - 86 - 87 87 (% style="color:#037691" %)**NB-IoT Spec:** 88 88 89 89 * - B1 @H-FDD: 2100MHz ... ... @@ -93,8 +93,6 @@ 93 93 * - B20 @H-FDD: 800MHz 94 94 * - B28 @H-FDD: 700MHz 95 95 96 - 97 - 98 98 (% style="color:#037691" %)**Battery:** 99 99 100 100 * Li/SOCI2 un-chargeable battery ... ... @@ -103,16 +103,11 @@ 103 103 * Max continuously current: 130mA 104 104 * Max boost current: 2A, 1 second 105 105 106 - 107 - 108 108 (% style="color:#037691" %)**Power Consumption** 109 109 110 110 * STOP Mode: 10uA @ 3.3v 111 111 * Max transmit power: 350mA@3.3v 112 112 113 - 114 - 115 - 116 116 == 1.4 Applications == 117 117 118 118 ... ... @@ -176,8 +176,6 @@ 176 176 * The local NB-IoT network used the band that NDDS75 supports. 177 177 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 178 178 179 - 180 - 181 181 ((( 182 182 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server. 183 183 ))) ... ... @@ -270,6 +270,8 @@ 270 270 271 271 ((( 272 272 For parameter description, please refer to AT command set 259 + 260 + 273 273 ))) 274 274 275 275 [[image:1657330452568-615.png]] ... ... @@ -278,6 +278,8 @@ 278 278 279 279 ((( 280 280 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. 269 + 270 + 281 281 ))) 282 282 283 283 [[image:1657330472797-498.png]] ... ... @@ -291,8 +291,6 @@ 291 291 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 292 292 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 293 293 294 - 295 - 296 296 [[image:1657330501006-241.png]] 297 297 298 298 ... ... @@ -311,8 +311,6 @@ 311 311 * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 312 312 * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 313 313 314 - 315 - 316 316 [[image:1657249978444-674.png]] 317 317 318 318 ... ... @@ -331,8 +331,6 @@ 331 331 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 332 332 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 333 333 334 - 335 - 336 336 [[image:image-20220709093918-1.png]] 337 337 338 338 ... ... @@ -347,20 +347,26 @@ 347 347 348 348 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 349 349 350 - 351 - 352 352 ((( 353 -(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.** 335 +(% style="color:red" %)**NOTE 1: By default, the device will send an uplink message every 1 hour.** 336 + 337 + 354 354 ))) 355 355 340 +(% style="color:red" %)**NOTE 2: When the firmware version is v1.3.2 and later firmware:** 356 356 342 +(% 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).** 357 357 344 + 345 + 358 358 == 2.3 Uplink Payload == 359 359 360 360 361 - Inthismode,uplink payload includesin total14bytes349 +=== 2.3.1 Before Firmware 1.3.2 === 362 362 363 363 352 +In this mode, uplink payload includes in total 14 bytes 353 + 364 364 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 365 365 |=(% style="width: 60px;" %)((( 366 366 **Size(bytes)** ... ... @@ -376,7 +376,7 @@ 376 376 377 377 378 378 ((( 379 -The payload is ASCII string, representative same HEX: 369 +The payload is **ASCII** string, representative same HEX: 380 380 ))) 381 381 382 382 ((( ... ... @@ -387,11 +387,11 @@ 387 387 Device ID: 0x724031556159 = 724031556159 388 388 ))) 389 389 * ((( 390 -Version: 0x0064=100=1.0.0 380 +Version: 0x0064=100=1.0.0 391 391 ))) 392 392 393 393 * ((( 394 -BAT: 0x0c6c = 3180 mV = 3.180V 384 +BAT: 0x0c6c = 3180 mV = 3.180V 395 395 ))) 396 396 * ((( 397 397 Signal: 0x19 = 25 ... ... @@ -404,9 +404,45 @@ 404 404 405 405 406 406 397 + 407 407 408 408 ))) 409 409 401 +=== **2.3.2 Since firmware v1.3.2** === 402 + 403 + 404 +In this mode, uplink payload includes 69 bytes in total by default. 405 + 406 +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. 407 + 408 +(% border="2" style="background-color:#ffffcc; color:green; width:896px" %) 409 +|(% 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 410 +|(% 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....... 411 + 412 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 413 + 414 +[[image:image-20220908175246-1.png]] 415 + 416 + 417 +The payload is ASCII string, representative same HEX: 418 + 419 +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: 420 + 421 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317 422 +* (% style="color:red" %)Version: 0x0084=132=1.3.2 423 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V 424 +* (% style="color:blue" %)Singal: 0x1e = 30 425 +* (% style="color:red" %)Mod: 0x01 = 1 426 +* Interrupt: 0x00= 0 427 +* Distance: 0x0039= 57 = 57 428 +* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 429 +* Distance,Time stamp : 00396319baf0 430 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,....... 431 + 432 + 433 + 434 + 435 + 410 410 == 2.4 Payload Explanation and Sensor Interface == 411 411 412 412 ... ... @@ -424,7 +424,7 @@ 424 424 ))) 425 425 426 426 ((( 427 -**Example:** 453 +(% style="color:blue" %)**Example :** 428 428 ))) 429 429 430 430 ((( ... ... @@ -432,11 +432,23 @@ 432 432 ))) 433 433 434 434 ((( 435 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 461 +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. 436 436 ))) 437 437 438 438 465 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:** 439 439 467 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.** 468 + 469 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 470 + 471 + 472 +(% style="color:blue" %)**Example :** 473 + 474 +AT+DEUI=868411056754138 475 + 476 + 477 + 440 440 === 2.4.2 Version Info === 441 441 442 442 ... ... @@ -633,9 +633,55 @@ 633 633 634 634 635 635 636 -== 2.6 LEDIndicator ==674 +== 2.6 Distance alarm function(Since firmware v1.3.2) == 637 637 638 638 677 +(% style="color:blue" %)** ➢ AT Command:** 678 + 679 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max** 680 + 681 +² When min=0, and max≠0, Alarm higher than max 682 + 683 +² When min≠0, and max=0, Alarm lower than min 684 + 685 +² When min≠0 and max≠0, Alarm higher than max or lower than min 686 + 687 + 688 +(% style="color:blue" %)** Example:** 689 + 690 +**AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 691 + 692 + 693 + 694 +== 2.7 Set the number of data to be uploaded and the recording time == 695 + 696 + 697 +(% style="color:blue" %)** ➢ AT Command:** 698 + 699 +(% 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) 700 + 701 +(% 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. 702 + 703 + 704 + 705 +== 2.8 Read or Clear cached data == 706 + 707 + 708 +(% style="color:blue" %)** ➢ AT Command:** 709 + 710 +(% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 711 + 712 + 713 +[[image:image-20220908175333-2.png]] 714 + 715 + 716 +(% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 717 + 718 + 719 + 720 +== 2.9 LED Indicator == 721 + 722 + 639 639 The NDDS75 has an internal LED which is to show the status of different state. 640 640 641 641 ... ... @@ -650,7 +650,7 @@ 650 650 651 651 652 652 653 -== 2. 7Firmware Change Log ==737 +== 2.10 Firmware Change Log == 654 654 655 655 656 656 ((( ... ... @@ -667,10 +667,10 @@ 667 667 668 668 669 669 670 -== 2. 8Battery Analysis ==754 +== 2.11 Battery Analysis == 671 671 672 672 673 -=== 2. 8.1 Battery Type ===757 +=== 2.11.1 Battery Type === 674 674 675 675 676 676 ((( ... ... @@ -695,7 +695,7 @@ 695 695 696 696 697 697 698 -=== 2. 8.2 Power consumption Analyze ===782 +=== 2.11.2 Power consumption Analyze === 699 699 700 700 701 701 ((( ... ... @@ -734,7 +734,7 @@ 734 734 735 735 736 736 737 -=== 2. 8.3 Battery Note ===821 +=== 2.11.3 Battery Note === 738 738 739 739 740 740 ((( ... ... @@ -743,7 +743,7 @@ 743 743 744 744 745 745 746 -=== 2. 8.4 Replace the battery ===830 +=== 2.11.4 Replace the battery === 747 747 748 748 749 749 ((( ... ... @@ -817,7 +817,23 @@ 817 817 818 818 AT+SERVADDR : Server Address 819 819 904 +AT+TR : Get or Set record time" 820 820 906 +AT+APN : Get or set the APN 907 + 908 +AT+FBAND : Get or Set whether to automatically modify the frequency band 909 + 910 +AT+DNSCFG : Get or Set DNS Server 911 + 912 +AT+GETSENSORVALUE : Returns the current sensor measurement 913 + 914 +AT+NOUD : Get or Set the number of data to be uploaded 915 + 916 +AT+CDP : Read or Clear cached data 917 + 918 +AT+LDDSALARM : Get or Set alarm of distance 919 + 920 + 821 821 (% style="color:#037691" %)**COAP Management** 822 822 823 823 AT+URI : Resource parameters ... ... @@ -941,5 +941,3 @@ 941 941 942 942 * 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. 943 943 * 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]] 944 - 945 -
- image-20220908175246-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +55.7 KB - Content
- image-20220908175333-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +31.1 KB - Content