Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual
Last modified by Bei Jinggeng on 2024/05/31 09:53
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- 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,9 +72,6 @@ 72 72 * 8500mAh Battery for long term use 73 73 74 74 75 - 76 - 77 - 78 78 == 1.3 Specification == 79 79 80 80 ... ... @@ -85,12 +85,12 @@ 85 85 86 86 (% style="color:#037691" %)**NB-IoT Spec:** 87 87 88 -* -B1 @H-FDD: 2100MHz89 -* -B3 @H-FDD: 1800MHz90 -* -B8 @H-FDD: 900MHz91 -* -B5 @H-FDD: 850MHz92 -* -B20 @H-FDD: 800MHz93 -* -B28 @H-FDD: 700MHz83 +* B1 @H-FDD: 2100MHz 84 +* B3 @H-FDD: 1800MHz 85 +* B8 @H-FDD: 900MHz 86 +* B5 @H-FDD: 850MHz 87 +* B20 @H-FDD: 800MHz 88 +* B28 @H-FDD: 700MHz 94 94 95 95 (% style="color:#037691" %)**Battery:** 96 96 ... ... @@ -106,9 +106,6 @@ 106 106 * Max transmit power: 350mA@3.3v 107 107 108 108 109 - 110 - 111 - 112 112 == 1.4 Applications == 113 113 114 114 ... ... @@ -123,8 +123,6 @@ 123 123 124 124 125 125 126 - 127 - 128 128 == 1.5 Pin Definitions == 129 129 130 130 ... ... @@ -131,10 +131,8 @@ 131 131 [[image:1657328609906-564.png]] 132 132 133 133 134 - 135 135 = 2. Use NDDS75 to communicate with IoT Server = 136 136 137 - 138 138 == 2.1 How it works == 139 139 140 140 ... ... @@ -157,10 +157,8 @@ 157 157 158 158 ))) 159 159 160 - 161 161 == 2.2 Configure the NDDS75 == 162 162 163 - 164 164 === 2.2.1 Test Requirement === 165 165 166 166 ... ... @@ -180,7 +180,6 @@ 180 180 [[image:1657328756309-230.png]] 181 181 182 182 183 - 184 184 === 2.2.2 Insert SIM card === 185 185 186 186 ... ... @@ -196,7 +196,6 @@ 196 196 [[image:1657328884227-504.png]] 197 197 198 198 199 - 200 200 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 201 201 202 202 ... ... @@ -209,13 +209,13 @@ 209 209 [[image:image-20220709092052-2.png]] 210 210 211 211 212 -**Connection:** 196 +(% style="color:blue" %)**Connection:** 213 213 214 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 198 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 215 215 216 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 200 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 217 217 218 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 202 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 219 219 220 220 221 221 In the PC, use below serial tool settings: ... ... @@ -238,7 +238,6 @@ 238 238 ))) 239 239 240 240 241 - 242 242 === 2.2.4 Use CoAP protocol to uplink data === 243 243 244 244 ... ... @@ -253,10 +253,10 @@ 253 253 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 254 254 ))) 255 255 * ((( 256 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 239 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 257 257 ))) 258 258 * ((( 259 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 242 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 260 260 261 261 262 262 ... ... @@ -281,13 +281,12 @@ 281 281 [[image:1657330472797-498.png]] 282 282 283 283 284 - 285 285 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 286 286 287 287 288 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 289 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 290 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 270 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 271 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 272 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 291 291 292 292 [[image:1657330501006-241.png]] 293 293 ... ... @@ -295,17 +295,16 @@ 295 295 [[image:1657330533775-472.png]] 296 296 297 297 298 - 299 299 === 2.2.6 Use MQTT protocol to uplink data === 300 300 301 301 302 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 303 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 304 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 305 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 306 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 307 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 308 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 283 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 284 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 285 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 286 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 287 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 288 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ Set the sending topic of MQTT 289 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ Set the subscription topic of MQTT 309 309 310 310 [[image:1657249978444-674.png]] 311 311 ... ... @@ -318,12 +318,11 @@ 318 318 ))) 319 319 320 320 321 - 322 322 === 2.2.7 Use TCP protocol to uplink data === 323 323 324 324 325 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 326 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 305 +* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 306 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 327 327 328 328 [[image:image-20220709093918-1.png]] 329 329 ... ... @@ -331,13 +331,12 @@ 331 331 [[image:image-20220709093918-2.png]] 332 332 333 333 334 - 335 335 === 2.2.8 Change Update Interval === 336 336 337 337 338 338 User can use below command to change the (% style="color:green" %)**uplink interval**. 339 339 340 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 319 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 341 341 342 342 ((( 343 343 ... ... @@ -353,23 +353,21 @@ 353 353 (% 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).** 354 354 355 355 356 - 357 357 == 2.3 Uplink Payload == 358 358 337 +=== 2.3.1 Before Firmware v1.3.2 === 359 359 360 -=== 2.3.1 Before Firmware 1.3.2 === 361 361 362 - 363 363 In this mode, uplink payload includes in total 14 bytes 364 364 365 -(% border="1" cellspacing="10" style="background-color:#fff fcc;color:green;width:440px" %)366 -|=(% style="width: 60px;" %)((( 342 +(% border="1" cellspacing="10" style="background-color:#f2f2f2; width:440px" %) 343 +|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)((( 367 367 **Size(bytes)** 368 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 345 +)))|=(% 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** 369 369 |(% 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"]] 370 370 371 371 ((( 372 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 1uplink data.349 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 373 373 ))) 374 374 375 375 ... ... @@ -376,49 +376,34 @@ 376 376 [[image:1657331036973-987.png]] 377 377 378 378 379 -((( 380 380 The payload is **ASCII** string, representative same HEX: 381 -))) 382 382 383 -((( 384 -0x72403155615900640c6c19029200 where: 385 -))) 358 +(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** 386 386 387 -* ((( 388 -Device ID: 0x724031556159 = 724031556159 389 -))) 390 -* ((( 391 -Version: 0x0064=100=1.0.0 392 -))) 360 +**where :** 393 393 394 -* ((( 395 -BAT: 0x0c6c = 3180 mV = 3.180V 396 -))) 397 -* ((( 398 -Signal: 0x19 = 25 399 -))) 400 -* ((( 401 -Distance: 0x0292= 658 mm 402 -))) 403 -* ((( 404 -Interrupt: 0x00 = 0 362 +* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159 405 405 364 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 406 406 366 +* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V 407 407 368 +* (% style="color:#037691" %)**Signal:**(%%) 0x19 = 25 408 408 409 - 410 -))) 370 +* (% style="color:#037691" %)**Distance:** (%%)0x0292= 658 mm 411 411 412 -= ==**2.3.2 Sincefirmware v1.3.2** ===372 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 413 413 374 +=== 2.3.2 Since firmware v1.3.2 === 414 414 376 + 415 415 In this mode, uplink payload includes 69 bytes in total by default. 416 416 417 417 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. 418 418 419 -(% border=" 2" style="background-color:#ffffcc; color:green; width:896px" %)420 -|(% 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" %)4421 -|(% 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....... 381 +(% border="1" style="background-color:#ffffcc; color:green; width:490px" %) 382 +|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**8**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:60px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:70px;background-color:#D9E2F3;color:#0070C0" %)**4**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:60px;background-color:#D9E2F3;color:#0070C0" %)**4** 383 +|=(% 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....... 422 422 423 423 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 424 424 ... ... @@ -427,26 +427,32 @@ 427 427 428 428 The payload is ASCII string, representative same HEX: 429 429 430 -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:392 +**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 (%%)** 431 431 432 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317 433 -* (% style="color:red" %)Version: 0x0084=132=1.3.2 434 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V 435 -* (% style="color:blue" %)Singal: 0x1e = 30 436 -* (% style="color:red" %)Mod: 0x01 = 1 437 -* Interrupt: 0x00= 0 438 -* Distance: 0x0039= 57 = 57 439 -* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 440 -* Distance,Time stamp : 00396319baf0 441 -* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,....... 394 +**where:** 442 442 396 +* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317 443 443 398 +* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2 444 444 400 +* (% style="color:#037691" %)**BAT:**(%%) 0x0cf4 = 3316 mV = 3.316V 445 445 402 +* (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 446 446 447 - ==2.4Payload ExplanationandSensorInterface==404 +* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 448 448 406 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 449 449 408 +* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57 409 + 410 +* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 411 + 412 +* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0 413 + 414 +* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 415 + 416 +== 2.4 Payload Explanation and Sensor Interface == 417 + 450 450 === 2.4.1 Device ID === 451 451 452 452 ... ... @@ -485,7 +485,6 @@ 485 485 AT+DEUI=868411056754138 486 486 487 487 488 - 489 489 === 2.4.2 Version Info === 490 490 491 491 ... ... @@ -498,7 +498,6 @@ 498 498 ))) 499 499 500 500 501 - 502 502 === 2.4.3 Battery Info === 503 503 504 504 ... ... @@ -511,7 +511,6 @@ 511 511 ))) 512 512 513 513 514 - 515 515 === 2.4.4 Signal Strength === 516 516 517 517 ... ... @@ -544,7 +544,6 @@ 544 544 ))) 545 545 546 546 547 - 548 548 === 2.4.5 Distance === 549 549 550 550 ... ... @@ -564,10 +564,6 @@ 564 564 565 565 ))) 566 566 567 -((( 568 - 569 -))) 570 - 571 571 === 2.4.6 Digital Interrupt === 572 572 573 573 ... ... @@ -580,7 +580,7 @@ 580 580 ))) 581 581 582 582 ((( 583 -(% 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]])**.** 543 +(% 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]])**.** 584 584 ))) 585 585 586 586 ... ... @@ -602,7 +602,6 @@ 602 602 ))) 603 603 604 604 605 - 606 606 === 2.4.7 +5V Output === 607 607 608 608 ... ... @@ -628,7 +628,6 @@ 628 628 ))) 629 629 630 630 631 - 632 632 == 2.5 Downlink Payload == 633 633 634 634 ... ... @@ -681,7 +681,6 @@ 681 681 ))) 682 682 683 683 684 - 685 685 == 2.6 Distance alarm function(Since firmware v1.3.2) == 686 686 687 687 ... ... @@ -701,16 +701,17 @@ 701 701 **AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 702 702 703 703 704 - 705 705 == 2.7 Set the number of data to be uploaded and the recording time == 706 706 707 707 708 708 (% style="color:blue" %)** ➢ AT Command:** 709 709 710 -* (% 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) 711 -* (% 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. 666 +* (% 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) 667 +* (% 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. 712 712 669 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 713 713 671 +[[image:image-20221009001114-1.png||height="687" width="955"]] 714 714 715 715 716 716 == 2.8 Read or Clear cached data == ... ... @@ -718,15 +718,12 @@ 718 718 719 719 (% style="color:blue" %)** ➢ AT Command:** 720 720 721 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 722 -* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 679 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 680 +* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 723 723 724 - 725 - 726 726 [[image:image-20220908175333-2.png]] 727 727 728 728 729 - 730 730 == 2.9 LED Indicator == 731 731 732 732 ... ... @@ -743,7 +743,6 @@ 743 743 ))) 744 744 745 745 746 - 747 747 == 2.10 Firmware Change Log == 748 748 749 749 ... ... @@ -752,100 +752,18 @@ 752 752 ))) 753 753 754 754 ((( 755 - 756 -))) 757 - 758 -((( 759 759 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 760 760 ))) 761 761 762 762 713 +== 2.11 Battery & Power Consumption == 763 763 764 -== 2.11 Battery Analysis == 765 765 716 +NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 766 766 767 - === 2.11.1 BatteryType===718 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 768 768 769 769 770 -((( 771 -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. 772 -))) 773 - 774 -((( 775 -The battery is designed to last for several years depends on the actually use environment and update interval. 776 -))) 777 - 778 -((( 779 -The battery related documents as below: 780 -))) 781 - 782 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 783 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 784 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 785 - 786 -((( 787 -[[image:image-20220709101450-2.png]] 788 -))) 789 - 790 - 791 - 792 -=== 2.11.2 Power consumption Analyze === 793 - 794 - 795 -((( 796 -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. 797 -))) 798 - 799 - 800 -((( 801 -Instruction to use as below: 802 -))) 803 - 804 -((( 805 -(% 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/]] 806 -))) 807 - 808 - 809 -((( 810 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 811 -))) 812 - 813 -* ((( 814 -Product Model 815 -))) 816 -* ((( 817 -Uplink Interval 818 -))) 819 -* ((( 820 -Working Mode 821 -))) 822 - 823 -((( 824 -And the Life expectation in difference case will be shown on the right. 825 -))) 826 - 827 -[[image:image-20220709110451-3.png]] 828 - 829 - 830 - 831 -=== 2.11.3 Battery Note === 832 - 833 - 834 -((( 835 -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. 836 -))) 837 - 838 - 839 - 840 -=== 2.11.4 Replace the battery === 841 - 842 - 843 -((( 844 -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). 845 -))) 846 - 847 - 848 - 849 849 = 3. Access NB-IoT Module = 850 850 851 851 ... ... @@ -862,10 +862,8 @@ 862 862 [[image:1657333200519-600.png]] 863 863 864 864 865 - 866 866 = 4. Using the AT Commands = 867 867 868 - 869 869 == 4.1 Access AT Commands == 870 870 871 871 ... ... @@ -872,96 +872,94 @@ 872 872 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]] 873 873 874 874 875 -AT+<CMD>? : Help on <CMD> 745 +AT+<CMD>? : Help on <CMD> 876 876 877 -AT+<CMD> : Run <CMD> 747 +AT+<CMD> : Run <CMD> 878 878 879 -AT+<CMD>=<value> : Set the value 749 +AT+<CMD>=<value> : Set the value 880 880 881 -AT+<CMD>=? : Get the value 751 +AT+<CMD>=? : Get the value 882 882 883 883 884 884 (% style="color:#037691" %)**General Commands**(%%) 885 885 886 -AT : Attention 756 +AT : Attention 887 887 888 -AT? : Short Help 758 +AT? : Short Help 889 889 890 -ATZ : MCU Reset 760 +ATZ : MCU Reset 891 891 892 -AT+TDC : Application Data Transmission Interval 762 +AT+TDC : Application Data Transmission Interval 893 893 894 -AT+CFG : Print all configurations 764 +AT+CFG : Print all configurations 895 895 896 -AT+CFGMOD : Working mode selection 766 +AT+CFGMOD : Working mode selection 897 897 898 -AT+INTMOD : Set the trigger interrupt mode 768 +AT+INTMOD : Set the trigger interrupt mode 899 899 900 -AT+5VT : Set extend the time of 5V power 770 +AT+5VT : Set extend the time of 5V power 901 901 902 -AT+PRO : Choose agreement 772 +AT+PRO : Choose agreement 903 903 904 -AT+WEIGRE : Get weight or set weight to 0 774 +AT+WEIGRE : Get weight or set weight to 0 905 905 906 -AT+WEIGAP : Get or Set the GapValue of weight 776 +AT+WEIGAP : Get or Set the GapValue of weight 907 907 908 -AT+RXDL : Extend the sending and receiving time 778 +AT+RXDL : Extend the sending and receiving time 909 909 910 -AT+CNTFAC : Get or set counting parameters 780 +AT+CNTFAC : Get or set counting parameters 911 911 912 -AT+SERVADDR 782 +AT+SERVADDR : Server Address 913 913 914 -AT+TR 784 +AT+TR : Get or Set record time" 915 915 916 -AT+APN : Get or set the APN 786 +AT+APN : Get or set the APN 917 917 918 -AT+FBAND 788 +AT+FBAND : Get or Set whether to automatically modify the frequency band 919 919 920 -AT+DNSCFG 790 +AT+DNSCFG : Get or Set DNS Server 921 921 922 -AT+GETSENSORVALUE : Returns the current sensor measurement 792 +AT+GETSENSORVALUE : Returns the current sensor measurement 923 923 924 -AT+NOUD 794 +AT+NOUD : Get or Set the number of data to be uploaded 925 925 926 -AT+CDP : Read or Clear cached data 796 +AT+CDP : Read or Clear cached data 927 927 928 -AT+LDDSALARM : Get or Set alarm of distance 798 +AT+LDDSALARM : Get or Set alarm of distance 929 929 930 930 931 931 (% style="color:#037691" %)**COAP Management** 932 932 933 -AT+URI : Resource parameters 803 +AT+URI : Resource parameters 934 934 935 935 936 936 (% style="color:#037691" %)**UDP Management** 937 937 938 -AT+CFM : Upload confirmation mode (only valid for UDP) 808 +AT+CFM : Upload confirmation mode (only valid for UDP) 939 939 940 940 941 941 (% style="color:#037691" %)**MQTT Management** 942 942 943 -AT+CLIENT 813 +AT+CLIENT : Get or Set MQTT client 944 944 945 -AT+UNAME 815 +AT+UNAME : Get or Set MQTT Username 946 946 947 -AT+PWD 817 +AT+PWD : Get or Set MQTT password 948 948 949 -AT+PUBTOPIC 819 +AT+PUBTOPIC : Get or Set MQTT publish topic 950 950 951 -AT+SUBTOPIC 821 +AT+SUBTOPIC : Get or Set MQTT subscription topic 952 952 953 953 954 954 (% style="color:#037691" %)**Information** 955 955 956 -AT+FDR : Factory Data Reset 826 +AT+FDR : Factory Data Reset 957 957 958 -AT+PWORD : Serial Access Password 828 +AT+PWORD : Serial Access Password 959 959 960 960 961 - 962 962 = 5. FAQ = 963 963 964 - 965 965 == 5.1 How to Upgrade Firmware == 966 966 967 967 ... ... @@ -978,10 +978,8 @@ 978 978 ))) 979 979 980 980 981 - 982 982 = 6. Trouble Shooting = 983 983 984 - 985 985 == 6.1 Connection problem when uploading firmware == 986 986 987 987 ... ... @@ -994,17 +994,20 @@ 994 994 995 995 ))) 996 996 997 - 998 998 == 6.2 AT Command input doesn't work == 999 999 1000 1000 1001 1001 ((( 1002 1002 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. 1003 - 1004 - 1005 1005 ))) 1006 1006 1007 1007 871 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 872 + 873 + 874 +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]]//**. 875 + 876 + 1008 1008 = 7. Order Info = 1009 1009 1010 1010 ... ... @@ -1011,11 +1011,6 @@ 1011 1011 Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 1012 1012 1013 1013 1014 -(% class="wikigeneratedid" %) 1015 -((( 1016 - 1017 -))) 1018 - 1019 1019 = 8. Packing Info = 1020 1020 1021 1021 ((( ... ... @@ -1030,7 +1030,6 @@ 1030 1030 ((( 1031 1031 1032 1032 1033 - 1034 1034 (% style="color:#037691" %)**Dimension and weight**: 1035 1035 1036 1036 * Device Size: 13.0 x 5 x 4.5 cm ... ... @@ -1042,7 +1042,6 @@ 1042 1042 ((( 1043 1043 1044 1044 1045 - 1046 1046 1047 1047 ))) 1048 1048 ... ... @@ -1050,4 +1050,5 @@ 1050 1050 1051 1051 1052 1052 * 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. 915 + 1053 1053 * 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,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +282.9 KB - Content