Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 108.20
edited by Xiaoling
on 2023/05/25 14:59
on 2023/05/25 14:59
Change comment:
There is no comment for this version
To version 103.1
edited by David Huang
on 2022/09/08 18:02
on 2022/09/08 18:02
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.David - Content
-
... ... @@ -16,6 +16,7 @@ 16 16 17 17 = 1. Introduction = 18 18 19 + 19 19 == 1.1 What is NDDS75 Distance Detection Sensor == 20 20 21 21 ((( ... ... @@ -53,6 +53,7 @@ 53 53 [[image:1657327959271-447.png]] 54 54 55 55 57 + 56 56 == 1.2 Features == 57 57 58 58 ... ... @@ -80,12 +80,12 @@ 80 80 81 81 (% style="color:#037691" %)**NB-IoT Spec:** 82 82 83 -* 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 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 89 89 90 90 (% style="color:#037691" %)**Battery:** 91 91 ... ... @@ -115,6 +115,8 @@ 115 115 116 116 117 117 120 + 121 + 118 118 == 1.5 Pin Definitions == 119 119 120 120 ... ... @@ -121,8 +121,10 @@ 121 121 [[image:1657328609906-564.png]] 122 122 123 123 128 + 124 124 = 2. Use NDDS75 to communicate with IoT Server = 125 125 131 + 126 126 == 2.1 How it works == 127 127 128 128 ... ... @@ -145,8 +145,10 @@ 145 145 146 146 ))) 147 147 154 + 148 148 == 2.2 Configure the NDDS75 == 149 149 157 + 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 177 + 169 169 === 2.2.2 Insert SIM card === 170 170 171 171 ... ... @@ -181,6 +181,7 @@ 181 181 [[image:1657328884227-504.png]] 182 182 183 183 193 + 184 184 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 185 185 186 186 ... ... @@ -193,13 +193,13 @@ 193 193 [[image:image-20220709092052-2.png]] 194 194 195 195 196 - (% style="color:blue" %)**Connection:**206 +**Connection:** 197 197 198 - (% style="background-color:yellow" %) **USB TTL GND <~-~-~-~-> GND**208 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 199 199 200 - **~(% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**210 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 201 201 202 - **~(% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**212 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 203 203 204 204 205 205 In the PC, use below serial tool settings: ... ... @@ -222,6 +222,7 @@ 222 222 ))) 223 223 224 224 235 + 225 225 === 2.2.4 Use CoAP protocol to uplink data === 226 226 227 227 ... ... @@ -236,10 +236,10 @@ 236 236 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 237 237 ))) 238 238 * ((( 239 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ 250 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 240 240 ))) 241 241 * ((( 242 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ 253 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 243 243 244 244 245 245 ... ... @@ -247,8 +247,6 @@ 247 247 248 248 ((( 249 249 For parameter description, please refer to AT command set 250 - 251 - 252 252 ))) 253 253 254 254 [[image:1657330452568-615.png]] ... ... @@ -257,19 +257,18 @@ 257 257 258 258 ((( 259 259 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. 260 - 261 - 262 262 ))) 263 263 264 264 [[image:1657330472797-498.png]] 265 265 266 266 274 + 267 267 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 268 268 269 269 270 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ 271 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ 272 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 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 273 273 274 274 [[image:1657330501006-241.png]] 275 275 ... ... @@ -277,16 +277,17 @@ 277 277 [[image:1657330533775-472.png]] 278 278 279 279 288 + 280 280 === 2.2.6 Use MQTT protocol to uplink data === 281 281 282 282 283 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ 284 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ 285 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ 286 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ 287 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ 288 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ 289 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ 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 290 290 291 291 [[image:1657249978444-674.png]] 292 292 ... ... @@ -299,11 +299,12 @@ 299 299 ))) 300 300 301 301 311 + 302 302 === 2.2.7 Use TCP protocol to uplink data === 303 303 304 304 305 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ 306 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ 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 307 308 308 [[image:image-20220709093918-1.png]] 309 309 ... ... @@ -311,42 +311,39 @@ 311 311 [[image:image-20220709093918-2.png]] 312 312 313 313 324 + 314 314 === 2.2.8 Change Update Interval === 315 315 316 316 317 317 User can use below command to change the (% style="color:green" %)**uplink interval**. 318 318 319 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ 330 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 320 320 321 321 ((( 322 - 333 +(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.** 323 323 324 - 325 -(% style="color:red" %)**NOTE:** 326 - 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:** 335 + 330 330 ))) 331 331 332 - (% style="color:red" %)**By default,thedevicewill sendan uplink messageevery 2 hours. Each Uplink Include 8 setof records inthis 2hour (15 minute interval /record).**338 +**NOTE:When the firmware version is v1.3.2 and later firmware:** 333 333 340 +**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).** 334 334 342 + 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" %)((( 348 + 349 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 350 +|=(% 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**352 +)))|=(% 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. 356 +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,70 +353,67 @@ 353 353 [[image:1657331036973-987.png]] 354 354 355 355 356 -The payload is **ASCII** string, representative same HEX: 363 +((( 364 +The payload is ASCII string, representative same HEX: 365 +))) 357 357 358 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** 367 +((( 368 +0x72403155615900640c6c19029200 where: 369 +))) 359 359 360 -**where :** 371 +* ((( 372 +Device ID: 0x724031556159 = 724031556159 373 +))) 374 +* ((( 375 +Version: 0x0064=100=1.0.0 376 +))) 361 361 362 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159 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 363 363 364 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 390 + 391 +))) 365 365 366 -* (% style="color:#037691" %)**BAT:**(%%)0x0c6c = 3180mV=3.180V393 +**NOTE:When the firmware version is v1.3.2 and later firmware:** 367 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 -=== 2.3.2 Since firmware v1.3.2 === 376 - 377 - 378 378 In this mode, uplink payload includes 69 bytes in total by default. 379 379 380 380 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. 381 381 382 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:490px" %) 383 -|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:70px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**4** 384 -|=(% 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....... 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 385 386 386 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 387 387 388 388 [[image:image-20220908175246-1.png]] 389 389 390 - 391 391 The payload is ASCII string, representative same HEX: 392 392 393 - **0x#00b0f0" %)1e#7030a0" %)01#d60093" %)00(% style="color:#a14d07" %)(% style="color:#0020b0" %)6315537b(% style="color:#663300" %)00396319baf0**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: 394 394 395 -**where:** 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**//,....... 396 396 397 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317 398 - 399 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2 400 - 401 -* (% style="color:#037691" %)**BAT:**(%%) 0x0cf4 = 3316 mV = 3.316V 402 - 403 -* (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 404 - 405 -* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 406 - 407 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 408 - 409 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57 410 - 411 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 412 - 413 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0 414 - 415 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 416 - 417 - 418 418 == 2.4 Payload Explanation and Sensor Interface == 419 419 423 + 420 420 === 2.4.1 Device ID === 421 421 422 422 ... ... @@ -431,7 +431,7 @@ 431 431 ))) 432 432 433 433 ((( 434 - (% style="color:blue" %)**Example438 +**Example:** 435 435 ))) 436 436 437 437 ((( ... ... @@ -439,22 +439,20 @@ 439 439 ))) 440 440 441 441 ((( 442 -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.446 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 443 443 ))) 444 444 445 445 446 - (% style="color:red" %)**NOTE:450 +**NOTE:When the firmware version is v1.3.2 and later firmware:** 447 447 448 - (% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**452 +By default, the Device ID equal to the last 15 bits of IMEI. 449 449 450 -User can use (% style="color:blue" %)**AT+DEUI**(%%)to set Device ID454 +User can use **AT+DEUI** to set Device ID 451 451 456 +**Example:** 452 452 453 -(% style="color:blue" %)**Example :** 454 - 455 455 AT+DEUI=868411056754138 456 456 457 - 458 458 === 2.4.2 Version Info === 459 459 460 460 ... ... @@ -467,6 +467,7 @@ 467 467 ))) 468 468 469 469 472 + 470 470 === 2.4.3 Battery Info === 471 471 472 472 ... ... @@ -479,6 +479,7 @@ 479 479 ))) 480 480 481 481 485 + 482 482 === 2.4.4 Signal Strength === 483 483 484 484 ... ... @@ -511,6 +511,7 @@ 511 511 ))) 512 512 513 513 518 + 514 514 === 2.4.5 Distance === 515 515 516 516 ... ... @@ -530,6 +530,10 @@ 530 530 531 531 ))) 532 532 538 +((( 539 + 540 +))) 541 + 533 533 === 2.4.6 Digital Interrupt === 534 534 535 535 ... ... @@ -542,7 +542,7 @@ 542 542 ))) 543 543 544 544 ((( 545 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/ 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]])**.** 546 546 ))) 547 547 548 548 ... ... @@ -564,6 +564,7 @@ 564 564 ))) 565 565 566 566 576 + 567 567 === 2.4.7 +5V Output === 568 568 569 569 ... ... @@ -589,17 +589,15 @@ 589 589 ))) 590 590 591 591 602 + 592 592 == 2.5 Downlink Payload == 593 593 594 594 595 595 By default, NDDS75 prints the downlink payload to console port. 596 596 597 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %) 598 -|(% 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)** 599 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4 600 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2 601 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4 608 +[[image:image-20220709100028-1.png]] 602 602 610 + 603 603 ((( 604 604 (% style="color:blue" %)**Examples:** 605 605 ))) ... ... @@ -644,13 +644,12 @@ 644 644 ))) 645 645 646 646 647 -== 2.6 (Sincefirmware v1.3.2)==655 +== 2.6 Distance alarm function == 648 648 657 +➢ AT Command: 649 649 650 - (% style="color:blue" %)** ➢ATCommand:**659 +AT+ LDDSALARM=min,max 651 651 652 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max** 653 - 654 654 ² When min=0, and max≠0, Alarm higher than max 655 655 656 656 ² When min≠0, and max=0, Alarm lower than min ... ... @@ -657,35 +657,28 @@ 657 657 658 658 ² When min≠0 and max≠0, Alarm higher than max or lower than min 659 659 667 +Example: 660 660 661 - (%style="color:blue"%)** Example:**669 +AT+ LDDSALARM=260,2000 ~/~/ Alarm when distance lower than 260. 662 662 663 -**AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 664 664 672 +== 2.7 Set the number of data to be uploaded and the recording time == 665 665 666 - ==2.7Set the numberof data to be uploaded andthe recording time ==674 +➢ AT Command: 667 667 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) 668 668 669 - (%style="color:blue"%)**➢ATCommand:**678 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 670 670 671 -* (% 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) 672 -* (% 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. 680 +== 2.8 Read or Clear cached data == 673 673 674 - T hediagram below explains the relationship between TR, NOUD, andTDC more clearly**:**682 +➢ AT Command: 675 675 676 - [[image:image-20221009001114-1.png||height="687"width="955"]]684 +AT+CDP ~/~/ Read cached data 677 677 678 - 679 -== 2.8 Read or Clear cached data == 680 - 681 - 682 -(% style="color:blue" %)** ➢ AT Command:** 683 - 684 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 685 -* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 686 - 687 687 [[image:image-20220908175333-2.png]] 688 688 688 +AT+CDP=0 ~/~/ Clear cached data 689 689 690 690 == 2.9 LED Indicator == 691 691 ... ... @@ -703,6 +703,7 @@ 703 703 ))) 704 704 705 705 706 + 706 706 == 2.10 Firmware Change Log == 707 707 708 708 ... ... @@ -711,18 +711,100 @@ 711 711 ))) 712 712 713 713 ((( 715 + 716 +))) 717 + 718 +((( 714 714 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 715 715 ))) 716 716 717 717 718 -== 2.11 Battery & Power Consumption == 719 719 724 +== 2.11 Battery Analysis == 720 720 721 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 722 722 723 - [[**BatteryInfo & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]].727 +=== 2.11.1 Battery Type === 724 724 725 725 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 + 726 726 = 3. Access NB-IoT Module = 727 727 728 728 ... ... @@ -739,8 +739,10 @@ 739 739 [[image:1657333200519-600.png]] 740 740 741 741 825 + 742 742 = 4. Using the AT Commands = 743 743 828 + 744 744 == 4.1 Access AT Commands == 745 745 746 746 ... ... @@ -747,94 +747,96 @@ 747 747 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]] 748 748 749 749 750 -AT+<CMD>? : 835 +AT+<CMD>? : Help on <CMD> 751 751 752 -AT+<CMD> : 837 +AT+<CMD> : Run <CMD> 753 753 754 -AT+<CMD>=<value> : 839 +AT+<CMD>=<value> : Set the value 755 755 756 -AT+<CMD>=? : 841 +AT+<CMD>=? : Get the value 757 757 758 758 759 759 (% style="color:#037691" %)**General Commands**(%%) 760 760 761 -AT : 846 +AT : Attention 762 762 763 -AT? : 848 +AT? : Short Help 764 764 765 -ATZ : 850 +ATZ : MCU Reset 766 766 767 -AT+TDC : 852 +AT+TDC : Application Data Transmission Interval 768 768 769 -AT+CFG : 854 +AT+CFG : Print all configurations 770 770 771 -AT+CFGMOD : 856 +AT+CFGMOD : Working mode selection 772 772 773 -AT+INTMOD : 858 +AT+INTMOD : Set the trigger interrupt mode 774 774 775 -AT+5VT : 860 +AT+5VT : Set extend the time of 5V power 776 776 777 -AT+PRO : 862 +AT+PRO : Choose agreement 778 778 779 -AT+WEIGRE : 864 +AT+WEIGRE : Get weight or set weight to 0 780 780 781 -AT+WEIGAP : 866 +AT+WEIGAP : Get or Set the GapValue of weight 782 782 783 -AT+RXDL : 868 +AT+RXDL : Extend the sending and receiving time 784 784 785 -AT+CNTFAC : 870 +AT+CNTFAC : Get or set counting parameters 786 786 787 -AT+SERVADDR : 872 +AT+SERVADDR : Server Address 788 788 789 -AT+TR 874 +AT+TR : Get or Set record time" 790 790 791 -AT+APN : 876 +AT+APN : Get or set the APN 792 792 793 -AT+FBAND : 878 +AT+FBAND : Get or Set whether to automatically modify the frequency band 794 794 795 -AT+DNSCFG : Get or Set DNS Server 880 +AT+DNSCFG : Get or Set DNS Server 796 796 797 -AT+GETSENSORVALUE : 882 +AT+GETSENSORVALUE : Returns the current sensor measurement 798 798 799 -AT+NOUD : 884 +AT+NOUD : Get or Set the number of data to be uploaded 800 800 801 -AT+CDP : 886 +AT+CDP : Read or Clear cached data 802 802 803 -AT+LDDSALARM : 888 +AT+LDDSALARM : Get or Set alarm of distance 804 804 805 805 806 806 (% style="color:#037691" %)**COAP Management** 807 807 808 -AT+URI : 893 +AT+URI : Resource parameters 809 809 810 810 811 811 (% style="color:#037691" %)**UDP Management** 812 812 813 -AT+CFM : 898 +AT+CFM : Upload confirmation mode (only valid for UDP) 814 814 815 815 816 816 (% style="color:#037691" %)**MQTT Management** 817 817 818 -AT+CLIENT 903 +AT+CLIENT : Get or Set MQTT client 819 819 820 -AT+UNAME :Get or Set MQTT Username905 +AT+UNAME : Get or Set MQTT Username 821 821 822 -AT+PWD 907 +AT+PWD : Get or Set MQTT password 823 823 824 -AT+PUBTOPIC :Get or Set MQTT publish topic909 +AT+PUBTOPIC : Get or Set MQTT publish topic 825 825 826 -AT+SUBTOPIC :Get or Set MQTT subscription topic911 +AT+SUBTOPIC : Get or Set MQTT subscription topic 827 827 828 828 829 829 (% style="color:#037691" %)**Information** 830 830 831 -AT+FDR : 916 +AT+FDR : Factory Data Reset 832 832 833 -AT+PWORD : 918 +AT+PWORD : Serial Access Password 834 834 835 835 921 + 836 836 = 5. FAQ = 837 837 924 + 838 838 == 5.1 How to Upgrade Firmware == 839 839 840 840 ... ... @@ -851,8 +851,10 @@ 851 851 ))) 852 852 853 853 941 + 854 854 = 6. Trouble Shooting = 855 855 944 + 856 856 == 6.1 Connection problem when uploading firmware == 857 857 858 858 ... ... @@ -865,20 +865,17 @@ 865 865 866 866 ))) 867 867 957 + 868 868 == 6.2 AT Command input doesn't work == 869 869 870 870 871 871 ((( 872 872 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 + 873 873 ))) 874 874 875 875 876 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 877 - 878 - 879 -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]]//**. 880 - 881 - 882 882 = 7. Order Info = 883 883 884 884 ... ... @@ -885,6 +885,11 @@ 885 885 Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 886 886 887 887 974 +(% class="wikigeneratedid" %) 975 +((( 976 + 977 +))) 978 + 888 888 = 8. Packing Info = 889 889 890 890 ((( ... ... @@ -899,6 +899,7 @@ 899 899 ((( 900 900 901 901 993 + 902 902 (% style="color:#037691" %)**Dimension and weight**: 903 903 904 904 * Device Size: 13.0 x 5 x 4.5 cm ... ... @@ -910,6 +910,7 @@ 910 910 ((( 911 911 912 912 1005 + 913 913 914 914 ))) 915 915 ... ... @@ -917,5 +917,4 @@ 917 917 918 918 919 919 * 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. 920 - 921 921 * 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