Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual
Last modified by Bei Jinggeng on 2024/05/31 09:53
<
edited by Bei Jinggeng
on 2024/05/31 09:53
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 Manual1 +NDDS75 NB-IoT Distance Detect Sensor User Manual - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Bei1 +XWiki.Xiaoling - Content
-
... ... @@ -1,7 +3,5 @@ 1 - 2 - 3 3 (% style="text-align:center" %) 4 -[[image:image-20220709085040-1.png|| _mstalt="429481"height="542" width="524"]]2 +[[image:image-20220709085040-1.png||height="542" width="524"]] 5 5 6 6 7 7 ... ... @@ -52,7 +52,7 @@ 52 52 53 53 ))) 54 54 55 -[[image:1657327959271-447.png ||_mstalt="297700"]]53 +[[image:1657327959271-447.png]] 56 56 57 57 58 58 == 1.2 Features == ... ... @@ -71,6 +71,8 @@ 71 71 * Micro SIM card slot for NB-IoT SIM 72 72 * 8500mAh Battery for long term use 73 73 72 + 73 + 74 74 == 1.3 Specification == 75 75 76 76 ... ... @@ -101,6 +101,8 @@ 101 101 * STOP Mode: 10uA @ 3.3v 102 102 * Max transmit power: 350mA@3.3v 103 103 104 + 105 + 104 104 == 1.4 Applications == 105 105 106 106 ... ... @@ -118,7 +118,7 @@ 118 118 == 1.5 Pin Definitions == 119 119 120 120 121 -[[image:1657328609906-564.png ||_mstalt="297440"]]123 +[[image:1657328609906-564.png]] 122 122 123 123 124 124 = 2. Use NDDS75 to communicate with IoT Server = ... ... @@ -139,7 +139,7 @@ 139 139 140 140 ))) 141 141 142 -[[image:1657328659945-416.png ||_mstalt="297999"]]144 +[[image:1657328659945-416.png]] 143 143 144 144 ((( 145 145 ... ... @@ -163,7 +163,7 @@ 163 163 ))) 164 164 165 165 166 -[[image:1657328756309-230.png ||_mstalt="294515"]]168 +[[image:1657328756309-230.png]] 167 167 168 168 169 169 === 2.2.2 Insert SIM card === ... ... @@ -177,9 +177,10 @@ 177 177 User need to take out the NB-IoT module and insert the SIM card like below: 178 178 ))) 179 179 180 -[[image:1657328884227-504.png||_mstalt="295776"]] 181 181 183 +[[image:1657328884227-504.png]] 182 182 185 + 183 183 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 184 184 185 185 ... ... @@ -189,7 +189,7 @@ 189 189 ))) 190 190 ))) 191 191 192 -[[image:image-20220709092052-2.png ||_mstalt="430235"]]195 +[[image:image-20220709092052-2.png]] 193 193 194 194 195 195 (% style="color:blue" %)**Connection:** ... ... @@ -213,7 +213,7 @@ 213 213 Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 214 214 ))) 215 215 216 -[[image:1657329814315-101.png ||_mstalt="292084"]]219 +[[image:1657329814315-101.png]] 217 217 218 218 219 219 ((( ... ... @@ -240,6 +240,7 @@ 240 240 * ((( 241 241 (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 242 242 246 + 243 243 244 244 ))) 245 245 ... ... @@ -249,14 +249,17 @@ 249 249 250 250 ))) 251 251 252 -[[image:1657330452568-615.png ||_mstalt="295555"]]256 +[[image:1657330452568-615.png]] 253 253 254 254 259 + 255 255 ((( 256 256 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 + 257 257 ))) 258 258 259 -[[image:1657330472797-498.png ||_mstalt="299481"]]266 +[[image:1657330472797-498.png]] 260 260 261 261 262 262 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === ... ... @@ -264,11 +264,12 @@ 264 264 265 265 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 266 266 * (% 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 267 267 268 -[[image:1657330501006-241.png ||_mstalt="290121"]]276 +[[image:1657330501006-241.png]] 269 269 270 270 271 -[[image:1657330533775-472.png ||_mstalt="295763"]]279 +[[image:1657330533775-472.png]] 272 272 273 273 274 274 === 2.2.6 Use MQTT protocol to uplink data === ... ... @@ -282,10 +282,10 @@ 282 282 * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ Set the sending topic of MQTT 283 283 * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ Set the subscription topic of MQTT 284 284 285 -[[image:1657249978444-674.png ||_mstalt="299377"]]293 +[[image:1657249978444-674.png]] 286 286 287 287 288 -[[image:1657330723006-866.png ||_mstalt="294996"]]296 +[[image:1657330723006-866.png]] 289 289 290 290 291 291 ((( ... ... @@ -299,10 +299,10 @@ 299 299 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 300 300 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 301 301 302 -[[image:image-20220709093918-1.png ||_mstalt="433706"]]310 +[[image:image-20220709093918-1.png]] 303 303 304 304 305 -[[image:image-20220709093918-2.png ||_mstalt="434070"]]313 +[[image:image-20220709093918-2.png]] 306 306 307 307 308 308 === 2.2.8 Change Update Interval === ... ... @@ -315,6 +315,7 @@ 315 315 ((( 316 316 317 317 326 + 318 318 (% style="color:red" %)**NOTE:** 319 319 320 320 (% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** ... ... @@ -332,11 +332,11 @@ 332 332 333 333 In this mode, uplink payload includes in total 14 bytes 334 334 335 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:440px" %)336 -|=(% style="width: 6 1px;background-color:#4F81BD;color:white" %)(((344 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:440px" %) 345 +|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)((( 337 337 **Size(bytes)** 338 -)))|=(% style="width: 6 1px;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"]] 347 +)))|=(% style="width: 60px;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"]] 340 340 341 341 ((( 342 342 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. ... ... @@ -343,7 +343,7 @@ 343 343 ))) 344 344 345 345 346 -[[image:1657331036973-987.png ||_mstalt="298740"]]355 +[[image:1657331036973-987.png]] 347 347 348 348 349 349 The payload is **ASCII** string, representative same HEX: ... ... @@ -364,6 +364,8 @@ 364 364 365 365 * (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 366 366 376 + 377 + 367 367 === 2.3.2 Since firmware v1.3.2 === 368 368 369 369 ... ... @@ -371,13 +371,13 @@ 371 371 372 372 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. 373 373 374 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:490px" %)375 -|(% style="background-color:# 4f81bd;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....... 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: 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....... 377 377 378 378 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 379 379 380 -[[image:image-20220908175246-1.png ||_mstalt="432328"]]391 +[[image:image-20220908175246-1.png]] 381 381 382 382 383 383 The payload is ASCII string, representative same HEX: ... ... @@ -400,12 +400,14 @@ 400 400 401 401 * (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57 402 402 403 -* (% _mstmutation="1" style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/||_mstmutation="1"]])414 +* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 404 404 405 405 * (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0 406 406 407 407 * (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 408 408 420 + 421 + 409 409 == 2.4 Payload Explanation and Sensor Interface == 410 410 411 411 === 2.4.1 Device ID === ... ... @@ -508,10 +508,16 @@ 508 508 Get the distance. Flat object range 280mm - 7500mm. 509 509 510 510 ((( 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.**524 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 512 512 ))) 513 513 514 514 ((( 528 +((( 529 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 530 +))) 531 +))) 532 + 533 +((( 515 515 516 516 ))) 517 517 ... ... @@ -535,8 +535,9 @@ 535 535 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. 536 536 ))) 537 537 557 + 538 538 ((( 539 - **Example:**559 +Example: 540 540 ))) 541 541 542 542 ((( ... ... @@ -555,12 +555,17 @@ 555 555 NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 556 556 ))) 557 557 578 + 558 558 ((( 559 559 The 5V output time can be controlled by AT Command. 581 + 582 + 560 560 ))) 561 561 562 562 ((( 563 563 (% style="color:blue" %)**AT+5VT=1000** 587 + 588 + 564 564 ))) 565 565 566 566 ((( ... ... @@ -573,12 +573,13 @@ 573 573 574 574 By default, NDDS75 prints the downlink payload to console port. 575 575 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)**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)** 578 578 |(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4 579 579 |(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2 580 580 |(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4 581 581 607 + 582 582 ((( 583 583 (% style="color:blue" %)**Examples:** 584 584 ))) ... ... @@ -652,7 +652,7 @@ 652 652 653 653 The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 654 654 655 -[[image:image-20221009001114-1.png|| _mstalt="425269"height="687" width="955"]]681 +[[image:image-20221009001114-1.png||height="687" width="955"]] 656 656 657 657 658 658 == 2.8 Read or Clear cached data == ... ... @@ -663,7 +663,7 @@ 663 663 * (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 664 664 * (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 665 665 666 -[[image:image-20220908175333-2.png ||_mstalt="431665"]]692 +[[image:image-20220908175333-2.png]] 667 667 668 668 669 669 == 2.9 LED Indicator == ... ... @@ -710,12 +710,12 @@ 710 710 ))) 711 711 712 712 ((( 713 -The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/ ||_mstmutation="1"]]739 +The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 714 714 715 715 716 716 ))) 717 717 718 -[[image:1657333200519-600.png ||_mstalt="291603"]]744 +[[image:1657333200519-600.png]] 719 719 720 720 721 721 = 4. Using the AT Commands = ... ... @@ -787,7 +787,11 @@ 787 787 AT+URI : Resource parameters 788 788 789 789 816 +(% style="color:#037691" %)**UDP Management** 790 790 818 +AT+CFM : Upload confirmation mode (only valid for UDP) 819 + 820 + 791 791 (% style="color:#037691" %)**MQTT Management** 792 792 793 793 AT+CLIENT : Get or Set MQTT client ... ... @@ -854,27 +854,6 @@ 854 854 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]]//**. 855 855 856 856 857 -== 6.4 Why does the DDS75 sensor keep flashing blue? == 858 - 859 -This is caused by the incompatibility between the latest firmware and the hardware. 860 - 861 -Please check your hardware production date 862 - 863 -The first two digits are the week of the year, and the last two digits are the year. 864 - 865 -The number 3322 is the first batch we changed the power IC. 866 - 867 -As shown below: 868 - 869 - [[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||_mstalt="431418" alt="image-20240531090837-1.png"]] 870 - 871 -Have you updated the Lora ST's firmware? Please send downline 26 01 to check the version number. 872 - 873 -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. 874 - 875 -Downlink is FF 01(AT+POWERIC=1);FF 00(AT+POWERIC=0). 876 - 877 - 878 878 = 7. Order Info = 879 879 880 880