Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 109.1
edited by Mengting Qiu
on 2024/04/02 16:59
on 2024/04/02 16:59
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 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. ting1 +XWiki.Xiaoling - Content
-
... ... @@ -1,5 +3,3 @@ 1 - 2 - 3 3 (% style="text-align:center" %) 4 4 [[image:image-20220709085040-1.png||height="542" width="524"]] 5 5 ... ... @@ -18,6 +18,7 @@ 18 18 19 19 = 1. Introduction = 20 20 19 + 21 21 == 1.1 What is NDDS75 Distance Detection Sensor == 22 22 23 23 ((( ... ... @@ -55,6 +55,7 @@ 55 55 [[image:1657327959271-447.png]] 56 56 57 57 57 + 58 58 == 1.2 Features == 59 59 60 60 ... ... @@ -81,12 +81,12 @@ 81 81 82 82 (% style="color:#037691" %)**NB-IoT Spec:** 83 83 84 -* B1 @H-FDD: 2100MHz 85 -* B3 @H-FDD: 1800MHz 86 -* B8 @H-FDD: 900MHz 87 -* B5 @H-FDD: 850MHz 88 -* B20 @H-FDD: 800MHz 89 -* B28 @H-FDD: 700MHz 84 +* - B1 @H-FDD: 2100MHz 85 +* - B3 @H-FDD: 1800MHz 86 +* - B8 @H-FDD: 900MHz 87 +* - B5 @H-FDD: 850MHz 88 +* - B20 @H-FDD: 800MHz 89 +* - B28 @H-FDD: 700MHz 90 90 91 91 (% style="color:#037691" %)**Battery:** 92 92 ... ... @@ -115,6 +115,8 @@ 115 115 116 116 117 117 118 + 119 + 118 118 == 1.5 Pin Definitions == 119 119 120 120 ... ... @@ -121,8 +121,10 @@ 121 121 [[image:1657328609906-564.png]] 122 122 123 123 126 + 124 124 = 2. Use NDDS75 to communicate with IoT Server = 125 125 129 + 126 126 == 2.1 How it works == 127 127 128 128 ... ... @@ -145,8 +145,10 @@ 145 145 146 146 ))) 147 147 152 + 148 148 == 2.2 Configure the NDDS75 == 149 149 155 + 150 150 === 2.2.1 Test Requirement === 151 151 152 152 ... ... @@ -166,6 +166,7 @@ 166 166 [[image:1657328756309-230.png]] 167 167 168 168 175 + 169 169 === 2.2.2 Insert SIM card === 170 170 171 171 ... ... @@ -177,9 +177,11 @@ 177 177 User need to take out the NB-IoT module and insert the SIM card like below: 178 178 ))) 179 179 187 + 180 180 [[image:1657328884227-504.png]] 181 181 182 182 191 + 183 183 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 184 184 185 185 ... ... @@ -192,13 +192,13 @@ 192 192 [[image:image-20220709092052-2.png]] 193 193 194 194 195 - (% style="color:blue" %)**Connection:**204 +**Connection:** 196 196 197 - (% style="background-color:yellow" %) **USB TTL GND <~-~-~-~-> GND**206 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 198 198 199 - **~(% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**208 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 200 200 201 - **~(% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**210 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 202 202 203 203 204 204 In the PC, use below serial tool settings: ... ... @@ -221,6 +221,7 @@ 221 221 ))) 222 222 223 223 233 + 224 224 === 2.2.4 Use CoAP protocol to uplink data === 225 225 226 226 ... ... @@ -235,11 +235,12 @@ 235 235 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 236 236 ))) 237 237 * ((( 238 -(% 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 239 239 ))) 240 240 * ((( 241 -(% 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 242 242 253 + 243 243 244 244 ))) 245 245 ... ... @@ -252,18 +252,23 @@ 252 252 [[image:1657330452568-615.png]] 253 253 254 254 266 + 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. 269 + 270 + 257 257 ))) 258 258 259 259 [[image:1657330472797-498.png]] 260 260 261 261 276 + 262 262 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 263 263 264 264 265 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 266 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 280 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 281 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 282 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 267 267 268 268 [[image:1657330501006-241.png]] 269 269 ... ... @@ -271,16 +271,17 @@ 271 271 [[image:1657330533775-472.png]] 272 272 273 273 290 + 274 274 === 2.2.6 Use MQTT protocol to uplink data === 275 275 276 276 277 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ 278 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ 279 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ 280 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ 281 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ 282 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ 283 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ 294 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 295 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 296 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 297 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 298 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 299 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 300 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 284 284 285 285 [[image:1657249978444-674.png]] 286 286 ... ... @@ -293,11 +293,12 @@ 293 293 ))) 294 294 295 295 313 + 296 296 === 2.2.7 Use TCP protocol to uplink data === 297 297 298 298 299 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ 300 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ 317 +* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 318 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 301 301 302 302 [[image:image-20220709093918-1.png]] 303 303 ... ... @@ -305,41 +305,42 @@ 305 305 [[image:image-20220709093918-2.png]] 306 306 307 307 326 + 308 308 === 2.2.8 Change Update Interval === 309 309 310 310 311 311 User can use below command to change the (% style="color:green" %)**uplink interval**. 312 312 313 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ 332 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 314 314 315 315 ((( 316 - 335 +(% style="color:red" %)**NOTE 1: By default, the device will send an uplink message every 1 hour.** 317 317 318 -(% style="color:red" %)**NOTE:** 319 - 320 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** 321 - 322 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:** 337 + 323 323 ))) 324 324 340 +(% style="color:red" %)**NOTE 2: When the firmware version is v1.3.2 and later firmware:** 341 + 325 325 (% 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).** 326 326 327 327 345 + 328 328 == 2.3 Uplink Payload == 329 329 330 -=== 2.3.1 Before Firmware v1.3.2 === 331 331 349 +=== 2.3.1 Before Firmware 1.3.2 === 332 332 351 + 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" %)(((354 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 355 +|=(% style="width: 60px;" %)((( 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"]] 357 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 358 +|(% 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 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 361 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 343 343 ))) 344 344 345 345 ... ... @@ -346,34 +346,49 @@ 346 346 [[image:1657331036973-987.png]] 347 347 348 348 368 +((( 349 349 The payload is **ASCII** string, representative same HEX: 370 +))) 350 350 351 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** 372 +((( 373 +0x72403155615900640c6c19029200 where: 374 +))) 352 352 353 -**where :** 376 +* ((( 377 +Device ID: 0x724031556159 = 724031556159 378 +))) 379 +* ((( 380 +Version: 0x0064=100=1.0.0 381 +))) 354 354 355 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159 383 +* ((( 384 +BAT: 0x0c6c = 3180 mV = 3.180V 385 +))) 386 +* ((( 387 +Signal: 0x19 = 25 388 +))) 389 +* ((( 390 +Distance: 0x0292= 658 mm 391 +))) 392 +* ((( 393 +Interrupt: 0x00 = 0 356 356 357 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 358 358 359 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V 360 360 361 -* (% style="color:#037691" %)**Signal:**(%%) 0x19 = 25 362 362 363 -* (% style="color:#037691" %)**Distance:** (%%)0x0292= 658 mm 398 + 399 +))) 364 364 365 - * (% style="color:#037691"%)**Interrupt:**(%%)0x00=0401 +=== **2.3.2 Since firmware v1.3.2** === 366 366 367 -=== 2.3.2 Since firmware v1.3.2 === 368 368 369 - 370 370 In this mode, uplink payload includes 69 bytes in total by default. 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; 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....... 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....... 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 ... ... @@ -382,32 +382,26 @@ 382 382 383 383 The payload is ASCII string, representative same HEX: 384 384 385 - **0x#00b0f0" %)1e#7030a0" %)01#d60093" %)00(% style="color:#a14d07" %)(% style="color:#0020b0" %)6315537b(% style="color:#663300" %)00396319baf0**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: 386 386 387 -**where:** 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**//,....... 388 388 389 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317 390 390 391 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2 392 392 393 -* (% style="color:#037691" %)**BAT:**(%%) 0x0cf4 = 3316 mV = 3.316V 394 394 395 -* (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 396 396 397 -* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 398 - 399 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 400 - 401 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57 402 - 403 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 404 - 405 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0 406 - 407 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 408 - 409 409 == 2.4 Payload Explanation and Sensor Interface == 410 410 438 + 411 411 === 2.4.1 Device ID === 412 412 413 413 ... ... @@ -446,6 +446,7 @@ 446 446 AT+DEUI=868411056754138 447 447 448 448 477 + 449 449 === 2.4.2 Version Info === 450 450 451 451 ... ... @@ -458,6 +458,7 @@ 458 458 ))) 459 459 460 460 490 + 461 461 === 2.4.3 Battery Info === 462 462 463 463 ... ... @@ -470,6 +470,7 @@ 470 470 ))) 471 471 472 472 503 + 473 473 === 2.4.4 Signal Strength === 474 474 475 475 ... ... @@ -502,6 +502,7 @@ 502 502 ))) 503 503 504 504 536 + 505 505 === 2.4.5 Distance === 506 506 507 507 ... ... @@ -508,13 +508,23 @@ 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.**543 +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 ((( 547 +((( 548 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 549 +))) 550 +))) 551 + 552 +((( 515 515 516 516 ))) 517 517 556 +((( 557 + 558 +))) 559 + 518 518 === 2.4.6 Digital Interrupt === 519 519 520 520 ... ... @@ -527,7 +527,7 @@ 527 527 ))) 528 528 529 529 ((( 530 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/ 572 +(% 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]])**.** 531 531 ))) 532 532 533 533 ... ... @@ -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 580 + 538 538 ((( 539 - **Example:**582 +Example: 540 540 ))) 541 541 542 542 ((( ... ... @@ -548,6 +548,7 @@ 548 548 ))) 549 549 550 550 594 + 551 551 === 2.4.7 +5V Output === 552 552 553 553 ... ... @@ -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 602 + 558 558 ((( 559 559 The 5V output time can be controlled by AT Command. 605 + 606 + 560 560 ))) 561 561 562 562 ((( 563 563 (% style="color:blue" %)**AT+5VT=1000** 611 + 612 + 564 564 ))) 565 565 566 566 ((( ... ... @@ -568,17 +568,15 @@ 568 568 ))) 569 569 570 570 620 + 571 571 == 2.5 Downlink Payload == 572 572 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)** 578 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4 579 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2 580 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4 626 +[[image:image-20220709100028-1.png]] 581 581 628 + 582 582 ((( 583 583 (% style="color:blue" %)**Examples:** 584 584 ))) ... ... @@ -623,6 +623,7 @@ 623 623 ))) 624 624 625 625 673 + 626 626 == 2.6 Distance alarm function(Since firmware v1.3.2) == 627 627 628 628 ... ... @@ -642,17 +642,16 @@ 642 642 **AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 643 643 644 644 693 + 645 645 == 2.7 Set the number of data to be uploaded and the recording time == 646 646 647 647 648 648 (% style="color:blue" %)** ➢ AT Command:** 649 649 650 -* (% 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) 651 -* (% 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. 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) 652 652 653 - The di agram belowexplainsthe relationshipbetweenTR, NOUD,andTDCmore clearly**:**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. 654 654 655 -[[image:image-20221009001114-1.png||height="687" width="955"]] 656 656 657 657 658 658 == 2.8 Read or Clear cached data == ... ... @@ -660,12 +660,16 @@ 660 660 661 661 (% style="color:blue" %)** ➢ AT Command:** 662 662 663 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 664 -* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 710 +(% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 665 665 712 + 666 666 [[image:image-20220908175333-2.png]] 667 667 668 668 716 +(% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 717 + 718 + 719 + 669 669 == 2.9 LED Indicator == 670 670 671 671 ... ... @@ -682,6 +682,7 @@ 682 682 ))) 683 683 684 684 736 + 685 685 == 2.10 Firmware Change Log == 686 686 687 687 ... ... @@ -690,18 +690,100 @@ 690 690 ))) 691 691 692 692 ((( 745 + 746 +))) 747 + 748 +((( 693 693 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 694 694 ))) 695 695 696 696 697 -== 2.11 Battery & Power Consumption == 698 698 754 +== 2.11 Battery Analysis == 699 699 700 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 701 701 702 - [[**BatteryInfo & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]].757 +=== 2.11.1 Battery Type === 703 703 704 704 760 +((( 761 +The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 762 +))) 763 + 764 +((( 765 +The battery is designed to last for several years depends on the actually use environment and update interval. 766 +))) 767 + 768 +((( 769 +The battery related documents as below: 770 +))) 771 + 772 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 773 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 774 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 775 + 776 +((( 777 +[[image:image-20220709101450-2.png]] 778 +))) 779 + 780 + 781 + 782 +=== 2.11.2 Power consumption Analyze === 783 + 784 + 785 +((( 786 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval. 787 +))) 788 + 789 + 790 +((( 791 +Instruction to use as below: 792 +))) 793 + 794 +((( 795 +(% style="color:blue" %)**Step 1: **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]] 796 +))) 797 + 798 + 799 +((( 800 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 801 +))) 802 + 803 +* ((( 804 +Product Model 805 +))) 806 +* ((( 807 +Uplink Interval 808 +))) 809 +* ((( 810 +Working Mode 811 +))) 812 + 813 +((( 814 +And the Life expectation in difference case will be shown on the right. 815 +))) 816 + 817 +[[image:image-20220709110451-3.png]] 818 + 819 + 820 + 821 +=== 2.11.3 Battery Note === 822 + 823 + 824 +((( 825 +The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased. 826 +))) 827 + 828 + 829 + 830 +=== 2.11.4 Replace the battery === 831 + 832 + 833 +((( 834 +The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes). 835 +))) 836 + 837 + 838 + 705 705 = 3. Access NB-IoT Module = 706 706 707 707 ... ... @@ -718,8 +718,10 @@ 718 718 [[image:1657333200519-600.png]] 719 719 720 720 855 + 721 721 = 4. Using the AT Commands = 722 722 858 + 723 723 == 4.1 Access AT Commands == 724 724 725 725 ... ... @@ -726,90 +726,96 @@ 726 726 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]] 727 727 728 728 729 -AT+<CMD>? : 865 +AT+<CMD>? : Help on <CMD> 730 730 731 -AT+<CMD> : 867 +AT+<CMD> : Run <CMD> 732 732 733 -AT+<CMD>=<value> : 869 +AT+<CMD>=<value> : Set the value 734 734 735 -AT+<CMD>=? : 871 +AT+<CMD>=? : Get the value 736 736 737 737 738 738 (% style="color:#037691" %)**General Commands**(%%) 739 739 740 -AT : 876 +AT : Attention 741 741 742 -AT? : 878 +AT? : Short Help 743 743 744 -ATZ : 880 +ATZ : MCU Reset 745 745 746 -AT+TDC : 882 +AT+TDC : Application Data Transmission Interval 747 747 748 -AT+CFG : 884 +AT+CFG : Print all configurations 749 749 750 -AT+CFGMOD : 886 +AT+CFGMOD : Working mode selection 751 751 752 -AT+INTMOD : 888 +AT+INTMOD : Set the trigger interrupt mode 753 753 754 -AT+5VT : 890 +AT+5VT : Set extend the time of 5V power 755 755 756 -AT+PRO : 892 +AT+PRO : Choose agreement 757 757 758 -AT+WEIGRE : 894 +AT+WEIGRE : Get weight or set weight to 0 759 759 760 -AT+WEIGAP : 896 +AT+WEIGAP : Get or Set the GapValue of weight 761 761 762 -AT+RXDL : 898 +AT+RXDL : Extend the sending and receiving time 763 763 764 -AT+CNTFAC : 900 +AT+CNTFAC : Get or set counting parameters 765 765 766 -AT+SERVADDR : 902 +AT+SERVADDR : Server Address 767 767 768 -AT+TR 904 +AT+TR : Get or Set record time" 769 769 770 -AT+APN : 906 +AT+APN : Get or set the APN 771 771 772 -AT+FBAND : 908 +AT+FBAND : Get or Set whether to automatically modify the frequency band 773 773 774 -AT+DNSCFG : Get or Set DNS Server 910 +AT+DNSCFG : Get or Set DNS Server 775 775 776 -AT+GETSENSORVALUE : 912 +AT+GETSENSORVALUE : Returns the current sensor measurement 777 777 778 -AT+NOUD : 914 +AT+NOUD : Get or Set the number of data to be uploaded 779 779 780 -AT+CDP : 916 +AT+CDP : Read or Clear cached data 781 781 782 -AT+LDDSALARM : 918 +AT+LDDSALARM : Get or Set alarm of distance 783 783 784 784 785 785 (% style="color:#037691" %)**COAP Management** 786 786 787 -AT+URI : 923 +AT+URI : Resource parameters 788 788 789 789 926 +(% style="color:#037691" %)**UDP Management** 790 790 928 +AT+CFM : Upload confirmation mode (only valid for UDP) 929 + 930 + 791 791 (% style="color:#037691" %)**MQTT Management** 792 792 793 -AT+CLIENT 933 +AT+CLIENT : Get or Set MQTT client 794 794 795 -AT+UNAME :Get or Set MQTT Username935 +AT+UNAME : Get or Set MQTT Username 796 796 797 -AT+PWD 937 +AT+PWD : Get or Set MQTT password 798 798 799 -AT+PUBTOPIC :Get or Set MQTT publish topic939 +AT+PUBTOPIC : Get or Set MQTT publish topic 800 800 801 -AT+SUBTOPIC :Get or Set MQTT subscription topic941 +AT+SUBTOPIC : Get or Set MQTT subscription topic 802 802 803 803 804 804 (% style="color:#037691" %)**Information** 805 805 806 -AT+FDR : 946 +AT+FDR : Factory Data Reset 807 807 808 -AT+PWORD : 948 +AT+PWORD : Serial Access Password 809 809 810 810 951 + 811 811 = 5. FAQ = 812 812 954 + 813 813 == 5.1 How to Upgrade Firmware == 814 814 815 815 ... ... @@ -826,8 +826,10 @@ 826 826 ))) 827 827 828 828 971 + 829 829 = 6. Trouble Shooting = 830 830 974 + 831 831 == 6.1 Connection problem when uploading firmware == 832 832 833 833 ... ... @@ -840,20 +840,17 @@ 840 840 841 841 ))) 842 842 987 + 843 843 == 6.2 AT Command input doesn't work == 844 844 845 845 846 846 ((( 847 847 In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string. 993 + 994 + 848 848 ))) 849 849 850 850 851 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 852 - 853 - 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 - 856 - 857 857 = 7. Order Info = 858 858 859 859 ... ... @@ -860,6 +860,11 @@ 860 860 Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 861 861 862 862 1004 +(% class="wikigeneratedid" %) 1005 +((( 1006 + 1007 +))) 1008 + 863 863 = 8. Packing Info = 864 864 865 865 ((( ... ... @@ -874,6 +874,7 @@ 874 874 ((( 875 875 876 876 1023 + 877 877 (% style="color:#037691" %)**Dimension and weight**: 878 878 879 879 * Device Size: 13.0 x 5 x 4.5 cm ... ... @@ -885,6 +885,7 @@ 885 885 ((( 886 886 887 887 1035 + 888 888 889 889 ))) 890 890 ... ... @@ -892,5 +892,4 @@ 892 892 893 893 894 894 * 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. 895 - 896 896 * 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]]
- image-20221009001114-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content