Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 104.7 >
edited by Xiaoling
on 2022/09/15 15:02
To version < 108.13 >
edited by Xiaoling
on 2023/04/24 10:07
>
Change comment: There is no comment for this version

Summary

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  
... ... @@ -83,12 +83,12 @@
83 83  
84 84  (% style="color:#037691" %)**NB-IoT Spec:**
85 85  
86 -* - B1 @H-FDD: 2100MHz
87 -* - B3 @H-FDD: 1800MHz
88 -* - B8 @H-FDD: 900MHz
89 -* - B5 @H-FDD: 850MHz
90 -* - B20 @H-FDD: 800MHz
91 -* - 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
92 92  
93 93  (% style="color:#037691" %)**Battery:**
94 94  
... ... @@ -119,8 +119,6 @@
119 119  ​
120 120  
121 121  
122 -
123 -
124 124  == 1.5  Pin Definitions ==
125 125  
126 126  
... ... @@ -127,10 +127,8 @@
127 127  [[image:1657328609906-564.png]]
128 128  
129 129  
130 -
131 131  = 2.  Use NDDS75 to communicate with IoT Server =
132 132  
133 -
134 134  == 2.1  How it works ==
135 135  
136 136  
... ... @@ -153,10 +153,8 @@
153 153  
154 154  )))
155 155  
156 -
157 157  == 2.2 ​ Configure the NDDS75 ==
158 158  
159 -
160 160  === 2.2.1 Test Requirement ===
161 161  
162 162  
... ... @@ -176,7 +176,6 @@
176 176  [[image:1657328756309-230.png]]
177 177  
178 178  
179 -
180 180  === 2.2.2 Insert SIM card ===
181 181  
182 182  
... ... @@ -192,7 +192,6 @@
192 192  [[image:1657328884227-504.png]]
193 193  
194 194  
195 -
196 196  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
197 197  
198 198  
... ... @@ -234,7 +234,6 @@
234 234  )))
235 235  
236 236  
237 -
238 238  === 2.2.4 Use CoAP protocol to uplink data ===
239 239  
240 240  
... ... @@ -277,7 +277,6 @@
277 277  [[image:1657330472797-498.png]]
278 278  
279 279  
280 -
281 281  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
282 282  
283 283  
... ... @@ -285,8 +285,6 @@
285 285  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
286 286  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
287 287  
288 -
289 -
290 290  [[image:1657330501006-241.png]]
291 291  
292 292  
... ... @@ -293,7 +293,6 @@
293 293  [[image:1657330533775-472.png]]
294 294  
295 295  
296 -
297 297  === 2.2.6 Use MQTT protocol to uplink data ===
298 298  
299 299  
... ... @@ -316,7 +316,6 @@
316 316  )))
317 317  
318 318  
319 -
320 320  === 2.2.7 Use TCP protocol to uplink data ===
321 321  
322 322  
... ... @@ -329,7 +329,6 @@
329 329  [[image:image-20220709093918-2.png]]
330 330  
331 331  
332 -
333 333  === 2.2.8 Change Update Interval ===
334 334  
335 335  
... ... @@ -351,10 +351,8 @@
351 351  (% 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).**
352 352  
353 353  
354 -
355 355  == 2.3  Uplink Payload ==
356 356  
357 -
358 358  === 2.3.1  Before Firmware v1.3.2 ===
359 359  
360 360  
... ... @@ -367,7 +367,7 @@
367 367  |(% 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"]]
368 368  
369 369  (((
370 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
351 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
371 371  )))
372 372  
373 373  
... ... @@ -374,49 +374,34 @@
374 374  [[image:1657331036973-987.png]]
375 375  
376 376  
377 -(((
378 378  The payload is **ASCII** string, representative same HEX:
379 -)))
380 380  
381 -(((
382 -0x72403155615900640c6c19029200 where:
383 -)))
360 +(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
384 384  
385 -* (((
386 -Device ID: 0x724031556159 = 724031556159
387 -)))
388 -* (((
389 -Version:  0x0064=100=1.0.0
390 -)))
362 +**where :**
391 391  
392 -* (((
393 -BAT:  0x0c6c = 3180 mV = 3.180V
394 -)))
395 -* (((
396 -Signal: 0x19 = 25
397 -)))
398 -* (((
399 -Distance: 0x0292= 658 mm
400 -)))
401 -* (((
402 -Interrupt: 0x00 = 0
364 +* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
403 403  
366 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
404 404  
368 +* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
405 405  
370 +* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
406 406  
407 -
408 -)))
372 +* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
409 409  
410 -=== **2.3.2  Since firmware v1.3.2** ===
374 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
411 411  
376 +=== 2.3.2  Since firmware v1.3.2 ===
412 412  
378 +
413 413  In this mode, uplink payload includes 69 bytes in total by default.
414 414  
415 415  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.
416 416  
417 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
418 -|(% 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" %)4
419 -|(% 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.......
383 +(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
384 +|=(% 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**
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.......
420 420  
421 421  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
422 422  
... ... @@ -425,24 +425,32 @@
425 425  
426 426  The payload is ASCII string, representative same HEX:
427 427  
428 -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 +**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 (%%)**
429 429  
430 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
431 -* (% style="color:red" %)Version: 0x0084=132=1.3.2
432 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
433 -* (% style="color:blue" %)Singal: 0x1e = 30
434 -* (% style="color:red" %)Mod: 0x01 = 1
435 -* Interrupt: 0x00= 0
436 -* Distance: 0x0039= 57 = 57
437 -* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
438 -* Distance,Time stamp : 00396319baf0
439 -* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
396 +**where:**
440 440  
398 +* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
441 441  
400 +* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
442 442  
443 -== 2.4  Payload Explanation and Sensor Interface ==
402 +* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
444 444  
404 +* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
445 445  
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 +== 2.4  Payload Explanation and Sensor Interface ==
419 +
446 446  === 2.4.1  Device ID ===
447 447  
448 448  
... ... @@ -481,7 +481,6 @@
481 481  AT+DEUI=868411056754138
482 482  
483 483  
484 -
485 485  === 2.4.2  Version Info ===
486 486  
487 487  
... ... @@ -494,7 +494,6 @@
494 494  )))
495 495  
496 496  
497 -
498 498  === 2.4.3  Battery Info ===
499 499  
500 500  
... ... @@ -507,7 +507,6 @@
507 507  )))
508 508  
509 509  
510 -
511 511  === 2.4.4  Signal Strength ===
512 512  
513 513  
... ... @@ -540,7 +540,6 @@
540 540  )))
541 541  
542 542  
543 -
544 544  === 2.4.5  Distance ===
545 545  
546 546  
... ... @@ -560,10 +560,6 @@
560 560  
561 561  )))
562 562  
563 -(((
564 -
565 -)))
566 -
567 567  === 2.4.6  Digital Interrupt ===
568 568  
569 569  
... ... @@ -598,7 +598,6 @@
598 598  )))
599 599  
600 600  
601 -
602 602  === 2.4.7  ​+5V Output ===
603 603  
604 604  
... ... @@ -624,7 +624,6 @@
624 624  )))
625 625  
626 626  
627 -
628 628  == 2.5  Downlink Payload ==
629 629  
630 630  
... ... @@ -677,7 +677,6 @@
677 677  )))
678 678  
679 679  
680 -
681 681  == 2.6  Distance alarm function(Since firmware v1.3.2) ==
682 682  
683 683  
... ... @@ -697,7 +697,6 @@
697 697  **AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
698 698  
699 699  
700 -
701 701  == 2.7  Set the number of data to be uploaded and the recording time ==
702 702  
703 703  
... ... @@ -704,9 +704,11 @@
704 704  (% style="color:blue" %)** ➢ AT Command:**
705 705  
706 706  * (% 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)
707 -* (% 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.
669 +* (% 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.
708 708  
671 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
709 709  
673 +[[image:image-20221009001114-1.png||height="687" width="955"]]
710 710  
711 711  
712 712  == 2.8  Read or Clear cached data ==
... ... @@ -720,7 +720,6 @@
720 720  [[image:image-20220908175333-2.png]]
721 721  
722 722  
723 -
724 724  == 2.9  ​LED Indicator ==
725 725  
726 726  
... ... @@ -737,7 +737,6 @@
737 737  )))
738 738  
739 739  
740 -
741 741  == 2.10  ​Firmware Change Log ==
742 742  
743 743  
... ... @@ -746,100 +746,18 @@
746 746  )))
747 747  
748 748  (((
749 -
750 -)))
751 -
752 -(((
753 753  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
754 754  )))
755 755  
756 756  
715 +== 2.11 Battery & Power Consumption ==
757 757  
758 -== 2.11  ​Battery Analysis ==
759 759  
718 +NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
760 760  
761 -=== 2.11.1  ​Battery Type ===
720 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
762 762  
763 763  
764 -(((
765 -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.
766 -)))
767 -
768 -(((
769 -The battery is designed to last for several years depends on the actually use environment and update interval. 
770 -)))
771 -
772 -(((
773 -The battery related documents as below:
774 -)))
775 -
776 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
777 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
778 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
779 -
780 -(((
781 -[[image:image-20220709101450-2.png]]
782 -)))
783 -
784 -
785 -
786 -=== 2.11.2  Power consumption Analyze ===
787 -
788 -
789 -(((
790 -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.
791 -)))
792 -
793 -
794 -(((
795 -Instruction to use as below:
796 -)))
797 -
798 -(((
799 -(% 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/]]
800 -)))
801 -
802 -
803 -(((
804 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
805 -)))
806 -
807 -* (((
808 -Product Model
809 -)))
810 -* (((
811 -Uplink Interval
812 -)))
813 -* (((
814 -Working Mode
815 -)))
816 -
817 -(((
818 -And the Life expectation in difference case will be shown on the right.
819 -)))
820 -
821 -[[image:image-20220709110451-3.png]]
822 -
823 -
824 -
825 -=== 2.11.3  ​Battery Note ===
826 -
827 -
828 -(((
829 -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.
830 -)))
831 -
832 -
833 -
834 -=== 2.11.4  Replace the battery ===
835 -
836 -
837 -(((
838 -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).
839 -)))
840 -
841 -
842 -
843 843  = 3. ​ Access NB-IoT Module =
844 844  
845 845  
... ... @@ -856,10 +856,8 @@
856 856  [[image:1657333200519-600.png]]
857 857  
858 858  
859 -
860 860  = 4.  Using the AT Commands =
861 861  
862 -
863 863  == 4.1  Access AT Commands ==
864 864  
865 865  
... ... @@ -952,10 +952,8 @@
952 952  AT+PWORD  :  Serial Access Password
953 953  
954 954  
955 -
956 956  = ​5.  FAQ =
957 957  
958 -
959 959  == 5.1 ​ How to Upgrade Firmware ==
960 960  
961 961  
... ... @@ -972,10 +972,8 @@
972 972  )))
973 973  
974 974  
975 -
976 976  = 6.  Trouble Shooting =
977 977  
978 -
979 979  == 6.1  ​Connection problem when uploading firmware ==
980 980  
981 981  
... ... @@ -988,17 +988,20 @@
988 988  
989 989  )))
990 990  
991 -
992 992  == 6.2  AT Command input doesn't work ==
993 993  
994 994  
995 995  (((
996 996  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.
997 -
998 -
999 999  )))
1000 1000  
1001 1001  
873 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
874 +
875 +
876 +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]]//**.
877 +
878 +
1002 1002  = 7. ​ Order Info =
1003 1003  
1004 1004  
... ... @@ -1005,11 +1005,6 @@
1005 1005  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1006 1006  
1007 1007  
1008 -(% class="wikigeneratedid" %)
1009 -(((
1010 -
1011 -)))
1012 -
1013 1013  = 8.  Packing Info =
1014 1014  
1015 1015  (((
... ... @@ -1024,7 +1024,6 @@
1024 1024  (((
1025 1025  
1026 1026  
1027 -
1028 1028  (% style="color:#037691" %)**Dimension and weight**:
1029 1029  
1030 1030  * Device Size: 13.0 x 5 x 4.5 cm
... ... @@ -1036,7 +1036,6 @@
1036 1036  (((
1037 1037  
1038 1038  
1039 -
1040 1040  
1041 1041  )))
1042 1042  
... ... @@ -1044,4 +1044,5 @@
1044 1044  
1045 1045  
1046 1046  * 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.
917 +
1047 1047  * 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

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0