<
From version < 100.3 >
edited by Xiaoling
on 2022/08/08 16:07
To version < 108.10 >
edited by Xiaoling
on 2023/04/04 12:01
>
Change comment: There is no comment for this version

Summary

Details

Page properties
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  (((
... ... @@ -70,8 +70,6 @@
70 70  * Micro SIM card slot for NB-IoT SIM
71 71  * 8500mAh Battery for long term use
72 72  
73 -
74 -
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: 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
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
91 91  
92 92  (% style="color:#037691" %)**Battery:**
93 93  
... ... @@ -102,8 +102,6 @@
102 102  * STOP Mode: 10uA @ 3.3v
103 103  * Max transmit power: 350mA@3.3v
104 104  
105 -
106 -
107 107  == ​1.4  Applications ==
108 108  
109 109  
... ... @@ -118,6 +118,7 @@
118 118  ​
119 119  
120 120  
118 +
121 121  == 1.5  Pin Definitions ==
122 122  
123 123  
... ... @@ -127,6 +127,7 @@
127 127  
128 128  = 2.  Use NDDS75 to communicate with IoT Server =
129 129  
128 +
130 130  == 2.1  How it works ==
131 131  
132 132  
... ... @@ -200,15 +200,16 @@
200 200  
201 201  [[image:image-20220709092052-2.png]]
202 202  
203 -**Connection:**
204 204  
205 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
203 +(% style="color:blue" %)**Connection:**
206 206  
207 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
205 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
208 208  
209 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
207 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
210 210  
209 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
211 211  
211 +
212 212  In the PC, use below serial tool settings:
213 213  
214 214  * Baud:  (% style="color:green" %)**9600**
... ... @@ -223,8 +223,9 @@
223 223  
224 224  [[image:1657329814315-101.png]]
225 225  
226 +
226 226  (((
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/]]
228 +(% 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]]**
228 228  )))
229 229  
230 230  
... ... @@ -243,21 +243,29 @@
243 243  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
244 244  )))
245 245  * (((
246 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
247 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
247 247  )))
248 248  * (((
249 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
250 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
251 +
252 +
253 +
250 250  )))
251 251  
252 252  (((
253 253  For parameter description, please refer to AT command set
258 +
259 +
254 254  )))
255 255  
256 256  [[image:1657330452568-615.png]]
257 257  
258 258  
265 +
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.
268 +
269 +
261 261  )))
262 262  
263 263  [[image:1657330472797-498.png]]
... ... @@ -267,9 +267,9 @@
267 267  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
268 268  
269 269  
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
279 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
280 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
281 +* (% 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  
... ... @@ -281,13 +281,13 @@
281 281  === 2.2.6 Use MQTT protocol to uplink data ===
282 282  
283 283  
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
293 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
294 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
295 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
296 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
297 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
298 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
299 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
291 291  
292 292  [[image:1657249978444-674.png]]
293 293  
... ... @@ -304,8 +304,8 @@
304 304  === 2.2.7 Use TCP protocol to uplink data ===
305 305  
306 306  
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
316 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
317 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
309 309  
310 310  [[image:image-20220709093918-1.png]]
311 311  
... ... @@ -319,24 +319,31 @@
319 319  
320 320  User can use below command to change the (% style="color:green" %)**uplink interval**.
321 321  
322 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
331 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
323 323  
324 324  (((
334 +
335 +
336 +
325 325  (% style="color:red" %)**NOTE:**
326 -)))
327 327  
328 -(((
329 329  (% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
340 +
341 +(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
330 330  )))
331 331  
344 +(% 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).**
332 332  
333 333  
347 +
334 334  == 2.3  Uplink Payload ==
335 335  
336 336  
337 -In this mode, uplink payload includes in total 14 bytes
351 +=== 2.3.1  Before Firmware v1.3.2 ===
338 338  
339 339  
354 +In this mode, uplink payload includes in total 14 bytes
355 +
340 340  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
341 341  |=(% style="width: 60px;" %)(((
342 342  **Size(bytes)**
... ... @@ -344,44 +344,74 @@
344 344  |(% 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"]]
345 345  
346 346  (((
347 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
363 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
348 348  )))
349 349  
350 350  
351 351  [[image:1657331036973-987.png]]
352 352  
353 -(((
369 +
370 +
371 +The payload is **ASCII** string, representative same HEX:
372 +
373 +(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
374 +
375 +**where :**
376 +
377 +* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
378 +
379 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
380 +
381 +* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
382 +
383 +* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
384 +
385 +* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
386 +
387 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
388 +
389 +=== 2.3.2  Since firmware v1.3.2 ===
390 +
391 +
392 +In this mode, uplink payload includes 69 bytes in total by default.
393 +
394 +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.
395 +
396 +(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
397 +|=(% 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**
398 +|=(% 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 +
400 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
401 +
402 +[[image:image-20220908175246-1.png]]
403 +
404 +
354 354  The payload is ASCII string, representative same HEX:
355 -)))
356 356  
357 -(((
358 -0x72403155615900640c6c19029200 where:
359 -)))
407 +**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 (%%)**
360 360  
361 -* (((
362 -Device ID: 0x724031556159 = 724031556159
363 -)))
364 -* (((
365 -Version: 0x0064=100=1.0.0
366 -)))
409 +**where:**
367 367  
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
411 +* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
379 379  
413 +* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
380 380  
415 +* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
381 381  
382 -
383 -)))
417 +* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
384 384  
419 +* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
420 +
421 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
422 +
423 +* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
424 +
425 +* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
426 +
427 +* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
428 +
429 +* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
430 +
385 385  == 2.4  Payload Explanation and Sensor Interface ==
386 386  
387 387  
... ... @@ -394,10 +394,12 @@
394 394  
395 395  (((
396 396  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
443 +
444 +
397 397  )))
398 398  
399 399  (((
400 -**Example:**
448 +(% style="color:blue" %)**Example :**
401 401  )))
402 402  
403 403  (((
... ... @@ -405,11 +405,23 @@
405 405  )))
406 406  
407 407  (((
408 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
456 +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.
409 409  )))
410 410  
411 411  
460 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
412 412  
462 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
463 +
464 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
465 +
466 +
467 +(% style="color:blue" %)**Example :**
468 +
469 +AT+DEUI=868411056754138
470 +
471 +
472 +
413 413  === 2.4.2  Version Info ===
414 414  
415 415  
... ... @@ -504,7 +504,7 @@
504 504  )))
505 505  
506 506  (((
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]])**.**
567 +(% 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]])**.**
508 508  )))
509 509  
510 510  
... ... @@ -537,10 +537,14 @@
537 537  
538 538  (((
539 539  The 5V output time can be controlled by AT Command.
600 +
601 +
540 540  )))
541 541  
542 542  (((
543 543  (% style="color:blue" %)**AT+5VT=1000**
606 +
607 +
544 544  )))
545 545  
546 546  (((
... ... @@ -602,125 +602,93 @@
602 602  
603 603  
604 604  
605 -== 2.6  ​LED Indicator ==
669 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
606 606  
607 607  
608 -The NDDS75 has an internal LED which is to show the status of different state.
672 +(% style="color:blue" %)** AT Command:**
609 609  
674 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
610 610  
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.
676 +² When min=0, and max≠0, Alarm higher than max
615 615  
616 -(((
617 -
618 -)))
678 +² When min≠0, and max=0, Alarm lower than min
619 619  
680 +² When min≠0 and max≠0, Alarm higher than max or lower than min
620 620  
621 621  
622 -== 2.7  ​Firmware Change Log ==
683 +(% style="color:blue" %)** Example:**
623 623  
685 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
624 624  
625 -(((
626 -Download URL & Firmware Change log
627 -)))
628 628  
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 -)))
632 632  
689 +== 2.7  Set the number of data to be uploaded and the recording time ==
633 633  
634 -(((
635 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
636 -)))
637 637  
692 +(% style="color:blue" %)** ➢ AT Command:**
638 638  
694 +* (% 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)
695 +* (% 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.
639 639  
640 -== 2.8  ​Battery Analysis ==
697 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
641 641  
642 -=== 2.8.1  ​Battery Type ===
699 +[[image:image-20221009001114-1.png||height="687" width="955"]]
643 643  
644 644  
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 -)))
648 648  
649 -(((
650 -The battery is designed to last for several years depends on the actually use environment and update interval. 
651 -)))
703 +== 2.8  Read or Clear cached data ==
652 652  
653 -(((
654 -The battery related documents as below:
655 -)))
656 656  
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/]]
706 +(% style="color:blue" %)** ➢ AT Command:**
660 660  
661 -(((
662 -[[image:image-20220709101450-2.png]]
663 -)))
708 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
709 +* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
664 664  
711 +[[image:image-20220908175333-2.png]]
665 665  
666 666  
667 -=== 2.8.2  Power consumption Analyze ===
668 668  
715 +== 2.9  ​LED Indicator ==
669 669  
670 -(((
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.
672 -)))
673 673  
718 +The NDDS75 has an internal LED which is to show the status of different state.
674 674  
675 -(((
676 -Instruction to use as below:
677 -)))
678 678  
721 +* 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)
722 +* Then the LED will be on for 1 second means device is boot normally.
723 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
724 +* For each uplink probe, LED will be on for 500ms.
725 +
679 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/]]
727 +
681 681  )))
682 682  
683 683  
731 +
732 +== 2.10  ​Firmware Change Log ==
733 +
734 +
684 684  (((
685 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
736 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]]
686 686  )))
687 687  
688 -* (((
689 -Product Model
690 -)))
691 -* (((
692 -Uplink Interval
693 -)))
694 -* (((
695 -Working Mode
696 -)))
697 -
698 698  (((
699 -And the Life expectation in difference case will be shown on the right.
740 +
700 700  )))
701 701  
702 -[[image:image-20220709110451-3.png]]
703 -
704 -
705 -
706 -=== 2.8.3  ​Battery Note ===
707 -
708 -
709 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.
744 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
711 711  )))
712 712  
713 713  
714 714  
715 -=== 2.8.4  Replace the battery ===
749 +== 2.11 Battery & Power Consumption ==
716 716  
717 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 -)))
752 +PS-LB-NA uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
721 721  
754 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
722 722  
723 -
724 724  = 3. ​ Access NB-IoT Module =
725 725  
726 726  
... ... @@ -730,6 +730,8 @@
730 730  
731 731  (((
732 732  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/]] 
765 +
766 +
733 733  )))
734 734  
735 735  [[image:1657333200519-600.png]]
... ... @@ -738,85 +738,103 @@
738 738  
739 739  = 4.  Using the AT Commands =
740 740  
775 +
741 741  == 4.1  Access AT Commands ==
742 742  
743 743  
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/]]
779 +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]]
745 745  
746 746  
747 -AT+<CMD>?  : Help on <CMD>
782 +AT+<CMD>?  :  Help on <CMD>
748 748  
749 -AT+<CMD>         : Run <CMD>
784 +AT+<CMD>         :  Run <CMD>
750 750  
751 -AT+<CMD>=<value> : Set the value
786 +AT+<CMD>=<value> :  Set the value
752 752  
753 -AT+<CMD>=?  : Get the value
788 +AT+<CMD>=?  :  Get the value
754 754  
755 755  
756 756  (% style="color:#037691" %)**General Commands**(%%)      
757 757  
758 -AT  : Attention       
793 +AT  :  Attention       
759 759  
760 -AT?  : Short Help     
795 +AT?  :  Short Help     
761 761  
762 -ATZ  : MCU Reset    
797 +ATZ  :  MCU Reset    
763 763  
764 -AT+TDC  : Application Data Transmission Interval
799 +AT+TDC  :  Application Data Transmission Interval
765 765  
766 -AT+CFG  : Print all configurations
801 +AT+CFG  :  Print all configurations
767 767  
768 -AT+CFGMOD           : Working mode selection
803 +AT+CFGMOD           :  Working mode selection
769 769  
770 -AT+INTMOD            : Set the trigger interrupt mode
805 +AT+INTMOD            :  Set the trigger interrupt mode
771 771  
772 -AT+5VT  : Set extend the time of 5V power  
807 +AT+5VT  :  Set extend the time of 5V power  
773 773  
774 -AT+PRO  : Choose agreement
809 +AT+PRO  :  Choose agreement
775 775  
776 -AT+WEIGRE  : Get weight or set weight to 0
811 +AT+WEIGRE  :  Get weight or set weight to 0
777 777  
778 -AT+WEIGAP  : Get or Set the GapValue of weight
813 +AT+WEIGAP  :  Get or Set the GapValue of weight
779 779  
780 -AT+RXDL  : Extend the sending and receiving time
815 +AT+RXDL  :  Extend the sending and receiving time
781 781  
782 -AT+CNTFAC  : Get or set counting parameters
817 +AT+CNTFAC  :  Get or set counting parameters
783 783  
784 -AT+SERVADDR  : Server Address
819 +AT+SERVADDR  :  Server Address
785 785  
821 +AT+TR  :  Get or Set record time"
786 786  
823 +AT+APN     :  Get or set the APN
824 +
825 +AT+FBAND  :  Get or Set whether to automatically modify the frequency band
826 +
827 +AT+DNSCFG  : Get or Set DNS Server
828 +
829 +AT+GETSENSORVALUE   :  Returns the current sensor measurement
830 +
831 +AT+NOUD  :  Get or Set the number of data to be uploaded
832 +
833 +AT+CDP     :  Read or Clear cached data
834 +
835 +AT+LDDSALARM :  Get or Set alarm of distance
836 +
837 +
787 787  (% style="color:#037691" %)**COAP Management**      
788 788  
789 -AT+URI            : Resource parameters
840 +AT+URI            :  Resource parameters
790 790  
791 791  
792 792  (% style="color:#037691" %)**UDP Management**
793 793  
794 -AT+CFM          : Upload confirmation mode (only valid for UDP)
845 +AT+CFM          :  Upload confirmation mode (only valid for UDP)
795 795  
796 796  
797 797  (% style="color:#037691" %)**MQTT Management**
798 798  
799 -AT+CLIENT               : Get or Set MQTT client
850 +AT+CLIENT  :  Get or Set MQTT client
800 800  
801 -AT+UNAME  : Get or Set MQTT Username
852 +AT+UNAME  :  Get or Set MQTT Username
802 802  
803 -AT+PWD                  : Get or Set MQTT password
854 +AT+PWD  :  Get or Set MQTT password
804 804  
805 -AT+PUBTOPIC  : Get or Set MQTT publish topic
856 +AT+PUBTOPIC  :  Get or Set MQTT publish topic
806 806  
807 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
858 +AT+SUBTOPIC  :  Get or Set MQTT subscription topic
808 808  
809 809  
810 810  (% style="color:#037691" %)**Information**          
811 811  
812 -AT+FDR  : Factory Data Reset
863 +AT+FDR  :  Factory Data Reset
813 813  
814 -AT+PWORD  : Serial Access Password
865 +AT+PWORD  :  Serial Access Password
815 815  
816 816  
817 817  
818 818  = ​5.  FAQ =
819 819  
871 +
820 820  == 5.1 ​ How to Upgrade Firmware ==
821 821  
822 822  
... ... @@ -836,6 +836,7 @@
836 836  
837 837  = 6.  Trouble Shooting =
838 838  
891 +
839 839  == 6.1  ​Connection problem when uploading firmware ==
840 840  
841 841  
... ... @@ -884,6 +884,7 @@
884 884  (((
885 885  
886 886  
940 +
887 887  (% style="color:#037691" %)**Dimension and weight**:
888 888  
889 889  * Device Size: 13.0 x 5 x 4.5 cm
image-20220908175246-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +31.1 KB
Content
image-20221009001114-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +282.9 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0