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 (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -NDDS75 NB-IoT Distance Detect Sensor User Manual 1 +NDDS75 -- NB-IoT Distance Detect Sensor User Manual - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Bei - Content
-
... ... @@ -1,3 +1,5 @@ 1 + 2 + 1 1 (% style="text-align:center" %) 2 2 [[image:image-20220709085040-1.png||height="542" width="524"]] 3 3 ... ... @@ -69,8 +69,6 @@ 69 69 * Micro SIM card slot for NB-IoT SIM 70 70 * 8500mAh Battery for long term use 71 71 72 - 73 - 74 74 == 1.3 Specification == 75 75 76 76 ... ... @@ -101,8 +101,6 @@ 101 101 * STOP Mode: 10uA @ 3.3v 102 102 * Max transmit power: 350mA@3.3v 103 103 104 - 105 - 106 106 == 1.4 Applications == 107 107 108 108 ... ... @@ -179,7 +179,6 @@ 179 179 User need to take out the NB-IoT module and insert the SIM card like below: 180 180 ))) 181 181 182 - 183 183 [[image:1657328884227-504.png]] 184 184 185 185 ... ... @@ -243,7 +243,6 @@ 243 243 * ((( 244 244 (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 245 245 246 - 247 247 248 248 ))) 249 249 ... ... @@ -256,11 +256,8 @@ 256 256 [[image:1657330452568-615.png]] 257 257 258 258 259 - 260 260 ((( 261 261 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. 262 - 263 - 264 264 ))) 265 265 266 266 [[image:1657330472797-498.png]] ... ... @@ -271,7 +271,6 @@ 271 271 272 272 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 273 273 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 274 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 275 275 276 276 [[image:1657330501006-241.png]] 277 277 ... ... @@ -323,7 +323,6 @@ 323 323 ((( 324 324 325 325 326 - 327 327 (% style="color:red" %)**NOTE:** 328 328 329 329 (% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** ... ... @@ -341,11 +341,11 @@ 341 341 342 342 In this mode, uplink payload includes in total 14 bytes 343 343 344 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:440px" %)345 -|=(% style="width: 6 0px;background-color:#D9E2F3;color:#0070C0" %)(((335 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:440px" %) 336 +|=(% style="width: 61px;background-color:#4F81BD;color:white" %)((( 346 346 **Size(bytes)** 347 -)))|=(% style="width: 6 0px;background-color:#D9E2F3;color:#0070C0" %)**6**|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 80px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**1**348 -|(% 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"]]338 +)))|=(% style="width: 61px;background-color:#4F81BD;color:white" %)**6**|=(% style="width: 37px;background-color:#4F81BD;color:white" %)2|=(% style="width: 37px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 82px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 102px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**1** 339 +|(% 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"]] 349 349 350 350 ((( 351 351 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. ... ... @@ -373,8 +373,6 @@ 373 373 374 374 * (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 375 375 376 - 377 - 378 378 === 2.3.2 Since firmware v1.3.2 === 379 379 380 380 ... ... @@ -382,9 +382,9 @@ 382 382 383 383 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. 384 384 385 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:490px" %)386 -| =(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:70px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**4**387 -| =(% style="width:;" %)**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.......374 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:490px" %) 375 +|(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:40px" %)**8**|(% style="background-color:#4f81bd; color:white; width:25px" %)**2**|(% style="background-color:#4f81bd; color:white; width:25px" %)**2**|(% style="background-color:#4f81bd; color:white; width:60px" %)**1**|(% style="background-color:#4f81bd; color:white; width:25px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:70px" %)**4**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:65px" %)**4** 376 +|(% 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....... 388 388 389 389 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 390 390 ... ... @@ -417,8 +417,6 @@ 417 417 418 418 * (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 419 419 420 - 421 - 422 422 == 2.4 Payload Explanation and Sensor Interface == 423 423 424 424 === 2.4.1 Device ID === ... ... @@ -521,16 +521,10 @@ 521 521 Get the distance. Flat object range 280mm - 7500mm. 522 522 523 523 ((( 524 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 511 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 525 525 ))) 526 526 527 527 ((( 528 -((( 529 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 530 -))) 531 -))) 532 - 533 -((( 534 534 535 535 ))) 536 536 ... ... @@ -554,9 +554,8 @@ 554 554 The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up. 555 555 ))) 556 556 557 - 558 558 ((( 559 -Example: 539 +**Example:** 560 560 ))) 561 561 562 562 ((( ... ... @@ -575,17 +575,12 @@ 575 575 NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 576 576 ))) 577 577 578 - 579 579 ((( 580 580 The 5V output time can be controlled by AT Command. 581 - 582 - 583 583 ))) 584 584 585 585 ((( 586 586 (% style="color:blue" %)**AT+5VT=1000** 587 - 588 - 589 589 ))) 590 590 591 591 ((( ... ... @@ -598,13 +598,12 @@ 598 598 599 599 By default, NDDS75 prints the downlink payload to console port. 600 600 601 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:520px" %)602 -|(% style="background-color:# d9e2f3; color:#0070c0; width:208px" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0; width:56px" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:154px" %)**Downlink payload size(bytes)**576 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 577 +|(% style="background-color:#4f81bd; color:white; width:208px" %)**Downlink Control Type**|(% style="background-color:#4f81bd; color:white; width:56px" %)**FPort**|(% style="background-color:#4f81bd; color:white; width:100px" %)**Type Code**|(% style="background-color:#4f81bd; color:white; width:151px" %)**Downlink payload size(bytes)** 603 603 |(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4 604 604 |(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2 605 605 |(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4 606 606 607 - 608 608 ((( 609 609 (% style="color:blue" %)**Examples:** 610 610 ))) ... ... @@ -813,11 +813,7 @@ 813 813 AT+URI : Resource parameters 814 814 815 815 816 -(% style="color:#037691" %)**UDP Management** 817 817 818 -AT+CFM : Upload confirmation mode (only valid for UDP) 819 - 820 - 821 821 (% style="color:#037691" %)**MQTT Management** 822 822 823 823 AT+CLIENT : Get or Set MQTT client ... ... @@ -884,6 +884,23 @@ 884 884 This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**. 885 885 886 886 857 +== 6.4 Why does the DDS75 sensor keep flashing blue? == 858 + 859 +The first two digits are the week of the year, and the last two digits are the year. 860 + 861 +The number 3322 is the first batch we changed the power IC. 862 + 863 +As shown below: 864 + 865 + [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDDS75%20-%20LoRaWAN%20Distance%20Detection%20Sensor%20User%20Manual/WebHome/image-20240531090837-1.png?rev=1.1||alt="image-20240531090837-1.png"]] 866 + 867 +Have you updated the Lora ST's firmware? Please send downline 26 01 to check the version number. 868 + 869 +If it is v1.4.1 version, please modify a value according to the above four digits, the AT command is AT+POWERIC. The date after 3322 is AT+POWERIC=1, and the date before it is AT+POWERIC=0. 870 + 871 +Downlink is FF 01(AT+POWERIC=1);FF 00(AT+POWERIC=0). 872 + 873 + 887 887 = 7. Order Info = 888 888 889 889