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)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. David1 +XWiki.Xiaoling - Content
-
... ... @@ -16,7 +16,6 @@ 16 16 17 17 = 1. Introduction = 18 18 19 - 20 20 == 1.1 What is NDDS75 Distance Detection Sensor == 21 21 22 22 ((( ... ... @@ -54,7 +54,6 @@ 54 54 [[image:1657327959271-447.png]] 55 55 56 56 57 - 58 58 == 1.2 Features == 59 59 60 60 ... ... @@ -72,6 +72,7 @@ 72 72 * 8500mAh Battery for long term use 73 73 74 74 73 + 75 75 == 1.3 Specification == 76 76 77 77 ... ... @@ -82,12 +82,12 @@ 82 82 83 83 (% style="color:#037691" %)**NB-IoT Spec:** 84 84 85 -* -B1 @H-FDD: 2100MHz86 -* -B3 @H-FDD: 1800MHz87 -* -B8 @H-FDD: 900MHz88 -* -B5 @H-FDD: 850MHz89 -* -B20 @H-FDD: 800MHz90 -* -B28 @H-FDD: 700MHz84 +* 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 91 91 92 92 (% style="color:#037691" %)**Battery:** 93 93 ... ... @@ -100,9 +100,10 @@ 100 100 (% style="color:#037691" %)**Power Consumption** 101 101 102 102 * STOP Mode: 10uA @ 3.3v 103 -* Max transmit power: 350mA@3.3v 102 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 104 104 105 105 105 + 106 106 == 1.4 Applications == 107 107 108 108 ... ... @@ -117,8 +117,6 @@ 117 117 118 118 119 119 120 - 121 - 122 122 == 1.5 Pin Definitions == 123 123 124 124 ... ... @@ -125,10 +125,8 @@ 125 125 [[image:1657328609906-564.png]] 126 126 127 127 128 - 129 129 = 2. Use NDDS75 to communicate with IoT Server = 130 130 131 - 132 132 == 2.1 How it works == 133 133 134 134 ... ... @@ -151,10 +151,8 @@ 151 151 152 152 ))) 153 153 154 - 155 155 == 2.2 Configure the NDDS75 == 156 156 157 - 158 158 === 2.2.1 Test Requirement === 159 159 160 160 ... ... @@ -174,7 +174,6 @@ 174 174 [[image:1657328756309-230.png]] 175 175 176 176 177 - 178 178 === 2.2.2 Insert SIM card === 179 179 180 180 ... ... @@ -190,7 +190,6 @@ 190 190 [[image:1657328884227-504.png]] 191 191 192 192 193 - 194 194 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 195 195 196 196 ... ... @@ -203,13 +203,13 @@ 203 203 [[image:image-20220709092052-2.png]] 204 204 205 205 206 -**Connection:** 198 +(% style="color:blue" %)**Connection:** 207 207 208 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 200 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 209 209 210 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 202 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 211 211 212 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 204 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 213 213 214 214 215 215 In the PC, use below serial tool settings: ... ... @@ -232,7 +232,6 @@ 232 232 ))) 233 233 234 234 235 - 236 236 === 2.2.4 Use CoAP protocol to uplink data === 237 237 238 238 ... ... @@ -247,10 +247,10 @@ 247 247 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 248 248 ))) 249 249 * ((( 250 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 241 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 251 251 ))) 252 252 * ((( 253 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 244 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 254 254 255 255 256 256 ... ... @@ -258,6 +258,8 @@ 258 258 259 259 ((( 260 260 For parameter description, please refer to AT command set 252 + 253 + 261 261 ))) 262 262 263 263 [[image:1657330452568-615.png]] ... ... @@ -266,18 +266,19 @@ 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. 262 + 263 + 269 269 ))) 270 270 271 271 [[image:1657330472797-498.png]] 272 272 273 273 274 - 275 275 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 276 276 277 277 278 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 279 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 280 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 272 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 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 281 281 282 282 [[image:1657330501006-241.png]] 283 283 ... ... @@ -285,17 +285,16 @@ 285 285 [[image:1657330533775-472.png]] 286 286 287 287 288 - 289 289 === 2.2.6 Use MQTT protocol to uplink data === 290 290 291 291 292 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 293 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 294 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 295 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 296 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 297 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 298 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 285 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 286 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 287 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 288 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 289 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 290 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ Set the sending topic of MQTT 291 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ Set the subscription topic of MQTT 299 299 300 300 [[image:1657249978444-674.png]] 301 301 ... ... @@ -308,12 +308,11 @@ 308 308 ))) 309 309 310 310 311 - 312 312 === 2.2.7 Use TCP protocol to uplink data === 313 313 314 314 315 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 316 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 307 +* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 308 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 317 317 318 318 [[image:image-20220709093918-1.png]] 319 319 ... ... @@ -321,31 +321,34 @@ 321 321 [[image:image-20220709093918-2.png]] 322 322 323 323 324 - 325 325 === 2.2.8 Change Update Interval === 326 326 327 327 328 328 User can use below command to change the (% style="color:green" %)**uplink interval**. 329 329 330 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 321 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 331 331 332 332 ((( 333 -(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.** 334 - 335 335 336 -))) 337 337 338 -**NOTE:When the firmware version is v1.3.2 and later firmware:** 339 339 340 - **Bydefault, the device willsend an uplink message every2 hours. Each Uplink Include8 set of records in this 2 hour(15 minute interval / record).**327 +(% style="color:red" %)**NOTE:** 341 341 329 +(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** 342 342 331 +(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:** 332 +))) 333 + 334 +(% 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).** 335 + 336 + 343 343 == 2.3 Uplink Payload == 344 344 339 +=== 2.3.1 Before Firmware v1.3.2 === 345 345 341 + 346 346 In this mode, uplink payload includes in total 14 bytes 347 347 348 - 349 349 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 350 350 |=(% style="width: 60px;" %)((( 351 351 **Size(bytes)** ... ... @@ -353,7 +353,7 @@ 353 353 |(% 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"]] 354 354 355 355 ((( 356 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 1uplink data.351 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 357 357 ))) 358 358 359 359 ... ... @@ -360,67 +360,72 @@ 360 360 [[image:1657331036973-987.png]] 361 361 362 362 363 -((( 364 -The payload is ASCII string, representative same HEX: 365 -))) 358 +The payload is **ASCII** string, representative same HEX: 366 366 367 -((( 368 -0x72403155615900640c6c19029200 where: 369 -))) 360 +(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** 370 370 371 -* ((( 372 -Device ID: 0x724031556159 = 724031556159 373 -))) 374 -* ((( 375 -Version: 0x0064=100=1.0.0 376 -))) 362 +**where :** 377 377 378 -* ((( 379 -BAT: 0x0c6c = 3180 mV = 3.180V 380 -))) 381 -* ((( 382 -Signal: 0x19 = 25 383 -))) 384 -* ((( 385 -Distance: 0x0292= 658 mm 386 -))) 387 -* ((( 388 -Interrupt: 0x00 = 0 364 +* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159 389 389 390 - 391 -))) 366 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 392 392 393 -** NOTE:Whenthefirmwareversionisv1.3.2andlaterfirmware:**368 +* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V 394 394 370 +* (% style="color:#037691" %)**Signal:**(%%) 0x19 = 25 371 + 372 +* (% style="color:#037691" %)**Distance:** (%%)0x0292= 658 mm 373 + 374 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 375 + 376 + 377 + 378 +=== 2.3.2 Since firmware v1.3.2 === 379 + 380 + 395 395 In this mode, uplink payload includes 69 bytes in total by default. 396 396 397 397 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. 398 398 399 -|**Size(bytes)**|**8**|2|2|1|1|1|2|4|2|4 400 -|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Distance|Timestamp|Distance|Timestamp....... 385 +(% border="1" style="background-color:#ffffcc; color:green; width:490px" %) 386 +|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:70px" %)**4**|(% style="width:40px" %)**2**|(% style="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....... 401 401 402 402 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 403 403 404 404 [[image:image-20220908175246-1.png]] 405 405 393 + 406 406 The payload is ASCII string, representative same HEX: 407 407 408 -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:396 +**0x (% style="color:red" %)f867787050213317 (% style="color:blue" %)0084 (% style="color:green" %)0cf4 (% style="color:#00b0f0" %)1e (% style="color:#7030a0" %)01 (% style="color:#d60093" %)00(% style="color:#a14d07" %) 0039 (% style="color:#0020b0" %)6315537b (% style="color:#663300" %)00396319baf0 00396319ba3c 00396319b988 00396319b8d4 00396319b820 00396319b76c 00396319b6b8 00396319b604 (%%)** 409 409 410 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317 411 -* (% style="color:red" %)Version: 0x0084=132=1.3.2 412 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V 413 -* (% style="color:blue" %)Singal: 0x1e = 30 414 -* (% style="color:red" %)Mod: 0x01 = 1 415 -* Interrupt: 0x00= 0 416 -* Distance: 0x0039= 57 = 57 417 -* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 418 -* Distance,Time stamp : 00396319baf0 419 -* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,....... 398 +**where:** 420 420 421 - ==2.4Payload Explanation and SensorInterface ==400 +* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317 422 422 402 +* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2 423 423 404 +* (% style="color:#037691" %)**BAT:**(%%) 0x0cf4 = 3316 mV = 3.316V 405 + 406 +* (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 407 + 408 +* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 409 + 410 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 411 + 412 +* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57 413 + 414 +* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 415 + 416 +* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0 417 + 418 +* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 419 + 420 + 421 + 422 +== 2.4 Payload Explanation and Sensor Interface == 423 + 424 424 === 2.4.1 Device ID === 425 425 426 426 ... ... @@ -435,7 +435,7 @@ 435 435 ))) 436 436 437 437 ((( 438 -**Example:** 438 +(% style="color:blue" %)**Example :** 439 439 ))) 440 440 441 441 ((( ... ... @@ -443,20 +443,22 @@ 443 443 ))) 444 444 445 445 ((( 446 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 446 +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. 447 447 ))) 448 448 449 449 450 -**NOTE:When the firmware version is v1.3.2 and later firmware:** 450 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:** 451 451 452 -By default, the Device ID equal to the last 15 bits of IMEI. 452 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.** 453 453 454 -User can use **AT+DEUI** to set Device ID 454 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 455 455 456 -**Example:** 457 457 457 +(% style="color:blue" %)**Example :** 458 + 458 458 AT+DEUI=868411056754138 459 459 461 + 460 460 === 2.4.2 Version Info === 461 461 462 462 ... ... @@ -469,7 +469,6 @@ 469 469 ))) 470 470 471 471 472 - 473 473 === 2.4.3 Battery Info === 474 474 475 475 ... ... @@ -482,7 +482,6 @@ 482 482 ))) 483 483 484 484 485 - 486 486 === 2.4.4 Signal Strength === 487 487 488 488 ... ... @@ -515,7 +515,6 @@ 515 515 ))) 516 516 517 517 518 - 519 519 === 2.4.5 Distance === 520 520 521 521 ... ... @@ -535,10 +535,6 @@ 535 535 536 536 ))) 537 537 538 -((( 539 - 540 -))) 541 - 542 542 === 2.4.6 Digital Interrupt === 543 543 544 544 ... ... @@ -551,7 +551,7 @@ 551 551 ))) 552 552 553 553 ((( 554 -(% 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]])**.** 549 +(% 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]])**.** 555 555 ))) 556 556 557 557 ... ... @@ -573,7 +573,6 @@ 573 573 ))) 574 574 575 575 576 - 577 577 === 2.4.7 +5V Output === 578 578 579 579 ... ... @@ -599,7 +599,6 @@ 599 599 ))) 600 600 601 601 602 - 603 603 == 2.5 Downlink Payload == 604 604 605 605 ... ... @@ -652,12 +652,13 @@ 652 652 ))) 653 653 654 654 655 -== 2.6 Distance alarm function == 648 +== 2.6 Distance alarm function(Since firmware v1.3.2) == 656 656 657 -➢ AT Command: 658 658 659 -AT +LDDSALARM=min,max651 +(% style="color:blue" %)** ➢ AT Command:** 660 660 653 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max** 654 + 661 661 ² When min=0, and max≠0, Alarm higher than max 662 662 663 663 ² When min≠0, and max=0, Alarm lower than min ... ... @@ -664,28 +664,35 @@ 664 664 665 665 ² When min≠0 and max≠0, Alarm higher than max or lower than min 666 666 667 -Example: 668 668 669 - AT+LDDSALARM=260,2000 ~/~/ Alarm when distancewerthan260.662 +(% style="color:blue" %)** Example:** 670 670 664 +**AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 671 671 672 -== 2.7 Set the number of data to be uploaded and the recording time == 673 673 674 - ➢ATCommand:667 +== 2.7 Set the number of data to be uploaded and the recording time == 675 675 676 -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) 677 677 678 - AT+NOUD=8~/~/The device uploads8 sets of recorded databy default. Up to 32 setsofrecorddatacan be uploaded.670 +(% style="color:blue" %)** ➢ AT Command:** 679 679 680 -== 2.8 Read or Clear cached data == 672 +* (% 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) 673 +* (% 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. 681 681 682 - ➢ATCommand:675 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 683 683 684 - AT+CDP ~/~/ Read cacheddata677 +[[image:image-20221009001114-1.png||height="687" width="955"]] 685 685 679 + 680 +== 2.8 Read or Clear cached data == 681 + 682 + 683 +(% style="color:blue" %)** ➢ AT Command:** 684 + 685 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 686 +* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 687 + 686 686 [[image:image-20220908175333-2.png]] 687 687 688 -AT+CDP=0 ~/~/ Clear cached data 689 689 690 690 == 2.9 LED Indicator == 691 691 ... ... @@ -703,7 +703,6 @@ 703 703 ))) 704 704 705 705 706 - 707 707 == 2.10 Firmware Change Log == 708 708 709 709 ... ... @@ -712,100 +712,18 @@ 712 712 ))) 713 713 714 714 ((( 715 - 716 -))) 717 - 718 -((( 719 719 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 720 720 ))) 721 721 722 722 719 +== 2.11 Battery & Power Consumption == 723 723 724 -== 2.11 Battery Analysis == 725 725 722 +NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 726 726 727 - === 2.11.1 BatteryType===724 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 728 728 729 729 730 -((( 731 -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. 732 -))) 733 - 734 -((( 735 -The battery is designed to last for several years depends on the actually use environment and update interval. 736 -))) 737 - 738 -((( 739 -The battery related documents as below: 740 -))) 741 - 742 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 743 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 744 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 745 - 746 -((( 747 -[[image:image-20220709101450-2.png]] 748 -))) 749 - 750 - 751 - 752 -=== 2.11.2 Power consumption Analyze === 753 - 754 - 755 -((( 756 -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. 757 -))) 758 - 759 - 760 -((( 761 -Instruction to use as below: 762 -))) 763 - 764 -((( 765 -(% 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/]] 766 -))) 767 - 768 - 769 -((( 770 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 771 -))) 772 - 773 -* ((( 774 -Product Model 775 -))) 776 -* ((( 777 -Uplink Interval 778 -))) 779 -* ((( 780 -Working Mode 781 -))) 782 - 783 -((( 784 -And the Life expectation in difference case will be shown on the right. 785 -))) 786 - 787 -[[image:image-20220709110451-3.png]] 788 - 789 - 790 - 791 -=== 2.11.3 Battery Note === 792 - 793 - 794 -((( 795 -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. 796 -))) 797 - 798 - 799 - 800 -=== 2.11.4 Replace the battery === 801 - 802 - 803 -((( 804 -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). 805 -))) 806 - 807 - 808 - 809 809 = 3. Access NB-IoT Module = 810 810 811 811 ... ... @@ -822,10 +822,8 @@ 822 822 [[image:1657333200519-600.png]] 823 823 824 824 825 - 826 826 = 4. Using the AT Commands = 827 827 828 - 829 829 == 4.1 Access AT Commands == 830 830 831 831 ... ... @@ -832,96 +832,94 @@ 832 832 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]] 833 833 834 834 835 -AT+<CMD>? : Help on <CMD> 751 +AT+<CMD>? : Help on <CMD> 836 836 837 -AT+<CMD> : Run <CMD> 753 +AT+<CMD> : Run <CMD> 838 838 839 -AT+<CMD>=<value> : Set the value 755 +AT+<CMD>=<value> : Set the value 840 840 841 -AT+<CMD>=? : Get the value 757 +AT+<CMD>=? : Get the value 842 842 843 843 844 844 (% style="color:#037691" %)**General Commands**(%%) 845 845 846 -AT : Attention 762 +AT : Attention 847 847 848 -AT? : Short Help 764 +AT? : Short Help 849 849 850 -ATZ : MCU Reset 766 +ATZ : MCU Reset 851 851 852 -AT+TDC : Application Data Transmission Interval 768 +AT+TDC : Application Data Transmission Interval 853 853 854 -AT+CFG : Print all configurations 770 +AT+CFG : Print all configurations 855 855 856 -AT+CFGMOD : Working mode selection 772 +AT+CFGMOD : Working mode selection 857 857 858 -AT+INTMOD : Set the trigger interrupt mode 774 +AT+INTMOD : Set the trigger interrupt mode 859 859 860 -AT+5VT : Set extend the time of 5V power 776 +AT+5VT : Set extend the time of 5V power 861 861 862 -AT+PRO : Choose agreement 778 +AT+PRO : Choose agreement 863 863 864 -AT+WEIGRE : Get weight or set weight to 0 780 +AT+WEIGRE : Get weight or set weight to 0 865 865 866 -AT+WEIGAP : Get or Set the GapValue of weight 782 +AT+WEIGAP : Get or Set the GapValue of weight 867 867 868 -AT+RXDL : Extend the sending and receiving time 784 +AT+RXDL : Extend the sending and receiving time 869 869 870 -AT+CNTFAC : Get or set counting parameters 786 +AT+CNTFAC : Get or set counting parameters 871 871 872 -AT+SERVADDR 788 +AT+SERVADDR : Server Address 873 873 874 -AT+TR 790 +AT+TR : Get or Set record time" 875 875 876 -AT+APN : Get or set the APN 792 +AT+APN : Get or set the APN 877 877 878 -AT+FBAND 794 +AT+FBAND : Get or Set whether to automatically modify the frequency band 879 879 880 -AT+DNSCFG 796 +AT+DNSCFG : Get or Set DNS Server 881 881 882 -AT+GETSENSORVALUE : Returns the current sensor measurement 798 +AT+GETSENSORVALUE : Returns the current sensor measurement 883 883 884 -AT+NOUD 800 +AT+NOUD : Get or Set the number of data to be uploaded 885 885 886 -AT+CDP : Read or Clear cached data 802 +AT+CDP : Read or Clear cached data 887 887 888 -AT+LDDSALARM : Get or Set alarm of distance 804 +AT+LDDSALARM : Get or Set alarm of distance 889 889 890 890 891 891 (% style="color:#037691" %)**COAP Management** 892 892 893 -AT+URI : Resource parameters 809 +AT+URI : Resource parameters 894 894 895 895 896 896 (% style="color:#037691" %)**UDP Management** 897 897 898 -AT+CFM : Upload confirmation mode (only valid for UDP) 814 +AT+CFM : Upload confirmation mode (only valid for UDP) 899 899 900 900 901 901 (% style="color:#037691" %)**MQTT Management** 902 902 903 -AT+CLIENT 819 +AT+CLIENT : Get or Set MQTT client 904 904 905 -AT+UNAME 821 +AT+UNAME : Get or Set MQTT Username 906 906 907 -AT+PWD 823 +AT+PWD : Get or Set MQTT password 908 908 909 -AT+PUBTOPIC 825 +AT+PUBTOPIC : Get or Set MQTT publish topic 910 910 911 -AT+SUBTOPIC 827 +AT+SUBTOPIC : Get or Set MQTT subscription topic 912 912 913 913 914 914 (% style="color:#037691" %)**Information** 915 915 916 -AT+FDR : Factory Data Reset 832 +AT+FDR : Factory Data Reset 917 917 918 -AT+PWORD : Serial Access Password 834 +AT+PWORD : Serial Access Password 919 919 920 920 921 - 922 922 = 5. FAQ = 923 923 924 - 925 925 == 5.1 How to Upgrade Firmware == 926 926 927 927 ... ... @@ -938,10 +938,8 @@ 938 938 ))) 939 939 940 940 941 - 942 942 = 6. Trouble Shooting = 943 943 944 - 945 945 == 6.1 Connection problem when uploading firmware == 946 946 947 947 ... ... @@ -954,14 +954,11 @@ 954 954 955 955 ))) 956 956 957 - 958 958 == 6.2 AT Command input doesn't work == 959 959 960 960 961 961 ((( 962 962 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. 963 - 964 - 965 965 ))) 966 966 967 967 ... ... @@ -971,11 +971,6 @@ 971 971 Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 972 972 973 973 974 -(% class="wikigeneratedid" %) 975 -((( 976 - 977 -))) 978 - 979 979 = 8. Packing Info = 980 980 981 981 ((( ... ... @@ -990,7 +990,6 @@ 990 990 ((( 991 991 992 992 993 - 994 994 (% style="color:#037691" %)**Dimension and weight**: 995 995 996 996 * Device Size: 13.0 x 5 x 4.5 cm ... ... @@ -1002,7 +1002,6 @@ 1002 1002 ((( 1003 1003 1004 1004 1005 - 1006 1006 1007 1007 ))) 1008 1008
- image-20221009001114-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +282.9 KB - Content