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, 0 added, 3 removed)
Details
- Page properties
-
- Content
-
... ... @@ -53,6 +53,7 @@ 53 53 [[image:1657327959271-447.png]] 54 54 55 55 56 + 56 56 == 1.2 Features == 57 57 58 58 ... ... @@ -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 85 +* - B1 @H-FDD: 2100MHz 86 +* - B3 @H-FDD: 1800MHz 87 +* - B8 @H-FDD: 900MHz 88 +* - B5 @H-FDD: 850MHz 89 +* - B20 @H-FDD: 800MHz 90 +* - B28 @H-FDD: 700MHz 90 90 91 91 (% style="color:#037691" %)**Battery:** 92 92 ... ... @@ -123,6 +123,7 @@ 123 123 [[image:1657328609906-564.png]] 124 124 125 125 127 + 126 126 = 2. Use NDDS75 to communicate with IoT Server = 127 127 128 128 == 2.1 How it works == ... ... @@ -147,8 +147,10 @@ 147 147 148 148 ))) 149 149 152 + 150 150 == 2.2 Configure the NDDS75 == 151 151 155 + 152 152 === 2.2.1 Test Requirement === 153 153 154 154 ... ... @@ -168,6 +168,7 @@ 168 168 [[image:1657328756309-230.png]] 169 169 170 170 175 + 171 171 === 2.2.2 Insert SIM card === 172 172 173 173 ... ... @@ -183,6 +183,7 @@ 183 183 [[image:1657328884227-504.png]] 184 184 185 185 191 + 186 186 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 187 187 188 188 ... ... @@ -194,16 +194,15 @@ 194 194 195 195 [[image:image-20220709092052-2.png]] 196 196 203 +**Connection:** 197 197 198 -(% style="color: blue" %)**Connection:**205 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 199 199 200 - (% style="background-color:yellow" %) **USB TTLGND <~-~-~-~->GND**207 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 201 201 202 - **~(% style="background-color:yellow" %)USB TTLTXD <~-~-~-~-> UART_RXD(%%)**209 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 203 203 204 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 205 205 206 - 207 207 In the PC, use below serial tool settings: 208 208 209 209 * Baud: (% style="color:green" %)**9600** ... ... @@ -218,12 +218,12 @@ 218 218 219 219 [[image:1657329814315-101.png]] 220 220 221 - 222 222 ((( 223 -(% style="color:red" %) **Note: the valid AT Commands can be found at:**(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]**227 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]] 224 224 ))) 225 225 226 226 231 + 227 227 === 2.2.4 Use CoAP protocol to uplink data === 228 228 229 229 ... ... @@ -238,39 +238,33 @@ 238 238 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 239 239 ))) 240 240 * ((( 241 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ 246 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 242 242 ))) 243 243 * ((( 244 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 245 - 246 - 249 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 247 247 ))) 248 248 249 249 ((( 250 250 For parameter description, please refer to AT command set 251 - 252 - 253 253 ))) 254 254 255 255 [[image:1657330452568-615.png]] 256 256 257 257 258 - 259 259 ((( 260 260 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. 261 - 262 - 263 263 ))) 264 264 265 265 [[image:1657330472797-498.png]] 266 266 267 267 266 + 268 268 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 269 269 270 270 271 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ 272 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ 273 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 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 274 274 275 275 [[image:1657330501006-241.png]] 276 276 ... ... @@ -278,16 +278,17 @@ 278 278 [[image:1657330533775-472.png]] 279 279 280 280 280 + 281 281 === 2.2.6 Use MQTT protocol to uplink data === 282 282 283 283 284 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ 285 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ 286 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ 287 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ 288 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ 289 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ 290 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ 284 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 285 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 286 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 287 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 288 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 289 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 290 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 291 291 292 292 [[image:1657249978444-674.png]] 293 293 ... ... @@ -300,11 +300,12 @@ 300 300 ))) 301 301 302 302 303 + 303 303 === 2.2.7 Use TCP protocol to uplink data === 304 304 305 305 306 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ 307 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ 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 308 308 309 309 [[image:image-20220709093918-1.png]] 310 310 ... ... @@ -312,113 +312,78 @@ 312 312 [[image:image-20220709093918-2.png]] 313 313 314 314 316 + 315 315 === 2.2.8 Change Update Interval === 316 316 317 317 318 318 User can use below command to change the (% style="color:green" %)**uplink interval**. 319 319 320 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ 322 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 321 321 322 322 ((( 323 - 324 - 325 325 (% style="color:red" %)**NOTE:** 326 +))) 326 326 328 +((( 327 327 (% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** 328 - 329 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:** 330 330 ))) 331 331 332 -(% 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).** 333 333 334 334 335 335 == 2.3 Uplink Payload == 336 336 337 -=== 2.3.1 Before Firmware v1.3.2 === 338 338 339 - 340 340 In this mode, uplink payload includes in total 14 bytes 341 341 342 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:440px" %) 343 -|=(% style="width: 61px;background-color:#D9E2F3;color:#0070C0" %)((( 339 + 340 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 341 +|=(% style="width: 60px;" %)((( 344 344 **Size(bytes)** 345 -)))|=(% style="width: 6 1px;background-color:#D9E2F3;color:#0070C0" %)**6**|=(% style="width: 37px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 37px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 82px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 102px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**1**343 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 346 346 |(% 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 347 348 348 ((( 349 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 347 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 350 350 ))) 351 351 352 352 353 353 [[image:1657331036973-987.png]] 354 354 355 - 356 -The payload is **ASCII** string, representative same HEX: 357 - 358 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** 359 - 360 -**where :** 361 - 362 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159 363 - 364 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 365 - 366 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V 367 - 368 -* (% style="color:#037691" %)**Signal:**(%%) 0x19 = 25 369 - 370 -* (% style="color:#037691" %)**Distance:** (%%)0x0292= 658 mm 371 - 372 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 373 - 374 - 375 - 376 -=== 2.3.2 Since firmware v1.3.2 === 377 - 378 - 379 -In this mode, uplink payload includes 69 bytes in total by default. 380 - 381 -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. 382 - 383 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:490px" %) 384 -|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**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** 385 -|(% 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....... 386 - 387 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 388 - 389 -[[image:image-20220908175246-1.png]] 390 - 391 - 353 +((( 392 392 The payload is ASCII string, representative same HEX: 355 +))) 393 393 394 -**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 (%%)** 357 +((( 358 +0x72403155615900640c6c19029200 where: 359 +))) 395 395 396 -**where:** 361 +* ((( 362 +Device ID: 0x724031556159 = 724031556159 363 +))) 364 +* ((( 365 +Version: 0x0064=100=1.0.0 366 +))) 397 397 398 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317 368 +* ((( 369 +BAT: 0x0c6c = 3180 mV = 3.180V 370 +))) 371 +* ((( 372 +Signal: 0x19 = 25 373 +))) 374 +* ((( 375 +Distance: 0x0292= 658 mm 376 +))) 377 +* ((( 378 +Interrupt: 0x00 = 0 399 399 400 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2 401 401 402 -* (% style="color:#037691" %)**BAT:**(%%) 0x0cf4 = 3316 mV = 3.316V 403 403 404 -* (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 382 + 383 +))) 405 405 406 -* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 407 - 408 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 409 - 410 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57 411 - 412 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 413 - 414 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0 415 - 416 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 417 - 418 - 419 - 420 420 == 2.4 Payload Explanation and Sensor Interface == 421 421 387 + 422 422 === 2.4.1 Device ID === 423 423 424 424 ... ... @@ -428,12 +428,10 @@ 428 428 429 429 ((( 430 430 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 431 - 432 - 433 433 ))) 434 434 435 435 ((( 436 - (% style="color:blue" %)**Example400 +**Example:** 437 437 ))) 438 438 439 439 ((( ... ... @@ -441,22 +441,11 @@ 441 441 ))) 442 442 443 443 ((( 444 -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.408 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 445 445 ))) 446 446 447 447 448 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:** 449 449 450 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.** 451 - 452 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 453 - 454 - 455 -(% style="color:blue" %)**Example :** 456 - 457 -AT+DEUI=868411056754138 458 - 459 - 460 460 === 2.4.2 Version Info === 461 461 462 462 ... ... @@ -469,6 +469,7 @@ 469 469 ))) 470 470 471 471 425 + 472 472 === 2.4.3 Battery Info === 473 473 474 474 ... ... @@ -481,6 +481,7 @@ 481 481 ))) 482 482 483 483 438 + 484 484 === 2.4.4 Signal Strength === 485 485 486 486 ... ... @@ -513,6 +513,7 @@ 513 513 ))) 514 514 515 515 471 + 516 516 === 2.4.5 Distance === 517 517 518 518 ... ... @@ -519,13 +519,23 @@ 519 519 Get the distance. Flat object range 280mm - 7500mm. 520 520 521 521 ((( 522 -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.**478 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 523 523 ))) 524 524 525 525 ((( 482 +((( 483 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 484 +))) 485 +))) 486 + 487 +((( 526 526 527 527 ))) 528 528 491 +((( 492 + 493 +))) 494 + 529 529 === 2.4.6 Digital Interrupt === 530 530 531 531 ... ... @@ -538,7 +538,7 @@ 538 538 ))) 539 539 540 540 ((( 541 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/ 507 +(% 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]])**.** 542 542 ))) 543 543 544 544 ... ... @@ -546,8 +546,9 @@ 546 546 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. 547 547 ))) 548 548 515 + 549 549 ((( 550 - **Example:**517 +Example: 551 551 ))) 552 552 553 553 ((( ... ... @@ -559,6 +559,7 @@ 559 559 ))) 560 560 561 561 529 + 562 562 === 2.4.7 +5V Output === 563 563 564 564 ... ... @@ -566,6 +566,7 @@ 566 566 NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 567 567 ))) 568 568 537 + 569 569 ((( 570 570 The 5V output time can be controlled by AT Command. 571 571 ))) ... ... @@ -579,17 +579,15 @@ 579 579 ))) 580 580 581 581 551 + 582 582 == 2.5 Downlink Payload == 583 583 584 584 585 585 By default, NDDS75 prints the downlink payload to console port. 586 586 587 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %) 588 -|(% 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)** 589 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4 590 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2 591 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4 557 +[[image:image-20220709100028-1.png]] 592 592 559 + 593 593 ((( 594 594 (% style="color:blue" %)**Examples:** 595 595 ))) ... ... @@ -634,85 +634,126 @@ 634 634 ))) 635 635 636 636 637 -== 2.6 Distance alarm function(Since firmware v1.3.2) == 638 638 605 +== 2.6 LED Indicator == 639 639 640 -(% style="color:blue" %)** ➢ AT Command:** 641 641 642 - (%style="color:#037691"%)**AT+LDDSALARM=min,max**608 +The NDDS75 has an internal LED which is to show the status of different state. 643 643 644 -² When min=0, and max≠0, Alarm higher than max 645 645 646 -² When min≠0, and max=0, Alarm lower than min 611 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 612 +* Then the LED will be on for 1 second means device is boot normally. 613 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 614 +* For each uplink probe, LED will be on for 500ms. 647 647 648 -² When min≠0 and max≠0, Alarm higher than max or lower than min 616 +((( 617 + 618 +))) 649 649 650 650 651 -(% style="color:blue" %)** Example:** 652 652 653 - **AT+ LDDSALARM=260,2000**~/~/ Alarmhendistancelowerthan 260.622 +== 2.7 Firmware Change Log == 654 654 655 655 656 -== 2.7 Set the number of data to be uploaded and the recording time == 625 +((( 626 +Download URL & Firmware Change log 627 +))) 657 657 629 +((( 630 +[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]] 631 +))) 658 658 659 -(% style="color:blue" %)** ➢ AT Command:** 660 660 661 -* (% 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) 662 -* (% 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. 634 +((( 635 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 636 +))) 663 663 664 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 665 665 666 -[[image:image-20221009001114-1.png||height="687" width="955"]] 667 667 640 +== 2.8 Battery Analysis == 668 668 669 -== 2.8 Read or Clearcacheddata==642 +=== 2.8.1 Battery Type === 670 670 671 671 672 -(% style="color:blue" %)** ➢ AT Command:** 645 +((( 646 +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. 647 +))) 673 673 674 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 675 -* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 649 +((( 650 +The battery is designed to last for several years depends on the actually use environment and update interval. 651 +))) 676 676 677 -[[image:image-20220908175333-2.png]] 653 +((( 654 +The battery related documents as below: 655 +))) 678 678 657 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 658 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 659 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 679 679 680 -== 2.9 LED Indicator == 661 +((( 662 +[[image:image-20220709101450-2.png]] 663 +))) 681 681 682 682 683 -The NDDS75 has an internal LED which is to show the status of different state. 684 684 667 +=== 2.8.2 Power consumption Analyze === 685 685 686 -* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 687 -* Then the LED will be on for 1 second means device is boot normally. 688 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 689 -* For each uplink probe, LED will be on for 500ms. 690 690 691 691 ((( 692 - 671 +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. 693 693 ))) 694 694 695 695 696 -== 2.10 Firmware Change Log == 675 +((( 676 +Instruction to use as below: 677 +))) 697 697 679 +((( 680 +(% 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/]] 681 +))) 698 698 683 + 699 699 ((( 700 - Download URL & FirmwareChangelog:[[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]]685 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 701 701 ))) 702 702 688 +* ((( 689 +Product Model 690 +))) 691 +* ((( 692 +Uplink Interval 693 +))) 694 +* ((( 695 +Working Mode 696 +))) 697 + 703 703 ((( 704 - UpgradeInstruction:[[UpgradeFirmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]699 +And the Life expectation in difference case will be shown on the right. 705 705 ))) 706 706 702 +[[image:image-20220709110451-3.png]] 707 707 708 -== 2.11 Battery & Power Consumption == 709 709 710 710 711 - NDDS75uses ER26500 + SPC1520 battery pack.See below link for detail information aboutthebatteryinfoand howto replace.706 +=== 2.8.3 Battery Note === 712 712 713 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 714 714 709 +((( 710 +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. 711 +))) 715 715 713 + 714 + 715 +=== 2.8.4 Replace the battery === 716 + 717 + 718 +((( 719 +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). 720 +))) 721 + 722 + 723 + 716 716 = 3. Access NB-IoT Module = 717 717 718 718 ... ... @@ -722,107 +722,91 @@ 722 722 723 723 ((( 724 724 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/]] 725 - 726 - 727 727 ))) 728 728 729 729 [[image:1657333200519-600.png]] 730 730 731 731 738 + 732 732 = 4. Using the AT Commands = 733 733 734 734 == 4.1 Access AT Commands == 735 735 736 736 737 -See this link for detail: pbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]744 +See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 738 738 739 739 740 -AT+<CMD>? : 747 +AT+<CMD>? : Help on <CMD> 741 741 742 -AT+<CMD> : 749 +AT+<CMD> : Run <CMD> 743 743 744 -AT+<CMD>=<value> : 751 +AT+<CMD>=<value> : Set the value 745 745 746 -AT+<CMD>=? : 753 +AT+<CMD>=? : Get the value 747 747 748 748 749 749 (% style="color:#037691" %)**General Commands**(%%) 750 750 751 -AT : 758 +AT : Attention 752 752 753 -AT? : 760 +AT? : Short Help 754 754 755 -ATZ : 762 +ATZ : MCU Reset 756 756 757 -AT+TDC : 764 +AT+TDC : Application Data Transmission Interval 758 758 759 -AT+CFG : 766 +AT+CFG : Print all configurations 760 760 761 -AT+CFGMOD : 768 +AT+CFGMOD : Working mode selection 762 762 763 -AT+INTMOD : 770 +AT+INTMOD : Set the trigger interrupt mode 764 764 765 -AT+5VT : 772 +AT+5VT : Set extend the time of 5V power 766 766 767 -AT+PRO : 774 +AT+PRO : Choose agreement 768 768 769 -AT+WEIGRE : 776 +AT+WEIGRE : Get weight or set weight to 0 770 770 771 -AT+WEIGAP : 778 +AT+WEIGAP : Get or Set the GapValue of weight 772 772 773 -AT+RXDL : 780 +AT+RXDL : Extend the sending and receiving time 774 774 775 -AT+CNTFAC : 782 +AT+CNTFAC : Get or set counting parameters 776 776 777 -AT+SERVADDR : 784 +AT+SERVADDR : Server Address 778 778 779 -AT+TR : Get or Set record time" 780 780 781 -AT+APN : Get or set the APN 782 - 783 -AT+FBAND : Get or Set whether to automatically modify the frequency band 784 - 785 -AT+DNSCFG : Get or Set DNS Server 786 - 787 -AT+GETSENSORVALUE : Returns the current sensor measurement 788 - 789 -AT+NOUD : Get or Set the number of data to be uploaded 790 - 791 -AT+CDP : Read or Clear cached data 792 - 793 -AT+LDDSALARM : Get or Set alarm of distance 794 - 795 - 796 796 (% style="color:#037691" %)**COAP Management** 797 797 798 -AT+URI : 789 +AT+URI : Resource parameters 799 799 800 800 801 801 (% style="color:#037691" %)**UDP Management** 802 802 803 -AT+CFM : 794 +AT+CFM : Upload confirmation mode (only valid for UDP) 804 804 805 805 806 806 (% style="color:#037691" %)**MQTT Management** 807 807 808 -AT+CLIENT 799 +AT+CLIENT : Get or Set MQTT client 809 809 810 -AT+UNAME :Get or Set MQTT Username801 +AT+UNAME : Get or Set MQTT Username 811 811 812 -AT+PWD 803 +AT+PWD : Get or Set MQTT password 813 813 814 -AT+PUBTOPIC :Get or Set MQTT publish topic805 +AT+PUBTOPIC : Get or Set MQTT publish topic 815 815 816 -AT+SUBTOPIC :Get or Set MQTT subscription topic807 +AT+SUBTOPIC : Get or Set MQTT subscription topic 817 817 818 818 819 819 (% style="color:#037691" %)**Information** 820 820 821 -AT+FDR : 812 +AT+FDR : Factory Data Reset 822 822 823 -AT+PWORD : 814 +AT+PWORD : Serial Access Password 824 824 825 825 817 + 826 826 = 5. FAQ = 827 827 828 828 == 5.1 How to Upgrade Firmware == ... ... @@ -841,6 +841,7 @@ 841 841 ))) 842 842 843 843 836 + 844 844 = 6. Trouble Shooting = 845 845 846 846 == 6.1 Connection problem when uploading firmware == ... ... @@ -855,20 +855,17 @@ 855 855 856 856 ))) 857 857 851 + 858 858 == 6.2 AT Command input doesn't work == 859 859 860 860 861 861 ((( 862 862 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. 857 + 858 + 863 863 ))) 864 864 865 865 866 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 867 - 868 - 869 -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]]//**. 870 - 871 - 872 872 = 7. Order Info = 873 873 874 874 ... ... @@ -875,6 +875,11 @@ 875 875 Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 876 876 877 877 868 +(% class="wikigeneratedid" %) 869 +((( 870 + 871 +))) 872 + 878 878 = 8. Packing Info = 879 879 880 880 ((( ... ... @@ -900,6 +900,7 @@ 900 900 ((( 901 901 902 902 898 + 903 903 904 904 ))) 905 905 ... ... @@ -907,5 +907,4 @@ 907 907 908 908 909 909 * 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. 910 - 911 911 * 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-20220908175246-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -55.7 KB - Content
- image-20220908175333-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.1 KB - Content
- image-20221009001114-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content