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. Xiaoling1 +XWiki.Edwin - Content
-
... ... @@ -256,8 +256,6 @@ 256 256 257 257 ((( 258 258 For parameter description, please refer to AT command set 259 - 260 - 261 261 ))) 262 262 263 263 [[image:1657330452568-615.png]] ... ... @@ -266,8 +266,6 @@ 266 266 267 267 ((( 268 268 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 - 271 271 ))) 272 272 273 273 [[image:1657330472797-498.png]] ... ... @@ -332,26 +332,21 @@ 332 332 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 333 333 334 334 ((( 335 - 331 +(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.** 336 336 337 - 338 -(% style="color:red" %)**NOTE:** 339 - 340 -(% style="color:red" %)**1: By default, the device will send an uplink message every 1 hour.** 341 - 342 -(% style="color:red" %)**2: When the firmware version is v1.3.2 and later firmware:** 333 + 343 343 ))) 344 344 345 - (% 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:** 346 346 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).** 347 347 348 348 349 349 == 2.3 Uplink Payload == 350 350 351 351 352 -=== 2.3.1 344 +=== 2.3.1 Before Firmware 1.3.2 === 353 353 354 - 355 355 In this mode, uplink payload includes in total 14 bytes 356 356 357 357 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) ... ... @@ -369,7 +369,7 @@ 369 369 370 370 371 371 ((( 372 -The payload is **ASCII**string, representative same HEX:363 +The payload is ASCII string, representative same HEX: 373 373 ))) 374 374 375 375 ((( ... ... @@ -380,11 +380,11 @@ 380 380 Device ID: 0x724031556159 = 724031556159 381 381 ))) 382 382 * ((( 383 -Version: 374 +Version: 0x0064=100=1.0.0 384 384 ))) 385 385 386 386 * ((( 387 -BAT: 378 +BAT: 0x0c6c = 3180 mV = 3.180V 388 388 ))) 389 389 * ((( 390 390 Signal: 0x19 = 25 ... ... @@ -395,28 +395,22 @@ 395 395 * ((( 396 396 Interrupt: 0x00 = 0 397 397 398 - 399 - 400 - 401 401 402 402 ))) 403 403 404 -=== **2.3.2 392 +=== **2.3.2 Since firmware v1.3.2** === 405 405 406 - 407 407 In this mode, uplink payload includes 69 bytes in total by default. 408 408 409 409 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. 410 410 411 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %) 412 -|(% 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 413 -|(% 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....... 414 414 415 415 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 416 416 417 417 [[image:image-20220908175246-1.png]] 418 418 419 - 420 420 The payload is ASCII string, representative same HEX: 421 421 422 422 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: ... ... @@ -432,10 +432,6 @@ 432 432 * Distance,Time stamp : 00396319baf0 433 433 * (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,....... 434 434 435 - 436 - 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 ... ... @@ -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,39 +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.( Theminimum canbe set to 180 seconds)681 +➢ AT Command: 703 703 704 - (% style="color:#037691" %)**AT+NOUD=8**(%%)~/~/Thedevice uploads8 sets of recorded data by default. Up to 32 sets of record datacan be uploaded.683 +AT+CDP ~/~/ Read cached data 705 705 706 - 707 - 708 -== 2.8 Read or Clear cached data == 709 - 710 - 711 -(% style="color:blue" %)** ➢ AT Command:** 712 - 713 -(% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 714 - 715 - 716 716 [[image:image-20220908175333-2.png]] 717 717 687 +AT+CDP=0 ~/~/ Clear cached data 718 718 719 -(% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 720 - 721 - 722 - 723 723 == 2.9 LED Indicator == 724 724 725 725